This repository was archived by the owner on Jul 31, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 63
This repository was archived by the owner on Jul 31, 2025. It is now read-only.
Stuck at connectAndSetup #12
Copy link
Copy link
Open
Labels
Description
Sometimes, there is no callback from connectAndSetup.
Then If I try to disconnect() and call connectAndSetup() again, It will hit the callback twice.
If we could have something, that either cancels a connectAndSetup callback, or much cleaner, if we could have the callback hit at all times.
Hci dump when the connectAndSetup is stuck
HCI Event: Command Complete (0x0e) plen 4
LE Set Scan Enable (0x08|0x000c) ncmd 1
status 0x0c
Error: Command Disallowed
< HCI Command: LE Create Connection (0x08|0x000d) plen 25
bdaddr 00:1E:C0:24:C7:2A type 0
interval 96 window 48 initiator_filter 0
own_bdaddr_type 0 min_interval 6 max_interval 12
latency 0 supervision_to 200 min_ce 4 max_ce 6
> HCI Event: Command Status (0x0f) plen 4
LE Create Connection (0x08|0x000d) status 0x00 ncmd 1
> HCI Event: LE Meta Event (0x3e) plen 19
LE Connection Complete
status 0x00 handle 64, role master
bdaddr 00:1E:C0:24:C7:2A (Public)
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2
> HCI Event: Command Status (0x0f) plen 4
LE Read Remote Used Features (0x08|0x0016) status 0x00 ncmd 1
> HCI Event: LE Meta Event (0x3e) plen 12
LE Read Remote Used Features Complete
status 0x3e handle 64
Error: Connection Failed to be Established
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 64 reason 0x3e
Reason: Connection Failed to be Established
< ACL data: handle 64 flags 0x00 dlen 7
ATT: MTU req (0x02)
client rx mtu 256
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 64 packets 1