It uses the kernel driver for your module. Maybe 4.9 driver is not up to date and this is the reason. What mean it might be never get solved. LE uses mainline with a new kernel but hardware decoder is very limited.
I think you will get better results and less trouble just update to a S905X3 device.
Thanks for the response and the box is pretty old and I might consider changing that in the future. I have the possibility to use wired network while I am limited at 100Mbit or I can go back and use the old kernel and nfs3. I will have a play around and see before swap SD again.
I know this is not the best thread to ask, but any recommendations on an inexpensive s905x3 box where all the hardware is supported by the new kernel? I appreciate the help here.
I did not see this topic when I searched before posting, but I am seeing the same thing as @elena421 . Wifi is fine, but bluetooth is no good. X96_Max_Plus_A100 `udevadm info /sys/bus/sdio/devices/sdio*
P: /devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
L: 0
E: DEVPATH=/devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=bcmsdh_sdmmc
E: SDIO_CLASS=00
E: SDIO_ID=02D0:4354
E: MODALIAS=sdio:c00v02D0d4354
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=7655891
E: ID_VENDOR_FROM_DATABASE=Broadcom Corp.
E: ID_MODEL_FROM_DATABASE=BCM4354 WLAN card
E: ID_SDIO_CLASS_FROM_DATABASE=Non-standard SDIO interface
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
P: /devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:2
L: 0
E: DEVPATH=/devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:2
E: DRIVER=bcmsdh_sdmmc
E: SDIO_CLASS=00
E: SDIO_ID=02D0:4354
E: MODALIAS=sdio:c00v02D0d4354
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=7667233
E: ID_VENDOR_FROM_DATABASE=Broadcom Corp.
E: ID_MODEL_FROM_DATABASE=BCM4354 WLAN card
E: ID_SDIO_CLASS_FROM_DATABASE=Non-standard SDIO interface
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
P: /devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:3
L: 0
E: DEVPATH=/devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:3
E: DRIVER=bcmsdh_sdmmc
E: SDIO_CLASS=02
E: SDIO_ID=02D0:4354
E: MODALIAS=sdio:c02v02D0d4354
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=7654815
E: ID_VENDOR_FROM_DATABASE=Broadcom Corp.
E: ID_MODEL_FROM_DATABASE=BCM4354 WLAN card
E: ID_SDIO_CLASS_FROM_DATABASE=Bluetooth Type-A standard interface
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
EDIT: SOLVED!
I can now report that bluetooth is working great on here. Here is what I did:
Copied the 4354 files from here My Files to /storage/.config/firmware/brcm
rebooted 
Let me know if I can supply any log files that might help
`
I have this box, X96_Max_Plus_A100, using Amlogic-ng.arm-20-Nexus-nightly_20211216 with the sm1_s905x3_4g.dtb
Bluetooth works well with the stock Android 9, but does not really work with Coreelec. Range is about 1 foot and keeps disconnecting, etc.
I am able to connect to the Android system with adb and remount as root, so I have some questions about the way Android loads bluetooth and whether i may be able to use the information to get similar bluetooth performance in Corelec?
First I looked at /vendor/etc/bluetooth
franklin:/ # ls -a /vendor/etc/bluetooth
. BCM43430A0.hcd BCM43751.hcd bcm4354a1.hcd
.. BCM43430B0.hcd auto_pairing.conf bcm43569a2.hcd
4343.hcd BCM4345C0.hcd bcm43241b4.hcd blacklist.conf
BCM20702.hcd BCM4345C5.hcd bcm43341b0.hcd bt_vendor.conf
BCM20703A2.hcd BCM4354.hcd bcm43342.hcd
BCM2076.hcd BCM4359C0.hcd bcm4335c0.hcd
BCM4330.hcd BCM4362A2.hcd bcm4350.hcd
franklin:/ # cat /vendor/etc/bluetooth/bt_vendor.conf
# UART device port where Bluetooth controller is attached
UartPort = /dev/ttyS1
# Firmware patch file location
FwPatchFilePath = /etc/bluetooth/
Then I looked at those patch files
franklin:/ # ls /etc/bluetooth/
bt_did.conf bt_stack.conf
franklin:/ # cat /etc/bluetooth/bt_did.conf
# Device ID (DID) configuration
[DID1]
# Primary Record - true or false (default)
# There can be only one primary record
primaryRecord = true
# Vendor ID '0xFFFF' indicates no Device ID Service Record is present in the device
# 0x000F = Broadcom Corporation (default)
#vendorId = 0x000F
# Vendor ID Source
# 0x0001 = Bluetooth SIG assigned Device ID Vendor ID value (default)
# 0x0002 = USB Implementer's Forum assigned Device ID Vendor ID value
#vendorIdSource = 0x0001
# Product ID & Product Version
# Per spec DID v1.3 0xJJMN for version is interpreted as JJ.M.N
# JJ: major version number, M: minor version number, N: sub-minor version number
# For example: 1200, v14.3.6
productId = 0x1200
version = 0x1436
# Optional attributes
#clientExecutableURL =
#serviceDescription =
#documentationURL =
#=================================================================================================#
# Device ID (DID) configuration
[DID2]
# Primary Record - true or false (default)
# There can be only one primary record
#primaryRecord = false
# Vendor ID '0xFFFF' indicates no Device ID Service Record is present in the device
# 0x000F = Broadcom Corporation (default)
#vendorId = 0x000F
# Vendor ID Source
# 0x0001 = Bluetooth SIG assigned Device ID Vendor ID value (default)
# 0x0002 = USB Implementer's Forum assigned Device ID Vendor ID value
#vendorIdSource = 0x0001
# Product ID & Product Version
# Per spec DID v1.3 0xJJMN for version is interpreted as JJ.M.N
# JJ: major version number, M: minor version number, N: sub-minor version number
# Default: 0x0000, v00.0.0
#productId = 0x0000
#version = 0x0000
# Optional attributes
#clientExecutableURL =
#serviceDescription =
#documentationURL =
#=================================================================================================#
# Device ID (DID) configuration
[DID3]
# Primary Record - true or false (default)
# There can be only one primary record
#primaryRecord = false
# Vendor ID '0xFFFF' indicates no Device ID Service Record is present in the device
# 0x000F = Broadcom Corporation (default)
#vendorId = 0x000F
# Vendor ID Source
# 0x0001 = Bluetooth SIG assigned Device ID Vendor ID value (default)
# 0x0002 = USB Implementer's Forum assigned Device ID Vendor ID value
#vendorIdSource = 0x0001
# Product ID & Product Version
# Per spec DID v1.3 0xJJMN for version is interpreted as JJ.M.N
# JJ: major version number, M: minor version number, N: sub-minor version number
# Default: 0x0000, v00.0.0
#productId = 0x0000
#version = 0x0000
# Optional attributes
#clientExecutableURL =
#serviceDescription =
#documentationURL =
franklin:/ # ls /etc/bluetooth/
bt_did.conf bt_stack.conf
franklin:/ # cat /etc/bluetooth/bt_stack.conf
# Enable trace level reconfiguration function
# Must be present before any TRC_ trace level settings
TraceConf=true
# Trace level configuration
# BT_TRACE_LEVEL_NONE 0 ( No trace messages to be generated )
# BT_TRACE_LEVEL_ERROR 1 ( Error condition trace messages )
# BT_TRACE_LEVEL_WARNING 2 ( Warning condition trace messages )
# BT_TRACE_LEVEL_API 3 ( API traces )
# BT_TRACE_LEVEL_EVENT 4 ( Debug messages for events )
# BT_TRACE_LEVEL_DEBUG 5 ( Full debug messages )
# BT_TRACE_LEVEL_VERBOSE 6 ( Verbose messages ) - Currently supported for TRC_BTAPP only.
TRC_BTM=2
TRC_HCI=2
TRC_L2CAP=2
TRC_RFCOMM=2
TRC_OBEX=2
TRC_AVCT=2
TRC_AVDT=2
TRC_AVRC=2
TRC_AVDT_SCB=2
TRC_AVDT_CCB=2
TRC_A2D=2
TRC_SDP=2
TRC_SMP=2
TRC_BTAPP=2
TRC_BTIF=2
TRC_BNEP=2
TRC_PAN=2
TRC_HID_HOST=2
TRC_HID_DEV=2
# This is Log configuration for new C++ code using LOG() macros.
# See libchrome/base/logging.h for description on how to configure your logs.
# sample configuration:
#LoggingV=--v=0
#LoggingVModule=--vmodule=*/btm/*=1,btm_ble_multi*=2,btif_*=1
# PTS testing helpers
# Secure connections only mode.
# PTS_SecurePairOnly=true
# Disable LE Connection updates
#PTS_DisableConnUpdates=true
# Disable BR/EDR discovery after LE pairing to avoid cross key derivation errors
#PTS_DisableSDPOnLEPair=true
# SMP Pair options (formatted as hex bytes) auth, io, ikey, rkey, ksize
#PTS_SmpOptions=0xD,0x4,0xf,0xf,0x10
# PTS AVRCP Test mode
#PTS_AvrcpTest=true
# SMP Certification Failure Cases
# Set any of the following SMP error values (from smp_api_types.h)
# to induce pairing failues for various PTS SMP test cases.
# Setting PTS_SmpFailureCase to 0 means normal operation.
# Failure modes:
#
# SMP_PASSKEY_ENTRY_FAIL = 1
# SMP_PAIR_AUTH_FAIL = 3
# SMP_CONFIRM_VALUE_ERR = 4
# SMP_PAIR_NOT_SUPPORT = 5
# SMP_PAIR_FAIL_UNKNOWN = 8
# SMP_REPEATED_ATTEMPTS = 9
# SMP_NUMERIC_COMPAR_FAIL = 12
#PTS_SmpFailureCase=0
So I am wondering if there is a way I can use these files bt_did.conf bt_stack.conf to try to improve BT performance in my Corelec installation?
Here is what lsmod shows in Android 9 franklin:/ # lsmod Module Size Used by dhd 1683456 0 galcore 344064 0 aml_hardware_dmx 139264 0 amvdec_mavs 40960 0 vpu 45056 0 encoder 49152 0 amvdec_avs2 192512 0 amvdec_vp9 110592 0 amvdec_vc1 57344 0 amvdec_real 40960 0 amvdec_mmpeg4 40960 0 amvdec_mpeg4 57344 0 amvdec_mmpeg12 40960 0 amvdec_mpeg12 102400 0 amvdec_mmjpeg 28672 0 amvdec_mjpeg 40960 0 amvdec_h265 131072 0 amvdec_h264mvc 53248 0 amvdec_mh264 151552 0 amvdec_h264 135168 0 amvdec_avs 65536 0 stream_input 163840 12 aml_hardware_dmx,amvdec_mavs,amvdec_avs2,amvdec_vp9,amvdec_real,amvdec_mmpeg12,amvdec_mpeg12,amvdec_h265,amvdec_h264mvc,amvdec_mh264,amvdec_h264,amvdec_avs decoder_common 159744 18 amvdec_mavs,encoder,amvdec_avs2,amvdec_vp9,amvdec_vc1,amvdec_real,amvdec_mmpeg4,amvdec_mpeg4,amvdec_mmpeg12,amvdec_mpeg12,amvdec_mmjpeg,amvdec_mjpeg,amvdec_h265,amvdec_h264mvc,amvdec_mh264,amvdec_h264,amvdec_avs,stream_input firmware 24576 19 amvdec_mavs,encoder,amvdec_avs2,amvdec_vp9,amvdec_vc1,amvdec_real,amvdec_mmpeg4,amvdec_mpeg4,amvdec_mmpeg12,amvdec_mpeg12,amvdec_mmjpeg,amvdec_mjpeg,amvdec_h265,amvdec_h264mvc,amvdec_mh264,amvdec_h264,amvdec_avs,stream_input,decoder_common media_clock 36864 14 aml_hardware_dmx,amvdec_mavs,vpu,encoder,amvdec_avs2,amvdec_vp9,amvdec_mpeg12,amvdec_h265,amvdec_mh264,amvdec_h264,amvdec_avs,stream_input,decoder_common,firmware tb_detect 20480 0 atbm8881_fe_32 118784 0 mali_kbase 471040 36 EDIT: SOLVED!
I see it is moved here, thanks. Sorry for the cross post. I can now report that bluetooth is working great on here. Here is what I did:
Let me know if I can supply any log files that might help
I opened the box, and see “AM7526 VT1821N 98BA” on the wifi chip
# udevadm info /sys/bus/sdio/devices/sdio*
P: /devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
L: 0
E: DEVPATH=/devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=bcmsdh_sdmmc
E: SDIO_CLASS=00
E: SDIO_ID=02D0:4354
E: MODALIAS=sdio:c00v02D0d4354
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=7655891
E: ID_VENDOR_FROM_DATABASE=Broadcom Corp.
E: ID_MODEL_FROM_DATABASE=BCM4354 WLAN card
E: ID_SDIO_CLASS_FROM_DATABASE=Non-standard SDIO interface
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
P: /devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:2
L: 0
E: DEVPATH=/devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:2
E: DRIVER=bcmsdh_sdmmc
E: SDIO_CLASS=00
E: SDIO_ID=02D0:4354
E: MODALIAS=sdio:c00v02D0d4354
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=7667233
E: ID_VENDOR_FROM_DATABASE=Broadcom Corp.
E: ID_MODEL_FROM_DATABASE=BCM4354 WLAN card
E: ID_SDIO_CLASS_FROM_DATABASE=Non-standard SDIO interface
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
P: /devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:3
L: 0
E: DEVPATH=/devices/platform/ffe03000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:3
E: DRIVER=bcmsdh_sdmmc
E: SDIO_CLASS=02
E: SDIO_ID=02D0:4354
E: MODALIAS=sdio:c02v02D0d4354
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=7654815
E: ID_VENDOR_FROM_DATABASE=Broadcom Corp.
E: ID_MODEL_FROM_DATABASE=BCM4354 WLAN card
E: ID_SDIO_CLASS_FROM_DATABASE=Bluetooth Type-A standard interface
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
Hey guys.
I´m experiencing something weird with my android box (amlogic S905X2 - https://amzn.to/3FQPKD9).
Since when I start using Coreelec my wifi and bluetooth never worked. Somedays ago I had to change my SD card used for CE, and I´ve done all installation process again, using the same dtb.img and all others steps just like I always did and for my surprise the Wifi and Bluetooth were working perfectly. I could use my Wifi 5g (my ethernet port is just fast) and the Bluetooth remote that came with the box and everything was working fine.
But after the reboot, they are all gone again. Trying reinstall and rebooting a dozen times, I could get it working more 2 or 3 times, and it works untill I turn off the box.
I´ve saved some logs:
Without wifi or BT - http://ix.io/3KEc
Working wifi and bt after fresh install - http://ix.io/3KT5
Working after restart kodi (not rebooting) - http://ix.io/3KT6
When I used my box with android, they all works great. So it´s not a hardware problem.
Any ideia of what´s going on?
Cheers!
Original post moved to this thread.
I have the same issue with the A95X-B7N which also uses the QCA9377. I started a thread, but wasn’t able to get much momentum.
No idea what wifi chip is assembled. When anyone want to have support please provide , like written in first post, some required info like:
udevadm info /sys/bus/sdio/devices/* | paste
I got this: Unknown device “/sys/bus/sdio/devices/*”: No such device
When I tried the BT and Wifi were not working. I’ll try again if I can get them working again
I could get the BT and WIFI working and I got this using “udevadm info /sys/bus/sdio/devices/* | paste”
http://ix.io/3L6u
P: /devices/platform/ffe05000.sd2/mmc_host/sdio/sdio:0001/sdio:0001:1
L: 0
E: DEVPATH=/devices/platform/ffe05000.sd2/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=rtl88x2bs
E: SDIO_CLASS=07
E: SDIO_ID=024C:B822
E: MODALIAS=sdio:c07v024CdB822
E: SUBSYSTEM=sdio
E: USEC_INITIALIZED=7021426
E: ID_SDIO_CLASS_FROM_DATABASE=WLAN interface
E: SYSTEMD_WANTS=rtkbt-firmware-aml.service
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
Please also run dmesg|paste
After rebooting no bt or wifi working, as expected
for the command “udevadm info /sys/bus/sdio/devices/* | paste” I got:
Unknown device “/sys/bus/sdio/devices/*”: No such device
for the command “dmesg|paste” I got:
http://ix.io/3L8j
I used the generic CE Matrix -ng firmware as recommended for this S905X3 Magicsee N5 Max 4GB box and used the suggested DTB sm1_s905x3_4g After going to Arthur L’s Github site I got a working VFD Conf file (thanks a lot Arthur) for the front panel display and found using the X96+ remote.conf file this worked well for the IR remote.
However I notice there is no WiFi available at all. Not sure about Bluetooth as forgot to test that and the box is now with a friend I set it up for who does not use BT anyway but he would like WiFi as a fall back though he normally uses Ethernet cable.
Can anyone help here ??
6 posts were merged into an existing topic: What box to buy for CoreELEC in 2022? (no premium streaming apps needed)
My tvbox H96Max plus5 wifi can not work.
Some infomaiton
device H96Max plus5 2G/16Gb
android :slimbox sbx_x96max_plus_5_atv_14_9
Coreelec:CoreELEC-Amlogic-ng.arm-19.4-Matrix_rc3-Generic.img
dtb:sm1_s905x3_2g.dtb
please help me to fix the wifi issue
Please read the first post of this topic and provide the information asked.
About | FAQ | Terms of Service | Privacy Policy | Legal Notice
