TL;DR: Google will soon restrict app installs to the Play Store only, breaking F-Droid and custom app use. This article explores alternatives to Android, focusing on Linux-based and Android-based OSes (like GrapheneOS, LineageOS, /e/, CalyxOS). Linux offers privacy and control but limited hardware/app support; Android-based ROMs extend device life and privacy but may lose some features. If you want to escape Google, check your device’s compatibility and ensure it’s OEM unlocked before proceeding. My current pick: GrapheneOS on Pixel.
As a systems operator, I’ve always been interested in alternatives to Android, but never had a pressing reason to switch. That changed when Google announced that, starting September 2026, only Play Store apps will be installable. This blocks F-Droid and custom apps—including two business-critical apps I commissioned.
This article documents my ongoing investigation into Android alternatives, with a focus on privacy, usability, and device compatibility. I’ll update it as I progress through installation and daily use.
Android is based on the Linux kernel, but diverges in many ways. Alternatives fall into two broad categories:
| Feature | Linux-based (Mobian, postmarketOS) | Android-based (GrapheneOS, LineageOS) |
|---|---|---|
| Hardware Support | Limited (few devices, missing drivers) | Broad (many devices, esp. Pixels/Samsungs) |
| App Compatibility | Low (Android apps need emulation) | High (runs most Android apps, Play Services may be missing) |
| Privacy | Very high (fully open source, no Google) | High (Google-free options, some vendor blobs) |
| Ease of Install | Difficult (bootloader, custom kernel) | Moderate (ROM flashing, guides available) |
| Updates | Community-driven, may lag | Regular (security updates, active devs) |
| Battery Life | Often worse than stock | Usually close to stock |
| Target User | Power users, tinkerers | Privacy-focused, mainstream users |
Linux is appealing for privacy and control, but hardware support is limited and installation is technical. Some notable projects:
Pros: - Full Linux userland and tools - Maximum privacy and freedom - Useful for portable servers, dev rigs, or desktop-like setups
Cons: - Very limited hardware support (modem, camera, sensors, GPU, etc.) - Installation is risky and technical (bootloader unlock, custom kernels) - Battery life and performance may suffer - Most Android apps won’t run natively (can use Anbox/Waydroid with caveats) - Frequent manual maintenance
These are Android variants with privacy/security tweaks and (sometimes) Google removed. My shortlist (not exhaustive):
Pros: - Extend device life with newer Android versions and security updates - More privacy control (some ROMs remove Google services) - Customization, performance tweaks, active communities
Cons: - Some hardware features may not work or need vendor blobs - OTA update quality/frequency varies by project/device - App compatibility can suffer if Google Play Services are removed (microG helps, but not perfect)
Your OS choice limits your hardware options (and vice versa). I use Pixel phones for their unlockable bootloaders and minimal vendor bloat. Always check:
If you buy used or refurbished, always confirm OEM unlock status with the vendor. I learned this the hard way—had to return a phone that was only carrier unlocked.
When buying a used phone, be sure to find a vendor with a good reputation. I was fortunate to purchase from a well-reputed vendor on eBay who helped me acquire an OEM Unlocked phone when I had failed to specify that in the initial order. (Pending vendor permission, I may link directly to their eBay store here.)
Flashing custom ROMs always carries a risk of “bricking” (rendering the device unusable). If you’re risk-averse, some vendors sell phones pre-flashed with your chosen OS.
I chose GrapheneOS for these reasons: - Security/privacy focus - Trust in Pixel hardware - No need for social apps (but you can install them if you want) - The web installer is user-friendly; CLI install also available
As of Spring 2026, GrapheneOS recommends Pixel 8 or 9 (not 10 yet), but supports 6 and 7. I’m starting with a Pixel 8, then will try a 7a.
Helpful resources: - Reddit: My ride through GrapheneOS - YouTube: GrapheneOS Security Setup (20 min)
| Term | Definition |
|---|---|
| Bootloader | Low-level software that loads the OS; must be unlocked to install custom ROMs |
| ROM | “Read-Only Memory”; here, a custom OS image for phones |
| Vendor blobs | Proprietary drivers/firmware needed for full hardware support |
| microG | Open-source replacement for Google Play Services |
| Bricking | Making a device unusable due to failed modification |
| OTA | Over-the-Air update; install updates without a computer |
| Chroot/Container | Run one OS inside another (e.g., Linux on Android) |
| F-Droid | Open-source app store for Android |
| Pixel | Google’s flagship phone line, popular for custom ROMs |
I chose GrapheneOS. Installing GrapheneOS: My Experience talks about my experience in performing the install.