Detecting Running Android Applications Using ADB Commands

Introduction

Android Debug Bridge (ADB) is a versatile tool for Android development and debugging. In many scenarios, such as automation scripts or system monitoring, it is necessary to detect whether a specific application is running on a device. Given the package name, ADB offers multiple methods for this detection, but support may vary across different Android versions.

Using the ps Command (Pre-Android 7.0)

In Android versions prior to 7.0, the ps command supports filtering via the COMM option to detect running processes. For example, to check if an application with the package name com.android.phone is running, you can execute the following command:

adb shell ps m.android.phone

This command filters the process list to show only entries where the COMM value matches the last 15 characters of the package name. If the process is running, it outputs details including the PID and application name; otherwise, no output is displayed. This method is efficient but limited to older Android versions.

Using the pidof Command (Android 7.0 and Above)

Starting from Android 7.0, the COMM filter option was removed from the ps command. A more robust alternative is to use the pidof command. For instance:

adb shell pidof com.android.phone

This command returns the process ID (PID) if the process is found, or an empty string if not. It provides a straightforward way to detect running processes by name, suitable for newer Android systems.

Alternative Methods

In addition to the core methods, you can use grep and awk in combination with the ps command for detection. For example, to search for a specific package name:

adb shell ps | grep com.we7.player | awk '{print $9}'

This approach filters the ps output for the package name and extracts the ninth column, which typically contains the package name. However, due to potential variations in output format, this method is less efficient and more error-prone, recommended only as a fallback.

Furthermore, to retrieve the package name of the currently focused application, you can use the following command chain:

adb shell "dumpsys activity activities | grep mResumedActivity | cut -d '{' -f2 | cut -d ' ' -f3 | cut -d '/' -f1"

This command extracts the package name from activity dumpsys data, useful for scenarios requiring foreground application monitoring. Note that it relies on internal system structures and may vary across devices or versions.

Comparison and Recommendations

For Android 7.0 and above, the pidof command is recommended due to its simplicity and low error rate. For older systems, the ps command with COMM filtering is preferred. In automation scripts, you can combine version detection to choose the appropriate command. For example, a simple shell script snippet is as follows:

if adb shell pidof com.android.phone &> /dev/null; then
    echo "Process is running."
else
    echo "Process is not running."
fi

This code uses pidof and checks the exit status to determine process existence, enhancing robustness. In practice, it is advisable to add error handling and consider device connectivity and permissions to ensure accurate detection.