com.android.server.telecom.auto_generated_rro_product__ Copy

A build-generated Runtime Resource Overlay (RRO) targeting Telecom (com.android.server.telecom), the platform component that manages calls and routes them between the built-in telephony stack and third-party calling apps that register connection services through the android.telecom APIs. The overlay applies product-partition resource values to Telecom at runtime without modifying it. The package name follows the pattern written by the AOSP build script that generates these overlays, "<target>.auto_generated_rro_<partition>__", and the generated manifest marks the overlay static (android:isStatic="true"). On this site it is seen signed by Google and by OEMs including Samsung, Motorola, OnePlus and OUKITEL. It keeps a build's product-level overrides of Telecom's resources separate from Telecom itself. Which resource values a given build overrides could not be sourced, so this note describes the overlay's role rather than its contents. It has no launcher icon and is applied by the overlay manager. Version note: this is a build artefact, so its presence and contents vary by OEM, build and Android release. No specific Android release that changed this overlay's role could be sourced, so treat its contents as build-specific. For Android Enterprise, EMM and kiosk use it has no role in enrolment or policy. Disabling it would revert Telecom's overlaid resources to the values in Telecom itself; as those values are build-specific and unknown, and Telecom is on the call path for voice-capable deployments, treat it as caution rather than routine cleanup and test before rolling out.

• 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) →
• android.telecom package summary - Android Developers reference →
• Package provenance for com.android.server.telecom.auto_generated_rro_product__ - Android System App Database →

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