zlacker

>>tripdo+(OP)
> Without the Pixel hardware repos (which include the device trees, driver binaries, and more), custom Android ROMs will have a hard time developing their OS updates. This might also have implications for security (vulnerability) researchers.

This concerns me as a GrapeneOS user.

>>yellow+o2
Yup, especially given what they posted: https://x.com/GrapheneOS/status/1932596516390072669?t=Tw_clE...

>>codeth+r4
Aw man… GrapheneOS makes owning a smartphone bearable. I hope this isn't the beginning of the end.

>>Freak_+s6
I really haven't kept up with third party roms for smartphones in a while. I take it graphene is a major player? Last one I heard of was lineage os. I guess I probably need to start looking as my pixel 5a has probably lapsed security updates

>>wing-_+0c
while lineageos and derived roms like /e/os are doing a good job supporting old smartphone models and temporarily saving them from thr landfill, they are struggling to support less than 5 year old models that aren't google pixel and fairphones.

The google pixel line were the only smartphone you could buy new on a brick and mortar shop on monday almost anywhere in the world and have it running on a custom rom on tuesday and graphene was leading the way in pushing privacy and security at its maximum while other rom maker are making a lot more concessions.

LineageOS still is king to save old devices but grapheneos definitely is a major player because some people like me did chose second hand google pixel with the sole purpose of being able to run graphene.

Ironically, running a google smartphone was the best way to live a life without sending data and rely on google services.