com.android.carrierconfig Copy

The default Carrier Config app from AOSP, signed by the device's framework key. It is not user-facing: it supplies the baseline set of carrier-specific settings that the telephony framework reads through CarrierConfigManager. These settings control how the device behaves on a given mobile network, for example VoLTE and Wi-Fi calling, visual voicemail, SMS/MMS behaviour, APN and roaming handling, and emergency-call options. It provides generic defaults that apply when no more specific configuration is present. Android uses a layered approach here: this default app provides the fallback values, and a carrier or OEM can ship a higher-priority carrier-config app that overrides them with network-specific tuning. The package therefore exists on devices with and without a SIM, and its contents differ between OEMs even though the role is the same. This role has been stable across releases rather than changing meaning at a particular Android version. For Android Enterprise, EMM and kiosk use it has no part in enrolment or management, but it underpins correct cellular behaviour on any device that uses mobile networks. It is framework-signed and generally not user-disableable, and disabling it offers no benefit while risking incorrect carrier behaviour (calling, messaging or data quirks). Leave it in place; on Wi-Fi-only devices it simply sits idle.

• CarrierConfigManager - Android Developers →
• platform/packages/apps/CarrierConfig - Git at Google →

• Re-signed by each device maker with its own platform key - 21 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.
• Its largest observed manifest declares 5 permissions: 3 signature or system-level and 2 vendor or uncatalogued. The signature/system share marks it as a privileged component, not an ordinary app.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.