Power & Battery Care

Linxira OS ships power-profiles-daemon, driven by the KDE Plasma power panel. tlp is not installed — do not stack two governors.

Check current state

linxira-config power status
powerprofilesctl get
powerprofilesctl list

Write actions under linxira-config power (suspend/hibernate policy changes) are disabled pending the transactional backend; use System Settings → Power Management instead.

Which profile

ProfileUseCost
power-saverTravel, writing, terminal workNoticeably slower builds
balancedDaily defaultNone
performanceCompiles, benchmarks, long jobs on ACFan noise, half the battery life
powerprofilesctl set power-saver

Battery health

Whether you can cap charging depends on firmware exposure:

ls /sys/class/power_supply/BAT*/charge_control_end_threshold

If the file exists (root required):

echo 80 | sudo tee /sys/class/power_supply/BAT0/charge_control_end_threshold

Most firmware keeps the value across reboots; if not, persist it with a udev rule.

If the machine does not support it

Do not force it. A missing charge_control_end_threshold means the firmware does not expose it:

Two correct options only:

  1. Look in BIOS / vendor tools. Many Lenovo, ASUS, and Dell machines expose a battery-care or charge-limit setting in firmware. That implementation is vendor-supported and safe.
  2. If there is none, manage behaviour instead: keep the charge between 40–80% when on AC for long periods, avoid all-night full charge at high temperature. Heat damages cells more than state of charge does — fix cooling first.

One command tells you whether it is supported:

ls /sys/class/power_supply/BAT*/charge_control_end_threshold 2>/dev/null || echo "unsupported — leave it alone"

What is draining the battery

upower -i "$(upower -e | grep BAT)"

Hibernate

Requires swap ≥ RAM:

swapon --show
free -h

Test manually with systemctl hibernate before making it the default.