linux - Pulse-audio: add bluetooth as sink

07
2014-07
  • Anton Balashov

    I'm trying to configure Bluetooth Audio System A2DP, but can't add bluetooth as sink:

    pactl load-module module-alsa-sink device=bluetooth
    

    In logs I got the next:

    ( 110.963|   0.011) D: [pulseaudio] alsa-util.c: Trying bluetooth with SND_PCM_NO_AUTO_FORMAT ...
    ( 110.963|   0.000) I: [pulseaudio] (alsa-lib)pcm.c: Unknown PCM bluetooth
    ( 110.964|   0.000) I: [pulseaudio] alsa-util.c: Error opening PCM device bluetooth: No such file or directory
    ( 110.965|   0.000) E: [pulseaudio] module.c: Failed to load module "module-alsa-sink" (argument: "device=bluetooth"): initialization failed.
    

    Where I can get the correct device name?

  • Answers
    Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

    Related Question

    Windows 7 bluetooth stereo audio A2DP only works when freshly paired
  • none

    The question is - how to fix it?

    I have a BCK-08 ( http://www.dealextreme.com/details.dx/sku.8422 ) bluetooth headset that features better quality stereo audio (A2DP). It's built around a IS1621N ( http://www.issc.com.tw/stereo.htm ). It connects to an USB Bluetooth stick (logilink bt0007 with csr chipset, http://www.logilink.eu/showproduct/BT0007.htm?seticlanguage=en ).

    Now Windows 7 has significantly improved audio handling. The device is found. When activated, it shows up in mixer as Bluetooth Audio Renderer.

    However, while the headset mode always seems to work, I have to "remove" the device from the bluetooth list, and when I "add" it again, it just works.

    Now what could interfere? Sleep mode, Skype, Realtek Audio Manager? Bad drivers? Problem with CSR chipset? Problem with IS1621N? BIOS USB settings?

    I don't have any other devices so I can't swap. I think chances are litte someone else has this problem, but maybe has more experience in getting misbehaving hardware to work as it should.. :-)


  • Related Answers
  • JMV2009

    Got the same or similar problems. After standby/hibernation I need to disable and enable the service, so you don't need to repair. Also turning the headset on and off works. I also like to use older drivers, but there I experience BSOD's.

    Basically you are reloading the driver then. I am assuming you are running the 5.0.14 latest drivers. These drivers are not strictly speaking inbox, although they used to be planned as such, and they were in the release candidate. You probably downloaded them automatically from windows update.

    They are courtesy of CSR, but they don't support them. Microsoft does not support them, as they are not inbox. Microsoft claims the headsets manufacturers should support them. The headset manufacturers claim they should be supported by the dongle manufacturers. These typically ship with alternate bluetooth stacks, which support a2dp profiles. Examples of bluetooth stacks are toshiba, bluesoleil and widcomm.