AGM A9 32Gb+4Gb Dual LTE [74/118] Touchscreen input

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

[C-1-1] MUST report TOUCHSCREEN_FINGER for the Configuration.touchscreen API field.

[C-1-2] MUST report the android.hardware.touchscreen and android.hardware.faketouch feature flags

If device implementations include a touchscreen that can track more than a single touch, they:

[C-2-1] MUST report the appropriate feature flags android.hardware.touchscreen.multitouch ,

android.hardware.touchscreen.multitouch.distinct , android.hardware.touchscreen.multitouch.jazzhand

corresponding to the type of the specific touchscreen on the device.

If device implementations do not include a touchscreen (and rely on a pointer device only) and meet

the fake touch requirements in section 7.2.5 , they:

[C-3-1] MUST NOT report any feature flag starting with android.hardware.touchscreen and

MUST report only android.hardware.faketouch .

7.2.5. Fake Touch Input

Fake touch interface provides a user input system that approximates a subset of touchscreen

capabilities. For example, a mouse or remote control that drives an on-screen cursor approximates

touch, but requires the user to first point or focus then click. Numerous input devices like the mouse,

trackpad, gyro-based air mouse, gyro-pointer, joystick, and multi-touch trackpad can support fake

touch interactions. Android includes the feature constant android.hardware.faketouch, which

corresponds to a high-fidelity non-touch (pointer-based) input device such as a mouse or trackpad

that can adequately emulate touch-based input (including basic gesture support), and indicates that

the device supports an emulated subset of touchscreen functionality.

If device implementations do not include a touchscreen but include another pointer input system

which they want to make available, they:

SHOULD declare support for the android.hardware.faketouch feature flag.

Page 74 of 118