There seems to be a small issue in the Guide.md: the activation command for Device Admin / Profile Owner / Device Owner is incorrect. In Guide.md, the activation command for Device Admin / Profile Owner / Device Owner is written as adb shell dpm set-(active-admin || profile-owner || device-owner) com.binbin.androidowner/com.binbin.androidowner.MyDeviceAdminReceiver. In fact, the receiver com.binbin.androidowner.MyDeviceAdminReceiver is not registered. Users executing the wrong activation command will receive an error, which could lead to some confusion.
Expected result
The correct receiver should be com.binbin.androidowner.dpm.MyDeviceAdminReceiver (as it is displayed within the app). Therefore, the activation command should be updated to adb shell dpm set-(active-admin || profile-owner || device-owner) com.binbin.androidowner/com.binbin.androidowner.dpm.MyDeviceAdminReceiver instead.
Describe the issue
There seems to be a small issue in the Guide.md: the activation command for Device Admin / Profile Owner / Device Owner is incorrect. In Guide.md, the activation command for Device Admin / Profile Owner / Device Owner is written as
adb shell dpm set-(active-admin || profile-owner || device-owner) com.binbin.androidowner/com.binbin.androidowner.MyDeviceAdminReceiver
. In fact, the receivercom.binbin.androidowner.MyDeviceAdminReceiver
is not registered. Users executing the wrong activation command will receive an error, which could lead to some confusion.Expected result
The correct receiver should be
com.binbin.androidowner.dpm.MyDeviceAdminReceiver
(as it is displayed within the app). Therefore, the activation command should be updated toadb shell dpm set-(active-admin || profile-owner || device-owner) com.binbin.androidowner/com.binbin.androidowner.dpm.MyDeviceAdminReceiver
instead.