GATT error 133 (0x85)

[Thangaraj]

Hi All, Am using SDK 11.0.0.89a8197 Device Manager, I get this error very randomly .. My case is I allow only one device to bond with me , After bond I always advertise with Whitelist .. If the user need to connect to other device he will delete the bond and then only can connect to a new device ..

Everything works fine ..

But Sometimes when one device connected and then disconnected , deleted bonds on both side .. ANd try to connect again I get GATT error in Android APP..

What will cause this issue ? How can I fix this .. I searched in FOrum but couldnt find the exact case ......

Thanks,

[Hung Bui]

@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.

[Thangaraj]

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 .

[Hung Bui]

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 ?

[Thangaraj]

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 ?

[Hung Bui]

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.