com.mediatek.frameworkresoverlay Copy

A MediaTek package whose name matches Android's Runtime Resource Overlay (RRO) convention, preinstalled on MediaTek-based devices. An RRO is a resource-only package that changes the values of resources (such as configuration flags and defaults) in a target package at runtime without modifying that target. From the "frameworkresoverlay" name this package appears to be a framework-targeting overlay, but that the target is the framework (android / framework-res), and that its purpose is to set chipset-appropriate framework resource values, is inference from the naming convention rather than a sourced fact: MediaTek publishes no manifest or documentation for this specific package. In our sample it appears across the same range of makes as the com.mediatek platform package, is signed with each maker's own platform key, and has no user-facing entry. The precise resource values it overrides are firmware-specific and are not published, so which behaviours it changes on any given device could not be sourced. For Android Enterprise, EMM and kiosk use it plays no part in enrolment or management and exposes nothing a user interacts with. As with other framework resource overlays, disabling it reverts the framework to its unoverlaid defaults, which can change platform behaviour in ways that are chipset and firmware specific, so it is best left enabled; only consider changing it with careful per-device testing.

• Runtime Resource Overlays (RROs) - Android Open Source Project →
• Package provenance for com.mediatek.frameworkresoverlay - Android System App Database →

• Re-signed by each device maker with its own platform key - 12 different certificates appear across 8 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.
• Its largest observed manifest declares 1 permissions: 1 runtime (user-granted).
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.