Xiaomi Pocophone F1 128Gb+6Gb Dual LTE [32/118] Api behavioral compatibility

[C-1-2] MUST support the HTML5/W3C webstorage API and SHOULD support the

HTML5/W3C IndexedDB API . Note that as the web development standards bodies are

transitioning to favor IndexedDB over webstorage, IndexedDB is expected to become a

required component in a future version of Android.

MAY ship a custom user agent string in the standalone Browser application.

SHOULD implement support for as much of HTML5 as possible on the standalone

Browser application (whether based on the upstream WebKit Browser application or a

third-party replacement).

However, If device implementations do not include a standalone Browser application, they:

[C-2-1] MUST still support the public intent patterns as described in section 3.2.3.1 .

3.5. API Behavioral Compatibility

The behaviors of each of the API types (managed, soft, native, and web) must be consistent with the

preferred implementation of the upstream Android Open Source Project . Some specific areas of

compatibility are:

[C-0-1] Devices MUST NOT change the behavior or semantics of a standard intent.

[C-0-2] Devices MUST NOT alter the lifecycle or lifecycle semantics of a particular type of

system component (such as Service, Activity, ContentProvider, etc.).

[C-0-3] Devices MUST NOT change the semantics of a standard permission.

Devices MUST NOT alter the limitations enforced on background applications. More

specifically, for background apps:

[C-0-4] they MUST stop executing callbacks that are registered by the app to

receive outputs from the GnssMeasurement and GnssNavigationMessage .

[C-0-5] they MUST rate-limit the frequency of updates that are provided to the

app through the LocationManager API class or the WifiManager.startScan() method.

[C-0-6] if the app is targeting API level 25 or higher, they MUST NOT allow to

intents in the app's manifest, unless the broadcast intent requires a "signature"

or "signatureOrSystem" protectionLevel permission or are on the exemption list .

[C-0-7] if the app is targeting API level 25 or higher, they MUST stop the app's

background services, just as if the app had called the services' stopSelf()

method, unless the app is placed on a temporary whitelist to handle a task

that's visible to the user.

[C-0-8] if the app is targeting API level 25 or higher, they MUST release the

wakelocks the app holds.

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.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:

Page 32 of 118