CoreELEC:~ # udevadm info /sys/bus/sdio/devices/*
P: /devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
L: 0
E: DEVPATH=/devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=rtl8723bs
E: SDIO_CLASS=07
E: SDIO_ID=024C:B723
E: MODALIAS=sdio:c07v024CdB723
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=11597526
E: SYSTEMD_WANTS=rtl8723bs_bt-firmware.service
E: TAGS=:systemd:
Thats a realtek chip, not a qualcomm and from what you have pasted it looks like you are using an old version of CE.
##############################################
CoreELEC
https://coreelec.org
##############################################
CoreELEC (official): 9.2.2 (Amlogic.arm)
CoreELEC:~ # lsb_release -a
CoreELEC (official): 9.2.2
CoreELEC:~ # udevadm info /sys/bus/sdio/devices/*
P: /devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
L: 0
E: DEVPATH=/devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=rtl8723bs
E: SDIO_CLASS=07
E: SDIO_ID=024C:B723
E: MODALIAS=sdio:c07v024CdB723
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=9284394
E: SYSTEMD_WANTS=rtkbt-firmware-aml.service
E: TAGS=:systemd:
CoreELEC:~ #
Hi there, i got some strange WIFI/BT behavior on my N5.
BT: does not auto connect to paired and trusted devices and even with manual pair command “bluetoothctl connect XX:XX:XX:X…” i get “Device not available”.
One workaround for this is to start “bluetoothctl scan on”. Then it shows some devices immediately but i need to wait around 10-30 Seconds to show my Audio-Bluetooth-Speaker. After that the connect command and audio is working.
WIFI: I can connect to my router but the connection is totally sluggish. SSH to the box times out most of the time. Ping to that wifi-interface works for some seconds then pauses for up to 20 seconds. To get a sluggish ssh-connection i have to go to the corelec-plugin and switch between the screens for bluetooth and wireless.
Maybe someone knows whats wrong with my box.
CoreELEC (official): 9.2.5
#udevadm info /sys/bus/sdio/devices/sdio*
P: /devices/platform/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
L: 0
E: DEVPATH=/devices/platform/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=ar6k_wlan
E: SDIO_CLASS=00
E: SDIO_ID=0271:0701
E: MODALIAS=sdio:c00v0271d0701
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=7992979
E: SYSTEMD_WANTS=qca9377-firmware-aml.service
E: TAGS=:systemd:
Firmware-Service:
#systemctl status qca9377-firmware-aml.service
Jan 09 16:44:33 MoWagenTV systemd[1]: Starting Attach /dev/ttyS1 to BlueZ stack using qca type...
Jan 09 16:44:34 MoWagenTV systemd[1]: Started Attach /dev/ttyS1 to BlueZ stack using qca type.
Jan 09 16:44:34 MoWagenTV hciattach[4275]: qca_soc_init: Rome Version (0x03020023)
Jan 09 16:44:38 MoWagenTV hciattach[4275]: read_vs_hci_event: Not an HCI-VS-Event! buf[0]: 255/lib/firmware/qca/tfbtnv11.bin File Open Fail
The file tfbtnv11.bin is nowhere, but i have this file:
/usr/lib/kernel-overlays/base/lib/firmware/qca/tfbtfw11.tlv
dmesg: http://ix.io/2LrF
Please let me know if u need more infos!
Thanks in advanced 
i have china brand tv box has fd6551 controller. i has bad software then flashed different device rom. before led display didnt work , I modifed dts file . then led panel working but leds show as mix up. how i can fix then. where i need look. FD655_Demo send clock info to /sys/class/fd655/panel
Are you using CoreELEC or a 3rd party Android ROM? If you’re using Android, I don’t know how you can fix it. It’s very likely that you can’t, because each firmware is designed specifically for a certain type of hardware and wiring schematic.
The OpenVFD driver in CE was specifically designed to be fully configurable to suit most hardware out there.
1 Like