search

xmikos / SnooperStopper

Android device ecryption password manager and failed unlock attempts monitor
GNU General Public License v3.0
48 stars 7 forks source link

Causes battery drop after reboot #12

Open rugk opened 8 years ago

rugk commented 8 years ago

I'm using CM13 and I have read https://github.com/xmikos/SnooperStopper/issues/8, but I have a different issue.

Because actually my device is not encrypted. However the reboot option still works (as I expect it), but strange things happen when it is triggered.

Because actually my battery level drops of several percent after rebooting the device: snooperstopperreboot

I could reproduce it too times (and only realized it was caused by this app the second time) and afterwards I had to recalibrate my battery. As you can image I'm not really keen on reproducing this again...

licaon-kter commented 8 years ago

It's normal, a boot sequence consumes a lot of battery (presumably because it will use full speed). Do try a reboot test with this app disabled, my guess is you will see the same thing.

/close as invalid

rugk commented 8 years ago

Have you actually looked how much the battery drops? (from estimating my own picture I'd say it is from 40% to 10% - in a very fast time)

I do not need to disable the app to reproduce it without the drop. I can just do a normal reboot. Only the "force reboot" this app does when the number of allowed guesses is exceeded seems to have these bad effects.

And if I need to calibrate the battery it is not a drain of battery, it is some kind of issue with the betterystats file or so...

xmikos commented 8 years ago

See my answer here: https://github.com/xmikos/SnooperStopper/issues/13#issuecomment-244013294

I can add graceful shutdown option in the future, but sadly I don't have time for it now. If you are programmer, I am open to accept push requests here on GitHub (but make it an option, not default).

gene-pavlovsky commented 8 years ago

Does it happen to you every time? I'm having no such issue (running CM13-based Resurrection Remix ROM, device encryption on). If your issue is reproducible, get the logcat right after you reboot your phone. Perhaps some app you have installed (or a system app) was doing something at the moment your phone got forcefully rebooted, corrupting it's data, and making it misbehave after booting again.