Fitbit OS 2.1 - Versa Firmware Release (32.32.10.15)

[AlessFitbit]

Fitbit Update 8/23/18:

Hey, everyone! Just wanted to thank you all for your participation in this thread. 

Since the majority of Versa users have successfully updated to OS 2.1.1 (v32.32.10.15) I have decided to close this topic from further comments. 

If you still have not updated your Versa to OS 2.1.1, check out this help article for how to update your device. Please complete this update so that you're prepared for the next release. 

If you are experiencing an issue with your Versa unrelated to the firmware-up process, I invite you to start a new topic on the Community or find a related topic. 

Thanks for all your feedback and contributions on this thread. We're looking forward to bringing you all the next Fitbit OS update! 

---

Fitbit Update 05/11/2018: We have released Fitbit OS 2.1 to 100% of Versa users (Firmware Version: 32.32.10.15).

---

Hi, everyone! 

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

We've started to roll out this update to 10% of Versa users. This is a progressive rollout, and all Versa 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?

WHAT’S FIXED

This release includes other bug fixes and improvements.

Step by step instructions for updating your Versa can be found here.

I recommend updating your Versa 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 Versa to Wi-Fi, check out this article. 

If you run into any trouble updating your Versa, 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! 

[BetroD]

Will we be able to reply with Apple devices? 

[meresydotes]

Question for people who got the 20 version by doing a factory reset (rather than being "new users" - for a month old device!) - did you delete the Versa from the app and add it as a new device, or just add it as a replacement? I did a factory reset and just got the 15 version again, but I just did the latter process.

[razerf15]

---

@meresydotes wrote:

Question for people who got the 20 version by doing a factory reset (rather than being "new users" - for a month old device!) - did you delete the Versa from the app and add it as a new device, or just add it as a replacement? I did a factory reset and just got the 15 version again, but I just did the latter process.

---

Deleted the Versa. See my long post on page 11. 

[meresydotes]

@razerf15 THANK YOU! I actually called support and they didn't even KNOW there were two releases...

[razerf15]

---

@meresydotes wrote:

@razerf15 THANK YOU! I actually called support and they didn't even KNOW there were two releases...

---

You're very welcome. I'm not surprised, lol. 

[duck_puddle]

@meresydotes Just FYI-I followed @razerf15‘s Post after the initial push via app but still ended up with .15.  I’m not sure if somehow Fitbit knows it already gave me .15 and forever .15 I shall be?  

I think that’s not worded well.  I got .15 via normal app push.  That rendered my Versa unusable so I then decided to follow @razerf15’s post - which installed .15 again.  

[razerf15]

@duck_puddle, that's interesting. I wonder if .15 and .20 are region specific. I'm currently in UK. However, like you said, your Versa could be tagged as updated and thus giving you the same .15 - the irony is that no one from Fitbit really knows the difference between the two and as @meresydotes stated, don't even know another firmware exists. 

From what I know about the cloud, I feel like the .20 update has been uploaded to a different server/database directly linked to new device updates, and the .15 update is uploaded to some server/database directly linked to app updates. Just speculation since it makes no sense to have two random updates that are "identical." In the IT world, that's just redundant, and redundancies are only put into place in case of crashes/data loss; this leads back to the two different servers speculation. 

[meresydotes]

@duck_puddle Thanks for stopping my madness. The factory reset is kind of a pain. Mostly because it takes more finesse than I have to get the app icons in the state where you can move them, rather than opening the app.

After spending most of a 45 minute call to support on hold, I got an email from the supervisor I insisted on speaking with saying the 20 version would be released to everyone, but with no timeline.

I guess there's going to be another firmware release eventually, I just find it astounding that they have a release available that fixes a known problem and they won't supply that release immediately to anyone complaining about that problem.

/end rant.

[Myrdhinn]

Personally I think it's pretty shabby Fitbit is giving new users the latest firmware and leaving those of us that bought since the Versa was available out in the cold. Well excuse me Fitbit but most of the fixes and work arounds have come from the community, not just the same old, same old canned response from the company trolls. But I get it, the newbies might not even know their new Versa is not operating up to snuff and think the behaviour is normal thus giving glowing reviews on Amazon, Best Buy, etc.   Ces't le Vie.

[meresydotes]

Yeah, I kinda understand it when the cable company offers a discount to new users - they're trying to lure you in. Providing the most updated software to all users can't cost Fitbit much of anything at all.

[razerf15]

---

@Myrdhinn wrote:

Personally I think it's pretty shabby Fitbit is giving new users the latest firmware and leaving those of us that bought since the Versa was available out in the cold. Well excuse me Fitbit but most of the fixes and work arounds have come from the community, not just the same old, same old canned response from the company trolls. But I get it, the newbies might not even know their new Versa is not operating up to snuff and think the behaviour is normal thus giving glowing reviews on Amazon, Best Buy, etc.   Ces't le Vie.

---

I'm in agreement with you, which is why I did the force update. Fitbit moderators all over including older forums for older devices said it wasn't possible, which is why I research as much as I can for alternate solutions. I've had the Versa like you since it was released. I bought it knowing full well how much Fitbit as a company isn't very up to date with the rest of the competition. It was a purchase simply to replace my best smartwatch to date (Pebble Time Steel), which they are shutting down support for in June 2018. I have gone back and forth between this watch and the Garmin Forerunner 645 because both have NFC (a big feature I wanted and use frequently) and sleep tracking (very important). Garmin didn't support my bank and had no nearby future plans to either. I knew quick replies were coming in May so I took a gamble since nothing better was in the market. They have a long way to go, but so far on 32.32.10.20, my Versa is rock solid. Battery life is what is expected (better than my other smartwatches except the Pebble - no one beats battery life of always on e-ink displays). I think Fitbit made a huge mistake not putting a mic on the Versa like the Pebble Time Steel. It works very well and would have made quick reply issues less cumbersome. I hope to see this on the Versa 2 unless something better comes along. 😊

[duck_puddle]

---

---

To be fair, Garmin tends to do the same thing with their top of the line new devices (like the Fenix 5 release last year).  The difference is that they are releasing a device that is targeted to a relatively hard core/devoted group of users who have years of training data tied up in their Garmin accounts and probably have hundreds (or thousands) of dollars in assorted training products purchased because of their compatibility with Garmin units.  They also will pay premium money for a device that will help them get their Vo2Max from 57.4 to 58.1 over 6 months.  In other words, an extremely devoted user group with very specific needs that are only met with that (or another) Garmin device.  They can use their early adopters as beta testers because those users have no alternative and they are going to stick it out anyway.  

At this price point, Fitbit is NOT marketing to that user group, nor do they have the market cornered on devices offering these features.  Garmin, Samsung, Apple, et al all offer similar devices at similar price points.  Fitbit DOES shine in the battery life department (among similar units), but for those that don’t put a premium on a watch with multi-day battery life (or ability to last a many-hour GPS activity), there are lots of other options.  

[luvswhippets]

I've tried everything but the firmware update still won't work.  I've tried both bluetooth and wifi.  I'm connected to both.  I also tried to update using my phone and then my tablet with no luck.  My phone and tablet are Samsung.  Help!

[AlessFitbit]

@luvswhippets Hey, there! 

Sorry to hear you're having trouble completing the firmware update for your Versa. To begin, I would make sure you're running the latest version of the Fitbit for Android app: 2.71. It is important to be on the latest version, but also make sure you are connected to Wifi as it is a speedier download than with Bluetooth. Restart your mobile device and restart the watch, make sure you have it connected to the charging cable so the battery level does not interfere. If you continue to have issues, please let me know where in the process you get stuck. 

For everyone else, I would like to make it clear it's not possible to force an update to firmware: 32.32.10.20. We're working hard to make it available to everyone, but for the time being the latest firmware version available is 32.32.10.15. Please update your Versa's to this firmware. I'm reporting back any issues and appreciate you all cooperating with this firmware release. 

[Ver0B8519]

I was able to force the update. And it works perfectly for me.  I can answer, ignore and return missed calls. I have quick replies. Not missing any notifications. No problem with GPS or "ghost steps". I have an android device Samsung s8. Only thing is when I forced the update, I lost all music I downloaded. Takes forever to transfer so I will have to redo that another day. 

---

@AlessFitbit wrote:

@luvswhippets Hey, there! 

Sorry to hear you're having trouble completing the firmware update for your Versa. To begin, I would make sure you're running the latest version of the Fitbit for Android app: 2.71. It is important to be on the latest version, but also make sure you are connected to Wifi as it is a speedier download than with Bluetooth. Restart your mobile device and restart the watch, make sure you have it connected to the charging cable so the battery level does not interfere. If you continue to have issues, please let me know where in the process you get stuck. 

For everyone else, I would like to make it clear it's not possible to force an update to firmware: 32.32.10.20. We're working hard to make it available to everyone, but for the time being the latest firmware version available is 32.32.10.15. Please update your Versa's to this firmware. I'm reporting back any issues and appreciate you all cooperating with this firmware release. 

---

[razerf15]

I forced the update from 32.32.4.19 to 32.32.10.20. There is plenty of proof in this thread regarding this. We'll discredit 32.32.10.20 if you actually know and understand the difference between the two current firmwares. @meresydotes, maybe you spoke to @AlessFitbit on the phone when you said they had no clue 32.32.10.20 existed. 🤔

[0hwell]

I don't know this for sure but if someone wants to try it here's my theory on getting 32.10.20. I forced mine and I think it worked because I did not yet have the update flag from fitbit but now everyone has been sent that flag. What if you did a factory reset than created a new account than set up your watch on the new account, this may give you the newest firmware. than maybe you could remove the watch go back to your original account and add it as a new device again just don't reset it. Now this may not work and I don't want to try it myself because I already have .20. Again it would be a lot of messing around and maybe could mess up your watch or account so its at your own risk. I think it would be best to wait for fitbit to push .20 or something newer to everyone.

[Skylan]

Has anyone else had issues with the update causing the battery percentage to always be the first thing you see when you look at your watch, and not your chosen watch face? When I turn my wrist toward myself, the screen doesn't pop up. I have to click the back button or touch the screen multiple times to get it to turn on and then when it does, it has the battery percentage in huge font and the time written tiny in the upper right hand corner. I have to click the screen to make this go away and go to my chosen clock face, which shows me this information anyway. 

I find this part of the update incredibly annoying and am wondering if there is a way to turn this function off?

[razerf15]

@Skylan

Haven't read about anyone having this issue.

1) What clock face are you using? 

2) What's your battery level when this happens - low battery or all the time? 

3) What's your current watch firmware? 

[DesiBoy]

I tried the post of page 11 but no luck. tried new account but still it's coming version 15 only.