I think I have to clarify that I have used the word BLE for the hardware, while I now have realized that most people mean different protocols of BLE software. I found this document Bluetooth Low Energy (BLE): A Complete Guide
with this text:
Advantages of BLE
Prevalence in smartphones
"This is probably the biggest advantage BLE has over its competitors, such as ZigBee, Z-Wave, and Thread. The vast majority of people in the world own a smartphone, and almost all of those smartphones have BLE hardware inside. This gives developers a much larger potential user base for their applications.”
Earlier this year I thought the problem was that Samsung and Oticon used the same micro circuits from the same faulty batch. How likely is that??
When my Samsung dealer told me, if I come back a third time with a faulty BLE, they will give me the money back. The advice was to look for a fault in the HA.
Then I made a summary of events:
ConnectClip 1 worked for eleven months with FW 1.1.1
After loading FW 1.4.1 ConnectClip stopped working after one month.
ConnectClip 2 was faulty on delivery, re-cycled.
Here between I got the updated FW 1.4.2.
ConnectClip 3 went faulty after 30 days.
Samsung Galaxy S22 faulty after tree weeks.
Samsung Galaxy S23 faulty after two months.
That’s why I am asking if a faulty setting in any BLE protocol can get the phone respectively the ClipConnect to “burn” its own BLE circuit. We do not believe there are enough power in the HA battery to “burn” the circuits.