Second characteristic write wont be received (From Android)

RE: Second characteristic write wont be received (From Android)

Petter Myhre — Mon, 29 May 2017 13:18:30 GMT

Yes, you should be able to run nRF Sniffer on the nRF52 DK (if you use the unofficial firmware).

RE: Second characteristic write wont be received (From Android)

sijohans — Mon, 29 May 2017 11:33:25 GMT

Installed the nRF Connect, when the phone is in this strange state, the nrf connect also behaves strange. Seems like gatt operations are only queued on the phone and not actually performed.

RE: Second characteristic write wont be received (From Android)

sijohans — Mon, 29 May 2017 11:25:52 GMT

Hello, i have not used the nRF sniffer, will look into that. Will this one work for that: devzone.nordicsemi.com/.../ ?

I'm using a dev phone without google play, will see if i can install the nRF connect APK (found it on github now) or try it on another phone. I also notice this behavior when i end up in this state:

When i do gatt.disconnect() I receive the onConnectionStateChange callback with status GATT_SUCCESS and new connection state DISCONNECTED. However, when i receive this, i don't get the disconnected event on the nRF52 side. If i however restart bluetooth on the phone, it starts working again.

RE: Second characteristic write wont be received (From Android)

Petter Myhre — Mon, 29 May 2017 08:41:27 GMT

I don't know what is unrecoverable state is, but do you have a sniffer log? To see what is happening on air? You can use nRF Sniffer. Have you been able to reproduce this with nRF Connect for Android?