09-12-2016 10:49 - edited 09-23-2016 15:17
09-12-2016 10:49 - edited 09-23-2016 15:17
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:
This release also resolves the following issue:
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!
09-12-2016 14:48
09-12-2016 14:48
09-12-2016 14:50
09-12-2016 14:50
Hi there Law541
I know that there's been some issues, but looking at the clock face that you've described, is there a way to set it as regular time vs. 24 hour military time?
Example: 2:00pm instead of 14:00
Hopefully that makes sense. This is the clock face that i'm looking forward to the most!
Thanks!
09-12-2016 14:50
09-12-2016 14:50
09-12-2016 14:50
09-12-2016 14:50
09-12-2016 14:51
09-12-2016 14:51
@bracken9422 wrote:
I finally got the update done only 3 hours to do. Only problem is no new clock faces. I'm in the UK and it's 2250 hours here. Any chance you can get the update sorted soon. Thanks fitbit
If you've done the update then you're free and clear. The rest is backend stuff that can be done without you. I don't know about you but I'm going to bed soon. I don't want to kick off an update at midnight.
Mike | London, UK
Blaze, Surge, Charge 2, Charge, Flex 2 - iPad Air 2, Nokia Lumia 925 (Deceased), iPhone 6
Take a look at the Fitbit help site for further assistance and information.
09-12-2016 14:52
09-12-2016 14:52
@chrisc76 wrote:
22.50 here in uk
No update so far
They'll roll it out over the next few days so it's not guaranteed to reach you this evening. I'd get some sleep.
Mike | London, UK
Blaze, Surge, Charge 2, Charge, Flex 2 - iPad Air 2, Nokia Lumia 925 (Deceased), iPhone 6
Take a look at the Fitbit help site for further assistance and information.
09-12-2016 14:58
09-12-2016 14:58
09-12-2016 14:59
09-12-2016 14:59
09-12-2016 14:59
09-12-2016 14:59
09-12-2016 15:02
09-12-2016 15:02
09-12-2016 15:02
09-12-2016 15:02
Downloaded the update and saw all five of the new clock faces, as well as the original four faces on my iPhone 6s with iOS 9.3.5. All was working well for an hour or so. Then tried to change to a different clock face on my Fitbit mobile app and found that all of the clock faces, both old and new, had vanished--there was only an empty screen where the clock faces should have been. Now at my iMac v. 10.11.16 and only the original clock faces are visible for selection. All five new clock faces have vanished from the clock face selection set. Reminderes to Move feature is still there. Have restarted my iPhone (Hard start), with no improvement. Can I download the upgrade again, or is it buggy yet? Please advise, Moderator. Thanks.
09-12-2016 15:11
09-12-2016 15:11
As stated elsewhere, the update is fine but some people got it earlier than intended so the roll out of the back-end srevives hasn't been as seamless as planned. They'll catch up with reality eventually I believe but you shouldn't need to update the update you've already got as far as I understand it
Mike | London, UK
Blaze, Surge, Charge 2, Charge, Flex 2 - iPad Air 2, Nokia Lumia 925 (Deceased), iPhone 6
Take a look at the Fitbit help site for further assistance and information.
09-12-2016 15:14
09-12-2016 15:14
09-12-2016 15:16
09-12-2016 15:16
09-12-2016 15:17
09-12-2016 15:17
@MatthewFitbit so for now I should take it off the charger and let it die? Darn, there goes this week's weekly step challenge but entirely my own fault for rushing to update as soon as I saw the update available all excited to try the new stuff. I have it on the charger, tried doing the 2 button reset, on the app it's reverted back to the 4 original faces but the unit itself is still stuck in an infite reboot loop, even as it sits on the charger it doesn't matter, it'll boot up, maybe last a minute and reboot itself, repeat ... forever. I guess I'll take it off the charger and just let it die and stand by to hear from your support team soon. Thank you for your hard work!
09-12-2016 15:18
09-12-2016 15:18
09-12-2016 15:19
09-12-2016 15:19
09-12-2016 15:27
09-12-2016 15:27
09-12-2016 15:31
09-12-2016 15:31
@Timpub that's my EXACT concern - I'm cool with standing by and appreciate @MatthewFitbit's help very much but that unit resets itself so quickly that I'm REALLY hopeful that when we try to ask it to do a firmware "upgrade" or "update" or "swap" or whatever it is it'll commit to that and not crash as it attempts to, completely bricking the tracker in the process. That would be sad and I'm hopeful that won't be how it is / as soon as it starts the update it won't be in a state of auto-crash/auto-reboot infinite loop anymore.
09-12-2016 15:32
09-12-2016 15:32
It might be. The final release of IOS10 doesn't come out until tomorrow.