com.samsung.android.wcmurlsnetworkstack Copy

Devices report this one as "WcmUrlsNetworkStackOverlay", and it has the same resource-only shape as the two Connectivity overlays above: no launcher entry, no declared permissions, roughly 12.8 KB to 17.0 KB, and version names that follow the platform. The label is unusually informative for an overlay, naming both the target (the NetworkStack module) and the kind of value it sets (URLs). Samsung does not publish what the "Wcm" prefix stands for, and it is left unexpanded here rather than guessed at. The URLs a NetworkStack overlay can set are published by the module. It declares an overlayable named NetworkStackConfig whose URL entries are config_captive_portal_http_url, config_captive_portal_https_url, their list forms config_captive_portal_http_urls and config_captive_portal_https_urls, config_captive_portal_fallback_urls, and config_evaluating_bandwidth_url. AOSP's own configuration file is explicit that overlaying is the supported route, noting that device makers wishing to change the captive portal URL configuration must set config_captive_portal_http_url rather than overlay the shipped default. Which values this Samsung overlay actually sets is not published and could not be sourced. It is a sibling of com.samsung.android.networkstack, the Samsung NetworkStack overlay documented separately on this site. Version note: NetworkStack is an updatable Mainline module, so the values in it can change independently of the firmware; this site's sample records the overlay with version names 12 through 17 and target SDK 31 to 37, tracking Android 12 through the Android 17 era. Whether its URL values changed across those releases could not be sourced. Provenance: recorded only on Samsung devices, signed with Samsung certificates marked as also signing the framework. For Android Enterprise, EMM and kiosk use this is the connectivity overlay most worth being aware of, because captive portal probe URLs determine which endpoint a device contacts to decide whether a network has working internet access, and those endpoints have to be reachable through a filtered or proxied corporate network. It is configuration, not a control: disabling it does not stop the probes, it discards the build's URL configuration and risks breaking network validation and the captive portal flow. Where kiosk mode is stopping a captive portal login from appearing, the supported fix is to allowlist the captive portal login app in the EMM application policy rather than to touch this package.

• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• Network Stack - Android Open Source Project →
• NetworkStack overlayable.xml (packages/modules/NetworkStack) - Android source →
• NetworkStack config.xml (packages/modules/NetworkStack) - Android source →
• Kiosk devices and captive portals - Android Enterprise FAQ →
• Package provenance for com.samsung.android.wcmurlsnetworkstack - 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).
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.