| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
pi-qpr1-release
Change-Id: Id700369af26cfbbffdcd5b72900a24435d5e02b8
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\| |
| | |
| | |
| | |
| | |
| | | |
pi-qpr1-release
Change-Id: Ic4efa33ea95c848327d49f41b7a29d927b53cbf9
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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
|
| |\ \ \ |
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- More consistency on the terminology update.
Bug: 110838439
Test: TH only, minor text changes
Change-Id: I21093ba2b14714dc6a6c22a34457b3243faf58df
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- 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
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
through statsd." into pi-dev
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
| |\ \ \ \
| | |_|/ /
| |/| | | |
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| |\ \ \ |
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Clarifying the condition to enter S3/S4 power saving modes.
Bug: b/76169148
Test: N/A
Change-Id: Ie98bcebd10b7f27c9816cfad52d3e130f4dae0e8
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
- Modifying the requirement language for C-0-12(kernel page table isolation)
requirement to add clarity.
Bug: 79088532
Change-Id: If3b3da40b78203c177cb4b833ea49837336a72b7
|
| |\ \
| | | |
| | | |
| | | | |
written to flash based SSD storage." into pi-dev
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| |\ \
| | | |
| | | |
| | | | |
consistent." into pi-dev
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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
|
| |\ \ \
| | |/ /
| |/| |
| | | | |
"android.permission.RECOVER_KEYSTORE"" into pi-dev
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
"android.permission.RECOVER_KEYSTORE"
- Prevent brute-force attacks on the lockscreen knowledge factor.
Bug: 73599998
Test: None
Change-Id: I8f7fa701b11f015e26429c4683a36d37aa2faa47
|
| |\ \
| | | |
| | | |
| | | | |
KEYCODE_MEDIA_PLAY_PAUSE/ KEYCODE_HEADSETHOOK." into pi-dev
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
KEYCODE_HEADSETHOOK.
This enables a way to launch voice search with wired/BT headsets
across different devices.
BUG: 69103849
TEST: manual -
Change-Id: I9e74bc8d8c09681338b5e7ec23565cb126258ec1
|
|\| |
| | |
| | |
| | |
| | |
| | | |
pi-qpr1-release
Change-Id: Ib0ce307e31eb7e94d1d75169f3594522ea7bf385
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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
|
| |\ \ \
| | |/ /
| |/| | |
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| |\ \ |
|
| | |/
| | |
| | |
| | |
| | |
| | | |
Bug: 76218955
Change-Id: Iba17c9a87736921e455b343037bc07f8ad4e71e7
|
| |\ \
| | | |
| | | |
| | | | |
conditions" into pi-dev
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- 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
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\|
| |
| |
| |
| |
| | |
pi-qpr1-release
Change-Id: I5d5b0d5ab0f13c54e99c0f6d0741d96802360cac
|
| |\
| | |
| | |
| | | |
with secure lock screen" into pi-dev
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
with secure lock screen
- Ensure the consistent security among handheld devices
-Bug:76434535, 73723272
Change-Id: Ic85fce3b71a771eba355830e7374b7517d3fc12a
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\|
| |
| |
| |
| |
| | |
pi-qpr1-release
Change-Id: I73465bbe388f8a5b5411c2e4cc270e545aec293a
|
| |\
| | |
| | |
| | | |
namespace API's." into pi-dev
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
API's.
Bug:74887599
Test: NA
Change-Id: I92ad9cfa4fd5b51b3b7d133e646f7b405fbed072
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
HEIF (HEIC) decoding relies on HEVC decoding which is already mandatory
in Android (since Lollipop) so added requirements for HEIF decoding.
Bug: 74978402
Test: CDD update only
Change-Id: I4e88e3b712fa99cfd55aaa1afb389d219202ee2d
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
consistency with CTS" into pi-dev
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
CTS
- Fix the number and update SR to MUST to align with CTS test.
Bug: 74593141
Test: All existing test passes.
Change-Id: I126b297b2c7316538d26932c67d52081689a8d4a
|
| |\ \ \ \ \ |
|