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. Freak_+Id[view] [source] 2025-06-12 18:08:23
>>wing-_+0c
A major player amongst the tiny world of user-centric privacy-focussed third party Android based OSes I guess. Their major selling point — aside from privacy and maximal degoogling — is that you could take a Pixel, install GrapheneOS, and have it work with not too much trouble. No elaborate study of a plethora of devices needed, and the device is supported for a comparatively long time.

The Pixel 6 I have will be hitting its end of life in October 2026. I had wished to be able to simply get a newer Pixel and just carry on.

[go to top]