Motorola to ship GrapheneOS on future Razr Fold

Motorola partners with GrapheneOS at MWC 2026

Motorola disclosed a partnership with the GrapheneOS Foundation during Mobile World Congress in Barcelona this week. The deal promises pre‑installed GrapheneOS on a yet‑to‑be‑named Motorola flagship and a port of select GrapheneOS features to the Razr Fold and Razr Ultra. The company called the arrangement a “long‑term partnership” and said joint research, software enhancements, and new security capabilities will roll out over the coming months. No hardware sketch was released, but Motorola emphasized that the future device will exceed the specs of its current Signature model, which still falls short of GrapheneOS’s hardware baseline.

Hardware requirements and the Razr roadmap

GrapheneOS currently runs only on Google Pixel phones because they meet a strict set of hardware security modules, including a Titan‑M chip and a verified boot chain. Motorola’s statement acknowledged that existing Razr models do not satisfy those requirements. The upcoming Razr Fold and Razr Ultra will inherit a subset of GrapheneOS security modules, according to the briefing. The exact features were not listed, but the mention of “certain features” suggests selective integration rather than a full OS flash. This approach mirrors earlier experiments where manufacturers expose isolated hardening components without abandoning the Google Play ecosystem. If the future flagship adopts a custom secure element comparable to Titan‑M, it could become the first non‑Pixel device to ship GrapheneOS out of the box. Until then, users will need to flash the OS manually, a process that remains inaccessible to the average consumer.

Expanding the GrapheneOS ecosystem beyond phones

Hyundai and Kia announced that their mobile apps now include official GrapheneOS support. The update reportedly required only a few seconds and occurs automatically when the app detects a compatible environment. No additional configuration steps are needed, according to the companies’ support pages. The move signals a modest shift in the Android‑centric app market. Historically, many OEM apps have relied on Google Play services for location, push notifications, and analytics. By adding GrapheneOS compatibility, Hyundai and Kia acknowledge a growing user base that runs de‑googled firmware. GrapheneOS also released a security preview (2026081301) that adds Google as a Network Location Provider. The change incorporates the September 2026 through January 2027 Android security patches and fixes a slate of CVEs. While GrapheneOS has traditionally avoided Google‑supplied services, the new provider offers a fallback for devices that lack a native GNSS‑only solution, reducing the need for third‑party location APIs.

Competitive context and market implications

Pixel devices have enjoyed de‑facto exclusivity for GrapheneOS since the project’s inception. The OS’s reputation for hardened privacy has attracted security‑conscious developers, but its market share remains limited to Pixel enthusiasts. Motorola’s entry could broaden the audience without diluting the OS’s security guarantees—provided the hardware meets the required attestation. Other Android OEMs have experimented with hardened builds, but none have partnered with the GrapheneOS Foundation itself. Samsung’s Knox and OnePlus’s OxygenOS offer security layers, yet they retain deep integration with Google services. Motorola’s strategy appears to target a niche that values both a distinctive form factor and a reduced Google footprint. The partnership also raises questions about supply‑chain logistics. GrapheneOS relies on open‑source AOSP code, but integrating proprietary secure elements demands coordination with chip vendors. If Motorola secures a Titan‑M equivalent, it may pressure other OEMs to reconsider their own security roadmaps.

What to watch

The first GrapheneOS‑preloaded Motorola device is expected in 2027, though the exact model name remains unconfirmed. Track the hardware specifications released in the next few months; a secure element comparable to Titan‑M will be the decisive factor for full OS adoption. Watch for the next GrapheneOS security preview, scheduled for early 2027, which will list additional CVE fixes and potentially expand the list of supported location providers. The rollout of Hyundai and Kia’s GrapheneOS‑compatible apps will also serve as a barometer for broader OEM willingness to support de‑googled environments. Finally, monitor Pixel 11’s official GrapheneOS support timeline. If Google enables the OS on its own next‑generation hardware, it could reinforce the perception that GrapheneOS is a viable alternative for mainstream users, while Motorola’s entry tests that hypothesis on a non‑Pixel platform.