Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Sense battery drains quickly

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

My Fitbit sense has recently been draining even faster than usual. It is about a year old. I have turned off all day sync, notifications and pretty much anything I think might be draining the battery. I’ve also reset factory settings, deleted the device and added it back, tried charging in regular outlet vs a usb dock. For the last few months the battery has been lasting about three days with most functions off, no all day sync and no always on etc, but today I took it off the charger when I headed to the gym, I was there for two hours and when I returned my battery was at 20%. It still charges all the way quickly, so it appears to be charging as expected. The only thing that’s different is yesterday I added the snore detection feature (if that is what is draining it then perhaps it shouldn’t be a feature until you guys figure out how to not have it devour battery??? Just a thought). I’m literally starting to consider going back to Apple Watch because if I can only get one day out of the charge then I might as well. Battery life is by far the main reason I’ve had fitbits pretty much since they hit the market but a one day battery life makes it pretty much a wash with other devices. I had this issue when I first got the watch also, but I’ve tried everything I did then. I love my Fitbit, but I hate looking down and seeing it needs a charge just hours after it was fully charged. Please help! 

 

Moderator Edit: Clarified subject

Best Answer
0 Votes
2 REPLIES 2

Hi, there are several main issues that drain the battery quickly;

  1. Snore detection [remove]
  2. SpO2 tracker App [uninstall] or SpO2 clock face [change to a non SpO2]
  3. Clock face bug [change clock face]
  4. Fitbit App bug [disable Bluetooth]

One of those is probably the reason but you can consult the help page for other options.

Author | ch, passion for improvement.

Best Answer
0 Votes

This was happening to me when I had a brand new watch and not much loaded on. I discussed it with Fitbit support who said it was my iPhone and they were waiting for an update. In the end I loaded the app onto my iPad and things were much better. I have since got an iPhone12 and the same thing happens if I load the watch onto that and the original problem was in June 2021. No update then 🤷‍:female_sign:

Best Answer
0 Votes