nRF Master Control Panel in Android

RE: nRF Master Control Panel in Android

Hung Bui — Wed, 25 Nov 2015 15:03:11 GMT

@Dani: Please follow the instruction for testing as I mentioned in the comment on 22nd Jul. The example for static passkey is provided here. Please continue to comment on above answer, not under Aleksander answer.

RE: nRF Master Control Panel in Android

Dani — Wed, 25 Nov 2015 14:54:40 GMT

Sorry, I meant static passkey-

RE: nRF Master Control Panel in Android

Hung Bui — Wed, 25 Nov 2015 14:50:03 GMT

@Dani: static address has nothing to do with static passkey, please clarify.

RE: nRF Master Control Panel in Android

Dani — Fri, 20 Nov 2015 11:12:58 GMT

I have just come back with this issue: Hung, is there any solution/proposal for my device to work with static address and being managed from Android/IoS. It is mandatory for my application to have static address as my device does not have any keyboard and it is required for it to have protection (ie.pin code)

RE: nRF Master Control Panel in Android

Hung Bui — Wed, 22 Jul 2015 10:59:18 GMT

@Dani: they should work both rev 2 and rev 3. What issue did you have ? My suggested sequence for you to test:

Start with ble_app_proximity, verify that bonding work fine -> ble_app_gls , verify that bonding with random passkey works fine -> test our statics passkey example -> your static passkey example.

RE: nRF Master Control Panel in Android

Dani — Wed, 22 Jul 2015 07:42:40 GMT

I have set Eval-Kit to work as sniffer, but it is not working. Eval-kit is based on IC rev 2, and Dongle and my proto board are based on IC rev 3 and SD110 v8.0. So, maybe I have an incompatibility problem. Could it be?

RE: nRF Master Control Panel in Android

Hung Bui — Tue, 21 Jul 2015 15:29:28 GMT

@Dani: I meant, if you try an example without static passkey but dynamic passkey, such as the ble_app_gls example (passkey will be printed on UART) would it managed to bond ?

You should also try bonding but no passkey (Just work), the example you should try is ble_app_proximity.

Note that you should better first testing without using DFU, especially butonless DFU because the attributable maybe changed, and the phone usually cache the attribute table. To make sure the bonding information is erased, click unbond in Bluetooth setting and turn off and on Bluetooth.

RE: nRF Master Control Panel in Android

Aleksander Nowakowski — Tue, 21 Jul 2015 14:55:25 GMT

If the issue is related to resolvable addresses it should be no matter what passkey you use. Bonding shouldn't work at all... I guess. But please talk with Hung, he knows more about this stuff. I only work with Android.

RE: nRF Master Control Panel in Android

Dani — Tue, 21 Jul 2015 14:35:57 GMT

I'm using the following firmware on my nRF51822-QFAC:
- s110_nrf51_8.0.0_softdevice
- DFU
- My app
In what regards Android device, I have tried with Huawey-P8-Lite (v5.0) and Sony-XPeria-C5303 (v4.3)
Without passkey, my app is perfectly working with both Android devices.
With passkey, my custom board initially connects. Then, when I try to send something from Android device, it asks me to introduce the passkey and then: it says 'bonded' but disconnected.
The example you provide is the one I have followed to implement static passkey. The only difference to work with or without passkey is:
#define SEC_PARAM_BOND (1 with passkey) (0 without passkey)
#define SEC_PARAM_MITM (1 with passkey) (0 without passkey)
In services attributes: BLE_GAP_CONN_SEC_MODE_SET_ENC_WITH_MITM (with passkey) or BLE_GAP_CONN_SEC_MODE_SET_OPEN (without passkey)

RE: nRF Master Control Panel in Android

Hung Bui — Tue, 21 Jul 2015 13:54:47 GMT

@Dani: Could you give some more information on the firmware you use on the device ? If you don't use static passkey would you have any issue when testing with Android ? Please let us know which Android device did you use.

If you try this example of static passkey, would the same issue occur ?

If possible, please provide us a sniffer trace.

RE: nRF Master Control Panel in Android

Dani — Tue, 21 Jul 2015 09:25:21 GMT

Yes. nRF MCP works fine without bonding... So. Which is the solution if I want to use a determined/fixed key? (I have no keyboard in my custom board). I suppose that static key can be used with Android and iOS, right?

RE: nRF Master Control Panel in Android

Aleksander Nowakowski — Tue, 21 Jul 2015 08:51:20 GMT

If this is the case you should have the same problems on iOS, but it should work fine on Android 4.4.4.

RE: nRF Master Control Panel in Android

Aleksander Nowakowski — Tue, 21 Jul 2015 08:50:04 GMT

Android 5 introduced private resolvable addresses while the PC version is using static address. Maybe this is the case? Does the nRF MCP work fine without bonding?