Distance measuring

[francesbyrnecar]

Fitbit charge 2 is not measuring distance correctly. 

[SteveH · Accepted solution]

Your Charge 2 measures distance by multiplying your step count by your stride length so it's either a problem with it counting steps or your stride is set incorrectly. 

Does your step count look reasonable? If so it's a problem with your stride. Fitbit calculates default stride lengths for walking and running. If you haven't overwritten these the defaults are based on your gender and height so it's worth checking your profile settings at https://www.fitbit.com/settings/profile If you have set the length yourself then you need to revisit this and this help file may be useful: Help article: How do I measure and adjust my stride length?

If the problem is with it counting steps then how far out is it? You could do a test where you count out 100 steps and see how many fitbit counts.

[SunsetRunner]

Try going for a bike ride with Connected GPS. It calculates the distance as about half the true distance. Fitbit have known about this for 2 years but have no intention of fixing it. The Charge 2 is useless in this respect. 

[SunsetRunner]

This is not the best answer if you are cycling via Connected GPS. The application under- reports the distance by as much as 50%. Despite displaying an accurate map,  the distance is way out. How exactly does Fitbit calculate the cycled distance?  Stride/steps are obviously not a valid measurement in this case. Nobody seems to be able to tell me how it is calculated or why it is so wrong. Which is why I'll never buy another Fitbit. Admins just promise that problems are known and being investigated as a priority but they never deliver. 

[hvdutra]

Running is the same.

Perfect map track on the Fitbit App and wrong distance.

Last run, 4.89 on the Charge2 and 6k registred on another android app. Same GPS signal.

[francesbyrnecar]

Still haven't the distance sorted. I have tried all the trouble shooting hints.

Sent from Yahoo Mail on Android

[MelleKing]

After two years, running distance is still not correct via GPS.

Tried all advices posted earlier.

Even when maps show correct run the distance is way off.

Fitbit is still unable to deliver or clarify any reasons for not being able to properly calculate GPS distances.

Other apps using the same GPS phone signal work perfectly fine.

I am giving up and look for another device

[dnmwales]

I've been getting the exact same problem for 6 months - Fitbit support have confirmed to me in several emails that there is an issue and that they are aware of other people having the same issue but nothing is being done about it!!!  Here are some of the responses I've had from Fitbit support.  Other responses are just the generic 'how device calculates steps', 'how to change stride length', 'how gps works etc.'  In fact I changed my stride manually to a ridiculous 70 inches and it was STILL 0.4 miles out!!

“Andrew (Fitbit Supervisor): Upon review of your case, we can see that this an ongoing concern that we working to get rectified.”

“Arianne: Yes, we can confirm that there have been many reports regarding the issue.”

“King 😧 I'd like to share with you that our engineers are still working on a concrete resolution and have yet to set a time frame as to when this will be fully resolved. We want to make sure that when a resolution is rolled out, this addresses the issue totally and you would not have any other problems.”

“Chester : We do not mean to interrupt or any means break our products." 

“Christine: we have received a small number of cases similar as yours with Charge 2 devices. We'd like to let you know that you that we can't provide a definite time frame when this will be resolved. We suggest to keep an eye for updates as Fitbit releases feature enhancements and bug fixes for your device through firmware and app updates.  Aside from that, we'd like to share with you that getting a replacement will not guarantee that the issue will be resolved since this is a software issue.”

[hvdutra]

Today I had a good surprise. It looks like my charge 2 finally started to track the correct distance again.

The only different thing that happened last weekend was that the charge 2 was dead for 2 days. No battery at all. 

After 2 days off, I've recharged and today was my first run.

The stride length was set by be sometime ago. And distance perfect again.

Let's see how it goes. I'll keep everybody posted.

Regards.

[SunsetRunner]

My Fitbit now plays nicely with my Samsung A70... accurate distances and reliable notifications. Happy with that! 

[Ashweb901]

The sounds you hear is me BUYING A GARMIN. FitBit distance tracking sucks.

[Ashweb901]

@MelleKing what did you buy? I'm fed up.

[SunsetRunner]

I retract my original statement about it working nicely with my A70... that must have been a flash in the pan. It's worse than ever now, just ridden 12 miles and Fitbit sort of shows the route with a distance of 1.5 miles. Bearing in mind the overlords that are Google now own Fitbit, I thought they'd be after as much accurate data as possible! Let's see them track my Fitbit from a drawer because that's where it's heading. 

[Ashweb901]

Yep yep - I've abandoned mine for a Garmin Vivoactive3. I know no wearable
is perfect, but 30%+ difference is too much, especially when my fitbit and
app can draw an exact map, that when driven by car is significantly longer.
In my case, I'm getting points toward better insurance premiums, so over
estimating would be preferred to severely under estimating!