Android Create AVD various parameters detailed

One, eclipse in the graphics create AVD:

• Device:

The device, which is a specific mobile device model, can be defined in window->android Virtual device manager->device definitions. Some phone models are preset in the development environment, many of which are Google's Nexus series, as follows:

Nexus 7 (7.0 ", x 1280:tvdpi):
A 7-inch screen tablet device with a screen resolution of 800X1280,DIP (device independent pixels, devices independent pixels) is 600x960, and the corresponding Android screen density is tvdpi (tvdpi:mdpi=1.3;hdpi: mdpi=1.5). Because most Android apps now contain hdpi resource files (especially image files) to reduce developer adaptation tasks, in Nexus 7 it is generally not necessary to re-add new image files to the "drawable-tvdpi" directory, The system automatically shrinks the graphics files in the hdpi directory, and most of the system images and system-brought images in the Nexus 7 are used in this way, and the graphics effect looks just as good.

SW600DP The layout can be used to make full use of the Nexus 7 screen to display memory, whereas for subsequent 10-inch tablets You can use the SW720DP limiter.
minimum width SWDP, for example: SW320DP, SW600DP, SW720DP, etc.
the basic size of the screen refers to the shortest available screen area. That is, the minimum width of the device is the shortest possible width and height of the screen (that is, the minimum width of the screen). This allows you to use this qualifier to ensure that the application has at least DP widths available for the UI interface, regardless of the current orientation of the screen.
For example, if the layout requires at least 600DP minimum screen size, you can use this qualifier to create a layout resource in the res/layout-sw600dp/directory. These resources are only used when the size of the available screen is at least 600DP, regardless of whether the 600DP is a user-perceived height or width. The minimum width is the fixed screen size feature of the device, and the minimum width of the device does not change when the orientation of the screen changes. The minimum width of the device requires consideration of screen decorations and system UI occupancy. For example, if the device has some fixed UI elements that take up a certain amount of screen space along the minimum width of the axis, the minimum width of the system declaration is smaller than the actual screen size, because the portion of the pixel that is occupied by the system is not valid for the UI of the user application. Therefore, this value should be the minimum actual size required for the application layout (typically, this value is the minimum width supported by the layout, regardless of the current orientation of the screen).

on the hardware side, Nexus 7 and most of the Andorid handheld devices have a 2-point difference:
* * Cannot call
There is only one front camera, no rear camera (the program uses the "Android.hardware.camera" feature cannot be installed in the Nexus 7, if the camera function is not required in your app, you can declare it as optional:

uses-feature android: name=”android.hardware.camera” android:required=”false”

Nexus 5 (4.95 ", x 1920:xxhdpi):
4.95-inch mobile phone, 1920*1080 resolution screen, PPI up to 445.

Nexus 4 (4.7 ", 768 x 1280:xhdpi):
4.7-inch mobile phone, 1280x768 resolution IPS display, pixel density up to 320PPI.

Nexus Ten (10.055 ", 2560 x 1600:xhdpi):
10.055-inch screen tablet device, 2560 x 1600 resolution, 300PPI,PLS material.

Nexus 7 (7.02 ", x 1920:xhdpi):
The 7-inch screen tablet device, 1920x1200 Pixel resolution, has a 323ppi and a 30% increase in color performance on the screen.

Galaxy Nexus (4.65 ", 720 x 1280:xhdpi):
4.65-inch mobile phone with a resolution of 720 x 1280 with a screen pixel density of approximately 316dpi.

Nexus S (4.0 ", 480 x 800:hdpi):
4-inch mobile phone with a resolution of 800x480,233ppi.

Nexus One (3.7 ", 480 x 800:hdpi):
3.7-inch mobile phone with a resolution of 800x480,252ppi.

Android Wear Round (x 320:hdpi):
Round screen Google smart watch with a resolution of 320 x.

Android Wear Square (280 x 280:hdpi):
Google smart watch on a square screen with a resolution of 280 x 280.

Android TV (720p) (720:tvdpi x):
Google TV with a resolution of 720 x.

Android TV (1080p) (1920x1080 x 1080:xhdpi):
Google TV with a resolution of 1080 X.

10.1 "WXGA (Tablet) (800:mdpi x):
Samsung Galaxy Tab 10.1, screen for 10.1WXGA (1280x800), Tft,149ppi.

• Target:

Android 1.6–api Level 4
Android 2.1–api Level 7
Android 2.2–api Level 8
Android 2.3.3–api Level 10
Android 3.0–api Level 11
Android 3.1–api Level 12
Android 3.2–api Level 13
Android 4.0–api Level 14
Android 4.0.3–api Level 15
Android 4.1.2–api Level 16
Android 4.2.2–api Level 17
Android 4.3–api Level 18
Android 4.4.2–api Level 19
Google APIs (Google Inc) –api level 7
Google APIs (Google Inc) –api level 8

• Cpu/abi: CPU/Application Binary interface

Android Wear ARM (armeabi-v7a)
ARM (armeabi-v7a)
Intel Atom (x86)
armeabi-v7a: Hardware floating point arithmetic is supported for ARM v7 CPUs with floating-point arithmetic or advanced extension functions.
Armeabi: For normal or old arm V5 CPU, refers to the so library for ARM's general purpose CPU, the versatility is strong, but the speed is slow. In the Air pack apk debug mode Adobe chooses a versatile Armeabi mode.

armeabi/armeabi-v7a/x86 When compiling the NDK library, there are three supported application binary interfaces (ABI):
Armeabi: Default option to create a library that targets ARM v5te devices. Floating-point operations with this goal use software floating-point arithmetic. Binary code created with this ABI will be available to run on all arm devices.
armeabi-v7a: Create a library that supports ARM V7 devices and use the hardware FPU instructions (float Point Unit, float unit).
x86: Generates binary code to support IA-32 instruction sets that contain hardware-based floating-point operations.

• Skin: Recommended Choice WVGA800

Skin with dynamic hardware controls:
Depending on the hardware, the skin is dynamically set.

No Skin:
No skin.

HVGA:
Half of the Half-size VGA:VGA (640*480), with a resolution of (480*320), (3:2 aspect ratio).

QVGA:
QUARTERVGA:VGA One-fourth, that is, the output resolution on the LCD is 240x320 pixels.

wqvga400/wqvga432
Wide Quarter Video Graphics Array: A screen resolution of a digital product that represents a screen resolution of 480x272 (aspect ratio 16:9) or 400x240 (aspect ratio 5:3), rather than the nominal 480x240 of a domestic manufacturer, than QVGA ( High resolution, lower than VGA (640x480) resolution.
WQVGA400 (240x400); WQVGA432 (240x320).

WSVGA
WSVGA (1024x600) is a eclectic wide screen between WVGA (800x480) and WXGA (1280x800 or 1280x768), and the range of applications is not very wide, Only Sony's Umpcvgn-ux series and some tablet computers, as well as popular netbook, have been used.

wvga800/wvga854
WIDEVGA: Resolution of 800x480 pixels, enlarged VGA (640x480). Used in PDA and mobile phone, because a lot of Web page width is 800, so WVGA screen will be more suitable for browsing the web, can be said to be the future of handheld device resolution trend.
WVGA800 (480x800); WVGA854 (480X854).

wxga720/wxga800/wxga800-7in
Wide Extended Graphics Array, the 16:10 scale widened the notebook screen, suitable for the aspect ratio of DVD film, so there is no image distortion or two sides of the image on the DVD display problem, this screen supports 1280x800 and 1680x The 10,502-pixel 15.4-inch screen is now used by most wide-screen notebooks.
WXGA720 (1280x720); WXGA800 (1280x800).

• Front Camera:none/emulated/webcam0

Front-facing camera: Choose "None", the analog camera will choose "emulated", using the PC's camera to select "WebCam0".

• Back Camera:none/emulated/webcam0

Rear camera: Use NOT to choose "None", Analog camera to choose "emulated", use PC's camera to choose "WebCam0".

Second, cmd create AVD:
Device hardware option is the default

• Snapshot:
  The snapshot, which holds the state at the time the AVD is closed, shows the last shutdown state at the next boot, similar to the caching mechanism. Generally cancel enable.

• bulit-in:
  The pixel that defines the screen size.

• Resolution:
  Custom resolutions are not recommended unless there is a special need to customize them. Because the custom size does not correspond to the right interface, of course, the corresponding skin can be self-made.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Android Create AVD various parameters detailed