Repository navigation
Conversation
The first phone in these notes has Samsung 128 GB UFS 3.1. A second retail Pixel 8 Pro has a Kioxia 256 GB part that reports UFS 4.0, on the same HS-G4 two-lane link, so the notes now say what differs and what was checked on it: - the read-only UFS probe (UFS-PLAN U2): link up, 4 disks and 62 partitions, the storage guard holding; - the install from the signed development channel (U4), the first boot hitting derekross#188, and phone-smoke's required checks; - the display going off about 40 s after the session starts, with what Hyprland logs when it does; - the test tag husky-test-20261031-c6: the salixp lines, decoded touch events and the key events, and the module order that matters after modules-push. Notes only, nothing else changes. The data is from the phone in question: serial numbers, IMEI and MACs are not in it. Facts are marked [V] with their source or [I] where they are inferences.
The first version of this section said what switches the display off was unknown. It is the lock service's idle blank: omarchy-brightness-display off, which is a DPMS disable through hyprctl. Caught with audit watch rules on the script and hyprctl, 43 s after the session started. The same dispatch with enable brings the display back by hand, and pressing Power wakes it on the c6 test tag (reported by the phone's owner); a swipe and the PIN pad by touch unlocked the session on that build. Notes only.
The display bullet cited BRINGUP-M1 test 23 for "Power alone does nothing", but that test is about forcing a restart of a hung phone, not about waking a blanked screen. What can be checked: the omamobile head's zuma-husky.dts has no gpio-keys node, the c6 test tag's has one (derekross#148), so on the head kernel no key can wake a blanked screen. Notes only.
The first bullet said the device's raw_device_capacity matched sda's sector count. 0x1DCBC000 is 499,892,224 512-byte blocks, sda shows 499,490,816, so they differ by 401,408 sectors. Say so, and say the difference was not looked into. Notes only.
The display bullet only said Power wakes the screen the lock screen's idle blank turned off. The phone's owner reports that a tap wakes it as well on the c6 test tag. The other phone's owner sees only Power on older shell packages, so say that too. Notes only.
Owner
|
Thank you, Lef. This is a careful second-unit record: the U2 probe, the guard's allowlist, the real cause of the blank and the module-order trap. It conflicted with Brett's notes from #208, so I rebased it on top of them and dropped the line saying the other phone wakes only on Power, since you both see tap-to-wake now. Landed on main as fbd1096, authored by you (the PR shows as closed rather than merged because the commit went in directly). |
derekross
added a commit
that referenced
this pull request
Oct 31, 2026
… rounds L-348 to L-361: shared drivers judged against every int-line user (#150), board pins against every stock user (#151), ownership flags under the consumer's lock (#152), /chosen children and Google's panel constants (#154), same-day notes PRs on one device (#208/#209), merge simulations for DEVICES rows, ours included (#165), stacked PRs that merged main (#115/#117), titles behind renumbered versions, a contributor merge that dropped the PR (#99), smoke package lists as provenance and "owner-authorized" writes (#200), promised fixes and named tags checked on the remote (#153/#157/#158), and file swaps into old packages (#193). C-23 (usbc-deadman's device scope, kernel #107) and C-24 (BNEP in a lynx-only fragment, #98). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7 of 9 tasks
derekross
pushed a commit
that referenced
this pull request
Nov 11, 2026
#453) and the slot B retry notes (#627) Records the Pixel 8 Pro's two boots of kernel #209's head with the overlay used (driver bound, nfc0, the pad clock at count 1 and a tag read; the plain boot with nothing enabled), with s2idle under the clkout driver still open. Adds stage Z8 to AOC-PLAN for the packaged start from #453: the first boot's "no firmware node", Trusty under soc@0, the clean cold boot, the A/B tone check and the CS35L41 mailbox lines, cause unknown. BATTERY-NOTES section 9 now says set_active b alone refills slot B's tries. Signed-off-by: Lef <me@lefteros.com>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…ss#209) A second Pixel 8 Pro: the U2 probe, the storage guard's allowlist on a Kioxia part, the real cause of the blank screen (the lock's idle blank) and the module-order trap. Rebased onto derekross#208's notes by the maintainer; the line saying the other phone wakes only on Power is dropped, since both owners now see tap-to-wake. Closes derekross#209 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
… rounds L-348 to L-361: shared drivers judged against every int-line user (derekross#150), board pins against every stock user (derekross#151), ownership flags under the consumer's lock (derekross#152), /chosen children and Google's panel constants (derekross#154), same-day notes PRs on one device (derekross#208/derekross#209), merge simulations for DEVICES rows, ours included (derekross#165), stacked PRs that merged main (derekross#115/derekross#117), titles behind renumbered versions, a contributor merge that dropped the PR (derekross#99), smoke package lists as provenance and "owner-authorized" writes (derekross#200), promised fixes and named tags checked on the remote (derekross#153/derekross#157/derekross#158), and file swaps into old packages (derekross#193). C-23 (usbc-deadman's device scope, kernel derekross#107) and C-24 (BNEP in a lynx-only fragment, derekross#98). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
… AoC start (derekross#453) and the slot B retry notes (derekross#627) Records the Pixel 8 Pro's two boots of kernel derekross#209's head with the overlay used (driver bound, nfc0, the pad clock at count 1 and a tag read; the plain boot with nothing enabled), with s2idle under the clkout driver still open. Adds stage Z8 to AOC-PLAN for the packaged start from derekross#453: the first boot's "no firmware node", Trusty under soc@0, the clean cold boot, the A/B tone check and the CS35L41 mailbox lines, cause unknown. BATTERY-NOTES section 9 now says set_active b alone refills slot B's tries. Signed-off-by: Lef <me@lefteros.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brett suggested on #1 that I record my phone in husky's NOTES as a second unit, so this is that. It's notes only, one new section at the top of device/husky/NOTES.md and nothing else changes.
The phone is a Pixel 8 Pro with a Kioxia 256 GB part that reports UFS 4.0 (the first one in the notes is Samsung 128 GB, UFS 3.1). The section covers what differs and what I ran on it: the read-only UFS probe (U2), the U4 install from the signed development channel, the clock problem from #188 on first boot, why the display goes off about 43 s into the session (it's the lock screen's idle blank, and Power or a tap wakes it), and Brett's test tag husky-test-20261031-c6 (the salixp lines, the decoded touch and key events, and the module order that matters after modules-push). Each fact is marked [V] with where it came from or [I] where it's a guess, like the rest of the file. The serial, IMEI and MACs aren't in it.
Update: later commits fix mistakes in my first version and add that a tap wakes the screen too. The display bullet said I didn't know what switches the display off, it's the lock screen's idle blank and Power wakes it on the c6 tag. I then cited a test that was about something else for the wake, so that sentence now says what I actually checked (the omamobile head's device tree has no gpio-keys node, the c6 tag's has one). And I said the UFS raw capacity matched sda, it doesn't exactly (499,892,224 against 499,490,816 sectors), the notes now say so.
Phone: Pixel 8 Pro (husky), the second unit. Kernel: 7.3.0-rc6-omamobile-push1-gc7a0b2ef2f66 (Brett's c6 tag) for the touch and key results, and 7.3.0-rc6-omamobile-push1-g1c5ba1aa2acb (the omamobile head) for the U2 probe and the install. Packages touched: none.
What ran: tools/pr-check origin/main passes and tests/all passes. I didn't run tests/packages because no package changed. phone-smoke ran on the phone booted into the c6 build and its report is below. What I didn't test: nothing in this change writes to a phone, it's text. I haven't checked B0 vs B1 beyond what the notes say, and I don't know why the lock screen's blank fires at about 43 s and not after a few seconds, the notes say so.
tools/phone-smoke report
phone-smoke: husky
Kernel
7.3.0-rc6-omamobile-push1-gc7a0b2ef2f66, tools at0f57856, 2026-10-31T12:39Z.Packages: hyprland 0.56.2-5.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-device-husky 0.1.1-1, omamobile-firstboot 0.1.2-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.20-1, omamobile-owl-widgets 0.1.1-1, omamobile-shell 0.2.45-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1