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 Eclipse
- or navigate to your SDK's {@code tools/} directory and execute
- android avd. You will see the AVD Manager as shown in
- figure 1.
-
- Figure 1. Screenshot of the AVD Manager.
- -From the main screen, you can create, delete, repair and start AVDs as well as see the details - of each AVD.
+ 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.
+
+ 
+ Figure 1. AVD Manager.
-Note: The emulator system images include experimental -64-bit system images along with standard 32-bit system images. The 64-bit system images -require the Intel x86 Emulator Accelerator (HAXM) Rev.5 which can be downloaded from the -SDK Manager Extras folder. -
-You can create as many AVDs as you would like to test on. It is recommended that you test your @@ -49,38 +40,68 @@ require the Intel x86 Emulator Accelerator (HAXM) Rev.5 which can be downloaded
in the Android Studio toolbar.tools/ directory and execute the
android tool with no arguments.In the Virtual Devices panel, you'll see a list of existing AVDs. Click - New to create a new AVD. The Create New AVD dialog appears.
- -
- Figure 2. Screenshot of the Create AVD window
+Click Create Virtual Device to create an AVD. The + Select Hardware dialog appears.
+ +
+ Figure 2. Select Hardware window.
+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.
+ +
+ Figure 3. Configure Hardware window.
+Give it a name, a platform target, an SD card size, and a skin (HVGA is default). You can - also add specific hardware features of the emulated device by clicking the - New... button and selecting the feature. 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. +
-Note: Be sure to define a target for your AVD that satisfies +
Tip:Store custom skins in an easily accessible directory, + such as ~/skins. From information about custom skins, see + Skins.
+ +
+ Figure 4. Configure AVD window.
+ +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 - launch an emulator with the AVD by selecting a device and clicking Start.
+ 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 @@ -242,3 +263,68 @@ to emulate:
+ +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.
+