zlacker

[parent] [thread] 4 comments
1. surgic+(OP)[view] [source] 2025-03-26 21:01:30
I am curious how it would affect projects such as GrapheneOS or LineageOS.

Hopefully they can still function like this

replies(2): >>bornto+hn >>charci+dB
2. bornto+hn[view] [source] 2025-03-26 23:28:38
>>surgic+(OP)
It sounds to me like Graphene will have a large gap of access to fixes compared to the special vendors.. I wont be upgrading to a newer Pixel until I see a year or two of this working out and I think that is less likely than a descent.
3. charci+dB[view] [source] 2025-03-27 01:41:17
>>surgic+(OP)
I doubt it effects them. Those operating systems are based off Android 15. I don't think either of them were trying to backport Android 16 code into their OS.
replies(2): >>nvllsv+EX >>jadbox+uc5
◧◩
4. nvllsv+EX[view] [source] [discussion] 2025-03-27 06:42:37
>>charci+dB
The 2025032500 release of GrapheneOS contains a backported fix from Android 16. https://grapheneos.org/releases#2025032500
◧◩
5. jadbox+uc5[view] [source] [discussion] 2025-03-28 16:25:04
>>charci+dB
+1 I don't think it effects them as they usually only pick up releases after they are published, which is when Google will release the source now anyways.
[go to top]