GPS distance totally wrong on Charge 3

[BertilDator]

Was doing cross country skiing, and set activity to "run" (as there is very limited activity list). Had phone connected, and got perfect GPS route on Fitbit activity. However, all the splits are way off. Total distance in Fitbit shows 4.8km while real distance was 7.5 km (I know the route, and even double checked via ontegomap.com).

How can Fitbit calculate distance so wrongly even though the GPS route is perfect on the activity? I repeat, the tracked route is 100% correct on the Fitbit activity in question, so there is no disconnections, or trees, or anything between the phone and GPS satellite, nor between phone and Charge 3.

Is Fitbit using GPS route for distance calculation when assisted GPS is enabled during "Run" activity, or does it STILL use stride length?

Should I use "Biking" activity for XC skiing to get accurate distance based on the GPS route?

[f1oyd3]

Can't agree more with the recent posts made here.  Fitbit continues to ignore the issue, I will be looking to ditch the charge 3 entirely.

[Kaflemd]

I gave up waiting for this to be "fixed" by Fitbit. I now own a Garmin Vivoactive 3 and it is SO much better. I would highly recommend it.

[FL_Runner]

I guess the moderator gave up since Fitbit is not going to fix the issue and keeps recommending the same things.  My walk this morning was another test.  Garmin Forerunner on one wrist, phone in pocket running the Fitbit App map and the Charge 3 on the other wrist.  Charge 3 was fully connected to phone, clear sky and route.  Walked 4.45 miles on Garmin, 4.45 miles on phone using Fitbit app and last but certainly least the tracker showed 4.2 miles.  If it is connected to the phone how is it not showing on the tracker.  And then the tracker took precedence over the app on the dashboard, map is correct but the lesser mileage showed.  Not big for me on the walk but I like my runs correct.  Just returned the Versa 2 since it was way off and after a few more experiments I may be sending back the Charge 3 as defective.

[f1oyd3]

Yup started my return process yesterday.  Will be buying a Garmin.  I would have likely stayed a fitbit customer if they had had even the slightest indication that they were aware of the issue and were offering a real soultion/timeline to fix.  Thanks for all the hard work everyone, happy trails.

[Nneicho]

There is definitely an issue with the distance.. after months of emails and tests and a dispute with the ceo team i was given a refund after sending back the whole device. I now own a garmin vivoactive, and it tracks perfectly. Its a great shame as i loved fitbit. If they had fixed the issue i wouldn't have had an issue and carried on with the charge3.

Fitbit will now be loosing so many customers to garmin and other brands. And its clear they dont seem to be bothered about it.

[Weather411]

The newest kicker for me - now the Bluetooth does not work. So my Charge 3 is essentially useless. GPS issue that I first wrote in this thread is not being taken seriously (or at all) by FitBit and I think that speaks for the direction the company (now owned by Google) is taking. My next task is now to wrestle with customer service to get my money back (watch was purchased in Sep-2019). From all the recent reviews here of people switching, maybe we should steer this conversation on any return-advice experience lessons learned.

[BrandonW92]

Mine was purchased October 2019. I have had three replacements which have all had the same tracking issue. I am now getting a full refund from Fitbit at long last. Will be purchasing a Garmin.

It's a shame as I really liked my Fitbit but when it does work as intended it's pretty useless!

[AdamH0]

Today I forgot my phone for the 5km parkrun. I still manually recorded the activity on the Charge 3, but it was obviously only able to use step count to estimate the distance.

This run was the most accurate yet! Using step count alone fitbit tells me 5.03km!

[FL_Runner]

I agree.  I did the same yesterday and tweaked the stride.  I don't think they have the program right for connecting gps.  So it is an expensive pedometer. 

[Hmmmmmmm1]

I'm having same problem with cycling

[tom43614]

Fellow Bicyclist. The answer may be to toss your Charge 3 and Go Garmin, This has been a problem for many months. I have tried all of the Fitbit fixes, or should I say non-fixes.

[DaleCooper]

Just got a Charge 3 and disappointed to discover this issue. The distance of my runs is consistently overstated by around 5% when connected to GPS, even while other apps running at the same time measure it accurately. 

[hazelnuts]

I have the same issue. Ran 10k today with my Charge 3 and also started Runkeeper on the same phone my Charge 3 is connected to. 

Guess what happened? Runkeeper said 10k and Fitbit app said 7.93k.

So apparently the GPS works. And the route is correctly printed in the Fitbit map and also the total time is correct.

I guess the problem is not in the Charge 3 or the GPS. The problem is the distance calculation at the Fitbit servers.

[MayaPapaya]

Same! I'm "glad" to hear others have the same issue, at the same time the inaccuracy is really getting to me. I want to be able to track my time and pace properly. I might just ditch the fitbit for a better GPS-tracking device, since no solution has been offered from FitBit. 

[ram555]

I'm having this issue and its shockingly poor service from fitbit. 

I've only had my charge 3 a couple of weeks and using GPS from my Samsung s20. 

I've done 2 runs. The first was OK and logged 3.2 miles which is correct. 

Then today I did the same route. GPS connected when I started. But whilst going round I noticed my pace was showing about 1-2 min slower than i normally run. When I completed the 3.20 mile run the fitbit said I had only done 2.70 miles. Clearly very wrong. 

What on earth is going on here fitbit. This is shocking. 

Has anyone logged specific calls with fitbit. This product isn't fit for purpose at the moment. 

[AdamH0]

I have several live chats, and email threads with support over several months.

They always act like it's an unheard of problem, take you slowly through basic scripted checks.

eg change your stride length, ensure GPS is connected before you start

Eventually you might get upgraded to the 'higher level support team'. You won't notice the difference. 

None of the conversations were around them trying to debug the issue, they didn't seek information or detail from me. (eg they never asked about my phone or how i start recording)

When you present recordings from Strava recorded on same phone at same time as fitbit recording, you'll get some mumblings about 'different algorithms for calculating distance'.

Eventually after I forced them to accept some gpx files I'd recorded, they agreed that it was a known problem, and there was no ETA for fix, and to keep checking the release notes.

I entered the support process confident that I'd be able to help them debug this issue, and left disappointed. The aim of their support team is to deflect.

I'd encourage you to have a go getting support, but to be prepared for disappointment.

BTW everyone with this problem seems to be on Android.

[Leeeeeem]

Has anyone managed to fix this? 

My device consistently gives a >20% error on every run. Have done all the "fixes" they suggest but nothing helps. 

Just going to ask for a refund. Such a joke

[BryanCork]

Totally putting me off the Charge 4. A good in built GPS would be amazing
in a fitbit charge. But whats the point when its just going to be 10-40%
inaccurate.

[ram555]

I'm early in the process with support.  They have just got me to do a hard reboot... I tried to say this is wasting time but they still want to go through the motions..

I suspect a painful few weeks with no result.

I do however think this must be an android app problem if no one has had this on iPhone?!?

[DaleCooper]

I have the problem on iPhone.