I’m currently using 7.9.0.8439 (fe3a0d4b) and have reproduced the issue. Passthrough is False, Refresh Rate Switching is False. I’m available to provide more information and logs if needed.
logs.txt (253.0 KB)
Oh, it seems we have separate issues…
They are probably related somehow. Exoplayer 2 sucks.
hey @sixones. here’s my logs. passthrough support was set to “auto” for both plays. As for refresh rate switching, that was enabled for the first play and disabled on the 2nd play.
170119_shield_plexlog.txt.txt (1.3 MB)
edit: please let me know should you require more logs.
Hi!
Glad to know people are having the same problem as me, bad that it is a problem. I also encounter this on my Shield, chromecast and android phone.
If you need some more logs let me know. I have found that playback is fine on the Ps4 and on my Samsung TV app.
This happens both on ethernet and WiFi which I thought might be the problem at first as the ps4 and TV use 2.4ghz whereas the chromecast and shield both use 5ghz.
Updates on this would be great as I’d originally bought the shield for use with plex.
1 Like
Yep. I can confirm xbox 1 and ps4 work fine.
I am getting this on my ASUS ZenPad S 8.0 (Z580C) using the latest android app, the only way round it is to force a transcode. It doesn’t seem to matter what the media container, codec, bitrate is but typically I’m watching 720p HEVC at about 1-1.5mb. Strangely enough the issue doesn’t happen on my Samsung S8 with the same content/wifi etc
I had this issue also. Plex worked fine on my IOS devices on the same network. It was firestick and my TV that didnt work. I was able to make the problem go away by turning off security.
@sixones It appears when I stream to the shield, and it is direct play, the stream does not build a buffer and will “stutter”. When I force a transcode, i can see a buffer being built from server and client side.
@sixones were you able to gather anything from the uploaded logs ?
This problem is there since Exoplayer v2. If you try Plex client version 6.12 where it still has Explayer v1 you won’t probably have this issue.
Seems google did some changes to video buffering or something which Plex devs still cannot fix.
I have the same issue here. Unfortunately if I use an older version of the player it does not output my audio in Dolby Atmos - it transcodes into AAC.
This is a lot of technical jargon that I don’t really understand. But what I do understand is that this connection to server not fast enough issue has been going on for over a year, on several different platforms and it continues to go on through a few server upgrades. No disrespect, but I would think this maybe should have been resolved by now. because this issue renders Plex virtually useless.
4 Likes
Agreed - Plex is now unusable for me on the nvidia Shield. No workaround and no fix so pretty frustrating for an app that I pay for!
How can i locate this version of the plex client? And how to install it?
Edit: Also, yeah. Plex on Shield is completely useless at the moment and its really frustrating -.-
maaaan.
Just look here around I am not very familiar here either 
well, i tried 6.12 and while videos appeared to be playing a little longer they did unfortunately also eventually start giving me the “connection to the server is not fast enough” message eventually. 
If that’s the case, then you probably have a different issue. You might be the one person who’s connection really isn’t fast enough, meaning there’s probably a network problem of some sort. Everybody else having this problem is having a client issue with a useless fake error message that isn’t related to the server or the network in any way.
Maybe check your logs, and make a new thread with them to see if there’s something else going on.
It’s not a fake message. It gets really slow then freezes. This is on Fire TV.
It’s a fake message because your server is fast enough, and your connection is working, it’s just the client that’s broken and giving an incorrect error message. If you downgrade to 6.12, switching from ExoPlayer v2 to ExoPlayer v1, then suddenly you don’t get the error message any more, because there was never anything wrong with your server or connection in the first place.
