Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

RE: Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

Mitch996 — Thu, 20 Jul 2017 05:25:48 GMT

@Aleksander Nowakowski:

Hello, how's things going? Have you reached a conclusion yet?

RE: Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

Aleksander Nowakowski — Mon, 17 Jul 2017 08:29:49 GMT

True. As we were accepting any write type, their tests could have passed. Bjorn will check some things before we claim anything.

RE: Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

endnode — Mon, 17 Jul 2017 08:26:46 GMT

@mitch996 I do understand your disillusion but I would claim that "S140 breaking compatibility with Android mainstream" wasn't really proven yet;) I have seen Android phones sending Write Request (with Response) before and your Android code + logs don't show with certainty if decision which GATT Write method type (with or without Response) is made in low level BT stack of Android phones (so probably even outside direct control of phone manufacturer) or in native Android code (so somewhere between Google/AOSP and handset vendors) or up in Android BLE API/app layer (so potentially able to influence by App developers).

RE: Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

Aleksander Nowakowski — Mon, 17 Jul 2017 08:17:01 GMT

Write Default is the same, but that's in Java API. Below they use normal stack constants and Google does it one way, but other manufacturers might have adopted it to their chipsets. As far as i know, old SDs were accepting and write type, no matter what phone sent. I would have to ask our support team to do some investigation and sniffing with the new SD and different phones.

RE: Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

Mitch996 — Mon, 17 Jul 2017 08:09:08 GMT

@Aleksander Nowakowski

Hello, I'm using a sony xperia phone. I don't get it, the write default is different in different level of APIs? So you are telling me somehow older versions of android API made the same mistake as old softdevices? And because of that, it worked in the old days? That's rather a far out notion.

If you can find a 3rd party API that is easy to use that will be great :)

RE: Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

Mitch996 — Mon, 17 Jul 2017 08:05:16 GMT

@endnode that's a great point except... I'm fairly sure it's the same, however even if it's different I'm positive a 3rd party library/framework came into play which means the official APIs are circumvented and abandoned... and that's a problem on the S140 SD's side as it has virtually rendered itself incompatible with the android mainstream.

RE: Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

Aleksander Nowakowski — Mon, 17 Jul 2017 07:31:03 GMT

I saw you test on Huawei P10 with 7.0. In the newer versions of Android the writeDescriptor method uses hardcoded write type instead of parents characteristic, which is correct. But maybe they hardcoded it to a wrong type...? I'll try to search for the source code on AOSP.

RE: Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

Aleksander Nowakowski — Mon, 17 Jul 2017 07:25:02 GMT

Hi, so in my opinion this: github.com/.../BleManager.java should work. What phone are you testing it on? Write Type Default is the Write Request aka Write With Response. If this doesn't work... I don't thing anything can be done on Android. Just make sure you are writing the correct cccd, set your in its parents characteristic and check the correct sniffer log. Also, as endnode suggested, did you try nRF Connect? I think I'm doing there the same workaround (that would be a zong if I didn't).

RE: Dear Nordic Semi, please consider allowing CCCD descriptor write using... write?

endnode — Mon, 17 Jul 2017 05:59:25 GMT

Just for the sanity check what Nordic nRF Connect app does when you connect with it to GAP Peripheral, discover services and try manually enable some notifications? Does RF sniffer trace still show the same GATT Write method used and now event generated by S140?