CoreELEC 21.0-Omega Amlogic-ng Discussion

This is the problem with the “users” only using a release. So some bugs are triggered lately and not within nighlty tests and the release needs a “hotfix”. We hope to have catched most problematic items and all users with 21.0-Omega should just update again with same release newly downloaded from Releases · CoreELEC/CoreELEC · GitHub.

I just flashed this release and am only getting HDR and no Dolby Vision. No options for Dolby Vision exist under System/CoreELEC.

https://wiki.coreelec.org/coreelec:ce_support

What Portisch said and please make sure you have dovi.ko as mentioned here: CE-NG Dolby Vision for G12 boxes (u22xj, am6+, firetv cube)

1 Like

Updated to April 9 Omega on my Odroid N2+, Hulu still freezing but Amazon, Disney+, Netflix and Youtube all work fine.

Anyone else having issues with Hulu and Omega?

Hello,

I want to install CoreELEC 21.0-Omega and I am looking for the right device-tree for my Odroid N2 4GB, but it seems that all device-trees at https://coreelec.org/dtb/ are down.

Where else can I get my device-tree?

Thanks for reply!

Greetings
Mark

Odroid N2 has dedicated img with dtb & BL already included, no need to modify anything.
Stable:

Nightly:

1 Like

@rho-bot

Thanks for your quick reply :+1:

Hello,

  • Khadas VIM3L device.

  • Freshly flashed original VIM3L firmware, from time since I bought it, working fine for my other vim3l device, cemmc’ed years ago, at some older 9.2 (?) version - VIM3L_Pie_V191011.7z

  • Vanilla uSD card with latest Omega 21-ng

  • Install to internal eMMC (ceemmc) works only in Dual Boot Mode, not Single Boot.


Issues found so far:

  • When wifi enabled (although not used, not even configured), with ondemand governor CPU freq is locked to the maximum all the time, due to dhd_dpc and irq/54-meson-am processes, taking a lot CPU. I can see That leads to expected +10/+15 °C on idle box.

CoreELEC:~/.config # cat /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
ondemand
CoreELEC:~/.config # cat /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq
1908000
CoreELEC:~/.config # cat /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq
1908000
CoreELEC:~/.config # cat /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq
1908000
CoreELEC:~/.config # cat /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq
1908000

image

try dual boot mode

1 Like

Hi, after direct update from CE 20 to CE 21 /to last nightly release from 13. april 2024 through .update folder/ is is not going internet connection after suspend. TV box have 1000 mbit issue, so i had script for suspend / resume/ power. Now i need restart after suspend for internet connection. With clear start of tv box is ok my autostart.sh script with same command: ethtool -s eth0 speed 100 duplex full

In CE 20 was both scripts (for resume from folder sleep.d and autostart ) OK. Something is wrong with script for resume from sleep.d in CE 21.
autostart.sh.zip (231 Bytes)
01-script-resume.power.zip (287 Bytes)

I have read all the above comments regarding the Omega upgrade channel showing “21 Omeg” etc. On my N2+ however I see two "21 Omeg) options but no 21 Omega option so cannot proceed with the upgrade. I there something that needs to be done to enable the 21 Omega option to be displayed?

Thanks to the Dev team for your ongoing work and dedication.

Update again manually by 21.0 release and its fixed:
https://wiki.coreelec.org/coreelec:updates#update_by_manual_place_a_update_file

I added also link to the exact firmware from Khadas to my previous post.

To be honest, I didnt remember ceemmc output, when it was sucessfull last time when I use the tool, but having only binary in ceemmc@sources.coreelec.org and KVIM3L officially supported (and no HW revisions to mess with testing, firmware available) I am relying totally on CE devs.

If there is anything I could try (dig deeper, get some more logs) just let me know…

Hello I just started looking into CoreElec and have one question and I searched but couldn’t find an answer. Does CoreElec do FEL properly, because the way Zidoo and Dune do it isn’t really true FEL and the chip used in the newer Dune Solo 8K is the non -J Armlogic version and way overpriced. My understanding , and correct me if I’m wrong, is in order to playback FEL like a UHD player the chip has to be able to decide 2 H265 streams/layers at once. The RPU method described below is a “work around” and doesn’t give the full benefits of FEL.

The media player supports direct playback of Dolby Vision profile 7 FEL double-track and double-layer files. This is the most advanced Dolby Vision format. The media player plays video in this format using both tracks/layers. The important Dolby Vision information from the second track/layer (Dolby Vision RPU metadata) is transmitted to TV together with video data from the first track/layer. The passed video data uses 10-bit color depth - the maximum color depth supported by OLED-panels in OLED TVs, i.e. this fully uses the capabilities of OLED TVs. Combined with the full use of Dolby Vision metadata this gives an excellent Dolby Vision picture on the TV screen.

Only these two devices can do FEL, Dolby Vision for Minix U22X-J (Max) and Ugoos AM6+ - Development / Development & Testing - CoreELEC Forums

1 Like

FEL is confirmed working on the Fire TV 2nd gen Cube as well, it uses the same s922 SOC.

Thanks for the quick response! I just wanted to confirm other stuff I read like the below on Reddit before buying one. 8 read the Amazon ones requires a custom bootloader so not an option for me.

It is now very mature and about a year ago, the CoreElec team noticed that DV FEL works on the Amlogic S922X-J SoC due it being the only SoC free of Dolby’s decoder restrictions that hobble FEL playback on other streaming boxes

In CoreELEC 21, the kodi-send script does not work for me, and therefore neither does the kodi-remote script.

When running the kodi-send script, the following error listing appears:

 # kodi-send -a ContextMenu
Traceback (most recent call last):
  File "/usr/bin/kodi-send", line 27, in <module>
    from kodi.xbmcclient import *
ModuleNotFoundError: No module named 'kodi'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/kodi-send", line 30, in <module>
    from xbmcclient import *
ModuleNotFoundError: No module named 'xbmcclient'

Dual Boot has no such issues

Filesystem                Size      Used Available Use% Mounted on
devtmpfs                911.5M      4.0K    911.5M   0% /dev
tmpfs                   367.0M     14.6M    352.4M   4% /run
/dev/CE_FLASH           511.0M    247.5M    263.4M  48% /flash
/dev/loop0              219.5M    219.5M         0 100% /
/dev/CE_STORAGE          10.5G    330.9M     10.2G   3% /storage
tmpfs                   917.4M         0    917.4M   0% /dev/shm
tmpfs                     4.0M         0      4.0M   0% /sys/fs/cgroup
tmpfs                   917.4M      4.0K    917.4M   0% /var
tmpfs                   917.4M      4.0K    917.4M   0% /tmp