Bluetooth issues after March update

Thanks both. My limited understanding from reading the blog was that this ‘new way of doing things’ uses a keymap file and I think I already have one of those. I’ll have a check and backup if I can find it then.


So this “new way” mainly concerns the OSMC remote controls. If you don’t have a dongle for one of those remotes plugged in this new custom keymap is not loaded. If you use a keyboard, or another remote or controller that presents itself to Kodi as a keyboard then there may be some interaction which you can mitigate by turning off the custom map as outlined [here].

If you have existing keymaps your using in your userdata folder (including what is created by the Keymap Editor add-on) these are not deleted, modified, or disabled. Any existing keymaps are actually loaded after our new custom map so your tweaks will not only stay in place, they will also affect the OSMC remote as well.

I know! I reset the hub/remote’s profile from the iPhone app intentionally as I wanted to eliminate the harmony hub being the problem when trying to connect to Vero via Bluetooth.

Also, looks like I spoke too soon. Successfully paired the hub with vero via Bluetooth earlier, all looked good. Rebooted vero just now and the Bluetooth pairing has disappeared. Repaired again, connected via Bluetooth, rebooted, and same again…Bluetooth profile on vero has disappeared.

As suggested previously I should now probably upload a log, yes? Try and pair again via Bluetooth, enable debug logging, reboot and upload log? (Sorry, bit of a novice with this stuff).

That would probably be the best course of action. I can’t help with the bluetooth hub pairing stuff myself but without logs the people who can are limited on how much they can assist.

Yep, Bluetooth lost connection again. Hope I’ve done this correctly…

1 Like
Mar 26 16:42:09 osmc hciattach[406]: Initialization timed out.
Mar 26 16:42:09 osmc hciattach[406]: bcm43xx_init
Mar 26 16:42:09 osmc hciattach[406]: Flash firmware /etc/firmware/BCM4345C0.hcd
Mar 26 16:42:09 osmc systemd[1]: sdio-bt-firmware.service: Control process exited, code=exited status=1
Mar 26 16:42:09 osmc systemd[1]: Failed to start Vero3 Bluetooth support.
Mar 26 16:42:09 osmc systemd[1]: Startup finished in 3.491s (kernel) + 32.717s (userspace) = 36.208s.
Mar 26 16:42:09 osmc systemd[1]: sdio-bt-firmware.service: Unit entered failed state.
Mar 26 16:42:09 osmc systemd[1]: sdio-bt-firmware.service: Failed with result 'exit-code'.

This is the same error as in Bluetooth audio March update - #3 by G4eva

Can you run the following commands:

sudo systemctl start sdio-bt-firmware.service
systemctl status  sdio-bt-firmware.service

and show us the output.

Interesting. Thanks for the response. I do have a keyboard somewhere but I’m an absolute novice with regards to this. If I plugged a keyboard in, how would I access the command line? And is this all one command? Need to brave a supermarket as the cupboards are bare but will try when I get back. Thanks.

Probably easier to SSH to the box, though an attached keyboard will work. See Working with OSMC via the command line - General - OSMC

Hi. Managed to SSH in to Vero and ran the commands one at as time. Hope I’ve done it right. If not, let me know and I’ll have another go. Thanks.

Using your new-found SSH skils, can you run a few commands:

lsmod | grep hci
sudo modprobe hci_uart

Please copy/paste the text, rather than providing a screen print, since an image uses unnecessary space on the (Discourse) system.

Here you go…nothing happened after inputting the second command.

osmc@osmc:~$ lsmod | grep hci
hci_uart 21989 0
bluetooth 251555 2 btsdio,hci_uart
osmc@osmc:~$ sudo modprobe hci_uart

I’m on a non-plus Vero4K and can’t reproduce the error you see.

Let’s try a few more commands:

ls -l /etc/modprobe.d
ls -l /dev/ttyS*
ls -l /var/run/sdio*

osmc@osmc:~$ ls -l /etc/modprobe.d
total 4
-rw-r–r-- 1 root root 130 Nov 22 2017 blacklist-rc6.conf
osmc@osmc:~$ ls -l /dev/ttyS*
crw–w---- 1 root tty 243, 0 Mar 26 20:12 /dev/ttyS0
crw-rw---- 1 root dialout 243, 1 Mar 26 20:12 /dev/ttyS1
osmc@osmc:~$ ls -l
total 16
drwxr-xr-x 2 osmc osmc 4096 Feb 2 17:18 Movies
drwxr-xr-x 2 osmc osmc 4096 Feb 2 17:18 Music
drwxr-xr-x 2 osmc osmc 4096 Feb 2 17:18 Pictures
drwxr-xr-x 2 osmc osmc 4096 Feb 2 17:18 TV Shows

Some more:

ls -l /var/run/sdio*
sudo /usr/bin/hciattach -s 115200 /dev/ttyS1 bcm43xx 2000000

osmc@osmc:~$ ls -l /var/run/sdio*
-rw-r–r-- 1 root root 0 Mar 26 20:12 /var/run/sdio_0x02d0:0xa9bf
osmc@osmc:~$ lsmod
Module Size Used by
bnep 11588 2
hci_uart 21989 1
fuse 78234 7
iptable_nat 2948 0
nf_conntrack_ipv4 7917 1
nf_defrag_ipv4 1441 1 nf_conntrack_ipv4
nf_nat_ipv4 3881 1 iptable_nat
nf_nat 13147 2 nf_nat_ipv4,iptable_nat
nf_conntrack 57010 4 nf_nat,nf_nat_ipv4,iptable_nat,nf_conntrack_ipv4
iptable_filter 1478 0
btsdio 3186 0
bluetooth 251555 22 bnep,btsdio,hci_uart
6lowpan_iphc 6007 1 bluetooth
dwc_otg 231871 0
dhd 723320 0
cfg80211 356403 1 dhd
rtl2832_sdr 17192 0
videobuf2_vmalloc 5385 1 rtl2832_sdr
videobuf2_memops 1340 1 videobuf2_vmalloc
videobuf2_v4l2 11694 1 rtl2832_sdr
videobuf2_core 32162 2 rtl2832_sdr,videobuf2_v4l2
r820t 17233 4
mn88473 6605 2
rtl2832 11765 2
dvb_usb_rtl28xxu 18247 15
dvb_usb_v2 14350 1 dvb_usb_rtl28xxu
dvb_core 91192 3 rtl2832,mn88473,dvb_usb_v2
ir_lirc_codec 4708 9
lirc_dev 7992 1 ir_lirc_codec
wifi_dummy 798 0
mali 196602 5
meson_ir 3981 0
rc_core 22791 8 lirc_dev,meson_ir,ir_lirc_codec,dvb_usb_rtl28xxu,dvb_usb_v2
amlvideodri 11554 1
videobuf_res 5514 1 amlvideodri
videobuf_core 16691 2 amlvideodri,videobuf_res
videodev 148029 5 amlvideodri,rtl2832_sdr,videobuf2_core,videobuf2_v4l2
media 21515 3 dvb_usb_v2,videodev,dvb_core
ip_tables 16731 2 iptable_filter,iptable_nat
x_tables 18035 2 ip_tables,iptable_filter
osmc@osmc:~$ sudo /usr/bin/hciattach -s 115200 /dev/ttyS1 bcm43xx 2000000
Failed to write reset command
Can’t initialize device: Success

Please try that command one more time.

osmc@osmc:~$ sudo /usr/bin/hciattach -s 115200 /dev/ttyS1 bcm43xx 2000000
Failed to write reset command
Can’t initialize device: Success

Sometimes shutting the device down at the mains for a minute or two resolves this issue.

ok, will try now.