os
OSphreX
A privacy-first mobile OS — your device, your choice.
What OSphreX is
A research initiative into what a mobile operating system would look like if it were designed around the premise that the device you bought is the device you own — and built by a small principled team rather than a billion-dollar consortium.
OSphreX is not a shipping product. It is a published feasibility study, a research roadmap, and a position on what we think a mobile OS should be allowed to be.
The core position
Modern smartphones are increasingly conditional. Bootloaders revoke. Custom ROMs become impossible. Privacy-respecting Android forks (GrapheneOS, CalyxOS) do excellent work — but they remain downstream of Google’s decisions about AOSP. A clean-slate alternative isn’t easy, but it is structurally different: when the OS doesn’t share a kernel architecture or a userspace contract with Android, the threat model is fundamentally different.
The plan
- Hardware target: Honor Magic 4 Pro as the design target (the case study for an aspirationally-spec’d device). Actual bring-up happens on Xiaomi 12 (cupid) or Nothing Phone (2) — both have unlockable bootloaders and active mainline Linux kernel work.
- Stack: Linux kernel + Wayland compositor (wlroots or Smithay) — not Android. Custom Rust + GTK4 / libadwaita UI shell. Apple’s Liquid Glass-style visual language for UI primitives.
- Timeline: 30–36 months to a tech-preview daily-driver — matching the postmarketOS / Mobian historical curve, not the optimistic indie-team projection.
- Year 1: Wayland boot, screen, Wi-Fi, USB charging, app menu.
- Year 2: Calls / SMS, notifications.
- Year 3: Camera, polish, app store, OTA.
Read the research
The full architectural feasibility study is open and downloadable — including hardware analysis, kernel mainline status, compositor choice, app ecosystem strategy, the customisation features modern Android and iOS lack, and the small-team scope roadmap.
Read the OSphreX research initiative →
Maturity
Research. No code yet — the feasibility report is the artefact. Implementation begins after the research questions in the report have explicit answers.