com.sec.unifiedwfc Copy

Labelled "Wi-Fi Calling" on Galaxy devices (and localised, so it appears as "WLAN-Anrufe", "Appels Wi-Fi" or "Llamadas Wi-Fi" depending on the device language), this is Samsung's Wi-Fi Calling component. Samsung describes the feature itself plainly: with it you can make calls and send messages over a Wi-Fi connection when cell service is not available, the phone must be on a Wi-Fi network and have active service via a SIM card or eSIM, and the control lives under Settings, Connections, Wi-Fi Calling. Samsung also notes a carrier dependency, that on AT&T phones VoLTE must be turned on before Wi-Fi Calling can be activated. In our sample it is signed by Samsung OEM keys that also sign the Android framework and has no launcher entry, so it is a preinstalled system component rather than an app a user opens. Its permission set is the useful evidence of where it sits: it holds permission identifiers naming com.sec.imsservice (the Samsung IMS stack documented separately on this site) and com.sec.epdg (documented below), read and write identifiers naming Samsung's own "iwlansettings" provider, and carrier-specific identifiers naming AT&T, Sprint, T-Mobile and Verizon. Those names are what the provenance data records; which package defines each one is not something it establishes. It also holds READ_SEARCH_INDEXABLES and a Samsung settings-search identifier, which is consistent with it supplying the Wi-Fi Calling entry inside Settings, though Samsung does not document that. For Android Enterprise, EMM and kiosk fleets it has no enrolment or management function, so the only question is whether the fleet uses the feature. On voice-capable deployments it usually earns its place: Wi-Fi calling is what keeps handsets usable in the exact environments corporate fleets live in, such as warehouses, basements and thick-walled buildings with poor cellular coverage. Removing it from a bulk debloat list is the safer default, and if it is disabled the change should be tested by placing a real call on a device with no cellular signal. Version note: the builds recorded here run from 6.9.13.63 to 8.5.00.26 with target SDKs from 30 to 36, and Samsung's own Common Criteria mode application lists record version 6.3.00.61 on Android 9-era Galaxy S10+ firmware and 6.5.00.50 on Android 11-era Galaxy S20 FE firmware. That spread points to a long-standing component rebuilt for each release rather than one superseded at a particular version. The platform around it has moved, though: AOSP states that from Android 12 Android includes support for TS.43 Service Entitlement Configuration, the GSMA specification defining the entitlement verification step for activating services including Voice-over-Wi-Fi, which is handled by a separate package (com.android.imsserviceentitlement, also documented here). Whether Samsung has moved any of its own Wi-Fi calling handling onto newer platform interfaces in recent One UI releases could not be sourced, so it is flagged here as an open question rather than answered.

• Turn on Wi-Fi Calling on Galaxy phones - Samsung US →
• IMS service entitlement - Android Open Source Project →
• Implement IMS - Android Open Source Project →
• Galaxy S10+ LTE (G975F) application list - Samsung Knox CC Mode documentation →
• Galaxy S20 FE 5G (G781B) application list - Samsung Knox CC Mode documentation →
• Package provenance for com.sec.unifiedwfc - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, but 2 different certificates appear across the fleet, so OEMs ship their own builds of it. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on Samsung devices (508 packages, 10196 observations).
• Its largest observed manifest declares 44 permissions: 1 runtime (user-granted), 10 signature or system-level, 10 install-time and 23 vendor or uncatalogued.
• APK size ranges from 5.2 MB to 8.5 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.