Merge "CDD: Remove physical display size requirement from VR High Performance." into nougat-dev

CDD: Relax CDD section 7.2.3 visibility requirement for nav functions

- This update is only to relax the visibility of the nav buttons but
not to remove the nav functions.
- When nav bars are invisible, require to provide clear guidance
for the user.

Bug: 64997502
Change-Id: I8b7b72a546e364d150da272ce247e9e1896e7317

CDD: Remove physical display size requirement from VR High Performance.

Bug:67383027
Test:N/A
Change-Id: I59bb1ce24537746d4c2951ccc7b4214f56927023

Merge "CDD: Allow display density to change, but require a fixed value for DENSITY_DEVICE_STABLE." into nougat-dev

CDD: Allow display density to change, but require a fixed value
for DENSITY_DEVICE_STABLE.

While the Android framework can scale the resources across different
density buckets now, the app distribution service that is preinstalled
might benefit from knowing the device's native density to filter and
allow downloads of the proper apks.

Bug: 27669029
Change-Id: I3ef5cd319c420b21c5a8cd85cc31dfa6ef3d4e66

CDD: Update Remote Control Req for Android
Television devices that support an assistant.

Bug: 62236250
Change-Id: Ie9b29f9873087d779bea4e01597c40e7ff7ef933

Merge "CDD: Updated section related to screen aspect ratio." into nougat-dev

CDD: Updated section related to screen aspect ratio.

Bug: 27694834
Change-Id: Idd6172e2ecf3cb5006200def4b30cce8b3d9b187

CDD: Clarify the charging specs to refer when a USB type C port.

Bug: 24936153
Change-Id: I56c85377f27e657335108383aabfb3b8e0d61718

CDD: Relax VR high performance requirement related to exclusive cores.

Some device implementation have been proven to work better without
using exclusive cores but only by utilizing SCHED_FIFO properly.

Bug:34973979
Change-Id: I99358bc41d6809ac30b85d168239be7b34e95774

CDD: Hi-Fi sensors, gyroscope noise density typo fix

Updated CDD section 7.3.9 to correctly state 0.007 °/s/√Hz,
instead of 0.07 °/s/√Hz

Bug: 34094339

Change-Id: Ie9bd52b20d46574ad51c441daa0b1f104a74d489

CDD: Clarify that the AOSP implementation of TEE is a preferred reference
Section: 7.3.10. Fingerprint Sensor

The following requirement, has occassionaly been read that the use of
the AOSP implementation of the TEE is mandated.

"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) using the TEE as implemented in the
Android Open Source project"

Clarifed that there is an implementation of the TEE in the AOSP that
meets the requirement, and not that it is the only allowed
implementation.

Bug: 25121419
Change-Id: I19bf5535b7a532e52975fe99fceab5706be9f74b

Docs: Final cleanup for CDD source.

   - Fix rowspan in table in section 2.1.
   - Put markdown links on a single line.
   - Escape parentheses in URLs.
   - Fix some internal links with dashes instead of underscores.
   - Replace tabs with spaces.
   - Other misc. cleanup.

Bug: 32070486
Change-Id: Ie44202b5a0bfe7133505880a0a9c74f08a9bac1f

CDD: Fix a typo for HIGH FI sensor requirements (gyro)

For Gyro --

Change-Id: I650a892e9b99dbb48c1396ed88e9f190ac928af7
From: MUST have a maximum measurement frequency of 200 Hz or higher.
To: MUST have a maximum measurement frequency of 400 Hz or higher.

Merge "CDD: Bump minimum memory requirements" into nyc-dev

CDD: Bump minimum memory requirements

Bug: 30739309
Change-Id: I6c6d93d9e98212c18606423f94b11f9e96ec1e77

CDD: Require Type-C devices with host/peripheral mode to implement
     Dual Role Port properly
     
     This requirement will help not break 3rd-party apps that interact
     with USB peripherals. If an Android phone uses some non-USB
     Type-C compliant method of configuring as host, there is a
     chance that plugging in an USB Type-C compliant device
     into the non-compliant phone will result in a poor user
     experience and hurt the experience designed by the
     3rd-party apps that depend on the USB device.

Bug: 29661367

Change-Id: I957834aa419b1521acd5471eecf7576c31c0ba04

CDD: Align WiFi requirement for TV with 7.4.2

Bug: 29640911
Change-Id: I4315259b110722fc9c884f1edc87561b971b8862

Docs: Replace ":" with "."

Bug: 32070486
Change-Id: Iaf8cdac7b6a71d819cf0c9dc20e0092c6439c6a7

Docs: Unit fixes and formatting.

Bug: 32070486
Change-Id: I8c8a6bfbfc0cbb9dd8e118de97ecd98593d3bb03

Docs: Fix heading levels.

Bug: 32070486

Change-Id: I452d828c0d04a1a61b280017ab416c56d545052c

Merge "CDD: MTP support on USB host mode" into nyc-dev

Merge "CDD: Number Blocking" into nyc-dev

CDD: Number Blocking

Android 7.0 (API level 24) adds platform support for blocking
unwanted calls and messages. Earlier this was being done on an
app level, versus the platform. This gives a more robust number
blocking experience to the end user.

Telephony device implementors must adapt the new platform based
number blocking.

BUG: 27421203
Change-Id: I7624bc792e9c5d5b499198a18dd6beebaa375185

CDD: MTP support on USB host mode

Bug: 27154362

Change-Id: Ic093ae88cf032bc5c5f8019008b979141c9a43f0

Merge "CDD: Long press on home should follow the user's setting for the assist app." into nyc-dev

CDD: Long press on home should follow the user's setting for the assist
app.

Bug: 28926809

Change-Id: I57f13fe4d9296a469ba39b21ed3e7176a90d02a2

Docs: Spell check

Change-Id: If9bf9affdf9d0ebc38f2a675e05ef620e03417ae

CDD: low power req only applies to Game Rotation Vector Sensor

Game Rotation Vector power should be capped. The power
of the pure rotation vector may be higher because of its
potential dependence on the magnetometer.

Bug: 31929779
Change-Id: I949b7c85ff6967e28dd8f66b3bb6f81aba7c2876

Merge "CDD: Data Saver" into nyc-dev

CDD: Data Saver

From Android 7.0 (API level 24), users can enable Data Saver on
a device-wide basis in order optimize their device's data usage, and
use less data.

The ConnectivityManager API has been extended for app developers
to interact with this new mode. It is important that the new APIs
and the data saver mode behavior is consistent across all devices.

Device implementers can ensure the feature works
as intended by running the following CTS test: 
com.android.cts.net.HostsideRestrictBackgroundNetworkTests

Bug: 27615168

Change-Id: I1e13953a45e80e5857343a120ae46697cae82853

Merge "CDD: Relax Wi-Fi requirements for Android Television devices due to      improvements in ethernet connection." into nyc-dev

CDD: Relax Wi-Fi requirements for Android Television devices due to
     improvements in ethernet connection.

Bug: 29640911

Change-Id: I57ca4193e875352ddde8b4f2cb5be31b1b0f5368

Merge "CDD: Strongly Recommend Screen Zoom" into nyc-dev

CDD: Strongly Recommend Screen Zoom

Screen zoom enables users to reconfigure the display size, thereby
improving device accessibility for users with low vision.

The modification of the display density might impact apps if not
implemented carefully and thus the requirement also spells out
the boundary conditions when implementing the feature.


Bug: 29831575

Change-Id: I444915594bbf27d79189d5fc9170bdccb50bdfb1

Merge "CDD: Add missing section on USB and added USB Type-C section." into nyc-dev

CDD: Add missing section on USB and added USB Type-C section.

Bug: 24136422
Bug: 27644658
Bug: 27661533

Change-Id: I6ea980fdd576aac918c2ed26be311a6239014a02

Docs: Remove line break for proper list formatting.

Change-Id: I3f26f23c2524c5d3efb4c695e88c89948953a33c

CDD: Change Android Auto screen size to 750x480 dp.

Change-Id: I1248026eba549bf55e3cc62a9207af2a27f256a0

Merge "CDD: High perf VR devices requires BT 4.2 and LE Data Length" into nyc-dev

Merge "CDD: Virtual Reality" into nyc-dev

CDD: High perf VR devices requires BT 4.2 and LE Data Length

High performance VR device implementations are expected to be
used in a full-immersive nature, which means there would be a
need to have controllers typically external to the device.
Bluetooth 4.2 and LE Data Length extensions would be the baseline
foundation to grow an interoperable ecosystem of such accessories
upon which apps can rely on.

Bug: 26671343

Change-Id: I60d72f5a0746057bb2b63a4afe81f5e843cd45e9

Merge "CDD: Pose Sensor Requirements" into nyc-dev

CDD: Pose Sensor Requirements

In Android 7.0 we added new sensor type SENSOR_TYPE_POSE_6DOF. 

Bug: 29010283

Change-Id: Ia6497708ceaf6c8da3d365180028dcee086e9352

CDD: Virtual Reality

Bug: 26671343

Change-Id: I8ba2b00d49a293747b359541f88058761a4c6d0b

CDD: Update app private storage requirements.

Bumping the generic requirement up from 1.5GB to 3GB since:

a. the size of apps being distributed are growing
b. the statistics on median usage of the data/ partition is now over
2GB across devices from various geographies
c. the change was already hinted since 2 years ago

Reducing television requirements from 5GB to 4GB, because the
adoptable storage feature introduced in Android 6.0 are widely
adopted by televisions and can be used to meet the need for larger
app private storage

Bug: 26744064
Bug: 30684041

Change-Id: Ia9721380191093163412ea942cbb50bf40a32b38

Merge "Docs: Fix wording." into nyc-dev

Merge "CDD: Chnage GPS/GNSS accuracy requirements to 20 meters" into nyc-dev

Docs: Fix wording.

Bug: 31372724
Change-Id: I8145f48e4e78ba0915cf2a200fa960395bb9f39d

Merge "CDD: Add native APIs and require memory req. for cameras." into nyc-dev

CDD: Require detection of three key ranges, strongly recommend fourth key range.

In order to support a more consistent behavior of the keys commonly used
on 3.5mm headsets across Android devices, Android 5.0 introduced a
recommended impedance range to detect the following four headset keys;

- KEYCODE_HEADSETHOOK ~ 70Ω
- KEYCODE_VOLUME_UP 210 ~ 290Ω
- KEYCODE_VOLUME_DOWN 360 ~ 680
- KEYCODE_VOICE_ASSIST 110 ~ 180Ω

In Android 7.0, we now REQUIRE that Android devices with a 3.5mm
four-conductor audio jack would at least map the the ranges defined for
the first three keys onto the same keycode events.

Some devices upgrading to Android 7.0 might not necessarily have the
hardware with sufficient resolution range to properly detect four ranges,
especially to distinguish between the two lower impedance ranges. Hence,
we do NOT REQUIRE the detection of the KEYCODE_VOICE_ASSIST yet.

Bug: 29619521

Change-Id: I6fc3407f176ade0ce1caf96ec7b21cb7618ef940

Merge "CDD: Relax and clarify near-ultrasound microphone requirements" into nyc-dev

Merge "CDD: Clarify external cameras MAY be connected through non-USB ports." into nyc-dev

CDD: Clarify external cameras MAY be connected through non-USB ports.

Previously the CDD requirements for external camera assumed the device
is connected with the external camera through the USB port.

As this does not have to be necessarily the case, the requirements are
rewritten to allow device implementations to introduce new mechanisms
to connect the external camera(s) with the device.

Bug: 27930643

Change-Id: I9094b6d038d9194531fc7ca083f478fbf0dfca27

CDD: Chnage GPS/GNSS accuracy requirements to 20 meters

Bug: 28621822
Change-Id: I2a966d93c36fc0d0582f6c43c7f07d06a420bedc

Merge "CDD: Specific Automotive Bluetooth profiles" into nyc-dev

CDD: Automotive sensors: update existing and new

Some sensors are physically separated from the Android Automotive
implementation by a vehicle network but still improve safe vehicle
operation when passed to Android. Examples include day-night,
mechanical wheel speed, and current gear.

Accelerometer clarifications and sensor coordinate system
defined for vehicles.

Change-Id: I341a9e1ffba42c72e53d90f7211a4a5b2e2f1ee3

Merge "CDD: Automotive specific sensors" into nyc-dev

CDD: Automotive specific sensors

Some sensors are physically separated from the Android Automotive
implementation by a vehicle network but still improve safe vehicle
operation when passed to Android. Examples include day-night,
mechanical wheel speed, and current gear.

Change-Id: Iac196ec1169dcd7c55d4dc48036638ff4bba231f

Merge "CDD: Minimum automotive screen size" into nyc-dev

Merge "Docs: Adding section 7.7 omitted in conversion." into nyc-dev

Docs: Adding section 7.7 omitted in conversion.

Change-Id: Ia6ecd693cc5e86f560f39456efd34ab5bee23b5c

CDD: Add native APIs and require memory req. for cameras.

Android 7.0 adds support to control the camera through the native
APIs through the camera2 native APIs and we enlist the camera2 library
in the standard library list.

We also make it a requirement to have memory of at least 3 times the
maximum camera resolution, which was previously recommendation only.
See test android.hardware.camera2.StillCaptureTest#testAllocateBitmap
for details.

Bug: 28091251

Change-Id: I4cc94f2289ad8e759955697aa521a7aeb9c2bb6e

Merge "CDD: Add requirements for when NFC Felica Host Card Emulation is on" into nyc-dev

CDD: Add requirements for when NFC Felica Host Card Emulation is on

Android 7.0 includes support for NFC Felica Host Card Emulation APIs.

The NFC Felica HCE feature itself is not mandatory, but the requirement
clarifies what is required when the device implementation want to
support NFC Felica host card emulation and make it available to
third-party apps.

Bug: 28795994
Bug: 28439266

Change-Id: Ib38f307fbead52913007e53a996e220076b68494

Merge "CDD: HiFi sensors now MUST have higher accel. measurement freq." into nyc-dev

CDD: HiFi sensors now MUST have higher accel. measurement freq.

The requirements for Hi-Fi sensors are bumped up.

Especially the measurement frequency of the accelerometer is now updated
to be at least capable to go up to 400Hz (instead of 200Hz).

Quality recommendations for the gyro and accellerometer are also added
along some minor format edits.

Bug: 27907905
Bug: 27908075
Bug: 27908031

Change-Id: I3019d5721b82bf730f01c3a20777bfb07e5a8775

CDD: Relax and clarify near-ultrasound microphone requirements

The microphone near-ultrasound requirement for SNR is relaxed from 80dB
to 50dB, but specified further in terms of the bandwidth, the way of
measurement, and finally the audio streams that it applies for.

Bug: 27665223

Change-Id: I405b2039f4a60c3d78b441f41d10075b107e50d5

Merge "CDD: Clarify that only Watches can consume the KEYCODE_BACK long press event." into nyc-dev

CDD: Clarify GPS requirements and the getGnssYearOfHardware test method

Clarify GPS requirements to assure minimal functionality of the
GPS/GNSS based location provider upon which app developers can work on.

Also getGnssYearoOfHardware API method is a new test API to get the
year of GNSS technology generation and requirements.

Bug: 28621822

Change-Id: Ic5ce8b3e4a4ad765584a1c5582a181c0489bdbbe

CDD: Clarify that only Watches can consume the KEYCODE_BACK long press event.

Android 7.0 introduces "config_longPressOnBackBehavior" as a device
configuration and this can only be overridden for Android Watches.

Bug: 27948532

Change-Id: If74c9499b31e4426204db59a65d62c6f269a9203

CDD: Minimum automotive screen size

* Physical screens in cars are 6 inches or larger
  to ensure minimum physical tap target size.
* Screen size should be a minimal size based on experience
  building user interfaces that have font size and UI
  elements that are safer for driving.

Change-Id: I11b51bf4edc7ec677d2c990fcb530813e79716a5

CDD: Specific Automotive Bluetooth profiles

Because vehicles often act as a host for MAP and media playback,
and an audio gateway for phone calls, a subset of Bluetooth
profiles are required.

Change-Id: I351d311da4381ba5677b5cd0955fed71b34d53e4

CDD: Add requirements for new OpenGL ES 3.2 support

Android 7.0 introduces the support for OpenGL ES 3.2.

Bug: 27800074

Change-Id: I1b3f3ffba2ac3a9e4557fa66a233d5696ca32e0d

Docs: Add CDD docs and the build script, and test examples

Bug: 25199595
This is based on the amended final CDD for M, hosted as commit
1846a9622485855d572705a7972116caf0be3669 on the AOSP master branch.

Change-Id: Ic3bd96cd652f7d7b13def03a4ca1f04645c34255