Forum Discussion

ercanert's avatar
ercanert
Honored Guest
3 years ago

ADB with wifi without a usb connection

Hi there,

We have a VR project, which requires us to use 20-40 Quest 2s and a mobile hotspot device for a local network. Our project consists of several .apk files installed into our devices, and we use MQDH to send adb scripts so we can launch them or return home, using the Local Network the hotspot device provides. The apps need to launch simultaneously or with minimal lag.

However, MQDH requires a USB connection to turn on adb-over-wifi, and also if the connection is lost somehow, we need to re-establish it, not so reliable.

How can we overcome this? We just need a local network with several Quest 2s and a computer/tablet/phone to launch apps wirelessly. I know there are some apps for that but they require us rooting the devices, which we do not want.

 

Any help? Thanks.

advice
dev mode
issue
Quest
question

2 Replies

  • AspenJag's avatar
    AspenJag
    Protege
    2 years ago

    This problem is made worse for a Quest 3 with it's aggressive power saving specifically with WiFi. I've found that having something like a bit of paper covering the sensor can make it help keep a Wifi connection but the headset turns off eventually if it doesn't move and turning off Wifi. For your situation this might not apply depending on what could be the issue. Setting the headset's display turn off timers can help too or in MQDH turning off the Proximity sensor. This is a pretty silly workaround since meta hasn't given us tools to specifically keep wifi enabled like this.

  • L4nd4u's avatar
    L4nd4u
    Explorer
    29 days ago

    Same problem. Some days I have to plug/unplug hundreds of times. A cumbersome process and the USB-C connector starts to show serious wear and tear.