From a1a9fd19df311a8c3be7dc3dd63a8992ecc50b03 Mon Sep 17 00:00:00 2001 From: Joe Fernandez Date: Mon, 7 Mar 2016 10:20:44 -0800 Subject: docs: InfoPros Project 02 - Batch 02 updates b/26490262 Change-Id: I3838f0c96ed687684457d2c56044148f56a29f8d --- docs/html/distribute/essentials/quality/core.jd | 3 +- docs/html/training/basics/firstapp/running-app.jd | 9 +---- docs/html/training/basics/fragments/creating.jd | 7 ---- docs/html/training/basics/intents/result.jd | 4 +- .../training/custom-views/making-interactive.jd | 4 +- .../training/game-controllers/compatibility.jd | 45 ++++++++-------------- docs/html/training/multiscreen/screensizes.jd | 5 +-- docs/html/training/system-ui/dim.jd | 2 +- docs/html/training/system-ui/navigation.jd | 6 +-- docs/html/training/system-ui/status.jd | 2 - 10 files changed, 29 insertions(+), 58 deletions(-) mode change 100644 => 100755 docs/html/training/basics/firstapp/running-app.jd mode change 100644 => 100755 docs/html/training/basics/fragments/creating.jd mode change 100644 => 100755 docs/html/training/basics/intents/result.jd mode change 100644 => 100755 docs/html/training/custom-views/making-interactive.jd mode change 100644 => 100755 docs/html/training/game-controllers/compatibility.jd mode change 100644 => 100755 docs/html/training/multiscreen/screensizes.jd mode change 100644 => 100755 docs/html/training/system-ui/dim.jd mode change 100644 => 100755 docs/html/training/system-ui/navigation.jd mode change 100644 => 100755 docs/html/training/system-ui/status.jd diff --git a/docs/html/distribute/essentials/quality/core.jd b/docs/html/distribute/essentials/quality/core.jd index 860d8809ea68..4b0b5467af88 100644 --- a/docs/html/distribute/essentials/quality/core.jd +++ b/docs/html/distribute/essentials/quality/core.jd @@ -988,8 +988,7 @@ data-cardsizes="6x3,6x3,6x3,6x3,6x3,6x3" data-maxresults="6"> Switch to another app to send the test app into the background. Go to Settings and check whether the test app has any services running while in the background. In Android 4.0 and higher, go to the Apps screen and find - the app in the "Running" tab. In earlier versions, use "Manage - Applications" to check for running services. + the app in the "Running" tab. diff --git a/docs/html/training/basics/firstapp/running-app.jd b/docs/html/training/basics/firstapp/running-app.jd old mode 100644 new mode 100755 index 74ec48deb1cb..99b38bfc6393 --- a/docs/html/training/basics/firstapp/running-app.jd +++ b/docs/html/training/basics/firstapp/running-app.jd @@ -54,17 +54,12 @@ line tools.

If you're developing on Windows, you might need to install the appropriate USB driver for your device. For help installing drivers, see the OEM USB Drivers document. -
  • Enable USB debugging on your device. -
    • diff --git a/docs/html/training/basics/fragments/creating.jd b/docs/html/training/basics/fragments/creating.jd old mode 100644 new mode 100755 index ac36531171cb..49fb8833be24 --- a/docs/html/training/basics/fragments/creating.jd +++ b/docs/html/training/basics/fragments/creating.jd @@ -38,13 +38,6 @@ extend the {@link android.support.v4.app.Fragment} class using the Support Library so your app remains compatible with devices running system versions as low as Android 1.6.

    -

    Note: If you decide that the minimum -API level your app requires is 11 or higher, you don't need to use the Support -Library and can instead use the framework's built in {@link android.app.Fragment} class and related -APIs. Just be aware that this lesson is focused on using the APIs from the Support Library, which -use a specific package signature and sometimes slightly different API names than the versions -included in the platform.

    -

    Before you begin this lesson, you must set up your Android project to use the Support Library. If you have not used the Support Library before, set up your project to use the v4 library by following the Support Library diff --git a/docs/html/training/basics/intents/result.jd b/docs/html/training/basics/intents/result.jd old mode 100644 new mode 100755 index b5214880fbbe..31d5a7c2616a --- a/docs/html/training/basics/intents/result.jd +++ b/docs/html/training/basics/intents/result.jd @@ -107,8 +107,8 @@ contact the user selected.

    In order to successfully handle the result, you must understand what the format of the result {@link android.content.Intent} will be. Doing so is easy when the activity returning a result is one of your own activities. Apps included with the Android platform offer their own APIs that -you can count on for specific result data. For instance, the People app (Contacts app on some older -versions) always returns a result with the content URI that identifies the selected contact, and the +you can count on for specific result data. For instance, the People app always returns a result +with the content URI that identifies the selected contact, and the Camera app returns a {@link android.graphics.Bitmap} in the {@code "data"} extra (see the class about Capturing Photos).

    diff --git a/docs/html/training/custom-views/making-interactive.jd b/docs/html/training/custom-views/making-interactive.jd old mode 100644 new mode 100755 index 4e9d53a5e773..14163d8bf267 --- a/docs/html/training/custom-views/making-interactive.jd +++ b/docs/html/training/custom-views/making-interactive.jd @@ -229,8 +229,8 @@ if (!mScroller.isFinished()) { is not available prior to API level 11, so this technique cannot be used on devices running Android versions lower than 3.0.

    -

    Note: {@link android.animation.ValueAnimator} isn't available - prior to API level 11, but you can still use it in applications that +

    Note: You can use {@link android.animation.ValueAnimator} in +applications that target lower API levels. You just need to make sure to check the current API level at runtime, and omit the calls to the view animation system if the current level is less than 11.

    diff --git a/docs/html/training/game-controllers/compatibility.jd b/docs/html/training/game-controllers/compatibility.jd old mode 100644 new mode 100755 index f68ab1ae1278..51ae9ee93669 --- a/docs/html/training/game-controllers/compatibility.jd +++ b/docs/html/training/game-controllers/compatibility.jd @@ -13,7 +13,7 @@ trainingnavtop=true Suppport
  • Add an Interface for Backward Compatibility
  • Implement the Interface on Android 4.1 and Higher
    • -
  • Implement the Interface on Android 2.3 up to Android +
  • Implement the Interface on Android 3.1 up to Android 4.0
  • Use the Version-Specific Implementations
    • @@ -36,7 +36,7 @@ their controllers even when they switch or upgrade their Android devices.

    This lesson demonstrates how to use APIs available in Android 4.1 and higher in a backward compatible way, enabling your game to support the following -features on devices running Android 2.3 and higher:

    +features on devices running Android 3.1 and higher: