Distance in my Fitbit app completely inaccurate

[CarlosUK]

Good afternoon. I have a Fitbit Blaze.

i recently changed my IPhone 5S for a 6S however since the change I have noticed that the distance registered in my app when I go out for my regular route is out by approx 100m per Km. I have done my usual route many times to notice that something is not right with either the phone GPS or the app.

I am a runner of approx 5:30min per Km and today when I went to run in a new route The app was telling me I was running at 3min per Km which is completely unreal.

can someone help me?

I have changed the settings of my stride length on the phone to calculate it automatically but it did not work. I also turned the GPS phone tracker on the Fitbit watch, without activating the app and it seems to work OK, which makes me think is the app.

thanks for your help.

[Colinm39]

@CarlosUK.  I have a problem on the Blaze using Connected GPS in and East/West direction. It gives me a 2min/km faster pace than my accurate Surge or MapMyRun. This equates to about 12"/second or 30cm/second in the Southern Hemisphere. 

Distance on Exercise tracking through the Android App is OK... if you only Pause and Finish.. We lose the map if we pause and resume in a mapping period.

---

@CarlosUK wrote:

Good afternoon. I have a Fitbit Blaze.

i recently changed my IPhone 5S for a 6S however since the change I have noticed that the distance registered in my app when I go out for my regular route is out by approx 100m per Km. I have done my usual route many times to notice that something is not right with either the phone GPS or the app.

I am a runner of approx 5:30min per Km and today when I went to run in a new route The app was telling me I was running at 3min per Km which is completely unreal.

can someone help me?

I have changed the settings of my stride length on the phone to calculate it automatically but it did not work. I also turned the GPS phone tracker on the Fitbit watch, without activating the app and it seems to work OK, which makes me think is the app.

thanks for your help.

---

[txjeep]

I have the very same issue, inaccurate recording of mileage & pace. did you receive any solutions to this issue? 

[Colinm39]

@txjeepWe are still waiting for acknowledgement from Fitbit.

I have explicitly chosen a route where I live in and East/West direction and had the Fitbit App (Android) exercise tracking (MobileRun) and Blaze Connected GPS and the Blaze definitely increases distance and Pace against MobileRun as I posted earlier.

I'm on the latest App of a few days ago and no difference, the problem is still there with Connected GPS . MobileRun is OK and I proved that last night an plotted the course afterwards on Google Earth and Google Pedometer and the mapped distance was within 1% on 3.7km...

---

@txjeep wrote:

I have the very same issue, inaccurate recording of mileage & pace. did you receive any solutions to this issue? 

---

[Veronicalolo]

I am having the same issue just did A 10k run it blaze gives me 12km normal pace about 6 and instead gives me 4. So frustrated 

what should we do about this?