Soundcore Life Q30 Bluetooth headphones disconnect after ~34s

Ask Fedora
1

The headphones always connect successfully and audio will play just fine, but no matter what I’m doing, they will always disconnect less than a minute later. I have seen other threads on this, but they are all marked as solved (less likely that people will look at the thread) and their solutions did not work for me.

Journal output from pairing, and then manually reconnecting a few minutes later:

Sep 07 16:15:51 fedora systemd[2027]: Reached target bluetooth.target - Bluetooth.
Sep 07 16:15:52 fedora bluetoothd[1437]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 98:47:44:A3:1A:DE: Connection refused (111)
Sep 07 16:15:52 fedora bluetoothd[1437]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 98:47:44:A3:1A:DE: Connection refused (111)
Sep 07 16:15:52 fedora plasmashell[2555]: PendingCall Error: "br-connection-refused"

Sep 07 16:16:03 fedora plasmashell[2555]: qrc:/qt/qml/org/kde/bluedevil/components/ForgetDeviceDialog.qml:38: TypeError: Cannot read property 'name' of null
Sep 07 16:16:03 fedora plasmashell[2555]: qrc:/qt/qml/org/kde/bluedevil/components/ForgetDeviceDialog.qml:89: TypeError: Cannot read property 'adapter' of null

Sep 07 16:16:14 fedora systemd[2027]: Started app-org.kde.bluedevilwizard@038ec0bfa8394f4d9707d2661115c76b.service - Add Bluetooth Device - Add Bluetooth Device.

Sep 07 16:16:23 fedora kernel: input: soundcore Life Q30 (AVRCP) as /devices/virtual/input/input25
Sep 07 16:16:23 fedora systemd-logind[1477]: Watching system buttons on /dev/input/event19 (soundcore Life Q30 (AVRCP))
Sep 07 16:16:23 fedora bluedevil-wizard[4904]: Had queued notifications on destruction. Was the eventloop running?
Sep 07 16:16:23 fedora systemd[2027]: app-org.kde.bluedevilwizard@038ec0bfa8394f4d9707d2661115c76b.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 16:16:23 fedora systemd[2027]: app-org.kde.bluedevilwizard@038ec0bfa8394f4d9707d2661115c76b.service: Failed with result 'exit-code'.

Sep 07 16:23:20 fedora plasmashell[2555]: qrc:/qt/qml/plasma/applet/org/kde/plasma/systemtray/ExpandedRepresentation.qml:239: TypeError: Cannot read property 'text' of null
Sep 07 16:23:24 fedora kernel: input: soundcore Life Q30 (AVRCP) as /devices/virtual/input/input26
Sep 07 16:23:24 fedora systemd-logind[1477]: Watching system buttons on /dev/input/event19 (soundcore Life Q30 (AVRCP))
Sep 07 16:23:29 fedora plasmashell[2555]: QIODevice::read (QSslSocket): device not open
Sep 07 16:23:38 fedora chronyd[1443]: Selected source 23.143.196.204 (2.fedora.pool.ntp.org)
Sep 07 16:23:39 fedora kwin_wayland[2353]: Libinput: event5  - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.31.3/touchpad-jumping-cursors.html for details
Sep 07 16:23:39 fedora kwin_wayland[2353]: Libinput: event5  - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.31.3/touchpad-jumping-cursors.html for details
Sep 07 16:23:39 fedora systemd[2027]: app-org.kde.konsole-5904.scope: Consumed 6.385s CPU time over 3min 23.456s wall clock time, 30.7M memory peak.
Sep 07 16:23:40 fedora systemd[2027]: Started app-org.kde.konsole@86b2972e3db34ddf8e523d3db73c0194.service - Konsole - Terminal.
Sep 07 16:23:41 fedora systemd[2027]: Started app-org.kde.konsole-6287.scope.
Sep 07 16:23:46 fedora konsole[6287]: QObject::disconnect: Unexpected nullptr parameter
Sep 07 16:23:48 fedora systemd[2027]: Started app-org.kde.konsole@7980c6fef04b49298cce8ba1fc650372.service - Konsole - Terminal.
Sep 07 16:23:48 fedora systemd[2027]: Started app-org.kde.konsole-6405.scope.
Sep 07 16:23:55 fedora bluetoothd[1437]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Sep 07 16:23:55 fedora kded6[2520]: No object for name "bluez_input.98:47:44:A3:1A:DE"
Sep 07 16:23:55 fedora kdeconnectd[2860]: No object for name "bluez_input.98:47:44:A3:1A:DE"
Sep 07 16:23:55 fedora plasmashell[2555]: No object for name "bluez_input.98:47:44:A3:1A:DE"
Sep 07 16:23:55 fedora kded6[2520]: No object for name "bluez_output.98_47_44_A3_1A_DE.1"
Sep 07 16:23:55 fedora kdeconnectd[2860]: No object for name "bluez_output.98_47_44_A3_1A_DE.1"
Sep 07 16:23:55 fedora plasmashell[2555]: No object for name "bluez_output.98_47_44_A3_1A_DE.1"

I am using Fedora 44 (KDE, kernel 7.1.13) on a ThinkPad T14 Gen2a with a Ryzen 7 PRO 5850U and a Realtek Bluetooth radio with the ID 0bda:4852.

I tried installing bluez (+ -obexd, -libs, -cups) version 5.80, as these issues specify 5.83 as a regression,

but that isn’t helping. Here’s the Fedora bug report too.

and a fourth thread I just found on the issue with a similar model of headphones:

2

I suspect it would be more likely users would look at the thread in the hopes that the solution on that topic would work for them. This is, after all, the reason for marking a solution.

Topics with no solution marked would seem dead-ended and no likely solution presented.

3

I meant “less likely that people who don’t have the problem but can help me make progress towards the answer will look at the thread”, I was assuming that based on a week of inactivity since I posted on one, a month of inactivity since I posted on another, and months of inactivity on the one I didn’t bother posting on. Should I post this information on one of those other three instead, and delete this thread?

4

Of course not.
Your topic is yours and discussion should be related to your issue.

Looking at other similar topics users may find a usable solution. Posting on the other topics with “me too” could be considered hijacking that topic. It is usually better to open your own topic as you did so all the discussion is about your issue and not interfering and possibly causing confusion within someone else’s issue.

Remember that all discussion here is freely given, and if users do not have the same hardware and software the readers may have nothing beneficial to add. Sometimes a particular piece of hardware, like your headphones, is relatively rare in use so few users may be able to assist.

Generally when topics are opened and there is little or no response it can be assumed there are few users on this forum who are in a position to assist.

You can help others here to be able to help you by providing as much detail as possible about your system, the actual issue, and the steps (including searching for solutions you may have done) you have taken to try and find a fix.

5

Well, I’ve posted exactly what’s happening, linked to three solutions I’ve tried, journal output, the version of Fedora I have and the model of Thinkpad I have. I will add some more system specs, I don’t know what else I could add.

6

Found out it’s a Realtek, which explains why the suggestion for Mediatek hardware didn’t work.

7

Added more links/info

8

If you are still interested in testing my revert of that one commit. I have uploaded it to copr under Soundcore-Bluez.

9

While it didn’t resolve the issue for me, thanks anyway for putting it up there, for those who want to try it: sudo dnf copr enable ethanej/Soundcore-Bluez (then remove the bluez* entries from the /etc/dnf/dnf.conf blacklist if you need to) and update

It was worth a shot. If it’s not that, I have no idea what’s going on

10

Dual booting with Windows? Have you tried repairing using bluetoothctl?

Edit I see some other people recommend killing kde connect.

11

When making additions to info please post it in time and post sequence.

When you edit the OP it does not show up for users who are following your topic and we are then not aware of what changes may have been made.

12

I have tried removing KDE Connect, which didn’t work either. I do have Windows on another partition but rarely use it. It does stay connected there, as well as with my Pixel.

13

I didn’t use bluetoothctl to re-pair but just used the interface in Plasma. I will try that soon.

14 
<bluetoothctl]> pair 98:47:44:A3:1A:DE
Attempting to pair with 98:47:44:A3:1A:DE
[CHG] Device 98:47:44:A3:1A:DE Connected: yes
[CHG] Device 98:47:44:A3:1A:DE Bonded: yes
[CHG] Device 98:47:44:A3:1A:DE UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 98:47:44:A3:1A:DE UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 98:47:44:A3:1A:DE UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 98:47:44:A3:1A:DE UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 98:47:44:A3:1A:DE UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 98:47:44:A3:1A:DE UUIDs: 66666666-6666-6666-6666-666666666666
[CHG] Device 98:47:44:A3:1A:DE UUIDs: df21fe2c-2515-4fdb-8886-f12c4d67927c
[CHG] Device 98:47:44:A3:1A:DE ServicesResolved: yes
[CHG] Device 98:47:44:A3:1A:DE Paired: yes
Pairing successful
[DEL] Device 4F:B1:CF:D6:7D:49 4F-B1-CF-D6-7D-49
[DEL] Device CB:A7:19:12:81:91 LHB-8564DCCD
[DEL] Device B8:8C:29:CA:EC:55 net
[DEL] Device 57:E9:DD:EA:1C:89 57-E9-DD-EA-1C-89
[DEL] Device 5C:E7:51:64:DC:13 5C-E7-51-64-DC-13
[DEL] Device 76:00:61:F6:05:6C 76-00-61-F6-05-6C
[DEL] Device F8:0E:2E:E9:F6:DF LHB-B9C3F8FB
[DEL] Device 62:E8:A0:E7:1F:92 62-E8-A0-E7-1F-92
[DEL] Device 7C:29:7B:D4:EF:39 7C-29-7B-D4-EF-39
[DEL] Device 0A:55:54:88:DF:F1 0A-55-54-88-DF-F1
[CHG] Device 98:47:44:A3:1A:DE ServicesResolved: no
[SIGNAL] BREDR.Disconnected - org.bluez.Reason.Local, Connection terminated by local host
[SIGNAL] Disconnected - org.bluez.Reason.Local, Connection terminated by local host
[CHG] Device 98:47:44:A3:1A:DE Connected: no
[DEL] Device 4E:A1:C9:B3:6A:60 4E-A1-C9-B3-6A-60
[DEL] Device FC:58:FA:F3:55:D3 ChromaComfort-Sensonic Speaker
[DEL] Device FA:4B:15:65:42:E5 Ring d9
[DEL] Device 6E:72:EC:78:F3:7F 6E-72-EC-78-F3-7F
[DEL] Device FC:58:FA:B7:76:B9 ChromaComfort-Sensonic Speaker
[bluetoothctl]> pair 98:47:44:A3:1A:DE
Attempting to pair with 98:47:44:A3:1A:DE
Failed to pair: org.bluez.Error.AlreadyExists
[bluetoothctl]> trust 98:47:44:A3:1A:DE
[CHG] Device 98:47:44:A3:1A:DE Trusted: yes
Changing 98:47:44:A3:1A:DE trust succeeded
[bluetoothctl]> connect 98:47:44:A3:1A:DE
Attempting to connect to 98:47:44:A3:1A:DE
[CHG] Device 98:47:44:A3:1A:DE Connected: yes
[NEW] Endpoint /org/bluez/hci0/dev_98_47_44_A3_1A_DE/sep1
[NEW] Endpoint /org/bluez/hci0/dev_98_47_44_A3_1A_DE/sep2
[NEW] Transport /org/bluez/hci0/dev_98_47_44_A3_1A_DE/sep2/fd0
[CHG] Transport /org/bluez/hci0/dev_98_47_44_A3_1A_DE/sep2/fd0 Delay: 0x0708 (1800)
Connection successful
[CHG] Transport /org/bluez/hci0/dev_98_47_44_A3_1A_DE/sep2/fd0 Volume: 0x003d (61)
[CHG] Device 98:47:44:A3:1A:DE ServicesResolved: yes
[CHG] Device 98:47:44:A3:1A:DE ServicesResolved: no
[SIGNAL] BREDR.Disconnected - org.bluez.Reason.Unknown, Unspecified
[SIGNAL] Disconnected - org.bluez.Reason.Unknown, Unspecified
[CHG] Device 98:47:44:A3:1A:DE Connected: no
[DEL] Transport /org/bluez/hci0/dev_98_47_44_A3_1A_DE/sep2/fd0
[DEL] Endpoint /org/bluez/hci0/dev_98_47_44_A3_1A_DE/sep1
[DEL] Endpoint /org/bluez/hci0/dev_98_47_44_A3_1A_DE/sep2
15

No hcitool/hciconfig in the repositories, but I found bluetooth-hcidump instead. Got a lead:

$ hcidump  
HCI sniffer - Bluetooth packet analyzer ver 2.5 
device: hci0 snap_len: 1500 filter: 0xffffffffffffffff 
> HCI Event: Disconn Complete (0x05) plen 4 
    status 0x00 handle 11 reason 0x22 
    Reason: LMP Response Timeout

Not sure what LMP is, but I did find a thread with Arch Linux users claiming some firmware fixed a disconnection issue with a TP-Link adapter which, from what I can tell, uses a specific Realtek chip. I can’t tell exactly what Realtek chip I have, though, all I have is its ID…

https://bbs.archlinux.org/viewtopic.php?id=302528

16

Inxi can show a lot of info about bluetooth devices as shown below. Note the chip-ID: that is shown, as it will be the exact chipset used.
This extract is from inxi -Exx

$ inxi -Exx
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 1-9:10 chip-ID: 8087:0032
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: 64:49:7D:E5:D3:5E
    bt-v: 5.4 lmp-v: 13

Please show us the output of that command so we may be able to assist in identifying the chipset and possible solutions.
That chip-ID can also be used to search for issues specific to that device.

17

Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-4:3 chip-ID: 0bda:4852
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: E0:0A:F6:52:CE:9A
bt-v: 5.2 lmp-v: 11

18

I went to the Lenovo support page for this laptop and saw they only have Windows drivers available for download there, but I found this in the Readme:

Realtek 8852AE Bluetooth

There’s a driver here:

It only mentions wifi though, not bluetooth, and looking at the issues isn’t encouraging

19

A quick search for linux driver for that chip-ID gave this as the AI response.

**Driver Status**

* **Bluetooth (`0bda:4852`):** This is supported natively in the Linux kernel by the standard **`btusb`** driver along with the **`btrtl`** module. You do not need to install an external third-party driver for this device to be recognized.
* **Wi-Fi Companion ([RTL8852AE]
** The Wi-Fi side of this chip is handled natively by the **`rtw89`** (`rtw89_8852ae`) kernel driver.

There are, however, many issues reported on this forum about that wifi adapter.
I suspect that it would be beneficial to either replace the wifi adapter in your laptop with one that has better support under linux or to get an external (usb) wifi dongle that has a better supported chipset and use it instead of the built in card.

In most laptops I have looked at the wifi adapter seems easy to replace.

20

Good idea, thanks. According to this thread, the Intel version of this laptop has the card soldered, but the AMD version which I have uses a socketed card. So that seems like a very feasible option. Looks like a trip to Micro Center is in order.