Xiaomi Pocophone F1 128Gb+6Gb Dual LTE [104/118] Permissions

Xiaomi Pocophone F1 128Gb+6Gb Dual LTE [104/118] Permissions
If device implementations include two or more CPU cores, they:
SHOULD provide at least one exclusive core that can be reserved by the top foreground
application.
If device implementations support reserving one exclusive core for the top foreground application,
they:
[C-2-1] MUST report through the Process.getExclusiveCores() API method the ID numbers of
the exclusive cores that can be reserved by the top foreground application.
[C-2-2] MUST not allow any user space processes except the device drivers used by the
application to run on the exclusive cores, but MAY allow some kernel processes to run as
necessary.
If device implementations do not support an exclusive core, they:
[C-3-1] MUST return an empty list through the Process.getExclusiveCores() API method.
9. Security Model Compatibility
Device implementations:
[C-0-1] MUST implement a security model consistent with the Android platform security
model as defined in Security and Permissions reference document in the APIs in the
Android developer documentation.
[C-0-2] MUST support installation of self-signed applications without requiring any
additional permissions/certificates from any third parties/authorities. Specifically,
compatible devices MUST support the security mechanisms described in the follow
subsections.
9.1. Permissions
Device implementations:
[C-0-1] MUST support the Android permissions model as defined in the Android developer
documentation. Specifically, they MUST enforce each permission defined as described in
the SDK documentation; no permissions may be omitted, altered, or ignored.
MAY add additional permissions, provided the new permission ID strings are not in the
android.\* namespace.
[C-0-2] Permissions with a protectionLevel of PROTECTION_FLAG_PRIVILEGED MUST only be
granted to apps preloaded in the privileged path(s) of the system image and within the
subset of the explicitly whitelisted permissions for each app. The AOSP implementation
meets this requirement by reading and honoring the whitelisted permissions for each app
from the files in the etc/permissions/ path and using the system/priv-app path as the privileged
path.
Permissions with a protection level of dangerous are runtime permissions. Applications with
targetSdkVersion > 22 request them at runtime.
Device implementations:
[C-0-3] MUST show a dedicated interface for the user to decide whether to grant the
requested runtime permissions and also provide an interface for the user to manage
Page 104 of 118

Содержание

Похожие устройства

Скачать