# Earphones get disconnected automatically **URL:** \ **Category:** Help\ **Tags:** plasma, wayland, bluetooth\ **Created:** [January 1, 2026, 6:50pm UTC](https://discuss.kde.org/t/earphones-get-disconnected-automatically/43046 "2026-01-01T18:50:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Aryetis](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/a/fbc32d/32.png) [@Aryetis](https://discuss.kde.org/u/Aryetis)\ **Post date:** [January 1, 2026, 6:50pm UTC](https://discuss.kde.org/t/earphones-get-disconnected-automatically/43046/1 "2026-01-01T18:50:35Z")
Hello, I have some “Moondrop Space Travel” IEMs. They work fine with my phone, tablet, projector, vita, etc. They even work fine when I’m using them on my computer with Hyprland Niri. Which is making me point fingers at KDE. Because whenever I try to connect them using KDE Plasma and its built-in bluetooth widget thingy, they do connect and even work just fine for about 2 seconds but then get disconnected automatically. Here are some logs from bluetoothtcl for instance whenever I try to connect them. ```auto [NEW] Endpoint /org/bluez/hci0/dev_23_11_07_B3_E9_EE/sep1 [NEW] Endpoint /org/bluez/hci0/dev_23_11_07_B3_E9_EE/sep2 [NEW] Transport /org/bluez/hci0/dev_23_11_07_B3_E9_EE/fd0 [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 23:11:07:B3:E9:EE Connected: no [DEL] Transport /org/bluez/hci0/dev_23_11_07_B3_E9_EE/fd0 [DEL] Endpoint /org/bluez/hci0/dev_23_11_07_B3_E9_EE/sep1 [DEL] Endpoint /org/bluez/hci0/dev_23_11_07_B3_E9_EE/sep2 ``` More information on my bluetooth USB Dongle ```auto Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:2 chip-ID: 0a12:0001 class-ID: e001 Report: btmgmt ID: hci0 rfk-id: 0 state: up address: bt-v: 4.0 lmp-v: 6 status: discoverable: no pairing: no class-ID: 6c0104 ``` `pactl info` : ```auto Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 327 Tile Size: 65472 User Name: aramir Host Name: SHODAN Server Name: PulseAudio (on PipeWire 1.4.9) Server Version: 15.0.0 Default Sample Specification: float32le 2ch 48000Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.usb-Creative_Technology_Ltd_Sound_Blaster_Play__3_00115584-00.analog-stereo Default Source: alsa_input.usb-3142_fifine_Microphone-00.analog-stereo Cookie: 3e95:9c59 ``` Does anyone have any idea of what could be going on ? What log to look at ? ---
**Author:** ![Aryetis](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/a/fbc32d/32.png) [@Aryetis](https://discuss.kde.org/u/Aryetis)\ **Post date:** [January 2, 2026, 11:36pm UTC](https://discuss.kde.org/t/earphones-get-disconnected-automatically/43046/2 "2026-01-02T23:36:16Z")
Ok seems like this is also affecting other people. > [@Bluetooth audio device disconnects shortly after connection](https://discuss.kde.org/t/bluetooth-audio-device-disconnects-shortly-after-connection/41142): > > Hello! Ever since I upgraded my system to KDE Plasma 6.5, I have had an issue with my Bluetooth audio devices. Whenever I try to connect it to my computer, a few seconds later, it disconnects. I had this issue on both Arch Linux, and KDE Linux. I have found a way to fix it by simply restarting the Bluetooth service using systemctl restart bluetooth But it is just a temporary fix, as the issue comes back after a system restart. I am not sure if it comes from my Bluetooth adapter, but just i… Their workaround do work for me too to some extent. As : 1/ yes it works if I connect from settings-\>bluetooth-\>“connect” on my device in the list 2/ the bluetooth icon in the system tray is acting like the bluetooth service is stopped when it is clearly not. ![image](https://discuss-cdn.kde.org/uploads/default/original/3X/c/5/c5f80d2d5bf9a735e36200ea420ca6b0e80745cb.png) Still looking for help if someone has any ideas, want to see some logs, etc. Please let me know. ---
**Author:** ![Aryetis](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/a/fbc32d/32.png) [@Aryetis](https://discuss.kde.org/u/Aryetis)\ **Post date:** [January 2, 2026, 11:43pm UTC](https://discuss.kde.org/t/earphones-get-disconnected-automatically/43046/3 "2026-01-02T23:43:11Z")
3/ the audio coming from the headphones is very very stuttery. I had similar a similar experience on windows when I was trying to use the headphones while scanning for/trying to add other devices. And the fact that I can’t stop the bt dongle from scanning in `bluetoothtcl` seems to indicate that this is also what’s going on. (No changing codec does not resolve the stutter issue) ---
**Author:** ![Aryetis](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/a/fbc32d/32.png) [@Aryetis](https://discuss.kde.org/u/Aryetis)\ **Post date:** [January 3, 2026, 10:36am UTC](https://discuss.kde.org/t/earphones-get-disconnected-automatically/43046/4 "2026-01-03T10:36:46Z")
4/ I also noticed that I have problems connecting the earphones ONLY when I try to connect them when using the system tray widget. Connecting them from the setting window works just fine. ---
**Author:** ![soumyadghosh](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/soumyadghosh/32/15961_2.png) [@soumyadghosh](https://discuss.kde.org/u/soumyadghosh)\ **Post date:** [March 5, 2026, 7:07pm UTC](https://discuss.kde.org/t/earphones-get-disconnected-automatically/43046/5 "2026-03-05T19:07:22Z")
I also have moondrop space travel 2, but I faced this problem with my another device GoBoult Audio Flex. The only solution for now is to disable Bluetooth provider of KDE Connect. It can be done, atleast in 25.08.1 by running ```auto kdeconnect-cli --disable-backend BluetoothLinkProvider ``` or adding this in `${HOME}/.config/kdeconnect/config` ```auto [General] disabled_providers=BluetoothLinkProvider ``` Or you can disable it from the KDE Connect settings via GUI ![image](https://discuss-cdn.kde.org/uploads/default/original/3X/a/6/a6f4ff013677c6ca1a7189e5b6a943d85194d867.png) If you’re an user of Arch or a very new version of KDE Connect, specifically around `25.12.1`, you might want to take a look at this bug report > **[516170 – Bluetooth backend is always active when kdeconnectd starts](https://bugs.kde.org/show_bug.cgi?id=516170)** To disable bluetooth backend for that version, set `AsyncLinkProvider` instead of `BluetoothLinkProvider`. This is what the `${HOME}/.config/kdeconnect/config` will look like ```auto [General] disabled_providers=AsyncLinkProvider ``` ---
**Author:** ![Aryetis](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/a/fbc32d/32.png) [@Aryetis](https://discuss.kde.org/u/Aryetis)\ **Post date:** [March 6, 2026, 10:12pm UTC](https://discuss.kde.org/t/earphones-get-disconnected-automatically/43046/6 "2026-03-06T22:12:09Z")
Thanks. Indeed, this seems to do the trick for me ```auto kdeconnect-cli --disable-backend AsyncLinkProvider ``` no doubt tweaking the kdeconnect config will work too.