• State Verified Answer
  • Replies 4 replies
  • Subscribers 63 subscribers
  • Views 8174 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 101611
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Error (0x81) GATT INTERNAL ERROR

Anne van Rossum

When running the Proximity Example application the Immediate Alert, Link Loss, and Tx Power services should be returned on a discovery request from the nRF Master Controller Android application.

Scanning for the device works, pairing with it works, connecting to it however shows this message. Surprisingly though the Heart Monitoring Service works as expected and lists the service it provides.

Is there something wrong with the Proximity Example? I haven't changed yet anything in the source code.

Any directions would be appreciated.

  • FormerMember
    0 FormerMember

    Hello,

    Does this happen everytime or just sometimes? What happens if you use the Master Control Panel on a PC instead of the nRF Master Control Panel on Android?

    Regards, Kristin

  • 0

    Hi Kristin,

    Sorry, I do not have a PC. :-) It does happen only for the mentioned applications, but it happens every time for them.

    I have no trouble in creating my own services, characteristics etc. See my github page github.com/.../bluenet. I was just surprised that a few of the examples did not work with the Master Control Panel app.

    Kind regards,

    Anne

  • FormerMember
    0 FormerMember

    Hi Anne,

    The proximity example should work on nRF Master Control Panel on Android.

    I am able to reproduce the error sometimes: If the phone and the device are connected and bonded, and then they get disconnected and the device is reset. The next time they are going to connect there may be an Gatt Internal Error (0x81). In this case the phone would expect to be bonded to the device, but the bonding information is deleted on the device.

    Regards, Kristin

  • 0

    I have now become accustomed to resetting low-energy bluetooth on my Nexus 4 every time I flash something new to the nrf51822. Then it's at times automatically paired by the phone itself. Unpairing it and only then starting with the nRF Master Control Panel solves the stale connection issue.

    Tip: It might be useful to disconnect(!) in the nRF Master Control Panel before a connect. This is something that is recommended somewhere on your own forums for the nrf51822 side, and might be just as useful on the Android phone.

Related