GrapheneOS announced on September 6, 2026 that it is overhauling its default apps into what the project calls “modern” apps, shipping RCS support in its messaging client, and implementing a secure clipboard designed to stop other apps from reading clipboard data (Privacy Guides, 2026). The announcement landed just days after the project publicly refused to support the Pixel 11. Why? Google’s Tensor G6 chip shipped without Memory Tagging Extension enabled. The two stories together paint a picture of a privacy OS evolving fast while its hardware foundation wobbles.
TL;DR: GrapheneOS is rebuilding its default apps as “modern” apps, adding RCS support to its messaging app, and introducing a secure clipboard that blocks apps from accessing clipboard contents. Separately, the Pixel 11 port hit a wall over missing MTE support, though developers later found “at least bare minimum support for MTE” (Privacy Guides, 2026).
What Did GrapheneOS Announce for Its Default Apps?
The project announced a full overhaul of its default apps, converting them into “modern” apps and folding RCS messaging support into the messaging client, alongside a new secure clipboard feature (Privacy Guides, 2026). This is one of the largest user-facing changes in the operating system’s history. Previously, GrapheneOS focused most of its engineering effort on hardening the Android framework itself rather than polishing the bundled apps.
The timing matters. The announcement came on September 6, 2026, roughly a week after the Pixel 11 controversy erupted. On August 31, 2026, TechTimes reported that Google had removed Pixel 11 memory safety hardware, blocking the GrapheneOS port entirely. The project had stated it would not support the Pixel 11 because the Tensor G6 chip lacked Memory Tagging Extension, a hardware security feature central to the operating system (Notebookcheck, 2026).
So the app overhaul reads partly as a signal. The team is still shipping. Leaked documents showed Google had planned and then cut the key Pixel 11 security feature intended to benefit GrapheneOS (Notebookcheck, 2026). Meanwhile, GrapheneOS keeps expanding elsewhere — BGR reported it now offers 7 years of software support for select new Motorola phones. The default apps refresh shows where the project’s priorities now lie: usability without giving up privacy.
How Does the New Secure Clipboard Feature Work?
The secure clipboard is designed to stop apps from accessing clipboard data (Privacy Guides, 2026). That is the core promise, and it addresses a long-standing Android weakness. On stock Android, any app granted clipboard permissions can read whatever you copied — passwords, crypto seed phrases, addresses, two-factor codes. Clipboard snooping has been a documented Android privacy problem for years.
GrapheneOS has historically restricted background clipboard access through its permission and sandboxing model. The new feature goes further by treating clipboard contents as sensitive data that foreground apps should not freely harvest either. The announcement frames it as part of the broader overhaul of the default app experience, tying clipboard handling into the modernized app stack (Privacy Guides, 2026).
Why does this matter in practice? Consider how people actually use phones. You copy a password from a manager, switch apps, paste it. Between those two taps, every app you passed through had a window into that secret. That window is what GrapheneOS wants closed. It fits the project’s philosophy: hardware-backed security where possible, tightened sandboxing everywhere else.
The feature also complements the MTE story. MTE protects memory; the secure clipboard protects data in transit between apps. CyberInsider reported the project may skip Pixel 11 over the missing hardware feature — but software defenses like the secure clipboard apply regardless of chip support. Layered defenses are the GrapheneOS way.
Why Is RCS Support Coming to GrapheneOS Messaging?
RCS support is arriving because messaging interoperability has become unavoidable, and GrapheneOS users were stuck outside it (Privacy Guides, 2026). Rich Communication Services is the protocol Google pushed as the replacement for SMS, bringing read receipts, typing indicators, higher-quality media, and encryption to Android messaging. Apple added RCS support in iOS 18, making it the default cross-platform bridge between iPhone and Android users.
For a privacy-focused OS, that created a gap. Without RCS, GrapheneOS users fell back to plain SMS when texting iPhone owners — an unencrypted, decades-old protocol. Adding RCS to the GrapheneOS messaging app means users get modern messaging without installing third-party clients that may demand Google account integration or broad permissions. The project bundles it into the same “modern apps” overhaul announced September 6, 2026 (Privacy Guides, 2026).
There is tension here, though. RCS on Android typically routes through Google’s servers and Google Messages. A de-Googled operating system implementing RCS has to work around that dependency. The announcement confirms the messaging app gains RCS support as part of the rework, which suggests the team found a workable path — but details on server routing remain thin in the source coverage. What is clear is the goal: native, modern messaging inside an app users can actually trust, without sending them to Google’s own client.
What Does ‘Modern’ Mean for GrapheneOS Default Apps?
“Modern” means rebuilding the bundled apps to meet current Android design and functionality expectations, rather than shipping stripped-down utilities (Privacy Guides, 2026). Historically, GrapheneOS inherited basic AOSP apps — functional but dated compared to polished commercial alternatives. That pushed privacy-conscious users toward third-party apps, which increases attack surface and undermines the point of a hardened OS.
The overhaul targets that problem directly. The messaging app gains RCS. The secure clipboard changes how copied data flows. The broader default app refresh aims to make first-party apps good enough that users do not need replacements. Fewer third-party apps means fewer permission grants, fewer data flows, and a smaller trust footprint.
The context makes this push more urgent. When the Pixel 11 launched without usable MTE, GrapheneOS warned buyers away — PurePC reported the team strongly advises against buying the new phones for anyone counting on the custom ROM. PhoneArena went further, reporting that security researchers advised buyers to skip the Pixel 11 entirely. An OS that loses its flagship hardware line needs to compete harder on software experience.
Then came the twist. Android Authority reported that Pixel 11 support is not dead, as developers tested newly discovered MTE support and its performance impact. Privacy Guides confirmed the hardware does have “at least bare minimum support for MTE,” discovered after GrapheneOS hit its initial roadblock. The team also noted that Android 17 QPR2 Beta 4, released August 28, 2026 as the first beta with Pixel 11 support, still ships with MTE completely disabled in the OS. Modern apps, a secure clipboard, and an unresolved hardware saga — that is GrapheneOS in late 2026.
Why Can’t GrapheneOS Finish Its Pixel 11 Port?
GrapheneOS stated it could not complete its port to the Pixel 11 because the Tensor G6 chip appeared to lack Memory Tagging Extension (MTE) support, with the OS boot configuration passing arm64.nomte unconditionally (GrapheneOS on Bluesky). MTE is a hardware memory-tagging mechanism that catches memory corruption bugs at the CPU level, and the GrapheneOS project treats it as a baseline requirement rather than a nice-to-have extra. Without it, the port would ship a weaker security posture than every previously supported Pixel generation.
The situation looked even worse once leaked documents surfaced. Reporting from Notebookcheck indicated that Google had planned and then cut the MTE capability from the Pixel 11 — meaning the removal was a deliberate engineering decision, not an oversight. PhoneArena went as far as framing it as Google making the Pixel 11 unsafe to save a few bucks, with security researchers advising buyers to skip the device entirely.
The team’s initial verdict was blunt. The project strongly discouraged anyone hoping to run the private custom ROM from buying the new phones (PurePC). That changed within days, but more on that below.
Did the Pixel 11 Turn Out to Support MTE After All?
Yes — partially. After hitting the roadblock, GrapheneOS developers discovered that the Pixel 11 hardware does have “at least bare minimum support for MTE,” and that the device “may still be usable” for the project (Privacy Guides). This flipped the narrative from a hard dead end to an open engineering question with real caveats attached.
Android Authority reported that the developers are actively testing the newly discovered MTE support and, critically, its performance impact. “Bare minimum” support is not the same as the full implementation found in earlier Tensor chips. The team needs to measure how much overhead tagging introduces on the G6 silicon before committing to anything.
The OS-side problem also remains. The Bluesky post noted that in the Android 17 QPR2 Beta 4 build released on August 28 — the first beta with Pixel 11 support — MTE is still completely disabled in the OS and arm64.nomte is unconditionally passed at boot (GrapheneOS on Bluesky). So hardware support existing does not mean Google enabled it. GrapheneOS would have to bridge that gap itself.
Which Phones Can Run GrapheneOS Now?
The officially supported list still centers on Google’s Pixel lineup, since GrapheneOS depends on Pixel hardware security features like the Titan M security chip, verified boot, and MTE on newer models. The Pixel 11 sits in limbo: hardware MTE support exists, but the port is unfinished. Meanwhile, the project made its first major expansion beyond Pixels in years.
GrapheneOS announced support for select Motorola phones — a notable shift for an OS historically tied to a single vendor. Coverage of the rollout appears at BGR.
The current landscape, based on the sources:
- Pixel 6 through Pixel 10 series — the traditional GrapheneOS base, with devices meeting the project’s hardware security baseline
- Pixel 11 — port blocked pending MTE testing; not yet supported
- Select Motorola models — newly supported, with a long support commitment
- Other Android vendors — not supported; devices lack the required security hardware
How Long Will GrapheneOS Support New Devices?
For the new Motorola phones, GrapheneOS is offering seven years of software support — a huge window that matches Google’s own Pixel support commitment (BGR). That matters because deGoogled ROMs live or die by long-term firmware and security patch availability. A device dropped after two years is a bad privacy investment.
For Pixels, support has historically tracked Google’s own update lifetime for each generation, with GrapheneOS shipping hardened builds alongside upstream releases. The Pixel 11 question complicates this: if the port proceeds, its timeline depends on how quickly developers can validate MTE performance and work around Google’s boot configuration.
Seven years is not a marketing number here. It reflects the project’s practice of supporting hardware for its full vendor lifecycle rather than pushing users toward premature upgrades.
Should You Buy a Pixel 11 for GrapheneOS?
No — not yet. The GrapheneOS team strongly advised against buying the new phones for anyone counting on running the privacy-focused custom ROM (PurePC). Even after the discovery of bare-minimum hardware MTE support, the OS-level implementation remains disabled in current Android 17 QPR2 betas (GrapheneOS on Bluesky).
Security researchers echoed that advice earlier in the saga, telling buyers to skip the Pixel 11 over the removed memory safety hardware (PhoneArena). The leaked documents showing Google planned and then cut the feature (Notebookcheck) add another reason for caution: a vendor that removes security hardware to cut costs may make similar calls again.
Practical alternatives exist today. Supported Pixels and the newly added Motorola phones with seven years of support (BGR) are both viable paths. Wait for an official GrapheneOS announcement before spending money on a Pixel 11.
Frequently Asked Questions
What is the secure clipboard in GrapheneOS?
GrapheneOS announced a secure clipboard feature that stops apps from accessing clipboard data unless they are in focus, as part of an overhaul of default apps (Privacy Guides). This closes a common Android leak where background apps could read copied passwords or addresses. It ships alongside the redesigned modern default apps.
Will GrapheneOS support the Pixel 11?
It is not confirmed yet. The project initially refused to support the Pixel 11 because the Tensor G6 was believed to lack MTE (Notebookcheck), but developers then found the hardware has “at least bare minimum support for MTE” (Privacy Guides). The final decision depends on ongoing performance testing.
Does the new GrapheneOS messaging app support RCS?
Yes. GrapheneOS announced it is overhauling default apps into modern apps, including RCS support in the messaging app (Privacy Guides). This brings the deGoogled ROM closer to feature parity with stock Android messaging. It removes one of the most common practical objections to switching.
Which Motorola phones get GrapheneOS support?
GrapheneOS expanded to select Motorola phones — its first major non-Pixel device family — with seven years of software support (BGR). The support window matches Google’s own Pixel commitment. Check the official GrapheneOS device list for the specific approved models.
Summary
- GrapheneOS rebuilt its default apps as modern replacements and added RCS messaging support plus a secure clipboard that blocks background apps from reading copied data (Privacy Guides).
- The Pixel 11 port stalled because the Tensor G6 was believed to lack MTE, with leaked documents showing Google planned and then cut the feature (Notebookcheck).
- Developers later found bare-minimum hardware MTE support, so the Pixel 11 “may still be usable” pending performance tests (Privacy Guides).
- Select Motorola phones now run GrapheneOS with a seven-year support commitment (BGR).
- Until an official port lands, buy a supported Pixel or Motorola device instead of a Pixel 11.
Want to follow the Pixel 11 saga as it develops? Watch the GrapheneOS Bluesky feed and the Privacy Guides news section for the definitive word on whether the port ships.