Daily driving a Linux phone, but why?

Original Article ↗ Hacker News Discussion ↗

De-Googled Android as “Linux phone”

  • Multiple commenters run stock Android with no Google account, using F-Droid, Aurora Store, and privacy tools (e.g., NetGuard, Obtanium).
  • Third‑party ROMs (LineageOS, GrapheneOS, CalyxOS, /e/OS) are presented as practical “Linux phones” with strong app compatibility.
  • Pixels, Fairphone and some Motorolas/OnePlus/Sony models are highlighted for good ROM support and (sometimes) bootloader relocking, improving resistance to physical tampering.

What Distinguishes “Linux Phones” from AOSP?

  • One side argues AOSP-based systems are already free/open, efficient, secure, and deeply integrated with phone hardware; reinventing the stack (XDG/dbus/etc.) on phones is seen as NIH and destined to remain niche.
  • The other side stresses:
    • Independence from Google’s priorities and development model.
    • Ability to run a “normal” Linux distro (Debian/Alpine), desktop apps, terminals, SSH, standard backups, and scripting.
    • Easier kernel/mainline work and community-driven control, despite remaining binary blobs.

Daily-Driving Linux Phones: Mixed but Improving

  • Reported daily drivers include PinePhone / PinePhone Pro (often with postmarketOS, Mobian, Arch), Librem 5, Sailfish on Xperia, Ubuntu Touch on Volla, and FuriPhone.
  • Success stories: stable calls/SMS, VoLTE in some cases, Firefox, desktop apps, Waydroid for key Android apps, acceptable performance on tuned setups.
  • Pain points: audio glitches (sometimes requiring reboots), incomplete VoLTE coverage, short battery life, occasional regressions, sluggish UIs on weaker GPUs, spotty GPS/maps.
  • FuriPhone is praised as the first “truly usable” Linux phone for many: Debian-based, good camera, Android apps via Waydroid, but large, somewhat rough, and relatively expensive.

Security Models and Tradeoffs

  • Some commenters distrust Linux phones’ lack of Android/iOS‑style mandatory sandboxing and secure boot, and want that model on desktop Linux.
  • Others note that desktop Linux already has tools (AppArmor, SELinux, Flatpak, containers) but they’re not consistently integrated or defaults.
  • Android security is praised (especially GrapheneOS) but vendor patch delays and closed ecosystems are criticized; Linux distros are said to patch faster.

Apps, Services, and Practicality

  • Major friction points: banking apps, proprietary 2FA (e.g., MS Authenticator), government ID, car keys, payments, EV charging, and vendor configuration apps.
  • Strategies:
    • Avoid such services or replace with web interfaces.
    • Run Android in Waydroid or keep a secondary Pixel/Android phone at home for rare tasks.
  • Some use Linux phones partly to curb smartphone addiction; others warn that social media is still easily reachable via mobile web.

Broader Reflections

  • Debate over whether Android “counts” as a Linux OS versus “GNU/Linux + standard userspace.”
  • Strong desire for phone hardware to become PC-like and standardized so any OS can be installed.
  • Recognized tradeoff: maximal privacy/control vs friction with mainstream social and commercial infrastructure.