Xiaomi Pocophone F1 64Gb+6Gb Dual LTE [102/118] User experience consistency

1920x1080@30fps-10Mbps and SHOULD be capable to decode 3840x2160@30fps-

20Mbps (equivalent to 4 instances of 1920x1080@30fps-5Mbps).

[C-1-13] MUST support HardwarePropertiesManager.getDeviceTemperatures API and return

accurate values for skin temperature.

[C-1-14] MUST have an embedded screen, and its resolution MUST be at least be

FullHD(1080p) and STRONGLY RECOMMENDED TO BE be QuadHD (1440p) or higher.

[C-1-15] The display MUST update at least 60 Hz while in VR Mode.

[C-1-16] The display latency on Gray-to-Gray, White-to-Black, and Black-to-White

switching time MUST be ≤ 3 ms.

[C-1-17] The display MUST support a low-persistence mode with ≤5 ms persistence,

persistence being defined as the amount of time for which a pixel is emitting light.

[C-1-18] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension section

7.4.3 .

[SR] STRONGLY RECOMMENDED to support android.hardware.sensor.hifi_sensors feature and

MUST meet the gyroscope, accelerometer, and magnetometer related requirements for

android.hardware.hifi_sensors .

MAY provide an exclusive core to the foreground application and MAY support the

Process.getExclusiveCores API to return the numbers of the cpu cores that are exclusive to the

top foreground application.

If exclusive core is supported, then the core:

[C-2-1] MUST not allow any other userspace processes to run on it (except device drivers

used by the application), but MAY allow some kernel processes to run as necessary.

8. Performance and Power

Some minimum performance and power criteria are critical to the user experience and impact the

baseline assumptions developers would have when developing an app.

8.1. User Experience Consistency

A smooth user interface can be provided to the end user if there are certain minimum requirements to

ensure a consistent frame rate and response times for applications and games. Device

implementations, depending on the device type, MAY have measurable requirements for the user

interface latency and task switching as described in section 2 .

8.2. File I/O Access Performance

Providing a common baseline for a consistent file access performance on the application private

data storage ( /data partition) allows app developers to set a proper expectation that would help their

software design. Device implementations, depending on the device type, MAY have certain

requirements described in section 2 for the following read and write operations:

Sequential write performance . Measured by writing a 256MB file using 10MB write

buffer.

Random write performance . Measured by writing a 256MB file using 4KB write buffer.

Sequential read performance . Measured by reading a 256MB file using 10MB write

buffer.

Random read performance . Measured by reading a 256MB file using 4KB write buffer.

Page 102 of 118