From ddbca9044318d55bbd03e297540612de2e214fea Mon Sep 17 00:00:00 2001
From: Android Partner Docs and
tags o... by cqn
and
blo... by cqn
debuggerd
(includes new examples), stack
,
+ strace
, and Valgrind
tools.
+ buttons:
+ - label: June 5th, 2017
+ path: /devices/tech/debug/
- heading: Using Reference Boards
description: >
The former Selecting Devices page has been renamed
@@ -84,14 +92,6 @@ landing_page:
buttons:
- label: April 27th, 2017
path: /devices/tech/debug/eval_perf
- - heading: Camera Image Test Suite (ITS) Test
- description: >
- The Android Compatibility Test Suite (CTS) now supports ITS test
- automation via Camera ITS-in-a-box, an assembly for testing
- multiple devices at once.
- buttons:
- - label: April 20th, 2017
- path: /compatibility/cts/camera-its-box
- classname: devsite-landing-row-100 tf-row-centered
items:
- buttons:
diff --git a/en/compatibility/5.1/android-5.1-cdd.html b/en/compatibility/5.1/android-5.1-cdd.html
index 3fcff269..77448964 100644
--- a/en/compatibility/5.1/android-5.1-cdd.html
+++ b/en/compatibility/5.1/android-5.1-cdd.html
@@ -2096,18 +2096,20 @@ devices only when supported by hardware.
2 STRONGLY RECOMMENDED for Android Television device implementations when supported by hardware.
-Android device implementations, when supporting H.265 codec as described in section 5.1.3, MUST support the Main Profile Level 3 Main tier and the following SD video -decoding profiles and SHOULD support the HD decoding profiles. Android -Television devices MUST support the Main Profile Level 4.1 Main tier and the HD -1080p decoding profile and SHOULD support Main10 Level 5 Main Tier profile and -the UHD decoding profile.
+Android device implementations, when supporting H.265 codec as described in +section 5.1.3, MUST support the Main Profile Level 3 Main tier +and the following SD video decoding profiles and SHOULD support the HD decoding profiles. Android +Television devices SHOULD support Main10 Level 5 Main Tier profile and the UHD decoding profile. +Android Television devices are STRONGLY RECOMMENDED to support the HD 1080p decoding profile. +If the HD 1080p decoding profile is supported, it MUST support the Main Profile Level +4.1 Main tier
SD (Low quality) | SD (High quality) | HD 720p 1 - | HD 1080p 1 + | HD 1080p 2 | UHD 2 | ||
---|---|---|---|---|---|---|---|
SD (Low quality) | SD (High quality) | HD 720p1 | -HD 1080p1 | +HD 1080p2 | UHD2 | |
---|---|---|---|---|---|---|
Key mappings should be declared within a HID application +collection. For accessories without a microphone, use Headphone (Usage +Page: Consumer (0x0C), Usage: Headphone (0x05)). For accesories with a +microphone, use Headset (Usage Page: Telephony (0x0B), Usage: Headset (0x05)).
+Accessory manufacturers must follow the requirements for USB connectors diff --git a/en/devices/accessories/stylus.html b/en/devices/accessories/stylus.html index d2c2b79f..da739f9a 100644 --- a/en/devices/accessories/stylus.html +++ b/en/devices/accessories/stylus.html @@ -52,7 +52,7 @@ Bluetooth Low Energy (BTLE), or USB.
+UsagePage(Digitizer) Usage(Pen) Collection(Application) @@ -110,7 +110,7 @@ unsigned char HID_DESC[] = { 0xC0, // End Collection 0xC0, // End Collection } -+
The Android 6.0 platform automatically handles pairing and event correlation, diff --git a/en/devices/audio/implement-policy.html b/en/devices/audio/implement-policy.html index 16cd0820..a6ccf0e9 100644 --- a/en/devices/audio/implement-policy.html +++ b/en/devices/audio/implement-policy.html @@ -75,10 +75,9 @@ shows many of these features in use.
/system/etc
. To view a simple audio policy configuration in the new
XML file format, view the example below.
-<xi:include href="default_volume_tables.xml"/> </audioPolicyConfiguration> -
The top level structure contains modules that correspond to each audio HAL hardware module, where each module has a list of mix ports, device ports, and @@ -160,7 +158,7 @@ overwritten.
+ +The XML Inclusions (XInclude) method can be used to include audio policy @@ -391,7 +389,7 @@ product. The following example from a Galaxy Nexus shows a dynamic channel mask, which means the audio policy manager queries the actual channel masks supported by the HDMI sink after connection.
-+audio_hw_modules { primary { outputs { diff --git a/en/devices/audio/implement-pre-processing.html b/en/devices/audio/implement-pre-processing.html index e42dfc1c..adbf156f 100644 --- a/en/devices/audio/implement-pre-processing.html +++ b/en/devices/audio/implement-pre-processing.html @@ -83,7 +83,7 @@ audio HAL implementation's default behavior. theAudioSource
configuration in this manner, the framework will automatically request from the audio HAL the use of those effects. -+pre_processing { voice_communication { aec {} @@ -93,7 +93,7 @@ pre_processing { agc {} } } -+Source tuning
diff --git a/en/devices/audio/implement-shared-library.html b/en/devices/audio/implement-shared-library.html index 0c999c81..9f687079 100644 --- a/en/devices/audio/implement-shared-library.html +++ b/en/devices/audio/implement-shared-library.html @@ -34,7 +34,7 @@ directory to contain your library's source files.
Android.mk
file to build the shared library. Ensure
the Makefile contains the following line:
+LOCAL_MODULE := audio.primary.<device>
@@ -46,7 +46,8 @@ hardware located on the device. The module namesaudio.usb.<device>
are also available for Bluetooth and USB audio interfaces. Here is an example of anAndroid.mk
from the Galaxy Nexus audio hardware: -+ +LOCAL_PATH := $(call my-dir) include $(CLEAR_VARS) @@ -62,29 +63,29 @@ LOCAL_SHARED_LIBRARIES := liblog libcutils libtinyalsa libaudioutils libdl LOCAL_MODULE_TAGS := optional include $(BUILD_SHARED_LIBRARY) -+
device/<company>/<device>/device.mk
Makefile:
-+PRODUCT_COPY_FILES := ... PRODUCT_COPY_FILES += \ frameworks/native/data/etc/android.hardware.audio.low_latency.xml:system/etc/permissions/android.hardware.audio.low_latency.xml \ -+
system/etc/
directory in your product's
device/<company>/<device>/device.mk
Makefile.
For example:
-+PRODUCT_COPY_FILES += \ device/samsung/tuna/audio/audio_policy.conf:system/etc/audio_policy.conf -+
device/<company>/<device>/device.mk
Makefile.
For example, the Galaxy Nexus requires the primary and Bluetooth audio HAL
modules:
-+PRODUCT_PACKAGES += \ audio.primary.tuna \ audio.a2dp.default diff --git a/en/devices/audio/latency_design.html b/en/devices/audio/latency_design.html index f777c8ab..59ab47e0 100644 --- a/en/devices/audio/latency_design.html +++ b/en/devices/audio/latency_design.html @@ -43,7 +43,10 @@ The client can optionally set bitAUDIO_OUTPUT_FLAG_FAST
in the
hw_module_t
struct along with other camera-specific function pointers:
-+typedef struct camera_module { hw_module_t common; int (*get_number_of_cameras)(void); @@ -137,7 +137,8 @@ typedef struct camera_module {When you implement a HAL and create the module struct, you must name it
-HAL_MODULE_INFO_SYM
. For instance, here is an example from the Nexus 9 audio HAL:+ +struct audio_module HAL_MODULE_INFO_SYM = { .common = { .tag = HARDWARE_MODULE_TAG, @@ -159,7 +160,7 @@ struct audio_module HAL_MODULE_INFO_SYM = {audio_hw_device_t
struct type contains function pointers to audio device operations: -+struct audio_hw_device { struct hw_device_t common; diff --git a/en/devices/tech/admin/multi-user.html b/en/devices/tech/admin/multi-user.html index 11a63df9..cc187660 100644 --- a/en/devices/tech/admin/multi-user.html +++ b/en/devices/tech/admin/multi-user.html @@ -91,7 +91,7 @@ for on-call duty. shared by the primary user and the corp profile.
AddressSanitizer (ASan) is a fast compiler-based tool for detecting memory bugs in native code. It is comparable to Valgrind (Memcheck tool), but, unlike it, ASan:
diff --git a/en/security/authentication/gatekeeper.html b/en/security/authentication/gatekeeper.html index 94661684..692212c5 100644 --- a/en/security/authentication/gatekeeper.html +++ b/en/security/authentication/gatekeeper.html @@ -128,7 +128,7 @@ in GateKeeper. only the addition of device-specific routines to be complete. To implement a TEE Gatekeeper with device-specific code for your TEE, please refer to the functions and comments in the following file: -+system/gatekeeper/include/gatekeeper/gatekeeper.hdiff --git a/en/security/bulletin/2017-06-01.html b/en/security/bulletin/2017-06-01.html index 8c3f8faf..02a2578a 100644 --- a/en/security/bulletin/2017-06-01.html +++ b/en/security/bulletin/2017-06-01.html @@ -20,7 +20,7 @@ See the License for the specific language governing permissions and limitations under the License. --> -Published June 5, 2017
+Published June 5, 2017 | Updated June 7, 2017
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of June 05, 2017 or later @@ -31,8 +31,8 @@ level.
Partners were notified of the issues described in the bulletin at least a month ago. 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.
+Open Source Project (AOSP) repository and linked from this bulletin. This +bulletin also includes links to patches outside of AOSP.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 @@ -132,21 +132,21 @@ to access data outside of its permission levels.