com.google.android.wfcactivation Copy

"Operator setup", the label this package carries on the devices recorded here. It is Google's carrier emergency-address activation app for Wi-Fi calling, and it exists to satisfy a carrier requirement rather than to offer the user a feature of its own. It has no launcher icon and is not user-facing in our sample. The mechanism it plugs into is documented in AOSP. The carrier configuration key wfc_emergency_address_carrier_app_string holds, in Android's own words, the component name of the activity that can set up the emergency address for Wi-Fi calling as per carrier requirement. The Settings Wi-Fi calling screen reads that key, turns the value into an intent aimed at the named component, and starts it with an EXTRA_LAUNCH_CARRIER_APP extra: LAUNCH_APP_ACTIVATE before Wi-Fi calling is switched on, and LAUNCH_APP_UPDATE when the user chooses to update their emergency address. In short, this package is the activity a carrier's configuration points that key at, so that a registered emergency address exists before Wi-Fi calling can carry an emergency call. Google's own AOSP test tooling names the component com.google.android.wfcactivation/.VzwEmergencyAddressActivity and uses it to set up a Verizon VoWiFi number, which corroborates both the package's role and the US carrier context it was built for. Version note: the package name filling this role has changed across releases, and AOSP has since grown its own implementation of it. The same Google test tooling selects com.google.android.carrierentitlement/.VzwEmergencyAddressActivity on Nougat MR2 builds and com.google.android.wfcactivation/.VzwEmergencyAddressActivity on Oreo builds, so the activity moved package between those releases. From Android 12 AOSP ships ImsServiceEntitlement, an open-source implementation of the GSMA TS.43 service entitlement flow whose component com.android.imsserviceentitlement/.WfcActivationActivity is pointed at by the same carrier-config key and which can render the carrier's VoWiFi sign-up portal. Whether a given current build uses the Google package recorded here, the AOSP module, or both for different carriers could not be sourced, so treat that split as build-specific. The package is still present in our sample on devices from API 29 through 37, with target SDKs of 29 to 36. Provenance in our sample is consistent with a Google-built carrier component: it is Google-signed by certificates that do not sign the framework, it is never Play-eligible, and it appears on Google Pixel models from the Pixel 6 to the Pixel 10 Pro alongside HMD Global, Motorola, NUU and Zebra Technologies. Its permissions fit the job, including MODIFY_PHONE_STATE, WRITE_APN_SETTINGS, READ_PRIVILEGED_PHONE_STATE, restricted-network access and a setup-wizard compatibility permission. For Android Enterprise, EMM and kiosk use it has no part in enrolment, policy or management. The flow described above is the one the Settings Wi-Fi calling screen drives, so on a fleet with no SIM or no Wi-Fi calling, which covers many kiosk and single-app deployments, that path is not expected to be exercised. Whether the package has any other entry point or responsibility could not be sourced, so do not read that as the package being inert. Where it clearly does matter is a fleet using Wi-Fi calling on a carrier that requires a registered emergency address. There, disabling it removes the activity the Settings screen launches to capture or update that address, which can stop Wi-Fi calling being turned on and has obvious implications for emergency calling. What else on a build might depend on it could not be sourced, so treat disabling it as a deliberate decision and test one device on the relevant carrier first.

• CarrierConfigManager.java, KEY_WFC_EMERGENCY_ADDRESS_CARRIER_APP_STRING - Android Open Source Project →
• WifiCallingSettingsForSub.java, carrier activity intent and EXTRA_LAUNCH_CARRIER_APP - Android Open Source Project →
• TelephonyBaseTest.py, VoWiFi setup naming the wfcactivation component - Android Open Source Project (tools/test/connectivity) →
• IMS service entitlement - Android Open Source Project →
• Package provenance for com.google.android.wfcactivation - Android System App Database →

• Signed by Google's own signing key (the same key Google uses across devices), so it is a Google-provided preinstall that updates independently of the system image, though 2 different Google signing keys appear across the fleet. This certificate spans 4 device makes - the hallmark of a globally distributed Google key.
• Its largest observed manifest declares 18 permissions: 1 runtime (user-granted), 5 signature or system-level, 6 install-time and 6 vendor or uncatalogued.
• APK size ranges from 2.8 MB to 5.4 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.