11-23-2022
10:04
- last edited on
11-24-2022
09:33
by
DavideFitbit
11-23-2022
10:04
- last edited on
11-24-2022
09:33
by
DavideFitbit
My Charge 5 GPS is not accurate. Today I ran 4.9 miles but the Fitbit recorder 5.74 miles. The map of my run looked like I was running drunk through yards and houses but I ran right along the edge of the road. Since the distance is wrong, my running pace is way off too. Anyone else having this issue?
Moderator edit: subject updated for clarity
11-24-2022 09:32
11-24-2022 09:32
Welcome to the Fitbit Community forums, @Tjhennessy.
I appreciate all the information provided about this inconvenience with your Charge 5.
If the GPS is getting disconnected during your activity, the Charge 5 may track different information for the the distance. Before considering other options, make sure to follow the steps suggested in this article.
All devices with GPS sensors require a direct path to GPS satellites to calculate location. A weak GPS signal might affect the accuracy of your route and other activity data. Your device uses your step count to calculate distance until it finds a signal, so the total distance calculated for a workout may be slightly less accurate when GPS isn't available for the entire time. In particular, please make sure of the following:
If you continue to experience the same behavior and your GPS is getting disconnected, make sure to try following the steps listed in this article to complete a restart, as this has been useful for other users experiencing something similar.
In case the problem is related to app and your map is not showing correctly, please try these steps as well:
I'll be around.
11-27-2022
10:49
- last edited on
12-10-2022
10:38
by
DavideFitbit
11-27-2022
10:49
- last edited on
12-10-2022
10:38
by
DavideFitbit
So far it is working better, but I will check it out for a couple weeks to be sure. In the past it has been accurate, then wildly off.
12-10-2022 10:38 - edited 12-10-2022 10:38
12-10-2022 10:38 - edited 12-10-2022 10:38
@Tjhennessy Thanks for sharing this update. Let me know if you continue to experience the same problem.
See you around in the Community.