Android: System-Level Understanding

Mastering Android Power Management: A Deep Dive into Doze Mode, App Standby, and Network Resilience.

Downloaded from internet

Android has evolved to become smarter about preserving battery life without compromising the user experience. Two core features that enable this are Doze Mode and App Standby. These mechanisms intelligently limit background processes to extend standby time and optimize power consumption. In this post, we’ll explore how these features work, how they affect app behavior, and how you can optimize your apps to work seamlessly within these constraints. We’ll also touch on strategies to deal with intermittent network conditions, which often go hand-in-hand with power-saving modes.

These modes affect all apps, regardless of target API level. Even if your app doesn’t target API level 23, Android 6.0+ still applies Doze and App Standby. Test your app under these conditions and adjust your code to ensure a smooth user experience. Here’s a quick look at what these modes do.

1. Doze Mode: This feature is activated when the device remains stationary and is not being actively used for a prolonged period. In Doze mode, the system significantly restricts background processes, including network activity, syncing, and alarms, to reduce battery drain. While the device is in Doze mode, apps’ access to battery-intensive resources is delayed until the maintenance window. Periodically, the system exits Doze briefly, allowing apps to complete deferred tasks. During this maintenance window, pending syncs, jobs, and alarms are executed, and apps can access the network.

Now, let’s take a closer look at what a maintenance window is:

Doze provides a recurring maintenance window for apps to use the network and handle pending activities.(taken from https://developer.android.com)

As shown in the image, when a device is idle, on battery, and the screen is off, the system enters Doze mode to save power by pausing network access, syncs, jobs, and alarms. Periodically, it briefly exits Doze during a maintenance window to let apps complete pending tasks. Once done, it returns to Doze. Over time, these maintenance windows become less frequent, further reducing battery usage during long periods of inactivity. When the user interacts with the device or connects a charger, the system exits Doze and all apps resume normal activity.

Understanding Android’s Doze Mode with a Simple Daily Life Example:

To understand it easily, think of it like how we sleep at night. When we sleep, we pause all our regular activities — we’re not checking messages, moving around, or doing any work. Similarly, when your phone is left untouched, with the screen off and running on battery, it enters Doze mode. In this state, background activities like syncing, network access, and job scheduling are paused to conserve energy.

However, just like how we occasionally wake up in the middle of the night to check the time or take a sip of water, the phone also briefly “wakes up” during what’s called a maintenance window. During this short period, it allows apps to run any pending tasks, perform syncs, trigger alarms, and access the internet. Once that’s done, it returns to Doze mode. Over time, if the phone remains idle, these maintenance windows become less frequent, helping extend battery life even further. This cycle of sleep and brief wake-ups ensures the device stays updated without draining too much power — just like how we get things done even while resting.

🔋 Doze Mode = You Sleeping

Think of your phone like you at night. When you go to sleep:

• You’re not checking notifications.
• You’re not working
• You’re resting to save energy.

That’s exactly what Doze Mode does. When your phone is idle, on battery, and the screen is off, Android gradually enters Doze mode to pause background activities like:

• Network access
• Syncs
• Jobs
• Alarms

This helps the phone save battery when it’s not in use.

🌙 Light Doze Mode = You Winding Down Before Sleep

Before falling into a deep sleep, there’s usually a winding down phase — you’re in bed, eyes closed, but still lightly aware of your surroundings. That’s similar to Android’s Light Doze Mode.

In this phase:

• The phone restricts network access, just like you putting your phone on silent.
• It ignores wake-up signals from apps, like you ignoring notifications.
• Tasks, jobs, alarms(Standard AlarmManager alarms (including setRepeating()) are deferred to the next maintenance window), and even GPS or Wi-Fi scans are postponed/defer or limited — just like how you pause work, skip notifications, and stop moving around when you’re preparing to sleep.
• Defers standard [AlarmManager](https://developer.android.com/reference/android/app/AlarmManager)alarms, including [setExact()](https://developer.android.com/reference/android/app/AlarmManager#setExact(int,%20long,%20android.app.PendingIntent)) and [setWindow()](https://developer.android.com/reference/android/app/AlarmManager#setWindow(int,%20long,%20long,%20android.app.PendingIntent)), to the next maintenance window.
• Alarms set with [setAlarmClock()](https://developer.android.com/reference/android/app/AlarmManager#setAlarmClock(android.app.AlarmManager.AlarmClockInfo,%20android.app.PendingIntent)) continue to fire normally. The system exits Doze shortly before those alarms fire.

This gentle transition helps the system conserve battery even before it enters full Doze mode.

⏰ Maintenance Window = You Waking Up Briefly

Now, imagine every few hours you wake up briefly to:

• Check your messages
• Take a sip of water
• Jot down a quick note

Then you go right back to sleep.

That’s what Android’s maintenance window does. During this short period, the system wakes up:

• Allows apps to sync
• Runs any deferred tasks or alarms
• Lets apps access the network

Once that’s done, the phone goes back into Doze mode to keep saving power.

🕒 Smarter Over Time

Just like how your sleep gets deeper if you’re undisturbed, Android also gets smarter: it starts spacing out these maintenance windows if the phone stays idle for a longer period, saving even more battery.

So next time you put your phone down, remember: it’s not just sitting there — it’s taking power naps and only waking up when it really needs to. Smart, right?

Optimizing Your App for Doze Mode:

• High-Priority FCM: Use FCM with high priority for critical, time-sensitive notifications. Use sparingly to avoid battery drain.
• WorkManager for Background Tasks: Schedule non-urgent work with WorkManager. It runs tasks during Doze-friendly windows based on defined constraints.
• Essential Alarms: Use [setAndAllowWhileIdle()](https://developer.android.com/reference/android/app/AlarmManager#setAndAllowWhileIdle(int,%20long,%20android.app.PendingIntent)) or [setExactAndAllowWhileIdle()](https://developer.android.com/reference/android/app/AlarmManager#setExactAndAllowWhileIdle(int,%20long,%20android.app.PendingIntent)) for critical alarms that must fire in Doze. However, be mindful of the battery impact and the frequency limitations (minimum interval of 9 minutes).
• Test Your App in Doze Mode: Use the bellow commands to simulate Doze mode on a test device and observe your app’s behavior. for more details, see Test Dose mode

adb shell dumpsys battery unplug
adb shell am set-inactive <packageName> true/false

• Minimize Wake Locks: Use wake locks only when necessary and release them promptly to avoid preventing Doze mode.

Be Tolerant of Delays: Design your app to gracefully handle potential delays in background tasks and notifications when the device is in Doze mode.

How Doze Mode Affects App Behaviour:

• Delayed Notifications: Background notifications may be postponed until the next maintenance window.
• Deferred Sync: Background sync tasks via JobScheduler or network triggers are delayed.
• Interrupted Tasks: Ongoing background tasks needing network or wake locks may be paused or blocked in Doze mode.
• Delayed Alarms: Time-sensitive alarms may not trigger exactly on schedule.

2. App Standby Mode:

App Standby focuses on managing apps individually based on their usage patterns. Apps that are not frequently used or actively interacted with by the user are placed into a “standby” state, which limits their background activities.This ensures that apps that aren’t in active use do not unnecessarily consume power. The system determines an app’s usage patterns and places it in one of five standby buckets:

• Active: Currently in use or recently used; no background restrictions.
• Working Set: Used regularly but not active; minor limits on background work.
• Frequent: Used occasionally; tighter restrictions on background network and jobs.
• Rare: Seldom used; strict limits on background activity and high-priority FCM.
• Restricted: High resource use or misbehavior; severe background restrictions, runs only briefly when explicitly launched.

Apps transition between these buckets based on how frequently the user interacts with them. Actions that can move an app to a more active bucket include:

• Explicitly launching the app.
• Having a foreground service running.
• Having a visible notification.
• Receiving an FCM high-priority message (can temporarily move it).

How App Standby Affects App Behavior:

• Limited Background Network Access: Apps in lower priority buckets have restricted or blocked background network access.
• Deferred Jobs: JobScheduler jobs run less frequently or may be deferred entirely.
• Alarm Restrictions: Alarms may be delayed, similar to Doze mode behavior.
• High-Priority FCM Limits: “Rare” bucket apps may face restrictions on triggering wake-ups via high-priority FCM messages.

Optimizing Your App for App Standby:

Focus on Providing Value: Encourage users to interact with your app regularly to keep it in more active standby buckets.

• Use FCM for Critical Notifications: Send important updates via FCM. Even “Rare” apps can trigger user interaction with well-crafted, relevant messages.
• Schedule Wisely with WorkManager: Use WorkManager with proper constraints (e.g., network, charging). It respects App Standby buckets and runs tasks when conditions are met.
• Avoid Background Overuse: Unnecessary background work increases the chance of your app being deprioritized.
• Test Standby Bucket Behavior: Use ADB commands to manually place your app in different standby buckets and evaluate its behavior. for more details, see Test Standby mode

adb shell am set-standby-bucket <packageName> active|working_set|frequent|rare|restricted

• Provide Clear Notifications: If your app relies on background processes, ensure that notifications are informative and encourage users to open the app if necessary.

Key Differences between Doze Mode and App Standby:

Other use cases for battery optimization settings:

In some cases, FCM alone may be insufficient, so the system allows a configurable list of apps to be partially exempt from Doze and App Standby. These apps can access the network and hold partial wake locks during these modes, though other restrictions still apply.

Users can manually exempt apps via Settings > Battery > Battery Optimization. Apps can also prompt users by invoking either:

• ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS to open the settings page, or
• ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS to request direct exemption if they meet acceptable use cases.

3. Optimizing Your App for Different Network Conditions (e.g., handling intermittent connectivity)

Dealing with varying network conditions is crucial for providing a reliable and user-friendly experience. Here are strategies to optimize your app for intermittent connectivity:

1. Graceful Error Handling and User Feedback:

• Detect Network State: Use ConnectivityManager to check connection status before making network requests.
• Handle Errors Gracefully: Catch network issues (e.g., IOException, timeouts) and show clear, user-friendly messages—avoid vague errors like “Something went wrong.”
• Retry Logic: Provide retry options for failed requests and use exponential backoff to prevent server overload during unstable connections.
• Loading Indicators: Use spinners or progress bars to indicate ongoing network activity.
• Offline Awareness: Clearly inform users when offline features are available.

2. Data Management and Synchronization Strategies:

• Caching: Use in-memory, disk-based, or libraries like Room with caching layers to store data locally, enabling offline access to previously fetched content.
• Offline Support: Ensure core features work without internet by storing data locally and syncing later when online.
• Background Sync: Use WorkManager with network constraints to sync local changes with the server once connectivity is restored.
• Delta Updates: Fetch only changed data instead of the full dataset to reduce bandwidth and improve performance.
• Optimistic Updates: Immediately reflect actions (e.g., likes) in the UI and sync in the background. If sync fails, notify the user and optionally revert the change.

3. Efficient Network Requests:

Minimize Data Usage:

• Compress Data: Use techniques like gzip to reduce request and response sizes.
• Optimize Media: Use efficient formats (e.g., WebP for images) and adaptive streaming for videos.
• Fetch Only What’s Needed: Design APIs to return only relevant data for the current screen or task.
• Prioritize Requests: Handle critical network requests first to improve responsiveness.
• Pagination & Lazy Loading: Load data in chunks as needed to avoid overwhelming the UI and network.
• Efficient Libraries: Use tools like Retrofit and OkHttp for optimized networking with features like connection pooling and request cancellation.

4. Connection Management:

• Check Connection Type: Use ConnectivityManager to detect network type (Wi-Fi, cellular, none) and adjust behavior accordingly—e.g., download high-res images only on Wi-Fi.
• Monitor Changes: Use a BroadcastReceiver (e.g., CONNECTIVITY_ACTION) to respond to connectivity changes—retry requests, update UI, etc. Balance responsiveness with battery usage.
• Use NetworkCallback (API 24+): For detailed monitoring, use ConnectivityManager.registerNetworkCallback() to receive updates on specific network capabilities and events.

5. User Experience Considerations:

• Offline Indicators: Clearly show when the app is offline or has limited connectivity.
• Queue Offline Actions: Let users perform actions offline by queuing them and syncing automatically once connection is restored.
• Data Usage Warnings: Notify users about potential data charges when performing heavy operations on cellular networks.

By implementing these strategies, your Android app can provide a more resilient and user-friendly experience even when faced with unreliable or intermittent network connectivity. Remember to prioritize the most critical functionalities for offline access and provide clear feedback to the user about the network status.

Ref. taken from https://developer.android.com/training/monitoring-device-state/doze-standby

That’s all.

Feel free to reach out to me on LinkedIn without hesitation, Cheers! 🍻