com.samsung.android.ConnectivityOverlay Copy

Samsung firmware carries a small family of connectivity-related Runtime Resource Overlays, and this is one of them. An RRO is a resource-only package that AOSP describes as changing the resource values of a target package at runtime without altering the target's code, which is how a device maker sets per-device configuration in a module it cannot edit. Everything this site records fits that shape: no launcher entry, a single declared permission (POST_NOTIFICATIONS), a size of roughly 12.8 KB to 16.9 KB, and version names that follow the platform numbering rather than an app's own. The connectivity configuration a build customises this way is published by the platform. The resources package behind ConnectivityService declares an overlayable named ServiceConnectivityResourcesConfig, whose entries include the captive portal server URL (config_networkCaptivePortalServerUrl), the switch for automatically moving off a Wi-Fi network that has lost internet access (config_networkAvoidBadWifi), the protected networks list, and the settings governing the no-internet and network-switch notifications. One entry in that list is itself version bound: AOSP states that config_activelyPreferBadWifi applies on Android 12 and 13, and that on Android 14 and above the behaviour is always the enabled one regardless of the value of the setting, so overlaying it stops mattering on newer releases. Note that Samsung does not publish which package this overlay targets or which values it sets: the connectivity target is inferred from the package name, and the specific values could not be sourced. Version note: this site's sample records version names 11 through 16 with target SDK 30 to 36, so the overlay has tracked Android 11 to Android 16 rather than belonging to a single release. Whether the values it sets changed across those releases is not published and could not be sourced. Provenance: it is recorded only on Samsung devices, signed with Samsung certificates marked as also signing the framework, consistent with an overlay built into Samsung's own firmware. For Android Enterprise, EMM and kiosk use it has no enrolment or policy role and nothing a user interacts with. It is worth knowing about only because connectivity configuration of this kind decides how the device treats a network it considers imperfect, which is exactly the behaviour that surfaces on filtered or captive corporate networks. Disabling it hardens nothing; it discards the build's connectivity configuration and reverts the platform to unoverlaid defaults, which can change connectivity behaviour in ways that are firmware specific, so it is best left enabled and only considered with careful per-device testing.

• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• ServiceConnectivityResources overlayable.xml (packages/modules/Connectivity) - Android source →
• ServiceConnectivityResources config.xml (packages/modules/Connectivity) - Android source →
• Package provenance for com.samsung.android.ConnectivityOverlay - 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 1 permissions: 1 runtime (user-granted).
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.