Things are getting worse instead of improving. In the Android version, when the setting is “Automatic Adjust Quality” and you activate subtitles, the playback NEVER START, you get an eternal spinning wheel.
Man this is horrible. How can we end up in this situation? It is like there is no QA department in Plex and things get released with no tests at all.
We are the QA department.
Another month, another chunk of my day spent chasing users down to update their default quality settings…
your welcome 
But but but datacaps bro.
So many data caps.
Interesting. Not seeing that on my shields yet and I’m on beta.
Strange, this is on a fire stick, no beta..
Also noticed this, not sure how it got to 93mbps for Peppa pig when it clearly seems to know original is 2mbps.
Detected is how fast we detected the connection from the server to client to be
Ahhh cheers Dave, that’s makes way more sense 
Is this supposed to be working already with stopping transcode or is this the first step?
I’m not sure what you mean exactly by “this”. Are you just referring to the detected speed, or more, or?
He asks if “this” is the solution to the main problem in this thread. The promised solution. Is this a first step or is this everything?
This = Bandwidth detection
@DaveBinM specifically is the whole solution to the problem using detected bandwidth to tell the user that they’re able to upgrade their quality?
If that’s the whole thing then I really wish you would’ve told us sooner because I have years of data showing that telling the user that their experience could be better if they just change a setting is not going to work.
The only thing way I’ve been able to get users to change the setting is by constantly badgering them, in some cases going to their house and changing it for them, and in rare cases threatening to remove their access to my server.
I don’t think a prompt from Plex will have any more success.
Without seeing the actual implementation I can’t be sure, but I’m fairly confident that if this is the whole thing, then it won’t have the intended effect.
I’ve not had much time to test but from my experience the “auto quality” seems to b default, which sounds like it’ll auto use that setting for users
Is that different then the current “Automatically adjust quality” option? Because I’ve never seen that work consistently.
It’s totally different. I explained what we’ll do much earlier in the thread. But, essentially, the app tries for the highest quality it can, and if it struggles to play, it’ll prompt the user to downgrade to a quality that it can play at. Should the connection improve, it’ll offer an upgrade. This all occurs during playback. It remembers what the connections are like for each server, and will treat each server appropriately.
I was asking if this picture posted here:
and here:
has anything to do with the solution you are currently implementing.
Yes, some users will be seeing the feature at the moment, but not everyone at this stage
