Bluetooth not working often in 20.04
Some of the answers work sometimes, and sometimes a combination of them and rebooting my system seem to magically help.
Symptoms of my earphones not connecting through bluetooth anymore:
- Using the GUI, while clicking on the connect on/off button to turn it on, it inmediatelly turns itself off.
- Using bluetoothctl, removing the device, trusting the device again and trying to pair just goes on until it fails due to my device turning off being so long trying to pair.
Might be related to some of these packages:
I’d like help in debugging this problem, I guess I’m tired of rebooting a few times every few days just to get my earphones working.
Edit: I’m using the tp link ub 400 bluetooth adapter.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 003: ID 1b1c:1b20 Corsair Corsair STRAFE RGB Gaming Keyboard Bus 003 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Edit 2: To clarify compared to this other question:
hci0: Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:15 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:718 acl:0 sco:0 events:54 errors:0 TX bytes:3673 acl:0 sco:0 commands:53 errors:0 As you can see, my device shows running compared to the other question in which it shows is DOWN.
Linux Bluetooth Not Working Troubleshooting
Issues with Bluetooth connectivity in Linux go way back in time. Many users have experienced issues sharing their documents. Others have had issues connecting their PCs to their handhelds or headphones to enjoy their desired playlists or bingeing on videos. This issue still pertains to the recently released Ubuntu LTS versions. The Linux forums are full of user complaints regarding this matter. So, in this article, we provide the solution to this issue and resolve it once and for all.
Determine If Bluetooth Is Working
First and foremost, check if our Bluetooth service is up and running. Despite being a flexible and powerful operating system, Ubuntu has its contretemps with Bluetooth connectivity. One of the common ones is the need to reconnect our Bluetooth when our computer wakes up from sleep. This can disturb the flow of data transfer on whatever task we were performing.
So, we check if the Bluetooth service at the backend is running properly. For that, we type in the following command:
As the status of connectivity suggests, our Bluetooth tethering is inactive. Hence, we should enable it so that it automatically starts when we boot up using the command:
After that, start the session again by using systemctl command as shown below:
And to ensure that it starts automatically upon boot, we type:
If you still have a problem connecting, it is always a good idea to check if your device is in the “trusted devices” list on your system. Also, re-pairing the Bluetooth device resolves the issue sometimes, so be sure to try these options to be on the safe side.
If the procedure demonstrated above did not work, that means our Bluetooth connection is probably being interrupted, and it needs to restart. Then, we continue in the sequential method demonstrated below.
First, we restart Bluetooth using the following command:
Having done that, we load the modules from the kernel using the command:
If the module is not loaded, you can use this link to find the command that enables it. Now, we enable Bluetooth by using the same command:
This should enable your Bluetooth device.
Using Bluez
The standard procedure to enable Bluetooth on your device is to install “Bluez”. Bluez is the official Bluetooth protocol software for Ubuntu and the other Linux distributions, such as Kali and Debian. If you happen to have Bluetooth connectivity issues on those distros, using Bluez will resolve your issue for those systems.
If your Bluetooth is not working, it is likely that Bluez is not properly responding or is simply outdated. In any case, we can uninstall Bluez by using the command:
And once it is uninstalled, we reinstall the package by using the command:
The primary purpose of this approach was so we can troubleshoot the prevalent problem in our Bluetooth software protocol. It may have some missing or corrupted packages which could be the root of the issue. In any case, once we have reinstalled the Bluez package, we have the verified files and an updated version on our system.
As we can see, the latest version of Bluez is installed in our system.
Finally, we use the enable command to activate the Bluetooth tethering feature:
Now, start Bluetooth on your system:
And finally, check the activity status using:
Using Update
We can enable our Bluetooth feature using the same old update option traditional to Linux users. Try this method in case the Bluez reinstallation method did not work, though it’s most likely it will work.
First, type in the following command to update your system:
Having done that, run the upgrade command to install the required packages and repositories:
Next, start the Bluetooth by typing in the following command:
Finally, we check the status of our Bluetooth connectivity by typing in the following instruction:
Now, we can see that our Bluetooth service is up and running.
Finally, to keep our Bluetooth connectivity smooth, we use the “rfkill” command which will unblock the feature of Bluetooth:
Other Reasons for Connectivity Issues
There can be several reasons why you cannot connect a Bluetooth device to your system such as:
“Unrecognized hardware”
The Dongle or device may not be recognized by the system. This issue usually arises because the drivers for the respective adapter are not installed. Some adapters are also not recognized by Linux. In that case, you should find a compatible adapter.
“The computer does not have a Bluetooth adapter”
Some computers do not come with a Bluetooth adapter. In that case, you can purchase an adapter and use it for Bluetooth.
“Untrusted or blocked connection”
There are some Bluetooth devices that block the connections by default. Or they may require you to change certain settings for connections to be made available. So ensure your system is set to allow conditions. This is a frequent case in Linux. You can check up those settings manually or using the terminal.
Conclusion
Whether enjoying your favorite playlist, bingeing on Netflix shows and movies, or straight up transferring documents and media, an issue in Bluetooth connectivity can impede our data transfer or bar us from that refreshing break we were looking forward to. Therefore, it is desirable to troubleshoot all connectivity issues so you can have a peaceful and trouble-free interaction with your system. An option is the use of the Bluez software to enable your Bluetooth connectivity. We hope your issue was resolved, and there are no further connectivity issues.
Bluetooth is not working ubuntu 18.04 LTS
This problem seems to be common but i tried all the solutions proposed in previous questions with no luck. my Bluetooth just keep searching for devices and it can’t detect them. output for rfkill list :
0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no [ 1.725292] usb 2-4: Product: Bluetooth Radio [ 22.987302] Bluetooth: Core ver 2.22 [ 22.987324] Bluetooth: HCI device and connection manager initialized [ 22.987326] Bluetooth: HCI socket layer initialized [ 22.987328] Bluetooth: L2CAP socket layer initialized [ 22.987331] Bluetooth: SCO socket layer initialized [ 24.192938] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723 [ 24.192940] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_config.bin [ 24.262074] Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin [ 24.279971] Bluetooth: hci0: rom_version status=0 version=1 [ 24.279990] Bluetooth: hci0: cfg_sz 0, total size 22496 [ 31.827382] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 31.827384] Bluetooth: BNEP filters: protocol multicast [ 31.827387] Bluetooth: BNEP socket layer initialized [ 69.606019] Bluetooth: RFCOMM TTY layer initialized [ 69.606024] Bluetooth: RFCOMM socket layer initialized [ 69.606029] Bluetooth: RFCOMM ver 1.11 [ 133.549264] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 149.425182] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 165.416224] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 195.195275] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 210.934271] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 227.034314] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 242.896317] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 259.043361] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 274.227449] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 289.383402] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 305.511470] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 321.387453] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 337.520479] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 353.398532] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 369.458540] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 385.298590] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 401.410629] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 417.274763] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 433.471653] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 449.380746] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 465.528845] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 481.409819] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 497.533809] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 513.404936] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 529.532964] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 545.408026] Bluetooth: hci0: last event is not cmd complete (0x0f) 0a:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:2231] Kernel driver in use: rtl8723be Kernel modules: rtl8723be Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0bda:b001 Realtek Semiconductor Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub after trying too many solution i erased the whole disk and installed a fresh 18.04 LTS version (i’m using HP 15 Notebook) but still the same problem.