2015-12-28 11:48:57

by Martin Kjær Jørgensen

[permalink] [raw]
Subject: Bose AE2 SoundLink issues

I'm having trouble "completing" the pairing with my Bose SoundLink
around-ear wireless headphones II (AE2) and Thinkpad X1, running
Debian stretch (testing/sid)

Let me start by stating that the headphones works flawlessly with my
Android 5 smartphone, both sound and the buttons on the headphones.

When pairing with the smartphone the pairing procedure makes the
bluetooth led on the headphones blink first blue, then white, shortly,
then flashing contant white, and the voice in the headphones says
"Connected to <name-of-the-smartphone>". According to Android, the
headphones are used for: "Phone audio", "Media audio", and
"Contact sharing (pbap server)".



Now on to the laptop. Status from bluetooth.service:

bluetoothd[811]: Not enough free handles to register service
bluetoothd[811]: Not enough free handles to register service
bluetoothd[811]: Current Time Service could not be registered
bluetoothd[811]: gatt-time-server: Input/output error (5)
bluetoothd[811]: Not enough free handles to register service
bluetoothd[811]: Not enough free handles to register service
bluetoothd[811]: Sap driver initialization failed.
bluetoothd[811]: sap-server: Operation not permitted (1)

Using only bluetoothctl (no desktop environment), I can discover the
device, see it's UUID's:

[NEW] Device 08:DF:1F:52:58:A0 Bose AE2 SoundLink
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 0000110d-0000-1000-8000-00805f9b34fb
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 0000110f-0000-1000-8000-00805f9b34fb
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 00001130-0000-1000-8000-00805f9b34fb
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 0000112e-0000-1000-8000-00805f9b34fb
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 00001131-0000-1000-8000-00805f9b34fb
[CHG] Device 08:DF:1F:52:58:A0 UUIDs: 0000febe-0000-1000-8000-00805f9b34fb

Pairing with the headphones, after setting the headphones in pairing
mode and a voice in the headphones says "Ready to pair", using:

pair 08:DF:1F:52:58:A0

... makes the kernel produce:

[19186.946754] Bluetooth: SMP security requested but not available

... and the bluetooth.service produce:

bluetoothd[811]: Unable to register GATT service with handle 0x0001 for device 08:DF:1F:52:58:A0
bluetoothd[811]: Unable to register GATT service with handle 0x0001 for device 08:DF:1F:52:58:A0

bluetoothctl lists the headphones as paired, and the prompt on changes
to the name of the device from "[bluetooth]#". The headphones
bluetooth led changes from blinking blue to blinking white, but never
stops blinking white, and no sound devices gets added to ALSA or pulseaudio.


Maybe the headphones requires some features of my OS? Maybe it
discovers for the "pbap server" on my laptop, or something? Maybe
Bluetooth LE SMP issues?

I'm willing to test, analyse more, or otherwise aid in the development if
anything if it's required.

/Martin



2016-02-14 11:39:49

by Martin Kjær Jørgensen

[permalink] [raw]
Subject: Re: Bose AE2 SoundLink issues

On søn, feb 14 2016, Emanuele Cozzi <[email protected]> wrote:

I should say first that I use pulseaudio as the A2DP source for
bluez, and pavucontrol to manage pulseaudio card profiles.

The profiles of Bose AE2 on my machine are "Off", "Headset Head Unit
(HSP/HFP)", "High Fidelity Playback (A2DP Sink)". I'm using A2DP by
default and selecting HSP/HFP doesnt trigger anything noticable. Audio
still gets transmittet with no clicks or pauses, and no voice in the
headset says anything.

I believe A2DP and HSP/HFP should be mutually exclusive because A2DP is
one way (from laptop to headset). HSP/HFP is two-way, so you can
listen and record audio simultaneously. I believe A2DP use different
codecs as well, but I'm not sure.

You too.

> Hi Martin,
>
> thank you for having solved this issue. My lack of full knowledge in the bluetooth stack would have never brought me so far in such a short time.
>
> One last question. I noticed that in this way, I can't select both telephony and a2dp profiles at the same moment but they are mutually exclusive. Basically I can assign only 1
> profile at time to the headset. Moreover, I noticed that the telephony profile somehow conflicts: if selected, every few secs the Bose starts announcing "Call from". Are you in the
> same situation?
>
> Have a great day! 
>
> Emanuele
>
> Il giorno dom 14 feb 2016 alle ore 11:56 Martin Kjær Jørgensen <[email protected]> ha scritto:
>
> On lør, feb 13 2016, Emanuele Cozzi <[email protected]> wrote:
>
> > Hi, 
> >
> > I was digging around to look for some info about the pairing issues there might be with the Bose AE2 SoundLink, and I found your email on the linux-bluetooth list (
> > http://article.gmane.org/gmane.linux.bluez.kernel/66210/match=bose+ae2).
> >
> > The same situation here. My personal laptop with Ubuntu Gnome 15.10, kernel 4.2.0, bluez 5.35 and all the pulseaudio related modules shows the same symptoms and logs of
> yours.
> >
> > I read that one of your guesses was the SMP security service. Few days ago I tried to disable SMP with hcitool but with no luck...
> > At the moment I'm pretty sure there is something wrong with the GATT service because every time I connect the headphones, the bluetooth daemon logs: "Unable to register GATT
> > service with handle 0x0001 for device ..."
> >
> > On the other side I have no issues with my bluetooth speakers, thus there should be some kind of incompatibility with our Bose.
> >
> > Concluding, I'm writing this e-mail both to share with you my experience but also to check if you made some progresses in the meanwhile.
> >
> > Sorry for this incursion!
> >
> > Cheers,
> >
> > Emanuele 
> > --
> >
> > Emanuele Cozzi
>
> I've tried repost an answer to the list. Apparently it didnt get
> posted. The answerer suggested that BLE conflicts with the pairing, so
> enforcing BR/EDR seems to fixit. So my main.conf ends up looking like this:
>
> [General]
> Name = mkjlap
> Class = 0x000100
> PairableTimeout = 0
> DiscoverableTimeout = 0
> # MKJ: bredr seems to be needed for Bose AE2 pairing
> ControllerMode = bredr
> MultiProfile = multiple
> FastConnectable = true
> AutoEnable = true
>
> --
>
> Emanuele Cozzi