zlacker

[return to "Google Pixels are no longer the AOSP reference device"]
1. yellow+o2[view] [source] 2025-06-12 17:06:15
>>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.

◧◩
2. codeth+r4[view] [source] 2025-06-12 17:15:06
>>yellow+o2
Yup, especially given what they posted: https://x.com/GrapheneOS/status/1932596516390072669?t=Tw_clE...
◧◩◪
3. Freak_+s6[view] [source] 2025-06-12 17:28:41
>>codeth+r4
Aw man… GrapheneOS makes owning a smartphone bearable. I hope this isn't the beginning of the end.
◧◩◪◨
4. wing-_+0c[view] [source] 2025-06-12 17:59:54
>>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
◧◩◪◨⬒
5. rfoo+ed[view] [source] 2025-06-12 18:06:41
>>wing-_+0c
> graphene is a major player?

No. It is not. Lineage and a lot of others are major players.

They just have different focus. GrapheneOS cares about being secure. Others cares about being, well, custom, and "privacy", "privacy" as in "noooooooooo I don't want to install google stuff jfc", instead of being secure against random threat actors.

[go to top]