The configuration file "/etc/bluetooth/audio.conf" installed by default for bluez-4.98-r1 breaks headset functionality (headset configured via ~/.asoundrc or phonon), bluetoothd somehow fails to register a newly switched on device (correctly paired and trusted by) with ALSA. I made a patch following the advice from the above URL that solves the problem. Reproducible: Always
Created attachment 300057 [details] Add Enable=Socket to [General] section of audio.conf
Not sure how to handle this yet as upstream thinks socket shouldn't be used
Created attachment 300121 [details, diff] 1.patch This patch should fix the problem WITHOUT changing default configuration
1.patch doesn't seem to work for me. Any info I can provide to debug the problem?
I would join to linux-bluetooth mailing list: http://www.bluez.org/development/lists/ And reply to that thread explaining the patch doesn't work for you
Thanks for the link, will do.
Hi, patch is working for me. I am not sure why simple bluetoothd stop/start is not working, I have to restart machine to have my HiFi audio over bluetooth working again. Thanks.
Hi there, Just to understand if I'm experiencing the same issue, my BT headset used to work fine, with the following definition in asound.rc: pcm.bthw_WBT210 { type bluetooth device 00:12:A1:XX:XX:XX profile "auto" } ctl.bthifi { type bluetooth device 00:12:A1:XX:XX:XX profile "auto" } pcm.bthifi { type plug slave { pcm bthw_WBT210 } hint { show on description "bthifi" } } but now, after correct pairing, I get the this error: $ aplay -D bthifi /usr/share/sounds/ekiga/voicemail.wav bt_audio_service_open: connect() failed: Connection refused (111) aplay: main:660: audio open error: Connection refused Is that symptom of the bug discussed here? Cheers, ^s
Probably. In audio.conf under [General], add the line Enable=Socket and test if everything works as before. Note that this is only a work-around, as socket-support might go away in the future.
+*bluez-4.98-r2 (14 Feb 2012) + + 14 Feb 2012; Pacho Ramos <pacho@gentoo.org> +bluez-4.98-r2.ebuild, + +files/bluez-4.98-fix-header.patch, +files/bluez-4.98-fix-socket.patch, + -bluez-4.98.ebuild: + Fix compilation problems against bluez, bug #403341 (by Steev Klimaszewski and + Marcel Unbehaun); fix needing to enable socket, bug #401065 (by Andreas + Eckstein and Ivan ivanov). Drop old. + Please recheck with this one and, to be sure the new bluetoothd is loaded, reboot after updating bluez
Sorry, Pacho, it does not work for me. I rebooted after update, I can pair the my headset with the PC and get the audio signal (two beeps), but applications cannot pick up the bluetooth audio device. My ~/.asoundrc is essentially the same as the one above, and unless something has to be changed there as well, the bluez patch does not work as intended.
I should probably add that bluez was compiled with the USE flags dencies... done! USE="alsa (consolekit) readline test-programs usb -caps -cups -debug -gstreamer -pcmcia and that I am not using gstreamer or pulseaudio.
(In reply to comment #5) > I would join to linux-bluetooth mailing list: > http://www.bluez.org/development/lists/ > > And reply to that thread explaining the patch doesn't work for you Can you reply to bluez mailing list telling them attached patch doesn't work for you? Otherwise I think will be difficult to get upstream attention and, then, to fix this Thanks
+*bluez-4.99 (08 Mar 2012) + + 08 Mar 2012; Pacho Ramos <pacho@gentoo.org> +bluez-4.99.ebuild, + -bluez-4.98-r1.ebuild: + Version bump, remove old. + It includes upstream fixes for problems like this, please re-test with that version
