Relationship between Android screen Density (Density) and resolution

Android has the following screens:

QVGA and WQVGA screens density = 120;

HVGA screen density = 160;

WVGA screen density = 240;

The following uses 240 dip * 800dip WVGA (density =) as an example to list the screen resolution information of different density:

When density = 120, the actual screen resolution is 240px * 400px (two points correspond to one resolution)

The height of the status bar is 19px or 25dip.

The screen width is 400px or 800dip, and the working area height is 211px or 480dip.

Screen width: Px or dip, working area Height: 381px or 775dip

When density = 160, the actual screen resolution is 320px * 533px (three points correspond to two resolutions)

The height of the status bar is 25px or 25dip.

The screen width is 533px or 800dip, and the working area height is 295px or 480dip.

Screen width: 320px or 480dip, working area Height: 508px or 775dip

When density = 240, the actual screen resolution is 480px * 800px (one point for one resolution)

The height of the status bar and title bar is 38px or 25dip.

The screen width is PX or dip, and the working area height is PX or dip.

Screen width 480px or 480dip, working area height 762px or 775dip

In the apk resource package, when the screen density is 240, the resources using the hdpi label

Resources that use the mdpi label when the screen density is 160

Ldpi tag resources are used when the screen density is 120.

Resources without any tags are shared in various resolutions.

Suggestion: Use the unit dip as much as possible during layout, and use less px.

Device independent pixels (device independent pixels). Different devices have different display effects. This is related to the hardware of the device. We recommend that you use this feature to support WVGA, HVGA, and QVGA, without relying on pixels.