Google Pixel 3 64Gb+4Gb LTE [36/132] Background restriction

6. HarmonyJSSE - com.android.org.conscrypt.JSSEProvider

7. AndroidKeyStore - android.security.keystore.AndroidKeyStoreProvider

The above list is not comprehensive. The Compatibility Test Suite (CTS) tests significant portions of

the platform for behavioral compatibility, but not all. It is the responsibility of the implementer to

ensure behavioral compatibility with the Android Open Source Project. For this reason, device

implementers SHOULD use the source code available via the Android Open Source Project where

possible, rather than re-implement significant parts of the system.

3.5.1. Background Restriction

If device implementations implement the app restrictions that are included in AOSP or extend the app

restrictions, they:

[C-1-1] MUST provide user affordance where the user can see the list of restricted apps.

[C-1-2] MUST provide user affordance to turn on / off the restrictions on each app.

[C-1-3] MUST not automatically apply restrictions without evidence of poor system health

behaviour, but MAY apply the restrictions on apps upon detection of poor system health

behaviour like stuck wakelocks, long running services, and other criteria. The criteria MAY

be determined by device implementers but MUST be related to the app’s impact on the

system health. Other criteria that is not purely related to the　system health, such as the

app’s lack of popularity in the market, MUST NOT be used as criteria.

[C-1-4] MUST not automatically apply app restrictions for apps when a user has turned off

app restrictions manually, and MAY suggest the user to apply app restrictions.

[C-1-5] MUST inform users if app restrictions are applied to an app automatically.

[C-1-6] MUST return true for ActivityManager.isBackgroundRestricted() when the restricted app

calls this API.

[C-1-7] MUST NOT restrict the top foreground app that is explicitly used by the user.

[C-1-8] MUST suspend restrictions on an app that becomes the top foreground application

when the user explicitly starts to use the app that used to be restricted.

[C-1-9] MUST report all app restriction events via UsageStats . If device implementations

extend the app restrictions that are implemented in AOSP, MUST follow the

implementation described in this document .

3.6. API Namespaces

Android follows the package and class namespace conventions defined by the Java programming

language. To ensure compatibility with third-party applications, device implementers MUST NOT

make any prohibited modifications (see below) to these package namespaces:

java.*

javax.*

sun.*

android.*

androidx.*

com.android.*

That is, they:

[C-0-1] MUST NOT modify the publicly exposed APIs on the Android platform by changing

any method or class signatures, or by removing classes or class fields.

Page 36 of 132