com.android.virtualdevicemanager Copy

"Virtual Device Manager", a platform application that supports Android's VirtualDeviceManager system service, which creates and manages virtual devices. Google's API reference states that a device supporting the ComputerControl feature, which lets an approved agent automate other apps, must preload the platform application VirtualDeviceManager, and must provide a per-app consent dialog and consent settings so users can choose which apps each agent may automate. Only the current assistant role holder can use ComputerControl, and target apps must be on the latest allowlist, off the denylist and have explicit user consent. The permissions recorded for this package include one to manage computer-control consent and one to manage app-op modes, consistent with it hosting that consent UI. It is not related to Android Studio's emulator tool of the same name. In our sample it is seen on Samsung Galaxy devices and on ASUS, Dell and HP Googlebooks, and where a signer is recorded for a device it is that manufacturer's own platform key. Version note: the VirtualDeviceManager API itself dates from API level 34 (Android 14), but this package appears in our sample only on API 36 and API 37 (Android 16 and Android 17), with target SDK 36 and above. The release that introduced ComputerControl and this consent app could not be sourced from the pages consulted. For Android Enterprise, EMM and kiosk use it has no enrolment or policy role. It appears to be the user-consent gate for agent automation, so disabling it would likely remove the ability to grant that consent, but its effect on the wider virtual-device service has not been documented. Leave it in place unless testing on the same model shows no side effects.

• VirtualDeviceManager - Android Developers →
• Package provenance for com.android.virtualdevicemanager - Android System App Database →

• Re-signed by each device maker with its own platform key - 5 different certificates appear across 4 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 5 permissions: 2 signature or system-level, 1 install-time and 2 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.