Repository navigation
omamobile-device-husky 0.1.15: Wi-Fi power save on by default - #836
Conversation
|
Thank you, Lef. The measurement is the right kind (alternating steps, medians, and the latency cost shown next to the saving), and the reasoning about the file's place is correct: I rebuilt your three cases with scratch config directories and NetworkManager 1.58, and got 2, 2 and 3 exactly as you describe. Omarchy's file sets Before I merge it:
A line in husky's NOTES with the two sets of numbers (30 mA, and the 71 ms spike) would be welcome too, so the trade stays on record. |
The Pixel 8 Pro's Wi-Fi read "Power save: off", and the phone drew about 30 mA more on battery that way than with it on (step medians of 532 to 543 mA off over four steps, 508 and 509 mA on over two, 2026-11-14). The package now ships wifi.powersave=3, the value the Pixel 6 Pro's package asks for, as /etc/NetworkManager/conf.d/zz-omamobile-wifi-powersave.conf, and lists it in backup= so an upgrade keeps a copy the user has changed. NetworkManager applies it when a connection comes up. Tested: the package's test/all on the desktop, and by hand on the phone (the package itself is not installed there): the same file in /etc/NetworkManager/conf.d, named zz-omamobile-wifi-powersave.conf with wifi.powersave=3, made NetworkManager --print-config read 3 where it read 2 before, iw reported power save on, and it stayed on after a reconnect. 200 pings at 0.2 s to the phone over Wi-Fi with power save off, on and off again: average 2.26, 2.52 and 2.27 ms, maximum 5.8, 71.2 and 6.1 ms, no loss in any. So it adds a latency spike here. 30 mA less on battery was measured earlier (2026-11-14, two 4-minute steps with it on between four with it off). Not tested: the installed package, hours of use, hotspot, resume from sleep. The file is installed in /etc and named zz-omamobile-wifi-powersave.conf on purpose: omarchy-settings ships /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf with wifi.powersave=2. Checked on the phone with NetworkManager --print-config: a file in /etc named 90-omamobile-... or omamobile-... still read 2, a zz-omamobile-... file in /etc read 3, and the same zz file in /usr/lib read 2 again, because NetworkManager reads /usr/lib first and /etc after it.
c81289b to
d4ce18c
Compare
|
Thanks @derekross. Rebased onto main after #806 and it's 0.1.15 now (version file and title), README rows kept both. The three wordings:
husky's NOTES has a Power save line with both sets of numbers (about 30 mA less, and the 71.2 ms ping max). The installed-package run with one attended suspend isn't done yet, my phone is off right now. I'll post the |
|
@derekross the run of the installed package, on my 8 Pro, on the charger, Wi-Fi connected. Package built from this branch's head (d4ce18c) and installed with One thing I didn't expect: right after the install a reconnect still gave The suspend, with a 120 s RTC alarm:
To be straight about what else was on the phone: my local sleep blocker for charging (it holds a block inhibitor while the charger is online) was stopped for this run and started again after.
Packages: hyprland 0.57.0-3.2, mesa 1:26.2.4-1.4, omamobile-device-husky 0.1.15-1, omamobile-shell 0.2.107-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1. The kernel is my own local build (omamobile plus my charger test commits), not the published one. |
|
Thank you, Lef. Version, rebase and the three wordings are all as asked, the NOTES line has both sets of numbers, and the run of the installed package is what I needed: the package owns the file, Your finding that the setting only applies after NetworkManager reloads its configuration is worth one sentence in the README: an updated phone gets it from its next boot. You were right to leave a reload out of the pacman script. Could you add that sentence in your next husky PR, and take out "Not yet booted from the package" there once you have rebooted on it? One thing for the record, since the smoke report shows it: this ran on your local kernel, in the hours you describe on #761. I've written about that on linux-omarchy-mobile#266; nothing to do here. |
The 8 Pro's Wi-Fi runs with power save off: Omarchy's
/etc/NetworkManager/conf.d/omarchy-wifi-powersave.confsetswifi.powersave=2, andiwsays "Power save: off". This turns it on for husky (wifi.powersave=3, as on the 6 Pro).Left: battery current with the cable out and the screen off, 2026-11-14, six steps of about 4 minutes with power save off, off, on, off, on, off (16 readings each). Step medians 537, 541, 532 and 543 mA with it off, 509 and 508 mA with it on, so about 30 mA less with it on. Right: 200 pings at 0.2 s from the desktop to the phone, off, on, off again: average 2.26, 2.52 and 2.27 ms, maximum 5.8, 71.2 and 6.1 ms, no loss in any. So power save adds an occasional latency spike, the usual trade.
Why the file is
/etc/NetworkManager/conf.d/zz-omamobile-wifi-powersave.confand not in /usr/lib: NetworkManager reads /usr/lib first and /etc after, so Omarchy's /etc file wins over anything in /usr/lib. I checked on the phone withNetworkManager --print-config: a file in /etc named90-omamobile-...oromamobile-...still read 2,zz-omamobile-...in /etc read 3, and the same zz file in /usr/lib read 2 again. It's inbackup=so a changed copy survives an upgrade.Tested: the package's test/all (26 ok) and tools/pr-check. On the phone by hand, the same file in /etc made
--print-configread 3, iw reported power save on, and it stayed on after a reconnect. Not tested: the installed package itself, hours of use, hotspot, and Wi-Fi after resume with power save on.The version says 0.1.14 since main is at 0.1.13; #806 also uses 0.1.14, so please set whatever fits at merge.