"position teleport" in track recording after pause/resume about osmand

[yuriiurshuliak]

The bug could not be reproduced. To reproduce the issue, I enabled live updates and began recording a track while rotating, zooming, and moving the map. After stopping the track recording for a few minutes, I resumed it. I also tested closing the app both while the track recording was active and paused. In all scenarios, my recorded track position remained accurate and did not teleport to any incorrect locations.

OsmAnd~ 4.8.0#2652m, released: 2024-07-02

video_2024-07-03_12-32-02.mp4

[sjvudp]

The bug could not be reproduced.

I was afraid you could not reproduce. Still, as it turned out, I had the same effect on different days using different recordings.
It could be a device or software issue, or it could be specific to the location.

Example:

<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<gpx version="1.1" creator="OsmAnd 4.7.17" xmlns="http://www.topografix.com/GPX/1/1" xmlns:osmand="https://osmand.net" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
  <metadata>
    <name>2024-06-02_13-31_Sun</name>
  </metadata>
  <trk>
    <trkseg>
<!-- ... -->
      <trkpt lat="35.0004317" lon="33.754555">
        <ele>37.1</ele>
        <time>2024-06-02T10:49:26Z</time>
        <hdop>2.1</hdop>
        <extensions>
          <osmand:speed>31.8</osmand:speed>
        </extensions>
      </trkpt>
      <trkpt lat="34.9937133" lon="33.7581617">
        <ele>34.4</ele>
        <time>2024-06-02T10:50:24Z</time>
        <hdop>2.2</hdop>
        <extensions />
      </trkpt>
      <trkpt lat="34.9653817" lon="33.9896133">
        <ele>8237.2</ele>
        <time>2024-06-02T10:51:22Z</time>
        <hdop>5.8</hdop>
        <extensions>
          <osmand:heading>286</osmand:heading>
          <osmand:speed>32</osmand:speed>
        </extensions>
      </trkpt>
      <trkpt lat="34.9814367" lon="33.794435">
        <ele>24.4</ele>
        <time>2024-06-02T10:51:53Z</time>
        <hdop>2.4</hdop>
        <extensions>
          <osmand:heading>325</osmand:heading>
          <osmand:speed>31.4</osmand:speed>
        </extensions>
      </trkpt>
      <trkpt lat="34.97957" lon="33.8048833">
        <ele>27.2</ele>
        <time>2024-06-02T10:52:24Z</time>
        <hdop>2.8</hdop>
        <extensions>
          <osmand:speed>32</osmand:speed>
        </extensions>
      </trkpt>
      <trkpt lat="34.9754233" lon="33.8144917">
        <ele>37.2</ele>
        <time>2024-06-02T10:52:55Z</time>
        <hdop>2.9</hdop>
        <extensions>
          <osmand:speed>33.9</osmand:speed>
        </extensions>
      </trkpt>
<!-- ... -->
    </trkseg>
  </trk>
</gpx>

I wrote a GPX parser that makes plain column-aligned text files from GPS, so you can see the issue (all math errors are mine!):

#date & time        lat. & long.           elev. hdg.  ang delta-lat. & delta-l dist. delta speed hdop  delta-
#                                                      le  ong.                       -elev             time  
#                                                                                     .                       
2024-06-02T10:49:26 35°2"N 33°45'16"E         37       118 0°17"S 0°31"E         1089   -28 114.5   2.1     31
2024-06-02T10:50:24 34°59'37"N 33°45'29"E     34       151 0°24"S 0°13"E          847    -2  52.6   2.2     58
2024-06-02T10:51:22 34°57'55"N 33°59'23"E   8237 286.0  96 0°1'42"S 0°13'53"E   25928  8202 115.2   5.8     58
2024-06-02T10:51:53 34°58'53"N 33°47'40"E     24 325.0 274 0°58"N 0°11'43"W     21776 -8212 113.0   2.4     31
2024-06-02T10:52:24 34°58'46"N 33°48'18"E     27       100 0°7"S 0°38"E          1180     2 115.2   2.8     31
2024-06-02T10:52:55 34°58'32"N 33°48'52"E     37       113 0°15"S 0°35"E         1163    10 122.0   2.9     31

See the "dist(ance)" column.