de0u Duh! That's a bit arsh.
On that use case I have reasons to believe Google has contributed to AOSP. As mentioned above the feature seems to be there and working fine, just the icon is hidden.
Adding a toggle and let the user choose for himself would have been a bit less radical approach? But I get the philosophy: GOS doesn't believe the end user is capable of taking the right decisions for himself. Fair enough.
My understanding is that the GOS's user base can roughly be split into 2 pools:
- the high profiles, searching to secure at all cost
- the nobodies searching for privacy and regain control over their phone kicking out Google's privileges.
Why not warning on each sensitive features + a toggle, instead of just simply obliterating them?
At the moment this implementation choice is not listed on the documentation, so the user find out when trying to configure the feature. It's quite an opinionated choice without prior notice.
I'm worried about the future choices to come. It's not an attack, it's a concern from a 2nd pool's member.