Software development for mobile platforms requires a secure testing environment, and it is Android Virtual Device (AVD) that solves this problem by allowing you to run applications on a virtual device directly on your computer. Modern versions of the development environment Android Studio possess powerful tools that greatly simplify the process of creating and managing simulators of various models of smartphones and tablets. You don't need to buy dozens of physical gadgets to check the code's compatibility with different screen resolutions or operating system versions.
However, beginners often encounter difficulties during the first initialization, since the process includes several stages: from installing the necessary SDK components to fine-tuning hardware parameters. Incorrect configuration can cause the system to run slowly or completely fail to start the virtual machine. In this material, we will analyze in detail each step necessary for successful deployment emulator in your production environment.
Preparing the development environment and checking components
Before you start creating a virtual device, you need to make sure that your installation Android Studio contains all required modules. Often, a standard installation includes only a basic set of tools, while the emulator requires a separate package Android Emulatorthat may not be available by default. Open the package manager through the menu Tools → SDK Manager and go to the SDK Toolstab to check the status of installed components.
If you see that the emulator component is not checked or has the status "Not installed", it must be downloaded and integrated into the system. This process may take some time depending on the speed of your Internet connection, as the downloaded files may be several hundred megabytes in size. It is also recommended to update Android SDK Build-Tools to the latest stable version to avoid compatibility conflicts when launching new system images.
⚠️ Attention: Make sure that you have at least 10 GB of free space available on your system drive (usually drive C). Virtual devices take up a significant amount of memory, and running out of space can cause critical errors when creating an image or running it.
After installing all components, restart the development environment for the changes to take effect. Now your system is ready to create the first virtual device, and you can proceed to the next stage of configuration through a specialized device manager.
Launch Device Manager and create a new device
To manage virtual machines in the environment, a tool is used Device Manager, which provides a convenient interface for creating, editing and deleting device profiles. You can open it by clicking on the phone icon in the right toolbar or by selecting Tools → Device Manager in the main menu. In the window that opens, you will see a list of already created devices, as well as a button Create device to add a new profile.
At the first stage of the creation wizard, you will be asked to select the physical model of the device from an extensive list, including phones, tablets, foldable devices and even Wear OS watches. Each profile has preset characteristics, such as screen size, pixel density (DPI) and the presence of sensors. The choice of a specific model depends on the target audiences you are developing the application for.
After selecting the hardware, press the button Nextto proceed to selecting the system image. Here it is important to pay close attention to the version Android API levelas it determines the functionality and limitations of the operating system inside the emulator. It is recommended to select images marked Recommendedas they are the most stable and optimized for the current version of the studio.
Selecting a system image and processor architecture
A critically important point when setting up is choosing the correct processor architecture for the system image. To ensure maximum performance on computers with processors Intel or AMD you must select images marked x86 or x86_64. These images use hardware virtualization of the host, which allows the emulator to work at high speeds close to the real device.
If you select an architecture image ARM, the emulator will be forced to emulate processor instructions in software, which will lead to extremely low performance and the inability to work comfortably. In the list of available images, look for the column ABI and make sure that it says x86_64. Also pay attention to the presence of the mark Google Playif you need access to the application store inside the virtual machine.
| Image type | Architecture | Performance | Recommendation |
|---|---|---|---|
| x86_64 | 64-bit Intel/AMD | High (hardware) | Main choice for PC |
| ARM64 | 64-bit ARM | Low (software) | Only for specific tests |
| x86 | 32-bit Intel | Medium | For old projects |
| armeabi-v7a | 32-bit ARM | Very low | Not recommended |
In some cases, you may need to download an image that is not in the default list. To do this, click on the link Download next to the desired version of Android in the selection wizard. The system will offer to download the image file, after which it will become available for selection and installation on a virtual device.
Use images marked "Google APIs" if your application requires access to Google services (maps, notifications), but does not need a full-fledged Play Store. This will save system resources.
Configuring hardware parameters and graphics
At the final stage of creating the device, the wizard will offer to configure the hardware characteristics of the virtual machine. By default, the system offers optimal values, but for heavy applications or game testing you may need to change them. Particular attention should be paid to the parameter Graphics, which determines the way the interface is rendered.
Value Automatic usually works correctly, but if you encounter artifacts on the screen or interface slowdowns, try switching the mode to Hardware - GLES 2.0/3.0. This will force the emulator to use your computer's video card to render graphics, which will significantly improve the smoothness of animations. Here you can also change the amount of RAM (RAM) and the internal memory of the device (Internal Storage).
⚠️ Attention: The interface and available functions of the emulator may change with the release of new versions of Android Studio. If you do not find the described menu items, check the current documentation on the official Android developer portal.
For advanced users You can configure the number of processor cores allocated to the emulator. Increasing this parameter can speed up the compilation of code inside the virtual machine, but you should not allocate more than half of the available cores of your physical processor so as not to “strangle” the main operating system.
Launch the emulator and debug applications
After completing the setup, click the button Finish, and the new device will appear in list Device Manager. To launch, click on the triangular button Play in the line with the device name. The download process can take from 30 seconds to several minutes depending on the power of your computer and the type of storage (SSD significantly speeds up loading).
When the emulator is fully loaded and displays the Android desktop, you can launch your applications on it directly from development environment. Select the created device in the drop-down list next to the project launch button (Run) and initiate the build. The application will be installed on the virtual device automatically, and you will see its interface on the screen.
☑️ Ready to launch the application
During the process, you can use the emulator toolbar to simulate various events: incoming calls, changing screen orientation, changing location (GPS) and battery level. These tools are located in the floating panel to the right of the emulator window and allow you to test the application’s response to external influences without using physical hardware.
Solving common problems and optimization
One of the most common problems when starting is an error related to the lack of virtualization support in the BIOS. the emulator does not start and displays an error message HAXM is not installed or similar, you need to go to the BIOS settings of your computer and enable virtualization technology (Intel VT-x or AMD-V). Without this hardware acceleration, the emulator cannot work.
Also, users often encounter a lack of disk space when updating system images. In this case, it is recommended to clear the emulator cache through the menu Actions → Wipe Data in the device manager. This action will reset the state of the virtual device to factory settings, deleting all installed applications and user data, but will free up space and may solve problems with unstable operation.
What to do if the emulator is slow?
If even after enabling virtualization the emulator is slow, try lowering the screen resolution in the device settings or switching the graphics mode to Software. Also make sure that the antivirus does not scan the emulator image files in real time, as this creates a huge load on the disk.
For maximum performance, it is recommended to store the emulator image files on a solid state drive (SSD). Mechanical hard drives (HDD) have a low random read speed, which is critical for the operation of the Android file system and leads to long loading times and interface freezes.
⚠️ Attention: The "Cold Boot Now" function completely reboots the emulator, ignoring the saved state (snapshot). Use it if the device freezes or behaves incorrectly after a long period of operation.
Frequently asked questions (FAQ)
Is it possible to run the emulator without virtualization enabled in the BIOS?
Technically this is possible, but the performance will be catastrophically low, making work impossible. The emulator will run in software processor emulation mode, resulting in speeds of several frames per second. It is strongly recommended to enable VT-x or AMD-V in the BIOS.
How to change the interface language inside the running emulator?
Go to the emulator settings (Settings), select the section System → Languages & input → Languages. Add the language you want and drag it to the top of the list. The changes will be applied immediately after confirmation.
Why doesn’t the emulator see my physical Android device?
The emulator and the physical device are different entities. If you want to debug the application on a real phone, select it from the list of devices before launching. Make sure that the mode is turned on on your phone USB debugging and the drivers are installed.
How to take a screenshot of the emulator screen?
In the emulator toolbar (on the right), click on the camera icon. The screenshot will be saved to the default folder or offered for saving through a dialog box. You can also use the key combination configured in the studio settings.
Where are the emulator image files stored on disk?
By default, the files are stored in the user directory: C:\Users\User_Name\.android\avd on Windows or ~/.android/avd on macOS and Linux. There you will find files with the extension .ini and folders with device data.