com.android.mms.service Copy

This is MmsService, the AOSP platform service that handles the sending and receiving of multimedia messages (MMS): picture, audio and video messages, and, depending on device and carrier settings, group messages and longer text messages that a messaging app chooses to send as MMS. It lives in the framework (packages/services/Mms) and is the backend that a messaging app, such as Google Messages or an OEM's own app, drives through the system MMS APIs. It prepares and transmits messages to the carrier's MMSC over the mobile data connection; it does not itself present a user interface. A version note worth flagging: MMS was split out into this separate system service around Android 5.0 (Lollipop), when Google added public MMS-sending APIs (SmsManager.sendMultimediaMessage) and decoupled the transport from any single messaging app. Since then this package has been the shared MMS plumbing rather than part of a specific app. The exact later-version details were not sourced beyond that split, so treat finer per-release changes as unconfirmed. For Android Enterprise, EMM and kiosk fleets it is shared telephony infrastructure. On any device that sends or receives MMS it is required, and disabling it breaks MMS-based multimedia and group messaging for any app that relies on the platform MMS service, not just one app. On a SIM-less or data-only kiosk that never uses cellular messaging it is effectively dormant, but because the breakage when it is needed is system-wide and non-obvious, do not disable it unless you are certain cellular messaging is never used.

• MmsService.java - platform/packages/services/Mms (Git at Google) →

• Re-signed by each device maker with its own platform key - 32 different certificates appear across 18 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 14 permissions: 2 runtime (user-granted), 5 signature or system-level, 3 install-time and 4 vendor or uncatalogued.
• APK size ranges from 0.0 MB to 7.2 MB across the reporting device profiles, so the build differs substantially between them.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.