Oddbean new post about login | logout In the past I used cyanogenmod , nostr:nprofile1qqstnr0dfn4w5grepk7t8sc5qp5jqzwnf3lejf7zs6p44xdhfqd9cgspzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcnv0md0 does #GrapheneOS team plan to extend support to other cheap devices? What the problem extend support to other devices? The hardware is so different or unsupported or have closed source driver?
IIRC, GrapheneOS doesn't support other phones because it's not possible to lock the bootloader after installation.
you told me i can install GrapheneOS on all devices where I can unlock the bootloader? 🤨
No. I believe they support Pixels because the bootloader can be locked after install.
I can't understand what you mean with lock Bootloader after installing GrapheneOS. I need to unlock before installing, not lock after.
Locking it after installation keeps your phone secure. If it remains unlocked, then I can get a lot of items off your phone if income into possession of it. It's a security issue. GrapheneOS prioritizes security over privacy more so than other Android builds.
They need to meet the security requirements on here: https://grapheneos.org/faq#future-devices If they don't then we aren't interested in supporting it. Users will just paint flaws caused by less secure devices to be a GrapheneOS problem. Some are just totally incompetent, for example, Fairphone 4 set ther verified boot keys as publicly available test keys, meaning anyone can just sign an update with those same keys. Samsung kills certain device features via an eFuse when the non-stock OS is installed.