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

Launcher should return to default Favourites view after quick-locking #2311

Closed
1 task done
DetourToNirvana opened this issue Jun 18, 2023 · 2 comments
Closed
1 task done
Assignees
Labels
duplicate This issue already exists

Comments

@DetourToNirvana
Copy link

Is your feature request related to a problem?

Hi, new Pro user here, and I love the simplicity of Niagra, and my top reason for using it is the speed of access to everything like search, widgets, calendar, weather and so much more.

One thing i enabled right away was the quick-lock. I noticed how Niagra actually scrolls down in the Apps List when i lock the screen using quick-lock. This makes logical sense, but when I unlock my screen the next time, I would prefer so much more to see my Favourites again, instead of ending up in a random point in my Apps List.

Describe the solution you'd like

I see 2 possible solutions, both of which resolve my issue:

  • When the screen is locked using the quick-lock, the next time I unlock my phone, Niagra should return to the default Favourites view, by default.
  • An option to set my preference to not "Remember position in Apps List after locking screen"

Feature Request Procedure

@Amorphous404
Copy link

Amorphous404 commented Jun 21, 2023

Hi @DetourToNirvana, Thanks for reaching out! If you lock your phone via double tapping the alphabet scroller and unlock the phone immediately (< 3 seconds), Niagara Launcher returns you to the last position (app list) instead of the main home screen. This is intentional and saves you time if you accidentally locked the phone.

More info here:
Pressing home doesn't show favorites

@Amorphous404 Amorphous404 added the duplicate This issue already exists label Jun 21, 2023
@DetourToNirvana
Copy link
Author

Thanks for the response. I confirm that this works, and actually is a more reasonable way to do it. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue already exists
Projects
None yet
Development

No branches or pull requests

2 participants