Detailed description of AVD parameters created for Android,

Detailed description of AVD parameters created for Android,

I. Create AVD for images in Eclipse:

• Device:

That is, the Device refers to the specific mobile phone Device model, which can be defined in window> Android Virtual Device Manager> Device Definitions. Some mobile phone models are preset in the development environment, many of which are google's Nexus series, as shown below:

Nexus 7 (7.0 ", 800x1280: tvdpi ):
For a 7-inch flat screen device, the screen resolution is 800x1280, the DIP (device independent pixels, device independent pixels) is 600x960, and the corresponding Android screen density is tvdpi (tvdpi: mdpi = 1.3; hdpi: mdpi = 1.5 ). Because most Android apps currently contain hdpi resource files (especially image files), fixed to reduce developer adaptation tasks, in Nexus 7, you do not need to add new image files to the "drawable-tvdpi" directory. The system will automatically scale down the image files in the hdpi directory, most of the images in the Nexus 7 system and those in the App that comes with the system are used in this way, and the graphic effect looks the same.

Sw600dp limiters are designed to make full use of the Nexus 7 screen to Display memory, while sw720dp limiters can be used for a 10-inch tablet in the future.
The minimum width is swdp, such as sw320dp, sw600dp, and sw720dp.
The basic screen size refers to the shortest available area. That is, the minimum width of the device is the shortest width and height of the screen (that is, the minimum possible width of the screen ). In this way, you can use this qualifier to ensure that the application has at least the dp width available for the UI interface, regardless of the current direction of the screen.
For example, if you need at least 600dp minimum screen size during layout, you can use this qualifier to create layout Resources in the res/layout-sw600dp/directory. The system uses these resources only when the available screen size is at least 600dp, regardless of whether the 600dp is the height or width recognized by the user. The minimum width is the fixed screen size feature of the device. When the screen direction changes, the minimum width of the device does not change. The minimum width of the device must consider the screen decoration and the occupation of the system UI. For example, if a device has some Fixed UI elements going along the axis of the smallest width and occupying a certain amount of screen space, the minimum width declared by the system is smaller than the actual screen size, because the pixels occupied by the system are invalid for the UI of the user application. Therefore, this value should be the minimum actual size required for the application layout (normally, this value is the minimum width supported by the layout regardless of the current direction of the screen ).

In terms of hardware, there are two main differences between Nexus 7 and most Andorid handheld devices:
** You cannot call
There is only one front camera and no rear camera (the program uses "android. hardware. the camera feature cannot be installed and run in 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 ", 1080x1920: xxhdpi ):
4.95 inch mobile phone, 1920*1080 resolution screen, PPI up to 445.

Nexus 4 (4.7 ", 768x1280: xhdpi ):
4.7 inch mobile phone, X resolution IPS display, pixel density reached 320PPI.

Nexus 10 (10.055 '', 2560x1600: xhdpi ):
10.055 inch flat screen device, 2560x1600 resolution, PPI, PLS material.

Nexus 7 (7.02 ", 1200x1920: xhdpi ):
A 7 inch-inch flat screen device with a resolution of 1920x1200 pixels and a 323ppi device, improves the screen color performance by 30%.

Galaxy Nexus (4.65 ", 720x1280: xhdpi ):
The resolution is 4.65 inch x 720, And the pixel density of the screen is about 1280 dpi.

Nexus S (4.0 ", 480x800: hdpi ):
4 inch mobile phone, resolution 800x480,233 ppi.

Nexus One (3.7 ", 480x800: hdpi ):
3.7 inch mobile phone, resolution 800x480,252 ppi.

Android Wear Round (320x320: hdpi ):
A round-screen Google smart watch with a resolution of 320x320.

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

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

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

10.1 "WXGA (Tablet) (1280x800: mdpi ):
Samsung galaxy tab 10.1, screen 10.1 WXGA (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: central processor/Application binary Interface

Android Wear ARM (armeabi-v7a)
ARM armeabi-v7a)
Intel Atom (x86)
Armeabi-v7a: For arm v7 CPUs with floating point operations or advanced extensions, hardware floating point operations are supported.
Armeabi: for common or old arm v5 CPUs, this so library is used for general cpu of ARM. It is versatile but slow. In the AIR packaging APK debugging mode, adobe selects the armeabi mode with strong versatility.

When armeabi/armeabi-v7a/x86 is compiling the NDK library, three supported application binary interfaces (ABI) can be used ):
Armeabi: the default option to create a library based on the ARM v5TE device. Floating-point operations with such goals use software floating-point operations. The binary code created using this ABI can run on all ARM devices.
Armeabi-v7a: Creates libraries that support ARM v7 devices and uses hardware FPU commands (Float Point Unit, floating Point Unit ).
X86: Generate binary code that supports IA-32 instruction sets that contain hardware-based floating point operations.

• Skin: We recommend that you select WVGA800.

Skin with dynamic hardware controls:
Dynamically set skin based on hardware.

No skin:
No skin.

HVGA:
Half-size VGA: Half of VGA (640*480), resolution (480*320), (Aspect Ratio ).

QVGA:
QuarterVGA: 1/4 of VGA, that is, the output resolution on the LCD is 240x320 pixels.

WQVGA400/WQVGA432
Wide Quarter Video Graphics Array: A screen resolution for digital products, representing a screen resolution of 480X272 (Aspect Ratio:) or 400X240 (Aspect Ratio, the resolution is higher than that of QVGA (480X240) and lower than that of VGA (320X240.
WQVGA400 (240x400); WQVGA432 (240x320 ).

WSVGA
WSVGA (1024x600) is a medium-width screen that is between WVGA (800x480) and WXGA (1280x800 or 1280x768, the range of applications is not very wide, only the Sony UMPCVGN-UX series and some tablet computers as well as popular Netbook applications.

WVGA800/WVGA854
WideVGA: resolution is 800x480 pixels, expanding the VGA (640x480) Resolution. It is used in PDAs and mobile phones. Because many web pages are 800 in width, the WVGA screen is more suitable for browsing web pages. It can be said that it is the general trend of the Resolution of handheld devices in the future.
WVGA800 (480x800); WVGA854 (480X854 ).

WXGA720/WXGA800/WXGA800-7in
Wide Extended Graphics Array, which is used to increase the aspect ratio of the notebook screen at. It is applicable to the aspect ratio of the DVD film. Therefore, no image deformation or no display of the images on both sides will occur when watching the DVD, this screen supports 1280x800 and 1680x1050 two pixel 15.4 inch screens, which are currently used in most wide screen laptops.
WXGA720 (1280x720); WXGA800 (1280x800 ).

• Front Camera: None/Emulated/Webcam0

Front camera: Select "None" if it is not used, select "Emulated" for the simulated camera, and select "WebCam0" for the PC camera ".

• Back Camera: None/Emulated/Webcam0

Rear camera: Select "None" if it is not used, select "Emulated" for the simulated camera, and select "WebCam0" for the PC camera ".

Ii. Create AVD in CMD:
The hardware option of the device is default.

• Snapshot:
  This is a snapshot that saves the status when AVD is disabled. The last status is displayed at the next startup, similar to the cache mechanism. Generally, enable can be canceled.

• Bucket-in:
  Defines the pixels of the screen size.

• Resolution:
  Custom resolution is not recommended unless you have special requirements. Because the Custom size does not correspond to the right interface, you can also customize the corresponding skin.

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.