Bluetooth keyboard stopped working after Nov.2020 Beta update

Hi, I just received a Vero 4K+ which I updated to the current software version two days ago. Yesterday I installed the Beta Update as described here in the forum. The update went smoothly, but my bluetooth keyboard that worked before is not working any more after the update. It is still being shown as a paired device under My OSMC, but all input will be ignored. Does anyone know more about this? Any workarounds? Thanks in advance! :wink:

Hi,

Thanks for opening the post here (tickets are usually for returns; sales queries etc).

Firstly – what model of keyboard do you have?

You could try unpairing the device and re-pairing as a first step and see if this helps

Otherwise, some logs may provide us some clues. It’s possible the 4.9 kernel (experimental) doesn’t support your specific Bluetooth device. If that’s the case, it should be trivial to re-add support for you.

Sam

Hi Sam,

it’s a cheap but sufficient backlit Jelly Comb as available here:

https://www.amazon.de/gp/product/B089SMN3L6/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

I already did unpairing/pairing of course but to no avail. I can definitively say that pairing was no problem with the official version that I updated to after receiving the (btw great) device three days ago.

Concerning the upload of logs: I just uses the Log Uploader from the My OSMC menu. Would that be enough or would you need something more?

Bye

Yes, use the log uploader, but please turn on debugging first.

You can often get better results using the commandline bluetoothctl.

If using bluetoothctl, start it from the commandline, make your BT device discoverable, then

agent on
scan on

Wait for your keyboard to show up, then, using its MAC instead of 01:23:45:67:89:ab:

pair 01:23:45:67:89:ab
trust 01:23:45:67:89:ab
connect 01:23:45:67:89:ab
scan off
agent off
quit

No problem, I did as asked:

osmc@osmc:~$ bluetoothctl
[NEW] Controller B0:02:47:F4:99:72 osmc [default]
[NEW] Device CC:90:93:10:D5:17 Surround Set
[NEW] Device 20:20:01:30:2B:93 Wireless Keyboard
[bluetooth]# pair 20:20:01:30:2B:93
Attempting to pair with 20:20:01:30:2B:93
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# trust 20:20:01:30:2B:93
Changing 20:20:01:30:2B:93 trust succeeded
[bluetooth]# connect 20:20:01:30:2B:93
Attempting to connect to 20:20:01:30:2B:93
[CHG] Device 20:20:01:30:2B:93 Connected: yes
Connection successful
[CHG] Device 20:20:01:30:2B:93 ServicesResolved: yes
[Wireless Keyboard]# scan off
Failed to stop discovery: org.bluez.Error.Failed
[Wireless Keyboard]# agent off
No agent is registered
[Wireless Keyboard]# quit
[DEL] Controller B0:02:47:F4:99:72 osmc [default]

Even though connect succeded, no reaction to key input. :frowning:

Try remove the device then re-pairing it.

I removed the keyboard using bluetoothctl and then paired again through My OSMC. Still no change. Pairing looks okay but no keyboard commands are accepted…

Can you post the output of bluetoothctl info 20:20:01:30:2B:93 info CC:90:93:10:D5:17 and grab-logs -A please.

also try pairing with bluetoothctl - you may see some useful error messages.

Yesssir, here you go:

[bluetooth]# info 20:20:01:30:2B:93
Device 20:20:01:30:2B:93
Name: Wireless Keyboard
Alias: Wireless Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: yes
UUID: Service Discovery Serve… (00001000-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device… (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v05ACp022Cd0001
[bluetooth]# info CC:90:93:10:D5:17
Device CC:90:93:10:D5:17
Name: Surround Set
Alias: Surround Set
Class: 0x240404
Icon: audio-card
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)

I don’t connect to the Surround Set though, that’s for something else for now.

Logs @ https://paste.osmc.tv/qoxekohoci

Already tried pairing by command line (see post #7):

[bluetooth]# pair 20:20:01:30:2B:93
Attempting to pair with 20:20:01:30:2B:93
Failed to pair: org.bluez.Error.AlreadyExists

Hope this helps…

Yes ‘Already exists’ but what do you get with connect 20:20:01:30:2B:93 as the info command says

I had a case of this:

[bluetooth]# connect 20:20:01:30:2B:93
Attempting to connect to 20:20:01:30:2B:93
Failed to connect: org.bluez.Error.Failed
[CHG] Device 20:20:01:30:2B:93 Class: 0x000540
[CHG] Device 20:20:01:30:2B:93 Icon: input-keyboard
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 Class: 0x002540
[CHG] Device 20:20:01:30:2B:93 Icon: input-keyboard
[CHG] Device 20:20:01:30:2B:93 Connected: yes
[CHG] Device 20:20:01:30:2B:93 Connected: no
[CHG] Device 20:20:01:30:2B:93 RSSI: -39

But after activating device discovery it went through:

[bluetooth]# connect 20:20:01:30:2B:93
Attempting to connect to 20:20:01:30:2B:93
[CHG] Device 20:20:01:30:2B:93 Connected: yes
Connection successful
[CHG] Device 20:20:01:30:2B:93 ServicesResolved: yes

As I said, the keyboard looks fine and connected in My OSMC, there is just no response from Kodi when I try to use it since the update to 4.9 Beta.

Try

sudo apt-get update
sudo apt-get install libbluetooth3
reboot

Done! No further updates on the first command, libbluetooth3 installed on the second. After rebooting the keyboard paired as before but is still not working unfortunately…

Well I’m stumped. My BT KB is working fine with 4.9 (updated to the latest just to be sure) and Kodi Matrix. Does your KB work with other devices,still?

Come to that, are there other devices around that the KB is connecting to when you are trying to connect Vero?

I checked with my tablet PC and and it connected and worked well. There are no other devices around except a surround speaker set but I deactivated bluetooth now. Still no change. The point is, the keyboard worked before the update so I suppose something is still not right with the update. Didn’t the logs help in any way?

That’s what I was wondering.

Have you tried exiting Kodi (power icon -> exit) after pairing and seeing if it helps?

Hello Sam, just did that. The device was still paired when Kodi came back up. Still no feedback when trying to navigate with the keyboard. Could it help comparing the regular repository with the updates from 4.9 Beta and check for the packages that could cause trouble?

They did, thanks, but only to confirm what packages you have and your settings. The details of BT communications is a whole other level and a bit outside my paygrade.

If you have a BT USB dongle you could try that, but I can’t recall how to disable the internal BT device. @sam_nazarko will know.

The other thing you could try is can you connect to any other BT device? Do you have another KB or mouse? Or you could even try your audio device. [How-to] install bluez-alsa for Bluetooth audio

@grahamh: What BT KB do you use?

It looks a lot like yours - branded LOGIK and sold by a big box retailer here in UK. No longer, though.