Posts by HansM

Quote from chewitt

Have you experimented with the HDMI ports the device is connected to on the TV? .. On modern TVs they are not all equal.

Yes sir. All 4 of them.

Even the LG G3 55" of a friend shows the same result with both Asus PN42 and RPi5. My friend owns a Homatics 4K Plus box running CoreELEC without the mentioned issues.

So I think I will use CoreELEC on Odroid N2+ for now. Fortunately I can keep using the Odroid of my friend as long as I need it.

I will try the nightlies now and then to see if this 'feature' has been fixed

Thanks for the suggestion chewitt!

So I bought myself a PI5 and experience exactly the same behaviour as seen on the Asus PN42 with Generic image. It doesn't matter if edid is created or not.

LG TV detects the Pi as PC and disables all kind of settings like the mentioned Clarity/TruMotion option which I really need for 4K HDR.

Sort of the same issue is discussed in RE: LG C3 OLED TV and Libreelect on the Pi4b - PC Mode Issue  MaxMustermann / dmsaudio

In short:

1. Power on TV and Pi (sequence doesn't matter in this case);

2. Play Youtube 4k HDR (@24hz), micro stuttering al the time and options for Clarity greyed out;

3. Use LG Homescreen to change the icon for HDMI into something else like Streaming Box or Bluray Player;

4. Play the same video, perfect stream. TruMotion is set to Cinematic or even Natural.

5. Switch to set-top box (TV channels);

6. Switch back to LibreELEC on pi and we are back at #2.

The same on the Asus PN42 with Generic LE. On the borrowed Odroid N2+ with CoreELEC no issues.

Thanks for any input, have a great day.

New development: Last night I borrowed an Odroid N2+ with CoreELEC 21.

Odroid/CoreELEC is not detected as PC, all image settings are available even after reboot/shutdown.

LG TV reports output signal: YCBCR444 8bit on 4K HDR.

Asus/LibreELEC does RGB on 4K HDR which the LG TV interprets as PC. Maybe the same on Pi but I don't have a Pi to test with.

Quote from noggin

This couldn't be as simple as RGB = PC, 4:2:2 YCbCr = Video could it? (Or infoframes flagging 0-255 = PC, 16-235 = Video levels?)

Is there a command line command you can run on a Pi 4B to report the HDMI output format being used - that might help add some information?

Thanks noggin, but I already tried 16-235 video levels in the settings. It doesn't matter.

More and more I think the problem is with LG OLED tv's and their detection methods of HDMI input signals.

As I mentioned earlier:

"It seems that after every start of LE and LG TV, HDMI4 input is reset to PC.

After changing the icon of the HDMI4 port on the LG TV, or even change one character of the name of the HDMI4 port, the desired settings are available again." -----> this is very strange imho...

smp is probably right and it is a bug in the LG firmware....

Thank you everyone!

My problem (LG G4, Asus PN42 mini-pc) is the same as dmsaudio (LG C3, RPI4) describes, just like MaxMustermann (LG G4)...

LG TV is the common factor here so let's wait for new firmware... Thanks all for your input!

Back to square one.

It seems that after every start of LE and LG TV, HDMI4 input is reset to PC.

After changing the icon of the HDMI4 port on the LG TV, or even change one character of the name of the HDMI4 port, the desired settings are available again. I don't have this issue with the set-top box of my Dutch ISP provider KPN connected to HDMI3.

So is it some kind of miscommunication between LE and LG TV? Who can tell...

I'm not.

@30 was just a first test as I mentioned.

My final whitelist is as recommended in the Wiki, without @60, @59,94 and @23.98. @24 is still in there.

As of today, I *HAD* the same problem on my LG G4.

After a lot of experimenting I came to the conclusion some signal is telling the HDMI port of the TV to jump into PC mode. Even the GUI at 1920x1080@60 jumped into PC mode.

Then I tried @50: no PC mode. tried @30: no PC mode. So started the whitelist with only 3840x2160@30: Happy times, no more PC mode!

Added all the other modes one by one and tested. In my case, the 3840x2160@60 and 3840x2160@23.98 modes on the whitelist were the culprit. Should be the same for 1920x1080 but didn't tried that yet...

Good luck with this 'typical feature' of your LG OLED TV.