com.android.managedprovisioning.overlay Copy

A package whose name, and the "ManagedProvisioningPixelOverlay" label this site records for most of its observations, point to a runtime resource overlay (RRO) aimed at the AOSP Managed Provisioning app, com.android.managedprovisioning, which is documented separately on this site as the component that sets up work profiles and fully managed deployments. We have not inspected this package's manifest, so its target is read from that naming rather than confirmed. AOSP defines an RRO as "a package that changes the resource values of a target package at runtime", and is explicit about the limits: "overlays can't overlay code, so they can't have DEX files", and "an RRO can only be used to change the values for an existing resource". This site records no permissions against the package. If it is the overlay its name indicates, how far it can reach is bounded by the target. Managed Provisioning ships an overlayable declaration, <overlayable name="ManagedProvisioning"> with a vendor|product policy, which lists a handful of setup layout dimensions and the boolean show_progress_label_on_left_side, and AOSP states that where an app defines an overlayable tag, overlays targeting it "can overlay only the resources listed within the <overlayable> tag". On builds where that declaration applies, an overlay of this target is therefore confined to that set. Provenance is worth noting. This site records the package on Google Pixel devices, where it is Google-signed, and on Xiaomi devices, where it is signed by a Xiaomi OEM key that also signs the Android framework, a platform-level key. The "Pixel" in the label therefore appears on builds that are not Pixel builds, which is a reminder that a label reflects the source a package was built from rather than the vendor shipping it. Its recorded version names are 13 to 17, which look like platform release numbers rather than an app version, though this site cannot pair a version with a build. Version note: the site's roll-ups run from API 31 (Android 12) to API 37 (Android 17), and the target's overlayable declaration carries a 2021 copyright, which is consistent with an overlay that has followed the platform for several releases; neither figure establishes when it was introduced. No change in its own role across releases could be sourced. The flow it decorates did change over that period, because provisioning can be delegated to a device policy management role holder, whose lookup method getDevicePolicyManagementRoleHolderPackage is documented as added in API level 33 (Android 13), but that is a change in the target app rather than in this package. For Android Enterprise, EMM and kiosk use, no enrolment or policy role for it is identified in the sources cited here: it presents nothing to the user, and an RRO contains no code. If it is the overlay its name indicates, disabling it would remove its resource overrides from the enrolment screens; the values that would then apply could not be sourced, since other enabled overlays and the target's own defaults share in setting the result. There is nothing to gain from that, so leave it alone and treat com.android.managedprovisioning itself as the package that matters.

• Runtime resource overlays (RROs) - Android Open Source Project →
• ManagedProvisioning res/values/overlayable.xml - Android (packages/apps/ManagedProvisioning) source →
• ManagedProvisioning README (bundled app responsible for provisioning an enterprise device) - Android source →
• Implement device management (role-holder delegation) - Android Open Source Project →
• DevicePolicyManager (getDevicePolicyManagementRoleHolderPackage, added in API level 33) - Android Developers →
• Package provenance for com.android.managedprovisioning.overlay - Android System App Database →

• Signed by Google's own signing key (the same key Google uses across devices), so it is a Google-provided preinstall that updates independently of the system image, though 7 different Google signing keys appear across the fleet.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.