Repository navigation
device/akita: stage 0 notes and descriptor for the Pixel 8a - #308
Conversation
Stage 0 for the Pixel 8a (akita, zuma), from a retail phone with root and the stock CP3A.261005.005 factory image, checked against Google's GPL akita and zuma device trees at android-16.0.0_r0.10. Both slots carry CP3A.261005.005 with bootloader akita-17.0-15681527, and two checksummed backups of every partition but userdata and super are kept off the repository. The descriptor is husky's with akita's board values: the IPOP base DTB entries (this phone boots B0/B1 IPOP, husky FOPLP), dtbo entry 18 (board id 0x40406, rev 0x10000) and the 1080x2400 panel. It writes no display register: DECON0's TRIG_CON at handover is still to be read on an 8a. Images wait for the board DTS, zuma-akita.dts, not written yet. tests/storage-guard and tests/usb-product now cover the descriptor. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Hi @aninmucek, and welcome. Thank you for this. It's a very good stage 0: the backups are done before anything else, both slots are on the same build, stock is kept as the way back, and every value in the descriptor has a source in the table at the end of the notes. What I checked:
Nothing here changes any other phone: the shared tests only add akita to their lists. Two small things, neither blocking:
Your CI run is waiting for my approval because this is your first PR here, and I'll start it. Once it's green, I'm happy to merge. The next step you describe, a minimal Thanks again for such a careful start. |
|
Thanks for the careful review and the merge, and for the welcome on #1. Both small points make sense: "this phone's bootloader" in DEVICES.md until a second 8a confirms it, and a one-line pointer to the provenance table at the top of Thanks too for the |
derekross's two non-blocking points on #308. DEVICES.md now says this phone's bootloader picks the IPOP base DTB: the 8a's factory image carries all four base trees, as husky's does, and only one 8a has been seen. device.conf gets a one-line pointer to its provenance table in NOTES.md, for anyone who opens the descriptor first. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…s#308) Stage 0 for the Pixel 8a (akita, zuma), from a retail phone with root and the stock CP3A.261005.005 factory image, checked against Google's GPL akita and zuma device trees at android-16.0.0_r0.10. Both slots carry CP3A.261005.005 with bootloader akita-17.0-15681527, and two checksummed backups of every partition but userdata and super are kept off the repository. The descriptor is husky's with akita's board values: the IPOP base DTB entries (this phone boots B0/B1 IPOP, husky FOPLP), dtbo entry 18 (board id 0x40406, rev 0x10000) and the 1080x2400 panel. It writes no display register: DECON0's TRIG_CON at handover is still to be read on an 8a. Images wait for the board DTS, zuma-akita.dts, not written yet. tests/storage-guard and tests/usb-product now cover the descriptor. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
derekross's two non-blocking points on derekross#308. DEVICES.md now says this phone's bootloader picks the IPOP base DTB: the 8a's factory image carries all four base trees, as husky's does, and only one 8a has been seen. device.conf gets a one-line pointer to its provenance table in NOTES.md, for anyone who opens the descriptor first. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
What and why
Stage 0 for the Pixel 8a (akita, zuma, Tensor G3), as claimed on #1: the device notes, the descriptor and its empty board overlay, and akita's line in DEVICES.md (CONTRIBUTING §5.1, §6.3 and §6.4; the same shape as #265). Every value comes from a retail 8a with root and the stock CP3A.261005.005 factory image, checked against Google's GPL akita and zuma device trees at
android-16.0.0_r0.10. The table at the end of the notes gives each descriptor value's source.Akita is husky with three board values changed: its bootloader boots the IPOP base DTB (B0/B1 IPOP,
pkg_mode1) where husky's boots FOPLP, its board overlay is dtbo entry 18 (board_id 0x40406,board_rev 0x10000), and its panel is 1080x2400. The descriptor writes no display register (noSIMPLEFB_TRIG_CON, L-4): DECON0'sTRIG_CONat handover is still to be read on an 8a. Images wait for the board DTS,zuma-akita.dts, which isn't written yet.Refs #1
Device and build
init_boot_bfor root. No build of ours has been flashed or booted.uname -r): none: there is no akita kernel yet.Checks (no phone needed)
tools/pr-check origin/mainpassestests/allpasses (260 ok)tests/packages: no package is touchedversionbumped: no package changedCo-Authored-By:orAssisted-by:trailer, never aSigned-off-by:Also checked with the loader (L-395):
DEVICE=akita bin/omamobile initramfs-configpacks the six-nameUFS_RWand the USB product "Pixel 8a"; the overlay compiles withdtc -@.On the phone
fastboot getvar all, both slots matched with two full-OTA sideloads, a factory reset, and two checksummed backups of every partition exceptuserdataandsuper, kept private.DEVICE=akita bin/omamobile imagescan't run untilzuma-akita.dtsdoes;VENDOR_CMDLINEis husky's line [I]; the silicon revision (B0 or B1) isn't known.userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1):UFS_RWis the five slot-B boot images anduserdata, and the descriptor carries no register write or probe.No
tools/phone-smokereport: no build of ours runs on the phone yet.🤖 Generated with Claude Code