-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Causes battery drop after reboot #12
Comments
It's normal, a boot sequence consumes a lot of battery (presumably because it will use full speed). /close as invalid |
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... |
See my answer here: #13 (comment) 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). |
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. |
I'm using CM13 and I have read #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:
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...
The text was updated successfully, but these errors were encountered: