10-14-2018
11:24
- last edited on
11-17-2020
15:06
by
MatthewFitbit
10-14-2018
11:24
- last edited on
11-17-2020
15:06
by
MatthewFitbit
The GPS on the fitbit3 is not accurate. My phone tracks me and the fitbit is at least 0.2 miles off. It also gives me like 60 active minutes for maybe 35min of exercise (and my heart rate was not elevated for that far beyond my exercise to account for that). Im dissapointed that this isn't nearly ad accurate and I still need to take my phone running to log a workout =(
Moderator edit: updated subject for clarity
01-13-2019 04:59
01-13-2019 04:59
i have the same issue on my Charge 2
Run the same route.
Mapmyrun = 8.5Km
Mobilerun on Fitbit App=8.5Km
Connected GPS using device = 9.6Km
they all show the same map, route is on the road no glitches etc. i do the route multiple times and what is interesting is that the device matches the km all the time I know exactly where the 1km and 2km marks are using the watch vs using the App and the watch is overestimating distance. Google maps agrees to Mapmyrun and i drove the route to double check.
I tried using my partners device and her phone and the connected GPS again had the same 9.6Km so its consistent.
how can the phone through the App for the same run show a different distance than Connected GPS for the same map?
Using latest Firmware APP is updated all is connected the map shows, no gaps but distance is wrong...
01-29-2019 06:15
01-29-2019 06:15
I'm using an iPhone XR. Is there anyone using another kind of phone and getting more accurate results?
01-29-2019 06:39
01-29-2019 06:39
01-29-2019 06:53
01-29-2019 06:53
So it´s just a IOS-problem? Hope they fix it quite soon.
01-29-2019 09:36
01-29-2019 09:36
01-29-2019 12:06
01-29-2019 12:06
02-16-2019 18:05
02-16-2019 18:05
Count me in as another with this issue. Android user: Moto G4 Plus.
When using Runkeeper on the same phone I was getting consistent data, but since moving to the Fitbit it's being wildly inconsistent: differences of up to 200m on a simple 1km walk on different days. For non-metric users that's a 20% difference.
The other day I did a walk that Runkeeper has listed as 2.2km in the past, Fitbit tracked it as 3km. Today I did an actually longer walk but was tracked in as 2.6km.
Considering I purchased the Charge 3 to help train for a multi day hike, not bring able to trust the GPS distance tracking is very annoying.
To be clear I am manually picking the activity and ensuring that my Fitbit is connected to my phone before starting the activity.
05-18-2019 04:11
05-18-2019 04:11
Run was exactly 5k.
A 5k run... fitbit was fully connected with my mobile at the start of the run. Says that it was only 3.8k. Makes the run tracking function utterly worthless.
06-06-2019 21:58
06-06-2019 21:58
Exact same issue here. Loved my Charge 1. But, charge 3 offers nothing more w/out gps. Phone is fine..MapMyRun is dead on.
07-30-2019 06:34
07-30-2019 06:34
The same issue. I found this discussion to see there are more ppl with the same issuem it is really frustrating to count less then reality. GPS is always connected. Using Android.
Anyone is taking care of this issue and when it will be solved, pls?
07-30-2019 07:12
07-30-2019 07:12
08-21-2019 10:30
08-21-2019 10:30
My Fitbit Charge 3's GPS is also wildly inaccurate. I followed all the listed steps to try to correct the problem but I am unable to perform the following step:
You selected an exercise type from the Exercise app that uses connected GPS. Swipe up on any exercise and check that Use Phone GPS is listed and set to On.
When I select "Exercise" it goes to "Exercise Goals." When I I then select "walk" and I see "Auto-recognize" which is toggled on and "walk longer than" which is set to 15 minutes. Is this where I should be able to swipe up? It doesn't respond to swiping. I noticed that other people also questioned how to do this. Would someone please explain in a detailed step-by-step way how to do this?
09-18-2019 08:58
09-18-2019 08:58
My Fitbit has been accurate in my morning runs until yesterday, I always take the same route so know the distance, around 10.3km. But since yesterday the Fitbit is showing shorter distance, yesterday was 9.73km and today 8.78km. In both cases the GPS connection stablished right away at the beginning of the run. Even the floor count after the runs are significantly lower than the previous runs. Although the map is the same for these runs the elevation is significantly different and KM markings on the map are different too. It looks like Fitbit loses connection to the phone. The distance calculation based on step count is similar though.
I haven't done any app update or phone change since Monday so I have no idea why this is happening, very annoying. I am planning to contact support.
09-18-2019 09:08
09-18-2019 09:08
09-23-2019 02:18
09-23-2019 02:18
I'm having the exact same problem. I've been using my fitbit almost daily to run the same 5 miles and since last tuesday its not recording only 4 miles when I've actually done 5. I notice the app updated on 16th september so I am now assuming its something wrong on the update. gps is connected and I've compared it against maps and run keeper and it is a 5 mile run! so frustrating as it's now knocking my fitness score down thinking its taking me longer to run a mile!!
09-25-2019 01:24
09-25-2019 01:24
Having had a charge HR and charge 2 I was happy to receive a charge 3 as a gift. However having started running training the issue of connected GPS distance is driving me to consider ditching Fitbit all together.
Repeatedly despite accurately showing the route Fitbit I'd significantly under recording the distance. For example a 6.25 mile route ( mapped on Google, confirmed on onthegomap and correctly measured by mapmyrun on the same phone is recorded by Fitbit as 5.77 miles.
How can it be that it accurately shows the route (using what appears to be a Google map) but massively under measure the distance especially given it using the same phone as mapmyrun??
Fitbit charge 3 sync to Moto G6.
09-25-2019 01:44
09-25-2019 01:44
09-25-2019 01:51
09-25-2019 01:51
09-25-2019 09:25
09-25-2019 09:25
hello to Fitbit moderators.
Anyone can explain this, please? The same route, but distance is different, how come?
09-27-2019 10:09
09-27-2019 10:09
I've read this entire thread. I have the exact same problem (just received as a birthday gift). Using Android on a Samsung Galaxy S7. At first I realized you had to disable "Power Saving" to get the GPS connected and remain connected. If you fail to do this, the GPS will cut out after ~ 10 seconds. Of course, this is NOT formally documented by FitBit. Pretty bad. Now I have the problem where the FitBit map shows accurate tracing but the distance is wrong (i walked 3.93 miles but FitBit totaled only 3.23 miles).