com.android.wifi.system.mainline.resources.overlay Copy

The sibling of com.android.wifi.system.resources.overlay, with "mainline" in its name. Like that package it is a resource-only package with no launcher entry which, going by its name and the family of overlays documented on this site, is a Runtime Resource Overlay for the Android Wi-Fi module. AOSP documents the RRO route for Wi-Fi configuration, noting that where the module ships its resource APK under a Google-signed name the overlay must target that package for its values to apply. Which package this overlay targets, and what it sets, could not be sourced. Provenance: in this site's sample it is listed on 31 devices, with the same ten platform-level OEM signing certificates as its sibling, across the same makes, and the roll-up reports target SDK 34 to 35 and version name 1.0. It is recorded alongside its sibling on 30 of its 31 devices, which fits builds that carry one overlay per possible Wi-Fi resources package name, though that reading could not be confirmed. Version note: the Wi-Fi module has been an APEX since Android 11 per AOSP; whether this overlay's role changed across releases could not be sourced. For Android Enterprise, EMM and kiosk use it has no enrolment or policy role. As with its sibling, no benefit to disabling it is identified, and its effect on Wi-Fi hardware capability settings cannot be ruled out, so leave it in place and manage Wi-Fi through your EMM's policies.

• Wi-Fi - Android Open Source Project →
• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• Package provenance for com.android.wifi.system.mainline.resources.overlay - Android System App Database →

• Re-signed by each device maker with its own platform key - 10 different certificates appear across 8 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.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.