post logs coreelec:ce_support [CoreELEC Wiki]
https://paste.coreelec.org/EhrlichTalented
It’s connected to a denon x3400h and uses the same HDMI cable as the Nvidia Shield used.
On the CE-NO nightly build I can play a H.264 movie in 1080p. But I’m running CE-NG nightly now and no signal, whatever I play.
Sound works perfectly
Just as a test, what happens for your picture when you connect the box straight to your TV? You didn’t share which one that is.
BTW, that 5310 is a very old build, you don’t want to go back to that one 
It can all work just nicely using ATV V14 on your device and CE as dualboot option.
When I connect it to the TV it works. I’ve got a Philips 65OLED809. How is that possible?! I’ve never had this problem. Thing is I can’t make it work like that because of the audio.
My previous setup was a Nvidia Shield, but it became so slow that I wanted to try this one.
Update: I’ve also switched out the HDMI cable to the receiver, no success.
So your Philips doesn’t support all audio codecs when using eARC and passthrough?
Well, it is clear now that it can work, so now it’s up to you to find what is blocking it when using passthrough using your receiver. It looks to me, some setting isn’t correct for now. Even if it worked before with your Shield, some “smart” devices can detect that another device is connected (not Shield), and settings are changed for that connection. So go through all of them, on your receiver, but also on your TV.
I posted the logs to Gemini Pro and said that I fixed a handschake by switching HDMI cables and that I have to turn off adjust display refresh rate. That actually works. In the ideal situation I would have to turn that on for a smoother expierience, but I have no clue how to fix that. I tried whitelisting but with no succes.
So it is kind of working now.
Edit: To answer your question about the codecs with a Philips tv, that’s correct. Otherwise I could just use Kodi on the tv’s ATV.
Use CE-NO. It gives best and last support of AVR/EDID.
I started with CE-NO, that gave the same results, no signal. Then I switched to CE-NG because I read that Dovi could be activated there by putting the dovi.ko file in storage folder, somehow I can’t get it to show up in the options. Or I must have missed some new piece of information.
So after reading some info on Corelec wiki, CE-NO is based on Amlogic Vendor Kernel 5.15.
And there’s no dovi.ko for this Kernel version, correct?
So Kodi 22.0, which is in alpha stage at the moment, will not support DV P7 FEL from MKV because of lack of dovi.ko, is this correct?
No, you’re wrong. There’s dovi.ko for 5.15, it works well. What’s missing from 4.9 onwards is FEL support because Dolby laboratories decided to just remove it.
I can confirm that P7 FEL works with CoreELEC-Amlogic-ng.arm-21.2-Omega-Generic.img.gz on Android 14 using the test file BL_EL.mkv from this post:
I can see the mentioned lady in the test file and as far as I know 21.2 is kernel 4.9.
So just not sure about 5.15
Ok, tested CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250726-Generic.img with a different dovi.ko.
Dovi settings show up but FEL is dead, TV Led or Player led. It doesn’t work.
The dovi.ko file that I used for NE does work the same for NO, meaning options do show up.
Maybe some more reading will help with confusion
NE is 5.4.210 kernel
NG is 4.9 kernel
Both use Omega 21.2
NO is 5.15 kernel
Uses Piers 22
1 Like
Yeah… deleted all that from previews post, you are correct.
I missred a NE build with a NG one.
DV P7 FEL is not working above 4.9 kernel as previewsly mentioned. My bad.
So that’s kinda sad.
If I understand it correctly the kernel we talk about is the linux kernel which corelec is build on top?
Kodi is system agnostic a aarch64 build should work on other similar arm architectures.
So would be possible to manually build Kodi 22 with 4.9 kernel and keep it updated for the future to come.
This is exactly what I’ve always wondered.
Why not just continue supporting NE and NO with kernel 4.9 and flush 5.4.210 and 5.15 down the toilet?
Because it’s a shit load of work supporting just one kernel by a couple of guys doing this in their free time. Kernel 4.9 is from 2016, and is hard to maintain because of incompatibilities that arise from all the packages with newer features that require newer kernel versions, needed to build CE.
Kernel 4.9 also doesn’t support any SOCs newer than s905x4, support for s904y4, s905w2, A311D2, s928x, s905x5, s905x5m (maybe one or two others) would have to be dropped.
The CE-NG source is available on github for anyone to fork, modify and build if they feel it’s worth their time.
2 Likes
Is it that hard?
I understand is not of CoreELEC team interest to do so and it wouldn’t make sense to do it just because of a feature tied to a specific kernel. That I understand, agree, there’s no debate to be had.
But am I being too simplistic here?
Wouldn’t be just a matter of keep merging kodi changes on top of existing CE-NG we have today?
As I said Kodi should be system agnostic, meaning, kodi itself shouldn’t care about the kernel version unless a specific feature is designed for a specific feature set of the kernel but that would be CoreELEC code and not Kodi.
I don’t want to deviate much from the topic intent which is talk about homatics box but if I understand a little how CE works, the code that cares about kernel version is CE code not Kodi.
So, of course, we would loose features implemented by the CE team, like I’ve seen you guys made a few different tonemap options for Kodi 22 on NO. That would have to be manually backported and this is indeed a ton of work.
Since I’m not talking about CE features and just talking about updating Kodi in the future to keep it compatible with addons and plugins this shouldn’t be this hard.
Unless I’m being simplistic here.
This is Homatics thread and is really not place to discuss
If you want/need Profile 7 FEL than just keep using NG 4.9
It will work for years to come!!!
Forget backport
Happy Testing
2 Likes
Yes, you are.
When it’s that simplistic why nobody provide a fork of CE-NG and Kodi 22?
CE-NG and CE-NE are EOL and CE-NO is current active working branch.
3 Likes
Ok, I’ll see what I can do.
3 Likes