Incorrect exercise duration data on Map and Speed tabs

[goryn]

Tracker via Pixel watch

For for  same exercise I have different duration on Map, Speed and all other tabs.

12 minutes vs 33 minutes (correct)

[Triletics]

Can you post a screenshot to illustrate the problem?

[goryn]

Same workout

[Triletics]

@goryn not sure what to make out of that. Was it a continuous ride or you stopped several times (I see your speed drops to 0 on several occasions)? Just a theory, but is it possible that 12:20 is your moving time (maybe you stopped for traffic lights a few times?) and the time you've been not moving has been deducted? Do you use auto-pause (I don't know whether Pixel Watch supports it)? Those charts usually show different durations but rarely with such a huge difference. Does this happen to your all rides? The middle (map) picture I can barely read (too small and blurry).

[goryn]

No, my moving time can't be less than 25 minutes for this route knowing my real avg speed.

Map is showing 12 minutes (sorry I thought small is the size of images previews)

Yep, autopause was enabled. I may also stop somewhere along the route for some minutes to do workout, setting pause manually.

So far was only spotted once.

.TCX file https://dropmeafile.com/#a1042c6485  https://dropfiles.org/joBgfDgf

[Triletics]

@goryn TCX file was useful. I dropped your file into the test account in Strava and here's what it shows:

Moving time is 11:51 and the actual cycling distance in the TCX is 2.56km. After correcting distance (so using only the GPS data) the distance increases and the moving time as well.

In the TCX file, I found 1230 entries of "<DistanceMeters>0.0</DistanceMeters>" which indicates the pause. Assuming every entry is 1 second (not always but as an estimation) that would give 20 minutes and 30 seconds of paused activity (which is about right).

So here's my theory. It's either your watch was very eager to force an auto-pause or you were pausing accidentally from time to time. Even when paused, Fitbit doesn't turn off GPS tracking and it still records data points in the file. Hence your route in the viewer seems to be correct after applying GPS correction either in Strava or in other tools.

I'm not quite sure why one chart shows elapsed time (elevation chart), and the other shows moving time (speed) but inconsistencies in this platform aren't new.

For the future, make sure you don't accidentally pause your watch (my bet is that this is what happens and it does happen to users of other Fitbit models, that does include me).

[goryn]

Accidental pauses are out of question since my screen is always off and set up to not react to screen touches, only bezel touch. I may've indeed stopped for a workout for about 15 minutes and of course traffic lights stops. Also Autopauses give a short vibration on watches, so I would've noticed that.

Feels like there is some bug.

[Triletics]

@goryn you may have paused for longer than you thought. The pause is quite clear in the data (you don't need to guess how long it was because it can be calculated which is exactly what Strava did showing the moving time). There is one more chart you can see that shows the duration of pauses and where they happened. Fitbit doesn't collect HR during pause so here's what the HR graph looks like for you for elapsed time (long horizontal lines are for no HR readings):

You can clearly see a very long pause almost at the beginning of your ride. How it happened, I can't tell because I don't know exactly. Something happened the watch paused around 00:01:43 and unpaused at 00:19:44.

The bug however lies in the presentation of the data. One chart shows your moving time, and the other shows your elapsed time. This inconsistency is a bug.

Edit: Little more investigation. It seems like, the pause happened around here:

Now a few questions:

- Did you pause the ride to cross the bridge?
- Did you walk your bike or...
- Did ride very slowly? (I'll explain that)

This is when your watch (approximately) unpaused (brings back some memories, I lived many years in London :D).

If you walked your bike or rode very slowly then there is a chance (can't confirm that but I know similar solutions) that Fitbit tracking has some threshold when it turns on auto-pause (so wouldn't count walking the bike, some people wouldn't want it to be included, mostly Strava segments fanatics who count every bit of average speed 😉 ). I pasted street view photos so it may bring back some memories and help you identify what could possibly happen that paused/unpaused your activity.