Database Info

[Q][SOLVED] Device turns off at 45% Battery

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

Full charge at 96 percent?

Hello community,
So, I've got myself a Nexus 5.
Problem (?):
When I'm charging my N5 and the battery indicator reaches 96%, the charging led goes green, indicating that it's fully charged. It doesn't STOP to charge at 96% like to prevent overcharging, it just shows green led at 96% and continues to charge to 100%. It thought the problem may be the stock kernel that comes with Cataclysm ROM, so I've flashed ElementalX kernel (Without wiping anything, do I have to wipe?) and the problem's still there.
Is that behavior normal?
Here are details about my phone:
Cataclysm ROM, 5.1.1 (Jun 20, 2015, stable build)
ElementalX Kernel, latest version for 5.1.1 (4.04)
I got my N5 one or two months ago, I rooted immediately but I believe it had this issue right out of the box. And I'm using the stock wall charger & usb cable which I received with my N5.
Thanks to anyone trying to help me.
Regards

I remember a Marques Brownlee Youtube video where he was talking about Li-On battery overcharging - they don't apparently, since there is circuitry in the battery to regulate the charging. From memory, he described it as a sort of "bounce" effect, where the charging gets close to 100%, cuts out, then says "Maybe a bit more" and starts again - and it may do that a number of times. So I reckon that this behaviour is what you're seeing, and you don't have any problem.

dahawthorne said:
I remember a Marques Brownlee Youtube video where he was talking about Li-On battery overcharging - they don't apparently, since there is circuitry in the battery to regulate the charging. From memory, he described it as a sort of "bounce" effect, where the charging gets close to 100%, cuts out, then says "Maybe a bit more" and starts again - and it may do that a number of times. So I reckon that this behaviour is what you're seeing, and you don't have any problem.
Click to expand...
Click to collapse
Thank your for your reply
Now I know that everything's behaving normal. I almost thought that I have to replace the battery - and it's non removeable, so that would be a hard nut for me to crack, even with the right tools.
Last question, if I would replace my current N5 battery with another (original) battery, would the 'problem' vanish? Now I know, everything's OK.. but I'm a sorta perfectionist when it comes to devices. In other words, is that behavior related to the battery?

Here's the Marques Brownlee video I mentioned: https://www.youtube.com/watch?v=hrcbcm11830
So the answer to your question is: no, a new battery will (most likely) make no difference at all - a lot of trouble, risk and expense for nothing. I leave my phone on a charging pad every night, on a timer switching off around 03:00, and it's usually around 95-97% in the morning. Like you, I'd much prefer 100%, but I've learned to live with it, especially as my Nexus 6 very rarely drops below 50% during the day - I'm a light user.
And a word of warning to anyone reading this. We tend to go looking for solutions to problems we've already suffered, when it can be too late. I managed a few months ago to drain my Nexus 5 battery down to zero, and when I recharged it the radio was stone dead - no SIM recognised, no data service (but wifi ok), no phone calls, no texts. There are many people reporting the same thing, so beware:
DON'T LET YOUR NEXUS 5 BATTERY DRAIN TO ZERO!!!

Unbenannt0412 said:
Now I know that everything's behaving normal. I almost thought that I have to replace the battery - and it's non removeable, so that would be a hard nut for me to crack, even with the right tools.
Click to expand...
Click to collapse
There is no need for you to replace your battery - the percentage issue might be solved with a simple battery calibration.
But just to answer your question, the hardest part when replacing the battery is getting the old one out since it's glued in pretty hard.

-SmOgER said:
There is no need for you to replace your battery - the percentage issue might be solved with a simple battery calibration.
But just to answer your question, the hardest part when replacing the battery is getting the old one out since it's glued in pretty hard.
Click to expand...
Click to collapse
Can you please forward me to some sort of instructions of how to calibrate properly? Can't find anything but the batterystats.bin hoax.

Anyone?

Unbenannt0412 said:
Anyone?
Click to expand...
Click to collapse
disccharge from 100% until your phone shuts down, then charge it to 100% while it is off

As far as I know, this issue is software side, not hardware. Have you ever encountered this problem before ? On my ROM (which is SAOSP), the LED started turning green at 95%. This could also mean that the green LED is set to appear at 95% - 96% charge.

F4uzan said:
As far as I know, this issue is software side, not hardware. Have you ever encountered this problem before ? On my ROM (which is SAOSP), the LED started turning green at 95%. This could also mean that the green LED is set to appear at 95% - 96% charge.
Click to expand...
Click to collapse
Yes, I've thought about that too. The LED could be the problem. Is there some sort of workaround for this?
And no, I'm encountering this for the first time. I've rooted and flashed Cataclysm ROM right after I unpacked my N5, so I don't know if the problem was on stock too.

Unbenannt, I would say that you need to stop looking at this as a problem - it doesn't seem to be one. You'll spend a lot of time and energy on this (you already have...) and the concensus seems to be that it's not worth the trouble. If you run down your battery you risk bricking the radio (and I know that GtrCraft is saying only until the phone shuts down, not drained to zero) but really, why take the risk of damaging a beautiful device for such a minor reason?

Unbenannt0412 said:
When I'm charging my N5 and the battery indicator reaches 96%, the charging led goes green, indicating that it's fully charged.
Click to expand...
Click to collapse
did you said charging LED ? wooh I've been using this device for 2-3 months and never seen LED blink when full charged !!
you are using any app or something for that ? bcz i'm on stock and i can't see any option to turn it on and No charging light for me at all !
does all people see it on stock ?!

jineshpatel30 said:
did you said charging LED ? wooh I've been using this device for 2-3 months and never seen LED blink when full charged !!
you are using any app or something for that ? bcz i'm on stock and i can't see any option to turn it on and No charging light for me at all !
does all people see it on stock ?!
Click to expand...
Click to collapse
I'm running a custom ROM (Cataclysm), so that's probably why.

dahawthorne said:
Unbenannt, I would say that you need to stop looking at this as a problem - it doesn't seem to be one. You'll spend a lot of time and energy on this (you already have...) and the concensus seems to be that it's not worth the trouble. If you run down your battery you risk bricking the radio (and I know that GtrCraft is saying only until the phone shuts down, not drained to zero) but really, why take the risk of damaging a beautiful device for such a minor reason?
Click to expand...
Click to collapse
Yeah, maybe you are right.

Unbenannt0412 said:
I'm running a custom ROM (Cataclysm), so that's probably why.
Click to expand...
Click to collapse
Oh..i thought you were fully stock before flashing custom kernel.

Insane Idle Battery Drain

Hi,
I'm getting some insane levels of idle battery drain recently. A bit of background,
- US Stock
- Rooted
- SuperCID
I was having this battery drain everyday for about 2 weeks, so I wiped my phone and started fresh. Since I did, I've been slowly introducing only a few apps everyday, and the battery was perfect until today.
All I did since yesterday when it was good, was tether to my laptop for an hour, and when I noticed a few hours later that the drain was back I removed the Bluetooth pairing completely. But the drain remains.
My phone sits in an awake state with the screen off for 99% of the time.
Here are some screenshots from Better Battery Stats and Wakelock Detector which don't seem to show much apart from a Google sensor.
http://imgur.com/a/eKqjl
Desperate for help because as much as I love this phone, with this situation it is barely usable.

Some more screenshots. Wakelock Detector and Android Settings.
The only red flag I can see is something called "Significant Motion(12)" which was awake for almost 7 hours. But I've been googling this and not finding anything about it.

Another screenshot now that I am at a computer - this is from a Google Historian report from a bugreport I just generated.
Something labelled "Abort:noirq suspend of c171000.uart device failed" woke the kernel up 89696 times. Wonder if this is the "significant motion" sensor that BBS is reporting?

I have the same problem.
It's started 3 days ago and i don't know how to fix the problem.
I hope that htc would fix this problem on this weak.
If someone know how to fix this problem until htc do something, please reply.

ShDorLq said:
I have the same problem.
It's started 3 days ago and i don't know how to fix the problem.
I hope that htc would fix this problem on this weak.
If someone know how to fix this problem until htc do something, please reply.
Click to expand...
Click to collapse
I don't even know what the problem is - so how do you know you have the same problem?
I'm not sure this is a problem for HTC, because my phone was perfect for 3 days after resetting it. It only started again last night. If it was great for 3 days and started on the 4th, odds are that it is something about my set-up rather than a problem with the stock firmware.

Zico 10 said:
I don't even know what the problem is - so how do you know you have the same problem?
I'm not sure this is a problem for HTC, because my phone was perfect for 3 days after resetting it. It only started again last night. If it was great for 3 days and started on the 4th, odds are that it is something about my set-up rather than a problem with the stock firmware.
Click to expand...
Click to collapse
I have not changed anything on my phone and the problem is surprising.
Last week I did not install apps or add files.
I also have Watsapep at the top of the table in the utilization of the battery.
android 8.0.0
software number 2.42.617.1
not rooted
stock rom

Try disabling google apps one by one
also try using your phone without wifi

I already tried disabling app by app when it first happened, and did this over 2-3 weeks basically going through all the main suspects and Google Apps.
About to go to sleep tonight, I am going to try,
1 - turning off wifi and Bluetooth and charging the phone to a decent charge level
2 - force restarting the phone after removing it from charge
3 - leaving it on the bedside table untouched until I wake up in ~7 hours
Someone with a U11+ said they need to force restart after charging, so it’s worth a shot right?
Also just posted this about the sensor in another thread. Anyone else having trouble, would appreciate if you could also try these steps,
Zico 10 said:
The ways I stumbled on this were,
1. Better Battery Stats
Under Sensors, you'll notice Google Play Services with a high percentage. Click/press it and you'll see a listing for "Sensor: Significant Motion". This to me indicates that the device thinks it is being moved and refuses to go into Doze mode.
2. Google Battery Historian
Charge your device and let it drain for a while. Then connect it to your computer and take a bug report using ADB - adb bugreport bugreport.zip .. visit an online version of the tool here https://bathist.ef.lc .. then upload the bug report. Under "kernel wake up reasons" you'll see "Abort:noirq suspend of c171000.uart device failed" with an abnormally high number.
3. Take a dumpsys of battery stats
Using ADB, after running your battery down a little, run - adb shell dumpsys batterystats > batterystats.txt .. read the file and you'll see the line I pasted above in my last post.
Would be interested to see if someone suffering from the same symptoms could try this and see if they get the same things. U11 or U11+.
Click to expand...
Click to collapse

Same problem of cell standby battery drain with U11+

EMEA U11 plus running 1.24.401.2
Abort:noirq suspend of c171000.uart device failed
Click to expand...
Click to collapse
repeating endlessly when i did a battery dump

hamdir said:
EMEA U11 plus running 1.24.401.2
repeating endlessly when i did a battery dump
Click to expand...
Click to collapse
With the associated battery drain I assume?
I did this overnight which actually seems to have worked,
1. Switch off Bluetooth and WiFi.
2. Charge phone (it got to 76% when I decided to sleep).
3. Remove from charger.
4. Force restart with vol down + power
Today I’ll experiment to see if I need to do the same 4 every time I charge, or if maybe it is related to only a few of these.
Overnight my battery lost only 5% in 8 hours.
When I get to work, I’ll do a battery dump to see if the noirq error is still present.

Guys today I update my google apps and the problem gone!
how your phone after the updates?

Still there. Seems to be related to charging my phone whilst Bluetooth is on.
When I disconnect from charge, I get battery drain until I charge again with Bluetooth first turned off, then restart the phone.

Zico 10 said:
Still there. Seems to be related to charging my phone whilst Bluetooth is on.
When I disconnect from charge, I get battery drain until I charge again with Bluetooth first turned off, then restart the phone.
Click to expand...
Click to collapse
Found my culprit to be related to Garmin Connect, Fenix 3 watch BT connection.
Could be related to bad firmware.
Edit: Found this same error in my logs a week or two ago when I was trying to track idle drain and lack of deep sleep.
Seems to have disappeared when I disconnected my Garmin watch.

Last night I just had the first occurrence that wasn't related to Bluetooth.
The drain happened despite having Bluetooth turned off when I charged the phone, however I didn't reboot either (and haven't been doing so unless I was trying to get rid of an ongoing battery drain).
I think until we hear of a new firmware release, I'm just going to go through and turn Bluetooth off whilst charging and then restart my phone when I unplug. A minor hassle but at least a working fix.

I had the exact same problem (Significant motion) not allowing my phone to go into deep sleep. For me, just a restart helped from what I remember. Haven't seen this issue since past 4-5 days since it last happened.

I have the same problem with battery drain since the last security update. I am able to fix it temporarily by disconnecting from my huawei smart watch. I will try disconnecting BT while charging and restart after it.

Got a security update today. Hopefully this will fix the drain.

Hello
the u11+ 1.24.401.7 update was just pushed, it is said to address standby issue, my battery dump after reboot no longer contains any reference to, Abort:noirq suspend of c171000.uart device failed
Also early this week a Chrome web view update was pushed in playstore which address issues from Google's side

Possible charging bug

Last night my S6 did not charge and was at 9% when I got up. It would not recognize the charger being plugged in. I then tried it on its original charger (which I had downstairs). It would not recognize that either.
I rebooted the S6 and all is fine again and it sees both chargers.
So that's two software bugs now. This and the WiFi crashing. Both fixed by reboots.

Mine has been perfect so far. Return it imo than to have this potential problem rearing it's head from time to time.
All the best

Don't think it needs returned as it appears to be a software problem not a hardware problem. The fact a reboot resolved it makes me think software. The charging issue has only happened once so far and hopefully a future patch will fix it.

charging should not be software. It may report wrong, but should charge.

There is a software component to evaluating the the charging connection. I that case above rebooting the tablet resolved it. That would not have helped if it was hardware.
Anyway it has not done it since.

I have mine set to MAX charge @ 85%, saves wear on battery I like this feature.

having same issues on charging. I need to reboot/restart my tablet for charging to work.

crazyGD said:
having same issues on charging. I need to reboot/restart my tablet for charging to work.
Click to expand...
Click to collapse
I have not seen it happen since that one time I reported it.

scaramonga said:
I have mine set to MAX charge @ 85%, saves wear on battery I like this feature.
Click to expand...
Click to collapse
Hi. How do you set your max charge?
Sent from my SM-N950U using Tapatalk

toomie said:
Hi. How do you set your max charge?
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Settings > Device Care > click on Battery (bottom left) > three dots (top right), Settings > Protect battery (bottom).

same issue
I have same issue right now. Device is closed and battery is empty I think. Tried all chargers no luck Any ideas?

Question I want limit my batteries charge to 80-85%. How do I do that?

Hi y'all!
Had my 7 Pro for a week now and have "manually" stopped the charging at 85%. Read that this can be done automatically when you root the phone. Anyone who can point me in the right direction where I can get more info on this?
/Dave

Just use your phone normally, make life simple ...
It just a phone btw

Advanced Charging Controller (ACC) magisk module will do that. You also might want a frontend app for it. I use AccA.

daspunner said:
Hi y'all!
Had my 7 Pro for a week now and have "manually" stopped the charging at 85%. Read that this can be done automatically when you root the phone. Anyone who can point me in the right direction where I can get more info on this?
/Dave
Click to expand...
Click to collapse
The suggested methods (ACC, AccA, etc) never worked properly for me--but the 80% module from this thread has worked perfectly. I rooted my phone almost immediately and have been using this since:
[MOD/magisk/root] Set charging limit to 80/85/90/95% v2
After some readings on: https://forum.xda-developers.com/t/limit-charge.4355851/ and https://forum.xda-developers.com/t/mod-magisk-root-set-charging-limit-to-90.4363477/ ( Credits to @rickysidhu_ and @foobar66 ) There is a thing I found and...
forum.xda-developers.com

ACC AccA works but you need to play with settings. I have mine set to 75% and so far works good with every monthly update.

Was ACCA updated for A13?

daspunner said:
Hi y'all!
Had my 7 Pro for a week now and have "manually" stopped the charging at 85%. Read that this can be done automatically when you root the phone. Anyone who can point me in the right direction where I can get more info on this?
/Dave
Click to expand...
Click to collapse
I've seen around over the last couple of months that it seems @roirraW "edor" ehT has the same attitude/intention that you do....you could ask him how he goes about it (he speaks a bit on what's already been suggested in this thread with ACC, but this confirms ACC works on P7P/A13, as well as he maybe can help further set things up) -- apparently he's been doing it for years...
roirraW edor ehT said:
I only charge to 75%, and I try not to let the battery go lower than 25%. This has been my standard for most of the last six years - about the time of my first Pixel. That 50% operating range typically lasts me about 24 hours.
When I sell phones on Swappa (I didn't this time when I got the 7 Pro), I advertise that the battery is gently treated. Of course, when I sell my wife's phone, it's a free for all as to how the battery has been treated.
Click to expand...
Click to collapse
roirraW edor ehT said:
I checked now.
I have two schedules set to run at 1AM if my battery level is at least 40%. I don't charge the battery overnight (and further off-topic, I start charging when it gets down to 25%, and stop charging at 75% - I use ACC and ACC settings to automatically stop charging at 75%, and I use GSam to alert me with different tones when it gets down to 25% and when it's charged to 75%).
Click to expand...
Click to collapse
Also, maybe @wilberfan has spoken a bit on it and maybe has some methods he employs. BTW, he states it shouldn't go above 80% (vs. your 85%)....
Apparently I've overlooked the fact that wilberfan has already replied to this thread...my bad...
wilberfan said:
In general,
For optimized battery life, your phone should never go below 20 percent or never above 80 percent. It may put your mind at ease when your smartphone’s battery reads 100 percent charge, but it’s actually not ideal for the battery. https://www.gearpatrol.com/tech/a624169/smartphone-lithium-ion-charging-tips/
I did this for three years with my OnePlus 7T and my battery was still at 90-something percent of it's original specs.
Click to expand...
Click to collapse

simplepinoi177 said:
I've seen around over the last couple of months that it seems @roirraW "edor" ehT has the same attitude/intention that you do....you could ask him how he goes about it (he speaks a bit on what's already been suggested in this thread with ACC, but this confirms ACC works on P7P/A13, as well as he maybe can help further set things up) -- apparently he's been doing it for years...
Also, maybe @wilberfan has spoken a bit on it and maybe has some methods he employs. BTW, he states it shouldn't go above 80% (vs. your 85%)....
Apparently I've overlooked the fact that wilberfan has already replied to this thread...my bad...
Click to expand...
Click to collapse
Thanks @simplepinoi177!
daspunner said:
Hi y'all!
Had my 7 Pro for a week now and have "manually" stopped the charging at 85%. Read that this can be done automatically when you root the phone. Anyone who can point me in the right direction where I can get more info on this?
/Dave
Click to expand...
Click to collapse
Hi Dave @daspunner.
You'll want to install:
@VR25's Advanced Charging Controller (ACC)
CrazyBoyFeng's ACC Settings
I switched from using MatteCarra's AccA (Advanced Charging Controller App) front-end to ACC Settings in the last six or eight months. I can't remember if AccA just stopped working, or working consistently, but ACC Settings has been working well.
I'm using the latest non-pre-release version of ACC Settings, v2022.6.7 - but I don't think I've even tried the v2022.6.13-pre Pre-release. I have mine set to stop charging at 75% "Pause above", and I have "Charge below" set to 25%. I also have GSam Battery Monitor set to give me different tone alerts for above 74% and below 26%. I also have one set for below 25% in case I miss the below 26% one - although my brother discovered a bug where the second notification sound for the same type of event never goes off, but I haven't paid attention to see if it's fixed, or if it's specific to his Samsung Galaxy S9+.

AccuBattery can do this without root. I use this app for many years.​

Carlosk1966 said:
AccuBattery can do this without root. I use this app for many years.​
Click to expand...
Click to collapse
AccuBattery only notifies you when you reach a certain charge percentage. It doesn't actually stop the phone from charging when you reach a certain percentage, which I believe is what the OP wants.

Lughnasadh said:
AccuBattery only notifies you when you reach a certain charge percentage. It doesn't actually stop the phone from charging when you reach a certain percentage, which I believe is what the OP wants.
Click to expand...
Click to collapse
Yes You are right.

roirraW edor ehT said:
Thanks @simplepinoi177!
Hi Dave @daspunner.
You'll want to install:
@VR25's Advanced Charging Controller (ACC)
CrazyBoyFeng's ACC Settings
I switched from using MatteCarra's AccA (Advanced Charging Controller App) front-end to ACC Settings in the last six or eight months. I can't remember if AccA just stopped working, or working consistently, but ACC Settings has been working well.
I'm using the latest non-pre-release version of ACC Settings, v2022.6.7 - but I don't think I've even tried the v2022.6.13-pre Pre-release. I have mine set to stop charging at 75% "Pause above", and I have "Charge below" set to 25%. I also have GSam Battery Monitor set to give me different tone alerts for above 74% and below 26%. I also have one set for below 25% in case I miss the below 26% one - although my brother discovered a bug where the second notification sound for the same type of event never goes off, but I haven't paid attention to see if it's fixed, or if it's specific to his Samsung Galaxy S9+.
Click to expand...
Click to collapse
I just tried CrazyBoyFeng's ACC Settings, and it seems to be working for me. (P7P on the latest A13 QPR beta) I turned off the Magisk module I've been using and will see how this new method works for a few days.
And it made me chuckle that I've been quoted in here--I am most definitely NOT an expert. An Advanced Beginner (or perhaps a Beginning Intermediate) at best!

roirraW edor ehT said:
Thanks @simplepinoi177!
Hi Dave @daspunner.
You'll want to install:
@VR25's Advanced Charging Controller (ACC)
CrazyBoyFeng's ACC Settings
I switched from using MatteCarra's AccA (Advanced Charging Controller App) front-end to ACC Settings in the last six or eight months. I can't remember if AccA just stopped working, or working consistently, but ACC Settings has been working well.
I'm using the latest non-pre-release version of ACC Settings, v2022.6.7 - but I don't think I've even tried the v2022.6.13-pre Pre-release. I have mine set to stop charging at 75% "Pause above", and I have "Charge below" set to 25%. I also have GSam Battery Monitor set to give me different tone alerts for above 74% and below 26%. I also have one set for below 25% in case I miss the below 26% one - although my brother discovered a bug where the second notification sound for the same type of event never goes off, but I haven't paid attention to see if it's fixed, or if it's specific to his Samsung Galaxy S9+.
Click to expand...
Click to collapse
Which version of ACC do you use? I have acc settings 2022.6.7 and ACC 2022.6.4 My configuration is to pause at 75% and charge below 70%. I have noticed that it does stop charging at 75% BUT if you use battery guru , for example, or something similar like charging Master, it indicates that is still gives some mah,it's not shut down, but this quantity isn't enough to charge the phone. In the battery properties, the phones states: connected, not charging, but battery guru says the opposite. Have you noticed something like this?

mavrovelos said:
Which version of ACC do you use? I have acc settings 2022.6.7 and ACC 2022.6.4 My configuration is to pause at 75% and charge below 70%. I have noticed that it does stop charging at 75% BUT if you use battery guru , for example, or something similar like charging Master, it indicates that is still gives some mah,it's not shut down, but this quantity isn't enough to charge the phone. In the battery properties, the phones states: connected, not charging, but battery guru says the opposite. Have you noticed something like this?
Click to expand...
Click to collapse
I'm using the same version of ACC (v2022.6.4). I might be having the same experience - I haven't paid attention, but I'm not concerned with it. If I remember, the next time I charge my phone, and it reaches 75%, I'll check, but no promises.

mavrovelos said:
Which version of ACC do you use? I have acc settings 2022.6.7 and ACC 2022.6.4 My configuration is to pause at 75% and charge below 70%. I have noticed that it does stop charging at 75% BUT if you use battery guru , for example, or something similar like charging Master, it indicates that is still gives some mah,it's not shut down, but this quantity isn't enough to charge the phone. In the battery properties, the phones states: connected, not charging, but battery guru says the opposite. Have you noticed something like this?
Click to expand...
Click to collapse
If you're using AccA and don't like that, untick prioritize battery idle mode.
A charging switch that works is gcpm/constant_charge_current_max 4000000 0. Usually this gets autodetected, but sometimes it lands on one that doesn't work as well. With this switch (or in general?), max current control only works (somewhat) with qi charging. I have a magsafe battery pack, and the phone will constantly pull too much current and cause the pack to shut off and back on. With a 500ma limit, it seems to charge stably at ~1A.

ziddey said:
If you're using AccA and don't like that, untick prioritize battery idle mode.
A charging switch that works is gcpm/constant_charge_current_max 4000000 0. Usually this gets autodetected, but sometimes it lands on one that doesn't work as well. With this switch (or in general?), max current control only works (somewhat) with qi charging. I have a magsafe battery pack, and the phone will constantly pull too much current and cause the pack to shut off and back on. With a 500ma limit, it seems to charge stably at ~1A.
Click to expand...
Click to collapse
I use acc settings, not acca!

Rooted and got charge to stop at 80%. Any of the settings you guys want to comment about?
I am using ACC settings.
When is says "Connected, not charging". Does it mean that the phone draw power from the charger then instead of the battery?

Unless you are planning on keeping this phone for many, many years limiting the charge will do very little for you. In fact, if by limiting the charge to 80% causes you to have to charge it up more often then it could actually work against you! Let the built in software do it's job. However, a lower charge is always better as long as the heat is controlled.