Calibrating this thing...

[Pearcey555]

Hoping someone can help.... or at least point me in the right direction. I thought i read that the Blaze auto calibrates your stride pattern etc when linked to GPS on your phone and then uses that going forward by calculating your stride and distance traveled. .... I have been for a few runs with GPS connected on my phone and no problem (well there is a little bit of a difference between the Blaze and Strava but i can live with that), i have route which i know is 4.1 miles as I have run it a number of times in the past including with the Blaze connected via phone GPS... however this morning i went out with just the Blaze and no phone it registered the exact same route as 3.45 miles... am I doing something wrong ?

[Rich_Laue]

Fitbit suggests doing several runs with the connected GPS. Most people do not have the same stride every day and by doing several runs, Fitbit will get a better setting. 

[Pearcey555]

Thx Rich.... I have done maybe half a dozen but nothing seems to have changed/improved. Is there a predetermined number of runs i need to take or will it be a case of waiting til it improves ?

[D4getmenot2]

I am having a similar issue except my blaze is saying I am doing much farther than my Garmin says I went.  I wore both today and it was a difference of almost .4 miles.  Is there a way to reset it? 

[Colinm39]

@Pearcey555@D4getmenot2I have had to do inflate my walking stride by about 20% to cover domestic walking which includes carparks, shopping malls etc. That made  my distance accurate.  This occurred on my two Blazes and my Support case was eventually passed onto the engineers with no answers.

Secondly, in the Southern Hemisphere while using Connected GPS some of us have reported an increase in distance in an East/West (E/W) direction of about 12" or 30cm/second.  North/South (N/S) is OK. Again no reaction from Fitbit.  Wearing my Surge when I go in an E/W direction my pace immediately increases goes faster on the Blaze by about 2kmh/hour while the Surge remains normal. Which proves there is an issue.

The Phone GPS with MapMyRun and MobileRun (Fitbit Exercise, Tracking, Run) is OK.

[CStewartTX]

Same thing has been happening to me.  It changed with the latest update.  I have been running a 5.25+ mile route for the past year and until a few weeks ago my Blaze was calculating accurately.  This morning I used my Blaze and another very reliable/accurate app and the results are...

Blaze - 4.80 miles - 53:39.6

Alternate App - 5.27 miles - 52:52

The response from Fitbit this morning....

Let's try to fix the situation with your distance, Fitbit trackers calculate distance by multiplying your walking steps and walking stride length. Similarly, your running steps are multiplied by your running stride length. 
You can enter your personal stride length to make the distance calculation more accurate. To measure your stride length, we recommend going to a track or somewhere that you know the exact distance of. Count your steps as you walk across that distance, making sure you travel at least 20 steps. To get your stride length, divide the total distance (in feet) by the number of steps taken. Your running stride can be calculated the same way, only by running a known distance rather than walking.
If you don't input your stride length, the site and tracker will use a default setting based off of your height and gender. As long as you've entered that information, the stride length it uses should be fairly accurate.