Pair Device with Legacy Connection OOB preshared key, using Android NRF connect

[Beldramma]

Hi,

I am working on NRF52832-based board, with SDK 15.2.

My BLE device is protected with Legacy Connection OOB preshared key.

I would like to use Android NRF Connect app to pair with my device, filling my OOB key.

I can be in pairing mode and fill my key in NRF Connect Desktop, but not with NRF Connect app.

I don't find any button to do that. There is only a button to bond, so I have added the bonding mode in my application, but I haven't succeeded to bond also.

DO you know how I can pair with my security parameters ? If I can do it only through bonding mode, can you help me resolve my problem ?

I have already checked these others subjects, but they haven't succeeded too :

https://devzone.nordicsemi.com/f/nordic-q-a/47932/oob-works-with-mcp-but-fails-with-nrf-connect

https://devzone.nordicsemi.com/f/nordic-q-a/60196/how-to-enter-oob-key-in-nrf-connect-app

https://devzone.nordicsemi.com/f/nordic-q-a/43338/android-pairing-without-bonding---nrf-connect/172332#172332

Thanks

[Beldramma]

Hi daviddedwin,

daviddedwin said:

I thought that the Android OOB was accessible only over NFC.  I also suspect that the Android OOB API is a private API in Android which complicates things a bit (not 100% sure but this was what I remember).
Adding NFC is a possible solution, will that work for you ?

Pairing mode with OOB without NFC works with NRF Connect Desktop, so  I am not sure that it is the problem.

When i did the researches to choose the security process ( Just Works, OOB, Passkey), it seemed to me that we can implement OOB without NFC.

By the way, the board is already made, we cannot add NFC inside.

[daviddedwin]

nRF Connect Desktop on the PC  is Nordicsemi controlled software infrastructure so all the BLE capability should be available for development and test, however  BLE apps on Android will have to use the Android Bluetooth API and its restrictions.
You can also try to get the development working with JUSTWORKS/PASSKEY and then focus on the OOB issue after that so that there are no other issues complicating the development.

[Beldramma]

daviddedwin said:

You can also try to get the development working with JUSTWORKS/PASSKEY and then focus on the OOB issue after that so that there are no other issues complicating the development.

For now, i deactivate the security part to test others parts.