Merge "Docs: Changes to source.android.com"android-o-mr1-iot-release-smart-display-r3oreo-mr1-1.2-iot-release

10 files changed, 75 insertions, 43 deletions

diff --git a/en/devices/_translation.yaml b/en/devices/_translation.yaml
index 64e32fca..32d1e74b 100644
--- a/en/devices/_translation.yaml
+++ b/en/devices/_translation.yaml
@@ -1,4 +1,4 @@
-enable_continuous_translation: True
+enable_continuous_translation: true
 title: Android Open Source Project Devices tab
 description: Translations for SAC devices tab
 language:
diff --git a/en/devices/accessories/index.html b/en/devices/accessories/index.html
index ec9ded65..787309c0 100644
--- a/en/devices/accessories/index.html
+++ b/en/devices/accessories/index.html
@@ -29,7 +29,7 @@ that extend Android capabilities in a wide range of Android-powered devices.
 <div class="layout-content-row">
 
   <div class="layout-content-col span-6">
-        <h4 id="audio-accessories">Audio Accessories</h4>
+        <h4 id="audio-accessories">Audio accessories</h4>
         <p>Android supports local on-device audio and remote off-device audio
         over a wired 3.5 mm headset jack, USB connection, or Bluetooth.
         Manufacturers should see the <a
@@ -41,7 +41,7 @@ that extend Android capabilities in a wide range of Android-powered devices.
   </div>
 
   <div class="layout-content-col span-6">
-        <h4 id="custom-accessories">Custom Accessories</h4>
+        <h4 id="custom-accessories">Custom accessories</h4>
         <p>What do you want to connect to your Android device? Alarm clock?
         Keyboard? Thermostat? Robot? Learn how to connect existing equipment or
         your own unique hardware to Android using the Android Open Accessory
diff --git a/en/devices/architecture/hidl/threading.html b/en/devices/architecture/hidl/threading.html
index 26c2cc12..fef555ad 100644
--- a/en/devices/architecture/hidl/threading.html
+++ b/en/devices/architecture/hidl/threading.html
@@ -112,7 +112,7 @@ concurrently with future calls from the client (unless the server threadpool has
 only one thread).</p>
 
 <p>In addition to synchronous callbacks, <code>oneway</code> calls from a
-single-threadedclient may be handled concurrently by a server with multiple
+single-threaded client may be handled concurrently by a server with multiple
 threads in its threadpool, but only if those <code>oneway</code> calls are
 executed on different interfaces. <code>oneway</code> calls on the same
 interface are always serialized.</p>
@@ -164,9 +164,9 @@ and does not wait for the server to complete its function call invocation. At th
 surface (and in aggregate), this means the function call takes half the
 time because it is executing half the code, but when writing implementations that
 are performance sensitive, this has some scheduling implications. Normally,
-using a oneway call causes the callee to continue to be scheduled whereas
+using a oneway call causes the caller to continue to be scheduled whereas
 using a normal synchronous call causes the scheduler to immediately transfer
-from the callee to the caller process. This is a performance optimization in
+from the caller to the callee process. This is a performance optimization in
 binder. For services where the oneway call must be executed in the target process
 with a high priority, the scheduling policy of the receiving service can be
 changed. In C++, using <code>libhidltransport</code>'s method
diff --git a/en/devices/audio/latency/design.html b/en/devices/audio/latency/design.html
index 59ab47e0..acbcc382 100644
--- a/en/devices/audio/latency/design.html
+++ b/en/devices/audio/latency/design.html
@@ -34,7 +34,7 @@ SoC vendors implement the design correctly on their particular devices
 and chipsets.  This article is not intended for application developers.
 </p>
 
-<h2 id="trackCreation">Track Creation</h2>
+<h2 id="trackCreation">Track creation</h2>
 
 <p>
 The client can optionally set bit <code>AUDIO_OUTPUT_FLAG_FAST</code> in the
@@ -83,7 +83,7 @@ If the client's request was accepted, it is called a "fast track."
 Otherwise it's called a "normal track."
 </p>
 
-<h2 id="mixerThreads">Mixer Threads</h2>
+<h2 id="mixerThreads">Mixer threads</h2>
 
 <p>
 At the time AudioFlinger creates a normal mixer thread, it decides
diff --git a/en/devices/input/input-device-configuration-files.html b/en/devices/input/input-device-configuration-files.html
index 97234ab0..c99d1f7c 100644
--- a/en/devices/input/input-device-configuration-files.html
+++ b/en/devices/input/input-device-configuration-files.html
@@ -106,7 +106,7 @@ touch.orientationAware = 1
 # Additional calibration properties...
 # etc...
 </pre>
-<h2 id="common-properties">Common Properties</h2>
+<h2 id="common-properties">Common properties</h2>
 <p>The following property is common to all input device classes.</p>
 <p>Refer to the documentation of each input device class for information about the
 special properties used by each class.</p>
diff --git a/en/devices/input/key-layout-files.html b/en/devices/input/key-layout-files.html
index 823770a5..be58e7e1 100644
--- a/en/devices/input/key-layout-files.html
+++ b/en/devices/input/key-layout-files.html
@@ -61,7 +61,7 @@ in the device name other than &#39;0&#39;-&#39;9&#39;, &#39;a&#39;-&#39;z&#39;,
 &#39;A&#39;-&#39;Z&#39;, &#39;-&#39; or &#39;&#95;&#39; are replaced by
 &#39;&#95;&#39;.</p>
 
-<h2 id="generic-key-layout-file">Generic Key Layout File</h2>
+<h2 id="generic-key-layout-file">Generic key layout file</h2>
 <p>The system provides a special built-in generic key layout file called
 <code>Generic.kl</code>. This key layout is intended to support a variety of
 standard external keyboards and joysticks. <strong>Do not modify the generic key
@@ -71,7 +71,7 @@ layout!</strong></p>
 <p>A key layout file is a plain text file consisting of key or axis declarations
 and flags.</p>
 
-<h3 id="key-declarations">Key Declarations</h3>
+<h3 id="key-declarations">Key declarations</h3>
 <p>Key declarations consist of the keyword <code>key</code> followed by a Linux
 key code number and Android key code name, or the keyword usage followed by a
 HID usage and Android key code name. The HID usage is represented as a 32-bit
@@ -95,12 +95,12 @@ adjacent to the main touch screen. This causes special debouncing logic to be
 enabled (see below).</li>
 </ul>
 
-<h3 id="axis-declarations">Axis Declarations</h3>
+<h3 id="axis-declarations">Axis declarations</h3>
 <p>Axis declarations each consist of the keyword <code>axis</code> followed by a
 Linux axis code number and qualifiers that control the behavior of the axis
 including at least one Android axis code name.</p>
 
-<h4 id="basic-axes">Basic Axes</h4>
+<h4 id="basic-axes">Basic axes</h4>
 <p>A basic axis simply maps a Linux axis code to an Android axis code name. The
 following declaration maps <code>ABS_X</code> (indicated by <code>0x00</code>)
 to <code>AXIS_X</code> (indicated by <code>X</code>).</p>
@@ -110,7 +110,7 @@ axis 0x00 X
 <p>In the above example, if the value of <code>ABS_X</code> is <code>5</code>
 then <code>AXIS_X</code> is set to <code>5</code>.</p>
 
-<h4 id="split-axes">Split Axes</h4>
+<h4 id="split-axes">Split axes</h4>
 <p>A split axis maps a Linux axis code to two Android axis code names, such that
 values less than or greater than a threshold are split across two different axes
 when mapped. This mapping is useful when a single physical axis reported by the
@@ -130,7 +130,7 @@ of <code>ABS_Y</code> is <code>0x83</code> then <code>AXIS_GAS</code> is set to
 the split value of <code>0x7f</code> then both <code>AXIS_GAS</code> and
 <code>AXIS_BRAKE</code> are set to <code>0</code>.</p>
 
-<h4 id="inverted-axes">Inverted Axes</h4>
+<h4 id="inverted-axes">Inverted axes</h4>
 <p>An inverted axis inverts the sign of the axis value. The following
 declaration maps <code>ABS_RZ</code> (indicated by <code>0x05</code>) to
 <code>AXIS_BRAKE</code> (indicated by <code>BRAKE</code>), and inverts the
@@ -141,7 +141,7 @@ axis 0x05 invert BRAKE
 <p>In the above example, if the value of <code>ABS_RZ</code> is <code>2</code>
 then <code>AXIS_BRAKE</code> is set to <code>-2</code>.</p>
 
-<h4 id="center-flat-option">Center Flat Option</h4>
+<h4 id="center-flat-option">Center flat option</h4>
 <p> A joystick device may report input events even when the joystick is not being used, due to noise.
 This noise typically comes from the left and/or right sticks, and causes the driver to report
   a position value near 0.
@@ -200,7 +200,7 @@ key 14    DEL
 # etc...
 </pre>
 
-<h4 id="system-controls">System Controls</h4>
+<h4 id="system-controls">System controls</h4>
 <pre class="devsite-click-to-copy">
 # This is an example of a key layout file for basic system controls,
 # such as volume and power keys which are typically implemented as GPIO pins
@@ -211,7 +211,7 @@ key 115   VOLUME_UP
 key 116   POWER
 </pre>
 
-<h4 id="capacitive-buttons">Capacitive Buttons</h4>
+<h4 id="capacitive-buttons">Capacitive buttons</h4>
 <pre class="devsite-click-to-copy">
 # This is an example of a key layout file for a touch device with capacitive buttons.
 
@@ -221,7 +221,7 @@ key 158    BACK           VIRTUAL
 key 217    SEARCH         VIRTUAL
 </pre>
 
-<h4 id="headset-jack-media-controls">Headset Jack Media Controls</h4>
+<h4 id="headset-jack-media-controls">Headset jack media controls</h4>
 <pre class="devsite-click-to-copy">
 # This is an example of a key layout file for headset mounted media controls.
 # A typical headset jack interface might have special control wires or detect known
@@ -269,7 +269,7 @@ axis 0x10 HAT_X
 axis 0x11 HAT_Y
 </pre>
 
-<h2 id="virtual-soft-keys">Virtual Soft Keys</h2>
+<h2 id="virtual-soft-keys">Virtual soft keys</h2>
 <p>The input system provides special features for implementing virtual soft keys
 in the following use cases:</p>
 <ol>
diff --git a/en/devices/tech/config/namespaces_libraries.html b/en/devices/tech/config/namespaces_libraries.html
index 1e94bf1b..5dae4b07 100644
--- a/en/devices/tech/config/namespaces_libraries.html
+++ b/en/devices/tech/config/namespaces_libraries.html
@@ -54,11 +54,43 @@ with <code>libpng</code>).
 libraries</h2>
 
 <p>
-In addition to standard public native libraries, vendors may choose to provide
-additional native libraries accessible to apps by putting them under the
-<code>/vendor</code> library folder (/vendor/lib for 32 bit libraries and,
-/vendor/lib64 for 64 bit) and listing them in:
-<code>/vendor/etc/public.libraries.txt</code>
+In addition to standard public native libraries, silicon vendors (starting from Android 7.0) and
+device manufactures (starting from Android 9) may choose to provide additional native libraries
+accessible to apps by putting them under the respective library folders and explicitly listing them
+in .txt files.
+</p>
+
+<p>The library folders are:</p>
+<ul>
+  <li><code>/vendor/lib</code> (for 32-bit) and <code>/vendor/lib64</code> (for 64-bit)
+    for libraries from silicon vendors</li>
+  <li><code>/system/lib</code> (for 32-bit) and <code>/system/lib64</code> (for 64-bit)
+    for libraries from device manufacturers</li>
+<ul>
+
+<p>The .txt files are:</p>
+<ul>
+  <li><code>/vendor/etc/public.libraries.txt</code> for libraries from silicon vendors</li>
+  <li><code>/system/etc/public.libraries-COMPANYNAME.txt</code> for libraries from device manufacturers,
+    where <code>COMPANYNAME</code> refers to a name of the manufacturer (such as
+    <code>awesome.company</code>). <code>COMPANYNAME</code> should match with
+    <code>[A-Za-z0-9_.-]+</code>; alphanumeric characters, _, . (dot) and -. It is possible to
+    have multiple such .txt files in a device if some libraries are from external solution
+    providers.
+</ul>
+
+<p>
+  Native libraries in the <code>system</code> partition that are made public by device manufacturers
+  <strong>MUST</strong> be named <code>lib*COMPANYNAME.so</code>, e.g., <code>libFoo.awesome.company.so</code>.
+  In other words, <code>libFoo.so</code> without the company name suffix MUST NOT be made public.
+  The <code>COMPANYNAME</code> in the library file name MUST match with the <code>COMPANYNAME</code> in the
+  txt file name in which the library name is listed.
+</p>
+
+<p>
+  Native libraries that are part of AOSP MUST NOT be made public (except the standard
+  public native libraries which are public by default). Only the additional libraries added by
+  silicon vendors or device manufacturers can be made accessible to apps.
 </p>
 
 <p>
diff --git a/en/devices/tech/display/adaptive-icons.html b/en/devices/tech/display/adaptive-icons.html
index 5d74b10c..31770a3a 100644
--- a/en/devices/tech/display/adaptive-icons.html
+++ b/en/devices/tech/display/adaptive-icons.html
@@ -109,7 +109,7 @@
     class="prettyprint">public class Icon extends Parceleable {
     method public Bitmap createWithAdaptiveBitmap();
     }</pre>
-    <h2>Reference Implementation</h2>
+    <h2>Reference implementation</h2>
     <p>
     Nothing needs to be done to render the static adaptive icons on any of the
     System UI surfaces. When PackageManager returns a drawable, simply bind that to
@@ -131,7 +131,7 @@
     A recommended manual test case can be found at:
     platform/development/samples/AdaptiveIconSample/.
     </p>
-    <h2>Known Issues</h2>
+    <h2>Known issues</h2>
     <p>
     Known issues include the following:
     </p><ul>
diff --git a/en/devices/tech/health/deprecation.md b/en/devices/tech/health/deprecation.md
index fcaf711f..9a31cd5b 100644
--- a/en/devices/tech/health/deprecation.md
+++ b/en/devices/tech/health/deprecation.md
@@ -49,21 +49,21 @@ To do so:
 1.  Remove `healthd` and `healthd.rc` from the system image by adding the
     following line to the device-specific implementation in Soong:
 
-        ```
-        cc_binary {
-            name: "android.hardware.health@2.0-service.device_name"
-            overrides: ["healthd"],
-            // ...
-        }
-        ```
-
-        Or, if the module is in Make:
-
-        ```yaml
-        LOCAL_MODULE_NAME := \
-            android.hardware.health@2.0-service.device_name
-        LOCAL_OVERRIDES_MODULES := healthd
-        ```
+    ```
+    cc_binary {
+        name: "android.hardware.health@2.0-service.device_name"
+        overrides: ["healthd"],
+        // ...
+    }
+    ```
+
+    Or, if the module is in Make:
+
+    ```yaml
+    LOCAL_MODULE_NAME := \
+        android.hardware.health@2.0-service.device_name
+    LOCAL_OVERRIDES_MODULES := healthd
+    ```
 
     If the default implementation `android.hardware.health@2.0-service` is
     installed, implement a device-specific
diff --git a/en/devices/tech/settings/info-architecture.html b/en/devices/tech/settings/info-architecture.html
index d0f027de..48f74bfe 100644
--- a/en/devices/tech/settings/info-architecture.html
+++ b/en/devices/tech/settings/info-architecture.html
@@ -103,7 +103,7 @@ single host fragment and multiple setting controllers.
 <p>
 <code>DashboardFragment</code> is the host of plugin-style preference controllers.
 The fragment inherits from <code>PreferenceFragment</code> and has hooks to
-inflate and update both static preference lists and dynamic preference lists.
+expand and update both static preference lists and dynamic preference lists.
 </p>
 
 <h3 id="static-preferences">Static preferences</h3>