Does LECC falls within somebody's expertise? This is a bug and would affect working of all BLE systems: We and have found this scenario which seems like a bug: Once an LECC fails to connect with a BLE device, the device must advertise to enable LECC to connect to another BLE device 1. Consider: Two devices BLE1 is OFF, BLE2 is advertising 2. hcitool lecc BLE1 fails since BLE is OFF Example: > hcitool lecc 00:07:80:C0:68:C7 Could not create connection: Connection timed out At this stage hcitool lecc will NOT connect to any BLE device until BLE1 advertises again. 4. hcitool lecc BLE2 fails Example: > hcitool lecc 00:07:80:C0:70:24 Could not create connection: Connection timed out BLE1 starts to advertise - now LECC would connect to BLE2 or anther device 5. hcitool lecc BLE2 connects Example: > hcitool lecc 00:07:80:C0:70:24 Connection handle 65 Seems BLE driver maintains a LECC failed connection and is not able to LE Connect to another device until the failed device advertises. A weird error and holding us from gating a product release. Easy to reproduce - takes 2 devices and only a few minutes. I appreciate your help in looking at this and give us a solution or a work around. Regards, Sanjay -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
