#StackBounty: #drivers #18.04 #sound #bluetooth #headphones Ubuntu 18.04.3 Failed to connect: org.bluez.Error.Failed

Bounty: 50

I’m unable to connect my Bluetooth headset Sony MDR-XB950N1. Here are some info that might help:

  1. This is a Ubuntu 18.04.3 from scratch (first time I did some changes, so this time it’s intact)

  2. Output for: rfkill list
    0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
    1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
    
  3. Output for: dmesg | grep Blue
    [    3.779924] Bluetooth: Core ver 2.22
    [    3.779933] Bluetooth: HCI device and connection manager initialized
    [    3.779936] Bluetooth: HCI socket layer initialized
    [    3.779937] Bluetooth: L2CAP socket layer initialized
    [    3.779939] Bluetooth: SCO socket layer initialized
    [    3.927905] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
    [    4.085989] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [    4.085990] Bluetooth: BNEP filters: protocol multicast
    [    4.085992] Bluetooth: BNEP socket layer initialized
    [   51.943002] Bluetooth: RFCOMM TTY layer initialized
    [   51.943005] Bluetooth: RFCOMM socket layer initialized
    [   51.943008] Bluetooth: RFCOMM ver 1.11
    [ 3337.300487] audit: type=1107 audit(1578332620.663:53): pid=714 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=5801 label="snap.teams-for-linux.teams-for-linux" peer_pid=847 peer_label="unconfined"
    
  4. Output for: lspci -knn | grep Net -A2; lsusb
    00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:a370] (rev 10)
        Subsystem: Intel Corporation Device [8086:0034]
        Kernel driver in use: iwlwifi
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 004: ID 048d:ce00 Integrated Technology Express, Inc. 
    Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
    Bus 001 Device 006: ID 8087:0aaa Intel Corp. 
    Bus 001 Device 005: ID 04f2:b65a Chicony Electronics Co., Ltd 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    
  5. Trying over bluetoothctl:
    [NEW] Controller 38:00:25:A1:F0:85 bonavel [default]
    Agent registered
    [bluetooth]# list
    Controller 38:00:25:A1:F0:85 bonavel [default]
    [NEW] Device 04:5D:4B:96:D5:65 MDR-XB950N1
    [bluetooth]# devices
    Device 04:5D:4B:96:D5:65 MDR-XB950N1
    [bluetooth]# scan on
    Discovery started
    [bluetooth]# devices
    Device 04:5D:4B:96:D5:65 MDR-XB950N1
    [bluetooth]# pair 04:5D:4B:96:D5:65
    Attempting to pair with 04:5D:4B:96:D5:65
    [CHG] Device 04:5D:4B:96:D5:65 Connected: yes
    [CHG] Device 04:5D:4B:96:D5:65 Connected: no
    [CHG] Device 04:5D:4B:96:D5:65 Paired: yes
    Pairing successful
    [CHG] Controller 38:00:25:A1:F0:85 Discoverable: no
    [bluetooth]# trust 04:5D:4B:96:D5:65
    [CHG] Device 04:5D:4B:96:D5:65 Trusted: yes
    Changing 04:5D:4B:96:D5:65 trust succeeded
    [bluetooth]# connect 04:5D:4B:96:D5:65
    Attempting to connect to 04:5D:4B:96:D5:65
    Failed to connect: org.bluez.Error.Failed
    [bluetooth]# 
    [CHG] Controller 38:00:25:A1:F0:85 DiscoverableTimeout: 0x00000000
    [CHG] Controller 38:00:25:A1:F0:85 DiscoverableTimeout: 0x00000000
    [CHG] Controller 38:00:25:A1:F0:85 Discoverable: yes
    [bluetooth]# devices
    Device 04:5D:4B:96:D5:65 MDR-XB950N1
    [bluetooth]# connect 04:5D:4B:96:D5:65
    Attempting to connect to 04:5D:4B:96:D5:65
    Failed to connect: org.bluez.Error.Failed
    
  6. My Bluetooth Logitech M585 worked fine:
    Device E1:B5:43:77:D0:97 M585/M590
    
  7. Output of tail -f /var/log/syslog when trying to connect again over bluetoothctl:
    Jan  4 16:46:43 bonavel bluetoothd[887]: 04:5D:4B:96:D5:65: error updating services: Host is down (112)
    
  8. Output of pactl list | grep -i bluetooth
    Name: module-bluetooth-policy
        module.description = "Policy module to make using bluetooth devices out-of-the-box easier"
    Name: module-bluetooth-discover
        module.description = "Detect available Bluetooth daemon and load the corresponding discovery module"
        module.description = "Detect available BlueZ 5 Bluetooth audio devices and load BlueZ 5 Bluetooth audio drivers"
    
  9. Applied this solution and it is still not working.

  10. Applied this solution and now I was able to pair and connect, but it was unable to reproduce sound though it quickly disconnected.

  11. Output of bluetoothctl after item 10.

    [bluetooth]# info 04:5D:4B:96:D5:65
    Device 04:5D:4B:96:D5:65 (public)
        Name: MDR-XB950N1
        Alias: MDR-XB950N1
        Class: 0x00240404
        Icon: audio-card
        Paired: yes
        Trusted: no
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Headset HS                (00001131-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
        Modalias: usb:v054Cp0BEAd0102
    [bluetooth]# connect 04:5D:4B:96:D5:65
    Attempting to connect to 04:5D:4B:96:D5:65
    [CHG] Device 04:5D:4B:96:D5:65 Connected: yes
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 00000000-deca-fade-deca-deafdecacaff
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 7b265b0e-2232-4d45-bef4-bb8ae62f813d
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
    [CHG] Device 04:5D:4B:96:D5:65 UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
    [CHG] Device 04:5D:4B:96:D5:65 ServicesResolved: yes
    Connection successful
    [CHG] Controller 38:00:25:A1:F0:85 Discovering: yes
    [CHG] Controller 38:00:25:A1:F0:85 DiscoverableTimeout: 0x00000000
    [CHG] Controller 38:00:25:A1:F0:85 DiscoverableTimeout: 0x00000000
    [CHG] Controller 38:00:25:A1:F0:85 Discoverable: yes
    [CHG] Device 04:5D:4B:96:D5:65 ServicesResolved: no
    [CHG] Device 04:5D:4B:96:D5:65 Connected: no
    [CHG] Device 04:5D:4B:96:D5:65 Connected: yes
    [CHG] Controller 38:00:25:A1:F0:85 Discoverable: no
    [MDR-XB950N1]# connect 04:5D:4B:96:D5:65
    Attempting to connect to 04:5D:4B:96:D5:65
    Failed to connect: org.bluez.Error.InProgress
  1. I factory restored the headset following this instructions. Then I was able to pair and connect to it. But when I put some audio through it, it feels like there was a lot of interference with only some random very cut noises that I couldn’t even relate to what was being played. Then I was able to disconnected and connect again but now no sound is being played at all. Then after 1 min or so, the headset lost the connection.

I’ve been searching for more than 2 hours and applying all possible solutions I found, but none of them fixed my problem, so I reinstalled Ubuntu 18.04.3 from scratch.


Get this bounty!!!

#StackBounty: #lubuntu #bluetooth #18.10 #lxqt Bluetooth connection (Bluez) not working after logout (works after restart)

Bounty: 50

I use LXQT in Lubuntu 18.10 and I have a problem with keeping the Bluetooth-speaker connected to the laptop after logging out and in. It works fine after reboot though.

So, I have a solution that always works: rebooting – OR: reinstalling bluez:

sudo apt-get install --reinstall bluez

and that always works!

In any case, when my problem happens, the bluetooth is never blocked.

If I reboot or reinstall bluez there is no need to remove and add again the device, setting it to “Audio sink” is enough.


When this happens, after logging out and in:

  • The speaker is listed by blueman-manager, setting to ‘Audio Sink’ brings the error Protocol Not available.

enter image description here

In terminal:

~$ blueman-manager
_________
Load (/usr/lib/python3/dist-packages/blueman/main/PluginManager.py:60)
['PulseAudioProfile', 'Services'] 
_________
__load_plugin (/usr/lib/python3/dist-packages/blueman/main/PluginManager.py:133)
loading <class 'blueman.plugins.manager.PulseAudioProfile.PulseAudioProfile'> 
_________
pa_context_event (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:341)
1 
_________
__load_plugin (/usr/lib/python3/dist-packages/blueman/main/PluginManager.py:133)
loading <class 'blueman.plugins.manager.Services.Services'> 
blueman-manager version 2.0.5 starting
Stale PID, overwriting
_________
pa_context_event (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:341)
2 
_________
on_bluez_name_owner_changed (/usr/bin/blueman-manager:96)
org.bluez owner changed to  :1.238 
_________
get_interface_version (/usr/lib/python3/dist-packages/blueman/bluez/BlueZInterface.py:13)
Detected BlueZ 5 
_________
SetAdapter (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:271)

_________
on_adapter_changed (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerToolbar.py:83)
toolbar adapter /org/bluez/hci0 
_________
__init__ (/usr/lib/python3/dist-packages/blueman/main/Device.py:26)
caching initial properties 
_________
add_device (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:317)
adding new device 
_________
do_cache (/usr/lib/python3/dist-packages/blueman/gui/DeviceList.py:496)
Caching new device C0:28:8D:81:64:5A 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Fake False 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Trusted 0 
_________
row_update_event (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceList.py:264)
row update event Paired 1 
_________
Generate (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:173)
UE BOOM 2 
_________
pa_context_event (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:341)
3 
_________
pa_context_event (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:341)
4 
_________
on_pa_ready (/usr/lib/python3/dist-packages/blueman/plugins/manager/PulseAudioProfile.py:29)
connected 
_________
<lambda> (/usr/lib/python3/dist-packages/blueman/main/PulseAudioUtils.py:353)
1 
_________
Generate (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:173)
UE BOOM 2 
_________
Generate (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:173)
UE BOOM 2 
_________
set_op (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:85)
op: regenerating instance <ManagerDeviceMenu.ManagerDeviceMenu object at 0x7f8fd0e05e10 (blueman+gui+manager+ManagerDeviceMenu+ManagerDeviceMenu at 0x1efcb60)> 
_________
set_op (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:85)
op: regenerating instance <ManagerDeviceMenu.ManagerDeviceMenu object at 0x7f8fd0e0eee8 (blueman+gui+manager+ManagerDeviceMenu+ManagerDeviceMenu at 0x1efce40)> 
_________
unset_op (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:99)
op: regenerating instance <ManagerDeviceMenu.ManagerDeviceMenu object at 0x7f8fd0e05e10 (blueman+gui+manager+ManagerDeviceMenu+ManagerDeviceMenu at 0x1efcb60)> 
_________
Generate (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:173)
UE BOOM 2 
_________
unset_op (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:99)
op: regenerating instance <ManagerDeviceMenu.ManagerDeviceMenu object at 0x7f8fd0e0eee8 (blueman+gui+manager+ManagerDeviceMenu+ManagerDeviceMenu at 0x1efce40)> 
_________
fail (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:124)
fail org.freedesktop.DBus.Python.blueman.bluez.errors.DBusFailedError: blueman.bluez.errors.DBusFailedError: Protocol not available

/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerProgressbar.py:165: Warning: Source ID 697 was not found when attempting to remove it
  GObject.source_remove(self.gsource)

and

~$ pactl load-module module-bluetooth-discover
Failure: Module initialization failed

because it was already loaded.

Removing the device and trying to add it again: it is not found at all!


Which aspect in the normal operation of bluez – one that is available at system startup as well as by reinstalling the package – could be lost by restarting the session? – And how to avoid that loss?


UPDATE/EDIT by the OP:

[I am the OP. At some point I have deleted my account and then I came back with the same id.] I want to add that this is a Lubuntu-LXQt-specific problem. I have seen this problem in many Ubuntu and Ubuntu-based distros before 18.04, but in none since 18.x. Since 18.04 it is fixed excepting in Lubuntu-LXQt.

Details of the bluetooth adapter:

lsusb | grep Bluetooth
Bus 001 Device 013: ID 0489:e00f Foxconn / Hon Hai Foxconn T77H114 BCM2070 [Single-Chip Bluetooth 2.1 + EDR Adapter]


Get this bounty!!!

#StackBounty: #bluetooth #thinkpad airpods 2 – ubuntu 19.10 – Thinkpad x1 extreme 2 – No success on pairing

Bounty: 50

Can’t get my airpods 2 to pair successfully with my laptop. In the bluetooth menu, I see my airpods 2 but double clicking does not pair and it stays with a text of ‘Not Set Up.’

I also tried with blueman to pair but blueman always says pairing failed. Did try the trick of changing ControllerMode in bluetooth/main.conf with either dual or bredr and both failed as well.

From journalctl -f, I did find this log:

Jan 06 07:19:36 edgar-ThinkPad-X1-Extreme-2nd gnome-control-c[5489]: Setting up /org/bluez/hci0/dev_E4_76_84_72_CB_79 failed: Timeout was reached

But I don’t know why the pairing would timeout.

Not sure what else to try/do.

relevant specs:

uname -a
Linux edgar-ThinkPad-X1-Extreme-2nd 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
(Mon Jan-1 7:10:21am)-(CPU 2.9%:0:Net 60)-(edgar:~)-(1.8G:60)
> cat /etc/os-release 
NAME="Ubuntu"
VERSION="19.10 (Eoan Ermine)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 19.10"
VERSION_ID="19.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=eoan
UBUNTU_CODENAME=eoan
> hciconfig -a
hci0:   Type: Primary  Bus: USB
    BD Address: 94:E6:F7:71:FA:47  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING 
    RX bytes:4354 acl:0 sco:0 events:132 errors:0
    TX bytes:1357 acl:0 sco:0 commands:56 errors:0
    Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
    Link policy: RSWITCH SNIFF 
    Link mode: SLAVE ACCEPT 
    Name: 'edgar-ThinkPad-X1-Extreme-2nd'
    Class: 0x000000
    Service Classes: Unspecified
    Device Class: Miscellaneous, 
    HCI Version: 5.0 (0x9)  Revision: 0x100
    LMP Version: 5.0 (0x9)  Subversion: 0x100
    Manufacturer: Intel Corp. (2)

hcitool dev
Devices:
    hci0    94:E6:F7:71:FA:47


Get this bounty!!!

#StackBounty: #bluetooth #pi-4 #raspbian-buster Bluetooth headset paired and connected, but can't be selected as audio output

Bounty: 100

I’m stuck trying a pretty standard A2DP Bluetooth headset to work with Raspbian Buster on an RPi 4. I successfully paired it with the RPi and can connect it via the GUI, and the buttons on the headset can control the playback in VLC for instance. However, when I select it as an audio output in Volume Control applet, the green checkmark stays on “HDMI”, which is the other audio output I have.

I would like to keep using bluealsa (which I assume is the default on Buster) and avoid installing pulse if possible. I use the built-in BT adapter, and WiFi is disabled. AFAIK I didn’t change any audio/BT-related config files.

I’m not sure which log I could provide, for a start there’s that:

hcitool con

Connections:
    < ACL 00:15:01:02:DE:02 handle 12 state 1 lm MASTER AUTH ENCRYPT 

service bluealsa status

● bluealsa.service - BluezALSA proxy
   Loaded: loaded (/lib/systemd/system/bluealsa.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:18:37 CEST; 10min ago
 Main PID: 3789 (bluealsa)
    Tasks: 3 (limit: 4915)
   Memory: 868.0K
   CGroup: /system.slice/bluealsa.service
           └─3789 /usr/bin/bluealsa

Sep 23 20:18:37 raspberrypi systemd[1]: Started BluezALSA proxy.
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: CMD: command:+CLCC, value:(null)
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: SET: command:+CSRSF, value:0,0,0,1,0,0,0

service bluetooth status

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:07:45 CEST; 10min ago
     Docs: man:bluetoothd(8)
 Main PID: 1007 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 2.2M
   CGroup: /system.slice/bluetooth.service
           └─1007 /usr/lib/bluetooth/bluetoothd

Sep 23 20:10:32 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.24 path=/org/bluez/hci0/A2DP/SBC/Sink/1
Sep 23 20:10:33 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.28 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:48 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:50 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:11 raspberrypi bluetoothd[1007]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:16 raspberrypi bluetoothd[1007]: Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

sudo dmesg -c

[  635.803532] Bluetooth: RFCOMM TTY layer initialized
[  635.803546] Bluetooth: RFCOMM socket layer initialized
[  635.803563] Bluetooth: RFCOMM ver 1.11
[  638.100771] input: 00:15:01:02:DE:02 as /devices/virtual/input/input7
[  669.713843] input: 00:15:01:02:DE:02 as /devices/virtual/input/input8


Get this bounty!!!

#StackBounty: #bluetooth #pi-4 #raspbian-buster Bluetooth headset paired and connected, but can't be selected as audio output

Bounty: 100

I’m stuck trying a pretty standard A2DP Bluetooth headset to work with Raspbian Buster on an RPi 4. I successfully paired it with the RPi and can connect it via the GUI, and the buttons on the headset can control the playback in VLC for instance. However, when I select it as an audio output in Volume Control applet, the green checkmark stays on “HDMI”, which is the other audio output I have.

I would like to keep using bluealsa (which I assume is the default on Buster) and avoid installing pulse if possible. I use the built-in BT adapter, and WiFi is disabled. AFAIK I didn’t change any audio/BT-related config files.

I’m not sure which log I could provide, for a start there’s that:

hcitool con

Connections:
    < ACL 00:15:01:02:DE:02 handle 12 state 1 lm MASTER AUTH ENCRYPT 

service bluealsa status

● bluealsa.service - BluezALSA proxy
   Loaded: loaded (/lib/systemd/system/bluealsa.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:18:37 CEST; 10min ago
 Main PID: 3789 (bluealsa)
    Tasks: 3 (limit: 4915)
   Memory: 868.0K
   CGroup: /system.slice/bluealsa.service
           └─3789 /usr/bin/bluealsa

Sep 23 20:18:37 raspberrypi systemd[1]: Started BluezALSA proxy.
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: CMD: command:+CLCC, value:(null)
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: SET: command:+CSRSF, value:0,0,0,1,0,0,0

service bluetooth status

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:07:45 CEST; 10min ago
     Docs: man:bluetoothd(8)
 Main PID: 1007 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 2.2M
   CGroup: /system.slice/bluetooth.service
           └─1007 /usr/lib/bluetooth/bluetoothd

Sep 23 20:10:32 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.24 path=/org/bluez/hci0/A2DP/SBC/Sink/1
Sep 23 20:10:33 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.28 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:48 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:50 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:11 raspberrypi bluetoothd[1007]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:16 raspberrypi bluetoothd[1007]: Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

sudo dmesg -c

[  635.803532] Bluetooth: RFCOMM TTY layer initialized
[  635.803546] Bluetooth: RFCOMM socket layer initialized
[  635.803563] Bluetooth: RFCOMM ver 1.11
[  638.100771] input: 00:15:01:02:DE:02 as /devices/virtual/input/input7
[  669.713843] input: 00:15:01:02:DE:02 as /devices/virtual/input/input8


Get this bounty!!!

#StackBounty: #bluetooth #pi-4 #raspbian-buster Bluetooth headset paired and connected, but can't be selected as audio output

Bounty: 100

I’m stuck trying a pretty standard A2DP Bluetooth headset to work with Raspbian Buster on an RPi 4. I successfully paired it with the RPi and can connect it via the GUI, and the buttons on the headset can control the playback in VLC for instance. However, when I select it as an audio output in Volume Control applet, the green checkmark stays on “HDMI”, which is the other audio output I have.

I would like to keep using bluealsa (which I assume is the default on Buster) and avoid installing pulse if possible. I use the built-in BT adapter, and WiFi is disabled. AFAIK I didn’t change any audio/BT-related config files.

I’m not sure which log I could provide, for a start there’s that:

hcitool con

Connections:
    < ACL 00:15:01:02:DE:02 handle 12 state 1 lm MASTER AUTH ENCRYPT 

service bluealsa status

● bluealsa.service - BluezALSA proxy
   Loaded: loaded (/lib/systemd/system/bluealsa.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:18:37 CEST; 10min ago
 Main PID: 3789 (bluealsa)
    Tasks: 3 (limit: 4915)
   Memory: 868.0K
   CGroup: /system.slice/bluealsa.service
           └─3789 /usr/bin/bluealsa

Sep 23 20:18:37 raspberrypi systemd[1]: Started BluezALSA proxy.
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: CMD: command:+CLCC, value:(null)
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: SET: command:+CSRSF, value:0,0,0,1,0,0,0

service bluetooth status

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:07:45 CEST; 10min ago
     Docs: man:bluetoothd(8)
 Main PID: 1007 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 2.2M
   CGroup: /system.slice/bluetooth.service
           └─1007 /usr/lib/bluetooth/bluetoothd

Sep 23 20:10:32 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.24 path=/org/bluez/hci0/A2DP/SBC/Sink/1
Sep 23 20:10:33 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.28 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:48 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:50 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:11 raspberrypi bluetoothd[1007]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:16 raspberrypi bluetoothd[1007]: Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

sudo dmesg -c

[  635.803532] Bluetooth: RFCOMM TTY layer initialized
[  635.803546] Bluetooth: RFCOMM socket layer initialized
[  635.803563] Bluetooth: RFCOMM ver 1.11
[  638.100771] input: 00:15:01:02:DE:02 as /devices/virtual/input/input7
[  669.713843] input: 00:15:01:02:DE:02 as /devices/virtual/input/input8


Get this bounty!!!

#StackBounty: #bluetooth #pi-4 #raspbian-buster Bluetooth headset paired and connected, but can't be selected as audio output

Bounty: 100

I’m stuck trying a pretty standard A2DP Bluetooth headset to work with Raspbian Buster on an RPi 4. I successfully paired it with the RPi and can connect it via the GUI, and the buttons on the headset can control the playback in VLC for instance. However, when I select it as an audio output in Volume Control applet, the green checkmark stays on “HDMI”, which is the other audio output I have.

I would like to keep using bluealsa (which I assume is the default on Buster) and avoid installing pulse if possible. I use the built-in BT adapter, and WiFi is disabled. AFAIK I didn’t change any audio/BT-related config files.

I’m not sure which log I could provide, for a start there’s that:

hcitool con

Connections:
    < ACL 00:15:01:02:DE:02 handle 12 state 1 lm MASTER AUTH ENCRYPT 

service bluealsa status

● bluealsa.service - BluezALSA proxy
   Loaded: loaded (/lib/systemd/system/bluealsa.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:18:37 CEST; 10min ago
 Main PID: 3789 (bluealsa)
    Tasks: 3 (limit: 4915)
   Memory: 868.0K
   CGroup: /system.slice/bluealsa.service
           └─3789 /usr/bin/bluealsa

Sep 23 20:18:37 raspberrypi systemd[1]: Started BluezALSA proxy.
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: CMD: command:+CLCC, value:(null)
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: SET: command:+CSRSF, value:0,0,0,1,0,0,0

service bluetooth status

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:07:45 CEST; 10min ago
     Docs: man:bluetoothd(8)
 Main PID: 1007 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 2.2M
   CGroup: /system.slice/bluetooth.service
           └─1007 /usr/lib/bluetooth/bluetoothd

Sep 23 20:10:32 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.24 path=/org/bluez/hci0/A2DP/SBC/Sink/1
Sep 23 20:10:33 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.28 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:48 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:50 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:11 raspberrypi bluetoothd[1007]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:16 raspberrypi bluetoothd[1007]: Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

sudo dmesg -c

[  635.803532] Bluetooth: RFCOMM TTY layer initialized
[  635.803546] Bluetooth: RFCOMM socket layer initialized
[  635.803563] Bluetooth: RFCOMM ver 1.11
[  638.100771] input: 00:15:01:02:DE:02 as /devices/virtual/input/input7
[  669.713843] input: 00:15:01:02:DE:02 as /devices/virtual/input/input8


Get this bounty!!!

#StackBounty: #bluetooth #pi-4 #raspbian-buster Bluetooth headset paired and connected, but can't be selected as audio output

Bounty: 100

I’m stuck trying a pretty standard A2DP Bluetooth headset to work with Raspbian Buster on an RPi 4. I successfully paired it with the RPi and can connect it via the GUI, and the buttons on the headset can control the playback in VLC for instance. However, when I select it as an audio output in Volume Control applet, the green checkmark stays on “HDMI”, which is the other audio output I have.

I would like to keep using bluealsa (which I assume is the default on Buster) and avoid installing pulse if possible. I use the built-in BT adapter, and WiFi is disabled. AFAIK I didn’t change any audio/BT-related config files.

I’m not sure which log I could provide, for a start there’s that:

hcitool con

Connections:
    < ACL 00:15:01:02:DE:02 handle 12 state 1 lm MASTER AUTH ENCRYPT 

service bluealsa status

● bluealsa.service - BluezALSA proxy
   Loaded: loaded (/lib/systemd/system/bluealsa.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:18:37 CEST; 10min ago
 Main PID: 3789 (bluealsa)
    Tasks: 3 (limit: 4915)
   Memory: 868.0K
   CGroup: /system.slice/bluealsa.service
           └─3789 /usr/bin/bluealsa

Sep 23 20:18:37 raspberrypi systemd[1]: Started BluezALSA proxy.
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: CMD: command:+CLCC, value:(null)
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: SET: command:+CSRSF, value:0,0,0,1,0,0,0

service bluetooth status

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:07:45 CEST; 10min ago
     Docs: man:bluetoothd(8)
 Main PID: 1007 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 2.2M
   CGroup: /system.slice/bluetooth.service
           └─1007 /usr/lib/bluetooth/bluetoothd

Sep 23 20:10:32 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.24 path=/org/bluez/hci0/A2DP/SBC/Sink/1
Sep 23 20:10:33 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.28 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:48 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:50 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:11 raspberrypi bluetoothd[1007]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:16 raspberrypi bluetoothd[1007]: Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

sudo dmesg -c

[  635.803532] Bluetooth: RFCOMM TTY layer initialized
[  635.803546] Bluetooth: RFCOMM socket layer initialized
[  635.803563] Bluetooth: RFCOMM ver 1.11
[  638.100771] input: 00:15:01:02:DE:02 as /devices/virtual/input/input7
[  669.713843] input: 00:15:01:02:DE:02 as /devices/virtual/input/input8


Get this bounty!!!

#StackBounty: #bluetooth #pi-4 #raspbian-buster Bluetooth headset paired and connected, but can't be selected as audio output

Bounty: 100

I’m stuck trying a pretty standard A2DP Bluetooth headset to work with Raspbian Buster on an RPi 4. I successfully paired it with the RPi and can connect it via the GUI, and the buttons on the headset can control the playback in VLC for instance. However, when I select it as an audio output in Volume Control applet, the green checkmark stays on “HDMI”, which is the other audio output I have.

I would like to keep using bluealsa (which I assume is the default on Buster) and avoid installing pulse if possible. I use the built-in BT adapter, and WiFi is disabled. AFAIK I didn’t change any audio/BT-related config files.

I’m not sure which log I could provide, for a start there’s that:

hcitool con

Connections:
    < ACL 00:15:01:02:DE:02 handle 12 state 1 lm MASTER AUTH ENCRYPT 

service bluealsa status

● bluealsa.service - BluezALSA proxy
   Loaded: loaded (/lib/systemd/system/bluealsa.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:18:37 CEST; 10min ago
 Main PID: 3789 (bluealsa)
    Tasks: 3 (limit: 4915)
   Memory: 868.0K
   CGroup: /system.slice/bluealsa.service
           └─3789 /usr/bin/bluealsa

Sep 23 20:18:37 raspberrypi systemd[1]: Started BluezALSA proxy.
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: CMD: command:+CLCC, value:(null)
Sep 23 20:19:16 raspberrypi bluealsa[3789]: /usr/bin/bluealsa: Unsupported AT message: SET: command:+CSRSF, value:0,0,0,1,0,0,0

service bluetooth status

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-09-23 20:07:45 CEST; 10min ago
     Docs: man:bluetoothd(8)
 Main PID: 1007 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 2.2M
   CGroup: /system.slice/bluetooth.service
           └─1007 /usr/lib/bluetooth/bluetoothd

Sep 23 20:10:32 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.24 path=/org/bluez/hci0/A2DP/SBC/Sink/1
Sep 23 20:10:33 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint unregistered: sender=:1.25 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Endpoint registered: sender=:1.28 path=/org/bluez/hci0/A2DP/SBC/Source/1
Sep 23 20:18:37 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:48 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:18:50 raspberrypi bluetoothd[1007]: Unable to get connect data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:11 raspberrypi bluetoothd[1007]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 23 20:19:16 raspberrypi bluetoothd[1007]: Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

sudo dmesg -c

[  635.803532] Bluetooth: RFCOMM TTY layer initialized
[  635.803546] Bluetooth: RFCOMM socket layer initialized
[  635.803563] Bluetooth: RFCOMM ver 1.11
[  638.100771] input: 00:15:01:02:DE:02 as /devices/virtual/input/input7
[  669.713843] input: 00:15:01:02:DE:02 as /devices/virtual/input/input8


Get this bounty!!!