CDD: Moving camera intents STILL_IMAGE_CAMERA, STILL_IMAGE_CAMERA_SECURE & VIDEO_CAMERA to HandHeld requirements.

The requirement are applicable to Handheld/Tablets only.

Change-Id: Ibfe97104dc29004237925e80936c4f4258e32404
BUG: 231313205

CDD: Correction to build parameters BASE_OS & SECURITY_PATCH.

Corrected, BASE_OS and SECURITY_PATCH are part of Build.VERSION
instead of the Build class.

Change-Id: I7d69dbdfab343cfbf65c7ad676f24e4eea9a98f3
BUG: 186475665

CDD: Clarification to Instant Apps requirements.

b/183149220
Test:  N/A

Change-Id: I811167d4d0d3efc19ae7d8497062ff6a82c9ef14

CDD: Clarify Quick Settings API requirement.

Bug: 179499659

Test: cdd-gen.sh script to build.
Change-Id: Ifa472937135488879bc4fc57f9bbc896ea177fdf

CDD: Remove language on app restriction reporting.

There is no event in the UsageStats API corresponding to app
restrictions and this is not met by AOSP.

Bug: 123961455

Test: cdd-gen.sh script to build.
Change-Id: Ie52d7ce8cb0b5b0208aba88b8d460c97a0475a35

Docs: Fix formatting on SBI link.

Bug: 184073020

Test: cdd-gen.sh script to build
Change-Id: I492ba0c35edea8076390f8620442dab0b951892f

CDD:Adding links to Android NDK SBIs

Bug: 184073020

Test: cdd-gen.sh script to build
Change-Id: I40c4fddd84505a552a585dc1caab956081959877

Merge "CDD: Typo fix in section 3.9.1." into android11-dev

Merge "CDD: Clarify Roboto font requirements." into android11-dev

CDD: Clarify Roboto font requirements.

Clarified the Roboto font language requirements and
setting up clear guidelines for partners to meet. The
earlier requirement was causing ambiguity.

Change-Id: If0d877a768a3a66ad9c119ce9d44015bd302b0f7
BUG: 170912345

CDD: Fixed the name of Tap & Pay to Contactless.

Corrected the CDD document to reflect the new name for
NFC payments from `Tap & Pay` to `Contactless`.

Change-Id: Ifd2ee874de95da6efe266880cfdbc77b5f1a7b3e
BUG: 171010325

CDD: Typo fix in section 3.9.1.

Fixed a typo in section 3.9.1.

Bug: 171049582
Change-Id: I0d7bde922d4e9f382bee8ca99cdd0a0e4a5789f5

Merge "CDD: Requirements for presentation of notifications" into rvc-dev

CDD: Requirements for presentation of notifications

Android 11 added in support for conversation notifications and
added in requirements for grouping/display of conversation
notification for a unified user experience.

Test: make
Fixes: 145622353
Change-Id: I133daed3222716197d82d3984432f2cdfb5c16ee

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

Merge "CDD: Intents visible to Instant Apps." into rvc-dev

CDD: Intents visible to Instant Apps.

An Android Instant App is a small version of your app
that runs without installation. Since Instant Apps cannot see
the other applications on the device and rely on pickers and
other system-defined components to do work, the request is
to expose certain intents and make them available to instant apps
i.e an instant application can launch this intent and there will
be a handler for it.

Bug: 147893121
Change-Id: Ied14e0e4753a3ddf2150b32387047b93ad9d23db

Merge "CDD: Add section for contacts local account" into rvc-dev

Merge "CDD: Handheld requirements for device controls." into rvc-dev

CDD: Add section for contacts local account

Standardize local account types in the ContactsProvider.

There is no standard way for applications to refer to local contacts on
Android. It is slightly different on devices from different
manufacturers. So applications  (e.g. contacts backup/restore or
device-to-device contact transfer applications) that want to operate on
local contacts on any Android device must understand the idiosyncrasies
of each manufacturer.

Test: N/A

Bug: 145120250
Change-Id: Ic4818bc7a630a5ec603338c0eafbfcb851ad0584

CDD: Handheld requirements for device controls.

Add definitions to support Device Controls. Device
Controls are an affordance within the Power Menu that allows users to
remotely control their home devices such as lights and thermostats,
as well as other IoT devices. SystemUI provides a default
implementation of this feature for AOSP.

The user experience for home control (IoT control) is fragmented
and not integrated across multiple vendor-supplied applications.
Adding in requirements to create a standard surface for the
individual controls provided by app developers to show on.

Bug: 145990227
Test: go/marked
Change-Id: Ic5cdb781683f3610f9600d40ea1f8fc568cb52ae

Merge "CDD: Update the wording on Android Extensions" into rvc-dev

Merge "CDD: Clarify Device Owner consent requirements" into rvc-dev

Merge "CDD: Update DisplayCutout requirements" into rvc-dev

Merge "CDD: Requirement for default material theme font." into rvc-dev

Merge "CDD: Clarify the condition for reqs under section 3.5.1 and 8.3 and  the timing of user notification for 3.5.1/C-1-5" into rvc-dev

CDD: Clarify the condition for reqs under section 3.5.1 and 8.3 and
 the timing of user notification for 3.5.1/C-1-5

- Updated 3.5.1/C-1-5 to specify the timing of user notification
for better user experience.
- Clarified the conditions for 3.5.1 and 8.3 that the former apply
 to proprietary app restrictions that are more restrictive than "rare"
 standby bucket.

Bug: 145312968

Change-Id: I5965e80b7d631da9ef4363a9a5dd090ba365b4cb

CDD: Clarify Device Owner consent requirements

Clarify device provisioning compatibility requirements for a fully managed device. This provisioning method is primarily used to provision a device that is owned by a company.

Bug: 64556174

CDD: Update the wording on Android Extensions

Added two requirements on the new extension version concept.

We're adding a concept of "extensions" of a given dessert release,
released independently of the dessert itself. Reporting a particular
extension version implies a set of APIs must be present, and passing
CTS.

Bug: 145614901
Test: ./cdd_gen.sh --version 11 --branch aosp-master
Change-Id: Iebc4ca61f85aef437ccfd6e9216f4230017922f8

CDD: Requirement for default material theme font.

The intent is to ensure that app developer's expectations are
consistent with the default (e.g. without explicit user consent)
on-device presentation of their apps, and the default sans-serif
font is a highly-visible aspect of this presentation.


Bug: 150033413
Change-Id: Ib434bbd28d27e513d3813a07aaaa5b1ff42ee9c2

Merge "CDD: Update managed profiles lockscreen CDD requirements" into rvc-dev

CDD: Update managed profiles lockscreen CDD requirements

Update CDD to allow managed profiles without lockscreen.
Android TV does not support lockscreens and requires managed profiles
for Unicorn (Kids) profiles.

Test: None
Bug: 152830725
Change-Id: I520ecee3638b8cc960162c5f2c4c4aee861ccf3a

CDD: Requirements for PIP window size

To respect the activity's minWidth and minHeight when accounting
for the minimal size for PIP.

Applications other than video-based ones may prefer a much more
condensed window when in PIP mode. Previously, the final size
of a PIP window was calculated by the system without the application
being involved.

Summary:
- Separate the requirement for TV from non-TV
- Respect the minimum dimension declared by application as the PIP
window size, if applicable

Bug: 144849584
Test: N/A
Change-Id: Ic6d4793475ed227eaa1b5b1e394dfa4dd2a87250

CDD: Update DisplayCutout requirements

Broaden display cutout definition to allow for waterfall displays.

Bug: 143907595
Test: n/a
Change-Id: I4f8bf0873621a6a9f259a850f2f1d3d7e692c15f

CDD: Change to Enable Notification Listener on the lowRam device

- The notification listener is supported on all RAM tiers,
not just normal.
- This is a change that reflects that
Notification Listener is enabled for low-ram flag
devices (it had earlier been disabled).

Bug: 151450994
Test: Manual test
Change-Id: Ibb3ce8f6fb950dc4103469ed1710da13a43d8d70

Docs: Almost final Cleanup CL.

Bug: 140142603

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

Docs: Prefer American spelling

per https://developers.google.com/style/spelling

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

Docs: Whitespace at EOF

Last line of file should end with a single newline.

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

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: 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

CDD: Update Media Center requirements.

This update is necessary for Android Auto and Automotive:
 * Remove C-1-1 as notifications are actually covered by
   https://source.android.com/compatibility/android-cdd#3_8_3_1_presentation_of_notifications
 * Clarify C-1-2 as nobody can display all the metadata that can be provided.
 * Change C-1-3 to display the app icon (icons convey branding better), and
   in more locations for improved content attribution
 * Remove the mention of a particular UI implementation in C-1-4, and
   mention safety regulations.


[For readability]

If device implementations include non voice based applications (the Apps)
that interact with third-party applications through MediaBrowser or
MediaSession, the Apps:
* [C-1-2] MUST clearly display icons obtained via getIconBitmap() or
  getIconUri() and titles obtained via getTitle() as described in
  MediaDescription. May shorten titles to comply with safety regulations
  (e.g. driver distraction).
* [C-1-3] MUST show the third-party application icon whenever displaying
  content provided by this application.
* [C-1-4] MUST allow the user to interact with the entire MediaBrowser
  hierarchy. MAY restrict the access to part of the hierarchy to comply
  with safety regulations (e.g. driver distraction), but MUST NOT give
  preferential treatment based on content or content provider.
* [C-1-5] MUST consider double tap of KEYCODE_HEADSETHOOK or
  KEYCODE_MEDIA_PLAY_PAUSE as KEYCODE_MEDIA_NEXT for
  MediaSession.Callback#onMediaButtonEvent.

Bug: 123357837
Test: N/A
Change-Id: Ibfaed0243cfefe4738333a019ece3447386f895a

CDD: Update requirements for app compatibility in Q.

- Update definition of non-SDK interfaces (previously hidden APIs) to
  reflect the name used in other docs. Update the definition of what
  they are based on AOSP changes in Q.
- Update definition of API classifications, as per code changes in Q.
- Add signed config requirement (new feature in Q), and remove the optional
  dynamic update since that is no longer needed.

Patched from http://ag/6933982

Bug: 122980592
Test: N/A
Change-Id: Ia74f196f8ecb228337cebe8977daa5492117551e

CDD: Restrict permitted BUILD.INCREMENTAL and TAGS

Restrictions to the permitted values of BUILD.INCREMENTAL and TAG
are needed to ensure that they do not contain characters that are
not permitted in the build fingerprint or could be confused with
field separators when parsing the build fingerprint.
Permitting arbitary replacement of invalid characters can lead to
ambiguity in the fingerprint.

BUG: 80051029

Change-Id: Ie562c9b6a9a5664e925e9e90453380a7f16c2578

CDD: Add InstantApps SystemUI requirements

- InstantApps launched as a framework provided feature
  in Android Oreo. These UI requirements were implemented
  in AOSP at the time, but never formalized in
  documentation. The product requires that these are met
  and a CTSVerifier CTS change has been added for these
  as well.

Bug: 125919647
Test: Verfied markdown using go/markdownr
Change-Id: Ie95cb539d6855d1ed4410502b2ac806ea3563427

CDD: Add requirement about multi-process WebView.

- Improve security and stability for third party apps
 that use WebView in the multi-process.

Bug: 32813129
Change-Id: Ifaac72a3b2b20e0c0f041bd54308cefa8df245e0

CDD: Add new density buckets.

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

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

Merge "CDD: Add requirement for libamidi.so" into qt-dev

Merge "CDD: Requirements on Myanmar/Zawgyi support" into qt-dev

CDD: Requirements on Myanmar/Zawgyi support

 -  Ensure the consistent Unicode support for Burmese upon the
    platform update on the language.

Bug: 120955413
Test: N/A
Change-Id: I0971b77334fa1daa213237921a1e23d9e74b0473

CDD: Add requirement for libamidi.so

- Aligning with the added support for midi library.

Test: N/A
Bug: 124249176
Change-Id: Ic15bac32af7fed12ff93cdedcfbafae36e7ceb03

CDD: Telecom Call Redirection

The intention of the CDD language proposed is to ensure that an OEM
supports the android.app.role.CALL_REDIRECTION role and the APIs
surrounding it. Because choosing an app to fill a role is not something
which can be tested easily using an automated CTS test, the CDD
language to enforce the availability of the role is appropriate.

Bug: 124124880
Test: Verified
Change-Id: I7b32d0b841f2d2b3ac94463e458d3376a52cc6a7

CDD: Relax requirements for WebView useragent.

Allow the "$(MODEL)" and "Build/$(BUILD)" tokens to be omitted from the
WebView useragent string, to match the current/future behaviour of
Chrome on Android. This is a minor improvement to privacy (reduces
fingerprinting) and security (removes information that may be useful for
targeting exploits).

Bug: 122453525
Change-Id: I8200e619e62a30f84b7c2ebf68f8fa0be47d95b8
(cherry picked from commit 9a8210988ede1f7ca1b76fbf90a3a0c44cf948b3)

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: Fixed language for section 3" into pi-dev

Merge "CDD: Requirement for Power Management features" into pi-dev

Docs: Fixed language for section 3

- 3.2.3.2: Excluded the Settings app that third party apps can override.
- 3.15 : Replacing "ephemeral" with "instant".

Bug:111602321
Change-Id: Idb99d9fd42a7a0b06273674c041dbad583158d62

Merge "CDD: Requirements for Heavyweight app mode" into pi-dev

CDD: Requirement for Power Management features

- Ensure the consistent behaviors of power management features across devices.
- Clarify the background restrictions so that apps aren't restricted when they shouldn't be.
- Ensure that the user affordance is provided so that the user has visibility into
what restrictions are enabled and can control the restriction.

Bug:70803569, 79491895
Change-Id: Ibf27cbbf6960521e5dc7c0c0de375f3a2ef86466

CDD: Requirements for Heavyweight app mode

Some apps like games have special needs for memory management, since they
tend to be very heavy on memory resources and unable to restore
to their last state (participate in Android’s state saving mechanism).
To preserve games in memory, Android P offers a heavyweight app mode that
will keep an app persistent in memory. There can be only one heavyweight
app designated at a time. If there are multiple heavyweight apps running,
the user will be asked to designate which app should stay in memory. To identify
themselves as a heavyweight app, the app designates a flag in their manifest,
"cantSaveState".  The entire experience is available in AOSP and does not require
modification. Device implementations are required to respect this behavior.

Bug: 78457189
Change-Id: I5397f169923abe530fca17af6a5631adbefeed08
Test: tested in CDD editor

CDD: Require the restrictive behavior of hidden APIs to be consistent.

- Ensure that the defined limitations for private API list is kept
to keep the same expectations across devices.
- Clarifying what can be allowed for adding / removing APIs in API
 list.


bug: 74128885
Test: m
Change-Id: I9a20ad2db814969e19dfc1f8cf8de1b930a310e5

CDD: Don't require any more the 32-bit equivalent ABIs for 64-bit devices

With 64-bit ABIs being introduced some time ago, and more apps and
system servers on the path to have 64-bit implementations, the need
to support 32-bit equivalent pairs of the 64-bit ABIs has been
diminshing.

This change will open the path to introduce 64-bit only devices.

Bug: 80085042
Test: n/a
Change-Id: I55b31e87363dc89b73093568d07639e0230ca245

Merge "CDD: Require a user warning for an app with API level <= 16" into pi-dev

Merge "CDD: Requirements for androidx namespace." into pi-dev

Merge "CDD: 2.5.3 Requirements for launching assistant for Automotive and Handheld." into pi-dev

CDD: Requirements for androidx namespace.

Device implementations must not make any modifications to Android
extension libraries (androidx) namespace as that creates developer
confusion.

BUG: 77285480

Change-Id: I3c7006db25a8c39e82354a9fd769d3cc045eb69a

CDD: 2.5.3 Requirements for launching assistant for Automotive and
Handheld.

On Automotive, short press of the Push to Talk (PTT) button MUST launch
the user-selected on-board assistant.

Also, moved the requirement long press on Home key  to launch assistant
from core requirement to Handheld as other form factors can have another
keys/buttons to launch the assistant e.g Automotive has PTT button.

Bug: 74882070
Bug: 74887509
Test: none
Change-Id: I23854ff211d05ebfa255ddb888fbb9fcf82b7cd7

Merge "Docs: Fixed intent link for section 3.2.3.5" into pi-dev

Merge "CDD: Requirements for ways to logout accessible from lockscreen" into pi-dev

Docs: Fixed intent link for section 3.2.3.5

 -Appended #ACTION_CHANGE_DEFAULT to
  https://developer.android.com/reference/android/provider/Telephony.Sms.Intents.html

Bug:110211242
Test: N/A
Change-Id: I16a6c194fe852d72eb29619e5cb7598b176a661a

CDD: Require a user warning for an app with API level <= 16

- Set the right expectation for the user when running an app that
is targeting at API level <=16.

Bug:74583359
Test:n/a

Change-Id: I7ea57a674b24a4e05a767373eaa0ab79b80c1e57

Merge "CDD: Add requirement for Remove Location Modes." into pi-dev

CDD: Requirements for ways to logout accessible from lockscreen

DevicePolicyManager.setLogoutEnabled enables a way to logout (stop current user and switch to user 0), but OEM can decide where to put the button, thus making CTS impossible. e.g. On Pixel, button is on power button menu and lockscreen. Want to include the requirement on CDD to make sure such a button is implemented.

Bug: 73800782
Test: None
Change-Id: Ie48a0ac8431fc0a39603dd996fcb8317394fb8e5

CDD: Add requirement for Remove Location Modes.

We have deprecated location mode in Android P, and would like to have
CDD language to make sure device settings UI doesn't show location
modes on P+ devices.

Bug:74576767

Test: N/A
Change-Id: If0a588c6cc61bd7d4079030e463369cb0445d501

Merge "CDD: Clarify default dialer language" into pi-dev

CDD: Require related to Apache HTTP client deprecation.

- Ensure the consistent behavior that is described in
Apache HTTP client deprecation of the developer doc.

Bug: 74130975
Test: n/a
Change-Id: I01c7cfabe3a20fbaac9c82527a30e43084a20028

Merge "CDD: Disallow modifying the default security provider list" into pi-dev

Merge "CDD: Relax TIF requirement for Android TV" into pi-dev

Merge "CDD: Display cutout requirements" into pi-dev

CDD: Display cutout requirements

- Clarify the requirements for devices that support cutout.
- The requirements are to ensure that cutout APIs work correctly and
consistently across devices.

Bug: 72669348
Test: ./make_cdd.py
Change-Id: I45aa5ce0be6e1053ef9e467eb26438ee3a695fa7

CDD: Clarify default dialer language

The intention of the existing CDD language is to communicate that a
device should allow the user to choose a different "Dialer/Phone"
app to replace the stock dialer/phone app.  This not only means for
placing calls, but also for providing the UI for incoming calls as
well.

We have seen reports in the field from developers creating such an
app that on some devices, the setting will work for most calls, but
sometimes incoming calls will result in the stock dialer UI being
shown instead of the user selected default dialer.  Since this is
an intermittent issue its hard to test with a CTS test.  Setting
the expectation through better requirements language.

Bug: 73368490
Test: Doc update
Change-Id: Ieed7c0c98a131c5749ffb64a93355f942eb02d5c

CDD: Relax TIF requirement for Android TV

Device implementations are no longer required to include a Third Party Input
framework (TIF) app by default. So references to how this app should function have been
removed. Validation of the APIs should continue.

Bug: 78113169
Test: NA CDD change
Change-Id: I8cf6baaacf2ad7c044e7be73b590643ba8738c60

CDD: Disallow modifying the default security provider list

- Security-related functionality is implemented by providing generic
  classes for a category of security functionality (such as
  javax.crypto.Cipher) and then security providers are registered that
  provide specific implementations of that functionality which are
  identified by a string identifier (such as "AES/GCM /NOPADDING").

- Interoperability is key for security functionality, and this
  requirement prevents device manufacturers from adding new security
  providers that are higher priority than the AOSP implementations and
  thus returning a different implementation than an app expects when
  it requests a specific identifier.

- If a device manufacturer wants to provide additional security
  functionality, they can put it at the end of the list, which means
  that developers will need to ask for it explicitly.

Test: manual inspection
Bug: 76462676
Change-Id: I20c2b6eb83488457fbebbbee6ddd10955c15410e

Merge "CDD: Require to render all resources on notification with more clarifications" into pi-dev

CDD: Require to render all resources on notification with more clarifications

- Ensure the consistent notifications and widgets.
- Ensure the actions and all resources are displayed together with the notification.
- SR to support Widgets features in default launcher.

Bug:77234794, 72669882, 77233433
Test: NA
Change-Id: I19c6569457046016aad1af2008528b617e6ce5cb

Merge "CDD: Gate Build.SERIAL behind the PHONE permission" into pi-dev

Merge "Docs: Clarify Device Owner consent requirements" into pi-dev

Docs: Clarify Device Owner consent requirements

In some scenarios (e.g. custom built devices) the user
may have already consented to Device Owner provisioning and
therefore it is unnecessary to require a further consent step.

Bug: 64556174
Test: ran make_cdd.py (success)

Change-Id: Ie84466fd6a88a7c58a9c9af257c1aee10a84c63f

CDD: Gate Build.SERIAL behind the PHONE permission

SERIAL now returns “UNKNOWN". For apps that need access a device's hardware serial number, they should request the READ_PHONE_STATE permission, then call getSerial()

Bug: 75962571

Test: none
Change-Id: I6de2dcc89ac12b2ccb9a5d8b0a285e112e50ab38

Merge "CDD: STRONGLY RECOMMEND Vulkan 1.1 / GLES 3.1" into pi-dev

Merge "CDD: Move managed_users requirement to handhelds section" into pi-dev

Merge "CDD: STRONGLY RECOMMEND to surface user affordance to block notification after multiple dismissals" into pi-dev

CDD: STRONGLY RECOMMEND to surface user affordance to block notification after multiple dismissals

- Provide better usability by providing users to dismiss unimportant notifications

Bug: 72670062
Change-Id: I0a808ed4535fd6639e9e3341be1322e59028d96c

CDD: STRONGLY RECOMMEND Vulkan 1.1 / GLES 3.1

- Changes recommendations to latest-available API versions.
- Narrows scope of GL implementations to fewer and newer versions, decreasing
 support surface and behavior variations.

Test: spellcheck
Bug: 77289694, 76152919, 109875843

Change-Id: Ieaa160f395a3b7c92f1847ef265c77502dda2b2a

CDD: Move managed_users requirement to handhelds section

Managed user provisioning feature currently only applies to
tablet/handhelds.

Bug: 73335228
Test: ran make_cdd.py (success)

Change-Id: I09d7fbe651c843ff3479fce92b4a7301969d0613

CDD: Relaxing the Media UI requirement to present MediaBrowser
hierarchy.

Allowing device implementations to have drawer or other mechanisms to
present MediaBrowser hierarchy.

Bug: 74885672
Test: Rand through markdown converter
Change-Id: I7ef6fad6fabcc9b1c836de8a4f97ecf949f3247e

CDD: Add libneuralnetworks.so to "Application Binary Interfaces"

  - NNAPI (libneuralnetworks.so) is a NDK API shipped in OC-MR1. Adding
  the NDK lib to CDD to ensure native API compatibility.

Bug: 70349981
Test: none
Change-Id: I4339e3a58ace2acaec1b8f0b8b9db8027438317d

Merge "Docs: Fix the broken link for Direct Boot Aware." into oreo-dev am: 144ce4d86f am: 027d7f02af
am: 4be0b9f900

Change-Id: I64b7ffe1aa27511e341afa66fb394f9961e7f2d1

Merge "Docs: Fix the broken link for Direct Boot Aware." into oreo-dev
am: 144ce4d86f

Change-Id: Ic59512af461dc7b56a489b935f9a2eea2ec7a89f

Merge "Docs: Fix the broken link for Direct Boot Aware." into oreo-dev