Daily Driving GrapheneOS

Original Article ↗ Hacker News Discussion ↗

Installation & Reverting to Stock

  • Several users report that installing GrapheneOS on Pixels and reverting to stock is straightforward via web installers in a desktop browser with USB.
  • Both directions (stock → GrapheneOS and back) wipe device data; backups are required.
  • eSIMs generally survive an install of GrapheneOS and can now be set up directly on GrapheneOS, but whether they always survive a full “round trip” back to stock is unclear.

Banking Apps, 2FA & Contactless Payments

  • Experiences with banking apps are mixed but mostly positive: many report multiple banking and trading apps (Germany, Netherlands, UK, US, Sweden, Belgium) working fine.
  • A community-maintained compatibility list is referenced; some apps require toggling “exploit protection compatibility mode.”
  • Device attestation is the main technical friction for some banks; a detailed attestation guide is linked.
  • Contactless payments are a recurring pain point:
    • Google Wallet often fails due to lack of Google whitelisting.
    • Some succeed using alternatives like Curve, PayPal, or bank-specific NFC solutions; others fall back to a physical card tucked behind the phone case.
    • For some, loss of phone-based tap-to-pay is a dealbreaker; others argue using a card (or even cash) is an acceptable trade-off.

Daily Use, Apps & Backups

  • Many daily drivers report GrapheneOS as stable and smooth over months/years, praising:
    • Minimal default apps, zero bloat/ads, and fast security updates.
    • Sandboxed Google Play and the ability to selectively install Google apps while restricting permissions (e.g., disabling network for Gboard or Google Camera).
  • Ride-hailing (Uber and others) generally works, though one user had payment verification failures.
  • RCS via Google Messages was broken for months but is now working again; some left GrapheneOS over this and would consider returning.
  • Seedvault backups are widely criticized as unreliable; some recommend relying on web apps and file sync instead.

Security, Privacy & Trade-offs

  • Enthusiasts highlight strong privacy, reduced Google privilege, and better carrier/VPN controls versus stock Android and iOS.
  • Some argue mobile banking is safer on modern phones than on desktops; others refuse banking apps entirely and use hardware tokens or card readers.
  • A minority is strongly skeptical: one calls GrapheneOS a “toy” for privacy enthusiasts and claims their device was compromised as easily as stock Android (no technical details given).

Alternatives, Ecosystem & Outlook

  • Other de-Googled or minimal Android options mentioned: LineageOS, /e/OS, iodéOS, de-Googled Samsung with work profiles.
  • Some users just want a near-plain AOSP OS; others dream of open iPhone hardware or government-mandated openness and APIs.
  • The upcoming Motorola–GrapheneOS collaboration is seen by some as a path to more mainstream adoption; others fear it could dilute the project’s focus, though current user growth is described as strong.