Errors in recorded tracks

[weitwanderer]

I have been working with oruxmaps since many years and I am really very happy with it, 100s of tracks are successfully recorded.

I stay with version 5.5.22 on Android 4.4.2 on Galaxy Note 2, nothing has changed in the last 4 years.



But since  two weeks some recorded tracks are corrupted:

- the recorded track (as displayed in oruxmaps and when exported as GPX) shows temporary "jumps" forward to some future (!) point in the track.

- the exported GPX shows crazy date/time stamps: in yesterdays track most points show 09/21/1999 as date



The only symptom I remember during walking and recording:

Maybe recording was interrupted as the red arrow was no more shown. I had to save the recording and start again (procede with the same track).



Here is yesterdays track:



https://www.dropbox.com/s/9w4esbv13nxv4uo/2019-05-07%20Launsdorf%20-%20Treibach__20190507_0833.gpx?dl=0">https://www.dropbox.com/s/9w4esbv13nxv4 ... 3.gpx?dl=0">https://www.dropbox.com/s/9w4esbv13nxv4uo/2019-05-07%20Launsdorf%20-%20Treibach__20190507_0833.gpx?dl=0



and the corresponding screenshot from ORUXMAPS:



https://www.dropbox.com/s/fx7bptdv15lp1hr/Track-Image_Launsdorf.png?dl=0">https://www.dropbox.com/s/fx7bptdv15lp1 ... f.png?dl=0">https://www.dropbox.com/s/fx7bptdv15lp1hr/Track-Image_Launsdorf.png?dl=0



Do you have any ideas what is running wrong?



Thanks and regards



Ferdinand (I had to re-register as the old registration didn't work any more)

[abel1]

I have noticed the same problem with wrong date (not time!) e.g. 2000-11-19 instead of 2020-07-05 in gpx trackpoints (not waypoints, however!) and <desc> Startzeit and Zielzeit (e.g. 03.10.2000 instead of 19.05.2020) on my Samsung Galaxy Note 3 with Android 5.0.
I have been using Oruxmaps 4.7.22 and 8.0.1 GP.
The error does not show on my Honor 8x with Android 10.
In the past this error never occured, now it seems to occur regularly.
System time is and was always correct.
The error occurs because of the "GPS Week Number Rollover" problem and has apparently been corrected by Orux in the beta release (7.5.9beta3) and also in the new GP VERSION 8.0.1 (Sensors>GPS).
I have not yet checked this, however...
See post "Error en la fecha de inicio del track".