GrapheneOS

Open source privacy and security focused mobile OS with Android app compatibility.

https://grapheneos.social/@GrapheneOS

Last Notes

2026-05-29 14:29:03 GMT

Vanadium version 149.0.7827.48.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/149.0.7827.48.0
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:
https://discuss.grapheneos.org/d/35921-vanadium-version-14907827480-released
#GrapheneOS #privacy #security #browser
🔗 https://grapheneos.social/@GrapheneOS/116658336122519015

2026-05-28 08:57:36 GMT

- reply

@Bebef The primary purpose of the API is to ban using an operating system not certified by Google to hinder competition with Google's apps and services. Google has convinced app developers to use it by marketing ti as a security protection. The result is supposed to be fetched and checked by a service enforcing obtaining a result with the properties they want to enforce. Some of the apps using it haven't correctly implemented it and it can be bypassed by simply blocking it since they fail open.
🔗 https://grapheneos.social/@GrapheneOS/116651370528991741

2026-05-27 18:48:32 GMT

- reply

@abon999 @aeris That could be what's wrong, although several other people are reporting it works for them without saying they needed the per-app exploit protection compatibility mode. One possibility is that @aeris opted into additional protections for user installed apps which aren't enabled by default and it might be incompatible with one of those, but those features show notices in nearly all cases where the app does something incompatible so that probably isn't the issue.
https://framapiaf.org/@abon999
https://firefish.imirhil.fr/@aeris
🔗 https://grapheneos.social/@GrapheneOS/116648031821508069

2026-05-27 18:45:12 GMT

- reply

@aeris Please provide the following info:
1) Confirm the device is locked as expected
2) Device model
3) GrapheneOS version from Settings > About > Build number
4) Version code of the app shown at the bottom of Settings > Apps > App name
5) Does GrapheneOS show a notice about it using the Play Integrity API? If it doesn't then the app isn't using it so that's not the issue.
Try the per-app exploit protection compatibility mode to see if it's a memory corruption bug or similar issue in the app.
https://firefish.imirhil.fr/@aeris
🔗 https://grapheneos.social/@GrapheneOS/116648018719191297

2026-05-26 03:17:52 GMT

- reply

@freya It's a different type of software and is meant to become a competitive alternative to Google Speech Recognition & Synthesis. It has a lot of room for improvement including simply not reading newlines which can waste a lot of time if the text being passed to it doesn't have the whitespace stripped down.
It doesn't use hardware acceleration yet and was trained on a AMD RX 6600 prior to obtaining an RTX 5090. It can't be expected to keep up with Google's yet but it will get better.
https://social.highenergymagic.net/@freya
🔗 https://grapheneos.social/@GrapheneOS/116638710007575375

2026-05-26 03:03:16 GMT

- reply

@freya No, performance was a major focus for it. It already has much lower latency than the existing options we were comparing against and there's huge room for improvement. It's the first public experimental release of the software and it has quirks to resolve including treating newlines as significant where reading newlines takes time and creates a barely audible sound. It doesn't use any form of hardware acceleration yet either. You're expecting too much from the first experimental release.
https://social.highenergymagic.net/@freya
🔗 https://grapheneos.social/@GrapheneOS/116638652587438363

2026-05-25 18:00:36 GMT

- reply

@gilbus You can install it from our App Store on older GrapheneOS releases or outside GrapheneOS too so you can already try it. See https://discuss.grapheneos.org/d/35722-initial-release-of-grapheneos-speech-services-for-text-to-speech/ for more info.
https://metalhead.club/@gilbus
🔗 https://grapheneos.social/@GrapheneOS/116636518735461535

2026-05-25 16:05:17 GMT

GrapheneOS version 2026052400 released:
https://grapheneos.org/releases#2026052400
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
https://discuss.grapheneos.org/d/35816-grapheneos-version-2026052400-released
#GrapheneOS #privacy #security
🔗 https://grapheneos.social/@GrapheneOS/116636065331233648

2026-05-24 05:12:25 GMT

- reply

@fishitherat Having 2 browser engines instead of 1 would massively increase the work required and heavily reduce security even if the 2nd browser engine had similar security. Adding a massive amount of attack surface and wasting huge amounts of our resources would make little sense.
Firefox is drastically less secure so it's definitely not a good starting point. It's trivial to make the privacy of Chromium far better than Firefox compared to closing even a tiny bit of the gap for security.
https://mastodon.social/@fishitherat
🔗 https://grapheneos.social/@GrapheneOS/116627835836810501

2026-05-24 05:10:43 GMT

- reply

@fishitherat Any replacement for the WebView needs very complete parity with the feature set and behavior it has to a far greater extent than a standalone browser. Most Chromium features work in the WebView with some exceptions. Firefox is nowhere close to being usable as a system WebView implementation for Android in terms of functionality. It's increasingly far behind what would be required.
Using Firefox as a base for a default browser would mean having 2 browser engines instead of 1.
https://mastodon.social/@fishitherat
🔗 https://grapheneos.social/@GrapheneOS/116627829121001745

2026-05-24 05:09:21 GMT

- reply

@fishitherat Aside from all of that, Vanadium isn't only the default browser on GrapheneOS. It's also the WebView implementation used by apps to handle web technologies far beyond providing an embedded browser. As an example. email clients will typically use it to render HTML emails in the default JavaScript disabled mode. It can be used in many different ways, not just as an embedded browser. Entire apps are written to run in the WebView to write them with web technologies.
https://mastodon.social/@fishitherat
🔗 https://grapheneos.social/@GrapheneOS/116627823771604129

2026-05-24 05:07:17 GMT

- reply

@fishitherat Firefox has atrocious security compared to Chromium. It's also missing a lot of what's needed and Firefox would not be a viable choice as a default browser due to how much is missing. It can't even run the GrapheneOS web installer due to not having WebUSB despite adding multiple of the features in the same family. It's missing due to marketing-focused differentiation from Chromium without substance and reduces security for Firefox users who need to run native applications instead.
https://mastodon.social/@fishitherat
🔗 https://grapheneos.social/@GrapheneOS/116627815622433530

2026-05-24 05:05:10 GMT

- reply

@fishitherat Firefox is several to many years behind in many important aspects of security. They have drastically lower resources invested in security. Firefox still doesn't even isolate sites with an OS level sandbox on Android which is a complete joke in 2026. Meanwhile, Chromium has built another layer of sandboxing for JavaScript in V8 with no sign of that coming to Firefox even years from now along with having lots of other hardening features not present in any form in Firefox.
https://mastodon.social/@fishitherat
🔗 https://grapheneos.social/@GrapheneOS/116627807296637331

2026-05-23 17:26:49 GMT

- reply

@wod0bow @nileane @macgeneration Canada's Bill C-22 has a carveout for security mechanisms protecting data from attacks including end-to-end encryption. You should read the relevant text for yourself.
Warrants for requesting data and metadata clearly already existed so that's not what the law isn't creating that as a new thing.
There might be a future law trying to subvert end-to-end encryption but Bill C-22 isn't doing that yet. It's not a Canadian form of Chat Control at all.
https://mastodon.social/@wod0bow
https://nileane.fr/@nileane
https://social.macg.co/@macgeneration
🔗 https://grapheneos.social/@GrapheneOS/116625061253805941

2026-05-23 15:22:22 GMT

- reply

@GrantJoseph No, all of the supported Pixels are Tensor rather than Snapdragon. It's possible to lock down EDL and other low-level Qualcomm SoC functionality via efuses and it's likely not all devices were vulnerable to this despite how the article is written. We don't know whether Snapdragon Pixels were vulnerable but they've been end-of-life for years and GrapheneOS hasn't had any official support for them for a long time. Pixel 5a was the last supported and was end-of-life after August 2024.
https://mastodon.social/@GrantJoseph
🔗 https://grapheneos.social/@GrapheneOS/116624571905840823

2026-05-22 05:34:54 GMT

- reply

@MoneroChanLovesYou Did you enable the Phone permission for Play services?
https://mastodon.social/@MoneroChanLovesYou
🔗 https://grapheneos.social/@GrapheneOS/116616599572933583

2026-05-21 02:51:15 GMT

- reply

@libreovergratis Hallucinated AI slop...
https://mastodon.social/@libreovergratis
🔗 https://grapheneos.social/@GrapheneOS/116610293810572117

2026-05-20 20:57:16 GMT

- reply

@pvagner GrapheneOS has built-in support for call recording in the system dialer app which we built ourselves. We're in the process of adding an implementation of automatic call recording as an extension to it.
🔗 https://grapheneos.social/@GrapheneOS/116608901899515861