[EXPERIMENTAL] CoreELEC 22 · samurihl DV build (20260909205124)

⚠️ EXPERIMENTAL · UNSUPPORTED · USE AT YOUR OWN RISK

This is an unofficial, experimental CoreELEC 22 build. It is NOT an official
CoreELEC release and it is NOT a supported CE22 port. I am not a CoreELEC 22
port maintainer, and I will not be providing support, bug fixes, updates, or
ongoing maintenance for this build.

The only purpose of this build is to give Amlogic AM9 Pro-class users a more
complete Dolby Vision experience than stock CoreELEC 22, by carrying a set of
custom Kodi features I built for my own device. That is the entire scope.

READ THIS BEFORE YOU FLASH ANYTHING

• USE ENTIRELY AT YOUR OWN RISK. There is no warranty of any kind, express
  or implied. It may fail to boot, misbehave, break Dolby Vision, or do nothing
  useful on your hardware.
• BACK UP YOUR CURRENT INSTALLATION FIRST. Take a full CoreELEC backup
  (Settings → CoreELEC → Backup) and/or image your existing boot media before
  you install anything from here. Assume you may have to restore it.
• Prefer a SEPARATE SD card or USB stick you can boot from, instead of
  overwriting a working internal (eMMC) install.
• Do NOT report problems with this build to the CoreELEC team or forums.
  This is not their build; it is not their responsibility. Do not ask them to
  support it.
• I am also not offering support. If it breaks, you keep both pieces.

By downloading or using any file in this release you accept all of the above.

Install

• Clean install (recommended): flash the *.img.gz to an SD card or USB with
  balenaEtcher (or the Amlogic USB Burning Tool for eMMC), then boot from it.
• In-place update: copy the *.tar to the /storage/.update folder on an
  existing CoreELEC install and reboot. (Back up first — see above.)
• Verify your download against the SHA256 sums below before flashing.

---

What's changed in this update

This is a single-fix incremental update to
v22.0-samurihl-20260909193640
(see that release and its predecessors for the standing feature set: Blu‑ray disc
menus, HDR10+ → Dolby Vision conversion, CMv4.0 metadata control, DV → HDR10 that
stays in HDR10, FEL profile‑7 reconstruction on non‑DV displays, VS10 output on
non‑DV displays, VSVDB override, tone‑mapping target controls, disc‑stated menu
detection and episode lists).

Nothing else changed. If you are on the previous release and the reference‑black
setting is not something you use, you can skip this one.

⚠️ Still experimental and completely unsupported — see the disclaimer above.
Back up your current install before flashing.

Dolby Vision still requires dovi.ko (the CE22 5.15 build) installed on your
device — it is not bundled; install it yourself as on stock CoreELEC 22. You do
not need to modify it — this build corrects it automatically at boot.

---

⚫ Fixed: reference black on HDR converted to Dolby Vision

The report. Black level did not apply to VSVDB -> DV output.

What was actually wrong. The August fix made the setting apply when the player
was told to output Dolby Vision. But Dolby Vision reaches your television by more
than one route, and on the other routes the player never knew it was the one
producing a Dolby Vision signal — so it wrote a zero and the setting sat there doing
nothing. Three routes were affected:

• "Convert HDR10 to Dolby Vision" (and the SDR equivalent) — the long‑standing
  CoreELEC toggle, used with the VS10 output spinner left at its default. This is
  almost certainly the one being reported: HDR10 on the disk, Dolby Vision on the
  wire, black‑level control inert.
• HDR10+ → Dolby Vision conversion — this build's own feature, same story.
• The first moments of a Blu‑ray disc — from disc open through the studio
  logos and the menu, Dolby Vision is already engaged before the first title
  starts, and the target was not applied until that title opened.

A native Dolby Vision title was never affected; that is the half August fixed, and
it is why the fault looked like a user error rather than a bug.

Measured, before and after, on the same box and the same film. An HDR10 title
with "Convert HDR10 to Dolby Vision" on, the VS10 spinner at its default, TV‑led
output, and the reference black set to 137:

	previous release	this release
Dolby Vision output mode	tunnel (i.e. real DV on the wire)	tunnel
Dolby Vision engine	on	on
target handed to the display engine	0 — setting ignored	137 — setting applied

Also fixed: moving the slider during playback. On those same routes, changing
the reference black while a film was playing reset it to zero instead of applying
it. It now follows the change immediately, which makes the setting practical to dial
in against a test pattern rather than by restarting a film per value.

What has not changed: the maximum (peak) target is still HDR10‑only, on purpose —
see the previous release's notes for why. Native Dolby Vision titles behave exactly
as before. A stream that is not going out as Dolby Vision still leaves the control
alone entirely.

Still asking for eyes. As with August: that the setting now reaches the display
engine on every route is measured and certain. Whether a given value looks better
on your television is not something this fork can answer for you — and note that on
TV‑led Dolby Vision your television performs the final mapping, so do not expect the
same behaviour there as on player‑led output. If you are the person who reported
this, please set it, watch it, and say what you see.

---

Source

• CoreELEC (distro): SamuriHL/CoreELEC tag v22.0-samurihl-20260909205124
• Kodi: SamuriHL/coreelec-xbmc tag v22.0-samurihl-20260909205124

Checksums (SHA256)

224a69b47a16b19f372f784e6526a42d06ea9936c7ca4e0ce19dee26aa1b85e9  CoreELEC-Amlogic-no.aarch64-22.0-Piers-samurihl-EXPERIMENTAL_20260909205124.tar
e11d441e4b66df4ab352ebc6e5617578ced2d14d4ebd48c37a6d771cc469f272  CoreELEC-Amlogic-no.aarch64-22.0-Piers-samurihl-EXPERIMENTAL_20260909205124-Generic.img.gz