I don’t see how GrapheneOS and Qubes are even in the same class of OS’s. If someone would add a community template running GrapheneOS, yes I would use it. I have been looking for a usable Android AppVM but have so far not been able to get any variant running properly thus far. GrapheneOS would be my go-to choice during to the security centered choices made in that OS. The problem is the supported hardware required for it is extreemly narrow and the likelyhood of standing up an x86 derivative is pretty slim. Running it under emulation in Xen isn’t going to be easy.
Could it supplant Qubes? Not even close. Could it be used under Qubes? Doable, but who is going to cross compile it and build the Qubes utilities needed to make it useful?
I would love to see this but it likely won’t happen in my lifetime.
I use both GrapheneOS, on two phones and a tablet, and QubesOS on a Protectli Vault. I wouldn’t say there’s a huge difference in difficulty setting up either to work.
Installation on both was fairly straight forward, both require specific hardware but work simply if you have it. Both I’ve had issues with some programs and had to make sacrifices to get them to work how I need.
It’s not really a choice for me between the two OS’s as both serve their purposes for the job I use them for.
Graphene OS is just another free Android.
Tried all kinds of Mobile OS’s and on none of them it is possible to activate essential applications for eID and payment without a Google account or Apple ID, not in my country that is.
So i stopped using smartphones totally and returned to a classical GSM (2G)
And for the time the 2G GSM network will be fased out (2028 in my country) i already bought a LTE version that can work on 4G
I’ll only use a smartphone again when the essential payment and eID apps are available for GNU/Linux mobile and can be activated whithout a Google-account or Apple-ID
The “All Around Qubes” category is discussions not directly pertaining to Qubes OS. As for whether it should be public or not, that is decided by the Qubes OS forum team.
I’m less than expert on the topic of smartphones. However, I sense that having a secure OS running on a device designed to steal your information is counterintuitive. Both Apple and Google have been caught red handed “accidentally” gathering location data. That’s just the tip of the iceberg.
My sense is that there is no way to secure a smartphone. Not because the OS is insecure, but because the very platform is insecure. There is no way to secure a device designed to track all of your movements while bringing cameras and microphones everywhere you go, while dumping everything by default to the cloud scanned under government duress.
When I think of a smart phone, I see a [CoC breach]. GrapheneOS is the smile of a [CoC breach].
When I think of a smart phone, I see a [CoC breach]. GrapheneOS is the smile of a [CoC breach].
Wow, that’s a strong statement
However, GrapheneOS and QubesOS both have to run on devices which are not secure by design. You can libreboot and disable ME as much as you want, but to my knowledge it doesn’t make hardware 100% secure and trusted anyway.
This is about privacy. Security-wise even stock Google’s Android is quite impressive. But Qubes doesn’t position itself as a privacy-oriented OS either.
As for the OP’s question, I would say that both solutions are imperfect, but they are the best options we currently have. And they have different usage scenarios.
But if I had a wallet with 1k bitcoins, I would probably choose to keep it on… an iPhone?
I do love DivestOS, but lately it struggles to keep up the pace, probably because Ted (Tavi) tries to solo-carry everything, maybe he is burned-out. But it is still Android 13, at best, and no new features implemented for a very long time. All OS’s news are about patches and some translations.
It is still the only decent option if you can’t have a Pixel, but you can’t really compare it with GrapheneOS, with the latest Android and a ton of new improvements.
It has hardware kill switches to cut power from the cellular modem, Wi-Fi/Bluetooth module, and/or camera + microphone. When all three hardware kill switches are toggled down, it enters Lockdown Mode, which disables all other sensors:
A few notable details include the operating system being PureOS (a FSF-endorsed Linux distribution), anti-interdiction services optional, and replaceable components, among others.