GPS distance on Charge 3 not accurate

[StrickersJ]

Hi Fitbit

I am new to Fitbit but have tracked my cycle commute to work for 3 days now, following exactly the same route each day but the distance recorded has been significantly different each day - 3.3, 3.92 and 2.85 miles. I have started the tracking form the Charge 3 and set off stopping it again on the device when I reach my location.

That is more than a mile difference on a route that is actually 3.65 miles.

I used to use Samsung health and that app used to track it accurately within .1 or .2 of a mile.

I am using the same Samsung Galaxy S10 as I did when I tracked with Samsung Health so something is terribly wrong with either the Charge 3 or the App.

I have seen a number of other posts complaining that the GPS is not accurate dating back at least a year now.

This is a premium product and as such should get the basics right at the very least.

Please fix this ASAP - currently not doing what you advertise it does!!!   

Moderator edit: updated subject for clarity

[MarreFitbit]

Hi there @StrickersJ, welcome to the Community Forums. I am sorry to hear that you are going through this situation. I appreciate your feedback for the connected GPS on your Charge 3. 

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 How do I measure and adjust my stride length?

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.

Note 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 run and see if the distance improves. 

Keep me posted, I'll be around.

[StrickersJ]

Hi

The answer does not reflect the problem which is the fact the run, cycle or walk functions started on the Charge 3 are completely inaccurate. I wait for it to connect to phone but the distance is always wrong when compared to other apps using the same phone to track distance. I did a walk yesterday and it registered half the distance that Google maps showed for the same route, half! This is fundamental to what the fit bit is bought for surely? 

This needs an urgent update.

[ikinga]

I had the charge 1, charge 2 and now the charge 3 and I never really cared of the accuracy until I have started running. Getting accurate pace is fundamental for a runner. I start my charge 3 and my Strava at the same instant, both track from the same phone and GPS signal, yet, Fitbit is always off. Well, not totally off, but it ALWAYS shows less distance, be it 100m on a 3km run or up to 500m on a 5k run. I often run on the same exact route, with the same starting and ending point. The huge issue is the lack of consistency as each time the distance is different (so are the pace). Strava is always the same with a 0,1 accuracy. I am very disspointed I cannot get my heart rate to Strava to analyse it, as I cannot use the GPS track measured with Fitbit because it is off. It only servers to measure heart rate and steps, but not activity... why on earth put a GPS on a device if it does not work?

[DJRumble]

I have the same problem. I went for a run the other day with the mobile connected via bluetooth and the GPS/data on. The fit bit recorded a distance of 3.3km but google tracked it separately as 4km. Please can fitbit please advise a solution to this. Please don't just send your stock response as that does not answer the question.  

[t.parker]

There is no solution. There is already a very long thread about this issue:

https://community.fitbit.com/t5/Charge-3/GPS-distance-totally-wrong-on-Charge-3/td-p/3259017

[Emkn45]

I'm having the same issues as the others who have replied. In a 4 mile run, it's off by as much as 0.85 miles each time. That's huge! My husband and I will run together and his apple watch comes up with a significantly different result for distance than my FitBit Charge 3. When we map it out using Google Maps/Map My Run, the Apple Watch is correct and the FitBit is way off. 

[richardsonp2]

Just adding in that I have had so much issue with the GPS with this product also. Not only does the distance not acurately track with the GPS but the run result will show to be less miles than the mileage points. It will show 10 mileage points for a total run of 7 miles for example.

Seems to be GPS/distance measuring issues galore on this forum to be honest.