Proof GPS distances, split times, and pace are WRONG on blaze

[JohnRi]

I was a Surge user, I love everything about the Blaze more, except for two things.

I hate that there isn't a dim mode on the watch and having to turn it to see the time, is annoying.  Similar issue, when the alarm goes off, why doesn't the screen just come on?

But my biggest complain is the GPS tracking is just wrong.   Here is the proof.

Setup - iPhone 6s, running ios 9.2.1, firmware 1.23.00

Mapmywalk Build 16.2.3

Fitbit app 2.20 (173)

Fitbit Blaze Version 17.8.102.7

As far as I know there are the current versions/build of the hardware and software.

I had the Fitbit app running, and I opened Mapmywalk.  I started a walk, then I put my phone into my belt pouch, put the pouch on, and put my water bottle on my belt.  This took approximately 1 minute. Then I started an exercise on my fitbit, for a walk, and had 4-5 bars on the GPS and started a walk. 

I then walked 1/10 of a mile to the local park in my neighborhood, and started walking a approximately 1/4 mile oval track until my Blaze showed I walked over 4 miles.  I then walked home and stoped my fitbit, and the mapmywalk app.

But the fitbit app and mapmywalk are using the SAME GPS on my phone to calculate distance traveled.

Mapmywalk

Distance traveled 4.36 miles

Durantion 1:25:39

Pace 19:37

Splits

1 mile 20:40

2 mile 18:50

3 mile 18:32

4 mile 19:33

4.37 mile 21:24

Blaze

Distance traveled 4.22 miles

Durantion 1:24:34

Pace 20:02

Splits

1 mile 20:45

2 mile 19:37

3 mile 18:55

4 mile 20:11

4.22 mile 23:01

So you can clearly see that the Blaze is wrong.  Which agrees with the numbers from my Surge.

Since both are using the SAME GPS system, they should be identical. 

I don't know what is wrong, but I'm not happy...

[Dominique]

---

@JohnRi wrote:

and started walking a approximately 1/4 mile oval track until my Blaze showed I walked over 4 miles

---

One thing comes to mind: many GPS systems are known not to perform optimally when moving in circle. If you want to do some further testing, you may want to do it by walking from A to B.

I have a standard routine that I’ve been doing 2-3 times a week for the past couple of years and looks like this:

 

The distance is consistently the same (8 km) with the Surge’s GPS, my running app (Runtastic) using my Android phone and now the Blaze (using Fitbit app and same phone). It’s not a straight line, but it’s not circular either. Moving in circles on a short track is not the optimal setup for testing GPS.

[JohnRi]

I walk a huge number of different tracks around the Houston, and Texas area. 

My first walk was on a 2.75 mile long straight course last Saturday.  My Surge would show 2.85 miles on this course.  My Blaze showed 2.60 miles.  I walked a 3 mile loop, that's really a large triangle.  My Surge shows it at 2.99 to 3.01 miles.  My Blaze, 2.90 miles both time I made a loop there.

I walked another course with the two loops that combined are .75 long on my Surge, and on Mapmywalk.  Blaze showed .70.

I did the walk yesterday due to weather.  I wanted to be able to get home in a hurry if it started raining.  So I walked the track behind my house. It's small, and flat. but short.  I prefer larger courses.  Gets boring walking in circles a million times....  I think I did 16 or 17 laps yesterday...

I've contacted support, and they suggested something ODD.  They suggested that the shortage is because I haven't set my stride length.  I could accept that, IF my Surge showed the same distances as the Blaze does.  But the Blaze is always short.  But I suppose the Blaze might take your step count into distance calculation, more than the Surge did.  Stupid, but maybe they did that because the GPS tracking isn't accurate.  But I've seen biker riders on the forum complain that the distances are wrong too.  I've also seen a few others complain about running and walking distances wrong with the Blaze.  So I'm not alone.  One guy was comparing his Polar to the Blaze, and it was off by 1/2 a mile.

But just in case I'll visit a football field this weekend, and I'll walk 50 yards a couple of times, and get a step count, and update my stride length.  Then I'll walk the 100 yards a couple of times with my Blaze, and then I'll walk the same 100 yards with my Surge.  I'll use mapmywalk too. 

I'm willing to bet the Blaze will be short.

[nfolsen]

I am with you on this issue, John.  I contacted Fitbit because my Blaze was recording distances way off, though my map route was drawn perfectly, so I know it had nothing to do with losing GPS signal.  I have been back and forth with customer support, who told me that when you track an activity like walking or running, it should calculate your distance based on what the GPS records, and not number of steps.  I believe it was only going off my number of steps (which is short since I am typically pushing a stroller).  I asked two different reps this same question for clarification and they both said it will use the GPS points to record distance unless it loses signal, in which case it uses steps.

After more back and forth, they said I should send my Blaze back for a replacement.  No surprise, but my new Blaze is having the same exact issue.  

I was wondering if you're still coming up with discrepancies in your statistics or have had anything resolved in all your dialog with customer service?

[Charles.K]

I have the Surge and even though it is becoming outdated in styling and presentation, the Blaze is not its replacement.  I have had the Blaze for several days now and even though it has some nice features the Surge is just a better fitness watch overall... for now.

My key concerns with the Blaze are:

1. Display is not continuously lit.  During the day I just like to casually glance and see what time it is without having to gesture my hand or push a button.  This is an issue when you are timing certain exercises and the display blanks out as it does with the Blaze.  If you are doing planks, you have no free hands to push the button or gesture.

2. No GPS.  At first I thought this was moving with the times as everyone takes their phones... almost.  The setting up and lack of accuracy is not good.  The accuracy of my Surge is excellent and consistent.

3.  The Blaze is lighter but the band is not as comfortable as the Surge.  I probably should try some other bands.

4.  For 2016 the display is small and can be hard to read and ergonomically there is no excuse for this now.

I will be returning my Blaze as it is nice, but really does not meet my needs.  I will keep using my Surge until the next update or may just move to Garmin.

[patrickbell]

Hello -

I'm experiencing the same issues as you've described.  I've installed the latest upgrade for Blaze about three weeks ago.  I sync the Blaze with the GPS on my phone (the phone app has the latest app version).  I run 5 to 6 miles.  During the run, I've noticed the distance on the Blaze is .5 miles behind the distance on the app. The distance on the app is correct.  The steps on the app is correct.  The calorie burn on the Blaze is accurate, but the distance is totally off....again, by about .5 miles. 

I ran 5 miles this morning and it seems to be getting worse.  The Blaze was 2 miles off and recorded twice as many steps as I normally average for a 5 miles run.  I have no idea what to do about this.

[OleMarius]

Here are my experience. logged alot. Ive compared many runs with Google map log, and fitbit log. Odd part is Fitbit use actuely mapping from Google.

Its off by several km every single jogging tour ive had