Merge "docs: InfoPros Project 02 - New API 15 baseline" into mnc-docs

docs/html/design/handhelds/index.jd

@@ -79,9 +79,9 @@ to allow the user to enjoy full screen content without distraction.</p>
 </li>
 <li>
 <h4>Navigation Bar</h4>
-<p>New for phones in Android 4.0, the navigation bar is present only on devices that don't have
+<p>The navigation bar is present only on devices that don't have
   the traditional hardware keys. It houses the device navigation controls Back, Home, and
-  Recents, and also displays a menu for apps written for Android 2.3 or earlier.</p>
+  Recents.</p>
 </li>
 </ol>
 

docs/html/design/patterns/navigation.jd

@@ -11,11 +11,10 @@ page.image=/design/media/navigation_between_siblings_gmail.png
 </a>
 
 <p itemprop="description">Consistent navigation is an essential component of the overall user experience. Few things frustrate
-users more than basic navigation that behaves in inconsistent and unexpected ways. Android 3.0
+users more than basic navigation that behaves in inconsistent and unexpected ways. Thoughtfully
-introduced significant changes to the global navigation behavior. Thoughtfully following the
+following the guidelines for Back and Up will make your app's navigation predictable and reliable
-guidelines for Back and Up will make your app's navigation predictable and reliable for your users.</p>
+for your users.</p>
-<p>Android 2.3 and earlier relied upon the system <em>Back</em> button for supporting navigation within an
+<p>Action bars provide a second, standard navigation mechanism:
-app. With the introduction of action bars in Android 3.0, a second navigation mechanism appeared:
 the <em>Up</em> button, consisting of the app icon and a left-point caret.</p>
 
 <img src="{@docRoot}design/media/navigation_with_back_and_up.png">

docs/html/design/patterns/new.jd

@@ -196,10 +196,7 @@ lockscreen, priority notifications, and cloud-synced notifications.</p>
   <div class="col-7">
     <p>Android 4.0 removes the need for traditional hardware keys on
     phones by replacing them with a virtual navigation bar that houses
-    the Back, Home and Recents buttons. Read the
+    the Back, Home and Recents buttons.</p>
-    <a href="{@docRoot}design/patterns/compatibility.html">Compatibility</a>
-    pattern to learn how the OS adapts to phones with hardware buttons and
-    how pre-Android 3.0 apps that rely on menu keys are supported.</p>
   </div>
   <div class="col-6">
     <img src="{@docRoot}design/media/whats_new_nav_bar.png">

docs/html/design/patterns/widgets.jd

@@ -3,6 +3,13 @@ page.tags="appwidget","home"
 page.metaDescription=Design guide to creating widgets that are easy to use and look great.
 @jd:body
 
+<a class="notice-developers" href="{@docRoot}guide/topics/appwidgets/index.html">
+  <div>
+    <h3>Developer Docs</h3>
+    <p>App Widgets</p>
+  </div>
+</a>
+
 <p itemprop="description">Widgets are an essential aspect of home screen customization. You can imagine them as "at-a-glance" views of an app's most important data and functionality that is accessible right from the user's home screen. Users can move widgets across their home screen panels, and, if supported, resize them to tailor the amount of information within a widget to their preference.</p>
 
 <h2>Widget types</h2>
@@ -80,7 +87,10 @@ A music player widget is primarily a control widget, but also keeps the user inf
 <div class="cols">
   <div class="col-6">
     <h3>Widget resizing</h3>
-    <p>With version 3.1, Android introduced resizable widgets to the platform. Resizing allows users to adjust the height and/or the width of a widget within the constraints of the home panel placement grid. You can decide if your widget is freely resizable or if it is constrained to horizontal or vertical size changes. You do not have to support resizing if your particular widget is inherently fixed-size.</p>
+    <p>Resizing allows users to adjust the height and/or the width of a widget within the
+constraints of the home panel placement grid. You can decide if your widget is freely resizable or
+if it is constrained to horizontal or vertical size changes. You do not have to support resizing if
+your particular widget is inherently fixed-size.</p>
     <p>Allowing users to resize widgets has important benefits:</p>
     <ul>
       <li>They can fine-tune how much information they want to see on each widget.</li>

docs/html/google/play/licensing/overview.jd

@@ -197,8 +197,7 @@ application: </p>
 
 <ul>
 <li>An application can use the service only if the Google Play client is
-installed on its host device and the device is running Android 1.5 (API level 3)
+installed on its host device and the device is running Android 1.5 (API level 3) or higher.</li>
-or higher.</li>
 <li>To complete a license check, the licensing server must be accessible over
 the network. You can implement license caching behaviors to manage access to your application when
 there is no network connectivity. </li>
@@ -233,8 +232,7 @@ managed on any device on any storage, including SD card.</p>
 
 <p>Although no license mechanism can completely prevent all unauthorized use,
 the licensing service lets you control access for most types of normal usage,
-across all compatible devices, locked or unlocked, that run Android 1.5 or
+across all compatible devices, locked or unlocked.</p>
-higher version of the platform.</p>
 
 <p>To begin adding application licensing to your application, continue to <a
 href="{@docRoot}google/play/licensing/setting-up.html">Setting Up for Licensing</a>.</p>

docs/html/google/play/licensing/setting-up.jd

@@ -161,7 +161,7 @@ the add-on, you need to create an AVD configuration that uses that system image.
 However, it does provide: </p>
 
 <ul>
-<li>An Google Play background service that implements the
+<li>A Google Play background service that implements the
 <code>ILicensingService</code> remote interface, so that your application can
 send license checks over the network to the licensing server. </li>
 <li>A set of underlying account services that let you add an a Google account on
@@ -213,24 +213,8 @@ Run/Debug Configuration that targets the appropriate device or AVD. </p>
 
 <p>You do not need to make any changes to your application's
 build configuration, provided that the project is already configured to compile
-against a standard Android 1.5 (API level 3) or higher library. For example:
+against a standard Android 1.5 (API level 3) or higher library. Adding licensing to an application
-
+should have no impact whatsoever on the application's build configuration.</p>
-<ul>
-<li>If you have an existing application that is compiled against
-the Android 1.5 library, you do not need to make any changes to your
-build configuration to support licensing. The build target meets the minimum
-requirements for licensing, so you would continue building
-against the same version of the Android platform.</li>
-
-<li>Similarly, if you are building against Android 1.5 (API level 3) but
-are using an emulator running the Google APIs Add-On API 8 as the application's
-runtime environment, there is no need to change your application's build
-configuration. </li>
-</ul>
-
-<p>In general, adding licensing to an application should have no impact
-whatsoever on the application's build configuration.</p>
-
 
 <h3 id="download-lvl">Downloading the LVL</h3>
 

docs/html/ndk/guides/ndk-gdb.jd

@@ -27,7 +27,8 @@ does not support using the legacy {@code make APP=<name>} method to build.
 {@code <application>} element that sets the {@code android:debuggable} attribute to {@code
 true}.</li>
 <li>Build your app to run on Android 2.2 (Android API level 8) or higher.</li>
-<li>Debug on a device or emulator running Android 2.2 or higher. For debugging purposes, the target
+<li>Debug on a device or emulator running Android 2.2 or higher.
+ For debugging purposes, the target
 API level that you declare in your {@code AndroidManifest.xml} file does not matter.</li>
 <li>Develop your app in a Unix shell. On Windows, use <a href="https://www.cygwin.com/">Cygwin</a>
 or the experimental {@code ndk-gdb-py} <a href="https://www.python.org/">Python</a>
@@ -221,14 +222,6 @@ Python version of {@code ndk-gdb}.</p></td>
 cannot debug native threads properly. The debugger can only debug the main thread, abd completely
 ignores the execution of other threads.</p>
 
-<p>Using a version of Android prior to 2.3 causes {@code ndk-gdb} to display the following message
-prior to showing the GDB prompt:</p>
-
-<pre class="no-pretty-print">
-Thread debugging is unsupported on this Android platform!
-</pre>
-
-
 <p>If you place a breakpoint on a function executed on a non-main thread, the program exits, and
 GDB displays the following message:</p>
 

docs/html/training/accessibility/service.jd

@@ -132,7 +132,7 @@ public void onServiceConnected() {
 }
 </pre>
 
-<p>Starting with Android 4.0, there is a second option available: configure the
+<p>The second option is to configure the
 service using an XML file.  Certain configuration options like
 {@link android.R.attr#canRetrieveWindowContent} are only available if you
 configure your service using XML.  The same configuration options above, defined
@@ -201,8 +201,7 @@ public void onAccessibilityEvent(AccessibilityEvent event) {
 </pre>
 
 <h2 id="query">Query the View Heirarchy for More Context</h2>
-<p>This step is optional, but highly useful.  One of the new features in Android
+<p>This step is optional, but highly useful. The Android platform provides the ability for an
-4.0 (API Level 14) is the ability for an
 {@link android.accessibilityservice.AccessibilityService} to query the view
 hierarchy, collecting information about the UI component that generated an event, and
 its parent and children.  In order to do this, make sure that you set the

docs/html/training/appbar/index.jd

@@ -9,12 +9,6 @@ startpage=true
 <div id="tb-wrapper">
 <div id="tb">
 
-<h2>Dependencies and prerequisites</h2>
-<ul>
-  <li>Android 2.1 (API level 7) or higher</li>
-</ul>
-
-
 <h2>You should also read</h2>
 <ul>
   <li><a href="{@docRoot}training/implementing-navigation/index.html">