I was really happy to see that MQDH has an option to enable ADB over Wi-Fi on a Quest 3, which would allow completely wireless development. The implementation seems to be bad joke though.
It does work, you can enable ADB over Wi-Fi and the Quest will stay connected and be reachable over ADB even after you disconnect the cable. Only for about a minute though, after which it just disables ADB over Wi-Fi and disconnects for no reason. To turn it back on you have to plug in the cable since it won't show up in MQDH again until you do that, making the feature completely pointless.
This can't possibly be intended behavior, right? It's easier to just keep the cable on if you need to connect it each time you need to communicate with the device.
I thought it might have to do with the Quest going into standby after a minute, but that's not an issue with cable connected. It also goes into standby after putting it down, but it stays online in MQDH and over ADB indefinitely without having to wake it. The only solution to actually use ADB over Wi-Fi in this state is to turn off the proximity sensor to keep the quest from going into standby and burn the screen in and drain the battery for no reason.
