Microsoft foldable keyboard doesn't connect

Can't connect with Microsoft foldable keyboard, "Connection Failed: Software caused connection abort". I'm asking for solving this problem because this keyboard works on Ubuntu 18.04 LTS (haven't tried the last release yet), android, and Raspberry Pi (tips from the Internet).
inxi -Fxxxz:

System:

  Host: Asus-pc Kernel: 5.6.12-1-MANJARO x86_64 bits: 64 compiler: gcc  
  v: 9.3.0 Desktop: KDE Plasma 5.18.5 tk: Qt 5.14.2 wm: kwin_x11 dm: SDDM  
  Distro: Manjaro Linux  
Machine:

  Type: Laptop System: LENOVO product: 81D2 v: Lenovo ideapad 330-15ARR  
  serial: <filter> Chassis: type: 10 v: Lenovo ideapad 330-15ARR  
  serial: <filter>  
  Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <filter> UEFI: LENOVO  
  v: 7VCN48WW date: 09/26/2019  
Battery:

  ID-1: BAT0 charge: 28.1 Wh condition: 28.4/35.0 Wh (81%) volts: 8.5/7.5  
  model: SMP L17M2PF0 type: Li-poly serial: <filter> status: Unknown  
CPU:

  Topology: Dual Core  
  model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx bits: 64  
  type: MT MCP arch: Zen L2 cache: 1024 KiB  
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm  
  bogomips: 19969  
  Speed: 2666 MHz min/max: 1600/2500 MHz boost: enabled  
  Core speeds (MHz): 1: 2526 2: 2554 3: 1469 4: 1555  
Graphics:

  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile  
  Series]  
  vendor: Lenovo driver: amdgpu v: kernel bus ID: 03:00.0  
  chip ID: 1002:15dd  
  Display: x11 server: X.Org 1.20.8 driver: amdgpu FAILED: ati  
  unloaded: modesetting alternate: fbdev,vesa compositor: kwin_x11  
  resolution: 1920x1080~60Hz  
  OpenGL: renderer: AMD RAVEN (DRM 3.36.0 5.6.12-1-MANJARO LLVM 10.0.0)  
  v: 4.6 Mesa 20.0.6 direct render: Yes  
Audio:

  Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Lenovo  
  driver: snd_hda_intel v: kernel bus ID: 03:00.1 chip ID: 1002:15de  
  Device-2: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel  
  v: kernel bus ID: 03:00.6 chip ID: 1022:15e3  
  Sound Server: ALSA v: k5.6.12-1-MANJARO  
Network:

  Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter  
  vendor: Lenovo driver: rtl8821ce v: N/A port: 3000 bus ID: 01:00.0  
  chip ID: 10ec:c821  
  IF: wlp1s0 state: up mac: <filter>  
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet  
  vendor: Lenovo driver: r8169 v: kernel port: 2000 bus ID: 02:00.0  
  chip ID: 10ec:8168  
  IF: enp2s0 state: down mac: <filter>  
Drives:

  Local Storage: total: 238.47 GiB used: 43.71 GiB (18.3%)  
  ID-1: /dev/sda vendor: Micron model: MTFDDAK256TBN size: 238.47 GiB  
  speed: 6.0 Gb/s serial: <filter> rev: N001 scheme: GPT  
Partition:

  ID-1: / size: 233.43 GiB used: 43.71 GiB (18.7%) fs: ext4  
  dev: /dev/sda2  
Sensors:

  System Temperatures: cpu: 48.5 C mobo: N/A gpu: amdgpu temp: 48 C  
  Fan Speeds (RPM): N/A  
Info:

  Processes: 249 Uptime: 1h 22m Memory: 7.39 GiB used: 4.88 GiB (65.9%)  
  Init: systemd v: 245 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.16  
  running in: konsole inxi: 3.0.37 

What happens if I try to connect keyboard:


"Connection Failed: Software caused connection abort".

I have searched for solving the issue, but find a solution only for Raspberry Pi, but not for Manjaro:


Well, I thought that the same attempt could solve the problem, but I haven't found any useful advice.
https://wiki.archlinux.org/index.php/bluetooth#Pairing
I tried to connect through a terminal with commands:
[maincpp@Asus-pc ~]$ bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller B0:FC:36:BA:5A:90 Discovering: yes
[CHG] Device 00:15:83:4F:E2:B0 RSSI: -72
[CHG] Device 00:15:83:4F:E2:B0 RSSI: -62
[CHG] Device FF:91:F1:48:78:6C TxPower: 2
[CHG] Device 00:15:83:4F:E2:B0 RSSI: -72
[CHG] Device 00:15:83:4F:E2:B0 RSSI: -62
[bluetooth]# scan off
Discovery stopped
[CHG] Controller B0:FC:36:BA:5A:90 Discovering: no
[CHG] Device FF:91:F1:48:78:6C TxPower is nil
[CHG] Device 00:15:83:4F:E2:B0 RSSI is nil
[bluetooth]# pair FF:91:F1:48:78:6C
Attempting to pair with FF:91:F1:48:78:6C
[CHG] Device FF:91:F1:48:78:6C Connected: yes
[agent] Passkey: 040970
[NEW] Primary Service (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service0001
        00001801-0000-1000-8000-00805f9b34fb
        Generic Attribute Profile
[NEW] Characteristic (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service0001/char0002
        00002a05-0000-1000-8000-00805f9b34fb
        Service Changed
[NEW] Descriptor (Handle 0x69f4)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service0001/char0002/desc0004
        00002902-0000-1000-8000-00805f9b34fb
        Client Characteristic Configuration
[NEW] Primary Service (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service002f
        a74df799-13fd-4f82-a45a-0340180eac97
        Vendor specific
[NEW] Characteristic (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service002f/char0030
        343f8f87-ec68-41a7-a97f-3141b2424e1d
        Vendor specific
[NEW] Primary Service (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service0032
        00001016-d102-11e1-9b23-00025b00a5a5
        Vendor specific
[NEW] Characteristic (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service0032/char0033
        00001013-d102-11e1-9b23-00025b00a5a5
        Vendor specific
[NEW] Characteristic (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service0032/char0035
        00001018-d102-11e1-9b23-00025b00a5a5
        Vendor specific
[NEW] Characteristic (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service0032/char0037
        00001014-d102-11e1-9b23-00025b00a5a5
        Vendor specific
[NEW] Descriptor (Handle 0x2134)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service0032/char0037/desc0039
        00002902-0000-1000-8000-00805f9b34fb
        Client Characteristic Configuration
[NEW] Primary Service (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service003a
        0000180a-0000-1000-8000-00805f9b34fb
        Device Information
[NEW] Characteristic (Handle 0xb83e)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service003a/char003b
        00002a26-0000-1000-8000-00805f9b34fb
        Firmware Revision String
[NEW] Characteristic (Handle 0xb1fe)
        /org/bluez/hci0/dev_FF_91_F1_48_78_6C/service003a/char003d
        00002a50-0000-1000-8000-00805f9b34fb
        PnP ID
[CHG] Device FF:91:F1:48:78:6C UUIDs: 00001016-d102-11e1-9b23-00025b00a5a5
[CHG] Device FF:91:F1:48:78:6C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F1:48:78:6C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F1:48:78:6C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F1:48:78:6C UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F1:48:78:6C UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F1:48:78:6C UUIDs: 00001813-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F1:48:78:6C UUIDs: a74df799-13fd-4f82-a45a-0340180eac97
[CHG] Device FF:91:F1:48:78:6C ServicesResolved: yes
[CHG] Device FF:91:F1:48:78:6C Paired: yes
Pairing successful
[CHG] Device FF:91:F1:48:78:6C Modalias: usb:v045Ep080Cd0110
[DEL] Device 44:AD:09:B3:32:11 44-AD-09-B3-32-11
[DEL] Device 75:1D:C2:A1:7F:8F 75-1D-C2-A1-7F-8F
[UniversalFoldableKb]# 

You can see that it shows that the keyboard is compared without issues, but, but it isn't! When I type on its, nothing happens on my laptop, so it's false. Also, I find that it requires typing row of numbers (see code up), but it doesn't wait for me until I'll type this, I don't know why. I've tried everything but haven't able to do this on my own. Can you help me, please?

Half of a day and issue has solved!
https://wiki.archlinux.org/index.php/Bluetooth_keyboard

[maincpp@Asus-pc ~]$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
Bus 003 Device 002: ID 174f:116a Syntek EasyCamera
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[maincpp@Asus-pc ~]$ bluetoothctl
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent KeyboardOnly
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller B0:FC:36:BA:5A:90 Discovering: yes
[NEW] Device 53:A0:95:B5:4D:86 53-A0-95-B5-4D-86
[NEW] Device FF:91:F4:48:78:6C UniversalFoldableKb
[CHG] Device 00:15:83:4F:E2:B0 RSSI: -68
[NEW] Device 75:99:73:3D:AF:53 75-99-73-3D-AF-53
[CHG] Device 53:A0:95:B5:4D:86 RSSI: -82
[CHG] Device 53:A0:95:B5:4D:86 ManufacturerData Key: 0x004c
[CHG] Device 53:A0:95:B5:4D:86 ManufacturerData Value:
  10 05 17 18 cf 37 a3                             .....7.         
[CHG] Device 00:15:83:4F:E2:B0 RSSI: -56
[bluetooth]# pair FF:91:F4:48:78:6C
Attempting to pair with FF:91:F4:48:78:6C
Failed to pair: org.bluez.Error.AuthenticationRejected
[CHG] Device FF:91:F4:48:78:6C Connected: yes
[agent] Passkey: 487344
[NEW] Primary Service (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service0001
        00001801-0000-1000-8000-00805f9b34fb
        Generic Attribute Profile
[NEW] Characteristic (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service0001/char0002
        00002a05-0000-1000-8000-00805f9b34fb
        Service Changed
[NEW] Descriptor (Handle 0x5a94)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service0001/char0002/desc0004
        00002902-0000-1000-8000-00805f9b34fb
        Client Characteristic Configuration
[NEW] Primary Service (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service002f
        a74df799-13fd-4f82-a45a-0340180eac97
        Vendor specific
[NEW] Characteristic (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service002f/char0030
        343f8f87-ec68-41a7-a97f-3141b2424e1d
        Vendor specific
[NEW] Primary Service (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service0032
        00001016-d102-11e1-9b23-00025b00a5a5
        Vendor specific
[NEW] Characteristic (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service0032/char0033
        00001013-d102-11e1-9b23-00025b00a5a5
        Vendor specific
[NEW] Characteristic (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service0032/char0035
        00001018-d102-11e1-9b23-00025b00a5a5
        Vendor specific
[NEW] Characteristic (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service0032/char0037
        00001014-d102-11e1-9b23-00025b00a5a5
        Vendor specific
[NEW] Descriptor (Handle 0x29d4)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service0032/char0037/desc0039
        00002902-0000-1000-8000-00805f9b34fb
        Client Characteristic Configuration
[NEW] Primary Service (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service003a
        0000180a-0000-1000-8000-00805f9b34fb
        Device Information
[NEW] Characteristic (Handle 0x983e)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service003a/char003b
        00002a26-0000-1000-8000-00805f9b34fb
        Firmware Revision String
[NEW] Characteristic (Handle 0x91fe)
        /org/bluez/hci0/dev_FF_91_F4_48_78_6C/service003a/char003d
        00002a50-0000-1000-8000-00805f9b34fb
        PnP ID
[CHG] Device FF:91:F4:48:78:6C UUIDs: 00001016-d102-11e1-9b23-00025b00a5a5
[CHG] Device FF:91:F4:48:78:6C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F4:48:78:6C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F4:48:78:6C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F4:48:78:6C UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F4:48:78:6C UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F4:48:78:6C UUIDs: 00001813-0000-1000-8000-00805f9b34fb
[CHG] Device FF:91:F4:48:78:6C UUIDs: a74df799-13fd-4f82-a45a-0340180eac97
[CHG] Device FF:91:F4:48:78:6C ServicesResolved: yes
[CHG] Device 75:99:73:3D:AF:53 ManufacturerData Key: 0x004c
[CHG] Device 75:99:73:3D:AF:53 ManufacturerData Value:
  10 05 2e 18 37 84 cb                             ....7..         
[CHG] Device 53:A0:95:B5:4D:86 RSSI is nil
[UniversalFoldableKb]# scan off
[CHG] Device 75:99:73:3D:AF:53 TxPower is nil
[CHG] Device 75:99:73:3D:AF:53 RSSI is nil
[CHG] Device 00:15:83:4F:E2:B0 RSSI is nil
[CHG] Device FF:91:F4:48:78:6C TxPower is nil
[CHG] Device FF:91:F4:48:78:6C RSSI is nil
[CHG] Device 53:A0:95:B5:4D:86 TxPower is nil
[CHG] Controller B0:FC:36:BA:5A:90 Discovering: no
Discovery stopped
[CHG] Device FF:91:F4:48:78:6C ServicesResolved: no
[CHG] Device FF:91:F4:48:78:6C Connected: no
[CHG] Device FF:91:F4:48:78:6C Connected: yes
[agent] Passkey: 688654
[CHG] Device FF:91:F4:48:78:6C Paired: yes
[CHG] Device FF:91:F4:48:78:6C Modalias: usb:v045Ep080Cd0110
[CHG] Device FF:91:F4:48:78:6C ServicesResolved: yes
[UniversalFoldableKb]# 

Well, I've tried different ways to solve it, my solution step-by-step:

  1. I read that a wi-fi connection can make an effect on Bluetooth pairing, so I turned off its and reboot my laptop.
  2. The second attempt trying keyboard way above:
    Make sure that command "bluetoothctl" is available in your system (if not, install the bluez-utils package, providing the bluetoothctl utility. https://wiki.archlinux.org/index.php/bluetooth). After that:
    $ bluetoothctl
    $ power on
    $ scan on (make sure your keyboard in connection mode).
    $ scan off (only when your keyboard shows in lists). Then, copy mac_adress. In my case, it names "FF:91:F4:48:78:6C".
    $ pair name_of_mac_adress
    then, it requires to input row of numbers on your own device.
    Ta-da, mission passed + respect.
  3. If your keyboard doesn't still work (like in my case), turn on wi-fi, go to https://wiki.archlinux.org/index.php/Bluetooth_keyboard and follow commands step-by-step. It helped me to connect the keyboard.
    Make sure your keyboard in Linux/Android mode + searched mode (keyboard becomes available to connecting its) before you'll start to do all of these commands!
1 Like

Forum kindly sponsored by