04-13-2020
07:49
- last edited on
09-08-2020
10:02
by
MatthewFitbit
04-13-2020
07:49
- last edited on
09-08-2020
10:02
by
MatthewFitbit
I have a charge 2 which i use mainly for running, however it is not tracking distances correctly (this is my 2nd device as my first one was replaced after developing a fault). The device is out by a considerable amount, for example my recent runs have been in the region of 8.9 kms and when tracked on run keeper or map my run yet my device records the same route as only 7.3 kms. This obviously then has a knock on effect on km's per hour and splits. I have done a re-boot but this hasn't worked. I also have GPS turned on for running on the app.
The whole point is having a fitness tracker is to track yourself and right now it isn't able to do the job.
Any help appreciated.
04-13-2020 12:22
04-13-2020 12:22
I’m also having the same problem. Very annoying! I’ll keep an eye out on an reply’s you might get.
04-14-2020 00:36
04-14-2020 00:36
04-14-2020 02:09
04-14-2020 02:09
Having the same issue, I updated my Fitbit yesterday. The thing is that it used to measure the distance correctly. Yesterday I went for a quick run, the Nike Run Club app showed 4.11km which is correct when I compare the distance with Google Maps but my Fitbit Charge was showing 3.10km but the map shows the same route as the Nike Run Club app. My girlfriend was also with my on this run, she wore a Fitbit Versa and used Strava to track her run. The Versa watch was also off by 800m while Strava showed the same result as the Nike app, 4.11km. How difficult is it to track distance with GPS? This is your main feature and it is totally unreliable now.