com.google.android.overlay.modules.permissioncontroller.forframework Copy

The framework-targeting counterpart to com.google.android.overlay.modules.permissioncontroller. Where that overlay customises the PermissionController module itself, the "forframework" suffix indicates an overlay whose target is the core framework package (shown on this site as "android") instead. AOSP notes that "only immutable overlays targeting the android package affect resource values retrieved through Resources.getSystem()", which is why permission-related resource values that must be visible through the framework are carried in a separate overlay package from those applied to the module. Like its sibling it is seen on this site signed by OEMs rather than by Google, has no user interface, and is applied by the overlay manager. Version note: it tracks PermissionController, a Mainline module since Android 11. In this site's sample it is observed from API 29 upwards. For Android Enterprise, EMM and kiosk use it has no enrolment or policy role and does not itself change what permissions apps hold. Disabling it would revert the framework-visible resource values the build shipped, which can have device-specific effects, so treat it as caution and test on a single device first.

• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• PermissionController - Android Open Source Project →
• Package provenance for com.google.android.overlay.modules.permissioncontroller.forframework - Android System App Database →

• Re-signed by each device maker with its own platform key - 22 different certificates appear across 16 device makers in our sample. That is the signature of a stock AOSP/system package every OEM builds and signs itself, not a single maker's or a third party's preinstall. These are platform-level keys: they also sign the Android framework itself.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.