Android Oreo启动Service的正确方式及ANR问题解决求助

Hey there, let's sort out this ANR issue you're facing with foreground services on Android Oreo (API 26)! The problem stems from Oreo's strict background service restrictions, and your current code is missing a critical step that triggers the ANR.

Why You're Getting ANR #

ContextCompat.startForegroundService() does correctly initiate the service on Oreo, but here's the catch: Android requires you to call startForeground() with a visible notification within 5 seconds of starting the service. If you skip this, the system will either kill the service immediately or throw an ANR—exactly what your Google Play Console is reporting. Additionally, if your SocketService is doing heavy work (like socket connections) on the main thread, that'll also cause ANR.

Correct Steps to Start Foreground Service on Oreo #

Follow these steps to fix the issue:

1. Declare Required Permission
   First, add the FOREGROUND_SERVICE permission to your AndroidManifest.xml (mandatory for Oreo+):

   <uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
   
   <!-- Register your service as usual -->
   <service android:name=".SocketService" />
   

2. Start the Service (Your Initial Call is Fine)
   Keep using ContextCompat.startForegroundService() to trigger the service—it's the right method for compatibility across versions:

   ContextCompat.startForegroundService(context, new Intent(context, SocketService.class));
   

3. Call startForeground() Immediately in the Service
   Inside your SocketService, you must call startForeground() within 5 seconds (best to do this in onCreate()). You also need to create a notification channel for Oreo+ (required for all notifications):

   public class SocketService extends Service {
       private static final int NOTIFICATION_ID = 1001;
       private static final String CHANNEL_ID = "SocketServiceChannel";
   
       @Override
       public void onCreate() {
           super.onCreate();
           // Launch foreground notification RIGHT AWAY to avoid ANR
           startForeground(NOTIFICATION_ID, createForegroundNotification());
       }
   
       @Override
       public int onStartCommand(Intent intent, int flags, int startId) {
           // Move ALL socket-related heavy work to a background thread!
           new Thread(() -> {
               // Your socket connection, listening logic here
           }).start();
   
           return START_STICKY; // Adjust based on your service's needs
       }
   
       private Notification createForegroundNotification() {
           // Create notification channel for Oreo+
           if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
               NotificationChannel channel = new NotificationChannel(
                   CHANNEL_ID,
                   "Socket Service",
                   NotificationManager.IMPORTANCE_LOW // Low importance so it doesn't intrude
               );
               NotificationManager notificationManager = getSystemService(NotificationManager.class);
               if (notificationManager != null) {
                   notificationManager.createNotificationChannel(channel);
               }
           }
   
           // Build the notification
           Intent mainIntent = new Intent(this, MainActivity.class);
           PendingIntent pendingIntent = PendingIntent.getActivity(
               this,
               0,
               mainIntent,
               PendingIntent.FLAG_IMMUTABLE // Use FLAG_MUTABLE if you need to update the intent later
           );
   
           return new NotificationCompat.Builder(this, CHANNEL_ID)
               .setSmallIcon(R.drawable.ic_service_notification) // Required - use your app's icon
               .setContentTitle("Socket Service Active")
               .setContentText("Listening for incoming connections")
               .setContentIntent(pendingIntent)
               .setPriority(NotificationCompat.PRIORITY_LOW)
               .build();
       }
   
       @Nullable
       @Override
       public IBinder onBind(Intent intent) {
           return null; // Return null if this is a started service (not bound)
       }
   }
   

4. Offload Heavy Work to Background Threads
   Never run socket connections, network calls, or other long-running tasks on the main thread. Use a dedicated thread, Kotlin Coroutines, or a modern concurrency library to keep the main thread responsive—this is another common cause of ANR.

Additional Notes #

• If your service finishes its task, call stopForeground(true) to remove the notification, then stopSelf() to shut down the service.
• For specific use cases (like location tracking, media playback), you might need additional permissions or use specialized foreground service types (e.g., FOREGROUND_SERVICE_LOCATION on API 29+), but the core steps above apply.

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