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

changed the alarm timeout to a saner value of 3 minutes #1233

Closed
wants to merge 1 commit into from
Closed

changed the alarm timeout to a saner value of 3 minutes #1233

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Jul 11, 2022

In pull #945 the alarm functionality got expanded by a auto-dismiss after 60 seconds. As others pointed out, this makes the alarm hardly usable for hard sleepers. Also in very loud environments, for example on stage, 60 seconds could be to short to notice the alarm.

@Riksu9000
Copy link
Contributor

I wouldn't say three minutes is more or less sane in this case. From what I've read, the issues people were having were most likely #1086 and not 60 seconds being too short. The use case on a watch is different than other alarms, as the watch should always be strapped to the wrist, whereas other alarms could be placed somewhere where they may not immediately get noticed. The timeout is to stop it from vibrating unnecessarily when the watch isn't worn. I think the proper solution to #1088 would be to have the alarm repeat and maybe with increasing strength.

@ghost
Copy link
Author

ghost commented Jul 12, 2022

Well, it might take quite a while until the behavior of the alarm is implemented in an advanced way. This small change from 60s to 180s would at least improve and maybe restore usability if these changes would not be ready until the next release.

@JF002
Copy link
Collaborator

JF002 commented Jul 19, 2022

The current timeout of 60s was decided after a rather long discussion with many users. The conclusion of this discussion is that the perfect timeout value does not exist: it depends on many factors and on the use-case. So we decided to stick with 60s as the default timeout for now.
It might take some time to implement a more advanced alarm, but you can be sure that if we switches to 180s, other users will open an issue similar to this one asking to change the timeout to another value :)

@JF002 JF002 closed this Jul 19, 2022
@ghost ghost deleted the alarm-length branch July 19, 2022 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants