Skip to content

device/tegu: the second 9a's notes and the kernel config fragment - #240

Closed
h4rkl wants to merge 1 commit into
derekross:mainfrom
h4rkl:tegu-second-phone-notes
Closed

h4rkl wants to merge 1 commit into
derekross:mainfrom
h4rkl:tegu-second-phone-notes

Conversation

@h4rkl

@h4rkl h4rkl commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

What and why

Follow-up #1 from #74 (comment), now that #152 carries the package.

  • device/tegu/NOTES.md: the second 9a's results as one dated entry (2026-10-28), in newest-first order. It states slot A's current state once, at the top: stock CP3A.261005.005, all five live boot images match the official October images by hash, and stock recovery boots (recovery ADB and its shell answered). That is not a full Android boot. This replaces the draft's "not a qualified rollback" line, which was written before the recovery check. The entry also notes that reboot-to bootloader came back to a normal boot on this phone, next to the button combination.
  • device/tegu/kernel.config: the fragment these boots used. kernel.sources and prepare-kernel are left out, as asked.

The panel name and the answer on the touch marker (follow-up #2) will follow in a comment.

Device and build

  • Phone: Pixel 9a (tegu), the second one; docs and kernel config only
  • Kernel release (uname -r): the releases each result rests on are in the entry (…-g9ea0e19f8dc2, …-g9386dfaa1d5d, …-gde2e0689c517)
  • Packages changed, with versions: none

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes (CI; no scripts change)
  • tests/packages passes (no package changes)
  • 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

On the phone

  • The results in the entry are from my own phone
  • What I did not test: a full stock Android boot on slot A, a clean install, 0.2.0 on this phone
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)

🤖 Generated with Claude Code

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

Copy link
Copy Markdown
Owner

Thank you, @h4rkl. This is just what I hoped for: the second 9a's record, with slot A's state stated plainly. Stock CP3A.261005.005 with the live images matching Google's by hash, and a verified recovery boot while being clear that a full Android boot wasn't tested, is exactly the answer §3.1 needs. Thanks for correcting the old "not a qualified rollback" line, and for the reboot-to bootloader note.

I merged it (a squash on main, authored by you) with two small changes to kernel.config: a header saying it's the fragment of the 2026-10-28 boots and bring-up only (the release kernel is one build from the shared fragment; the eUSB2 PHY, mailbox, ACPM and S2MPG14 lines go once #227 puts them there; TG4C is already shared; touch as a module is a test choice), and the MIT SPDX line the other fragments use. Two wording nits for a later pass: "Omarchy on camera" reads oddly (filmed?), and "(the cap this branch's package set; 0.2.0 drops it)" is missing a word. I'm looking forward to the panel name and the answer on the touch marker.

@derekross derekross closed this in f53b272 Nov 1, 2026
derekross pushed a commit that referenced this pull request Nov 12, 2026
BRINGUP-M3 records akita's input milestone on `omamobile` `fc7086a68` plus linux-omarchy-mobile #240 and #241: Power wakes and locks, the GT9895 touchscreen works after its supplies read 3.0 V and 1.8 V with no consumer, and the panel carries the measured 64 x 141 mm (Google's 70 x 149 is larger than the glass). NOTES and BRINGUP-M2 take the two wording fixes from #607, and the `ufs-probe` overlay's bootargs gain `mem_sleep_default=s2idle`. Two one-off userspace findings (an app-switcher disconnect and a touch lockout) are recorded, not filed; suspend is untested.

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
…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>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ekross#650)

BRINGUP-M3 records akita's input milestone on `omamobile` `fc7086a68` plus linux-omarchy-mobile derekross#240 and derekross#241: Power wakes and locks, the GT9895 touchscreen works after its supplies read 3.0 V and 1.8 V with no consumer, and the panel carries the measured 64 x 141 mm (Google's 70 x 149 is larger than the glass). NOTES and BRINGUP-M2 take the two wording fixes from derekross#607, and the `ufs-probe` overlay's bootargs gain `mem_sleep_default=s2idle`. Two one-off userspace findings (an app-switcher disconnect and a touch lockout) are recorded, not filed; suspend is untested.

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