setExactAndAllowWhileIdle()异常：闹钟未按指定时间触发

Hey there! Let's figure out why your alarm is firing after 3 seconds instead of the exact time you specified—I’ve dealt with similar quirks with setExactAndAllowWhileIdle() before, so here are the most likely fixes to try:

1. You’re using the wrong time unit for your trigger timestamp #

The triggerAtMillis parameter of setExactAndAllowWhileIdle() expects a millisecond-level timestamp (since the epoch). A super common mistake is accidentally passing in seconds instead of milliseconds. For example:

• Wrong: System.currentTimeMillis() + 3600 (adds 3.6 seconds, not 1 hour)
• Correct: System.currentTimeMillis() + 3600 * 1000 (adds 1 hour in milliseconds)

Double-check how you’re calculating your trigger time—if you’re using a date picker or time picker, make sure you convert the selected time to milliseconds properly.

2. Your PendingIntent is being reused incorrectly #

If you’re reusing a PendingIntent without canceling the old one first, it might be carrying over a previous (immediate) alarm request. Try these steps:

• When creating the PendingIntent, use FLAG_CANCEL_CURRENT | FLAG_IMMUTABLE (API 23+ recommends FLAG_IMMUTABLE, and API 30+ requires it for most cases). This ensures you’re creating a fresh PendingIntent each time.
• Before setting a new alarm, cancel any existing ones tied to the same PendingIntent:

  alarmManager.cancel(pendingIntent);
  

3. Your BroadcastReceiver setup has API 26+ compatibility issues #

Android 8.0 (API 26) restricted implicit broadcast receivers, which can break alarm triggers if you’re using an action-based intent. Fix this by:

• Using an explicit Intent to target your receiver directly:

  Intent intent = new Intent(this, YourAlarmReceiver.class); // No action string needed
  

• Confirming your Manifest receiver declaration is correct (mark it as non-exported unless you need external access):

  <receiver
      android:name=".YourAlarmReceiver"
      android:exported="false">
  </receiver>
  

4. You’re accidentally triggering the alarm immediately in code #

Double-check your setup logic—are you calling your receiver’s onReceive() method directly somewhere, or showing the Toast right after setting the alarm? That could make you think the alarm fired early when it actually didn’t. Add a log statement in your receiver to confirm when it’s truly triggered:

@Override
public void onReceive(Context context, Intent intent) {
    Log.d("AlarmDebug", "Alarm fired at: " + System.currentTimeMillis());
    Toast.makeText(context, "Alarm triggered!", Toast.LENGTH_SHORT).show();
}

5. Test outside Doze mode first #

Sometimes testing Doze mode incorrectly can lead to false positives. First verify your alarm works in normal mode (unplug the device, don’t touch it for a few minutes but don’t let it enter Doze). You can check if your device is in Doze with this adb command:

adb shell dumpsys deviceidle

Here’s a clean example of how to set an exact alarm with API 26+ compatibility:

AlarmManager alarmManager = (AlarmManager) getSystemService(Context.ALARM_SERVICE);
long triggerTime = System.currentTimeMillis() + 10 * 60 * 1000; // 10 minutes from now

Intent intent = new Intent(this, MyAlarmReceiver.class);
PendingIntent pendingIntent = PendingIntent.getBroadcast(
        this,
        0,
        intent,
        PendingIntent.FLAG_IMMUTABLE | PendingIntent.FLAG_CANCEL_CURRENT
);

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
    alarmManager.setExactAndAllowWhileIdle(AlarmManager.RTC_WAKEUP, triggerTime, pendingIntent);
} else {
    alarmManager.setExact(AlarmManager.RTC_WAKEUP, triggerTime, pendingIntent);
}

Start with checking the timestamp unit first—9 times out of 10, that’s the root cause of this "instant trigger" issue!

内容的提问来源于stack exchange，提问作者Tae Hyun Na