Fitbit OS 4.1.3 Firmware Update (70.80.0)

[MattFitbit]

Hello Ionic family!

We’re excited to announce the release of Fitbit OS 4.1.3.

We started releasing this new update 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 aren’t distributed based on region or location and can reach anyone no matter where you reside.

WHAT’S NEW AND FIXED

Read our help article for the latest updates.

HOW DO I UPDATE?

Find step-by-step instructions for updating Ionic here. 

If you run into any trouble updating Ionic, review these troubleshooting tips.

We appreciate your patience while we work to roll this out to everyone. Looking forward to hearing everyone's feedback in the comments below. 🤖

[JSIconic]

I reset my iconic to factory. The process forced the update. The clock works. Nothing else. No steps. No heartbeat. No sleep. I have cancelled my premium service.

Moderator Edit: Formatting

[Damons]

@Giampi71 

Keep up the good work!

[Paintcheckref]

I also had to do a factory reset. Everything came back on mine except the sleep function, it says It can't get a steady heartbeat so I received the simplified sleep details.So as I look at the tracker now, it is giving a steady heartbeat. Somewhat stumped on this one.

[Hubeekm]

MY iconic is slowly dieing.

First it was notification then somewhere to reset Iconic which was done now it does not do my heart rate now.

Notifications not working.

And now it can not even update after the first one. Have started with messenger and now gone to email but nothing in 24 hours.

BEWARE doing updates when they are not checked. 

[Seaescape]

Terrible update! Killed my Ionic, and nobody at Fitbit cares! Tech support told me it was dead after 30 mins of trying useless ways to fix. Your update killed it, and was told to buy a new one. What a great update!! Very upsetting. Then, when I inquire more..... no one wants to help.  I never thought Fitbit was this greedy. I guess if you have a bad update - kill a few hundred watches - sales go up?!? Terrible customer service!! Wow!!!! If Their update ruins our watches, shouldn’t They make it right? I’ve been a loyal fan/customer/advocate for years.... and this is how they treat us?!? Shame on Fitbit!!

[UserRoslyn]

Thanks @Markyzs180 for the instructions, I didn’t know how to do a factory reset without the watch screen. A case had been raised but all I was told was to charge the watch. Once I had the watch back working using your instructions I haven’t updated. Still on version 27.70.8.0 and not budging until Fitbit fixes all the issues with this update. 

[Hubeek]

I agree there should be checks before a release is done.

[Piste]

I did the upgrade and now my Ionic does not accurately record my sleep. It misses at least two hours (usually the first two) every night.  I am a Veteran, currently in hospital being treated for my PTSD, and the upgrade has completely screwed up the sleep tracking.  You might think that this is a trivial matter, but when one is already suffering sleep deprivation and the staff are relying on the Ionic to give them semi-accurate sleep data, it becomes a health management issue. Please don't demean me by telling me to reset the device blah, blah, blah. I upgraded before I came to hospital and now the medical staff are having a difficult time trying to prescribe the appropriate sleep medication. It worked well before the upgrade - thanks for nothing Google and Fitbit!

[Icedancer]

Since the update I have two problems with my Ionic.

The GPS takes forever to connect. Sometimes it does not connect.

If it picks up I am running on auto it does not connect to GPS at all and all I get is a time.

The reminders to move no longer works.

On a separate issue, the sleep function is very flakey. It frequently does not record my sleep correctly no matter where in my wrist its located or how loose or tight it is.

[YojanaFitbit]

Hi everybody, once again thanks for being part of our family and provide rich feedback to us. 

Your voice is being heard . We're actively reviewing your responses and providing feedback to our product development team. We really like to see you here in the Forums. Our goal is to foster a pleasant and collaborative environment, so please just keep in mind that you can share your comments in a constructive way and relevant to the topic.

As mentioned before if you already have a case open for this situation, please keep communication open with our team. They will be getting in touch with you. About Fitbit warranty, you can read more details about it here. Or you can reply to the last email from our team, as they are in charge to check these details according the case.

@Hubeek thank you for sharing this information. I've requested a case on your behalf, our team will be getting in touch with you as soon as possible. We really appreciate your patience.

@Piste and @Icedancer I really appreciate that time you took to report this issues with your Ionic. Please confirm that you've followed the suggested steps for each one of the issues that you're Fitbit having. If you already tried those steps, please confirm that you're phone and Fitbit app is running the latest update and provide with a screenshot of the issues that you're facing. Thank you in advance for your help.

I'll be around. 

[MikeDmyterko]

I finally made it work. Restore to factory settings first.  Then I spent an entire day trying to get it to sync. That didn’t work until I disconnected it from my Bluetooth settings on my iPhone. I forgot it the device. Then went back set up a new ionic and voilà it synced. I now have full settings again.

[RBGUS]

All I had to do was re-connect the device. My system is working fine now

RB Gustavson MPH, RN, CHRNC-A, CWCN, CHT-A, CRT

[YojanaFitbit]

@RBGUS and @MikeDmyterko thank you for sharing this information. We're glad to know that you're back on track.

[Chereda]

I’m having an issue with my watch since the most recent update and I feel the same way. I’m just gonna order an Apple Watch. I tried getting support through twitter and the responses are too slow. I called in and was told to use Twitter or that they would offer me 25% off a new device. The watch was working before the update. 

[Hans2vt]

My GPS is now dropping parts of my route. Never did that before. Wondering if that is a new issue introduced with the update. 

[ghate56]

So, my iconic is still "bricked" and I have tried a couple other things that some folks have pointed out and some that hasn't. I let the battery get totally dead, beyond the "low" battery charge me screen. It still pops up but only after the battery (I assume) has dissipated enough to warrant the screen pop up. I have left it totally dead where the screen hasn't popped up, connected to the charger, let it charge all the way ...at least a day. Don't know for sure since the screen wont come up. I attempted to do the factory reset and still nothing comes up. When the battery dissipates, it shows the low battery screen again until it totally goes dead. It really is bricked like the other folks on this forum. I'm pretty sure fitbit is going to accept the loss of customers for this since its their software update that caused this. I think these devices aren't meant to last beyond a year. Fitbit will not be repairing or replacing these out of warranty, bricked units. They could, probably enough back stock, but we would be in the same boat again on further updates. They would rather accept the loss of a customer and move on than to pay for a repair. The want recurring revenue anyway. Only way for you to feel better about the situation is to purchase from another brand and discontinue any subscription service you were using from fitbit. Let everyone know your experience, point them to these forums, point them to twitter, point them to the comments in facebook to help them make an informed decision about a purchase. While I didn't like how the iconic issues were handled, it was a comfortable watch to wear. I think that's really the only thing I can say I really liked about it. I dealt with all the bugs and issues that didn't work,  I was used to it being flaky and flawed. If Fitbit truly valued the user and their brand, then they would own the mistake, make it right, and retain the customer base...which is probably why google bought them anyway. I'm trying a garmin vivoctive 3 music and so far the only complaint I have about it, its not as comfortable as the ionic. but it works, the features work, its fast, but then again...its new too. I made my vote for garmin after the responses I see here and from support about the issue. I'm still keeping the ionic in case some how a fix  comes out. It will just gather dust with the other fitbits I have purchased.

Editado por moderador: Título actualizado para claridad.

[SunsetRunner]

After a few days, a support staff did contact me and offered the standard script of 25% off a new device. I declined and ask the issue to be escalated. For me, It’s doing the right thing. We all know Apple and Samsung watches are far superior than Fitbit.  If I leave the Fitbit ecosystem, that’s it. Whether corporate Fitbit has the vision of a long term relationship will be determined. 

Apple Watch 5 is nearly $100 off now...

[Mcpro7]

Watch was working perfectly until yesterday afternoon when I did the update. Watch is now dead, stuck on the fitbit logo. I’ve restarted it, let the power drown out and then plugged it in to recharge, nothing  works. I tried unsynching it from my phone and synching again but I can’t because the numbers won’t show up on the screen. Can’t do a factory reset since the screen is stuck in the Fitbit logo. This is my second Ionic in 2 years. Very disappointed with it. 

[Chereda]

That is my exact situation.  I'm very disappointed as well.  I do think it is only right for Fitbit to correct this situation as soon as possible.  It is evident that the update has a glitch.

[Chereda]

Is there a way to address the concerns or issues with device?