Configuration | Qualifier Values | Description |
---|---|---|
MCC and MNC | Examples:mcc310
mcc310-mnc004
mcc208-mnc00 etc. | The mobile country code (MCC), optionally followed by mobile network code (MNC) from the SIM card in the device. For example, If the device uses a radio connection (GSM phone), the MCC and MNC values come from the SIM card. You can also use the MCC alone (for example, to include country-specific legalresources in your application). If you need to specify based on the language only, then use thelanguage and region qualifier instead (discussed next). If you decide to use the MCC andMNC qualifier, you should do so with care and test that it works as expected. Also see the configuration fields |
Language and region | Examples:en fr en-rUS fr-rFR fr-rCA etc. | The language is defined by a two-letter ISO 639-1 language code, optionally followed by a two letter ISO 3166-1-alpha-2 region code (preceded by lowercase " The codes are not case-sensitive; the This can change during the lifeof your application if the user changes his or her language in the system settings. SeeHandling Runtime Changes for information abouthow this can affect your application during runtime. See Localization for a complete guide to localizingyour application for other languages. Also see the |
smallestWidth | sw<N>dp Examples: sw320dp sw600dp sw720dp etc. | The fundamental size of a screen, as indicated by the shortest dimension of the availablescreen area. Specifically, the device's smallestWidth is the shortest of the screen's availableheight and width (you may also think of it as the "smallest possible width" for the screen). You canuse this qualifier to ensure that, regardless of the screen's current orientation, yourapplication's has at least For example, if your layout requires that its smallest dimension of screen area be atleast 600 dp at all times, then you can use this qualifer to create the layout resources, The smallestWidth of a device takes into account screen decorations and system UI. Forexample, if the device has some persistent UI elements on the screen that account for space alongthe axis of the smallestWidth, the system declares the smallestWidth to be smaller than the actualscreen size, because those are screen pixels not available for your UI. Thus, the value you useshould be the actual smallest dimensionrequired by your layout (usually, this value is the"smallest width" that your layout supports, regardless of the screen's current orientation). Some values you might use here for common screen sizes:
When your application provides multiple resource directories with different values for the smallestWidth qualifier, the system uses the one closest to (without exceeding) thedevice's smallestWidth. Added in API level 13. Also see the For more information about designing for different screens and using thisqualifier, see theSupportingMultiple Screens developer guide. |
Available width | w<N>dp Examples: w720dp w1024dp etc. | Specifies a minimum available screen width, in When your application provides multiple resource directories with different values for this configuration, the system uses the one closest to (without exceeding) the device's current screen width. The value here takes into account screen decorations, so if the device has some persistent UI elements on the left or right edge of the display, it uses a value for the width that is smaller than the real screen size, accounting for these UI elements and reducing the application's available space. Added in API level 13. Also see the For more information about designing for different screens and using thisqualifier, see theSupportingMultiple Screens developer guide. |
Available height | h<N>dp Examples: h720dp h1024dp etc. | Specifies a minimum available screen height, in "dp" units at which the resource should be used—defined by the When your application provides multiple resource directories with different values for this configuration, the system uses the one closest to (without exceeding) the device's current screen height. The value here takes into account screen decorations, so if the device has some persistent UI elements on the top or bottom edge of the display, it uses a value for the height that is smaller than the real screen size, accounting for these UI elements and reducing the application's available space. Screen decorations that are not fixed (such as a phone status bar that can be hidden when full screen) arenot accounted for here, nor are window decorations like the title bar or action bar, so applications must be prepared to deal with a somewhat smaller space than they specify. Added in API level 13. Also see the For more information about designing for different screens and using thisqualifier, see theSupportingMultiple Screens developer guide. |
Screen size | small normal large xlarge |
Note: Using a size qualifier does not imply that theresources areonly for screens of that size. If you do not provide alternativeresources with qualifiers that better match the current device configuration, the system may usewhichever resources are thebest match. Caution: If all your resources use a size qualifier thatislarger than the current screen, the system will not use them and yourapplication will crash at runtime (for example, if all layout resources are tagged with the Added in API level 4. See Supporting MultipleScreens for more information. Also see the |
Screen aspect | long notlong |
Added in API level 4. This is based purely on the aspect ratio of the screen (a "long" screen is wider). Thisis not related to the screen orientation. Also see the |
Screen orientation | port land |
This can change during the life of your application if the user rotates thescreen. SeeHandling Runtime Changes for information abouthow this affects your application during runtime. Also see the |
UI mode | car desk television |
Added in API level 8, television added in API 13. This can change during the life of your application if the user places the device in adock. You can enable or disable some of these modes using |
Night mode | night notnight |
Added in API level 8. This can change during the life of your application if night mode is left inauto mode (default), in which case the mode changes based on the time of day. You can enableor disable this mode using |
Screen pixel density (dpi) | ldpi mdpi hdpi xhdpi nodpi tvdpi |
There is a 3:4:6:8 scaling ratio between the four primary densities (ignoring thetvdpi density). So, a 9x9 bitmap in ldpi is 12x12 in mdpi, 18x18 in hdpi and 24x24 in xhdpi. If you decide that your image resources don't look good enough on a television orother certain devices and want to try tvdpi resources, the scaling factor is 1.33*mdpi. Forexample, a 100px x 100px image for mdpi screens should be 133px x 133px for tvdpi. Note: Using a density qualifier does not imply that theresources areonly for screens of that density. If you do not provide alternativeresources with qualifiers that better match the current device configuration, the system may usewhichever resources are thebest match. See Supporting MultipleScreens for more information about how to handle different screen densities and how Androidmight scale your bitmaps to fit the current density. |
Touchscreen type | notouch finger |
Also see the |
Keyboard availability | keysexposed keyshidden keyssoft |
If you provide This can change during the life of your application if the user opens a hardwarekeyboard. SeeHandling Runtime Changes for information about howthis affects your application during runtime. Also see the configuration fields |
Primary text input method | nokeys qwerty 12key |
Also see the |
Navigation key availability | navexposed navhidden |
This can change during the life of your application if the user reveals the navigationkeys. SeeHandling Runtime Changes forinformation about how this affects your application during runtime. Also see the |
Primary non-touch navigation method | nonav dpad trackball wheel |
Also see the |
Platform Version (API level) | Examples:v3 v4 v7 etc. | The API level supported by the device. For example, Caution: Android 1.5 and 1.6 only match resourceswith this qualifier when it exactly matches the platform version. See the section below aboutKnown Issues for more information. |
Note: Some configuration qualifiers have been added since Android1.0, so not all versions of Android support all the qualifiers. Using a new qualifier implicitlyadds the platform version qualifier so that older devices are sure to ignore it. For example, usinga w600dp
qualifier will automatically include thev13
qualifier, becausethe available-width qualifier was new in API level 13. To avoid any issues, always include a set ofdefault resources (a set of resources withno qualifiers). For more information, see thesection about Providing the Best Device Compatibility withResources.
当有一个包有多个匹配项的时候,数目多的优先匹配。同等数目下,根据该规则匹配
http://developer.android.com/guide/topics/resources/providing-resources.html#table2
http://developer.android.com/guide/topics/resources/providing-resources.html#BestMatch