Running a mobile operating system on a desktop computer opens up unique opportunities for developers and enthusiasts. You can test applications, study architecture Android or simply use your favorite instant messenger on the big screen without having to buy an additional device. Emulation via VirtualBox is one of the safest and most flexible methods that does not require any risk to the main system.
The installation process Android x86 is fundamentally different from the usual installation of Windows or Linux distributions. There is no graphical installer with a “Next” button, and setting up virtual hardware requires understanding the specifics of the emulator’s operation. In this material we will analyze in detail each stage: from loading the image to the first boot of the desktop.
Why choose this method? Unlike heavy emulators like BlueStacks or NoxPlayer, a pure system based on VirtualBox consumes fewer resources and gives full access to system settings. You get a “bare” Android, which can be modified to suit any needs by installing root access or custom kernels.
Preparing the image and software
The first step is to download the necessary software. You will need the latest version Oracle VM VirtualBoxcompatible with your operating system. For the Android system itself, we need a project Android-x86that ports the mobile OS code for the architecture of Intel and AMD processors.
Go to the official website of the project and select the appropriate ISO image. Pay attention to the bit depth: for modern computers, always select version 64-bit. If your processor is very old, you may need 32-bit version, but support for such systems is gradually being discontinued by developers.
⚠️ Attention: Download images only from the official SourceForge repository or the android-x86.org website. Files from third-party trackers may contain malicious code or be modified versions with unstable operation.
After downloading the file, check its checksum (MD5 or SHA256), if such information is provided by the developer. This ensures data integrity and no errors when writing to the virtual disk. A damaged ISO file is the most common cause of errors during the installation phase.
Use a download manager to download the image, as files can weigh more than 1 GB and the connection may be interrupted.
Creating and setting up a virtual machine
Run VirtualBox and click the button "Create". In the creation wizard, specify the machine name, for example, Android_X86. Select the operating system type Linux, and the version - Other Linux (64-bit) or Ubuntu (64-bit), since there is often no separate item for Android in the list.
RAM allocation is a critical parameter. The minimum acceptable value for comfortable work is 2048 MB (2 GB). If you have a supply of resources, allocate 4 GB, this will significantly speed up the operation of the interface and the launch of heavy applications.
At the stage of creating a virtual hard disk, select the type VDI (VirtualBox Disk Image) and storage format “Dynamic”. This means that the file on the physical disk will grow as it fills up, rather than immediately taking up all the allocated space. The recommended size is from 16 to 32 GB.
Before starting, you need to go to the settings of the created machine. In the "System" section of the "Processor" tab, increase the number of cores to 2 or 4. In the "Display" section, increase the video memory to the maximum (usually 128 MB) and enable 3D acceleration if available.
☑️ Virtual machine settings
The process of installing the system on a virtual disk
Connect the downloaded ISO image in the virtual machine media settings and run it. In the boot menu, select Installation - Install Android-x86 to harddisk. Do not select LiveCD mode if your goal is a full installation with data saved.
After loading the installer, you will see a list of partitions. Most likely, the disk will be empty. Select item Create/Modify partitions. The utility cfdiskwill open. You need to create a new partition: select [ New ], then [ Primary ], leave the default size and select [ Bootable ]. At the end, select [ Write ], enter yes to confirm and exit via [ Quit ].
Now select the created partition (usually sda1) and confirm the formatting. The file system ext4is recommended as it is the most stable for the Linux kernel used in Android. When asked about installing the GRUB boot loader, answer Yes.
⚠️ Attention: Be extremely careful when choosing a partition to format. Make sure that you do not accidentally select a virtual disk with important data from another virtual machine, if there are several of them.
When asked about setting the directory /system in Read/Write mode, also answer in the affirmative. This will allow you in the future to change system files, remove pre-installed applications and gain root access without rebuilding the image.
What to do if the installer does not see the disk?
If the list of partitions is empty or gives an error, try enabling port 0 in the virtual machine’s SATA controller settings and connecting a virtual hard disk to it. Sometimes changing the controller type to IDE helps, although SATA is preferable for speed.
Initial configuration and launch
After installation is complete, select Run Android-x86 or reboot the machine, having previously disabled the ISO image in the media settings. When you first start the system, it will perform a basic initialization of the hardware. This may take from 1 to 5 minutes depending on the speed of your physical drive (SSD or HDD).
You will see the familiar Android welcome screen. Select a language, connect to a Wi-Fi network. The virtual machine emulates a network card, so the Internet should work immediately if the host computer is connected to the network. To enter text, use a physical keyboard, switching the layout with a keyboard shortcut.
Sign in to your Google account. This is necessary to access Google Play Store and synchronize data. If sign-in fails due to device certification errors, you may need to install GApps (Google Apps) separately, but recent versions of Android-x86 often have them built-in.
| Parameter | Recommended value | Minimum value |
|---|---|---|
| RAM | 4096 MB | 2048 MB |
| Video memory | 128 MB | 64 MB |
| CPU cores | 2-4 cores | 1 core |
| Disk space | 32 GB | 8 GB |
The first launch of the system is always slower than subsequent ones due to application optimization and cache creation. Don't panic if the interface slows down in the first minutes.
Solving problems with graphics and resolution
One of the most common problems is incorrect screen resolution or lack of hardware acceleration. If the image is stretched or the interface is slow, you may need to change your graphics settings. In the virtual machine menu, go to Devices → Insert guest OS add-ons disk image.
However, for Android-x86 standard VirtualBox add-ons are not suitable. The solution lies in the settings of the virtual machine itself before launch. In the “Display” section, the graphics controller must be set to VBoxVGA or VMSVGAmode. Experiment with these modes, as support varies by Android version.
If graphics artifacts persist, you can try changing the resolution via the command line at boot. In the GRUB menu, press the key e to edit boot options. Find the line starting with kerneland add the parameter UVESA_MODE=1920x1080 or other desired resolution to the end.
⚠️ Attention: VirtualBox interfaces and Android-x86 versions are updated. The location of menu items or driver names may vary. If the setting does not work, check the documentation for the specific version of the emulator.
OpenGL debugging mode is available for advanced users. In the virtual machine settings, enable Enable 3D Acceleration. This is critical for running games and heavy applications. Without this checkbox, many apps will simply close at startup.
If the mouse gets stuck inside the virtual machine window, use the right Ctrl key (Host Key) to release the cursor and return control of the main system.
Performance optimization and network
For maximum speed, it is recommended to use network mode Network Bridge (Bridged Adapter) instead of NAT. This will allow the virtual machine to get its own IP address on your local network, which simplifies ADB debugging and accessing files from other devices.
To activate USB debugging (emulated as a network), go to Settings → For Developers and enable the appropriate item. Now you can connect to the emulator from a physical smartphone or another PC through the command adb connect.
adb connect 192.168.1.XX:5555Regularly clear the application cache, as the virtual disk can fill up quickly. Use built-in cleaning tools or third-party utilities like SD Maid. Remember that writing speed to a virtual disk is always lower than to a physical SSD.
Using Android x86 on VirtualBox is a powerful tool for training and testing. It allows you to isolate potentially dangerous applications from the main system and experiment with settings without fear of “bricking” your main smartphone.
Why does the Google Play Market not work?
In some builds of Android-x86, Google services are not installed by default due to licensing restrictions. You need to download the package OpenGApps corresponding version of Android and x86 architecture, then install it via Recovery mode or command line.
How to increase the size of a virtual disk?
The virtual disk can be expanded through the VirtualBox menu: File → Virtual Media Manager. Select your drive and change the size using the slider. After this, inside Android you will need to expand the partition through the terminal or partition management utility.
Can you play heavy 3D games?
Yes, but the performance will be lower than on a physical device with similar characteristics. Make sure that 3D acceleration is enabled in the VirtualBox settings and that the latest video card drivers are installed on the host machine.
How to take a screenshot in the emulator?
Use the keyboard shortcut Host Key + E (by default Right Ctrl + E) to take a screenshot of the virtual window cars. Or use the built-in Android function by holding down the power and volume down buttons (emulated through the virtual machine menu).