Omarchy Mobile runs native Omarchy on the Pixel 7 Pro, with community ports under way on eight more phones
No Android underneath: Derek Ross’s community project puts Arch Linux ARM, Hyprland and Omarchy’s own packages straight onto a Pixel, and it is looking for help bringing them to more phones.
Image: Omarchy Mobile (omamobile.org)
Omarchy on a phone is no longer a thought experiment. Omarchy Mobile, a community project by Derek Ross, runs “native Omarchy on mobile devices: Arch Linux ARM, Hyprland and Omarchy’s own packages running directly on the device with a mainline kernel,” according to its README. The project site sums it up as Omarchy “with no Android underneath.” The reference device is the Pixel 7 Pro, and Android apps through Waydroid are listed as a later goal.
The Pixel 7 Pro status list on the site has 22 components, and 20 of them are marked “Works”: display at 120 Hz, GPU, touch, buttons, Wi-Fi, Bluetooth audio, battery, charging, haptics, torch, GNSS, sensors with auto-rotate, NFC, all four cameras, fingerprint unlock and more. Audio got its latest upgrade on October 27, 2026: since omamobile-audio 0.5.3-0.5.4, the device matrix says both speakers play clean and loud, with the maximum still a little below the stock system’s.
The fine print is honest. The telephoto camera is fixed-focus for now, sharp on distant subjects and soft up close, because its focus motor isn’t driven yet. Fingerprint unlock is opt-in, since its first run writes the phone’s secure storage. The modem is “In progress”: it boots Google’s firmware, but no SIM has been in the phone yet, so registration, SMS, data and calls are untested. Suspend is also in progress: s2idle works and gives about 16 hours of standby with the screen off, but it isn’t on by default yet.
All of this runs on the project’s own drivers, written against upstream Linux and published in linux-omarchy-mobile; the README says the kernel branch sits on mainline v7.3-rc6, with one commit per subsystem so patches can go upstream. The first one is on its way: on October 19, 2026, the README noted that a patch for the battery’s charging status had been sent upstream and reviewed.
The last week has been busy. On October 22, 2026, the project’s own camera app, omacam 0.3.3, gained Night mode and HDR, merging bursts of raw frames on the phone. On October 26, 2026, omamobile-shell 0.2.17 and 0.2.18 added a home pill (swipe up for Home, swipe and hold for recent apps) and a round of touch fixes: bigger hit areas, two taps for destructive actions and no text under 12 px.
Installing is not for the faint of heart, and the README says so: “The installer is new: expect rough edges.” You need a Pixel 7 Pro with an unlocked bootloader, an Omarchy laptop with Docker, and Google’s factory image for the phone. The safety model is the reassuring part: stock Android stays on slot A as the way back, and the installer writes only slot B’s boot images and userdata, which it erases. 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.
Other phones are catching up. Under “Bring it to your phone,” the devices page says community ports are under way on “8 more phones”: the Pixel Fold, 6 Pro, 7a, 6, 4, 4 XL, 9a and 8 Pro. The Pixel 6 Pro is the only one of the eight whose boot is already marked “Works.” The POCO F3 is the first non-Pixel port, with a guarded installer still in review in pull request #25 at the time of writing, and tracking issues are open for the Pixel 10 Pro XL and the Pixel 11 Pro Fold.
If you have a spare phone and some kernel patience, this is a good moment to jump in. The wanted list names each target with its closest starting point, and CONTRIBUTING.md walks through the safety model, the build and flash loop and a step-by-step guide to bringing up a new device. Just keep in mind what the site’s footer says: Omarchy Mobile is a community project that “isn’t an official Omarchy or Basecamp product.”
