GrapheneOS

We're happy to announce a long-term partnership with Motorola. We're collaborating on future devices meeting our privacy and security standards with official GrapheneOS support. motorolanews.com/motorola-three…

@PiereChangstein Their attacks on GrapheneOS are getting increasingly desperate because we're winning. We're not going to leave.

@GrapheneOS Please don't leave X over this.

There's a group coordinating attacks on GrapheneOS on X via a Telegram group. They have a couple dozen accounts here. They've based their attacks around claiming modular builds and updates via packages somehow aren't open source. We debunked this here: x.com/GrapheneOS/sta…

@nikolaiG22 @techdroider There's not going to be any change from this on GrapheneOS.

@techdroider Hey, @GrapheneOS , I assume this nonsence about Google saying what I can and cannot do with my device will be ignored by you, so we all keep using Obtanium, Aurora, F-Droid etc as we successfully and safely do for years?

As expected, Google is making sideloading harder on Android… but it is NOT going anywhere Here's the new way in simple steps: • Turn ON Developer Mode in settings • Confirm no one is forcing you • Restart your phone and unlock again • Wait 24 hours, then verify with fingerprint / face / PIN • Now you can install apps (7 days or always) More steps, but you still have the choice

@ssamat @Le_happy_can It's not clear what Google thinks they gain from making monthly and quarterly updates exclusive to the stock Pixel OS without pushing the code to AOSP. It makes Pixels increasingly non-viable as a platform for other operating systems and negatively impacts Google's OEM partners.

@ssamat @Le_happy_can GrapheneOS made substantial contributions to Android Open Source Project privacy and security but we're no longer able to do that due to changes by Google. It has also become increasingly difficult to support Pixels and we'll likely be fully using different devices in the future.

Android has always been about choice. Today, we’re sharing how we’re evolving the ecosystem so you don’t have to choose between an open platform and a secure one. We’re introducing a new advanced flow for sideloading where power users can go through a one time flow to enable their devices to load software from unverified developers. We’ve designed this process to stop more vulnerable users from being coerced to do this during a guided scam (which are a major problem today for people) We also have new account types for students and hobbyists that address their feedback.

@P4mui @sorrow_io @COWCATGames @grap There's not going to be any change to installing apps on GrapheneOS from this. It's a Google Mobile Services device feature and GrapheneOS doesn't have any of that built into the OS.

@sorrow_io @COWCATGames @grap Graphene tu veux dire ? Normalement non mdrr @GrapheneOS just to confirm: you guys will not have that on graphene right?

Google a tranché concernant le sideloading sur Android à partir de fin 2026 : Au lieu d’interdire les apps de développeurs non-vérifiés (pour passer outre la solution était adb) : Google va vous donner le choix d’une manière bien particulière : la désactivation de cette « sécurité » (en bref activer un mode développeur), avec un délais de 24h avant de pouvoir vraiment la désactiver (c’est quelque chose à faire UNE fois, pas une fois par apps)

@Yiannis128 @techdroider It has no impact on GrapheneOS.

@techdroider @GrapheneOS Would it be difficult to completely bypass this new system and keep the old system intact?

@underscor31 @mainlinedbutter @TeleviziaSTB @TheVancedGamer Reading what you've posted publicly isn't an invasion of privacy. We're taking sensible steps to protect ourselves from relentless attacks on our project and team. That includes archiving what we can find from people trying to harm us in case our legal team ends up needing it.

@Fxg0dfan @rhizome @webrecorder_io archive.today is the same site as archive.ph. Multiple people have raised concerns about us using it. We don't know enough about to comment on it right now but you can find info about it searching for it.

@GrapheneOS archive.today Sadly sunsetting new archives as of May, but has promised to keep their recordings, conifer.rhizome.org by @rhizome Browsertrix if you need automation, ArchiveWeb.Page for doing locally through software or extension, both by @webrecorder_io

We posted a thread on our Mastodon instance addressing the underhanded attacks being made on GrapheneOS by Volla due to our opposition to their Unified Attestation API: @GrapheneOS/116251325625494349" target="_blank" rel="nofollow noopener">grapheneos.social/@GrapheneOS/11… An account previously pretending to be a fan supporting Volla has been clearly exposed as run by them. Despite how this account has previously posted, it began repeatedly posting on behalf of Volla and referring to themselves as being part of it. They referenced Volla contacting us half a year ago wanting a partnership with us which didn't go anywhere as they're unable to meet our requirements. We've opposed Unified Attestation on very reasonable grounds which we've once again elaborated on in the linked thread after covering this. This account clearly run by Volla themselves has repeatedly posted outrageous conspiracy theories about GrapheneOS implying we're working for the US government. We included links to a history of posts predating our opposition to Unified Attestation where they engage in false marketing of Volla products and try to convince people to use those over other options with inaccurate claims. That includes them replying to threads where people discussed GrapheneOS. They were misleading people about GrapheneOS prior to us speaking of them. They're now attacking us in a super underhanded way because we oppose them seizing control over which devices and operating systems are allowed for European banking/government apps. Don't allow them to memory hole this. The account is very clearly run by Volla, has openly acknowledged it and proven it with insider knowledge. We also have a very good idea of exactly who is running the account due to the writing style. These companies using sockpuppet accounts and personal accounts to attack us doesn't lessen it.

@underscor31 @mainlinedbutter @TeleviziaSTB @TheVancedGamer Your group has a dozen accounts with few follows or followers beyond each other. You're making completely disingenuous claims about GrapheneOS in a highly unethical attempt to cause harm to it. We've thoroughly debunked your nonsensical fabrications at x.com/GrapheneOS/sta….

I have been looking into @GrapheneOS for long, even once considered pushing it at the workplace to ensure our mobile devices can be as safe as they can no matter their age, but hesitated after seeing what is going on in the Team, the Codebase and the Community. [1/x]

> Once again: Please stick to the facts. We're sticking to the facts. You're posting baseless conspiracy theories about GrapheneOS: x.com/GrapheneOS/sta… > We are not attacking the Graphene OS team. We are clarifying the intent behind UnifiedAttestation and have invited the Graphene OS team to participate. You are attacking GrapheneOS and the GrapheneOS team. > Vollaficationist is not an account belonging to Volla Systeme or any Volla Systeme employee. If it doesn't belong to a Volla employee, how do they know when Volla contacted GrapheneOS and other internal details from Volla? Why do they have a very unique writing style and posts with unique content matching one of Volla's employees on LinkedIn and elsewhere? > Today, some apps use Google Play Integrity. These are primarily banking, payment, and digital ID apps. In some countries, citizens rely on these apps because government-issued ID apps, for example, are a prerequisite for opening a bank account. We view this development critically. A tiny portion of Android apps use the Play Integrity API. 90% of banking and government apps do not enforce it. >99.999% of other categories of apps do not enforce it. This is something we can be fought and defeated. Creating another system with a similar design helps the Play Integrity API by legitimizing it and harming efforts to defeat it. > To be able to offer alternative Android operating systems to all users without limitations, UnifiedAttestation is an open-source, freely available alternative to Google Play Integrity. It's a centralized, anti-competitive system which will not permit freely using arbitrary hardware and software. It will only permit products from the companies involved in it. It's irrelevant whether the server side code is open source to whether it's anti-competitive. It cannot simply be hosted by anyone else since apps aren't going to trust arbitrary servers. Claiming it's open source is simply a red herring. It being freely available is worse than if it was paid. > We see a greater chance of convincing app developers and publishers who currently use Google Play Integrity to adopt an alternative rather than to abandon Google Play Integrity altogether. However, this persuasion will only succeed if app developers and publishers see a relevant market. Hence the consortium. Perhaps we will even succeed in making UnifiedAttestation an open standard. The Android hardware attestation API already exists. Unified Attestation is entirely built on top of it. There's no legitimate reason for it to exist beyond a power grab. > Once again, for clarification: UnifiedAttestation should not be a prerequisite for apps to be installed and used on alternative Android systems—not at all. It concerns a small subset of apps that currently prevents customers from using an alternative Android operating system. These apps can use the standard Android hardware attestation API to permit arbitrary operating systems. There's no need for a centralized service wrapping it and putting control over what's allowed in your hands. > Regarding your statement about Volla as a hardware manufacturer. That is a false statement. Volla Systems is an OEM with complex supply chains for its own hardware, in which our designers and engineers are involved, and with its own production capacities for the final production steps. This gives us full access to the source code generated in the supply chain, starting with the Android source tree of the SoC manufacturer. No, it's a correct statement. Your devices are designed and produced for you by an ODM. You do not have the full source code as you claim. You're misrepresenting your level of involvement in designing and producing the devices along with how much access you have. You certainly don't have access to all of the sources for the firmware, let alone the hardware. The source tree of the SoC manufacturer (MediaTek) provided to their partners is not even the full sources for userspace. Vollaficationist quite clearly belongs to someone at Volla who has made very similar posts from his personal accounts on LinkedIn and elsewhere. It's the same writing style and claims coming from the personal accounts elsewhere. How do you explain this account having internal information from Volla and using the same unique writing style and unique claims coming from someone who works for Volla from their personal accounts on other platforms? > Let’s make good products and develop the market for alternatives. You're working towards locking out alternatives including GrapheneOS. We aren't on the same side and trying to mislead people with your inaccurate marketing about both Unified Attestation, your products and many inaccurate claims about GrapheneOS further confirms it. You're posting the same stuff you were via the Vollaficationist account dressed up in a more formal way.

Once again: Please stick to the facts. We are not attacking the Graphene OS team. We are clarifying the intent behind UnifiedAttestation and have invited the Graphene OS team to participate. Vollaficationist is not an account belonging to Volla Systeme or any Volla Systeme employee. It makes no sense to repeat our arguments; instead, let us describe UnifiedAttestation from a different perspective: Today, some apps use Google Play Integrity. These are primarily banking, payment, and digital ID apps. In some countries, citizens rely on these apps because government-issued ID apps, for example, are a prerequisite for opening a bank account. We view this development critically. To be able to offer alternative Android operating systems to all users without limitations, UnifiedAttestation is an open-source, freely available alternative to Google Play Integrity. We see a greater chance of convincing app developers and publishers who currently use Google Play Integrity to adopt an alternative rather than to abandon Google Play Integrity altogether. However, this persuasion will only succeed if app developers and publishers see a relevant market. Hence the consortium. Perhaps we will even succeed in making UnifiedAttestation an open standard. Once again, for clarification: UnifiedAttestation should not be a prerequisite for apps to be installed and used on alternative Android systems—not at all. It concerns a small subset of apps that currently prevents customers from using an alternative Android operating system. Regarding your statement about Volla as a hardware manufacturer. That is a false statement. Volla Systems is an OEM with complex supply chains for its own hardware, in which our designers and engineers are involved, and with its own production capacities for the final production steps. This gives us full access to the source code generated in the supply chain, starting with the Android source tree of the SoC manufacturer. Let’s make good products and develop the market for alternatives.

@Jaoheah Likely.

@GrapheneOS Will it support the 2027 version of the Razr Fold?

@GrapheneOS Will the Motorola Razr Fold support Graphene? Or is it the next gen one? I heard something about Motorola having a Fold version that will support Graphene.

@errkatze @therealfunar @ProtonVPN 6 full time developers, 2 at 75% and 1 at 50%.

@GrapheneOS @therealfunar @ProtonVPN How many developers are you guys currently employing full-time?

1/4 Google has known about a bug that breaks VPN apps for 7 months, leaving users exposed with no warning or error, just a VPN app that stopped working in the background. If you're using ANY VPN on Android, you can help us by getting Google's attention to fix it. Details 👇 🧵

Vanadium version 146.0.7680.153.0 released: github.com/GrapheneOS/Van… See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread: discuss.grapheneos.org/d/33290-vanadi… #GrapheneOS #privacy #security #browser

@therealfunar @ProtonVPN Our priority is fixing leaks rather than an issue causing an annoyance where a reboot might be required to get connectivity again since leak blocking is working properly for it. We have 1 full-time developer mainly working on resolving VPN issues right now. We can't assign more.

@therealfunar @ProtonVPN We already have fixes for 5 holes in Android's VPN leak protection. We're working on identifying all remaining issues and resolving those. The most severe issues are fixed but there are remaining bugs in the Android VPN APIs we need to resolve. It's a lot of work and not easy.

@therealfunar @ProtonVPN Our priority is fixing the leaks rather than an issue causing an annoyance where a reboot might be required to get connectivity again which is successfully blocked by the VPN leak protection. Google has far more resources. It's inherently slow for us to get a dozen bugs fixed.