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.
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?
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.
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?
how to open video file in oculus quest?
I'm trying to open a video file in Oculus quest 2 through a specific app , but it just open the application and no error appears in command line. the command is: adb shell am start -n com.oculus.tv/com.oculus.livingroom.PanelActivity -t video/mp4 -d file:///storage/emulated/0//UI/Content/Movies/1.mp4 Is there any permission issue ? Please HelpQuest 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.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.
