09-14-2023
18:59
- last edited on
09-15-2023
04:48
by
MarreFitbit
09-14-2023
18:59
- last edited on
09-15-2023
04:48
by
MarreFitbit
Can't restart. Can't get help. Just happen today.
Moderator Edit: Clarified subject
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Hi there, @wcherry1964. Welcome to the Fitbit Community Forums. Thanks for the details provided in your post about the issue with your Sense. I'll be glad to help you with this.
If you haven't done so yet, I suggest trying the steps below in the order listed:
With the steps above, what I want you to do is to pair your Sense first to your phone's Bluetooth settings before any other Bluetooth device is connected to your phone.
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
Best Answer
09-17-2023
16:10
- last edited on
09-20-2023
08:31
by
ManuFitbit
09-17-2023
16:10
- last edited on
09-20-2023
08:31
by
ManuFitbit
Same with me. This seems to be a problem multiple people are having. I wish there were a solution that actually fixed it. I was just offered a discount on a new Fitbit since mine is out of warranty.
------
I now have tried twice to let the Fitbit die completely. Yesterday I couldn’t get it to charge. Today it started charging- yeah- but now I’m stuck on the Fitbit logo again. 😩 not again. And it won’t let me do a restart or factory reset
Why is everyone's doing this?? Mine is doing the same! Did they do some update or something to force us out of our watches and get new? I don't understand how all of us all of the sudden can't use our watches and stuck on logo and nothing is making it go away! This honestly has to be something the company did and did on purpose! Very frustrating!
I thought I was the only one this was happening too until it also happened to me. Tried everything and ultimately decided to upgrade to a Sense 2. It doesn't have that problem, but really this problem should not be happening on the Sense at all.