I tried pairing a JBL Flip 5 with my Dell Laptop running version 22.04. I got a Connection Failed: br-connection-profile-unavailable error message when attempting to connect. I had a feeling a Bluetooth speaker would suck to set up, just like a wireless printer, and I was correct. If you don't have a lot of hours to waste stay away from these speakers.
1 Like
Do you have a bluetooth adapter? lsusb will tell you.
Do you get any messages in dmesg | grep Blue?
Is it blocked? sudo rfkill list should show no on both hard, soft
I pair with a BOSE SoundLink Mini speaker, no issues.
1 Like
It looks like I have the adapter-
jim@jim-Latitude-E5530-non-vPro:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0c45:643f Microdia Dell Integrated HD Webcam
Bus 001 Device 003: ID 413c:8197 Dell Computer Corp. BCM20702A0 Bluetooth Module
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
dmesg command FAILED-
dmesg: read kernel buffer failed: Operation not permitted
It looks like it isn't blocked-
1: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Thanks for trying to help. At first Bluetooth Manager detected the speaker, now it won't detect the speaker even when it's in pairing mode. I got it to work for awhile on my other laptop running Mate 22.04. It's a shame they can't engineer Bluetooth devices that are user friendly and work without wasting hours trying to set them up. It's a lot less hassle using hardwired devices.
1 Like
try sudo dmesg | grep Blue
also check in /lib/firmware/brcm/ if you have the module BCM20702A0
1 Like
That command worked:
7.061299] Bluetooth: Core ver 2.22
[ 7.061339] Bluetooth: HCI device and connection manager initialized
[ 7.062476] Bluetooth: HCI socket layer initialized
[ 7.062481] Bluetooth: L2CAP socket layer initialized
[ 7.062491] Bluetooth: SCO socket layer initialized
[ 7.273082] Bluetooth: hci0: BCM: chip id 63
[ 7.274079] Bluetooth: hci0: BCM: features 0x07
[ 7.290082] Bluetooth: hci0: jim-Latitude-E5530-non-vPro
[ 7.290090] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 7.292039] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 7.292046] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-413c-8197.hcd'
[ 7.292048] Bluetooth: hci0: BCM: 'brcm/BCM-413c-8197.hcd'
[ 19.081288] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 19.081294] Bluetooth: BNEP filters: protocol multicast
[ 19.081299] Bluetooth: BNEP socket layer initialized
[ 21.278432] Bluetooth: RFCOMM TTY layer initialized
[ 21.278442] Bluetooth: RFCOMM socket layer initialized
[ 21.278449] Bluetooth: RFCOMM ver 1.11
1 Like
Seems it could not find BCM20702A1 (001.002.014)
this site has plenty of Broadcom Bluetooth drivers
try broadcom-bt-firmware/README.md at master · winterheart/broadcom-bt-firmware · GitHub
(read the details, you may have to bring in a few drivers so that BT works)
1 Like
I used the command prompts from the link you sent and here got these results-
[ 7.061299] Bluetooth: Core ver 2.22
[ 7.061337] NET: Registered PF_BLUETOOTH protocol family
[ 7.061339] Bluetooth: HCI device and connection manager initialized
[ 7.062476] Bluetooth: HCI socket layer initialized
[ 7.062481] Bluetooth: L2CAP socket layer initialized
[ 7.062491] Bluetooth: SCO socket layer initialized
[ 7.273082] Bluetooth: hci0: BCM: chip id 63
[ 7.274079] Bluetooth: hci0: BCM: features 0x07
[ 7.290082] Bluetooth: hci0: jim-Latitude-E5530-non-vPro
[ 7.290090] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 7.292039] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 7.292046] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-413c-8197.hcd'
[ 7.292048] Bluetooth: hci0: BCM: 'brcm/BCM-413c-8197.hcd'
[ 19.081288] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 19.081294] Bluetooth: BNEP filters: protocol multicast
[ 19.081299] Bluetooth: BNEP socket layer initialized
[ 21.278432] Bluetooth: RFCOMM TTY layer initialized
[ 21.278442] Bluetooth: RFCOMM socket layer initialized
[ 21.278449] Bluetooth: RFCOMM ver 1.11
jim@jim-Latitude-E5530-non-vPro:~$ sudo dmesg | grep -i bluetooth | grep -i
Usage: grep [OPTION]... PATTERNS [FILE]...
Try 'grep --help' for more information.
jim@jim-Latitude-E5530-non-vPro:~$ sudo dmesg dmesg | grep -i bluetooth
dmesg: bad usage
Try 'dmesg --help' for more information.
jim@jim-Latitude-E5530-non-vPro:~$ sudo dmesg | grep -i bluetooth | grep -i firmware
[ 7.292039] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
why do you have 2 dmesg in the last command?
sudo dmesg | grep -i bluetooth | grep -i firmware should give you this line
[ 7.292039] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
I probably had it in that line because I'm a Terminal neophyte with limited knowledge about file paths and the correct syntax. I only know how to copy and paste and I must have screwed it up.
I tried it again and got:
jim@jim-Latitude-E5530-non-vPro:~$ sudo dmesg | grep -i bluetooth
[ 7.061299] Bluetooth: Core ver 2.22
[ 7.061337] NET: Registered PF_BLUETOOTH protocol family
[ 7.061339] Bluetooth: HCI device and connection manager initialized
[ 7.062476] Bluetooth: HCI socket layer initialized
[ 7.062481] Bluetooth: L2CAP socket layer initialized
[ 7.062491] Bluetooth: SCO socket layer initialized
[ 7.273082] Bluetooth: hci0: BCM: chip id 63
[ 7.274079] Bluetooth: hci0: BCM: features 0x07
[ 7.290082] Bluetooth: hci0: jim-Latitude-E5530-non-vPro
[ 7.290090] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 7.292039] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 7.292046] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-413c-8197.hcd'
[ 7.292048] Bluetooth: hci0: BCM: 'brcm/BCM-413c-8197.hcd'
[ 19.081288] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 19.081294] Bluetooth: BNEP filters: protocol multicast
[ 19.081299] Bluetooth: BNEP socket layer initialized
[ 21.278432] Bluetooth: RFCOMM TTY layer initialized
[ 21.278442] Bluetooth: RFCOMM socket layer initialized
[ 21.278449] Bluetooth: RFCOMM ver 1.11
No worries, we all started as neophytes ...
download BCM20702A1-413c-8197.hcd from the link I sent you, it will go into ~/Downloads
cd Downloads, sudo cp BCM20702A1-413c-8197.hcd /lib/firmware/brcm/
in essence, you are adding a firmware file into that dir.
Reboot and see if sudo dmesg | grep Blue does not complain about patch file not found,
then test bluetooth.
4 Likes
The problem seemed to rectify itself because the Flip 5 connects fine now. I didn't have to download the firmware file. Perhaps I wasn't using the proper Flip 5 button combination to activate discovery mode during my first few attempts or perhaps rebooting the computer after taking a break corrected the problem.
The quick start manual included with the device uses icons because it's an internationally sold product which didn't help me much. This was my first attempt at using a bluetooth device so I'm way below the learning curve. Please forgive my poor attitude at the beginning of this thread. It's frustrating for some of us old dogs to learn new tricks. Thank you again pavlos_kairis!
1 Like