Help needed with bluetooth keyboard

Devices
1

My older bluetooth keyboards stopped working and i am trying to get e new one, particularly for using it with my xperia 10iii with sailfish os.

This is not successful. I now ran into the second bluetooth keyboard that is not working with the sailfish os. The keyboard can be paired and shows up in the device list but not as a keyboard. And so input is not possible. It works fine with other android devices.

The keyboards show only GAP as supported profiles when connected to my sailfish phone.

I have no idea how to proceed from here. Is there a limitation to what kind of bluetooth keyboards can be connected to sailfish os?

Any hints and advice welcome!

2

Doubt it helps but just my experience. I bought this one a while back as a cheap input device for a project I was working on at the time, can confirm it works fine on my 10 IV…

3

ssh into your device and enter devel-su journalctl -f then try to connect the keyboard. Show us the output.

1 Like
4

My first nonworking device: HZ-2758 (this one)

Device B6:7A:DF:XX:XX:X (public)
        Name: SmartRemote
        Alias: SmartRemote
        Appearance: 0x03c1 (961)
        Icon: input-keyboard
        Paired: yes
        Bonded: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        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: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
        UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
        UUID: Unknown                   (0000ae40-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v05ACp022Cd011B
        Battery Percentage: 0x58 (88)

I can pair no problem, and after pairing it stays connected, but any button press shows no effect (it should be registering with mpris??).

journal has nothing interesteng. evdev_trace shows nothing.

Another keyboard that does not work, this one has two BT “channels”, so you can pair two devices and switch:

Device DE:9E:51:xx:xx:xx(random)
        Name: Wireless Keyboard
        Alias: Ständer I
        Appearance: 0x03c1 (961)
        Icon: input-keyboard
        Paired: yes
        Bonded: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
        UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
        UUID: Unknown                   (0000ff00-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v04E8p7021d0001

 Device DE:9E:51:xx:xx:xx(random)
        Name: Wireless Keyboard
        Alias: Ständer II
        Appearance: 0x03c1 (961)
        Icon: input-keyboard
        Paired: yes
        Bonded: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
        UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
        UUID: Unknown                   (0000ff00-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v04E8p7021d0001
1 Like