Repository navigation
device-oriole: add minimal first-light policy package - #222
Conversation
Recover portable helpers and shared policy without enabling hardware services. Keep experimental battery and boot-check services outside this initial package.
|
Thank you for starting a public package for the Pixel 6. Keeping it minimal, with nothing enabled at install, is the right instinct. The copied files (
Nothing here is urgent, and I'm happy to look again whenever you've had a boot with it. |
Provide the repository configuration and package metadata, remove the unqualified boot-control tool, and document the safeguards required before replacing a local integration package.
Record the first-light audit without attributing untested behavior to the blocked drivers. Explain the separate experimental battery provider and the limits of charger status evidence.
Record ARM64 build and temporary-directory installation on the phone. Keep baseline smoke findings distinct from exact-package qualification; the installed integration safeguards were preserved. Co-Authored-By: Codex <noreply@openai.com>
Use a version above the installed local device package so normal pacman checks admit migration with the preserved integration safeguards. Record native makepkg and signed installation evidence, including the private companion and outstanding standalone/boot qualification limits. Co-Authored-By: Codex <noreply@openai.com>
|
Thank you, @Gr-linkk, for working through every point from my last comment. I went through them one by one against the new head:
One thing left before it comes out of draft, and it comes from your own notes: on your phone the package runs next to a private companion that keeps the boot check, the battery scripts and the reboot watchdog. One small, optional one: When it merges I'll write the squash title and body myself ( |
Separate the private staged-start guard from boot-success marking and explain why it cannot be copied into this minimal policy package alone. Mark the descriptor and README as unsupported for standalone installs, with startup and reboot-watchdog qualification still outstanding. Exercise install refusal with a relative destination instead of the host root. No installed policy, services or package version change. Co-Authored-By: Codex <noreply@openai.com>
|
Thank you, @Gr-linkk. This answers my last point the way I suggested: I ran Two small optional ones, if you're touching it again: the refusal test One heads-up for later: two open PRs (#459 and #403) update every copy of |
Round 46's confirmed candidates from the reviews of the open omarchy-mobile and linux-omarchy-mobile pull requests, the round's own process slips (shared refs and scratch files deleted by glob, a maintainer fixup that skipped the package's test/all, an amend on a contributor branch) and the 2026.11.08 release PRs (#547, #548, #549, #550, #560). Repeats of existing lessons extend them instead: L-45 (kernel #222), L-183 (#409), L-426 (the round's version collisions, now set by hand at merge) and L-550 (#471 with #420). C-34 and C-35 correct our #290 shell suggestion and round 45's claim that tests/dipper-probe guards anything. Stacked on #551 (round 45's lessons). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Round 46's confirmed candidates from the reviews of the open omarchy-mobile and linux-omarchy-mobile pull requests, the round's own process slips (shared refs and scratch files deleted by glob, a maintainer fixup that skipped the package's test/all, an amend on a contributor branch) and the 2026.11.08 release PRs (#547, #548, #549, #550, #560). Repeats of existing lessons extend them instead: L-45 (kernel #222), L-183 (#409), L-426 (the round's version collisions, now set by hand at merge) and L-550 (#471 with #420). C-34 and C-35 correct our #290 shell suggestion and round 45's claim that tests/dipper-probe guards anything. Stacked on #551 (round 45's lessons). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Check the staging refusal diagnostic so an unrelated install failure cannot satisfy the test. Keep the safe relative destination. Explain that any stock boot requires declining reset offers and fresh read-only protected radio backups before further radio work. Validation: package test/all passes; no runtime or version change. No phone access or hardware qualification. Co-Authored-By: Codex <noreply@openai.com>
|
Thank you, @Gr-linkk. The last commit takes both optional points: the refusal test now checks the message, and the slot A paragraph says to decline a reset and take a fresh read-only backup after any stock boot. Nothing else changed, the package test passes here on the branch merged with today's main, and the copied files still match cheetah's. I'm merging it as |
The Pixel 6's package came to main with its own copy of reboot-to.c (derekross#222), held to the 7 Pro's by its test. This pull request changes that source (the note for a deliberate restart, no printf family), so the ninth copy gets the same file.
Round 46's confirmed candidates from the reviews of the open omarchy-mobile and linux-omarchy-mobile pull requests, the round's own process slips (shared refs and scratch files deleted by glob, a maintainer fixup that skipped the package's test/all, an amend on a contributor branch) and the 2026.11.08 release PRs (derekross#547, derekross#548, derekross#549, derekross#550, derekross#560). Repeats of existing lessons extend them instead: L-45 (kernel derekross#222), L-183 (derekross#409), L-426 (the round's version collisions, now set by hand at merge) and L-550 (derekross#471 with derekross#420). C-34 and C-35 correct our derekross#290 shell suggestion and round 45's claim that tests/dipper-probe guards anything. Stacked on derekross#551 (round 45's lessons). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…or the Pixel 6 (derekross#222) A device package for the Pixel 6 with nothing enabled at install: the storage udev rule, USB gadget networking, `reboot-to`, the mirrorlist, sleep modes off, and blacklists for six modules whose coldplug isn't qualified. The README and `device.conf` say that an image built from this package alone is not a supported install: the boot check and recovery safeguards of the contributor's private companion are not in it, and slot B is not marked. Installed and smoke-tested on the contributor's Pixel 6 next to that companion. Co-Authored-By: Codex <noreply@openai.com>
Offline follow-up to the 2026-11-08 review
This package alone is not yet a supported Pixel 6 install. README and
device.confnow state that an image built from this package omits the private startup/recovery safeguards. This takes the documentation option offered in the review; no private services, battery code, boot-success writes or watchdog configuration are added.The audited private boot check validates staged storage, compositor, shell and touch state, then disarms its bounded handoff watchdog and clears a persistent Linux hang marker. The matching initramfs uses a leftover marker to enter guarded USB rescue before providers. It does not mark B successful or reset ABL's retry budget. The README explains the unmarked-slot limit and why stock-A fallback cannot be assumed to recover a phone whose userdata now contains Linux.
The private check depends on unpublished initramfs assets and a matching kernel. RebootWatchdogSec=1min is a separate shutdown safeguard; the recovered watchdog prerequisites do not establish standalone public-kernel binding/shutdown-reset qualification. It remains deferred rather than importing private integration code or claiming unsupported recovery coverage.
The optional refusal test now passes
relative-dirinstead of/, so a broken destination guard would not target the build host's root. Package contents/version and installed runtime behavior are unchanged.Validation: package
test/all, repositorytests/all, repository policy and whitespace checks pass. No phone access or new hardware qualification occurred. Derek accepted the unsupported-standalone scope on 2026-11-09 and confirmed this PR is ready for review. Standalone boot/recovery and package-combination boot/live rollback remain unqualified; they are limitations of this minimal package, not remaining readiness gates for this PR. The historical installation/smoke evidence below used a private companion and does not establish a supported standalone install.Adds a minimal Pixel 6 first-light policy package: reboot/system-setup helpers, storage-guard continuation, USB fallback networking, disabled sleep modes and six coldplug refusals. No services are enabled. Includes keyring dependency, device provides/conflicts, repository mirrorlist and channel-preserving install hook; omamobile-bootctl is omitted.
Version 0.2.0 sorts above the installed local 0.1.9-2 and satisfies the hardware packages' existing minimum-version dependencies. Native makepkg build/check/package passed with a separate BUILDDIR, and local package tests pass.
On 2026-11-07, normal signed pacman -U installed 0.2.0-1 on the Pixel 6, together with a PRIVATE companion preserving the existing boot-check/battery scripts and units, power-key policy and reboot-watchdog policy. This companion is not included in this PR; the public package must not replace a local integration package alone. All package signatures were verified by the phone's existing keyring; dependencies, signatures and hooks stayed enabled. Offline pacman replacement/rollback ownership tests pass.
Fresh SSH, safeguard hashes/ownership, unchanged enabled units, repository configuration/channel and pacman database checks passed. The supported systemd update marker temporarily prevented a udev retrigger. Laptop logging and a bounded rollback timer covered installation; owned safety markers/timer were cleared after checks. No reboot, flash, provider retry or shell restart.
Historical smoke has existing error-level kernel messages and backlight/NFC startup refusals; this is not a clean standalone-image or boot qualification. Live rollback and a boot of the new package combination remain untested. See device/oriole/NOTES.md's 2026-11-07 installation entry for the safeguards and evidence.
Post-install phone-smoke report (integration system with private safeguard companion)
phone-smoke: oriole
Kernel
7.3.0-rc6-oriole-hsi1-late-dev0-g4bd35d34abb9-dirty, tools atpr222-0.2.0, 2026-11-07T17:46Z.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.2.0-1, 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-oriole-local-safeguards 0.1.9-2, omamobile-owl-widgets 0.1.1-1, omamobile-shell 0.2.15-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