Slightly off-topic, apologies — but this thread has the most owners of this box. Has anyone tried adb shell dpm set-device-owner (e.g. with OwnDroid) on the Google TV side? The stock firmware declares android.software.device_admin in the product partition, so it should work in theory. I’d like to lock the box down for my young child (hide YouTube/Play Store). Does it work after “Set up basic TV” (no Google account)? Thanks!
Hi all, reporting a WiFi regression on the Xiaomi 3rd Gen (S905X5M) with recent Piers nightlies, plus what I found so far.
Setup: Xiaomi Mi Box S 3rd Gen, s7d_s905x5m_xiaomi_3rd_gen.dtb, booting from USB. The WiFi module is the FN-Link K265B-UU (Amlogic W2 over USB, ID 1b8e:0641). I’ve been updating nightlies pretty often and WiFi was fine until now.
What happened: after updating to CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20261001 the box never connects to WiFi at all. My UniFi controller never even saw it associate, and it stayed like that for over an hour, so it’s not just slow to connect. For me it showed up as a Kodi bootloop because my library is on MariaDB:
Unable to open database: MyMusic84 [2002](Can't connect to server on '...' (101))
critical <general>: Failed to initialize databases
(101 is “network unreachable”). If you don’t use a MySQL library you’d probably just see no WiFi.
What I tested:
22.0-Piers_beta2: WiFi works- My own build of the 20261001 nightly (
coreelec-22at52ea384) with onlyw2-amlput back tocaabab74, the version beta2 ships: WiFi works
projects/Amlogic-ce/packages/linux-drivers/amlogic/w2-aml/package.mk
-PKG_VERSION="971d459af3009c984618ac01b17f3eb9a367fce0"
+PKG_VERSION="caabab742672bf9b9744cc7502958a981656a521"Does anyone else experience constant video playback crashing after pausing? While I’m streaming from a debrid service, it runs great without any stuttsring but then I pause it for 2 minutes to go to the toilet and after resuming it crashes within 30 seconds and I have to restart the movie.
It would be a perfect media player if it weren’t for that one annoying issue.
Update: found it, and it’s not really the driver.
The W2 driver creates three interfaces (wlan0, p2p0, ap0), and connman manages all of them because CoreELEC’s NetworkInterfaceBlacklist doesn’t exclude ap/p2p. On my box the WiFi network I saved during setup had ended up on ap0. connman keys saved networks by MAC (wifi_<mac>_<ssid>_managed_psk), and w2-aml v2.3.2 (commit de208ed) changed how the ap0 MAC is derived:
- vif2_mac[5] ^= BIT(0);
+ vif2_mac[0] ^= BIT(2);
So ap0 went from b2:...:45:93 to b6:...:45:92, connman had no saved network for it, and it just never connected. No errors anywhere, the driver loads fine and wlan0 is up.
To confirm it, I booted the “broken” v2.3.2 build again after copying my saved network to the wlan0 name (that MAC comes from efuse and doesn’t change between driver versions). It connected straight away on wlan0.
If you lost WiFi after a recent nightly, re-adding your network should fix it (or copy the folder in /storage/.cache/connman/ to the wlan0 MAC). As a proper fix, I think ap,p2p should be added to connman’s NetworkInterfaceBlacklist in packages/network/connman/package.mk, so client connections can’t land on those interfaces in the first place. Happy to open a PR for that if it sounds right.
Hello, new user here. Sorry if this is questioned before. Please, explain why a fast SSD USB flash drive is an advantage to boot Coreelec from, when the box has only one usb 2.0 port ? Why not use a simple cheap usb 2.0 flash drive ? Thank you in advance for the clarification !
An inexpensive flash drive might not even fully utilize the speed potential of a 2.0 port.