CDD: Gyro measurement range for Automotive
Automotive device implementations gyroscope SHOULD have a measurement
range of -250 and +250 degrees per second (dps).
Automotive devices do not need high measurement ranges that are seen in
other device types and the lower measurement range increases the
accuracy.
Bug: b/67084877
Test: N/A
Change-Id: I17af280aac8139fb4e755fdb4944aee1e911771f
CDD: Specify channel configurations for opus codec
Both decoder and encoder, which have different configuration limits.
Bug: 139210584
Test: compatibility/cdd/cdd_gen.sh
Change-Id: Ic7963d0fa2a13fa1e4aa409b1b2d194bfc74abb2
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
CDD: add media codec characterization
Added rules for codecs starting with "OMX" and "C2." so
there is less developer confusion, Also device implementations
MUST publish achievable frame rates information to app developers.
Bug: 123950993
Change-Id: I74d729fdd6d748acea3011b48c9434d646a37f9b
CDD: Updates must be signed and verified on device.
Clarify that all updates must be signed and verified
on device.
Bug: 124238047
Test: None
Change-Id: Ibbb1cecaa3bbb2166fe33ab83d761e9d9e93cec3
CDD: Codec 2.0 and OMX requirements for Media Codec Security.
These requirements are added to ensure compliance with media
codec security features.
Bug: 124333998
Change-Id: Ic0b13595807ab95917ea4af4536912c6e525ac82
CDD: Clarify privacy requirement for bugreports.
Clarify that bugreports are covered by the following requirement:
MUST NOT preload or distribute software components out-of-box that send
user's private information off the device without the user's consent or
clear ongoing notifications.
Bug: 132458597
Test: N/A
Change-Id: I4d1732bb45153e5eccce1964437f9bdf25350d54
CDD: Require new device identifier access restrictions
Devices must prevent access to all device identifiers from
an app that does not meet one of the new requirements.
Bug: 123367433
Test: N/A
Change-Id: I683ff569f8f51c38fa4defa0f60c898ea48414ab
Docs: Clean up Automotive sensor requirements.
Clean up Automotive sensor requirements struture.
Bug: b/124318257
Test: N/A
Change-Id: Iaabb094b5e993230fb6949167dcb2ef34b8c21e1
CDD: Strongly recommend StrongBox for devices with secure processors
This arguably is a weakening of the P recommendation, but it's part of
an incremental strategy to mandate StrongBox across the entire
ecosystem. We'll start by recommending it for devices with the
necessary hardware, then move to mandating it for such devices and
recommending that all devices add such hardware, then mandate it for
all devices.
Bug: 135707870
Test: N/A
Change-Id: Idf18fde8fc163ee0944a6ce1e611441414ebc461
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
CDD: Strengthen requirements for audio timestamp accuracy
Improve app compatibility for A/V sync (lip sync), video + audio camcorder
recording, synchronized playback over multiple paths, and other use
cases by strengthening the accuracy requirement for audio timestamps.
Bug: 123941630
Test: N/A
Change-Id: I4d4c2dffe27e8c231bb38526cd707b69d7be2c66
CDD: Android Automotive Media UI requirements
Android Automotive media applications rely on Media UI for all their
features to ensure driver distraction concerns are addressed by the
device implementation.
These requirements ensure that applications core functionalities are
reachable (settings, search, etc.).
Bug: 123357837
Test: N/A
Change-Id: Ic1567ea49fab8f6527e175b6c4eb0783e69d263d
CDD: Require Android Automotive permissions.
Automotive device implementations MUST support and enforce all
permissions constants as defined in android.car.Car.
Bug: b/124333135
Test: N/A
Change-Id: I6bdca51829d9266de432387065c93cb40ecedc2f
Docs: Add link to measuring biometric unlock security
Test: N/A
Fixes: 124403616
Change-Id: I45cb719ffe15dd9a1c3456304951f1faea6b2000
CDD: Automotive devices driver distraction restrictions
Add language to Automotive devices to consider
driver distraction conditions while implementing
UI functions like notificiations and systemUI
Bug: 128602332
Bug: 128602599
Bug: 128602611
Bug: 128603958
Bug: 128604385
Bug: 128603807
Test: N/A
Change-Id: I8890197ecb0210f0778ccef2c92f57f599dc17f0
CDD: Add automotive camera requirements for external view camera
- This change puts additional camera requirements for automotive device
implementations.
- Clarify the requirements for external view camera.
Bug: 118935945
Change-Id: I84d34db347f688db90eb2b98505d9b947166304a
Signed-off-by: Changyeon Jo <changyeon@google.com>
CDD: changed CPU performance test from SimpleSynth to SynthMark.
Added benchmarks and test instructions for testing CPU performance
using SynthMark.
Test: N/A
Bug: 120295894
Change-Id: I6d1b5cfca40bc7ced5470c52064c5e515b43ec7f
CDD: Audio effects in float and multi-channel
Justfication: this change improves application compatibility for audio
effects when applied to streams that use either floating-point format
and/or have multiple channels, by specifying that the effects must be
supported in those cases.
Test: N/A
Bug: 123958100
Change-Id: I304b0db87d0252ceb435e05e5fffc11f52d3a322
CDD: Automotive requirements for Garage Mode.
Android Automotive implementations MUST enter Garage Mode at least 1
time before the car starts powering down and have a Garage Mode minimum
duration of 15 minutes. Device implementations MAY reduce duration based
on the device battery level.
Garage mode enables applications to run operations when the device is
idle.
Bug: b/120432704
Test: N/A
Change-Id: I57bc912f553bd9855059af05e27023c8e6aa7e87
CDD: Automotive MUST provide dead reckoning sensors
- Ensure that 3rd party applications can use original raw data
to create their own dead reckoning.
Bug: b/123728101
Test: N/A
Change-Id: Ia00cab0218d5e9f43090c838df8ceb9ea8d2dd18
CDD: Auto req for Headless System and Guest Users.
If Automotive device implementations support multiple users, they:
* MUST NOT allow users to interact with nor switch into the Headless System
User, except for device provisioning.
* MUST switch into a Secondary User before BOOT_COMPLETED.
* MUST support the ability to create a Guest User even when the maximum
number of Users on device has been reached.
Headless System User should not be a user-facing user. Users and 3rd party
applications should be able to rely that the system is on Secondary User
after boot is completed.
Because Automotive devices are likely to used temporarily by different
users, if they support multiple users they MUST support Guest User (even
if the maximum number of Users on device has been reached).
Bug: 127875406, 124243324
Test: N/A
Change-Id: Id8794008e49de684eecc61ad47463f9b25f7cb52
CDD: Relax hardware vulnerability requirements
Limit mitigation requirements to vulnerable hardware.
Bug: 122834364
Change-Id: If81385671bfd42f0d100f139c081fd759de81cd0
CDD: clarify 5.5.1 raw audio playback is source format
Bug: 136131226
Test: N/A
Change-Id: I31c7df43fa5b336fa01e9af28e0108b9c94b1dc4
CDD: Add requirement to meet AAudio latency over MMAP path
Clarified that latency and USB audio requirements MUST be met
for atleast one path of AAudio and it is Strongly Recommended
to meet over both the paths.
Bug: 78022860
Test: N/A
Change-Id: I6f9fdb1552b7afe64cd74fe15b892fdcafc08084
CDD: Android Automotive devices MUST implement FBE.
Android Automotive devices MUST implement FBE. That requirement is now
covered in the core language, so the Automotive specific language can
be removed.
Bug: 131866367
Test: N/A
Change-Id: Id402a875d7522a5e90089c02e882cbd0535d439e
CDD: Relax GNSS requirement for Automotive.
Relaxing GNSS technology generation requirements for Automotive from
MUST to STRONGLY RECOMMENDED.
Bug: 121005128
Test: N/A
Change-Id: I2e7812545ccbb05a91a7bd680ea432d016db3097
CDD: Require 48kHz raw audio capture.
Adding in requirement for audio capture at 48kHz as it is
useful for video recording applications. The lack of 48 kHz
audio capture and SW resampling reduces overall audio quality
for many of the common video capture use cases.
Bug: 123959292
Test: N/A
Change-Id: I2df11ad731c877b0e5ace272d18c217051cab10c
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
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: Align mic and playback capture requirement
- The two audio sources should have the same privacy requirements.
- Some typo correction for section 5.4.
Test: N/A
Bug: 124333245
Change-Id: Ida67df090b028b35f0dbea84c1e43de8339c5696
Signed-off-by: Kevin Rocard <krocard@google.com>
CDD: Update CDD for CFI and SCS
-Strongly recommend shadow-call-stack (SCS) and control-flow-integrity
(CFI) for the kernel and userspace to provide additional protection
against code-reuse attacks.
Bug: 123365748
Test: --
Change-Id: Ida7b2f190da26439443d5247d467047e134933c1
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: Add requirement for libamidi.so
- Aligning with the added support for midi library.
Test: N/A
Bug: 124249176
Change-Id: Ic15bac32af7fed12ff93cdedcfbafae36e7ceb03
CDD: Relax HDMI requirement for pro audio
Test: N/A
Bug: 110202363
Change-Id: Ic41d8a5234330a5c6fe95ca1db014644d9c05f9e
CDD: Require multi-channel, high-resolution audio over USB
- Consistently support USB audio at high resolution.
Test: N/A
Bug: 123958167
Change-Id: I1ac7757a20b01fb896ac069ea640c8d6eb64a4fb
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: 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: Update shared storage sandboxing
- Isolate storage sandboxes to tighten privacy and security of shared
storage.
Bug: 121275794
Test: none
Change-Id: I018ba6a13c10d0adc41e4aac3c62f6407be38803
CDD: Remove "shared device" exception for encryption
-This can potentially be used to try to gain exceptions for devices
we never envisioned (for example, many phones allow multiple user
accounts, and any device shipping with family features is
pretty much by definition going to be "shared").
-This exception was also somewhat designed for devices with
lower hardware capabilities. But with Adiantum available, we
haven't seen any data showing such an exception is still
needed.
Bug: 124123642
Test: None
Change-Id: Ie2b3f0b5be2c8cda80176160255558e6e5a2cff5
CDD: Remove encryption performance exception
We now require encryption on all devices, without any
exceptions for performance.
For devices which lack AES CPU instructions, and thus have
performance concerns with AES, we allow the use of Adiantum as
the encryption method.
Bug: 118200376
Test: None
Change-Id: I219fd6d1733c053741d8b71b7f5bd067938d1196
CDD: Remove FDE, mandate FBE where encryption is mandated
- Already-launched devices are exempted, and must instead follow
mandates of their launch CDD.
Bug: 118760699
Test: not applicable to CDD changes
Change-Id: Icea70b46c986af187248d9b946e5c17d2b8ef1dd
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: Remove Automotive SR on Quick Settings.
Remove:
Automotive device implementations are STRONGLY RECOMMENDED to include a
Quick Settings UI component.
Bug: 129265298
Test: N/A
Change-Id: I130548c4cc2286c3b431262842ee9ec403347305
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: Remove Doze requirements for Automotive.
Remove "MUST provide user affordance to display all apps that are
exempted from App Standby and Doze power-saving modes.
Bug: b/120475309
Test: N/A
Change-Id: I25c3a8aa2fca8a9738ef159025cdd31bce8c16bd
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 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)
CDD: Clarify data deletion requirements
- Make it clear that all generated data, not just user-generated data
should be deleted on factory device reset.
- Clarify that only operating system files on read-only filesystems are
exempt from being deleted.
Bug: 124238463
Test: None
Change-Id: I3cd0bb57ed2c425763b7a50849dc216bc5dcab50
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
CDD Errata: Fixing missing changes from Oreo-MR1 to Pie.
BUG: 116495107
Change-Id: I0d469a5abf6c7fa573c108952d4d1e0b1cad7f02
Docs: First batch of errata fixes for 10/18.
- 7.3/C-1-6: Fixing CDD language to align with the corresponding CTS test (bug: 809654).
- Other updates are to fix typos.
Bug: 809654, 111602321, 74593141
Test: make_cdd.py --version 8.0 --branch "oreo-dev"
Change-Id: I773b93e384ee6729348d6765172b7f5079eea3d6
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: correct file type for USAC
Remove requirement for .loas and .xhe files, not required by P.
Bug: 77327971
Test: stage CDD
Change-Id: Ibf085b5f3f1e6466c5e839de84916561003cfcfa
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: Fix links in section numbering.
Bug: 112010610
Test: ./cdd-gen.sh --version 9 --branch pie-dev
Change-Id: I02fb87458e8ffa4ef71f143f33e0144335425a66
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
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: 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
CDD: Move the req of supporting encryption under perf carve-out
- Ensure the consistent security across devices
- Replace the carve-out of secure lock screen with the perf carve-out
for supporting encryption
Test: None
Bug: 71909258
Change-Id: Ied56bb0bdd99e3f27e68c13829073c5982019c74
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
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: Update the condition to enter S3/S4 power saving modes
- Clarifying the condition to enter S3/S4 power saving modes.
Bug: b/76169148
Test: N/A
Change-Id: Ie98bcebd10b7f27c9816cfad52d3e130f4dae0e8
CDD: Clarifying kernel page table isolation
- Modifying the requirement language for C-0-12(kernel page table isolation)
requirement to add clarity.
Bug: 79088532
Change-Id: If3b3da40b78203c177cb4b833ea49837336a72b7
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: Require logging of some basic events available to app developers through statsd.
Enlist required fields to be more specific about what is
needed for developer tools and what is needed for privacy.
Bug: 76161779
Bug: 74125988
Test: None
Change-Id: I4ff9a73f72c3270caaac0f116297d666a58561fb
CDD: Device implementations must report the number of bytes read
and written to flash based SSD storage.
Flash wear is an important concern. The statistics
reported here is important to analyze and find the apps that use flash
most heavily.
This CDD requirement requires that these statistics should be
reported.
Bug: 74887330
Test: N/A
Change-Id: I361f23e59649705d2b2fc517ddb80ede1647f92f
CDD: Requirements for services that have access to "android.permission.RECOVER_KEYSTORE"
- Prevent brute-force attacks on the lockscreen knowledge factor.
Bug: 73599998
Test: None
Change-Id: I8f7fa701b11f015e26429c4683a36d37aa2faa47
CDD: Add section about Android Protected Confirmation API
- Device implementations with secure hardware may implement the
Android Protected Confirmation API to request the user to
approve a textual message.
Bug: 73001803
Test: n/a
Change-Id: I96c5929b0b4ab99b31a9fe7ca0ac82710f94cdca
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: 9.10. Device Integrity: Change verified boot items from SR to MUST.
Change STRONGLY RECOMMENDED to MUST for verified boot items and slight
cleanup of language used:
- MUST use tamper-evident storage: for storing whether the bootloader
is unlocked. Tamper-evident storage means that the boot loader can
detect if the storage has been tampered with from inside Android.
- MUST 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.
- MUST implement rollback protection for the partitions used by
Android (e.g. boot, system partitions) and use tamper-evident
storage for storing the metadata used for determining the minimum
allowable OS version.
Test: n/a
Bug: 72919368
Change-Id: Ifcb0c994cb86f92a422dcde6fa6da1ca064d4ca0
CDD: Handheld recommedations for long press of KEYCODE_MEDIA_PLAY_PAUSE/
KEYCODE_HEADSETHOOK.
This enables a way to launch voice search with wired/BT headsets
across different devices.
BUG: 69103849
TEST: manual -
Change-Id: I9e74bc8d8c09681338b5e7ec23565cb126258ec1
Docs: Clarification to `KEYCODE_BACK` requirements.
Bug: 76218955
Change-Id: Iba17c9a87736921e455b343037bc07f8ad4e71e7
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
CDD: Handheld: Require Lockdown mode and sleep timeout for devices
with secure lock screen
- Ensure the consistent security among handheld devices
-Bug:76434535, 73723272
Change-Id: Ic85fce3b71a771eba355830e7374b7517d3fc12a
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
Docs: Automotive: Added developer facing links for android.car.* namespace
API's.
Bug:74887599
Test: NA
Change-Id: I92ad9cfa4fd5b51b3b7d133e646f7b405fbed072
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: 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
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
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: 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 CDD changes for CFI and IOSAN
This CL renames section 9.7 to 'Security Features' (instead of kernel
security features), and adds a new sub-section for userspace specific
security feature advice. There's only a single recommendation in for
P, but we will be using this section to add more details and
recommendations/constraints for Q.
Bug: 73724250
Test: --
Change-Id: If45c5fd9b7668dcafc9ce8dbd2a59b9c4418ca42
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
CDD: StrongBox requirements
- Tighten the security by supporting StrongBox.
- Clarifying the requirements if StrongBox is supported.
Bug: 73002261
Test: N/A
Change-Id: I9834ced2e697bee013cb0725f31745826da1f0c5
CDD: Require verified boot on all devices, including low ram devices
We remove the low RAM exception for verified boot.
Test: None
Bug: 73374550
Change-Id: I340e8753c8648bbe2a68426123851359d4cba1cb
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: 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
CDD: Developer options to be made available for all developers
- The mechanism to enable developer options can be different per
partners and it should be clearly documented publicly so that any
developers can enable developer options when necessary (i.e.
disallowing only selected developers to access to developer options).
- Fixing a few minor section numbering issues.
Bug: 78370047
Test: NA
Change-Id: I6e433b424aea20caf977838a17690194b45ebe25
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
CDD: Tighten SR to MUST for HOT GNSS TTFF to 5 sec to keep consistency with
CTS
- Fix the number and update SR to MUST to align with CTS test.
Bug: 74593141
Test: All existing test passes.
Change-Id: I126b297b2c7316538d26932c67d52081689a8d4a
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
CDD: Recommended values for AAudioStream_getFramesPerBurst()
In order for AAudio to work properly, device implementations should
always have a burst size which is the same or less than that reported
by PROPERTY_OUTPUT_FRAMES_PER_BUFFER.
Bug: 74756238
Test: N/A
Change-Id: I1c365b6651357c3125339dd45d56f325e1153667
Docs: HDMI in at least one configuration.
Clarification to HDMI requirement, if device include HDMI port
and at least one configuration supports 24 bit/8 channels it is
considered compliant.
Bug: 76418651
Test: N/A
Change-Id: Iabfd2c75c2013c5acea1a30853b57d611e3ef9bd
Docs: clarify that that CONFIG_ARM_LPAE is not allowed for 32-bit ARM
- It's incompatible with PAN emulation for arm32 kernels.
- This is already implicitly tested when checking for
CONFIG_CPU_SW_DOMAIN_PAN.
Bug: 109828784, 74078653, 79088532, 73728376
Test: n/a
Change-Id: Idb6a96d6f8c13a959b4bdc2c5580294beeff2d7c
CDD: Add recommendation for touch input to audio output latency for Pro Audio.
Pro audio devices should not have a Touch input to audio output latency more
than 40 ms. This is useful for apps that require pro audio and low latency.
Bug: 28160677
Test: N/A
Change-Id: I173b454734b687582a46dc53db5c1b169f047675
CDD: Latency requirements also applicable to AAudio native APIs (in addition to OpenSL ES)
AAudio [AAudio native audio](https://developer.android.com/ndk/guides/audio/aaudio/aaudio.html)
is a newer native audio API for Android, with several advantages
over the OpenSL ES audio API. Requiring the corresponding performance
in AAudio as OpenSL ES will enable app developers to move towards AAudio.
Bug: 63663812
Test: N/A
Change-Id: Id4f6435b31d29d567461ff5dfa17b75d2776fdb5
CDD: Add GPU debug layer developer requirement
- This ensures that Vulkan graphics debug tools can connect and
interact with applications uniformly without requiring root access
to the device. Previously they could only discover layers that were
packaged with the application, or from system locations on rooted
devices.
- This functionality is covered by CtsGpuToolsHostTestCases
Bug: 76152639
Test: N/A
Change-Id: I02694399c9e9da21e19b0e94c4adf9de33959bbe