Start Automate privileged service

1. Automate Community
2. Tools

[Info]
Premium?⁦ ✔️
Root? ⁦⁩❌
Wireless Debugging? ✔️
3rd Party Apps? ❌


[Description]
Start automate privileged service manually at boot


[Required Android version]
11+


[Things to set up]
1. Setup block #18 ADB shell command by setting the keychain and pairing the device over Wi-Fi.

2. Grant automate WRITE_SECURE_SETTINGS permission using adb or Permission Manager X. This only needs to be done once.

"pm grant com.llamalab.automate android.permission.WRITE_SECURE_SETTINGS"

3. Set automate privileged to start manually
How to set automate privileged service
Goto Settings -> Privileged service start method
Set it to Manually

4. Then start "Watchdogs" and automate privileged service should run each time the device restarts.


—————Version 3—————
Added a notification that will appear when connected to a wifi network.

The notification has 3 options.
Option 1: Never, never allow wireless debugging on the network you are connected to
Option 2: Only once, allow wireless debugging on the network you are connected to once
Option 3: All the time, allow wireless debugging on the network you are connected to all of the time
Note that the notification will time out after a 1 minute

—————Version 6—————
Added a way to modify and export the database
Change the delay block for shell command block to use sleep 0.5
Change the database to use base64Encode instead of md5
Fix some more bugs

—————Version 8—————
Merged P. Andreas Schmidt changes into this flow

P. Andreas Schmidt forked flow:
Added support for multiple languages for the xpath
Added more notification
Added a way to select a keychain for the adb shell command block
Blocks # 126, 127, 128, 129, 130, 132, 133, 134, 135, 136, 137, 138, 139, 140

—————Version 10—————
Fix a export database timestamp bug


[Things todo]
Fix any remaining bug
Maybe try to reduce the block count


[Developer's]
Billy Lutcher - the main idea & coder

P. Andreas Schmidt, IVE - contributed several ideas, the xpath for allow wireless debugging, found several errors & bugs, and a fork flow that was merged into this flow