A hostile change can also be an API that apps start depending on.
You can of course re-implement the feature so it’s less hostile. But then again, why keep fighting an OS that is designed by someone who doesn’t have your best interest in mind?
>why keep fighting an OS that is designed by someone who doesn’t have your best interest in mind?
Most of the things people object to are not AOSP, but things from GMS (Play Services). AOSP does a much better job protecting the user via its security and privacy than other Linux distros.
>A hostile change can also be an API that apps start depending on.
That's already happening. Apps are using the Play Integrity API to block GrapheneOS. But GrapheneOS and their users have convinced some apps to officially support GrapheneOS. Roblox, for example, officially supports GrapheneOS.
AOSP is not anti privacy. They're adding helpful permissions like the local network just recently in Android 17.