[SOLVED] Fedora 37 Wireless Earbuds Will Not Pair

Been hunting down this issue for a day now and it’s driving me crazy. Have my batch 2 11th gen Framework and have been running Fedora on it, hadn’t bothered to upgrade from Fedora 35. In all this time, I have never been able to connect my bluetooth earbuds to this device.

I finally decided it was time to change up my current workflow and cut out some fat from my applications, so I decided to do a completely fresh install of Fedora 37. I had hoped that this would mean I could finally connect my earbuds, but to no avail.

I have searched for hours today and not found any solution to my issue, despite trying numerous ways to pair. My Bluetooth hardware and firmware seem to be running fine and I can pair, connect and use my bluetooth mouse with no issue, it seems to be exclusively related to the earbuds. I have no errors with bluetooth in dmesg or the kernel logs that I have been able to see.

The only info I have been able to gather thus far is this:

When trying to pair via bluetoothctl, the console returns:

Attempting to pair with 27:A5:11:0D:A2:34
Failed to pair: org.bluez.Error.AuthenticationTimeout

Doing a journalctl on bluetoothd shows a connect_failed_callback():

Dec 30 17:34:29 Laptop bluetoothd[5572]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 27:A5:11:0D:A2:34 type 0 status 0x8
Dec 30 17:34:29 Laptop bluetoothd[5572]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 27:A5:11:0D:A2:34 type 0 status 0x8
Dec 30 17:34:29 Laptop bluetoothd[5572]: src/adapter.c:connect_failed_callback() hci0 27:A5:11:0D:A2:34 status 8
Dec 30 17:33:59 Laptop bluetoothd[5572]: src/adapter.c:adapter_bonding_attempt() hci0 bdaddr 27:A5:11:0D:A2:34 type 0 io_cap 0x04
Dec 30 17:33:59 Laptop bluetoothd[5572]: src/device.c:bonding_request_new() Requesting bonding for 27:A5:11:0D:A2:34
Dec 30 17:33:49 Laptop bluetoothd[5572]: src/adapter.c:device_found_callback() hci0 addr 27:A5:11:0D:A2:34, rssi -58 flags 0x0000 eir_len 17

My Bluetooth adapter is not blocked by rfkill, My /etc/bluetooth/main.conf has the cotroller set to dual mode, I have also reinstalled pipewire and bluez and I have seen no change in this error message throughout, so I am absolutely missing something somewhere, I have just run out of ideas for places to look.

Have you already tried this?

@Sven_Hiller Yes, I have. I receive the same Timeout error whether the controller is in dual or bredr mode.

I too couldn’t pair my AirPods Pro 2 on Fedora 37. What worked for me was resetting the AirPods by pressing the button on the back of the case around 15 seconds (marked by chirp and stop of white flashing).
Then the pairing with the Framework worked flawlessly and the reconnection with my Apple devices worked too. Now I can switch between the laptop and other devices like you’d expect.

Additional context :

  • Found this fix after restarting the laptop and bluetooth, not sure if this is needed.
  • The AirPods mic works too, according to the Sound Settings.
  • It was the first time I tried to pair the AirPods with this laptop. Usually my Bluetooth issues are solved by removing the device from the list and repairing it again.
  • I didn’t need to edit any files, did everything from the UI.
  • Resetting your AirPods means they forget having been connected to your Apple or other devices and will appear as new devices when pairing them again. If you have customized their name or gesture controls on Apple devices, you probably want to check their device settings after pairing.
1 Like

@Test_Person I have a set of Raycon E50’s. Gave them a factory reset anyway, and restarted my device.

Interestingly, this time my bluetooth did not restart properly on my framework. I saw this in dmesg:

[   29.135891] Bluetooth: hci0: setting interface failed (110)
[   50.256083] Bluetooth: hci0: Opcode 0x c03 failed: -110
[   52.304201] Bluetooth: hci0: Failed to read MSFT supported features (-110)

And this was in the status of the service:

Failed to set mode: Authentication Failed (0x05)

I couldn’t enable the adapter at all. I had to reset the kernel btusb module by doing:

rmmod btusb
modprobeusb

After resetting this, the bluetooth came back on, but sadly I was still not able to pair to the factory reset earbuds. :confused:

Ran a btmon while trying to pair.

@ MGMT Command: Pair Device (0x0019) plen 8                                         {0x0001} [hci0] 92.161157
        BR/EDR Address: 27:A5:11:0D:A2:34 (OUI 27-A5-11)
        Capability: DisplayYesNo (0x01)
> HCI Event: Command Complete (0x0e) plen 4                                              #19 [hci0] 92.162527
      LE Set Extended Scan Parameters (0x08|0x0041) ncmd 1
        Status: Success (0x00)
< HCI Command: Create Connection (0x01|0x0005) plen 13                                   #20 [hci0] 92.162563
        Address: 27:A5:11:0D:A2:34 (OUI 27-A5-11)
        Packet type: 0xcc18
          DM1 may be used
          DH1 may be used
          DM3 may be used
          DH3 may be used
          DM5 may be used
          DH5 may be used
        Page scan repetition mode: R2 (0x02)
        Page scan mode: Mandatory (0x00)
        Clock offset: 0x0000
        Role switch: Allow peripheral (0x01)
> HCI Event: Command Status (0x0f) plen 4                                                #21 [hci0] 92.164522
      Create Connection (0x01|0x0005) ncmd 1
        Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6                          #22 [hci0] 92.164543
        Extended scan: Enabled (0x01)
        Filter duplicates: Enabled (0x01)
        Duration: 0 msec (0x0000)
        Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4                                              #23 [hci0] 92.165514
      LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
        Status: Success (0x00)
< HCI Command: Write Scan Enable (0x03|0x001a) plen 1                                    #24 [hci0] 92.165649
        Scan enable: Page Scan (0x02)
> HCI Event: Command Complete (0x0e) plen 4                                              #25 [hci0] 92.197585
      Write Scan Enable (0x03|0x001a) ncmd 2
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 57                                                #26 [hci0] 92.753653
      LE Extended Advertising Report (0x0d)
        Num reports: 1
        Entry 0
          Event type: 0x0010
            Props: 0x0010
              Use legacy advertising PDUs
            Data status: Complete
          Legacy PDU Type: ADV_NONCONN_IND (0x0010)
          Address type: Random (0x01)
          Address: 54:60:A6:91:B9:6D (Resolvable)
          Primary PHY: LE 1M
          Secondary PHY: No packets
          SID: no ADI field (0xff)
          TX power: 127 dBm
          RSSI: -81 dBm (0xaf)
          Periodic advertising interval: 0.00 msec (0x0000)
          Direct address type: Public (0x00)
          Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
          Data length: 0x1f
        1e ff 06 00 01 09 20 02 08 01 bd 21 44 7b c2 8b  ...... ....!D{..
        d7 90 f5 94 ae 1a 84 12 af c8 89 94 b3 b1 a3     ............... 
        Company: Microsoft (6)
          Data: 010920020801bd21447bc28bd790f594ae1a8412afc88994b3b1a3
> HCI Event: LE Meta Event (0x3e) plen 48                                                #27 [hci0] 93.818728
      LE Extended Advertising Report (0x0d)
        Num reports: 1
        Entry 0
          Event type: 0x0013
            Props: 0x0013
              Connectable
              Scannable
              Use legacy advertising PDUs
            Data status: Complete
          Legacy PDU Type: ADV_IND (0x0013)
          Address type: Random (0x01)
          Address: 7F:B9:F3:62:CC:C2 (Resolvable)
          Primary PHY: LE 1M
          Secondary PHY: No packets
          SID: no ADI field (0xff)
          TX power: 127 dBm
          RSSI: -100 dBm (0x9c)
          Periodic advertising interval: 0.00 msec (0x0000)
          Direct address type: Public (0x00)
          Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
          Data length: 0x16
        02 01 02 0e ff 75 00 01 00 02 00 01 02 ff 00 00  .....u..........
        43 09 03 19 c0 00                                C.....          
        Flags: 0x02
          LE General Discoverable Mode
        Company: Samsung Electronics Co. Ltd. (117)
          Data: 010002000102ff00004309
        Appearance: Watch (0x00c0)
> HCI Event: LE Meta Event (0x3e) plen 56                                                #28 [hci0] 95.199590
      LE Extended Advertising Report (0x0d)
        Num reports: 1
        Entry 0
          Event type: 0x0013
            Props: 0x0013
              Connectable
              Scannable
              Use legacy advertising PDUs
            Data status: Complete
          Legacy PDU Type: ADV_IND (0x0013)
          Address type: Random (0x01)
          Address: CE:31:46:E5:DF:EA (Static)
          Primary PHY: LE 1M
          Secondary PHY: No packets
          SID: no ADI field (0xff)
          TX power: 127 dBm
          RSSI: -84 dBm (0xac)
          Periodic advertising interval: 0.00 msec (0x0000)
          Direct address type: Public (0x00)
          Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
          Data length: 0x1e
        02 01 06 11 06 e8 bf 6c cf 17 8b 32 b8 4c 48 6a  .......l...2.LHj
        e5 00 ff ba ab 08 16 0a 18 39 04 41 66 01        .........9.Af.  
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        128-bit Service UUIDs (partial): 1 entry
          Vendor specific
        Service Data: Device Information (0x180a)
          Data: 3904416601
> HCI Event: LE Meta Event (0x3e) plen 29                                                #29 [hci0] 95.978641
      LE Extended Advertising Report (0x0d)
        Num reports: 1
        Entry 0
          Event type: 0x0013
            Props: 0x0013
              Connectable
              Scannable
              Use legacy advertising PDUs
            Data status: Complete
          Legacy PDU Type: ADV_IND (0x0013)
          Address type: Random (0x01)
          Address: 4B:E6:A3:25:85:02 (Resolvable)
          Primary PHY: LE 1M
          Secondary PHY: No packets
          SID: no ADI field (0xff)
          TX power: 127 dBm
          RSSI: -100 dBm (0x9c)
          Periodic advertising interval: 0.00 msec (0x0000)
          Direct address type: Public (0x00)
          Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
          Data length: 0x03
        02 01 02                                         ...             
        Flags: 0x02
          LE General Discoverable Mode
> HCI Event: Connect Complete (0x03) plen 11                                            #30 [hci0] 123.796571
        Status: LMP Response Timeout / LL Response Timeout (0x22)
        Handle: 65535
        Address: 27:A5:11:0D:A2:34 (OUI 27-A5-11)
        Link type: ACL (0x01)
        Encryption: Disabled (0x00)
@ MGMT Event: Connect Failed (0x000d) plen 8                                       {0x0001} [hci0] 123.796678
        BR/EDR Address: 27:A5:11:0D:A2:34 (OUI 27-A5-11)
        Status: Timeout (0x08)
@ MGMT Event: Command Complete (0x0001) plen 10                                    {0x0001} [hci0] 123.796686
      Pair Device (0x0019) plen 7
        Status: Timeout (0x08)
        BR/EDR Address: 27:A5:11:0D:A2:34 (OUI 27-A5-11)
@ MGMT Command: Remove Device (0x0034) plen 7                                      {0x0001} [hci0] 123.834907
        BR/EDR Address: 27:A5:11:0D:A2:34 (OUI 27-A5-11)
@ MGMT Event: Command Complete (0x0001) plen 10                                    {0x0001} [hci0] 123.834923
      Remove Device (0x0034) plen 7
        Status: Success (0x00)
        BR/EDR Address: 27:A5:11:0D:A2:34 (OUI 27-A5-11)

For Airpods and likely other select earbuds (this guide assumes Gnome), in the terminal:

sudo cp /etc/bluetooth/main.conf /etc/bluetooth/main.bak

then

sudo gedit /etc/bluetooth/main.conf

Press Ctrl F and search for ControllerMod

Make sure ControllerMode = dual is set to ControllerMode = bredr

So we’re trying dual to bredr.

Save the file, then reboot. Try pairing again.

2 Likes