0a5c:21e8 [Gigabyte GA-MA770-UD3] Broadcom bluetooth device BCM20702A0 not working

[Struan]

I have a IOGEAR Bluetooth 4.0 USB Micro Adapter (GBU521) which cannot audio sink with my bluetooth headphones (Kinovio BTH-220). Headphones can be detected and pair, but audio sink or mic input doesn't work. Blueman manager gives the error "Connection Failed: Stream Setup Failed. It used to work in the LTS Ubuntu version 12.04 but now no longer does with a kernel update.

lsusb | grep Bluetooth
Bus 001 Device 006: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0

$ dmesg | grep Bluetooth
[ 7.117429] Bluetooth: Core ver 2.16
[ 7.117460] Bluetooth: HCI device and connection manager initialized
[ 7.117468] Bluetooth: HCI socket layer initialized
[ 7.117471] Bluetooth: L2CAP socket layer initialized
[ 7.117475] Bluetooth: SCO socket layer initialized
[ 7.515068] Bluetooth: can't load firmware, may not work correctly
[ 8.685277] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.685281] Bluetooth: BNEP filters: protocol multicast
[ 8.685288] Bluetooth: BNEP socket layer initialized
[ 8.695821] Bluetooth: RFCOMM TTY layer initialized
[ 8.695832] Bluetooth: RFCOMM socket layer initialized
[ 8.695833] Bluetooth: RFCOMM ver 1.11

$ usb-devices
T: Bus=01 Lev=02 Prnt=03 Port=03 Cnt=02 Dev#= 6 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a5c ProdID=21e8 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0
S: SerialNumber=000272C5F0A4
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.23
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubu1204 2700 F.... pulseaudio
 /dev/snd/controlC0: ubu1204 2700 F.... pulseaudio
Date: Mon Jan 13 01:33:26 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-05-17 (605 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=a8818c2a-d269-4da2-aac0-3eda50c15e0c ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-15-generic N/A
 linux-backports-modules-3.11.0-15-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-12-10 (33 days ago)
dmi.bios.date: 08/12/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: GA-MA770-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd08/12/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA770-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Struan, thank you for reporting this and helping make Ubuntu better. Could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please just make a comment to this.

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Struan (struans)]

I am posting from a live install of trusty-desktop-amd64.iso and am happy to say that A2DP audio works again! The dmesg firmware error still exists though. I noticed too that although sound works on my BT headphones, the mic input does not get picked up by the ubuntu sound utility. Perhaps it should be relegated to a seperate bug report.

$ dmesg | grep Bluetooth
[ 41.605423] Bluetooth: Core ver 2.17
[ 41.605443] Bluetooth: HCI device and connection manager initialized
[ 41.605451] Bluetooth: HCI socket layer initialized
[ 41.605453] Bluetooth: L2CAP socket layer initialized
[ 41.605456] Bluetooth: SCO socket layer initialized
[ 41.652025] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 41.652029] Bluetooth: BNEP filters: protocol multicast
[ 41.652037] Bluetooth: BNEP socket layer initialized
[ 41.658083] Bluetooth: RFCOMM TTY layer initialized
[ 41.658094] Bluetooth: RFCOMM socket layer initialized
[ 41.658100] Bluetooth: RFCOMM ver 1.11
[ 42.590497] Bluetooth: can't load firmware, may not work correctly

Should I test anything else?

[penalvch (penalvch)]

Straun:
"I noticed too that although sound works on my BT headphones, the mic input does not get picked up by the ubuntu sound utility. Perhaps it should be relegated to a seperate bug report."

Yes, it should.

Regarding just the audio in, would you need a backport to a release prior to Trusty, or may this be closed as Status Invalid?

[Chris Weyl (rsrchboy)]

As someone with the same problem and a long-standing decision to use only stable kernel builds on his primary laptop ;), I'd love to see a backport to at least saucy, with precise as a distinct bonus (LTS + new h/w support == goodness).

[Chris Weyl (rsrchboy)]

Oh -- and I updated the tags / flags as best I could given the information in the ticket; hopefully this helps place it in the right queues for attention :)

[penalvch (penalvch)]

Chris Weyl, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

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