You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changed
Stopping or restarting the service (including OS shutdown and reboot, which it
cannot tell apart) no longer writes "no limit" to native thresholds. Linux
sysfs, Lenovo conservation mode and Intel BCLM keep the saved limit; a
temporary top-up or target is replaced by it. Gates, forced discharge, the
MagSafe light and the idle-sleep override are still always released. Before this
change every orderly stop cleared Linux thresholds, so upgrading a package
or rebooting briefly lifted the limit.
Each hardware release now has an explicit scope (daemon-held overrides or
everything). Pause and Reset release everything; Reset is acknowledged only
after the hardware accepted it and the empty policy was saved. Cleanup steps
are independent, and a failure names every step that failed.
Debian and RPM removal now starts a stopped service, runs batterybridge reset,
stops the service and checks it exited cleanly before disabling it. Failure stops
removal.
After macOS wake, status reports that hardware state is unverified until the
first reconciliation finishes. Sleep preparation steps no longer skip each other.
Shutdown refuses queued requests with an explicit error instead of dropping them
(the request is read first, and the drain is limited to five seconds).
batterybridge status labels the saved limit as configuration and prints the
device's own threshold readback separately where the driver exposes it.
The app's colors now follow the icon's greens in light and dark themes instead of blue,
and the tray icon is plain white (a black template on macOS, which the menu bar
recolors). The app icon is a horizontal battery with a limit marker.
The paused-control message lists what pause releases and that a restart ends it,
in all seven languages.
Fixed
A failed reconciliation (for example an unreadable battery percentage) no longer
writes "no limit" to a native threshold; it releases daemon-held overrides and
re-applies the saved threshold. Previously it cleared Linux and Lenovo limits until
the next successful 30-second check.
Selected items in drop-down lists keep readable text in both themes.
The app no longer silently drops an action issued while another request is
running or leaves the previous success banner in place; it shows a message.
Service troubleshooting names the correct socket group for Debian and RPM packages.
Compatibility
IPC (version 3) and the saved policy format are unchanged.
The persistence of any threshold or gate while the computer is off is unverified on every device; no hardware validation report exists. SIGKILL,
power loss and forced OS shutdown run no cleanup. See lifecycle.
Version 0.4.0 rather than a patch release: the protocol and configuration are
compatible, but observable stop and removal behavior changed.