AOSP isn't dead, but Google just landed a huge blow to custom ROM developers

It is now available in the new release (still in alpha at the moment) to opt in to use the additional security patches from November and December.

4 Likes

I am really torn about this. Great for security, but GOS proposing those release is going to validate Google delaying open-sourcing critical security patches.

It feels illegal to me. Why is a company allowed to purposely not release patches that will secure millions of AOSP devices?

2 Likes

Men, 2025 is exhausting in terms of privacy. It almost feel coordinated….

7 Likes

It is. All governments hate GOS. Pretty sure nation states (or their intelligence services) have put pressure on Google to make this happen.

2 Likes

I hope not. I hope its just Google being idiotic with its antitrust and being overly protective of its Android ecosystem as it ever so slightly slips out of their control.

2 Likes

I understand why speculation is rampant in this thread, but I am not sure why people believe it has anything to do with custom OS distributions or GrapheneOS. Any harms to those projects seem entirely incidental to them and I doubt they alter their business plans around that. Blog - Divested Computing from SkewedZeppelin provides a nice overview of some of the bad decisions Google are making.

I honestly think the only way to know if custom Android distrubitions are in the scope of their targets is if they remove/disable bootloader unlocking for future Pixel phones. This hasn’t been the case for the Pixel 10 series release, so we’ll see if things change with the Pixel 10a/Pixel 11.

4 Likes