program failure

[Plurkccc]

Timing stops after the app cuts to the background and no alert is issued.

[DeweyReed]

Hi, I need more info.

• What's your phone's manufacturer and system version?
• Did you see an error message after the timers stopped when you opened the app?
• Is there any related event on the record screen?
• Have you tried https://dontkillmyapp.com/?

[Plurkccc]

The device I'm using is Oppo A3 Pro ,the OS is Color OS15 ,I got it back up and running after allowing all background behavior of Timer Machine within the app power consumption management.The other issue is that I also installed it (https://github.com/BlackyHawky/Clock?tab=readme-ov-file),but without having to make similar settings its Timer Machine also runs and alerts properly, I don't understand what causes this difference.

[DeweyReed]

Thank you! I'm glad it works!

I installed Clock, which requested disabling battery optimization the first time I opened the app. This could be the reason. Besides, it's based on the AOSP Clock. I read the code in AOSP a long time ago. If everything hasn't changed much, it implements timers using the alarm manager, which seems more reliable under certain circumstances.

[Plurkccc]

If I turn on the system's do-not-disturb mode, Clock's timer and notifications still work fine, while Timer Machine's timer works fine but the sound and vibration of the notification step don't work.

[DeweyReed]

There is a "Sound Type" setting in the app settings. If you change it to "Alarm" or "Notification," does the app work as expected in Do-not-disturb mode?

[Plurkccc]

I'm on Do-not-disturb mode.When I switch the audio type to "Notification", the notification step doesn't work. But when I switch the audio type to "Alarm" and "Media", the notification step works fine.

One more problem, text-to-speech error: -1.The TTS software I use is MultiTTS.

I would also like to add the ability to delete run logs, as a lot of tests generate a lot of unneeded history.