We need to do a large number of generate-prep and development builds as part of finishing up our new approach and automation for Pixel device support. Can anyone get us cloud computing credits? Otherwise, we need to start paying for multiple new Hetzner dedicated servers.

We'll be making at least one more Android 15 QPR2 release soon to ship backports of important firmware and driver security patches released with Android 16. This wouldn't usually be required since we'd have Android 16 released to end users using the Alpha channel and soon Beta.

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

WebRTC is a peer-to-peer communications protocol for web sites and therefore causes numerous privacy issues through making direct connections between participants. By default our Vanadium browser disables the peer-to-peer aspect by only using server-based (proxied) connections.

GrapheneOS version 2025052800 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 2025052800 released - GrapheneOS Discussion Forum

GrapheneOS discussion forum

#GrapheneOS #privacy #security