09-13-2018
05:53
- last edited on
09-16-2018
04:31
by
AlejandraFitbit
09-13-2018
05:53
- last edited on
09-16-2018
04:31
by
AlejandraFitbit
Hi, got the Versa as a birthday gift just over two weeks ago, and my experience thus far has been pretty poor all told.
Barely a day goes by without me having to restart the watch, toggle Bluetooth, restart my phone and goodness knows what else to get the watch to sync or receive notifications. At one point, I had to set the watch up again, and wait another half hour or so while it reloaded the firmware.
After finally getting my credit card into the wallet, it has disappeared from my watch on more than one occasion (while still visible in the Fitbit app), necessitating the re-installation of the app and more toggling on and off of the phone, watch and app. The issue with the card not appearing on the watch was only resolved (as per a suggestion here) by reloading another card, as I only have one, I had to add that again so now have two identical cards there.
Setting up music was similarly problematical in trying to establish a WiFi connection, and when I did it then took an inordinate amount of time to transfer any tracks. Then after I did, listening to the first one or two tracks was fairly good on my quality headphones, but playback soon developed an annoying whine which made it unlistenable.
I’ve also noticed the watch restarting itself when wearing it, apropos of nothing at all. To cap it all, yesterday I noticed it was around an hour and seventeen minutes slow and no timezone setting will fix that. Switching it off and again going thru many hoops to get it to re sync seemed to resolve that. At times, it’s also slow to waken the screen after pressing the left button. To cap it all, the screen display was corrupted (like the screen shear older Pebble watches suffered from), but again that has settled after a restart.
I’m a retired technical manager who is very au fait with technology, and it seems I’ve spent more time here and on Facebook investigating my issues, and have gone thru all suggested solutions to the many issues I’ve faced with the Versa, so any suggested calls to support to progress this would be frankly just wasting my and their time.
From these forums, it seems the issues I face aren’t unknown or perhaps even uncommon, and would suggest some manufacturing or firmware issues, maybe even (or hopefully) restricted to one or more batches. Rather than going down the return route at this point directly with Fitbit, I intend taking it back to the retailer for at least a swap if not a refund. It’s just that my experience (particularly in light of the comparatively sterling performance I get from my three year old Pebble Time Steel) would suggest I might face some of those issues again.
Moderator edit: subject for clarity
09-16-2018 04:34
09-16-2018 04:34
It's great to see you around @Brantome.
I appreciate all the efforts in trying to fix the different issues you are experiencing with your Versa and recommend taking a look at the following help articles and follow the instructions provide in them:
Also, I recommend checking our list of compatible mobile devices to see if yours is listed.
Let me know how it goes.
09-16-2018 05:28
09-16-2018 05:28
Hi, thanks for the reply.
As mentioned above, I have a technical background and have been thru all the links you mentioned and more. My phone is an Honor 10 on build 8.1.0.146 which I accept is not on your compatibility list although its predecessors are. As it was a gift, I didn’t have the opportunity to validate this, but as a long time Pebble Time Steel user which still works with my phone (indeed, it receives the phone notifications the Versa doesn’t), I really wouldn’t have expected the difficulties I’m facing.
Also, several of my issues do appear to be watch related, independent of the phone I would have expected - for example, the restarts, slow response, wrong time and screen shearing.
I’m still waiting on my nephew to send me the watch receipt as I’m still seriously considering returning it to the retailer for a swap or refund.
Thanks again
09-21-2018 04:25
09-21-2018 04:25
Just had an email prompting me to mark a response here as an accepted solution. A list of actions to overcome circumvent bugs in the firmware unfortunately doesn’t cut if for me. An acknowledgement from Fitbit that they’re aware of the underlying issues and are working to fix them might begin to approach an acceptable interim solution.