Repository navigation
Conversation
The Pixel 6 notes still say Linux has not booted, although a native integration image passed the read-only phone smoke check. Record that result and its limits, and bring the matrix into line with the hardware states the check observed. The S2MPG10 alarm-status register differs from S2MPS14. Record the source evidence and distinguish the published kernel from the test phone's corrected integration kernel. No live pending-alarm result is claimed. Co-Authored-By: Codex <noreply@openai.com>
|
Congratulations on the first native boot! Before this lands: please record where the kernel and the oriole packages come from (branch, commit, and how slot B was written) in NOTES, and mark the matrix cells "unpublished kernel/packages" with a link to the notes, as raven's row does. The smoke report lists |
Answer the review's source, keyring and recovery questions without turning the private integration stack into a public support claim. Record the recovered kernel and package bases, local shell backport, keyring payload audit and limits of the historical slot evidence. Mark the observed matrix cells as unpublished kernel/packages. The recovered root image's packaged keyring and trusted list contain a local signing key, verified against its mtree and device-package signature. Document the existing contributor workflow as the next image's correction; no phone trust or partition state changes here. Assisted-by: OpenAI GPT-6 Astra
The image and mtree establish that the local key was packaged. The rebuilt recipe remains in an unavailable backup; do not imply its exact command was reconstructed. Assisted-by: OpenAI GPT-6 Astra
|
Thank you for the candour; this is exactly what the notes are for. Before I merge:
No further |
Record the recovered local deployment-tool differences and the explicit block-device read-only changes used for B success. State that the metadata writes lacked project approval and further writes await the maintainer's approval. Distinguish the recovered header-write and executed slot assertions from the original byte pair and retry count, which remain unavailable in the offline backup. Assisted-by: OpenAI GPT-6 Astra
… 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>
|
Thank you for answering everything so plainly, including the parts that can't be recovered. Going through my questions:
One thing I should have said last time. Slot B is marked on your phone, and we're not marking it again until #252 is settled. So please use Two small edits I'll make when I merge, unless you'd rather do them yourself:
I'll write the squash message myself, since the branch has a merge from main in it. Thanks again. This is the kind of record that lets the next Pixel 6 owner start from solid ground. |
…s files `-d husky` staged the four Wi-Fi files only, with Bluetooth and the rest left "for drivers". Kernel derekross#199 (Bluetooth) and derekross#200 (haptics) are on `omamobile` now, so an installed Pixel 8 Pro had the drivers and not the files: cs40l26-vibra stopped at "No cs40l26.wmfw" and btbcm at "firmware Patch file not found" (a scan found nothing). husky's map gains stock's `BCM.hcd` as `brcm/BCM.google,zuma-husky.hcd` and the five CS40L26 files the 7 Pro and the 9a take. This `BCM.hcd` names the module and board ("G5SN_V17_HK3 REL ..."), not the chip, so husky's Bluetooth check looks for that; the haptics checks run for husky too. The test's husky fixture has the new files and a case refuses another chip's patch. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…s files (#722) `-d husky` staged Wi-Fi only; the Bluetooth and haptics drivers are on `omamobile` now (kernel #199, #200), so an installed Pixel 8 Pro had the drivers without their files. husky's map gains stock's `BCM.hcd` as `brcm/BCM.google,zuma-husky.hcd` and the five CS40L26 files under the 7 Pro's names; its Bluetooth check looks for the module and board string (`G5SN_V<n>_HK3`), since this patch names no chip, and the haptics checks run for husky too. Tested on the author's own factory image (CP3A.261005.005, ten files) and phone. `Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>` (the commit's trailer, kept).
… 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>
…nd the RTC alarm finding (derekross#200) Pixel 6 notes: the native boot on one phone, its build provenance and recovery limits, and the RTC alarm finding (the S2MPG10 alarm callback reads INT3M at 0x08 instead of STATUS2 at 0x0d, fixed by linux-omarchy-mobile#149). The DEVICES row records that slot B was marked successful and vbmeta_b verification turned off without project approval (Gr-linkk). Closes derekross#200 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Requested tooling and metadata evidence (2026-10-31)
The
vbmeta_banddevinfowrites were done without project approval. NOTES now says that explicitly. No furtherdevinfoorvbmetawrites will be made without the maintainer's explicit approval; this follow-up is an offline audit.Installer and push: the recovered October 28 project snapshot is based on
1155a7c352edf6313fb4e2ff02f054c9cb1902b6. Itstools/install-phoneis byte-identical to that base. Itsbin/omamobilediffers:pushadds the optionalPUSH_MODULES_POLICY=require-matchrefusal, follows image symlinks for readback length, and uses systemd's reboot when PID 1 is systemd. The complete diff of both files is below, including the other builder/Fastboot changes inbin/omamobile. This compares the recovered source snapshot to its pinned upstream base, not today's main, and does not establish the exact script bytes used for every earlier deployment.Snapshot SHA-256:
tools/install-phone:bd194ef43768a2aa94e34fa7fbb762fdc22a38e713d02b0bda1ed62008a10d07(also the base file's hash).bin/omamobile:302c5e717fee5d720d6a4edff1cead8efa8c31cab996a72228f5bb98d5e852e3.The recovered Oriole descriptor has
BOOT_IMAGES="boot vendor_boot dtbo"andUFS_RW="boot_b vendor_boot_b dtbo_b userdata". Thedevinfoandvbmeta_bchanges were separate bring-up operations.What made
devinfowritable: recovered source for the separatemark-b-success-37.pygate explicitly usedblockdev --setrwon the containing boot LUN and then thedevinfopartition. It restored the partition and disk to read-only with an EXIT trap, a 20-second systemd undo timer and a 120-second watchdog. It did not stop the watcher or alterUFS_RW: the historical init watcher skipped nodes already marked in/run/ufs-ro/, so it did not continuously reassert their read-only flags. The opening was an explicit block-device RO change, not an installer operation or device-node permission change.The helper performs a 128-byte header write, with only bit 1 at
0x35changed, followed by full 8192-byte verification. The recovered gate execution result at 2026-10-18 09:04:51 UTC reports that one-bit change, unchanged A/opaque bytes, both nodes restored RO, and refreshed backups verified.Requested before/after evidence: the original gate's
devinfo-before-b-success.img,devinfo-after-b-success.imgand write logs are listed in the private backup inventory, but they are not recovered locally and the backup host is unreachable. I cannot yet supply the original0x30–0x37byte pair or contemporaneous retry count. The next Fastboot controller completed at 09:06:19 UTC after assertingcurrent-slot=b,slot-successful:b=yes, andslot-unbootable:b=no, with no set-active. A native audit at 09:11:29 UTC reported B success persisted and A unchanged. Those are recovered executed assertions/results, not a recovered raw Fastboot transcript. The notes state this evidence gap explicitly; no new metadata write was attempted to reconstruct it.Validation for this documentation-only follow-up:
tools/pr-check upstream/mainand the whitespace check passed. The runtime tools and packages are unchanged by this PR; the historical diff below is evidence, not code being proposed for installation.Complete local tools diff against 1155a7c (install-phone has no diff)
Review follow-up (2026-10-31)
The new NOTES section records the exact kernel/mobile bases, detached native kernel worktree and unpublished source changes, local package snapshots, shell backport, installation method and recovery limits. Every observed matrix cell now links to "unpublished kernel/packages".
The keyring concern was confirmed: the recovered local image's
omamobile-keyring 20261013.oriole1-1contains the upstream public key plus the local package-signing public key, and trusts the latter. Both keyring files match the package mtree; the additional key verifies the archived local device package. This was a packaged trust change, not merely a build-container key. The exact rebuilt recipe has not been recovered; the payload audit does not claim to reconstruct its build command. The note explicitly identifies it as outside contributor-build policy and describes the existing--localworkflow with an unchanged upstream keyring as the correction for the next image. No modified keyring, signing material, image or package is included in this PR, and no phone trust was changed during this audit.Historical records show the matching stock build booted on B then A with the expected bootloader before Linux installation. Per-slot bootloader-version queries were unsupported; this is not a fresh partition-version audit. The notes also disclose that the B verification and B-success writes were done without project approval, the historical record of preserved A images/slot record, and Linux userdata's separate Android restoration requirement.
After merging current main:
tools/pr-check upstream/mainandtests/allpass. The package sources are unchanged from the same main revision whosetests/packagespassed during the companion #195 follow-up. Existing local environment skips are recorded below. This revision is an offline artifact/documentation audit, not a new hardware qualification.The Pixel 6 notes and device matrix still say Linux has not booted. A
read-only smoke check on a native test image now confirms the boot, storage
guard, USB and session. Update those entries with the observed hardware
states, keeping the unpublished integration stack distinct from public
images.
Document the source-confirmed S2MPG10 alarm-status register discrepancy
that a separate kernel change addresses. The test phone already contains
the correction; the smoke check does not test a pending alarm or wake.
Checks:
tools/pr-check upstream/mainandtests/allpassed. The suiteskipped Docker provisioning, AOSP image-layout checks, overlay compilation
and root-image smoke because their prerequisites were unavailable. The 45
overlays and the full image-layout test, including AVB test footers, passed
separately with a recovered
dtcand Android 16 AOSP tools. The tests usefake devices and images; no package was changed.
The smoke check recorded no failed units, oops, BUG or WARN and 48 dmesg
error lines. Sound, sensors and cameras were skipped.
Pixel 6 smoke report
{ "device": "oriole", "repo": "review-readonly", "kernel": "7.3.0-rc6-oriole-hsi1-late-dev0-g4bd35d34abb9-dirty", "packages": [ "hyprland 0.56.2-7", "libcamera 0.7.2-4", "mesa 1:26.2.4-1", "omacam 0.1.9-1", "omamobile-apps 0.2.0-1", "omamobile-backlight-oriole 0.1.0-8", "omamobile-battery-counters-oriole 0.2.0-1", "omamobile-bluetooth-oriole 0.1.2-2", "omamobile-bluez 5.87.omamobile1-1", "omamobile-charger-cache-oriole 0.1.0-8", "omamobile-device-oriole 0.1.9-2", "omamobile-firstboot 0.1.1-1", "omamobile-gpu-oriole 0.1.0-3", "omamobile-keyring 20261013.oriole1-1", "omamobile-mirror 0.2.1-1", "omamobile-nfc-oriole 0.1.0-9", "omamobile-omarchy 0.1.6-1", "omamobile-owl-widgets 0.1.1-1", "omamobile-shell 0.2.12-1", "omamobile-torch-oriole 0.1.1-2", "omamobile-wifi-oriole 0.1.8-3", "omarchy 4.0.4-2", "quickshell 0.3.2.r7.g2b4501a-1" ], "checks": [ { "name": "boot", "status": "ok", "required": true, "detail": "kernel 7.3.0-rc6-oriole-hsi1-late-dev0-g4bd35d34abb9-dirty, slot b, up 851s" }, { "name": "storage guard", "status": "ok", "required": true, "detail": "49 partitions; only userdata and slot B's boot images writable" }, { "name": "root", "status": "ok", "required": true, "detail": "ext4 on userdata, 97G free" }, { "name": "kernel health", "status": "ok", "required": true, "detail": "no oops or BUG; 0 WARN, 48 error lines in dmesg" }, { "name": "systemd units", "status": "ok", "required": false, "detail": "none failed" }, { "name": "USB gadget", "status": "ok", "required": true, "detail": "bound to 11110000.usb" }, { "name": "display", "status": "ok", "required": false, "detail": "card0-Unknown-1 connected, 1080x2400" }, { "name": "GPU", "status": "ok", "required": false, "detail": "render node on panfrost" }, { "name": "session", "status": "ok", "required": true, "detail": "Hyprland and the Omarchy shell running" }, { "name": "lock", "status": "ok", "required": false, "detail": "PAM file present (the shell didn't answer lock status)" }, { "name": "touch", "status": "ok", "required": false, "detail": "ST FTM5 touchscreen (oriole staged)" }, { "name": "buttons", "status": "ok", "required": false, "detail": "gpio-keys" }, { "name": "Wi-Fi", "status": "ok", "required": false, "detail": "wlP1p1s0 on brcmfmac, link up" }, { "name": "Bluetooth", "status": "ok", "required": false, "detail": "hci0, powered true" }, { "name": "battery", "status": "ok", "required": false, "detail": "78% Charging, 34 °C" }, { "name": "sound cards", "status": "skip", "required": false, "detail": "none" }, { "name": "sensors", "status": "skip", "required": false, "detail": "no sensor proxy" }, { "name": "cameras", "status": "skip", "required": false, "detail": "no libcamera tools" }, { "name": "thermal", "status": "ok", "required": false, "detail": "hottest zone 34 °C" } ] }