android.auto_generated_rro_product__ Copy

A Runtime Resource Overlay (RRO) that overlays the core framework package (shown on this site as "android") from the device's product partition. An RRO is "a package that changes the resource values of a target package at runtime" without altering the target's code: when an app resolves a framework resource, the value from the overlay is returned instead. This particular package is not hand-written but emitted automatically by the Android build, which is why its name carries the "auto_generated_rro" pattern and the "_product__" suffix that records the partition it ships on. On this site it is seen signed by Google and by many different OEMs (Samsung, Motorola and others), because each vendor's build produces its own copy. It holds a build's product-level customisations to framework resources (branding, default configuration values, styling and similar) as a separate overlay rather than baking them into the framework itself. It has no launcher icon and is not something a user opens; it is enabled and applied by the platform's overlay manager. For Android Enterprise, EMM and kiosk use it plays no part in enrolment or policy and exposes nothing interactive. Disabling it would revert whatever product-partition resource customisations the build shipped, which can change system appearance or default configuration in device-specific ways, so it is best left alone. Which auto-generated RROs are present, and what they contain, varies by OEM, build and Android release, so treat removal as caution and test per device.

• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• Customize apps (build generates one RRO per target package) - Android Open Source Project →
• Package provenance for android.auto_generated_rro_product__ - Android System App Database →

• Re-signed by each device maker with its own platform key - 20 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.
• APK size ranges from 0.0 MB to 13.1 MB across the reporting device profiles, so the build differs substantially between them.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.