Omarchy Mobile

Native Omarchy on mobile devices: Arch Linux ARM, Hyprland and Omarchy's own packages running directly on the device with a mainline kernel, with Android apps in Waydroid as a later goal. The reference device is the Pixel 7 Pro (cheetah, gs201); community ports cover more Pixels, and the first non-Pixel ports are in review (docs/DEVICES.md).

Status (2026-10-27), on the Pixel 7 Pro. Each item's detail and the notes behind it: docs/DEVICES.md; what's missing and the plan to get there: docs/ROADMAP.md.

• Works: display at 120 Hz, GPU, touch, buttons, USB networking, Wi-Fi, Bluetooth audio, battery, charging (on at boot under a battery temperature guard), haptics, torch, sensors with auto-rotate, GNSS (Location tile, GeoClue), NFC (reading and writing tags, opening a tag's link) and fingerprint unlock alongside the PIN pad or password, which keeps working across sleep (opt-in, because its first run writes Trusty's secure storage). The speakers and microphones work: both speakers play clean and loud enough for music under the amplifiers' own protection firmware, a little below stock's maximum. All four cameras work in omacam ("Camera", our own camera app, the default since omamobile-apps 0.2.0: one zoom control from the ultrawide to the telephoto, full-resolution photos, tap to focus, Night mode and an HDR chip) through libcamera: main, ultrawide, front and telephoto, at full size by default (cam with no options). The telephoto is fixed-focus for now: sharp on distant subjects, soft up close, because its focus motor isn't driven yet (it holds its I2C bus when driven). Single shots are still well below stock's quality: that is tuning.
• In progress: the modem boots Google's firmware and answers our IPC (SIM and radio state), but no SIM has been in the phone yet, so registration, SMS, data and calls are untested. Sleep: s2idle works with Wi-Fi staying connected (31 of 31 cycles) and the AoC and sensors working across it, and draws 312 mA with the screen off, about 16 h of standby (2026-10-19). It isn't on by default yet: the phone doesn't sleep by itself when the screen goes off until the screen-off policy (S8) has run. Deep sleep, which stock's standby needs, is research.
• New on 2026-10-26: a home pill that goes Home on a swipe up and opens recent apps on a swipe and hold, the dock hidden under apps, and Power waking a dark screen (omamobile-shell 0.2.17, #43), then the touch audit's quick wins: bigger hit areas, two taps for destructive actions, no text under 12 px (0.2.18, #46, docs/TOUCH-PLAN.md); the Pixel 7 Pro's boot no longer reports a reserved-memory overlap (kernel #58). Updates: omarchy update brings Omarchy's own packages over Wi-Fi, but Omarchy Mobile's packages aren't published yet, so they still come from your own build. Community ports: the Pixel Fold's volume and power keys and its cover touch chip id are in the kernel (kernel #41, #32); the Pixel 7a reached first light with USB and SSH (#36); the Pixel 6 Pro runs Omarchy on our kernel, with its device package in review (#41); the Pixel 8 Pro's device package and storage plan are in review (#42); a tracking issue is open for the Pixel 11 Pro Fold (#40).
• New on 2026-10-22: Night mode and HDR in omacam 0.3.3: a burst of raw sensor frames aligned and merged on the phone before the colour processing (Night's 12 frames in about 4.6 s), on top of chroma noise reduction and defective pixel correction in our libcamera (docs/CAMERA-QUALITY-PLAN.md); images and updates follow Omarchy's stable channel, and omarchy update on the phone runs Omarchy's own update with the phone's safeguards (Omarchy Mobile's own packages aren't hosted yet). Community ports: the Pixel 8 Pro boots our mainline kernel with USB and SSH (#1), the Pixel 9a reached first light (in review), the Pixel 6 Pro has provisioning tools in review, and the POCO F3 is the first non-Pixel port proposed; tracking issues are open for the Pixel 10 Pro XL and Pixel 11 Pro.
• New on 2026-10-19: the Pixel Fold boots to its cover screen and the Pixel 6 builds, both community ports (docs/DEVICES.md), and the Pixel 4 runs a read-only first-light probe; the Tensor phones share one initramfs, with each phone's quirks packed from its descriptor; our first kernel patch went upstream (the battery's charging status) and was reviewed; first login invites you to pick an AI agent, with none preinstalled.
• New on 2026-10-13: home screens with 47 built-in widgets (Simon Schubert's MIT-licensed omarchy-widgets, his OWL originals run by our own OWL runtime since 2026-10-14, plus an OWL widget Store tab with an approval sheet for what each widget may run) and your own widgets made with "Create with AI" through Omarchy's default agent, behind a crash guard; 19 quick-settings tiles with an editor; one app per screen, with a "Show with…" action; the phone's screen and input on a computer over USB (omamobile-mirror, tools/phone-mirror); a device descriptor (device.conf) for more than one phone; and a first installer (below), which passed its first clean reinstall.

Quick start

The installer is new: expect rough edges. You need a Pixel 7 Pro with an unlocked bootloader, an Omarchy (Arch) laptop with Docker, android-tools and e2fsprogs, and Google's factory image for the phone. Stock Android stays on slot A as the way back; installing erases userdata.

tools/build-packages                 # Omarchy Mobile's packages for aarch64 (out/repo)
tools/build-rootfs                   # the root image: Arch Linux ARM, Omarchy, our packages
tools/install-phone --dry-run        # phone in fastboot: checks it, asks for your user, shows every command
tools/install-phone                  # writes only slot B's boot images and userdata
# after the first boot: a read-only backup of the modem's partitions into DIR (below)
tools/phone-provision --nv-backup DIR FACTORY.zip   # firmware from your own factory image, NV sums from DIR

Back up before you provision. After the first boot, copy the modem's partitions (persist, modem_a, modem_b, efs, efs_backup, modem_userdata) and devinfo off the phone, read-only, into a new directory of your own outside the repository, with a SHA256SUMS file. The commands, which check each copy against the phone, are in REINSTALL-RUNBOOK section 4a. tools/phone-provision doesn't take this backup for you: it holds your IMEI, so you keep it, and never commit, post or attach it. --nv-backup DIR puts its six NV checksums on the phone (the modem starts only from copies of its partitions that still match them); the modem's board id is read from the phone's own bootconfig and written on the phone, never printed. A reinstall of your own takes the same steps; only the runbook's reinstall from Phase 0's phone-config.tar (a backup of the hand-installed system) restores from that tar instead.

The kernel and boot images come from bin/omamobile kernel, modules, initramfs and images (CONTRIBUTING.md §4). Step by step, with what to expect at each point: device/cheetah/REINSTALL-RUNBOOK.md.

Layout

Path	What it is
bin/omamobile	Build and flash tooling: capture, kernel, modules, initramfs, images, flash, push, kexec, fastboot
tools/build-packages, tools/build-rootfs, tools/install-phone, tools/phone-provision, tools/make-bundle	The installer: aarch64 packages and the root image built on the laptop, the narrow fastboot installer, per-phone provisioning, release bundles (rootfs/ holds the image's package lists; tests/ their tests)
tools/	Staged bring-up and capture tools, on-phone probes, firmware extraction from the user's factory image, package and repository helpers
packages/	pacman packages: omamobile-shell (the phone profile for Omarchy's shell), omamobile-apps (the mobile apps desktop Omarchy lacks: Camera, Maps, NFC), omacam (the camera app, built from its own repository), omamobile-device-cheetah (Pixel 7 Pro support), omamobile-device-felix (Pixel Fold), omamobile-sensors (sensors and auto-rotate through the AoC), omamobile-gnss (location on demand), omamobile-mirror (the phone's screen and input on a computer over USB, VNC), omamobile-audio (PipeWire and speaker protection), omamobile-speaker-tuning (stock's speaker tuning, off by default), omamobile-fingerprint with a patched libfprint, omamobile-modem (the modem's vendor chroot profile), omamobile-modem-sit (the SIT client daemon; talks to the modem, registration untested), omamobile-mmd (ModemManager's D-Bus API in front of it, for GNOME Calls, Chatty and NetworkManager), neard, omamobile-keyring (the [omamobile] repository's signing key), patched mesa and hyprland. tools/phone-install-package builds one on the phone and installs it
patches/omarchy/	Changes to Omarchy for touch devices, to send upstream (bridge-* ones are stopgaps for the phone's older Omarchy); a link to packages/omamobile-omarchy/patches, whose pacman hook re-applies them after every Omarchy upgrade
bin/lineage-ref	Builds LineageOS for the phone. Used as a rooted reference Android (M0) and, later, for Waydroid images
kernel/configs/	Our kernel config fragment, merged on top of arm64 defconfig
device/cheetah/	Pixel 7 Pro bring-up notes, one plan per subsystem, overlays, the initramfs and the device descriptor (device.conf)
device/<codename>/	The other devices' descriptors, notes and bring-up plans (felix, oriole, flame, husky, tegu)
omamobile.conf	Shared settings (source dir, jobs, container image). Override in omamobile.local.conf
docker/	Ubuntu 24.04 build environment
docs/DEVICES.md	Supported-devices matrix
docs/ROADMAP.md	Where things stand and the plan to a working phone
docs/DEMO.md	Fictional demo data, screenshots and screen recordings for the website and videos (tools/phone-demo)
docs/RELEASES.md	How builds and releases work for several devices: device descriptors, the kernel package, release bundles

Large trees live outside the repo: the Android-side sources, images and captures under ~/android/, and the kernel under ~/omamobile-kernel/ (~/android/mainline on setups from before 2026-10-29; the tools find either):

Path	Contents
~/android/omamobile	LineageOS 24.0 source. Includes Google's GPL Pixel 7 kernel at out-kernel/google/gs-6.1
~/omamobile-kernel/linux	Our kernel repo: branch omamobile on mainline v7.3-rc6 (remote upstream is Linus's tree), one commit per subsystem so patches can go upstream. Published to derekross/linux-omarchy-mobile by tools/publish-kernel (a squashed upstream base, our commits unchanged on top)
~/omamobile-kernel/pmos-tensor	postmarketOS Tensor kernel, for reference
~/android/reference	Captures from the phone. Contains serial numbers and partition backups: never commit
~/android/factory	Verified stock factory images, used to restore the phone

Ground rules

• We only ever flash the boot images and userdata. Never bootloader, radio, devinfo, persist or calibration partitions.
• Licensing: this repository is MIT (LICENSE) except where a file's SPDX header says otherwise. Kernel patches (and the board dtbo source) are GPL-2.0. The port of Google's Apache-2.0 boot-control code keeps that licence and Google's notice (packages/omamobile-device-cheetah/src/omamobile-bootctl.c). Every file we write carries an SPDX header.
• Google's proprietary firmware and binaries are never committed: our scripts extract them from the user's own factory image.
• No code from unlicensed sources. Google's GPL kernel, upstream Linux, postmarketOS and Mesa are fine.

Contributing

Bringing up another device, fixing a driver or improving the phone shell: start with CONTRIBUTING.md. It covers the safety model (stock Android stays on slot A, the read-only storage guard, backups, dead-man switches), the build and flash loop, a step-by-step guide to bringing up a new device, and how to submit kernel and package changes. AI coding agents should also read AGENTS.md. The status of each device is in docs/DEVICES.md, and what's next in docs/ROADMAP.md.