Doogee S55 64Gb+4Gb Dual LTE [12/118] Performance and power

2.2.4. Performance and Power

[ 8.1 /H-0-1] Consistent frame latency . Inconsistent frame latency or a delay to render

frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below

1 frames in a second.

[ 8.1 /H-0-2] User interface latency . Device implementations MUST ensure low latency

user experience by scrolling a list of 10K list entries as defined by the Android

Compatibility Test Suite (CTS) in less than 36 secs.

[ 8.1 /H-0-3] Task switching . When multiple applications have been launched, re-

launching an already-running application after it has been launched MUST take less than

1 second.

Handheld device implementations:

[ 8.2 /H-0-1] MUST ensure a sequential write performance of at least 5 MB/s.

[ 8.2 /H-0-2] MUST ensure a random write performance of at least 0.5 MB/s.

[ 8.2 /H-0-3] MUST ensure a sequential read performance of at least 15 MB/s.

[ 8.2 /H-0-4] MUST ensure a random read performance of at least 3.5 MB/s.

[ 8.3 /H-0-1] All Apps exempted from App Standby and Doze power-saving modes MUST

be made visible to the end user.

[ 8.3 /H-0-2] The triggering, maintenance, wakeup algorithms and the use of global

system settings of App Standby and Doze power-saving modes MUST not deviate from

the Android Open Source Project.

Handheld device implementations:

[ 8.4 /H-0-1] MUST provide a per-component power profile that defines the current

consumption value for each hardware component and the approximate battery drain

caused by the components over time as documented in the Android Open Source Project

site.

[ 8.4 /H-0-2] MUST report all power consumption values in milliampere hours (mAh).

[ 8.4 /H-0-3] MUST report CPU power consumption per each process's UID. The Android

Open Source Project meets the requirement through the uid_cputime kernel module

implementation.

[ 8.4 /H-0-4] MUST make this power usage available via the adb shell dumpsys batterystats shell

command to the app developer.

[ 8.4 /H] SHOULD be attributed to the hardware component itself if unable to attribute

hardware component power usage to an application.

If Handheld device implementations include a screen or video output, they:

[ 8.4 /H-1-1] MUST honor the android.intent.action.POWER_USAGE_SUMMARY intent and

display a settings menu that shows this power usage.

2.2.5. Security Model

Handheld device implementations:

[ 9.1 /H-0-1] MUST allow third-party apps to access the usage statistics via the

android.permission.PACKAGE_USAGE_STATS permission and provide a user-accessible

mechanism to grant or revoke access to such apps in response to the

android.settings.ACTION_USAGE_ACCESS_SETTINGS intent.

Page 12 of 118