12-26-2019
14:18
- last edited on
09-29-2020
20:25
by
MatthewFitbit
12-26-2019
14:18
- last edited on
09-29-2020
20:25
by
MatthewFitbit
Hi, just got a Fitbit Charge 3 and the thing will not turn on. I have tried plugging in the charger, pressing the button. Nothing works. It vibrates but nothing appears on the screen. Does any one have a suggestion?
Thank you
Moderator edit: subject for clarity
12-26-2019 06:04
12-26-2019 06:04
Hi!
When I flick my wrist towards me to see the time the screen rarely turns on, meaning I have to manually press the side button to turn on the screen. Someone suggested increasing the sleep sensitivity but I have an Android and so can't find that setting on the app.
Any help would be greatly appreciated!
12-26-2019 12:54
12-26-2019 12:54
So, I have tried resetting the device and changing the clock face. The blank screen has happened before but resetting it always worked. Now, still a blank screen. It has been a year to the day since I got it.
12-26-2019 19:54
12-26-2019 19:54
Hey, I've got a charge 3 the screen became unresponsive and when I try to restart it I get a very small vibration telling me its plugged in but then it either doesnt do anything no matter how long i hold the button or it vibrates for the entire time I hold the button but screen never comes on and nothing else happens, cant get it synced to my phone cant do a factory reset any ideas?
12-27-2019 03:34
12-27-2019 03:34
Hey @SunsetRunner, @Stormwsong, @andreia__ and @Felony_tattoos, welcome to the Forums.
I understand how are you all feeling and appreciate all the efforts in trying to fix this turning on issue. I recommend taking a look at this post and make sure you have followed the instructions provided there.
Let me know the outcome. 🙂
12-27-2019 03:57
12-27-2019 03:57
Hello,
i am am having the exact same issue, with the small exception that when it died it hadn’t a 70% charge, and randomly started vibrating at 4am. It’s been on charge for a few hours now but no joy.
01-01-2020 08:13
01-01-2020 08:13
Since I had mentioned that I had tried reset my device already, no, it didn’t work.