Android Oreo系统中，唤醒锁能否阻止带前台服务的应用被系统杀死？

Hey there, let's tackle this head-on—Android 8 (API 26+) introduced some pretty strict background restrictions, and even foreground services can get tripped up by these rules, especially on custom ROMs like Nokia's. Here's a breakdown of the most likely issues and fixes for your EBT Music Player:

1. Mandatory Notification Channel (API 26+) #

Android 8 and above require every notification to be tied to a notification channel. If you skip this, your foreground service notification won't show up, and the system will treat your service as improperly started—leading to it getting killed quickly.

Add this code to create your channel (do this once, like in your Application class or service onCreate):

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
    val channel = NotificationChannel(
        "MUSIC_PLAYBACK_CHANNEL",
        "Music Playback",
        NotificationManager.IMPORTANCE_LOW // Use low importance to avoid intrusive alerts
    )
    channel.description = "Shows currently playing music"
    val notificationManager = getSystemService(NotificationManager::class.java)
    notificationManager.createNotificationChannel(channel)
}

2. Use startForegroundService() Instead of startService() (API 26+) #

For API 26+, you need to use startForegroundService() to launch your service, paired with calling startForeground() within 5 seconds of the service starting. This tells the system explicitly that you're launching a foreground service, which gets higher priority.

Update your service launch code:

val serviceIntent = Intent(context, YourMusicService::class.java)
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
    serviceIntent.addFlags(Intent.FLAG_FOREGROUND_SERVICE)
    context.startForegroundService(serviceIntent)
} else {
    context.startService(serviceIntent)
}

Then in your service's onCreate() or onStartCommand(), immediately call:

val notification = NotificationCompat.Builder(this, "MUSIC_PLAYBACK_CHANNEL")
    .setContentTitle("Now Playing")
    .setContentText(currentTrackName)
    .setSmallIcon(R.drawable.ic_music_note)
    .setOngoing(true) // Replaces deprecated FLAG_ONGOING_EVENT
    .build()

startForeground(NOTIFICATION_ID, notification)

3. Fix Deprecated Flags #

You mentioned using FLAG_ONGOING_EVENT—this is deprecated in API 26+. Replace it with Notification.Builder.setOngoing(true) (as shown above) to mark the notification as persistent (non-dismissible), which signals to the system that your service is actively running a critical task.

Also, FLAG_FOREGROUND_SERVICE should be added to the Intent used to start the service, not the notification itself—make sure you're applying it correctly.

4. Set the Right onStartCommand() Return Value #

Ensure your service's onStartCommand() returns START_STICKY or START_REDELIVER_INTENT. This tells the system to restart your service if it's killed unexpectedly:

override fun onStartCommand(intent: Intent?, flags: Int, startId: Int): Int {
    // Initialize foreground service and playback logic here
    return START_STICKY
}

5. Bypass Device-Specific Battery Optimization #

Nokia devices (like your Nokia 6) often have aggressive battery optimization settings that can kill even foreground services. You have two options here:

• Guide users to whitelist your app: Instruct them to go to Settings > Battery > Battery Optimization > Find EBT Music Player > Select "Don't optimize".
• Request permission to ignore battery optimization: You can ask for the REQUEST_IGNORE_BATTERY_OPTIMIZATIONS permission (note: Google Play has policies around this, so only use it if your app's core functionality requires persistent background operation—like a music player).

6. Avoid Long-Running Operations in Service Setup #

Make sure your service's onCreate() and onStartCommand() don't have any slow, blocking operations (like heavy file scans). If you need to load media files, do this on a background thread so startForeground() gets called within the 5-second window.

Following these steps should resolve the termination issue on Android 8. The biggest culprits here are usually missing notification channels or incorrect foreground service launch logic—start with those first!

内容的提问来源于stack exchange，提问作者Eric Bergman-Terrell