05-03-2018 15:07 - edited 05-11-2018 14:04
05-03-2018 15:07 - edited 05-11-2018 14:04
Fitbit Update: Fitbit OS2.1 has been released to 100% of users!
Hi all!
I am excited to announce the release of Fitbit OS 2.1! (Firmware Version: 27.32.10.15)
We've started to roll out this update to 10% of Ionic users. This is a progressive rollout, and all Ionic users can expect to have it within a few weeks. We roll out releases in phases as a cautionary measure so that we can monitor performance closely and make adjustments if needed.
WHAT’S NEW
Introducing quick replies. Send customized responses to text messages and messages from select messaging apps with your Fitbit watch. Note that this feature is currently only available on watches paired to an Android phone. For more information, see How do I respond to messages with my Fitbit watch?
This release includes other bug fixes and improvements.
Step by step instructions for updating your Ionic can be found here.
I recommend updating your Ionic over a home Wi-Fi network as this can greatly reduce the time it can take to get set up. For more information on connecting your Ionic to Wi-Fi, check out this article.
If you run into any trouble updating your Ionic, I can also 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 deep sleep? Join the discussion on our Sleep better forum.
05-10-2018 23:24
05-10-2018 23:24
Is the latest version 32.10.20?
05-11-2018 01:18
05-11-2018 01:18
I've sent mine back I'm afraid. I thought the hardware and styling was great but the software was not even close to being ready for release. That's the problem.
05-11-2018 01:26
05-11-2018 01:26
@MattFitbit wrote:
@Mark2018 If you are still are not receiving sleep stages, I recommend checking out the tips detailed in this article.
Thank you! I'm sure you are doing your best.
Of course, I have done all advices from support and have read all information concerning this problem.
My new hobby since I have Charge 2 and Ionic: restarts, new installation, reconnectin. Position changing!
So, you know what cardiac arrhythmia is? Here you don't have consistant heart rate! And this is the mentioned error message. Strange!
Sometimes slow, sometimes faster. More Fitbit, more faster. 😉
If Fitbit really uses HRV that problem doesn't exist! We should have sleep stages for sure!
And why did I have sleep stages until an update of the Fitbit app? After update: no sleep stages!
That was the only change!
I'm looking forward for detail information! Support can't answer!
Strange!
But my Ionic is now on the way to the technical center in the Netherland!
It looks like the Ionic has a technical problem with the sensors.
The Charge 2 works when my wife is using that tracker!
But not for me! Still no sleep stages!
No detail information which data is missing!
No information where the signal strength is to low!
etc.
etc.
Thank you very much for your help!
Best regards,
Mark
05-11-2018 05:28
05-11-2018 05:28
Yeah. One day I had climbed 21 floors...yet only walked ~1200 steps.
@imeson79 wrote:Updated mine, and seems to be a little bit better,
One thing i did notice is that it now states i've climbed 17 floors of stairs.. which i can guarentee you i would know if i have done some stair climbing or not.
05-11-2018 06:18
05-11-2018 06:18
Matt
The issue I have is I always used all day sync because I've always had a hard time getting it to sync. I've always used notifications becausev that's why I have the watch. I have used the same clock face since the second week I owned the watch. I could count on getting 5 days out of a full charge doing all these things. Since the update, I barely get three days even after fit bit ask to remove all day sync and notifications for a test run. Now you mention the clock face as a potential issue?? It has to have something to do with the latest update.
05-11-2018 06:34
05-11-2018 06:34
I haven' t received the latest update yet but I have a Samsung s6 and I went for a run on Tuesday and it didn't sync with Strava until the following morning. Fitbit need to sort there acts out as I am slowly going off them.
05-11-2018 06:36
05-11-2018 06:36
05-11-2018 06:37
05-11-2018 06:37
05-11-2018 07:41
05-11-2018 07:41
Day 4 of 'the adventures with my Ionic':
a totally irresponsive screen that is black... Nothing to see on it... Translation: my Fitbit Ionic that I bought in January 2018 for 300 Euros, is totally 'dead', after the last update you guys released.
Also: no reaction at all of the moderators here, just ignoring...
Thank you, guys!
Sofie
05-11-2018 10:47
05-11-2018 10:47
I'm a little worried to upgrade to the latest OS when it gets pushed to my Ionic. There seems to be a lot of problems. Did they pull the update or is it still coming through?
05-11-2018 11:03
05-11-2018 11:03
Would be great if you guys included some more details on the bug fixes, instead of simply saying:
>>This release includes other bug fixes and improvements.
05-11-2018 11:38 - edited 05-11-2018 11:39
05-11-2018 11:38 - edited 05-11-2018 11:39
I did a factory reset and upgraded to the newest 32.10.20. Everything seems okay here . I did not get the upgrade pushed to me but removing the Ionic from my account and doing a factory reset gave me the newest update. I always do a factory reset when I update the firmware anyway, this has made the process problem free for me.
05-11-2018 11:55
05-11-2018 11:55
Do you notice the issues that were in the .15 update persisting in the .20? The .15 seems pretty bad so far. I'm eagerly awaiting the .20 push.
05-11-2018 11:59 - edited 05-11-2018 12:02
05-11-2018 11:59 - edited 05-11-2018 12:02
I never had the .15 update on my watch. If you did a factory reset now I believe you would get .20. I would also remove the Ionic from your app and set it up again as a new Ionic.
05-11-2018 12:13
05-11-2018 12:13
I am just curious to see to see if they try to cover up 32.10.15 ever existing, they changed the subject of the forum posts for both Ionic and Versa and they haven't added 2.1.1 to the change log yet. So who knows if there will be a long standing record of the problems 2.1/32.10.15 caused or if it will be a cover up.
05-11-2018 12:43
05-11-2018 12:43
05-11-2018 12:46
05-11-2018 12:46
I bet we will never get that.
05-11-2018 14:54
05-11-2018 14:54
It’s interesting you said 2.1 was available to all back in this post from May 3rd but I JUST received the 2.1 prompt to update in my iOS app just today May 10th. Did not release to 100% as you said I guess? Confidence is dwindling here. 😞
@MattFitbit wrote:Fitbit Update: Fitbit OS2.1 has been released to 100% of use
Hi all!
I am excited to announce the release of Fitbit OS 2.1! (Firmware Version: 27.32.10.15)
We've started to roll out this update to 10% of Ionic users. This is a progressive rollout, and all Ionic users can expect to have it within a few weeks. We roll out releases in phases as a cautionary measure so that we can monitor performance closely and make adjustments if needed.
WHAT’S NEW
Introducing quick replies. Send customized responses to text messages and messages from select messaging apps with your Fitbit watch. Note that this feature is currently only available on watches paired to an Android phone. For more information, see How do I respond to messages with my Fitbit watch?
This release includes other bug fixes and improvements.
Step by step instructions for updating your Ionic can be found here.
I recommend updating your Ionic over a home Wi-Fi network as this can greatly reduce the time it can take to get set up. For more information on connecting your Ionic to Wi-Fi, check out this article.
If you run into any trouble updating your Ionic, I can also 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!
05-11-2018
15:09
- last edited on
05-11-2018
15:23
by
ErickFitbit
05-11-2018
15:09
- last edited on
05-11-2018
15:23
by
ErickFitbit
Fitbit Update: Fitbit OS 2.1 (v32.10.15) has been pushed to 100% of users!
@SunsetRunner @nasder @MattJ71 @JamesIonic @0hwell @Mark2018 Sorry for any confusion in regard to the release version number. We wanted to give our newest customers our most updated software experience. Existing customers, stay tuned for more updates.
@sfringer Thanks for the quick reply! I have forwarded this information to our team along with your report. I appreciate you taking the time to call out this issue.
@Frodo007 Sorry to see that your screen is unresponsive. I have gone ahead and reached out to our support team on your behalf to have a case created. They will be in contact via email soon with some additional help!
@imeson79 @MissUrka Glad to see that you were able to get updated. Ionic counts floors using changes in barometric pressure. So erroneous floors can appear from time to time if the pressure around you was changing. If you continue to see odd floor counts, I would recommend performing a restart.
@Mark2018 Thanks for the reply. I appreciate you taking the time to contact our support team.
@Navigator243 Thanks for the clarification. I will forward this information on to our partner team. In the meantime, have you attempted to restart your Ionic to help refresh its system?
@Shepden As mentioned in my previous post. Our team is aware that exercises may not be syncing to Strava. You can follow this issue in the dedicated thread. Additionally, I can confirm that this OS 2.1 release is not related to the Strava syncing issue.
@petermh Sorry to see that your Ionic continues to act up! That must be very frustrating. I appreciate you taking the time to reach out to our support team. I have let them know that your Ionic is still not working and they will be in touch via email with the next steps we can take to get you back on track.
@bhwolf Thanks for the feedback. I will be sure to forward this info to the broader team.
Want to get more deep sleep? Join the discussion on our Sleep better forum.
05-11-2018 15:12
05-11-2018 15:12
Okay, Matt!
I already received a mail of Fitbit support. I hope they can help me soon enough.