If occurred "RuntimeException: Unable to set Dhizuku as device owner"

[s1204IT]

Result example:

$ adb shell dpm set-device-owner com.rosan.dhizuku/.server.DhizukuDAReceiver
java.lang.RuntimeException: Can't set package ComponentInfo{com.rosan.dhizuku/com.rosan.dhizuku.server.DhizukuDAReceiver} as device owner.
        at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:149)
        at com.android.commands.dpm.Dpm.onRun(Dpm.java:96)
        at com.android.internal.os.BaseCommand.run(BaseCommand.java:51)
        at com.android.commands.dpm.Dpm.main(Dpm.java:41)
        at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
        at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:294)

If occurred this, basically give up.

---

For this reason, the feature android.software.device_admin is required.

If you want to add this feature manually, you can make it work by adding this file to /system/etc/permissions/.
However, as the path suggests, this is not an area that users can directly write to, so you will have to give up on this.

---

At least, this is what I proofed with MagiskOnWSA.
LSPosed/MagiskOnWSALocal@dfcb381

[nktnet1]

Actually, another plausible cause is disabled apps holding onto old references to the account.

A useful command to check is:

adb shell dumpsys account list

and also:

adb shell dumpsys user | grep 'UserInfo{'

For more details, see here:

• Can't Activate Dhizuku and OwnDroid BinTianqi/OwnDroid#233 (comment)
• When I activate it through Shizuku, it prompts "You are Owner!!" but when I return to the homepage, it says "Waiting for activation". #257 (comment)