Oddbean new post about login | logout I don’t know. All I’m saying is that relying on a single OS that only runs on a single device that is manufactured by Google doesn’t exactly sound like the guarantee of privacy that Graphene users suggest it is. Maybe it’s safer that other setups from some prying eyes, but seems pretty obvious that the device shouldn’t be trusted as much as most Graphene users seem to trust it.
*than
I agree, and I am one of those users. Every time I turn on my phone and see the Google logo before the Graphene logo, I cringe a little bit 😂
Is that before or after you get that nasty orange warning? 😂
BEWARE YOUR PHONE IS LOADING A DIFFERENT OS
Many other devices are supported by GrapheneOS at a source level, and it can be built for them without modifications. Building specifically for Pixels is afaik just a manpower thing
Being technically supported at the source level is still effectively useless though for most end users.
it can only be used with a pixel because it’s the only device that will allow you to install a custom os and relock the bootloader. Here’s the thing though, a thief could steal your device, unlock it again, which wipes everything, and now your device is theirs. This is possible because the ORM unlock toggle is still turned on. Now, you could turn it off, but if graphene screws up an update, you’re pretty much screwed and can’t even return to stock because you can’t turn that switch back on without the device being bootable. It’s a catch 22. Turn it off and you risk ending up with a brick or keep it on and risk someone coming along and showing you how unsecured your device really is.