[aninmucek]

Follows #607: akita's M3 (input), in BRINGUP-M3. The buttons passed gate (f) and touch passed gate (g): Power wakes the screen, the PIN pad unlocks by touch, and the shell and on-screen keyboard work by hand.

What and why

Docs only:

• device/akita/BRINGUP-M3.md (new): the plan, facts, runbook and results (tests 27-34). The kernel side:
  • linux-omarchy-mobile#238: the buttons and mem_sleep_default=s2idle, merged;
  • device/tegu: the second 9a's notes and the kernel config fragment #240: the S2MPG14 supply setter, open;
  • omamobile-shell 0.2.62: one voice bar, a themed keyboard with an action row, and pill gestures #241: the touch supplies, the GT9895 touchscreen and the panel size, stacked on device/tegu: the second 9a's notes and the kernel config fragment #240, open.
• device/akita/NOTES.md:
  • an M3 section: the GT9895 from stock's firmware headers, ABL's 3.3 V on LDO4M against stock's 3.0 V, and the S2MPG14 RTC, which now keeps the clock across reboots;
  • the panel-size line now cites stock's DPI.
• device/akita/BRINGUP-M2.md, your two notes from device/akita: M2.7 passed gate (e), Omarchy's image on the Pixel 8a #607:
  • the USB finding now reads "probably the same as on the Pixel 7 Pro and the 9a, not checked on akita";
  • M2.7's session ends with slot B's tries (2).
• device/akita/overlays/ufs-probe.dtso: its copy of the board file's bootargs gains omamobile-device-tegu 0.2.4: Wi-Fi at boot through the zumapro PCIe host #238's mem_sleep_default=s2idle, so the overlay doesn't silently revert it.

Findings worth a look:

• The session is slow. There's no GPU and no cpufreq on akita yet.
• The app switcher, once: closing an app from it made Hyprland drop the shell's Wayland connection ("error in client communication"), and the shell relaunched. It didn't happen on the next try, so there's no issue yet.

Device and build

• Phone: Pixel 8a (akita)
• Kernel release (uname -r): 7.3.0-rc6-omamobile-push1-g7b13e4166249 (omamobile fc7086a68 + device/tegu: the second 9a's notes and the kernel config fragment #240 + omamobile-shell 0.2.62: one voice bar, a themed keyboard with an action row, and pill gestures #241)
• Packages changed, with versions: none (docs only; the overlay is a bring-up probe, never default)

Checks (no phone needed)

• tools/pr-check origin/main passes
• tests/all passes (563 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-M3 M3.1 (gate f): pass; M3.2: pass with device/tegu: the second 9a's notes and the kernel config fragment #240; M3.3: pass; M3.4 (gate g): pass
• What I did not test:
  • Suspend;
  • a long idle with the screen off;
  • the ufs-probe overlay with its new bootargs (a bring-up probe, not booted since M2.3);
  • anything needing the GPU, Wi-Fi or sound
• 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 (M3.4's second boot, main's tool)

phone-smoke: akita

Kernel 7.3.0-rc6-omamobile-push1-g7b13e4166249, tools at c3cfd86, 2026-11-11T01:14Z.

Check	Result	Detail
boot (required)	ok	kernel 7.3.0-rc6-omamobile-push1-g7b13e4166249, slot b, up 28s
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, 2 error lines in dmesg (2 known, 0 new)
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	ok	Goodix Berlin Capacitive 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.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

[derekross]

Thank you, @aninmucek. This is a good record: each step ends with slot B's tries, the supplies were read back with nothing connected before the touch controller was powered, the first driver load was by hand behind a blacklist that you then removed, and the "what I didn't test" list is honest. Thanks also for the two wording fixes from #607 and for catching that the ufs-probe overlay would have reverted the s2idle default; I compared its bootargs with the board file's on omamobile and they match.

tools/pr-check passes here, CI is green, and it merges cleanly onto today's main.

One change, please. It's the same point as on linux-omarchy-mobile#241: the NOTES line about the panel size used to say that 70 × 149 mm "is larger than a 6.1-inch 20:9 panel (about 64 × 141 mm), so no size goes into the board file yet", and this PR replaces that with stock's DPI and "the board file carries it since M3". Both halves are true: Google's panel driver and stock's DPI say 70 × 149, and the glass is about 64 × 141 (Google's touch node says goodix,panel-height-mm = <141>). Please keep the sentence that says the value is larger than the glass, and let this line, the open question in BRINGUP-M3 and test 34 follow what we settle on #241.

Two small things, not blockers:

• The 8a's row in docs/DEVICES.md still says "no Arch root yet". Once the two kernel PRs are in, could you send a row update for what M2.7 and M3 showed (or tell me and I'll do it in my next pass)?
• The plan says device/tegu: the second 9a's notes and the kernel config fragment #240 and omamobile-shell 0.2.62: one voice bar, a themed keyboard with an action row, and pill gestures #241 are open; a date on that line saves a touch-up later.

I'll merge this right after #241.

[aninmucek]

Thanks. Pushed one more commit, 0c5c922:

• The panel size follows omamobile-shell 0.2.62: one voice bar, a themed keyboard with an action row, and pill gestures #241. NOTES keeps the sentence that Google's 70 × 149 mm, and stock's DPI with it, is larger than the glass. It adds that the lit area measures 64 × 141 mm, which is what omamobile-shell 0.2.62: one voice bar, a themed keyboard with an action row, and pill gestures #241 now carries. BRINGUP-M3's facts, design and open question follow, and test 35 is the boot with the measured size: Hyprland reports 64 × 141, the keyboard is at its normal height, and phone-smoke has 0 new lines.
• The line about device/tegu: the second 9a's notes and the kernel config fragment #240 and omamobile-shell 0.2.62: one voice bar, a themed keyboard with an action row, and pill gestures #241 now says "open as of 2026-11-11".
• A lockout, seen once. While I measured the screen, the session stopped taking touch: first in the clipboard panel, then on the lock screen, where swiping up no longer showed the PIN pad. The touches still reached the kernel. A reboot fixed it. Opening the panel on purpose and locking over it unlocks normally, so the panel wasn't the cause. The journal only has leads: on-screen-keyboard keymap reloads and Qt text-input focus warnings just before the lock. It's recorded in BRINGUP-M3's findings, not filed, until it happens again.

DEVICES.md: if you're still happy to update akita's row in your next pass, please do. Otherwise I'll send it once #241 is in.