Skip to content

device/cheetah, RELEASES: AVB footers on boot and init_boot (#11) - #104

Merged
derekross merged 2 commits into
derekross:mainfrom
jkjoplin:device-cheetah-avb-footers
Oct 30, 2026
Merged

derekross merged 2 commits into
derekross:mainfrom
jkjoplin:device-cheetah-avb-footers

Conversation

@jkjoplin

@jkjoplin jkjoplin commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

What and why

A Pixel 7 Pro installed with tools/install-phone never started slot B, the symptom of #11: the phone ended in Fastboot Mode with "Enter reason: BL1 requested", slot-retry-count:b 1, slot-successful:b no, and no USB gadget reached the laptop in four minutes. Its slot A runs stock CP3A.261005.002.A1 and both slots run ABL cloudripper-17.0-15902555. Its vbmeta_b, though, was left from BP2A.250605.031.A2 (Android 16, June 2025). Both vbmetas chain boot (rollback index location 2) and init_boot (location 4).

This adds AVB_FOOTERS to cheetah's descriptor, as device/lynx/device.conf does. bin/omamobile images then gives boot and init_boot hash footers. With stock CP3A's footer values, after bin/omamobile flash the phone booted, ran first boot and marked slot B successful. After review, the second commit carries CP2A.260705.006's values instead (rollback index 1783209600, security patch 2026-07-05, per L-225), and the phone boots those too (below).

Only the footers changed between the failed boot and the good one. Rebuilt from the same kernel output with and without the descriptor lines, vendor_boot, vendor_kernel_boot and dtbo are byte for byte the same, and boot and init_boot match up to their padding and footer. The footer build is reproducible (a second build was byte-identical). Each version was flashed once.

Also in this PR:

  • a dated entry in device/cheetah/NOTES.md that marks what is verified [V] and what is inferred [I];
  • a change to the AVB_FOOTERS row in docs/RELEASES.md. It said the Pixel 7 Pro's bootloader takes images without footers.

What the review settled (second commit):

  • What triggers it: a vbmeta_b that chains boot and init_boot, as stock's does. libavb reads a chained partition with no footer from its first byte, finds an invalid vbmeta header and returns ERROR_INVALID_METADATA, which result_should_continue() never lets an unlocked boot past. A wrong key (ERROR_PUBLIC_KEY_REJECTED) or hash (ERROR_VERIFICATION) it does let through, and VERIFICATION_DISABLED skips the descriptors (checked in external/avb c5066a9). This phone's older vbmeta_b isn't the trigger: stock CP3A's vbmeta chains them the same way. The descriptor comment, the NOTES entry and the RELEASES row now state the condition that way.
  • The rollback index: CP2A's values boot on this phone. Rebuilt with them, boot and init_boot differ from the CP3A-footer images only in the footer, and the other three images are byte for byte the same. bin/omamobile push wrote and verified slot B. The phone booted it: slot _b, verifiedbootstate orange, no failed units, slot B still successful. Slot A runs CP3A, whose footers carry 1791158400, so this unlocked ABL accepts a footer index below that one. Whether it stores indexes while unlocked is still untested.

Device and build

  • Phone: Pixel 7 Pro (cheetah), MP1.0 B0, stock CP3A.261005.002.A1 on slot A
  • Kernel release (uname -r, both commits): 7.3.0-rc6-omamobile-push1-g1cb4bd36f3be (omamobile-int at 1cb4bd36f3be, Android clang r596125, mkbootimg, libufdt and avb from AOSP, no LineageOS tree)
  • Packages changed, with versions: none
  • How this phone was set up, for the record:
    • Before the install, slot B's bootloader was written from the CP3A factory image (fastboot flash bootloader_b), so that both slots carry the same version (REINSTALL-RUNBOOK I1). I didn't read slot B's version before that write.
    • The root image was built from f5da1df with a local signing key. Eight packages were built from f5da1df (keyring, device-cheetah, audio, sensors, omarchy, shell, modem, firstboot); the rest were copied from the development channel. The versions are in the smoke report below.

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes (168 ok)
  • tests/packages: not run, since no package changed
  • Each changed package has its version bumped: none changed
  • Commits have area prefixes and bodies that say why; AI help is a Co-Authored-By: trailer, no Signed-off-by:

On the phone

  • I ran this on my own phone, booted into this build
  • Runbook steps passed (REINSTALL-RUNBOOK):
    • I1: pass, 15902555 on both slots.
    • I2: pass, the eight commands.
    • I3: the installer finished and rebooted (its terminal output wasn't kept), then the boot failure above. After this change, bin/omamobile flash booted.
    • F1: pass, the root grew to 109G and === firstboot done ===.
    • F2: the user and its groups, the host name, the root's size, and SDDM, sshd, NetworkManager and networkd active, as expected. omamobile-boot-success had run and exited (slot B successful), and ufw was already active. Before provisioning, omamobile-aoc (no aoc.bin), omamobile-wifi, omamobile-bt-addr@hci0 and systemd-firstboot (no console) had failed.
    • V2/V3: provisioned everything but camera data (a separate issue). Afterwards no unit failed, and persist, efs, efs_backup, modem_userdata, modem_a and modem_b match the read-only backup taken before provisioning. devinfo differs only in three bytes of ABL's own header (0x6d-0x70); its records from 0x80 are identical.
  • What I did not test:
    • this change on a phone whose vbmeta_b is from the current stock build, or on the maintainer's phone;
    • a fresh tools/install-phone run with the footer images (tests/images-layout covers it offline; bin/omamobile flash and push ran on the phone);
    • whether ABL stores footer indexes while unlocked, and rollback index 0;
    • omamobile-boot-update (RELEASES §5.3), which isn't in the package yet. When it lands, it will need to apply these footers on cheetah too.
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)
tools/phone-smoke report (second commit's images, 2026-10-30T04:01Z)

phone-smoke: cheetah

Kernel 7.3.0-rc6-omamobile-push1-g1cb4bd36f3be, tools at 64e6d42, 2026-10-30T04:01Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-g1cb4bd36f3be, slot b, up 54s
storage guard (required) ok 55 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 97G free
kernel health (required) ok no oops or BUG; 0 WARN, 194 error lines in dmesg
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card2-DSI-1 connected, 1440x3120
GPU ok render node on panthor
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked false)
touch ok Synaptics TouchComm Touchscreen
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered false
battery ok 69% Charging, 31 °C
sound cards ok googleaocsndcar
sensors ok Accelerometer AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 31 °C

Packages: hyprland 0.56.2-5.1, libcamera 0.7.2-4.21, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-audio 0.5.4-1, omamobile-device-cheetah 0.1.34-1, omamobile-fingerprint 0.1.8-1, omamobile-firstboot 0.1.2-1, omamobile-gnss 0.2.1-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-modem 0.1.7-1, omamobile-omarchy 0.1.12-1, omamobile-owl-widgets 0.1.1-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.32-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1

🤖 Generated with Claude Code

https://claude.ai/code/session_01TTVics5jHkiz34wzjZWkb9

…s#11)

A second Pixel 7 Pro, installed with tools/install-phone, never started
slot B: the phone ended in Fastboot Mode with "Enter reason: BL1
requested", slot-retry-count:b 1 and no USB gadget, the symptom of
issue derekross#11. Its slot A runs stock CP3A.261005.002.A1 and both slots ABL
15902555, but vbmeta_b was left from BP2A.250605.031.A2 (Android 16,
June 2025). Both vbmetas chain boot and init_boot.

With the descriptor's AVB_FOOTERS (stock CP3A's rollback index and
security patch, AOSP's test key, as lynx does), bin/omamobile images
gives those two images hash footers, and after bin/omamobile flash the
phone booted, ran first boot and marked slot B successful. Nothing else
changed between the two: rebuilt from the same kernel output,
vendor_boot, vendor_kernel_boot and dtbo are byte for byte the same, and
boot and init_boot match up to their padding and footer.

The maintainer's phone (ABL 15199429) and the Pixel 7 in derekross#79 (15902555)
boot footer-less images, so the trigger may be the older vbmeta_b; the
NOTES entry records what is verified and what isn't. RELEASES' row for
AVB_FOOTERS no longer says the Pixel 7 Pro's bootloader takes images
without one.

Tested: tests/all (168 ok); on the phone, the boot above and
tools/phone-smoke (every check ok, cameras skipped).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TTVics5jHkiz34wzjZWkb9
@derekross

Copy link
Copy Markdown
Owner

Thank you, Jeremy, and welcome. This is a careful first pull request: the notes separate what you verified from what you inferred, the body says plainly what you didn't test, and the smoke report is there. I rebuilt cheetah's images here with main's descriptor and with yours. vendor_boot, vendor_kernel_boot and dtbo are byte-identical. boot and init_boot match main's byte for byte up to their old length, followed by the padding and a test-key footer. tools/pr-check and the descriptor and image tests pass too. (CI needs my approval for a first pull request; I'll approve the run.)

I think I can answer your "what triggers it" question, and the answer changes two things in the PR.

Why my phone boots without footers. I checked my own vbmeta_b from my partition backup. It isn't a stock vbmeta: it lists boot and init_boot as hash descriptors and doesn't chain them. Stock's vbmeta, on my slot A and in the factory image, chains boot (rollback index location 2) and init_boot (location 4), as yours does. In libavb, a chained partition with no footer fails with "invalid metadata", and an unlocked bootloader doesn't let that through. A hash that doesn't match is only a verification error, and unlocked it does. So the age of your vbmeta_b isn't the trigger. Any Pixel 7 Pro whose vbmeta_b is stock's needs these footers, and that includes the phone in #11. fastboot oem disable-verification worked there because a vbmeta with verification disabled skips its descriptors. Could you reword the NOTES bullet, the device.conf comment and the RELEASES row along those lines? "A phone whose vbmeta_b chains boot and init_boot, as stock's does" is the condition. It also means the footers can't change anything on my phone, because nothing there ever reads them. I'll still boot it before merging, since this changes the reference phone's images.

The rollback index and patch level. My slot A runs CP2A.260705.006, and so did the phone in #11. CP2A's footers carry rollback index 1783209600 and security patch 2026-07-05. The descriptor would put CP3A's 1791158400 and 2026-10-05 on every Pixel 7 Pro. Rollback indexes are stored per location for the whole device, not per slot. Once a slot is marked successful, which omamobile-boot-success does, libavb's reference flow stores any index higher than the stored one. Whether Pixel's bootloader does that while unlocked is exactly the open question you named. I set a rule for this on the Pixel 9a, and it applies here too: the descriptor carries the values of the oldest stock build any owner runs on slot A, and a pull request never raises them. Two options would satisfy it:

  • CP2A's values, AVB_ROLLBACK_INDEX=1783209600 and AVB_SECURITY_PATCH=2026-07-05, which also match the descriptor's OS_PATCH_LEVEL=2026-07 in the init_boot header; or
  • rollback index 0. libavb never stores a zero index, and a Pixel 9a contributor has booted footers with index 0 on that phone's bootloader (device-tegu 0.1.1: public-kernel boot, native display and guarded touch #74's notes).

You offered to try a lower index, and your phone is the right one to try it on: its CP3A slot A is newer than either value, and your vbmeta_b (1749081600) already shows that the unlocked bootloader accepts an index below the stored one. Could you build with one of the two (I'd lean towards CP2A's values, since that's the rule as written), write slot B with bin/omamobile flash or push as before, and add the result to the NOTES entry? If the bootloader refuses it, please record the exact screen or enter-reason, then flash your current images back.

Two smaller things:

  • Your notes say you wrote bootloader_b from the CP3A image before installing. That followed our reinstall runbook, but CONTRIBUTING's §3.1 says to stop and ask when the slots differ. That conflict is mine to fix. Thanks for recording it.
  • docs/RELEASES.md will conflict by one row with device-alioth: add experimental POCO F3 source build and guarded installer #25, whose copy of that row is older. Whichever lands second keeps yours.

Once the values are changed and the notes say what triggers it, I'll put these images on my phone and merge after it boots. Thanks again: this closes a real gap for everyone installing on a stock Pixel 7 Pro.

…e footers

From the review of derekross#104. The trigger is a vbmeta_b that chains boot and
init_boot, as stock's does, not the age of this phone's vbmeta_b:
libavb reads a chained partition with no footer from its first byte,
finds an invalid vbmeta header and returns ERROR_INVALID_METADATA,
which result_should_continue() never lets an unlocked boot past (a
wrong key or hash it does; external/avb c5066a9). The maintainer's
vbmeta_b lists them as hash descriptors instead, which is why that
phone boots footer-less images. The descriptor comment, the NOTES entry
and RELEASES' row now say so.

The footers now carry CP2A.260705.006's rollback index and security
patch (1783209600, 2026-07-05), the oldest stock an owner runs on slot
A (review lesson L-225), matching OS_PATCH_LEVEL, instead of CP3A's.
Tested on this phone, whose slot A runs CP3A (1791158400): rebuilt,
boot and init_boot differ from the CP3A-footer images only in the
footer, the other images are byte for byte the same, and after
bin/omamobile push slot B booted (orange, no failed units, slot still
successful) and tools/phone-smoke passed with cameras skipped.

Tested: tests/all (168 ok), tools/pr-check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TTVics5jHkiz34wzjZWkb9
@jkjoplin

Copy link
Copy Markdown
Contributor Author

Thanks for the review, and for rebuilding the images yourself. Both changes are in the second commit, 3936918:

  • What triggers it. The descriptor comment, the NOTES entry and the RELEASES row now give the condition as a phone whose vbmeta_b chains boot and init_boot, as stock's does. I checked the libavb side in external/avb c5066a9. With no footer, load_and_verify_vbmeta() keeps vbmeta_offset = 0, the header check fails, and it returns ERROR_INVALID_METADATA, which result_should_continue() never continues past. It does continue past ERROR_PUBLIC_KEY_REJECTED, ERROR_VERIFICATION and ERROR_ROLLBACK_INDEX, and VERIFICATION_DISABLED skips the descriptors. Your finding about your own vbmeta_b is attributed to this review in the notes.
  • The rollback index. The footers now carry CP2A's values, 1783209600 and 2026-07-05. Rebuilt with them, boot and init_boot differ from the CP3A-footer images only in the footer, and vendor_boot, vendor_kernel_boot and dtbo are byte for byte the same. I wrote slot B with bin/omamobile push and the phone booted it: slot _b, verifiedbootstate orange, no failed units, slot B still successful, and tools/phone-smoke ok (the new report is in the description). Slot A here runs CP3A, whose footers carry 1791158400, so this unlocked bootloader accepts a footer index below that one. I haven't tested whether it stores indexes while unlocked, and I didn't try index 0.

The description is updated to match. Noted on the RELEASES row and #25.

@derekross

Copy link
Copy Markdown
Owner

Thank you, Jeremy, for the quick and thorough follow-up. Both points are in, and the libavb reading is clearly sourced. Testing the lower index on your own phone is exactly what I hoped for: a footer index below slot A's CP3A one boots under an unlocked ABL, and that's useful to know.

I checked the new head here:

  • Cheetah's images rebuilt from the same kernel output with main's descriptor and with yours. vendor_boot, vendor_kernel_boot and dtbo are byte-identical. boot and init_boot match up to main's length, then pad to the partition sizes, with footers carrying 1783209600 and 2026-07-05.
  • Those values match the footers on my own CP2A slot A exactly.
  • tools/pr-check and the image, boot-method and installer tests pass.

I've approved the CI run for this push.

My vbmeta_b doesn't chain these partitions, so on my phone the footers are never read. I'll still put these images on it before merging, as I said, since they change the reference phone's images. Once it boots, I'll merge. When I squash, I'll write the commit message myself, so the first commit's earlier guesses (the older vbmeta_b, CP3A's values) don't land on main.

One small optional fix: the RELEASES row for AVB_ROLLBACK_INDEX still shows 1791158400, 2026-10-05 as its example. Now that the row above names the Pixel 7 Pro, someone could read that as cheetah's value. If you'd like, name the device for each value (husky's CP3A, cheetah's and lynx's CP2A). Otherwise I'll do it at merge.

Thanks again: this fixes slot B for everyone installing on a stock Pixel 7 Pro.

@derekross

Copy link
Copy Markdown
Owner

Tested on my Pixel 7 Pro, and it turned out to be a real test. My earlier note was wrong: my phone's vbmeta_b is no longer the one in my 10-11 backup. Slot B got CP2A's factory bootloader and vbmeta during the first install, so it's byte-identical to vbmeta_a and chains boot and init_boot (rollback index locations 2 and 4), the same as yours.

I rebuilt the images at 3936918 from the kernel the phone runs (7.3.0-rc6-omamobile-push1-00571-gd40c36abfc0d), so nothing else changed: vendor_boot, vendor_kernel_boot, dtbo and the DTB are byte-identical. avbtool info_image shows index 1783209600 and patch 2026-07-05 on both, which match my stock boot_a's footer exactly. After push it came back on slot B in under a minute, and tools/phone-smoke passes every check (no failed units, display, GPU, touch, Wi-Fi, Bluetooth, sound, sensors and all four cameras).

Merging now, with a squash message I've written so the first commit's earlier guesses don't land. I'll fix the AVB_ROLLBACK_INDEX example in RELEASES in a follow-up. Thank you, Jeremy: this fixes slot B for everyone installing on a stock Pixel 7 Pro.

@derekross
derekross merged commit 4bcaebc into derekross:main Oct 30, 2026
2 checks passed
derekross added a commit that referenced this pull request Oct 30, 2026
…VB footers (#174)

NOTES records 2026-10-29 and 10-30's charging work: the 10-29 outage was
upower's 0 % suspends and a laptop route, charging works asleep, and the
charger read offline at Full because the driver required CHG_OK (fixed on
the kernel side, with the fast-charge timer off). It also records how the
phone stopped booting footer-less images after #104's first boot, the stock
recovery that followed, and the fresh radio backup.

AGENTS gains the footer rule and what to do on stock's recovery screen.
The kernel config drops CONFIG_GS201_CAM_PROBE: the read-only CSIS probe
was left out when the kernel was curated for publishing.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Oct 30, 2026
The matrix and the Wanted list against what has merged since #140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were
  closed because they landed unchanged through kernel #134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the
  2026-10-28 notes. Touch stays WIP: kernel #134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel #133)
  and the kernel option with the touch notes (#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names
  its open kernel PR, #116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133)
  records it scanning through its own UART; kernel #98 and #98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes
  the merged tier 1 auto-sleep (#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open #171, #172, #174-#176.
- Wanted: coral's #52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (#55, #56, #58,
  #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and
  kernel #115, both open.

The Pixel 9a row and the Pixel 9 family line are left to #165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
derekross pushed a commit that referenced this pull request Nov 2, 2026
…ing (#307)

The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to.

- **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel #178 on #156, both in review) and brcmfmac (kernel #56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after #178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did.
- **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (#268, #275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, #284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word.
- **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel #125's boot, which also checks the panel ID).
- **Charging, Haptics, Torch, NFC:** kernel #161, #96, #104 and #105 are merged.
- **USB net:** the rescue also handles a replug the gadget didn't see (#280).

The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel #99), the panel ID (kernel #125), the RTC without the PMIC interrupt (kernel #55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers.

Closes #307

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ekross#11 (derekross#104)

A stock Pixel 7 Pro's vbmeta chains boot and init_boot, so ABL reads
their own AVB footers. Without footers, slot B depended on the bootloader
tolerating the missing descriptor. cheetah's descriptor now sets
AVB_FOOTERS with CP2A's rollback index (1783209600) and security patch
(2026-07-05), the values on stock CP2A's boot_a, so a footer is never
above stock.

The trigger is a vbmeta_b that chains boot/init_boot, as stock's does;
NOTES records both owners' tests and RELEASES corrects the AVB_FOOTERS
row. Tested on two Pixel 7 Pros with chaining vbmeta_b: push, slot B,
orange, smoke test all ok.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…VB footers (derekross#174)

NOTES records 2026-10-29 and 10-30's charging work: the 10-29 outage was
upower's 0 % suspends and a laptop route, charging works asleep, and the
charger read offline at Full because the driver required CHG_OK (fixed on
the kernel side, with the fast-charge timer off). It also records how the
phone stopped booting footer-less images after derekross#104's first boot, the stock
recovery that followed, and the fresh radio backup.

AGENTS gains the footer rule and what to do on stock's recovery screen.
The kernel config drops CONFIG_GS201_CAM_PROBE: the read-only CSIS probe
was left out when the kernel was curated for publishing.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
The matrix and the Wanted list against what has merged since derekross#140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were
  closed because they landed unchanged through kernel derekross#134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the
  2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133)
  and the kernel option with the touch notes (derekross#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names
  its open kernel PR, derekross#116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133)
  records it scanning through its own UART; kernel derekross#98 and derekross#98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes
  the merged tier 1 auto-sleep (derekross#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176.
- Wanted: coral's derekross#52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58,
  derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and
  kernel derekross#115, both open.

The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ing (derekross#307)

The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to.

- **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (derekross#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel derekross#178 on derekross#156, both in review) and brcmfmac (kernel derekross#56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after derekross#178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did.
- **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (derekross#268, derekross#275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, derekross#284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word.
- **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel derekross#125's boot, which also checks the panel ID).
- **Charging, Haptics, Torch, NFC:** kernel derekross#161, derekross#96, derekross#104 and derekross#105 are merged.
- **USB net:** the rescue also handles a replug the gadget didn't see (derekross#280).

The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel derekross#99), the panel ID (kernel derekross#125), the RTC without the PMIC interrupt (kernel derekross#55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers.

Closes derekross#307

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants