help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Versa screen won't turn on

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎02-13-2021 13:59 - last edited on ‎02-14-2021 13:34 by

‎02-13-2021 13:59 - last edited on ‎02-14-2021 13:34 by

I woke up one morning and my Fitbit Versa would not turn on. No problems prior to that, just stopped working. The screen then kept flickering on and off. I left it alone for a day and it started working again but only when it was on charge. As soon as I take it off charge it turns off. It has 100% battery and will still connect to my phone when on charge. I have restarted it and done a factory reset but no change. It's like as soon as it comes off of charge it turns off immediately and then when I place it back on charge it turns on again. Cannot work out what is going on! I see other people have had this problem recently and therefore could this be due to the recent update? Does anyone knows how to fix this problem or just what could be causing it?

 

 

Moderator edit: subject for clarity 

Best Answer
Labels:
0 Votes
1 REPLY 1

‎02-13-2021 22:26

‎02-13-2021 22:26

Seems like this is quite a common issue. following the recent updates, as it was working fine before.

In which case its probably best to inform Fitbit Support directly. They may be able to help you.

Author | ch, passion for improvement.

Best Answer