安卓应用后台时能否通过OnClickListener捕获触摸屏幕坐标？

Hey there! Let's cut to the chase: you can't use OnClickListener to capture touch events when your app is in the background or inactive—and here's why, plus the real solutions you'll need to implement.

Why OnClickListener Fails Here #

OnClickListener is tied directly to UI components within your app's foreground window. When your app moves to the background, Android removes your app's UI from the system's foreground view hierarchy. Touch events are routed exclusively to the currently active app's UI, so your OnClickListener will never receive any callbacks in this state.

Workable Solutions to Capture System-Wide Touch Events #

If you need to track touch coordinates even when your app isn't active, you'll need to use system-level services that have permission to monitor device-wide input. Here are the two main approaches:

1. Accessibility Service (Most Common & Reliable Approach) #

Android's Accessibility Service is built to assist users with disabilities, but it also lets apps listen to system-wide input events—including touches—even when your app runs in the background.

How to Implement It:

• First, declare the service in your AndroidManifest.xml with required permissions and intent filters:

  <service
      android:name=".TouchTrackingAccessibilityService"
      android:permission="android.permission.BIND_ACCESSIBILITY_SERVICE">
      <intent-filter>
          <action android:name="android.accessibilityservice.AccessibilityService" />
      </intent-filter>
      <meta-data
          android:name="android.accessibilityservice"
          android:resource="@xml/accessibility_service_config" />
  </service>
  

• Create an accessibility config file (res/xml/accessibility_service_config.xml) to specify you want to capture touch events:

  <accessibility-service xmlns:android="http://schemas.android.com/apk/res/android"
      android:accessibilityEventTypes="typeTouchEvent|typeTouchInteractionStart|typeTouchInteractionEnd"
      android:accessibilityFeedbackType="feedbackGeneric"
      android:accessibilityFlags="flagDefault"
      android:canRequestTouchExplorationMode="true"
      android:description="@string/accessibility_service_desc" />
  

• Implement the service class to handle and extract touch coordinates:

  class TouchTrackingAccessibilityService : AccessibilityService() {
      override fun onAccessibilityEvent(event: AccessibilityEvent) {
          if (event.eventType == AccessibilityEvent.TYPE_TOUCH_EVENT) {
              val motionEvent = event.parcelableData as MotionEvent
              val touchX = motionEvent.x
              val touchY = motionEvent.y
              // Use the coordinates (e.g., log them, send to your app's core logic)
          }
      }
  
      override fun onInterrupt() {
          // Handle service interruptions (e.g., system stopping the service)
      }
  }
  

• Key Notes:
  • Users must manually enable your Accessibility Service in device settings (Settings > Accessibility > Your App's Service). You'll need to guide users through this flow in your app.
  • Android enforces strict policies for Accessibility Services—misusing this capability (e.g., tracking user input without explicit consent) will get your app rejected from Google Play.

2. MediaProjection + Overlay View (For Screen Capture Use Cases) #

If your app is focused on screen recording or capturing display content alongside touches, you can combine MediaProjection (for screen capture) with a system overlay view. The overlay sits on top of all other apps and can listen to touches, but this requires your app to run a foreground service (mandatory on Android 10+).

This approach is less flexible than Accessibility Service and only works while the overlay is visible, so it's best suited for niche use cases like screen recording tools.

Critical Reminders #

• Privacy First: Capturing touch coordinates counts as sensitive user data. You must clearly disclose this usage in your privacy policy and only collect data for a legitimate, user-facing purpose.
• API Level Testing: Android 10+ tightened restrictions on background input access—test your implementation across multiple OS versions to ensure compatibility.

内容的提问来源于stack exchange，提问作者Farhan Abdul Salam