Skip to content

device-tegu 0.1.1: public-kernel boot, native display and guarded touch - #74

Closed
h4rkl wants to merge 24 commits into
derekross:mainfrom
h4rkl:tegu-device-package
Closed

h4rkl wants to merge 24 commits into
derekross:mainfrom
h4rkl:tegu-device-package

Conversation

@h4rkl

@h4rkl h4rkl commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Add Pixel 9a (tegu) v0.1.1 boot, native-display and guarded-touch policy, using a pinned public kernel source recipe instead of private board patches. Keep the shared descriptor on Android 16 / September 2025 metadata, with its selector and AVB/display-register overrides inactive pending cross-owner qualification.

The package gates the touchscreen module behind a synced persistent marker and explicit retry. It preserves tarball-installed kernel modules against Arch's old-kernel cleanup, enables native DSI brightness commands following the other Tensor packages, and limits refresh to the tested 60 Hz. The shared clock change is separate in #97, entirely within omamobile-firstboot. New commits include the co-author trailer. Upstream main f5da1df is merged.

On-device validation on the second contributor's phone used the pinned public board/touch/native-display tree with Android 16 / September 2025 headers and private AVB footers at rollback index 0. Footer-free images returned to fastboot; adding footers to byte-identical payloads booted. Native DRM appeared on camera, the owner confirmed touch, and a subsequent boot automatically initialized display and touch while retaining all 1,782 modules. Required smoke checks passed. Earlier guarded tests verified persistent-marker skip across reboot and explicit retry. Stock A recovery boot and return through fastboot were verified without writing A or resetting userdata.

Offline/native build checks: source-tree reproduction, kernel builds, targeted DRM W=1 without diagnostics, full-schema display validation, native aarch64 package build/check and integrity checks, Linux tests, and PR policy checks. The base ACPM W=1 check has inherited kernel-documentation warnings. The user is coordinating the older-stock owner's footer test; no reply or contact has been sent by the agent.

This remains draft: shared footer activation awaits that owner's result, clean installation and signed release artifacts are unqualified, and automatic B-success marking is disabled. Plymouth's early splash daemon still crashes, there is no GPU render node, and the remaining peripherals in the report are absent or untested. These results establish a working native display/touch development build on existing Arch userdata, not an installable release for every 9a.

phone-smoke: tegu

Kernel 7.3.0-rc6-omamobile-push1-gde2e0689c517, tools snapshot 53a106f, 2026-10-27T22:51Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-gde2e0689c517, slot b, up 223s
storage guard (required) ok 62 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 98G free
kernel health (required) ok no oops or BUG; 0 WARN, 11 error lines in dmesg
systemd units not ok failed: plymouth-start.service
USB gadget (required) ok bound to 11210000.usb
display ok card0-DSI-1 connected, 1080x2424
GPU not ok no render node
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked true)
touch ok Synaptics TouchComm Touchscreen
buttons ok gpio-keys
Wi-Fi skip no wireless interface
Bluetooth skip no controller
battery skip no battery power supply
sound cards skip none
sensors skip no sensor proxy
cameras skip no libcamera tools

Packages: hyprland 0.56.2-7, libcamera 0.7.2-4, mesa 1:26.2.5-1, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-device-tegu 0.1.1-6, omamobile-firstboot 0.1.3-2, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.12-1, omamobile-owl-widgets 0.1.1-1, omamobile-shell 0.2.28-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1

h4rkl and others added 14 commits October 27, 2026 12:41
Ignore local development playbooks and captures so tegu work can retain private context without exposing it in public changes.

Co-Authored-By: Codex <codex@openai.com>
Provide tegu-only userspace policy for the first native root: keep the storage guard in force, configure USB networking, and bound a hung shutdown. Keep slot-success marking and peripheral startup absent until the board and recovery gates pass.

The package stages cleanly on the Linux build host; tests/all passes there. This does not make the staged descriptor installable.
The package needs its reboot-to helper at build time, but packages/.gitignore ignores src directories. Track this tegu copy explicitly so a clean checkout can build the package.
The currently running stock Pixel 9a and the verified CP3A.261005.005 factory init_boot header agree on Android 17 and the October 2026 patch level. Keep the image selector disabled until the board and AVB gates pass.
The tegu USB gadget runs in the guarded initramfs before root filesystem modules are available. Build the Synopsys eUSB2 PHY into the kernel so the high-speed link can probe at that stage.
The shared SOC_COMPATIBLE packer is now on upstream main. Keep tegu gated until its public DTB and AVB values are qualified, while removing stale review wording from both descriptor copies.
Tegu first light has no usable wall clock before network time. On the first full Omarchy boot, the clock predated the bundled package keys, so pacman-key skipped them and firstboot finished with a trust warning.

Raise only a stale clock to the installed keyring file timestamp before omamobile-firstboot. This lets the signed local repository initialise without depending on a particular build host or network connection.

Verified with the tegu package test, an arm64 package build, and on-device unit verification and start. The existing installed keyring was repaired after setting current time.
ABL leaves the tegu command-mode display trigger masked after its splash. The live register read 0x3070; 0x3061 sent the simpledrm framebuffer to the panel while Hyprland and Omarchy Shell were running. Pack the board-checked trigger pair into the tegu initramfs so the desktop appears after boot.
The package installs a copy of the device descriptor. The booted tegu descriptor gained the board-checked DECON trigger, but the package copy did not, so package tests failed and an installed package would leave the screen at the boot splash.

Keep the installed descriptor identical to the boot-tested source. The tegu package test passes in the Linux build environment.
The S3908 child waits for S2MPG14 regulators. Keep ACPM and PMIC modules from autoloading during early boot, then load them through a tegu timer after the USB rescue path is available. Fail the service if touch input does not appear.

On the Pixel 9a, a native B cold boot reached systemd before the timer, then registered Synaptics TouchComm input at 35 seconds without manual commands. The package staging test passed on Linux and the phone stayed responsive over USB.
Select both observed tegu IPOP revisions, apply the staged watchdog, USB, UFS and touch overlays, and use the October Android 17 partition sizes and AVB metadata. Keep package descriptor synchronized with the image builder.

The public recipe rebuilt all five images and the overlaid DTB byte-for-byte from the working touch-child bundle with the same frozen kernel and initramfs. The device cold booted Omarchy and registered S3908 touch after the delayed ACPM start; physical taps and swipes were confirmed.

The public tegu kernel and signed root image remain separate release dependencies.
The boot recipe and device package now reach native Omarchy with working touch on slot B. Keep the first-light summary aligned with the qualified source while naming the public kernel, signed root image and clean install still needed for a release.
@derekross

Copy link
Copy Markdown
Owner

Welcome, and thank you for the package. It's a careful piece of work: the eight files you took from the Pixel 7 Pro's package are byte-identical to main's, the test refuses boot-success, bootctl and every hardware start, and I ran tools/pr-check, tests/all, the package test and a dtc -@ compile of all four overlays here: all pass. (CI needs a maintainer's approval for a first pull request; I'll approve your runs so they show up.) I agree with keeping it a draft, and here is what it needs before it can leave that state.

The board DTS first. The four overlays name 28 nodes (&cmu_top, &watchdog_cl0, &usb32drd, &ufs_phy, &acpm_ipc, /firmware/power-management/pmic-1, the touchscreen path, and so on) that exist in no tree anyone else can build: linux-omarchy-mobile has no zumapro-tegu DTS yet, and no open kernel PR adds one. The package's ConditionPathExists and the touch script hard-code the same node path. Device-tree nodes go into the kernel first, disabled, and the overlays here only switch them on, so the descriptor can land once that DTS is public and the overlays are checked against it.

One descriptor, two phones. device/tegu/device.conf and NOTES.md on main are W4HO-ham's, whose Pixel 9a runs BP3A.250905.014. His notes record OS_VERSION=16.0.0 and OS_PATCH_LEVEL=2025-09 as verified against that build's init_boot header, and say no display trigger write is requested. This PR replaces them with CP3A.261005.005's values (17.0.0, 2026-10), adds AVB footers with a rollback index and patch level for 2026-10-05, and adds the trigger write. Before I can merge a descriptor that both of you install from, I need to know what a 9a on the 2025-09 stock does with images that carry a 2026-10 rollback index and patch level: refuse them, boot them, or boot them and store the index (which could then refuse the older stock on slot A, and slot A is everyone's way back). Could you say which build your slot A runs, and could the two of you agree on one set of values, or on deriving them from the owner's slot A? The trigger address itself is right for this SoC (DECON0 is at 0x19470000 in the stock zumapro DPU dtsi, so 0x19470030 is TRIG_CON, and the value is the same bit change the 7 Pro and 8 Pro use); the difference is that W4HO-ham's kernel drives the panel through the DRM driver and yours boots on the simple framebuffer, so the descriptor should say which path it serves.

The notes. Rather than rewriting the header of the existing notes, please add a dated entry below the existing sections with the kernel release (uname -r), the tree it came from (private is fine, just say so), how slot B was written, what was and wasn't tested, and that it's your phone, since there are two now. The pull request template's smoke report (tools/phone-smoke) would be welcome too.

The touch timer. omamobile-tegu-touch-start.timer loads ACPM and the PMIC at 35 s into every boot with nothing written first. The 7 Pro's start scripts (omamobile-wifi-start, omamobile-aoc-start) write a marker before they touch hardware and skip the step if the next boot still finds it, so a step that hangs can't hang every boot after it; this one needs the same. Two details there: blacklist s2mps11 does nothing with arm64 defconfig's CONFIG_REGULATOR_S2MPS11=y (and nothing in the script loads it, so I assume it's built in on your tree as well), and the README's "before the USB rescue path is available" refers to something this package doesn't contain.

Smaller things, for when you get to them:

Thanks again for taking this on. Having two 9a owners is a real asset, as long as you're both building the same tree, so getting the DTS into linux-omarchy-mobile is the next step that unblocks everything else here.

@derekross

Copy link
Copy Markdown
Owner

On the descriptor values, the rule I'll apply so neither of you has to wait for the other: the descriptor carries the values of the oldest stock build any owner runs on slot A, which today is W4HO-ham's 2025-09 (what main has), and a pull request never raises them. A newer rollback index or patch level in slot B's images can only ever lock an older stock out of slot A, and slot A is the way back for everyone. If your phone's bootloader refuses the older values, that is a finding for the notes (with the exact fastboot or ABL message), and we'd look at deriving the values from the owner's own slot A at install time rather than pinning newer ones in the repository. The AVB footer and the trigger line follow the same rule: in only once both of you have seen them boot.

h4rkl added 2 commits October 28, 2026 08:59
The current mainline kernel builds exynos_mailbox as a module. Starting ACPM before it leaves all 16 channels unusable, so S2MPG14 cannot supply the Synaptics controller. Load the mailbox before ACPM and keep the startup scoped to tegu.

The new B kernel booted Omarchy and registered touch after loading the mailbox first. The tegu package staging test passes on Linux; pkgrel 2 upgrades the on-device package. Use coreutils for the descriptor test so a minimal build root does not need cmp.
@h4rkl

h4rkl commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor Author

This is amazing feedback ty @derekross. My Clanker is still clanking and opened this PR last night while I was asleep - but will read through and address all the feedback.

We should open a comms channel @W4HO-ham so we don't overlap - what suits best? I'm on TG at this expiring link handle or twitter @ harkl_ . Ping me and we can connect.

h4rkl and others added 2 commits October 28, 2026 10:37
Restore the shared descriptor to the oldest owner firmware values and leave image selection gated. Remove prototype-only overlays in favor of the public board and touch series. Preserve the first owner notes and append the second phone results with their limits.

Persist a touch-start marker before loading drivers, retain it on failure, and require an explicit retry after an incomplete start. Handle the public and prototype DT paths, remove the ineffective regulator blacklist, and move the clock floor to a separate firstboot change.

Linux tests/all passes with environment-dependent skips. Image layout and overlay checks also pass with the AOSP and kernel build tools. Mocked package tests cover module order, marker persistence, retry, timeout and disabled nodes. Hardware smoke evidence predates this review change and is recorded separately.

Co-Authored-By: Codex <codex@openai.com>
Phones without an RTC can start before the installed signing keys were created. Use the newest public keyring timestamp in the verified root image as a clock floor before GnuPG creates or imports keys, without moving an accurate clock backwards.

The Linux firstboot tests cover an old clock, an accurate clock, absent keyrings, and ordering before pacman-key. Move this shared policy out of the tegu package.

Co-Authored-By: Codex <codex@openai.com>
@h4rkl h4rkl changed the title device-tegu 0.1.1: native boot and touch support device-tegu 0.1.1: guarded boot and touch package Oct 27, 2026
h4rkl and others added 2 commits October 28, 2026 11:00
The package check uses cmp, which is absent from the minimal phone root. Declare diffutils as a check dependency so makepkg can run the full tests in a fresh build environment.

Built with checks enabled on aarch64 tegu, installed 0.1.3-2, and ran the installed keyring setup against an isolated keyring root. Clock seeding and real pacman-key initialization and population passed.

Co-Authored-By: Codex <codex@openai.com>
Keep the tegu review focused on device support. The shared omamobile-firstboot clock floor and native check dependency are carried by the firstboot-clock-floor branch instead.

Co-Authored-By: Codex <codex@openai.com>
h4rkl and others added 4 commits October 28, 2026 11:12
The public board needs ACPM for early USB power, so gate the modular touchscreen itself behind the synced startup marker. Pin the public board, touch and native display source tree and provide a worktree preparation command instead of depending on private patches.

Native aarch64 package checks, installation integrity and retry pass. The existing private kernel also passed automatic startup, cross-boot marker skip, guarded retry and stock A recovery boot. Public-source reproduction and display schema checks pass; public-kernel hardware qualification remains pending, so the descriptor stays gated with the oldest shared metadata.

Co-Authored-By: Codex <codex@openai.com>
The footer-free images returned to fastboot. Adding index-zero AVB footers to byte-identical payloads booted the public board and touch kernel with Android 16 and September 2025 metadata on the newer phone. Record actual smoke results and limits without changing the shared descriptor or claiming cross-owner display qualification.

Co-Authored-By: Codex <codex@openai.com>
…policy

Arch kernel-modules-hook removes unowned future-kernel modules, leaving a flashed kernel without display, touch or firewall modules. Skip that cleanup while the tegu package is installed. Enable native DSI brightness commands as on the other Tensor packages and cap refresh at the tested 60 Hz.

Native aarch64 package checks and integrity checks passed. A subsequent public-kernel boot retained all 1782 modules, automatically initialized DRM and touch, and passed every required phone-smoke check. Camera and owner testing confirmed the visible Omarchy lock screen and touch; backlight restore and firewall passed. Record the remaining Plymouth failure, missing GPU/peripherals and cross-owner footer qualification limits.

Co-Authored-By: Codex <codex@openai.com>
@h4rkl h4rkl changed the title device-tegu 0.1.1: guarded boot and touch package device-tegu 0.1.1: public-kernel boot, native display and guarded touch Oct 27, 2026
@derekross

Copy link
Copy Markdown
Owner

Thanks for working through everything. I went through my earlier points one by one against the new head:

  • The overlays are gone, and the kernel now comes from the public board, touch and display pull requests. That was the main blocker.
  • The descriptor: device/tegu/device.conf is unchanged, and the package's copy is identical to it (your test checks that). Your notes record what I needed to know: the September 2025 header values boot on your phone with index-0 footers, and footer-free images don't. So footers on the shared descriptor wait for W4HO-ham's result, as you say.
  • The notes: a dated entry for your phone, with each kernel release, the tree it came from and how slot B was written. Thank you for correcting the slot A result in the same entry rather than leaving the earlier claim.
  • The touch timer: the synced marker before any modprobe, kept on failure and timeout, plus --retry, is what I asked for, and test/touch-start covers every path. With ACPM and the PMIC built in, the marker really gates the touch driver alone, and the README says so.
  • The s2mps11 blacklist, the README's rescue line, and the clock floor (now omamobile-firstboot 0.1.3: seed an offline clock before key setup #97) are all done.

tools/pr-check and the package's tests pass here. (I'll approve the CI run.) Two new things came with this push:

  1. kernel.sources pins old revisions on a fork. The base 9386dfaa1d5d is an earlier head of kernel omamobile-audio 0.5.3: the boost converter off below gain 17, DRE and the jump rule by stage; AOC-PLAN C9j #81, which has been force-pushed since (its head is now 8c0c38e1dbe8). Three of the picks are an earlier Touch batch 4: landscape layouts for the home, call card, quick settings, drawer and recents (omamobile-shell 0.2.30) #90. Only the panel commit has merged. Commits that a force-push dropped can vanish from a fork, and then the recipe can't be rebuilt. Once Speakers: the bottom CS35L41's protection model runs away with DRE on below stock's gain (media muted since 2026-10-26) #80, omamobile-audio 0.5.3: the boost converter off below gain 17, DRE and the jump rule by stage; AOC-PLAN C9j #81, device-lynx 0.2.0: the device package, the Arch root and the Wi-Fi plan #88 and Touch batch 4: landscape layouts for the home, call card, quick settings, drawer and recents (omamobile-shell 0.2.30) #90 are merged, please point it at omamobile commits in derekross/linux-omarchy-mobile, or drop it in favour of a KERNEL_DIR on the published branch plus device/tegu/kernel.config, as the other devices do. I'd lean towards dropping it. Until then it's fine in a draft.
  2. The module cleanup. Your notes trace the deleted modules to kernel-modules-hook. That package is in Omarchy's base package list, and Omarchy's installer enables linux-modules-cleanup.service, so I suspect every phone has it, the Pixel 7 Pro included. I'll check mine. If it's there, the fix belongs in a shared place, as the clock floor did, and the tegu drop-in can go. Could you say which package installed it on your phone, in case it came from somewhere else?

Minor: pkgrel should start at 1 when the package first lands on main. Your note that reboot-to bootloader comes back to a normal boot on the 9a is worth a line in the recovery notes next to the button combination, since buttons are then the only way into fastboot.

This stays a draft until the kernel PRs land and W4HO-ham has seen the footers boot, but from my side the package itself is close.

@derekross

Copy link
Copy Markdown
Owner

@h4rkl, I missed one thing in my last review, sorry. vendor/modprobe.d/omamobile-tegu-display.conf sets options gs_dsim_cmd allow_tx=1 for every panel.

Google's tegu device tree lists three panels (TG4A, TG4B and TG4C), and gs-dsim-cmd can't read the panel's ID yet, so it can't tell which one it's driving. TG4B's rate switch sends more than TG4C's, so a TG4B phone given TG4C's commands would get half a rate switch. On derekross/linux-omarchy-mobile#90 we agreed the guard goes in the tegu device package: turn on allow_tx only when the bootloader names google-tg4c. Any other panel then gets no commands and keeps the bootloader's picture. The kernel side was accepted on that basis, and W4HO-ham's 9a reports exynos_drm.panel_name=google-tg4c.2d008004.

A modprobe.d options line can't be conditional, so one way is an install line that hands the load to a small script:

# omamobile-tegu-display.conf
install gs_dsim_cmd /usr/lib/omamobile/omamobile-tegu-dsim-load
#!/bin/sh
# Native DSI commands only for the panel they were written for (TG4C).
case " $(cat /proc/cmdline) " in
*" exynos_drm.panel_name=google-tg4c"*)
	exec /usr/bin/modprobe --ignore-install gs_dsim_cmd allow_tx=1 ;;
esac
exec /usr/bin/modprobe --ignore-install gs_dsim_cmd

Please add a test case for each branch, with the command line passed in so it doesn't read the host's /proc/cmdline. Use whatever shape fits the package; what matters is that no panel other than google-tg4c gets allow_tx.

Two small things while you're there:

This is still a draft and waits on the kernel PRs either way, so there's no hurry.

1 similar comment
@derekross

Copy link
Copy Markdown
Owner

@h4rkl, I missed one thing in my last review, sorry. vendor/modprobe.d/omamobile-tegu-display.conf sets options gs_dsim_cmd allow_tx=1 for every panel.

Google's tegu device tree lists three panels (TG4A, TG4B and TG4C), and gs-dsim-cmd can't read the panel's ID yet, so it can't tell which one it's driving. TG4B's rate switch sends more than TG4C's, so a TG4B phone given TG4C's commands would get half a rate switch. On derekross/linux-omarchy-mobile#90 we agreed the guard goes in the tegu device package: turn on allow_tx only when the bootloader names google-tg4c. Any other panel then gets no commands and keeps the bootloader's picture. The kernel side was accepted on that basis, and W4HO-ham's 9a reports exynos_drm.panel_name=google-tg4c.2d008004.

A modprobe.d options line can't be conditional, so one way is an install line that hands the load to a small script:

# omamobile-tegu-display.conf
install gs_dsim_cmd /usr/lib/omamobile/omamobile-tegu-dsim-load
#!/bin/sh
# Native DSI commands only for the panel they were written for (TG4C).
case " $(cat /proc/cmdline) " in
*" exynos_drm.panel_name=google-tg4c"*)
	exec /usr/bin/modprobe --ignore-install gs_dsim_cmd allow_tx=1 ;;
esac
exec /usr/bin/modprobe --ignore-install gs_dsim_cmd

Please add a test case for each branch, with the command line passed in so it doesn't read the host's /proc/cmdline. Use whatever shape fits the package; what matters is that no panel other than google-tg4c gets allow_tx.

Two small things while you're there:

This is still a draft and waits on the kernel PRs either way, so there's no hurry.

derekross added a commit that referenced this pull request Oct 28, 2026
…wenty-sixth rounds (#127)

* docs/review: 19 lessons and 3 corrections from the twenty-fifth round

The confirmed candidates from round 25 (L-260 to L-278): the 9a slot B
marking as a devinfo question, cross-repository links, squash-merged
stacks and version files, stale hand-built prebuilts, and before-merge
Pixel 7 Pro runs on omamobile-int. C-16 to C-18 correct our own earlier
comments on kernel #98, kernel #80 and #74; L-241 is corrected in place.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs/review: 15 lessons from the twenty-sixth round

L-279 to L-293: the 9a's slot B hold and what made devinfo writable
(#125), per-device flags checked by building both command lines
(#101), env defaults in the shared build library and CI waiting for
approval (#79), GLib retry paths and radio stops checked at the
controller (#99), silent re-pushes and stacks with several tops (the
tegu stack), and two of our own: merge only after every check has
finished (#126), and an empty diff is checked for empty inputs
(kernel #123).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@W4HO-ham

Copy link
Copy Markdown
Contributor

Hi h4rkl, W4HO here, the other 9a. Thanks for building on the public kernel PRs; that's the right base.

So we don't duplicate, here is where my phone stands on the same kernel line: display at 120 Hz on the panel driver, GPU (Panthor, DVFS), touch, battery and charging, Wi-Fi, Bluetooth, haptics and torch, speakers and sensors through the AoC, three cameras, NFC (reads a payment card), fingerprint (unlocks the lock screen), modem ONLINE, s2idle with wake. GNSS is the one link still open (an SPI timing problem, being worked on #138). The bring-up for all of that runs from scripts and units on the phone that I never packaged; I'm packaging them now as omamobile-device-tegu and will open that PR shortly.

I'd suggest we treat that one as the device package and rebase the pieces of this PR onto it. Two of yours I'll carry over as they are: the linux-modules-cleanup drop-in and the retry marker around a risky driver start. Two notes on this PR meanwhile: max_refresh=60 isn't needed with the public panel driver (120 Hz is what my phone runs all day), and Derek's point about allow_tx only for google-tg4c stands.

On the AVB footer question: I'll run the footered-image test on my phone (the 2025-09 bootloader) and post the result here, so the shared descriptor can move.

@W4HO-ham

Copy link
Copy Markdown
Contributor

The AVB footer result from the 2025-09 phone, and it turns out every boot here has been the test: my push kit's descriptor carries AVB_FOOTERS="boot:0x4000000", AVB_ROLLBACK_INDEX=1757030400 and AVB_SECURITY_PATCH=2025-09-05, which are stock BP3A.250905.014's own values (avbtool info_image on the saved slot A boot_a.img: rollback index 1757030400, com.android.build.boot.security_patch 2025-09-05, os_version 16). So the boot image I boot from slot B has had a SHA256_RSA4096 hash footer with those values all along, padded to the 64 MiB partition, signed with a throwaway key; init_boot goes in without a footer (8 KiB) and boots too. Dozens of boots, no fastboot fallback from the footer side.

So for the shared descriptor, per Derek's rule (the oldest owner's values, never raised), these three lines are what I'd propose; they're exactly what main's bin/omamobile images already knows how to apply. What's left is your side: whether your newer bootloader takes a boot image whose rollback index is the 2025-09 one, which is below what your stock stored. If it refuses, that's the finding Derek described, and deriving the index from the owner's own slot A at install time would be the way.

@W4HO-ham

Copy link
Copy Markdown
Contributor

The package I mentioned is up: #152, omamobile-device-tegu 0.2.0. It carries your linux-modules-cleanup drop-in and the scratch-root test pattern, credited in the description.

@derekross

Copy link
Copy Markdown
Owner

@h4rkl, W4HO-ham has opened #152, a fuller omamobile-device-tegu (0.2.0) built from the bring-up on his phone. It carries your module-cleanup drop-in and your scratch-root test pattern, and eight of its files are the same as yours. Two packages with the same name can't both land, so here's how I'd like to bring them together. Your work stays in either way.

The package goes through #152. It covers what yours does and more, so once it merges the package part of this PR is superseded, and I'd close this one then (or you can turn the branch into the follow-ups below, whichever you prefer). This PR also conflicts with main in tests/all now. That line isn't needed: tests/packages already runs every package's tests.

What I'd still like from you, as separate pull requests:

  1. Your phone's notes (the dated NOTES entry) and device/tegu/kernel.config, in a device/tegu PR. The notes are the only record of the second 9a, and we want the kernel config in the repository. Please also add the line about reboot-to bootloader coming back to a normal boot, next to the button combination. Please leave out kernel.sources and prepare-kernel: once the kernel PRs merge, the published branch plus kernel.config is the recipe. One thing to clear up there: your notes say slot A "is not currently a qualified rollback", while this PR's description says a stock A recovery boot was verified. Which is current? A phone without a working stock slot A matters under CONTRIBUTING §3.1, so I'd like the notes to say plainly what state it's in.
  2. Your touch marker, as a small follow-up on top of omamobile-device-tegu 0.2.0: the Pixel 9a's bring-up as a package #152 if your phone still needs it. 0.2.0 doesn't gate the touchscreen, so with your =m touch driver it would autoload at boot. With ACPM and the mailbox built in, that may be fine now. Either way, please say which.

Before you install 0.2.0 on your phone, please wait until #152's current round of changes is in. As it stands it would set allow_tx=1 on a panel we haven't identified, and on your kernel, which has the display but no GPU node, it would leave gs_decon unloaded and the screen dark. I've asked for both to be fixed there. The panel name helps with the first one, so could you post it (tr ' ' '\n' < /proc/cmdline | grep -i panel_name)? That's still the open question from my last comment.

The questions I asked earlier about this PR's own files (pkgrel, the Codex-authored commit, the 60 Hz cap) become moot once the package goes through #152. Thank you for getting the second 9a this far. The footer results from your phone and the touch work are a real help to both of you.

derekross pushed a commit that referenced this pull request Oct 29, 2026
The Pixel 9a's (tegu) bring-up moves from hand-copied files into a
device package, on in-tree drivers only. Built on h4rkl's #74.

At boot (vendor wants links), two units:
- omamobile-tegu-graphics: loads the GPU (panthor), display (gs_decon),
  haptics, torch, battery gauge and Bluetooth UART, each blacklisted
  against autoload, after a synced hang marker. Each step keys on its
  own node; a load or bind that returns and fails is logged and skipped
  (a GPU without mali_csffw.bin keeps the display), and only a step that
  never returns keeps the marker, so the next boot leaves them off until
  --retry. gs_dsim_cmd.allow_tx (DSI commands, 120 Hz) is turned on
  before gs_decon only when the bootloader names the google-tg4c panel
  (with or without its id suffix); any other panel stays read-only at
  60 Hz. The session's side ships as /usr/share/uwsm/env.d (KMS card,
  hardware GL only when the GPU came up).
- omamobile-tegu-usb-rescue: closes the MAX77779's USB data switch after
  a replug while no Type-C driver owns it, through a C helper that checks
  the board, the chip's identity and VBUS (twice), never forces an I2C
  address, and reads back its one write; it reads VBUS first, so the
  cable out costs a register read and no log lines.

Also: the Bluetooth address from the bootloader's DT, a charge limit
from /etc/omamobile/charge-limit, s2idle only, the reboot watchdog (no
runtime watchdog), the storage rule, usb0 as a fallback route, Arch's
module cleanup held off, and sleep hooks: Wi-Fi kept or reloaded as
flagged; NFC's poll loop stopped before a sleep and restarted after
(powering the ST54L off only behind
/etc/omamobile/nfc-power-off-across-sleep, off by default). The AoC
start ships without a wants link until a kernel enables its nodes.

Nothing marks a slot or touches devinfo, persist, the RPMB or Trusty's
storage. Tested on the owner's 9a (private kernel 7.3.0-rc6, five
package boots on 10-29, phone-smoke 19/19 on ffbf958); test/all runs
every script in a scratch root.

Co-authored-by: W4HO-ham <87742609+W4HO-ham@users.noreply.github.com>
Co-authored-by: h4rkl <89045610+h4rkl@users.noreply.github.com>
@derekross

Copy link
Copy Markdown
Owner

Closing this now that #152 has merged: omamobile-device-tegu 0.2.0 is built on this PR (eight of its files are yours byte for byte, and the squash credits you as co-author). Thank you for laying the groundwork.

Two things from here would still be very welcome as a new device/tegu PR: your NOTES entry and device/tegu/kernel.config. The touch-start marker and the 60 Hz cap can come as a follow-up to the package. Before you install 0.2.0 on your 9a, note that it turns on DSI commands (120 Hz) only when the bootloader names the google-tg4c panel, and the display now loads even without a GPU node. Please do tell me your exynos_drm.panel_name when you get a chance.

@derekross derekross closed this Oct 29, 2026
h4rkl added a commit to h4rkl/omandroid that referenced this pull request Nov 1, 2026
derekross#152 landed omamobile-device-tegu 0.2.0, which supersedes this branch's
package, so the package and tests/all come from main unchanged. Following
the review on derekross#74, kernel.sources and prepare-kernel are dropped; the
branch keeps the second phone's notes and device/tegu/kernel.config.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
h4rkl added a commit to h4rkl/omandroid that referenced this pull request Nov 1, 2026
Following the review on derekross#74, now that derekross#152 carries the package: the second
phone's results go into NOTES as one dated entry in newest-first order, and
device/tegu/kernel.config joins the repository so the published kernel
branch plus this fragment is the recipe.

The entry now states slot A's current state once, at the top: stock's
five boot images match the official October images and its recovery boots,
which supersedes the earlier "not a qualified rollback" line. It also notes
that reboot-to bootloader comes back to a normal boot on this phone, next
to the button combination.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross pushed a commit that referenced this pull request Nov 1, 2026
…its boots (#240)

The second Pixel 9a's record (the phone behind #74): a dated NOTES entry with slot A's state stated once and plainly (stock CP3A.261005.005, live images matching Google's by hash, a recovery boot verified, a full Android boot not), the corrected "not a qualified rollback" line and the `reboot-to bootloader` note, plus `device/tegu/kernel.config`, the fragment those boots ran. The maintainer marked the fragment bring-up only (its shared lines go once #227 lands; touch as a module is a test choice) and gave it the MIT licence line the other fragments carry.

Closes #240

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
…rekross#152)

The Pixel 9a's (tegu) bring-up moves from hand-copied files into a
device package, on in-tree drivers only. Built on h4rkl's derekross#74.

At boot (vendor wants links), two units:
- omamobile-tegu-graphics: loads the GPU (panthor), display (gs_decon),
  haptics, torch, battery gauge and Bluetooth UART, each blacklisted
  against autoload, after a synced hang marker. Each step keys on its
  own node; a load or bind that returns and fails is logged and skipped
  (a GPU without mali_csffw.bin keeps the display), and only a step that
  never returns keeps the marker, so the next boot leaves them off until
  --retry. gs_dsim_cmd.allow_tx (DSI commands, 120 Hz) is turned on
  before gs_decon only when the bootloader names the google-tg4c panel
  (with or without its id suffix); any other panel stays read-only at
  60 Hz. The session's side ships as /usr/share/uwsm/env.d (KMS card,
  hardware GL only when the GPU came up).
- omamobile-tegu-usb-rescue: closes the MAX77779's USB data switch after
  a replug while no Type-C driver owns it, through a C helper that checks
  the board, the chip's identity and VBUS (twice), never forces an I2C
  address, and reads back its one write; it reads VBUS first, so the
  cable out costs a register read and no log lines.

Also: the Bluetooth address from the bootloader's DT, a charge limit
from /etc/omamobile/charge-limit, s2idle only, the reboot watchdog (no
runtime watchdog), the storage rule, usb0 as a fallback route, Arch's
module cleanup held off, and sleep hooks: Wi-Fi kept or reloaded as
flagged; NFC's poll loop stopped before a sleep and restarted after
(powering the ST54L off only behind
/etc/omamobile/nfc-power-off-across-sleep, off by default). The AoC
start ships without a wants link until a kernel enables its nodes.

Nothing marks a slot or touches devinfo, persist, the RPMB or Trusty's
storage. Tested on the owner's 9a (private kernel 7.3.0-rc6, five
package boots on 10-29, phone-smoke 19/19 on ffbf958); test/all runs
every script in a scratch root.

Co-authored-by: W4HO-ham <87742609+W4HO-ham@users.noreply.github.com>
Co-authored-by: h4rkl <89045610+h4rkl@users.noreply.github.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…its boots (derekross#240)

The second Pixel 9a's record (the phone behind derekross#74): a dated NOTES entry with slot A's state stated once and plainly (stock CP3A.261005.005, live images matching Google's by hash, a recovery boot verified, a full Android boot not), the corrected "not a qualified rollback" line and the `reboot-to bootloader` note, plus `device/tegu/kernel.config`, the fragment those boots ran. The maintainer marked the fragment bring-up only (its shared lines go once derekross#227 lands; touch as a module is a test choice) and gave it the MIT licence line the other fragments carry.

Closes derekross#240

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.

4 participants