Android Q privacy features in the context of the AndroidHardening project:
gist.github.com/thestinger/e4b
This is a list of Q privacy features divided up based on whether they'll be new features for the AndroidHardening project along with a partial list of features not yet upstream.
Conversation
I'll need to decide if it's worth porting features to Android P that are already going to be provided by Android Q. It makes more sense to focus on changes still relevant for Android Q, including a dozen features that were planned out but not yet implemented (not listed there).
1
AndroidHardening has always been focused on under the hood changes preserving app compatibility and avoiding changes to the user experience. That led to the vast majority of the work being dedicated to improving security of the OS and apps. Privacy changes are usually disruptive.
Replying to
Privacy changes are inherently breaks in compatibility and the AndroidHardening project is not in a position to force the app ecosystem to adapt, unlike the upstream Android project. Downstream implementations require exposing more toggles and disabling some of it by default.
1
For example, Android P was able to eliminate background audio, camera and sensors access by forcing apps to do it in the foreground, including via foreground services where audio recording is displayed to the user. The AndroidHardening approach had to expose toggles to end users.