Is setting CCCD enabled by default allowed by BT SIG?

RE: Is setting CCCD enabled by default allowed by BT SIG?

ovrebekk — Tue, 19 Oct 2021 09:11:16 GMT

As I said we can't recommend anyone break the specification. Even if you pass compliance testing today the test might be changed in the future to check this specifically.

It is also hard to know how different clients (the phone in your case) will respond to receiving notifications when they haven't been properly enabled from their side.

If the phone is failing to enable the CCCD I believe that is the problem that needs investigating.

Best regards
Torbjørn

RE: Is setting CCCD enabled by default allowed by BT SIG?

jeffdev3 — Mon, 18 Oct 2021 16:06:49 GMT

I am enabling CCCD every time after connection right now but I want to reduce the packets being transferred and eliminate some of the occasional problems on the phone side failing to enable CCCD. My device bonds to the phone but it seems Android and iOS does not enforce the BT spec feature that CCCD state for bonded devices are saved. I have seen Android phones enabling CCCD by default on the service changed characteristic also because it is sending the indication to my device in certain cases when I never enabled it.

RE: Is setting CCCD enabled by default allowed by BT SIG?

ovrebekk — Mon, 18 Oct 2021 08:23:08 GMT

[quote user=""]Will there be any problem qualifying my product if I enable CCCD by default on a custom service and characteristic?[/quote]

Custom services are not validated by qualification tests, so you will most likely get through qualification, but you would still be breaking the specification so it is obviously not something we would recommend.

Is there any particular reason you can't just have the client write this value after connection establishment?

Best regards
Torbjørn