diff options
Diffstat (limited to 'en')
46 files changed, 13666 insertions, 375 deletions
diff --git a/en/_index.yaml b/en/_index.yaml index 24c39733..fd444ebc 100644 --- a/en/_index.yaml +++ b/en/_index.yaml @@ -7,7 +7,7 @@ landing_page: path: /setup/downloading rows: - items: - - heading: 8.0 interfaces and architecture + - heading: 8.1 interfaces and architecture description: > Port the latest Android platform using simple HIDL interfaces to create compelling devices for your customers. @@ -72,28 +72,27 @@ landing_page: image_path: /images/android_stack.png - heading: News items: - - heading: November Security Bulletins + - heading: Android 8.1 Instructions description: > - The November 2017 Android and Pixel/Nexus Security Bulletins have been - published along with links to associated fixes and new build numbers - to support the November security release. + The Android 8.1 release is now available and offers many new features + aimed at device manufacturers and users alike. buttons: - - label: November 8th, 2017 - path: /security/bulletin/2017-11-01 - - heading: ART Faster Native Methods + - label: December 5th, 2017 + path: /setup/site-updates#Dec-2017 + - heading: HIDL Reference Updates description: > - ART offers faster native methods that speed up JNI transitions and - replace the now deprecated <em>!bang JNI</em> notation. + The reference materials for the HAL Interface Description Language + (HIDL) have been updated to reflect the Android 8.1 release. buttons: - - label: October 27th, 2017 - path: /devices/tech/dalvik/improvements#faster-native-methods - - heading: ART Concurrent Compacting GC + - label: December 5th. 2017 + path: /reference/hidl/ + - heading: December Security Bulletins description: > - Android runtime (ART) features a new concurrent compacting garbage - collector (GC) that compacts the heap every time GC runs. + The December 2017 Android and Pixel/Nexus Security Bulletins have been + published to support the December security release. buttons: - - label: October 16th, 2017 - path: /devices/tech/dalvik/improvements#concurrent-compacting-gc + - label: December 4th, 2017 + path: /security/bulletin/2017-12-01 - classname: devsite-landing-row-100 tf-row-centered items: - buttons: diff --git a/en/compatibility/8.1/android-8.1-cdd.html b/en/compatibility/8.1/android-8.1-cdd.html new file mode 100644 index 00000000..52557f99 --- /dev/null +++ b/en/compatibility/8.1/android-8.1-cdd.html @@ -0,0 +1,9442 @@ +<html devsite="" xmlns="http://www.w3.org/1999/xhtml"> + <head> + <title> + Android 8.1 Compatibility Definition + </title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + <h2 id="1_introduction"> + 1. Introduction + </h2> + <p> + This document enumerates the requirements that must be met in order for devices to be compatible with Android 8.1. + </p> + <p> + The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard defined in <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC2119</a>. + </p> + <p> + As used in this document, a “device implementer” or “implementer” is a person or organization developing a hardware/software solution running Android 8.1. A “device implementation” or “implementation is the hardware/software solution so developed. + </p> + <p> + To be considered compatible with Android 8.1, device implementations MUST meet the requirements presented in this Compatibility Definition, including any documents incorporated via reference. + </p> + <p> + Where this definition or the software tests described in <a href="#10_software_compatibility_testing">section 10</a> is silent, ambiguous, or incomplete, it is the responsibility of the device implementer to ensure compatibility with existing implementations. + </p> + <p> + For this reason, the <a href="http://source.android.com/">Android Open Source Project</a> is both the reference and preferred implementation of Android. Device implementers are STRONGLY RECOMMENDED to base their implementations to the greatest extent possible on the “upstream” source code available from the Android Open Source Project. While some components can hypothetically be replaced with alternate implementations, it is STRONGLY RECOMMENDED to not follow this practice, as passing the software tests will become substantially more difficult. It is the implementer’s responsibility to ensure full behavioral compatibility with the standard Android implementation, including and beyond the Compatibility Test Suite. Finally, note that certain component substitutions and modifications are explicitly forbidden by this document. + </p> + <p> + Many of the resources linked to in this document are derived directly or indirectly from the Android SDK and will be functionally identical to the information in that SDK’s documentation. In any cases where this Compatibility Definition or the Compatibility Test Suite disagrees with the SDK documentation, the SDK documentation is considered authoritative. Any technical details provided in the linked resources throughout this document are considered by inclusion to be part of this Compatibility Definition. + </p> + <h3 id="1_1_document_structure"> + 1.1 Document Structure + </h3> + <h4 id="1_1_1_requirements_by_device_type"> + 1.1.1. Requirements by Device Type + </h4> + <p> + <a href="#2_device_types">Section 2</a> contains all the MUST and STRONGLY RECOMMENDED requirements that apply to a specific device type. Each subsection of <a href="#2_device_types">Section 2</a> is dedicated to a specific device type. + </p> + <p> + All the other requirements, that universally apply to any Android device implementations, are listed in the sections after <a href="#2_device_types">Section 2</a>. These requirements are referenced as "Core Requirements" in this document. + </p> + <h4 id="1_1_2_requirement_id"> + 1.1.2. Requirement ID + </h4> + <p> + Requirement ID is assigned for MUST requirements. + </p> + <ul> + <li>The ID is assigned for MUST requirements only. + </li> + <li>STRONGLY RECOMMENDED requirements are marked as [SR] but ID is not assigned. + </li> + <li>The ID consists of : Device Type ID - Condition ID - Requirement ID (e.g. C-0-1). + </li> + </ul> + <p> + Each ID is defined as below: + </p> + <ul> + <li>Device Type ID (see more on <a href="#2_device_types">2. Device Types</a> + <ul> + <li>C: Core (Requirements that are applied to any Android device implementations) + </li> + <li>H: Android Handheld device + </li> + <li>T: Android Television device + </li> + <li>A: Android Automotive implementation + </li> + </ul> + </li> + <li>Condition ID + <ul> + <li>When the requirement is unconditional, this ID is set as 0. + </li> + <li>When the requirement is conditional, 1 is assinged for the 1st condition and the number increments by 1 within the same section and the same device type. + </li> + </ul> + </li> + <li>Requirement ID + <ul> + <li>This ID starts from 1 and increments by 1 within the same section and the same condition. + </li> + </ul> + </li> + </ul> + <h2 id="2_device_types"> + 2. Device Types + </h2> + <p> + While the Android Open Source Project provides a software stack that can be used for a variety of device types and form factors, there are a few device types that have a relatively better established application distribution ecosystem. + </p> + <p> + This section describes those device types, and additional requirements and recommendations applicable for each device type. + </p> + <p> + All Android device implementations that do not fit into any of the described device types MUST still meet all requirements in the other sections of this Compatibility Definition. + </p> + <h3 id="2_1_device_configurations"> + 2.1 Device Configurations + </h3> + <p> + For the major differences in hardware configuration by device type, see the device-specific requirements that follow in this section. + </p> + <h3 id="2_2_handheld_requirements"> + 2.2. Handheld Requirements + </h3> + <p> + An <strong>Android Handheld device</strong> refers to an Android device implementation that is typically used by holding it in the hand, such as an mp3 player, phone, or tablet. + </p> + <p> + Android device implementations are classified as a Handheld if they meet all the following criteria: + </p> + <ul> + <li>Have a power source that provides mobility, such as a battery. + </li> + <li>Have a physical diagonal screen size in the range of 2.5 to 8 inches. + </li> + </ul> + <p> + The additional requirements in the rest of this section are specific to Android Handheld device implementations. + </p> + <div class="note"> + <b>Note:</b> Requirements that do not apply to Android Tablet devices are marked with an *. + </div> + <h4 id="2_2_1_hardware"> + 2.2.1. Hardware + </h4> + <p> + <strong>Screen Size (Section 7.1.1.1)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST have a screen at least 2.5 inches in physical diagonal size.<sup>*</sup> + </li> + </ul> + <p> + <strong>Screen Density (Section 7.1.1.3)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-SR] Are STRONGLY RECOMMENDED to provide users an affordance to change the display size. + </li> + </ul> + <p> + <strong>Legacy Application Compatibility Mode (Section 7.1.5)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST include support for legacy application compatibility mode as implemented by the upstream Android open source code. That is, device implementations MUST NOT alter the triggers or thresholds at which compatibility mode is activated, and MUST NOT alter the behavior of the compatibility mode itself. + </li> + </ul> + <p> + <strong>Keyboard (Section 7.2.1)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST include support for third-party Input Method Editor (IME) applications. + </li> + </ul> + <p> + <strong>Navigation Keys (Section 7.2.3)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li> + <p> + [H-0-1] MUST provide the Home, Recents, and Back functions. + </p> + </li> + <li> + <p> + [H-0-2] MUST send both the normal and long press event of the the Back function (<a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK"><code>KEYCODE_BACK</code></a>) to the foreground application. + </p> + </li> + </ul> + <p> + <strong>Touchscreen Input (Section 7.2.4)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST support touchscreen input. + </li> + </ul> + <p> + <strong>Accelerometer (Section 7.3.1)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-SR] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer. + </li> + </ul> + <p> + If Handheld device implementations include a 3-axis accelerometer, they: + </p> + <ul> + <li>[H-1-1] MUST be able to report events up to a frequency of at least 100 Hz. + </li> + </ul> + <p> + <strong>Gyroscope (Section 7.3.4)</strong> + </p> + <p> + If Handheld device implementations include a gyroscope, they: + </p> + <ul> + <li>[H-1-1] MUST be able to report events up to a frequency of at least 100 Hz. + </li> + </ul> + <p> + <strong>Proximity Sensor (Section 7.3.8 )</strong> + </p> + <p> + Handheld device implementations that can make a voice call and indicate any value other than <code>PHONE_TYPE_NONE</code> in <code>getPhoneType</code>: + </p> + <ul> + <li>SHOULD include a proximity sensor. + </li> + </ul> + <p> + <strong>Pose Sensor (Section 7.3.12)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>Are RECOMMENDED to support pose sensor with 6 degrees of freedom. + </li> + </ul> + <p> + <strong>Bluetooth (Section 7.4.3)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>SHOULD include support for Bluetooth and Bluetooth LE. + </li> + </ul> + <p> + <strong>Data Saver (Section 7.4.7)</strong> + </p> + <p> + If Handheld device implementations include a metered connection, they: + </p> + <ul> + <li>[H-1-1] MUST provide the data saver mode. + </li> + </ul> + <p> + <strong>Minimum Memory and Storage (Section 7.6.1)</strong> + </p> + <p> + If Handheld device implementations declare support of only a 32-bit ABI: + </p> + <ul> + <li> + <p> + [H-1-1] The memory available to the kernel and userspace MUST be at least 416MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA). + </p> + </li> + <li> + <p> + [H-2-1] The memory available to the kernel and userspace MUST be at least 592MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA). + </p> + </li> + <li> + <p> + [H-3-1] The memory available to the kernel and userspace MUST be at least 896MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+). + </p> + </li> + <li> + <p> + [H-4-1] The memory available to the kernel and userspace MUST be at least 1344MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA). + </p> + </li> + </ul> + <p> + If Handheld device implementations declare support of 32-bit and 64-bit ABIs: + </p> + <ul> + <li> + <p> + [H-5-1] The memory available to the kernel and userspace MUST be at least 816MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA). + </p> + </li> + <li> + <p> + [H-6-1] The memory available to the kernel and userspace MUST be at least 944MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA). + </p> + </li> + <li> + <p> + [H-7-1] The memory available to the kernel and userspace MUST be at least 1280MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+). + </p> + </li> + <li> + <p> + [H-8-1] The memory available to the kernel and userspace MUST be at least 1824MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA). + </p> + </li> + </ul> + <p> + Note that the "memory available to the kernel and userspace" above refers to the memory space provided in addition to any memory already dedicated to hardware components such as radio, video, and so on that are not under the kernel’s control on device implementations. + </p> + <p> + If Handheld device implementations include less than or equal to 1GB of memory available to the kernel and userspace, they: + </p> + <ul> + <li>[H-9-1] MUST declare the feature flag <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_RAM_LOW"><code>android.hardware.ram.low</code></a>. + </li> + <li>[H-9-2] MUST have at least 1.1 GB of non-volatile storage for application private data (a.k.a. "/data" partition). + </li> + </ul> + <p> + If Handheld device implementations include more than 1GB of memory available to the kernel and userspace, they: + </p> + <ul> + <li>[H-10-1] MUST have at least 4GB of non-volatile storage available for application private data (a.k.a. "/data" partition). + </li> + <li>SHOULD declare the feature flag <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_RAM_NORMAL"><code>android.hardware.ram.normal</code></a>. + </li> + </ul> + <p> + <strong>Application Shared Storage (Section 7.6.2)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST NOT provide an application shared storage smaller than 1 GiB. + </li> + </ul> + <p> + <strong>USB peripheral mode (Section 7.7.1)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>SHOULD include a USB port supporting peripheral mode. + </li> + </ul> + <p> + If handheld device implementations include a USB port supporting peripheral mode, they: + </p> + <ul> + <li>[H-1-1] MUST implement the Android Open Accessory (AOA) API.<sup>*</sup> + </li> + </ul> + <p> + <strong>Microphone (Section 7.8.1)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST include a microphone. + </li> + </ul> + <p> + <strong>Audio Output (Section 7.8.2)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST have an audio output and declare <code>android.hardware.audio.output</code>. + </li> + </ul> + <p> + <strong>Virtual Reality Mode (Section 7.9.1)</strong> + </p> + <p> + If Handheld device implementations include support for the VR mode, they: + </p> + <ul> + <li>[H-1-1] MUST declare the <code>android.software.vr.mode</code> feature.<sup>*</sup> + </li> + </ul> + <p> + If device implementations declare <code>android.software.vr.mode</code> feature, they: + </p> + <ul> + <li>[H-2-1] MUST include an application implementing <code>android.service.vr.VrListenerService</code> that can be enabled by VR applications via <code>android.app.Activity#setVrModeEnabled</code>.<sup>*</sup> + </li> + </ul> + <p> + <strong>Virtual Reality High Performance (Section 7.9.2)</strong> + </p> + <p> + If Handheld device implementations are capable of meeting all the requirements to declare the <code>android.hardware.vr.high_performance</code> feature flag, they: + </p> + <ul> + <li>[H-1-1] MUST declare the <code>android.hardware.vr.high_performance</code> feature flag.<sup>*</sup> + </li> + </ul> + <h4 id="2_2_2_multimedia"> + 2.2.2. Multimedia + </h4> + <p> + <strong>Audio Encoding (Section 5.1.1)</strong> + </p> + <p> + Handheld device implementations MUST support the following audio encoding: + </p> + <ul> + <li>[H-0-1] AMR-NB + </li> + <li>[H-0-2] AMR-WB + </li> + <li>[H-0-3] MPEG-4 AAC Profile (AAC LC) + </li> + <li>[H-0-4] MPEG-4 HE AAC Profile (AAC+) + </li> + <li>[H-0-5] AAC ELD (enhanced low delay AAC) + </li> + </ul> + <p> + <strong>Audio Decoding (Section 5.1.2)</strong> + </p> + <p> + Handheld device implementations MUST support the following audio decoding: + </p> + <ul> + <li>[H-0-1] AMR-NB + </li> + <li>[H-0-2] AMR-WB + </li> + </ul> + <p> + <strong>Video Encoding (Section 5.2)</strong> + </p> + <p> + Handheld device implementations MUST support the following video encoding and make it available to third-party applications: + </p> + <ul> + <li>[H-0-1] H.264 AVC + </li> + <li>[H-0-2] VP8 + </li> + </ul> + <p> + <strong>Video Decoding (Section 5.3)</strong> + </p> + <p> + Handheld device implementations MUST support the following video decoding: + </p> + <ul> + <li>[H-0-1] H.264 AVC. + </li> + <li>[H-0-2] H.265 HEVC. + </li> + <li>[H-0-3] MPEG-4 SP. + </li> + <li>[H-0-4] VP8. + </li> + <li>[H-0-5] VP9. + </li> + </ul> + <h4 id="2_2_3_software"> + 2.2.3. Software + </h4> + <p> + <strong>WebView Compatibility (Section 3.4.1)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST provide a complete implementation of the <code>android.webkit.Webview</code> API. + </li> + </ul> + <p> + <strong>Browser Compatibility (Section 3.4.2)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST include a standalone Browser application for general user web browsing. + </li> + </ul> + <p> + <strong>Launcher (Section 3.8.1)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li> + <p> + [H-SR] Are STRONGLY RECOMMENDED to implement a default launcher that supports in-app pinning of shortcuts and widgets. + </p> + </li> + <li> + <p> + [H-SR] Are STRONGLY RECOMMENDED to implement a default launcher that provides quick access to the additional shortcuts provided by third-party apps through the <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html">ShortcutManager</a> API. + </p> + </li> + <li> + <p> + [H-SR] Are STRONGLY RECOMMENDED to include a default launcher app that shows badges for the app icons. + </p> + </li> + </ul> + <p> + <strong>Widgets (Section 3.8.2)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-SR] Are STRONGLY RECOMMENDED to support third-party app widgets. + </li> + </ul> + <p> + <strong>Notifications (Section 3.8.3)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST allow third-party apps to notify users of notable events through the <a href="https://developer.android.com/reference/android/app/Notification.html"><code>Notification</code></a> and <a href="https://developer.android.com/reference/android/app/NotificationManager.html"><code>NotificationManager</code></a> API classes. + </li> + <li>[H-0-2] MUST support rich notifications. + </li> + <li>[H-0-3] MUST support heads-up notifications. + </li> + <li>[H-0-4] MUST include a notification shade, providing the user the ability to directly control (e.g. reply, snooze, dismiss, block) the notifications through user affordance such as action buttons or the control panel as implemented in the AOSP. + </li> + </ul> + <p> + <strong>Search (Section 3.8.4)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-SR] Are STRONGLY RECOMMENDED to implement an assistant on the device to handle the <a href="http://developer.android.com/reference/android/content/Intent.html#ACTION_ASSIST">Assist action</a>. + </li> + </ul> + <p> + <strong>Lock Screen Media Control (Section 3.8.10)</strong> + </p> + <p> + If Android Handheld device implementations support a lock screen,they: + </p> + <ul> + <li>[H-1-1] MUST display the Lock screen Notifications including the Media Notification Template. + </li> + </ul> + <p> + <strong>Device administration (Section 3.9)</strong> + </p> + <p> + If Handheld device implementations support a secure lock screen, they: + </p> + <ul> + <li>[H-1-1] MUST implement the full range of <a href="http://developer.android.com/guide/topics/admin/device-admin.html">device administration</a> policies defined in the Android SDK documentation. + </li> + </ul> + <p> + <strong>Accessibility (Section 3.10)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li> + <p> + [H-SR] MUST support third-party accessibility services. + </p> + </li> + <li> + <p> + [H-SR] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preloaded Text-to-speech engine) accessibility services as provided in the <a href="https://github.com/google/talkback">talkback open source project</a>. + </p> + </li> + </ul> + <p> + <strong>Text-to-Speech (Section 3.11)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li> + <p> + [H-0-1] MUST support installation of third-party TTS engines. + </p> + </li> + <li> + <p> + [H-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device. + </p> + </li> + </ul> + <p> + <strong>Quick Settings (Section 3.13)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-SR] Are STRONGLY RECOMMENDED to include a Quick Settings UI component. + </li> + </ul> + <p> + <strong>Companion Device Pairing (Section 3.15)</strong> + </p> + <p> + If Android handheld device implementations declare <code>FEATURE_BLUETOOTH</code> or <code>FEATURE_WIFI</code> support, they: + </p> + <ul> + <li>[H-1-1] MUST support the companion device pairing feature. + </li> + </ul> + <h4 id="2_2_4_performance_and_power"> + 2.2.4. Performance and Power + </h4> + <p> + <strong>User Experience Consistency (Section 8.1)</strong> + </p> + <p> + For handheld device implementations: + </p> + <ul> + <li>[H-0-1] <strong>Consistent frame latency</strong>. Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second. + </li> + <li>[H-0-2] <strong>User interface latency</strong>. Device implementations MUST ensure low latency user experience by scrolling a list of 10K list entries as defined by the Android Compatibility Test Suite (CTS) in less than 36 secs. + </li> + <li>[H-0-3] <strong>Task switching</strong>. When multiple applications have been launched, re-launching an already-running application after it has been launched MUST take less than 1 second. + </li> + </ul> + <p> + <strong>File I/O Access Performance (Section 8.2)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST ensure a sequential write performance of at least 5 MB/s. + </li> + <li>[H-0-2] MUST ensure a random write performance of at least 0.5 MB/s. + </li> + <li>[H-0-3] MUST ensure a sequential read performance of at least 15 MB/s. + </li> + <li>[H-0-4] MUST ensure a random read performance of at least 3.5 MB/s. + </li> + </ul> + <p> + <strong>Power-Saving Modes (Section 8.3)</strong> + </p> + <p> + For handheld device implementations: + </p> + <ul> + <li>[H-0-1] All Apps exempted from App Standby and Doze power-saving modes MUST be made visible to the end user. + </li> + <li>[H-0-2] The triggering, maintenance, wakeup algorithms and the use of global system settings of App Standby and Doze power-saving modes MUST not deviate from the Android Open Source Project. + </li> + </ul> + <p> + <strong>Power Consumption Accounting (Sections 8.4)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST provide a per-component power profile that defines the <a href="http://source.android.com/devices/tech/power/values.html">current consumption value</a> for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site. + </li> + <li>[H-0-2] MUST report all power consumption values in milliampere hours (mAh). + </li> + <li>[H-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the <code>uid_cputime</code> kernel module implementation. + </li> + <li>[H-0-4] MUST make this power usage available via the <a href="http://source.android.com/devices/tech/power/batterystats.html"><code>adb shell dumpsys batterystats</code></a> shell command to the app developer. + </li> + <li>SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application. + </li> + </ul> + <p> + If Handheld device implementations include a screen or video output, they: + </p> + <ul> + <li>[H-1-1] MUST honor the <a href="http://developer.android.com/reference/android/content/Intent.html#ACTION_POWER_USAGE_SUMMARY"><code>android.intent.action.POWER_USAGE_SUMMARY</code></a> intent and display a settings menu that shows this power usage. + </li> + </ul> + <h4 id="2_2_5_security_model"> + 2.2.5. Security Model + </h4> + <p> + <strong>Permissions (Sections 9.1)</strong> + </p> + <p> + Handheld device implementations: + </p> + <ul> + <li>[H-0-1] MUST allow third-party apps to access the usage statistics via the <code>android.permission.PACKAGE_USAGE_STATS</code> permission and provide a user-accessible mechanism to grant or revoke access to such apps in response to the <a href="https://developer.android.com/reference/android/provider/Settings.html#ACTION&lowbar;USAGE&lowbar;ACCESS&lowbar;SETTINGS"><code>android.settings.ACTION_USAGE_ACCESS_SETTINGS</code></a> intent. + </li> + </ul> + <h3 id="2_3_television_requirements"> + 2.3. Television Requirements + </h3> + <p> + An <strong>Android Television device</strong> refers to an Android device implementation that is an entertainment interface for consuming digital media, movies, games, apps, and/or live TV for users sitting about ten feet away (a “lean back” or “10-foot user interface”). + </p> + <p> + Android device implementations are classified as a Television if they meet all the following criteria: + </p> + <ul> + <li>Have provided a mechanism to remotely control the rendered user interface on the display that might sit ten feet away from the user. + </li> + <li>Have an embedded screen display with the diagonal length larger than 24 inches OR include a video output port, such as VGA, HDMI, DisplayPort or a wireless port for display. + </li> + </ul> + <p> + The additional requirements in the rest of this section are specific to Android Television device implementations. + </p> + <h4 id="2_3_1_hardware"> + 2.3.1. Hardware + </h4> + <p> + <strong>Non-touch Navigation (Section 7.2.2)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST support <a href="https://developer.android.com/reference/android/content/res/Configuration.html#NAVIGATION_DPAD">D-pad</a>. + </li> + </ul> + <p> + <strong>Navigation Keys (Section 7.2.3)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST provide the Home and Back functions. + </li> + <li>[T-0-2] MUST send both the normal and long press event of the the Back function (<a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK"><code>KEYCODE_BACK</code></a>) to the foreground application. + </li> + </ul> + <p> + <strong>Button Mappings (Section 7.2.6.1)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST include support for game controllers and declare the <code>android.hardware.gamepad</code> feature flag. + </li> + </ul> + <p> + <strong>Remote Control (Section 7.2.7)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>SHOULD provide a remote control from which users can access <a href="#7_2_2_non-touch_navigation">non-touch navigation</a> and <a href="#7_2_3_navigation_keys">core navigation keys</a> inputs. + </li> + </ul> + <p> + <strong>Gyroscope (Section 7.3.4)</strong> + </p> + <p> + If Television device implementations include a gyroscope, they: + </p> + <ul> + <li>[T-1-1] MUST be able to report events up to a frequency of at least 100 Hz. + </li> + </ul> + <p> + <strong>Bluetooth (Section 7.4.3)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST support Bluetooth and Bluetooth LE. + </li> + </ul> + <p> + <strong>Minimum Memory and Storage (Section 7.6.1)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST have at least 4GB of non-volatile storage available for application private data (a.k.a. "/data" partition) + </li> + <li>[T-0-2] MUST return “true” for <code>ActivityManager.isLowRamDevice()</code> when there is less than 1GB of memory available to the kernel and userspace. + </li> + </ul> + <p> + <strong>Microphone (Section 7.8.1)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>SHOULD include a microphone. + </li> + </ul> + <p> + <strong>Audio Output (Section 7.8.2)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST have an audio output and declare <code>android.hardware.audio.output</code>. + </li> + </ul> + <h4 id="2_3_2_multimedia"> + 2.3.2. Multimedia + </h4> + <p> + <strong>Audio Encoding (Section 5.1)</strong> + </p> + <p> + Television device implementations MUST support the following audio encoding: + </p> + <ul> + <li>[T-0-1] MPEG-4 AAC Profile (AAC LC) + </li> + <li>[T-0-2] MPEG-4 HE AAC Profile (AAC+) + </li> + <li>[T-0-3] AAC ELD (enhanced low delay AAC) + </li> + </ul> + <p> + <strong>Video Encoding (Section 5.2)</strong> + </p> + <p> + Television device implementations MUST support the following video encoding: + </p> + <ul> + <li>[T-0-1] H.264 AVC + </li> + <li>[T-0-2] VP8 + </li> + </ul> + <p> + <strong>H-264 (Section 5.2.2)</strong> + </p> + <p> + Television device implementations are: + </p> + <ul> + <li>[T-SR] STRONGLY RECOMMENDED to support H.264 encoding of 720p and 1080p resolution videos. + </li> + <li>[T-SR] STRONGLY RECOMMENDED to support H.264 encoding of 1080p resolution video at 30 frame-per-second (fps). + </li> + </ul> + <p> + <strong>Video Decoding (Section 5.3)</strong> + </p> + <p> + Television device implementations MUST support the following video decoding: + </p> + <ul> + <li>[T-0-1] H.264 AVC + </li> + <li>[T-0-2] H.265 HEVC + </li> + <li>[T-0-3] MPEG-4 SP + </li> + <li>[T-0-4] VP8 + </li> + <li>[T-0-5] VP9 + </li> + </ul> + <p> + Television device implementations are STRONGLY RECOMMENDED to support the following video decoding: + </p> + <ul> + <li>[T-SR] MPEG-2 + </li> + </ul> + <p> + <strong>H.264 (Section 5.3.4)</strong> + </p> + <p> + If Television device implementations support H.264 decoders, they: + </p> + <ul> + <li>[T-1-1] MUST support High Profile Level 4.2 and the HD 1080p (at 60 fps) decoding profile. + </li> + <li>[T-1-2] MUST be capable of decoding videos with both HD profiles as indicated in the following table and encoded with either the Baseline Profile, Main Profile, or the High Profile Level 4.2 + </li> + </ul> + <p> + <strong>H.265 (HEVC) (Section 5.3.5)</strong> + </p> + <p> + If Television device implementations support H.265 codec and the HD 1080p decoding profile, they: + </p> + <ul> + <li>[T-1-1] MUST support the Main Profile Level 4.1 Main tier. + </li> + <li>[T-SR] Are STRONGLY RECOMMENDED to support 60 fps video frame rate for HD 1080p. + </li> + </ul> + <p> + If Television device implementations support H.265 codec and the UHD decoding profile, then: + </p> + <ul> + <li>[T-2-1] The codec MUST support Main10 Level 5 Main Tier profile. + </li> + </ul> + <p> + <strong>VP8 (Section 5.3.6)</strong> + </p> + <p> + If Television device implementations support VP8 codec, they: + </p> + <ul> + <li>[T-1-1] MUST support the HD 1080p60 decoding profile. + </li> + </ul> + <p> + If Television device implementations support VP8 codec and support 720p, they: + </p> + <ul> + <li>[T-2-1] MUST support the HD 720p60 decoding profile. + </li> + </ul> + <p> + <strong>VP9 (Section 5.3.7)</strong> + </p> + <p> + If Television device implementations support VP9 codec and the UHD video decoding, they: + </p> + <ul> + <li>[T-1-1] MUST support 8-bit color depth and SHOULD support VP9 Profile 2 (10-bit). + </li> + </ul> + <p> + If Television device implementations support VP9 codec, the 1080p profile and VP9 hardware decoding, they: + </p> + <ul> + <li>[T-2-1] MUST support 60 fps for 1080p. + </li> + </ul> + <p> + <strong>Secure Media (Section 5.8)</strong> + </p> + <p> + If device implementations are Android Television devices and support 4K resolution, they: + </p> + <ul> + <li>[T-1-1] MUST support HDCP 2.2 for all wired external displays. + </li> + </ul> + <p> + If Television device implementations don't support 4K resolution, they: + </p> + <ul> + <li>[T-2-1] MUST support HDCP 1.4 for all wired external displays. + </li> + </ul> + <p> + Television device implementations: + </p> + <ul> + <li>[T-SR] Are STRONGLY RECOMMENDED to support simulataneous decoding of secure streams. At minimum, simultaneous decoding of two steams is STRONGLY RECOMMENDED. + </li> + </ul> + <p> + <strong>Audio Output Volume (Section 5.5.3)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST include support for system Master Volume and digital audio output volume attenuation on supported outputs, except for compressed audio passthrough output (where no audio decoding is done on the device). + </li> + </ul> + <h4 id="2_3_3_software"> + 2.3.3. Software + </h4> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST declare the features <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_LEANBACK"><code>android.software.leanback</code></a> and <code>android.hardware.type.television</code>. + </li> + </ul> + <p> + <strong>WebView compatibility (Section 3.4.1)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST provide a complete implementation of the <code>android.webkit.Webview</code> API. + </li> + </ul> + <p> + <strong>Lock Screen Media Control (Section 3.8.10)</strong> + </p> + <p> + If Android Television device implementations support a lock screen,they: + </p> + <ul> + <li>[T-1-1] MUST display the Lock screen Notifications including the Media Notification Template. + </li> + </ul> + <p> + <strong>Multi-windows (Section 3.8.14)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-SR] Are STRONGLY RECOMMENDED to support picture-in-picture (PIP) mode multi-window. + </li> + </ul> + <p> + <strong>Accessibility (Section 3.10)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li> + <p> + [T-SR] MUST support third-party accessibility services. + </p> + </li> + <li> + <p> + [T-SR] Android Television device implementations are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preloaded Text-to-speech engine) accessibility services as provided in the <a href="https://github.com/google/talkback">talkback open source project</a>. + </p> + </li> + </ul> + <p> + <strong>Text-to-Speech (Section 3.11)</strong> + </p> + <p> + If device implementations report the feature android.hardware.audio.output, they: + </p> + <ul> + <li> + <p> + [T-SR] STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device. + </p> + </li> + <li> + <p> + [T-0-1] MUST support installation of third-party TTS engines. + </p> + </li> + </ul> + <p> + <strong>TV Input Framework (Section 3.12)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST support TV Input Framework. + </li> + </ul> + <h4 id="2_2_4_performance_and_power"> + 2.2.4. Performance and Power + </h4> + <p> + <strong>User Experience Consistency (Section 8.1)</strong> + </p> + <p> + For Television device implementations: + </p> + <ul> + <li>[T-0-1] <strong>Consistent frame latency</strong>. Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second. + </li> + </ul> + <p> + <strong>File I/O Access Performance (Section 8.2)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST ensure a sequential write performance of at least 5MB/s. + </li> + <li>[T-0-2] MUST ensure a random write performance of at least 0.5MB/s. + </li> + <li>[T-0-3] MUST ensure a sequential read performance of at least 15MB/s. + </li> + <li>[T-0-4] MUST ensure a random read performance of at least 3.5MB/s. + </li> + </ul> + <p> + <strong>Power-Saving Modes (Section 8.3)</strong> + </p> + <p> + For Television device implementations: + </p> + <ul> + <li>[T-0-1] All Apps exempted from App Standby and Doze power-saving modes MUST be made visible to the end user. + </li> + <li>[T-0-2] The triggering, maintenance, wakeup algorithms and the use of global system settings of App Standby and Doze power-saving modes MUST not deviate from the Android Open Source Project. + </li> + </ul> + <p> + <strong>Power Consumption Accounting (Sections 8.4)</strong> + </p> + <p> + Television device implementations: + </p> + <ul> + <li>[T-0-1] MUST provide a per-component power profile that defines the <a href="http://source.android.com/devices/tech/power/values.html">current consumption value</a> for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site. + </li> + <li>[T-0-2] MUST report all power consumption values in milliampere hours (mAh). + </li> + <li>[T-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the <code>uid_cputime</code> kernel module implementation. + </li> + <li>SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application. + </li> + <li>[T-0-4] MUST make this power usage available via the <a href="http://source.android.com/devices/tech/power/batterystats.html"><code>adb shell dumpsys batterystats</code></a> shell command to the app developer. + </li> + </ul> + <h3 id="2_4_watch_requirements"> + 2.4. Watch Requirements + </h3> + <p> + An <strong>Android Watch device</strong> refers to an Android device implementation intended to be worn on the body, perhaps on the wrist. + </p> + <p> + Android device implementations are classified as a Watch if they meet all the following criteria: + </p> + <ul> + <li>Have a screen with the physical diagonal length in the range from 1.1 to 2.5 inches. + </li> + <li>Have a mechanism provided to be worn on the body. + </li> + </ul> + <p> + The additional requirements in the rest of this section are specific to Android Watch device implementations. + </p> + <h4 id="2_4_1_hardware"> + 2.4.1. Hardware + </h4> + <p> + <strong>Screen Size (Section 7.1.1.1)</strong> + </p> + <p> + Watch device implementations: + </p> + <ul> + <li>[W-0-1] MUST have a screen with the physical diagonal size in the range from 1.1 to 2.5 inches. + </li> + </ul> + <p> + <strong>Navigation Keys (Section 7.2.3)</strong> + </p> + <p> + Watch device implementations: + </p> + <ul> + <li>[W-0-1] MUST have the Home function available to the user, and the Back function except for when it is in <code>UI_MODE_TYPE_WATCH</code>. + </li> + </ul> + <p> + <strong>Touchscreen Input (Section 7.2.4)</strong> + </p> + <p> + Watch device implementations: + </p> + <ul> + <li>[W-0-2] MUST support touchscreen input. + </li> + </ul> + <p> + <strong>Accelerometer (Section 7.3.1)</strong> + </p> + <p> + Watch device implementations: + </p> + <ul> + <li>[W-SR] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer. + </li> + </ul> + <p> + <strong>Bluetooth (Section 7.4.3)</strong> + </p> + <p> + Watch device implementations: + </p> + <ul> + <li>[W-0-1] MUST support Bluetooth. + </li> + </ul> + <p> + <strong>Minimum Memory and Storage (Section 7.6.1)</strong> + </p> + <p> + Watch device implementations: + </p> + <ul> + <li>[W-0-1] MUST have at least 1GB of non-volatile storage available for application private data (a.k.a. "/data" partition) + </li> + <li>[W-0-2] MUST have at least 416MB memory available to the kernel and userspace. + </li> + </ul> + <p> + <strong>Microphone (Section 7.8.1)</strong> + </p> + <p> + Watch device implementations: + </p> + <ul> + <li>[W-0-1] MUST include a microphone. + </li> + </ul> + <p> + <strong>Audio Output (Section 7.8.1)</strong> + </p> + <p> + Watch device implementations: + </p> + <ul> + <li>MAY but SHOULD NOT have audio output. + </li> + </ul> + <h4 id="2_4_2_multimedia"> + 2.4.2. Multimedia + </h4> + <p> + No additional requirements. + </p> + <h4 id="2_4_3_software"> + 2.4.3. Software + </h4> + <p> + Watch device implementations: + </p> + <ul> + <li>[W-0-1] MUST declare the feature android.hardware.type.watch. + </li> + <li>[W-0-2] MUST support uiMode = <a href="http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_WATCH">UI_MODE_TYPE_WATCH</a>. + </li> + </ul> + <p> + <strong>Search (Section 3.8.4)</strong> + </p> + <p> + Watch device implementations: + </p> + <ul> + <li>[W-SR] Are STRONGLY RECOMMENDED to implement an assistant on the device to handle the <a href="http://developer.android.com/reference/android/content/Intent.html#ACTION_ASSIST">Assist action</a>. + </li> + </ul> + <p> + <strong>Accessibility (Section 3.10)</strong> + </p> + <p> + Watch device implementations that declare the <code>android.hardware.audio.output</code> feature flag: + </p> + <ul> + <li> + <p> + [W-1-1] MUST support third-party accessibility services. + </p> + </li> + <li> + <p> + [W-SR] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preloaded Text-to-speech engine) accessibility services as provided in the <a href="https://github.com/google/talkback">talkback open source project</a>. + </p> + </li> + </ul> + <p> + <strong>Text-to-Speech (Section 3.11)</strong> + </p> + <p> + If Watch device implementations report the feature android.hardware.audio.output, they: + </p> + <ul> + <li> + <p> + [W-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device. + </p> + </li> + <li> + <p> + [W-0-1] MUST support installation of third-party TTS engines. + </p> + </li> + </ul> + <h3 id="2_5_automotive_requirements"> + 2.5. Automotive Requirements + </h3> + <p> + <strong>Android Automotive implementation</strong> refers to a vehicle head unit running Android as an operating system for part or all of the system and/or infotainment functionality. + </p> + <p> + Android device implementations are classified as an Automotive if they declare the feature <code>android.hardware.type.automotive</code> or meet all the following criteria. + </p> + <ul> + <li>Are embedded as part of, or pluggable to, an automotive vehicle. + </li> + <li>Are using a screen in the driver's seat row as the primary display. + </li> + </ul> + <p> + The additional requirements in the rest of this section are specific to Android Automotive device implementations. + </p> + <h4 id="2_5_1_hardware"> + 2.5.1. Hardware + </h4> + <p> + <strong>Screen Size (Section 7.1.1.1)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST have a screen at least 6 inches in physical diagonal size. + </li> + <li>[A-0-2] MUST have a screen size layout of at least 750 dp x 480 dp. + </li> + </ul> + <p> + <strong>Navigation Keys (Section 7.2.3)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST provide the Home function and MAY provide Back and Recent functions. + </li> + <li>[A-0-2] MUST send both the normal and long press event of the the Back function (<a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK"><code>KEYCODE_BACK</code></a>) to the foreground application. + </li> + </ul> + <p> + <strong>Accelerometer (Section 7.3.1)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-SR] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer. + </li> + </ul> + <p> + If Automotive device implementations include a 3-axis accelerometer, they: + </p> + <ul> + <li>[A-1-1] MUST be able to report events up to a frequency of at least 100 Hz. + </li> + <li>[A-1-2] MUST comply with the Android <a href="http://source.android.com/devices/sensors/sensor-types.html#auto_axes">car sensor coordinate system</a>. + </li> + </ul> + <p> + <strong>GPS (Section 7.3.3)</strong> + </p> + <p> + If Automotive device implementations include a GPS/GNSS receiver and report the capability to applications through the <code>android.hardware.location.gps</code> feature flag: + </p> + <ul> + <li>[A-1-1] GNSS technology generation MUST be the year "2017" or newer. + </li> + </ul> + <p> + <strong>Gyroscope (Section 7.3.4)</strong> + </p> + <p> + If Automotive device implementations include a gyroscope, they: + </p> + <ul> + <li>[A-1-1] MUST be able to report events up to a frequency of at least 100 Hz. + </li> + </ul> + <p> + <strong>Android Automotive-only sensors (Section 7.3.11)</strong> <strong>Current Gear (Section 7.3.11.1)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>SHOULD provide current gear as <code>SENSOR_TYPE_GEAR</code>. + </li> + </ul> + <p> + <strong>Day Night Mode (Section 7.3.11.2)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST support day/night mode defined as <code>SENSOR_TYPE_NIGHT</code>. + </li> + <li>[A-0-2] The value of the <code>SENSOR_TYPE_NIGHT</code> flag MUST be consistent with dashboard day/night mode and SHOULD be based on ambient light sensor input. + </li> + <li>The underlying ambient light sensor MAY be the same as <a href="#7_3_7_photometer">Photometer</a>. + </li> + </ul> + <p> + <strong>Driving Status (Section 7.3.11.3)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST support driving status defined as <code>SENSOR_TYPE_DRIVING_STATUS</code>, with a default value of <code>DRIVE_STATUS_UNRESTRICTED</code> when the vehicle is fully stopped and parked. It is the responsibility of device manufacturers to configure <code>SENSOR_TYPE_DRIVING_STATUS</code> in compliance with all laws and regulations that apply to markets where the product is shipping. + </li> + </ul> + <p> + <strong>Wheel Speed (Section 7.3.11.4)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST provide vehicle speed defined as <code>SENSOR_TYPE_CAR_SPEED</code>. + </li> + </ul> + <p> + <strong>Bluetooth (Section 7.4.3)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li> + <p> + [A-0-1] MUST support Bluetooth and SHOULD support Bluetooth LE. + </p> + </li> + <li> + <p> + [A-0-2] Android Automotive implementations MUST support the following Bluetooth profiles: + </p> + <ul> + <li>Phone calling over Hands-Free Profile (HFP). + </li> + <li>Media playback over Audio Distribution Profile (A2DP). + </li> + <li>Media playback control over Remote Control Profile (AVRCP). + </li> + <li>Contact sharing using the Phone Book Access Profile (PBAP). + </li> + </ul> + </li> + <li>SHOULD support Message Access Profile (MAP). + </li> + </ul> + <p> + <strong>Minimum Network Capability (Section 7.4.5)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>SHOULD include support for cellular network based data connectivity. + </li> + </ul> + <p> + <strong>Minimum Memory and Storage (Section 7.6.1)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST have at least 4GB of non-volatile storage available for application private data (a.k.a. "/data" partition) + </li> + </ul> + <p> + <strong>USB peripheral mode (Section 7.7.1)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>SHOULD include a USB port supporting peripheral mode. + </li> + </ul> + <p> + <strong>Microphone (Section 7.8.1)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST include a microphone. + </li> + </ul> + <p> + <strong>Audio Output (Section 7.8.2)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST have an audio output and declare <code>android.hardware.audio.output</code>. + </li> + </ul> + <h4 id="2_5_2_multimedia"> + 2.5.2. Multimedia + </h4> + <p> + <strong>Audio Encoding (Section 5.1)</strong> + </p> + <p> + Automotive device implementations MUST support the following audio encoding: + </p> + <ul> + <li>[A-1-1] MPEG-4 AAC Profile (AAC LC) + </li> + <li>[A-1-2] MPEG-4 HE AAC Profile (AAC+) + </li> + <li>[A-1-3] AAC ELD (enhanced low delay AAC) + </li> + </ul> + <p> + <strong>Video Encoding (Section 5.2)</strong> + </p> + <p> + Automotive device implementations MUST support the following video encoding: + </p> + <ul> + <li>[A-0-1] H.264 AVC + </li> + <li>[A-0-2] VP8 + </li> + </ul> + <p> + <strong>Video Decoding (Section 5.3)</strong> + </p> + <p> + Automotive device implementations MUST support the following video decoding: + </p> + <ul> + <li>[A-0-1] H.264 AVC + </li> + <li>[A-0-2] MPEG-4 SP + </li> + <li>[A-0-3] VP8 + </li> + <li>[A-0-4] VP9 + </li> + </ul> + <p> + Automotive device implementations are STRONGLY RECOMMENDED to support the following video decoding: + </p> + <ul> + <li>[A-SR] H.265 HEVC + </li> + </ul> + <h4 id="2_5_3_software"> + 2.5.3. Software + </h4> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST declare the feature android.hardware.type.automotive. + </li> + <li>[A-0-2] MUST support uiMode = <a href="http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_CAR">UI_MODE_TYPE_CAR</a>. + </li> + <li>[A-0-3] Android Automotive implementations MUST support all public APIs in the <code>android.car.*</code> namespace. + </li> + </ul> + <p> + <strong>WebView Compatibility (Section 3.4.1)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST provide a complete implementation of the <code>android.webkit.Webview API</code>. + </li> + </ul> + <p> + <strong>Notifications (Section 3.8.3)</strong> + </p> + <p> + Android Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST display notifications that use the <a href="https://developer.android.com/reference/android/app/Notification.CarExtender.html"><code>Notification.CarExtender</code></a> API when requested by third-party applications. + </li> + </ul> + <p> + <strong>Search (Section 3.8.4)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST implement an assistant on the device to handle the <a href="http://developer.android.com/reference/android/content/Intent.html#ACTION_ASSIST">Assist action</a>. + </li> + </ul> + <p> + <strong>Media UI (Section 3.14)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST include a UI framework to support third-party apps using the media APIs as described in section 3.14. + </li> + </ul> + <h4 id="2_2_4_performance_and_power"> + 2.2.4. Performance and Power + </h4> + <p> + <strong>Power-Saving Modes (Section 8.3)</strong> + </p> + <p> + For Automotive device implementations: + </p> + <ul> + <li>[A-0-1] All Apps exempted from App Standby and Doze power-saving modes MUST be made visible to the end user. + </li> + <li>[A-0-2] The triggering, maintenance, wakeup algorithms and the use of global system settings of App Standby and Doze power-saving modes MUST not deviate from the Android Open Source Project. + </li> + </ul> + <p> + <strong>Power Consumption Accounting (Sections 8.4)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST provide a per-component power profile that defines the <a href="http://source.android.com/devices/tech/power/values.html">current consumption value</a> for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site. + </li> + <li>[A-0-2] MUST report all power consumption values in milliampere hours (mAh). + </li> + <li>[A-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the <code>uid_cputime</code> kernel module implementation. + </li> + <li>SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application. + </li> + <li>[A-0-4] MUST make this power usage available via the <a href="http://source.android.com/devices/tech/power/batterystats.html"><code>adb shell dumpsys batterystats</code></a> shell command to the app developer. + </li> + </ul> + <h4 id="2_2_5_security_model"> + 2.2.5. Security Model + </h4> + <p> + <strong>Multi-User Support (Section 9.5)</strong> + </p> + <p> + If Automotive device implementations include multiple users, they: + </p> + <ul> + <li>[A-1-1] MUST include a guest account that allows all functions provided by the vehicle system without requiring a user to log in. + </li> + </ul> + <p> + <strong>Automotive Vehicle System Isolation (Section 9.14)</strong> + </p> + <p> + Automotive device implementations: + </p> + <ul> + <li>[A-0-1] MUST gatekeep messages from Android framework vehicle subsystems, e.g., whitelisting permitted message types and message sources. + </li> + <li>[A-0-2] MUST watchdog against denial of service attacks from the Android framework or third-party apps. This guards against malicious software flooding the vehicle network with traffic, which may lead to malfunctioning vehicle subsystems. + </li> + </ul> + <h3 id="2_6_tablet_requirements"> + 2.6. Tablet Requirements + </h3> + <p> + An <strong>Android Tablet device</strong> refers to an Android device implementation that is typically used by holding in both hands and not in a clamshell form-factor. + </p> + <p> + Android device implementations are classified as a Tablet if they meet all the following criteria: + </p> + <ul> + <li>Have a power source that provides mobility, such as a battery. + </li> + <li>Have a physical diagonal screen size in the range of 7 to 18 inches. + </li> + </ul> + <p> + Tablet device implementations have similar requirements to handheld device implementations. The exceptions are in indicated by and * in that section and noted for reference in this section. + </p> + <h4 id="2_4_1_hardware"> + 2.4.1. Hardware + </h4> + <p> + <strong>Screen Size (Section 7.1.1.1)</strong> + </p> + <p> + Tablet device implementations: + </p> + <ul> + <li>[Ta-0-1] MUST have a screen in the range of 7 to 18 inches. + </li> + </ul> + <p> + <strong>Minimum Memory and Storage (Section 7.6.1)</strong> + </p> + <p> + The screen densities listed for small/normal screens in the handheld requirements are not applicable to tablets. + </p> + <p> + <strong>USB peripheral mode (Section 7.7.1)</strong> + </p> + <p> + If handheld device implementations include a USB port supporting peripheral mode, they: + </p> + <ul> + <li>MAY implement the Android Open Accessory (AOA) API. + </li> + </ul> + <p> + <strong>Virtual Reality Mode (Section 7.9.1)</strong> + </p> + <p> + <strong>Virtual Reality High Performance (Section 7.9.2)</strong> + </p> + <p> + Virtual reality requirements are not applicable to tablets. + </p> + <h2 id="3_software"> + 3. Software + </h2> + <h3 id="3_1_managed_api_compatibility"> + 3.1. Managed API Compatibility + </h3> + <p> + The managed Dalvik bytecode execution environment is the primary vehicle for Android applications. The Android application programming interface (API) is the set of Android platform interfaces exposed to applications running in the managed runtime environment. + </p> + <ul> + <li> + <p> + [C-0-1] Device implementations MUST provide complete implementations, including all documented behaviors, of any documented API exposed by the <a href="http://developer.android.com/reference/packages.html">Android SDK</a> or any API decorated with the “@SystemApi” marker in the upstream Android source code. + </p> + </li> + <li> + <p> + [C-0-2] Device implementations MUST support/preserve all classes, methods, and associated elements marked by the TestApi annotation (@TestApi). + </p> + </li> + <li> + <p> + [C-0-3] Device implementations MUST NOT omit any managed APIs, alter API interfaces or signatures, deviate from the documented behavior, or include no-ops, except where specifically allowed by this Compatibility Definition. + </p> + </li> + <li> + <p> + [C-0-4] Device implementations MUST still keep the APIs present and behave in a reasonable way, even when some hardware features for which Android includes APIs are omitted. See <a href="#7_hardware_compatibility">section 7</a> for specific requirements for this scenario. + </p> + </li> + </ul> + <h3 id="3_1_1_android_extensions"> + 3.1.1. Android Extensions + </h3> + <p> + Android includes the support of extending the managed APIs while keeping the same API level version. + </p> + <ul> + <li>[C-0-1] Android device implementations MUST preload the AOSP implementation of both the shared library <code>ExtShared</code> and services <code>ExtServices</code> with versions higher than or equal to the minimum versions allowed per each API level. For example, Android 7.0 device implementations, running API level 24 MUST include at least version 1. + </li> + </ul> + <h3 id="3_2_soft_api_compatibility"> + 3.2. Soft API Compatibility + </h3> + <p> + In addition to the managed APIs from <a href="#3_1_managed_api_compatibility">section 3.1</a>, Android also includes a significant runtime-only “soft” API, in the form of such things as intents, permissions, and similar aspects of Android applications that cannot be enforced at application compile time. + </p> + <h4 id="3_2_1_permissions"> + 3.2.1. Permissions + </h4> + <ul> + <li>[C-0-1] Device implementers MUST support and enforce all permission constants as documented by the <a href="http://developer.android.com/reference/android/Manifest.permission.html">Permission reference page</a>. Note that <a href="#9_security_model_compatibility">section 9</a> lists additional requirements related to the Android security model. + </li> + </ul> + <h4 id="3_2_2_build_parameters"> + 3.2.2. Build Parameters + </h4> + <p> + The Android APIs include a number of constants on the <a href="http://developer.android.com/reference/android/os/Build.html">android.os.Build class</a> that are intended to describe the current device. + </p> + <ul> + <li>[C-0-1] To provide consistent, meaningful values across device implementations, the table below includes additional restrictions on the formats of these values to which device implementations MUST conform. + </li> + </ul> + <table> + <tr> + <th> + Parameter + </th> + <th> + Details + </th> + </tr> + <tr> + <td> + VERSION.RELEASE + </td> + <td> + The version of the currently-executing Android system, in human-readable format. This field MUST have one of the string values defined in <a href="http://source.android.com/compatibility/8.1/versions.html">8.1</a>. + </td> + </tr> + <tr> + <td> + VERSION.SDK + </td> + <td> + The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 8.1, this field MUST have the integer value 8.1_INT. + </td> + </tr> + <tr> + <td> + VERSION.SDK_INT + </td> + <td> + The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 8.1, this field MUST have the integer value 8.1_INT. + </td> + </tr> + <tr> + <td> + VERSION.INCREMENTAL + </td> + <td> + A value chosen by the device implementer designating the specific build of the currently-executing Android system, in human-readable format. This value MUST NOT be reused for different builds made available to end users. A typical use of this field is to indicate which build number or source-control change identifier was used to generate the build. There are no requirements on the specific format of this field, except that it MUST NOT be null or the empty string (""). + </td> + </tr> + <tr> + <td> + BOARD + </td> + <td> + A value chosen by the device implementer identifying the specific internal hardware used by the device, in human-readable format. A possible use of this field is to indicate the specific revision of the board powering the device. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression “^[a-zA-Z0-9_-]+$”. + </td> + </tr> + <tr> + <td> + BRAND + </td> + <td> + A value reflecting the brand name associated with the device as known to the end users. MUST be in human-readable format and SHOULD represent the manufacturer of the device or the company brand under which the device is marketed. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression “^[a-zA-Z0-9_-]+$”. + </td> + </tr> + <tr> + <td> + SUPPORTED_ABIS + </td> + <td> + The name of the instruction set (CPU type + ABI convention) of native code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>. + </td> + </tr> + <tr> + <td> + SUPPORTED_32_BIT_ABIS + </td> + <td> + The name of the instruction set (CPU type + ABI convention) of native code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>. + </td> + </tr> + <tr> + <td> + SUPPORTED_64_BIT_ABIS + </td> + <td> + The name of the second instruction set (CPU type + ABI convention) of native code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>. + </td> + </tr> + <tr> + <td> + CPU_ABI + </td> + <td> + The name of the instruction set (CPU type + ABI convention) of native code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>. + </td> + </tr> + <tr> + <td> + CPU_ABI2 + </td> + <td> + The name of the second instruction set (CPU type + ABI convention) of native code. See <a href="#3_3_native_api_compatibility">section 3.3. Native API Compatibility</a>. + </td> + </tr> + <tr> + <td> + DEVICE + </td> + <td> + A value chosen by the device implementer containing the development name or code name identifying the configuration of the hardware features and industrial design of the device. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression “^[a-zA-Z0-9_-]+$”. This device name MUST NOT change during the lifetime of the product. + </td> + </tr> + <tr> + <td> + FINGERPRINT + </td> + <td> + A string that uniquely identifies this build. It SHOULD be reasonably human-readable. It MUST follow this template: + <p class="small"> + $(BRAND)/$(PRODUCT)/<br /> + $(DEVICE):$(VERSION.RELEASE)/$(ID)/$(VERSION.INCREMENTAL):$(TYPE)/$(TAGS) + </p> + <p> + For example: + </p> + <p class="small"> + acme/myproduct/<br /> + mydevice:8.1/LMYXX/3359:userdebug/test-keys + </p> + <p> + The fingerprint MUST NOT include whitespace characters. If other fields included in the template above have whitespace characters, they MUST be replaced in the build fingerprint with another character, such as the underscore ("_") character. The value of this field MUST be encodable as 7-bit ASCII. + </p> + </td> + </tr> + <tr> + <td> + HARDWARE + </td> + <td> + The name of the hardware (from the kernel command line or /proc). It SHOULD be reasonably human-readable. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression “^[a-zA-Z0-9_-]+$”. + </td> + </tr> + <tr> + <td> + HOST + </td> + <td> + A string that uniquely identifies the host the build was built on, in human-readable format. There are no requirements on the specific format of this field, except that it MUST NOT be null or the empty string (""). + </td> + </tr> + <tr> + <td> + ID + </td> + <td> + An identifier chosen by the device implementer to refer to a specific release, in human-readable format. This field can be the same as android.os.Build.VERSION.INCREMENTAL, but SHOULD be a value sufficiently meaningful for end users to distinguish between software builds. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression “^[a-zA-Z0-9._-]+$”. + </td> + </tr> + <tr> + <td> + MANUFACTURER + </td> + <td> + The trade name of the Original Equipment Manufacturer (OEM) of the product. There are no requirements on the specific format of this field, except that it MUST NOT be null or the empty string (""). This field MUST NOT change during the lifetime of the product. + </td> + </tr> + <tr> + <td> + MODEL + </td> + <td> + A value chosen by the device implementer containing the name of the device as known to the end user. This SHOULD be the same name under which the device is marketed and sold to end users. There are no requirements on the specific format of this field, except that it MUST NOT be null or the empty string (""). This field MUST NOT change during the lifetime of the product. + </td> + </tr> + <tr> + <td> + PRODUCT + </td> + <td> + A value chosen by the device implementer containing the development name or code name of the specific product (SKU) that MUST be unique within the same brand. MUST be human-readable, but is not necessarily intended for view by end users. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression “^[a-zA-Z0-9_-]+$”. This product name MUST NOT change during the lifetime of the product. + </td> + </tr> + <tr> + <td> + SERIAL + </td> + <td> + A hardware serial number, which MUST be available and unique across devices with the same MODEL and MANUFACTURER. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression “^([a-zA-Z0-9]{6,20})$”. + </td> + </tr> + <tr> + <td> + TAGS + </td> + <td> + A comma-separated list of tags chosen by the device implementer that further distinguishes the build. This field MUST have one of the values corresponding to the three typical Android platform signing configurations: release-keys, dev-keys, test-keys. + </td> + </tr> + <tr> + <td> + TIME + </td> + <td> + A value representing the timestamp of when the build occurred. + </td> + </tr> + <tr> + <td> + TYPE + </td> + <td> + A value chosen by the device implementer specifying the runtime configuration of the build. This field MUST have one of the values corresponding to the three typical Android runtime configurations: user, userdebug, or eng. + </td> + </tr> + <tr> + <td> + USER + </td> + <td> + A name or user ID of the user (or automated user) that generated the build. There are no requirements on the specific format of this field, except that it MUST NOT be null or the empty string (""). + </td> + </tr> + <tr> + <td> + SECURITY_PATCH + </td> + <td> + A value indicating the security patch level of a build. It MUST signify that the build is not in any way vulnerable to any of the issues described up through the designated Android Public Security Bulletin. It MUST be in the format [YYYY-MM-DD], matching a defined string documented in the <a href="source.android.com/security/bulletin">Android Public Security Bulletin</a> or in the <a href="http://source.android.com/security/advisory">Android Security Advisory</a>, for example "2015-11-01". + </td> + </tr> + <tr> + <td> + BASE_OS + </td> + <td> + A value representing the FINGERPRINT parameter of the build that is otherwise identical to this build except for the patches provided in the Android Public Security Bulletin. It MUST report the correct value and if such a build does not exist, report an empty string (""). + </td> + </tr> + <tr> + <td> + <a href="https://developer.android.com/reference/android/os/Build.html#BOOTLOADER">BOOTLOADER</a> + </td> + <td> + A value chosen by the device implementer identifying the specific internal bootloader version used in the device, in human-readable format. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression “^[a-zA-Z0-9._-]+$”. + </td> + </tr> + <tr> + <td> + <a href="https://developer.android.com/reference/android/os/Build.html#getRadioVersion()">getRadioVersion()</a> + </td> + <td> + MUST (be or return) a value chosen by the device implementer identifying the specific internal radio/modem version used in the device, in human-readable format. If a device does not have any internal radio/modem it MUST return NULL. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression “^[a-zA-Z0-9._-,]+$”. + </td> + </tr> + </table> + <h4 id="3_2_3_intent_compatibility"> + 3.2.3. Intent Compatibility + </h4> + <h5 id="3_2_3_1_core_application_intents"> + 3.2.3.1. Core Application Intents + </h5> + <p> + Android intents allow application components to request functionality from other Android components. The Android upstream project includes a list of applications considered core Android applications, which implements several intent patterns to perform common actions. + </p> + <ul> + <li> + <p> + [C-0-1] Device implementations MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following core android applications in AOSP: + </p> + <ul> + <li>Desk Clock + </li> + <li>Browser + </li> + <li>Calendar + </li> + <li>Contacts + </li> + <li>Gallery + </li> + <li>GlobalSearch + </li> + <li>Launcher + </li> + <li>Music + </li> + <li>Settings + </li> + </ul> + </li> + </ul> + <h5 id="3_2_3_2_intent_resolution"> + 3.2.3.2. Intent Resolution + </h5> + <ul> + <li>[C-0-1] As Android is an extensible platform, device implementations MUST allow each intent pattern referenced in <a href="#3_2_3_1_core_application_intents">section 3.2.3.1</a> to be overridden by third-party applications. The upstream Android open source implementation allows this by default. + </li> + <li> + <p> + [C-0-2] Dvice implementers MUST NOT attach special privileges to system applications' use of these intent patterns, or prevent third-party applications from binding to and assuming control of these patterns. This prohibition specifically includes but is not limited to disabling the “Chooser” user interface that allows the user to select between multiple applications that all handle the same intent pattern. + </p> + </li> + <li> + <p> + [C-0-3] Device implementations MUST provide a user interface for users to modify the default activity for intents. + </p> + </li> + <li> + <p> + However, device implementations MAY provide default activities for specific URI patterns (e.g. http://play.google.com) when the default activity provides a more specific attribute for the data URI. For example, an intent filter pattern specifying the data URI “http://www.android.com” is more specific than the browser's core intent pattern for “http://”. + </p> + </li> + </ul> + <p> + Android also includes a mechanism for third-party apps to declare an authoritative default <a href="https://developer.android.com/training/app-links">app linking behavior</a> for certain types of web URI intents. When such authoritative declarations are defined in an app's intent filter patterns, device implementations: + </p> + <ul> + <li>[C-0-4] MUST attempt to validate any intent filters by performing the validation steps defined in the <a href="https://developers.google.com/digital-asset-links">Digital Asset Links specification</a> as implemented by the Package Manager in the upstream Android Open Source Project. + </li> + <li>[C-0-5] MUST attempt validation of the intent filters during the installation of the application and set all successfully validated UIR intent filters as default app handlers for their UIRs. + </li> + <li>MAY set specific URI intent filters as default app handlers for their URIs, if they are successfully verified but other candidate URI filters fail verification. If a device implementation does this, it MUST provide the user appropriate per-URI pattern overrides in the settings menu. + </li> + <li>MUST provide the user with per-app App Links controls in Settings as follows: + <ul> + <li>[C-0-6] The user MUST be able to override holistically the default app links behavior for an app to be: always open, always ask, or never open, which must apply to all candidate URI intent filters equally. + </li> + <li>[C-0-7] The user MUST be able to see a list of the candidate URI intent filters. + </li> + <li>The device implementation MAY provide the user with the ability to override specific candidate URI intent filters that were successfully verified, on a per-intent filter basis. + </li> + <li>[C-0-8] The device implementation MUST provide users with the ability to view and override specific candidate URI intent filters if the device implementation lets some candidate URI intent filters succeed verification while some others can fail. + </li> + </ul> + </li> + </ul> + <h5 id="3_2_3_3_intent_namespaces"> + 3.2.3.3. Intent Namespaces + </h5> + <ul> + <li>[C-0-1] Device implementations MUST NOT include any Android component that honors any new intent or broadcast intent patterns using an ACTION, CATEGORY, or other key string in the android. <em>or com.android.</em> namespace. + </li> + <li>[C-0-2] Device implementers MUST NOT include any Android components that honor any new intent or broadcast intent patterns using an ACTION, CATEGORY, or other key string in a package space belonging to another organization. + </li> + <li>[C-0-3] Device implementers MUST NOT alter or extend any of the intent patterns used by the core apps listed in <a href="#3_2_3_1_core_application_intents">section 3.2.3.1</a>. + </li> + <li>Device implementations MAY include intent patterns using namespaces clearly and obviously associated with their own organization. This prohibition is analogous to that specified for Java language classes in <a href="#3_6_api_namespaces">section 3.6</a>. + </li> + </ul> + <h5 id="3_2_3_4_broadcast_intents"> + 3.2.3.4. Broadcast Intents + </h5> + <p> + Third-party applications rely on the platform to broadcast certain intents to notify them of changes in the hardware or software environment. + </p> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST broadcast the public broadcast intents in response to appropriate system events as described in the SDK documentation. Note that this requirement is not conflicting with section 3.5 as the limitation for background applications are also described in the SDK documentation. + </li> + </ul> + <h5 id="3_2_3_5_default_app_settings"> + 3.2.3.5. Default App Settings + </h5> + <p> + Android includes settings that provide users an easy way to select their default applications, for example for Home screen or SMS. + </p> + <p> + Where it makes sense, device implementations MUST provide a similar settings menu and be compatible with the intent filter pattern and API methods described in the SDK documentation as below. + </p> + <p> + If device implementations report <code>android.software.home_screen</code>, they: + </p> + <ul> + <li>[C-1-1] MUST honor the <a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_HOME_SETTINGS"><code>android.settings.HOME_SETTINGS</code></a> intent to show a default app settings menu for Home Screen. + </li> + </ul> + <p> + If device implementations report <code>android.hardware.telephony</code>, they: + </p> + <ul> + <li> + <p> + [C-2-1] MUST provide a settings menu that will call the <a href="http://developer.android.com/reference/android/provider/Telephony.Sms.Intents.html"><code>android.provider.Telephony.ACTION_CHANGE_DEFAULT</code></a> intent to show a dialog to change the default SMS application. + </p> + </li> + <li> + <p> + [C-2-2] MUST honor the <a href="https://developer.android.com/reference/android/telecom/TelecomManager.html#ACTION_CHANGE_DEFAULT_DIALER"><code>android.telecom.action.CHANGE_DEFAULT_DIALER</code></a> intent to show a dialog to allow the user to change the default Phone application. + </p> + </li> + <li> + <p> + [C-2-3] MUST honor the <a href="https://developer.android.com/reference/android/telecom/TelecomManager.html#ACTION_CHANGE_PHONE_ACCOUNTS">android.telecom.action.CHANGE_PHONE_ACCOUNTS</a> intent to provide user affordance to configure the <a href="https://developer.android.com/reference/android/telecom/ConnectionService.html"><code>ConnectionServices</code></a> associated with the <a href="https://developer.android.com/reference/android/telecom/PhoneAccount.html"><code>PhoneAccounts</code></a>, as well as a default PhoneAccount that the telecommunications service provider will use to place outgoing calls. The AOSP implementation meets this requirement by including a "Calling Accounts option" menu within the "Calls" settings menu. + </p> + </li> + </ul> + <p> + If device implementations report <code>android.hardware.nfc.hce</code>, they: + </p> + <ul> + <li>[C-3-1] MUST honor the <a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_NFC_PAYMENT_SETTINGS">android.settings.NFC_PAYMENT_SETTINGS</a> intent to show a default app settings menu for Tap and Pay. + </li> + </ul> + <p> + If device implementations support the <code>VoiceInteractionService</code> and have more than one application using this API installed at a time, they: + </p> + <ul> + <li>[C-4-1] MUST honor the <a href="https://developer.android.com/reference/android/provider/Settings.html#ACTION_VOICE_INPUT_SETTINGS"><code>android.settings.ACTION_VOICE_INPUT_SETTINGS</code></a> intent to show a default app settings menu for voice input and assist. + </li> + </ul> + <h4 id="3_2_4_activities_on_secondary_displays"> + 3.2.4. Activities on secondary displays + </h4> + <p> + If device implementations allow launching normal <a href="https://developer.android.com/reference/android/app/Activity.html">Android Activities</a> on secondary displays, they: + </p> + <ul> + <li>[C-1-1] MUST set the <code>android.software.activities_on_secondary_displays</code> feature flag. + </li> + <li>[C-1-2] MUST guarantee API compatibility similar to an activity running on the primary display. + </li> + <li>[C-1-3] MUST land the new activity on the same display as the activity that launched it, when the new activity is launched without specifying a target display via the <a href="https://developer.android.com/reference/android/app/ActivityOptions.html#setLaunchDisplayId%28int%29"><code>ActivityOptions.setLaunchDisplayId()</code></a> API. + </li> + <li>[C-1-4] MUST destory all activities, when a display with the <a href="http://developer.android.com/reference/android/view/Display.html#FLAG_PRIVATE"><code>Display.FLAG_PRIVATE</code></a> flag is removed. + </li> + <li>[C-1-5] MUST resize accordingly all activities on a <a href="https://developer.android.com/reference/android/hardware/display/VirtualDisplay.html"><code>VirtualDisplay</code></a> if the display itself is resized. + </li> + <li>MAY show an IME (input method editor, a user control that enables users to enter text) on the primary display, when a text input field becomes focused on a secondary display. + </li> + <li>SHOULD implement the input focus on the secondary display independently of the primary display, when touch or key inputs are supported. + </li> + <li>SHOULD have <a href="https://developer.android.com/reference/android/content/res/Configuration.html"><code>android.content.res.Configuration</code></a> which corresponds to that display in order to be displayed, operate correctly, and maintain compatibility if an activity is launched on secondary display. + </li> + </ul> + <p> + If device implementations allow launching normal <a href="https://developer.android.com/reference/android/app/Activity.html">Android Activities</a> on secondary displays and primary and secondary displays have different <a href="https://developer.android.com/reference/android/util/DisplayMetrics.html">android.util.DisplayMetrics</a>: + </p> + <ul> + <li>[C-2-1] Non-resizeable activities (that have <code>resizeableActivity=false</code> in <code>AndroidManifest.xml</code>) and apps targeting API level 23 or lower MUST NOT be allowed on secondary displays. + </li> + </ul> + <p> + If device implementations allow launching normal <a href="https://developer.android.com/reference/android/app/Activity.html">Android Activities</a> on secondary displays and a secondary display has the <a href="https://developer.android.com/reference/android/view/Display.html#FLAG_PRIVATE">android.view.Display.FLAG_PRIVATE</a> flag: + </p> + <ul> + <li>[C-3-1] Only the owner of that display, system, and activities that are already on that display MUST be able to launch to it. Everyone can launch to a display that has <a href="https://developer.android.com/reference/android/view/Display.html#FLAG_PUBLIC">android.view.Display.FLAG_PUBLIC</a> flag. + </li> + </ul> + <h3 id="3_3_native_api_compatibility"> + 3.3. Native API Compatibility + </h3> + <p> + Device implementers are: + </p> + <p> + Native code compatibility is challenging. For this reason, device implementers are: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to use the implementations of the libraries listed below from the upstream Android Open Source Project. + </li> + </ul> + <h4 id="3_3_1_application_binary_interfaces"> + 3.3.1. Application Binary Interfaces + </h4> + <p> + Managed Dalvik bytecode can call into native code provided in the application <code>.apk</code> file as an ELF <code>.so</code> file compiled for the appropriate device hardware architecture. As native code is highly dependent on the underlying processor technology, Android defines a number of Application Binary Interfaces (ABIs) in the Android NDK. + </p> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST be compatible with one or more defined ABIs and implement compatibility with the Android NDK. + </li> + <li>[C-0-2] MUST include support for code running in the managed environment to call into native code, using the standard Java Native Interface (JNI) semantics. + </li> + <li>[C-0-3] MUST be source-compatible (i.e. header-compatible) and binary-compatible (for the ABI) with each required library in the list below. + </li> + <li>[C-0-4] MUST support the equivalent 32-bit ABI if any 64-bit ABI is supported. + </li> + <li>[C-0-5] MUST accurately report the native Application Binary Interface (ABI) supported by the device, via the <code>android.os.Build.SUPPORTED_ABIS</code>, <code>android.os.Build.SUPPORTED_32_BIT_ABIS</code>, and <code>android.os.Build.SUPPORTED_64_BIT_ABIS</code> parameters, each a comma separated list of ABIs ordered from the most to the least preferred one. + </li> + <li>[C-0-6] MUST report, via the above parameters, only those ABIs documented and described in the latest version of the <a href="https://developer.android.com/ndk/guides/abis.html">Android NDK ABI Management documentation</a>, and MUST include support for the <a href="http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0388f/Beijfcja.html">Advanced SIMD</a> (a.k.a. NEON) extension. + </li> + <li> + <p> + [C-0-7] MUST make all the following libraries, providing native APIs, available to apps that include native code: + </p> + <ul> + <li>libaaudio.so (AAudio native audio support) + </li> + <li>libandroid.so (native Android activity support) + </li> + <li>libc (C library) + </li> + <li>libcamera2ndk.so + </li> + <li>libdl (dynamic linker) + </li> + <li>libEGL.so (native OpenGL surface management) + </li> + <li>libGLESv1_CM.so (OpenGL ES 1.x) + </li> + <li>libGLESv2.so (OpenGL ES 2.0) + </li> + <li>libGLESv3.so (OpenGL ES 3.x) + </li> + <li>libicui18n.so + </li> + <li>libicuuc.so + </li> + <li>libjnigraphics.so + </li> + <li>liblog (Android logging) + </li> + <li>libmediandk.so (native media APIs support) + </li> + <li>libm (math library) + </li> + <li>libOpenMAXAL.so (OpenMAX AL 1.0.1 support) + </li> + <li>libOpenSLES.so (OpenSL ES 1.0.1 audio support) + </li> + <li>libRS.so + </li> + <li>libstdc++ (Minimal support for C++) + </li> + <li>libvulkan.so (Vulkan) + </li> + <li>libz (Zlib compression) + </li> + <li>JNI interface + </li> + </ul> + </li> + <li> + <p> + [C-0-8] MUST NOT add or remove the public functions for the native libraries listed above. + </p> + </li> + <li>[C-0-9] MUST list additional non-AOSP libraries exposed directly to third-party apps in <code>/vendor/etc/public.libraries.txt</code>. + </li> + <li>[C-0-10] MUST NOT expose any other native libraries, implemented and provided in AOSP as system libraries, to third-party apps targeting API level 24 or higher as they are reserved. + </li> + <li>[C-0-11] MUST export all the OpenGL ES 3.1 and <a href="http://developer.android.com/guide/topics/graphics/opengl.html#aep">Android Extension Pack</a> function symbols, as defined in the NDK, through the <code>libGLESv3.so</code> library. Note that while all the symbols MUST be present, section 7.1.4.1 describes in more detail the requirements for when the full implementation of each corresponding functions are expected. + </li> + <li>[C-0-12] MUST export function symbols for the core Vulkan 1.0 function symobls, as well as the <code>VK_KHR_surface</code>, <code>VK_KHR_android_surface</code>, <code>VK_KHR_swapchain</code>, <code>VK_KHR_maintenance1</code>, and <code>VK_KHR_get_physical_device_properties2</code> extensions through the <code>libvulkan.so</code> library. Note that while all the symbols MUST be present, section 7.1.4.2 describes in more detail the requirements for when the full implementation of each corresponding functions are expected. + </li> + <li>SHOULD be built using the source code and header files available in the upstream Android Open Source Project + </li> + </ul> + <p> + Note that future releases of the Android NDK may introduce support for additional ABIs. + </p> + <h4 id="3_3_2_32-bit_arm_native_code_compatibility"> + 3.3.2. 32-bit ARM Native Code Compatibility + </h4> + <p> + If device implementations are 64-bit ARM devices, then: + </p> + <ul> + <li> + <p> + [C-1-1] Although the ARMv8 architecture deprecates several CPU operations, including some operations used in existing native code, the following deprecated operations MUST remain available to 32-bit native ARM code, either through native CPU support or through software emulation: + </p> + <ul> + <li>SWP and SWPB instructions + </li> + <li>SETEND instruction + </li> + <li>CP15ISB, CP15DSB, and CP15DMB barrier operations + </li> + </ul> + </li> + </ul> + <p> + If device implementations include a 32-bit ARM ABI, they: + </p> + <ul> + <li> + <p> + [C-2-1] MUST include the following lines in <code>/proc/cpuinfo</code> when it is read by 32-bit ARM applications to ensure compatibility with applications built using legacy versions of Android NDK. + </p> + <ul> + <li> + <code>Features:</code>, followed by a list of any optional ARMv7 CPU features supported by the device. + </li> + <li> + <code>CPU architecture:</code>, followed by an integer describing the device's highest supported ARM architecture (e.g., "8" for ARMv8 devices). + </li> + </ul> + </li> + <li> + <p> + SHOULD not alter <code>/proc/cpuinfo</code> when read by 64-bit ARM or non-ARM applications. + </p> + </li> + </ul> + <h3 id="3_4_web_compatibility"> + 3.4. Web Compatibility + </h3> + <h4 id="3_4_1_webview_compatibility"> + 3.4.1. WebView Compatibility + </h4> + <p> + If device implementations provide a complete implementation of the <code>android.webkit.Webview</code> API, they: + </p> + <ul> + <li>[C-1-1] MUST report <code>android.software.webview</code>. + </li> + <li>[C-1-2] MUST use the <a href="http://www.chromium.org/">Chromium</a> Project build from the upstream Android Open Source Project on the Android 8.1 branch for the implementation of the <a href="http://developer.android.com/reference/android/webkit/WebView.html"><code>android.webkit.WebView</code></a> API. + </li> + <li> + <p> + [C-1-3] The user agent string reported by the WebView MUST be in this format: + </p> + <p> + Mozilla/5.0 (Linux; Android $(VERSION); $(MODEL) Build/$(BUILD); wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 $(CHROMIUM_VER) Mobile Safari/537.36 + </p> + <ul> + <li>The value of the $(VERSION) string MUST be the same as the value for android.os.Build.VERSION.RELEASE. + </li> + <li>The value of the $(MODEL) string MUST be the same as the value for android.os.Build.MODEL. + </li> + <li>The value of the $(BUILD) string MUST be the same as the value for android.os.Build.ID. + </li> + <li>The value of the $(CHROMIUM_VER) string MUST be the version of Chromium in the upstream Android Open Source Project. + </li> + <li>Device implementations MAY omit Mobile in the user agent string. + </li> + </ul> + </li> + <li> + <p> + The WebView component SHOULD include support for as many HTML5 features as possible and if it supports the feature SHOULD conform to the <a href="http://html.spec.whatwg.org/multipage/">HTML5 specification</a>. + </p> + </li> + </ul> + <h4 id="3_4_2_browser_compatibility"> + 3.4.2. Browser Compatibility + </h4> + <p> + If device implementations include a standalone Browser application for general web browsing, they: + </p> + <ul> + <li>[C-1-1] MUST support each of these APIs associated with HTML5: + <ul> + <li> + <a href="http://www.w3.org/html/wg/drafts/html/master/browsers.html#offline">application cache/offline operation</a> + </li> + <li> + <a href="http://www.w3.org/html/wg/drafts/html/master/semantics.html#video"><video> tag</a> + </li> + <li> + <a href="http://www.w3.org/TR/geolocation-API/">geolocation</a> + </li> + </ul> + </li> + <li>[C-1-2] MUST support the HTML5/W3C <a href="http://www.w3.org/TR/webstorage/">webstorage API</a> and SHOULD support the HTML5/W3C <a href="http://www.w3.org/TR/IndexedDB/">IndexedDB API</a>. Note that as the web development standards bodies are transitioning to favor IndexedDB over webstorage, IndexedDB is expected to become a required component in a future version of Android. + </li> + <li>MAY ship a custom user agent string in the standalone Browser application. + </li> + <li>SHOULD implement support for as much of <a href="http://html.spec.whatwg.org/multipage/">HTML5</a> as possible on the standalone Browser application (whether based on the upstream WebKit Browser application or a third-party replacement). + </li> + </ul> + <p> + However, If device implementations do not include a standalone Browser application, they: + </p> + <ul> + <li>[C-2-1] MUST still support the public intent patterns as described in <a href="#3_2_3_1_core_application_intents">section 3.2.3.1</a>. + </li> + </ul> + <h3 id="3_5_api_behavioral_compatibility"> + 3.5. API Behavioral Compatibility + </h3> + <p> + The behaviors of each of the API types (managed, soft, native, and web) must be consistent with the preferred implementation of the upstream <a href="http://source.android.com/">Android Open Source Project</a>. Some specific areas of compatibility are: + </p> + <ul> + <li>[C-0-1] Devices MUST NOT change the behavior or semantics of a standard intent. + </li> + <li>[C-0-2] Devices MUST NOT alter the lifecycle or lifecycle semantics of a particular type of system component (such as Service, Activity, ContentProvider, etc.). + </li> + <li>[C-0-3] Devices MUST NOT change the semantics of a standard permission. + </li> + <li>Devices MUST NOT alter the limitations enforced on background applications. More specifically, for background apps: + <ul> + <li>[C-0-4] they MUST stop executing callbacks that are registered by the app to receive outputs from the <a href="https://developer.android.com/reference/android/location/GnssMeasurement.html"><code>GnssMeasurement</code></a> and <a href="https://developer.android.com/reference/android/location/GnssNavigationMessage.html"><code>GnssNavigationMessage</code></a>. + </li> + <li>[C-0-5] they MUST rate-limit the frequency of updates that are provided to the app through the <a href="https://developer.android.com/reference/android/location/LocationManager.html"><code>LocationManager</code></a> API class or the <a href="https://developer.android.com/reference/android/net/wifi/WifiManager.html#startScan%28%29"><code>WifiManager.startScan()</code></a> method. + </li> + <li>[C-0-6] if the app is targeting API level 25 or higher, they MUST NOT allow to register broadcast receivers for the implicit broadcasts of standard Android intents in the app's manifest, unless the broadcast intent requires a <code>"signature"</code> or <code>"signatureOrSystem"</code> <a href="https://developer.android.com/guide/topics/manifest/permission-element.html#plevel"><code>protectionLevel</code></a> permission or are on the <a href="https://developer.android.com/preview/features/background-broadcasts.html">exemption list</a> . + </li> + <li>[C-0-7] if the app is targeting API level 25 or higher, they MUST stop the app's background services, just as if the app had called the services'<a href="https://developer.android.com/reference/android/app/Service.html#stopSelf%28%29"><code>stopSelf()</code></a> method, unless the app is placed on a temporary whitelist to handle a task that's visible to the user. + </li> + <li>[C-0-8] if the app is targeting API level 25 or higher, they MUST release the wakelocks the app holds. + </li> + </ul> + </li> + </ul> + <p> + The above list is not comprehensive. The Compatibility Test Suite (CTS) tests significant portions of the platform for behavioral compatibility, but not all. It is the responsibility of the implementer to ensure behavioral compatibility with the Android Open Source Project. For this reason, device implementers SHOULD use the source code available via the Android Open Source Project where possible, rather than re-implement significant parts of the system. + </p> + <h3 id="3_6_api_namespaces"> + 3.6. API Namespaces + </h3> + <p> + Android follows the package and class namespace conventions defined by the Java programming language. To ensure compatibility with third-party applications, device implementers MUST NOT make any prohibited modifications (see below) to these package namespaces: + </p> + <ul> + <li> + <code>java.*</code> + </li> + <li> + <code>javax.*</code> + </li> + <li> + <code>sun.*</code> + </li> + <li> + <code>android.*</code> + </li> + <li> + <code>com.android.*</code> + </li> + </ul> + <p> + That is, they: + </p> + <ul> + <li>[C-0-1] MUST NOT modify the publicly exposed APIs on the Android platform by changing any method or class signatures, or by removing classes or class fields. + </li> + <li>[C-0-2] MUST NOT add any publicly exposed elements (such as classes or interfaces, or fields or methods to existing classes or interfaces) or Test or System APIs to the APIs in the above namespaces. A “publicly exposed element” is any construct that is not decorated with the “@hide” marker as used in the upstream Android source code. + </li> + </ul> + <p> + Device implementers MAY modify the underlying implementation of the APIs, but such modifications: + </p> + <ul> + <li>[C-0-3] MUST NOT impact the stated behavior and Java-language signature of any publicly exposed APIs. + </li> + <li>[C-0-4] MUST NOT be advertised or otherwise exposed to developers. + </li> + </ul> + <p> + However, device implementers MAY add custom APIs outside the standard Android namespace, but the custom APIs: + </p> + <ul> + <li>[C-0-5] MUST NOT be in a namespace owned by or referring to another organization. For instance, device implementers MUST NOT add APIs to the <code>com.google.*</code> or similar namespace: only Google may do so. Similarly, Google MUST NOT add APIs to other companies' namespaces. + </li> + <li>[C-0-6] MUST be packaged in an Android shared library so that only apps that explicitly use them (via the <uses-library> mechanism) are affected by the increased memory usage of such APIs. + </li> + </ul> + <p> + If a device implementer proposes to improve one of the package namespaces above (such as by adding useful new functionality to an existing API, or adding a new API), the implementer SHOULD visit <a href="http://source.android.com/">source.android.com</a> and begin the process for contributing changes and code, according to the information on that site. + </p> + <p> + Note that the restrictions above correspond to standard conventions for naming APIs in the Java programming language; this section simply aims to reinforce those conventions and make them binding through inclusion in this Compatibility Definition. + </p> + <h3 id="3_7_runtime_compatibility"> + 3.7. Runtime Compatibility + </h3> + <p> + Device implementations: + </p> + <ul> + <li> + <p> + [C-0-1] MUST support the full Dalvik Executable (DEX) format and <a href="https://android.googlesource.com/platform/dalvik/">Dalvik bytecode specification and semantics</a>. + </p> + </li> + <li> + <p> + [C-0-2] MUST configure Dalvik runtimes to allocate memory in accordance with the upstream Android platform, and as specified by the following table. (See <a href="#7_1_1_screen_configuration">section 7.1.1</a> for screen size and screen density definitions.) + </p> + </li> + <li> + <p> + SHOULD use Android RunTime (ART), the reference upstream implementation of the Dalvik Executable Format, and the reference implementation’s package management system. + </p> + </li> + <li> + <p> + SHOULD run fuzz tests under various modes of execution and target architectures to assure the stability of the runtime. Refer to <a href="https://android.googlesource.com/platform/art/+/master/tools/dexfuzz/">JFuzz</a> and <a href="https://android.googlesource.com/platform/art/+/master/tools/dexfuzz/">DexFuzz</a> in the Android Open Source Project website. + </p> + </li> + </ul> + <p> + Note that memory values specified below are considered minimum values and device implementations MAY allocate more memory per application. + </p> + <table> + <tr> + <th> + Screen Layout + </th> + <th> + Screen Density + </th> + <th> + Minimum Application Memory + </th> + </tr> + <tr> + <td rowspan="12"> + Android Watch + </td> + <td> + 120 dpi (ldpi) + </td> + <td rowspan="3"> + 32MB + </td> + </tr> + <tr> + <td> + 160 dpi (mdpi) + </td> + </tr> + <tr> + <td> + 213 dpi (tvdpi) + </td> + </tr> + <tr> + <td> + 240 dpi (hdpi) + </td> + <td rowspan="2"> + 36MB + </td> + </tr> + <tr> + <td> + 280 dpi (280dpi) + </td> + </tr> + <tr> + <td> + 320 dpi (xhdpi) + </td> + <td rowspan="2"> + 48MB + </td> + </tr> + <tr> + <td> + 360 dpi (360dpi) + </td> + </tr> + <tr> + <td> + 400 dpi (400dpi) + </td> + <td> + 56MB + </td> + </tr> + <tr> + <td> + 420 dpi (420dpi) + </td> + <td> + 64MB + </td> + </tr> + <tr> + <td> + 480 dpi (xxhdpi) + </td> + <td> + 88MB + </td> + </tr> + <tr> + <td> + 560 dpi (560dpi) + </td> + <td> + 112MB + </td> + </tr> + <tr> + <td> + 640 dpi (xxxhdpi) + </td> + <td> + 154MB + </td> + </tr> + <tr> + <td rowspan="12"> + small/normal + </td> + <td> + 120 dpi (ldpi) + </td> + <td rowspan="2"> + 32MB + </td> + </tr> + <tr> + <td> + 160 dpi (mdpi) + </td> + </tr> + <tr> + <td> + 213 dpi (tvdpi) + </td> + <td rowspan="3"> + 48MB + </td> + </tr> + <tr> + <td> + 240 dpi (hdpi) + </td> + </tr> + <tr> + <td> + 280 dpi (280dpi) + </td> + </tr> + <tr> + <td> + 320 dpi (xhdpi) + </td> + <td rowspan="2"> + 80MB + </td> + </tr> + <tr> + <td> + 360 dpi (360dpi) + </td> + </tr> + <tr> + <td> + 400 dpi (400dpi) + </td> + <td> + 96MB + </td> + </tr> + <tr> + <td> + 420 dpi (420dpi) + </td> + <td> + 112MB + </td> + </tr> + <tr> + <td> + 480 dpi (xxhdpi) + </td> + <td> + 128MB + </td> + </tr> + <tr> + <td> + 560 dpi (560dpi) + </td> + <td> + 192MB + </td> + </tr> + <tr> + <td> + 640 dpi (xxxhdpi) + </td> + <td> + 256MB + </td> + </tr> + <tr> + <td rowspan="12"> + large + </td> + <td> + 120 dpi (ldpi) + </td> + <td> + 32MB + </td> + </tr> + <tr> + <td> + 160 dpi (mdpi) + </td> + <td> + 48MB + </td> + </tr> + <tr> + <td> + 213 dpi (tvdpi) + </td> + <td rowspan="2"> + 80MB + </td> + </tr> + <tr> + <td> + 240 dpi (hdpi) + </td> + </tr> + <tr> + <td> + 280 dpi (280dpi) + </td> + <td> + 96MB + </td> + </tr> + <tr> + <td> + 320 dpi (xhdpi) + </td> + <td> + 128MB + </td> + </tr> + <tr> + <td> + 360 dpi (360dpi) + </td> + <td> + 160MB + </td> + </tr> + <tr> + <td> + 400 dpi (400dpi) + </td> + <td> + 192MB + </td> + </tr> + <tr> + <td> + 420 dpi (420dpi) + </td> + <td> + 228MB + </td> + </tr> + <tr> + <td> + 480 dpi (xxhdpi) + </td> + <td> + 256MB + </td> + </tr> + <tr> + <td> + 560 dpi (560dpi) + </td> + <td> + 384MB + </td> + </tr> + <tr> + <td> + 640 dpi (xxxhdpi) + </td> + <td> + 512MB + </td> + </tr> + <tr> + <td rowspan="12"> + xlarge + </td> + <td> + 120 dpi (ldpi) + </td> + <td> + 48MB + </td> + </tr> + <tr> + <td> + 160 dpi (mdpi) + </td> + <td> + 80MB + </td> + </tr> + <tr> + <td> + 213 dpi (tvdpi) + </td> + <td rowspan="2"> + 96MB + </td> + </tr> + <tr> + <td> + 240 dpi (hdpi) + </td> + </tr> + <tr> + <td> + 280 dpi (280dpi) + </td> + <td> + 144MB + </td> + </tr> + <tr> + <td> + 320 dpi (xhdpi) + </td> + <td> + 192MB + </td> + </tr> + <tr> + <td> + 360 dpi (360dpi) + </td> + <td> + 240MB + </td> + </tr> + <tr> + <td> + 400 dpi (400dpi) + </td> + <td> + 288MB + </td> + </tr> + <tr> + <td> + 420 dpi (420dpi) + </td> + <td> + 336MB + </td> + </tr> + <tr> + <td> + 480 dpi (xxhdpi) + </td> + <td> + 384MB + </td> + </tr> + <tr> + <td> + 560 dpi (560dpi) + </td> + <td> + 576MB + </td> + </tr> + <tr> + <td> + 640 dpi (xxxhdpi) + </td> + <td> + 768MB + </td> + </tr> + </table> + <h3 id="3_8_user_interface_compatibility"> + 3.8. User Interface Compatibility + </h3> + <h4 id="3_8_1_launcher_(home_screen)"> + 3.8.1. Launcher (Home Screen) + </h4> + <p> + Android includes a launcher application (home screen) and support for third-party applications to replace the device launcher (home screen). + </p> + <p> + If device implementations allow third-party applications to replace the device home screen, they: + </p> + <ul> + <li>[C-1-1] MUST declare the platform feature <code>android.software.home_screen</code>. + </li> + <li>[C-1-2] MUST return the <a href="https://developer.android.com/reference/android/graphics/drawable/AdaptiveIconDrawable.html"><code>AdaptiveIconDrawable</code></a> object when the third party application use <code><adaptive-icon></code> tag to provide their icon, and the <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html"><code>PackageManager</code></a> methods to retrieve icons are called. + </li> + </ul> + <p> + If device implementations include a default launcher that supports in-app pinning of shortcuts, they: + </p> + <ul> + <li>[C-2-1] MUST report <code>true</code> for <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html#isRequestPinShortcutSupported%28%29"><code>ShortcutManager.isRequestPinShortcutSupported()</code></a>. + </li> + <li>[C-2-2] MUST have user affordance asking the user before adding a shortcut requested by apps via the <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html#requestPinShortcut%28android.content.pm.ShortcutInfo,%20android.content.IntentSender%29"><code>ShortcutManager.requestPinShortcut()</code></a> API method. + </li> + <li>[C-2-3] MUST support pinned shortcuts and dynamic and static shortcuts as documented on the <a href="https://developer.android.com/guide/topics/ui/shortcuts.html">App Shortcuts page</a>. + </li> + </ul> + <p> + Conversely, if device implementations do not support in-app pinning of shortcuts, they: + </p> + <ul> + <li>[C-3-1] MUST report <code>false</code> for <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html#isRequestPinShortcutSupported%28%29"><code>ShortcutManager.isRequestPinShortcutSupported()</code></a>. + </li> + </ul> + <p> + If device implementations implement a default launcher that provides quick access to the additional shortcuts provided by third-party apps through the <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html">ShortcutManager</a> API, they: + </p> + <ul> + <li>[C-4-1] MUST support all documented shortcut features (e.g. static and dynamic shortcuts, pinning shortcuts) and fully implement the APIs of the <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html"><code>ShortcutManager</code></a> API class. + </li> + </ul> + <p> + If device implementations include a default launcher app that shows badges for the app icons, they: + </p> + <ul> + <li>[C-5-1] MUST respect the <a href="https://developer.android.com/reference/android/app/NotificationChannel.html#setShowBadge%28boolean%29"><code>NotificationChannel.setShowBadge()</code></a> API method. In other words, show a visual affordance associated with the app icon if the value is set as <code>true</code>, and do not show any app icon badging scheme when all of the app's notification channels have set the value as <code>false</code>. + </li> + <li>MAY override the app icon badges with their proprietary badging scheme when third-party applications indicate support of the proprietary badging scheme through the use of proprietary APIs, but SHOULD use the resources and values provided through the notification badges APIs described in <a href="https://developer.android.com/preview/features/notification-badges.html">the SDK</a> , such as the <a href="http://developer.android.com/reference/android/app/Notification.Builder.html#setNumber%28int%29"><code>Notification.Builder.setNumber()</code></a> and the <a href="http://developer.android.com/reference/android/app/Notification.Builder.html#setBadgeIconType%28int%29"><code>Notification.Builder.setBadgeIconType()</code></a> API. + </li> + </ul> + <h4 id="3_8_2_widgets"> + 3.8.2. Widgets + </h4> + <p> + Android supports third-party app widgets by defining a component type and corresponding API and lifecycle that allows applications to expose an <a href="http://developer.android.com/guide/practices/ui_guidelines/widget_design.html">“AppWidget”</a> to the end user. + </p> + <p> + If device implementations support third-party app widgets, they: + </p> + <ul> + <li>[C-1-1] MUST declare support for platform feature <code>android.software.app_widgets</code>. + </li> + <li>[C-1-2] MUST include built-in support for AppWidgets and expose user interface affordances to add, configure, view, and remove AppWidgets directly within the Launcher. + </li> + <li>[C-1-3] MUST be capable of rendering widgets that are 4 x 4 in the standard grid size. See the <a href="http://developer.android.com/guide/practices/ui_guidelines/widget_design.html">App Widget DesignGuidelines</a> in the Android SDK documentation for details. + </li> + <li>MAY support application widgets on the lock screen. + </li> + </ul> + <p> + If device implementations support third-party app widgets and in-app pinning of shortcuts, they: + </p> + <ul> + <li>[C-2-1] MUST report <code>true</code> for <a href="https://developer.android.com/reference/android/appwidget/AppWidgetManager.html#isRequestPinAppWidgetSupported%28%29"><code>AppWidgetManager.html.isRequestPinAppWidgetSupported()</code></a>. + </li> + <li>[C-2-2] MUST have user affordance asking the user before adding a shortcut requested by apps via the <a href="https://developer.android.com/reference/android/appwidget/AppWidgetManager.html#requestPinAppWidget%28android.content.ComponentName,android.os.Bundle,%20android.app.PendingIntent%29"><code>AppWidgetManager.requestPinAppWidget()</code></a> API method. + </li> + </ul> + <h4 id="3_8_3_notifications"> + 3.8.3. Notifications + </h4> + <p> + Android includes <a href="https://developer.android.com/reference/android/app/Notification.html"><code>Notification</code></a> and <a href="https://developer.android.com/reference/android/app/NotificationManager.html"><code>NotificationManager</code></a> APIs that allow third-party app developers to notify users of notable events and attract users' attention using the hardware components (e.g. sound, vibration and light) and software features (e.g. notification shade, system bar) of the device. + </p> + <h5 id="3_8_3_1_presentation_of_notifications"> + 3.8.3.1. Presentation of Notifications + </h5> + <p> + If device implementations allow third party apps to <a href="http://developer.android.com/guide/topics/ui/notifiers/notifications.html">notify users of notable events</a>, they: + </p> + <ul> + <li>[C-1-1] MUST support notifications that use hardware features, as described in the SDK documentation, and to the extent possible with the device implementation hardware. For instance, if a device implementation includes a vibrator, it MUST correctly implement the vibration APIs. If a device implementation lacks hardware, the corresponding APIs MUST be implemented as no-ops. This behavior is further detailed in <a href="#7_hardware_compatibility">section 7</a>. + </li> + <li>[C-1-2] MUST correctly render all <a href="https://developer.android.com/guide/topics/resources/available-resources.html">resources</a> (icons, animation files etc.) provided for in the APIs, or in the Status/System Bar <a href="http://developer.android.com/design/style/iconography.html">icon style guide</a>, although they MAY provide an alternative user experience for notifications than that provided by the reference Android Open Source implementation. + </li> + <li>[C-1-3] MUST honor and implement properly the behaviors described for <a href="https://developer.android.com/guide/topics/ui/notifiers/notifications.html#Managing">the APIs</a> to update, remove and group notifications. + </li> + <li>[C-1-4] MUST provide the full behavior of the <a href="https://developer.android.com/reference/android/app/NotificationChannel.html">NotificationChannel</a> API documented in the SDK. + </li> + <li>[C-1-5] MUST provide a user affordance to block and modify a certain third-party app's notification per each channel and app package level. + </li> + <li>[C-1-6] MUST also provide a user affordance to display deleted notification channels. + </li> + <li>SHOULD support rich notifications. + </li> + <li>SHOULD present some higher priority notifications as heads-up notifications. + </li> + <li>SHOULD have a user affordance to snooze notifications. + </li> + <li>MAY only manage the visibility and timing of when third-party apps can notify users of notable events to mitigate safety issues such as driver distraction. + </li> + </ul> + <p> + If device implementations support rich notifications, they: + </p> + <ul> + <li>[C-2-1] MUST use the exact resources as provided through the <a href="https://developer.android.com/reference/android/app/Notification.Style.html"><code>Notification.Style</code></a> API class and its subclasses for the presented resource elements. + </li> + <li>SHOULD present each and every resource element (e.g. icon, title and summary text) defined in the <a href="https://developer.android.com/reference/android/app/Notification.Style.html"><code>Notification.Style</code></a> API class and its subclasses. + </li> + </ul> + <p> + If device impelementations support heads-up notifications: they: + </p> + <ul> + <li>[C-3-1] MUST use the heads-up notification view and resources as described in the <a href="https://developer.android.com/reference/android/app/Notification.Builder.html"><code>Notification.Builder</code></a> API class when heads-up notifications are presented. + </li> + </ul> + <h5 id="3_8_3_2_notification_listener_service"> + 3.8.3.2. Notification Listener Service + </h5> + <p> + Android includes the <a href="https://developer.android.com/reference/android/service/notification/NotificationListenerService.html"><code>NotificationListenerService</code></a> APIs that allow apps (once explicitly enabled by the user) to receive a copy of all notifications as they are posted or updated. + </p> + <p> + If device implementations report the feature flag <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_RAM_NORMAL"><code>android.hardware.ram.normal</code></a>, they: + </p> + <ul> + <li>[C-1-1] MUST correctly and promptly update notifications in their entirety to all such installed and user-enabled listener services, including any and all metadata attached to the Notification object. + </li> + <li>[C-1-2] MUST respect the <a href="https://developer.android.com/reference/android/service/notification/NotificationListenerService.html#snoozeNotification%28java.lang.String,%20long%29"><code>snoozeNotification()</code></a> API call, and dismiss the notification and make a callback after the snooze duration that is set in the API call. + </li> + </ul> + <p> + If device implementations have a user affordance to snooze notifications, they: + </p> + <ul> + <li>[C-2-1] MUST reflect the snoozed notification status properly through the standard APIs such as <a href="https://developer.android.com/reference/android/service/notification/NotificationListenerService.html#getSnoozedNotifications%28%29"><code>NotificationListenerService.getSnoozedNotifications()</code></a>. + </li> + <li>[C-2-2] MUST make this user affordance available to snooze notifications from each installed third-party app's, unless they are from persistent/foreground services. + </li> + </ul> + <h5 id="3_8_3_3_dnd_(do_not_disturb)"> + 3.8.3.3. DND (Do not Disturb) + </h5> + <p> + If device implementations support the DND feature, they: + </p> + <ul> + <li>[C-1-1] MUST implement an activity that would respond to the intent <a href="https://developer.android.com/reference/android/provider/Settings.html#ACTION_NOTIFICATION_POLICY_ACCESS_SETTINGS">ACTION_NOTIFICATION_POLICY_ACCESS_SETTINGS</a>, which for implementations with UI_MODE_TYPE_NORMAL it MUST be an activity where the user can grant or deny the app access to DND policy configurations. + </li> + <li>[C-1-2] MUST, for when the device implementation has provided a means for the user to grant or deny third-party apps to access the DND policy configuration, display <a href="https://developer.android.com/reference/android/app/NotificationManager.html#addAutomaticZenRule%28android.app.AutomaticZenRule%29">Automatic DND rules</a> created by applications alongside the user-created and pre-defined rules. + </li> + <li>[C-1-3] MUST honor the <a href="https://developer.android.com/reference/android/app/NotificationManager.Policy.html#suppressedVisualEffects"><code>suppressedVisualEffects</code></a> values passed along the <a href="https://developer.android.com/reference/android/app/NotificationManager.Policy.html#NotificationManager.Policy%28int,%20int,%20int,%20int%29"><code>NotificationManager.Policy</code></a> and if an app has set any of the SUPPRESSED_EFFECT_SCREEN_OFF or SUPPRESSED_EFFECT_SCREEN_ON flags, it SHOULD indicate to the user that the visual effects are suppressed in the DND settings menu. + </li> + </ul> + <h4 id="3_8_4_search"> + 3.8.4. Search + </h4> + <p> + Android includes APIs that allow developers to <a href="http://developer.android.com/reference/android/app/SearchManager.html">incorporate search</a> into their applications and expose their application’s data into the global system search. Generally speaking, this functionality consists of a single, system-wide user interface that allows users to enter queries, displays suggestions as users type, and displays results. The Android APIs allow developers to reuse this interface to provide search within their own apps and allow developers to supply results to the common global search user interface. + </p> + <ul> + <li>Android device implementations SHOULD include global search, a single, shared, system-wide search user interface capable of real-time suggestions in response to user input. + </li> + </ul> + <p> + If device implementations implement the global search interface, they: + </p> + <ul> + <li>[C-1-1] MUST implement the APIs that allow third-party applications to add suggestions to the search box when it is run in global search mode. + </li> + </ul> + <p> + If no third-party applications are installed that make use of the global search: + </p> + <ul> + <li>The default behavior SHOULD be to display web search engine results and suggestions. + </li> + </ul> + <p> + Android also includes the <a href="https://developer.android.com/reference/android/app/assist/package-summary.html">Assist APIs</a> to allow applications to elect how much information of the current context is shared with the assistant on the device. + </p> + <p> + If device implementations support the Assist action, they: + </p> + <ul> + <li>[C-2-1] MUST indicate clearly to the end user when the context is shared, by either: + <ul> + <li>Each time the assist app accesses the context, displaying a white light around the edges of the screen that meet or exceed the duration and brightness of the Android Open Source Project implementation. + </li> + <li>For the preinstalled assist app, providing a user affordance less than two navigations away from <a href="#3_2_3_5_default_app_settings">the default voice input and assistant app settings menu</a>, and only sharing the context when the assist app is explicitly invoked by the user through a hotword or assist navigation key input. + </li> + </ul> + </li> + <li>[C-2-2] The designated interaction to launch the assist app as described in <a href="#7_2_3_navigation_keys">section 7.2.3</a> MUST launch the user-selected assist app, in other words the app that implements <code>VoiceInteractionService</code>, or an activity handling the <code>ACTION_ASSIST</code> intent. + </li> + <li>[SR] STRONGLY RECOMMENDED to use long press on <code>HOME</code> key as this designated interaction. + </li> + </ul> + <h4 id="3_8_5_alerts_and_toasts"> + 3.8.5. Alerts and Toasts + </h4> + <p> + Applications can use the <a href="http://developer.android.com/reference/android/widget/Toast.html"><code>Toast</code></a> API to display short non-modal strings to the end user that disappear after a brief period of time, and use the <a href="http://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#TYPE_APPLICATION_OVERLAY"><code>TYPE_APPLICATION_OVERLAY</code></a> window type API to display alert windows as an overlay over other apps. + </p> + <p> + If device implementations include a screen or video output, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST provide a user affordance to block an app from displaying alert windows that use the <a href="http://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#TYPE_APPLICATION_OVERLAY"><code>TYPE_APPLICATION_OVERLAY</code></a> . The AOSP implementation meets this requirement by having controls in the notification shade. + </p> + </li> + <li> + <p> + [C-1-2] MUST honor the Toast API and display Toasts from applications to end users in some highly visible manner. + </p> + </li> + </ul> + <h4 id="3_8_6_themes"> + 3.8.6. Themes + </h4> + <p> + Android provides “themes” as a mechanism for applications to apply styles across an entire Activity or application. + </p> + <p> + Android includes a “Holo” and "Material" theme family as a set of defined styles for application developers to use if they want to match the <a href="http://developer.android.com/guide/topics/ui/themes.html">Holo theme look and feel</a> as defined by the Android SDK. + </p> + <p> + If device implementations include a screen or video output, they: + </p> + <ul> + <li>[C-1-1] MUST NOT alter any of the <a href="http://developer.android.com/reference/android/R.style.html">Holo theme attributes</a> exposed to applications. + </li> + <li>[C-1-2] MUST support the “Material” theme family and MUST NOT alter any of the <a href="http://developer.android.com/reference/android/R.style.html#Theme_Material">Material theme attributes</a> or their assets exposed to applications. + </li> + </ul> + <p> + Android also includes a “Device Default” theme family as a set of defined styles for application developers to use if they want to match the look and feel of the device theme as defined by the device implementer. + </p> + <ul> + <li>Device implementations MAY modify the <a href="http://developer.android.com/reference/android/R.style.html">Device Default theme attributes</a> exposed to applications. + </li> + </ul> + <p> + Android supports a variant theme with translucent system bars, which allows application developers to fill the area behind the status and navigation bar with their app content. To enable a consistent developer experience in this configuration, it is important the status bar icon style is maintained across different device implementations. + </p> + <p> + If device implementations include a system status bar, they: + </p> + <ul> + <li>[C-2-1] MUST use white for system status icons (such as signal strength and battery level) and notifications issued by the system, unless the icon is indicating a problematic status or an app requests a light status bar using the SYSTEM_UI_FLAG_LIGHT_STATUS_BAR flag. + </li> + <li>[C-2-2] Android device implementations MUST change the color of the system status icons to black (for details, refer to <a href="http://developer.android.com/reference/android/R.style.html">R.style</a>) when an app requests a light status bar. + </li> + </ul> + <h4 id="3_8_7_live_wallpapers"> + 3.8.7. Live Wallpapers + </h4> + <p> + Android defines a component type and corresponding API and lifecycle that allows applications to expose one or more <a href="http://developer.android.com/reference/android/service/wallpaper/WallpaperService.html">“Live Wallpapers”</a> to the end user. Live wallpapers are animations, patterns, or similar images with limited input capabilities that display as a wallpaper, behind other applications. + </p> + <p> + Hardware is considered capable of reliably running live wallpapers if it can run all live wallpapers, with no limitations on functionality, at a reasonable frame rate with no adverse effects on other applications. If limitations in the hardware cause wallpapers and/or applications to crash, malfunction, consume excessive CPU or battery power, or run at unacceptably low frame rates, the hardware is considered incapable of running live wallpaper. As an example, some live wallpapers may use an OpenGL 2.0 or 3.x context to render their content. Live wallpaper will not run reliably on hardware that does not support multiple OpenGL contexts because the live wallpaper use of an OpenGL context may conflict with other applications that also use an OpenGL context. + </p> + <ul> + <li>Device implementations capable of running live wallpapers reliably as described above SHOULD implement live wallpapers. + </li> + </ul> + <p> + If device implementations implement live wallpapers, they: + </p> + <ul> + <li>[C-1-1] MUST report the platform feature flag android.software.live_wallpaper. + </li> + </ul> + <h4 id="3_8_8_activity_switching"> + 3.8.8. Activity Switching + </h4> + <p> + The upstream Android source code includes the <a href="https://developer.android.com/guide/components/activities/recents.html">overview screen</a>, a system-level user interface for task switching and displaying recently accessed activities and tasks using a thumbnail image of the application’s graphical state at the moment the user last left the application. + </p> + <p> + Device implementations including the recents function navigation key as detailed in <a href="#7_2_3_navigation_keys">section 7.2.3</a> MAY alter the interface. + </p> + <p> + If device implementations including the recents function navigation key as detailed in <a href="#7_2_3_navigation_keys">section 7.2.3</a> alter the interface, they: + </p> + <ul> + <li>[C-1-1] MUST support at least up to 7 displayed activities. + </li> + <li>SHOULD at least display the title of 4 activities at a time. + </li> + <li>[C-1-2] MUST implement the <a href="http://developer.android.com/about/versions/android-5.0.html#ScreenPinning">screen pinning behavior</a> and provide the user with a settings menu to toggle the feature. + </li> + <li>SHOULD display highlight color, icon, screen title in recents. + </li> + <li>SHOULD display a closing affordance ("x") but MAY delay this until user interacts with screens. + </li> + <li>SHOULD implement a shortcut to switch easily to the previous activity + </li> + <li>SHOULD trigger the fast-switch action between the two most recently used apps, when the recents function key is tapped twice. + </li> + <li>SHOULD trigger the split-screen multiwindow-mode, if supported, when the recents functions key is long pressed. + </li> + <li> + <p> + MAY display affiliated recents as a group that moves together. + </p> + </li> + <li> + <p> + [SR] Are STRONGLY RECOMMENDED to use the upstream Android user interface (or a similar thumbnail-based interface) for the overview screen. + </p> + </li> + </ul> + <h4 id="3_8_9_input_management"> + 3.8.9. Input Management + </h4> + <p> + Android includes support for <a href="http://developer.android.com/guide/topics/text/creating-input-method.html">Input Management</a> and support for third-party input method editors. + </p> + <p> + If device implementations allow users to use third-party input methods on the device, they: + </p> + <ul> + <li>[C-1-1] MUST declare the platform feature android.software.input_methods and support IME APIs as defined in the Android SDK documentation. + </li> + <li>[C-1-2] MUST provide a user-accessible mechanism to add and configure third-party input methods in response to the android.settings.INPUT_METHOD_SETTINGS intent. + </li> + </ul> + <p> + If device implementations declare the <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_AUTOFILL"><code>android.software.autofill</code></a> feature flag, they: + </p> + <ul> + <li>[C-2-1] MUST fully implement the <a href="https://developer.android.com/reference/android/service/autofill/AutofillService.html"><code>AutofillService</code></a> and <a href="https://developer.android.com/reference/android/view/autofill/AutofillManager.html"><code>AutofillManager</code></a> APIs and honor the <a href="https://developer.android.com/reference/android/provider/Settings.html#ACTION_REQUEST_SET_AUTOFILL_SERVICE"><code>android.settings.REQUEST_SET_AUTOFILL_SERVICE</code></a> intent to show a default app settings menu to enable and disable autofill and change the default autofill service for the user. + </li> + </ul> + <h4 id="3_8_10_lock_screen_media_control"> + 3.8.10. Lock Screen Media Control + </h4> + <p> + The Remote Control Client API is deprecated from Android 5.0 in favor of the <a href="http://developer.android.com/reference/android/app/Notification.MediaStyle.html">Media Notification Template</a> that allows media applications to integrate with playback controls that are displayed on the lock screen. + </p> + <h4 id="3_8_11_screen_savers_(previously_dreams)"> + 3.8.11. Screen savers (previously Dreams) + </h4> + <p> + Android includes support for <a href="http://developer.android.com/reference/android/service/dreams/DreamService.html">interactivescreensavers</a>, previously referred to as Dreams. Screen savers allow users to interact with applications when a device connected to a power source is idle or docked in a desk dock. Android Watch devices MAY implement screen savers, but other types of device implementations SHOULD include support for screen savers and provide a settings option for users toconfigure screen savers in response to the <code>android.settings.DREAM_SETTINGS</code> intent. + </p> + <h4 id="3_8_12_location"> + 3.8.12. Location + </h4> + <p> + If device implementations include a hardware sensor (e.g. GPS) that is capable of providing the location coordinates: + </p> + <ul> + <li>[C-1-1] <a href="http://developer.android.com/reference/android/provider/Settings.Secure.html#LOCATION_MODE">location modes</a> MUST be displayed in the Location menu within Settings. + </li> + </ul> + <h4 id="3_8_13_unicode_and_font"> + 3.8.13. Unicode and Font + </h4> + <p> + Android includes support for the emoji characters defined in <a href="http://www.unicode.org/versions/Unicode10.0.0/">Unicode 10.0</a>. + </p> + <p> + If device implementations include a screen or video output, they: + </p> + <ul> + <li>[C-1-1] MUST be capable of rendering these emoji characters in color glyph. + </li> + <li>[C-1-2] MUST include support for: + </li> + <li>Roboto 2 font with different weights—sans-serif-thin, sans-serif-light, sans-serif-medium, sans-serif-black, sans-serif-condensed, sans-serif-condensed-light for the languages available on the device. + </li> + <li>Full Unicode 7.0 coverage of Latin, Greek, and Cyrillic, including the Latin Extended A, B, C, and D ranges, and all glyphs in the currency symbols block of Unicode 7.0. + </li> + <li>SHOULD support the skin tone and diverse family emojis as specified in the <a href="http://unicode.org/reports/tr51">Unicode Technical Report #51</a>. + </li> + </ul> + <p> + If device implementations include an IME, they: + </p> + <ul> + <li>SHOULD provide an input method to the user for these emoji characters. + </li> + </ul> + <h4 id="3_8_14_multi-windows"> + 3.8.14. Multi-windows + </h4> + <p> + If device implementations have the capability to display multiple activities at the same time, they: + </p> + <ul> + <li>[C-1-1] MUST implement such multi-window mode(s) in accordance with the application behaviors and APIs described in the Android SDK <a href="https://developer.android.com/guide/topics/ui/multi-window.html">multi-window mode support documentation</a> and meet the following requirements: + </li> + <li>[C-1-2] Applications can indicate whether they are capable of operating in multi-window mode in the <code>AndroidManifest.xml</code> file, either explicitly via setting the <a href="https://developer.android.com/reference/android/R.attr.html#resizeableActivity"><code>android:resizeableActivity</code></a> attribute to <code>true</code> or implicitly by having the targetSdkVersion > 24. Apps that explicitly set this attribute to <code>false</code> in their manifest MUST NOT be launched in multi-window mode. Older apps with targetSdkVersion < 24 that did not set this <code>android:resizeableActivity</code> attribute MAY be launched in multi-window mode, but the system MUST provide warning that the app may not work as expected in multi-window mode. + </li> + <li>[C-1-3] MUST NOT offer split-screen or freeform mode if the screen height < 440 dp and the the screen width < 440 dp. + </li> + <li>Device implementations with screen size <code>xlarge</code> SHOULD support freeform mode. + </li> + </ul> + <p> + If device implementations support multi-window mode(s), and the split screen mode, they: + </p> + <ul> + <li>[C-2-1] MUST preload a <a href="https://developer.android.com/guide/topics/ui/multi-window.html#configuring">resizeable</a> launcher as the default. + </li> + <li>[C-2-2] MUST crop the docked activity of a split-screen multi-window but SHOULD show some content of it, if the Launcher app is the focused window. + </li> + <li>[C-2-3] MUST honor the declared <a href="https://developer.android.com/reference/android/R.styleable.html#AndroidManifestLayout_minWidth"><code>AndroidManifestLayout_minWidth</code></a> and <a href="https://developer.android.com/reference/android/R.styleable.html#AndroidManifestLayout_minHeight"><code>AndroidManifestLayout_minHeight</code></a> values of the third-party launcher application and not override these values in the course of showing some content of the docked activity. + </li> + </ul> + <p> + If device implementations support multi-window mode(s) and Picture-in-Picture multi-window mode, they: + </p> + <ul> + <li>[C-3-1] MUST launch activities in picture-in-picture multi-window mode when the app is: * Targeting API level 26 or higher and declares <a href="https://developer.android.com/reference/android/R.attr.html#supportsPictureInPicture"><code>android:supportsPictureInPicture</code></a> * Targeting API level 25 or lower and declares both <a href="https://developer.android.com/reference/android/R.attr.html#resizeableActivity"><code>android:resizeableActivity</code></a> and <a href="https://developer.android.com/reference/android/R.attr.html#supportsPictureInPicture"><code>android:supportsPictureInPicture</code></a>. + </li> + <li>[C-3-2] MUST expose the actions in their SystemUI as specified by the current PIP activity through the <a href="https://developer.android.com/reference/android/app/PictureInPictureParams.Builder.html#setActions%28java.util.List%3Candroid.app.RemoteAction%3E%29"><code>setActions()</code></a> API. + </li> + <li>[C-3-3] MUST support aspect ratios greater than or equal to 1:2.39 and less than or equal to 2.39:1, as specified by the PIP activity through the <a href="https://developer.android.com/reference/android/app/PictureInPictureParams.Builder.html#setAspectRatio%28android.util.Rational%29"><code>setAspectRatio()</code></a> API. + </li> + <li>[C-3-4] MUST use <a href="https://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_WINDOW"><code>KeyEvent.KEYCODE_WINDOW</code></a> to control the PIP window; if PIP mode is not implemented, the key MUST be available to the foreground activity. + </li> + <li>[C-3-5] MUST provide a user affordance to block an app from displaying in PIP mode; the AOSP implementation meets this requirement by having controls in the notification shade. + </li> + <li>[C-3-6] MUST allocate minimum width and height of 108 dp for the PIP window and minimum width of 240 dp and height of 135 dp for the PIP window when the <code>Configuration.uiMode</code> is configured as <a href="https://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_TELEVISION"><code>UI_MODE_TYPE_TELEVISION</code></a> + </li> + </ul> + <h3 id="3_9_device_administration"> + 3.9. Device Administration + </h3> + <p> + Android includes features that allow security-aware applications to perform device administration functions at the system level, such as enforcing password policies or performing remote wipe, through the <a href="http://developer.android.com/guide/topics/admin/device-admin.html">Android Device Administration API</a>]. + </p> + <p> + If device implementations implement the full range of <a href="http://developer.android.com/guide/topics/admin/device-admin.html">device administration</a> policies defined in the Android SDK documentation, they: + </p> + <ul> + <li>[C-1-1] MUST declare <code>android.software.device_admin</code>. + </li> + <li>[C-1-2] MUST support device owner provisioning as described in <a href="#3_9_1_device_provisioning">section 3.9.1</a> and <a href="#3_9_1_1_device_owner_provisioning">section 3.9.1.1</a>. + </li> + <li>[C-1-3] MUST declare the support of manged profiles via the <code>android.software.managed_users</code> feature flag, except for when the device is configured so that it would <a href="http://developer.android.com/reference/android/app/ActivityManager.html#isLowRamDevice%28%29">report</a> itself as a low RAM device or so that it allocate internal (non-removable) storage as shared storage. + </li> + </ul> + <h4 id="3_9_1_device_provisioning"> + 3.9.1 Device Provisioning + </h4> + <h5 id="3_9_1_1_device_owner_provisioning"> + 3.9.1.1 Device owner provisioning + </h5> + <p> + If device implementations declare <code>android.software.device_admin</code>, they: + </p> + <ul> + <li>[C-1-1] MUST support enrolling a Device Policy Client (DPC) as a <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isDeviceOwnerApp%28java.lang.String%29">Device Owner app</a> as described below:. + <ul> + <li>when the device implementation has no user data is configured yet, it: + <ul> + <li>[C-1-3] MUST report <code>true</code> for <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isProvisioningAllowed(java.lang.String)"><code>DevicePolicyManager.isProvisioningAllowed(ACTION_PROVISION_MANAGED_DEVICE)</code></a>. + </li> + <li>[C-1-4] MUST enroll the DPC application as the Device Owner app in response to the intent action <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_DEVICE"><code>android.app.action.PROVISION_MANAGED_DEVICE</code></a>. + </li> + <li>[C-1-5] MUST enroll the DPC application as the Device Owner app if the device declares Near-Field Communications (NFC) support via the feature flag <code>android.hardware.nfc</code> and receives an NFC message containing a record with MIME type <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#MIME_TYPE_PROVISIONING_NFC"><code>MIME_TYPE_PROVISIONING_NFC</code></a>. + </li> + </ul> + </li> + <li>When the device implementation has user data, it: + <ul> + <li>[C-1-6] MUST report <code>false</code> for the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isProvisioningAllowed(java.lang.String)"><code>DevicePolicyManager.isProvisioningAllowed(ACTION_PROVISION_MANAGED_DEVICE)</code></a>. + </li> + <li>[C-1-7] MUST not enroll any DPC application as the Device Owner App any more. + </li> + </ul> + </li> + </ul> + </li> + <li>[C-1-2] MUST NOT set an application (including pre-installed app) as the Device Owner app without explicit consent or action from the user or the administrator of the device. + </li> + </ul> + <p> + If device implementations declare <code>android.software.device_admin</code>, but also include a proprietary Device Owner management solution and provide a mechanism to promote an application configured in their solution as a "Device Owner equivalent" to the standard "Device Owner" as recognized by the standard Android <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html">DevicePolicyManager</a> APIs, they: + </p> + <ul> + <li>[C-2-1] MUST have a process in place to verify that the specific app being promoted belongs to a legitimate enterprise device management solution and it has been already configured in the proprietary solution to have the rights equivalent as a "Device Owner". + </li> + <li>[C-2-2] MUST show the same AOSP Device Owner consent disclosure as the flow initiated by <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_DEVICE"><code>android.app.action.PROVISION_MANAGED_DEVICE</code></a> prior to enrolling the DPC application as "Device Owner". + </li> + <li>MAY have user data on the device prior to enrolling the DPC application as "Device Owner". + </li> + </ul> + <h5 id="3_9_1_2_managed_profile_provisioning"> + 3.9.1.2 Managed profile provisioning + </h5> + <p> + If device implementations declare <code>android.software.managed_users</code>, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST implement the <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_PROFILE">APIs</a> allowing a Device Policy Controller (DPC) application to become the <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isProfileOwnerApp%28java.lang.String%29">owner of a new Managed Profile</a>. + </p> + </li> + <li> + <p> + [C-1-2] The managed profile provisioning process (the flow initiated by <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_PROFILE">android.app.action.PROVISION_MANAGED_PROFILE</a>) users experience MUST align with the AOSP implementation. + </p> + </li> + <li> + <p> + [C-1-3] MUST provide the following user affordances within the Settings to indicate to the user when a particular system function has been disabled by the Device Policy Controller (DPC): + </p> + <ul> + <li>A consistent icon or other user affordance (for example the upstream AOSP info icon) to represent when a particular setting is restricted by a Device Admin. + </li> + <li>A short explanation message, as provided by the Device Admin via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setShortSupportMessage%28android.content.ComponentName,%20java.lang.CharSequence%29"><code>setShortSupportMessage</code></a>. + </li> + <li>The DPC application’s icon. + </li> + </ul> + </li> + </ul> + <h3 id="3_9_2_managed_profile_support"> + 3.9.2 Managed Profile Support + </h3> + <p> + If device implementations declare <code>android.software.managed_users</code>, they: + </p> + <ul> + <li>[C-1-1] MUST support managed profiles via the <code>android.app.admin.DevicePolicyManager</code> APIs. + </li> + <li>[C-1-2] MUST allow one and only <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_PROFILE">one managed profile to be created</a>. + </li> + <li>[C-1-3] MUST use an icon badge (similar to the AOSP upstream work badge) to represent the managed applications and widgets and other badged UI elements like Recents & Notifications. + </li> + <li>[C-1-4] MUST display a notification icon (similar to the AOSP upstream work badge) to indicate when user is within a managed profile application. + </li> + <li>[C-1-5] MUST display a toast indicating that the user is in the managed profile if and when the device wakes up (ACTION_USER_PRESENT) and the foreground application is within the managed profile. + </li> + <li>[C-1-6] Where a managed profile exists, MUST show a visual affordance in the Intent 'Chooser' to allow the user to forward the intent from the managed profile to the primary user or vice versa, if enabled by the Device Policy Controller. + </li> + <li>[C-1-7] Where a managed profile exists, MUST expose the following user affordances for both the primary user and the managed profile: + <ul> + <li>Separate accounting for battery, location, mobile data and storage usage for the primary user and managed profile. + </li> + <li>Independent management of VPN Applications installed within the primary user or managed profile. + </li> + <li>Independent management of applications installed within the primary user or managed profile. + </li> + <li>Independent management of accounts within the primary user or managed profile. + </li> + </ul> + </li> + <li>[C-1-8] MUST ensure the preinstalled dialer, contacts and messaging applications can search for and look up caller information from the managed profile (if one exists) alongside those from the primary profile, if the Device Policy Controller permits it. + </li> + <li>[C-1-9] MUST ensure that it satisfies all the security requirements applicable for a device with multiple users enabled (see<a href="#9_5_multi-user_support">section 9.5</a>), even though the managed profile is not counted as another user in addition to the primary user. + </li> + <li>[C-1-10] MUST support the ability to specify a separate lock screen meeting the following requirements to grant access to apps running in a managed profile. + <ul> + <li>Device implementations MUST honor the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_SET_NEW_PASSWORD"><code>DevicePolicyManager.ACTION_SET_NEW_PASSWORD</code></a> intent and show an interface to configure a separate lock screen credential for the managed profile. + </li> + <li>The lock screen credentials of the managed profile MUST use the same credential storage and management mechanisms as the parent profile, as documented on the <a href="http://source.android.com/security/authentication/index.html">Android Open Source Project Site</a> + </li> + <li>The DPC <a href="https://developer.android.com/guide/topics/admin/device-admin.html#pwd">password policies</a> MUST apply to only the managed profile's lock screen credentials unless called upon the <code>DevicePolicyManager</code> instance returned by <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#getParentProfileInstance%28android.content.ComponentName%29">getParentProfileInstance</a>. + </li> + </ul> + </li> + <li>When contacts from the managed profile are displayed in the preinstalled call log, in-call UI, in-progress and missed-call notifications, contacts and messaging apps they SHOULD be badged with the same badge used to indicate managed profile applications. + </li> + </ul> + <h3 id="3_10_accessibility"> + 3.10. Accessibility + </h3> + <p> + Android provides an accessibility layer that helps users with disabilities to navigate their devices more easily. In addition, Android provides platform APIs that enable accessibility service implementations to receive callbacks for user and system events and generate alternate feedback mechanisms, such as text-to-speech, haptic feedback, and trackball/d-pad navigation. + </p> + <p> + If device implementations support third-party accessibility services, they: + </p> + <ul> + <li>[C-1-1] MUST provide an implementation of the Android accessibility framework as described in the <a href="http://developer.android.com/reference/android/view/accessibility/package-summary.html">accessibility APIs</a> SDK documentation. + </li> + <li>[C-1-2] MUST generate accessibility events and deliver the appropriate <code>AccessibilityEvent</code> to all registered <a href="http://developer.android.com/reference/android/accessibilityservice/AccessibilityService.html"><code>AccessibilityService</code></a> implementations as documented in the SDK. + </li> + <li>[C-1-3] MUST honor the <code>android.settings.ACCESSIBILITY_SETTINGS</code> intent to provide a user-accessible mechanism to enable and disable the third-party accessibility services alongside the preloaded accessibility services. + </li> + <li>[C-1-4] MUST add a button in the system's navigation bar allowing the user to control the accessibility service when the enabled accessibility services declare the <a href="https://developer.android.com/reference/android/accessibilityservice/AccessibilityServiceInfo.html#FLAG%5FREQUEST%5FACCESSIBILITY%5FBUTTON"><code>AccessibilityServiceInfo.FLAG_REQUEST_ACCESSIBILITY_BUTTON</code></a> . Note that for device implementations with no system navigation bar, this requirement is not applicable, but device implementations SHOULD provide a user affordance to control these accessibility services. + </li> + </ul> + <p> + If device implementations include preloaded accessibility services, they: + </p> + <ul> + <li>[C-2-1] MUST implement these preloaded accessibility services as [Direct Boot aware] (https://developer.android.com/reference/android/content/pm/ComponentInfo.html#directBootAware) apps when the data storage is encrypted with File Based Encryption (FBE). + </li> + <li>SHOULD provide a mechanism in the out-of-box setup flow for users to enable relevant accessibility services, as well as options to adjust the font size, display size and magnification gestures. + </li> + </ul> + <h3 id="3_11_text-to-speech"> + 3.11. Text-to-Speech + </h3> + <p> + Android includes APIs that allow applications to make use of text-to-speech (TTS) services and allows service providers to provide implementations of TTS services. + </p> + <p> + If device implementations reporting the feature android.hardware.audio.output, they: + </p> + <ul> + <li>[C-1-1] MUST support the <a href="http://developer.android.com/reference/android/speech/tts/package-summary.html">Android TTS framework</a> APIs. + </li> + </ul> + <p> + If device implementations support installation of third-party TTS engines, they: + </p> + <ul> + <li>[C-2-1] MUST provide user affordance to allow the user to select a TTS engine for use at system level. + </li> + </ul> + <h3 id="3_12_tv_input_framework"> + 3.12. TV Input Framework + </h3> + <p> + The <a href="http://source.android.com/devices/tv/index.html">Android Television Input Framework (TIF)</a> simplifies the delivery of live content to Android Television devices. TIF provides a standard API to create input modules that control Android Television devices. + </p> + <p> + If device implementations support TIF, they: + </p> + <ul> + <li>[C-1-1] MUST declare the platform feature <code>android.software.live_tv</code>. + </li> + <li>[C-1-2] MUST preload a TV application (TV App) and meet all requirements described in <a href="#3_12_tv-input-framework">section 3.12.1</a>. + </li> + </ul> + <h4 id="3_12_1_tv_app"> + 3.12.1. TV App + </h4> + <p> + If device implementations support TIF: + </p> + <ul> + <li>[C-1-1] The TV App MUST provide facilities to install and use <a href="http://developer.android.com/reference/android/media/tv/TvContract.Channels.html">TV Channels</a> and meet the following requirements: + </li> + </ul> + <p> + The TV app that is required for Android device implementations declaring the <code>android.software.live_tv</code> feature flag, MUST meet the following requirements: + </p> + <ul> + <li>Device implementations SHOULD allow third-party TIF-based inputs (<a href="https://source.android.com/devices/tv/index.html#third-party_input_example">third-party inputs</a>) to be installed and managed. + </li> + <li>Device implementations MAY provide visual separation between pre-installed <a href="https://source.android.com/devices/tv/index.html#tv_inputs">TIF-based inputs</a> (installed inputs) and third-party inputs. + </li> + <li>Device implementations SHOULD NOT display the third-party inputs more than a single navigation action away from the TV App (i.e. expanding a list of third-party inputs from the TV App). + </li> + </ul> + <p> + The Android Open Source Project provides an implementation of the TV App that meets the above requirements. + </p> + <h5 id="3_12_1_1_electronic_program_guide"> + 3.12.1.1. Electronic Program Guide + </h5> + <p> + If device implementations support TIF, they: + </p> + <ul> + <li>[C-1-1] MUST show an informational and interactive overlay, which MUST include an electronic program guide (EPG) generated from the values in the <a href="https://developer.android.com/reference/android/media/tv/TvContract.Programs.html">TvContract.Programs</a> fields. + </li> + <li>[C-1-2] On channel change, device implementations MUST display EPG data for the currently playing program. + </li> + <li>[SR] The EPG is STRONGLY RECOMMENDED to display installed inputs and third-party inputs with equal prominence. The EPG SHOULD NOT display the third-party inputs more than a single navigation action away from the installed inputs on the EPG. + </li> + <li>The EPG SHOULD display information from all installed inputs and third-party inputs. + </li> + <li>The EPG MAY provide visual separation between the installed inputs and third-party inputs. + </li> + </ul> + <h5 id="3_12_1_2_navigation"> + 3.12.1.2. Navigation + </h5> + <p> + If device implementations support TIF, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST allow navigation for the following functions via the D-pad, Back, and Home keys on the Android Television device’s input device(s) (i.e. remote control, remote control application, or game controller): + </p> + <ul> + <li>Changing TV channels + </li> + <li>Opening EPG + </li> + <li>Configuring and tuning to third-party TIF-based inputs (if those inputs are supported) + </li> + <li>Opening Settings menu + </li> + </ul> + </li> + <li> + <p> + SHOULD pass key events to HDMI inputs through CEC. + </p> + </li> + </ul> + <h5 id="3_12_1_3_tv_input_app_linking"> + 3.12.1.3. TV input app linking + </h5> + <p> + Android Television device implementations SHOULD support <a href="http://developer.android.com/reference/android/media/tv/TvContract.Channels.html#COLUMN_APP_LINK_INTENT_URI">TV input app linking</a>, which allows all inputs to provide activity links from the current activity to another activity (i.e. a link from live programming to related content). The TV App SHOULD show TV input app linking when it is provided. + </p> + <h5 id="3_12_1_4_time_shifting"> + 3.12.1.4. Time shifting + </h5> + <p> + If device implementations support TIF, they: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to support time shifting, which allows the user to pause and resume live content. + </li> + <li>SHOULD provide the user a way to pause and resume the currently playing program, if time shifting for that program <a href="https://developer.android.com/reference/android/media/tv/TvInputManager.html#TIME_SHIFT_STATUS_AVAILABLE">is available</a>. + </li> + </ul> + <h5 id="3_12_1_5_tv_recording"> + 3.12.1.5. TV recording + </h5> + <p> + If device implementations support TIF, they: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to support TV recording. + </li> + <li>If the TV input supports recording and the recording of a program is not <a href="https://developer.android.com/reference/android/media/tv/TvContract.Programs.html#COLUMN_RECORDING_PROHIBITED">prohibited</a>, the EPG MAY provide a way to <a href="https://developer.android.com/reference/android/media/tv/TvInputInfo.html#canRecord%28%29">record a program</a>. + </li> + </ul> + <h3 id="3_13_quick_settings"> + 3.13. Quick Settings + </h3> + <p> + Android provides a Quick Settings UI component that allows quick access to frequently used or urgently needed actions. + </p> + <p> + If device implementations include a Quick Settings UI component, they: + </p> + <ul> + <li>[C-1-1] MUST allow the user to add or remove the tiles provided through the <a href="https://developer.android.com/reference/android/service/quicksettings/package-summary.html"><code>quicksettings</code></a> APIs from a third-party app. + </li> + <li>[C-1-2] MUST NOT automatically add a tile from a third-party app directly to the Quick Settings. + </li> + <li>[C-1-3] MUST display all the user-added tiles from third-party apps alongside the system-provided quick setting tiles. + </li> + </ul> + <h3 id="3_14_media_ui"> + 3.14. Media UI + </h3> + <p> + If device implementations include the UI framework that supports third-party apps that depend on <a href="http://developer.android.com/reference/android/media/browse/MediaBrowser.html"><code>MediaBrowser</code></a> and <a href="http://developer.android.com/reference/android/media/session/MediaSession.html"><code>MediaSession</code></a> , they: + </p> + <ul> + <li>[C-1-1] MUST display <a href="http://developer.android.com/reference/android/media/browse/MediaBrowser.MediaItem.html">MediaItem</a> icons and notification icons unaltered. + </li> + <li>[C-1-2] MUST display those items as described by MediaSession, e.g., metadata, icons, imagery. + </li> + <li>[C-1-3] MUST show app title. + </li> + <li>[C-1-4] MUST have drawer to present <a href="http://developer.android.com/reference/android/media/browse/MediaBrowser.html">MediaBrowser</a> hierarchy. + </li> + <li>[C-1-5] MUST consider double tap of <a href="https://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_HEADSETHOOK"><code>KEYCODE_HEADSETHOOK</code></a> or <a href="https://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_MEDIA_PLAY_PAUSE"><code>KEYCODE_MEDIA_PLAY_PAUSE</code></a> as <a href="https://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_MEDIA_NEXT"><code>KEYCODE_MEDIA_NEXT</code></a> for <a href="https://developer.android.com/reference/android/media/session/MediaSession.Callback.html#onMediaButtonEvent%28android.content.Intent%29"><code>MediaSession.Callback#onMediaButtonEvent</code></a>. + </li> + </ul> + <h3 id="3_15_instant_apps"> + 3.15. Instant Apps + </h3> + <p> + Device implementations MUST satisfy the following requirements: + </p> + <ul> + <li>[C-0-1] Instant Apps MUST only be granted permissions that have the <a href="https://developer.android.com/guide/topics/manifest/permission-element.html#plevel"><code>android:protectionLevel</code></a> set to <code>"ephemeral"</code>. + </li> + <li>[C-0-2] Instant Apps MUST NOT interact with installed apps via <a href="https://developer.android.com/reference/android/content/Intent.html">implicit intents</a> unless one of the following is true: + <ul> + <li>The component's intent pattern filter is exposed and has CATEGORY_BROWSABLE + </li> + <li>The action is one of ACTION_SEND, ACTION_SENDTO, ACTION_SEND_MULTIPLE + </li> + <li>The target is explicitly exposed with <a href="https://developer.android.com/reference/android/R.attr.html#visibleToInstantApps">android:visibleToInstantApps</a> + </li> + </ul> + </li> + <li>[C-0-3] Instant Apps MUST NOT interact explicitly with installed apps unless the component is exposed via android:visibleToInstantApps. + </li> + <li>[C-0-4] IInstalled Apps MUST NOT see details about Instant Apps on the device unless the Instant App explicitly connects to the installed application. + </li> + </ul> + <h3 id="3_16_companion_device_pairing"> + 3.16. Companion Device Pairing + </h3> + <p> + Android includes support for companion device pairing to more effectively manage association with companion devices and provides the <a href="https://developer.android.com/reference/android/companion/CompanionDeviceManager.html"><code>CompanionDeviceManager</code></a> API for apps to access this feature. + </p> + <p> + If device implementations support the companion device pairing feature, they: + </p> + <ul> + <li>[C-1-1] MUST declare the feature flag <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html?#FEATURE_COMPANION_DEVICE_SETUP"><code>FEATURE_COMPANION_DEVICE_SETUP</code></a> . + </li> + <li>[C-1-2] MUST ensure the APIs in the <a href="https://developer.android.com/reference/android/companion/package-summary.html"><code>android.companion</code></a> package is fully implemented. + </li> + <li>[C-1-3] MUST provide user affordances for the user to select/confirm a companion device is present and operational. + </li> + </ul> + <h2 id="4_application_packaging_compatibility"> + 4. Application Packaging Compatibility + </h2> + <p> + Devices implementations: + </p> + <ul> + <li>[C-0-1] MUST be capable of installing and running Android “.apk” files as generated by the “aapt” tool included in the <a href="http://developer.android.com/tools/help/index.html">official Android SDK</a>. + </li> + <li>As the above requirement may be challenging, device implementations are RECOMMENDED to use the AOSP reference implementation's package management systemDevice implementations. + </li> + <li>[C-0-2] MUST support verifying “.apk” files using the <a href="https://source.android.com/security/apksigning/v2.html">APK Signature Scheme v2</a> and <a href="https://source.android.com/security/apksigning/v2.html#v1-verification">JAR signing</a>. + </li> + <li>[C-0-3] MUST NOT extend either the <a href="http://developer.android.com/guide/components/fundamentals.html">.apk</a>, <a href="http://developer.android.com/guide/topics/manifest/manifest-intro.html">Android Manifest</a>, <a href="https://android.googlesource.com/platform/dalvik/">Dalvik bytecode</a>, or RenderScript bytecode formats in such a way that would prevent those files from installing and running correctly on other compatible devices. + </li> + <li>[C-0-4] MUST NOT allow apps other than the current "installer of record" for the package to silently uninstall the app without any prompt, as documented in the SDK for the <a href="https://developer.android.com/reference/android/Manifest.permission.html#DELETE_PACKAGES"><code>DELETE_PACKAGE</code></a> permission. The only exceptions are the system package verifier app handling <a href="https://developer.android.com/reference/android/content/Intent.html#ACTION_PACKAGE_NEEDS_VERIFICATION">PACKAGE_NEEDS_VERIFICATION</a> intent and the storage manager app handling <a href="https://developer.android.com/reference/android/os/storage/StorageManager.html#ACTION_MANAGE_STORAGE">ACTION_MANAGE_STORAGE</a> intent. + </li> + </ul> + <p> + Device implementations MUST NOT install application packages from unknown sources, unless the app that <a href="https://developer.android.com/reference/android/content/Intent.html#ACTION_INSTALL_PACKAGE">requests the installation</a> meets all the following requirements: + </p> + <ul> + <li>It MUST declare the <a href="http://developer.android.com/reference/android/Manifest.permission.html#REQUEST_INSTALL_PACKAGES"><code>REQUEST_INSTALL_PACKAGES</code></a> permission or have the <code>android:targetSdkVersion</code> set at 24 or lower. + </li> + <li>It MUST have been granted permission by the user to install apps from unknown sources. + </li> + </ul> + <p> + Device implementations MUST have an activity that handles the <a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_MANAGE_UNKNOWN_APP_SOURCES"><code>android.settings.MANAGE_UNKNOWN_APP_SOURCES</code></a> intent. They SHOULD provide a user affordance to grant/revoke the permission to install apps from unknown sources per application, but MAY choose to implement this as a no-op and return <code>RESULT_CANCELED</code> for <a href="http://developer.android.com/reference/android/app/Activity.html#startActivityForResult%28android.content.Intent,%20int%29"><code>startActivityForResult()</code></a>, if the device implementation does not want to allow users to have this choice. However even in such cases, they SHOULD indicate to the user why there is no such choice presented. + </p> + <h2 id="5_multimedia_compatibility"> + 5. Multimedia Compatibility + </h2> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST support the media formats, encoders, decoders, file types, and container formats defined in <a href="#5_1_media-codecs.md">section 5.1</a> for each and every codec declared by <code>MediaCodecList</code>. + </li> + <li>[C-0-2] MUST declare and report support of the encoders, decoders available to third-party applications via <a href="http://developer.android.com/reference/android/media/MediaCodecList.html"><code>MediaCodecList</code></a>. + </li> + <li>[C-0-3] MUST be able to decode and make available to third-party apps all the formats it can encode. This includes all bitstreams that its encoders generate and the profiles reported in its <a href="http://developer.android.com/reference/android/media/CamcorderProfile.html"><code>CamcorderProfile</code></a>. + </li> + </ul> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD aim for minimum codec latency, in others words, they + <ul> + <li>SHOULD NOT consume and store input buffers and return input buffers only once processed. + </li> + <li>SHOULD NOT hold onto decoded buffers for longer than as specified by the standard (e.g. SPS). + </li> + <li>SHOULD NOT hold onto encoded buffers longer than required by the GOP structure. + </li> + </ul> + </li> + </ul> + <p> + All of the codecs listed in the section below are provided as software implementations in the preferred Android implementation from the Android Open Source Project. + </p> + <p> + Please note that neither Google nor the Open Handset Alliance make any representation that these codecs are free from third-party patents. Those intending to use this source code in hardware or software products are advised that implementations of this code, including in open source software or shareware, may require patent licenses from the relevant patent holders. + </p> + <h3 id="5_1_media_codecs"> + 5.1. Media Codecs + </h3> + <h4 id="5_1_1_audio_encoding"> + 5.1.1. Audio Encoding + </h4> + <p> + See more details in <a href="#5_1_3_audio_codecs_details">5.1.3. Audio Codecs Details</a>. + </p> + <p> + If device implementations declare <code>android.hardware.microphone</code>, they MUST support the following audio encoding: + </p> + <ul> + <li>[C-1-1] PCM/WAVE + </li> + </ul> + <h4 id="5_1_2_audio_decoding"> + 5.1.2. Audio Decoding + </h4> + <p> + See more details in <a href="#5_1_3_audio_codecs_details">5.1.3. Audio Codecs Details</a>. + </p> + <p> + If device implementations declare support for the <code>android.hardware.audio.output</code> feature, they: + </p> + <ul> + <li>[C-1-1] MPEG-4 AAC Profile (AAC LC) + </li> + <li>[C-1-2] MPEG-4 HE AAC Profile (AAC+) + </li> + <li>[C-1-3] MPEG-4 HE AACv2 Profile (enhanced AAC+) + </li> + <li>[C-1-4] AAC ELD (enhanced low delay AAC) + </li> + <li>[C-1-5] FLAC + </li> + <li>[C-1-6] MP3 + </li> + <li>[C-1-7] MIDI + </li> + <li>[C-1-8] Vorbis + </li> + <li>[C-1-9] PCM/WAVE + </li> + <li>[C-1-10] Opus + </li> + </ul> + <p> + If device implementations support the decoding of AAC input buffers of multichannel streams (i.e. more than two channels) to PCM through the default AAC audio decoder in the <code>android.media.MediaCodec</code> API, the following MUST be supported: + </p> + <ul> + <li>[C-2-1] Decoding MUST be performed without downmixing (e.g. a 5.0 AAC stream must be decoded to five channels of PCM, a 5.1 AAC stream must be decoded to six channels of PCM). + </li> + <li>[C-2-2] Dynamic range metadata MUST be as defined in "Dynamic Range Control (DRC)" in ISO/IEC 14496-3, and the <code>android.media.MediaFormat</code> DRC keys to configure the dynamic range-related behaviors of the audio decoder. The AAC DRC keys were introduced in API 21,and are: KEY_AAC_DRC_ATTENUATION_FACTOR, KEY_AAC_DRC_BOOST_FACTOR, KEY_AAC_DRC_HEAVY_COMPRESSION, KEY_AAC_DRC_TARGET_REFERENCE_LEVEL and KEY_AAC_ENCODED_TARGET_LEVEL + </li> + </ul> + <h4 id="5_1_3_audio_codecs_details"> + 5.1.3. Audio Codecs Details + </h4> + <table> + <tr> + <th> + Format/Codec + </th> + <th> + Details + </th> + <th> + Supported File Types/Container Formats + </th> + </tr> + <tr> + <td> + MPEG-4 AAC Profile<br /> + (AAC LC) + </td> + <td> + Support for mono/stereo/5.0/5.1 content with standard sampling rates from 8 to 48 kHz. + </td> + <td> + <ul> + <li class="table_list">3GPP (.3gp) + </li> + <li class="table_list">MPEG-4 (.mp4, .m4a) + </li> + <li class="table_list">ADTS raw AAC (.aac, ADIF not supported) + </li> + <li class="table_list">MPEG-TS (.ts, not seekable) + </li> + </ul> + </td> + </tr> + <tr> + <td> + MPEG-4 HE AAC Profile (AAC+) + </td> + <td> + Support for mono/stereo/5.0/5.1 content with standard sampling rates from 16 to 48 kHz. + </td> + <td></td> + </tr> + <tr> + <td> + MPEG-4 HE AACv2<br /> + Profile (enhanced AAC+) + </td> + <td> + Support for mono/stereo/5.0/5.1 content with standard sampling rates from 16 to 48 kHz. + </td> + <td></td> + </tr> + <tr> + <td> + AAC ELD (enhanced low delay AAC) + </td> + <td> + Support for mono/stereo content with standard sampling rates from 16 to 48 kHz. + </td> + <td></td> + </tr> + <tr> + <td> + AMR-NB + </td> + <td> + 4.75 to 12.2 kbps sampled @ 8 kHz + </td> + <td> + 3GPP (.3gp) + </td> + </tr> + <tr> + <td> + AMR-WB + </td> + <td> + 9 rates from 6.60 kbit/s to 23.85 kbit/s sampled @ 16 kHz + </td> + <td></td> + </tr> + <tr> + <td> + FLAC + </td> + <td> + Mono/Stereo (no multichannel). Sample rates up to 48 kHz (but up to 44.1 kHz is RECOMMENDED on devices with 44.1 kHz output, as the 48 to 44.1 kHz downsampler does not include a low-pass filter). 16-bit RECOMMENDED; no dither applied for 24-bit. + </td> + <td> + FLAC (.flac) only + </td> + </tr> + <tr> + <td> + MP3 + </td> + <td> + Mono/Stereo 8-320Kbps constant (CBR) or variable bitrate (VBR) + </td> + <td> + MP3 (.mp3) + </td> + </tr> + <tr> + <td> + MIDI + </td> + <td> + MIDI Type 0 and 1. DLS Version 1 and 2. XMF and Mobile XMF. Support for ringtone formats RTTTL/RTX, OTA, and iMelody + </td> + <td> + <ul> + <li class="table_list">Type 0 and 1 (.mid, .xmf, .mxmf) + </li> + <li class="table_list">RTTTL/RTX (.rtttl, .rtx) + </li> + <li class="table_list">OTA (.ota) + </li> + <li class="table_list">iMelody (.imy) + </li> + </ul> + </td> + </tr> + <tr> + <td> + Vorbis + </td> + <td></td> + <td> + <ul> + <li class="table_list">Ogg (.ogg) + </li> + <li class="table_list">Matroska (.mkv, Android 4.0+) + </li> + </ul> + </td> + </tr> + <tr> + <td> + PCM/WAVE + </td> + <td> + 16-bit linear PCM (rates up to limit of hardware). Devices MUST support sampling rates for raw PCM recording at 8000, 11025, 16000, and 44100 Hz frequencies. + </td> + <td> + WAVE (.wav) + </td> + </tr> + <tr> + <td> + Opus + </td> + <td></td> + <td> + Matroska (.mkv), Ogg(.ogg) + </td> + </tr> + </table> + <h4 id="5_1_4_image_encoding"> + 5.1.4. Image Encoding + </h4> + <p> + See more details in <a href="#5_1_6_image_codecs_details">5.1.6. Image Codecs Details</a>. + </p> + <p> + Device implementations MUST support encoding the following image encoding: + </p> + <ul> + <li>[C-0-1] JPEG + </li> + <li>[C-0-2] PNG + </li> + <li>[C-0-3] WebP + </li> + </ul> + <h4 id="5_1_5_image_decoding"> + 5.1.5. Image Decoding + </h4> + <p> + See more details in <a href="#5_1_6_image_codecs_details">5.1.6. Image Codecs Details</a>. + </p> + <p> + Device impelementations MUST support encoding the following image decoding: + </p> + <ul> + <li>[C-0-1] JPEG + </li> + <li>[C-0-2] GIF + </li> + <li>[C-0-3] PNG + </li> + <li>[C-0-4] BMP + </li> + <li>[C-0-5] WebP + </li> + <li>[C-0-6] Raw + </li> + </ul> + <h4 id="5_1_6_image_codecs_details"> + 5.1.6. Image Codecs Details + </h4> + <table> + <tr> + <th> + Format/Codec + </th> + <th> + Details + </th> + <th> + Supported File Types/Container Formats + </th> + </tr> + <tr> + <td> + JPEG + </td> + <td> + Base+progressive + </td> + <td> + JPEG (.jpg) + </td> + </tr> + <tr> + <td> + GIF + </td> + <td></td> + <td> + GIF (.gif) + </td> + </tr> + <tr> + <td> + PNG + </td> + <td></td> + <td> + PNG (.png) + </td> + </tr> + <tr> + <td> + BMP + </td> + <td></td> + <td> + BMP (.bmp) + </td> + </tr> + <tr> + <td> + WebP + </td> + <td></td> + <td> + WebP (.webp) + </td> + </tr> + <tr> + <td> + Raw + </td> + <td></td> + <td> + ARW (.arw), CR2 (.cr2), DNG (.dng), NEF (.nef), NRW (.nrw), ORF (.orf), PEF (.pef), RAF (.raf), RW2 (.rw2), SRW (.srw) + </td> + </tr> + </table> + <h4 id="5_1_7_video_codecs"> + 5.1.7. Video Codecs + </h4> + <ul> + <li>For acceptable quality of web video streaming and video-conference services, device implementations SHOULD use a hardware VP8 codec that meets the <a href="http://www.webmproject.org/hardware/rtc-coding-requirements/">requirements</a>. + </li> + </ul> + <p> + If device implementations include a video decoder or encoder: + </p> + <ul> + <li> + <p> + [C-1-1] Video codecs MUST support output and input bytebuffer sizes that accommodate the largest feasible compressed and uncompressed frame as dictated by the standard and configuration but also not overallocate. + </p> + </li> + <li> + <p> + [C-1-2] Video encoders and decoders MUST support YUV420 flexible color format (COLOR_FormatYUV420Flexible). + </p> + </li> + </ul> + <p> + If device implementations advertise HDR profile support through <a href="https://developer.android.com/reference/android/view/Display.HdrCapabilities.html"><code>Display.HdrCapabilities</code></a>, they: + </p> + <ul> + <li>[C-2-1] MUST support HDR static metadata parsing and handling. + </li> + </ul> + <p> + If device implementations advertise intra refresh support through <code>FEATURE_IntraRefresh</code> in the <a href="https://developer.android.com/reference/android/media/MediaCodecInfo.CodecCapabilities.html#FEATURE_IntraRefresh"><code>MediaCodecInfo.CodecCapabilities</code></a> class, they: + </p> + <ul> + <li>[C-3-1]MUST support the refresh periods in the range of 10 - 60 frames and accurately operate within 20% of configured refresh period. + </li> + </ul> + <h4 id="5_1_8_video_codecs_list"> + 5.1.8. Video Codecs List + </h4> + <table> + <tr> + <th> + Format/Codec + </th> + <th> + Details + </th> + <th> + Supported File Types/<br /> + Container Formats + </th> + </tr> + <tr> + <td> + H.263 + </td> + <td></td> + <td> + <ul> + <li class="table_list">3GPP (.3gp) + </li> + <li class="table_list">MPEG-4 (.mp4) + </li> + </ul> + </td> + </tr> + <tr> + <td> + H.264 AVC + </td> + <td> + See <a href="#5_2_video_encoding">section 5.2</a> and <a href="#5_3_video_decoding">5.3</a> for details + </td> + <td> + <ul> + <li class="table_list">3GPP (.3gp) + </li> + <li class="table_list">MPEG-4 (.mp4) + </li> + <li class="table_list">MPEG-2 TS (.ts, AAC audio only, not seekable, Android 3.0+) + </li> + </ul> + </td> + </tr> + <tr> + <td> + H.265 HEVC + </td> + <td> + See <a href="#5_3_video_decoding">section 5.3</a> for details + </td> + <td> + MPEG-4 (.mp4) + </td> + </tr> + <tr> + <td> + MPEG-2 + </td> + <td> + Main Profile + </td> + <td> + MPEG2-TS + </td> + </tr> + <tr> + <td> + MPEG-4 SP + </td> + <td></td> + <td> + 3GPP (.3gp) + </td> + </tr> + <tr> + <td> + VP8 + </td> + <td> + See <a href="#5_2_video_encoding">section 5.2</a> and <a href="#5_3_video_decoding">5.3</a> for details + </td> + <td> + <ul> + <li class="table_list"> + <a href="http://www.webmproject.org/">WebM (.webm)</a> + </li> + <li class="table_list">Matroska (.mkv) + </li> + </ul> + </td> + </tr> + <tr> + <td> + VP9 + </td> + <td> + See <a href="#5_3_video_decoding">section 5.3</a> for details + </td> + <td> + <ul> + <li class="table_list"> + <a href="http://www.webmproject.org/">WebM (.webm)</a> + </li> + <li class="table_list">Matroska (.mkv) + </li> + </ul> + </td> + </tr> + </table> + <h3 id="5_2_video_encoding"> + 5.2. Video Encoding + </h3> + <p> + If device implementations support any video encoder and make it available to third-party apps, they: + </p> + <ul> + <li>SHOULD NOT be, over two sliding windows, more than ~15% over the bitrate between intraframe (I-frame) intervals. + </li> + <li>SHOULD NOT be more than ~100% over the bitrate over a sliding window of 1 second. + </li> + </ul> + <p> + If device implementations include an embedded screen display with the diagonal length of at least 2.5 inches or include a video output port or declare the support of a camera via the <code>android.hardware.camera.any</code> feature flag, they: + </p> + <ul> + <li>[C-1-1] MUST include the support of at least one of the VP8 or H.264 video encoders, and make it available for third-party applications. + </li> + <li>SHOULD support both VP8 and H.264 video encoders, and make it available for third-party applications. + </li> + </ul> + <p> + If device implementations support any of the H.264, VP8, VP9 or HEVC video encoders and make it available to third-party applications, they: + </p> + <ul> + <li>[C-2-1] MUST support dynamically configurable bitrates. + </li> + <li>SHOULD support variable frame rates, where video encoder SHOULD determine instantaneous frame duration based on the timestamps of input buffers, and allocate its bit bucket based on that frame duration. + </li> + </ul> + <p> + If device implementations support the MPEG-4 SP video encoder and make it available to third-party apps, they: + </p> + <ul> + <li>SHOULD support dynamically configurable bitrates for the supported encoder. + </li> + </ul> + <h4 id="5_2_1_h_263"> + 5.2.1. H.263 + </h4> + <p> + If device implementations support H.263 encoders and make it available to third-party apps, they: + </p> + <ul> + <li>[C-1-1] MUST support Baseline Profile Level 45. + </li> + <li>SHOULD support dynamically configurable bitrates for the supported encoder. + </li> + </ul> + <h4 id="5_2_2_h-264"> + 5.2.2. H-264 + </h4> + <p> + If device implementations support H.264 codec, they: + </p> + <ul> + <li>[C-1-1] MUST support Baseline Profile Level 3. However, support for ASO (Arbitrary Slice Ordering), FMO (Flexible Macroblock Ordering) and RS (Redundant Slices) is OPTIONAL. Moreover, to maintain compatibility with other Android devices, it is RECOMMENDED that ASO, FMO and RS are not used for Baseline Profile by encoders. + </li> + <li>[C-1-2] MUST support the SD (Standard Definition) video encoding profiles in the following table. + </li> + <li>SHOULD support Main Profile Level 4. + </li> + <li>SHOULD support the HD (High Definition) video encoding profiles as indicated in the following table. + </li> + </ul> + <p> + If device implementations report support of H.264 encoding for 720p or 1080p resolution videos through the media APIs, they: + </p> + <ul> + <li>[C-2-1] MUST support the encoding profiles in the following table. + </li> + </ul> + <table> + <tr> + <th></th> + <th> + SD (Low quality) + </th> + <th> + SD (High quality) + </th> + <th> + HD 720p + </th> + <th> + HD 1080p + </th> + </tr> + <tr> + <th> + Video resolution + </th> + <td> + 320 x 240 px + </td> + <td> + 720 x 480 px + </td> + <td> + 1280 x 720 px + </td> + <td> + 1920 x 1080 px + </td> + </tr> + <tr> + <th> + Video frame rate + </th> + <td> + 20 fps + </td> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + </tr> + <tr> + <th> + Video bitrate + </th> + <td> + 384 Kbps + </td> + <td> + 2 Mbps + </td> + <td> + 4 Mbps + </td> + <td> + 10 Mbps + </td> + </tr> + </table> + <h4 id="5_2_3_vp8"> + 5.2.3. VP8 + </h4> + <p> + If device implementations support VP8 codec, they: + </p> + <ul> + <li>[C-1-1] MUST support the SD video encoding profiles. + </li> + <li>SHOULD support the following HD (High Definition) video encoding profiles. + </li> + <li>SHOULD support writing Matroska WebM files. + </li> + <li>SHOULD use a hardware VP8 codec that meets the <a href="http://www.webmproject.org/hardware/rtc-coding-requirements">WebM project RTC hardware coding requirements</a>, to ensure acceptable quality of web video streaming and video-conference services. + </li> + </ul> + <p> + If device implementations report support of VP8 encoding for 720p or 1080p resolution videos through the media APIs, they: + </p> + <ul> + <li>[C-2-1] MUST support the encoding profiles in the following table. + </li> + </ul> + <table> + <tr> + <th></th> + <th> + SD (Low quality) + </th> + <th> + SD (High quality) + </th> + <th> + HD 720p + </th> + <th> + HD 1080p + </th> + </tr> + <tr> + <th> + Video resolution + </th> + <td> + 320 x 180 px + </td> + <td> + 640 x 360 px + </td> + <td> + 1280 x 720 px + </td> + <td> + 1920 x 1080 px + </td> + </tr> + <tr> + <th> + Video frame rate + </th> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + </tr> + <tr> + <th> + Video bitrate + </th> + <td> + 800 Kbps + </td> + <td> + 2 Mbps + </td> + <td> + 4 Mbps + </td> + <td> + 10 Mbps + </td> + </tr> + </table> + <h4 id="5_2_4_vp9"> + 5.2.4. VP9 + </h4> + <p> + If device implementations support VP9 codec, they: + </p> + <ul> + <li>SHOULD support writing Matroska WebM files. + </li> + </ul> + <h3 id="5_3_video_decoding"> + 5.3. Video Decoding + </h3> + <p> + If device implementations support VP8, VP9, H.264, or H.265 codecs, they: + </p> + <ul> + <li>[C-1-1] MUST support dynamic video resolution and frame rate switching through the standard Android APIs within the same stream for all VP8, VP9, H.264, and H.265 codecs in real time and up to the maximum resolution supported by each codec on the device. + </li> + </ul> + <p> + If device implementations declare support for the Dolby Vision decoder through <a href="https://developer.android.com/reference/android/view/Display.HdrCapabilities.html#HDR_TYPE_DOLBY_VISION"><code>HDR_TYPE_DOLBY_VISION</code></a> , they: + </p> + <ul> + <li>[C-2-1] MUST provide a Dolby Vision-capable extractor. + </li> + <li>[C-2-2] MUST properly display Dolby Vision content on the device screen or on a standard video output port (e.g., HDMI). + </li> + <li>[C-2-3] MUST set the track index of backward-compatible base-layer(s) (if present) to be the same as the combined Dolby Vision layer's track index. + </li> + </ul> + <h4 id="5_3_1_mpeg-2"> + 5.3.1. MPEG-2 + </h4> + <p> + If device implementations support MPEG-2 decoders, they: + </p> + <ul> + <li>[C-1-1] MUST support the Main Profile High Level. + </li> + </ul> + <h4 id="5_3_2_h_263"> + 5.3.2. H.263 + </h4> + <p> + If device implementations support H.263 decoders, they: + </p> + <ul> + <li>[C-1-1] MUST support Baseline Profile Level 30 and Level 45. + </li> + </ul> + <h4 id="5_3_3_mpeg-4"> + 5.3.3. MPEG-4 + </h4> + <p> + If device implementations with MPEG-4 decoders, they: + </p> + <ul> + <li>[C-1-1] MUST support Simple Profile Level 3. + </li> + </ul> + <h4 id="5_3_4_h_264"> + 5.3.4. H.264 + </h4> + <p> + If device implementations support H.264 decoders, they: + </p> + <ul> + <li>[C-1-1] MUST support Main Profile Level 3.1 and Baseline Profile. Support for ASO (Arbitrary Slice Ordering), FMO (Flexible Macroblock Ordering) and RS (Redundant Slices) is OPTIONAL. + </li> + <li>[C-1-2] MUST be capable of decoding videos with the SD (Standard Definition) profiles listed in the following table and encoded with the Baseline Profile and Main Profile Level 3.1 (including 720p30). + </li> + <li>SHOULD be capable of decoding videos with the HD (High Definition) profiles as indicated in the following table. + </li> + </ul> + <p> + If the height that is reported by the <code>Display.getSupportedModes()</code> method is equal or greater than the video resolution, device implementations: + </p> + <ul> + <li>[C-2-1] MUST support the HD 720p video encoding profiles in the following table. + </li> + <li>[C-2-2] MUST support the HD 1080p video encoding profiles in the following table. + </li> + </ul> + <table> + <tr> + <th></th> + <th> + SD (Low quality) + </th> + <th> + SD (High quality) + </th> + <th> + HD 720p + </th> + <th> + HD 1080p + </th> + </tr> + <tr> + <th> + Video resolution + </th> + <td> + 320 x 240 px + </td> + <td> + 720 x 480 px + </td> + <td> + 1280 x 720 px + </td> + <td> + 1920 x 1080 px + </td> + </tr> + <tr> + <th> + Video frame rate + </th> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + <td> + 60 fps + </td> + <td> + 30 fps (60 fps<sup>Television</sup>) + </td> + </tr> + <tr> + <th> + Video bitrate + </th> + <td> + 800 Kbps + </td> + <td> + 2 Mbps + </td> + <td> + 8 Mbps + </td> + <td> + 20 Mbps + </td> + </tr> + </table> + <h4 id="5_3_5_h_265_(hevc)"> + 5.3.5. H.265 (HEVC) + </h4> + <p> + If device implementations support H.265 codec, they: + </p> + <ul> + <li>[C-1-1] MUST support the Main Profile Level 3 Main tier and the SD video decoding profiles as indicated in the following table. + </li> + <li>SHOULD support the HD decoding profiles as indicated in the following table. + </li> + <li>[C-1-2] MUST support the HD decoding profiles as indicated in the following table if there is a hardware decoder. + </li> + </ul> + <p> + If the height that is reported by the <code>Display.getSupportedModes()</code> method is equal to or greater than the video resolution, then: + </p> + <ul> + <li>[C-2-1] Device implementations MUST support at least one of H.265 or VP9 decoding of 720, 1080 and UHD profiles. + </li> + </ul> + <table> + <tr> + <th></th> + <th> + SD (Low quality) + </th> + <th> + SD (High quality) + </th> + <th> + HD 720p + </th> + <th> + HD 1080p + </th> + <th> + UHD + </th> + </tr> + <tr> + <th> + Video resolution + </th> + <td> + 352 x 288 px + </td> + <td> + 720 x 480 px + </td> + <td> + 1280 x 720 px + </td> + <td> + 1920 x 1080 px + </td> + <td> + 3840 x 2160 px + </td> + </tr> + <tr> + <th> + Video frame rate + </th> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + <td> + 30/60 fps (60 fps<sup>Television with H.265 hardware decoding</sup>) + </td> + <td> + 60 fps + </td> + </tr> + <tr> + <th> + Video bitrate + </th> + <td> + 600 Kbps + </td> + <td> + 1.6 Mbps + </td> + <td> + 4 Mbps + </td> + <td> + 5 Mbps + </td> + <td> + 20 Mbps + </td> + </tr> + </table> + <h4 id="5_3_6_vp8"> + 5.3.6. VP8 + </h4> + <p> + If device implementations support VP8 codec, they: + </p> + <ul> + <li>[C-1-1] MUST support the SD decoding profiles in the following table. + </li> + <li>SHOULD use a hardware VP8 codec that meets the <a href="" title="http://www.webmproject.org/hardware/rtc-coding-requirements/">requirements</a>. + </li> + <li>SHOULD support the HD decoding profiles in the following table. + </li> + </ul> + <p> + If the height as reported by the <code>Display.getSupportedModes()</code> method is equal or greater than the video resolution, then: + </p> + <ul> + <li>[C-2-1] Device implementations MUST support 720p profiles in the following table. + </li> + <li>[C-2-2] Device implementations MUST support 1080p profiles in the following table. + </li> + </ul> + <table> + <tr> + <th></th> + <th> + SD (Low quality) + </th> + <th> + SD (High quality) + </th> + <th> + HD 720p + </th> + <th> + HD 1080p + </th> + </tr> + <tr> + <th> + Video resolution + </th> + <td> + 320 x 180 px + </td> + <td> + 640 x 360 px + </td> + <td> + 1280 x 720 px + </td> + <td> + 1920 x 1080 px + </td> + </tr> + <tr> + <th> + Video frame rate + </th> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + <td> + 30 fps (60 fps<sup>Television</sup>) + </td> + <td> + 30 (60 fps<sup>Television</sup>) + </td> + </tr> + <tr> + <th> + Video bitrate + </th> + <td> + 800 Kbps + </td> + <td> + 2 Mbps + </td> + <td> + 8 Mbps + </td> + <td> + 20 Mbps + </td> + </tr> + </table> + <h4 id="5_3_7_vp9"> + 5.3.7. VP9 + </h4> + <p> + If device implementations support VP9 codec, they: + </p> + <ul> + <li>[C-1-1] MUST support the SD video decoding profiles as indicated in the following table. + </li> + <li>SHOULD support the HD decoding profiles as indicated in the following table. + </li> + </ul> + <p> + If device implementations support VP9 codec and a hardware decoder: + </p> + <ul> + <li>[C-2-2] MUST support the HD decoding profiles as indicated in the following table. + </li> + </ul> + <p> + If the height that is reported by the <code>Display.getSupportedModes()</code> method is equal to or greater than the video resolution, then: + </p> + <ul> + <li>[C-3-1] Device implementations MUST support at least one of VP9 or H.265 decoding of the 720, 1080 and UHD profiles. + </li> + </ul> + <table> + <tr> + <th></th> + <th> + SD (Low quality) + </th> + <th> + SD (High quality) + </th> + <th> + HD 720p + </th> + <th> + HD 1080p + </th> + <th> + UHD + </th> + </tr> + <tr> + <th> + Video resolution + </th> + <td> + 320 x 180 px + </td> + <td> + 640 x 360 px + </td> + <td> + 1280 x 720 px + </td> + <td> + 1920 x 1080 px + </td> + <td> + 3840 x 2160 px + </td> + </tr> + <tr> + <th> + Video frame rate + </th> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + <td> + 30 fps + </td> + <td> + 30 fps (60 fps<sup>Television with VP9 hardware decoding</sup>) + </td> + <td> + 60 fps + </td> + </tr> + <tr> + <th> + Video bitrate + </th> + <td> + 600 Kbps + </td> + <td> + 1.6 Mbps + </td> + <td> + 4 Mbps + </td> + <td> + 5 Mbps + </td> + <td> + 20 Mbps + </td> + </tr> + </table> + <h3 id="5_4_audio_recording"> + 5.4. Audio Recording + </h3> + <p> + While some of the requirements outlined in this section are listed as SHOULD since Android 4.3, the Compatibility Definition for future versions are planned to change these to MUST. Existing and new Android devices are <strong>STRONGLY RECOMMENDED</strong> to meet these requirements that are listed as SHOULD, or they will not be able to attain Android compatibility when upgraded to the future version. + </p> + <h4 id="5_4_1_raw_audio_capture"> + 5.4.1. Raw Audio Capture + </h4> + <p> + If device implementations declare <code>android.hardware.microphone</code>, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST allow capture of raw audio content with the following characteristics: + </p> + </li> + <li> + <p> + <strong>Format</strong>: Linear PCM, 16-bit + </p> + </li> + <li> + <strong>Sampling rates</strong>: 8000, 11025, 16000, 44100 Hz + </li> + <li> + <p> + <strong>Channels</strong>: Mono + </p> + </li> + <li> + <p> + [C-1-2] MUST capture at above sample rates without up-sampling. + </p> + </li> + <li>[C-1-3] MUST include an appropriate anti-aliasing filter when the sample rates given above are captured with down-sampling. + </li> + <li> + <p> + SHOULD allow AM radio and DVD quality capture of raw audio content, which means the following characteristics: + </p> + </li> + <li> + <p> + <strong>Format</strong>: Linear PCM, 16-bit + </p> + </li> + <li> + <strong>Sampling rates</strong>: 22050, 48000 Hz + </li> + <li> + <strong>Channels</strong>: Stereo + </li> + </ul> + <p> + If device implementations allow AM radio and DVD quality capture of raw audio content, they: + </p> + <ul> + <li>[C-2-1] MUST capture without up-sampling at any ratio higher than 16000:22050 or 44100:48000. + </li> + <li>[C-2-2] MUST include an appropriate anti-aliasing filter for any up-sampling or down-sampling. + </li> + </ul> + <h4 id="5_4_2_capture_for_voice_recognition"> + 5.4.2. Capture for Voice Recognition + </h4> + <p> + If device implementations declare <code>android.hardware.microphone</code>, they: + </p> + <ul> + <li>[C-1-1] MUST capture <code>android.media.MediaRecorder.AudioSource.VOICE_RECOGNITION</code> audio source at one of the sampling rates, 44100 and 48000. + </li> + <li>[C-1-2] MUST, by default, disable any noise reduction audio processing when recording an audio stream from the <code>AudioSource.VOICE_RECOGNITION</code> audio source. + </li> + <li>[C-1-3] MUST, by default, disable any automatic gain control when recording an audio stream from the <code>AudioSource.VOICE_RECOGNITION</code> audio source. + </li> + <li>SHOULD record the voice recognition audio stream with approximately flat amplitude versus frequency characteristics: specifically, ±3 dB, from 100 Hz to 4000 Hz. + </li> + <li>SHOULD record the voice recognition audio stream with input sensitivity set such that a 90 dB sound power level (SPL) source at 1000 Hz yields RMS of 2500 for 16-bit samples. + </li> + <li>SHOULD record the voice recognition audio stream so that the PCM amplitude levels linearly track input SPL changes over at least a 30 dB range from -18 dB to +12 dB re 90 dB SPL at the microphone. + </li> + <li>SHOULD record the voice recognition audio stream with total harmonic distortion (THD) less than 1% for 1 kHz at 90 dB SPL input level at the microphone. + </li> + </ul> + <p> + If device impelementations declare <code>android.hardware.microphone</code> and noise suppression (reduction) technologies tuned for speech recognition, they: + </p> + <ul> + <li>[C-2-1] MUST allow this audio affect to be controllable with the <code>android.media.audiofx.NoiseSuppressor</code> API. + </li> + <li>[C-2-2] MUST uniquely identfiy each noise suppression technology implementation via the <code>AudioEffect.Descriptor.uuid</code> field. + </li> + </ul> + <h4 id="5_4_3_capture_for_rerouting_of_playback"> + 5.4.3. Capture for Rerouting of Playback + </h4> + <p> + The <code>android.media.MediaRecorder.AudioSource</code> class includes the <code>REMOTE_SUBMIX</code> audio source. + </p> + <p> + If device implementations declare both <code>android.hardware.audio.output</code> and <code>android.hardware.microphone</code>, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST properly implement the <code>REMOTE_SUBMIX</code> audio source so that when an application uses the <code>android.media.AudioRecord</code> API to record from this audio source, it captures a mix of all audio streams except for the following: + </p> + <ul> + <li> + <code>AudioManager.STREAM_RING</code> + </li> + <li> + <code>AudioManager.STREAM_ALARM</code> + </li> + <li> + <code>AudioManager.STREAM_NOTIFICATION</code> + </li> + </ul> + </li> + </ul> + <h3 id="5_5_audio_playback"> + 5.5. Audio Playback + </h3> + <p> + Android includes the support to allow apps to playback audio through the audio output peripheral as defined in section 7.8.2. + </p> + <h4 id="5_5_1_raw_audio_playback"> + 5.5.1. Raw Audio Playback + </h4> + <p> + If device implementations declare <code>android.hardware.audio.output</code>, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST allow playback of raw audio content with the following characteristics: + </p> + <ul> + <li> + <strong>Format</strong>: Linear PCM, 16-bit + </li> + <li> + <strong>Sampling rates</strong>: 8000, 11025, 16000, 22050, 32000, 44100 + </li> + <li> + <strong>Channels</strong>: Mono, Stereo + </li> + </ul> + </li> + <li> + <p> + SHOULD allow playback of raw audio content with the following characteristics: + </p> + <ul> + <li> + <strong>Sampling rates</strong>: 24000, 48000 + </li> + </ul> + </li> + </ul> + <h4 id="5_5_2_audio_effects"> + 5.5.2. Audio Effects + </h4> + <p> + Android provides an <a href="http://developer.android.com/reference/android/media/audiofx/AudioEffect.html">API for audio effects</a> for device implementations. + </p> + <p> + If device implementations declare the feature <code>android.hardware.audio.output</code>, they: + </p> + <ul> + <li>[C-1-1] MUST support the <code>EFFECT_TYPE_EQUALIZER</code> and <code>EFFECT_TYPE_LOUDNESS_ENHANCER</code> implementations controllable through the AudioEffect subclasses <code>Equalizer</code>, <code>LoudnessEnhancer</code>. + </li> + <li>[C-1-2] MUST support the visualizer API implementation, controllable through the <code>Visualizer</code> class. + </li> + <li>SHOULD support the <code>EFFECT_TYPE_BASS_BOOST</code>, <code>EFFECT_TYPE_ENV_REVERB</code>, <code>EFFECT_TYPE_PRESET_REVERB</code>, and <code>EFFECT_TYPE_VIRTUALIZER</code> implementations controllable through the <code>AudioEffect</code> sub-classes <code>BassBoost</code>, <code>EnvironmentalReverb</code>, <code>PresetReverb</code>, and <code>Virtualizer</code>. + </li> + </ul> + <h4 id="5_5_3_audio_output_volume"> + 5.5.3. Audio Output Volume + </h4> + <p> + Automotive device implementations: + </p> + <ul> + <li>SHOULD allow adjusting audio volume separately per each audio stream using the content type or usage as defined by <a href="" title="http://developer.android.com/reference/android/media/AudioAttributes.html">AudioAttributes</a> and car audio usage as publicly defined in <code>android.car.CarAudioManager</code>. + </li> + </ul> + <h3 id="5_6_audio_latency"> + 5.6. Audio Latency + </h3> + <p> + Audio latency is the time delay as an audio signal passes through a system. Many classes of applications rely on short latencies, to achieve real-time sound effects. + </p> + <p> + For the purposes of this section, use the following definitions: + </p> + <ul> + <li> + <strong>output latency</strong>. The interval between when an application writes a frame of PCM-coded data and when the corresponding sound is presented to environment at an on-device transducer or signal leaves the device via a port and can be observed externally. + </li> + <li> + <strong>cold output latency</strong>. The output latency for the first frame, when the audio output system has been idle and powered down prior to the request. + </li> + <li> + <strong>continuous output latency</strong>. The output latency for subsequent frames, after the device is playing audio. + </li> + <li> + <strong>input latency</strong>. The interval between when a sound is presented by environment to device at an on-device transducer or signal enters the device via a port and when an application reads the corresponding frame of PCM-coded data. + </li> + <li> + <strong>lost input</strong>. The initial portion of an input signal that is unusable or unavailable. + </li> + <li> + <strong>cold input latency</strong>. The sum of lost input time and the input latency for the first frame, when the audio input system has been idle and powered down prior to the request. + </li> + <li> + <strong>continuous input latency</strong>. The input latency for subsequent frames, while the device is capturing audio. + </li> + <li> + <strong>cold output jitter</strong>. The variability among separate measurements of cold output latency values. + </li> + <li> + <strong>cold input jitter</strong>. The variability among separate measurements of cold input latency values. + </li> + <li> + <strong>continuous round-trip latency</strong>. The sum of continuous input latency plus continuous output latency plus one buffer period. The buffer period allows time for the app to process the signal and time for the app to mitigate phase difference between input and output streams. + </li> + <li> + <strong>OpenSL ES PCM buffer queue API</strong>. The set of PCM-related <a href="https://developer.android.com/ndk/guides/audio/opensl/index.html">OpenSL ES</a> APIs within <a href="https://developer.android.com/ndk/index.html">Android NDK</a>. + </li> + <li> + <strong>AAudio native audio API</strong>. The set of <a href="https://developer.android.com/ndk/guides/audio/aaudio/aaudio.html">AAudio</a> APIs within <a href="https://developer.android.com/ndk/index.html">Android NDK</a>. + </li> + </ul> + <p> + If device implementations declare <code>android.hardware.audio.output</code> they are STRONGLY RECOMMENDED to meet or exceed the following requirements: + </p> + <ul> + <li>[SR] Cold output latency of 100 milliseconds or less + </li> + <li>[SR] Continuous output latency of 45 milliseconds or less + </li> + <li>[SR] Minimize the cold output jitter + </li> + </ul> + <p> + If device implementations meet the above requirements after any initial calibration when using the OpenSL ES PCM buffer queue API, for continuous output latency and cold output latency over at least one supported audio output device, they are: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to report low latency audio by declaring <code>android.hardware.audio.low_latency</code> feature flag. + </li> + <li>[SR] STRONGLY RECOMMENDED to also meet the requirements for low-latency audio via the AAudio API. + </li> + </ul> + <p> + If device implementations do not meet the requirements for low-latency audio via the OpenSL ES PCM buffer queue API, they: + </p> + <ul> + <li>[C-1-1] MUST NOT report support for low-latency audio. + </li> + </ul> + <p> + If device implementations include <code>android.hardware.microphone</code>, they are STRONGLY RECOMMENDED to meet these input audio requirements: + </p> + <ul> + <li>[SR] Cold input latency of 100 milliseconds or less + </li> + <li>[SR] Continuous input latency of 30 milliseconds or less + </li> + <li>[SR] Continuous round-trip latency of 50 milliseconds or less + </li> + <li>[SR] Minimize the cold input jitter + </li> + </ul> + <h3 id="5_7_network_protocols"> + 5.7. Network Protocols + </h3> + <p> + Device implementations MUST support the <a href="http://developer.android.com/guide/appendix/media-formats.html">media network protocols</a> for audio and video playback as specified in the Android SDK documentation. + </p> + <p> + If device implementations include an audio or a video decoder, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST support all required codecs and container formats in <a href="#5_1_media_codecs">section 5.1</a> over HTTP(S). + </p> + </li> + <li> + <p> + [C-1-2] MUST support the media segment formats shown in the Media Segmant Formats table below over <a href="http://tools.ietf.org/html/draft-pantos-http-live-streaming-07">HTTP Live Streaming draft protocol, Version 7</a>. + </p> + </li> + <li> + <p> + [C-1-3] MUST support the following RTP audio video profile and related codecs in the RTSP table below. For exceptions please see the table footnotes in <a href="#5_1_media_codecs">section 5.1</a>. + </p> + </li> + </ul> + <p> + Media Segment Formats + </p> + <table> + <tr> + <th> + Segment formats + </th> + <th> + Reference(s) + </th> + <th> + Required codec support + </th> + </tr> + <tr id="mp2t"> + <td> + MPEG-2 Transport Stream + </td> + <td> + <a href="http://www.iso.org/iso/catalogue_detail?csnumber=44169">ISO 13818</a> + </td> + <td> + Video codecs: + <ul> + <li class="table_list">H264 AVC + </li> + <li class="table_list">MPEG-4 SP + </li> + <li class="table_list">MPEG-2 + </li> + </ul>See <a href="#5_1_3_video_codecs">section 5.1.3</a> for details on H264 AVC, MPEG2-4 SP,<br /> + and MPEG-2. + <p> + Audio codecs: + </p> + <ul> + <li class="table_list">AAC + </li> + </ul>See <a href="#5_1_1_audio_codecs">section 5.1.1</a> for details on AAC and its variants. + </td> + </tr> + <tr> + <td> + AAC with ADTS framing and ID3 tags + </td> + <td> + <a href="http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=43345">ISO 13818-7</a> + </td> + <td> + See <a href="#5_1_1_audio_codecs">section 5.1.1</a> for details on AAC and its variants + </td> + </tr> + <tr> + <td> + WebVTT + </td> + <td> + <a href="http://dev.w3.org/html5/webvtt/">WebVTT</a> + </td> + <td></td> + </tr> + </table> + <p> + RTSP (RTP, SDP) + </p> + <table> + <tr> + <th> + Profile name + </th> + <th> + Reference(s) + </th> + <th> + Required codec support + </th> + </tr> + <tr> + <td> + H264 AVC + </td> + <td> + <a href="https://tools.ietf.org/html/rfc6184">RFC 6184</a> + </td> + <td> + See <a href="#5_1_3_video_codecs">section 5.1.3</a> for details on H264 AVC + </td> + </tr> + <tr> + <td> + MP4A-LATM + </td> + <td> + <a href="https://tools.ietf.org/html/rfc6416">RFC 6416</a> + </td> + <td> + See <a href="#5_1_1_audio_codecs">section 5.1.1</a> for details on AAC and its variants + </td> + </tr> + <tr> + <td> + H263-1998 + </td> + <td> + <a href="https://tools.ietf.org/html/rfc3551">RFC 3551</a><br /> + <a href="https://tools.ietf.org/html/rfc4629">RFC 4629</a><br /> + <a href="https://tools.ietf.org/html/rfc2190">RFC 2190</a> + </td> + <td> + See <a href="#5_1_3_video_codecs">section 5.1.3</a> for details on H263 + </td> + </tr> + <tr> + <td> + H263-2000 + </td> + <td> + <a href="https://tools.ietf.org/html/rfc4629">RFC 4629</a> + </td> + <td> + See <a href="#5_1_3_video_codecs">section 5.1.3</a> for details on H263 + </td> + </tr> + <tr> + <td> + AMR + </td> + <td> + <a href="https://tools.ietf.org/html/rfc4867">RFC 4867</a> + </td> + <td> + See <a href="#5_1_1_audio_codecs">section 5.1.1</a> for details on AMR-NB + </td> + </tr> + <tr> + <td> + AMR-WB + </td> + <td> + <a href="https://tools.ietf.org/html/rfc4867">RFC 4867</a> + </td> + <td> + See <a href="#5_1_1_audio_codecs">section 5.1.1</a> for details on AMR-WB + </td> + </tr> + <tr> + <td> + MP4V-ES + </td> + <td> + <a href="https://tools.ietf.org/html/rfc6416">RFC 6416</a> + </td> + <td> + See <a href="#5_1_3_video_codecs">section 5.1.3</a> for details on MPEG-4 SP + </td> + </tr> + <tr> + <td> + mpeg4-generic + </td> + <td> + <a href="https://tools.ietf.org/html/rfc3640">RFC 3640</a> + </td> + <td> + See <a href="#5_1_1_audio_codecs">section 5.1.1</a> for details on AAC and its variants + </td> + </tr> + <tr> + <td> + MP2T + </td> + <td> + <a href="https://tools.ietf.org/html/rfc2250">RFC 2250</a> + </td> + <td> + See <a href="#mp2t">MPEG-2 Transport Stream</a> underneath HTTP Live Streaming for details + </td> + </tr> + </table> + <h3 id="5_8_secure_media"> + 5.8. Secure Media + </h3> + <p> + If device implementations support secure video output and are capable of supporting secure surfaces, they: + </p> + <ul> + <li>[C-1-1] MUST declare support for <code>Display.FLAG_SECURE</code>. + </li> + </ul> + <p> + If device implementations declare support for <code>Display.FLAG_SECURE</code> and support wireless display protocol, they: + </p> + <ul> + <li>[C-2-1] MUST secure the link with a cryptographically strong mechanism such as HDCP 2.x or higher for the displays connected through wireless protocols such as Miracast. + </li> + </ul> + <p> + If device implementations declare support for <code>Display.FLAG_SECURE</code> and support wired external display, they: + </p> + <ul> + <li>[C-3-1] MUST support HDCP 1.2 or higher for all wired external displays. + </li> + </ul> + <h3 id="5_9_musical_instrument_digital_interface_(midi)"> + 5.9. Musical Instrument Digital Interface (MIDI) + </h3> + <p> + If device implementations report support for feature <code>android.software.midi</code> via the <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html"><code>android.content.pm.PackageManager</code></a> class, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST support MIDI over <em>all</em> MIDI-capable hardware transports for which they provide generic non-MIDI connectivity, where such transports are: + </p> + <ul> + <li>USB host mode, <a href="#7_7_USB">section 7.7</a> + </li> + <li>USB peripheral mode, <a href="#7_7_USB">section 7.7</a> + </li> + <li>MIDI over Bluetooth LE acting in central role, <a href="#7_4_3_bluetooth">section 7.4.3</a> + </li> + </ul> + </li> + <li> + <p> + [C-1-2] MUST support the inter-app MIDI software transport (virtual MIDI devices) + </p> + </li> + </ul> + <h3 id="5_10_professional_audio"> + 5.10. Professional Audio + </h3> + <p> + If device implementations report support for feature <code>android.hardware.audio.pro</code> via the <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">android.content.pm.PackageManager</a> class, they: + </p> + <ul> + <li>[C-1-1] MUST report support for feature <code>android.hardware.audio.low_latency</code>. + </li> + <li>[C-1-2] MUST have the continuous round-trip audio latency, as defined in <a href="#5_6_audio_latency">section 5.6 Audio Latency</a>, MUST be 20 milliseconds or less and SHOULD be 10 milliseconds or less over at least one supported path. + </li> + <li>[C-1-3] MUST include a USB port(s) supporting USB host mode and USB peripheral mode. + </li> + <li>[C-1-4] MUST report support for feature <code>android.software.midi</code>. + </li> + <li>[C-1-5] MUST meet latencies and USB audio requirements using the <a href="https://developer.android.com/ndk/guides/audio/opensl-for-android.html">OpenSL ES</a> PCM buffer queue API. + </li> + <li>[SR] Are STRONGLY RECOMMENDED to provide a consistent level of CPU performance while audio is active and CPU load is varying. This should be tested using <a href="https://github.com/googlesamples/android-audio-high-performance/tree/master/SimpleSynth">SimpleSynth</a> commit <a href="https://github.com/googlesamples/android-audio-high-performance/commit/1bd6391f8ba9512f9f8798e979bc55b899f856d1">1bd6391</a>. The SimpleSynth app needs to be run with below parameters and achieve zero underruns after 10 minutes: + <ul> + <li>Work cycles: 200,000 + </li> + <li>Variable load: ON (this will switch between 100% and 10% of the work cycles value every 2 seconds and is designed to test CPU governor behavior) + </li> + <li>Stabilized load: OFF + </li> + </ul> + </li> + <li>SHOULD minimize audio clock inaccuracy and drift relative to standard time. + </li> + <li>SHOULD minimize audio clock drift relative to the CPU <code>CLOCK_MONOTONIC</code> when both are active. + </li> + <li>SHOULD minimize audio latency over on-device transducers. + </li> + <li>SHOULD minimize audio latency over USB digital audio. + </li> + <li>SHOULD document audio latency measurements over all paths. + </li> + <li>SHOULD minimize jitter in audio buffer completion callback entry times, as this affects usable percentage of full CPU bandwidth by the callback. + </li> + <li>SHOULD provide zero audio underruns (output) or overruns (input) under normal use at reported latency. + </li> + <li>SHOULD provide zero inter-channel latency difference. + </li> + <li>SHOULD minimize MIDI mean latency over all transports. + </li> + <li>SHOULD minimize MIDI latency variability under load (jitter) over all transports. + </li> + <li>SHOULD provide accurate MIDI timestamps over all transports. + </li> + <li>SHOULD minimize audio signal noise over on-device transducers, including the period immediately after cold start. + </li> + <li>SHOULD provide zero audio clock difference between the input and output sides of corresponding end-points, when both are active. Examples of corresponding end-points include the on-device microphone and speaker, or the audio jack input and output. + </li> + <li>SHOULD handle audio buffer completion callbacks for the input and output sides of corresponding end-points on the same thread when both are active, and enter the output callback immediately after the return from the input callback. Or if it is not feasible to handle the callbacks on the same thread, then enter the output callback shortly after entering the input callback to permit the application to have a consistent timing of the input and output sides. + </li> + <li>SHOULD minimize the phase difference between HAL audio buffering for the input and output sides of corresponding end-points. + </li> + <li>SHOULD minimize touch latency. + </li> + <li>SHOULD minimize touch latency variability under load (jitter). + </li> + </ul> + <p> + If device implementations meet all of the above requirements, they: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to report support for feature <code>android.hardware.audio.pro</code> via the <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html"><code>android.content.pm.PackageManager</code></a> class. + </li> + </ul> + <p> + If device implementations meet the requirements via the OpenSL ES PCM buffer queue API, they: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to also meet the same requirements via the <a href="https://developer.android.com/ndk/guides/audio/aaudio/aaudio.html">AAudio</a> API. + </li> + </ul> + <p> + If device implementations include a 4 conductor 3.5mm audio jack, they: + </p> + <ul> + <li>[C-2-1] MUST have the continuous round-trip audio latency to be 20 milliseconds or less over the audio jack path. + </li> + <li>[SR] STRONGLY RECOMMENDED to comply with section <a href="https://source.android.com/devices/accessories/headset/jack-headset-spec">Mobile device (jack) specifications</a> of the <a href="https://source.android.com/devices/accessories/headset/plug-headset-spec">Wired Audio Headset Specification (v1.1)</a>. + </li> + <li>The continuous round-trip audio latency SHOULD be 10 milliseconds or less over the audio jack path. + </li> + </ul> + <p> + If device implementations omit a 4 conductor 3.5mm audio jack and include a USB port(s) supporting USB host mode, they: + </p> + <ul> + <li>[C-3-1] MUST implement the USB audio class. + </li> + <li>[C-3-2] MUST have a continuous round-trip audio latency of 20 milliseconds or less over the USB host mode port using USB audio class. + </li> + <li>The continuous round-trip audio latency SHOULD be 10 milliseconds or less over the USB host mode port using USB audio class. + </li> + </ul> + <p> + If device implementations include an HDMI port, they: + </p> + <ul> + <li>[C-4-1] MUST support output in stereo and eight channels at 20-bit or 24-bit depth and 192 kHz without bit-depth loss or resampling. + </li> + </ul> + <h3 id="5_11_capture_for_unprocessed"> + 5.11. Capture for Unprocessed + </h3> + <p> + Android includes support for recording of unprocessed audio via the <code>android.media.MediaRecorder.AudioSource.UNPROCESSED</code> audio source. In OpenSL ES, it can be accessed with the record preset <code>SL_ANDROID_RECORDING_PRESET_UNPROCESSED</code>. + </p> + <p> + If device implementations intent to support unprocessed audio source and make it available to third-party apps, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST report the support through the <code>android.media.AudioManager</code> property <a href="http://developer.android.com/reference/android/media/AudioManager.html#PROPERTY_SUPPORT_AUDIO_SOURCE_UNPROCESSED">PROPERTY_SUPPORT_AUDIO_SOURCE_UNPROCESSED</a>. + </p> + </li> + <li> + <p> + [C-1-2] MUST exhibit approximately flat amplitude-versus-frequency characteristics in the mid-frequency range: specifically ±10dB from 100 Hz to 7000 Hz for each and every microphone used to record the unprocessed audio source. + </p> + </li> + <li> + <p> + [C-1-3] MUST exhibit amplitude levels in the low frequency range: specifically from ±20 dB from 5 Hz to 100 Hz compared to the mid-frequency range for each and every microphone used to record the unprocessed audio source. + </p> + </li> + <li> + <p> + [C-1-4] MUST exhibit amplitude levels in the high frequency range: specifically from ±30 dB from 7000 Hz to 22 KHz compared to the mid-frequency range for each and every microphone used to record the unprocessed audio source. + </p> + </li> + <li> + <p> + [C-1-5] MUST set audio input sensitivity such that a 1000 Hz sinusoidal tone source played at 94 dB Sound Pressure Level (SPL) yields a response with RMS of 520 for 16 bit-samples (or -36 dB Full Scale for floating point/double precision samples) for each and every microphone used to record the unprocessed audio source. + </p> + </li> + <li> + <p> + [C-1-6] MUST have a signal-to-noise ratio (SNR) at 60 dB or higher for each and every microphone used to record the unprocessed audio source. (whereas the SNR is measured as the difference between 94 dB SPL and equivalent SPL of self noise, A-weighted). + </p> + </li> + <li> + <p> + [C-1-7] MUST have a total harmonic distortion (THD) less than be less than 1% for 1 kHZ at 90 dB SPL input level at each and every microphone used to record the unprocessed audio source. + </p> + </li> + <li> + <p> + MUST not have any other signal processing (e.g. Automatic Gain Control, High Pass Filter, or Echo cancellation) in the path other than a level multiplier to bring the level to desired range. In other words: + </p> + </li> + <li>[C-1-8] If any signal processing is present in the architecture for any reason, it MUST be disabled and effectively introduce zero delay or extra latency to the signal path. + </li> + <li>[C-1-9] The level multiplier, while allowed to be on the path, MUST NOT introduce delay or latency to the signal path. + </li> + </ul> + <p> + All SPL measurements are made directly next to the microphone under test. For multiple microphone configurations, these requirements apply to each microphone. + </p> + <p> + If device implementations declare <code>android.hardware.microphone</code> but do not support unprocessed audio source, they: + </p> + <ul> + <li>[C-2-1] MUST return <code>null</code> for the <code>AudioManager.getProperty(PROPERTY_SUPPORT_AUDIO_SOURCE_UNPROCESSED)</code> API method, to properly indicate the lack of support. + </li> + <li>[SR] are still STRONGLY RECOMMENDED to satisfy as many of the requirements for the signal path for the unprocessed recording source. + </li> + </ul> + <h2 id="6_developer_tools_and_options_compatibility"> + 6. Developer Tools and Options Compatibility + </h2> + <h3 id="6_1_developer_tools"> + 6.1. Developer Tools + </h3> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST support the Android Developer Tools provided in the Android SDK. + </li> + <li> + <p> + <a href="http://developer.android.com/tools/help/adb.html"><strong>Android Debug Bridge (adb)</strong></a> + </p> + <ul> + <li>[C-0-2] MUST support all adb functions as documented in the Android SDK including <a href="https://source.android.com/devices/input/diagnostics.html">dumpsys</a>. + </li> + <li>[C-0-3] MUST NOT alter the format or the contents of device system events (batterystats , diskstats, fingerprint, graphicsstats, netstats, notification, procstats) logged via dumpsys. + </li> + <li>[C-0-4] MUST have the device-side adb daemon be inactive by default and there MUST be a user-accessible mechanism to turn on the Android Debug Bridge. + </li> + <li>[C-0-5] MUST support secure adb. Android includes support for secure adb. Secure adb enables adb on known authenticated hosts. + </li> + <li> + <p> + [C-0-6] MUST provide a mechanism allowing adb to be connected from a host machine. For example: + </p> + <ul> + <li>Device implementations without a USB port supporting peripheral mode MUST implement adb via local-area network (such as Ethernet or Wi-Fi). + </li> + <li>MUST provide drivers for Windows 7, 9 and 10, allowing developers to connect to the device using the adb protocol. + </li> + </ul> + </li> + </ul> + </li> + <li> + <p> + <a href="http://developer.android.com/tools/debugging/ddms.html"><strong>Dalvik Debug Monitor Service (ddms)</strong></a> + </p> + <ul> + <li>[C-0-7] MUST support all ddms features as documented in the Android SDK. As ddms uses adb, support for ddms SHOULD be inactive by default, but MUST be supported whenever the user has activated the Android Debug Bridge, as above. + </li> + </ul> + </li> + <li> + <a href="http://developer.android.com/tools/help/monkey.html"><strong>Monkey</strong></a> + <ul> + <li>[C-0-8] MUST include the Monkey framework and make it available for applications to use. + </li> + </ul> + </li> + <li> + <a href="http://developer.android.com/tools/help/systrace.html"><strong>SysTrace</strong></a> + <ul> + <li>[C-0-9] MUST support systrace tool as documented in the Android SDK. Systrace must be inactive by default and there MUST be a user-accessible mechanism to turn on Systrace. + </li> + </ul> + </li> + </ul> + <h3 id="6_2_developer_options"> + 6.2. Developer Options + </h3> + <p> + Android includes support for developers to configure application development-related settings. + </p> + <p> + Device implementations MUST provide a consistent experience for Developer Options, they: + </p> + <ul> + <li>[C-0-1] MUST honor the <a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_APPLICATION_DEVELOPMENT_SETTINGS">android.settings.APPLICATION_DEVELOPMENT_SETTINGS</a> intent to show application development-related settings. The upstream Android implementation hides the Developer Options menu by default and enables users to launch Developer Options after pressing seven (7) times on the <strong>Settings</strong> > <strong>About Device</strong> > <strong>Build Number</strong> menu item. + </li> + <li>[C-0-2] MUST hide Developer Options by default and MUST provide a mechanism to enable Developer Options without the need for any special whitelisting. + </li> + <li>MAY temporarily limit access to the Developer Options menu, by visually hiding or disabling the menu, to prevent distraction for scenarios where the safety of the user is of concern. + </li> + </ul> + <h2 id="7_hardware_compatibility"> + 7. Hardware Compatibility + </h2> + <p> + If a device includes a particular hardware component that has a corresponding API for third-party developers: + </p> + <ul> + <li>[C-0-1] The device implementation MUST implement that API as described in the Android SDK documentation. + </li> + </ul> + <p> + If an API in the SDK interacts with a hardware component that is stated to be optional and the device implementation does not possess that component: + </p> + <ul> + <li>[C-0-2] Complete class definitions (as documented by the SDK) for the component APIs MUST still be presented. + </li> + <li>[C-0-3] The API’s behaviors MUST be implemented as no-ops in some reasonable fashion. + </li> + <li>[C-0-4] API methods MUST return null values where permitted by the SDK documentation. + </li> + <li>[C-0-5] API methods MUST return no-op implementations of classes where null values are not permitted by the SDK documentation. + </li> + <li>[C-0-6] API methods MUST NOT throw exceptions not documented by the SDK documentation. + </li> + <li>[C-0-7] Device implementations MUST consistently report accurate hardware configuration information via the <code>getSystemAvailableFeatures()</code> and <code>hasSystemFeature(String)</code> methods on the <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">android.content.pm.PackageManager</a> class for the same build fingerprint. + </li> + </ul> + <p> + A typical example of a scenario where these requirements apply is the telephony API: Even on non-phone devices, these APIs must be implemented as reasonable no-ops. + </p> + <h3 id="7_1_display_and_graphics"> + 7.1. Display and Graphics + </h3> + <p> + Android includes facilities that automatically adjust application assets and UI layouts appropriately for the device to ensure that third-party applications run well on a <a href="http://developer.android.com/guide/practices/screens_support.html">variety of hardware configurations</a>. Devices MUST properly implement these APIs and behaviors, as detailed in this section. + </p> + <p> + The units referenced by the requirements in this section are defined as follows: + </p> + <ul> + <li> + <strong>physical diagonal size</strong>. The distance in inches between two opposing corners of the illuminated portion of the display. + </li> + <li> + <strong>dots per inch (dpi)</strong>. The number of pixels encompassed by a linear horizontal or vertical span of 1”. Where dpi values are listed, both horizontal and vertical dpi must fall within the range. + </li> + <li> + <strong>aspect ratio</strong>. The ratio of the pixels of the longer dimension to the shorter dimension of the screen. For example, a display of 480x854 pixels would be 854/480 = 1.779, or roughly “16:9”. + </li> + <li> + <strong>density-independent pixel (dp)</strong>. The virtual pixel unit normalized to a 160 dpi screen, calculated as: pixels = dps * (density/160). + </li> + </ul> + <h4 id="7_1_1_screen_configuration"> + 7.1.1. Screen Configuration + </h4> + <h5 id="7_1_1_1_screen_size"> + 7.1.1.1. Screen Size + </h5> + <p> + The Android UI framework supports a variety of different logical screen layout sizes, and allows applications to query the current configuration's screen layout size via <code>Configuration.screenLayout</code> with the <code>SCREENLAYOUT_SIZE_MASK</code> and <code>Configuration.smallestScreenWidthDp</code>. + </p> + <ul> + <li> + <p> + [C-0-1] Device implementations MUST report the correct layout size for the <code>Configuration.screenLayout</code> as defined in the Android SDK documentation. Specifically, device implementations MUST report the correct logical density-independent pixel (dp) screen dimensions as below: + </p> + <ul> + <li>Devices with the <code>Configuration.uiMode</code> set as any value other than UI_MODE_TYPE_WATCH, and reporting a <code>small</code> size for the <code>Configuration.screenLayout</code>, MUST have at least 426 dp x 320 dp. + </li> + <li>Devices reporting a <code>normal</code> size for the <code>Configuration.screenLayout</code>, MUST have at least 480 dp x 320 dp. + </li> + <li>Devices reporting a <code>large</code> size for the <code>Configuration.screenLayout</code>, MUST have at least 640 dp x 480 dp. + </li> + <li>Devices reporting a <code>xlarge</code> size for the <code>Configuration.screenLayout</code>, MUST have at least 960 dp x 720 dp. + </li> + </ul> + </li> + <li> + <p> + [C-0-2] Device implementations MUST correctly honor applications' stated support for screen sizes through the <a href="https://developer.android.com/guide/topics/manifest/supports-screens-element.html"><<code>supports-screens</code>></a> attribute in the AndroidManifest.xml, as described in the Android SDK documentation. + </p> + </li> + </ul> + <h5 id="7_1_1_2_screen_aspect_ratio"> + 7.1.1.2. Screen Aspect Ratio + </h5> + <p> + While there is no restriction to the screen aspect ratio value of the physical screen display, the screen aspect ratio of the logical display that third-party apps are rendered within, as can be derived from the height and width values reported through the <a href="https://developer.android.com/reference/android/view/Display.html"><code>view.Display</code></a> APIs and <a href="https://developer.android.com/reference/android/content/res/Configuration.html">Configuration</a> API, MUST meet the following requirements: + </p> + <ul> + <li> + <p> + [C-0-1] Device implementations with the <code>Configuration.uiMode</code> set as <code>UI_MODE_TYPE_NORMAL</code> MUST have an aspect ratio value between 1.3333 (4:3) and 1.86 (roughly 16:9), unless the app can be deemed as ready to be stretched longer by meeting one of the following conditions: + </p> + <ul> + <li>The app has declared that it supports a larger screen aspect ratio through the <a href="https://developer.android.com/guide/practices/screens&lowbar;support.html#MaxAspectRatio"><code>android.max_aspect</code></a> metadata value. + </li> + <li>The app declares it is resizeable via the <a href="https://developer.android.com/guide/topics/ui/multi-window.html#configuring">android:resizeableActivity</a> attribute. + </li> + <li>The app is targeting API level 26 or higher and does not declare a <a href="https://developer.android.com/reference/android/R.attr.html#maxAspectRatio"><code>android:MaxAspectRatio</code></a> that would restrict the allowed aspect ratio. + </li> + </ul> + </li> + <li> + <p> + [C-0-2] Device implementations with the <code>Configuration.uiMode</code> set as <code>UI_MODE_TYPE_WATCH</code> MUST have an aspect ratio value set as 1.0 (1:1). + </p> + </li> + </ul> + <h5 id="7_1_1_3_screen_density"> + 7.1.1.3. Screen Density + </h5> + <p> + The Android UI framework defines a set of standard logical densities to help application developers target application resources. + </p> + <ul> + <li> + <p> + [C-0-1] By default, device implementations MUST report only one of the following logical Android framework densities through the <a href="https://developer.android.com/reference/android/util/DisplayMetrics.html#DENSITY_DEVICE_STABLE">DENSITY_DEVICE_STABLE</a> API and this value MUST NOT change at any time; however, the device MAY report a different arbitrary density according to the display configuration changes made by the user (for example, display size) set after initial boot. + </p> + <ul> + <li>120 dpi (ldpi) + </li> + <li>160 dpi (mdpi) + </li> + <li>213 dpi (tvdpi) + </li> + <li>240 dpi (hdpi) + </li> + <li>260 dpi (260dpi) + </li> + <li>280 dpi (280dpi) + </li> + <li>300 dpi (300dpi) + </li> + <li>320 dpi (xhdpi) + </li> + <li>340 dpi (340dpi) + </li> + <li>360 dpi (360dpi) + </li> + <li>400 dpi (400dpi) + </li> + <li>420 dpi (420dpi) + </li> + <li>480 dpi (xxhdpi) + </li> + <li>560 dpi (560dpi) + </li> + <li>640 dpi (xxxhdpi) + </li> + </ul> + </li> + <li> + <p> + Device implementations SHOULD define the standard Android framework density that is numerically closest to the physical density of the screen, unless that logical density pushes the reported screen size below the minimum supported. If the standard Android framework density that is numerically closest to the physical density results in a screen size that is smaller than the smallest supported compatible screen size (320 dp width), device implementations SHOULD report the next lowest standard Android framework density. + </p> + </li> + </ul> + <p> + If there is an affordance to change the display size of the device: + </p> + <ul> + <li>[C-1-1] The display size MUST NOT be scaled any larger than 1.5 times the native density or produce an effective minimum screen dimension smaller than 320dp (equivalent to resource qualifier sw320dp), whichever comes first. + </li> + <li>[C-1-2] Display size MUST NOT be scaled any smaller than 0.85 times the native density. + </li> + <li>To ensure good usability and consistent font sizes, it is RECOMMENDED that the following scaling of Native Display options be provided (while complying with the limits specified above) + </li> + <li>Small: 0.85x + </li> + <li>Default: 1x (Native display scale) + </li> + <li>Large: 1.15x + </li> + <li>Larger: 1.3x + </li> + <li>Largest 1.45x + </li> + </ul> + <h4 id="7_1_2_display_metrics"> + 7.1.2. Display Metrics + </h4> + <p> + If device implementations include a screen or video output, they: + </p> + <ul> + <li>[C-1-1] MUST report correct values for all display metrics defined in the <a href="https://developer.android.com/reference/android/util/DisplayMetrics.html"><code>android.util.DisplayMetrics</code></a> API. + </li> + </ul> + <p> + If device implementations does not include an embedded screen or video output, they: + </p> + <ul> + <li>[C-2-1] MUST report reasonable values for all display metrics defined in the <a href="https://developer.android.com/reference/android/util/DisplayMetrics.html"><code>android.util.DisplayMetrics</code></a> API for the emulated default <code>view.Display</code>. + </li> + </ul> + <h4 id="7_1_3_screen_orientation"> + 7.1.3. Screen Orientation + </h4> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST report which screen orientations they support (<code>android.hardware.screen.portrait</code> and/or <code>android.hardware.screen.landscape</code>) and MUST report at least one supported orientation. For example, a device with a fixed orientation landscape screen, such as a television or laptop, SHOULD only report <code>android.hardware.screen.landscape</code>. + </li> + <li>[C-0-2] MUST report the correct value for the device’s current orientation, whenever queried via the <code>android.content.res.Configuration.orientation</code>, <code>android.view.Display.getOrientation()</code>, or other APIs. + </li> + </ul> + <p> + If device implementations support both screen orientations, they: + </p> + <ul> + <li>[C-1-1] MUST support dynamic orientation by applications to either portrait or landscape screen orientation. That is, the device must respect the application’s request for a specific screen orientation. + </li> + <li>[C-1-2] MUST NOT change the reported screen size or density when changing orientation. + </li> + <li>MAY select either portrait or landscape orientation as the default. + </li> + </ul> + <h4 id="7_1_4_2d_and_3d_graphics_acceleration"> + 7.1.4. 2D and 3D Graphics Acceleration + </h4> + <h5 id="7_1_4_1_opengl_es"> + 7.1.4.1 OpenGL ES + </h5> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST correctly identify the supported OpenGL ES versions (1.1, 2.0, 3.0, 3.1, 3.2) through the managed APIs (such as via the <code>GLES10.getString()</code> method) and the native APIs. + </li> + <li>[C-0-2] MUST include the support for all the corresponding managed APIs and native APIs for every OpenGL ES versions they identified to support. + </li> + </ul> + <p> + If device implementations include a screen or video output, they: + </p> + <ul> + <li>[C-1-1] MUST support both OpenGL ES 1.0 and 2.0, as embodied and detailed in the <a href="https://developer.android.com/guide/topics/graphics/opengl.html">Android SDK documentation</a>. + </li> + <li>[SR] are STRONGLY RECOMMENDED to support OpenGL ES 3.0. + </li> + <li>SHOULD support OpenGL ES 3.1 or 3.2. + </li> + </ul> + <p> + If device implementations support any of the OpenGL ES versions, they: + </p> + <ul> + <li>[C-2-1] MUST report via the OpenGL ES managed APIs and native APIs any other OpenGL ES extensions they have implemented, and conversely MUST NOT report extension strings that they do not support. + </li> + <li>[C-2-2] MUST support the <code>EGL_KHR_image</code>, <code>EGL_KHR_image_base</code>, <code>EGL_ANDROID_image_native_buffer</code>, <code>EGL_ANDROID_get_native_client_buffer</code>, <code>EGL_KHR_wait_sync</code>, <code>EGL_KHR_get_all_proc_addresses</code>, <code>EGL_ANDROID_presentation_time</code>, <code>EGL_KHR_swap_buffers_with_damage</code> and <code>EGL_ANDROID_recordable</code> extensions. + </li> + <li>[SR] are STRONGLY RECOMMENDED to support EGL_KHR_partial_update. + </li> + <li>SHOULD accurately report via the <code>getString()</code> method, any texture compression format that they support, which is typically vendor-specific. + </li> + </ul> + <p> + If device implementations declare support for OpenGL ES 3.0, 3.1, or 3.2, they: + </p> + <ul> + <li>[C-3-1] MUST export the corresponding function symbols for these version in addition to the OpenGL ES 2.0 function symbols in the libGLESv2.so library. + </li> + </ul> + <p> + If device implementations support OpenGL ES 3.2, they: + </p> + <ul> + <li>[C-4-1] MUST support the OpenGL ES Android Extension Pack in its entirety. + </li> + </ul> + <p> + If device implementations support the OpenGL ES <a href="https://developer.android.com/reference/android/opengl/GLES31Ext.html">Android Extension Pack</a> in its entirety, they: + </p> + <ul> + <li>[C-5-1] MUST identify the support through the <code>android.hardware.opengles.aep</code> feature flag. + </li> + </ul> + <p> + If device implementations expose support for the <code>EGL_KHR_mutable_render_buffer</code> extension, they: + </p> + <ul> + <li>[C-6-1] MUST also support the <code>EGL_ANDROID_front_buffer_auto_refresh</code> extension. + </li> + </ul> + <h5 id="7_1_4_2_vulkan"> + 7.1.4.2 Vulkan + </h5> + <p> + Android includes support for <a href="https://www.khronos.org/registry/vulkan/specs/1.0-wsi&lowbarextensions/xhtml/vkspec.html">Vulkan</a> , a low-overhead, cross-platform API for high-performance 3D graphics. + </p> + <p> + If device implementations support OpenGL ES 3.0 or 3.1, they: + </p> + <ul> + <li>[SR] Are STRONGLY RECOMMENDED to include support for Vulkan 1.0 . + </li> + </ul> + <p> + If device implementations include a screen or video output, they: + </p> + <ul> + <li>SHOULD include support for Vulkan 1.0. + </li> + </ul> + <p> + Device implementations, if including support for Vulkan 1.0: + </p> + <ul> + <li>[C-1-1] MUST report the correct integer value with the <code>android.hardware.vulkan.level</code> and <code>android.hardware.vulkan.version</code> feature flags. + </li> + <li>[C-1-2] MUST enumarate, at least one <code>VkPhysicalDevice</code> for the Vulkan native API <a href="https://www.khronos.org/registry/vulkan/specs/1.0/man/html/vkEnumeratePhysicalDevices.html"><code>vkEnumeratePhysicalDevices()</code></a> . + </li> + <li>[C-1-3] MUST fully implement the Vulkan 1.0 APIs for each enumerated <code>VkPhysicalDevice</code>. + </li> + <li>[C-1-4] MUST enumerate layers, contained in native libraries named as <code>libVkLayer*.so</code> in the application package’s native library directory, through the Vulkan native APIs <a href="https://www.khronos.org/registry/vulkan/specs/1.0/man/html/vkEnumerateInstanceLayerProperties.html"><code>vkEnumerateInstanceLayerProperties()</code></a> and <a href="https://www.khronos.org/registry/vulkan/specs/1.0/man/html/vkEnumerateDeviceLayerProperties.html"><code>vkEnumerateDeviceLayerProperties()</code></a> . + </li> + <li>[C-1-5] MUST NOT enumerate layers provided by libraries outside of the application package, or provide other ways of tracing or intercepting the Vulkan API, unless the application has the <code>android:debuggable</code> attribute set as <code>true</code>. + </li> + <li>[C-1-6] MUST report all extension strings that they do support via the Vulkan native APIs , and conversely MUST NOT report extension strings that they do not correctly support. + </li> + </ul> + <p> + Device implementations, if not including support for Vulkan 1.0: + </p> + <ul> + <li>[C-2-1] MUST NOT declare any of the Vulkan feature flags (e.g. <code>android.hardware.vulkan.level</code>, <code>android.hardware.vulkan.version</code>). + </li> + <li>[C-2-2] MUST NOT enumarate any <code>VkPhysicalDevice</code> for the Vulkan native API <code>vkEnumeratePhysicalDevices()</code>. + </li> + </ul> + <h5 id="7_1_4_3_renderscript"> + 7.1.4.3 RenderScript + </h5> + <ul> + <li>[C-0-1] Device implementations MUST support <a href="http://developer.android.com/guide/topics/renderscript/">Android RenderScript</a>, as detailed in the Android SDK documentation. + </li> + </ul> + <h5 id="7_1_4_4_2d_graphics_acceleration"> + 7.1.4.4 2D Graphics Acceleration + </h5> + <p> + Android includes a mechanism for applications to declare that they want to enable hardware acceleration for 2D graphics at the Application, Activity, Window, or View level through the use of a manifest tag <a href="http://developer.android.com/guide/topics/graphics/hardware-accel.html">android:hardwareAccelerated</a> or direct API calls. + </p> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST enable hardware acceleration by default, and MUST disable hardware acceleration if the developer so requests by setting android:hardwareAccelerated="false” or disabling hardware acceleration directly through the Android View APIs. + </li> + <li>[C-0-2] MUST exhibit behavior consistent with the Android SDK documentation on <a href="http://developer.android.com/guide/topics/graphics/hardware-accel.html">hardware acceleration</a>. + </li> + </ul> + <p> + Android includes a TextureView object that lets developers directly integrate hardware-accelerated OpenGL ES textures as rendering targets in a UI hierarchy. + </p> + <ul> + <li>[C-0-3] MUST support the TextureView API, and MUST exhibit consistent behavior with the upstream Android implementation. + </li> + </ul> + <h5 id="7_1_4_5_wide-gamut_displays"> + 7.1.4.5 Wide-gamut Displays + </h5> + <p> + If device implementations claim support for wide-gamut displays through <a href="https://developer.android.com/reference/android/view/Display.html#isWideColorGamut%28%29"><code>Display.isWideColorGamut()</code></a> , they: + </p> + <ul> + <li>[C-1-1] MUST have a color-calibrated display. + </li> + <li>[C-1-2] MUST have a display whose gamut covers the sRGB color gamut entirely in CIE 1931 xyY space. + </li> + <li>[C-1-3] MUST have a display whose gamut has an area of at least 90% of NTSC 1953 in CIE 1931 xyY space. + </li> + <li>[C-1-4] MUST support OpenGL ES 3.0, 3.1, or 3.2 and report it properly. + </li> + <li>[C-1-5] MUST advertise support for the <code>EGL_KHR_no_config_context</code>, <code>EGL_EXT_pixel_format_float</code>,<code>EGL_KHR_gl_colorspace</code>, <code>EGL_EXT_colorspace_scrgb_linear</code>, and <code>EGL_GL_colorspace_display_p3</code> extensions. + </li> + <li>[SR] Are STRONGLY RECOMMENDED to support <code>GL_EXT_sRGB</code>. + </li> + </ul> + <p> + Conversely, if device implementations do not support wide-gamut displays, they: + </p> + <ul> + <li>[C-2-1] SHOULD cover 100% or more of sRGB in CIE 1931 xyY space, although the screen color gamut is undefined. + </li> + </ul> + <h4 id="7_1_5_legacy_application_compatibility_mode"> + 7.1.5. Legacy Application Compatibility Mode + </h4> + <p> + Android specifies a “compatibility mode” in which the framework operates in a 'normal' screen size equivalent (320dp width) mode for the benefit of legacy applications not developed for old versions of Android that pre-date screen-size independence. + </p> + <h4 id="7_1_6_screen_technology"> + 7.1.6. Screen Technology + </h4> + <p> + The Android platform includes APIs that allow applications to render rich graphics to the display. Devices MUST support all of these APIs as defined by the Android SDK unless specifically allowed in this document. + </p> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST support displays capable of rendering 16-bit color graphics. + </li> + <li>SHOULD support displays capable of 24-bit color graphics. + </li> + <li>[C-0-2] MUST support displays capable of rendering animations. + </li> + <li>[C-0-3] MUST use the display technology that have a pixel aspect ratio (PAR) between 0.9 and 1.15. That is, the pixel aspect ratio MUST be near square (1.0) with a 10 ~ 15% tolerance. + </li> + </ul> + <h4 id="7_1_7_secondary_displays"> + 7.1.7. Secondary Displays + </h4> + <p> + Android includes support for secondary display to enable media sharing capabilities and developer APIs for accessing external displays. + </p> + <p> + If device implementations support an external display either via a wired, wireless, or an embedded additional display connection, they: + </p> + <ul> + <li>[C-1-1] MUST implement the <a href="https://developer.android.com/reference/android/hardware/display/DisplayManager.html"><code>DisplayManager</code></a> system service and API as described in the Android SDK documentation. + </li> + </ul> + <h3 id="7_2_input_devices"> + 7.2. Input Devices + </h3> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST include an input mechanism, such as a <a href="#7_2_4_touchScreen_input">touchscreen</a> or <a href="#7_2_2_non-touch_navigation">non-touch navigation</a>, to navigate between the UI elements. + </li> + </ul> + <h4 id="7_2_1_keyboard"> + 7.2.1. Keyboard + </h4> + <p> + If device implementations include support for third-party Input Method Editor (IME) applications, they: + </p> + <ul> + <li>[C-1-1] MUST declare the <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_INPUT_METHODS"><code>android.software.input_methods</code></a> feature flag. + </li> + <li>[C-1-2] MUST implement fully <a href="https://developer.android.com/reference/android/view/inputmethod/InputMethodManager.html"><code>Input Management Framework</code></a> + </li> + <li>[C-1-3] MUST have a preloaded software keyboard. + </li> + </ul> + <p> + Device implementations: <em>[C-0-1] MUST NOT include a hardware keyboard that does not match one of the formats specified in <a href="http://developer.android.com/reference/android/content/res/Configuration.html">android.content.res.Configuration.keyboard</a> (QWERTY or 12-key).</em> SHOULD include additional soft keyboard implementations. * MAY include a hardware keyboard. + </p> + <h4 id="7_2_2_non-touch_navigation"> + 7.2.2. Non-touch Navigation + </h4> + <p> + Android includes support for d-pad, trackball, and wheel as mechanisms for non-touch navigation. + </p> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST report the correct value for <a href="https://developer.android.com/reference/android/content/res/Configuration.html#navigation">android.content.res.Configuration.navigation</a>. + </li> + </ul> + <p> + If device implementations lack non-touch navigations, they: + </p> + <ul> + <li>[C-1-1] MUST provide a reasonable alternative user interface mechanism for the selection and editing of text, compatible with Input Management Engines. The upstream Android open source implementation includes a selection mechanism suitable for use with devices that lack non-touch navigation inputs. + </li> + </ul> + <h4 id="7_2_3_navigation_keys"> + 7.2.3. Navigation Keys + </h4> + <p> + The <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_HOME">Home</a>, <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_APP_SWITCH">Recents</a>, and <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK">Back</a> functions typically provided via an interaction with a dedicated physical button or a distinct portion of the touch screen, are essential to the Android navigation paradigm and therefore, device implementations: + </p> + <ul> + <li>[C-0-1] MUST provide a user affordance to launch installed applications that have an activity with the <code><intent-filter></code> set with <code>ACTION=MAIN</code> and <code>CATEGORY=LAUNCHER</code> or <code>CATEGORY=LEANBACK_LAUNCHER</code> for Television device implementations. The Home function SHOULD be the mechanism for this user affordance. + </li> + <li>SHOULD provide buttons for the Recents and Back function. + </li> + </ul> + <p> + If the Home, Recents, or Back functions are provided, they: + </p> + <ul> + <li>[C-1-1] MUST be accessible with a single action (e.g. tap, double-click or gesture) when any of them are accessible. + </li> + <li>[C-1-2] MUST provide a clear indication of which single action would trigger each function. Having a visible icon imprinted on the button, showing a software icon on the navigation bar portion of the screen, or walking the user through a guided step-by-step demo flow during the out-of-box setup experience are examples of such an indication. + </li> + </ul> + <p> + Device implementations: + </p> + <ul> + <li>[SR] are STRONGLY RECOMMENDED to not provide the input mechanism for the <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK">Menu function</a> as it is deprecated in favor of action bar since Android 4.0. + </li> + </ul> + <p> + If device implementations provide the Menu function, they: + </p> + <ul> + <li>[C-2-1] MUST display the action overflow button whenever the action overflow menu popup is not empty and the action bar is visible. + </li> + <li>[C-2-2] MUST NOT modify the position of the action overflow popup displayed by selecting the overflow button in the action bar, but MAY render the action overflow popup at a modified position on the screen when it is displayed by selecting the Menu function. + </li> + </ul> + <p> + If device implementations do not provide the Menu function, for backwards compatibility, they: + </p> + <ul> + <li>[C-3-1] MUST make the Menu function available to applications when <code>targetSdkVersion</code> is less than 10, either by a physical button, a software key, or gestures. This Menu function should be accessible unless hidden together with other navigation functions. + </li> + </ul> + <p> + If device implementations provide the <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_ASSIST">Assist function</a>, they: + </p> + <ul> + <li>[C-4-1] MUST make the Assist function accessible with a single action (e.g. tap, double-click or gesture) when other navigation keys are accessible. + </li> + <li>[SR] STRONGLY RECOMMENDED to use long press on HOME function as this designated interaction. + </li> + </ul> + <p> + If device implementations use a distinct portion of the screen to display the navigation keys, they: + </p> + <ul> + <li>[C-5-1] Navigation keys MUST use a distinct portion of the screen, not available to applications, and MUST NOT obscure or otherwise interfere with the portion of the screen available to applications. + </li> + <li>[C-5-2] MUST make available a portion of the display to applications that meets the requirements defined in <a href="#7_1_1_screen_configuration">section 7.1.1</a>. + </li> + <li>[C-5-3] MUST honor the flags set by the app through the <a href="https://developer.android.com/reference/android/view/View.html#setSystemUiVisibility%28int%29"><code>View.setSystemUiVisibility()</code></a> API method, so that this distinct portion of the screen (a.k.a. the navigation bar) is properly hidden away as documented in the SDK. + </li> + </ul> + <h4 id="7_2_4_touchscreen_input"> + 7.2.4. Touchscreen Input + </h4> + <p> + Android includes support for a variety of pointer input systems, such as touchscreens, touch pads, and fake touch input devices. <a href="http://source.android.com/devices/tech/input/touch-devices.html">Touchscreen-based device implementations</a> are associated with a display such that the user has the impression of directly manipulating items on screen. Since the user is directly touching the screen, the system does not require any additional affordances to indicate the objects being manipulated. + </p> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD have a pointer input system of some kind (either mouse-like or touch). + </li> + <li>SHOULD support fully independently tracked pointers. + </li> + </ul> + <p> + If device implementations include a touchscreen (single-touch or better), they: + </p> + <ul> + <li>[C-1-1] MUST report <code>TOUCHSCREEN_FINGER</code> for the <a href="https://developer.android.com/reference/android/content/res/Configuration.html#touchscreen"><code>Configuration.touchscreen</code></a> API field. + </li> + <li>[C-1-2] MUST report the <code>android.hardware.touchscreen</code> and <code>android.hardware.faketouch</code> feature flags + </li> + </ul> + <p> + If device implementations include a touchscreen that can track more than a single touch, they: + </p> + <ul> + <li>[C-2-1] MUST report the appropriate feature flags <code>android.hardware.touchscreen.multitouch</code>, <code>android.hardware.touchscreen.multitouch.distinct</code>, <code>android.hardware.touchscreen.multitouch.jazzhand</code> corresponding to the type of the specific touchscreen on the device. + </li> + </ul> + <p> + If device implementations do not include a touchscreen (and rely on a pointer device only) and meet the fake touch requirements in <a href="#7_2_5_fake_touch_input">section 7.2.5</a>, they: + </p> + <ul> + <li>[C-3-1] MUST NOT report any feature flag starting with <code>android.hardware.touchscreen</code> and MUST report only <code>android.hardware.faketouch</code>. + </li> + </ul> + <h4 id="7_2_5_fake_touch_input"> + 7.2.5. Fake Touch Input + </h4> + <p> + Fake touch interface provides a user input system that approximates a subset of touchscreen capabilities. For example, a mouse or remote control that drives an on-screen cursor approximates touch, but requires the user to first point or focus then click. Numerous input devices like the mouse, trackpad, gyro-based air mouse, gyro-pointer, joystick, and multi-touch trackpad can support fake touch interactions. Android includes the feature constant android.hardware.faketouch, which corresponds to a high-fidelity non-touch (pointer-based) input device such as a mouse or trackpad that can adequately emulate touch-based input (including basic gesture support), and indicates that the device supports an emulated subset of touchscreen functionality. + </p> + <p> + If device implementations do not include a touchscreen but include another pointer input system which they want to make available, they: + </p> + <ul> + <li>SHOULD declare support for the <code>android.hardware.faketouch</code> feature flag. + </li> + </ul> + <p> + If device implementations declare support for <code>android.hardware.faketouch</code>, they: + </p> + <ul> + <li>[C-1-1] MUST report the <a href="http://developer.android.com/reference/android/view/MotionEvent.html">absolute X and Y screen positions</a> of the pointer location and display a visual pointer on the screen. + </li> + <li>[C-1-2] MUST report touch event with the action code that specifies the state change that occurs on the pointer <a href="http://developer.android.com/reference/android/view/MotionEvent.html">going down or up on the screen</a>. + </li> + <li>[C-1-3] MUST support pointer down and up on an object on the screen, which allows users to emulate tap on an object on the screen. + </li> + <li>[C-1-4] MUST support pointer down, pointer up, pointer down then pointer up in the same place on an object on the screen within a time threshold, which allows users to <a href="http://developer.android.com/reference/android/view/MotionEvent.html">emulate double tap</a> on an object on the screen. + </li> + <li>[C-1-5] MUST support pointer down on an arbitrary point on the screen, pointer move to any other arbitrary point on the screen, followed by a pointer up, which allows users to emulate a touch drag. + </li> + <li>[C-1-6] MUST support pointer down then allow users to quickly move the object to a different position on the screen and then pointer up on the screen, which allows users to fling an object on the screen. + </li> + <li>[C-1-7] MUST report <code>TOUCHSCREEN_NOTOUCH</code> for the <a href="https://developer.android.com/reference/android/content/res/Configuration.html#touchscreen"><code>Configuration.touchscreen</code></a> API field. + </li> + </ul> + <p> + If device implementations declare support for <code>android.hardware.faketouch.multitouch.distinct</code>, they: + </p> + <ul> + <li>[C-2-1] MUST declare support for <code>android.hardware.faketouch</code>. + </li> + <li>[C-2-2] MUST support distinct tracking of two or more independent pointer inputs. + </li> + </ul> + <p> + If device implementations declare support for <code>android.hardware.faketouch.multitouch.jazzhand</code>, they: + </p> + <ul> + <li>[C-3-1] MUST declare support for <code>android.hardware.faketouch</code>. + </li> + <li>[C-3-2] MUST support distinct tracking of 5 (tracking a hand of fingers) or more pointer inputs fully independently. + </li> + </ul> + <h4 id="7_2_6_game_controller_support"> + 7.2.6. Game Controller Support + </h4> + <h5 id="7_2_6_1_button_mappings"> + 7.2.6.1. Button Mappings + </h5> + <p> + If device implementations declare the <code>android.hardware.gamepad</code> feature flag, they: + </p> + <ul> + <li>[C-1-1] MUST have embed a controller or ship with a separate controller in the box, that would provide means to input all the events listed in the below tables. + </li> + <li>[C-1-2] MUST be capable to map HID events to it's associated Android <code>view.InputEvent</code> constants as listed in the below tables. The upstream Android implementation includes implementation for game controllers that satisfies this requirement. + </li> + </ul> + <table> + <tr> + <th> + Button + </th> + <th> + HID Usage<sup>2</sup> + </th> + <th> + Android Button + </th> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_A">A</a><sup>1</sup> + </td> + <td> + 0x09 0x0001 + </td> + <td> + KEYCODE_BUTTON_A (96) + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_B">B</a><sup>1</sup> + </td> + <td> + 0x09 0x0002 + </td> + <td> + KEYCODE_BUTTON_B (97) + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_X">X</a><sup>1</sup> + </td> + <td> + 0x09 0x0004 + </td> + <td> + KEYCODE_BUTTON_X (99) + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_Y">Y</a><sup>1</sup> + </td> + <td> + 0x09 0x0005 + </td> + <td> + KEYCODE_BUTTON_Y (100) + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_DPAD_UP">D-pad up</a><sup>1</sup><br /> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_DPAD_DOWN">D-pad down</a><sup>1</sup> + </td> + <td> + 0x01 0x0039<sup>3</sup> + </td> + <td> + <a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_HAT_Y">AXIS_HAT_Y</a><sup>4</sup> + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_DPAD_LEFT">D-pad left</a>1<br /> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_DPAD_RIGHT">D-pad right</a><sup>1</sup> + </td> + <td> + 0x01 0x0039<sup>3</sup> + </td> + <td> + <a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_HAT_X">AXIS_HAT_X</a><sup>4</sup> + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_L1">Left shoulder button</a><sup>1</sup> + </td> + <td> + 0x09 0x0007 + </td> + <td> + KEYCODE_BUTTON_L1 (102) + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_R1">Right shoulder button</a><sup>1</sup> + </td> + <td> + 0x09 0x0008 + </td> + <td> + KEYCODE_BUTTON_R1 (103) + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_THUMBL">Left stick click</a><sup>1</sup> + </td> + <td> + 0x09 0x000E + </td> + <td> + KEYCODE_BUTTON_THUMBL (106) + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BUTTON_THUMBR">Right stick click</a><sup>1</sup> + </td> + <td> + 0x09 0x000F + </td> + <td> + KEYCODE_BUTTON_THUMBR (107) + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_HOME">Home</a><sup>1</sup> + </td> + <td> + 0x0c 0x0223 + </td> + <td> + KEYCODE_HOME (3) + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK">Back</a><sup>1</sup> + </td> + <td> + 0x0c 0x0224 + </td> + <td> + KEYCODE_BACK (4) + </td> + </tr> + </table> + <p class="table_footnote"> + 1 <a href="http://developer.android.com/reference/android/view/KeyEvent.html">KeyEvent</a> + </p> + <p class="table_footnote"> + 2 The above HID usages must be declared within a Game pad CA (0x01 0x0005). + </p> + <p class="table_footnote"> + 3 This usage must have a Logical Minimum of 0, a Logical Maximum of 7, a Physical Minimum of 0, a Physical Maximum of 315, Units in Degrees, and a Report Size of 4. The logical value is defined to be the clockwise rotation away from the vertical axis; for example, a logical value of 0 represents no rotation and the up button being pressed, while a logical value of 1 represents a rotation of 45 degrees and both the up and left keys being pressed. + </p> + <p class="table_footnote"> + 4 <a href="http://developer.android.com/reference/android/view/MotionEvent.html">MotionEvent</a> + </p> + <table> + <tr> + <th> + Analog Controls<sup>1</sup> + </th> + <th> + HID Usage + </th> + <th> + Android Button + </th> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_LTRIGGER">Left Trigger</a> + </td> + <td> + 0x02 0x00C5 + </td> + <td> + AXIS_LTRIGGER + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_THROTTLE">Right Trigger</a> + </td> + <td> + 0x02 0x00C4 + </td> + <td> + AXIS_RTRIGGER + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_Y">Left Joystick</a> + </td> + <td> + 0x01 0x0030<br /> + 0x01 0x0031 + </td> + <td> + AXIS_X<br /> + AXIS_Y + </td> + </tr> + <tr> + <td> + <a href="http://developer.android.com/reference/android/view/MotionEvent.html#AXIS_Z">Right Joystick</a> + </td> + <td> + 0x01 0x0032<br /> + 0x01 0x0035 + </td> + <td> + AXIS_Z<br /> + AXIS_RZ + </td> + </tr> + </table> + <p class="table_footnote"> + 1 <a href="http://developer.android.com/reference/android/view/MotionEvent.html">MotionEvent</a> + </p> + <h4 id="7_2_7_remote_control"> + 7.2.7. Remote Control + </h4> + <p> + See <a href="#2_3_1_hardware">Section 2.3.1</a> for device-specific requirements. + </p> + <h3 id="7_3_sensors"> + 7.3. Sensors + </h3> + <p> + If device implementations include a particular sensor type that has a corresponding API for third-party developers, the device implementation MUST implement that API as described in the Android SDK documentation and the Android Open Source documentation on <a href="http://source.android.com/devices/sensors/">sensors</a>. + </p> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST accurately report the presence or absence of sensors per the <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html"><code>android.content.pm.PackageManager</code></a> class. + </li> + <li>[C-0-2] MUST return an accurate list of supported sensors via the <code>SensorManager.getSensorList()</code> and similar methods. + </li> + <li>[C-0-3] MUST behave reasonably for all other sensor APIs (for example, by returning <code>true</code> or <code>false</code> as appropriate when applications attempt to register listeners, not calling sensor listeners when the corresponding sensors are not present; etc.). + </li> + </ul> + <p> + If device implementations include a particular sensor type that has a corresponding API for third-party developers, they: + </p> + <ul> + <li>[C-1-1] MUST <a href="http://developer.android.com/reference/android/hardware/SensorEvent.html">report all sensor measurements</a> using the relevant International System of Units (metric) values for each sensor type as defined in the Android SDK documentation. + </li> + <li>[C-1-2] MUST report sensor data with a maximum latency of 100 milliseconds + </li> + <li>2 * sample_time for the case of a sensor streamed with a minimum required latency of 5 ms + 2 * sample_time when the application processor is active. This delay does not include any filtering delays. + </li> + <li>[C-1-3] MUST report the first sensor sample within 400 milliseconds + 2 * sample_time of the sensor being activated. It is acceptable for this sample to have an accuracy of 0. + </li> + <li> + <p> + [SR] SHOULD <a href="http://developer.android.com/reference/android/hardware/SensorEvent.html#timestamp">report the event time</a> in nanoseconds as defined in the Android SDK documentation, representing the time the event happened and synchronized with the SystemClock.elapsedRealtimeNano() clock. Existing and new Android devices are <strong>STRONGLY RECOMMENDED</strong> to meet these requirements so they will be able to upgrade to the future platform releases where this might become a REQUIRED component. The synchronization error SHOULD be below 100 milliseconds. + </p> + </li> + <li> + <p> + [C-1-7] For any API indicated by the Android SDK documentation to be a <a href="https://source.android.com/devices/sensors/report-modes.html#continuous">continuous sensor</a>, device implementations MUST continuously provide periodic data samples that SHOULD have a jitter below 3%, where jitter is defined as the standard deviation of the difference of the reported timestamp values between consecutive events. + </p> + </li> + <li> + <p> + [C-1-8] MUST ensure that the sensor event stream MUST NOT prevent the device CPU from entering a suspend state or waking up from a suspend state. + </p> + </li> + <li>When several sensors are activated, the power consumption SHOULD NOT exceed the sum of the individual sensor’s reported power consumption. + </li> + </ul> + <p> + The list above is not comprehensive; the documented behavior of the Android SDK and the Android Open Source Documentations on <a href="http://source.android.com/devices/sensors/">sensors</a> is to be considered authoritative. + </p> + <p> + Some sensor types are composite, meaning they can be derived from data provided by one or more other sensors. (Examples include the orientation sensor and the linear acceleration sensor.) + </p> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD implement these sensor types, when they include the prerequisite physical sensors as described in <a href="https://source.android.com/devices/sensors/sensor-types.html">sensor types</a>. + </li> + </ul> + <p> + If device implementations include a composite sensor, they: + </p> + <ul> + <li>[C-2-1] MUST implement the sensor as described in the Android Open Source documentation on <a href="https://source.android.com/devices/sensors/sensor-types.html#composite_sensor_type_summary">composite sensors</a>. + </li> + </ul> + <h4 id="7_3_1_accelerometer"> + 7.3.1. Accelerometer + </h4> + <ul> + <li>Device implementations SHOULD include a 3-axis accelerometer. + </li> + </ul> + <p> + If device implementations include a 3-axis accelerometer, they: + </p> + <ul> + <li>[C-1-1] MUST be able to report events up to a frequency of at least 50 Hz. + </li> + <li>[C-1-2] MUST implement and report <a href="http://developer.android.com/reference/android/hardware/Sensor.html#TYPE_ACCELEROMETER"><code>TYPE_ACCELEROMETER</code></a> sensor. + </li> + <li>[C-1-3] MUST comply with the <a href="http://developer.android.com/reference/android/hardware/SensorEvent.html">Android sensor coordinate system</a> as detailed in the Android APIs. + </li> + <li>[C-1-4] MUST be capable of measuring from freefall up to four times the gravity(4g) or more on any axis. + </li> + <li>[C-1-5] MUST have a resolution of at least 12-bits. + </li> + <li>[C-1-6] MUST have a standard deviation no greater than 0.05 m/s^, where the standard deviation should be calculated on a per axis basis on samples collected over a period of at least 3 seconds at the fastest sampling rate. + </li> + <li>[SR] are <strong>STRONGLY RECOMMENDED</strong> to implement the <code>TYPE_SIGNIFICANT_MOTION</code> composite sensor. + </li> + <li>[SR] are STRONGLY RECOMMENDED to implement the <code>TYPE_ACCELEROMETER_UNCALIBRATED</code> sensor if online accelerometer calibration is available. + </li> + <li>SHOULD implement the <code>TYPE_SIGNIFICANT_MOTION</code>, <code>TYPE_TILT_DETECTOR</code>, <code>TYPE_STEP_DETECTOR</code>, <code>TYPE_STEP_COUNTER</code> composite sensors as described in the Android SDK document. + </li> + <li>SHOULD report events up to at least 200 Hz. + </li> + <li>SHOULD have a resolution of at least 16-bits. + </li> + <li>SHOULD be calibrated while in use if the characteristics changes over the life cycle and compensated, and preserve the compensation parameters between device reboots. + </li> + <li>SHOULD be temperature compensated. + </li> + <li>SHOULD also implement <a href="https://developer.android.com/reference/android/hardware/Sensor.html#STRING_TYPE_ACCELEROMETER_UNCALIBRATED"><code>TYPE_ACCELEROMETER_UNCALIBRATED</code></a> sensor. + </li> + </ul> + <p> + If device implementations include a 3-axis accelerometer and any of the <code>TYPE_SIGNIFICANT_MOTION</code>, <code>TYPE_TILT_DETECTOR</code>, <code>TYPE_STEP_DETECTOR</code>, <code>TYPE_STEP_COUNTER</code> composite sensors are implemented: + </p> + <ul> + <li>[C-2-1] The sum of their power consumption MUST always be less than 4 mW. + </li> + <li>SHOULD each be below 2 mW and 0.5 mW for when the device is in a dynamic or static condition. + </li> + </ul> + <p> + If device implementations include a 3-axis accelerometer and a gyroscope sensor, they: + </p> + <ul> + <li>[C-3-1] MUST implement the <code>TYPE_GRAVITY</code> and <code>TYPE_LINEAR_ACCELERATION</code> composite sensors. + </li> + <li>SHOULD implement the <code>TYPE_GAME_ROTATION_VECTOR</code> composite sensor. + </li> + <li>[SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the <code>TYPE_GAME_ROTATION_VECTOR</code> sensor. + </li> + </ul> + <p> + If device implementations include a 3-axis accelerometer, a gyroscope sensor and a magnetometer sensor, they: + </p> + <ul> + <li>[C-4-1] MUST implement a <code>TYPE_ROTATION_VECTOR</code> composite sensor. + </li> + </ul> + <h4 id="7_3_2_magnetometer"> + 7.3.2. Magnetometer + </h4> + <ul> + <li>Device implementations SHOULD include a 3-axis magnetometer (compass). + </li> + </ul> + <p> + If device impelementations include a 3-axis magnetometer, they: + </p> + <ul> + <li>[C-1-1] MUST implement the <code>TYPE_MAGNETIC_FIELD</code> sensor. + </li> + <li>[C-1-2] MUST be able to report events up to a frequency of at least 10 Hz and SHOULD report events up to at least 50 Hz. + </li> + <li>[C-1-3] MUST comply with the <a href="http://developer.android.com/reference/android/hardware/SensorEvent.html">Android sensor coordinate system</a> as detailed in the Android APIs. + </li> + <li>[C-1-4] MUST be capable of measuring between -900 µT and +900 µT on each axis before saturating. + </li> + <li>[C-1-5] MUST have a hard iron offset value less than 700 µT and SHOULD have a value below 200 µT, by placing the magnetometer far from dynamic (current-induced) and static (magnet-induced) magnetic fields. + </li> + <li>[C-1-6] MUST have a resolution equal or denser than 0.6 µT. + </li> + <li>[C-1-7] MUST support online calibration and compensation of the hard iron bias, and preserve the compensation parameters between device reboots. + </li> + <li>[C-1-8] MUST have the soft iron compensation applied—the calibration can be done either while in use or during the production of the device. + </li> + <li>[C-1-9] MUST have a standard deviation, calculated on a per axis basis on samples collected over a period of at least 3 seconds at the fastest sampling rate, no greater than 1.5 µT; SHOULD have a standard deviation no greater than 0.5 µT. + </li> + <li>SHOULD implement <code>TYPE_MAGNETIC_FIELD_UNCALIBRATED</code> sensor. + </li> + <li>[SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the <code>TYPE_MAGNETIC_FIELD_UNCALIBRATED</code> sensor. + </li> + </ul> + <p> + If device impelementations include a 3-axis magnetometer, an accelerometer sensor and a gyroscope sensor, they: + </p> + <ul> + <li>[C-2-1] MUST implement a <code>TYPE_ROTATION_VECTOR</code> composite sensor. + </li> + </ul> + <p> + If device impelementations include a 3-axis magnetometer, an accelerometer, they: + </p> + <ul> + <li>MAY implement the <code>TYPE_GEOMAGNETIC_ROTATION_VECTOR</code> sensor. + </li> + </ul> + <p> + If device impelementations include a 3-axis magnetometer, an accelerometer and <code>TYPE_GEOMAGNETIC_ROTATION_VECTOR</code> sensor, they: + </p> + <ul> + <li>[C-3-1] MUST consume less than 10 mW. + </li> + <li>SHOULD consume less than 3 mW when the sensor is registered for batch mode at 10 Hz. + </li> + </ul> + <h4 id="7_3_3_gps"> + 7.3.3. GPS + </h4> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD include a GPS/GNSS receiver. + </li> + </ul> + <p> + If device implementations include a GPS/GNSS receiver and report the capability to applications through the <code>android.hardware.location.gps</code> feature flag, they: + </p> + <ul> + <li>[C-1-1] MUST support location outputs at a rate of at least 1 Hz when requested via <code>LocationManager#requestLocationUpdate</code>. + </li> + <li>[C-1-2] MUST be able to determine the location in open-sky conditions (strong signals, negligible multipath, HDOP < 2) within 10 seconds (fast time to first fix), when connected to a 0.5 Mbps or faster data speed internet connection. This requirement is typically met by the use of some form of Assisted or Predicted GPS/GNSS technique to minimize GPS/GNSS lock-on time (Assistance data includes Reference Time, Reference Location and Satellite Ephemeris/Clock). + <ul> + <li>[SR] After making such a location calculation, it is STRONGLY RECOMMENDED for the device to be able to determine its location, in open sky, within 10 seconds, when location requests are restarted, up to an hour after the initial location calculation, even when the subsequent request is made without a data connection, and/or after a power cycle. + </li> + </ul> + </li> + <li> + <p> + In open sky conditions after determining the location, while stationary or moving with less than 1 meter per second squared of acceleration: + </p> + <ul> + <li>[C-1-3] MUST be able to determine location within 20 meters, and speed within 0.5 meters per second, at least 95% of the time. + </li> + <li>[C-1-4] MUST simultaneously track and report via <a href="https://developer.android.com/reference/android/location/GnssStatus.Callback.html#GnssStatus.Callback()'"><code>GnssStatus.Callback</code></a> at least 8 satellites from one constellation. + </li> + <li>SHOULD be able to simultaneously track at least 24 satellites, from multiple constellations (e.g. GPS + at least one of Glonass, Beidou, Galileo). + </li> + <li>[C-1-5] MUST report the GNSS technology generation through the test API ‘getGnssYearOfHardware’. + </li> + <li>[SR] Continue to deliver normal GPS/GNSS location outputs during an emergency phone call. + </li> + <li>[SR] Report GNSS measurements from all constellations tracked (as reported in GnssStatus messages), with the exception of SBAS. + </li> + <li>[SR] Report AGC, and Frequency of GNSS measurement. + </li> + <li>[SR] Report all accuracy estimates (including Bearing, Speed, and Vertical) as part of each GPS Location. + </li> + <li>[SR] are STRONGLY RECOMMENDED to meet as many as possible from the additional mandatory requirements for devices reporting the year "2016" or "2017" through the Test API <code>LocationManager.getGnssYearOfHardware()</code>. + </li> + </ul> + </li> + </ul> + <p> + If device implementations include a GPS/GNSS receiver and report the capability to applications through the <code>android.hardware.location.gps</code> feature flag and the <code>LocationManager.getGnssYearOfHardware()</code> Test API reports the year "2016" or newer, they: + </p> + <ul> + <li>[C-2-1] MUST report GPS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported. + </li> + <li>[C-2-2] MUST report GPS pseudoranges and pseudorange rates, that, in open-sky conditions after determining the location, while stationary or moving with less than 0.2 meter per second squared of acceleration, are sufficient to calculate position within 20 meters, and speed within 0.2 meters per second, at least 95% of the time. + </li> + </ul> + <p> + If device implementations include a GPS/GNSS receiver and report the capability to applications through the <code>android.hardware.location.gps</code> feature flag and the <code>LocationManager.getGnssYearOfHardware()</code> Test API reports the year "2017" or newer, they: + </p> + <ul> + <li>[C-3-1] MUST continue to deliver normal GPS/GNSS location outputs during an emergency phone call. + </li> + <li>[C-3-2] MUST report GNSS measurements from all constellations tracked (as reported in GnssStatus messages), with the exception of SBAS. + </li> + <li>[C-3-3] MUST report AGC, and Frequency of GNSS measurement. + </li> + <li>[C-3-4] MUST report all accuracy estimates (including Bearing, Speed, and Vertical) as part of each GPS Location. + </li> + </ul> + <h4 id="7_3_4_gyroscope"> + 7.3.4. Gyroscope + </h4> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD include a gyroscope (angular change sensor). + </li> + <li>SHOULD NOT include a gyroscope sensor unless a 3-axis accelerometer is also included. + </li> + </ul> + <p> + If device implementations include a gyroscope, they: + </p> + <ul> + <li>[C-1-1] MUST be able to report events up to a frequency of at least 50 Hz. + </li> + <li>[C-1-2] MUST implement the <code>TYPE_GYROSCOPE</code> sensor and SHOULD also implement <code>TYPE_GYROSCOPE_UNCALIBRATED</code> sensor. + </li> + <li>[C-1-3] MUST be capable of measuring orientation changes up to 1,000 degrees per second. + </li> + <li>[C-1-4] MUST have a resolution of 12-bits or more and SHOULD have a resolution of 16-bits or more. + </li> + <li>[C-1-5] MUST be temperature compensated. + </li> + <li>[C-1-6] MUST be calibrated and compensated while in use, and preserve the compensation parameters between device reboots. + </li> + <li>[C-1-7] MUST have a variance no greater than 1e-7 rad^2 / s^2 per Hz (variance per Hz, or rad^2 / s). The variance is allowed to vary with the sampling rate, but MUST be constrained by this value. In other words, if you measure the variance of the gyro at 1 Hz sampling rate it SHOULD be no greater than 1e-7 rad^2/s^2. + </li> + <li>[SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the <code>SENSOR_TYPE_GYROSCOPE_UNCALIBRATED</code> sensor. + </li> + <li>[SR] Calibration error is STRONGLY RECOMMENDED to be less than 0.01 rad/s when device is stationary at room temperature. + </li> + <li>SHOULD report events up to at least 200 Hz. + </li> + </ul> + <p> + If device implementations include a gyroscope, an accelerometer sensor and a magnetometer sensor, they: + </p> + <ul> + <li>[C-2-1] MUST implement a <code>TYPE_ROTATION_VECTOR</code> composite sensor. + </li> + </ul> + <p> + If device implementations include a gyroscope and a accelerometer sensor, they: + </p> + <ul> + <li>[C-3-1] MUST implement the <code>TYPE_GRAVITY</code> and <code>TYPE_LINEAR_ACCELERATION</code> composite sensors. + </li> + <li>[SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the <code>TYPE_GAME_ROTATION_VECTOR</code> sensor. + </li> + <li>SHOULD implement the <code>TYPE_GAME_ROTATION_VECTOR</code> composite sensor. + </li> + </ul> + <h4 id="7_3_5_barometer"> + 7.3.5. Barometer + </h4> + <ul> + <li>Device implementations SHOULD include a barometer (ambient air pressure sensor). + </li> + </ul> + <p> + If device implementations include a barometer, they: + </p> + <ul> + <li>[C-1-1] MUST implement and report <code>TYPE_PRESSURE</code> sensor. + </li> + <li>[C-1-2] MUST be able to deliver events at 5 Hz or greater. + </li> + <li>[C-1-3] MUST be temperature compensated. + </li> + <li>[SR] STRONGLY RECOMMENDED to be able to report pressure measurements in the range 300hPa to 1100hPa. + </li> + <li>SHOULD have an absolute accuracy of 1hPa. + </li> + <li>SHOULD have a relative accuracy of 0.12hPa over 20hPa range (equivalent to ~1m accuracy over ~200m change at sea level). + </li> + </ul> + <h4 id="7_3_6_thermometer"> + 7.3.6. Thermometer + </h4> + <p> + Device implementations: <em>MAY include an ambient thermometer (temperature sensor).</em> MAY but SHOULD NOT include a CPU temperature sensor. + </p> + <p> + If device implementations include an ambient thermometer (temperature sensor), they: + </p> + <ul> + <li>[C-1-1] MUST be defined as <code>SENSOR_TYPE_AMBIENT_TEMPERATURE</code> and MUST measure the ambient (room/vehicle cabin) temperature from where the user is interacting with the device in degrees Celsius. + </li> + <li>[C-1-2] MUST be defined as <code>SENSOR_TYPE_TEMPERATURE</code>. + </li> + <li>[C-1-3] MUST measure the temperature of the device CPU. + </li> + <li>[C-1-4] MUST NOT measure any other temperature. + </li> + </ul> + <p> + Note the <code>SENSOR_TYPE_TEMPERATURE</code> sensor type was deprecated in Android 4.0. + </p> + <h4 id="7_3_7_photometer"> + 7.3.7. Photometer + </h4> + <ul> + <li>Device implementations MAY include a photometer (ambient light sensor). + </li> + </ul> + <h4 id="7_3_8_proximity_sensor"> + 7.3.8. Proximity Sensor + </h4> + <ul> + <li>Device implementations MAY include a proximity sensor. + </li> + </ul> + <p> + If device implementations include a proximity sensor, they: + </p> + <ul> + <li>[C-1-1] MUST measure the proximity of an object in the same direction as the screen. That is, the proximity sensor MUST be oriented to detect objects close to the screen, as the primary intent of this sensor type is to detect a phone in use by the user. If device implementations include a proximity sensor with any other orientation, it MUST NOT be accessible through this API. + </li> + <li>[C-1-2] MUST have 1-bit of accuracy or more. + </li> + </ul> + <h4 id="7_3_9_high_fidelity_sensors"> + 7.3.9. High Fidelity Sensors + </h4> + <p> + If device implementations include a set of higher quality sensors as defined in this section, and make available them to third-party apps, they: + </p> + <ul> + <li>[C-1-1] MUST identify the capability through the <code>android.hardware.sensor.hifi_sensors</code> feature flag. + </li> + </ul> + <p> + If device implementations declare <code>android.hardware.sensor.hifi_sensors</code>, they: + </p> + <ul> + <li> + <p> + [C-2-1] MUST have a <code>TYPE_ACCELEROMETER</code> sensor which: + </p> + <ul> + <li>MUST have a measurement range between at least -8g and +8g. + </li> + <li>MUST have a measurement resolution of at least 1024 LSB/G. + </li> + <li>MUST have a minimum measurement frequency of 12.5 Hz or lower. + </li> + <li>MUST have a maximum measurement frequency of 400 Hz or higher. + </li> + <li>MUST have a measurement noise not above 400 uG/√Hz. + </li> + <li>MUST implement a non-wake-up form of this sensor with a buffering capability of at least 3000 sensor events. + </li> + <li>MUST have a batching power consumption not worse than 3 mW. + </li> + <li>SHOULD have a stationary noise bias stability of \<15 μg √Hz from 24hr static dataset. + </li> + <li>SHOULD have a bias change vs. temperature of ≤ +/- 1mg / °C. + </li> + <li>SHOULD have a best-fit line non-linearity of ≤ 0.5%, and sensitivity change vs. temperature of ≤ 0.03%/C°. + </li> + <li>SHOULD have white noise spectrum to ensure adequate qualification of sensor’s noise integrity. + </li> + </ul> + </li> + <li> + <p> + [C-2-2] MUST have a <code>TYPE_ACCELEROMETER_UNCALIBRATED</code> with the same quality requirements as <code>TYPE_ACCELEROMETER</code>. + </p> + </li> + <li> + <p> + [C-2-3] MUST have a <code>TYPE_GYROSCOPE</code> sensor which: + </p> + <ul> + <li>MUST have a measurement range between at least -1000 and +1000 dps. + </li> + <li>MUST have a measurement resolution of at least 16 LSB/dps. + </li> + <li>MUST have a minimum measurement frequency of 12.5 Hz or lower. + </li> + <li>MUST have a maximum measurement frequency of 400 Hz or higher. + </li> + <li>MUST have a measurement noise not above 0.014°/s/√Hz. + </li> + <li>SHOULD have a stationary bias stability of < 0.0002 °/s √Hz from 24-hour static dataset. + </li> + <li>SHOULD have a bias change vs. temperature of ≤ +/- 0.05 °/ s / °C. + </li> + <li>SHOULD have a sensitivity change vs. temperature of ≤ 0.02% / °C. + </li> + <li>SHOULD have a best-fit line non-linearity of ≤ 0.2%. + </li> + <li>SHOULD have a noise density of ≤ 0.007 °/s/√Hz. + </li> + <li>SHOULD have white noise spectrum to ensure adequate qualification of sensor’s noise integrity. + </li> + <li>SHOULD have calibration error less than 0.002 rad/s in temperature range 10 ~ 40 ℃ when device is stationary. + </li> + </ul> + </li> + <li> + <p> + [C-2-4] MUST have a <code>TYPE_GYROSCOPE_UNCALIBRATED</code> with the same quality requirements as <code>TYPE_GYROSCOPE</code>. + </p> + </li> + <li>[C-2-5] MUST have a <code>TYPE_GEOMAGNETIC_FIELD</code> sensor which: + <ul> + <li>MUST have a measurement range between at least -900 and +900 uT. + </li> + <li>MUST have a measurement resolution of at least 5 LSB/uT. + </li> + <li>MUST have a minimum measurement frequency of 5 Hz or lower. + </li> + <li>MUST have a maximum measurement frequency of 50 Hz or higher. + </li> + <li>MUST have a measurement noise not above 0.5 uT. + </li> + </ul> + </li> + <li>[C-2-6] MUST have a <code>TYPE_MAGNETIC_FIELD_UNCALIBRATED</code> with the same quality requirements as <code>TYPE_GEOMAGNETIC_FIELD</code> and in addition: + <ul> + <li>MUST implement a non-wake-up form of this sensor with a buffering capability of at least 600 sensor events. + </li> + <li>SHOULD have white noise spectrum to ensure adequate qualification of sensor’s noise integrity. + </li> + </ul> + </li> + <li>[C-2-7] MUST have a <code>TYPE_PRESSURE</code> sensor which: + <ul> + <li>MUST have a measurement range between at least 300 and 1100 hPa. + </li> + <li>MUST have a measurement resolution of at least 80 LSB/hPa. + </li> + <li>MUST have a minimum measurement frequency of 1 Hz or lower. + </li> + <li>MUST have a maximum measurement frequency of 10 Hz or higher. + </li> + <li>MUST have a measurement noise not above 2 Pa/√Hz. + </li> + <li>MUST implement a non-wake-up form of this sensor with a buffering capability of at least 300 sensor events. + </li> + <li>MUST have a batching power consumption not worse than 2 mW. + </li> + </ul> + </li> + <li>[C-2-8] MUST have a <code>TYPE_GAME_ROTATION_VECTOR</code> sensor which: + <ul> + <li>MUST implement a non-wake-up form of this sensor with a buffering capability of at least 300 sensor events. + </li> + <li>MUST have a batching power consumption not worse than 4 mW. + </li> + </ul> + </li> + <li>[C-2-9] MUST have a <code>TYPE_SIGNIFICANT_MOTION</code> sensor which: + <ul> + <li>MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving. + </li> + </ul> + </li> + <li>[C-2-10] MUST have a <code>TYPE_STEP_DETECTOR</code> sensor which: + <ul> + <li>MUST implement a non-wake-up form of this sensor with a buffering capability of at least 100 sensor events. + </li> + <li>MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving. + </li> + <li>MUST have a batching power consumption not worse than 4 mW. + </li> + </ul> + </li> + <li>[C-2-11] MUST have a <code>TYPE_STEP_COUNTER</code> sensor which: + <ul> + <li>MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving. + </li> + </ul> + </li> + <li>[C-2-12] MUST have a <code>TILT_DETECTOR</code> sensor which: + <ul> + <li>MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving. + </li> + </ul> + </li> + <li>[C-2-13] The event timestamp of the same physical event reported by the Accelerometer, Gyroscope sensor and Magnetometer MUST be within 2.5 milliseconds of each other. + </li> + <li>[C-2-14] MUST have Gyroscope sensor event timestamps on the same time base as the camera subsystem and within 1 milliseconds of error. + </li> + <li>[C-2-15] MUST deliver samples to applications within 5 milliseconds from the time when the data is available on any of the above physical sensors to the application. + </li> + <li>[C-2-16] MUST not have a power consumption higher than 0.5 mW when device is static and 2.0 mW when device is moving when any combination of the following sensors are enabled: + <ul> + <li> + <code>SENSOR_TYPE_SIGNIFICANT_MOTION</code> + </li> + <li> + <code>SENSOR_TYPE_STEP_DETECTOR</code> + </li> + <li> + <code>SENSOR_TYPE_STEP_COUNTER</code> + </li> + <li> + <code>SENSOR_TILT_DETECTORS</code> + </li> + </ul> + </li> + <li>[C-2-17] MAY have a <code>TYPE_PROXIMITY</code> sensor, but if present MUST have a minimum buffer capability of 100 sensor events. + </li> + </ul> + <p> + Note that all power consumption requirements in this section do not include the power consumption of the Application Processor. It is inclusive of the power drawn by the entire sensor chain—the sensor, any supporting circuitry, any dedicated sensor processing system, etc. + </p> + <p> + If device implementations include direct sensor support, they: + </p> + <ul> + <li>[C-3-1] MUST correctly declare support of direct channel types and direct report rates level through the <a href="https://developer.android.com/reference/android/hardware/Sensor.html#isDirectChannelTypeSupported%28int%29"><code>isDirectChannelTypeSupported</code></a> and <a href="https://developer.android.com/reference/android/hardware/Sensor.html#getHighestDirectReportRateLevel%28%29"><code>getHighestDirectReportRateLevel</code></a> API. + </li> + <li>[C-3-2] MUST support at least one of the two sensor direct channel types for all sensors that declare support for sensor direct channel + </li> + <li> + <a href="https://developer.android.com/reference/android/hardware/SensorDirectChannel.html#TYPE_HARDWARE_BUFFER"><code>TYPE_HARDWARE_BUFFER</code></a> + </li> + <li> + <a href="https://developer.android.com/reference/android/hardware/SensorDirectChannel.html#TYPE_MEMORY_FILE"><code>TYPE_MEMORY_FILE</code></a> + </li> + <li>SHOULD support event reporting through sensor direct channel for primary sensor (non-wakeup variant) of the following types: + </li> + <li> + <code>TYPE_ACCELEROMETER</code> + </li> + <li> + <code>TYPE_ACCELEROMETER_UNCALIBRATED</code> + </li> + <li> + <code>TYPE_GYROSCOPE</code> + </li> + <li> + <code>TYPE_GYROSCOPE_UNCALIBRATED</code> + </li> + <li> + <code>TYPE_MAGNETIC_FIELD</code> + </li> + <li> + <code>TYPE_MAGNETIC_FIELD_UNCALIBRATED</code> + </li> + </ul> + <h4 id="7_3_10_fingerprint_sensor"> + 7.3.10. Fingerprint Sensor + </h4> + <p> + If device implementations include a secure lock screen, they: + </p> + <ul> + <li>SHOULD include a fingerprint sensor. + </li> + </ul> + <p> + If device implementations include a fingerprint sensor and make the sensor available to third-party apps, they: + </p> + <ul> + <li>[C-1-1] MUST declare support for the <code>android.hardware.fingerprint</code> feature. + </li> + <li>[C-1-2] MUST fully implement the <a href="https://developer.android.com/reference/android/hardware/fingerprint/package-summary.html">corresponding API</a> as described in the Android SDK documentation. + </li> + <li>[C-1-3] MUST have a false acceptance rate not higher than 0.002%. + </li> + <li>[SR] Are STRONGLY RECOMMENDED to have a spoof and imposter acceptance rate not higher than 7%. + </li> + <li>[C-1-4] MUST disclose that this mode may be less secure than a strong PIN, pattern, or password and clearly enumerate the risks of enabling it, if the spoof and imposter acceptance rates are higher than 7%. + </li> + <li>[C-1-5] MUST rate limit attempts for at least 30 seconds after five false trials for fingerprint verification. + </li> + <li>[C-1-6] MUST have a hardware-backed keystore implementation, and perform the fingerprint matching in a Trusted Execution Environment (TEE) or on a chip with a secure channel to the TEE. + </li> + <li>[C-1-7] MUST have all identifiable fingerprint data encrypted and cryptographically authenticated such that they cannot be acquired, read or altered outside of the Trusted Execution Environment (TEE) as documented in the <a href="https://source.android.com/devices/tech/security/authentication/fingerprint-hal.html">implementation guidelines</a> on the Android Open Source Project site. + </li> + <li>[C-1-8] MUST prevent adding a fingerprint without first establishing a chain of trust by having the user confirm existing or add a new device credential (PIN/pattern/password) that's secured by TEE; the Android Open Source Project implementation provides the mechanism in the framework to do so. + </li> + <li>[C-1-9] MUST NOT enable 3rd-party applications to distinguish between individual fingerprints. + </li> + <li>[C-1-10] MUST honor the DevicePolicyManager.KEYGUARD_DISABLE_FINGERPRINT flag. + </li> + <li>[C-1-11] MUST, when upgraded from a version earlier than Android 6.0, have the fingerprint data securely migrated to meet the above requirements or removed. + </li> + <li>[SR] Are STRONGLY RECOMMENDED to have a false rejection rate of less than 10%, as measured on the device. + </li> + <li>[SR] Are STRONGLY RECOMMENDED to have a latency below 1 second, measured from when the fingerprint sensor is touched until the screen is unlocked, for one enrolled finger. + </li> + <li>SHOULD use the Android Fingerprint icon provided in the Android Open Source Project. + </li> + </ul> + <h4 id="7_3_11_android_automotive-only_sensors"> + 7.3.11. Android Automotive-only sensors + </h4> + <p> + Automotive-specific sensors are defined in the <code>android.car.CarSensorManager API</code>. + </p> + <h5 id="7_3_11_1_current_gear"> + 7.3.11.1. Current Gear + </h5> + <p> + See <a href="#2_5_1_hardware">Section 2.5.1</a> for device-specific requirements. + </p> + <h5 id="7_3_11_2_day_night_mode"> + 7.3.11.2. Day Night Mode + </h5> + <p> + See <a href="#2_5_1_hardware">Section 2.5.1</a> for device-specific requirements. + </p> + <h5 id="7_3_11_3_driving_status"> + 7.3.11.3. Driving Status + </h5> + <p> + See <a href="#2_5_1_hardware">Section 2.5.1</a> for device-specific requirements. + </p> + <h5 id="7_3_11_4_wheel_speed"> + 7.3.11.4. Wheel Speed + </h5> + <p> + See <a href="#2_5_1_hardware">Section 2.5.1</a> for device-specific requirements. + </p> + <h3 id="7_3_12_pose_sensor"> + 7.3.12. Pose Sensor + </h3> + <p> + Device implementations: + </p> + <ul> + <li>MAY support pose sensor with 6 degrees of freedom. + </li> + </ul> + <p> + If device implementations support pose sensor with 6 degrees of freedom, they: + </p> + <ul> + <li>[C-1-1] MUST implement and report <a href="https://developer.android.com/reference/android/hardware/Sensor.html#TYPE_POSE_6DOF"><code>TYPE_POSE_6DOF</code></a> sensor. + </li> + <li>[C-1-2] MUST be more accurate than the rotation vector alone. + </li> + </ul> + <h3 id="7_4_data_connectivity"> + 7.4. Data Connectivity + </h3> + <h4 id="7_4_1_telephony"> + 7.4.1. Telephony + </h4> + <p> + “Telephony” as used by the Android APIs and this document refers specifically to hardware related to placing voice calls and sending SMS messages via a GSM or CDMA network. While these voice calls may or may not be packet-switched, they are for the purposes of Android considered independent of any data connectivity that may be implemented using the same network. In other words, the Android “telephony” functionality and APIs refer specifically to voice calls and SMS. For instance, device implementations that cannot place calls or send/receive SMS messages are not considered a telephony device, regardless of whether they use a cellular network for data connectivity. + </p> + <ul> + <li>Android MAY be used on devices that do not include telephony hardware. That is, Android is compatible with devices that are not phones. + </li> + </ul> + <p> + If device implementations include GSM or CDMA telephony, they: + </p> + <ul> + <li>[C-1-1] MUST declare the <code>android.hardware.telephony</code> feature flag and other sub-feature flags according to the technology. + </li> + <li>[C-1-2] MUST implement full support for the API for that technology. + </li> + </ul> + <p> + If device implementations do not include telephony hardware, they: + </p> + <ul> + <li>[C-2-1] MUST implement the full APIs as no-ops. + </li> + </ul> + <h5 id="7_4_1_1_number_blocking_compatibility"> + 7.4.1.1. Number Blocking Compatibility + </h5> + <p> + If device implementations report the <code>android.hardware.telephony feature</code>, they: + </p> + <ul> + <li>[C-1-1] MUST include number blocking support + </li> + <li>[C-1-2] MUST fully implement <a href="http://developer.android.com/reference/android/provider/BlockedNumberContract.html"><code>BlockedNumberContract</code></a> and the corresponding API as described in the SDK documentation. + </li> + <li>[C-1-3] MUST block all calls and messages from a phone number in 'BlockedNumberProvider' without any interaction with apps. The only exception is when number blocking is temporarily lifted as described in the SDK documentation. + </li> + <li>[C-1-4] MUST NOT write to the <a href="http://developer.android.com/reference/android/provider/CallLog.html">platform call log provider</a> for a blocked call. + </li> + <li>[C-1-5] MUST NOT write to the <a href="http://developer.android.com/reference/android/provider/Telephony.html">Telephony provider</a> for a blocked message. + </li> + <li>[C-1-6] MUST implement a blocked numbers management UI, which is opened with the intent returned by <code>TelecomManager.createManageBlockedNumbersIntent()</code> method. + </li> + <li>[C-1-7] MUST NOT allow secondary users to view or edit the blocked numbers on the device as the Android platform assumes the primary user to have full control of the telephony services, a single instance, on the device. All blocking related UI MUST be hidden for secondary users and the blocked list MUST still be respected. + </li> + <li>SHOULD migrate the blocked numbers into the provider when a device updates to Android 7.0. + </li> + </ul> + <h5 id="7_4_1_2_telecom_api"> + 7.4.1.2. Telecom API + </h5> + <p> + If device implementations report <code>android.hardware.telephony</code>, they: + </p> + <ul> + <li>[C-SR] Are STRONGLY RECOMMENDED to handle the the audio headset's <code>KEYCODE_MEDIA_PLAY_PAUSE</code> and <code>KEYCODE_HEADSETHOOK</code> events for the <a href="https://developer.android.com/reference/android/telecom/package-summary.html"><code>android.telecom</code></a> APIs as below: + <ul> + <li>Call <a href="https://developer.android.com/reference/android/telecom/Connection.html#onDisconnect%28%29"><code>Connection.onDisconnect()</code></a> when a short press of the key event is detected during an ongoing call. + </li> + <li>Call <a href="https://developer.android.com/reference/android/telecom/Connection.html#onAnswer%28%29"><code>Connection.onAnswer()</code></a> when a short press of the key event is detected during an incoming call. + </li> + <li>Call <a href="https://developer.android.com/reference/android/telecom/Connection.html#onReject%28%29"><code>Connection.onReject()</code></a> when a long press of the key event is detected during an incoming call. + </li> + <li>Toggle the mute status of the <a href="https://developer.android.com/reference/android/telecom/CallAudioState.html"><code>CallAudioState</code></a> + </li> + </ul> + </li> + </ul> + <h4 id="7_4_2_ieee_802_11_(wi-fi)"> + 7.4.2. IEEE 802.11 (Wi-Fi) + </h4> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD include support for one or more forms of 802.11. + </li> + </ul> + <p> + If device implementations include support for 802.11 and expose the functionality to a third-party application, they + </p> + <ul> + <li>[C-1-1] MUST implement the corresponding Android API. + </li> + <li>[C-1-2] MUST report the hardware feature flag <code>android.hardware.wifi</code>. + </li> + <li>[C-1-3] MUST implement the <a href="http://developer.android.com/reference/android/net/wifi/WifiManager.MulticastLock.html">multicast API</a> as described in the SDK documentation. + </li> + <li>[C-1-4] MUST support multicast DNS (mDNS) and MUST NOT filter mDNS packets (224.0.0.251) at any time of operation including: + <ul> + <li>Even when the screen is not in an active state. + </li> + <li>For Android Television device implementations, even when in standby power states. + </li> + </ul> + </li> + <li>SHOULD randomize the source MAC address and sequence number of probe request frames, once at the beginning of each scan, while STA is disconnected. + <ul> + <li>Each group of probe request frames comprising one scan should use one consistent MAC address (SHOULD NOT randomize MAC address halfway through a scan). + </li> + <li>Probe request sequence number should iterate as normal (sequentially) between the probe requests in a scan + </li> + <li>Probe request sequence number should randomize between the last probe request of a scan and the first probe request of the next scan + </li> + </ul> + </li> + <li>SHOULD only allow the following information elements in probe request frames, while STA is disconnected: + <ul> + <li>SSID Parameter Set (0) + </li> + <li>DS Parameter Set (3) + </li> + </ul> + </li> + </ul> + <h5 id="7_4_2_1_wi-fi_direct"> + 7.4.2.1. Wi-Fi Direct + </h5> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD include support for Wi-Fi Direct (Wi-Fi peer-to-peer). + </li> + </ul> + <p> + If device implementations include support for Wi-Fi Direct, they: + </p> + <ul> + <li>[C-1-1] MUST implement the <a href="http://developer.android.com/reference/android/net/wifi/p2p/WifiP2pManager.html">corresponding Android API</a> as described in the SDK documentation. + </li> + <li>[C-1-2] MUST report the hardware feature <code>android.hardware.wifi.direct</code>. + </li> + <li>[C-1-3] MUST support regular Wi-Fi operation. + </li> + <li>SHOULD support Wi-Fi and Wi-Fi Direct operations concurrently. + </li> + </ul> + <h5 id="7_4_2_2_wi-fi_tunneled_direct_link_setup"> + 7.4.2.2. Wi-Fi Tunneled Direct Link Setup + </h5> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD include support for <a href="http://developer.android.com/reference/android/net/wifi/WifiManager.html">Wi-Fi Tunneled Direct Link Setup (TDLS)</a> as described in the Android SDK Documentation. + </li> + </ul> + <p> + If device implementations include support for TDLS and TDLS is enabled by the WiFiManager API, they: + </p> + <ul> + <li>[C-1-1] MUST declare support for TDLS through [<code>WifiManager.isTdlsSupported</code>] (https://developer.android.com/reference/android/net/wifi/WifiManager.html#isTdlsSupported%28%29). + </li> + <li>SHOULD use TDLS only when it is possible AND beneficial. + </li> + <li>SHOULD have some heuristic and NOT use TDLS when its performance might be worse than going through the Wi-Fi access point. + </li> + </ul> + <h5 id="7_4_2_3_wi-fi_aware"> + 7.4.2.3. Wi-Fi Aware + </h5> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD include support for <a href="http://www.wi-fi.org/discover-wi-fi/wi-fi-aware">Wi-Fi Aware</a>. + </li> + </ul> + <p> + If device implementations include support for Wi-Fi Aware and expose the functionality to third-party apps, then they: + </p> + <ul> + <li>[C-1-1] MUST implement the <code>WifiAwareManager</code> APIs as described in the <a href="http://developer.android.com/reference/android/net/wifi/aware/WifiAwareManager.html">SDK documentation</a>. + </li> + <li>[C-1-2] MUST declare the <code>android.hardware.wifi.aware</code> feature flag. + </li> + <li>[C-1-3] MUST support Wi-Fi and Wi-Fi Aware operations concurrently. + </li> + <li>[C-1-4] MUST randomize the Wi-Fi Aware management interface address at intervals no longer then 30 minutes and whenever Wi-Fi Aware is enabled. + </li> + </ul> + <h5 id="7_4_2_4_wi-fi_passpoint"> + 7.4.2.4. Wi-Fi Passpoint + </h5> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD include support for <a href="http://www.wi-fi.org/discover-wi-fi/wi-fi-certified-passpoint">Wi-Fi Passpoint</a>. + </li> + </ul> + <p> + If device implementations include support for Wi-Fi Passpoint, they: + </p> + <ul> + <li>[C-1-1] MUST implement the Passpoint related <code>WifiManager</code> APIs as described in the <a href="http://developer.android.com/reference/android/net/wifi/WifiManager.html">SDK documentation</a>. + </li> + <li>[C-1-2] MUST support IEEE 802.11u standard, specifically related to Network Discovery and Selection, such as Generic Advertisement Service (GAS) and Access Network Query Protocol (ANQP). + </li> + </ul> + <p> + Conversely if device implementations do not include support for Wi-Fi Passpoint: + </p> + <ul> + <li>[C-2-1] The implementation of the Passpoint related <code>WifiManager</code> APIs MUST throw an <code>UnsupportedOperationException</code>. + </li> + </ul> + <h4 id="7_4_3_bluetooth"> + 7.4.3. Bluetooth + </h4> + <p> + If device implementations support Bluetooth Audio profile, they: + </p> + <ul> + <li>SHOULD support Advanced Audio Codecs and Bluetooth Audio Codecs (e.g. LDAC). + </li> + </ul> + <p> + If device implementations declare <code>android.hardware.vr.high_performance</code> feature, they: + </p> + <ul> + <li>[C-1-1] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension. + </li> + </ul> + <p> + Android includes support for <a href="http://developer.android.com/reference/android/bluetooth/package-summary.html">Bluetooth and Bluetooth Low Energy</a>. + </p> + <p> + If device implementations include support for Bluetooth and Bluetooth Low Energy, they: + </p> + <ul> + <li>[C-2-1] MUST declare the relevant platform features (<code>android.hardware.bluetooth</code> and <code>android.hardware.bluetooth_le</code> respectively) and implement the platform APIs. + </li> + <li>SHOULD implement relevant Bluetooth profiles such as A2DP, AVCP, OBEX, etc. as appropriate for the device. + </li> + </ul> + <p> + If device implementations include support for Bluetooth Low Energy, they: + </p> + <ul> + <li>[C-3-1] MUST declare the hardware feature <code>android.hardware.bluetooth_le</code>. + </li> + <li>[C-3-2] MUST enable the GATT (generic attribute profile) based Bluetooth APIs as described in the SDK documentation and <a href="http://developer.android.com/reference/android/bluetooth/package-summary.html">android.bluetooth</a>. + </li> + <li>[C-3-3] MUST report the correct value for <code>BluetoothAdapter.isOffloadedFilteringSupported()</code> to indicate whether the filtering logic for the <a href="https://developer.android.com/reference/android/bluetooth/le/ScanFilter.html">ScanFilter</a> API classes is implemented. + </li> + <li>[C-3-4] MUST report the correct value for <code>BluetoothAdapter.isMultipleAdvertisementSupported()</code> to indicate whether Low Energy Advertising is supported. + </li> + <li>SHOULD support offloading of the filtering logic to the bluetooth chipset when implementing the <a href="https://developer.android.com/reference/android/bluetooth/le/ScanFilter.html">ScanFilter API</a>. + </li> + <li>SHOULD support offloading of the batched scanning to the bluetooth chipset. + </li> + <li> + <p> + SHOULD support multi advertisement with at least 4 slots. + </p> + </li> + <li> + <p> + [SR] STRONGLY RECOMMENDED to implement a Resolvable Private Address (RPA) timeout no longer than 15 minutes and rotate the address at timeout to protect user privacy. + </p> + </li> + </ul> + <h4 id="7_4_4_near-field_communications"> + 7.4.4. Near-Field Communications + </h4> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD include a transceiver and related hardware for Near-Field Communications (NFC). + </li> + <li>[C-0-1] MUST implement <code>android.nfc.NdefMessage</code> and <code>android.nfc.NdefRecord</code> APIs even if they do not include support for NFC or declare the <code>android.hardware.nfc</code> feature as the classes represent a protocol-independent data representation format. + </li> + </ul> + <p> + If device implementations include NFC hardware and plan to make it available to third-party apps, they: + </p> + <ul> + <li>[C-1-1] MUST report the <code>android.hardware.nfc</code> feature from the <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html"><code>android.content.pm.PackageManager.hasSystemFeature()</code> method</a>. + </li> + <li>MUST be capable of reading and writing NDEF messages via the following NFC standards as below: + </li> + <li>[C-1-2] MUST be capable of acting as an NFC Forum reader/writer (as defined by the NFC Forum technical specification NFCForum-TS-DigitalProtocol-1.0) via the following NFC standards: + </li> + <li>NfcA (ISO14443-3A) + </li> + <li>NfcB (ISO14443-3B) + </li> + <li>NfcF (JIS X 6319-4) + </li> + <li>IsoDep (ISO 14443-4) + </li> + <li>NFC Forum Tag Types 1, 2, 3, 4, 5 (defined by the NFC Forum) + </li> + <li> + <p> + [SR] STRONGLY RECOMMENDED to be capable of reading and writing NDEF messages as well as raw data via the following NFC standards. Note that while the NFC standards are stated as STRONGLY RECOMMENDED, the Compatibility Definition for a future version is planned to change these to MUST. These standards are optional in this version but will be required in future versions. Existing and new devices that run this version of Android are very strongly encouraged to meet these requirements now so they will be able to upgrade to the future platform releases. + </p> + </li> + <li> + <p> + [C-1-3] MUST be capable of transmitting and receiving data via the following peer-to-peer standards and protocols: + </p> + </li> + <li>ISO 18092 + </li> + <li>LLCP 1.2 (defined by the NFC Forum) + </li> + <li>SDP 1.0 (defined by the NFC Forum) + </li> + <li> + <a href="http://static.googleusercontent.com/media/source.android.com/en/us/compatibility/ndef-push-protocol.pdf">NDEF Push Protocol</a> + </li> + <li>SNEP 1.0 (defined by the NFC Forum) + </li> + <li>[C-1-4] MUST include support for <a href="http://developer.android.com/guide/topics/connectivity/nfc/nfc.html">Android Beam</a> and SHOULD enable Android Beam by default. + </li> + <li>[C-1-5] MUST be able to send and receive using Android Beam, when Android Beam is enabled or another proprietary NFC P2p mode is turned on. + </li> + <li>[C-1-6] MUST implement the SNEP default server. Valid NDEF messages received by the default SNEP server MUST be dispatched to applications using the <code>android.nfc.ACTION_NDEF_DISCOVERED</code> intent. Disabling Android Beam in settings MUST NOT disable dispatch of incoming NDEF message. + </li> + <li>[C-1-7] MUST honor the <code>android.settings.NFCSHARING_SETTINGS</code> intent to show <a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_NFCSHARING_SETTINGS">NFC sharing settings</a>. + </li> + <li>[C-1-8] MUST implement the NPP server. Messages received by the NPP server MUST be processed the same way as the SNEP default server. + </li> + <li>[C-1-9] MUST implement a SNEP client and attempt to send outbound P2P NDEF to the default SNEP server when Android Beam is enabled. If no default SNEP server is found then the client MUST attempt to send to an NPP server. + </li> + <li>[C-1-10] MUST allow foreground activities to set the outbound P2P NDEF message using <code>android.nfc.NfcAdapter.setNdefPushMessage</code>, and <code>android.nfc.NfcAdapter.setNdefPushMessageCallback</code>, and <code>android.nfc.NfcAdapter.enableForegroundNdefPush</code>. + </li> + <li>SHOULD use a gesture or on-screen confirmation, such as 'Touch to Beam', before sending outbound P2P NDEF messages. + </li> + <li>[C-1-11] MUST support NFC Connection handover to Bluetooth when the device supports Bluetooth Object Push Profile. + </li> + <li>[C-1-12] MUST support connection handover to Bluetooth when using <code>android.nfc.NfcAdapter.setBeamPushUris</code>, by implementing the “<a href="http://members.nfc-forum.org/specs/spec_list/#conn_handover">Connection Handover version 1.2</a>” and “<a href="http://members.nfc-forum.org/apps/group_public/download.php/18688/NFCForum-AD-BTSSP_1_1.pdf">Bluetooth Secure Simple Pairing Using NFC version 1.0</a>” specs from the NFC Forum. Such an implementation MUST implement the handover LLCP service with service name “urn:nfc:sn:handover” for exchanging the handover request/select records over NFC, and it MUST use the Bluetooth Object Push Profile for the actual Bluetooth data transfer. For legacy reasons (to remain compatible with Android 4.1 devices), the implementation SHOULD still accept SNEP GET requests for exchanging the handover request/select records over NFC. However an implementation itself SHOULD NOT send SNEP GET requests for performing connection handover. + </li> + <li>[C-1-13] MUST poll for all supported technologies while in NFC discovery mode. + </li> + <li>SHOULD be in NFC discovery mode while the device is awake with the screen active and the lock-screen unlocked. + </li> + <li>SHOULD be capable of reading the barcode and URL (if encoded) of <a href="http://developer.android.com/reference/android/nfc/tech/NfcBarcode.html">Thinfilm NFC Barcode</a> products. + </li> + </ul> + <p> + (Note that publicly available links are not available for the JIS, ISO, and NFC Forum specifications cited above.) + </p> + <p> + Android includes support for NFC Host Card Emulation (HCE) mode. + </p> + <p> + If device implementations include an NFC controller chipset capable of HCE (for NfcA and/or NfcB) and support Application ID (AID) routing, they: + </p> + <ul> + <li>[C-2-1] MUST report the <code>android.hardware.nfc.hce</code> feature constant. + </li> + <li>[C-2-2] MUST support <a href="http://developer.android.com/guide/topics/connectivity/nfc/hce.html">NFC HCE APIs</a> as defined in the Android SDK. + </li> + </ul> + <p> + If device implementations include an NFC controller chipset capable of HCE for NfcF, and implement the feature for third-party applications, they: + </p> + <ul> + <li>[C-3-1] MUST report the <code>android.hardware.nfc.hcef</code> feature constant. + </li> + <li>[C-3-2] MUST implement the [NfcF Card Emulation APIs] (https://developer.android.com/reference/android/nfc/cardemulation/NfcFCardEmulation.html) as defined in the Android SDK. + </li> + </ul> + <p> + If device implementations include general NFC support as described in this section and support MIFARE technologies (MIFARE Classic, MIFARE Ultralight, NDEF on MIFARE Classic) in the reader/writer role, they: + </p> + <ul> + <li>[C-4-1] MUST implement the corresponding Android APIs as documented by the Android SDK. + </li> + <li>[C-4-2] MUST report the feature <code>com.nxp.mifare</code> from the <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html"><code>android.content.pm.PackageManager.hasSystemFeature</code>()</a> method. Note that this is not a standard Android feature and as such does not appear as a constant in the <code>android.content.pm.PackageManager</code> class. + </li> + </ul> + <h4 id="7_4_5_minimum_network_capability"> + 7.4.5. Minimum Network Capability + </h4> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST include support for one or more forms of data networking. Specifically, device implementations MUST include support for at least one data standard capable of 200Kbit/sec or greater. Examples of technologies that satisfy this requirement include EDGE, HSPA, EV-DO, 802.11g, Ethernet, Bluetooth PAN, etc. + </li> + <li>[C-0-2] MUST include an IPv6 networking stack and support IPv6 communication using the managed APIs, such as <code>java.net.Socket</code> and <code>java.net.URLConnection</code>, as well as the native APIs, such as <code>AF_INET6</code> sockets. + </li> + <li>[C-0-3] MUST enable IPv6 by default. + </li> + <li>MUST ensure that IPv6 communication is as reliable as IPv4, for example. + </li> + <li>[C-0-4] MUST maintain IPv6 connectivity in doze mode. + </li> + <li>[C-0-5] Rate-limiting MUST NOT cause the device to lose IPv6 connectivity on any IPv6-compliant network that uses RA lifetimes of at least 180 seconds. + </li> + <li>SHOULD also include support for at least one common wireless data standard, such as 802.11 (Wi-Fi) when a physical networking standard (such as Ethernet) is the primary data connection + </li> + <li>MAY implement more than one form of data connectivity. + </li> + </ul> + <p> + The required level of IPv6 support depends on the network type, as follows: + </p> + <p> + If devices implementations support Wi-Fi networks, they: + </p> + <ul> + <li>[C-1-1] MUST support dual-stack and IPv6-only operation on Wi-Fi. + </li> + </ul> + <p> + If device impelementations support Ethernet networks, they: + </p> + <ul> + <li>[C-2-1] MUST support dual-stack operation on Ethernet. + </li> + </ul> + <p> + If device implementations support cellular data, they: + </p> + <ul> + <li>[C-3-1] MUST simultaneously meet these requirements on each network to which it is connected when a device is simultaneously connected to more than one network (e.g., Wi-Fi and cellular data), . + </li> + <li>SHOULD support IPv6 operation (IPv6-only and possibly dual-stack) on cellular data. + </li> + </ul> + <h4 id="7_4_6_sync_settings"> + 7.4.6. Sync Settings + </h4> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST have the master auto-sync setting on by default so that the method <a href="http://developer.android.com/reference/android/content/ContentResolver.html"><code>getMasterSyncAutomatically()</code></a> returns “true”. + </li> + </ul> + <h4 id="7_4_7_data_saver"> + 7.4.7. Data Saver + </h4> + <p> + If device implementations include a metered connection, they are: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to provide the data saver mode. + </li> + </ul> + <p> + If device implementations provide the data saver mode, they: + </p> + <ul> + <li>[C-1-1] MUST support all the APIs in the <code>ConnectivityManager</code> class as described in the <a href="https://developer.android.com/training/basics/network-ops/data-saver.html">SDK documentation</a> + </li> + <li>[C-1-2] MUST provide a user interface in the settings, that handles the <a href="https://developer.android.com/reference/android/provider/Settings.html#ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS"><code>Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS</code></a> intent, allowing users to add applications to or remove applications from the whitelist. + </li> + </ul> + <p> + If device implementations do not provide the data saver mode, they: + </p> + <ul> + <li>[C-2-1] MUST return the value <code>RESTRICT_BACKGROUND_STATUS_DISABLED</code> for <a href="https://developer.android.com/reference/android/net/ConnectivityManager.html#getRestrictBackgroundStatus%28%29"><code>ConnectivityManager.getRestrictBackgroundStatus()</code></a> + </li> + <li>[C-2-2] MUST NOT broadcast <code>ConnectivityManager.ACTION_RESTRICT_BACKGROUND_CHANGED</code>. + </li> + <li>[C-2-3] MUST have an activity that handles the <code>Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS</code> intent but MAY implement it as a no-op. + </li> + </ul> + <h3 id="7_5_cameras"> + 7.5. Cameras + </h3> + <p> + If device implementations include at least one camera, they: + </p> + <ul> + <li>[C-1-1] MUST declare the <code>android.hardware.camera.any</code> feature flag. + </li> + <li>[C-1-2] MUST be possible for an application to simultaneously allocate 3 RGBA_8888 bitmaps equal to the size of the images produced by the largest-resolution camera sensor on the device, while camera is open for the purpose of basic preview and still capture. + </li> + </ul> + <h4 id="7_5_1_rear-facing_camera"> + 7.5.1. Rear-Facing Camera + </h4> + <p> + A rear-facing camera is a camera located on the side of the device opposite the display; that is, it images scenes on the far side of the device, like a traditional camera. + </p> + <p> + Device implementations: + </p> + <ul> + <li>SHOULD include a rear-facing camera. + </li> + </ul> + <p> + If device implementations include at least one rear-facing camera, they: + </p> + <ul> + <li>[C-1-1] MUST report the feature flag <code>android.hardware.camera</code> and <code>android.hardware.camera.any</code>. + </li> + <li>[C-1-2] MUST have a resolution of at least 2 megapixels. + </li> + <li>SHOULD have either hardware auto-focus or software auto-focus implemented in the camera driver (transparent to application software). + </li> + <li>MAY have fixed-focus or EDOF (extended depth of field) hardware. + </li> + <li>MAY include a flash. + </li> + </ul> + <p> + If the Camera includes a flash: + </p> + <ul> + <li>[C-2-1] the flash lamp MUST NOT be lit while an <code>android.hardware.Camera.PreviewCallback</code> instance has been registered on a Camera preview surface, unless the application has explicitly enabled the flash by enabling the <code>FLASH_MODE_AUTO</code> or <code>FLASH_MODE_ON</code> attributes of a <code>Camera.Parameters</code> object. Note that this constraint does not apply to the device’s built-in system camera application, but only to third-party applications using <code>Camera.PreviewCallback</code>. + </li> + </ul> + <h4 id="7_5_2_front-facing_camera"> + 7.5.2. Front-Facing Camera + </h4> + <p> + A front-facing camera is a camera located on the same side of the device as the display; that is, a camera typically used to image the user, such as for video conferencing and similar applications. + </p> + <p> + Device implementations: + </p> + <ul> + <li>MAY include a front-facing camera + </li> + </ul> + <p> + If device implementations include at least one front-facing camera, they: + </p> + <ul> + <li>[C-1-1] MUST report the feature flag <code>android.hardware.camera.any</code> and <code>android.hardware.camera.front</code>. + </li> + <li>[C-1-2] MUST have a resolution of at least VGA (640x480 pixels). + </li> + <li>[C-1-3] MUST NOT use a front-facing camera as the default for the Camera API and MUST NOT configure the API to treat a front-facing camera as the default rear-facing camera, even if it is the only camera on the device. + </li> + <li>[C-1-5] The camera preview MUST be mirrored horizontally relative to the orientation specified by the application when the current application has explicitly requested that the Camera display be rotated via a call to the <a href="http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)"><code>android.hardware.Camera.setDisplayOrientation()</code></a> method. Conversely, the preview MUST be mirrored along the device’s default horizontal axis when the the current application does not explicitly request that the Camera display be rotated via a call to the <a href="http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)"><code>android.hardware.Camera.setDisplayOrientation()</code></a> method. + </li> + <li>[C-1-6] MUST NOT mirror the final captured still image or video streams returned to application callbacks or committed to media storage. + </li> + <li>[C-1-7] MUST mirror the image displayed by the postview in the same manner as the camera preview image stream. + </li> + <li>MAY include features (such as auto-focus, flash, etc.) available to rear-facing cameras as described in <a href="#7_5_1_rear-facing_camera">section 7.5.1</a>. + </li> + </ul> + <p> + If device implementations are capable of being rotated by user (such as automatically via an accelerometer or manually via user input): + </p> + <ul> + <li>[C-2-1] The camera preview MUST be mirrored horizontally relative to the device’s current orientation. + </li> + </ul> + <h4 id="7_5_3_external_camera"> + 7.5.3. External Camera + </h4> + <p> + Device implementations: + </p> + <ul> + <li>MAY include support for an external camera that is not necessarily always connected. + </li> + </ul> + <p> + If device impelmentations include support for an external camera, they: + </p> + <ul> + <li>[C-1-1] MUST declare the platform feature flag <code>android.hardware.camera.external</code> and <code>android.hardware camera.any</code>. + </li> + <li>[C-1-2] MUST support USB Video Class (UVC 1.0 or higher) if the external camera connects through the USB port. + </li> + <li>SHOULD support video compressions such as MJPEG to enable transfer of high-quality unencoded streams (i.e. raw or independently compressed picture streams). + </li> + <li>MAY support multiple cameras. + </li> + <li>MAY support camera-based video encoding. If supported, a simultaneous unencoded / MJPEG stream (QVGA or greater resolution) MUST be accessible to the device implementation. + </li> + </ul> + <h4 id="7_5_4_camera_api_behavior"> + 7.5.4. Camera API Behavior + </h4> + <p> + Android includes two API packages to access the camera, the newer android.hardware.camera2 API expose lower-level camera control to the app, including efficient zero-copy burst/streaming flows and per-frame controls of exposure, gain, white balance gains, color conversion, denoising, sharpening, and more. + </p> + <p> + The older API package, <code>android.hardware.Camera</code>, is marked as deprecated in Android 5.0 but as it should still be available for apps to use. Android device implementations MUST ensure the continued support of the API as described in this section and in the Android SDK. + </p> + <p> + Device implementations MUST implement the following behaviors for the camera-related APIs, for all available cameras. Device implementations: + </p> + <ul> + <li>[C-0-1] MUST use <code>android.hardware.PixelFormat.YCbCr_420_SP</code> for preview data provided to application callbacks when an application has never called <code>android.hardware.Camera.Parameters.setPreviewFormat(int)</code>. + </li> + <li>[C-0-2] MUST further be in the NV21 encoding format when an application registers an <code>android.hardware.Camera.PreviewCallback</code> instance and the system calls the <code>onPreviewFrame()</code> method and the preview format is YCbCr_420_SP, the data in the byte[] passed into <code>onPreviewFrame()</code>. That is, NV21 MUST be the default. + </li> + <li>[C-0-3] MUST support the YV12 format (as denoted by the <code>android.graphics.ImageFormat.YV12</code> constant) for camera previews for both front- and rear-facing cameras for <code>android.hardware.Camera</code>. (The hardware video encoder and camera may use any native pixel format, but the device implementation MUST support conversion to YV12.) + </li> + <li>[C-0-4] MUST support the <code>android.hardware.ImageFormat.YUV_420_888</code> and <code>android.hardware.ImageFormat.JPEG</code> formats as outputs through the <code>android.media.ImageReader</code> API for <code>android.hardware.camera2</code> devices that advertise <a href="https://developer.android.com/reference/android/hardware/camera2/CameraMetadata.html#REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE"><code>REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE</code></a> capability in <a href="https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#REQUEST_AVAILABLE_CAPABILITIES"><code>android.request.availableCapabilities</code></a>. + </li> + <li>[C-0-5] MUST still implement the full <a href="http://developer.android.com/reference/android/hardware/Camera.html">Camera API</a> included in the Android SDK documentation, regardless of whether the device includes hardware autofocus or other capabilities. For instance, cameras that lack autofocus MUST still call any registered <code>android.hardware.Camera.AutoFocusCallback</code> instances (even though this has no relevance to a non-autofocus camera.) Note that this does apply to front-facing cameras; for instance, even though most front-facing cameras do not support autofocus, the API callbacks must still be “faked” as described. + </li> + <li>[C-0-6] MUST recognize and honor each parameter name defined as a constant on the <a href="http://developer.android.com/reference/android/hardware/Camera.Parameters.html"><code>android.hardware.Camera.Parameters</code></a> class. Conversely, device implementations MUST NOT honor or recognize string constants passed to the <code>android.hardware.Camera.setParameters()</code> method other than those documented as constants on the <code>android.hardware.Camera.Parameters</code>. That is, device implementations MUST support all standard Camera parameters if the hardware allows, and MUST NOT support custom Camera parameter types. For instance, device implementations that support image capture using high dynamic range (HDR) imaging techniques MUST support camera parameter <code>Camera.SCENE_MODE_HDR</code>. + </li> + <li>[C-0-7] MUST report the proper level of support with the <a href="https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#INFO_SUPPORTED_HARDWARE_LEVEL"><code>android.info.supportedHardwareLevel</code></a> property as described in the Android SDK and report the appropriate <a href="http://source.android.com/devices/camera/versioning.html">framework feature flags</a>. + </li> + <li>[C-0-8] MUST also declare its individual camera capabilities of <code>android.hardware.camera2</code> via the <code>android.request.availableCapabilities</code> property and declare the appropriate <a href="http://source.android.com/devices/camera/versioning.html">feature flags</a>; MUST define the feature flag if any of its attached camera devices supports the feature. + </li> + <li>[C-0-9] MUST broadcast the <code>Camera.ACTION_NEW_PICTURE</code> intent whenever a new picture is taken by the camera and the entry of the picture has been added to the media store. + </li> + <li>[C-0-10] MUST broadcast the <code>Camera.ACTION_NEW_VIDEO</code> intent whenever a new video is recorded by the camera and the entry of the picture has been added to the media store. + </li> + </ul> + <h4 id="7_5_5_camera_orientation"> + 7.5.5. Camera Orientation + </h4> + <p> + If device implementations have a front- or a rear-facing camera, such camera(s): + </p> + <ul> + <li>[C-1-1] MUST be oriented so that the long dimension of the camera aligns with the screen’s long dimension. That is, when the device is held in the landscape orientation, cameras MUST capture images in the landscape orientation. This applies regardless of the device’s natural orientation; that is, it applies to landscape-primary devices as well as portrait-primary devices. + </li> + </ul> + <h3 id="7_6_memory_and_storage"> + 7.6. Memory and Storage + </h3> + <h4 id="7_6_1_minimum_memory_and_storage"> + 7.6.1. Minimum Memory and Storage + </h4> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST include a <a href="http://developer.android.com/reference/android/app/DownloadManager.html">Download Manager</a> that applications MAY use to download data files and they MUST be capable of downloading individual files of at least 100MB in size to the default “cache” location. + </li> + </ul> + <h4 id="7_6_2_application_shared_storage"> + 7.6.2. Application Shared Storage + </h4> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST offer storage to be shared by applications, also often referred as “shared external storage”, "application shared storage" or by the Linux path "/sdcard" it is mounted on. + </li> + <li>[C-0-2] MUST be configured with shared storage mounted by default, in other words “out of the box”, regardless of whether the storage is implemented on an internal storage component or a removable storage medium (e.g. Secure Digital card slot). + </li> + <li>[C-0-3] MUST mount the application shared storage directly on the Linux path <code>sdcard</code> or include a Linux symbolic link from <code>sdcard</code> to the actual mount point. + </li> + <li>[C-0-4] MUST enforce the <code>android.permission.WRITE_EXTERNAL_STORAGE</code> permission on this shared storage as documented in the SDK. Shared storage MUST otherwise be writable by any application that obtains that permission. + </li> + </ul> + <p> + Device implementations MAY meet the above requirements using either: + </p> + <ul> + <li>a user-accessible removable storage, such as a Secure Digital (SD) card slot. + </li> + <li>a portion of the internal (non-removable) storage as implemented in the Android Open Source Project (AOSP). + </li> + </ul> + <p> + If device implementations use removable storage to satisfy the above requirements, they: + </p> + <ul> + <li>[C-1-1] MUST implement a toast or pop-up user interface warning the user when there is no storage medium inserted in the slot. + </li> + <li>[C-1-2] MUST include a FAT-formatted storage medium (e.g. SD card) or show on the box and other material available at time of purchase that the storage medium has to be purchased separately. + </li> + </ul> + <p> + If device implementations use a protion of the non-removable storage to satisfy the above requirements, they: + </p> + <ul> + <li>SHOULD use the AOSP implementation of the internal application shared storage. + </li> + <li>MAY share the storage space with the application private data. + </li> + </ul> + <p> + If device implementations include multiple shared storage paths (such as both an SD card slot and shared internal storage), they: + </p> + <ul> + <li>[C-3-1] MUST allow only pre-installed and privileged Android applications with the <code>WRITE_EXTERNAL_STORAGE</code> permission to write to the secondary external storage, except when writing to their package-specific directories or within the <code>URI</code> returned by firing the <code>ACTION_OPEN_DOCUMENT_TREE</code> intent. + </li> + </ul> + <p> + If device implementations have a USB port with USB peripheral mode support, they: + </p> + <ul> + <li>[C-3-1] MUST provide a mechanism to access the data on the application shared storage from a host computer. + </li> + <li>SHOULD expose content from both storage paths transparently through Android’s media scanner service and <code>android.provider.MediaStore</code>. + </li> + <li>MAY use USB mass storage, but SHOULD use Media Transfer Protocol to satisfy this requirement. + </li> + </ul> + <p> + If device implementations have a USB port with USB peripheral mode and support Media Transfer Protocol, they: + </p> + <ul> + <li>SHOULD be compatible with the reference Android MTP host, <a href="http://www.android.com/filetransfer">Android File Transfer</a>. + </li> + <li>SHOULD report a USB device class of 0x00. + </li> + <li>SHOULD report a USB interface name of 'MTP'. + </li> + </ul> + <h4 id="7_6_3_adoptable_storage"> + 7.6.3. Adoptable Storage + </h4> + <p> + If the device is expected to be mobile in nature unlike Television, device implementations are: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to implement the adoptable storage in a long-term stable location, since accidentally disconnecting them can cause data loss/corruption. + </li> + </ul> + <p> + If the removable storage device port is in a long-term stable location, such as within the battery compartment or other protective cover, device implementations are: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to implement <a href="http://source.android.com/devices/storage/adoptable.html">adoptable storage</a>. + </li> + </ul> + <h3 id="7_7_usb"> + 7.7. USB + </h3> + <p> + If device implementations have a USB port, they: + </p> + <ul> + <li>SHOULD support USB peripheral mode and SHOULD support USB host mode. + </li> + </ul> + <h4 id="7_7_1_usb_peripheral_mode"> + 7.7.1. USB peripheral mode + </h4> + <p> + If device implementations include a USB port supporting peripheral mode: + </p> + <ul> + <li>[C-1-1] The port MUST be connectable to a USB host that has a standard type-A or type-C USB port. + </li> + <li>[C-1-2] MUST report the correct value of <code>iSerialNumber</code> in USB standard device descriptor through <code>android.os.Build.SERIAL</code>. + </li> + <li>[C-1-3] MUST detect 1.5A and 3.0A chargers per the Type-C resistor standard and MUST detect changes in the advertisement if they support Type-C USB. + </li> + <li>[SR] The port SHOULD use micro-B, micro-AB or Type-C USB form factor. Existing and new Android devices are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will be able to upgrade to the future platform releases. + </li> + <li>[SR] The port SHOULD be located on the bottom of the device (according to natural orientation) or enable software screen rotation for all apps (including home screen), so that the display draws correctly when the device is oriented with the port at bottom. Existing and new Android devices are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will be able to upgrade to future platform releases. + </li> + <li>[SR] SHOULD implement support to draw 1.5 A current during HS chirp and traffic as specified in the <a href="http://www.usb.org/developers/docs/devclass_docs/BCv1.2_070312.zip">USB Battery Charging specification, revision 1.2</a>. Existing and new Android devices are <strong>STRONGLY RECOMMENDED to meet these requirements</strong> so they will be able to upgrade to the future platform releases. + </li> + <li>[SR] STRONGLY RECOMMENDED to not support proprietary charging methods that modify Vbus voltage beyond default levels, or alter sink/source roles as such may result in interoperability issues with the chargers or devices that support the standard USB Power Delivery methods. While this is called out as "STRONGLY RECOMMENDED", in future Android versions we might REQUIRE all type-C devices to support full interoperability with standard type-C chargers. + </li> + <li>[SR] STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping when they support Type-C USB and USB host mode. + </li> + <li>SHOULD support Power Delivery for high-voltage charging and support for Alternate Modes such as display out. + </li> + <li>SHOULD implement the Android Open Accessory (AOA) API and specification as documented in the Android SDK documentation. + </li> + </ul> + <p> + If device implementations including a USB port, implement the AOA specification, they: + </p> + <ul> + <li>[C-2-1] MUST declare support for the hardware feature <a href="http://developer.android.com/guide/topics/connectivity/usb/accessory.html"><code>android.hardware.usb.accessory</code></a>. + </li> + <li>[C-2-2] The USB mass storage class MUST include the string "android" at the end of the interface description <code>iInterface</code> string of the USB mass storage + </li> + <li>SHOULD NOT implement <a href="https://source.android.com/devices/accessories/aoa2#audio-support">AOAv2 audio</a> documented in the Android Open Accessory Protocol 2.0 documentation. AOAv2 audio is deprecated as of Android version 8.0 (API level 26). + </li> + </ul> + <h4 id="7_7_2_usb_host_mode"> + 7.7.2. USB host mode + </h4> + <p> + If device implementations include a USB port supporting host mode, they: + </p> + <ul> + <li>[C-1-1] MUST implement the Android USB host API as documented in the Android SDK and MUST declare support for the hardware feature <a href="http://developer.android.com/guide/topics/connectivity/usb/host.html"><code>android.hardware.usb.host</code></a>. + </li> + <li>[C-1-2] MUST implement support to connect standard USB peripherals, in other words, they MUST either: + <ul> + <li>Have an on-device type C port or ship with cable(s) adapting an on-device proprietary port to a standard USB type-C port (USB Type-C device). + </li> + <li>Have an on-device type A or ship with cable(s) adapting an on-device proprietary port to a standard USB type-A port. + </li> + <li>Have an on-device micro-AB port, which SHOULD ship with a cable adapting to a standard type-A port. + </li> + </ul> + </li> + <li>[C-1-3] MUST NOT ship with an adapter converting from USB type A or micro-AB ports to a type-C port (receptacle). + </li> + <li>[SR] STRONGLY RECOMMENDED to implement the <a href="http://developer.android.com/reference/android/hardware/usb/UsbConstants.html#USB_CLASS_AUDIO">USB audio class</a> as documented in the Android SDK documentation. + </li> + <li>SHOULD support charging the connected USB peripheral device while in host mode; advertising a source current of at least 1.5A as specified in the Termination Parameters section of the <a href="http://www.usb.org/developers/docs/usb_31_021517.zip">USB Type-C Cable and Connector Specification Revision 1.2</a> for USB Type-C connectors or using Charging Downstream Port(CDP) output current range as specified in the <a href="http://www.usb.org/developers/docs/devclass_docs/BCv1.2_070312.zip">USB Battery Charging specifications, revision 1.2</a> for Micro-AB connectors. + </li> + <li>SHOULD implement and support USB Type-C standards. + </li> + </ul> + <p> + If device implementations include a USB port supporting host mode and the USB audio class, they: + </p> + <ul> + <li>[C-2-1] MUST support the <a href="https://developer.android.com/reference/android/hardware/usb/UsbConstants.html#USB_CLASS_HID">USB HID class</a> + </li> + <li>[C-2-2] MUST support the detection and mapping of the following HID data fields specified in the <a href="http://www.usb.org/developers/hidpage/Hut1_12v2.pdf">USB HID Usage Tables</a> and the <a href="http://www.usb.org/developers/hidpage/Voice_Command_Usage.pdf">Voice Command Usage Request</a> to the <a href="https://developer.android.com/reference/android/view/KeyEvent.html"><code>KeyEvent</code></a> constants as below: + <ul> + <li>Usage Page (0xC) Usage ID (0x0CD): <code>KEYCODE_MEDIA_PLAY_PAUSE</code> + </li> + <li>Usage Page (0xC) Usage ID (0x0E9): <code>KEYCODE_VOLUME_UP</code> + </li> + <li>Usage Page (0xC) Usage ID (0x0EA): <code>KEYCODE_VOLUME_DOWN</code> + </li> + <li>Usage Page (0xC) Usage ID (0x0CF): <code>KEYCODE_VOICE_ASSIST</code> + </li> + </ul> + </li> + </ul> + <p> + If device implementations include a USB port supporting host mode and the Storage Access Framework (SAF), they: + </p> + <ul> + <li>[C-3-1] MUST recognize any remotely connected MTP (Media Transfer Protocol) devices and make their contents accessible through the <code>ACTION_GET_CONTENT</code>, <code>ACTION_OPEN_DOCUMENT</code>, and <code>ACTION_CREATE_DOCUMENT</code> intents. . + </li> + </ul> + <p> + If device implementations include a USB port supporting host mode and USB Type-C, they: + </p> + <ul> + <li>[C-4-1] MUST implement Dual Role Port functionality as defined by the USB Type-C specification (section 4.5.1.3.3). + </li> + <li>[SR] STRONGLY RECOMMENDED to support DisplayPort, SHOULD support USB SuperSpeed Data Rates, and are STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping. + </li> + <li>[SR] STRONGLY RECOMMENDED to NOT support Audio Adapter Accessory Mode as described in the Appendix A of the <a href="http://www.usb.org/developers/docs/">USB Type-C Cable and Connector Specification Revision 1.2</a>. + </li> + <li>SHOULD implement the Try.* model that is most appropriate for the device form factor. For example a handheld device SHOULD implement the Try.SNK model. + </li> + </ul> + <h3 id="7_8_audio"> + 7.8. Audio + </h3> + <h4 id="7_8_1_microphone"> + 7.8.1. Microphone + </h4> + <p> + If device implementations include a microphone, they: + </p> + <ul> + <li>[C-1-1] MUST report the <code>android.hardware.microphone</code> feature constant. + </li> + <li>[C-1-2] MUST meet the audio recording requirements in <a href="#5_4_audio_recording">section 5.4</a>. + </li> + <li>[C-1-3] MUST meet the audio latency requirements in <a href="#5_6_audio_latency">section 5.6</a>. + </li> + <li>[SR] STRONGLY RECOMMENDED to support near-ultrasound recording as described in <a href="#7_8_3_near_ultrasound">section 7.8.3</a>. + </li> + </ul> + <p> + If device implementations omit a microphone, they: + </p> + <ul> + <li>[C-2-1] MUST NOT report the <code>android.hardware.microphone</code> feature constant. + </li> + <li>[C-2-2] MUST implement the audio recording API at least as no-ops, per <a href="#7_hardware_compatibility">section 7</a>. + </li> + </ul> + <h4 id="7_8_2_audio_output"> + 7.8.2. Audio Output + </h4> + <p> + If device implementations include a speaker or an audio/multimedia output port for an audio output peripheral such as a 4 conductor 3.5mm audio jack or USB host mode port using <a href="https://source.android.com/devices/audio/usb#audioClass">USB audio class</a>, they: + </p> + <ul> + <li>[C-1-1] MUST report the <code>android.hardware.audio.output</code> feature constant. + </li> + <li>[C-1-2] MUST meet the audio playback requirements in <a href="#5_5_audio_playback">section 5.5</a>. + </li> + <li>[C-1-3] MUST meet the audio latency requirements in <a href="#5_6_audio_latency">section 5.6</a>. + </li> + <li>[SR] STRONGLY RECOMMENDED to support near-ultrasound playback as described in <a href="#7_8_3_near_ultrasound">section 7.8.3</a>. + </li> + </ul> + <p> + If device implementations do not include a speaker or audio output port, they: + </p> + <ul> + <li>[C-2-1] MUST NOT report the <code>android.hardware.audio.output</code> feature. + </li> + <li>[C-2-2] MUST implement the Audio Output related APIs as no-ops at least. + </li> + </ul> + <p> + For the purposes of this section, an "output port" is a <a href="https://en.wikipedia.org/wiki/Computer_port_%28hardware%29">physical interface</a> such as a 3.5mm audio jack, HDMI, or USB host mode port with USB audio class. Support for audio output over radio-based protocols such as Bluetooth, WiFi, or cellular network does not qualify as including an "output port". + </p> + <h5 id="7_8_2_1_analog_audio_ports"> + 7.8.2.1. Analog Audio Ports + </h5> + <p> + In order to be compatible with the <a href="http://source.android.com/accessories/headset-spec.html">headsets and other audio accessories</a> using the 3.5mm audio plug across the Android ecosystem, if a device implementation includes one or more analog audio ports, at least one of the audio port(s) SHOULD be a 4 conductor 3.5mm audio jack. + </p> + <p> + If device implementations have a 4 conductor 3.5mm audio jack, they: + </p> + <ul> + <li>[C-1-1] MUST support audio playback to stereo headphones and stereo headsets with a microphone. + </li> + <li>[C-1-2] MUST support TRRS audio plugs with the CTIA pin-out order. + </li> + <li>[C-1-3] MUST support the detection and mapping to the keycodes for the following 3 ranges of equivalent impedance between the microphone and ground conductors on the audio plug: + <ul> + <li> + <strong>70 ohm or less</strong>: <code>KEYCODE_HEADSETHOOK</code> + </li> + <li> + <strong>210-290 ohm</strong>: <code>KEYCODE_VOLUME_UP</code> + </li> + <li> + <strong>360-680 ohm</strong>: <code>KEYCODE_VOLUME_DOWN</code> + </li> + </ul> + </li> + <li>[C-1-4] MUST trigger <code>ACTION_HEADSET_PLUG</code> upon a plug insert, but only after all contacts on plug are touching their relevant segments on the jack. + </li> + <li>[C-1-5] MUST be capable of driving at least 150mV ± 10% of output voltage on a 32 ohm speaker impedance. + </li> + <li>[C-1-6] MUST have a microphone bias voltage between 1.8V ~ 2.9V. + </li> + <li>[SR] STRONGLY RECOMMENDED to detect and map to the keycode for the following range of equivalent impedance between the microphone and ground conductors on the audio plug: + <ul> + <li> + <strong>110-180 ohm:</strong> <code>KEYCODE_VOICE_ASSIST</code> + </li> + </ul> + </li> + <li>SHOULD support audio plugs with the OMTP pin-out order. + </li> + <li>SHOULD support audio recording from stereo headsets with a microphone. + </li> + </ul> + <p> + If device implementations have a 4 conductor 3.5mm audio jack and support a microphone, and broadcast the <code>android.intent.action.HEADSET_PLUG</code> with the extra value microphone set as 1, they: + </p> + <ul> + <li>[C-2-1] MUST support the detection of microphone on the plugged in audio accessory. + </li> + </ul> + <h4 id="7_8_3_near-ultrasound"> + 7.8.3. Near-Ultrasound + </h4> + <p> + Near-Ultrasound audio is the 18.5 kHz to 20 kHz band. + </p> + <p> + Device implementations: + </p> + <ul> + <li>MUST correctly report the support of near-ultrasound audio capability via the <a href="http://developer.android.com/reference/android/media/AudioManager.html#getProperty%28java.lang.String%29">AudioManager.getProperty</a> API as follows: + </li> + </ul> + <p> + If <a href="http://developer.android.com/reference/android/media/AudioManager.html#PROPERTY_SUPPORT_MIC_NEAR_ULTRASOUND"><code>PROPERTY_SUPPORT_MIC_NEAR_ULTRASOUND</code></a> is "true", the following requirements MUST be met by the <code>VOICE_RECOGNITION</code> and <code>UNPROCESSED</code> audio sources: + </p> + <ul> + <li>[C-1-1] The microphone's mean power response in the 18.5 kHz to 20 kHz band MUST be no more than 15 dB below the response at 2 kHz. + </li> + <li>[C-1-2] The microphone's unweighted signal to noise ratio over 18.5 kHz to 20 kHz for a 19 kHz tone at -26 dBFS MUST be no lower than 50 dB. + </li> + </ul> + <p> + If <a href="http://developer.android.com/reference/android/media/AudioManager.html#PROPERTY_SUPPORT_SPEAKER_NEAR_ULTRASOUND"><code>PROPERTY_SUPPORT_SPEAKER_NEAR_ULTRASOUND</code></a> is "true": + </p> + <ul> + <li>[C-2-1] The speaker's mean response in 18.5 kHz - 20 kHz MUST be no lower than 40 dB below the response at 2 kHz. + </li> + </ul> + <h3 id="7_9_virtual_reality"> + 7.9. Virtual Reality + </h3> + <p> + Android includes APIs and facilities to build "Virtual Reality" (VR) applications including high quality mobile VR experiences. Device implementations MUST properly implement these APIs and behaviors, as detailed in this section. + </p> + <h4 id="7_9_1_virtual_reality_mode"> + 7.9.1. Virtual Reality Mode + </h4> + <p> + Android includes support for <a href="https://developer.android.com/reference/android/app/Activity.html#setVrModeEnabled%28boolean,%20android.content.ComponentName%29">VR Mode</a>, a feature which handles stereoscopic rendering of notifications and disables monocular system UI components while a VR application has user focus. + </p> + <h4 id="7_9_2_virtual_reality_high_performance"> + 7.9.2. Virtual Reality High Performance + </h4> + <p> + If device implementations identify the support of high performance VR for longer user periods through the <code>android.hardware.vr.high_performance</code> feature flag, they: + </p> + <ul> + <li>[C-1-1] MUST have at least 2 physical cores. + </li> + <li>[C-1-2] MUST declare <code>android.software.vr.mode feature</code>. + </li> + <li>[C-1-3] MUST support sustained performance mode. + </li> + <li>[C-1-4] MUST support OpenGL ES 3.2. + </li> + <li>[C-1-5] MUST support Vulkan Hardware Level 0 and SHOULD support Vulkan Hardware Level 1. + </li> + <li>[C-1-6] MUST implement <a href="https://www.khronos.org/registry/EGL/extensions/KHR/EGL_KHR_mutable_render_buffer.txt"><code>EGL_KHR_mutable_render_buffer</code></a>, <a href="https://www.khronos.org/registry/EGL/extensions/ANDROID/EGL_ANDROID_front_buffer_auto_refresh.txt"><code>EGL_ANDROID_front_buffer_auto_refresh</code></a>, <a href="https://www.khronos.org/registry/EGL/extensions/ANDROID/EGL_ANDROID_get_native_client_buffer.txt"><code>EGL_ANDROID_get_native_client_buffer</code></a>, <a href="https://www.khronos.org/registry/EGL/extensions/KHR/EGL_KHR_fence_sync.txt"><code>EGL_KHR_fence_sync</code></a>, <a href="https://www.khronos.org/registry/EGL/extensions/KHR/EGL_KHR_wait_sync.txt"><code>EGL_KHR_wait_sync</code></a>, <a href="https://www.khronos.org/registry/EGL/extensions/IMG/EGL_IMG_context_priority.txt"><code>EGL_IMG_context_priority</code></a>, <a href="https://www.khronos.org/registry/EGL/extensions/EXT/EGL_EXT_protected_content.txt"><code>EGL_EXT_protected_content</code></a>, and expose the extensions in the list of available EGL extensions. + </li> + <li>[C-1-7] The GPU and display MUST be able to synchronize access to the shared front buffer such that alternating-eye rendering of VR content at 60fps with two render contexts will be displayed with no visible tearing artifacts. + </li> + <li>[C-1-8] MUST implement <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_multisampled_render_to_texture.txt"><code>GL_EXT_multisampled_render_to_texture</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview.txt"><code>GL_OVR_multiview</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview2.txt"><code>GL_OVR_multiview2</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview_multisampled_render_to_texture.txt"><code>GL_OVR_multiview_multisampled_render_to_texture</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_protected_textures.txt"><code>GL_EXT_protected_textures</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_EGL_image_array.txt"><code>GL_EXT_EGL_image_array</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_external_buffer.txt"><code>GL_EXT_external_buffer</code></a>, and expose the extensions in the list of available GL extensions. + </li> + <li>[C-1-9] MUST implement support for <a href="https://developer.android.com/ndk/reference/hardware__buffer_8h.html"><code>AHardwareBuffer</code></a> flags <code>AHARDWAREBUFFER_USAGE_GPU_DATA_BUFFER</code> and <code>AHARDWAREBUFFER_USAGE_SENSOR_DIRECT_DATA</code> as described in the NDK. + </li> + <li>[C-1-10] MUST implement support for <code>AHardwareBuffers</code> with more than one layer. + </li> + <li>[C-1-11] MUST support H.264 decoding at least 3840x2160@30fps-40Mbps (equivalent to 4 instances of 1920x1080@30fps-10Mbps or 2 instances of 1920x1080@60fps-20Mbps). + </li> + <li>[C-1-12] MUST support HEVC and VP9, MUST be capable to decode at least 1920x1080@30fps-10Mbps and SHOULD be capable to decode 3840x2160@30fps-20Mbps (equivalent to 4 instances of 1920x1080@30fps-5Mbps). + </li> + <li>[C-1-13] MUST support <code>HardwarePropertiesManager.getDeviceTemperatures</code> API and return accurate values for skin temperature. + </li> + <li>[C-1-14] MUST have an embedded screen, and its resolution MUST be at least be FullHD(1080p) and STRONGLY RECOMMENDED TO BE be QuadHD (1440p) or higher. + </li> + <li>[C-1-15] The display MUST update at least 60 Hz while in VR Mode. + </li> + <li>[C-1-16] The display latency (as measured on Gray-to-Gray, White-to-Black, and Black-to-White switching time) MUST be ≤ 6 milliseconds. + </li> + <li>[C-1-17] The display MUST support a low-persistence mode with ≤ 5 milliseconds persistence, persistence being defined as the amount of time for which a pixel is emitting light. + </li> + <li>[C-1-18] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension <a href="#7_4_3_bluetooth">section 7.4.3</a>. + </li> + <li>[C-1-19] MUST support and properly report <a href='https://developer.android.com/reference/android/hardware/Sensor.html#isDirectChannelTypeSupported%28int%29"'>Direct Channel Type</a> for all of the following default sensor types: + <ul> + <li> + <code>TYPE_ACCELEROMETER</code> + </li> + <li> + <code>TYPE_ACCELEROMETER_UNCALIBRATED</code> + </li> + <li> + <code>TYPE_GYROSCOPE</code> + </li> + <li> + <code>TYPE_GYROSCOPE_UNCALIBRATED</code> + </li> + <li> + <code>TYPE_MAGNETIC_FIELD</code> + </li> + <li> + <code>TYPE_MAGNETIC_FIELD_UNCALIBRATED</code> + </li> + </ul> + </li> + <li>[C-1-20] MUST support the <a href="https://developer.android.com/reference/android/hardware/SensorDirectChannel.html#TYPE_HARDWARE_BUFFER"><code>TYPE_HARDWARE_BUFFER</code></a> direct channel type for all Direct Channel Types listed above. + </li> + <li>[SR] Are STRONGLY RECOMMENDED to support <code>android.hardware.sensor.hifi_sensors</code> feature and MUST meet the gyroscope, accelerometer, and magnetometer related requirements for <code>android.hardware.hifi_sensors</code>. + </li> + <li>MAY provide an exclusive core to the foreground application and MAY support the <code>Process.getExclusiveCores</code> API to return the numbers of the cpu cores that are exclusive to the top foreground application. If exclusive core is supported then the core MUST not allow any other userspace processes to run on it (except device drivers used by the application), but MAY allow some kernel processes to run as necessary. + </li> + </ul> + <h2 id="8_performance_and_power"> + 8. Performance and Power + </h2> + <p> + Some minimum performance and power criteria are critical to the user experience and impact the baseline assumptions developers would have when developing an app. + </p> + <h3 id="8_1_user_experience_consistency"> + 8.1. User Experience Consistency + </h3> + <p> + A smooth user interface can be provided to the end user if there are certain minimum requirements to ensure a consistent frame rate and response times for applications and games. Device implementations, depending on the device type, MAY have measurable requirements for the user interface latency and task switching as described in <a href="#2_device-types">section 2</a>. + </p> + <h3 id="8_2_file_i/o_access_performance"> + 8.2. File I/O Access Performance + </h3> + <p> + Providing a common baseline for a consistent file access performance on the application private data storage (<code>/data</code> partition) allows app developers to set a proper expectation that would help their software design. Device implementations, depending on the device type, MAY have certain requirements described in <a href="#2_device-type">section 2</a> for the following read and write operations: + </p> + <ul> + <li> + <strong>Sequential write performance</strong>. Measured by writing a 256MB file using 10MB write buffer. + </li> + <li> + <strong>Random write performance</strong>. Measured by writing a 256MB file using 4KB write buffer. + </li> + <li> + <strong>Sequential read performance</strong>. Measured by reading a 256MB file using 10MB write buffer. + </li> + <li> + <strong>Random read performance</strong>. Measured by reading a 256MB file using 4KB write buffer. + </li> + </ul> + <h3 id="8_3_power-saving_modes"> + 8.3. Power-Saving Modes + </h3> + <p> + Android includes App Standby and Doze power-saving modes to optimize battery usage. <em>[SR] All Apps exempted from these modes are STRONGLY RECOMMENDED to be made visible to the end user.</em> [SR] The triggering, maintenance, wakeup algorithms and the use of global system settings of these power-saving modes are STRONGLY RECOMMENDED NOT to deviate from the Android Open Source Project. + </p> + <p> + In addition to the power-saving modes, Android device implementations MAY implement any or all of the 4 sleeping power states as defined by the Advanced Configuration and Power Interface (ACPI). + </p> + <p> + If device implementations implements S3 and S4 power states as defined by the ACPI, they: + </p> + <ul> + <li>[C-1-1] MUST only enter these states when closing a lid that is physically part of the device. + </li> + </ul> + <h3 id="8_4_power_consumption_accounting"> + 8.4. Power Consumption Accounting + </h3> + <p> + A more accurate accounting and reporting of the power consumption provides the app developer both the incentives and the tools to optimize the power usage pattern of the application. + </p> + <p> + Device implementations: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to provide a per-component power profile that defines the <a href="http://source.android.com/devices/tech/power/values.html">current consumption value</a> for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site. + </li> + <li>[SR] STRONGLY RECOMMENDED to report all power consumption values in milliampere hours (mAh). + </li> + <li>[SR] STRONGLY RECOMMENDED to report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the <code>uid_cputime</code> kernel module implementation. + </li> + <li>[SR] STRONGLY RECOMMENDED to make this power usage available via the <a href="http://source.android.com/devices/tech/power/batterystats.html"><code>adb shell dumpsys batterystats</code></a> shell command to the app developer. + </li> + <li>SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application. + </li> + </ul> + <h3 id="8_5_consistent_performance"> + 8.5. Consistent Performance + </h3> + <p> + Performance can fluctuate dramatically for high-performance long-running apps, either because of the other apps running in the background or the CPU throttling due to temperature limits. Android includes programmatic interfaces so that when the device is capable, the top foreground application can request that the system optimize the allocation of the resources to address such fluctuations. + </p> + <p> + Device implementations: + </p> + <ul> + <li> + <p> + [C-0-1] MUST report the support of Sustained Performance Mode accurately through the <a href="https://developer.android.com/reference/android/os/PowerManager.html#isSustainedPerformanceModeSupported%28%29"><code>PowerManager.isSustainedPerformanceModeSupported()</code></a> API method. + </p> + </li> + <li> + <p> + SHOULD support Sustained Performance Mode. + </p> + </li> + </ul> + <p> + If device implementations report support of Sustained Performance Mode, they: + </p> + <ul> + <li>[C-1-1] MUST provide the top foreground application a consistent level of performance for at least 30 minutes, when the app requests it. + </li> + <li>[C-1-2] MUST honor the <a href="https://developer.android.com/reference/android/view/Window.html#setSustainedPerformanceMode%28boolean%29"><code>Window.setSustainedPerformanceMode()</code></a> API and other related APIs. + </li> + </ul> + <p> + If device implementations include two or more CPU cores, they: + </p> + <ul> + <li>SHOULD provide at least one exclusive core that can be reserved by the top foreground application. + </li> + </ul> + <p> + If device implementations support reserving one exclusive core for the top foreground application, they: + </p> + <ul> + <li>[C-2-1] MUST report through the <a href="https://developer.android.com/reference/android/os/Process.html#getExclusiveCores%28%29"><code>Process.getExclusiveCores()</code></a> API method the ID numbers of the exclusive cores that can be reserved by the top foreground application. + </li> + <li>[C-2-2] MUST not allow any user space processes except the device drivers used by the application to run on the exclusive cores, but MAY allow some kernel processes to run as necessary. + </li> + </ul> + <p> + If device implementations do not support an exclusive core, they: + </p> + <ul> + <li>[C-3-1] MUST return an empty list through the <a href="https://developer.android.com/reference/android/os/Process.html#getExclusiveCores%28%29"><code>Process.getExclusiveCores()</code></a> API method. + </li> + </ul> + <h2 id="9_security_model_compatibility"> + 9. Security Model Compatibility + </h2> + <p> + Device implementations: + </p> + <ul> + <li> + <p> + [C-0-1] MUST implement a security model consistent with the Android platform security model as defined in <a href="http://developer.android.com/guide/topics/security/permissions.html">Security and Permissions reference document</a> in the APIs in the Android developer documentation. + </p> + </li> + <li> + <p> + [C-0-2] MUST support installation of self-signed applications without requiring any additional permissions/certificates from any third parties/authorities. Specifically, compatible devices MUST support the security mechanisms described in the follow subsections. + </p> + </li> + </ul> + <h3 id="9_1_permissions"> + 9.1. Permissions + </h3> + <p> + Device implementations: + </p> + <ul> + <li> + <p> + [C-0-1] MUST support the <a href="http://developer.android.com/guide/topics/security/permissions.html">Android permissions model</a> as defined in the Android developer documentation. Specifically, they MUST enforce each permission defined as described in the SDK documentation; no permissions may be omitted, altered, or ignored. + </p> + </li> + <li> + <p> + MAY add additional permissions, provided the new permission ID strings are not in the <code>android.\*</code> namespace. + </p> + </li> + <li> + <p> + [C-0-2] Permissions with a <code>protectionLevel</code> of <a href="https://developer.android.com/reference/android/content/pm/PermissionInfo.html#PROTECTION&lowbar;FLAG&lowbar;PRIVILEGED"><code>PROTECTION_FLAG_PRIVILEGED</code></a> MUST only be granted to apps preloaded in the privileged path(s) of the system image and within the subset of the explicitly whitelisted permissions for each app. The AOSP implementation meets this requirement by reading and honoring the whitelisted permissions for each app from the files in the <code>etc/permissions/</code> path and using the <code>system/priv-app</code> path as the privileged path. + </p> + </li> + </ul> + <p> + Permissions with a protection level of dangerous are runtime permissions. Applications with <code>targetSdkVersion</code> > 22 request them at runtime. + </p> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-3] MUST show a dedicated interface for the user to decide whether to grant the requested runtime permissions and also provide an interface for the user to manage runtime permissions. + </li> + <li>[C-0-4] MUST have one and only one implementation of both user interfaces. + </li> + <li>[C-0-5] MUST NOT grant any runtime permissions to preinstalled apps unless: + </li> + <li>the user's consent can be obtained before the application uses it + </li> + <li>the runtime permissions are associated with an intent pattern for which the preinstalled application is set as the default handler + </li> + </ul> + <p> + If device implementations include a pre-installed app or wish to allow third-party apps to access the usage statistics, they: + </p> + <ul> + <li>[C-1-1] are STRONGLY RECOMMENDED provide user-accessible mechanism to grant or revoke access to the usage stats in response to the <a href="https://developer.android.com/reference/android/provider/Settings.html#ACTION&lowbar;USAGE&lowbar;ACCESS&lowbar;SETTINGS"><code>android.settings.ACTION_USAGE_ACCESS_SETTINGS</code></a> intent for apps that declare the <code>android.permission.PACKAGE_USAGE_STATS</code> permission. + </li> + </ul> + <p> + If device implementations intend to disallow any apps, including pre-installed apps, from accessing the usage statistics, they: + </p> + <ul> + <li>[C-2-1] MUST still have an activity that handles the <a href="https://developer.android.com/reference/android/provider/Settings.html#ACTION&lowbar;USAGE&lowbar;ACCESS&lowbar;SETTINGS"><code>android.settings.ACTION_USAGE_ACCESS_SETTINGS</code></a> intent pattern but MUST implement it as a no-op, that is to have an equivalent behavior as when the user is declined for access. + </li> + </ul> + <h3 id="9_2_uid_and_process_isolation"> + 9.2. UID and Process Isolation + </h3> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST support the Android application sandbox model, in which each application runs as a unique Unixstyle UID and in a separate process. + </li> + <li>[C-0-2] MUST support running multiple applications as the same Linux user ID, provided that the applications are properly signed and constructed, as defined in the <a href="http://developer.android.com/guide/topics/security/permissions.html">Security and Permissions reference</a>. + </li> + </ul> + <h3 id="9_3_filesystem_permissions"> + 9.3. Filesystem Permissions + </h3> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST support the Android file access permissions model as defined in the <a href="http://developer.android.com/guide/topics/security/permissions.html">Security and Permissions reference</a>. + </li> + </ul> + <h3 id="9_4_alternate_execution_environments"> + 9.4. Alternate Execution Environments + </h3> + <p> + Device implementations MUST keep consistency of the Android security and permission model, even if they include runtime environments that execute applications using some other software or technology than the Dalvik Executable Format or native code. In other words: + </p> + <ul> + <li> + <p> + [C-0-1] Alternate runtimes MUST themselves be Android applications, and abide by the standard Android security model, as described elsewhere in <a href="#9_security_model_compatibility">section 9</a>. + </p> + </li> + <li> + <p> + [C-0-2] Alternate runtimes MUST NOT be granted access to resources protected by permissions not requested in the runtime’s <code>AndroidManifest.xml</code> file via the <<code>uses-permission</code>> mechanism. + </p> + </li> + <li> + <p> + [C-0-3] Alternate runtimes MUST NOT permit applications to make use of features protected by Android permissions restricted to system applications. + </p> + </li> + <li> + <p> + [C-0-4] Alternate runtimes MUST abide by the Android sandbox model and installed applications using an alternate runtime MUST NOT reuse the sandbox of any other app installed on the device, except through the standard Android mechanisms of shared user ID and signing certificate. + </p> + </li> + <li> + <p> + [C-0-5] Alternate runtimes MUST NOT launch with, grant, or be granted access to the sandboxes corresponding to other Android applications. + </p> + </li> + <li> + <p> + [C-0-6] Alternate runtimes MUST NOT be launched with, be granted, or grant to other applications any privileges of the superuser (root), or of any other user ID. + </p> + </li> + <li> + <p> + [C-0-7] When the <code>.apk</code> files of alternate runtimes are included in the system image of device implementations, it MUST be signed with a key distinct from the key used to sign other applications included with the device implementations. + </p> + </li> + <li> + <p> + [C-0-8] When installing applications, alternate runtimes MUST obtain user consent for the Android permissions used by the application. + </p> + </li> + <li> + <p> + [C-0-9] When an application needs to make use of a device resource for which there is a corresponding Android permission (such as Camera, GPS, etc.), the alternate runtime MUST inform the user that the application will be able to access that resource. + </p> + </li> + <li> + <p> + [C-0-10] When the runtime environment does not record application capabilities in this manner, the runtime environment MUST list all permissions held by the runtime itself when installing any application using that runtime. + </p> + </li> + <li> + <p> + Alternate runtimes SHOULD install apps via the <code>PackageManager</code> into separate Android sandboxes (Linux user IDs, etc.). + </p> + </li> + <li> + <p> + Alternate runtimes MAY provide a single Android sandbox shared by all applications using the alternate runtime. + </p> + </li> + </ul> + <h3 id="9_5_multi-user_support"> + 9.5. Multi-User Support + </h3> + <p> + Android includes <a href="http://developer.android.com/reference/android/os/UserManager.html">support for multiple users</a> and provides support for full user isolation. + </p> + <ul> + <li>Device implementations MAY but SHOULD NOT enable multi-user if they use <a href="http://developer.android.com/reference/android/os/Environment.html">removable media</a> for primary external storage. + </li> + </ul> + <p> + If device implementations include multiple users, they: + </p> + <ul> + <li>[C-1-1] MUST meet the following requirements related to <a href="http://source.android.com/devices/storage/traditional.html">multi-user support</a>. + </li> + <li>[C-1-2] MUST, for each user, implement a security model consistent with the Android platform security model as defined in <a href="http://developer.android.com/guide/topics/security/permissions.html">Security and Permissions reference document</a> in the APIs. + </li> + <li>[C-1-3] MUST have separate and isolated shared application storage (a.k.a. <code>/sdcard</code>) directories for each user instance. + </li> + <li>[C-1-4] MUST ensure that applications owned by and running on behalf a given user cannot list, read, or write to the files owned by any other user, even if the data of both users are stored on the same volume or filesystem. + </li> + <li>[C-1-5] MUST encrypt the contents of the SD card when multiuser is enabled using a key stored only on non-removable media accessible only to the system if device implementations use removable media for the external storage APIs. As this will make the media unreadable by a host PC, device implementations will be required to switch to MTP or a similar system to provide host PCs with access to the current user’s data. + </li> + </ul> + <p> + If device implementations include multiple users and do not declare the <code>android.hardware.telephony</code> feature flag, they: + </p> + <ul> + <li>[C-2-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments. + </li> + </ul> + <p> + If device implementations include multiple users and declare the <code>android.hardware.telephony</code> feature flag, they: + </p> + <ul> + <li>[C-3-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS. + </li> + </ul> + <h3 id="9_6_premium_sms_warning"> + 9.6. Premium SMS Warning + </h3> + <p> + Android includes support for warning users of any outgoing <a href="http://en.wikipedia.org/wiki/Short_code">premium SMS message</a>. Premium SMS messages are text messages sent to a service registered with a carrier that may incur a charge to the user. + </p> + <p> + If device implementations declare support for <code>android.hardware.telephony</code>, they: + </p> + <ul> + <li>[C-1-1] MUST warn users before sending a SMS message to numbers identified by regular expressions defined in <code>/data/misc/sms/codes.xml</code> file in the device. The upstream Android Open Source Project provides an implementation that satisfies this requirement. + </li> + </ul> + <h3 id="9_7_kernel_security_features"> + 9.7. Kernel Security Features + </h3> + <p> + The Android Sandbox includes features that use the Security-Enhanced Linux (SELinux) mandatory access control (MAC) system, seccomp sandboxing, and other security features in the Linux kernel. Device implementations: + </p> + <ul> + <li>[C-0-1] MUST maintain compatibility with existing applications, even when SELinux or any other security features are implemented below the Android framework. + </li> + <li>[C-0-2] MUST NOT have a visible user interface when a security violation is detected and successfully blocked by the security feature implemented below the Android framework, but MAY have a visible user interface when an unblocked security violation occurs resulting in a successful exploit. + </li> + <li>[C-0-3] MUST NOT make SELinux or any other security features implemented below the Android framework configurable to the user or app developer. + </li> + <li>[C-0-4] MUST NOT allow an application that can affect another application through an API (such as a Device Administration API) to configure a policy that breaks compatibility. + </li> + <li>[C-0-5] MUST split the media framework into multiple processes so that it is possible to more narrowly grant access for each process as <a href="https://source.android.com/devices/media/framework-hardening.html#arch_changes">described</a> in the Android Open Source Project site. + </li> + <li>[C-0-6] MUST implement a kernel application sandboxing mechanism which allows filtering of system calls using a configurable policy from multithreaded programs. The upstream Android Open Source Project meets this requirement through enabling the seccomp-BPF with threadgroup synchronization (TSYNC) as described <a href="http://source.android.com/devices/tech/config/kernel.html#Seccomp-BPF-TSYNC">in the Kernel Configuration section of source.android.com</a>. + </li> + </ul> + <p> + Kernel integrity and self-protection features are integral to Android security. Device implementations: + </p> + <ul> + <li>[C-0-7] MUST implement kernel stack buffer overflow protections (e.g. <code>CONFIG_CC_STACKPROTECTOR_STRONG</code>). + </li> + <li>[C-0-8] MUST implement strict kernel memory protections where executable code is read-only, read-only data is non-executable and non-writable, and writable data is non-executable (e.g. <code>CONFIG_DEBUG_RODATA</code> or <code>CONFIG_STRICT_KERNEL_RWX</code>). + </li> + <li>[SR] STRONGLY RECOMMENDED to keep kernel data which is written only during initialization marked read-only after initialization (e.g. <code>__ro_after_init</code>). + </li> + <li>[SR} STRONGLY RECOMMENDED to implement static and dynamic object size bounds checking of copies between user-space and kernel-space (e.g. <code>CONFIG_HARDENED_USERCOPY</code>). + </li> + <li>[SR] STRONGLY RECOMMENDED to never execute user-space memory when running in the kernel (e.g. hardware PXN, or emulated via <code>CONFIG_CPU_SW_DOMAIN_PAN</code> or <code>CONFIG_ARM64_SW_TTBR0_PAN</code>). + </li> + <li>[SR] STRONGLY RECOMMENDED to never read or write user-space memory in the kernel outside of normal usercopy access APIs (e.g. hardware PAN, or emulated via <code>CONFIG_CPU_SW_DOMAIN_PAN</code> or <code>CONFIG_ARM64_SW_TTBR0_PAN</code>). + </li> + <li>[SR] STRONGLY RECOMMENDED to randomize the layout of the kernel code and memory, and to avoid exposures that would compromise the randomization (e.g. <code>CONFIG_RANDOMIZE_BASE</code> with bootloader entropy via the <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/chosen.txt"><code>/chosen/kaslr-seed Device Tree node</code></a> or <a href="https://docs.microsoft.com/en-us/windows-hardware/drivers/bringup/efi-rng-protocol"><code>EFI_RNG_PROTOCOL</code></a>). + </li> + </ul> + <p> + If device implementations use a Linux kernel, they: + </p> + <ul> + <li>[C-1-1] MUST implement SELinux. + </li> + <li>[C-1-2] MUST set SELinux to global enforcing mode. + </li> + <li>[C-1-3] MUST configure all domains in enforcing mode. No permissive mode domains are allowed, including domains specific to a device/vendor. + </li> + <li>[C-1-4] MUST NOT modify, omit, or replace the neverallow rules present within the system/sepolicy folder provided in the upstream Android Open Source Project (AOSP) and the policy MUST compile with all neverallow rules present, for both AOSP SELinux domains as well as device/vendor specific domains. + </li> + <li>SHOULD retain the default SELinux policy provided in the system/sepolicy folder of the upstream Android Open Source Project and only further add to this policy for their own device-specific configuration. + </li> + </ul> + <p> + If device implementations use kernel other than Linux, they: + </p> + <ul> + <li>[C-2-1] MUST use an mandatory access control system that is equivalent to SELinux. + </li> + </ul> + <h3 id="9_8_privacy"> + 9.8. Privacy + </h3> + <h4 id="9_8_1_usage_history"> + 9.8.1. Usage History + </h4> + <p> + Android stores the history of the user's choices and manages such history by <a href="https://developer.android.com/reference/android/app/usage/UsageStatsManager.html">UsageStatsManager</a>. + </p> + <p> + Device implementations: + </p> + <ul> + <li>[C-1-1] MUST keep a reasonable retention period of such user history. + </li> + <li>[SR] Are STRONGLY RECOMMENDED to keep the 14 days retention period as configured by default in the AOSP implementation. + </li> + </ul> + <h4 id="9_8_2_recording"> + 9.8.2. Recording + </h4> + <p> + If device implementations include functionality in the system that captures the contents displayed on the screen and/or records the audio stream played on the device, they: + </p> + <ul> + <li>[C-1-1] MUST have an ongoing notification to the user whenever this functionality is enabled and actively capturing/recording. + </li> + </ul> + <p> + If device implementations include a component enabled out-of-box, capable of recording ambient audio to infer useful information about user’s context, they: + </p> + <ul> + <li>[C-2-1] MUST NOT store in persistent on-device storage or transmit off the device the recorded raw audio or any format that can be converted back into the original audio or a near facsimile, except with explicit user consent. + </li> + </ul> + <h4 id="9_8_3_connectivity"> + 9.8.3. Connectivity + </h4> + <p> + If device implementations have a USB port with USB peripheral mode support, they: + </p> + <ul> + <li>[C-1-1] MUST present a user interface asking for the user's consent before allowing access to the contents of the shared storage over the USB port. + </li> + </ul> + <h4 id="9_8_4_network_traffic"> + 9.8.4. Network Traffic + </h4> + <p> + Device implementations: + </p> + <ul> + <li>[C-0-1] MUST preinstall the same root certificates for the system-trusted Certificate Authority (CA) store as <a href="https://source.android.com/security/overview/app-security.html#certificate-authorities">provided</a> in the upstream Android Open Source Project. + </li> + <li>[C-0-2] MUST ship with an empty user root CA store. + </li> + <li>[C-0-3] MUST display a warning to the user indicating the network traffic may be monitored, when a user root CA is added. + </li> + </ul> + <p> + If device traffic is routed through a VPN, device implementations: + </p> + <ul> + <li>[C-1-1] MUST display a warning to the user indicating either: + <ul> + <li>That network traffic may be monitored. + </li> + <li>That network traffic is being routed through the specific VPN application providing the VPN. + </li> + </ul> + </li> + </ul> + <p> + If device implementations have a mechanism, enabled out-of-box by default, that routes network data traffic through a proxy server or VPN gateway (for example, preloading a VPN service with <code>android.permission.CONTROL_VPN</code> granted), they: + </p> + <ul> + <li>[C-2-1] MUST ask for the user's consent before enabling that mechanism, unless that VPN is enabled by the Device Policy Controller via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setAlwaysOnVpnPackage%28android.content.ComponentName,%20java.lang.String,%20boolean%29"><code>DevicePolicyManager.setAlwaysOnVpnPackage()</code></a> , in which case the user does not need to provide a separate consent, but MUST only be notified. + </li> + </ul> + <p> + If device implementations implement a user affordance to toggle on the "always-on VPN" function of a 3rd-party VPN app, they: + </p> + <ul> + <li>[C-3-1] MUST disable this user affordance for apps that do not support always-on VPN service in the <code>AndroidManifest.xml</code> file via setting the <a href="https://developer.android.com/reference/android/net/VpnService.html#SERVICE_META_DATA_SUPPORTS_ALWAYS_ON"><code>SERVICE_META_DATA_SUPPORTS_ALWAYS_ON</code></a> attribute to <code>false</code>. + </li> + </ul> + <h3 id="9_9_data_storage_encryption"> + 9.9. Data Storage Encryption + </h3> + <p> + If device implementations support a secure lock screen as described in <a href="#9_11_1_secure_lock_screen">section 9.11.1</a>, they: + </p> + <ul> + <li>[C-1-1] MUST support data storage encryption of the application private data (<code>/data partition</code>), as well as the application shared storage partition (<code>/sdcard partition</code>) if it is a permanent, non-removable part of the device. + </li> + </ul> + <p> + If device implementations support a secure lock screen as described in <a href="#9_11_1_secure_lock_screen">section 9.11.1</a> and support data storage encryption with Advanced Encryption Standard (AES) crypto performance above 50MiB/sec, they: + </p> + <ul> + <li> + <p> + [C-2-1] MUST enable the data storage encryption by default at the time the user has completed the out-of-box setup experience. If device implementations are already launched on an earlier Android version with encryption disabled by default, such a device cannot meet the requirement through a system software update and thus MAY be exempted. + </p> + </li> + <li> + <p> + SHOULD meet the above data storage encryption requirement via implementing <a href="https://source.android.com/security/encryption/file-based.html">File Based Encryption</a> (FBE). + </p> + </li> + </ul> + <h4 id="9_9_1_direct_boot"> + 9.9.1. Direct Boot + </h4> + <p> + Device implementations: + </p> + <ul> + <li> + <p> + [C-0-1] MUST implement the <a href="http://developer.android.com/preview/features/direct-boot.html">Direct Boot mode</a> APIs even if they do not support Storage Encryption. + </p> + </li> + <li> + <p> + [C-0-2] The <a href="https://developer.android.com/reference/android/content/Intent.html#ACTION_LOCKED_BOOT_COMPLETED"><code>ACTION_LOCKED_BOOT_COMPLETED</code></a> and <a href="https://developer.android.com/reference/android/content/Intent.html#ACTION_USER_UNLOCKED"><code>ACTION_USER_UNLOCKED</code></a> Intents MUST still be broadcast to signal Direct Boot aware applications that Device Encrypted (DE) and Credential Encrypted (CE) storage locations are available for user. + </p> + </li> + </ul> + <h4 id="9_9_2_file_based_encryption"> + 9.9.2. File Based Encryption + </h4> + <p> + If device implementations support FBE, they: + </p> + <ul> + <li>[C-1-1] MUST boot up without challenging the user for credentials and allow Direct Boot aware apps to access to the Device Encrypted (DE) storage after the <code>ACTION_LOCKED_BOOT_COMPLETED</code> message is broadcasted. + </li> + <li>[C-1-2] MUST only allow access to Credential Encrypted (CE) storage after the user has unlocked the device by supplying their credentials (eg. passcode, pin, pattern or fingerprint) and the <code>ACTION_USER_UNLOCKED</code> message is broadcasted. + </li> + <li>[C-1-3] MUST NOT offer any method to unlock the CE protected storage without the user-supplied credentials. + </li> + <li>[C-1-4] MUST support Verified Boot and ensure that DE keys are cryptographically bound to the device's hardware root of trust. + </li> + <li>[C-1-5] MUST support encrypting file contents using AES with a key length of 256-bits in XTS mode. + </li> + <li> + <p> + [C-1-6] MUST support encrypting file name using AES with a key length of 256-bits in CBC-CTS mode. + </p> + </li> + <li> + <p> + The keys protecting CE and DE storage areas: + </p> + </li> + <li> + <p> + [C-1-7] MUST be cryptographically bound to a hardware-backed Keystore. + </p> + </li> + <li>[C-1-8] CE keys MUST be bound to a user's lock screen credentials. + </li> + <li>[C-1-9] CE keys MUST be bound to a default passcode when the user has not specified lock screen credentials. + </li> + <li> + <p> + [C-1-10] MUST be unique and distinct, in other words no user's CE or DE key matches any other user's CE or DE keys. + </p> + </li> + <li> + <p> + SHOULD make preloaded essential apps (e.g. Alarm, Phone, Messenger) Direct Boot aware. + </p> + </li> + <li>MAY support alternative ciphers, key lengths and modes for file content and file name encryption, but MUST use the mandatorily supported ciphers, key lengths and modes by default. + </li> + </ul> + <p> + The upstream Android Open Source project provides a preferred implementation of this feature based on the Linux kernel ext4 encryption feature. + </p> + <h4 id="9_9_3_full_disk_encryption"> + 9.9.3. Full Disk Encryption + </h4> + <p> + If device implementations support <a href="http://source.android.com/devices/tech/security/encryption/index.html">full disk encryption</a> (FDE), they: + </p> + <ul> + <li>[C-1-1] MUST use AES with a key of 128-bits (or greater) and a mode designed for storage (for example, AES-XTS, AES-CBC-ESSIV). + </li> + <li>[C-1-2] MUST use a default passcode to wrap the encryption key and MUST NOT write the encryption key to storage at any time without being encrypted. + </li> + <li>[C-1-3] MUST AES encrypt the encryption key by default unless the user explicitly opts out, except when it is in active use, with the lock screen credentials stretched using a slow stretching algorithm (e.g. PBKDF2 or scrypt). + </li> + <li>[C-1-4] The above default password stretching algorithm MUST be cryptographically bound to that keystore when the user has not specified a lock screen credentials or has disabled use of the passcode for encryption and the device provides a hardware-backed keystore. + </li> + <li>[C-1-5] MUST NOT send encryption key off the the device (even when wrapped with the user passcode and/or hardware bound key). + </li> + </ul> + <p> + The upstream Android Open Source project provides a preferred implementation of this feature, based on the Linux kernel feature dm-crypt. + </p> + <h3 id="9_10_device_integrity"> + 9.10. Device Integrity + </h3> + <p> + The following requirements ensures there is transparancy to the status of the device integrity. Device implementations: + </p> + <ul> + <li>[C-0-1] MUST correctly report through the System API method <code>PersistentDataBlockManager.getFlashLockState()</code> whether their bootloader state permits flashing of the system image. The <code>FLASH_LOCK_UNKNOWN</code> state is reserved for device implementations upgrading from an earlier version of Android where this new system API method did not exist. + </li> + </ul> + <p> + Verified boot is a feature that guarantees the integrity of the device software. If a device implementation supports the feature, it: + </p> + <ul> + <li>[C-1-1] MUST declare the platform feature flag <code>android.software.verified_boot</code>. + </li> + <li>[C-1-2] MUST perform verification on every boot sequence. + </li> + <li>[C-1-3] MUST start verification from an immutable hardware key that is the root of trust and go all the way up to the system partition. + </li> + <li>[C-1-4] MUST implement each stage of verification to check the integrity and authenticity of all the bytes in the next stage before executing the code in the next stage. + </li> + <li>[C-1-5] MUST use verification algorithms as strong as current recommendations from NIST for hashing algorithms (SHA-256) and public key sizes (RSA-2048). + </li> + <li>[C-1-6] MUST NOT allow boot to complete when system verification fails, unless the user consents to attempt booting anyway, in which case the data from any non-verified storage blocks MUST not be used. + </li> + <li>[C-1-7] MUST NOT allow verified partitions on the device to be modified unless the user has explicitly unlocked the boot loader. + </li> + <li>[SR] If there are multiple discrete chips in the device (e.g. radio, specialized image processor), the boot process of each of those chips is STRONGLY RECOMMENDED to verify every stage upon booting. + </li> + <li>[SR] STRONGLY RECOMMENDED to use tamper-evident storage: for when the bootloader is unlocked. Tamper-evident storage means that the boot loader can detect if the storage has been tampered with from inside the HLOS (High Level Operating System). + </li> + <li>[SR] STRONGLY RECOMMENDED to prompt the user, while using the device, and require physical confirmation before allowing a transition from boot loader locked mode to boot loader unlocked mode. + </li> + <li>[SR] STRONGLY RECOMMENDED to implement rollback protection for the HLOS (e.g. boot, system partitions) and to use tamper-evident storage for storing the metadata used for determining the minimum allowable OS version. + </li> + <li>SHOULD implement rollback protection for any component with persistent firmware (e.g. modem, camera) and SHOULD use tamper-evident storage for storing the metadata used for determining the minimum allowable version. + </li> + </ul> + <p> + The upstream Android Open Source Project provides a preferred implementation of this feature in the <a href="http://android.googlesource.com/platform/external/avb/"><code>external/avb/</code></a> repository, which can be integrated into the boot loader used for loading Android. + </p> + <p> + If device implementations report the feature flag <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_RAM_NORMAL"><code>android.hardware.ram.normal</code></a> , they: + </p> + <ul> + <li>[C-2-1] MUST support verified boot for device integrity. + </li> + </ul> + <p> + If a device implementation is already launched without supporting verified boot on an earlier version of Android, such a device can not add support for this feature with a system software update and thus are exempted from the requirement. + </p> + <h3 id="9_11_keys_and_credentials"> + 9.11. Keys and Credentials + </h3> + <p> + The <a href="https://developer.android.com/training/articles/keystore.html">Android Keystore System</a> allows app developers to store cryptographic keys in a container and use them in cryptographic operations through the <a href="https://developer.android.com/reference/android/security/KeyChain.html">KeyChain API</a> or the <a href="https://developer.android.com/reference/java/security/KeyStore.html">Keystore API</a>. Device implementations: + </p> + <ul> + <li>[C-0-1] MUST at least allow more than 8,192 keys to be imported. + </li> + <li>[C-0-2] The lock screen authentication MUST rate-limit attempts and MUST have an exponential backoff algorithm. Beyond 150 failed attempts, the delay MUST be at least 24 hours per attempt. + </li> + <li>SHOULD not limit the number of keys that can be generated + </li> + </ul> + <p> + When the device implementation supports a secure lock screen, it: + </p> + <ul> + <li>[C-1-1] MUST back up the keystore implementation with secure hardware. + </li> + <li>[C-1-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the <a href="https://source.android.com/security/trusty/">Trusty</a> implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options. + </li> + <li>[C-1-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the <a href="http://source.android.com/devices/tech/security/authentication/gatekeeper.html">Gatekeeper Hardware Abstraction Layer (HAL)</a> and Trusty, which can be used to satisfy this requirement. + </li> + <li>[C-1-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units. + </li> + </ul> + <p> + Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a hardware-backed keystore, unless it declares the <code>android.hardware.fingerprint</code> feature which requires a hardware-backed keystore. + </p> + <h4 id="9_11_1_secure_lock_screen"> + 9.11.1. Secure Lock Screen + </h4> + <p> + If device implementations have a secure lock screen and include one or more trust agent, which implements the <code>TrustAgentService</code> System API, then they: + </p> + <ul> + <li>[C-1-1] MUST indicate the user in the Settings and Lock screen user interface of situations where either the screen auto-lock is deferred or the screen lock can be unlocked by the trust agent. The AOSP meets the requirement by showing a text description for the "Automatically lock setting" and "Power button instantly locks setting" menus and a distinguishable icon on the lock screen. + </li> + <li>[C-1-2] MUST respect and fully implement all trust agent APIs in the <code>DevicePolicyManager</code> class, such as the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#KEYGUARD&lowbarDISABLE&lowbarTRUST&lowbarAGENTS"><code>KEYGUARD_DISABLE_TRUST_AGENTS</code></a> constant. + </li> + <li>[C-1-3] MUST NOT fully implement the <code>TrustAgentService.addEscrowToken()</code> function on a device that is used as the primary personal device (e.g. handheld) but MAY fully implement the function on device implementations typically shared. + </li> + <li>[C-1-4] MUST encrypt the tokens added by <code>TrustAgentService.addEscrowToken()</code> before storing them on the device. + </li> + <li>[C-1-5] MUST NOT store the encryption key on the device. + </li> + <li>[C-1-6] MUST inform the user about the security implications before enabling the escrow token to decrypt the data storage. + </li> + </ul> + <p> + If device implementations add or modify the authentication methods to unlock the lock screen, then for such an authentication method to be treated as a secure way to lock the screen, they: + </p> + <ul> + <li>[C-2-1] MUST be the user authentication method as described in <a href="https://developer.android.com/training/articles/keystore.html#UserAuthentication">Requiring User Authentication For Key Use</a>. + </li> + <li>[C-2-2] MUST unlock all keys for a third-party developer app to use when the user unlocks the secure lock screen. For example, all keys MUST be available for a third-party developer app through relevant APIs, such as <a href="https://developer.android.com/reference/android/app/KeyguardManager.html#createConfirmDeviceCredentialIntent%28java.lang.CharSequence,%20java.lang.CharSequence%29"><code>createConfirmDeviceCredentialIntent</code></a> and <a href="https://developer.android.com/reference/android/security/keystore/KeyGenParameterSpec.Builder.html#setUserAuthenticationRequired%28boolean%29"><code>setUserAuthenticationRequired</code></a>. + </li> + </ul> + <p> + If device implementations add or modify the authentication methods to unlock the lock screen if based on a known secret then for such an authentication method to be treated as a secure way to lock the screen, they: + </p> + <ul> + <li>[C-3-1] The entropy of the shortest allowed length of inputs MUST be greater than 10 bits. + </li> + <li>[C-3-2] The maximum entropy of all possible inputs MUST be greater than 18 bits. + </li> + <li>[C-3-3] MUST not replace any of the existing authentication methods (PIN,pattern, password) implemented and provided in AOSP. + </li> + <li>[C-3-4] MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordQuality%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setPasswordQuality()</code></a> method with a more restrictive quality constant than <code>PASSWORD_QUALITY_SOMETHING</code>. + </li> + </ul> + <p> + If device implementations add or modify the authentication methods to unlock the lock screen if based on a physical token or the location, then for such an authentication method to be treated as a secure way to lock the screen, they: + </p> + <ul> + <li>[C-4-1] MUST have a fall-back mechanism to use one of the primary authentication methods which is based on a known secret and meets the requirements to be treated as a secure lock screen. + </li> + <li>[C-4-2] MUST be disabled and only allow the primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the policy with either the <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setKeyguardDisabledFeatures%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setKeyguardDisabledFeatures(KEYGUARD_DISABLE_TRUST_AGENTS)</code></a> method or the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordQuality%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setPasswordQuality()</code></a> method with a more restrictive quality constant than <code>PASSWORD_QUALITY_UNSPECIFIED</code>. + </li> + <li>[C-4-3] The user MUST be challenged for the primary authentication (e.g.PIN, pattern, password) at least once every 72 hours or less. + </li> + </ul> + <p> + If device implementations add or modify the authentication methods to unlock the lock screen based on biometrics, then for such an authentication method to be treated as a secure way to lock the screen, they: + </p> + <ul> + <li>[C-5-1] MUST have a fall-back mechanism to use one of the primary authentication methods which is based on a known secret and meets the requirements to be treated as a secure lock screen. + </li> + <li>[C-5-2] MUST be disabled and only allow the primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the keguard feature policy by calling the method <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setKeyguardDisabledFeatures%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setKeyguardDisabledFeatures(KEYGUARD_DISABLE_FINGERPRINT)</code></a>. + </li> + <li>[C-5-3] MUST have a false acceptance rate that is equal or stronger than what is required for a fingerprint sensor as described in section 7.3.10, or otherwise MUST be disabled and only allow the primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the password quality policy via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordQuality%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setPasswordQuality()</code></a> method with a more restrictive quality constant than <code>PASSWORD_QUALITY_BIOMETRIC_WEAK</code>. + </li> + <li>[SR] Are STRONGLY RECOMMENDED to have spoof and imposter acceptance rates that are equal to or stronger than what is required for a fingerprint sensor as described in section 7.3.10. + </li> + </ul> + <p> + If the spoof and imposter acceptance rates are not equal to or stronger than what is required for a fingerprint sensor as described in <a href="#7_3_10_fingerprint_sensor">section 7.3.10</a> and the Device Policy Controller (DPC) application has set the password quality policy via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordQuality%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setPasswordQuality()</code></a> method with a more restrictive quality constant than <code>PASSWORD_QUALITY_BIOMETRIC_WEAK</code>, then: + </p> + <ul> + <li>[C-6-1] MUST disable these biometric methods and allow only the primary authentication to unlock the screen. + </li> + <li>[C-6-2] MUST challenge the user for the primary authentication (e.g.PIN, pattern, password) at least once every 72 hours or less. + </li> + </ul> + <p> + If device implementations add or modify the authentication methods to unlock the lock screen and if such an authentication method will be used to unlock the keyguard, but will not be treated as a secure lock screen, then they: + </p> + <ul> + <li>[C-7-1] MUST return <code>false</code> for both the <a href="http://developer.android.com/reference/android/app/KeyguardManager.html#isKeyguardSecure%28%29"><code>KeyguardManager.isKeyguardSecure()</code></a> and the <a href="https://developer.android.com/reference/android/app/KeyguardManager.html#isDeviceSecure%28%29"><code>KeyguardManager.isDeviceSecure()</code></a> methods. + </li> + <li>[C-7-2] MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordQuality%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setPasswordQuality()</code></a> method with a more restrictive quality constant than <code>PASSWORD_QUALITY_UNSPECIFIED</code>. + </li> + <li>[C-7-3] MUST NOT reset the password expiration timers set by <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordExpirationTimeout%28android.content.ComponentName,%20long%29"><code>DevicePolicyManager.setPasswordExpirationTimeout()</code></a>. + </li> + <li>[C-7-4] MUST NOT authenticate access to keystores if the application has called <a href="https://developer.android.com/reference/android/security/keystore/KeyGenParameterSpec.Builder.html#setUserAuthenticationRequired%28boolean%29"><code>KeyGenParameterSpec.Builder.setUserAuthenticationRequired(true)</code></a>). + </li> + </ul> + <h3 id="9_12_data_deletion"> + 9.12. Data Deletion + </h3> + <p> + All device implementations: + </p> + <ul> + <li>[C-0-1] MUST provide users a mechanism to perform a "Factory Data Reset". + </li> + <li>[C-0-2] MUST delete all user-generated data. That is, all data except for the following: + <ul> + <li>The system image + </li> + <li>Any operating system files required by the system image + </li> + </ul> + </li> + <li>[C-0-3] MUST delete the data in such a way that will satisfy relevant industry standards such as NIST SP800-88. + </li> + <li>[C-0-4] MUST trigger the above "Factory Data Reset" process when the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#wipeData%28int%29"><code>DevicePolicyManager.wipeData()</code></a> API is called by the primary user's Device Policy Controller app. + </li> + <li>MAY provide a fast data wipe option that conducts only a logical data erase. + </li> + </ul> + <h3 id="9_13_safe_boot_mode"> + 9.13. Safe Boot Mode + </h3> + <p> + Android provides Safe Boot Mode, which allows users to boot up into a mode where only preinstalled system apps are allowed to run and all third-party apps are disabled. This mode, known as "Safe Boot Mode", provides the user the capability to uninstall potentially harmful third-party apps. + </p> + <p> + Device implementations are: + </p> + <ul> + <li>[SR] STRONGLY RECOMMENDED to implement Safe Boot Mode. + </li> + </ul> + <p> + If device implementations implement Safe Boot Mode, they: + </p> + <ul> + <li> + <p> + [C-1-1] MUST provide the user an option to enter Safe Boot Mode in such a way that is uninterruptible from third-party apps installed on the device, except when the third-party app is a Device Policy Controller and has set the <a href="https://developer.android.com/reference/android/os/UserManager.html#DISALLOW_SAFE_BOOT"><code>UserManager.DISALLOW_SAFE_BOOT</code></a> flag as true. + </p> + </li> + <li> + <p> + [C-1-2] MUST provide the user the capability to uninstall any third-party apps within Safe Mode. + </p> + </li> + <li> + <p> + SHOULD provide the user an option to enter Safe Boot Mode from the boot menu using a workflow that is different from that of a normal boot. + </p> + </li> + </ul> + <h3 id="9_14_automotive_vehicle_system_isolation"> + 9.14. Automotive Vehicle System Isolation + </h3> + <p> + Android Automotive devices are expected to exchange data with critical vehicle subsystems by using the <a href="http://source.android.com/devices/automotive.html">vehicle HAL</a> to send and receive messages over vehicle networks such as CAN bus. + </p> + <p> + The data exchange can be secured by implementing security features below the Android framework layers to prevent malicious or unintentional interaction with these subsystems. + </p> + <h2 id="10_software_compatibility_testing"> + 10. Software Compatibility Testing + </h2> + <p> + Device implementations MUST pass all tests described in this section. + </p> + <p> + However, note that no software test package is fully comprehensive. For this reason, device implementers are <strong>STRONGLY RECOMMENDED</strong> to make the minimum number of changes as possible to the reference and preferred implementation of Android available from the Android Open Source Project. This will minimize the risk of introducing bugs that create incompatibilities requiring rework and potential device updates. + </p> + <h3 id="10_1_compatibility_test_suite"> + 10.1. Compatibility Test Suite + </h3> + <p> + Device implementations MUST pass the <a href="http://source.android.com/compatibility/index.html">Android Compatibility Test Suite (CTS)</a> available from the Android Open Source Project, using the final shipping software on the device. Additionally, device implementers SHOULD use the reference implementation in the Android Open Source tree as much as possible, and MUST ensure compatibility in cases of ambiguity in CTS and for any reimplementations of parts of the reference source code. + </p> + <p> + The CTS is designed to be run on an actual device. Like any software, the CTS may itself contain bugs. The CTS will be versioned independently of this Compatibility Definition, and multiple revisions of the CTS may be released for Android 8.1. Device implementations MUST pass the latest CTS version available at the time the device software is completed. + </p> + <h3 id="10_2_cts_verifier"> + 10.2. CTS Verifier + </h3> + <p> + Device implementations MUST correctly execute all applicable cases in the CTS Verifier. The CTS Verifier is included with the Compatibility Test Suite, and is intended to be run by a human operator to test functionality that cannot be tested by an automated system, such as correct functioning of a camera and sensors. + </p> + <p> + The CTS Verifier has tests for many kinds of hardware, including some hardware that is optional. Device implementations MUST pass all tests for hardware that they possess; for instance, if a device possesses an accelerometer, it MUST correctly execute the Accelerometer test case in the CTS Verifier. Test cases for features noted as optional by this Compatibility Definition Document MAY be skipped or omitted. + </p> + <p> + Every device and every build MUST correctly run the CTS Verifier, as noted above. However, since many builds are very similar, device implementers are not expected to explicitly run the CTS Verifier on builds that differ only in trivial ways. Specifically, device implementations that differ from an implementation that has passed the CTS Verifier only by the set of included locales, branding, etc. MAY omit the CTS Verifier test. + </p> + <h2 id="11_updatable_software"> + 11. Updatable Software + </h2> + <p> + Device implementations MUST include a mechanism to replace the entirety of the system software. The mechanism need not perform “live” upgrades—that is, a device restart MAY be required. + </p> + <p> + Any method can be used, provided that it can replace the entirety of the software preinstalled on the device. For instance, any of the following approaches will satisfy this requirement: + </p> + <ul> + <li>“Over-the-air (OTA)” downloads with offline update via reboot. + </li> + <li>“Tethered” updates over USB from a host PC. + </li> + <li>“Offline” updates via a reboot and update from a file on removable storage. + </li> + </ul> + <p> + However, if the device implementation includes support for an unmetered data connection such as 802.11 or Bluetooth PAN (Personal Area Network) profile, it MUST support OTA downloads with offline update via reboot. + </p> + <p> + The update mechanism used MUST support updates without wiping user data. That is, the update mechanism MUST preserve application private data and application shared data. Note that the upstream Android software includes an update mechanism that satisfies this requirement. + </p> + <p> + For device implementations that are launching with Android 6.0 and later, the update mechanism SHOULD support verifying that the system image is binary identical to expected result following an OTA. The block-based OTA implementation in the upstream Android Open Source Project, added since Android 5.1, satisfies this requirement. + </p> + <p> + Also, device implementations SHOULD support <a href="https://source.android.com/devices/tech/ota/ab_updates.html">A/B system updates</a>. The AOSP implements this feature using the boot control HAL. + </p> + <p> + If an error is found in a device implementation after it has been released but within its reasonable product lifetime that is determined in consultation with the Android Compatibility Team to affect the compatibility of third-party applications, the device implementer MUST correct the error via a software update available that can be applied per the mechanism just described. + </p> + <p> + Android includes features that allow the Device Owner app (if present) to control the installation of system updates. To facilitate this, the system update subsystem for devices that report android.software.device_admin MUST implement the behavior described in the <a href="http://developer.android.com/reference/android/app/admin/SystemUpdatePolicy.html">SystemUpdatePolicy</a> class. + </p> + <h2 id="12_document_changelog"> + 12. Document Changelog + </h2> + <p> + For a summary of changes to the Compatibility Definition in this release: + </p> + <ul> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/?pretty=full&no-merges">Document changelog</a> + </li> + </ul> + <p> + For a summary of changes to individuals sections: + </p> + <ol> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/1_introduction?pretty=full&no-merges">Introduction</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/2_device_types?pretty=full&no-merges">Device Types</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/3_software?pretty=full&no-merges">Software</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/4_application-packaging?pretty=full&no-merges">Application Packaging</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/5_multimedia?pretty=full&no-merges">Multimedia</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/6_dev-tools-and-options?pretty=full&no-merges">Developer Tools and Options</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/7_hardware-compatibility?pretty=full&no-merges">Hardware Compatibility</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/8_performance-and-power?pretty=full&no-merges">Performance and Power</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/9_security-model?pretty=full&no-merges">Security Model</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/10_software-compatibility-testing?pretty=full&no-merges">Software Compatibility Testing</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/11_updatable-software?pretty=full&no-merges">Updatable Software</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/12_document-changelog?pretty=full&no-merges">Document Changelog</a> + </li> + <li> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/13_contact-us?pretty=full&no-merges">Contact Us</a> + </li> + </ol> + <h3 id="12_1_changelog_viewing_tips"> + 12.1. Changelog Viewing Tips + </h3> + <p> + Changes are marked as follows: + </p> + <ul> + <li> + <p> + <strong>CDD</strong><br /> + Substantive changes to the compatibility requirements. + </p> + </li> + <li> + <p> + <strong>Docs</strong><br /> + Cosmetic or build related changes. + </p> + </li> + </ul> + <p> + For best viewing, append the <code>pretty=full</code> and <code>no-merges</code> URL parameters to your changelog URLs. + </p> + <h2 id="13_contact_us"> + 13. Contact Us + </h2> + <p> + You can join the <a href="https://groups.google.com/forum/#!forum/android-compatibility">android-compatibility forum</a> and ask for clarifications or bring up any issues that you think the document does not cover. + </p> + </body> +</html> diff --git a/en/compatibility/8.1/versions.html b/en/compatibility/8.1/versions.html new file mode 100644 index 00000000..9d241cfe --- /dev/null +++ b/en/compatibility/8.1/versions.html @@ -0,0 +1,43 @@ +<html devsite> + <head> + <title>Permitted Version Strings for Android 8.1</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + + + +<p>As described in Section 3.2.2 of the <a +href="android-8.1-cdd.pdf">Android 8.1 Compatibility Definition</a>, +only certain strings are allowable for the system property +<code>android.os.Build.VERSION.RELEASE</code>. The reason for this is that +applications and web sites may rely on predictable values for this string, and +so that end users can easily and reliably identify the version of Android +running on their devices.</p> +<p>Because subsequent releases of the Android software may revise this string, +but not change any API behavior, such releases may not be accompanied by a new +Compatibility Definition Document. This page lists the versions that are +allowable by an Android 8.1-based system. The only permitted values for +<code>android.os.Build.VERSION.RELEASE</code> for Android 8.1 are:</p> +<ul> +<li>8.1</li> +</ul> + + </body> +</html> diff --git a/en/compatibility/_translation.yaml b/en/compatibility/_translation.yaml index 9ff3ad1c..08b9cc29 100644 --- a/en/compatibility/_translation.yaml +++ b/en/compatibility/_translation.yaml @@ -14,6 +14,7 @@ ignore_paths: - /compatibility/7.0/... - /compatibility/7.1/... - /compatibility/8.0/... +- /compatibility/8.1/... - /compatibility/images/... enable_continuous_translation: True title: Android Open Source Project Compatibility tab diff --git a/en/compatibility/android-cdd.html b/en/compatibility/android-cdd.html index 30b613dd..52557f99 100644 --- a/en/compatibility/android-cdd.html +++ b/en/compatibility/android-cdd.html @@ -1,7 +1,7 @@ <html devsite="" xmlns="http://www.w3.org/1999/xhtml"> <head> <title> - Android 8.0 Compatibility Definition + Android 8.1 Compatibility Definition </title> <meta name="project_path" value="/_project.yaml" /> <meta name="book_path" value="/_book.yaml" /> @@ -26,16 +26,16 @@ 1. Introduction </h2> <p> - This document enumerates the requirements that must be met in order for devices to be compatible with Android 8.0. + This document enumerates the requirements that must be met in order for devices to be compatible with Android 8.1. </p> <p> The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard defined in <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC2119</a>. </p> <p> - As used in this document, a “device implementer” or “implementer” is a person or organization developing a hardware/software solution running Android 8.0. A “device implementation” or “implementation is the hardware/software solution so developed. + As used in this document, a “device implementer” or “implementer” is a person or organization developing a hardware/software solution running Android 8.1. A “device implementation” or “implementation is the hardware/software solution so developed. </p> <p> - To be considered compatible with Android 8.0, device implementations MUST meet the requirements presented in this Compatibility Definition, including any documents incorporated via reference. + To be considered compatible with Android 8.1, device implementations MUST meet the requirements presented in this Compatibility Definition, including any documents incorporated via reference. </p> <p> Where this definition or the software tests described in <a href="#10_software_compatibility_testing">section 10</a> is silent, ambiguous, or incomplete, it is the responsibility of the device implementer to ensure compatibility with existing implementations. @@ -76,7 +76,7 @@ Each ID is defined as below: </p> <ul> - <li>Device Type ID (see more on <a href="#2_device_types">2. Device Types</a>) + <li>Device Type ID (see more on <a href="#2_device_types">2. Device Types</a> <ul> <li>C: Core (Requirements that are applied to any Android device implementations) </li> @@ -86,8 +86,6 @@ </li> <li>A: Android Automotive implementation </li> - <li>W: Android Watch implementation - </li> </ul> </li> <li>Condition ID @@ -201,7 +199,7 @@ </li> <li> <p> - [H-0-2] MUST send both the normal and long press event of the Back function (<a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK"><code>KEYCODE_BACK</code></a>) to the foreground application. + [H-0-2] MUST send both the normal and long press event of the the Back function (<a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK"><code>KEYCODE_BACK</code></a>) to the foreground application. </p> </li> </ul> @@ -286,132 +284,77 @@ <strong>Minimum Memory and Storage (Section 7.6.1)</strong> </p> <p> - Handheld device implementations: - </p> - <ul> - <li>[H-0-1] MUST have at least 4GB of non-volatile storage available for application private data (a.k.a. "/data" partition) - </li> - <li>[H-0-2] MUST return “true” for <code>ActivityManager.isLowRamDevice()</code> when there is less than 1GB of memory available to the kernel and userspace. - </li> - </ul> - <p> - If Handheld device implementations are 32-bit: + If Handheld device implementations declare support of only a 32-bit ABI: </p> <ul> <li> <p> - [H-1-1] The memory available to the kernel and userspace MUST be at least 512MB if any of the following densities are used: + [H-1-1] The memory available to the kernel and userspace MUST be at least 416MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA). </p> - <ul> - <li>280dpi or lower on small/normal screens<sup>*</sup> - </li> - <li>ldpi or lower on extra large screens - </li> - <li>mdpi or lower on large screens - </li> - </ul> </li> <li> <p> - [H-2-1] The memory available to the kernel and userspace MUST be at least 608MB if any of the following densities are used: + [H-2-1] The memory available to the kernel and userspace MUST be at least 592MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA). </p> - <ul> - <li>xhdpi or higher on small/normal screens<sup>*</sup> - </li> - <li>hdpi or higher on large screens - </li> - <li>mdpi or higher on extra large screens - </li> - </ul> </li> <li> <p> - [H-3-1] The memory available to the kernel and userspace MUST be at least 896MB if any of the following densities are used: + [H-3-1] The memory available to the kernel and userspace MUST be at least 896MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+). </p> - <ul> - <li>400dpi or higher on small/normal screens<sup>*</sup> - </li> - <li>xhdpi or higher on large screens - </li> - <li>tvdpi or higher on extra large screens - </li> - </ul> </li> <li> <p> - [H-4-1] The memory available to the kernel and userspace MUST be at least 1344MB if any of the following densities are used: + [H-4-1] The memory available to the kernel and userspace MUST be at least 1344MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA). </p> - <ul> - <li>560dpi or higher on small/normal screens<sup>*</sup> - </li> - <li>400dpi or higher on large screens - </li> - <li>xhdpi or higher on extra large screens - </li> - </ul> </li> </ul> <p> - If Handheld device implementations are 64-bit: + If Handheld device implementations declare support of 32-bit and 64-bit ABIs: </p> <ul> <li> <p> - [H-5-1] The memory available to the kernel and userspace MUST be at least 816MB if any of the following densities are used: + [H-5-1] The memory available to the kernel and userspace MUST be at least 816MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA). </p> - <ul> - <li>280dpi or lower on small/normal screens<sup>*</sup> - </li> - <li>ldpi or lower on extra large screens - </li> - <li>mdpi or lower on large screens - </li> - </ul> </li> <li> <p> - [H-6-1] The memory available to the kernel and userspace MUST be at least 944MB if any of the following densities are used: + [H-6-1] The memory available to the kernel and userspace MUST be at least 944MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA). </p> - <ul> - <li>xhdpi or higher on small/normal screens<sup>*</sup> - </li> - <li>hdpi or higher on large screens - </li> - <li>mdpi or higher on extra large screens - </li> - </ul> </li> <li> <p> - [H-7-1] The memory available to the kernel and userspace MUST be at least 1280MB if any of the following densities are used: + [H-7-1] The memory available to the kernel and userspace MUST be at least 1280MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+). </p> - <ul> - <li>400dpi or higher on small/normal screens<sup>*</sup> - </li> - <li>xhdpi or higher on large screens - </li> - <li>tvdpi or higher on extra large screens - </li> - </ul> </li> <li> <p> - [H-8-1] The memory available to the kernel and userspace MUST be at least 1824MB if any of the following densities are used: + [H-8-1] The memory available to the kernel and userspace MUST be at least 1824MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA). </p> - <ul> - <li>560dpi or higher on small/normal screens<sup>*</sup> - </li> - <li>400dpi or higher on large screens - </li> - <li>xhdpi or higher on extra large screens - </li> - </ul> </li> </ul> <p> Note that the "memory available to the kernel and userspace" above refers to the memory space provided in addition to any memory already dedicated to hardware components such as radio, video, and so on that are not under the kernel’s control on device implementations. </p> <p> + If Handheld device implementations include less than or equal to 1GB of memory available to the kernel and userspace, they: + </p> + <ul> + <li>[H-9-1] MUST declare the feature flag <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_RAM_LOW"><code>android.hardware.ram.low</code></a>. + </li> + <li>[H-9-2] MUST have at least 1.1 GB of non-volatile storage for application private data (a.k.a. "/data" partition). + </li> + </ul> + <p> + If Handheld device implementations include more than 1GB of memory available to the kernel and userspace, they: + </p> + <ul> + <li>[H-10-1] MUST have at least 4GB of non-volatile storage available for application private data (a.k.a. "/data" partition). + </li> + <li>SHOULD declare the feature flag <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_RAM_NORMAL"><code>android.hardware.ram.normal</code></a>. + </li> + </ul> + <p> <strong>Application Shared Storage (Section 7.6.2)</strong> </p> <p> @@ -829,7 +772,7 @@ <ul> <li>[T-0-1] MUST provide the Home and Back functions. </li> - <li>[T-0-2] MUST send both the normal and long press event of the Back function (<a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK"><code>KEYCODE_BACK</code></a>) to the foreground application. + <li>[T-0-2] MUST send both the normal and long press event of the the Back function (<a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK"><code>KEYCODE_BACK</code></a>) to the foreground application. </li> </ul> <p> @@ -881,6 +824,8 @@ <ul> <li>[T-0-1] MUST have at least 4GB of non-volatile storage available for application private data (a.k.a. "/data" partition) </li> + <li>[T-0-2] MUST return “true” for <code>ActivityManager.isLowRamDevice()</code> when there is less than 1GB of memory available to the kernel and userspace. + </li> </ul> <p> <strong>Microphone (Section 7.8.1)</strong> @@ -1153,8 +1098,8 @@ <li>[T-0-1] MUST support TV Input Framework. </li> </ul> - <h4 id="2_3_4_performance_and_power"> - 2.3.4. Performance and Power + <h4 id="2_2_4_performance_and_power"> + 2.2.4. Performance and Power </h4> <p> <strong>User Experience Consistency (Section 8.1)</strong> @@ -1421,7 +1366,7 @@ <ul> <li>[A-0-1] MUST provide the Home function and MAY provide Back and Recent functions. </li> - <li>[A-0-2] MUST send both the normal and long press event of the Back function (<a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK"><code>KEYCODE_BACK</code></a>) to the foreground application. + <li>[A-0-2] MUST send both the normal and long press event of the the Back function (<a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK"><code>KEYCODE_BACK</code></a>) to the foreground application. </li> </ul> <p> @@ -1693,8 +1638,8 @@ <li>[A-0-1] MUST include a UI framework to support third-party apps using the media APIs as described in section 3.14. </li> </ul> - <h4 id="2_5_4_performance_and_power"> - 2.5.4. Performance and Power + <h4 id="2_2_4_performance_and_power"> + 2.2.4. Performance and Power </h4> <p> <strong>Power-Saving Modes (Section 8.3)</strong> @@ -1726,8 +1671,8 @@ <li>[A-0-4] MUST make this power usage available via the <a href="http://source.android.com/devices/tech/power/batterystats.html"><code>adb shell dumpsys batterystats</code></a> shell command to the app developer. </li> </ul> - <h4 id="2_5_5_security_model"> - 2.5.5. Security Model + <h4 id="2_2_5_security_model"> + 2.2.5. Security Model </h4> <p> <strong>Multi-User Support (Section 9.5)</strong> @@ -1769,8 +1714,8 @@ <p> Tablet device implementations have similar requirements to handheld device implementations. The exceptions are in indicated by and * in that section and noted for reference in this section. </p> - <h4 id="2_6_1_hardware"> - 2.6.1. Hardware + <h4 id="2_4_1_hardware"> + 2.4.1. Hardware </h4> <p> <strong>Screen Size (Section 7.1.1.1)</strong> @@ -1885,7 +1830,7 @@ VERSION.RELEASE </td> <td> - The version of the currently-executing Android system, in human-readable format. This field MUST have one of the string values defined in <a href="http://source.android.com/compatibility/8.0/versions.html">8.0</a>. + The version of the currently-executing Android system, in human-readable format. This field MUST have one of the string values defined in <a href="http://source.android.com/compatibility/8.1/versions.html">8.1</a>. </td> </tr> <tr> @@ -1893,7 +1838,7 @@ VERSION.SDK </td> <td> - The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 8.0, this field MUST have the integer value 8.0_INT. + The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 8.1, this field MUST have the integer value 8.1_INT. </td> </tr> <tr> @@ -1901,7 +1846,7 @@ VERSION.SDK_INT </td> <td> - The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 8.0, this field MUST have the integer value 8.0_INT. + The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 8.1, this field MUST have the integer value 8.1_INT. </td> </tr> <tr> @@ -1991,7 +1936,7 @@ </p> <p class="small"> acme/myproduct/<br /> - mydevice:8.0/LMYXX/3359:userdebug/test-keys + mydevice:8.1/LMYXX/3359:userdebug/test-keys </p> <p> The fingerprint MUST NOT include whitespace characters. If other fields included in the template above have whitespace characters, they MUST be replaced in the build fingerprint with another character, such as the underscore ("_") character. The value of this field MUST be encodable as 7-bit ASCII. @@ -2131,7 +2076,7 @@ <ul> <li> <p> - [C-0-1] Device implementations MUST include these application, service components, or at least a handler, for all the public intent filter patterns defined by the following core Android applications in AOSP: + [C-0-1] Device implementations MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following core android applications in AOSP: </p> <ul> <li>Desk Clock @@ -2239,14 +2184,27 @@ If device implementations report <code>android.software.home_screen</code>, they: </p> <ul> - <li>[C-1-1] MUST honor the <a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_HOME_SETTINGS">android.settings.HOME_SETTINGS</a> intent to show a default app settings menu for Home Screen. + <li>[C-1-1] MUST honor the <a href="http://developer.android.com/reference/android/provider/Settings.html#ACTION_HOME_SETTINGS"><code>android.settings.HOME_SETTINGS</code></a> intent to show a default app settings menu for Home Screen. </li> </ul> <p> If device implementations report <code>android.hardware.telephony</code>, they: </p> <ul> - <li>[C-2-1] MUST provide a settings menu that will call the <a href="http://developer.android.com/reference/android/provider/Telephony.Sms.Intents.html">android.provider.Telephony.ACTION_CHANGE_DEFAULT</a> intent to show a dialog to change the default SMS application. + <li> + <p> + [C-2-1] MUST provide a settings menu that will call the <a href="http://developer.android.com/reference/android/provider/Telephony.Sms.Intents.html"><code>android.provider.Telephony.ACTION_CHANGE_DEFAULT</code></a> intent to show a dialog to change the default SMS application. + </p> + </li> + <li> + <p> + [C-2-2] MUST honor the <a href="https://developer.android.com/reference/android/telecom/TelecomManager.html#ACTION_CHANGE_DEFAULT_DIALER"><code>android.telecom.action.CHANGE_DEFAULT_DIALER</code></a> intent to show a dialog to allow the user to change the default Phone application. + </p> + </li> + <li> + <p> + [C-2-3] MUST honor the <a href="https://developer.android.com/reference/android/telecom/TelecomManager.html#ACTION_CHANGE_PHONE_ACCOUNTS">android.telecom.action.CHANGE_PHONE_ACCOUNTS</a> intent to provide user affordance to configure the <a href="https://developer.android.com/reference/android/telecom/ConnectionService.html"><code>ConnectionServices</code></a> associated with the <a href="https://developer.android.com/reference/android/telecom/PhoneAccount.html"><code>PhoneAccounts</code></a>, as well as a default PhoneAccount that the telecommunications service provider will use to place outgoing calls. The AOSP implementation meets this requirement by including a "Calling Accounts option" menu within the "Calls" settings menu. + </p> </li> </ul> <p> @@ -2257,17 +2215,10 @@ </li> </ul> <p> - If device implementations report <code>android.hardware.telephony</code>, they: + If device implementations support the <code>VoiceInteractionService</code> and have more than one application using this API installed at a time, they: </p> <ul> - <li>[C-4-1] MUST honor the <a href="https://developer.android.com/reference/android/telecom/TelecomManager.html#ACTION_CHANGE_DEFAULT_DIALER">android.telecom.action.CHANGE_DEFAULT_DIALER</a> intent to show a dialog to allow the user to change the default Phone application. - </li> - </ul> - <p> - If device implementations support the VoiceInteractionService, they: - </p> - <ul> - <li>[C-5-1] MUST honor the <a href="https://developer.android.com/reference/android/provider/Settings.html#ACTION_VOICE_INPUT_SETTINGS">android.settings.ACTION_VOICE_INPUT_SETTINGS</a> intent to show a default app settings menu for voice input and assist. + <li>[C-4-1] MUST honor the <a href="https://developer.android.com/reference/android/provider/Settings.html#ACTION_VOICE_INPUT_SETTINGS"><code>android.settings.ACTION_VOICE_INPUT_SETTINGS</code></a> intent to show a default app settings menu for voice input and assist. </li> </ul> <h4 id="3_2_4_activities_on_secondary_displays"> @@ -2469,7 +2420,7 @@ <ul> <li>[C-1-1] MUST report <code>android.software.webview</code>. </li> - <li>[C-1-2] MUST use the <a href="http://www.chromium.org/">Chromium</a> Project build from the upstream Android Open Source Project on the Android 8.0 branch for the implementation of the <a href="http://developer.android.com/reference/android/webkit/WebView.html"><code>android.webkit.WebView</code></a> API. + <li>[C-1-2] MUST use the <a href="http://www.chromium.org/">Chromium</a> Project build from the upstream Android Open Source Project on the Android 8.1 branch for the implementation of the <a href="http://developer.android.com/reference/android/webkit/WebView.html"><code>android.webkit.WebView</code></a> API. </li> <li> <p> @@ -3047,19 +2998,21 @@ </li> </ul> <p> - If device implementations include a default launcher that supports in-app pinning of shortcuts and widgets, they: + If device implementations include a default launcher that supports in-app pinning of shortcuts, they: </p> <ul> - <li>[C-2-1] MUST report <code>true</code> for <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html#isRequestPinShortcutSupported%28%29"><code>ShortcutManager.isRequestPinShortcutSupported()</code></a> and <a href="https://developer.android.com/reference/android/appwidget/AppWidgetManager.html#isRequestPinAppWidgetSupported%28%29"><code>AppWidgetManager.html.isRequestPinAppWidgetSupported()</code></a>. + <li>[C-2-1] MUST report <code>true</code> for <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html#isRequestPinShortcutSupported%28%29"><code>ShortcutManager.isRequestPinShortcutSupported()</code></a>. + </li> + <li>[C-2-2] MUST have user affordance asking the user before adding a shortcut requested by apps via the <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html#requestPinShortcut%28android.content.pm.ShortcutInfo,%20android.content.IntentSender%29"><code>ShortcutManager.requestPinShortcut()</code></a> API method. </li> - <li>[C-2-2] MUST have user affordance asking the user before adding a shortcut requested by apps via the <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html#requestPinShortcut%28android.content.pm.ShortcutInfo,%20android.content.IntentSender%29"><code>ShortcutManager.requestPinShortcut()</code></a> and the <a href="https://developer.android.com/reference/android/appwidget/AppWidgetManager.html#requestPinAppWidget%28android.content.ComponentName,android.os.Bundle,%20android.app.PendingIntent%29"><code>AppWidgetManager.requestPinAddWidget()</code></a> API method. + <li>[C-2-3] MUST support pinned shortcuts and dynamic and static shortcuts as documented on the <a href="https://developer.android.com/guide/topics/ui/shortcuts.html">App Shortcuts page</a>. </li> </ul> <p> - Conversely, if device implementations do not support in-app pinning, they: + Conversely, if device implementations do not support in-app pinning of shortcuts, they: </p> <ul> - <li>[C-3-1] MUST report <code>false</code> for <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html#isRequestPinShortcutSupported%28%29"><code>ShortcutManager.isRequestPinShortcutSupported()</code></a> and <a href="https://developer.android.com/reference/android/appwidget/AppWidgetManager.html#isRequestPinAppWidgetSupported%28%29"><code>AppWidgetManager.html#isRequestPinAppWidgetSupported()</code></a>. + <li>[C-3-1] MUST report <code>false</code> for <a href="https://developer.android.com/reference/android/content/pm/ShortcutManager.html#isRequestPinShortcutSupported%28%29"><code>ShortcutManager.isRequestPinShortcutSupported()</code></a>. </li> </ul> <p> @@ -3088,15 +3041,24 @@ If device implementations support third-party app widgets, they: </p> <ul> - <li>[C-1-1] MUST declare support for platform feature android.software.app_widgets. + <li>[C-1-1] MUST declare support for platform feature <code>android.software.app_widgets</code>. </li> <li>[C-1-2] MUST include built-in support for AppWidgets and expose user interface affordances to add, configure, view, and remove AppWidgets directly within the Launcher. </li> - <li>[C-1-3] MUST be capable of rendering widgets that are 4 x 4 in the standard grid size. See the <a href="http://developer.android.com/guide/practices/ui_guidelines/widget_design.html">App Widget Design Guidelines</a> in the Android SDK documentation for details. + <li>[C-1-3] MUST be capable of rendering widgets that are 4 x 4 in the standard grid size. See the <a href="http://developer.android.com/guide/practices/ui_guidelines/widget_design.html">App Widget DesignGuidelines</a> in the Android SDK documentation for details. </li> <li>MAY support application widgets on the lock screen. </li> </ul> + <p> + If device implementations support third-party app widgets and in-app pinning of shortcuts, they: + </p> + <ul> + <li>[C-2-1] MUST report <code>true</code> for <a href="https://developer.android.com/reference/android/appwidget/AppWidgetManager.html#isRequestPinAppWidgetSupported%28%29"><code>AppWidgetManager.html.isRequestPinAppWidgetSupported()</code></a>. + </li> + <li>[C-2-2] MUST have user affordance asking the user before adding a shortcut requested by apps via the <a href="https://developer.android.com/reference/android/appwidget/AppWidgetManager.html#requestPinAppWidget%28android.content.ComponentName,android.os.Bundle,%20android.app.PendingIntent%29"><code>AppWidgetManager.requestPinAppWidget()</code></a> API method. + </li> + </ul> <h4 id="3_8_3_notifications"> 3.8.3. Notifications </h4> @@ -3126,7 +3088,7 @@ </li> <li>SHOULD present some higher priority notifications as heads-up notifications. </li> - <li>SHOULD have user affordance to snooze notifications. + <li>SHOULD have a user affordance to snooze notifications. </li> <li>MAY only manage the visibility and timing of when third-party apps can notify users of notable events to mitigate safety issues such as driver distraction. </li> @@ -3154,21 +3116,21 @@ Android includes the <a href="https://developer.android.com/reference/android/service/notification/NotificationListenerService.html"><code>NotificationListenerService</code></a> APIs that allow apps (once explicitly enabled by the user) to receive a copy of all notifications as they are posted or updated. </p> <p> - Device implementations: + If device implementations report the feature flag <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_RAM_NORMAL"><code>android.hardware.ram.normal</code></a>, they: </p> <ul> - <li>[C-0-1] MUST correctly and promptly update notifications in their entirety to all such installed and user-enabled listener services, including any and all metadata attached to the Notification object. + <li>[C-1-1] MUST correctly and promptly update notifications in their entirety to all such installed and user-enabled listener services, including any and all metadata attached to the Notification object. </li> - <li>[C-0-2] MUST respect the <a href="https://developer.android.com/reference/android/service/notification/NotificationListenerService.html#snoozeNotification%28java.lang.String,%20long%29"><code>snoozeNotification()</code></a> API call, and dismiss the notification and make a callback after the snooze duration that is set in the API call. + <li>[C-1-2] MUST respect the <a href="https://developer.android.com/reference/android/service/notification/NotificationListenerService.html#snoozeNotification%28java.lang.String,%20long%29"><code>snoozeNotification()</code></a> API call, and dismiss the notification and make a callback after the snooze duration that is set in the API call. </li> </ul> <p> If device implementations have a user affordance to snooze notifications, they: </p> <ul> - <li>[C-1-1] MUST reflect the snoozed notification status properly through the standard APIs such as <a href="https://developer.android.com/reference/android/service/notification/NotificationListenerService.html#getSnoozedNotifications%28%29"><code>NotificationListenerService.getSnoozedNotifications()</code></a>. + <li>[C-2-1] MUST reflect the snoozed notification status properly through the standard APIs such as <a href="https://developer.android.com/reference/android/service/notification/NotificationListenerService.html#getSnoozedNotifications%28%29"><code>NotificationListenerService.getSnoozedNotifications()</code></a>. </li> - <li>[C-1-2] MUST make this user affordance available to snooze notifications from each installed third-party app's, unless they are from persistent/foreground services. + <li>[C-2-2] MUST make this user affordance available to snooze notifications from each installed third-party app's, unless they are from persistent/foreground services. </li> </ul> <h5 id="3_8_3_3_dnd_(do_not_disturb)"> @@ -3320,7 +3282,7 @@ If device implementations including the recents function navigation key as detailed in <a href="#7_2_3_navigation_keys">section 7.2.3</a> alter the interface, they: </p> <ul> - <li>[C-1-1] MUST support at least up to 20 displayed activities. + <li>[C-1-1] MUST support at least up to 7 displayed activities. </li> <li>SHOULD at least display the title of 4 activities at a time. </li> @@ -3343,7 +3305,7 @@ </li> <li> <p> - [SR] Device implementations are STRONGLY RECOMMENDED to use the upstream Android user interface (or a similar thumbnail-based interface) for the overview screen. + [SR] Are STRONGLY RECOMMENDED to use the upstream Android user interface (or a similar thumbnail-based interface) for the overview screen. </p> </li> </ul> @@ -3430,7 +3392,7 @@ </li> <li>[C-1-2] Applications can indicate whether they are capable of operating in multi-window mode in the <code>AndroidManifest.xml</code> file, either explicitly via setting the <a href="https://developer.android.com/reference/android/R.attr.html#resizeableActivity"><code>android:resizeableActivity</code></a> attribute to <code>true</code> or implicitly by having the targetSdkVersion > 24. Apps that explicitly set this attribute to <code>false</code> in their manifest MUST NOT be launched in multi-window mode. Older apps with targetSdkVersion < 24 that did not set this <code>android:resizeableActivity</code> attribute MAY be launched in multi-window mode, but the system MUST provide warning that the app may not work as expected in multi-window mode. </li> - <li>[C-1-3] MUST NOT offer split-screen or freeform mode if the screen height < 440 dp and the screen width < 440 dp. + <li>[C-1-3] MUST NOT offer split-screen or freeform mode if the screen height < 440 dp and the the screen width < 440 dp. </li> <li>Device implementations with screen size <code>xlarge</code> SHOULD support freeform mode. </li> @@ -3726,7 +3688,7 @@ </li> <li>Opening EPG </li> - <li>Configuring and tuning to third-party TIF-based inputs + <li>Configuring and tuning to third-party TIF-based inputs (if those inputs are supported) </li> <li>Opening Settings menu </li> @@ -3742,14 +3704,8 @@ 3.12.1.3. TV input app linking </h5> <p> - If device implementations support TIF, they: + Android Television device implementations SHOULD support <a href="http://developer.android.com/reference/android/media/tv/TvContract.Channels.html#COLUMN_APP_LINK_INTENT_URI">TV input app linking</a>, which allows all inputs to provide activity links from the current activity to another activity (i.e. a link from live programming to related content). The TV App SHOULD show TV input app linking when it is provided. </p> - <ul> - <li>[C-1-1] Android Television device implementations MUST support <a href="http://developer.android.com/reference/android/media/tv/TvContract.Channels.html#COLUMN_APP_LINK_INTENT_URI">TV input app linking</a>, which allows all inputs to provide activity links from the current activity to another activity (i.e. a link from live programming to related content). - </li> - <li>[C-1-2] The TV App MUST show TV input app linking when it is provided. - </li> - </ul> <h5 id="3_12_1_4_time_shifting"> 3.12.1.4. Time shifting </h5> @@ -3771,15 +3727,7 @@ <ul> <li>[SR] STRONGLY RECOMMENDED to support TV recording. </li> - <li> - <p> - If the TV input supports recording and the recording of a program is not <a href="https://developer.android.com/reference/android/media/tv/TvContract.Programs.html#COLUMN_RECORDING_PROHIBITED">prohibited</a>, the EPG MAY provide a way to <a href="https://developer.android.com/reference/android/media/tv/TvInputInfo.html#canRecord%28%29">record a program</a>. - </p> - </li> - <li> - <p> - SHOULD provide a user interface to play recorded programs. - </p> + <li>If the TV input supports recording and the recording of a program is not <a href="https://developer.android.com/reference/android/media/tv/TvContract.Programs.html#COLUMN_RECORDING_PROHIBITED">prohibited</a>, the EPG MAY provide a way to <a href="https://developer.android.com/reference/android/media/tv/TvInputInfo.html#canRecord%28%29">record a program</a>. </li> </ul> <h3 id="3_13_quick_settings"> @@ -3814,6 +3762,8 @@ </li> <li>[C-1-4] MUST have drawer to present <a href="http://developer.android.com/reference/android/media/browse/MediaBrowser.html">MediaBrowser</a> hierarchy. </li> + <li>[C-1-5] MUST consider double tap of <a href="https://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_HEADSETHOOK"><code>KEYCODE_HEADSETHOOK</code></a> or <a href="https://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_MEDIA_PLAY_PAUSE"><code>KEYCODE_MEDIA_PLAY_PAUSE</code></a> as <a href="https://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_MEDIA_NEXT"><code>KEYCODE_MEDIA_NEXT</code></a> for <a href="https://developer.android.com/reference/android/media/session/MediaSession.Callback.html#onMediaButtonEvent%28android.content.Intent%29"><code>MediaSession.Callback#onMediaButtonEvent</code></a>. + </li> </ul> <h3 id="3_15_instant_apps"> 3.15. Instant Apps @@ -5591,28 +5541,26 @@ 5.9. Musical Instrument Digital Interface (MIDI) </h3> <p> - If a device implementation supports the inter-app MIDI software transport (virtual MIDI devices), and it supports MIDI over <em>all</em> of the following MIDI-capable hardware transports for which it provides generic non-MIDI connectivity, it is: - </p> - <ul> - <li>[SR] STRONGLY RECOMMENDED to report support for feature android.software.midi via the <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html">android.content.pm.PackageManager</a> class. - </li> - </ul> - <p> - The MIDI-capable hardware transports are: + If device implementations report support for feature <code>android.software.midi</code> via the <a href="http://developer.android.com/reference/android/content/pm/PackageManager.html"><code>android.content.pm.PackageManager</code></a> class, they: </p> <ul> - <li>USB host mode (section 7.7 USB) - </li> - <li>USB peripheral mode (section 7.7 USB) - </li> - <li>MIDI over Bluetooth LE acting in central role (section 7.4.3 Bluetooth) + <li> + <p> + [C-1-1] MUST support MIDI over <em>all</em> MIDI-capable hardware transports for which they provide generic non-MIDI connectivity, where such transports are: + </p> + <ul> + <li>USB host mode, <a href="#7_7_USB">section 7.7</a> + </li> + <li>USB peripheral mode, <a href="#7_7_USB">section 7.7</a> + </li> + <li>MIDI over Bluetooth LE acting in central role, <a href="#7_4_3_bluetooth">section 7.4.3</a> + </li> + </ul> </li> - </ul> - <p> - If the device implementation provides generic non-MIDI connectivity over a particular MIDI-capable hardware transport listed above, but does not support MIDI over that hardware transport, it: - </p> - <ul> - <li>[C-1-1] MUST NOT report support for feature android.software.midi. + <li> + <p> + [C-1-2] MUST support the inter-app MIDI software transport (virtual MIDI devices) + </p> </li> </ul> <h3 id="5_10_professional_audio"> @@ -5632,7 +5580,15 @@ </li> <li>[C-1-5] MUST meet latencies and USB audio requirements using the <a href="https://developer.android.com/ndk/guides/audio/opensl-for-android.html">OpenSL ES</a> PCM buffer queue API. </li> - <li>SHOULD provide a sustainable level of CPU performance while audio is active. + <li>[SR] Are STRONGLY RECOMMENDED to provide a consistent level of CPU performance while audio is active and CPU load is varying. This should be tested using <a href="https://github.com/googlesamples/android-audio-high-performance/tree/master/SimpleSynth">SimpleSynth</a> commit <a href="https://github.com/googlesamples/android-audio-high-performance/commit/1bd6391f8ba9512f9f8798e979bc55b899f856d1">1bd6391</a>. The SimpleSynth app needs to be run with below parameters and achieve zero underruns after 10 minutes: + <ul> + <li>Work cycles: 200,000 + </li> + <li>Variable load: ON (this will switch between 100% and 10% of the work cycles value every 2 seconds and is designed to test CPU governor behavior) + </li> + <li>Stabilized load: OFF + </li> + </ul> </li> <li>SHOULD minimize audio clock inaccuracy and drift relative to standard time. </li> @@ -5695,26 +5651,21 @@ </li> </ul> <p> - If device implementations omit a 4 conductor 3.5mm audio jack, they: + If device implementations omit a 4 conductor 3.5mm audio jack and include a USB port(s) supporting USB host mode, they: </p> <ul> - <li>[C-3-1] MUST have a continuous round-trip audio latency of 20 milliseconds or less. + <li>[C-3-1] MUST implement the USB audio class. </li> - <li>The continuous round-trip audio latency SHOULD be 10 milliseconds or less over the USB host mode port using USB audio class. + <li>[C-3-2] MUST have a continuous round-trip audio latency of 20 milliseconds or less over the USB host mode port using USB audio class. </li> - </ul> - <p> - If device implementations include a USB port(s) supporting USB host mode, they: - </p> - <ul> - <li>[C-4-1] MUST implement the USB audio class. + <li>The continuous round-trip audio latency SHOULD be 10 milliseconds or less over the USB host mode port using USB audio class. </li> </ul> <p> If device implementations include an HDMI port, they: </p> <ul> - <li>[C-5-1] MUST support output in stereo and eight channels at 20-bit or 24-bit depth and 192 kHz without bit-depth loss or resampling. + <li>[C-4-1] MUST support output in stereo and eight channels at 20-bit or 24-bit depth and 192 kHz without bit-depth loss or resampling. </li> </ul> <h3 id="5_11_capture_for_unprocessed"> @@ -6342,10 +6293,10 @@ 7.2.3. Navigation Keys </h4> <p> - The <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_HOME">Home</a>, <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_APP_SWITCH">Recents</a>, and <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK">Back</a> functions typically provided via an interaction with a dedicated physical button or a distinct portion of the touch screen, are essential to the Android navigation paradigm and therefore: + The <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_HOME">Home</a>, <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_APP_SWITCH">Recents</a>, and <a href="http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_BACK">Back</a> functions typically provided via an interaction with a dedicated physical button or a distinct portion of the touch screen, are essential to the Android navigation paradigm and therefore, device implementations: </p> <ul> - <li>[C-0-1] MUST provide the Home function. + <li>[C-0-1] MUST provide a user affordance to launch installed applications that have an activity with the <code><intent-filter></code> set with <code>ACTION=MAIN</code> and <code>CATEGORY=LAUNCHER</code> or <code>CATEGORY=LEANBACK_LAUNCHER</code> for Television device implementations. The Home function SHOULD be the mechanism for this user affordance. </li> <li>SHOULD provide buttons for the Recents and Back function. </li> @@ -7313,37 +7264,33 @@ <ul> <li>[C-3-1] MUST correctly declare support of direct channel types and direct report rates level through the <a href="https://developer.android.com/reference/android/hardware/Sensor.html#isDirectChannelTypeSupported%28int%29"><code>isDirectChannelTypeSupported</code></a> and <a href="https://developer.android.com/reference/android/hardware/Sensor.html#getHighestDirectReportRateLevel%28%29"><code>getHighestDirectReportRateLevel</code></a> API. </li> - <li>[C-3-2] MUST support at least one of the two sensor direct channel types for all sensors that declare support for sensor direct channel: - <ul> - <li> - <a href="https://developer.android.com/reference/android/hardware/SensorDirectChannel.html#TYPE_HARDWARE_BUFFER"><code>TYPE_HARDWARE_BUFFER</code></a> - </li> - <li> - <a href="https://developer.android.com/reference/android/hardware/SensorDirectChannel.html#TYPE_MEMORY_FILE"><code>TYPE_MEMORY_FILE</code></a> - </li> - </ul> + <li>[C-3-2] MUST support at least one of the two sensor direct channel types for all sensors that declare support for sensor direct channel + </li> + <li> + <a href="https://developer.android.com/reference/android/hardware/SensorDirectChannel.html#TYPE_HARDWARE_BUFFER"><code>TYPE_HARDWARE_BUFFER</code></a> + </li> + <li> + <a href="https://developer.android.com/reference/android/hardware/SensorDirectChannel.html#TYPE_MEMORY_FILE"><code>TYPE_MEMORY_FILE</code></a> </li> <li>SHOULD support event reporting through sensor direct channel for primary sensor (non-wakeup variant) of the following types: - <ul> - <li> - <code>TYPE_ACCELEROMETER</code> - </li> - <li> - <code>TYPE_ACCELEROMETER_UNCALIBRATED</code> - </li> - <li> - <code>TYPE_GYROSCOPE</code> - </li> - <li> - <code>TYPE_GYROSCOPE_UNCALIBRATED</code> - </li> - <li> - <code>TYPE_MAGNETIC_FIELD</code> - </li> - <li> - <code>TYPE_MAGNETIC_FIELD_UNCALIBRATED</code> - </li> - </ul> + </li> + <li> + <code>TYPE_ACCELEROMETER</code> + </li> + <li> + <code>TYPE_ACCELEROMETER_UNCALIBRATED</code> + </li> + <li> + <code>TYPE_GYROSCOPE</code> + </li> + <li> + <code>TYPE_GYROSCOPE_UNCALIBRATED</code> + </li> + <li> + <code>TYPE_MAGNETIC_FIELD</code> + </li> + <li> + <code>TYPE_MAGNETIC_FIELD_UNCALIBRATED</code> </li> </ul> <h4 id="7_3_10_fingerprint_sensor"> @@ -7366,23 +7313,27 @@ </li> <li>[C-1-3] MUST have a false acceptance rate not higher than 0.002%. </li> - <li>[C-1-4] MUST rate limit attempts for at least 30 seconds after five false trials for fingerprint verification. + <li>[SR] Are STRONGLY RECOMMENDED to have a spoof and imposter acceptance rate not higher than 7%. + </li> + <li>[C-1-4] MUST disclose that this mode may be less secure than a strong PIN, pattern, or password and clearly enumerate the risks of enabling it, if the spoof and imposter acceptance rates are higher than 7%. + </li> + <li>[C-1-5] MUST rate limit attempts for at least 30 seconds after five false trials for fingerprint verification. </li> - <li>[C-1-5] MUST have a hardware-backed keystore implementation, and perform the fingerprint matching in a Trusted Execution Environment (TEE) or on a chip with a secure channel to the TEE. + <li>[C-1-6] MUST have a hardware-backed keystore implementation, and perform the fingerprint matching in a Trusted Execution Environment (TEE) or on a chip with a secure channel to the TEE. </li> - <li>[C-1-6] MUST have all identifiable fingerprint data encrypted and cryptographically authenticated such that they cannot be acquired, read or altered outside of the Trusted Execution Environment (TEE) as documented in the <a href="https://source.android.com/devices/tech/security/authentication/fingerprint-hal.html">implementation guidelines</a> on the Android Open Source Project site. + <li>[C-1-7] MUST have all identifiable fingerprint data encrypted and cryptographically authenticated such that they cannot be acquired, read or altered outside of the Trusted Execution Environment (TEE) as documented in the <a href="https://source.android.com/devices/tech/security/authentication/fingerprint-hal.html">implementation guidelines</a> on the Android Open Source Project site. </li> - <li>[C-1-7] MUST prevent adding a fingerprint without first establishing a chain of trust by having the user confirm existing or add a new device credential (PIN/pattern/password) that's secured by TEE; the Android Open Source Project implementation provides the mechanism in the framework to do so. + <li>[C-1-8] MUST prevent adding a fingerprint without first establishing a chain of trust by having the user confirm existing or add a new device credential (PIN/pattern/password) that's secured by TEE; the Android Open Source Project implementation provides the mechanism in the framework to do so. </li> - <li>[C-1-8] MUST NOT enable 3rd-party applications to distinguish between individual fingerprints. + <li>[C-1-9] MUST NOT enable 3rd-party applications to distinguish between individual fingerprints. </li> - <li>[C-1-9] MUST honor the DevicePolicyManager.KEYGUARD_DISABLE_FINGERPRINT flag. + <li>[C-1-10] MUST honor the DevicePolicyManager.KEYGUARD_DISABLE_FINGERPRINT flag. </li> - <li>[C-1-10] MUST, when upgraded from a version earlier than Android 6.0, have the fingerprint data securely migrated to meet the above requirements or removed. + <li>[C-1-11] MUST, when upgraded from a version earlier than Android 6.0, have the fingerprint data securely migrated to meet the above requirements or removed. </li> - <li>[SR] STRONGLY RECOMMENDED to have a false rejection rate of less than 10%, as measured on the device. + <li>[SR] Are STRONGLY RECOMMENDED to have a false rejection rate of less than 10%, as measured on the device. </li> - <li>[SR] STRONGLY RECOMMENDED to have a latency below 1 second, measured from when the fingerprint sensor is touched until the screen is unlocked, for one enrolled finger. + <li>[SR] Are STRONGLY RECOMMENDED to have a latency below 1 second, measured from when the fingerprint sensor is touched until the screen is unlocked, for one enrolled finger. </li> <li>SHOULD use the Android Fingerprint icon provided in the Android Open Source Project. </li> @@ -7489,6 +7440,26 @@ <li>SHOULD migrate the blocked numbers into the provider when a device updates to Android 7.0. </li> </ul> + <h5 id="7_4_1_2_telecom_api"> + 7.4.1.2. Telecom API + </h5> + <p> + If device implementations report <code>android.hardware.telephony</code>, they: + </p> + <ul> + <li>[C-SR] Are STRONGLY RECOMMENDED to handle the the audio headset's <code>KEYCODE_MEDIA_PLAY_PAUSE</code> and <code>KEYCODE_HEADSETHOOK</code> events for the <a href="https://developer.android.com/reference/android/telecom/package-summary.html"><code>android.telecom</code></a> APIs as below: + <ul> + <li>Call <a href="https://developer.android.com/reference/android/telecom/Connection.html#onDisconnect%28%29"><code>Connection.onDisconnect()</code></a> when a short press of the key event is detected during an ongoing call. + </li> + <li>Call <a href="https://developer.android.com/reference/android/telecom/Connection.html#onAnswer%28%29"><code>Connection.onAnswer()</code></a> when a short press of the key event is detected during an incoming call. + </li> + <li>Call <a href="https://developer.android.com/reference/android/telecom/Connection.html#onReject%28%29"><code>Connection.onReject()</code></a> when a long press of the key event is detected during an incoming call. + </li> + <li>Toggle the mute status of the <a href="https://developer.android.com/reference/android/telecom/CallAudioState.html"><code>CallAudioState</code></a> + </li> + </ul> + </li> + </ul> <h4 id="7_4_2_ieee_802_11_(wi-fi)"> 7.4.2. IEEE 802.11 (Wi-Fi) </h4> @@ -7958,7 +7929,7 @@ </li> <li>[C-1-3] MUST NOT use a front-facing camera as the default for the Camera API and MUST NOT configure the API to treat a front-facing camera as the default rear-facing camera, even if it is the only camera on the device. </li> - <li>[C-1-5] The camera preview MUST be mirrored horizontally relative to the orientation specified by the application when the current application has explicitly requested that the Camera display be rotated via a call to the <a href="http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)"><code>android.hardware.Camera.setDisplayOrientation()</code></a> method. Conversely, the preview MUST be mirrored along the device’s default horizontal axis when the current application does not explicitly request that the Camera display be rotated via a call to the <a href="http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)"><code>android.hardware.Camera.setDisplayOrientation()</code></a> method. + <li>[C-1-5] The camera preview MUST be mirrored horizontally relative to the orientation specified by the application when the current application has explicitly requested that the Camera display be rotated via a call to the <a href="http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)"><code>android.hardware.Camera.setDisplayOrientation()</code></a> method. Conversely, the preview MUST be mirrored along the device’s default horizontal axis when the the current application does not explicitly request that the Camera display be rotated via a call to the <a href="http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)"><code>android.hardware.Camera.setDisplayOrientation()</code></a> method. </li> <li>[C-1-6] MUST NOT mirror the final captured still image or video streams returned to application callbacks or committed to media storage. </li> @@ -8018,7 +7989,7 @@ </li> <li>[C-0-3] MUST support the YV12 format (as denoted by the <code>android.graphics.ImageFormat.YV12</code> constant) for camera previews for both front- and rear-facing cameras for <code>android.hardware.Camera</code>. (The hardware video encoder and camera may use any native pixel format, but the device implementation MUST support conversion to YV12.) </li> - <li>[C-0-4] MUST support the <code>android.hardware.ImageFormat.YUV_420_888</code> and <code>android.hardware.ImageFormat.JPEG</code> formats as outputs through the <code>android.media.ImageReader</code> API for <code>android.hardware.camera2</code>. + <li>[C-0-4] MUST support the <code>android.hardware.ImageFormat.YUV_420_888</code> and <code>android.hardware.ImageFormat.JPEG</code> formats as outputs through the <code>android.media.ImageReader</code> API for <code>android.hardware.camera2</code> devices that advertise <a href="https://developer.android.com/reference/android/hardware/camera2/CameraMetadata.html#REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE"><code>REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE</code></a> capability in <a href="https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#REQUEST_AVAILABLE_CAPABILITIES"><code>android.request.availableCapabilities</code></a>. </li> <li>[C-0-5] MUST still implement the full <a href="http://developer.android.com/reference/android/hardware/Camera.html">Camera API</a> included in the Android SDK documentation, regardless of whether the device includes hardware autofocus or other capabilities. For instance, cameras that lack autofocus MUST still call any registered <code>android.hardware.Camera.AutoFocusCallback</code> instances (even though this has no relevance to a non-autofocus camera.) Note that this does apply to front-facing cameras; for instance, even though most front-facing cameras do not support autofocus, the API callbacks must still be “faked” as described. </li> @@ -8309,7 +8280,7 @@ If device implementations do not include a speaker or audio output port, they: </p> <ul> - <li>[C-2-1] MUST NOT report the <code>android.hardware.audio output</code> feature. + <li>[C-2-1] MUST NOT report the <code>android.hardware.audio.output</code> feature. </li> <li>[C-2-2] MUST implement the Audio Output related APIs as no-ops at least. </li> @@ -8431,7 +8402,7 @@ </li> <li>[C-1-7] The GPU and display MUST be able to synchronize access to the shared front buffer such that alternating-eye rendering of VR content at 60fps with two render contexts will be displayed with no visible tearing artifacts. </li> - <li>[C-1-8] MUST implement <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_multisampled_render_to_texture.txt"><code>GL_EXT_multisampled_render_to_texture</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview.txt"><code>GL_OVR_multiview</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview2.txt"><code>GL_OVR_multiview2</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview_multisampled_render_to_texture.txt"><code>GL_OVR_multiview_multisampled_render_to_texture</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_protected_textures.txt"><code>GL_EXT_protected_textures</code></a>, and expose the extensions in the list of available GL extensions. + <li>[C-1-8] MUST implement <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_multisampled_render_to_texture.txt"><code>GL_EXT_multisampled_render_to_texture</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview.txt"><code>GL_OVR_multiview</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview2.txt"><code>GL_OVR_multiview2</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview_multisampled_render_to_texture.txt"><code>GL_OVR_multiview_multisampled_render_to_texture</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_protected_textures.txt"><code>GL_EXT_protected_textures</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_EGL_image_array.txt"><code>GL_EXT_EGL_image_array</code></a>, <a href="https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_external_buffer.txt"><code>GL_EXT_external_buffer</code></a>, and expose the extensions in the list of available GL extensions. </li> <li>[C-1-9] MUST implement support for <a href="https://developer.android.com/ndk/reference/hardware__buffer_8h.html"><code>AHardwareBuffer</code></a> flags <code>AHARDWAREBUFFER_USAGE_GPU_DATA_BUFFER</code> and <code>AHARDWAREBUFFER_USAGE_SENSOR_DIRECT_DATA</code> as described in the NDK. </li> @@ -8445,17 +8416,39 @@ </li> <li>[C-1-14] MUST have an embedded screen, and its resolution MUST be at least be FullHD(1080p) and STRONGLY RECOMMENDED TO BE be QuadHD (1440p) or higher. </li> - <li>[C-1-15] The display MUST measure between 4.7" and 6.3" diagonal. + <li>[C-1-15] The display MUST update at least 60 Hz while in VR Mode. </li> - <li>[C-1-16] The display MUST update at least 60 Hz while in VR Mode. + <li>[C-1-16] The display latency (as measured on Gray-to-Gray, White-to-Black, and Black-to-White switching time) MUST be ≤ 6 milliseconds. </li> - <li>[C-1-17] The display latency on Gray-to-Gray, White-to-Black, and Black-to-White switching time MUST be ≤ 3 ms. + <li>[C-1-17] The display MUST support a low-persistence mode with ≤ 5 milliseconds persistence, persistence being defined as the amount of time for which a pixel is emitting light. </li> - <li>[C-1-18] The display MUST support a low-persistence mode with ≤5 ms persistence, persistence being defined as the amount of time for which a pixel is emitting light. + <li>[C-1-18] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension <a href="#7_4_3_bluetooth">section 7.4.3</a>. </li> - <li>[C-1-19] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension <a href="#7_4_3_bluetooth">section 7.4.3</a>. + <li>[C-1-19] MUST support and properly report <a href='https://developer.android.com/reference/android/hardware/Sensor.html#isDirectChannelTypeSupported%28int%29"'>Direct Channel Type</a> for all of the following default sensor types: + <ul> + <li> + <code>TYPE_ACCELEROMETER</code> + </li> + <li> + <code>TYPE_ACCELEROMETER_UNCALIBRATED</code> + </li> + <li> + <code>TYPE_GYROSCOPE</code> + </li> + <li> + <code>TYPE_GYROSCOPE_UNCALIBRATED</code> + </li> + <li> + <code>TYPE_MAGNETIC_FIELD</code> + </li> + <li> + <code>TYPE_MAGNETIC_FIELD_UNCALIBRATED</code> + </li> + </ul> </li> - <li>[SR] STRONGLY RECOMMENDED to support <code>android.hardware.sensor.hifi_sensors</code> feature and MUST meet the gyroscope, accelerometer, and magnetometer related requirements for <code>android.hardware.hifi_sensors</code>. + <li>[C-1-20] MUST support the <a href="https://developer.android.com/reference/android/hardware/SensorDirectChannel.html#TYPE_HARDWARE_BUFFER"><code>TYPE_HARDWARE_BUFFER</code></a> direct channel type for all Direct Channel Types listed above. + </li> + <li>[SR] Are STRONGLY RECOMMENDED to support <code>android.hardware.sensor.hifi_sensors</code> feature and MUST meet the gyroscope, accelerometer, and magnetometer related requirements for <code>android.hardware.hifi_sensors</code>. </li> <li>MAY provide an exclusive core to the foreground application and MAY support the <code>Process.getExclusiveCores</code> API to return the numbers of the cpu cores that are exclusive to the top foreground application. If exclusive core is supported then the core MUST not allow any other userspace processes to run on it (except device drivers used by the application), but MAY allow some kernel processes to run as necessary. </li> @@ -8937,6 +8930,13 @@ <li>[C-2-1] MUST ask for the user's consent before enabling that mechanism, unless that VPN is enabled by the Device Policy Controller via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setAlwaysOnVpnPackage%28android.content.ComponentName,%20java.lang.String,%20boolean%29"><code>DevicePolicyManager.setAlwaysOnVpnPackage()</code></a> , in which case the user does not need to provide a separate consent, but MUST only be notified. </li> </ul> + <p> + If device implementations implement a user affordance to toggle on the "always-on VPN" function of a 3rd-party VPN app, they: + </p> + <ul> + <li>[C-3-1] MUST disable this user affordance for apps that do not support always-on VPN service in the <code>AndroidManifest.xml</code> file via setting the <a href="https://developer.android.com/reference/android/net/VpnService.html#SERVICE_META_DATA_SUPPORTS_ALWAYS_ON"><code>SERVICE_META_DATA_SUPPORTS_ALWAYS_ON</code></a> attribute to <code>false</code>. + </li> + </ul> <h3 id="9_9_data_storage_encryption"> 9.9. Data Storage Encryption </h3> @@ -9043,11 +9043,11 @@ </li> <li>[C-1-2] MUST use a default passcode to wrap the encryption key and MUST NOT write the encryption key to storage at any time without being encrypted. </li> - <li>[C-1-3] MUST provide the user the possibility to AES encrypt the encryption key, except when it is in active use, with the lock screen credentials stretched using a slow stretching algorithm (e.g. PBKDF2 or scrypt). + <li>[C-1-3] MUST AES encrypt the encryption key by default unless the user explicitly opts out, except when it is in active use, with the lock screen credentials stretched using a slow stretching algorithm (e.g. PBKDF2 or scrypt). </li> <li>[C-1-4] The above default password stretching algorithm MUST be cryptographically bound to that keystore when the user has not specified a lock screen credentials or has disabled use of the passcode for encryption and the device provides a hardware-backed keystore. </li> - <li>[C-1-5] MUST NOT send encryption key off the device (even when wrapped with the user passcode and/or hardware bound key). + <li>[C-1-5] MUST NOT send encryption key off the the device (even when wrapped with the user passcode and/or hardware bound key). </li> </ul> <p> @@ -9069,17 +9069,17 @@ <ul> <li>[C-1-1] MUST declare the platform feature flag <code>android.software.verified_boot</code>. </li> - <li>[C-2-1] MUST perform verification on every boot sequence. + <li>[C-1-2] MUST perform verification on every boot sequence. </li> - <li>[C-3-1] MUST start verification from an immutable hardware key that is the root of trust and go all the way up to the system partition. + <li>[C-1-3] MUST start verification from an immutable hardware key that is the root of trust and go all the way up to the system partition. </li> - <li>[C-4-1] MUST implement each stage of verification to check the integrity and authenticity of all the bytes in the next stage before executing the code in the next stage. + <li>[C-1-4] MUST implement each stage of verification to check the integrity and authenticity of all the bytes in the next stage before executing the code in the next stage. </li> - <li>[C-5-1] MUST use verification algorithms as strong as current recommendations from NIST for hashing algorithms (SHA-256) and public key sizes (RSA-2048). + <li>[C-1-5] MUST use verification algorithms as strong as current recommendations from NIST for hashing algorithms (SHA-256) and public key sizes (RSA-2048). </li> - <li>[C-6-1] MUST NOT allow boot to complete when system verification fails, unless the user consents to attempt booting anyway, in which case the data from any non-verified storage blocks MUST not be used. + <li>[C-1-6] MUST NOT allow boot to complete when system verification fails, unless the user consents to attempt booting anyway, in which case the data from any non-verified storage blocks MUST not be used. </li> - <li>[C-7-1] MUST NOT allow verified partitions on the device to be modified unless the user has explicitly unlocked the boot loader. + <li>[C-1-7] MUST NOT allow verified partitions on the device to be modified unless the user has explicitly unlocked the boot loader. </li> <li>[SR] If there are multiple discrete chips in the device (e.g. radio, specialized image processor), the boot process of each of those chips is STRONGLY RECOMMENDED to verify every stage upon booting. </li> @@ -9096,10 +9096,10 @@ The upstream Android Open Source Project provides a preferred implementation of this feature in the <a href="http://android.googlesource.com/platform/external/avb/"><code>external/avb/</code></a> repository, which can be integrated into the boot loader used for loading Android. </p> <p> - Device implementations with Advanced Encryption Standard (AES) crypto performance above 50 MiB/seconds: + If device implementations report the feature flag <a href="https://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_RAM_NORMAL"><code>android.hardware.ram.normal</code></a> , they: </p> <ul> - <li>[C-8-1] MUST support verified boot for device integrity. + <li>[C-2-1] MUST support verified boot for device integrity. </li> </ul> <p> @@ -9127,7 +9127,7 @@ </li> <li>[C-1-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the <a href="https://source.android.com/security/trusty/">Trusty</a> implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options. </li> - <li>[C-1-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. The upstream Android Open Source Project provides the <a href="http://source.android.com/devices/tech/security/authentication/gatekeeper.html">Gatekeeper Hardware Abstraction Layer (HAL)</a> and Trusty, which can be used to satisfy this requirement. + <li>[C-1-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the <a href="http://source.android.com/devices/tech/security/authentication/gatekeeper.html">Gatekeeper Hardware Abstraction Layer (HAL)</a> and Trusty, which can be used to satisfy this requirement. </li> <li>[C-1-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units. </li> @@ -9198,20 +9198,29 @@ </li> <li>[C-5-3] MUST have a false acceptance rate that is equal or stronger than what is required for a fingerprint sensor as described in section 7.3.10, or otherwise MUST be disabled and only allow the primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the password quality policy via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordQuality%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setPasswordQuality()</code></a> method with a more restrictive quality constant than <code>PASSWORD_QUALITY_BIOMETRIC_WEAK</code>. </li> - <li>[C-5-4] The user MUST be challenged for the primary authentication (e.g.PIN, pattern, password) at least once every 72 hours or less. + <li>[SR] Are STRONGLY RECOMMENDED to have spoof and imposter acceptance rates that are equal to or stronger than what is required for a fingerprint sensor as described in section 7.3.10. + </li> + </ul> + <p> + If the spoof and imposter acceptance rates are not equal to or stronger than what is required for a fingerprint sensor as described in <a href="#7_3_10_fingerprint_sensor">section 7.3.10</a> and the Device Policy Controller (DPC) application has set the password quality policy via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordQuality%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setPasswordQuality()</code></a> method with a more restrictive quality constant than <code>PASSWORD_QUALITY_BIOMETRIC_WEAK</code>, then: + </p> + <ul> + <li>[C-6-1] MUST disable these biometric methods and allow only the primary authentication to unlock the screen. + </li> + <li>[C-6-2] MUST challenge the user for the primary authentication (e.g.PIN, pattern, password) at least once every 72 hours or less. </li> </ul> <p> If device implementations add or modify the authentication methods to unlock the lock screen and if such an authentication method will be used to unlock the keyguard, but will not be treated as a secure lock screen, then they: </p> <ul> - <li>[C-6-1] MUST return <code>false</code> for both the <a href="http://developer.android.com/reference/android/app/KeyguardManager.html#isKeyguardSecure%28%29"><code>KeyguardManager.isKeyguardSecure()</code></a> and the <a href="https://developer.android.com/reference/android/app/KeyguardManager.html#isDeviceSecure%28%29"><code>KeyguardManager.isDeviceSecure()</code></a> methods. + <li>[C-7-1] MUST return <code>false</code> for both the <a href="http://developer.android.com/reference/android/app/KeyguardManager.html#isKeyguardSecure%28%29"><code>KeyguardManager.isKeyguardSecure()</code></a> and the <a href="https://developer.android.com/reference/android/app/KeyguardManager.html#isDeviceSecure%28%29"><code>KeyguardManager.isDeviceSecure()</code></a> methods. </li> - <li>[C-6-2] MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordQuality%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setPasswordQuality()</code></a> method with a more restrictive quality constant than <code>PASSWORD_QUALITY_UNSPECIFIED</code>. + <li>[C-7-2] MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordQuality%28android.content.ComponentName,%20int%29"><code>DevicePolicyManager.setPasswordQuality()</code></a> method with a more restrictive quality constant than <code>PASSWORD_QUALITY_UNSPECIFIED</code>. </li> - <li>[C-6-3] MUST NOT reset the password expiration timers set by <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordExpirationTimeout%28android.content.ComponentName,%20long%29"><code>DevicePolicyManager.setPasswordExpirationTimeout()</code></a>. + <li>[C-7-3] MUST NOT reset the password expiration timers set by <a href="http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#setPasswordExpirationTimeout%28android.content.ComponentName,%20long%29"><code>DevicePolicyManager.setPasswordExpirationTimeout()</code></a>. </li> - <li>[C-6-4] MUST NOT authenticate access to keystores if the application has called <a href="https://developer.android.com/reference/android/security/keystore/KeyGenParameterSpec.Builder.html#setUserAuthenticationRequired%28boolean%29"><code>KeyGenParameterSpec.Builder.setUserAuthenticationRequired(true)</code></a>). + <li>[C-7-4] MUST NOT authenticate access to keystores if the application has called <a href="https://developer.android.com/reference/android/security/keystore/KeyGenParameterSpec.Builder.html#setUserAuthenticationRequired%28boolean%29"><code>KeyGenParameterSpec.Builder.setUserAuthenticationRequired(true)</code></a>). </li> </ul> <h3 id="9_12_data_deletion"> @@ -9296,7 +9305,7 @@ Device implementations MUST pass the <a href="http://source.android.com/compatibility/index.html">Android Compatibility Test Suite (CTS)</a> available from the Android Open Source Project, using the final shipping software on the device. Additionally, device implementers SHOULD use the reference implementation in the Android Open Source tree as much as possible, and MUST ensure compatibility in cases of ambiguity in CTS and for any reimplementations of parts of the reference source code. </p> <p> - The CTS is designed to be run on an actual device. Like any software, the CTS may itself contain bugs. The CTS will be versioned independently of this Compatibility Definition, and multiple revisions of the CTS may be released for Android 8.0. Device implementations MUST pass the latest CTS version available at the time the device software is completed. + The CTS is designed to be run on an actual device. Like any software, the CTS may itself contain bugs. The CTS will be versioned independently of this Compatibility Definition, and multiple revisions of the CTS may be released for Android 8.1. Device implementations MUST pass the latest CTS version available at the time the device software is completed. </p> <h3 id="10_2_cts_verifier"> 10.2. CTS Verifier @@ -9353,7 +9362,7 @@ </p> <ul> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/?pretty=full&no-merges">Document changelog</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/?pretty=full&no-merges">Document changelog</a> </li> </ul> <p> @@ -9361,43 +9370,43 @@ </p> <ol> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/1_introduction?pretty=full&no-merges">Introduction</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/1_introduction?pretty=full&no-merges">Introduction</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/2_device_types?pretty=full&no-merges">Device Types</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/2_device_types?pretty=full&no-merges">Device Types</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/3_software?pretty=full&no-merges">Software</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/3_software?pretty=full&no-merges">Software</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/4_application-packaging?pretty=full&no-merges">Application Packaging</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/4_application-packaging?pretty=full&no-merges">Application Packaging</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/5_multimedia?pretty=full&no-merges">Multimedia</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/5_multimedia?pretty=full&no-merges">Multimedia</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/6_dev-tools-and-options?pretty=full&no-merges">Developer Tools and Options</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/6_dev-tools-and-options?pretty=full&no-merges">Developer Tools and Options</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/7_hardware-compatibility?pretty=full&no-merges">Hardware Compatibility</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/7_hardware-compatibility?pretty=full&no-merges">Hardware Compatibility</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/8_performance-and-power?pretty=full&no-merges">Performance and Power</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/8_performance-and-power?pretty=full&no-merges">Performance and Power</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/9_security-model?pretty=full&no-merges">Security Model</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/9_security-model?pretty=full&no-merges">Security Model</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/10_software-compatibility-testing?pretty=full&no-merges">Software Compatibility Testing</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/10_software-compatibility-testing?pretty=full&no-merges">Software Compatibility Testing</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/11_updatable-software?pretty=full&no-merges">Updatable Software</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/11_updatable-software?pretty=full&no-merges">Updatable Software</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/12_document-changelog?pretty=full&no-merges">Document Changelog</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/12_document-changelog?pretty=full&no-merges">Document Changelog</a> </li> <li> - <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-dev/13_contact-us?pretty=full&no-merges">Contact Us</a> + <a href="https://android.googlesource.com/platform/compatibility/cdd/+log/oreo-mr1-dev/13_contact-us?pretty=full&no-merges">Contact Us</a> </li> </ol> <h3 id="12_1_changelog_viewing_tips"> diff --git a/en/compatibility/cdd.html b/en/compatibility/cdd.html index 59bfbafe..c5dd7314 100644 --- a/en/compatibility/cdd.html +++ b/en/compatibility/cdd.html @@ -71,6 +71,12 @@ You may view the latest CDD either as an HTML web page or an easily downloadable <th>Strings</th> </tr> <tr> + <td>8.1</td> + <td><a href="8.1/android-8.1-cdd.pdf">android-8.1-cdd.pdf</a></td> + <td><a href="8.1/android-8.1-cdd.html">android-8.1-cdd.html</a></td> + <td><a href="8.1/versions.html">Version 8.1</a></td> + </tr> + <tr> <td>8.0</td> <td><a href="8.0/android-8.0-cdd.pdf">android-8.0-cdd.pdf</a></td> <td><a href="8.0/android-8.0-cdd.html">android-8.0-cdd.html</a></td> diff --git a/en/compatibility/cts/downloads.html b/en/compatibility/cts/downloads.html index d6741f03..19635ca1 100644 --- a/en/compatibility/cts/downloads.html +++ b/en/compatibility/cts/downloads.html @@ -28,6 +28,25 @@ you access to key documents and information about the program. As CTS is updated, new versions are added to this page. CTS versions are denoted by R<number> in the link name.</p> +<h2 id="android-81">Android 8.1</h2> +<p>Android 8.1 is the release of the development milestone code-named Oreo-MR1. +The source code for the following tests can be synced with the +'android-cts-8.1_r1' tag in the open-source tree.</p> +<ul> +<li><a +href="https://dl.google.com/dl/android/cts/android-cts-8.1_r1-linux_x86-arm.zip">Android +8.1 R1 Compatibility Test Suite (CTS) - ARM</a></li> +<li><a +href="https://dl.google.com/dl/android/cts/android-cts-8.1_r1-linux_x86-x86.zip">Android +8.1 R1 Compatibility Test Suite (CTS) - x86</a></li> +<li><a +href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.1_r1-linux_x86-arm.zip">Android +8.1 R1 CTS Verifier - ARM</a></li> +<li><a +href="https://dl.google.com/dl/android/cts/android-cts-verifier-8.1_r1-linux_x86-x86.zip">Android +8.1 R1 CTS Verifier - x86</a></li> +</ul> + <h2 id="android-80">Android 8.0</h2> <p>Android 8.0 is the release of the development milestone code-named Oreo. The source code for the following tests can be synced with the diff --git a/en/devices/_toc-interfaces.yaml b/en/devices/_toc-interfaces.yaml index a7958fc3..0a5ce26f 100644 --- a/en/devices/_toc-interfaces.yaml +++ b/en/devices/_toc-interfaces.yaml @@ -155,6 +155,8 @@ toc: path: /devices/audio/data_formats - title: Attributes path: /devices/audio/attributes + - title: AAudio and MMAP + path: /devices/audio/aaudio - title: Warmup path: /devices/audio/warmup - title: Latency diff --git a/en/devices/_toc-tech.yaml b/en/devices/_toc-tech.yaml index dd7e48a2..9daad091 100644 --- a/en/devices/_toc-tech.yaml +++ b/en/devices/_toc-tech.yaml @@ -37,6 +37,8 @@ toc: path: /devices/tech/config/perms-whitelist - title: Runtime Permissions path: /devices/tech/config/runtime_perms + - title: Time Zone Rules + path: /devices/tech/config/timezone-rules - title: UICC path: /devices/tech/config/uicc - title: USB HAL @@ -63,6 +65,8 @@ toc: path: /devices/tech/connect/connect_tests - title: Radio Interface Layer (RIL) path: /devices/tech/connect/ril + - title: Wi-Fi Aware + path: /devices/tech/connect/wifi-aware - title: Data Usage section: - title: Overview @@ -147,6 +151,8 @@ toc: path: /devices/tech/display/app-shortcuts - title: Circular Icons path: /devices/tech/display/circular-icons + - title: Color Management + path: /devices/tech/display/color-mgmt - title: Do Not Disturb path: /devices/tech/display/dnd - title: HDR Video @@ -161,6 +167,8 @@ toc: path: /devices/tech/display/retail-mode - title: Split-Screen Interactions path: /devices/tech/display/split-screen + - title: TEXTCLASSIFIER + path: /devices/tech/display/textclassifier - title: Widgets & Shortcuts path: /devices/tech/display/widgets-shortcuts - title: OTA Updates diff --git a/en/devices/architecture/hidl-cpp/index.html b/en/devices/architecture/hidl-cpp/index.html index f42d8f8a..7d8466cb 100644 --- a/en/devices/architecture/hidl-cpp/index.html +++ b/en/devices/architecture/hidl-cpp/index.html @@ -92,11 +92,13 @@ hidl-gen -o $LOC -Landroidbp-impl -randroid.hardware:hardware/interfaces \ <p>For the HAL to work in passthrough mode (for legacy devices), you must have the function <em>HIDL_FETCH_IModuleName</em> residing in -<code>/system/lib(64)?/hw/android.hardware.package@3.0-impl(-$OPTIONAL_IDENTIFIER).so</code> +<code>/system/lib(64)?/hw/android.hardware.package@3.0-impl($OPTIONAL_IDENTIFIER).so</code> where <code>$OPTIONAL_IDENTIFIER</code> is a string identifying the passthrough implementation. The passthrough mode requirements are met automatically by the above commands, which also create the <code>android.hardware.nfc@1.0-impl</code> -target.</p> +target, but any extension can be used. For instance +<code>android.hardware.nfc@1.0-impl-foo</code> uses <code>-foo</code> to +differentiate itself.</p> <p>Next, fill out the stubs with functionality and setup a daemon. Example daemon code (supporting passthrough):</p> diff --git a/en/devices/architecture/hidl/hashing.html b/en/devices/architecture/hidl/hashing.html index e083fd4c..3debea85 100644 --- a/en/devices/architecture/hidl/hashing.html +++ b/en/devices/architecture/hidl/hashing.html @@ -151,6 +151,8 @@ interfaces which maintain ABI stability. Review the following types of changes: <td> <ul> <li>Reordering arguments, methods, etc…</li> +<li>Renaming an interface or moving it to a new package.</li> +<li>Renaming a package.</li> <li>Adding a method/struct field/etc… anywhere in the interface.</li> <li>Anything that would break a C++ vtable.</li> <li>etc..</li> diff --git a/en/devices/architecture/images/treble_latency_bubble.png b/en/devices/architecture/images/treble_latency_bubble.png Binary files differnew file mode 100644 index 00000000..72a83c05 --- /dev/null +++ b/en/devices/architecture/images/treble_latency_bubble.png diff --git a/en/devices/architecture/images/treble_priority_inv_rta.png b/en/devices/architecture/images/treble_priority_inv_rta.png Binary files differnew file mode 100644 index 00000000..5ece38be --- /dev/null +++ b/en/devices/architecture/images/treble_priority_inv_rta.png diff --git a/en/devices/architecture/images/treble_priority_inv_rta_blocked.png b/en/devices/architecture/images/treble_priority_inv_rta_blocked.png Binary files differnew file mode 100644 index 00000000..fe218529 --- /dev/null +++ b/en/devices/architecture/images/treble_priority_inv_rta_blocked.png diff --git a/en/devices/architecture/images/treble_systrace_binder_processes.png b/en/devices/architecture/images/treble_systrace_binder_processes.png Binary files differnew file mode 100644 index 00000000..425dcd07 --- /dev/null +++ b/en/devices/architecture/images/treble_systrace_binder_processes.png diff --git a/en/devices/audio/aaudio.html b/en/devices/audio/aaudio.html new file mode 100644 index 00000000..fb62ab87 --- /dev/null +++ b/en/devices/audio/aaudio.html @@ -0,0 +1,359 @@ +<html devsite> + <head> + <title>AAudio and MMAP</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + +<p> +AAudio is an audio API introduced in the Android 8.0 release. The Android 8.1 +release has enhancements to reduce latency when used in conjunction with a HAL +and driver that support MMAP. This document describes the hardware abstraction +layer (HAL) and driver changes needed to support AAudio's MMAP feature in +Android. +</p> + +<p> +Support for AAudio MMAP requires: +</p> + +<ul> +<li>reporting the MMAP capabilities of the HAL +<li>implementing new functions in the HAL +<li>optionally implementing a custom ioctl() for the EXCLUSIVE mode buffer +<li>providing an additional hardware data path</li> +<li>setting system properties that enable MMAP feature</li> +</ul> + +<aside class="note"><strong>Note:</strong> Enable the MMAP feature +only on Android O MR1 or higher.</aside> + +<h2 id="aaudio-architecture">AAudio architecture</h2> + +<p> +<a +href="https://developer.android.com/ndk/guides/audio/aaudio/aaudio.html">AAudio</a> +is a new native C API that provides an alternative to Open SL ES. It uses a +Builder design pattern to create audio streams. +</p> + +<p> +AAudio provides a low-latency data path. In EXCLUSIVE mode, the feature +allows client application code to write directly into a memory mapped buffer +that is shared with the ALSA driver. In SHARED mode, the MMAP buffer is used by +a mixer running in the AudioServer. In EXCLUSIVE mode, the latency is +significantly less because the data bypasses the mixer. +</p> + +<p> +In EXCLUSIVE mode, the service requests the MMAP buffer from the HAL and manages +the resources. The MMAP buffer is running in NOIRQ mode, so there are no shared +read/write counters to manage access to the buffer. Instead, the client +maintains a timing model of the hardware and predicts when the buffer will be +read. +</p> + +<p> +In the diagram below, we can see the Pulse-code modulation (PCM) data flowing +down through the MMAP FIFO into the ALSA driver. Timestamps are periodically +requested by the AAudio service and then passed up to the client's timing model +through an atomic message queue. +</p> + +<figure id="pcm-data-flow"> + <img src="/devices/audio/images/pcm_data_flow.png" + width="630" + alt="PCM data flow diagram."> + <figcaption><b>Figure 1.</b> PCM data flow through FIFO to ALSA</figcaption> +</figure> + +<p> +In SHARED mode, a timing model is also used, but it lives in the AAudioService. +</p> + +<p> +For audio capture, a similar model is used, but the PCM data flows in the +opposite direction. +</p> + +<h2 id="hal-changes">HAL changes</h2> +<p> +For tinyALSA see: +</p> + +<pre +class="prettyprint"> +external/tinyalsa/include/tinyalsa/asoundlib.h +external/tinyalsa/include/tinyalsa/pcm.c +</pre> + +<pre +class="prettyprint"> +int pcm_start(struct pcm *pcm); +int pcm_stop(struct pcm *pcm); +int pcm_mmap_begin(struct pcm *pcm, void **areas, + unsigned int *offset, + unsigned int *frames); +int pcm_get_poll_fd(struct pcm *pcm); +int pcm_mmap_commit(struct pcm *pcm, unsigned int offset, + unsigned int frames); +int pcm_mmap_get_hw_ptr(struct pcm* pcm, unsigned int *hw_ptr, + struct timespec *tstamp); +</pre> + +<p> +For the legacy HAL, see: +</p> + +<pre +class="prettyprint"> +hardware/libhardware/include/hardware/audio.h +hardware/qcom/audio/hal/audio_hw.c +</pre> + +<pre +class="prettyprint"> +int start(const struct audio_stream_out* stream); +int stop(const struct audio_stream_out* stream); +int create_mmap_buffer(const struct audio_stream_out *stream, + int32_t min_size_frames, + struct audio_mmap_buffer_info *info); +int get_mmap_position(const struct audio_stream_out *stream, + struct audio_mmap_position *position); +</pre> + +<p> +For HIDL audio HAL: +</p> + +<pre +class="prettyprint"> +hardware/interfaces/audio/2.0/IStream.hal +hardware/interfaces/audio/2.0/types.hal +hardware/interfaces/audio/2.0/default/Stream.h +</pre> + +<pre +class="prettyprint"> +start() generates (Result retval); +stop() generates (Result retval) ; +createMmapBuffer(int32_t minSizeFrames) + generates (Result retval, MmapBufferInfo info); +getMmapPosition() + generates (Result retval, MmapPosition position); +</pre> + +<h3 id="reporting-mmap-support">Reporting MMAP support</h3> + +<p> +System property "aaudio.mmap_policy" should be set to 2 (AAUDIO_POLICY_AUTO) so +the audio framework knows that MMAP mode is supported by the audio HAL. (see +"Enabling AAudio MMAP Data Path" below.) +</p> + +<p> +audio_policy_configuration.xml file must also contain an output and input +profile specific to MMAP/NO IRQ mode so that the Audio Policy Manager knows +which stream to open when MMAP clients are created: +</p> + +<pre +class="prettyprint"> +<mixPort name="mmap_no_irq_out" role="source" + flags="AUDIO_OUTPUT_FLAG_DIRECT|AUDIO_OUTPUT_FLAG_MMAP_NOIRQ"> + <profile name="" format="AUDIO_FORMAT_PCM_16_BIT" + samplingRates="48000" + channelMasks="AUDIO_CHANNEL_OUT_STEREO"/> +</mixPort> + +<mixPort name="mmap_no_irq_in" role="sink" flags="AUDIO_INPUT_FLAG_MMAP_NOIRQ"> + <profile name="" format="AUDIO_FORMAT_PCM_16_BIT" + samplingRates="48000" + channelMasks="AUDIO_CHANNEL_IN_STEREO"/> +</mixPort> +</pre> + +<h3 id="opening-and-closing-an-mmap-stream">Opening and closing an MMAP +stream</h3> + +<pre +class="prettyprint"> +createMmapBuffer(int32_t minSizeFrames) + generates (Result retval, MmapBufferInfo info); +</pre> + +<p> +The MMAP stream can be opened and closed by calling Tinyalsa functions. +</p> + +<h3 id="querying-mmap-position">Querying MMAP position</h3> + +<p> +The timestamp passed back to the Timing Model contains a frame position and a +MONOTONIC time in nanoseconds: +</p> + +<pre +class="prettyprint"> +getMmapPosition() + generates (Result retval, MmapPosition position); +</pre> + +<p> +The HAL can obtain this information from the ALSA driver by calling a new +Tinyalsa function: +</p> + +<pre +class="prettyprint"> +int pcm_mmap_get_hw_ptr(struct pcm* pcm, + unsigned int *hw_ptr, + struct timespec *tstamp); +</pre> + +<h2 id="kernel-changes">Kernel changes</h2> + +<p> +Enable MMAP/NOIRQ mode in the driver. +</p> + +<p> +The shared memory is referenced using a file descriptor that is generated by the +ALSA driver. If the file descriptor is directly associated with a +<code>/dev/snd/</code> driver file, then it can be used by the AAudio service in +SHARED mode. But the descriptor cannot be passed to the client code for +EXCLUSIVE mode. The <code>/dev/snd/</code> file descriptor would provide too +broad of access to the client, so it is blocked by SELinux. +</p> + +<p> +In order to support EXCLUSIVE mode, it is necessary to convert the +<code>/dev/snd/</code> descriptor to an <code>anon_inode:dmabuffer</code> file +descriptor. SELinux allows that file descriptor to be passed to the client. It +can also be used by the AAudioService. +</p> + +<p> +An <code>anon_inode:dmabuffer</code> file descriptor can be generated using the +Android Ion memory library. +</p> + +<p> +For additional information, see these external resources: +</p> + +<ol> +<li>"The Android ION memory allocator" <a +href="https://lwn.net/Articles/480055/">https://lwn.net/Articles/480055/</a> +<li>"Android ION overview" <a +href="https://wiki.linaro.org/BenjaminGaignard/ion">https://wiki.linaro.org/BenjaminGaignard/ion</a> +<li>"Integrating the ION memory allocator" <a +href="https://lwn.net/Articles/565469/">https://lwn.net/Articles/565469/</a></li> +</ol> + +<p> +The AAudio service needs to know if this <code>anon_inode:dmabuffer</code> is +supported. Currently, the only way to do that is to pass the size of the MMAP +buffer as a negative number, eg. -2048 instead of 2048, if supported. A better +way of reporting this without having to open the stream is planned. +</p> + +<h2 id="audio-subsystem-changes">Audio subsystem changes</h2> + +<p> +AAudio requires an additional data path at the audio front end of the audio +subsystem so it can operate in parallel with the original AudioFlinger path. +That legacy path is used for all other system sounds and application sounds. +This functionality could be provided by a software mixer in a DSP or a hardware +mixer in the SOC. +</p> + +<h2 id="enabling-aaudio-mmap-data-path">Enabling AAudio MMAP Data Path</h2> + +<p> +AAudio will use the legacy AudioFlinger data path if MMAP is not supported or +fails to open a stream. So AAudio will work with an audio device that does not +support MMAP/NOIRQ path. +</p> + +<p> +When testing MMAP support for AAudio, it is important to know whether you are +actually testing the MMAP data path or merely testing the legacy data path. The +following describes how to enable or force specific data paths, and how to query +the path used by a stream. +</p> + +<h3 id="system-properties">System properties</h3> + +<p> +You can set the MMAP policy through system properties: +</p> + +<ul> +<li>1 = AAUDIO_POLICY_NEVER - Only use legacy path. Do not even try to use MMAP. +<li>2 = AAUDIO_POLICY_AUTO - Try to use MMAP. If that fails or is not available, +then use legacy path. +<li>3 = AAUDIO_POLICY_ALWAYS - Only use MMAP path. Do not fall back to legacy +path.</li> +</ul> + +<p> +These may be set in the devices Makefile, like so: +</p> + +<pre +class="prettyprint"> +# Enable AAudio MMAP/NOIRQ data path. +# 2 is AAUDIO_POLICY_AUTO so it will try MMAP then fallback to Legacy path. +PRODUCT_PROPERTY_OVERRIDES += aaudio.mmap_policy=2 +# Allow EXCLUSIVE then fall back to SHARED. +PRODUCT_PROPERTY_OVERRIDES += aaudio.mmap_exclusive_policy=2 +</pre> + +<p> +You can also override these values after the device has booted. For example, to +enable AUTO mode for MMAP: +</p> + +<pre class="devsite-terminal devsite-click-to-copy"> +adb root +</pre> +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell setprop aaudio.mmap_policy 2 +</pre> + +<p> +There are functions provided in +<code>ndk/sysroot/usr/include/aaudio/AAudioTesting.h</code> that allow you to +override the policy for using MMAP path: +</p> + +<pre +class="prettyprint">aaudio_result_t AAudio_setMMapPolicy(aaudio_policy_t policy); +</pre> + +<p> +To find out whether a stream is using MMAP path, call: +</p> + +<pre +class="prettyprint">bool AAudioStream_isMMapUsed(AAudioStream* stream); +</pre> +</body> +</html> diff --git a/en/devices/audio/images/pcm_data_flow.png b/en/devices/audio/images/pcm_data_flow.png Binary files differnew file mode 100644 index 00000000..2279e422 --- /dev/null +++ b/en/devices/audio/images/pcm_data_flow.png diff --git a/en/devices/audio/latency.html b/en/devices/audio/latency.html index 58b3024b..03dabb64 100644 --- a/en/devices/audio/latency.html +++ b/en/devices/audio/latency.html @@ -34,7 +34,8 @@ </tr> <tr> <td>Description of audio latency for purposes of Android compatibility</td> - <td><a href="/compatibility/android-cdd#5_6_audio_latency">Android CDD</a><br /><em>section 5.6 Audio Latency</em></td> + <td><a href="/compatibility/android-cdd#5_6_audio_latency">Android Compatibility Definition Document (CDD)</a><br /> + <em>section 5.6 Audio Latency</em></td> </tr> <tr> <td>Common causes of audio latency</td> @@ -60,6 +61,9 @@ <td>Applications</td> <td><a href="latency_app.html">Audio Latency for App Developers</a></td> </tr> +<tr> + <td>AAudio and MMAP</td> + <td><a href="aaudio.html">AAudio for OEMs and SoC Vendors</a></td> </table> </body> diff --git a/en/devices/audio/terminology.html b/en/devices/audio/terminology.html index 277b25e4..e691e285 100644 --- a/en/devices/audio/terminology.html +++ b/en/devices/audio/terminology.html @@ -94,7 +94,7 @@ Both PCM and DSD represent multiple channels by independent sequences. DSD is better suited to content distribution than as an internal representation for processing as it can be difficult to apply traditional digital signal processing (DSP) algorithms to DSD. DSD is used in <a href="http://en.wikipedia.org/wiki/Super_Audio_CD">Super Audio CD (SACD)</a> and in DSD over PCM (DoP) for USB. For details, refer -to <a href="http://en.wikipedia.org/wiki/Direct_Stream_Digital">Digital Stream +to <a href="http://en.wikipedia.org/wiki/Direct_Stream_Digital">Direct Stream Digital</a>. </dd> diff --git a/en/devices/graphics/arch-sh.html b/en/devices/graphics/arch-sh.html index 3b597abb..d581234e 100644 --- a/en/devices/graphics/arch-sh.html +++ b/en/devices/graphics/arch-sh.html @@ -83,8 +83,8 @@ will be handled by SurfaceFlinger or HWC; but since we need to only read from it, there's no need to wait for exclusive access.</p> <p>The main non-Canvas way for an application to draw directly on a Surface is -through OpenGL ES. That's described in the <a href="#eglsurface">EGLSurface and -OpenGL ES</a> section.</p> +through OpenGL ES (as described in the <a href="/devices/graphics/arch-egl-opengl">EGLSurface +and OpenGL ES</a> section).</p> <h2 id="surfaceholder">SurfaceHolder</h2> diff --git a/en/devices/graphics/renderer.html b/en/devices/graphics/renderer.html index 7ee28f10..fe0a0e79 100644 --- a/en/devices/graphics/renderer.html +++ b/en/devices/graphics/renderer.html @@ -25,6 +25,10 @@ <p>This document describes performance tuning that you can do to get the most out of your hardware.</p> +<p class="note"><strong>Note:</strong> In Android 8.1 and later, only the +<code>ro.zygote.disable_gl_preload</code> property still applies. All other +properties have been removed.</p> + <h2>OpenGLRenderer (libhwui) Properties</h2> <p>This document lists all the properties that you can use to control Android’s 2D hardware accelerated rendering pipeline. Set these properties diff --git a/en/devices/tech/config/images/tz_call_rulesmanagerservice.png b/en/devices/tech/config/images/tz_call_rulesmanagerservice.png Binary files differnew file mode 100644 index 00000000..65a1b2a9 --- /dev/null +++ b/en/devices/tech/config/images/tz_call_rulesmanagerservice.png diff --git a/en/devices/tech/config/images/tz_check_complete.png b/en/devices/tech/config/images/tz_check_complete.png Binary files differnew file mode 100644 index 00000000..efc8876a --- /dev/null +++ b/en/devices/tech/config/images/tz_check_complete.png diff --git a/en/devices/tech/config/images/tz_data_app_updates.png b/en/devices/tech/config/images/tz_data_app_updates.png Binary files differnew file mode 100644 index 00000000..108e4ec1 --- /dev/null +++ b/en/devices/tech/config/images/tz_data_app_updates.png diff --git a/en/devices/tech/config/images/tz_get_info_distro.png b/en/devices/tech/config/images/tz_get_info_distro.png Binary files differnew file mode 100644 index 00000000..70498a42 --- /dev/null +++ b/en/devices/tech/config/images/tz_get_info_distro.png diff --git a/en/devices/tech/config/images/tz_trigger_update.png b/en/devices/tech/config/images/tz_trigger_update.png Binary files differnew file mode 100644 index 00000000..cb9cb0a5 --- /dev/null +++ b/en/devices/tech/config/images/tz_trigger_update.png diff --git a/en/devices/tech/config/images/tz_version_check.png b/en/devices/tech/config/images/tz_version_check.png Binary files differnew file mode 100644 index 00000000..dd26a30e --- /dev/null +++ b/en/devices/tech/config/images/tz_version_check.png diff --git a/en/devices/tech/config/timezone-rules.html b/en/devices/tech/config/timezone-rules.html new file mode 100644 index 00000000..6a3f81ef --- /dev/null +++ b/en/devices/tech/config/timezone-rules.html @@ -0,0 +1,724 @@ +<html devsite> + <head> + <title>Time Zone Rules</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + +<p>Android 8.1 provides a new mechanism for OEMs to push updated time zone rules +data to devices without requiring a system update. This mechanism enables users +to receive timely updates (thus extending the useful lifetime of an Android +device) and enables OEMs to test time zone updates independently of system image +updates.</p> + +<p>The Android core libraries team will provide the necessary data files for +updating time zone rules on a stock Android device. OEMs can choose to use these +data files when creating time zone updates for their devices or can create their +own data files if preferred. In all cases, OEMs retain control over the quality +assurance/testing, timing, and launch of time zone rule updates for their +supported devices.</p> + +<h2 id="source-code">Android time zone source code and data</h2> +<p>All stock Android devices, even those not using this feature, need time zone +rules data and must ship with a default set of time zone rules data in the +<code>/system</code> partition. This data is then used by code from the +following libraries in the Android source tree: </p> + +<ul> +<li>Managed code from <code>libcore/</code> (e.g. +<code>java.util.TimeZone</code>) uses <code>tzdata</code> and +<code>tzlookup.xml</code> files.</li> +<li>Native library code in <code>bionic/</code> (e.g. for <code>mktime</code>, +localtime system calls) uses the <code>tzdata</code> file.</li> +<li>ICU4J/ICU4C library code in <code>external/icu/</code> uses the icu .dat +file.</li> +</ul> + +<p>These libraries are configured to be aware of overlay files that may be +present in the <code>/data/misc/zoneinfo/current</code> directory. Overlay files +are expected to contain improved time zone rules data thereby enabling devices +to be updated without changing <code>/system</code>.</p> + +<p>Android system components that need time zone rule data check the following +locations first:</p> + +<ul> +<li><code>libcore/</code> and <code>bionic/</code> code use the +<code>/data</code> copy of the <code>tzdata</code> and <code>tzlookup.xml</code> +files.</li> +<li>ICU4J/ICU4C code use the files in <code>/data</code> and fallback to +<code>/system</code> files for data that isn't present (for formats, localized +strings, etc.).</li> +</ul> + +<h2 id="distro-files">Distro files</h2> +<p>Distro .zip files contain the data files needed to populate the +<code>/data/misc/zoneinfo/current</code> directory. The distro file also +contains metadata that allows devices to detect versioning issues.</p> +<p>The distro file format is Android-release dependent because the contents +change with the ICU version, Android platform requirements, +etc. Android provides distro files for supported Android releases for every IANA +update (in addition to updating the platform system files). To keep their +devices up to date, OEMs can choose to take this distro file or create their own +distro file using the Android source tree (which contains the scripts and other +files needed to generate distro files).</p> + +<h2>Time zone update components</h2> +<p>A time zone rules update involves the transmission of a distro file to a +device and the safe installation of the files contained within. Transfer and +installation requires the following:</p> + +<ul> +<li>Platform service functionality +(<a href="https://android.googlesource.com/platform/frameworks/base/+/master/services/core/java/com/android/server/timezone/RulesManagerService.java">timezone.RulesManagerService</a>), +which is disabled by default. OEMs must enable the functionality via +configuration. The RulesManagerService runs in the system server process and +stages time zone update operations by writing to +<code>/data/misc/zoneinfo/staged</code>. It can also replace or delete already +staged operations.</li> +<li> +<a href="https://android.googlesource.com/platform/packages/apps/TimeZoneUpdater/">Time +Zone Updater</a>, a non-updateable system application (aka the <em>Updater +App</em>). OEMs must include this application in the system image of devices +using the feature.</li> +<li>OEM +<a href="https://android.googlesource.com/platform/packages/apps/TimeZoneData/">Time +Zone Data</a>, an updateable system application (aka the <em>Data App</em>) +that carries the distro file to the device and makes it available to the Updater +App. OEMs must include this application in the system image of devices using the +feature.</li> +<li> +<a href="https://android.googlesource.com/platform/system/timezone/+/master/tzdatacheck/">tzdatacheck</a>, +a boot-time binary required for the correct and safe operation of time zone +updates.</li> +</ul> + +<p>The Android source tree contains generic source code for the above +components, which the OEM can choose to use without modification. +<a href="https://android.googlesource.com/platform/packages/apps/TimeZoneData/+/master/testing/">Test +code</a> is provided to enable OEMs to automatically check that they have +enabled the feature correctly.</p> + +<h3 id="distro-install">Distro installation</h3> +<p>The distro installation process includes the following steps:</p> + +<ol> +<li><strong>Data App is updated</strong> via an app store download or +sideload. The system server process (via +<code>timezone.RulesManagerServer/timezone.PackageTracker</code> classes) +watches for changes to the configured, OEM-specific, Data App package +name. +<figure> +<img src="images/tz_data_app_updates.png" alt="Data app updates" +id="data-app-updates" /> +<figcaption><strong>Figure 1.</strong> Data App updates.</figcaption></figure> +</li> +<li><strong>System server process triggers an update check</strong> by +broadcasting a targeted intent with a unique, single-use token to the Updater +App. The system server keeps track of the most recent token it generated so it +can later tell when the most recent check it triggered has completed; any other +tokens are ignored. +<figure> +<img src="images/tz_trigger_update.png" alt="Trigger update" +id="trigger-update" /> +<figcaption><strong>Figure 2.</strong> Trigger update check.</figcaption> +</figure> +</li> +<li><strong>Update check</strong>, in which the Updater App performs the +following tasks: +<ul> +<li>Queries the current device state by calling the RulesManagerService. +<figure> +<img src="images/tz_call_rulesmanagerservice.png" alt="Call RulesManagerService" +id="call-rulesmanagerservice" /> +<figcaption><strong>Figure 3.</strong> Data App updates, calling +RulesManagerService.</figcaption></figure> +</li> +<li>Queries the Data App by querying a well-defined ContentProvider URL and +column specs to get information about the distro: +<figure> +<img src="images/tz_get_info_distro.png" alt="Get distro information" +id="get-distro-info" /> +<figcaption><strong>Figure 4.</strong> Data App updates, get info about distro. +</figcaption></figure> +</li> +</ul> +<li><strong>Updater App takes the appropriate action</strong> based on the +information it has. Available actions include: +<ul> +<li><em>Request an installation</em>. Distro data is read from the Data App +and is passed to the RulesManagerService in the system server. The +RulesManagerService re-confirms the distro format version and content is +appropriate for the device and stages the install.</li> +<li><em>Request an uninstall</em> (this is rare). For example, if the updated +.apk in <code>/data</code> is being disabled or uninstalled and the device is +returning to the version present in <code>/system</code>.</li> +<li><em>Do nothing</em>. Occurs when the Data App distro is found to be invalid. +</li> +</ul> +In all cases, the Updated App calls the RulesManagerService with the check token +so the system server knows the check is complete and successful. +<figure> +<img src="images/tz_check_complete.png" alt="Check complete" +id="check-complete" /> +<figcaption><strong>Figure 5.</strong> Check complete.</figcaption></figure> +</li> +<li><strong>Reboot and tzdatacheck</strong>. When the device next boots, +the tzdatacheck binary executes any staged operation. The tzdatacheck binary can +perform the following tasks: +<ul> +<li>Execute the staged operation by handling the creation, replacement, +and/or deletion of the <code>/data/misc/zoneinfo/current</code> files before +other system components have opened and started to use the files.</li> +<li>Check the files in <code>/data</code> are correct for the current platform +version, which might not be the case if the device has just received a system update +and the distro format version has changed.</li> +<li>Ensure the IANA rules version is the same or newer than the version in +<code>/system</code>. This protects against a system update leaving a device +with older time zone rules data than is present in the <code>/system</code> +image. +</li> +</ul> +</li> +</ol> + +<h3 id="reliability">Reliability</h3> +<p>The end-to-end installation process is asynchronous and split across three OS +processes. At any point during the installation, the device may lose power, run +out of disk space, etc., causing the installation check to not complete +successfully. In the best unsuccessful case, the Updater App is able to inform +the system server it was unsuccessful; in the worst unsuccessful case, the +RulesManagerService receives no call at all.</p> +<p>To handle this, the system server code keeps track of whether a triggered +update check has completed and what the last checked version code of the Data +App is. When the device is idle and charging, the system server code can check +the current state. If it discovers an incomplete update check or unexpected Data +App version, it spontaneously triggers an update check.</p> + +<h3 id="security">Security</h3> +<p>When enabled, the RulesManagerService code in the system server performs +several checks to ensure the system is safe to use.</p> +<ul> +<li>Problems that indicate a badly configured system image will prevent a +device booting; examples include a bad Updater or Data App configuration or the +Updater or Data App not being in <code>/system/priv-app</code>.</li> +<li>Problems that indicate a bad Data App has been installed will not prevent a +device booting but will prevent an update check being triggered; examples +include a lack of required system permissions or the Data App doesn't expose a +ContentProvider on the expected URI.</li> +</ul> + +<p>File permissions for the <code>/data/misc/zoneinfo</code> directories are +enforced via SELinux rules. As with any APK, the Data App must be signed by the +same key used to sign the <code>/system/priv-app</code> version. The Data App is +expected to have a dedicated, OEM-specific package name and key.</p> + +<h2 id="integrating">Integrating time zone updates</h2> +<p>To enable the time zone update feature, OEMs typically:</p> +<ul> +<li>Create their own Data App.</li> +<li>Include the Updater and Data Apps in the system image build.</li> +<li>Configure the system server to enable the RulesManagerService.</li> +</ul> + +<h3 id="preparing">Preparing</h3> +<p>Before starting, review the following policy, quality assurance, and security +considerations:</p> +<ul> +<li>OEMs should create a dedicated app-specific signing key for their Data +App.</li> +<li>OEMs should create a release and versioning strategy for time zone updates +to understand which devices are going to be updated and how they will ensure +updates are only installed on devices that need them. For example, OEMs may want +to have a single Data App for all their devices or may choose to have different +Data Apps for different devices. The decision impacts the choice of package +name, possibly the version codes used, and the QA strategy.</li> +<li>OEMs should understand whether they want to use stock Android timezone data +from AOSP or create their own.</li> +</ul> + +<h3 id="creating-data-app">Creating a Data App</h3> +<p>AOSP includes all source code and build rules needed to create a Data App in +<code>packages/apps/TimeZoneData</code>, with instructions and example templates +for <code>AndroidManifest.xml</code> and other files located in +<code>packages/apps/TimeZoneData/oem_template</code>. Example templates include +both a build target for the real Data App .apk file and extra targets for +creating test versions of the Data App.</p> +<p>OEMs can customize the Data App with their own icon, name, translations, +etc. However, as the Data App cannot be launched, the icon appears only in the +<em>Settings > Apps</em> screen.</p> +<p>The Data App is intended to be built with a <strong>tapas</strong> build +that produces .apks suitable to be added to the system image (for the initial +release) and signed and distributed via an app store (for subsequent updates). +For details on using tapas, see <a href="#building-tapas">Building the Data app +using tapas</a>.</p> + +<aside class="note"><strong>Note:</strong> Securely signing APKs and key +management is outside of the scope of this article.</aside> + +<p>OEMs must install the Data App prebuilt in the system image of a device in +<code>/system/priv-app</code>. To include prebuilt .apks (generated by the tapas +build process) in the system image, OEMs can copy the example files in +<code>packages/apps/TimeZoneData/oem_template/data_app_prebuilt</code>. The +example templates also include build targets for including test versions of the +Data App in test suites.</p> + +<h3 id="including">Including the Updater and Data Apps in the system image</h3> +<p>OEMs must place the Updater and Data App .apk files in the +<code>/system/priv-app</code> directory of the system image. To do this, the +system image build must explicitly include the Updater App and Data App prebuilt +targets.</p> +<p>The Updater App should be signed with the platform key and included as any +other system app. The target is defined in +<code>packages/apps/TimeZoneUpdater</code> as <code>TimeZoneUpdater</code>. The +Data App inclusion is OEM-specific and depends on the target name chosen for the +prebuild.</p> + +<h3 id="configuring-system-server">Configuring the system server</h3> +<p>To enable time zone updates, OEMs can configure the system server by +overriding configuration properties defined in +<code>frameworks/base/core/res/res/values/config.xml</code>.</p> + +<table> +<thead> +<tr> +<th>Property</th> +<th width="20%">Override Required?</th> +</tr> +</thead> +<tbody> +<tr> +<td> +<pre class="prettyprint">config_enableUpdateableTimeZoneRules</pre> +Must be set to true to enable the RulesManagerService.</td> +<td>Yes</td> +</tr> +<tr> +<td><pre class="prettyprint">config_timeZoneRulesUpdateTrackingEnabled</pre> +Must be set to true to have the system listen for changes to the Data App.</td> +<td>Yes</td> +</tr> +<tr> +<td><pre class="prettyprint">config_timeZoneRulesDataPackage</pre> +Package name of the OEM-specific Data App.</td> +<td>Yes</td> +</tr> +<tr> +<td><pre class="prettyprint">config_timeZoneRulesUpdaterPackage</pre> +Configured for the default Updater App. Change only when providing a different +Updater App implementation.</td> +<td>No</td> +</tr> +<tr> +<td><pre class="prettyprint">config_timeZoneRulesCheckTimeMillisAllowed</pre> +Time allowed between an update check being triggered by the RulesManagerService +and an install, uninstall, or do nothing response. After this point, a +spontaneous reliability trigger may be generated.</td> +<td>No</td> +</tr> +<tr> +<td><pre class="prettyprint">config_timeZoneRulesCheckRetryCount</pre> +The number of sequential unsuccessful update checks allowed before the +RulesManagerService stops generating more.</td> +<td>No</td> +</tr> +</tbody> +</table> + +<p>Configuration overrides should be in the system image (not vendor or other) +as a misconfigured device can refuse to boot. If the configuration overrides +were in <code>/vendor</code>, updating to a system image without a Data App (or +with different Data App/Updater App package names) would be considered a +misconfiguration.</p> + +<h3 id="xts-testing">xTS testing</h3> +<p>xTS refers to any OEM-specific test suite that is similar to standard Android +test suites using Tradefed (such as CTS and VTS). OEMs that have such test +suites can add the Android time zone update tests provided in the following +locations:</p> + +<ul> +<li><code>packages/apps/TimeZoneData/testing/xts</code>. Includes the code +needed for basic automated functional testing.</li> +<li><code>packages/apps/TimeZoneData/oem_template/xts</code>. Contains a sample +directory structure for including tests in a Tradefed-like xTS suite. As with +other template directories, OEMs are expected to copy and customize to their +needs.</li> +<li><code>packages/apps/TimeZoneData/oem_template/data_app_prebuilt</code>. +Contains build-time configuration for including the pre-built test .apk files +required by the test.</li> +</ul> + +<aside class="note"><strong>Note:</strong> Setting up an OEM-specific test suite +is outside of the scope of this article.</aside> + +<h2 id="creating-updates">Creating time zone updates</h2> +<p>When IANA releases a new set of time zone rules, the Android core libraries +team generates patches to update releases in AOSP. OEMs using the stock Android +system and distro files can pick up these commits, use them to create a new +version of their Data App, then release the new version to update their devices +in production.</p> + +<aside class="note"><strong>Note:</strong> The following steps do not describe +how to update the base data files in the <code>/system</code> image, which is +required when preparing the factory image or system updates. That process also +generates the distro file for inclusion in the Data app. For instructions on +updating the platform files, refer to +<code>/system/timezone/README.android</code>.</aside> + +<p>Because Data Apps contain distro files closely tied to Android versions, +OEMs must create a new version of the Data App for <em>every</em> supported +Android release an OEM wants to update. For example, if an OEM wants to provide +updates for O-MR1, P, and Q devices, they must complete the process three +times.</p> + +<h3 id="step1">Step 1: Updating system/timezone and external/icu data files</h3> +<p>In this step, OEMs take stock Android commits for +<code>system/timezone</code> and <code>external/icu</code> from the +<em>release</em>-dev branches in AOSP and apply those commits to their copy of +the Android source code.</p> +<p>The system/timezone AOSP patch contains updated files in +<code>system/timezone/input_data</code> and +<code>system/timezone/output_data</code>. OEMs who need to make additional local +fixes can modify the input files then use the files in +<code>system/timezone/input_data</code> and <code>external/icu</code> to +generate files in <code>output_data</code>.</p> +<p>The most important file is +<code>system/timezone/output_data/distro/distro.zip</code>, which is +automatically included when the Data App .apk is built.</p> + +<h3 id="step2">Step 2: Updating the version code of the Data App</h3> +<p>In this step, OEMs update the version code of the Data App. The build +automatically picks up the <code>distro.zip</code>, but the new version of the +Data App must have a new version code so it is recognized as new and is used to +replace a pre-loaded Data App or a Data App installed on a device by a previous +update.</p> +<p>When building the Data App using files copied from +<code>package/apps/TimeZoneData/oem_template/data_app</code>, you can find the +version code/version name applied to the .apk in the <code>Android.mk</code>: +</p> + +<pre class="prettyprint"> +TIME_ZONE_DATA_APP_VERSION_CODE := +TIME_ZONE_DATA_APP_VERSION_NAME := +</pre> + +<p>Similar entries can be found in <code>testing/Android.mk</code> (however, the +test version codes must be higher than the system image version). For details, +see the <a href="#example-version-code-strategy">example version code strategy +scheme</a>; if the example scheme or a similar scheme is used, the test +version codes do not need to be updated because they are guaranteed to be higher +than the real version codes.</p> + +<h3 id="step3">Step 3: Rebuild, sign, test, and release</h3> +<p>In this step, OEMs rebuild the .apk files using tapas, sign the generated +.apk files, then test and release the .apks:</p> +<ul> +<li>For unreleased devices (or when preparing a system update for a +released device), submit the new .apk files in the Data App prebuilt directory +to ensure the system image and xTS tests have the latest .apks. OEMs should test +the new file works correctly (i.e. it passes CTS and any OEM-specific automated +and manual tests).</li> +<li>For released devices that no longer receive system updates, the signed .apk +might only be released via an app store.</li> +</ul> +<p>OEMs are entirely responsible for quality assurance and testing the updated +Data App on their devices before release.</p> + +<h2 id="version-code-strategy">Data App version code strategy</h2> +<p>The Data App must have a +<a href="https://developer.android.com/google/play/publishing/multiple-apks.html#VersionCodes">suitable +versioning strategy</a> to ensure that devices receive the correct .apk +files. For example, if a system update is received that contains an older .apk +than one downloaded from the app store, the app store version should be +retained.</p> +<p>The .apk version code should include the following information:</p> +<ul> +<li>Distro format version (major + minor)</li> +<li>An incrementing (opaque) version number</li> +</ul> +<p>Currently, platform API level is strongly correlated to distro format version +because each API level is usually associated with a new version of ICU (which +makes the distro files incompatible). In the future, Android may change this so +that a distro file can work across multiple Android platform releases (and API +level is not used in the Data App version code scheme).</p> + +<h3 id="example-version-code-strategy">Example version code strategy</h3> +<p>This example versioning number scheme ensures that higher distro format +versions beat lower distro format versions. The <code>AndroidManifest.xml</code> +uses <code>android:minSdkVersion</code> to ensure old devices don't receive +versions with a higher distro format version than they can handle.</p> + +<figure> +<img src="images/tz_version_check.png" alt="Version check" +id="version-check" /> +<figcaption><strong>Figure 6.</strong> Example version code strategy. +</figcaption></figure> + +<table> +<thead> +<tr> +<th>Example</th> +<th width="20%">Value</th> +<th>Purpose</th> +</tr> +</thead> +<tbody> +<tr> +<td><strong>Y</strong></td> +<td>Reserved</td> +<td>Allows for future alternative schemes and/or test APKs. It will initially +be (implicitly) 0. Because the underlying type is a signed 32-bit int type, +this scheme supports up to two future numbering scheme revisions.</td> +</tr> +<tr> +<td><strong>01</strong></td> +<td>Major format version</td> +<td>Tracks the 3 decimal digit major format version. The distro format supports +3 decimal digits but only 2 digits are used here. It is unlikely 100 will +be reached given the expected major increment per API level. Major version +1 == API level 27.</td> +</tr> +<tr> +<td><strong>1</strong></td> +<td>Minor format version</td> +<td>Tracks the 3 decimal digit minor format version. The distro format supports +3 decimal digits but only 1 digit is used here. It is unlikely 10 will be +reached.</td> +</tr> +<tr> +<td><strong>X</strong></td> +<td>Reserved</td> +<td>Is 0 for production releases (and may be different for test APKs).</td> +</tr> +<tr> +<td><strong>ZZZZZ</strong></td> +<td>Opaque version number</td> +<td>Decimal number allocated on demand. Includes gaps to allow interstitial +updates to be made if required.</td> +</tr> +</tbody> +</table> + +<p>The scheme could be packed better if binary were used instead of decimal, but +this scheme has the advantage of being human-readable. If the full number range +is exhausted, future releases could change the Data App package name and start +again.</p> + +<p>Version name will be a human-readable representation of the details, e.g.: +<code>major=001,minor=001,iana=2017a, revision=1,respin=2</code>. Examples:</p> + +<table> +<thead> +<tr> +<th>#</th> +<th>Version code</th> +<th>minSdkVersion</th> +<th>{Major format version}.{Minor format version}.{IANA rules +version}.{Revision}</th> +</tr> +</thead> +<tbody> +<tr> +<td>1</td> +<td>11000010</td> +<td>O-MR1</td> +<td>major=001,minor=001,iana=2017a,revision=1</td> +</tr> +<tr> +<td>2</td> +<td>21000010</td> +<td>P</td> +<td>major=002,minor=001,iana=2017a,revision=1</td> +</tr> +<tr> +<td>3</td> +<td>11000020</td> +<td>O-MR1</td> +<td>major=001,minor=001,iana=2017a,revision=2</td> +</tr> +<tr> +<td>4</td> +<td>11000030</td> +<td>O-MR1</td> +<td>major=001,minor=001,iana=2017b,revision=1</td> +</tr> +<tr> +<td>5</td> +<td>21000020</td> +<td>P</td> +<td>major=002,minor=001,iana=2017b,revision=1</td> +</tr> +<tr> +<td>6</td> +<td>11000040</td> +<td>O-MR1</td> +<td>major=001,minor=001,iana=2018a,revision=1</td> +</tr> +<tr> +<td>7</td> +<td>21000030</td> +<td>P</td> +<td>major=002,minor=001,iana=2018a,revision=1</td> +</tr> +<tr> +<td>8</td> +<td>1123456789</td> +<td>-</td> +<td>-</td> +</tr> +<tr> +<td>9</td> +<td>11000021</td> +<td>O-MR1</td> +<td>major=001,minor=001,iana=2017a,revision=2,respin=2</td> +</tr> +</tbody> +</table> + +<ul> +<li>Examples 1 and 2 show two .apk versions for the same 2017a IANA release +with different major format versions. 2 is numerically higher than 1, which is +needed to ensure that newer devices receive the higher format versions. The +minSdkVersion ensures the P version will not be supplied to O devices.</li> +<li>Example 3 is an example revision/fix for 1 and is numerically higher than 1. +</li> +<li>Examples 4 and 5 show the 2017b releases for O-MR1 and P. Being numerically +higher, they replace prior IANA releases/Android revisions of their respective +predecessors.</li> +<li>Examples 6 and 7 show the 2018a releases for O-MR1 and P.</li> +<li>Example 8 demonstrates the use of Y to completely replace the Y=0 scheme. +</li> +<li>Example 9 demonstrates the use of the gap left between 3 and 4 to re-spin +the apk.</li> +</ul> + +<p>As each device will ship with a default, appropriately versioned .apk in the +system image, there is no risk of an O-MR1 version being installed on a P device +because it will have a lower version number than a P system image version. A +device with an O-MR1 version installed in <code>/data</code> that then receives +a system update to P will use the <code>/system</code> version in preference to +the O-MR1 version in<code> /data</code> because the P version will always be +higher than any app intended for O-MR1.</p> + +<h2 id="building-tapas">Building the Data App using tapas</h2> +<p>OEMs are responsible for managing most aspects of the time zone Data App and +configuring the system image correctly. The Data App is intended to be built +with a <strong>tapas</strong> build that produces .apks suitable to be added to +the system image (for the initial release) and signed and distributed via an app +store (for subsequent updates).<p> +<p><strong>Tapas</strong> is a slimmed-down version of the Android build +system that uses a reduced source tree to produce distributable versions of +apps. OEMs familiar with the normal Android build system will recognize the +build files from the normal Android platform build.</p> + +<h3 id="creating-manifest">Creating the manifest</h3> +<p>A reduced source tree is usually achieved with a custom manifest file that +refers only to the Git projects needed by the build system and for building the +app. After following the instructions in +<a href="#creating-data-app">Creating a Data App</a>, OEMs should have at +least two OEM-specific git projects created by using the template files under +<code>packages/apps/TimeZoneData/oem_template</code>:</p> + +<ul> +<li>One git project contains application files such as the manifest and the +build files required to create the application .apk file (e.g. +<code>vendor/<em>oem</em>/apps/TimeZoneData</code>). This project also contains +build rules for test APKs that can be used by xTS tests.</li> +<li>One git project contains the signed .apk files produced by the app build for +inclusion in the system image build and xTS tests.</li> +</ul> + +<p>The app build leverages several other git projects that are shared with the +platform build or contain OEM-independent code libraries.</p> +<p>The following manifest snippet contains the minimal set of git projects +needed to support an O-MR1 build of the time zone Data App (future versions of +Android will have different lists or may even change the build system). OEMs +must add their OEM-specific git projects (which typically include a project that +contains the signing certificate) to this manifest, and may configure different +branches accordingly.</p> + +<pre class="prettyprint"> + <!-- Tapas Build --> + <project + path="build" + name="platform/build"> + <copyfile src="core/root.mk" dest="Makefile" /> + </project> + <project + path="prebuilts/build-tools" + name="platform/prebuilts/build-tools" + clone-depth="1" /> + <project + path="prebuilts/go/linux-x86" + name="platform/prebuilts/go/linux-x86" + clone-depth="1" /> + <project + path="build/blueprint" + name="platform/build/blueprint" /> + <project + path="build/kati" + name="platform/build/kati" /> + <project + path="build/soong" + name="platform/build/soong"> + <linkfile src="root.bp" dest="Android.bp" /> + <linkfile src="bootstrap.bash" dest="bootstrap.bash" /> + </project> + + <!-- SDK for system / public API stubs --> + <project + path="prebuilts/sdk" + name="platform/prebuilts/sdk" + clone-depth="1" /> + <!-- App source --> + <project + path="system/timezone" + name="platform/system/timezone" /> + <project + path="packages/apps/TimeZoneData" + name="platform/packages/apps/TimeZoneData" /> + <!-- Enable repohooks --> + <project + path="tools/repohooks" + name="platform/tools/repohooks" + revision="master" + clone_depth="1" /> + <repo-hooks + in-project="platform/tools/repohooks" + enabled-list="pre-upload" /> +</pre> + +<h3 id="running-tapas">Running the tapas build</h3> +<p>After the source tree is established, invoke the <strong>tapas</strong> build +using the following commands:</p> + +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">source build/envsetup.sh</code> +<code class="devsite-terminal">tapas</code> +<code class="devsite-terminal">make -j30 showcommands dist TARGET_BUILD_APPS='TimeZoneData TimeZoneData_test1 TimeZoneData_test2' TARGET_BUILD_VARIANT=userdebug</code> +</pre> + +<p>A successful build generates files in the <code>out/dist</code> directory for +testing. These files can be placed into the prebuilts directory for inclusion in +the system image and/or distributed via an app store for compatible +devices.</p> + +</body> +</html> diff --git a/en/devices/tech/connect/wifi-aware.html b/en/devices/tech/connect/wifi-aware.html new file mode 100644 index 00000000..7244abb2 --- /dev/null +++ b/en/devices/tech/connect/wifi-aware.html @@ -0,0 +1,122 @@ +<html devsite> + <head> + <title>Wi-Fi Aware</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + + + +<p> +The <a +href="https://developer.android.com/guide/topics/connectivity/wifi-aware.html">Wi-Fi +Aware</a> feature in the Android 8.1 (O MR1) release enables supporting devices to +connect to one another directly over Wi-Fi without internet or cellular network +access. This feature, built upon the <a href="https://www.wi-fi.org/">Wi-Fi +Alliance</a> <a href="https://www.wi-fi.org/discover-wi-fi/wi-fi-aware">Wi-Fi +Aware specification</a> (version 2.0), allows easy sharing of high-throughput +data among trusted devices and apps that are otherwise off network. +</p> + +<h2 id="examples-and-source">Examples and source</h2> + +<p> +To use this feature, device manufacturers should implement the Wi-Fi Hardware +Interface Design Language (HIDL) provided in the Android Open Source Project +(AOSP). In the Android 8.0 (O) release, HIDL replaces the previous Hardware +Abstraction Layer (HAL) structure used in order to streamline implementations by +specifying types and method calls collected into interfaces and packages. +</p> + +<p> +Follow the Wi-Fi HIDL to employ the Wi-Fi aware feature: +hardware/interfaces/wifi/1.0. The Wi-Fi Aware HAL surface is very large; the +<a href + ="https://android.googlesource.com/platform/hardware/interfaces/+/master/wifi/1.0/README-NAN.md">hardware/interfaces/wifi/1.0/README-NAN.md</a> +file describes the subset which is currently in use. +</p> + +<p> +You may reference the legacy Wi-Fi HAL to see how it correlates with the new +HIDL interface: +<a +href="https://android.googlesource.com/platform/hardware/libhardware_legacy/+/master/include/hardware_legacy/wifi_nan.h">hardware/libhardware_legacy/+/master/include/hardware_legacy/wifi_nan.h</a>. +</p> + +<h2 id="implementation">Implementation</h2> + +<p> +Device manufacturers need to provide both framework and HAL/firmware support: +</p> +<ul> + <li>Framework: + <ul> + <li>AOSP code</li> + <li>Enable Aware: requires both a feature flag and an HIDL build flag</li> + </ul> + <li>Wi-Fi Aware (NAN) HAL support (which implies firmware support)</li> + </li> +</ul> + +<p> +To implement this feature, device manufacturers implement the Wi-Fi HIDL and +also enable two feature flags: +</p> + +<p> +In <code>BoardConfig.mk</code>, add this flag to tell the Wi-Fi HIDL to include +the Wi-Fi Aware feature: +<code>WIFI_HIDL_FEATURE_AWARE := true</code> +</p> + +<p> +And in <code>device.mk</code>, modify the <code>PRODUCT_COPY_FILES</code> +environment variable to include support for the Wi-Fi Aware feature: +<code>PRODUCT_COPY_FILES += +frameworks/native/data/etc/android.hardware.wifi.aware.xml:system/etc/permissions/android.hardware.wifi.aware.xml</code> +</p> + +<p> +Otherwise, everything required for this feature is included in AOSP. +</p> + +<h2 id="validation">Validation</h2> + +<p> +Android Compatibility Test Suite (CTS) tests exist for this feature. CTS detects +when the feature is enabled and automatically includes the associated tests. +</p> + +<p> +This feature can also be tested using the <a +href="/devices/tech/test_infra/tradefed/fundamentals/vts">Vendor +Test Suite (VTS)</a> and <a +href="https://android.googlesource.com/platform/tools/test/connectivity/+/master/acts/tests/google/wifi/">acts/sl4a</a>, +a test suite that conducts extensive integration testing. +</p> + +<p> +The acts/sl4a test suite, described in +<a +href="https://android.googlesource.com/platform/tools/test/connectivity/+/master/acts/tests/google/wifi/aware/README.md">tools/test/connectivity/acts/tests/google/wifi/aware/README.md</a>, +provides functional, performance, and stress tests. +</p> + +</body> +</html> diff --git a/en/devices/tech/dalvik/configure.html b/en/devices/tech/dalvik/configure.html index 6a5fa86e..4809c2fe 100644 --- a/en/devices/tech/dalvik/configure.html +++ b/en/devices/tech/dalvik/configure.html @@ -129,10 +129,10 @@ pre-optimization of prebuilt apps that are likely to be updated via Google Play saves <code>/system</code> space but does add to first boot time. </p> -<li><code>WITH_DEXPREOPT_BOOT_IMG_ONLY</code></li> +<li><code>WITH_DEXPREOPT_BOOT_IMG_AND_SYSTEM_SERVER_ONLY</code> (new in Android O MR1)</li> -<p>Enabling <code>WITH_DEXPREOPT_BOOT_IMG_ONLY</code> pre-optimizes only the -boot classpath. +<p>Enabling <code>WITH_DEXPREOPT_BOOT_IMG_AND_SYSTEM_SERVER_ONLY</code> pre-optimizes only the +boot classpath and system server jars.</p> <li><code>LOCAL_DEX_PREOPT</code></li> @@ -212,6 +212,12 @@ should enable PIC compilation.</p> <p>In Android 7.0, PIC compilation was enabled by default.</p> +<li><code>WITH_DEXPREOPT_BOOT_IMG_ONLY</code> (removed in Android O MR1)</li> +<p> +This option was replaced with WITH_DEXPREOPT_BOOT_IMG_AND_SYSTEM_SERVER_ONLY +that also preopts the system server jars. +</p> + </ul> diff --git a/en/devices/tech/display/color-mgmt.html b/en/devices/tech/display/color-mgmt.html new file mode 100644 index 00000000..d73f091d --- /dev/null +++ b/en/devices/tech/display/color-mgmt.html @@ -0,0 +1,149 @@ +<html devsite> + <head> + <title>Color Management</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> +<p>Android 8.1 adds support for color management that can be used to provide a +consistent experience across display technologies. Applications running on +Android 8.1 can access the full capabilities of a wide gamut display to get the +most out of a display device.</p> + +<p>Previous Android releases did not include color management support and +instead relied on content and displays being compatible (a goal often aided by +the TV industry). However, recent display technologies allow for much larger +gamut displays that do not display existing content as expected. With Android +8.1, devices that use a wide-gamut display (e.g. active-matrix organic +light-emitting diode or AMOLED, some LCDs) will be able to see wide-gamut +content from applications.</p> + +<h2>Determining device support</h2> +<p>Devices with wide-color displays running Android 8.1 should support color +management (wide-color). Before enabling this feature, ensure the device meets +the following requirements:</p> +<ul> +<li>Device display meets the hardware requirements, which include a +well-characterized display that supports the Display-P3 colorspace. If the +display does not meet this requirement, do not enable color management. To +reduce CPU and GPU impact, support for extended sRGB and HDR10 in the display +pipeline is desirable.</li> +<li>Device supports a factory calibration process that generates calibration +data (stored on the device) to adjust for manufacturing variance in display +behavior. At a minimum, calibration data should allow the display to accurately +display sRGB content and D65 and D73 white points (future versions of Android +may support full ICC profiles for each device).</li> +</ul> +<p>If the above requirements are met, you can enable the color management +feature for the device.</p> + +<h2>Implementing color management</h2> +<p>To implement color management, you must first update the +<a href="/devices/graphics/implement-hwc">Hardware Composer 2 (HWC2)</a> driver +to understand color modes and to apply those modes to the hardware. +Specifically, the HWC2 composer must report the Display-P3 and sRGB +color modes using <code>HWCDisplay::GetColorModes</code>.</p> + +<aside class="key-term"><strong>Key Term:</strong> Display-P3 uses Digital +Cinema Initiatives primaries and sRGB transfer function.</aside> + +<p>Next, enable the necessary OpenGL extensions and library support to +translate OpenGL color spaces to HAL data spaces. Required OpenGL extensions +include:</p> +<ul> +<li> +<a href="https://www.khronos.org/registry/egl/extensions/EXT/EGL_EXT_pixel_format_float.txt" class="external">EGL_EXT_pixel_format_float</a>. +Allows applications to create presentable EGLSurface(s) with 16-bit float color +components. Priority: high (expect this is the default pixel format for +wide-color aware applications). Requires driver support.</li> +<li> +<a href="https://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_gl_colorspace.txt" class="external">EGL_KHR_gl_colorspace</a>. +For applications that want to use sRGB format default framebuffers to more +easily achieve sRGB rendering to display devices, this extension allows creating +EGLSurfaces that will be rendered to in sRGB by OpenGL contexts supporting that +capability. Requires driver support for sRGB behavior.</li> +</ul> +<p>Android also provides the following optional extensions:</p> +<ul> +<li> +<a href="https://www.khronos.org/registry/egl/extensions/EXT/EGL_EXT_gl_colorspace_scrgb_linear.txt" class="external">EGL_EXT_colorspace_scrgb_linear</a>. +This extension provides a new color space option, scRGB, for applications to +choose when creating an EGLSurface. The scRGB color space defines a linear +display referred space with the same white point and color primaries as sRGB +(and thus is backward-compatible with sRGB). This should not require driver +support and can be implemented in the Android EGL wrapper. To be useful, this +extension requires support for 16-bit floating point (FP16).</li> +<li> +<a href="https://github.com/KhronosGroup/EGL-Registry/pull/10/files" class="external">EGL_KHR_gl_colorspace_display_p3 +and EGL_EXT_gl_colorspace_display_p3_linear</a>. For applications that want +to use Display-P3 format default framebuffers to more easily achieve sRGB +rendering to display devices, this extension allows creating EGLSurfaces that +will be rendered to in Display-P3 by OpenGL contexts supporting that capability. +This can be implemented in EGL driver wrapper.</li> +<li> +<a href="https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#VK_EXT_swapchain_colorspace" class="external">VK_EXT_swapchain_colorspace</a> +(Vulkan). Enables applications to tag swap chains with the color space they are +using. Includes a number of common color spaces such as DCI-P3, Display-P3, +AdobeRGB, BT2020, etc.</li> +</ul> + +<h2>Customizing</h2> +<p>You can customize the color management feature by including support for a +variety of color standards such as DCI-P3, AdobeRGB, Rec709, Rec2020. Other +customizations include:</p> +<ul> +<li><strong>Hardware support for color conversion in the display +pipeline</strong>. Enables support for multiple color transforms in hardware. +</li> +<li><strong>Support for independent color transform on multiple layers</strong> +(e.g. some layers could be sRGB and others extended-sRGB, each with their own +color pipeline). When there is more than one color space visible, some color +spaces will need to be converted to the color space of the display. Ideally, +this transform is best provided by the display engine (otherwise Android must +perform GPU composition).</li> +</ul> + +<h2>Testing</h2> +<p>To test color management, use the following resources in +<code>opengl/tests</code>:</p> +<ul> +<li><code>gl2_basic</code>. Simple OpenGL demo that requests a Display-P3 +colorspace.</li> +<li><code> +<a href="https://android.googlesource.com/platform/frameworks/native/+/master/opengl/tests/EGLTest/EGL_test.cpp">EGL_test</code></a>. +Tests for necessary extension and config support (10:10:10:2 and FP16).</li> +<li><code>test_wide_color</code>. Creates surface in same manner as +SurfaceFlinger (e.g. config, color space, pixel format).</li> +</ul> + +<h2>Reference implementation</h2> +<p>For a reference implementation, refer to <code>frameworks/native</code>. For +headers, refer to:</p> +<ul> +<li> +<code><a href="https://android.googlesource.com/platform/system/core/+/master/libsystem/include/system/graphics.h">system/core/include/system/graphics.h</code></a></li> +<li> +<code><a href="https://android.googlesource.com/platform/system/core/+/master/libsystem/include/system/graphics-base.h">system/core/include/system/graphics-base.h</code></a><ul> +<li><code>HAL_DATASPACE_*</code></li> +<li><code>HAL_COLOR_MODE_*</code></li> +</ul> +</li> +</ul> + +</body> +</html> diff --git a/en/devices/tech/display/images/textclassifier.png b/en/devices/tech/display/images/textclassifier.png Binary files differnew file mode 100644 index 00000000..adbeb0b8 --- /dev/null +++ b/en/devices/tech/display/images/textclassifier.png diff --git a/en/devices/tech/display/retail-mode.html b/en/devices/tech/display/retail-mode.html index b694e616..2928b88a 100644 --- a/en/devices/tech/display/retail-mode.html +++ b/en/devices/tech/display/retail-mode.html @@ -21,34 +21,131 @@ limitations under the License. --> +<p> +Android 7.1.1 and later offer system-level support for retail mode so +users may readily examine the devices in action. Android 8.1 revises +this support to create demo users via Device Policy Manager. This +allows much greater OEM customization to the standard retail mode. +</p> +<h2 id=android-8-1-and-later>Android 8.1 and later</h2> <p> -Android 7.1.1 and later offer system-level support for retail mode so -users may readily examine the devices in action. This feature enables anyone in -a retail environment to get a quick, safe, and consistent demonstration of an -Android device and significantly reduce the cost and complexity of a retail mode -for OEMs so that demonstration units are commonplace. +Through Device Policy Manager, Android 8.1 supports demonstrating +device functionality to users in retail stores. While Device Policy Manager's +APIs can be used on versions prior to 8.1, demo-type users cannot be created +with <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#createAndManageUser(android.content.ComponentName, java.lang.String, android.content.ComponentName, android.os.PersistableBundle, int)"> +createAndManageUser</a> prior to 8.1. </p> -<h2 id="key-use-cases">Key use cases</h2> +<h3 id="implementation">Implementation</h3> + +<h4 id="provisioning">Provisioning</h4> +<p> +Set <code>Settings.Global.DEVICE_DEMO_MODE</code> to 1 prior to +provisioning to indicate that the device should enter retail mode. System +Server will use this flag to manage aspects of retail mode, such as power +profile. In addition, retail employees must grant device ownership to the +demo application. Once a consumer setup is complete, device owners cannot +be set. +</p> +<h4 id="create-demo-app">Creating the demo application</h4> +<p> +Device owner apps do not need elevated privileges or pre-installation on the +system image. They are mostly implmented like traditional apps, with the +following differences: +</p> <ul> -<li>Any off-the-shelf Android device can be set to retail mode by adding a -single demo video to the build. -<li>All devices have a video highlighting the unique features of the device. -<li>Devices work in both online and offline environments. -<li>Device are self maintaining, requiring minimal interaction by -employees.</li></ul> + <li>All device owner apps must extend the <code>DeviceAdminReceiver</code> +component, which serves as the authorization token for all Device Policy +Manager APIs. The component must hold the <code>android.permission.BIND_DEVICE_ADMIN</code> +permission, include the requested special policies as metadata, and filter the +<code>android.app.action.PROFILE_PROVISIONING_COMPLETE</code> and + <code>android.app.action.DEVICE_ADMIN_ENABLED</code> intents.</li> + <li>The <code>DevicePolicyManager#MAKE_USER_DEMO</code> flag, which is set +to create special demo-type users, is a hidden API. This flag is a constant 0x4.</li> + <li>Device ownership can be assigned only via Managed Provisioning.</li> +</ul> + +<h4 id="device-policy-manager">Device Policy Manager</h4> +<p> +Device Policy Manager APIs grant all Device Owner (DO) and Profile Owner (PO) +rights, except for installing packages, which is automatically allowed. A PO +affiliated with a DO can use an AIDL interface to access rights that are only +granted to the DO. Functionality available includes: +</p> +<ul> + <li>Create users. Users created through the DevicePolicyManager are +automatically set as PO.</li> + <li>Switch users.</li> + <li>Set the permission policy to <code>PERMISSION_POLICY_AUTO_GRANT</code> +which will automatically grant all runtime permissions. Permissions can also be +granted more narrowly: a single permission to a single app. This does not +apply to Appops permissions, which users must still grant on a per-user, +per-app basis.</li> + <li>Add user restrictions. Restrictions relevant to retail mode may include, +but are not limited to: + <ul> + <li><code>DISALLOW_MODIFY_ACCOUNTS</code></li> + <li><code>DISALLOW_USB_FILE_TRANSFER</code></li> + <li><code>DISALLOW_DEBUGGING_FEATURES</code></li> + <li><code>DISALLOW_CONFIG_WIFI</code></li> + <li><code>DISALLOW_CONFIG_BLUETOOTH</code></li> + <li><code>DISALLOW_INSTALL_UNKNOWN_SOURCES</code></li> + <li><code>DISALLOW_CONFIG_MOBILE_NETWORKS</code></li> + </ul> + </li> + <li>Enable automatic system updates. Devices will automatically download and apply +OTA updates.</li> + <li>Set LockTask allowed packages.</li> + <li>Factory reset the device.</li> + <li>Disable the keyguard.</li> + <li>Prevent setting passwords / fingerprints.</li> + <li>Control Wi-fi network changes. When used with the <code>DISALLOW_CONFIG_WIFI</code> +user restriction, device owner apps can control access to the wifi network selection +setting.</li> + <li>Reboot the device.</li> + <li>Install packages through <a href="https://developer.android.com/reference/android/content/pm/PackageInstaller.html"> +PackageInstaller</a>.</li> + <li>Set a whitelisted set of <a href="https://developer.android.com/reference/android/provider/Settings.Global.html"> +Settings.Global</a>, <a href="https://developer.android.com/reference/android/provider/Settings.Secure.html"> +Settings.Secure</a>, and <a href="https://developer.android.com/reference/android/provider/Settings.System.html"> +Settings.System</a> settings.</li> + <li>Block packages from being uninstalled.</li> +</ul> + +<h3 id="examples-additional-resources">Examples and additional resources</h3> +<ul> + <li><a href="/devices/tech/admin/multi-user"> +Android Developer definitions</a> of users, profiles, and accounts</li> + <li><a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html"> +Device Policy Manager API documentation</a></li> + <li><a href="https://developer.android.com/samples/DeviceOwner/index.html"> +Sample Device Owner app</a></li> +</ul> + +<h3 id="validation">Validation</h3> +<p> +CTS does not cover Retail Demo Mode because it is an optional feature. Testing +should be conducted manually or with unit tests for the demo application. +</p> + +<h2 id="retail-demo-mode-8-and-earlier">Android 8.0 and earlier</h2> + +<p> +Android 7.1.1 introduced retail demo mode and provided a simple API to play a +demonstration video. This implementation was removed in Android 8.1. +</p> -<h2 id="lifecycle">Lifecycle</h2> +<h3 id="lifecycle">Lifecycle</h3> <img src="/devices/tech/display/images/retail-demo-flow.png" alt="retail demo mode flow" width="XXX" id="retail-demo-flow" /> <p class="img-caption"> <strong>Figure 1.</strong> Retail demonstration mode option in Language selection </p> -<h3 id="setup-wizard-suw">Setup Wizard (SUW)</h3> +<h4 id="setup-wizard-suw">Setup Wizard (SUW)</h4> <p> Retail employees can enable retail mode directly from the first screen of any setup @@ -64,7 +161,7 @@ available. Once selected, the device finishes SUW with an abbreviated flow. selection </p> -<h3 id="guest-session">Guest session</h3> +<h4 id="guest-session">Guest session</h4> <p> When the device enters retail mode, it switches to a new demo user and @@ -125,14 +222,14 @@ settings, including: <li>Language <li>Accessibility</li></ul> -<h3 id="exiting-retail-mode">Exiting retail mode</h3> +<h4 id="exiting-retail-mode">Exiting retail mode</h4> <p> In order to exit retail mode, retail employees must factory reset the device from the boot loader. </p> -<h2 id="examples-and-source">Examples and source</h2> +<h3 id="examples-and-source">Examples and source</h3> <p> Find the custom launcher that plays a video in a loop within:</p> @@ -140,9 +237,9 @@ Find the custom launcher that plays a video in a loop within:</p> /packages/apps/RetailDemo </pre> -<h2 id="implementation">Implementation</h2> +<h3 id="implementation">Implementation</h3> -<h3 id="enabling-retaildemomodeservice">Enabling RetailDemoModeService</h3> +<h4 id="enabling-retaildemomodeservice">Enabling RetailDemoModeService</h4> <p> Setup wizard sets a Global setting <code>Global.DEVICE_DEMO_MODE=true</code> to @@ -153,8 +250,8 @@ disables SUW. System Server and SystemUI also use this flag to manage aspects of retail mode. </p> -<h3 id="setting-custom-launcher-or-video-player">Setting custom launcher or -video player</h3> +<h4 id="setting-custom-launcher-or-video-player">Setting custom launcher or +video player</h4> <p> An OEM specifies a custom launcher by overriding the framework resource @@ -207,7 +304,7 @@ To set retail mode-specific settings, use: timeout default but is configurable. </p> -<h3 id="finding-sample-images">Finding sample images</h3> +<h4 id="finding-sample-images">Finding sample images</h4> <p> This feature places sample photos in a special folder that is visible to any @@ -215,7 +312,7 @@ gallery app. The photos are available only in demo mode and cannot be modified by the demo user as they are in a protected directory. </p> -<h3 id="preventing-google-accounts">Preventing Google accounts</h3> +<h4 id="preventing-google-accounts">Preventing Google accounts</h4> <p> Certain restrictions are set in the guest user, similar to managed @@ -232,14 +329,14 @@ general problem not unique to retail mode. It is likely already solved for enterprise use cases. </p> -<h3 id="customizing-the-system-launcher">Customizing the system launcher</h3> +<h4 id="customizing-the-system-launcher">Customizing the system launcher</h4> <p> OEMs are free to choose their layout but should include apps that function well on the home screen and hotseat. </p> -<h3 id="Customizing-built-in-apps">Customizing built-in apps for retail demo mode</h3> +<h4 id="Customizing-built-in-apps">Customizing built-in apps for retail demo mode</h4> <p> Built-in apps may have their experience for retail demo mode customized by @@ -247,7 +344,7 @@ calling the API <code>UserManager.isDemoUser()</code> to see if the app is launched in a demo environment. </p> -<h3 id="following-demo-video-guidelines">Following demo video guidelines</h3> +<h4 id="following-demo-video-guidelines">Following demo video guidelines</h4> <p> Demonstration videos should be in portrait layout (or natural orientation of the @@ -255,16 +352,16 @@ device, if tablet) and can be any length greater than five seconds. Content should not result in burn-in, since it will be played 24/7 when on display. </p> -<h2 id="maintenance">Maintenance</h2> +<h3 id="maintenance">Maintenance</h3> -<h3 id="bringing-the-device-out-of-retail-mode">Bringing the device out of -retail mode</h3> +<h4 id="bringing-the-device-out-of-retail-mode">Bringing the device out of +retail mode</h4> <p> This can be done only by factory resetting from the boot loader. </p> -<h3 id="auto-ota-of-system-software">Auto-OTA of system software</h3> +<h4 id="auto-ota-of-system-software">Auto-OTA of system software</h4> <p> By default, when retail mode is enabled, device policy is set to over-the-air @@ -280,7 +377,7 @@ subsequent factory reset will result in an inability to go back into retail mode. </p> -<h3 id="updating-demo-video-via-the-web">Updating demo video via the web</h3> +<h4 id="updating-demo-video-via-the-web">Updating demo video via the web</h4> <p> The RetailDemo app in <code>/packages/apps/RetailDemo</code> has the ability to diff --git a/en/devices/tech/display/textclassifier.html b/en/devices/tech/display/textclassifier.html new file mode 100644 index 00000000..81ed87f3 --- /dev/null +++ b/en/devices/tech/display/textclassifier.html @@ -0,0 +1,153 @@ +<html devsite> + <head> + <title>Implementing TEXTCLASSIFIER</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + +<h2 id="overview">Overview</h2> + +<p> +Android 8.1 introduces the TextClassfier API that uses machine learning +techniques to help developers classify text: +</p> + + +<pre +class="prettyprint">TextClassificationManager tcm = + context.getSystemService(TextClassificationManager.class); +TextClassifier classifier = tcm.getTextClassifier(); +TextSelection selection = classifier.suggestSelection(...); +TextClassification classification = classifier.classifyText(...); +</pre> +<p> +Developers may choose to set a custom text classifier: +</p> +<p> + <code>tcm.setTextClassifier(customTextClassifier);</code> +</p> +<p> +But if an app developer sets the text classifier to null, a system default text +classifier is returned for <code>getTextClassifier()</code>. +</p> +<p> +See: <code>android.view.textclassifier.TextClassifierImpl</code> +</p> +<p> +TextView and WebView use the TextClassifier for smart selection and smart text +share features: +</p> + +<img src="/devices/tech/display/images/textclassifier.png"> +<p class="img-caption"> + <b>Figure 1.</b> TEXTCLASSIFIER usage. +</p> + +<h2 id="textclassifier-neural-net-models">TextClassifier neural-net models</h2> +<p> +The Android Open Source Project (AOSP) features a number of neural network +models for classifying text. Each model file is trained for a single language. +You may choose to install any combination of models. The models are defined in: +</p> +<p> +<code>external/libtextclassifier/Android.mk</code> +</p> + +<h2 id="pre-installing-language-models-on-devices">Pre-installing language +models on devices</h2> +<p> +You may specify a bundle of language models and install them on a device: +</p> + + +<pre +class="prettyprint"># ----------------------- +# Smart Selection bundles +# ----------------------- + +include $(CLEAR_VARS) +LOCAL_MODULE := textclassifier.smartselection.bundle1 +LOCAL_REQUIRED_MODULES := textclassifier.smartselection.en.model +LOCAL_REQUIRED_MODULES += textclassifier.smartselection.es.model +LOCAL_REQUIRED_MODULES += textclassifier.smartselection.de.model +LOCAL_REQUIRED_MODULES += textclassifier.smartselection.fr.model +include $(BUILD_STATIC_LIBRARY) +</pre> + +<p> +For example, in <code>device/google/marlin/device-common.mk</code> +</p> + + +<pre +class="prettyprint"># TextClassifier smart selection model files +PRODUCT_PACKAGES += \ + textclassifier.smartselection.bundle1 +</pre> + +<h2 id="inspecting-installed-language-modules">Inspecting installed language +modules</h2> +<p> +Use ADB to list the files in the directory: +</p> + + +<pre +class="prettyprint">$ adb shell ls -l /etc/textclassifier +-rw-r--r-- 1 root root ... textclassifier.smartselection.de.model +-rw-r--r-- 1 root root ... textclassifier.smartselection.en.model +-rw-r--r-- 1 root root ... textclassifier.smartselection.es.model +-rw-r--r-- 1 root root ... textclassifier.smartselection.fr.model +</pre> + +<h2 id="gservices-model-updates">Model updates</h2> + +<p> +Models can be updated either by having a new model included as part of a system image update, +or dynamically via having a system component that would trigger an update through the +System <code>API ACTION_UPDATE_SMART_SELECTION</code> intent. By broadcasting this System API +intent, the framework is able to update the language model of the currently set language. +The models themselves contain the supported +language and a version number so the latest appropriate model is used. +</p> + +<p> +So you don't need to preload models for all languages because they can be added later. +If no model file is found for the specified language, text classification will return no-op values. +</p> + +<h2 id="compatibility-test-suite-tests">Compatibility Test Suite tests</h2> +<p> +The associated Android Compatibility Test Suite (CTS) tests can be found in: +</p> +<p> +<code>cts/tests/tests/view/src/android/view/textclassifier/cts/TextClassificationManagerTest.java</code> +</p> +<p> +<code>cts/tests/tests/widget/src/android/widget/cts/TextViewTest.java</code> +</p> + +<ul> +<li><code>testSmartSelection</code></li> +<li><code>testSmartSelection_dragSelection</code></li> +<li><code>testSmartSelection_resetSelection</code></li> +</ul> + +</body> +</html> diff --git a/en/devices/tech/perf/boot-times.html b/en/devices/tech/perf/boot-times.html index 4712cce0..e74ef1fc 100644 --- a/en/devices/tech/perf/boot-times.html +++ b/en/devices/tech/perf/boot-times.html @@ -254,9 +254,10 @@ us uncover many meaningful bugs in some Android device drivers). <p> Many processes launch during boot, but only components in critical path (bootloader > kernel > init > file system mount > zygote > system server) -directly affect boot time. Use the early kernel log to identify -peripheral/components that are not critical to the start init process, then -delay those peripherals/components until later in the boot process. +directly affect boot time. Profile <strong>initcall</strong> during kernel +booting to identify peripheral/components that are not critical to the +start init process, then delay those peripherals/components until later +in the boot process. </p> <h2 id="optimizing-i-o-efficiency">Optimizing I/O efficiency</h2> @@ -456,6 +457,49 @@ zygote-start). When doing this, make sure to allow zygote to run in all CPUs (as the wrong cpuset setting may force zygote to run in specific CPUs). </p> +<h3 id="disable-power-saving">Disable power saving</h3> + +<p> +During device booting, power saving setting for components like UFS and/or CPU +governor can be disabled. +</p> +<p class="aside"><strong>Caution:</strong> Power saving should be enabled in +charger mode for efficiency.</p> + +<pre +class="prettyprint"> +on init + # Disable UFS powersaving + write /sys/devices/soc/${ro.boot.bootdevice}/clkscale_enable 0 + write /sys/devices/soc/${ro.boot.bootdevice}/clkgate_enable 0 + write /sys/devices/soc/${ro.boot.bootdevice}/hibern8_on_idle_enable 0 + write /sys/module/lpm_levels/parameters/sleep_disabled Y +on property:sys.boot_completed=1 + # Enable UFS powersaving + write /sys/devices/soc/${ro.boot.bootdevice}/clkscale_enable 1 + write /sys/devices/soc/${ro.boot.bootdevice}/clkgate_enable 1 + write /sys/devices/soc/${ro.boot.bootdevice}/hibern8_on_idle_enable 1 + write /sys/module/lpm_levels/parameters/sleep_disabled N +on charger + # Enable UFS powersaving + write /sys/devices/soc/${ro.boot.bootdevice}/clkscale_enable 1 + write /sys/devices/soc/${ro.boot.bootdevice}/clkgate_enable 1 + write /sys/devices/soc/${ro.boot.bootdevice}/hibern8_on_idle_enable 1 + write /sys/class/typec/port0/port_type sink + write /sys/module/lpm_levels/parameters/sleep_disabled N</pre> + +<h3 id="defer-non-critical-initialization">Defer non-critical initialization</h3> + +<p> +Non-critical initialization such as ZRAM can be deferred to boot_complete. +</p> + +<pre +class="prettyprint"> +on property:sys.boot_completed=1 + # Enable ZRAM on boot_complete + swapon_all /vendor/etc/fstab.${ro.hardware}</pre> + <h2 id="optimizing-boot-animation">Optimizing boot animation</h2> <p> diff --git a/en/security/_toc.yaml b/en/security/_toc.yaml index c8e29d4a..d1fb641a 100644 --- a/en/security/_toc.yaml +++ b/en/security/_toc.yaml @@ -43,6 +43,8 @@ toc: section: - title: 2017 Bulletins section: + - title: December + path: /security/bulletin/2017-12-01 - title: November path: /security/bulletin/2017-11-01 - title: October @@ -113,6 +115,8 @@ toc: section: - title: Overview path: /security/bulletin/pixel/index + - title: December 2017 + path: /security/bulletin/pixel/2017-12-01 - title: November 2017 path: /security/bulletin/pixel/2017-11-01 - title: October 2017 @@ -131,6 +135,8 @@ toc: path: /security/authentication/fingerprint-hal - title: Gatekeeper path: /security/authentication/gatekeeper +- title: Biometric Unlock + path: /security/biometric/ - title: Keystore section: - title: Overview diff --git a/en/security/biometric/index.html b/en/security/biometric/index.html new file mode 100644 index 00000000..6961e586 --- /dev/null +++ b/en/security/biometric/index.html @@ -0,0 +1,287 @@ +<html devsite> + <head> + <title>Measuring Biometric Unlock Security</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + + + +<p> +Today, biometric-based unlock modalities are evaluated almost solely on the +basis of <em>False Accept Rate (FAR)</em>, a metric that defines how often a +model mistakenly accepts a randomly chosen incorrect input. While this is a +useful measure, it does not provide sufficient information to evaluate how well +the model stands up to targeted attacks. +</p> + +<h2 id="metrics">Metrics</h2> + +<p> +Android 8.1 introduces two new metrics associated with biometric unlocks that +are intended to help device manufacturers evaluate their security more +accurately: +</p> + +<ul> +<li><em>Imposter Accept Rate (IAR)</em>: The chance that a biometric model +accepts input that is meant to mimic a known good sample. For example, in the <a +href="https://support.google.com/nexus/answer/6093922">Smart Lock</a> trusted +voice (voice unlock) mechanism, this would measure how often someone trying to +mimic a user's voice (using similar tone, accent, etc) can unlock their device. +We call such attacks <em>Imposter Attacks</em>.</li> +<li><em>Spoof Accept Rate (SAR)<strong>:</strong></em> The chance that a +biometric model accepts a previously recorded, known good sample. For example, +with voice unlock this would measure the chances of unlocking a user's phone +using a recorded sample of them saying: "Ok, Google" We call such attacks +<em>Spoof Attacks<strong>.</strong></em></li> +</ul> + +<p> +Of these, IAR measurements are not universally useful for all biometric +modalities. Consider fingerprint for example. An attacker could create a mold of +a user's fingerprint and attempt to use that to bypass the fingerprint sensor, +which would count as a spoof attack. However, there isn't a way to mimic a +fingerprint that would be accepted as the user's - and so there's not a clear +notion of an imposter attack against fingerprint sensors. +</p> + +<p> +SAR, however, works for every biometric modality. +</p> + +<h3 id="example-attacks">Example attacks</h3> + +<p> +The table below lists examples of imposter and spoof attacks for four +modalities. +</p> + +<table> + <tr> + <th>Modality</th> + <th>Imposter Attack</th> + <th>Spoof Attack</th> + </tr> + <tr> + <td>Fingerprint + </td> + <td>N/A + </td> + <td>Fingerprint + Fingerprint mold + </td> + </tr> + <tr> + <td>Face + </td> + <td>Trying to look like the user + </td> + <td>High-res photo, Latex (or other high quality) face masks + </td> + </tr> + <tr> + <td>Voice + </td> + <td>Trying to sound like the user + </td> + <td>Recording + </td> + </tr> + <tr> + <td>Iris + </td> + <td>N/A + </td> + <td>High-res photo + contact lens + </td> + </tr> +</table> + +<p> +<strong>Table 1. Example attacks</strong> +</p> + +<p> +See <a href="#test-methods">Test methodology</a> for advice and more details on +methodologies to measure SAR and IAR for different biometrics. +</p> + +<h3 id="strong-weak-unlocks">Strong vs. weak unlocks</h3> + +<p> +The bar for an unlock to be considered strong is a combination of the three +accept rates - FAR, IAR, and SAR. In cases where an imposter attack does not +exist, we consider only the FAR and SAR. +</p> + +<p> +See the <a href="https://source.android.com/compatibility/android-cdd">Android +Compatibility Definition Document</a> (CDD) for the measures to be taken for +weak unlock modalities<strong>.</strong> +</p> + +<h2 id="test-methods">Test methodology</h2> + +<p> +Here we explain considerations and offer advice regarding test setups to measure +spoof (SAR) and imposter acceptance rates (IAR) for biometric unlock modalities. +See <a href="#metrics">Metrics</a> for more information on what these metrics mean +and why they're useful. +</p> + +<h3 id="common-considerations">Common considerations</h3> + +<p> +While each modality requires a different test setup, there are a few common +aspects that apply to all of them. +</p> + +<h4 id="test-hw">Test the actual hardware</h4> + +<p> +Collected SAR/IAR metrics can be inaccurate when biometric models are tested +under idealized conditions and on different hardware than it would actually +appear on in a mobile device. For example, voice unlock models that are +calibrated in an anechoic chamber using a multi-microphone setup behave very +differently when used on a single microphone device in a noisy environment. In +order to capture accurate metrics, tests should be carried out on an actual +device with the hardware installed, and failing that with the hardware as it +would appear on the device. +</p> + +<h4 id="known-attacks">Use known attacks</h4> + +<p> +Most biometric modalities in use today have been successfully spoofed, and +public documentation of the attack methodology exists. Below we provide a brief +high-level overview of test setups for modalities with known attacks. We +recommend using the setup outlined here wherever possible. +</p> + +<h4 id="anticipate-attacks">Anticipate new attacks</h4> + +<p> +For modalities where significant new improvements have been made, the test setup +document may not contain a suitable setup, and no known public attack may exist. +Existing modalities may also need their test setup tuned in the wake of a newly +discovered attack. In both cases you will need to come up with a reasonable test +setup. Please use the <a +href="https://issuetracker.google.com/issues/new?component=191476">Site +Feedback</a> link at the bottom of this page to let us know if you have set up a +reasonable mechanism that can be added. +</p> + +<h3 id="setups-for-different-modalities">Setups for different modalities</h3> + +<h4 id="fingerprint">Fingerprint</h4> + +<table> + <tr> + <td><strong>IAR</strong> + </td> + <td>Not needed. + </td> + </tr> + <tr> + <td><strong>SAR</strong> + </td> + <td> + <ul> +<li>Create fake fingerprints using a mold of the target fingerprint.</li> +<li>Measurement accuracy is sensitive to the quality of the fingerprint mold. +Dental silicon is a good choice.</li> +<li>The test setup should measure how often a fake fingerprint created with the +mold is able to unlock the device.</li> + </ul> + </td> + </tr> +</table> + +<h4 id="face-and-iris">Face and Iris</h4> + +<table> + <tr> + <td><strong>IAR</strong> + </td> + <td>Lower bound will be captured by SAR so separately measuring this is not +needed. + </td> + </tr> + <tr> + <td><strong>SAR</strong> + </td> + <td> + <ul> +<li>Test with photos of the target's face. For iris, the face will need to be +zoomed in to mimic the distance a user would normally use the feature.</li> +<li>Photos should be high resolution, otherwise results are misleading.</li> +<li>Photos should not be presented in a way that reveals they are images. For +example: + <ul> + <li>image borders should not be included</li> + <li>if the photo is on a phone, the phone screen/bezels should not be visible</li> + <li>if someone is holding the photo, their hands should not be seen</li> + </ul> + </li> +<li>For straight angles, the photo should fill the sensor so nothing else +outside can be seen.</li> +<li>Face and iris models are typically more permissive when the sample +(face/iris/photo) is at an acute angle w.r.t to the camera (to mimic the use +case of a user holding the phone straight in front of them and pointing up at +their face). Testing at this angle will help determine if your model is +susceptible to spoofing.</li> +<li>The test setup should measure how often an image of the face or iris is able +to unlock the device.</li> +</ul> +</li> +</ul> + </td> + </tr> +</table> + +<h4 id="voice">Voice</h4> + +<table> + <tr> + <td><strong>IAR</strong> + </td> + <td> + <ul> +<li>Test using a setup where participants hear a positive sample and then try to +mimic it.</li> +<li>Test the model with participants across genders and with different accents +to ensure coverage of edge cases where some intonations/accents have a higher +FAR.</li> +</ul> + </td> + </tr> + <tr> + <td><strong>SAR</strong> + </td> + <td> + <ul> +<li>Test with recordings of the target's voice.</li> +<li>The recording needs to be of a reasonably high quality, or the results will +be misleading.</li> +</ul> + </td> + </tr> +</table> +</body> +</html> diff --git a/en/security/bulletin/2017-06-01.html b/en/security/bulletin/2017-06-01.html index 4dc34227..52bf53a6 100644 --- a/en/security/bulletin/2017-06-01.html +++ b/en/security/bulletin/2017-06-01.html @@ -131,13 +131,6 @@ to access data outside of its permission levels.</p> <th>Updated AOSP versions</th> </tr> <tr> - <td>CVE-2017-0639</td> - <td><a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/f196061addcc56878078e5684f2029ddbf7055ff">A-35310991</a></td> - <td>ID</td> - <td>High</td> - <td>4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> - </tr> - <tr> <td>CVE-2017-0645</td> <td><a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/14b7d7e1537af60b7bca6c7b9e55df0dc7c6bf41">A-35385327</a></td> <td>EoP</td> @@ -1119,6 +1112,32 @@ site</a>.</p> <td>June 05, 2017</td> </tr> </table> + +<p>Google device updates also contain patches for these security +vulnerabilities, if applicable:</p> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Updated AOSP versions</th> + </tr> + <tr> + <td>CVE-2017-0639</td> + <td><a href="https://android.googlesource.com/platform/packages/apps/Bluetooth/+/f196061addcc56878078e5684f2029ddbf7055ff">A-35310991</a></td> + <td>ID</td> + <td>High</td> + <td>4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> + </tr> +</table> + <h2 id="acknowledgements">Acknowledgements</h2> <p>We would like to thank these researchers for their contributions:</p> diff --git a/en/security/bulletin/2017-12-01.html b/en/security/bulletin/2017-12-01.html new file mode 100644 index 00000000..c841d979 --- /dev/null +++ b/en/security/bulletin/2017-12-01.html @@ -0,0 +1,801 @@ +<html devsite> + <head> + <title>Android Security Bulletin—December 2017</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> + +<p><em>Published December 4, 2017</em> +</p> + +<p> +The Android Security Bulletin contains details of security vulnerabilities +affecting Android devices. Security patch levels of 2017-12-05 or later address +all of these issues. To learn how to check a device's security patch level, see +<a href="https://support.google.com/pixelphone/answer/4457705">Check & update +your Android version</a>. +</p> +<p> +Android partners are notified of all issues at least a month before publication. +Source code patches for these issues will be released to the Android Open Source +Project (AOSP) repository in the next 48 hours. We will revise this bulletin +with the AOSP links when they are available. +</p> +<p> +The most severe of these issues is a critical security vulnerability in Media +framework that could enable a remote attacker using a specially crafted file to +execute arbitrary code within the context of a privileged process. The <a +href="/security/overview/updates-resources.html#severity">severity +assessment</a> is based on the effect that exploiting the vulnerability would +possibly have on an affected device, assuming the platform and service +mitigations are turned off for development purposes or if successfully bypassed. +</p> +<p> +We have had no reports of active customer exploitation or abuse of these newly +reported issues. Refer to the <a href="#mitigations">Android +and Google Play Protect mitigations</a> section for details on the +<a href="/security/enhancements/index.html">Android +security platform protections</a> and Google Play Protect, which improve the +security of the Android platform. +</p> +<p class="note"> +<strong>Note:</strong> Information on the latest over-the-air update (OTA) and +firmware images for Google devices is available in the +<a href="/security/bulletin/pixel/2017-12-01">December 2017 Pixel / Nexus +Security Bulletin</a>. +</p> +<h2 id="mitigations">Android and Google Service +Mitigations</h2> +<p> +This is a summary of the mitigations provided by the <a +href="/security/enhancements/index.html">Android +security platform</a> and service protections such as <a +href="https://www.android.com/play-protect">Google Play Protect</a>. These +capabilities reduce the likelihood that security vulnerabilities could be +successfully exploited on Android. +</p> +<ul> + <li>Exploitation for many issues on Android is made more difficult by + enhancements in newer versions of the Android platform. We encourage all users + to update to the latest version of Android where possible.</li> + <li>The Android security team actively monitors for abuse through <a + href="https://www.android.com/play-protect">Google Play Protect</a> and warns + users about <a + href="/security/reports/Google_Android_Security_PHA_classifications.pdf">Potentially + Harmful Applications</a>. Google Play Protect is enabled by default on devices + with <a href="http://www.android.com/gms">Google Mobile Services</a>, and is + especially important for users who install apps from outside of Google + Play.</li> +</ul> +<h2 id="2017-12-01-details">2017-12-01 security patch level—Vulnerability details</h2> +<p> +In the sections below, we provide details for each of the security +vulnerabilities that apply to the 2017-12-01 patch level. Vulnerabilities are +grouped under the component that they affect. There is a description of the +issue and a table with the CVE, associated references, <a href="#type">type +of vulnerability</a>, +<a href="/security/overview/updates-resources.html#severity">severity</a>, +and updated AOSP versions (where applicable). When available, we link the public +change that addressed the issue to the bug ID, like the AOSP change list. When +multiple changes relate to a single bug, additional references are linked to +numbers following the bug ID. +</p> +<h3 id="framework">Framework</h3> +<p>The most severe vulnerability in this section could enable a local malicious +application to bypass user interaction requirements in order to gain access to +additional permissions.</p> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Updated AOSP versions</th> + </tr> + <tr> + <td>CVE-2017-0807</td> + <td>A-35056974</td> + <td>EoP</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2</td> + </tr> + <tr> + <td>CVE-2017-0870</td> + <td>A-62134807</td> + <td>EoP</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-0871</td> + <td>A-65281159</td> + <td>EoP</td> + <td>High</td> + <td>8.0</td> + </tr> +</table> + + +<h3 id="media-framework">Media framework</h3> +<p>The most severe vulnerability in this section could enable a remote attacker +using a specially crafted file to execute arbitrary code within the context of +a privileged process.</p> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Updated AOSP versions</th> + </tr> + <tr> + <td>CVE-2017-0872</td> + <td>A-65290323</td> + <td>RCE</td> + <td>Critical</td> + <td>7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-0876</td> + <td>A-64964675</td> + <td>RCE</td> + <td>Critical</td> + <td>6.0</td> + </tr> + <tr> + <td>CVE-2017-0877</td> + <td>A-66372937</td> + <td>RCE</td> + <td>Critical</td> + <td>6.0</td> + </tr> + <tr> + <td>CVE-2017-0878</td> + <td>A-65186291</td> + <td>RCE</td> + <td>Critical</td> + <td>8.0</td> + </tr> + <tr> + <td>CVE-2017-13151</td> + <td>A-63874456</td> + <td>RCE</td> + <td>Critical</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-13153</td> + <td>A-65280854</td> + <td>EoP</td> + <td>High</td> + <td>8.0</td> + </tr> + <tr> + <td>CVE-2017-0837</td> + <td>A-64340921</td> + <td>EoP</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-0873</td> + <td>A-63316255</td> + <td>DoS</td> + <td>High</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-0874</td> + <td>A-63315932</td> + <td>DoS</td> + <td>High</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-0880</td> + <td>A-65646012</td> + <td>DoS</td> + <td>High</td> + <td>7.0, 7.1.1, 7.1.2</td> + </tr> + <tr> + <td>CVE-2017-13148</td> + <td>A-65717533</td> + <td>DoS</td> + <td>High</td> + <td>6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> +</table> + + +<h3 id="system">System</h3> +<p>The most severe vulnerability in this section could enable a proximate +attacker to execute arbitrary code within the context of a privileged +process.</p> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Updated AOSP versions</th> + </tr> + <tr> + <td>CVE-2017-13160</td> + <td>A-37160362</td> + <td>RCE</td> + <td>Critical</td> + <td>7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-13156</td> + <td>A-64211847</td> + <td>EoP</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-13157</td> + <td>A-32990341</td> + <td>ID</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-13158</td> + <td>A-32879915</td> + <td>ID</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>CVE-2017-13159</td> + <td>A-32879772</td> + <td>ID</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> +</table> + +<h2 id="2017-12-05-details">2017-12-05 security patch level—Vulnerability details</h2> +<p> +In the sections below, we provide details for each of the security +vulnerabilities that apply to the 2017-12-05 patch level. Vulnerabilities are +grouped under the component that they affect and include details such as the +CVE, associated references, <a href="#type">type of vulnerability</a>, +<a href="/security/overview/updates-resources.html#severity">severity</a>, +component (where applicable), and updated AOSP versions (where applicable). When +available, we link the public change that addressed the issue to the bug ID, +like the AOSP change list. When multiple changes relate to a single bug, +additional references are linked to numbers following the bug ID. +</p> + +<h3 id="kernel-components">Kernel components</h3> +<p>The most severe vulnerability in this section could enable a local malicious +application to execute arbitrary code within the context of a privileged +process.</p> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-13162</td> + <td>A-64216036<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>High</td> + <td>Binder</td> + </tr> + <tr> + <td>CVE-2017-0564</td> + <td>A-34276203<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>High</td> + <td>ION</td> + </tr> + <tr> + <td>CVE-2017-7533</td> + <td>A-63689921<br /> + <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=49d31c2f389acfe83417083e1208422b4091cd9"> +Upstream kernel</a></td> + <td>EoP</td> + <td>High</td> + <td>File handling</td> + </tr> + <tr> + <td>CVE-2017-13174</td> + <td>A-63100473<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>High</td> + <td>EDL</td> + </tr> +</table> + + +<h3 id="mediatek-components">MediaTek components</h3> +<p>The most severe vulnerability in this section could enable a local malicious +application to execute arbitrary code within the context of a privileged +process.</p> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-13170</td> + <td>A-36102397<a href="#asterisk">*</a><br /> + M-ALPS03359280</td> + <td>EoP</td> + <td>High</td> + <td>Display driver</td> + </tr> + <tr> + <td>CVE-2017-13171</td> + <td>A-64316572<a href="#asterisk">*</a><br /> + M-ALPS03479086</td> + <td>EoP</td> + <td>High</td> + <td>Performance service</td> + </tr> + <tr> + <td>CVE-2017-13173</td> + <td>A-28067350<a href="#asterisk">*</a><br /> + M-ALPS02672361</td> + <td>EoP</td> + <td>High</td> + <td>System server</td> + </tr> +</table> + + +<h3 id="nvidia-components">NVIDIA components</h3> +<p>The most severe vulnerability in this section could enable a local malicious +application to execute arbitrary code within the context of a privileged +process.</p> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-6262</td> + <td>A-38045794<a href="#asterisk">*</a><br /> + N-CVE-2017-6262</td> + <td>EoP</td> + <td>High</td> + <td>NVIDIA driver</td> + </tr> + <tr> + <td>CVE-2017-6263</td> + <td>A-38046353<a href="#asterisk">*</a><br /> + N-CVE-2017-6263</td> + <td>EoP</td> + <td>High</td> + <td>NVIDIA driver</td> + </tr> + <tr> + <td>CVE-2017-6276</td> + <td>A-63802421<a href="#asterisk">*</a><br /> + N-CVE-2017-6276</td> + <td>EoP</td> + <td>High</td> + <td>Mediaserver</td> + </tr> +</table> + + +<h3 id="qualcomm-components">Qualcomm components</h3> +<p>The most severe vulnerability in this section could enable a remote attacker +using a specially crafted file to execute arbitrary code within the context of +a privileged process.</p> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-11043</td> + <td>A-64728953<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=613f91ebcd0838c2c2bec3657e36dd57fcc6a7ea"> +QC-CR#2067820</a></td> + <td>RCE</td> + <td>Critical</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2016-3706</td> + <td>A-34499281<br /> + <a href="https://source.codeaurora.org/quic/le/oe/recipes/commit/?h=LNX.LE.5.3&id=6cfcc1c582a565f5360f7a3977f4a8f42d5245cd"> +QC-CR#1058691</a> + [<a href="https://source.codeaurora.org/quic/le/oe/recipes/commit/?h=LNX.LE.5.3&id=0f70f82655ceac279f9f0c76d7995294189096f9">2</a>]</td> + <td>RCE</td> + <td>Critical</td> + <td>UDP RPC</td> + </tr> + <tr> + <td>CVE-2016-4429</td> + <td>A-68946906<br /> + <a href="https://source.codeaurora.org/quic/le/oe/recipes/commit/?h=LNX.LE.5.3&id=6cfcc1c582a565f5360f7a3977f4a8f42d5245cd"> +QC-CR#1058691</a> + [<a href="https://source.codeaurora.org/quic/le/oe/recipes/commit/?h=LNX.LE.5.3&id=0f70f82655ceac279f9f0c76d7995294189096f9">2</a>]</td> + <td>RCE</td> + <td>Critical</td> + <td>UDP RPC</td> + </tr> + <tr> + <td>CVE-2017-11007</td> + <td>A-66913719<br /> + <a href="https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=5c710156bb55b0a085da7c4142b124f3cd986d25"> +QC-CR#2068824</a></td> + <td>EoP</td> + <td>High</td> + <td>Fastboot</td> + </tr> + <tr> + <td>CVE-2017-14904</td> + <td>A-63662821<a href="#asterisk">*</a><br /> + QC-CR#2109325</td> + <td>EoP</td> + <td>High</td> + <td>Gralloc</td> + </tr> + <tr> + <td>CVE-2017-9716</td> + <td>A-63868627<br /> + <a href="https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=aab2cc06db7cb6c7589bef71e65b5acfa58adc33"> +QC-CR#2006695</a></td> + <td>EoP</td> + <td>High</td> + <td>Qbt1000 driver</td> + </tr> + <tr> + <td>CVE-2017-14897</td> + <td>A-65468973<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=11e7de77bd5ab0a7706a013598f845ad0c4a8b4c"> +QC-CR#2054091</a></td> + <td>EoP</td> + <td>High</td> + <td>RPMB driver</td> + </tr> + <tr> + <td>CVE-2017-14902</td> + <td>A-65468970<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=8c4901802968b8c8356860ee689b1ef9cd2cbfe4"> +QC-CR#2061287</a></td> + <td>EoP</td> + <td>High</td> + <td>MProc</td> + </tr> + <tr> + <td>CVE-2017-14895</td> + <td>A-65468977<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=b15f0ff7351eb6b6a8f6694b4cd5ad27145bd439"> +QC-CR#2009308</a></td> + <td>EoP</td> + <td>High</td> + <td>WLAN</td> + </tr> +</table> + + +<h3 id="qualcomm-closed-source-components">Qualcomm closed-source +components</h3> +<p>These vulnerabilities affect Qualcomm components and are described in +further detail in the appropriate Qualcomm AMSS security bulletin or security +alert. The severity assessment of these issues is provided directly by +Qualcomm.</p> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-6211 </td> + <td>A-36217326<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Critical</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-14908</td> + <td>A-62212840<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-14909</td> + <td>A-62212839<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-14914</td> + <td>A-62212297<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-14916</td> + <td>A-62212841<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-14917</td> + <td>A-62212740<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-14918</td> + <td>A-65946406<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-11005</td> + <td>A-66913715<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-11006</td> + <td>A-66913717<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>High</td> + <td>Closed-source component</td> + </tr> +</table> + + +<h2 id="common-questions-and-answers">Common questions and answers</h2> +<p> +This section answers common questions that may occur after reading this +bulletin. +</p> +<p> +<strong>1. How do I determine if my device is updated to address these issues? +</strong> +</p> +<p> +To learn how to check a device's security patch level, see <a +href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Check +& update your Android version</a>. +</p> +<ul> + <li>Security patch levels of 2017-12-01 or later address all issues associated + with the 2017-12-01 security patch level.</li> + <li>Security patch levels of 2017-12-05 or later address all issues associated + with the 2017-12-05 security patch level and all previous patch levels.</li> +</ul> +<p> +Device manufacturers that include these updates should set the patch string +level to: +</p> +<ul> + <li>[ro.build.version.security_patch]:[2017-12-01]</li> + <li>[ro.build.version.security_patch]:[2017-12-05]</li> +</ul> +<p> +<strong>2. Why does this bulletin have two security patch levels?</strong> +</p> +<p> +This bulletin has two security patch levels so that Android partners have the +flexibility to fix a subset of vulnerabilities that are similar across all +Android devices more quickly. Android partners are encouraged to fix all issues +in this bulletin and use the latest security patch level. +</p> +<ul> + <li>Devices that use the 2017-12-01 security patch level must include all issues + associated with that security patch level, as well as fixes for all issues + reported in previous security bulletins.</li> + <li>Devices that use the security patch level of 2017-12-05 or newer must + include all applicable patches in this (and previous) security + bulletins.</li> +</ul> +<p> +Partners are encouraged to bundle the fixes for all issues they are addressing +in a single update. +</p> +<p id="type"> +<strong>3. What do the entries in the <em>Type</em> column mean?</strong> +</p> +<p> +Entries in the <em>Type</em> column of the vulnerability details table reference +the classification of the security vulnerability. +</p> +<table> + <col width="25%"> + <col width="75%"> + <tr> + <th>Abbreviation</th> + <th>Definition</th> + </tr> + <tr> + <td>RCE</td> + <td>Remote code execution</td> + </tr> + <tr> + <td>EoP</td> + <td>Elevation of privilege</td> + </tr> + <tr> + <td>ID</td> + <td>Information disclosure</td> + </tr> + <tr> + <td>DoS</td> + <td>Denial of service</td> + </tr> + <tr> + <td>N/A</td> + <td>Classification not available</td> + </tr> +</table> +<p> +<strong>4. What do the entries in the <em>References</em> column mean?</strong> +</p> +<p> +Entries under the <em>References</em> column of the vulnerability details table +may contain a prefix identifying the organization to which the reference value +belongs. +</p> +<table> + <col width="25%"> + <col width="75%"> + <tr> + <th>Prefix</th> + <th>Reference</th> + </tr> + <tr> + <td>A-</td> + <td>Android bug ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm reference number</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek reference number</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA reference number</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom reference number</td> + </tr> +</table> +<p id="asterisk"> +<strong>5. What does a * next to the Android bug ID in the <em>References</em> +column mean?</strong> +</p> +<p> +Issues that are not publicly available have a * next to the Android bug ID in +the <em>References</em> column. The update for that issue is generally contained +in the latest binary drivers for Nexus devices available from the <a +href="https://developers.google.com/android/nexus/drivers">Google Developer +site</a>. +</p> +<p> +<strong>6. Why are security vulnerabilities split between this bulletin and +device/partner security bulletins, such as the Pixel / Nexus +bulletin?</strong> +</p> +<p> +Security vulnerabilities that are documented in this security bulletin are +required in order to declare the latest security patch level on Android devices. +Additional security vulnerabilities that are documented in the +device / partner +security bulletins are not required for declaring a security patch level. +Android device and chipset manufacturers are encouraged to document the presence +of other fixes on their devices through their own security websites, such as the +<a href="https://security.samsungmobile.com/securityUpdate.smsb">Samsung</a>, +<a href="https://lgsecurity.lge.com/security_updates.html">LGE</a>, or +<a href="/security/bulletin/pixel/">Pixel / Nexus</a> security bulletins. +</p> +<h2 id="versions">Versions</h2> +<table> + <col width="25%"> + <col width="25%"> + <col width="50%"> + <tr> + <th>Version</th> + <th>Date</th> + <th>Notes</th> + </tr> + <tr> + <td>1.0</td> + <td>December 4, 2017</td> + <td>Bulletin published.</td> + </tr> +</table> +</body></html> diff --git a/en/security/bulletin/2017.html b/en/security/bulletin/2017.html index 2da8877c..0f26eeea 100644 --- a/en/security/bulletin/2017.html +++ b/en/security/bulletin/2017.html @@ -37,16 +37,59 @@ of all bulletins, see the <a href="index.html">Android Security Bulletins</a> ho <th>Security patch level</th> </tr> <tr> + <td><a href="/security/bulletin/2017-12-01.html">December 2017</a></td> + <td>Coming soon + <!-- + <a href="/security/bulletin/2017-12-01.html">English</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-12-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-12-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>December 4, 2017</td> + <td>2017-12-01<br> + 2017-12-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/2017-11-01.html">November 2017</a></td> + <td> + <a href="/security/bulletin/2017-11-01.html">English</a> / + <a href="/security/bulletin/2017-11-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-11-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-11-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-11-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-11-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>November 6, 2017</td> + <td>2017-11-01<br> + 2017-11-05<br> + 2017-11-06</td> + </tr> + <tr> + <td><a href="/security/bulletin/2017-10-01.html">October 2017</a></td> + <td> + <a href="/security/bulletin/2017-10-01.html">English</a> / + <a href="/security/bulletin/2017-10-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-10-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-10-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-10-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-10-01.html?hl=zh-tw">中文 (台灣)</a> + </td> + <td>October 2, 2017</td> + <td>2017-10-01<br> + 2017-10-05</td> + </tr> + <tr> <td><a href="2017-09-01.html">September 2017</a></td> - <td>Coming soon - <!-- + <td> <a href="/security/bulletin/2017-09-01.html">English</a> / <a href="/security/bulletin/2017-09-01.html?hl=ja">日本語</a> / <a href="/security/bulletin/2017-09-01.html?hl=ko">한국어</a> / <a href="/security/bulletin/2017-09-01.html?hl=ru">ру́сский</a> / <a href="/security/bulletin/2017-09-01.html?hl=zh-cn">中文 (中国)</a> / <a href="/security/bulletin/2017-09-01.html?hl=zh-tw">中文 (台灣)</a> - --> </td> <td>September 5, 2017</td> <td>2017-09-01<br> @@ -54,15 +97,13 @@ of all bulletins, see the <a href="index.html">Android Security Bulletins</a> ho </tr> <tr> <td><a href="2017-08-01.html">August 2017</a></td> - <td>Coming soon - <!-- + <td> <a href="/security/bulletin/2017-08-01.html">English</a> / <a href="/security/bulletin/2017-08-01.html?hl=ja">日本語</a> / <a href="/security/bulletin/2017-08-01.html?hl=ko">한국어</a> / <a href="/security/bulletin/2017-08-01.html?hl=ru">ру́сский</a> / <a href="/security/bulletin/2017-08-01.html?hl=zh-cn">中文 (中国)</a> / <a href="/security/bulletin/2017-08-01.html?hl=zh-tw">中文 (台灣)</a> - --> </td> <td>August 7, 2017</td> <td>2017-08-01<br> diff --git a/en/security/bulletin/index.html b/en/security/bulletin/index.html index 987801e4..cb8a84f1 100644 --- a/en/security/bulletin/index.html +++ b/en/security/bulletin/index.html @@ -68,16 +68,30 @@ Android Open Source Project (AOSP), the upstream Linux kernel, and system-on-chi <th>Security patch level</th> </tr> <tr> - <td><a href="/security/bulletin/2017-11-01.html">November 2017</a></td> + <td><a href="/security/bulletin/2017-12-01.html">December 2017</a></td> <td>Coming soon <!-- + <a href="/security/bulletin/2017-12-01.html">English</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/2017-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/2017-12-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/2017-12-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>December 4, 2017</td> + <td>2017-12-01<br> + 2017-12-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/2017-11-01.html">November 2017</a></td> + <td> <a href="/security/bulletin/2017-11-01.html">English</a> / <a href="/security/bulletin/2017-11-01.html?hl=ja">日本語</a> / <a href="/security/bulletin/2017-11-01.html?hl=ko">한국어</a> / <a href="/security/bulletin/2017-11-01.html?hl=ru">ру́сский</a> / <a href="/security/bulletin/2017-11-01.html?hl=zh-cn">中文 (中国)</a> / <a href="/security/bulletin/2017-11-01.html?hl=zh-tw">中文 (台灣)</a> - --> </td> <td>November 6, 2017</td> <td>2017-11-01<br> diff --git a/en/security/bulletin/pixel/2017-12-01.html b/en/security/bulletin/pixel/2017-12-01.html new file mode 100644 index 00000000..c40844aa --- /dev/null +++ b/en/security/bulletin/pixel/2017-12-01.html @@ -0,0 +1,735 @@ +<html devsite> + <head> + <title>Pixel / Nexus Security Bulletin—December 2017</title> + <meta name="project_path" value="/_project.yaml" /> + <meta name="book_path" value="/_book.yaml" /> + </head> + <body> + <!-- + Copyright 2017 The Android Open Source Project + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + //www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + --> +<p><em>Published December 4, 2017 | Updated December 5, 2017</em></p> + +<p> +The Pixel / Nexus Security Bulletin contains details of security +vulnerabilities and functional improvements affecting <a +href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">supported +Google Pixel and Nexus devices</a> (Google devices). For Google devices, +security patch levels of 2017-12-05 or later address all issues in this +bulletin. To learn how to check a device's security patch level, see <a +href="https://support.google.com/pixelphone/answer/4457705">Check & update your +Android version</a>. +</p> +<p> +All supported Google devices will receive an update to the 2017-12-05 patch +level. We encourage all customers to accept these updates to their devices. +</p> +<p class="note"> +<strong>Note:</strong> The Google device firmware images are available on the <a +href="//developers.google.com/android/nexus/images">Google Developer site</a>. +</p> +<h2 id="announcements">Announcements</h2> +<p> +In addition to the security vulnerabilities described in the <a +href="/security/bulletin/2017-12-01">December 2017 +Android Security Bulletin</a>, Pixel and Nexus devices also contain patches for +the security vulnerabilities described below. Partners were notified of these +issues at least a month ago and may choose to incorporate them as part of their +device updates. +</p> +<h2 id="security-patches">Security patches</h2> +<p> +Vulnerabilities are grouped under the component that they affect. There is a +description of the issue and a table with the CVE, associated references, <a +href="#type">type of vulnerability</a>, <a +href="/security/overview/updates-resources.html#severity">severity</a>, +and updated Android Open Source Project (AOSP) versions (where applicable). When +available, we link the public change that addressed the issue to the bug ID, +like the AOSP change list. When multiple changes relate to a single bug, +additional references are linked to numbers following the bug ID. +</p> + +<h3 id="media-framework">Media framework</h3> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Updated AOSP versions</th> + </tr> + <tr> + <td>CVE-2017-13154</td> + <td>A-63666573</td> + <td>EoP</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-0879</td> + <td rowspan="2">A-65025028</td> + <td>ID</td> + <td>Moderate</td> + <td>7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>DoS</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13149</td> + <td rowspan="2">A-65719872</td> + <td>ID</td> + <td>Moderate</td> + <td>7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>DoS</td> + <td>High</td> + <td>5.1.1, 6.0, 6.0.1</td> + </tr> + <tr> + <td rowspan="2">CVE-2017-13150</td> + <td rowspan="2">A-38328132</td> + <td>ID</td> + <td>Moderate</td> + <td>7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> + <tr> + <td>DoS</td> + <td>High</td> + <td>6.0, 6.0.1</td> + </tr> + <tr> + <td>CVE-2017-13152</td> + <td>A-62872384</td> + <td>ID</td> + <td>Moderate</td> + <td>5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0</td> + </tr> +</table> + + +<h3 id="broadcom-components">Broadcom components</h3> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-13161</td> + <td>A-63930471<a href="#asterisk">*</a><br /> + BC-V2017092501</td> + <td>EoP</td> + <td>Moderate</td> + <td>undefined</td> + </tr> +</table> + + +<h3 id="kernel-components">Kernel components</h3> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-13167</td> + <td>A-37240993<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>High</td> + <td>Sound timer</td> + </tr> + <tr> + <td>CVE-2017-13163</td> + <td>A-37429972<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>MTP USB driver</td> + </tr> + <tr> + <td>CVE-2017-15868</td> + <td>A-33982955<br /> + <a href="https://patchwork.kernel.org/patch/9882449/">Upstream kernel</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Wireless driver</td> + </tr> + <tr> + <td>CVE-2017-13165</td> + <td>A-31269937<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>File system</td> + </tr> + <tr> + <td>CVE-2017-13166</td> + <td>A-34624167<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>V4L2 video driver</td> + </tr> + <tr> + <td>CVE-2017-1000380</td> + <td>A-64217740<br /> + <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d11662f4f798b50d8c8743f433842c3e40fe3378"> +Upstream kernel</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Sound timer driver</td> + </tr> + <tr> + <td>CVE-2017-13168</td> + <td>A-65023233<a href="#asterisk">*</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>SCSI driver</td> + </tr> + <tr> + <td>CVE-2017-13169</td> + <td>A-37512375<a href="#asterisk">*</a></td> + <td>ID</td> + <td>Moderate</td> + <td>Camera server</td> + </tr> + <tr> + <td>CVE-2017-13164</td> + <td>A-36007193<a href="#asterisk">*</a></td> + <td>ID</td> + <td>Moderate</td> + <td>Binder driver</td> + </tr> +</table> + + +<h3 id="mediatek-components">MediaTek components</h3> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-13172</td> + <td>A-36493287<a href="#asterisk">*</a><br /> + M-ALPS03495791</td> + <td>EoP</td> + <td>Moderate</td> + <td>Bluetooth driver</td> + </tr> +</table> + + +<h3 id="nvidia-components">NVIDIA components</h3> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-6280</td> + <td>A-63851980<a href="#asterisk">*</a><br /> + N-CVE-2017-6280</td> + <td>ID</td> + <td>Moderate</td> + <td>NVIDIA driver</td> + </tr> + <tr> + <td>CVE-2017-13175</td> + <td>A-64339309<a href="#asterisk">*</a><br /> + N-CVE-2017-13175</td> + <td>ID</td> + <td>Moderate</td> + <td>Libwilhelm</td> + </tr> +</table> + + +<h3 id="qualcomm-components">Qualcomm components</h3> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-9708</td> + <td>A-62674846<a href="#asterisk">*</a><br /> + QC-CR#2081806</td> + <td>EoP</td> + <td>Moderate</td> + <td>Kernel</td> + </tr> + <tr> + <td>CVE-2017-11042</td> + <td>A-38232268<a href="#asterisk">*</a><br /> + QC-CR#2070438</td> + <td>EoP</td> + <td>Moderate</td> + <td>Binder</td> + </tr> + <tr> + <td>CVE-2017-11030</td> + <td>A-64431967<br /> + <a +href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=89e6c2d38405cdeefaa278cbf6d18791f255ee5e">QC-CR#2034255</a> + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=2be7caec635de9fcf0d2145f858635e9366f0f4f">2</a>]</td> + <td>EoP</td> + <td>Moderate</td> + <td>Display</td> + </tr> + <tr> + <td>CVE-2017-9703</td> + <td>A-34329758<a href="#asterisk">*</a><br /> + QC-CR#2038086</td> + <td>EoP</td> + <td>Moderate</td> + <td>Video driver</td> + </tr> + <tr> + <td>CVE-2017-9718</td> + <td>A-36386076<a href="#asterisk">*</a><br /> + QC-CR#2045918</td> + <td>EoP</td> + <td>Moderate</td> + <td>Kernel</td> + </tr> + <tr> + <td>CVE-2017-8244</td> + <td>A-35138888<a href="#asterisk">*</a><br /> + QC-CR#2013361</td> + <td>EoP</td> + <td>Moderate</td> + <td>Debugfs driver</td> + </tr> + <tr> + <td>CVE-2017-14901</td> + <td>A-65468984<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=e4f54acdc4e0d41530d0189e6c59301b8b900ba6"> +QC-CR#2059714</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-9698</td> + <td>A-63868678<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=79492490423bc369da4ded113dca7f5a5b38e656"> +QC-CR#2023860</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Graphics</td> + </tr> + <tr> + <td>CVE-2017-9700</td> + <td>A-63868780<br /> + <a href="https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=c2e5af21d3d3bb856ff3b5783aa2a6147a4c9089"> +QC-CR#2043822</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Audio</td> + </tr> + <tr> + <td>CVE-2017-9722</td> + <td>A-64453224<br /> + <a +href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=ab0ae43628cff92d10792b762667ddfaf243d796">QC-CR#2034239</a> + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=cd7e77fbab7e2b7e737a10d5300e826572fee82f">2</a>]</td> + <td>EoP</td> + <td>Moderate</td> + <td>Display</td> + </tr> + <tr> + <td>CVE-2017-11049</td> + <td>A-64728945<br /> + <a href="https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-3.18.git;a=commit;h=430f3805c82634a3cb969d83acc4fc4c0ee6af27"> +QC-CR#2034909</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Display</td> + </tr> + <tr> + <td>CVE-2017-11047</td> + <td>A-64728948<br /> + <a href="https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-4.4.git;a=commit;h=8d0b17fdbea77753ce4388e4b7538f1c32b2b730"> +QC-CR#2057285</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Display</td> + </tr> + <tr> + <td>CVE-2017-14898</td> + <td>A-65468978<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=f4bc0d11aa35ffe5f58fdcb7e4bfeffa08011128"> +QC-CR#2054748</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-14899</td> + <td>A-65468980<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=424a72b2a924d32e6a777c93c5ccf8979c776d25"> +QC-CR#2054752</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-11044</td> + <td>A-65468989<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=704512a933415f38c190d21e28bcd2dd122dc4b8"> +QC-CR#2063166</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Graphics</td> + </tr> + <tr> + <td>CVE-2017-11045</td> + <td>A-65468993<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=6c815ebc37f49e4e3edb10def9c45f2fd9362a84"> +QC-CR#2060377</a> + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=2a657721dd71aec745534af9f8712537b83c410e">2</a>]</td> + <td>EoP</td> + <td>Moderate</td> + <td>Camera</td> + </tr> + <tr> + <td>CVE-2017-14900</td> + <td>A-65468983<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=8a4da03089ec78d44e44efa594d08cecc177326e"> +QC-CR#2058468</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-9710</td> + <td>A-63868933<br /> + <a href="https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-4.4.git;a=commit;h=938946fef09130dfe6b8158bfebeb85a4c5c29e3"> +QC-CR#2023883</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Data HLOS</td> + </tr> + <tr> + <td>CVE-2017-11019</td> + <td>A-64453105<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=a2e451a1e1d973709ccd062c9aade669cd0daca4"> +QC-CR#2030638</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Display</td> + </tr> + <tr> + <td>CVE-2017-11016</td> + <td>A-64453423<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=6bb0d13bbd9df966a9a2b801e5204937285413fe"> +QC-CR#2038685</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>Audio</td> + </tr> + <tr> + <td>CVE-2017-11033</td> + <td>A-64453422<br /> + <a +href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=b54141365805ae1a5254bff5442e1a103d3701d0">QC-CR#2031930</a> + [<a href="https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=fd98387b3d30da51773ad7597bb9febb87c70394">2</a>]</td> + <td>EoP</td> + <td>Moderate</td> + <td>Kernel</td> + </tr> + <tr> + <td>CVE-2017-14896</td> + <td>A-65468975<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=07c254f9c167b7114385a50abd29938db45d5052"> +QC-CR#2013716</a></td> + <td>EoP</td> + <td>Moderate</td> + <td>GUD mobicore driver</td> + </tr> + <tr> + <td>CVE-2017-8281</td> + <td>A-62378232<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=9b209c4552779edb86221787fb8681dd212e3a0c"> +QC-CR#2015892</a></td> + <td>ID</td> + <td>Moderate</td> + <td>DCI driver</td> + </tr> + <tr> + <td>CVE-2017-14903</td> + <td>A-63522505<a href="#asterisk">*</a><br /> + QC-CR#2088768</td> + <td>ID</td> + <td>Moderate</td> + <td>WLAN</td> + </tr> + <tr> + <td>CVE-2017-11031</td> + <td>A-64442463<br /> + <a href="https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=70b104dcaf84f61b9ae37fde4d9fca69170cebe5"> +QC-CR#2059181</a></td> + <td>ID</td> + <td>Moderate</td> + <td>Display</td> + </tr> + <tr> + <td>CVE-2017-14905</td> + <td>A-37719782<br /> + <a href="https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=4d9812973e8b12700afd8c3d6f36a94506ffb6fc"> +QC-CR#2061251</a></td> + <td>ID</td> + <td>Moderate</td> + <td>Wireless networking</td> + </tr> +</table> + + +<h3 id="qualcomm-closed-source-components">Qualcomm closed-source +components</h3> + +<table> + <col width="17%"> + <col width="19%"> + <col width="9%"> + <col width="14%"> + <col width="39%"> + <tr> + <th>CVE</th> + <th>References</th> + <th>Type</th> + <th>Severity</th> + <th>Component</th> + </tr> + <tr> + <td>CVE-2017-14907</td> + <td>A-62212113<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Critical</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2016-5341</td> + <td>A-63983006<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-9709 </td> + <td>A-65944335<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> + <tr> + <td>CVE-2017-15813</td> + <td>A-63979947<a href="#asterisk">*</a></td> + <td>N/A</td> + <td>Moderate</td> + <td>Closed-source component</td> + </tr> +</table> + +<h2 id="functional-updates">Functional updates</h2> +<p> +All supported Google devices will receive an Android 8.1 update as part of the December OTA. +Android 8.1 contains many functional updates and improvements to various parts of the +Android platform. +</p> + +<h2 id="common-questions-and-answers">Common questions and answers</h2> +<p> +This section answers common questions that may occur after reading this +bulletin. +</p> +<p> +<strong>1. How do I determine if my device is updated to address these issues? +</strong> +</p> +<p> +Security patch levels of 2017-12-05 or later address all issues associated with +the 2017-12-05 security patch level and all previous patch levels. To learn how +to check a device's security patch level, read the instructions on the <a +href="https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices">Pixel +and Nexus update schedule</a>. +</p> +<p id="type"> +<strong>2. What do the entries in the <em>Type</em> column mean?</strong> +</p> +<p> +Entries in the <em>Type</em> column of the vulnerability details table reference +the classification of the security vulnerability. +</p> +<table> + <col width="25%"> + <col width="75%"> + <tr> + <th>Abbreviation</th> + <th>Definition</th> + </tr> + <tr> + <td>RCE</td> + <td>Remote code execution</td> + </tr> + <tr> + <td>EoP</td> + <td>Elevation of privilege</td> + </tr> + <tr> + <td>ID</td> + <td>Information disclosure</td> + </tr> + <tr> + <td>DoS</td> + <td>Denial of service</td> + </tr> + <tr> + <td>N/A</td> + <td>Classification not available</td> + </tr> +</table> +<p> +<strong>3. What do the entries in the <em>References</em> column mean?</strong> +</p> +<p> +Entries under the <em>References</em> column of the vulnerability details table +may contain a prefix identifying the organization to which the reference value +belongs. +</p> +<table> + <col width="25%"> + <col width="75%"> + <tr> + <th>Prefix</th> + <th>Reference</th> + </tr> + <tr> + <td>A-</td> + <td>Android bug ID</td> + </tr> + <tr> + <td>QC-</td> + <td>Qualcomm reference number</td> + </tr> + <tr> + <td>M-</td> + <td>MediaTek reference number</td> + </tr> + <tr> + <td>N-</td> + <td>NVIDIA reference number</td> + </tr> + <tr> + <td>B-</td> + <td>Broadcom reference number</td> + </tr> +</table> +<p id="asterisk"> +<strong>4. What does a * next to the Android bug ID in the <em>References</em> +column mean?</strong> +</p> +<p> +Issues that are not publicly available have a * next to the Android bug ID in +the <em>References</em> column. The update for that issue is generally contained +in the latest binary drivers for Nexus devices available from the <a +href="https://developers.google.com/android/nexus/drivers">Google Developer +site</a>. +</p> +<p> +<strong>5. Why are security vulnerabilities split between this bulletin and the +Android Security Bulletins?</strong> +</p> +<p> +Security vulnerabilities that are documented in the Android Security Bulletins +are required in order to declare the latest security patch level on Android +devices. Additional security vulnerabilities, such as those documented in this +bulletin, are not required for declaring a security patch level. +</p> +<h2 id="versions">Versions</h2> +<table> + <col width="25%"> + <col width="25%"> + <col width="50%"> + <tr> + <th>Version</th> + <th>Date</th> + <th>Notes</th> + </tr> + <tr> + <td>1.0</td> + <td>December 4, 2017</td> + <td>Bulletin published.</td> + </tr> + <tr> + <td>1.1</td> + <td>December 5, 2017</td> + <td>Bulletin updated with link to firmware images and details on functional updates.</td> + </tr> +</table> + +</body></html> diff --git a/en/security/bulletin/pixel/index.html b/en/security/bulletin/pixel/index.html index 4b18dd6e..5479a4fa 100644 --- a/en/security/bulletin/pixel/index.html +++ b/en/security/bulletin/pixel/index.html @@ -59,16 +59,29 @@ AOSP 24–48 hours after the Pixel / Nexus bulletin is release <th>Security patch level</th> </tr> <tr> - <td><a href="/security/bulletin/pixel/2017-11-01.html">November 2017</a></td> + <td><a href="/security/bulletin/pixel/2017-12-01.html">December 2017</a></td> <td>Coming soon <!-- + <a href="/security/bulletin/pixel/2017-12-01.html">English</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=ja">日本語</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=ko">한국어</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=ru">ру́сский</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=zh-cn">中文 (中国)</a> / + <a href="/security/bulletin/pixel/2017-12-01.html?hl=zh-tw">中文 (台灣)</a> + --> + </td> + <td>December 4, 2017</td> + <td>2017-12-05</td> + </tr> + <tr> + <td><a href="/security/bulletin/pixel/2017-11-01.html">November 2017</a></td> + <td> <a href="/security/bulletin/pixel/2017-11-01.html">English</a> / <a href="/security/bulletin/pixel/2017-11-01.html?hl=ja">日本語</a> / <a href="/security/bulletin/pixel/2017-11-01.html?hl=ko">한국어</a> / <a href="/security/bulletin/pixel/2017-11-01.html?hl=ru">ру́сский</a> / <a href="/security/bulletin/pixel/2017-11-01.html?hl=zh-cn">中文 (中国)</a> / <a href="/security/bulletin/pixel/2017-11-01.html?hl=zh-tw">中文 (台灣)</a> - --> </td> <td>November 6, 2017</td> <td>2017-11-05</td> diff --git a/en/security/overview/acknowledgements.html b/en/security/overview/acknowledgements.html index a918dadd..cafa4e38 100644 --- a/en/security/overview/acknowledgements.html +++ b/en/security/overview/acknowledgements.html @@ -78,7 +78,8 @@ Barbara</td> Alibaba Mobile Security Group</td> <td>CVE-2017-0463, CVE-2017-0506, CVE-2017-0711, CVE-2017-0741, CVE-2017-0742, CVE-2017-0751, CVE-2017-0796, CVE-2017-0798, CVE-2017-0800, -CVE-2017-0827, CVE-2017-0843, CVE-2017-0864, CVE-2017-11000, CVE-2017-11059</td> +CVE-2017-0827, CVE-2017-0843, CVE-2017-0864, CVE-2017-9703, CVE-2017-9708, +CVE-2017-11000, CVE-2017-11059, CVE-2017-13170</td> </tr> <tr> <td>Ben Actis (<a href="https://twitter.com/ben_ra">@Ben_RA</a>)</td> @@ -91,11 +92,12 @@ CVE-2017-0827, CVE-2017-0843, CVE-2017-0864, CVE-2017-11000, CVE-2017-11059</td> <tr> <td>Billy Lau of Android Security</td> <td>CVE-2017-0335, CVE-2017-0336, CVE-2017-0338, CVE-2017-0460, -CVE-2017-8263, CVE-2017-9682</td> +CVE-2017-8263, CVE-2017-9682, CVE-2017-13162</td> </tr> <tr> <td>Bo Liu of <a href="http://www.ms509.com/">MS509Team</a></td> - <td>CVE-2017-0490, CVE-2017-0601, CVE-2017-0639, CVE-2017-0645, CVE-2017-0784</td> + <td>CVE-2017-0490, CVE-2017-0601, CVE-2017-0639, CVE-2017-0645, + CVE-2017-0784, CVE-2017-11042</td> </tr> <tr> <td>Chao Yang of Alibaba Mobile Security Group</td> @@ -107,15 +109,15 @@ CVE-2017-8263, CVE-2017-9682</td> CVE-2017-0766, CVE-2017-0794, CVE-2017-9681, CVE-2017-9684, CVE-2017-9693, CVE-2017-9694, CVE-2017-9715, CVE-2017-9717, CVE-2017-9720, CVE-2017-11001, CVE-2017-10999, CVE-2017-11057, -CVE-2017-11060, CVE-2017-11061, CVE-2017-11064</td> +CVE-2017-11060, CVE-2017-11061, CVE-2017-11064, CVE-2017-11089, CVE-2017-11090</td> </tr> <tr> <td>Chengming Yang of Alibaba Mobile Security Group</td> <td>CVE-2016-10280, CVE-2016-10281, CVE-2017-0463, CVE-2017-0506, CVE-2017-0565, CVE-2017-0711, CVE-2017-0741, CVE-2017-0742, CVE-2017-0751, CVE-2017-0796, CVE-2017-0798, CVE-2017-0800, CVE-2017-0827, CVE-2017-0843, -CVE-2017-0864, CVE-2017-9696, CVE-2017-9702, CVE-2017-11000, CVE-2017-11059, -CVE-2017-11089, CVE-2017-11090</td> +CVE-2017-0864, CVE-2017-9696, CVE-2017-9702, CVE-2017-9708, +CVE-2017-11000, CVE-2017-11059, CVE-2017-13170</td> </tr> <tr> <td>Chenxiong Qian of Georgia Tech</td> @@ -125,7 +127,7 @@ CVE-2017-11089, CVE-2017-11090</td> <td><a href="mailto:zc1991@mail.ustc.edu.cn">Chi Zhang</a> of <a href="https://c0reteam.org/">C0RE Team</a></td> <td>CVE-2017-0666, CVE-2017-0681, CVE-2017-0684, CVE-2017-0765, -CVE-2017-0836, CVE-2017-0857</td> +CVE-2017-0836, CVE-2017-0857, CVE-2017-0880, CVE-2017-13166</td> </tr> <tr> <td>Chiachih Wu (<a href="https://twitter.com/chiachih_wu">@chiachih_wu</a>) @@ -151,6 +153,10 @@ Palo Alto Networks</td> <td>CVE-2017-0807</td> </tr> <tr> + <td>Cusas (华为公司的cusas)</td> + <td>CVE-2017-0870</td> + </tr> + <tr> <td><a href="mailto:shaodacheng2016@gmail.com">Dacheng Shao</a> of <a href="http://c0reteam.org/">C0RE Team</a></td> <td>CVE-2017-0483, CVE-2017-0739, CVE-2017-0769, CVE-2017-0801</td> @@ -161,7 +167,8 @@ href="http://c0reteam.org/">C0RE Team</a></td> </tr> <tr> <td>Daniel Micay of Copperhead Security</td> - <td>CVE-2017-0397, CVE-2017-0405, CVE-2017-0410, CVE-2017-0826</td> + <td>CVE-2017-0397, CVE-2017-0405, CVE-2017-0410, CVE-2017-0826, + CVE-2017-13160</td> </tr> <tr> <td>Daxing Guo (<a href="https://twitter.com/freener0">@freener0</a>) of @@ -187,7 +194,8 @@ CVE-2017-0525, CVE-2017-8265</td> </tr> <tr> <td><a href="http://www.linkedin.com/in/dzima">Dzmitry Lukyanenka</a></td> - <td>CVE-2017-0414, CVE-2017-0703, CVE-2017-0808</td> + <td>CVE-2017-0414, CVE-2017-0703, CVE-2017-0808, CVE-2017-13157, + CVE-2017-13158, CVE-2017-13159</td> </tr> <tr> <td>Ecular Xu (徐健) of Trend Micro</td> @@ -205,7 +213,12 @@ CVE-2017-0525, CVE-2017-8265</td> <td>En He (<a href="http://twitter.com/heeeeen4x">@heeeeen4x</a>) of <a href="http://www.ms509.com/">MS509Team</a></td> <td>CVE-2017-0394, CVE-2017-0490, CVE-2017-0601, CVE-2017-0639, -CVE-2017-0645, CVE-2017-0784</td> +CVE-2017-0645, CVE-2017-0784, CVE-2017-11042</td> + </tr> + <tr> + <td>Eric Lafortune of + <a href="https://www.guardsquare.com/en">GuardSquare</a></td> + <td>CVE-2017-13156</td> </tr> <tr> <td>Ethan Yonker of <a href="https://twrp.me/">Team Win Recovery Project</a></td> @@ -234,8 +247,8 @@ CVE-2017-0432, CVE-2017-0434, CVE-2017-0446, CVE-2017-0447, CVE-2017-0500, CVE-2017-0501, CVE-2017-0502, CVE-2017-0503, CVE-2017-0509, CVE-2017-0524, CVE-2017-0529, CVE-2017-0536, CVE-2017-0566, CVE-2017-0573, CVE-2017-0581, CVE-2017-0616, CVE-2017-0617, CVE-2017-0624, CVE-2017-0649, CVE-2017-0744, -CVE-2017-6426, CVE-2017-8243, CVE-2017-8266, CVE-2017-8270, CVE-2017-9691, -CVE-2017-10997</td> +CVE-2017-6426, CVE-2017-8243, CVE-2017-8244, CVE-2017-8266, CVE-2017-8270, +CVE-2017-9691, CVE-2017-10997</td> </tr> <tr> <td>Godzheng (郑文选 <a @@ -263,7 +276,7 @@ CVE-2017-0567, CVE-2017-0574, CVE-2017-0575, CVE-2017-0577, CVE-2017-0580, CVE-2017-0584, CVE-2017-0692, CVE-2017-0694, CVE-2017-0727, CVE-2017-0748, CVE-2017-0771, CVE-2017-0774, CVE-2017-0775, CVE-2017-0786, CVE-2017-0787, CVE-2017-0788, CVE-2017-0789, CVE-2017-0790, CVE-2017-0791, CVE-2017-0792, -CVE-2017-0825, CVE-2017-6424</td> +CVE-2017-0825, CVE-2017-6424, CVE-2017-14904</td> </tr> <tr> <td>Guangdong Bai of Singapore Institute of Technology (SIT)</td> @@ -277,10 +290,14 @@ Illinois at Urbana-Champaign</a></td> <td>CVE-2017-0593</td> </tr> <tr> + <td>Guo Haoran of King Team</td> + <td>CVE-2017-13172</td> + </tr> + <tr> <td><a href="mailto:arnow117@gmail.com">Hanxiang Wen</a> of <a href="http://c0reteam.org/">C0RE Team</a></td> <td>CVE-2017-0400, CVE-2017-0418, CVE-2017-0479, CVE-2017-0480, -CVE-2017-0665, CVE-2017-0681, CVE-2017-0737</td> +CVE-2017-0665, CVE-2017-0681, CVE-2017-0737, CVE-2017-14904</td> </tr> <tr> <td>Hao Chen of Alpha Team, Qihoo 360 Technology Co. Ltd.</td> @@ -302,9 +319,12 @@ CVE-2017-0792, CVE-2017-0825, CVE-2017-6424</td> <td>CVE-2017-0481</td> </tr> <tr> - <td><a href="mailto:hlhan@bupt.edu.cn">Hongli Han</a> of <a -href="http://c0reteam.org/">C0RE Team</a></td> - <td>CVE-2017-0384, CVE-2017-0385, CVE-2017-0731, CVE-2017-0739</td> + <td><a href="mailto:hlhan@bupt.edu.cn">Hongli Han</a> + (<a href="https://twitter.com/HexB1n">@HexB1n</a>) of + <a href="http://c0reteam.org/">C0RE Team</a></td> + <td>CVE-2017-0384, CVE-2017-0385, CVE-2017-0731, CVE-2017-0739, + CVE-2017-13154, CVE-2017-6276 + </td> </tr> <tr> <td>hujianfei of Qihoo360 Qex Team</td> @@ -335,6 +355,12 @@ href="http://c0reteam.org/">C0RE Team</a></td> <td>CVE-2017-0422</td> </tr> <tr> + <td>Jeremy Huang + (<a href="https://twitter.com/bittorrent3389">@bittorrent3389</a>) + of King Team</td> + <td>CVE-2017-13172</td> + </tr> + <tr> <td>Jianjun Dai (<a href="https://twitter.com/Jioun_dai">@Jioun_dai</a>) of <a href="https://skyeye.360safe.com/">Qihoo 360 Skyeye Labs</a></td> <td>CVE-2017-0478, CVE-2017-0541, CVE-2017-0559</td> @@ -346,7 +372,7 @@ Qihoo 360</td> <td>CVE-2016-5346, CVE-2016-8416, CVE-2016-8475, CVE-2016-8478, CVE-2017-0445, CVE-2017-0458, CVE-2017-0459, CVE-2017-0518, CVE-2017-0519, CVE-2017-0533, CVE-2017-0534, CVE-2017-0862, CVE-2017-6425, CVE-2017-8233, -CVE-2017-8261, CVE-2017-8268</td> +CVE-2017-8261, CVE-2017-8268, CVE-2017-9718, CVE-2017-1000380</td> </tr> <tr> <td>Joey Brand of Census Consulting Inc.</td> @@ -391,6 +417,10 @@ CVE-2017-11060, CVE-2017-11061, CVE-2017-11064, CVE-2017-11089, CVE-2017-11090</ <td>CVE-2017-0647</td> </tr> <tr> + <td><a href="https://microlab.red/">Lorenzo Nicolodi</a></td> + <td>CVE-2017-13165</td> + </tr> + <tr> <td><a href="mailto:zlbzlb815@163.com">Lubo Zhang</a> of <a href="http://c0reteam.org/">C0RE Team</a></td> <td>CVE-2016-8479, CVE-2017-0564, CVE-2017-7368</td> @@ -421,7 +451,7 @@ href="http://c0reteam.org/">C0RE Team</a></td> </tr> <tr> <td><a href="https://github.com/michalbednarski">Michal Bednarski</a></td> - <td>CVE-2017-0598, CVE-2017-0806</td> + <td>CVE-2017-0598, CVE-2017-0806, CVE-2017-0871</td> </tr> <tr> <td>Mike Anderson (<a href="https://twitter.com/manderbot">@manderbot</a>) of @@ -437,7 +467,9 @@ CVE-2017-0450, CVE-2017-0479, CVE-2017-0480, CVE-2017-0483, CVE-2017-0665, CVE-2017-0666, CVE-2017-0681, CVE-2017-0684, CVE-2017-0731, CVE-2017-0737, CVE-2017-0739, CVE-2017-0765, CVE-2017-0768, CVE-2017-0769, CVE-2017-0779, CVE-2017-0801, CVE-2017-0812, CVE-2017-0815, CVE-2017-0816, CVE-2017-0836, -CVE-2017-0840, CVE-2017-0857</td> +CVE-2017-0837, CVE-2017-0840, CVE-2017-0857, CVE-2017-8080, CVE-2017-6276, +CVE-2017-13152, CVE-2017-13154, CVE-2017-13166, CVE-2017-13169, CVE-2017-14904 + </td> </tr> <tr> <td>Monk Avel</td> @@ -520,16 +552,17 @@ CVE-2017-0459, CVE-2017-0500, CVE-2017-0501, CVE-2017-0502, CVE-2017-0503, CVE-2017-0509, CVE-2017-0518, CVE-2017-0519, CVE-2017-0524, CVE-2017-0529, CVE-2017-0533, CVE-2017-0534, CVE-2017-0536, CVE-2017-0566, CVE-2017-0573, CVE-2017-0581, CVE-2017-0616, CVE-2017-0617, CVE-2017-0624, CVE-2017-0649, -CVE-2017-0744, CVE-2017-0862, CVE-2017-6425, CVE-2017-6426, CVE-2017-8233, -CVE-2017-8243, CVE-2017-8261, CVE-2017-8266, CVE-2017-8268, CVE-2017-8270, -CVE-2017-9691, CVE-2017-10997</td> +CVE-2017-0744, CVE-2017-0862, CVE-2017-6425, CVE-2017-6426, CVE-2017-8233, +CVE-2017-8243, CVE-2017-8244, CVE-2017-8261, CVE-2017-8266, CVE-2017-8268, +CVE-2017-8270, CVE-2017-9691, CVE-2017-9718, CVE-2017-10997, CVE-2017-1000380</td> </tr> <tr> <td>Qidan He (何淇丹) (<a href="https://twitter.com/flanker_hqd">@flanker_hqd</a>) of KeenLab, Tencent (腾讯科恩实验室)</td> <td>CVE-2017-0325, CVE-2017-0337, CVE-2017-0382, CVE-2017-0427, -CVE-2017-0476, CVE-2017-0544, CVE-2017-0861, CVE-2017-0866</td> +CVE-2017-0476, CVE-2017-0544, CVE-2017-0861, CVE-2017-0866, CVE-2017-13167, +CVE-2017-15868</td> </tr> <tr> <td>Qing Zhang of Qihoo 360</td> @@ -546,7 +579,8 @@ CVE-2017-0476, CVE-2017-0544, CVE-2017-0861, CVE-2017-0866</td> <tr> <td>Roee Hay (<a href="https://twitter.com/roeehay">@roeehay</a>) of Aleph Research, HCL Technologies</td> - <td>CVE-2016-10277, CVE-2017-0563, CVE-2017-0582, CVE-2017-0648, CVE-2017-0829</td> + <td>CVE-2016-10277, CVE-2017-0563, CVE-2017-0582, CVE-2017-0648, CVE-2017-0829, + CVE-2017-13174</td> </tr> <tr> <td>Roee Hay of IBM Security X-Force Research</td> @@ -564,14 +598,14 @@ Communications in DarkMatter</td> <tr> <td>salls (<a href="https://twitter.com/chris_salls">@chris_salls</a>) of Shellphish Grill Team, UC Santa Barbara</td> - <td>CVE-2017-0505</td> + <td>CVE-2017-0505, CVE-2017-13168</td> </tr> <tr> <td><a href="mailto:sbauer@plzdonthack.me">Scott Bauer</a> (<a href="https://twitter.com/ScottyBauer1">@ScottyBauer1</a>)</td> <td>CVE-2016-10274, CVE-2017-0339, CVE-2017-0405, CVE-2017-0504, CVE-2017-0516, CVE-2017-0521, CVE-2017-0562, CVE-2017-0576, CVE-2017-0705, -CVE-2017-8259, CVE-2017-8260, CVE-2017-9680, CVE-2017-11053</td> +CVE-2017-8259, CVE-2017-8260, CVE-2017-9680, CVE-2017-11053, CVE-2017-13160</td> </tr> <tr> <td>Sean Beaupre (<a @@ -709,7 +743,7 @@ href="http://c0reteam.org/">C0RE Team</a></td> </tr> <tr> <td>Xingyuan Lin of 360 Marvel Team</td> - <td>CVE-2017-0627</td> + <td>CVE-2017-0627, CVE-2017-13163</td> </tr> <tr> <td>Xuxian Jiang of <a href="http://c0reteam.org/">C0RE Team</a></td> @@ -726,6 +760,10 @@ CVE-2017-0739, CVE-2017-0765, CVE-2017-0768, CVE-2017-0769, CVE-2017-0779, CVE-2017-0801, CVE-2017-7368, CVE-2017-8264, CVE-2017-10661</td> </tr> <tr> + <td><a href="https://xtn-lab.com/">XTN</a></td> + <td>CVE-2017-13165</td> + </tr> + <tr> <td>Yan Zhou of Eagleye team, SCC, Huawei</td> <td>CVE-2017-9678</td> </tr> @@ -741,14 +779,18 @@ href="http://c0reteam.org/">C0RE Team</a></td> <tr> <td><a href="mailto:huahuaisadog@gmail.com">Yang Dai</a> of Vulpecker Team, Qihoo 360 Technology Co. Ltd</td> - <td>CVE-2017-0795, CVE-2017-0799, CVE-2017-0804, CVE-2017-0803</td> + <td>CVE-2017-0795, CVE-2017-0799, CVE-2017-0804, CVE-2017-0803, + CVE-2017-6262, CVE-2017-6263, CVE-2017-6280 + </td> </tr> <tr> <td>Yang Song of Alibaba Mobile Security Group</td> <td>CVE-2016-10280, CVE-2016-10281, CVE-2017-0463, CVE-2017-0506, CVE-2017-0565, CVE-2017-0711, CVE-2017-0741, CVE-2017-0742, CVE-2017-0751, CVE-2017-0796, CVE-2017-0798, CVE-2017-0800, CVE-2017-0827, CVE-2017-0842, -CVE-2017-0843, CVE-2017-0864, CVE-2017-11000, CVE-2017-11059</td> +CVE-2017-0843, CVE-2017-0864, CVE-2017-11000, CVE-2017-11059, CVE-2017-9703, +CVE-2017-9708, CVE-2017-13170 + </td> </tr> <tr> <td>Yanick Fratantonio (UC Santa Barbara, Shellphish Grill Team, EURECOM)</td> @@ -765,9 +807,14 @@ href="http://c0reteam.org/">C0RE Team</a></td> <td>CVE-2016-8431, CVE-2016-8432, CVE-2016-8435, CVE-2016-8480</td> </tr> <tr> + <td>Yaoguang Chen of Ant-financial Light-Year Security Lab (蚂蚁金服巴斯光年安全实验室)</td> + <td>CVE-2017-13171</td> + </tr> + <tr> <td>Yong Wang (王勇) (<a href="https://twitter.com/ThomasKing2014">@ThomasKing2014</a>) of Alibaba Inc.</td> - <td>CVE-2017-0404, CVE-2017-0588, CVE-2017-0842</td> + <td>CVE-2017-0404, CVE-2017-0588, CVE-2017-0842, CVE-2017-13164, CVE-2017-9708, + CVE-2017-13170 </td> </tr> <tr> <td>Yonggang Guo (<a href="https://twitter.com/guoygang">@guoygang</a>) of @@ -789,7 +836,8 @@ Lab</a></td> <td>Yu Pan of Vulpecker Team, Qihoo 360 Technology Co. Ltd</td> <td>CVE-2016-10282, CVE-2017-0517, CVE-2017-0532, CVE-2017-0615, CVE-2017-0618, CVE-2017-0625, CVE-2017-0795, CVE-2017-0799, CVE-2017-0804, -CVE-2017-0803</td> +CVE-2017-0803, CVE-2017-6262, CVE-2017-6263, CVE-2017-6280 + </td> </tr> <tr> <td><a href="mailto:computernik@gmail.com">Yuan-Tsung Lo</a> of <a @@ -800,7 +848,7 @@ CVE-2016-8481, CVE-2016-8482, CVE-2016-10291, CVE-2017-0326, CVE-2017-0333, CVE-2017-0428, CVE-2017-0429, CVE-2017-0435, CVE-2017-0436, CVE-2017-0444, CVE-2017-0448, CVE-2017-0526, CVE-2017-0527, CVE-2017-6264, CVE-2017-6274, CVE-2017-6275, CVE-2017-0651, CVE-2017-0709, CVE-2017-0824, CVE-2017-7368, -CVE-2017-8264, CVE-2017-10661</td> +CVE-2017-8264, CVE-2017-10661, CVE-2017-14903</td> </tr> <tr> <td>Yuebin Sun of <a href="http://xlab.tencent.com/">Tencent's Xuanwu Lab</a></td> @@ -854,7 +902,7 @@ CVE-2017-0691, CVE-2017-0700, CVE-2017-0714, CVE-2017-0718, CVE-2017-0719, CVE-2017-0720, CVE-2017-0722, CVE-2017-0725, CVE-2017-0745, CVE-2017-0760, CVE-2017-0761, CVE-2017-0764, CVE-2017-0776, CVE-2017-0777, CVE-2017-0778, CVE-2017-0813, CVE-2017-0814, CVE-2017-0820, CVE-2017-0823, CVE-2017-0850, -CVE-2017-0858</td> +CVE-2017-0858, CVE-2017-0879</td> </tr> <tr> <td>Zubin Mithra of Google</td> @@ -862,6 +910,14 @@ CVE-2017-0858</td> </tr> </table> +<h4 id="2017-additional-contributions">Additional contributions</h4> +<p>We would also like to acknowledge the contributions of the following +individuals to Android security:</p> + <ul> + <li>William Roberts + (<a href="mailto:william.c.roberts@intel.com">william.c.roberts@intel.com</a>)</li> + </ul> + <h2 id="2016">2016</h2> <div style="LINE-HEIGHT:25px;"> diff --git a/en/setup/build-numbers.html b/en/setup/build-numbers.html index 1236ec35..7325803d 100644 --- a/en/setup/build-numbers.html +++ b/en/setup/build-numbers.html @@ -208,6 +208,24 @@ site:</p> </thead> <tbody> <tr> + <td>OPM1.171019.011</td> + <td>android-8.1.0_r1</td> + <td>Oreo</td> + <td>Pixel 2 XL, Pixel 2, Pixel XL, Pixel, Pixel C, Nexus 6P, Nexus 5X</td> + </tr> + <tr> + <td>OPR5.170623.014</td> + <td>android-8.0.0_r36</td> + <td>Oreo</td> + <td>Nexus 6P</td> + </tr> + <tr> + <td>OPR4.170623.020</td> + <td>android-8.0.0_r35</td> + <td>Oreo</td> + <td>Nexus 5X</td> + </tr> + <tr> <td>OPD3.170816.023</td> <td>android-8.0.0_r34</td> <td>Oreo</td> @@ -370,6 +388,12 @@ site:</p> <td>Pixel C</td> </tr> <tr> + <td>N2G48H</td> + <td>android-7.1.2_r36</td> + <td>Nougat</td> + <td></td> + </tr> + <tr> <td>NZH54D</td> <td>android-7.1.2_r33</td> <td>Nougat</td> @@ -857,6 +881,12 @@ site:</p> <td>Pixel XL, Pixel</td> </tr> <tr> + <td>NBD92Q</td> + <td>android-7.0.0_r35</td> + <td>Nougat</td> + <td></td> + </tr> + <tr> <td>NBD92N</td> <td>android-7.0.0_r34</td> <td>Nougat</td> diff --git a/en/setup/site-updates.html b/en/setup/site-updates.html index 5b2356a8..d55ef9d9 100644 --- a/en/setup/site-updates.html +++ b/en/setup/site-updates.html @@ -22,11 +22,104 @@ --> -<p>This page describes significant revisions to source.android.com. Please see the <a +<p>This page describes significant revisions to source.android.com. Please see +the <a href="https://android.googlesource.com/platform/docs/source.android.com/+log/master?pretty=full&no-merges">Android Open Source Project (AOSP) docs/source.android.com log</a> for the complete list of changes to this site. +<h2 id="Dec-2017">December 2017</h2> + +<p>Android 8.1 has been released! See the entries below for the major platform +features introduced in this release.</p> + +<h3 id="aaudio">AAudio and MMAP</h3> + +<p>AAudio is an audio API that has enhancements to reduce latency when used in +conjunction with a HAL and driver that support MMAP. See <a +href="/devices/audio/aaudio">AAudio and MMAP</a> for documentation +describing the hardware abstraction layer (HAL) and driver changes needed to +support AAudio's MMAP feature in Android.</p> + +<h3 id="art-config">ART configuration changes</h3> + +<p>The <code>WITH_DEXPREOPT_BOOT_IMG_ONLY</code> makefile option was removed +from the Android runtime (ART) in Android 8.1 and replaced with the +<code>WITH_DEXPREOPT_BOOT_IMG_AND_SYSTEM_SERVER_ONLY</code> option that +pre-optimizes the system server jars, as well as the boot classpath. See <a +href="/devices/tech/dalvik/configure#uild_options">Configuring ART</a> for the +deprecation notice.</p> + +<h3 id="biometric-unlock">Biometric unlock security measurements</h3> + +<p>Android 8.1 introduces two new metrics associated with biometric unlocks +that are intended to help device manufacturers evaluate their security more +accurately: Imposter Accept Rate (IAR) and Spoof Accept Rate (SAR). See <a +href="/security/biometric/">Measuring Biometric Unlock Security</a> for +example attacks and test methodology.</p> + +<h3 id="boot-times">Boot time optimizations</h3> + +<p>Starting in Android 8.1, power saving setting for components like UFS and +CPU governor can be disabled to improve device boot times. See <a +href="/devices/tech/perf/boot-times#disable-power-saving">Optimizing Boot +Times</a> for the new <code>init.*.rc</code> settings.</p> + +<h3 id=“color-mgmt”>Color management</h3> + +<p>Android 8.1 adds support for color management that can be used to provide a +consistent experience across display technologies. Applications running on +Android 8.1 can access the full capabilities of a wide gamut display to get the +most out of a display device. See <a +href="/devices/tech/display/color-mgmt">Color Management</a> for +instructions on implementing, customizing, and testing this feature.</p> + +<h3 id="opengl-config">OpenGLRenderer configuration simplification</h3> + +<p>In Android 8.1 and later, only the <code>ro.zygote.disable_gl_preload +property</code> still applies to OpenGLRenderer configuration. All other +properties have been removed. See <a +href="/devices/graphics/renderer">OpenGLRenderer Configuration</a> for the +notice and previously supported properties.</p> + +<h3 id="retail-mode">Retail demo mode made easy</h3> + +<p>Through Device Policy Manager, Android 8.1 supports demonstrating device +functionality in retail stores via a demo-type user role. See <a +href="/devices/tech/display/retail-mode.html">Retail Demo Mode</a> for +implementation instructions.</p> + +<h3 id="textclassifier">TEXTCLASSIFIER</h3> + +<p>Android 8.1 introduces the TextClassfier API that uses machine learning +techniques to help developers classify text. +See <a href="/devices/tech/display/textclassifier.html">TEXTCLASSIFIER</a> for +implementation instructions.</p> + +<h3 id="timezone-rules">Time zone rules</h3> + +<p>Android 8.1 provides a new mechanism for device manufacturers (OEMs) to push +updated time zone rules data to devices without requiring a system update. This +mechanism enables users to receive timely updates and OEMs to test time zone +updates independently of system image updates. See <a +href="/devices/tech/config/timezone-rules">Time Zone Rules</a> for +instructions on applying these updates.</p> + +<h3 id="wifi-aware">Wi-Fi Aware</h3> + +<p>The Wi-Fi Aware feature in Android 8.1 enables supporting devices to connect +to one another directly over Wi-Fi without internet or cellular network access. +This feature allows easy sharing of high-throughput data among trusted devices +and apps that are otherwise off network. See <a +href="/devices/tech/connect/wifi-aware">Wi-Fi Aware</a> for examples, source +files, and links to additional documentation.</p> + +<h2 id="Nov-2017">November 2017</h2> + +<p>The <em>Source</em> section has been renamed to + <a href="/setup"><em>Setup</em></a>. Redirects are in place to ensure the old + URLs still work.</p> + <h2 id="Sept-2017">September 2017</h2> <p>This site has been released in China at <a @@ -37,7 +130,8 @@ list of changes to this site. <h2 id="August-2017">August 2017</h2> -<p>Android 8.0 has been released! This section describes the major new features in the Android 8.0 platform.</p> +<p>Android 8.0 has been released! This section describes the major new features +in the Android 8.0 platform.</p> <h3 id="architecture">Architecture</h3> |
