Skip to content

omamobile-omarchy 0.1.33: About fits a phone's screen - #431

Merged
derekross merged 1 commit into
derekross:mainfrom
jkjoplin:omarchy-about-fits-the-phone
Nov 7, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
jkjoplin:omarchy-about-fits-the-phone

Conversation

@jkjoplin

@jkjoplin jkjoplin commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

What and why

Omarchy's About (the menu's About, omarchy-launch-about) puts the logo (about.txt, 54 columns) beside fastfetch's module boxes (54 columns), 118 columns with the config's padding, and the config turns line wrapping off. On a phone the About window is the width of the screen, 63 columns on the Pixel 7 Pro, so each of the 28 module lines showed only its first character (a box corner or an icon) to the right of the logo. TOUCH-PLAN 3.5: "a compact About layout under 600 px".

Patch 0030 has omarchy-launch-about pick the layout from the terminal's size before each draw:

  • narrower than the side-by-side layout: --logo-position top, which needs 56 columns and 57 rows with Omarchy's logo;
  • too small for that as well, such as with the on-screen keyboard up (41 rows): --logo none, the modules alone;
  • wide enough (what fit_window sizes a desktop window for), a user's own fastfetch config, or no logo file: fastfetch as before.

The sizes come from the measurement fit_window already makes (the logo file and fastfetch --logo none), taken again when the logo changes, and the render loop already redraws on every resize, so the layout follows the keyboard going up and down. It costs one more fastfetch --logo none before the first frame: 240-330 ms on the Pixel 7 Pro (three runs). Marked as a candidate for upstream Omarchy: 4.5.0's launcher, reworked since 4.0.6, still has only the side-by-side layout.

Numbered 0030 because #420 uses 0029.

No window rule is needed. On Hyprland 0.57 with omamobile-shell 0.2.100, About opens maximized (480x952, 58 rows by 63 columns) through phone.lua's maximize rule, though Omarchy floats it by class. Hyprland also refuses fit_window's resize and center on that window: sent by hand, they answer "Window is fullscreen" and "No floating window found", and the window stays at 480x952.

Device and build

  • Phone: Pixel 7 Pro (cheetah)
  • Kernel release (uname -r): 7.3.0-rc6-omamobile-push1-g1cb4bd36f3be
  • Packages changed, with versions: omamobile-omarchy 0.1.33

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes (415 ok; skipped for missing local tools: AOSP mkbootimg twice, dtc, and a root image in out/)
  • tests/packages omamobile-omarchy passes; test/patches.py applies the series with --fuzz=0 to the real omarchy 4.0.6-1 aarch64 package (28 applied, none upstream), 231 ok, none skipped
  • Each changed package has its version bumped, and the new version is in the commit subject
  • 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:

The 0030 checks in test/patches.py use a stand-in fastfetch as big as Omarchy's (54x28 modules, a 54x26 logo):

  • the layout chosen at nine terminal sizes, including the edges: 57 rows and 56 columns get the logo on top, one row or column fewer gets none, and 118 columns get fastfetch as before;
  • a user's own fastfetch config, and no logo file;
  • About's real render loop under script(1) at 61x63, 41x63 and 29x118, where the fastfetch that draws on the terminal gets --logo-position top, --logo none and nothing, and a key still closes it.

With 0030 moved out of the series, the five checks of a narrow terminal fail and the as-before ones pass.

On the phone

  • I ran this on my own phone, booted into this build: built natively with tools/phone-install-package (as 0.1.33-0, so a channel release of 0.1.33-1 replaces it). The package's hook applied 28 patches, and the patched /usr/bin/omarchy-launch-about is byte-identical to the one the laptop tests run.
  • Runbook steps passed: TOUCH-PLAN 3.5, About from the menu:
    • With the real fastfetch, the phone measures the same room as the stand-in: 118 columns side by side, 56 by 57 with the logo on top.
    • Keyboard hidden (58x63): the logo above the modules, every box whole.
    • Keyboard up (41x63): the modules alone, every box whole.
    • Unpatched at 63 columns, on the same phone: one character of each module line.
  • What I did not test:
    • A desktop. My laptop runs Omarchy 4.5, which this patch doesn't apply to. On a desktop the patch adds the measurement and nothing else at the width fit_window sizes for; the tests cover 118- and 136-column terminals.
    • A first launch on a desktop, before fit_window has sized the float. If Omarchy's 920x480 float is narrower than 118 columns, the first frame is the stacked layout until the resize redraws it, where it was a cut side-by-side one before.
    • A rebranded logo, or a user's own fastfetch config on a phone.
    • Any phone other than the Pixel 7 Pro.
  • 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

phone-smoke: cheetah

Kernel 7.3.0-rc6-omamobile-push1-g1cb4bd36f3be, tools at eb5bc2d, 2026-11-04T22:38Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-g1cb4bd36f3be, slot b, up 7526s
storage guard (required) ok 55 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 95G free
kernel health (required) ok no oops or BUG; 0 WARN, 218 error lines in dmesg (11 known, of them ASoC no backend DAIs (PipeWire probe) x1, 207 new)
new dmesg errors not ok wc-mbox N: Try increasing MBOX_TX_QUEUE_LEN x148; cpif: rx_demux: PCIE: ERR! N is not opened x19; cpif: pass_skb_to_demux: PCIE: N<N: ERR! N>recv_skb fail (N) x19
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card2-DSI-1 connected, 1440x3120
GPU ok render node on panthor
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 ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered false
battery ok 100% Charging, 31 °C
sound cards ok googleaocsndcar
sensors ok Accelerometer AmbientLight Proximity
cameras ok 4 listed by libcamera
thermal ok hottest zone 31 °C

Packages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.2-1, omamobile-apps 0.2.2-1, omamobile-audio 0.5.13-1, omamobile-device-cheetah 0.1.44-1, omamobile-fingerprint 0.1.15-1, omamobile-firstboot 0.1.3-1, omamobile-gnss 0.2.7-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-modem 0.1.16-1, omamobile-omarchy 0.1.33-0, omamobile-owl-widgets 0.1.2-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.100-1, omaphone 0.2.3-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1

"new dmesg errors" is from boot, not this change: every error line in this boot's dmesg is from its first 41 seconds, and the three listed (the AoC mailbox and the modem interface) are at 16-21 s, as the modem stack starts, which it does at boot on a provisioned phone (the 2026.11.03 release notes). About was tested about two hours after boot.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TTVics5jHkiz34wzjZWkb9

Omarchy's About (omarchy-launch-about, the menu's About) shows the logo
(about.txt, 54 columns) beside fastfetch's modules (54 columns), 118
columns in all with the config's padding, and the config turns line
wrapping off. A phone's About window is the width of the screen, 63
columns at Omarchy's terminal font on a Pixel 7 Pro, so the logo filled
it and every module line was cut to a single character.

Patch 0030 gives a terminal narrower than that the logo above the
modules (56 columns by 57 rows with Omarchy's logo), and one too small
for that as well, such as a phone with its on-screen keyboard up, the
modules alone. The room comes from the measurement fit_window already
makes (the logo file and fastfetch --logo none), so a window fit_window
has sized, as on a desktop, renders as before, and a user's own
fastfetch config is left alone. Applies with --fuzz=0 to Omarchy
4.0.6-1 (aarch64); test/patches.py checks the layout chosen at nine
terminal sizes against a stand-in fastfetch as big as Omarchy's, and
runs About's render loop under script(1) at 61x63, 41x63 and 29x118.
Without the patch, the five checks of a narrow terminal fail.

The window needs no rule of its own: on Hyprland 0.57 with
omamobile-shell 0.2.100, About opens maximized (480x952) and Hyprland
refuses the launcher's resize of a maximized window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TTVics5jHkiz34wzjZWkb9
@derekross

Copy link
Copy Markdown
Owner

Thank you, @jkjoplin, for a careful, well-tested patch. The measurement reuses what fit_window already does, a
desktop and a user's own config are left alone, the tests run the real render loop at the edge sizes, and the
phone run and the smoke report are exactly what I like to see. About really is unreadable on a phone today.

Unfortunately the ground moved under it: Omarchy 4.5.0 landed this week and broke our whole patch series (#434).
I'm porting the series to 4.5.0 as omamobile-omarchy 0.1.34. I checked 0030 against the published 4.5.0-3
package: omarchy-launch-about was largely rewritten (181 to 424 lines), and two of the patch's three hunks no
longer apply. Could you redo it on top of the port once it's up? What I noticed in the new launcher:

  • fastfetch now runs through about_fastfetch (a translated copy of the config), so the measurement and the
    render both go through it.
  • fit_window takes the height from measure_layout, a real render, instead of the module count, because
    fastfetch adds a row once the logo is the taller block. The stacked layout's rows are best measured the same
    way.
  • There's a new logo shimmer animation (build_sheen). It finds the logo in a render without any logo options
    and paints frames of the logo on those cells. With the logo hidden, it would draw the logo over the module
    boxes, and with the logo on top it lines up only if the padding happens to match. It needs the same logo
    options, or to stay off when the layout isn't side by side.
  • Your test's stand-in fastfetch will need to answer --list-config-paths and --pipe false, and the launcher
    now sources omarchy-branding-about-animation.

Then please take the next free version after 0.1.34 (I'll confirm it at merge) and run About on a phone with
4.5.0 again. Two small things for then: the TOUCH-PLAN entry names 0.1.33, and I'll leave the Claude-Session:
link out of the squash message. I'll post on #434 when the port is ready. Sorry for the churn, and thanks again!

@jkjoplin

jkjoplin commented Nov 5, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for checking it against 4.5.0-3, and for the notes on the new launcher. I'll redo 0030 on top of the 0.1.34 port once it's up: through about_fastfetch, with the stacked layout measured by measure_layout, the sheen kept consistent with the layout, and the stand-in fastfetch extended for --list-config-paths, --pipe false and the branding script. Then I'll take the next free version, fix the TOUCH-PLAN entry, and run About again on the Pixel 7 Pro with 4.5.0.

@derekross

Copy link
Copy Markdown
Owner

Thanks, @jkjoplin, and sorry for the back-and-forth. Plans changed the day after my last comment: Omarchy 4.5 turned out to need more than our patch series (the update flow, /run permissions, our notification shade). So instead of shipping a partial port, our repository now carries Omarchy's own 4.0.6 packages, and phones stay on 4.0.6 until all of that is ready (#434). That will take a while.

That makes your patch useful as it is: it's written and tested for 4.0.6, which is what every phone runs. I've checked that it still applies with fuzz 0 to the 4.0.6-1 package and merges cleanly with today's main. So I'd like to merge it as it stands, at the next free version (#469 also uses 0.1.33, so I'll set the number and fix the TOUCH-PLAN line at merge, and leave the session link out of the squash message). No new phone run is needed.

For 4.5 later: #471 includes a 4.5 version of 0030 that builds on your patch, and it handles the logo shimmer by skipping it in the compact layouts. I've asked there for it to credit you or leave 0030 to you, so if you'd like to own the 4.5 port, please say so on #471. Thanks again for the careful work and the phone run!

@derekross
derekross merged commit 061dda6 into derekross:main Nov 7, 2026
2 checks passed
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
Omarchy's About draws its logo (54 columns) beside fastfetch's modules (54 columns), which needs 118 columns, and Omarchy's fastfetch config turns line wrapping off. In a phone's About window (63 columns on the Pixel 7 Pro) every module line was cut to a single character. Patch 0030 puts the logo above the modules in a terminal narrower than that, and shows the modules alone in one too small for both, such as with the on-screen keyboard up. A desktop window and a user's own fastfetch config render as before.

Checked on the Pixel 7 Pro on 2026-11-04 (Omarchy 4.0.6-1, Hyprland 0.57.0, omamobile-shell 0.2.100): the patch applies through the package's hook, and About shows every box whole at 58 rows by 63 columns and with the keyboard up. The measurement costs one more fastfetch --logo none before the first frame (240-330 ms).

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