-
-
Notifications
You must be signed in to change notification settings - Fork 327
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
feat: Force app into landscape-only mode #544
Comments
This comment was marked as spam.
This comment was marked as spam.
Not sure why you would "constantly change the rotation settings." You can also automate it with something like Tasker. |
I don't think telling me to get some paid app is a good solution. |
Why not? I gave an example. we'd have to pay time to implement this |
Because for other people's sake, unless they go out of their way to ask this, then they'll be stuck with an annoying interface on tablet mode. The reason you have to fiddle with rotation lock settings is because if you try to use Youtube holding the tablet in an orientation where your viewing the screen not relative to the ground (lying down for instance) then the tablet will display the video incorrectly. This means if you want to view a video in landscape but then use other apps in portrait you have to lock the screen every time you move between apps. In the short time this issue has been open, someone else has already agreed with my point of view. |
If you want to do it, then make a new ReVanced patch and create a GitHub pull request for the change. It can be a universal "change to landscape orientation" patch that can be applied to any app. |
@Green-de-la-Bean The lock rotation setting on Android does this already, as explained; you can automate it using Tasker as an example |
Some apps, such as Freezer, ignore that setting and will auto-rotate no matter what you do. |
There was no issue with former vanced in full screen on tablet when auto rotate was OFF. It is expected that revanced behaves the same. Yes there are some third apps that can automate the screen orientation for specific app. But it's not the same as a built-in feature allowing to use revanced in portrait and only switch to landscape when full screen. Why this issue is closed and marked completed instead of not planned? It's misleading. Requested many times like in ReVanced/revanced-patches-template#1840 ReVanced/revanced-patches-template#1052. ReVanced/revanced-patches-template#985 describes perfectly the issue and motivation. Currently you can not lock video in landscape unless using a third party app or playing with the QS multiple time to achieve what you want every time. This feature keeps being asked for a reason. The problem seems to be YouTube itself. Official app 18.31.37 has the same issue. Full screen sticks in portrait if auto rotate is OFF. But if a patch can solve this to only use landscape sensor to force any landscape mode in full screen, it would be perfect. |
# [2.62.0](ReVanced/revanced-patches@v2.61.1...v2.62.0) (2022-09-21) ### Features * `hide-time-and-seekbar` patch ([ReVanced#544](ReVanced/revanced-patches#544)) ([ef7afc7](ReVanced/revanced-patches@df4d8ea))
Co-authored-by: oSumAtrIX <[email protected]>
Application
YouTube
Issue
Unlike all other video players, on the YouTube app when on an Android tablet, if you open a video in full screen and then rotate the device to a vertical orientation, it will change the video to be shown in that orientation. This makes watching a video in bed very annoying as you constantly have to adjust the rotation lock.
Patch
Have the app run in a mode similar to many Android games where it will only display in landscape mode at all times. I believe this would be fairly simple to add as you could just add the line:
android:screenOrientation="landscape"
to the manifest.Motivation
I personally would benefit from this because I hate having to constantly change the rotation settings. I don't think it would take very long to add and would probably benefit other users of YouTube ReVanced who have it installed on a tablet device.
Acknowledgements
The text was updated successfully, but these errors were encountered: