Android Kotlin Navigation Component场景下Activity后台返回重启问题及后台保活方案咨询

Hey there, let's work through this problem together—since you're new to Android development, I'll keep things practical and avoid overly technical jargon where I can.

First, let's clarify why your app is restarting when you come back from the background: Android's system is designed to reclaim memory for foreground apps when resources are tight. If your app's process is in the background with no active foreground components (like a foreground service), it's a prime candidate for being killed. Your Login Activity redirect is likely because your app's process was terminated, so when you reopen it, it starts from the launch component (which is your Login screen).

Now, let's go through the solutions you're considering, plus some other approaches that fit your use case (Bluetooth + background tasks):

1. 优先使用前台服务（Foreground Service） #

This is the most reliable way to keep your app's core logic (like Bluetooth communication) running in the background without getting killed. Foreground services have higher priority in the system, and they require a persistent notification (so users know your app is running in the background—this is a system requirement for Android 8.0+).

Here's a quick breakdown of how to implement it:

• Create a subclass of Service (let's call it BluetoothForegroundService).
• In the service's onStartCommand method, create a notification (use NotificationCompat.Builder for compatibility) and call startForeground(NOTIFICATION_ID, notification) to mark it as a foreground service.
• Bind your Activity to this service so you can communicate between the UI and the Bluetooth logic. This way, even if the Activity is destroyed, the service keeps running.
• Don't forget to request the necessary permissions:
  • Add <uses-permission android:name="android.permission.FOREGROUND_SERVICE" /> in your AndroidManifest.xml.
  • For Android 12+, you'll also need the POST_NOTIFICATIONS permission (request it at runtime like other dangerous permissions).

Pro tip: Since you're using AsyncTask, consider migrating to Kotlin Coroutines or WorkManager within the service—AsyncTask is deprecated and has lifecycle issues that can cause memory leaks if not handled carefully.

2. 优化Activity状态保存（缓解重启体验） #

If you don't need to keep the Activity itself alive (just want to avoid jumping back to Login when the app restarts), you can save and restore your Activity's state:

• Override onSaveInstanceState(Bundle outState) to save critical data (like user session info, Bluetooth connection state) into the bundle.
• Override onRestoreInstanceState(Bundle savedInstanceState) or use getIntent().getExtras() in onCreate to restore that data when the Activity is recreated.
• This won't prevent the system from killing your app, but it will let you resume from where the user left off instead of starting over at Login.

3. Widgets are not a replacement for background logic #

Widgets (App Widgets) are primarily for displaying information on the home screen—they can't keep an Activity alive. If you want a widget to show Bluetooth status or interact with your app, you'll still need a background service (like the foreground service above) to handle the actual Bluetooth communication. The widget can send broadcasts to the service to trigger actions, but it won't keep your Activity from being destroyed.

4. Avoid common pitfalls with AsyncTask #

Since you're using AsyncTask with Bluetooth:

• Never hold a strong reference to your Activity in the AsyncTask—this causes memory leaks when the Activity is destroyed. Use a WeakReference instead, or better yet, move the AsyncTask logic into the foreground service (since services have a longer lifecycle).
• For long-running background tasks, WorkManager is a better alternative—it's designed to handle tasks that need to run even if the app is closed or the device is restarted.

Final Notes #

Remember: Android's system is built to manage resources efficiently, so trying to "force" an Activity to stay alive in the background is against best practices and might get your app flagged for misbehavior on Google Play. Foreground services are the legitimate way to keep critical background logic running, as they're transparent to users (via the notification).

Start with the foreground service approach—it aligns with your Bluetooth SDK needs and will solve the restart issue for your core functionality.

内容的提问来源于stack exchange，提问作者Bruno Sosa Fast Tag