Quest 3 ADB permissions
Hello! I recently upgraded from Quest 2 to Quest 3. But my MQDH Custom Buttons to grab logs & bugreport don't work anymore. I don't seem to have any permissions on the headset via `adb` I can see the device with `adb devices`; I can shell into the device with `adb shell` But whenever I tried to pull a file or use `cat` I get a permission denied error on all the files in my sdcard/Android/ ... folders. Any advice would be much appreciated! JoelSolved9.8KViews1like8CommentsDeveloper 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!8.2KViews2likes12CommentsJust 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.821Views0likes0CommentsManage Multiple Windows with adb
MQDH has a open browser option. However, the browser always opens in the main central window. This can be achieved over adb as: am start -n com.oculus.vrshell/.MainActivity -a android.intent.action.MAIN -d apk://com.oculus.browser -e uri "www.google.com" How do I specific which window area to open the browser in using adb?785Views0likes0CommentsIs 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.1.3KViews0likes3CommentsOculus 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.15KViews1like7Comments