03-25-2020
17:07
- last edited on
04-22-2020
16:50
by
RicardoFitbit
03-25-2020
17:07
- last edited on
04-22-2020
16:50
by
RicardoFitbit
I use a Charge 3 and have been tracking runs by opening the app and starting a workout, using GPS.
When I select the recorded run, the top bar of the "Map" tab and the stats on the "recent" tab show the accurate distance/pace (I've checked using other tracking systems). The map itself shows the correct route but wrong total distance (typically about .5 miles less), and the "Splits" uses the incorrect distance as well, resulting in incorrect splits.
Battery is fully charged and it's happened for over a week now on every run I record.
Any ideas?
Moderator edit: Subject for clarity
04-22-2020 16:50
04-22-2020 16:50
Hi @Mqhorn, welcome to the Community Forums! Sorry for the delay in responding your post.
Thanks for bringing this to our attention and for all the details that were shared. I'd like to share with you that our Support team informed me that they already provided you assistance to resolve this situation. That said, I recommend you to contact them back if you require further assistance or if you have any additional questions about the outcome of your case.
I'll be here if you need anything else.
04-24-2020 05:13
04-24-2020 05:13
Hi I'm also having this issue. How do I fix it?
05-08-2020 03:44
05-08-2020 03:44
i have found a couple of things regarding this: if the watch recognizes a run and you also use the app to start a run through the Exercise option, then you can have two separate entries. But My wife has been running without her watch on, just using the app to monitor the distance. This creates just one entry for the run but still creates two different distances. It seems that this problem has been a recurring one for a number of years, going by previous posts and forums on this site, yet no clue as to a resolution.
Any update?
11-25-2020 08:32
11-25-2020 08:32
Also a Charge 3.
Here is graph of the two GPS Maps and Data. Which is correct? The watch on top? Or the phone on bottom?
I also contacted Support team, but was unable to get answer other than "with both devices using GPS, they may be overwriting each other."
(1:43 pace difference per mile is a Huge Margin. And phone cues had me at the 3.5 mile distance. Not sure how Over half a mile got added on the watch.)
I'll be carrying an additional stopwatch next run to see which is correct, but wanted to see if there may be another solution someone has found. Thanks