Unity messing up ADB

Unity Engine
,
1

Unity is messing up the ADB connection.
I already have problems using the WiFi, so I am continually plugging the USB cable, with the risk to destroy the connector of the headset, sooner or later.
Now, Unity is doing this:

7578715--939157--upload_2021-10-17_4-22-34.png
7578715--939157--upload_2021-10-17_4-22-34.png965×329 65.7 KB

It tries and tries forever to work the ADB but can’t.
And at one point, it DESTROYS the connection so that even Oculus Dev Hub won’t be able to connect to the set and I can’t install the app.
When this happens, I have to restart EVERYTHING: the Quest and the PC, wasting a huge amount of time.
Up to now this didn’t happen.
Can you PLEASE add a checkbox in the BUILD WINDOW where to enable or disable the use of the ADB from Unity?
I don’t want Unity to mess up with the ADB, just let me do the build and allow me to have Unity NOT messing crazily with the system to gain access to ADB.

2

Could you file a bug report for us? Would love for QA to have a look.

3

Hi, before sending a bug report, I must say that I was keeping open both Unity and ODH, so that may be the problem.
In fact, since Unity managed to see the headset, I’m keeping the ODH closed and the problem is not presenting itself again.
However that continuous trying the use of ADB should be avoided in my opinion, because somehow it brings to the opening of HUNDREDS of ADB TASKS (checked in the Task Manager, Win10), and the only way to get them off is to restart the system.