Mileage pace/distance whilst on a run incorrect

[squisheeseal]

Hi,

Wondering if anyone else has been having the same problem.

Ever since the last few updates my blaze is about 1m 30s out per mile, and the distance is always incorrect.

It's using the GPS on my Galaxy S6, phone connects fine pre run and I make sure that Wi-fi is switched off so it doesn't randomly connect to free wi-fi and drop mid run?

Any help/ideas appreciated.

Cheers

[AlejandraFitbit]

Welcome to the Forums @squisheeseal. Your Blaze, uses the steps you do and multiply them by your stride length to calculate your distance and this may not be the same as a premeassured distance or calculated by GPS.

If you would like to improve the accuracy of your running, I recommend calculate your stride length by doing the following:

1. Go to a track or some place where you're sure of the distance.
2. Count your steps as you walk across that distance, making sure you travel at least 20 steps.
3. Divide the total distance (in feet) taken by the number of steps to get your stride length.

Your running stride can be calculated the same way if you run instead of walk. To adjust your stride lengths using the fitbit.com dashboard, click the gear icon in the top right and go to Settings > Personal Info.

The stride length fields are in the Body Info section. If you use the Fitbit mobile app, go into the app and turn off Set Automatically under the Stride Length setting.

I hope this helps, let me know the outcome.