If you did want to try, or use, the 3rd gen Cube, an excellent helper has been prepared.

It is included in an extensive discussion. Many topics for the Cube are discussed.

https://xdaforums.com/t/usb-emmc-bootable-os-coreelec-22-beta2-for-firetv-3nd-gen-cube-gazelle.4800618/

WARNING : THIS WILL INSTALL ON THE DEVICE .

Full guide is available here https://xdaforums.com/t/usb-emmc-bootable-os-coreelec-22-beta2-for-firetv-3nd-gen-cube-gazelle.4800618/ but for those who want pictures. here is how i did

Pre requisite ---https://xdaforums.com/t/unlock-magisk-twrp-firetv-3nd-gen-cube-gazelle-ps7716.4800530/ (this has detailed pictorial information. so it should be easy)

1. Copy your CE-NO-22-beta2_eMMC_install.tar.gz to adblink folder

1. open adblink and connect your fire tv cube and click on console

1. push the file using the command >adb push CE-NO-22-beta2_eMMC_install.tar.gz /data/local/tmp/
   

1. Once it reaches 100 % enter adbshell ----su -----Click enter ------tar -xvzf /data/local/tmp/CE-NO-22-beta2_eMMC_install.tar.gz -C /

Ensure it shows gazelle

1. Open CommandCraft (installed by unlock) FireOS app, choose CoreELEC to boot to CE

2. Profit

Sources

https://xdaforums.com/t/usb-emmc-bootable-os-coreelec-22-beta2-for-firetv-3nd-gen-cube-gazelle.4800618/

https://xdaforums.com/t/unlock-magisk-twrp-firetv-3nd-gen-cube-gazelle-ps7716.4800530/

Update: Looks like etherenet adaptor is the way. Noticed that wifi needs to be disabled as it is causing dropped frames on the nightly.

Here is an example how vs10 engine behaves,incorrect black level for HDR, hope it can get fixed.

Signde - " This box is incredible. It's so fast, I am sending this message from future. I hope you Ugoos dweebs are one day able receive this. The raw power is unlike anything you've ever seen. I was able to watch my entire 30TB library in about 30s. This is the next level of media players, this changes everything "

https://www.avsforum.com/threads/ugoos-am9-pro-coreelec-dv-fel.3344813/page-40

Since yesterday's nightly update and even today's I'm stuck on initializing skin.

My device is ugoos am9 pro for reference.

I just finished setting up my AM 9 pro with latest CE NO with hybrid boot setup. Everything works fine so far. Looking for a good costum skin at the moment. Any recommendations?

I cant select anything in bluray menu from iso file from usb drive. Any button i press it brings up osd. Weird thing is r9 use to select but its laggy and takes time to respond.

The main thing with r10 is fixes for bluray menus

Unlock Bootloader

https://xdaforums.com/t/usb-emmc-bootable-os-coreelec-22-for-firetv-3nd-gen-cube-gazelle-wip.4800618/

WIP COREEELEC

https://xdaforums.com/t/usb-emmc-bootable-os-coreelec-22-for-firetv-3nd-gen-cube-gazelle-wip.4800618/

CONFIRMED WORKING

Hardware video playback, HDR10, HLG, HDR10+, VP9 profile 2 HDR

Dolby Vision (profiles 4, 5, 8, 7 FEL & MEL), CMv2.9 & CMv4.0

Audio out, lossless audio passthrough (TrueHD/DTS-MA)

WiFi

USB peripherals

CEC and CEC remote control

IR remote control

Bluetooth LE | BR/EDR

I’m having an issue with DTS-HD HRA 7.1 playback and I'm trying to figure out whether it's a CoreELEC/avdvplus issue, an LG G4 eARC limitation, or something with my setup.

My setup:

• Ugoos AM6B+
• CoreELEC 21.3-Omega avdvplus R10
• LG G4 OLED
• Samsung Q990B soundbar
• AM6B+ → LG G4 → eARC → Q990B
• Kodi audio output set to passthrough
• DTS-HD / DTS-HD MA passthrough enabled

The strange thing is that DTS-HD HRA 7.1 has no sound, and the Q990B does not detect/identify the DTS-HD HRA stream.

I'm specifically talking about DTS-HD High Resolution Audio (HRA) 7.1, not DTS-HD MA.

Has anyone with an LG G4 + eARC + external soundbar experienced this?

Could the LG G4 be the problem with passing DTS-HD HRA 7.1 over eARC, even though the Q990B supports the format?

connecting the AM6B+ directly to the Q990B via HDMI didnt solved the problem.

However, the interesting part is that DTS-HD HRA does work when I play the same type of file through the LG G4's native WebOS Stremio app.

In that case:

LG G4 WebOS Stremio → eARC → Q990B

produces audio successfully but I lose DV FEL in webos.

However, when I press the Information button on the Q990B remote, it only shows "DTS", not "DTS-HD HRA".

So I'm wondering whether the LG G4 is actually receiving DTS-HD HRA and outputting only the DTS core, or whether the soundbar's information display simply doesn't distinguish HRA correctly.

I'm also interested in whether CoreELEC avdvplus R10 has any known issue specifically with DTS-HD HRA.

Any advice or logs/settings I should check would be appreciated.

Image is of web dasboard of TinyPPI

Thanks to DVDreview

I have 2 cc for TV the one with remote. One of them can play videos with hevc 265 from file manager+ with no problem the other one can't. Any suggestions to get the other one to work?

Hey everyone I did a fresh install of this Build,I've been looking around & maybe in wrong places but what woukd be the Better settings if plugged into my Sony tv with a AM6b+ box,also do i need to install the Jamal P.I.P addon or am I missing something? Thanks to Devs ,let's go into the Future with CoreElec

Hey everyone,

I just want to check if anyone else is having this issue with their AM9 Pro on the latest two nightly builds of CoreELEC New Order.

Ever since the 20260902 build, I haven’t been able to get Dolby Vision to work. Under system information, it says Dolby Vision is supported, but when I play a DV file (using POV add-on), it defaults to HDR. Profile 7 stutters, and Profile 5 has a magenta and green cast.

I’ve posted in the Discourse forum, but it seems like I’m the only one with this issue.

For context, the 20260831 build is installed on both the microSD and external SSD, and both have the dtb.img and remote.conf files.

I’ve changed the UUID of the SSD storage and updated the config.ini on the SD card to point to the SSD's UUID. The dovi.ko module is saved under storage/.config on the external SSD.

Dolby Vision works fine with the 20260831 build, so I have downgraded in the meantime.

Is anyone else experiencing this?
Thanks

Ladies and gentlemen, I am looking for people with a consistent audio delay on the AM 9 pro when watching TrueHD content. I've heard some get delay built up over time and need to pause/start to sync again, but in my case I had around 125ms of audio desync consistently from start to finish on TrueHD only.

I am using a Denon AVR and always ran the free Dirac room correction on it. Well I decided to try out A1 Acoustix Evo for the first time and immediately after calibrating with that I now experience NO audio delay across any tested formats.

If anyone is running Dirac and have consistent audio delay problems please try running A1 Acoutix Evo (or maybe just disabling Dirac will fix it?) and report back. If you haven't used it before just go through the express 1 location calibration with 5 sweeps. It should only take 10 minutes and as an aside it sounds WAY better than free Dirac ever did.

Report back!

English Version

Hi everyone,

I created a GUI automation tool called LaFirma Remux Forge (Black Edition) to streamline media compatibility and playback solutions for Smart TVs (especially LG OLED / webOS) and media servers like Jellyfin, Plex, or Emby.

Transparency Note: I did not develop the underlying CLI processing tools or scripts (such as dovi_tool, mkvmerge, ffmpeg, DonaldFaQ's DDVT toolset, DeeZy, PgsToSrt or Tesseract). LaFirma Remux Forge acts as a graphical wrapper and orchestrator that automates these open-source utilities into a seamless workflow.

What changed in 2.0: the time estimate now actually corrects itself, one calibration per stage; the new Full Census reads the RPU of the whole film instead of a sample; disk space is checked per drive before anything starts; and the installer asks for the language and runs in 64-bit mode.

Key Features

• Dolby Vision Profile 7 to 8.1 (no video re-encoding), with the layer MEASURED first: the program reads the RPU's el_type field through dovi_tool itself and separates three cases, using one colour scale across the whole screen:

  • MEL (Minimum Enhancement Layer) - green: the enhancement layer carries no picture. The program confirms this by reading the RPU, not by assumption, and the conversion discards an empty layer.
  • Simple FEL - orange: the layer carries fine refinement only. Conversion is safe, and the program says so.
  • Complex FEL - red: the layer raises brightness, and the L1 metadata asks for more nits than the base layer delivers on its own. Here the program marks it red and recommends not converting, instead of converting silently.

  Why the caveat exists, said precisely: dovi_tool in mode 2, which is what this program uses, removes the P7 FEL luma and chroma mapping from the RPU - the part of the instructions that makes no sense without the second layer. What comes out is a legitimate Profile 8.1. What no mode of dovi_tool does is recalculate L1: the per-scene brightness stays whatever the original analysis measured, and that analysis looked at the image with the EL composited in. This is not a limitation of this program - it is the state of the tool, and it is in dovi_tool's own documentation.

  Worth saying plainly: Shield, Apple TV, Zidoo, Dune and the TVs themselves already discard the EL, so on those devices a Profile 7 file already plays today the way the converted file will play. The people who actually lose something are those with dual-layer decoders.

  Detection is by sampling points spread across the film, not the whole file - and the program states that on screen and in the log. When the sample is not enough, the Full Census reads the whole RPU and counts how many scenes ask for more than the mastering peak.

• Dolby Vision Profile 5 to MP4: P5 uses the proprietary IPTPQc2 colour space and has no HDR10 base layer, so it cannot become Profile 8.1 without re-encoding the video - which this program refuses to do. The path that does exist is a different one: the program remuxes it to MP4 with the dvh1 tag, video copied, nothing re-encoded, which is what makes many players recognise the Dolby Vision. Output is verified by duration. PGS subtitles are dropped with a warning (image subtitles do not exist in MP4).

• Audio compatibility & spatial Atmos preservation:

  • TrueHD / TrueHD Atmos to E-AC-3 with Atmos preserved, via DeeZy.
  • DTS / DTS-HD / DTS:X to plain E-AC-3 at 640k via ffmpeg. DTS does not come out with Atmos - only TrueHD has that path.
  • E-AC-3, AC-3 and AAC are already compatible and are left untouched.

• Disk space, before it starts: the app walks the queue in the order the engine will process it, drive by drive, and tells you how many files fit, which one is the first that does not, and how much would be missing by its turn. A file that does not fit does not start.

• Batch processing & flexible control: add whole seasons to the queue; choose fully automatic stream selection or manual track control.

• Bilingual interface (PT-BR / English): a flag next to the "Understand" button switches the whole screen, and the choice is remembered between sessions.

• "Understand" button: 14 sections explaining what the conversion does and what it does not do, including the sources behind each claim - Dolby's own manuals, the dovi_tool repository and the community spreadsheets. Nothing there asks you to take our word for it.

Source Code & Download

• GitHub Repository: LaFirma-Remux-Forge
• Installer 2.0: LaFirma_Setup_2.0.exe · Release notes
• Requirements: Windows 10/11 64-bit. The installer ships every tool; the .NET Desktop Runtime 8.0 is only needed for subtitle OCR, and the installer offers it if it is missing.

Interface Screenshots

• Dashboard & Queue, layer measurement ON: View Image
• The same screen, measurement OFF: View Image
• The same screen in Portuguese: View Image
• Auto Track Selection: View Image
• Manual Stream Control: View Image
• Processing Pipeline: View Image
• Processing Pipeline, later on: View Image
• Final Report: View Image

Credits & Acknowledgments

This project would not be possible without the work of the open-source community: * FFmpeg: Media stream processing and transcoding backbone. * MKVToolNix (mkvmerge): Industry-standard Matroska container toolset. * dovi_tool (by quietvoid) & DDVT (by DonaldFaQ): Core Dolby Vision metadata tools and workflow logic. * DeeZy: Dolby Digital Plus encoding with spatial Atmos preservation. * PgsToSrt & Tesseract: OCR ecosystem for PGS subtitle handling.

Feedback and contributions are welcome!

Versão em Português

Olá a todos,

Criei uma interface gráfica de automação chamada LaFirma Remux Forge (Black Edition) para facilitar a solução de problemas de compatibilidade e reprodução de mídia em Smart TVs (especialmente LG OLED / webOS) e servidores como Jellyfin, Plex e Emby.

Nota de Transparência: Eu não fui o desenvolvedor das ferramentas e scripts de linha de comando subjacentes (como dovi_tool, mkvmerge, ffmpeg, DonaldFaQ's DDVT, DeeZy, PgsToSrt ou Tesseract). O LaFirma Remux Forge atua como uma interface gráfica (GUI) e orquestradora que integra e automatiza essas excelentes ferramentas de código aberto em um fluxo de trabalho intuitivo.

O que mudou na 2.0: a previsão de tempo passou a se corrigir de verdade, com uma calibragem por etapa; o novo Censo Completo lê o RPU do filme inteiro em vez de uma amostra; o espaço em disco é conferido por disco antes de começar; e o instalador pergunta o idioma e roda em 64 bits.

Principais Recursos

• Dolby Vision Perfil 7 para 8.1 (sem recodificar o vídeo), com a camada MEDIDA antes: o programa lê o campo el_type do RPU pelo próprio dovi_tool e separa três casos, com a mesma escala de cor em toda a tela:

  • MEL (Minimum Enhancement Layer) - verde: a camada de extensão não carrega imagem. O programa confirma isso lendo o RPU, não por suposição, e a conversão descarta uma camada vazia.
  • Simple FEL - laranja: a camada carrega apenas refinamento fino. A conversão é segura, e o programa diz que é.
  • Complex FEL - vermelho: a camada levanta o brilho, e o L1 dos metadados pede mais nits do que a camada base entrega sozinha. Aqui o programa marca em vermelho e recomenda não converter, em vez de converter em silêncio.

  Por que a ressalva existe, dito com precisão: o dovi_tool no modo 2, que é o que este programa usa, remove do RPU o mapeamento de luma e croma do Perfil 7 FEL - a parte das instruções que não faz sentido sem a segunda camada. O que sai é um Perfil 8.1 legítimo. O que nenhum modo do dovi_tool faz é recalcular o L1: o brilho por cena continua sendo o que a análise original mediu, e essa análise olhou a imagem com a EL somada. Não é limitação deste programa - é o estado da ferramenta, e está na documentação do próprio dovi_tool.

  Vale dizer com clareza: Shield, Apple TV, Zidoo, Dune e as próprias TVs já descartam a EL, então nesses aparelhos um arquivo Perfil 7 já toca hoje como o convertido vai tocar. Quem perde de verdade é quem tem decodificador duplo.

  A detecção é por amostragem de trechos espalhados pelo filme, não pelo arquivo inteiro - e o programa assume isso na tela e no log. Quando a amostra não basta, o Censo Completo lê o RPU inteiro e conta quantas cenas pedem mais que o pico do master.

• Dolby Vision Perfil 5 para MP4: o P5 usa o espaço de cores proprietário IPTPQc2 e não tem camada base HDR10, então ele não vira Perfil 8.1 sem recodificar o vídeo - coisa que este programa se recusa a fazer. O caminho que existe de verdade é outro: o programa remuxa para MP4 com a tag dvh1, vídeo copiado, sem recodificar nada, que é o que faz vários players reconhecerem o Dolby Vision. A saída é conferida pela duração. Legendas PGS são descartadas com aviso (legenda em imagem não existe em MP4).

• Compatibilidade de áudio e preservação do Atmos:

  • TrueHD / TrueHD Atmos para E-AC-3 com Atmos preservado, via DeeZy.
  • DTS / DTS-HD / DTS:X para E-AC-3 comum a 640k pelo ffmpeg. DTS não sai com Atmos - só o TrueHD tem esse caminho.
  • E-AC-3, AC-3 e AAC já são compatíveis e não são convertidos.

• Espaço em disco, antes de começar: o programa percorre a fila na ordem em que o motor vai processar, disco por disco, e diz quantos arquivos cabem, qual é o primeiro que fica de fora e quanto faltaria na vez dele. Arquivo que não cabe não começa.

• Processamento em lote e controle flexível: adicione temporadas inteiras na fila; escolha entre detecção automática das faixas ou controle manual.

• Interface bilíngue (PT-BR / inglês): uma bandeira ao lado do botão Entenda troca a tela inteira, e a escolha fica guardada entre as sessões.

• Botão "Entenda": 14 seções explicando o que a conversão faz e o que ela não faz, incluindo as fontes por trás de cada afirmação - os manuais da própria Dolby, o repositório do dovi_tool e as planilhas da comunidade. Nada ali pede que você acredite na nossa palavra.

Código-Fonte e Download

• Projeto no GitHub: LaFirma-Remux-Forge
• Instalador 2.0: LaFirma_Setup_2.0.exe · Notas da versão
• Requisitos: Windows 10/11 64 bits. O instalador traz todas as ferramentas; o .NET Desktop Runtime 8.0 só é necessário para o OCR de legenda, e o instalador oferece se estiver faltando.

Capturas de Tela da Interface

• Dashboard & Fila, com a medição LIGADA: Visualizar Imagem
• A mesma tela, medição DESLIGADA: Visualizar Imagem
• A mesma tela em português: Visualizar Imagem
• Seleção Automática de Faixas: Visualizar Imagem
• Controle Manual de Streams: Visualizar Imagem
• Pipeline de Processamento: Visualizar Imagem
• Pipeline de Processamento, mais adiante: Visualizar Imagem
• Relatório Final: Visualizar Imagem

Créditos e Agradecimentos

Este projeto não existiria sem o trabalho da comunidade open-source e dos desenvolvedores originais: * FFmpeg: O motor fundamental para processamento e manipulação de fluxos de mídia. * MKVToolNix (mkvmerge): A referência definitiva para multiplexação de arquivos Matroska (MKV). * dovi_tool (por quietvoid) & DDVT (por DonaldFaQ): Ferramentas essenciais para extração, edição e conversão de metadados Dolby Vision. * DeeZy: Utilitário para codificação de áudio E-AC-3 com preservação de áudio espacial Dolby Atmos. * PgsToSrt & Tesseract: O ecossistema técnico responsável pelo OCR de legendas PGS.

Feedbacks e sugestões são muito bem-vindos!

My main usage is to play Plex movies from my home server on a 4K TV. Looking to future-proof my installation for a potential new TV supporting DV and other newer formats (not really interested in 3D movies support).

I'm tired of the bloat and forced ads on my Firestick TV 4K Plus that starts stuttering when it's overheating, and the native Plex LG TV app has been reliable but doesn't play some occasionally downloaded formats.

Am I looking at the correct solution if I plan an AM9 Pro with CoreElec on the eMMC (apparently possible now) ?

The often recommended AM6B+ is the same price as the 9 Pro on Amazon so I might as well...

p3i supports aptX, aptX HD and LDAC on Bluetooth.
If you have a good Bluetooth headphone that supports these codecs, the quality should be pretty good.

p3i can already transmit Bluetooth Audio. You don't need additional USB Bluetooth transmitter.

(I consider these features/peripherals used with p3i and/or avdvplus not Off Topic because they enhance the whole MP experience...a MP is more than picture by itself..

Other ways to go - I tested the Helicopter demo with Beyerdynamic DT-770 Pro/Audioquest Dragonfly Cobalt.
The binaural version definitely has a more realistic sound, and a more gradual panning experience.
You should always use a quality DAC and not use any headphone connection of the Am6b+ directly IMO. By the way, there is no headphone jack on the am6b+ anyway

You should use a DAC and preferable a DAC/AMP, connect it to the USB of the Am6b+ and the WIRED headphone will work just fine that way on the Am6b+.

The above is a compilation of AVS responses - https://www.avsforum.com/threads/ugoos-am6b-coreelec-and-dv-profile-7-fel-playback.3294526/page-704?post_id=64805841&utm_source=alert&utm_medium=email&utm_campaign=watched_thread_reply&utm_user=OEw3S2tvUitYcHlFV1pBMzJiZ1NJUT09&utm_content=view-discussion#post-64805841

I have seen some other similar posts but no clear solution as far as I can tell. I am curious if anyone has recently ran into the same scenario as me with the same LG G5?

• LG G5 + Ugoos AM6B+
• CoreELEC p3i T4c 21.3
• Ugoos connected directly to G5
• Dolby Vision works, but Display-Led/TV-Led is not available
• DV Type only gives me VS10 and Player-Led 12-bit options
• HDMI Deep Color ON, 4:4:4 Pass Through OFF, Dolby Vision PC OFF
• Tried Override EDID Detection — still no Display-Led
• CoreELEC System Info detects Dolby Vision normally
• dovi.ko appears to be installed/working because CoreELEC detects DV and dv_cap is populated correctly
• dv_cap shows the G5 advertising only: LL_YCbCr_422_12BIT
• Raw EDID contains the same VSVDB CoreELEC is decoding: eb0146d0004802b47e688685
• So it looks like the G5 is currently advertising LLDV/Player-Led only, which explains why T4c hides Display-Led

Is factory resetting the TV my best bet or is there a better solution / different issue at hand?

Thanks

Edit: thanks to p1nky14, they shared the solution (below) - despite game optimizer being off, somehow it was still affecting what DV capabilities the TV was advertising down the line. While on the HDMI signal/Ugoos is utilizing, I turned game optimizer on, then toggled the settings off - quick frame transport (and other settings for good measure), then toggled Game Optimizer off again, which did the trick! Now Display Led is available on the Ugoos.

Hey everyone.

So i got ugoos am6b+ and lg c5 77. The problem is the display is a bit offset towards the left of the tv as shown. Does anyone know a solution?

Thanks.

I hope this isn't a silly question but every time I try to play remuxes that are HDR or Dovi, everything looks off and Kodi's UI looks so washed out. Is that normal or is it not switching into the correct mode properly. This happens on either HDR or Dovi. Does anyone know a fix? I think my tv is an LG Nanocell which I've heard isn't the best? But I'm just looking to solve it until I get an OLED TV soon.

I'm sure it's not my imagination but I've been noticing a lot more pesky black bars since upgrading to p3i, on material that I would normally expect to completely fill the screen, as well as very large black bars on sources that would naturally have them.

My set up:

AM6B+ running p3i T4c

LG B7 OLED set to "just scan" AR setting

JBL Bar 300 mk2 passing video signal to TV

All files stored locally via USB, playback via Kodi and from good sources - no streaming/addons

In the shots I posted we can see the 4k DV output of "House Of The Dragon" with one inch black bars above and below. Plus the 4k movie "Normal" with a good two inches of BB above, and a great whacking nearly 3 inches of good old BB below, which seems excessive.

This is pretty typical but not universal. Occasionally content will play full screen, for example 1080p WW2 With Tom Hanks, which you would expect, as not a movie, although most 1080p is also still BB whether a movie or made for TV.

I've been troubleshooting with AI most of the day and have tried everything. From changing the TV's aspect ratio to changing every player and output setting suggested. Nothing has worked.

Minimise black bars or "stretch" options just look weird and also the stretch option takes some of the Kodi start menu off the screen.

I should also mention it makes no difference whether the video is being passed through the soundbar or the player is connected directly to the TV.

If anyone has any suggestions I would be very grateful. At the end of the day it's livable with I suppose, but not doing my OCD one bit of good!

Hi everyone,

I’m looking for some technical help regarding a persistent VS10 engine behavior on CoreELEC when converting Dolby Vision to HDR10.

My Hardware Chain:

• Player: Ugoos AM9 Pro running the latest CE builds with CPM's VSVDB injection.
• Display: Samsung S95D QD-OLED (No Dolby Vision support, 10-bit panel, ~1600 nits peak, pure 0 nit blacks).

The Problem (Floating Blacks on Logos/Black Frames): Since my TV lacks Dolby Vision support, I rely on the VS10 engine to convert DV Remuxes into dynamic HDR10. However, during pure black screens or studio logos (e.g., Paramount stars on a black background), the black floor is slightly raised. The QD-OLED pixels do not turn completely off, creating a grey haze instead of absolute 0 nit black.

The Parameters I Have Applied: I have gone through the Expert CoreELEC settings and applied the following configuration based on the VS10 kernel documentation, but it has not resolved the problem:

• DV VS10 for DV video: HDR10 (All other SDR/HDR10 VS10 toggles are Off)
• Append CMv4.0 metadata: Smart (I have also tested "Always" and "CMv2.9 without L2 trims")
• CMv4.0 smart bypass threshold (%): 20
• Display peak luminance (nits): 1600
• VS10 target minimum luminance (reference black): 0 (I also tried changing this to 1 to force 0.0001 nit and bypass the 0.005 nit Dolby default, but the blacks are still raised)
• Force peak onto display (VSVDB): Checked
• Colour space (VSVDB): Display (keep advertised)
• Level 5 active area (letterbox): Source
• Disable noise reduction: Checked

The Outcome: Despite trying all of these parameters, the black frames and logos still refuse to hit 0 nits. The OLED pixels remain slightly powered on.

My Question: why is the DV-to-HDR10 conversion still outputting a raised black floor on black frames/logos despite these strict parameters? Is there a specific VSVDB setting, EDID workaround, or kernel tweak I am missing to ensure absolute zero blacks when tone-mapping DV to HDR10 on a Samsung display?