Blaze Firmware 17.8.301.7 - Thanks!

[muppetman]

I just wanted to say thanks!

I updated today and it's working great.  Notifications are fantastic now (I was using a 3rd Party App, but I no longer need it now)

I'm just so sick of reading all the negative comments on here, I just wanted to say thanks because I'm actually a happy Blaze user.  I knew what I was buying before I bought it, so any additional features are welcomed as far as I'm concerned, not something I'm entitled to.

I love the new watchfaces too!!

Moderator edit: content

[SunriseRun1250]

so the picture of the battery is larger which is nice but do they have a percentage shown? (I know people have been asking for years). Shame there isn't any news of a % on the blaze itself. 

[Rich_Laue]

Fitbit does have a beta program, and the update has been thoroughly tested. What was not tested and could not be tested is will there be any problems with felt very of the final release.
Fitbit chooses 5% to test and hopefully prevent past problems. Unfortunately it would do it was discovered a problem when the clock faces were released with the update. Fitbit now to work on what what happened and why and then proceed to create fix.
The moderators have been doing a good job in keeping us informed, maybe not at the rate desired, please remember that the moderators are not developers and are only able to pass on information that is shared with them.

Now if you where in the beta group you roil know, since you would have known since a NDA would have been signed.

[Rylan]

---

@Rich_Laue wrote:
Fitbit does have a beta program, and the update has been thoroughly tested. What was not tested and could not be tested is will there be any problems with felt very of the final release.

---

Do you genuinely believe that an update that caused an error for so many people on Day 1 was thoroughly tested?

You can expect software releases to be a little problematic from time to time. You put the best testing regime together that you can and you'll still get people coming back to you and saying "There is a problem when you press the button on the right side of the device on Wednesday but I can only replicate it when the device is upside down" and you think, "Yeah, I can see why we missed that".

Thorough testing generally picks up when a major component of the update - the watch faces - is completely missing. If any QA team thoroughly tested that update they want to go through a thorough competency check and maybe even a thorough disciplinary procedure.

[ramkumar]

I didn't get any update in fitbit blaze and I'm from india. If anyone can provide me with necessary details. Tell me

[muppetman]

It's a staged rollout. Be patient. Your fitbit app will notify you when the update is ready for you.

[dorketh]

---

@Rylan wrote:

---

@Rich_Laue wrote:
Fitbit does have a beta program, and the update has been thoroughly tested. What was not tested and could not be tested is will there be any problems with felt very of the final release.

---

Do you genuinely believe that an update that caused an error for so many people on Day 1 was thoroughly tested?

You can expect software releases to be a little problematic from time to time. You put the best testing regime together that you can and you'll still get people coming back to you and saying "There is a problem when you press the button on the right side of the device on Wednesday but I can only replicate it when the device is upside down" and you think, "Yeah, I can see why we missed that".

Thorough testing generally picks up when a major component of the update - the watch faces - is completely missing. If any QA team thoroughly tested that update they want to go through a thorough competency check and maybe even a thorough disciplinary procedure.

---

Do you know how many people experienced problems?  Of course you don't.

Do you know the precise nature of the problem?  Was it something at the server end, something about a specific watch face that caused an unexpected interaction?  Of course you don't.

You are making random wild guesses about what went wrong and the scale of the problem, and ultimately don't have a clue as to what failed.  So please stop making out like you do know what went wrong.

[Haidj1981]

congratulates ban.I not see the update report

[Scottwheels]

My update was waiting for me when I synced this morning. It took a few aborted tries before it was successful, but since it was installed it's worked flawlessly. I'm particularly happy with the reminder to move notifications. Today was the first time since the hourly movement tracking was introduced that I've met the hourly targets on a work day. I work in an office and tend to lose track of the time so I'm really pleased with how well the reminders work.

[AlejandraFitbit]

It's great to see you here @muppetman and I think it is really good to hear that your Blaze is working without any inconvenience and that the update is working too.  Thanks for feedback and if you need anything else do not hesitate in posting it. 

Keep the stepping up! 

[kenlpeters]

@tractorlegs - Thanks for the information.  I did not know that about the update.  Another reason I am excited to get, until then twiddle my thumbs.

[Paints]

@muppetman there are lots of negative comments because support for the blaze so far has been very poor.

I bought my blaze in March and, at that time, the reminder to move feature was promised as "coming soon".

It's almost October and I still haven't got reminder to move, which was one of the main reasons I wanted a fitness tracker. To be honest I couldn't care less about new watch faces, but I would like a tracker that works and has the features that I was promised before I bought it.

The blaze was marketed as the newest, shiniest, best fitbit product and I was initially impressed. However, as the promises of RTM "coming soon" went on and on and the many issues I've had with my blaze (sync problems, inaccurate step count, unreliable notifications / phone call alerts, notifications being switched off randomly, pointless silent alarm, inaccurate maps when using connected GPS, not being able to use connected GPS).

As you can see it's quite a long list! I'm already on my second blaze as the first was replaced.

Hopefully this firmware release will go more smoothly than the last shambles, but seeing as there isn't an official post on the forum from fitbit yet, even though people are posting that they have the latest firmware,  I'm not convinced it will!

[Krayziezay]

So what do I do to check and see if I have the update or not I just have it on my phone I'm no where near a computer

[DibaSr]

Look at the sticky post at the top. What is your definition of "coming soon"? Is 6 months, soon? Everyone all worked up about "RTM" is amusing to me.

[Amy2507]

Nothing for me, I'm in the UK. Fingers crossed it will happen over the weekend. I've been checking my iOS updates everyday since 1st September. If anyone happens to find out when the uk will get the update please let me know.

[Rylan]

---

@dorketh wrote:

Do you know how many people experienced problems?  Of course you don't.

Do you know the precise nature of the problem?  Was it something at the server end, something about a specific watch face that caused an unexpected interaction?  Of course you don't.

You are making random wild guesses about what went wrong and the scale of the problem, and ultimately don't have a clue as to what failed.  So please stop making out like you do know what went wrong.

---

Funny. You get the base logic but just aren't able to follow it through to conclusion.

We don't know have enough information to understand how many experienced a problem by percentage of those that received the update but, even ignoring the anecdotal evidence, the number was significant enough to stop the rollout. A number sufficiently above the acceptable tolerance level for failed updates, set by Fitbit, was reached.

Remember, we're not talking about a percentage of all users with a surge, but a percentage of the 5% they released it to.

In short...if there wasnt a major fault they'd still be rolling it out.

One way or another, Fitbit rolled out an update without sufficient testing or they rolled out an update without sufficiently testing their delivery mechanism. There's no random act of some unseen force here, no case whereby another element outside of Fitbit's control caused an issue. Give me one other, palatable reason, which could have caused the error that lies outside of their control and I'll concede the point.

I'm OK with that. People screw up. But stop pretending it was tested enough to prevent a problem when a problem clearly manifested.

It's not a wild guess. It's logic. Try it out.

[wrx5327]

 It is hard for me to fathom the degree of anger expressed here. I did not get the update yet but am perfectly happy with the actual hardware and current software. Just to think that I can go on a bike ride and come back to see not only heart rate throughout, distance, calories but a full map of my ride. Wow! Please guys, focus on what you have and not what might be. The food data is so helpful to keep a balanced diet! The update will happen for me when it happens. In the meantime, after multiple (4+) trackers, Blaze is the best. The app is the best. The bracelet are the best. I am 100% happy. Maybe 110%. It is like having a dashboard to drive your life. I love it! Enough with the negatives! I encourage all to celebrate this great piece of affordable technology. Keep the praise going.

[mujipanda]

Just wondering, did you have to update the app first?

[tractorlegs]

@mujipanda, no 

[tractorlegs]

---

@FitMad wrote:

so the picture of the battery is larger which is nice but do they have a percentage shown? (I know people have been asking for years). Shame there isn't any news of a % on the blaze itself. 

---

A percentage would be nice, but with the size of the graphic probably is not necessary. Side note: The Blaze has been on the market (available) for only 6 months - It was first announced at CES in January 2016 - so people have probably not been asking about this "for years" lol

[Yaakovchaim]

Now for the big question.  Those of us that did receive the 17.8.301.4 update, how long before we get the .7 update?