com.android.server.telecom Copy

The Telecom framework, a core Android system service that is part of AOSP and signed by the device's framework key. Shown to users as "Phone calls", it is the switchboard that manages audio and video calls: it routes calls between ConnectionService implementations (the telephony carrier stack, or a VoIP app) and the InCallService that provides the call UI (usually the bundled phone app). It handles SIM selection, audio routing, emergency calls, call screening and redirection. The dialer app is only the interface; the actual call logic runs in this service, so it underpins all calling on the device. Disabling or removing it breaks calling and is not supported. On devices with no telephony it is largely inert but remains a framework service rather than an optional app. For Android Enterprise, EMM and kiosk use it has no role in enrolment or management and should be left alone. To restrict calling, use the EMM's dialer/app controls rather than disabling this service.

• Telecom framework overview - Android Developers →

• 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 72 permissions: 11 runtime (user-granted), 26 signature or system-level, 7 install-time and 28 vendor or uncatalogued.
• APK size ranges from 0.0 MB to 16.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.