Android 11与12前台服务问题：如何实现前后台每秒获取位置更新

Hey there, let's break down why your location tracking app is failing on Android 11 and 12—these versions introduced stricter background restrictions that often trip up location-focused apps. Here are the key fixes to try:

1. Double-Check Permission Request Flow #

Android 11+ changed how background location permissions work:

• You must first request foreground location permissions (ACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION) and get user approval before asking for ACCESS_BACKGROUND_LOCATION. Skipping this order will result in the background permission being automatically denied.
• For Android 12+, make sure you're explicitly requesting precise location if you need it—users now get a separate toggle for precise vs approximate location in the permission dialog.

Example permission request sequence:

// First request foreground location
val foregroundPermissions = arrayOf(Manifest.permission.ACCESS_FINE_LOCATION)
requestPermissions(foregroundPermissions, FOREGROUND_LOCATION_REQUEST_CODE)

// After user approves, request background location
val backgroundPermissions = arrayOf(Manifest.permission.ACCESS_BACKGROUND_LOCATION)
requestPermissions(backgroundPermissions, BACKGROUND_LOCATION_REQUEST_CODE)

2. Update Foreground Service Setup for Android 12+ #

Android 12 added specific requirements for location-focused foreground services:

• Add the FOREGROUND_SERVICE_LOCATION permission to your AndroidManifest.xml:

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

• Ensure you start the foreground service only from a user-initiated context (like an Activity button click)—starting it from the background will be blocked on Android 12+.
• Your foreground service notification must be visible and non-dismissible by default (users can still disable it later, but initial setup needs a clear, prominent notification explaining why the service is running).

3. Optimize Location Request Parameters #

Even with foreground services, Android 11+ might throttle location updates if your request isn't configured correctly:

• Use FusedLocationProviderClient with a LocationRequest set to high priority and tight intervals:

  val locationRequest = LocationRequest.create().apply {
      interval = 1000 // 1 second
      fastestInterval = 1000
      priority = Priority.PRIORITY_HIGH_ACCURACY
  }
  

• Note: On some devices, even with high priority, the system might cap updates to 1Hz in background scenarios—but foreground services should bypass this. Confirm your service is actually running in the foreground by checking the notification shade.

4. Bypass Battery Optimization #

Android 11+ aggressive battery optimization can kill your service even if it's foregrounded:

• Ask users to disable battery optimization for your app. You can redirect them to the settings with this intent:

  val intent = Intent(Settings.ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS).apply {
      data = Uri.parse("package:" + context.packageName)
  }
  startActivity(intent)
  

• Keep in mind: Google Play has strict policies for using this permission, so only use it if your app's core functionality (like continuous location tracking) absolutely requires it.

5. Check Logcat for Hidden Errors #

Don't skip checking Logcat—look for these common issues:

• Errors like Foreground service started from background mean you're violating Android 12's foreground service launch rules.
• Messages about location updates throttled indicate the system is limiting your updates, even with foreground services (this might require adjusting your request or verifying device-specific settings).
• Permission denial logs will confirm if the background location permission was actually granted.

Final Tips #

• Test on real devices, not just emulators—emulators often don't replicate real-world background restrictions accurately.
• Ensure your service isn't being killed by the system: override onTaskRemoved() in your service to log when it's terminated, and consider using WorkManager as a fallback for critical location updates if the service is killed.

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