How to launch the Android emulator in Android Studio

Development of mobile applications requires constant testing of functionality on different versions of the operating system and hardware configurations. Physical devices are essential for final testing, but quick access to virtual environments is critical during the initial stages of debugging and prototyping. Google's toolkit provides a powerful solution - a built-in emulator that allows you to simulate the operation of a real smartphone or tablet right on your computer.

Running a virtual device opens up the ability for the developer to instantly switch between different screen resolutions, API versions and hardware characteristics. You don't need to buy a dozen gadgets from different brands to make sure that your interface displays correctly everywhere. Correctly setting up the environment saves hours of routine work and allows you to focus on writing high-quality code.

The process of integrating the emulator into the workflow begins immediately after installing the integrated development environment. Modern versions of the software are as automated as possible, but for stable operation they require proper configuration of system resources. In this article we will analyze in detail all the stages: from creating the first virtual device to fine-tuning parameters to achieve maximum performance.

It is worth noting that the correct operation of the emulator directly depends on the capabilities of your hardware and installed drivers. If you have difficulty starting, the reason most often lies in disabled virtualization in the BIOS or insufficient RAM. We will pay special attention to these technical nuances so that you can avoid common beginner mistakes.

Preparing the development environment and system requirements

Before you start creating a virtual device, you need to make sure that your system is ready for the loads that emulation creates. Android Studio is a resource-intensive application that requires a significant amount of RAM. memory and free disk space. The minimum requirements are often specified as underestimated, so for comfortable work it is recommended to have at least 16 GB of RAM and a processor that supports virtualization technologies.

The key component for fast operation of the emulator is hardware virtualization technology. On processors Intel it is called VT-x, and on AMD — AMD-V. Without enabling this feature in the BIOS/UEFI, the emulator will either not start or will run extremely slowly using software emulation of processor instructions.

⚠️ Attention: If you are using third-party hypervisors (such as VirtualBox or VMware) simultaneously with Android Studio, driver conflicts may occur. In such cases, it is recommended to disable third-party virtual machines while working with the emulator or use Hyper-V compatibility mode if it is supported by your version of the SDK.

It is also important to check for the latest updates for SDK Tools. The component Android Emulator regularly receives updates that improve compatibility with new versions of the operating system and correct graphics rendering bugs. Outdated versions of the tools may incorrectly display the interface of modern applications.

Installing components via SDK Manager

The process of installing the necessary tools is carried out through the built-in package manager. To access the components you need, open your development environment settings and go to the SDK management section. Here you will see a list of available platforms, build tools and system images.

You will need to find the tab SDK Tools and make sure that there is a checkmark next to the item Android Emulator . If the component is not installed, the system will prompt you to download and install it. The weight of the package can reach several gigabytes, since it includes binary files of the emulator and libraries for interacting with the guest OS.

• 📦 Open the menu Tools → SDK Manager in the top bar of the app.
• 💾 Go to the tab SDK Tools and mark check mark Android Emulator.
• 🔄 Click the button Apply and wait until the files are downloaded and installed.
• ✅ After installation, restart the development environment to apply the changes.

Special attention should be paid to choosing the installation path. By default, all components are loaded into the user's system directory, which can quickly fill up the C drive. If you have an additional partition with a lot of free space, it makes sense to change the SDK path in the settings to avoid problems with low space in the future.

Creating and configuring a virtual device (AVD)

After installing all the necessary components, you can proceed to creating the device itself. For this purpose, there is a special manager in the development environment - AVD Manager (Android Virtual Device). It allows you to configure hardware parameters, select the operating system version and configure peripherals.

You can launch the manager through the toolbar by clicking on the smartphone icon, or through the menu Tools → Device Manager. In the window that opens, you will see a list of already created devices. To add a new one, click the button Create Device. A setup wizard will open in front of you, consisting of several steps.

At the first stage, you need to select a device profile. The list includes many preset configurations that simulate popular phone and tablet models from various manufacturers. You can select a device with a specific screen resolution, pixel density (DPI) and the presence of physical buttons.

Device model	Screen resolution	Pixel density	Screen size
Pixel 6	1080 x 2400	411 dpi	6.4 inches
Pixel Tablet	1600 x 2560	320 dpi	10.95 inches
Nexus 5X	1080 x 1920	420 dpi	5.2 inches
Wear OS Round	454 x 454	328 dpi	1.38 inches

The choice of a specific model affects how your application will look to end users. For example, testing on a device with a screen cutout or dynamic island will help ensure that important UI elements are not obscured by system areas. Don't limit yourself to just the latest models - support for older resolutions is also important to reach a wide audience.

Choice of system image and architecture processor

The second step of the setup wizard is devoted to selecting the operating system version. You will be offered a list of available images (System Images), sorted by API level. It is recommended to select images marked Google Playif your application requires Google services such as maps or notifications.

The processor architecture is a critically important parameter. For modern computers based on x86_64 you should choose images labeled x86 or x86_64. Using architecture images ARM on conventional PCs will lead to extremely low performance, since the system will have to emulate the instructions of another processor programmatically.

If the required Android version is not in the list, you can download it directly from this window by clicking on the link Download next to the version name. After downloading, the image will appear in the list of available for installation. Please note that new versions of Android may require more powerful hardware for the GUI to run smoothly.

⚠️ Attention: Images marked "ARM" should only be used if you are developing an application for specific devices with this architecture or testing native libraries compiled exclusively for ARM. In all other cases, this will lead to interface slowdowns.

It is also worth paying attention to the availability of images without Google Play if you want to test the application on devices without pre-installed services of the search giant. This is relevant for developers working in markets where Google services are limited, or for creating custom firmware.

Why are x86 images faster?

X86 images use hardware virtualization of your processor (Intel VT-x or AMD-V), executing instructions directly. ARM images require translation of instructions, which creates a huge load on the CPU and reduces operating speed by 5-10 times.

Configuring hardware parameters and graphics

At the final stage of creating a device, you can configure its hardware characteristics in detail. By default, the system offers balanced settings, but they can be changed for specific tasks. Particular attention should be paid to the distribution of RAM and the number of processor cores allocated to the emulator.

In the hardware settings section (Hardware Profile) you can change the amount of RAM, internal memory and even add an SD memory card. However, you should not allocate too many resources: if you give the emulator all the free memory, the main operating system will start using the page file, which will slow down the entire computer.

A separate settings block is dedicated to graphics. The parameter Graphics defines how the image is rendered. Several modes are available:

• 🎨 Automatic —the system itself selects the best rendering method based on your hardware.
• 🖥️ Hardware - GLES 2.0/3.0 —uses the computer's video card to accelerate graphics (recommended).
• 💻 Software - GLSwiftShader —emulates graphics with the processor (slow, used for debugging drivers).

For For most game development tasks and heavy interfaces, you need to select the Hardwaremode. This will allow you to use the powerful GPU of your video card to render animations and 3D objects. If artifacts appear on the screen in this mode, you can try switching to Software, but be prepared for a drop in FPS.

Launch the emulator and control the console

After completing the setup, click the button Finish. The new device will appear in the manager's list. To launch it, just click the Play button (green triangle) next to the device name. The boot process can take from a few seconds to a minute depending on the speed of your drive (SSD speeds up this process significantly).

After boot, you will see the familiar Android lock screen. The emulator is controlled both with the mouse and with the keyboard. The development environment provides a toolbar on the side or bottom of the emulator window, duplicating the physical buttons of the device: home, back, menu, volume control and screen rotation.

For advanced users, an emulator console is available that allows you to control the device through text commands. You can connect to it via telnet or using the tool adb (Android Debug Bridge). This allows you to automate tests, change geolocation, simulate calls and manage battery status programmatically.

adb shell am start -n com.android.settings/.Settings

This command, for example, opens settings inside the running emulator. Knowledge of basic commands adb significantly expands debugging capabilities, allowing you to install applications, record logs and take screenshots without using a graphical interface.

⚠️ Attention: The interface and set of available commands in Android Studio can be updated with the release of new versions of the IDE. If you do not find the described button or menu, check the documentation for your specific version of the development environment or use the settings search (Ctrl+Shift+A).

Frequent problems and ways to solve them

Despite the streamlined process, users may encounter a number of typical problems when they first start. One of the most common is the error “HAXM is not installed” or messages that virtualization is not available. In this case, you need to go back to the BIOS settings and activate the appropriate technologies.

Another common problem is a black screen at startup or endless loading. This is often due to low disk space or corrupted emulator cache. Clearing device data (Wipe Data in the device action menu) usually solves this problem by resetting the emulator to its factory state.

If the emulator is running slowly, check if there are other heavy applications running at the same time. Also make sure that the antivirus does not scan emulator files in real time, since constantly checking disk images can greatly slow down data input/output. Adding the SDK folder to antivirus exceptions often gives a performance boost.

How to reset the emulator to factory settings?

In Device Manager, click on the three dots next to the device name, select "Wipe Data". This will remove all installed applications and user data inside the virtual device, but will preserve its configuration.

Why does the emulator not start and gives an error about virtualization?

Most likely, virtualization technology (VT-x or AMD-V) is disabled in the BIOS of your computer. This function may also be occupied by another hypervisor, for example, Hyper-V on Windows. Try disabling Hyper-V through "Turn Windows components on or off" or use the command bcdedit /set hypervisorlaunchtype off in the command line as an administrator.

How to change the interface language inside the emulator?

The language changes in the standard way, as on a real phone: go to Settings → System → Languages & input → Languages. If the language you need is not in the list, click "Add a language" and select it. After that, drag it to the top position of the list.

Is it possible to run several emulators at the same time?

Yes, Android Studio allows you to run several virtual devices in parallel. This is useful for testing interaction between applications or checking operation on different versions of Android. However, each additional emulator consumes a significant amount of RAM and processor resources.

Where are the files of created emulators stored on disk?

By default, emulator data is stored in the user directory. On Windows, the path usually looks like C:\Users\UserName\.android\avd. There you will find files with the extension .ini and folders with image data. It is not recommended to edit these files manually without understanding the structure.

How to take a screenshot of the emulator screen?

In the toolbar of the emulator window there is a button in the form of a camera. Clicking on it saves the screenshot to the default folder. You can also use the command adb shell screencap -p /sdcard/screen.png and then download the file to your computer via adb pull.