Repository navigation
Conversation
|
Thank you, this is a lovely step for the Pixel 7: brightness and display off/on from the shell's slider, with a plan that has a Pass, a Stop and a Rollback for every gate, and results recorded with their kernel release. Thanks also for listing exactly what you didn't test. What I checked: Before it lands:
One practical note: you mention slot B is at its last retry. Please don't spend that last try on this check. Instead, Not blocking: the Pixel 7 Pro BOE-panel PR (#262) adds its option on the same line of Thanks again. Once #177 is in and the boot result is posted, I'll merge. |
…ernel config The plan for the Pixel 7's display: what is known about its S6E3FC3 P10 panel and ABL's pipeline, the changes (a panel driver and the DSI command path in panther's device tree, then gs-decon with 1080x2400 modes), and the gates. G1 (the new omamobile base), D1 (the DSI command path, read-only) and D2 (brightness and display off/on over DCS) passed on the phone; their results are recorded. The Pixel 7 row's display cell names brightness and links the plan and linux-omarchy-mobile#177. kernel/configs/omamobile.config builds the panel driver as a module. It binds only to its compatible, which only panther's board file has. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ship a modprobe.d file that sets gs_dsim_cmd's allow_tx, so the panel driver can send the panel its brightness (DCS 0x51) and display off/on, as the Pixel 7 Pro's package does. The DSI command driver ships with sending off; on the Pixel 7, DISPLAY-PLAN gate D2 proved brightness at four levels, display off and back on, and the shell's slider. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks! I've rebased onto The boot from the package: it ran on a fastboot flash, so it didn't spend the last retry. That was the first gs-decon test boot (
The phone has booted from the package several times since, always with
Agreed on the merge order: this one goes right after #177. 🤖 Generated with Claude Code |
19805f0 to
7772dfc
Compare
|
Thank you, that's everything I asked for: the rebase kept Two things, neither for this PR to wait on:
I'll merge right after linux-omarchy-mobile#177, and handle the one-line conflict with the BOE-panel PR (#262) in the config fragment, whichever lands first. Thanks again, this is a really nice step for the Pixel 7. |
…ross#258) The Pixel 7's display brightness and off/on from the shell's slider. device-panther 0.1.4 ships a modprobe.d file setting the DSI command path's allow_tx=1, as the Pixel 7 Pro's package does, and the shared config fragment builds the S6E3FC3 panel driver (CONFIG_DRM_PANEL_SAMSUNG_S6E3FC3=m, linux-omarchy-mobile#177), which binds only to samsung,s6e3fc3-p10. DISPLAY-PLAN gets gated steps with a Pass, a Stop and a Rollback each, and the results with their kernel release. DEVICES' Pixel 7 display cell is updated. Maintainer edit at merge: DISPLAY-PLAN records the package boot posted on the PR (allow_tx reads Y, /etc/modprobe.d clean). Closes derekross#258 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…outside the rule; where data was checked The plan now says plainly that the 2026-11-13 and 11-14 sleeps with the modem up ran outside the rule in AGENTS.md, with their start times, and that the rule stands until the maintainer decides otherwise. For the night and the package runs it says where mobile data was checked (at the end, with Wi-Fi the first route), adds the night's count of "Reserve doorbell interrupt" and "PCI not powered on" lines (1,205 and 1,142, with data answering at the end; the daily kernel logs the same line awake with no sleep), and lists a run in the shape that lost data on the 7 Pro under what is left. The AGENTS sentence takes the maintainer's wording, so it doesn't go stale now that derekross#258 has merged. The series script checks data 5 s after every wake (a ping and a DNS query sent out of the bearer's interface), takes WIFI=off for runs with the bearer as the only route, refuses to start and stops when the palmtop isn't charging, and counts the doorbell lines at the end.
… up on a test kernel with the sleep guard (2026-11-13 to 11-15) This records the 9a's sleeps with the modem up on test kernels with linux-omarchy-mobile#232 and the zumapro sleep guard (#258): a refusal no longer costs the phone service, 299 of 300 sleeps in one boot were entered and woke with the modem registered, calls and texts wake the sleeping palmtop, and a cable-out night ended with mobile data down while the bearer was reported up. The runs of 11-13 to 11-15 were outside AGENTS' rule for modem-up sleep, as the section says with their start times; from 2026-11-15 the owner's palmtop runs these under #809, whose terms the plan quotes. It adds `device/tegu/bringup/modem-sleep-series.sh` (data over the bearer after every wake, `WIFI=off`, N 10 by default, stops off the charger, on the CP not ONLINE, and on a UFS error line or an oops in dmesg) and one sentence in AGENTS.md's modem-up entry.
…ell to works (opt-in), with the runs on the published branch The cell's old condition was a fix for the third no-wake and a series from the published kernel as it is. Kernel derekross#247 is merged, and on derek/omamobile at 26867fc4e (derekross#224, derekross#232, derekross#247, derekross#258) 300 of 300 sleeps with a 60 s alarm woke with the modem off on the night of 2026-11-17: 296 on the alarm and 4 within seconds on the touchscreen's interrupt with nobody at the palmtop. On 2026-11-16, 86 of 86 sleeps entered with the modem up woke, each ended by the modem within 29 s, so none of those reached its alarm. From the review of derekross#846: the word is "works (opt-in)", since auto-sleep ships off on the 9a (omamobile-device-tegu doesn't install /usr/share/omamobile/auto-sleep-default); the cell says again that a new sleep test runs attended first and that the modem's inhibitor stays, the owner's palmtop under derekross#809 excepted; and it cites merged notes, not derekross#758's comments. MODEM-PLAN gains the 2026-11-16 section: the runs on the test kernel and on the published branch under derekross#809's terms, the route finding that became derekross#837, and the palmtop hanging awake twice at a power-up of the modem's link (once between the sleeps of a series, once in everyday use with Wi-Fi connected), with the NV check after each. The Modem cell names those hangs. SLEEP-PLAN's S1 table gains a row for the 86 modem-up sleeps and one for the night's 300, and its status line is brought up to date.
What and why
Brightness for the Pixel 7. The kernel side is derekross/linux-omarchy-mobile#177: the S6E3FC3 panel driver and the DSI command path in panther's board file. This PR brings the rest:
omamobilebase alone), D1 (the DSI command path, read-only) and D2 (brightness and display off/on over DCS) passed on the phone, and their results are recorded.kernel/configs/omamobile.configgetsCONFIG_DRM_PANEL_SAMSUNG_S6E3FC3=m. It binds only tosamsung,s6e3fc3-p10, which only panther's board file has.modprobe.d/omamobile-display.confsetsoptions gs_dsim_cmd allow_tx=1, as the Pixel 7 Pro's package does, so the panel driver can send brightness and display off/on.screen_offcomes withgs-decon, in D3.Device and build
uname -r):7.3.0-rc6-omamobile-push1-g54fb87ae5295(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 and DEVICES: the matrix as of 2026-10-30 #177); G1 was…-g53710bb094e3.Checks (no phone needed)
tools/pr-check upstream/mainpassestests/allpassestests/packagespassesversionbumped, and the new version is in the commit subjectCo-Authored-By:trailer, never aSigned-off-by:On the phone
schedutil.modprobe -clists the option.allow_txat boot. The phone hasn't rebooted since the install, because slot B is at its last retry. I'll check it at the next boot and add the result.userdata, weakens the storage guard, or reads registers from userspace.The new kernel brings one warning,
cpu cpuN: EM: invalid perf. state: -22on the three clusters. It comes fromomamobile's new gs201 CPU DVFS: G1 already had it, without this branch.tools/phone-smokereportphone-smoke: panther
Kernel
7.3.0-rc6-omamobile-push1-g54fb87ae5295, tools at19805f0, 2026-11-01T15:59Z.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.4-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