Custom ROMs, such as CalyxOS, are based on AOSP. Per their own website(which lambasts Google and highlights Samsung for some reason):
“Android Open Source Project (AOSP) is the core backbone for all Android phones that manufacturers such as Samsung build upon. Maintained by Google, AOSP receives contributions from developers around the world.”
By using a Custom ROM, and from developers contributing to the AOSP, they are supporting Google, agreeing to Google, and helping Google further their ends. Yes, your experience may differ from stockdroid, but if you think you are away from Google, Calyx admits in that one line that despite their platitudes, they are still beholden to Google. If Google restricts access to AOSP, which they can as they are who grants access in the first place, congrats, it becomes the high waters or a dead project.
uhh no, that’s technically not correct. google can not “restrict access to AOSP”. nobody can “restrict access” to an open source project. (at least not read/use access, if that’s what you’re talking about. they can exclude you from contributing your own code changes; for which case forks are the way to go)
They can restrict access to the current form of the Source as they are the Arbiters of who can obtain the Source. When I went to try to get the most recent AOSP some time ago, one of the requirements was agreeing to Google. All projects that stem out of the AOSP agreed to the terms Google laid out for the access to the AOSP. It is only “open source,” insofar as Google allowing one to access it. It is akin to a park that is free to access, so long as you pay the toll booth at the authorized road to get there.
Custom ROMs, such as CalyxOS, are based on AOSP. Per their own website(which lambasts Google and highlights Samsung for some reason):
By using a Custom ROM, and from developers contributing to the AOSP, they are supporting Google, agreeing to Google, and helping Google further their ends. Yes, your experience may differ from stockdroid, but if you think you are away from Google, Calyx admits in that one line that despite their platitudes, they are still beholden to Google. If Google restricts access to AOSP, which they can as they are who grants access in the first place, congrats, it becomes the high waters or a dead project.
uhh no, that’s technically not correct. google can not “restrict access to AOSP”. nobody can “restrict access” to an open source project. (at least not read/use access, if that’s what you’re talking about. they can exclude you from contributing your own code changes; for which case forks are the way to go)
They can restrict access to the current form of the Source as they are the Arbiters of who can obtain the Source. When I went to try to get the most recent AOSP some time ago, one of the requirements was agreeing to Google. All projects that stem out of the AOSP agreed to the terms Google laid out for the access to the AOSP. It is only “open source,” insofar as Google allowing one to access it. It is akin to a park that is free to access, so long as you pay the toll booth at the authorized road to get there.