Repository navigation
Conversation
derekross
left a comment
There was a problem hiding this comment.
Thanks for this. It's a careful port. The alioth installer's fixed write targets, the phone-bound backup receipts, the explicit wipe flag and the dry-run default are exactly the kind of guards we want, and keeping the userdata-only allowlist in the F3 initramfs is a nice touch.
One blocker before we can merge, because it affects the reference device:
initramfs/init label check breaks Pixel boot. The Pixel initramfs has no util-linux; /sbin/blkid is busybox, which ignores -s LABEL -o value and prints the full dev: LABEL="…" UUID="…" TYPE="ext4" line. I checked this with our current cheetah initramfs busybox (1.37) under qemu, so with this change every Pixel would stay in the initramfs. The F3 only works because your initramfs adds util-linux, and test-storageguard.py stubs blkid. Could you read the label with dumpe2fs -h instead, the way grow_root already does, and add a test against the real busybox behaviour? Our dev phone's userdata does carry the omamobile-root label, so the check itself is fine once it reads the label correctly. It is still a new requirement for existing installs, so please mention it in the commit message.
Also requested:
- Shared rootfs/firstboot changes (masking
systemd-firstboot, the coredump drop-in,clock-epoch,date -s,Wants=time-set.target) change cheetah images too. Please move them into their own commit with the Pixel rationale, or gate them per device. Per systemd.special(7),time-set.targetshould only be ordered after, not pulled in. - Pin the serial in
tools/alioth/install.py. Readserialnoonce and pass-sto every fastboot call, so the checks and the writes can't reach different devices when more than one phone is in fastboot. - Keep F3 outputs and keys out of the maintainer paths.
init-keys.pyreuseskeys/gnupg/keys/fingerprint(our release signing key), andbuild.pyrebuildsomamobile-keyringinto the sharedout/repo. Please usekeys/alioth/,out/alioth/repoandout/alioth/for the root image. Today an F3 root becomes the default pick fortests/allandinstall-phone. - Status table. Please mark the DEVICES.md columns as "testing" until the clean install of this branch passes, and keep the F3 out of the Pixel quick start for now.
- Probe wording. Please make
--probesay in its help and dry-run text that it erasesdtbo_band leaves slot B active.
Smaller items (fine as follow-ups): package the extracted firmware instead of overlaying unowned files; replace the string-patching of the shared init with descriptor hooks; make UFS_RW in device.conf match the userdata-only allowlist you actually ship; one reboot-to.c; drop the Waydroid chains and unused ufw/bluez depends; bump firstboot to 0.1.1; squash to area-prefixed commits.
On the prebuilt reference kernel: since nothing is redistributed it's within our rules, but we'd like DEVICES.md to say plainly that the F3 kernel is a third-party pinned binary, with a path towards building it here.
* DEVICES: status as of 2026-10-26, from today's merged pull requests The matrix and the wanted list had fallen behind what merged since 2026-10-22: - Pixel Fold buttons, no -> works (volume and power): the volume keys (linux-omarchy-mobile#11, felix NOTES 2026-10-22) and the power key (#41: event0 reports KEY_POWER, logind ignores it, the phone stays up). - Pixel Fold GPU, no -> testing: Panthor bound and glmark2 ran on the cover (#5), but #41's smoke test found no render node, so not on by default. A new felix NOTES entry records both, since the 2026-10-22 entry still says the power key is not described. - Pixel Fold touch: still WIP; links the cover touch reports (#48, in review). - Pixel 9a boot: still WIP; "private kernel" is now "SoC patches merging, board DTS not public" (#18-#31, #34, #46 merged; issue #28). - Wanted: the Pixel 7a reached first light (#43, issue #36; descriptor in omarchy-mobile#37/#38); the Pixel 6 Pro boots our kernel to Hyprland on the G78 (#2, #3; package in #41); the Pixel 8 Pro's UFS plan and the zuma DT are in review (omarchy-mobile#42, kernel #13); the Pixel 11 Pro Fold has a tracking issue (#40). CAMERA-PLAN's status line still said the telephoto is "out of focus"; it is fixed-focus, sharp at a distance (2026-10-26, as DEVICES says). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * README, ROADMAP, CONTRIBUTING: status as of 2026-10-26 - README: a 2026-10-26 entry for omamobile-shell 0.2.17 and 0.2.18 (#43, #46: home pill, recents on swipe and hold, Power wakes a dark screen, the touch audit's quick wins), the reserved-memory overlap fix (linux-omarchy-mobile#58) and the community ports' merged steps. It now says Omarchy Mobile's own packages aren't hosted yet, since the 2026-10-22 entry read as if `omarchy update` fetched them over Wi-Fi: pkgs.omamobile.org is set up (30052e8) but nothing is published. The first non-Pixel ports (#25, #47) are still in review, not running. - ROADMAP: the updates row and OTA track name pkgs.omamobile.org as set up and empty; the telephoto's lens holds its I2C bus when driven (not "doesn't answer" or "NACKs"); the shell row gains #43 and #46; §3.7 no longer calls the installer "not started" while §1 has it in testing; §3.8 step 9 lists the ports under way. - CONTRIBUTING §5.2: zuma and zumapro are no longer "not started" (zuma: kernel #15-#17, #49, #50; zumapro: #18-#28, #34, #46). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * DEVICES, CONTRIBUTING: the Pixel 8 Pro in the matrix, and the naming rule husky's notes merged in #23 and its package and UFS plan in #42, so by DEVICES.md's own rule it moves from Wanted into the matrix: boot WIP (our kernel on slot B, the zuma DT in review as kernel #13), storage testing (UFS at HS-G4 behind the guard, Arch on userdata, UFS-PLAN U1-U3), a simple-framebuffer console, USB and SSH. It also makes the website's "under way on N more phones" count it. CAMERA-PLAN's older "telephoto lens works" entry is marked superseded by the fixed-focus finding, and kept as the record of that test. The rule that public copy describes a base by its parts and doesn't name other mobile Linux projects was only written in the website's repository. It is in CONTRIBUTING §6.3 and AGENTS.md now, with the exception for licensed sources (raised by #47). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Hi @bc-abe, a short follow-up for when you pick this up again. Main has moved since my review, so here is what the rebase needs on top of the points there:
The busybox |
Require omamobile-root before any repair, resize or mount of userdata. This is a new requirement for existing installations: an unlabelled root stays in rescue rather than being modified. Read the label with dumpe2fs, since Pixel BusyBox blkid ignores util-linux label/output selectors. Exercise the boot function with real ext4 images and ARM BusyBox 1.37, including its actual full-line blkid output and rejected Android labels. Co-Authored-By: Codex <noreply@openai.com>
Allow private signing/repository/image paths while keeping maintainer defaults. Support a board package profile and locally extracted runtime. Use optional device firewall and clock helpers; gate the RTC lower bound, interactive-firstboot mask and coredump workaround to alioth. Do not pull in time-set.target on Pixels or alter their firstboot ordering. Preserve upstream touch and autologin changes with shell 0.2.24 and firstboot 0.1.3. Rebased shell and firstboot suites pass. Co-Authored-By: Codex <noreply@openai.com>
…lags as a named exception Two decisions the Qualcomm ports (#17/#55-#59 flame, #52 coral, #25 alioth) were waiting on: - AGENTS.md said never to run an unsuffixed fastboot flash, but our own tools/install-phone already flashes userdata that way behind its guards. The rule now says so: userdata has no slots, and it is flashed only through install-phone. - On the Pixel 4 family the A/B slot flags live in GPT attributes, so marking slot B bootable is a partition-table write the storage guard can't block. It is allowed only as a narrow exception named per device in CONTRIBUTING §3.1 (LUN, sectors, bit, CRCs), done by hand once per boot-image install, with the flags recorded before and after, a rollback for a corrupted GPT and a way back. Never automatic. No device has an entry yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…lags as a named exception (#60) * AGENTS, CONTRIBUTING: userdata through install-phone; Qualcomm slot flags as a named exception Two decisions the Qualcomm ports (#17/#55-#59 flame, #52 coral, #25 alioth) were waiting on: - AGENTS.md said never to run an unsuffixed fastboot flash, but our own tools/install-phone already flashes userdata that way behind its guards. The rule now says so: userdata has no slots, and it is flashed only through install-phone. - On the Pixel 4 family the A/B slot flags live in GPT attributes, so marking slot B bootable is a partition-table write the storage guard can't block. It is allowed only as a narrow exception named per device in CONTRIBUTING §3.1 (LUN, sectors, bit, CRCs), done by hand once per boot-image install, with the flags recorded before and after, a rollback for a corrupted GPT and a way back. Never automatic. No device has an entry yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * DEVICES: the PinePhone Pro's codename and starting point The Wanted row had "-" as its codename, which omamobile.org prints next to the SoC ("-, Rockchip RK3399S"). It takes mainline's board name, pinephone-pro, and names that device tree, already in our kernel, as the starting point (promised on #47). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Build the pinned prebuilt 6.15.1-sm8250 kernel/runtime into private owner images. Keep F3 keys under keys/alioth and outputs under out/alioth, including its signed repository. Do not reuse release signing keys. Require phone-bound original backups, validated image payloads, explicit userdata-loss approval, and guarded rescue/readback gates. Read serialno once and pin subsequent fastboot checks and writes to that device. Fixed write targets are userdata and boot_b, with dtbo_b erase; probe help and dry runs disclose that erase and persistent slot B selection. Keep positive hardware status at testing pending a clean install of this assembly. Document the exact prebuilt kernel provenance and source-build path outside the Pixel quick start. No keys, images, firmware, captures or per-phone identifiers are included. Validation: tests/all, shell (189 checks), firstboot, 19 installer gates, real ext4 provisioning, owner-key isolation, ARM BusyBox 1.37 label checks. Fresh signed package/root build, personalized image/boot verification, ARM userspace checks and packed Dropbear key login pass. Clean physical reinstall remains pending. Co-Authored-By: Codex <noreply@openai.com>
f336beb to
2a9b1cd
Compare
|
Thank you, @bc-abe. I went through the new head against both my review and the follow-up, and you've done everything I asked: the label check reads What's left is new, and two of the three items are mine to decide, so I'll be explicit:
Small: the alioth-specific I'll post the decision on item 1 as soon as I have it. Thanks for your patience with a moving target. |
|
The decision on item 1: the F3's boot method becomes a branch inside Items 2 and 3 stand as above: |
|
A note to unblock this: #79 has merged, so contributor builds with a local key ( |
|
A friendly check-in: this has been quiet for over a week and now conflicts with main. If you'd like to continue, a rebase onto main will get it reviewed again. If I don't hear back within a week I'll close it to keep the queue tidy; it can be reopened any time. |
|
Yeah just leave me behind. I've been trying to get this update date but I am hitting different walls. When I have more time, I'll jump back in. Thanks for your hard work on this. |
|
Thank you, @bc-abe, and no hard feelings at all: this was the first port to a phone that isn't a Pixel, and the tree has moved a lot under it since October. The work that's here was careful: the serial pinned on every fastboot call, the label check through I'll close this to keep the queue tidy, as I said last week. It can be reopened any time, and your branch stays as it is. If you come back to it, a smaller first step would be easier to land than a rebase of all 68 files: Thanks again for all the work on this. |
…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>
…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>
What and why
Add an experimental private source-build and guarded installer for an unlocked POCO F3 (
alioth). Its Android-v0 boot image uses an appended DTB, so it needs a dedicated install path. The runbook isdevice/alioth/FLASH-RUNBOOK.md; provenance and gates are indevice/alioth/BRINGUP-M1.md.Review changes:
LC_ALL=C dumpe2fs, with a real ARM BusyBox 1.37/ext4 regression check. Existing installations now need theomamobile-rootlabel; other userdata stays in rescue without repair or mounting.time-set.targetwithout pulling that target in. Preserve main's touch/autologin changes.dtbo_berase and persistent slot-B selection.keys/alioth/, signed packages inout/alioth/repo, and generic root images inout/alioth/. Maintainer paths retain their defaults.The kernel is a prebuilt
6.15.1-sm8250kernel from mainlining/linux'snikroks/aliothtree at022f7f866a9377c34301e60ba131121c624d2e56, extracted from the checksum-pinned 2026-09-28 reference release with matching modules/runtime. No binary or firmware is redistributed. The notes record the path toward building it here. Firmware packaging and replacing shared-init string patches with descriptor hooks remain follow-ups.Device and build
alioth), existing native installation.6.15.1-sm8250.Checks (no phone needed)
tools/pr-check origin/mainpasses.tests/allpasses, including Pixel installer/image/storage tests.Additional checks: 19 installer gates; real ext4 provisioning with spaces and target-account validation; actual owner-key generation preserving maintainer sentinels; and real ARM BusyBox 1.37 label behaviour. A foreign-key cached neard package was quarantined; signature verification stayed enabled.
On the phone
userdata,boot_b, anddtbo_berase.Camera/haptic runtime experiments on the existing phone are a separate follow-up and do not change this PR's initial hardware claims. Calls, messaging/data, GPS, cameras/audio, haptics, fingerprint and suspend are not claimed supported by this initial profile. No keys, images, device identifiers or raw captures are included.
Read-only phone-smoke report — existing runtime, not the new root assembly
Kernel:
6.15.1-sm8250. The Camera app was open during this inventory; the camera-list result below records that limitation. Separate runtime tests captured main-camera frames, without claiming a clean install of this PR.