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
AlarmManager can only be used for exact alarms. #976
Comments
same |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Not stale. |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Not stale. |
Hello 👋, to help manage issues we automatically close stale issues. This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
Thank you for your contributions. |
Not stale |
I want to use inexact alarms in the Notifee library's timestamp trigger.
I would like to use
set
orsetAndAllowWhileIdle
options similar to the URL https://developer.android.com/develop/background-work/services/alarms/schedule#inexact. However, the current AlarmManager options in Notifee appear to strictly enforce the use of exact alarms.Although there are AlarmType options such as
set
andsetAndAllowWhileIdle
, based on the code, it seems that these options are effective only when using exact alarms.So, starting from Android 12, even if you set the alarm as inexact, it won't ring unless you allow 'Alarm & reminder'.
The text was updated successfully, but these errors were encountered: