Package
com.google.android.microdroid.empty_payload
Guidance
A test payload package for the Android Virtualization Framework (AVF), not an app. In the Android source, AVF's com.android.virt APEX contains EmptyPayloadApp, whose manifest declares the package com.android.microdroid.empty_payload, marks the application android:testOnly="true" with android:hasCode="false", requests MANAGE_VIRTUAL_MACHINE and requires the android.software.virtualization_framework feature. Microdroid is the small Google-provided Android OS that AVF runs inside a virtual machine, so an empty payload is a minimal guest workload for that environment. The package recorded here has the same name with a com.google prefix, and this site records it requesting MANAGE_VIRTUAL_MACHINE, matching the AOSP manifest. In our sample it appears only on Google Pixel and Googlebook devices, has no launcher entry, and where signer data is available is signed by a key this site classifies as Google. Treating it as Google's build of the AOSP empty payload is an inference from the matching name and permission. Version note: the AOSP build file sets a minimum and target SDK of 34 (Android 14), and in our sample this package appears from API 35 to API 37, including on a Pixel 9a at API 35. It was not recorded on the Pixel 7 at API 33 that carries the other two packages in this file. AOSP states that AVF is supported only on ARM64 devices. For Android Enterprise, EMM and kiosk use, no enrolment, policy or user-facing role is identified in the sources cited here. It will show up in an app inventory and can be ignored. If it is the AOSP test payload its name indicates, it ships inside a platform APEX, and there is nothing to gain from trying to remove it, so leave it alone.
- Android Virtualization Framework (AVF) overview - Android Open Source Project →
- Microdroid - Android Open Source Project →
- EmptyPayloadApp AndroidManifest.xml - Android (packages/modules/Virtualization) source →
- EmptyPayloadApp Android.bp - Android (packages/modules/Virtualization) source →
- Package provenance for com.google.android.microdroid.empty_payload - Android System App Database →
- Package provenance for com.google.android.compos.payload - Android System App Database →
- Package provenance for com.google.android.virtualmachine.res - Android System App Database →
Package intelligence
Observed signing, permission, version and size signals from contributing devices - descriptive of that sample, not a verdict. These come from the v2 Package Search sync, which not every device has contributed to yet, so for some packages this detail is partial or not present at all.
- 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, and that single certificate is consistent across all 10 device profiles.
- Its largest observed manifest declares 1 permissions: 1 vendor or uncatalogued.
- Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.
Declared permissions (1)
Largest permission set observed for this package. Text is Android's own published description where one exists; platform permissions Android does not document show their granted protection level (in grey) instead; vendor or unknown constants show the name only.
| Permission | Description |
|---|---|
MANAGE_VIRTUAL_MACHINE |
- |
Manage on devices
ADB commands for this package (the inverse of each is included so you can undo). Run from an authorised shell or wire the equivalent into your DPC. Verify on a test device first - this database doesn’t yet classify which packages are safe to change. --user 0 targets the current user; drop it (and use a privileged shell) to act device-wide.
/system, so Restore re-adds it (-k keeps app data)Seen on
Each record is a device profile (make + model + Android version). Each unique handset that syncs against a matching profile will increase the observations of a package, thereby increasing confidence that a package is expected to be on a device.
| OEM | Model | Android | Provenance | Observations | Last seen |
|---|---|---|---|---|---|
| ASUS | ASUS Googlebook 14 | Android 17 | - | 1 | 12 Oct 2026 |
| Dell | XPS Googlebook | Android 17 | - | 2 | 1 Nov 2026 |
| Pixel 10 Pro | Android 16 | 1 | 26 Mar 2026 | ||
| Pixel 10 Pro | Android 17 | 1 | 1 Nov 2026 | ||
| Pixel 6 | Android 16 | - | 1 | 13 Oct 2025 | |
| Pixel 6 Pro | Android 15 | - | 9 | 23 Jun 2025 | |
| Pixel 7 Pro | Android 16 | 1 | 9 Mar 2026 | ||
| Pixel 8 | Android 16 | - | 4 | 3 Jun 2026 | |
| Pixel 8a | Android 15 | - | 1 | 5 Oct 2025 | |
| Pixel 9 Pro XL | Android 16 | 21 | 29 Mar 2026 | ||
| Pixel 9 Pro XL | Android 17 | 2 | 26 Oct 2026 | ||
| Pixel 9a | Android 15 | - | 1 | 15 Jun 2025 | |
| Pixel 9a | Android 16 | 6 | 2 Jun 2026 | ||
| Pixel 9a | Android 17 | - | 1 | 16 Jul 2026 | |
| Hp | HP Googlebook 14 | Android 17 | - | 2 | 10 Oct 2026 |
Known labels
Locale-aware display names seen in the wild.
| Label | Locale | Seen |
|---|---|---|
| com.google.android.microdroid.empty_payload | en-us | 31 |
| com.google.android.microdroid.empty_payload | nl-NL | 27 |
| com.google.android.microdroid.empty_payload | en | 25 |
| com.google.android.microdroid.empty_payload | en-gb | 14 |
| com.google.android.microdroid.empty_payload | en-GB | 4 |
| com.google.android.microdroid.empty_payload | 3 | |
| com.google.android.microdroid.empty_payload | nl-nl | 3 |
| com.google.android.microdroid.empty_payload | en-ca-u-fw-mon-mu-celsius | 1 |
| com.google.android.microdroid.empty_payload | en-de | 1 |
| com.google.android.microdroid.empty_payload | en-us-u-fw-mon-ms-ussystem-mu-fahrenhe | 1 |