reykell betsie elmiria
Argelia Long
prior to yesterday's update (1/16/24) for my roku 2, two clicks of the star button while streaming on netflix brought up mbps speed and resolution in right upper hand corner. now it disconnects the streaming and causes an error message. this star button dysfunction only happens while streaming netflix, nowhere else. contacted netflix support and was told this is a roku issue, not a netflix issue, because netflix streaming is otherwise working as it should; it is only the star button on the roku remote which causes a problem.
There was nothing at all wrong with my network connection. I checked the Wi-Fi on other devices and it was fine. I restarted the Roku. Checked for any more recent updates. Checked my connection speed on the Roku home page. Checked other sites, like Amazon prime video, YouTube. etc. and there was no problem. Checked my connection speed through Netflix and, though it was substantially slower than the speed on the Roku home page, it still was OK. As for the microSD card, I checked it on the Roku "About" page and it hadn't changed. Everything else on the Netflix app worked just fine. Go figure!
And today the TV show I watched, Berlin, was no longer on my "Home" list, but when I searched for it and clicked on it, it's menu indicated it was still on my list. After I streamed it a bit, to check the star button, it reappeared on my list. Go figure.
We understand you're having a problem with the Netflix channel. We're happy to assist you further, but we will need to gather some details. Can you please provide us with the error message or code that you're getting? What troubleshooting steps have you taken so far?
I have a Roku 3 and after the 12.5.5 Build 4174 OS and channel updates, I haven't had this issue when pressing the star key twice on my Roku remote when in Netflix unless this issue is specific to the Roku 2. I do see the mbps speed and resolution in the upper left-hand corner after pressing the star key twice while watching a Netflix video, so my model should be similar to yours. Have you tried to restart your Roku device to see if that fixes your issue?
Since the Roku 2 has a micro-SD card slot, if you have a micro-SD card inserted, remove the HDMI cord, remove the micro-SD card, restart your Roku, and see if this resolves your Netflix issue. If it does, you'll need to format the SD card in a computer (make sure not to format the wrong drive) and then after a Roku restart, reinsert the SD card. (My Roku Ultra just threw a complete malfunction out of nowhere after getting the OS update yesterday and doing this resolved my issue. I'll probably have to do this same thing with my Roku 3 now that I know this is an issue.)
If my troubleshooting advice doesn't work for you, and if John is unable to further assist you after you provide all your details, even though the Roku 2 (4210X) is still supported, you may want to consider purchasing a newer model (just be aware that the mbps speed and resolution Netflix feature is no longer available on newer Roku devices when watching a Netflix video as that has been taken over by the accessibility menu, so you have to press the star key twice when not watching a video in Netflix). After nearly a decade, I'm always surprised that my Roku 3 continues to receive updates after my Roku 1 (SE) has turned into an outdated brick.
Hi - I am having serious issues downloading and streaming content on my Deco x60. In particular, streaming or downloading content on Netflix is a problem (on my ipad, iphone, and tvs). I frequently get an error. I have also tried changing my IPv4 DNS, turned off (and on) beamforming and fast roarming.
In addition to the netflix issues, other streaming services sometimes do not work. Finally, when I try to download large files for work, it only downloads 3-5MB of the total and then stops and says download failed.
On all of the devices, other services, such as google, youtube, etc. work and have no issues. And when I test the internet speed, it says I have no problems, with over 100 Mbps down and 40 mbps up. Thank you for your help.
I was testing it again, and it seems like it isnt as much of an issue when I am connected to the main deco, only to the mesh ones. Not sure if it matters, but I am using ethernet cables to backlink with the main deco. The problem is that I am mainly connected the mesh / endpoint decos, not the main one. Also, it appears that if I connect to the main deco (over wifi), download something on netflix, and then go to a different area and use the mesh, streaming sometimes works for a short period of time, then fails again.
First off, I've tried QoS... It does not help.
My brother is an internet hog who doesn't realise he utlises way more than his fair share of bandwidth.
So, in clear terms can someone tell me how to throttle Netflix traffic. Preferably to 1 Megabits, thanks.
from cursory looking the keyword is "brother". This is not a technological issue and hence requires a non-technical solution. Talk to your brother make him change his behavior ; this is way more sustainable than going into an technological arms-race.
But since netflix is only going to use one flow as far as I know, why does flow-fair queueing as performed by qos-scripts or sqm-scripts not solve or severely ameliorate the problem? What is the total bandwidth you have available on your link for downstream an upstream, and how much of that bandwidth does netflix traffic consume?
Hey moeller0, I've talked to the stubborn bastard but he does not comprehend the fact that him constantly streaming HD Netflix severely deteriorates other's trying to use the connection (4.5mbit)
I don't know why QoS does not work for streaming, Netflix just seems to bulldoze over it. Regardless I'm not really interested in a conversation about QoS, if you have a solution to throttle Netflix then please share.
Cheers.
I guess than our conversation ends here; all I am interested in is getting sqm-scripts to work "as advertised" under the widest range of circumstances. So figuring out why netflix does not behave is potential interesting, your preferred alternative not so much...
But as an guideline for your plan, you need to find some invariance in the traffic coming in from netflix to your brother and the use this invariance to mark those packets, then you can sort them into a specifically set up band in your traffic shaper that only allows 1 Mbps at maximum. Finding those invariances is going to be tricky and error-prone as your brother most likely is going to adapt (say you throttle his IP, he simple changes it, same foe MAC or simply uses some one else's computer). But hey, if that is how you roll, more luck to you...
I guess I should be less grumpy, so sorry. I remember that we had a two topics in which we discussed facets of your set up, but in both cases you seemed to drop out of the discussion before it reached a conclusion/solution. Obviously, it is your right to do so, but on the other hand it makes me question the validity of your initial premise: "First off, I've tried QoS... It does not help." (ironically quality-of-service or QoS is the shorthand name for the kind solution of traffic engineering you are looking for.)
Again, you might be right in your assessment that neither qos-scripts nor sqm-scripts actually can solve your issue, but there is just not enough data to figure out whether this could be fixed.
Don't get me wrong, SQM-QOS works at keeping latency low for gaming etc... but in my experience doesn't help share bandwidth for streaming. That's just my experience, so I'd just like to know how to set a hard limit on his bandwidth because I know that should 100% fix it.
luckily there is some overlap between our interest: namely figuring out how the netflix traffic actually looks. You need to know this to design the filters you ultimately need to isolate that traffic, and I am curious to learn that to figure out why netflix seems to evade/side-step fq_codel's flow isolation. I already assume that netflix traffic will be quite bursty (so dash instead of smooth streaming), but are they using tcp or udp, are the port numbers constant will packets always be served from the same IP all of this will be interesting to know. So, in case you take some packet traces and look at them, please post at least a summary to this thread. With lots of luck this might indicate why qos- and sqm-scripts fail to solve your problem. (I just want to add that your link is quite interesting as due its low bandwidth it will show problems more prominent than faster links where people might not notice).
90f70e40cf