You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I set a device owner it will behave correctly (including automatically launching the DeviceAdminService when the owner is set) until a restart, where the DeviceAdminService will not launch but the package will remain as device owner.
It was my understanding that the DeviceAdminService should be started on boot by the system. This was working recently until I updated to Android 13 (though I am unable to confirm if this is the cause).
Repro steps:
Starts with clean device that has no device owner registered
Install Test DPC
Set Test DPC as device owner with adb command: adb shell dpm set-device-owner com.afwsamples.testdpc/.DeviceAdminReceiver
Check running services with command: adb shell dumpsys activity services. DeviceAdminService will be listed as running.
Restart the device
Run the same adb shell dumpsys activity services command. The service will not be listed as running despite being the DeviceAdminService
Is this behaviour correct? Is there any way to manually start the DeviceAdminService on boot?
The text was updated successfully, but these errors were encountered:
When I set a device owner it will behave correctly (including automatically launching the DeviceAdminService when the owner is set) until a restart, where the DeviceAdminService will not launch but the package will remain as device owner.
It was my understanding that the DeviceAdminService should be started on boot by the system. This was working recently until I updated to Android 13 (though I am unable to confirm if this is the cause).
Repro steps:
adb shell dpm set-device-owner com.afwsamples.testdpc/.DeviceAdminReceiver
adb shell dumpsys activity services
. DeviceAdminService will be listed as running.Is this behaviour correct? Is there any way to manually start the DeviceAdminService on boot?
The text was updated successfully, but these errors were encountered: