Can not connect to Bluetooth headset

Bug #1633583 reported by DimanNe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Expired
Undecided
Unassigned
pulseaudio (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I managed to pair with my wireless headset, but I was unable to connect to it.

Every time I try to do it, I get this message in syslog:
Oct 14 21:38:09 localhost bluetoothd[2246]: Unable to get Headset Voice gateway SDP record: Host is down

Relating info is below

==================== Info from bluetoothctl: ====================
bluetooth]# devices
Device 00:1B:66:03:C4:66 MOMENTUM M2 AEBT
bluetooth]# info 00:1B:66:03:C4:66
Device 00:1B:66:03:C4:66
        Name: MOMENTUM M2 AEBT
        Alias: MOMENTUM M2 AEBT
        Class: 0x240404
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: yes
        UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific (1ddce62a-ecb1-4455-8153-0743c87aec9f)
        Modalias: bluetooth:v0082p004Bd010E

==================== Info from hciconfig ====================
$ sudo hciconfig -a
[sudo] password for dimanne:
hci0: Type: Primary Bus: USB
        BD Address: 5C:F3:70:73:F2:B1 ACL MTU: 1021:8 SCO MTU: 64:1
        UP RUNNING PSCAN ISCAN
        RX bytes:14866 acl:33 sco:0 events:2022 errors:0
        TX bytes:17848 acl:33 sco:0 commands:1639 errors:0
        Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH SNIFF
        Link mode: SLAVE ACCEPT
        Name: 'impedance #1'
        Class: 0x1c0104
        Service Classes: Rendering, Capturing, Object Transfer
        Device Class: Computer, Desktop workstation
        HCI Version: 4.0 (0x6) Revision: 0x1000
        LMP Version: 4.0 (0x6) Subversion: 0x220e
        Manufacturer: Broadcom Corporation (15)

hci1: Type: Primary Bus: USB
        BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1
        DOWN
        RX bytes:2926 acl:0 sco:0 events:161 errors:0
        TX bytes:5699 acl:0 sco:0 commands:157 errors:0
        Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH SNIFF
        Link mode: SLAVE ACCEPT

==================== rfkill: ====================
$ rfkill list
1: hci1: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

==================== Info from dmesg: ====================
$ dmesg | grep -i blue
[ 5.170808] Bluetooth: Core ver 2.21
[ 5.170819] Bluetooth: HCI device and connection manager initialized
[ 5.170821] Bluetooth: HCI socket layer initialized
[ 5.170822] Bluetooth: L2CAP socket layer initialized
[ 5.170826] Bluetooth: SCO socket layer initialized
[ 5.185923] Bluetooth: hci0: BCM: chip id 63
[ 5.186665] Bluetooth: hci1: BCM: chip id 63
[ 5.202506] Bluetooth: hci0: impedance #2
[ 5.203150] Bluetooth: hci1: ChromeLinux_5818
[ 5.203498] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 5.203670] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cb.hcd failed with error -2
[ 5.203671] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not found
[ 5.204662] Bluetooth: hci1: BCM20702A1 (001.002.014) build 0000
[ 5.204671] bluetooth hci1: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
[ 5.204671] Bluetooth: hci1: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found
[ 11.359871] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 11.359872] Bluetooth: BNEP filters: protocol multicast
[ 11.359874] Bluetooth: BNEP socket layer initialized
[ 34.046364] Bluetooth: RFCOMM TTY layer initialized
[ 34.046368] Bluetooth: RFCOMM socket layer initialized
[ 34.046371] Bluetooth: RFCOMM ver 1.11
[ 1193.523500] Bluetooth: hci0: BCM: chip id 63
[ 1193.539525] Bluetooth: hci0: BCM20702A
[ 1193.540524] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 1193.540535] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cb.hcd failed with error -2
[ 1193.540536] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not found
[ 1575.051358] Bluetooth: Inquiry failed: status 0x12
[ 1593.226346] Bluetooth: Inquiry failed: status 0x12
[ 1684.104314] Bluetooth: Inquiry failed: status 0x12
[ 1694.087408] Bluetooth: Inquiry failed: status 0x12

================================================================================
pulseaudio-module-bluetooth is installed:
dpkg -l | grep pulseaudio-module-bluetooth
ii pulseaudio-module-bluetooth 1:9.0-2ubuntu2 amd64 Bluetooth module for PulseAudio sound server

My config /etc/bluetooth/audio.conf is here - http://pastebin.com/Yh3QtKVA

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: pulseaudio 1:9.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dimanne 14105 F.... pulseaudio
 /dev/snd/controlC0: dimanne 14105 F.... pulseaudio
CurrentDesktop: KDE
Date: Fri Oct 14 21:28:54 2016
InstallationDate: Installed on 2014-07-05 (832 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to yakkety on 2016-10-09 (4 days ago)
dmi.bios.date: 01/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0701
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X79-DELUXE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd01/07/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX79-DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
DimanNe (dimanne) wrote :
Revision history for this message
Luke Yelavich (themuso) wrote : Re: [Bug 1633583] [NEW] Can not connect to Bluetooth headset

Is it possible that the issue you are experiencing is similar to bug 1574324? One way to be sure is to try the potential fix that I have given in one of my last few comments on that bug.

Thanks.

Revision history for this message
Jeremy (wa113y3s) wrote :

DimanNe
See https://workingninja.com/installing-asus-bt400-raspberry-pi-raspbian-wheezy
It will show how to get the firmware needed for the broadcom bluetooth device and see if the issue still exists after the firmware install

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

Changed in pulseaudio (Ubuntu):
status: New → Incomplete
Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in pulseaudio (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in bluez (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.