Unable to write CCCD descriptor with WRITE_TYPE_DEFAULT or WRITE_TYPE_NO_RESPONSE in androidhttps://devzone.nordicsemi.com/f/nordic-q-a/23459/unable-to-write-cccd-descriptor-with-write_type_default-or-write_type_no_response-in-androidHello, a quick rundown on the problem here: New versions of Softdevices S140 corrected an error and now correctly ignores writing to cccd descriptor using write instead of write request. According to an individual ( Possibly a Nordicen-USTelligent Community 13Mon, 17 Jul 2017 11:27:45 GMTRE: Unable to write CCCD descriptor with WRITE_TYPE_DEFAULT or WRITE_TYPE_NO_RESPONSE in androidhttps://devzone.nordicsemi.com/thread/92162?ContentTypeID=1Mon, 17 Jul 2017 11:27:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:82a6bf64-2dfa-4131-84e0-49a2c87767dfHung Bui<p>@Mitch: Please use wireshark v1.10</p><div style="clear:both;"></div>RE: Unable to write CCCD descriptor with WRITE_TYPE_DEFAULT or WRITE_TYPE_NO_RESPONSE in androidhttps://devzone.nordicsemi.com/thread/92161?ContentTypeID=1Fri, 14 Jul 2017 09:22:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:477d4c46-cd04-4d24-91d9-efe8a24e5e22Mitch996<p>@Hung Bui</p> <p>Hello, I&#39;m working on it, but got stuck on filtering pdu packets, the btle.lendgth !=0 doesn&#39;t work in wireshark 1.12.7</p><div style="clear:both;"></div>RE: Unable to write CCCD descriptor with WRITE_TYPE_DEFAULT or WRITE_TYPE_NO_RESPONSE in androidhttps://devzone.nordicsemi.com/thread/92160?ContentTypeID=1Fri, 14 Jul 2017 09:21:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d4297e5b-5907-4a44-bb1e-00693ba905a7Mitch996<p>@endnode</p> <blockquote> <p>Btw. you aren&#39;t using BT LE Security Manager layer for any kind of pairing and bonding, are you?</p> </blockquote> <p>I think not... because I don&#39;t even know what they are... and the Android program worked on nrf51 before...</p><div style="clear:both;"></div>RE: Unable to write CCCD descriptor with WRITE_TYPE_DEFAULT or WRITE_TYPE_NO_RESPONSE in androidhttps://devzone.nordicsemi.com/thread/92163?ContentTypeID=1Thu, 13 Jul 2017 14:25:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f4611219-5ff4-42e1-a880-9a7896d56482Hung Bui<p>@Mitch: Have you tried nRFConnect to test ? Which phone did you use for testing ? I agree with endnode , a sniffer trace will help.</p><div style="clear:both;"></div>RE: Unable to write CCCD descriptor with WRITE_TYPE_DEFAULT or WRITE_TYPE_NO_RESPONSE in androidhttps://devzone.nordicsemi.com/thread/92158?ContentTypeID=1Thu, 13 Jul 2017 06:35:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8817929f-3d94-4a94-ac81-58d498ab4624endnode<p>You won&#39;t know without seeing what is exchanged over the radio. You are trying some Android APIs but do you know what they do over the air? And that&#39;s the only thing which counts. Btw. you aren&#39;t using BT LE Security Manager layer for any kind of pairing and bonding, are you?</p><div style="clear:both;"></div>RE: Unable to write CCCD descriptor with WRITE_TYPE_DEFAULT or WRITE_TYPE_NO_RESPONSE in androidhttps://devzone.nordicsemi.com/thread/92159?ContentTypeID=1Thu, 13 Jul 2017 01:12:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2312dea3-5ccc-4908-b2f3-50be1cd37f22Mitch996<p>On it... But I got make sure I know what the is going on first.</p><div style="clear:both;"></div>RE: Unable to write CCCD descriptor with WRITE_TYPE_DEFAULT or WRITE_TYPE_NO_RESPONSE in androidhttps://devzone.nordicsemi.com/thread/92164?ContentTypeID=1Wed, 12 Jul 2017 14:22:26 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0e727f56-fc33-4c50-a576-8ee11f67c2deendnode<p>Get a BLE RF sniffer trace...</p><div style="clear:both;"></div>