diff options
| -rw-r--r-- | docs/html/guide/appendix/api-levels.jd | 4 | ||||
| -rw-r--r-- | docs/html/sdk/android-2.3.4.jd | 379 | ||||
| -rw-r--r-- | docs/html/sdk/android-3.0-highlights.jd | 6 | ||||
| -rw-r--r-- | docs/html/sdk/android-3.0.jd | 2 | ||||
| -rw-r--r-- | docs/html/sdk/android-3.1-highlights.jd | 380 | ||||
| -rw-r--r-- | docs/html/sdk/android-3.1.jd | 1053 | ||||
| -rw-r--r-- | docs/html/sdk/images/3.1/controls.png | bin | 0 -> 103866 bytes | |||
| -rw-r--r-- | docs/html/sdk/images/3.1/home.png | bin | 0 -> 142023 bytes | |||
| -rw-r--r-- | docs/html/sdk/images/3.1/home_full.png | bin | 0 -> 624953 bytes | |||
| -rw-r--r-- | docs/html/sdk/images/3.1/resizeable.png | bin | 0 -> 64928 bytes | |||
| -rw-r--r-- | docs/html/sdk/images/3.1/tasks.png | bin | 0 -> 136355 bytes | |||
| -rw-r--r-- | docs/html/sdk/sdk_toc.cs | 44 | ||||
| -rw-r--r-- | docs/html/sdk/tools-notes.jd | 2 |
13 files changed, 1850 insertions, 20 deletions
diff --git a/docs/html/guide/appendix/api-levels.jd b/docs/html/guide/appendix/api-levels.jd index 013cc94..5c18a83 100644 --- a/docs/html/guide/appendix/api-levels.jd +++ b/docs/html/guide/appendix/api-levels.jd @@ -83,8 +83,10 @@ Android platform.</p> <table> <tr><th>Platform Version</th><th>API Level</th></tr> + <tr><td>Android 3.1</td><td>12</td></tr> <tr><td>Android 3.0</td><td>11</td></tr> - <tr><td>Android 2.3.3</td><td>10</td></tr> + <tr><td>Android 2.3.4</td><td rowspan="2">10</td></tr> + <tr><td>Android 2.3.3</td></tr> <tr><td>Android 2.3</td><td>9</td></tr> <tr><td>Android 2.2</td><td>8</td></tr> <tr><td>Android 2.1</td><td>7</td></tr> diff --git a/docs/html/sdk/android-2.3.4.jd b/docs/html/sdk/android-2.3.4.jd new file mode 100644 index 0000000..e5765d3 --- /dev/null +++ b/docs/html/sdk/android-2.3.4.jd @@ -0,0 +1,379 @@ +page.title=Android 2.3.4 Platform +sdk.platform.version=2.3.4 +sdk.platform.apiLevel=10 + + +@jd:body + +<div id="qv-wrapper"> +<div id="qv"> + +<h2>In this document</h2> +<ol> + <li><a href="#relnotes">Revisions</a></li> + <li><a href="#api">API Overview</a></li> + <li><a href="#openaccessory">Open Accessory Library</a></li> + <li><a href="#api-level">API Level</a></li> + <li><a href="#apps">Built-in Applications</a></li> + <li><a href="#locs">Locales</a></li> + <li><a href="#skins">Emulator Skins</a></li> +</ol> + +<h2>Reference</h2> +<ol> +<li><a +href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API +Differences Report »</a> </li> +</ol> + +<h2>See Also</h2> +<ol> + <li><a href="{@docRoot}sdk/adding-components.html">Adding SDK Components</a></li> +</ol> + +</div> +</div> + +<p> +<em>API Level:</em> <strong>{@sdkPlatformApiLevel}</strong></p> + +<p>Android 2.3.4 is a maintenance release that adds several bug fixes and patches +to the Android 2.3 platform, without any API changes from Android 2.3.3. Additionally, +Android 2.3.4 brings support for the Open Accessory API to mobile devices, +through the optional <a href="#usb">Open Accessory Library</a>. </p> + +<p>For developers, the Android {@sdkPlatformVersion} platform and the Open +Accessory Library are available together in the latest version of the Google +APIs Add-On, a downloadable component for the Android SDK.</p> + +<p>To get started developing or testing against Android {@sdkPlatformVersion}, +use the Android SDK Manager to download the latest version of the Google APIs +Add-On into your SDK. For more information, see <a +href="{@docRoot}sdk/adding-components.html">Adding SDK Components</a>. If you +are new to Android, <a href="{@docRoot}sdk/index.html">download the SDK Starter +Package</a> first.</p> + +<p>For a high-level introduction to Android 2.3, see the <a +href="{@docRoot}sdk/android-2.3-highlights.html">Platform Highlights</a>.</p> + + +<h2 id="relnotes">Revisions</h2> + +<p>The sections below provide notes about successive releases of +the Android {@sdkPlatformVersion} platform component for the Android SDK, as denoted by +revision number. To determine what revision(s) of the Android +{@sdkPlatformVersion} platforms are installed in your SDK environment, refer to +the "Installed Packages" listing in the Android SDK and AVD Manager.</p> + +<script type="text/javascript"> +function toggleDiv(link) { + var toggleable = $(link).parent(); + if (toggleable.hasClass("closed")) { + //$(".toggleme", toggleable).slideDown("fast"); + toggleable.removeClass("closed"); + toggleable.addClass("open"); + $(".toggle-img", toggleable).attr("title", "hide").attr("src", (toRoot + "assets/images/triangle-opened.png")); + } else { + //$(".toggleme", toggleable).slideUp("fast"); + toggleable.removeClass("open"); + toggleable.addClass("closed"); + $(".toggle-img", toggleable).attr("title", "show").attr("src", (toRoot + "assets/images/triangle-closed.png")); + } + return false; +} +</script> +<style> +.toggleable { + padding: .25em 1em 0em 1em; + margin-bottom: 0; +} +.toggleme { + padding: 1em 1em 0 2em; + line-height:1em; +} +.toggleable a { + text-decoration:none; +} +.toggleme a { + text-decoration:underline; +} +.toggleable.closed .toggleme { + display:none; +} +#jd-content .toggle-img { + margin:0; +} +</style> + +<div class="toggleable opened"> + <a href="#" onclick="return toggleDiv(this)"> + <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-img" height="9px" width="9px" /> + Android {@sdkPlatformVersion}, Revision 1</a> <em>(May 2011)</em></a> + <div class="toggleme"> +<dl> +<dt>Dependencies:</dt> +<dd> +<p>Requires SDK Tools r11 or higher.</p> +</dd> + +</dl> + </div> +</div> + + +<h2 id="api">API Overview</h2> + +<p>Android 2.3.4 provides the same framework API to applications as Android 2.3.3 +(API level 10). For a summary of the API, see the +<a href="{@docRoot}sdk/android-2.3.3.html">Android 2.3.3 version notes</a>.</p> + + +<h2 id="openaccessory">Open Accessory Library</h3> + +<p><em>Open Accessory</em> is a new capability for integrating +connected peripherals with applications running on the platform. The capability +is based on a USB (Universal Serial Bus) stack built into the platform and an +API exposed to applications. Peripherals that attach to Android-powered devices +as accessories connect as USB hosts. </p> + +<p>Open Accessory is introduced in <a +href="{@docRoot}sdk/android-3.1.html#usb">Android 3.1</a> (API level 12), but is +made available to devices running Android 2.3.4 by means of an optional external +library, the Open Accessory Library. The library exposes a framework API that +lets applications discover, communicate with, and manage a variety of device +types connected over USB. It also provides the implementation of the API against +parts of the Android platform that are not directly exposed to applications in +Android 2.3.4.</p> + +<p>The Open Accessory Library is optional on any given device. Device +manufacturers may choose whether to include the Open Accessory Library in their +products or exclude it. The library is forward-compatible with Android 3.1, so +applications developed against Android 2.3.4 will run properly on devices +running Android 3.1, if those devices support USB accessories. </p> + +<p>The API provided by the Open Accessory Library is based on the Open Accessory +API provided in Android 3.1. In most areas, you can use the same techniques and +APIs. However, developing for the Open Accessory Library on Android 2.3.4 differs +from the standard USB API in these ways: + +<ul> +<li>Obtaining a {@link android.hardware.usb.UsbManager} object — To obtain +a {@link android.hardware.usb.UsbManager} object when using the add-on library, +use the helper method <code>getInstance()</code> rather than {@link +android.content.Context#getSystemService(java.lang.String) getSystemService()} +For example: + +<pre>UsbManager manager = UsbManager.getInstance(this);</pre></li> + +<li>Obtaining a {@link android.hardware.usb.UsbAccessory} from a filtered intent +— When you filter for a connected device or accessory with an intent +filter, the {@link android.hardware.usb.UsbAccessory} object is contained +inside the intent that is passed to your application. If you are using the +add-on library, you can get the {@link android.hardware.usb.UsbAccessory} object +in the following manner: + +<pre>UsbAccessory accessory = UsbManager.getAccessory(intent)</pre></li> + +<li>No USB host support — Android 2.3.4 and the Open Accessory Library do +not support USB host mode (for example, through {@link +android.hardware.usb.UsbDevice}), although USB host mode is supported in Android +3.1. An Android-powered device running Android 2.3.4 can not function as a USB +host. The library enables the Android-powered device to function as +a peripheral only, with the connected accessory functioning as USB host +(through {@link android.hardware.usb.UsbAccessory}).</li> +</ul> + +<p>To develop apps using the Open Accessory Library, you need:</p> + +<ul> +<li>The latest version of the Android SDK tools</li> +<li>The latest version of the Google APIs add-on, which includes the library +itself (for linking)</li> +<li>An actual hardware device running Android 2.3.4 (or Android 3.1) with USB +accessories support, for runtime testing against connected devices</li> +</ul> + +<p>For a full discussion of how to develop applications that interact with USB +accessories, please see the related <a +href="{@docRoot}guide/topics/usb/index.html">developer documentation</a>.</p> + +<p>Additionally, developers can request filtering on Android Market, such that +their applications are not available to users whose devices do not provide the +appropriate accessory support. To request filtering, add the element below +to the application manifest:</p> + +<pre><uses-feature + android:name="android.hardware.usb.accessory" + android:required="true"></pre> + + +<h2 id="api-level">API Level</h2> + +<p>The Android 2.3.4 platform does <em>not</em> increment the API level — +it uses the same API level as Android 2.3.3, API level 10. + +<p>To use APIs introduced in API level 10 in your application, +you need compile the application against the Android library that is provided in +the latest version of the Google APIs Add-On, which also includes the Open +Accessory Library.</p> + +<p>Depending on your needs, you might +also need to add an <code>android:minSdkVersion="{@sdkPlatformApiLevel}"</code> +attribute to the <code><uses-sdk></code> element in the application's +manifest. If your application is designed to run only on Android 2.3.3 and higher, +declaring the attribute prevents the application from being installed on earlier +versions of the platform.</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="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>Browser</li> +<li>Calculator</li> +<li>Camera</li> +<li>Clock</li> +<li>Contacts</li> +<li>Cusom Locale</li> +<li>Dev Tools</li> +<li>Downloads</li> +<li>Email</li> +</ul> +</td> +<td style="border:0;padding-bottom:0;margin-bottom:0;padding-left:5em;"> +<ul> +<li>Gallery</li> +<li>IMEs for Japanese, Chinese, and Latin text input</li> +<li>Messaging</li> +<li>Music</li> +<li>Phone</li> +<li>Search</li> +<li>Settings</li> +<li>Spare Parts (developer app)</li> +<li>Speech Recorder</li> +</ul> +</td> +</tr> +</table> + + +<h2 id="locs" style="margin-top:.75em;">Locales</h2> + +<p>The system image included in the downloadable SDK 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;padding-bottom:0;margin-bottom:0;"> +<tr> +<td style="border:0;padding-bottom:0;margin-bottom:0;"> +<ul> +<li>Arabic, Egypt (ar_EG)</li> +<li>Arabic, Israel (ar_IL)</li> +<li>Bulgarian, Bulgaria (bg_BG)</li> +<li>Catalan, Spain (ca_ES)</li> +<li>Czech, Czech Republic (cs_CZ)</li> +<li>Danish, Denmark(da_DK)</li> +<li>German, Austria (de_AT)</li> +<li>German, Switzerland (de_CH)</li> +<li>German, Germany (de_DE)</li> +<li>German, Liechtenstein (de_LI)</li> +<li>Greek, Greece (el_GR)</li> +<li>English, Australia (en_AU)</li> +<li>English, Canada (en_CA)</li> +<li>English, Britain (en_GB)</li> +<li>English, Ireland (en_IE)</li> +<li>English, India (en_IN)</li> +<li>English, New Zealand (en_NZ)</li> +<li>English, Singapore(en_SG)</li> +<li>English, US (en_US)</li> +<li>English, Zimbabwe (en_ZA)</li> +<li>Spanish (es_ES)</li> +<li>Spanish, US (es_US)</li> +<li>Finnish, Finland (fi_FI)</li> +<li>French, Belgium (fr_BE)</li> +<li>French, Canada (fr_CA)</li> +<li>French, Switzerland (fr_CH)</li> +<li>French, France (fr_FR)</li> +<li>Hebrew, Israel (he_IL)</li> +<li>Hindi, India (hi_IN)</li> +</ul> +</td> +<td style="border:0;padding-bottom:0;margin-bottom:0;padding-left:5em;"> +<li>Croatian, Croatia (hr_HR)</li> +<li>Hungarian, Hungary (hu_HU)</li> +<li>Indonesian, Indonesia (id_ID)</li> +<li>Italian, Switzerland (it_CH)</li> +<li>Italian, Italy (it_IT)</li> +<li>Japanese (ja_JP)</li> +<li>Korean (ko_KR)</li> +<li>Lithuanian, Lithuania (lt_LT)</li> +<li>Latvian, Latvia (lv_LV)</li> +<li>Norwegian-Bokmol, Norway(nb_NO)</li> +<li>Dutch, Belgium (nl_BE)</li> +<li>Dutch, Netherlands (nl_NL)</li> +<li>Polish (pl_PL)</li> +<li>Portuguese, Brazil (pt_BR)</li> +<li>Portuguese, Portugal (pt_PT)</li> +<li>Romanian, Romania (ro_RO)</li> +<li>Russian (ru_RU)</li></li> +<li>Slovak, Slovakia (sk_SK)</li> +<li>Slovenian, Slovenia (sl_SI)</li> +<li>Serbian (sr_RS)</li> +<li>Swedish, Sweden (sv_SE)</li> +<li>Thai, Thailand (th_TH)</li> +<li>Tagalog, Philippines (tl_PH)</li> +<li>Turkish, Turkey (tr_TR)</li> +<li>Ukrainian, Ukraine (uk_UA)</li> +<li>Vietnamese, Vietnam (vi_VN)</li> +<li>Chinese, PRC (zh_CN)</li> +<li>Chinese, Taiwan (zh_TW)</li> +</td> +</tr> +</table> + +<p class="note"><strong>Note:</strong> The Android platform may support more +locales than are included in the SDK system image. All of the supported locales +are available in the <a href="http://source.android.com/">Android Open Source +Project</a>.</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> + WQVGA400 (240x400, low density, normal screen) + </li> + <li> + WQVGA432 (240x432, low density, normal 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> diff --git a/docs/html/sdk/android-3.0-highlights.jd b/docs/html/sdk/android-3.0-highlights.jd index d4fd002..33897de 100644 --- a/docs/html/sdk/android-3.0-highlights.jd +++ b/docs/html/sdk/android-3.0-highlights.jd @@ -39,10 +39,6 @@ page.title=Android 3.0 Platform Highlights </style> - - - - <p>Welcome to Android 3.0!</p> <p>The Android 3.0 platform introduces many new and exciting features for users and developers. @@ -265,5 +261,3 @@ allowscriptaccess="always" allowfullscreen="true" width="278" height="180"></emb href="{@docRoot}sdk/android-3.0.html">Android 3.0 Platform</a> document.</p> <p>For a video overview of platform features, see the Android 3.0 Sneak Peek. </p> - - diff --git a/docs/html/sdk/android-3.0.jd b/docs/html/sdk/android-3.0.jd index a81be20..d73bd63 100644 --- a/docs/html/sdk/android-3.0.jd +++ b/docs/html/sdk/android-3.0.jd @@ -559,7 +559,7 @@ menu.</p></li> <p>Provides a search box that you can configure to deliver search queries to a specified activity and display search suggestions (in the same manner as the traditional search dialog). This widget is particularly useful for offering a search widget in the Action Bar. For more information, -see <a href="{@docRoot}guide/topics/search/search-dialog.html">Creating a Search Interface</p>.</li> +see <a href="{@docRoot}guide/topics/search/search-dialog.html">Creating a Search Interface.</p></li> <li>{@link android.widget.StackView} <p>A view that displays its children in a 3D stack and allows users to swipe through diff --git a/docs/html/sdk/android-3.1-highlights.jd b/docs/html/sdk/android-3.1-highlights.jd new file mode 100644 index 0000000..3d132a3 --- /dev/null +++ b/docs/html/sdk/android-3.1-highlights.jd @@ -0,0 +1,380 @@ +page.title=Android 3.1 Platform Highlights + +@jd:body + + +<style type="text/css"> +#jd-content { + max-width:1200px; +} +#jd-content div.screenshot { + float:left; + clear:left; + padding:15px 30px 15px 0; +} +#jd-content div.video { + float:right; + padding:0 60px 40px; + margin-top:-15px; +} +#jd-content table.columns { + margin:0 0 1em 0; +} +#jd-content table.columns td { + padding:0; +} +#jd-content table.columns td+td { + padding:0 2em; +} +#jd-content table.columns td img { + margin:0; +} +#jd-content table.columns td+td>*:first-child { + margin-top:-2em; +} +.green { + color:#8db529; + font-weight:bold; +} +</style> + +<p>Welcome to Android 3.1!</p> + +<p>Android 3.1 is an incremental platform release that refines many of the +features introduced in Android 3.0. It builds on the same tablet-optimized UI +and features offered in Android 3.0 and adds several new capabilities for +users and developers. This document provides an overview of the new features and +technologies introduced in Android 3.1. For a more detailed look at new +developer APIs, see the <a href="{@docRoot}sdk/android-3.1.html">API +Overview</a> document.</p> + +<p>For a high-level introduction to Android 3.0, please see the <a +href="{@docRoot}sdk/android-3.0-highlights.html">Android 3.0 Platform +Highlights</a>.</p> + +<ul> + <li><a href="#UserFeatures">New User Features</a></li> + <li><a href="#DeveloperApis">New Developer Features</a></li> +</ul> + +<h2 id="UserFeatures" style="clear:right">New User Features</h2> + +<div style="padding-top:0em;"> +<div style="margin-right:1em;margin-left:1em;float:right;padding-top:2em;"><a href="images/3.1/home_full.png" target="_android"><img src="images/3.1/home.png" alt="" height="280" /></a> +<div style="padding-left:1.25em;padding-bottom:1.25em;width:450px;font-size:.9em"><strong>Figure 1.</strong> An Android 3.1 Home screen.</div> +</div> + +<h3>UI refinements</h3> + +<p>The Android 3.1 platform adds a variety of refinements to make the user +interface more intuitive and more efficient to use.</p> + +<p>UI transitions are improved throughout the system and across the standard +apps. The Launcher animation is optimized for faster, smoother transition to and +from the Apps list. Adjustments in color, positioning, and text make UI elements +easier to see, understand, and use. Accessibility is improved with consistent +audible feedback throughout the UI and a new setting to let users customize the +touch-hold interval to meet their needs.</p> + +<p>Navigation to and from the five home screens is now easier — touching +the Home button in the system bar now takes you to the home screen most recently +used. Settings offers an improved view of internal storage, +showing the storage used by a larger set of file types. </p> + +<h3 id="accessories">Connectivity for USB accessories</h3> + +<p>Android 3.1 adds broad platform support for a variety of USB-connected +peripherals and accessories. Users can attach many types of input devices +(keyboards, mice, game controllers) and digital cameras. Applications can build +on the platform’s USB support to extend connectivity to almost any type of USB +device.</p> + +<p>The platform also adds new support for USB accessories — external +hardware devices designed to attach to Android-powered devices as USB hosts. When an +accessory is attached, the framework will look for a corresponding application +and offer to launch it for the user. The accessory can also present a URL +to the user, for downloading an appropriate application if one is not already +installed. Users can interact with the application to control powered accessories such +as robotics controllers; docking stations; diagnostic and musical equipment; +kiosks; card readers; and much more.</p> + +<p>The platform’s USB capabilities rely on components in device hardware, so +support for USB on specific devices may vary and is determined by device +manufacturers.</p> + +<div style="padding-top:0em;"> +<div style="margin-right:.8em;float:left;width:200px;"><img src="{@docRoot}sdk/images/3.1/tasks.png" alt="" /> +<div style="padding-left:1em;padding-bottom:1em;xwidth:auto;font-size:.9em"><strong>Figure 2.</strong> The Recent Apps menu is now expandable and scrollable.</div> +</div> + +<h3 id="recentapps">Expanded Recent Apps list</h3> + +<p>For improved multitasking and instant visual access to a much larger number +of apps, the Recent Apps list is now expandable. Users can now scroll the list +of recent apps vertically to see thumbnail images all of the tasks in progress +and recently used apps, then touch a thumbnail to jump back into that task.</p> + +<h3 id="resizewidgets">Resizeable Home screen widgets</h3> + +<p>For more flexible Home screen customization, users can now resize their Home +screen widgets using drag bars provided by the system. Users can expand widgets +both horizontally and/or vertically to include more content, where supported by +each widget.</p> + + +<h3 id="keyboards">Support for external keyboards +and pointing devices</h3> + +<p>Users can now attach almost any type of external keyboard or mouse to their +Android-powered devices, to create a familiar environment and work more +efficiently. One or more input devices can be attached to the system simultaneously +over USB and/or Bluetooth HID, in any combination. No special configuration or +driver is needed, in most cases. When multiple devices are connected, users can +conveniently manage the active keyboard and IME using the keyboard settings that +are available from the System bar.</p> + +<p>For pointing devices, the platform supports most types of mouse with a single +button and optionally a scroll wheel, as well as similar devices such as +trackballs. When these are connected, users can interact with the UI using +point, select, drag, scroll, hover, and other standard actions.</p> + +<h3 id="joysticks">Support for joysticks and gamepads</h3> + +<p>To make the platform even better for gaming, Android 3.1 adds support for +most PC joysticks and gamepads that are connected over USB or Bluetooth HID.</p> + +<p>For example, users can connect Sony Playstation™ 3 and XBox 360™ game +controllers over USB (but not Bluetooth), Logitech Dual Action™ gamepads and +flight sticks, or a car racing controller. Game controllers that use proprietary +networking or pairing are not supported by default, but in general, the platform +supports most PC-connectible joysticks and gamepads.</p> + +<h3 id="wifi">Robust Wi-Fi networking</h3> + +<p>Android 3.1 adds robust Wi-Fi features, to make sure that users and their +apps can take full advantage of higher-speed Wi-Fi access at home, at work, and +while away.</p> + +<p>A new high-performance Wi-Fi lock lets applications maintain +high-performance Wi-Fi connections even when the device screen is off. Users can +take advantage of this to play continuous streamed music, video, and voice +services for long periods, even when the device is otherwise idle and the screen +is off. </p> + +<p>Users can now configure an HTTP proxy for each individual Wi-Fi access +point, by touch-hold of the access point in Settings. The browser uses the HTTP +proxy when communicating with the network over the access point and other apps +may also choose to do so. The platform also provides backup and restore of the +user-defined IP and proxy settings.</p> +<p>The platform adds support for Preferred Network Offload (PNO), a background +scanning capability that conserves battery power savings in cases where Wi-Fi +needs to be available continuously for long periods of time.</p> + +<h3 id="apps">Updated set of standard apps</h3> + +<p>The Android 3.1 platform includes an updated set of standard applications +that are optimized for use on larger screen devices. The sections below +highlight some of the new features.</p> + +<div style="padding-top:0em;"> +<div style="margin-right:1em;float:right;margin-left:1em;margin-top:1.5em;margin-bottom:0;padding-bottom:0;"><img src="{@docRoot}sdk/images/3.1/controls.png" alt="" height="280px" /> +<div style="padding-left:1.25em;padding-bottom:1.25em;margin-top:0;padding-top:0;font-size:.9em"><strong>Figure 3.</strong> Quick Controls menu in the Browser.</div> +</div> +</div> + +<p><strong>Browser</strong></p> + +<p>The Browser app includes a variety of new features and UI improvements that +make viewing web content simpler, faster, and more convenient.</p> + +<p>The Quick Controls UI, accessible from Browser Settings, is extended and +redesigned. Users can now use the controls to view thumbnails of open tabs and +close the active tab, as well as access the overflow menu for instant access to +Settings and other controls.</p> + +<p>To ensure a consistent viewing experience, the Browser extends it's support +for popular web standards such as CSS 3D, animations, and CSS fixed +positioning to all sites, mobile or desktop. It also adds support for embedded +playback of HTML5 video content. To make it easier to manage favorite +content, users can now save a web page locally for offline viewing, including +all styling and images. For convenience when visiting Google sites, an improved +auto-login UI lets users sign in quickly and manage access when multiple users +are sharing a device.</p> + +<p>For best performance, the Browser adds support for plugins that use hardware +accelerated rendering. Page zoom performance is also dramatically improved, +making it faster to navigate and view web pages.</p> + +<p><strong>Gallery</strong></p> + +<p>The Gallery app now supports Picture Transfer Protocol (PTP), so that users +can connect their cameras over USB and import their pictures to Gallery with a +single touch. The app also copies the pictures to local storage and provides an +indicator to let users see how much space is available.</p> + +<div style="padding-top:0em;"> +<div style="margin-right:1em;float:left;margin-left:0em;"><img src="{@docRoot}sdk/images/3.1/resizeable.png" alt="" width="170" target="_android" style="margin-bottom:0;" /> +<div style="padding-left:1.4em;padding-bottom:1em;width:180px;font-size:.9em"><strong>Figure +4.</strong> Home screen widgets can now be resized.</div></div> + +<p><strong>Calendar</strong></p> + +<p>Calendar grids are larger, for better readability and more accurate +touch-targeting. Additionally, users can create a larger viewing area for grids +by hiding the calendar list controls. Controls in the date picker are +redesigned, making them easier to see and use.</li> +</ul> + +<p><strong>Contacts</strong></p> + +<p>The Contacts app now lets you locate contacts more easily using full text +search. Search returns matching results from all fields that are stored for a +contact. +</p> + +<p><strong>Email</strong></p> + +<p>When replying or forwarding an HTML message, The Email app now sends both +plain text and HTML bodies as a multi-part mime message. This ensures that the +message will be formatted properly for all recipients. Folder prefixes for IMAP +accounts are now easier to define and manage. To conserve battery power and +minimize cell data usage, the application now prefetches email from the server +only when the device is connected to a Wi-Fi access point. </p> + +<p>An updated Home screen widget give users quick access to more email. Users +can touch Email icon at the top of the widget to cycle through labels such as +Inbox, Unread, and Starred. The widget itself is now resizable, both +horizontally and vertically.</p> + +<h3 id="enterprise">Enterprise support</h3> + +<p>Users can now configure an HTTP proxy for each connected Wi-Fi access point. +This lets administrators work with users to set a proxy hostname, port, and any +bypass subdomains. This proxy configuration is automatically used by the Browser +when the Wi-Fi access point is connected, and may optionally be used by other +apps. The proxy and IP configuration is now backed up and restored across system +updates and resets.</p> + +<p>To meet the needs of tablet users, the platform now allows a "encrypted +storage card" device policy to be accepted on devices with emulated storage +cards and encrypted primary storage.</p> + + +<h2 id="DeveloperApis" style="clear:both">New Developer Features</h2> + +<p>The Android 3.1 platform adds refinements and new capabilities that +developers can build on, to create powerful and engaging application experiences +on tablets and other large-screen devices. </p> + +<h3 id="accessory">Open Accessory API for rich interaction with +peripherals</h3> + +<p>Android 3.1 introduces a new API for integrating hardware accessories with +applications running on the platform. The API provides a way to interact across +a wide range of peripherals, from robotics controllers to musical equipment, +exercise bicycles, and more.</p> + +<p>The API is based on a new USB (Universal Serial Bus) stack and services +that are built into the platform. The platform provides services for discovering +and identifying connected hardware, as well as for notifying interested +applications that the hardware is available.</p> + +<p>When a user plugs in a USB accessory, the platform receives +identifying information such as product name, accessory type, manufacturer, and +version. The platform sets up communication with the accessory and uses its +information to notify and launch a targeted app, if one is available. Optionally, +an accessory can provide a URL that lets users find and download an +app that works with the accessory. These discovery features make +first-time setup easier for the user and ensure that an appropriate application +is available for interacting with the connected hardware. </p> + +<p>For application developers and accessory manufacturers, accessory mode offers +many new ways to engage users and build powerful interaction experiences with +connected hardware.</p> + +<p>To learn more about how to develop applications that interact with +accessories, see the <a href="{@docRoot}guide/topics/usb/accessory.html">USB +Accessory</a> documentation.</p> + +<h3 id="host">USB host API</h3> + +<p>Android 3.1 provides built-in platform support for USB host mode and exposes +an API that lets applications manage connected peripherals. On devices that +support host mode, applications can use the API to identify and communicate with +connected devices such as audio devices. input devices, communications devices, +hubs, cameras, and more.</p> + +<p>To learn more about how to develop applications that interact with +USB devices, see the <a href="{@docRoot}guide/topics/usb/host.html">USB +Host</a> documentation.</p> + +<h3 id="inputdevices">Input from mice, joysticks, and gamepads</h3> + +<p>Android 3.1 extends the input event system to support a variety of new input +sources and motion events, across all views and windows. Developers can build on +these capabilities to let users interact with their applications using mice, +trackballs, joysticks, gamepads, and other devices, in addition to keyboards and +touchscreens.</p> + +<p>For mouse and trackball input, the platform supports two new motion event +actions: scroll (horizontal or vertical) such as from a scrollwheel; and hover, +which reports the location of the mouse when no buttons are pressed. +Applications can handle these events in any way needed.</p> + +<p>For joysticks and gamepads, the platform provides a large number of motion +axes that applications can use from a given input source, such as X, Y, Hat X, +Hat Y, rotation, throttle, pressure, size, touch, tool, orientation, and others. +Developers can also define custom axes if needed, to capture motion in +additional ways. The platform provides motion events to applications as a batch, +and applications can query the details of the movements included in the batch, +for more efficient and precise handling of events.</p> + +<p>Applications can query for the list of connected input devices and the motion +ranges (axes) supported by each device. Applications can also handle multiple +input and motion events from a single input device. For example, an application +can use mouse and joystick and mouse event sources from a single input +device.</p> + +<h3 id="resizewidgetsapp">Resizable Home screen widgets</h3> + +<p>Developers can now create Home screen widgets that users can resize +horizontally, vertically, or both. By simply adding an attribute to the +declaration of a widget, the widget becomes resizable horizontally, vertically, +or both. This lets users customize the display of the widget content and display +more of it on their Home screens.</p> + +<h3 id="mtp">MTP API for integrating with external cameras</h3> + +<p>In Android 3.1, a new MTP (Media Transfer Protocol) API lets developers write +apps that interact directly with connected cameras and other PTP devices. The +new API makes it easy for applications to receive notifications when devices are +attached and removed, manage files and storage on those devices, and transfer +files and metadata to and from them. The MTP API implements the PTP (Picture +Transfer Protocol) subset of the MTP specification.</p> + +<h3 id="rtp">RTP API, for control over audio streaming sessions</h3> + +<p>Android 3.1 exposes an API to its built-in RTP (Real-time Transport Protocol) +stack, which applications can use to directly manage on-demand or interactive +data streaming. In particular, apps that provide VOIP, push-to-talk, +conferencing, and audio streaming can use the API to initiate sessions and +transmit or receive data streams over any available network.</p> + +<h3 id="performance">Performance optimizations</h3> + +<p>Android 3.1 includes a variety of performance optimizations that help make +applications faster and more responsive. Some of the optimizations include:</p> + +<ul> +<li>A new LRU cache class lets applications benefit from efficient caching. +Applications can use the class to reduce the time spent computing or downloading +data from the network, while maintaining a sensible memory footprint for the +cached data.</li> +<li>The UI framework now supports partial invalidates in hardware-accelerated +Views, which makes drawing operations in those Views more efficient.</li> +<li>A new graphics method, {@link android.graphics.Bitmap#setHasAlpha(boolean) +setHasAlpha()}, allows apps to hint that a given bitmap is opaque. This provides +an extra performance boost for some types of blits and is especially useful for +applications that use ARGB_8888 bitmaps.</li> +</ul> + diff --git a/docs/html/sdk/android-3.1.jd b/docs/html/sdk/android-3.1.jd new file mode 100644 index 0000000..57fe1eb --- /dev/null +++ b/docs/html/sdk/android-3.1.jd @@ -0,0 +1,1053 @@ +page.title=Android 3.1 Platform +sdk.platform.version=3.1 +sdk.platform.apiLevel=12 +@jd:body + +<div id="qv-wrapper"> +<div id="qv"> + +<h2>In this document</h2> +<ol> + <li><a href="#relnotes">Revisions</a></li> + <li><a href="#api">API Overview</a></li> + <li><a href="#api-level">API Level</a></li> + <li><a href="#apps">Built-in Applications</a></li> + <li><a href="#locs">Locales</a></li> + <li><a href="#skins">Emulator Skins</a></li> +</ol> + +<h2>Reference</h2> +<ol> +<li><a +href="{@docRoot}sdk/api_diff/11/changes.html">API +Differences Report »</a> </li> +</ol> + +<h2>See Also</h2> +<ol> + <li><a href="{@docRoot}guide/practices/optimizing-for-3.0.html">Optimizing +Apps for Android 3.0</a></li> +</ol> + +</div> +</div> + + +<p><em>API Level:</em> <strong>{@sdkPlatformApiLevel}</strong></p> + +<p>For developers, the Android {@sdkPlatformVersion} platform is available as a +downloadable component for the Android SDK. The downloadable platform includes +an Android library and system image, as well as a set of emulator skins and +more. The downloadable platform includes no external libraries.</p> + +<p>To get started developing or testing against Android {@sdkPlatformVersion}, +use the Android SDK Manager to download the platform into your SDK. For more +information, see <a href="{@docRoot}sdk/adding-components.html">Adding SDK +Components</a>. If you are new to Android, <a +href="{@docRoot}sdk/index.html">download the SDK Starter Package</a> first.</p> + +<p>For a high-level introduction to Android {@sdkPlatformVersion}, see the <a +href="{@docRoot}sdk/android-{@sdkPlatformVersion}-highlights.html">Platform +Highlights</a>.</p> + +<p class="note"><strong>Reminder:</strong> If you've already published an +Android application, please test and optimize your application on Android 3.0 +and Android 3.1 as soon as possible. You should do so to be sure your +application provides the best experience possible on the latest Android-powered +devices. For information about what you can do, read <a +href="{@docRoot}guide/practices/optimizing-for-3.0.html">Optimizing Apps for +Android 3.0</a>.</p> + + +<h2 id="relnotes">Revisions</h2> + +<p>To determine what revision of the Android {@sdkPlatformVersion} platform you +have installed, refer to the "Installed Packages" listing in the Android SDK and +AVD Manager.</p> + + +<div class="toggle-content opened" style="padding-left:1em;"> + + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-opened.png" +class="toggle-content-img" alt="" /> + Android {@sdkPlatformVersion}, Revision 1</a> <em>(May 2011)</em> + </a></p> + + <div class="toggle-content-toggleme" style="padding-left:2em;"> + +<dl> + +<dt>Dependencies:</dt> +<dd> +<p>Requires <a href="{@docRoot}sdk/tools-notes.html">SDK Tools r11</a> or +higher.</p> +</dd> + +</dl> + + </div> +</div> + + +<h2 id="#api" style="margin-top:1.5em;">API Overview</h2> + +<p>The sections below provide a technical overview of what's new for developers +in Android 3.1, including new features and changes in the framework API since +the previous version.</p> + +<h3 id="usb">USB APIs</h3> + +<p>Android 3.1 introduces powerful new APIs for +integrating connected peripherals with applications running on the platform. +The APIs are based on a USB (Universal Serial Bus) stack and services that are +built into the platform, including support for both USB host and device +interactions. Using the APIs, developers can create applications that are able to +discover, communicate with, and manage a variety of device types connected over +USB. </p> + +<p>The stack and APIs distinguish two basic types of USB hardware, based on +whether the platform iself is acting as host or the external hardware is acting +as host: </p> + +<ul> +<li>A <em>USB device</em> is a piece of connected hardware that depends on the +Android-powered device to serve as host. For example, most input devices, mice, +and joysticks are USB devices, as are many cameras, hubs, and so on.</li> +<li>A <em>USB accessory</em> is a piece of connected hardware that has a USB +host controller, provides power, and is designed to communicate with +Android-powered devices over USB, A variety of peripherals can connect as +accessories, from robotics controllers to musical equipment, exercise bicycles, +and more.</li> +</ul> + +<p>For both types — USB devices and USB accessories — the +platform's USB APIs support discovery by intent broadcast when attached or +detached, as well as standard interfaces, endpoints, and transfer modes +(control, bulk, and interrupt).</p> + +<p>The USB APIs are available in the package {@link android.hardware.usb}. The +central class is {@link android.hardware.usb.UsbManager}, which provides +helper methods for identifying and communicating with +both USB devices and USB accessories. Applications can acquire an instance of +{@link android.hardware.usb.UsbManager} and then query for the list of attached +devices or accessories and then communicate with or manage them. +{@link android.hardware.usb.UsbManager} also declares intent actions that the +system broadcasts, to announce when a USB device or accessory is attached or +detached.</p> + +<p>Other classes include:</p> + +<ul> +<li>{@link android.hardware.usb.UsbDevice}, a class representing external +hardware connected as a USB device (with the Android-powered device acting as +host).</li> +<li>{@link android.hardware.usb.UsbAccessory}, representing external hardware +connected as the USB host (with the Android-powered device acting as a USB +device).</li> +<li>{@link android.hardware.usb.UsbInterface} and {@link +android.hardware.usb.UsbEndpoint}, which provide access to standard USB +interfaces and endpoints for a device.</li> +<li>{@link android.hardware.usb.UsbDeviceConnection} and {@link +android.hardware.usb.UsbRequest}, for sending and receiving data and control +messages to or from a USB device, sychronously and asynchronously. +<li>{@link android.hardware.usb.UsbConstants}, which provides constants for +declaring endpoint types, device classes, and so on.</li> +</ul> + +<p>Note that although the USB stack is built into the platform, actual support +for USB host and open accessory modes on specific devices is determined by +their manufacturers. In particular, host mode relies on appropriate USB +controller hardware in the Android-powered device. </p> + +<p>Additionally, developers can request filtering on Android Market, such that +their applications are not availabe to users whose devices do not provide the +appropriate USB support. To request filtering, add one or both of the elements +below to the application manifest, as appropriate: </p> + +<ul> +<li>If the application should only be visible to devices that support USB +host mode (connection of USB devices), declare this element: + <p style="margin-left:1.5em;"><code><uses-feature + android:name="android.hardware.usb.host" + android:required="true"></code></p> +</li> +<li>If the application should only be visible to devices that support USB +accessories (connection of USB hosts), declare this element: + <p style="margin-left:1.5em;"><code><uses-feature + android:name="android.hardware.usb.accessory" + android:required="true"></code></p> +</li> +</ul> + +<p>For complete information about how to develop applications that interact with +USB accessories, please see the +<a href="{@docRoot}guide/topics/usb/index.html">developer documentation</a>.</p> + +<p class="note">To look at sample applications that use the USB host API, see <a +href="{@docRoot}resources/samples/USB/AdbTest/index.html">ADB Test</a> and <a +href="{@docRoot}resources/samples/USB/MissileLauncher/index.html">Missile +Launcher</a></p> + +<h3>MTP/PTP API</h3> + +<p>Android 3.1 exposes a new MTP API that lets applications interact directly +with connected cameras and other PTP devices. The new API makes it easy for an +application to receive notifications when devices are attached and removed, +manage files and storage on those devices, and transfer files and metadata to +and from them. The MTP API implements the PTP (Picture Transfer Protocol) subset +of the MTP (Media Transfer Protocol) specification.</p> + +<p>The MTP API is available in the {@link android.mtp} package and provides +these classes: </p> + +<ul> + <li>The {@link android.mtp.MtpDevice} encapsulates an MTP device that is +connected over the USB host bus. An application can instantiate an object of +this type and then use its methods to get information about the device and +objects stored on it, as well as opening the connection and transferring data. +Some of the methods include: + <ul> + <li>{@link android.mtp.MtpDevice#getObjectHandles(int, int, int) +getObjectHandles()} returns a list of handles for all objects on the device that +match a specified format and parent. To get information about an object, an +application can pass a handle to {@link android.mtp.MtpDevice#getObjectInfo(int) +getObjectInfo()}.</li> + <li>{@link android.mtp.MtpDevice#importFile(int, java.lang.String) +importFile()} lets an application copy data for an object to a file in external +storage. This call may block for an arbitrary amount of time depending on the +size of the data and speed of the devices, so should be made from a spearate +thread.</li> + <li>{@link +android.mtp.MtpDevice#open(android.hardware.usb.UsbDeviceConnection) open()} +lets an application open a connected MTP/PTP device. </li> + <li>{@link android.mtp.MtpDevice#getThumbnail(int) getThumbnail()} returns +the thumbnail of the object as a byte array. </li> + </ul> + </li> + <li>{@link android.mtp.MtpStorageInfo} holds information about about a storage +unit on an MTP device, corresponding to the StorageInfo Dataset described in +section 5.2.2 of the MTP specification. Methods in the class let an application +get a storage unit’s description string, free space, maximum storage capacity, +storage ID, and volume identifier.</li> + <li>{@link android.mtp.MtpDeviceInfo} holds information about an MTP device +corresponding to the DeviceInfo Dataset described in section 5.1.1 of the MTP +specification. Methods in the class let applications get a device’s +manufacturer, model, serial number, and version.</li> + <li>{@link android.mtp.MtpObjectInfo} holds information about an object stored +on an MTP device, corresponding to the ObjectInfo Dataset described in section +5.3.1 of the MTP specification. Methods in the class let applications get an +object’s size, data format, association type, creation date, and thumbnail +information.</li> + <li>{@link android.mtp.MtpConstants} provides constants for declaring MTP file +format codes, association type, and protection status.</li> +</ul> + +<h3 id="motionevents">Support for new input devices and motion events</h3> + +<p>Android 3.1 extends the input subsystem to support new input devices and new +types of motion events, across all views and windows. Developers can build on +these capabilities to let users interact with their applications using mice, +trackballs, joysticks, gamepads, and other devices, in addition to keyboards and +touchscreens. </p> + +<p>For handling mouse, scrollwheel, and trackball input, the platform supports +two new motion event actions:</p> +<ul> +<li>{@link android.view.MotionEvent#ACTION_SCROLL}, which describes the pointer +location at which a non-touch scroll motion, such as from a mouse scroll wheel, +took place. In the MotionEvent, the value of the {@link +android.view.MotionEvent#AXIS_HSCROLL} and {@link +android.view.MotionEvent#AXIS_VSCROLL} axes specify the relative scroll +movement. </li> +<li>{@link android.view.MotionEvent#ACTION_HOVER_MOVE}, reports the current +position of the mouse when no buttons are pressed, as well as any intermediate +points since the last <code>HOVER_MOVE</code> event. Hover enter and exit +notifications are not yet supported.</li> +</ul> + +<p>To support joysticks and gamepads, the {@link android.view.InputDevice} class +includes these new input device sources:</p> +<ul> +<li>{@link android.view.InputDevice#SOURCE_CLASS_JOYSTICK} — the source +device has joystick axes.</li> +<li>{@link android.view.InputDevice#SOURCE_CLASS_BUTTON} — the source +device has buttons or keys.</li> +<li>{@link android.view.InputDevice#SOURCE_GAMEPAD} — the source device +has gamepad buttons such as {@link android.view.KeyEvent#KEYCODE_BUTTON_A} +or {@link android.view.KeyEvent#KEYCODE_BUTTON_B}. Implies +{@link android.view.InputDevice#SOURCE_CLASS_BUTTON}</li> +<li>{@link android.view.InputDevice#SOURCE_JOYSTICK} — the source device +has joystick axes. Implies SOURCE_CLASS_JOYSTICK.</li> +</ul> + +<p>To describe motion events from these new sources, as well as those from mice +and trackballs, the platform now defines axis codes on {@link +android.view.MotionEvent}, similar to how it defines key codes on {@link +android.view.KeyEvent}. New axis codes for joysticks +and game controllers include +{@link android.view.MotionEvent#AXIS_HAT_X}, {@link +android.view.MotionEvent#AXIS_HAT_Y}, {@link +android.view.MotionEvent#AXIS_RTRIGGER}, {@link +android.view.MotionEvent#AXIS_ORIENTATION}, {@link +android.view.MotionEvent#AXIS_THROTTLE}, and many others. +Existing {@link android.view.MotionEvent} axes are represented by {@link +android.view.MotionEvent#AXIS_X}, {@link android.view.MotionEvent#AXIS_Y}, +{@link android.view.MotionEvent#AXIS_PRESSURE}, {@link +android.view.MotionEvent#AXIS_SIZE}, {@link +android.view.MotionEvent#AXIS_TOUCH_MAJOR}, {@link +android.view.MotionEvent#AXIS_TOUCH_MINOR}, {@link +android.view.MotionEvent#AXIS_TOOL_MAJOR}, {@link +android.view.MotionEvent#AXIS_TOOL_MINOR}, and {@link +android.view.MotionEvent#AXIS_ORIENTATION}.</p> + +<p>Additionally, {@link android.view.MotionEvent} defines a number of generic +axis codes that are used when the framework does not know how to map a +particular axis. Specific devices can use the generic axis codes to pass custom +motion data to applications. For a full list of axes and their intended +interpretations, see the {@link android.view.MotionEvent} class documentation. +</p> + +<p>The platform provides motion events to applications in batches, so a single +event may contain a current position and multiple so-called historical movements. +Applications should use {@link android.view.MotionEvent#getHistorySize()} to get +the number of historical samples, then retrieve and process all historical +samples in order using {@link +android.view.MotionEvent#getHistoricalAxisValue(int, int, int) +getHistoricalAxisValue()}. After that, applications should process the current +sample using {@link android.view.MotionEvent#getAxisValue(int) getAxisValue()}. +</p> + +<p>Some axes can be retrieved using special accessor methods. For example, +instead of calling {@link android.view.MotionEvent#getAxisValue(int) +getAxisValue()}, applications can call {@link android.view.MotionEvent#getX(int) +getX()}. Axes that have built-in accessors include {@link +android.view.MotionEvent#AXIS_X}, {@link android.view.MotionEvent#AXIS_Y}, +{@link android.view.MotionEvent#AXIS_PRESSURE}, {@link +android.view.MotionEvent#AXIS_SIZE}, {@link +android.view.MotionEvent#AXIS_TOUCH_MAJOR}, {@link +android.view.MotionEvent#AXIS_TOUCH_MINOR}, {@link +android.view.MotionEvent#AXIS_TOOL_MAJOR}, {@link +android.view.MotionEvent#AXIS_TOOL_MINOR}, and {@link +android.view.MotionEvent#AXIS_ORIENTATION}.</p> + +<p>Each input device has a unique, system-assigned ID and may also provide +multiple sources. When a device provides multiple sources, more than one source +can provide axis data using the same axis. For example, a touch event coming +from the touch source uses the X axis for screen position data, while a joystick +event coming from the joystick source will use the X axis for the stick position +instead. For this reason, it's important for applications to interpret axis +values according to the source from which they originate. When handling a motion +event, applications should use methods on the {@link android.view.InputDevice} +class to determine the axes supported by a device or source. Specifically, +applications can use {@link android.view.InputDevice#getMotionRanges() +getMotionRanges()} to query for all axes of a device or all axes of a given +source of the device. In both cases, the range information for axes returned in +the {@link android.view.InputDevice.MotionRange} object specifies the source for +each axis value.</p> + +<p>Finally, since the motion events from joysticks, gamepads, mice, and +trackballs are not touch events, the platform adds a new callback method for +passing them to a {@link android.view.View} as "generic" motion events. +Specifically, it reports the non-touch motion events to +{@link android.view.View}s through a call to {@link +android.view.View#onGenericMotionEvent(android.view.MotionEvent) +onGenericMotionEvent()}, rather than to {@link +android.view.View#onTouchEvent(android.view.MotionEvent) +onTouchEvent()}.</p> + +<p>The platform dispatches generic motion events differently, depending on the +event source class. {@link android.view.InputDevice#SOURCE_CLASS_POINTER} events +go to the {@link android.view.View} under the pointer, similar to how touch +events work. All others go to the currently focused {@link android.view.View}. +For example, this means a {@link android.view.View} must take focus in order to +receive joystick events. If needed, applications can handle these events at the +level of Activity or Dialog by implementing {@link +android.view.View#onGenericMotionEvent(android.view.MotionEvent) +onGenericMotionEvent()} there instead.</p> + +<p class="note">To look at a sample application that uses joystick motion +events, see <a +href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/view/ +GameControllerInput.html">GameControllerInput</a> and <a +href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/view/ +GameView.html">GameView</a>.</p> + +<h3>RTP API</h3> + +<p>Android 3.1 exposes an API to its built-in RTP (Real-time Transport Protocol) +stack, which applications can use to manage on-demand or interactive data +streaming. In particular, apps that provide VOIP, push-to-talk, conferencing, +and audio streaming can use the API to initiate sessions and transmit or receive +data streams over any available network.</p> + +<p>The RTP API is available in the {@link android.net.rtp} package. Classes +include: </p> +<ul> +<li>{@link android.net.rtp.RtpStream}, the base class of streams that send and +receive network packets with media payloads over RTP.</li> +<li>{@link android.net.rtp.AudioStream}, a subclass of {@link +android.net.rtp.RtpStream} that carries audio payloads over RTP.</li> +<li>{@link android.net.rtp.AudioGroup}, a local audio hub for managing and +mixing the device speaker, microphone, and {@link android.net.rtp.AudioStream}.</li> +<li>{@link android.net.rtp.AudioCodec}, which holds a collection of codecs that +you define for an {@link android.net.rtp.AudioStream}.</li> +</ul> + +<p>To support audio conferencing and similar usages, an application instantiates +two classes as endpoints for the stream:</p> + +<ul> +<li>{@link android.net.rtp.AudioStream} specifies a remote endpoint and consists +of network mapping and a configured {@link android.net.rtp.AudioCodec}.</li> +<li>{@link android.net.rtp.AudioGroup} represents the local endpoint for one +or more {@link android.net.rtp.AudioStream}s. The {@link android.net.rtp.AudioGroup} mixes +all the {@link android.net.rtp.AudioStream}s and optionally interacts with the device +speaker and the microphone at the same time.</li> +</ul> + +<p>The simplest usage involves a single remote endpoint and local endpoint. +For more complex usages, please refer to the limitations described for +{@link android.net.rtp.AudioGroup}.</p> + +<p>To use the RTP API, applications must request permission from the user by +declaring <code><uses-permission +android:name="android.permission.INTERNET"></code> +in their manifest files. To acquire the device microphone, the <code><uses-permission +android:name="android.permission.RECORD_AUDIO"></code> permission is also required.</p> + +<h3 id="resizewidgets">Resizable app widgets</h3> + +<p>Starting in Android 3.1, developers can make their homescreen widgets +resizeable — horizontally, vertically, or on both axes. Users touch-hold a +widget to show its resize handles, then drag the horizontal and/or vertical +handles to change the size on the layout grid. </p> + +<p>Developers can make any Home screen widget resizeable by defining a +<code>resizeMode</code> attribute in the widget's {@link +android.appwidget.AppWidgetProviderInfo} metadata. Values for the +<code>resizeMode</code> attribute include "horizontal", "vertical", and "none". +To declare a widget as resizeable horizontally and vertically, supply the value +"horizontal|vertical". + +<p>Here's an example: </p> + +<pre><appwidget-provider xmlns:android="http://schemas.android.com/apk/res/android" + android:minWidth="294dp" + android:minHeight="72dp" + android:updatePeriodMillis="86400000" + android:previewImage="@drawable/preview" + android:initialLayout="@layout/example_appwidget" + android:configure="com.example.android.ExampleAppWidgetConfigure" + android:resizeMode="horizontal|vertical" > +</appwidget-provider></pre> + +<p>For more information about Home screen widgets, see the <a +href="{@docRoot}guide/topics/appwidgets/index.html">App Widgets</a> +documentation.</p> + +<h3 id="animation" style="margin-top:1.25em;">Animation framework</h3> + +<ul> +<li>New ViewPropertyAnimator class + <ul> + <li>A new {@link android.view.ViewPropertyAnimator} class provides a +convenient +way for developers to animate select properties on {@link android.view.View} objects. The class +automaties and optimizes the animation of the properties and makes it easier to +manage multiple simulataneous animations on a {@link android.view.View} object. +<p>Using the {@link android.view.ViewPropertyAnimator} is straightforward. To animate properties for +a {@link android.view.View}, call {@link android.view.View#animate()} to +construct a {@link android.view.ViewPropertyAnimator} object for that {@link android.view.View}. Use the +methods on the {@link android.view.ViewPropertyAnimator} to specify what property to +animate and how to animate it. For example, to fade the {@link android.view.View} to transparent, +call <code>alpha(0);</code>. The {@link android.view.ViewPropertyAnimator} object +handles the details of configuring the underlying {@link +android.animation.Animator} class and starting it, then rendering the +animation.</p></li> + </ul> +</li> +<li>Animation background color + <ul> + <li>New {@link android.view.animation.Animation#getBackgroundColor()} and + {@link android.view.animation.Animation#setBackgroundColor(int)} methods let + you get/set the background color behind animations, for window animations +only. Currently the background must be black, with any desired alpha level.</li> + </ul> +</li> +<li>Getting animated fraction from <code>ViewAnimator</code> + <ul> + <li>A new {@link android.animation.ValueAnimator#getAnimatedFraction()} +method +lets you get the current animation fraction — the elapsed/interpolated +fraction used in the most recent frame update — from a {@link +android.animation.ValueAnimator}.</li> + </ul> +</li> +</ul> + +<h3 "ui">UI framework</h3> +<ul> +<li>Forced rendering of a layer + <ul> + <li>A new {@link android.view.View#buildLayer()} method lets an application +force a View's layer to be created and the View rendered into it immediately. +For example, an application could use this method to render a View into its +layer before starting an animation. If the View is complex, rendering it into +the layer before starting the animation will avoid skipping frames.</li> + </ul> +</li> +<li>Camera distance + <ul> + <li>Applications can use a new method +{@link android.view.View#setCameraDistance(float)} to set the distance from the +camera +to a View. This gives applications improved control over 3D transformations of +the View, such as rotations. </li> + </ul> +</li> +<li>Getting a calendar view from a DatePicker + <ul> + <li>A new {@link android.widget.DatePicker#getCalendarView()} method + lets you get a {@link android.widget.CalendarView} from a {@link +android.widget.DatePicker} + instance.</li> + </ul> +</li> +<li>Getting callbacks when views are detached + <ul> + <li>A new {@link android.view.View.OnAttachStateChangeListener} lets you +receive +callbacks when a View is attached or detached from its window. Use {@link +android.view.View#addOnAttachStateChangeListener(android.view.View.OnAttachStateChangeListener) addOnAttachStateChangeListener()} +to add a listener and {@link +android.view.View#removeOnAttachStateChangeListener(android.view.View.OnAttachStateChangeListener) addOnAttachStateChangeListener()} to remove it.</li> + </ul> +</li> +<li>Fragment breadcrumb listener, new onInflate() signature + <ul> + <li>A new method, {@link +android.app.FragmentBreadCrumbs#setOnBreadCrumbClickListener(android.app.FragmentBreadCrumbs.OnBreadCrumbClickListener) setOnBreadCrumbClickListener()}, +provides a hook to let +applications intercept fragment-breadcrumb clicks and take any action needed +before going to the backstack entry or fragment that was clicked. </li> + <li>In the {@link android.app.Fragment} class, {@link +android.app.Fragment#onInflate(android.util.AttributeSet, android.os.Bundle) +onInflate(attrs, savedInstanceState)} is deprecated. Please use {@link +android.app.Fragment#onInflate(android.app.Activity, android.util.AttributeSet, +android.os.Bundle) onInflate(activity, attrs, savedInstanceState)} instead.</li> + </ul> +</li> +<li>Display search result in new tab + <ul> + <li>An {@link android.app.SearchManager#EXTRA_NEW_SEARCH} data key for {@link +android.content.Intent#ACTION_WEB_SEARCH} intents lets you open a search in a +new browser tab, rather than in an existing one.</li> + </ul> +</li> + +<li>Drawable text cursor + <ul> +<li>You can now specify a drawable to use as the text cursor using the new +resource attribute {@link android.R.attr#textCursorDrawable}.</li> + </ul> +</li> +<li>Setting displayed child in remote views + <ul> + <li>A new convenience method, {@link +android.widget.RemoteViews#setDisplayedChild(int, int) setDisplayedChild(viewId, +childIndex)}, is available in {@link android.widget.RemoteViews} subclasses, to +let you set the child displayed in {@link android.widget.ViewAnimator} and +{@link android.widget.AdapterViewAnimator} subclasses such as {@link +android.widget.AdapterViewFlipper}, {@link android.widget.StackView}, {@link +android.widget.ViewFlipper}, and {@link android.widget.ViewSwitcher}.</li> + </ul> +</li> +<li>Generic keys for gamepads and other input devices + <ul> + <li>{@link android.view.KeyEvent} adds a range of generic keycodes to + accommodate gamepad buttons. The class also adds + {@link android.view.KeyEvent#isGamepadButton(int)} and several other + helper methods for working with keycodes.</li> + </ul> +</li> +</ul> + +<h3 id="graphics" style="margin-top:1.3em;">Graphics</h3> + +<ul> +<li>Helpers for managing bitmaps + <ul> + <li>{@link android.graphics.Bitmap#setHasAlpha(boolean)} lets an app indicate that +all of the pixels in a Bitmap are known to be opaque (false) or that some of the +pixels may contain non-opaque alpha values (true). Note, for some configs (such +as RGB_565) this call is ignored, since it does not support per-pixel alpha +values. This is meant as a drawing hint, as in some cases a bitmap that is known +to be opaque can take a faster drawing case than one that may have non-opaque +per-pixel alpha values. </li> + <li>{@link android.graphics.Bitmap#getByteCount()} gets a Bitmap's size in +bytes.</li> + <li>{@link android.graphics.Bitmap#getGenerationId()} lets an application find +out whether a Bitmap has been modified, such as for caching.</li> + <li>{@link android.graphics.Bitmap#sameAs(android.graphics.Bitmap)} determines +whether a given Bitmap differs from the current Bitmap, in dimension, +configuration, or pixel data. </li> + </ul> +</li> +<li>Setting camera location and rotation + <ul> + <li>{@link android.graphics.Camera} adds two new methods {@link +android.graphics.Camera#rotate(float, float, float) rotate()} and {@link +android.graphics.Camera#setLocation(float, float, float) setLocation()} for +control of the +camera's location, for 3D transformations.</li> +</ul> +</li> +</ul> + +<h3 id="network" style="margin-top:1.25em;">Network</h3> + +<ul> +<li>High-performance Wi-Fi lock + <ul> + <li>A new high-performance Wi-Fi lock lets applications maintain +high-performance Wi-Fi connections even when the device screen is off. +Applications that stream music, video, or voice for long periods can acquire the +high-performance Wi-Fi lock to ensure streaming performance even when the screen +is off. Because it uses more power, applications should acquire the +high-performance Wi-Fi when there is a need for a long-running active +connection. +<p>To create a high-performance lock, pass {@link +android.net.wifi.WifiManager#WIFI_MODE_FULL_HIGH_PERF} as the lock mode in a +call to {@link android.net.wifi.WifiManager#createWifiLock(int, +java.lang.String) createWifiLock()}.</p></li> + </ul> +</li> +<li>More traffic stats + <ul> + <li>Applications can now access statistics about more types of network usage +using new methods in {@link android.net.TrafficStats}. Applications can use the +methods to get UDP stats, packet count, TCP transmit/receive payload bytes and +segments for a given UID.</li> + </ul> +</li> +<li>SIP auth username + <ul> + <li>Applications can now get and set the SIP auth username for a profile +using +the new methods {@link android.net.sip.SipProfile#getAuthUserName() +getAuthUserName()} and {@link +android.net.sip.SipProfile.Builder#setAuthUserName(java.lang.String) +setAuthUserName()}.</li> + </ul> +</li> +</ul> + + +<h3 id="download" style="margin-top:1.25em;">Download Manager</h3> +<ul> +<li>Handling of completed downloads + <ul> + <li>Applications can now initiate downloads that notify users only on +completion. To initiate this type of download, applications pass {@link +android.app.DownloadManager.Request#VISIBILITY_VISIBLE_NOTIFY_ONLY_COMPLETION} +in the {@link +android.app.DownloadManager.Request#setNotificationVisibility(int) +setNotificationVisibility()} method of +the a request object.</li> + <li>A new method, {@link +android.app.DownloadManager#addCompletedDownload(java.lang.String, +java.lang.String, boolean, java.lang.String, java.lang.String, long, boolean) +addCompletedDownload()}, lets an application add a file to the +downloads database, so that it can be managed by the Downloads application.</li> + </ul> +</li> +<li>Show downloads sorted by size + <ul> + <li>Applications can start the Downloads application in sort-by-size mode by +adding the new extra {@link +android.app.DownloadManager#INTENT_EXTRAS_SORT_BY_SIZE} to an {@link +android.app.DownloadManager#ACTION_VIEW_DOWNLOADS} intent.</li> + </ul> +</li> +</ul> + +<h3 id="ime" style="margin-top:1.25em;">IME framework</h3> + +<ul> +<li>Getting an input method's extra value key + <ul><li>The {@link android.view.inputmethod.InputMethodSubtype} adds the +method +{@link +android.view.inputmethod.InputMethodSubtype#containsExtraValueKey(java.lang.String) containsExtraValueKey()} to check whether an ExtraValue string is stored +for the subtype and +the method {@link +android.view.inputmethod.InputMethodSubtype#getExtraValueOf(java.lang.String) +getExtraValueOf()} to extract a specific key value from the ExtraValue hashmap. +</li> + </ul> +</li> +</ul> + +<h3 id="media" style="margin-top:1.25em;">Media</h3> + +<ul> +<li>New streaming audio formats + <ul> + <li>The media framework adds built-in support for raw ADTS AAC content, for +improved streaming audio, as well as support for FLAC audio, for highest quality +(lossless) compressed audio content. See the <a +href="{@docRoot}guide/appendix/media-formats.html">Supported Media Formats</a> +document for more information.</p></li> + </ul> +</li> +</ul> + +<h3 id="launchcontrols" style="margin-top:1.25em;">Launch controls on stopped +applications</h3> + +<p>Starting from Android 3.1, the system's package manager keeps track of +applications that are in a stopped state and provides a means of controlling +their launch from background processes and other applications.</p> + +<p>Note that an application's stopped state is not the same as an Activity's +stopped state. The system manages those two stopped states separately.</p> + +<p>The platform defines two new intent flags that let a sender specify +whether the Intent should be allowed to activate components in stopped +application.</p> + +<ul> +<li>{@link android.content.Intent#FLAG_INCLUDE_STOPPED_PACKAGES} — +Include intent filters of stopped applications in the list of potential targets +to resolve against. </li> +<li>{@link android.content.Intent#FLAG_EXCLUDE_STOPPED_PACKAGES} — +Exclude intent filters of stopped applications from the list of potential +targets.</li> +</ul> + +<p>When neither or both of these flags is defined in an intent, the default +behavior is to include filters of stopped applications in the list of +potential targets.</p> + +<p>Note that the system adds {@link +android.content.Intent#FLAG_EXCLUDE_STOPPED_PACKAGES} <em>to all broadcast +intents</em>. It does this to prevent broadcasts from background services from +inadvertently or unnecessarily launching components of stoppped applications. +A background service or application can override this behavior by adding the +{@link android.content.Intent#FLAG_INCLUDE_STOPPED_PACKAGES} flag to broadcast +intents that should be allowed to activate stopped applications.</p> + +<p>Applications are in a stopped state when they are first installed but are not +yet launched and when they are manually stopped by the user (in Manage +Applications).</p> + +<h3 id="installnotification">Notification of application first launch and upgrade</h3> + +<p>The platform adds improved notification of application first launch and +upgrades through two new intent actions:</p> + +<ul> +<li>{@link android.content.Intent#ACTION_PACKAGE_FIRST_LAUNCH} — Sent to +the installer package of an application when that application is first launched +(that is, the first time it is moved out of a stopped state). The data +contains the name of the package. </li> + +<li>{@link android.content.Intent#ACTION_MY_PACKAGE_REPLACED} — Notifies +an application that it was updated, with a new version was installed over +an existing version. This is only sent to the application that was replaced. It +does not contain any additional data. To receive it, declare an intent filter +for this action. You can use the intent to trigger code that helps get your +application back in proper running shape after an upgrade. + +<p>This intent is sent directly to the application, but only if the application +was upgraded while it was in started state (not in a stopped state).</p></li> + +</ul> + +<h3 if="other">Core utilities</h3> + +<ul> +<li>LRU cache + <ul> + <li>A new {@link android.util.LruCache} class lets your applications benefit +from efficient caching. Applications can use the class to reduce the time spent +computing or downloading data from the network, while maintaining a sensible +memory footprint for the cached data.{@link android.util.LruCache} is a cache +that holds strong references to a limited number of values. Each time a value is +accessed, it is moved to the head of a queue. When a value is added to a full +cache, the value at the end of that queue is evicted and may become eligible for +garbage collection.</li> + </ul> +</li> +<li>File descriptor as <code>int</code> + <ul> + <li>You can now get the native file descriptor int for a {@link +android.os.ParcelFileDescriptor} using either of the new methods {@link +android.os.ParcelFileDescriptor#getFd()} or {@link +android.os.ParcelFileDescriptor#detachFd()}. </li> + </ul> +</li> +</ul> + + + + + + +<h3 id="webkit" style="margin-top:1.25em;">WebKit</h3> + +<ul> + +<li>File scheme cookies + <ul> + <li>The {@link android.webkit.CookieManager} now supports cookies that use +the +<code>file:</code> URI scheme. You can use {@link +android.webkit.CookieManager#setAcceptFileSchemeCookies(boolean) +setAcceptFileSchemeCookies()} to +enable/disable support for file scheme cookies, before constructing an instance +of <code>WebView</code> or <code>CookieManager</code>. In a +<code>CookieManager</code> instance, you can check whether file scheme cookies +is enabled by calling {@link +android.webkit.CookieManager#allowFileSchemeCookies()}.</li> + </ul> +</li> +<li>Notification of login request + <ul> + <li>To support the browser autologin features introduced in Android 3.0, the +new +method {@link +android.webkit.WebViewClient#onReceivedLoginRequest(android.webkit.WebView,java.lang.String, java.lang.String, java.lang.String) onReceivedLoginRequest()} +notifies the host +application that an autologin request for the user was processed. </li> + </ul> +</li> +<li>Removed classes and interfaces + <ul> + <li>Several classes and interfaces were removed from the public API, after +previously being in deprecated state. See the <a +href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API +Differences Report</a> for more information.</p></li> + </ul> + </li> +</ul> + + + +<h3 id="browser" style="margin-top:1.25em;">Browser</h3> + +<p>The Browser application adds the following features to support web +applications:</p> + +<ul> +<li>Support for inline playback of video embedded in HTML5 +<code><video></code> tag. Playback is hardware-accelerated where possible. +</li> +<li>Layer support for fixed position elements for all sites (mobile and +desktop).</li> +</ul> + + + + + +<h3 id="features">New feature constants</h3> + +<p>The platform adds new hardware feature constants that developers can declare +in their application manifests, to inform external entities such as Android +Market of the application's requirement for new hardware capabilities supported +in this version of the platform. Developers declare these and other feature +constants in <a +href="{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code +<uses-feature>}</a> manifest elements. + +<ul> + <li>{@link android.content.pm.PackageManager#FEATURE_USB_ACCESSORY +android.hardware.usb.accessory} — The application uses the <a href="#usb">USB +API</a> to communicate with external hardware devices connected over USB and +function as hosts.</li> + <li>{@link android.content.pm.PackageManager#FEATURE_USB_HOST +android.hardware.usb.host} — The application uses the <a href="#usb">USB API</a> +to communicate with external hardware devices connected over USB and function as +devices.</li> +</ul> + +<p>Android Market filters applications based on features declared in <a +href="{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code +<uses-feature>}</a> manifest elements. For more information about +declaring features in an application manifest, read <a +href="{docRoot}guide/appendix/market-filters.html">Android Market +Filters</a>.</p> + + + +<h3 id="api-diff">API Differences Report</h3> + +<p>For a detailed view of all API changes in Android {@sdkPlatformVersion} (API +Level +{@sdkPlatformApiLevel}), see the <a +href="{@docRoot}sdk/api_diff/{@sdkPlatformApiLevel}/changes.html">API +Differences Report</a>.</p> + + + + + +<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 — +<strong>{@sdkPlatformApiLevel}</strong> — 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 compile the application against the Android library that is provided in +the Android {@sdkPlatformVersion} SDK platform. Depending on your needs, you +might +also need to add an <code>android:minSdkVersion="{@sdkPlatformApiLevel}"</code> +attribute to the <code><uses-sdk></code> element in the 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="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>API Demos</li> +<li>Browser</li> +<li>Calculator</li> +<li>Camera</li> +<li>Clock</li> +<li>Contacts</li> +<li>Custom Locale</li> +<li>Dev Tools</li> +<li>Downloads</li> +<li>Email</li> +</ul> +</td> +<td style="border:0;padding-bottom:0;margin-bottom:0;padding-left:5em;"> +<ul> +<li>Gallery</li> +<li>Gestures Builder</li> +<li>Messaging</li> +<li>Music</li> +<li>Search</li> +<li>Settings</li> +<li>Spare Parts</li> +<li>Speech Recorder</li> +<li>Widget Preview</li> +</ul> +</td> +</tr> +</table> + + +<h2 id="locs" style="margin-top:.75em;">Locales</h2> + +<p>The system image included in the downloadable SDK 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 3.0 system +image are listed below (with <em>language</em>_<em>country/region</em> locale +descriptor).</p> + +<table style="border:0;padding-bottom:0;margin-bottom:0;"> +<tr> +<td style="border:0;padding-bottom:0;margin-bottom:0;"> +<ul> +<li>Arabic, Egypt (ar_EG)</li> +<li>Arabic, Israel (ar_IL)</li> +<li>Bulgarian, Bulgaria (bg_BG)</li> +<li>Catalan, Spain (ca_ES)</li> +<li>Czech, Czech Republic (cs_CZ)</li> +<li>Danish, Denmark(da_DK)</li> +<li>German, Austria (de_AT)</li> +<li>German, Switzerland (de_CH)</li> +<li>German, Germany (de_DE)</li> +<li>German, Liechtenstein (de_LI)</li> +<li>Greek, Greece (el_GR)</li> +<li>English, Australia (en_AU)</li> +<li>English, Canada (en_CA)</li> +<li>English, Britain (en_GB)</li> +<li>English, Ireland (en_IE)</li> +<li>English, India (en_IN)</li> +<li>English, New Zealand (en_NZ)</li> +<li>English, Singapore(en_SG)</li> +<li>English, US (en_US)</li> +<li>English, Zimbabwe (en_ZA)</li> +<li>Spanish (es_ES)</li> +<li>Spanish, US (es_US)</li> +<li>Finnish, Finland (fi_FI)</li> +<li>French, Belgium (fr_BE)</li> +<li>French, Canada (fr_CA)</li> +<li>French, Switzerland (fr_CH)</li> +<li>French, France (fr_FR)</li> +<li>Hebrew, Israel (he_IL)</li> +<li>Hindi, India (hi_IN)</li> +</ul> +</td> +<td style="border:0;padding-bottom:0;margin-bottom:0;padding-left:5em;"> +<li>Croatian, Croatia (hr_HR)</li> +<li>Hungarian, Hungary (hu_HU)</li> +<li>Indonesian, Indonesia (id_ID)</li> +<li>Italian, Switzerland (it_CH)</li> +<li>Italian, Italy (it_IT)</li> +<li>Japanese (ja_JP)</li> +<li>Korean (ko_KR)</li> +<li>Lithuanian, Lithuania (lt_LT)</li> +<li>Latvian, Latvia (lv_LV)</li> +<li>Norwegian bokmål, Norway (nb_NO)</li> +<li>Dutch, Belgium (nl_BE)</li> +<li>Dutch, Netherlands (nl_NL)</li> +<li>Polish (pl_PL)</li> +<li>Portuguese, Brazil (pt_BR)</li> +<li>Portuguese, Portugal (pt_PT)</li> +<li>Romanian, Romania (ro_RO)</li> +<li>Russian (ru_RU)</li></li> +<li>Slovak, Slovakia (sk_SK)</li> +<li>Slovenian, Slovenia (sl_SI)</li> +<li>Serbian (sr_RS)</li> +<li>Swedish, Sweden (sv_SE)</li> +<li>Thai, Thailand (th_TH)</li> +<li>Tagalog, Philippines (tl_PH)</li> +<li>Turkish, Turkey (tr_TR)</li> +<li>Ukrainian, Ukraine (uk_UA)</li> +<li>Vietnamese, Vietnam (vi_VN)</li> +<li>Chinese, PRC (zh_CN)</li> +<li>Chinese, Taiwan (zh_TW)</li> +</td> +</tr> +</table> + +<p class="note"><strong>Note:</strong> The Android platform may support more +locales than are included in the SDK system image. All of the supported locales +are available in the <a href="http://source.android.com/">Android Open Source +Project</a>.</p> + +<h2 id="skins">Emulator Skins</h2> + +<p>The downloadable platform includes the following emulator skin:</p> + +<ul> + <li> + WXGA (1280x800, medium density, xlarge 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>
\ No newline at end of file diff --git a/docs/html/sdk/images/3.1/controls.png b/docs/html/sdk/images/3.1/controls.png Binary files differnew file mode 100644 index 0000000..e0ca1f8 --- /dev/null +++ b/docs/html/sdk/images/3.1/controls.png diff --git a/docs/html/sdk/images/3.1/home.png b/docs/html/sdk/images/3.1/home.png Binary files differnew file mode 100644 index 0000000..ea0a75a --- /dev/null +++ b/docs/html/sdk/images/3.1/home.png diff --git a/docs/html/sdk/images/3.1/home_full.png b/docs/html/sdk/images/3.1/home_full.png Binary files differnew file mode 100644 index 0000000..2b8e85e --- /dev/null +++ b/docs/html/sdk/images/3.1/home_full.png diff --git a/docs/html/sdk/images/3.1/resizeable.png b/docs/html/sdk/images/3.1/resizeable.png Binary files differnew file mode 100644 index 0000000..c9f5e8e --- /dev/null +++ b/docs/html/sdk/images/3.1/resizeable.png diff --git a/docs/html/sdk/images/3.1/tasks.png b/docs/html/sdk/images/3.1/tasks.png Binary files differnew file mode 100644 index 0000000..89d69e5 --- /dev/null +++ b/docs/html/sdk/images/3.1/tasks.png diff --git a/docs/html/sdk/sdk_toc.cs b/docs/html/sdk/sdk_toc.cs index 3240b57..11f29b1 100644 --- a/docs/html/sdk/sdk_toc.cs +++ b/docs/html/sdk/sdk_toc.cs @@ -77,37 +77,59 @@ class="new">new!</span></li> </ul> <ul> <li class="toggle-list"> + <div><a href="<?cs var:toroot ?>sdk/android-3.1.html"> + <span class="en">Android 3.1 Platform</span></a> <span class="new">new!</span></div> + <ul> + <li><a href="<?cs var:toroot ?>sdk/android-3.1-highlights.html">Platform Highlights</a></li> + <li><a href="<?cs var:toroot ?>sdk/api_diff/12/changes.html">API Differences Report »</a></li> + </ul> + </li> + <li class="toggle-list"> <div><a href="<?cs var:toroot ?>sdk/android-3.0.html"> - <span class="en">Android 3.0 Platform</span></a> <span class="new">new!</span></div> + <span class="en">Android 3.0 Platform</span></a></div> <ul> <li><a href="<?cs var:toroot ?>sdk/android-3.0-highlights.html">Platform Highlights</a></li> <li><a href="<?cs var:toroot ?>sdk/api_diff/11/changes.html">API Differences Report »</a></li> </ul> </li> + <li><a href="<?cs var:toroot ?>sdk/android-2.3.4.html">Android 2.3.4 Platform</span></a> <span class="new">new!</span></li> <li class="toggle-list"> <div><a href="<?cs var:toroot ?>sdk/android-2.3.3.html"> - <span class="en">Android 2.3.3 Platform</span></a> <span class="new">new!</span></div> + <span class="en">Android 2.3.3 Platform</span></a></div> <ul> <li><a href="<?cs var:toroot ?>sdk/api_diff/10/changes.html">API Differences Report »</a></li> </ul> </li> <li class="toggle-list"> - <div><a href="<?cs var:toroot ?>sdk/android-2.3.html"> - <span class="en">Android 2.3 Platform</span></a></div> + <div><a href="<?cs var:toroot ?>sdk/android-2.2.html"> + <span class="en">Android 2.2 Platform</span></a></div> + <ul> + <li><a href="<?cs var:toroot ?>sdk/android-2.2-highlights.html">Platform Highlights</a></li> + <li><a href="<?cs var:toroot ?>sdk/api_diff/8/changes.html">API Differences Report »</a></li> + </ul> + </li> + <li class="toggle-list"> + <div><a href="<?cs var:toroot ?>sdk/android-2.1.html"> + <span class="en">Android 2.1 Platform</span></a></div> <ul> - <li><a href="<?cs var:toroot ?>sdk/android-2.3-highlights.html">Platform Highlights</a></li> - <li><a href="<?cs var:toroot ?>sdk/api_diff/9/changes.html">API Differences Report »</a></li> + <li><a href="<?cs var:toroot ?>sdk/api_diff/7/changes.html">API Differences Report »</a></li> </ul> </li> - <li><a href="<?cs var:toroot ?>sdk/android-2.2.html">Android 2.2 Platform</a></li> - <li><a href="<?cs var:toroot ?>sdk/android-2.1.html">Android 2.1 Platform</a></li> - <li><a href="<?cs var:toroot ?>sdk/android-1.6.html">Android 1.6 Platform</a></li> - <li><a href="<?cs var:toroot ?>sdk/android-1.5.html">Android 1.5 Platform</a></li> <li class="toggle-list"> - <div><a href="#" onclick="toggle(this.parentNode.parentNode,true); return false;">Older Platforms</a></div> + <div><a href="#" onclick="toggle(this.parentNode.parentNode,true); return false;">Other Platforms</a></div> <ul> + <li class="toggle-list"> + <div><a href="<?cs var:toroot ?>sdk/android-2.3.html"> + <span class="en">Android 2.3 Platform</span></a></div> + <ul> + <li><a href="<?cs var:toroot ?>sdk/android-2.3-highlights.html">Platform Highlights</a></li> + <li><a href="<?cs var:toroot ?>sdk/api_diff/9/changes.html">API Differences Report »</a></li> + </ul> + </li> <li><a href="<?cs var:toroot ?>sdk/android-2.0.1.html">Android 2.0.1 Platform</a></li> <li><a href="<?cs var:toroot ?>sdk/android-2.0.html">Android 2.0 Platform</a></li> + <li><a href="<?cs var:toroot ?>sdk/android-1.6.html">Android 1.6 Platform</a></li> + <li><a href="<?cs var:toroot ?>sdk/android-1.5.html">Android 1.5 Platform</a></li> <li><a href="<?cs var:toroot ?>sdk/android-1.1.html">Android 1.1 Platform</a></li> </ul> </li> diff --git a/docs/html/sdk/tools-notes.jd b/docs/html/sdk/tools-notes.jd index 354fec9..64c8f2a 100644 --- a/docs/html/sdk/tools-notes.jd +++ b/docs/html/sdk/tools-notes.jd @@ -65,7 +65,7 @@ padding: .25em 1em; <div class="toggleable opened"> <a href="#" onclick="return toggleDiv(this)"> <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-img" height="9px" width="9px" /> -SDK Tools, Revision 10</a> <em>(February 2011)</em> +SDK Tools, Revision 11</a> <em>(May 2011)</em> <div class="toggleme"> <dl> <dt>Dependencies:</dt> |
