OSC/WebSocket/MQTT to Quest
Hi there, I'm trying for a few days to have something working on UE4.27 and I'm hitting a wall. I've made a blueprint where i'm able to receive OSC input data from a remote laptop to a UE4.27 app that then triggers an event (for now print something or play a specific audio cue). It works flawlessly on UE4.27 but as soon as I load the project onto the quest and send that same OSC input data it crashes the app on the Quest 2. I tried different ports, data formats but still the same behavior without much logs to learn from which make me wonder if the Quest forbids such incoming IP communication ... could someone confirm whether or not Oculus Quest accepts remote information (regardless of the protocol used). Maybe I'm missing something in the settings somewhere but I couldn't find much information about it. Thanks for your response
v79 Dialog-Related Crashes in Android Settings
Since the v79 update, various dialogs in the Android Settings app are no longer accessible and crash the Android Settings app when opened. This includes, but is not limited to, the following: WiFi & Internet -> Private DNS Accessibility -> [ANY SERVICE] -> Turn On System -> Developer -> Wireless Debugging -> Pair with Pairing Code The following error is visible in LOGCAT: FATAL EXCEPTION: main Process: com.android.settings, PID: 2626 java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity. at androidx.appcompat.app.AppCompatDelegateImpl.createSubDecor(AppCompatDelegateImpl.java:926) at androidx.appcompat.app.AppCompatDelegateImpl.ensureSubDecor(AppCompatDelegateImpl.java:889) at androidx.appcompat.app.AppCompatDelegateImpl.setContentView(AppCompatDelegateImpl.java:772) at androidx.appcompat.app.AppCompatDialog.setContentView(AppCompatDialog.java:99) at androidx.appcompat.app.AlertController.installContent(AlertController.java:232) at androidx.appcompat.app.AlertDialog.onCreate(AlertDialog.java:278) at android.app.Dialog.dispatchOnCreate(Dialog.java:436) at android.app.Dialog.show(Dialog.java:325) at androidx.fragment.app.DialogFragment.onStart(DialogFragment.java:973) at androidx.fragment.app.Fragment.performStart(Fragment.java:3173) at androidx.fragment.app.FragmentStateManager.start(FragmentStateManager.java:625) at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:290) at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1938) at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1841) at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1778) at androidx.fragment.app.FragmentManager$5.run(FragmentManager.java:564) at android.os.Handler.handleCallback(Handler.java:958) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:218) at android.os.Looper.loop(Looper.java:310) at android.app.ActivityThread.main(ActivityThread.java:8250) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:978) This is a regression from v78 and prior versions, where these dialogs all worked as expected.
MQDH Won’t Connect Quest 3 at Final Cable Step Despite USB and ADB Working
Hello everyone, I’m encountering a frustrating issue with Meta Quest Developer Hub (MQDH) v5.7.2 on macOS while trying to set up a Quest 3 running firmware V78. ISSUE DESCRIPTION I enabled Developer Mode on Quest 3 via the mobile app. In the Quest headset, I selected “Always allow USB access.” SideQuest and ADB (adb devices) can successfully detect the Quest 3. However, when I run “Set Up New Device” in MQDH, it stalls at the final step asking me to plug in the cable, even after doing exactly that. No prompt appears inside the headset; MQDH hangs without progressing. I tried reinstalling MQDH and rebooting both Mac and headset—problem persists. WHAT I’VE TRIED Verified Developer Mode is enabled, and USB Connection Dialog permission is granted. Confirmed USB‑C cable works (SideQuest and ADB both connect). Rebooted Quest and Mac multiple times. Uninstalled and reinstalled MQDH, cleared caches/settings. Used both bundled Quest cable and a known good USB‑C data cable (I tested USB 3.2 cable / Thunderbolt cable with Mac mini USB‑C Thunderbolt port). adb works fine. REQUESTED HELP Could someone please advise on potential causes why MQDH stalls even though ADB and SideQuest work? Has anyone else experienced this on Quest 3 running firmware V78 with MQDH 5.7.2? Are there any logs or advanced diagnostics I can capture to pinpoint the blockage? If anyone has successfully connected MQDH after the V78 update, what steps resolved it? FULL ENVIRONMENT INFO Headset Firmware: Quest 3 V78 MQDH Version: 5.7.2 (macOS) OS: macOS (latest version) USB cable: Verified data-capable USB‑C ADB Output: adb devices correctly lists the headset (adb cmd / MacDroid) MQDH Behavior: stuck at final prompt, no progress NEXT STEPS I’m considering doing a factory reset and strictly following the community-suggested flow (skip Air Link until first USB prompt), but not sure if firmware V78 changed behavior. Thank you in advance!
ADB with wifi without a usb connection
Hi there, We have a VR project, which requires us to use 20-40 Quest 2s and a mobile hotspot device for a local network. Our project consists of several .apk files installed into our devices, and we use MQDH to send adb scripts so we can launch them or return home, using the Local Network the hotspot device provides. The apps need to launch simultaneously or with minimal lag. However, MQDH requires a USB connection to turn on adb-over-wifi, and also if the connection is lost somehow, we need to re-establish it, not so reliable. How can we overcome this? We just need a local network with several Quest 2s and a computer/tablet/phone to launch apps wirelessly. I know there are some apps for that but they require us rooting the devices, which we do not want. Any help? Thanks.
OVR Metric Tool + AirLink do not save metrics
Dear Quest development community, I have an issue when using OVR Metric tool with AirLink. OVR Metric tool is correctly installed and I am using it through the Meta Quest Developer Hub. Everything is fine, when I am using it with a VR app running on the Quest but it doesn't work when I am running an app installed on a PC with Airlink. More specifically, when I toogle the "Metrics UHD on" button, I can see the OVR metrics performance graphs and stats while playing. However, it doesn't save the metrics even when the "Metrics Recording on" and the "Meta Quest Link on" buttons (as shown in the screenshot). Do you have any idea or suggestion to solve this? Thank youapps from unknow sources not showing after updating v54
After updating to v54, my Quest2 no longer shows apps from unknown sources under the "unknown" category。 Previously, I could easily access a list of apps from unknown sources by selecting "unknown" from the filter icon in the App library. However, after the v54 update, selecting "unknown" only results in a perpetually loading icon, without displaying the list. Is anyone having the same issue? I would greatly appreciate your advice on how to fix this issue.
Dev mode in quest 3
I am trying to activate debug mode following tuto but not working Double authentification activated with sms Dev mode activated on helmet I tried to use side quest because meta link dies not work on my computer and it says dev mode is not activated What is strange is i can access to helmet using mtu Thank you for help
ADB not requesting authorization after the latest Oculus Quest 2 update
I’m having an issue after the latest update on my Oculus Quest 2. Everything used to work perfectly: I used the same USB cable, SideQuest, Web ADB, and other tools for debugging through ADB. However, now ADB says the device is connected, but the authorization prompt doesn’t appear. Here’s what I’ve tried so far: Connecting the headset to a different USB port. Web ADB shows the device as connected, but nothing works. Using another USB cabel. Restarting PC and Oculus In SideQuest, the headset is detected, and it shows that: ADB is available. Developer mode is enabled. Quest is found and connected. However, still displays the device as unauthorized, and I can’t proceed. It seems like this issue started after the latest Quest 2 firmware update. Has anyone else experienced this issue? Are there any workarounds or solutions? Thanks in advance for your help!
Access to spatial data as either point cloud or bounding box or any other form
I have been using quest pro for a while. Although it doesn't have a depth sensor like LiDAR, it has spatial understanding of its environment. Like if you create a roomscale boundary, you will see objects being detected with red dots and blue lines. If you place a new object inside your boundary, it will be detected as well. My question is , do devs have access to this spatial data? If yes, through which API?Built Unity standalone app becoming laggy after enabling passthrough through airlink
Hi everyone, I have a problem regarding my built app becoming lagging after enabling passthrough in airlink, because I needed the depth api and passthrough mode. When I run the app when disabling passthrough in airlink, my app will run smoothly. I used the oculus debug tool and I will see that my compositor latency is very high when passthrough is being turned on. Any solution for this situation? I have connected my PC using ethernet cable and used a dedicated 5GHz router for my quest 3.
