适配Android Oreo(API26)时钟小部件的屏幕开关广播监听方案问询

Hey there! Let's work through this broadcast adaptation issue for your clock widget—this is a super common hurdle when moving to API 26+, so I’ve got clear, actionable steps to get your widget behaving correctly while saving battery.

Why Your Old Setup Broke #

Android Oreo introduced strict background execution limits. Any service running in the background (not as a foreground service) can no longer receive most implicit broadcasts—including android.intent.action.SCREEN_ON and android.intent.action.SCREEN_OFF. While TIME_SET and TIMEZONE_CHANGED are exceptions (system allows these in the background), we’ll still adjust your registration logic to align with modern Android best practices.

Step-by-Step Solutions #

1. Handle SCREEN_ON/SCREEN_OFF: Switch to a Foreground Service

To keep listening for screen state changes, you need to upgrade your background service to a foreground service. Foreground services are exempt from Oreo's broadcast restrictions because they’re visibly active to the user (via a persistent notification).

• First, set up the foreground service:
  In your service’s onCreate() or onStartCommand() method, create a notification channel (required for API 26+) and start the service in foreground mode:

  override fun onCreate() {
      super.onCreate()
      // Create notification channel (API 26+ mandatory)
      if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
          val channel = NotificationChannel(
              "clock_widget_channel",
              "Clock Widget Service",
              NotificationManager.IMPORTANCE_LOW // Low priority to avoid distracting users
          )
          getSystemService(NotificationManager::class.java).createNotificationChannel(channel)
      }
      // Build a minimal foreground notification
      val notification = NotificationCompat.Builder(this, "clock_widget_channel")
          .setContentTitle("Clock Widget Active")
          .setContentText("Keeping your clock updated efficiently")
          .setSmallIcon(R.drawable.ic_clock) // Use your widget's icon here
          .build()
      // Start the service in foreground mode
      startForeground(1, notification)
  }
  

• Then register your screen broadcast receiver:
  Now you can safely register the SCREEN_ON/SCREEN_OFF receiver in the foreground service’s onCreate()—just like you did before, but now it’ll work on Oreo+:

  private lateinit var screenStateReceiver: BroadcastReceiver
  
  override fun onCreate() {
      super.onCreate()
      // ... foreground service setup code above ...
  
      screenStateReceiver = object : BroadcastReceiver() {
          override fun onReceive(context: Context?, intent: Intent?) {
              intent?.action?.let { action ->
                  when (action) {
                      Intent.ACTION_SCREEN_ON -> resumeClockUpdates() // Resume your clock logic
                      Intent.ACTION_SCREEN_OFF -> pauseClockUpdates() // Pause to save battery
                  }
              }
          }
      }
      val filter = IntentFilter().apply {
          addAction(Intent.ACTION_SCREEN_ON)
          addAction(Intent.ACTION_SCREEN_OFF)
      }
      registerReceiver(screenStateReceiver, filter)
  }
  
  override fun onDestroy() {
      super.onDestroy()
      // Don't forget to unregister the receiver when the service stops
      unregisterReceiver(screenStateReceiver)
  }
  

2. Handle TIME_SET/TIMEZONE_CHANGED: Bind to Widget Lifecycle

These two broadcasts are allowed in the background, but it’s better to tie their receiver to your widget’s lifecycle instead of a long-running service. This way, you only listen when the widget is active:

class ClockWidgetProvider : AppWidgetProvider() {
    private lateinit var timeChangeReceiver: BroadcastReceiver

    override fun onEnabled(context: Context) {
        super.onEnabled(context)
        // Register receiver when the first widget instance is added
        timeChangeReceiver = object : BroadcastReceiver() {
            override fun onReceive(context: Context?, intent: Intent?) {
                // Trigger a widget update when time/timezone changes
                updateClockWidget(context)
            }
        }
        val filter = IntentFilter().apply {
            addAction(Intent.ACTION_TIME_SET)
            addAction(Intent.ACTION_TIMEZONE_CHANGED)
        }
        context.registerReceiver(timeChangeReceiver, filter)
    }

    override fun onDisabled(context: Context) {
        super.onDisabled(context)
        // Unregister receiver when the last widget instance is removed
        context.unregisterReceiver(timeChangeReceiver)
    }
}

3. Bonus Optimization: Combine with TIME_TICK for Clock Updates

For a smoother clock experience, you can listen to ACTION_TIME_TICK (sent every minute) when the screen is on. Just register this receiver alongside SCREEN_ON in your foreground service, and unregister it when the screen turns off—this balances accuracy and battery efficiency.

Critical Permissions to Add #

Make sure to add these permissions to your AndroidManifest.xml:

<!-- Required for foreground services (API 28+) -->
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
<!-- Required for post notifications (API 31+) -->
<uses-permission android:name="android.permission.POST_NOTIFICATIONS" />

For API 31+, you’ll also need to dynamically request the POST_NOTIFICATIONS permission from the user.

内容的提问来源于stack exchange，提问作者Elefterios Papalimani