com.google.android.devicelockcontroller Copy

Labelled "DeviceLockController", this appears to be Google's own build of the AOSP Device Lock Controller (com.android.devicelockcontroller, documented separately on this site). Tooling maintained by the LineageOS and GrapheneOS projects maps com.google.android.devicelockcontroller to com.android.devicelockcontroller, in the same lists that pair other Google-named packages such as com.google.android.documentsui with their AOSP names. If it is that build, it is the on-device side of Android's device lock feature: Google's DeviceLockManager reference describes a feature used by special "kiosk apps", downloaded and installed by a device lock solution, to lock and unlock a device, with a financed device as the typical use case, where the financing entity can lock the device after a missed payment and only a limited set of interactions (for example, placing emergency calls) remains allowed. Note that "kiosk app" here means the device lock solution's app, not an EMM kiosk or dedicated-device setup. In our sample it is recorded on Google, Motorola, Xiaomi, TCL, vivo and Infinix devices. Where this site holds signer data, which is 5 of those 6 makes (all but Infinix), it is signed by a key this site classifies as Google's, not one that also signs the Android framework. It requests, among others, INTERNET, com.google.android.c2dm.permission.RECEIVE, INSTALL_PACKAGES, MASTER_CLEAR and several MANAGE_DEVICE_POLICY permissions including MANAGE_DEVICE_POLICY_LOCK_TASK. This site aggregates permissions across observations rather than per build, so which builds request which permissions cannot be established. Version note: DeviceLockManager is documented as added in API level 34 (Android 14), and this site has only observed this package on devices reporting API 34 to 37, consistent with that. This site's roll-up reports version strings from "16" to "17" and target SDKs from 35 to 37. One Motorola firmware dump in a third-party GitHub repository ships an enable-disable-packages file that sets this package's default action to "disable", with a criterion to enable it when the system property ro.mot.gms.dlc2 is true, so on that build its default state depends on that property. The property's value on shipping devices, and whether other makers do the same, could not be established. For Android Enterprise, EMM and kiosk use, no enrolment or management role is identified in the sources cited here; the typical use case Google documents for the device lock feature is a financed device. No role for it outside such a programme is documented in these sources, but if a device genuinely is financed, interfering with it could matter. Treat it with caution rather than disabling it by default.

• DeviceLockManager - API reference - Android Developers →
• android.devicelock - API reference - Android Developers →
• dev/rro/target_package.py - LineageOS/scripts - GitHub →
• arsclib Constants.java - GrapheneOS/platform_tools_arsclib - GitHub →
• enable-disable-com.google.android.devicelockcontroller.xml - Motorola firmware dump (RandomPush/motorola_vienna_dump) - GitHub →
• Package provenance for com.google.android.devicelockcontroller - Android System App Database →

• 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. This certificate spans 5 device makes - the hallmark of a globally distributed Google key.
• Its largest observed manifest declares 31 permissions: 1 runtime (user-granted), 14 signature or system-level, 7 install-time and 9 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.