You are not logged in.

#1 2023-09-14 01:28:18

Jotunn
Member
Registered: 2023-04-29
Posts: 69

[resolved] Unable to pair bluetooth devices.

I am able to see other devices but some of my devices are not showing up while scanning.
Regardless of the device I try to connect to, I immediately get an error "failed to connect"
Some devices seem to be working in spite of the connection failure. As an example, I was able to transfer a picture from my computer to my phone over bluetooth even though it keeps failing to connect.
I am not getting any functionality out of audio devices.

What I did to set up BT initially:

$ sudo pacman -S bluez
$ sudo pacman -S bluez-utils
$ sudo pacman -S bluedevil
$ sudo systemctl start bluetooth.service

Last edited by Jotunn (2024-03-13 03:56:12)

Offline

#2 2023-09-14 07:31:14

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,024

Re: [resolved] Unable to pair bluetooth devices.

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
https://wiki.archlinux.org/title/Blueto … leshooting
From the vague symptoms: do you have a parallel windows isntallation?

Offline

#3 2023-09-14 16:32:06

Jotunn
Member
Registered: 2023-04-29
Posts: 69

Re: [resolved] Unable to pair bluetooth devices.

I am not running Windows parallel. Arch is the only OS installed on the system.

The generic Bluetooth driver is the btusb kernel module
and when I check loaded modules I get this output:

$ lsmod | grep btusb
btusb                  81920  0
btrtl                  28672  1 btusb
btbcm                  24576  1 btusb
btintel                57344  1 btusb
btmtk                  12288  1 btusb
bluetooth            1110016  40 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm

which I think is a good thing
unless that 0 means it is off?
but if I run

$ modprobe btusb 

then rerun lsmod I get the same output.

Maybe I need a different BT driver?

Offline

#4 2023-09-14 18:58:47

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,024

Re: [resolved] Unable to pair bluetooth devices.

"0" means there're no users (userspace processes or kernel modules)

Try to pair a device and post the entire bluetoothctl session, https://wiki.archlinux.org/title/Bluetooth#Pairing
Do you use a 2.4GHz wifi connection or other 2.4GHz consumers (wireless mouse etc)?

Offline

#5 2023-09-15 23:51:04

Jotunn
Member
Registered: 2023-04-29
Posts: 69

Re: [resolved] Unable to pair bluetooth devices.

Sorry for the delay! Here is the output from trying to pair a device:

$ modprobe btusb
$ sudo systemctl start bluetooth.service
[sudo] password for ******: 
$ bluetoothctl
Agent registered
[bluetooth]# devices
Device 38:18:4C:B6:A6:33 WF-1000XM3
Device 30:74:67:EB:3A:AE ****'s S22 Ultra
Device 00:42:79:87:63:56 STOCKWELL II
[CHG] Device 38:18:4C:B6:A6:33 Connected: yes
[CHG] Device 38:18:4C:B6:A6:33 Modalias: usb:v054Cp0CE0d0137
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000fe26-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000fe2c-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 81c2e72a-0591-443e-a1ff-05f988593351
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 8901dfa8-5c7e-4d8f-9f0c-c2b70683f5f0
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: f8d1fbe4-7966-4334-8024-ff96c9330e15
[CHG] Device 38:18:4C:B6:A6:33 ServicesResolved: yes
[CHG] Device 38:18:4C:B6:A6:33 ServicesResolved: no
[CHG] Device 38:18:4C:B6:A6:33 Connected: no
[bluetooth]# 
seth wrote:

Do you use a 2.4GHz wifi connection or other 2.4GHz consumers (wireless mouse etc)?

The computer is on ethernet and has no other wireless devices connected but I believe the bluetooth transponder is functioning as part of the wifi card that came attached to the motherboard. This is why I suspected it might be a driver-related issue.

Last edited by Jotunn (2023-09-15 23:55:03)

Offline

#6 2023-09-16 00:21:37

Jotunn
Member
Registered: 2023-04-29
Posts: 69

Re: [resolved] Unable to pair bluetooth devices.

I ran a quick check for bluetooth related errors and this is what I got:

$ sudo dmesg | grep -i blue
[    5.444188] Bluetooth: Core ver 2.22
[    5.444204] NET: Registered PF_BLUETOOTH protocol family
[    5.444205] Bluetooth: HCI device and connection manager initialized
[    5.444208] Bluetooth: HCI socket layer initialized
[    5.444211] Bluetooth: L2CAP socket layer initialized
[    5.444214] Bluetooth: SCO socket layer initialized
[    5.643595] Bluetooth: hci0: Device setup in 162399 usecs
[    5.643599] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[    5.943841] Bluetooth: hci0: AOSP extensions version v1.00
[    5.943844] Bluetooth: hci0: AOSP quality report is supported
[  295.473749] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  295.473751] Bluetooth: BNEP filters: protocol multicast
[  295.473754] Bluetooth: BNEP socket layer initialized
[  295.474436] Bluetooth: MGMT ver 1.22
[  295.494893] Bluetooth: RFCOMM TTY layer initialized
[  295.494896] Bluetooth: RFCOMM socket layer initialized
[  295.494898] Bluetooth: RFCOMM ver 1.11
[  295.774878] Bluetooth: hci0: Device setup in 162104 usecs
[  295.774884] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[  296.060136] Bluetooth: hci0: AOSP extensions version v1.00
[  296.060141] Bluetooth: hci0: AOSP quality report is supported

Offline

#7 2023-09-16 00:33:30

Jotunn
Member
Registered: 2023-04-29
Posts: 69

Re: [resolved] Unable to pair bluetooth devices.

Here is a longer output of me removing the device, re-adding it, and trying again to connect:

$ bluetoothctl
Agent registered
[DEL] Device 38:18:4C:B6:A6:33 WF-1000XM3
[CHG] Controller 50:C2:E8:33:58:E0 Discovering: yes
[NEW] Device 38:18:4C:B6:A6:33 WF-1000XM3
[NEW] Device 88:C6:26:F1:EC:C1 88-C6-26-F1-EC-C1
[NEW] Device 39:47:1E:39:9F:E4 39-47-1E-39-9F-E4
[NEW] Device 42:9C:0F:1C:CD:8E 42-9C-0F-1C-CD-8E
[NEW] Device 64:F2:30:28:83:FF 64-F2-30-28-83-FF
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device D0:03:4B:24:CC:29 D0-03-4B-24-CC-29
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffac (-84)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device 4F:EE:2A:6D:52:56 4F-EE-2A-6D-52-56
[NEW] Device 41:3C:09:3F:69:03 Galaxy Watch5 Pro (S3TW)
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffba (-70)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device 70:57:BF:AB:23:B4 70-57-BF-AB-23-B4
[NEW] Device 10:BA:D1:EC:94:48 10-BA-D1-EC-94-48
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device 73:19:CD:D7:3A:3A 73-19-CD-D7-3A-3A
[CHG] Device 70:57:BF:AB:23:B4 RSSI: 0xffffffa3 (-93)
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffab (-85)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device 67:43:5D:C2:12:BE 67-43-5D-C2-12-BE
[NEW] Device 79:85:7A:9C:38:6F 79-85-7A-9C-38-6F
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffc0 (-64)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device 72:49:FD:69:E4:28 72-49-FD-69-E4-28
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffab (-85)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffba (-70)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device 71:AF:D2:6F:A1:9C 71-AF-D2-6F-A1-9C
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffab (-85)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffba (-70)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device 44:85:39:A6:C9:0A 44-85-39-A6-C9-0A
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffab (-85)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 41:3C:09:3F:69:03 RSSI: 0xffffffc1 (-63)
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffba (-70)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[CHG] Device 71:AF:D2:6F:A1:9C RSSI: 0xffffffb9 (-71)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device F9:98:7A:F9:BC:FE ID216
[CHG] Device 71:AF:D2:6F:A1:9C RSSI: 0xffffffc1 (-63)
[CHG] Device 42:9C:0F:1C:CD:8E RSSI: 0xffffffb5 (-75)
[CHG] Device 88:C6:26:F1:EC:C1 RSSI: 0xffffffab (-85)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Key: 0x0003 (3)
[CHG] Device 88:C6:26:F1:EC:C1 ManufacturerData Value:
  00 30 54 00 00 05 44 90 bb e6 28 de 88 c6 26 f1  .0T...D...(...&.
  ec c1 12                                         ...             
[NEW] Device 70:09:71:7A:97:99 [TV] Samsung AU8000 55 TV
[NEW] Device 5C:F6:DC:1B:57:42 5C-F6-DC-1B-57-42
[CHG] Device 5C:F6:DC:1B:57:42 RSSI is nil
[CHG] Device 70:09:71:7A:97:99 RSSI is nil
[CHG] Device F9:98:7A:F9:BC:FE RSSI is nil
[CHG] Device 44:85:39:A6:C9:0A TxPower is nil
[CHG] Device 44:85:39:A6:C9:0A RSSI is nil
[CHG] Device 71:AF:D2:6F:A1:9C TxPower is nil
[CHG] Device 71:AF:D2:6F:A1:9C RSSI is nil
[CHG] Device 72:49:FD:69:E4:28 TxPower is nil
[CHG] Device 72:49:FD:69:E4:28 RSSI is nil
[CHG] Device 79:85:7A:9C:38:6F TxPower is nil
[CHG] Device 79:85:7A:9C:38:6F RSSI is nil
[CHG] Device 67:43:5D:C2:12:BE TxPower is nil
[CHG] Device 67:43:5D:C2:12:BE RSSI is nil
[CHG] Device 73:19:CD:D7:3A:3A TxPower is nil
[CHG] Device 73:19:CD:D7:3A:3A RSSI is nil
[CHG] Device 10:BA:D1:EC:94:48 RSSI is nil
[CHG] Device 70:57:BF:AB:23:B4 TxPower is nil
[CHG] Device 70:57:BF:AB:23:B4 RSSI is nil
[CHG] Device 41:3C:09:3F:69:03 RSSI is nil
[CHG] Device 4F:EE:2A:6D:52:56 TxPower is nil
[CHG] Device 4F:EE:2A:6D:52:56 RSSI is nil
[CHG] Device D0:03:4B:24:CC:29 TxPower is nil
[CHG] Device D0:03:4B:24:CC:29 RSSI is nil
[CHG] Device 64:F2:30:28:83:FF TxPower is nil
[CHG] Device 64:F2:30:28:83:FF RSSI is nil
[CHG] Device 42:9C:0F:1C:CD:8E TxPower is nil
[CHG] Device 42:9C:0F:1C:CD:8E RSSI is nil
[CHG] Device 39:47:1E:39:9F:E4 RSSI is nil
[CHG] Device 88:C6:26:F1:EC:C1 RSSI is nil
[CHG] Device 38:18:4C:B6:A6:33 TxPower is nil
[CHG] Device 38:18:4C:B6:A6:33 RSSI is nil
[CHG] Controller 50:C2:E8:33:58:E0 Discovering: no
[CHG] Device 38:18:4C:B6:A6:33 Connected: yes
[CHG] Device 38:18:4C:B6:A6:33 Bonded: yes
[CHG] Device 38:18:4C:B6:A6:33 Modalias: usb:v054Cp0CE0d0137
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000fe26-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 0000fe2c-0000-1000-8000-00805f9b34fb
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 81c2e72a-0591-443e-a1ff-05f988593351
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 8901dfa8-5c7e-4d8f-9f0c-c2b70683f5f0
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
[CHG] Device 38:18:4C:B6:A6:33 UUIDs: f8d1fbe4-7966-4334-8024-ff96c9330e15
[CHG] Device 38:18:4C:B6:A6:33 ServicesResolved: yes
[CHG] Device 38:18:4C:B6:A6:33 Paired: yes
[CHG] Device 38:18:4C:B6:A6:33 Trusted: yes
[DEL] Device 70:57:BF:AB:23:B4 70-57-BF-AB-23-B4
[DEL] Device 72:49:FD:69:E4:28 72-49-FD-69-E4-28
[DEL] Device 10:BA:D1:EC:94:48 10-BA-D1-EC-94-48
[CHG] Device 38:18:4C:B6:A6:33 ServicesResolved: no
[CHG] Device 38:18:4C:B6:A6:33 Connected: no
[DEL] Device 73:19:CD:D7:3A:3A 73-19-CD-D7-3A-3A
[DEL] Device 44:85:39:A6:C9:0A 44-85-39-A6-C9-0A
[DEL] Device 41:3C:09:3F:69:03 Galaxy Watch5 Pro (S3TW)
[DEL] Device F9:98:7A:F9:BC:FE ID216
[DEL] Device D0:03:4B:24:CC:29 D0-03-4B-24-CC-29
[DEL] Device 64:F2:30:28:83:FF 64-F2-30-28-83-FF
[DEL] Device 71:AF:D2:6F:A1:9C 71-AF-D2-6F-A1-9C
[DEL] Device 88:C6:26:F1:EC:C1 88-C6-26-F1-EC-C1
[DEL] Device 39:47:1E:39:9F:E4 39-47-1E-39-9F-E4
[DEL] Device 70:09:71:7A:97:99 [TV] Samsung AU8000 55 TV
[DEL] Device 5C:F6:DC:1B:57:42 5C-F6-DC-1B-57-42
[DEL] Device 67:43:5D:C2:12:BE 67-43-5D-C2-12-BE
[DEL] Device 79:85:7A:9C:38:6F 79-85-7A-9C-38-6F
[DEL] Device 42:9C:0F:1C:CD:8E 42-9C-0F-1C-CD-8E
[DEL] Device 4F:EE:2A:6D:52:56 4F-EE-2A-6D-52-56
[bluetooth]# 

I noticed that the status always reports connected for a moment before re-reporting no. IDK if that is normal or not.

Offline

#8 2023-09-16 07:49:07

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,024

Offline

#9 2024-03-13 03:54:50

Jotunn
Member
Registered: 2023-04-29
Posts: 69

Re: [resolved] Unable to pair bluetooth devices.

I just ran everything back and it works now!
I'm not sure if a system update fixed it somewhere along the way of if the issue was with my devices all along and my PC was fine from the first.
Either way, it works now so I am marking the thread as resolved.
Thanks again for the help Seth!

Offline

Board footer

Powered by FluxBB