I'm running into a recurring issue when trying to use SideQuest with my Meta Quest 3 connected at the same time as my SGWZone AI&Gaming Box (a portable eGPU enclosure). The AIBox includes an Android-based board that exposes itself over ADB using the generic serial number 1234567890ABCDEF.

Problem: When both devices are connected:

• SideQuest toggles between showing "Quest 3" and "undefined" in the top-left corner.
• Sideloading through the GUI is unreliable or fails outright.

Selecting Quest 3 manually in the dropdown only works briefly before SideQuest switches away or becomes confused again.

Cause: The AIBox uses an internal Android 4.4.2 board to run its LCD screen and diagnostics. This phantom ADB device appears alongside my Quest 3 like this:

1234567890ABCDEF        device  ← AIBox Android board
2G0YC5ZGBL02W1          device  ← Quest 3

Since SideQuest tries to automatically select the target, it gets confused between the two ADB devices — and there’s currently no way to lock or prioritize the correct device.

Workaround: I have to bypass SideQuest’s GUI entirely and sideload manually using ADB:

adb -s 2G0YC5ZGBL02W1 install myapp.apk

This works consistently, but defeats the point of using SideQuest’s interface.

Request: It would be incredibly helpful if SideQuest could:

• Allow us to persistently select a preferred ADB device, or
• Let us ignore/blacklist specific device serials (like the phantom one from the AIBox).

This would make the app much more reliable for users with embedded ADB hardware in their setups (e.g., eGPU docks, phones, dev kits).

Thanks in advance!