kernel-packages team mailing list archive

[Tim Abell <tim@xxxxxxxxxxxxx>]

@erotavlas, thanks but that didn't work for me with an ASUS dongle with
the same chip in it. :-(

tim@atom:~% lsusb | grep ASUS
Bus 003 Device 003: ID 0b05:17cb ASUSTek Computer, Inc. 

http://www.ebuyer.com/623493-asus-usb-bt400-mini-bluetooth-4-0-usb-adapter-usb-bt400
"Asus USB-BT400 - Mini Bluetooth 4.0 USB Adapter"

I have the same problem of no sound in or out.

=======

Quoting the article in case it moves/vanishes:

-----

It has come to our attention that there are some issues on certain Linux
systems with regards to using Headset Profile and Hands-Free Profile
with our USB Bluetooth Adapters.

The issue stems from a lack of support for these profiles on the
Broadcom BCM20702 chipset found inside our device, unless a proprietary
firmware file is loaded into it to enable this functionality.

The steps to install the firmware are as follows:Screenshot from
2014-06-23 17:34:49

    Open your favorite terminal
    Run the following command to download the firmware file:

    wget https://s3.amazonaws.com/plugable/bin/fw-0a5c_21e8.hcd

    Copy the firmware file to the /lib/firmware folder:

    sudo cp fw-0a5c_21e8.hcd /lib/firmware

    Reboot

New kernel versions have moved the location in which the firmware file
has to be installed. The instructions that follow are for kernels 3.18
and newer

    Open your favorite terminal
    Run the following command to download the firmware file:

    wget https://s3.amazonaws.com/plugable/bin/fw-0a5c_21e8.hcd

    Create the directory /lib/firmware/brcm

    sudo mkdir /lib/firmware/brcm

    Copy the firmware file to the /lib/firmware/brcm folder and rename
the file to BCM20702A0-0a5c-21e8.hcd:

    sudo mv fw-0a5c_21e8.hcd /lib/firmware/brcm/BCM20702A0-0a5c-21e8.hcd

    Reboot

That’s it! HFP and HSP profiles should now work without issue!

We have also heard of some reports that these steps can solve some
issues with other profiles, like A2DP, but have been unable to reproduce
the issues.  It is possible that newer versions of BlueZ and the Linux
kernel have fixed these issues, and that is why we are not seeing them
any more.

UPDATE: These steps will also fix many incompatibility issues with
certain A2DP devices, such as Bluetooth Headsets and Speakers. If you
are having trouble pairing your Bluetooth Audio device to your Linux PC,
this firmware file will likely fix your issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/962082

Title:
  Profiles that require duplex audio like Head Set (HSP) and Hands Free
  (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips

Status in HWE Next Project:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  This problem seems to occur on every device that uses  the BCM20702A0
  Bluetooth hardware.

  How to reproduce:

  (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0.
  (2) Activate the device.  Usually there is a button on the headset you should press to notify the bluetooth stack that you're ready to use the device.  This creates SCO link and the plumbs the audio components.
  (3) Open the sound settings tool and select the bluetooth device under the "Input" and "Output" tabs.  Under each tab you should see a table with an entry that has a headset icon on the left with the bluetooth device name to the right.  This is the item to select.

  Now, everything should be configured so that you can use your
  bluetooth device to hear and record audio.  Test this by:

  Testing Input:

  (1) In the sound settings tool, select the "Input" tab.
  (2) Make sure the "Input Volume" is not muted and the scale widget is not set to zero.
  (3) Make sounds into the headset mic -- you should see the "Input Level" bar raise.

  Testing Output:
  In the same program:
  (1) Select the "Hardware" tab.
  (2) In the box labeled "Choose a device to configure", select your bluetooth device.
  (3) A combobox should appear at the bottom of the window labeled "Settings for the selected device".  Choose "Telephony Duplex (HSP/HFP)".
  (4) Now click on the "Test Speakers" button to the right.
  (5) Run speaker test.  You should hear a sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/962082/+subscriptions