Versa inaccurate GPS tracking

[Dorispen]

I have used my versa for 2 years now and in the last three months, the gps tracking is not showing an accurate distance. I have used a different fitbit and it's doing the same. I have checked the distance with google maps and it's definitely off and I use the same track every day. How do I reslove this please as it's very annoying!

Moderator edit: Labels and format

[mortie5k]

Same.  I've had mine for around a year and it always showed pretty accurate pace and distance information.  For the last few weeks, it's been off by 25% (overestimating).

I don't know what to tell you.  I've spent hours on chat with support trying to troubleshoot this and nothing has helped.  It's not my phone because other aps report accurate distances.  I am going to factory reset it and then give up.  Nothing they have suggested has helped in the slightest.  you can try some of the steps they've had me go through if you like, maybe you'll get lucky, test between each step:

Reboot the device, and your phone

Make sure firmware on your phone is up to date, including whatever maps app you use

Make sure the app and the firmaware on the device are up to date

Reboot again if you had to update anything

Remove the device from your fitbit account, and re-add it

Uninstall the app from your phone and reinstall it

You can also adjust your stride length and see if that helps.  Walk or run or whatever it is you do a known distance in feet, and calculate your stride length using the number of steps you took to cover that distance.  You can then manually input your stride length and see if that is helpful.  That was one of the first things I tried.

[Clairey83]

Hi, I've experienced the same thing. I've only had my versa since April, but have been doing more running recently, including parkrun. My watch records 5k parkrun as 4km & often, when I run with a friend who also has a versa, my watch calculates a much lower mileage. It's really frustrating, what's the point in tracking your exercise when it's inaccurate! Really unhappy & it sounds like it's not an easy fix!

[KHorvath56]

My Versa/phone are also tracking very inaccurate and jagged. I can't find a fix within the site. There was a fix for a similar issue back in 2/2018 but I couldn't find the solution post with what to try. Exampes, with my hiking club they have 4 miles and I have 5.2. Or they have 7.7 and I have 9 miles.  Help!

[nicholasBhu]

Same problem with my Charge 3.  There are other recent threads with others having the same problem and one person got a reply from Fitbit saying they are aware of an issue but a fix in the immediate future is not likely.

[Feng]

Hey. Just want to add that I am experiencing inaccurate gps tracking of my runs this week.

I have been using versa connected gps since April this year and it was fine until this this week.

My route was correctly represented on the map in the fitbit app. But the distance was off by 10 to 20%. Hope fitbit will look into this issue ASAP.

[dryheatwriter]

I'm having the same issue. I have 3 recorded runs that each calculated a 20-25% increase over the actual distance. The Fitbit did this consistently throughout the run - I hit Mile 1 while running partners were at .75. My friend's total (and Google maps) showed we did 9.3 miles, Fitbit showed 11.8

I ran a measured race (14k/8.7 miles) and hit mile markers well in advance of the posted markers by the race people and ahead of my running partner who was using MapMyRun. Fitbit ended with 10.2 miles.

For me, this seems to have started since the Firmware update received on 9/20.

Fitbit is version 32.68.9.12

I use a Galaxy S10; recording runs with MapMyRun on this device works fine - I get exact distance.

I have had no other bluetooth devices connected during the runs in question.]

[KHorvath56]

Negates the value of owning a Fitbit... Might have to go to Apple Watch! Cant trust Fitbit anymore. Especially since this has been going on and off since at least February 2018! Guess they need new upper management at Fitbit...

[Jackos]

Fix not likely? How do they excuse that? Mine C3 is recording 20% less distance than Google fit.  I know google is correct because i've running the same route around my island for years.  This inaccuracy makes the C3 unusable and needs fixing.  Even if they really are getting out of hardware and don't care about sales of the c3 you'd think theyd want their software to be accurate?

[dryheatwriter]

I just did a complete reset of my Fitbit: 

1. Removed Versa from my account
2. Unpaired versa from my phone
3. Uninstalled Fitbit app
4. Rebooted phone
5. Reset Versa to factory settings
6. Reinstalled everything. Made no customizations to Versa (default watch face, didn't turn on notifications) . 

Versa is now back on older firmware 32.33.1.30; I have no prompt to download new firmware. This process took about an hour, so not for the feint of heart. 

I started Run app on versa and it connected GPS quickly (it was having issues with connecting GPS before firmware update) and I went for a measured 1 mile run around the block, run on the inside of the circle. Versa showed .9 miles. I'm assuming that the Google maps measurement used the other side of the street, which accounts for the difference.

I'm going to try my 2.2 mile dog jog tonight (I don't run 100% of route and pause a lot for the dogs stuff). It came up 2.6 miles this morning, so it may be a better test of the GPS vs stride length question. 

Tomorrow I'll try a point-to-point to test running again. 

[mortie5k]

I'll be interested to hear how it goes.

I can't even find how to factory reset mine.  The instructions I am finding seem outdated.

I've tried some other things, adjustment to stride length, etc...still get the same +25%

I'm about done with this thing.

[nicholasBhu]

Was accurate today.  Anyone else?

[Feng]

Just finished a run. Still inaccurate for me.

Runkeeper = 13.7km

Fitbit = 15 km

[mortie5k]

I had the first accurate one in months - but the trick is I let it track my run as a walk instead of a run.

I tried this because when my fitbit auto tracks my runs (I don't start them manually) it lists them as a "walk" . So this time I tried manually starting my run as a walk.  

It was dead on.

Next time I will try it as a run again but I think for whatever my issue is, a viable workaround might be to track my runs as walks.  It's disappointing because I have worked **ahem** hard for months to be able to run like I am doing now so it sucks to hit the walk button and then take off running, but whatever.

Hopefully this will continue to work for me and save me from having to buy a different product that...you know...works...for now.  I do think this is going to be my last fit bit purchase, though.  Too bad, because overall I do like the versa.

[dryheatwriter]

I did my "2.2 mile" dog walk last night and it came up as 2 miles, so it seems I'm now losing 0.1 miles for each mile I move. I tracked it as a walk, not a run. I've double-checked my route using Google Maps and it does indeed come up as 2.2 miles; past walks using MapMyRun would show 2.18 miles.

I've yet to test the point-to-point accuracy, or longer distances and am hoping to try again tonight for at least 4 or 5 miles on an out and back, and using the Run setting (along with my pitifully slow running style).

I also now got the prompt to download the Firmware update. I'm going to hold on doing that until after my Saturday long run (10.6 miles) to complete this testing. Then, post upgrade, will continue testing and will report here.

Overall - I'd rather it show me short than long. At least with short, I can know that my pace shown is lower than actual.

[mortie5k]

Yeah I have also declined to install the update the app is telling me right now.

For reference, my pace is ALWAYS listed as being faster than actual and my distance is ALWAYS calculated at right around 25% higher than actual.

I think I know why, but no idea how to solve it.

[dryheatwriter]

Just did my 2.2 miles walk again, but used run tracker - didn't run much because dogs were to busy sniffing around. This time it came out as 2.34 miles. 

I'll try for my point to point run tomorrow (and actually run it) to see what happens. 

I'm just sad to think that Fitbit seems to have changed the behind the scenes way it calculates distance and while it logs the GPS route on a map, it's not using GPS for distance traveled. 

[nicholasBhu]

My Charge 3 was over again today.  4.09 miles when it should be about 3.45 miles.

[jacqcrooks]

I've been having the same issue with my Versa for a few weeks now.  GPS on my phone is working perfectly as I've tested it by using Pacer at the same time, so can't be fobbed with with the trees or cloud cover nonsense. Today a regular route of just over 9k route showed as 7k on Versa.  Pure rubbish when you're trying to track pace & distance.  Anyone know how to return a Fitbit.  Pointless if it doesn't work 👎

[Jackos]

I reinstalled the app a couple of days ago and have done two runs since that, both runs matched the distance reported by Google Fit, (9.3KM) so either Fitbit fixed something or reinstalling the android has helped in my case.