Not sure what the exact number is. What I can say is some devices have it (mine does, obviously). You have to test and see whether the switch works on yours.
Hello! With your module you can program the load at night, so that it will charge up to 50% and after 2 or 3 hours it will charge the other 50%?Not sure what the exact number is. What I can say is some devices have it (mine does, obviously). You have to test and see whether the switch works on yours.
About over provisioning...
I believe indeed there is (at least in modern batteries); otherwise, these would last much less.
You use a terminal emulator for that. Instructions are on the README (from the OP or zip file). I always try to make everything as simple and user friendly as possible. Note that the terminal must be running (either in foreground or background) till the process is complete. I recommend Termux terminal emulator.
Sure. I can add that too.
Please provide more information about your phone (model, ROM). It works for me, but your phone may be incompatible with this app....
You should su before, e.g.
su -c cs -i
Try the attached build.Results of acc --log tail
354: eval echo '$on'
354: echo 0
355: sleep 0.5
260: shift 3
88: set +eux
And after restarting the daemon (if this is helpful)
141: set +eu
142: eval ''
143: eval ''
145: '[' -n '' ']'
214: '[' -n '' ']'
267: sleep 10
Readme > troubleshooting > custom max charging voltage and current limits reads:
Back to the combination of Custom Max Charging Voltage with a max Capacity in %.
What I think could go wrong is that over time the set maximum charging capacity becomes associated with the set voltage limit. That can possibly lead to rapid drops at the lower end.
My initial observations suggest that all the above may be the case.