page.title=Android 4.0.3 APIs excludeFromSuggestions=true sdk.platform.version=4.0.3 sdk.platform.apiLevel=15 @jd:body
API Level: {@sdkPlatformApiLevel}
Android {@sdkPlatformVersion} ({@link android.os.Build.VERSION_CODES#ICE_CREAM_SANDWICH_MR1}) is an incremental release of the Android 4.x (Ice Cream Sandwich) platform family. This release includes new features for users and developers, API changes, and various bug fixes.
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. To get started developing or testing against Android {@sdkPlatformVersion}, use the Android SDK Manager to download the platform into your SDK.
The sections below provide a technical overview of new APIs in Android 4.0.3.
Applications that use social stream data such as status updates and check-ins can now sync that data with each of the user’s contacts, providing items in a stream along with photos for each.
The database table that contains an individual contact’s social stream is defined by android.provider.ContactsContract.StreamItems, the Uri for which is nested within the {@link android.provider.ContactsContract.RawContacts} directory to which the stream items belong. Each social stream table includes several columns for metadata about each stream item, such as an icon representing the source (an avatar), a label for the item, the primary text content, comments about the item (such as responses from other people), and more. Photos associated with a stream are stored in another table, defined by android.provider.ContactsContract.StreamItemPhotos, which is available as a sub-directory of the android.provider.ContactsContract.StreamItems Uri.
See android.provider.ContactsContract.StreamItems and android.provider.ContactsContract.StreamItemPhotos for more information.
To read or write social stream items for a contact, an application must
request permission from the user by declaring <uses-permission
android:name="android.permission.READ_SOCIAL_STREAM">
and/or <uses-permission
android:name="android.permission.WRITE_SOCIAL_STREAM">
in their manifest files.
Starting from Android 4.0, home screen widgets should no longer include their own padding. Instead, the system now automatically adds padding for each widget, based the characteristics of the current screen. This leads to a more uniform, consistent presentation of widgets in a grid. To assist applications that host home screen widgets, the platform provides a new method {@link android.appwidget.AppWidgetHostView#getDefaultPaddingForWidget(android.content.Context, android.content.ComponentName, android.graphics.Rect) getDefaultPaddingForWidget()}. Applications can call this method to get the system-defined padding and account for it when computing the number of cells to allocate to the widget.
Apps connected to the spell-checker can use the {@link android.view.textservice.SuggestionsInfo#RESULT_ATTR_HAS_RECOMMENDED_SUGGESTIONS} flag in combination with other suggestion attributes, as well as the {@link android.view.textservice.SuggestionsInfo#getSuggestionsAttributes()} and {@link android.view.textservice.SuggestionsInfo#getSuggestionsCount()} methods, to determine whether to mark input words as typos and offer suggestions.
New public methods {@link android.bluetooth.BluetoothDevice#fetchUuidsWithSdp()} and {@link android.bluetooth.BluetoothDevice#getUuids()} let apps determine the features (UUIDs) supported by a remote device. In the case of {@link android.bluetooth.BluetoothDevice#fetchUuidsWithSdp()}, the system performs a service discovery on the remote device to get the UUIDs supported, then broadcasts the result in an {@link android.bluetooth.BluetoothDevice#ACTION_UUID} intent.
New methods {@link android.app.Fragment#setUserVisibleHint(boolean) setUserVisibleHint()} and {@link android.app.Fragment#getUserVisibleHint() getUserVisibleHint()} allow a fragment to set a hint of whether or not it is currently user-visible. The system defers the start of fragments that are not user-visible until the loaders for visible fragments have run. The visibility hint is "true" by default.
The {@link android.database.CrossProcessCursorWrapper} class fixes common performance issues and bugs that applications have encountered when implementing content providers.
Adds new categories for targeting common types of applications on the device, such as {@link android.content.Intent#CATEGORY_APP_BROWSER}, {@link android.content.Intent#CATEGORY_APP_CALENDAR}, {@link android.content.Intent#CATEGORY_APP_MAPS}, and more.
The following are new permissions:
For a detailed view of all API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), see the API Differences Report.
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 an Android platform that supports API level {@sdkPlatformApiLevel} or
higher. Depending on your needs, you might also need to add an
android:minSdkVersion="{@sdkPlatformApiLevel}"
attribute to the
{@code <uses-sdk>}
element.
For more information, see the API Levels document.