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-16-2016 15:13
09-16-2016 15:13
new version support Vietnamese language???
09-16-2016 15:18
09-16-2016 15:24
09-16-2016 15:24
@AndrewFitbit That makes sense. Sometimes I need small words. I guess this is one of the times I'm perhaps lucky to be last. I think I would probably cry if my Blaze broke.
Thanks!
09-16-2016 16:11
09-16-2016 16:11
Is there any way to be part of the "Group 1" test group? I'd love to get a hold of it! thank you!
09-16-2016 16:22
09-16-2016 16:22
09-16-2016 16:29 - edited 09-16-2016 16:31
09-16-2016 16:29 - edited 09-16-2016 16:31
I suspected this would happen. The first wave had issues so they stopped rolling it out. However, the problem is that no one said the rollout fully stopped. So we've all been checking daily, expecting it will come (in my case checking the app and web browser multiple times per day) when there was absolutely no chance anyone would be getting the update. That's not cool.
09-16-2016 17:28
09-16-2016 17:28
@AndrewFitbit
>>>All - the firmware update will remain at 5% of users until we're confident that we can release to 100%. There is no exact date, but we appreciate your continued patience.
Why FitBIT did not previously clarify that the firmware update download was suspended since the problems occurred? Users are thinking that the download is on the way by random selection. Does FitBIT think that HIDING the fact is the best solution?
09-16-2016 18:04
09-16-2016 18:04
09-16-2016 19:02
09-16-2016 19:02
Releasing unstable update without proper testing is BAD.
But the way you handle the issue, hiding the fact, not making a clear explanation is WORST. It is inexcusable.
09-16-2016 19:04
09-16-2016 19:04
09-16-2016 23:40
09-16-2016 23:40
09-16-2016 23:50
09-16-2016 23:50
@AndrewFitbit
>>>@meresydotes I sort of explained in the post above, but perhaps I can clarify. Think of the 5% as group 1 and the 95% as group 2. Group 1 currently has the update, and group 2 will have to wait until we make sure we're ready to release to them. Typically group 2 will receive the update a week or two after group 1 has received the update. We want to try and make sure things go as smooth as possible when updating everyone's firmware. Hopefully that makes sense.
This explanation is confusing. It sounds like that the 5% already distributed firmware update contains NO BUG, and the remaining 95% will receive the update later.
My simple question is:
1. At this moment, have the 5% users already downloaded the update completely? If not, how many percent still remaining? Why does it take so much time?
2. When you allow the last 95% users to start downloading the update, are the first group of 5% users also required to re-download the firmware update? If the answer is YES, then you are lying... You are trying to excuse the fault of fitBIT in releasing BUGGY update in the first time.
09-17-2016 00:07
09-17-2016 00:07
If you are more gentlement by saying that the first release of firmware update which already downloaded for around 5% contains critical bugs so that it is necessary to be suspended and a newer firmware will be released after the bugs have been fixed, users will not be so anxious and furious. The more you are trying to elude the problem, the more you are falling into a deeper problem.
09-17-2016 00:10
09-17-2016 00:10
09-17-2016 00:45
09-17-2016 00:45
Sense, Charge 5, Inspire 2; iOS and Android
09-17-2016 00:58
09-17-2016 00:58
@Julia_G
>>>To be fair, I think @AndrewFitbit's information was very clear: the update was released to a small number (5% of randomly chosen users across all regions). Some issues emerged from the initial release and the update has been temporarily paused while they troubleshoot those issues.
If you think that it is clear.
So, please answer my simple question: If that is the case, why should they create the perception of "Group 1 of 5%" and "Group 2 of 95%".
If the update was suspended TOTALLY due to critical bugs, then nothing to say about Group 1 or Group 2. They all MUST download the NEWER firmware after the bugs have been fixed. So, there will be no more 95%, but 100% [Read Again: 100%] of users MUST download the firmware.
09-17-2016 01:08
09-17-2016 01:08
09-17-2016 01:12
09-17-2016 01:12
Simple question - When will the full roll out if the firmwear take place - a date would help - Thanks
09-17-2016 01:47
09-17-2016 01:47
09-17-2016 04:57
09-17-2016 04:57
I see that people have downloaded the update. But I haven´t got a notification about the update. Does it matter where you live?