providing-resources.jd revision be0cf70dc3ff77661dbdf416d415757f2500e889
1page.title=Providing Resources 2parent.title=Application Resources 3parent.link=index.html 4@jd:body 5 6<div id="qv-wrapper"> 7<div id="qv"> 8 <h2>Quickview</h2> 9 <ul> 10 <li>Different types of resources belong in different subdirectories of {@code res/}</li> 11 <li>Alternative resources provide configuration-specific resource files</li> 12 <li>Always include default resources so your app does not depend on specific 13device configurations</li> 14 </ul> 15 <h2>In this document</h2> 16 <ol> 17 <li><a href="#ResourceTypes">Grouping Resource Types</a></li> 18 <li><a href="#AlternativeResources">Providing Alternative Resources</a> 19 <ol> 20 <li><a href="#QualifierRules">Qualifier name rules</a></li> 21 <li><a href="#AliasResources">Creating alias resources</a></li> 22 </ol> 23 </li> 24 <li><a href="#Compatibility">Providing the Best Device Compatibility with Resources</a> 25 <ol> 26 <li><a href="#ScreenCompatibility">Providing screen resource compatibility for Android 271.5</a></li> 28 </ol> 29 </li> 30 <li><a href="#BestMatch">How Android Finds the Best-matching Resource</a></li> 31 <li><a href="#KnownIssues">Known Issues</a></li> 32 </ol> 33 34 <h2>See also</h2> 35 <ol> 36 <li><a href="accessing-resources.html">Accessing Resources</a></li> 37 <li><a href="available-resources.html">Resource Types</a></li> 38 <li><a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple 39Screens</a></li> 40 </ol> 41</div> 42</div> 43 44<p>You should always externalize application resources such as images and strings from your 45code, so that you can maintain them independently. You should also provide alternative resources for 46specific device configurations, by grouping them in specially-named resource directories. At 47runtime, Android uses uses the appropriate resource based on the current configuration. For 48example, you might want to provide a different UI layout depending on the screen size or different 49strings depending on the language setting.</p> 50 51<p>Once you externalize your application resources, you can access them 52using resource IDs that are generated in your project's {@code R} class. How to use 53resources in your application is discussed in <a href="accessing-resources.html">Accessing 54Resources</a>. This document shows you how to group your resources in your Android project and 55provide alternative resources for specific device configurations.</p> 56 57 58<h2 id="ResourceTypes">Grouping Resource Types</h2> 59 60<p>You should place each type of resource in a specific subdirectory of your project's 61{@code res/} directory. For example, here's the file hierarchy for a simple project:</p> 62 63<pre class="classic no-pretty-print"> 64MyProject/ 65 src/ <span style="color:black"> 66 MyActivity.java </span> 67 res/ 68 drawable/ <span style="color:black"> 69 icon.png </span> 70 layout/ <span style="color:black"> 71 main.xml 72 info.xml</span> 73 values/ <span style="color:black"> 74 strings.xml </span> 75</pre> 76 77<p>As you can see in this example, the {@code res/} directory contains all the resources (in 78subdirectories): an image resource, two layout resources, and a string resource file. The resource 79directory names are important and are described in table 1.</p> 80 81<p class="table-caption" id="table1"><strong>Table 1.</strong> Resource directories 82supported inside project {@code res/} directory.</p> 83 84<table> 85 <tr> 86 <th scope="col">Directory</th> 87 <th scope="col">Resource Type</th> 88 </tr> 89 90 <tr> 91 <td><code>animator/</code></td> 92 <td>XML files that define <a href="{@docRoot}guide/topics/graphics/animation.html">property 93animations</a>.</td> 94 </tr> 95 96 <tr> 97 <td><code>anim/</code></td> 98 <td>XML files that define <a 99href="{@docRoot}guide/topics/graphics/view-animation.html#tween-animation">tween 100animations</a>. (Property animations can also be saved in this directory, but 101the {@code animator/} directory is preferred for property animations to distinguish between the two 102types.)</td> 103 </tr> 104 105 <tr> 106 <td><code>color/</code></td> 107 <td>XML files that define a state list of colors. See <a href="color-list-resource.html">Color 108State List Resource</a></td> 109 </tr> 110 111 <tr> 112 <td><code>drawable/</code></td> 113 <td><p>Bitmap files ({@code .png}, {@code .9.png}, {@code .jpg}, {@code .gif}) or XML files that 114are compiled into the following drawable resource subtypes:</p> 115 <ul> 116 <li>Bitmap files</li> 117 <li>Nine-Patches (re-sizable bitmaps)</li> 118 <li>State lists</li> 119 <li>Shapes</li> 120 <li>Animation drawables</li> 121 <li>Other drawables</li> 122 </ul> 123 <p>See <a href="drawable-resource.html">Drawable Resources</a>.</p> 124 </td> 125 </tr> 126 127 <tr> 128 <td><code>layout/</code></td> 129 <td>XML files that define a user interface layout. 130 See <a href="layout-resource.html">Layout Resource</a>.</td> 131 </tr> 132 133 <tr> 134 <td><code>menu/</code></td> 135 <td>XML files that define application menus, such as an Options Menu, Context Menu, or Sub 136Menu. See <a href="menu-resource.html">Menu Resource</a>.</td> 137 </tr> 138 139 <tr> 140 <td><code>raw/</code></td> 141 <td><p>Arbitrary files to save in their raw form. To open these resources with a raw 142{@link java.io.InputStream}, call {@link android.content.res.Resources#openRawResource(int) 143Resources.openRawResource()} with the resource ID, which is {@code R.raw.<em>filename</em>}.</p> 144 <p>However, if you need access to original file names and file hierarchy, you might consider 145saving some resources in the {@code 146assets/} directory (instead of {@code res/raw/}). Files in {@code assets/} are not given a 147resource ID, so you can read them only using {@link android.content.res.AssetManager}.</p></td> 148 </tr> 149 150 <tr> 151 <td><code>values/</code></td> 152 <td><p>XML files that contain simple values, such as strings, integers, and colors.</p> 153 <p>Whereas XML resource files in other {@code res/} subdirectories define a single resource 154based on the XML filename, files in the {@code values/} directory describe multiple resources. 155For a file in this directory, each child of the {@code <resources>} element defines a single 156resource. For example, a {@code <string>} element creates an 157{@code R.string} resource and a {@code <color>} element creates an {@code R.color} 158resource.</p> 159 <p>Because each resource is defined with its own XML element, you can name the file 160whatever you want and place different resource types in one file. However, for clarity, you might 161want to place unique resource types in different files. For example, here are some filename 162conventions for resources you can create in this directory:</p> 163 <ul> 164 <li>arrays.xml for resource arrays (<a 165href="more-resources.html#TypedArray">typed arrays</a>).</li> 166 <li>colors.xml for <a 167href="more-resources.html#Color">color values</a></li> 168 <li>dimens.xml for <a 169href="more-resources.html#Dimension">dimension values</a>.</li> 170 <li>strings.xml for <a href="string-resource.html">string 171values</a>.</li> 172 <li>styles.xml for <a href="style-resource.html">styles</a>.</li> 173 </ul> 174 <p>See <a href="string-resource.html">String Resources</a>, 175 <a href="style-resource.html">Style Resource</a>, and 176 <a href="more-resources.html">More Resource Types</a>.</p> 177 </td> 178 </tr> 179 180 <tr> 181 <td><code>xml/</code></td> 182 <td>Arbitrary XML files that can be read at runtime by calling {@link 183android.content.res.Resources#getXml(int) Resources.getXML()}. Various XML configuration files 184must be saved here, such as a <a 185href="{@docRoot}guide/topics/search/searchable-config.html">searchable configuration</a>. 186<!-- or preferences configuration. --></td> 187 </tr> 188</table> 189 190<p class="caution"><strong>Caution:</strong> Never save resource files directly inside the 191{@code res/} directory—it will cause a compiler error.</p> 192 193<p>For more information about certain types of resources, see the <a 194href="available-resources.html">Resource Types</a> documentation.</p> 195 196<p>The resources that you save in the subdirectories defined in table 1 are your "default" 197resources. That is, these resources define the default design and content for your application. 198However, different types of Android-powered devices might call for different types of resources. 199For example, if a device has a larger than normal screen, then you should provide 200different layout resources that take advantage of the extra screen space. Or, if a device has a 201different language setting, then you should provide different string resources that translate the 202text in your user interface. To provide these different resources for different device 203configurations, you need to provide alternative resources, in addition to your default 204resources.</p> 205 206 207<h2 id="AlternativeResources">Providing Alternative Resources</h2> 208 209 210<div class="figure" style="width:429px"> 211<img src="{@docRoot}images/resources/resource_devices_diagram2.png" height="167" alt="" /> 212<p class="img-caption"> 213<strong>Figure 1.</strong> Two different devices, each using different layout resources.</p> 214</div> 215 216<p>Almost every application should provide alternative resources to support specific device 217configurations. For instance, you should include alternative drawable resources for different 218screen densities and alternative string resources for different languages. At runtime, Android 219detects the current device configuration and loads the appropriate 220resources for your application.</p> 221 222<p>To specify configuration-specific alternatives for a set of resources:</p> 223<ol> 224 <li>Create a new directory in {@code res/} named in the form {@code 225<em><resources_name></em>-<em><config_qualifier></em>}. 226 <ul> 227 <li><em>{@code <resources_name>}</em> is the directory name of the corresponding default 228resources (defined in table 1).</li> 229 <li><em>{@code <qualifier>}</em> is a name that specifies an individual configuration 230for which these resources are to be used (defined in table 2).</li> 231 </ul> 232 <p>You can append more than one <em>{@code <qualifier>}</em>. Separate each 233one with a dash.</p> 234 <p class="caution"><strong>Caution:</strong> When appending multiple qualifiers, you must 235place them in the same order in which they are listed in table 2. If the qualifiers are ordered 236wrong, the resources are ignored.</p> 237 </li> 238 <li>Save the respective alternative resources in this new directory. The resource files must be 239named exactly the same as the default resource files.</li> 240</ol> 241 242<p>For example, here are some default and alternative resources:</p> 243 244<pre class="classic no-pretty-print"> 245res/ 246 drawable/ <span style="color:black"> 247 icon.png 248 background.png </span> 249 drawable-hdpi/ <span style="color:black"> 250 icon.png 251 background.png </span> 252</pre> 253 254<p>The {@code hdpi} qualifier indicates that the resources in that directory are for devices with a 255high-density screen. The images in each of these drawable directories are sized for a specific 256screen density, but the filenames are exactly 257the same. This way, the resource ID that you use to reference the {@code icon.png} or {@code 258background.png} image is always the same, but Android selects the 259version of each resource that best matches the current device, by comparing the device 260configuration information with the qualifiers in the resource directory name.</p> 261 262<p>Android supports several configuration qualifiers and you can 263add multiple qualifiers to one directory name, by separating each qualifier with a dash. Table 2 264lists the valid configuration qualifiers, in order of precedence—if you use multiple 265qualifiers for a resource directory, you must add them to the directory name in the order they 266are listed in the table.</p> 267 268 269<p class="table-caption" id="table2"><strong>Table 2.</strong> Configuration qualifier 270names.</p> 271<table> 272 <tr> 273 <th>Configuration</th> 274 <th>Qualifier Values</th> 275 <th>Description</th> 276 </tr> 277 <tr id="MccQualifier"> 278 <td>MCC and MNC</td> 279 <td>Examples:<br/> 280 <code>mcc310</code><br/> 281 <code><nobr>mcc310-mnc004</nobr></code><br/> 282 <code>mcc208-mnc00</code><br/> 283 etc. 284 </td> 285 <td> 286 <p>The mobile country code (MCC), optionally followed by mobile network code (MNC) 287 from the SIM card in the device. For example, <code>mcc310</code> is U.S. on any carrier, 288 <code>mcc310-mnc004</code> is U.S. on Verizon, and <code>mcc208-mnc00</code> is France on 289 Orange.</p> 290 <p>If the device uses a radio connection (GSM phone), the MCC comes 291 from the SIM, and the MNC comes from the network to which the 292 device is connected.</p> 293 <p>You can also use the MCC alone (for example, to include country-specific legal 294resources in your application). If you need to specify based on the language only, then use the 295<em>language and region</em> qualifier instead (discussed next). If you decide to use the MCC and 296MNC qualifier, you should do so with care and test that it works as expected.</p> 297 <p>Also see the configuration fields {@link 298android.content.res.Configuration#mcc}, and {@link 299android.content.res.Configuration#mnc}, which indicate the current mobile country code 300and mobile network code, respectively.</p> 301 </td> 302 </tr> 303 <tr id="LocaleQualifier"> 304 <td>Language and region</td> 305 <td>Examples:<br/> 306 <code>en</code><br/> 307 <code>fr</code><br/> 308 <code>en-rUS</code><br/> 309 <code>fr-rFR</code><br/> 310 <code>fr-rCA</code><br/> 311 etc. 312 </td> 313 <td><p>The language is defined by a two-letter <a 314href="http://www.loc.gov/standards/iso639-2/php/code_list.php">ISO 315 639-1</a> language code, optionally followed by a two letter 316 <a 317href="http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html">ISO 318 3166-1-alpha-2</a> region code (preceded by lowercase "{@code r}"). 319 </p><p> 320 The codes are <em>not</em> case-sensitive; the {@code r} prefix is used to 321 distinguish the region portion. 322 You cannot specify a region alone.</p> 323 <p>This can change during the life 324of your application if the user changes his or her language in the system settings. See <a 325href="runtime-changes.html">Handling Runtime Changes</a> for information about 326how this can affect your application during runtime.</p> 327 <p>See <a href="localization.html">Localization</a> for a complete guide to localizing 328your application for other languages.</p> 329 <p>Also see the {@link android.content.res.Configuration#locale} configuration field, which 330indicates the current locale.</p> 331 </td> 332 </tr> 333 <tr id="SmallestScreenWidthQualifier"> 334 <td>smallestWidth</td> 335 <td><code>sw<N>dp</code><br/><br/> 336 Examples:<br/> 337 <code>sw320dp</code><br/> 338 <code>sw600dp</code><br/> 339 <code>sw720dp</code><br/> 340 etc. 341 </td> 342 <td> 343 <p>The fundamental size of a screen, as indicated by the shortest dimension of the available 344screen area. Specifically, the device's smallestWidth is the shortest of the screen's available 345height and width (you may also think of it as the "smallest possible width" for the screen). You can 346use this qualifier to ensure that, regardless of the screen's current orientation, your 347application's has at least {@code <N>} dps of width available for it UI.</p> 348 <p>For example, if your layout requires that its smallest dimension of screen area be at 349least 600 dp at all times, then you can use this qualifer to create the layout resources, {@code 350res/layout-sw600dp/}. The system will use these resources only when the smallest dimension of 351available screen is at least 600dp, regardless of whether the 600dp side is the user-perceived 352height or width. The smallestWidth is a fixed screen size characteristic of the device; <strong>the 353device's smallestWidth does not change when the screen's orientation changes</strong>.</p> 354 <p>The smallestWidth of a device takes into account screen decorations and system UI. For 355example, if the device has some persistent UI elements on the screen that account for space along 356the axis of the smallestWidth, the system declares the smallestWidth to be smaller than the actual 357screen size, because those are screen pixels not available for your UI. Thus, the value you use 358should be the actual smallest dimension <em>required by your layout</em> (usually, this value is the 359"smallest width" that your layout supports, regardless of the screen's current orientation).</p> 360 <p>Some values you might use here for common screen sizes:</p> 361 <ul> 362 <li>320, for devices with screen configurations such as: 363 <ul> 364 <li>240x320 ldpi (QVGA handset)</li> 365 <li>320x480 mdpi (handset)</li> 366 <li>480x800 hdpi (high density handset)</li> 367 </ul> 368 </li> 369 <li>480, for screens such as 480x800 mdpi (tablet/handset).</li> 370 <li>600, for screens such as 600x1024 mdpi (7" tablet).</li> 371 <li>720, for screens such as 720x1280 mdpi (10" tablet).</li> 372 </ul> 373 <p>When your application provides multiple resource directories with different values for 374 the smallestWidth qualifier, the system uses the one closest to (without exceeding) the 375device's smallestWidth. </p> 376 <p><em>Added in API level 13.</em></p> 377 <p>Also see the <a 378href="{@docRoot}guide/topics/manifest/supports-screens-element.html#requiresSmallest">{@code 379android:requiresSmallestWidthDp}</a> attribute, which declares the minimum smallestWidth with which 380your application is compatible, and the {@link 381android.content.res.Configuration#smallestScreenWidthDp} configuration field, which holds the 382device's smallestWidth value.</p> 383 <p>For more information about designing for different screens and using this 384qualifier, see the <a href="{@docRoot}guide/practices/screens_support.html">Supporting 385Multiple Screens</a> developer guide.</p> 386 </td> 387 </tr> 388 <tr id="ScreenWidthQualifier"> 389 <td>Available width</td> 390 <td><code>w<N>dp</code><br/><br/> 391 Examples:<br/> 392 <code>w720dp</code><br/> 393 <code>w1024dp</code><br/> 394 etc. 395 </td> 396 <td> 397 <p>Specifies a minimum available screen width, in {@code dp} units at which the resource 398 should be used—defined by the <code><N></code> value. This 399 configuration value will change when the orientation 400 changes between landscape and portrait to match the current actual width.</p> 401 <p>When your application provides multiple resource directories with different values 402 for this configuration, the system uses the one closest to (without exceeding) 403 the device's current screen width. The 404 value here takes into account screen decorations, so if the device has some 405 persistent UI elements on the left or right edge of the display, it 406 uses a value for the width that is smaller than the real screen size, accounting 407 for these UI elements and reducing the application's available space.</p> 408 <p><em>Added in API level 13.</em></p> 409 <p>Also see the {@link android.content.res.Configuration#screenWidthDp} 410 configuration field, which holds the current screen width.</p> 411 <p>For more information about designing for different screens and using this 412qualifier, see the <a href="{@docRoot}guide/practices/screens_support.html">Supporting 413Multiple Screens</a> developer guide.</p> 414 </td> 415 </tr> 416 <tr id="ScreenHeightQualifier"> 417 <td>Available height</td> 418 <td><code>h<N>dp</code><br/><br/> 419 Examples:<br/> 420 <code>h720dp</code><br/> 421 <code>h1024dp</code><br/> 422 etc. 423 </td> 424 <td> 425 <p>Specifies a minimum available screen height, in "dp" units at which the resource 426 should be used—defined by the <code><N></code> value. This 427 configuration value will change when the orientation 428 changes between landscape and portrait to match the current actual height.</p> 429 <p>When your application provides multiple resource directories with different values 430 for this configuration, the system uses the one closest to (without exceeding) 431 the device's current screen height. The 432 value here takes into account screen decorations, so if the device has some 433 persistent UI elements on the top or bottom edge of the display, it uses 434 a value for the height that is smaller than the real screen size, accounting 435 for these UI elements and reducing the application's available space. Screen 436 decorations that are not fixed (such as a phone status bar that can be 437 hidden when full screen) are <em>not</em> accounted for here, nor are 438 window decorations like the title bar or action bar, so applications must be prepared to 439 deal with a somewhat smaller space than they specify. 440 <p><em>Added in API level 13.</em></p> 441 <p>Also see the {@link android.content.res.Configuration#screenHeightDp} 442 configuration field, which holds the current screen width.</p> 443 <p>For more information about designing for different screens and using this 444qualifier, see the <a href="{@docRoot}guide/practices/screens_support.html">Supporting 445Multiple Screens</a> developer guide.</p> 446 </td> 447 </tr> 448 <tr id="ScreenSizeQualifier"> 449 <td>Screen size</td> 450 <td> 451 <code>small</code><br/> 452 <code>normal</code><br/> 453 <code>large</code><br/> 454 <code>xlarge</code> 455 </td> 456 <td> 457 <ul class="nolist"> 458 <li>{@code small}: Screens that are of similar size to a 459 low-density QVGA screen. The minimum layout size for a small screen 460 is approximately 320x426 dp units. Examples are QVGA low density and VGA high 461 density.</li> 462 <li>{@code normal}: Screens that are of similar size to a 463 medium-density HVGA screen. The minimum 464 layout size for a normal screen is approximately 320x470 dp units. Examples 465 of such screens a WQVGA low density, HVGA medium density, WVGA 466 high density.</li> 467 <li>{@code large}: Screens that are of similar size to a 468 medium-density VGA screen. 469 The minimum layout size for a large screen is approximately 480x640 dp units. 470 Examples are VGA and WVGA medium density screens.</li> 471 <li>{@code xlarge}: Screens that are considerably larger than the traditional 472 medium-density HVGA screen. The minimum layout size for an xlarge screen 473 is approximately 720x960 dp units. In most cases, devices with extra large 474 screens would be too large to carry in a pocket and would most likely 475 be tablet-style devices. <em>Added in API level 9.</em></li> 476 </ul> 477 <p class="note"><strong>Note:</strong> Using a size qualifier does not imply that the 478resources are <em>only</em> for screens of that size. If you do not provide alternative 479resources with qualifiers that better match the current device configuration, the system may use 480whichever resources are the <a href="#BestMatch">best match</a>.</p> 481 <p class="caution"><strong>Caution:</strong> If all your resources use a size qualifier that 482is <em>larger</em> than the current screen, the system will <strong>not</strong> use them and your 483application will crash at runtime (for example, if all layout resources are tagged with the {@code 484xlarge} qualifier, but the device is a normal-size screen).</p> 485 <p><em>Added in API level 4.</em></p> 486 487 <p>See <a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple 488Screens</a> for more information.</p> 489 <p>Also see the {@link android.content.res.Configuration#screenLayout} configuration field, 490which indicates whether the screen is small, normal, 491or large.</p> 492 </td> 493 </tr> 494 <tr id="ScreenAspectQualifier"> 495 <td>Screen aspect</td> 496 <td> 497 <code>long</code><br/> 498 <code>notlong</code> 499 </td> 500 <td> 501 <ul class="nolist"> 502 <li>{@code long}: Long screens, such as WQVGA, WVGA, FWVGA</li> 503 <li>{@code notlong}: Not long screens, such as QVGA, HVGA, and VGA</li> 504 </ul> 505 <p><em>Added in API level 4.</em></p> 506 <p>This is based purely on the aspect ratio of the screen (a "long" screen is wider). This 507is not related to the screen orientation.</p> 508 <p>Also see the {@link android.content.res.Configuration#screenLayout} configuration field, 509which indicates whether the screen is long.</p> 510 </td> 511 </tr> 512 <tr id="OrientationQualifier"> 513 <td>Screen orientation</td> 514 <td> 515 <code>port</code><br/> 516 <code>land</code> <!-- <br/> 517 <code>square</code> --> 518 </td> 519 <td> 520 <ul class="nolist"> 521 <li>{@code port}: Device is in portrait orientation (vertical)</li> 522 <li>{@code land}: Device is in landscape orientation (horizontal)</li> 523 <!-- Square mode is currently not used. --> 524 </ul> 525 <p>This can change during the life of your application if the user rotates the 526screen. See <a href="runtime-changes.html">Handling Runtime Changes</a> for information about 527how this affects your application during runtime.</p> 528 <p>Also see the {@link android.content.res.Configuration#orientation} configuration field, 529which indicates the current device orientation.</p> 530 </td> 531 </tr> 532 <tr id="DockQualifier"> 533 <td>Dock mode</td> 534 <td> 535 <code>car</code><br/> 536 <code>desk</code> 537 </td> 538 <td> 539 <ul class="nolist"> 540 <li>{@code car}: Device is in a car dock</li> 541 <li>{@code desk}: Device is in a desk dock</li> 542 </ul> 543 <p><em>Added in API level 8.</em></p> 544 <p>This can change during the life of your application if the user places the device in a 545dock. You can enable or disable this mode using {@link 546android.app.UiModeManager}. See <a href="runtime-changes.html">Handling Runtime Changes</a> for 547information about how this affects your application during runtime.</p> 548 </td> 549 </tr> 550 <tr id="NightQualifier"> 551 <td>Night mode</td> 552 <td> 553 <code>night</code><br/> 554 <code>notnight</code> 555 </td> 556 <td> 557 <ul class="nolist"> 558 <li>{@code night}: Night time</li> 559 <li>{@code notnight}: Day time</li> 560 </ul> 561 <p><em>Added in API level 8.</em></p> 562 <p>This can change during the life of your application if night mode is left in 563auto mode (default), in which case the mode changes based on the time of day. You can enable 564or disable this mode using {@link android.app.UiModeManager}. See <a 565href="runtime-changes.html">Handling Runtime Changes</a> for information about how this affects your 566application during runtime.</p> 567 </td> 568 </tr> 569 <tr id="DensityQualifier"> 570 <td>Screen pixel density (dpi)</td> 571 <td> 572 <code>ldpi</code><br/> 573 <code>mdpi</code><br/> 574 <code>hdpi</code><br/> 575 <code>xhdpi</code><br/> 576 <code>nodpi</code><br/> 577 <code>tvdpi</code> 578 </td> 579 <td> 580 <ul class="nolist"> 581 <li>{@code ldpi}: Low-density screens; approximately 120dpi.</li> 582 <li>{@code mdpi}: Medium-density (on traditional HVGA) screens; approximately 583160dpi.</li> 584 <li>{@code hdpi}: High-density screens; approximately 240dpi.</li> 585 <li>{@code xhdpi}: Extra high-density screens; approximately 320dpi. <em>Added in API 586Level 8</em></li> 587 <li>{@code nodpi}: This can be used for bitmap resources that you do not want to be scaled 588to match the device density.</li> 589 <li>{@code tvdpi}: Screens somewhere between mdpi and hdpi; approximately 213dpi. This is 590not considered a "primary" density group. It is mostly intended for televisions and most 591apps shouldn't need it—providing mdpi and hdpi resources is sufficient for most apps and 592the system will scale them as appropriate. This qualifier was introduced with API level 13.</li> 593 </ul> 594 <p>There is a 3:4:6:8 scaling ratio between the four primary densities (ignoring the 595tvdpi density). So, a 9x9 bitmap in ldpi is 12x12 in mdpi, 18x18 in hdpi and 24x24 in xhdpi.</p> 596 <p>If you decide that your image resources don't look good enough on a television or 597other certain devices and want to try tvdpi resources, the scaling factor is 1.33*mdpi. For 598example, a 100px x 100px image for mdpi screens should be 133px x 133px for tvdpi.</p> 599 <p class="note"><strong>Note:</strong> Using a density qualifier does not imply that the 600resources are <em>only</em> for screens of that density. If you do not provide alternative 601resources with qualifiers that better match the current device configuration, the system may use 602whichever resources are the <a href="#BestMatch">best match</a>.</p> 603 <p>See <a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple 604Screens</a> for more information about how to handle different screen densities and how Android 605might scale your bitmaps to fit the current density.</p> 606 </td> 607 </tr> 608 <tr id="TouchscreenQualifier"> 609 <td>Touchscreen type</td> 610 <td> 611 <code>notouch</code><br/> 612 <code>stylus</code><br/> 613 <code>finger</code> 614 </td> 615 <td> 616 <ul class="nolist"> 617 <li>{@code notouch}: Device does not have a touchscreen.</li> 618 <li>{@code stylus}: Device has a resistive touchscreen that's suited for use with a 619stylus.</li> 620 <li>{@code finger}: Device has a touchscreen.</li> 621 </ul> 622 <p>Also see the {@link android.content.res.Configuration#touchscreen} configuration field, 623which indicates the type of touchscreen on the device.</p> 624 </td> 625 </tr> 626 <tr id="KeyboardAvailQualifier"> 627 <td>Keyboard availability</td> 628 <td> 629 <code>keysexposed</code><br/> 630 <code>keyshidden</code><br/> 631 <code>keyssoft</code> 632 </td> 633 <td> 634 <ul class="nolist"> 635 <li>{@code keysexposed}: Device has a keyboard available. If the device has a 636software keyboard enabled (which is likely), this may be used even when the hardware keyboard is 637<em>not</em> exposed to the user, even if the device has no hardware keyboard. If no software 638keyboard is provided or it's disabled, then this is only used when a hardware keyboard is 639exposed.</li> 640 <li>{@code keyshidden}: Device has a hardware keyboard available but it is 641hidden <em>and</em> the device does <em>not</em> have a software keyboard enabled.</li> 642 <li>{@code keyssoft}: Device has a software keyboard enabled, whether it's 643visible or not.</li> 644 </ul> 645 <p>If you provide <code>keysexposed</code> resources, but not <code>keyssoft</code> 646resources, the system uses the <code>keysexposed</code> resources regardless of whether a 647keyboard is visible, as long as the system has a software keyboard enabled.</p> 648 <p>This can change during the life of your application if the user opens a hardware 649keyboard. See <a href="runtime-changes.html">Handling Runtime Changes</a> for information about how 650this affects your application during runtime.</p> 651 <p>Also see the configuration fields {@link 652android.content.res.Configuration#hardKeyboardHidden} and {@link 653android.content.res.Configuration#keyboardHidden}, which indicate the visibility of a hardware 654keyboard and and the visibility of any kind of keyboard (including software), respectively.</p> 655 </td> 656 </tr> 657 <tr id="ImeQualifier"> 658 <td>Primary text input method</td> 659 <td> 660 <code>nokeys</code><br/> 661 <code>qwerty</code><br/> 662 <code>12key</code> 663 </td> 664 <td> 665 <ul class="nolist"> 666 <li>{@code nokeys}: Device has no hardware keys for text input.</li> 667 <li>{@code qwerty}: Device has a hardware qwerty keyboard, whether it's visible to the 668user 669or not.</li> 670 <li>{@code 12key}: Device has a hardware 12-key keyboard, whether it's visible to the user 671or not.</li> 672 </ul> 673 <p>Also see the {@link android.content.res.Configuration#keyboard} configuration field, 674which indicates the primary text input method available.</p> 675 </td> 676 </tr> 677 <tr id="NavAvailQualifier"> 678 <td>Navigation key availability</td> 679 <td> 680 <code>navexposed</code><br/> 681 <code>navhidden</code> 682 </td> 683 <td> 684 <ul class="nolist"> 685 <li>{@code navexposed}: Navigation keys are available to the user.</li> 686 <li>{@code navhidden}: Navigation keys are not available (such as behind a closed 687lid).</li> 688 </ul> 689 <p>This can change during the life of your application if the user reveals the navigation 690keys. See <a href="runtime-changes.html">Handling Runtime Changes</a> for 691information about how this affects your application during runtime.</p> 692 <p>Also see the {@link android.content.res.Configuration#navigationHidden} configuration 693field, which indicates whether navigation keys are hidden.</p> 694 </td> 695 </tr> 696 <tr id="TouchQualifier"> 697 <td>Primary non-touch navigation method</td> 698 <td> 699 <code>nonav</code><br/> 700 <code>dpad</code><br/> 701 <code>trackball</code><br/> 702 <code>wheel</code> 703 </td> 704 <td> 705 <ul class="nolist"> 706 <li>{@code nonav}: Device has no navigation facility other than using the 707touchscreen.</li> 708 <li>{@code dpad}: Device has a directional-pad (d-pad) for navigation.</li> 709 <li>{@code trackball}: Device has a trackball for navigation.</li> 710 <li>{@code wheel}: Device has a directional wheel(s) for navigation (uncommon).</li> 711 </ul> 712 <p>Also see the {@link android.content.res.Configuration#navigation} configuration field, 713which indicates the type of navigation method available.</p> 714 </td> 715 </tr> 716<!-- DEPRECATED 717 <tr> 718 <td>Screen dimensions</td> 719 <td>Examples:<br/> 720 <code>320x240</code><br/> 721 <code>640x480</code><br/> 722 etc. 723 </td> 724 <td> 725 <p>The larger dimension must be specified first. <strong>This configuration is deprecated 726and should not be used</strong>. Instead use "screen size," "wider/taller screens," and "screen 727orientation" described above.</p> 728 </td> 729 </tr> 730--> 731 <tr id="VersionQualifier"> 732 <td>Platform Version (API level)</td> 733 <td>Examples:<br/> 734 <code>v3</code><br/> 735 <code>v4</code><br/> 736 <code>v7</code><br/> 737 etc.</td> 738 <td> 739 <p>The API level supported by the device. For example, <code>v1</code> for API level 7401 (devices with Android 1.0 or higher) and <code>v4</code> for API level 4 (devices with Android 7411.6 or higher). See the <a 742href="{@docRoot}guide/appendix/api-levels.html">Android API levels</a> document for more information 743about these values.</p> 744 <p class="caution"><strong>Caution:</strong> Android 1.5 and 1.6 only match resources 745with this qualifier when it exactly matches the platform version. See the section below about <a 746href="#KnownIssues">Known Issues</a> for more information.</p> 747 </td> 748 </tr> 749</table> 750 751 752<p class="note"><strong>Note:</strong> Some configuration qualifiers have been added since Android 7531.0, so not all versions of Android support all the qualifiers. Using a new qualifier implicitly 754adds the platform version qualifier so that older devices are sure to ignore it. For example, using 755a <code>w600dp</code> qualifier will automatically include the <code>v13</code> qualifier, because 756the available-width qualifier was new in API level 13. To avoid any issues, always include a set of 757default resources (a set of resources with <em>no qualifiers</em>). For more information, see the 758section about <a href="#Compatibility">Providing the Best Device Compatibility with 759Resources</a>.</p> 760 761 762 763<h3 id="QualifierRules">Qualifier name rules</h3> 764 765<p>Here are some rules about using configuration qualifier names:</p> 766 767<ul> 768 <li>You can specify multiple qualifiers for a single set of resources, separated by dashes. For 769example, <code>drawable-en-rUS-land</code> applies to US-English devices in landscape 770orientation.</li> 771 <li>The qualifiers must be in the order listed in <a href="#table2">table 2</a>. For 772example: 773 <ul> 774 <li>Wrong: <code>drawable-hdpi-port/</code></li> 775 <li>Correct: <code>drawable-port-hdpi/</code></li> 776 </ul> 777 </li> 778 <li>Alternative resource directories cannot be nested. For example, you cannot have 779<code>res/drawable/drawable-en/</code>.</li> 780 <li>Values are case-insensitive. The resource compiler converts directory names 781 to lower case before processing to avoid problems on case-insensitive 782 file systems. Any capitalization in the names is only to benefit readability.</li> 783 <li>Only one value for each qualifier type is supported. For example, if you want to use 784the same drawable files for Spain and France, you <em>cannot</em> have a directory named 785<code>drawable-rES-rFR/</code>. Instead you need two resource directories, such as 786<code>drawable-rES/</code> and <code>drawable-rFR/</code>, which contain the appropriate files. 787However, you are not required to actually duplicate the same files in both locations. Instead, you 788can create an alias to a resource. See <a href="#AliasResources">Creating 789alias resources</a> below.</li> 790</ul> 791 792<p>After you save alternative resources into directories named with 793these qualifiers, Android automatically applies the resources in your application based on the 794current device configuration. Each time a resource is requested, Android checks for alternative 795resource directories that contain the requested resource file, then <a href="#BestMatch">finds the 796best-matching resource</a> (discussed below). If there are no alternative resources that match 797a particular device configuration, then Android uses the corresponding default resources (the 798set of resources for a particular resource type that does not include a configuration 799qualifier).</p> 800 801 802 803<h3 id="AliasResources">Creating alias resources</h3> 804 805<p>When you have a resource that you'd like to use for more than one device 806configuration (but do not want to provide as a default resource), you do not need to put the same 807resource in more than one alternative resource directory. Instead, you can (in some cases) create an 808alternative 809resource that acts as an alias for a resource saved in your default resource directory.</p> 810 811<p class="note"><strong>Note:</strong> Not all resources offer a mechanism by which you can 812create an alias to another resource. In particular, animation, menu, raw, and other unspecified 813resources in the {@code xml/} directory do not offer this feature.</p> 814 815<p>For example, imagine you have an application icon, {@code icon.png}, and need unique version of 816it for different locales. However, two locales, English-Canadian and French-Canadian, need to 817use the same version. You might assume that you need to copy the same image 818into the resource directory for both English-Canadian and French-Canadian, but it's 819not true. Instead, you can save the image that's used for both as {@code icon_ca.png} (any 820name other than {@code icon.png}) and put 821it in the default {@code res/drawable/} directory. Then create an {@code icon.xml} file in {@code 822res/drawable-en-rCA/} and {@code res/drawable-fr-rCA/} that refers to the {@code icon_ca.png} 823resource using the {@code <bitmap>} element. This allows you to store just one version of the 824PNG file and two small XML files that point to it. (An example XML file is shown below.)</p> 825 826 827<h4>Drawable</h4> 828 829<p>To create an alias to an existing drawable, use the {@code <bitmap>} element. 830For example:</p> 831 832<pre> 833<?xml version="1.0" encoding="utf-8"?> 834<bitmap xmlns:android="http://schemas.android.com/apk/res/android" 835 android:src="@drawable/icon_ca" /> 836</pre> 837 838<p>If you save this file as {@code icon.xml} (in an alternative resource directory, such as 839{@code res/drawable-en-rCA/}), it is compiled into a resource that you 840can reference as {@code R.drawable.icon}, but is actually an alias for the {@code 841R.drawable.icon_ca} resource (which is saved in {@code res/drawable/}).</p> 842 843 844<h4>Layout</h4> 845 846<p>To create an alias to an existing layout, use the {@code <include>} 847element, wrapped in a {@code <merge>}. For example:</p> 848 849<pre> 850<?xml version="1.0" encoding="utf-8"?> 851<merge> 852 <include layout="@layout/main_ltr"/> 853</merge> 854</pre> 855 856<p>If you save this file as {@code main.xml}, it is compiled into a resource you can reference 857as {@code R.layout.main}, but is actually an alias for the {@code R.layout.main_ltr} 858resource.</p> 859 860 861<h4>Strings and other simple values</h4> 862 863<p>To create an alias to an existing string, simply use the resource ID of the desired 864string as the value for the new string. For example:</p> 865 866<pre> 867<?xml version="1.0" encoding="utf-8"?> 868<resources> 869 <string name="hello">Hello</string> 870 <string name="hi">@string/hello</string> 871</resources> 872</pre> 873 874<p>The {@code R.string.hi} resource is now an alias for the {@code R.string.hello}.</p> 875 876<p> <a href="{@docRoot}guide/topics/resources/more-resources.html">Other simple values</a> work the 877same way. For example, a color:</p> 878 879<pre> 880<?xml version="1.0" encoding="utf-8"?> 881<resources> 882 <color name="yellow">#f00</color> 883 <color name="highlight">@color/red</color> 884</resources> 885</pre> 886 887 888 889 890<h2 id="Compatibility">Providing the Best Device Compatibility with Resources</h2> 891 892<p>In order for your application to support multiple device configurations, it's very important that 893you always provide default resources for each type of resource that your application uses.</p> 894 895<p>For example, if your application supports several languages, always include a {@code 896values/} directory (in which your strings are saved) <em>without</em> a <a 897href="#LocaleQualifier">language and region qualifier</a>. If you instead put all your string files 898in directories that have a language and region qualifier, then your application will crash when run 899on a device set to a language that your strings do not support. But, as long as you provide default 900{@code values/} resources, then your application will run properly (even if the user doesn't 901understand that language—it's better than crashing).</p> 902 903<p>Likewise, if you provide different layout resources based on the screen orientation, you should 904pick one orientation as your default. For example, instead of providing layout resources in {@code 905layout-land/} for landscape and {@code layout-port/} for portrait, leave one as the default, such as 906{@code layout/} for landscape and {@code layout-port/} for portrait.</p> 907 908<p>Providing default resources is important not only because your application might run on a 909configuration you had not anticipated, but also because new versions of Android sometimes add 910configuration qualifiers that older versions do not support. If you use a new resource qualifier, 911but maintain code compatibility with older versions of Android, then when an older version of 912Android runs your application, it will crash if you do not provide default resources, because it 913cannot use the resources named with the new qualifier. For example, if your <a 914href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#min">{@code 915minSdkVersion}</a> is set to 4, and you qualify all of your drawable resources using <a 916href="#NightQualifier">night mode</a> ({@code night} or {@code notnight}, which were added in API 917Level 8), then an API level 4 device cannot access your drawable resources and will crash. In this 918case, you probably want {@code notnight} to be your default resources, so you should exclude that 919qualifier so your drawable resources are in either {@code drawable/} or {@code drawable-night/}.</p> 920 921<p>So, in order to provide the best device compatibility, always provide default 922resources for the resources your application needs to perform properly. Then create alternative 923resources for specific device configurations using the configuration qualifiers.</p> 924 925<p>There is one exception to this rule: If your application's <a 926href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#min">{@code minSdkVersion}</a> is 4 or 927greater, you <em>do not</em> need default drawable resources when you provide alternative drawable 928resources with the <a href="#DensityQualifier">screen density</a> qualifier. Even without default 929drawable resources, Android can find the best match among the alternative screen densities and scale 930the bitmaps as necessary. However, for the best experience on all types of devices, you should 931provide alternative drawables for all three types of density. If your <a 932href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#min">{@code minSdkVersion}</a> is 933<em>less than</em> 4 (Android 1.5 or lower), be aware that the screen size, density, and aspect 934qualifiers are not supported on Android 1.5 or lower, so you might need to perform additional 935compatibility for these versions.</p> 936 937 938<h3 id="ScreenCompatibility">Providing screen resource compatibility for Android 1.5</h3> 939 940<p>Android 1.5 (and lower) does not support the following configuration qualifers:</p> 941<dl> 942 <dt><a href="#DensityQualifier">Density</a></dt> 943 <dd>{@code ldpi}, {@code mdpi}, {@code ldpi}, and {@code nodpi}</dd> 944 <dt><a href="#ScreenSizeQualifier">Screen size</a></dt> 945 <dd>{@code small}, {@code normal}, and {@code large}</dd> 946 <dt><a href="#ScreenAspectQualifier">Screen aspect</a></dt> 947 <dd>{@code long} and {@code notlong}</dd> 948</dl> 949 950<p>These configuration qualifiers were introduced in Android 1.6, so Android 1.5 (API level 3) and 951lower does not support them. If you use these configuration qualifiers and do not provide 952corresponding default resources, then an Android 1.5 device might use any one of the resource 953directories named with the above screen configuration qualifiers, because it ignores these 954qualifiers and uses whichever otherwise-matching drawable resource it finds first.</p> 955 956<p>For example, if your application supports Android 1.5 and includes drawable resources for 957each density type ({@code drawable-ldpi/}, {@code drawable-mdpi/}, and {@code drawable-ldpi/}), 958and does <em>not</em> include default drawable resources ({@code drawable/}), then 959an Android 1.5 will use drawables from any one of the alternative resource directories, which 960can result in a user interface that's less than ideal.<p> 961 962<p>So, to provide compatibility with Android 1.5 (and lower) when using the screen configuration 963qualifiers:</p> 964<ol> 965 <li>Provide default resources that are for medium-density, normal, and notlong screens. 966 967 <p>Because all Android 1.5 devices have medium-density, normal, not-long screens, you can 968place these kinds of resources in the corresponding default resource directory. For example, put all 969medium density drawable resources in {@code drawable/} (instead of {@code drawable-mdpi/}), 970put {@code normal} size resources in the corresponding default resource directory, and {@code 971notlong} resources in the corresponding default resource directory.</p> 972 </li> 973 974 <li>Ensure that your <a href="{@docRoot}sdk/tools-notes.html">SDK Tools</a> version 975is r6 or greater. 976 977 <p>You need SDK Tools, Revision 6 (or greater), because it includes a new packaging tool that 978automatically applies an appropriate <a href="#VersionQualifier">version qualifier</a> to any 979resource directory named with a qualifier that does not exist in Android 1.0. For example, because 980the density qualifier was introduced in Android 1.6 (API level 4), when the packaging tool 981encounters a resource directory using the density qualifier, it adds {@code v4} to the directory 982name to ensure that older versions do not use those resources (only API level 4 and higher support 983that qualifier). Thus, by putting your medium-density resources in a directory <em>without</em> the 984{@code mdpi} qualifier, they are still accessible by Android 1.5, and any device that supports the 985density qualifer and has a medium-density screen also uses the default resources (which are mdpi) 986because they are the best match for the device (instead of using the {@code ldpi} or {@code hdpi} 987resources).</p> 988</li> 989</ol> 990 991<p class="note"><strong>Note:</strong> Later versions of Android, such as API level 8, 992introduce other configuration qualifiers that older version do not support. To provide the best 993compatibility, you should always include a set of default resources for each type of resource 994that your application uses, as discussed above to provide the best device compatibility.</p> 995 996 997 998<h2 id="BestMatch">How Android Finds the Best-matching Resource</h2> 999 1000<p>When you request a resource for which you provide alternatives, Android selects which 1001alternative resource to use at runtime, depending on the current device configuration. To 1002demonstrate how Android selects an alternative resource, assume the following drawable directories 1003each contain different versions of the same images:</p> 1004 1005<pre class="classic no-pretty-print"> 1006drawable/ 1007drawable-en/ 1008drawable-fr-rCA/ 1009drawable-en-port/ 1010drawable-en-notouch-12key/ 1011drawable-port-ldpi/ 1012drawable-port-notouch-12key/ 1013</pre> 1014 1015<p>And assume the following is the device configuration:</p> 1016 1017<p style="margin-left:1em;"> 1018Locale = <code>en-GB</code> <br/> 1019Screen orientation = <code>port</code> <br/> 1020Screen pixel density = <code>hdpi</code> <br/> 1021Touchscreen type = <code>notouch</code> <br/> 1022Primary text input method = <code>12key</code> 1023</p> 1024 1025<p>By comparing the device configuration to the available alternative resources, Android selects 1026drawables from {@code drawable-en-port}.</p> 1027 1028<p>The system arrives at its decision for which resources to use with the following 1029logic:</p> 1030 1031 1032<div class="figure" style="width:371px"> 1033<img src="{@docRoot}images/resources/res-selection-flowchart.png" alt="" height="471" /> 1034<p class="img-caption"><strong>Figure 2.</strong> Flowchart of how Android finds the 1035best-matching resource.</p> 1036</div> 1037 1038 1039<ol> 1040 <li>Eliminate resource files that contradict the device configuration. 1041 <p>The <code>drawable-fr-rCA/</code> directory is eliminated, because it 1042contradicts the <code>en-GB</code> locale.</p> 1043<pre class="classic no-pretty-print"> 1044drawable/ 1045drawable-en/ 1046<strike>drawable-fr-rCA/</strike> 1047drawable-en-port/ 1048drawable-en-notouch-12key/ 1049drawable-port-ldpi/ 1050drawable-port-notouch-12key/ 1051</pre> 1052<p class="note"><strong>Exception:</strong> Screen pixel density is the one qualifier that is not 1053eliminated due to a contradiction. Even though the screen density of the device is hdpi, 1054<code>drawable-port-ldpi/</code> is not eliminated because every screen density is 1055considered to be a match at this point. More information is available in the <a 1056href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple 1057Screens</a> document.</p></li> 1058 1059 <li>Pick the (next) highest-precedence qualifier in the list (<a href="#table2">table 2</a>). 1060(Start with MCC, then move down.) </li> 1061 <li>Do any of the resource directories include this qualifier? </li> 1062 <ul> 1063 <li>If No, return to step 2 and look at the next qualifier. (In the example, 1064 the answer is "no" until the language qualifier is reached.)</li> 1065 <li>If Yes, continue to step 4.</li> 1066 </ul> 1067 </li> 1068 1069 <li>Eliminate resource directories that do not include this qualifier. In the example, the system 1070eliminates all the directories that do not include a language qualifier:</li> 1071<pre class="classic no-pretty-print"> 1072<strike>drawable/</strike> 1073drawable-en/ 1074drawable-en-port/ 1075drawable-en-notouch-12key/ 1076<strike>drawable-port-ldpi/</strike> 1077<strike>drawable-port-notouch-12key/</strike> 1078</pre> 1079<p class="note"><strong>Exception:</strong> If the qualifier in question is screen pixel density, 1080Android selects the option that most closely matches the device screen density. 1081In general, Android prefers scaling down a larger original image to scaling up a smaller 1082original image. See <a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple 1083Screens</a>.</p> 1084 </li> 1085 1086 <li>Go back and repeat steps 2, 3, and 4 until only one directory remains. In the example, screen 1087orientation is the next qualifier for which there are any matches. 1088So, resources that do not specify a screen orientation are eliminated: 1089<pre class="classic no-pretty-print"> 1090<strike>drawable-en/</strike> 1091drawable-en-port/ 1092<strike>drawable-en-notouch-12key/</strike> 1093</pre> 1094<p>The remaining directory is {@code drawable-en-port}.</p> 1095 </li> 1096</ol> 1097 1098<p>Though this procedure is executed for each resource requested, the system further optimizes 1099some aspects. One such optimization is that once the device configuration is known, it might 1100eliminate alternative resources that can never match. For example, if the configuration 1101language is English ("en"), then any resource directory that has a language qualifier set to 1102something other than English is never included in the pool of resources checked (though a 1103resource directory <em>without</em> the language qualifier is still included).</p> 1104 1105<p>When selecting resources based on the screen size qualifiers, the system will use resources 1106designed for a screen smaller than the current screen if there are no resources that better match 1107(for example, a large-size screen will use normal-size screen resources if necessary). However, if 1108the only available resources are <em>larger</em> than the current screen, the system will 1109<strong>not</strong> use them and your application will crash if no other resources match the device 1110configuration (for example, if all layout resources are tagged with the {@code xlarge} qualifier, 1111but the device is a normal-size screen).</p> 1112 1113<p class="note"><strong>Note:</strong> The <em>precedence</em> of the qualifier (in <a 1114href="#table2">table 2</a>) is more important 1115than the number of qualifiers that exactly match the device. For example, in step 4 above, the last 1116choice on the list includes three qualifiers that exactly match the device (orientation, touchscreen 1117type, and input method), while <code>drawable-en</code> has only one parameter that matches 1118(language). However, language has a higher precedence than these other qualifiers, so 1119<code>drawable-port-notouch-12key</code> is out.</p> 1120 1121<p>To learn more about how to use resources in your application, continue to <a 1122href="accessing-resources.html">Accessing Resources</a>.</p> 1123 1124 1125 1126 1127<h2 id="KnownIssues">Known Issues</h2> 1128 1129<h3>Android 1.5 and 1.6: Version qualifier performs exact match, instead of best match</h3> 1130 1131<p>The correct behavior is for the system to match resources marked with a <a 1132href="#VersionQualifier">version qualifier</a> equal 1133to or less than the platform version on the device, but on Android 1.5 and 1.6, (API level 3 and 4), 1134there is a bug that causes the system to match resources marked with the version qualifier 1135only when it exactly matches the version on the device.</p> 1136 1137<p><b>The workaround:</b> To provide version-specific resources, abide by this behavior. However, 1138because this bug is fixed in versions of Android available after 1.6, if 1139you need to differentiate resources between Android 1.5, 1.6, and later versions, then you only need 1140to apply the version qualifier to the 1.6 resources and one to match all later versions. Thus, this 1141is effectively a non-issue.</p> 1142 1143<p>For example, if you want drawable resources that are different on each Android 1.5, 1.6, 1144and 2.0.1 (and later), create three drawable directories: {@code drawable/} (for 1.5 and lower), 1145{@code drawable-v4} (for 1.6), and {@code drawable-v6} (for 2.0.1 and later—version 2.0, v5, 1146is no longer available).</p> 1147 1148 1149