![]() See /etc/dbus-1/system.d/nf for reference. Add your user to the lp group, then restart pulseaudio. It can also be due to permission, especially if starting pulseaudio as root allows you to connect. Install it if it missing, then restart pulseaudio. This may be due to the pulseaudio-bluetooth package not being installed. To further investigate, check the unit status of rvice or have a look at the log as follows:īluetoothd: a2dp-sink profile connect failed for 00:1D:43:6D:03:26: Protocol not available You might see the following error in bluetoothctl:Īttempting to connect to 00:1D:43:6D:03:26įailed to connect: You may need to turn off BlueTooth while you run this command. If pairing fails, you can try enabling or disabling SSPMode with: There may be configuration options to remove the need to do this each time, but neither pairing nor trusting induce automatic connecting for me. Make sure to run bluetoothctl as root and connect the device manually. The menu seems to be created as soon as the receiver recognizes the device. Selected audio profile, but headset inactive and audio cannot be redirectedĭeceptively, this menu is available before the device has been connected annoyingly it will have no effect. $ pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez list-codecs Where a list of available codecs can be obtained by: $ pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez switch-codec '"sbc"' If you suspect the bad sound quality is due to a poor bluetooth connection, you might compensate for it by switching to a lower bit-rate and lower audio quality codec such as SBC or aptX using pactl: See #Switch between HSP/HFP and A2DP setting to solve the problem. If you experience bad sound quality with your headset, it could in all likelihood be because your headset is not set to the correct profile. see #Switch between HSP/HFP and A2DP setting for additional information. Note: Many users report frustration with getting A2DP/Bluetooth Headsets to work. If everything works correctly, you now have a separate output device in PulseAudio. If you are getting a connection error retry by killing existing PulseAudio daemon first:įinally, if you want to automatically connect to this device in the future: We will now use that MAC address to initiate the pairing:Īfter pairing, you also need to explicitly connect the device (if this does not work, try the trust command below before attempting to connect): Shows a device that calls itself "Lasmex LBT10" and has MAC address "00:1D:43:6D:03:26". Now make sure that your headset is in pairing mode. To be greeted by its internal command prompt. For troubleshooting and more detailed explanations of bluetoothctl see the Bluetooth article. Now we can use the bluetoothctl command line utility to pair and connect. Note: Before continuing, ensure that the bluetooth device is not blocked by rfkill.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |