Skip to main content
kostyabakay
New Participant
November 20, 2023
Solved

CompanionDeviceManager 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?

 

 

    kostyabakayAnswer
    New Participant
    December 18, 2023

    I found a solution. Bluetooth and CompanionDeviceManager work only if Location Services are enabled. It is not a permission but a setting for all Location permissions on the device level. When you enable this setting you see a proper permission dialog that asks for location (approximate or precise). The documentation says: "Meta Quest’s default setting for Location Services is off. You can turn Location Services on for your Meta Quest device, and then choose to turn location on for select apps individually. Location Services must be on to share location with an individual app.". You can read more here:
    https://www.meta.com/help/quest/articles/accounts/privacy-information-and-settings/location-settings-on-meta-quest

    View in thread

    3 replies

    PyryVuorelaHiab
    Participant
    November 25, 2023

    Meta please prioritize fixing this, this issue has been around since v57.

    kostyabakayAuthorAnswer
    New Participant
    December 18, 2023

    I found a solution. Bluetooth and CompanionDeviceManager work only if Location Services are enabled. It is not a permission but a setting for all Location permissions on the device level. When you enable this setting you see a proper permission dialog that asks for location (approximate or precise). The documentation says: "Meta Quest’s default setting for Location Services is off. You can turn Location Services on for your Meta Quest device, and then choose to turn location on for select apps individually. Location Services must be on to share location with an individual app.". You can read more here:
    https://www.meta.com/help/quest/articles/accounts/privacy-information-and-settings/location-settings-on-meta-quest

      PyryVuorelaHiab
      Participant
      December 18, 2023

      You are the real MVP, thanks kostyabakay!

        Terms & ConditionsAccessibility statement