No AVDTP in Bluetooth HCI trace with LDAC audio

asked 2021-01-11 00:12:21 +0000

dandreye gravatar image

updated 2021-01-26 15:43:46 +0000

Hi All,

Is it normal notto see any AVDTP packets in a Bluetooth HCI trace with a successful LDAC audio codec negotiation and a bit of audio? Here's the trace in question (with a session between Samsung SM-A320FL running Android 8 Oreo and a Bluetooth DAC with CSR8675 chip - they both support BLE): https://drive.google.com/file/d/1zUte...

I can see a lot of some Vendor Commands in it, just wondering if there are any issues decoding AVDTP in case of BLE..

Many thanks in advance!

edit retag flag offensive close merge delete

Comments

@Guy Harris: Would it be possible to confirm if we have full BLE decoding support in recent Wireshark versions?

dandreye gravatar imagedandreye ( 2021-01-26 15:41:49 +0000 )edit

Would it be possible to confirm if we havefull BLE decoding support in recent Wireshark versions?

Yes, it would be possible for somebody to confirm that, by reading the dissector and the specs.

Guy Harris gravatar imageGuy Harris ( 2021-01-27 02:04:43 +0000 )edit

I was just looking at packet #910 with "Vendor Command 0x0154 (opcode 0xFD54)" (one of those with vendor commands) and thinking perhaps vendor stuff is just not dissected yet.

dandreye gravatar imagedandreye ( 2021-01-27 12:28:27 +0000 )edit

Update: looks like AVDTP/A2DP traffic is not captured with the "Take Bug Report" feature in Developer Options of the smartphone as apparently it's there in Wireshark running on an Ubuntu18-based A2DP sink.

dandreye gravatar imagedandreye ( 2021-02-10 17:49:17 +0000 )edit
add a comment