07-24-2019
11:00
- last edited on
09-08-2020
14:11
by
MatthewFitbit
07-24-2019
11:00
- last edited on
09-08-2020
14:11
by
MatthewFitbit
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!
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
Answered! Go to the Best Answer.
10-08-2019 01:40
10-08-2019 01:40
Fitbit admitted the recent update only worked properly (syncing, tracking etc) with a very limited range of phones, which they have listed on their site, so if you (like me) now have an 'incompatible' phone (which was fine before the update) it will never work properly, even with a refurbished or new device.
They claimed a while ago to be working on a solution, not seen anything further to say when (if) Fitbit will fix the software to work on a wider range of devices. I suspect the Charge 2 is basically now a redundant device even though you can still buy new ones on Amazon and other sites.
10-08-2019 11:15 - last edited on 07-12-2020 11:50 by LiliyaFitbit
10-08-2019 11:15 - last edited on 07-12-2020 11:50 by LiliyaFitbit
It figures. It seems that the folks at Fitbit don't give a hoot about users.
Moderator edit: format
10-08-2019 11:20
10-08-2019 11:20
Fitbit Update: 10/8
Hi folks,
We really appreciate everyone's feedback on this last firmware update for Charge 2.
At this time the firmware has been rolled out to 100% of customers and all of the feedback on the latest release has been passed on to our team. I'll be closing this thread for further comments. This is to keep the Community organized, productive, and on-topic.
If there are anymore firmware releases for Charge 2, we'll make sure to announce them here on the Community.
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
10-08-2019 11:23
10-08-2019 11:23
10-08-2019 11:29
10-08-2019 11:29
So we have to start another thread for our complaints about this? Seems silly to me but if that's what you want us to do, I am sure we are up to the challenge. And that way someone looking can find MULTIPLE threads about the problem. Seems like you guys thought this out very well.
10-08-2019 11:36
10-08-2019 11:36
We are organized and on topic. We're angry that the firmware destroyed our charge 2's and the company doesn't seem to care!! How is this not on topic?
My fitbit is still a paperweight sitting on my nightstand because of the firmware updates.
10-08-2019 11:56
10-08-2019 11:56