Possible causes of GATT 133 (0x85)?

RE: Possible causes of GATT 133 (0x85)?

Torsten Robitzki — Mon, 14 Sep 2015 12:25:50 GMT

Maybe it's an issue that is fixed in latter versions of android? If not, maybe http://bluekitchen-gmbh.com/ can help you, getting a proper version with your application shiped. Good Luck! ;-)

RE: Possible causes of GATT 133 (0x85)?

Lionel Sacks — Mon, 14 Sep 2015 12:21:26 GMT

yes... also, I captured a hop request of 20 from the Nexus 7 (Android 5.1.1). whereas the Samsung asks for 4.

seems a pretty poor situation! Is this common?

RE: Possible causes of GATT 133 (0x85)?

Torsten Robitzki — Mon, 14 Sep 2015 12:01:33 GMT

The seq1 and seq2 seams identical to me. In both files the master requests a hop value of 21. According to 2.3.3.1 the hop value should be in the range 5 to 16. In addition, is the "next expected sequence number" field set to 1. I think it should be set to 0. So to me it looks like the stack on your Moto G seems to be broken.

RE: Possible causes of GATT 133 (0x85)?

Lionel Sacks — Mon, 14 Sep 2015 11:44:40 GMT

Sure, just took me a moment to figure in Wirshark...

seq1.txt

seq2.txt

any good? And here (should be) a normal connection setup from the Samsung...

seq-normal.txt

RE: Possible causes of GATT 133 (0x85)?

Torsten Robitzki — Mon, 14 Sep 2015 11:38:56 GMT

Maybe this helps: www.wireshark.org/.../ChIOSaveSection.html

RE: Possible causes of GATT 133 (0x85)?

Lionel Sacks — Mon, 14 Sep 2015 11:34:25 GMT

sure, but couldn't figure out how to save a subset of packets...

RE: Possible causes of GATT 133 (0x85)?

Torsten Robitzki — Mon, 14 Sep 2015 11:22:44 GMT

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?

RE: Possible causes of GATT 133 (0x85)?

Lionel Sacks — Mon, 14 Sep 2015 10:27:14 GMT

Note, another go with wireshark captures a sequence with LL_FEATURE_REQ's....

seq

seq2.PNG

LL_FEATURE.PNG

RE: Possible causes of GATT 133 (0x85)?

Lionel Sacks — Mon, 14 Sep 2015 10:19:21 GMT

From wireshark - if this helps:

seq.PNG

adv ind advind.PNG

scan req scan_req.PNG

scan resp scan_resp.PNG

connect_req conn_req.PNG

empty PDU?!? empty.PNG

RE: Possible causes of GATT 133 (0x85)?

Lionel Sacks — Mon, 14 Sep 2015 09:16:40 GMT

ps. I see nothing of use on wireshark When I try and fail to connect from the Android MCP, the device goes into a long timeout before re-starting adverting... consistent, I guess with the connection supervisory timeout,