I do think that its two different problems, but the “not fast enough” message seems too generic. I am sure my connection to the plex server is fast enough, and like almost everyone else that’s posting about this problem its limited to either android devices or shield in paticular. Also it happens regardless of bitrate. The content used to provoke this message yesterday was 720p, while before when the shield worked perfectly (~ a week before christmas) i could stream 4k movies with 80mbit bitrate with no problems. I don’t have this issue on my Samsung TV, or my iOS devices. But yeah, maybe I will create a new topic. Unsure wether it will help considering how long some of you say you had this issue though… 
I get this message on my shield regularly and it has nothing to do with download or cpu speed. I like the shield but the plex client is unfortunate.
So if it is a fake message and the clients don’t work properly, then why don’t the developers fix this in both server and client updates. I mean if this has been going on for over a year, why can’t anyone get a handle on this?
I recently purchased nvidia shield. Immediately got this error message. The only fix I was able to find was to install plex through kodi add on. After installed unchecked ipv6 in network shield settings. It worked for me
1 Like
is your shield plugged into your TV, or is it plugged into a 4k/hdr/atmos capable receiver?
are you trying to use subtitles? did you try disabling?
for full 4k direct play without errors or transcoding, you need a shield > 4k/hdr/atmos receiver > 4k tv
I finally gave up on Plex. It was a bit annoying to set things up with the competitor, but it wasn’t as bad as i thought (fixing wrong matches). I took me less then a day, and i have finally something that works on all devices (Nvidia Shield, iOS tablets, Android Tablets, PS4). In the end i found that i even prefer the new thing. For fear of violating some forums rules i’ll not mention what the competitor is … but most will know or a simple google search will point you at the right direction. So … farewell Plex.
@elan another example of a long standing android bug that has gone unfixed.
I’m now getting bitten by this one myself, seeing this message all the time on a hardwired network.
Yep I had a binge session earlier.
No less than 7 occasions in 9 hours.
Oh my God!! Look at that!!
Pinging 192.168.1.17 with 32 bytes of data:
Reply from 192.168.1.17: bytes=32 time=69ms TTL=64
Reply from 192.168.1.17: bytes=32 time=6ms TTL=64
Reply from 192.168.1.17: bytes=32 time=33ms TTL=64
Reply from 192.168.1.17: bytes=32 time=112ms TTL=64
Reply from 192.168.1.17: bytes=32 time=26ms TTL=64
Reply from 192.168.1.17: bytes=32 time=38ms TTL=64
Reply from 192.168.1.17: bytes=32 time=1ms TTL=64
Reply from 192.168.1.17: bytes=32 time=1ms TTL=64
Reply from 192.168.1.17: bytes=32 time=1ms TTL=64
Reply from 192.168.1.17: bytes=32 time=91ms TTL=64
Reply from 192.168.1.17: bytes=32 time=97ms TTL=64
Reply from 192.168.1.17: bytes=32 time=1ms TTL=64
Reply from 192.168.1.17: bytes=32 time=19ms TTL=64
Reply from 192.168.1.17: bytes=32 time=31ms TTL=64
Reply from 192.168.1.17: bytes=32 time=38ms TTL=64
The ping reply time IS all over the place!! Garbage!! If I ping anything else in my house, 95% of the replies are <5ms with most of them being 1 or 2ms.
nVidia Shield TV v8.0.0
Plex v7.10.0.8875
Ubiquiti AP AC Pro
Shield TV connected via 802.11ac
Plex server running in an unRAID Docker container on an HP ProLiant DL360e G8
CONSTANT “Your connection isn’t fast enough” nonsense, only when playing certain things though…oddly.
There HAS TO BE a fix for this…
I fixed it connecting the Shield with the cable. It has been always like that.
Here my story with the Shield. I’ve moved three times in the past two years, and until recently I thought my old WiFi was the issue (Netgeat R7000). During my last move, I’ve also changed it, initially with an RBK50 (one router + one satellite). My house has three floors now. Internet comes at the first, my nas at the 3rd and the TV, soundbar, Xbox etc at the 2nd. Any device connected though WiFi is just perfect besides the Shield, so I ended up buying another RKS50 (199€) bacause of course I couldn’t have a cable between floors.
During my tests I really tested every possible combination (connection local to the satellite, dasy chain on and off, mtu, etc). All other devices are between 2 to 4ms from the distant point in my house (aka 3rd floor to router and 1st floor to everywhere else)
My NAS currently host a few VMs including PMS and my goal would be to use the Shield for everything. Another satellite in my case was cheaper than ATV + Intel NUC for PMS.
During my research I found people started complaining about poor WiFi since 7.0 but in general WiFi has bene poor on some models. Given I always had those issues with my Shield, I guess, it’s an hardware flaw (and it’s out of warranty)
Yea, I’ll run a cable to it. My house isn’t 3 stories, nor is my LAN super complex. That’s why, when I started getting this error, I was like, “ok…no.” It’s just kind of ridiculous that we have wifi but can’t use it.
What do you mean by “satellite”?
Oh well. Not the end of the world. I’ve been getting cables run little here, little there over the past couple months so I’ll add this run to the list.
I would definitely hard wire it to get a real sense of the issue. That said my shield has never used WiFi and I get this error semi regularly.
Well THAT doesn’t inspire confidence…
Hopefully hard wiring corrects the issue for you but at the risk of sounding negative, I don’t hold out a ton of hope this gets resolved any time soon. I’d love to be wrong (and would happily admit if I am) but I’ve lost some faith in the last year or so that this stuff gets taken seriously.
People mix up issues here. Most people complaining about the “not fast enough to stream” are on wired network. It put’s out this error message, but it is entirely unrelated to network speed. In my case i can see the server delivering up to 800mbits of data for a video stream that is 20mbit (including all audio streams). So something fishy is going on. This is on most of my H264 / MP4 container files with more then one audio track and subtitles when direct played. Anywho … as i said before it’s now more an academic interest for me as I’m rather happy with emby.
A satellite in my case is a Netgear RBS50. Mesh-wifi network, it’s a device in the chain the connects to the router
I believe the Shield connectivity can play a major role for the “not fast enough to stream” error
In my case, it has always been a hardware wifi issue. Is that the case also for rmp5s? I don’t know, maybe it’s his wifi. The cheapest option I had was the cable through a new satellite. Any other solutions were MUCH more expensive 
One thing for sure, anybody that has this problem should give a try to the Ethernet cable. Maybe it will turn out as a completely different story but a bad/noisy wifi can give a lot of issues kinda difficult to troubleshoot.
Then, the discussion if using a cable is mandatory, frankly, it’s nonsense. Even if we talk about the latest UHD standard of 128Mbit/s bitrate, a modern 5GHz connectivity is perfectly capable to handle much more than that with decent (and stable) latency.
I don’t use wifi. I only get this message through shield plex app. The offical kodi plex add on and native Samsung TV plex app doesn’t give this error message. It’s not unplayable just annoying to restart after every 15 mins
Oh oh. Got ya.
Same problem here! This issue has made Plex useless for 1080p and 4k HDR.
