I'm switching my phone from Android to Linux

Original Article ↗ Hacker News Discussion ↗

Growing frustration with Google’s tightening control over Android — from Play Services lock-in to remote attestation and app-store gatekeeping — is pushing some users to experiment with “real” Linux phones and alternative mobile OSes like Sailfish, Ubuntu Touch, postmarketOS, and GrapheneOS. Commenters weigh the appeal of owning and hacking their device against harsh trade-offs: weak hardware support, poor cameras, missing banking and government apps, and patchy VoLTE, GPS, and app ecosystems. Many conclude that, for now, the most practical escape from the Google/Apple duopoly is either a de-Googled Android (e.g. GrapheneOS on a Pixel) or carrying two phones: one locked-down handset for critical apps and one Linux-based device for everything else.

State of Mobile Linux Options

  • Multiple Linux-based OSes discussed: postmarketOS, Ubuntu Touch/UBports, Sailfish OS, Mobian, PureOS on Librem 5, Plasma Mobile, Phosh.
  • Some users report successfully daily‑driving Linux phones for years; others find them unusable beyond tinkering.
  • Sailfish’s Android compatibility layer is seen as key to its practicality; Ubuntu Touch and postmarketOS rely more on native apps and Waydroid.

Hardware Support and Performance

  • Hardware support is a major pain point: cameras, fingerprint sensors, suspend/battery, VoLTE/eSIM, Bluetooth, and USB‑C video out are often partial or broken.
  • Opinions differ sharply on devices like Pinephone/Pro, Librem 5, Furiphone, F(x)tec:
    • Fans say they’re “good enough” and improving fast.
    • Critics describe them as unbearably slow and buggy, with outdated SoCs compared to modern Android/iOS phones.
  • Mainlining kernels and reverse‑engineering vendor blobs are described as hard but not “hacky”; long‑term support (e.g., Nokia N900) is a positive example.

Google/Android Ecosystem Concerns

  • Many see Android’s path as “death by a thousand cuts”: Play Services centralization, proprietary APIs, Play Integrity, impending store lock‑down (linked campaign), and Wear OS watch‑face restrictions.
  • AOSP is defended by some as still open and not inherently dependent on Play Services; others argue that in practice most apps now assume GMS.
  • De‑Googled Android variants (GrapheneOS, LineageOS, /e/OS) are proposed as pragmatic compromises.

Apps, Banking, and Government Lock‑in

  • Biggest blocker to Linux phones: critical apps (banking, ID, transit/taxi, parking, digital keys, government services) often require Android/iOS and Play integrity/attestation.
  • Some regions still support web, SMS, hardware tokens, or card readers; others report app‑only banking and public services, effectively mandating the duopoly.
  • Workarounds: keeping a cheap Android phone in a drawer, or running Android in a VM (Waydroid), though attestation often breaks this.

Usability, Security, and Ownership

  • Pro‑Linux arguments: genuine device ownership, root access, standard GNU/Linux stack, easier hacking/automation, less tracking.
  • Critics emphasize poor UX: keyboards, performance, janky updates, limited app ecosystems, weak cameras and maps.
  • Many conclude a two‑phone model is currently most realistic: one locked‑down Android/iOS device for “must‑have” apps, one Linux (or de‑Googled Android) device for everything else.

Long‑Term Prospects

  • Some believe LLM‑assisted development and growing dissatisfaction with Google/Apple could accelerate Linux phone ecosystems.
  • Others see maintaining a full mobile OS stack as too costly for volunteer projects, arguing that strengthening open Android (microG, alternative services) is a more viable path.