Moving time/stopped time bug

redshift

21 September 2024 12:08

The displayed moving and stopped time (and as a result the pace numbers) are grossly in error on iPad and iPhone for all recorded tracks. This bug started after the last app update on iOS. For example, a recent hike shows a moving time of 56:51 and a stopped time of 3:48:45! The numbers shown on the gaiagps website are correctly shown as 3:29 moving, 38:7 stopped.

2

• 

  jrd63

  22 September 2024 05:18

  Same here. Messed up on iPhone. Have not checked website.

  0
• 

  jamieorc

  24 September 2024 17:13

  I started noticing weird data a couple weeks ago. I updated to the latest version (2024.8) yesterday, still crazy. I've sent the info to Gaia support.

  Examples

  While recording:

  • during a sub-2 hour hike, showing hours of stopped time in Trip
  • Showing crazy speeds of tens and even hundreds of miles per hour in Trip
  • Showing negative speed on Map
  • Then showing moving speed of 0.0 for the rest of the hike

  Then after finishing the track and saving, everything looks good... until

  Then next morning I look and the Trip info has gone from 2.2 mph moving speed to 4.5. Stopped time has gone from about 10 minutes to 40 minutes. Then I look again a few minutes later and moving speed is now showing 6.1 mph and stopped time over 80 minutes, while moving time has gone down to an absurd 40 minutes for the 4 mile hike.

  A crazy bug! I sent this information to Gaia with a bunch of screen shots.

  0
• 

  Tek

  04 November 2024 21:36

  Same issue here as of late.  A track that I recorded and cropped. The red line is speed and you can see that it never even gets close to 0 yet the stats show 4m19s of stopped time.

  

  0

Please sign in to leave a comment.