The source code is still fully available (and even searchable with code references) which is why all of these community and FOSS forks are still possible.
Google is absolutely abusing their influence over the Android brand to continually lock down consumer devices and the versions of Android that ship on them, but AOSP has only gotten more open-source friendly over time if anything. The problem is there are fewer and fewer devices that will actually let you leave branded Android™ for some version of AOSP.
Only on that platform. The Android™ platform is way more popular than AOSP, but that doesn’t mean Android™ precludes AOSP.
For the purposes of making a custom Android-based OS like GrapheneOS, AOSP is better than ever. Whether or not there are actually devices to install GrapheneOS on kind of isn’t the point here in my mind since we’re talking about which one someone prefers, which means they’re already able to use both.
And as GrapheneOS’ existence demonstrates, it’s still pretty easy and even increasingly mainstream now to change your device’s firmware. GrapheneOS currently is only built for Pixel devices, made by Google, the company that also develops AOSP and owns the Android brand. In theory Lenovo is going to have a Motorola branded device running GrapheneOS officially in the near future, but Lenovo doesn’t have a great track record with mobile software support.
Android™ itself might be getting more locked down and centered around Google’s services, but it’s still an option to move to something else based on AOSP, and thanks to things like Project Treble (which is enforced by Google Play’s compatibility tests), you might not even need device-specific firmware to have a usable and pleasant non-proprietary experience.
The situation with Android is weird, because Google technically owns all of it, but it’s completely different departments going completely different directions, and it doesn’t help that we all call the entire concept Android when that’s technically the brand for Google’s special certified versions of AOSP (which also includes the word Android but not as a brand…).
The source code is still fully available (and even searchable with code references) which is why all of these community and FOSS forks are still possible.
Google is absolutely abusing their influence over the Android brand to continually lock down consumer devices and the versions of Android that ship on them, but AOSP has only gotten more open-source friendly over time if anything. The problem is there are fewer and fewer devices that will actually let you leave branded Android™ for some version of AOSP.
Ok, so basically what you are saying is Android is “Open” in name only and that in practice it is functionally not open.
No the software is open, it’s the hardware you run it on that’s locked down to the manufacturers own specific fork.
No, they are explaining that “Android” effectively refers to two different things.
And one of those things, in practice, makes it harder for users to take advantage of the openness of the other.
Only on that platform. The Android™ platform is way more popular than AOSP, but that doesn’t mean Android™ precludes AOSP.
For the purposes of making a custom Android-based OS like GrapheneOS, AOSP is better than ever. Whether or not there are actually devices to install GrapheneOS on kind of isn’t the point here in my mind since we’re talking about which one someone prefers, which means they’re already able to use both.
And as GrapheneOS’ existence demonstrates, it’s still pretty easy and even increasingly mainstream now to change your device’s firmware. GrapheneOS currently is only built for Pixel devices, made by Google, the company that also develops AOSP and owns the Android brand. In theory Lenovo is going to have a Motorola branded device running GrapheneOS officially in the near future, but Lenovo doesn’t have a great track record with mobile software support.
Android™ itself might be getting more locked down and centered around Google’s services, but it’s still an option to move to something else based on AOSP, and thanks to things like Project Treble (which is enforced by Google Play’s compatibility tests), you might not even need device-specific firmware to have a usable and pleasant non-proprietary experience.
The situation with Android is weird, because Google technically owns all of it, but it’s completely different departments going completely different directions, and it doesn’t help that we all call the entire concept Android when that’s technically the brand for Google’s special certified versions of AOSP (which also includes the word Android but not as a brand…).