Database Develop

[Think Tank] Modify Kernel to fix charging

I haven't actually looked at the battery driver or even the kernel for that matter, but does it specifically state the cutoff voltages for charging the battery? If it does, we should compare those to what the phone is charging the battery to when the phone is off and make them match. Hell if you want to live on the wild side bump it up another .05 - .075V or so...

Just a question.....but do you know what you are talking about??
Froyo seemed to solve the charging 'problem' for me, then again I never had a charging problem.

Qazme said:
Just a question.....but do you know what you are talking about??
Froyo seemed to solve the charging 'problem' for me, then again I never had a charging problem.
Click to expand...
Click to collapse
Erm, how did it fix it? We still have that problem.

I believe what he is talking about is modifying the kernel to allow the battery to fully charge when powered on rather than leaving the "buffer" which requires the bump charge to get the extra 10% or so out of the battery. I'd definitely like to see this as well, but I've found performing the recalibration did help a bit.

Disclaimer: I'm a noob and don't know ****!
However, it would seem if htc (or google), put code in the kernel to prevent the phone from charging to 100% while turned on, I'm sure they had good reason. My guess would be to keep the phone from over heating.
It would seem that if the phone is on and draining the battery, but at the same time you're trying to charge the battery, achieving that last few percent might be difficult and could take considerable more time, and thus getting hotter.
Just a guess though.
________________________________
Unrevoked forever
SkyRaider 2.5.2 Sense
Hrdra kernel ocuv_ov_v10 (#2)

I'll look at the battery driver when I get home (currently at work), but I have seen devices where charging limits were invoked directly in the kernel. These could be modified if they are.
On the issue of heat, manufacturers play it VERY safe. It looks bad if someone is charging their phone in their car during the summer and the battery cooks off in the passenger seat. I'd be fairly comfortable pushing the battery to a little bit higher voltage than it is right now.

What about the charging SPEED? Myself and several others have noticed that Froyo ROMs charge at a much slower rate, plugged in to ac power, compared to 2.1 Rom. For me, it takes about twice as long to charge. Is this something that could also be addressed with a kernel fix? I literally went from being able to charge from ~10% to full in about 90 mins, to now taking about 4 hours on Froyo.

bast525 said:
What about the charging SPEED? Myself and several others have noticed that Froyo ROMs charge at a much slower rate, plugged in to ac power, compared to 2.1 Rom. For me, it takes about twice as long to charge. Is this something that could also be addressed with a kernel fix? I literally went from being able to charge from ~10% to full in about 90 mins, to now taking about 4 hours on Froyo.
Click to expand...
Click to collapse
The 2.15 radio probably broke the phone's ability to differentiate between the wall-charger (fast) and normal USB (slow). The reason I say "radio" and not "kernel" is because it charges slowly when powered off as well. Hopefully the radio included in the upcoming OTA will fix this.

I had the slow charging problem on the 2.05 radio as well but doesn't change much about what's being said about a potential fix.
Anyone able to confirm that this (something in the radio) is the reason?
Hope the OTA comes soon so I can get back to recharging in a timely fashion.
Sent from my Dinc using XDA App

Qazme said:
Just a question.....but do you know what you are talking about??
Froyo seemed to solve the charging 'problem' for me, then again I never had a charging problem.
Click to expand...
Click to collapse
Apparently you are one of the users that were lucky enough not to have this issue. This thread is not for you. Move on. And btw, Froyo did not fix this problem. Again, nothing for you to see here, move on.
For the rest of us who are interested in solving this issue we will continue to put ideas out there in the hope that a smart one figures this out. Until then, we will keep reading about how fortunate some people are and how some other unfortunate people are willing to work on this. Thanks OP.

the difference between bump charging and not never really affected me because the phone charged so damn fast, that just plugging it in for a few minutes helped out a ton. but now with froyo, it literally take 5 to 6 times longer to charge to 100%. its ridiculous

i got sick of letting my phone charge overnight then 10 min after i unplug it in the morning its down to 92%. and unless you charge it while the phone is off it rapidly drops all the way down to like 80% before it starts decreasing normally, at least for me. so i started turning it off and topping it off in the mornings for about 30-45 min before i would leave for work, doing this i noticed a HUGE difference in my battery life through out the day. that got to be a pain because sometimes i just don't have time to do that in the mornings, so i ended up buying an external charger and an extra battery. this way charge the extra battery overnight on the external charger, pop the fresh battery in the phone in the morning and i'm ready to go. but all this could be avoided if the phone would charge the battery as good as the $2 wall charger, so if you could find a fix for this battery problem it would be awesome.

I had slow charging with 2.05 and 2.15 radios, unfortunately...

Did any of you that are having this issue root and install froyo immediately after buying the phone? a friend of mine is having a similar issue. Have you tried battery recalibration? Also I would recommend checking your up time and awake times in battery info and see if there's something keeping your phone awake while charging . One last thing, try installing battery save mode toggle from market.
Sent from my ADR6300 using Tapatalk

I've been messing with the slow charge issue all night tonight, and as far as I can tell, it is not the 2.xx radio, and it must be the .32 kernel.
Slow charging started for me when I installed the first 2.2 leak which had the 2.05 radio, and remained on the the 2nd 2.2 leak and 2.15 radio. Before that I had the 2.05 radio on 2.1 and charging was normal, tonight I rolled back to complete stock 2.1/1.0 radio and charging was normal again, I kept the 1.0 radio and installed a 2.2 rom, charging slowed again, changed to 2.15 radio, still slow, so I installed the old CM6 test 8 rom which was used the old kernel with the broken camera, and sure enough, charging was fast again.
I'd really love to figure this out, if any of you get on IRC and want to discuss this, /msg digi

earthtodigi said:
I've been messing with the slow charge issue all night tonight, and as far as I can tell, it is not the 2.xx radio, and it must be the .32 kernel.
Slow charging started for me when I installed the first 2.2 leak which had the 2.05 radio, and remained on the the 2nd 2.2 leak and 2.15 radio. Before that I had the 2.05 radio on 2.1 and charging was normal, tonight I rolled back to complete stock 2.1/1.0 radio and charging was normal again, I kept the 1.0 radio and installed a 2.2 rom, charging slowed again, changed to 2.15 radio, still slow, so I installed the old CM6 test 8 rom which was used the old kernel with the broken camera, and sure enough, charging was fast again.
I'd really love to figure this out, if any of you get on IRC and want to discuss this, /msg digi
Click to expand...
Click to collapse
Great work. on testing at least...
Is there anyone out there who can help fix this? I hate these slow charge times.

I thought the issue was that the phone starts running off battery one its at 100%, not that it can't charge the last 10%...am I misunderstanding that?
I've tested this by taking it off the charger as soon as the light turns green...seems I get much better battery life this way.

This doesn't quite explain why some of us have had no problems at all either. Maybe an issue with newer devices but personally my device has been up for over 31 hours since charge and haven't noticed this issue but a friend of mine has complained of it, and he recently bought his device. Tomorrow after I charge my device I'll post with findings after charging.
Sent from my ADR6300 using Tapatalk

trunksta said:
This doesn't quite explain why some of us have had no problems at all either. Maybe an issue with newer devices but personally my device has been up for over 31 hours since charge and haven't noticed this issue but a friend of mine has complained of it, and he recently bought his device. Tomorrow after I charge my device I'll post with findings after charging.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
this has to do with 2.2 and new kernels. not stock 2.1.

trunksta said:
This doesn't quite explain why some of us have had no problems at all either. Maybe an issue with newer devices but personally my device has been up for over 31 hours since charge and haven't noticed this issue but a friend of mine has complained of it, and he recently bought his device. Tomorrow after I charge my device I'll post with findings after charging.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I pre-ordered my phone and I have the charging issue as well so it can't be new phones vs old phones. I hope it gets figured out soon.

2600Mah ext batt+AMERICANANDROID TEST

This a combined test of an unofficial extended battery and a gingerbread rom for the HD2
The battery:
Unofficial 2600Mah(not confirmed) extended battery
The Rom:
AmeriCanAndroid AOSP HD2
GB233 CM7030111 booted from SD
the circumstances:
fully charged battery
NO cable plugged in the whole time, phone was on all time
Loud ringtones, vibrate on
launcher pro
beautiful widgets on home screen
mobile data globally off (don't have a data plan), deleted apn
wifi on/off manually, only when I needed it. It was on for:3h09m29s
autosync off, wifi enabled autosync
talktime: about 30 calls, some were very short 10-15sec, some longer 5-10min all togeher 46m20s +10text message
Screen brightness on auto, Screen filter on 48% when in low light conditions
Screen was on for 2h36m08s
Signal Reception 0-4 bars depending on location, most of the time around 3 bars
Used apps:
Soundhound, Maps/streetview, Earth, Facebook, Market, app installs, Nfs Shift(5min), DolphinHD, Astro, Poweramp couple of minutes each per day
GPS was off the whole time, didn't need it.
I used the phone moderatly, not excessively. Only turned the screen on when I needed it to be on. Obviously I wanted the battery to last long, but used my phone when I needed to.
Drain readings seem to be fine, got stuck on 15% and 1% for a while, you can see it in the diagram.
See currentwidget log as well
WELL:
2DAYS18HOURS14MINUTES51SECONDS
This should be more than enough.
PLEASE NOTE, that short times of Screen/Wifi uses don't appear under the diagram

How long does the original battery last for you?

the results seems great, maybe i should get one of those as well!!

Which app did you use?...than i can do the same with a NAND ROM of android using an extended battery,too?
Sent from my HTC HD2 using XDA Premium App

robrob777 said:
How long does the original battery last for you?
Click to expand...
Click to collapse
More than 24 hours on moderate use. About 12 hours on excessive use. Might test that as well soon. It is a great idea to have two of those and swap them when needed. But I only managed to get these times with the rom above.
Sent from my HTC HD2 using XDA App

jonas2295 said:
Which app did you use?...than i can do the same with a NAND ROM of android using an extended battery,too?
Click to expand...
Click to collapse
You mean the app for benchmarking?
The diagram thing is a built in gingerbread feature I guess. Settings-About phone-battery use and tap the diagram on top
I used currentwidget to see drain in Mah.

I am testing the OEM original battery with the same rom, will post the results soon.

Wow two days thats impressive. I have a different rom. I might consider getting an extended battery now I can barely squeeze a few hours out of my phone.

hey frkm where didi u buy it?.plz give link fir that

You had to remove the battery to spend 100% of energy?
Edit: Sorry, had no read this:
NO cable plugged in the whole time, phone was on all time

Where did you get the battery? I checked ebay and only found the 2400mah version now.
Also any more updates about it?

have you test the battery with windows phone 7? it works?

i use 2600 ma too, n using hyperdroid n tytung kernel v8 or higher...
i think tytung the most compatible with 2600 ma batt

I bought the 2400mah battery, but it turned out it was marked 2600mah.
It lasts for a full day before it powers down, then it shows up as 44% battery if I take it out and put it back in. In process of testing it now. It's normal use with over 12hrs of poor reception and a few hours of wifi.
I'll probably boot into SD Android and retry this test.

aceo07 said:
I bought the 2400mah battery, but it turned out it was marked 2600mah.
It lasts for a full day before it powers down, then it shows up as 44% battery if I take it out and put it back in. In process of testing it now. It's normal use with over 12hrs of poor reception and a few hours of wifi.
I'll probably boot into SD Android and retry this test.
Click to expand...
Click to collapse
Please do test and let us know, i am using tmobile HD2 running SuperFroyo ROM from SD, doesn't matter how i shut off the batt. life is not good as at all.
I am also looking to an extended batt. with batt. cover from ebay, i came across this:
http://cgi.ebay.com/2400mAh-Extende...Accessories&hash=item27b991a2d4#ht_2375wt_905
What do u think.
Thanks.

[Q] Nook battery dies fast

I only have 5 widgets, and my brightness is also low as possible. I have wifi off when i don't use it, but my battery still dies kinda fast. Should i delete cell standby? And what else can i do?

You really should define "kinda fast" so folks can answer objectively

Well just playing games like angry birds for 20 minutes it drops like 10%

EverythingNook said:
Well just playing games like angry birds for 20 minutes it drops like 10%
Click to expand...
Click to collapse
1) Which ROM
2) What widgets
3) What are you using to monitor battery drop
10% in 20 minutes (screen on, in use) is pretty aggressive.

HotShotAzn said:
1) Which ROM
2) What widgets
3) What are you using to monitor battery drop
10% in 20 minutes (screen on, in use) is pretty aggressive.
Click to expand...
Click to collapse
1. Stock with launcherpro
2. Typoclock power control beautiful battery google search and music
3. Beautiful battery

EverythingNook said:
1. Stock with launcherpro
2. Typoclock power control beautiful battery google search and music
3. Beautiful battery
Click to expand...
Click to collapse
What drain are you seeing with screen off/idle?

with the screen off for about 5 hours i saw a 21% drain.

Drop the widgets and livewallpaper if you've got it. Retest standby.
If you're getting high battery drain during standby your nook isn't going into deep sleep and chances are that background overhead translates to poor efficiency at idle when the nook is on as well. Couple poor idle efficiency with CPU intensive work while in use and your overall battery life is terrible.
If you're forcing the nook to stay out of deep sleep for other reasons like keeping wifi alive then you may be stuck with living with some sort of elevated drain but you can minimize it by reducing idle overhead by keeping widgets to a minimum and refraining from using live wallpapers and other background services that aren't critical.

Tacking on to here rather than starting a new thread...
My Nook Color rooted, but still on stock ROM goes from 100% charge to 25% in about 8-9 hours with zero usage. Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running. I do have Google Voice app installed.
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Thanks in advance!

distortedloop said:
Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running.
Click to expand...
Click to collapse
If you suspect it, disable it and see. I'm thinking that would be a prime suspect.
distortedloop said:
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Click to expand...
Click to collapse
I believe typically overnight you should see less than 10% drain.

In CM7 at least, in Spare Parts you can see what uses the battery while the NC is asleep.

distortedloop said:
Tacking on to here rather than starting a new thread...
My Nook Color rooted, but still on stock ROM goes from 100% charge to 25% in about 8-9 hours with zero usage. Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running. I do have Google Voice app installed.
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Thanks in advance!
Click to expand...
Click to collapse
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked

hxh103 said:
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
Click to expand...
Click to collapse
No, not yet. It's 100% stock, other than rooting and downloading apps. I'm going to put SystemPanel on it and see if it gives a clue.
I've got a good idea of how to track down battery issues on most android devices, I was just mostly curious what the typical drain other rooted users saw was.
Thx for the suggestions to all.

hxh103 said:
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
Click to expand...
Click to collapse
Good lord, this isn't going to help anything. Normal Nook Colors on the stock ROM (and kernel....) use about .2%/hr in standby.
Clearly something is running wild on this guys NC, and needs to look at Spare Parts. Install it from the market.
System Panel as well as other tools can help as well.

Okay, I'm a pretty smart guy usually, but I'll publicly put on the dunce cap and admit to my ignorance on this one.
System Panel actually showed some amazingly good lack of drain with all my apps running.
The reason my battery was so low when I checked it each afternoon is because even though I thought I was charging the thing over night, I wasn't. I was using a regular micro-usb cable for my phone to plug the thing in most nights.
Turns out the Nook Color has an extra deep micro-usb receptacle and requires a better endowed male plug to get it charged properly.
Lame...
(Lame of me, but also lame of B&N to make such a design decision. What were they thinking? I HATE proprietary connectors.)

distortedloop said:
Okay, I'm a pretty smart guy usually, but I'll publicly put on the dunce cap and admit to my ignorance on this one.
System Panel actually showed some amazingly good lack of drain with all my apps running.
The reason my battery was so low when I checked it each afternoon is because even though I thought I was charging the thing over night, I wasn't. I was using a regular micro-usb cable for my phone to plug the thing in most nights.
Turns out the Nook Color has an extra deep micro-usb receptacle and requires a better endowed male plug to get it charged properly.
Lame...
(Lame of me, but also lame of B&N to make such a design decision. What were they thinking? I HATE proprietary connectors.)
Click to expand...
Click to collapse
Extra WIDE, not deep. And there's good reason USB standards are .5A over the typical 4 pin connection. The B&N cable has FOUR extra pins, delivering the other 1.4A of power.

Extra deep. Two stages...
First stage 5 pins, second stage 12 pins...
Sent from my Nexus One using XDA Premium App

Yup same cable as my Droid2 and Droid before it....

Krazypoloc said:
Yup same cable as my Droid2 and Droid before it....
Click to expand...
Click to collapse
Does this mean we can use the droid2 and droid's cables as alternatives?

khaytsus said:
Extra WIDE, not deep. And there's good reason USB standards are .5A over the typical 4 pin connection. The B&N cable has FOUR extra pins, delivering the other 1.4A of power.
Click to expand...
Click to collapse
Thanks for the extra info about the additional voltage; so it will charge much faster this way? (rhetorical question)
I still am annoyed at yet another non-standard cable that I'll have to carry around with me when I travel to keep various devices charged, but in the scheme of things it's a minor annoyance. Stuff like this should be standardized, IMHO.
And it's extra DEEP, not wide. It's the same width as a standard micro-usb cable or I wouldn't have been able to stick my phone's charging cable into it at all, but I was able to, it just didn't go in deep enough to charge at all. On the flips side, the B&N cable fits into my phone, but only inserts half-way deep; if it were extra wide it wouldn't fit into my phone at all.

Bluetooth sucking battery?

I just got this watch and updated it. On the first day of real-world use, it sucked up around 10% an hour. At first I thought that this was normal, but when I looked at the battery stats Bluetooth had used 80 to 90 percent, while the others only used 1%. Are there any tips or way I can help with this? I did update to the beta version (the one with Android o as the base and not n) so if that's the issue I'm fine with that, it does make it to around 4 pm and I wake up at 6-7. This is a very good watch though. I had tilt to wake, aod, Bluetooth and wifi although wifi didn't appear to use much. Cellular is disabled because I don't have a plan for it.

I also just got this watch, and was concerned about the rapid battery usage. However it is now much better. This could be for 2 reasons, or one or the other. The first is that the initial pairing causes a lot of activity over Bluetooth while the watch updates and syncs all apps and may have just settled down. The other, and from advice on this forum, was that I disabled cloud sync (not that easy to find, go into Android Wear app on phone then Settings, then Privacy and Personal Data). Since then the battery life has improved vastly. Hope that helps.

zjjpp said:
I just got this watch and updated it. On the first day of real-world use, it sucked up around 10% an hour. At first I thought that this was normal, but when I looked at the battery stats Bluetooth had used 80 to 90 percent, while the others only used 1%. Are there any tips or way I can help with this? I did update to the beta version (the one with Android o as the base and not n) so if that's the issue I'm fine with that, it does make it to around 4 pm and I wake up at 6-7. This is a very good watch though. I had tilt to wake, aod, Bluetooth and wifi although wifi didn't appear to use much. Cellular is disabled because I don't have a plan for it.
Click to expand...
Click to collapse
At least you get something other than Bluetooth. I'm on the beta as well as now I get nothing but Bluetooth listed. I had major drain and thought it might be because I tried sideloading apps via Bluetooth. Whatever it was I couldn't figure it out. Factory reset and I'm back to normal
Sent from my Pixel XL using Tapatalk

Yea today I woke up at the same time and before, at 3 I would be charging it from 5%. Today, it's 6 and it's at 33. I did disable cloud sync and a weather complication. I also disabled NFC. Other than that I dont remember changing anything else.

You don't happen to be using a Pixel 2 XL?

iliketrains said:
You don't happen to be using a Pixel 2 XL?
Click to expand...
Click to collapse
Having a very similar problem and I am indeed using a PIxel 2 XL, is there something you know about this?

I started a thread in the questions section for battery consumption, which still shows on the first page. The biggest consumers of the battery I've found are the Bluetooth/wifi radios and Tilt to Wake Sensor. That TtW Sensor was sucking down about 4% of the battery just on its own. The best configuration I've found is no wifi, no TtW sensor, no bluetooth, using LTE combined with AT&T NumberSync, from which I get approximately 24 hours. If you want to see other configurations that have been tried and reported, you can check out the other thread.

Taguiera said:
I started a thread in the questions section for battery consumption, which still shows on the first page. The biggest consumers of the battery I've found are the Bluetooth/wifi radios and Tilt to Wake Sensor. That TtW Sensor was sucking down about 4% of the battery just on its own. The best configuration I've found is no wifi, no TtW sensor, no bluetooth, using LTE combined with AT&T NumberSync, from which I get approximately 24 hours. If you want to see other configurations that have been tried and reported, you can check out the other thread.
Click to expand...
Click to collapse
I've had pretty decent battery life on my watch (depending on what it's doing in a day) but today the thing was dead in less than 7 hours and it shows it's all from Bluetooth. So, riddle me this....do I even need to be synced via Bluetooth when I have NumberSync? What are the advantages/disadvantages (besides battery drain) to leaving Bluetooth on and connected to my phone?

jeffreycpackard said:
I've had pretty decent battery life on my watch (depending on what it's doing in a day) but today the thing was dead in less than 7 hours and it shows it's all from Bluetooth. So, riddle me this....do I even need to be synced via Bluetooth when I have NumberSync? What are the advantages/disadvantages (besides battery drain) to leaving Bluetooth on and connected to my phone?
Click to expand...
Click to collapse
Sounds like something wasnt letting it sleep
Do what I do. Every 2-3 days do a restart of the watch just keeps things fresh.
Mine can easily last 2 days if stretch it. Normally I'm around 50% by the time I get home after 12 hours

Thanks for the advice! I'll start that routine tomorrow and see how it works out.

Limit Battey Charge % Android 11

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!