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

Auto silence for timers does not work properly #145

Open
mimaiself opened this issue Nov 25, 2024 · 7 comments
Open

Auto silence for timers does not work properly #145

mimaiself opened this issue Nov 25, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@mimaiself
Copy link

Describe the bug
The option introduced in release 2.9 to silence timers automatically after a certain time does not work properly in version 2.10 either.

To Reproduce
For example, if three timers with a duration of 5, 10 and 15 minutes are started simultaneously and the signal duration is set to 1 minute, it will only work correctly if you wait until the end of the signal duration for the first two timers.
But if, for example, the first timer is switched off manually before the end of the signal duration, the following timers are also ended before the preset duration expires. The termination takes place after seemingly randomly selected shorter time intervals.

Expected behavior
Auto-Silence should work for all simultaneously started timers according to the preset duration, even if a timer is ended manually beforehand.

Screenshots

App version
2.9 and 2.10

Device (please complete the following information):
Samsung Galaxy S23
Android 14

Additional context

@mimaiself mimaiself added the bug Something isn't working label Nov 25, 2024
@BlackyHawky
Copy link
Owner

@mimaiself
To make testing easier, I've set 3 timers with durations of 5 seconds, 1 minute 10 seconds and 1 minute 20 seconds.

The duration for turning off the alarm is 1 minute.

Impossible to reproduce what you describe. The alarm on all three timers stops after 1 minute, even if I manually reset one of the timers.

First, can you please install version 2.10.1, which fixes a major alarm bug?

Then can you please do the same test as I did and tell me if the bug you describe appears?

@BlackyHawky BlackyHawky added the waiting for info Further information is requested label Nov 25, 2024
@mimaiself
Copy link
Author

I installed version 2.10.1 on the Galaxy S23 and then ran exactly the same test as you several times. However, the problem persists.
What is noticeable is that the time at which the signal tone is canceled is different. Sometimes it stops after 52 seconds, then 32 seconds and then after 51 seconds. In another test it stopped after just 13 seconds.

I then installed version 2.10.1 on my Samsung Galaxy Tab with Android 11 and repeated the test. The same problem there too.

Maybe it is caused by the Samsung devices? I may have the opportunity to test it with a device from another manufacturer later this week. I would then provide appropriate feedback.

I don't know if the following information is still helpful:
I did not have the problem described in #136 "Cannot dismiss upcoming alarm ..." on the Galaxy S23 with version 2.10.

@BlackyHawky
Copy link
Owner

@mimaiself
Thank you very much for your tests; it helps a lot.
I will test after my real job (in 7 hours) with my Samsung tablet and I will let you know.

I did not have the problem described in #136 "Cannot dismiss upcoming alarm ..." on the Galaxy S23 with version 2.10.

Thanks for the clarification.
The bug appears if one of the days of the week is selected.

@mimaiself
Copy link
Author

Re #136: It doesn't matter whether one, two or all days of the week are selected. I don't have this bug on the S23.

@BlackyHawky
Copy link
Owner

@mimaiself
As promised, I tested with my Samsung tablet (Android 14) and everything works fine. It also works fine on my Huawei phone with Android 12.

@BlackyHawky BlackyHawky added the specific device Not all devices are affected by the issue label Nov 26, 2024
@mimaiself
Copy link
Author

Okay, then it's probably due to an incompatibility with an app installed on my devices. If I find out which one it is, I'll pass the information on to you.

A follow-up to #136: I rejoiced too soon. It only worked on the first day. On the second day, I had the same errors on the Galaxy S23 as described in #136.

@BlackyHawky
Copy link
Owner

@mimaiself
I finally managed to reproduce this bug; I was just doing the test wrong.
I'll try to find a solution.

@BlackyHawky BlackyHawky removed waiting for info Further information is requested specific device Not all devices are affected by the issue labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants