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

BLE vendor service can't read characteristic after bonded

Derek

I try to implement a BLE vendor service that has some characteristics. When I bonded the nRF devive (vendor service already download to device) with my Android phone and then try to read characteristic or enable characteristic, I can't get any notification or characteristic value from BLE device. If device connect (without bond ), I can get notification or characteristic value from BLE device. I List my Android App log below:

services discovered .... OK!! setCharacteristicNotification() - uuid: 0000bbcc-1212-efde-1523-785feabcd123 enable: true Enabling notifications for 0000bbcc-1212-efde-1523-785feabcd123 gatt.writeDescriptor(00002902-0000-1000-8000-00805f9b34fb, value=0x01-00) onDescriptorWrite error 133

The issue only happen on bonded device case. I think the issue is my vendor service (source code) need do something on bonded case but I don't know to fix it.

Thank you !!

Parents
  • 0

    Hi Derek,

    Did you configure your characteristic to require authorization ? If you did and if you don't authorize that read/write, you may receive error 133. I also suspect there could be the wrong cache with the attribute table (usually happens when you bond and don't have IS_SRVC_CHANGED_CHARACT_PRESENT set to 1). I suggest you to try with our nRF Master Control Panel app. This is the app that can clear the att table cache when you disconnect. You can try to read and write a characteristic with this app.

Reply
  • 0

    Hi Derek,

    Did you configure your characteristic to require authorization ? If you did and if you don't authorize that read/write, you may receive error 133. I also suspect there could be the wrong cache with the attribute table (usually happens when you bond and don't have IS_SRVC_CHANGED_CHARACT_PRESENT set to 1). I suggest you to try with our nRF Master Control Panel app. This is the app that can clear the att table cache when you disconnect. You can try to read and write a characteristic with this app.

Children
Related
Terms of service