Databases
StackOverflow2013
Postsdbo
POAlarmManager triggers PendingIntent too soon
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAlarmManager triggers PendingIntent too soon
    primarykey
    data
    text
    <p>I've searched for 3 days now but didn't find a solution or similar problem/question anywhere else. Here is the deal:</p> <p>Trigger in 1 hour -> works correct</p> <p>Trigger in 2 hours -> Goes of in 1:23</p> <p>Trigger in 1 day -> Goes of in ~11:00</p> <p>So why is the AlarmManager so unpredictable and always too soon? Or what am I doing wrong? And is there another way so that it could work correctly?</p> <p>This is the way I register my PendingIntent in the AlarmManager (stripped down):</p> <pre><code>AlarmManager alarmManager = (AlarmManager)parent.getSystemService(ALARM_SERVICE); Intent myIntent = new Intent(parent, UpdateKlasRoostersService.class); PendingIntent pendingIntent = PendingIntent.getService(parent, 0, myIntent, PendingIntent.FLAG_UPDATE_CURRENT); //Set startdate of PendingIntent so it triggers in 10 minutes Calendar start = Calendar.getInstance(); start.setTimeInMillis(SystemClock.elapsedRealtime()); start.add(Calendar.MINUTE, 10); //Set interval of PendingIntent so it triggers every day Integer interval = 1*24*60*60*1000; //Cancel any similar instances of this PendingIntent if already scheduled alarmManager.cancel(pendingIntent); //Schedule PendingIntent alarmManager.setRepeating(AlarmManager.ELAPSED_REALTIME_WAKEUP, start.getTimeInMillis(), interval, pendingIntent); //Old way I used to schedule a PendingIntent, didn't seem to work either //alarmManager.set(AlarmManager.RTC_WAKEUP, start.getTimeInMillis(), pendingIntent); </code></pre> <p>It would be awesome if anyone has a solution. Thanks for any help!</p> <p>Update: 2 hours ago it worked to trigger it with an interval of 2 hours, but after that it triggered after 1:20 hours. It's getting really weird. I'll track the triggers down with a logfile and post it here tomorrow.</p> <p>Update: The PendingIntent is scheduled to run every 3 hours. From the log's second line it seems like an old scheduled PendingIntent is still running:</p> <pre><code>[2012-5-3 2:15:42 519] Updating Klasroosters [2012-5-3 4:15:15 562] Updating Klasroosters [2012-5-3 5:15:42 749] Updating Klasroosters [2012-5-3 8:15:42 754] Updating Klasroosters [2012-5-3 11:15:42 522] Updating Klasroosters </code></pre> <p>But, I'm sure I cancelled the scheduled PendingIntent's before I schedule a new one. And every PendingIntent isn't recreated in the same way, so it should be exactly the same. If not , this threads question isn't relevant anymore.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USWezelkrozum
    1. USWezelkrozum
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAlarmManager triggers PendingIntent too soon
      1. USAndrey Ermakov
      1. VTFavorite
    2. VO
      singulars
      1. POAlarmManager triggers PendingIntent too soon
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAlarmManager triggers PendingIntent too soon
      1. USmostashaar
      1. VTFavorite
    1. COI cannot recreate your problem. Exactly how do you change `start` to advance it 2 hour, also 1 day?
      singulars
      1. POAlarmManager triggers PendingIntent too soon
      1. USSam
    2. COI added the logfile and found out that probably an old PendingIntent is still running.
      singulars
      1. POAlarmManager triggers PendingIntent too soon
      1. USWezelkrozum
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload