Resolving Android Studio Emulator Running But Not Showing in Device Selection

Problem Description and Background

During Android application development, developers often encounter situations where the emulator has started successfully but does not appear in the Choose a Running Device dialog. This typically indicates a connection or recognition issue between Android Studio and the running emulator.

Core Issue Diagnosis

The primary checkpoint is the compatibility between project configuration and emulator settings. In the build.gradle file, it is essential to verify that the targetSdkVersion and minSdkVersion values are compatible with the emulator's API level. For instance, if the emulator runs on API 30 while the project's minSdkVersion is set to 31, incompatibility will occur.

Below is a typical build.gradle configuration example:

android {
    compileSdkVersion 33
    defaultConfig {
        applicationId "com.example.myapp"
        minSdkVersion 21
        targetSdkVersion 33
        versionCode 1
        versionName "1.0"
    }
}

In this configuration, minSdkVersion 21 indicates the minimum API level supported by the application, while targetSdkVersion 33 shows that the app is optimized for API 33. If the emulator's API version is below 21 or above 33 with compatibility issues, the device may not appear in the list.

ADB Integration Settings Adjustment

Android Debug Bridge (ADB) integration is a critical component for communication between Android Studio and devices. In some cases, disabling and re-enabling ADB integration can resolve device recognition problems. The specific operation path is: Tools > Android > Enable ADB Integration. Uncheck this option, wait a few seconds, and then recheck it to force ADB to rescan connected devices.

This operation is equivalent to executing the following ADB command sequence in the terminal:

adb kill-server
adb start-server
adb devices

These commands restart the ADB service and re-list all connected devices, including emulators.

Environment Restart Strategy

When the above methods are ineffective, a full development environment restart often proves successful. This involves closing Android Studio, terminating all related background processes (such as the ADB server), and then restarting Android Studio and the emulator. This action clears potential temporary states or resource locks.

On Windows, use Task Manager to ensure all adb.exe processes are terminated; on macOS or Linux, use the following command:

pkill -f adb

After restarting, launch the emulator first, wait for it to fully run, and then execute the Run App operation in Android Studio.

Additional Troubleshooting Methods

Referencing other developers' experiences, device driver issues are more common with physical device connections, but in emulator scenarios, checking Android Studio's log output (via View > Tool Windows >> Logcat) can provide more detailed error information. Additionally, ensure the emulator uses the latest system image, as outdated images may cause compatibility problems.

If the issue persists, consider creating a new AVD (Android Virtual Device) instance to avoid potential corruption in the current configuration. In the AVD Manager, deleting the current emulator and recreating one with the same or higher API level often resolves issues caused by configuration errors.

Summary and Best Practices

A systematic approach to resolving the emulator not showing issue includes: verifying project configuration compatibility, adjusting ADB integration settings, performing environment restarts, and checking log information. By following these steps, developers can efficiently restore normal development workflows. Regularly updating Android Studio and SDK components, along with using stable emulator images, are effective strategies to prevent such problems.