Closed feather-47 closed 6 months ago
The Android API used for getting information of the currently running foreground app is not very reliable. I'll add a tolerance to mitigate the fluctuations.
I just notice it today but, idle mode seem to be working properly if resume_capacity
< CAPACITY
< pause_capacity
At first, it was 80 < 82 < 85, idle mode ran smoothly, battery even slowly discharged as if it wasn't emulated. Then i let it discharge to <80 and fluctuation appeared. So i set acc -s rc=
lower than the CAPACITY
then and idle mode worked smoothly again. But then, idle mode would still continue after i have closed the app, unless i unplug and replug the cable.
This also happened during the 202401190 dev build i think.
I have similar issues with my Nexus 5 device. When I ran 'acc 50 40' device is not charging. But monitoring CURRENT= showing values from -2000 to 2000 it seems charger is not turned off completely and keep maintaining battery level.
Web showing some answers:
Here are two modes available for devices: 'ac/charging_enabled' and 'battery/battery_charging_enabled' first suppose to cut power off completely and battery_charging_enabled suppose to maintain current battery charge level. Seems like some devices misbehave and using only one preferred mode. It maybe kernel issue or IC issue.
EDIT: I guess acc can detect such behaviour and report it back to the user (you can see 4mA while idle):
1/6: ac/charging_enabled 1 0
switch: off (0) current: 4mA status: Idle
switch: off (0) current: 6mA status: Idle
switch: on (1) current: 953mA status: Charging
Switch works ✅
- battIdleMode=true
Idle mode worked properly with new dev update
Phone: Galaxy Note 10 ROM: SealROMv7 I've flashed the newest .zip (202401260),
acc -i
reportSTATUS=Idle
withcharging_switch=battery/hmt_ta_charge 1 0 --
so Idle mode work. When running an app inidle_app
, i noticed that battery slowly charged up,acc -w
showed the battery to be idle for ~11s then switched to charging for also ~11s then repeat. I've only tried to address it withaccd
and rerunning the test withacc -t
andacc -ss
.acc -le
acc-logs-d1.tgz.zip