Screen Lock Service as a Device Administrator Background:

I was looking at the device administrators of my phone in the settings and saw a device administrator called &quot;screen lock service&quot;. It's description is &quot;Activating this administrator will allow the app Google play services to perform the following operations: set password rules&quot;.

A previously unsettled question is found here.
I searched the net for the apk file of the application but could not find one. So as per suggestions, I ran
adb shell dumpsys package  resolvers | sed -n /android.app.action.DEVICE_ADMIN_ENABLED/,/:/p

The output for the above code was:
  android.app.action.DEVICE_ADMIN_ENABLED:
    438a74 com.motorola.demo/.admin.DemoModeAdminReceiver
    2acd3de com.google.android.gms/.auth.managed.admin.DeviceAdminReceiver
    36b5d24 ch.deletescape.lawnchair.ci/ch.deletescape.lawnchair.gestures.handlers.SleepMethodDeviceAdmin$SleepDeviceAdmin
    42aae3e com.google.android.gms/.tapandpay.admin.TpDeviceAdminReceiver
    8efd08d com.google.android.gms/.kids.account.receiver.ProfileOwnerReceiver
    9b4f242 com.google.android.gms/.mdm.receivers.MdmDeviceAdminReceiver
    a9980b6 com.oasisfeng.greenify/.DeviceAdmin
    b5771b7 com.google.android.gm/com.android.email.SecurityPolicy$PolicyAdmin
  com.motorola.internal.intent.action.INETCONDITION_REPORT:

The data for the code is quite unsettling for the fact that none seem to correspond to screen lock service.

For reference, I am using Moto G5 Plus (not rooted, stock build with no customizations)
Also note that, I own another same device which is rooted and runs Pixel-Experience (Android 10 latest build) and unfortunately it does not have the Screen Lock Service.
An insight/breakdown for this application is helpful.
The data for the code is quite unsettling for the fact that none seem to correspond to screen lock service.

I can see why it confused you, believing that there would be an app or a service running with the same name on the system which you would have been able to identify quite easily, but could not.
The device administrator &quot;Screen Lock Service&quot; is a device administration service offered by Google Play Services (com.google.android.gms) app.
This is how I approached the problem:

I searched for a device with this problem. I managed to get my hands on a Xiaomi Redmi Note 5 running Android 9 having this administrator service enabled.

I went ahead with disabling Screen Lock Service administrator. Side by side, I had logcat running to grep any entry beginning with &quot;admin&quot;.

Through logcat I got the following output on disabling the said administrator.
Device admin ComponentInfo{com.google.android.gms/com.google.android.gms.auth.managed.admin.DeviceAdminReceiver} removed from user 0


com.google.android.gms/com.google.android.gms.auth.managed.admin.DeviceAdminReceiver is one among the many device administrators mentioned in the output of the command adb shell dumpsys package  resolvers | sed -n /android.app.action.DEVICE_ADMIN_ENABLED/,/:/p and is also mentioned in your output.

I decided to verify further by pulling the apk of Google Play Services and decompiling it. In the decompiled AndroidManifest.xml file, the relevant entry for this device administrator was this:
&lt;receiver android:description=&quot;@string/auth_device_admin_receiver_description&quot; android:enabled=&quot;false&quot; android:exported=&quot;true&quot; android:icon=&quot;@drawable/product_logo_security_shield_color_24&quot; android:label=&quot;@string/auth_device_admin_receiver_label&quot; android:name=&quot;com.google.android.gms.auth.managed.admin.DeviceAdminReceiver&quot; android:permission=&quot;android.permission.BIND_DEVICE_ADMIN&quot; android:process=&quot;@string/common_persistent_process&quot; chimera:autoEnabled=&quot;false&quot;&gt;
         &lt;meta-data android:name=&quot;android.app.device_admin&quot; android:resource=&quot;@xml/auth_password_complexity_device_admin&quot;/&gt;
         &lt;intent-filter&gt;
             &lt;action android:name=&quot;android.app.action.DEVICE_ADMIN_ENABLED&quot;/&gt;
             &lt;action android:name=&quot;android.app.action.DEVICE_ADMIN_DISABLED&quot;/&gt;
         &lt;/intent-filter&gt;


I used the information in step 6 to get three things:

the label of the device administrator in res/values/string.xml:
&lt;string name=&quot;auth_device_admin_receiver_label&quot;&gt;Screen lock service&lt;/string&gt;


the description of the device administrator in res/values/string.xml:
&lt;string name=&quot;auth_device_admin_receiver_description&quot;&gt;&quot;&lt;b&gt;Allow apps to determine the quality of the device's screen lock&lt;/b&gt;&quot;&lt;/string&gt;


the icon for the device administrator in res/drawable-xhdpi/product_logo_security_shield_color_24.png:




As for disabling it. While you can disable it, a reboot re-enables it automatically without user intervention. It appears to me that com.google.android.gms.persistent process is responsible for this. Not only is that process mentioned in the Manifest, but also during logcat it was the one after which auto-enabling of Screen Lock Service took place. Relevant logcat of post boot process:
 [ 10-01 19:59:17.126  3058: 7809 W/.gms.persisten ]
 Long monitor contention with owner lowpool[10] (7811) at void java.lang.ref.FinalizerReference.add(java.lang.Object)(FinalizerReference.java:56) waiters=0 in java.util.Map bggj.a() for 980ms   

[ 10-01 19:59:17.163  3441: 7374 I/Auth     ]
[AuthManaged, PasswordComplexityHelperImpl] Updating password complexity components state.

[ 10-01 19:59:17.163  3441: 7374 I/Auth     ]
[AuthManaged, PasswordComplexityHelperImpl] Enabling com.google.android.gms.auth.managed.ui.SetNewPasswordActivity

[ 10-01 19:59:17.164  3441: 7374 I/Auth     ]
[AuthManaged, PasswordComplexityHelperImpl] Enabling com.google.android.gms.auth.managed.admin.DeviceAdminReceiver




Summary

Screen Lock Service is a device administrator feature of Google Play Services app

If you disable it, Google Play Services app would re-enable it without seeking your authentication.

Its purpose is not documented on Google Support / Answers as of now.