This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

how to change the IO capability in nRF master control panel android application?

Hi, I have nexus 4 smart phone with nRF Master Control Panel application. How can i change the IO capability of the master device? I need to test the pairing process (passkey type) using the android application. I have a evaluation board with sample gluco-meter application programmed on it, and the IO capability is set to Keyboard only. When i do testing with the IOS BLE toolbox application it is working fine as i expected (i can see the passkey displayed on the IPhone, which i need to enter it on the device side.) But the same android application in the nexus 4 smart phone is not working as proper as IPhone application. Is there any difference between the android application and the IOS application, in particular with bonding? Please suggest us how to test the android application with passkey pairing method.

Regards, Balaji

Parents
  • Hi Balaji,

    The phone support both Keyboard and Display. You don't have to do anything to setup the IO capability on the phone. If you try to bond to a device that require passkey for bonding you will see a notification automatically appear on the status bar showing that you would need to type a code to pair. It should be noted that there is an issue with bonding on Nexus 4 (and Nexus 7) that you will not be able to reconnect after bonding. The BLE stack on Android is not very stable and sometimes you will find it hard to connect to a device even without previous bonding.

  • Hi Balaji,

    Since the question is a little bit out of the content of this thread, I would suggest you to open a new case next time.

    You meant you want to have keyboard IO for both side central and peripheral. This actually not possible. You should have keyboard on one side and display on the other.

    You can come up with the idea of having a hard-coded passkey on the peripheral, and pretend that your device has a display. Then type that code on the master. However, this's against the Spec, as it require the passkey is to be generated randomly on every pairing. Also this is not supported by the stack or on the phone, a random key is always generated.

Reply
  • Hi Balaji,

    Since the question is a little bit out of the content of this thread, I would suggest you to open a new case next time.

    You meant you want to have keyboard IO for both side central and peripheral. This actually not possible. You should have keyboard on one side and display on the other.

    You can come up with the idea of having a hard-coded passkey on the peripheral, and pretend that your device has a display. Then type that code on the master. However, this's against the Spec, as it require the passkey is to be generated randomly on every pairing. Also this is not supported by the stack or on the phone, a random key is always generated.

Children
No Data
Related