Updating to the newest Firmware version 70.7.14

[SunsetRunner]

Hi all,

how is it possible that soo many users are having troubles updating their Versa's to the newest Firmware? I certainly will not deny their problems (cause they reported them), but to bring things into perspective: I have updated to the newest version three days ago on a officially unsupported device, e,g, the Oppo Reno 2. The installation over WiFi was easy and finished within10 minutes, after which I got the green succeeded icon and pressed confirm. The new version has two added apps over the previous version, e.g. the clock switch app and the calendar app. Personally I love the clock switch app, which allows you to store up to five CF's and change them on your Versa without going into the Fitbit app for it. I realize this message is bitter for all those users with problems, but I just wanted to let hear another sound, regardless of the fact that I do not understand why it works for me and not for all the others. To proof that I really have the latest version, see attached picture. 

Regards kuzibri

[SunsetRunner]

@SunsetRunner 

Below is the response I got when i asked if a patch was in the works and / or if Fitbit would be pulling the update like they did in October until the developers fix the multitude of issues users are experiencing after the installation if a bug ridden firmware. 

They acknowledged there are issues with this firmware due to all the reports they are receiving.   The right thing to do is for Fitbit to pull this firmware until the developers fixed the multitude of issues.  Especially the major battery drain.

I'm opting out of this firmware for now.  The enhancements are nice but not nice enough to risk my functioning Versa to get bricked.  No wonder users are looking at other options.

 

[SunsetRunner]

Hi @SunsetRunner , I have seen your message, that why I posted mine, to show that's possible to install it (proofed with a picture). I really do not know why I succeed in doing that and lot's of others not. I think that I succeeded cause I did the update over WiFi and not BT. Regards kuzibri

[pbug56]

To many of us it's not worth the chance of bricking or making nearly useless our Fitbit's by applying the October-November updates that came just before the one you describe.  I for one have found that every time I do a software / firmware update that something breaks or disappears.  As an example, it has been months since syncing didn't take multiple tries and even having to reboot the Fitbit.  Sure, we like enhancements, but we need debugged prior updates first, and we need to know that this latest update has been fully tested and debugged.

[SunsetRunner]

Hi @pbug56 , in an earlier post you mentioned that you were not able to use WiFi with your Versa. See this answer to this: https://community.fitbit.com/t5/forums/editpage/board-id/versa/message-id/145012.

Furthermore I need to mention that I never, but really never, had any problems updating my Versa and never bricked it. Possibly the key in this is that I always update over WiFi and not BT. Regards kuzibri

[SunsetRunner]

@SunsetRunner 

I've always utilized wifi for the updates via my compatible phone.  I've never had an issue. With this update there are major issues and I personally don't feel the enhancements with the new firmware are worth my Versa being bricked / unresponsive  and have issues with syncing and not receiving notifications. 

[SunsetRunner]

Hi @SunsetRunner , really do understand your decision and respect it, but as you have seen from my post with picture, it's possible to do it. Regards kuzibri

[pbug56]

How you update could be a problem. But the problems that many have seen
appear to be in the actual software, not how the update was done. Though
it could be both.

[SunsetRunner]

Hi @SunsetRunner and thanks for your message.  It would appear that updating over WiFi is the most reliable way to go, my wife's Versa 2 took about 10 minutes yesterday to update (though the phone - unsupported Nokia 7.1 - took several attempts to connect to the Wifi mind! 

[RottieLover]

I updated to the latest Firmware last week. I have no issues either. My phone is not on the list of compatible phones. It took me over 2 hrs to update, but there were issues on my end with my wifi/data connection. So far, everything is still working as it should. Actually, notifications are a lot better now than what they were when I first turned them on. I have syncing issues, but that again is b/c of non-compatible phone.Other than that, no issues. I like the new features.

[pbug56]

You've raised another issue - how can an Android phone of recent vintage
not be compatible for synching? All using recent versions of the same O/S
and the same software? That shouldn't be possible unless an app uses a
piece of hardware specific to some phone or manufacturer, and that should
not be the case here. Many different phones use the same or very similar
chip sets. Biggest differences between phones are the camera and screen,
and interface tools that sit on top of the O/S like the app launchers.
Older phones can easily be a problem because over time, Android evolves.

[SunsetRunner]

Hi @pbug56 , it's not the issue of recent vintage android phones, but whether Fitbit has your mobile device in their lists of supported devices. Mine is not in the list, yet, which means that can can experience problems on a lot of areas as the device in not tested by the Fitbit tech team for full compatibility. My mobile device is brand new and just released in my country, e.g. the Oppo Reno 2. I realized this possible problem between the device and Fitbit, but took my chances anyway cause: 1. The Oppo Reno is supported (although the 2 has some major differences and inprovements versus the Reno) and 2. you can always connect you Versa to your Windows 10 PC by installing the Fitbit app on it. Did that earlier and worked rather good. Regards kuzibri   

[pbug56]

Please explain to me how which recent (last few years, Android 8 and
higher) phone you have would affect sync, which does not do anything that
is specific to a given phone's hardware or software? We all use the same
OS, the phones share many of the same components. We all use bluetooth for
most sync purposes. Most of this is standards based. It's like PC's that
all have to have certain very like components, varying mainly in speed and
bandwidth and extra features. A program that runs on a low end PC will run
on a high end unless the developer doesn't follow the standards for
Windows, or in our case Android. Now if Fitbit were to not follow the
standards set for Android, then we would have a (preventable) problem.

[SunsetRunner]

Hi @pbug56 , the answer you will get now are these two lists: 

1. https://www.fitbit.com/devices

2. https://help.fitbit.com/articles/nl_NL/Help_article/2315.

Both lists speak for themselves. I have/get the idea that we are thinking along seperate lines and, thus, do not understand each other fully. Regards kuzibri

[pbug56]

So, like I said, most modern Android phones should be compatible. Yes,
it's possible that a manufacturer does not follow the rules and causes
problems. But when you get down to it, the problems so many people have
had are most likely due to problems in the update software and firmware,
not their specific phones. And what should be needless to say, old phones
(with older versions of Android like 7 or earlier) and PC's Windows being
more that about 2 years old should not expect to be compatible. So while
someone reporting a problem should confirm they don't have old equipment /
OS's to sync to, it's very clear that we've had major problems with the
updated software and firmware.

[SunsetRunner]

Amen, regards kuzibri