From 11c585f4b9296f0490df9ef40ce6e48db4c9da0c Mon Sep 17 00:00:00 2001 From: Gr-linkk <280405187+Gr-linkk@users.noreply.github.com> Date: Fri, 30 Oct 2026 18:17:19 -0700 Subject: [PATCH 1/4] device-oriole: record the native boot and RTC status finding 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 --- device/oriole/NOTES.md | 8 +++++++- docs/DEVICES.md | 2 +- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/device/oriole/NOTES.md b/device/oriole/NOTES.md index 5d1e10154..68fde9945 100644 --- a/device/oriole/NOTES.md +++ b/device/oriole/NOTES.md @@ -1,7 +1,7 @@ # Pixel 6 (oriole) bring-up notes -Findings for the Pixel 6 port, newest first. The port is a community effort tracked in [issue #2](https://github.com/derekross/omarchy-mobile/issues/2); the 6 Pro (raven) and 6a (bluejay) share it. Facts are marked [V] (checked, with the source) or [I] (an inference to check on a phone). Nothing has been flashed or booted yet: the phone facts come from read-only adb and fastboot queries of a stock phone. +Findings for the Pixel 6 port, newest first. The port is a community effort tracked in [issue #2](https://github.com/derekross/omarchy-mobile/issues/2); the 6 Pro (raven) and 6a (bluejay) share it. Facts are marked [V] (checked, with the source) or [I] (an inference or a recovered report still to check). The October 14–16 phone facts below came from read-only queries of a stock phone; later tests booted Linux on a Pixel 6. Sources: @@ -9,6 +9,12 @@ Sources: - `U/`: upstream Linux v7.0, `arch/arm64/boot/dts/exynos/google/gs101*.dts(i)`. - `P/`: postmarketOS pmaports [`device/testing/device-google-oriole`](https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/main/device/testing/device-google-oriole), [`soc-google-gs101`](https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/main/device/testing/soc-google-gs101) and [`linux-postmarketos-gs101`](https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/main/device/testing/linux-postmarketos-gs101) (7.0.6), which builds [gs101-mainline/linux @ d28cfa42](https://github.com/gs101-mainline/linux/tree/d28cfa4275b95e93f4b7a1e743de31b723bd21b8). +## 2026-10-30: native boot and RTC alarm status + +- [V] A Pixel 6 booted native Linux from slot B with its root on `userdata`, using the unpublished `7.3.0-rc6-oriole-hsi1-late-dev0-g4bd35d34abb9-dirty` kernel and a separate integration package set. A read-only `phone-smoke --here --json` run passed all required checks: storage guard, root, USB and desktop session. It reported no failed units, oops, BUG or WARN, and 48 existing dmesg error lines; sound, sensors and cameras were skipped. This is a test-phone result, not an installation claim for the public images. +- [V, source] On the published kernel's `omamobile` branch, the S2MPG10 alarm callback reads `S2MPS14_REG_ST2` at offset `0x08`. On S2MPG10 that is `INT3M`; [Google's register definitions](https://android.googlesource.com/kernel/google-modules/soc/gs/+/204078758737776959ecc85c527a00fd2cabb62f/include/linux/mfd/samsung/s2mpg10-register.h) place `STATUS2` at `0x0d`, and its [RTC driver](https://android.googlesource.com/kernel/google-modules/soc/gs/+/204078758737776959ecc85c527a00fd2cabb62f/drivers/rtc/rtc-s2mpg10.c) reads the alarm-0 status bit there. The proposed kernel fix is S2MPG10-specific; the S2MPG12 path remains unchanged. The test phone's unpublished kernel already contains the correction. +- [I] The smoke test does not exercise a live pending alarm, alarm delivery, suspend or wake. Those paths remain to be independently verified. + ## 2026-10-16: stage 0, part 2: a retail Pixel 6 (stock, bootloader locked) Read-only queries (`adb shell getprop`, `/dev/block/by-name`, `fastboot getvar all`) of a stock phone; facts only, no serial numbers. diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 3ae5e481c..a8f1cfe79 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -22,7 +22,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | Pixel Fold | felix | gs201 (Tensor G2) | WIP ([#3](https://github.com/derekross/omarchy-mobile/issues/3)) | WIP (UFS behind the read-only guard, checked on the phone) | WIP (cover: simplefb console; inner: simpledrm output listed by Hyprland, its splash reserved by [kernel #72](https://github.com/derekross/linux-omarchy-mobile/pull/72); both panels' display triggers set by the descriptor, [#82](https://github.com/derekross/omarchy-mobile/pull/82)) | testing (Panthor; glmark2 on the cover, not up on every image yet; [notes](../device/felix/NOTES.md#2026-10-26-the-power-key-and-the-gpu-in-the-published-kernel)) | WIP (cover: chip id read, no touches yet; the driver's touch reports are merged, [kernel #48](https://github.com/derekross/linux-omarchy-mobile/pull/48), untested on the Fold; [notes](../device/felix/NOTES.md#2026-10-23-cover-touch-id)) | works (volume and power; [notes](../device/felix/NOTES.md#2026-10-26-the-power-key-and-the-gpu-in-the-published-kernel)) | works | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | | Pixel 6 Pro ([notes](../device/raven/NOTES.md)) | raven | gs101 (Tensor) | works ([#2](https://github.com/derekross/omarchy-mobile/issues/2)) | works | works (120 Hz through gs-decon and the S6E3HC3 driver; unpublished kernel, `omamobile-gs101-display`, in review as [kernel #116](https://github.com/derekross/linux-omarchy-mobile/pull/116), [plan](../device/raven/DISPLAY-PLAN.md)); the published kernel has the boot console only | partial (Panfrost; DVFS on an unpublished kernel, [plan](../device/raven/GPU-PLAN.md)) | works ([kernel #8](https://github.com/derekross/linux-omarchy-mobile/pull/8)) | works | works (a NOT FOR MERGE DT change; [plan](../device/raven/USB-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-wifi`; [plan](../device/raven/WIFI-PLAN.md)) | partial ([kernel #6](https://github.com/derekross/linux-omarchy-mobile/pull/6); own address; pairing untested; start-up after a warm reboot is [#77](https://github.com/derekross/omarchy-mobile/issues/77)) | works (the gauge; unpublished kernel) | works (the MAX77759 charger at stock's limits with its temperature guard, loaded at boot by device-raven 0.1.26; a full charge to 100 %; the battery node is in the published kernel, [kernel #112](https://github.com/derekross/linux-omarchy-mobile/pull/112), tested on an unpublished kernel; [plan](../device/raven/USB-PLAN.md#4-charging-the-max77759-charger-ravens-b3-after-cheetahs)) | works (CS40L25A through feedbackd, device-raven 0.1.27, with the phone's own firmware from `tools/extract-vendor-firmware -d raven`; the driver and node are merged, [kernel #114](https://github.com/derekross/linux-omarchy-mobile/pull/114); [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (tested on `omamobile-gs101-torch`; the LED's node is now in the published kernel, [kernel #113](https://github.com/derekross/linux-omarchy-mobile/pull/113), not yet run from it; [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-gnss`; [plan](../device/raven/GNSS-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-aoc`; [plan](../device/raven/AUDIO-PLAN.md)) | no (the amplifiers stay off until raven's own limits are validated, and without them the card doesn't probe, so no mics either; [plan](../device/raven/AUDIO-PLAN.md#without-the-amplifiers-2026-10-27-gb3d6253b0d61-device-raven-0123)) | works (accelerometer, light, proximity, compass through the AoC; unpublished kernel) | WIP (calls, texts and data on an unpublished kernel, `omamobile-gs101-cpif`; the package doesn't enable it; [plan](../device/raven/MODEM-PLAN.md)) | no | no | no | no | | Pixel 7a ([notes](../device/lynx/NOTES.md)) | lynx | gs201 (Tensor G2) | WIP ([#36](https://github.com/derekross/omarchy-mobile/issues/36): Arch root on `userdata` from slot B, SSH; the device package marks the slot successful) | WIP (UFS behind the read-only guard, in the published kernel, [kernel #91](https://github.com/derekross/linux-omarchy-mobile/pull/91); [notes](../device/lynx/NOTES.md#2026-10-24-on-screen-console-and-ufs)) | WIP (simpledrm console only, [notes](../device/lynx/NOTES.md)) | no | WIP (GT9895 touches in the session, in the published kernel, [kernel #93](https://github.com/derekross/linux-omarchy-mobile/pull/93); [notes](../device/lynx/NOTES.md#2026-10-24-touchscreen-rtc-and-slot-retries)) | no | works | no (parked at the chip's boot ROM; [plan](../device/lynx/WIFI-PLAN.md)) | WIP (same chip as Wi-Fi; scans through its own UART; the device tree is in review, [kernel #98](https://github.com/derekross/linux-omarchy-mobile/pull/98), and the package side, [#98](https://github.com/derekross/omarchy-mobile/pull/98); [plan](../device/lynx/WIFI-PLAN.md)) | no | no | no | no | no | no | no | no | no | no | no | no | no | -| Pixel 6 | oriole | gs101 (Tensor G1) | WIP ([#2](https://github.com/derekross/omarchy-mobile/issues/2): descriptor and boot images from the factory image and a retail phone; not booted yet) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | +| Pixel 6 | oriole | gs101 (Tensor G1) | WIP (native test image on one phone; [notes](../device/oriole/NOTES.md#2026-10-30-native-boot-and-rtc-alarm-status)) | WIP (guarded `userdata` root on test image) | WIP (connected output on test image) | WIP (Panfrost render node present) | WIP (touchscreen detected; input not checked by smoke) | WIP (gpio-keys detected; input not checked by smoke) | WIP (USB network and SSH on test image) | WIP (link up; traffic not checked by smoke) | WIP (controller powered; pairing not checked) | WIP (charge and temperature reported) | WIP (charging reported; control not checked) | no | no | no | no | no | no | no | no | no | no | no | | Pixel 4 | flame | SM8150 (Snapdragon 855) | testing (temporary RAM boot; [notes](../device/flame/BRINGUP-M1.md)) | testing (RAM probe; all UFS read-only) | testing (1080x2280 console; software desktop in separate Arch payload) | testing (separate Arch payload; FD640 contexts, llvmpipe desktop) | testing (separate Arch payload; events and PIN unlock verified) | no | testing (NCM + ACM + SSH; sustained transfers can disconnect) | testing (guarded RAM scan; association untested) | no | no | no | no | no | no | - | no | no | no | no | no | no | - | | Pixel 4 XL ([notes](../device/coral/NOTES.md)) | coral | SM8150 (Snapdragon 855) | WIP (direct ABL v2 boot on the test handset's slot A; slot-B install and §3.1 entry pending; [notes](../device/coral/BRINGUP-M1.md)) | testing (read-only `blockdev` guard + RAM `overlayfs`) | testing (1440x3040@60Hz S6E3HC2 DSC 1.1 KMS, DPMS, brightness) | testing (Adreno 640 / FD640 Mesa Freedreno, Hyprland) | testing (FTS SPI multitouch + read-only flash guard) | testing (power via `qcom-pon` + volume via `gpio-keys`) | testing (CDC ECM + ACM + SSH; stays up with host USB switched off) | testing (`WCN3990` `ath10k_snoc` + `rmtfs -r`, WPA2/DHCP/HTTPS; radio sessions ran before the modem baseline) | WIP (`WCN3990` `hci_qca` `hci0` up + BLE scan; audio/pairing open) | WIP (PM8150B ADC `VBAT_SNS` voltage + FG temp; aftermarket pack on test unit: no reply from `1-0036`) | testing (PM8150B SMB5 charger with `4.20 V` / `500 mA` kernel clamp) | testing (`CS40L25A` I2C click waveform) | testing (PM8150L flash LEDs + quick-settings tile) | no | - | testing (QDSP6 + dual `CS35L36` amps capped at `-26 dB` + `IA8508` SPI mic DSP) | testing (`SLPI` + `fastrpc` + RAM-backed `hexagonrpcd` + QMI SSC: 7 sensors + Soli radar) | WIP (`MPSS` boots with `rmtfs -r` + patched `tqftpserv`, SIM detected; no IPA/voice yet; radio sessions ran before the modem baseline) | no | testing (`CAMSS` + `IMX363`, `IMX481`, `IMX520`, dual `OV7251` NIR; `libcamera` softISP) | no | - | | Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | WIP ([#28](https://github.com/derekross/omarchy-mobile/issues/28): clocks, ACPM, panel and TCPC merged; the SoC and board device tree is in review, [kernel #80](https://github.com/derekross/linux-omarchy-mobile/pull/80)) | WIP (UFS root; reset across suspend merged, idle clock gating [kernel #99](https://github.com/derekross/linux-omarchy-mobile/pull/99)) | WIP (DSI panel 1080x2424 at 60 Hz, 120 Hz in review; panel driver merged, display DT [kernel #90](https://github.com/derekross/linux-omarchy-mobile/pull/90), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88)) | WIP (Panthor to 890 MHz; DT [kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85), [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87)) | WIP (DT [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), sleep fix [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82)) | WIP (gpio-keys; Power wakes s2idle) | WIP (gadget and replug; host mode: VBUS on, no enumeration yet; repeater driver [kernel #107](https://github.com/derekross/linux-omarchy-mobile/pull/107)) | WIP (brcmfmac joins WPA2; driver in review, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56)) | WIP (BCM4383 merged, [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); BlueZ, A2DP) | WIP (the gauge reads; unpublished kernel) | WIP (status and inhibit [kernel #92](https://github.com/derekross/linux-omarchy-mobile/pull/92); PD contract, tcpci_maxim merged, [kernel #97](https://github.com/derekross/linux-omarchy-mobile/pull/97)) | WIP (CS40L26, VPBR merged, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96)) | WIP (LM3644, 25 steps; DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96)) | no (firmware and CHPP run; the engine faulted with its three rails off at hand-off, now on, [kernel #101](https://github.com/derekross/linux-omarchy-mobile/pull/101)) | WIP (audio and sensors; unpublished kernel) | WIP (speakers capped, mics, A2DP; unpublished kernel) | WIP (accelerometer, light, proximity; unpublished kernel) | WIP (ONLINE with IPC, no SIM yet) | WIP (reads cards, [kernel #100](https://github.com/derekross/linux-omarchy-mobile/pull/100), clock [kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104)) | WIP (all three stream through libcamera, switching between them works; [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63), [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103)) | WIP (s2idle; Power and RTC alarm wake; drain still high) | WIP (sensor, trusted app and secure storage up, its stores on loop devices of images in `userdata`, [#101](https://github.com/derekross/omarchy-mobile/pull/101); factory calibration fetched, not loaded yet) | From 1db8eb2843baa6a5dc078b7f46f6f65bc3c84873 Mon Sep 17 00:00:00 2001 From: Gr-linkk <280405187+Gr-linkk@users.noreply.github.com> Date: Sat, 31 Oct 2026 10:03:20 -0700 Subject: [PATCH 2/4] device-oriole: document the local build and trust provenance 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 --- device/oriole/NOTES.md | 66 ++++++++++++++++++++++++++++++++++++++++++ docs/DEVICES.md | 2 +- 2 files changed, 67 insertions(+), 1 deletion(-) diff --git a/device/oriole/NOTES.md b/device/oriole/NOTES.md index 68fde9945..9e1b2fafe 100644 --- a/device/oriole/NOTES.md +++ b/device/oriole/NOTES.md @@ -9,6 +9,72 @@ Sources: - `U/`: upstream Linux v7.0, `arch/arm64/boot/dts/exynos/google/gs101*.dts(i)`. - `P/`: postmarketOS pmaports [`device/testing/device-google-oriole`](https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/main/device/testing/device-google-oriole), [`soc-google-gs101`](https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/main/device/testing/soc-google-gs101) and [`linux-postmarketos-gs101`](https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/main/device/testing/linux-postmarketos-gs101) (7.0.6), which builds [gs101-mainline/linux @ d28cfa42](https://github.com/gs101-mainline/linux/tree/d28cfa4275b95e93f4b7a1e743de31b723bd21b8). +## 2026-10-31: build provenance and recovery limits + +This describes the unpublished stack in the October 30 smoke report. It is +not a reproducible build of the public Oriole descriptor or an installer +qualification. The records and recovered artifacts were audited offline; +this audit did not reflash or inspect the phone's current partitions. + +- **Kernel** [V, recovered source metadata]: the base is + [`omamobile` commit `4bd35d34abb9`](https://github.com/derekross/linux-omarchy-mobile/commit/4bd35d34abb92a745479a2de62816b28304b4449). + The native build used a detached worktree at that commit with unpublished + local changes, producing + `7.3.0-rc6-oriole-hsi1-late-dev0-g4bd35d34abb9-dirty`. + There is no published branch containing that complete integration tree. +- **Packages** [V, recovered sources and build receipts]: the mobile source + was local branch `pixel6-bringup`, based on + [`1155a7c352ed`](https://github.com/derekross/omarchy-mobile/commit/1155a7c352edf6313fb4e2ff02f054c9cb1902b6), + with unpublished changes and separate package-source snapshots. The + `omamobile-device-oriole 0.1.9-2` source matches all 24 files in its build + receipt; its archived package and the GPU, Wi-Fi, Bluetooth, torch, + battery, charger, NFC and backlight packages are local builds, not + packages from the project's published repository. The device package + was built in an offline ARM64 package container. The smoke report + establishes the installed versions; source receipts alone do not. +- **Shell** [V, recovered package]: local `omamobile-shell 0.2.12-1` was + rebuilt from the installed local 0.2.10 source on + `omamobile-oriole-canvas-budget`, preserving its phone-specific files and + backporting the Canvas budget fix from + [`be98c2c22e2b`](https://github.com/derekross/omarchy-mobile/commit/be98c2c22e2b260300c59787861fee200ef2ad58). + The recovered package's `runtime.js` matches that commit byte for byte. + This is not a claim that upstream shell 0.2.12 was installed unchanged. +- **Keyring correction** [V, recovered root image]: the local rebuild + `omamobile-keyring 20261013.oriole1-1` retained the upstream public key + and added a local public signing key to `omamobile.gpg` and its trusted + list. The keyring payload matches the installed package's mtree in the + recovered image; the additional key verifies the archived local device + package. The local key therefore entered the packaged trust list, not + only the build environment. This does not follow the contributor-build + policy, and that rebuilt keyring must not be distributed as the project's + keyring. Neither the modified keyring nor signing material is included + in this PR. The correction for the next image is the existing + [contributor build workflow](../../docs/RELEASES.md#10-signing): + unchanged upstream keyring, preserved published-package signatures, + separate `keys/oriole/` and `out/oriole/`, and local-key trust confined to + the build image. Any later on-device local trust is a separate owner + action. No installed trust database was changed by this audit. +- **Slot B installation** [I, historical run records]: the initial root + installation used the local `tools/install-phone` after its dry run, + writing `boot_b`, `vendor_boot_b`, `dtbo_b` and `userdata`. Later kernel + deployments used the local `bin/omamobile push` with B-image readback. + Bring-up also used separately owner-authorized exceptions: a flags-3 + stock copy of `vbmeta_b`, and an audited B-success flag update at offset + `0x35` in `devinfo`, preserving the other bytes and restoring read-only + protection. Early verification tests restored original `vbmeta_b`; + the later native-root run records retain the B verification change. + These exceptions are historical facts, not instructions or an extension + of this repository's public installer permissions. +- **Slot A and bootloaders** [I, historical run records]: before Linux + installation, the matching factory build and full OTA booted stock on + B and then A, both reporting `slider-17.0-15681480`. The separate + per-slot bootloader-version variables were unsupported, so independent + partition-version equality was not established. The subsequent Linux + records preserve A's images and slot record. A fresh partition audit + has not been performed for this PR. `userdata` now contains Linux; + returning to Android requires deliberate data restoration, not simply + switching to slot A. + ## 2026-10-30: native boot and RTC alarm status - [V] A Pixel 6 booted native Linux from slot B with its root on `userdata`, using the unpublished `7.3.0-rc6-oriole-hsi1-late-dev0-g4bd35d34abb9-dirty` kernel and a separate integration package set. A read-only `phone-smoke --here --json` run passed all required checks: storage guard, root, USB and desktop session. It reported no failed units, oops, BUG or WARN, and 48 existing dmesg error lines; sound, sensors and cameras were skipped. This is a test-phone result, not an installation claim for the public images. diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 59e7f064a..fb07b899a 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -22,7 +22,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | Pixel Fold | felix | gs201 (Tensor G2) | WIP ([#3](https://github.com/derekross/omarchy-mobile/issues/3)) | WIP (UFS behind the read-only guard, checked on the phone) | WIP (cover: simplefb console; inner: simpledrm output listed by Hyprland, its splash reserved by [kernel #72](https://github.com/derekross/linux-omarchy-mobile/pull/72); both panels' display triggers set by the descriptor, [#82](https://github.com/derekross/omarchy-mobile/pull/82)) | testing (Panthor; glmark2 on the cover, not up on every image yet; [notes](../device/felix/NOTES.md#2026-10-26-the-power-key-and-the-gpu-in-the-published-kernel)) | WIP (cover: chip id read, no touches yet; the driver's touch reports are merged, [kernel #48](https://github.com/derekross/linux-omarchy-mobile/pull/48), untested on the Fold; [notes](../device/felix/NOTES.md#2026-10-23-cover-touch-id)) | works (volume and power; [notes](../device/felix/NOTES.md#2026-10-26-the-power-key-and-the-gpu-in-the-published-kernel)) | works | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | | Pixel 6 Pro ([notes](../device/raven/NOTES.md)) | raven | gs101 (Tensor) | works ([#2](https://github.com/derekross/omarchy-mobile/issues/2)) | works | works (120 Hz through gs-decon and the S6E3HC3 driver; unpublished kernel, `omamobile-gs101-display`, in review as [kernel #116](https://github.com/derekross/linux-omarchy-mobile/pull/116), [plan](../device/raven/DISPLAY-PLAN.md)); the published kernel has the boot console only | partial (Panfrost; DVFS on an unpublished kernel, [plan](../device/raven/GPU-PLAN.md)) | works ([kernel #8](https://github.com/derekross/linux-omarchy-mobile/pull/8)) | works | works (a NOT FOR MERGE DT change; [plan](../device/raven/USB-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-wifi`; [plan](../device/raven/WIFI-PLAN.md)) | partial ([kernel #6](https://github.com/derekross/linux-omarchy-mobile/pull/6); own address; pairing untested; start-up after a warm reboot is [#77](https://github.com/derekross/omarchy-mobile/issues/77)) | works (the gauge; unpublished kernel) | works (the MAX77759 charger at stock's limits with its temperature guard, loaded at boot by device-raven 0.1.26; a full charge to 100 %; the battery node is in the published kernel, [kernel #112](https://github.com/derekross/linux-omarchy-mobile/pull/112), tested on an unpublished kernel; [plan](../device/raven/USB-PLAN.md#4-charging-the-max77759-charger-ravens-b3-after-cheetahs)) | works (CS40L25A through feedbackd, device-raven 0.1.27, with the phone's own firmware from `tools/extract-vendor-firmware -d raven`; the driver and node are merged, [kernel #114](https://github.com/derekross/linux-omarchy-mobile/pull/114); [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (tested on `omamobile-gs101-torch`; the LED's node is now in the published kernel, [kernel #113](https://github.com/derekross/linux-omarchy-mobile/pull/113), not yet run from it; [plan](../device/raven/HAPTICS-TORCH-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-gnss`; [plan](../device/raven/GNSS-PLAN.md)) | works (unpublished kernel, `omamobile-gs101-aoc`; [plan](../device/raven/AUDIO-PLAN.md)) | no (the amplifiers stay off until raven's own limits are validated, and without them the card doesn't probe, so no mics either; [plan](../device/raven/AUDIO-PLAN.md#without-the-amplifiers-2026-10-27-gb3d6253b0d61-device-raven-0123)) | works (accelerometer, light, proximity, compass through the AoC; unpublished kernel) | WIP (calls, texts and data on an unpublished kernel, `omamobile-gs101-cpif`; the package doesn't enable it; [plan](../device/raven/MODEM-PLAN.md)) | no | no | no | no | | Pixel 7a ([notes](../device/lynx/NOTES.md)) | lynx | gs201 (Tensor G2) | WIP ([#36](https://github.com/derekross/omarchy-mobile/issues/36): Arch root on `userdata` from slot B, SSH; the device package marks the slot successful) | WIP (UFS behind the read-only guard, in the published kernel, [kernel #91](https://github.com/derekross/linux-omarchy-mobile/pull/91); [notes](../device/lynx/NOTES.md#2026-10-24-on-screen-console-and-ufs)) | WIP (simpledrm console only, [notes](../device/lynx/NOTES.md)) | no | WIP (GT9895 touches in the session, in the published kernel, [kernel #93](https://github.com/derekross/linux-omarchy-mobile/pull/93); [notes](../device/lynx/NOTES.md#2026-10-24-touchscreen-rtc-and-slot-retries)) | no | works | no (parked at the chip's boot ROM; [plan](../device/lynx/WIFI-PLAN.md)) | WIP (same chip as Wi-Fi; scans through its own UART; the device tree is in review, [kernel #98](https://github.com/derekross/linux-omarchy-mobile/pull/98), and the package side, [#98](https://github.com/derekross/omarchy-mobile/pull/98); [plan](../device/lynx/WIFI-PLAN.md)) | no | no | no | no | no | no | no | no | no | no | no | no | no | -| Pixel 6 | oriole | gs101 (Tensor G1) | WIP (native test image on one phone; [notes](../device/oriole/NOTES.md#2026-10-30-native-boot-and-rtc-alarm-status)) | WIP (guarded `userdata` root on test image) | WIP (connected output on test image) | WIP (Panfrost render node present) | WIP (touchscreen detected; input not checked by smoke) | WIP (gpio-keys detected; input not checked by smoke) | WIP (USB network and SSH on test image) | WIP (link up; traffic not checked by smoke) | WIP (controller powered; pairing not checked) | WIP (charge and temperature reported) | WIP (charging reported; control not checked) | no | no | no | no | no | no | no | no | no | no | no | +| Pixel 6 | oriole | gs101 (Tensor G1) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); native test image on one phone) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); guarded `userdata` root on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); connected output on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); Panfrost render node present) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); touchscreen detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); gpio-keys detected; input not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); USB network and SSH on test image) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); link up; traffic not checked by smoke) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); controller powered; pairing not checked) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charge and temperature reported) | WIP ([unpublished kernel/packages](../device/oriole/NOTES.md#2026-10-31-build-provenance-and-recovery-limits); charging reported; control not checked) | no | no | no | no | no | no | no | no | no | no | no | | Pixel 4 | flame | SM8150 (Snapdragon 855) | testing (temporary RAM boot; [notes](../device/flame/BRINGUP-M1.md)) | testing (RAM probe; all UFS read-only) | testing (1080x2280 console; software desktop in separate Arch payload) | testing (separate Arch payload; FD640 contexts, llvmpipe desktop) | testing (separate Arch payload; events and PIN unlock verified) | no | testing (NCM + ACM + SSH; sustained transfers can disconnect) | testing (guarded RAM scan; association untested) | no | no | no | no | no | no | - | no | no | no | no | no | no | - | | Pixel 4 XL ([notes](../device/coral/NOTES.md)) | coral | SM8150 (Snapdragon 855) | WIP (direct ABL v2 boot on the test handset's slot A; slot-B install and §3.1 entry pending; [notes](../device/coral/BRINGUP-M1.md)) | testing (read-only `blockdev` guard + RAM `overlayfs`) | testing (1440x3040@60Hz S6E3HC2 DSC 1.1 KMS, DPMS, brightness) | testing (Adreno 640 / FD640 Mesa Freedreno, Hyprland) | testing (FTS SPI multitouch + read-only flash guard) | testing (power via `qcom-pon` + volume via `gpio-keys`) | testing (CDC ECM + ACM + SSH; stays up with host USB switched off) | testing (`WCN3990` `ath10k_snoc` + `rmtfs -r`, WPA2/DHCP/HTTPS; radio sessions ran before the modem baseline) | WIP (`WCN3990` `hci_qca` `hci0` up + BLE scan; audio/pairing open) | WIP (PM8150B ADC `VBAT_SNS` voltage + FG temp; aftermarket pack on test unit: no reply from `1-0036`) | testing (PM8150B SMB5 charger with `4.20 V` / `500 mA` kernel clamp) | testing (`CS40L25A` I2C click waveform) | testing (PM8150L flash LEDs + quick-settings tile) | no | - | testing (QDSP6 + dual `CS35L36` amps capped at `-26 dB` + `IA8508` SPI mic DSP) | testing (`SLPI` + `fastrpc` + RAM-backed `hexagonrpcd` + QMI SSC: 7 sensors + Soli radar) | WIP (`MPSS` boots with `rmtfs -r` + patched `tqftpserv`, SIM detected; no IPA/voice yet; radio sessions ran before the modem baseline) | no | testing (`CAMSS` + `IMX363`, `IMX481`, `IMX520`, dual `OV7251` NIR; `libcamera` softISP) | no | - | | Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | works ([#28](https://github.com/derekross/omarchy-mobile/issues/28): native boot from slot B, the Arch root on `userdata`, `omamobile-device-tegu`; slot B was marked successful by hand on 2026-10-28 with the `devinfo` write approved on 2026-10-22, now on hold ([#125](https://github.com/derekross/omarchy-mobile/pull/125)), and the package does not mark it; unpublished kernel: the SoC and board device tree is [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (UFS behind the read-only guard; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (120 Hz through gs-decon; the panel driver [kernel #89](https://github.com/derekross/linux-omarchy-mobile/pull/89), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88), merged, the display DT [kernel #90](https://github.com/derekross/linux-omarchy-mobile/pull/90) in review; brightness and the panel's sleep are not claimed until they have a dated record; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Panthor, the desktop renders, runtime suspend when idle; this boot runs at a fixed 160 MHz, so frequency scaling and the GPU thermal zone count as in review, [kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) in review, [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Synaptics S3908 over SPI, [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; survives sleep, [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (gpio-keys: power and volume; the power key wakes from sleep; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CDC NCM and SSH; reconnects after a replug, `omamobile-tegu-usb-rescue` ([the replug record](../device/tegu/NOTES.md#2026-10-28-what-the-device-tables-claims-rest-on)); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (BCM4383 on PCIe through brcmfmac, WPA2 with iwd, kept loaded across sleep by the package's sleep hook; started by hand, not by the package; [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (hci_uart on the bootloader's address, BlueZ, A2DP; [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (MAX77779 gauge with temperature, current and time estimates through UPower; [kernel #66](https://github.com/derekross/linux-omarchy-mobile/pull/66); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (the chip charges on its own; the charger driver with its charge limit and inhibit is loaded by hand, [kernel #92](https://github.com/derekross/linux-omarchy-mobile/pull/92); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CS40L26A through feedbackd, with brownout prevention, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (LM3644, 25 steps to 75 mA, quick-settings tile; its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | WIP (a position fix on 2026-10-30 and Omarchy's Location switch serving it on 2026-10-31, started by hand: 46 of 52 GGA sentences fixed, 9-13 satellites, first fix about 80 s after a client connects; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150) and [#114](https://github.com/derekross/omarchy-mobile/pull/114), and a session lasts as long as the modem's PCIe link, one to five minutes, which is the open item; [plan](../device/tegu/MODEM-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | testing (audio and sensor DSP through the GSA and Trusty, 93 services; the package ships its start disabled until a kernel enables the nodes, so it is started by hand; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (speakers at a -10 dB ceiling, microphone, through the AoC card and PipeWire; by hand, as the AoC; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (accelerometer, light, proximity through the AoC; by hand, as the AoC; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | WIP (ONLINE with IPC on an unpublished kernel, no SIM yet; [plan](../device/tegu/MODEM-PLAN.md)) | testing (NXP ST54L through nxp-nci: polls and read a payment card on 2026-10-29 with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged ([kernel #100](https://github.com/derekross/linux-omarchy-mobile/pull/100) closed into it), [kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) in review; started by hand; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (three cameras stream through libcamera; by hand; [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) in review, [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | WIP (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on, which ships off; the power key or the RTC wakes it, but three test sleeps have not woken, so sleep tests stay attended ([plan](../device/tegu/SLEEP-PLAN.md) S1); the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (enrolls, matches, refuses other fingers and unlocks the lock screen through Trusty and `omamobile-fingerprint`, 2026-10-29; the service ships disabled; [kernel #126](https://github.com/derekross/linux-omarchy-mobile/pull/126), merged; [plan](../device/tegu/FINGERPRINT-PLAN.md)) | From 170341bae739d197e369e12e2e95e9418d3dc3af Mon Sep 17 00:00:00 2001 From: Gr-linkk <280405187+Gr-linkk@users.noreply.github.com> Date: Sat, 31 Oct 2026 10:08:58 -0700 Subject: [PATCH 3/4] device-oriole: distinguish keyring payload evidence from its recipe 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 --- device/oriole/NOTES.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/device/oriole/NOTES.md b/device/oriole/NOTES.md index 9e1b2fafe..643e3d769 100644 --- a/device/oriole/NOTES.md +++ b/device/oriole/NOTES.md @@ -45,7 +45,9 @@ this audit did not reflash or inspect the phone's current partitions. list. The keyring payload matches the installed package's mtree in the recovered image; the additional key verifies the archived local device package. The local key therefore entered the packaged trust list, not - only the build environment. This does not follow the contributor-build + only the build environment. The rebuilt source recipe has not yet been + recovered; this establishes the package contents, not its exact build + command. This does not follow the contributor-build policy, and that rebuilt keyring must not be distributed as the project's keyring. Neither the modified keyring nor signing material is included in this PR. The correction for the next image is the existing From 0e54fdc2430ea9101803373f44c0dafdff6a9209 Mon Sep 17 00:00:00 2001 From: Gr-linkk <280405187+Gr-linkk@users.noreply.github.com> Date: Sat, 31 Oct 2026 11:48:41 -0700 Subject: [PATCH 4/4] device-oriole: document unapproved metadata writes 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 --- device/oriole/NOTES.md | 57 ++++++++++++++++++++++++++++++++++++------ 1 file changed, 50 insertions(+), 7 deletions(-) diff --git a/device/oriole/NOTES.md b/device/oriole/NOTES.md index 643e3d769..15c46adcc 100644 --- a/device/oriole/NOTES.md +++ b/device/oriole/NOTES.md @@ -60,13 +60,26 @@ this audit did not reflash or inspect the phone's current partitions. installation used the local `tools/install-phone` after its dry run, writing `boot_b`, `vendor_boot_b`, `dtbo_b` and `userdata`. Later kernel deployments used the local `bin/omamobile push` with B-image readback. - Bring-up also used separately owner-authorized exceptions: a flags-3 - stock copy of `vbmeta_b`, and an audited B-success flag update at offset - `0x35` in `devinfo`, preserving the other bytes and restoring read-only - protection. Early verification tests restored original `vbmeta_b`; - the later native-root run records retain the B verification change. - These exceptions are historical facts, not instructions or an extension - of this repository's public installer permissions. + The flags-3 stock-copy write to `vbmeta_b` and the B-success flag + update at offset `0x35` in `devinfo` were done without project approval. + The run records report the other `devinfo` bytes preserved and read-only + protection restored. Early verification tests restored original + `vbmeta_b`; the later native-root run records retain the B verification + change. No further `devinfo` or `vbmeta` writes will be made without + the maintainer's explicit approval. These are historical facts, not + instructions or an extension of the public installer's permissions. +- **Local deployment tools** [V, recovered October 28 source snapshot]: + `tools/install-phone` is byte-identical to the version at the mobile + base `1155a7c352ed` above. `bin/omamobile` has local changes; its `push` + path adds a `PUSH_MODULES_POLICY=require-match` option, follows image + symlinks for readback length, and uses systemd's reboot on a native root. + The complete two-file comparison against that base is in + [PR #200](https://github.com/derekross/omarchy-mobile/pull/200). + This is a dated source-snapshot comparison, not proof of the exact + script bytes used for every earlier deployment, and not a comparison + against today's main. The recovered Oriole descriptor still allows + only `boot_b vendor_boot_b dtbo_b userdata`; the metadata writes were + separate bring-up operations. - **Slot A and bootloaders** [I, historical run records]: before Linux installation, the matching factory build and full OTA booted stock on B and then A, both reporting `slider-17.0-15681480`. The separate @@ -77,6 +90,36 @@ this audit did not reflash or inspect the phone's current partitions. returning to Android requires deliberate data restoration, not simply switching to slot A. +### Historical B-success write: mechanism and evidence limits + +[V, recovered October 18 source and execution transcript] The separate +`mark-b-success-37.py` wrapper made `devinfo` writable with `blockdev --setrw` +on its containing boot LUN and then the partition. It restored the partition +and then the disk to read-only with an EXIT trap, backed by a 20-second +systemd undo timer and a 120-second watchdog. The wrapper did not stop the +storage watcher or change its allowlist. The recovered init's watcher skipped +nodes already marked in `/run/ufs-ro/`; it did not continuously reassert their +read-only flags. This is how the explicit opening remained possible. + +The helper wrote a **128-byte header**, with only bit 1 at offset `0x35` +changed, followed by comparison of the full 8192-byte record. The gate's +2026-10-18 09:04:51 UTC execution result reports the one-bit change, unchanged +slot-A/opaque bytes, both nodes restored read-only and refreshed backups +verified. This was not a one-byte write. + +The next Fastboot controller completed at 09:06:19 UTC after requiring +`current-slot=b`, `slot-successful:b=yes` and `slot-unbootable:b=no`, without +issuing set-active. The native audit at 09:11:29 UTC reported B success +persisting and A's record unchanged. These are recovered executed assertions +and results; the original Fastboot output and contemporaneous retry count +have not been recovered. + +The original gate's before/after images are listed in the private backup +inventory but are not available locally, and the backup host was unreachable +during this audit. The exact bytes at `0x30`–`0x37` therefore remain unverified +for the original pair. This gap is not filled by deriving bytes from the +helper's logic or from a later backup. No new metadata write was attempted. + ## 2026-10-30: native boot and RTC alarm status - [V] A Pixel 6 booted native Linux from slot B with its root on `userdata`, using the unpublished `7.3.0-rc6-oriole-hsi1-late-dev0-g4bd35d34abb9-dirty` kernel and a separate integration package set. A read-only `phone-smoke --here --json` run passed all required checks: storage guard, root, USB and desktop session. It reported no failed units, oops, BUG or WARN, and 48 existing dmesg error lines; sound, sensors and cameras were skipped. This is a test-phone result, not an installation claim for the public images.