Devices with GrapheneOS support should be available in 2027

Original Article ↗ Hacker News Discussion ↗

GrapheneOS has confirmed that the first officially supported non-Pixel phones—high-end Motorola flagships using Qualcomm’s latest Snapdragon chips—are expected in 2027, once they meet strict requirements for long-term updates and advanced hardware security features like memory tagging and secure elements. Commenters weigh the trade-offs between price, hardware quality, and privacy, and explore how well such devices can support everyday needs such as banking apps and NFC payments amid growing use of Google’s Play Integrity attestation. The thread also broadens into a comparison between Android-based platforms and “mainstream” Linux phones, with many arguing that Android’s security model, app ecosystem, and hardware integration make it a more realistic foundation for privacy-focused mobile OSes.

Motorola–GrapheneOS Partnership & Timeline

  • First officially supported Motorola devices are targeted for 2027, initially high-end flagships (Signature, Razr fold, Razr flip / Razr Ultra class).
  • Support is expected to coincide with Motorola’s normal flagship release cadence, not retrofitted to existing models.
  • Some commenters misread this as “GrapheneOS coming in 2027 to current models”; core clarification: current Motorolas do not meet requirements.

Hardware & Security Requirements

  • Pixels are currently the only phones meeting GrapheneOS’ update and hardware‑security bar.
  • Key missing pieces on most devices:
    • Hardware memory tagging (MTE) – currently only Snapdragon 8 Elite Gen 5; next-gen Snapdragon flagships add needed features and a better secure element.
    • Long-term, timely security updates from OEM + Qualcomm.
  • Lower‑end Motorola devices lag on both security features and update commitments; support may come later if Qualcomm/OEM improve this.
  • Unlockable bootloader with all security features intact is explicitly required.

App Ecosystem, Banking, and Attestation

  • Major advantage of staying on Android: access to existing apps, especially banking, government, and messaging.
  • GrapheneOS uses a sandboxed Google Play layer and reportedly runs “almost all” apps; about 90% of banking apps work, according to a community compatibility list.
  • Problems concentrate around:
    • Google’s Play Integrity API and other attestation / root-detection SDKs.
    • Some banks, governments, and car makers enforcing “stock Android only”; a few have partially reversed positions after user pressure.
  • Tap‑to‑pay works via some regional providers (e.g., Curve, PayPal, certain EU banks). Google Pay continues to block GrapheneOS and may require regulatory pressure to change.

Android vs “Mainstream Linux” on Phones

  • Long thread debating why not base a secure mobile OS on a desktop-style Linux distro.
  • Arguments for Android/AOSP: vastly better existing mobile security model (mandatory app sandbox, SELinux-based MAC/MLS, verified boot, modern exploit mitigations, heavy use of memory‑safe languages), app ecosystem, and power management.
  • Arguments for Linux phones: more user control, Nix-style declarative systems, dislike of Google ecosystem.
  • Counterpoint: current Linux phones (PinePhone, Librem, Sailfish, etc.) are widely described as immature (poor camera, telephony, battery, and security), with fragmented efforts and weak app support.

Google, Pixels, and Open-Source Friction

  • Several comments criticize Google:
    • Pixels seen as mediocre hardware (battery, Tensor performance, Exynos/Mediatek modems).
    • Kernel/device source for Pixels now distributed via request forms and Drive tarballs with squashed history, seen as hostile to GPL’s “preferred form for modification.”
  • Some worry Google’s tightening control (e.g., Play Integrity) makes non‑Google Android increasingly fragile.

Cost, Availability, and Form Factors

  • Expectation that Motorola GrapheneOS flagships will be pricier than Pixels; concern from users on limited budgets.
  • Enthusiasm for:
    • Foldables and especially Razr‑style flips as “small phone” replacements.
    • Future trickle‑down of GrapheneOS support to cheaper devices once hardware catches up.
  • Disappointment that Fairphone and current low‑end Motorolas (with SD card support, smaller sizes) don’t and likely won’t meet the required security/update bar.