LineageOS 23

Original Article ↗ Hacker News Discussion ↗

Who Uses LineageOS and Why

  • Common use cases:
    • Extending life of older phones/tablets after OEM support stops, while still getting recent Android versions and security patches.
    • Removing OEM bloatware (especially from vendors like Samsung, Moto, Kindle Fire) for better performance and battery life.
    • Reducing or avoiding Google dependence, using F-Droid and other app stores instead of Play Store.
    • Having a uniform, minimal, predictable Android experience across multiple devices.

Privacy, Google, and “De-Googling”

  • Many see stock Android/OEM ROMs as spyware-heavy; LineageOS is valued for being FOSS and able to run without Google Play Services.
  • Some note LineageOS still uses Google for DNS/captive portal checks by default, but say this is easily patched.
  • GrapheneOS is viewed as the more complete “de-Google”/security solution, but only for Pixels; some find it ironic that de-Googling starts with a Google phone.

Banking, Payments, and App Compatibility

  • Mixed experience:
    • Many banking apps and financial services work fine on LineageOS, sometimes with root hiding (Magisk) and microG.
    • Google Wallet / tap-to-pay often does not work; same on GrapheneOS.
    • Some regions force app-only banking, making web fallbacks impossible.
  • Various “root-detection” or “unapproved platform” blocks (e.g., garage doors, AC control, McDonald’s app) frustrate users.

LineageOS vs GrapheneOS (and Others)

  • Characterizations from the thread:
    • Security & privacy first: GrapheneOS.
    • Freedom, customization & broad device support: LineageOS.
  • Debates:
    • Some praise GrapheneOS’s hardening and early security fixes.
    • Others criticize GrapheneOS for forbidding things like system-wide firewalls or full app-data backups, seeing this as prioritizing app developers over device owners.
    • Limited device support for GrapheneOS (Pixels only) vs many OEMs for LineageOS.

Hardware, Ecosystem, and Regulation

  • Device choices discussed: Pixels, Fairphone, Moto, OnePlus, Samsung; warnings about Samsung eFuses and newer models blocking bootloader unlocks.
  • Concern that Google is making third-party ROM support harder (e.g., Pixel kernels as stripped tarballs).
  • Some call for EU-style regulation to counter monopolistic trends; others blame regulation and modem/baseband realities for entrenchment.

Other Topics

  • Backups: nandroid-style backups with root and tools like Neo Backup; generally workable but with quirks.
  • Non-phone uses: Nintendo Switch, Android TV boxes, Raspberry Pi builds, VM/Waydroid setups.
  • Adoption barriers: needing ADB/PC for updates, streaming services refusing unapproved devices, tightening bootloader policies.