Introducing Charge 5 Firmware Release - Version 1.171.50

[FitbitCommunity]

We’re excited to announce that a firmware update for Charge 5. Some of you might already have this update available. If you installed it, let us know what you think!

We release updates to customers in phases. If you don’t see it, check the Fitbit app in a few days, and you’ll see a message when you can install the update. We appreciate your patience while we get this update to all of our customers. 

WHAT’S NEW AND FIXED

See What's changed in the latest Fitbit device update? for release notes.

HOW DO I UPDATE?

See How do I update my Fitbit device? for step-by-step instructions for updating your Charge 5. If you run into difficulty updating, see Why can't I update my Fitbit device?. 

We’re interested in hearing your feedback on this update! Let us know what you like! If you encounter unexpected behavior during or after your update, please post the details below.

[DrDaveUK]

UPDATE: I installed the update yesterday.  I had the unit on the charger during the update, as suggested on the app. It took around 10 minutes to complete.  When I took it off the charger yesterday the battery was at 83%. Tonight, after about a day and a half on the new firmware the battery is showing 68%. ECG function is working (and not resetting like my old one would do). I haven't really checked for new watch faces, as I like the split-flap style.   

Summary: All good at the moment. I will try more functions during the week, but the key ones, steps, heart rate, active minutes appear to be working properly. 

[CoreyMac]

@DrDaveUK 

Glad to hear it.  What version are you running now?

[DrDaveUK]

It updated to the 1.171.50.  The only choice was to update to the latest version.   

[CoreyMac]

@DrDaveUKI was sort of hoping that they had fixed some of the bugs and released a new version by now for folks.

Thank you for checking though.  Glad yours is well.

[DrDaveUK]

You got me wondering if the problem is only occuring if you were updating from 1.149.11 rather than from 1.142.37, which this replacement unit came with.  

[CoreyMac]

@DrDaveUKThat is one of the largest issue with these problems are the lack of data about the sequences and steps and versions.  We do not know if the hardware version matters or the previous version it was upgraded from or what. 

Fitbit has been zero help in this area as well.

[SteveCDN]

… and that surprises you ??

[CoreyMac]

No but you can always have hope they will change and fix this sort of behavior, even though it is unlikely.

[Just_A_User_J]

Is your Fitbit device on 3.42?

[delawareBirder]

@DrDaveUK  My wife updated her Charge 5 successfully from 1.149.11.  Hers worked, mine bricked.

[KSparrow254]

I called and got a replacement after having issues with the battery during in hours and then not holding a charge.  The replacement is 1.142.37.

I have not updated yet as I am afraid to and have issues again.  Has anyone done this?  What has been the result?

[VballKitty]

I got a replacement FitBit and updated its firmware. I had it plugged in and held my fully charged  phone next to it while the update took place. The update worked for me and my battery is fine.  No guarantees though. Good luck with whatever you decide

[SteveCDN]

Thanks for the update… will look for more confirmation before au jump down that rabbit hole.

Do you remember what Firmware number you upgraded from ??

[radesix]

@delawareBirder I’m curious to know if your device and your wife’s device were purchased near the same time or a significant amount of time in between.

I have a working theory that earlier devices were made with one manufacturing bill of materials then At some point newer devices were made with a different manufacturing BOM. This might explain why they missed it in regression testing if they were only testing on the units with the newer mBOM and not original units with the older mBOM.

I purchased my unit not long after the Charge 5 debuted. I didn’t have the original battery problem they say the release fixed. But I ended up with a major battery problem when the firmware update was applied.

My wife’s unit was purchased many months after my unit. We never updated her firmware after mine blew up but I suspect she has one that would work fine with the update because she probably has a version with the newer mBOM that was actually tested before the update was released.

I'm just not willing to try it! She won't gain anything by it as she isn't having battery problems with the older firmware. But she isn't using GPS either so who knows.

We're all left guessing when the vendor doesn't acknowledge and communicate.

[DrDaveUK]

Take a look at my comment a few posts earlier.   I am now on day 3 after updating. So far, so good.    Battery life still seems good.  Battery was at 83% after update, 68% yesterday evening, and now about 18 hours later, down to 61%.   I updated from the same version that you received.  

[SteveCDN]

Wouldn’t it be nice if Fitbit answered these questions and provided SOME guidance rather than jumping through hoops and speculating 😀

[delawareBirder]

@radesix  I purchased my Charge 5 from Amazon in mid-December of 2021.  My wife's Charge 5 was purchased directly from Fitbit in mid-January 2022.  When activating we both upgraded to the then latest firmware at the time which would have been 1.149.11.  Since they both updated I will assume that they both started at 1.142.37.  When they both were updated to 1.171.50, mine bricked and hers is working fine.

[SteveCDN]

Thanks for info.

[WCC10522]

If Fitbit told you the below, would you believe them and update?

Thanks for contacting us, we are glad to help you

Our recommendation is updating the Fitbit Charge 5,te update appears when the Fitbit device required, the issue about the update is resolved.

We hope this helps. If you have any questions about your Fitbit device or services, visit help.fitbit.com

Sincerely,

The Fitbit Team

[Catwoman777]

Uh no. I lost trust. I will not be updating.