求助：AlarmManager每20秒重复告警及启停校验代码检查

首先得明确一个关键背景：从Android API 19（KitKat）开始，系统对setRepeating()的行为做了调整——系统会根据电池优化策略自动调整重复间隔，这就是你遇到"重复间隔因设备而异"的核心原因。如果需要严格的20秒重复触发，不能依赖setRepeating()，得用精确闹钟+手动重复的方式。

下面逐个分析你的代码片段：

一、启动监控的代码问题与改进 #

原代码：

public void StartMoniterning() { 
    try { 
        Alarammanager = (AlarmManager) getSystemService(Context.ALARM_SERVICE); 
        Intent alarmIntent = new Intent(this, AppMoniteringBroadCastReceiver.class); 
        alarmIntent.putExtra("id", 1314); 
        pendingIntent = PendingIntent.getBroadcast(this, 1314, alarmIntent, PendingIntent.FLAG_UPDATE_CURRENT); 
        Alarammanager.setRepeating(AlarmManager.ELAPSED_REALTIME_WAKEUP , 0, 2*10000, pendingIntent); 
        Toast.makeText(this, "Starting Monitering", Toast.LENGTH_LONG).show(); 
    } catch (Exception e) { 
        e.printStackTrace(); 
    } 
}

存在的问题： #

1. 变量名拼写错误：Alarammanager应该是AlarmManager（虽然不影响运行，但属于不规范写法）
2. API 19+重复间隔不精确：setRepeating()的间隔会被系统调整，无法保证严格的20秒
3. PendingIntent Flag兼容性问题：在Android 12（API 31）及以上，必须指定FLAG_IMMUTABLE或FLAG_MUTABLE，否则会抛出异常
4. 初始延迟设置为0：ELAPSED_REALTIME_WAKEUP是基于系统启动时间的，设置0会立即触发一次闹钟，如果你希望第一次触发也等待20秒，应该用SystemClock.elapsedRealtime() + 20*1000

改进后的代码： #

public void startMonitoring() { 
    try { 
        AlarmManager alarmManager = (AlarmManager) getSystemService(Context.ALARM_SERVICE); 
        Intent alarmIntent = new Intent(this, AppMoniteringBroadCastReceiver.class); 
        alarmIntent.putExtra("id", 1314); 
        // 适配API 31+的Flag，这里用IMMUTABLE因为Intent不需要后续修改
        int flags = PendingIntent.FLAG_UPDATE_CURRENT | PendingIntent.FLAG_IMMUTABLE;
        PendingIntent pendingIntent = PendingIntent.getBroadcast(this, 1314, alarmIntent, flags); 
        
        long triggerAtMillis = SystemClock.elapsedRealtime() + 20 * 1000;
        // 用精确闹钟保证触发时间，API 23+支持后台休眠时也触发
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
            alarmManager.setExactAndAllowWhileIdle(AlarmManager.ELAPSED_REALTIME_WAKEUP, triggerAtMillis, pendingIntent);
        } else if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
            alarmManager.setExact(AlarmManager.ELAPSED_REALTIME_WAKEUP, triggerAtMillis, pendingIntent);
        } else {
            // 低版本可以用setRepeating，不过尽量统一逻辑
            alarmManager.setRepeating(AlarmManager.ELAPSED_REALTIME_WAKEUP, triggerAtMillis, 20*1000, pendingIntent);
        }
        
        Toast.makeText(this, "Starting Monitoring", Toast.LENGTH_LONG).show(); 
    } catch (Exception e) { 
        e.printStackTrace(); 
    } 
}

同时，需要在AppMoniteringBroadCastReceiver的onReceive()方法里，再次设置下一次闹钟，实现重复触发：

@Override
public void onReceive(Context context, Intent intent) {
    // 这里执行你的告警逻辑
    
    // 再次设置下一次精确闹钟
    AlarmManager alarmManager = (AlarmManager) context.getSystemService(Context.ALARM_SERVICE);
    Intent nextIntent = new Intent(context, AppMoniteringBroadCastReceiver.class);
    nextIntent.putExtra("id", 1314);
    int flags = PendingIntent.FLAG_UPDATE_CURRENT | PendingIntent.FLAG_IMMUTABLE;
    PendingIntent pendingIntent = PendingIntent.getBroadcast(context, 1314, nextIntent, flags);
    
    long nextTrigger = SystemClock.elapsedRealtime() + 20 * 1000;
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
        alarmManager.setExactAndAllowWhileIdle(AlarmManager.ELAPSED_REALTIME_WAKEUP, nextTrigger, pendingIntent);
    } else if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
        alarmManager.setExact(AlarmManager.ELAPSED_REALTIME_WAKEUP, nextTrigger, pendingIntent);
    }
}

二、取消闹钟的代码问题与改进 #

原代码：

private void cancelAlaram() { 
    try { 
        Alarammanager = (AlarmManager) getSystemService(Context.ALARM_SERVICE); 
        Intent i = new Intent(getBaseContext(), AppMoniteringBroadCastReceiver.class); 
        PendingIntent pendingIntent = PendingIntent.getBroadcast( 
            getApplicationContext(), 1314, i, 0); 
        Alarammanager.cancel(pendingIntent); 
        pendingIntent.cancel(); 
    } catch (Exception e) { 
        e.printStackTrace(); 
    } 
}

存在的问题： #

1. PendingIntent Flag不匹配：取消时用的flag是0，和启动时的FLAG_UPDATE_CURRENT（加上IMMUTABLE）不一致，可能导致找不到对应的PendingIntent，取消失败
2. 变量名拼写错误：Alarammanager同样拼写错误

改进后的代码： #

private void cancelAlarm() { 
    try { 
        AlarmManager alarmManager = (AlarmManager) getSystemService(Context.ALARM_SERVICE); 
        Intent i = new Intent(getBaseContext(), AppMoniteringBroadCastReceiver.class); 
        // 必须和启动时的Flag完全一致
        int flags = PendingIntent.FLAG_UPDATE_CURRENT | PendingIntent.FLAG_IMMUTABLE;
        PendingIntent pendingIntent = PendingIntent.getBroadcast( 
            getApplicationContext(), 1314, i, flags); 
        alarmManager.cancel(pendingIntent); 
        pendingIntent.cancel(); 
    } catch (Exception e) { 
        e.printStackTrace(); 
    } 
}

三、检查闹钟是否运行的代码问题与改进 #

原代码：

public boolean isAlaramManagerExist() { 
    Intent myIntent = new Intent(HomeActivity.this, AppMoniteringBroadCastReceiver.class); 
    return (PendingIntent.getBroadcast(HomeActivity.this, 1314, myIntent, PendingIntent.FLAG_NO_CREATE) != null); 
}

存在的问题： #

1. Flag不匹配：同样需要和启动时的Flag保持一致，否则可能返回错误的结果（比如启动时用了IMMUTABLE，检查时没加，可能找不到PendingIntent）
2. 变量名拼写错误：AlaramManager拼写错误

改进后的代码： #

public boolean isAlarmManagerRunning() { 
    Intent myIntent = new Intent(HomeActivity.this, AppMoniteringBroadCastReceiver.class); 
    int flags = PendingIntent.FLAG_NO_CREATE | PendingIntent.FLAG_IMMUTABLE;
    return PendingIntent.getBroadcast(HomeActivity.this, 1314, myIntent, flags) != null; 
}

额外注意事项 #

• 权限问题：从Android 12（API 31）开始，设置精确闹钟需要申请SCHEDULE_EXACT_ALARM权限，在Manifest中添加：

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

  并且在代码中动态申请（如果是后台场景）
• 电池优化：某些厂商的电池优化会阻止闹钟触发，建议引导用户将应用加入白名单

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