456537 2022-07-10 04:30:46 +0000 Changing battery charge limit does not persist through subsequent boot (ASUS Specific) 2022-07-13 20:06:36 +0000 1 1 10 Unmaintained Powerdevil general 5.25.2 Fedora RPMs Linux RESOLVED DUPLICATE 450551 NOR normal --- 0 aisdavid9 plasma-bugs-null aisdavid9 me nate 0 oldest_to_newest 2138053 0 aisdavid9 2022-07-10 04:30:46 +0000 SUMMARY On ASUS ROG devices, changing the charge battery limit through KDE System Settings --> Advanced Power Settings, does not persist. On subsequent boot, the number goes back to the default 100% charge limit. This issue seems to be specific to only ASUS ROG laptops across different distros and perhaps maybe across DE as well. There's a popular workaround within the Zephyrus G14 community using a third-party system-level daemon (https://gitlab.com/asus-linux/asusctl). Changing the battery limit through the asusctl command line does work, I've confirmed it myself and the change does persist. However, the package is maintained by third party developers and causes unnecessary issues. STEPS TO REPRODUCE 1. Open System Settings --> Power Management --> Advanced Power Settings 2. Change the "stop charging at" number to any value between 0 - 100, input the sudo password prompt 3. Reboot OBSERVED RESULT Charge limit resets back to 100% default value. this is not a visual bug either, charging the ASUS laptop goes beyond the set threshold (e.g 80%) and up to 100% EXPECTED RESULT Charge limit should persist through GUI change, setting a 80% value should persist and stay 80% in the next boot. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Kernel Version: 5.18.10-200.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800HS with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G14 GA401IU_GA401IU System Version: 1.0 ADDITIONAL INFORMATION Please see the asusctl gitlab link as it describes this issue in further detail. A lot of ASUS linux users seems to be having this problem as well. This post can be considered as duplicate to: https://bugs.kde.org/show_bug.cgi?id=450551, but I'm reporting this issue in much further detail and with the request that a fix should be implemented within KDE itself rather than through a workaround third party package. 2138924 1 nate 2022-07-13 20:06:36 +0000 *** This bug has been marked as a duplicate of bug 450551 ***