App: Lock screen orientation only during navigation / follow

:roll_eyes: :confused:
I have been using “System” (automatic rotation) for years and do not need an orientation mode any way.

Precisely, we cannot limit other users when introduce new features.
(only offer additional options)

Ich fürchte wir reden aneinander vorbei oder ich versteh wieder einmal das Englische nicht, was ja auch ein Thema in einem anderen Beitrag ist. Ich benutze auch schon immer “System”. Nur mit der Einstellung “System” sperrt sich mein Bildschirm in der App nicht. Er sperrt sich explizit nur wenn ich Hoch oder Quer auswähle…

Let me make two alternative proposals:

Variant 1

As described above:
App “reads” current orientation (which could be one of the either landscape, portrait, reverse portrait, reverse landscape) and locks it at start of navigation.
If the user has selected e.g. system then the app would need to “read” the result, what the current orientation actually is, than lock the resulting orientation.
(that may be difficult to implement :thinking: )

Variant 2

Two independent settings for route planning and navigation/following

  1. Screen orientation for planning:
    • system
    • portrait
    • landscape
    • portrait reverse
    • landscape reverse
    • sensor
  2. Screen orientation for navigation
    • system
    • portrait
    • landscape
    • portrait reverse
    • landscape reverse
    • sensor

(may be easier to implement :thinking: )

Most devices allow 3 screen orientations with “System” setting.
App offers much more options (if they can work on each device).
It’s more flexible for users to try all options and see what works.

That seems more complicated.

Current options are already common, as they’re used likewise in other settings:
Fullscreen mode, Sceeen on, etc.

Leute, ich schüttle den Kopf - bin raus …

Guys, I shake my head, I’m out.

1 Like

Hi. My idea in the first post was to block the current state of the screen rotation - currently reading by the Sensor (including upside down, which the System does not always allow) - when starting the navigation/following.

This would probably be the most intuitive and flexible solution - you can imagine someone wanting to simulate a ride on a vertical screen in hand but on a motorcycle, during real driving, they have a horizontal handle.

True, the introduced solution may be a bit confusing at first glance, but after understanding the principle… it works! So thank you Emux for them :slight_smile:


That is not reliable, as Android does not report the “exact” screen orientation.
Only rotation with reference to display’s “natural” orientation (phone vs tablet).
(so the report in each device is different…)

Better let users to test what modes are possible in their devices & then lock it.

I didn’t know that, and I’m surprised! Especially since Tasker recognizes all four orientations. But I wouldn’t be surprised to find Tasker using some unofficial tricks that don’t work on all OEM devices… I believe you have implemented it deliberately and in the right way. It’s OK now.

Implemented in Kurviger 1.13.17.