On charge but battery draining? - Touch HD General

I have touch HD, stock rom. The past few days I have put my HD on charge, LED light is red to show charging but battery indicator actually shows it has lost power after an hours charge. Any ideas??
Phil G, South Wales

Hi Phil,
how is battery usage while using the phone, does it drain quite quickly at all?
Im just thinking that it could be a hardware fault with your battery.
Please try the following:
(1) Charge the battery to 100%.
(2) Disable from running or uninstall any 3rd party applications.
(3) Disable Bluetooth and Wi-Fi,
(4) Enable flight mode
(5) Set backlight to maximum settings.
(6) In the power management settings, uncheck any option that would set the backlight to turn off.
(7) Let phone stay idle for 1 hour and check battery capacity.
(8) If there is a loss of 40% or more, then this means that battery is faulty and needs to be replaced.
Regards.

Related

Power Button and Data Retention BiG Problems

Hi All,
I have such a big Power issue with the Magician, or at least Orange's M500 version of it that i'm thinking of taking back the device :'(
It doesn't appear to be a device fault, but a design fault.
In the manual it says that if you press the power button for a short time (less than a second) it turns the PDA on and off. This seems to be correct.
In the manual it says that if you press and hold the power button for two seconds it turns the phone off, but this doesn't work. Instead it turns on and off the back light. If the PDA is on, it turns on and off the back light. If the PDA is off it turns it on with the backlight on.
Last night I turned my PDA into standby mode (As i can't turn the phone off) before going to bed. Around 3am in the morning my PDA woke up saying that the battery power was low. I turned the PDA back into standby mode but it complained later on that night. i.e. had a bad nights sleep last night.
I thought it best to remove the main battery so that it wouldn't continue to wake me up, making sure that the phone and PDA were turned off (no power) and let the data backup battery retain the data until i woke up (5 hours time). However, when i woke up the internal data backup batery was flat. It was fully charged before the i took the main battery out. It is supposed to last 72 hours right!!!!? What a nightmare!
I was wondering if anyone could help me answer these power related questions, as i love the device, but its useless if it won't retain the data when it says it should.
How do you turn the phone off so that nothing is running at all? (i.e. to make sure that the internal battery is only being used to retain my data)
Does activating bluetooth drain the main battery faster even when the PDA is in standby mode? (I think i may have left it switched on last night)
Why would the internal data retention battery drain flat in under 5 hours when the main battery is removed loosing all data? Does it need the main battery in place in order to work? Could the phone and the PDA in standby mode by running off of the internal power?
Thanks in advance to any help you can give. As you can imagine i'm very disappointed as i love the functionality of this device.
Neil
When you took the battery out and left it out, if you had slid the back down (this is the same as a power off) you would of been ok.
The action of sliding the back down and back up is equvalent to a power off. When you press the power button after this, it is like a cold boot. (Not a hard reset)
I hope that made sense.
So to power off the phone and PDA you have to slide off the battery cover and slide it back on again without taking the battery out. Surely there is an easier way to turn off the phone and PDA that to remove the battery cover?
Thats how i do it. I'm sure there is a different [proper] way, but i'm not sure what it is.
Hi
The main battery when flat enough to power off the pda should have 72 hours data retention, its designed that way... so if it goes flat on friday you will still have your data on monday. thats why it was designed that way and apparently it shuts of at 50% capacity.
Bluetooth active will drain more power.
the backup battery is only supposed to last around 20 mins or less, designed so you can take the main battery out without losing data. this is because Ram needs constant voltage to store contents. hence if you leave your main battery out for more time the backup battery has charge you will end up with a hard reset occuring.
The manual needs to be updated i guess. If you want to turn off the phone you can turn on flight mode which disables the GSM radio functions.
Oh and out of interest for the battery type Li ion, its actually better to keep them charged, they dont have cycles like older batteries. they only have a certain lifespan which starts from the date of manufactor and keeping them at low charge degrades them faster.
Enjoy
SpeedN
So up until the 50% point, pressing the power button just puts the PDA in standby and the Phone is still running. Only when the power goes below 50% ish does the PDA power off completely?
So after the phone is fully charged, the M500 battery life meter says there is 6 hours and 31 minutes of battery life in it. You say that the device will turn itself off at 50% battery life remaining, so that means it only has 3h 15m of useable time before it switches off? Can the phone / PDA be used when power gets below 50% or will it just not power up until its recharged?
Thanks for your help BTW very useful information.
Neil
The battery life meter will say eg 6h 31m, the device will turn off in 6h 31m give or take (usage dependant).
when the device is flat there will be still 50% capacity in the battery to allow for the 72 hours data retention. hope thats clearer.
when it is in that state it wont turn on I think...sorry been along time since i been in that state, untill you charge it.
SpeedN
Surely the easiest way to solve this (and yes I was fooled by the manuals answer to press and hold) is to enable flight mode(which turns the phone off) then turn off ? there are a few apps/ shortcuts that will switch to flight mode easily, you then simply press the off button.
Or did I miss something
I think when we push the power off button (or if we select the machine to be powered off after a period of idle time, through setting), the machine will be off except GSM functions. So when you turn on again, it takes a few seconds to make the machine runs.
You can try if you turn off the button, after few minutes (should be more than 180 seconds), then push the Green button to dial, it takes 3-5 seconds to make the dialing pad comes out.
If you do not select the machine to be power off after a period of idle time, you can use other software to "screen off" the machine, so that when you push green button to dial, it comes out very quickly.
If you turn off the GMS, and turn off the PDA, it will not really get into sleep but will be in the state of retention of data. In any case, when you wake up the machine it takes a few seconds.
Therefore, when you are on the run (say on the street) and make calls frequently, do not power off the machine so that you can make calls quickly.
That is only my experience, I have checked other HP and XDA phones, same results. So nothing to do with the speed CPU and size internal ram.
When the machine is ON, I under clock to 208, the dialing pad also comes out very quickly.
flight mode = on , thats all, it turns the gsm function off, so battery would last long.

Another clue to battery and shutdown problem

It seems I have the same prob with the mda pro shutting down at a set battery level.
I followed the recommendations on the other threads:
<quote>
1. Fully charge the device with the "wall charger" not USB.
2. Put device into bootloader mode (backlight+power+reset) and run until device goes dead.
3. Charge the device completely with the “wall charger” not USB again.
4. Set screen brightness to MAX and turn off ALL power saving features.
5. Unplug the device from charger and run until completely dead again.
6. Repeat step 3, then restore custom screen brightness and power saving features.
7. Finished.</quote>
I did the drain method above about 5 times, and let it charge up for about 12+ hours each time to full.
I also flashed back to official T-Mobile UK Rom and this didn't make much difference.
Now my battery drains normally if the MDA pro is left idle- it goes from 100% all the way until 30%.
But as soon as I use a battery intensive task, such as connect to the internet, put the screen brightness up to full... it again just shuts down as before.
The only thing i haven't tried is getting a new battery... then I'm calling T-Mobile to get it replaced.
Just thought I'd add a clue to help solve this weird problem.
I had a similar problem with my jasjar - only thing that helped was a new battery. I'm not more cautious of ensuring I fully drain the battery regularly, and it seems to be working well...

Turning on phone while charging

Hello all,
Recently i've been noticing that my GS4 battery is draining too fast, i think that it's time to recalibrate it. Since my phone is not rooted, i have searched for guides on how to recalibrate the battery.. and i found this one:
To calibrate your Android phone battery correctly:
1-First drain your battery down. Let the device switch itself off naturally. You will know if it is completely dead because it won’t switch on again.
2-Place the phone ion charge while it is turned off. Allow it to charge for at the very least 2 hours, if not 4, until the battery meter reads 100%
3-Switch on the phone while the charge is still connected to it. When your phone is on the home screen, leave the charger connected for a further 2 minutes before removing it.
4-Repeat the above steps twice more, always allowing the phone to completely discharge first.
The reason for leaving your charger connected is to allow the configuration files to update with the new, correct charge values. Some of the best ways to avoid battery usage is to make sure all connections are turned off when they are not in use – Wi-Fi, Bluetooth, GPS etc. Make sure your screen locks down in under a minute when not in use and that your screen is not set too bright
My question is.. is it safe to turn on the phone while it is charging? is it safe to turn on the phone when it is plugged to a charger while it is off?
Thank you in advance.
Gab! said:
Hello all,
Recently i've been noticing that my GS4 battery is draining too fast, i think that it's time to recalibrate it. Since my phone is not rooted, i have searched for guides on how to recalibrate the battery.. and i found this one:
To calibrate your Android phone battery correctly:
1-First drain your battery down. Let the device switch itself off naturally. You will know if it is completely dead because it won’t switch on again.
2-Place the phone ion charge while it is turned off. Allow it to charge for at the very least 2 hours, if not 4, until the battery meter reads 100%
3-Switch on the phone while the charge is still connected to it. When your phone is on the home screen, leave the charger connected for a further 2 minutes before removing it.
4-Repeat the above steps twice more, always allowing the phone to completely discharge first.
The reason for leaving your charger connected is to allow the configuration files to update with the new, correct charge values. Some of the best ways to avoid battery usage is to make sure all connections are turned off when they are not in use – Wi-Fi, Bluetooth, GPS etc. Make sure your screen locks down in under a minute when not in use and that your screen is not set too bright
My question is.. is it safe to turn on the phone while it is charging? is it safe to turn on the phone when it is plugged to a charger while it is off?
Thank you in advance.
Click to expand...
Click to collapse
Hi
Yes and yes
BTW I do not believe to much in those battery calibration methods , as far as i know a new file is generated each time you switch off and back on
You can charge your phone in any status, on, off, flight mode, playing games etc.It will only affect your charging speed.
As for calibration - I have heard about such thing and try to discharge my battery till some 1-3% and full charge at least once a month. Don't know if this helps. I think also important is the environment temperature and how you discharge the last percent.My suggestion is that last percent must be discharged as slow as possible - with screen locked let it die natural way, with normal usage, very slowly. I and other usually switch all possible things to drain battery faster at this stage. That seems wrong on my personal opinion.
Gab! said:
Hello all,
Recently i've been noticing that my GS4 battery is draining too fast, i think that it's time to recalibrate it. Since my phone is not rooted, i have searched for guides on how to recalibrate the battery.. and i found this one:
To calibrate your Android phone battery correctly:
1-First drain your battery down. Let the device switch itself off naturally. You will know if it is completely dead because it won’t switch on again.
2-Place the phone ion charge while it is turned off. Allow it to charge for at the very least 2 hours, if not 4, until the battery meter reads 100%
3-Switch on the phone while the charge is still connected to it. When your phone is on the home screen, leave the charger connected for a further 2 minutes before removing it.
4-Repeat the above steps twice more, always allowing the phone to completely discharge first.
The reason for leaving your charger connected is to allow the configuration files to update with the new, correct charge values. Some of the best ways to avoid battery usage is to make sure all connections are turned off when they are not in use – Wi-Fi, Bluetooth, GPS etc. Make sure your screen locks down in under a minute when not in use and that your screen is not set too bright
My question is.. is it safe to turn on the phone while it is charging? is it safe to turn on the phone when it is plugged to a charger while it is off?
Thank you in advance.
Click to expand...
Click to collapse
NO NO NO
Draining your battery is BAD!!! Draining it below 0 is the dumbest thing you can do. That damages your battery. Whoever made that "guide" has absolutely no understanding about his battery.
Calibrating is easy.
Charge to 100%. Pull your battery. Put battery back in. Charge again until full when powered off. Volia calibrated.
Though it will probably not help. My guess is that you just need a new battery (if it's no software problem).

Try This If You're Having Battery Drain/Slow Mobile Network Issues

Was having trouble with both issues, pulled battery with phone on, waited a minute, put battery back in, both problems fixed!
isnt this bad for the phone? Im having horrible battery life so I'll try anything but just wanna make sure
zorian said:
isnt this bad for the phone? Im having horrible battery life so I'll try anything but just wanna make sure
Click to expand...
Click to collapse
You wouldn't want do it if on a regular basis but you can try turning phone off, pulling battery out, putting it back in after a minute and if that doesn't work, try my method.
I would wait until the battery is super low and then reset network settings under the reset menu. Power down, pull battery and sim wait 30 sec to a minute and replace everything. Then plug in the phone first and then reboot. Let it charge completely and for about 20 minutes more after it reaches 100. If you do a lot of rebooting I have found the phone has issues. I only reboot with the phone plugged in, otherwise it drops 2% every reboot..
Be careful, I did that with a ZTE Zmax 2 once (75% charged battery) and it sent a phone into a bootloop. The only means of fixing it was that I luckily had a 2nd Zmax2 laying around and used its battery on the bootlooped phone which remedied the problem. Both batteries work fine , I just swapped them between the two phones.
zorian said:
isnt this bad for the phone? Im having horrible battery life so I'll try anything but just wanna make sure
Click to expand...
Click to collapse
I used to worry about this too. This is my first LG product and it MAY be different but at the Sprint store the first thing they would normally do is pull the nattery to look at the ESN. They never bothered to power it doen forst so I asked a couple times and was told it will mot hurt anything. I had Samsung products for uears and have done battery pulls at all levels of charge and for many reasons, but I never had a problem as long as the battery had enough juice left to boot the phone. If not I had to charge it, LoL.
Just thought I would share, I personally wouldn't worry.
I know on my old Nexus 6 pulling the battery with phone on was only an issue with fsync disabled using a custom kernel. I think most phones have built in protection to stop this from damaging the file system.
so a battery pull is your fix? lol some ppl should be hard resetting every so often regardlessi reboot at least once a day
hi
my v20 phone battery draining was about 1% per hour before (about 7% totally ) and recently increased to 2% during sleeping time overnight. (draining 15% overnight in sleeping state)
it seems that during day either performance off battery is decreased.(about 5h with wifi and screen on usage)
Fast charging while second screen is On , is slower than when it is off therefore when second screen is Off , fast charging goes better . exactly , first 30 mins fast charging makes about 40% battery charge(instead of 50%) and after 60 min leads to 85% and full charging taking place after about 100 min instead of 80 mins.
another important thing is that sometimes shades have been seen on the LCD that many users have complained about it.
phone information is :
Android security patch level: September 1, 2017
BASEBAND : MPSS.TH.2.0.1.c3-00045-M8996FAAAANAZM-1
KERNEL : 3.18.31
BUILD NUMBER : NRD90M
SOFTWARE VERSION : V10g-AME-XX
MODEL NUMBER : LG-H990ds
my actions are as follows :
phone is factory reseted. No third party apps is installed. [especially social media apps.]
battery calibration steps for not rooted phones is taken place.(turning off the phone and charging several times repeatedly).
testing battery drain in safe mode in done and didn't change results
turn off location services and location scanning for WiFi and Bluetooth scanning
turn off WiFi being On during screen is Off.
turn off auto sync, NFC, GPS etc.
not using auto brightness.
not using comfort view .
turn off location services and location scanning for WiFi and Bluetooth scanning
second screen is off during test overnight. (either with second screen is ON with faced down to lower brightness in other day test )
phone is in Air Plane Mode and all data services is off.
system apps like Google services and Play and Assistance is limited by permissions.
following are some advanced battery drain overnight figures of my phone for more analyzing.
any help with this issue is appreciated.
While I don't get extremely bad battery drain. The few times I've noticed it going down a bit faster than normal have had Android system at the top of the list or at least 2nd in place. A reboot usually fixes it for a while. This has happened in every ROM I've tried. Also I swear that stupid Wi-Fi scanning when WiFi is off option in locations settings turns itself on when it feels like it. I rarely turn my location on and I've checked a few times and that feature is on for whatever reason
Power down.
Pull battery.
Hold power button for one minute to discharge any juice that may be on the motherboard.
Let phone sit for 30 minutes.
Put battery back in.
Power up.
The motherboard and battery should now be re-calibrated. If you still have problems, try a new battery.

[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?

Categories

Resources