Xiaomi Pocophone F1 128Gb+6Gb Dual LTE [105/118] Uid and process isolation

runtime permissions.

[C-0-4] MUST have one and only one implementation of both user interfaces.

[C-0-5] MUST NOT grant any runtime permissions to preinstalled apps unless:

the user's consent can be obtained before the application uses it

the runtime permissions are associated with an intent pattern for which the preinstalled

application is set as the default handler

If device implementations include a pre-installed app or wish to allow third-party apps to access the

usage statistics, they:

[SR] are STRONGLY RECOMMENDED provide user-accessible mechanism to grant or

revoke access to the usage stats in response to the

android.settings.ACTION_USAGE_ACCESS_SETTINGS intent for apps that declare the

android.permission.PACKAGE_USAGE_STATS permission.

If device implementations intend to disallow any apps, including pre-installed apps, from accessing

the usage statistics, they:

[C-1-1] MUST still have an activity that handles the

android.settings.ACTION_USAGE_ACCESS_SETTINGS intent pattern but MUST implement it as

a no-op, that is to have an equivalent behavior as when the user is declined for access.

9.2. UID and Process Isolation

Device implementations:

[C-0-1] MUST support the Android application sandbox model, in which each application

runs as a unique Unixstyle UID and in a separate process.

[C-0-2] MUST support running multiple applications as the same Linux user ID, provided

that the applications are properly signed and constructed, as defined in the Security and

Permissions reference .

9.3. Filesystem Permissions

Device implementations:

[C-0-1] MUST support the Android file access permissions model as defined in the

Security and Permissions reference .

9.4. Alternate Execution Environments

Device implementations MUST keep consistency of the Android security and permission model, even

if they include runtime environments that execute applications using some other software or

technology than the Dalvik Executable Format or native code. In other words:

[C-0-1] Alternate runtimes MUST themselves be Android applications, and abide by the

standard Android security model, as described elsewhere in section 9 .

[C-0-2] Alternate runtimes MUST NOT be granted access to resources protected by

permissions not requested in the runtime’s AndroidManifest.xml file via the < uses-permission >

mechanism.

[C-0-3] Alternate runtimes MUST NOT permit applications to make use of features

protected by Android permissions restricted to system applications.

Page 105 of 118