Xiaomi Redmi Note 8 Pro 64Gb+6Gb Dual LTE [51/132] Application packaging compatibility

Device implementations MUST satisfy the following requirements:

[C-0-1] Instant Apps MUST only be granted permissions that have the android:protectionLevel

set to "instant" .

[C-0-2] Instant Apps MUST NOT interact with installed apps via implicit intents unless one

of the following is true:

The component's intent pattern filter is exposed and has

CATEGORY_BROWSABLE

The action is one of ACTION_SEND, ACTION_SENDTO,

ACTION_SEND_MULTIPLE

The target is explicitly exposed with android:visibleToInstantApps

[C-0-3] Instant Apps MUST NOT interact explicitly with installed apps unless the

component is exposed via android:visibleToInstantApps.

[C-0-4] IInstalled Apps MUST NOT see details about Instant Apps on the device unless the

Instant App explicitly connects to the installed application.

3.16. Companion Device Pairing

Android includes support for companion device pairing to more effectively manage association with

companion devices and provides the CompanionDeviceManager API for apps to access this feature.

If device implementations support the companion device pairing feature, they:

[C-1-1] MUST declare the feature flag FEATURE_COMPANION_DEVICE_SETUP .

[C-1-2] MUST ensure the APIs in the android.companion package is fully implemented.

[C-1-3] MUST provide user affordances for the user to select/confirm a companion device

is present and operational.

3.17. Heavyweight Apps

If device implementations declare the feature FEATURE_CANT_SAVE_STATE , then they:

[C-1-1] MUST have only one installed app that specifies cantSaveState running in the system

at a time. If the user leaves such an app without explicitly exiting it (for example by

pressing home while leaving an active activity the system, instead of pressing back with

no remaining active activities in the system), then device implementations MUST

prioritize that app in RAM as they do for other things that are expected to remain running,

such as foreground services. While such an app is in the background, the system can still

apply power management features to it, such as limiting CPU and network access.

[C-1-2] MUST provide a UI affordance to chose the app that won't participate in the normal

state save/restore mechanism once the user launches a second app declared with

cantSaveState attribute.

[C-1-3] MUST NOT apply other changes in policy to apps that specify cantSaveState , such as

changing CPU performance or changing scheduling prioritization.

If device implementations don't declare the feature FEATURE_CANT_SAVE_STATE , then they:

[C-1-1] MUST ignore the cantSaveState attribute set by apps and MUST NOT change the app

behavior based on that attribute.

4. Application Packaging Compatibility

Page 51 of 132