CoreELEC 22.0-Piers_alpha3 Discussion

I have a GT-King 922x device and have Wi-Fi problems for a few weeks

@kengithub9 Strange

I also have a GT-King 922x but I have no Wi-Fi at all. I run nightly NO images and ssh login shows

CoreELEC (official): 22.0-Piers_nightly_20260321 (Amlogic-no.aarch64)

Machine model: Beelink
CoreELEC dt-id: g12b_s922x_beelink_gt_king_rev_a
Amlogic dt-id: g12b_w400_a
Linux version: 5.15.196 (docker@173d49f57196) #1 Sat Mar 21 01:29:10 IST 2026
Kodi compiled: 2026-03-21 01:41:57 +0100

I use g12b_s922x_beelink_gt_king.dtb (md5sum b4b90595d5fec302a5de21259f587401)

Does your system show deviating information (like maybe another rev)?

My system is the same as yours i think, where can i see these information?

1 Like

It looks like CoreELEC has these values in /proc/device-tree which is a symbolic link to /sys/firmware/devicetree/base

Here some values you can find via ssh to the box

I append the ‘ && echo’ since these files don’t have a trailing newline

Note that wifi/status says okay but WiFi is not available

GT-King:/sys/firmware/devicetree/base # cat amlogic-dt-id && echo
g12b_w400_a
GT-King:/sys/firmware/devicetree/base # cat compatible && echo
amlogic, g12b
GT-King:/sys/firmware/devicetree/base # cat coreelec-dt-id && echo
g12b_s922x_beelink_gt_king_rev_a
GT-King:/sys/firmware/devicetree/base # cat model && echo
Beelink
GT-King:/sys/firmware/devicetree/base # cat wifi/compatible && echo
amlogic, aml-wifi

GT-King:/sys/firmware/devicetree/base # cat wifi/name && echo
wifi
GT-King:/sys/firmware/devicetree/base # cat wifi/status && echo
okay
GT-King:/sys/firmware/devicetree/base # cat wifi/compatible && echo
amlogic, aml-wifi

while on topic bt-dev/status says okay but Bluetooth is not available

GT-King:/sys/firmware/devicetree/base # cat ./bt-dev/compatible && echo
amlogic, aml-bt
GT-King:/sys/firmware/devicetree/base # cat ./bt-dev/status && echo
okay
GT-King:/sys/firmware/devicetree/base # cat ./bt-dev/name && echo
bt-dev

/proc/device-tree is a read-only pseudo-filesystem directory that exposes the Device Tree as it was parsed and used by the running kernel.
It just shows the values in DTB.

1 Like

2 posts were merged into an existing topic: Amlogic-NO discussion

Hi there.

I also removed it for it to work properly but I’m not satisfied. When playing a video, the sound plays immediately but the screen is still black because the whole HDMI chain is a bit slow to react and properly sync/detect the signals. DuneHD Box R 4K → Denon AVR → OLED TV

This is especially noticeable when switching from Kodi interface (1080p SDR) to 4K HDR (no matter if plain HDR, DolbyVision, HDR10+ or HLG). Some videos have immediate content without “introduction/credits” screens (ie: “Previously on …” for TV shows) and some visual content is lost.

Up until CE-NO 20250624, any delay would work without issue. I suppose that the real problem is in Kodi with some kind of race condition somewhere.

3 posts were merged into an existing topic: Homatics Box R 4K Plus

Hi everyone. I have a Dune Pro Vision 4K box. I decided to upgrade from the 21-NE to the 22-NO to solve AV1 playback issues. The 22-NO hasn’t had any issues so far, except for one. I’m using a pseudo-sleep script (turning on the red LED instead of the blue one and disabling the video output). It works on both the NE and NO. However, in NO, it consumes 105% of CPU (waiting for the ‘value 408’ IR signal) and runs slightly hotter than when playing FHD video, even just with the main screen on. “CoreELEC:~ # top” also shows the R status instead of the S on the 21-NE, for kodi.bin process. In 21-NE it consumes about 6% of the CPU. Here’s the script itself; it works perfectly with the included R4 remote control:

#!/bin/sh
sleep 1
/usr/bin/kodi-send --host=127.0.0.1 --action=“PlayerControl(Stop)”
pkill -f “evtest /dev/input/by-path/platform-fe084040.meson-ir-event”
/usr/bin/systemctl stop eventlircd
kodi-send --action=“InhibitScreensaver(true)”
echo 0 > /sys/class/amhdmitx/amhdmitx0/phy
echo 0 > /sys/class/leds/sys_led/brightness
(/storage/.kodi/addons/virtual.system-tools/bin/evtest /dev/input/by-path/platform-fe084040.meson-ir-event &) | grep -m 1 ‘value 408’
echo 1 > /sys/class/leds/sys_led/brightness
echo 1 > /sys/class/amhdmitx/amhdmitx0/phy
kodi-send --action=“InhibitScreensaver(false)”
/usr/bin/systemctl start eventlircd

How to reduce CPU consumption?

Sorry for text. Unable to paste media here for some reason, maybe because I’ve just registered.

Tasks: 184 total, 2 running, 182 sleep, 0 d-sleep, 0 stopped, 0 zombie
%Cpu(s): 24.6 us,  1.8 sy,  0.4 ni, 72.4 id,  0.0 wa,  0.7 hi,  0.1 si,  0.0 st
MiB Mem :   3661.1 total,   1607.1 free,    907.6 used,   1234.3 buff/cache
MiB Swap:      0.0 total,      0.0 free,      0.0 used.   2753.5 avail Mem

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
1359 root      20   0 3206640 425064 115096 R 104.5  11.3  34:21.35 kodi.bin
1470 root      20   0 9666436 114244  24856 S   0.7   3.0   0:41.80 python
2414 root      20   0    7188   4040   1896 R   0.7   0.1   0:00.43 top
15 root      20   0       0      0      0 I   0.3   0.0   0:00.41 rcu_preempt
556 root      20   0   86532    276    228 S   0.3   0.0   0:07.55 OpenVFDService
663 root      -2   0       0      0      0 S   0.3   0.0   0:08.00 ksdioirqd/mmc2

Maybe kodi goes crazy because you stopped eventlircd and doesn’t have input anymore?

Try suspend and resume kodi process? Something like that

kodi-send --action="PlayerControl(Stop)"
kodi-send --action="InhibitScreensaver(true)"
pkill -STOP kodi.bin
....
pkill -CONT kodi.bin
kodi-send --action="InhibitScreensaver(false)"
1 Like

Thanks for the reply. I’m stopping eventlircd to listen for events on platform-fe084040.meson-ir-event, otherwise it’s blocked. I’ve previously tried pkill -STOP and pkill -CONT, but stopping/starting eventlircd prevents Kodi from waking up, even with a separate command via SSH, Kodi stays freezes in forever. It seems there’s a glitch that can only be fixed with a restart.

UPD! This was the case in 21-NE. No matter how much I tried, Kodi always crashed after a few cycles. But in 22-NO, it seems that pkill -STOP, pkill -CONT combined with stopping and starting eventlircd no longer cause a Kodi crash! Thank you again.

2 Likes

I was watching a two-hour movie with a video bitrate of 78.6 Mbps and about once every 20-30 minutes there was buffering for about 5 seconds.

CoreELEC:~ # smbclient “``//192.168.1.1/Keenetic`` SSD” -N -c “get Hamnet.2025.BDRemux.2160p.HDR-DV.mkv -” | dd of=/dev/null bs=1M count=50000
0+50000 records in
0+50000 records out
3276800000 bytes (3.1GB) copied, 263.403484 seconds, 11.9MB/s

It’s WiFi, but it’s stable; there were no other devices connected during playback. I have a Dune HD Pro Vision 4K (S905X4-J), and the read speed is around 20 MB/s in DuneOS. I tried buffer sizes from 128 to 512 MB, and the problem persisted each time. It’s very strange, considering even such a low speed (~11.9 MB/s) should be sufficient for this movie, especially with such a huge buffer. Why is the Coreelec’s speed so much lower?

I changed the chunk size to 1 MB for SMB, otherwise there would be a slideshow. The highest temperature I saw during playback was 44 degrees.

I regret to tell you that your test is invalid.

Does not take into account overhead of WiFi and CPU usage.

Does not take into account variable bitrates of video, even if the average video bitrate is 78.6 that doesn’t account for video bitrate spikes.

Doesn’t account for 20-30 minutes of video playback or the ram usage associated with it.

I can tell you though that 95Mbps is not enough for smooth 4K playback even if that’s what you actually got during the entire playback.

I can also tell you 95Mbps is rather slow even for WiFi.

Yes, but why does DuneOS show 160+ Mbps for the same file? The physical position of the box didn’t change, nor did anything else. The maximum RAM consumption during playback was about 55% of 4GB.

I was addressing …

For this part …

I have no information to base on such as Dune vs CE : Driver, Kernel version, Power config

I’ll defer to team CE to answer why is it slower than dune os.

We are not the provider of the WiFi driver source code. So please ask your vendor or better as always use LAN. LAN is LAN, working. WiFi is WiFi, maybe working,. maybe not…

1 Like

When ever I get issues like that I always verify by using an ethernet cable to my router to rule out wifi etc before fault finding.

Baz

2 Likes

Love the Easter Logo, Happy Easter :smiley:

2 Likes

A post was split to a new topic: Ugoos SK1 (S928X) - Hard lockup when using USB Microphone (G20S Pro)

3 posts were split to a new topic: Aeon nox silvo skin

On my X96 X10 Pro (S928X-J), I receive the following message after startup:

I installed the latest firmware (20240803-1308) from the manufacturer’s website, x96mini.com, but the kernel is only version 5.4.210. Since I don’t own a Dolby Vision-compatible TV, this isn’t currently a problem for me. Is there a way to disable this message when the receiver starts up?
And: Does this mean that Dolby Vision playback would be possible with NE 21.3? However, I have another problem with NE: Many AV1 videos cannot be hardware-decoded. They stutter and exhibit numerous decoding errors, which appear as vertical lines. Software decoding works, with increased CPU usage, at least up to 1080p. Hardware decoding works for the affected files with NO. However, these progressive videos are incorrectly displayed as interlaced in the player process info. The aspect ratio is listed as 0.00 for all AV1 videos, but the aspect ratio displayed on the TV is correct. With software decoding, both pieces of information are displayed correctly in the player process info.
I also noticed that the DTB for X88 King is missing from the device trees for the S922X. Is this device no longer supported?