Force landscape display

[Mandrake]

So I am building myself a TV box on the Rasberry pi 4 with the Lineage OS 17.1 adpted for Pi 4 by Konstang running Android 10. It is supposed to be forced landscape, but I am still getting apps that aren't displaying in landscape and show as portrait e.g. APKPure. I really don't think it is the manifest.xml for these apps as they display in landscape on my Mecool M8S Max. I have tried multiple screen rotation apps (most have no effect whatsoever, and a few will simply rotate the potrait app 90 degrees so that the app lies on it's side). I have tried modifying persist.sys.app.rotation in build.prop to various values and also no effect. I have tried scouring the net to find answers, I have even contacted the ROM developer, and he says there is nothing that can be done. I don't believe this as the same apps that display as potrait on the Pi will display as landscape on my TV box. Any suggestions of what I need to do to force these apps into landscape view?

[Guest]

...I have tried modifying persist.sys.app.rotation in build.prop to various values and also no effect...

Try this, maybe ii will work, and set ...hwrotation=0

https://forum.khadas.com/t/rotate-vi...android/1313/5

[RiCkLaR_atvX]

Are you using the ATV build of Android 10 or the standard Android AOSP build from KonstaKANG?

[Mandrake]

RiCkLaR_atvX I'm using the standard build. I'm not a fan of ATV.

Guest thanks I'll try that tomorrow. I assume it also goes in the build.prop right?

[Mandrake]

Guest i did a combination of the following changes to build.prop

I added the following two lines:
persist.sys.app.rotation=force_land
ro.sf.hwrotation=0

On their own they did nothing. However as soon as I installed a rotation control app then I could force rotate those problem apps to landscape.

Any way to permanently force rotation without the need for a rotation control app?

[RiCkLaR_atvX]

Normally these are the two choices used for Rotation:

persist.sys.app.rotation=middle_port
persist.sys.app.rotation=force_land

After inserting "force_land" has always fixed the issue in the past for myself. After editing the build.prop did you Reboot System before installing the rotation-app?

As far as an additional permanent fix, the only thing I can think of is Toggle on the Auto-Rotate "Quick Setting" tile if it is available in the pull-down menu, or add a tool/utility app that gives the option to add a 'Force_Landscape' quick-setting tile or the option to make one.

[Mandrake]

Normally these are the two choices used for Rotation:

persist.sys.app.rotation=middle_port
persist.sys.app.rotation=force_land

After inserting "force_land" has always fixed the issue in the past for myself. After editing the build.prop did you Reboot System before installing the rotation-app?

As far as an additional permanent fix, the only thing I can think of is Toggle on the Auto-Rotate "Quick Setting" tile if it is available in the pull-down menu, or add a tool/utility app that gives the option to add a 'Force_Landscape' quick-setting tile or the option to make one.

Yes I rebooted after the build.prop change.I have also used the autorotate quick setting previously with no luck. I also previously tried
persist.sys.app.rotation=force_land
on it's own and the rotation apps wouldn't work. I think it was the addition of
ro.sf.hwrotation=0
that did the trick. I haven't tried persist.sys.app.rotation=middle_port, so I will go back and play with it. I think if ro.sf.hwrotation=0 is what did the trick, it may be that because there is no sensor for rotation, that somewhere in Android that the data for sensor is incorrect or unspecified. I have seen previously that the control rotation apps have read that the orientation is unspecified. Besides build prop is there somewhere else one can specify a value for the gyroscope sensor, although there isn't one physically present?

[RiCkLaR_atvX]

....Besides build prop is there somewhere else one can specify a value for the gyroscope sensor, although there isn't one physically present?

Don't think so.