From fefa95a9c828d2b67227894b7ee3979504c0f52a Mon Sep 17 00:00:00 2001
From: Dirk Dougherty
Date: Mon, 7 Feb 2011 17:32:11 -0800
Subject: [PATCH] Doc change: Add version notes for Android 2.3.3.
---
docs/html/guide/appendix/api-levels.jd | 1 +
docs/html/sdk/android-2.3-highlights.jd | 5 +-
docs/html/sdk/android-2.3.3.jd | 426 ++++++++++++++++++++++++++++++++
docs/html/sdk/sdk_toc.cs | 7 +
4 files changed, 438 insertions(+), 1 deletion(-)
create mode 100644 docs/html/sdk/android-2.3.3.jd
diff --git a/docs/html/guide/appendix/api-levels.jd b/docs/html/guide/appendix/api-levels.jd
index 6ab0fc2af8d7..cbe3bf4c2981 100644
--- a/docs/html/guide/appendix/api-levels.jd
+++ b/docs/html/guide/appendix/api-levels.jd
@@ -83,6 +83,7 @@ Android platform.
Platform Version | API Level |
+ Android 2.3.3 | 10 |
Android 2.3 | 9 |
Android 2.2 | 8 |
Android 2.1 | 7 |
diff --git a/docs/html/sdk/android-2.3-highlights.jd b/docs/html/sdk/android-2.3-highlights.jd
index d8614d3afa52..b076b3de191c 100644
--- a/docs/html/sdk/android-2.3-highlights.jd
+++ b/docs/html/sdk/android-2.3-highlights.jd
@@ -336,12 +336,15 @@ can create new applications that offer proximity-based information and services
to users, organizations, merchants, and advertisers.
Using the NFC API,
-applications can respond to NFC tags âdiscoveredâ as the user âtouchesâ an
+applications can read and respond to NFC tags âdiscoveredâ as the user âtouchesâ an
NFC-enabled device to elements embedded in stickers, smart posters, and even
other devices. When a tag of interest is collected, applications can respond to
the tag, read messages from it, and then store the messages, prompting
the user as needed.
+Starting from Android 2.3.3, applications can also write to tags and
+set up peer-to-peer connections with other NFC devices.
+
NFC communication relies on wireless technology in the device hardware, so
support for the platform's NFC features on specific devices is determined by
their manufacturers.
diff --git a/docs/html/sdk/android-2.3.3.jd b/docs/html/sdk/android-2.3.3.jd
new file mode 100644
index 000000000000..dbc48f429f9a
--- /dev/null
+++ b/docs/html/sdk/android-2.3.3.jd
@@ -0,0 +1,426 @@
+page.title=Android 2.3.3 Platform
+sdk.platform.version=2.3.3
+sdk.platform.apiLevel=10
+
+
+@jd:body
+
+
+
+
+API Level: {@sdkPlatformApiLevel}
+
+Android 2.3.3 is a small feature release that adds several improvements
+and APIs to the Android 2.3 platform.
+
+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.
+
+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 Adding SDK
+Components. If you are new to Android, download the SDK Starter Package
+first.
+
+For a high-level introduction to Android 2.3, see the Platform Highlights.
+
+
+Revisions
+
+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.
+
+
+
+
+
+
+
+API Overview
+
+The sections below provide a technical overview of what's new for developers
+in {@sdkPlatformVersion}, including new features and changes in the framework
+API since the previous version.
+
+Near Field Communications (NFC)
+
+Android 2.3.3 provides improved and extended support for NFC, to allow
+applications to interact with more types of tags in new ways.
+
+A new, comprehensive set of APIs give applications read and write access
+to a wider range of standard tag technologies, including:
+
+
+- NFC-A (ISO 14443-3A)
+- NFC-B (ISO 14443-3B)
+- NFC-F (JIS 6319-4)
+- NFC-V (ISO 15693)
+- ISO-DEP (ISO 14443-4)
+- Mifare Classic
+- Mifare Ultralight
+- NFC Forum NDEF tags
+
+
+The platform also provides a limited peer-to-peer communication protocol
+and API. Foreground Activities can use the API to register an NDEF
+message that will get pushed to other NFC devices when they connect.
+
+Advanced tag dispatching now gives applications more control over how and
+when they are launched, when an NFC tag is discovered. Previously, the platform
+used a single-step intent dispatch to notify interested applications that a tag
+was discovered. The platform now uses a four-step process that enables the
+foreground application to take control of a tag event before it is passed to any
+other applications (android.nfc.NfcAdapter.enableForegroundDispatch()
).
+
+The new dispatch process also lets apps listen for specific tag content and
+tag technologies, based on two new intent actions —
+android.nfc.action.NDEF_DISCOVERED
and
+android.nfc.action.TECH_DISCOVERED
.
+
+The NFC API is available in the {@link android.nfc} and
+{@link android.nfc.tech} packages. The key classes are:
+
+
+- {@link android.nfc.NfcAdapter}, which represents the NFC hardware on the device.
+- {@link android.nfc.NdefMessage}, which represents an NDEF data message,
+the standard format in which "records" carrying data are transmitted between
+devices and tags. An NDEF message certain many NDEF records of different types.
+Applications can receive these messages from
+{@link android.nfc.NfcAdapter#ACTION_NDEF_DISCOVERED NDEF_DISCOVERED},
+{@link android.nfc.NfcAdapter#ACTION_TECH_DISCOVERED TECH_DISCOVERED}, or
+{@link android.nfc.NfcAdapter#ACTION_TAG_DISCOVERED TAG_DISCOVERED} Intents.
+- {@link android.nfc.NdefRecord}, delivered in an
+{@link android.nfc.NdefMessage}, which describes the type of data being shared
+and carries the data itself.
+- {@link android.nfc.Tag}, which represents a tag scanned by the device.
+Multiple types of tags are supported, based on the underlying tag
+technology.
+- {@link android.nfc.tech.TagTechnology}, an interface that gives applications
+access to tag properties and I/O operations based on the technologies present
+in the tag. For a full list of tag technologies supported in Android 2.3.3, see
+{@link android.nfc.tech}.
+
+
+NFC communication relies on wireless technology in the device hardware, and
+is not present in all Android devices. Android devices that do not support
+NFC will return a null object when
+{@link android.nfc.NfcAdapter#getDefaultAdapter(android.content.Context)
+getDefaultAdapter(Context)} is called, and
+context.getPackageManager().hasSystemFeature(PackageManager.FEATURE_NFC)
+will return false
. The NFC API is always present, however, regardless of
+underlying hardware support.
+
+To use the NFC API, applications must request permission from the user by
+declaring <uses-permission
+android:name="android.permission.NFC">
in their manifest files.
+
+Additionally, developers can request filtering on Android Market, such that
+their applications are not discoverable to users whose devices do not support
+NFC. To request filtering, add
+<uses-feature android:name="android.hardware.nfc"
+android:required="true">
to the application's manifest.
+
+To look at sample code for NFC, see
+NFCDemo app, filtering by tag technology, using foreground dispatch, and foreground NDEF push (P2P).
+
+Bluetooth
+
+Android 2.3.3 adds platform and API support for Bluetooth nonsecure socket
+connections. This lets applications communicate with simple devices that may not
+offer a UI for authentication. See
+{@link android.bluetooth.BluetoothDevice#createInsecureRfcommSocketToServiceRecord(java.util.UUID)} and
+{@link android.bluetooth.BluetoothAdapter#listenUsingInsecureRfcommWithServiceRecord(java.lang.String, java.util.UUID)}
+for more information.
+
+Graphics
+
+
+- A new {@link android.graphics.BitmapRegionDecoder} class lets applications
+decode a rectangle region from an image. The API is particularly useful when an
+original image is large and and the application only need parts of the image.
+
+- A new {@link
+android.graphics.BitmapFactory.Options#inPreferQualityOverSpeed} field in {@link
+android.graphics.BitmapFactory.Options} allows applications to use a more accurate
+but slightly slower IDCT method in JPEG decode. This in turn improves the
+quality of the reconstructed image.
+
+
+
+
+
+
+- A new {@link android.media.MediaMetadataRetriever} class provides a unified
+interface for retrieving frame and metadata from an input media file.
+- {@link android.media.MediaRecorder.AudioEncoder} and {@link
+android.media.MediaRecorder.OutputFormat} include new fields for specifying AMR
+Wideband and AAC formats.
+
+
+
+Speech recognition
+
+The speech-recognition API includes new constants to let you manage voice
+search results in new ways. Although the new constants are not needed for normal
+use of speech recognition, you could use them to offer a different view of voice
+search results in your application. For information, see {@link
+android.speech.RecognizerResultsIntent}.
+
+
+API Level
+
+The Android {@sdkPlatformVersion} platform delivers an updated version of
+the framework API. The Android {@sdkPlatformVersion} API
+is assigned an integer identifier —
+{@sdkPlatformApiLevel} — 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.
+
+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 android:minSdkVersion="{@sdkPlatformApiLevel}"
+attribute to the <uses-sdk>
element in the application's
+manifest. If your application is designed to run only on Android 2.3 and higher,
+declaring the attribute prevents the application from being installed on earlier
+versions of the platform.
+
+For more information about how to use API Level, see the API Levels document.
+
+Built-in Applications
+
+The system image included in the downloadable platform provides these
+built-in applications:
+
+
+
+
+
+- Browser
+- Calculator
+- Camera
+- Clock
+- Contacts
+- Cusom Locale
+- Dev Tools
+- Downloads
+- Email
+
+ |
+
+
+- Gallery
+- IMEs for Japanese, Chinese, and Latin text input
+- Messaging
+- Music
+- Phone
+- Search
+- Settings
+- Spare Parts (developer app)
+- Speech Recorder
+
+ |
+
+
+
+
+Locales
+
+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 language_country/region locale
+descriptor).
+
+
+
+
+
+- Arabic, Egypt (ar_EG)
+- Arabic, Israel (ar_IL)
+- Bulgarian, Bulgaria (bg_BG)
+- Catalan, Spain (ca_ES)
+- Czech, Czech Republic (cs_CZ)
+- Danish, Denmark(da_DK)
+- German, Austria (de_AT)
+- German, Switzerland (de_CH)
+- German, Germany (de_DE)
+- German, Liechtenstein (de_LI)
+- Greek, Greece (el_GR)
+- English, Australia (en_AU)
+- English, Canada (en_CA)
+- English, Britain (en_GB)
+- English, Ireland (en_IE)
+- English, India (en_IN)
+- English, New Zealand (en_NZ)
+- English, Singapore(en_SG)
+- English, US (en_US)
+- English, Zimbabwe (en_ZA)
+- Spanish (es_ES)
+- Spanish, US (es_US)
+- Finnish, Finland (fi_FI)
+- French, Belgium (fr_BE)
+- French, Canada (fr_CA)
+- French, Switzerland (fr_CH)
+- French, France (fr_FR)
+- Hebrew, Israel (he_IL)
+- Hindi, India (hi_IN)
+
+ |
+
+Croatian, Croatia (hr_HR)
+Hungarian, Hungary (hu_HU)
+Indonesian, Indonesia (id_ID)
+Italian, Switzerland (it_CH)
+Italian, Italy (it_IT)
+Japanese (ja_JP)
+Korean (ko_KR)
+Lithuanian, Lithuania (lt_LT)
+Latvian, Latvia (lv_LV)
+Norwegian-Bokmol, Norway(nb_NO)
+Dutch, Belgium (nl_BE)
+Dutch, Netherlands (nl_NL)
+Polish (pl_PL)
+Portuguese, Brazil (pt_BR)
+Portuguese, Portugal (pt_PT)
+Romanian, Romania (ro_RO)
+Russian (ru_RU)
+Slovak, Slovakia (sk_SK)
+Slovenian, Slovenia (sl_SI)
+Serbian (sr_RS)
+Swedish, Sweden (sv_SE)
+Thai, Thailand (th_TH)
+Tagalog, Philippines (tl_PH)
+Turkish, Turkey (tr_TR)
+Ukrainian, Ukraine (uk_UA)
+Vietnamese, Vietnam (vi_VN)
+Chinese, PRC (zh_CN)
+Chinese, Taiwan (zh_TW)
+ |
+
+
+
+Note: The Android platform may support more
+locales than are included in the SDK system image. All of the supported locales
+are available in the Android Open Source
+Project.
+
+Emulator Skins
+
+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:
+
+
+ -
+ QVGA (240x320, low density, small screen)
+
+ -
+ WQVGA400 (240x400, low density, normal screen)
+
+ -
+ WQVGA432 (240x432, low density, normal screen)
+
+ -
+ HVGA (320x480, medium density, normal screen)
+
+ -
+ WVGA800 (480x800, high density, normal screen)
+
+ -
+ WVGA854 (480x854 high density, normal screen)
+
+
+
+For more information about how to develop an application that displays
+and functions properly on all Android-powered devices, see Supporting Multiple
+Screens.
diff --git a/docs/html/sdk/sdk_toc.cs b/docs/html/sdk/sdk_toc.cs
index 9b67fee99668..2ba807686a3f 100644
--- a/docs/html/sdk/sdk_toc.cs
+++ b/docs/html/sdk/sdk_toc.cs
@@ -87,6 +87,13 @@ class="new">new!