Amlogic-NO discussion

Creator44 · 1 June 2026 19:34

Yes I know I will try to add debug info soon if the new dovi.ko does not fix the problem. I added the most info I found out myself. Thanks for your work!

Creator44 · 2 June 2026 03:01

@Portisch Ok, I found another solution to my problem. It seems that when my GUI is at 1080p@120hz (for more smoothness), I get the DV block screen on the tv but if my gui is at 1080p60hz then it’s playing correctly.

I got debug logs of both situations but by checking it myself I did not see anything different between the two. Maybe you can see something that I did not see?

kodi dv ok gui at 1080p60:

kodi dv black screen gui at 1080p120:

1080p@120 worked fine on am6b+ with corelec NG.

Also, I use AM9 Pro, a Yamaha AVR and Sony TV. I tried direct to tv and it did not change the problem.

Thanks!

Portisch · 2 June 2026 06:38

This is your bit:

github.com/CoreELEC/common_drivers

drivers/media/vout/hdmitx_common/hdmitx_edid_parse.c

5.15.196_20260225


      
          				dv->sup_yuv422_12bit = dat[pos] & 0x1;
          				dv->sup_backlight_control = (dat[pos] >> 1) & 0x1;
          				pos++;
          				dv->sup_global_dimming = (dat[pos] >> 2) & 0x1;
          				dv->backlt_min_luma = dat[pos] & 0x3;
          				dv->tminPQ = dat[pos] >> 3;
          				pos++;
          				dv->Interface = dat[pos] & 0x3;
          				dv->parity = (dat[pos] >> 2) & 0x1;
          				/* if parity = 0, then not support > 60hz nor 8k */
          				dv->sup_1080p120hz = dv->parity;
          				dv->tmaxPQ = dat[pos] >> 3;
          				pos++;
          				dv->sup_10b_12b_444 = ((dat[pos] & 0x1) << 1) |
          					(dat[pos + 1] & 0x1);
          				dv->Gx = 0x00 | (dat[pos] >> 1);
          				pos++;
          				dv->Gy = 0x80 | (dat[pos] >> 1);
          				pos++;
          				dv->Rx = 0xA0 | (dat[pos] >> 3);
          				dv->Bx = 0x20 | (dat[pos] & 0x7);

So don’t use higher than 60Hz!

And read Wiki how to provide logs:

Crunt · 2 June 2026 10:14

Whilst watching DV 8.1 content, starts fine but then i keep getting a black screen retrigger with dv logo, i then tried something else with DV 8.1 and dont get the black screen retrigger anymore.

https://paste.coreelec.org/RunninDollars

Portisch · 2 June 2026 10:57

As any other user told everywhere a sample to reproduce is easiest and the only solution…

Crunt · 2 June 2026 11:23

Sample - 290.67 MB file on MEGA

Creator44 · 2 June 2026 13:21

Ahhhh you are right I did see the parity difference between the two tvs! Guess we know what that bit is now.

Thanks!

As for the logs, what did I do wrong? I sent using the hastebin method as described in the wiki page?

Portisch · 2 June 2026 13:46

Portisch · 2 June 2026 19:04

No problems, on two systems.
I guess a local hardware issue like bad cables.

Crunt · 2 June 2026 19:09

But everything else plays fine? the cable is pretty new

Crunt · 2 June 2026 19:17

Tried different HDMI, no difference

pete · 3 June 2026 01:23

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

Upgraded to CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20260602-Generic.img.gz

Cleared DB and tried a scan and it is not working. DB is still messed up.

Downgraded to: CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20260529

pete · 3 June 2026 01:41

This is CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20260529

This is what I normally see and what I do not see with latest upgrade.

BTW VNC is working well.

atirage21 · 3 June 2026 01:54

You must adjust of provider of information. After build of 29 may is empty as default.

coreelec-user · 3 June 2026 08:07

The Numeric pad popped up to change “eMMC Speed Mode” cut the most part of the confirmation code, which makes it very hard to see the code and input the code correctly. I tried like 20 times and still not be able to input the code. Can the dialog be adjusted? Or remove the confirmation at all? I don’t see why the point to confirm? The “HS200,HS400” option is compatible with the “HS200” option, right?

bluesea · 3 June 2026 08:13

You can start typing after changing the skin font back to default and use default language english.

coreelec-user · 3 June 2026 10:06

That was what I did, but it didn’t work for me. With “Arial based” font for Estuary, I can see a little bit of the confirmation code, but with the “Skin default” font, the confirmation code is covered completely.

vpeter · 3 June 2026 11:37

Make a screenshot.

Crunt · 3 June 2026 17:57

Narrowed down the problem to 24hz, plays fine on 23.98hz

pete · 3 June 2026 19:55

Thank you @atirage21 I did notice that the provider was empty on the last few attempts.