Skip to content

device/akita: M2.7 passed gate (e), Omarchy's image on the Pixel 8a - #607

Merged
derekross merged 1 commit into
derekross:mainfrom
aninmucek:device-akita-m27
Nov 10, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
aninmucek:device-akita-m27

Conversation

@aninmucek

Copy link
Copy Markdown
Contributor

Follows #456 and #509: M2.7 of BRINGUP-M2, Omarchy's image on the Pixel 8a. M2.7 passed gate (e), so M2 is done.

What and why

BRINGUP-M2 gets M2.7's results (tests 19-26) and a status that says M2 is complete. Docs only.

  • The image: DEVICE=akita tools/build-rootfs --channel development, with omamobile-device-akita 0.1.1 from the signed development channel. Thank you for publishing it.
  • The install: tools/install-phone --reinstall, with --dry-run first.
  • The pass conditions:
    • the user logs in over SSH;
    • the guard's flags hold under the full image;
    • reboot-to bootloader works from Omarchy (27 s);
    • a second boot reads running with no failed units, in 2.0 s + 3.2 s;
    • phone-smoke's required rows, the session included (Hyprland and the Omarchy shell), are ok.
  • The runbook:
    • The pass condition "systemctl --failed is empty" now says "from the second boot on". systemd-firstboot fails once (208/STDIN, console=null), as lynx's NOTES and panther's BRINGUP-M1 record.
    • "Watch for" says how to wake the display. The lock blanks it after 10 s, and with no touch or key input yet only SSH (omarchy-shell lock wake) brings it back.
  • tools/phone-smoke: zuma's two exynos-clkout lines are known #584: thank you for the careful explanation, and you're right. The two exynos-clkout lines are left as "new" in the report below (main's tool, a51ef02). This kernel predates linux-omarchy-mobile#209, and the findings say the next akita kernel should stop printing them.
  • Other findings:
    • one preset line for the masked systemd-networkd-wait-online.service;
    • the USB link didn't come back after the laptop lost power, while fastboot enumerated at once;
    • the clock survives a reboot through systemd's saved time.
  • Not changed here: akita's DEVICES.md row. You said you'd update it yourself.

Device and build

  • Phone: Pixel 8a (akita)
  • Kernel release (uname -r): 7.3.0-rc6-omamobile-push1-gabcd6aac51cf (omamobile at abcd6aac5, no overlay)
  • Packages changed, with versions: none (docs only)

Checks (no phone needed)

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

On the phone

  • I ran this on my own phone, booted into this build
  • Runbook steps passed (plan, step, result): BRINGUP-M2 M2.7, tests 19-26: pass (gate e)
  • What I did not test: Suspend (not until the Pixel 8 Pro's U6), anything needing touch, the GPU or the radios, and pacman -Syu on the phone (no network yet)
  • 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 boot, main's tool)

phone-smoke: akita

Kernel 7.3.0-rc6-omamobile-push1-gabcd6aac51cf, tools at a51ef02, 2026-11-10T09:36Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-gabcd6aac51cf, slot b, up 243s
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, 4 error lines in dmesg (2 known, 2 new)
new dmesg errors not ok exynos-clkout exynos-clkout: probe with driver exynos-clkout failed with error N x1; exynos-clkout exynos-clkout: cannot match parent device x1
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card0-Unknown-1 connected, 1080x2400
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 not ok no multitouch input device
buttons skip no key input device found by name
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.57.0-3.2, libcamera 0.7.2-4.23, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.2-1, omamobile-apps 0.2.2-1, omamobile-device-akita 0.1.1-1, omamobile-firstboot 0.1.3-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.38-1, omamobile-owl-widgets 0.1.2-1, omamobile-shell 0.2.108-1, omamobile-voice 0.1.0-1, omaphone 0.2.3-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1

🤖 Generated with Claude Code

BRINGUP-M2 gets M2.7's results (tests 19-26): build-rootfs, the dry run
and the install, the first boot, SSH logins, the guard under the full
image, phone-smoke, reboot-to bootloader from Omarchy, and a second boot
that comes up running with no failed units. The status says M2 is done.

The runbook's pass condition notes that systemd-firstboot fails once on
the first boot (console=null, as on lynx and panther), and "Watch for"
says how to wake the display while there is no touch or key input.

Findings: the two exynos-clkout lines stay new in phone-smoke until a
kernel with linux-omarchy-mobile#209 is on the phone (derekross#584 is closed);
a preset line for the masked wait-online unit; the lock's 10 s blank;
the USB link not coming back after the host lost power; and the clock
surviving a reboot through systemd's saved time.

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

Copy link
Copy Markdown
Owner

Thank you, this is a clean close to M2, and a pleasure to check. Everything I could verify from here holds: the kernel commit and the three kernel PRs' merge dates, the image's source commit (main at b5207b8 plus the one phone-smoke commit, which touches nothing in the image), the installer options, and the smoke report matching tests 24 and 26. Narrowing "systemctl --failed is empty" to the second boot onwards, with the reason, is the right change to the runbook, and the note on waking the screen over SSH will save the next 8a owner some worry. Thanks also for leaving the two exynos-clkout lines as "new" and saying why.

I'm merging it as it is. Two small things for your next akita PR, neither worth another push here:

  • The USB finding. "Our kernel doesn't notice a cable coming back yet" may well be right, but it wasn't tested. On the Pixel 7 Pro and the 9a the same symptom comes from the charger IC opening the USB2 data switch when VBUS drops, with no Type-C driver yet to close it again, and a laptop losing power looks like an unplug to the phone. I'd word it as "probably the same as on the 7 Pro and the 9a, not checked on akita" until someone reads the switch.
  • Slot B's tries. By my count the phone ended the session with two left (test 26's --set-active=b, then one boot). A line saying so at the end of a session helps whoever boots it next.

I'll update akita's row in DEVICES.md myself, as promised: it still says "no Arch root yet", which hasn't been true since #456. Congratulations on getting Omarchy's session up on the 8a.

@derekross
derekross merged commit c5f3bbe into derekross:main Nov 10, 2026
2 checks passed
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
…erekross#607)

The Pixel 8a's M2.7 record: gate (e) passed, with Omarchy's image booting on the phone from slot B. Notes only; no package or script changes.

The DEVICES.md row for akita is updated separately.
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