How to Inspect Content Capture and Intelligence Events on Android Using ADB dumpsys content_capture

Modern Android platforms (Android 10 through Android 15+) incorporate sophisticated on-device artificial intelligence capabilities\u2014such as Smart Text Selection, Live Caption, contextual Smart Replies, App Actions, and Now Playing song recognition. Rather than requiring applications to build custom machine learning pipelines, Android aggregates contextual screen text and interactive view hierarchies using a centralized system framework: Content Capture. Managed by ContentCaptureManagerService, the subsystem streams user interface state changes to designated, sandboxed system intelligence services. To audit what screen data is captured, inspect whitelisted intelligence packages, and debug session events, the Android Debug Bridge (ADB) provides dumpsys content_capture.

Understanding the Android Content Capture Framework

The Content Capture architecture operates transparently within application view hierarchies:

• View Tree Traversal: When an activity loads, the framework walks the view tree (ViewStructure) and records text nodes, layout bounds, and accessibility labels.
• Event Streaming: As the user scrolls, types, or navigates, the app emits granular events (TYPE_VIEW_APPEARED, TYPE_VIEW_DISAPPEARED, TYPE_VIEW_TEXT_CHANGED).
• System Intelligence Service: Events are delivered over an IPC pipe exclusively to an authorized, sandboxed system intelligence package (e.g., com.google.android.as on Pixel devices, known as Private Compute Core). This service cannot access the internet directly.
• App Exclusions (ContentCaptureSession): Developers can flag sensitive views (such as credit card numbers, OTP fields, or passwords) with IMPORTANT_FOR_CONTENT_CAPTURE_NO to prevent data collection.

Generating a Full Content Capture Diagnostics Dump

To inspect active capture sessions, registered intelligence packages, and buffer parameters across your connected Android device, execute:

adb shell dumpsys content_capture

The command outputs a structured report detailing the operational health of the content capture service.

Inspecting Authorized Intelligence Services and Whitelists

To verify which package is authorized to receive screen capture events on the device:

adb shell dumpsys content_capture | grep -A 10 "Service Info:"

The output identifies the bound intelligence daemon:

Service Info:
  Name: com.google.android.as/com.google.android.apps.miphone.aiai.common.service.AiAiContentCaptureService
  User: 0
  Disabled by default: false
  Whitelist:
    Packages: [com.android.chrome, com.google.android.apps.messaging, com.example.targetapp]
    Activities: []

Evaluating this output confirms:

• Service Component: Confirms the exact system package receiving real-time view data.
• Whitelist: If whitelisting is enforced, only specified applications are monitored by the intelligence pipeline.

Auditing Active Capture Sessions and View Events

To inspect active capture sessions currently open on the device:

adb shell dumpsys content_capture | grep -A 25 "Sessions:"

The diagnostic log exposes live session records:

Sessions:
  Session 1024:
    app: com.example.targetapp
    activity: com.example.targetapp/.MainActivity
    state: ACTIVE
    events buffered: 42
    flush reason: BUFFER_FULL
    view counts: 14 nodes captured, 2 nodes excluded

Notice 2 nodes excluded. This confirms that views flagged with IMPORTANT_FOR_CONTENT_CAPTURE_NO or password input fields were successfully withheld from the stream, preserving user privacy.

Temporarily Disabling Content Capture for Privacy Testing

If you are testing application security or need to verify how your app behaves when system intelligence hooks are offline, disable Content Capture via ADB:

adb shell cmd content_capture set temporary-service 0

To re-enable default system intelligence services:

adb shell cmd content_capture set default-service-enabled 0 true

Clearing Cached Content Capture Telemetry

To flush all buffered view structures and reset system event counters:

adb shell cmd content_capture clear-cache

This empties on-device capture queues, allowing developers to conduct clean, repeatable audits of Android UI text extraction and smart suggestion triggers.