FitBit Run Tracker incapable of simple arithmetic

[aoanla]

So, like a lot of people, I've been having issues with the fitbit run tracker.

A lot of the "advice" seems to be to set your GPS on High Accuracy - but I've done this, and, in any case, it shouldn't cause the actual issues I've seen.

These are twofold, and I suspect related:

1) The split for the last part of a run is usually ridiculously incorrect. (For example, for my last run, all of the other splits are probably roughly okay, at around 5 min /km, but the final "1.13" km is assigned a split of 77minutes!). 

2) The "overall average pace" calculation is also often wrong. On the summary panel at the top part for my run for my last run, it shows three bits of information: Total distance (6.24km), Average Pace (8minutes and 3 seconds) and total time (34:51minutes).

As everyone knows, Average Pace is the result of dividing Total Time by Total Distance: but (34.86minutes)/(6.24km) is 5.58minutes (or about 5 minutes and 34 seconds).

This is very very different to the average pace that the tracker reports.

I suspect that the two issues are interconnected - that the tracker calculates an "average pace" from the splits, and that whatever bug causes the massively inflated final split time also causes the average pace to be completely out of whack.

[This is made worse by the fact that you still can't properly edit tracked run data in the app - I'd like to keep my splits, and just fix the last one, but I can't even edit the tracking data!]

Edited to add: having just looked at my run data in the web interface, I think I understand the issue - I "pause" my run at the end, and then "stop" it at a later time. For some reason, the FitBit App doesn't properly cope with this - it considers the "total time" for the run, in some interfaces, to be the duration of the recorded run (that is the accumulated seconds when the tracker was not paused), and, in some other interfaces, the result of subtracting "time when stop was pressed" and "time when start was pressed".

Obviously, everything that does a calculation based on the absolute difference between the "start" and "stop" button press events is wrong - otherwise what would be the point of having a pause/resume button?

Can this be fixed, please, and retroactively?

[AlvaroFitbit]

@aoanla Welcome to our Community! This is really odd. Could you try logging out from the app, restart your phone and logging back in? You may also want to delete the app's cache by going to settings > apps > Fitbit > clear cache. After this retry using the feature. Make sure you are running the latest app version on your phone. By the way which phone do you have? Which OS version is it running? Did you notice this with a previous version of the app? Have you recently updated your phone's OS? Have you tried stopping the activity instead of just pausing it?

Let me know how it goes!