Charge 2 Firmware Release (22.58.0)

[AlessFitbit]

Fitbit Update: 8/14

Hey all!

Today we have completely released (out to 100%) this new Charge 2 firmware (22.58.0) to all users. This means everyone should now see it available for download in the Fitbit app. Please update to this new firmware. For instructions on how to complete the update, read How do I update my Fitbit device?

If you come across any difficulty updating, read Why can't I update my Fitbit device?

We've included bug fixes and improvements in this new firmware and always recommend having your tracker up to date, including the Fitbit app on the latest app version. 

---

Fitbit Update: 7/24

Hi everyone,

We’re excited to announce a new firmware update for Charge 2 (version: 22.58.0). 

We've begun releasing this new firmware to customers. This is a progressive rollout which means everyone will receive it at different stages until it has been completely released to all users. We roll out releases in phases as a cautionary measure so that we can monitor performance closely and make adjustments if needed. 

*Firmware releases are not distributed based on region or location and can reach anyone no matter where you reside. We do not recommend performing a factory reset to force the update to your device as your data will be lost and you may not get the update. Please be patient and wait until you see the update banner inside of the Fitbit app to begin the firmware download.

WHAT’S NEW AND FIXED

 
This release includes other bug fixes and improvements.

HOW DO I UPDATE?

Step by step instructions for updating your Charge 2 can be found here.

If you run into any trouble updating your Charge 2, I recommend reviewing these troubleshooting tips. 

Looking forward to hearing everyone's feedback on the latest release. If you have any questions, feel free to let me know! 

[daz1701d]

Ive hit the same issues as above with battery life. Less than 10 minutes with no interaction from full charge once I disconnect. Heart rate lights on constantly but nothing registering on the device.

Ive raised a support case when the first update bricked the device, worked through each of the options provided by Support to  fix the device, and was effectively told "bad luck, its out of warranty, have 25% off a new device, but we cant guarantee we wont brick that one too"

Sorry but thats not an acceptable response to this situation.

I then emailed Support earlier today, but was told that updates are free, and my device is out of warranty, so again they have to stick to policy. So their policy is to kill everyone's devices once theyre out of warranty. Way to drive customer loyalty!!

Again this isnt acceptable. Fitbit either have to roll back the updates until they figure out what theyve done wrong, or they need to stand up and admit theyve made an error and provide a resolution that doesnt leave lots of users out of pocket 

[Cars100]

This amount of problems are disappointing. It smells of the FitBit software group developing a new release to include new features, and not taking the time or expense to test it thoroughly before releasing it. In short, the customers are unpaid testers. And actually, since the 25% retail discount, given to customers who’s hardware is rendered useless due to FitBit’s premature release, more than covers production costs, they are actually making money on our problem. It’s their win-win situation. Shameful. 

[Stushaw247]

For those that are old enough, the "Big 3" US car manufacturers pulled the "planned obsolescence" game in the 1970's, and it blew up in their faces.  It took decades for them to recover, and they're not so big anymore.  Funny what you can learn by studying history.  Perhaps the Fitbit folks should look backwards for future guidance......

[Gama92]

Fitbit software has always been full of bugs and poorly tested.

They don't care about customers.

I recognize they build good and nice devices, but their software engineering team it is not up to the job. 

[HD78]

This update won't load but also has stopped my fitbit from syncing looks like I have lost my 20,000+ day yesterday. 

So sick of fitbit, the products are expensive tat. My screen is cracked I have had to replace straps this doesn't happen with ordinary watches it is less than a year old. Much improvement needed from the market leader 

[Jennyw73]

I'm having exactly the same issue. Just got an A70 and cannot pair nor update. If you find out anymore information please can you post on here and I will do the same 😊

[mikehcox]

... and add a list of fixed reported bugs to the release notes.  Duh!

[Jlgjr]

Still not getting messages either

[MarkAE]

I installed the update yesterday. I don't know if there is a relationship but last night for the first time ever, my sleep was not able to be recorded.  

[HD78]

I went to sync last night was informed of the update and I thing has worked since, not synced, no sleep, no steps today and still saying a fault with update

[hulagirl88]

UGH!!  there have been 2 Android app updates since I initially reported the issue early July, last one on 8/8.  None of them fixed the sync (text message) issue.  Agreed with several Charge 2 friends that the sleep sync is very inconsistent.  @AlessFitbit Thank you for acknowledging the issues.  Can you please provide us with an eta when the fixes will be made.  I think this team is growing in frustration.  Thank you!

[Whitedan]

Updated yesterday, really hoping that it would of fixed the no showing of the texts just the name from my S9. It started doing that right after the last app update It didn't and now battery life is almost cut in half. Tried the suggestions I've found on the forum, nothing seems to work. Great job Fitbit, think it's time to go to the galaxy watch if this still isn't fixed in the next little while.

[SunsetRunner]

Firmware update seemed to be ok for me, but after I charged up my Fitbit, the app began to detect the battery as run down.

If I restart the app and my Bluetooth a few times in a row, that seems to work, but there are chunks of data missing.

The recent major app update has been been tracking heart rate strangely since - my Fitbit will show a given heart rate for part of the day, and so will the app when it is open, but once it is synced the points for that timeframe are 10 to 15 bpm higher than the watch reading. Have taken my pulse manually to cross-check, so the issue is with the app and not the heart rate monitor.

Given the plethora of problems people are having with the update, many of which are more severe than mine, Fitbit needs to make rollbacks available immediately for the firmware and the app whilst they work on a proper fix. These devices are expensive and this isn't in any way ok.

[TomDuke]

This is not the first time Fitbit has done this.  Last year an update for the Ionic made SMS notifications that had been working flawlessly stop all together.  Took 3 or 4 weeks to fix that one.  I'm not loading the Charge 2 firmware update until I see that it's fixed on this forum.  Other companies do the same stuff though; I bought a DJI drone a couple years ago and did the initial firmware update and then NEVER connected it to my computer again after reading countless tales of drone failures after subsequent updates.  The motto seems to be: "If it's not broke, break it."

[NathanJM]

My Charge 2 no longer tracks heart rate after the firmware update. The lights on the back are not blinking. I've tried a restart, and I've tried turning the sensor off, synching it, turning it back on, and resynching. It is still not measuring heart rate and the green lights are not flashing. I've also followed troubleshooting steps listed elsewhere on the site (unpairing / removing device from app / re-adding as a new device). Not sure where to go next. Don't have much use for a Fitbit that won't measure heart rate. Please advise.

UPDATE: 

I followed the steps @Dtherrian posted, here: https://community.fitbit.com/t5/Charge-2/Charge-2-Firmware-update-fix/m-p/3690626#M210549

and my device is now working.  In my case, on iOS, I only had to do steps 1-4, then proceeded to step 6 to sign into the app and re-pair the charge 2.  I knew I was in good shape after the green lights were blinking on the back again after the reboot. It seems the key was to sign out / uninstall the app before unpairing from the bluetooth settings and rebooting.

[ShannonH46]

I did the firmware update the other day only thing not working is my sleep
stages

[A-JM]

After updating my Charge 2 I lost sleep stages (3 nights in a row). I'm lucky to have a spare one. I'm not going to update this one before I can see that this issue is fixed. 

[ShannonH46]

I have a new ginut coming in mail that I ordered. I hate not having sleep
stages

[bulek]

Well.. I thought I had a good luck because my upgrade went well, fitbit was synced properly and I was able to see my HR. Today morning however no sleep stages :(.

Looking at over hundred posts, very fuzzy explanations and template answers from Fitbit I don't have a good feeling on the course of actions. All of this looks almost as forcing users to drop existing devices in favor of Charge 3. Apple did this by silently slowing down older devices on purpose not so long ago. Is this the same here? Publishing a broken upgrade for devices which are out of warranty in most of cases? Not admitting to faulty firmware and as a last resort proposing 25% for new device? Sad to say but I see a lot of similarities here.

[HICAndrew]

yesterday I switched my plug from the wall to my laptop. My Fitbit turned on and charged. lasted maybe 1/2  the day zero synchronization  happened.  tried to recharge the battery and nothing. 15 minutes ago it turned on. I think I have updated everything. Im not sure why it died it says I'm at 53% on the battery even though I could not wake it...

i still have never gotten text messages across my fitbit, i do see phone numbers though.

Fingers crossed I dont lose another week . Due to this issue. 

I've been loyal, turned friends on to the brand. this is my 2nd generation of the Fitbit brand. 6 months and I will get the next generation, unless this issue isnt fixed! Otherwise why would I bother???