Is auto stride really off?

[Twitchy]

I have had the Blaze since it came out. I have noticed over time that the tracker always changes my steps to less then I have taken based on distance walked.

I know that the Blaze is capable of calculating stride when used with a gps. I also know you can turn that feature off in settings. With it off it should use the stride length in settings. I have a stride length that has been taken over 400 meters then averaged over 10 measurements.

I have been checking it against my Charge HR and something is wrong. My guess would be the programming is ignoring the settings button.

Anyone else experienced this?

[Corvettekid]

Lots of us...check out the Steps and Walking threads.

FitBit tech support is supposedly on a fix.

[Rich_Laue]

îis The Charge amd Blaze connrcted to the same account, and ate ypu using the connected gps with tue blaze. If so then it would be using the GPS for distance

[Twitchy]

Charge and Blaze are on the same account. 

All my calculations as to actual steps were made without the Charge HR connected to anything. The battery was totally flat. 

Again, I have my actual stride length measured over 400 meters at the middle school track. It is a modern new 400 meter track. I then took all the measurements I made (some more, some less) and averaged them to get the stride of 79.9cm that I have entered in settings (Main Program Settings on computer). 

If the switch on the phone app (App>Account>Advanced Settings>Stride Length>Set Automatically) is set to off whether a gps is used or not the stride whould use 79.9cm/step (stride) to measure the distance. Right now it does not. It remains variable.

steps x stride = distance or distance/stride = steps

Either of these calculations should remain constant. When I use the Blaze with the (App>Account>Advanced Settings>Stride Length>Set Automatically) turned off. The Blaze remains variable.