Connected GPS on my Charge 3 is not tracking distance accurately

[petteyc84]

Hi everyone,

I used to have a Charge 2 until about 6 months ago.  I never had any issues with accurate distance measurements with it when I did runs/walks with GPS synced up to my phone.  Worked perfectly and always measured the same distance that I could map out on Google Maps.

With my Charge 3, I have been noticing wide disparity in the GPS distance tracking.  Sometimes it works properly, but other times it cuts off about 20% of the run distance, whereas other times, such as today, it adds distance on.

For example, last week I did a run that, by google maps measurements, should have been 6.4 miles.  Instead, my Charge 3 with GPS tracked 4.98 miles.

Today, I did a run that should have been 7.3 miles; but the Charge 3 with GPS tracked 7.9 miles.

Very frustrating when trying to pace my runs accurately and use the tools that are available to me on the device, and it's not accurate.

Anyone else having these issues, or found a solution that works for them?

Thanks.

-Chris

Moderator edit: updated subject for clarity

[MarreFitbit]

Hello @petteyc84, welcome to the Community Forums. We apologize for the late response, due to recent events affecting our operations, we're taking longer to respond.

I'm sorry to hear that your Charge 3 hasn't been tracking your distance accurately. Thanks for the details provided, I'm here to help you.

Fitbit devices calculate distance by multiplying your walking steps by your walking stride length and multiplying your running steps by your running stride length. We estimate your stride lengths using your height and sex. Track one or more runs using on-board or connected GPS, we evaluate that data to automatically update your running stride length. For best results, run at a comfortable pace for at least 10 minutes.

If you prefer to measure your walking and running stride lengths yourself and enter them manually, see Can I change my stride length in my Fitbit account?

Note that when you're tracking an activity with GPS, Fitbit calculates your distance using GPS data rather than steps. If you begin moving before you get a GPS signal, the tracker will calculate distance using steps and stride length as described above until a GPS signal is found.

Keep in mind that your device uses your step count to calculate distance until it finds a GPS signal. In this scenario, your total distance calculated for the workout may be slightly less accurate than if GPS data were available for the entire duration. For more information, see How accurate is GPS?. After reviewing this factors, please go for another activity and see if the distance improves. 

On the other hand, I was wondering if the mobile device you're syncing with is included in our list of supported devices? You can see the list at: Which phones and tablets can I use with my Fitbit watch or tracker?

Fitbit products are compatible with most devices that have the following operating systems: Apple iOS 12.2 and higher, Android OS 7.0 and higher, or Windows 10 v1607 or higher. Please keep in mind that when a device is not supported we cannot guarantee its functionality with the Fitbit app. It might work at a certain time and then it can stop working out of nowhere after an update. This is because the app is not optimized to that device and any change could impact the performance. 

Let me know how it goes.

[petteyc84]

Thanks for the info.  As I stated in my original post, I am using connected GPS with all of my runs, so it is not an issue with stride length.  The device should be tracking distance according to the GPS on my phone, as you noted below.  It even shows on the map the route that I ran, and will record different distances each time.  It seems, for about the past week, that the distance tracking has normalized.  But this has happened before, only to go back to inaccurate tracking a week or so later.  I will keep you posted.

[Rhino07]

I have this issue. Fitbit just fob you off with answers like the above. 

This should be an easy fix for Fitbit but for some reason the issue still exists. The only solution I can see is to buy a new fitness tracker other than a Fitbit 

[MarreFitbit]

Hello @petteyc84, thanks for getting back and for the update. If you continue having this issue with the distance, please keep in touch and also let me know the make/brand of your mobile phone so I can go from there. 

Hope to hear good news. Have a nice day! 

[declan_scully]

I have had the same issue a few times but caught it perfectly this morning.I have the Samsung S8 running the latest fitbit app.

Fitbit mapCorrect Distance

[petteyc84]

It's started happening again.  Now swinging the other direction.  I did a 9 mile run on Saturday that FitBit with GPS tracked as 9.62.  Today did a 3.2 mile run that was tracked as 3.7 miles.

Again, I am always using connected GPS with my phone, and I can see the runs mapped out on my app, but the distances are simply just completely inaccurate.  Seems odd that, even though the device is tracking using google maps, that it can't get the distance right.

I was using a Samsung Galaxy s8 up until about a month ago, and now using an s10e.  Same issue with both devices; sometimes it tracks correctly, other times it adds distance, other times it cuts distance off.

[petteyc84]

It's just all over the place now.  Occasionally it works correctly, but most of the time it's completely wrong.  For example, yesterday I did a 10 mile run that was measured at 12.9 miles; the map view of the run is completely wrong in where the mile markers are at on the streets.  I just don't understand if the app is using the map and GPS to log distance, how it could be so inaccurate.

The only consistent thing I can point to, is that for my old Charge 2, I never had a single issue with this feature. Distance was always correct, no matter what device I was connected to.  But with the Charge 3, it's almost never right, regardless of the device.  So frustrating, as this is a feature I would like to be able to use and rely on for pacing, speed, etc.