Blaze Firmware Release - 17.8.301.4 [Closed]

[AndrewFitbit]

9/23 Update:

See the new firmware thread here

---

9/22 Update:

For those that have the firmware update already, new clock faces have been re-enabled.

We've continued the rollout process. If you don't yet have the update, please be patient. We'll post updates about the rollout when we have more information.

---

9/19 Update:

Hey everyone - it seems like we're struggling to maintain civil conversation on this topic, so I'm going to go ahead and lock the thread. We'll open a new thread once the firmware update goes into wider distribution. Until then, here are answers to the questions that keep getting asked here:

When will I be able to download the latest update?

The update is on hold while our team addresses an issue found at the beginning of the release. Once their work is complete, we will start rolling it out again. We generally don't announce specific dates or timeframes, but you will see the update on your dashboard as soon as it is available. The only thing you need to do right now is wait patiently.

Why did you release the latest update to only a small percentage of users?

We've done tons of testing on this new firmware, but there can still be unexpected issues when we release it. If every Blaze customer updated at once, those surprises would affect everyone. Instead, we use an incremental release to observe and address issues on a relatively small scale. We definitely want the best experience possible for our Blaze customers, and a slow, cautious release helps accomplish that goal.

If only 5% of Blaze users have the update now, does that mean 10% will have it next week and 15% will have it the week after? Won't that take forever?

Nope! We aren't moving in 5% increments. We started the release at 5% and will increase it in much larger increments once we are confident that it's good to go. You should receive it soon.

Why haven't you communicated this information to customers?

All this information was previously posted in this thread, and also added to the lead post. Any time you find a discussion of an emerging issue or a newly-released update, make sure to check the first post for the latest information. We aim for clear, concise, transparent, and frequent communication - you should always find what you need in the lead post.

---

9/15 Update:

The new Blaze update is currently available only to a very small percentage of users, as we are troubleshooting some emerging issues. It will be released more widely soon. Once it is available, you will see a banner at the top of your website or mobile app dashboard. Thanks for your patience!

---

Hey everyone! 

We're rolling out a new update for Blaze, release notes below: 

• In addition to call, text, and calendar event notifications, you can receive notifications from email and other third-party apps on your tracker.Common emojis also appear. Keep in mind all notifications currently on your tracker will be deleted after the update.
• You can receive reminders to move throughout the day.
• Five new clock faces are available. Navigate to your device settings and check them out!

This release also resolves the following issue:

• Some users reported that auto-brightness was too dim or delayed.

Important to note: A sync is required after a manual shutdown or a battery drain in order to show the correct time on Blaze. This is especially important for your activity tracked by Blaze because you'll want to make sure it's associated with the current date and time.

The initial wave of users will receive the update starting September 12th, 2016, and will eventually be rolled out to everyone within a few days. If the update to the latest firmware version is not yet available for your Blaze, just hang tight!

[AGKittyHook]

SOLVED

I cancelled the update/setup on my cell phone and initiated it on my Tablet.  I also switched to wall charging instead of computer charging. The update/setup completed in 10 minutes max. Yay!

[SunsetRunner]

The latest updated has broken the GPS connection with the phone. All worked fine until I updated the device yesterday. Restarting the device and the app does not fix the problem. The device is syncing with the phone but refuses to accept the GPS connection. Extremly annoying.

[eulisef]

What is the criteria for the rollout? You mentioned it is not region based, but I honestly think you have taken too long. Almost three weeks ago you started promoting this firmware release and now that it's finally "available" it is only being trickled down slowly and with a lot of issues and bugs.

I am sure you are fully aware that the lack of more clock faces or customizations was the number one request from users since the device exists, and it appeared you covered it on this release, but it's now disabled. I am honestly really dissapointed at Fitbit and how you guys have been proving that the Blaze was not thought very well in the planning stage.Seriously thinking about asking for a refund and going all the way with an Apple Watch.

Because at the end, that is the reason this tracker exists: to compete against the Apple Watch. Try to hide it or make up fancy arguments, but that is the honest truth. So it doesn't make sense that your "premium" color touchscreen tracker does not get constant firmware updates to add features and fix bugs but most of all necessary features that are not just users whinning about but actual great improvements to the product.

[gandj3028]

I did read that but it's not just the watch faces the update has screwed up the tracker itself.. GPS signal no longer works and and I have to keep disconnecting the tracker from Fitbit and reconnecting it in order to get it to work for a little bit. The whole point is this update needs a new update to fix all the problems.

[Raviblore]

Unable to update firmware despite multiple restart of my blaze and reinstallation of fitbit for android. I dont see the uodate (pink) icon on the app

[Darmichar]

...over the next WEEK or so?!? This is my 2nd and last Fitbit product. Do you only have the bandwidth to serve up one update at a time? Did marketing catch you off guard when they announced the update a week and a half ago? I have zero faith left on this company.

[clairelaberge]

@MatthewFitbit I am in the same boat as @Timpub with the constant resetting and no function, and reported it here yesterday. Should I have received an email form?

[clairelaberge]

Never mind @MatthewFitbit. I read back and submitted a form. Might just call support in the morning. Thanks.

[boney]

just received new blaze, worked once on charger showed correct time would not work at all in case nothing now in charger will not show correct time and date{ its dead}

[CyndyFit]

I'm sure the Fitbit folks can tell their audience wants to be excited by the updates. I really hope you guys can knock this out of the park for more than 5% of Blaze users. Soon.

[Xehinz]

Hey @MatthewFitbit, any chance wether you know if this firmware update includes support for Windows Mobile 10? Can we receive notifications on our tracker aswell now?

I read that Fitbit was working closely with Microsoft to implement this after their Anniversary Update, so i'm hoping this firmware includes it.

Thanks in advance!

[dqvh.0611]

I haven't received the update yet. =(((

[Rich_Laue]

@dqvh.0611 skim through the posts above and you'll see why. 

[AnitaI]

Hey @MatthewFitbit, I updated my Blaze 2 days ago. Everything works fine except for the new clock faces. Yes, I read that they are unavailable for all users but I would really like to know how long it will take to put them back on.
I'm pretty sure there are many users out there who are as impatient as I am so it would help a lot if you could give us approx time for when the clock faces will be back. Days, ..weeks?

[CyndyFit]

Agreed! How long now?

[Steveculles74]

Hi any idea when this will all be reinstated at present I'm still showing the old clocks and notifications?

[NoKeRse]

Hi Fitibit Community and Fitbit Team!

Is anyone else seeing issues with recieving notifications from apps that were previously selected to receive notifications from and the deselected? 

For my part I tested with notifications from snapchat. Then unticked that Snapchat should send notifications to the Blaze. 

Directly after doing this I have done a sync in the app. 

But after some hours the notifications from snapchat reappears. 

Regarding the time to complete the update, I cant see why a massive load of users that wont to update their Blaze should slow it down as much as 2 hrs. I havent checked the size of the update file, but I cant be so much that is sent to the Blaze. Hopefully Fitbit will iron out the small bugs with clock faces and such soon. 

But from my point of view it seems like the earlybirds that updated is betatesters for the update. And that is not good. 

[PieMavi]

How long will it take to get to italy? I mean, it's already been three days since it was released in America wherever you guys are 🙂

[dorketh]

---

@PieMavi wrote:

How long will it take to get to italy? I mean, it's already been three days since it was released in America wherever you guys are 🙂

---

As much as I would love to have the revised watch faces and extended notifications, I would prefer to wait for the various issues to be ironed out before updating.

Having said that, if the update appears for me, I'd probably just go for it (I'm in the UK) - I've been on the MS Developer Preview programme on the desktop and mobile for a while now (with some interesting problems at times!)

[Travinator]

I havent even got the update when it was supposed to be out to days ago