Any kernel with Battery Idle Mode/Pass through Charging

Any kernel with Battery Idle Mode/Pass through Charging - OnePlus 5 Questions & Answers

Hello!
Some time ago I found inside Advanced Charging Controller this feature called battery idle mode. When the ASUS ROG phone 3 was launched I immediately noticed the pass through charging.
Basically it is the ability to run the phone directly from the charger and stop charging the battery in certain conditions (like when the battery is hot, or it reaches 80 %). On the long run this could mean a big improvement in battery longevity, especially for people that use their phones while charging (overnight charging, in-car navi, gaming, etc.)
Sadly, this feature is kernel dependent. So I am trying to figure out if there is a kernel that supports this feature. I've tried searching around the development area, but there was nothing obvious and I didn't dig through the discussions.
Thanks!

Did you happen to find a kernel with support?

Sadly I haven't.
But I did find a different trick: set ACC to charge with 0 A (or any other very low value) and you'd basically get the same outcome (the battery will stay at the same value). Now I am not sure if this is in fact activating some trickle charging mode (and wearing the battery in the process)...

Related

Battery does not charge properly when D2 is off

Hi,
I noticed the following problem on my Diamond 2:
If I turn off the phone for night charge it never shows green in the morning.
The only way to see that amazing green light is to charge the phone whent it is turned on.
Of course I applied the latest hotfix - no use for the off mode charging. And of course I wrote to htc - will not waste your time repeating their suggestions.
And I am not happy with my phone battery life - it hardly endures one working day - lets say - 10 hours...
ROM - Official, yet.

orlean said:
Hi,
I noticed the following problem on my Diamond 2:
If I turn off the phone for night charge it never shows green in the morning.
The only way to see that amazing green light is to charge the phone whent it is turned on.
Of course I applied the latest hotfix - no use for the off mode charging. And of course I wrote to htc - will not waste your time repeating their suggestions.
And I am not happy with my phone battery life - it hardly endures one working day - lets say - 10 hours...
ROM - Official, yet.
Click to expand...
Click to collapse
I never turn my phone off so the green light problem never arises. However I will check and see if occurs.
As for battery life, you will need to give it a few weeks of use before you see maximum battery life.
Make sure you don't continually discharge the battery (better still keep it charging whenever you can) and you should see improvement over time.
Unlocking and replaceing the ROM can also have a significant effect on battery performance as does the Radio version in use. That's going to need some work on your part but the improvements are there to be had.
Some apps that are in common use are also power hungry and can cause a significant drain on power.
And if you install your apps to mem card then again that uses more power than installs to phone storage memory.
You can also turn off any unused background apps and processes.
Only turn on Bluetooth and WiFi when needed.
All these things help.
Personally I carry a spare standard battery with me at all times and strangely since I bought it I haven't needed to us it. The placebo battery effect?

Thanks for the answer.
About the battery usage conseption:
You suggest that I plug my phone each time when possible?
I thought that as the battery has XX recharges according to the specifications it is not good to charge each time whenever you got AC or USB access
I started to follow your recommendation anyway.
For example however - my laptop is never (when possible) with battery in it. I use the battery only when necessary, becasue in the user manual is written that has 300 cycles of recharging. And I always wait until completely discharged before charging. That is how I began treating the Dimond, too.

orlean said:
Thanks for the answer.
About the battery usage conseption:
You suggest that I plug my phone each time when possible?
I thought that as the battery has XX recharges according to the specifications it is not good to charge each time whenever you got AC or USB access
I started to follow your recommendation anyway.
For example however - my laptop is never (when possible) with battery in it. I use the battery only when necessary, becasue in the user manual is written that has 300 cycles of recharging. And I always wait until completely discharged before charging. That is how I began treating the Dimond, too.
Click to expand...
Click to collapse
With Lithium Ion batteries the "quoted" numbers of "rechage" is is an approximate equivalent to give some idea of life expectacy.
It's a hangover from the old NiCad battery days and is not really very helpful when applied to Lithium Ion usage.
The most important aspect of LIon is it's ability to hold it's voltge at max current for longer than other technology. It does this best when well charged and maintained at near max as possible as often as possible. The downside is it's life expectancy which does deteriorate over time.
If you require max daily useage then max charging whenever possible will give you this and you will have to accept that the battery will at some point loose it's charge retaining capabilities and will have to be replaced.
For most of us that's the most important thing.

This is not a battery issue, I believe that this is a software one.
I noticed this morning, having left my phone on charge, and 'off', all night, that the indicator light was still red. When I switched on the phone, it showed only 80% charged.
Having seen this before, I carried out a soft reset, the battery indicator then showed fully charged.
So the battery is charging fully, but the battery charge indicator is showing less than that.

Advanced battery management

Hi,
I wonder if we could have advanced battery charging management on Android in order to minimize wear. The basic idea is to avoid micro-cycles, i.e. don't start charging every time the power supply is plugged in. I find myself plugging in my Nexus several times a day, so I get several charge cycles every day. Instead, the Nexus should draw its power over USB, but not start charging.
The thinkpad_smapi module implements this for IBM/Lenovo laptops. There are two thresholds, start_charge_thresh and stop_charge_thresh. Setting the start threshold to e.g. 40 will not start charging unless the remaining capacity is below 40 %, and stop_charge_thresh will probably (I don't use it) stop charging early. I use a start threshold of 25 % on my Thinkpad, so I always have at least around 1 hour left, which is enough for me. I understand if people want a full battery all the time and rather buy a new battery every now and then. However, my first Thinkpad battery died after 1.5 years (~500 cycles). The second battery is 2 years old and still charges to 77 % of the original capacity (50 Wh of 64 Wh), so this simple measure has a significant effect.
There's a lot to know about LiPo/LiIon-batteries, way more than I know, but the bottom line is that keeping the battery between 40 % and 95 % minimizes chemical wear.
Maybe someone came across battery-related stuff while digging through the kernel sources and can comment on this. Charging is probably not handled in the kernel, but in the radio or by a dedicated circuit, but maybe there's an interface exposed to the kernel that can be used to set those threshold values. That's how it's done on Thinkpads.

Some changes to how charge management (which is done in the kernel in the ds2784_battery driver) is handled in full and near-full situations are under way. Look for them in the .32-test1 kernel sources in the near future. We're not planning on being quite as aggressive as you propose (wait until 40% to begin charging, etc), but reducing discharge/recharge cycling once the battery is full is planned.

swetland said:
Some changes to how charge management (which is done in the kernel in the ds2784_battery driver) is handled in full and near-full situations are under way. Look for them in the .32-test1 kernel sources in the near future. We're not planning on being quite as aggressive as you propose (wait until 40% to begin charging, etc), but reducing discharge/recharge cycling once the battery is full is planned.
Click to expand...
Click to collapse
i found some unusual battery behavior on the nexus one. i'll charge to 100% when on. then ill delete the batterystats.bin and power off. when off, the light is still orange. takes about a full 5 minutes later then turns green. when i do this and power on, with heavy usage it stays on 100% for 15-35 min, then slowly drops. but without doing this, it just slowly drops from 100%.

100% is not quite the same as fully charged (yes this is a little confusing). If you yank power immediately upon hitting 100% you will typically have a less full battery than if you let it sit until it stops charging. The "power off charge mode" doesn't indicate 100% with the green light -- it indicates "charge complete".
The battery log at /d/battery_log gives a bit more detail as to what's going on (as well as the chatter from the battery driver in the dmesg log).

swetland said:
100% is not quite the same as fully charged (yes this is a little confusing). If you yank power immediately upon hitting 100% you will typically have a less full battery than if you let it sit until it stops charging. The "power off charge mode" doesn't indicate 100% with the green light -- it indicates "charge complete".
The battery log at /d/battery_log gives a bit more detail as to what's going on (as well as the chatter from the battery driver in the dmesg log).
Click to expand...
Click to collapse
thanks for the response! i learned something new today

I've used the Battery University to guide me on Li-Ion batteries:
http://www.batteryuniversity.com/parttwo-34.htm
http://www.batteryuniversity.com/partone-12.htm
(scroll down on either page to see some guidelines).
The first page says that multiple partial recharges are healthier for the battery than fewer deeper discharge/recharges due to less heat buildup. Personally I have never fretted about just plugging in my Macbooks or phones whenever I wanted and the batteries have all lasted quite well.
I also use a slightly weaker charger for my G1 and N1 than the supplied chargers (500 to 700mA Blackberry chargers) and they don't get as hot when I charge them, yet charge to full capacity quickly enough for my needs. The second page recommends a 0.5C charge current (1C == 1400mAmps, 0.5C == 700mAmps) for better life.

I've been playing w the 32 test kernel and looks like this commit has implemented the battery management.
I've now noticed that if the battery level is higher than 90%, plugging in the charger will not charge the phone. Once the battery drops below 90, the battery will start getting charged.
http://r.android.com/#change,13342

is this .32 kernel going to be released as an OTA soon? or is it still in dev stages?

*push*
1.8 years later...
Is it finally implemented in Gingerbread? Are there any mods that provide a frontend to that settings?

Nexus One Battery Charging

Greetings all, I was wondering if anyone else has noticed that their battery doesn't charge to full when using the wall charger or USB? I have LiPo chargers from RC cars and I have used one to discharge and fully charge the battery to 1400mah and found that the phone seems to have much better battery life than when charged with wall charger / USB.
When charged with the external ("direct") battery charger, I can get to 4211mv whereas normally with the wall/usb it only goes to 4173mv max. From what I know of LiPo/LiIon batteries, they need to get to their max charge voltage (~4200mv) or so and stay there for some time to get full charge.
I have noticed that my phone has terrible battery life when compared to my Touch HD which used to get 20hrs+ of full use on 3G/HSDPA, same usage pattern with push e-mail and I can't even get 12hrs with the Nexus One before the battery runs right down. And I thought the Touch HD had bad battery life!
Any help / feedback would be most appreciated. Thanks!

It's interesting I see this as today has been a very odd battery day. I woke up and unplugged it at exactly 5am. For 7 minutes I checked e-mails and twitter and it had dropped 3%!!! By 8am I was down to 82% (ride in to work, listening to music for 25 mins, thats about all) I was thinking this was getting silly. It's now 5pm here and I'm still at 61%?!?! So, over the first 3 hours it went 6%ph, since then it's done 2.3%... that's the best I've ever got from it.
Could this be related? It's not really fully charged, even though it shows 100%, drops very quickly and then when it returns to where it perhaps should be (around 80%) it acts as normal?
What is a LiPo charger and how can I use one to charge my Nexus battery?

http://blog.quantifly.com/?p=2
iMAX B6 is what I have been using. I have another heavier duty one but this one is good enough for the battery. I have a generic battery charger thing which I got from China which holds the battery while the other unit charges it. Right now as I write this, my phone has been on for 1hr 25minutes after being charged with the charger, I have used the browser for 10minutes, on 3G, downloading things etc. and it is still on 4211mv and 100% charge.
Curious if this is an issue with the onboard battery microchip, or the radio/firmware. Does anyone know where to source an original replacement battery (non-generic replacement)?

The batteries in these smart phones makes no sense. The other day, I charged the phone overnight using USB, and the next day, I was at 97% after 3.5 hrs. Then, another day, with basically the same usage, I'm down to 85% after 3.5 hrs. No rhyme or reason. I wish someone could explain it.
I also wish someone could make a battery that lasts for 48 hours on normal use

"Drops very quicky"
same here but ive had this 'problems' since stock firmware. its not CM related.
I also noticed that its dropping from 100 to 80ish very fast when starting many apps in the morning for example. Like stopping airplane mode, starting some apps and opening browser. stays at 80ish for some hours then

xPatriicK said:
"Drops very quicky"
same here but ive had this 'problems' since stock firmware. its not CM related.
I also noticed that its dropping from 100 to 80ish very fast when starting many apps in the morning for example. Like stopping airplane mode, starting some apps and opening browser. stays at 80ish for some hours then
Click to expand...
Click to collapse
Yep. That was the same thing with my Pre. It would never stay at 100% for more than a few minutes, and then it would plummet into the 80's, and then it would be okay.

Battery Antics
I purposely left the phone not to charge last night from about 1AM - and I woke up (around 9:30AM) with it at 99% charge still. Used it for a bit and it dropped to 89% and now it's 1:06PM and it dropped to 75% with calls, web browsing and some other stuff. Previous days to this it would be at 75% after just 2-3 hours!
I also noticed that the phone didn't download any e-mails overnight (since there's no "scheduling" for peak/offpeak like in WM I assumed this shouldn't happen?) which may account for the minimal discharge.
All in all very strange, seems like I am not the only one with these problems - maybe I'll try get another battery and see what happens!

The thing about the battery in a smart phone is that it has a micro chip in it, and the phone reads info from it to give us the battery meter(this is true of any phone, actually)... your LiPo charger reads charge in a similar manner, only it doesn't talk with the batteries chip, instead it does it's own thing(I will spare the details)
With this in mind, what you want to do to get the most out of your battery is get the chip in the battery, and in turn the "circuit" it completes with the phone properly calibrated. To do this, you want to run the phone's battery down until it turns itself off. Do a battery pull and let it sit for a little bit (at least 30 seconds, I usually wait several minutes)... then, put the battery back in, and turn the phone on. One of two things will happen, it will either power off before fully booting, or if it does not you will want to use the phone until it powers off again.
At this point, pull the battery again and let it sit out of the phone for a bit again. Then put it back in, and without trying to power the phone on, put it on the charger and leave it on the charger until it is fully charged "green light comes on" plus a couple hours.(best to leave it on the charger overnight) At this point, take it off the charger, and then turn the phone.
This will properly set the low point and the high point for the battery stats. Do not do this a lot, it is bad for a LiIon battery to be "deep cycled", which this comes really close to doing. Ultimately, the phone is not going to charge the battery as high as a LiPo charger will, nor will it discharge it as low, because unlike an RC car's batteries that are used for rapid discharge, these batteries are designed and used in a slow long term discharge.

Thanks, I'll try that myself
Do you run any risk of damaging the battery when charging with a LiPo?

How to Make Your Cell Phone Battery Last Longer when you need it the most
Tips: How to Make Your Cell Phone Battery Last Longer when you need it the most:
1. Always try to drain your battery or wait till its 15% or below then charge your phone. Its very important to turn the phone off before you plug it to charge. This help maximizing your battery charge.
2. Stop searching for a signal. When you are in an area with poor or no signal, your phone will constantly look for a better connection, and will use up all your power doing so.
3. Switch off the vibrate function on your phone, and use just the ring tone instead.
4. Turn off your phone's back light.
5. Avoid using unnecessary features. If you know it will be a while before your phone’s next charge, don’t use the camera or connect to the Internet. Flash photography can drain your battery especially quickly.
6. Keep calls short. This is obvious, but how many times have you heard someone on their mobile phone say, "I think my battery’s dying," and then continue their conversation for several minutes? Sometimes, the dying battery is just an excuse to get off the phone (and a good one, at that), but if you really need to conserve the battery, limit your talk time.
7. Turn off Bluetooth. It will drain your battery very quickly.
8. Same goes for WIFI, GPS, and infrared capabilities, if your phone has these features built in. Keep them off; save more power.
9. Use GSM - Using your phone in 3G / Dual Mode will drain the battery quicker than if you just use GSM mode - have a look at your phones spec and you'll see it will quote two different battery life times - normally 50% more for pure GSM use.
Very Important:
Anyone purchase a new phone. Its best DO NOT USE the phone with the little remaining power the battery has. It is best that you put the battery in the phone and turn off the phone and change for minimum of 5-6 hours.
The 1st charge for the battery is very important for lithium ion battery. Leaving the phone off will give the full maximize charge the battery can take. Normal when phone shows charge complete by integrator light or on the screen means its 95% complete. To complete the 100% charge you need additional 1-2 hours after the full charge integrator show. Having the phone off also help keep the charge. A phone that is on and charging will never get that 100% charge because there is alway a little battery being drained just because the phone is one even if its plugged in to a charger.
If you see your battery is not giving the same performance what it use to. You can try this method at least 3-4 times for 1 week and follow up every other month. Meaning turn the phone off and charge it every night. It is best if you can drain the battery to 15% or less before charging the phone.

So one person says don't let it drop down low very often, the next person says let it drop to 15% all the time...
Personally I've heard not to let it drop low more often these days. The old 'let it decharge regularly' was talked about a lot 4 or 5 years ago... no?

nuc70st said:
Tips: How to Make Your Cell Phone Battery Last Longer when you need it the most:
1. Always try to drain your battery or wait till its 15% or below then charge your phone. Its very important to turn the phone off before you plug it to charge. This help maximizing your battery charge.
2. Stop searching for a signal. When you are in an area with poor or no signal, your phone will constantly look for a better connection, and will use up all your power doing so.
3. Switch off the vibrate function on your phone, and use just the ring tone instead.
4. Turn off your phone's back light.
5. Avoid using unnecessary features. If you know it will be a while before your phone’s next charge, don’t use the camera or connect to the Internet. Flash photography can drain your battery especially quickly.
6. Keep calls short. This is obvious, but how many times have you heard someone on their mobile phone say, "I think my battery’s dying," and then continue their conversation for several minutes? Sometimes, the dying battery is just an excuse to get off the phone (and a good one, at that), but if you really need to conserve the battery, limit your talk time.
7. Turn off Bluetooth. It will drain your battery very quickly.
8. Same goes for WIFI, GPS, and infrared capabilities, if your phone has these features built in. Keep them off; save more power.
9. Use GSM - Using your phone in 3G / Dual Mode will drain the battery quicker than if you just use GSM mode - have a look at your phones spec and you'll see it will quote two different battery life times - normally 50% more for pure GSM use.
Very Important:
Anyone purchase a new phone. Its best DO NOT USE the phone with the little remaining power the battery has. It is best that you put the battery in the phone and turn off the phone and change for minimum of 5-6 hours.
The 1st charge for the battery is very important for lithium ion battery. Leaving the phone off will give the full maximize charge the battery can take. Normal when phone shows charge complete by integrator light or on the screen means its 95% complete. To complete the 100% charge you need additional 1-2 hours after the full charge integrator show. Having the phone off also help keep the charge. A phone that is on and charging will never get that 100% charge because there is alway a little battery being drained just because the phone is one even if its plugged in to a charger.
If you see your battery is not giving the same performance what it use to. You can try this method at least 3-4 times for 1 week and follow up every other month. Meaning turn the phone off and charge it every night. It is best if you can drain the battery to 15% or less before charging the phone.
Click to expand...
Click to collapse
I think you didn't understand a LI-ION battery!!!
1. completely false
2. I've a mobilephone also I wan't to use it!!!
3. Maybe... Have you tested it with a ampere meter?
4. A black display is always a good idea!
5. Why not buying a Nokia 3210 ?
6. Better: Don't use it for call.
7. Correct! (If you don't use a headset)
8. See Pt. 5
9. See Pt. 5
A few facts:
- a new lithium-ion pack does not need cycling through charging and discharging
- Limit the time at which the battery stays at 4.20/cell. Prolonged high voltage promotes corrosion, especially at elevated temperatures.
- 3.92V/cell is the best upper voltage threshold for cobalt-based lithium-ion
- The 1st charge is no different to the 5th or the 50th charge. Stickers instructing to charge the battery for 8 hours or more for the first time may be a leftover from the nickel battery days.
Whole article on: batteryuniversity.com/partone-12.htm (by Cadex Electronic Inc.)

jahmann82 said:
I think you didn't understand a LI-ION battery!!!
1. completely false
2. I've a mobilephone also I wan't to use it!!!
3. Maybe... Have you tested it with a ampere meter?
4. A black display is always a good idea!
5. Why not buying a Nokia 3210 ?
6. Better: Don't use it for call.
7. Correct! (If you don't use a headset)
8. See Pt. 5
9. See Pt. 5
A few facts:
- a new lithium-ion pack does not need cycling through charging and discharging
- Limit the time at which the battery stays at 4.20/cell. Prolonged high voltage promotes corrosion, especially at elevated temperatures.
- 3.92V/cell is the best upper voltage threshold for cobalt-based lithium-ion
- The 1st charge is no different to the 5th or the 50th charge. Stickers instructing to charge the battery for 8 hours or more for the first time may be a leftover from the nickel battery days.
Whole article on: batteryuniversity.com/partone-12.htm (by Cadex Electronic Inc.)
Click to expand...
Click to collapse
I second this as well. The tips given by nuc70st is only applicable in the old days with nickel based batteries (Ni-cd and Ni-MH), which for the past 5 years mobile phones have in general stopped using and have shifted to lithium varieties. Nickel Cadium and a smaller extent Nickel Metal Hydride suffer from "memory effect" so it was important to deep cycle the batteries to maintain its capacity.
Lithium batteries in contrast should be treated in the opposite. You should keep it charged up whenever possible, and fast discharging (draining its charge as fast as possible) actually does more harm than good. Most mobile phones don't discharge it fast enough for it to be problem, but plugging a lithium battery in a purpose made discharger is still a no-no.

I dont know if anybody else can try this with their N1 but I have recently noticed that when my battery does its initial.. drop to 95% before you can wonder what happened, I can charge it with the phone on and the green light stays on, implying that the phone is fully charged.
Then I turn the phone off and charge it, and the red light quickly comes on and allows another hour? of charging before the green light will re-appear.
I think i'll be trying leaving my phone on and on charge overnight and then turning it off while I get ready in the morning and don't necessarily need it.

The green light comes on before the battery is fully charged

AndyCr15 said:
So one person says don't let it drop down low very often, the next person says let it drop to 15% all the time...
Personally I've heard not to let it drop low more often these days. The old 'let it decharge regularly' was talked about a lot 4 or 5 years ago... no?
Click to expand...
Click to collapse
I'm right and the other guy is dead wrong. Deep cycling was better for nickel metal hydride batteries, because it helped delay the memory effect.
No such issue for Li-ion batteries, plus charging makes Li-ion batteries HOT, which isn't particularly good for the battery. So numerous charges leads to less exposure to prolonged heating.

mikesm1234 said:
all very good tips
Click to expand...
Click to collapse
Oh dear. Have you read this thread?
No, they are not good tips...

Rusty! said:
The green light comes on before the battery is fully charged
Click to expand...
Click to collapse
I noticed that just last night! Are you supposed to keep charging it until its 100% or stop it from charging when the green light turns on?
Cheers,
M

Still having charging issues with 4.2.2

I'm really frustrated because i really used to love the n7 so much I was an early adopter and bought another one after I dropped my first and then went on to buy my girlfriend one. But after being plagued with this issue and stuck on 4.1 its just not the same anymore since I cant flash custom roms all day :/
I've been having a charging issue with android 4.2.1 since it came out (both stock and all the roms I tried) but I noticed that whenever I reverted to 4.1.2 the issue went away completely. So I've been waiting for 4.2.2 to come out for a while now to see if it fixed the issue and after flashing the update tonight it seems to have the same problem.
I've tried searching for months now and haven't found any answers.
So this is the issue with both 4.2.1 and 4.2.2:
The battery charges at an insanely slow pace to the point that it ruins the tablet completely. I'll plug it in over night for 8+ hours and it will not gain more then 40% battery life in that time.
Its to the point that when I was just using it right now on the charger with brightness turned all the way down and nothing on other then sync and WiFi that light web browsing for 10 mins caused it to discharge a percent after being plugged in for 19 minutes.
Notes:
Its a c70 16gb
I tried 3 different stock N7 chargers with stock cables as well as trying them with other cables.
I'm not plugged into any kind of extension cords and I've tried multiple wall sockets at different locations.
My girlfriends nexus 7 32g charges fine on 4.2.1 and I have not updated her to 4.2.2 to test yet.
I haven't checked the battery connection because like I said whenever I revert to stock 4.1.2 or any 4.1.2 rom it charges in 4 hours flat or 6 hours with heavy usage while charging.
So anyone have any ideas? If not I guess I have to rma.

Do both, yours and your girlfriend's devices take that long to charge?

sl4y3r88 said:
Do both, yours and your girlfriend's devices take that long to charge?
Click to expand...
Click to collapse
Nope her nexus 7 charges fine. ( a little slower on 4.2 then 4.1 but nothing like mine)

Her nexus does have issues with turning on sometimes on 4.2.1 like a lot of other users but its nothing holding the power button for 10 seconds doesn't fix.

It also just noticed it seems to discharge at an extremely fast pace. (still on 4.2.2)
It just dropped from 55% to 51% in the time I've typed these responses with brightness all the way down.

So anyone want to try and help me figure this out before I send it in friday? I called it in to Google play device support to try and report the software bug and they said its the first they heard of it and they would pass it on but I felt like the rep didnt want to help as I bought it from a third party. I'm willing to do any tests suggested and hop between software versions to try and figure out this bug.

Why do you think it is a "software bug" when millions of people running the "same software" don't experience the same behavior?
I realize that software can exhibit data-dependent behaviors, and thus exhibit low occurrence rates... but there is no "software" involved in charging the battery.
Do you think a booted Linux kernel is needed to charge a battery? How would the battery get charged when the device is turned off in that case? C'mon!
Send it back and tell them the battery (or charge contoller CIRCUIT) is defective.
If it's out of warranty, PAY them to replace it.

bftb0 said:
Why do you think it is a "software bug" when millions of people running the "same software" don't experience the same behavior?
I realize that software can exhibit data-dependent behaviors, and thus exhibit low occurrence rates... but there is no "software" involved in charging the battery.
Do you think a booted Linux kernel is needed to charge a battery? How would the battery get charged when the device is turned off in that case? C'mon!
Send it back and tell them the battery (or charge contoller CIRCUIT) is defective.
If it's out of warranty, PAY them to replace it.
Click to expand...
Click to collapse
Then how do you explain that if right now I flash back to 4.1.2 it will work fine? If you want I'll provide screenshots.
I just flashed back to 4.1.2 this morning and it worked perfectly. Just now I flashed codefires 4.2.2 build and the problems back.
Please explain how that is hardware related.

I may of jumped the gun assuming it was a charging issue. It seems like it might be a battery drain issue. Here's a couple screenshots from a fresh install of codefirex 4.2.2 build.
Sent from my Nexus 7 using XDA Premium HD app

All I was trying to say is that when the OS is booted, at most all it does is monitor battery voltage and current - it doesn't get actively involved in control of charging circuitry.
At most this historical data can be used to *predict* when the battery will run out of juice, and this number is what is shown to the user as a % charge number. Hopefully that allows the prediction to be sort of correct as the battery ages and it's characteristics change.
This "calibration data" is only used for prediction - it does absolutely nothing to alter the rate at which current is drawn from the battery by the motherboard, nor for attempting to alter the behavior of a battery charge controller.
Li-Ion and Li-Polymer batteries are indeed complicated enough that they should not be charged by extremely simple circuits if a long operating lifetime is desired. For this purpose though, monolithic battery charge controllers chips are used - they do not need any assistance of a micro-controller or advanced CPU running a modern OS. That's why they are able to charge batteries rapidly and appropriately when the motherboard is in a "powered down" state.
Relative to a big multi-core CPU chip, which might have hundreds of millions of transistors, battery charge controllers are extremely small circuits - they are sold by the billions and cost in the ballpark of one to several pennies. They don't need the support of a CPU or even a microcontroller to operate correctly.
Good luck with your tab; I hope you enjoy it.

bftb0 said:
All I was trying to say is that when the OS is booted, at most all it does is monitor battery voltage and current - it doesn't get actively involved in control of charging circuitry.
At most this historical data can be used to *predict* when the battery will run out of juice, and this number is what is shown to the user as a % charge number. Hopefully that allows the prediction to be sort of correct as the battery ages and it's characteristics change.
This "calibration data" is only used for prediction - it does absolutely nothing to alter the rate at which current is drawn from the battery by the motherboard, nor for attempting to alter the behavior of a battery charge controller.
Li-Ion and Li-Polymer batteries are indeed complicated enough that they should not be charged by extremely simple circuits if a long operating lifetime is desired. For this purpose though, monolithic battery charge controllers chips are used - they do not need any assistance of a micro-controller or advanced CPU running a modern OS. That's why they are able to charge batteries rapidly and appropriately when the motherboard is in a "powered down" state.
Relative to a big multi-core CPU chip, which might have hundreds of millions of transistors, battery charge controllers are extremely small circuits - they are sold by the billions and cost in the ballpark of one to several pennies. They don't need the support of a CPU or even a microcontroller to operate correctly.
Good luck with your tab; I hope you enjoy it.
Click to expand...
Click to collapse
Thank you for taking the time to write out this detailed explanation. I read it over a couple times and that all makes a lot of sense and now I have a little better understanding of how things work charging wise.
But I still can't wrap my head around how the problem DISAPPEARS COMPLETELY on any 4.1 based build...
I'm not trying to contradict you in anyway it seems like you are way more knowledgeable then me on the subject.
It just doesn't make any sense and I was hoping you could make more of it for me.
Maybe it isn't the charging but a battery drain issue something on 4.2 based builds is draining more current then the charger can dish out.
But while i was doing research I read that chargers up the current they dish out if the device is in use. Is that correct?
I've looked into the media server bug but as I just did a fresh install of stock 4.2.1 and haven't changed or added anything to the file structure that wasn't included in the factory image, I also went through and turned off the keyboard press sound and all other sounds like explained in some of the threads I have read. I also read that the problem is supposed to be fixed in 4.2.2. I also haven't installed any apps from the market.
I guess all I'm looking for is the answer to this question:
Could there really be a hardware related problem of any sort (not just charging and battery problems but anything) that causes problems with 4.2 based builds specifically but doesn't cause problems with 4.1?
If the answer is yes then I don't have to feel bad about sending it in but if its software based issues I'll be upset that I wasn't able to fix it and gave up.

Have you let the battery drain all the way or do you just plug it in at a certain point? if not let it get to the point were it will turn itself off. if the battery with the cross in it stays for more than it would take for 1% to drain then it just might be your battery stats file. even if its not let it drain and then charge it while its off. you can check the battery by pushing the power button quick. i know i have had this problem with other devices that were fixed by doing this. and my N7 did it last night were i updated and plugged it in, it was at 60% and when i woke up it was at 46%.

projectzro said:
Have you let the battery drain all the way or do you just plug it in at a certain point? if not let it get to the point were it will turn itself off. if the battery with the cross in it stays for more than it would take for 1% to drain then it just might be your battery stats file. even if its not let it drain and then charge it while its off. you can check the battery by pushing the power button quick. i know i have had this problem with other devices that were fixed by doing this. and my N7 did it last night were i updated and plugged it in, it was at 60% and when i woke up it was at 46%.
Click to expand...
Click to collapse
I'll give this a try right now then post results, the battery is already pretty low so It shouldn't take very long. Thanks for the response.

projectzro said:
Have you let the battery drain all the way or do you just plug it in at a certain point? if not let it get to the point were it will turn itself off. if the battery with the cross in it stays for more than it would take for 1% to drain then it just might be your battery stats file. even if its not let it drain and then charge it while its off. you can check the battery by pushing the power button quick. i know i have had this problem with other devices that were fixed by doing this. and my N7 did it last night were i updated and plugged it in, it was at 60% and when i woke up it was at 46%.
Click to expand...
Click to collapse
So I let it run dry and am getting some weird behavior...
The dead battery symbol did not pop at all. It actually booted played the low battery sound half way through the nexus logo loaded into the OS and immediately was greeted by the battery to low logo powering down message and then it returned off. It did this cycle all the way through three times in a row before holding the power button did nothing. I let it sit for a minute before trying again and I got another boot out of it all the way to the OS again. But I've yet to be greeted by the battery with the cross symbol. Holding the power button will do the cycle described above or do nothing at all.

krisserapin said:
But while i was doing research I read that chargers up the current they dish out if the device is in use. Is that correct?
Click to expand...
Click to collapse
Well, the 120v->5v converter certainly can be providing more current @5v because the device is active, but that's only because the motherboard is drawing current in parallel with the battery charging circuit. It doesn't mean the battery charge rate is higher.
krisserapin said:
Could there really be a hardware related problem of any sort (not just charging and battery problems but anything) that causes problems with 4.2 based builds specifically but doesn't cause problems with 4.1?
Click to expand...
Click to collapse
I suppose so.
I would do a few things to determine whether that is a reasonable hypotheses, though.
1) See how fast the battery charges with the tablet turned off. Should be close to 40%/hour for a new battery. You know there is no "software" running with the tablet turned off, so if you don't see some reasonable number here (say > 20%/hr) then a bad battery or charge controller circuit in the tab are the most likely culprits. Also, if the temperature rise of the tablet while doing this seems higher than the gf's unit, that would implicate the battery, not the charging circuit.
2) There's software, and then there's software. (Preinstalled vs. User installed) Run the battery down a ways, and then observe the battery charging rate with the device on but screen off (sleeping), but on a stock 4.2 install with ZERO user apps installed. Then, install/restore all your favorite apps, reboot, maybe use a couple of your fave apps, and repeat the same charge rate trial (screen off/sleeping). Are there large differences between the two cases? If so, that would implicate one of your apps in causing either lots of additional compute operations or preventing entry into the LP0 state (perhaps because of wakelocks?)
The thing is, the N7 battery is rated at 4325 mAh; that is sort of the same thing as 4.325 amps of current for 1 hour. (Voltage range of roughly 4v to 3.5v).
So, if a "good battery" can be charged in 2.5hrs, that is sort of like stuffing 1.73 amps into the battery for that time (1.73 x 2.5 = 4.325 A-h or 4325 mA-h). That's pretty near to the max capacity of the AC charger (2A)
Now, some users have reported discharging their tabs in 4 hours under heavy continuous use; that would be about 1.08 amps for 4 hours.
Since the wall charger is rated to produce 2A, this suggests that very heavy usage simultaneous with charging would indeed cause battery charging to slow down significantly - let's suppose it drops from 1.73a to 0.65a. Now it takes the battery 6.6hrs to charge ... but that is still just over 15%/hr ... with the tab in active use.
But that's not what you were noticing - you were seeing much worse charge rates than this when the tablet was supposed to be more or less idle!
Finally I should point out that I previously mentioned that the % charge number is a prediction, not a measurement! If for some reason this number were screwed up, then the "charge rate" observations could be completely screwed up. (Think of this as being analogous to trying to partially fill a gas tank in a car or estimate fuel mileage with a broken gas gauge) The only way to be sure that you are not falling victim to something like this is to record battery voltages - the 100% level should be up around 4v, and the 10% values down around 3.5v.
You can observe this value at /sys/devices/platform/tegra-i2c.4/i2c-4/4-0055/power_supply/battery/voltage_now
(note value is reported in uV)
Whew - long post. It doesn't directly answer your question about "why was 4.1 so different?" - but gives you an idea about why I was skeptical when you saw charging rates as low as you did.
I dunno, maybe the % charge prediction value numbers are screwy on your tab for some strange reason in 4.2, perhaps because of a minor hardware difference. I can't rule it out - I once saw a bug expression in a hardware/software combination that required three independent conditions (from three separate vendors!) to have precise configurations before the bug would show itself.
I hope this post gives you some ideas to try; it certainly doesn't give a solution.
Good luck - if you feel like spending more time investigating, go for it; just don't let the clock run out on the warranty period if you have one left.

bftb0 said:
Well, the 120v->5v converter certainly can be providing more current @5v because the device is active, but that's only because the motherboard is drawing current in parallel with the battery charging circuit. It doesn't mean the battery charge rate is higher.
I suppose so.
I would do a few things to determine whether that is a reasonable hypotheses, though.
1) See how fast the battery charges with the tablet turned off. Should be close to 40%/hour for a new battery. You know there is no "software" running with the tablet turned off, so if you don't see some reasonable number here (say > 20%/hr) then a bad battery or charge controller circuit in the tab are the most likely culprits. Also, if the temperature rise of the tablet while doing this seems higher than the gf's unit, that would implicate the battery, not the charging circuit.
2) There's software, and then there's software. (Preinstalled vs. User installed) Run the battery down a ways, and then observe the battery charging rate with the device on but screen off (sleeping), but on a stock 4.2 install with ZERO user apps installed. Then, install/restore all your favorite apps, reboot, maybe use a couple of your fave apps, and repeat the same charge rate trial (screen off/sleeping). Are there large differences between the two cases? If so, that would implicate one of your apps in causing either lots of additional compute operations or preventing entry into the LP0 state (perhaps because of wakelocks?)
The thing is, the N7 battery is rated at 4325 mAh; that is sort of the same thing as 4.325 amps of current for 1 hour. (Voltage range of roughly 4v to 3.5v).
So, if a "good battery" can be charged in 2.5hrs, that is sort of like stuffing 1.73 amps into the battery for that time (1.73 x 2.5 = 4.325 A-h or 4325 mA-h). That's pretty near to the max capacity of the AC charger (2A)
Now, some users have reported discharging their tabs in 4 hours under heavy continuous use; that would be about 1.08 amps for 4 hours.
Since the wall charger is rated to produce 2A, this suggests that very heavy usage simultaneous with charging would indeed cause battery charging to slow down significantly - let's suppose it drops from 1.73a to 0.65a. Now it takes the battery 6.6hrs to charge ... but that is still just over 15%/hr ... with the tab in active use.
But that's not what you were noticing - you were seeing much worse charge rates than this when the tablet was supposed to be more or less idle!
Finally I should point out that I previously mentioned that the % charge number is a prediction, not a measurement! If for some reason this number were screwed up, then the "charge rate" observations could be completely screwed up. (Think of this as being analogous to trying to partially fill a gas tank in a car or estimate fuel mileage with a broken gas gauge) The only way to be sure that you are not falling victim to something like this is to record battery voltages - the 100% level should be up around 4v, and the 10% values down around 3.5v.
You can observe this value at /sys/devices/platform/tegra-i2c.4/i2c-4/4-0055/power_supply/battery/voltage_now
(note value is reported in uV)
Whew - long post. It doesn't directly answer your question about "why was 4.1 so different?" - but gives you an idea about why I was skeptical when you saw charging rates as low as you did.
I dunno, maybe the % charge prediction value numbers are screwy on your tab for some strange reason in 4.2, perhaps because of a minor hardware difference. I can't rule it out - I once saw a bug expression in a hardware/software combination that required three independent conditions (from three separate vendors!) to have precise configurations before the bug would show itself.
I hope this post gives you some ideas to try; it certainly doesn't give a solution.
Good luck - if you feel like spending more time investigating, go for it; just don't let the clock run out on the warranty period if you have one left.
Click to expand...
Click to collapse
Wow thank you so much for the help. I'll play around with this tonight and see what happens. If I can't figure it out by the morning I think I'll be able to RMA it without feeling like I just rolled over and let my n7 get the best of me.

So after charging it on stock 4.2.1 with the power completely off it only charged 3% in a little over a hour and voltages read 3.6. I'm gonna leave it on the charger over night turned on starting from 3% with only two extra battery monitoring apps installed and report back in the morning with screenshots of the results. After that ill probably revert to 4.1.2 drain the battery fully, charge it off for an hour report the values then let it charge fully with the battery apps on for reference take a few more screenshots then lock the bootloader install the ota and ship it off to good old ASUS since it sounds like its hardware from whats been explained.

FWIW, I drained my N7 last night (LOL, typing novels into XDA threads) - when I finished I was at 6% charge - that was 3.66v. In the morning @ 100%, the battery voltage was 4.1-something.
Sounds to me like you've definitely got a hardware problem.
Good luck with the RMA.

Canyou help me?
Since I flashed 4.2.2 my 240V-USB charger only cahrges thes battery about 5% in one hour.
Before (with 4.2.1) It was definitely faster. It charged more tha 5% per hour (maybe 20-25%).
I double checked the plug in the socket. checked the correct fit of the USB cable on the docking station.
Everything fits tight. No wiggle.
It must be software related, since it started after flashing the OTA zip from 4.2.1 to 4.2.2

Polarfuchs said:
Canyou help me?
Since I flashed 4.2.2 my 240V-USB charger only cahrges thes battery about 5% in one hour.
Before (with 4.2.1) It was definitely faster. It charged more tha 5% per hour (maybe 20-25%).
I double checked the plug in the socket. checked the correct fit of the USB cable on the docking station.
Everything fits tight. No wiggle.
It must be software related, since it started after flashing the OTA zip from 4.2.1 to 4.2.2
Click to expand...
Click to collapse
From a partially charged state, say below 50%, turn the device off, (NOT sleeping, but powered OFF) and put it on the charger for one hour.
It should charge at around 30-40%/hr.
As I pointed out above, how is it possible that software would be affecting the charging with the device turned OFF?
I believe you are seeing exactly what you report; my best guess is that a hardware problem occurred just about coincidentally with your upgrade. Just coincidence - not causation.
You also should inspect the battery voltage (see above for path in /sys) in case something crazy is happening with the %charge *prediction* (it is not a measurement) - because the total charging range is from about 3.65v-4.15v, a normal charge rate should be roughly 150 to 200 mV/hr
good luck

[Guide]Using the Advanced Charging Controller (ACC) Magisk Module with Pixel 3a/XL

While I've had many Android phones, this is the first phone that I decided to use a battery charging controller to regulate how my battery is charged. I just wanted to share my journey with others and encourage others to try this out if you are not already.
Although there are several different battery charging controllers out there (and more than one named "ACC" which makes it even more confusing) I decided to use the Advanced Charging Controller module developed by VR25. I choose this module because I felt it provided the most customization.
Step 1 - Installation
Installing the module is easy. It is listed in the Magisk repository. Simply browse the available modules and find the one titled, "Advanced Charging Controller (acc) created by VR25 @ XDA-developers". There are several ACC modules, so make sure you install the one by VR25 to follow this thread.
Magisk will flash the module and start it automatically. You don't even need to reboot, although it is the only way to clear the Magisk notification that the module will be started at the next reboot.
Step 2 - Changing the Charging Switch Setting
I found that the default charging switch setting (auto) does not work reliably with our phones. Therefore I would suggest changing it using the commands below. Personally I have choose option 2 (battery/charge_disable 0 1) but I listed all the options with the quirks that I have found with each one.
Step 2.1 - open your preferred command line app - I use Terminal Emulator.
Step 2.2 - type "su" and hit enter to gain root
Step 2.3 - type "acc -s s" and hit enter - this is the command that allows us to select another charging switch
Step 2.4 - type what number of the charging switch you want to use.
Here are the available charging switches and the issues I have found with them:
1) Automatic - this switch tries to cycle through the available switches until if find one that "works".
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: No - I found that the phone would charge anytime it was plugged in and below the Pause threshold. It did not seem to wait until the battery level was below the Resume threshold.
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:
2) battery/charge_disable 0 1 :
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:3) battery/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): No - phone begins discharging from battery when Pause threshold is reached but the phone is still plugged in
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: No - may show charging icon when phone is really discharging, especially during cooldownratio times and the chime doesn't always ring when charging resumes.
- Suffers from wakelock issues when phone is plugged in but not charging: No
- Other issues: The phone seems to follow the cooldown charge/discharge times even before reaching the cooldown threshold. I find the phone pausing for 10 seconds (my cool down ratio) when the batter level might be a 50% - long before the 60% cooldown threshold I have set in the config file.4) dc/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:5) battery/charge_control_limit 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:
Step 3 - Configuration
You can configure the ACC controller using a couple of different methods. You can do everything using command lines, you can use the beta ACC app (see note below), or you can edit a config file that ACC creates when it is installed. Personally I found that editing the config file was the quickest and easiest method to make general changes.
The ACC config file is found at /storage/emulated/0/acc The file is named "config.txt" You can open the file with a text editor. I personally use the app Root Explorer. I long click on the file name, and then press the three dot button in the upper right hand corner. Choose "Open in Text Editor" and the config file will open and allow changes to be made. Saving the file will automatically push the changes to ACC, you do not need to reboot or restart the ACC daemon for changes to take effect.
I won't go into a lot of detail about all of the different configuration options here as the developer's xda thread is the best place to get that type of information. But I will talk about the most basic setting - the "capacity" setting. It is the second setting listed in the config file and it should look something like "capacity=0, 60, 70-80". Here is a break down of what those numbers mean:
- The First Number (0): is battery level were the phone will shut off. The default setting of 0 means the phone will turn off when the battery level hits 0. Personally I don't want my battery completely draining, so I have it set at 5.
- The Second Number (60): is the battery level where the module starts it's "cool down" functionality. Cool down (listed as coolDownRatio in the config file) is where the phone will stop charging briefly and then restart charging. The default "cool down" setting is coolDownRatio=50/10 which means the phone will charge for 50 seconds, and then stop charging for 10 seconds before charging again for 50 seconds, etc, etc, etc. This is designed to keep the battery temps low. A battery with a charge level less than this number (60 in this example) will charge without pausing, but when the battery level gets to this number or above, the phone will charge and pause based on the coolDownRatio.
- The Third Number (70): is the "resume" value. If the phone's battery level is below this resume value, the phone will charge. If the battery level is at or above this resume value, the phone will not charge even while plugged in.
- The Fourth Number (80): is the "pause" value. This is the battery level where the phone will stop charging and should not charge above this value.
The default settings are set this way because research has shown that a phone's battery will last the longest with the least amount of battery capacity loss if it is charged to a max of 80% of the battery's capacity, and allowed to discharge just a small amount (10%) before being charged again. I realize this goes against the old "wives tale" that our phone's batteries have a very limited number of charges and it is best to limit the number of charges by only charging the phone when it gets to a low level. This is not true in actual battery performance however and if you charge like this, you are actually decreasing your battery's life expectancy and performance.
Obviously the default settings may not be the best setting for you. The default settings are probably only practical for a device that is plugged in 100% of the time. Personally I have changed my capacity setting to capacity=5, 60, 70-90. This means my phone will turn off when the battery level reaches 5% (something it has never dropped to yet), it is charged to a max of 90% and will discharge to 70% before charging again, and the cooldown charging cycling starts when the battery is 60% or higher. Obviously I'm not on my charger all the time, so it is very common for my battery to drop below 70%. However, if the battery is below 70% and I have a charger at my disposal, I am going to charge the phone back to 90% rather than let it the battery levels continue to fall.
Final Notes and Misc Thoughts
There are lots of other options and commands you can use in ACC. Feel free to share any changes you like to make, or post if you are having problems getting the module to work as expected on the 3a. I hope this helps some people feel give the module a try.
There is an ACC app that is available now that allows you to control some of the settings from a nice GUI. I personally did not like using it as I found it would overwrite settings in the config file that I was not intending to be changed.
There is an ACC telegram group if you want to join and have direct communication with the developer and others.
Thanks to @jellopuddingstick for educating me on what the battery idle mode does and why it is beneficial to have it working!

if you want to extend your batteries life, one of the best ways is to not fast charge it. fast charging not only degrades it a bit faster because of the amount of current, but it also tends to heat the battery up more which makes it degrade even faster too. heat is the main reason i tell people not to use wireless charging.

pbanj said:
if you want to extend your batteries life, one of the best ways is to not fast charge it. fast charging not only degrades it a bit faster because of the amount of current, but it also tends to heat the battery up more which makes it degrade even faster too. heat is the main reason i tell people not to use wireless charging.
Click to expand...
Click to collapse
This is why I always use a low current charger unless I absolutely need a quick charge. I have used the Dash charger that came with my OnePlus 5 only about 10 times in 2 years.

As I use my phone more, I realize that none of the charging switches seem to work 100% of the time as expected. I'll continue to do trial and error tests, but please share if you find a switch that works consistently.

sic0048 said:
As I use my phone more, I realize that none of the charging switches seem to work 100% of the time as expected. I'll continue to do trial and error tests, but please share if you find a switch that works consistently.
Click to expand...
Click to collapse
I was having issues with ACC not working before installing the apk. I'll report back if I have any issues.
Nice guide BTW.

I've continued to edit my original post to provide as much information about the different charging switches and the issues I see with each one. Hopefully it is easy to understand.
I still find myself defaulting to the 3rd charging switch option and while it can act a little erratic sometimes, it does work normally most of the time.

I'm just curious if anyone has tried the "auto" charging switch in the latest ACC version? According to the release notes, there was some changes made to the auto system as it may not have been working correctly.
I'll try it here in a little while, but thought I would ask.

sic0048 said:
I'm just curious if anyone has tried the "auto" charging switch in the latest ACC version? According to the release notes, there was some changes made to the auto system as it may not have been working correctly.
I'll try it here in a little while, but thought I would ask.
Click to expand...
Click to collapse
I've been using the apk auto switch, no issues.

Is this working for anyone:
usb/current_max:500000
I have is set in the app as an On plugged option and It is not working for me.

gargleblarg said:
I've been using the apk auto switch, no issues.
Click to expand...
Click to collapse
The phone discharges at the pause threshold and not simply hold the charge at the threshold percentage?
I found the auto setting showed the same tendencies as switch 2 - not discharging below the pause threshold. But I haven't tried it with the new release which specifically mentioned the auto setting bring changed.

sic0048 said:
The phone discharges at the pause threshold and not simply hold the charge at the threshold percentage?
I found the auto setting showed the same tendencies as switch 2 - not discharging below the pause threshold. But I haven't tried it with the new release which specifically mentioned the auto setting bring changed.
Click to expand...
Click to collapse
I'm on 2019.6.14-r1 version.
I charged up to 80% and kept it plugged in to see if it would drop or maintain, it dropped. It took forever.
Edit: 8 hours later and it has only dropped to 78%
@creeve4, I can't get the On Plugged options to work either. I tried "./usb/current_max:500000" and "usb/current_max:500000", I tried unplugging/plugging in the charger, resetting the daemon, still no luck. The settings were saved to the config file correctly. No idea.

gargleblarg said:
I'm on 2019.6.14-r1 version.
I charged up to 80% and kept it plugged in to see if it would drop or maintain, it dropped. It took forever.
Edit: 8 hours later and it has only dropped to 78%
Click to expand...
Click to collapse
Interesting. That's unfortunately not what I experience.
I just tried the auto setting and plugged my phone in and it immediately went into what I am calling a "maintenance charge". It was only charging the phone by about 200 mA. I set the charging switch back to #3, unplugged and replugged in the phone and it is charging at about 1200mA which a pretty normal charging current for me.
It's this same roughly 200mA charge that I have seen previously with the auto setting after the phone reaches the set pause threshold - so the phone charges at normal current levels and then drops to the 200mA current after reaching the pause threshold. Admittedly, I did not allow the phone to reach the pause threshold this time (which would take forever at 200mA), but seeing that charging level at all leads me to believe that the auto charging switch is still not working for me (it should either be fully charging or full discharging). I suspect because the phone was above the resume threshold it defaulted to this maintenance charge (thinking the phone shouldn't be fully charged until it dropped below the resume threshold).

sic0048 said:
Interesting. That's unfortunately not what I experience.
Click to expand...
Click to collapse
What was the battery level when you plugged it in?

sic0048 said:
Interesting. That's unfortunately not what I experience.
Click to expand...
Click to collapse
That is interesting, have you tried updating yet?
I should also mention that I have only changed the percentage to 3% for the phone to shut off, the rest of the options are default.

Is anyone else getting the following message in the acc app after updating to the latest version?

creeve4 said:
Is anyone else getting the following message in the acc app after updating to the latest version?
Click to expand...
Click to collapse
I'm not using the app, so I can't answer your question. I was hoping someone else might chime in if they are using the app.

sic0048 said:
I'm not using the app, so I can't answer your question. I was hoping someone else might chime in if they are using the app.
Click to expand...
Click to collapse
I just needed to update to the latest app version. The module was updated before the app.

Did anyone else lose their config settings when updating the ACC module recently? I updated a day or two ago and woke up to my phone at 100% charge. I started troubleshooting and found that the config file was set to all the default settings. This means the charging switch was set to "auto" which has never worked for me and it explains why the module didn't pause the charging at the default pause setting (80%).
The release notes talked about a lot of changes in the config file, but it never mentioned that users would lose their settings and be reset to default. I was just curious if anyone else experienced the same thing or not.

There's a bit of misinformation / misunderstanding going on here, I think. The best control file for our devices is battery/charge_disable. The "maintenance charge" (ACC refers to it as "idle mode") you're referring to is a good thing! This is explained both in the ACC readme [1] and by the developer of Battery Charge Limit [2][3]. The ping-ponging between the upper and lower thresholds is a fallback, it's not the desired mechanism. Hope this clears things up!
[1] "Charging switches that support battery idle mode take precedence", https://github.com/VR-25/acc/blob/master/README.md
[2] https://forum.xda-developers.com/showpost.php?p=76523599&postcount=1834
[3] https://android.stackexchange.com/a/200037

umm, i would be happy if someone give an advice to me the best configuration for the best battery charging cycle, anyone can help me?

Database Users

welcome