This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Package Manager (Android) | |
|---|---|
| Name | Package Manager (Android) |
| Developer | |
| Released | 2008 |
| Operating system | Android (operating system) |
| Platform | ARM, x86, MIPS |
| Genre | Package management system |
| License | Apache License |
Package Manager (Android) is the system service and API set in Android (operating system) responsible for installing, updating, querying, and removing application packages. It coordinates with the Linux kernel, Android Runtime, Binder (inter-process communication), and system services to manage application lifecycle, metadata, permissions, and signatures across device profiles such as Google Pixel and vendor distributions like Samsung Electronics and OnePlus. The component underpins interactions with Google Play Store, alternative stores such as F-Droid and Amazon Appstore, and enterprise management tools including Android Enterprise.
The package management subsystem mediates between package artifacts (APKs, AABs) and system-level runtime environments like the Android Runtime and legacy Dalvik (software) VM. It exposes APIs to framework components including Activity Manager, PackageManagerService implementations, and frontends such as Settings (Android) and Google Play Services. Package Manager integrates with platform features including PackageInstaller, Device Policy Manager, and distribution mechanisms like Google Play Console for app publishing and rollout. Its responsibilities encompass package discovery, metadata indexing, intent resolution with Intent (Android), and storage allocation for apps on internal storage and external storage.
Core components include the system-side service process often called Package Manager Service, the framework-level PackageManager API exposed to apps and system components, and native tooling in the android framework and system image. Key modules are: - Package parsing module that reads manifest entries produced by Android Studio and the Android Asset Packaging Tool. - Signing and verification module interacting with KeyStore (Android), X.509 certificates, and APK Signature Scheme v2. - Permission management integrated with PermissionController and AndroidManifest.xml handling. - PackageInstaller session manager used by installation frontends, including adb (Android Debug Bridge) and Google Play Store. Interactions use IPC via Binder (inter-process communication) and system permissions mediated by SELinux (Linux) policies applied in the Android Open Source Project runtime image.
Installation workflows support user-initiated installs from storefronts like Google Play Store or command-line installs via adb (Android Debug Bridge). Package Manager resolves package names, versions, shared user IDs, and ABI compatibility for armeabi-v7a or arm64-v8a binaries. It performs staged installs, rollbacks, and updates coordinated with Runtime Resource Overlay (RRO) and split APK/AAB handling. Management operations include enable/disable, freeze/unfreeze, uninstall, and data wipe, with hooks consumed by Device Policy Controller apps used in corporate deployments and by OEM customization layers such as Samsung Knox. Package Manager also coordinates with PackageVerifier and background updater processes to enforce update policies.
Permissions are declared in AndroidManifest.xml and granted through runtime prompts governed by the permission model introduced in Android 6.0 (Marshmallow), with additional controls in Android 11 and later for background access. The model distinguishes protection levels like signature, dangerous, and normal, and supports app-op controls exposed by AppOpsManager. Security enforcement leverages SELinux (Linux) mandatory access control, kernel namespaces, and sandboxing provided by the Android Runtime. Package Manager enforces install-time signature checks for sharedUserId, verifies installer provenance (e.g., Google Play Store), and cooperates with SafetyNet and Play Protect services to mitigate malware and tampering.
Primary formats include APK (Android Package) and the newer AAB (Android App Bundle) used for optimized distribution via Google Play Store server-side generation of split APKs. APKs contain compiled code, resources, and a manifest; AABs contain module bundles processed by bundletool during publishing. Signing schemes evolved from JAR signing to APK Signature Scheme v2 and v3, relying on X.509 certificate chains and keys often managed via KeyStore (Android) or Android Keystore System. Package Manager verifies signatures during install and update to enforce certificate continuity, enabling features like shared UID and system app privileges for packages signed with platform keys used by vendors such as Qualcomm and MediaTek.
Developers interact with package management through the framework-level PackageManager (Android) API to query installed packages, resolve activities, and check permissions. Installation and management programmatically use PackageInstaller and session APIs for staged installs and multi-package transactions. Command-line and debugging tools include adb (Android Debug Bridge), pm (Android shell command), and bundletool for bundle generation and local testing. Build tooling in Android Studio and continuous integration services integrate with Gradle (software) and Firebase App Distribution to automate packaging, signing, and deployment.
Since Android 1.0, Package Manager functionality has evolved alongside platform releases such as Android 4.4 (KitKat), Android 6.0 (Marshmallow), Android 8.0 (Oreo), and Android 11. Major shifts include runtime permission model changes in Marshmallow, split APK and app bundle support introduced with Android 9 (Pie) and Google Play distribution updates, and stronger signing scheme enforcement in Android 7.0 and later. Vendor customization and enterprise features expanded with initiatives like Android Enterprise and security hardening via Project Treble and GSI (Generic System Image), shaping Package Manager behavior across diverse device ecosystems.