Repository navigation
device-akita 0.1.0: the Pixel 8a's package, and its storage plan (M2) - #456
Conversation
The Pixel 8a's UFS comes up behind the storage guard (gate c), and a fresh read-only backup is taken from our own kernel. - device/akita/BRINGUP-M2.md: stage 2's runbook (M2.1-M2.7) and the results of M2.1-M2.4. - device/akita/overlays/ufs-probe.dtso: the bring-up overlay for the first UFS boot, never default. - device.conf: NV_PARTS and NV_BACKUP_EXTRA, for tools/nv-backup, with their row in NOTES.md's provenance table. - packages/omamobile-device-akita 0.1.0: the generic set of the Pixel 8 Pro's first package. - device/akita/build-u3-root: husky's test-root builder, for M2.6. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, @aninmucek, this is another clean stage. The read-only first UFS boot, the guard's listing checked partition by partition against stock, and a fresh backup taken from your own kernel with both ends hashed are exactly the order I'd want. Explaining the eleven changed items by what stock and the bootloader write is what makes the new baseline trustworthy. The package is tidy too: every shared file is compared with its source, the test guards those comparisons so the package still builds on its own, and nothing in it touches a slot or the radio. CI is green. Two small fixes in
Suggestions, none blocking:
I'll merge #206 first, then this one. Thanks also for the note on the guard's timing. You're right, and it means husky's plan has the same wrong sentence. I'll fix that one. |
|
Tested on another retail Pixel 8a: M2.3, M2.4 and M2.6 pass on Starting point: stock CP3A.261005.005, bootloader M2.3 (guard), checked from the M1 initramfs over SSH:
M2.4 (backups), with the guard on and nothing mounted:
M2.6 (test root on
Findings:
Nothing outside |
…ew notes - packages/omamobile-device-akita: the suspend-to-idle drop-in. The 8a's /sys/power/mem_sleep reads "s2idle [deep]", and Linux has no zuma SoC sleep sequence to wake from deep. It uses cheetah's settings, with a comment that names zuma; the test compares the settings. - device/akita/build-u3-root: install kmod and run depmod for the slot B kernel's release, so modprobe finds modules in the test root (found by a second tester on derekross#456). - BRINGUP-M2.md: the status and the kernel citations now name linux-omarchy-mobile#206 and its DTS blob; --reinstall in the M2.6 and M2.7 commands; M2.6's results (gate d). - NOTES.md: the storage findings, and the per-phone partitions that NV_PARTS doesn't name. - ufs-probe.dtso: where its copied bootargs come from. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks for the review! Both fixes are in the new commit, along with M2.6's results:
The suggestions:
M2.6 (gate d) passed on this phone too:
@ShoreBits, thank you for testing on a second 8a! Your findings are in:
Your results are cited in BRINGUP-M2 and NOTES as the second unit. |
|
Thank you, @aninmucek. Both fixes are in, and I checked each one. The status line now matches the results. The plan cites linux-omarchy-mobile#206: @ShoreBits, thank you for running M2.3, M2.4 and M2.6 on a second 8a. Your phone was on the same build and bootloader, which also confirms the descriptor's AVB values for a second owner. The depmod and Checks: I'm happy to merge this as it is. A few small things, none blocking, for this PR or the next one:
I'll update the 8a's row in DEVICES.md for the Arch root after this merges, unless you'd rather add it here. Thanks again for another careful stage. |
…up, and #456's notes (#509) From the review of #456: - device.conf (and the package's copy): NV_BACKUP_EXTRA adds trusty_persist and trusty_userdata next to devinfo, as husky's package does since #449, so tools/nv-backup --check shows when Android has written Trusty's storage. - NOTES.md: trusty_userdata in the list of per-phone partitions, and the provenance row for the new value. - BRINGUP-M2.md: don't use Suspend in M2.7 until husky's U6; linux-omarchy-mobile#206 spelled out; tools/phone-smoke's report from the M2.6 root (test 18). - ufs-probe.dtso: "If the board file's bootargs change". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…i 8 lines #505 left (#680) The Pixel 8a's row still described first light. Since then Omarchy's image runs from userdata (BRINGUP-M2 gate e, #456 and kernel #206 merged), and the buttons and the touchscreen passed gates f and g (kernel #238 and #241 merged): Boot, Storage, Touch and Buttons say so. For the Mi 8, three lines promised on #505: BRINGUP-M1's [NOTES.md] link had no definition, the board DTS (kernel #220) is merged, not in review, and the status line names the 2026-11-11 boot NOTES records. The POCO F3 row said #25 was in review; it was closed as paused on 2026-11-11. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
…derekross#456) The Pixel 8a's UFS comes up behind the storage guard (gate c), and a fresh read-only backup is taken from our own kernel. - device/akita/BRINGUP-M2.md: stage 2's runbook (M2.1-M2.7) and the results of M2.1-M2.6 (gate d ran on linux-omarchy-mobile#206). - device/akita/overlays/ufs-probe.dtso: the bring-up overlay for the first UFS boot, never default. - device.conf: NV_PARTS and NV_BACKUP_EXTRA, for tools/nv-backup, with their row in NOTES.md's provenance table, and the per-phone partitions NV_PARTS doesn't name. - packages/omamobile-device-akita 0.1.0: the generic set of the Pixel 8 Pro's first package, plus the suspend-to-idle drop-in (the 8a offers "deep", and Linux has no zuma SoC sleep sequence to wake from it). - device/akita/build-u3-root: husky's test-root builder for M2.6, with kmod and depmod for the slot B kernel's release (found by a second tester). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…up, and derekross#456's notes (derekross#509) From the review of derekross#456: - device.conf (and the package's copy): NV_BACKUP_EXTRA adds trusty_persist and trusty_userdata next to devinfo, as husky's package does since derekross#449, so tools/nv-backup --check shows when Android has written Trusty's storage. - NOTES.md: trusty_userdata in the list of per-phone partitions, and the provenance row for the new value. - BRINGUP-M2.md: don't use Suspend in M2.7 until husky's U6; linux-omarchy-mobile#206 spelled out; tools/phone-smoke's report from the M2.6 root (test 18). - ufs-probe.dtso: "If the board file's bootargs change". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…i 8 lines derekross#505 left (derekross#680) The Pixel 8a's row still described first light. Since then Omarchy's image runs from userdata (BRINGUP-M2 gate e, derekross#456 and kernel derekross#206 merged), and the buttons and the touchscreen passed gates f and g (kernel derekross#238 and derekross#241 merged): Boot, Storage, Touch and Buttons say so. For the Mi 8, three lines promised on derekross#505: BRINGUP-M1's [NOTES.md] link had no definition, the board DTS (kernel derekross#220) is merged, not in review, and the status line names the 2026-11-11 boot NOTES records. The POCO F3 row said derekross#25 was in review; it was closed as paused on 2026-11-11. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Follows #414. The Pixel 8a's storage now comes up behind the guard, and this adds what the Arch root needs next, in one PR as the Pixel 8 Pro's #42 did. The kernel side is derekross/linux-omarchy-mobile#206.
device/akita/BRINGUP-M2.md(new): stage 2's runbook on husky's UFS-PLAN path (M2.1-M2.7), with the results so far:UFS_RWwritable.device/akita/overlays/ufs-probe.dtso(new): the bring-up overlay for M2.3's boot, never default. It sets the board'sbootargsplusomamobile.ufs-probe omamobile.initramfs.device/akita/device.conf:NV_PARTSandNV_BACKUP_EXTRA, with cheetah's values, so thattools/nv-backup -d akitaworks. All seven partitions exist on akita, and none is onUFS_RW. NOTES.md's provenance table gets the row.packages/omamobile-device-akita0.1.0 (new): the generic set of the Pixel 8 Pro's first package (device-husky 0.1.0: the Pixel 8 Pro's package, and its UFS plan #42):reboot-to;The shared files are byte-identical to cheetah's and husky's, and its test checks that.
installstages nine files, none of which marks a slot or starts the radio, the charger or a camera.device/akita/build-u3-root(new): husky's test-root builder with akita's names, for M2.6.M2.7, Omarchy's image, needs
omamobile-device-akitain the signed[omamobile]repository, which only you can publish.Two observations:
/initstarting at 0.28 s. The guard flags every partition by 0.61 s, and nothing is mounted or written in between. husky's UFS-PLAN (Design 6) says the guard runs before the disks appear; it's probably this way on husky too.nv-backup's retries absorbed. A plain stream afterwards ran at 36 MB/s.Checks:
tests/all: 424 ok, 0 not ok.tests/packages: every package passes, the new one included (15 ok). Under the load of a kernel gate running alongside, timing tests in five other packages failed:omamobile-mirror,-mmd,-shell,-audio(its 30-minute timeout) and-sensors. All of them pass with the CPU free, andmmdandsensorsalso when run on their own.tools/pr-check: passes.tools/nv-backup -d akita --list, the loader check (DEVICE=akita bin/omamobile initramfs-config) andtests/device-overlayspass.tools/phone-smoke: not run, since it needs the Arch root and a session, which come in M2.6 and M2.7.🤖 Generated with Claude Code