All snapshots made during execution will be saved to this file. Snapshot storage path – Path to the snapshot storage file where all snapshots are stored. If this option is not specified, the default is ramdisk.img in the emulator system directory. The ramdisk image typically contains boot-time binaries and initialization scripts. The ramdisk image is a subset of the system image that is loaded by the kernel before the system image is mounted. Ramdisk path – Path to the boot partition (ramdisk) image. The minimum size is 9M and the maximum size is 1023G. You can also specify the size in kilobytes, megabytes, and gigabytes by appending K, M, or G to the value. If this value is an integer, it specifies the size in bytes. Note that this option cannot be left blank.ĭata partition size – Specifies the size of the user data partition in bytes. If is set, its content will be copied to the file at boot-time. The special value causes the emulator to create and use a temporary file. If you don't specify a path, the default file is named userdata-qemu.img. If the file doesn't exist, the emulator creates an image from the default file userdata.img, stores it in the filename specified by, and persists user data to it when the emulator shuts down. To configure a persistent user data file, enter a filename and a path on your development computer.
Path to the data partition – Specifies the user data partition file. After wiping user data, the emulator copies the contents of the specified file to user data (by default, userdata-qemu.img) instead of using userdata.img as the initial version. Initial path to the data partition – Specifies the initial contents of the data partition. This option is ignored if disk.cachePartition is set to no. Normally you do not need to set this option unless the app will be downloading very large files that are larger than the default cache size of 66 megabytes. This option is ignored if disk.cachePartition is set to no.Ĭache partition size – The size of the cache partition file (in bytes). If the file does not exist, it is created as an empty file.
If not set, the emulator creates an empty temporary file called cache.img on your development computer. Enter an absolute path or a path relative to the emulator's data directory. The emulator will use this file for the /cache partition. If set to no, the emulator will not use a /cache partition and the other disk.cache settings will be ignored.Ĭache partition path – Specifies a cache partition image file on your development computer.
The /cache partition (which is initially empty) is the location where Android stores frequently accessed data and app components. The arm64-v8a option is for the ARM instruction set that supports AArch64.Ĭache partition – Determines whether the emulated device will use a /cache partition on the device. The armeabi-v7a option is for the ARM instruction set with v7-a ARM extensions. The x86 option is for the instruction set commonly referred to as "x86" or "IA-32." The x86_64 option is for the 64-bit x86 instruction set. Listed in the New Device and Device Editor screens: PropertyĪBI type – Specifies the ABI (application binary interface) type of the emulated device. The following table provides a detailed explanation of the properties To the right of the property and choose a new value. To change an enum (enumerated) property, click the pull-down menu
String or integer setting in the value column and enter a new value. To change a string or integer property, double-click the current The right of the property and choose a new value. To change an enum (enumerated) property, click the down-arrow to To change a boolean property, click the check mark to the right of You can change properties by using the following guidelines: For example,ĪVD properties can be configured to specify how the AVD uses yourĭevelopment computer's graphics card for rendering. Properties specify the operation of the AVD when it runs. Of available RAM, whether or not an accelerometer is present. These characteristics include screen size, the amount Hardware profile properties (such as hw.ramSizeĪnd hw.accelerometer) describe the physical characteristics of theĮmulated device. You can modify hardware profile propertiesĪnd AVD properties. When you select a property, a detailed description of that property isĭisplayed on the right. The first column, with the corresponding values of each property in the The New Device andĭevice Edit screens list the properties of the virtual device in The Android Device Manager supports the editing of individualĪndroid virtual device profile properties.