Xiaomi Redmi Note 8 Pro 64Gb+6Gb Dual LTE [79/132] Touchscreen input

[C-1-1] MUST be accessible with a single action (e.g. tap, double-click or gesture) when

any of them are accessible.

[C-1-2] MUST provide a clear indication of which single action would trigger each

function. Having a visible icon imprinted on the button, showing a software icon on the

navigation bar portion of the screen, or walking the user through a guided step-by-step

demo flow during the out-of-box setup experience are examples of such an indication.

Device implementations:

[SR] are STRONGLY RECOMMENDED to not provide the input mechanism for the Menu

function as it is deprecated in favor of action bar since Android 4.0.

If device implementations provide the Menu function, they:

[C-2-1] MUST display the action overflow button whenever the action overflow menu

popup is not empty and the action bar is visible.

[C-2-2] MUST NOT modify the position of the action overflow popup displayed by

selecting the overflow button in the action bar, but MAY render the action overflow popup

at a modified position on the screen when it is displayed by selecting the Menu function.

If device implementations do not provide the Menu function, for backwards compatibility, they: * [C-

3-1] MUST make the Menu function available to applications when targetSdkVersion is less than 10,

either by a physical button, a software key, or gestures. This Menu function should be accessible

unless hidden together with other navigation functions.

If device implementations provide the Assist function , they: [C-4-1] MUST make the Assist function

accessible with a single action (e.g. tap, double-click or gesture) when other navigation keys are

accessible. [SR] STRONGLY RECOMMENDED to use long press on HOME function as this designated

interaction.

If device implementations use a distinct portion of the screen to display the navigation keys, they:

[C-5-1] Navigation keys MUST use a distinct portion of the screen, not available to

applications, and MUST NOT obscure or otherwise interfere with the portion of the screen

available to applications.

[C-5-2] MUST make available a portion of the display to applications that meets the

requirements defined in section 7.1.1 .

[C-5-3] MUST honor the flags set by the app through the View.setSystemUiVisibility() API

method, so that this distinct portion of the screen (a.k.a. the navigation bar) is properly

hidden away as documented in the SDK.

7.2.4. Touchscreen Input

Android includes support for a variety of pointer input systems, such as touchscreens, touch pads,

and fake touch input devices. Touchscreen-based device implementations are associated with a

display such that the user has the impression of directly manipulating items on screen. Since the

user is directly touching the screen, the system does not require any additional affordances to

indicate the objects being manipulated.

Device implementations:

SHOULD have a pointer input system of some kind (either mouse-like or touch).

SHOULD support fully independently tracked pointers.

If device implementations include a touchscreen (single-touch or better), they:

Page 79 of 132