ADB protocol-set block: does it require a second wireless-debugging pairing

[Alex]

A flow such as   Auto ADB over TCP/IP   requires  Automate’s Privileged Service be enabled with  `Settings ▸ Privileged service start method ▸ Android Debug Bridge (ADB)`.

Thus, I already pair the phone once when enabling "Privileged service start method".

The same flow includes an **ADB protocol set** block whose setup dialog shows its own **Pair** button within the block itself.

Q1. **Do I have to run that second pairing, or can the block reuse the key created  when enabling "Privileged service start method"?

Q2. **If two separate pairing codes are unavoidable, which pairing should come first (Automate Settings-level or block-level), and will that leave me with two certificates or one?**  

Q3. **If my only goal is a hands-free Privileged Service that survives reboots, can I disable  *Connection security*  (no TLS)** inside the block, without breaking anything?**

[Henrik "The Developer" Lindqvist]

1. The Privileged service use it's own internal key inaccessible to the ADB blocks, so they have use the own, separate paring key.
2. There's no "first", they simply use different keys. Yes, the there will be at least tow keys, one for the Privileged service, and one for the ADB blocks.
3. The only reason to disable TLS is if an ADB block should connected to an Android 10 and lower device.

[Alex]

In my flow, I have Block 'System setting set' Name = "adb_wifi_enabled" Value = 1 .
Even though I stay on the same home Wi-Fi network,     **Wireless debugging prompts me to tap “Always allow on this network” after every phone reboot**.

So i have to manually select "Always allow on this network"  after every reboot. 

What should I change or add in the flow  or  in the phone settings  so that the authorization persists across reboots and the flow runs hands-free? My only goal is a hands-free Privileged Service that survives reboots.

*Device*: Samsung Galaxy A20F, Android 11, One UI 3.1

On Saturday, July 12, 2025 at 9:15:07 AM UTC-4 Henrik "The Developer" Lindqvist wrote:

1. The Privileged service use it's own internal key inaccessible to the ADB blocks, so they have use the own, separate paring key.
2. There's no "first", they simply use different keys. Yes, the there will be at least tow keys, one for the Privileged service, and one for the ADB blocks.
3. The only reason to disable TLS is if an ADB block should connected to an Android 10 and lower device.

[Henrik "The Developer" Lindqvist]

I don't know, neither what cause the dialog to reappear, nor if there's a way to prevent it, it might be device specific. Disabling the Developer option probably does.

[Henrik "The Developer" Lindqvist]

Try enabling "Disable adb authorization timeout" option.

On Saturday, July 12, 2025 at 4:02:32 PM UTC+2 Alex wrote: