-
-
Notifications
You must be signed in to change notification settings - Fork 922
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
Unlock watch mechanism #697
Comments
I would support this request. I have also the problem, that sometimes there is another screen, often also the alarm is disabled or brightness has changed by unwanted inputs, the watch plays pong with itself, the heartbeat measurement started/stopped alone and so on... The issue appeared with the changed touch behaviour in 1.4.0, with Version 1.3.0 and prior there were rarely unwanted inputs. |
#723 is a wip implementation |
I feel this is a bug, the ghost touches/oversensitivity, and once that bug is squashed this feature should be unnecessary. It could still be interesting, but as a solution to false inputs, it's a patch to hide another problem. |
This in combination with #395 would be a great improvement for the every day use of the watch! |
Let's track this issue in #618 |
I need everyone feedback on this. I constantly find that when I look at the watch, it is in one menu or another that was randomly registered while I was wearing the watch.
Can we have it such (suggestion only) where when we take or raise the wrist, it shows the watchface and any other touch input (while watchface is displayed before going to sleep) requires a "slide to unlock" before we can access the menus.
I am also open to any other suggestion. That said, it's only a discussion to gather ideas and hopefully, for a dev to take up as I don't code in "modern" languages... :)
The text was updated successfully, but these errors were encountered: