[Libero 5G II] Taskkilling Issues

[jpgjm]

Bug description

Even if you set an alarm, it may not ring.

When you set an alarm on your device, an alarm icon appears in the status bar.

However, sometimes the alarm icon disappears. This may be why the alarm isn't working.
This suggests that the OS is killing tasks on its own.

As a workaround for some devices, could you please add an option for a ground notification or witchdog function to let us know that it's running?

Steps to reproduce

1. Set an alarm.
2. Sleep until the alarm goes off.
3. Sometimes the alarm doesn't go off.

If the time until the alarm is due to go off is short, it will ring.

Pre-installed (manufacturer-specific) alarm apps do work.

Logs (optional but highly recommended)

Please wait a moment.
This will occur irregularly.

App version

Clock 2.28

Install Source

GitHub

Device model

Libero 5G II(A103ZT)

Android version

Android 12

Checklist

• I searched for existing issues (open and closed) before filing this report.
• I have read and understood the contribution guidelines.
• I have provided all required details. I understand that the feature request will be dismissed otherwise.

[BlackyHawky]

@jpgjm
Hi,

Apart from aggressive optimization of your device, I can't see where this could be coming from.

[jpgjm]

Battery optimization is disabled.

The following permissions are enabled:

1. Auto-launch app
2. Related load
3. Background running

I think I've done everything I can.

[jpgjm]

I think it's the OS's fault.

As a workaround for some devices, could you please add an option for a ground notification or witchdog function to let us know that it's running?

[BlackyHawky]

@jpgjm
The behavior you’re describing is very likely caused by the battery‑optimization system on your device.
The alarm icon in the status bar is controlled entirely by Android, not by the app. When the icon disappears, it usually means the system has restricted or stopped the app in the background, which prevents scheduled alarms from working reliably. This is unfortunately common on some devices, especially when aggressive power‑saving rules are enabled.

Adding a permanent notification wouldn’t fully solve the issue. Even with a foreground notification, some devices still apply their own restrictions and may stop background processes anyway. I prefer not to add a permanent notification, as it would change how the app behaves without guaranteeing a real improvement.

The most effective solution is to adjust the battery or background‑activity settings on your device so the app is allowed to run normally. Once the system stops restricting it, the alarm icon should remain visible and alarms should work as expected.

Do you see the same behavior with other alarm apps as well?

[jpgjm]

The chrono app will work correctly if you turn on "show Foreground Notification" in the settings.

I haven't used the following apps for long, but they seemed to work fine while I was using them.
・Alarm Klock
・Simple Alarm Clock

The following apps have stopped working from time to time:
・Clock You
・Fossify Clock Beta

[jpgjm]

Alarm not sounded log

Clock_debug_log_2026_01_21_06-01-27.zip

[BlackyHawky]

@jpgjm

Alarm not sounded log

Very strange because the log says the opposite for the alarm set at 5:00 a.m.:

2026-01-20 05:00:00 [INFO] Clock: Setting fire state to instance 1
2026-01-20 05:00:00 [DEBUG] Events: [Alarm] [Fire]
2026-01-20 05:00:00 [VERBOSE] Clock: AlarmService.start with instance: 1
2026-01-20 05:00:00 [VERBOSE] Clock: AlarmKlaxon.start() with MediaPlayer
2026-01-20 05:00:00 [DEBUG] AsyncRingtonePlayer: Executing play
2026-01-20 05:00:00 [DEBUG] AsyncRingtonePlayer: AsyncRingtonePlayer - Playing ringtone URI: ...
...
2026-01-20 05:00:00 [VERBOSE] AsyncRingtonePlayer: Scheduling volume adjustment
2026-01-20 05:00:00 [VERBOSE] Clock: Ringtone crescendo 0.01% complete (scalar: 0.010006, volume: -39.994400 dB)
2026-01-20 05:00:00 [VERBOSE] Clock: Ringtone crescendo 0.05% complete (scalar: 0.010025, volume: -39.978668 dB)
2026-01-20 05:00:00 [VERBOSE] Clock: Ringtone crescendo 0.09% complete (scalar: 0.010042, volume: -39.964001 dB)
...
2026-01-20 05:02:30 [VERBOSE] Clock: Ringtone crescendo 99.93% complete (scalar: 0.996934, volume: -0.026669 dB)
2026-01-20 05:02:30 [VERBOSE] Clock: Ringtone crescendo 99.97% complete (scalar: 0.998711, volume: -0.011200 dB)
2026-01-20 05:03:14 [VERBOSE] AlarmActivity: onTouch started ...
2026-01-20 05:03:14 [VERBOSE] AlarmActivity: Dismissed: AlarmInstance{mId=1, mYear=2026, mMonth=0, mDay=20, mHour=5, mMinute=0, ...
...
2026-01-20 05:03:14 [VERBOSE] Clock: AlarmService.stop with instance: 1
2026-01-20 05:03:14 [VERBOSE] Clock: AlarmKlaxon.stop() MediaPlayer
2026-01-20 05:03:14 [DEBUG] AsyncRingtonePlayer: Executing stop

The same applies to the alarm set for 6:00 a.m.

The log even says that you dismissed both alarms by sliding the button to “Dismiss.”

Your screenshot was taken at 6:01 a.m. and, as indicated in the log, you dismissed the alarm at 6:00:38 a.m. So there is nothing unusual about the notification icon no longer being present:

2026-01-20 06:00:38 [VERBOSE] AlarmActivity: onTouch ended
2026-01-20 06:00:38 [VERBOSE] AlarmActivity: Dismissed: AlarmInstance{mId=2, mYear=2026, mMonth=0, mDay=20, mHour=6, mMinute=0...
2026-01-20 06:00:38 [VERBOSE] Clock: Clearing notifications for alarm instance: 2

[jpgjm]

Wait a moment. The alarm went off on January 20th. However, the alarm for 5:00 and 6:00 on January 21st didn't go off.

[jpgjm]

Your screenshot was taken at 6:01 a.m.

This photo was taken on today's date, January 21st.