Skip to content
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

Feature request: prevent screen control from switching the display off during screen interactions #15313

Open
scaidermern opened this issue Sep 15, 2022 · 1 comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning

Comments

@scaidermern
Copy link
Contributor

scaidermern commented Sep 15, 2022

If the screen gets activated by screen control, for example due to navigation instructions, the user is able to interact with the map and with menus. With the current behavior the screen will suddenly switch off again, even if the user is interacting with the map by panning or typing something into the search function. Any user interaction should stop or better reset the screen timeout so that the screen stays on while the user is performing actions.

@vshcherb vshcherb added the Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning label Sep 23, 2022
@mariush444
Copy link
Contributor

--- up ---

I use screen control as:
Use system screen timeout - off
Timeout after wake-up - 45sek
Proximity sensor - on
Navigation instructions - on

When the screen is wake-up and I wanto to verify something on the screen (map) then screen is off during my action.

In my opinion Timeout (45sek) should be after last touch and not after wake-up

The same behavior should be with the option
Map during navigation -> Auto-center map view.

auto-center should be activated after the last touch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning
Projects
None yet
Development

No branches or pull requests

3 participants