Bug 207625 - avrcp: Cannot connect Sennheiser Momentum True Wireless 2
Summary: avrcp: Cannot connect Sennheiser Momentum True Wireless 2
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-08 10:40 UTC by Andrey Semashev
Modified: 2020-05-31 20:07 UTC (History)
0 users

See Also:
Kernel Version: 5.4.0
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Packet dump of the failed connection attempt on Linux (32.70 KB, application/x-pcapng)
2020-05-08 10:40 UTC, Andrey Semashev
Details
Another failed connection attempt on Linux, in btsnoop format (12.12 KB, application/octet-stream)
2020-05-08 10:42 UTC, Andrey Semashev
Details
Packet dump of a successful connect on Windows. Use Decode As -> Bluetooth in Wireshark. (17.05 KB, application/x-pcapng)
2020-05-08 10:44 UTC, Andrey Semashev
Details

Description Andrey Semashev 2020-05-08 10:40:49 UTC
Created attachment 289003 [details]
Packet dump of the failed connection attempt on Linux

I have a problem connecting Sennheiser Momentum True Wireless 2 headset over Bluetooth. The headset says "Connected" and then reboots immediately after. After reboot the headset says "Power on" and tries connecting again, and fails the same way, and so on.

From the Bluetooth packet dump it looks like the problem happens after bluetoothd sends AVRCP ListPlayerApplicationSettingAttributes message to the headset. The headset sends Not Implemented response and then reboots. In the response Wireshark shows warnings about encoding issues.

I'm attaching a packet dump captured from one of the connection attempts. The ListPlayerApplicationSettingAttributes message is in packet 262 and the response is in packet 264.

This is on Kubuntu 20.04. I tried bluez 5.53 from Kubuntu and revision 3146b7a0785758be2d4e894d44e99d29c0db983e from git master - the behavior is the same.

I've also verified that the headset does work on Windows 10. On that system, ListPlayerApplicationSettingAttributes is not present in the packet exchange.

Also, the headset does connect if AVRCP is disabled by adding --noplugin=avrcp to bluetoothd command line.
Comment 1 Andrey Semashev 2020-05-08 10:42:10 UTC
Created attachment 289005 [details]
Another failed connection attempt on Linux, in btsnoop format
Comment 2 Andrey Semashev 2020-05-08 10:44:00 UTC
Created attachment 289007 [details]
Packet dump of a successful connect on Windows. Use Decode As -> Bluetooth in Wireshark.
Comment 3 Andrey Semashev 2020-05-08 10:47:48 UTC
For the record, the problem happens with headset firmware versions 4.5.0 and 4.6.0 (which is currently the latest one).
Comment 4 Andrey Semashev 2020-05-31 20:07:59 UTC
Should be fixed by bluez commits b7fe84c4582a54e098c0f52500d0ed7396026d05 and ba91d0ad7379fc7b064af911229e50ffa1a16169.

Note You need to log in before you can comment on or make changes to this bug.