2024-12-26 13:57:16.039 T:1214 info <general>: CAMLCodec::OpenDecoder DOVI: version 1.0, profile 8
2024-12-26 13:57:16.039 T:1214 info <general>: CAMLCodec::OpenDecoder Amlogic device does support DV, DV is enabled by user, display does not support DV, DV system is disabled
1 Like
i have same bug on am6plus.
Jump back to post # 907
7 days ago
Use Portisch test image from there
And the dovi.ko link there
Copy *dovi to root ,alongside renamed DTB.
Turn off automatically update in settings
*dovi
For some reason i had to rename dovi.ko to just dovi
Still reads as ko file
1 Like
I just tried to boot from ĀµSD and eMMC. Boot and update from 20241220 to 20241225 did work without issues. The boot switch is in MMC position.
The same frame skipping with x265 encoded sources that was observed in -ne after November 26th happens also with the latest -no.
Freddy, the Mega folder associated with message 907 is now empty.
Ok
Thought maybe would help
1 Like
Because your AVR cut off DV modes?
Decode your EDID, there is no info about DV at all.
1 Like
Itās ok! @Portisch, sorry for wasting your time with this problem that was on my TV side. Quite surprising that it is not specified anywhere in the Sony interface that activating VRR disables compatibility with Dolby Vision. 
Which does not suit me, by the way.
On the CE interface side, rather than making the Dolby Vision options disappear in the system settings, it would be more meaningful to gray them out by showing a message like ādisplay does not support DVā. This would allow you to more quickly discard bad tracks and focus on the other side of the chain.
Thank you very much for your support!
Set to Player-LED (YCbCr 4:2:2), Dolby Vision works on all my samples, even on hybrid HDR10/DV files. Perfect!
However, I still see the following issues:
- While playing an HDR movie, Artifact flashes appear every time you move forward or backward.
- When reading a movie, we get a black screen when DV is set to TV-LED (RGB 4:4:4).
- I am experiencing abnormally very low GUI performance. About 100% less framerate compared to the CE-21 build and CE-22 (5.4.210) : 30 FPS VS 15 FPS on average (GUI is set to 4K resolution without upscaling). Maybe GPU driver issues?
- Permanent signal loss when changing sources. Forced to reboot to recover the image.
- Tone map SDR to HDR function that darkens the interface abnormally; when Dolby vision mode is not activated. And which sends a definitive black screen, when this function is applied and Dolby Vision is activated. Tip: if this happens to you, simply deactivate Dolby Vision from your TV and restart everything to find an image.
Accidentally auto-upgraded, so was able to grab dmesg before I downgrade again:
On first boot HDMI output works fine, but as soon as the display is turned off once, no HDMI output until reboot, though Kodi continues to successfully send CEC messages across the link.
Below is the diff between boot and good display power cycle (5.15.119), and boot and bad display power cycle (5.15.137):
1 Like
I want to install coreelec on my tv box.
The installation is working fine, unfortunately I canāt install any add-ons.
The problem is with the version: CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20241225
Error message: error <general>: CCurlFile::Open - <https://addons.coreelec.org/Amlogic-no/22.0.3/aarch64/addons.xml.gz?sha256> Failed with code 0: error <general>: CCurlFile::Open - <https://addons.coreelec.org/Amlogic-no/22.0.3/aarch64/addons.xml.gz?sha256> Failed with code 404:
The message on the screen: Could not connect to repository.
There are currently issues with addon server what we need to sort out first.
All new CE-NO 22.0 are affected.
1 Like
I frankly prefer to leave the legality side of this completely out of the discussion, as not the whole worldās rules are equal and, more broadly speaking, I donāt want to be a hypocrite, regarding piracy, etc.
What I would like to understand is the NGās side of this. Is there anything stopping a sufficiently motivated developer from implementing Kodi 22 in the NG branch? I am not asking for you to do this, itās your choice and not mine, I am simply trying to understand if the problem is a matter of resources or if there is something else stopping Kodi 22 coming to the NG branch.
Again, I stress this, I am NOT asking Team CE to do it. You have expressed many times your view on this. Iām just trying to understand if there could be other ways to make it happen, as NG, on some hardware, still represents some sort of a āunicumā in the Kodi boxes world (FEL compatibility).
Thanks for your answer and thanks for CE.
1 Like
There are not much people who understands Amlogic and Kodi. So I would say your wishes will not come true.
1 Like
Good luck with that. Weāve said multiple times that we would accept help from other Devs and we got almost nowhere.
2 Likes
As also written already NG kernel is not CE-22 compatible and Kodi 22 is not CE-21 compatible.
3 Likes
I must have missed this. But I understand weāre offtopic here (donāt know where this discussion could be on topic but I am afraid of boring or upsetting you).
You will need to share a short sample.
Same issue here, revert back to the previous version. Something that I also noticed was that I stopped receiving new update notifications when I went from 21 to 22 nightlies. I was surprised on Christmas on the update notification, which I loved the bootscreen. Thanks devs & contributors.
Happy holidays!
1 Like