Skip to content

moarchy 0.5.0 — gestures you choose, one surface for what is running, and Android apps that fit

Latest

Choose a tag to compare

@SimonSchubert SimonSchubert released this 19 Sep 11:31
· 30 commits to main since this release

Omarchy's look, keybindings and theming on a phone, as a flashable image for the original PinePhone and the Pixel 3a.

PinePhone

You need an SD card of 8 GB or more.

  1. Download moarchy-pinephone-0.5.0-20260919.img.xz.

  2. Write it to the card:

    # macOS (find N with: diskutil list external physical)
    diskutil unmountDisk /dev/diskN
    xz -dc moarchy-pinephone-0.5.0-20260919.img.xz | sudo dd of=/dev/rdiskN bs=4m
    
    # Linux (find X with: lsblk)
    xz -dc moarchy-pinephone-0.5.0-20260919.img.xz | sudo dd of=/dev/sdX bs=4M status=progress conv=fsync
  3. Put the card in the phone and power it on. The first boot grows the system to fill the card.

sha256 774dd9d43ce54fb270cf7ea6be0dbdcd10c7d3a80f700f4d132721a617e1f771

Pixel 3a

You need an unlocked bootloader and fastboot (Android platform-tools) on your computer. Unlocking with fastboot flashing unlock erases the phone.

  1. Download moarchy-sargo-0.5.0-20260919.tar.xz and unpack it:

    tar -xJf moarchy-sargo-0.5.0-20260919.tar.xz
    cd moarchy-sargo-0.5.0-20260919
  2. Put the phone in fastboot: power it off, hold Volume Down and tap Power. Connect it over USB.

  3. Run ./flash.sh. It overwrites boot and userdata, so Android is gone afterwards, and the phone reboots into moarchy.

sha256 aa81bc9d2e49ceab3518e866696f1c7ee6889814ca01a4e321c8ed69c3650710

After flashing

The phone logs in by itself, so there is no password to set. To reach it over SSH, open the terminal on the phone and authorise your GitHub keys:

curl -sL https://raw.githubusercontent.com/SimonSchubert/moarchy/main/scripts/authorize-ssh.sh | sh -s <your-github-user>

Already on 0.4.0? sudo pacman -Syu is the whole upgrade — nothing leaves the package set, so there is nothing to remove afterwards. If you enabled moarchy-waydroid-immersive by hand, that unit is gone in this release and the upgrade tells you to disable it: it forces the Android bars hidden, which is exactly what removes the insets an app needs.

New in 0.5.0

Four gestures that point wherever you set them. The strip, the right edge, the strip's hold and — new — a double press of the power button. The two edges drag a sheet, so they may name one: none, the drawer, the overview or the shade, and the sheet arrives from the edge that raised it, so the overview on the strip rises from the bottom rather than sliding in from the right. The two taps may name anything that opens, including any app the drawer lists. Shipped they are the drawer, the overview, the coding agent and nothing, so a phone nobody has touched behaves as it did. Settings > Shell & plugins > Gestures.

One press of the power button still blanks the screen the instant it lands; two inside 400ms undo that and fire. The first press acts and the second undoes it, rather than every press waiting 400ms to see whether a second is coming — which would put a delay on the only button this device has.

One surface for what is running. The drawer had a shelf of open apps across its top and the overview had a card per workspace, and both answered the same question. The shelf is gone, and the one thing it could do that the overview could not — close a window — is now a bin at the foot of the overview. Drop a window in it and sway sends the same close request a window manager does, so an editor with unsaved work still prompts.

Picking a window up stops being a timed hold, too. A bin is a place rather than a direction, so the lift is the ordinary drag every other gesture here makes — travel past the slop threshold — and the 500ms hold is gone rather than shortened.

Android apps fit the screen. Three things, all measured on the Pixel 3a rather than chosen:

  • They draw behind the bar and the strip and pad themselves against their own insets. 0.4.0 told every app there was no status bar at all, so each one laid itself out as though the top of the screen were free. Now the status inset's bottom lands at y=77 against this bar's 78, and the nav inset's top at 2160, which is the strip's top edge to the pixel.
  • They get the panel's density rather than the scale's. Waydroid computes 180 × scale, which is 540 here; the panel is 444 ppi. Everything was 23% too large, and — the more expensive half — Android was told the screen is 320dp wide when it is 393dp, so apps picked small-screen layouts. Spotify drew a one-column shortcut grid; it draws its normal two-column grid now.
  • Android's own gesture handle is taken out at the source, by a fabricated overlay that zeroes the dimension it draws from. 0.4.0 covered it with an opaque strip, which stopped the app's background 20px short of the screen and put a slab of chrome under every light app — a dark grey bar across the bottom of a white map.

The volume rocker shows something. It drew nothing at all before: the bindings went to wpctl, and upstream's on-screen display is told by each command that changes something, which on this phone was only the brightness one. So the one hardware control this device really has was the one with no feedback — and a sink already at 100% takes a 5%+ and stays there, which makes a key that does nothing indistinguishable from a key that does nothing visible.

Android's shape for Android's reason, since the thumb of the hand holding the phone is already at that edge: a vertical track against the right edge, drag it to set the volume, gone three seconds after the last press. The wiring runs the other way from upstream's — moarchy-volume moves the sink and stops, and the panel raises itself when the sink it is bound to changes — so the shade's slider, an Android app and wpctl over SSH all raise the same panel, and the rocker keeps working with the shell down or too busy to answer.

Louder speakers on the Pixel 3a. Both amps are CS35L36s and the device tree provisions a 10 V rail for them, while upstream's use-case profile left both boost converters bypassed — so they were swinging against the battery, which was the only hardware gain the phone had left. With that fixed, music still reached the speaker at -17.0 dBFS RMS; a compressor into a fast lookahead limiter takes the same track to -10.8 with peaks pinned at -0.5 and no clipped samples.

Opening an app while an Android app is up no longer buries it. The drawer asked "is this workspace occupied" of two signals that cannot answer it — a focused toplevel that is null whenever one of our own sheets is up, and a sway workspace representation that no floating window ever appears in. Occupancy is one function over one signal now, and the daemon underneath counts every window rather than only tiled ones.

Under it, Omarchy 4.0.4.

Android apps, if you want them. moarchy-waydroid is published to the repo and is deliberately not installed by either image: waydroid init downloads about 1 GB on first run and lands as 2.4 GB on disk, and that is not a decision an image should make for you. The package carries no Android code and no Google apps — only the configuration that makes Waydroid fit a phone.

It is three steps, and the last one is not optional — Android latches its display size when the session is calibrated and never follows a later resize:

sudo pacman -S moarchy-waydroid
waydroid init                                     # ~1 GB down, 2.4 GB on disk

# then, from inside the phone's session:
waydroid session start
/usr/lib/moarchy/bin/moarchy-waydroid-setup       # pins the display, writes the sway rule
waydroid session stop

Re-run moarchy-waydroid-setup if the scale, the panel, the bar or the strip ever changes: every number it writes is computed from the device.

Android apps then appear in the drawer on their own, and that is where to launch them from — the drawer routes them through moarchy-android-launch, where waydroid app launch by hand gives up the status bar inset.

docs/android.md is the specification, including what does not work: the back gesture does not yet navigate inside an Android app, and Android's own volume is still unreachable from the phone, so a quiet app can be quiet for a reason nothing here can change.

Built from b3a9c19.