Posts by Da Flex

He will not benefit from selecting a separate audio device, because HDMI is his only digital audio output on the NUC.

The NUC does not allow to use Thunderbolt as an audio-only device, so it's not available as Kodi audio device.

I'm reading here for a while, but I never heard about such a routing option. Buy an HDMI audio splitter and go optical to your receiver.

I suggest to start the RPi with your preferred HDMI mode, defined at config.txt.

Quote from chewitt

I suggest upstream translators don't do a half-arsed job with their translations. It's the correct and darn sight easier approach

I always try to think from users perspective while programming: When LE just cashes, users think you're the bad boy. When LE doesn't crashes and pops up a toast "Incomplete translation / skin", then users know the real bad boys, and can address them. Isn't that great?

It's worth to program all the if's and then's, because bad translations and skins will never die. Doing some tests before allowing an add-on to be uploaded might help, too. You already do add-on quality control to avoid illegal stuff.

Quote from yossigo

So basically the issue is HDMI needs to be connected only *after* Kodi is up.

Put tvservice -p into autostart.sh.

If this is not successful, post your current config.txt.

Try this settings at config.txt:

hdmi_ignore_edid=0xa5000080
hdmi_force_hotplug=1

Quote from mglae

A bug in resource.language.el_gr causes Kodi to crush in certain skins.

Yes, a combination of custom skins and translation files is a possible cause.

@ LE developers:

I suggest to rework the LE code to make it more error-tolerant against incomplete skin / translation files. LE shouldn't crash in such cases.

It's not the Greek language, your custom skin just needs an update to work on LE 9.x.x (missing texture files):

2020-03-21 15:00:48.704 T:140011197126848  NOTICE:   load skin from: /storage/.kodi/addons/skin.aeonmq8 (version: 2.9.0)
2020-03-21 15:00:49.116 T:140011197126848 WARNING: Trying to add unsupported control type 1
2020-03-21 15:00:49.161 T:140011197126848 WARNING: Previous line repeats 3 times.
2020-03-21 15:00:49.161 T:140011197126848   ERROR: Control 9000 in window 10000 has been asked to focus, but it can't
2020-03-21 15:00:49.379 T:140010747717376   ERROR: DoWork - Direct texture file loading failed for resource://resource.images.recordlabels.white/
2020-03-21 15:00:49.383 T:140010756110080   ERROR: DoWork - Direct texture file loading failed for resource://resource.images.studios.white/

If you want maximum stability, use the default skin.

This hardware situation has some unknown factors. I suggest to try a full desktop Linux first (like Ubuntu on DVD or USB stick). If such Linux is HDMI-visible (maybe only in Live mode for testing), then you have a chance to install LE.

There are some RPi 4B reports about 5GHz problems when using internal WiFi.

If you're an 5GHz-only user, then activate another frequency band on your router.

My theory about this issue is higher energy consumption at 5GHz, and the need of developing a proper energy management. I still have no confirmation for this theory, but it looks like they are working on it.

I had a look at the Argon ONE install script. The location of argononed.conf is wrong. Move it to /storage:

mv /storage/.config/argononed.conf /storage

Quote from fyrstyk

Log attached.

You're still using a custom skin, but it's important to use the default skin to avoid any EGL scaling errors.

I'm no Hyperion user. By just reading here, it looks like the add-on needs a fix to work with RPi 4B. Maybe some higher resolutions lead to approximation errors, resulting in wrongly triggered lights. Just my 5 cents.

Quote from micj1420

Doesn't work. The cable is the original one (Official Raspberry Pi MicroHDMI Cable) sold by The Pi Hut.

I wouldn't count on that "official" cable too much (source).

Your TV seems to be a new one, so it shouldn't be on the list of problematic old TV's (which need a workaround at config.txt).

I would buy another microHDMI cable (2.0 or 2.1 standard), and remove the workaround at config.txt.

The list of provided screen modes looks OK, I think the cable is just too slow to deliver them.

The HDMI cable has to fulfill HDMI 2.0 or 2.1 standard to work on 4K devices. If your monitor is not 4K, then it's not a proof of complete function. On a 4K device, data transfer will speed up.

Any results when using the described setting at config.txt? It's a proved solution for many problematic TV's.

OSD could be part of the problem, because it looks like EGL doesn't scales OSD right.

If you haven't activated logging yet, then you can do so by creating /storage/.kodi/userdata/advancedsettings.xml:

<advancedsettings>
    <loglevel>2</loglevel>  
</advancedsettings>

If you can't get the URL, then shutdown LE, remove the microSD card and manually copy kodi.log by using a PC with microSD card reader.

PS: Use the default skin for all further tests!

Quote from PadreMartini

Code

tvservice --explicit "CEA 16 HDMI"

If this screen mode works, then you can make it permanent by adding this lines to config.txt:

hdmi_ignore_edid=0xa5000080
framebuffer_width=1920
framebuffer_height=1080
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16

Remove this, because 4K / 60Hz content is not in common use, and it can cause trouble:

hdmi_enable_4kp60=1