Originally Posted By: DWallach
I've forwarded a link to this thread to a Google Android insider. Dunno if/when they can engineer a workaround, and whether or not that will help you with your Samsung phone, but I'd put my money on Google doing a workaround before I'd put my money on Honda doing a bug fix.


I really appreciate that. Right now, I'm anxious to find out if the missing UUID really is the likely cause or something else. For all I know it could be a search string syntax issue, e.g. none of the working traces use colons ":" in the search string.

In the interest of completeness, I'm attaching 3 new traces. These traces include the initial pairing process through to audio playback. One trace is for the Honda, the other two are for a Plantronics bluetooth headset and a Mercedes Benz OEM head unit. Only the Honda has the delay.

Thanks again,
Ruben


Attachments
btsnoop_hci_Honda_3sec_audio_delay.log (277 downloads)
btsnoop_hci_Mercedes_no_audio_delay.log (254 downloads)
btsnoop_hci_plantronics.log (244 downloads)