Blaze distance walked is not accurate

[DLNothy]

 The distance walked on the Blaze (w/gps and w/o gps) is not accurate.  At ten miles it showed only 7+ miles.  With less distance it is the same difference.  Tech support says the engineers are aware of it and a fix is coming.  My Charge is also off.  The engineers are working on it, and is an issue across the board,  seems to be an old answer.  A "fix" is coming but no time frame,  I have been with Fitbit for a long time but it may be time for a change,

[Julia_G]

Hi, @DLNothy, I have to say that I am notvaware of any current issue that the engineers are working on with GPS inaccuracy...

As I am sure you know, the Blaze doesn't actually have built in GPS.  It uses the GPS on your phone using the "connected GPS" facility.  So I am not quite sure what your issue might be.  Could it be that your Blaze is not staying connected to your phone so that you cannot get an accurate report?

Whenever you do not use GPS, your distance is calculated using number of steps multiplied by stride length.  If this is incorrect, either the number of steps counted is wrong, or your stride length setting is wrong.

Fitbit estimates your stride length based on your profile settings.  If it seems to be wrong, it can be a good idea to change this manually by measuring your stride length and entering updated information in your settings.  Instructions here

[DLNothy]

Blaze and charge are both inaccurate. Charge only captured 2/3 of my morning walk. Started way late even though the display showed it tracking. The tech said they were aware of the problem and they were working on the solution and it could take some time. So for now both trackers are inaccurate for me.


Sent from my U.S.Cellular© Smartphone

[megkiwi]

I see you posted about the distance inaccuracy several months ago.  I just recently acquired a Blaze and mine is way off, too.  It says I went 4.15 miles when I have two other source that clocked 5.7.

A question for the other person who replied to your original post - if it is using stride to measure distance, how does it obtain that data? 

Anxiously awaiting a fix.

[FitOneKen]

I have not seen a fix for this issue, but it appears to be related to how often GPS coordinates are stored. I run through a neighborhood with a number of loops. Based on the route map that is generated, sometimes coordinates are stored when I am on opposite sides of loop. When this happens Fitbit draws a line across the loop (shorter distance) instead of showing my path around the loop (longer distance).