Repository navigation
Conversation
|
Thank you, @nesmeck. The D3 runbook is exactly what I'd hoped for: each stage has its Pass, Stop and Rollback, and the stage-0 bring-up file comes with the rule to delete it. The results read well too, including the failed first try of stage 2 and why it failed, and the The package is safe in either order with linux-omarchy-mobile#181, since
If you reorder the kernel series as I asked on #181 (the padded-row commit before the DECON0 enable), the numbered list under "The changes" should follow. Either push that here, or I'll do it with the edits above. One question for the plan's next step, not for this PR. Suspend hasn't run on the Pixel 7 yet, and now gs-decon drives the screen at every boot. Before the first s2idle test, it would be good to add a D-step or a SLEEP gate that checks the screen comes back after a wake: DPMS on, a cold init if the panel was asleep, flips resuming. That way the first suspend doesn't also become the first test of gs-decon across a suspend. Thanks again, this is a really nice step for the Pixel 7. |
|
Thanks! I've pushed the reordered list of changes in D3: the padded-row commit is now number 4, with the reason it comes before the DECON0 enable, and the enable is number 5, matching linux-omarchy-mobile#181's new order. The "Kernel D3" paragraph and the "merged" edits are yours to make at merge, as you offered. Noted on the suspend gate: before the Pixel 7's first s2idle test I'll add a step that checks gs-decon across a wake (DPMS on, the panel's cold init if it slept, flips resuming). 🤖 Generated with Claude Code |
53d06e0 to
9432567
Compare
|
Thank you, @nesmeck. The list of changes in D3 now matches linux-omarchy-mobile#181's new order, with the reason the padded-row commit comes first. The package commit is unchanged, and thank you for taking the suspend gate on board. One thing moved under the PR since my last comment, not through anything you did. The release-channel change (#313) merged into Since you've allowed edits, I'll do that when I merge, with the edits from my last comment:
The squashed title will be "device-panther 0.1.6: the screen sleeps with the display off, and the D3 plan". I'll merge this after linux-omarchy-mobile#181, which waits for my Pixel 7 Pro run. Nothing more is needed from you here. |
9432567 to
2308680
Compare
|
Updated, as asked on linux-omarchy-mobile#181. The new head is
🤖 Generated with Claude Code |
Record D3's changes and runbook and its results on the phone: stage 0 and stage 1 (frame starts at 60.02 Hz), stage 2 first failing on Hyprland's padded 1080-pixel rows and then passing with the fix (1080x2400 at 60 Hz, smooth, no flip timeouts), and DPMS off/on with screen_off 0, 1 and 2, the last putting the panel to sleep and waking it through its cold init, also from the power key's lock. The Pixel 7 row's display cell names gs-decon and links linux-omarchy-mobile#181, which brings the kernel side. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Set gs_decon's screen_off to 2 in the display modprobe.d file, as the Pixel 7 Pro's package does: with the screen off, DECON stops sending frames and the panel goes to sleep, and DPMS on wakes it through the panel driver's cold init. DISPLAY-PLAN gate D3d proved it on the Pixel 7, from Hyprland's DPMS and from the power key's lock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
angelrenefm's unit passed every D3 step on linux-omarchy-mobile#181's head (issue derekross#342), as derekross asked on derekross#181: stage 0 found ABL's state as on the first unit, 60 Hz with no storm, 871 flips with no timeouts, and screen_off=2 six times out of six. The plan records it with his kernel release. The D3a paragraph now says its kernel lacked the padded-row commit, and D3c's that it had all five, for the series' new order. The package ships as 0.1.7: 0.1.6 is omarchy-mobile#396's AVB footers, which merges first. The results keep that the build tested was numbered 0.1.5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2308680 to
6bd1746
Compare
|
@derekross, the suspend gate you suggested has run: gs-decon across a wake on the Pixel 7, before any other suspend work. The kernel. It isn't linux-omarchy-mobile#181 alone. It is my local daily stack: The gate (D5). Each sleep wrote
All four sleeps had no flip timeouts or late flips, and no gs-decon, DSIM, panel or UFS errors. The one UFS line at each resume is the What it means for the suspend plan:
The gate and its results are in panther's DISPLAY-PLAN as D5, on a local branch. I'll send them after this PR merges, rather than add them here. 🤖 Generated with Claude Code |
…1.6 is derekross#396's, 0.1.7 is kept for derekross#281)
|
Thank you, @nesmeck, for the update, and thank you @angelrenefm for the D3 run on the second unit. The new table reads well: every step with its result and the kernel it ran on, and an honest "not checked" line. The rebase kept the Pixel 7 row as it was, the package change is the same one line with its test, and the version, status line and matrix now say 0.1.7, with the record still noting that the tested build was numbered 0.1.5. The plan stays as before: I'll merge linux-omarchy-mobile#181 once it has run on my Pixel 7 Pro, then #396 (0.1.6), then this as 0.1.7. At merge I'll flip "in review" to "merged" for #181 and write the squash title and body from the 0.1.7 version file, since the title here still says 0.1.5. One small thing I'll fix at the same time unless you get to it first: the "2026-11-03: D3 on a second Pixel 7" heading needs a blank line above it. Thanks for keeping this current while the kernel side waits. |
What and why
The Pixel 7's screen through
gs-decon. The kernel side is derekross/linux-omarchy-mobile#181. This PR brings the rest:screen_off0, 1 and 2.omamobile-display.confaddsoptions gs_decon screen_off=2, as the Pixel 7 Pro's package does. With the screen off, DECON stops its frames and the panel goes to sleep; DPMS on wakes it through the panel's cold init.gs_deconneeds no other option, since it goes straight to KMS (stage 2) by default.Device and build
uname -r):7.3.0-rc6-omamobile-push1-g53fab72d1489(omamobilecaf5f8a2b with device/lynx: WIFI-PLAN after the fs_ready boot #133, omamobile-omarchy 0.1.19: fingerprint on the lock only when a finger is enrolled #171, Lock screen retries fingerprint every 250 ms all night when no finger is enrolled #170, DEVICES: the matrix as of 2026-10-30 #177 and the gs-decon branch); stage 0 and 1 ran on…-gdc3f0ce5e425, the same branch without its last commit.Checks (no phone needed)
tools/pr-check upstream/mainpassestests/allpassestests/packagespasses (the panther package'stest/all)versionbumped, and the new version is in the commit subjectCo-Authored-By:trailer, never aSigned-off-by:On the phone
screen_off0, 1 and 2 all passed. With 2, the panel slept and woke through its cold init, also from the power key's lock and a tap.allow_txreadYandstageandscreen_offread 2 from the package alone, with everything above working.userdata, weakens the storage guard, or reads registers from userspace.tools/phone-smokereport (that boot, 0.1.5)phone-smoke: panther
Kernel
7.3.0-rc6-omamobile-push1-g53fab72d1489, tools at05b472c, 2026-11-01T18:20Z.Packages: hyprland 0.56.2-5.1, libcamera 0.7.2-4.21, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-device-panther 0.1.5-1, omamobile-firstboot 0.1.2-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.12-1, omamobile-owl-widgets 0.1.1-1, omamobile-shell 0.2.28-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1
🤖 Generated with Claude Code