dennisguse
commented
3 weeks ago Duplicate of #1898.
Please upgrade to v4.12.3.
Please note that the upgrade will not fix those tracks - it just prevents the occurrence of the problem. If you want to fix those tracks, you need to export them and remove the 0/0 coordinates.
While recording tracks on an auto trip, five of the tracks recorded report huge final distances (22,586.56 mi; 11324.52 mi, 22687.96 mi; 11463.22 mi; and 12109.85 mi). I know that the 11463.22 record was correct at 48.04 mi; the actual final distance was about 56 miles.
This seems to be a random issue; seven other tracks recorded on the same trip had no problems. I am not able to reproduce the issue with any particular actions. All tracks were recorded by tapping the start button, then holding the start/stop button to stop. The phone was always in the same location in the vehicle during all tracks recording, or in my pocket while walking. In one case, I set three markers; in the other three cases, no markers were set; several other records with markers had no problem, so no consistency there.
Attached screenshots are from the first two instances, showing the Stats, [two] Intervals, By time, and By distance pages. Two Intervals pages are included - the "Early" one is where any discrepancy from reality is first noted and the "Late" one has the largest recorded distance. For the 11324 instance, I realised I could get more resolution in the Intervals distance so took another pair of Early and Late Intervals at 528ft intervals, which shows more precisely where the issue begins.
I could make the GPS coordinates available if that might help; I'm reluctant to export tracks because of potential storage issues.
Samsung Galaxy S22 (SM-S901U) H/W Rev 1.0 Android version 14; Kernel version 5.10.198-android12-9-28575149-abS901USQS5EXE2 #1 Fri May 10 18:49:30 UTC 2024 Opentracks v4.12.2; version code 5749