zlacker

Ah so I guess this is the reason that GrapheneOS just works on Pixels? Maybe after the initial hurdle this change has introduced will actually lead to a wider device support once the necessary changes are better understood. Let's hope.

edit: missed a word

>>shrx+(OP)
Or it leads to GrapheneOS not supporting any new devices.

>>shrx+(OP)
In part. The stated reasons[1] are: (1) best hardware security features, such as memory tagging (2) quick patches (3) many years of official device support.

[1]: https://grapheneos.org/faq#future-devices

>>shrx+(OP)
Back in the day I was maintainer of a CyanogenMod device. Back then you could pull the device trees and basebands and proprietary parts off the OTAs and phones directly after rooting them. Has that changed? LineageOS still exists. I haven't been in that scene for... over a decade but is Lineage freaking out to this extent? Yes, it takes effort to maintain a port and it's not as easy, but how much of GrapheneOS is actually implemented in the kernel vs post-init things (which are easy to modify).