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!
12-04-2018 15:37
12-04-2018 15:37
Yeah, I guess they just don't care. I've taken the same walk twice in a row now, it shows 1.27 miles (for over 5800 steps - seriously, you'd think even a computer could see that's wrong unless you're taking baby steps!). I checked it with my car and bike odometers and they both give me 2.3 miles. so it's ridiculous that it's recording barely half the distance. Pitiful. I think I'll try a different fitness watch next time.
01-29-2019 06:39
01-29-2019 06:39
I'm also having similar problems. Got a new fit bit 2 version 2.85 for Christmas. Disappointed to find it consistently under records distance & the pace shown is incorrect too. I run 3.1 miles regularly on the sane circuit. Strava shows this as 3.1 k pace 10.33, fitbit gives 2.88 miles at pace of 13.38.
Can anyone help?
01-29-2019 07:16
01-29-2019 07:16
01-29-2019 08:35
01-29-2019 08:35
01-29-2019 08:49
01-29-2019 08:49
@Ruth61 as mentioned above and in other places accurately set your Stride. For starters increase your stride setting by 1.08.
01-29-2019 09:00
01-29-2019 09:00
I’ve given up on Fitbit as a brand. They haven’t and unlikely to fix the problem which has been raised for over a year.
Im disappointed that Fitbit is still selling this model knowing there is a major issue. Clearly it shows Fitbit does not care about their customers at all
01-29-2019 09:40
01-29-2019 09:40
Fortunately @NickMac Fitbit users have figured out what was going on and have provided both the reason for the inaccuracy and the fix. These boards are scattered with users documenting on how to get an accurate distance while out on a walk or run.
01-29-2019 09:42
01-29-2019 09:42
01-29-2019 09:51
01-29-2019 09:51
If I have the time I’d go through the endless information on how to fix something that should be working in the first place. Alternatively Fitbit should just fix the **ahem** thing
01-29-2019 10:03
01-29-2019 10:03
There is a valid reason as to why Fitbit uses the logic that they do, I summed up the fix above with " set the stride setting accurately".
01-29-2019 10:14
01-29-2019 10:14
01-30-2019 05:46
01-30-2019 05:46
Tried your suggestion Rich_Laue. My distance measured almost exactly the same as Strava this morning, so that's great. Thanks for the tip.
Pace however was stll incorrect...knocked 2mins off my normal pace - if only!!
Thanks for your help.
01-30-2019 14:39
01-30-2019 14:39
This thread has prompted me to contact Fitbit on facebook and this is their last response:
Not the experience we want you to have. We’re aware of the GPS issue, but may not be able to provide a fix in the near future. We'll continue to monitor the situation and keep our team informed of its impact. We're sorry for the trouble, and understand this isn't the resolution you're hoping for.
There you have it. They are aware it is an issue but it wont be fixed.
Good luck everyone
01-30-2019 14:54
01-30-2019 14:54
01-30-2019 15:52
01-30-2019 15:52
@NickMac I think you missed the phrase, " n the near future', Fitbit never said that it won't be fixed.
01-30-2019 15:55
01-30-2019 15:55
Considering this issue has been ongoing for a year, and Charge 3 is already out, i wont be holding my breath.
01-30-2019 17:44
01-30-2019 17:44
And regarding adjusting stride length, I have experimented with it at length trying to find the “sweet spot” and every time I think I have it, the next time I go out and do the exact same route (which I know the distance of) it will be a different story completely. This leads me to believe that the device simply does not work properly.
Furthermore, even if you are lucky enough to find your stride length “sweet spot”, you have to keep in mind that this whole approach breaks down as soon as you adjust your pace. In theory, if you do a faster pace you are taking slightly longer steps, so the result of this will be very counterintuitive. The Fitbit will still do the calculation based on your “normal” stride length, and so the end result will be that it will show your distance, and also your pace, as being LOWER when you run faster. This is of course because you took slightly fewer steps to run, what is in reality, the same distance.
01-30-2019 17:55
01-30-2019 17:55
Maybe I'm old fashioned but a sports watch shouldn't be this complicated.
You shouldn't have to manually find your sweet spot or adjust your stride.
It should just work.
02-02-2019 06:08
02-02-2019 06:08
Hey everybody! I hope you are doin' great!
If you are experiencing GPS issues, like inaccurate distance and pace, I would suggest you the following:
- Review this help article: Why isn't my GPS working on my Fitbit device?
- Make sure that you have the latest version of the Fitbit app
- If you are using an Android device, please review this help article as well
Let me know how it goes!
02-17-2019 17:47
02-17-2019 17:47
Considering this has been a known issue for a few years I can't believe we're still offering this as an excuse for a manufacturer not taking the responsibility for fixing their product offering.