CE-NG Dolby Vision (+FEL) for DV-licensed SOCs (s905x2, s922x/z, s905x4)

A post was merged into an existing topic: Help, support CPM build

Unfortunately, the CPM build wasn’t a viable solution from my perspective as I want native DV support and no tone mapping conversion substitute (Player LED and VS10).

I’ll keep trying the CE-NG releases from time to time to see if the detection of native DV (as well as HDR10+) is fixed.

What is native Dolby Vision?

Native DV is TV-LED, using RGB tunneling to send the data to the TV where it is processed.

That’s been supported in cpm builds and CE.

1 Like

What’s broken about that? Working fine on the NG nightlies for me

1 Like

I’m not sure it will be “fixed” soon, since you seem to be the only one who has an issue with it.

I own a Dune HD Homatics Box R 4K Plus and it works fine in TV-led DV mode (what you call native DV). It is connected to a Denon AVR-X2800H with a Philips 48OLED808 TV behind it.

I admit that it’s weird that in your case CE-NG does not recognize your setup as DV capable while CE-NE does, but that will need to be investigated by providing log files etc. to the developers.

Issue ist in your setup. I have 5 homatics boxes with different batch, and color, and Ugoos amb6+.
No any issue with tv Led, or hdr10plus, or other formats…

So its not CoreElec and/or cpm build issue.

edit;
Using Nokia 8010, Shield Tube via Denon 760h.
Tried NE and NG version with working DV.

As direct-to-tv (bypassing receiver) also fails I would consider replacing HDMI cable anyway and fac-reset.
Also try before all that to change HDR settings in Android (and reboot) to see if such fixes some EDID.

–before edit below–

I risk talking nonsense, especially as it may actually do stuff, but as you are here you probably can digest such yourself;

You could try using a laptop, connected somewhere in your chain, and use Custom Resolution Utility (CRU) to review/adjust EDID readings. Source to be selected/changed.

Worked for me in the past to fix audio/video stuff that was not recognized but supported.

That’s exactly my fear, that it won’t be “fixed” since nobody else than me is experiencing the issue :frowning:

I’m also very puzzled by the fact that CE-NE works perfectly while CE-NG does not “detect” anything.

What’s the AndroidTV of your box? Is it up-to-date on that front or are you still lagging far behind as mine does?

Clearly, CE-NE needs dovi.ko from ATV available at /android/odm/lib/modules/dovi.ko but CE-NG seems really totally independent as we have to put the kernel module ourselves in the right directory.

As far as I can see, this is the only major difference between me and everyone else.

I don’t blame CPM build at all, I’m convinced the problem is elsewhere.

Same question as @MauriceW67 : Are all your boxes up to date on AndroidTV or far behind?

For the record, I don’t even have an account setup on ATV. If I boot it up, it doesn’t get farther than the login screen. I don’t need nor use AndroidTV at all and I don’t want to set it up.

Blockquote As direct-to-tv (bypassing receiver) also fails I would consider replacing HDMI cable anyway and fac-reset.
Also try before all that to change HDR settings in Android (and reboot) to see if such fixes some EDID.

This week end I’ll try with another HDMI cable but I’m not really convinced since they already are high grade certified cables and confirmed by the internal testing procedure on the Denon AVR.

What factory reset are you talking about?

I don’t understand the EDID part. As far as I know, EDID is provided by each display device and not modifiable (except extracting it, modifying localy and forcing it in the related driver and/or application) so I don’t know what Android will do that will make the TV “change” the EDID in any way.

Best guess is that that you are dealing with an EDID parsing bug that is present in CE-NG, and not CE-NE. But the bug seems to only be triggered by a very small number of TVs/EDIDs. If you have a second DV capable television you can double check that DV support is appearing there under CE-NG.

(edit 2 (most recent));

ensure you adopt the correct dovi.ko, even if you, as mentioned, already confirmed

Download
dovi.ko for s905x2 & s922x/z
dovi.ko for s905x4
Three optional locations to copy dovi.ko to CoreELEC:
a) Samba: copy dovi.ko to Configfiles folder
b) PC: plug CoreELEC USB into computer copy dovi.ko over (same directory with dtb.img & kernel.img).
c) SSH: copy dovi.ko to /storage/dovi.ko
This will supersede any other copy of dovi.ko on the device

(edit; typo and adding to opted possibility of read-out issues)

I lack proper know-how and do/did not know in what way EDID values will stick to devices.
For testing purposes it makes sense to remove the receiver to rule it out.

The factory reset was ambiguous because it only relates to devices in the chain that could benefit from such.
So with TV-device scenario it is reset on tv and/or device.
Again, this is trying to inspire as I lack any fair grasp of the situation.

As I make this response I also see the response by YadaYada and would take his/her advice to more value as mine :wink:

If EDID is never to be corrupted I would say you should ensure a proper format and re-installation of CE to try to remove unknown causes.
This also depends on what sticks to Android device itself…

Im not talking just about cpm build, but CE NG.
You wrote, those not working for you.
My homatics and dune homatics boxes all have different atv12 firmware, and different revisions number.

So again, your issue not the CE=NG or cpm-NG issue.

Made a factory reset in your android, then build new the CE installation.
When thats not help try in one other tv, other cables, etc. until you find your issue.

My Dune Homatics is running the latest ATV 12 beta build (7954).

I think you’re right as I suspect the same thing. I’ve tried a brand new install with the latest nightly CoreELEC-Amlogic-ng.arm-21.1.1-Omega_nightly_20241109-Generic.img on a different USB stick and even used a different cable from a different brand connected directly to the TV, the result was no joy again. In Kodi, SystemInfo → Video keeps only listing HDR and HLG.

This week I’ll reach out to the store where I bought the TV as I befriended the manager and I’ll ask if I can test my DuneHD Box R on a few TVs, mainly from Panasonic and LG as Samsung doesn’t support DV at all. I’ll keep you posted on the results.

Well, factory reset the CE install is what I’ve done many times now. Doing it on the TV is not an option as I already spent a great deal of time configuring it to scan DVB-T channels, removing all bells-and-whistles effects and modes all activated by default. Modern TVs have settings dependent on the current HDMI input as well as input content (SDR, HDR, HDR10+, DV, HLG) because depending on that, some settings are unavailable and/or greyed out. I’ve leveraged that in trying one HDMI input still using factory default settings. Nothing changed so factory reset the TV would only be a hassle without any benefit :wink:

Don’t worry about your “lack of grasp”. The mere fact that you’re trying to help so willingly deserves respect so thank you!

As said above, tried new cables and I’ll try a new TV. Factory reset the Android is not yet an option, at least not until I test on other TVs. Because of this mystery on my device, I don’t want to end up with a non-functional DV in case the factory reset ruins the CE-NE side too for some obscure reason.

I’m in a situation nobody faced yet which is a working CE-NE and non-working CE-NG. I don’t want to start a war at home because the “video thingy” is not working if you see what I mean :wink: I need to proceed cautiously :sweat_smile:

I just tested your EDID and there is no difference between NG or NE. Result is same. Make a log of fw_printenv | paste, should not matter if NG or NE.

Here we go https://paste.coreelec.org/FuhrerRamona

Thank you for your help

– EDIT –
This is from CE-NE working fine

CoreELEC (official): 21.1.1-Omega (Amlogic-ne.aarch64)
      Machine model: Dune/Homatics R 4K Plus
     CoreELEC dt-id: sc2_s905x4_sei_smb_280_id5
      Amlogic dt-id: sc2_s905x4_ah212-id5
      Linux version: 5.4.210 (portisch@ubuntu) #1 Mon Aug 26 19:57:51 CEST 2024
      Kodi compiled: 2024-08-26 18:23:54 +0200

Run fw_setenv hdr_priority 0 and reboot.

4 Likes