Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Blaze Distance Measurement is Inaccurate

Replies are disabled for this topic. Start a new one or visit our Help Center.

I have been testing the Blaze vs the Surge on my last two walks. The Blaze is not reading distance correctly using Connected GPS. Here are the detailed results from the last quite slow walk.

 

Unit              Blaze    Surge           Notes

Time             41:50    41:42.22      I pressed the two starts and stops within 0.5 sec

Dist               2.59km 2.20km        The 2.20 is accurate - on both walks the Flaze was well over

Avg Pace      16'07"   18'55"          The surge is closer

Hrt Avg          86         80

Steps             2953     2920            The surge step counting is a little erratic

Elevation       36.57    36.57

 

My phone is a Samsung S5 running Android 5.0

Best Answer
0 Votes
135 REPLIES 135

I'm not teaching the theory of it all just trying to give a basic course without getting into a deep technical discussion about it all. I know all about triangulation and such as I worked on Radar, Tracking and Navigation  all the other cool goodies that tell a Navy Carrier Battle Group where everyone is, was and need to go. I was just trying to keep it basic and illustrate possibly one explanation. Yes you are right that you need at least 4 for Triangulation as you stated.  

 

On that note It's time to head for the gym you guys have at it. Good luck. 

Best Answer
0 Votes

Great, so you probably know that triangulation is an inferior term to trilateration for this discussion ...

Best Answer
0 Votes
Pedants, there's always one. 😉
Best Answer

@DavS All my testing is done from starting the exercise from the Blaze, not the app. I wait until I see the gps connection on the blaze, then start the watch and Endomondo on my phone at the same time.

 

I did a 5k run this morning.EndomondoFitbit

 

Both are using the same gps signal. There is a 0.1 mile difference between the blaze and endomondo. However, as you can see on the map, that difference came up at the start of the run and stayed constant the whole time. For some reason, there was a glitch on the blaze. Other than that glitch, I think accuracy is pretty good, at least for use with my phone. I have an original Nexus 5.

 

The current pace shown on the blaze seemed ok but not very precise. It's hard to validate because it's not stable at all on endomondo either. If my main goal is to have a very accurate current pace, maybe a phone gps won't cut it. I love the blaze and fitbit in general, but I'm not sure it's aimed at runners who want to improve their pace.

Best Answer
0 Votes
@SunsetRunner Sorry but no. Just highlighting that if one asserts 10% variance in GPS accuracy is expected and acceptable then one doesn't know flip from flop and should not be misleading nor discounting the very real issues experienced with the device.
Best Answer
0 Votes

Regarding GPS errors, keep in mind that many phone apps will process the raw GPS, "smoothing" the data which (usually) results in a cleaner and more accurate track. 

Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze

Best Answer

I just repeated the same walk this morning that I did yesterday, initiated from the "walk" exercise on the Blaze. I had increased my stride length by 8" to see if that had an impact on the distance reading.  I made sure I had a good connection to my phone prior to starting, and today is a clear day. My Blaze ended up logging 0.73 miles (should be 0.98), so it is still coming up short on the distance even with the change in the stride length.

 

Walk 3 Blaze adjusted stride.PNG

Later today I am going to repeat the walk but initiate it from the "run" exercise on the Blaze to see if that makes any difference. It is interesting that some people are getting shorted on distance while others have the Blaze showing increased distance. That is why I was curious to see if the stride played any part in the variability.

 

Best Answer
0 Votes

@DavS This is interesting and may point to an app-Blaze communication error rather than the Blaze only. I get a reliable 10+% over distance no matter the stride length and I get 10+% on a bike ride too.

So, I am running Android 5.0 on a Samsung S5. What phone/system are you running?

Best Answer
0 Votes
@MuzDownUnder I am running Android 5.1.1 on a Samsung S6.
Best Answer
0 Votes
This thread got me wondering so I checked mine out today.

Before I left, I ran the route through Google maps. It says it's 1 mile.
After walking it, my Blaze reported .99 miles.
My cars trip meter reported it as .9 miles.

Not the best test in the world but I'm not showing any crazy differences...yet.
I might go to a local track later this week since that has each mile marked off and see what I get there.

I'm using an LG G4 with android 6.0. All day sync off. Notification widget on. Stride length set correctly.
Best Answer
0 Votes

I have emailed Fitbit at https://contact.fitbit.com with this version/app error idea so I await any response.

I have also suggested someone from fitbit join in this thread to show everyone that they are not just ignoring the problem. 

Best Answer

@MuzDownUnder Thanks for sending the email to support!  I think it would be a great idea to have a fitbit employee join the thread. So far my Blaze is consistently showing about 25% less distance than actual when I initiate the exercise from the device. Maybe there is something wrong with my Blaze, but it seems as though enough people are having problems with this that they should be investigating this. I will probably email support as well once I have finished all the rest of the "test" walks I want to do. 

Best Answer
0 Votes

Ok, so I just did the walk 2 more times. The first time, I initiated it from the Blaze in the "Run" exercise tile. Prior to this, I had only entered in a walking stride, since I'm still not at a point where I can run. I had updated the walking stride prior to this morning's walk to see if that made any difference in the distance measurement (it didn't). I thought that I should probably put something into the running stride, so I put in a number that was the same as the walking stride (currently at 3.3 feet after increeasing it this morning). I then went on the walk and got a distance of 0.92 miles (actual distance is 0.98 miles). This is considerably better than the 0.73 miles I got this morning.

 

Run 1 Blaze adjusted stride from 0 to 3.3.PNG

 

Immediately after I completed the above walk, I stopped, initiated a walk from the Blaze using the "walk" tile and got the following:

 

Walk 4 Blaze (walk & run stride at 3.3 feet).PNG

 

While it is still off, it is better than the 0.73 from this morning. I'm not sure what any of this means. Did putting something into both the walking and running stride settings improve the readings? I may clear both of those out and try it again later this afternoon. All I can say for sure is that I get inconsistent readings when I initiate a walk from the Blaze compared to doing it from the fitbit app.

 

Best Answer
0 Votes

The reply I have from Fitbit is

 

"Thank you so much for letting us know about the details of the issue you're experiencing.

Rest assured that the issue has already been brought up with our product specialists and our engineers are hard at work in fixing the issue."

 

It would have been nice if they had told everyone here that they are even aware of a problem

Best Answer

@MuzDownUnder That kind of sounds like a canned response, but I hope they are taking it seriously and working on a solution.

 

I did another couple of walks today. For the first one, I wasn't getting a good connection between my Blaze and my phone, and it didn't end up using GPS data (at least I didn't get a route plot). I discovered that somehow my phone was set to "GPS Only" instead of "High Accuracy". I changed this setting and was able to get a good connection, so I did another walk. During both of the walks, I had SHealth running as well, and both walks gave me the same distance of 0.97 miles. My Blaze gave me distances of 0.8 miles (the one without route data) and 0.82 miles (seen below).

 

Screenshot_2016-03-10-12-29-51.png

Walk 5 Blaze (walk stride at 2.75 feet, run at 0).PNG

 

I am still getting somewhere between 15 and 20% low on distance measurements initiated by the Blaze, using the connected GPS. An interesting thing is that even though the two plots above should look identical (presumably using the same GPS signal), there are some differences. Maybe it's because SHealth is using thicker lines, but that is something I'll have to investigate.

 

Best Answer
0 Votes

Hi All

 

An update to all having similar problems. After a string of emails to Fitbit support (about 70% of which only got canned answers) we made small progress. Fitbit decided the Blaze must be faulty and sent me a replacement. This one has an identical problem. I tried the Blaze on another phone with a different operating system with exactly the same result.

Fitbit did admit they couldn't duplicate the GPS problem but that is as far as we have got.

 

What fitbit need to do is

1) Assign one member of the "fitbit support team" to a case. Every time I email I get a different person answering the email and it is obvious that they do not know any of the history. This is very frustrating.

 

2) Create some system where they can put me in touch with the development team so we can actually make progress on finding out what the problem is. I have eliminated the Blaze and the phone so I am only left with my location in the world or some other obscure issue. I am more than happy to work with the development team. If it is a location issue you need people in other locations to test for you.

3) Stop sending out the really annoying canned answers to emails that are trying to help. Not good PR fitbit.

 

@EmersonFitbit I hope you get this and can do something constructive with it.

 

I await a constructive reply.

MH

Best Answer

Fascinating threat.  I saw this because I'm having the opposite problem.  My Blaze is always 3% short on distances.  My Surge was always spot on.  There is a 3.00 track I did this weekend.  One loop with my Surge, one loop with my Blaze connect to my iphone 6s. 

 

Surge was 2.97 miles off by 1%.   Blaze was 2.92% off by 3%.  Every single walk I've taken with my Blaze has been short.  Interesting that you guys are seeing longer distances...

John | Texas,USA | Surge | Aria | Blaze | Windows | iPhone | Always consult with a doctor regarding all medical issues. Keep active!!!
Best Answer
0 Votes
@JohnRi
I am seeing shorter distances like you. The Blaze is always between .12mi and .25mi short. My average pace is always 30s to 34s slow when comparing to Runkeeper. In order to eliminate the variable of another Galaxy S3 based app simultaneously using GPS with Blaze fitbit connected GPS, I used my Polar watch & GPS arm band combo (I know it's older, but it is still accurate). The Blaze exhibits the same shorter distance and slower pace discrepancy range when compared to my Polar device stats. Btw, there is less than .06% variation between Runkeeper and Polar mileage and avg. pace.

(Additionally, I know I'll have to find another forum thread for thus issue, but I'm experiencing a great amount of wear on the Blaze's plastic housing. It's not the band and this is not a good sign!)
Best Answer
0 Votes

I have had the opposite experience. I ran today and last weekend and the distance on my Fitbit Blaze was way short. 

 

Last week

Blaze: 3.36mi

Actual: 3.82 mi

 

Today

Blaze: 2.3 mi

Actual: 3.1 mi

 

Anyone else having issues with the distance being short?

Best Answer
Glad to see I'm not the only one with distance issues. On Friday I did a ride that I know was 44km and this was confirmed by all my other mates using Garmin and yet The Blaze reported it as 50km. Then when I synced it to Strava it reported it as 44km.

On Monday I did a 29km ride. The Blaze was saying 16.8km and when uploaded to Strava it said 52.8km.

So clearly Fitbit has a distance problem that needs to be fixed! Otherwise I guess I will be taking mine back for a refund given I bought it primarily for riding.
Best Answer
0 Votes