Our initial port to Android 16 has been completed and can be built for the emulator from our 16 branch. All of the device-independent GrapheneOS code has been ported. There are some parts of the port which will be redone better and a lot of testing and fixing regressions to do.

We're going to be moving forward under the expectation that future Pixel devices may not meet the requirements to run GrapheneOS (

Frequently Asked Questions | GrapheneOS

and may not support using another OS. We've been in talks with a couple OEMs about making devices and what it would cost.

In May, we began preparing to port to Android 16 despite our most active senior developer responsible for leading OS development being unavailable (

Mastodon hosted on grapheneos.social

GrapheneOS Mastodon

GrapheneOS server for official project accounts and project members.

Android 16 launched today and porting is going to be significantly more difficult than we were expecting.

Vanadium version 137.0.7151.72.1 released:

GitHub

Release 137.0.7151.72.1 · GrapheneOS/Vanadium

Changes in version 137.0.7151.72.1: enable Local Network Access checks by default (this was already shipped in Vanadium Config 95 so it doesn't ch...

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:

GrapheneOS Discussion Forum

Vanadium version 137.0.7151.72.1 released - GrapheneOS Discussion Forum

GrapheneOS discussion forum

#GrapheneOS #privacy #security #browser

A growing number of apps are using the Play Integrity API to enforce installation from the Play Store. This is clearly highly illegal anti-competitive behavior. It doesn't impact GrapheneOS users installing apps with the sandboxed Play Store but does impact other install sources.

We still need help getting early access to Android 16 sources prior to the stable release in June. Every mainstream Android OEM has it. We're currently spending significant time on reverse engineering Android 16 Beta releases. It's a huge waste compared to having what we need.

We need an Android OEM or someone working at one to provide us with early access to the Android 16 sources in order to have a smooth port this year. We need this before June. We requested it to help with this very difficult situation (see the linked thread) and still need it.

GrapheneOS Mastodon

GrapheneOS (@GrapheneOS@grapheneos.social)

One of our two senior developers has been forcibly detained and conscripted to participate in a war. When they first went missing, we revoked their...

GrapheneOS version 2025050500 released:

Releases | GrapheneOS

See the linked release notes for a summary of the improvements over the previous release. Forum discussion thread:

GrapheneOS Discussion Forum

GrapheneOS version 2025050500 released - GrapheneOS Discussion Forum

GrapheneOS discussion forum

#GrapheneOS #privacy #security

In anticipation of Let's Encrypt dropping Must-Staple support on May 7th and OCSP 3 months later, our services previously using OCSP stapling and Must-Staple have been moved to the Let's Encrypt `tlsserver` profile made publicly usable a couple weeks ago.

Let's Encrypt Community Support

Removing OCSP URLs from Certificates

Let’s Encrypt will be removing OCSP URLs from certificates on May 7, 2025 as part of our plan to drop OCSP support and instead support certificat...

We're in the process deploying a major upgrade to the GrapheneOS server infrastructure to provide faster connections to our services and higher robustness. If you notice any new issues connecting to our services, please report them in our Infrastructure chat room (grapheneos.org/contact#community-chat).