My Bluetooth earphones doesn't connect

endless · 2025-11-30 19:25:05

I use pipewire, it's a while now that my Bluetooth earphones doesn't connect, when ever i try to connect it connects but disconnects almost instantly. I tried connecting via terminal using bluetoothctl but in vein.
I hope someone can help me , if you need more information i'll gladly tell you.

Last edited by endless (2025-12-27 08:47:44)

ewaller · 2025-11-30 19:28:37

Any chance that some other device (your phone) is grabbing them first?
If not, are there any messages in the journal of interest?

endless · 2025-11-30 19:34:27

what is this journal of interest? and no bluetooth is activated only in my pc

Last edited by endless (2025-11-30 19:35:07)

ewaller · 2025-11-30 22:32:26

Sorry, sometimes I forget English is not everyone's first language when I write unexpectedly twisted phrases. It is the messages that are of interest. The journal is a logging mechanism to compile information from the various system processed. To see the entire journal from this boot, use the command journalctl -b

Try this to see if there is anything about Bluetooth:

journalctl -b | grep Blue

HasakeShinonome · 2025-11-30 23:08:57

Try to forget your Bluetooth headphones and then reconnect them. It might be a problem with the Bluetooth location, which can happen when shutting down a computer before removing a Bluetooth connection and then later on connecting the same Bluetooth hardware onto something different.

endless · 2025-12-15 18:32:28

ewaller wrote:

Sorry, sometimes I forget English is not everyone's first language when I write unexpectedly twisted phrases. It is the messages that are of interest. The journal is a logging mechanism to compile information from the various system processed. To see the entire journal from this boot, use the command journalctl -b
Try this to see if there is anything about Bluetooth:
journalctl -b | grep Blue

sorry I forgot that I posted this topic... so the thing is before you replied i understood what you meant by journal (you are absolutely correct, English isn't my native language) and I took a glimpse of the journal and from what I understood the connection between my PC and the earphones get cut the moment it connects and I don't know why . if you want to see it for yourself i can try to connect to them and send you the journal afterwards but I honestly think that this is likely to be a compatibility issue because the earphones work on my PC when i turn on windows.

Last edited by endless (2025-12-15 19:03:32)

endless · 2025-12-15 18:33:05

HasakeShinonome wrote:

Try to forget your Bluetooth headphones and then reconnect them. It might be a problem with the Bluetooth location, which can happen when shutting down a computer before removing a Bluetooth connection and then later on connecting the same Bluetooth hardware onto something different.

I tried but in vain

Last edited by endless (2025-12-15 19:03:07)

kalenux81 · 2025-12-15 18:56:17

I just struggled with the same thing yesterday Used bluetoothctl, scanned and paired with my headphones and instantly it disconnects. This worked for me:

Install pulseaudio-bluetooth if you haven't already (pacman -S pulseaudio-bluetooth) and then run "pulseaudio --daemonize"

Then just connect again with bluetoothctl should work okay!

PS: the pulseaudio might give some error "Daemon startup failed" but don't mind about it. You can try running it with sudo also.

endless · 2025-12-15 19:07:23

kalenux81 wrote:

I just struggled with the same thing yesterday Used bluetoothctl, scanned and paired with my headphones and instantly it disconnects. This worked for me:
Install pulseaudio-bluetooth if you haven't already (pacman -S pulseaudio-bluetooth) and then run "pulseaudio --daemonize"
Then just connect again with bluetoothctl should work okay!
PS: the pulseaudio might give some error "Daemon startup failed" but don't mind about it. You can try running it with sudo also.

won't that cause a conflict between Pusleaudio and Pipewire(the one I used)?

kalenux81 · 2025-12-15 19:10:31

Not sure but try? I use alsa and for all works okay. You can always uninstall the pulseaudio-bluetooth it you run into problems.

Edit: and it's only the bluetooth stuff of pulseaudio not the whole thing.

Last edited by kalenux81 (2025-12-15 19:11:34)

qinohe · 2025-12-15 19:19:37

@kalenux81, hmmm bluetooth don't work that way in dual-boot
You get a different pairing key from both OS

@OP, Since you said: 'bluetooth is activated only in my pc'
I assume you're dual booting
My guess is this where thing go wrong

Fully unpair untrust remove the windows connection
Now boot into Arch
Remove any old entry of the ear pieces
then connect pair trust etc.

So now you should navigate to '/var/lib/bluetooth/stack-MAC/device-MAC/info'
copy the key and use that key in windows

Ow and BTW. I have no idea which file should hold that key, I don't use window

kalenux81 · 2025-12-15 19:30:27

@qinohe, well can't say for sure about dualbooting but I'd assume that if OP is booted in Linux the Windows isn't running any connections... Also I think the "is activated only in my pc" means that the headphones aren't connected to anything else at the moment (like phone or tablet) but only his computer+Linux.

Anyway I had the same exact problem yesterday and that solution worked for me (although I didnt not have pipewire).

qinohe · 2025-12-15 19:47:17

@kalenux81, when dualbooting your keys get overwritten so they need to be the same in both OS's

@OP, I read you need to edit the registry, I remember having done that in the past.
If you're uncomfortable editing the registry, you can also copy the key from there and use that in Arch...
The registry is probably?? on a path like: \ControlSet001\Services\BTHPORT\Parameters\Keys
But I can't really help you with that

endless · 2025-12-15 20:41:33

qinohe wrote:

@kalenux81, hmmm bluetooth don't work that way in dual-boot
You get a different pairing key from both OS
@OP, Since you said: 'bluetooth is activated only in my pc'
I assume you're dual booting
My guess is this where thing go wrong
Fully unpair untrust remove the windows connection
Now boot into Arch
Remove any old entry of the ear pieces
then connect pair trust etc.
So now you should navigate to '/var/lib/bluetooth/stack-MAC/device-MAC/info'
copy the key and use that key in windows
Ow and BTW. I have no idea which file should hold that key, I don't use window

I am dual booting , you said that the key needs to be the same one for both OSs , so I need to unpair the earphones from windows, then pair them with linux, then what ?
edit:WOW! it really worked! amazing!

Last edited by endless (2025-12-15 21:01:13)

qinohe · 2025-12-16 09:39:17

Glad it did
Please mark your post 'Solved' by editing the first post

endless · 2025-12-27 08:48:49

qinohe wrote:

Glad it did
Please mark your post 'Solved' by editing the first post

It isn't working i changed the pairing key many times and it fails to connect not matter how many times i did it , do i do something wrong?

Last edited by endless (2025-12-27 08:49:40)

zpg443 · 2025-12-27 13:19:47

1. Ensure both bluez and bluez-utils are installed. If you are using a USB dongle, unplug and replug.

Check service:

systemctl status bluetooth.service

sudo systemctl enable --now bluetooth.service

2. Check if the controller exists:

rfkill list

lsusb (USB dongle) or lspci -k (PCIe Wi‑Fi/Bluetooth combo)
Make sure the Bluetooth device is not “Hard blocked” / “Soft blocked”.

3. Check BlueZ sees hardware:

bluetoothctl show

If it says “No default controller available”, the kernel driver for your chipset is not binding correctly

4. If you use a Wi‑Fi/Bluetooth combo card, ensure Wi‑Fi is enabled in firmware/hardware switches; some chipsets only expose BT when Wi‑Fi radio is on.

5. Paste the outputs of:

systemctl status bluetooth.service

rfkill list

lsusb (and lspci -k | grep -A3 -i network)

bluetoothctl show

journalctl -u bluetooth -b | sed -n '1,80p'

endless · 2025-12-28 20:05:29

zpg443 wrote:

1. Ensure both bluez and bluez-utils are installed. If you are using a USB dongle, unplug and replug.
Check service:
systemctl status bluetooth.service

sudo systemctl enable --now bluetooth.service
2. Check if the controller exists:
rfkill list
lsusb (USB dongle) or lspci -k (PCIe Wi‑Fi/Bluetooth combo)
Make sure the Bluetooth device is not “Hard blocked” / “Soft blocked”.
3. Check BlueZ sees hardware:
bluetoothctl show
If it says “No default controller available”, the kernel driver for your chipset is not binding correctly
4. If you use a Wi‑Fi/Bluetooth combo card, ensure Wi‑Fi is enabled in firmware/hardware switches; some chipsets only expose BT when Wi‑Fi radio is on.
5. Paste the outputs of:
systemctl status bluetooth.service

rfkill list

lsusb (and lspci -k | grep -A3 -i network)

bluetoothctl show

journalctl -u bluetooth -b | sed -n '1,80p'

systemctl status bluetooth.service:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Sun 2025-12-28 13:05:08 +01; 7h ago
Invocation: 1eba5ee8de914bf6a24f09bf3e29d751
Docs: man:bluetoothd(8)
Main PID: 1991 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 18856)
Memory: 2.3M (peak: 3.2M)
CPU: 105ms
CGroup: /system.slice/bluetooth.service
└─1991 /usr/lib/bluetooth/bluetoothd

Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource/faststream
Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource/faststream_duplex
Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSink/opus_05
Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource/opus_05
Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Dec 28 20:52:38 Archbox bluetoothd[1991]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource/opus_05_duplex

rfkill list :
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 3151:3020 YICHIP Wireless Device
Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 001 Device 005: ID 04f2:b5ab Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 013: ID 138a:0097 Validity Sensors, Inc.
Bus 001 Device 015: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader

lspci -k | grep -A3 -i network:
04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
Subsystem: Intel Corporation Dual Band Wireless-AC 8265
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

bluetoothctl show:
Controller 94:B8:6D:B8:05:FF (public)
Manufacturer: 0x0002 (2)
Version: 0x08 (8)
Name: Archbox
Alias: Archbox
Class: 0x006c010c (7078156)
Powered: yes
PowerState: on
Discoverable: no
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0555
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x05 (5)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedCapabilities.MaxAdvLen: 0x1f (31)
SupportedCapabilities.MaxScnRspLen: 0x1f (31)

Arch Linux

#1 2025-11-30 19:25:05

My Bluetooth earphones doesn't connect

#2 2025-11-30 19:28:37

Re: My Bluetooth earphones doesn't connect

#3 2025-11-30 19:34:27

Re: My Bluetooth earphones doesn't connect

#4 2025-11-30 22:32:26

Re: My Bluetooth earphones doesn't connect

#5 2025-11-30 23:08:57

Re: My Bluetooth earphones doesn't connect

#6 2025-12-15 18:32:28

Re: My Bluetooth earphones doesn't connect

#7 2025-12-15 18:33:05

Re: My Bluetooth earphones doesn't connect

#8 2025-12-15 18:56:17

Re: My Bluetooth earphones doesn't connect

#9 2025-12-15 19:07:23

Re: My Bluetooth earphones doesn't connect

#10 2025-12-15 19:10:31

Re: My Bluetooth earphones doesn't connect

#11 2025-12-15 19:19:37

Re: My Bluetooth earphones doesn't connect

#12 2025-12-15 19:30:27

Re: My Bluetooth earphones doesn't connect

#13 2025-12-15 19:47:17

Re: My Bluetooth earphones doesn't connect

#14 2025-12-15 20:41:33

Re: My Bluetooth earphones doesn't connect

#15 2025-12-16 09:39:17

Re: My Bluetooth earphones doesn't connect

#16 2025-12-27 08:48:49

Re: My Bluetooth earphones doesn't connect

#17 2025-12-27 13:19:47

Re: My Bluetooth earphones doesn't connect

#18 2025-12-28 20:05:29

Re: My Bluetooth earphones doesn't connect

Board footer