I just created a new Linux box with Plex docker in it (coming from PMS in Windows 10) and it has the same exact issue!
Itās been 462 days since Plex became aware of this issue, still no fix.
Four. Hundred. Sixty. Two. Days.
3 Likes
Maybe they will fix it at 500 days /sarcasm
1 Like
Thatās because this is a client side issue. Not a server side issue.
We are still waiting for an Android TV client update to address these issues.
Yes, Iām aware. I just thought sharing my observation in case Plex somehow fixes the client side issue by implementing something server side. But thatāa proven to be untrue now.
nVidia just released a test update (info on the SHIELD forums) for the SHIELD OS. For me, I can confirm, after updating to it ā all of these issues instantly vanished. Mission accomplished.
1 Like
Update:
I installed the āSHIELD Experience Upgrade 7.2.3+ Test Imageā and it solved all my issues.
Plex, Please make a sticky for users experiencing this issue.
They simply need to enter their Shield serial number here to retrieve the update.
Enter Here:
https://surveys.nvidia.com/index.jsp?pi=ba7320153df027d1e7ff8991eb3a8173
Plex really need to work with their community properly and engage. Nvidia have given me more info on Plex bugs than Plex doā¦ itās incredible.
4 Likes
Oh my God, this is really good news. I think Iām gonna cry!
1 Like
Yes, also have been testingā¦all seems fine for nowā¦
1 Like
This is great news!
How long did it take for the update to show on in your device after putting in your serial number?
Did this but it didnāt work for me. Donāt get your hopes up guys.
5 days, but the holiday was in there
What is your current version and build now?
Put your serial number in and wait for the engineering build to be pushed down to your shield. it will not be instant. Could take a couple of days.
It Does solve the problem.
Right. I think he mightāve just been impatient and expecting that the upgrade will be pushed down right away.
Yea I noticed this happening a lot. WiFi, routers, switches etc. some at the time of writing seem almost convinced they resolved it (which of course they didnāt).
just adding my 2 cents to this. latest version of plex for FireTV and still getting the error at random. when looking at the logs from the server and the FireTV it just looks like at some random point the plex app just doesnt ask for the next chunk of videoā¦so the server doesnt send itā¦then eventually exoplayer/plex gives the generic message when it hits the end of the last chunk. as others have confirmedā¦file types make no differenceā¦it has destroyed the plex experience for my local LAN watching and all my external clientsā¦
3 Likes
Had the update from Nvidia pushed to my shield last night. So far so good. Will update if the issue returns.
Right. We were talking about mainly about the Nvidia Shield update though. The issue being fixed in the Nvidia Shield is just a proof that this is a client app issue.
A Shield Experience update wonāt fix this issue. The issue is random, so even if you donāt see it for a week of solid use, it doesnāt mean someone else with the exact same components and software version isnāt seeing it daily.
I thought for a second that one of the recent client beta builds fixed the issue, but nope. Still here, even with the latest May 31 update.
I havenāt seen any solid info showing that anyone at Plex has actually looked into this from a code perspective or made any changes whatsoever to address it at all in the past year. Iāve asked numerous times in public and private for a destination to send logs and have gotten nothing but silence.
