new smartphone, LMP recording very few points. CAT S42 from CAT S41

[balloni55]

I don't have any of your $GPGGA sentences

do you find $GNGGA sentence ?

EDIT:
and if, please share them with your answer

[pat22043@gmail.com]

Here is a list of all the keywords in my NMEA test file:
$BDGSA
$BDGSV
$GAGSA
$GAGSV
$GLGSA
$GLGSV
$GNACCURACY
$GNGGA
$GNRMC
$GNVTG
$GPGSA
$GPGSV
$PMTKAG2
$PMTKAGC
$PMTKGALM
$PMTKGEPH
$PMTKTSX1

There are 3305 of the $GNGGA sentences. Attached.

[balloni55]

for me it looks not so bad if i display your GNGAA values with
e.g.
https://www.routeconverter.de/home/en
looks the recorded track diplayed inside LMP different??

[pat22043@gmail.com]

Sorry, I was unclear.
I have no good data of a case where the GPX data is missing parts, where I also have the NMEA data.
This NMEA data was from a 20 mile trip within suburban Philly. Both the LMP GPX file and the NMEA data are complete.

I also have run Google's GNSS logger. https://developer.android.com/guide/topics/sensors/gnss
which records all the raw data. But again, only on a 20 mile local trip.

The issue happens when I drive two hours, get on my dirt bike and ride in areas out in the boondocks.

[michaelbechtold]

As only a comparison between raw data and Locus can point the right direction for analysis, you have to wait until you do this exercise again, then compare.

[pat22043@gmail.com]

As only a comparison between raw data and Locus can point the right direction for analysis, you have to wait until you do this exercise again, then compare.

Success. Or repeated failure.
Here is a session from today where I have a GPX file created by LMP with only 19 "<time" stamps
but the raw NMEA log shows over 900 $GNGGA lines.

I'll try to attach both files.

[balloni55]

the result is in both files generally identical
- count of "track points" inside .gpx depend on tracking settings inside locus time/distance.
These recording end at 22:08
> question: at what time did you stop track recording inside locus? the recording of the nmea data did not end until 01:20 ?

but main question is, what was different between

20:53 (19:53 UTC) and 21:03
as well as
21:54 and 22:08

there was neither a track nor an nma recording in these time windows

[pat22043@gmail.com]

Short: I don't know.
The last time I see in the GPX file is 21:08:16.892Z. Since I'm in the US Eastern zone, this is 4:08 PM

The trip was from about 2:30 PM (19:30z) to 4:10PM  (21:10Z)
for a portion of the time, I was sitting in a dentist's chair, stopped. So the GPX file last record time is consistent. I was inside, but I would expect some GNSS reception.

Sorry, but this is consistent with the main issue, there are simply blocks where there are no recorded measurements.

[michaelbechtold]

$GNGGA,195308.000,4003.9223,N,07522.2462,W,1,25,0.56,141.9,M,-33.9,M,,*46
...
$GNGGA,200314.407,4003.9223,N,07522.2462,W,0,0,,141.9,M,-33.9,M,,*6C

That is from the Operating System / Android level, recorded in the NMEA file: no data for 10 minutes. That means that NO app will have a chance to record in between ...

If I were in your shoes I would go for forums around your device. As this is the behaviour of the OS of your device brand, there is y good chance not only you are suffering.

[pat22043@gmail.com]

I'll pass that on to the CAT engineer.

BTW, the lat/long here are identical in the two quoted lines

[pat22043@gmail.com]

The CAT engineer asked me to do a test running Glympse and Locus Map for a half hour while sitting at home. So I did. Glympse does not generate a log, so while it was running, there is nothing to see.

I had Locus Map generate both the GPX and NMEA files. Attached. (NMEA file is big, so I gzip'd it.)
I was also running Google's GnssLogger, that log is too big to attach. Let me know if you want to see it and I'll put it on Dropbox