Btw
It would be better to prove that it is secure.
If you think about last year, for example (That applies to Qualcomm, so you’d have to check what hardware is installed. ) —CVE-2026-25262(But it’s only now making headlines)—the question remains: what hasn’t been discovered yet?
The focus is still on what has been discovered; the question remains: what has not yet been discovered?
And you still need firmware you can trust. You can’t trust Qualcomm.
Are you implying that they put the vulnerability there? What is even your point? As far as I know they were the first ones to have a fix for that issue but apparently that means that they’re inherently insecure. Like seriously, do you even have any idea what you’re talking about???
I mean… GrapheneOS is here to do exactly the opposite of that. Lol. I mean… Fuck Yoti but like ¯\(ツ)/¯
Btw It would be better to prove that it is secure. If you think about last year, for example (That applies to Qualcomm, so you’d have to check what hardware is installed. ) —CVE-2026-25262(But it’s only now making headlines)—the question remains: what hasn’t been discovered yet?
Oh look, grapheneOS was vulnerable… but it’s been fixed now https://discuss.grapheneos.org/d/35355-details-on-the-may-2026-android-security-bulletin (not same CVE)
https://forum.torproject.org/t/enabling-grapheneos-protections-causes-tor-browser-for-android-to-break/21535 lol
The focus is still on what has been discovered; the question remains: what has not yet been discovered? And you still need firmware you can trust. You can’t trust Qualcomm.
Dont forget the whole infrastructure. https://youtu.be/fM5w7bFNvWI
Are you implying that they put the vulnerability there? What is even your point? As far as I know they were the first ones to have a fix for that issue but apparently that means that they’re inherently insecure. Like seriously, do you even have any idea what you’re talking about???
GrapheneOS: Our Daily Honeypot. You can’t trust any cell phone. The operating system doesn’t matter. 🤣