currently, timestamp-trigger in android, only has basic support for alarmManager
it would be helpful to have all types of alarms available, instead of just allowWhileIdle option
my suggestion is changing TimestampTriggerAlarmManager type, with having a key for setting type of alarm ("set" | "setExact" | "setAndAllowWhileIdle" | "setExactAndAllowWhileIdle" | "setAlarmClock") and another option for setting launch intent for alarm icon (when using setAlarmClock just like you can with actions (fullscreen aciton and press action)
this allows for finer control over execution
background:
I'm specifically interested in "setAlarmClock" part of it, as my use case is very similar to alarm
because I think using an alarm clock will probably reduce the chances of getting your app killed by the OS (especially in well known brands)
currently my phone (Xiaomi) kills the app whenever it wants and I have no control over it, and I assume many other have the same problem, here's part of a log I found when a trigger was about to show a notification (there's not much log surrounding it, it just outright kills the app):
ProcessManager: LockScreenClean: kill-background com.github.meypod.al_azan
So I think changing the alarm type affects if the app gets killed or not
plus I'd like to have an indicator of an alarm being set, which is the alarm clock icon shown by android
currently, timestamp-trigger in android, only has basic support for alarmManager
it would be helpful to have all types of alarms available, instead of just allowWhileIdle option
my suggestion is changing
TimestampTriggerAlarmManagertype, with having a key for setting type of alarm ("set" | "setExact" | "setAndAllowWhileIdle" | "setExactAndAllowWhileIdle" | "setAlarmClock") and another option for setting launch intent for alarm icon (when usingsetAlarmClockjust like you can with actions (fullscreen aciton and press action)this allows for finer control over execution
background:
I'm specifically interested in "setAlarmClock" part of it, as my use case is very similar to alarm
because I think using an alarm clock will probably reduce the chances of getting your app killed by the OS (especially in well known brands)
currently my phone (Xiaomi) kills the app whenever it wants and I have no control over it, and I assume many other have the same problem, here's part of a log I found when a trigger was about to show a notification (there's not much log surrounding it, it just outright kills the app):
ProcessManager: LockScreenClean: kill-background com.github.meypod.al_azanSo I think changing the alarm type affects if the app gets killed or not
plus I'd like to have an indicator of an alarm being set, which is the alarm clock icon shown by android