New answers tagged

0

I've just remembered that it might be a weird Fn-Key combination that might have disabled bluetooth. I went through them and accidentially enabled airplane mode after bluetooth broke. Then I switched Wifi + Bluetooth back on and it works again. I have no clue what happened, but I guess Bluetooth was just disabled by software.


0

To add to 1nfern0's answer, pactl info was giving me a connection failure after following all the steps. I got around it by running: systemctl --user --now enable pipewire pipewire-pulse. You may also need to restart your system once.


0

Edit /etc/init.d/bluetooth and make sure ControllerMode is ControllerMode = dual If you needed to change it, make sure to restart your bluetooth service with sudo /etc/init.d/bluetooth restart


0

If you want to connect beats devices to your Ubuntu system, then you’ll need to set up Bluetooth manager. sudo apt update sudo apt install bluez bluez-tools sudo apt install blueman sudo reboot


0

you need to first disable the HSP/HSF profile if you're not using a mic. In /etc/bluetooth/audio.conf (create it if it doesn't exist), add this line to the [General] section: Disable=Headset Then restart the bluetooth service via : systemctl restart bluetooth.service Now we need to disable auto switching to HSP profile on call events, because call apps ...


0

For Airpods devices download and run https://github.com/delphiki/AirStatus with: git clone git@github.com:delphiki/AirStatus.git cd AirStatus pip3 install bleak python3 main.py


0

My solution is probably related to the first answer in this thread. After trying a couple of configurations I found on the net, nothing worked for me. Then I thought maybe my WiFi signal is clashing with the Bluetooth signal, and voila - it worked. Just switch off your WiFi adapter and it should work. However, if you need to use your WiFi then I suspect the ...


2

≥ 2021: with pipewire Pipewire supports APT-X through libfreeaptx0. To install it use the instruction of the pipewire-debian ppa, in summary: sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream sudo apt install gstreamer1.0-pipewire libpipewire-0.3-{0,dev,modules} libspa-0.2-{bluetooth,dev,jack,modules} pipewire{,-{audio-client-libraries,pulse,...


1

Perhaps you don't need aptX - as there is sbc-xq Recently the 'lifehack' sbc-xq has been added to linux. According to this blog audio quality of SBC XQ is comparable to aptX HD. Perhaps you want to give it a try. On my machine, I could choose between sbc and sbc-xq with the help of the blueman-manager.


0

I've installed Pipewire (this commands are for Ubuntu 21.04, but they can be easily adapted to previous versions of Ubuntu). install PPA with this commands: sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream sudo apt-get update Install pipewire and several related utilities sudo apt install pipewire pipewire-pulse \ pipewire-tests pipewire-...


0

After 5 days of trying I finally got it to work for me. What I did is firstly I deleted all of the .hcd files from /lib/firmware/brcm (used sudo nautilus file manager) then very important to download the correct files from given link. Go to repo winterheart/broadcom-bt-firmware and download the file BCM43142A0-0a5c-216c.hcd (according your Bluetooth chip-...


1

I like Jerguš's answer, but I don't want to compile c code. Here is the equivalent one-line bash echo -ne "\x10\xff\x0b\x1e\x00\x00\x00" | sudo tee /dev/[the device] Even better, this can be automatized! Create a file /etc/udev/rules.d/70-logi-k380.rules with the folloing line ACTION=="add", SUBSYSTEM=="hidraw", KERNEL=="...


1

I know this is a quite old question. service command worked for me. To stop the service - service bluetooth stop To start the service - service bluetooth start


0

Turns out the issue is caused by Bluez contending with the headset, for the right to connect A2DP first. Some headsets don't handle such crossovers well -- in this case, the confusion manifests as the headset taking several seconds to respond to AVDTP commands. The result is that, when PulseAudio needs to urgently route audio, it seems it notices A2DP isn't ...


0

Ubuntu 21.10 will include pulseaudio 15 pulseaudio 1:15.0+dfsg1-1ubuntu2 pulseaudio-module-bluetooth 1:15.0+dfsg1-1ubuntu2 pulseaudio-utils 1:15.0+dfsg1-1ubuntu2


0

The Good News The latest PulseAudio includes support for aptX. This is version 15.0 released on 2021-07-27. Support for LDAC and AptX bluetooth codecs, plus "SBC XQ" (SBC with higher-quality parameters) PulseAudio now supports the LDAC and AptX codecs for A2DP. In order to use them (...) The Bad News Ubuntu 20.04 is running version 13.99.1. $ ...


0

Just installed Ubuntu on to my Raspberry Pi 4 (8GB). But I hate wires, so I want to connect my BT keyboard and mouse. However I get the [Please plug in dongle] message when I open by BT settings. I have also tried updating the software and firmware as well as commands such as sudo systemctl restart bluetooth service bluetooth restart when I run service ...


0

yes i have similar bluetooth csr 5.0 and ubuntu os 20.04 . I have also tried everything you've mentioned above i doesn't work for me either. i've tried few more methods/patches. it seems csr bt with ID 0a12:0001 are cloned products. and that's why this product are only tested for windows.


0

mpris-proxy is available in bluez, path /usr/lib/bluetooth/mpris-proxy. I would also suggest looking at https://wiki.archlinux.org/title/MPRIS#Bluetooth for automatically starting the service.


1

Please run the command: rfkill list all You will see something like this: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 48: hci0: Bluetooth Soft blocked: no Hard blocked: no Take note of the device identifier values; in this case, 0, 1 and 48. Toggle the bluetooth off: sudo ...


0

Run sudo btmgmt [mgmt]# info (information obtained) [mgmt]# select hci0 Selected index 0 [hci0]# discov no [hci0]# exit If the name of the device that you get is different from hci0 you should use that. You can check with # info (under current settings) that the change took place. The same can be achieved with sudo hciconfig hci0 pscan Check with hciconfig ...


0

The issue you are facing is not related to the Bluetooth timeout but more likely the USB auto suspend feature built into the kernel. I am running Arch and i have a Mx master 3 and i aslo experienced similar issue to what you described. This is how i went about fixing it: run command to find out the id of your bluetooth module $ lsusb -vt Bus 07.Port 1: ...


0

I had a bluetooth keyboard, which, after about 5 minutes of use, the connection just drops. I can't simply reconnect and had to restart PC and/or keyboard to rereconnect. It was fixed by hanging a Bluetooth dangle only 20 cm away from the keyboard. This required a USB extension cable in my case to get the Bluetooth dangle that close.


0

Remove the device on Pulse Audio Bluetooth Devices Kill pulse audio and restart the Bluetooth service sudo killall pulseaudio && sudo service bluetooth restart


3

This command seemed to work on a later version of Ubuntu (18.04 LTS). sudo systemctl restart bluetooth and then enter your password.


1

If you are using Ubuntu 20.04, I would recommend to replace Pulseaudio with Pipewire. It will work with all your apps, because it aims to replace both PulseAudio and JACK, by providing a PulseAudio-compatible server implementation and ABI-compatible libraries for JACK clients.. I run Ubuntu 20.04.3 and Pipewire runs very stable so far. My bluetooth headset ...


0

If you are using Ubuntu 20.04, I would recommend to replace Pulseaudio with Pipewire. It will work with all your apps, because it aims to replace both PulseAudio and JACK, by providing a PulseAudio-compatible server implementation and ABI-compatible libraries for JACK clients.. I run Ubuntu 20.04.3 and Pipewire runs very stable so far. My bluetooth headset ...


0

I didn't have any luck with /var/lib/gdm3/.config/pulse/client.conf or /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket or /var/lib/gdm3/.config/pulse/default.pa - I kept seeing Debian-gdm's pulseaudio process. What worked for me was the link from https://wiki.debian.org/BluetoothUser/a2dp#Refused_to_switch_profile_to_a2dp_sink:...


0

After a bit of digging I was able to sove this issue for myself which involved connecting a bluetooth audio device. For me it was specifically a JBL Charge4. The solution was to install the pulseaudio Bluetooth module and restart it: sudo apt install pulseaudio-module-bluetooth pulseaudio -k pulseaudio --start Then when I try to pair I no longer get the ...


0

I occasionally get this issue. Though I don't know the root reason for it I normally reboot my laptop, select the drop down settings menu in the upper right hand side of the screen, which has always displayed bluetooth as on at the top, I click the menu to Turn it off: Then go to the main setting menu to turn it back on. Usually last for a few days.


Top 50 recent answers are included