I have Bose bluetooth headphones and I can’t get the headset mode to work.
I installed bluez and blueman and I paired and connected the headphones.
See screenshot for more details.
First of all make sure no other device has paired to them. I think the best way is to use bluetoothctl and go through the steps. Also check if bluetooth is blocked with rfkill. Sometimes it can be a little finacky getting it to pair, register, connect, trust etc… Remove and start from the beginning.
Okay so I removed and started from the beginning, this time the cli way. But the issue is still there. I can’t get it into headset mode, which is what I need for Zoom sessions and Google Meet etc, so I can use earphones and mic.
Check https://wiki.archlinux.org/title/bluetooth_headset, especially the troubleshooting section. Look in the journalctl for the exact error message while connecting the headset and Google them. Linux, bluetooth and headsets is something which may not work as expected. Sometimes it is the headset sometimes the bluetooth part which causes the problems.
My idea would be to reboot your PC. After rebooting login and open a terminal. Then connect your headset.
Run following command in the terminal: journalctl -b -0 -n20 > journal.log (this will take the last 20 lines of the actual journal)
Open the journal.log with any editor and copy the complete content of the file and paste it here.
You need to open the terminal full screen so we can see all the info. Also please use code tags before and after what you copy and post from the terminal here. (~~~)
And somehow it just started working. I wish I could explain why. All I can say is sometimes certain bluetooth devices are a hit or miss and unfortunately there isn’t a simple, quick fix for every issues, sometimes it’s down on the kernel level, other times it’s with one of the bluetooth packages. I don’t know how you feel about a clean install (that’s like a last resort option), but it may be something to consider as in my case I needed bluetooth to work since that was a deal breaker for me. I wish I could provide more help! But I hope my suggestion may be of value if you get to that point. Good luck for now!
@shmu26
Use Blueman as the GUI. Do you have bluez, pulseaudio-bluetooth, & bluez-utils installed. Make sure bluetooth is enabled and running. Try this and see if it works.
The output of “journalctl -b -0 -n20 > journal.log” is below. I have bluez, pulseaudio-bluetooth, & bluez-utils installed.
I have blueman open, but it can’t switch to headset mode, it does like in the screenshot in the OP.
-- Journal begins at Tue 2021-08-03 03:32:45 IDT, ends at Tue 2021-08-03 06:34:01 IDT. --
Aug 03 06:33:59 shmuel-eos dbus-daemon[4592]: [session uid=1000 pid=4592] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.64' (uid=1000 pid=41331 comm="thunar-volman --device-added /sys/devices/virtual/")
Aug 03 06:33:59 shmuel-eos systemd[4514]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Aug 03 06:33:59 shmuel-eos dbus-daemon[4592]: [session uid=1000 pid=4592] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Aug 03 06:33:59 shmuel-eos systemd[4514]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Aug 03 06:33:59 shmuel-eos dbus-daemon[4592]: [session uid=1000 pid=4592] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.64' (uid=1000 pid=41331 comm="thunar-volman --device-added /sys/devices/virtual/")
Aug 03 06:33:59 shmuel-eos systemd[4514]: Starting Virtual filesystem service - digital camera monitor...
Aug 03 06:33:59 shmuel-eos dbus-daemon[4592]: [session uid=1000 pid=4592] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Aug 03 06:33:59 shmuel-eos systemd[4514]: Started Virtual filesystem service - digital camera monitor.
Aug 03 06:33:59 shmuel-eos obexd[5215]: CONNECT(0x0), <unknown>(0xff)
Aug 03 06:33:59 shmuel-eos obexd[5215]: CONNECT(0x0), <unknown>(0x0)
Aug 03 06:33:59 shmuel-eos obexd[5215]: SETPATH(0x5), <unknown>(0xff)
Aug 03 06:33:59 shmuel-eos obexd[5215]: stat(/home/shmuel/phonebook/): No such file or directory (2)
Aug 03 06:33:59 shmuel-eos obexd[5215]: SETPATH(0x5), Not Found(0x44)
Aug 03 06:34:00 shmuel-eos bluetoothd[1407]: /org/bluez/hci0/dev_60_AB_D2_45_5D_47/fd0: fd(42) ready
Aug 03 06:34:00 shmuel-eos rtkit-daemon[5163]: Supervising 4 threads of 1 processes of 1 users.
Aug 03 06:34:00 shmuel-eos rtkit-daemon[5163]: Successfully made thread 42603 of process 5144 owned by '1000' RT at priority 5.
Aug 03 06:34:00 shmuel-eos rtkit-daemon[5163]: Supervising 5 threads of 1 processes of 1 users.
Aug 03 06:34:01 shmuel-eos plasmashell[5066]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height"
Aug 03 06:34:01 shmuel-eos systemd[4514]: Finished EOS update notifier service.
Aug 03 06:34:01 shmuel-eos systemd[4514]: eos-update-notifier.service: Consumed 1.778s CPU time.
