Hello!
I'm using my Versa 2 to track my runs with connected GPS. But it is not using the GPS data for calculating the distance. For some reason it's using the steps or other metric to calculate this, but not the GPS data.
Before you give me the standard text for restarting the phone/bluetooth/GPS, don't bother, I have done all that. My GPS is working fine, it's tracking everything fine. When I export the route as tcx, convert it to gpx and upload to google maps, I get the exact same route. It's exactly the same. Except for the distance, which is way off in the Fitbit workout.
To prove my point, I tracked this run (excersise nr 30359910679):
But all I did was sit behind the same desk, I'm now writing this message, and move the watch back and forth, simulating steps. The phone didn't move one centimeter, but somehow it shows that I moved 0.25 KM, which obviously is not correct.
I even loaded the same data to google maps, and it shows 0,0km for the distance as it should.
The issue is not with our phones as you'd like us to believe, but the problem is that there is a bug in your platform causing some other data, besides the GPS data to calculate the distance. It sickens me that you're avoiding responsibility for resolving this problem. The only reason I got this watch was to track my runs and this renders it pretty much useless for that purpose.
So please, Fitbit, pull your legs out, and fix your platform!
Best Answer
