Distance tracking WAY off

[Andih86]

I'm wondering if anyone else has had an issue with the distance tracking being way off. I ran a 5k race today that was chip timed. Strava has my distance as 3.06 miles which is really close but fit bit is showing 4.22 miles. My pace with Strava was 13:00 but fit bit it was under 10 minutes. Anyone have any idea how to fix this issue? I would love to think I'm running that quickly but I know the distance I was running so I know my versa was way off.

[nicholasBhu]

I think it is an issue with the new app update.  I rolled back to Version 3.5 and it fixed it.  Guide how to do that here: https://www.androidpolice.com/2018/06/03/go-back-older-version-app-android/ 

I advise to let customer services know so they can see this is a widespread issue.

[nicholasBhu · Accepted solution]

My old phone where it was working with App Ver 3.5 autoupdated yesterday to 3.6.1.  It actually calculated the right distance just now on my walk.  The problem for me started with my new Samsung Galaxy A70 seemingly after the app update a week ago.  Haven't retested on my Samsung yet.  Will probably wait for another update.  So it seems to be phone specific issue with the new app update if the issue still exists.

[GrubbyDuck]

Check your stride length is correct in settings.

Mine is 'automatically changed back to default' every upgrade 'Why do this FitBit?' or patch issued so giving subsequent incorrect calculations for distances.  

[ithinkdancan]

Same here. Ever since I updated to iOS 13 my tracking has been way off and my path on the map is just a jagged mess. Not sure what’s going on. Seems to happen on other running apps as well though. 

 

[Andih86]

The interesting thing is I didn't have the issues with my GPS location being really off. It actually tracked my location perfectly. It just registered the distance differently, which is really weird. 

 

 

[Andih86]

Im not sure stride length is the issue since it was connected to GPS. Sounds like others are having this issue as well. I think I'm going to rollback my version of the app because I didn't have this issue with the previous version.

[Andih86]

Thanks. I will definitely rollback to the previous version of the app because it was the update that precipitated the issue.

[wilson23uk]

Hi both, Did you find that rolling back to V3.5 worked in the long run? Are you still using 3.5 now and finding it works ok?

I'm having the same problem.

[nicholasBhu]

Hi Wilson.  I ended up getting a Garmin during Black Friday.  Couldn't get Fitbit to track properly.