Related
Did the S-Off; Custom Recovery; Permanent Root last night. Everything went fine, rebooted after everything was done and charged my phone to 100%.
Wake up this morning after not touching the phone for 8 hours and the phone lost 30% over night. Looking at the battery stats the Kernel (Android OS) took up 60% of the battery. Wakelock Detector is showing Google Search as a wakeup trigger 92 times.
Before this whole process I was averaging 5-6 hours of screen on time, anybody else seeing some weirdness going on with their battery life?
dadams312 said:
Did the S-Off; Custom Recovery; Permanent Root last night. Everything went fine, rebooted after everything was done and charged my phone to 100%.
Wake up this morning after not touching the phone for 8 hours and the phone lost 30% over night. Looking at the battery stats the Kernel (Android OS) took up 60% of the battery. Wakelock Detector is showing Google Search as a wakeup trigger 92 times.
Before this whole process I was averaging 5-6 hours of screen on time, anybody else seeing some weirdness going on with their battery life?
Click to expand...
Click to collapse
Nothing abnormal here... Getting the same performance as I did pre s-off
M8, nuff said.
Root and S-Off alone? No. Mods/tweaks that require root? Yes.
Can Google search be a random wakelock sometimes for seemingly no reason? Absolutely.
Sent from my HTC6525LVW using Tapatalk
dadams312 said:
Did the S-Off; Custom Recovery; Permanent Root last night. Everything went fine, rebooted after everything was done and charged my phone to 100%.
Wake up this morning after not touching the phone for 8 hours and the phone lost 30% over night. Looking at the battery stats the Kernel (Android OS) took up 60% of the battery. Wakelock Detector is showing Google Search as a wakeup trigger 92 times.
Before this whole process I was averaging 5-6 hours of screen on time, anybody else seeing some weirdness going on with their battery life?
Click to expand...
Click to collapse
Install gsam and get a better idea of whats going on. I also flashed the insecure kernel thats floating around and since actually noticing back to normal use.
Questions should go in Q/A btw
droidkevlar said:
Install gsam and get a better idea of whats going on. I also flashed the insecure kernel thats floating around and since actually noticing back to normal use.
Questions should go in Q/A btw
Click to expand...
Click to collapse
I'm using gsam, that is what showed "kernel (android os) using 60%
dadams312 said:
I'm using gsam, that is what showed "kernel (android os) using 60%
Click to expand...
Click to collapse
Im down at 7%. Have you tried flashing the insecure kernel? I swear after flashing that, batt life got better. But only been 2 days, so I cant really say
droidkevlar said:
Im down at 7%. Have you tried flashing the insecure kernel? I swear after flashing that, batt life got better. But only been 2 days, so I cant really say
Click to expand...
Click to collapse
No I will look around for that though and see what it's about.
I've been rooting my phones since the Thunderbolt and I'm my opinion/experience nothing is better than stock. Once I started messing with Kernels, custom recoveries, Roms, "tweaks" ect...battery seems to be affected big time. Maybe its things I do as I'm not an expert at any of this and by no means am I trying to bash on devs for the work they do but that has just been my personal experience.
Sent from my HTC6525LVW using Tapatalk
FWIW I didn't experience any sort of battery drain with the temp root before we got S-Off.
root and s-off will not affect battery. Xposed modules, root apps, and other mods can. I have about 6 or so xposed modules running and I still get way, way over 1.5 days of battery life. I had 2 hours of screen on time and my phone used 55% in 1.5 days so.... its pretty good. Check to make sure google now isnt causing wakelocks, turn off location reporting and if you can, turn off google now completely. I really only used it for weather because I don't see much other functionality with it.
123421342 said:
root and s-off will not affect battery. Xposed modules, root apps, and other mods can. I have about 6 or so xposed modules running and I still get way, way over 1.5 days of battery life. I had 2 hours of screen on time and my phone used 55% in 1.5 days so.... its pretty good. Check to make sure google now isnt causing wakelocks, turn off location reporting and if you can, turn off google now completely. I really only used it for weather because I don't see much other functionality with it.
Click to expand...
Click to collapse
I haven't added any apps since running the temp root when I was getting great battery life.
I did the s-off, recovery, and root...uninstalled Verizon bloat and that's it.
Lost 30% over night last night. I drained the battery to 1% last night, turned phone off and charged to 100%, unplugged and didn't touch it....woke up to 70% battery life.
dadams312 said:
I haven't added any apps since running the temp root when I was getting great battery life.
I did the s-off, recovery, and root...uninstalled Verizon bloat and that's it.
Lost 30% over night last night. I drained the battery to 1% last night, turned phone off and charged to 100%, unplugged and didn't touch it....woke up to 70% battery life.
Click to expand...
Click to collapse
Have you tried flashing the insecure kernel yet? If not, you should and then see how your battery life is.
FWIW I didn't experience any sort of battery drain with the temp root before we got S-Off.
droidkevlar said:
Have you tried flashing the insecure kernel yet? If not, you should and then see how your battery life is.
Click to expand...
Click to collapse
Wont change a single thing
dadams312 said:
I haven't added any apps since running the temp root when I was getting great battery life.
I did the s-off, recovery, and root...uninstalled Verizon bloat and that's it.
Lost 30% over night last night. I drained the battery to 1% last night, turned phone off and charged to 100%, unplugged and didn't touch it....woke up to 70% battery life.
Click to expand...
Click to collapse
Clearly you have wakelock issues. Get gsam battery and wakelock detector, post your stats after your phone is idle for a few hours.
123421342 said:
Wont change a single thing
Clearly you have wakelock issues. Get gsam battery and wakelock detector, post your stats after your phone is idle for a few hours.
Click to expand...
Click to collapse
I've had both of those running since the temp. root. which screens will give you the best idea of what is going on?
I did flash the insecure kernel earlier this afternoon, and turned off google now.
If anything try a factory reset. It should definitely help.
Sent from my HTC6525LVW using Tapatalk
dadams312 said:
I've had both of those running since the temp. root. which screens will give you the best idea of what is going on?
I did flash the insecure kernel earlier this afternoon, and turned off google now.
Click to expand...
Click to collapse
Post the gsam home screen and the apps section. Also post the home screen of wakelock detector for kernel wakelocks
Most s-off will turn on debug process.
return s on state after you have done modes or you need many tweaks in further.
dadams312 said:
Did the S-Off; Custom Recovery; Permanent Root last night. Everything went fine, rebooted after everything was done and charged my phone to 100%.
Wake up this morning after not touching the phone for 8 hours and the phone lost 30% over night. Looking at the battery stats the Kernel (Android OS) took up 60% of the battery. Wakelock Detector is showing Google Search as a wakeup trigger 92 times.
Before this whole process I was averaging 5-6 hours of screen on time, anybody else seeing some weirdness going on with their battery life?
Click to expand...
Click to collapse
Fix here:
http://forum.xda-developers.com/showthread.php?t=2745179
Hello enthusiasts,
I'm having a problem with my HTC One Mini (from German Telekom).
The device keeps turning off at around 45% battery charge. There is no warning prior to the shutdown. You can briefly see the "Battery is low!" warning for a tenth of a second until the phone shuts down completely. It can then not be turned on again unless I plug it into the charger. When turned on immediately afterwards, while charging, the battery status has changed to 0%.
There is a screenshot attached which shows the Voltage of the battery about 2 minutes before the device shut down.
I have already used the search and found numerous threads about devices shutting down with a high battery load, but the linked tutorials are often obsolete or unappliable.
I've been studying Wikipedia articles about Lithium-Ion batteries which say that the lowest voltage for a battery generally is 2.5V. Many manufacturers implemented security measurements that keep the battery far away from this low voltage level. I expect the 0%-load to be around 3V, but 3.3V should still be rather "loaded".
Concerning the overall device duration after a full charge: It has become far worse. After first flashing Cyanogenmod M11 Snapshot M6 a fully charged battery would give me around 20h of time until it would die. I've always recharged the device when it reached about 20% charge, before it turned red. Now it barely manages to get to 12-14h. And I don't even use it heavily.
I've already tried some battery calibration apps, but they all haven't shown any influence on the symptoms.
Information about the system:
HTC One Mini
Cyanogenmod 11, Snapshot M11 released on 2014-10-08 02:18:05
Battery Apps: Battery Doctor, Greenify (no difference with or without these apps)
I'd be glad to provide more information on this matter if I forgot something, but I hope I got everything you need. Would greatly appreciate help as this problem is slowly grinding my gears.
Doctor Luk said:
Hello enthusiasts,
I'm having a problem with my HTC One Mini (from German Telekom).
The device keeps turning off at around 45% battery charge. There is no warning prior to the shutdown. You can briefly see the "Battery is low!" warning for a tenth of a second until the phone shuts down completely. It can then not be turned on again unless I plug it into the charger. When turned on immediately afterwards, while charging, the battery status has changed to 0%.
There is a screenshot attached which shows the Voltage of the battery about 2 minutes before the device shut down.
I have already used the search and found numerous threads about devices shutting down with a high battery load, but the linked tutorials are often obsolete or unappliable.
I've been studying Wikipedia articles about Lithium-Ion batteries which say that the lowest voltage for a battery generally is 2.5V. Many manufacturers implemented security measurements that keep the battery far away from this low voltage level. I expect the 0%-load to be around 3V, but 3.3V should still be rather "loaded".
Concerning the overall device duration after a full charge: It has become far worse. After first flashing Cyanogenmod M11 Snapshot M6 a fully charged battery would give me around 20h of time until it would die. I've always recharged the device when it reached about 20% charge, before it turned red. Now it barely manages to get to 12-14h. And I don't even use it heavily.
I've already tried some battery calibration apps, but they all haven't shown any influence on the symptoms.
Information about the system:
HTC One Mini
Cyanogenmod 11, Snapshot M11 released on 2014-10-08 02:18:05
Battery Apps: Battery Doctor, Greenify (no difference with or without these apps)
I'd be glad to provide more information on this matter if I forgot something, but I hope I got everything you need. Would greatly appreciate help as this problem is slowly grinding my gears.
Click to expand...
Click to collapse
Have you tried using a different ROM?
Everest_ said:
Have you tried using a different ROM?
Click to expand...
Click to collapse
I've had the stock ROM installed for about 7 months until July and then I've only installed different versions of Cyanogenmod.
Namely Snapshot M7, a Nightly one from July, back to Snapshot M7 (at this point, the problem with the battery started occuring), then a nightly from October 6th and just recently the Snapshot M11. It should be noted that I've always wiped the system partition before installing a new build.
Doctor Luk said:
I've had the stock ROM installed for about 7 months until July and then I've only installed different versions of Cyanogenmod.
Namely Snapshot M7, a Nightly one from July, back to Snapshot M7 (at this point, the problem with the battery started occuring), then a nightly from October 6th and just recently the Snapshot M11. It should be noted that I've always wiped the system partition before installing a new build.
Click to expand...
Click to collapse
Flash a stock ROM and see if it still happens.
I have this problem also on any roms. But my isn't at 45%. It's usually at around 14% or 30 something. After it reboots my battery will be 0%
I've had the stock rom running for some time now and the battery display is absolutely fine with it. As soon as I go back to my CM M11 backup and recharge the phone, the measurement gets all confused and the phone starts shutting down at ~45%-50% again.
Doctor Luk said:
Hello enthusiasts,
I'm having a problem with my HTC One Mini (from German Telekom).
The device keeps turning off at around 45% battery charge. There is no warning prior to the shutdown. You can briefly see the "Battery is low!" warning for a tenth of a second until the phone shuts down completely. It can then not be turned on again unless I plug it into the charger. When turned on immediately afterwards, while charging, the battery status has changed to 0%.
There is a screenshot attached which shows the Voltage of the battery about 2 minutes before the device shut down.
I have already used the search and found numerous threads about devices shutting down with a high battery load, but the linked tutorials are often obsolete or unappliable.
I've been studying Wikipedia articles about Lithium-Ion batteries which say that the lowest voltage for a battery generally is 2.5V. Many manufacturers implemented security measurements that keep the battery far away from this low voltage level. I expect the 0%-load to be around 3V, but 3.3V should still be rather "loaded".
Concerning the overall device duration after a full charge: It has become far worse. After first flashing Cyanogenmod M11 Snapshot M6 a fully charged battery would give me around 20h of time until it would die. I've always recharged the device when it reached about 20% charge, before it turned red. Now it barely manages to get to 12-14h. And I don't even use it heavily.
I've already tried some battery calibration apps, but they all haven't shown any influence on the symptoms.
Information about the system:
HTC One Mini
Cyanogenmod 11, Snapshot M11 released on 2014-10-08 02:18:05
Battery Apps: Battery Doctor, Greenify (no difference with or without these apps)
I'd be glad to provide more information on this matter if I forgot something, but I hope I got everything you need. Would greatly appreciate help as this problem is slowly grinding my gears.
Click to expand...
Click to collapse
I have the same problem. As soon as my phone gets to about 40%, the battery drains to 0% within minutes, even while the screen is off and no data is being used. My phone is just over a year old and running a rooted, but stock version of 4.4.2. I don't think it's ROM related since it only started doing this recently. My guess is that our phone batteries are malfunctioning. Check out this person who has the exact same problem I have on the One M8:
http://forums.androidcentral.com/htc-one-m8/396770-htc-one-m8-battery-drain-40-60-0-seconds.html
His screen shots mirror mine EXACTLY. One thing I discovered is that while charging from 0% while in recovery, I was able to see my battery percentage jump from 7% to 50% when I booted to the OS. The battery then died again minutes later. This only happened once, but I'm guessing that our phone might be displaying a higher percentage than what is true just before it dies.
I have a strong feeling this might be CyanogenMod related, as it is known to have caused great problems on dozens M4's with overheating / strange battery drain / weird stuff like that, among many other bugs.
If I were you, I would do a fully clean install of a stable Sense-based ROM and kernel on upgraded firmware and see if problem persists.
Upgrade to the latest TWRP recovery
Wipe everything
Factory/Data reset
Advanced wipe: Cache / Dalvik Cache / System / Data / Internal Storage
Format Data
Upgrade your firmware, if not done yet
Install latest InsertCoin, choose "Perform a full wipe" option in AROMA
When installer finished, uncheck "Reboot phone now" and get back to recovery
Wipe [Cache] + [Dalvik Cache]
Install latest Xceed kernel (for Android 4.4.3)
Wipe [Cache] + [Dalvik Cache]
Reboot
I wish it was that simple. Thought CM may have some known issues, my device and the other example I linked to are running stock Roms.
If it wasn't happening every single day, it wouldn't be such a big deal, but now I'm seriously worried that I can't get a full days use from it anymore and it's barely over a year old. Sending it back to HTC would be a huge pain since I'm rooted. Though I guess it would be worth it in the long run to finally have a phone that doesn't shut down at 40%
Sent from my HTC One mini using XDA Free mobile app
Hello everyone, sorry for the delay.
It looks as if there might be damage to the battery as the %-display for the battery is still wrong on a Stock ROM (rooted and outdated) that I've had on the device for a week now.
Okay guys, what to do next? I guess I would like to completely revert everything and reset the phone to 100% stock. Would you guys recommend opening a new thread for that?
Anyway, here are some details:
Kernel 3.4.10-g8974365 [email protected] #1 SMP PREEMT
CID: T-MOB101
TAMPERED
UNLOCKED
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.24.40e.00.26
OpenDSP-v19.2.0268.0927
OS-3.10.111.4
eMMC-boot 1024MB
Feb 14 2014, 17:48:26.0
I'm running a Stock branded ROM (T-Mobile Germany) with Sense 5.5 and Android 4.4.2 which is OUTDATED, however using the stock Recovery, I can NOT install OTA Updates as it stops at 50% showing the attached image (courtesy of droider.eu).
So the plan is to get the default Kernel (remove root), make the Stock ROM updateable, remove TAMPERED [might require S-OFF if I'm correct] and get everything LOCKED again (and not RE-LOCKED). I need your help to achieve all of this and it would be awesome if you could help me or just tell me to open a new thread.
Doctor Luk said:
Hello everyone, sorry for the delay.
It looks as if there might be damage to the battery as the %-display for the battery is still wrong on a Stock ROM (rooted and outdated) that I've had on the device for a week now.
Click to expand...
Click to collapse
I am in the same boat with you. I have completely given up on this battery. It's not ROM related. The battery simply doesn't hold a full charge anymore and the only remedy is to send it back to HTC for replacement. Since my phone has no insurance or warranty, I'd have to pay for it completely out of pocket. Fortunately, I've got my old HTC One S that still works perfectly and just loaded the latest KitKat Rom to it. The battery life and over-all performance of the One S is nearly better than my One Mini. I'm not feeling very compelled to get it fixed at the moment, but I'll let you guys know how much it costs if I change my mind. Good luck with yours.
Thanks, I'll just have to get mine fully back to stock to be able to turn it in... Hope it'll not be that pricy for you.
Can you get rid of the tampered warning on the boot screen? I thought it was irreversible. If not, I don't think HTC will warranty it.
Sent from my HTC One S using XDA Free mobile app
Of course you can, at least I assume you can. On the HTC One there are already guides and I guess the Mini is not that much different. It requires S-OFF though, so at least I would have to tinker around with my phone even more.
Our Plain vanilla -stockROM One mini is having similar issues:
It shuts down at battery 30%
- removed unneccessary app's - no result
- Factory reset - No result
Contacted HTC support, they advised to run self-test ( *#*#3424#*#*) in safe mode
Tried that: Boot-up in safe mode - charge full - batterytest : Put it away for the night while batterytest running, hoping for a report in the morning. Unfortunately no report, but a battery status of 1% - so no shutdown at 30%
Second time: Charged full in regular mode (100%) - reboot in safe-mode: Battery shows up @57% and could be charged for at least one hour.
Ran battery-test : after one hour of testing, battery = 91 % while 71 % is lower limit for failing battery, so battery succeeded.
Third time: Just testing the difference between battery-status in regular mode vs. safe-mode
Full charge in regular = 50% in safe mode (and able to continue charging)
Don't want to sent it away for repair: expecting to have it sent back after a couple of weeks: " we did the batterytest, and it's functioning fine. Your device is not broken"
My idea: something interfering with the battery-status indicator ?
But what ?
Any ideas ?
jamf said:
Our Plain vanilla -stockROM One mini is having similar issues:
It shuts down at battery 30%
- removed unneccessary app's - no result
- Factory reset - No result
Any ideas ?
Click to expand...
Click to collapse
not sure it works, but try this
the wiping the partition cache from stock recovery is not quite the same as factory reset
jamf said:
Tried that: Boot-up in safe mode - charge full - batterytest : Put it away for the night while batterytest running, hoping for a report in the morning. Unfortunately no report, but a battery status of 1% - so no shutdown at 30%
Click to expand...
Click to collapse
Thanks for reporting a similar problem to mine. I haven't gotten to fix mine, yet, too. Mine even powers down at 75% Battery and now has a horrible battery life of about 2h of normal usage (occasional screen activity, listening to music).
But how did you find a batterytest? I can't seem to find one in the safe-mode via that dial code. Can you explain where you found the battery test?
jamf said:
Our Plain vanilla -stockROM One mini is having similar issues:
It shuts down at battery 30%
- removed unneccessary app's - no result
- Factory reset - No result
Contacted HTC support, they advised to run self-test ( *#*#3424#*#*) in safe mode
Tried that: Boot-up in safe mode - charge full - batterytest : Put it away for the night while batterytest running, hoping for a report in the morning. Unfortunately no report, but a battery status of 1% - so no shutdown at 30%
Second time: Charged full in regular mode (100%) - reboot in safe-mode: Battery shows up @57% and could be charged for at least one hour.
Ran battery-test : after one hour of testing, battery = 91 % while 71 % is lower limit for failing battery, so battery succeeded.
Third time: Just testing the difference between battery-status in regular mode vs. safe-mode
Full charge in regular = 50% in safe mode (and able to continue charging)
Don't want to sent it away for repair: expecting to have it sent back after a couple of weeks: " we did the batterytest, and it's functioning fine. Your device is not broken"
My idea: something interfering with the battery-status indicator ?
But what ?
Any ideas ?
Click to expand...
Click to collapse
Wow - I wish you had posted this 2 days earlier! I just had a new battery purchased for my phone and I'm getting a local repair shop to replace it. Sounds like my battery could be fine and I will likely have the same results after it's replaced!
If you fully charge the phone in safe mode, does the phone battery still last the appropriate amount of time in regular mode or does it still shut off prematurely?
Doctor Luk said:
Thanks for reporting a similar problem to mine. I haven't gotten to fix mine, yet, too. Mine even powers down at 75% Battery and now has a horrible battery life of about 2h of normal usage (occasional screen activity, listening to music).
But how did you find a batterytest? I can't seem to find one in the safe-mode via that dial code. Can you explain where you found the battery test?
Click to expand...
Click to collapse
Dial *#*#3424#*#* and click <more> in the right lower corner
iourikil said:
not sure it works, but try this
the wiping the partition cache from stock recovery is not quite the same as factory reset
Click to expand...
Click to collapse
Not sure if I understand this: I did the Power-button - volume down - 'Factory reset withour keeping data" - as given on the HTC website
PuffDaddy_d said:
Wow - I wish you had posted this 2 days earlier! I just had a new battery purchased for my phone and I'm getting a local repair shop to replace it. Sounds like my battery could be fine and I will likely have the same results after it's replaced!
If you fully charge the phone in safe mode, does the phone battery still last the appropriate amount of time in regular mode or does it still shut off prematurely?
Click to expand...
Click to collapse
It still does: Fully charged in safe-mode it shuts down @30% - does seem to last longer to reach 30% level
Last night I tried a different trick:
After shutdown @30% I kept the phone off and recharged it to 29 %
I put the phone back on and drained the battery to 0% - ignoring all warnings ("please charge .... CHARGE ..... G*DDAMN START CHARGING, I'M FREAKING DYING HERE ....)
Recharged the battery while powered off from 0% to 100%
Tested this morning: Same battery level in regular mode as in safe mode (98%)
Hmmm, I seem to remember doing some thing similar by accident with my phone when I stopped charging around 30% to use it. It drained to 0 shortly after and I fully recharged while in recovery mode. The battery seemed to last longer that time, but any subsequent charging before letting the battery die seemed to result in the same poor battery life. It's not a real solution but if you can confirm that yours acts similarly, then it's more info for us to have as we try to figure this out.
Sent from my HTC One S using XDA Free mobile app
Is there anything / any ROM available. I've noticed this past week (where I live goes in and out of 3G /LTE) that my battery life does down 3% in 30mins to 45mins and my phone is on Power Saving Mode, Airplane Mode and Restrict background data. Go into battery and est time I have after full charge is 12hours but after I check the phone while at work. (Everything is off no data can come in or go out) Android OS is wide awake constantly. I cannot decipher whats causing this. I did a clear cache, factory reset. Disabled Android Device Manager, GPS, ( developer options) -- limit background process to None.
I bought the phone off craigslist it came with a MOAR which I had to go to Sprint store to activate it. ( me being paranoid I found the tarbal for the PC3, installed MM 6.0 back on this thing and activated it) 3 weeks of good vibes now all the battery issues. If it is possible to flash to any older SW version like lollipop or any stable build for battery life please let me know. I see S5 people getting 2 days battery like really on stock firmware.
Try flashing a new kernel.
Do a full system wipe on it fully charged.
Flash whatever rom you want and a kernel. I use the forest noble.
Download a kernel editor like kernel toolkit. Look around for good governors for battery life.
Fully charge it after then let it drain until it shuts off. Keep it off and fully charge. After go into recovery and wipe cache /dalvik cache.
If that doesn't work idk. If you have the TEP insurance with sprint they can do something called an Advanced Exchange of they're a repair center for a defective battery.
I have inside sources don't say anything about root or custom recovery they will AE it anyways. But you have to have TEP or TEP plus insurance.
Good luck.
Just curious what's the going rate for a note 5 with MOAR pre installed?
hi, today I bough used (one year old, still in warranty) shield k1 and battery drain, even when not playing, is like 1% a minute. Also recharging is pretty slow. I have stock rom noughat version 5.2 and I did factory reset. I found some issues occuring after update to 7.0. But I can't find anything how to fix it. and also I'm not sure if battery can be dead after one year or if it's software related... Please see attached picture
Should I root and try some custom rom? I will stop my warranty
Rooting doesn't void warranty and you can always simply unroot and go to stock ROM, so I suggest you to flash latest stock ROM to get the newest firmware (the one for faster charging) and then you can flash which ever custom ROM you like the most.
Edit : so to answer your question, this is far from a good battery life, but I am 95% sure that with customisation you can make that better. When you do that we can evaluate the health of your battery.
My shield on tesla rom took 6 days to go from 100% to 20% idleing. It took my charger 2 hours to put it back to 100%
I'm not even kidding. Everything was perfect and I had absolutely no problems until they sent out that update. Now I can watch my battery percentage dropping by the second and my phone will shut off around 30%.
Once again, I had no problems until the August update. I never even rooted this phone, so the last thing I want to do is to figure that out to downgrade to the last version. I will if I have to though
If your phone spontaneously shuts down with the battery at 30%, then I see 2 possibilities:
It's overheating, or
The battery has reached end-of-life
Use an app to determine the remaining capacity of your battery (usually displayed in mAh). The results of such apps should be taken with a grain of salt, but if it says your battery is only at 60 or 70% of original capacity, then it's definitely not normal.
magnumtripod said:
I'm not even kidding. Everything was perfect and I had absolutely no problems until they sent out that update. Now I can watch my battery percentage dropping by the second and my phone will shut off around 30%.
Once again, I had no problems until the August update. I never even rooted this phone, so the last thing I want to do is to figure that out to downgrade to the last version. I will if I have to though
Click to expand...
Click to collapse
You could try to go to recovery, wipe cache and reboot. Or, if possible, wait for the next security update and see if it gets fixed if you have a spare phone to use. These are the only two opportunities without messing around or loosing data.
A downgrade always needs a full data wipe AFAIK. If you aren't afraid of data loss, you could try a full factory reset and see if the battery drain is gone.
I noticed the same on my Pixel - i don't use it a great deal and was seeing 6 days before it'd drop to 30 to 35% battery level, now i'm seeing 2.5 to 3 days - my usage has not changed
I really don't think it's battery nearing end of life - the phone & battery are just now hitting the 2 yr mark
TheOrigRalph said:
I noticed the same on my Pixel - i don't use it a great deal and was seeing 6 days before it'd drop to 30 to 35% battery level, now i'm seeing 2.5 to 3 days - my usage has not changed
I really don't think it's battery nearing end of life - the phone & battery are just now hitting the 2 yr mark
Click to expand...
Click to collapse
I don't think it's end of life either. Like I said, everything was great until the update. My GF got the same phone around the same time and I told her not to update. So she's still running the last version and her phone is still perfect.
Is the battery life still abysmal when running in safe mode? if so, it may be a rogue 3rd party app.
my battery life was crap with the kernel and android system after i updated to August as well. I assumed it was a Magisk update or module that was the issue. Once I moved to Android Pie my battery life has returned.
mruno said:
Is the battery life still abysmal when running in safe mode? if so, it may be a rogue 3rd party app.
my battery life was crap with the kernel and android system after i updated to August as well. I assumed it was a Magisk update or module that was the issue. Once I moved to Android Pie my battery life has returned.
Click to expand...
Click to collapse
I haven't tried safe mode - my battery was surprising decent under Android 8. the day it updated to Android 9 it went south in a handbasket. And i noticed "battery saver" selection is no longer available
i'm trying to read up and re-learn installing a custom rom, and which rom to choose - i last did a custom rom in 2010 and haven't been near the forums since then, but this issue and the more i learn about google's surveillance collection, i want to go custom
Since you're willing to install a custom ROM, why not try to reinstall the full stock ROM first?
appreciate the suggestion - that's what i originally wanted to do and posted here a few weeks back asking how to revert to android 8 and was told it couldn't be done but i could do a custom rom
and now, with the privacy issues i've been reading about, i think i'd prefer to limit my services as googles' "product". It kind of alarmed me how sensitive the phone's microphone was - i actually wrapped the phone in a heavy towel and left it 5 feet away, and said "OK google" in a normal voice - and bam, it was opened when i unwrapped the phone. There's no reason for the microphone to be that sensitive, imho
but i'm an old fart, and the younger generations don't seem to relish their privacy like i do - that's fine for them, no judgment on my part, i just like my privacy