Bluethooth didn`t work

[mkikets]

Can somebody help me?

I have (ASUS X555UB) laptop with "Win10" and "Linux Mint 19 Tara Cynnamon Edition" in dual boot

On windows i have properly worked bluetooth driver, which can see new devices, connect to paired and other bluetooth stuff.

But on Mint I cant do that...

And, I don`t even know what to do...

I followed some instructions, like:

• Install bluemon
• Reinstall bluez
• Downgrade kernel or Mate version

But this didn`t helps me.

[pishta]

Im asking same question. I deleted blueberry, installed blueman (sudo apt-get install blueman) and I can get blueman to see device, I can pair it and it even beeps and says connected, but the device never leaves flashing discovery mode, and I cannot get any sound from it (BT speaker) I have trusted it and even tried to send it a file, didn't do anything. In sound properties, it only listed internal headphone and internal speaker, no Bluetooth speaker found outside of blueman. This is crazy, BT is here to stay and we cant get it to work on the newest Mint? Dell internal Broadcom BT 1/2 height board using mints BC proprietary drivers. Wifi works fine. Ill use Mint 17 if its Bluetooth works......

[JeremyB]

If you need help with bluetooth issues, please include results from terminal for

Code: Select all

lsusb; lspci -nnk | grep -iA3 net; dmesg | egrep -i 'blue|firm'

Some Dell bluetooth modules need to be switched to HCI mode in Windows or we can try to use usb-modeswitch in Linux, a lot of broadcom bluetooth devices need firmware to function in linux and broadcom does not allow Linux Distros to distribute this firmware, but there is a workaround

[mchandler]

I had a similar problem and here's how I fixed it.

If you haven't already installed Pulse Audio Volume Control (PAVC), do so.
After you install PAVC, install the Bluetooth module using this command:
sudo apt-get install pulseaudio-module-bluetooth

Pair your BT headphones or speaker.
Launch Spotify (for example) and PAVC.
On PAVC's Playback tab, click the device button and select your speaker/headphones.
On PAVC's Output Devices tab, you should see your speaker/headphones.
On PAVC's Configuration tab, select the High Fidelity Playback (A2DP sink) profile.

[mkikets]

If you need help with bluetooth issues, please include results from terminal for

Code: Select all

lsusb; lspci -nnk | grep -iA3 net; dmesg | egrep -i 'blue|firm'

Some Dell bluetooth modules need to be switched to HCI mode in Windows or we can try to use usb-modeswitch in Linux, a lot of broadcom bluetooth devices need firmware to function in linux and broadcom does not allow Linux Distros to distribute this firmware, but there is a workaround

Code: Select all

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0bda:b721 Realtek Semiconductor Corp. 
Bus 001 Device 006: ID 0bda:57de Realtek Semiconductor Corp. 
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 004: ID 1d57:fa60 Xenta 
Bus 001 Device 002: ID 2166:6649  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)
	Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:200f]
	Kernel driver in use: r8169
	Kernel modules: r8169
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723]
	Subsystem: Lite-On Communications Inc RTL8723BE PCIe Wireless Network Adapter [11ad:1723]
	Kernel driver in use: rtl8723be
	Kernel modules: rtl8723be
[    0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.062997] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.973355] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
[    0.973361] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
[    1.606772] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_26.bin (v1.26)
[    3.037734] usb 1-8: Product: Bluetooth Radio 
[   29.465691] rtl8723be: Using firmware rtlwifi/rtl8723befw_36.bin
[   29.686661] elan_i2c i2c-ELAN1000:00: Elan Touchpad: Module ID: 0x0005, Firmware: 0x0004, Sample: 0x000d, IAP: 0x000e
[   30.964328] Bluetooth: Core ver 2.22
[   30.964347] Bluetooth: HCI device and connection manager initialized
[   30.964350] Bluetooth: HCI socket layer initialized
[   30.964352] Bluetooth: L2CAP socket layer initialized
[   30.964356] Bluetooth: SCO socket layer initialized
[   30.974580] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
[   30.974581] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_config.bin
[   30.996157] bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin failed with error -2
[   30.996160] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin
[   31.005669] Bluetooth: hci0: rom_version status=0 version=1
[   31.005672] Bluetooth: hci0: cfg_sz 0, total size 22496
[   39.145009] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   39.145010] Bluetooth: BNEP filters: protocol multicast
[   39.145013] Bluetooth: BNEP socket layer initialized
[ 1040.870936] Bluetooth: RFCOMM TTY layer initialized
[ 1040.870963] Bluetooth: RFCOMM socket layer initialized

[stuboy_spain]

As a Mint newbie, I didn't entirely understand your post (I know to you, it's simple) I've just migrated from MS Win trying to preserve an old EEE901 - why not??...
Anyway, I copied and pasted the instructions for pulse and now my Broadcom Bluetooth drivers are Bluetooth 4.2 supporting and working with the device I was having problems with... Thank you.