com.android.devicelockcontroller Copy

This is the AOSP DeviceLockController, the on-device component that backs Android's system device-lock feature (the "android.devicelock" API and its DeviceLockManager). It ships as part of the platform DeviceLock module and is signed by the platform, so it appears as Google-signed on Google devices and with the OEM's platform signature on other builds. Its role is to let an approved device-financing or subsidy programme lock and unlock a device: on a financed handset the financing entity can restrict the device if payments are missed, and when locked only a limited set of interactions (such as placing emergency calls) remains available. Version behaviour is the key thing to flag here. The "android.devicelock" system API and its DeviceLockManager were introduced in Android 14 (API level 34), and this AOSP DeviceLockController is the component that implements it; on this site the package is only observed on Android 14 and 15 devices, consistent with that. It should not be confused with the older, separate Play Store app "Device Lock Controller" (package com.google.android.apps.devicelock), which Google introduced in 2020 for device-financing creditors and which is a different, downloadable package. For ordinary Android Enterprise, EMM and kiosk fleets that are not part of a carrier or retailer financing programme, this component is dormant and plays no part in enrolment or management, so it can usually be left alone. It is a protected system package, so removing it is neither necessary nor straightforward for a normal deployment, and on a device that is genuinely subject to a financing lock, interfering with it could matter. Treat with caution rather than disabling by default.

• android.devicelock - API reference - Android Developers →
• platform/packages/modules/DeviceLock - Git at Google →
• Google's 'Device Lock Controller' app lets creditors manage financed phones - 9to5Google →
• Device Lock Controller - Apps on Google Play (com.google.android.apps.devicelock) →

• 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, though 18 different Google signing keys appear across the fleet. It also signs the Android framework, so it is a platform-level key on its device(s).
• Its largest observed manifest declares 26 permissions: 1 runtime (user-granted), 13 signature or system-level, 7 install-time and 5 vendor or uncatalogued. The signature/system share marks it as a privileged component, not an ordinary app.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.