Please reenable/reimplement the video rotation button. It's missing since the update to 0.20.0
It's not possible to easily view a video in fullscreen in Newpipe anymore while laying on one side in bed or on the couch, floor...
It's a hassle to go into Android settings and deactivate the screen auto rotation just to view a video in full screen and to reenable it again afterwards. The button was a very shrewd feature.
Maybe I didn't understand something but don't autorotation allows you to hold your phone horizontally and view the video in fullscreen in landscape orientation?
I'm pretty sure that this issue is about the option to watch videos like this, which doesn't exist anymore in v0.20, because manual video rotation control has been removed.
As the author correctly pointed out,
It's not possible to easily view a video in fullscreen in Newpipe anymore while laying on one side in bed
In 0.20, your only portrait mode is not full screen, and looks like this, which is worse for a number of reasons:
I really don't understand what you mean
It's not possible to easily view a video in fullscreen in Newpipe anymore while laying on one side in bed
Of course you can
In 0.20, it looks like this
Just click on the full screen button: (the button which looks like this [ ] next to 25:29)

You're missing the key point:
while laying on one side in bed
If you're lying on your side and holding the phone with one hand, you don't want the video to play in landscape mode, because holding a phone in such position would be very inconvenient (let's hope I don't have to take reference photos to get my point across). Screenshot 1 in my comment (taken in v0.19) shows the optimal way to watch a video in such situation, which is no longer possible with v0.20, because someone thought that manual video rotation control should no longer exist in NewPipe.
And here's another argument in favor of the manual rotation control: there are YouTube videos with 1:1 aspect ratio. Currently NewPipe treats them as landscape videos, and always plays them in landscape mode when you press the full screen button. The video is square, so why does NewPipe have to assume that it should be played in landscape, without giving any choice to the user?
Let's keep discussion in #4383
https://github.com/TeamNewPipe/NewPipe/issues/4383 is about a bug that unexpectedly puts the whole app in landscape mode.
This is more relevant to https://github.com/TeamNewPipe/NewPipe/issues/4414 , which explicitly mentions "Add the force rotation".
Good point, @nbmrjuhneibkr.
@Stypox, since you've made a PR for #4414 that adds the player switch buttons but doesn't add the rotation button, let's keep this one open for that purpose and leave #4414 for the player switch buttons.
If you're lying on your side and holding the phone with one hand, you don't want the video to play in landscape mode, because holding a phone in such position would be very inconvenient
You can lock the orientation in portrait via status bar panel. This is what you can do with any apps on a phone. This task shouldn't be made by all apps just because you want it included into the UI. Every feature needs a correct place for it.
This message is not something that needs a reply, it's a final thought that couldn't be changed over time or with a further discussion.
You can lock the orientation in portrait via status bar panel.
Did you even read the comment https://github.com/TeamNewPipe/NewPipe/issues/4500#issuecomment-706980931 ? The orientation is locked. The app is in portrait mode. System-wide auto-rotation is not an issue here. As I mentioned, in 0.19 full screen portrait mode (which is optimal for this situation) looked like this.
In 0.20 this doesn't exist anymore, so the only available portrait mode looks like this,
which is worse for a number of reasons:
This message is not something that needs a reply, it's a final thought that couldn't be changed
Maybe I'm missing something, but the developer of NewPipe is listed as "Team NewPipe", not @avently .
And yet it seems like @avently (who is one of the many contributors, and not even the original creator of the app) has the power to dismiss any input, be it from users or from other contributors. What is happening here?
@nbmrjuhneibkr
Maybe I'm missing something,
And yet it seems like avently (who is one of the many contributors, and not even the original creator of the app)
You missed something. It's not so important who is the creator of the app because he doesn't develop the app right now. What is important is people who continue to develop the app.
has the power to dismiss any input, be it from users or from other contributors. What is happening here?
I have a power to say my opinion. It doesn't mean who I am, I can say what I think. If I don't like an idea, I (personally) will not implement the idea. It doesn't mean I have a power to say "no" for a feature. Some people can do this but not me.
If you don't see your ideas implemented then nobody have a time or desire to implement such idea.
And where did you see that I
has a power to dismiss any input from other contributors
?
It doesn't mean I have a power to say "no" for a feature.
Alright, so the comment expressed a personal opinion which may not represent the opinions of other NewPipe contributors, and shouldn't overrule their decisions either. Thanks for the clarification.
Comments like that one make this environment appear rather hostile towards anyone who is dissatisfied with major changes introduced by the 0.20 update, and who wants some of them to be optional. So this clarification was necessary.
But what about the misunderstanding of the actual issue, which I pointed out in the first part of my previous comment?
Also, I don't think it's fair to treat requests for features that already existed in NewPipe, but have been removed in the recent update, as other regular feature requests.
@nbmrjuhneibkr
Also, I don't think it's fair to treat requests for features that already existed in NewPipe, but have been removed in the recent update, as other regular feature requests.
It's not about fairness it's about logic.
See, many years ago you could find other features that don't present now. It is because developers removed something and made the app better with other features. If something is removed this is a sign that the feature shouldn't be in the app. In some cases I removed useful features for others and they should be returned but not in the case of this issue.
@nbmrjuhneibkr
Also, I don't think it's fair to treat requests for features that already existed in NewPipe, but have been removed in the recent update, as other regular feature requests.
It's not about fairness it's about logic.
See, many years ago you could find other features that don't present now. It is because developers removed something and made the app better with other features. If something is removed this is a sign that the feature shouldn't be in the app. In some cases I removed useful features for others and they should be returned but not in the case of this issue.
But what about the misunderstanding of the actual issue, which I pointed out in the first part of my previous comment?
If you're talking about three points in a list from your top comment then I'm ok with current behaviour. It works like it should.
Importance level of such points is 1 of 10
they should be returned but not in the case of this issue
Again, this doesn't sound like a personal opinion of one contributor, but rather like a final answer for anyone (either user or developer) who thinks that this feature should not have been removed. I'm getting some conflicting messages here.
If something is removed this is a sign that the feature shouldn't be in the app.
But who gets to decide which features should or shouldn't be removed? A community of developers and users, or a single contributor whose understanding of usage scenarios may be too narrow to make decisions that affect the development in major ways?
After some digging I noticed this comment in your initial PR (which was rejected) for the unified player: https://github.com/TeamNewPipe/NewPipe/pull/834#issuecomment-343673960
In this comment, original creator of NewPipe points out that manual video rotation control has gained enough recognition to be praised in publications.
It's clear that this feature was neither unknown nor useless. I've never seen anyone asking for its removal, but I already see comments asking for it to be brought back (which I fully agree with).
@nbmrjuhneibkr you're asking me and than blame that my opinion is not like yours. Man, i'm not interesting in talking on the issue. You know what I think. Nothing will be changed in my mind even if you give another portion of arguments. If you don't like it it's not my problem.
No one ever asked you specifically to address this issue. Last time I checked, there were other developers who are also working on NewPipe. If you're not interested in it, then why are you even commenting on it?
@opusforlife2 what about closing this too? Or you think it is a good idea to show the fullscreen button even with autorotation enabled?
I don't know WHERE my comments keep vanishing. Somebody help me with my vanishing problem first. 馃槱
Anyway, I still think overloading the full screen button to 'force rotate on long press' is a better idea than a separate button. If you're watching a portrait video in full screen, long pressing would turn it to landscape forcefully. And vice versa.
Once you have long pressed on the button to force rotate, all further videos in the queue should obey that orientation.
@opusforlife2 but this issue is about showing the fullscreen button when autorotation is enabled. So right now a user can rotate the phone to get the orientation rotated. He wants a button which can be clicked to rotate the orientation even with autorotation enabled.
So it's kind of a different issue than what you wrote
@avently I have no idea what you're talking about.
This is the title of the issue: "Add back orientation switch button in full screen # 4500"
but this issue is about showing the fullscreen button when autorotation is enabled
No, that issue is here: https://github.com/TeamNewPipe/NewPipe/issues/4478
Original description of this issue is kind of confusing, but this part
It's not possible to easily view a video in fullscreen in Newpipe anymore while laying on one side in bed or on the couch
makes sense if this issue is about
Adding back orientation switch button in full screen
Which is the title right now, and the author hasn't expressed any complaints about it so far. And the original title was also about the manual rotation control anyway.
@opusforlife2 sorry, wrote in the wrong issue. I mean #4478. What for you think about closing it?
I still think overloading the full screen button to 'force rotate on long press' is a better idea than a separate button. If you're watching a portrait video in full screen, long pressing would turn it to landscape forcefully. And vice versa.
This is nice in theory, but it's also yet another feature that users will not discover without reading about it first. All long press actions require additional explanation.
Tooltips are already used for the queuing actions.
Not everywhere though. I don't remember seeing them in this dialog.
This suggestion is fine for me personally, but I'm not sure if all users will appreciate increasing number of long press actions in the UI, especially for something that was previously available as a dedicated button.
Oh. I didn't realise this before, but if you toggle on automatic full screening, you basically wouldn't need the full screen button at all. It could be replaced by force rotation entirely.
the full screen button
I think this is more related to https://github.com/TeamNewPipe/NewPipe/issues/4478
Auto full-screen + manual rotation button is exactly how it worked before 0.20, but what if user is fine with new player behavior (without auto full-screen), and just wants to have access to manual controls?
My device is kinda broken, I guess. It is not recognize horizontal orientation anymore, and I can't rotate video manually at all. VLC player and Google Photo. Only official Youtube, which have huge of advertising, can do this. I'm shocked.
I too am really missing the the auto full-screen feature. Many of us prefer compact and smaller handsets over bigger screen ones. Watching videos in tiny portrait mode is not satisfying experience for (at least) those of us. I don't like to active system-wide rotation just for an app and the orientation switches back to portrait mode if you lay on your side. It was a well-accustomed hassle in YouTube client/mobile browser to manually switch videos to full screen for every short clip. Many of us saw NewPipe's way as a fix. I really hope the devs will consider bringing this feature back.
I too am really missing the the auto full-screen feature.
@HattinGokbori87 Wrong issue. You're looking for #4152.
Most helpful comment
Again, this doesn't sound like a personal opinion of one contributor, but rather like a final answer for anyone (either user or developer) who thinks that this feature should not have been removed. I'm getting some conflicting messages here.
But who gets to decide which features should or shouldn't be removed? A community of developers and users, or a single contributor whose understanding of usage scenarios may be too narrow to make decisions that affect the development in major ways?
After some digging I noticed this comment in your initial PR (which was rejected) for the unified player: https://github.com/TeamNewPipe/NewPipe/pull/834#issuecomment-343673960
In this comment, original creator of NewPipe points out that manual video rotation control has gained enough recognition to be praised in publications.
It's clear that this feature was neither unknown nor useless. I've never seen anyone asking for its removal, but I already see comments asking for it to be brought back (which I fully agree with).