Xiaomi Pocophone F1 128Gb+6Gb Dual LTE [73/118] Navigation keys

Android includes support for d-pad, trackball, and wheel as mechanisms for non-touch navigation.

Device implementations:

[C-0-1] MUST report the correct value for android.content.res.Configuration.navigation .

If device implementations lack non-touch navigations, they:

[C-1-1] MUST provide a reasonable alternative user interface mechanism for the selection

and editing of text, compatible with Input Management Engines. The upstream Android

open source implementation includes a selection mechanism suitable for use with

devices that lack non-touch navigation inputs.

7.2.3. Navigation Keys

The Home , Recents , and Back functions typically provided via an interaction with a dedicated

physical button or a distinct portion of the touch screen, are essential to the Android navigation

paradigm and therefore:

[C-0-1] MUST provide the Home function.

SHOULD provide buttons for the Recents and Back function.

If the Home, Recents, or Back functions are provided, they:

[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]

((http://developer.android.com/reference/android/view/KeyEvent.html# KEYCODE_ASSIST ), 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:

Page 73 of 118