Android应用锁屏长期运行后UI消失但Service存活，是否为系统杀死UI？

Hey there, let's break down exactly what's happening with your Android app—this is a super common scenario tied to how Android manages memory and component lifecycles. Here's the breakdown:

1. Android's Priority-Driven Memory Reclamation #

Android’s top priority is keeping the system responsive, so it constantly ranks app processes by priority to free up RAM when needed. Your app’s UI (built with Activity components) falls into a lower priority tier when the app is in the background (like after locking the screen for days).

• When the system needs memory, it will destroy idle Activity instances first. But if your Service is still running, the app’s underlying process gets a higher priority, so it stays alive. That’s why your service keeps working even though the UI is gone.

2. Activity vs. Service Lifecycle Differences #

Activity components are tightly tied to the visible UI—their lifecycle is directly linked to whether the user can see them. Once you lock the screen, your Activity goes through onPause() → onStop(), and if the system needs resources, it will trigger onDestroy() to wipe the UI instance.

• Services, by contrast, are designed to run independently of the visible UI. Even a regular background service has higher survival priority than a background Activity. If you’ve set your service as a foreground service (with a persistent notification), it’s even less likely to be touched by the system’s cleanup.

3. Doze Mode & App Standby (Android 6.0+) #

For devices running Android 6.0 (API 23) or newer, long periods of idle time trigger Doze Mode, which limits background activity to save battery. While Doze is gentle with running services (especially if they’re whitelisted), it aggressively cleans up unused background Activity instances to cut down on resource usage.

• App Standby, another battery-saving feature, also restricts apps that haven’t been actively used. This can lead the system to discard the Activity state entirely, forcing you to relaunch the UI when you wake the device.

Is the System Killing the UI? #

Yes, but not the entire app process. The system is destroying the Activity (your UI component) to free up memory, but since your Service is still running, the app’s core process remains intact. When you relaunch the app, the system creates a brand new Activity instance, but your existing Service continues running without interruption.

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