PTC 57 - Unable to allow Bluetooth Device in Companion Device Manager

[PyryVuorelaHiab]

Hi,

Today I downloaded the PTC 57 firmware version and noticed that I was unable to allow Bluetooth devices to connect to my application using Companion Device Manager. This functionality was still working on the V56 but seems to be somehow broken in PTC 57.  My Application is able to start Companion Device Manager but the Allow-window that previously came up does not appear anymore. Companion Device Manager stays on its loading screen as seen image below for 10 second until it disappears. 

[FunkyTanuki]

Hello there! Thank you for sharing what you're running into with PTC v57. I did want to ask you what troubleshooting you've tried so far.

If you could also specify the device you're using, the software version on the headset I would really appreciate it.

[PyryVuorelaHiab]

Hi @FunkyTanuki ,

I found this issue when I tested an application developed by me in PTC v57 which I share to my customers through AppLab. In my application I connect to a Bluetooth LE device using Android's CompanionDeviceManager service. This has worked well in previous Meta Quest 2 firmware versions (v56 and below) but in the PTC v57 the CompanionDeviceManager process starts but it does not bring up the device confirmation page anymore. Our application targets Android API 32 and I have tested this issue on 3 different Meta Quest 2 devices with following version. 

System version: 50623410045000150
Version: 57.0.0.201.669.510738969
Runtime version: 57.0.0.201.669.510739335

I have also performed factory reset but this has not solved the issue on PTC v57. Below you can find the Java code from the native android plugin that I use to work with CompanionDeviceManager. This is working on V56 but not anymore on V57.

public void AssociateNewDevice() {

    BluetoothDeviceFilter deviceFilter = new BluetoothDeviceFilter.Builder()
            .setNamePattern(Pattern.compile("Remote"))
            .build();

    AssociationRequest pairingRequest = new AssociationRequest.Builder()
            .addDeviceFilter(deviceFilter)
            .setSingleDevice(true)
            .build();

    CompanionDeviceManager deviceManager = (CompanionDeviceManager) mUnityPlayer.currentActivity.getSystemService(Context.COMPANION_DEVICE_SERVICE);

    deviceManager.associate(pairingRequest, new CompanionDeviceManager.Callback() {
        @Override
        public void onAssociationPending(IntentSender chooserLauncher) {
            try {
                mUnityPlayer.currentActivity.startIntentSenderForResult(chooserLauncher, 0, null, 0, 0, 0);
            } catch (IntentSender.SendIntentException e) {
            }
        }

        @Override
        public void onAssociationCreated(AssociationInfo associationInfo) {
            OnDeviceAssociated(associationInfo.getDeviceMacAddress().toString());
        }

        @Override
        public void onFailure(CharSequence error) {
        }
    }, null);
}

@Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
    if (requestCode == 0) {
        if (resultCode == Activity.RESULT_OK && data != null) {
            BluetoothDevice deviceToPair = data.getParcelableExtra(
                    CompanionDeviceManager.EXTRA_DEVICE
            );

            if (deviceToPair != null) {
                OnDeviceAssociated(deviceToPair.getAddress());
            }
        }
    } else {
        super.onActivityResult(requestCode, resultCode, data);
    }
}

I'm happy to help in any way I can to get this issue solved because this is extremely important to me, so please reach out to me for any other information I can provide.

[FunkyTanuki]

Thanks for relaying this info to me. Our engineers have been made aware and are looking into it now. If you notice any changes please let me know. As well as anyone else who happens to cross this thread, giving me as much info as possible so that I can give it to our engineers would be greatly appreciated. Thanks in advance guys!

[PyryVuorelaHiab]

Today I downloaded a new update and the issue still exists on the following version.

System version: 50623410052400150
Version: 57.0.0.236.669.513664915
Runtime version: 57.0.0.236.669.513665197