Android Fitbit GPS inaccurate for Walk

[Robertson]

I tracked a walk using the Android App (with my Charge HR on my wrist). The GPS map was ridiculously inaccurate - when making a turn the map would calculate the route cutting the corners by a lot. I checked the route we walked to determine the KMs (6.1) but the Fitbit App came up with 5km because it was losing a lot of what we did with its infrequent GPS location sampling.

What's going on? This makes it useless.

[Robertson]

Here is a screenshot of the walk - you can see the ridiculous path it is tracking instead of the 90 degree turns we are doing. For example we walked Lumsden to Woodbine, up Woodbine to Cosburn (behind the #1), then down Woodbine to Holborne, across Holborne for 3 blocks to Binswood.... but look at the path is has for that part!

I use Strava daily for tracking my Running with GPS and it has no issues like this.

[USAF-Larry]

It appears that the GPS is shutting down on your phone, @Robertson.  What version of Android OS are you running?  If it is Android 6.0x Marshmallow, you need to ensure that Battery Optimization is turned off for the Fitbit app.

[Robertson]

Great suggestion. Tried it and no success - it still cut corners and came up with 2.2 km vs another App tracking the same run at 2.6 km. Map shows the screwy path too.

Did a run with Strava on same phone and no issue. Guess I have to stick to Strava

[rtbrown560]

I am having similar issues, I have a thread over here about the issues (and proposed solutions that haven't worked). My solution is the same as yours, just use Strava. Fitbit would lose part of my ride at least once weekly, haven't had a single issue with Strava (and the autopause is kind of nice too).