android - Why do AlarmManager broadcasts get cancelled when app gets killed? -

OK, I have two broadcast receivers registered when the app is closed, then they set fire to both at the appropriate time and Do the right thing

If the app stops, then killed (say with app culler), receivers never get their broadcasts, and nothing happens.

Probably this happens if the original application is killed due to low memory, how do I ensure that those promotions have been removed / received? The API says that even if the app is killed, it should also be set on fire, does anyone else have to face this situation?

If it helps in my progress:

  & lt ;! - Receiver for alarm manager - & gt; & Lt; Receiver Android: export = "true" android: label = "Shift Roster Update Calendar." Android: name = "com.skooter.shiftroster.backend.service.UpdateCalendar" & gt; & Lt; / Receiver & gt; & Lt; Receiver Android: export = "true" Android: label = "Pastor Roster Checking Alarm." Android: name = "com.skooter.shiftroster.backend.service.SetWakeup" & gt; & Lt; / Receiver & gt;  

and nothing else in the alarm-manager / broadcaster receiver

You misunderstood the so called "work killers" APIs are exploiting, which is not used in low-memory situations "Task killer" API provides everything, including scheduled alarm.

In addition, your original app expects that there is no memory in the first place. The whole point of using AlarmManager is so that your "Parental App" is not close to taking memory when it is not doing anything.