Best way to communicate with an ESP32 and Unity app through BLE (or BT serial) on an Oculus Quest?
Hi, Been trying for a long while to get an ESP32 to communicate with a Unity app on an Oculus Quest. Recently got that ESP32 to connect to the Unity app on Quest by using the "Bluetooth LE for Android and iOS" plugin that is on the Unity store, but the app didn't find the BLE service on the ESP32 ("Error during initialize: Service not found for Write") although it was connected to that ESP32. Have tried the same Unity app on an Android phone and thankfully it functions properly on the phone. Main goal with that is to get it functioning on Oculus Quest right now though. Thanks in advance for recommendations on how to make that Unity app communicate with that ESP32 through BLE (or BT serial) on the Quest properly!6.4KViews0likes7CommentsCompanionDeviceManager doesn't work on v59, Quest 2 can't connect BLE device
We have project for Oculus VR headsets which connects to external BLE devices, receive sensor data and represent it in VR. Recently Bluetooth and Location permissions were prohibited on Oculus so our functionality with BLE devices was broken and doesn't work on v59. Even if Location permission is enabled in app settings in logs it says that this permission is disabled. Documentation says we should use CompanionDeviceManager API for that purpose as alternative solution. The problem is that CompanionDeviceManager also doesn't work on v59. It shows system dialog with ProgressBar but after waiting for a short time it closes without finding Bluetooth devices. In the logs can be found a message from com.android.companiondevicemanager with a text "No adapter attached, skipping layout". It looks like internal bug with RecyclerView implementation on Oculus side. The same code works perfectly on Google Pixel 7 with Android 14 but on Oculus our project doesn't work for both approaches – Bluetooth and CompanionDeviceManager. Is there any workaround to make it work on v59? When will it be fixed by Oculus team?Solved2KViews1like3CommentsBUG. Quest 2 Bluetooth BLE Notifications often arrive in groups
My code runs on Quest 2 (Android 12.0 and OS version 56) and subscribes to the Gatt Cadence characteristic of a cadence sensor. The Cadence notifications typically arrive once per second. However some notifications can take up to 5 seconds to arrive. In that case all 5 notifications arrive at once. This makes it impractical to control a biped character using an exercise bike on the Quest 2. To verify that this is not a problem with my app, I've installed Nordic Semiconductors nRF Connect app on the Quest 2. It exhibits the same behavior as my app. Notifications often come in groups. However when the nRF Connect app is installed on IOS (my IPhone 13). All cadence notifications come in separately, about one second apart. The OVRMetrics tool shows CPU Utilization at only 25%, so the Bluetooth Stack should not have a problem keeping up with notifications that come in one second apart. I tried submitting this as a bug report but it seems there is no way to submit technical bugs through the website. Technical bugs are referred to this forum. This is discouraging since my only other post to this forum has not received any replies in 3 months.668Views0likes0CommentsBluetooth Activation in Oculus Quest (Unity)
I'm developing software to Oculus Quest. I need to connect a arduino board to my Quest via bluetooth. I tried to use the asset "Arduino Bluetooth Plugin" from Unity Asset Store, but my oculus quest bluetooth seems not be enabled. What is the way to enabled Oculus Quest bluetooth and scan/connect another devices? Thank you!5.3KViews0likes2Comments