Sent u a PM with logs
//Lasse
Sent u a PM with logs
//Lasse
This topic was automatically closed after 90 days. New replies are no longer allowed.
Pertinent details are mostly in the link above. But below I have updated some version details.
Plex Server Version: 1.14.1.5488
Plex Player Version on TV:3.82 ( I am not home currently so not 100% of the full version number) Will update tonight.
TV: Samsung QN65Q8FN
Software Version: T-KTM2AKUC-1153.1, BT - S
Firmware: 1203.3
I will double check some of the updated version numbers when I get home as I might be slightly off on the TV Firmware and Software version but they HAVE been updated recently.
I wanted to Report that the “Network Connection” black screen is still occurring but since Plex has been updated the issue has worsened.
Now, when this issue occurs you cannot navigate and close down Plex nicely, you have to hold the back button to close it. Then it launches fine.
@sLumpy Hi Slumpy, just tagging you to ensure the update is received ![]()
Same here, Samsung Q9FN
I realise this is somewhat late but thankyou for this. This error is popping up constantly on my Plex app with Samsung QLED 4K HDR TV, even when i exit the app via the profile drop down, still isn’t cleanly shutting the app down.
Most times I would just come back to the app and be able to still move the highlighted selection box behind the error window to manually exit, but just lately the app wasn’t even responding, so the long hold on the back button of the remote worked, even easier than use the exit in app!
I, too have looked and tried for months the different recommendations, but the box keeps coming back. It only shows with 4K movies on Plex. 1080P of the same movie has no box and plays perfect. So Plex & Samsung QLED 4K HDR TV & Network have incompatibility somewhere. I’m thankful Shield TV works. Just wish the Samsung Apps would work…
@sLumpy Any progress on this bug? After the last Plex Update this issue now forces you to close out Plex “hard” with a long press and re-launch.
So it seems something was changed from the previous release which has made it worse in a way.
I don’t bother trying 4K content as the Plex App on Samsung is unable to play it without buffering constantly so I cannot confirm nor deny reports that this only happens with 4k. Sure would be nice to have this resolved as well… my network and Media server are overkill for a home network so there is no way this is a bandwidth or CPU issue.
Back to the black box issue, I can say it is 100% reproducible with 1080p, 720p, SD content. In fact I’d venture to say it is not related to the content at all as the issue is when you start up Plex after the TV has been shut down. On restart of Plex it works fine for all content I am using.
+1
Have exact same issue on 2018 Q8
@sLumpy and anyone else following this thread. Version 3.90.2 just came out and I do believe it has fixed the black screen issue! Going to run through some tests but here is hoping what I saw wasn’t a one off.
Now if they could only fix playing 4K movies 
@sLumpy Unfortunately, 3.90.2 did not fix the network lost issue for me, eventhough the release notes mention it.
Multiple threads on this forum address the same issue. I post my experience on this thread Plex for Samsung Network Connection Lost error
4K is working for me now. Direct play if using AC3 5.1 and transcoding audio only if using TrueHD audio which as far as I know is not supported by my Samsung.
I’ll have to do some more testing as I mentioned. I did shut down the TV a couple times last night with no sign of the network black box.
Promising! I’ll give it a try.
Sadly it was a one time thing… the network black box is back all the time now 
We have an internal issue logged and a potential fix for this. I’ll be looking at it in the next few days.
@slumpy doing gods work my friend! once this is fixed many a geek will rejoice! lol
Sounds great. Keeping my fingers crossed
Found another case where the black box stays up. I put in a fix for it and managed to sneak it into our next release. It’ll be out after Samsung approval
@sLumpy Out of curiosity how long does that usually take?