Devices lacking standard privacy/security patches and protections aren't private

GrapheneOS Discussion Forum

Devices lacking standard privacy/security patches and protections aren't private - GrapheneOS Discussion Forum

GrapheneOS discussion forum

ANDROID 16 BUILDS OF #GrapheneOS ARE NOW IN STABLE!

Releases | GrapheneOS

Robert Braxman has published another video spreading blatant misinformation about #GrapheneOS in order to promote his highly insecure products and services. In addition to many false technical claims and fabrications about our team, he's falsely claiming the project is dying. We have a thread already debunking this recent line of attack on GrapheneOS at: https://xcancel.com/GrapheneOS/status/1936420921931084075 GrapheneOS quickly provided the June security patches, was ported to Android 16 and is working with a major Android OEM. It's not dying and we haven't said or implied it is. Braxman presents himself as a privacy and security expert but isn't one. He's a shady businessman selling unsafe snake oil products and services. His content is filled with outright fabrications and is heavily aimed at promoting his products. It misinforms rather than educating.

#GrapheneOS version 2025070700 released (a few hours ago, it's in Beta now) - raise security patch level to 2025-07-05 since it's already provided without applying any additional patches - only permit third party apps to use custom activity animations for transitions between their own activities to prevent a recently disclosed Android tapjacking vulnerability branded as TapTrap (not patched upstream yet) - Pixel 8, Pixel 8 Pro, Pixel 8a: fix regression breaking DisplayPort alternate mode in the previous release - Sandboxed Google Play compatibility layer: fix phenotype flag overrides not working on production builds which regressed quite a while ago and limited our ability to fix certain compatibility issues via quick GmsCompatConfig updates

Releases | GrapheneOS