Technical Implementation and Configuration Methods for Custom Screen Resolution of Android-x86 in VirtualBox

Technical Background and Problem Analysis

Configuring screen resolution presents a common technical challenge when running Android-x86 in virtualized environments. Users often need to set specific resolutions (such as 320x480) for development testing or particular application scenarios. As a mainstream virtualization platform, VirtualBox has significantly different video mode configuration mechanisms compared to physical devices, requiring users to implement custom resolutions through multi-layer configuration adjustments.

Detailed Core Configuration Steps

Implementing custom screen resolution for Android-x86 requires following a systematic configuration workflow, primarily involving three key aspects: VirtualBox extra data settings, GRUB boot parameter modifications, and system file editing.

VirtualBox Custom Video Mode Configuration

First, custom video modes must be added to the virtual machine using the VBoxManage command-line tool. Configuration parameters vary depending on the Android version:

# For Android versions below 6.0
VBoxManage setextradata "VM_NAME_HERE" "CustomVideoMode1" "320x480x16"

# For Android 6.0 and above
VBoxManage setextradata "VM_NAME_HERE" "CustomVideoMode1" "320x480x32"

The numerical suffix (16 or 32) represents color depth, with this difference arising from graphical subsystem optimizations in different Android versions. After configuration, the virtual machine must be restarted for the settings to take effect.

VGA Mode Value Identification and Conversion

The next step involves determining the VGA mode value corresponding to the target resolution. After starting the virtual machine, in the GRUB boot menu:

1. Press the a key (for Android 6.0+, press e) to enter edit mode
2. Add the vga=ask parameter to the end of the kernel line
3. Press Enter to boot, after which the system will display available resolution options
4. Record the hexadecimal Mode value corresponding to the target resolution

For example, if the hexadecimal value for 320x480 resolution is 360, it must be converted to decimal: 0x360 = 864. This conversion is necessary because the GRUB configuration file requires the vga parameter in decimal format.

GRUB Configuration File Modification

Modifying the menu.lst file through debug mode is a critical step in the configuration process:

# Enter debug mode and mount the system partition
mount -o remount,rw /mnt
cd /mnt/grub
vi menu.lst

Locate the kernel boot line in the configuration file and add the necessary parameters. A complete configuration example is as follows:

kernel /android-2.3-RC1/kernel quiet root=/dev/ram0 androidboot_hardware=eeepc \
acpi_sleep=s3_bios,s3_mode DPI=160 UVESA_MODE=320x480 \
SRC=/android-2.3-RC1 SDCARD=/data/sdcard.img vga=864

Here, vga=864 corresponds to the previously converted decimal value, UVESA_MODE=320x480 specifies the userspace video mode, and DPI=160 controls display density. After saving changes, execute:

:wq
cd /
umount /mnt
reboot -f

Alternative Solutions and Technical Comparison

Simplified configuration approaches exist in the community, using only UVESA_MODE and DPI parameters while omitting the vga definition. An example of this method is:

UVESA_MODE=320x480 DPI=160

This approach directly sets resolution through userspace video drivers, avoiding the complex conversion of VGA mode values. However, this method may have compatibility issues with certain hardware combinations or Android versions. In contrast, the complete solution including the vga parameter provides lower-level display control, ensuring higher configuration success rates.

Technical Key Points Summary

Successful configuration of Android-x86 custom resolution requires attention to the following technical aspects:

1. Android version differences determine the choice of color depth parameters (16-bit or 32-bit)
2. Hexadecimal-to-decimal conversion of VGA mode values is a critical step in the configuration process
3. The UVESA_MODE and vga parameters can work together to provide multi-level display control
4. The DPI parameter affects the physical size of interface elements and should be adjusted according to actual requirements
5. When modifying system files through debug mode, proper mounting and unmounting operations must be ensured

These configuration methods are not limited to 320x480 resolution but can be extended to other custom resolution scenarios, providing a technical foundation for flexible deployment of Android-x86 in virtualized environments.