ADB device list empty
Hey there, when I came back to work this morning, I found both of my Quests unable to be listed under adb devices. I tried Mac and Win but the list won't get populated. In difference to yesterday I realised that every time I connect a Quest to a computer the Quest will ask to confirm: "Allow Access to Data. The connected device will be able to access files on this headset." This wasn't there before remains come back every time. I am unable to side load any builds which is kind of a show stopper.Renderdoc Meta Fork 44.1 - Failed to install Android remote server
Hi, I've been having this really frustrating issue with Renderdoc Meta Fork (previously called Renderdoc for Oculus). When selecting replay context (both Oculus Quest 2 and Oculus Quest 2 Profiling Mode) I'm getting a following error message: "Failed to install Android remote server for unknown reasons: Couldn't install APK(s). stderr: . lease check that your device is connected and accessible to adb, and that installing APKs over USB is allowed." Of course I have adb configured and Quest 2 in developer mode. I am able to install any apk's and when using regular Renderdoc (not the oculus-specific fork) the replay context attaches successfully. I've been able to succesfully connect with previous version of this tool (v40.1) in the past. However, when I downgraded today, even the old version showed the same error. I have no idea why this issue magically popped up, but I would be really glad if something could be done about this. Here's the renderdoc log if this is of any importance: RDOC 008684: [13:09:16] core.cpp( 497) - Log - RenderDoc v1.22 Windows 64-bit Release (RENDERDOC_FOR_META_QUEST) loaded in replay application RDOC 008684: [13:09:16] core.cpp( 500) - Log - Packaged for RenderDoc Meta Fork (44.1) - www.oculus.com RDOC 008684: [13:09:16] core.cpp( 508) - Warning - Couldn't open socket for target control RDOC 008684: [13:09:16] settings.cpp( 460) - Log - Loading config from C:\Users\<user>\AppData\Roaming\RenderDocMetaFork\renderdoc.conf QTRD 008684: [13:09:16] qrenderdoc.cpp( 169) - Log - QRenderDoc initialising. QTRD 008684: [13:09:16] mainwindow.cpp( 270) - Log - Disabling error reports due to invalid commit hash QTRD 008684: [13:09:16] mainwindow.cpp(3202) - Log - Couldn't load layout from "C:/Users/<user>/AppData/Roaming/QRenderDocMetaFork/DefaultLayout.config" "Nie można odnaleźć określonego pliku." RDOC 008684: [13:09:16] android_tools.cpp( 347) - Log - Initialising adb using 'C:\Program Files\Android\platform-tools\adb.exe' QTRD 008684: [13:09:16] toolwindowmanager.cpp(1548) - Warning - area parameter ignored for this type RDOC 008684: [13:09:16] d3d11_replay.cpp( 142) - Log - Running replay on nVidia / NVIDIA GeForce RTX 3060 31.0.15.1694 RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 root' RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.product.manufacturer' RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.product.model' RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.build.version.sdk' RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell "getprop ro.product.manufacturer"' RDOC 008684: [13:09:17] streamio.cpp( 428) - Warning - Socket unexpectedly disconnected during reading RDOC 008684: [13:09:17] remote_server.cpp(1211) - Warning - Didn't get proper handshake RDOC 008684: [13:09:17] streamio.cpp( 428) - Warning - Socket unexpectedly disconnected during reading RDOC 008684: [13:09:17] remote_server.cpp(1211) - Warning - Didn't get proper handshake RDOC 008684: [13:09:18] d3d12_sdk_select.cpp( 370) - Log - System D3D12 runtime is version 2 RDOC 008684: [13:09:18] d3d12_replay.cpp( 111) - Log - Running replay on nVidia / NVIDIA GeForce RTX 3060 31.0.15.1694 RDOC 008684: [13:09:18] vk_replay.cpp(4711) - Log - Created device. RDOC 008684: [13:09:24] streamio.cpp( 428) - Warning - Socket unexpectedly disconnected during reading RDOC 008684: [13:09:24] remote_server.cpp(1211) - Warning - Didn't get proper handshake RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.build.version.sdk' RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell "getprop ro.product.manufacturer"' RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell pm list packages com.oculus.renderdoccmd' RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.product.cpu.abi' RDOC 008684: [13:09:24] android.cpp(1187) - Log - Starting RenderDoc server, supported ABIs: RDOC 008684: [13:09:24] android.cpp(1189) - Log - - armeabi_v7a RDOC 008684: [13:09:24] android.cpp(1189) - Log - - arm64_v8a RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.product.cpu.abi' RDOC 008684: [13:09:24] android.cpp( 480) - Log - Checking for server APK in C:\Program Files\RenderDocForMetaQuest/plugins/android/ RDOC 008684: [13:09:24] android.cpp( 487) - Log - APKs found: C:\Program Files\RenderDocForMetaQuest/plugins/android/ RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.build.version.sdk' RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 install -r -g "C:\Program Files\RenderDocForMetaQuest/plugins/android/com.oculus.renderdoccmd.arm32.apk"' RDOC 008684: [13:09:29] android.cpp( 538) - Log - Installed package 'C:\Program Files\RenderDocForMetaQuest/plugins/android/com.oculus.renderdoccmd.arm32.apk', checking for success... RDOC 008684: [13:09:29] android.cpp( 374) - Log - Checking installed version of com.oculus.renderdoccmd.arm32 on 1WMHHA6DBG1454 RDOC 008684: [13:09:29] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell pm dump com.oculus.renderdoccmd.arm32' RDOC 008684: [13:09:29] android.cpp( 416) - Log - Installed server version (122:441) is compatible RDOC 008684: [13:09:29] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.build.version.sdk' RDOC 008684: [13:09:30] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 install -r -g "C:\Program Files\RenderDocForMetaQuest/plugins/android/com.oculus.renderdoccmd.arm64.apk"' RDOC 008684: [13:09:34] android.cpp( 538) - Log - Installed package 'C:\Program Files\RenderDocForMetaQuest/plugins/android/com.oculus.renderdoccmd.arm64.apk', checking for success... RDOC 008684: [13:09:34] android.cpp( 374) - Log - Checking installed version of com.oculus.renderdoccmd.arm64 on 1WMHHA6DBG1454 RDOC 008684: [13:09:34] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell pm dump com.oculus.renderdoccmd.arm64' RDOC 008684: [13:09:35] android.cpp( 416) - Log - Installed server version (122:441) is compatible RDOC 008684: [13:09:35] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell pm list packages com.oculus.renderdoccmd' RDOC 008684: [13:09:35] android.cpp( 573) - Error - Couldn't install APK(s). stderr: RDOC 008684: [13:09:35] android.cpp(1216) - Error - Failed to install RenderDoc server appDeveloper 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!
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?
Quest must be restarted while plugged in to be detected by Win10 PC on Developer mode
We are using the latest Oculus adb drivers, but the Quest in developer mode won't be detected by the PC once plugged in or started up whilst it is plugged in. The Quest seems to need to be plugged in while on, then restarted while still plugged in to be detected. Is this expected and desired behaviour? It creates a few extra minutes of hassle every day when setting the device up for building and testing on from a development PC.
Oculus Go ADB No Device Found
I cannot seem to get my Unity builds into the Go. I have followed every step listed here https://developer.oculus.com/documentation/mobilesdk/latest/concepts/mobile-device-setup-go/ . Yet every time I go to build I keep getting the same warning "ADB - No Device Found - output" followed by several failed errors such as "Couldn't find Android device". Unfortunately I know very little about the ADB manager and everything I've come across online either goes over my head or I does not work. Any ideas on what I could do to fix the problem or any helpful, simple tutorials on the ADB would be greatly appreciated. I should note that attempting to build on the Gear VR is successful.
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
