Post #1140724
2026-03-27 09:52 UTC
I do use a (modded) version of graphene as a daily driver and I do appreciate many of the features that it offer.
And I totally agree that some people seem to try to turn graphene into some rigid cult (especially on the philosophy of running root and "who decides how application backup should be made? The application developer or the device/data owner")
That said:
> the idea that the only way I can not get assraped on the reg is to give a shitload of money to google and then use this elitist OS is something I have a gigantic problem with.
There is actually a technical reason for this. Pixel phones are the only ones to support [custom AvB keys](https://github.com/chenxiaolong/avbroot).
Basically, this allows you (or graphene) to create a key, which can be used to _sign your custom firmware_. So, you can have a locked bootloader that will only allow OS updates signed with your key.
You can basically create your own OTA updates. It's fantastic.
It's amazing and disappointing that most phone manufacturers don't allow custom AvB keys, but it's a reflection of how they truly don't care about people who like to tinker.
Now, should the lack of custom AvB keys be a barrier towards using graphene? Tbh, I don't think so - but it does fit the graphene rigid MO of "root is bad".
_edit_ : fixed link
Replies (1)
-
@WhyJiffie@sh.itjust.works 2026-03-30 00:55
> There is actually a technical reason for this. Pixel phones are the only ones to support [custom AvB keys](https://github.com/chenxiaolong/avbroot). that's not true. Fairphones and certain Motorolas have supported that for years. check the calyxos device support page. all of them supports it.