Own an LG TV or webOS device? Join our Forum!
Register now to gain access to our webOS user support forum. Once registered and logged in, you will be able to post a user to user support request topic to this site or reply to existing topics posted by other users. You can also take part in our other webOS user forums. You'll be able to customize your profile, receive reputation points, while also communicating with other members via your own private inbox, plus much more!
By Void Toast
Please consider adding a new menu for 2017 OLED's in HDR Game mode preset called "Static Tone Mapping" to picture options with a selection of 4000 nits (default) or 1000 nits.
The reason so many complain about dim HDR on 2017 OLED's is down to an overly tone mapped image, game consoles HDR titles are mastered in 1000 nits range, LG's default tone mapping is set to 4000 nits and because the consoles do not send any HDR metadata, LG tone maps 1000 nits content to 4000 nits. We know this is the cause as advanced tools like HD Fury Vertex can trick the TV into thinking it's 1000 nits content and give correct looking HDR (very complex thing to setup far beyond normal users).
This is entirely fixable by giving us a menu under game mode to force the TV to tone map to 1000 nits instead. If you read around online I'm almost certain this is what the special "Active HDR dynamic contrast = low" under Cinema mode does but this setting is not the same under any other preset. Maybe the "Active HDR" trick is not possible under game mode but forcing the TV to 1000 nits tone mapping is because the HD Fury Vertex can do it so the TV has the capability.
The 2018 models do not have this issue as they have "Dynamic Tone Mapping" under picture options so please throw us 2017 owners a bone on this, thanks.
(Yes game consoles could possible fix this by sending metadata but that's unlikely).
Youtube App on LG 55UF7709 behavior changed over time (scrolling vertically, jumping to a certain timestamp)By AndreasW
I am glad I found this board. Unfortunately the circumstances are not that great. I use my LG 55UF7709 (latest updates are installed) mostly for Youtube and streaming movies from a network storage. Second thing works great. But over the last couple months I see my YT app behaving worse and worse in the little things:
First it started with a different kind of scrolling. I believe after an update I just can't scroll vertically through the YT clips by only using the scroll wheel. This was alwasy working fine but know it is almost like I have to jump start the scroll with the arrow up/dow keys on the remote and than I can use the scroll wheel. Almost feels like it is blocked virtually even though the little red arrow changes its form which is telling me my scroll command is recognized.
Now since a couple of weeks (I think since the last YT app update) every time I use the red arrow to jump to a certain position in the stream the video will start from beginning - no exception.
Has anybody seen these issues, too? Isn't there a official support channel I can use? Looks like LG does not feel responsible for issues with the apps.
Best and Thank you!
I am new to the community and have an exasperating problem. It is on an
OLED65B7A unit. When I pause my streaming service, after about 3 minutes I get the fireworks. Trouble is, about 3 minutes after that, it kicks out of the fireworks to a screen that says, "Please check the TX input signal." That stays on for quite a while.
Is there a way to prolong that fireworks screen until I resume streaming?
Thanks in advance!
By Bob Wolkowitz
I have two LG OLEDs. I have given each a name in the WebOS. Occasionally when a TV is powered on, I am first requested to enter the TV name along with the dialog to enter text with the on screen keyboard. I can enter anything and it is accepted and I get past that screen and then normal operation follows. This happens on both TVs albeit only occasionally. It is a real nuisance when this happens and I see no need for this.
Has anyone else experienced this and if so, is there a solution to disable this behavior? Is there some setting that I have missed?