acc icon indicating copy to clipboard operation
acc copied to clipboard

Unexpected reboots on Samsung SM-T580 (gtaxlwifi)

Open BVollmerhaus opened this issue 3 years ago • 0 comments

OS: LineageOS 18.1 (Unofficial) ACC Version: v2022.7.30-dev Magisk Version: 25.2

Setup

I just set up a Samsung Galaxy Tab A 10.1 (2016) with a clean installation of Lineage 18.1 and installed the latest ACC version via Magisk. Right afterward, it randomly rebooted once, but I paid it no mind and configured my desired charging limits (acc 50 45). This is the only configuration change I made so far.

Issue

The charging does start and stop at the desired thresholds (45/50), but the device reboots seemingly randomly (irrespective of whether a threshold is reached or the screen being on, for example). For instance, it just now rebooted while sitting at 50 % battery with the screen off (but also does so mid-use). As far as I can see, this only happens while the device is plugged into a charger, not on battery. I'll leave it running some more to confirm this.

Running acc -t results in a reboot pretty much immediately (both with the charger plugged in or removed, although I'm aware the latter isn't supposed to be useful). I tried explicitly testing the batt_slate_mode charge switch (presumably used by default on Samsung devices?) via acc -t "battery/batt_slate_mode 0 1", which also leads to an immediate reboot. Testing the only other obvious charging switch–looking thing I could find in sysfs (acc -t "sm5703-charger/charging_enabled 1 0") does as well.

Progress

To debug this, I manually set the value of the battery/batt_slate_mode charging switch via echo 1 > /sys/class/power_supply/battery/batt_slate_mode, which successfully starts (0) and stops (1) the charging without a reboot. sm5703-charger/charging_enabled does not appear to be settable (cannot create <path>: Permission denied, even when run as root).

Considering ACC starts and stops the charging correctly, it seems as though the switch works properly. Perhaps ACC performs some other operation (such as accessing another sysfs file) which triggers a reboot? What might be the best way to debug this?

Attachments

Please see the attached output generated via acc -le right after a random reboot occurred: acc-logs-gtaxlwifi.tgz

BVollmerhaus avatar Sep 14 '22 17:09 BVollmerhaus