diff --git a/docs/html/tools/device.jd b/docs/html/tools/device.jd index 89b3857ab6e69..5d8d3842008a1 100644 --- a/docs/html/tools/device.jd +++ b/docs/html/tools/device.jd @@ -27,7 +27,7 @@ environment and Android-powered device for testing and debugging on the device.<

You can use any Android-powered device as an environment for running, debugging, and testing your applications. The tools included in the SDK make it easy to install and run your application on the device each time you compile. You can install your application on the -device directly from Eclipse or from the command line with ADB. If +device directly from Android Studio or from the command line with ADB. If you don't yet have a device, check with the service providers in your area to determine which Android-powered devices are available.

@@ -73,13 +73,21 @@ screen to find Developer options at the bottom.

would on the emulator. Before you can start, there are just a few things to do:

    -
  1. Declare your application as "debuggable" in your Android Manifest. -

    When using Eclipse, you can skip this step, because running your app directly from -the Eclipse IDE automatically enables debugging.

    +
  2. Verify that your application is "debuggable" in your manifest or build.gradle file. +

    In the build file, make sure the debuggable property in the debug build + type is set to true. The build type property overrides the manifest setting.

    +
    +android {
+    buildTypes {
+        debug {
+            debuggable true
+        }
+
    +

    In the AndroidManifest.xml file, add android:debuggable="true" to the <application> element.

    Note: If you manually enable debugging in the manifest - file, be sure to disable it before you build for release (your published application + file, be sure to disable it in your release build (your published application should usually not be debuggable).

  3. Enable USB debugging on your device.