Open Source Android Alternatives Explained (October 2026)

Open source Android alternatives are operating systems built from the publicly released core of Android, called AOSP, and installed on a phone in place of the version its maker released. They cut Google’s tracking layer, drop the pre-installed apps you never wanted, and in several cases keep an aging phone useful for years past its final update.

That is the short version. The detail matters more than usual here, because these projects are not variations on a theme. Some are privacy-first Android builds limited to a single phone family. Some are maintained Android distributions that cover hundreds of models. Two of the biggest names are not Android at all, and they run neither Google apps nor most of the apps on your current phone.

We unpack each category below, including the practical parts competitors tend to skip: which banking apps actually work, why you may lose RCS messaging, and what happens to security patches once your manufacturer stops caring.

Open Source Android Alternatives at a Glance

The shortlist below covers the projects worth knowing. Every one of them is free software, but they divide into two families that behave very differently once you install them.

Project	Built on	Google services	Devices	Best for
LineageOS	AOSP, maintained as a community distribution	None by default, microG optional	Hundreds of models across many makers	Broadest device choice
GrapheneOS	AOSP, security-hardened	Optional, sandboxed Play in a separate profile	Google Pixel only	Privacy and exploit protection
CalyxOS	LineageOS	Optional, microG or sandboxed Play	Google Pixel only	Privacy with a gentler setup
iodéOS	LineageOS	Optional microG, no Play by default	Growing device list	Tracking blocking plus network controls
DivestOS	LineageOS	None by default, microG optional	LineageOS-supported devices	LineageOS users who want less telemetry
/e/OS	LineageOS	Optional microG	Selected models	Beginners who want an easy app store
Ubuntu Touch	Ubuntu and Qt, not Android	None	Selected community-supported phones	Convergence and a Linux phone
postmarketOS	Linux, mainline kernel	None	Early hardware list, plus desktops	Developers testing the mainline mobile stack
Sailfish OS	Independent Linux distribution	None, with a compatibility layer	Community-supported models	Swipe gestures and a wholly different UI

What the table does not show

Device support is the filter that decides everything else. If your phone is not on a project’s support list, the project is irrelevant to you no matter how good its privacy features are. Check the support list before reading any feature list.

Updates also run on different clocks. A project that supports an old phone may have stopped receiving new Android releases, while still applying monthly security patches to the parts it can. The next section explains why that distinction matters.

What Does Open Source Android Mean?

Android is not one piece of software. It is an open core wrapped in a large proprietary layer, and every project described as an open source Android alternative makes a different decision about which parts to keep.

AOSP is the open core, Google Play Services is not

The Android Open Source Project is the source code Google publishes for free: the launcher framework, the window system, the core system apps, and most of the user interface. Your phone’s original version is AOSP plus Google Mobile Services, which is the closed Google Play Services layer handling push notifications, location, in-app billing and sign-in.

Many projects are AOSP builds with nothing proprietary in place, so apps relying on Google Play Services install but behave oddly: no push notifications, no location, no in-app purchases. A few optional pieces can be added back later.

What microG is and why it decides app compatibility

microG is a free reimplementation of Google Play Services. Where available, it restores most of what a deGoogled phone loses, including push messaging, maps and sign-in. It is the single biggest factor in whether a phone running an open source build feels like a normal phone or a frustrating one.

microG runs in two modes. The default replaces Play Services outright. The signature-spoofing mode tricks apps into treating it as the real thing, which unlocks more banking and payment apps but also disables hardware attestation, and those apps can refuse to run. It is a genuine trade-off, and projects that require it will say so plainly.

Three things people mean by open source Android

The phrase covers three different projects that are often lumped together. AOSP distributions such as LineageOS are still Android, wearing a different system layer. AOSP builds with Google’s proprietary pieces stripped out, such as GrapheneOS and DivestOS, keep Android’s interface while cutting Google’s code. Independent operating systems such as Ubuntu Touch and Sailfish are Linux systems with their own interface, running their own app catalogs, and running almost none of your existing apps.

Which Open Source Android Alternative Is Best?

The best option depends on which constraint you refuse to give up. Pick by your priority and the answer is usually obvious within a minute.

• Most phone models available: LineageOS, by a wide margin.
• Strongest privacy and exploit protection: GrapheneOS, with the Pixel requirement.
• Privacy with less configuration: CalyxOS.
• An app store that does not require a Google account: /e/OS.
• Blocking trackers at the network layer: iodéOS.
• A phone that runs Linux instead of Android: Ubuntu Touch or postmarketOS.

If none of those fit, the honest answer is that no project here improves on the Android your phone already runs. Only switch if a specific problem pushes you.

DivestOS: LineageOS without the tracking

DivestOS is a LineageOS fork aimed squarely at long-term device support. Its pitch is an update window that outlasts the manufacturer’s own, with recurring builds and a downloadable system for supported hardware.

The tradeoff is a smaller device list, since it follows LineageOS’s support. It suits someone who wants fewer decisions and a clear update promise rather than a large feature set.

iodéOS: network control built into the system

iodéOS extends LineageOS with a DNS blocker and network permission toggles, so individual apps can be cut off from the network without root access. It also ships an encrypted cloud backup and a hardened browser with tracker blocking.

Device support is narrower than LineageOS’s, and it has not always matched upstream on update speed. It is the practical pick for someone who wants per-app network control more than they want the widest device list.

/e/OS: the least technical entry point

/e/OS adds an app store called Murena’s own frontend on top of LineageOS, so you can install apps without a Google account, plus a recovery system that can reinstall the OS from the browser after a wipe. It targets first-time users more directly than anything else on this list.

The cost is a smaller selection of phones and a narrower set of community resources when something breaks. Expect the same bootloader process as any other ROM.

LineageOS: The Best Choice for Broad Device Support

LineageOS is the answer for most people because it covers the widest range of phones by a distance. Maintained builds are published per device model, with a dedicated wiki page for each one covering unlock instructions, build instructions and known issues.

The project takes the upstream AOSP source, maintains its own device trees, and publishes official builds for each supported model. Downloads go through the LineageOS site rather than a forum post, which removes the single largest risk in this whole article: installing firmware from an unverified source.

That device page also tells you something most lists omit: which Android version the model is on, and whether it still receives updates. Older builds may have stopped getting new Android releases while continuing to take monthly security patches. Check that before committing.

LineageOS for microG is the pragmatic middle ground

The LineageOS for microG variant ships with microG already configured. For most deGoogling newcomers this is where they land, because push notifications and location keep working and the number of apps that refuse to launch drops sharply.

The version with signature spoofing enabled unlocks more apps and disables hardware attestation, which some banks read as a warning sign. If you use banking apps daily, weigh that carefully before enabling it.

The limits worth knowing

An unlocked bootloader is the price of entry everywhere, and it means anyone with physical access to your phone can flash a modified system. LineageOS supports relocking the bootloader after installation on most devices, which restores the secure state and is the option to pick unless a device explicitly needs an unlocked bootloader to boot.

Beyond that, the honest limits are these. There is no Play Store unless you add microG yourself. There is no Google Pay anywhere. Camera quality can trail the manufacturer’s version because vendors write their own camera software. And proprietary firmware patches stop when the manufacturer stops issuing them, which usually means the kernel and baseband stop being patched too, even while AOSP components keep receiving fixes.

GrapheneOS and CalyxOS: Privacy-Focused Android Options

These two are the strongest privacy choices that still run Android apps, and they share the same hard limitation: Google Pixel phones only. Neither is more willing to loosen that rule than the other.

Why the Pixel requirement exists

Two reasons, and both are structural rather than ideological. Google publishes the kernel source needed to keep bootloader relocking secure on Pixel devices, so an installed system can be cryptographically verified. Most other manufacturers ship incomplete or delayed kernel source, which means relocking a bootloader would leave a phone unable to trust its own operating system.

The second reason is update timing. A Pixel receives its monthly patch from Google directly, so a ROM built on it ships current. On a phone whose manufacturer still has patches queued, a new ROM build could easily be older than what you replaced.

GrapheneOS

GrapheneOS takes Android’s own hardening features and turns them up further: a redesigned memory allocator, memory tagging, hardened kernel and libc, re-compiled WebView, application spawning and a JIT-to-AOT compilation model. Its privacy layer adds per-app network and sensor permissions, storage scopes, an on-device DNS blocklist, metadata stripping and a duress PIN that wipes the device.

Its handling of Google Play is the detail people ask about most. Google Play installs in a separate user profile that can be launched and stopped like any other app, so its services reach your data only while that profile is running. You decide per app whether it gets network permission and whether it can see your contacts or sensors.

The downside is honest: it is Pixel-only, learning the interface takes an afternoon, and RCS messaging is the sticking point for many people who leave.

CalyxOS

CalyxOS builds on LineageOS and arrives with privacy defaults already applied: microG preinstalled, a firewall blocking trackers, Signal, the Tor browser and Aurora Store in place, plus per-app permissions and sensor toggles that do not require root. For most newcomers it reaches a sensible configuration in minutes rather than an afternoon of reading.

The cost is more control. The sandboxed Play arrangement is less capable than GrapheneOS’s profile model, and you are working within LineageOS’s device coverage rather than a first-party project.

GrapheneOS or CalyxOS?

Criterion	GrapheneOS	CalyxOS
Base	AOSP, independently hardened	LineageOS
Memory hardening	Extensive, the project’s core focus	Standard LineageOS protections
Google Play approach	Separate sandboxed profile, per-app toggles	Optional, microG preinstalled
Default setup	Minimal, you add what you want	Privacy apps and firewall preinstalled
Devices	Google Pixel	Google Pixel
Easiest for a newcomer	Harder	Easier

Decide by what you want to manage. Choose GrapheneOS if you want control and hardening and will spend time configuring it. Choose CalyxOS if you want the privacy decisions made for you.

Ubuntu Touch and postmarketOS: Independent Mobile Platforms

Now the category almost nobody mixes in with ROMs, and the distinction is worth internalising early. Ubuntu Touch and postmarketOS are not Android alternatives in the ROM sense. They are Linux systems with their own interfaces, their own app stores and their own idea of what a phone is.

Ubuntu Touch

Ubuntu Touch runs Ubuntu with the Qt interface, built around convergence: the same application can present as a phone app or as a desktop window when the phone is connected to a display. That is a genuine capability no Android ROM offers.

Its app catalog is thin, and most mainstream Android apps are not available. Hardware support depends on community porting, so only certain models are officially supported. Calls and messaging work on supported networks, with some carriers outside Europe needing extra setup.

postmarketOS

postmarketOS targets the Linux mainline kernel on phones, aiming at hardware that proprietary vendor kernels never supported well. Because it shares code with desktop and server Linux, the same machine can run a conventional Linux environment, which makes it genuinely interesting to developers.

It is not finished phone software. Hardware support is early, camera and radio behaviour is inconsistent, and the interface is minimal. Its value right now is as the place where that work is happening.

Sailfish OS and Plasma Mobile

Sailfish OS is a Linux distribution built around swipe gestures, with a compatibility layer that lets some unmodified Android apps run on it. Plasma Mobile is the KDE interface for phones, aiming at the same convergence model as Ubuntu Touch with more conventional desktop integration.

Both trade away the app ecosystem for independence. That is a fine trade for some people and a non-starter for anyone whose apps are part of their job.

How to Choose an Alternative by App, Hardware, and Update Needs

Run through this list before you commit. Each line is a place where projects genuinely differ, and most regrets come from skipping one.

Banking and payment apps. This is the most common blocker. Many banks check hardware attestation and refuse to run on a device that fails device integrity checks. Sandboxed Google Play keeps attestation working because the real Play Services runs, which is why GrapheneOS users are the least likely group to hit this. A microG signature-spoofing setup is the most likely to hit it.

Everyday apps. Most Android apps still work on an AOSP build without Google Play Services, but push notifications and location break. Banking, ticketing, and some streaming apps are the usual casualties, and games with anti-cheat or licensing checks are unreliable.

Camera, Bluetooth and calls. Vendor camera software is usually the part Android ROMs lose first. Bluetooth is usually fine. Calls and SMS generally work better than people expect, though carrier VoLTE and RCS support varies by network and project.

RCS messaging. If your contacts use RCS, leaving Google’s messaging stack often means going back to SMS and MMS, and existing group threads stop rendering. If that matters, check whether your carrier offers RCS through another route before you switch.

eSIM. eSIM setup depends on a carrier’s provisioning app, and some users report failures after leaving Google’s eUICC app. Physical SIM cards are the reliable path.

Android Auto. Almost no ROM supports it, because the certified app will not run outside its approved environment. Plan on a CarPlay-style alternative or an older car-compatible setup if you rely on it daily.

Update length. Decide whether you need new Android versions or only security patches. Projects on older hardware often keep applying monthly security fixes to AOSP components long after the Android version stops moving, and that is usually enough for most people.

Willingness to modify the phone. Every option here requires unlocking the bootloader. If your phone does not permit it, the decision is already made for you.

What Are the Main Risks and Tradeoffs?

None of this is risk-free, and the honest risks are worth stating plainly before you start.

Bricking is real. A failed flash or an interrupted update can leave a phone that does not boot. It is uncommon and usually recoverable, but on a phone with no other way in, recovery may mean a board-level repair. Newcomers to deGoogling are regularly advised to try a project on a spare device first, and that is sound advice.

Warranty and unlocking rules. Flashing custom firmware almost always voids the manufacturer’s warranty. More significantly, Samsung, Xiaomi, OnePlus and Asus have restricted or removed bootloader unlocking on many recent models, some limiting it to a narrow service window. Google, Sony, Motorola and Fairphone remain the practical options.

Back up first. A factory reset wipes everything. Use your platform’s backup or an encrypted local backup, and confirm you can restore it before you flash anything.

Patches are partial, not total. A ROM can carry current AOSP security fixes while the proprietary firmware running the radio, baseband and other closed components receives nothing. Updates from the Android Security Bulletin cover the open source layer, not the whole device. Treat this as a reason to keep choosing supported hardware, not as reassurance.

Projects can change. Maintainers retire devices, and a project can slow down or disappear. That is the strongest argument for GrapheneOS’s and LineageOS’s extended support on hardware other systems have abandoned.

Some loss is permanent. No Google Pay, no Android Auto on most projects, possible RCS regression, occasional camera regressions. Balance these against what you gain.

Frequently Asked Questions

Conclusion

Start with LineageOS if your phone model is supported and you simply want Android without Google’s tracking layer, and start with LineageOS for microG if you rely on push notifications and location. Buy a Pixel and start with GrapheneOS if privacy and exploit protection matter more to you than device choice, or CalyxOS if you would rather not configure everything yourself.

Look at Ubuntu Touch or postmarketOS only if you want a phone that runs Linux and can accept a much smaller app catalog. Before anything else, check your model’s support page, confirm your bootloader can be unlocked, and back up your data.