Sorry I do not have an update.
Can you ask devs for one please?
Alternatively, can you undo the updates to the version before the app broke please?
I would also like to know if the devs can be asked for some kind of update on progress.
We are approaching multiple months of this issue. I have been able to replicate this issue on multiple Samsung TVs at multiple locations. This is a major issue on one of the largest TV manufacturers in the world.
If there was an update I would tell you. I’m sorry the cause has not been figured out yet.
I’m another one with the same issue. My Samsung TV used to work perfectly fine with my Synology NAS and Plex. I cannot watch a thing. Please advise.
It sounds like they arent working on a fix, were about 2 months from the start of this ticket + this issue was plaguing me for a few months before i wrote in.
As a ‘temporary’ fix, i’ve been casting from my phone to the tv - to use that as a ‘player’. its a debilitating experience for a main TV, and you wont be able to do that if you updated to the new iOS they put out. (casting is broken on the new iOS release, no word on a fix for that either).
Sounds like that could be true. Given the limited number of Samsung TV users, I’m assuming they would have to revamp their existing coding pretty extensively, and they don’t see it as a high priority project to fix.
I have a frame at home and tried to replicate tonight to try and help out on this one. Unfortunately (fortunately? Not sure if this is a good or bad thing 
) I was able to play everything I tested just fine with no issues. Does anyone have any suggestions here on anything I might be able to do to get it into the state that you all are seeing? My model is a 2019 55" frame. The OS version is 1500.5 (showing no updates available) and my plex client version is 5.64.1 from 4/22/25
Hey @McWanke - Thanks for trying to replicate this issue on your end.
I am using a 2022 55” frame TV. TV software is 1661, which it says is current (found under Settings > All Settings > Support) - not sure why our TV OS versions are different.. Perhaps different model years have different levels of OS support.
I can also confirm my Plex client is the 5.64.1, latest version, updated 04/22/25.
Please let me know if I can provide logs or any other information to assist troubleshooting this issue, happy to help any way that will contribute to a resolution.
EDIT:
I just attempted to play a few types of content, and I was unable to get H.264 or HEVC Direct Play stream to start - same issue as the original post.
Across multiple tests on different media files (especially ones i’ve confirmed direct play flawlessly on other clients), I was actually able to get one H264 in an MKV container to start, albeit this one was a Direct Stream Video with Audio Transcode. Not sure if this points to some kind of Direct Play issue, or if this was simply a fluke.
Just curious as I went back and re-read the original post - is this only an issue with direct play? Will the device playback from a server with a transcode (esp one of these H.264 files that won’t direct play)?
Thanks for the follow up @McWanke - I just did some more testing on the client.
First, I tried some files that Direct Play flawlessly on other clients, but have failed on the Samsung OS - but I changed their video settings in the playback UI to force them to transcode to see if it could circumvent this issue, and potentially identify if Direct Playing was a part of the issue. The stream was successful!
Here’s an example of one of the Transcoded streams specs:
1080p (h264) → 720p (h264) (Hardware Transcode)
English (DTS-HD MA 5.1) → AAC (Transcode)
Subs: English SRT (burn in)
While its good to have a successful stream, this is - of course - less than ideal. But if we can assume Direct Playing is causing the issue, then perhaps degrading the resolution isnt necessary, and direct play can simply be disabled. I tried a new stream - again, one that direct plays perfectly elsewhere (and has direct played on Samsung OS in the past) - but this time pausing the stream in the playback UI, and then unchecking “Allow Direct Play” in the settings. This also worked. Although I had to be fast, because the nature of this issue is that it loads a black playback screen for about 10 seconds then crashes, giving the error.
The specs from that stream:
1080p HEVC Main 10 (Direct Stream)
English (AC3 5.1) → AAC (Transcode)
This seems to give some weight to an issue of Direct Play in the Samsung OS, but my testing sample size has been small so far. It could, for example, only want to play nicely with AAC audio - as it keeps forcing transcodes to that audio codec. Who knows?
Let me know if this is helpful, happy to provide any information I can.
EDIT: These ‘fixed’ streams are quite fragile, doing something as simple as seeking on the playbar will cause a crash and the “unknown playback error” dialog to pop.
Can you grab some logs when you’re attempting to direct play something and it fails? Let me know around what time the error happens too so I can correlate timing in the logs.
Looks related to the issue I opened ( Media stops playing after a while ).
Hi @Moussa - the logs I sent over to you via DM on July 20, 2025 will contain this. I actually cleared my logs completely, then replicated the error, and then sent those logs - in hopes of making the error easier to identify with less other noise. Let me know if these logs are insufficient and I will send over a new batch.
FYI - dragging out resolution on this is enough to make my Plex media server essentially unusable, and will result in members leaving Plex. Please provide some sort of an update as I am prepared, but prefer not to leave Plex.
I am getting a similar issue when my audio transcodes but my video is direct playing; Overzealous client asked for end range of 899247, content size is 288248; we'll clip. fills up my logs and the TV starts buffering with no chance of stopping. Both the Samsung TV and Plex are up to date and on the same network 
Hey @Moussa - were the logs sent over DM productive in assisting with this issue? Let me know if anything further is needed
Please advise. It’s been three weeks without a reply from Plex. Clearly this is not an issue Plex appears to have interest in solving. Please prove me wrong - let the community know what Plex is doing behind the scenes to fix this issue.
