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

Sense 2 battery goes to 0% after shutting it down

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

I have had the Sense 2 for almost a month, and it seems like whenever I shut it down from the settings menu, and just leave it (not on charger), when I turn it back on, it reflects a battery percentage of 0. I have to then hook it to the charger for 10 to 30 seconds and then it will register the actual battery status. Most recent example is this evening, I turned it off because I was waiting for a new band and wasn't wearing it. When I turned it back on before bed, it reported 0% battery, I charged it yesteday. In the past it has actually turned off automatically after reporting the 0% so I had to put it on charge, then after a little bit, suddenly it had 94% battery life. It is annoying, but hopefully it can be fixed in a patch if other people have the same issue? (maybe that is related to the complaints that it discharges when it is off? It isn't actually discharging, just isn't registering correctly when it powers back on.)

 

Moderator Edit: Clarified subject

Best Answer
10 REPLIES 10

Hi there, @TechNerd42. Welcome back to the forums.

Thanks for the detailed information, and your efforts while charging it. I understand the issue is with the battery level not showing up correctly after turning your Sense 2 back on and to see if it helps, please try restarting your watch and follow the rest of the steps described here. If the issue persists, let me know so I can continue helping you with this matter.

Best Answer

I switched mine off in "Settings", same happend Battery shows 0%, waited for five minutes, still reports 0%, attached it to the charger and after 15 to 20 seconds battery status showed correctly. I guess this must be a bug, and hm @LizzyFitbit , shutdown from settings is a restart 😉

Fitbit user since September 2019
Sense2 Sense, Charge3, Android, Windows
Best Answer

@LizzyFitbit is anyone testing those devices at all? 🤔 this is a bug that appears first time right after the very first startup when user takes watch out of box and turns it on. For a while, the battery indicator shows 0% and after some time it jumps to real value. The same happens after shutting down and restarting the device. You want to tell me that the bug that hits you in face on first startup of device went unnoticed? I'm sure you must have access to the Sense 2. Why don't you try it yourself. The bug takes seconds to reproduce. Here:

20221028_072132.jpg

with 71% of battery which shows up a few minutes later correctly.

Best Answer

@t.parker @LizzyFitbit , I got curious what happens if I instead of connecting the charger, restart the device? I have long press shortcut enabled, and set to start a walk.When I kept holding the button. it did not restart, it reset Sense to Factory settings (!). When it had reset, I tried again, but with shortcut set to "Off". It restarted as it is supposed to, and showed correct battery%.

 

Lizzie, are bugs we find escalated, or am I just wasting my time?

Fitbit user since September 2019
Sense2 Sense, Charge3, Android, Windows
Best Answer
0 Votes

Congratulations on your new job as a software validation engineer!  Google has a very generous bug bounty program.

Best Answer
0 Votes

Ha ha 😅, I validated software for a Norwegian company 25 years ago. I find it kind of fascinating to find bugs, especially those who doesn't make any sense at all. But, if they don't look into bug reports, it's just a waste of time. 

Fitbit user since September 2019
Sense2 Sense, Charge3, Android, Windows
Best Answer
0 Votes

Now that Google owns FitBit I would suggest looking into Google's bug bounty program and not FitBit's especially with the Pixel watch launch.

Best Answer
0 Votes

I continue to have same problem with my Sense. It's less than 1 year old.

Best Answer
0 Votes

@TechNerd42 same thing over here, i'm tired already 

 

Best Answer
0 Votes

Hi @RichInArizona - this is the Sense 2 forum, you may have a different issue, as it doesn't have this bug.

Hi @Micheal_javier - the initial firmware had the 0% bug but you may find it fixed in the latest firmware.

Author | ch, passion for improvement.

Best Answer
0 Votes