android Copy

The core Android framework package, shown as "Android System". This is not a normal app: it represents the platform itself, the group of Java classes, interfaces and precompiled code that every app is built on, together with the system services (such as system_server) that bridge those APIs to the hardware. It runs with the privileged android.uid.system shared user ID and is signed by the platform key, which is why each device's copy is signed by its own maker (Google on Pixel, Samsung, Xiaomi, Motorola and so on). Its contents change with every Android release, but its role does not: it is the operating system framework, present on every device. It cannot be disabled, uninstalled or sensibly managed by an EMM, and any attempt to do so would break the device rather than harden it. In an Android Enterprise, kiosk or EMM context you can safely treat it as a fixed part of the platform and ignore it in app-control or allowlist policies.

• Android architecture - Android Open Source Project →

• Re-signed by each device maker with its own platform key - 33 different certificates appear across 19 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 96 permissions: 4 runtime (user-granted), 30 signature or system-level, 4 install-time and 58 vendor or uncatalogued.
• APK size ranges from 13.0 MB to 91.5 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.