help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Charge 2 GPS Inaccurate distance

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎03-28-2018 13:05 - edited ‎05-02-2018 09:07

‎03-28-2018 13:05 - edited ‎05-02-2018 09:07

This has been discussed here  but the thread has been closed I am still having issues.

 

Compared to Strava and some other apps that I have been checking Fitbit against, Fitbit is consistently showing that I have traveled a shorter distance than what I actually have.  It is out by about 250 meters for 6km.  This is a big margin of error.

 

I believe that I have found the cause of the issue.  Fitbit app does not log from the centre of your location but rather to the outside of the GPS accuracy circle.  This means that if you have run that has a lot of twists and turns the overall run will show as a shorter distance.

 

From the following images you can see that the trace line (recorded route) never actually touches where I am.  So in this example when I turn this 90 corner, Fitbit records it as a smooth curve.

 

 

Now the turn

 

trace has never actually caught up with my location.

 

Most of the turn is smoothed out

 

Add all of these up throughout a run an it leads to a massive margin of error.

All of the other apps that I use do not have this issue.  Its as if Fitbit does not use a high enough sample rate to record position.

 

 

Moderator Edit: Updated Subject For Clarity.

Best Answer
20 REPLIES 20

‎10-24-2019 06:14

In response to NBrouss

‎10-24-2019 06:14

Same issue.  Getting large differences in run stats for same route/time.  The app shows a map that appears accurate, but the distance is wrong and recorded differently in the app...It doe not seem like it should be necessary to switch off WIFI as others have suggested and Bluetooth is necessary for Charge2 to connect to phone.

 

If I just use the app on the phone and not the band to track runs, it works as expected.  It is an issue with the band in my case and recently started - past couple of months.  

Best Answer
0 Votes