Honestly, I think at this point, the Plex team should just bite the bullet and say they are not interested in supporting older webOS versions before the 2018 models. No matter how complex the bug, if a team was actually interested in solving it, they should have been able to in 12 months, especially after being able to triage the exact version that introduced the issue.
I’ll ping @anon18523487 in case they hopefully prove me wrong 
Just got a mail from Plex. Not in response to this issue, but just a “little” heads-up.
Basically what they’re saying is that we, the LG people, are f@cked. Plex apps are at a point that they need a 1.18.x server version.
Not amused 
Let’s hope they’ll respond to this.
Just received an email from Plex stating that they will be increasing the minimum version of Plex Media Server required by player apps to [1.18.3] or newer.
So since we’re fked… do you have any good media server/player alternatives to Plex to recommend?
This was never going to be fixed. Doesn’t matter how hard we pushed. Plex Devs are not interested in fixing issues. We just get bombarded with new unfinished bug-ridden features so they can lure more customers on board.
I switched to Emby. Absolutely no issues. I will switch to Jellyfin (Emby clone) when they release an LG app.
Just want to add my voice here, I’ve been staying on 1.16 for the past year now because of this bug. Now that support will end for that version can Plex acknowledge the issue and give us an update on progress?
@anon18523487 pinging again… I think the latest news that PMS Server 1.16 will no longer be supported does warrant some level of communication for this issue, right? People who own these TVs seem to be utterly screwed now when it comes to Plex
I think I have the same problem, a temporary sidefix you could try is to load external subs, through the Plex WebOS player aka ignore the internal subs. Maybe that will help some of us. In any case, as paying contributors to Plex, we need better visibility to these issues.
I’m done with it.
Just contacted plex billing/subscriptions, claiming my money back for plexpass
Edit:
Finally someone woke up at plex. Requested some logfiles and a forum thread link.
A new spark of hope ignited
A question to all you guys…
Are you transcoding via hardware or cpu?
I just upgraded my unraid PMS to 1.21.recent and there is no buffering…
A few moments later I realised that there wasn’t any transcoding going on… Downgrading a bit triggered a transcode. After pausing i got the buffers again. Logs have been sent to Plex.
My TV app just started showing my server as unavailable due to version, updating now, but I’m guessing we’re screwed
Intel HW transcode.
Ended up using a Google TV Chromecast with plex app to avoid this bug on my main TV (Before I used a RaspberryPI with Kodi to workaround the bug).
Dammit, even my old PS3 didn’t had this bug. Every device at home works as intended if it is not LG branded while using Plex…
…while using Emby/jellyfin/or any DLNA server my LG tv just works out of the box.
@anon18523487
Any news??
We are dying here…
I do not have any news. Plex is aware of the issue and that the new requirement to use a newer PMS will affect some users.
Jamie from Plex asked me to attach my logfiles to this thread, so the devs would have easy access to them and have a complete overview of the issue. This afternoon (EU timezone) I’ll attach everything I have including a video of the buffering/glitching issue
@anon18523487
That is sad to hear.
is there anyway to get in contact with a developer / support staff ?
do they need anything from us?
I mean, we do not have a work around anymore and it forces LG/Plex users to search for working plex alternatives.
I sincerely hope Plex support staff will priorities this major issue for LG/Plex users.
You can always attach your logfiles. The more the merrier I guess 
I’ve upgraded to the latest version of the server when my client app required it, and haven’t experienced this issue since (not sure if I haven’t transcoded anything yet but I find that unlikely).
Jesus, just fix this ■■■■ already
A bit later than promised.
Finally got some time to dive into the PC and keep my promise to plex.
Attatched, a bunch of logs
(File removed)
(File removed)
(File removed)
And a preview of what it looks like when the issue occurs
