com.mediatek.SettingsProviderResOverlay Copy

A MediaTek package whose name follows Android's Runtime Resource Overlay (RRO) convention, preinstalled on MediaTek-based devices. An RRO is a resource-only package that changes the resource values of a target package at runtime without modifying that target's code. From the name, the target is SettingsProvider, the AOSP component that backs the system, secure and global settings databases and whose shipped defaults live in packages/SettingsProvider/res/values/defaults.xml in frameworks/base. On that reading the package exists to give a MediaTek-based build chipset-appropriate default settings values. That target and purpose are inference from the naming convention and the structure of the AOSP component, not a sourced fact: MediaTek publishes no manifest or documentation for this specific package, and which values it overrides on any given firmware is not published. Provenance is the more interesting part of this entry, and it is recorded rather than inferred. This site's sample sees the same package name across Xiaomi, Samsung, Motorola, TCL, OPPO, vivo, OUKITEL, Newland and NUU devices, with thirteen distinct signing certificates, each of them that maker's own platform key. That per-maker platform signing is the pattern seen when a silicon vendor's component is rebuilt into each device maker's firmware rather than shipped under one shared key, and it matches the pattern already recorded for com.mediatek and com.mediatek.frameworkresoverlay, documented separately on this site. It has no launcher entry and no user-facing observation. This site also records one declared permission, POST_NOTIFICATIONS, which is unusual for a resource-only package; no sourced explanation for it was found, so it is noted here without interpretation. Version note: the sample spans target SDK 31 to 36 with version names 12 through 16, so the package has tracked Android 12 to Android 16 rather than being tied to one release. Whether the values it overlays changed across those releases 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. It is worth noting that it is not a policy mechanism: an RRO sets default and configuration resource values, and it does not grant, deny or override the restrictions an EMM applies through device policy. Disabling it would revert SettingsProvider 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.

• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• SettingsProvider - Android (frameworks/base) source →
• SettingsProvider default resource values (res/values/defaults.xml) - Android (frameworks/base) source →
• Package provenance for com.mediatek.SettingsProviderResOverlay - Android System App Database →

• Re-signed by each device maker with its own platform key - 15 different certificates appear across 10 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.