equaeghe
l33t
Joined: 22 Feb 2005
Posts: 652
|
 Posted: Sun Sep 29, 2024 2:48 pm Post subject: Bluetooth headset pairing not remembered and mike not shown |
 |
|
I have a bluetooth headset (Poly V6200 Series) that used to work without any problems. Recently, it does not autoconnect anymore, while the system does try to autoconnect. When I put it in pairing more, I can reconnect again, but that isn't remembered. Furthermore, when connected, the headset microphone is not shown in the list of microphones in Plasma's Volume control plasmoid. It is shown in others.
Bigger things that have changed recently are a kernel update 6.6.47 → 6.6.52 and the move from KDE 5 to KDE 6.
Error in log when powering on the headset:
| Code: | sep 29 16:07:21.732753 bluetoothd[557]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 38:5C:76:38:A3:41: Connection refused (111)
sep 29 16:07:21.900743 bluetoothd[557]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 38:5C:76:38:A3:41: Connection refused (111)
sep 29 16:07:21.901487 plasmashell[1371]: kf.bluezqt: PendingCall Error: "br-connection-unknown"
sep 29 16:07:24.220391 bluetoothd[557]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 38:5C:76:38:A3:41: Connection refused (111)
|
Log output when pairing again and changing headset from HiFi (audio out only) to headset mode (audio out+microphone):
| Code: | sep 29 16:40:49.719947 wireplumber[1229]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+BTRH?
sep 29 16:40:49.729237 kernel: input: Poly V6200 Series (AVRCP) as /devices/virtual/input/input23
sep 29 16:40:49.750848 systemd-logind[562]: Watching system buttons on /dev/input/event18 (Poly V6200 Series (AVRCP))
sep 29 16:40:49.757320 obexd[1702]: CONNECT(0x0), <unknown>(0xff)
sep 29 16:40:49.757375 obexd[1702]: CONNECT(0x0), <unknown>(0x0)
sep 29 16:40:54.008372 bluetoothd[557]: /org/bluez/hci0/dev_38_5C_76_38_A3_41/sep1/fd0: fd(44) ready
sep 29 16:40:58.442149 kded6[1323]: org.kde.pulseaudio: No object for name "bluez_output.38_5C_76_38_A3_41.1"
sep 29 16:40:58.442202 kdeconnectd[1729]: 2024-09-29T16:40:58 org.kde.pulseaudio: No object for name "bluez_output.38_5C_76_38_A3_41.1"
sep 29 16:40:58.442508 plasmashell[1371]: org.kde.pulseaudio: No object for name "bluez_output.38_5C_76_38_A3_41.1"
sep 29 16:40:58.651222 kernel: Bluetooth: hci0: corrupted SCO packet [REPEATED 7 TIMES]
sep 29 16:41:01.214480 pipewire[1226]: pw.node: (alsa_input.usb-046d_0990_EC269F09-02.mono-fallback-57) graph xrun not-triggered (0 suppressed)
sep 29 16:41:01.214507 pipewire[1226]: pw.node: (alsa_input.usb-046d_0990_EC269F09-02.mono-fallback-57) xrun state:0x7bc86c0f1008 pending:1/1 s:7300080603298 a:7300080705731 f:7300080710711 waiting:102433 process:4980 status:triggered
sep 29 16:41:04.371694 pipewire[1226]: pw.node: (alsa_input.usb-046d_0990_EC269F09-02.mono-fallback-57) graph xrun not-triggered (1 suppressed)
sep 29 16:41:04.371722 pipewire[1226]: pw.node: (alsa_input.usb-046d_0990_EC269F09-02.mono-fallback-57) xrun state:0x7bc86c0f1008 pending:1/1 s:7303237817183 a:7303237910048 f:7303237914837 waiting:92865 process:4789 status:triggered
|
Bluetooth gives rise to various errors and warnings during startup of my system, but it is impractical to give all such log output. Please do ask for more info, if needed.
BTW: I have a bluetooth mouse that autoconnects without problems. It is only the headset whose behavior changed in that regard in the last few weeks.
Would anyone have an idea of what might be the matter and how I could fix it? |
|
Kernel & Hardware
