ps: Have no doubt, every claim Google makes about restricting stuff for your own good is just them lying out of their asses.
So I guess more free open source projects won’t be able to be maintained by overworked volunteers, and they’ll get “rescued” by trillion-dollar corporations that will close-source everything, backdoor the shit out of it, and decide what you can and cannot have.
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.
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.
They dont acturally need to change the liscense at all, despite what most people think (and would logically make sense) AOSP is acturally downstream from Android. So basically as we’re seeing right now if Android doesn’t want to release the source code for something they just need to not push it to AOSP. It has been over two months already and Android 16 QPR1 still hadn’t been upstreamed to AOSP nor are they legally required to (they are legally required to publish kernel sources which they have failed to do).
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.
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
?
I must know as much as I thought.
I thought they owned Android. Is that not true?
https://www.androidauthority.com/google-android-development-aosp-3538503/
https://www.androidauthority.com/google-sideloading-android-developer-verification-rules-3602811/
ps: Have no doubt, every claim Google makes about restricting stuff for your own good is just them lying out of their asses.
So I guess more free open source projects won’t be able to be maintained by overworked volunteers, and they’ll get “rescued” by trillion-dollar corporations that will close-source everything, backdoor the shit out of it, and decide what you can and cannot have.
They do, but Android is open source, and now Google is trying to close it down.
How? Are they retroactively changing the license?
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.
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.
They dont acturally need to change the liscense at all, despite what most people think (and would logically make sense) AOSP is acturally downstream from Android. So basically as we’re seeing right now if Android doesn’t want to release the source code for something they just need to not push it to AOSP. It has been over two months already and Android 16 QPR1 still hadn’t been upstreamed to AOSP nor are they legally required to (they are legally required to publish kernel sources which they have failed to do).
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.
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/
Nope. Android phones without google are a thing. Its the default when you install the OS yourself, actually