Fitbit OS 4.1.2 Firmware Update (70.7.27)

[MattFitbit]

Hello Ionic family!

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

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. 🤖

[SunsetRunner]

I did buy a Versa 2 this week. Still in
the box unopened due to this issue.
I'm going to be returning it,
unopened.

[lucaiuli]

I really think that this is a risk they are willing to take.
Remember that we are, let's say 100? here on the forum complaining about bricked Ionics, maybe 100 on Versa, and so on. The Fitbit user base is way bigger than that. So, I think that the way they updated the firmware and the number of bricked devices shows that it is a small price to pay for them as they continue to release firmware with "issues" on some old hardware batch devices.

The previous firmware bricked my Ionic, they sent me a replacement, and from the moment on I said I will never update my watch again. Now I do not update their iOS app either.

When your watch dies, it is gone for good. Even if you manage to bring it somehow to life, your next reboot or discharge will die again and then all you can do with it is to recycle.

Sorry, but that's just the way they are playing right now.

And boy... their replies here it just makes you wanna scream 🙂

[ComputerGardian]

@lucaiuli 

"So, I think that the way they updated the firmware and the number of bricked devices shows that it is a small price to pay for them as they continue to release firmware with "issues" on some old hardware batch devices."

My replacement was 34 days old when this happened. So I dont wholeheartedly believe that is completely accurate.

And fitbit had me send that replacement back to them so they can send me another one (long story, not relevant to the story) and I REALLY hope they dig into the watch and figure out what they did so they can fix it, but I'm sure they'll just clean it up and erase it put it back into their inventory for the next unsuspecting sole.

[Alldo]

Tried to update you all with my current feedback from Fitbit Support but they classed my post as Spam and wouldn’t let it post. 
basically they offered my 50% off a new Fitbit (why would I need to pay when they have broken my perfectly good tracker) or a Free replacement, I opted form the replacement Ionic - it arrived in about 3 days, switched it on by the usual left button and bang it came on. I tried to test it several hours later - switched it off, went to switch back on and the fault is back, had to hold left button and bottom right buttons, also battery already draining when switched off. Absolute waste of time - Save Your Money People. 

[ifatokun]

Sorry to hear this but not surprised. My wife's Versa2 also now messing about showing only the time, fortunately her's is only 6 months old so will be going back to retailer for full refund and goodbye to Fitbit🤬🤬🤬

[ifatokun]

👍👍👍👍

[LouAnnD]

Best Buy return policy is only 45 days. My Fitbit is 6 months old as well. I contacted Fitbit directly yesterday and the order has been placed for my replacement.

Sent from my iPhone

[Paintcheckref]

man thats aweful.. they emailed me back and indicated that they opened a ticket and will get back to me.  Lets see what happens??

[SunsetRunner]

The new versa 2 I just bought is now on its way back unopened. No more Fitbit for me, period. Used them for 10 years. No more. 

[ifatokun]

If you get a response then all that will happen is "we can offer you 25% or up to 40% off a versa and at some point at next update, until problems are fixed, your new device will brick again. Best advice is to cut your losses and explore other devices, there some excellent alternatives out there at same price and cheaper. Good luck. 

[ifatokun]

I hear ya, and I've just got my hands on my new Samsung Active2 watch. Looking and feeling good.

[SunsetRunner]

Thank you @SilviaFitbit  I've emailed the support yesterday just to find out what the status is. I haven't got a response. 

[Paulmac]

I’ve just done this & now my Ionic is working perfectly. 
1) Remove Ionic from Fitbit App
2) Unpair Ionic from Bluetooth  3) Perform a Factory Reset on Ionic 
4) Set up New Device in Fitbit App
The Ionic will download & install firmware, you will then receive notification about the update. Run the update and it will work perfectly 

[LouAnnD]

Nope, I did all of that. Ionic remained dead. My new one will go in a drawer until Fitbit gets their shi! together.


Sent from my iPad

[Paulmac]

Perhaps you could tell Fitbit they could use it as a suppository 
Paul McGavock0414745840

[ComputerGardian]

FYI dont know if this would be the reason why @Paulmac  this might have worked, but it seems fitbit quietly updated the fitbit app from 3.19.2 to 3.20.

I would try for anyone to uninstall the app and try redownloading the app and see if you get the 3.20 version (Help button) and then try again, I seriously doubt it will work, but its worth a try. I do believe the app has some part to play in this mess up.

[Paulmac]

I also deleted & reloaded the app. That could also be a reason why I had success where many others haven’t. 

[SunsetRunner]

I already have the 3.20 app and mine failed

[lucaiuli]

@ComputerGardian 

"My replacement was 34 days old when this happened. So I dont wholeheartedly believe that is completely accurate."

Maybe 34 days old from the moment you purchased it. Right? The device you bought "as hardware" is way older than that. Anyway... I'm working for a smart device manufacturer, too. It is not related to fitness trackers, but the idea is the same - you cannot make every hardware component by yourself, you have to source it from somewhere - that somewhere are real suppliers, some of them get out of business, some of them update/upgrade those components to much better/faster ones. You need to update your firmware software to be up to date with their requirements. If you cannot source a component from a supplier you have to find another one, that new one will not be able to make the same standard you need and so on...

You get yourself, as a smart device manufacturer, in the situation that you need to make a decision in order to keep selling the product you make - either create a new generation, either take the hit that some old batch devices will brick and continue with the same generation of products and the firmware updated for the new hardware batches.

You cannot create a new generation of devices if they are not different enough so the people could switch. Also, it is expensive to keep software development alive and on a high standards for all.

Maybe this is not the Fitbit case, I'm just saying what I think this bad firmware release might be all about... That's it.

Thanks

[Paintcheckref]

unfortunetly mine is already at 3.2