Firmware update v 220.31

[EstuardoFitbit]

Thank you for your patience as you waited for the firmware update. 

This update includes key fixes for battery and display issues, along with new clock faces for Charge 6. 

Please keep an eye on the Fitbit mobile app for the update notification as it continues to become available to all users, beginning this week.

Thank you for your continued support and patience!

[AjmP]

Why was the last update roll out so badly handled?

[xambro]

Should we see it now cause I still don’t.

[e1lacros]

Never got the last update, how does that happen?   I am still at 214.24

[xambro]

Question: how is .31 out already when people still haven’t even gotten .21???

[mikey_pdx]

Is this going to be for all Charge 6 devices, or will there be some obscure criteria that won't be communicated as to why we don't get the update? Also, are there more new clock faces, or are the new ones in 220.31 the same 3 from 220.21 that we didn't get because there was some arbitrary reasoning that some devices didn't get the update?

[xambro]

Does “beginning this week” mean the beginning of this week, or like it could happen next week? Cause I’d really like to see these new clock faces

[Wahoox2]

I have been following prompts/suggestions here and from fitbit support to get the update for 220.21 for months with no success so I would appreciate it if they give me SPECIFIC information on when 220.31 will actually be available to ME.  "Beginning next week" sounds alot like what we heard before.  I'm tired of wasting time.

[AjmP]

Soon™... The next couple* of weeks... or something equally vague but they thanked us all for our patience (like we had any choice) so we should be grateful? I doubt we'll get any useful information they seem committed to obfuscating their botched update process.

The 'couple' in 'next couple of weeks' should not be considered to represent two or any actual number. 

[reevald]

The version v220.21 is being terrible till now on my charge 6, randomly restart and stuck on logo since 5 nov (already report to fitbit help center, but no solution), hope i got the last version immediately.

[xambro]

So has anyone actually gotten this update?

[Vokster]

Hi Estuardo, we have been waiting for a looong time for the update. What’s happening?

[JoeG151]

Did the update a month or two ago and the Charge 6 stopped charging.... Second Fitbit to do that to me.... of course its right after the warranty expired

[Steltek]

Will this also be announced at https://support.google.com/fitbit/answer/14236725?hl=en#zippy=%2Ccharge? (So far only 220.21 is listed there.)

[xambro]

Has anyone actually gotten 220.31 yet?

[AjmP]

Has anyone gotten v220.31 yet? Haha, no one has received v220.21 yet! At this point it's vapourware. Fitbit have refused to make any substantive statement on the rollout or failure thereof. Support have, according to post here, been less than honest regarding how updates work and the company representatives have made blatantly inaccurate statements and stood by them (next couple of weeks which was several months ago). 

Vapourware or abandonware, but hey there are rumours that they're releasing new hardware next year! Maybe they can promise firmware updates that go beyond a "couple of weeks".

[Wahoox2]

I got the following this AM to my latest ask on firmware - 

“Thanks for reaching out to the Fitbit Customer Care Team.

We have received an update from our senior team regarding the status of the software update.

Please be advised that the update will be available to you soon. The reason you have not yet received it is that the rollout has been currently paused.

We appreciate your patience and understanding in this matter.”

[narf57]

---

@Wahoox2 wrote:

I got the following this AM to my latest ask on firmware - 

“Thanks for reaching out to the Fitbit Customer Care Team.

We have received an update from our senior team regarding the status of the software update.

Please be advised that the update will be available to you soon. The reason you have not yet received it is that the rollout has been currently paused.

We appreciate your patience and understanding in this matter.”

---

Thanks for the info. If the Fitbit team would just communicate this kind of thing directly it would go a long way towards improving thier reputation around here. Nobody wants to rush a buggy update, but once you announce it's release.......then release it or explain the delay.

[StepCount123]

---

@Steltek wrote:

Will this also be announced at https://support.google.com/fitbit/answer/14236725?hl=en#zippy=%2Ccharge? (So far only 220.21 is listed there.)

---

I was wondering the same thing, I follow the charge threads because it was also announced (there at least, not here) for other devices (I am sense 2). And also noticed that page had not been updated after the .31 announcement. 

I saw the other posts about a "pause" comment from support, but have gotten so cynical and the fact that the update page was not updated, that I am not sure if support is referring to .21 or if .31 has now ALSO been paused too?

[xambro]

@EstuardoFitbit Can you please explain why this update has not shown up yet?