From cd1b08e1e239269f7d0d48119505313f52d3dd5a Mon Sep 17 00:00:00 2001 From: Scott Main Date: Tue, 27 Dec 2011 16:22:27 -0800 Subject: docs: fix broken links in .jd docs Change-Id: Ide8bb1a11a704d6821b52a0128b24a76de2e707f --- docs/html/guide/appendix/api-levels.jd | 2 +- docs/html/guide/developing/device.jd | 6 +- docs/html/guide/developing/devices/emulator.jd | 6 +- docs/html/guide/practices/screens-support-1.5.jd | 2 +- docs/html/guide/practices/security.jd | 103 +++++++++------------ docs/html/guide/practices/tablets-and-handsets.jd | 2 +- docs/html/guide/publishing/preparing.jd | 4 +- docs/html/guide/publishing/publishing_overview.jd | 2 +- docs/html/guide/topics/appwidgets/index.jd | 14 +-- .../html/guide/topics/manifest/activity-element.jd | 2 +- .../guide/topics/manifest/application-element.jd | 4 +- docs/html/guide/topics/media/mediaplayer.jd | 2 +- docs/html/guide/topics/nfc/nfc.jd | 6 +- docs/html/guide/topics/renderscript/index.jd | 2 +- .../guide/topics/resources/animation-resource.jd | 2 +- docs/html/guide/topics/sensors/sensors_motion.jd | 2 +- docs/html/guide/topics/ui/actionbar.jd | 6 +- docs/html/guide/topics/usb/accessory.jd | 5 +- docs/html/guide/topics/usb/adk.jd | 2 +- docs/html/guide/topics/wireless/bluetooth.jd | 5 +- docs/html/sdk/RELEASENOTES.jd | 4 +- docs/html/sdk/android-1.1.jd | 2 +- docs/html/sdk/android-3.0.jd | 6 +- docs/html/sdk/android-3.1.jd | 9 +- docs/html/sdk/android-4.0.jd | 6 +- docs/html/training/id-auth/authenticate.jd | 4 +- .../monitoring-device-state/manifest-receivers.jd | 2 +- 27 files changed, 98 insertions(+), 114 deletions(-) diff --git a/docs/html/guide/appendix/api-levels.jd b/docs/html/guide/appendix/api-levels.jd index 7d119ca78141..cc98f8fe8df7 100644 --- a/docs/html/guide/appendix/api-levels.jd +++ b/docs/html/guide/appendix/api-levels.jd @@ -154,7 +154,7 @@ Highlights 2 {@link android.os.Build.VERSION_CODES#BASE_1_1} - Android 1.0 + Android 1.0 1 {@link android.os.Build.VERSION_CODES#BASE} diff --git a/docs/html/guide/developing/device.jd b/docs/html/guide/developing/device.jd index 76b2516f9817..48de46652173 100644 --- a/docs/html/guide/developing/device.jd +++ b/docs/html/guide/developing/device.jd @@ -79,10 +79,8 @@ located in Settings > Developer options).

OEM USB Drivers document.
  • If you're developing on Mac OS X, it just works. Skip this step.
    • -
  • If you're developing on Ubuntu Linux, you need to add a -udev -rules file that contains a USB configuration for each type of device +
  • If you're developing on Ubuntu Linux, you need to add a +udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see -help-disk-images.

    Enable the root shell (as in -shell and specify the QEMU character device to use for communication with the shell. <device> must be a QEMU device type. See the documentation for '-serial dev' at -     http://www.bellard.org/qemu/qemu-doc.html#SEC10 + http://wiki.qemu.org/download/qemu-doc.html for a list of device types.

    Here are some examples:

    @@ -619,7 +619,7 @@ scale in direct relationship with <delay> values.

    Use this command to emulate an NMEA-compatible GPS unit connected to an external character device or socket. The format of <device> must be QEMU-specific serial device specification. See the documentation for 'serial -dev' at - http://www.bellard.org/qemu/qemu-doc.html#SEC10. + http://wiki.qemu.org/download/qemu-doc.html. @@ -638,7 +638,7 @@ scale in direct relationship with <delay> values.

    Redirect radio mode to the specified character device. The format of <device> must be QEMU-specific serial device specification. See the documentation for 'serial -dev' at -http://www.bellard.org/qemu/qemu-doc.html#SEC10. +http://wiki.qemu.org/download/qemu-doc.html. diff --git a/docs/html/guide/practices/screens-support-1.5.jd b/docs/html/guide/practices/screens-support-1.5.jd index 9f033b4d2b93..4c6fb99f9397 100644 --- a/docs/html/guide/practices/screens-support-1.5.jd +++ b/docs/html/guide/practices/screens-support-1.5.jd @@ -46,7 +46,7 @@ android:targetSdkVersion} set to {@code "4"} or higher, then this document i default, an application written for Android 1.5 or below that does not set the {@code android:targetSdkVersion} set to {@code "4"} or higher runs in screen compatibility mode when on a device with a screen larger than +href="screen-compat-mode.html">screen compatibility mode when on a device with a screen larger than the normal screen size (basically, the system displays the application in a small window that is roughly the size of the normal screen size).

    diff --git a/docs/html/guide/practices/security.jd b/docs/html/guide/practices/security.jd index 476c3013c6a5..eeaac44e3940 100644 --- a/docs/html/guide/practices/security.jd +++ b/docs/html/guide/practices/security.jd @@ -126,8 +126,8 @@ applications.

    Use of world writable or world readable files for IPC is discouraged because it does not provide +href="{@docRoot}reference/android/content/Context.html#MODE_WORLD_READABLE">world +readable files for IPC is discouraged because it does not provide the ability to limit data access to particular applications, nor does it provide any control on data format. As an alternative, you might consider using a ContentProvider which provides read and write permissions, and can make @@ -199,10 +199,10 @@ ContentProvider.

    ContentProviders can also provide more granular access by declaring the grantUriPermissions element and using the FLAG_GRANT_READ_URI_PERMISSION and FLAG_GRANT_WRITE_URI_PERMISSION flags in the Intent object +href="{@docRoot}reference/android/content/Intent.html#FLAG_GRANT_READ_URI_PERMISSION">FLAG_GRANT_READ_URI_PERMISSION +and FLAG_GRANT_WRITE_URI_PERMISSION +flags in the Intent object that activates the component. The scope of these permissions can be further limited by the @@ -211,14 +211,9 @@ grant-uri-permission element.

    When accessing a ContentProvider, use parameterized query methods such as -query(), update(), and delete() to avoid +query(), update(), and delete() to avoid potential SQL Injection from untrusted data. Note that using parameterized methods is not sufficient if the selection is built by concatenating user data @@ -249,8 +244,9 @@ href="{@docRoot}reference/android/R.styleable.html#AndroidManifestActivity"> Activities, and Services are all declared in the application manifest. If your IPC mechanism is -not intended for use by other applications, set the android:exported property -to false. This is useful for applications that consist of multiple processes +not intended for use by other applications, set the {@code android:exported} +property to false. This is useful for applications that consist of multiple processes within the same UID, or if you decide late in development that you do not actually want to expose functionality as IPC but you don’t want to rewrite the code.

    @@ -276,11 +272,10 @@ activity.

    Intents are the preferred mechanism for asynchronous IPC in Android. Depending on your application requirements, you might use sendBroadcast(), sendOrderedBroadcast(), or -direct an intent to a specific application component.

    +href="{@docRoot}reference/android/content/Context.html#sendBroadcast(android.content.Intent)">sendBroadcast(), +sendOrderedBroadcast(), +or direct an intent to a specific application component.

    Note that ordered broadcasts can be “consumed” by a recipient, so they may not be delivered to all applications. If you are sending an Intent where @@ -311,14 +306,13 @@ and/or access controls on a specific binder interface, those controls must be explicitly added as code in the interface.

    If providing an interface that does require access controls, use checkCallingPermission() to verify whether the +href="{@docRoot}reference/android/content/Context.html#checkCallingPermission(java.lang.String)">checkCallingPermission() +to verify whether the caller of the Binder has a required permission. This is especially important before accessing a Service on behalf of the caller, as the identify of your application is passed to other interfaces. If invoking an interface provided by a Service, the bindService() +href="{@docRoot}reference/android/content/Context.html#bindService(android.content.Intent,%20android.content.ServiceConnection,%20int)">bindService() invocation may fail if you do not have permission to access the given Service. If calling an interface provided locally by your own application, it may be useful to use the

    By default, receivers are exported and can be invoked by any other application. If your +href="{@docRoot}reference/android/content/BroadcastReceiver.html"> BroadcastReceivers is intended for use by other applications, you may want to apply security permissions to receivers using the +href="{@docRoot}guide/topics/manifest/receiver-element.html"> <receiver> element within the application manifest. This will prevent applications without appropriate permissions from sending an intent to the +href="{@docRoot}reference/android/content/BroadcastReceiver.html"> BroadcastReceivers.

    Using Services

    @@ -349,19 +343,21 @@ use. Each service class must have a corresponding declaration in its package's AndroidManifest.xml.

    By default, Services are exported and can be invoked by any other -application. Services can be protected using the android:permission attribute +application. Services can be protected using the {@code android:permission} +attribute within the manifest’s +href="{@docRoot}guide/topics/manifest/service-element.html"> <service> tag. By doing so, other applications will need to declare a corresponding <uses-permission> element in their own manifest to be +href="{@docRoot}guide/topics/manifest/uses-permission-element.html"><uses-permission> + element in their own manifest to be able to start, stop, or bind to the service.

    A Service can protect individual IPC calls into it with permissions, by calling checkCallingPermission()before executing +href="{@docRoot}reference/android/content/Context.html#checkCallingPermission(java.lang.String)">checkCallingPermission() +before executing the implementation of that call. We generally recommend using the declarative permissions in the manifest, since those are less prone to oversight.

    @@ -376,9 +372,9 @@ Service to handle IPC, since this modular approach reduces the risk of exposing functionality that is not intended for use by other applications.

    If you do expose an Activity for purposes of IPC, the android:permission attribute in the +href="{@docRoot}guide/topics/manifest/activity-element.html#prmsn">android:permission +attribute in the <activity> declaration in the application manifest can be used to restrict access to only those applications which have the stated permissions.

    @@ -432,8 +428,8 @@ rkeley.edu/~afelt/felt_usenixsec2011.pdf

    Generally, you should strive to create as few permissions as possible while satisfying your security requirements. Creating a new permission is relatively uncommon for most applications, since -system-defined permissions cover many situations. Where appropriate, +href="{@docRoot}reference/android/Manifest.permission.html">system-defined +permissions cover many situations. Where appropriate, perform access checks using existing permissions.

    If you must create a new permission, consider whether you can accomplish @@ -560,17 +556,14 @@ href="{@docRoot}reference/android/webkit/WebView.html">WebView does not execute JavaScript so cross-site-scripting is not possible.

    Use addJavaScriptInterface() with +href="{@docRoot}reference/android/webkit/WebView.html#addJavascriptInterface(java.lang.Object,%20java.lang.String)">addJavaScriptInterface() with particular care because it allows JavaScript to invoke operations that are normally reserved for Android applications. Only expose addJavaScriptInterface() to +href="{@docRoot}reference/android/webkit/WebView.html#addJavascriptInterface(java.lang.Object,%20java.lang.String)">addJavaScriptInterface() to sources from which all input is trustworthy. If untrusted input is allowed, untrusted JavaScript may be able to invoke Android methods. In general, we recommend only exposing addJavaScriptInterface() to +href="{@docRoot}reference/android/webkit/WebView.html#addJavascriptInterface(java.lang.Object,%20java.lang.String)">addJavaScriptInterface() to JavaScript that is contained within your application APK.

    Do not trust information downloaded over HTTP, use HTTPS instead. Even if @@ -578,13 +571,11 @@ you are connecting only to a single website that you trust or control, HTTP is subject to MiTM attacks and interception of data. Sensitive capabilities using addJavaScriptInterface() should +href="{@docRoot}reference/android/webkit/WebView.html#addJavascriptInterface(java.lang.Object,%20java.lang.String)">addJavaScriptInterface() should not ever be exposed to unverified script downloaded over HTTP. Note that even with the use of HTTPS, addJavaScriptInterface() +href="{@docRoot}reference/android/webkit/WebView.html#addJavascriptInterface(java.lang.Object,%20java.lang.String)">addJavaScriptInterface() increases the attack surface of your application to include the server infrastructure and all CAs trusted by the Android-powered device.

    @@ -683,8 +674,7 @@ discussed in the Requesting Permissions section.

    If a GUID is required, create a large, unique number and store it. Do not use phone identifiers such as the phone number or IMEI which may be associated with personal information. This topic is discussed in more detail in the Android Developer Blog.

    +href="http://android-developers.blogspot.com/2011/03/identifying-app-installations.html">Android Developer Blog.

    Application developers should be careful writing to on-device logs. In Android, logs are a shared resource, and are available @@ -724,9 +714,8 @@ credentials to the wrong application.

    If credentials are to be used only by applications that you create, then you can verify the application which accesses the -AccountManager using checkSignature(). +AccountManager using checkSignature(). Alternatively, if only one application will use the credential, you might use a KeyStore for @@ -756,15 +745,15 @@ RSA provided in the Cipher class.

    Use a secure random number generator ( - + SecureRandom) to initialize any cryptographic keys ( +href="{@docRoot}reference/javax/crypto/KeyGenerator.html"> KeyGenerator). Use of a key that is not generated with a secure random number generator significantly weakens the strength of the algorithm, and may allow offline attacks.

    If you need to store a key for repeated use, use a mechanism like KeyStore that +href="{@docRoot}reference/java/security/KeyStore.html">KeyStore that provides a mechanism for long term storage and retrieval of cryptographic keys.

    diff --git a/docs/html/guide/practices/tablets-and-handsets.jd b/docs/html/guide/practices/tablets-and-handsets.jd index dc35801ea78a..3f4aaa95a8ab 100644 --- a/docs/html/guide/practices/tablets-and-handsets.jd +++ b/docs/html/guide/practices/tablets-and-handsets.jd @@ -481,7 +481,7 @@ href="{@docRoot}guide/topics/ui/actionbar.html#Home">Action Bar developer gu information in each list item based on the available space. That is, you can create alternative layouts to be used by the items in your list adapter such that a large screen might display more detail for each item.
    • -
  • Create alternative resource +
  • Create alternative resource files for values such as integers, dimensions, and even booleans. Using size qualifiers for these resources, you can easily apply different layout sizes, font sizes, or enable/disable features based on the current screen size.
    • diff --git a/docs/html/guide/publishing/preparing.jd b/docs/html/guide/publishing/preparing.jd index 5ed55febc155..4d3bffa98507 100644 --- a/docs/html/guide/publishing/preparing.jd +++ b/docs/html/guide/publishing/preparing.jd @@ -120,8 +120,8 @@ suitable private key.

    You may also have to obtain other release keys if your application accesses a service or uses a third-party library that requires you to use a key that is based on your private key. For example, if your application uses the MapView class, which is part of the MapView +class, which is part of the Google Maps external library, you will need to register your application with the Google Maps service and obtain a Maps API key. For information about getting a Maps API key, see

    See also

      -
    1. Preparing for +
    2. Preparing for Release
    3. Publishing on Android Market
    diff --git a/docs/html/guide/topics/appwidgets/index.jd b/docs/html/guide/topics/appwidgets/index.jd index 7b869a09b9fe..ba7b67c9770f 100644 --- a/docs/html/guide/topics/appwidgets/index.jd +++ b/docs/html/guide/topics/appwidgets/index.jd @@ -518,15 +518,12 @@ method. From within the Service, you can perform your own updates to the App Widget without worrying about the AppWidgetProvider closing down due to an Application Not Responding (ANR) error. See the Wiktionary sample's -AppWidgetProvider for an example of an App Widget running a {@link +href="http://code.google.com/p/wiktionary-android/source/browse/trunk/Wiktionary/src/com/example/android/wiktionary/WordWidget.java">Wiktionary sample's AppWidgetProvider for an example of an App Widget running a {@link android.app.Service}.

    Also see the -ExampleAppWidgetProvider.java sample class.

    +href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/appwidget/ExampleAppWidgetProvider.html">ExampleAppWidgetProvider.java +sample class.

    Receiving App Widget broadcast Intents

    @@ -683,9 +680,8 @@ cancelled and the App Widget will not be added.

    See the -ExampleAppWidgetConfigure.java sample class in ApiDemos for an example.

    +href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/appwidget/ExampleAppWidgetConfigure.html">ExampleAppWidgetConfigure.java +sample class in ApiDemos for an example.

    Setting a Preview Image

    diff --git a/docs/html/guide/topics/manifest/activity-element.jd b/docs/html/guide/topics/manifest/activity-element.jd index e23fb0ec7e3e..e76a6becb011 100644 --- a/docs/html/guide/topics/manifest/activity-element.jd +++ b/docs/html/guide/topics/manifest/activity-element.jd @@ -59,7 +59,7 @@ by the system and will never be run.
    attributes:
    -
    {@code android:allowTaskReparenting}
    +
    {@code android:allowTaskReparenting}
    Whether or not the activity can move from the task that started it to the task it has an affinity for when that task is next brought to the front — "{@code true}" if it can move, and "{@code false}" if it diff --git a/docs/html/guide/topics/manifest/application-element.jd b/docs/html/guide/topics/manifest/application-element.jd index 4f1964cd4028..df6f61a54e06 100644 --- a/docs/html/guide/topics/manifest/application-element.jd +++ b/docs/html/guide/topics/manifest/application-element.jd @@ -249,7 +249,7 @@ of that name is created. A global process can be shared with other applications, reducing resource usage.

    -
    {@code android:restoreAnyVersion}
    +
    {@code android:restoreAnyVersion}
    Indicate that the application is prepared to attempt a restore of any backed-up data set, even if the backup was stored by a newer version of the application than is currently installed on the device. Setting @@ -260,7 +260,7 @@ incompatible. Use with caution!

    The default value of this attribute is {@code false}.

    -
    {@code android:taskAffinity}
    +
    {@code android:taskAffinity}
    An affinity name that applies to all activities within the application, except for those that set a different affinity with their own taskAffinity diff --git a/docs/html/guide/topics/media/mediaplayer.jd b/docs/html/guide/topics/media/mediaplayer.jd index b3ca7dd4c7bb..002d113ea31a 100644 --- a/docs/html/guide/topics/media/mediaplayer.jd +++ b/docs/html/guide/topics/media/mediaplayer.jd @@ -251,7 +251,7 @@ href="{@docRoot}guide/topics/resources/runtime-changes.html">Handling Runtime Ch "background media" even when the user leaves your activity, much in the same way that the built-in Music application behaves. In this case, what you need is a {@link android.media.MediaPlayer MediaPlayer} controlled by a {@link android.app.Service}, as -discussed in Using a Service with MediaPlayer.

    +discussed in Using a Service with MediaPlayer.

    Using a Service with MediaPlayer

    diff --git a/docs/html/guide/topics/nfc/nfc.jd b/docs/html/guide/topics/nfc/nfc.jd index 175bc7cc0234..83873c37217c 100644 --- a/docs/html/guide/topics/nfc/nfc.jd +++ b/docs/html/guide/topics/nfc/nfc.jd @@ -666,7 +666,7 @@ Android Market is launched to download the application.

    potentially handling specific tags that you have deployed. AARs are only supported at the application level, because of the package name constraint, and not at the Activity level as with intent filtering. If you want to handle an intent at the Activity level, use intent filters. +href="#filtering-intents">use intent filters.

    @@ -795,8 +795,8 @@ depending on what the user is doing in your application.

    The following sample shows how a simple activity calls {@link android.nfc.NfcAdapter.CreateNdefMessageCallback} in the onCreate() method of an -activity (see for the -complete sample). This example also has methods to help you create a MIME record:

    +activity (see AndroidBeamDemo +for the complete sample). This example also has methods to help you create a MIME record:

     package com.example.android.beam;
diff --git a/docs/html/guide/topics/renderscript/index.jd b/docs/html/guide/topics/renderscript/index.jd
index 148705cfbca1..63f341adbf22 100644
--- a/docs/html/guide/topics/renderscript/index.jd
+++ b/docs/html/guide/topics/renderscript/index.jd
@@ -376,7 +376,7 @@ describes how these classes are generated through reflection.
    
   you call the constructor for the {@link android.renderscript.Script.FieldBase} class and specify
   the amount of structures that you want to allocate memory for. To allocate memory for a primitive
   type pointer, you must build an allocation manually, using the memory management classes
-  described in Table 1. The example below allocates memory for both
+  described in Table 1. The example below allocates memory for both
   the intPointer and touchPoints pointer and binds it to the
   RenderScript:
    
   
    diff --git a/docs/html/guide/topics/resources/animation-resource.jd b/docs/html/guide/topics/resources/animation-resource.jd
index eaa698fc45a7..6473155f33fd 100644
--- a/docs/html/guide/topics/resources/animation-resource.jd
+++ b/docs/html/guide/topics/resources/animation-resource.jd
@@ -335,7 +335,7 @@ set.start();
 
    
 
 
    
diff --git a/docs/html/guide/topics/sensors/sensors_motion.jd b/docs/html/guide/topics/sensors/sensors_motion.jd
index 3f712b2be68e..b6c3cb4ff966 100644
--- a/docs/html/guide/topics/sensors/sensors_motion.jd
+++ b/docs/html/guide/topics/sensors/sensors_motion.jd
@@ -28,7 +28,7 @@ parent.link=index.html
 href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/os/RotationVectorDemo.html">
 API Demos (OS - RotationVectorDemo)
       
  • API Demos (OS - Sensors)
    • 
     
     
    See also
    
diff --git a/docs/html/guide/topics/ui/actionbar.jd b/docs/html/guide/topics/ui/actionbar.jd
index 3c0ef26ef5fb..1bb4fa46b79c 100644
--- a/docs/html/guide/topics/ui/actionbar.jd
+++ b/docs/html/guide/topics/ui/actionbar.jd
@@ -642,7 +642,7 @@ work as designed otherwise.
    
   
    Adding this value requires that you set your build target to Android 4.0 or higher in order to
 compile. Older versions of Android ignore the {@code "collapseActionView"} value because they don't
 understand it. Just be sure not to use other APIs in your source code that are not supported in the
-version declared by your {@code
+version declared by your {@code
 minSdkVersion}, unless you add the appropriate version check at runtime.
    
 
 
@@ -843,8 +843,8 @@ you do not need to handle click events from the {@link
 android.app.Activity#onOptionsItemSelected onOptionsItemSelected()} callback method.
    
 
 
    For a sample using the share action provider, see
-ActionBarActionProviderActivity.
+ActionBarShareActionProviderActivity.
 
 
 
diff --git a/docs/html/guide/topics/usb/accessory.jd b/docs/html/guide/topics/usb/accessory.jd
index b0f488170c06..8b74bc0d6429 100644
--- a/docs/html/guide/topics/usb/accessory.jd
+++ b/docs/html/guide/topics/usb/accessory.jd
@@ -169,8 +169,9 @@ UsbAccessory accessory = (UsbAccessory) intent.getParcelableExtra(UsbManager.EXT
     include a <uses-feature> element that declares that your application uses
     the android.hardware.usb.accessory feature.
 
-    
  • If you are using the add-on library, add the
-    <uses-library> element specifying
+    
  • If you are using the 
+    add-on library,
+    add the <uses-library> element specifying
     com.android.future.usb.accessory for the library.
    • 
 
     
  • Set the minimum SDK of the application to API Level 10 if you are using the add-on library
diff --git a/docs/html/guide/topics/usb/adk.jd b/docs/html/guide/topics/usb/adk.jd
index 6c7ab0d80dd9..99c5f928ad82 100644
--- a/docs/html/guide/topics/usb/adk.jd
+++ b/docs/html/guide/topics/usb/adk.jd
@@ -699,7 +699,7 @@ bool AndroidAccessory::switchDevice(byte addr)
 
    • If this method returns false, the board waits until a new device is connected. If it is
 successful, the device displays itself on the USB bus as being in accessory mode when the ADK board
 re-enumerates the bus. When the device is in accessory mode, the accessory then establishes communication with the device.
+"#establish-adk">establishes communication with the device.
 
   
    Establish communication with the device
    
 
diff --git a/docs/html/guide/topics/wireless/bluetooth.jd b/docs/html/guide/topics/wireless/bluetooth.jd
index 0af1d2c86fb2..e4c6e1b96a90 100644
--- a/docs/html/guide/topics/wireless/bluetooth.jd
+++ b/docs/html/guide/topics/wireless/bluetooth.jd
@@ -902,8 +902,9 @@ the Bluetooth A2DP  Service via IPC.
 
    Here are the basic steps for working with a profile:
     
 
       
 
-  
    1. Get the default adapter, as described in Setting Up Bluetooth.
      2.  
+  
    2. Get the default adapter, as described in
+    Setting Up
+      Bluetooth.
      3.  
 
   
    3. Use {@link
 android.bluetooth.BluetoothAdapter#getProfileProxy(android.content.Context,
diff --git a/docs/html/sdk/RELEASENOTES.jd b/docs/html/sdk/RELEASENOTES.jd
index bf091e9956b2..91eb57f48582 100644
--- a/docs/html/sdk/RELEASENOTES.jd
+++ b/docs/html/sdk/RELEASENOTES.jd
@@ -657,8 +657,8 @@ href="{@docRoot}sdk/eclipse-adt.html">ADT Plugin for Eclipse.
      
 
      T-Mobile G1 Compatibility
      
 
 
      This version of the SDK has been tested for compatibility with the first 
-Android-powered mobile device, the T-Mobile
-G1. 
      
+Android-powered mobile device, the T-Mobile
+G1. 
      
 
 
      MapView API Key
      
 
diff --git a/docs/html/sdk/android-1.1.jd b/docs/html/sdk/android-1.1.jd
index 8123fa8dad0e..b61f18615c75 100644
--- a/docs/html/sdk/android-1.1.jd
+++ b/docs/html/sdk/android-1.1.jd
@@ -106,7 +106,7 @@ data, a Maps API Key is required.
      4. 
 
      The Android 1.1 system image was tested for compatability with the
 Android-powered devices listed below:
      
 	
 
 
      Built-in Applications
      
diff --git a/docs/html/sdk/android-3.0.jd b/docs/html/sdk/android-3.0.jd
index 7b04446d9e3b..96b92d9a59e3 100644
--- a/docs/html/sdk/android-3.0.jd
+++ b/docs/html/sdk/android-3.0.jd
@@ -262,8 +262,8 @@ android.content.ClipData.Item}s.
      
 
 
      For more information, read the Copy
 and Paste documentation. You can also see a simple implementation of copy and paste in the API Demos and a more complete implementation in the API Demos
+and a more complete implementation in the Note Pad application.
      
 
 
@@ -386,7 +386,7 @@ loader for your activity or fragment.
      
 
      For more information, read the Loaders documentation. You can also see
 example code using loaders in the FragmentListCursorLoader
+href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/app/LoaderCursor.html">LoaderCursor
 and 
 LoaderThrottle samples.
      
diff --git a/docs/html/sdk/android-3.1.jd b/docs/html/sdk/android-3.1.jd
index 0d2d7f8636be..78f265d2f055 100644
--- a/docs/html/sdk/android-3.1.jd
+++ b/docs/html/sdk/android-3.1.jd
@@ -422,10 +422,9 @@ onGenericMotionEvent()} there instead.
      
 
 
      To look at a sample application that uses joystick motion
 events, see GameControllerInput and GameView.
      
+href="{@docRoot}resources/samples/ApiDemos/src/com/example/android/apis/view/GameControllerInput.html">GameControllerInput 
+and GameView.
      
 
 
      RTP API
      
 
@@ -931,7 +930,7 @@ devices.
 href="{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code
 <uses-feature>} manifest elements. For more information about
 declaring features in an application manifest, read Android Market
+href="{@docRoot}guide/appendix/market-filters.html">Android Market
 Filters.
      
 
 
diff --git a/docs/html/sdk/android-4.0.jd b/docs/html/sdk/android-4.0.jd
index 7161b03708b5..5f55947bb0e6 100644
--- a/docs/html/sdk/android-4.0.jd
+++ b/docs/html/sdk/android-4.0.jd
@@ -1292,9 +1292,9 @@ public boolean onCreateOptionsMenu(Menu menu) {
 }
    -

    For an example using the {@link android.widget.ShareActionProvider}, see the ActionBarActionProviderActivity class in ApiDemos.

    +

    For an example using the {@link android.widget.ShareActionProvider}, see ActionBarShareActionProviderActivity in ApiDemos.

    Collapsible action views

    diff --git a/docs/html/training/id-auth/authenticate.jd b/docs/html/training/id-auth/authenticate.jd index 4eba87b4624c..592fe1cc02dd 100644 --- a/docs/html/training/id-auth/authenticate.jd +++ b/docs/html/training/id-auth/authenticate.jd @@ -63,8 +63,8 @@ Tasks. strings that identify your app to the service. You need to obtain these strings directly from the service owner. Google has a self-service system for obtaining client ids and secrets. The article Getting Started with the Tasks API and OAuth 2.0 on Android explains +href="http://code.google.com/apis/tasks/articles/oauth-and-tasks-on-android.html">Getting +Started with the Tasks API and OAuth 2.0 on Android explains how to use this system to obtain these values for use with the Google Tasks API. diff --git a/docs/html/training/monitoring-device-state/manifest-receivers.jd b/docs/html/training/monitoring-device-state/manifest-receivers.jd index 556a733e4ee4..0b79ce6f36ce 100644 --- a/docs/html/training/monitoring-device-state/manifest-receivers.jd +++ b/docs/html/training/monitoring-device-state/manifest-receivers.jd @@ -14,7 +14,7 @@ previous.link=connectivity-monitoring.html

    This lesson teaches you to

      -
    1. Toggle and Cascade State Change Receivers to Improve +
    2. Toggle and Cascade State Change Receivers to Improve Efficiency
    -- cgit v1.2.3-59-g8ed1b