Android Oreo下电池警报应用长时间运行Service的实现方法咨询

Hey there! I get it, dealing with Android Oreo's background restrictions can be a real headache—especially when you're trying to build a battery alert app that needs to trigger when the battery's full. Let's break down what might be going wrong and how to fix it, tailored to your minSDK 15 and targetSDK 27 setup.

首先，排查startForegroundService的正确用法 #

If you've already used startForegroundService but it's still failing, chances are one of these steps was missed:

• Timing is critical: After calling startForegroundService(), your Service must call startForeground() within 5 seconds—otherwise the system will kill your Service immediately. Make sure this call happens right in onCreate() or onStartCommand() of your Service, no delayed operations allowed.
• Don't skip Notification Channels: Oreo (API 26+) requires every notification to be tied to a channel. If you haven't created one, your foreground notification won't show up, and the system will reject your startForeground() call. Here's how to create a channel (run this in your Application class or before starting the Service):

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
    val channel = NotificationChannel(
        "battery_alert_channel",
        "Battery Alert",
        NotificationManager.IMPORTANCE_LOW
    ).apply {
        description = "Tracks battery status for full charge alerts"
    }
    val notificationManager = getSystemService(NotificationManager::class.java)
    notificationManager.createNotificationChannel(channel)
}

• Add the FOREGROUND_SERVICE permission: For targetSDK 27, this is a normal permission (no runtime request needed), so just add it to your AndroidManifest.xml:

<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />

替代方案：用JobScheduler适配Oreo的后台限制 #

Oreo's background restrictions make long-running Services impractical for most cases. Instead, JobScheduler (introduced in API 21) is designed for tasks that need to run under specific conditions—like when the battery is charging and full. It plays nicely with system optimizations, so your app won't get throttled.

Step 1: Create a JobService #

This is the component that will run when your job is triggered:

class BatteryFullJobService : JobService() {
    override fun onStartJob(params: JobParameters?): Boolean {
        // Check if battery is fully charged
        val batteryIntent = registerReceiver(null, IntentFilter(Intent.ACTION_BATTERY_CHANGED))
        val status = batteryIntent?.getIntExtra(BatteryManager.EXTRA_STATUS, -1)
        
        if (status == BatteryManager.BATTERY_STATUS_FULL) {
            // Play your alert sound here
            playAlertSound()
        }
        
        // We're done, no need to keep the job alive
        jobFinished(params, false)
        return false
    }

    override fun onStopJob(params: JobParameters?): Boolean {
        // Don't retry if the job is stopped
        return false
    }

    private fun playAlertSound() {
        val mediaPlayer = MediaPlayer.create(this, R.raw.battery_alert)
        mediaPlayer.start()
        mediaPlayer.setOnCompletionListener { it.release() }
    }
}

Don't forget to declare this in your manifest:

<service
    android:name=".BatteryFullJobService"
    android:permission="android.permission.BIND_JOB_SERVICE" />

Step 2: Schedule the Job #

Call this code when your app starts (e.g., in your main Activity's onCreate()) to set up the job trigger:

fun scheduleBatteryAlertJob(context: Context) {
    val jobScheduler = context.getSystemService(JOB_SCHEDULER_SERVICE) as JobScheduler
    val jobInfo = JobInfo.Builder(
        1001, // Unique job ID
        ComponentName(context, BatteryFullJobService::class.java)
    )
        .setRequiresCharging(true) // Trigger only when device is charging
        .setMinimumLatency(1000) // Wait 1s before first check
        .setOverrideDeadline(5000) // Ensure job runs within 5s of meeting conditions
        .build()
    
    jobScheduler.schedule(jobInfo)
}

兼容低版本设备（API <21） #

Since your minSDK is 15, for devices running Android 4.4 or lower, you can fall back to a regular Service with foreground mode. Use version checks to handle this:

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
    // Use startForegroundService + JobScheduler
} else {
    // Start a regular Service and call startForeground() immediately
    startService(Intent(this, BatteryAlertService::class.java))
}

Final Checks #

• Make sure your app isn't marked as "battery optimized" in system settings—this can block JobScheduler from running. If needed, you can prompt users to disable optimization, but try to avoid this unless absolutely necessary.
• Test the flow thoroughly: Plug in a device, let it charge to 100%, and verify the alert plays. Check logcat for any errors if it doesn't work (look for messages about Service termination or notification channel issues).

内容的提问来源于stack exchange，提问作者Lokik Soni