com.android.settings.auto_generated_rro_product__ Copy

A build-generated Runtime Resource Overlay (RRO) whose name marks it as targeting the system Settings app (com.android.settings, documented separately on this site). An RRO changes the resource values of a target package at runtime without altering its code. This package's name has exactly the shape written by the AOSP build script that generates these overlays, whose manifest template sets the package name to "<target>.auto_generated_rro_<partition>__", with "product" recording the partition. The same template marks the overlay static (android:isStatic="true") and sets the version name to 1.0, and this site's roll-up reports 1.0 as both the oldest and newest version name. The build makefile gives product-partition overlays a higher priority than vendor ones, so results stay deterministic if both overlay the same resource. If it is the generated overlay its name indicates, it holds a build's product-level overrides of Settings resources, kept apart from the Settings app itself. Which values a given build puts in it could not be sourced. This site's size roll-up runs from about 8 KB to about 960 KB; what accounts for that range could not be sourced either. No observation recorded here reports it as user-facing. Provenance: it is listed on Google Pixel devices, where the recorded signers are keys this site classifies as Google's, and on devices from Motorola, OnePlus, realme, OUKITEL, Lenovo, HMD Global, DOOGEE, HOTWAV and others. The site records 11 distinct signers, including OEM keys from Motorola and OUKITEL, which is consistent with each build producing its own copy. Version note: its presence and contents vary by OEM and build, and in our sample it is listed on devices running API 30 to API 37. This site's roll-up reports a maximum target SDK of 10000, the value Android defines as CUR_DEVELOPMENT, "a current development build, which has not yet turned into an official release"; that suggests at least one observation came from a pre-release build, not a change in the overlay's role. No Android release that changed the role of this overlay could be sourced. For Android Enterprise, EMM and kiosk use, no enrolment or policy role is identified in the sources cited here. If it is the generated overlay its name indicates, disabling it would remove its resource overrides from Settings; the resulting values could not be sourced, so treat removal as caution and test per device. To restrict what users can reach in Settings, use your EMM's restriction policies instead.

• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• generate-enforce-rro-android-manifest.py - auto_generated_rro package name and isStatic overlay manifest (AOSP build/make source) →
• generate_enforce_rro.mk - product overlays given higher priority than vendor (AOSP build/make source) →
• Build.VERSION_CODES.CUR_DEVELOPMENT - Android Developers →
• Package provenance for com.android.settings.auto_generated_rro_product__ - 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 11 different Google signing keys appear across the fleet.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.