It's important to consider that setting Tasker as the Device Owner can impact your device, so please keep that in mind before doing this procedure.
If anything stops working because of this procedure, it is possible to remove Tasker as the Device Owner by using the Clear Device Owner option in the Device Admin/Owner action in Tasker.
A known issue for Samsung owners is that some of their Samsung services stop working and there's currently no known way to get them back to working while Tasker is the Device Owner:
YOU HAVE BEEN WARNED!
Here's how to make Tasker the Device Owner on your device
adb shell dumpsys account | find "Account {" | find /V "Session"If you're on a mac/linux write
./adb shell dumpsys account | grep "Account {" | grep -v "Session"
adb shell dpm set-device-owner net.dinglisch.android.taskerm/.MyDeviceAdminReceiverIf you're on a mac write
./adb shell dpm set-device-owner net.dinglisch.android.taskerm/.MyDeviceAdminReceiver
Note: If the ADB command above does not work you have to
If the system is not allowing you to set the permission via ADB you first have to:
On some devices the system backup functions might be disabled after you do the above. If so, use the Tasker Device Admin/Owner action to run the following Custom action:
setBackupServiceEnabled(true)After running that in Tasker backups should run again.