Charge 3 is showing accurate GPS map, but inaccurate distance

[SunsetRunner]

I've been using my Charge 3 for about two months now and noticed that often when I run, the GPS map accurately reflects my route, but the distance is quite a bit off. I tested this a few times by running the perimeter of Mile Square Park, a park so named because it's a square approximately 1 mile on each side (4 miles total).

Here are the conflicting data points (links to screenshots):

1. 3.93 miles: the distance according to Map My Run.
2. 4.01 miles: the distance my Charge 3 calculated, presumably based on my steps and stride length, when I ran the perimeter without connected GPS.
3. 3.35 mi: the distance my Charge 3 calculated when I ran the perimeter with connected GPS last month
4. 3.23 mi: the distance my Charge 3 calculated when I ran the perimeter with connected GPS today

As you can see in #3 and #4, the route captured by my phone's GPS seems accurate; it goes around the perimeter of the park, with no gaps. But somehow the distance is approximately 0.6 to 0.7 miles less than what it should be, which suggests that Fitbit is interpreting the GPS data incorrectly. Any idea what's going on here?

Moderator edit: updated subject for clarity

[Watched]

I will say that after downgrading my app and turning off auto updates, this
was fixed.

So obviously this is a bug in the code that is hiding somewhere and comes
out with some app updates

[Aaron.a]

Hi may I ask how you downgrade the apps ?

[Watched]

You just have to delete the app and then download a different version from
an app mirror. I can't give more information than that without violating the code of conduct for this forum (I tried and the message was not allowed). This is not a recommended Android
method and should be avoided if possible because it opens that phone up to
potential security vulnerabilities.
Since I downgraded there have been 2 app updates (3.19.2 and 3.20) that I
haven't tried, so I will have to reupdate and see if things have been been
fixed.

[BredaMG]

Just did a 7.4km walk map is accurate but fitbit distance shows 5.79km big difference, very annoying.

[AdamFerguson]

Any word if 3.21 release addressed this? I'd rather not have to buy another option but will should I need to.

[BredaMG]

Still having issues

[AdamFerguson]

Thanks for the update. I think based on the reading I've done recently, Fitbit has lost quite a few customers

[Watched]

For flatter terrains, 3.21 has been really good for me, but when I'm mixing in steeper sections everything goes out of wack. 3.17 was the most stable for me.

[BredaMG]

They have offered me a new device if I return my existing one, waiting for
a few days now to get a shipping label from them via email. I dodn't think
the device is the issue as I've used my sons charge 3, linked to my
account, and same issue.

[BredaMG]

Excuse my stupidity but how do I check if I have latest update

[Watched]

This is on Android, right? Go to the play store, click "My apps & games" and find where your fitbit app is. It will either have an update available or be up-to-date.

[BredaMG]

Perfect thanks, no update pending

[Nicolevx]

I run with my GPS connected and the map shown on my Fitbit app after my run is perfectly accurate. However, the distance is horrible. On Google maps, my run today was 4.6 km, on Fitbit it recorded 3.55 km with GPS connected. What is the issue here. This happens 99% of the time and it is negatively impacting my pace and my overall fitness score on the app.

[BredaMG]

I've tried adjusting stride length and it makes no difference. It's very frustrating 

[Nicolevx]

Yeah, literally tried all the suggestions given here to try and fix it 🤷

[Aaron.a]

Hi I managed to solve my issue. Before the run I restart my Samsung S9 plus and make sure the phone power saver mode is not turn on. With this I am able to get quite accurate GPS distance. Cheers!

[Nicolevx]

I'll try this just in case, though my phone is never on power saver mode
when I run, it is continuously connected to mobile data and the map I get
on my Fitbit app is perfectly accurate, it's only the distance which is not
synced from Google maps 🤷

[Aaron.a]

Ya this is the same issue I had. Goggle map is accurate but the distance for around 9 km run only show around 7.30 km.

[PiaNE]

Same issue with mine. 

1 the connection was done before the run

2. I measured the length using Google maps built in tool + I measured with another app. They showed the same 1,7km for my short beginner run. However firbit told me 1,4. Even if drawing the line for my run close to correct.

Soo disappointing. My next watch is not a firbit.... 

[October8]

Mine is off about 1.5 miles