Unix Server Tech Knowledge Base

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Android Alternatives ======

===== 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). Key points: 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.

===== Alternatives =====

I have always been interested in alternatives to the Android operating system used in various mobile devices, but never had a reason to investigate further. As a systems operator, I spend most of my waking hours working on digital equipment, and this is an area which does not relate to my job. However, I have two custom apps which were written specifically for me, and I tend to use F-Droid for as much as possible.

Google has announced that in September 2026, they will no longer allow any software to be installed that is not available on their Play Store. The result would be that I could no longer install apps from F-Droid, and the two custom apps I paid a significant amount to have build specifically for our business, would no longer be usable.

This took 'interested in Android alternatives' into 'really need to see if they will work for me.'

This article explores my investigation, and the results. I am in the middle of the task now (more on that later), so no conclusions yet. I'll add to this article while I perform the install, then when I have used Graphene for a while.

===== Alternatives =====

I had a lot of trouble deciding which alternative I would need. Android was originally based on the Linux kernel (the 'center' of the Linux operating system), and continues to this day, though there is some divergence as Android includes some specific patches for phone and tablet functionality.

The choices broke down into two main groups; Linux operating systems modified for cellular use, and Android derived products.

===== Comparison Table =====
^ Feature ^ Linux-based (e.g., Mobian, postmarketOS) ^ Android-based (e.g., GrapheneOS, LineageOS) ^
| Hardware Support | Limited (few devices, missing drivers for modem/camera/etc.) | Broad (many devices, especially Pixels/Samsungs) |
| App Compatibility | Low (Android apps need emulation/containers) | High (runs most Android apps, but Play Services may be missing) |
| Privacy | Very high (fully open source, no Google) | High (Google-free options, but some vendor blobs) |
| Ease of Install | Difficult (bootloader, custom kernel, risk of brick) | Moderate (ROM flashing, some tools, 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 =====

Linux is a decent alternative for me, as a Unix Systems Administrator, but generally the hardware is fairly limited, and battery life and performance can suffer. Also, for non-Unix users, it can require technical skills beyond what most end users have. Some Linux distributions specifically targeting cell phones are listed below. These were found using https://duck.ai, a privacy focused AI tool, so will have the limitations of current AI

  * [https://ubports.com/|Ubuntu Touch] (UBports)
  * [https://www.debian.org/|Debian] (via chroot/containers, but native on some devices)
  * [https://getfedora.org/|Fedora] (including Fedora Mobile spins / Fedora on ARM)
  * [https://manjaro.org/downloads/arm/|Manjaro] / [https://archlinuxarm.org/|Arch ARM]
  * [https://mobian-project.org/|Mobian] (Debian for mobile)
  * [https://pureos.net/|PureOS] (and other privacy-focused Debian derivatives)
  * [https://postmarketos.org/|postmarketOS] (Alpine Linux-based)
  * [https://archlinuxarm.org/|Arch Linux ARM] (native on supported ARM devices)
  * [https://www.opensuse.org/|openSUSE] (including Kubuntu/YaST variants on ARM)
  * [https://alpinelinux.org/|Alpine Linux] (lightweight)

=== General pros ===

  * Full Linux userland and tooling (package managers, development tools).
  * Potentially longer software control and customization.
  * Privacy and freedom benefits for open-source distros.
  * Useful for turning devices into portable servers, dev rigs, or desktop-convergent systems.

=== General cons ===

  * Very limited hardware support: cellular modems, baseband, cameras, sensors, GPS, GPU acceleration, and power management often require Android drivers or vendor blobs.
  * Installation often requires unlocking bootloader, custom kernels, and technical skills — risk of bricking and voiding warranty.
  * Battery life and performance may be worse without vendor power optimizations.
  * App ecosystem smaller; many Android apps won't run natively (can use containers, Anbox/Waydroid with caveats).
  * Frequent manual maintenance and debugging on less-supported devices.

==== Android based alternatives ====

**Note**: I have only chosen a few here. These are the main ones I was interested in. Do not think that this is a definitive list; do your own research.

For example, GrapheneOS is my preferred because I have a Pixel phone, want to try without Google, and value privacy. /e/ is of interest because I also have an ancient Samsung tablet and my sister has a Samsung phone. You may have totally different needs from me, so do your own research.

  * [https://lineageos.org/|LineageOS]: Wide device support, regular security updates, some vendor features/drivers may be missing
  * [https://e.foundation/|/e/ (e Foundation)]: Google free by default, privacy forward apps and services, easier install on many phones, smaller app ecosystem
  * [https://grapheneos.org/|GrapheneOS]: Strong security and privacy, focus on Pixel devices means it will install on most Pixel devices, but limited availability for non-Pixel devices.
  * [https://calyxos.org/|CalyxOS]: Privacy-focused with Google services, limited device support, mainly Pixel
  
=== General pros ===

  * Extend device life with newer Android versions and security updates.
  * More privacy control (some ROMs remove Google services).
  * Increased customization, performance tweaks, and feature choices.
  * Active communities and device-specific builds.

=== General cons ===

  * Some hardware features (baseband/modem, camera optimizations, fingerprint sensors) may not work or need vendor blobs.
  * OTA ('Over the Air' installation)/update quality and frequency depend on project and device.
  * App compatibility can suffer if Google Play Services are removed. Some ROMs support workarounds like microG, an open-source reimplementation of Google Play Services, which allows many apps that depend on Google’s APIs to function. However, microG is not perfect—some apps (especially those with advanced DRM, banking, or push notification requirements) may not work, or may require additional setup. For more information, see: https://microg.org/.

===== Choosing Phone =====

Your choice in phones is limited by your choice of operating systems. You will either need to choose an operating system, then find the list of supported hardware, or choose a phone and find a list of supported operating systems.

In my case, I have used Pixel phones for a long time. I appreciate the hardware, and I also bought them because they had little vendor software installed (obviously, they have all sorts of Google apps, but so do other phones). The latter will be removed when I change OS, but it is the reason I have a Pixel that I'm willing to test on.

==== Unlocked vs OEM Unlocked ====

I decided to purchase a refurbished phone for my test. Since my current phone was a Pixel, I decided to buy a new Pixel.

I did not understand the difference between Unlocked and OEM Unlocked. I did not even know there was a difference. Because of that, I was looking for an Unlocked phone, which was unfortunately, not OEM Unlocked. I spent many fruitless days trying to get the boot load unlocked (OEM Unlock) and was saved only by the fact that I purchased from a vendor on [https://www.ebay.com/|ebay] who was sympathetic and allowed me to exchange it for one they had tested to be OEM Unlocked.

  * Unlocked (carrier unlocked): The phone is not restricted to a single carrier’s network — you can use SIM cards from different carriers (subject to supported bands). It typically means any carrier locks (SIM/network restrictions) have been removed.
  * OEM unlocked (bootloader unlocked): The device’s bootloader is unlocked, allowing you to flash custom recovery/ROMs, install custom kernels, root the device, or modify system partitions. This is a software/bootloader state, not a network lock
  
Basically, Unlocked (or Carrier Unlocked) means you can move from T-Mobile to AT&T to whatever just by putting your SIM in. If you purchase a device from your carrier, it is generally Carrier Locked until the device is completely paid off. After that, most times you need to contact the carrier to have it unlocked.

OEM Unlocked is what you need for these projects. It allows you to install a new operating system on it, overwriting Android. Some Linux Cellular operating systems do not require this as they simply install within Android, but those tend to run slower.

Again, ensure you have an OEM Unlocked phone. In my case, a simple request to the vendor would have ensured that (they go through their inventory and find one that is OEM Unlocked). Instead, it took me a couple of weeks of research, then a couple more while I returned the original to the vendor and received a replacement (I'm a cheapskate, so didn't opt for higher postage).

===== DANGER =====

You will always run the risk of bricking your phone. 'bricking' means messing up the phone so badly that it won't be usable.

If you are skittish, or just don't want to run the risk/take the time, there are vendors who specialize in supplying phones with your chosen OS installed. I was not able to locate a definitive list rapidly, but again, I understand there are vendors who do this for a living.

===== My Choice =====

As I have alluded to several times, I am choosing GrapheneOS, https://grapheneos.org/. My reasons for this are:
  * I am a security/privacy freak. I don't like the idea that anyone can track me, read my mail, try to sync my contacts after an update, stuff like that.
  * I am familiar with and trust the physical Pixel device
  * I do not use social apps (X, Facebook, etc...) so I don't care about installing them (however, you can install them on GrapheneOS, it just decreases security). The only apps I'll miss are Google Maps (I live in a metropolitan area with high traffic, but I'll give OSMAnd a chance) and Stellarium+
  * I like the look of the [https://grapheneos.org/install/web|web installer]. It looks much simpler than anything else and, since I will be recommending my results to some non-technical users, I'm going to try it that way. Later, I'll try the [https://grapheneos.org/install/cli|command line installation]
  
As of this writing (Spring, 2026), Graphene recommends Pixel 8 or 9 (not 10 yet), but says they support 6 and 7. I bought a Pixel 8, which will be my first install and, when I decide I like it, I'll install on a Pixel 7a.

As mentioned before, I did not realize what OEM Unlock meant, so I had to return the Pixel 8. I'll receive the new one in a couple of weeks and do the install then.

Oh, and I found this site that is very interesting: 

https://www.reddit.com/r/GooglePixel/comments/18sjlrf/my_ride_through_grapheneos_what_works_and_guide/.

This is for people who want the security of GrapheneOS, but still want their apps from the Google Play Store.

Here is a 20 minute YouTube video showing how to set up Graphene, after it is installed, for security.
https://www.youtube.com/watch?app=desktop&v=GLJyD9MJgIQ

===== Conclusion / Results (To Be Updated) =====
I am still in the process of testing GrapheneOS and other alternatives. Once I have completed installation and daily use, I will update this section with my experiences, recommendations, and any issues encountered. Stay tuned!

===== Glossary =====
^ Term ^ Definition ^
| Bootloader | Low-level software that loads the operating system on device startup. Must be unlocked to install custom OSes. |
| ROM | "Read-Only Memory"; in this context, a custom operating system image for phones. |
| Vendor blobs | Proprietary drivers or firmware provided by hardware manufacturers, often required for full hardware support. |
| microG | Open-source replacement for Google Play Services, used to enable some app compatibility on de-Googled Android ROMs. |
| Bricking | Rendering a device unusable (like a "brick") due to failed software modification. |
| OTA | Over-the-Air update; method for installing updates directly on the device without a computer. |
| Chroot/Container | Methods for running one OS inside another, often used to run Linux on Android devices. |
| F-Droid | Open-source app store for Android, focused on privacy and free software. |
| Pixel | Google’s flagship phone line, popular for custom ROMs due to unlockable bootloaders and good support. |

===== Links =====
  * https://duck.ai
  * https://ubports.com/
  * https://www.debian.org/
  * https://getfedora.org/
  * https://manjaro.org/downloads/arm/
  * https://archlinuxarm.org/
  * https://mobian-project.org/
  * https://pureos.net/
  * https://postmarketos.org/
  * https://www.opensuse.org/
  * https://alpinelinux.org/
  * https://lineageos.org/
  * https://e.foundation/
  * https://grapheneos.org/
  * https://calyxos.org/
  * https://www.ebay.com/
  * https://microg.org/
  * https://www.reddit.com/r/GooglePixel/comments/18sjlrf/my_ride_through_grapheneos_what_works_and_guide/
  * https://www.youtube.com/watch?app=desktop&v=GLJyD9MJgIQ