Xiaomi Pocophone F1 128Gb+6Gb Dual LTE [29/118] Application binary interfaces

resized.

MAY show an IME (input method editor, a user control that enables users to enter text) on

the primary display, when a text input field becomes focused on a secondary display.

SHOULD implement the input focus on the secondary display independently of the

primary display, when touch or key inputs are supported.

SHOULD have android.content.res.Configuration which corresponds to that display in order to be

displayed, operate correctly, and maintain compatibility if an activity is launched on

secondary display.

If device implementations allow launching normal Android Activities on secondary displays and

primary and secondary displays have different android.util.DisplayMetrics :

[C-2-1] Non-resizeable activities (that have resizeableActivity=false in AndroidManifest.xml ) and

apps targeting API level 23 or lower MUST NOT be allowed on secondary displays.

If device implementations allow launching normal Android Activities on secondary displays and a

secondary display has the android.view.Display.FLAG_PRIVATE flag:

[C-3-1] Only the owner of that display, system, and activities that are already on that

display MUST be able to launch to it. Everyone can launch to a display that has

android.view.Display.FLAG_PUBLIC flag.

3.3. Native API Compatibility

Native code compatibility is challenging. For this reason, device implementers are:

[SR] STRONGLY RECOMMENDED to use the implementations of the libraries listed below

from the upstream Android Open Source Project.

3.3.1. Application Binary Interfaces

Managed Dalvik bytecode can call into native code provided in the application .apk file as an ELF .so

file compiled for the appropriate device hardware architecture. As native code is highly dependent on

the underlying processor technology, Android defines a number of Application Binary Interfaces

(ABIs) in the Android NDK.

Device implementations:

[C-0-1] MUST be compatible with one or more defined ABIs and implement compatibility

with the Android NDK.

[C-0-2] MUST include support for code running in the managed environment to call into

native code, using the standard Java Native Interface (JNI) semantics.

[C-0-3] MUST be source-compatible (i.e. header-compatible) and binary-compatible (for

the ABI) with each required library in the list below.

[C-0-4] MUST support the equivalent 32-bit ABI if any 64-bit ABI is supported.

[C-0-5] MUST accurately report the native Application Binary Interface (ABI) supported by

the device, via the android.os.Build.SUPPORTED_ABIS , android.os.Build.SUPPORTED_32_BIT_ABIS

, and android.os.Build.SUPPORTED_64_BIT_ABIS parameters, each a comma separated list of

ABIs ordered from the most to the least preferred one.

[C-0-6] MUST report, via the above parameters, only those ABIs documented and

described in the latest version of the Android NDK ABI Management documentation , and

MUST include support for the Advanced SIMD (a.k.a. NEON) extension.

[C-0-7] MUST make all the following libraries, providing native APIs, available to apps that

Page 29 of 118