01-10-2019
23:44
- last edited on
09-08-2020
17:54
by
MatthewFitbit
01-10-2019
23:44
- last edited on
09-08-2020
17:54
by
MatthewFitbit
Hi
My Mapped routes using connected GPS are always higher than using the Mobile run App. If do a run directly using the APP and not the watch it seems more accurate and agrees with MapMyrun and even Google maps, but when I use the watch it states that connected GPS is on, shows the map etc but distances are different. I have updated the APP using the latest Firmware etc but for example i runa route and it will say 9.6Km on the Map when using the watch and on the same route say 8.5Km using the App direct from the phone.
I have seen some similar topics from 2016 but thought this would be fixed they both GPS on the same phone but taking different readings. Does Connected GPS really use GPS or is it just to show the route and the step count does the distance?
Cheers
Answered! Go to the Best Answer.
01-13-2019 10:34
01-13-2019 10:34
@Batbit Welcome to the Fitbit Community! It's great to have you here! Sorry to hear that your Connected GPS distance is incorrect. Currently there is a bug that affects the distance calculation. The team is investigating this but at the moment there isn't a resolution so I can only ask for your patience while this is resolved.
I'll be around!
If a post helped you try voting and selecting it as a solution so other members benefit from it. Select it as Best Solution!
01-13-2019 10:34
01-13-2019 10:34
@Batbit Welcome to the Fitbit Community! It's great to have you here! Sorry to hear that your Connected GPS distance is incorrect. Currently there is a bug that affects the distance calculation. The team is investigating this but at the moment there isn't a resolution so I can only ask for your patience while this is resolved.
I'll be around!
If a post helped you try voting and selecting it as a solution so other members benefit from it. Select it as Best Solution!
02-20-2019 18:55
02-20-2019 18:55
I'm experiencing the same issue. Would love to have this fixed
03-07-2019 22:22
03-07-2019 22:22
Connected GPS is why I got this Fitbit in the first place. its alot better to check your progress on your wrist rather than wait for an app to give voice Prompts.
Well played fitbit scammed me good. I have rid myself of the device and will be getting a GARMIN.
11-23-2019 11:48
11-23-2019 11:48
Also having the same issue except I generally run 12 km, the app on my phone says 12 km but fitbit generally will claim that it is 11 km. Once or twice it credited me for 13 km. The funny thing is that fitbit was always just as accurate as my phone up until a couple months ago.
Why is this bug taking so long to fix? Does Fitbit actually care about the quality of their product now since they have already established themselves? Most exercise enthusiasts and athletes care about the accuracy of their activity trackers. The fact that this is still an issue really shows where fitbit's priorities are.
02-24-2020 12:29
02-24-2020 12:29
I just started experiencing this as well. My usual 3 mile route that I have been running for years is now suddenly 4/10 shorter when logged on my watch. Mapmy run is consistent, however even my average pace is off by almost 45 seconds. How is this still an issue? Totally disappointed.
02-25-2020 06:47 - edited 02-25-2020 06:54
02-25-2020 06:47 - edited 02-25-2020 06:54
05-15-2020 12:44
05-15-2020 12:44
I just purchased 2 Charge 3 devices and the GPS is not accurate, or consistent. My wife and I walk the exact same route, together, every morning and get different results for the distance, sometimes as much as 1/2 mile different. The fitbit displayed GPS map is always correct, but the locations for the splits and the reported distances vary all over the place, FOR THE SAME EXACT ROUTE every day.
I've read about 20 pages of people with the same issue, on multiple fitbit threads, and no solution from Fitbit. This is pretty pathetic - something as simple as logging the GPS data from the phone into the Fitbit app is not rocket science. Come on, Fitbit, lets get this fixed.
Android, Galaxy S9, S9+
08-18-2022 15:08
08-18-2022 15:08
Can we get an update on this bug? It's 3 1/2 years since the original post and this problem still exists. If you can't fix it, can you provide more information about the nature of the bug, e.g. is there a factor we can multiply the Fitbit distance reading by to get the actual distance, or are there things we can do with our trackers or our phones to improve the accuracy? Thanks!