From 1bfa6a655a3166c6f8582a6e55edb8cb45ee698b Mon Sep 17 00:00:00 2001 From: Adarsh Fernando Date: Tue, 22 Mar 2016 09:23:15 -0700 Subject: [PATCH] Docs: Added AS 2.0 Release Notes Bug: 26853658 Bug: 27814328 Change-Id: Ie4ac3af4270b3341be75b50c28db5a93c92266bc --- docs/html/tools/revisions/studio.jd | 269 +++++++++++++++++++++++++++- 1 file changed, 263 insertions(+), 6 deletions(-) diff --git a/docs/html/tools/revisions/studio.jd b/docs/html/tools/revisions/studio.jd index a65c1646dc6a5..2e42c9d7ff4c7 100755 --- a/docs/html/tools/revisions/studio.jd +++ b/docs/html/tools/revisions/studio.jd @@ -19,11 +19,21 @@ page.title=Android Studio Release Notes everything you need to begin developing Android apps:

For an introduction to Android Studio, read the @@ -39,9 +49,256 @@ select Android Studio > Check for updates).

The sections below provide notes about successive releases of Android Studio, as denoted by revision number.

-
+

Android Studio v2.0.0 (March 2016) +

+ +
+ +

+ Note: If you are developing for the N Developer Preview, you + should use Android Studio 2.1 Preview. Android Studio 2.0 does not support + all the features required to target the N Preview. To learn more, read about + how to properly set up your + developer environment for the N Preview. +

+ +

+ Instant Run: +

+ +
    +
  • Android Studio now deploys clean builds faster than ever before. + Additionally, pushing incremental code changes to the emulator or a physical + device is now almost instantaneous. Review your updates without redeploying a + new debug build or, in many cases, without restarting the app. +
    • + +
  • Instant Run supports pushing the following changes to a running app: +
      +
    • Changes to the implementation of an existing instance method or + static method +
      • + +
    • Changes to an existing app resource +
      • + +
    • Changes to structural code, such as a method signature or a static + field (requires a target device running API level 21 or higher). +
      • +
    +
    • + +
  • Read the documentation to learn more about Instant + Run. +

    + Note: Instant Run is supported only when you deploy the + debug build variant, use Android Plugin for + Gradle version 2.0.0 or higher, and configure your app's module-level + build.gradle file for minSdkVersion 15 or higher. + For the best performance, configure your app for minSdkVersion + 21 or higher. +

    +
    • +
+ +

+ Android Emulator 2.0: +

+
    +
  • Performance improvements: +
    • +
      +
    • Emulator now uses CPU acceleration on x86 emulator system images by + default. +
      • + +
    • Added SMP support + to take advantage of host multi-core architecture when emulating Android + 6.0 (API level 23) or higher, resulting in much better performance and + speed than the physical counterpart. Also with SMP support, you can test + apps that specifically target multi-core Android devices. +
      • + +
    • Improved data and APK push-pull protocol between the the Android Debug Bridge and devices + running Android 5.0 (API level 21) or higher. See speed improvements up + to five times faster than using a physical device. +
      • +
    + +
  • Extended UI controls and a floating toolbar provide easy access to features + previously available only through the command line, such as taking screen + captures, adjusting the battery level, rotating the screen, and managing + virtual calls. +
    • + +
  • Upload KML and GPX files to play back a set of custom location points. +
    • + +
  • Dynamically resize the emulator by dragging a corner or zoom into the + emulator window. +
    • + +
  • Install APKs or add media files to the emulator’s internal SD card by + dragging and dropping files into the emulator window. +
    • + +
  • Simulate multi-touch input. While interacting with the emulator screen, + enter multi-touch mode by holding down the Ctrl key on + Windown/Linux, or Command key on Mac OSX. +
    • + +
  • Improvements to the Android Virtual Device + Manager: +
      +
    • System images are now categorized under the following tabs: + Recommended, x86, and Other. +
      • + +
    • Under advanced settings, you can enable multi-core support and + specify the number of cores the emulator can use. +
      • + +
    • Under advanced settings, you can determine how graphics are rendered + on the emulator by selecting one of the following options: +
        +
      • + Hardware: use you computer's graphics card for + faster rendering. +
        • + +
      • + Software: use software-based rendering. +
        • + +
      • + Auto: let the emulator decide the best option. This + is the default setting. +
        • +
      +
      • +
    +
    • + +
  • Read the documentation to find out more about using the Android Emulator. +
    • + +
+ +

New additions to Lint:

+
    +
  • Inspection of {@code switch} statements using {@link + android.support.annotation.IntDef @IntDef} annotated integers to make sure + all constants are handled. To quickly add any missing statements, use the the + intention action drop-down menu and select Add Missing @IntDef + Constants. +
    • + +
  • Flags for incorrect attempts to use string interpolation to insert + version numbers in the {@code build.gradle} file. +
    • + +
  • Flags for anonymous classes that extend the {@link android.app.Fragment + Fragment} class. +
    • + +
  • Flags for native code in unsafe locations, such as the {@code res/} and {@code + asset/} folders. This flag encourages storing native code in the {@code libs/} + folder, which is then securely packaged into the application’s {@code + data/app-lib/} folder at install time. AOSP: #169950 +
    • + +
  • Flags for unsafe calls to {@link java.lang.Runtime#load(java.lang.String) + Runtime.load()} and {@link java.lang.System#load(java.lang.String) + System.load()} calls. AOSP: #179980 +
    • + +
  • Find and remove any unused resources by selecting Refactor > Remove + Unused Resources from the menu bar. Unused resource detection now + supports resources only referenced by unused resources, references in raw + files such as {@code .html} image references, and {@code tools:keep} and + {@code tools:discard} attributes used by the Gradle resource shrinker, while + considering inactive source sets (such as resources used in other build + flavors) and properly handling static field imports. +
    • + +
  • Checks that implicit API references are supported on all platforms + targeted by {@code minSdkVersion}. +
    • + +
  • Flags improper usage of {@link android.support.v7.widget.RecyclerView} + and {@link android.os.Parcelable}. +
    • + +
  • {@link android.support.annotation.IntDef @IntDef}, {@link + android.support.annotation.IntRange @IntRange}, and {@link + android.support.annotation.Size @Size} inspections are now also checked for + {@code int} arrays and varargs. +
    • +
+ +

Additional Improvements:

+
    +
  • Improved AAPT packaging times by specifying deploy target before the app + is built. This allows Android Studio to efficiently package only the + resources required by the specified device. +
    • + +
  • Added Cloud Test Lab integration to provide on-demand app testing with + the convenience and scalability of a cloud service. Learn more about how you + can use Cloud + Test Lab with Android Studio. +
    • + +
  • Added a preview of the new GPU Debugger. For graphics + intensive applications, you can now visually step through your OpenGL ES code + to optimize your app or game. +
    • + +
  • Added support for Google App Indexing integration and testing. Add deep + links, app indexing, and search functionality to your apps to help drive more + traffic to your app, discover which app content is used most, and attract new + users. Test and validate your URL links in your app all within Android + Studio. Learn more about implementing and testing Deep Link and App Indexing + APIs. +
    • + +
  • Upgrades from the latest IntelliJ 15 release, including improved code + analysis and performance. See What's New in IntelliJ for a + complete description of the new features and enhancements. +
    • + +
  • XML editor auto-complete now adds quotations marks when completing + attributes. To check if this option is enabled, open the Setting or + Preferences dialogue, navigate to Editor > General > Smart + Keys, and check the box next to Add quotes for attribute value on + attribute completion. Issue: 195113 +
    • + +
  • The XML editor now supports code completion for data binding + expressions. +
    • +
+
+
+ +
+

+ Android Studio v1.5.1 (December 2015)