Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
[feature request] Limit battery charging level to reduce wear
Reported by moWerk · filed Oct 31, 2025Closed upstream on 2026-02-02. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
What do you need?
Coming from KDE, i miss a config feature to limit the battery charging to a user defined level.
On devices with support for the kernel feature, charge_control_end_threshold and charge_control_start_threshold are available in /sys/class/power_supply/BAT0/
I tested to manually echo values to the Sysfs files and had success after setting charge_behaviour to auto.
For myself i made a quick and dirty service that writes the values after boot, suspend and sleep.
[Unit]
Description=Set battery charge thresholds
After=multi-user.target suspend.target hybrid-sleep.target
[Service]
Type=oneshot
ExecStart=/bin/sh -c "echo auto > /sys/class/power_supply/BAT0/charge_behaviour; echo 75 > /sys/class/power_supply/BAT0/charge_control_start_threshold; echo 80 > /sys/class/power_supply/BAT0/charge_control_end_threshold"
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target suspend.target hybrid-sleep.targetI made an attempt to cleanly add the feature to omarchy setup next to the power profile settings and make it depend on hardware availability but failed. I used battery-monitor as an implementation example for the service and menu entry and now face the issue that i got a user service running but my script needs to write to Sysfs as root.
This is how far i got in case someone is interested in either giving me hints on how to continue or pick up the work.
https://github.com/basecamp/omarchy/compare/master...moWerk:omarchy:feature/battery-thresholds-configurable
View raw text
### What do you need? Coming from KDE, i miss a config feature to limit the battery charging to a user defined level. On devices with support for the kernel feature, `charge_control_end_threshold` and `charge_control_start_threshold ` are available in `/sys/class/power_supply/BAT0/` I tested to manually echo values to the Sysfs files and had success after setting `charge_behaviour` to `auto`. For myself i made a quick and dirty service that writes the values after boot, suspend and sleep. ``` [Unit] Description=Set battery charge thresholds After=multi-user.target suspend.target hybrid-sleep.target [Service] Type=oneshot ExecStart=/bin/sh -c "echo auto > /sys/class/power_supply/BAT0/charge_behaviour; echo 75 > /sys/class/power_supply/BAT0/charge_control_start_threshold; echo 80 > /sys/class/power_supply/BAT0/charge_control_end_threshold" RemainAfterExit=yes [Install] WantedBy=multi-user.target suspend.target hybrid-sleep.target ``` I made an attempt to cleanly add the feature to omarchy setup next to the power profile settings and make it depend on hardware availability but failed. I used battery-monitor as an implementation example for the service and menu entry and now face the issue that i got a user service running but my script needs to write to Sysfs as root. This is how far i got in case someone is interested in either giving me hints on how to continue or pick up the work. https://github.com/basecamp/omarchy/compare/master...moWerk:omarchy:feature/battery-thresholds-configurable
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
- Related PRpr/12177· confirmed
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.