Fitbit OS 3.0 - Ionic Firmware Release (27.33.1.30)

[MattFitbit]

Fitbit Update 1/10/19: 

Hi all! Big thanks to everyone for your feedback on the release of Fitbit OS 3.0!

Since the majority of users have now updated to 3.0, I will be closing this thread from further comments to help keep our community discussions on-topic. 

If you are experiencing an issue outside of the firmware update process, I invite you to start a new thread on this forum and we will be happy to assist you there. Thanks again and happy stepping!

---

Fitbit Update 12/26:

Hey, everyone! We're aware that some of you may have noticed a fast battery drain on your Ionic watches after completing this firmware update. Our team is investigating the root cause of this issue and whether it was caused by this update or other factors are involved. 

In the meantime, if you're experiencing this problem please try a restart on the device then consider switching to a Fitbit made clock face! Many 3rd party clockfaces (especially those with animations) are known to use up more battery. If you try this out and are still seeing a fast battery drain, we can connect you with Customer Support for next steps or you can reach out to them and create a case. 

We look forward to getting you all back on track! 

---

Fitbit Update 12/22: 

We've released Fitbit OS 3.0 out to 100% of users. Please make sure you have the latest version of the Fitbit app (2.84) before downloading the newest firmware. 

We're excited for you all to have the newest Fitbit OS, but please let us know if you have any questions about this update. Happy Holidays, everyone! 

---

Hi, everyone!

I am excited to announce the release of Fitbit OS 3.0! (Firmware Version: 27.33.1.30)

We've started to roll out this update to 20% of Ionic users. This is a progressive rollout, and all Ionic users can expect to have it soon. We roll out releases in phases as a cautionary measure so that we can monitor performance closely and make adjustments if needed.

WHAT'S CHANGED?

Please check out this help article to see what's new in this update.

HOW DO I UPDATE?

Step by step instructions for updating your Ionic can be found here. We 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 trouble updating your Ionic, please follow these steps:

1. Restart the watch. 
2. "Remove" the watch from your account inside of the Fitbit app.  
3. "Forget" the watch from your phone's Bluetooth settings (along with any other Fitbit devices paired to your phone)
4. Try the update again. 

If anyone isn't seeing the Today app after updating, please try the following:

1. Make sure you're running the newest version of the Fitbit app. 

2. Connect to Wi-Fi in the Fitbit app, plug your Ionic into the charger and let it sit. This will automatically update the Today app. 

Looking forward to hearing everyone's feedback on the latest release. If you have questions, please let me know in this thread!

[bIonicman]

I updated my Ionic last week, and so far I have noticed two issues with it, which I did not have before the update :

- The HR monitor does not always pickup anymore. Quite often I notice no indication of an HR at all. This was working perfectly fine.

- When I push the left button to activate the screen, from time to time nothing happens at all. When I then push it again, the screen flashes, and goes dark again. I have to push it a third time to finally activate my screen, which is also something that was not an issue before.

Before this update my Ionic was finally working the way I believe it should after having it for about a year or so and many updated. This last update is a step back from what I can see, as I do not see any positive changes, just the two negative changes I mentioned above.

[EdsonFitbit]

Hello everybody, thanks for visiting the Fitbit Community.

At the moment, there is no information about this situation. Once any update be available it will be communicated as soon as possible. If you are still experiencing difficulties please be so kind to follow these steps.

Keep on stepping.

[MeThomas3]

Well once again. My watch gets an update and now my watch goes crazy. I am on my 3rd Ionic this year (all under warranty). now my warranty is gone and this update is causing so many problems. won't charge correctly, loses connection with phone, locks up with the Fitbit Diamond on screen, the last one I have to reset the watch and charge it again and maybe it works. Not a happy camper with the Ionic, thinking of changing models or evan brands.

[SunsetRunner]

Yes, the pay wave terminals that the Fitbit is designed to work at are failing unless it is my bank's terminals. This was never an issue before the OS3.0 upgrade. I have used the Fitbit Pay function for ages with no issues until now.

[Fitbatter]

I was asked to do this by Fitbit support so they are not all aware that a reset is the way to destroy the Ionic. The factory reset rolls the Ionic back to 2.x and then the subsequent firmware update to 3.0 bricks the Ionic device. I now have an Ionic paperweight.

[LarryQW]

---

@SunsetRunner wrote:

Yes, the pay wave terminals that the Fitbit is designed to work at are failing unless it is my bank's terminals. This was never an issue before the OS3.0 upgrade. I have used the Fitbit Pay function for ages with no issues until now.

---

I'm in the USA, which has totally different terminology from what you use. After the OS3.0 update, I've noticed no difference in the Fitbit Pay at several store's pay terminals. (Is that what you mean by "pay wave"?) Actually, FitBit Pay seems to be working a bit better with near instant beep and acceptance, but that could just be good luck.

Maybe something about the payment is different in your country and was messed up in the upgrade?

[SunsetRunner]

Yes, terminology differs a little but the more I test and retest, it would appear our banks in Australia have not allowed for cross bank terminal support for Fitbit pay. 

Firbit it seems to be working well so I can only deduce our banks need to catch up here 

[Fitbatter]

I travel a lot and just happen not to be in the U.S. at the moment. I’ve read quite a few posts of erratic operation in version 3.0 as well as third party clock faces and then subsequent resets rolling back the Ionic too far and then the 3.0 re-update bricking the device. I wish the NFC functionality was my issue. I can’t even get it to turn on, restart, reset etc. the firmware has obviously corrupted and the buttons don’t tell the watch to do anything, the battery is at a full charge and plugging it in doesn’t bring it back to life. Was told I could buy a new one because as an early adopter a botched firmware update was not eligible for replacement.

[tfellenb]

I had the exact same thing happen to me and Fitbit has yet to resolve anything! They said the engineering team in San Francisco is looking into it, but no news yet (although they did remind me that my watch is no longer under warranty...). I’m extremely disappointed by their response and lack of resolution to date; this is no way to treat a repeat and loyal customer.

[drtechieMOH]

@MeThomas3 I'm with you on this. I thought I was the only one who's Ionic will be replaced more than once. First was a few weeks shy of 6 months into it's very short and sad life.  Then a day over my supposed warranty with the messed up update, and after much ranting with FitBit support, they will replace the Ionic for the 2nd time within a year. 

It was doing so well until this recent so-called update was released.  Sad to say I will be saying good bye to it and switching to another brand. I don't think i will even reconsider switching back as it is not worth the cost they charge and the headache that comes with it.

[Stenis]

After update the ionic shows messages direct instead of after i turn my wrist

[Ebojager]

---

@Fitbatter wrote:

I was asked to do this by Fitbit support so they are not all aware that a reset is the way to destroy the Ionic. The factory reset rolls the Ionic back to 2.x and then the subsequent firmware update to 3.0 bricks the Ionic device. I now have an Ionic paperweight.

---

This is interesting...I have factory reset mine atleast twice under 3.0 and haven't had any issues, though once the watch said it was done updating but the app still was not finished for maybe another 5-10 minutes. When I forced a restart after maybe 15minutes, it did jump to the updating display on the Ionic for a few minutes, but then loaded back up normally.

Im curious what would cause some to brick and others not. Maybe its the mobile or desktop app that's causing the issue? Im on a Windows 10 Phone by the way.

[26Dolly]

Hello

I had the same problem when I purchased my Fitbit Ionic. I plugged it into the computer and let it  do its set up and it did. It took a bit but just plug it in and be patient. I have not had any other issues with it and that was almost a year ago. It works great and I love it.

[neptus1234]

I have tried to update my watch 5 times, 3 with my android and 2 times with my iphone and it appears to get to the install part and then goes into a reboot loop.  i've factory reset the watch everytime, deleted and removed the fitbit app and the watch from the app each time and still no luck?  is my watch bricked?

[theGman88]

Did something change with the alarm? It used to be that the watch would vibrate 3-4 times and then snooze automatically. This seems not to be the case anymore...now I have to touch the snooze symbol on the screen. Can I change this back?

[SunsetRunner]

For those people who are trying to update their watch by just using their smartphone, have you tried just doing it through a PC or tablet only?  I'm just wondering if the smartphone Fitbit app could be the problem.  Since I don't have an iPhone or an Android, I cannot really test the Fitbit apps on either one of those devices.  However, after looking through this thread, it seems that those who have updated recently through just their PC and not their smartphone seem to have had better luck.   Again, I'm not sure, but perhaps we can figure some of this out through the process of elimination.

[blackboxone]

The updating process seems working fine until after it finishes downloading and starts installing. It reboots, displaying the fitbit logo, after 5 seconds, reboots again and this loop continues forever.

What I have tried:

1. Factory reset, this is the only way to stop the loop and attempt another update. I have repeated this for at least 4 times.

2. Try installation through both wifi and bluetooth.

Any suggestion please. 

Chuan

[MultiMartin]

---

@EdsonFitbit wrote:

Hello everybody, thanks for visiting the Fitbit Community.

At the moment, there is no information about this situation. Once any update be available it will be communicated as soon as possible. If you are still experiencing difficulties please be so kind to follow these steps.

Keep on stepping.

---

This is unacceptable. My replacement device which I have had for 5 days has now bricked also! I cannot fathom how you can release software that does this. I have been a loyal Fitbit user the launch of the first Fitbit but don’t know how I can keep getting replacements which die complemently.

[STEWEE]

There is an update for the adidas app that now shows the previews

[Robyn-TWR]

---

N@SunsetRunner wrote:

Yes, terminology differs a little but the more I test and retest, it would appear our banks in Australia have not allowed for cross bank terminal support for Fitbit pay. 

Firbit it seems to be working well so I can only deduce our banks need to catch up here 

---

I’m not sure I agree with that. I’m in Aus and since the upgrade, Fitbit Pay no longer works for me. Doesn’t matter which EFT terminal the shop has. I’m leaning towards a bug in the firmware