GATT error 133 (0x85)

RE: GATT error 133 (0x85)

howard n2wx — Wed, 18 Jul 2018 20:25:48 GMT

Hi Eliot, did anyone ever read you in to the fix for this? I've just started seeing it with a Moto G3 as a central, Android ver 7.1.1. No prob with Acer and 7.0. something

RE: GATT error 133 (0x85)

Eliot Stock — Sun, 31 Dec 2017 15:09:07 GMT

Hi @Fanis. What min and max connection interval did you settle on to get this to work? I'm seeing the same problem, I think.

RE: GATT error 133 (0x85)

Fanis — Sun, 19 Nov 2017 13:49:25 GMT

It seems that playing with connection intervals and connection interval update times can solve the problem. I have had an issue in which i could connect with honor 9 to the main firmware and couldn't to dfu bootloader. Increasing conn parameter update delays seems to solve this problem (by default there was a 100ms after first connection and honor reports disconnect right after connect, or sometimes 0x85 error).

RE: GATT error 133 (0x85)

Hung Bui — Fri, 21 Jul 2017 07:31:41 GMT

@annapalu: Please test with other phones, newer phone doesn't often have this problem. Turn off and on Bluetooth usually fix it (for a period before it comes back)

RE: GATT error 133 (0x85)

annapalu — Thu, 20 Jul 2017 17:51:46 GMT

Hi, i have the same problem, have you resolved ?

what i can see that after tot time, i can connect without problem

RE: GATT error 133 (0x85)

Thangaraj — Wed, 27 Jul 2016 09:41:04 GMT

I will update with sniffer trace , when I face it next time

RE: GATT error 133 (0x85)

Hung Bui — Wed, 27 Jul 2016 09:33:47 GMT

If it's reproduceable, please record a sniffer trace.

RE: GATT error 133 (0x85)

Thangaraj — Wed, 27 Jul 2016 08:48:34 GMT

Yes I have the issue when I delete bond on both side ..

RE: GATT error 133 (0x85)

Hung Bui — Wed, 27 Jul 2016 07:38:30 GMT

@Thangaraj: If you delete bond on the nRF5 and don't do that on the phone, the phone would try to use its bond information to encrypt the link and will be rejected by the nRF5. This could explain why you receive the error 133. If you delete bond information on both devices would you have the issue ?

RE: GATT error 133 (0x85)

Thangaraj — Tue, 26 Jul 2016 11:39:29 GMT

Hi Hung , The issue happens only after I have deleted the bond in nRF5 .. I will capture the sniffer and share you when I get the issue next time ..

Thanks

RE: GATT error 133 (0x85)

Hung Bui — Tue, 26 Jul 2016 11:22:22 GMT

Next time when you experience that please capture a sniffer trace so we can find what happened over the air. The trace should cover both, when you receive error 133 and after you erase and re-flash the application.

There is a small chance that it was because the bond information on the phone was deleted when it's not on the nRF chip and results in that the chip refuse to bond and cause the phone to throw the issue. And this could explain why if you erase the whole chip and flash again it worked.

You can also try to delete bond information on the nRF5 when the issue happens to see if it was the case.

RE: GATT error 133 (0x85)

Thangaraj — Tue, 26 Jul 2016 09:11:17 GMT

yes , even if I turn off and turn On BLE it is not recovering from it

RE: GATT error 133 (0x85)

Hung Bui — Tue, 26 Jul 2016 08:21:03 GMT

You meant when you see 133 error, everything you re-connect it will appear until you erase and flash again ? It's pretty strange, what we experienced was that it randomly appeared and went away when we reconnect/turn off and on Bluetooth.

RE: GATT error 133 (0x85)

Thangaraj — Mon, 25 Jul 2016 12:18:37 GMT

This is happening very rarely, I have faced it three times in last three months, The only way solution after that is to erase and flash again .. Any specific area I can check on ?

RE: GATT error 133 (0x85)

Hung Bui — Mon, 25 Jul 2016 12:08:11 GMT

Until now we still don't have a clue to completely fix the issue with Android issue 133. However, I haven't seen that issue very commonly especially on Samsung/Nexus devices. How often do you see the issue ? Do you also see it with our examples from the SDK ?

RE: GATT error 133 (0x85)

Thangaraj — Thu, 21 Jul 2016 10:38:19 GMT

Central is MOTO G3, and 5.1.1 ,I tried Master Control Panel APP also .. I could face the issue there also .. The same issue persist .

RE: GATT error 133 (0x85)

Hung Bui — Thu, 21 Jul 2016 08:50:30 GMT

@Thangaraj: Which central device did you use ? Which Android version was on the device ? We experienced this Android bug, error 133 quite often before. You could also try to test with our app nRF Master Control Panel to see if it can remedy the issue.