04-21-2016 12:12 - edited 09-12-2016 10:52
04-21-2016 12:12 - edited 09-12-2016 10:52
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:
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:
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!
04-27-2016 11:46
04-27-2016 11:46
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. 🙂
04-27-2016 13:37
04-27-2016 13:37
04-27-2016 13:49
04-27-2016 13:49
@AndrewFitbit wrote: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. 🙂
The update seemed to go fine, although it took over an hour, rather than the "up to 10 minutes" estimate given. Just a heads up for others. Phone and tracker on chargers next to each other and within a few feet of my router, so neither WiFi nor charging were issues.
04-27-2016 14:15
04-27-2016 14:15
04-27-2016 14:35
04-27-2016 14:35
My Blaze updated in about 15 minutes as well. No problems.
04-27-2016 14:49
04-27-2016 14:49
04-27-2016 15:03
04-27-2016 15:03
@hawkyou wrote:
Still no new clock faces or reminder to move. Amazing!
@hawkyou All in good time my friend, just be on the lookout for future updates.
@nlmux In some cases it can take a few tries before updating successfully, but it shouldn't take that long though. Usually when I notice a firmware update getting 'stuck' or taking too long, I'll start the update process over again. Sometimes a restart of the tracker can help too.
@TechJunkie Glad to hear it!
@Markii Setting stride length will only affect your distance. You can check out the post I made here about accuracy, or you can check out the suggestions from @DavS and @TracyV125 from earlier in the thread.
04-27-2016 15:05
04-27-2016 15:05
04-27-2016 15:52
04-27-2016 15:52
04-27-2016 16:22
04-27-2016 16:22
04-27-2016 16:23
04-27-2016 16:23
04-27-2016 16:45
04-27-2016 16:45
I noticed that both @hawkyou and @TechJunkie reported their update taking ~15 minutes. I have a concern about this as my phone has a tendency to sleep if not active use on about 2 minutes. Will this impact the update as I do not have the Dongle with me and I am traveling for work.
04-27-2016 17:12
04-27-2016 17:12
@dumont6666 wrote:
When will you do a REAL update with new features?
@dumont6666 I would imagine this question is on most, if not everyone's mind. As I said to @hawkyou, be on the lookout for future updates. Our team is working hard to bring new features to Blaze, and we just have to be patient.
@pmlp I'd say try it again, it should work now.
@Andhanni If your phone goes to sleep, the update should still work as long as the Fitbit app is running in the background. For example, I have an iPhone 6s and firmware updates work just fine for me if my phone happens to go to sleep during an update.
04-27-2016 17:15
04-27-2016 17:15
04-27-2016 17:45
04-27-2016 17:45
@Andhanni wrote:I noticed that both @hawkyou and @TechJunkie reported their update taking ~15 minutes. I have a concern about this as my phone has a tendency to sleep if not active use on about 2 minutes. Will this impact the update as I do not have the Dongle with me and I am traveling for work.
I have an iPhone 6s and the screen when off and locked while updading with no issues.
04-27-2016 19:59
04-27-2016 19:59
Any chance on an update to the "POP" screen on the blaze... it cuts off the very bottom... so you miss a little bit of each number....(time)
04-27-2016 20:03
04-27-2016 20:03
@JeromyL It does cut off the bottom of each number, but it is actually designed this way.
04-27-2016 20:34 - edited 04-28-2016 07:19
04-27-2016 20:34 - edited 04-28-2016 07:19
12 minutes in Australia from the PC dongle via WiFi into my network and using the computer at the same time..
No dramas, all of my previous settings remained intact...
04-27-2016 23:50
04-27-2016 23:50
Hi, Does the update have impact on the design of the POP Watchface ?
Before the update when my HR was under the fat burning zone the heart in the middle was empty.
When i was gettin into the fat burning zone it changes its colour to fully red.
Now its all time fully red - is this a bug or a feature ? 😛
04-28-2016 04:14
04-28-2016 04:14