CDD: Clarifications to Wi-Fi Aware Management interface address
randomization requirements.

Minor clarification of the requirement and updating it to match
with the Wi-Fi Aware standard specification.

Change-Id: I5f6d792ba267e1b1fffd2da3bcc571d286597395
BUG:171723353
(cherry picked from commit 32644bda8d1e4464d4bb5d71800d40e51d7cb428)

CDD: Update reference to androidx-master-dev in CDD

Bug: 175313425
Change-Id: I0b0c104577b93cef0f8f2f2dcc9248972f8ea017
Test: N/A

Merge "CDD: Add requirement for Window Manager Jetpack for foldables." into rvc-dev

Merge "CDD: Requirements for IPV6 and Captive Portal." into rvc-dev

Merge "CDD: Haptics requirements for Handheld devices." into rvc-dev

Merge "CDD: Update requirements for Android biometrics" into rvc-dev

CDD: Requirements for IPV6 and Captive Portal.

Adding requirements for captive portal handling to make sure
that devices do not break interoperability. This also ensures
that developers do not need to implement workarounds for
captive portal networks, as the platform should be managing
such networks for them.

Also, IPV6 requirements have been tightened since the requirements
have existed for multiple desert releases and now the ecosystem
seems ready to provide IPV6 functionality to app developers on
cellular, Wi-Fi and ethernet.


Bug: 144673601
Bug: 147156245
Change-Id: I26bfe88963fe4854556daba72de539cb705ee7da

CDD: Haptics requirements for Handheld devices.

Update Haptics CDD requirements to provide informative guidelines
about Android Haptics to solve existing fragmentation and device
qualification problems on Handheld devices.

Bug: 143966455
Test: None
Change-Id: I650cb83eb0b461d74efa9b184fadce0f31edb881

CDD: Intents Classification and Clarification

Intents have been classified as application intents and
broadcast intents.
Application intents have been listed for each form factor.
Removed the terminology of Core intents and called it common
application intents to be more inline with the developer pages.

Also renamed section "3.2.3.5 default app settings" to
"conditional application intents" and moved in the conditional
application intents in that section.

The goal is to provide clarity to OEM's and developers on the
list of intents to expect an activity/handler.

Change-Id: I4416c2b06b7845581e701f8137e7d870d4749938
BUG: 148181180

CDD: Update requirements for Android biometrics

Update biometric section to clarify security requirements and enforce
consistent biometric implementations. This ensures that biometric
solutions are correctly implemented and surfaced via the biometrics APIs,
and that their security is measured and tested appropriately.

Bug: 145928315
Test: make -j

Change-Id: I633980e0f8993eb5814451e57601c216e03adaa8

Merge "CDD: Changes related to Scoped Storage" into rvc-dev

CDD: Changes related to Scoped Storage

* Dropped references to WRITE_EXTERNAL_STORAGE and
  WRITE_MEDIA_STORAGE permissions as the permission
  WRITE_EXTERNAL_STORAGE is a no-op for apps targeting Android R.
  Also the privileged permission WRITE_MEDA_STORAGE is deprecated
  in Android R.
* Scoped storage is enforced only by target SDK but the flag
  requestLegacyExternalStorage is not a way to opt out when targeting
  Android R.
* We no longer need text to emphasize how apps can access SD cards,
  this is enforced in the SDK
* Raw file path access now allowed as privacy rules are enforced 
  behind the scenes

BUG: 144375132
Change-Id: I292426ee55ecb395dcdbcc3f840d8c9bc5e7a6fc

CDD: Add requirement for Window Manager Jetpack for foldables.

Require providing implementation of `sidecar` or `extensions`
to be used by Window Manager Jetpack library and report
state and configuration of a foldable device to app developers.
This will help app developers to optimize their apps with a
single support library which will work across all devices.

Bug: 148290425
Change-Id: I9c3a0cf49d49367984b740b07b2ab24c6e75f385

Merge "CDD: Clarify faketouch requirements for multi-displays" into rvc-dev

Merge "CDD: Change for camera intent handling" into rvc-dev

CDD: Clarify faketouch requirements for multi-displays

- Moved 7.2.5/C-1-7 to under 7.2.4 as TOUCHSCREEN_NOTOUCH is that
 it *only* supports fake touch and not any of the
 android.hardware.touch.* features (e.g. a normal
 desktop computer without a touchscreen attached).
- Clarified a case for multi-display devices, that may have different
touch implementations per display.

Change-Id: Id125d3b829e6c9b55cce3a64cbe8409f83820228
bug:128322943

CDD: Sensors updates for timestamps and more

Change summary:
 - Timestamp synchronization is now mandatory with tightened guidance
 - Make +/- 16g accel guidance in hifi_sensors strongly recommended
 - Correct misleading wording in gyroscope and thermometer sections

Bug: 145023264
Test: view formatted markdown
Change-Id: If62e8a931d76f04f147c6dc5aeeb5ee1afb5968e

CDD: Update various requirements relating to sensors

Updated sensor requirements for Android 11 relating to:
- Magnetometer, accelerometer, and gyroscope placement in order to
  improve the ability to detect orientation of device.
- Requiring non-zero resolution for all sensors to mitigate
  privacy attacks.
- Recommend uncalibrated magnetometer be implemented when a
  magnetometer is present on a device
- Hinge angle sensors to reduce developer fragmentation when
  using hinge sensor API's.


Bug: 148824514
Test: View in go/MarkEd
Change-Id: I6f681e515f64ee1fb6e48a31af42a15328528bc3

Merge "CDD: Relax/Clarify Rounded Corner Req." into rvc-dev

Merge "CDD: Camera: Disallow facial appearance alteration" into rvc-dev

CDD: Camera: Disallow facial appearance alteration

Altering facial appearance by default is problematic in many ways.
Disallow it in the images provided by the Android Camera APIs.

Test: None
Bug: 145841721
Change-Id: I3e547bf3f71bd5decc785bbbb51e3e3b88dfcf88

Merge "CDD: Bluetooth Privacy Updates." into rvc-dev

Merge "CDD: Update Secure Element requirements" into rvc-dev

CDD: Change for camera intent handling

Specify that only preinstalled apps may handle the following
intents :
- MediaStore.ACTION_IMAGE_CAPTURE
- MediaStore.ACTION_IMAGE_CAPTURE_SECURE
- MediaStore.ACTION_VIDEO_CAPTURE

Apps requesting image or video capture via ACTION_IMAGE_CAPTURE,
ACTION_IMAGE_CAPTURE_SECURE, ACTION_VIDEO_CAPTURE and
ACTION_VIDEO_CAPTURE_SECURE can optionally pass in a URI via
an intent extra (EXTRA_OUTPUT) or by setting clip
data (Intent#setClipData). Images or videos captured using this
mechanism may contain location info their EXIF metadata depending
on the implementation of the app handling these intents
The intention behind this change is to prevent EXIF metadata
being leaked to apps that don’t hold the location permission.
Hence, restricting these intents in R to only pre-installed apps.

Test: none
Bug: 147582001
Change-Id: I0b9cbcf478fcba063e9d42c0bf64f782d9b7bc0a

CDD: Relax/Clarify Rounded Corner Req.

- The additional language to clarify the ambiguity in case the shape of a rounded corner is not perfect circle (e.g. oval).
- Rounded corners are utilized by most modern phones and end up cutting into app content (buttons, text, media, etc.). As the corners grow larger in size, they start completely hiding app content - we need to ensure that critical functions (e.g. ad or close buttons) are still visible to the user on screen by finding a balance between app UI and HW modernness.

Bug: 155688050
Change-Id: Id77295e37bc449de237aa30cfdfd02f47350d7c3

CDD: Update Secure Element requirements

Add requirements for OMAPI reader feature flags.
Applications could know if the device has a valid OMAPI reader
before applications are installed and executed.

Bug: 147706053
Bug: 146527692
Test: NA
Change-Id: I0feb26767a505f4141343638d8441c3ef04ef4bc

CDD: Explain Vulkan dEQP test requirements

Device implementations that support Vulkan must provide a feature
flag, android.software.vulkan.deqp.level, specifying the version of
the Vulkan dEQP tests that the device claims to pass.  This allows for
flexibility for device makers in the level of Vulkan dEQP tests that
are supported, and allows apps to query the level of support that is
provided.  This CDD change sets out the requirements related to this
new feature flag.

Bug: 148619801
Change-Id: I59aec5fed4bca33473f184a362d34a7b7cb450b3

CDD: Bluetooth Privacy Updates.

Tightened the Resolvable Private address requirement to protect
user privacy and avoid timing attacks.

BUG:148566806
Change-Id: I7ee26f8389821b1a299d0de977e20dc5a7b737fd

CDD: Carve out gyro 250dps range for Automotive am: 29db8c2624 am: 0c38e67bb0 am: 3299790889 am: 0e6259a0f6 am: f552dc3750

Bug: 147831815
Test: N/A
Change-Id: I2d40f0c688c35cd07e274f41db771cf694363dc9
(cherry picked from commit 0e5da195af73c4647fde15fba915f24a94b37b31)

Revise gamepad requirements

Our gamepad requirements are currently incorrect. For example, we
require all Android devices to handle gamepads, but in the requirements,
it seems that only the devices with "android.hardware.gamepad" do this.

Fix this by splitting a separate section for the gamepad shipped with
the Android device.

The purpose of the feature flag `android.hardware.gamepad` is to indicate
to app developers that a given device was shipped with
an Android-compatible controller in the box. The developer is then
guaranteed that the user will have a gamepad they can use for their
gamepad-only Android application. However, it is still expected that all
Android devices (phone, car, TV, etc.) should have gamepad support,
because a user may connect a supported gamepad to the device at any time.
It's not the expectation that the only devices with gamepad support are
the ones that claim the above feature flag.

Bug: 112265413
Bug: 145056738
Test: visually reviewed the page that opened at http://localhost:8090/
Change-Id: I715300c5c3178225be10f63bb6a493da035da833

Docs: Almost final Cleanup CL.

Bug: 140142603

Test: ./cdd_gen.sh --version <version-number> --branch <branch-name>
Change-Id: Ib0a8e55035eab94ff6ab28ad3c6aa6c7c1ae19d3

CDD: Remove Android Beam related requirements

- Android Beam has deprecated and thus removing the related
 requirements.

Test: None
Bug: 122551568
Bug: 111689901
Bug: 124001390
Change-Id: Ifbc34e464fdf4fdf8c08eced8930960d74d813d6
(cherry picked from commit efdadaef4db20edf215d1303c35d0e6b99142bd0)

CDD: Revise power and batching target for Game Rotation Vector

    - The power target was unreasonable as the individual sensors that
      are used to create a Game Rotation Vector use more power than
      the previous target.
    - No practical application for batching of the GRV has been
      determined, therefore, the requirement is being removed.
Bug: 123996403
Test: None

Change-Id: I3ab55f5beef03fe1044627197f52cdb0574cb349
(cherry picked from commit f64b6c0823cfded4cdf6a5836180f39cf60c0487)

Docs: Whitespace at EOF

Last line of file should end with a single newline.

Bug: 140034464
Test: N/A
Change-Id: Icdaaf61f25a0448fdf866fee4295b0ee15348812

Docs: Remove whitespace at end of line

Bug: 140034464
Test: N/A
Change-Id: Ice72bae4111a657da940a77e81aa8f22b6887bfd

Docs: Fix misspellings

Bug: 140034464
Test: N/A
Change-Id: If526c0b31459c7f368c623a0d0e916bfc3fd344f

Docs: Editorial fixes for the Android 10 release.

Master CL for editorial fixes.

Test: ./cdd_gen.sh --version <version-number> --branch <branch-name>

Bug:129537662
70503811
72342052
124383840
129711581
123095216
127703043
110493109

Change-Id: Ife1a549aa79979532465c64d6cd2054ffa2d94b9

CDD: Lockscreen and biometrics changes

- Introducing new biomatrics tier model, adding
 the requirements and constraints for each tier.
- Some editorial changes by reorganizing and folding some sections
- Transferred ag/6940471 on master to qt-branch

Bug: 126002559
Bug: 120995257 (7.3.10/C-2-5)
Bug: 124243324 (9.11.1/C-7-12)
Bug: 124403616 (7.3.10 additional background)
Bug: 123365828 (9.11.1/C-7-11)
Test: NA

Change-Id: Ib36d40935c77ec370a2494ddb1506b0a952fd525

CDD: Updating location and corresponding privacy requirements

- Some minor changes for reporting GNSS measurements
- Bumping up from Should to SR for 3-axis accelerometer
- Update privacy requirements related to the user's location to align
with the updated privacy policy

Bug: 124539379
Bug: 124405285
Bug: 124405354
Bug: 123593924
Bug: 124404671
Bug: 124404696
Test: N/A
Change-Id: I6278b6af8f1f3f00fe455d66fa051d3d7f5a2dc7

CDD: Digital Audio Ports

Added in requirements to be compatible with the headsets
and other audio accessories using USB-C connectors and
implementing (USB audio class) across the Android ecosystem.

Bug: 36515288
Test: make
Change-Id: I65bfe1049ab922db25d4748514c6e5fc5c53e09e

CDD: Camera: Clarify logical multi-camera requirements

- Ensure CDD language for logical multi-camera matches the key
  priorities for Android applications.

Test: None
Bug: 120859606
Change-Id: Iced34bfc0b90de8f2d2e6e9e709eb950fd921d48

CDD: Update aspect ratio requirement for devices with UI_MODE_TYPE_NORMAL

- Updating the requirement permissive for smaller or larger aspect ratio
 as long as the app's settings through the APIs are respected.
- Adding C-0-4 based on the newly introduced API (minAspectRatio).

Test: n/a
Bug: 121048097, 120129697, 124494228
Change-Id: I41716018b4039cb63e98001696687998ac961b02

CDD: Add requirement for Wi-Fi Easy Connect

Wi-Fi Easy Connect is a new standard from the Wi-Fi Alliance (WFA).
It is used to provision credentials on devices. The provisioning is
done over a secure channel using separate credentials obtained out-
of-band (e.g. QR code scan). The protocol is a replacement for WPS
(e.g. push-button) which has been determined to be insecure and was
deprecated in Android P.

Android Q supports 2 Easy Connect use-cases:
- Provision credentials on the device from an external source (e.g. AP)
- Provision credentials on IoT devices from the device itself.

Bug: 124063637
Test: manual test with go/markdownr
Change-Id: I0d6a899032b9d2a53e821d0ae70d07e43adfe592

CDD: Requirement for WiFi QoS.

This is to ensure that on average the latency of low-latency mode
is not worse than that of high performance mode.

Bug: 124108091
Test: manual test with go/markdownr

Change-Id: I75c4152a11fad9a67e1a75ebbe89cd2cd87325c8

CDD: Update multi-display requirements

- Update handheld requirements to accommodate with multi-display
devices.
- Clarify the requirements for multiple displays.
- Update resizeableActivity requirements to reflect the API change.

bug: 124445210
Change-Id: I0dd65f4dbbb698f733ec2114ff82dc7744dd1a38

Merge "CDD: Add requirements for audio signal integrity" into qt-dev

Merge "CDD: Offload Keep Alive messages" into qt-dev

CDD: Add requirements for audio signal integrity

as defined by absence of audio glitches.

This requirement improves application compatibility by ensuring a good
quality audio signal is available to apps.

Test: N/A
Bug: 124333844
Change-Id: I652105c9c52e1027e6d9072a25ef2eda2a03a785

CDD: Offload Keep Alive messages

Since the keepalive APIs are exported in ConnectivityManager,
corresponding CDD needs to be properly mentioned in
data-connectivity section.

Bug: 124124130
Test: ./cdd_gen.sh

Change-Id: Ibb8b4f9706f7f4306e78843f023b4a4790a38c56

CDD: Strongly recommend VK_KHR_driver_properties & VK_GOOGLE_display_timing

 -For Vulkan 1.0 drivers, make the VK_KHR_driver_properties and
  VK_GOOGLE_display_timing extensions STRONGLY RECOMMENDED.

 -VK_KHR_driver_properties was created by Vulkan IHVs and will be used
  to indicate which version of CTS the Vulkan driver passes (i.e. which
  bugs they've fixed).

 -VK_GOOGLE_display_timing is used by the SwappyVk part of the Games
  SDK; is implemented by the Android platform, and has been enabled
  since Oreo.

Test: Visual diff of the CDD text.
Bug: b/122480075
Change-Id: I23112a06f479dc1f29a328d1c526a1a549c56da1

CDD: Add EGL_ANDROID_GLES_layers

Added a requirement for EGL_ANDROID_GLES_layers, which is implemented
by the platform in libEGL.  The extension does not add any new entry
points or tokens, but its presence indicates that the Android platform
will detect and enable GLES layers in GraphicsEnvironment.java.

Documentation on GLES layers can be found here:
  frameworks/native/opengl/libs/EGL/GLES_layers.md

Bug: 124228367
Test: atest CtsGpuToolsHostTestCases
Change-Id: I2950265b720e97141c6d592ff545ad792fe0331c

CDD: Add requirement for EuiccManager API
Bug: 124392245
Test: None

- Clarify the EuiccManager requirements starting from Android Q
- Reduce API fragmentation and developer friction: mandate that if eSIM functionality is made available to 3p apps through any proprietary mechanism, then the AOSP EuiccManager API must also be implemented and made available.

Change-Id: I76b4104cee97c39b77b3b152248f1417e9d5ad0d

Docs: Clarify that gyroscope MUST have 3 axis

- Clarify CDD language that gyroscopes exposed to Android MUST have
3 axis. Expectation that gyroscopes MUST have 3 axis was already set here:
https://developer.android.com/guide/topics/sensors/sensors_motion.

Bug: b/112750848
Test: N/A
Change-Id: Iaf007c8724c418363eff5a529e8f06dd77125309

CDD: Devices with telephony MUST implement default InCallService.

If device implementations report android.hardware.telephony,
they MUST have an application that implements InCallService.

InCallService is a critical component for emergency calls and must be
implemented in every Android device that supports telephony.

Bug: 124533490
Test: N/A
Change-Id: Ic401b1cf74fc04b410e03be8414353d605bca7fe

CDD: Requirements for Hearing Aids Profile.

Device implementations that support Hearing Aids Profile with BLE must report support for it, so Heading Aids app developers can query to know if the platform has support for Hearing Aids Profile or not.

Bug: 124455749
Test: None
Change-Id: Ib1593efdba370a93e034b5040f2639aaa8713285

CDD: Camera: Mention camera2 CaptureRequest

- Much of the CDD still refers to the deprecated android.hardware.Camera
  API. While those requirements are still valid (since the old API still
  functions), it is important to mention the preferred camera2 API
  classes where appropriate.

Bug: 121389587
Test: None
Change-Id: Ie61eb7717e74a98c2aefd20d9e4acad270ce1500

Merge "CDD: Update screen aspect ratio requirements." into qt-dev

Merge "CDD: Upgrade USB audio class requirement for handheld/tablets." into qt-dev

CDD: Update screen aspect ratio requirements.

Bug: 127878899

Test: -
Change-Id: I3f6b762961b8e238cd7bb209e61fc0295e27c375

CDD: Upgrade USB audio class requirement for handheld/tablets.

This will enable apps to utilize high resolution USB audio on Handheld
and tablet devices.

Test: N/A
Bug: 64042820
Change-Id: Idb6273e9aac08f136eb719c421d90c087b570fd2

CDD: Add new density buckets.

Add new density buckets 140, 180, 200, 220.

Bug: 127714569
Test: N/A
Change-Id: I5fcf4c120e3221be77cdfb40141571533a00037c

CDD: Gesture nav requirements for insets & Back

    - New Insets API documentation is developer-facing and does not go
    into depth on how partners should be linking navigation functions to
    the insets communicated. Adding rules for this.
    - Back function is now available as a gesture from the left and
    right edges, which conflicts with app design/components. We're
    accounting for this with clear requirements for Back and other
    system conflicts (system panels).
    - As part of the back opt out APIs, we're enforcing a restriction
    that's only going to be mentioned in documentation and may be
    changed in the future (3-6 months) based on app compatibility.
    Calling this out as part of [C-6-2].

Bug: 124518180
Test: None (CDD change)
Change-Id: I3f8739b7559f5164d1a38ac8119b38f8cf11cf97

CDD: Camera: Location removal for image/video capture intents

- To improve user privacy, require that location metadata is
  not provided to requesting applications that lack the location
  permission, when they use the mediastore capture intents to
  request an image or video from the default camera app

Test: None
Bug: 124462769
Change-Id: I84bf0c5236660cb6986988fd004efd202fb26839

Docs: Clean up Automotive sensor requirements.

Clean up Automotive sensor requirements struture.

Bug: b/124318257
Test: N/A
Change-Id: Iaabb094b5e993230fb6949167dcb2ef34b8c21e1

CDD: Require TYPE_GYROSCOPE_UNCALIBRATED for Auto.

If Automotive device implementations include a gyroscope, they MUST
implement TYPE_GYROSCOPE_UNCALIBRATED sensor.

Clean up language for TYPE_GYROSCOPE_UNCALIBRATED in core requirements.

Bug: b/122917895
Test: N/A
Change-Id: I46a34ece0c70bc496d8306c95759882dbe6a11fa

Merge "Docs: Add link to measuring biometric unlock security" into qt-dev

Merge "CDD: Strongly recommend TYPE_GAME_ROTATION_VECTOR." into qt-dev

Merge "CDD: SR TYPE_ACCELEROMETER_UNCALIBRATED." into qt-dev

Merge "CDD: Revise sensor latency requirement for streaming" into qt-dev

Docs: Add link to measuring biometric unlock security

Test: N/A
Fixes: 124403616
Change-Id: I45cb719ffe15dd9a1c3456304951f1faea6b2000

Merge "CDD: Camera: Add custom SDK requirements" into qt-dev

CDD: Strongly recommend TYPE_GAME_ROTATION_VECTOR.

If device implementations include a 3-axis accelerometer and a gyroscope
sensor, they are STRONGLY RECOMMENDED to implement the
`TYPE_GAME_ROTATION_VECTOR` composite sensor.

This is a language clean up. Previous language had both STRONGLY
RECOMMENDED and SHOULD - Consolidated into a single STRONGLY
RECOMMENDED.

Bug: b/36478002
Test: N/A
Change-Id: I62a86bcdbd5fff074fd4345b92c144e2d865d2f9

Merge "CDD: Add necessary graphics extensions for supporting OS level GPU composition." into qt-dev

CDD: Add necessary graphics extensions for supporting OS level GPU composition.

The features are needed for their respective APIs in order for HWUI
(the hardware accelerated renderer for the View system) to function
without need of any modifications. Specifically, HWUI cannot import
content produced in other parts of the system without these extensions.

Bug: 78110728, 77289694
Test: spellcheck
Change-Id: I64a19563d92b3d8232b80710ddb27833f4ce0417

CDD: Camera: Add custom SDK requirements

- Require proprietary API exposed to third party apps based off Camera2.
- Require Camera 1/2 API parity.

Test: None
Bug: 127497237
Change-Id: I3fcd63735d6cad4df6843731200c6a4a2f5e56dd

CDD: Update shared storage sandboxing

- Isolate storage sandboxes to tighten privacy and security of shared
storage.

Bug: 121275794
Test: none
Change-Id: I018ba6a13c10d0adc41e4aac3c62f6407be38803

Merge "CDD: Update SR to MUST for `VK_ANDROID_external_memory_android_hardware_buffer` for Vulkan 1.1 devices with hardware support." into qt-dev

CDD: Add EGL_EXT_gl_colorspace_display_p3_passthrough

 -Added a new EGL extension to support Wide Color Gamut better and have
implemented inside the platform.

BUG: 122109156
Test: atest android.opengl.cts.OpenGlEsVersionTest#testRequiredEglExtensionsForWideColorDisplay
Change-Id: Iff348c35d6dbc537c4ec6a78e9cf40564ef950be

CDD: Update SR to MUST for `VK_ANDROID_external_memory_android_hardware_buffer`
for Vulkan 1.1 devices with hardware support.

Vulkan VK_ANDROID_external_memory_android_hardware_buffer (AHB) is important
because it allows graphic buffers allocated in GPU to flow around media codecs,
GL renderers and Vulkan renderers without any additional memory copies.

Bug: b/111695747
Bug: b/115676580
Test: VulkanFeaturesTest
Change-Id: Icdf35d8d7bd7cf25c6e4cc2ce876a30bfea57c35

CDD: SR TYPE_ACCELEROMETER_UNCALIBRATED.

If device implementations include a 3-axis accelerometer, they are
STRONGLY RECOMMENDED to implement and report
TYPE_ACCELEROMETER_UNCALIBRATED sensor.

Bug: b/124133530
Test: N/A
Change-Id: I1565932ca8c57c37329bb1610a082d062b120d60

CDD: Revise sensor latency requirement for streaming

- Clarify under what circumstances the maximum latency requirement
must be met. The previous version of the requirement was not
describing a streaming sensor request, which was incorrect. This
change modifies the requirement to only apply to streaming sensor
requests which is when the maximum latency is requested to be zero.

Bug: 123997763
Test: N/A
Change-Id: Ie2e52adbfac980cee06f80ff5feaf24587088e6b

CDD: Relax untested Vulkan requirements for VR.

These requirements are currently missing CTS tests, so vendors cannot
verify them in a systematic way. Downgrade from MUST to SR.

Bug: 119684099
Test: N/A
Change-Id: Icf94b6c022d33665cf5e602c702589cd8b4b76d1

Merge "CDD: Relax the radius requirement for rounded corners"

CDD: Errata for VR requirements.

Demote sensor direct channel, layered AHardwareBuffers,
GL_EXT_external_buffer and GL_EXT_EGL_image_array to 'strongly
recommended'. Some upgrading phones cannot meet these requirements.

Bug: 119322466
Test: N/A
Change-Id: Ic94161dbd55412eba1c75083b501032987e7cec4

CDD: Relax the radius requirement for rounded corners

- Updated the radius up to 38dp.


Bug: 114749730

modified:   7_hardware-compatibility/7_1_display-and-graphics.md

Change-Id: Id031916d02dd58222f511e1d2300108e54034018

Docs: Errata for Android 9 CDD.

- Fixed Section 9.10 by removing C-2-1 due to the introduction of C-0-2
- Fixed typos in other sections

Bug: 112010610

Test: ./cdd_gen.sh --version 9 --branch pie-dev
Change-Id: Ie4003beb20425a7fc83cf68ea23772aca389b85b

Merge "Docs: Resolving bug on 7.3 C-1-2" into pi-dev

Docs: Resolving bug on 7.3 C-1-2

Requirement 7.3 C-1-2 was breaking into a different bullet point due to
a bug in markdown. Breaking the line in a different place to resolve
that.

Test: N/A
Bug: 111654280
Change-Id: I065ff4a07f6c3a0749b2fc0f44dc504d9e53c04a

Docs: Correct the words for GPS and GNSS

- More consistency on the terminology update.

Bug: 110838439
Test: TH only, minor text changes
Change-Id: I21093ba2b14714dc6a6c22a34457b3243faf58df

Merge "CDD: Update CDD language for biometrics and lockscreen." into pi-dev

CDD: Update CDD language for biometrics and lockscreen.

This CL makes CDD changes that are aimed at providing more explicit
guidance on creating secure biometric based unlocks, and on
consolidating the CDD language for secure lockscreens to make the
authentication model consistent with our security bar.

More specifically, it changes the following things:
(1) A new section similar to "7.3.10 Fingerprint Sensors" that's more
generic and applicable to all biometric sensors. Should have mostly
the same constraints but slightly altered where necessary.
(2) Language that deals with match-on-chip solutions for biometrics.
(3) A new requirement in 9.11 that mandates keeping a minimum
Sleep timeout of at most 15 seconds.
(4) New requirements in "9.11.1 Secure Lock Screens" that:
  (a) Constrain what a primary authentication can be.
  (b) Adds information related to alternate biometric unlocks and
  adhering to the SAR/IAR bar that was introduced in the 8.1 CDD
  (c) Adds requirements around 'passive' biometric unlocks like Face
  when used to unlock keystore keys.
  (d) Clarifies some language around falling back to requiring primary
  auth every 72 hours for all non-primary modes of authentication
(5) Removes the API requirement to return false for both the KeyguardManager.isKeyguardSecure() and the KeyguardManager.isDeviceSecure() methods.

Bug: 73723272
Bug: 77656214
Bug: 111053551
Test: --
Change-Id: Iede9eba5ac79de56802cd830c3dc4e521f40e098

CDD: Allow rectangular display with rounded corners with certain conditions

- Unless UI_MODE_WATCH, the assumption of app developers has been that the
 rectangular logical display will be used, without any part of it being
 obscured (except for the notch). However since 2017 there are devices
 that have been launched with rounded-corners, this is to institutionalize
 the rules for such device implementations so that the rounded corners
 would not obstruct the touch target
 (https://material.io/design/layout/density.html#touch-click-targets)
- Ensure the consistent behavior for devices with UI normal mode.


Bug:68055709
Change-Id: I3b665eb010b1d0312b1d07a5f622bc2c66602411

Merge "CDD: Tighten SR to MUST for HOT GNSS TTFF to 5 sec to keep consistency with CTS" into pi-dev

Merge "CDD: Strengthen analog audio port requirements." into pi-dev

CDD: Strengthen analog audio port requirements.

Strengthened analog audio requirements for devices with 3.5 mm jack
so accessories work the same across everywhere.

Bug: 36478936
Test: N/A
Change-Id: Idfef08f81ce477ea4b1af243ee5d3a29010ef805

Merge "Docs: Fix broken link in Section 7.2.4" into pi-dev

Merge "CDD: Require the notification for an incoming call" into pi-dev

Merge "CDD: Add requirement for Open Mobile API" into pi-dev

CDD: Modifying VR requirements due to the deprecation of VR flag

- The change is to accommodate the deprecation of android.software.vr.mode

Bug: 71365436
Test: N/A
Change-Id: Id7185bbcc05ea0ae90088624792db8c74e2dfe64

CDD: Update HiFi sensors requirements for P

Provides additional ecosystem guidance targeted primarily at improving
VR and AR experiences.

Bug: 74577780
Test: n/a
Change-Id: Iac08461baf40e8e2eeab2b7b077dcf755669143d