Just got my unit. Everything runs smooth on the base android firmware (running nightly 20260418), except for one critical issue: using Wi-Fi causes a hard lockup and the box reboots.
Since standard persistent logs couldn’t catch it, I did a live capture of /proc/kmsg right up until the crash.
I have just purchased one of these and updated to latest firmware UKG3.250826.001.V816.0.7.0.UZFAABX.
Enabled developer options
Enabled usb debugging
Then adb reboot update
worked first time.
Using current nightly build.
I get better wifi results coming from tox3 (100mbits/sec), xiaomi (250mbits/sec) same as my intel nuc (wifi6).
The one thing that concerned me was running coreelec from a usb 2.0 port but its not really a issue, Coming from a tox3 that was using coreelec installed on emmc.
I am using a ugoos ur-01 remote and created a configuration to shutdown kodi (so tv and avr will shutdown) with the power button, As there is no ir reciever, Thanks to this forum.
The only major issue I have is sometimes wifi drops, even from bootup sometimes does not connect.
Overall I am impressed with this device and yes I play 4k remuxes, and only have wifi available not wired so this box suits my needs and at a good price.
The 2g ram is also not an issue coreelec only uses about 75% of this.
Is support for this device going to continue?, Shame if not as your so close.
Hi,
I have a TP-Link UE300 USB-LAN adapter, and after connecting it, I only see available Wi-Fi networks in the settings, not a wired connection. Here’s the output from the lsusb command:
2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153]
Is this adapter supported by CoreElec? I have the latest nightly version installed.
After connecting the adapter, only this is displayed in dmesg
[ 96.764808] usb 3-1.1: new high-speed USB device number 5 using xhci-hcd-meson
[ 96.873684] usb 3-1.1: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00
[ 96.873698] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 96.873702] usb 3-1.1: Product: USB 10/100/1000 LAN
[96.873704] usb 3-1.1: Manufacturer: TP-LINK
[96.873707] usb 3-1.1: Serial Number: 000001000000
I don’t know if there are any other logs I could check.
EDIT: enabled the r8152 module, check tomorrows nightly to see if it works for you.
Ok I see the problem, CE-NO only has the r8153_ecm module enabled which has a limited lists of devices that it binds to. I’ll check into enabling the r8152 as well.
On the Xiaomi there is no IR, So wake it up is impossible.
Extract this pack to you CoreElec install.
Using this will shutdown Kodi, But keeps Bluetooth connected.
Setup CEC to shutdown TV & AVR.
Here I am using a Ugoos UR-01 remote, If using different you need to edit the .hwdb file.
The only thing that would stop this working is the EV device number set, I only have a USB stick in both my Xiaomi’s and the EV device number is the same on both.
If you are using a USB hub along with other devices then the EV device number will defer from one set.
Also I have added LED control, Turn off LED in CoreElec settings for this to work otherwise be permanently on.
Along with this script when Kodi is running the LED is on, When you press the Power button on your remote Kodi will shutdown then CEC will shutdown your TV, Then the LED will turn off.
The LED is also useful if Kodi crashes due to us having to use nightly builds.
This does not fully shutdown the Xiaomi but it only draw about 1.8watts anyway. The Vero V works in similar way but via internal USB.
Would you be able to make something like this but without using remote? Using cec signal from tv/avr when it boots to wake up kodi and when it goes to sleep shut down kodi?