Dolby Vision for Minix U22X-J (Max) and Ugoos AM6+

Development Development & Testing
1105

Hi, what actual settings can I look for to see under either CoreElec settings or Kodi settings to see if dovi.ko is actually “installed” correctly? Because I am having multiple audio/video problems. I think I should back up… I got my new Ugoos am6B+ today, installed the new “CoreELEC-Amlogic-ng.arm-21.0-Omega-Generic.img” file onto SD card using Rufus. Then stuck that dovi.ko file in the root.

  1. I guess my first question is: Did I use the right file? “CoreELEC-Amlogic-ng.arm-21.0-Omega-Generic.img”?

  2. If yes, is the Ugoos remote still supposed to work? Because it doesn’t and luckily my Sony TV remote is able to work with it otherwise I wouldn’t be able to navigate at all.

  3. What settings can I look for to see if I installed dovi.ko correctly and supposed to be working? Because all my DV files whether remuxed with FEL or just the basic streamed DV only show in HDR using PlexMod4Kodi, they never kick on the DV flag on my Sony X85J. I looked under Kodi Settings > System > CoreElec and the only thing I see that mentions DV is a slider that says “Disable DV support”. Is this right or should there be more?

  4. And am having audio problems too (static DTS-HD MA) which leads me back I guess to my first question. Did I use the proper file? I hope not because that would explain all the problems I am having… thanks guys :slight_smile:

1106

3.) In SSH terminal type command

journalctl -l | grep dovi
1107

Where is the SSH terminal please? I am noooob

1108

https://wiki.coreelec.org/coreelec:ssh

If any DV video plays as DV then it is working I assume.

1109

None of my DV files are playing as DV. I am having huge amounts of problems so tomorrow I will remove the SD card and start fresh with one of the known good nightlies instead of this final “CoreELEC-Amlogic-ng.arm-21.0-Omega-Generic.img” file. Perhaps this is where all my issues lay

1110

I’d check your HDMI cable. That version of the image you used is fine.

Included remote works via IR, I just use CEC though:

I have issues with BT on CoreElec, especially with not reconnecting once it awakens from suspend. I think that’s a library issue in Kodi vs the Android BT library.

1111

  1. Yes

  2. Can you pair the remote. If you can pair and then it unpairs upon reboot, do a hard reset.

  3. Try playing the file directly from a USB drive or via a network share. PlexMod4Kodi has issues.

  4. What is the audio problem? Static in the channel? No sound?

1112

… there’s no issue with PM4K. I’ve been using that since 20.3-ng-dv. In the PM4K thread many others are using that with the Am6b+. No issue.

Even in the “problem” log that was posted above, PM4K did everything it was supposed to.

It took the webstream generated from Plex server, and passed the URL onto the internal player to open. That’s the extent of PM4K’s involvement. What the internal player did with the webstream after has nothing to do with PM4K anymore.

1 Like
1113

Has CEC improved and/or does anyone have any thoughts on what might be necessary for this to improve?

1114

CEC can’t be improved since the bootloader is encrypted and bl301 blob can’t be installed. Suspend gives me problems so I configured the box to shutdown with the TV and let home assistant send a WOL packet to turn on with my reciever.

1 Like
1115

Tbf, CEC control is about the buggiest hot mess in home AV, IME.

Long live Logitech Harmony remotes! i’m clinging onto mine as long as I can, and hoping Logitech doesn’t shutdown the sync/programming infrastructure anytime soon.

1 Like
1116

This is my remote.conf for the UR-01. Basically the red power button is discrete on, and the black power button is the discrete "off (or rather suspend):

work_mode     = 0
repeat_enable = 1
repeat_delay  = 130
repeat_peroid = 120
release_delay = 20
debug_enable  = 1

custom_begin
		factory_code	= 0xff000001

		key_begin
				0x14 143 #wakeup
				0xff 116 #power
				0x13 139 #menu
				0x03 103 #up
				0x02 108 #down
				0x0e 105 #left
				0x1a 106 #right
				0x07 28  #ok
				0x58 114 #volume-
				0x0b 115 #volume+
				0x01 158 #back
				0x48 102 #home
				0x5c 164 #play/pause
		key_end
custom_end

The default remote.conf, the red power button is Power (on/off) and the black power button isn’t even mapped:

2 Likes
1117

So could this be fixed if we pleaded with Ugoos to decrypt the bootloader or make fixes this community could provide? They seem reasonably responsive

1118

I’m having some trouble with Profile 5 Dolby Vision on 21.0.

On some content (Shogun), it’s stutters, and gets worse when the OSD is called on screen. On other DV 5 content (Three-Body, not NF version), I get the DolbyVision logo, but the screen is completely black. Even the OSD does not show. Audio continues to play but video stays black.

Logs:

https://paste.coreelec.org/EQJWON

Edit2: Capturing a better debug log.

https://paste.coreelec.org/h6WRTF

1119

If the bootloader was unlocked the cec fix could be injected. Send them an email. Hell I’ll do the same. It’s unlikely they unlock the bootloader again but who knows.

1 Like
1120

Which platforms or ways to contact them are they the most responsive in

1121

Boot encrypt is a SOC feature that is enabled with an efuse, once it’s enabled it can’t be disabled. An unencrypted bootloader won’t load on a SOC with boot encrypt enabled.

1122

So what we need is a bootloader with the features we need, which they most certainly won’t be bothered with.

1123

Watch. I wouldn’t be surprised if popping that fuse irrevocably disables DV support within the SOC.:joy:

Wouldn’t put it past Dolby to make such a draconian requirement to get it…

1 Like
1124

Is the bootloader encrypted on the minux U22-xj boxes as well?