Related
Heys Guys Im having an issue with my Captivate, its was working fine for the past week. It started giving me problems like battery temps too high, cant charge, had to charge it manually, removing battery & charging it all night. All this happened when im with stock rom latest with leaked 2.3.5
& i did unlock this with changing the 01 digit to 00 in efs file.
From the past 2 days im trying to install CM10,9, 10.1..... after installation it shuts down itself. Not able to use it.
Is there any way around to make this work. If pics are needed i can provide that too.
Thanks
No reply... :/
Some one should have had an issue.
vivek90 said:
Heys Guys Im having an issue with my Captivate, its was working fine for the past week. It started giving me problems like battery temps too high, cant charge, had to charge it manually, removing battery & charging it all night. All this happened when im with stock rom latest with leaked 2.3.5
& i did unlock this with changing the 01 digit to 00 in efs file.
From the past 2 days im trying to install CM10,9, 10.1..... after installation it shuts down itself. Not able to use it.
Is there any way around to make this work. If pics are needed i can provide that too.
Thanks
Click to expand...
Click to collapse
When/how does it happen?
What are the changes/mods you made?
Did you restore anything?
Did you try different kernel settings?
Did you try flashing a different kernel (like Semaphore?) or flashing a different ROM?
I could be asking more questions but really, I dunno what causes it, I can only guess. Also a search in the CM10.1 thread might give you an answer to your SoD <-- Should've been your first step*
BWolf56 said:
When/how does it happen?
What are the changes/mods you made?
Did you restore anything?
Did you try different kernel settings?
Did you try flashing a different kernel (like Semaphore?) or flashing a different ROM?
I could be asking more questions but really, I dunno what causes it, I can only guess. Also a search in the CM10.1 thread might give you an answer to your SoD <-- Should've been your first step*
Click to expand...
Click to collapse
It just happened, battery temp too high errors, thought flashing CM9 would solve this, was bored of Stock Gingerbread, flashed corn kernel & flashed cm9 rom. I did mod anything else. That all
vivek90 said:
It just happened, battery temp too high errors, thought flashing CM9 would solve this, was bored of Stock Gingerbread, flashed corn kernel & flashed cm9 rom. I did mod anything else. That all
Click to expand...
Click to collapse
Battery temp to high is a big problem. Did you overcloak? Have you running bunch of stuff at the same time?
When it shuts down, does it reboot by itself or you have to do it manually?
Sent from my SGH-I747 using xda app-developers app
Sounds like Battery health status does not equal healthy. That forces an immediate shutdown, whether due to temperature or excessive internal resistance. That's because once a Li ion battery reaches critical temperature, it combusts and destroys your phone, burns you and anything around it, etc.
GET ANOTHER BATTERY ASAP.
Stop trying to circumvent high temperature shut down.
.........
BWolf56 said:
Battery temp to high is a big problem. Did you overcloak? Have you running bunch of stuff at the same time?
When it shuts down, does it reboot by itself or you have to do it manually?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Recently i bought a new battery, original samsung make, it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high". No overclocking here, just used to call, receive & wifi hotspot. Currently i charge battery in a battery charger & use it in phone.
U pointed out something right, sometimes screen just goes blank, i have to manually switch it on.
laughingT said:
Sounds like Battery health status does not equal healthy. That forces an immediate shutdown, whether due to temperature or excessive internal resistance. That's because once a Li ion battery reaches critical temperature, it combusts and destroys your phone, burns you and anything around it, etc.
GET ANOTHER BATTERY ASAP.
Stop trying to circumvent high temperature shut down..........
Click to expand...
Click to collapse
I bought a new battery & it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high".
But im not able to under stand, why is Cynogenmod shuts down itself after installation, can i just stop shutting down ?
vivek90 said:
Recently i bought a new battery, original samsung make, it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high". No overclocking here, just used to call, receive & wifi hotspot. Currently i charge battery in a battery charger & use it in phone.
U pointed out something right, sometimes screen just goes blank, i have to manually switch it on.
I bought a new battery & it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high".
But im not able to under stand, why is Cynogenmod shuts down itself after installation, can i just stop shutting down ?
Click to expand...
Click to collapse
I think it's not CM related but hardware related. Does this happen when not using the wifi hotspot too?
I'm thinking your battery is bad (even if new), charger is bad, connection is bad (maybe from water/humidity) or that your usb port is bad. No easy way of finding it other than testing.
BWolf56 said:
I think it's not CM related but hardware related. Does this happen when not using the wifi hotspot too?
I'm thinking your battery is bad (even if new), charger is bad, connection is bad (maybe from water/humidity) or that your usb port is bad. No easy way of finding it other than testing.
Click to expand...
Click to collapse
May be yes, the phone some times just goes blank, i have to manually switch ON. The same battery works well in my frnds phone quite well.
Port dont know, i can copy files no errors even now when i plug it in on stock gingerbread the battery doesnt charge but can copy files as before.
Since the batt works well in other phone, a couple of ideas. Perhaps silly to ask, but just checking:
did you wipe battery stats in cwm after flashing?
did you clean the phone's battery terminals with a bit of alcohol?
what's the battery health,temperature and voltage history look like, if you can get it. you can log it with battery monitor widget or similar app. set to short 1 minute interval for testing.
.........
I found another thread with the same issue but no satisfactory answer for me - http://forum.xda-developers.com/galaxy-s5-mini/help/g800f-battery-drain-off-t3445071
A friend's S5 mini G800F suddenly started draining battery - it will completely drain in about 3 hours even when the phone is turned off. My friend claims that nothing changed right before the problem started - no updates, bumps, etc, but I wasn't using it so I can't verify that is the case.
Things I have tried.
- running in safe mode
- wiping the cache
- factory reset
- new battery
- installed cyanogenmod 13.0.1
- battery calibrator app
The other thread was resolved by installing a new mainboard which unfortunately is not an option as I am out of the country currently. With the things that I have tried I am fairly certain that software is not the issue, but I really have no idea where to look when it comes to hardware.
The phone charges normally and works fine as long as it is plugged in and does not overheat but as soon as the cord is unplugged the percentage quickly drains and will continue to drain even when the phone is off.
Any help would be appreciated.
You can install Ampere to monitor both charging and draining currents. But if even with a new and known good battery the problem exists then most probably it's a hardware issue... Good luck.
lfom said:
You can install Ampere to monitor both charging and draining currents. But if even with a new and known good battery the problem exists then most probably it's a hardware issue... Good luck.
Click to expand...
Click to collapse
Ok, I'll give that a try and see what I can figure out.
Unfortunately I was unable to find any useful information with the app. I am left with the conclusion that there is a hardware issue somewhere draining the battery...
the same issue here
It's about two weeks my phone has the same behavior,
I've already tried two batteries from two vendors, but with no success,
In the service they refused to replace the hw, as it would be actually a "new phone"
So I was forced to buy a new one.
As you know, i have same issue. I posted a "fix" but it didnt really do anything.
It turns out its a issue in the usb circuit.
An possible problem-causer could be:
Bad battery
2. Bad sim/sd
3. Bad software (factory reset/reflash stock
4. USB circuit.
So, you would need an hardware repair. It wont cost much, as its only a circuit.
I am gonna repair my phone soon. Ill report what happened then.
Have you been able to fix the issue? Can you provide some details about it?
Hello!
I have a huge battery problem with my Note 5... I flashed a lot of roms to see if anything changes but it doesn't... I always get max. 3hours of screen on time. Even after installing xposed for amplify and greenify but it doesn't make any difference. In the battdry settings i always get this Android OS bug which is very high. But it doesn't go away with the latest SuperSU or disabling a lot of things in the settings (googled this Android OS bug) I even replaced the battery but it didn't help at all... I'm really desperate...
Perhaps one of you has a solution, that would be fu******* awesome!
Thank you
I found the problem finally!! BLUEDROID_TIMER is causing wakelocks!! If i turn bluetooth off everything is great! But i have bluetooth headphones and i can't find a fix online...
battery drain issue may be the cause for this so try to flash stock rom and then supersu systemless with xposed and check your battery
also it may be an app that you installed causing this wake locks so I suggest making a factory reset if the problem presists
AlMaghraby said:
battery drain issue may be the cause for this so try to flash stock rom and then supersu systemless with xposed and check your battery
also it may be an app that you installed causing this wake locks so I suggest making a factory reset if the problem presists
Click to expand...
Click to collapse
I flashed at least 10 roms with no success... I amplified this bluedroid_timer wakelock and battery sees to be better.
only 3hours of screen time??? I wish i got 2hr
Hey guys
I already posted my problem in the thread related to LineageOS, but since the issue couldn't be solved I want to try it this way.
So what is my problem?
While using my phone it gets very hot. According to Powerful Monitor the CPU gets up to 65 °C and battery up to 35 °C, while under load. Besides this my battery goes down rapidly. So watching 10 minutes of YouTube sucks up 8-9 % battery. Just a plain normal video.
What is my setup?
I9295, running LineageOS 14.1-2017-06-06-UNOFFICIAL-jactivelte, OpenGApps 06-07-17 nano, only apps installed manually are GeekBench, Powerful Monitor and YouTube. Baseband is I9295XXUDOB4 (German unbranded DBT). I bought a new original Samsung battery and currently using it. So it's basically stock LineageOS.
What have I already tried?
- flashed stock firmware (all available for Germany that are unbranded). With and without erasing NAND, with different Odin versions. Last time I flashed I used Odin 3.07
- different batteries: the old ones the phone came with (bought it used), the new one I bought separately, a new one from PowerCell with higher capacity (2900 mAh)
- different phones. I have a second I9295 from a friend, that worked definitely without any issues. Same problem.
- different custom ROMs: now I'm running LineageOS, but I also tried CM13 (20161228), CM12.1, MIUI and Super WizCyan (everything from xda)
Is it possible break something ciritcal when disassembling the phone? Both phones came with broken covers for the USB port, so I opened it, but only removed the screws and the mid-frame (?) and replaced the cover. Nothing was damaged, at least I was very carefully and didn't see anything that looked suspicious.
Another very strange thing I noticed:
If I use the phone a lot (lets say 30 minutes, so almost 25 % battery!) and after that the phone is not in use for an hour or so, the battery goes up for up to 7-8 %. How it that possible?
I really have no idea what else to do.
Any help is appreciated.
dotnano said:
Hey guys
While using my phone it gets very hot.
I bought a new original Samsung battery and currently using it. So it's basically stock LineageOS.
Any help is appreciated.
Click to expand...
Click to collapse
Hey there. Well, there are tons of possible reasons why your phone acts like that. My modest opinion is that you have some sort of wakelock active in background. Install both Wakelock Detector and Gsam Battery Monitor, grant all the permissions and let it obtain data for some minutes. Than look at the results, and check if there's any Wakelock active. If instead Gsam shows an excessive consume by the kernel, try in terminal the following commands:
Code:
su
setenforce 1
setenforce 0
Then see if there's still the drain (you have to wait some minutes).
If it still doesn't work, I'd advice you to update to the latest stock firmware (doesn't matter which Country, just select a non-branded one), reinstall LOS again and verify if with nothing installed you still get the battery drain.
Anyway, IMHO it's not an hardware related problem, even messing up with the components this shouldn't happen. The only hardware fault could be the battery short-life, but 1st you said you just replaced it, 2nd it would not justify the thermal overload. Let us know
Thank you very much for your answer. I'm quite short on time next days but maybe I have a few minutes on sunday.
On the matter latest stock firmware: already tried that on monday, still too much battery drain, but I didn't install LOS till now. Maybe sunday.
But still thank you
Finally I found some time to try your suggestions
I skipped the part of trying it on the old setup, so I flashed everything new with latest stock(UDOB4-DBT, not the last one but still Android 5.0.1), then TWRP 3.1.0, after that LOS 14.1-20170606 and OpenGApps 7.1 nano from 17-06-06. Only apps I installed beside that are GSam Battery and Wakelock Detector. Root activated and granted where asked and needed.
Here I uploaded the pictures I took from GSam Battery.
So what seems strange to me:
- why is Phone Radio used at all? I don't have a SIM card inserted...?! It's on a very high level, even if the screen isn't on.
- The battery gets hot quite fast. If it's not in use, everything is fine. But as soon as I use the phone it gets hot.
- As you said: kernel usage seems quite high, tried to install "Terminal Emulator" and executed the commands - no difference.
According wakelock: where do I check that?
dotnano said:
- Why is Phone Radio used at all? I don't have a SIM card inserted...?! It's on a very high level, even if the screen isn't on.
- The battery gets hot quite fast. If it's not in use, everything is fine. But as soon as I use the phone it gets hot.
- As you said: kernel usage seems quite high, tried to install "Terminal Emulator" and executed the commands - no difference.
According wakelock: where do I check that?
Click to expand...
Click to collapse
Sorry for the delay, but if you do not quote/reply me I cannot see the message cause I'm not extremely active on XDA. Anyway...
- Phone Radio is used even without SIM, at least in TouchWiz, dunno in LOS, but it looks like so. The only way to disable it is Airplane Mode.
- It gets hot due to kernel usage, what I still do not understand is why it does so.
- Those commands where the only commands I think could be useful in this case (they set SELinux Permissive/Enforcing)
But if you say you get the Drain on TouchWiz too, the problem is serious and there's a (little?) chanche it would be HW related.
IvanCristina said:
Sorry for the delay, but if you do not quote/reply me I cannot see the message cause I'm not extremely active on XDA. Anyway...
- Phone Radio is used even without SIM, at least in TouchWiz, dunno in LOS, but it looks like so. The only way to disable it is Airplane Mode.
- It gets hot due to kernel usage, what I still do not understand is why it does so.
- Those commands where the only commands I think could be useful in this case (they set SELinux Permissive/Enforcing)
But if you say you get the Drain on TouchWiz too, the problem is serious and there's a (little?) chanche it would be HW related.
Click to expand...
Click to collapse
No need to apologise, you're doing this in your free time...
Besides that, I wasn't at home all week, so I couldn't try anything even if you had answered.
So, how do I get the kernel to calm down and stop draining my battery? I mean, I didn't install anything besides clean LOS and GApps. So what could lead to so much kernel usage? Are there any further information that could help you?
dotnano said:
Thank you very much for your answer. On the matter latest stock firmware: already tried that on monday, still too much battery drain, but I didn't install LOS till now.
Click to expand...
Click to collapse
I didn't read this post before, the points are two:
- No need to write Thanks, there's a button for it. It's free and very grateful
- If it drains even on stock it's a serious problem.
dotnano said:
So, how do I get the kernel to calm down and stop draining my battery? I mean, I didn't install anything besides clean LOS and GApps. So what could lead to so much kernel usage? Are there any further information that could help you?
Click to expand...
Click to collapse
The situation is very weird. Let's analyze.
1) TW/LOS doesn't matter. Battery drain in both
2) No apps installed which could cause wakelocks
3) Battery SHOULDN'T be the problem
4) The drain is recognised as kernel "usage", though it couldn't be real 'cause of point 1
5) Neither Permissive nor Enforcing SELinux mods helped
At this point it doesn't look so much a SW problem, but more an HW one. About:
dotnano said:
If I use the phone a lot (lets say 30 minutes, so almost 25 % battery!) and after that the phone is not in use for an hour or so, the battery goes up for up to 7-8 %. How it that possible?
Click to expand...
Click to collapse
Well, sometimes the discharge happens so fast the battery doesn't calculate the remaining capacity so well, and after some minutes the real charged cells are more than the "estimated" ones. It would explain the "goes up" of the percentage, but still not the drain.
It's very strange and very rare, but there's an infinitesimal possibility that the thermal paste went to the hell. And in this case there's not that much to do.
That's pretty pessimist though. I'd advice you to format everything, reinstall the latest stock TW and stick with it, and if it still doesn't work, try with some apps like Greenify and ForceDoze (this one works just with 6.0+) in order to at least TRY to reduce the drain.
I'm sorry I cannot help you more, if anyone has some suggestion, please let us know.
IvanCristina said:
I didn't read this post before, the points are two:
- No need to write Thanks, there's a button for it. It's free and very grateful
- If it drains even on stock it's a serious problem.
The situation is very weird. Let's analyze.
1) TW/LOS doesn't matter. Battery drain in both
2) No apps installed which could cause wakelocks
3) Battery SHOULDN'T be the problem
4) The drain is recognised as kernel "usage", though it couldn't be real 'cause of point 1
5) Neither Permissive nor Enforcing SELinux mods helped
At this point it doesn't look so much a SW problem, but more an HW one. About: Well, sometimes the discharge happens so fast the battery doesn't calculate the remaining capacity so well, and after some minutes the real charged cells are more than the "estimated" ones. It would explain the "goes up" of the percentage, but still not the drain.
It's very strange and very rare, but there's an infinitesimal possibility that the thermal paste went to the hell. And in this case there's not that much to do.
That's pretty pessimist though. I'd advice you to format everything, reinstall the latest stock TW and stick with it, and if it still doesn't work, try with some apps like Greenify and ForceDoze (this one works just with 6.0+) in order to at least TRY to reduce the drain.
I'm sorry I cannot help you more, if anyone has some suggestion, please let us know.
Click to expand...
Click to collapse
Next strange thing is, I have two S4 Active devices, both have the same problems. Am I just unlucky enough to get two broken phones?
Still, the device I got from I friend was ok the moment he gave it to me. He said battery lasted for only one day, but that would be ok. So it has to be something I did with the phone.
Youre are not alone. My Phone was/is also getting hot.
Then I did a full wipe ( format also internal memory partition!)
I'm current running cm13 (CM13 (20161228)). Batterie works now / normal ok / 1 / 2 Day s ( no great usage ). But when i telephone with someone it's getting hot in 15 min. Modem Version is I2995XXUDPB3.
dotnano said:
Next strange thing is, I have two S4 Active devices, both have the same problems. Am I just unlucky enough to get two broken phones?
Still, the device I got from I friend was ok the moment he gave it to me. He said battery lasted for only one day, but that would be ok. So it has to be something I did with the phone.
Click to expand...
Click to collapse
Have you flashed any custom ROM? Try downloading an entire stock firmware for your country / carrier from sammobile and flash through odin 3.09 and check. The S4 active generally gets hot on usage but should not get very hot. You can also try using powersave mode that limits cpu max freq and prevents heating. Battery on normal usage shoukd last for little under a day to a day with normal usage unless you are using data (otherwise set mobile networks to GSM only which saves battery and reduces heat)
JASONRR said:
Have you flashed any custom ROM? Try downloading an entire stock firmware for your country / carrier from sammobile and flash through odin 3.09 and check. The S4 active generally gets hot on usage but should not get very hot. You can also try using powersave mode that limits cpu max freq and prevents heating. Battery on normal usage shoukd last for little under a day to a day with normal usage unless you are using data (otherwise set mobile networks to GSM only which saves battery and reduces heat)
Click to expand...
Click to collapse
I have flashed the latest DBT (unbranded German) and I have the same problems. Does the version of Odin make a significant difference? I used 3.10.6.
dotnano said:
I have flashed the latest DBT (unbranded German) and I have the same problems. Does the version of Odin make a significant difference? I used 3.10.6.
Click to expand...
Click to collapse
Normally i have seen issues flashing through odin 3.10 and prefer 3.07 or 3.09. If the firmware flashed correctly and you do not have any issues then it should be fine.
CPU temp of 65% without powersave mode is fine and watching youtube videos does consume battery. Try a different charger / cable combination as that too can have issues. If the battery gets charged quickly (on stock kernel under 2 - 2.5 hours from 0 to 100) then there is definitely an issue with the charger and it will drain quickly too.
JASONRR said:
Normally i have seen issues flashing through odin 3.10 and prefer 3.07 or 3.09. If the firmware flashed correctly and you do not have any issues then it should be fine.
CPU temp of 65% without powersave mode is fine and watching youtube videos does consume battery. Try a different charger / cable combination as that too can have issues. If the battery gets charged quickly (on stock kernel under 2 - 2.5 hours from 0 to 100) then there is definitely an issue with the charger and it will drain quickly too.
Click to expand...
Click to collapse
I tried 3.10, 3.12 and 3.07 so far. Not successfully. Tried 3.09 now, we'll see.
I have a Sony Xperia Z1C as comparison, YouTube needs maybe 1% for 5 Minutes.
Cables/Chargers shouldn't be the problem. I have the original Samsung, also cable. Charged to 0 to 75 % in 90 Minutes. Same with cable and charger from Anker. So should be fine?
So no new ideas?
dotnano said:
So no new ideas?
Click to expand...
Click to collapse
I have no idea too but i have the same Trouble with mine BUT I'm still using the original Rom and didn't flash it. So maybe it is an Hardware issue.
My Battery is getting old, yes, but it is the third one. The Phone gets hotter than in its first years.
I hope you'll find a reason!
My i9295 always has been like this: 1 minute on-screen time = 1% battery loss. So this basically is a 2 hour phone... Stock or custom rom didn't matter. A friends i9505 used a lot less power, therefore I assume that the LCD (instead of the S4's AMOLED) is the problem.
Vardion said:
My i9295 always has been like this: 1 minute on-screen time = 1% battery loss. So this basically is a 2 hour phone... Stock or custom rom didn't matter. A friends i9505 used a lot less power, therefore I assume that the LCD (instead of the S4's AMOLED) is the problem.
Click to expand...
Click to collapse
Nah, why should it? There are a lot of i9295 users that don't have any problems.
Anyone found a consistent way to limit battery charge % on Android 11? The custom settings I used with Battery Charge Limit app on 10 work intermittently on 11. Often times I'd wake up to 100% charge.
Currently I'm using Advanced Charging Controller magisk module with it's accompanying AccA app but often AccA gets killed in the background even after not optimizing it in battery optimization. The only workaround I've found is to create a macro that opens AccA every time I plug in the charger. With that step it's consistent but I'd like to find something not so hacky.
I've been running A11 for about a week and did not encounter any issues with Battery Charge Limit. Maybe make sure that it's not battery optimized? I have it "not optimized" because I'm paranoid about it, rather than having direct problems.
jljtgr said:
I've been running A11 for about a week and did not encounter any issues with Battery Charge Limit. Maybe make sure that it's not battery optimized? I have it "not optimized" because I'm paranoid about it, rather than having direct problems.
Click to expand...
Click to collapse
I made sure battery charge limit wasn't optimized. You're using the same custom setting from android 10? Maybe I'll try it again
This the settings you have?
Path Data: /sys/class/power_supply/charger/charge_disable
Enable Value: 0
Disabled Value: 1
hawkswind1 said:
I made sure battery charge limit wasn't optimized. You're using the same custom setting from android 10? Maybe I'll try it again
Click to expand...
Click to collapse
I didn't change anything at all... and honestly with all of the other A11 problems I've been having... I didn't even think to check that it was working. It just has been. I also double-checked with AccuBattery and the history never shows above my limit.
This is my control file settings as seen on the main screen:
Code:
/sys/class/power_supply/charger/charge_disable, 0, 1
jljtgr said:
I didn't change anything at all... and honestly with all of the other A11 problems I've been having... I didn't even think to check that it was working. It just has been. I also double-checked with AccuBattery and the history never shows above my limit.
This is my control file settings as seen on the main screen:
Code:
/sys/class/power_supply/charger/charge_disable, 0, 1
Click to expand...
Click to collapse
I think that's the custom setting probably restored from your Google backup. Same one I was using. I'm gonna try it again though, thanks
hawkswind1 said:
Anyone found a consistent way to limit battery charge % on Android 11? The custom settings I used with Battery Charge Limit app on 10 work intermittently on 11. Often times I'd wake up to 100% charge. Currently I'm using Advanced Charging Controller magisk module with it's accompanying AccA app but often AccA gets killed in the background even after not optimizing it in battery optimization. The only workaround I've found is to create a macro that opens AccA every time I plug in the charger. With that step it's consistent but I'd like to find something not so hacky.
Click to expand...
Click to collapse
Have you tried Accubattery? Along with charge limiting it has other useful features, including reporting battery capacity vs. new (under health).
v12xke said:
Have you tried Accubattery? Along with charge limiting it has other useful features, including reporting battery capacity vs. new (under health).
Click to expand...
Click to collapse
Accubattery is fine and all for reporting and giving an idea of where you want to stop charging... but it has no ability to limit charging. The only thing it can do is nag you to take the phone off the charger. This thread is about root applications actually blocking the phone from charging past a certain level without making the user do anything or even notifying the user about what's being done.
I realize this is a couple of months old. but I just got a new OnePlus 8T, now rooted, and I'm trying to use Battery Charge Limit on it. I can't quite figure out the settings to have it work consistently. Let's say the phone is already at 100% when I plug it in. Battery Charge Limit starts, but then it flip-flops between Charging and Not Charging, starting and restarting. The phone woke me up last night because it was making a ding every time Battery Charge Limit flipped between charging and not charging. One would think that if the phone was at 100% Battery Charge Limit would turn off charging and let it drop down to my 85% limit and then back up to 91%, but never got above 91%. Thoughts? Thanks.
rcbjr2 said:
I realize this is a couple of months old. but I just got a new OnePlus 8T, now rooted, and I'm trying to use Battery Charge Limit on it. I can't quite figure out the settings to have it work consistently. Let's say the phone is already at 100% when I plug it in. Battery Charge Limit starts, but then it flip-flops between Charging and Not Charging, starting and restarting. The phone woke me up last night because it was making a ding every time Battery Charge Limit flipped between charging and not charging. One would think that if the phone was at 100% Battery Charge Limit would turn off charging and let it drop down to my 85% limit and then back up to 91%, but never got above 91%. Thoughts? Thanks.
Click to expand...
Click to collapse
It's possible it's not configured correctly for your phone. You can also just disable that notification channel, since mostly it's just annoying. It constantly fliping might mean that there's more than one control file for your phone type and it's using an ineffectual one that the OS is overriding immediately. For example, the default one it detects for Pixel 4's is not the one it should use.
jljtgr said:
It's possible it's not configured correctly for your phone. You can also just disable that notification channel, since mostly it's just annoying. It constantly fliping might mean that there's more than one control file for your phone type and it's using an ineffectual one that the OS is overriding immediately. For example, the default one it detects for Pixel 4's is not the one it should use.
Click to expand...
Click to collapse
Thanks for the reply. The problem is that I use the notification to trigger Tasker profiles, so I was hoping to figure out a way to get it to stop flipping back and forth while also retaining the notification. I think it's just the standard control file since it's a OnePlus phone, but I'm not sure I can figure out otherwise. When I first start using BCL, I found the control file and was able to manipulate it with a SQL editor and Shell commands in Tasker, but I haven't poked around the OnePlus 8T that much yet.
Just as a PSA, I think Adaptive Charging from the January update can conflict with this. On days where I set a morning alarm, I found that my battery was more full than it should be. I suspect that Adaptive Charging does something that Battery Charge Limit cannot block. I won't know for a few days if turning this off in settings fixes things 100% or the January update just really screws with this.
Battery Charge Limit settings for pixel 3
Hi all, I like the app, Battery Charge Limit (root required), but was wondering how to set the control file. I works fine with Xperia (with/without Lineage), but doesn't work with Pixel 3 stock firmware (Android 10). And finally found how to...
forum.xda-developers.com
Well, as a root method it does seem to work. Depending on your taste, it might be cleaner than an app toggling a different variable. Of course you need an app to set the file back to 100 when you want it. Some Tasker widgets work for my purposes... could probably make it a QuickSettings toggle in the shade, actually.
Bottom of that thread, I was wondering specifically if there might be way to force an unrooted device to think it met one of these conditions, so it only charges to 80%.
Specific post link:
Battery Charge Limit settings for pixel 3
Hi all, I like the app, Battery Charge Limit (root required), but was wondering how to set the control file. I works fine with Xperia (with/without Lineage), but doesn't work with Pixel 3 stock firmware (Android 10). And finally found how to...
forum.xda-developers.com
i.e.
... your phone automatically limits charging to about 80% under certain conditions:
Continuous charging under high battery drain conditions, like game play.
Continuous charging for four days or more.
I've done very little research on this, but I expect the ways to fool the phone into thinking those things are happening is even more complicated than using that root file control. Meaning also requiring root but manipulating other control files.
I suppose you could have a case and a ribbon USBC connector that fools the charging logic into thinking it is constantly connected to a hardware charger even though it's still at a net negative power. After 4 days of having the case on, it might work. I don't know why anyone would have already built something like that, however.
I would root my phone but, as my daily driver, I need things like banking apps to work. They (at least some) detect rooted phones and refuse to load as a security measure (which is probably a good thing) :-(
Banking apps are usually just a frontend to their website used API. They have no problem with you using a browser on a rooted phone or Linux PC, etc. Any app that stores sensitive data on your phone and relies 100% on the filesystem being locked down was created wrong and lazily. The only thing about banking apps that might be legitimate is when things like unique CC info is stored for NFC and using a TPM can't be assured. Most banking apps, however, do not store anything sensitive on your phone aside from a login token which all websites also do. (it's called a cookie)
My personal preference is that no app is better for me than being able to root my phone. I don't play mobile games that want to keep you from cheating and I don't even care about Google Pay, which I'm not sure has legitimate need to block root either... they just do it to keep banks happy, which as I suggested, I think they're full of BS.
The only thing more BS than this no-root nonsense from app companies is when carriers do it by locking bootloaders. I try to re-use my phones for as long as possible and without the ability to limit battery charge, the batteries swell and die quickly, every time. It's good news that Google added code where phones plugged in constantly will limit charge automatically... but I doubt there is a way to trick it from the outside. (without root)
Hmmm. Maybe lazy programming, but I'm not ready to change my Bank so I can root my phone
Back to the topic... I don't think I'm ready to trust the /sys/devices/platform/soc/soc:google,charger/charge_stop_level method. Several times I found my phone at low battery and not pulling any current from the USB port, but not losing charge either. It had put itself into a stalemate where it was stuck below 10% for hours. Resetting the value from 60 to 100 allowed charging again. The battery charge limit app never really caused this. So I guess I'm going back to the full app method.
jljtgr said:
Back to the topic... I don't think I'm ready to trust the /sys/devices/platform/soc/soc:google,charger/charge_stop_level method. Several times I found my phone at low battery and not pulling any current from the USB port, but not losing charge either. It had put itself into a stalemate where it was stuck below 10% for hours. Resetting the value from 60 to 100 allowed charging again. The battery charge limit app never really caused this. So I guess I'm going back to the full app method.
Click to expand...
Click to collapse
I would like to definitely solve this problem I have been struggling with for years. What did you do, can you please help me? It seems extremely similar to what you wrote here.
I have been using battery charge limit on my Xiaomi Mi Mix (1st model) since android 7.1 (lineageos) (and I might have messed with a couple files, not sure, can't remember). When updating to android 9 (lineageos) couple years ago I started having the problem you described. Also I notice sometimes I plug the phone at safe levels such as 35% or 60% and it doesn't charge same thing. Also it only charges with certain chargers and not others.
Earlier today it was 11% battery, could not boot android, didn't charge. I got the idea for the first time to try booting in TWRP (on+volume up buttons) and it immediately started charging at full speed. So there's obviously nothing wrong in the hardware, it's software or just config.
I would like to definitely solve this problem, but I don't understand exactly what you did on your side to fix it. Please reply or message me if you have any suggestion Thank you!