Tasker-Permissions VS platform_frameworks_base

You have to grant Tasker WRITE_SECURE_SETTINGS using https://github.com/joaomgcd/Tasker-Permissions/releases/tag/v0.2.0 to toggle airplane mode.

Can you not use Tasker Permissions APP ?

Thanks! It should be added to https://github.com/joaomgcd/Tasker-Permissions , i suppose

Also, make sure you have your ADB permissions properly set. I would recommend /u/joaomgcd's Tasker Permission's app.

the task should be 'voice command' 'keyboard' 'say' (then input what you want assistant to do in the say box. i tested it with turn on my lights in place of turn off the usb device cuz i don't have it yet. just to see if it works. i also downloaded this from the dev to grant more permissions to tasker https://github.com/joaomgcd/Tasker-Permissions/releases/tag/v0.2.0 )

It's gotten a lot easier, a lot of helper utilities have been made.

Grant additional special permissions for Tasker (Will need computer for this part) on a pc/Mac go to this link follow instructions to download appropriate OS version and install on computer. Open the .exe and follow the prompts to install the program, connect your phone to the computer and enable all special permissions for Tasker. Disconnect phone from computer when finished.

Check this out if you're not aware of it; all the juicy ADB perms.

Other users reported that if you grant all permissions with this the issue will go away. Can you confirm?

Also the commit was made to AOSP not any Pixel specific Android fork.

The code is in AOSP: https://github.com/aosp-mirror/platform_frameworks_base/commit/ecbed81c3a331f2f0458923cc7e744c85ece96da

>Their fix included a similarly large refactor

Their change is hardly a big refactor. This includes all the new code, all the parameter changes everywhere the function is used, and two additional test cases. This is a tiny change.

>12 changed files with 102 additions and 26 deletions. [1]

https://github.com/aosp-mirror/platform_frameworks_base/comm...

windowmanagerimpl

This seems to be an android 12 thing, cause AccessibilityServiceInfo in master branch doesn't define the isAccessibilityTool() function (since added in API 31) and attrs.xml doesn't define which you can get with android-31-2 sdk sources after setting compileSdkVersion=31 in android studio so that it can be used as android:isAccessibilityTool="true" in accessibility-service metadata file. The AccessibilityServiceInfo is currently just a stub class for sdk 31. Since you have android 12, maybe you have noticed the notifications already.

Shell have the following permissions: https://github.com/aosp-mirror/platform_frameworks_base/blob/master/packages/Shell/AndroidManifest.xml

First, we instantiate the ArrayAdapter by passing 3 arguments: context, layout and the array of data. We passed this for the Context as it represents the current activity. We chose simple_list_item_1 for the layout, which just contains a single TextView. And here we assume that there is an ArrayList called students containing a series of student names, which was passed as our 3rd argument.

So android gets the forced density value by calling getForcedDisplayDensityForUserLocked() which gets the system secure setting DISPLAY_DENSITY_FORCED. If the setting is unset, then android ignores it. According to this commit as mentioned here, android now writes secure settings to /data/system/users/0/settings_secure.xml for user 0 instead of a database. So all that is needed is to open that file in recovery and delete the entry for the key display_density_forced, save and reboot.

https://github.com/aosp-mirror/platform_frameworks_base/commit/66c7ea91b413c9d812047288efb343c16b23d865#diff-d0d0f287428f1314466cce035e6ae3a1