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!

[gbailey]

Is anyone else having issues just doing the update?   Mine is charging right next to my phone and the update has failed multiple times with no indication of why.  Bluetooth is on, WIFI connection is up and running.  I have rebooted my phone multiple times.   Help!

[bpsrun]

My update took over 90 minutes this morning. Galaxy S7 Edge, strong wifi the whole time and phone sitting right next the watch. Rediculous.

[robguitar]

Mine was completed in about 10 minutes. No problem so far.

iPhone 6S

[MOHAMMEDR]

What about the Arabic language???

[Rich_Laue]

---

@gbailey wrote:

Is anyone else having issues just doing the update?   Mine is charging right next to my phone and the update has failed multiple times with no indication of why.  Bluetooth is on, WIFI connection is up and running.  I have rebooted my phone multiple times.   Help!

---

@gbailey after the update finished and you noticed problems, did you try the recommended restart procedure?

[PJ007]

I got the firmware update last night. (17.8.200.3)  Update worked quickly and I have found one thing that definately works now that did not work before.  I have a Samsung Galaxy Note 5 which for some reason was not listed on the supported devices list.  Prior to the update, I would only receive text notifications. Now I am receiving call notifications.  Not sure yet about calendar notifications, but if that also works now I will be ecstatic.  Since the update notes indicate a fix to the display, I have just changed my clock face to POP to see if it has fixed the cut off letters issue.    NOPE!  Still the cut off letter issue.  Hope that comes along next with the move reminders!!!!  For now I am happy with my phone call notificatons working 

[Vaya1989]

Hi, what about the heart symbol of your POP screen - is it filled or not filled ?
Means is it everytime fully red or not ?

[Ammin]

This has happened to me as well after yesterday's update.  It's abosultely ridiculous that the steps aren't being recorded accurately - I didn't pay $250 CAD to have only 70% - 80% of my steps recorded.  

[meresydotes]

Has everyone having problems after the update restarted their trackers? Hold in the single button and bottom button until the fitbit logo comes on.

[Vaya1989]

Just want to say that the number of steps doesnt have impact on the calories burned ^^

[Mikeyb50]

I was hoping the update would allow Android to answer/reject calls like ios, it's a shame that the same features are not available across all platforms ios, Android and windows although they are still to be commended for attempting such a feat

[yamaf15e]

This update took 2 hours and 10 minutes...not only that, but by it taking so long, and using both my phone and Blaze to do so, was unable to log any steps! 

Moderator edit: format

[Fosse66]

I went ahead and updated despite reservations (if it ain't broke) - took 10 minutes using my iPod.

It seems to have affected the auto brightness levels - it will still adjust brightness, but is definitely dimmer than before under the same conditions.

I may set it manually instead. I still love the Blaze.

[AZPete]

My Blaze has been working fine out of the box, so I skipped the last two updates. Didn't see anything reported in either one that would benefit me.

[SunsetRunner]

Gave up after 2 hours. All previous updates have also taken over 2 hours, last one a week or two ago took 3 hours. I have strong 4G around here.

Updating direct from PC app with wireless dongle seems to be faster, but still not 5-10 minutes like it says. It's been 20 minutes and it is about 40% complete. This is on a 20Mb/s fiber connection at a business.

EDIT: It took about 1hr from start to finish with USB dongle. My Charge HR always used to update fast, but not the Blaze

[Enjoytodaytoday]

My blaze has stopped tracking floors since the update. I have gone upstairs 7 times since the update. It still says 2. The number of flights I had prior to the update.

[Nocturnx]

I just did the update and it took about 5 minutes.  I'll test step and stair count and see what I get for accuracy.

[Nocturnx]

@Enjoytodaytoday  Have you tried resetting it by holding in the left button and bottom right button until the fitbit logo displays?

[Hockeycrew]

Updated on Iphone 6 this morning.  Took about 10 mins.  Love the new "auto calculate stride" feature on the Blaze!!   

[Nocturnx]

So I just went and counted taking 211 steps and went down a flight of stairs and up a flight of stairs.  The Blaze had me at 2,330 steps and 5 flights of stairs before and 2,531 steps and 6 flights of stairs afterward.  So it was pretty accurate on my Blaze and then I synced it to the fitbit app on my phone and it changed my step count down to 2,501...  Not sure why it made this adjustment but that killed the accuracy.  Any idea why it would do this?