04-20-2024, 02:38 PM
Holy, Moley, Bluetooth is chatty. Your trace is 2000+ lines. I just took a btmon trace of my own---Pixel 6a pairing with ~pre4 from scratch---and it's 1100+ lines.
I clearly see now how my first-time pairing results in a connection closely followed by a disconnection initiated by the Pixel, just as you saw
The difference is that I can now connect and stay connected with the Pixel?!?
I've replicated your btmon trace while trying to pair and connect my iPad. One thing I notice is that when the first connection is dropped, the iPad reverts to asking for a PIN code again whereas my Pixel silently connects.
I'm really out of my depth here and so far Internet searches have been frustrating. The 0x13 return code is pretty generic.
One whiff I caught is this response to a sensor developer on a TI forum "My suspicion here is that the Android stack is terminating the link because it doesn't like something about the notification that you sent." ... or not
Regards,
Kent
I clearly see now how my first-time pairing results in a connection closely followed by a disconnection initiated by the Pixel, just as you saw
Code:
< HCI Command: Disconnect (0x01|0x0006) plen 3 #108 [hci0] 27.788052
Handle: 12 Address: 0C:C4:13:D6:3A:36 (Google, Inc.)
Reason: Remote User Terminated Connection (0x13)The difference is that I can now connect and stay connected with the Pixel?!?
I've replicated your btmon trace while trying to pair and connect my iPad. One thing I notice is that when the first connection is dropped, the iPad reverts to asking for a PIN code again whereas my Pixel silently connects.
I'm really out of my depth here and so far Internet searches have been frustrating. The 0x13 return code is pretty generic.
One whiff I caught is this response to a sensor developer on a TI forum "My suspicion here is that the Android stack is terminating the link because it doesn't like something about the notification that you sent." ... or not
Regards,
Kent
