Comment 14 for bug 1941977

For comparison, I've attached these Android HCI snoop logs, taken when the same headset initiates a connection to an Android handset this time.

From ~22:00:50 UTC when the ACL was connected between them, one can see that the handset remains chill, allowing the headset to connect any profiles its heart desires. The headset happened to connect only HFP and A2DP signalling here, before going "silent". Then precisely 2s later, the handset accepts the responsibility of connecting the rest -- it connects A2DP media, while the headset then connects AVRCP (probably on some internal timeout).

Within 500ms, everything relevant had been connected and configured, and media streaming was underway, showing none of the issues I found with my PC.