ObliviOS

Home / Devices

Devices

Which phones run ObliviOS, which one I use every day, and what has to be true before I call any of them supported.

No device is supported. Two phones run ObliviOS builds: the Pixel 10a I use every day, and the Pixel 7a I develop on.

ObliviOS is source only: there is no image to flash.

Pixel 10a stallion
My daily phone, with my personal data on it. Calls, the SIM and the camera work on it. Its bootloader is locked with my own key, so verified boot reads yellow and locked, and it takes signed updates through the system updater: six so far, the latest read on 9 November 2026. It runs Compartments, Network exit, Atlas, Duress Unlock, Passwords, grab detection, the app drawer, the keyboard and AirPods support.
Pixel 7a lynx
My development phone and the first engineering target. New work is built and checked here first. It has no SIM card, so calls and mobile data are not tested on it.
Supported
No device. A device counts as supported only after it passes the entry gate below.

What supported means

A device is supported only with verified upstream device source, current firmware and driver coverage, a monthly update path, signed images and updates, locked-bootloader verification, recovery validation, and evidence for emergency and radio functions. A booting image alone is not support, and a phone that I use myself is not a support claim.

Images

If real interest in ObliviOS shows, I want to publish images for the Pixel 10a. I have not set a date. Before I do, the five gates of a public beta on the status page have to be met. One more thing stands in the way, and I postponed it on purpose: nobody has rebuilt a signed image independently and compared it byte for byte (decision 112). I decide on the day, separately. Until then ObliviOS is source only.

No date, no promise

Nothing on this page says that an image will exist. It says what I intend and what stands in the way.