Quest 2 and ADB stopped working
Hello! I've been using MQDH with Quest2 for almost a year now and they used to work perfectly fine, but since a few days ago, every time I connect my Quest 2 via Link Cable, it is detected and shown as below: However, if I try to issue any command whatsoever, be it a push, install, reconnect, etc, it turns offline. This can be seen by simply opening the Meta Quest Developer Hub. It initially appears as following: But as soon as one of those commands "finishes" (they always fail), this is the screen I'm left with. I have tried issuing `adb reconnect offline`, which simply makes the device completely vanish from the devices list. Needing a reboot of the device (and a unplug/plug of the USB cable) for it to reappear. I have tried deleting the adb keys and re-authorizing; rebooting the adb server; disabling and re-enabling the developer mode; factory resetting the Quest 2; disabling Oculus Air Link; changing which adb version to use; clean reinstall of Windows; all above with no other program running on PC, to no avail. Any help would be greatly appreciated. Maybe it was something in the last update? I can't find a way to rollback and test. INFOS Headset System Version: 49068160412800150 Version: 47.0.0.282.341.428237303 Runtime Version: 47.0.0.282.341.428237138 OS Version: user-49068160412800150 No lock pattern Oculus Android App Version: 198.0.0.4.103 MQDH Version 3.1.1 ADB Version 1.0.40 4986621 OS Windows 10 Pro 22H2 Build: 19045.2486
Mac Oculus Developer Hub Cant connect to Quest 2
I usually do a lot of development on my mac and hate to switch to windows 10 to do stuff. I wanted to get my quest 2 working with my Mac but so far nothing that I do seems to trigger enabled usb debugging on my mac with the quest 2. This works fine in windows and my Quest 1 also works on my mac. I have all the bells and whistles and settings enabled on the quest 2 (hence it works on windows 10).. the device shows up with lsusb command but adb devices listes nothing.. Thoughts?
