Jabra BT125 headset crashes

[Ben Jencks]

Binary package hint: bluez

(This is on Jaunty as of today, March 30).

Steps to reproduce:
1. Stop and start /etc/init.d/bluetooth to ensure a clean state; delete device from known devices
2. Put headset into pairing mode
3. "Setup new device..." from bluetooth-applet
4. It discovers and connects fine.
5. Attempt to play something with mplayer -ao alsa:device=headset
6. Headset crashes -- disconnects from computer, stops blinking, and no longer responds to its button. It must be plugged into its charger to reset it.
7. Error appears:
[AO_ALSA] alsa-lib: pcm_bluetooth.c:1569:(audioservice_expect) BT_START_STREAM failed : Success(0)
[AO_ALSA] alsa-lib: pcm_bluetooth.c:1528:(audioservice_recv) Too short (1 bytes) IPC packet from bluetoothd
[AO_ALSA] Unable to set hw-parameters: Invalid argument
Failed to initialize audio driver 'alsa:device=headset'
Could not open/initialize audio device -> no sound.

Nothing appears in dmesg. daemon.log has:

Mar 30 10:01:15 bartok bluetoothd[2513]: link_key_request (sba=00:11:F6:09:DF:D9, dba=00:16:8F:91:7C:D4)
Mar 30 10:01:15 bartok bluetoothd[2513]: pin_code_request (sba=00:11:F6:09:DF:D9, dba=00:16:8F:91:7C:D4)
Mar 30 10:01:46 bartok bluetoothd[2513]: Discovery session 0x7f513f5303f0 with :1.592 activated
Mar 30 10:01:54 bartok bluetoothd[2513]: link_key_request (sba=00:11:F6:09:DF:D9, dba=00:16:8F:91:7C:D4)
Mar 30 10:01:54 bartok bluetoothd[2513]: pin_code_request (sba=00:11:F6:09:DF:D9, dba=00:16:8F:91:7C:D4)
Mar 30 10:01:54 bartok bluetoothd[2513]: link_key_notify (sba=00:11:F6:09:DF:D9, dba=00:16:8F:91:7C:D4, type=0)
Mar 30 10:01:56 bartok bluetoothd[2513]: Registered interface org.bluez.Input on path /org/bluez/2513/hci0/dev_00_16_8F_91_7C_D4
Mar 30 10:01:56 bartok bluetoothd[2513]: Registered interface org.bluez.Serial on path /org/bluez/2513/hci0/dev_00_16_8F_91_7C_D4
Mar 30 10:01:56 bartok bluetoothd[2513]: Registered interface org.bluez.Headset on path /org/bluez/2513/hci0/dev_00_16_8F_91_7C_D4
Mar 30 10:02:12 bartok bluetoothd[2513]: link_key_request (sba=00:11:F6:09:DF:D9, dba=00:16:8F:91:7C:D4)
Mar 30 10:02:12 bartok bluetoothd[2513]: Connection refused (111)
Mar 30 10:02:12 bartok bluetoothd[2513]: Unable to get a SCO fd
Mar 30 10:02:12 bartok bluetoothd[2513]: headset_resume_complete: resume failed

My bluetooth dongle is:
Bus 008 Device 010: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

[Peng Deng (d6g)]

I have a similar problem with a logitech headset and a bluetooth adpater with Thinkpad T43:

Bus 004 Device 002: ID 0a5c:201e Broadcom Corp. IBM Integrated Bluetooth IV

The only difference is the headset is not disconnected after the failure.

Headset info:

$ hcitool name 00:0D:44:4F:EC:3F
Logitech HS03 V04

$ hcitool info 00:0D:44:4F:EC:3F
Requesting information ...
 BD Address: 00:0D:44:4F:EC:3F
 Device Name: Logitech HS03 V04
 LMP Version: 1.2 (0x2) LMP Subversion: 0x79d
 Manufacturer: Cambridge Silicon Radio (10)
 Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00
  <encryption> <slot offset> <timing accuracy> <role switch>
  <hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
  <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
  <paging scheme> <power control> <transparent SCO>
  <AFH cap. slave> <AFH cap. master>

[REM (1815131-gmail)]

Hi!

Similar problem with Logitech headset and BT Sony Vaio Z1VA:

>uname -a
Linux virgin 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:38:53 UTC 2009 i686 GNU/Linux

>cat .asoundrc
pcm.bluetooth {
   type bluetooth
   device 00:0D:44:5C:94:CB
   profile "voice"
}

> mplayer -quiet -ao alsa:device=bluetooth 01.mp3
MPlayer 1.0rc2-4.3.3 (C) 2000-2007 MPlayer Team
CPU: Intel(R) Pentium(R) M processor 1600MHz (Family: 6, Model: 9, Stepping: 5)
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing 01.mp3.
Audio file file format detected.
==========================================================================
Forced audio codec: mad
Opening audio decoder: [libmad] libmad mpeg audio decoder
AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400)
Selected audio codec: [mad] afm: libmad (libMAD MPEG layer 1-2-3)
==========================================================================
[AO_ALSA] alsa-lib: pcm_bluetooth.c:1569:(audioservice_expect) BT_START_STREAM failed : Success(0)
[AO_ALSA] alsa-lib: pcm_bluetooth.c:1528:(audioservice_recv) Too short (1 bytes) IPC packet from bluetoothd
[AO_ALSA] Unable to set hw-parameters: Invalid argument
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video

>lsusb:
Bus 004 Device 002: ID 044e:3003 Alps Electric Co., Ltd Bluetooth Device

>hcitool name 00:0D:44:5C:94:CB
Logitech HS05 V02

>sudo hcitool info 00:0D:44:5C:94:CB
Requesting information ...
        BD Address: 00:0D:44:5C:94:CB
        Device Name: Logitech HS05 V02
        LMP Version: 1.2 (0x2) LMP Subversion: 0x79d
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00
                <encryption> <slot offset> <timing accuracy> <role switch>
                <hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
                <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
                <paging scheme> <power control> <transparent SCO>
                <AFH cap. slave> <AFH cap. master>

[Srećko Jurić-Kavelj (jksrecko)]

I'm also experiencing similar problem. My bluetooth headset (SonyEricsson HBH-610a) never worked with bluez (works on Win XP with Bluesoleil, Vista). Just upgraded to Jaunty. This is what I get:

$ arecord -D bluetooth -f S16_LE | aplay
Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono
ALSA lib pcm_bluetooth.c:1569:(audioservice_expect) BT_START_STREAM failed : Success(0)
ALSA lib pcm_bluetooth.c:1528:(audioservice_recv) Too short (1 bytes) IPC packet from bluetoothd
arecord: set_params:1022: 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
aplay: playback:2208: read error

.asoundrc:

pcm.bluetoothraw {
 type bluetooth
 device "00:16:B8:0A:F9:79"
 profile "voice"
}

pcm.bluetooth {
 type plug
 slave {
  pcm bluetoothraw
 }
}

I'm using Gigabyte GN-BTD02 dongle. It works with SonyEricsson HVB-PV712. Same setup!

[Thawn (webmaster-korten-privat)]

Same problem here with a Samsung WEP180&185 headset and an asus usb dongle (USB ID 0b05:1715 ASUSTek Computer, Inc. 2045 Bluetooth 2.0 Device with trace filter).

>mplayer -ao alsa:device=headset /usr/share/sounds/alsa/Noise.wav
MPlayer 1.0rc2-4.3.3 (C) 2000-2007 MPlayer Team
CPU: AMD Athlon(tm) X2 Dual Core Processor BE-2350 (Family: 15, Model: 107, Stepping: 1)
CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing /usr/share/sounds/alsa/Noise.wav.
Audio file file format detected.
==========================================================================
Forced audio codec: mad
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 48000 Hz, 1 ch, s16le, 768.0 kbit/100.00% (ratio: 96000->96000)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
[AO_ALSA] alsa-lib: pcm_bluetooth.c:1569:(audioservice_expect) BT_START_STREAM failed : Success(0)
[AO_ALSA] alsa-lib: pcm_bluetooth.c:1528:(audioservice_recv) Too short (1 bytes) IPC packet from bluetoothd
[AO_ALSA] Unable to set hw-parameters: Invalid argument
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video

Before the BT start stream failed error appears, there is a long pause during which the headset beeps once directly before the error appears. The headset beeps again after the error message appears.

[Brian J. Murrell (brian-interlinx)]

Wow. Real nice. A whole load of "me too" posts but not a single post from a Ubuntu developer.

[Baptiste Mille-Mathias (bmillemathias)]

Benjamin,

Did you had chance to test with a newer version and tell if it works better.
I see you use directly alsa, does it work better with pulseaudio?

[Rex Tsai (chihchun)]

Thank you for reporting this bug to Ubuntu. Jaunty reached EOL on October 23, 2010.

Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please upgrade to newer release. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

[Brian J. Murrell (brian-interlinx)]

> [Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Which is probably just an indication that everyone involved has just given up any hope that anything will be done to fix the problem.