03-02-2016
13:12
- last edited on
09-22-2021
13:26
by
AlvaroFitbit
03-02-2016
13:12
- last edited on
09-22-2021
13:26
by
AlvaroFitbit
Ever since I switched from my charge hr to the blaze, my miles have decreased. I am 6" 6' and I average about 1900-2000 steps per mile. I went into settings to update my stride length, bit it is still putting my average to 2250 steps per mile. Help
Moderator Edit: Clarified subject
Answered! Go to the Best Answer.
04-22-2016 09:48
04-22-2016 09:48
04-23-2016 08:19 - edited 04-23-2016 08:21
04-23-2016 08:19 - edited 04-23-2016 08:21
Then before starting your walk/run I would turn the connected gps option off, by clicking the settings gear on the let's go screen.
Now since the Blaze now is only able to count steos and has no way of measuring distances, you will need to calculate and set your stride.
I used the GPS and the step count for 5 days worth of event data, averaged then out to come up with a stride measurement.
04-23-2016 08:40
04-23-2016 08:40
04-23-2016 09:47
04-23-2016 09:47
Hello @Heathershy if your using connected GPS then seeing the stride will not work, this is because the tracker gets its distance from the GPS. Now If your not using the connected GPS then let us know.
04-23-2016 09:51
04-23-2016 09:51
04-23-2016 10:04
04-23-2016 10:04
04-23-2016 10:04
04-23-2016 10:04
04-23-2016 10:16
04-23-2016 10:16
04-23-2016 10:18
04-23-2016 10:18
04-23-2016 10:51
04-23-2016 10:51
04-23-2016 13:22
04-23-2016 13:22
04-23-2016 15:44
04-23-2016 15:44
04-23-2016 16:26
04-23-2016 16:26
04-24-2016 12:23 - edited 04-24-2016 12:43
04-24-2016 12:23 - edited 04-24-2016 12:43
Please remember if your using the connected GPS then stride length will not have any affect on the distance the GPS has recorded.
Now I'd the phone is not with you, our you have the connected GPS turned off, then the stride length will have everything to do with distance.
This is why it is impossible to give an interagency answer to this post, without knowing what mode your tracker is on.
Ive been doing some testing recently, I have a set path that when using MMW says is anywhere from .74 to .76 miles.
Three walks with the Fitbit app GPS tracking have me .75(2) and .76
Two walks with the Charge HR and no GPS have me .74 and .75.
The Surge with GPS gave me .75 .76 .77
The connected GPS on the Blaze said .75.
The 2 walks with connected GPS off gave me .74 and .76
As for step count the Blaze has been consistently low by 20-50 steps over 1400+ steps walked. This is an error of 2%. I use an event counter to count every left foot step.
For me it seems to be accurate, but it could be that some units have hardware that snuck in that is slightly out of spec, and could be causing problems.
04-24-2016 13:12
04-24-2016 13:12
I believe I have found what the problem is with the distance measurement. See
https://community.fitbit.com/t5/Blaze/Connected-GPS-vs-Mobile-Run-Difference/m-p/1322307#M14798
04-24-2016 13:20
04-24-2016 13:20
04-24-2016 17:31
04-24-2016 17:31
04-28-2016 16:13
04-28-2016 16:13
FOUND THE PROBLEM!!!!!
You have to go to settings in the app and disable the automatic stride length. It says it automatically adjusts every time you go on a run with a GPS enabled device, which might be true, but it does not help with walking.... and not every stide is recognized while running anyway but that is a seperat issue.
Either way, try changing this setting and entering your correct stride manually and see if it works... it did for me.
04-28-2016 20:58
04-28-2016 20:58
06-24-2016 08:51
06-24-2016 08:51
Have they actually solved this issue yet? I got a Blaze 10 days ago and I'm noticing the same problem.