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???
People trust the GrapheneOS devs blindly… As if the devs had found the Holy Grail… There have already been several security vulnerabilities… For some, they can actively do something; for others, they’re dependent on the hardware manufacturers… (The fact that they only support Qualcomm besides Pixel also leaves a bad taste in the mouth)… So in the end, you still have to trust the hardware and the entire infrastructure (cellular networks, etc.), and you simply can’t trust any of it…
Instead of treating phones as untrustworthy, grapheneOS users blindly trust the devices 100%, which is fatal. That’s why I call it a honeypot… Ultimately, you can’t trust ANY phone, no matter what OS is installed… That would require at least open hardware.
It’s not like I haven’t already mentioned a few things, along with sources. Oh, come on, just stay in your bubble…
Plus, you’re ignoring what security researchers, hackers, and others have always been saying: that there’s no such thing as 100% protection…
Come on, prove that it’s 100% secure—I’m waiting… Oh, wait, you can’t prove that because it’s impossible…
For that to be true, it would have to be a completely isolated OS… Without cellular connectivity, usb, etc.
I’m having fun trying to get the modem out of the SoC… Ohhh
You just can’t trust these devices 100%. But you do it anyway, because you know better, of course.
By the way, just using this OS is already causing problems with Yoti, but I’m sure you’d deny that too. 😏
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???
CVE-2026-25262 they cant fix qualcomms Firmware… Qualcomm could but well…
You are correct I believe. My understanding was that graphene blocked an api or something like that to address the vulnerability…?
There are various CVEs… They can fix Qualcomm’s firmware… Just as they can’t say exactly what’s going on there…
Okay I’m just gonna say it. So what?
People trust the GrapheneOS devs blindly… As if the devs had found the Holy Grail… There have already been several security vulnerabilities… For some, they can actively do something; for others, they’re dependent on the hardware manufacturers… (The fact that they only support Qualcomm besides Pixel also leaves a bad taste in the mouth)… So in the end, you still have to trust the hardware and the entire infrastructure (cellular networks, etc.), and you simply can’t trust any of it… Instead of treating phones as untrustworthy, grapheneOS users blindly trust the devices 100%, which is fatal. That’s why I call it a honeypot… Ultimately, you can’t trust ANY phone, no matter what OS is installed… That would require at least open hardware.
GrapheneOS is great but the users are well…
And you have anything other vibes? No. No you do not.
Or are you gonna pull the old “do your own research line” cause you think it makes you sound smart?
It’s not like I haven’t already mentioned a few things, along with sources. Oh, come on, just stay in your bubble…
Plus, you’re ignoring what security researchers, hackers, and others have always been saying: that there’s no such thing as 100% protection… Come on, prove that it’s 100% secure—I’m waiting… Oh, wait, you can’t prove that because it’s impossible…
For that to be true, it would have to be a completely isolated OS… Without cellular connectivity, usb, etc. I’m having fun trying to get the modem out of the SoC… Ohhh
You just can’t trust these devices 100%. But you do it anyway, because you know better, of course.
By the way, just using this OS is already causing problems with Yoti, but I’m sure you’d deny that too. 😏
I see what you’re saying. I’m partial to Graphene but I am picking up what you’re putting down.