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

A Runtime Resource Overlay (RRO) for the Wi-Fi module's resources, going by its name and by the device copy described below. AOSP explains that the Wi-Fi module does not support direct customisation and that its configuration can be customised with RROs or carrier configs; the overlayable set is named WifiCustomization, with a policy allowing overlays from the odm, product, system or vendor partitions. No observation recorded here reports this package as user-facing. This site's roll-ups report a size of about 12 KB to 17 KB and 1.0 as both the oldest and newest version name. The "mainline" in the name matches the target seen in the one copy examined. AOSP's ServiceWifiResources manifest declares the package name com.android.wifi.resources, and AOSP's Wi-Fi documentation warns that where the module delivers its resource APK as com.google.android.wifi.resources, "you must set the overlay APKS targetPackage to com.google.android.wifi.resources to overlay Wi-Fi configurations successfully". A LineageOS device tree for a Xiaomi handset (codename corot) carries an overlay named WifiResMainlineOverlay whose manifest declares this exact package name, sets android:targetPackage to com.google.android.wifi.resources and android:targetName to WifiCustomization, marks it static, and declares no code. Its values there include 5 GHz and 6 GHz support, SAE hash-to-element, fast BSS transition, background scan support and soft AP capabilities. That is one device tree; this site records a package's name, not its targetPackage, so copies on other builds could differ. Provenance: in our sample it is listed on 35 devices across 18 makes, including TCL, Motorola, Lenovo, OUKITEL, Infinix, Xiaomi, OPPO, vivo and Nothing. The site records 13 signers, each classified as an OEM key that also signs the Android framework, a platform-level key. The provenance API also lists com.android.wifi.resources.overlay, documented separately on this site, on 34 of these 35 devices. One reading is that those builds carry one overlay for each possible Wi-Fi resources package name, but that could not be confirmed. The only permission recorded is POST_NOTIFICATIONS, which is also the only one recorded for that sibling overlay; no source consulted accounts for it, and this site aggregates permissions across observations rather than per build. Version note: AOSP states the Wi-Fi module (com.android.wifi) is in APEX format and available for devices running Android 11 or higher, so an overlay for its resources belongs to the Android 11 and later module layout. In our sample it is listed on devices running API 31 to API 36, and this site's roll-up reports target SDKs of 31 to 35. No change in its role across those releases could be sourced. For Android Enterprise, EMM and kiosk use, no enrolment or policy role is identified in the sources cited here. If a device's copy is a Wi-Fi configuration overlay like the one described above, disabling it would remove its resource overrides from the Wi-Fi stack; the resulting values could not be sourced, and in the copy described above those overrides include hardware capability settings. No source consulted suggests that disabling it restricts Wi-Fi use, so no management benefit is identified to weigh against that risk: leave it in place and use your EMM's Wi-Fi configuration and restriction policies instead.

• Wi-Fi - Android Open Source Project →
• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• ServiceWifiResources AndroidManifest.xml (packages/modules/Wifi) - Android source →
• ServiceWifiResources overlayable.xml, WifiCustomization (packages/modules/Wifi) - Android source →
• WifiResMainlineOverlay AndroidManifest.xml - LineageOS device tree for Xiaomi corot (GitHub) →
• WifiResMainlineOverlay bools.xml - LineageOS device tree for Xiaomi corot (GitHub) →
• WifiResMainlineOverlay Android.bp - LineageOS device tree for Xiaomi corot (GitHub) →
• Package provenance for com.android.wifi.mainline.resources.overlay - Android System App Database →
• Package provenance for com.android.wifi.resources.overlay - Android System App Database →

• Re-signed by each device maker with its own platform key - 13 different certificates appear across 9 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.
• 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.