For “live” media this closed PR is need:
But origin Kodi isn’t at that level with DV as we are.
Once when that live bitrate merged into Kodi, we can add to that to the CE ppinfo, replace the current static bitrates.
But it is nothing about the DV profile detection.
At least it’s good that you got an acknowledgement from them that the way Kodi does it is wrong:
“Even so, it is still incorrect that VideoPlayer infolabels are fed by information from the database and not from the stream that is being played… “.
A shame they don’t want to change it. Maybe a CE feature instead, until they decide to implement.
The CEC issue has finally been resolved. This problem had arisen with the new Polk Audio soundbar I purchased.
I was able to partially resolve the issue by turning off the screen refresh rate.
The real problem was this: When I set the TV’s resolution and refresh rate to 1080p and 50 Hz, this setting didn’t work, and the soundbar kept changing the screen refresh rate to 60 Hz.
Now, after setting the TV’s resolution and refresh rate to 1080i and 50 Hz, everything started working as it should.
Note: The TV is 1080 HD, not 4K.
With today’s night CE NO got a visible ( at least for me) leap forward on any video format.
Bravo! as usually CE Team. If someone do not understand what you are doing is simply ignorant.
Me too! I have an old TV and a Klipsch 200 soundbar, the volume of which is controlled via CEC with the box remote. Previously, until about the second-to-last nightly build, CEC would sometimes randomly fail, and instead of adjusting the soundbar volume, the remote would adjust the volume in Kodi (the volume circle at the top of the screen). Restarting Kodi (often multiple times!) helped. Now the problem is completely gone. Thanks!
The fact is that CE-NO, even in its nightly version, is much more stable than the official firmware of my Dune Pro Vision 4K 
My TV doesn’t even have HDR, let alone DV. But it’s precisely because of its stability and open source nature that I prefer CE.
The only problem I have now is crashes when closing/restarting Kodi, which occurs if addons using threading lib, like YouTube, are running. Shutdown takes much longer than usual, a Crash log file appears and contains something like:
Program terminated with signal SIGABRT, Aborted.
#0 0x0000007fa78ad844 in ?? () from /usr/lib/libc.so.6
————————
info : CPythonInvoker(…/plugin.video.youtube/resources/lib/service.py): waiting on thread…
But Kodi never crashes or glitches while running, so it’s not a big deal. Although, I’d like to see it fixed.
@Portisch can you enable emmc HS400 support in dtb for AM8?
I have a very problematic UHD BD, “A Knight’s Tale”, the problems show in both the original BD and all the remuxes. It appears almost exactly the same as I reported some time ago in NG on the AM6B+ here:
In short, there are many places where a scene change occurs and there is a brief blackout and loss of audio. Always the same place, and this does not occur when using any other player on Windows to play the same files.
I managed to grab a logfile a few seconds after one of them:
https://paste.coreelec.org/CultureRaincoat
In the logfile, I think it happens a few seconds before the pause key press at around time 2026-05-30 00:06:04.523. I notice there’s an ffmpeg fail, which was originally a red herring when investigating this on NG.
A new oddity which did not occur originally in NG is that, if I skip backwards to before the glitch happens, it does not reliably repeat the glitch when playing again. In NG it would happen every time. But later glitches (there are many) will still happen when playback continues.
Also, during playback of that file I noticed that I could not skip forward past the chapter marker where the first glitch happens at 17:20. It just kept restarting from that chapter marker. Using the slider to move past worked.
Finally, I was going to turn on debugging when the above started to happen, but when I pressed back a few times to get to the menu, the AM9 Pro spontaneously rebooted before I could get there and rebooted into Android. I could not get that to reproduce but it is the second such reboot I’ve had (the other was playing “The Gorge” and also would not reproduce).
Of course, if I can get any of the above to reproduce, I’ll get a log.
I answer myself.
Yes, it works.
From CE21 update to CE22 on eMMC (ceemmc -x) worked nicely.
CE22 on SD card >> eMMC
(Generic S905X3 device)
There is this old patch from OSMC that is supposed to fix BDs with seamless branching. If you are able to build a CE image you can try it:
kodi-osmc-174-avoid-flooding-the-AMLCodec-with-empty-packets-solve.patch (944 Bytes)
Amlogic S905X4 Android 11.0 HK1 Box X4 4GB RAM 64GB ROM Dual-WiFi 2.4GHz/5GHz BT Quad Core 64 Bits 3D/8K 1000M
Updating NO when Nightly available for update.
Currently running and updated to:
CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20260531-Generic.img.gz
Seems to be stuck on DB update for a while…then after about 5 minutes boots to KODI then it reboots; never plays any movies on my NAS. Seems stuck.
Lost DB and history of movies / TV series watched.
Downgraded to:
22.0-Piers_alpha3/CoreELEC-Amlogic-no.aarch64-22.0-Piers_alpha3-Generic.img.gz
After update to 20260531 I got empty movies and tv series database. roll back to 29
I have this same experience with media database at last build with SMB (SQLite error SQLITE_ERROR). HS400 emmc is working for my device Ugoos am6plus (this function is not for all device and new users - high risk of bootlooping with devices as Minix u22 s922xj). After update is also yuotube as instabile.
Installed CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20260531-Generic.img from scratch, SD-card, AM9 Pro.
Media database built correctly with movies and music, using NAS with nfs.
Bluetooth pairings are lost on every reboot, they show correctly on list with yellow star but are impossible to connect without re-pairing.
EDIT: Paired device MAC address changes every time after lost connection, permanent pairing impossible
Audio output device setting is lost after reboot, defaults to:
ALSA:surround71:CARD=AMLAUGESOUND,DEV=0|AML-AUGESOUND
It should be:
ALSA:iec958:CARD=DAC58580408,DEV=0|ADI-2 DAC (58580408)
This is correctly saved in guisettings.xml but after reboot it is back to wrong default.
EDIT: Default audio device is marvellously and totally intuitively placed in BLUETOOTH SETTINGS
What a great idea to put this setting into.
Looks like TK have merged the wrong PR. Nightly got removed and next 20260601 should work normal again. Maybe a new setup of the library is need when 20260531 was installed.
I confirm, me too
The library setting is present and therefore configured as in version 29, so the search for new elements is not performed or bypassed because it does not find anything new
if you are getting a database migration failed error need to roll back to the previous nightly you can find it here
There is also second issue which was not before update to build from 31 may 2026. After update to last build and also after roll back was create new issue for both cases:
2026-05-31 13:39:09.596 T:1494 debug <inputstream.adaptive>: [AS-0] Download finished: https://dash3.antik.sk/stream/nvidia_jednotka/v_h264_1080_5500_cbcs_init.mp4 (downloaded 1230 byte, speed 483490.00 byte/s)
2026-05-31 13:39:09.597 T:1491 debug <inputstream.adaptive>: UpdateSampleDescription: Codec fourcc: avc1 (1635148593)
2026-05-31 13:39:09.598 T:1491 debug <inputstream.adaptive>: Initialize crypto session
2026-05-31 13:39:09.598 T:1491 debug <inputstream.adaptive>: SelectDRM: Selected DRM key system: com.widevine.alpha
2026-05-31 13:39:09.598 T:1491 debug <inputstream.adaptive>: [WV-CDM-Library] CDM version: 4.10.2662.3
2026-05-31 13:39:09.614 T:1491 debug <inputstream.adaptive>: [WV-CDM-Library] CDM is initialized: true
2026-05-31 13:39:09.649 T:1491 error <inputstream.adaptive>: CreateSession: Session creation failed: CDM reject: 0 sys=2
2026-05-31 13:39:09.649 T:1491 error <inputstream.adaptive>: InitializeSession: Failed to create the DRM session