This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

GATT error 133 (0x85)

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,

Parents
  • 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.

Reply
  • 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.

Children
No Data
Related