Motorola announces a partnership with GrapheneOS

Original Article ↗ Hacker News Discussion ↗

Overall reaction

  • Many are enthusiastic that GrapheneOS will no longer depend solely on Pixel hardware and see Motorola as a strong hardware partner.
  • Others are cautious, emphasizing that the real value depends on update policies, firmware access, and whether Motorola truly embraces openness rather than marketing.

Hardware, openness, and updates

  • Motorola is praised for decent, often “near‑stock” Android, good price–performance, and some standout models (e.g., ThinkPhone, Edge series, Razr/flip phones).
  • Criticisms: inconsistent cameras, hard‑to‑replace batteries, some models without video‑out, bloatware and adware (e.g., Glance, MotoApps), and historically weak update policies.
  • The partnership is framed as solving Motorola’s weakest point: security updates. A “Motorola Signature (2026)” device is said to have 7 years of support, with GrapheneOS support starting on a subset of future (2027+) devices.
  • GrapheneOS requirements (e.g., MTE‑capable SoC, separate high‑quality secure element, long support window) likely limit initial support to higher‑end models.

Security, privacy, and Chinese ownership

  • Major thread: confusion between Motorola Mobility (phones, owned by Lenovo) and Motorola Solutions (US gov/NSA contractor). Several comments stress they’re now separate companies.
  • Some worry about Lenovo being effectively Chinese state‑linked, especially for baseband/radio firmware and supply‑chain risks.
  • Others counter that US vendors also cooperate with their governments, that virtually all phones are China‑made anyway, and that GrapheneOS’ hardware requirements (strict baseband isolation, access to low‑level code) mitigate some risks.

Banking, payments, and app compatibility

  • Current GrapheneOS experience: many banking apps work; those requiring strict Google Play Integrity often do not.
  • Contactless payments: Google Wallet/Pay is blocked by Google’s certification rules, but alternative NFC wallets (Curve, PayPal, some EU banks’ apps) reportedly work fine on GrapheneOS.
  • Several people say loss of Google Pay is their main blocker; others argue a plastic card or watch is “good enough” and prefer privacy.

Regulation and long‑term support

  • EU ecodesign rules (5+ years of updates) are discussed; Motorola is criticized for publicly hunting for wording loopholes for cheaper models.
  • Supporters reply that the GrapheneOS partnership is explicitly about meeting stricter requirements on specific future devices (with 7‑year support mentioned), separate from legacy Motorola lines.

GrapheneOS project governance and trust

  • Some commenters express concern about limited transparency: who exactly controls signing keys, update servers, and donations, and who is now “in charge”.
  • Others note the foundation’s directors are publicly listed and argue the project has matured, but agree clearer communication and bios would build trust, especially as GrapheneOS moves into a more mainstream B2B role.

Use cases and wishlist

  • Strong interest in:
    • Flip/razr‑style phones with GrapheneOS.
    • Smaller form factors, headphone jacks, IPS or DC‑dimming OLED screens.
    • Desktop/“Ready For”/Android 16 desktop mode plus virtualization on GrapheneOS.
    • Better low‑end options eventually (~€200) and, for some, hardware kill‑switches and removable batteries.