https://bugzilla.novell.com/show_bug.cgi?id=410683 User tiwai@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@novell.com AssignedTo|tiwai@novell.com |seife@novell.com --- Comment #1 from Takashi Iwai 2008-07-28 10:31:00 MDT --- Looks like you need to install bluez-audio.rpm and set up the asoundrc stuff. Reassigned to bluez-audio maintainer for more details. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User carlos.bessa@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c3 --- Comment #3 from Carlos Bessa 2008-08-22 13:50:04 MDT --- I have bluez-audio 3.32-8.1 installed. The error is still the same, as described above. I must add that that happens as root (su). If i try as regular user i get this error:

mplayer -ao alsa:device=bluetooth /home/***/Music/***.mp3 ... [AO_ALSA] alsa-lib: pcm_bluetooth.c:1593:(bluetooth_init) BT_GETCAPABILITIES failed : Input/output error(5) [AO_ALSA] Playback open error: Input/output error Could not open/initialize audio device -> no sound. Audio: no sound Video: no video

regards, Carlos -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c5 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vbotka@novell.com Status|NEEDINFO |ASSIGNED Info Provider|carlos.bessa@gmail.com | Priority|P5 - None |P3 - Medium --- Comment #5 from Stefan Seyfried 2008-09-19 08:12:14 MDT --- This might be related to bug 412464... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User vbotka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c7 Vladimir Botka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |carlos.bessa@gmail.com --- Comment #7 from Vladimir Botka 2008-10-15 12:52:55 MDT --- Hello Carlos, I think you got enough information, so we can put it together. The message "Could not open/initialize audio device -> no sound." tells us that alsa is not able to open the BT headset. This can happen when the BT headset is not switched on. Some BT headset switched off after some timeout and others just enter stand-by mode and waik-up on demand. Please check your case. I would suggest that we start from the beginning avoiding any error. Please, as root, restart the bletooth subsytem #rcbluetooth restart, then put the BT headset into the pairing mode, then issue command #hcitool scan and check the BT headset in the list, then as user put the address of BT headset into the file ~/.asoundrc and try #mplayer -ao alsa:bluetooth x.mp3 . If the BT headset is not paired it will try to do so. Then you should hear the sound in the BT headset. If this does not work plese post the following information: #uname -a #zypper se -s bluez #hcitool scan #cat ~/.asoundrc #mplayer -ao alsa:bluetooth x.mp3 Thank you, -vlado Vladimir Botka -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User tiwai@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c9 --- Comment #9 from Takashi Iwai 2008-10-16 04:49:49 MDT --- Please try first with the standard tools like aplay. % aplay -Dbluetooth your-wave-file.wav -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User tiwai@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c11 --- Comment #11 from Takashi Iwai 2008-10-16 06:37:25 MDT --- Weird. Could you run "strace -o strace.log apaly -Dbluetooth xxx.wav" and attach the log file? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User carlos.bessa@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c13 --- Comment #13 from Carlos Bessa 2008-10-16 07:18:17 MDT --- Created an attachment (id=245976) --> (https://bugzilla.novell.com/attachment.cgi?id=245976) strace log file for aplay -Dplug argument -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User vbotka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c15 --- Comment #15 from Vladimir Botka 2008-10-16 08:36:03 MDT --- alsa does not see the file .asoundrc, thats the error "ALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM bluetooth" Run the aplay command as the user (not as a root). Check the HOME global variable. The $HOME/.asounrc should be readable by the user. If this does not work plese post the following information: #whoami #echo $HOME #cat $HOME/.asoundrc #aplay -Dbluetooth x.wav Thank you, -vlado Vladimir Botka -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User vbotka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c17 --- Comment #17 from Vladimir Botka 2008-10-16 12:00:41 MDT --- There should be no "plug:" between -D and the bluetooth argument. WRONG: #aplay -Dplug:bluetooth x.wav RIGHT: #aplay -Dbluetooth x.wav Please try again, -vlado Vladimir Botka -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User vbotka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c19 --- Comment #19 from Vladimir Botka 2008-10-16 14:02:26 MDT --- Sorry for the "plug:" noise. I tried, and for me it works both with and without the "plug:". Let us check the pairing. Is kbluetooth running? If not, start it as a user and check if you can see the BT headset among the "Paired/Trusted Devices". "Right click the BT applet in the System Tray" -> Configuration -> "Paired/Trusted Devices" If you can not see the BT headset there, just put the BT headset into the pairing mode and start the command #aplay -Dbluetooth x.wav The kbluetooth applet should ask for the PIN. In this case the PIN should be 0000. If the kbluetooth does not ask for the PIN, there is something wrong with the kbluetooth. Then you got this option: Kill the kbluetooth and start from the commandline #passkey-agent 0000 00:1A:0E:77:DF:C5 Then put the BT headset into the pairing mode again and start #aplay -Dbluetooth x.wav Passkey-agent should provide the PIN and BT headset shoud be paired afterwards. So, please try and send the results, -vlado Vladimir Botka -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User carlos.bessa@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c21 --- Comment #21 from Carlos Bessa 2009-01-15 07:05:58 MST --- Hi! I have since moved to openSuSE 11.1 with KDE4.13. I'm writing my phd thesis at the moment so i haven't had free time to look into this. But i have been "playing" with it in the last couple of days. The problem is that kbluetooth is not working from what i've read in other bug reports. I've tried to start again and follow the steps you've mentioned so far but can't even make a connection. "hcitool scan" works and sees the headset but "hcitool cc 00:1A:0E:77:DF:C5" doesn't do anything because "hcitool con" doesn't show any connection. My guess it's because of the pin, since kbluetooth doesn't work the ask the pin to connect. I've tried the "passkey-agent 0000 00:1A:0E:77:DF:C5" but get: "bash: passkey-agent: command not found" regards, Carlos -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User carlos.bessa@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c23 --- Comment #23 from Carlos Bessa 2009-01-15 08:53:01 MST --- ok, i'm leaving here the info from some of the commands i used above since i'm now on openSuSE11.1. KTPORT-Linux:/home/carlos # hciconfig -a hci0: Type: USB BD Address: 00:11:09:E6:5A:06 ACL MTU: 120:20 SCO MTU: 0:0 UP RUNNING PSCAN ISCAN RX bytes:11720 acl:124 sco:0 events:474 errors:0 TX bytes:5304 acl:129 sco:0 commands:235 errors:0 Features: 0xff 0xff 0x05 0x38 0x18 0x18 0x00 0x00 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT Name: 'KTPORT-Linux-0' Class: 0x4a210c Service Classes: Networking, Capturing, Telephony Device Class: Computer, Laptop HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x757 Manufacturer: Silicon Wave (11) KTPORT-Linux:/home/carlos # dmesg | grep Bluetooth Bluetooth: Core ver 2.13 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: Generic Bluetooth USB driver ver 0.3 Bluetooth: L2CAP ver 2.11 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.10 Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HCI USB driver ver 2.10 KTPORT-Linux:/home/carlos # /usr/bin/lsusb -v | grep Blue Bus 003 Device 009: ID 0db0:6855 Micro Star International Bluetooth Device bDeviceProtocol 1 Bluetooth idProduct 0x6855 Bluetooth Device bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth KTPORT-Linux:/home/carlos # uname -a Linux KTPORT-Linux 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux carlos@KTPORT-Linux:~> cat $HOME/.asoundrc pcm.bluetooth { type bluetooth device 00:1A:0E:77:DF:C5 profile "auto" } KTPORT-Linux:/home/carlos # zypper se -s bluez Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+-----------------------------+------------+------------+--------+------------------ i | bluez | package | 4.22-28.1 | x86_64 | Seife Factory v | bluez | package | 4.19-1.5 | x86_64 | openSUSE 11.1 DVD v | bluez | package | 4.22-30.1 | i586 | Seife Factory v | bluez | package | 4.19-1.5 | x86_64 | openSUSE-11.1-Oss v | bluez | package | 4.19-1.5 | i586 | openSUSE-11.1-Oss | bluez | srcpackage | 4.22-30.1 | noarch | Seife Factory | bluez | srcpackage | 4.22-28.1 | noarch | Seife Factory i | bluez-alsa | package | 4.22-28.1 | x86_64 | Seife Factory v | bluez-alsa | package | 4.22-30.1 | i586 | Seife Factory v | bluez-alsa | package | 4.19-1.5 | x86_64 | openSUSE-11.1-Oss v | bluez-alsa | package | 4.19-1.5 | i586 | openSUSE-11.1-Oss i | bluez-compat | package | 4.22-28.1 | x86_64 | Seife Factory v | bluez-compat | package | 4.22-30.1 | i586 | Seife Factory v | bluez-compat | package | 4.19-1.5 | x86_64 | openSUSE-11.1-Oss v | bluez-compat | package | 4.19-1.5 | i586 | openSUSE-11.1-Oss | bluez-cups | package | 4.22-28.1 | x86_64 | Seife Factory | bluez-cups | package | 4.19-1.5 | x86_64 | openSUSE 11.1 DVD | bluez-cups | package | 4.22-30.1 | i586 | Seife Factory | bluez-cups | package | 4.19-1.5 | x86_64 | openSUSE-11.1-Oss | bluez-cups | package | 4.19-1.5 | i586 | openSUSE-11.1-Oss | bluez-debuginfo | package | 4.22-28.1 | x86_64 | Seife Factory | bluez-debuginfo | package | 4.22-30.1 | i586 | Seife Factory | bluez-debugsource | package | 4.22-28.1 | x86_64 | Seife Factory | bluez-debugsource | package | 4.22-30.1 | i586 | Seife Factory | bluez-devel | package | 4.22-28.1 | x86_64 | Seife Factory | bluez-devel | package | 4.19-1.5 | x86_64 | openSUSE 11.1 DVD | bluez-devel | package | 4.22-30.1 | i586 | Seife Factory | bluez-devel | package | 4.19-1.5 | x86_64 | openSUSE-11.1-Oss | bluez-devel | package | 4.19-1.5 | i586 | openSUSE-11.1-Oss i | bluez-firmware | package | 1.2-28.72 | x86_64 | openSUSE 11.1 DVD i | bluez-firmware | package | 1.2-28.72 | x86_64 | openSUSE-11.1-Oss v | bluez-firmware | package | 1.2-28.88 | i586 | openSUSE-11.1-Oss i | bluez-gnome | package | 1.8-2.5 | x86_64 | openSUSE 11.1 DVD i | bluez-gnome | package | 1.8-2.5 | x86_64 | openSUSE-11.1-Oss v | bluez-gnome | package | 1.8-2.5 | i586 | openSUSE-11.1-Oss | bluez-gnome-lang | package | 1.8-2.5 | x86_64 | openSUSE-11.1-Oss | bluez-gnome-lang | package | 1.8-2.5 | i586 | openSUSE-11.1-Oss i | bluez-gstreamer | package | 4.22-29.1 | x86_64 | Seife Factory v | bluez-gstreamer | package | 4.22-31.1 | i586 | Seife Factory v | bluez-gstreamer | package | 4.19-1.9 | x86_64 | openSUSE-11.1-Oss v | bluez-gstreamer | package | 4.19-1.8 | i586 | openSUSE-11.1-Oss | bluez-gstreamer | srcpackage | 4.22-31.1 | noarch | Seife Factory | bluez-gstreamer | srcpackage | 4.22-29.1 | noarch | Seife Factory | bluez-gstreamer-debuginfo | package | 4.22-29.1 | x86_64 | Seife Factory | bluez-gstreamer-debuginfo | package | 4.22-31.1 | i586 | Seife Factory | bluez-gstreamer-debugsource| package | 4.22-29.1 | x86_64 | Seife Factory | bluez-gstreamer-debugsource| package | 4.22-31.1 | i586 | Seife Factory | bluez-hcidump | package | 1.42-18.4 | x86_64 | Seife Factory | bluez-hcidump | package | 1.42-17.39 | x86_64 | openSUSE 11.1 DVD | bluez-hcidump | package | 1.42-18.4 | i586 | Seife Factory | bluez-hcidump | package | 1.42-17.39 | x86_64 | openSUSE-11.1-Oss | bluez-hcidump | package | 1.42-17.41 | i586 | openSUSE-11.1-Oss | bluez-hcidump | srcpackage | 1.42-18.4 | noarch | Seife Factory | bluez-hcidump-debuginfo | package | 1.42-18.4 | x86_64 | Seife Factory | bluez-hcidump-debuginfo | package | 1.42-18.4 | i586 | Seife Factory | bluez-hcidump-debugsource | package | 1.42-18.4 | x86_64 | Seife Factory | bluez-hcidump-debugsource | package | 1.42-18.4 | i586 | Seife Factory i | bluez-test | package | 4.22-28.1 | x86_64 | Seife Factory v | bluez-test | package | 4.22-30.1 | i586 | Seife Factory v | bluez-test | package | 4.19-1.5 | x86_64 | openSUSE-11.1-Oss v | bluez-test | package | 4.19-1.5 | i586 | openSUSE-11.1-Oss | python-pybluez | package | 0.15-3.42 | x86_64 | openSUSE 11.1 DVD | python-pybluez | package | 0.15-3.42 | x86_64 | openSUSE-11.1-Oss | python-pybluez | package | 0.15-3.44 | i586 | openSUSE-11.1-Oss I've tried the gnome applet and it seems to work. I have managed to configure a new device, added the pin, and now every time i turn the headset on the connection is established for a few seconds: KTPORT-Linux:/home/carlos # hcitool con Connections: > ACL 00:1A:0E:77:DF:C5 handle 1 state 1 lm SLAVE AUTH ENCRYPT .but then drops. I can also see it connects from the gnome applet->bluetooth preferences->known devices .. there is an icon that means it's connected and it appears but only for a few seconds. If i press the button on the headset it connects again but also drops afterwards. This is what i get with aplay and mplayer: carlos@KTPORT-Linux:~> aplay -Dplug:bluetooth /opt/kde3/share/sounds/KDE_Startup.wav Playing WAVE '/opt/kde3/share/sounds/KDE_Startup.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono aplay: 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: 22050 PERIOD_TIME: 125000 PERIOD_SIZE: (2756 2757) PERIOD_BYTES: (5512 5514) PERIODS: (3 5) BUFFER_TIME: 500000 BUFFER_SIZE: 11025 BUFFER_BYTES: 22050 TICK_TIME: 0 carlos@KTPORT-Linux:~> mplayer -ao alsa:device=bluetooth /opt/kde3/share/sounds/KDE_Startup.wav MPlayer dev-SVN-r27637-4.3-openSUSE Linux 11.1 (x86_64)-Packman (C) 2000-2008 MPlayer Team CPU: AMD Turion(tm) 64 Mobile Technology MT-32 (Family: 15, Model: 36, Stepping: 2) CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1 Compiled with runtime CPU detection. Can't open joystick device /dev/input/js0: No such file or directory Can't init input joystick 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 /opt/kde3/share/sounds/KDE_Startup.wav. Audio only file format detected. ========================================================================== Opening audio decoder: [pcm] Uncompressed PCM audio decoder AUDIO: 22050 Hz, 1 ch, s16le, 352.8 kbit/100.00% (ratio: 44100->44100) Selected audio codec: [pcm] afm: pcm (Uncompressed PCM) ========================================================================== [AO_ALSA] Unable to set hw-parameters: Invalid argument Failed to initialize audio driver 'alsa:device=bluetooth' Could not open/initialize audio device -> no sound. Audio: no sound Video: no video Exiting... (End of file) I could see from the gnome app that it temporarilly connects when executing the aplay and mplayer commands. regards, Carlos -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 Vladimir Botka changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Sound |Sound AssignedTo|vbotka@novell.com |tiwai@novell.com Product|openSUSE 11.0 |openSUSE 11.1 Target Milestone|--- |Final OS/Version|openSUSE 11.0 |openSUSE 11.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User carlos.bessa@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c26 --- Comment #26 from Carlos Bessa 2009-01-16 06:11:46 MST --- I updated to alsa.rpm and libasound2.rpm from factory and still get exactly the same error. I'm downloading some live cds from other distros to see if it works and then report back. Carlos -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User carlos.bessa@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c28 --- Comment #28 from Carlos Bessa 2009-02-10 10:54:49 MST --- Just an update. Tried the latest ubuntu and fedora distros, with livecds, and got exactly the same error. Also tested another 2 different headsets and one bt adapter... same result. Today i updated to bluez 4.29 and the result is a bit different: carlos@KTPORT-Linux:~> aplay -Dplug:bluetooth /opt/kde3/share/sounds/KDE_Startup.wav Playing WAVE '/opt/kde3/share/sounds/KDE_Startup.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono ALSA lib pcm_bluetooth.c:1563:(audioservice_expect) BT_START_STREAM failed : Success(0) ALSA lib pcm_bluetooth.c:1531:(audioservice_recv) Bogus message type 5 - name 3received from audio service aplay: 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: 22050 PERIOD_TIME: 125000 PERIOD_SIZE: (2756 2757) PERIOD_BYTES: (5512 5514) PERIODS: (3 5) BUFFER_TIME: 500000 BUFFER_SIZE: 11025 BUFFER_BYTES: 22050 TICK_TIME: 0 regards, Carlos -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=410683 User carlos.bessa@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=410683#c30 --- Comment #30 from Carlos Bessa 2009-03-12 05:30:34 MST --- One more try at this and it's working now, sort of. I've been updating bluez and alsa packages from the audio repo whenever new ones come out so i tried once some to see if it might be working now. Bluez version is 4.32-43.1 Alsa version is alsa-1.0.19.git20090304-2.1 My laptop bluetooth adaptor still doesn't work... but i'll get to that in the end. I gave a friends cheap usb adapter, Anycom USB-500, another shot. This one actually said it is suported under linux on the box. I had already tried this one before too with no success. I also found a "new" bluetooth entry on opensuse wiki, and altered the asoundrc file according to it: http://en.opensuse.org/Bluetooth/Headphones-HOWTO Aplay was giving me problems: carlos@KTPORT-Linux:~> aplay -D btheadset /usr/share/sounds/k3b_success1.wav Playing WAVE '/usr/share/sounds/k3b_success1.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono aplay: set_params:961: Sample format non available So i tried mplayer: mplayer -ao alsa:device=btheadset ***.mp3 .......AO: [alsa] 8000Hz 1ch s16le (2 bytes per sample) Video:novideo Startingplayback... A: 18.6 (18.5) of 254.0 (04:14.0) 2.3% And it's working! I can hear sound perfectly. Skype still doesn't work but it's another matter, that's skypes problem. This is the info i got from the adaptor: carlos@KTPORT-Linux:~> dmesg | grep Bluetooth Bluetooth: Core ver 2.13 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: Generic Bluetooth USB driver ver 0.3 Bluetooth: L2CAP ver 2.11 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.10 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast carlos@KTPORT-Linux:~> /usr/bin/lsusb -v |grep Blue bDeviceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth carlos@KTPORT-Linux:~> sudo /usr/sbin/hciconfig -a hci0: Type: USB BD Address: 00:0A:3A:87:A4:02 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1199 acl:0 sco:0 events:60 errors:0 TX bytes:2902 acl:0 sco:0 commands:60 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'KTPORT-Linux-0' Class: 0x4a210c Service Classes: Networking, Capturing, Telephony Device Class: Computer, Laptop HCI Ver: 2.1 (0x4) HCI Rev: 0x5183 LMP Ver: 2.1 (0x4) LMP Subver: 0x420e Manufacturer: Broadcom Corporation (15) carlos@KTPORT-Linux:~> cat $HOME/.asoundrc pcm.!default { type pulse } ctl.!default { type pulse } pcm.btheadset { type bluetooth device 00:1A:0E:77:DF:C5 } One thing that i immediately saw that's different from the laptop adapter is the connection. This one connects to the headset and keeps the connection (can see it with "hcitool con"), while the laptop adapter connects but usually drops after a few seconds. This is the "hcitool con" output for the ANYKEY adapter after i turn on the headset: Connections: > ACL 00:1A:0E:77:DF:C5 handle 11 state 1 lm SLAVE AUTH ENCRYPT After i start mplayer: Connections: < eSCO 00:1A:0E:77:DF:C5 handle 6 state 1 lm SLAVE > ACL 00:1A:0E:77:DF:C5 handle 11 state 1 lm SLAVE AUTH ENCRYPT This is the "hcitool con" output for the laptop adatper after i turn on the headset: Connections: > ACL 00:1A:0E:77:DF:C5 handle 7 state 1 lm MASTER AUTH ENCRYPT When the connection was being requested by mplayer i got this: Connections: < ACL 00:1A:0E:77:DF:C5 handle 2 state 1 lm MASTER and 2 seconds later: Connections: < ACL 00:1A:0E:77:DF:C5 handle 2 state 1 lm SLAVE This is the same hw info for the laptop adapter again: carlos@KTPORT-Linux:~> dmesg | grep Bluetooth Bluetooth: Core ver 2.13 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: Generic Bluetooth USB driver ver 0.3 Bluetooth: L2CAP ver 2.11 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.10 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast carlos@KTPORT-Linux:~> /usr/bin/lsusb -v |grep Blue Bus 003 Device 011: ID 0db0:6855 Micro Star International Bluetooth Device bDeviceProtocol 1 Bluetooth idProduct 0x6855 Bluetooth Device bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth bInterfaceProtocol 1 Bluetooth carlos@KTPORT-Linux:~> /usr/sbin/hciconfig -a hci0: Type: USB BD Address: 00:11:09:E6:5A:06 ACL MTU: 120:20 SCO MTU: 0:0 UP RUNNING PSCAN RX bytes:1108 acl:0 sco:0 events:45 errors:0 TX bytes:432 acl:0 sco:0 commands:45 errors:0 Features: 0xff 0xff 0x05 0x38 0x18 0x18 0x00 0x00 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT Name: 'KTPORT-Linux-0' Class: 0x4a010c Service Classes: Networking, Capturing, Telephony Device Class: Computer, Laptop HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x757 Manufacturer: Silicon Wave (11) This is the current output from mplayer for the laptop adapter: carlos@KTPORT-Linux:~> mplayer -ao alsa:device=btheadset ***.mp3 MPlayer dev-SVN-r27637-4.3-openSUSE Linux 11.1 (x86_64)-Packman (C) 2000-2008 MPlayer Team *** ========================================================================== Opening audio decoder: [mp3lib] MPEG layer-2, layer-3 AUDIO: 44100 Hz, 2 ch, s16le, 320.0 kbit/22.68% (ratio: 40000->176400) Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-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 Failed to initialize audio driver 'alsa:device=btheadset' Could not open/initialize audio device -> no sound. Audio: no sound Video: no video Exiting... (End of file) Only the hciconfig output if different, but that's hardware specific anyway. So maybe the laptop adapter is just "old" (the laptop is from 2005) and not very well supported by the bluez driver? Or could the problem just be in the connection? regards, Carlos -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.