09-05-2019 12:11
09-05-2019 12:11
My fitbit versa has been great, just over a year old and have had no issues at all until yesterday. In the morning I noticed my screen was a little darker, more pixalated looking but thought nothing of it. Then a few hours later I noticed it had some verticals lines showing up and was still a tad darker than normal. By the end of yesteday nothing will display on the screen. I can tell it tries to, but cannot make anything out. I've tried restarting and factory resetting it with the buttons and by the little light that it does display but I can't see the logo when it turns on. I feel so let down, as I saved money to get the special edition versa and just after a year it stops working. I cannot afford a new "smart watch" every year. I'm also really wondering why so many others are having the same issue, was there just an update? I see they just announced versa 2...any coincidence my watch failed just days after the announcement for the new version?
09-05-2019 15:14
09-05-2019 15:14
Hi, there is no coincidence with the Versa 2 announcement, happens to other users of the Versa 1 also. You already tried all the known solutions to solve the problem, so contact Customer Support with your problem. Good luck, kuzibri
09-06-2019 06:58
09-06-2019 06:58
@SunsetRunner - It is a coincidence. Please keep in mind that Fitbit has over 25 Million active users. We see people with problems in these forums because rarely do customers post to say ... “Wow! Everything is working.” Let me say that I have been using Fitbit devices since at least 2004. In all that time, I’ve had two problems which Support quickly resolved. I’ve been using the Versa and Versa Lite through all the various updates. No problems so far.
09-09-2019 05:55
09-09-2019 05:55
So I really didn't get much help besides being told to restart it, which I've tried. I looked and my app updated the same day the display stopped working. The watch is still fully functional besides the display. And I had it flash a bit so I'm not giving up hope. But I do think this is a glitch not a device failure.