09-05-2019 14:47
09-05-2019 14:47
I never updated to the 3.3.1 update that bricked a lot of versas and/or made them have a multitude of issues after reading all of the frustrations and lack of response from Fitbit. Mine is on the 3.1 version I believe with the occasional syncing issues. I set my phone not to do the automatic updates from Fitbit.
For those who have downloaded the android update - 3.5 version of August 30th, are you able to sync without any issues or does this version still have bugs? Not willing to have my Fitbit bricked or not not work properly if this is still an issue.
Will probably start looking for other options once this Versa dies.
09-05-2019 15:09
09-05-2019 15:09
Hi @SunsetRunner updated yesterday (Samsung Galaxy 8m Android system 9) and all is well. Many posts on the forums confirm that Android users are doing great.
09-05-2019 15:19
09-05-2019 15:19
Hi @Odyssey13 , thank you for responding. I'm on a Samsung 7 operating on Android system 8. I was just wondering if this would work without any issues. I would hate for it to brick my Versa and / or render it useless.
09-05-2019 17:03
09-05-2019 17:03
@SunsetRunner if you're not sure, then wait a few days and see how things go for others on that system. I have friends with newer Android phones (not Samsung) and they seem to be doing well.
09-05-2019 17:30
09-05-2019 17:30
I have a Charge 3 and a OnePlus 6T. I went to 3.5 last night and it did even out functionality for me.
As a caveat, when I went to 3.5 I did go to set up a device and answered yes to replace the Charge 3 that was there. Once I did that, then all was good.
09-05-2019 17:48
09-05-2019 17:48
My Galaxy S7 running Android v8.0.0 is a bit slow to sync with the overnight numbers but always comes through.
My only issue with 3.5 is it keeps refreshing step count, active minutes, and calorie burn. Even when I’m sitting still those numbers refresh and repaint those 3 icons. I have all-day sync and always connected turned off. If that’s the worst I get out of this update I’ll be happy.