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 app
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.
persistence of debug apps
Hi All, Happy Holidays! I have a question about the persistence of a debugging app on Oculus Quest 2. When I start an app, for example i run it from Android Studio, I cannot find it in the device after the debug session. On other android devices, like smartphones, the app stay in the device until I delete it. That's good because you can deploy an app only for yourself, without submitting it to Oculus store. Can I do it on Oculus Quest 2?
Process finished when hit breakpoint remote debugging Oculus Quest 2
I'm starting to play with Android Studio and Mobile SDK and Oculus Quest 2. Everything is working correctly but when I start remote debugging any of the SDK samples in the device, when the debugger hits a breakpoint, after two or three seconds the process finishes and the debugging session closes. The logcat pane shows something like this: Process 26768 exited due to signal 9 (Killed) And the Debug pane shows something like this: Process finished with exit code 22 Is there a way to avoid the process to finish/exit when debugging the application? Thanks in advance.
Debugging of Virtual Reality application in Unity .. How to do?
I am developing a virtual reality application in unity. Every time I want to test my application I build and run the application on android note 5, Please tell me the way to debug the code? How to debug the VR application in unity and Visual studio?
Is there a way to attach gdb to debug my application on the oculus quest?
I'm using an android NativeActivity, so I need to debug my `libApp.so`. I've used adb logcat, but because my program crashes essentially immediately, there isn't time to do much meaningful inspection. The backtrace it prints isn't symbolized, so that also isn't helpful. I've looked into adbd, but I get the error "/system/bin/sh: adbd: not found", so I don't think that's a possibility.
