ADB privileged service start method dialog fails to open

[Desu]

Nothing Phone 2 running Nothing OS 3.0 (Android 15).

Tapping the ADB starting method option in the settings menu opens up a dialog prompting to "Tap Pair device with pairing code" with the options "Cancel" and "Show". This window only persists for two seconds or so. Tapping either option flashes the screen, closes the dialog and returns to the settings page.

After this, until the next reboot, tapping the starting method only flashes the screen and displays the text "Follow the instructions shown on screen to pair Automate with ADB on this device" for a quarter of a second before returning to the settings menu. At no point does an input field appear.

Wireless debugging is enabled, "Allow screen overlays on settings" is enabled and Automate has been given privileges to appear on top of other apps or parts of the screen, in case these settings matter.

How should I go about making this work? Thank you for your help in advance!

[Henrik "The Developer" Lindqvist]

Choosing the "Android Debug Bridge" option should show an head-up notification with the instructions, and finally a text field to input the pairing code.

Whey the "Tap Pair device with pairing code" dialog is dismissed within two seconds must be an device issue, it's not Automate doing it.

A workaround is to choose the "Manually" option and start the service from some other ADB shell, see:

https://llamalab.com/automate/doc/adb.html

[Desu]

Yes. I've seen in screenshots what intended app behaviour looks like. The scenario I described happens specifically when I choose the "Android Debug Bridge" option in the starting method sub-menu, sorry if I was unclear about that.

The two second window itself is of little consequence, it is more than enough time to tap the desired option. The issue is that no input field for the pairing code ever shows up regardless of what actions I take.

I have previously been able to start the privileged service remotely from a PC using the "Manually" option, however, that is (to my knowledge) not something I can set up to automatically run without my deliberate input when my device boots.

Are there any steps I might have missed or known issues that could be causing this?

[Henrik "The Developer" Lindqvist]

Sorry for the delay. I've got report of some devices not supporting head-up notifications, i.e. that's always shown on screen, as used during the pairing process.

For such device i'll likely have to implement some kind of workaround, e.g. showing a floating window.

The problem is that such overlays are not permitted atop system settings unless the users enabled the "Allow screen overlays on Settings" option in Developer options.

Try enabling that option to to see if it makes the notification remain on screen.

[Desu]

I believe I've had that setting enabled this entire time, but no dice. The situation hasn't changed on my end.

[Henrik "The Developer" Lindqvist]

Then you'll have to use the "Manually" option until i've implemented an alternative for the heads-up notification, or you might be able to use the ADB shell command block to execute the start command after a reboot.