Quest doesn't ask to give USB permissions in dev mode
I'm using Linux, Manjaro, with the Gnome desktop. When I connect my Oculus Quest to the PC, I get no popup in the headset about giving the system USB debugging permissions, and adb devices -l says: List of devices attached 1PASH9ADMX9305 no permissions; see [http://developer.android.com/tools/device.html] usb:1-1.4 transport_id:13 If I disable developer mode, then I get a popup to allow access to the file system, and this has no checkbox to remember my choice, and the device isn't visible in adb, and I can't access it as an Android device. I had this work fine on Manjaro XFCE, but now it doesn't function for some reaosn. I have yet to restart my PC after installing adb, so I'll see if it works after a restart in the morning.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.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?
How to get the Device ID
Hey Developers, I got myself a new Oculus Quest and wanted to do some sideloading, but the device ID just won't show up. I enabled the Developer Mode in the app, created a new organisation on the oculus dashboard and installed the Oculus Go ADB-Drivers, but the command "adb devices" is still invalid in the cmd. Please help me!Adb shell start - how?
I can successfully install my (unity developed) myapp.apk file onto the Quest 2. Two issues: 1. Where does adb actually put the app? 2. I want to be able to start and restart my app at will. I can "adb shell" but when I run "start" it requires root. Somehow, Unity is causing my app to start after the install. HOW?
Can't push build to Quest through ADB
I'm having a lot of trouble pushing a build to my quest through the ADB cli. It works on one laptop I have but not another. The error I get says something about vendor keys not being set and the quest shows up as "Unauthorized" when I run "adb devices". I'm assuming from reading this thread (https://www.reddit.com/r/OculusQuest/comments/bux8ki/my_oculus_quest_wont_authorize_adb/) that I should be getting a pop-up in the quest asking to trust the computer but I haven't seen any. I've tried all of the suggested solutions short of a factory reset, which I would rather avoid (internet speed where I am is not the best and it takes a while to update). I hoping there's some more concrete way of triggering the handshake between the quest and the computer.
Quest 2 not authorizing adb wifi connection
Meta docs and many forum posts seem to indicate that it is possible to connect adb to a Quest 2 over WiFi, as it is to older Oculus hmds. But it is not working for me. I am on a Win10 laptop. When I connect the Quest 2 via usb, it presents an authorization dialog and adb works as expected. When I then follow the instructions for setting up a wifi connection, everything seems to go OK, however no authorization dialog shows up, and adb reports the device as connected but not authorized. Is this normal? Or should I be looking for a configuration problem on my PC?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.
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?ADB not running logcat properly
Adb does not seem to be behaving properly with my quest 2. Windows 10, connecting over wifi. I plugged the quest in with USB, did an adb devices and the quest was listed. I ran: adb tcpip 5555 and then unplugged the quest I ran adb connect IPaddress and it connected. I then attempted to run logcat because I'm trying to get crash information for an app I'm working on. At this point, it starts behaving oddly. When I run: adb logcat all I get is: adb server is out of date. killing... * daemon started successfully * - waiting for device - adb server is out of date. killing... * daemon started successfully * error: protocol fault (couldn't read status): Invalid argument over and over. In fact any command I try to run starts with 'adb server is out of date'. Some googling indicates that his might be due to having multiple SDKs on the machine and someone even wrote a tool to detect that (adbfixer) however running that tool doesn't show any conflicting versions. So I'm manually running a search on my machine to see if I can find multiple copies of adb.exe or not. But that's taking quite a bit of time. Any other suggestions?