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

Service Discovery and Bonding Do Not Work in nRF Master Control Panel on Android 5.1 (Nexus 5).

PeterH

Hi,

Thank you for looking into this issue. The target BLE module we are using is a custom board (Rigado BMD200) based on nRF51822 s110 chip. We have tried a few example projects such as the ble_app_hts on the module.

To test the module, we have downloaded the nRF Master Control Panel on devices including a Nexus 5, a Nexus 7 tablet, and a Asus Zen phone. From the master control panel app, we are able to connect to the module and discover services except for Nexus 5 (runs Android 5.1), where none of the services are discovered. Upon "Connect", errors: (0x81): GATT internal error, (0x16) UnKnown(22) and Error (0x85): GATT ERROR occurred subsequently. (Please find attached the log file retrieved from the app)nRFMasterControl_Nordic_HTS.png

We thought there might something wrong with our Nexus 5 BT, but, we had no problem connecting to and performing services discovery with TI's Sensor tag (CC2541) using the master control app. (Please find attached the screenshot displaying the services from the app) nRFMasterControl_TI_SensorTag.png

One last thing, we also noticed that the "bond" function doesn't work on all the models mentioned above. So, for the HTS example, we could not read the simulated temperature measurement due to the authentication error returned when tried to enable the indicate.

Just wondering if anyone has experienced this issue, and if there's any work around with it.

Thanks.

Parents
  • 0

    @Hung, I think I found what the problem is. The version of the softdevice running on my module was 7.1.0. But in Keil, I am developing with API from version 8.0.0. Not sure how it even worked in the first place.

    After updating the softdevice .hex to 8.0.0 with nRFgo Studio and making the memory regions accordingly in Keil Flash configuration, the examples work now with my Nexus 5.

    Sorry for not checking the versions more in detail. Really appreciate your help!

Reply
  • 0

    @Hung, I think I found what the problem is. The version of the softdevice running on my module was 7.1.0. But in Keil, I am developing with API from version 8.0.0. Not sure how it even worked in the first place.

    After updating the softdevice .hex to 8.0.0 with nRFgo Studio and making the memory regions accordingly in Keil Flash configuration, the examples work now with my Nexus 5.

    Sorry for not checking the versions more in detail. Really appreciate your help!

Children
Related