BCM20732S not notifying with newer Mac OSX versions

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

We recently noticed that notifications are not working with apps running on Mac OSX 10.10 Yosemite and the most current version of OSX 10.11 El Capitan.  It has worked on previous versions without issues, and It does work for OSX 10.9 Mavericks without issues.  In addition to our own app, we are using the LightBlue App for basic testing of notifications.  We also tried with Apple's bluetooth verification app, but these all fail with these newer OSX versions.

Broadcom provided us a newer Wiced sensor tag with the newer broadcom module and it works just fine. So we are wondering if the issue is with the BCM20732S module?  Please advise.

Thanks in advance,

    Aaron

0 Likes
1 Solution
Anonymous
Not applicable

Given the non-response on this question, it seems that others have not seen this problem.

The fix in my case was to add the following to each notify characteristic in the database, with a handle specific to each.

After CHARACTERISTIC_UUID128_WRITABLE section, add:

CHAR_DESCRIPTOR_UUID16_WRITABLE (HANDLE_CHARACTERISTIC_CHAR1_CLIENT_CONFIGURATION_DESCRIPTOR,      UUID_DESCRIPTOR_CLIENT_CHARACTERISTIC_CONFIGURATION,

     LEGATTDB_PERM_READABLE |      LEGATTDB_PERM_WRITE_REQ, 2),

     0x00,0x00,

View solution in original post

1 Reply
Anonymous
Not applicable

Given the non-response on this question, it seems that others have not seen this problem.

The fix in my case was to add the following to each notify characteristic in the database, with a handle specific to each.

After CHARACTERISTIC_UUID128_WRITABLE section, add:

CHAR_DESCRIPTOR_UUID16_WRITABLE (HANDLE_CHARACTERISTIC_CHAR1_CLIENT_CONFIGURATION_DESCRIPTOR,      UUID_DESCRIPTOR_CLIENT_CHARACTERISTIC_CONFIGURATION,

     LEGATTDB_PERM_READABLE |      LEGATTDB_PERM_WRITE_REQ, 2),

     0x00,0x00,