Repository navigation
omamobile-device-husky 0.1.10: Suspend means suspend-to-idle on the Pixel 8 Pro - #656
Conversation
…ixel 8 Pro The 8 Pro had no sleep drop-in, so systemd's Suspend used the kernel's default, deep (/sys/power/mem_sleep reads "s2idle [deep]" on a second phone too, on husky-test-20261109-t1), which Linux can't wake from on zuma yet. The drop-in's settings are the Pixel 7 Pro's, as on the 8a (derekross#456); the test checks that, that install stages the file, and the two settings that matter. No hibernation: there is no swap. Suspend itself is still untested on the 8 Pro (ROADMAP, UFS-PLAN U5 and U6). This only keeps a tap on Suspend from choosing deep. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
@gitColinX thank you, this closes a real gap: six other device packages ship this drop-in (the 8a's among them) and the 8 Pro's didn't, so a tap on Suspend went to Yes please to the kernel PR that adds One note for whoever runs the first suspend test on an 8 Pro, since this makes the Suspend button reachable: the package starts Wi-Fi and has no sleep hook for it (on the Pixel 7 Pro the hook unloads Wi-Fi around a sleep unless the D3 handshake is proven), UFS wants @Somnius, for the record here too: your |
…ixel 8 Pro (derekross#656) The 8 Pro's package had no sleep drop-in, so systemd's Suspend used the kernel's default, `deep`, which Linux can't wake from on zuma yet. It now ships the Pixel 7 Pro's `sleep.conf.d/10-omamobile.conf` settings (`MemorySleepMode=s2idle`, no hibernation), as the 8a's package does, with a test that the settings match cheetah's and that install stages the file. Suspend itself is not qualified on the 8 Pro by this change. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Derek asked on derekross#656 for a short runbook in device/husky before an attended suspend test on an 8 Pro: Wi-Fi across sleep, UFS spm_lvl 5, NFC not polling. SUSPEND-PLAN.md has husky's read-only state for each (no sleep hook, so every stage unloads Wi-Fi and the PCIe host; spm_lvl 5 at boot; no NFC driver bound), the rest of what cheetah and raven needed (s2idle only, no cpuidle on husky), recovery, and four stages: pm_test dry runs, one RTC-woken s2idle, systemctl suspend woken by Power, ten cycles. Nothing in it has run on this unit yet. The ROADMAP Suspend row and UFS-PLAN U6 point to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 8 Pro's package had no sleep drop-in, so a tap on Suspend (or
systemctl suspend) used the kernel's default,deep, which Linux can't wake from on zuma yet. The 8a's package has had the drop-in since #456; this gives husky the same one.vendor/systemd/sleep.conf.d/10-omamobile.conf:MemorySleepMode=s2idle, no hibernation, hybrid sleep or suspend-then-hibernate. The settings are the Pixel 7 Pro's; only the comment names zuma and the 8 Pro.installstages it to/usr/lib/systemd/sleep.conf.d.test/all: the settings match cheetah's, install stages the file, and it holdsMemorySleepMode=s2idleandAllowHibernation=no.deepis the default on my phone too, and the drop-in doesn't cover a test that writes/sys/power/stateitself.Checked on my phone (G1MNW,
husky-test-20261109-t1, device package 0.1.8, read only):/sys/power/mem_sleepreadss2idle [deep], there is nomem_sleep_defaulton the command line, and nosleep.conf.dexists.Tested:
packages/omamobile-device-husky/test/allpasses; it fails with the install line removed, and withMemorySleepMode=deep.tools/pr-checkpasses.Not tested: suspend itself. It has never run on the 8 Pro (ROADMAP; UFS-PLAN U5 and U6), and I haven't run it. This only keeps Suspend from choosing
deep; it doesn't make s2idle known-good. The kernel side,mem_sleep_default=s2idleinzuma-husky.dtsas kernel #238 did for the 8a, is a separate PR I can send if you want it.