CoreELEC 21.0-Omega Amlogic-ng Discussion

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

Looks like only for you: it works here.
Run this commands and post url.

which kodi-send >/tmp/paste.txt
env >>/tmp/paste.txt
set >>/tmp/paste.txt
paste /tmp/paste.txt

Here it is…
https://paste.coreelec.org/Q0FaTz

@JiRo: try this

LD_LIBRARY_PATH= kodi-send -a ContextMenu
LD_LIBRARY_PATH= && kodi-send -a ContextMenu

Still the same error…

What about

PATH=/usr/bin kodi-send -a ContextMenu

The problem is that you are using entware which interfere with Python. I forgot what needs to be done to work.

Sure, I hadn’t thought of that, but it could…
Thanks for the clarification.
I have Entware there for some Tvheadend related apps. I’m moving Tvheadend to a dedicated machine right now, I’ll clean it up!
Thank you once again.
EDIT Entware uninstall and kodi-send works!

@vpeter can these two be change somehow ?
HISTFILESIZE=200
HISTSIZE=500

I would like to have longer history kept :wink: ?

Try with this workaround in file /storage/.profile.
You need to reboot twice to get the effect.

case $- in
  *i*)
    func_exit() {
      history -w /storage/.history-saved
      rm /storage/.history
      sync
    }

    trap func_exit EXIT SIGHUP

    export HISTFILE=/storage/.history
    export HISTFILESIZE=10000
    export HISTSIZE=10000
    export HISTCONTROL=ignoredups

    history -c
    history -r /storage/.history-saved
    ;;
  *)
    ;;
esac
3 Likes

This does work indeed! :blush:
Happy days! Thank you Peter! :heart:

1 Like

The update does not work on my Minix NEO U22-XJ Max → ERROR: CoreELEC-Amlogic-ng.arm-21.0-Omega.tar is not compatible with Amlogic-ng-dv.arm hardware - update canceled. What can I do?

Although not recommended (create a backup and store it in a safe place) you can ssh to the device and run this command touch /storage/.update/.nocompat this will create an empty file named nocompat that will.let you use the .tar to update. Don’t forget, obviously, to also put the update .tar in the folder.

Still having an issue with Omega and Hulu on my N2+. Is there any way the CE repository version of InputSteam Adaptive can be updated to the latest available, 21.4.5? I am working with the Hulu and IA addon developers and they requested any additional troubleshooting be done with the latest IA.

Make sure you install the right version of 21. I had that problem initially but ended up with it being the Omega 21 Alpha rather than stable.

Looks like it was not build when it should. Anyway, here is local build 1.15 MB file on MEGA