01-22-2022 17:39
01-22-2022 17:39
Tonight I went on a walk and started the recording on my Sense. When I got back and synced it with the app, I noticed that on the exercise summary screen, it only shows the first and last ~1.25km of my walk in distance and on the map. The total walk was actually 7.6km and around 1.5 hours.
When I go into the specific recording details, it still says I only walked 2.59km for 27 minutes, but the map now shows the full "track" of my walk (which is the 7.6km).
Any idea why it is not showing the proper distance and time even though when I go into the details it shows the full map? It doesn't look like GPS disconnected at all during the walk as when I pull up the full track map, there is no straight line "connectors" like if I had lost GPS signal.
02-09-2022 11:25
02-09-2022 11:25
Sounds like the real question is, why did my sense loose a GPS lock?
And why did my sense not use my stride durring the failure gps period.
Is the step count look correct @SquatLikeSlav
02-09-2022 16:22 - edited 02-09-2022 16:26
02-09-2022 16:22 - edited 02-09-2022 16:26
Regarding the difference between the 1.25 km shown in the summary screen and the 2.59 km in the recording details it might be a problem of conversion from km to miles (where 2.59 km = 1.25 miles) but shown as km. It's a silly bug that many people reported but that it appears Fitbit developers are not targetting (likely because very busy or because they didn't receive the bug report)
Regarding the distance very different compared to the map it would be interesting to see a screenshot of the workout you made and, even better, a TCX file of the exported session to understand where the culprit is. Based on your description it appears the GPS worked correctly but the distance (that all Fitbit calculates as steps multiplied by stride regardless the presence of GPS) seems grossly understimate, likely because of a wrong stride.