Can not pair with bluetooth headphones

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

Bug Description

I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 wireless aebt).
(If it matters, I *CAN* pair and use it on another laptop with Linux and with my android smartphone. So headset itself is working well.)

Here is how I try to pair:
$ bluetoothctl
[NEW] Controller 54:27:1E:33:4B:85 impedance [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 54:27:1E:33:4B:85 Discovering: yes
[bluetooth]# scan on

I tried to put my headset in pairing mode just before and after issuing "scan on" command. It ends up with nothing - I waited for 3-5 minutes. For example, my smartphone pairs with the headset within 5-15 seconds, my laptop pairs with the headset within about 30 seconds.

=================================================================

Here is info

$ hciconfig -a
hci0: Type: Primary Bus: USB
        BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1
        UP RUNNING PSCAN ISCAN
        RX bytes:4475 acl:0 sco:0 events:565 errors:0
        TX bytes:7214 acl:0 sco:0 commands:487 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'
        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)

=================================================================

rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

=================================================================

Bluez packages installed:
$ dpkg -l | grep bluez
ii bluez
ii bluez-btsco
ii bluez-cups
ii bluez-hcidump
ii bluez-obexd
ii bluez-tools
ii libkf5bluezqt-data
ii libkf5bluezqt6:amd64
ii qml-module-org-kde-bluezqt:amd64

=================================================================

$ dmesg | grep -i blue
[ 4.632406] Bluetooth: Core ver 2.21
[ 4.632414] Bluetooth: HCI device and connection manager initialized
[ 4.632416] Bluetooth: HCI socket layer initialized
[ 4.632417] Bluetooth: L2CAP socket layer initialized
[ 4.632420] Bluetooth: SCO socket layer initialized
[ 4.644619] Bluetooth: hci0: BCM: chip id 63
[ 4.660554] Bluetooth: hci0: impedance
[ 4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 4.661798] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
[ 4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found
[ 15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.061604] Bluetooth: BNEP filters: protocol multicast
[ 15.061606] Bluetooth: BNEP socket layer initialized
[ 48.001553] Bluetooth: RFCOMM TTY layer initialized
[ 48.001558] Bluetooth: RFCOMM socket layer initialized
[ 48.001562] Bluetooth: RFCOMM ver 1.11
[ 615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd intel_cstate input_leds intel_rapl_perf 8021q garp mrp stp serio_raw llc b43 mac80211 snd_hda_codec_realtek snd_hda_codec_generic

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: bluez 5.41-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Jan 7 22:36:22 2017
InstallationDate: Installed on 2014-07-05 (917 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed root=UUID=6cdd6da7-49a5-4892-8a76-48d290860bcf ro acpi=force apm=power_off quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to yakkety on 2016-10-09 (89 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
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1
  UP RUNNING PSCAN ISCAN
  RX bytes:3452 acl:0 sco:0 events:379 errors:0
  TX bytes:6067 acl:0 sco:0 commands:332 errors:0
rfkill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

Revision history for this message
DimanNe (dimanne) wrote :
DimanNe (dimanne)
description: updated
Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

Hey,

Thanks for the report. I will mark it as "needs information" because I need a follow up from your side. Once I get the log files I ask about below I will change the status to further.

- what kind of Ubuntu version is installed on the Linux computer that works just wine with your headset?

Also, could you capture a somewhat more verbose logs. I would love to see at least a HCI trace. You can capture it with sudo btmon --write ~/hcitrace.snoop. Just start it and then try to pair with your headset. Also please do not make the test case really long so that it is easier to understand the output :) Finally please read also https://wiki.ubuntu.com/DebuggingBluetooth to understand how different logs for BT debugging can be captured.

Thanks.

Changed in bluez (Ubuntu):
status: New → Incomplete
Changed in bluez (Ubuntu):
assignee: nobody → Konrad Zapałowicz (kzapalowicz)
Revision history for this message
Jeremy (wa113y3s) wrote :

Konrad, the bluetooth device in this computer needs the firmware to even be able find devices while scanning. Jesse Sung made hex2hcd to convert the windows firmware with .hex filenames to something that can be used in Linux. Pilot6 wrote this http://askubuntu.com/a/632348/300665 as a general guide

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 bluez (Ubuntu):
assignee: Konrad Zapałowicz (kzapalowicz) → nobody
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.