com.android.dynsystem Copy

Dynamic System Updates (DSU), part of AOSP. It is the system component that lets a device download a Generic System Image (GSI) or other Android system image, install it onto a temporary dynamic partition, and boot it as a guest operating system alongside the device's normal system. This lets a developer try a new Android build without flashing or wiping the device; rebooting returns the device to its original system. Version note: DSU was introduced in Android 10. From Android 11 a "DSU Loader" user interface was added under Settings > System > Developer options, but using DSU still requires Developer options to be enabled and the images must be trusted (signed by Google or the OEM), and the feature depends on the manufacturer supporting it. On a managed device where Developer options and OEM unlocking are disabled by policy, DSU cannot be triggered in the first place. For Android Enterprise, EMM and kiosk use it has no end-user function and no role in enrolment or day-to-day management; it exists only for developer and testing workflows. It is a reasonable candidate to disable on locked-down fleets, and on a properly managed device it is effectively dormant already.

• Dynamic System Updates (DSU) - Android Developers →
• Dynamic System Updates - Android Open Source Project →

• Re-signed by each device maker with its own platform key - 31 different certificates appear across 17 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 9 permissions: 1 runtime (user-granted), 3 signature or system-level, 4 install-time and 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.