Database Users

My HTC Magician freezes when cold

I have a SPV M500 for a while, and now, when it coulder outside the phone simply locks afther a while. The green led keeps blinking but a can't receive calls, if a reminder is set, it dousent react, and the only solution to revive the phone is a fost reset (or to remove the battery cover a few time). Does anyone experience this problem? Is it normal that a 15-18 C temperature to freeze these phone model? Does anyone knows a solution? I have the last BigStore ROMs installed, could it be a software prob?

That behaviour may happen in subzero, but it should never happen within the 10 degree range! Batteries tend to be the component most sensitive to the cold, so I suggest trying another battery. Or for now, try conditioning the battery to increase the chemical activity in it - this may help its resistance to the cold, in addition to possibly extending its battery life. Conditioning the battery is basically letting the battery drop to near zero with intense usage (like looping a video or heavy gaming) before charging it, charging it to full and letting it drop to zero again through intense usage - this cycle may have to repeated 2 to 3 times to get results.

WOW it must be cold where you are.

HI,
I use my XDA to do count stock in frigdes that are 0 to -16 degrees and i have had no problems?
Maybe its because im only in the fridge for a few minutes. But i count everyday and i have no problems.
I'm pointing to a software prob too. I have those 'it wont turn back on' things (hot or cold) happen and the only way to fix it is with a soft reset.
Maybe cleaning the contacts of the battery would help.

I really dont think to be a software problem, cause it's happening evena after a couple of hard resets, and with the latest original rom for the model. I tryed even to empty and recharce a couple of times the internal battery, thinking that im might need "formating" due to usure. Ive bought an extra battery of 1300mAh, but all is the same. I-ve installed a prog callet Batti, that shows the battery pover and alo the temperature of the external battery, but it shows a 2.5-2.8 C INDOORE, IN MY HAND, where it sould be around 25-28 C.
I observed that the phoone freezes when the batti shows 2.1-2.2 C (i think 21-22 C). Can someone try this program (it's free) to see what temperature its showing?
Tx

Can someone please use a temperature reading software, to see at what temperature works usualy the phone. I'm using Batti, that shows 2.4-2.6 C when it should show 24-26C. Tx.

Wrong temperature reported

Hi,
I think their is a probleme with the temperature driver.
I have seen the value go from 44°C (when cold and just start on a 22°C piece) to 28°C ( when doing heavy data download and feel the phone really warm in my hand).
Anybody have the same thing ?
PS : i use powerguard and wmwifirouter for checking the temperature

battery and crazy clock

Hi, i've the following problem: every time that i'm removing the battery from the phone when i'm restarting it the clock time is not more right.
I've to set the clock again.
Is it normal?
Have the phone a backup battery to mantein the time?
thanks

Have your HD2 get it's time from the internet. I am running a NAND Android ROM right now so I can not go through my HD2 to refresh my memory but Just go to your settings tab and keep going through your settings there and you will find option. Hint you eill have to select a sub option in one of the settings that you touch on to see the option, sorry I can not give you a step by step guide.

Hi i've already disabled the option to receive the time from internet, but i've the same problem: everey time i'm removing the battery the clock losts the right time and i've to set it again.

ekosbravo said:
Hi i've already disabled the option to receive the time from internet, but i've the same problem: everey time i'm removing the battery the clock losts the right time and i've to set it again.
Click to expand...
Click to collapse
No don't disable it, I was telling you to enable it as it will help keep you clock set to the correct time. Sorry if I was unclear.

i've done as you described and the time difference between the real time and the hd2 clock is decresead but there is yet.
Have the phone a memory battery to mantain the clock time without the main power/battery?

ekosbravo said:
i've done as you described and the time difference between the real time and the hd2 clock is decresead but there is yet.
Have the phone a memory battery to mantain the clock time without the main power/battery?
Click to expand...
Click to collapse
No the battery is the main source of power. for the HD2 unless you have it plugged into the wall charger. And even if you have it plugged into the wall charger but the battery is out you would have to bridge to of the battery pins to make it turn on.
Now how exactly the phone keeps time if you pull the battery out is a unknown to me. But lube someone else here can fell you and I in on how this works.

T-Macgnolia said:
No the battery is the main source of power. for the HD2 unless you have it plugged into the wall charger. And even if you have it plugged into the wall charger but the battery is out you would have to bridge to of the battery pins to make it turn on.
Now how exactly the phone keeps time if you pull the battery out is a unknown to me. But lube someone else here can fell you and I in on how this works.
Click to expand...
Click to collapse
I suspect there is a capacitor in line somewhere that is good for a few minutes, designed to allow one to change out the battery.
But you bring up an interesting point. Even when I power off my HD2, when I power it back on the time is correct. Of course, I have it set to get the time off the network, maybe it is doing that when it connects.

ekosbravo said:
Hi, i've the following problem: every time that i'm removing the battery from the phone when i'm restarting it the clock time is not more right.
I've to set the clock again.
Is it normal?
Have the phone a backup battery to mantein the time?
thanks
Click to expand...
Click to collapse
On the phone's mainboard is soldered a small tablet battery just as for handwatch but with leads, may be it is depleted. If You can handle a soldering iron, it's no problem to change it, else go to service.

pvii said:
On the phone's mainboard is soldered a small tablet battery just as for handwatch but with leads, may be it is depleted. If You can handle a soldering iron, it's no problem to change it, else go to service.
Click to expand...
Click to collapse
Rock on brother teach me some more.

I guess it's a lithium battery or a EDLC (Electric double-layer capacitor) like in any other digital device with on-board RTC but a very small one

yep, it's a lithium - manganese dioxide cell. The problem with those found in cellphones is that they are not quite rechargeable. Normally they aren't supposed to discharge in the typical lifetime of these devices but prolonged exposure to heat is their main enemy (they can be damaged by temperatures above 50-60 degree).
I don't remember it's exact placement, but from pvii's pictures and what i remember from disassembling my hd2.. i guess it's just underneath the CPU
Careful when soldering there, you have a multi-layered pcb and the bga matrix for the cpu on the otherside.

facdemol said:
yep, it's a lithium - manganese dioxide cell. The problem with those found in cellphones is that they are not quite rechargeable. Normally they aren't supposed to discharge in the typical lifetime of these devices but prolonged exposure to heat is their main enemy (they can be damaged by temperatures above 50-60 degree).
I don't remember it's exact placement, but from pvii's pictures and what i remember from disassembling my hd2.. i guess it's just underneath the CPU
Careful when soldering there, you have a multi-layered pcb and the bga matrix for the cpu on the otherside.
Click to expand...
Click to collapse
The behaviour of my clock is very strange because when i'm removing the main battery it does not restart from the same time every time (if i'm removing the battery from a digital clock and every time it restarts at th same time es 12:00). Each time the clock has a different time but it is not right.
Could you explain me this, please?
thanks

ekosbravo said:
The behaviour of my clock is very strange because when i'm removing the main battery it does not restart from the same time every time (if i'm removing the battery from a digital clock and every time it restarts at th same time es 12:00). Each time the clock has a different time but it is not right.
Could you explain me this, please?
thanks
Click to expand...
Click to collapse
A digital clock is a counting system. It counts pulses from a pulse generator and turn them into figures that we read as seconds, minutes, hours, days, months and years.
A simple digital clock does a hardware reset every time you replace the battery in it and starts count from default value, e.g. 12:00 or 00:00.
But a more sophisticated device as a mobile phone contains a more complicated real-time clock which is powered by two sources: an autonomous coin battery and voltage derived from main battery. Once backup battery discharged (still not 0V on it) and main battery is taken out clock may still run but with some errors in counts because clock pulse generator isn't properly powered, i.e. I take out main battery from my phone at 12:00 and put it back at 14:00. Then, if clock battery is discharged but not at 0V, my phone will show any hour between 12:00 and 14:00 but not 14:00 because of interruptions in the work of the generator. Phone's clock doesn't do a hardware reset after the main battery replacement. It will reset to default value only if backup battery is replaced i think, just as in computers.
"A real-time clock (RTC) is a computer clock (most often in the form of an integrated circuit) that keeps track of the current time. Although the term often refers to the devices in personal computers, servers and embedded systems, RTCs are present in almost any electronic device which needs to keep accurate time." ((c)Wiki http://en.wikipedia.org/wiki/Real-time_clock)

Hi, if you are right i'm realizing that my backup battery is not working or it's discharged .
My phone is 6 months old.
is it possible this case?
is it possible to see when the phone has been made?
thanks

ekosbravo said:
Hi, if you are right i'm realizing that my backup battery is not working or it's discharged .
My phone is 6 months old.
is it possible this case?
is it possible to see when the phone has been made?
thanks
Click to expand...
Click to collapse
You should ask HTC when your mainboard has been made by providing them your IMEI but I doubt they will answer... Did you bought your phone from authorized HTC dealer? It's still under warranty? Then try to change it by warranty if clock stability is so important. 6 months is too fast for lithium clock battery to discharge I think.
Edit: Date of production is printed on mainboard but you should open your phone to read it

I'm not sure if this helps, but my phone went an hour ahead everytime I restarted/removed the battery. When I went to WinMo settings>personal>phone
and disabled the time synchronization from GSM services the problem was solved.

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

Question ACC not working on 1.1.6

Did anyone solve this conundrum? Haven't had a working config file since 1.1.3. If you do, please share your config please.

I haven't had issues with Acc from the beginning. Following is an excerpt from my config;
Bash:
default_config () {
acc --daemon
acc --set --reset a
acc --set batt_status_workaround=true off_mid=true apply_on_plug=true reset_batt_stats_on_pause=true
# Specific to Nothing Phone
acc --set charging_switch="battery/charge_control_limit 0 battery/charge_control_limit_max --" force_off=true
acc --set max_temp=45 max_temp_pause=90 shutdown_temp=55 shutdown_capacity=5
acc --set pause_capacity=60 resume_capacity=55 max_charging_voltage=3900
acc --set cooldown_capacity=60 cooldown_charge=50 cooldown_pause=10 cooldown_temp=40
}
What does this do?
* Enforces 98% of the time proper shut-off at 60% battery
* Stops charging both wireless and cabled
* No issues with desynced battery status
My Samsung triple wireless charger works flawlessly. I have another unbranded (got gifted) super cheap wireless charger that makes my phone feel warm when charging is turned off.
I actually had issues, but those were AccA and scheduler related. AccA just crashes a lot, up to the point that it's only good for watching battery stats. The inbuilt scheduler didn't work how I wanted, because the CPU sleeps the Acc daemon when not charging, also Acc fails to set new charging voltage/amperages without a recent battery charge applied (the command hangs asking for attaching the charger).

BertProesmans said:
I haven't had issues with Acc from the beginning. Following is an excerpt from my config;
Bash:
default_config () {
acc --daemon
acc --set --reset a
acc --set batt_status_workaround=true off_mid=true apply_on_plug=true reset_batt_stats_on_pause=true
# Specific to Nothing Phone
acc --set charging_switch="battery/charge_control_limit 0 battery/charge_control_limit_max --" force_off=true
acc --set max_temp=45 max_temp_pause=90 shutdown_temp=55 shutdown_capacity=5
acc --set pause_capacity=60 resume_capacity=55 max_charging_voltage=3900
acc --set cooldown_capacity=60 cooldown_charge=50 cooldown_pause=10 cooldown_temp=40
}
What does this do?
* Enforces 98% of the time proper shut-off at 60% battery
* Stops charging both wireless and cabled
* No issues with desynced battery status
My Samsung triple wireless charger works flawlessly. I have another unbranded (got gifted) super cheap wireless charger that makes my phone feel warm when charging is turned off.
I actually had issues, but those were AccA and scheduler related. AccA just crashes a lot, up to the point that it's only good for watching battery stats. The inbuilt scheduler didn't work how I wanted, because the CPU sleeps the Acc daemon when not charging, also Acc fails to set new charging voltage/amperages without a recent battery charge applied (the command hangs asking for attaching the charger).
Click to expand...
Click to collapse
Would you mind sharing the whole config?

miris83 said:
Would you mind sharing the whole config?
Click to expand...
Click to collapse
CLI commands here, the important bits are functions default_config and idle_config.
nothing-phone/acc-setup.sh at d2cb377baed74b3a6f240df88df44fd29503469f · Bert-Proesmans/nothing-phone
Contribute to Bert-Proesmans/nothing-phone development by creating an account on GitHub.
github.com
Attached the daemon config, constructed from the CLI commands.
!! I use acc version 2022-7-30-DEV btw, https://github.com/VR-25/acc/releases/download/v2022.7.30-dev/acc_v2022.7.30-dev_202207300_2206.zip
I truly believe the dev is doing his best to document all things, but I got worn out trying to understand the limits of acc. So I ended up using a single configuration (till 60%) and dropped the dynamic charging profiles.
Acca profiles weren't of much help either because of crashes (i guess the same "connect charger to set charging voltage" issue). Didn't dig deeper since 2 months.

Not sure what's happening with my attachment; I cannot see it myself. Editing my post also doesn't show it.
So I'll workaround this by providing this gist link to the daemon config.
acc-default-conf.txt
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com

Sorry for the confusion.
* There were no issues with my phone using acc until I upgraded to OS version 1.5
* After upgrading to version 1.5, I had to remove my root modules (because of boot failure) and I slacked on fixing those for a while
** Meanwhile I re-assembled a config from my data above and the phone DOES NOT stop charging at 60% as configured (on version 1.5)
I'm going to find out what's wrong. Best case I might have ran some (extra) out-of-order commands.

Hi, me again!
I've ran my config (see attached) now since new years day.
EDIT; I purged everything acc related from my phone (using the uninstaller package) and started from scratch, even tested all the charging switches it could find.
I used the latest acc development version, which was 2022-7-30-DEV.
EDIT; Don't even open the AccA app before acc is installed and properly configured, because it will install the latest stable of acc and configure it without you approving. Very weird because it explicitly asks approval to install and configure but has done it anyway before you even deny the modal.
The final config didn't change from before actually. At first it seemed broken because I experimented as far until my kernel started lying about the charge/discharge rate. So my phone didn't want to stop charging above the configured threshold.
I gave up, rebooted and left it alone, battery dropped to around 40%. The next time charging (and all following times) it properly stopped charging again at 60% as per config. I'm confused but remember the same 'trick' actually happening in september.
I can't explain why my phone needs to discharge to below the charging threshold before the charging switch properly works, but it does. Probably weird driver shenanigans.
So for me it "just works".
So after 4 days, I've put my phone on a wireless charger at least 40 times. I can say it always properly stops at 60% charge. Around 10% of the times I put the phone on my samsung charger, the samsung charger gets confused and doesn't provide power. This is not misalignment (99% sure), and physically removing the phone for 10 seconds and putting it on the charger again will work normally every time.
This 10% number is certainly a regression in OS 1.5 because before I had <1% charging issues before the upgrade. In the end not that big of a deal for me though.

Don't know why attaching my text file config doesn't work ..
config.txt
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com