From 28d905c38828fa3def168fa3d9bf7b84cbe16779 Mon Sep 17 00:00:00 2001 From: Nate Crawford Date: Sun, 8 Nov 2026 01:04:57 -0600 Subject: [PATCH 1/3] device-comet 0.1.0: stage the Pixel 9 Pro Fold descriptor and boot policy The first comet submission after issue #143: the descriptor, curated hardware observations, the remaining gates and an inert boot-policy package. Boot-success stays off: the package ships no boot-success script, unit or devinfo writer and enables nothing, and status, install and README agree. SOC_COMPATIBLE stays commented out, as on tegu, so install-phone and flash refuse comet until the public board DTB lands. The storage guard allows only the five slot-B boot images and userdata. NOTES records the 2026-11-07 stock restore (CP3A.261005.005 on both slots), the commands that put Linux back on slot B, the slot-B marking and the fresh protected backup, and marks the 2026-10-30 slot-state paragraphs as historical. BRINGUP-M1 writes out both recovery procedures as fastboot commands now that slot A is a live stock fallback. The package starts at 0.1.0. It no longer depends on omamobile-shell and the descriptor drops MONITOR_SCALE (the panel-size scale is #635's job). The AoC blacklist names the modules the comet zumapro kernel builds, not gs201's. reboot-to.c follows cheetah's current copy. Co-Authored-By: Claude Opus 5.5 --- device/comet/BRINGUP-M1.md | 98 +++++++ device/comet/NOTES.md | 242 ++++++++++++++++++ device/comet/comet-m1-overlay.dts | 20 ++ device/comet/device.conf | 60 +++++ device/comet/kernel.config | 4 + docs/DEVICES.md | 3 +- packages/omamobile-device-comet/LICENSE | 21 ++ packages/omamobile-device-comet/PKGBUILD | 27 ++ packages/omamobile-device-comet/README.md | 39 +++ packages/omamobile-device-comet/build | 8 + packages/omamobile-device-comet/device.conf | 60 +++++ .../etc/omamobile-mirrorlist | 18 ++ packages/omamobile-device-comet/install | 19 ++ .../omamobile-device-comet.install | 62 +++++ .../omamobile-device-comet/src/reboot-to.c | 118 +++++++++ packages/omamobile-device-comet/status | 8 + packages/omamobile-device-comet/test/all | 39 +++ .../conf.d/10-omamobile-usb.conf | 5 + .../modprobe.d/omamobile-comet-aoc.conf | 20 ++ .../logind.conf.d/10-omamobile-lid.conf | 8 + .../logind.conf.d/10-omamobile-power-key.conf | 7 + .../systemd/network/20-usb-gadget.network | 22 ++ .../10-omamobile-reboot-watchdog.conf | 7 + .../udev/rules.d/10-omamobile-storage.rules | 8 + packages/omamobile-device-comet/version | 1 + 25 files changed, 923 insertions(+), 1 deletion(-) create mode 100644 device/comet/BRINGUP-M1.md create mode 100644 device/comet/NOTES.md create mode 100644 device/comet/comet-m1-overlay.dts create mode 100644 device/comet/device.conf create mode 100644 device/comet/kernel.config create mode 100644 packages/omamobile-device-comet/LICENSE create mode 100644 packages/omamobile-device-comet/PKGBUILD create mode 100644 packages/omamobile-device-comet/README.md create mode 100755 packages/omamobile-device-comet/build create mode 100644 packages/omamobile-device-comet/device.conf create mode 100644 packages/omamobile-device-comet/etc/omamobile-mirrorlist create mode 100755 packages/omamobile-device-comet/install create mode 100644 packages/omamobile-device-comet/omamobile-device-comet.install create mode 100644 packages/omamobile-device-comet/src/reboot-to.c create mode 100644 packages/omamobile-device-comet/status create mode 100755 packages/omamobile-device-comet/test/all create mode 100644 packages/omamobile-device-comet/vendor/NetworkManager/conf.d/10-omamobile-usb.conf create mode 100644 packages/omamobile-device-comet/vendor/modprobe.d/omamobile-comet-aoc.conf create mode 100644 packages/omamobile-device-comet/vendor/systemd/logind.conf.d/10-omamobile-lid.conf create mode 100644 packages/omamobile-device-comet/vendor/systemd/logind.conf.d/10-omamobile-power-key.conf create mode 100644 packages/omamobile-device-comet/vendor/systemd/network/20-usb-gadget.network create mode 100644 packages/omamobile-device-comet/vendor/systemd/system.conf.d/10-omamobile-reboot-watchdog.conf create mode 100644 packages/omamobile-device-comet/vendor/udev/rules.d/10-omamobile-storage.rules create mode 100644 packages/omamobile-device-comet/version diff --git a/device/comet/BRINGUP-M1.md b/device/comet/BRINGUP-M1.md new file mode 100644 index 000000000..d88888389 --- /dev/null +++ b/device/comet/BRINGUP-M1.md @@ -0,0 +1,98 @@ + +# Comet first-port gates + +Prepared 2026-11-08 and rebased onto main on 2026-11-17: descriptor and +inert boot policy only. Preparing it contacted no phone; the hardware +history it relies on, from 2026-10-28 on, is in [NOTES.md](NOTES.md) by +date. The comet board DTS (`dt-bindings` commit first, new nodes +disabled) and the USB glue are their own linux-omarchy-mobile pull +requests, linux-omarchy-mobile#273 and #271; this descriptor builds +from public code only once they land. +Kernel #80 is closed, not a merge dependency. A later owner-approved +enablement and qualification is still required. + +The goal is a reviewable descriptor, storage policy and evidence record. +Kernel worktrees and output directories belong to the separate kernel +submission. No kernel was built or phone contacted for this change. + +**Slot state.** Since 2026-11-07 both slots carry stock CP3A.261005.005, +and Linux runs from slot B (NOTES, 2026-11-07/08). Slot A is bootable +stock: a slot B that exhausts its tries falls back to it. + +| Step | Command / action | Expect / Pass | Stop condition | Rollback | Risk | +| --- | --- | --- | --- | --- | --- | +| Offline policy | `tools/pr-check upstream/main` | identifier, blob and script checks pass | any failure | edit or exclude before publication | low | +| Offline package | `tests/packages omamobile-device-comet` | staged descriptor matches; no service wants links; no devinfo writer is staged | any failure | retain prior package; do not install | low | +| Slot read | `fastboot -s getvar current-slot`, `slot-successful:b`, `slot-retry-count:b`, `slot-unbootable:a`, `slot-unbootable:b`, `version-bootloader` | B current, A not unbootable, one bootloader version | any other state | none (read-only) | none | +| Future hardware | No command authorized here | separately agreed runbook, read-only first, fresh protected backups, log stream and watchdog before driver loads, one change per boot | lost transport, refusal or unexpected state | stop; R1 or R2 below with the owner present; no speculative commands | high | + +No `devinfo` write or boot-success enablement is admitted; the +boot-success policy for comet is the maintainer's decision. Keep reboots +few: with B unmarked, each boot spends one of its tries. + +## Recovery procedures + +Both run from fastboot on the laptop, with the owner present and the +owner's go for each write. `` is the phone's serial. Neither +touches slot A, the bootloader, radio, `devinfo`, `persist`, `efs*`, +`modem*` or `vbmeta`, and neither runs an unsuffixed `flash`. +Approval: the owner, in a private working session on 2026-10-30 (R1); +there is no public record, so the procedures are written out here in full +for review. + +### R1: slot B boots but is broken (bad kernel, lost USB) + +Used on 2026-10-30 after the i-touch2 USB loss, through our development +tree's `bin/omamobile flash --keep-active` (not on main), which runs the +`current-slot` check, the five writes and the reboot below. `SET` is the +last saved slot-B set that booted, with its five images and their +checksums; the matching modules must be on the root. + +```sh +# Reach fastboot: Volume Down + Power held about 20 s. +fastboot -s getvar current-slot # must print b; stop otherwise +(cd "$SET" && shasum -a 256 -c SHA256SUMS) # stop on any mismatch +fastboot -s flash boot_b "$SET/boot.img" +fastboot -s flash init_boot_b "$SET/init_boot.img" +fastboot -s flash vendor_boot_b "$SET/vendor_boot.img" +fastboot -s flash vendor_kernel_boot_b "$SET/vendor_kernel_boot.img" +fastboot -s flash dtbo_b "$SET/dtbo.img" +fastboot -s reboot +``` + +No `--set-active`: B is already current. Stop at the first write that +fails and write the set again before any reboot; never boot a half-written +slot B. A fastboot flash may clear B's successful flag, so B then has its +three tries and a failure falls back to stock (R2). + +### R2: slot B exhausted its tries and stock booted on A + +What happened three times on 2026-11-07 (NOTES). + +1. If stock offers a factory data reset or to wipe data, **decline**: it + would erase the Linux root on `userdata`. Power the phone off instead. +2. Reach fastboot (Volume Down + Power about 20 s) and read, without + writing: `fastboot -s getvar current-slot`, then + `slot-successful:b`, `slot-retry-count:b`, `slot-unbootable:b`. +3. If B's images are suspect, run R1's checksum and five `flash ..._b` + lines first, without its `reboot`. +4. With the owner's go (a slot flag write), return to B. This is how B + was reselected after each 2026-11-07 fallback: + + ```sh + fastboot -s --set-active=b + fastboot -s reboot + ``` + +5. On Linux, before any radio, PMIC, AoC or Trusty start: a fresh + read-only backup of `efs`, `efs_backup`, `modem_userdata`, `persist` + and `modem_a/b` (AGENTS.md §1), because stock's modem stack rewrites + them. The 2026-11-07 capture is described in NOTES. + +Stop at any unexpected `getvar` value, any refused or failed write, or a +phone that stops answering; don't guess at its state. A full factory +restore is a separate owner/maintainer decision outside this runbook. + +Results: local preparation only; the package is a curated boot-policy +snapshot, version 0.1.0. Later subsystem startup policies and their +unmerged candidate runbooks are intentionally deferred. diff --git a/device/comet/NOTES.md b/device/comet/NOTES.md new file mode 100644 index 000000000..fa6fba8e9 --- /dev/null +++ b/device/comet/NOTES.md @@ -0,0 +1,242 @@ + +# Pixel 9 Pro Fold (comet) bring-up notes + +This is a curated first-port record for [issue #143](https://github.com/derekross/omarchy-mobile/issues/143). +The results below came from the owner's Comet and private kernels +(`7.3.0-rc6-omamobile-comet-zumapro+` in October, the `comet-rc2-cand*` +series from November), not this PR's build. They establish hardware +observations, not support in the published kernel. Each entry is dated by +the session that produced it. Preparing this PR (first on 2026-10-30, +reworked on 2026-11-08, rebased onto main on 2026-11-17) contacted no phone. + +## 2026-11-07/08: stock restored on both slots, Linux back on slot B + +**What was flashed.** Google's CP3A.261005.005 factory image for comet, +its SHA-256 checked against Google's published value before use. +`flash-all.sh` flashes `bootloader` and `radio` without a slot suffix, so +to the current slot, then runs `fastboot -w update`. It was run twice, +once with each slot current, so both slots carry the same build; the OTA +sideloads first planned for the second slot were not used. The flash log +records these steps and their output (`` is the phone's serial): + +```sh +fastboot -s getvar current-slot # b +./flash-all.sh # writes slot B's set, wipes userdata +fastboot -s --set-active=a +fastboot -s reboot-bootloader +fastboot -s getvar current-slot # a +./flash-all.sh # writes slot A's set +``` + +The flash log shows `bootloader_b` and then `bootloader_a` written from +pack `ripcurrentpro-17.0-16118441`, and `radio` from pack +`g5400c-260604-260807`. Slot lines after the second run (2026-11-07): + +```text +current-slot:a +slot-unbootable:a:no +slot-unbootable:b:no +version-bootloader:ripcurrentpro-17.0-16118441 +``` + +Stock Android then booted on slot A. + +**Slot flags as they read now** (2026-11-17, from Linux, read-only: +`omamobile-bootctl dump` opens `devinfo` `O_RDONLY`, and the partition is +`ro=1` under the storage guard). Read this way rather than in fastboot to +avoid a reboot: + +```text +slot a: active no, successful yes, unbootable no, retry-count 2 +slot b: active yes, successful yes, unbootable no, retry-count 2 +``` + +The bootloader version was not re-read; the 2026-11-07 reading above +stands. + +`getvar` reports the bootloader version of the current slot only. Both +slots were written from the same pack; the installer below read slot A's +version itself and took slot B's from the owner's +`--bootloader-slots-match ripcurrentpro-17.0-16118441`, which rests on +that flash log. + +**How Linux went back onto slot B (2026-11-08 UTC).** `tools/install-phone`, +run from our development tree with a private copy of `device.conf` that +sets the `SOC_COMPATIBLE` selector line kept commented out below and that +pins the private `comet-rc2-cand11` kernel. Main's installer refuses comet +because this descriptor names no selector, and it stays that way. The +installer's plan, with the phone in fastboot on slot A, ran exactly: + +```sh +fastboot -s flash boot_b images/boot.img +fastboot -s flash init_boot_b images/init_boot.img +fastboot -s flash vendor_boot_b images/vendor_boot.img +fastboot -s flash vendor_kernel_boot_b images/vendor_kernel_boot.img +fastboot -s flash dtbo_b images/dtbo.img +fastboot -s flash userdata root.simg +fastboot -s --set-active=b +fastboot -s reboot +``` + +Nothing else was written: no slot A partition, bootloader, radio, +`persist`, `efs`, modem partition or `vbmeta`. `bin/omamobile flash` +was not used for this. (`flash --keep-active`, asked about on this PR, +exists only in our development tree's `bin/omamobile`; it is not on main +and this PR does not add it. Its commands are written out under recovery +procedure R1 in [BRINGUP-M1.md](BRINGUP-M1.md).) + +**First boots.** The new root lacked the watchdog feeder the old install +had carried as a hand-installed file, so it reset about 90 s into each +boot (`CONFIG_WATCHDOG_OPEN_TIMEOUT`). Each reset spent one of slot B's +tries, and ABL fell back to stock on slot A three times, each needing a +button restart. The feeder went into the root image, enabled before +`sysinit`, and later into our development device package (not part of +this PR, which ships boot policy only). + +**Slot B marking.** With the feeder in place, slot B was marked successful +once by hand, with the owner's approval: one `devinfo` byte, the same +helper and before/after images as on 2026-10-29. `omamobile-boot-success` +has stayed **masked** since 2026-11-07 (it was masked on the old install +before the restore and is masked on the new one); this package ships no +writer and enables nothing. No `devinfo` write has been made since: the bytes read on 2026-11-17 +match the post-restore backup (below). + +**devinfo bytes 0x30-0x37.** In the post-restore backup below (image taken +2026-11-07 19:41 CST): `02 1a 00 00 02 16 00 00`. Read again on 2026-11-17 (read-only): `02 1a 00 00 02 16 00 00`, the same. +The layout of these bytes is not decoded here; earlier readings are in the +2026-10-30 entry. + +**Fresh protected backup.** Stock's modem stack rewrote `efs`, `persist`, +`modem_userdata` and `trusty_userdata`, and the factory flash rewrote +`modem_a` and `devinfo`, so the 2026-10-30 checksums no longer apply. +A new read-only capture was taken from a RAM-only hold (every block +device read-only, nothing mounted) before any modem, PMIC, AoC or Trusty +start: `efs`, `efs_backup`, `modem_userdata`, `persist`, `modem_a`, +`modem_b`, `devinfo`, `trusty_persist` and `trusty_userdata`. Each +partition was read twice in phone RAM and hash-checked before it was +copied, and the backup tool's `verify` passed. Rechecked offline on +2026-11-17: all nine laptop images match the manifest and the hashes +computed on the phone (9/9 MATCH). `modem_a` and `modem_b` are identical, +and match the factory image's modem. The images stay off-repo. +Stock booted again on 2026-11-11, so this capture is no longer the +reference. A new read-only capture of the same nine partitions was taken +on 2026-11-14 at 03:29Z on the running Linux system (each partition +`ro=1` and unmounted, read twice on the phone with matching sha256, a +third hash of the laptop copy); that one is current, and also stays +off-repo. + +**Superseded by this entry:** the 2026-10-30 statements that slot A is +unbootable, that ABL has no slot to fall back to, and that recovery means +fastboot by the buttons only. With stock on A, a slot B that exhausts its +tries boots stock; that is what happened three times on 2026-11-07. +The way back is procedure R2 in [BRINGUP-M1.md](BRINGUP-M1.md). + +## 2026-10-30: slot state, devinfo history and the way back (for issue #143) + +*Historical: written while slot A was unbootable. The 2026-11-07/08 entry +above supersedes its slot state and recovery paragraphs.* + +**Slot facts** (`fastboot getvar`; only slot and bootloader lines kept): + +```text +current-slot:b slot-count:2 slot-suffixes:_a,_b +slot-successful:a:yes slot-unbootable:a:yes slot-retry-count:a:2 slot-fastboot-ok:a:yes +slot-successful:b:yes slot-unbootable:b:no slot-retry-count:b:2 slot-fastboot-ok:b:yes +version-bootloader:ripcurrentpro-17.0-16118441 (ABL reports the active slot's only) +``` + +Slot A's bootloader version is not reported by `getvar` and has not been +read; A stays unbootable and is never selected. + +**devinfo writes.** `devinfo` is /dev/sdd1, 8192 bytes, layout 3.15, kept +`ro=1` by the storage guard. `omamobile-boot-success` +(`omamobile-bootctl mark-successful`) wrote it three times, all on 2026-10-29, +lifting the read-only flag only for the write. Each write saved before/after +images in `/var/lib/omamobile/`, and full 8192-byte comparisons of all three +pairs show **exactly one changed byte, 0x35: 0x1c → 0x1e** (slot B +successful). Bytes 0x30-0x37 went from `02 1b 00 00 02 1c 00 00` to +`02 1b 00 00 02 1e 00 00`; the live bytes on 2026-10-30 are still +`02 1b 00 00 02 1e 00 00`. Every later boot found B already successful, and +the unit wrote nothing. + +The writable interval was limited to each helper invocation; an exact +wall-clock duration was not captured. Before-write fastboot slot flag +output is not available in this curated record. The table above is the +2026-10-30 after-state, not a reconstructed before/after getvar comparison. +Those observations were not reconstructed. The maintainer accepted the +record on issue #143 and requested no further devinfo writes. + +**Paused on 2026-10-30** at the maintainer's request (#143): the unit is +masked on the phone (`systemctl mask omamobile-boot-success`). No further +devinfo write until it is agreed on the issue. Because slot A is unbootable, +ABL has no slot to fall back to. Retry exhaustion on B would land in fastboot +rather than lose the Linux root; on #143 the maintainer agreed that Comet +needed no marking **while slot A was unbootable**. That reasoning ended +with the 2026-11-07 restore, and the boot-success policy for Comet is +now the maintainer's open decision. This is historical slot state, not a +current read. Issue #143 separately +requires stock restoration before modem, PMIC regulator and Trusty storage +stages; this preparation grants no hardware exception. + +**The way back if slot B stops booting.** +- Buttons-only fastboot works on comet: the owner forced fastboot on + 2026-10-30 after the i-touch2 USB loss, and recovery was procedure R1 + in [BRINGUP-M1.md](BRINGUP-M1.md): the five saved slot-B images written + back with `fastboot flash _b`, no slot change; no automatic slot + marking is enabled. +- Stock restoration needs a factory image **CP3A.261005.005 or newer**, + never older, because of anti-rollback. The image on the laptop + (CP2A.260805.005) is older and **must not** be flashed. +- A full factory flash overwrites both slots' bootloader/radio/boot + partitions and wipes userdata (the Linux root). efs/persist/modem are + backed up off-repo and checksum-verified (6/6 MATCH on 2026-10-30). +- **Owner acceptance recorded on issue #143:** until stock is back on a slot, recovery + means fastboot by the buttons. (Stock went back on both slots on + 2026-11-07; see the entry above.) + + +## 2026-10-28 to 2026-10-29: internal root and inner display + +[V, owner's captures] The shared-base kernel booted eight CPUs with +MemTotal 15,873,676 kB. All 28 fixed live firmware ranges were excluded +from the allocator. UFS enumerated 62 partitions behind the storage guard; +only the five slot-B boot images and `userdata` were writable. Arch ran +on `userdata`, grown to 225 GiB. Protected partition backups remained +outside the repository and were checksum-verified before PMIC work. +Both watchdogs were taken over at probe. Warm reboot and watchdog reset +retained ramoops. NCM USB networking and fresh SSH reached the root. +Replug reliability was not qualified. + +[V, owner's captures] The inherited CT3B inner panel displayed the Omarchy +login with gs-decon KMS at about 60 Hz, Panthor and Hyprland rendering. +This was an unpublished display-enabled tree, with zero flip timeouts in +that observation window. It does not establish 120 Hz, brightness control, +DPMS, cover switching or sustained GPU stability. Power and both volume +keys produced evtest events. Earlier inner Goodix probes hung the phone +twice; those hangs and several boot-return failures are unresolved. +Later subsystem experiments are deferred to their own submissions. + +## Descriptor evidence from Comet + +[V, owner's stock captures and factory-image parses] Comet's reported +DTBO index was 14: board ID `0x60606`, revision `0x10000`. The stock +`vendor_kernel_boot` contains four zumapro candidates: product `0x9875`, +major 0, minor 0/1, FOPLP package mode 0 or IPOP mode 1. Their union is +recorded without claiming the retail phone's exact stepping/package. +The cover panel is 1080x2424; the inner is 2076x2152 before mounting transform. + +[V, owner's CP3A.261005.005 parses, 2026-10-28] AOSP avbtool info_image +and verify_image established boot/init_boot footer sizes 67108864 and +8388608 bytes, rollback index 1791158400 and security patch 2026-10-05; +init_boot header v4 carries Android 17.0.0 and patch level 2026-10. +These supersede older factory-reference values. They do not establish +slot A's unread bootloader version or authorize a flash. + +No register address is imported from the Pixel 9a descriptor. In +particular SIMPLEFB_TRIG_CON and BRINGUP_PROBE are absent: no display +MMIO read or write is admitted by this descriptor. Future register values +must be checked against Comet itself with powered/clocked block evidence. +The board kernel and module closure are external dependencies; this +repository change alone cannot build or validate a Comet kernel. + +See [BRINGUP-M1.md](BRINGUP-M1.md) for the remaining gates. diff --git a/device/comet/comet-m1-overlay.dts b/device/comet/comet-m1-overlay.dts new file mode 100644 index 000000000..4b61f0b9a --- /dev/null +++ b/device/comet/comet-m1-overlay.dts @@ -0,0 +1,20 @@ +// SPDX-License-Identifier: GPL-2.0-only +/* + * Empty Pixel 9 Pro Fold board overlay for ABL. The retail MP1.0 board + * selects board_id 0x60606, board_rev 0x10000 (stock dtbo entry 14, + * the phone's dtbo_idx; NOTES.md). Keep hardware description in the + * kernel board DTS. + */ +/dts-v1/; +/plugin/; + +/ { + board_id = <0x60606>; + board_rev = <0x10000>; + + fragment@0 { + target-path = "/"; + __overlay__ { + }; + }; +}; diff --git a/device/comet/device.conf b/device/comet/device.conf new file mode 100644 index 000000000..5f390941c --- /dev/null +++ b/device/comet/device.conf @@ -0,0 +1,60 @@ +# SPDX-License-Identifier: MIT +# Device descriptor: Google Pixel 9 Pro Fold (comet), internal root. +# See NOTES.md. Data only: this is a staged port, not an installable +# release. +CODENAME=comet +NAME="Pixel 9 Pro Fold" +SOC=zumapro +COMPATIBLE="google,zumapro-comet" +PACKAGE=omamobile-device-comet + +# The PMIC variant is flattened into the board DTS (the comet kernel PR). +DTB=exynos/google/zumapro-comet.dtb +# Deliberately no SOC_IDS: this loader uses /soc_compatible matching. +# Stock vendor_kernel_boot carries four zumapro DTBs (NOTES.md): +# product_id 0x9875, major 0, minor 0/1, FOPLP (pkg_mode 0) and IPOP +# (pkg_mode 1). The staged common DT carries this verified candidate union; +# this does not identify the retail phone's exact package and stepping. +# SOC_COMPATIBLE="a0-foplp:0x9875:0:0:0 a1-foplp:0x9875:0:1:0 a0-ipop:0x9875:0:0:1 a1-ipop:0x9875:0:1:1" +# Keep both selector keys unset, as tegu does, so install-phone and flash +# refuse comet until the public board DTB lands and the maintainer has +# decided comet's boot-success and recovery policy. Stock CP3A.261005.005 +# is on both slots since 2026-11-07, so slot A is a live fallback +# (BRINGUP-M1.md, R2). +# Do not use a dummy soc_id or borrow another SoC's values to bypass +# the check. Requires the shared-base kernel and BRINGUP-M1.md; +# this is a bring-up configuration, not a supported release. +# Stock boot and init_boot: AOSP avbtool info_image and verify_image, +# CP3A.261005.005 (NOTES.md). Both use the same rollback index. +AVB_FOOTERS="boot:0x4000000 init_boot:0x800000" +AVB_ROLLBACK_INDEX=1791158400 +AVB_SECURITY_PATCH=2026-10-05 + +DTBO_SOURCE=comet-m1-overlay.dts +DTBO_BOARD_ID=0x60606 +DTBO_BOARD_REV=0x10000 +DTB_OVERLAYS="" +VENDOR_CMDLINE="console=tty0 clk_ignore_unused pd_ignore_unused printk.devkmsg=on bootconfig" +VENDOR_PAGESIZE=0x800 +# Stock CP3A.261005.005 init_boot header; check against the build on +# both slots before flashing (CONTRIBUTING.md section 3.1). +OS_VERSION=17.0.0 +OS_PATCH_LEVEL=2026-10 +BOOT_METHOD=android-v4 +BOOT_IMAGES="boot init_boot vendor_boot vendor_kernel_boot dtbo" +UFS_RW="boot_b init_boot_b vendor_boot_b vendor_kernel_boot_b dtbo_b userdata" + +INITRAMFS_INIT=/initramfs/init +# No SIMPLEFB_TRIG_CON: no Comet display register write is admitted, +# and writing the wrong DECON (cover vs inner) is a display fault, not +# a fallback. No BRINGUP_PROBE either: its reads cover every display +# DMA channel, including the inner panel. +# No MONITOR_SCALE: with #635 (open) the shell works the scale out from +# the panel's size, so the descriptor carries none. +PANEL_SIZE=1080x2424 +# Cover panel, portrait (dumpsys display); inner is 2076x2152. + +INITRAMFS_MODULES="exynos-mailbox sec-acpm s2mps11 phy-snps-eusb2 phy-exynos5-usbdrd dwc3-zumapro phy-exynos-ufs ufs-exynos" + +# Require our root label before handing over to userdata. +ROOT_LABEL=omamobile-root diff --git a/device/comet/kernel.config b/device/comet/kernel.config new file mode 100644 index 000000000..b699b1f2b --- /dev/null +++ b/device/comet/kernel.config @@ -0,0 +1,4 @@ +# SPDX-License-Identifier: MIT +# Staged source builds need the separately prepared public Tensor G4 glue. +# This does not enable the board's USB node or qualify a recovery path. +CONFIG_USB_DWC3_ZUMAPRO=m diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 22a8d46a7..4e1fe2754 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -27,6 +27,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | 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)), unmarked by the 10-31 fastboot recovery and marked again on 2026-10-31 during the hold ([record](../device/tegu/NOTES.md#2026-10-31-a-fastboot-flash-of-slot-b-cleared-its-successful-mark-and-b-was-marked-again)), 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, merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96); brightness, DPMS off and on and the 60/120 Hz switch on the boot of [kernel #125](https://github.com/derekross/linux-omarchy-mobile/pull/125), merged, which also checks the panel's ID; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on), [brightness record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | works (Panthor, the desktop renders, runtime suspend when idle; this boot runs at a fixed 160 MHz; the GPU's levels and its thermal zone are merged with [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) ([kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) and [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) landed through it), not yet run from it; [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`, also after a replug the gadget didn't see ([#280](https://github.com/derekross/omarchy-mobile/pull/280); [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)) | works (BCM4383 on PCIe channel 1 through the shared gs201 host and zuma PHY, [kernel #178](https://github.com/derekross/linux-omarchy-mobile/pull/178) on [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156), in review, and brcmfmac, [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; started at boot by `omamobile-device-tegu` 0.2.4 ([#238](https://github.com/derekross/omarchy-mobile/pull/238)) with the extractor's firmware; WPA2 with iwd, kept loaded across sleep by the package's sleep hook; [record](../device/tegu/NOTES.md#2026-11-01-afternoon-and-evening-wi-fi-from-the-package-the-wake-and-the-replug-storage-idle-the-panel-id)) | 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)) | works (the MAX77779 charger binds from the device tree, [kernel #161](https://github.com/derekross/linux-omarchy-mobile/pull/161), merged, built by [#227](https://github.com/derekross/omarchy-mobile/pull/227); the charge limit in `omamobile-device-tegu` 0.2.3 holds charging off at the limit through `charge_behaviour` and lets it run again 5 below; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | 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), merged; [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), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (Omarchy's Location switch serves fixes from GPS, Galileo, BeiDou and GLONASS through the modem's Kepler once the modem is up; `omamobile-device-tegu`'s boot unit, opt-in ([#372](https://github.com/derekross/omarchy-mobile/pull/372)), starts gnssd with the modem: on 2026-11-03, after a reboot with nothing started by hand, a session through the switch's socket had 133 of 135 GGA sentences fixed, first fix 48 s after the client connected, 18 satellites; on 2026-11-09 the same from the in-tree drivers (the GNSS link driver, [kernel #185](https://github.com/derekross/linux-omarchy-mobile/pull/185), and the 9a's GNSS nodes, [kernel #237](https://github.com/derekross/linux-omarchy-mobile/pull/237), the `modem-cpif` overlay with the driver's config line, [#594](https://github.com/derekross/omarchy-mobile/pull/594), and the PCIe PHY's config line, [#274](https://github.com/derekross/omarchy-mobile/pull/274), all merged): four 150 s sessions, 497 of 507 GGA sentences fixed, up to 24 satellites; a 30-minute session on 2026-11-01 (omamobile-gnss 0.2.5's start, by hand, the modem link left to cycle) had 1763 of 1765, first fix 37 s, and a session in a moving car from [#114](https://github.com/derekross/omarchy-mobile/pull/114)'s package build fixed 145 of 153 times; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150) and the PERIC0 clock fix [kernel #172](https://github.com/derekross/linux-omarchy-mobile/pull/172), both merged (without the latter the modem link hung the palmtop within minutes); not on by default because the modem isn't (the Modem cell); [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/TELEPHONY-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | works (audio and sensor DSP through the GSA and Trusty, 93 services, started at boot by `omamobile-device-tegu` 0.2.3 from the device tree, [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162) in review; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (the TAS2572 amplifiers and the microphone through the AoC card and PipeWire, at boot with the AoC: a tone from the speaker, the microphone at -32 dBFS; speakers at a -10 dB ceiling; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (accelerometer, light, proximity, compass and gyroscope through the AoC and the sensor proxy, at boot with the AoC; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (opt-in) (calls in and out on the speakerphone, texts both ways, mobile data over the device `omamobile-sit-data` finds, with the Phone and Messages apps on the bridge ([#356](https://github.com/derekross/omarchy-mobile/pull/356), [#364](https://github.com/derekross/omarchy-mobile/pull/364), [#367](https://github.com/derekross/omarchy-mobile/pull/367), [#371](https://github.com/derekross/omarchy-mobile/pull/371)); `omamobile-device-tegu`'s boot unit starts the modem, the phone service and the bridge at boot when the owner enables it ([#372](https://github.com/derekross/omarchy-mobile/pull/372)), and is skipped on a phone that isn't provisioned or has no CP drivers; opt-in, not on by default, while marking slot B on the 9a is on hold ([#483](https://github.com/derekross/omarchy-mobile/pull/483)): with B unmarked a reset spends one of ABL's three tries, and the unit can't tell; it ran by itself on the owner's palmtop over a day of reboots on 2026-11-09 with 42 of 43 stops confirmed, one unexplained ([record](../device/tegu/TELEPHONY-PLAN.md#29-the-in-tree-drivers-through-the-starter-on-the-published-tip-plus-four-open-changes-2026-11-09)), and the NV partitions unchanged, on the owner's kernel with the bring-up modules, and on the in-tree drivers ([kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187) and [kernel #162](https://github.com/derekross/linux-omarchy-mobile/pull/162), merged), which need the `modem-cpif` overlay and the GNSS link driver's config line ([#594](https://github.com/derekross/omarchy-mobile/pull/594)) and the PCIe PHY's config line ([#274](https://github.com/derekross/omarchy-mobile/pull/274)), all merged; on the published branch (derek/omamobile 26867fc4e) the palmtop hung awake twice on 2026-11-16 at a power-up of the modem's link, once between the sleeps of a series and once in everyday use with Wi-Fi connected, with no oops and no UFS line, cause open ([record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); the far end still hears an echo on the speakerphone ([#378](https://github.com/derekross/omarchy-mobile/pull/378)) and there's no earpiece route yet; [plan](../device/tegu/MODEM-PLAN.md), [record](../device/tegu/MODEM-PLAN.md#sim-test-results-2026-11-02-730-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty)) | works (NXP ST54L through nxp-nci, its clock pad from the PMU ([kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) and [kernel #105](https://github.com/derekross/linux-omarchy-mobile/pull/105), merged, with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged), loaded at boot by `omamobile-device-tegu` 0.2.3 with neard and the link opener: polls with no I2C errors and read a payment card; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | works (main, ultrawide and front from the device tree, [kernel #164](https://github.com/derekross/linux-omarchy-mobile/pull/164) in review, with [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) and [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review: their drivers load at boot with nothing by hand, libcamera lists all three, and each streams, main at 19 fps and the others at 30 fps at 1280x960; basic picture quality through libcamera's software ISP; [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel); the main camera's contrast autofocus through its LC898129 ([kernel #213](https://github.com/derekross/linux-omarchy-mobile/pull/213) in review, and a lens node on top of kernel #164, not yet in a pull request; libcamera 0.7.2-4.23), close subjects checked, the far end not yet ([notes](../device/tegu/NOTES.md#2026-11-07-the-main-cameras-autofocus-lc898129))) | works (opt-in) (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on; opt-in, not on by default: `omamobile-device-tegu` doesn't install the file that turns auto-sleep on for a phone (`/usr/share/omamobile/auto-sleep-default`, [#737](https://github.com/derekross/omarchy-mobile/pull/737)) yet; the power key lights the lock screen on the first press, and the RTC wakes it ([kernel #236](https://github.com/derekross/linux-omarchy-mobile/pull/236), merged 2026-11-10); the three ways a wake failed are fixed on the published branch (kernel-2026.11.15 has the first two; kernel #247 comes with the next release): dead storage after a wake (the UFS pads came back as plain inputs; [kernel #224](https://github.com/derekross/linux-omarchy-mobile/pull/224), merged 2026-11-12, re-applies the pin state at resume), a silent no-wake with C2 entered through s2idle's own path ([#591](https://github.com/derekross/omarchy-mobile/pull/591)'s sleep hook), and a core locked up in the noirq resume of an HSI0 USI ([kernel #247](https://github.com/derekross/linux-omarchy-mobile/pull/247), merged 2026-11-15, keeps those clocks on: 300 of 300 on the published tip with it, 2026-11-13); on the published branch as it is (derek/omamobile 26867fc4e, with kernel #224 and #247, and #232 and #258 for the modem) 300 of 300 sleeps with a 60 s alarm woke with the modem off, 296 on the alarm and 4 within seconds on the touchscreen's interrupt with nobody at the palmtop (the night of 2026-11-17, [plan](../device/tegu/SLEEP-PLAN.md) S1), and 86 of 86 sleeps entered with the modem up woke, each ended by the modem within 29 s, so none of those reached its alarm, with the modem ONLINE and mobile data back after every one (2026-11-16, [record](../device/tegu/MODEM-PLAN.md#suspend-with-the-modem-on-on-the-published-branch-every-sleep-woke-with-data-back-and-the-palmtop-hangs-awake-at-a-link-power-up-2026-11-16)); a new sleep test still runs attended first, and with the modem up the modem's sleep inhibitor stays, the owner's palmtop under [#809](https://github.com/derekross/omarchy-mobile/issues/809) excepted (AGENTS.md); that day the palmtop also hung twice while awake at a power-up of the modem's link, which is in the Modem cell; the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [plan](../device/tegu/SLEEP-PLAN.md) S1, [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (opt-in) (enrolls, matches, refuses other fingers and unlocks the lock screen through Trusty and `omamobile-fingerprint`, 2026-10-29; the sensor binds from the device tree, [kernel #165](https://github.com/derekross/linux-omarchy-mobile/pull/165) in review, with [kernel #126](https://github.com/derekross/linux-omarchy-mobile/pull/126), merged; opt-in as on the 7 Pro, because the service's first run writes Trusty's secure storage; [plan](../device/tegu/FINGERPRINT-PLAN.md), [record](../device/tegu/NOTES.md#2026-10-31-and-11-01-every-testing-row-on-a-published-style-kernel)) | +| Pixel 9 Pro Fold ([notes](../device/comet/NOTES.md)) | comet | zumapro (Tensor G4) | WIP (private kernel; slot-B root, stock CP3A.261005.005 on both slots since 2026-11-07, boot-success off; [notes](../device/comet/NOTES.md)) | WIP (guarded UFS, userdata root; [notes](../device/comet/NOTES.md)) | WIP (inner login at about 60 Hz; [notes](../device/comet/NOTES.md)) | WIP (Panthor/Hyprland; [notes](../device/comet/NOTES.md)) | no (not qualified in this PR) | WIP (three keys in evtest; [notes](../device/comet/NOTES.md)) | WIP (NCM/SSH; replug unqualified; [notes](../device/comet/NOTES.md)) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | | Pixel 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B; from 2026-11-01 to 2026-11-07 a local unit marked slot B on Lef's phone; stopped pending [#252](https://github.com/derekross/omarchy-mobile/issues/252); Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | works (gs-decon, DSIM0 and the HK3 panel at 120 Hz with brightness, merged, [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160), started by the device package, [#228](https://github.com/derekross/omarchy-mobile/pull/228); [notes](../device/husky/NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)) | works (panthor on the Mali-G715 with the ACPM GPU clock and a thermal zone, merged, [kernel #157](https://github.com/derekross/linux-omarchy-mobile/pull/157) with [#158](https://github.com/derekross/linux-omarchy-mobile/pull/158); [notes](../device/husky/NOTES.md#2026-11-13-display-gpu-and-cpu-dvfs-on-merged-omamobile)) | works (ST FTM5 over SPI, merged, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-31-the-touchscreen)) | works (power and volume through `gpio-keys`, merged, [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148); verified on both phones, [notes](../device/husky/NOTES.md#2026-10-30-the-buttons)) | testing (USB and SSH) | partial (BCM4398 on PCIe, merged through [kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); no P2P, and reloading after a firmware crash is untested, [NOTES](../device/husky/NOTES.md#2026-10-31-wi-fi)) | works (BCM4398D0 on the APM UART, merged, [kernel #199](https://github.com/derekross/linux-omarchy-mobile/pull/199); firmware from the owner's image, [#722](https://github.com/derekross/omarchy-mobile/pull/722); pairing and A2DP verified on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone)) | partial (the gauge, temperature, MFD and pack EEPROM, merged, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163), [#175](https://github.com/derekross/linux-omarchy-mobile/pull/175), the bus on by default with [kernel #205](https://github.com/derekross/linux-omarchy-mobile/pull/205), read at boot on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone); no battery model in the published tree, so the percentage is the gauge's default (Google's ATL model only through a bring-up overlay); [BATTERY-NOTES](../device/husky/BATTERY-NOTES.md)) | testing (the charger driver and `tcpci_maxim` as a sink, by hand under a dead-man tool: sink at the Type-C 3 A level (input limit 0xc2 0x13 to 0x77); +1.5 A measured from a 30 W charger without the driver (1.485 A is the device-tree cap); no host mode, [#282](https://github.com/derekross/omarchy-mobile/pull/282); [notes](../device/husky/BATTERY-NOTES.md), [#1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6562547503)) | works (CS40L26, merged, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200); firmware from the owner's image, [#722](https://github.com/derekross/omarchy-mobile/pull/722); felt on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone)) | works (LM3644, 50 mA cap, merged, [kernel #200](https://github.com/derekross/linux-omarchy-mobile/pull/200); seen on the third phone, [notes](../device/husky/NOTES.md#2026-11-15-bluetooth-haptics-the-torch-and-the-gauge-on-merged-omamobile-a-third-phone)) | no (first steps as drafts: [kernel #210](https://github.com/derekross/linux-omarchy-mobile/pull/210), [#211](https://github.com/derekross/linux-omarchy-mobile/pull/211)) | testing (loads and runs through the GSA and Trusty on a test kernel; plan and results [AOC-PLAN](../device/husky/AOC-PLAN.md)) | testing (stereo speakers and one microphone through UCM2 and PipeWire on a test kernel, [kernel #203](https://github.com/derekross/linux-omarchy-mobile/pull/203), [#204](https://github.com/derekross/linux-omarchy-mobile/pull/204), package [#453](https://github.com/derekross/omarchy-mobile/pull/453)) | no | no | testing (a test kernel reads tags; [kernel #208](https://github.com/derekross/linux-omarchy-mobile/pull/208), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209)) | no | no | no | | Pixel 8a ([notes](../device/akita/NOTES.md)) | akita | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B boots Omarchy's root image from `userdata` with the session and the lock, and a second boot comes up clean, [BRINGUP-M2](../device/akita/BRINGUP-M2.md) gate (e), 2026-11-10; `reboot-to bootloader` reaches fastboot; the first-light board file is merged, [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [BRINGUP-M1](../device/akita/BRINGUP-M1.md)) | testing (UFS at HS-G4 behind the storage guard, Omarchy's image on `userdata`; merged, [kernel #206](https://github.com/derekross/linux-omarchy-mobile/pull/206) and the device package and storage plan, [#456](https://github.com/derekross/omarchy-mobile/pull/456)) | WIP (simple-framebuffer: the boot console over Omarchy's splash; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192); [notes](../device/akita/NOTES.md#2026-11-03-first-light-m13-and-the-console-m14)) | no | testing (the GT9895 touchscreen: the PIN pad unlocks by touch, and the shell and on-screen keyboard work by hand, [BRINGUP-M3](../device/akita/BRINGUP-M3.md) gate (g), 2026-11-11; merged, [kernel #241](https://github.com/derekross/linux-omarchy-mobile/pull/241)) | testing (Power wakes and locks, volume keys; [BRINGUP-M3](../device/akita/BRINGUP-M3.md) gate (f); merged, [kernel #238](https://github.com/derekross/linux-omarchy-mobile/pull/238)) | testing (USB and SSH from the initramfs; merged with [kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192)) | no | no | no | no | no | no | no | no | no | no | no | no | no | no | no | | Pixel 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; `boot` and `init_boot` carry AVB footers, which a phone whose `vbmeta_b` is stock's needs to start slot B (device-panther 0.1.6, [#396](https://github.com/derekross/omarchy-mobile/pull/396), [notes](../device/panther/NOTES.md#2026-11-02-avb-footers-on-boot-and-init_boot)); `reboot-to bootloader` reaches fastboot with `reboot=warm`, merged, [kernel #198](https://github.com/derekross/linux-omarchy-mobile/pull/198); [BRINGUP-M1](../device/panther/BRINGUP-M1.md); board file merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (UFS behind the read-only guard; Arch on `userdata`; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | WIP (simple-framebuffer: console and the Hyprland desktop; brightness and display off/on over DCS through the S6E3FC3 panel driver and device-panther 0.1.4, merged, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177); [DISPLAY-PLAN](../device/panther/DISPLAY-PLAN.md)) | testing (Panthor on the Mali-G710; Hyprland renders on it; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the always-on rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | WIP (FocalTech FT3658: touches drive Hyprland and unlock the PIN screen on a test kernel; the driver, [kernel #109](https://github.com/derekross/linux-omarchy-mobile/pull/109), and the touch node, [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), are merged; stock's interrupt pull-up and CS delay, [kernel #166](https://github.com/derekross/linux-omarchy-mobile/pull/166), the driver's review fixes, [kernel #133](https://github.com/derekross/linux-omarchy-mobile/pull/133), and the kernel option with the touch notes, [#149](https://github.com/derekross/omarchy-mobile/pull/149), are merged) | testing (gpio-keys: power, volume; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (USB and SSH; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108); a replug comes back through `omamobile-usb-rescue` in device-panther 0.1.3, on the MAX77759's I2C bus, merged, [kernel #167](https://github.com/derekross/linux-omarchy-mobile/pull/167); [notes](../device/panther/NOTES.md#2026-10-29-usb-comes-back-after-a-replug-u1)) | no | testing (BCM4389 on the APM UART through hci_bcm with the phone's own patch, merged, [kernel #196](https://github.com/derekross/linux-omarchy-mobile/pull/196): a BLE mouse drives the shell, and headphones play over A2DP with their AVRCP buttons, on its author's Pixel 7; the Bluetooth address and the rest of the package side aren't merged yet; headset calls, suspend and power not tested) | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; merged, [kernel #171](https://github.com/derekross/linux-omarchy-mobile/pull/171) and the driver fix [#170](https://github.com/derekross/linux-omarchy-mobile/pull/170); a second unit's Lishen pack isn't matched by that model yet, [notes](../device/panther/NOTES.md#2026-11-03-a-second-unit-angelrenefm); [BATTERY-PLAN](../device/panther/BATTERY-PLAN.md)) | no | testing (CS40L26 with the phone's own firmware, `tools/extract-vendor-firmware -d panther`; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the feedbackd rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | testing (LM3644 rear flash, 36 steps, from the node merged in [kernel #197](https://github.com/derekross/linux-omarchy-mobile/pull/197) and the bring-up overlay `torch.dtso`, [#426](https://github.com/derekross/omarchy-mobile/pull/426): lit on a second Pixel 7; the quick-settings tile not checked) | no | no | no | no | no | no | no (the package's camera start and DMA heap rule are merged, device-panther 0.1.9, [#443](https://github.com/derekross/omarchy-mobile/pull/443), inert until the camera device tree is proposed) | no (s2idle by default since [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134) and device-panther 0.1.1; not run yet) | WIP (the sensor's node, disabled, is merged, [kernel #207](https://github.com/derekross/linux-omarchy-mobile/pull/207); with a bring-up overlay and the package side, which is in review ([#458](https://github.com/derekross/omarchy-mobile/pull/458)), a finger enrolled and unlocked its author's Pixel 7, also after a reboot) | @@ -74,7 +75,7 @@ Devices we'd like to support, with the closest starting point. Open an issue to | Pixel 6 Pro | raven | gs101 | upstream mainline `gs101-raven.dts`; shares oriole's port ([#2](https://github.com/derekross/omarchy-mobile/issues/2)). Boots our kernel from slot B to Omarchy's Hyprland on the Mali-G78 ([kernel #2](https://github.com/derekross/linux-omarchy-mobile/pull/2), [#3](https://github.com/derekross/linux-omarchy-mobile/pull/3)); its device package and plans ([#41](https://github.com/derekross/omarchy-mobile/pull/41)) and provisioning tools ([#22](https://github.com/derekross/omarchy-mobile/pull/22)) are merged | | Pixel 6a | bluejay | gs101 | **WIP, community port: [#348](https://github.com/derekross/omarchy-mobile/issues/348)**; persistent Arch/Omarchy desktop on a development kernel ([notes](../device/bluejay/NOTES.md)); polling touch ([kernel #229](https://github.com/derekross/linux-omarchy-mobile/pull/229)), station Wi-Fi ([#227](https://github.com/derekross/linux-omarchy-mobile/pull/227), [#228](https://github.com/derekross/linux-omarchy-mobile/pull/228), [#230](https://github.com/derekross/linux-omarchy-mobile/pull/230)) and Panfrost GPU are development-kernel results, not release support; display is retained simpledrm, native panel modesetting unqualified; source/reproduction limits in [UPSTREAM](../device/bluejay/UPSTREAM.md) | | Pixel 8, 8 Pro, 8a | shiba, husky, akita | zuma (Tensor G3) | **WIP, community port: [#1](https://github.com/derekross/omarchy-mobile/issues/1)**. 8 Pro (husky): WIP, in the matrix above; its device package and UFS plan are merged ([#42](https://github.com/derekross/omarchy-mobile/pull/42)), and its bootloader picks the base DTB by `/soc_compatible`, not `/soc_id`. 8a (akita): stage 0 stock facts and a descriptor from a retail phone ([notes](../device/akita/NOTES.md)); this phone's bootloader picks the IPOP base DTB where husky's picks FOPLP. WIP, in the matrix above: the first-light board file is merged ([kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192)) and boots from slot B with USB networking, SSH and the framebuffer console ([BRINGUP-M1](../device/akita/BRINGUP-M1.md)); UFS is merged too ([kernel #206](https://github.com/derekross/linux-omarchy-mobile/pull/206)), and the device package with its storage plan is in review ([#456](https://github.com/derekross/omarchy-mobile/pull/456)) | -| Pixel 9 family | tokay, caiman, komodo, comet, tegu | zumapro (Tensor G4) | 9a (tegu): in the matrix above; its SoC and board device tree is merged ([kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81)), with the rest of its kernel work merging into linux-omarchy-mobile; tracking [#28](https://github.com/derekross/omarchy-mobile/issues/28) | +| Pixel 9 family | tokay, caiman, komodo, comet, tegu | zumapro (Tensor G4) | 9a (tegu): in the matrix above; its SoC and board device tree is merged ([kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81)), with the rest of its kernel work merging into linux-omarchy-mobile; tracking [#28](https://github.com/derekross/omarchy-mobile/issues/28); 9 Pro Fold (comet): staged, in the matrix above, tracking [#143](https://github.com/derekross/omarchy-mobile/issues/143) | | Pixel 10 family | mustang (10 Pro XL) | laguna (Tensor G5) | 10 Pro XL (mustang): stage 0 stock facts ([notes](../device/mustang/NOTES.md)), contributors welcome ([#18](https://github.com/derekross/omarchy-mobile/issues/18)) | | Pixel 11 Pro, 11 Pro XL, 11 Pro Fold | grizzly, kodiak, yogi | malibu (Tensor G6) | stock facts, contributors welcome: 11 Pro ([#26](https://github.com/derekross/omarchy-mobile/issues/26)), 11 Pro XL ([#199](https://github.com/derekross/omarchy-mobile/issues/199), [notes](../device/kodiak/NOTES.md)), 11 Pro Fold ([#40](https://github.com/derekross/omarchy-mobile/issues/40)) | | Pixel 4 | flame | SM8150 (Snapdragon 855) | **WIP, community port**, in the matrix above: the RAM-only first-light probe is merged ([BRINGUP-M1](../device/flame/BRINGUP-M1.md)); the native install is in review, split out of [#17](https://github.com/derekross/omarchy-mobile/pull/17) into [#55](https://github.com/derekross/omarchy-mobile/pull/55), [#56](https://github.com/derekross/omarchy-mobile/pull/56), [#58](https://github.com/derekross/omarchy-mobile/pull/58) and [#59](https://github.com/derekross/omarchy-mobile/pull/59) | diff --git a/packages/omamobile-device-comet/LICENSE b/packages/omamobile-device-comet/LICENSE new file mode 100644 index 000000000..f407f722f --- /dev/null +++ b/packages/omamobile-device-comet/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2026 Derek Ross and Omarchy Mobile contributors + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/packages/omamobile-device-comet/PKGBUILD b/packages/omamobile-device-comet/PKGBUILD new file mode 100644 index 000000000..f59acad7a --- /dev/null +++ b/packages/omamobile-device-comet/PKGBUILD @@ -0,0 +1,27 @@ +# SPDX-License-Identifier: MIT +pkgname=omamobile-device-comet +pkgver=$(cat "${startdir:-.}/version") +pkgrel=1 +pkgdesc="Omarchy Mobile boot policy for the Google Pixel 9 Pro Fold (comet): storage guard, USB networking, reboot-to" +arch=(aarch64) +url="https://github.com/derekross/omarchy-mobile" +license=(MIT) +depends=(bash coreutils grep sed systemd util-linux kmod omamobile-keyring) +provides=(omamobile-device) +conflicts=(omamobile-device) +backup=(etc/pacman.d/omamobile-mirrorlist) +install=omamobile-device-comet.install +makedepends=(gcc) +checkdepends=(python) + +build() { + "$startdir/build" "$srcdir/build" +} + +check() { + "$startdir/test/all" +} + +package() { + "$startdir/install" "$pkgdir" "$srcdir/build" +} diff --git a/packages/omamobile-device-comet/README.md b/packages/omamobile-device-comet/README.md new file mode 100644 index 000000000..96e34a898 --- /dev/null +++ b/packages/omamobile-device-comet/README.md @@ -0,0 +1,39 @@ + +# omamobile-device-comet 0.1.0 + +Staged boot policy for the Pixel 9 Pro Fold (comet, Tensor G4 / zumapro). +This is not a supported install profile. The descriptor needs the separate +public Comet board DTS and USB glue before it can build from upstream. +The per-device build fragment selects that glue as a module; it does not +enable USB in the board DTS. Release builds exclude per-device fragments, +and this candidate is not a release-build profile. The separately prepared +board subset leaves USB disabled and needs its own attended qualification. + +The package installs the descriptor, reboot-to, USB networking at metric +2000, storage-hiding udev rules, power-key/lid logind policy, shutdown watchdog +configuration, an AoC module blacklist and the repository mirrorlist hook. +The initramfs storage guard, not the udev rule, enforces read-only storage. +Shared network, mirrorlist, hook and reboot-to files follow current main. +The package ships nothing the shell reads and does not depend on +`omamobile-shell`. The descriptor sets no MONITOR_SCALE: with #635 (open) +the shell works the scale out from the panel's size. The AoC blacklist names +the modules the comet zumapro kernel builds. + +## Boot-success disabled + +BOOT_SUCCESS=disabled in status, and install creates no service wants links. +No boot-success script, unit or devinfo writer is shipped. This keeps the +maintainer's [issue #143](https://github.com/derekross/omarchy-mobile/issues/143) +hold in force. Existing owner-installed scripts or service links are outside +this package: the owner must keep the reported mask in place. Installing or +upgrading this candidate does not remove administrator-created files. + +Daily hardware startup, display/touch rules, AoC firmware loading, modem, +charging, trial-kernel writes and automatic slot marking remain separate +work. No binary firmware, calibration or boot image is included. + +Run ./build [DIR], ./install DESTDIR [DIR], and test/all offline. +The tests compile reboot-to without executing it, stage the package, check +the allowlist and assert that neither service enablement nor a devinfo writer +is present. They do not establish phone behavior. Historical private-kernel +observations and recovery limitations are recorded in device/comet/NOTES.md. diff --git a/packages/omamobile-device-comet/build b/packages/omamobile-device-comet/build new file mode 100755 index 000000000..f1d93f8cd --- /dev/null +++ b/packages/omamobile-device-comet/build @@ -0,0 +1,8 @@ +#!/bin/bash +# SPDX-License-Identifier: MIT +# Compile the C tools into BUILDDIR (default: build). +set -euo pipefail +cd -- "$(dirname -- "${BASH_SOURCE[0]}")" +out=${1:-build} +mkdir -p "$out" +${CC:-cc} ${CFLAGS:--O2} -Wall -Wextra -o "$out/reboot-to" src/reboot-to.c ${LDFLAGS:-} diff --git a/packages/omamobile-device-comet/device.conf b/packages/omamobile-device-comet/device.conf new file mode 100644 index 000000000..5f390941c --- /dev/null +++ b/packages/omamobile-device-comet/device.conf @@ -0,0 +1,60 @@ +# SPDX-License-Identifier: MIT +# Device descriptor: Google Pixel 9 Pro Fold (comet), internal root. +# See NOTES.md. Data only: this is a staged port, not an installable +# release. +CODENAME=comet +NAME="Pixel 9 Pro Fold" +SOC=zumapro +COMPATIBLE="google,zumapro-comet" +PACKAGE=omamobile-device-comet + +# The PMIC variant is flattened into the board DTS (the comet kernel PR). +DTB=exynos/google/zumapro-comet.dtb +# Deliberately no SOC_IDS: this loader uses /soc_compatible matching. +# Stock vendor_kernel_boot carries four zumapro DTBs (NOTES.md): +# product_id 0x9875, major 0, minor 0/1, FOPLP (pkg_mode 0) and IPOP +# (pkg_mode 1). The staged common DT carries this verified candidate union; +# this does not identify the retail phone's exact package and stepping. +# SOC_COMPATIBLE="a0-foplp:0x9875:0:0:0 a1-foplp:0x9875:0:1:0 a0-ipop:0x9875:0:0:1 a1-ipop:0x9875:0:1:1" +# Keep both selector keys unset, as tegu does, so install-phone and flash +# refuse comet until the public board DTB lands and the maintainer has +# decided comet's boot-success and recovery policy. Stock CP3A.261005.005 +# is on both slots since 2026-11-07, so slot A is a live fallback +# (BRINGUP-M1.md, R2). +# Do not use a dummy soc_id or borrow another SoC's values to bypass +# the check. Requires the shared-base kernel and BRINGUP-M1.md; +# this is a bring-up configuration, not a supported release. +# Stock boot and init_boot: AOSP avbtool info_image and verify_image, +# CP3A.261005.005 (NOTES.md). Both use the same rollback index. +AVB_FOOTERS="boot:0x4000000 init_boot:0x800000" +AVB_ROLLBACK_INDEX=1791158400 +AVB_SECURITY_PATCH=2026-10-05 + +DTBO_SOURCE=comet-m1-overlay.dts +DTBO_BOARD_ID=0x60606 +DTBO_BOARD_REV=0x10000 +DTB_OVERLAYS="" +VENDOR_CMDLINE="console=tty0 clk_ignore_unused pd_ignore_unused printk.devkmsg=on bootconfig" +VENDOR_PAGESIZE=0x800 +# Stock CP3A.261005.005 init_boot header; check against the build on +# both slots before flashing (CONTRIBUTING.md section 3.1). +OS_VERSION=17.0.0 +OS_PATCH_LEVEL=2026-10 +BOOT_METHOD=android-v4 +BOOT_IMAGES="boot init_boot vendor_boot vendor_kernel_boot dtbo" +UFS_RW="boot_b init_boot_b vendor_boot_b vendor_kernel_boot_b dtbo_b userdata" + +INITRAMFS_INIT=/initramfs/init +# No SIMPLEFB_TRIG_CON: no Comet display register write is admitted, +# and writing the wrong DECON (cover vs inner) is a display fault, not +# a fallback. No BRINGUP_PROBE either: its reads cover every display +# DMA channel, including the inner panel. +# No MONITOR_SCALE: with #635 (open) the shell works the scale out from +# the panel's size, so the descriptor carries none. +PANEL_SIZE=1080x2424 +# Cover panel, portrait (dumpsys display); inner is 2076x2152. + +INITRAMFS_MODULES="exynos-mailbox sec-acpm s2mps11 phy-snps-eusb2 phy-exynos5-usbdrd dwc3-zumapro phy-exynos-ufs ufs-exynos" + +# Require our root label before handing over to userdata. +ROOT_LABEL=omamobile-root diff --git a/packages/omamobile-device-comet/etc/omamobile-mirrorlist b/packages/omamobile-device-comet/etc/omamobile-mirrorlist new file mode 100644 index 000000000..f9be3d0e9 --- /dev/null +++ b/packages/omamobile-device-comet/etc/omamobile-mirrorlist @@ -0,0 +1,18 @@ +# SPDX-License-Identifier: MIT +# Where pacman gets Omarchy Mobile's packages ([omamobile] in /etc/pacman.conf). +# +# The one active Server line is the channel this phone follows: +# stable what has run on the Pixel 7 Pro; phones installed from a +# release follow it +# development every day's build, first; for builders and testers +# local the repository on the phone itself, /var/lib/omamobile/repo, +# filled from a build machine by tools/repo-push +# +# Switch with: sudo omamobile-update channel development (or stable, local) +# See which: omamobile-update check +# +# pacman keeps a changed copy of this file across upgrades (backup= in the +# device package); a new default then arrives as omamobile-mirrorlist.pacnew. +Server = https://pkgs.omamobile.org/stable/$arch +#Server = https://pkgs.omamobile.org/development/$arch +#Server = file:///var/lib/omamobile/repo/$arch diff --git a/packages/omamobile-device-comet/install b/packages/omamobile-device-comet/install new file mode 100755 index 000000000..faa26a0f1 --- /dev/null +++ b/packages/omamobile-device-comet/install @@ -0,0 +1,19 @@ +#!/bin/bash +# SPDX-License-Identifier: MIT +# Stage inert boot policy only. No service enablement or devinfo writer. +set -euo pipefail +cd -- "$(dirname -- "${BASH_SOURCE[0]}")" +destination=${1:?Usage: ./install DESTDIR [BUILDDIR]} +build=${2:-build} +[[ $destination == /* && $destination != / ]] || { echo "Use an absolute staging directory" >&2; exit 1; } +put() { mkdir -p "$(dirname -- "$3")"; install -m "$1" "$2" "$3"; } +put 755 "$build/reboot-to" "$destination/usr/bin/reboot-to" +while IFS= read -r -d '' file; do + put 644 "$file" "$destination/usr/lib/${file#vendor/}" +done < <(find vendor -type f -print0) +put 644 device.conf "$destination/usr/share/omamobile/device.conf" +put 644 etc/omamobile-mirrorlist "$destination/etc/pacman.d/omamobile-mirrorlist" +put 644 LICENSE "$destination/usr/share/licenses/omamobile-device-comet/LICENSE" +for file in version status README.md; do + put 644 "$file" "$destination/usr/share/omamobile/device-comet/$file" +done diff --git a/packages/omamobile-device-comet/omamobile-device-comet.install b/packages/omamobile-device-comet/omamobile-device-comet.install new file mode 100644 index 000000000..96da5786e --- /dev/null +++ b/packages/omamobile-device-comet/omamobile-device-comet.install @@ -0,0 +1,62 @@ +# SPDX-License-Identifier: MIT +# Add the [omamobile] repository to pacman.conf, before [omarchy] so its +# builds (e.g. Mesa with Mali-G710 support) win. Added once; never removed +# automatically, so a user's edits stay. +add_repository() { + local conf=/etc/pacman.conf + grep -q '^\[omamobile\]' "$conf" && return + local entry='[omamobile]\nInclude = /etc/pacman.d/omamobile-mirrorlist\n' + if grep -q '^\[omarchy\]' "$conf"; then + sed -i "0,/^\[omarchy\]/s//${entry//\//\\/}\n[omarchy]/" "$conf" + elif grep -q '^\[core\]' "$conf"; then + sed -i "0,/^\[core\]/s//${entry//\//\\/}\n[core]/" "$conf" + else + printf '\n[omamobile]\nInclude = /etc/pacman.d/omamobile-mirrorlist\n' >>"$conf" + fi +} + +# --- the [omamobile] channel (identical in every device package) --- +# The mirrorlist names the channel (stable, development or local). It is a +# backup= file, so pacman keeps a changed copy; an unchanged one, though, is +# replaced by the new default. Phones from before 2026-11-01 read the +# repository on the phone (file:///var/lib/omamobile/repo, filled by +# tools/repo-push), unchanged, and would silently move to stable: such a phone +# keeps reading its own repository, and is told how to switch. +OMAMOBILE_MIRRORLIST=/etc/pacman.d/omamobile-mirrorlist +OMAMOBILE_LOCAL_MARK=/var/lib/omamobile/.mirrorlist-was-local +OMAMOBILE_LOCAL_SERVER='Server = file:///var/lib/omamobile/repo/$arch' + +remember_local_channel() { + [[ -f $OMAMOBILE_MIRRORLIST ]] || return 0 + if grep -qxF "$OMAMOBILE_LOCAL_SERVER" "$OMAMOBILE_MIRRORLIST"; then + mkdir -p "${OMAMOBILE_LOCAL_MARK%/*}" && : > "$OMAMOBILE_LOCAL_MARK" + fi +} + +keep_local_channel() { + [[ -e $OMAMOBILE_LOCAL_MARK ]] || return 0 + rm -f "$OMAMOBILE_LOCAL_MARK" + [[ -f $OMAMOBILE_MIRRORLIST ]] || return 0 + grep -qxF "$OMAMOBILE_LOCAL_SERVER" "$OMAMOBILE_MIRRORLIST" && return 0 + # Comment out every Server line, then turn the local one back on + sed -i -E 's|^([[:space:]]*Server[[:space:]]*=)|#\1|' "$OMAMOBILE_MIRRORLIST" + sed -i 's|^#Server = file:///var/lib/omamobile/repo/\$arch$|Server = file:///var/lib/omamobile/repo/$arch|' "$OMAMOBILE_MIRRORLIST" + grep -qxF "$OMAMOBILE_LOCAL_SERVER" "$OMAMOBILE_MIRRORLIST" || + printf '%s\n' "$OMAMOBILE_LOCAL_SERVER" >>"$OMAMOBILE_MIRRORLIST" + echo "==> [omamobile] stays on this phone's own repository (/var/lib/omamobile/repo)." + echo " Installed phones follow the stable channel at pkgs.omamobile.org; switch with" + echo " sudo omamobile-update channel stable (or development)" +} + +pre_upgrade() { + remember_local_channel +} + +post_install() { + add_repository +} + +post_upgrade() { + add_repository + keep_local_channel +} diff --git a/packages/omamobile-device-comet/src/reboot-to.c b/packages/omamobile-device-comet/src/reboot-to.c new file mode 100644 index 000000000..bacead54c --- /dev/null +++ b/packages/omamobile-device-comet/src/reboot-to.c @@ -0,0 +1,118 @@ +// SPDX-License-Identifier: MIT +// reboot-to: reboot with a reason the Pixel bootloader understands, +// e.g. "reboot-to bootloader" lands in fastboot. +// The kernel's syscon-reboot-mode driver stores the reason in the PMU +// before the reset; busybox reboot can't pass one. +#include +#include +#include +#include +#include + +/* From (stable ABI); musl's sysroot has no kernel headers */ +#define LINUX_REBOOT_MAGIC1 0xfee1dead +#define LINUX_REBOOT_MAGIC2 672274793 +#define LINUX_REBOOT_CMD_RESTART2 0xA1B2C3D4 + +/* + * The modem's start refuses after a boot that ended with the modem up and + * no clean stop (a hang or a reset). This restart skips systemd's shutdown, + * so it notes the boot it ends, before rebooting: the next start then knows + * this boot ended on purpose. Best effort: without /var/lib/omamobile (the + * initramfs) there is no note, and the start refuses as before. + * + * Only a boot with the modem up writes the note: its marker (the 7 Pro's + * modem-up, the 9a's modem-bringup-started) names this boot. A restart in + * a later boot without the modem would otherwise replace the note, and the + * boot that had the modem up would read as a hang at the next start. + */ +#ifndef NOTE_DIR +#define NOTE_DIR "/var/lib/omamobile" +#endif +#define NOTE NOTE_DIR "/deliberate-restart" + +static int marker_names_boot(const char *path, const char *id) +{ + char buf[512], want[80]; + FILE *f = fopen(path, "r"); + size_t n; + char *p; + + if (!f) + return 0; + n = fread(buf, 1, sizeof(buf) - 1, f); + fclose(f); + buf[n] = '\0'; + /* No printf family here: the initramfs links this file against musl + * without compiler builtins, and musl's vfprintf needs them. */ + strcpy(want, "boot "); + strcat(want, id); + for (p = strstr(buf, want); p; p = strstr(p + 1, want)) { + char end = p[strlen(want)]; + + if (end == '\n' || end == '\0') + return 1; + } + return 0; +} + +static void note_deliberate_restart(void) +{ + char id[64]; + FILE *f = fopen("/proc/sys/kernel/random/boot_id", "r"); + int fd, dir; + + if (!f) + return; + if (!fgets(id, sizeof(id), f)) { + fclose(f); + return; + } + fclose(f); + id[strcspn(id, "\n")] = '\0'; + if (!marker_names_boot(NOTE_DIR "/modem-up", id) && + !marker_names_boot(NOTE_DIR "/modem-bringup-started", id)) + return; + strcat(id, "\n"); + fd = open(NOTE ".new", O_WRONLY | O_CREAT | O_TRUNC | O_CLOEXEC, 0644); + if (fd < 0) + return; + if (write(fd, id, strlen(id)) != (ssize_t)strlen(id) || fsync(fd)) { + close(fd); + unlink(NOTE ".new"); + return; + } + close(fd); + if (rename(NOTE ".new", NOTE)) + return; + dir = open(NOTE_DIR, O_RDONLY | O_DIRECTORY | O_CLOEXEC); + if (dir >= 0) { + fsync(dir); + close(dir); + } +} + +int main(int argc, char **argv) +{ + const char *reason = argc > 1 ? argv[1] : "bootloader"; + + /* An option is never a reason: "--help" or a typo prints the usage and + * reboots nothing, before the note below, so it writes nothing either. + * write(), not the printf family (see marker_names_boot). */ + if (reason[0] == '-') { + static const char usage[] = + "usage: reboot-to [REASON]\n" + "Reboot with REASON (default: bootloader), e.g. bootloader or recovery.\n"; + ssize_t written = write(STDOUT_FILENO, usage, sizeof(usage) - 1); + + (void)written; + return strcmp(reason, "-h") && strcmp(reason, "--help") ? 2 : 0; + } + + note_deliberate_restart(); + sync(); + syscall(SYS_reboot, LINUX_REBOOT_MAGIC1, LINUX_REBOOT_MAGIC2, + LINUX_REBOOT_CMD_RESTART2, reason); + perror("reboot"); + return 1; +} diff --git a/packages/omamobile-device-comet/status b/packages/omamobile-device-comet/status new file mode 100644 index 000000000..43e228a94 --- /dev/null +++ b/packages/omamobile-device-comet/status @@ -0,0 +1,8 @@ +# SPDX-License-Identifier: MIT +SCHEMA=omamobile-device-v1 +CODENAME=comet +PACKAGE=omamobile-device-comet +STATUS=boot-policy +PHYSICAL_SUPPORT=historical-private-kernel-only +INSTALLABLE_PROFILE=no +BOOT_SUCCESS=disabled diff --git a/packages/omamobile-device-comet/test/all b/packages/omamobile-device-comet/test/all new file mode 100755 index 000000000..ebd3960de --- /dev/null +++ b/packages/omamobile-device-comet/test/all @@ -0,0 +1,39 @@ +#!/bin/bash +# SPDX-License-Identifier: MIT +# Build and stage only; no hardware tool is executed. +set -euo pipefail +cd -- "$(dirname -- "${BASH_SOURCE[0]}")/.." +t=$(mktemp -d); trap 'rm -rf "$t"' EXIT +./build "$t/build" +./install "$t/stage" "$t/build" +python3 - "$t/stage" <<'PYTEST' +from pathlib import Path +import sys +stage = Path(sys.argv[1]) +assert (stage / 'usr/bin/reboot-to').is_file() +assert (stage / 'usr/share/omamobile/device.conf').read_bytes() == Path('device.conf').read_bytes() +assert not list(stage.rglob('*.wants')) +assert not list(stage.rglob('omamobile-boot-success*')) +assert not list(stage.rglob('omamobile-bootctl*')) +assert 'BOOT_SUCCESS=disabled' in Path('status').read_text() +conf = dict(line.split('=', 1) for line in Path('device.conf').read_text().splitlines() + if line and not line.startswith('#') and '=' in line) +assert conf['UFS_RW'].strip('"').split() == [ + 'boot_b', 'init_boot_b', 'vendor_boot_b', 'vendor_kernel_boot_b', 'dtbo_b', 'userdata'] +assert conf['INITRAMFS_INIT'] == '/initramfs/init' +assert 'SIMPLEFB_TRIG_CON' not in conf and 'BRINGUP_PROBE' not in conf +assert 'Metric=2000' in (stage / 'usr/lib/systemd/network/20-usb-gadget.network').read_text() +repo_conf = Path('../../device/comet/device.conf') +if repo_conf.exists(): + assert repo_conf.read_bytes() == Path('device.conf').read_bytes() +for name in ['src/reboot-to.c', 'etc/omamobile-mirrorlist', + 'vendor/systemd/network/20-usb-gadget.network', + 'vendor/udev/rules.d/10-omamobile-storage.rules']: + peer = Path('../omamobile-device-cheetah') / name + if peer.exists(): + assert peer.read_bytes() == Path(name).read_bytes(), name +PYTEST +if ./install / "$t/build" >/dev/null 2>&1; then + echo 'not ok - refuses live root as staging directory'; exit 1 +fi +echo 'ok - comet package stages boot policy; boot-success disabled, no writer or enablement' diff --git a/packages/omamobile-device-comet/vendor/NetworkManager/conf.d/10-omamobile-usb.conf b/packages/omamobile-device-comet/vendor/NetworkManager/conf.d/10-omamobile-usb.conf new file mode 100644 index 000000000..252de6e15 --- /dev/null +++ b/packages/omamobile-device-comet/vendor/NetworkManager/conf.d/10-omamobile-usb.conf @@ -0,0 +1,5 @@ +# SPDX-License-Identifier: MIT +# Omarchy Mobile: the USB gadget link to the host (usb0) is configured by +# systemd-networkd; NetworkManager manages everything else (Wi-Fi later). +[keyfile] +unmanaged-devices=interface-name:usb0 diff --git a/packages/omamobile-device-comet/vendor/modprobe.d/omamobile-comet-aoc.conf b/packages/omamobile-device-comet/vendor/modprobe.d/omamobile-comet-aoc.conf new file mode 100644 index 000000000..2f2dee9fe --- /dev/null +++ b/packages/omamobile-device-comet/vendor/modprobe.d/omamobile-comet-aoc.conf @@ -0,0 +1,20 @@ +# SPDX-License-Identifier: MIT +# Offline AoC preparation only: no automatic load, start, or firmware request. +# Explicit modprobe is reserved for an approved AOC-PLAN stage. +# These are the Trusty, GSA, AoC and amplifier modules the comet zumapro +# kernel builds (its AoC/Trusty stack is not in linux-omarchy-mobile yet). +# gs201's AoC module names are not built for zumapro and are not listed. +blacklist trusty +blacklist trusty_log +blacklist trusty_irq +blacklist trusty_ipc +blacklist trusty_virtio +blacklist exynos_gsa +blacklist comet_aoc_s2mpu +blacklist aoc +blacklist aoc_channel +blacklist aoc_usf +blacklist aoc_usf_iio +blacklist aoc_audio +blacklist hci_aoc +blacklist snd_soc_cs35l41_spi diff --git a/packages/omamobile-device-comet/vendor/systemd/logind.conf.d/10-omamobile-lid.conf b/packages/omamobile-device-comet/vendor/systemd/logind.conf.d/10-omamobile-lid.conf new file mode 100644 index 000000000..c59ca2124 --- /dev/null +++ b/packages/omamobile-device-comet/vendor/systemd/logind.conf.d/10-omamobile-lid.conf @@ -0,0 +1,8 @@ +# SPDX-License-Identifier: MIT +# A closed fold must not suspend the phone. The hall switch stays shut, +# and logind would otherwise suspend and retry 30s after every resume, +# which drops the USB gadget. +[Login] +HandleLidSwitch=ignore +HandleLidSwitchDocked=ignore +HandleLidSwitchExternalPower=ignore diff --git a/packages/omamobile-device-comet/vendor/systemd/logind.conf.d/10-omamobile-power-key.conf b/packages/omamobile-device-comet/vendor/systemd/logind.conf.d/10-omamobile-power-key.conf new file mode 100644 index 000000000..a1e2cb0eb --- /dev/null +++ b/packages/omamobile-device-comet/vendor/systemd/logind.conf.d/10-omamobile-power-key.conf @@ -0,0 +1,7 @@ +# SPDX-License-Identifier: MIT +# Omarchy Mobile: a short press of the power button opens Omarchy's system menu +# (bound in Hyprland by omamobile-setup-user), as Super + Escape does, instead +# of powering off. A long press still forces a reset in the PMIC hardware. +[Login] +HandlePowerKey=ignore +HandlePowerKeyLongPress=ignore diff --git a/packages/omamobile-device-comet/vendor/systemd/network/20-usb-gadget.network b/packages/omamobile-device-comet/vendor/systemd/network/20-usb-gadget.network new file mode 100644 index 000000000..973c61db7 --- /dev/null +++ b/packages/omamobile-device-comet/vendor/systemd/network/20-usb-gadget.network @@ -0,0 +1,22 @@ +# SPDX-License-Identifier: MIT +# Omarchy Mobile: USB networking to the host. The initramfs sets up the USB +# gadget (CDC NCM) before handing over to Arch; this gives it an address. +# The host shares its internet over this link (NetworkManager "shared" +# mode on 172.16.42.2), so it is also a gateway, the last one: Wi-Fi (600) +# and mobile data (700) go first. ConfigureWithoutCarrier keeps this route +# after an unplug (and usb0 keeps its carrier anyway), so at metric 0 IPv4 +# went into the dead cable once the phone left the desk: IPv4-only sites +# such as github.com failed on Wi-Fi while IPv6 ones loaded (raven, +# 2026-10-28). DNS goes to public resolvers. +[Match] +Name=usb0 + +[Network] +Address=172.16.42.1/24 +DNS=1.1.1.1 +DNS=9.9.9.9 +ConfigureWithoutCarrier=yes + +[Route] +Gateway=172.16.42.2 +Metric=2000 diff --git a/packages/omamobile-device-comet/vendor/systemd/system.conf.d/10-omamobile-reboot-watchdog.conf b/packages/omamobile-device-comet/vendor/systemd/system.conf.d/10-omamobile-reboot-watchdog.conf new file mode 100644 index 000000000..9764faba8 --- /dev/null +++ b/packages/omamobile-device-comet/vendor/systemd/system.conf.d/10-omamobile-reboot-watchdog.conf @@ -0,0 +1,7 @@ +# SPDX-License-Identifier: MIT +# Omarchy Mobile: if shutdown hangs (a driver stuck in remove(), say), let the +# hardware watchdog reset the phone after a minute instead of leaving it +# on the shutdown splash until someone holds Power. systemd's default is +# 10 minutes. Nothing holds the watchdog while the system runs. +[Manager] +RebootWatchdogSec=1min diff --git a/packages/omamobile-device-comet/vendor/udev/rules.d/10-omamobile-storage.rules b/packages/omamobile-device-comet/vendor/udev/rules.d/10-omamobile-storage.rules new file mode 100644 index 000000000..89c02cf30 --- /dev/null +++ b/packages/omamobile-device-comet/vendor/udev/rules.d/10-omamobile-storage.rules @@ -0,0 +1,8 @@ +# SPDX-License-Identifier: MIT +# Omarchy Mobile storage guard, continued in Arch. The initramfs marks every UFS +# partition read-only except slot B's boot images and userdata, and removes +# the whole-disk node of the main LUN. udev would recreate /dev/sda, so make +# the whole-disk node inaccessible and keep desktop tools from touching any +# Android partition. +SUBSYSTEM=="block", KERNEL=="sda", MODE="0000", ENV{UDISKS_IGNORE}="1" +SUBSYSTEM=="block", KERNEL=="sd[a-d][0-9]*", ENV{ID_PART_ENTRY_NAME}!="userdata", ENV{UDISKS_IGNORE}="1" diff --git a/packages/omamobile-device-comet/version b/packages/omamobile-device-comet/version new file mode 100644 index 000000000..6e8bf73aa --- /dev/null +++ b/packages/omamobile-device-comet/version @@ -0,0 +1 @@ +0.1.0 From edd38aa6ab3983cec30aa4740e79f96fe29e5c71 Mon Sep 17 00:00:00 2001 From: Nate Crawford Date: Wed, 18 Nov 2026 13:20:16 -0600 Subject: [PATCH 2/3] comet notes: record the 11-08 mark in full, correct the 11-11 stock boot Answers the maintainer's 11-18 questions on #203. The slot B mark of 2026-11-08 gets its time (01:25:18Z), what made devinfo writable (the helper's own setrw on sdd and sdd1 around its single bootctl call, set read-only again right after and from an exit trap), the before/after bytes at 0x30-0x37 and the one-byte compare. The post-restore backup (01:28-01:41Z) is recorded as taken after the mark. The earlier text said stock booted again on 2026-11-11. It did not: that night's boots are all Linux on slot B, and the 2026-11-14 capture is byte-identical, devinfo included, to the 2026-11-08 02:32Z one. The entry now says so and places the Fold's first storage start (03:31:11Z) after the 03:29:09Z capture. BRINGUP-M1: with B marked there is no fallback, so a broken slot B means the buttons and R1, whose flashes clear the mark. R2's --set-active=b waits for the maintainer's decision. Co-Authored-By: Claude Opus 5.5 --- device/comet/BRINGUP-M1.md | 16 +++++--- device/comet/NOTES.md | 79 ++++++++++++++++++++++++++++---------- 2 files changed, 69 insertions(+), 26 deletions(-) diff --git a/device/comet/BRINGUP-M1.md b/device/comet/BRINGUP-M1.md index d88888389..33c132ede 100644 --- a/device/comet/BRINGUP-M1.md +++ b/device/comet/BRINGUP-M1.md @@ -28,7 +28,10 @@ stock: a slot B that exhausts its tries falls back to it. No `devinfo` write or boot-success enablement is admitted; the boot-success policy for comet is the maintainer's decision. Keep reboots -few: with B unmarked, each boot spends one of its tries. +few. B has been marked successful since 2026-11-08, so a normal boot +spends no tries and nothing falls back to stock: a broken slot B image +means the buttons and R1. R1's flashes clear the mark, so B then has +three tries again, and if they run out stock boots (R2). ## Recovery procedures @@ -36,9 +39,10 @@ Both run from fastboot on the laptop, with the owner present and the owner's go for each write. `` is the phone's serial. Neither touches slot A, the bootloader, radio, `devinfo`, `persist`, `efs*`, `modem*` or `vbmeta`, and neither runs an unsuffixed `flash`. -Approval: the owner, in a private working session on 2026-10-30 (R1); -there is no public record, so the procedures are written out here in full -for review. +Approval: R1, the owner, in a private working session on 2026-10-30, +written out here in full for review. R2's step 4 (`--set-active=b`, a slot +flag write outside the tools our rules name) waits for the maintainer's +decision on #203; until then, stop after step 3 and ask there. ### R1: slot B boots but is broken (bad kernel, lost USB) @@ -62,8 +66,8 @@ fastboot -s reboot No `--set-active`: B is already current. Stop at the first write that fails and write the set again before any reboot; never boot a half-written -slot B. A fastboot flash may clear B's successful flag, so B then has its -three tries and a failure falls back to stock (R2). +slot B. A fastboot flash of slot B clears B's successful flag, so B then +has its three tries and a failure falls back to stock (R2). ### R2: slot B exhausted its tries and stock booted on A diff --git a/device/comet/NOTES.md b/device/comet/NOTES.md index fa6fba8e9..154b31e32 100644 --- a/device/comet/NOTES.md +++ b/device/comet/NOTES.md @@ -93,37 +93,76 @@ button restart. The feeder went into the root image, enabled before `sysinit`, and later into our development device package (not part of this PR, which ships boot policy only). -**Slot B marking.** With the feeder in place, slot B was marked successful -once by hand, with the owner's approval: one `devinfo` byte, the same -helper and before/after images as on 2026-10-29. `omamobile-boot-success` -has stayed **masked** since 2026-11-07 (it was masked on the old install -before the restore and is masked on the new one); this package ships no -writer and enables nothing. No `devinfo` write has been made since: the bytes read on 2026-11-17 -match the post-restore backup (below). - -**devinfo bytes 0x30-0x37.** In the post-restore backup below (image taken -2026-11-07 19:41 CST): `02 1a 00 00 02 16 00 00`. Read again on 2026-11-17 (read-only): `02 1a 00 00 02 16 00 00`, the same. -The layout of these bytes is not decoded here; earlier readings are in the -2026-10-30 entry. +**Slot B marking (2026-11-08 01:25:18Z).** With the feeder in place, slot +B was marked successful once by hand, with the owner's approval but not +the maintainer's (asked on 2026-11-05 for no further `devinfo` write; see +#203). It was the same helper and before/after images as on 2026-10-29: +`/usr/bin/omamobile-boot-success`, run over USB SSH on the booted system +after its health check passed (storage guard active, `devinfo` and its +disk `ro=1`, sshd, USB gadget, SDDM, Hyprland, the display on, no failed +units). + +- **What made `devinfo` writable:** the helper itself. It runs + `blockdev --setrw` on the parent disk (`sdd`) and then on the partition + (`sdd1`) immediately before its single `omamobile-bootctl + mark-successful` call, and `blockdev --setro` on both right after it, also + from an exit trap. The window is that one call; the whole run took about + 5 s (01:25:18Z to 01:25:23Z), and it logged no failed attempt. + `devinfo` is not in `/etc/omamobile-ufs-rw` (`boot_b init_boot_b + vendor_boot_b vendor_kernel_boot_b dtbo_b userdata`), and the storage + guard sets both `ro=1` again on its own. +- **Bytes 0x30-0x37:** before `02 1a 00 00 02 14 00 00`, after + `02 1a 00 00 02 16 00 00`. A full compare of the helper's before and + after images (8 KiB each) shows exactly one changed byte: 0x35, + `0x14 -> 0x16` (B's successful bit). +- `omamobile-boot-success.service` has stayed **masked** since 2026-11-07 + (masked on the old install before the restore and on the new one); this + package ships no writer and enables nothing. + +**No `devinfo` write since.** The whole partition read on 2026-11-18 +(read-only, `ro=1`) has the same sha256 as the copies in the 2026-11-08 +02:32Z and 2026-11-14 backups. The only difference from the post-restore +backup (01:41Z) is two bytes in ABL's own unused area (0x6e, 0x70), which +ABL changed during the reboots between the two captures; no tool of ours +writes there. **Fresh protected backup.** Stock's modem stack rewrote `efs`, `persist`, `modem_userdata` and `trusty_userdata`, and the factory flash rewrote `modem_a` and `devinfo`, so the 2026-10-30 checksums no longer apply. A new read-only capture was taken from a RAM-only hold (every block -device read-only, nothing mounted) before any modem, PMIC, AoC or Trusty -start: `efs`, `efs_backup`, `modem_userdata`, `persist`, `modem_a`, +device read-only, nothing mounted), entered right after the mark: the +hold started at about 01:28Z and the last image was read at 01:41Z on +2026-11-08 (19:41 CST on 11-07). So **this backup was taken after the +mark**, and its `devinfo` already has B's successful bit. It came before +any modem, AoC or Trusty start: the fresh root carried the package's +AoC and Trusty blacklist, and our local bring-up files (the modem start +among them) went back only at 01:46Z. It covers `efs`, `efs_backup`, `modem_userdata`, `persist`, `modem_a`, `modem_b`, `devinfo`, `trusty_persist` and `trusty_userdata`. Each partition was read twice in phone RAM and hash-checked before it was copied, and the backup tool's `verify` passed. Rechecked offline on 2026-11-17: all nine laptop images match the manifest and the hashes computed on the phone (9/9 MATCH). `modem_a` and `modem_b` are identical, and match the factory image's modem. The images stay off-repo. -Stock booted again on 2026-11-11, so this capture is no longer the -reference. A new read-only capture of the same nine partitions was taken -on 2026-11-14 at 03:29Z on the running Linux system (each partition -`ro=1` and unmounted, read twice on the phone with matching sha256, a -third hash of the laptop copy); that one is current, and also stays -off-repo. + +**Stock has not booted since 2026-11-08.** An earlier version of this +entry said stock booted again on 2026-11-11. That was wrong: on 11-11 the +phone dropped off USB during a Wi-Fi sleep trial, and every boot in that +night's journal is Linux on slot B. The captures confirm it: + +- A read-only capture of the same nine partitions was taken on + 2026-11-14 at 03:29:09Z on the running Linux system (each partition + `ro=1` and unmounted, no `storageproxyd`, read twice on the phone with + matching sha256, a third hash of the laptop copy). All nine images, + `devinfo` included, are byte-identical to a capture taken on 2026-11-08 + at 02:32Z, so nothing wrote `efs`, `persist` or `modem_userdata` (as + stock's modem stack does) and no slot change wrote `devinfo` (as both a + fallback and a switch to A do). +- Between those captures the phone ran Linux on slot B only, with + Trusty, the AoC and the modem started at each boot; the identical + images show those starts wrote none of the nine partitions. +- The Fold's first fingerprint storage start came after that capture: + the runner's state directories were created at 03:31:11Z on + 2026-11-14, about two minutes after it (FINGERPRINT-PLAN F4). **Superseded by this entry:** the 2026-10-30 statements that slot A is unbootable, that ABL has no slot to fall back to, and that recovery means From 1b69b80ec1f7667376260f1e665ed3689c7ff44b Mon Sep 17 00:00:00 2001 From: Nate Crawford Date: Wed, 18 Nov 2026 14:45:09 -0600 Subject: [PATCH 3/3] device-comet: drop the dwc3 glue, USB on the plain dwc3 node linux-omarchy-mobile#273 now enables comet's USB the Pixel 9a's way, on a plain snps,dwc3 node, and #271's zumapro glue is closed: a cold boot of #273's DT bound 11210000.usb to dwc3 directly and the host configured the gadget, with no glue module. The shared kernel config builds dwc3 in, so dwc3-zumapro leaves the initramfs module list and device/comet/kernel.config, which only selected the glue, goes. BRINGUP-M1 and the package README now name #273 as the one kernel dependency. Co-Authored-By: Claude Opus 5.5 --- device/comet/BRINGUP-M1.md | 7 ++++--- device/comet/device.conf | 2 +- device/comet/kernel.config | 4 ---- packages/omamobile-device-comet/README.md | 10 +++++----- packages/omamobile-device-comet/device.conf | 2 +- 5 files changed, 11 insertions(+), 14 deletions(-) delete mode 100644 device/comet/kernel.config diff --git a/device/comet/BRINGUP-M1.md b/device/comet/BRINGUP-M1.md index 33c132ede..0a35b1c68 100644 --- a/device/comet/BRINGUP-M1.md +++ b/device/comet/BRINGUP-M1.md @@ -5,9 +5,10 @@ Prepared 2026-11-08 and rebased onto main on 2026-11-17: descriptor and inert boot policy only. Preparing it contacted no phone; the hardware history it relies on, from 2026-10-28 on, is in [NOTES.md](NOTES.md) by date. The comet board DTS (`dt-bindings` commit first, new nodes -disabled) and the USB glue are their own linux-omarchy-mobile pull -requests, linux-omarchy-mobile#273 and #271; this descriptor builds -from public code only once they land. +disabled, USB on the Pixel 9a's plain `snps,dwc3` node) is its own +linux-omarchy-mobile pull request, #273; this descriptor builds from +public code only once it lands. The dwc3 glue (#271) is closed: a cold +boot of #273's DT showed the plain node binds without it. Kernel #80 is closed, not a merge dependency. A later owner-approved enablement and qualification is still required. diff --git a/device/comet/device.conf b/device/comet/device.conf index 5f390941c..ebdde3cab 100644 --- a/device/comet/device.conf +++ b/device/comet/device.conf @@ -54,7 +54,7 @@ INITRAMFS_INIT=/initramfs/init PANEL_SIZE=1080x2424 # Cover panel, portrait (dumpsys display); inner is 2076x2152. -INITRAMFS_MODULES="exynos-mailbox sec-acpm s2mps11 phy-snps-eusb2 phy-exynos5-usbdrd dwc3-zumapro phy-exynos-ufs ufs-exynos" +INITRAMFS_MODULES="exynos-mailbox sec-acpm s2mps11 phy-snps-eusb2 phy-exynos5-usbdrd phy-exynos-ufs ufs-exynos" # Require our root label before handing over to userdata. ROOT_LABEL=omamobile-root diff --git a/device/comet/kernel.config b/device/comet/kernel.config deleted file mode 100644 index b699b1f2b..000000000 --- a/device/comet/kernel.config +++ /dev/null @@ -1,4 +0,0 @@ -# SPDX-License-Identifier: MIT -# Staged source builds need the separately prepared public Tensor G4 glue. -# This does not enable the board's USB node or qualify a recovery path. -CONFIG_USB_DWC3_ZUMAPRO=m diff --git a/packages/omamobile-device-comet/README.md b/packages/omamobile-device-comet/README.md index 96e34a898..70202dc81 100644 --- a/packages/omamobile-device-comet/README.md +++ b/packages/omamobile-device-comet/README.md @@ -3,11 +3,11 @@ Staged boot policy for the Pixel 9 Pro Fold (comet, Tensor G4 / zumapro). This is not a supported install profile. The descriptor needs the separate -public Comet board DTS and USB glue before it can build from upstream. -The per-device build fragment selects that glue as a module; it does not -enable USB in the board DTS. Release builds exclude per-device fragments, -and this candidate is not a release-build profile. The separately prepared -board subset leaves USB disabled and needs its own attended qualification. +public Comet board DTS (linux-omarchy-mobile#273) before it can build from +upstream. That DTS enables USB on the Pixel 9a's plain `snps,dwc3` node, +which the shared kernel config builds in, so comet has no per-device build +fragment. Everything else the DTS leaves disabled needs its own attended +qualification. The package installs the descriptor, reboot-to, USB networking at metric 2000, storage-hiding udev rules, power-key/lid logind policy, shutdown watchdog diff --git a/packages/omamobile-device-comet/device.conf b/packages/omamobile-device-comet/device.conf index 5f390941c..ebdde3cab 100644 --- a/packages/omamobile-device-comet/device.conf +++ b/packages/omamobile-device-comet/device.conf @@ -54,7 +54,7 @@ INITRAMFS_INIT=/initramfs/init PANEL_SIZE=1080x2424 # Cover panel, portrait (dumpsys display); inner is 2076x2152. -INITRAMFS_MODULES="exynos-mailbox sec-acpm s2mps11 phy-snps-eusb2 phy-exynos5-usbdrd dwc3-zumapro phy-exynos-ufs ufs-exynos" +INITRAMFS_MODULES="exynos-mailbox sec-acpm s2mps11 phy-snps-eusb2 phy-exynos5-usbdrd phy-exynos-ufs ufs-exynos" # Require our root label before handing over to userdata. ROOT_LABEL=omamobile-root