Possible causes of GATT 133 (0x85)?

[Lionel Sacks]

Hi, I'm really struggling and the Android side (I guess?)

I have a nRF51 app based on the UART initially, with my own services added. etc.

On the Windows MCP it behaves exactly as expected, advertise, connect service discover. On a little Samsung YoungII, also perfect behaviour.

However, on my Moto G (and, indeed a Nexus 7) I have less luck.

• it adverts who up very slowly.
• but when I connect, from the MCP App, I get GATT 133 error, pretty consistently... and in my app also.

I have tried removing my services - and have just the bas_ service right out of the SDK. Same problem. I have the 'recommended' (as per example app) min/max conn intervals (20/75ms).

And I turn the BLE interface on/off whenever I change anything to avoid caching etc.

I'm pretty stuck!

Any ideas welcome.

cheers.

[Torsten Robitzki]

Making any sense out of the sceenshot of a single PDU is realy hard. Why don't you just save the captured samples and attach them here?