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

Niaga swipe travel distance is much higher than other launchers / lag on swipe. #2370

Closed
renantmagalhaes opened this issue Sep 4, 2023 · 3 comments
Labels
bug Something isn't working in progress / implemented Already implemented/fixed or currently in the works and an update will be published soon.

Comments

@renantmagalhaes
Copy link

Describe the bug

Niagara Launcher has a "lag" to swipe up (open app drawer) and even more to swipe down (expand notifications) if compared with several (if not all) launchers.

I believe this is due to the fact that Niagara has a “list” approach, so the sensitivity is much higher compared to other launchers. However, this makes the finger strain much worse as well.

Furthermore, the location of the swipe seems to matter.

Ideally, this can be a toggle to opt-in or opt-out in the settings, or if the launcher identifies it, there's nothing more to scroll down, and the sensitivity is automatically lowered by the same standards as the other launchers.

I'm uploading a video showing the behaviour/differences.

Steps to reproduce

Just try to scroll down on Niagara and on other launchers to see the difference in the minimum travel distance.

Does the issue also occur with other 3rd-party launchers?

Problem doesn't occur with other launchers

Other 3rd-party launcher(s) tested

Nova, Microsoft Launche, Default Android

Device name

OnePlus 9 Pro

Android version

Android 13

Screenshots / Screen recordings

https://www.youtube.com/shorts/ucgnP1iqhqo

document_5165962865215013945.mp4
@renantmagalhaes renantmagalhaes added the bug Something isn't working label Sep 4, 2023
@renantmagalhaes
Copy link
Author

Hey @Amorphous404, do you think this has a change to be fixed, or is this actually the expected behavior?

cc/ @8bitPit, @TFackler

@8bitPit
Copy link
Owner

8bitPit commented Oct 9, 2023

Thanks for your detailed report, @renantmagalhaes. Yes, you're right; the threshold is higher, and it's because it can overlap with vertical scrolling of the list. However, the required swipe distance was higher when increasing the display size/zoom level due to a bug. We'll fix that with the next release and set the swipe threshold to 2.5cm. If that's still too high, you can also trigger the gesture by scrolling with a high velocity. I hope that helps.

@8bitPit 8bitPit added the in progress / implemented Already implemented/fixed or currently in the works and an update will be published soon. label Oct 9, 2023
@8bitPit
Copy link
Owner

8bitPit commented Nov 14, 2023

Fixed in v1.10.0

@8bitPit 8bitPit closed this as completed Nov 14, 2023
@8bitPit 8bitPit mentioned this issue Nov 20, 2023
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working in progress / implemented Already implemented/fixed or currently in the works and an update will be published soon.
Projects
None yet
Development

No branches or pull requests

3 participants