A new package, {@link android.net.wifi.p2p}, contains all the APIs for performing peer-to-peer connections with Wi-Fi. The primary class you need to work with is {@link android.net.wifi.p2p.WifiP2pManager}, which you can acquire by calling {@link -android.app.Activity#getSystemService(java.lang.String) getSystemService(WIFI_P2P_SERVICE)}. -The {@link android.net.wifi.p2p.WifiP2pManager} includes APIs that allow you to:
+android.app.Activity#getSystemService getSystemService(WIFI_P2P_SERVICE)}. The {@link +android.net.wifi.p2p.WifiP2pManager} includes APIs that allow you to:Android now allows your app to display unique content on additional screens that are connected to the user’s device over either a wired connection or Wi-Fi. To create unique content for a secondary display, extend the {@link android.app.Presentation} -class and implement the {@link android.app.Dialog#onCreate onCreate()} callback. Within -{@link android.app.Dialog#onCreate onCreate()}, specify your UI for the secondary display -by calling {@link android.app.Dialog#setContentView setContentView()}. +class and implement the {@link android.app.Presentation#onCreate onCreate()} callback. Within +{@link android.app.Presentation#onCreate onCreate()}, specify your UI for the secondary display +by calling {@link android.app.Presentation#setContentView setContentView()}. As an extension of the {@link android.app.Dialog} class, the {@link android.app.Presentation} class provides the region in which your app can display a unique UI on the secondary display.
@@ -241,13 +241,13 @@ appear on the secondary display.To detect at runtime when a new display has been connected, create an instance of {@link android.media.MediaRouter.SimpleCallback} in which you implement the {@link -android.media.MediaRouter.Callback#onRoutePresentationDisplayChanged +android.media.MediaRouter.SimpleCallback#onRoutePresentationDisplayChanged onRoutePresentationDisplayChanged()} callback method, which the system will call when a new presentation display is connected. Then register the {@link android.media.MediaRouter.SimpleCallback} by passing it to {@link android.media.MediaRouter#addCallback MediaRouter.addCallback()} along with the {@link android.media.MediaRouter#ROUTE_TYPE_LIVE_VIDEO} route type. When you receive a call to -{@link android.media.MediaRouter.Callback#onRoutePresentationDisplayChanged +{@link android.media.MediaRouter.SimpleCallback#onRoutePresentationDisplayChanged onRoutePresentationDisplayChanged()}, simply call {@link android.media.MediaRouter#getSelectedRoute MediaRouter.getSelectedRoute()} as mentioned above.
@@ -262,7 +262,7 @@ applied to your application or activity. likely a different screen density. Because the screen characteristics may different, you should provide resources that are optimized specifically for such larger displays. If you need to request additional resources from your {@link -android.app.Presentation}, call {@link android.app.Dialog#getContext()}{@link +android.app.Presentation}, call {@link android.app.Presentation#getContext()}{@link android.content.Context#getResources .getResources()} to get the {@link android.content.res.Resources} object corresponding to the display. This provides the appropriate resources from your app that are best suited for the @@ -510,7 +510,7 @@ common operations for you such as:To use a script intrinsic, call the static create() method of each instrinsic
to create an instance of the script. You then call the available set()
methods of each script intrinsic to set any necessary inputs and options.
- Finally, call the {@link android.renderscript.Script#forEach forEach()}
+ Finally, call the {@link android.renderscript.ScriptC#forEach forEach()}
method to execute the script.
To track changes to inserts and updates, you can now include the {@link android.provider.ContactsContract.ContactsColumns#CONTACT_LAST_UPDATED_TIMESTAMP} parameter with your selection to query only the contacts that have changed since the last time you queried the provider.
-To track which contacts have been deleted, the new table {@link android.provider.ContactsContract.DeletedContacts} provides a log of contacts that have been deleted (but each contact deleted is held in this table for a limited time). Similar to {@link android.provider.ContactsContract.ContactsColumns#CONTACT_LAST_UPDATED_TIMESTAMP}, you can use the new selection parameter, {@link android.provider.ContactsContract.DeletedContactsColumns#CONTACT_DELETED_TIMESTAMP} to check which contacts have been deleted since the last time you queried the provider. The table also contains the constant {@link android.provider.ContactsContract.DeletedContacts#DAYS_KEPT_MILLISECONDS} containing the number of days (in milliseconds) that the log will be kept.
+To track which contacts have been deleted, the new table {@link android.provider.ContactsContract.DeletedContacts} provides a log of contacts that have been deleted (but each contact deleted is held in this table for a limited time). Similar to {@link android.provider.ContactsContract.ContactsColumns#CONTACT_LAST_UPDATED_TIMESTAMP}, you can use the new selection parameter, {@link android.provider.ContactsContract.DeletedContacts#CONTACT_DELETED_TIMESTAMP} to check which contacts have been deleted since the last time you queried the provider. The table also contains the constant {@link android.provider.ContactsContract.DeletedContacts#DAYS_KEPT_MILLISECONDS} containing the number of days (in milliseconds) that the log will be kept.
Additionally, the Contacts Provider now broadcasts the {@link android.provider.ContactsContract.Intents#CONTACTS_DATABASE_CREATED} action when the user diff --git a/docs/html/about/versions/marshmallow/android-6.0-changes.jd b/docs/html/about/versions/marshmallow/android-6.0-changes.jd index 65c976beb7b95..b44142e9842ab 100644 --- a/docs/html/about/versions/marshmallow/android-6.0-changes.jd +++ b/docs/html/about/versions/marshmallow/android-6.0-changes.jd @@ -280,7 +280,7 @@ change fixes a problem where Dalvik was checking access rules incorrectly in pre If your app uses the {@link java.lang.reflect.Constructor#newInstance(java.lang.Object...) newInstance()} method and you want to override access checks, call the -{@link java.lang.reflect.AccessibleObject#setAccessible(boolean) setAccessible()} method with the input +{@link java.lang.reflect.Constructor#setAccessible(boolean) setAccessible()} method with the input parameter set to {@code true}. If your app uses the v7 appcompat library or the v7 recyclerview library, diff --git a/docs/html/guide/components/activities.jd b/docs/html/guide/components/activities.jd index 94439248c920d..e757288424d81 100644 --- a/docs/html/guide/components/activities.jd +++ b/docs/html/guide/components/activities.jd @@ -624,8 +624,8 @@ android.app.Activity#onSaveInstanceState onSaveInstanceState()}.
before making the activity vulnerable to destruction. The system passes this method a {@link android.os.Bundle} in which you can save state information about the activity as name-value pairs, using methods such as {@link -android.os.BaseBundle#putString putString()} and {@link -android.os.BaseBundle#putInt putInt()}. Then, if the system kills your application +android.os.Bundle#putString putString()} and {@link +android.os.Bundle#putInt putInt()}. Then, if the system kills your application process and the user navigates back to your activity, the system recreates the activity and passes the {@link android.os.Bundle} to both {@link android.app.Activity#onCreate onCreate()} and {@link android.app.Activity#onRestoreInstanceState onRestoreInstanceState()}. Using either of these diff --git a/docs/html/guide/topics/manifest/meta-data-element.jd b/docs/html/guide/topics/manifest/meta-data-element.jd index 945b116dbe5a1..2d1bdfe59259c 100644 --- a/docs/html/guide/topics/manifest/meta-data-element.jd +++ b/docs/html/guide/topics/manifest/meta-data-element.jd @@ -60,7 +60,7 @@ Java-style naming convention — for example,If you query on a {@link
-android.provider.CalendarContract.SyncColumns#ACCOUNT_NAME
+android.provider.CalendarContract.Calendars#ACCOUNT_NAME
Calendars.ACCOUNT_NAME}, you must also include
-{@link android.provider.CalendarContract.SyncColumns#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}
+{@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE}
in the selection. That is because a given account is
only considered unique given both its ACCOUNT_NAME and its
ACCOUNT_TYPE. The ACCOUNT_TYPE is the string corresponding to the
diff --git a/docs/html/guide/topics/providers/contacts-provider.jd b/docs/html/guide/topics/providers/contacts-provider.jd
index ac855aa0ab272..2b145585ab837 100644
--- a/docs/html/guide/topics/providers/contacts-provider.jd
+++ b/docs/html/guide/topics/providers/contacts-provider.jd
@@ -329,13 +329,13 @@ page.title=Contacts Provider
_ID column of the raw contact for this data.
diff --git a/docs/html/guide/topics/search/search-dialog.jd b/docs/html/guide/topics/search/search-dialog.jd index 8278ab19ee611..4d6b4001e0c9e 100644 --- a/docs/html/guide/topics/search/search-dialog.jd +++ b/docs/html/guide/topics/search/search-dialog.jd @@ -699,7 +699,7 @@ public boolean onCreateOptionsMenu(Menu menu) { inflater.inflate(R.menu.options_menu, menu); // Get the SearchView and set the searchable configuration - SearchManager searchManager = (SearchManager) {@link android.app.Activity#getSystemService(java.lang.String) getSystemService()}(Context.SEARCH_SERVICE); + SearchManager searchManager = (SearchManager) {@link android.app.Activity#getSystemService getSystemService}(Context.SEARCH_SERVICE); SearchView searchView = (SearchView) menu.findItem(R.id.menu_search).getActionView(); // Assumes current activity is the searchable activity searchView.setSearchableInfo(searchManager.getSearchableInfo({@link android.app.Activity#getComponentName()})); diff --git a/docs/html/guide/topics/ui/accessibility/apps.jd b/docs/html/guide/topics/ui/accessibility/apps.jd index c415762693706..ab8c792cd24b6 100644 --- a/docs/html/guide/topics/ui/accessibility/apps.jd +++ b/docs/html/guide/topics/ui/accessibility/apps.jd @@ -298,7 +298,7 @@ then the {@link android.view.View#dispatchPopulateAccessibilityEvent dispatchPopulateAccessibilityEvent()} method for each child of this view. In order to support accessibility services on revisions of Android prior to 4.0 (API Level 14) you must override this method and populate {@link -android.view.accessibility.AccessibilityRecord#getText} with descriptive text for your custom +android.view.accessibility.AccessibilityEvent#getText} with descriptive text for your custom view, which is spoken by accessibility services, such as TalkBack.
Note: In Android 4.1 (API Level 16) and higher, the -{@link android.view.accessibility.AccessibilityRecord#getSource getSource()} method, +{@link android.view.accessibility.AccessibilityEvent#getSource getSource()} method, as well as {@link android.view.accessibility.AccessibilityNodeInfo#getChild AccessibilityNodeInfo.getChild()} and {@link android.view.accessibility.AccessibilityNodeInfo#getParent getParent()}, return only @@ -372,7 +372,7 @@ public class MyAccessibilityService extends AccessibilityService { service configuration file. When events are received by your service, it can then retrieve the {@link android.view.accessibility.AccessibilityNodeInfo} object from the event using - {@link android.view.accessibility.AccessibilityRecord#getSource getSource()}. + {@link android.view.accessibility.AccessibilityEvent#getSource getSource()}. With the {@link android.view.accessibility.AccessibilityNodeInfo} object, your service can then explore the view hierarchy to determine what action to take and then act for the user using {@link android.view.accessibility.AccessibilityNodeInfo#performAction performAction()}.
diff --git a/docs/html/guide/topics/ui/declaring-layout.jd b/docs/html/guide/topics/ui/declaring-layout.jd index ecdcfdc69ae16..bf0db576cf2eb 100755 --- a/docs/html/guide/topics/ui/declaring-layout.jd +++ b/docs/html/guide/topics/ui/declaring-layout.jd @@ -423,7 +423,7 @@ ArrayAdapter<String> adapter = new ArrayAdapter<String>(this,Then simply call -{@link android.widget.AdapterView#setAdapter setAdapter()} on your {@link android.widget.ListView}:
+{@link android.widget.ListView#setAdapter setAdapter()} on your {@link android.widget.ListView}:
ListView listView = (ListView) findViewById(R.id.listview);
listView.setAdapter(adapter);
diff --git a/docs/html/guide/topics/ui/dialogs.jd b/docs/html/guide/topics/ui/dialogs.jd
index 52cd1a03c38e8..7ab4ca552b4d5 100644
--- a/docs/html/guide/topics/ui/dialogs.jd
+++ b/docs/html/guide/topics/ui/dialogs.jd
@@ -643,7 +643,7 @@ android.support.v4.app.Fragment}.
or other {@link android.app.Dialog} objects to build the dialog in this case. If
you want the {@link android.support.v4.app.DialogFragment} to be
embeddable, you must define the dialog's UI in a layout, then load the layout in the
-{@link android.support.v4.app.Fragment#onCreateView
+{@link android.support.v4.app.DialogFragment#onCreateView
onCreateView()} callback.
Here's an example {@link android.support.v4.app.DialogFragment} that can appear as either a
diff --git a/docs/html/guide/topics/ui/layout/gridview.jd b/docs/html/guide/topics/ui/layout/gridview.jd
index 4ed6ff55efa31..13467ae17245b 100644
--- a/docs/html/guide/topics/ui/layout/gridview.jd
+++ b/docs/html/guide/topics/ui/layout/gridview.jd
@@ -81,7 +81,7 @@ public void onCreate(Bundle savedInstanceState) {
After the {@code main.xml} layout is set for the content view, the
{@link android.widget.GridView} is captured from the layout with {@link
android.app.Activity#findViewById(int)}. The {@link
-android.widget.AdapterView#setAdapter(T) setAdapter()} method then sets a custom adapter ({@code
+android.widget.GridView#setAdapter(T) setAdapter()} method then sets a custom adapter ({@code
ImageAdapter}) as the source for all items to be displayed in the grid. The {@code ImageAdapter} is
created in the next step.
To do something when an item in the grid is clicked, the {@link
@@ -170,7 +170,7 @@ the height and width for the View—this ensures that, no matter the size of
image is resized and cropped to fit in these dimensions, as appropriate.
That's it. Now when the user selects an item with a long-click, the system calls the {@link -android.view.ActionMode.Callback#onCreateActionMode onCreateActionMode()} +android.widget.AbsListView.MultiChoiceModeListener#onCreateActionMode onCreateActionMode()} method and displays the contextual action bar with the specified actions. While the contextual action bar is visible, users can select additional items.
diff --git a/docs/html/training/accessibility/service.jd b/docs/html/training/accessibility/service.jd index de00db76c4b34..9935c97ba61f4 100755 --- a/docs/html/training/accessibility/service.jd +++ b/docs/html/training/accessibility/service.jd @@ -174,7 +174,7 @@ android.accessibilityservice.AccessibilityService#onAccessibilityEvent} method. In that method, use {@link android.view.accessibility.AccessibilityEvent#getEventType} to determine the type of event, and {@link -android.view.accessibility.AccessibilityRecord#getContentDescription} to extract +android.view.accessibility.AccessibilityEvent#getContentDescription} to extract any label text associated with the view that fired the event.@@ -211,7 +211,7 @@ android:canRetrieveWindowContent="true"
Once that's done, get an {@link android.view.accessibility.AccessibilityNodeInfo} object using {@link -android.view.accessibility.AccessibilityRecord#getSource}. This call only +android.view.accessibility.AccessibilityEvent#getSource}. This call only returns an object if the window where the event originated is still the active window. If not, it will return null, so behave accordingly. The following example is a snippet of code that, when it receives an event, does diff --git a/docs/html/training/articles/perf-anr.jd b/docs/html/training/articles/perf-anr.jd index 88483545e2d9a..2eda4fa679cae 100644 --- a/docs/html/training/articles/perf-anr.jd +++ b/docs/html/training/articles/perf-anr.jd @@ -146,7 +146,7 @@ as the UI thread by default.
If you implement {@link java.lang.Thread} or {@link android.os.HandlerThread}, be sure that your UI thread does not block while waiting for the worker thread to -complete—do not call {@link java.lang.Object#wait Thread.wait()} or +complete—do not call {@link java.lang.Thread#wait Thread.wait()} or {@link java.lang.Thread#sleep Thread.sleep()}. Instead of blocking while waiting for a worker thread to complete, your main thread should provide a {@link android.os.Handler} for the other threads to post back to upon completion. diff --git a/docs/html/training/contacts-provider/display-contact-badge.jd b/docs/html/training/contacts-provider/display-contact-badge.jd index d286440998bb9..6c9616befe13f 100644 --- a/docs/html/training/contacts-provider/display-contact-badge.jd +++ b/docs/html/training/contacts-provider/display-contact-badge.jd @@ -113,10 +113,10 @@ trainingnavtop=true
For Android 3.0 (API level 11) and later, include the following columns in your projection:
The remainder of this lesson assumes that you've already loaded a @@ -187,14 +187,14 @@ trainingnavtop=true
Note: The - {@link android.provider.ContactsContract.ContactsColumns#PHOTO_THUMBNAIL_URI} column isn't available + {@link android.provider.ContactsContract.Contacts#PHOTO_THUMBNAIL_URI} column isn't available in platform versions prior to 3.0. For those versions, you must retrieve the URI from the {@link android.provider.ContactsContract.Contacts.Photo Contacts.Photo} subtable.
First, set up variables for accessing the {@link android.database.Cursor} containing the - {@link android.provider.BaseColumns#_ID Contacts._ID} and - {@link android.provider.ContactsContract.ContactsColumns#LOOKUP_KEY Contacts.LOOKUP_KEY} columns, as + {@link android.provider.ContactsContract.Contacts#_ID Contacts._ID} and + {@link android.provider.ContactsContract.Contacts#LOOKUP_KEY Contacts.LOOKUP_KEY} columns, as described previously:
diff --git a/docs/html/training/contacts-provider/modify-data.jd b/docs/html/training/contacts-provider/modify-data.jd
index e993c56337275..64853ef3a7b8e 100644
--- a/docs/html/training/contacts-provider/modify-data.jd
+++ b/docs/html/training/contacts-provider/modify-data.jd
@@ -196,8 +196,8 @@ intent.putExtra(Intents.Insert.EMAIL, mEmailAddress.getText())
Contacts.CONTENT_LOOKUP_URI}, call
{@link android.provider.ContactsContract.Contacts#getLookupUri
Contacts.getLookupUri(id, lookupkey)} with the contact's
- {@link android.provider.BaseColumns#_ID Contacts._ID} and
- {@link android.provider.ContactsContract.ContactsColumns#LOOKUP_KEY Contacts.LOOKUP_KEY} values as
+ {@link android.provider.ContactsContract.Contacts#_ID Contacts._ID} and
+ {@link android.provider.ContactsContract.Contacts#LOOKUP_KEY Contacts.LOOKUP_KEY} values as
arguments.
diff --git a/docs/html/training/contacts-provider/retrieve-details.jd b/docs/html/training/contacts-provider/retrieve-details.jd
index a463b751de5f9..0de3b6750be46 100644
--- a/docs/html/training/contacts-provider/retrieve-details.jd
+++ b/docs/html/training/contacts-provider/retrieve-details.jd
@@ -55,11 +55,11 @@ trainingnavtop=true
To retrieve all the details for a contact, search the
{@link android.provider.ContactsContract.Data} table for any rows that contain the contact's
- {@link android.provider.ContactsContract.ContactsColumns#LOOKUP_KEY}. This column is available in
+ {@link android.provider.ContactsContract.Data#LOOKUP_KEY}. This column is available in
the {@link android.provider.ContactsContract.Data} table, because the Contacts
Provider makes an implicit join between the {@link android.provider.ContactsContract.Contacts}
table and the {@link android.provider.ContactsContract.Data} table. The
- {@link android.provider.ContactsContract.ContactsColumns#LOOKUP_KEY} column is described
+ {@link android.provider.ContactsContract.Contacts#LOOKUP_KEY} column is described
in more detail in the Retrieving Contact Names lesson.
@@ -85,9 +85,9 @@ trainingnavtop=true
the data is in different columns depending on the data type.
To ensure you get all the possible columns for all possible data types, you need to add all the
column names to your projection. Always retrieve
- {@link android.provider.BaseColumns#_ID Data._ID} if you're binding the result
+ {@link android.provider.ContactsContract.Data#_ID Data._ID} if you're binding the result
{@link android.database.Cursor} to a {@link android.widget.ListView}; otherwise, the binding
- won't work. Also retrieve {@link android.provider.ContactsContract.DataColumns#MIMETYPE Data.MIMETYPE}
+ won't work. Also retrieve {@link android.provider.ContactsContract.Data#MIMETYPE Data.MIMETYPE}
so you can identify the data type of each row you retrieve. For example:
@@ -128,7 +128,7 @@ trainingnavtop=true
Define a constant for your selection clause, an array to hold selection arguments, and a
variable to hold the selection value. Use
- the {@link android.provider.ContactsContract.ContactsColumns#LOOKUP_KEY Contacts.LOOKUP_KEY} column to
+ the {@link android.provider.ContactsContract.Contacts#LOOKUP_KEY Contacts.LOOKUP_KEY} column to
find the contact. For example:
@@ -153,7 +153,7 @@ trainingnavtop=true
Define the sort order you want in the resulting {@link android.database.Cursor}. To
keep all rows for a particular data type together, sort by
- {@link android.provider.ContactsContract.DataColumns#MIMETYPE Data.MIMETYPE}. This query argument
+ {@link android.provider.ContactsContract.Data#MIMETYPE Data.MIMETYPE}. This query argument
groups all email rows together, all phone rows together, and so forth. For example:
@@ -299,7 +299,7 @@ public class DetailsFragment extends Fragment implements
Define a search text expression that retrieves rows for a specific contact's
- {@link android.provider.ContactsContract.ContactsColumns#LOOKUP_KEY} and the
- {@link android.provider.ContactsContract.DataColumns#MIMETYPE Data.MIMETYPE} of the details you
- want. Enclose the {@link android.provider.ContactsContract.DataColumns#MIMETYPE MIMETYPE} value in
+ {@link android.provider.ContactsContract.Data#LOOKUP_KEY} and the
+ {@link android.provider.ContactsContract.Data#MIMETYPE Data.MIMETYPE} of the details you
+ want. Enclose the {@link android.provider.ContactsContract.Data#MIMETYPE MIMETYPE} value in
single quotes by concatenating a "'" (single-quote) character to the start and end
of the constant; otherwise, the provider interprets the constant as a variable name rather
than as a string value. You don't need to use a placeholder for this value, because you're
@@ -368,10 +368,10 @@ public class DetailsFragment extends Fragment implements
Define a sort order for the returned {@link android.database.Cursor}. Since you're retrieving a - specific data type, omit the sort on {@link android.provider.ContactsContract.DataColumns#MIMETYPE}. + specific data type, omit the sort on {@link android.provider.ContactsContract.Data#MIMETYPE}. Instead, if the type of detail data you're searching includes a subtype, sort on it. For example, for email data you can sort on - {@link android.provider.ContactsContract.CommonDataKinds.CommonColumns#TYPE Email.TYPE}: + {@link android.provider.ContactsContract.CommonDataKinds.Email#TYPE Email.TYPE}:
private static final String SORT_ORDER = Email.TYPE + " ASC ";
diff --git a/docs/html/training/contacts-provider/retrieve-names.jd b/docs/html/training/contacts-provider/retrieve-names.jd
index 7d70ceb2f4df5..49d6e955536c9 100755
--- a/docs/html/training/contacts-provider/retrieve-names.jd
+++ b/docs/html/training/contacts-provider/retrieve-names.jd
@@ -227,7 +227,7 @@ public class ContactsFragment extends Fragment implements
Note: Since
- {@link android.provider.ContactsContract.ContactNameColumns#DISPLAY_NAME_PRIMARY
+ {@link android.provider.ContactsContract.Contacts#DISPLAY_NAME_PRIMARY
Contacts.DISPLAY_NAME_PRIMARY} requires Android 3.0 (API version 11) or later, setting your
app's minSdkVersion to 10 or below generates an Android Lint warning in
Android Studio. To turn off this warning, add the annotation
@@ -261,7 +261,7 @@ public class ContactsFragment extends Fragment implements
that displays the contacts, you need to call {@link android.app.Activity#findViewById
Activity.findViewById()} using the parent activity of the
{@link android.support.v4.app.Fragment}. Use the {@link android.content.Context} of the
- parent activity when you call {@link android.widget.AdapterView#setAdapter setAdapter()}.
+ parent activity when you call {@link android.widget.ListView#setAdapter setAdapter()}.
For example:
@@ -293,7 +293,7 @@ public class ContactsFragment extends Fragment implementsTo continue setting up the listener, bind it to the {@link android.widget.ListView} by - calling the method {@link android.widget.AdapterView#setOnItemClickListener + calling the method {@link android.widget.ListView#setOnItemClickListener setOnItemClickListener()} in {@link android.support.v4.app.Fragment#onActivityCreated onActivityCreated()}. For example:
@@ -318,15 +318,15 @@ public class ContactsFragment extends Fragment implements the {@link android.widget.ListView} displays the contact's display name, which contains the main form of the contact's name. In Android 3.0 (API version 11) and later, the name of this column is - {@link android.provider.ContactsContract.ContactNameColumns#DISPLAY_NAME_PRIMARY + {@link android.provider.ContactsContract.Contacts#DISPLAY_NAME_PRIMARY Contacts.DISPLAY_NAME_PRIMARY}; in versions previous to that, its name is - {@link android.provider.ContactsContract.ContactsColumns#DISPLAY_NAME Contacts.DISPLAY_NAME}. + {@link android.provider.ContactsContract.Contacts#DISPLAY_NAME Contacts.DISPLAY_NAME}.- The column {@link android.provider.BaseColumns#_ID Contacts._ID} is used by the + The column {@link android.provider.ContactsContract.Contacts#_ID Contacts._ID} is used by the {@link android.support.v4.widget.SimpleCursorAdapter} binding process. - {@link android.provider.BaseColumns#_ID Contacts._ID} and - {@link android.provider.ContactsContract.ContactsColumns#LOOKUP_KEY} are used together to + {@link android.provider.ContactsContract.Contacts#_ID Contacts._ID} and + {@link android.provider.ContactsContract.Contacts#LOOKUP_KEY} are used together to construct a content URI for the contact the user selects.
@@ -635,7 +635,7 @@ public class ContactsFragment extends Fragment implements
This lesson shows you how to listen for touch events to let users rotate an OpenGL ES object.
@@ -44,7 +44,7 @@ android.view.View#onTouchEvent onTouchEvent()} to listen for touch events.In order to make your OpenGL ES application respond to touch events, you must implement the -{@link android.view.View#onTouchEvent onTouchEvent()} method in your +{@link android.opengl.GLSurfaceView#onTouchEvent onTouchEvent()} method in your {@link android.opengl.GLSurfaceView} class. The example implementation below shows how to listen for {@link android.view.MotionEvent#ACTION_MOVE MotionEvent.ACTION_MOVE} events and translate them to an angle of rotation for a shape.
diff --git a/docs/html/training/implementing-navigation/nav-drawer.jd b/docs/html/training/implementing-navigation/nav-drawer.jd index abc79b6499266..8aebd4b091d9e 100644 --- a/docs/html/training/implementing-navigation/nav-drawer.jd +++ b/docs/html/training/implementing-navigation/nav-drawer.jd @@ -148,7 +148,7 @@ public class MainActivity extends Activity { } -This code also calls {@link android.widget.AdapterView#setOnItemClickListener +
This code also calls {@link android.widget.ListView#setOnItemClickListener setOnItemClickListener()} to receive click events in the navigation drawer's list. The next section shows how to implement this interface and change the content view when the user selects an item.
@@ -160,7 +160,7 @@ and change the content view when the user selects an item.When the user selects an item in the drawer's list, the system calls {@link android.widget.AdapterView.OnItemClickListener#onItemClick onItemClick()} on the {@link android.widget.AdapterView.OnItemClickListener OnItemClickListener} given to -{@link android.widget.AdapterView#setOnItemClickListener setOnItemClickListener()}.
+{@link android.widget.ListView#setOnItemClickListener setOnItemClickListener()}.What you do in the {@link android.widget.AdapterView.OnItemClickListener#onItemClick onItemClick()} method diff --git a/docs/html/training/notify-user/build-notification.jd b/docs/html/training/notify-user/build-notification.jd index 7df2787ea5184..baa10748c4ec4 100644 --- a/docs/html/training/notify-user/build-notification.jd +++ b/docs/html/training/notify-user/build-notification.jd @@ -134,8 +134,8 @@ mBuilder.setContentIntent(resultPendingIntent);
To create a notification with the support library, you create an instance of {@link android.support.v4.app.NotificationCompat.Builder} and issue the notification by -passing it to {@link android.support.v4.app.NotificationManagerCompat#notify(int, android.app.Notification) notify()}. For example: +passing it to {@link android.support.v4.app.NotificationManagerCompat#notify notify()}. For example:
diff --git a/docs/html/training/wearables/notifications/stacks.jd b/docs/html/training/wearables/notifications/stacks.jd index c3f43a7f6eb07..8056fc8ad53de 100644 --- a/docs/html/training/wearables/notifications/stacks.jd +++ b/docs/html/training/wearables/notifications/stacks.jd @@ -37,7 +37,7 @@ possible while allowing you to still provide only one summary notification on thTo create a stack, call {@link android.support.v4.app.NotificationCompat.Builder#setGroup setGroup()} for each notification you want in the stack and specify a -group key. Then call {@link android.support.v4.app.NotificationManagerCompat#notify(int, android.app.Notification) notify()} +group key. Then call {@link android.support.v4.app.NotificationManagerCompat#notify notify()} to send it to the wearable.
@@ -59,7 +59,7 @@ notificationManager.notify(notificationId1, notif);Later on, when you create another notification, specify the same group key. When you call -{@link android.support.v4.app.NotificationManagerCompat#notify(int, android.app.Notification) notify()}, +{@link android.support.v4.app.NotificationManagerCompat#notify notify()}, this notification appears in the same stack as the previous notification, instead of as a new card:
diff --git a/docs/html/work/managed-configurations.jd b/docs/html/work/managed-configurations.jd index 76ca82fca4ffa..6de4d8ba75894 100644 --- a/docs/html/work/managed-configurations.jd +++ b/docs/html/work/managed-configurations.jd @@ -349,7 +349,7 @@ enterprise administrator to:To get a {@link android.content.RestrictionsManager} object, get the current activity with {@link android.app.Fragment#getActivity getActivity()}, then - call that activity's {@link android.app.Activity#getSystemService(java.lang.String) + call that activity's {@link android.app.Activity#getSystemService Activity.getSystemService()} method:
@@ -399,9 +399,9 @@ enterprise administrator to:String, andString[]. Once you have the managed configurations {@link android.os.Bundle}, you can check the current configuration settings with the standard {@link android.os.Bundle} methods for - those data types, such as {@link android.os.BaseBundle#getBoolean getBoolean()} + those data types, such as {@link android.os.Bundle#getBoolean getBoolean()} or - {@link android.os.BaseBundle#getString getString()}. + {@link android.os.Bundle#getString getString()}.