Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
88 changes: 88 additions & 0 deletions docs/release-notes/2026.11.14.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
<!-- SPDX-License-Identifier: MIT -->
# Omarchy Mobile 2026.11.14 (developer preview)

The third release of Omarchy Mobile, and the first with sleep on by default: native Omarchy (Arch Linux ARM, Hyprland and Omarchy's own packages) on the Google Pixel 7 Pro, with a mainline Linux kernel and no Android underneath. This is a **developer preview**: it installs and runs as an everyday Linux phone for people comfortable with fastboot, but some hardware is still being worked on (below), installing erases the phone's data, and stock Android stays on slot A as the way back.

Omarchy Mobile is a community project built on [Omarchy](https://omarchy.org). It is not an official Omarchy or Basecamp product, and it is not affiliated with or endorsed by Google.

## What's in it

- **Device:** Google Pixel 7 Pro (`cheetah`, Tensor G2 / gs201). No other phone is part of this release.
- **Kernel:** `kernel-2026.11.13`, linux-omarchy-mobile's `omamobile` branch at `36d61a33795b` (Linux 7.3-rc6 plus our drivers); `uname -r` is `7.3.0-rc6-omamobile-g36d61a33795b`. The source is public at that tag before any binary ships. It adds two fixes to the kernel of 2026.11.08 and 2026.11.12: power off stays off ([linux-omarchy-mobile#233](https://github.com/derekross/linux-omarchy-mobile/pull/233)), and the touchscreen can wake the phone from sleep ([linux-omarchy-mobile#248](https://github.com/derekross/linux-omarchy-mobile/pull/248)).
- **Userspace:** Arch Linux ARM, Omarchy 4.5.0-3 (held at that version in `[omamobile]`: it is the one our patches were checked against) with our 28 pending patches (re-applied after every Omarchy upgrade), and the signed `[omamobile]` repository (pkgs.omamobile.org, stable channel) for the phone shell, Mesa for the Mali-G710, Hyprland, libcamera and the device support packages.
- **Updates:** `omarchy update` on the phone or the Updates entry in the app drawer, from the stable channel, kernel included: the kernel is the `linux-omamobile` package, and `omamobile-boot-update`'s pacman hook writes a new one to slot B (it never reboots by itself; the update sheet asks for a restart). The reference phone took this release's kernel that way on 2026-11-14, from the development channel.

### Hardware on the Pixel 7 Pro

From [docs/DEVICES.md](../DEVICES.md) on the release day:

| Works | Notes |
| --- | --- |
| Boot, storage | Slot B with stock Android kept on slot A; the Arch root on `userdata` behind a read-only guard for every other partition |
| Display | 120 Hz, brightness, the panel sleeps with the screen off |
| GPU | Mali-G710 on Panthor with Mesa, frequency scaling |
| Touch, buttons, haptics, torch | Touchscreen, power and volume keys, vibration through feedbackd, the torch tile |
| Wi-Fi, Bluetooth | Wi-Fi (stays connected across sleep); Bluetooth pairing and A2DP audio (headset calls not yet) |
| Modem | Calls, texts and mobile data on the one network tested so far (a Verizon-network SIM), the stack started at boot once the phone is provisioned; the carrier's APNs come from the SIM ([#373](https://github.com/derekross/omarchy-mobile/pull/373); see Known issues) |
| Battery, charging | Fuel gauge with the stock battery model; charging with a temperature guard |
| Speakers, microphones | Both speakers in stereo under Google's speaker-protection firmware with the phone's own calibration, plus the microphones; at the louder level, a little below stock's maximum volume, on a phone whose speaker firmware is the verified one (today: the factory image cp2a.260705.006); other phones start at a quieter everyday level until their firmware is verified |
| Sensors | Accelerometer (auto-rotate), light, proximity and compass |
| GNSS | Location through GeoClue, with a quick-settings tile |
| NFC | Reads and writes tags; a tag with a link opens it |
| Cameras | Main, ultrawide and front through libcamera; the telephoto at fixed focus |
| Fingerprint | Starts automatically after provisioning: enrollment offered at setup, unlock on the lock screen |
| CPU | Frequency scaling and thermal zones |
| Sleep | The phone sleeps when the screen goes off (s2idle), and Power or a double tap wakes it; about 22 hours of standby with the modem off (see Known issues for the modem) |
| Power off | Stays off; an off phone on a charger starts a dark charging-only boot |

### New since 2026.11.12

- **Sleep is on by default.** With the screen off the phone goes into s2idle by itself (`omamobile-shell` 0.2.129 turns auto-sleep on once, at the first login, where the device package says suspend is verified; `omamobile-device-cheetah` 0.1.55 says so for the 7 Pro). A 10-hour night in one sleep with the modem off drew about 228 mA, roughly 22 hours of standby. Turn it off with `omarchy-toggle omamobile-sleep off`; a user who turns it off keeps it off. ([#730](https://github.com/derekross/omarchy-mobile/pull/730), [#737](https://github.com/derekross/omarchy-mobile/pull/737))
- **A double tap wakes a sleeping phone,** as Power does, and lights the lock screen (the kernel's touch wake, [linux-omarchy-mobile#248](https://github.com/derekross/linux-omarchy-mobile/pull/248), enabled by the device package).
- **Power off stays off.** Shutdown from the power menu (or `systemctl poweroff`) no longer starts the phone again by itself ([linux-omarchy-mobile#233](https://github.com/derekross/linux-omarchy-mobile/pull/233)). An off phone plugged into a charger starts a dark charging-only boot; hold Power to start it.
- **Power off at a critical battery.** At 3 % the phone shuts down cleanly instead of running flat while asleep.
- **Swap on a phone updated from 2026.11.08.** `omamobile-omarchy` 0.1.46 depends on `zram-generator`, so a phone that updated to Omarchy 4.5 gets its zram swap too; a fresh install had it already ([#768](https://github.com/derekross/omarchy-mobile/pull/768)).
- **The guided install ships in the bundle:** in the unpacked folder, `bash install --guided` runs the install, the first start, the radio backup, the firmware step and the phone check as one command that resumes where it stopped, and asks rather than wanting options such as `--reinstall` ([#773](https://github.com/derekross/omarchy-mobile/pull/773); [docs/INSTALL-GUIDED.md](../INSTALL-GUIDED.md)).
- **The root image keeps a place for the owner's answers** (`/etc/omamobile/firstboot.conf` and `boot-update.conf`, one 4096-byte block each, listed in `manifest.json` under `root_image.placeholders`), so installers that stream the image to the phone, such as the coming desktop installer and web page, can fill them in place. Unfilled, they mean nothing, and `bash install` still writes its own ([#742](https://github.com/derekross/omarchy-mobile/pull/742)). `omamobile-firstboot` 0.1.6 also takes a time zone the phone doesn't have as UTC, with a warning, instead of stopping the first start.
- **The phone check** (`tools/phone-smoke`, which the guided install runs at the end) counts two known families of kernel lines at modem start as known rather than new errors ([#769](https://github.com/derekross/omarchy-mobile/pull/769)).

## Known issues

- **Calls, texts and mobile data work on the tested network.** Tested on the reference phone with one Verizon-network SIM (Tracfone): VoLTE calls both ways, texts over IMS, and mobile data as a fallback route behind Wi-Fi ([DEVICES](../DEVICES.md)). Other networks are untested. The SIM's APNs and bearer order come from its carrier, read once from the SIM at boot ([#373](https://github.com/derekross/omarchy-mobile/pull/373)): a Verizon-network SIM is the one proven end to end; other carriers take the carrier database's APNs, and the Mobile network page under Setup shows and corrects them. Call audio through the earpiece works at every speaker stage (`omamobile-audio` 0.5.13), on by default (`omamobile-modem-sit` 0.3.30 with `omamobile-device-cheetah` 0.1.44). A development install whose `/etc/omamobile/modem-sit.conf` was edited (the Mobile network page writes it) keeps its `card = none` line: delete it for call audio. With the modem up the phone never sleeps (the stack holds a sleep inhibitor, because suspend with the modem up isn't qualified), and each restart with the modem up costs one recovered storage error-handler pass. After a hang or a forced reset with the modem up, the next boot starts the modem all the same (`journalctl -b -1 -u omamobile-modem` has that boot's line); if that boot ends the same way, the modem stays off (the Mobile data tile says "Off after a hang or reset (held)") until the markers are cleared by hand (`sudo rm -f /var/lib/omamobile/modem-up /var/lib/omamobile/modem-up.refused-*`, then restart the phone), and a clean reboot in between resets the count. `sudo touch /etc/omamobile/modem-hold` holds it from the first time. To keep the whole stack off: `sudo systemctl mask omamobile-modem-boot.target` (`disable` doesn't remove the package's link, and `systemctl is-enabled` reads "disabled" either way).
- **With the modem up the phone doesn't sleep.** The modem stack holds a sleep inhibitor until the phone restarts, because sleep with the modem up isn't qualified: the first test of it ([linux-omarchy-mobile#232](https://github.com/derekross/linux-omarchy-mobile/pull/232), 2026-11-13) slept and woke but lost mobile data after a run of refused sleeps. On a provisioned phone with a SIM the modem starts at boot, so in practice such a phone stays awake with the screen off; the standby above is with the modem off (`sudo systemctl mask omamobile-modem-boot.target`, then restart). Wi-Fi traffic and a USB plug can't wake a sleeping phone, and a few timer wakes come early on an unidentified power-chip interrupt.
- **Cameras:** basic image quality (no Google ISP or tuning); the telephoto doesn't focus.
- **Bluetooth:** headset calls (HFP) don't work yet.
- **USB-C:** the phone is a USB device only (no host mode or role switch yet); after a replug, `omamobile-usb-rescue` reconnects it.
- **Fingerprint starts once per boot by design:** if it stops, restart the phone. Its first start writes the phone's secure storage (Trusty's area in the RPMB, the same kind of write as an Android factory reset); `persist` and `mfg_data` are only read. Fingers are enrolled again after a reinstall. To keep it off, `sudo systemctl mask omamobile-fp`.
- **Google's firmware is not included** and never will be, and installing it is still a separate step: after the first start, run the bundle's `tools/phone-provision` with your own factory image for your phone (Wi-Fi, Bluetooth, haptics, speakers, sensors, the modem, cameras and the fingerprint sensor), then restart the phone. Until then Wi-Fi, sound, the modem and fingerprint don't work, and the setup can't offer a fingerprint. Installers that do this on their own are being built.
- **Run `omarchy update` as yourself, never as root:** from the phone's terminal or the Updates entry. As root it is refused, with the reason.
- **A completely flat battery:** if the phone keeps restarting on the cable, hold Volume Down + Power for fastboot and leave it there on the charger for 20-30 minutes (`fastboot getvar battery-voltage` should pass 3.8 V), then choose Start ([#169](https://github.com/derekross/omarchy-mobile/issues/169)).
- **Stopping the modem** (`systemctl stop omamobile-modem`) takes 40 s and is logged as a crash ([#532](https://github.com/derekross/omarchy-mobile/issues/532)), though it stops cleanly; to get the modem back, restart the phone rather than starting it again.
- **A first install from stock Android with the guided install (or the coming installer app) stops at the bootloader-slots check.** On a phone that has only run stock Android, the check of slot B's bootloader against the factory image's stops the install; don't work around it, [open an issue](https://github.com/derekross/omarchy-mobile/issues) or install by hand (below). A reinstall over Omarchy Mobile goes through: the guided install asks whether the phone already runs Omarchy Mobile and passes the bootloader the phone runs.
- **`systemd-firstboot` fails once** on the first start (the phone has no console); Omarchy Mobile's own first-boot setup does its job.

## Updating from 2026.11.12 or 2026.11.08

A phone installed from an earlier release doesn't need this image: open Updates, or run `omarchy update`, then restart when the update sheet asks. The update carries the new kernel to slot B and the device package that turns sleep on. A phone that updated from 2026.11.08 to Omarchy 4.5 gets its swap with this update. From 2026.11.08, the first update also moves the phone to Omarchy 4.5 (see [the 2026.11.12 notes](2026.11.12.md)); there is no way back to Omarchy 4.0.6 short of installing again.

Auto-sleep is turned on once, at the first login after the update, unless it was turned off by hand before.

## Phones running a development build

A phone installed from the repository follows the development channel and gets all of this with `omarchy update`. Its kernel stays as it is: `omamobile-boot-update` is off unless `/etc/omamobile/boot-update.conf` says `AUTO_WRITE=yes`, so slot B is still written by `bin/omamobile push`. A phone from before the release key or before Hyprland 0.57 needs the two one-time steps in [the 2026.11.08 notes](2026.11.08.md) first.

## Installing

Follow [docs/INSTALL.md](../INSTALL.md), step by step. In short: a Pixel 7 Pro with an **unlocked bootloader**, a Linux computer with `fastboot` and the tools INSTALL.md lists, and Google's factory image for `cheetah`. Download the one file `omamobile-cheetah-2026.11.14.tar` with its `.tar.sha256` (and `.tar.sha256.sig`, to check the signature) from `https://pkgs.omamobile.org/releases/cheetah/2026.11.14/`, check it with `sha256sum -c`, unpack it with `tar -xf`, then run `bash install --guided` in the unpacked folder for the guided install, or `bash install --dry-run` and `bash install` to install by hand. Installing by hand, after the first start, back up the phone's radio partitions with the bundle's `bash tools/nv-backup BACKUP-DIR` (INSTALL.md step 6; read-only, keep the backup folder private: it holds your IMEI), then add Google's firmware with `bash tools/phone-provision --first-install --nv-backup BACKUP-DIR FACTORY-IMAGE.zip` (INSTALL.md step 7).

If the installer stops about the bootloader slots on a first install, don't work around it: [open an issue](https://github.com/derekross/omarchy-mobile/issues). On a reinstall over Omarchy Mobile, the phone already runs slot B's bootloader, and the installer's message names the two options to add (`--reinstall` and `--bootloader-slots-match`).

What it writes: slot B's `boot`, `init_boot`, `vendor_boot`, `vendor_kernel_boot` and `dtbo`, and `userdata` (**erased**). It never touches slot A, the bootloader, radio, `persist`, `efs`, `modem`, `devinfo` or `vbmeta`.

## Going back to stock Android

Stock Android is still on slot A. In fastboot: `fastboot --set-active=a`, then `fastboot reboot`, and factory-reset Android when it asks (its data was erased by the install). Or flash Google's factory image for `cheetah`. Before you first boot stock again, note that stock's modem stack rewrites `efs`, `persist` and `modem_userdata`; keep your read-only backup of them.

## Checksums and signatures

The bundle's `SHA256SUMS` is signed with the Omarchy Mobile release key (`2056 7593 566E EEE2 DD88 6460 8632 C807 5EB9 4673`); its `MANIFEST` and `manifest.json` name the root image and its SHA-256, so the installer checks the root image against the signed record before it contacts the phone.