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

[Tao75]

So version 17.8.301.4 seems to be replaced by version 17.8.301.7. Anyone knows when it will be released?

[Tao75]

http://help.fitbit.com/articles/en_US/Help_article/1372/?q=update&l=en_US&fs=Search&pn=1

[MikeF]

Are we really going round this loop again?

No, no one knows when it will be released. Fitbit don't announce this stuff ahead of time.

[Tao75]

@MikeF Well they wrote the news the 16. Sept, so i thought this would replace the cancelled firmware from 12. Sept. Why write about it when they cant release it?!

[MikeF]

---

@Tao75 wrote:
@MikeF Well they wrote the news the 16. Sept, so i thought this would replace the cancelled firmware from 12. Sept. Why write about it when they cant release it?!

---

It presumably does replace the other. Until it's actually released, however, we won't see an announcement (if they behave as they always have so far), Why do you think they can't release it?

[Tao75]

Ok, i got the impression from fitbits help Page that the new 17.8.301.7 already was released september 16. My mistake then. Keep up waiting, and stepping

[KiloLima64]

No the update that was released earlier this month was 17.8.301.4 this update mentioned is 17.8.301.7

[bcalvanese]

As a software developer I would guess that they had to make some changes to the code to fix the issues with the release.

When ever code gets changed and a new build gets created, the build number increments. The code should be tested each time a new build is created, and if anything does not pass testing, the code needs to be changed again to fix any issues, and a new build must be deployed to the test environment which increments the build number again.

So it looks like since the number incremented from 4 to 7, a new build has been deployed to testing 3 times. This will keep going back and forth until testing passes everything.

To me, this indicates that fitbit is following a good software development process, and they aren't just pushing stuff out to the public without testing.

Keep in mind that bugs do happen even with good processes in place, and it seems like fitbit had a bug in the release and is doing the best they can to insure it is fixed before continuing with the release.

So why don't we cut them some slack and be patient.

I have owned many different trackers and if you go on the Garmin forums you will see that they are riddled with bugs, and they are constantly rushing out releases and beta releases. They may fix one or two things, but create two or three more bugs in the process.

Just my 2 cents.

[Tao75]

And since september 19. they change back to version 17.8.301.4 in the help site...?
http://help.fitbit.com/articles/en_US/Help_article/1372/?q=update&l=en_US&fs=Search&pn=1
Hope this means they have sorted out the trouble with all this firmware mess?!

[Graeme1974]

Well it looks as the those it's finally here and all is working well. So those still waiting check in you account on Fitbit and then update with the pink arrow.

[Tao75]

anyone got the update today?

[Krayziezay]

Nope not me

[runwithnewmedia]

Just popped up for me! Updating now.

[AndrewFitbit]

I've added an update to the lead post in the firmware thread in regard to this.

[TRAILBLAZER06]

I received the update and it works perfectly so far! Thanks Fitbit!

[Krayziezay]

So was y'all phone connected to your blaze or no because I still haven't gotten it yet

[TRAILBLAZER06]

When I went into the Fitbit app it said software update available. I think they are still releasing it in small percentages at first to make sure nothing goes wrong.

[Graeme1974]

I always have my Bluetooth turned on, by the sounds of it they are rolling it out in slow time

Sent from my iPhone

[akaserge]

Update process was fine.