Bug 75351 - Can't connect to AD2P profiles of some bluetooth headsets
Summary: Can't connect to AD2P profiles of some bluetooth headsets
Status: NEW
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: 2014-05-03 08:24 UTC by Marcin Stefański
Modified: 2014-07-26 20:45 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Marcin Stefański 2014-05-03 08:24:00 UTC 
There seems to be a problem connecting with AD2P profile of some bluetooth headsets.

kernel: [ 2013.010319] Bluetooth: re-auth of legacy device is not possible.
bluetoothd[716]: Protocol not supported (93)

Some of the devices affected: Motorola S805 BT, Medion MD86751

This bug was originally discovered here:

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1283003?comments=all
Comment 1 Sander van Grieken 2014-07-03 10:58:15 UTC 
Likely related:

https://lists.debian.org/debian-kernel/2014/02/msg00235.html

This is a HSP profile headset, not a A2DP one. Also the first kernel the problem manifests is 3.12
Comment 2 Johan Hedberg 2014-07-03 12:39:24 UTC 
"Bluetooth: re-auth of legacy device is not possible." sounds like a kernel bug that was fixed quite recently. It'd be good if you could check with the latest bluetooth-next kernel whether the problem persists (however I do think the patch has already made it to latest 3.16-rc release as well).
Comment 3 Sander van Grieken 2014-07-03 15:14:29 UTC 
No, just tried a build of bluetooth-next master, but it does not work.
There's no entries like re-auth or protocol not supported appearing in the log though.
Comment 4 Nadia Yvette Chambers 2014-07-26 20:45:53 UTC 
This used to break in Ubuntu's 3.11.0-12 with a Logitech h800 for me, but is now confirmed to work with the same Logitech h800 on 3.16.0-rc6.
Note You need to log in before you can comment on or make changes to this bug.