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
Quest 1 Headset Stuck in Setup Loop. Serial Number Not Recognized.
Hello everyone! I've encountered a very strange and frustrating issue with my Meta Quest 1 headset and I'm hoping someone in the community has faced something similar and can help. My headset is stuck in a setup loop after I performed a factory reset. The screen constantly shows a message to "Continue setup in the Meta Quest mobile app," and I can't proceed past it. I have already tried all the standard solutions I could find: Factory Reset: I performed this both through the phone app and the Fastboot menu, but nothing changed. App Data Clearing: I cleared all the data for the Meta Quest app on my phone and tried to connect again. Manual Firmware Update: I successfully sideloaded both the latest and an older firmware version onto the headset. The headset updated, but the problem remains. ADB Commands: After the firmware update, I tried to run a command to complete the setup, but it failed because the headset was not detected by ADB. Here's what puzzles me the most: Serial Number Not Recognized: When I enter my headset's serial number on the Meta website for verification, I get a message that the device could not be found. My account page also shows no registered devices. ADB Issue: Before the factory reset, my headset connected to my PC without issues and showed the "Allow USB debugging" window. Now, it doesn't. It seems that the problem isn't with the headset or the firmware itself, but with its connection to Meta's databases. I have exhausted all the solutions I know. Also, the headset hasn't been launched for a year Has anyone else encountered a similar issue where the device's serial number is not recognized by the system? Are there any other options besides contacting official support? Thanks for any help!
No response with USB and ADB on Meta Quest 3S
I am in the organization and can activate the developer option in the Meta Horizon app. I have also activated the developer option in the Meta Quest 3S. When I connect the headset to the PC, I only hear a tone that the headset is charging, but there is no reaction in the headset or on the PC. ADB cannot find any device. SideQuest cannot find any device either. I have restarted the headset and still cannot establish a connection. I can connect my phone to ADB without any problems. SideQuest also recognizes my phone with the same cable. I have deactivated and activated the developer option several times. Link does not work with Meta Quest Link either.No ADB devices connected
No ADB devices connected. I keep refreshing, restarting and double checking cables but still I cannot Build my Unity project to my Quest 3. The Windows 10 PC states that the Quest 3 is connected via USB. I had this working 6 months ago but now I simply cannot connect. I wish to run my Unity game on the Quest 3. Any advice or help pages most appreciated. Michael - not a programmer but an enthusiastic creator.
macOS MQDH 4.4.1 ships with x86_64 adb
Title says it all. Current (as of this writing) revision of MQDH for macOS ships with adb built only for x86 when it should probably be a universal build like the rest of the app. Evidence from the CLI: my-fancy-prompt$ pwd /Applications/Meta Quest Developer Hub.app/Contents/Resources/bin my-fancy-prompt$ ls Casting.app/ NOTICE.txt aapt2 InputForwardingService.apk OculusDeveloperHubService adb my-fancy-prompt$ file adb adb: Mach-O 64-bit executable x86_64 This drove me bonkers for a goot bit trying to get my Quest 3 connected to the developer hub. My Ventura-based Mac does not have Rosetta installed on it as it's actually a clean install and I avoid Rosetta unless it's absolutely necessary. When attempting to connect my Q3 to MQDH it went through the whole process and ultimatley did nothing with zero feedback, error or otherwise. There was no indication that adb failed to launch because of the "Bad CPU type" of the binary. I grabbed the platform-tools from android.com and those are indeed a universal build as they should be. I pointed MQDH at that adb and it's good for now. Please consider packaging a universal arch adb with a near-future release of MQDH for macos. Cheers!
Developer Hub - Build Upload Failed - PROCESSING ERROR, API ERROR, ECONNRESET
I am trying to upload a new build of my game through the Meta Quest Developer Hub. I am uploading it to a private release channel for alpha testing. I am getting a number of errors after multiple attempts with a different error each time. I get upload failed errors sometimes showing Processing Error please try again later, API error, or ECONNRESET Network error. I've tried looking at the log files but Im not experienced enough to know what to do. It is strange because I havent had these issues before, I've uploaded multiple builds with the most recent being a little over a week ago. I am using unity 2021, the most recent version of MQDH, and am attempting to upload an apk and single OBB file (2.2 GB). I have tried copying the adb files associated with my unity project and pasting them into the "Meta Quest Developer\resources\bin" file path. I've also tried changing the MQDH ADB file path to match the unity version in the file path "C:\Program Files\Unity\Hub\Editor\2021.3.15f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools" Nothing seems to work and its more strange that different errors pop up instead of a single consistent error. I've made sure my manifest file is correct and am increasing the version and bundle code with each build, and done other things like make sure MQDH is able to pass through my firewall, tried making a fresh release channel. I also sometimes receive this error when attempting to open MQDH and I have to uninstall it and reinstall just to get it to reopen. Am i doing something completely wrong? Here are two of the errors, with the other one saying PROCESSING_ERROR please try again later. I can send log files if needed. Thank you for any help in advance!Project Has Stopped on Oculus Quest
Unity 2019.1.2f1 and most recent Oculus SDK Oculus Quest fully updated. For some reason when building this project I get no errors at all and it runs perfect in the unity editor with good FPS and went through the Oculus Performance Lint Tool and the other tools. It installs on the headset just fine but once run, it loads up and then crashes stating: "IEP Framework has Stopped". ( IEP Framework is the project ) I included the logcat files from adb. I am not good at reading these and cannot figure out why it is doing this. When I remove everything from the scene except the LocalAvatarWithGrab, it still does the same. Any ideas?
Prompt Player Eye Tracking Setup via ADB or API call?
My team is performing a study utilizing the Quest Pro eye tracking feature. Many of our participants are new to VR and we don't want to make them traverse through many menus outside of our experience. Is there a way we can start the eye tracking calibration pop-up prior to starting our demo? It is trivial for us to load our game via an ADB call. Is there a similar method for calling the eye tracking calibrator? Can we otherwise call the eye tracking calibrator via an in-game API call? Are there any options at all to solve this problem aside from manually guiding each of our participants through to start the calibration themselves?Just lost
Hello everyone! I'm seeking advice from someone well-versed in using adb with Oculus apps. Specifically, I'd like to manage tasks such as initiating video recording, capturing photos, and other interesting functionalities. While I've gained some understanding through reverse engineering and analyzing logcat, I'm still searching for the core resources. Is it best to analyze the .apk using tools like ClassyShark, or is there official documentation available? I'd prefer to avoid the "hacker" route for simple tasks. ➜ ~ adb shell 'pm list packages | grep "com.oculus" package:com.oculus.assetdelivery package:com.oculus.avatareditor package:com.oculus.updater package:com.oculus.statscollector package:com.oculus.systemdriver package:com.oculus.websafety package:com.oculus.captionservice package:com.oculus.preshutdowntaskservice package:com.oculus.browser package:com.oculus.os.vrlockscreen package:com.oculus.cvp package:com.oculus.accountscenter package:com.oculus.identitymanagement.service package:com.oculus.vrshell.desktop package:com.oculus.integrity package:com.oculus.vrshell package:com.oculus.os.vrusb package:com.oculus.metacam package:com.oculus.extrapermissions package:com.oculus.horizon package:com.oculus.systemutilities package:com.oculus.deviceauthserver package:com.oculus.firsttimenux package:com.oculus.os.cm package:com.oculus.store package:com.oculus.linefrequencyservice package:com.oculus.bugreportuploader package:com.oculus.xrstreamingclient package:com.oculus.socialplatform package:com.oculus.qplservice package:com.oculus.assistant package:com.oculus.notification_proxy package:com.oculus.systemresource package:com.oculus.companion.server package:com.oculus.backuptransportservice package:com.oculus.MiramarSetupRetail package:com.oculus.systempermissions package:com.oculus.os.qrcodereader package:com.oculus.vrcast package:com.oculus.systemux package:com.oculus.samples.firsthand package:com.oculus.nux.ota package:com.oculus.fitnesstracker package:com.oculus.remotedesktop package:com.oculus.q4bservice package:com.oculus.bugreportservice package:com.oculus.guidebook package:com.oculus.gatekeeperservice package:com.oculus.os.chargecontrol package:com.oculus.os.clearactivity package:com.oculus.ocms package:com.oculus.yadi package:com.oculus.appsafety package:com.oculus.bodyapiservice package:com.oculus.systemactivities package:com.oculus.tv package:com.oculus.userserver2 package:com.oculus.guardianresources package:com.oculus.guardian package:com.oculus.gamingactivity package:com.oculus.explore package:com.oculus.presence package:com.oculus.helpcenter package:com.oculus.externalstorage package:com.oculus.preloader package:com.oculus.maintenanceboot package:com.oculus.micservice package:com.oculus.mobile_mrc_setup package:com.oculus.vralertservice package:com.oculus.shellenv P.S. Just visiting resource like this one - https://developer.oculus.com/documentation/native/android/mobile-testing-capture/ - c'mon - it seems like all the things in Meta are not going well if you can not properly update the documentation.
