SoC S5 S928X

Here you go.

No dovi.ko file in storage, DV files playback as HDR10.
https://paste.coreelec.org/LeapsBreathed

ugoos.am8.dovi.ko renamed to dovi.ko in storage, DV files switch TV into DV mode but just display a blue screen.
https://paste.coreelec.org/DrivenTulips

Oct 20 07:14:18.484775 CoreELEC dovi-loader[1194]: filename:       /storage/dovi.ko
Oct 20 07:14:18.484775 CoreELEC dovi-loader[1194]: description:    Amlogic Dolby Vision Driver
Oct 20 07:14:18.484775 CoreELEC dovi-loader[1194]: license:        AML
Oct 20 07:14:18.484775 CoreELEC dovi-loader[1194]: vermagic:       5.4.210-android12-9-08157-g5e16466dfeb7-dirty SMP preempt mod_unload modversions aarch64
Oct 20 07:14:18.484775 CoreELEC dovi-loader[1194]: name:           dovi
Oct 20 07:14:18.484775 CoreELEC dovi-loader[1194]: depends:
Oct 20 07:14:18.575154 CoreELEC kernel: dovi: disagrees about version of symbol module_layout
Oct 20 07:14:18.575341 CoreELEC kernel: please rebuild ko: dovi
Oct 20 07:14:18.575390 CoreELEC kernel: dovi: module license 'AML' taints kernel.
Oct 20 07:14:18.575436 CoreELEC kernel: Disabling lock debugging due to kernel taint
Oct 20 07:14:18.575477 CoreELEC kernel: dovi: no symbol version for register_dv_functions
Oct 20 07:14:18.579200 CoreELEC kernel: *** amlogic_dolby_vision_init dv: s5 ***
Oct 20 07:14:18.579322 CoreELEC kernel: *** register_dv_multi_stb_functions.***
Oct 20 07:14:18.579368 CoreELEC kernel: Creating DV mp success
Oct 20 07:14:18.579412 CoreELEC kernel: Creating DV mp success
Oct 20 07:14:18.579455 CoreELEC kernel: enable DV HLG when stb v2.6. policy 123
Oct 20 07:14:18.579497 CoreELEC kernel: efuse_mode=0 reg_value = 0x0
Oct 20 07:14:18.579540 CoreELEC kernel: dv capability 7

dovi.ko get loaded and SoC looks support DV.
All your media is Profile 8?
You might share a cut sample as there were issues with P8 in past.

Yep but I don’t think it’s the correct dovi.ko for this box. The one I’m using is the ugoos.am8.dovi.ko posted awhile ago.

No, this is media that plays perfectly fine on a S905X4 device in Dolby Vision.

This is a test file I’ve tried:- Downloads Page - Demolandia

It’s a Profile 5 video, without dovi.ko it plays back with purple and green colors and with dovi.ko again it switches to Dolby Vision on my TV then just a blue screen.

No, dovi.ko is correct. Correct kernel version and for S5.

Run fw_printenv hdr_priority and fw_printenv | paste

fw_printenv hdr_priority returns:-

## Error: "hdr_priority" not defined

fw_printenv | paste
https://paste.coreelec.org/ProteusRisotto

bootargs=init=/init console=ttyS0,921600 no_console_suspend earlycon=aml-uart,0xfe078000 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 loop.max_part=4 scramble_reg=0x0xfe02e030 otg_device=0 logo=osd0,loaded,0x00300000 vout=2160p60hz,disable panel_type=lcd_1 hdmitx=,420,10bit hdmimode=2160p60hz hdmichecksum=0x96390000 dolby_vision_on=0 hdr_policy=0 hdr_priority= frac_rate_policy=1 hdmi_read_edid=1 cvbsmode=576cvbs osd_reverse=0 video_reverse=0 irq_check_en=0 androidboot.selinux=permissive androidboot.firstboot=0 jtag=disable disable_ir=0 androidboot.bootloader=01.01.230824.140247 androidboot.hardware=amlogic mac=90:0E:B3:6D:72:1D androidboot.mac=90:0E:B3:6D:72:1D androidboot.wificountrycode=US androidboot.serialno=tyson80966011c740090b

Try fw_setenv hdr_priority 0 and reboot.
And maybe fw_setenv dolby_vision_on 1

Thanks, tried both, rebooting after each and no change. The TV still switches into DV mode and I get a blue screen.

Before try with fw_setenv hdr_policy 1.

If still not works:
In Kodi enable only component video and video/audio timing and enable debug.
Then start a ssh session and run:

dmesg -c
echo 3 > /sys/module/aml_media/parameters/debug_dolby

Then start a DV video for 1-3 seconds until you see the black screen - really short only! Stop again.

Then share the results by:

cat /storage/.kodi/temp/kodi.log | paste
dmesg | paste

cat /storage/.kodi/temp/kodi.log | paste
https://paste.coreelec.org/DigginSeparate

dmesg | paste
https://paste.coreelec.org/BelieveRatty

[  147.268981@0]  AMDV: sink on,cap 0x1,vd1 on,vd2 off,osd on,vf 00000000487123e7 0000000000000000,toggle 0 2
[  147.268995@0]  AMDV: [inst1 vd1]dvbldec get 00000000487123e7(0,index 1),fmt -1,aux 000000007e68cc92 190,el 0
[  147.269093@0]  AMDV: [inst1]meta(352), pts(1) -> md(194), comp(1800)
[  147.269103@0]  AMDV: dovi->AMDV_OUTPUT_MODE_SDR8, cap=0
[  147.269109@0]  [amdv_parse_metadata_v2_stb] output change from 1 to 4(0, 00000000487123e7, 0)

It change mode from AMDV_OUTPUT_MODE_IPT_TUNNEL to AMDV_OUTPUT_MODE_SDR8. No idea yet why this happen. Will need to search a bit in code.

We got told the 4G version of the X10 does not support DV but the module loads and show it should work. Playback does start also in DV mode:

[  147.000418@0]  AMDV: [inst1]update src fmt: NONE=>DV, signal_type 0x0, src fmt 0
[  147.000430@0]  AMDV: dovi->AMDV_OUTPUT_MODE_IPT_TUNNEL

Thanks for taking the time to investigate this, let me know if there is any more information you need or testing you need me to do :+1:

I see same behavior in dmesg here with AM8. With P5 it switch from DV/SDR/DV/SDR/DV… until it end up as DV.

On 1080p the Player Process Info show wrong information SDR 444, 8bit but Vertex shows me correct DV-LL 422, 12bit. So this info isn’t ā€œtrustfulā€ at all.

Does OSD show up on your device or do it stay black while DV is playing?

If it’s the X10 4G variant you might return it as we got told ā€œonlyā€ the X10 8G does support DV. But I would not see now why this should be the case…

No OSD shows up just a black screen.

I have X10 Pro 8 gig.

I think a remember having to change a setting In Android.

Reboot from eMMc/ nand in CoreELEC

In Android settings
Screen Resolution

Check that you have HDR policy set to
Adaptive Hdr

And HDR Priority set to
Dolby Vision

Yep, I have that set.

I have no options in Android that refers to Dolby Vision :frowning:

Thanks for the suggestion.

Hmmmmmm

No Dolby Vision settings in Android…

Thats not good…

Maybe is best to return as you indicated earlier…

So after opening the box and removing the heatsink unfortunately it’s not the J or K variant of the chip :frowning:

Strange, because the DV capability say 7, this is for DV. Maybe the fuse is burned but the licence not!?

Minix confirmed on their forum that the S928X will not support FEL, but convert it. It’ll probably only decode the RPU and convert it to 8.1 like Dune does.

1 Like

Minix claims Fel is hardware based but we know that’s not true.

1 Like