Apache Cordova setInterval计时变慢问题咨询（Android 7.0环境）

Hey there, I’ve helped a few developers troubleshoot exactly this issue before—let’s break down why this happens and how to fix it.

The Root Cause: Android 7.0’s Background Resource Throttling #

The key here is understanding how Android Nougat (7.0) manages background apps, especially when the screen is off:

• Initial Grace Period: When you first lock the screen, Android doesn’t immediately clamp down on your app. It gives a short grace period (usually a few minutes) where it maintains normal resource allocation for things like timers, network calls, etc. This is why your 5-second intervals work fine at first.
• Doze Mode & App Standby: After that grace period, if your device is stationary, not charging, and the app is truly in the background, Android kicks in Doze Mode (or the lighter "App Standby" state for less restrictive cases).
  • In Doze, the system pauses non-critical app processes, batches network requests, and drastically reduces timer precision. Your setInterval calls aren’t running on schedule anymore—Android groups them with other background timers and only fires them when the system wakes up briefly (which can be every 10, 15, or even 30+ seconds, depending on how deep into Doze the device is).
  • WebView (where your Cordova JS runs) gets its thread priority lowered in the background, so even if the timer tries to fire, the system might not allocate CPU time to it immediately.

Why The Delay Before Slowdown? #

Android’s background restrictions are designed to balance battery life and app functionality. It doesn’t want to kill or throttle apps the second you lock the screen—instead, it waits a few minutes to confirm the app isn’t actively doing something important (like playing music, tracking a workout, etc.). Once that window passes, it ramps up the restrictions to save battery.

Fixes to Try #

Here are the most reliable solutions for Cordova apps:

1. Use a Background Mode Plugin #

Cordova has plugins like cordova-plugin-background-mode that can keep your app’s process alive in the background and avoid Doze restrictions.

• You’ll need to configure it to request battery optimization exemptions (Android 7.0+ requires the REQUEST_IGNORE_BATTERY_OPTIMIZATIONS permission).
• Example setup snippet:

  document.addEventListener("deviceready", function() {
    cordova.plugins.backgroundMode.enable();
    // Optional: Request exemption from battery optimization
    cordova.plugins.backgroundMode.requestIgnoreBatteryOptimizations();
  }, false);
  

• Note: This isn’t a silver bullet—some manufacturers (like Samsung, Xiaomi) have their own battery saver tools that might still override this, so you may need to guide users to whitelist your app.

2. Use Android’s Native AlarmManager Instead of JS setInterval #

For precise periodic tasks, JavaScript timers are never going to be reliable in the background. Instead, use Android’s AlarmManager via a Cordova plugin (or write a small native plugin wrapper).

• AlarmManager has methods like setExactAndAllowWhileIdle() that can wake your app even in Doze Mode (though Android 7.0+ limits how often you can use exact alarms to prevent battery drain).
• If your task doesn’t need sub-minute precision, setAndAllowWhileIdle() is a better option (it’s less battery-heavy).

3. Guide Users to Whitelist Your App #

Ask users to add your app to their device’s battery optimization whitelist:

• On Android 7.0+, this is in Settings > Battery > Battery Optimization > Select your app > Don’t optimize.
• This ensures the system won’t apply Doze restrictions to your app, but it requires manual user action.

Final Notes #

Keep in mind that Android’s background rules are getting stricter with each version—even if you fix this on 7.0, newer versions might have additional restrictions. Always test on target devices, especially those with custom skins (like MIUI, One UI) which often have more aggressive battery saving features.

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