Device is now visible but the driver must be fixed.
Tomorrow…
do you need me to extract any information from Android?
I see no way to get this old WiFi chip working.
It’s the 0x4334 chip ID. I think it’s the AP6334 chip.
The driver isn’t the problem, but the firmware is.
Newest firmware I can find is from 2019 but this still does not supply some features need for the new driver.
The old driver is just not compatible at all anymore with new kernel.
So youre only chance is to ask the vendor for a firmware compatible with at least kernel 5.15.
Okay, thanks for trying.
I just try last attemp - and will cleanup when done.
Okay, let me know when I can disable tmate, please.
Will the driver be updated to version 2019 for CE NE?
It’s already disabled. The Khadas driver does also not work. CE-NE, CE-21 is EOL.
2 Likes
A post was merged into an existing topic: CoreELEC 21.3-Omega Amlogic-ne Discussion
My wifi woes returned again in my HK1 RBOX
logs
Anybody got a cheap usb-wifi dongle to recommend? I’m way to far from my router to even try ethernet 
https://tinyurl.com/53twvntpIve used a couple that look like this one that work OK.
1 Like
Thanks for the tip. I got mine off of Walmart so it’ll be returnable if it doesn’t work 
Just to circle back. This wifi dongle works with the HK RBOX/Vontar box.
There’s a few clones that you can get shipped to you a Lil quicker but yeah. 10 bucks and you dont have to deal with the dodgy wifi chip these boxes have…
1 Like
I discovered a bug with my HK1 RBOx
The integrated wlan card got a random MAC address with nightlies
Example :
Today : 88:00:33:77:5b:34
Yesterday : 88:00:33:77:dc:47
CoreELEC-Chambre:~ # dmesg | paste
https://paste.coreelec.org/PSRm.bin
CoreELEC-Chambre:~ # udevadm info /sys/bus/sdio/devices/* | paste
https://paste.coreelec.org/PSRB.txt
CoreELEC-Chambre:~ # lsusb | paste
https://paste.coreelec.org/PSRM.txt
CoreELEC-Chambre:~ # udevadm info /sys/bus/pci/devices/* | paste
Unknown device “/sys/bus/pci/devices/*”: No such device
451 Unavailable For Legal Reasons
CoreELEC-Chambre:~ # lspci | paste
451 Unavailable For Legal Reasons
Thanks
Ask your vendor to fix it he WiFi driver?
Use CE supported hardware?
So, why did you accept to add network support for HK1 
It’s supported : the dtb file s7d_s905x5m_4g_1gbit.dtb works with S905X5M(S905A)
And of course, I’ll ask a vendor from the Aliexpress Marketplace to develop a Linux Driver for Coreelec right 
Also I saw in an other topic the same problem for an other device
1 Like
You use a complete other driver than a 0x4339: rtw_8822bu: GitHub - lwfinger/rtw88: A backport of the Realtek Wifi 5 drivers from the wireless-next repo.
It’s not for coreelec, it’s for all platforms. It’s your fault getting the cheapest device and think others fix the issues for you.
This is from years back and not releated to Wifi at all…
1 Like
What is your point exactly?
You are using generic DTB for SoC. Driver support varies in such cases because no one has device to work on it.
A post was merged into an existing topic: Ugoos AM9 - SoC S6 S905X5
An update on my Ugoos AM9 Bluetooth journey.
I bit the bullet and Purchased a TP-Link UB5A Bluetooth USB adapter, and following the information provided here
I now have both my UR02 controller and my Harmony Hub connected. I am pleased to report that everything works well.
The Ugoos turns off and on from my harmony companion controller.
I removed power from the box for 15min, re-applied power and my Bluetooth connections remained unaffected.
My Ugoos AM9 is updated to the latest firmware 2.0.6, with the latest CE 22 nightly build 14/03/2026
Doing a happy dance now.
@YadaYada Thank you
2 Likes
Probably a silly ask.
Since the general consensus is about the Ugoos internal bluetooth being problematic.
Could the Bluetooth menu in the Coreelec utility be modified in some way to add a check box option to choose which Bluetooth receiver to use when adding an external connection, maybe even an option to disable the internal receiver?
2 Likes