[Bluez-devel] SCO flowcontrol patch v4.4 on 2.6.25/6 causes hardlocks when connecting to BT device

[Bluez-devel] SCO flowcontrol patch v4.4 on 2.6.25/6 causes hardlocks when connecting to BT device

[martin f krafft]

[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]

also sprach martin f krafft <madduck@madduck.net> [2008.04.11.0932 +0200]:
> I have just compiled a Debian 2.6.24 with the v4.4 patch: it applied
> and compiled cleanly.
> 
> And it works most of the time with my BT500v headset (sco)! Thank
> you for that.

So I used to have a working Bluetooth setup with 2.6.24, and it also
still works. However, the kernel developers have moved on, and even
though the sco-flowcontrol v4.4 patch applies to 2.6.25/6 as well
[0], the resulting 2.6.25 and 2.6.26 kernels both freeze hard when
I try to connect to the headset.

0. http://bugs.debian.org/493098

Does anyone have an idea what could be going on? How can I help
debug this? Is there a newer patch floating around somewhere?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"we did rate the microsoft security researcher as
 less-bad than the people who prepare the carcasses for dissection in
 biology laboratories."
             -- michael moyer, executive editor of _popular science_
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #1.2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO flowcontrol patch v4.4 on 2.6.25/6 causes hardlocks when connecting to BT device

[Marcel Holtmann]

Hi Martin,

> > I have just compiled a Debian 2.6.24 with the v4.4 patch: it applied
> > and compiled cleanly.
> > 
> > And it works most of the time with my BT500v headset (sco)! Thank
> > you for that.
> 
> So I used to have a working Bluetooth setup with 2.6.24, and it also
> still works. However, the kernel developers have moved on, and even
> though the sco-flowcontrol v4.4 patch applies to 2.6.25/6 as well
> [0], the resulting 2.6.25 and 2.6.26 kernels both freeze hard when
> I try to connect to the headset.
> 
> 0. http://bugs.debian.org/493098
> 
> Does anyone have an idea what could be going on? How can I help
> debug this? Is there a newer patch floating around somewhere?

what about not using that patch at all? I am using the new audio
interface without that patch. And you wanna use the btusb driver and
since 2.6.27-rc4 that one actually has SCO support.

Regards

Marcel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) hardlocks when connecting to BT device

[martin f krafft]

[-- Attachment #1.1: Type: text/plain, Size: 1461 bytes --]

also sprach Marcel Holtmann <marcel@holtmann.org> [2008.08.22.0933 +0100]:
> what about not using that patch at all? I am using the new audio
> interface without that patch. And you wanna use the btusb driver
> and since 2.6.27-rc4 that one actually has SCO support.

If I had known... :)

Unfortunately, I have not yet succeeded. I modprobed 'sco' and then
ran headsetd as before, but that just prints

  headsetd[9417]: Bluetooth headset daemon version 0.5
  headsetd[9417]: Configuration phase ended: target bdaddr is 00:1A:45:14:EE:D7, timeout is 90000 ms
  headsetd[9417]: Changing state: Idle-->Paging
  headsetd[9417]: Changing state: Paging-->Connecting
  headsetd[9417]: Changing state: Connecting-->Ready
  headsetd[9417]: Changing state: Ready-->Opening

At this point, the headset makes the sound it makes when
a connection is established, but there is no sound coming from it.

After about 40 seconds, the client says:

  aplay: main:564: audio open error: Connection timed out

and headsetd writes:

  headsetd[9417]: unable to open SCO channel to headset: Connection timed out
  headsetd[9417]: Changing state: Opening-->ZombieAppl
  headsetd[9417]: Appli closed socket
  headsetd[9417]: Changing state: ZombieAppl-->Idle

So something's still broken... :(

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
never underestimate the power of human stupidity.
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #1.2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) hardlocks when connecting to BT device

[Marcel Holtmann]

Hi Martin,

>> what about not using that patch at all? I am using the new audio
>> interface without that patch. And you wanna use the btusb driver
>> and since 2.6.27-rc4 that one actually has SCO support.
>
> If I had known... :)
>
> Unfortunately, I have not yet succeeded. I modprobed 'sco' and then
> ran headsetd as before, but that just prints
>
>  headsetd[9417]: Bluetooth headset daemon version 0.5
>  headsetd[9417]: Configuration phase ended: target bdaddr is 00:1A: 
> 45:14:EE:D7, timeout is 90000 ms
>  headsetd[9417]: Changing state: Idle-->Paging
>  headsetd[9417]: Changing state: Paging-->Connecting
>  headsetd[9417]: Changing state: Connecting-->Ready
>  headsetd[9417]: Changing state: Ready-->Opening

don't use headsetd. Use the audio stuff that comes with bluez-utils.

Regards

Marcel


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) hardlocks when connecting to BT device

[martin f krafft]

[-- Attachment #1.1: Type: text/plain, Size: 540 bytes --]

also sprach Marcel Holtmann <marcel@holtmann.org> [2008.08.26.1819 +0100]:
> don't use headsetd. Use the audio stuff that comes with
> bluez-utils.

The dbus API documented at /usr/share/doc/bluez-utils/audio-api.txt?
How would I make existing applications speak to that?

Sorry, but dpkg -L bluez-utils (3.36-1) doesn't list anything else
audio-related. Is the version outdated?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
a farmer is a man outstanding in his field.
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #1.2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) hardlocks when connecting to BT device

[Marcel Holtmann]

Hi Martin,

>> don't use headsetd. Use the audio stuff that comes with
>> bluez-utils.
>
> The dbus API documented at /usr/share/doc/bluez-utils/audio-api.txt?
> How would I make existing applications speak to that?
>
> Sorry, but dpkg -L bluez-utils (3.36-1) doesn't list anything else
> audio-related. Is the version outdated?

you don't have to. The bluez-utils-3.36 comes with an audio plugin  
that does all this for you. You just have to add 4 magic lines  
into .asoundrc. See wiki.bluez.org for these for it.

We have native support for ALSA and GStreamer with the audio plugin  
and it can either use the headset profile or A2DP. And native  
PulseAudio support is in the making :)

Regards

Marcel


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) hardlocks when connecting to BT device

[martin f krafft]

[-- Attachment #1.1: Type: text/plain, Size: 1644 bytes --]

also sprach Marcel Holtmann <marcel@holtmann.org> [2008.08.27.0618 +0100]:
> you don't have to. The bluez-utils-3.36 comes with an audio plugin
> that does all this for you. You just have to add 4 magic lines
> into .asoundrc. See wiki.bluez.org for these for it.

So I added

pcm.bluetooth {
   type bluetooth
   device 00:1A:45:14:EE:D7
}

to .asoundrc and if I try to play something with aplay, I am told that

  Playing WAVE '/usr/share/twinkle/ringback.wav' : Unsigned 8 bit,
  Rate 8287 Hz, Mono aplay: set_params:918: Sample format non
  available

Trying to use the device with twinkle, the programme starts up
taking ages trying to connect (http://bugs.debian.org/475962) and
eventually just says that it cannot access the speaker/microphone.
When twinkle tries to talk to the headset, the bluetooth LED starts
to blink, the headset makes the
noise it makes when a connection is established, and after a while,
twinkle tells me

  snd_pcm_hw_params failed: Invalid argument

and then

  snd_pcm_hw_params failed: Input/output error

The bluetooth LED continues blinking and the headset will not make
the disconnection sound until I turn bluetooth off. Once I turn it
back on, the headset disconnects, and the cycle repeats.

I am using 2.6.27-rc4 and bluez-utils 3.36-1.

Any ideas what may be wrong?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"it isn't pollution that's harming the environment.
 it's the impurities in our air and water that are doing it." 
                                                          - dan quayle
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #1.2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset (was: btusb+sco failing to play sound through Jabra BT500v headset)

[martin f krafft]

[-- Attachment #1.1: Type: text/plain, Size: 1643 bytes --]

also sprach Marcel Holtmann <marcel@holtmann.org> [2008.08.26.1819 +0100]:
> don't use headsetd. Use the audio stuff that comes with bluez-utils.

So I am trying, and I got a little further, installing the right
lines into .asoundrc as per
http://wiki.bluez.org/wiki/HOWTO/AudioDevices. I have gotten beyond
issues of

  bt_audio_service_open: connect() failed: Connection refused (111)
  aplay: main:564: audio open error: Connection refused 

but it still doesn't want to work. If I execute

  arecord -D bt500v -f S16_LE | aplay -D bt500v -f S16_LE

then the headset makes a noise, the bluetooth LED flashes and
arecord prints

  Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono

But then after about 30 or 40 seconds, it all fails:

  ALSA lib pcm_bluetooth.c:464:(bluetooth_hsp_hw_params) BT_SETCONFIGURATION failed : Input/output error(5)
  arecord: set_params:979: Unable to install hw params:
  ACCESS:  RW_INTERLEAVED
  FORMAT:  S16_LE
  SUBFORMAT:  STD
  SAMPLE_BITS: 16
  FRAME_BITS: 16
  CHANNELS: 1
  RATE: 8000
  PERIOD_TIME: 125000
  PERIOD_SIZE: 1000
  PERIOD_BYTES: 2000
  PERIODS: 4
  BUFFER_TIME: 500000
  BUFFER_SIZE: 4000
  BUFFER_BYTES: 8000
  TICK_TIME: [0 0]
  aplay: playback:2019: read error

I have bluez-audio installed, but /etc/bluetooth/audio.conf is
default. No PulseAudio or anything other than plain ALSA here...

Any clues?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"alas, i am dying beyond my means."
                                                        -- oscar wilde
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #1.2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset (was: btusb+sco failing to play sound through Jabra BT500v headset)

[Marcel Holtmann]

Hi Martin,

> > don't use headsetd. Use the audio stuff that comes with bluez-utils.
> 
> So I am trying, and I got a little further, installing the right
> lines into .asoundrc as per
> http://wiki.bluez.org/wiki/HOWTO/AudioDevices. I have gotten beyond
> issues of
> 
>   bt_audio_service_open: connect() failed: Connection refused (111)
>   aplay: main:564: audio open error: Connection refused 
> 
> but it still doesn't want to work. If I execute
> 
>   arecord -D bt500v -f S16_LE | aplay -D bt500v -f S16_LE
> 
> then the headset makes a noise, the bluetooth LED flashes and
> arecord prints
> 
>   Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono
> 
> But then after about 30 or 40 seconds, it all fails:
> 
>   ALSA lib pcm_bluetooth.c:464:(bluetooth_hsp_hw_params) BT_SETCONFIGURATION failed : Input/output error(5)
>   arecord: set_params:979: Unable to install hw params:
>   ACCESS:  RW_INTERLEAVED
>   FORMAT:  S16_LE
>   SUBFORMAT:  STD
>   SAMPLE_BITS: 16
>   FRAME_BITS: 16
>   CHANNELS: 1
>   RATE: 8000
>   PERIOD_TIME: 125000
>   PERIOD_SIZE: 1000
>   PERIOD_BYTES: 2000
>   PERIODS: 4
>   BUFFER_TIME: 500000
>   BUFFER_SIZE: 4000
>   BUFFER_BYTES: 8000
>   TICK_TIME: [0 0]
>   aplay: playback:2019: read error
> 
> I have bluez-audio installed, but /etc/bluetooth/audio.conf is
> default. No PulseAudio or anything other than plain ALSA here...
> 
> Any clues?

actually I have none. It simply works for me. And I have tested it a
lot. There are some rare conditions where the btusb driver is off on the
16-bit boundaries, but I am looking at a fix for it. However this will
not disturb the audio service. You just don't here anything.

Regards

Marcel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset (was: btusb+sco failing to play sound through Jabra BT500v headset)

[martin f krafft]

[-- Attachment #1.1: Type: text/plain, Size: 625 bytes --]

also sprach Marcel Holtmann <marcel@holtmann.org> [2008.09.05.1800 +0100]:
> actually I have none. It simply works for me. And I have tested it a
> lot. There are some rare conditions where the btusb driver is off on the
> 16-bit boundaries, but I am looking at a fix for it. However this will
> not disturb the audio service. You just don't here anything.

Where should we go from here? How can I help debug this?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
no cat has eight tails.
a cat has one tail more than no cat.
therefore, a cat has nine tails.
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #1.2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset

[martin f krafft]

[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]

also sprach Marcel Holtmann <marcel@holtmann.org> [2008.09.05.1900 +0200]:
> actually I have none. It simply works for me. And I have tested it a
> lot. There are some rare conditions where the btusb driver is off on the
> 16-bit boundaries, but I am looking at a fix for it. However this will
> not disturb the audio service. You just don't here anything.

Ported original thread from SF list:
  http://article.gmane.org/gmane.linux.bluez.devel/16060

I can reproduce the exact same error with a BT250 hooked up via
a different bluetooth adapter to an amd64 machine this time (the
last one was i386), running 2.6.26.

Stuart Pook told me about bluez-utils 4.4 [0] - I am still using 3.36
[1], but the wiki page says that I need 3.16 or newer. Would
I have better luck with 4.4? Where does this stuff come in anyway?
I am running hcid in the background, but I know too little about
ALSA or Bluetooth to be able to see how the two interlink. The wiki
mentions a btaudiod, which 3.36 seems not to have. Is that needed?

0. http://article.gmane.org/gmane.linux.bluez.devel/16113
1. http://bugs.debian.org/499529

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"sometimes the urge to do bad is nearly overpowering"
                                                          -- ben horne
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset

[Stuart Pook]

On 23/09/08 15:00, martin f krafft wrote:
> I can reproduce the exact same error with a BT250 hooked up via
> a different bluetooth adapter to an amd64 machine this time (the
> last one was i386), running 2.6.26.

I as said on http://bugzilla.kernel.org/show_bug.cgi?id=11514 aplay and 
my JX10 headset work with bluez-4.4 and linux 2.6.26. I only get the 
"unable to install hw params" error on 2.6.27-rc5.

> Stuart Pook told me about bluez-utils 4.4 [0] - I am still using 3.36
> [1], but the wiki page says that I need 3.16 or newer. Would
> I have better luck with 4.4? Where does this stuff come in anyway?

I would suggest using bluez-4.x and checking that your headset works 
with a 2.6.26 kernel. Note don't use SCO headsets and linux 2.6.26 for 
too long as using SCO and the old hci_usb driver will cause your machine 
to hard crash sooner or later. The new btusb driver gained SCO support 
in 2.6.27-rc4.

> I am running hcid in the background, but I know too little about
> ALSA or Bluetooth to be able to see how the two interlink. The wiki
> mentions a btaudiod, which 3.36 seems not to have. Is that needed?

I don't remember btaudiob. Bluetoothd has replaced hcid. If you run 
"bluetoothd -d -n" you will see that aplay (via the bluetooth alsa 
libraries) contacts bluetoothd and that it is bluetoothd that connects 
to the headset (at least that is how I understand things).

Be careful when you install bluez-4.x that you replace the alsa 
bluetooth libraries that aplay uses. I can tell you more about this if 
required.

I have added hcidump -XV dumps of the communication between my machine 
and my JX10 headset using 2.6.27-rc5 to the bug report mentioned above. 
Tomorrow I'll add hcidump -XV using 2.6.26 so that we can see the 
differences.

Stuart

SCO headset, bluez-4.9 & linux 2.6.27-rc7 -> Unable to install hw params

[Stuart Pook]

Hi

I've installed bluez 4.9 and linux kernel 2.6.27-rc7 and I still cannot get any
sound out of my Jabra JX10 bluetooth headset connected via a Cambridge Silicon
Radio Bluetooth Dongle (0a12:0001). Bluetoothd says "connect: Operation
not permitted" and aplay "Unable to install hw params".

What should I try next? I think that I'm missing something stupid.

thanks for any help (or requests for more information)

Stuart

PS BTW, if use bluez 4.4 & linux 2.6.26, aplay works, if I use bluez 4.7 and
linux 2.6.26, aplay fails.

Bluetoothd says

bluetoothd[24162]: Accepted new client connection on unix socket (fd=23)
bluetoothd[24162]: Audio API: received BT_GETCAPABILITIES_REQ
bluetoothd[24162]: Audio API: sending BT_GETCAPABILITIES_RSP
bluetoothd[24162]: Audio API: received BT_SETCONFIGURATION_REQ
bluetoothd[24162]: config sco - device = 00:1A:45:2F:49:98 access_mode = 2
bluetoothd[24162]: /org/bluez/hci0/dev_00_1A_45_2F_49_98: Connecting to 00:1A:45:2F:49:98 channel 1
bluetoothd[24162]: State changed /org/bluez/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
bluetoothd[24162]: adapter_get_device(00:1A:45:2F:49:98)
bluetoothd[24162]: link_key_request (sba=00:0C:41:E1:FF:30, dba=00:1A:45:2F:49:98)
bluetoothd[24162]: kernel auth requirements = 0x04
bluetoothd[24162]: stored link key type = 0x00
bluetoothd[24162]: /org/bluez/hci0/dev_00_1A_45_2F_49_98: Connected to 00:1A:45:2F:49:98
bluetoothd[24162]: Received AT+BRSF=27
bluetoothd[24162]: HFP HF features: "EC and/or NR function" "Call waiting and 3-way calling" "Voice recognition activation" "Remote volume control"
bluetoothd[24162]: Received AT+CIND=?
bluetoothd[24162]: Received AT+CIND?
bluetoothd[24162]: Received AT+CMER=3, 0, 0, 1
bluetoothd[24162]: Event reporting (CMER): mode=3, ind=1
bluetoothd[24162]: HFP Service Level Connection established
bluetoothd[24162]: State changed /org/bluez/hci0/dev_00_1A_45_2F_49_98: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_CONNECTED
bluetoothd[24162]: connect: Operation not permitted (1)
bluetoothd[24162]: config failed
bluetoothd[24162]: Audio API: sending BT_SETCONFIGURATION_RSP
bluetoothd[24162]: Unix client disconnected (fd=23)
bluetoothd[24162]: Received AT+VGS=00

aplay says:

Playing WAVE 'alarm.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono
ALSA lib pcm_bluetooth.c:464:(bluetooth_hsp_hw_params) BT_SETCONFIGURATION failed : Input/output error(5)
aplay: set_params:979: Unable to install hw params:

The second time I run aplay the error messages arrives more quickly:

bluetoothd[24162]: Accepted new client connection on unix socket (fd=23)
bluetoothd[24162]: Audio API: received BT_GETCAPABILITIES_REQ
bluetoothd[24162]: Audio API: sending BT_GETCAPABILITIES_RSP
bluetoothd[24162]: Audio API: received BT_SETCONFIGURATION_REQ
bluetoothd[24162]: config sco - device = 00:1A:45:2F:49:98 access_mode = 2
bluetoothd[24162]: connect: Operation not permitted (1)
bluetoothd[24162]: config failed
bluetoothd[24162]: Audio API: sending BT_SETCONFIGURATION_RSP
bluetoothd[24162]: Unix client disconnected (fd=23)

hcidump -XV doesn't show anything that looks like an error to me:

HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
     bdaddr 00:1A:45:2F:49:98 ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
     Packet type: DM1 DM3 DM5 DH1 DH3 DH5
 > HCI Event: Command Status (0x0f) plen 4
     Create Connection (0x01|0x0005) status 0x00 ncmd 1
 > HCI Event: Connect Complete (0x03) plen 11
     status 0x00 handle 41 bdaddr 00:1A:45:2F:49:98 type ACL encrypt 0x00
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
     handle 41
 > HCI Event: Command Status (0x0f) plen 4
     Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 0
 > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
     bdaddr 00:1A:45:2F:49:98 mode 1
 > HCI Event: Max Slots Change (0x1b) plen 3
     handle 41 slots 5
 > HCI Event: Command Status (0x0f) plen 4
     Unknown (0x00|0x0000) status 0x00 ncmd 1
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
     bdaddr 00:1A:45:2F:49:98 mode 2 clkoffset 0x0000
 > HCI Event: Command Status (0x0f) plen 4
     Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
 > HCI Event: Read Remote Supported Features (0x0b) plen 11
     status 0x00 handle 41
     Features: 0xbf 0xfe 0x8b 0xf8 0x1b 0x18 0x00 0x80
< ACL data: handle 41 flags 0x02 dlen 10
     L2CAP(s): Info req: type 2
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 16
     L2CAP(s): Info rsp: type 2 result 0
       Extended feature mask 0x0000
< ACL data: handle 41 flags 0x02 dlen 12
     L2CAP(s): Connect req: psm 3 scid 0x0040
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 16
     L2CAP(s): Connect rsp: dcid 0x008c scid 0x0040 result 1 status 2
       Connection pending - Authorization pending
 > HCI Event: Remote Name Req Complete (0x07) plen 255
     status 0x00 bdaddr 00:1A:45:2F:49:98 name 'Jabra JX10 series 2'
 > HCI Event: Link Key Request (0x17) plen 6
     bdaddr 00:1A:45:2F:49:98
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
     bdaddr 00:1A:45:2F:49:98 key F63331CE2D0DBCA190DC73C930CD6117
 > HCI Event: Command Complete (0x0e) plen 10
     Link Key Request Reply (0x01|0x000b) ncmd 1
     status 0x00 bdaddr 00:1A:45:2F:49:98
 > ACL data: handle 41 flags 0x02 dlen 16
     L2CAP(s): Connect rsp: dcid 0x008c scid 0x0040 result 0 status 0
       Connection successful
< ACL data: handle 41 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x008c flags 0x00 clen 4
       MTU 1013
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 14
     L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
       Success
 > ACL data: handle 41 flags 0x02 dlen 16
     L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
       MTU 1013
< ACL data: handle 41 flags 0x02 dlen 18
     L2CAP(s): Config rsp: scid 0x008c flags 0x00 result 0 clen 4
       MTU 1013
< ACL data: handle 41 flags 0x02 dlen 8
     L2CAP(d): cid 0x008c len 4 [psm 3]
       RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 41 flags 0x02 dlen 18
     L2CAP(d): cid 0x008c len 14 [psm 3]
       RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
       dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
       frame_size 1008 max_retrans 0 credits 7
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 18
     L2CAP(d): cid 0x0040 len 14 [psm 3]
       RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
       dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0
       frame_size 127 max_retrans 0 credits 0
< ACL data: handle 41 flags 0x02 dlen 8
     L2CAP(d): cid 0x008c len 4 [psm 3]
       RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 8
     L2CAP(d): cid 0x0040 len 4 [psm 3]
       RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 41 flags 0x02 dlen 12
     L2CAP(d): cid 0x008c len 8 [psm 3]
       RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
       dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
 > ACL data: handle 41 flags 0x02 dlen 12
     L2CAP(d): cid 0x0040 len 8 [psm 3]
       RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
       dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 12
     L2CAP(d): cid 0x008c len 8 [psm 3]
       RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
       dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 12
     L2CAP(d): cid 0x0040 len 8 [psm 3]
       RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
       dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 9
     L2CAP(d): cid 0x008c len 5 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
 > ACL data: handle 41 flags 0x02 dlen 9
     L2CAP(d): cid 0x0040 len 5 [psm 3]
       RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 15
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 19
     L2CAP(d): cid 0x0040 len 15 [psm 3]
       RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 11 fcs 0x40
       0000: 41 54 2b 42 52 53 46 3d  32 37 0d                 AT+BRSF=27.
< ACL data: handle 41 flags 0x02 dlen 19
     L2CAP(d): cid 0x008c len 15 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 11 fcs 0x9a
       0000: 0d 0a 2b 42 52 53 46 3d  30 0d 0a                 ..+BRSF=0..
< ACL data: handle 41 flags 0x02 dlen 14
     L2CAP(d): cid 0x008c len 10 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
       0000: 0d 0a 4f 4b 0d 0a                                 ..OK..
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 19
     L2CAP(d): cid 0x0040 len 15 [psm 3]
       RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 10 fcs 0x5c credits 2
       0000: 41 54 2b 43 49 4e 44 3d  3f 0d                    AT+CIND=?.
< ACL data: handle 41 flags 0x02 dlen 135
     L2CAP(d): cid 0x008c len 131 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 127 fcs 0x9a
       0000: 0d 0a 2b 43 49 4e 44 3a  28 22 62 61 74 74 63 68  ..+CIND:("battch
       0010: 67 22 2c 28 30 2d 35 29  29 2c 28 22 73 69 67 6e  g",(0-5)),("sign
       0020: 61 6c 22 2c 28 30 2d 35  29 29 2c 28 22 73 65 72  al",(0-5)),("ser
       0030: 76 69 63 65 22 2c 28 30  2c 31 29 29 2c 28 22 63  vice",(0,1)),("c
       0040: 61 6c 6c 22 2c 28 30 2c  31 29 29 2c 28 22 63 61  all",(0,1)),("ca
       0050: 6c 6c 73 65 74 75 70 22  2c 28 30 2d 33 29 29 2c  llsetup",(0-3)),
       0060: 28 22 63 61 6c 6c 68 65  6c 64 22 2c 28 30 2d 32  ("callheld",(0-2
       0070: 29 29 2c 28 22 72 6f 61  6d 22 2c 28 30 2c 31     )),("roam",(0,1
< ACL data: handle 41 flags 0x02 dlen 12
     L2CAP(d): cid 0x008c len 8 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 4 fcs 0x9a
       0000: 29 29 0d 0a                                       ))..
< ACL data: handle 41 flags 0x02 dlen 14
     L2CAP(d): cid 0x008c len 10 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
       0000: 0d 0a 4f 4b 0d 0a                                 ..OK..
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 18
     L2CAP(d): cid 0x0040 len 14 [psm 3]
       RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 9 fcs 0x5c credits 3
       0000: 41 54 2b 43 49 4e 44 3f  0d                       AT+CIND?.
< ACL data: handle 41 flags 0x02 dlen 31
     L2CAP(d): cid 0x008c len 27 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 23 fcs 0x9a
       0000: 0d 0a 2b 43 49 4e 44 3a  35 2c 35 2c 31 2c 30 2c  ..+CIND:5,5,1,0,
       0010: 30 2c 30 2c 30 0d 0a                              0,0,0..
< ACL data: handle 41 flags 0x02 dlen 14
     L2CAP(d): cid 0x008c len 10 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
       0000: 0d 0a 4f 4b 0d 0a                                 ..OK..
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 28
     L2CAP(d): cid 0x0040 len 24 [psm 3]
       RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 19 fcs 0x5c credits 2
       0000: 41 54 2b 43 4d 45 52 3d  33 2c 20 30 2c 20 30 2c  AT+CMER=3, 0, 0,
       0010: 20 31 0d                                           1.
< ACL data: handle 41 flags 0x02 dlen 14
     L2CAP(d): cid 0x008c len 10 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
       0000: 0d 0a 4f 4b 0d 0a                                 ..OK..
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1
 > ACL data: handle 41 flags 0x02 dlen 19
     L2CAP(d): cid 0x0040 len 15 [psm 3]
       RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 10 fcs 0x5c credits 1
       0000: 41 54 2b 56 47 53 3d 30  30 0d                    AT+VGS=00.
< ACL data: handle 41 flags 0x02 dlen 14
     L2CAP(d): cid 0x008c len 10 [psm 3]
       RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
       0000: 0d 0a 4f 4b 0d 0a                                 ..OK..
 > HCI Event: Number of Completed Packets (0x13) plen 5
     handle 41 packets 1