Blaze Firmware Update - 17.8.200.3 [Closed]

[AndrewFitbit]

Update 5/6/16:

Hey all,

I've been keeping a close eye on this thread, and I wanted to give a quick update.

For reports of Blaze steps and/or distance being inaccurate, I think this is definitely something worth looking into. I've passed on all the feedback to our team so they can investigate. As a friendly reminder, remember that accuracy depends on many factors.

Here's a couple things being worked on:

• Excess Calendar Notifications
• 'Auto' brightness setting is too dim or adjusts slowly

For 'Auto' setting being too dim, you can switch to 'Normal' as a workaround in the meantime. Please note switching to 'Normal' will have a slight impact on battery life.

I'll provide updates when I can. Thanks everyone. 🙂

Update 4/27/16:

The firmware update should now be available to everyone. Update your Blaze and let me know how it goes! You can read the release notes for version 17.8.200.3 in the lead post or check them out on our help site. 🙂

Update 4/23/16:

Sorry for the wait, here's the release notes!

"The Simplified Chinese, Japanese, and Korean languages are now available on Blaze. Note that Blaze is only available for pre-order from fitbit.com in China, Japan, and Korea.

This release also resolves a couple issues:

• Some customers were unable to resume a paused FitStar workout.
• Some customers reported problems with the Blaze screen (display)."

You can find these release notes for this update (17.8.200.3) on our help site.

4/21/16:

Hey everybody,

Some of you may have noticed there's a new firmware update for Blaze! We just started pushing this update out yesterday, and just like any other update, we'll be rolling it out in waves. This update focuses on a few bug fixes. Release notes will be posted here soon.

Thanks!

[Fands]

the only way to get an answer to corvette's question is to post this to their facebook page...they respond within a couple of hours--those that monitor the fb posts will be made aware, maybe it become apparent through negative posts on their advertsing fb page.

[Robofit]

Thanks. I had seen that in the past but Wasn't sure what it was. I'll have to pay attention but I would still prefer a percentage as you have to pay attention, especially if traveling.

Sent from my iPhone

[bmiller1969]

Well since it's been since April I'm beginning to wonder if it will ever
happen.

[Rich_Laue]

@Robofit as @Fands says swipe to any a reen but the clock and you will see tyr battery indicator. It will turn red when the battery geta to a critical low level.

[goosey]

the app is the problem I have to keep redoing the same miles over and over again. Mt phone says I have 42,000 steps but my wrist says I have49,831. If I sync it it will go to 42,000. I called them and they said it was the app. They gave me a case number not that is going to do me any good

[bmiller1969]

Yes they gave me a case number and said to just be patient. Patience
running out.

[Rich_Laue]

@goosey lately i also am seeing screwy step or miles after a sync, sometimes it too also just shows the cached numbers and not the updated totals. If i wait a minute and sync it usually straightens out, otherwise in an hour it is correct.

@bmiller1969 i might be missing somerhing, are you having an unmentioned problem that we might be able to help with?

[bmiller1969]

I have been in contact with you guys for about 2 months with my steps and
miles being off. Today mine shows 14941 steps and my friend who has a hr
charge shows 18783 and we have been together all day. We walk each night
and hers always shows at least mile difference. It never matches with my
fitness app on my phone. I was finally told on the phone that it was a
problem with fitbit and to just be patient. I hate to be ugly but my
patients is running out.

[Liztrailblazer]

Hi there! Has there been any further progress with this.. Have noticed only over the last 3 weeks that my blaze will stop counting steps and seems to freeze... Odd though as the heart rate monitor still seems to work.. Then it doesn't sync properly and often my app has a different step count to my watch!! Not good when you are competing against friend in the step count!!!! Lol. As long as I know it is being fixed/ looked into I can cope... Love my blaze!!

[bmiller1969]

Could we get an update on what is being done to correct problems?

[AVM]

My Blaze just froze after 1 week of use. It had the latest firmware!!

I see a lot of people are facing the issue of Blaze getting stuck up. Please identify the issue and release an update for it.

Hope to hear from FitBit about this issue very soon.

-AVM

[jharla1]

---

@AVM wrote:

My Blaze just froze after 1 week of use. It had the latest firmware!!

I see a lot of people are facing the issue of Blaze getting stuck up. Please identify the issue and release an update for it.

Hope to hear from FitBit about this issue very soon.

-AVM

---

I've had it freeze on a handful of occasions.  Maybe 3 to 5x.  Usually it was because I was asking it to do many things at once (such as syncing after setting an alarm, and also trying to scroll through the options on the watch).

Was just a simple matter of either letting it recognize the error itself and it reboots, or force it to by holding the buttons on the left and bottom right for 10 seconds to give it a nudge.

I don't find it annoying given it has happened so infrequently.  No different than having to reboot my phone or restart a browser.

Were you able to get yours restarted and working again?

[AVM]

My Blaze is constantly having the issue. It freezes even after I restart it.

Even the Heart Rate LEDs stop blinking and I can't go to anyother screen, stuck at clock.

-AVM

[jharla1]

---

@AVM wrote:

My Blaze is constantly having the issue. It freezes even after I restart it.

Even the Heart Rate LEDs stop blinking and I can't go to anyother screen, stuck at clock.

-AVM

---

I didn't look over your other posts, so don't know if you contacted support or not.  Sounds to me like if you reach out to them they'd send you a new device.  Just seems like you got a bad one.  This is certainly not the norm for it.  I've had mine since launch day, and as I noted other than a handful of times where I was trying to get it to do 5 things at once don't run into this issue.

[AVM]

Just contacted support. They told me that they will be shipping a replacement device. I hope they send a new unit and not a refurbished one.

-AVM

[jharla1]

---

@AVM wrote:

Just contacted support. They told me that they will be shipping a replacement device. I hope they send a new unit and not a refurbished one.

-AVM

---

Don't know if there is any way to tell.  But glad they were responsive and prompt (as they usually are).  For the majority, the Blaze has been a great device.  Unfortunately you're on the support page where those with issues of course post them.  It's an incomplete look at how well received the device is.  Judging from my interaction on other message boards and personal experience (gifted quite a few Blaze), it's a great Fitbit and hopefully the new one will work as you expected.  Good luck!

[AVM]

Thanks! I hope I don't face these issues again.

[jharla1]

---

@AVM wrote:

Thanks! I hope I don't face these issues again.

---

You hopefully won't.  Again, exception, not the norm.  You just got a lemon.  It happens.  Don't let the support board make you jaded.  There are many many more people happy with the Blaze than not satisfied.  Best of luck again with your (soon to be) new Blaze!

[Corvettekid]

"You hopefully won't.  Again, exception, not the norm.  You just got a lemon.  It happens.  Don't let the support board make you jaded.  There are many many more people happy with the Blaze than not satisfied."

That may or may not be true.   Too many people are reporting the Steps/Distance accuracy problem for it to be a rare glitch.  It seems to be the NORM.

If it was a production glitch, then Support would have said anybody with a Blaze that is off should send it in for a replacement.  Instead, we have been told that a firmware/software fix is coming.

We are not talking about something that should be 100% accurate and instead it's at 97% accuracy.  We are talking about brand-new Blaze's that are only registering 70-75% of steps/distance.

I have walked on a track and found it is meauring 0.18 miles instead of 1/4 mile.  That is 72% accuracy. That is WAY off.....unacceptable.

I don't know why a fix is taking this long.  Either support is wrong and they are NOT working on a fix or something is screwey that a fix takes this long on a basic steps/distance counting algorithm that apparently earlier and simpler FitBit devices had no problem counting.

[jharla1]

---

@Corvettekid wrote:

"You hopefully won't.  Again, exception, not the norm.  You just got a lemon.  It happens.  Don't let the support board make you jaded.  There are many many more people happy with the Blaze than not satisfied."

That may or may not be true.   Too many people are reporting the Steps/Distance accuracy problem for it to be a rare glitch.  It seems to be the NORM.

---

I disagree in that I have gifted several Blaze.  Hasn't been an issue.  Keep in mind they have sold millions of devices.  How many have posted on this board about an issue?  It's a very small number in the scheme of things.

Of course that doesn't mean that everyone with a problem has posted here.  I'm sure that's far from the case.  Overall though I suspect it's a minor amount of affected devices just basing it on my experience.

Folks posting "My Blaze works perfectly!" wouldn't do any good on a support page.  And I'm hesitant to post as such because I get met with the few that are affected with how wrong I am.

I can only speak on my device and the several I have purchased for others, not to mention my interaction on non-support boards with fellow Blaze users that don't have the issue.

I don't know the particulars of your case.  If they are telling you repeatedly it's a firmware fix, I'd stick to my guns and tell them you want a new device, and I imagine they will send it.

Good luck with your Blaze.  When you get one that works well, it is a great tracker.  Hopefully your situation will be rectified soon!

(edited some spelling and still probably left some errors in)