You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having recently installed the app from F-Droid, I was playing a few solitaire games in bed when I noticed that the screen would automatically switch orientation to landscape as soon as the phone was being held sufficiently horizontally. This kept happening even though I had specified in Android settings to not auto-rotate the screen.
Additionally (and perhaps related), when double-tapping anywhere on the screen I get a message saying "screen rotation enabled", but I cannot find a corresponding setting (either in the options menu or elsewhere) to disable screen rotation. Double-tapping again after that message doesn't seem to change anything.
I am running Android 13 on a Sony Xperia 10 III phone, and I have confirmed identical behaviour on an Oppo Pad 2 running Android 14.
The text was updated successfully, but these errors were encountered:
We use Activity#SetRequestedOrientation to manage screen lock vs. screen unlock (screen-full-sensor). As of Android 12 the android os can prevent that in many ways. The problem will need a deeper dive into android developer infos. So don't expect a fast fix. Google keeps us busy.
Could also be that you will find an os setting that helps. Let us know.
Having recently installed the app from F-Droid, I was playing a few solitaire games in bed when I noticed that the screen would automatically switch orientation to landscape as soon as the phone was being held sufficiently horizontally. This kept happening even though I had specified in Android settings to not auto-rotate the screen.
Additionally (and perhaps related), when double-tapping anywhere on the screen I get a message saying "screen rotation enabled", but I cannot find a corresponding setting (either in the options menu or elsewhere) to disable screen rotation. Double-tapping again after that message doesn't seem to change anything.
I am running Android 13 on a Sony Xperia 10 III phone, and I have confirmed identical behaviour on an Oppo Pad 2 running Android 14.
The text was updated successfully, but these errors were encountered: