Duration to Update Firmware

[Andhanni]

I have been reading the thread on the latest firmware update for the Blaze and even posted a few comments about duration cause of all the posts about how long it was taking.

Some people reported 5 minutes others an hour... So it got me wondering from a 6-Sigma (Yes I am a Green Belt from my Motorola days) prespective, what could be the cause.

One individual reported 5 minutes cause their Blaze was in the charging craddle connected to a power source.  Several said 10 minutes, but did not say what the power level of their blaze was and others that reported longer times did not mention.

So my question more towards fitbit themselves was when they QA the release did they do power consideration testing and could/should there be a recommendation that the blaze have x amount of juice prior to the update being performed?  If they did not will they do regression testing on this matter to help for future releases?

Just my Engineering mind wondering...

[MikeS1971]

I honestly don't think it has anything to do with battery level, WiFi or data signal strength, tracker, phone or computer. My theory is its all on FitBits end and their servers can't handle the traffic. I think its the luck of the draw when someone gets a quick update time. 

[MakMak]

@Andhanni, just to obfuscate your data, my update took less than ten minutes and I got a low battery indication within an hour following the update!

[Julia_G]

Mine was very quick -- not more than 5 minutes, but I always update Fitbits plugged in, because updates draw a lot on the battery and running out in the middle can be bad news.

[Andhanni]

@MikeS1971: Actually I would agree to some point considering what I do for a living.  But I would assume that the update was properly staged to ensure against overloading the servers.

Just my thoughts considering the last update.

[Pattipat]

Thank it was so h

[Pattipat]

Thank you very helpful. I give you a 10 great instructions.👏