05-16-2018
11:27
- last edited on
09-08-2020
18:54
by
MatthewFitbit
05-16-2018
11:27
- last edited on
09-08-2020
18:54
by
MatthewFitbit
I know this was an issue couple of months ago, but now this issue seems to be re-surfaced (at least for me). While running I'm seeing that my pace is off (too high) even though I kept same pace. In order to be sure I just ran on an exactly 1km track for 6 laps and also recorded the run on Nike+ Run (both apps use GPS).
My fitbit app is v2.71 (2193273) on Android One Plus 5.
On this run Nike+ recorded correctly a distance of 6.07kms while Fitbit (Charge 2 connected to phone) 5.77kms!!! This is hugely annoying not just because my Charge2 is completely useless but all since my data is wrong, screwing up other metrics.
I am so disappointed with the current support and the incapability of getting something like this correct in over 6 months! (I'm being generous since found posts from 2 years ago reporting same issue).
Fix this ASAP!
05-05-2020 09:45
05-05-2020 09:45
Old post but gonna rage too.
It's Versa 2, but the problem seems to be an app-
05-22-2020 05:37 - edited 05-22-2020 05:38
05-22-2020 05:37 - edited 05-22-2020 05:38
On my Samsung A50 the simple solution for all of this seems to be to keep the screen of the smart phone ON during the run. This can be done by the app "screen timeout". I hope this will work for all of you.
05-22-2020 14:07
05-22-2020 14:07
I always keep my screen on when running however unfortunately it dosen't help. .
05-24-2020 02:42
05-24-2020 02:42
Nice one Fitbit.. Nice one!
Meanwhile Samsung health...
Will try out "screen on" method. I have a bad feeling about that.
05-24-2020 09:23 - edited 05-24-2020 09:25
05-24-2020 09:23 - edited 05-24-2020 09:25
@DFLK TBH it worked.. This time the run was off only by 0,1km, which is better than 2.5 km. After 1 km I locked the screen and it still worked.
I think the reason it worked this time is that I opened the Fitbit app in the phone. I don't usually do this and it runs on background. I'll do new run tomorrow or one day after again and I will try to open Fitbit app and then I'll lock the screen. Maybe the app need to run on foreground or smth and running in background just does not work.
05-24-2020 09:51
05-24-2020 09:51
05-24-2020 11:19
05-24-2020 11:19
Very interesting! Will give it a go.
09-17-2020 20:19
09-17-2020 20:19
This exact thing is happening to me too and it is so frustrating!! I am training for a half marathon and would like to know my accurate mileage and time but Fitbit has never tracked correctly. I was running on the treadmill most of the summer so I didn’t know for sure that it was wrong even when I ran outside until recently and now it is too late to return it.’
has Fitbit responded to you about fixing the issue?
06-05-2021 08:09
06-05-2021 08:09
I took part in an organised 10k today (remote - runners must send proof of distance and route). My FitBit Charge 4 had me at 10k, when my running companion’s TomTom had us (correctly) at just under 9k. We used her watch in the end and at exactly 10k, my Fitbit said 11.2k. Had I run this on my own, I would have stopped sooner than legitimate and thought I’d run a faster time. Absolutely crap for a sports device.
08-22-2021 13:23
08-22-2021 13:23
I see people complaining about 5-10% difference...
Today my Fitbit Versa Light measured only 1.3km out of 6.7km route. The path looks pretty much accurate though, showing detours and every tiny detail. How is this even possible?
08-24-2022 08:45
08-24-2022 08:45
I have the same issue. For a while my Fitbit would track my runs accurately but now it's saying my runs are longer than they actually are and it's messing with my pacing