They’ve been moving more and more out of AOSP into their Play Services for a good while now. However I suspect OP was referring to their announcement that they’ll require developer verification, and apps to be signed with a certificate they issue, for any app install on a verified device (read any device sold with the Play Store). Long story short, no more building and distributing APKs without Google knowing who you are and that your app exists.
There is also the fact that Google used to have a public git with the beta source code of upcoming Android releases, but have recently stopped publishing that source code
Not all at once, but I feel like since the beginning more and more stuff has moved to closed source components like the Google services framework. Even the launcher used to be open source and that’s not maintained now in favor of closed OEM (including Pixel) ones.
slowing down AOSP releases (why Graphene is looking into other phone options). Google is also trying to enforce developer signatures on apps, which would give google the power to kill small developers on 3rd party app stores and ruin sideloading, as you would have to go through google to be verified to make apks.
these are a few example that has popped up in the past year.
I don’t think so but it seems you two are mixing Android and AOSP.
Android is owned by Google. AOSP is not.
I might be wrong on this but it seems to me they’re replacing in Android, the OS shipped with many smartphones, parts that have open licenses, i.e. parts from AOSP. Like they are replacing open parts of code with privative parts of code.
They do, but Android is open source, and now Google is trying to close it down.
How? Are they retroactively changing the license?
They’ve been moving more and more out of AOSP into their Play Services for a good while now. However I suspect OP was referring to their announcement that they’ll require developer verification, and apps to be signed with a certificate they issue, for any app install on a verified device (read any device sold with the Play Store). Long story short, no more building and distributing APKs without Google knowing who you are and that your app exists.
https://android-developers.googleblog.com/2025/08/elevating-android-security.html
There is also the fact that Google used to have a public git with the beta source code of upcoming Android releases, but have recently stopped publishing that source code
https://www.androidauthority.com/google-android-development-aosp-3538503/
Not all at once, but I feel like since the beginning more and more stuff has moved to closed source components like the Google services framework. Even the launcher used to be open source and that’s not maintained now in favor of closed OEM (including Pixel) ones.
slowing down AOSP releases (why Graphene is looking into other phone options). Google is also trying to enforce developer signatures on apps, which would give google the power to kill small developers on 3rd party app stores and ruin sideloading, as you would have to go through google to be verified to make apks.
these are a few example that has popped up in the past year.
I don’t think so but it seems you two are mixing Android and AOSP.
Android is owned by Google. AOSP is not.
I might be wrong on this but it seems to me they’re replacing in Android, the OS shipped with many smartphones, parts that have open licenses, i.e. parts from AOSP. Like they are replacing open parts of code with privative parts of code.