Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 44108b54 authored by Dirk Dougherty's avatar Dirk Dougherty
Browse files

Doc change: Move framework api change info higher in platform notes documents. 

Small adjustment to compatibility doc.

Change-Id: I2af896292b00323d7f4eb2c828c8dea36b9e94ad
parent 68728cb3

docs/html/guide/practices/compatibility.jd

+4 −3
Original line number Diff line number Diff line
@@ -36,15 +36,16 @@ exchange, however, it also means that your apps will have to cope with that same 
variety of hardware.</p>



<p>Fortunately, Android has built-in tools and support that make it easy for

your apps to do that, while at the same time maintaining control of what types

of devices your app is available to. If you do your work properly, users

your apps to do that, while at the same time letting you maintain control of

what types of devices your app is available to. With a bit of forethought and

some minor changes in your app's manifest file, you can ensure that users

whose devices can’t run your app will never see it in the Android Market, and

will not get in trouble by downloading it. This page explains how you can

control which devices have access to your apps, and how to prepare your apps to

make sure they reach the right audience.</p>





<h3 id="defined">What does “Compatibility” mean?</h3>

<h3 id="defined">What does “compatibility” mean?</h3>



<p>A device is “Android compatible” if it can correctly run apps written for the

<em>Android execution environment</em>. The exact details of the Android execution

docs/html/guide/practices/screens_support.jd

+3 −1
Original line number Diff line number Diff line
@@ -171,7 +171,9 @@ device screen, and adapts them to the actual pixel map of the screen.</p> 


<p>The table below lists some of the more common screens supported

by Android and illustrates how the platform maps them to generalized screen

configurations.</p>

configurations. Some devices use screens that are not specifically listed

in the table &mdash; the platform maps those to the same set generalized

screen configurations. </p>



<p class="table-caption" id="screens-table"><strong>Table 1.</strong> Examples of

device screens supported by Android.</p>

docs/html/sdk/android-1.5.jd

+127 −118
Original line number Diff line number Diff line
@@ -14,15 +14,21 @@ sdk.platform.deployableDate=May 2009 
<ol>

  <li><a href="#features">Platform Highlights</a></li>

  <li><a href="#relnotes">Revisions</a></li>

  <li><a href="#api-level">API Level</a></li>

  <li><a href="#api">Framework API Changes</a>

  <li><a href="#apps">Built-in Applications</a></li>

  <li><a href="#locs">Locales</a></li>

  <li><a href="#skins">Emulator Skins</a></li>

	<li><a href="#api">Framework API</a>



    </ol>

  </li>

</ol>



<h2>Reference</h2>

<ol>

	<li><a href="#api-level">API level</a></li>

	<li><a href="#api-changes">API changes summary</a></li>

	<li><a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API differences report &raquo;</a> </li>

        </ol></li>

<li><a

href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API

Differences Report &raquo;</a> </li>

</ol>



<h2>See Also</h2>
@@ -87,7 +93,8 @@ function toggleDiv(link) { 
</script>

<style>

.toggleable {

padding: .25em 1em;

  padding: .25em 1em 0em 1em;

  margin-bottom: 0;

}

.toggleme {

  padding: 1em 1em 0 2em;
@@ -162,6 +169,106 @@ padding: .25em 1em; 
 </div>

</div>





<h2 id="api-level">API Level</h2>



<p>The Android {@sdkPlatformVersion} platform delivers an updated version of

the framework API. The Android {@sdkPlatformVersion} API

is assigned an integer identifier &mdash;

<strong>{@sdkPlatformApiLevel}</strong> &mdash; that is

stored in the system itself. This identifier, called the "API Level", allows the

system to correctly determine whether an application is compatible with

the system, prior to installing the application. </p>



<p>To use APIs introduced in Android {@sdkPlatformVersion} in your

application, you need to set the proper value, "{@sdkPlatformApiLevel}", in the

<code>android:minSdkVersion</code> attributes of the <code>&lt;uses-sdk&gt;</code>

element in your application's manifest. </p>



<p>For more information about how to use API Level, see the <a

href="{@docRoot}guide/appendix/api-levels.html">API Levels</a> document. </p>





<h2 id="api">Framework API Changes</h2>



<p>The sections below provide information about the application framework API provided by the Android {@sdkPlatformVersion} platform. </p>



<h3>UI framework</h3>

  <ul>

    <li>Framework for easier background/UI thread interaction</li>

    <li>New {@link android.widget.SlidingDrawer SlidingDrawer} widget</li>

    <li>New {@link android.widget.HorizontalScrollView HorizontalScrollview} widget</li>

  </ul>



<h3>AppWidget framework</h3>

  <ul>

    <li>APIs for creating secure home screen {@link android.appwidget

AppWidgets}. For information about how to use AppWidgets, see the Developer's

Guide <a href="{@docRoot}guide/topics/appwidgets/index.html">AppWidgets</a>

documentation. Also see <a

href="http://android-developers.blogspot.com/2009/04/introducing-home-screen-widgets-and.html">

Introducing home screen widgets and the AppWidget

framework</a> on the Android Developer's Blog.</li>

    <li>APIs for populating {@link android.provider.LiveFolders Live Folders}

        with custom content.</li>

  </ul>



<h3>Media framework</h3>

  <ul>

    <li>Raw audio recording and playback APIs</li>

    <li>Interactive MIDI playback engine</li>

    <li>Video recording APIs for developers (3GP format)</li>

    <li>Video and photo sharing Intents</li>

    <li>Media search Intent</li>

  </ul>



<h3>Input Method framework </h3>

   <ul>

    <li>{@link android.inputmethodservice.InputMethodService Input Method

        Service} framework</li>

    <li>Text-prediction engine</li>

    <li>Ability to provide downloadable IMEs to users</li>

  </ul>



<h3>Application-defined hardware requirements</h3>



<p>Applications can now use a new element in their manifest files, <a

href="{@docRoot}guide/topics/manifest/uses-configuration-element.html"><code>&lt;uses-configuration&gt;</code></a>

 to indicate to the Android system what hardware features

they require in order to function properly. For example, an application might

use the element to specify that it requires a physical keyboard or a particular

navigation device, such as a trackball. Prior to installing the application, the

Android system checks the attributes defined for the

<code>&lt;uses-configuration&gt;</code> element and allows the installation to

continue only if the required hardware is present.</p>



<h3>Speech recognition framework</h3>

    <ul>

    <li>Support for using speech recognition libraries via Intent. See {@link

android.speech.RecognizerIntent RecognizerIntent}.</li>

  </ul>



<h3>Miscellaneous API additions</h3>

  <ul>

    <li>LocationManager - Applications can get location change updates via

        Intent</li>

    <li>WebView - Touch start/end/move/cancel DOM event support</li>

    <li>Redesigned {@link android.hardware.SensorManager Sensor Manager

        APIs}</li>

    <li>GLSurfaceView - convenience framework for creating OpenGL

        applications</li>

    <li>Broadcast Intent for app update install succeeded - for smoother app

        upgrade experience</li>

  </ul>





<h3 id="api-diff">API differences report</h3>



<p>For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to 

the previous version, see the <a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API 

Differences Report</a>.</p>





<h2 id="apps">Built-in Applications</h2>



<p>The system image included in the downloadable platform provides these
@@ -268,101 +375,3 @@ through Settings.</p> 
</ul>



<p>For more information about how to develop an application that displays and functions properly on all Android-powered devices, see <a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a>.</p>
 




<h2 id="api">Framework API</h2>



<p>The sections below provide information about the application framework API provided by the Android {@sdkPlatformVersion} platform. </p>





<h3 id="api-level">API level</h3>



<p>The Android {@sdkPlatformVersion} platform delivers an updated version of the framework

API. As with previous versions, the Android {@sdkPlatformVersion} API 

is assigned an integer identifier &mdash; <strong>{@sdkPlatformApiLevel}</strong> &mdash; that is

stored in the system itself. This identifier, called the "API Level", allows the

system to correctly determine whether an application is compatible with

the system, prior to installing the application. </p>



<p>To use APIs introduced in Android {@sdkPlatformVersion} in your application, you need to 

set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <code>&lt;uses-sdk&gt;</code> 

element in your application's manifest. </p>



<p>For more information about how to use API Level, see the <a

href="{@docRoot}guide/appendix/api-levels.html">API Levels</a> document. </p>



<h3 id="api-changes">API changes summary</h3>



<h4>UI framework</h4>

  <ul>

    <li>Framework for easier background/UI thread interaction</li>

    <li>New {@link android.widget.SlidingDrawer SlidingDrawer} widget</li>

    <li>New {@link android.widget.HorizontalScrollView HorizontalScrollview} widget</li>

  </ul>



<h4>AppWidget framework</h4>

  <ul>

    <li>APIs for creating secure home screen {@link android.appwidget

AppWidgets}. For information about how to use AppWidgets, see the Developer's

Guide <a href="{@docRoot}guide/topics/appwidgets/index.html">AppWidgets</a>

documentation. Also see <a

href="http://android-developers.blogspot.com/2009/04/introducing-home-screen-widgets-and.html">

Introducing home screen widgets and the AppWidget

framework</a> on the Android Developer's Blog.</li>

    <li>APIs for populating {@link android.provider.LiveFolders Live Folders}

        with custom content.</li>

  </ul>



<h4>Media framework</h4>

  <ul>

    <li>Raw audio recording and playback APIs</li>

    <li>Interactive MIDI playback engine</li>

    <li>Video recording APIs for developers (3GP format)</li>

    <li>Video and photo sharing Intents</li>

    <li>Media search Intent</li>

  </ul>



<h4>Input Method framework </h4>

   <ul>

    <li>{@link android.inputmethodservice.InputMethodService Input Method

        Service} framework</li>

    <li>Text-prediction engine</li>

    <li>Ability to provide downloadable IMEs to users</li>

  </ul>



<h4>Application-defined hardware requirements</h4>

   <p>Applications can now use a new element in their manifest files, <a

href="{@docRoot}guide/topics/manifest/uses-configuration-element.html"><code>&lt;uses-configuration&gt;</code></a>

 to indicate to the Android system what hardware features

they require in order to function properly. For example, an application might

use the element to specify that it requires a physical keyboard or a particular

navigation device, such as a trackball. Prior to installing the application, the

Android system checks the attributes defined for the

<code>&lt;uses-configuration&gt;</code> element and allows the installation to

continue only if the required hardware is present.</p>



<h4>Speech recognition framework</h4>

    <ul>

    <li>Support for using speech recognition libraries via Intent. See {@link

android.speech.RecognizerIntent RecognizerIntent}.</li>

  </ul>



<h4>Miscellaneous API additions</h4>

  <ul>

    <li>LocationManager - Applications can get location change updates via

        Intent</li>

    <li>WebView - Touch start/end/move/cancel DOM event support</li>

    <li>Redesigned {@link android.hardware.SensorManager Sensor Manager

        APIs}</li>

    <li>GLSurfaceView - convenience framework for creating OpenGL

        applications</li>

    <li>Broadcast Intent for app update install succeeded - for smoother app

        upgrade experience</li>

  </ul>





<h3 id="api-diff">API differences report</h3>



<p>For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to 

the previous version, see the <a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API 

Differences Report</a>.</p>

docs/html/sdk/android-1.6.jd

+156 −149
Original line number Diff line number Diff line
@@ -14,15 +14,21 @@ sdk.platform.deployableDate=October 2009 
<ol>

  <li><a href="#features">Platform Highlights</a></li>

  <li><a href="#relnotes">Revisions</a></li>

  <li><a href="#api-level">API Level</a></li>

  <li><a href="#api">Framework API Changes</a>

  <li><a href="#apps">Built-in Applications</a></li>

  <li><a href="#locs">Locales</a></li>

  <li><a href="#skins">Emulator Skins</a></li>

	<li><a href="#api">Framework API</a>



    </ol>

  </li>

</ol>



<h2>Reference</h2>

<ol>

	<li><a href="#api-level">API level</a></li>

	<li><a href="#api-changes">API changes summary</a></li>

	<li><a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API differences report &raquo;</a> </li>

        </ol></li>

<li><a

href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API

Differences Report &raquo;</a> </li>

</ol>



<h2>See Also</h2>
@@ -89,7 +95,8 @@ function toggleDiv(link) { 
</script>

<style>

.toggleable {

padding: .25em 1em;

  padding: .25em 1em 0em 1em;

  margin-bottom: 0;

}

.toggleme {

  padding: 1em 1em 0 2em;
@@ -186,138 +193,31 @@ available Android-powered devices.</li> 
 </div>

</div>



<h2 id="apps">Built-in Applications</h2>



<p>The system image included in the downloadable platform provides these

built-in applications:</p>



<table style="border:0;padding-bottom:0;margin-bottom:0;">

<tr>

<td style="border:0;padding-bottom:0;margin-bottom:0;">

	<ul>

	<li>Alarm Clock</li>

	<li>Browser</li>

	<li>Calculator</li>

	<li>Camcorder</li>

	<li>Camera</li>

	<li>Contacts</li>

	<li>Custom Locale (developer app)</li>

	<li>Dev Tools (developer app)</li>

	<li>Dialer</li>

	</ul>

</td>

<td style="border:0;padding-bottom:0;margin-bottom:0;padding-left:5em;">

	<ul>

	<li>Email</li>

	<li>Gallery</li>

	<li>Gestures Builder</li>

	<li>IME for Japanese text input</li>

	<li>Messaging</li>

	<li>Music</li>

	<li>Settings</li>

	<li>Spare Parts (developer app)</li>

	</ul>

</td>

</tr>

</table>



<h2 id="locs" style="margin-top:.75em;">Locales</h2>



<p>The system image included in the downloadable platform provides a variety of

built-in locales. In some cases, region-specific strings are available for the

locales. In other cases, a default version of the language is used. The

languages that are available in the Android {@sdkPlatformVersion} system 

image are listed below (with <em>language</em>_<em>country/region</em> 

locale descriptor).</p>



<table style="border:0;margin-bottom:0;padding-bottom:0;">

<tr>

<td style="border:0;padding-bottom:0;margin-bottom:0;">

<ul>

<li>Chinese, PRC (zh_CN)</li>

<li>Chinese, Taiwan (zh_TW)</li>

<li>Czech (cs_CZ)</li>

<li>Dutch, Netherlands (nl_NL)</li>

<li>Dutch, Belgium (nl_BE)</li>

<li>English, US (en_US)</li>

<li>English, Britain (en_GB)</li>

<li>English, Canada (en_CA)</li>

<li>English, Australia (en_AU)</li>

<li>English, New Zealand (en_NZ)</li>

<li>English, Singapore(en_SG)</li>

<li>French, France (fr_FR)</li>

<li>French, Belgium (fr_BE)</li>

</ul>

</td>

<td style="border:0;padding-bottom:0;margin-bottom:0;padding-left:5em;">

<li>French, Canada (fr_CA)</li>

<li>French, Switzerland (fr_CH)</li>

<li>German, Germany (de_DE)</li>

<li>German, Austria (de_AT)</li>

<li>German, Switzerland (de_CH)</li>

<li>German, Liechtenstein (de_LI)</li>

<li>Italian, Italy (it_IT)</li>

<li>Italian, Switzerland (it_CH)</li>

<li>Japanese (ja_JP)</li>

<li>Korean (ko_KR)</li>

<li>Polish (pl_PL)</li>

<li>Russian (ru_RU)</li>

<li>Spanish (es_ES)</li>

</td>

</tr>

</table>



<p>Localized UI strings match the locales that are accessible 

through Settings.</p>



<h2 id="skins">Emulator Skins</h2>



<p>The downloadable platform includes a set of emulator skins that you can 

use for modeling your application in different screen sizes and resolutions. 

The emulator skins are: </p>



<ul>

  <li>

    QVGA (240x320, low density, small screen)

  </li>

  <li>

    HVGA (320x480, medium density, normal screen)

  </li>

  <li>

    WVGA800 (480x800, high density, normal screen)

  </li>

  <li>

    WVGA854 (480x854 high density, normal screen)

  </li>

</ul>



<p>For more information about how to develop an application that displays and functions properly on all Android-powered devices, see <a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a>.</p>



<h2 id="api-level">API Level</h2>



<h2 id="api">Framework API</h2>



<p>The sections below provide information about the application framework API provided by the Android {@sdkPlatformVersion} platform. </p>





<h3 id="api-level">API level</h3>



<p>The Android {@sdkPlatformVersion} platform delivers an updated version of the framework

API. As with previous versions, the Android {@sdkPlatformVersion} API 

is assigned an integer identifier &mdash; <strong>{@sdkPlatformApiLevel}</strong> &mdash; that is

<p>The Android {@sdkPlatformVersion} platform delivers an updated version of

the framework API. The Android {@sdkPlatformVersion} API

is assigned an integer identifier &mdash;

<strong>{@sdkPlatformApiLevel}</strong> &mdash; that is

stored in the system itself. This identifier, called the "API Level", allows the

system to correctly determine whether an application is compatible with

the system, prior to installing the application. </p>



<p>To use APIs introduced in Android {@sdkPlatformVersion} in your application, you need to 

set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <code>&lt;uses-sdk&gt;</code> 

<p>To use APIs introduced in Android {@sdkPlatformVersion} in your

application, you need to set the proper value, "{@sdkPlatformApiLevel}", in the

<code>android:minSdkVersion</code> attributes of the <code>&lt;uses-sdk&gt;</code>

element in your application's manifest. </p>



<p>For more information about how to use API Level, see the <a

href="{@docRoot}guide/appendix/api-levels.html">API Levels</a> document. </p>



<h3 id="api-changes">API changes summary</h3>



<h4 id="UIFramework">UI framework</h4>

<h2 id="api">Framework API Changes</h2>



<p>The sections below provide information about the application framework API provided by the Android {@sdkPlatformVersion} platform. </p>



<h3 id="UIFramework">UI framework</h3>

    <ul>

      <li>New classes in {@link android.view.animation}

      to control the behavior of animations:
@@ -342,7 +242,7 @@ set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <code>& 
element in your application's manifest. </p>

    </ul>



<h4>Search framework</h4>

<h3>Search framework</h3>

  <ul>

    <li>Applications can now expose relevant content to users as search

suggestions in the Quick Search Box, a new device-wide search capability that is
@@ -352,7 +252,7 @@ attributes to the searchable metadata file. For complete information, see the 
    </li>

  </ul>



<h4>Accessibility framework</h4>

<h3>Accessibility framework</h3>

  <ul>

    <li>New {@link android.view.accessibility android.accessibility} package

that includes classes for capturing accessibility events and forwarding them to
@@ -362,38 +262,38 @@ that lets your application track user events and provide visual, audible, or 
haptic feedback to the user. </li>

  </ul>



<h4>Gesture Input</h4>

<h3>Gesture input</h3>

  <ul>

    <li>New {@link android.gesture gesture} API for creating, recognizing,

loading, and saving gestures.</li>

  </ul>



<h4>Text-to-speech</h4>

<h3>Text-to-speech</h3>

  <ul>

    <li>New {@link android.speech.tts android.speech.tts} package provides

classes for synthesizing speech from text, for immediate playback or to create a

sound file.</li>

  </ul>



<h4>Graphics</h4>

<h3>Graphics</h3>

  <ul>

    <li>Classes in {@link android.graphics android.graphics} now support scaling

for different screen densities.</li>

  </ul>



<h4>Telephony</h4>

<h3>Telephony</h3>

  <ul>

    <li>New {@link android.telephony.SmsManager SmsManager} and other classes

for sending and receiving SMS messages.</li>

  </ul>



<h4>Utilities</h4>

<h3>Utilities</h3>

  <ul>

    <li>New {@link android.util.DisplayMetrics DisplayMetrics} fields for

determining the density of the current device screen.</li>

  </ul>



<h4 id="AndroidManifest">Android Manifest elements</h4>

<h3 id="AndroidManifest">Android Manifest elements</h3>



    <ul>

      <li>New <a href="{@docRoot}guide/topics/manifest/supports-screens-element.html">{@code
@@ -463,7 +363,7 @@ determining the density of the current device screen.</li> 
      </li>

    </ul>



<h4>New Permissions</h4>

<h3>New permissions</h3>



    <ul>

      <li>{@link android.Manifest.permission#CHANGE_WIFI_MULTICAST_STATE
@@ -498,3 +398,110 @@ determining the density of the current device screen.</li> 
<p>For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to 

the previous version, see the <a href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API 

Differences Report</a>.</p>



<h2 id="apps">Built-in Applications</h2>



<p>The system image included in the downloadable platform provides these

built-in applications:</p>



<table style="border:0;padding-bottom:0;margin-bottom:0;">

<tr>

<td style="border:0;padding-bottom:0;margin-bottom:0;">

	<ul>

	<li>Alarm Clock</li>

	<li>Browser</li>

	<li>Calculator</li>

	<li>Camcorder</li>

	<li>Camera</li>

	<li>Contacts</li>

	<li>Custom Locale (developer app)</li>

	<li>Dev Tools (developer app)</li>

	<li>Dialer</li>

	</ul>

</td>

<td style="border:0;padding-bottom:0;margin-bottom:0;padding-left:5em;">

	<ul>

	<li>Email</li>

	<li>Gallery</li>

	<li>Gestures Builder</li>

	<li>IME for Japanese text input</li>

	<li>Messaging</li>

	<li>Music</li>

	<li>Settings</li>

	<li>Spare Parts (developer app)</li>

	</ul>

</td>

</tr>

</table>



<h2 id="locs" style="margin-top:.75em;">Locales</h2>



<p>The system image included in the downloadable platform provides a variety of

built-in locales. In some cases, region-specific strings are available for the

locales. In other cases, a default version of the language is used. The

languages that are available in the Android {@sdkPlatformVersion} system 

image are listed below (with <em>language</em>_<em>country/region</em> 

locale descriptor).</p>



<table style="border:0;margin-bottom:0;padding-bottom:0;">

<tr>

<td style="border:0;padding-bottom:0;margin-bottom:0;">

<ul>

<li>Chinese, PRC (zh_CN)</li>

<li>Chinese, Taiwan (zh_TW)</li>

<li>Czech (cs_CZ)</li>

<li>Dutch, Netherlands (nl_NL)</li>

<li>Dutch, Belgium (nl_BE)</li>

<li>English, US (en_US)</li>

<li>English, Britain (en_GB)</li>

<li>English, Canada (en_CA)</li>

<li>English, Australia (en_AU)</li>

<li>English, New Zealand (en_NZ)</li>

<li>English, Singapore(en_SG)</li>

<li>French, France (fr_FR)</li>

<li>French, Belgium (fr_BE)</li>

</ul>

</td>

<td style="border:0;padding-bottom:0;margin-bottom:0;padding-left:5em;">

<li>French, Canada (fr_CA)</li>

<li>French, Switzerland (fr_CH)</li>

<li>German, Germany (de_DE)</li>

<li>German, Austria (de_AT)</li>

<li>German, Switzerland (de_CH)</li>

<li>German, Liechtenstein (de_LI)</li>

<li>Italian, Italy (it_IT)</li>

<li>Italian, Switzerland (it_CH)</li>

<li>Japanese (ja_JP)</li>

<li>Korean (ko_KR)</li>

<li>Polish (pl_PL)</li>

<li>Russian (ru_RU)</li>

<li>Spanish (es_ES)</li>

</td>

</tr>

</table>



<p>Localized UI strings match the locales that are accessible 

through Settings.</p>



<h2 id="skins">Emulator Skins</h2>



<p>The downloadable platform includes a set of emulator skins that you can 

use for modeling your application in different screen sizes and resolutions. 

The emulator skins are: </p>



<ul>

  <li>

    QVGA (240x320, low density, small screen)

  </li>

  <li>

    HVGA (320x480, medium density, normal screen)

  </li>

  <li>

    WVGA800 (480x800, high density, normal screen)

  </li>

  <li>

    WVGA854 (480x854 high density, normal screen)

  </li>

</ul>



<p>For more information about how to develop an application that displays and functions properly on all Android-powered devices, see <a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a>.</p>

docs/html/sdk/android-2.1.jd

+121 −122

File changed.

Preview size limit exceeded, changes collapsed.