LG K10 2017（Android 7.0）设备Foreground Service无法启动求助

Hey there, let's tackle this foreground service issue you're hitting on the LG K10 2017. Older LG devices often have stricter adherence to Android's notification and service rules, even when other brands play nice. Here are the key fixes and checks to get your service running:

1. Ditch Deprecated Notification APIs (The Likely Culprit) #

Your current code uses the old Notification constructor and SetLatestEventInfo method—both deprecated since API 11. While many manufacturers still tolerate these, LG's Android 7.0 implementation probably rejects them outright (since a valid notification is mandatory for foreground services to start).

Replace your RegisterForegroundService method with this updated version using NotificationCompat.Builder (make sure you have the Xamarin.Android.Support.v4 NuGet package installed):

void RegisterForegroundService()
{
    // Optional but safe: Create a notification channel (required for API 26+, harmless for 24)
    if (Build.VERSION.SdkInt >= BuildVersionCodes.O)
    {
        var channel = new NotificationChannel(
            "SMART_DELIVERY_CHANNEL", 
            "Foreground Service Updates", 
            NotificationImportance.Default
        );
        var notificationManager = (NotificationManager)GetSystemService(NotificationService);
        notificationManager.CreateNotificationChannel(channel);
    }

    // Build a compliant notification
    var notificationBuilder = new NotificationCompat.Builder(this, "SMART_DELIVERY_CHANNEL")
        .SetSmallIcon(Resource.Drawable.SmartDeliveryAppIcon)
        .SetContentTitle("Smart Delivery")
        .SetContentText("waiting ....")
        .SetContentIntent(pendingIntent)
        .SetOngoing(true); // Mark as ongoing for foreground service

    var ongoingNotification = notificationBuilder.Build();

    // Use a unique static ID for the notification (avoid using NotificationFlags values here)
    StartForeground(1001, ongoingNotification);
}

2. Fix PendingIntent Flags #

On Android 7.0, using 0 as the PendingIntent flag can cause unexpected failures. Update your PendingIntent creation to:

pendingIntent = PendingIntent.GetActivity(this, 56, intent, PendingIntentFlags.UpdateCurrent);

UpdateCurrent ensures that if the PendingIntent already exists, its intent is refreshed with the latest data—this is more reliable for foreground service notifications.

3. Wrap Service Setup in a Try-Catch to Catch Silent Errors #

LG devices sometimes fail silently without crashing the app. Add error logging to spot issues:

public override StartCommandResult OnStartCommand(Intent intent, StartCommandFlags flags, int startId)
{
    try
    {
        if (shared.Readbool("work_in_bg")) 
        {
            RegisterForegroundService();
        }
    }
    catch (Exception ex)
    {
        Android.Util.Log.Error("ForegroundServiceError", $"Failed to start service: {ex.Message}\n{ex.StackTrace}");
    }

    Thread thread = new Thread(new ThreadStart(request_new_orders));
    thread.Start();
    background_active = true;

    return StartCommandResult.Sticky;
}

4. Check Logcat for Clues #

Connect the LG K10 2017 to Android Studio or run adb logcat to filter for your app's logs. Look for errors like:

• "Notification does not meet Android standards"
• "Failed to start foreground service"
• Permission-related warnings (less likely on API 24, but worth checking)

These logs will give you direct insight into what's blocking the service.

Most likely, switching to NotificationCompat.Builder will fix your issue—older LG devices are notoriously strict about deprecated APIs. Give these changes a test and let me know how it goes!

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