Android Studio中日历事件通知无法准时触发问题求助

核心原因 #

通知延迟或不触发的核心问题在于Android 6.0+的Doze模式/App Standby限制了普通AlarmManager.set()的触发时机，同时PendingIntent配置、闹钟API选择也会影响可靠性。

具体修复步骤 #

1. 替换为精确闹钟API #

普通set(RTC_WAKEUP)在Doze模式下会被延迟到设备退出低功耗状态才触发，需根据系统版本选用精确闹钟API：

private void setAlarm(Calendar calendar, String event, String time, int RequestCode){
    Intent intent = new Intent(context.getApplicationContext(), AlarmReceiver.class);
    intent.putExtra("event",event);
    intent.putExtra("time",time);
    intent.putExtra("id",RequestCode);
    
    // 适配Android 12+的PendingIntent不可变标记
    int pendingFlags;
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.S) {
        pendingFlags = PendingIntent.FLAG_ONE_SHOT | PendingIntent.FLAG_IMMUTABLE;
    } else {
        pendingFlags = PendingIntent.FLAG_ONE_SHOT;
    }
    PendingIntent pendingIntent = PendingIntent.getBroadcast(context, RequestCode, intent, pendingFlags);
    
    AlarmManager alarmManager = (AlarmManager) context.getApplicationContext().getSystemService(Context.ALARM_SERVICE);
    long triggerTime = calendar.getTimeInMillis();
    
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.S) {
        // Android 12+需先确认精确闹钟权限
        if (alarmManager.canScheduleExactAlarms()) {
            alarmManager.setExactAndAllowWhileIdle(AlarmManager.RTC_WAKEUP, triggerTime, pendingIntent);
        }
    } else if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
        // Android 6.0-11使用允许Doze模式下触发的API
        alarmManager.setExactAndAllowWhileIdle(AlarmManager.RTC_WAKEUP, triggerTime, pendingIntent);
    } else {
        // 低版本使用精确触发API
        alarmManager.setExact(AlarmManager.RTC_WAKEUP, triggerTime, pendingIntent);
    }
}

2. 申请必要权限 #

在AndroidManifest.xml中添加权限：

<!-- Android 12+精确闹钟权限 -->
<uses-permission android:name="android.permission.SCHEDULE_EXACT_ALARM" />
<!-- 唤醒锁权限，确保设备唤醒处理通知 -->
<uses-permission android:name="android.permission.WAKE_LOCK" />

Android 12+需动态申请精确闹钟权限：

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.S) {
    AlarmManager alarmManager = (AlarmManager) getSystemService(Context.ALARM_SERVICE);
    if (!alarmManager.canScheduleExactAlarms()) {
        Intent intent = new Intent(Settings.ACTION_REQUEST_SCHEDULE_EXACT_ALARM);
        startActivity(intent);
    }
}

3. 优化BroadcastReceiver与通知渠道 #

• 避免在onReceive中重复创建通知渠道，将渠道创建移至App启动时（如自定义Application类）：

// 自定义Application的onCreate方法中调用
private void initNotificationChannel() {
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
        String channelId = "channel_id";
        CharSequence name = "日历事件通知";
        String description = "提醒用户即将到来的日历事件";
        NotificationChannel channel = new NotificationChannel(channelId, name, NotificationManager.IMPORTANCE_HIGH);
        channel.setDescription(description);
        NotificationManager notificationManager = getSystemService(NotificationManager.class);
        notificationManager.createNotificationChannel(channel);
    }
}

• 确保AlarmReceiver在Manifest中正确注册：

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

4. 处理设备重启后的闹钟恢复 #

设备重启后已设置的闹钟会丢失，需监听开机广播重新设置：

• 添加开机广播权限：

<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />

• 注册开机广播接收器：

<receiver android:name=".BootReceiver" android:exported="true">
    <intent-filter>
        <action android:name="android.intent.action.BOOT_COMPLETED" />
        <action android:name="android.intent.action.LOCKED_BOOT_COMPLETED" />
    </intent-filter>
</receiver>

• 实现BootReceiver加载未触发的事件：

public class BootReceiver extends BroadcastReceiver {
    @Override
    public void onReceive(Context context, Intent intent) {
        if (Intent.ACTION_BOOT_COMPLETED.equals(intent.getAction()) ||
            Intent.ACTION_LOCKED_BOOT_COMPLETED.equals(intent.getAction())) {
            // 从本地存储（如Room、SharedPreferences）读取未触发的日历事件，重新调用setAlarm
        }
    }
}

5. 额外验证建议 #

• 关闭应用的电池优化：系统设置→应用→你的应用→电池→电池优化→设置为“不优化”
• 确保每个闹钟的RequestCode唯一，避免PendingIntent被覆盖

内容的提问来源于stack exchange，提问作者Sehej Kumar