Tasker critical permission "wite_secure_settings" refused

[Roberto Colauto]

Having switched to a non-rooted device, when installing Tasker I tried to follow the instructions to gain "write_secure_settings" through ADB. As can be seen from the attached screenshot the device is recognized and authorized. However, upon using the command line

adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS

the permission is refused with the following message: "Security exception: grantRuntimepermission: neither user 2000 not current process has android.permission.Grant_Runtime_Permissions"

The device is a non-rooted Realme X2, running ColorOS 6.1, based on Android 9.

Anyone who could help me to resolve this problem? Your help would be much appreciated. 

[João Dias]

Hhmm. strange. For some reason seems like ADB on your computer doesn't have permissions to grant permissions :/ I really don't know what could cause that....

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[Roberto Colauto]

Finally figured it out, in the Developers options of the Realme ColorOS there is an option (the very last one) dealing with Permission monitoring. When disabled the ADB command "write_secure_settings" works just fine.

However, this Permission monitoring option remains a problem when running my Wifi profile (Wifi on/off depending on when I’m home or not). With Permission monitoring enabled, when Tasker tries to switch the WIfi on a window pops op stating Tasker wants to switch on Wifi - Allow or Prohibit – However, if Tasker is in the background, this window can't appear and nothing happens. With Permission monitoring disabled everything works just fine.

Is there any way or command to overcome this problem and allow Tasker to run the profile successfully with Permission monitoring enabled as it should?