From ed5ff51b2ca7c051e2719dfc8a8a083e6208848e Mon Sep 17 00:00:00 2001
From: Bart Sears
The database table that contains an individual contact’s social stream is -defined by android.provider.ContactsContract.StreamItems, the Uri for +defined by {@link 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 +{@link android.provider.ContactsContract.StreamItemPhotos}, which is available +as a sub-directory of the {@link android.provider.ContactsContract.StreamItems} Uri.
-See android.provider.ContactsContract.StreamItems and -android.provider.ContactsContract.StreamItemPhotos for more information.
+See {@link android.provider.ContactsContract.StreamItems} and +{@link 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 The following are new permissions:<uses-permission
@@ -272,8 +272,8 @@ let you check and manage video stabilization for a {@link android.hardware.Camer
-
diff --git a/docs/html/about/versions/android-4.0.jd b/docs/html/about/versions/android-4.0.jd
index cc1d1c70d9df..6c4ccb4c4958 100644
--- a/docs/html/about/versions/android-4.0.jd
+++ b/docs/html/about/versions/android-4.0.jd
@@ -108,9 +108,9 @@ android.provider.ContactsContract.RawContacts} Uri; instead, you must add a prof
the table at {@link android.provider.ContactsContract.Profile#CONTENT_RAW_CONTACTS_URI}. Raw
contacts in this table are then aggregated into the single user-visible profile labeled "Me".
Adding a new raw contact for the profile requires the -android.Manifest.permission#WRITE_PROFILE permission. Likewise, in order to read from the profile -table, you must request the android.Manifest.permission#READ_PROFILE permission. However, +
Adding a new raw contact for the profile requires the {@link +android.Manifest.permission#WRITE_PROFILE} permission. Likewise, in order to read from the profile +table, you must request the {@link android.Manifest.permission#READ_PROFILE} permission. However, most apps should not need to read the user profile, even when contributing data to the profile. Reading the user profile is a sensitive permission and you should expect users to be skeptical of apps that request it.
@@ -1638,9 +1638,9 @@ messages to the device. android.service.textservice.SpellCheckerService} must require this permission for itself.