My videos aren't sponsored by anyone but you. Monthly sustainers get access to my Discord/Matrix space, and are what keeps the lights on around here. Thank you for your consideration! https://patre...
Its not up to grapheneos devs which devices support bootloader relocking with different keys, literally only pixels allow this and without it you cant properly secure the phone.
My understanding is that a locked bootloader helps protect against evil maid attacks and bootloader-level malware persistence. I find this a security risk that I would absolutely take for Google independence. “Properly secure” is subjective.
GrapheneOS do decide what phones they support. It is exactly their choice to support only Google Pixels, rather than taking a security hit for hardware independence (whether you agree with the decision or not).
Exactly, seems like this should be up to the consumer. The devs can say: pixels have best security, here’s a 2nd and 3rd option, here’s their pros and cons.
Because as much as I approve of privacy measures and security, my phone doesn’t have any lock screen. No pin, no biometrics, nothing.
I work from home, I don’t really travel, I have 4 children. Physical security is annoying. I want grapheneos for data security. I don’t have people trying to steal my phone, I do have people constantly stealing my data.
And without a non-pixel option (fuck google), I’m likely to go for to a competitor because, while their data security might not be as good as graphene, it is better than what I currently have.
I’ve got the pixel 8 with graphene on it, it’s very nice but I also have a soft spot for emulation and the Tensor devices are trash for anything higher than GameCube tbh
Bring on support for more devices, and I’ll likely switch with my next phone.
Its not up to grapheneos devs which devices support bootloader relocking with different keys, literally only pixels allow this and without it you cant properly secure the phone.
My understanding is that a locked bootloader helps protect against evil maid attacks and bootloader-level malware persistence. I find this a security risk that I would absolutely take for Google independence. “Properly secure” is subjective.
GrapheneOS do decide what phones they support. It is exactly their choice to support only Google Pixels, rather than taking a security hit for hardware independence (whether you agree with the decision or not).
Exactly, seems like this should be up to the consumer. The devs can say: pixels have best security, here’s a 2nd and 3rd option, here’s their pros and cons.
Because as much as I approve of privacy measures and security, my phone doesn’t have any lock screen. No pin, no biometrics, nothing.
I work from home, I don’t really travel, I have 4 children. Physical security is annoying. I want grapheneos for data security. I don’t have people trying to steal my phone, I do have people constantly stealing my data.
And without a non-pixel option (fuck google), I’m likely to go for to a competitor because, while their data security might not be as good as graphene, it is better than what I currently have.
(No OP, but…)
Well, unfortunately, we’re at an impasse, then. :(
They’re working on an alternative device with a large OEM they’ve not disclosed yet. They’re aiming at releasing it in 2027.
The smart money is they’re going to go with Motorola, honestly idc who they go with it’ll likely be my next phone
Same here, i can’t wait to ditch my old xiaomi 10 full of bloatwares and ads
I’ve got the pixel 8 with graphene on it, it’s very nice but I also have a soft spot for emulation and the Tensor devices are trash for anything higher than GameCube tbh
If you don’t wanna use a pixel, just build it. It’s open source ¯_(ツ)_/¯