Skip to content

fix(power): power off at 3% instead of suspending - #669

Open
enij90 wants to merge 1 commit into
armada-os:mainfrom
enij90:pr/low-battery-poweroff
Open

enij90 wants to merge 1 commit into
armada-os:mainfrom
enij90:pr/low-battery-poweroff

Conversation

@enij90

@enij90 enij90 commented Oct 8, 2026

Copy link
Copy Markdown

With the default CriticalPowerAction=Auto and no hibernation, UPower resolves the critical action to
a suspend (GetCriticalAction returns Sleep), so at 2% the device goes to sleep and keeps draining
in s2idle until the battery is flat. On the Lenovo Legion Tab Gen 3 it then stayed dead on the
charger, with no sign of life for half an hour, until a forced reset (holding the buttons) brought it
back. This powers off at 3% instead (critical warning at 6%).

On the TB321FU port I also wake the device from s2idle with the PMIC RTC to re-check the battery
(power off at 5%, otherwise sleep again); the RTC that can wake differs per SoC, so that part stays in
the port, but I can propose a generic version if it's of interest.

AI assistance

Claude Opus 5.5, with review and on-device testing by me.

With the default CriticalPowerAction=Auto and no hibernation, UPower
suspends at 2%, and the device keeps draining in s2idle until the battery
is flat. On the Lenovo Legion Tab Gen 3 it then stayed dead on the charger,
with no sign of life for half an hour, until a forced reset (holding the
buttons) brought it back. Power off at 3% instead (critical warning at 6%).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant