bug(YouTube/Video playback): Default video quality does not apply

[Cast0r-999]

Type

Error at runtime

Tools used

RVX Manager

Application

Youtube 19.21.40
Patch 4.9.2 dev.1
Noticed this on 4.8.6

Bug description

Some videos randomly start on low resolution (360p/480p), even when my automatic set to 1080p. I don't know exact pattern or reason: maybe it's often when i continue video; maybe it's ~1/10 or ~1/20 frequency.

Error logs

No response

Solution

Reset resolution manually, which is obviously annoying.

Additional context

Any king of spoofing (playback, device, codec) is turned OFF.

Device Environment

Android 10, MIUI 12.0.1, Global, Official, non-root.

Acknowledgements

• This issue does not reproduce on unpatched YouTube or YT Music.
• This issue is not a duplicate of an existing bug report.
• I have chosen an appropriate title.
• All requested information has been provided properly.
• I have written the title and contents in English.

[GucekPL]

Same, it seems the Default Video Quality option is working randomly - I have set 1080p on Wi-Fi and mobile network, but the videos are starting between 360p and 720p

[inotia00]

Google added delay for video quality changes in YouTube 18.39.41+. (server side)

Even if you change the video quality, there is a delay of 3 to 7 seconds to apply it.

This is the cause of the bug and is reproduced not only in RVX but also in ReVanced.

Temporary workaround is as follows:

1. Patches YouTube 18.38.44 or earlier.
2. Use Skip preload buffer setting (Experimental Flag)

[Cast0r-999]

Does Google 1-3 days ago changed something again with resolution mechanism ???
"Skip preload buffer" now doesn't help and some videos stuck at 480p, until i restart the app.
P.S. I'm on same YT/patch version (first post description).

[GKid94]

Still a issue

[CoolCooler0]

Spoof Youtube version to 18.20.39 that fixed it for me. I had it on Revanced as well before moving to rvx.

[inotia00]

As mentioned in the comments, it's a behavior of the new YouTube client, not a bug

[CoolCooler0]

As mentioned in the comments, it's a behavior of the new YouTube client, not a bug

I did read through it. I thought it will be a good idea to comment this. Maybe someone wants a quick "fix" until you release an update.

[inotia00]

reflected in revanced-patches-4.10.2