page.title=Managing AVDs with AVD Manager parent.title=Managing Virtual Devices parent.link=index.html @jd:body
The AVD Manager is an easy to use user interface to manage your AVD (Android Virtual Device)
configurations. An AVD is a device configuration for the Android emulator that allows you to
model different configurations of Android-powered devices. When you start the AVD Manager in Android
Studio or navigate to your SDK's {@code tools/} directory and execute
android avd
, you will see the AVD Manager main screen with your current virtual
devices. You can right-click an existing AVD to perform actions on the AVD, such as delete,
duplicate, wipe data, show on disk, and display details.
You can create as many AVDs as you would like to test on. It is recommended that you test your applications on all API levels higher than the target API level for your application.
To create an AVD:
tools/
directory and execute the
android
tool with no arguments.Click Create Virtual Device to create an AVD. The Select Hardware dialog appears.
Select the device category and form factor. Click Edit Device to modify an existing AVD, or click New Hardware Profile to create a new hardware profile. Click Next to continue.
The hardware profile includes settings for screen size, camera, memory options,input type, and sensors. For a list of hardware features, see Hardware options.
Give it a name, device type, platform target, image size, orientation, and emulator performance. Click Show Advanced Settings to assign a custom skin to the hardware profile and other advanced settings for the device type.
Tip:Store custom skins in an easily accessible directory, such as ~/skins. From information about custom skins, see Skins.
Tip: Be sure to define a target for your AVD that satisfies your application's Build Target (the AVD platform target must have an API Level equal to or greater than the API Level that your application compiles against).
Your AVD is now ready and you can either close the AVD Manager, create more AVDs, or manage an emulator with the AVD by clicking an icon in the Actions column:
If you are creating a new AVD, you can specify the following hardware options for the AVD to emulate:
Characteristic | Description | Property |
---|---|---|
Device ram size | The amount of physical RAM on the device, in megabytes. Default value is "96". | hw.ramSize |
Touch-screen support | Whether there is a touch screen or not on the device. Default value is "yes". | hw.touchScreen |
Trackball support | Whether there is a trackball on the device. Default value is "yes". | hw.trackBall |
Keyboard support | Whether the device has a QWERTY keyboard. Default value is "yes". | hw.keyboard |
DPad support | Whether the device has DPad keys. Default value is "yes". | hw.dPad |
GSM modem support | Whether there is a GSM modem in the device. Default value is "yes". | hw.gsmModem |
Camera support | Whether the device has a camera. Default value is "no". | hw.camera |
Maximum horizontal camera pixels | Default value is "640". | hw.camera.maxHorizontalPixels |
Maximum vertical camera pixels | Default value is "480". | hw.camera.maxVerticalPixels |
GPS support | Whether there is a GPS in the device. Default value is "yes". | hw.gps |
Battery support | Whether the device can run on a battery. Default value is "yes". | hw.battery |
Accelerometer | Whether there is an accelerometer in the device. Default value is "yes". | hw.accelerometer |
Audio recording support | Whether the device can record audio. Default value is "yes". | hw.audioInput |
Audio playback support | Whether the device can play audio. Default value is "yes". | hw.audioOutput |
SD Card support | Whether the device supports insertion/removal of virtual SD Cards. Default value is "yes". | hw.sdCard |
Cache partition support | Whether we use a /cache partition on the device. Default value is "yes". | disk.cachePartition |
Cache partition size | Default value is "66MB". | disk.cachePartition.size |
Abstracted LCD density | Sets the generalized density characteristic used by the AVD's screen. Default value is "160". | hw.lcd.density |
A custom Android emulator skin is a collection of files that enable you to customize the visual and control elements of an emulator display. Custom emulator skins enable you to define variations of emulation properties, such as the use of a trackball or touchscreen, to match your device customizations. Each custom emulator skin contains:
hardware.ini file
for initialization settingsTo create and use a custom skin:
layout
in the skin folder.
parts { device { display { width 1080 height 1920 x 0 y 0 } } portrait { background { image background_port.png } buttons { power { image button_vertical.png x 1229 y 616 } } } ... }
hardware.ini
file for the skin-specific properties that determine
emulator specifications and behavior. For a complete list of emulator properties, see
Managing AVDs from the Command
Line. For example:# skin-specific hardware values hw.lcd.density=213 vm.heapSize=48 hw.ramSize=1024 hw.keyboard.lid=no hw.mainKeys=no
You can now run the AVD with a custom skin for testing and viewing your app.