How to add a virtual device to AVD Manager Android Studio: a complete guide

Developing mobile applications for Android requires constant testing on different devices. But buying dozens of smartphones to check compatibility is irrational. This is where AVD Manager (Android Virtual Device Manager), built into Android Studio, comes to the rescue. This tool allows you to create virtual emulators with various characteristics: from old versions of Android to the latest updates, from low-power devices to flagship smartphones.

However, many developers - especially beginners - have difficulty setting up AVD. How to properly add a new virtual device? Which settings should I choose for optimal performance? Why might the emulator not start? In this article we will analyze the process of creating an AVD taking into account the current requirements of Android Studio 2026+and also give recommendations for eliminating common errors.

What is AVD Manager and why do you need it

AVD Manager (Android Virtual Device Manager) is a tool v Android Studio, which allows you to create and manage virtual devices for testing applications. Essentially, this is an emulator that simulates the operation of a real smartphone or tablet on your computer.

Main tasks of AVD:

• 📱 Testing on different versions of Android - from Android 4.4 KitKat to the last Android 15 (at the time of writing).
• 🔄 Checking interface adaptability for different screen resolutions (from 320×480 to 1440×3200).
• 🛠️ Debugging without a physical device - convenient if you don’t have all smartphone models at hand.
• 🔒 Safe testing — you can experiment with system settings without the risk of “breaking” the real device.

Without AVD, the developer would have to buy or rent dozens of devices, which is not always possible. However, virtual devices also have limitations: they can work slower than real smartphones and do not support some hardware functions (for example, NFC or IR Blaster).

⚠️ Attention: The performance of the emulator directly depends on the power of your PC. If you have a weak processor or little RAM, the AVD may slow down or not start at all. In such cases, consider alternatives like Genymotion or testing on physical devices.

Preparing Android Studio to work with AVD

Before adding a virtual device, make sure that your Android Studio is ready to work with emulators. Here's what you need to check:

1. Is Android Emulator installed?

   Open File → Settings → Appearance & Behavior → System Settings → Android SDK. The tab SDK Tools should contain a checkmark opposite Android Emulator. If it is not there, install the component.

2. Are the system images downloaded?

   In the same window, go to tab SDK Platforms and make sure that images for the required versions of Android are downloaded (for example, Android 13.0 (Tiramisu) or Android 14.0 (Upside Down Cake)).

3. Is the path to the SDK configured?

   Check the environment variable ANDROID_HOME —it should point to the folder with the Android SDK (usually this C:\Users\UserName\AppData\Local\Android\Sdk on Windows or /Users/UserName/Library/Android/sdk on macOS).

If anything from this list is missing, Android Studio will offer to download the missing components automatically when you first launch AVD Manager. However, it is better to prepare in advance to avoid delays.

Step-by-step guide: how to add a new virtual device

Now let's move on to the main thing - creating an AVD. add a virtual device to Android Studio:

1. Open AVD Manager

   Run Android Studio and click on the icon AVD Manager in the upper right corner (the icon with a phone and an arrow) or select Tools → Device Manager.

2. Click "Create Virtual" Device"

   In the window that opens, click on the button Create Virtual Device (or + Create Device in new versions).

3. Select a device category

   You will be prompted to select the device type:

   • 📱 Phone - smartphones (for example, Pixel 7 or Samsung Galaxy S23).
   • 📺 Tablet - tablets (for example, Nexus 9 or Samsung Galaxy Tab S8).
   • 🖥️ TV - Android TV (for example, NVIDIA SHIELD).
   • ⌚ Wear OS - smart watches (for example, Wear OS Square).
   • 🚗 Automotive —automotive systems (for example, Automotive 1024p).

4. Select a specific model

   After selecting a category, you will be offered a list of devices with different screen resolutions and pixel densities (dpi). For example, for smartphones the following are popular:

   • Pixel 6 Pro (resolution 1440×3120, 512 dpi).
   • Pixel 5 (resolution 1080×2340, 440 dpi).
   • Nexus 5X (resolution 1080×1920, 420 dpi) - suitable for testing on weak devices.

5. Select the system image (System Image)

   At this stage you need to specify the Android version. Options available:

   • 📦 Recommended —images with Google Play Services (needed for testing applications that use Google services).
   • 📱 x86_64 or ARM —processor architecture is better to choose x86_64 (works faster).
   • 🔄 Release Name — version code name (for example, Tiramisu for Android 13).

   If the desired image is not in the list, click Download next to it.

6. Configure AVD settings

   After selecting the image, a window with additional settings will open:

   • Device name (AVD Name) — come up with a unique name (for example, Pixel_6_Android14).
   • Orientation (Portrait/Landscape) — select the starting screen orientation.
   • Camera (Front/Back) — emulation of the front and rear cameras (you can select VirtualScene for test pictures).
   • GPU (Graphics) — for better performance select Hardware - GLES 2.0.

Optimizing emulator performance

Even on powerful PCs, the Android emulator can run slowly. Here are several ways to speed it up:

If the emulator is still slow, try:

• 🔄 Reduce the number of CPU cores in the AVD settings (the default is 2–4, try 1–2).
• 🗑️ Clear the emulator cache via .android/avd (delete the folder with the name of your AVD and create the device again).
• 🔌 Use Android Studio Electric Eel or later —in the latter versions, work with emulators is optimized.

Typical errors when working with AVDs and their solutions

Even experienced developers encounter problems when setting up AVDs. Here are the most common errors and ways to correct them:

1. Error: "No system images installed for this target"

Cause: The system image for the selected version of Android has not been downloaded. Android Studio The system image for the selected Android version has not been downloaded.

Solution:

• Open SDK Manager (Tools → SDK Manager).
• Go to the SDK Platforms tab and download the desired version (for example, Android 13.0).
• Return to AVD Manager and repeat creating the device.

2. Error: "Emulator: emulator: ERROR: x86 emulation currently requires hardware acceleration!"

Cause: Hardware virtualization is disabled on your PC (VT-x for Intel or AMD-V for AMD).

Solution:

• Restart your computer and go to BIOS/UEFI (usually by pressing the F2, Del or Esc at startup).
• Find the option Virtualization Technology (or SVM Mode for AMD) and turn it on.
• For Windows, also check whether Windows Hypervisor Platform is enabled in the system components.

3. Error: "The emulator process for AVD was killed"

Cause: Not enough RAM or emulator conflicts with other apps (for example, with Docker or VirtualBox).

Solution:

• Close all resource-intensive applications (browsers, IDEs, games).
• Reduce the volume RAM for AVD in the settings (for example, from 2048 MB to 1536 MB).
• Try to run the emulator with the flag -no-snapshot (to do this, open a terminal in the folder with the SDK and run the command:

  emulator -avd Your_AVD_Name -no-snapshot

⚠️ Attention: If you are using macOS, make sure that you have the latest version installed Android Studio and the drivers for Apple Silicon (M1/M2) are updated (for example, for Apple Silicon) may require additional settings.

4. Error: "Failed to allocate memory: 8"

Cause: The system cannot allocate enough memory for the emulator (often found on Windows with a 32-bit system or when there is insufficient virtual memory).

Solution:

• Increase the page file in Windows settings (at least 4 GB recommended).
• Run Android Studio as administrator.
• Try creating an AVD with less RAM (for example, 1024 MB instead of 2048 MB).

AVD Manager Alternatives: When to Use Other Emulators

Although AVD Manager is a standard tool for Android developers, in some cases it is worth consider alternatives:

If you need to test the application on a rare version of Android (for example Android 4.0 Ice Cream Sandwich) or on a device with a non-standard resolution, Genymotion may be the best choice. Suitable for games or applications with high graphics requirements BlueStacks.

Tips for managing multiple AVDs

If you are working on multiple projects or testing an application on different versions of Android, you will need several virtual devices. Here's how to simplify their management:

• 📂 Group devices by projects - for example ProjectX_Pixel5_Android13, ProjectX_GalaxyTab_Android12This will help you avoid confusion. settings.
• 🔄 Use snapshots —in the AVD settings you can enable state saving (Quick Boot) so that the emulator starts faster.
• 🗑️ Delete unnecessary AVD —old devices take up disk space (each - from 1 to 5 GB). To delete, click on the arrow next to the AVD and select Delete.
• ⚙️ Export and import configurations - if you need to transfer the AVD settings to another PC, copy the folder with the device from .android/avd.

For convenience, you can create a batchscript (for Windows) or a shellscript (for macOS/Linux) that will launch the required AVDs with one command. Example script for Windows:

@echo off
cd %ANDROID_HOME%\emulator
emulator -avd Pixel_6_Android14 -netdelay none -netspeed full
emulator -avd Galaxy_Tab_Android12 -netdelay none -netspeed full

Save this file as start_emulators.bat and launch it when you need to quickly deploy multiple emulators.

FAQ: Frequently asked questions about working with AVD Manager

emulator -avd. Name_of_your_AVD

emulator -avd Pixel_5_Android13 -writable-system

emulator -avd Your_AVD_Name -dns-server 8.8.8.8,8.8.4.4