-
-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug(youtube): auto quality option does not change quality when switching to full screen #589
Comments
Auto quality uses the stock (unpatched) behavior, where the actual video quality is whatever YouTube wants to give you. When changing to full screen, the quality will remain as "auto" and it won't necessarily change anything. Not a bug |
@LisoUseInAIKyrios I tried the regular YouTube app and it works there but it doesn't work in Revanced |
@GKid94 what do you mean "it works"? |
It changes the resolution to 1080p when I go to fullscreen |
I cannot reproduce with stock YouTube. Resolution does not change when switching to full screen. If you have the preferred video resolution set to "auto" in ReVanced (under ReVanced -> Misc), then it should never override whatever resolution YouTube chooses. You can repatch ReVanced and exclude |
It happens now on the regular YouTube app |
It's not a ReVanced issue. |
This comment was marked as spam.
This comment was marked as spam.
# [2.67.0](ReVanced/revanced-patches@v2.66.2...v2.67.0) (2022-09-23) ### Bug Fixes * **hide-premium-nav-bar:** invalid import ([ReVanced#590](ReVanced/revanced-patches#590)) ([37ad223](ReVanced/revanced-patches@692b841)) ### Features * `hide-premium-nav-bar` patch ([ReVanced#589](ReVanced/revanced-patches#589)) ([1811416](ReVanced/revanced-patches@489235a))
Type
Other
Bug description
The auto quality option doesn't work in fullscreen, it won't change the video quality
Steps to reproduce
Play a video and select the auto quality option and go to fullscreen
Relevant log output
Screenshots or videos
Solution
No response
Additional context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: