Android official documentation: (2) Application List -- 2.23 & lt; uses-configuration & gt; tag

Syntax:

<uses-configuration  android:reqFiveWayNav=["true" | "false"]  android:reqHardKeyboard=["true" | "false"]  android:reqKeyboardType=["undefined" | "nokeys" | "qwerty" | "twelvekey"]  android:reqNavigation=["undefined" | "nonav" | "dpad" | "trackball" | "wheel"]  android:reqTouchScreen=["undefined" | "notouch" | "stylus" | "finger"] />

Contained in:

<manifest>

Description:

Indicates what hardware and software features the application requires. for example, an application might specify that it requires a physical keyboardor a particle navigation device, like a trackball. the specification isused to avoid installing the application on devices where it will not work.

Note: Most apps shocould not use this manifest tag.You shoshouldAlwaysSupport input with a directional pad (d-pad) in order to assist sight-impairedusers and support devices that provide d-pad input in addition to or instead of touch. forinformation about how to support d-pad input in your app, read Enabling Focus Navigation. ifyour app absolutely cannot function without a touchscreen, then instead use<uses-feature>Tag todeclare the required touchscreen type, ranging from"android.hardware.faketouch"For basictouch-style events to more advanced touch types such"android.hardware.touchscreen.multitouch.jazzhand"For distinct input from multiple fingers.

Attributes:

android:reqFiveWayNav

Whether or not the application requires a five-way navigation control -" true"If it does, and" false"If not. A five-waycontrol is one that can move the selection up, down, right, or left, andalso provides a way of invoking the current selection. it cocould be aD-pad (directional pad), trackball, or other device.

If an application requires a directional control, but not a control of aparticular type, it can set this attribute"true"And ignorethereqNavigationAttribute. However, if it requires a participant type of directional control, it can ignorethis attribute and setreqNavigationInstead.

android:reqHardKeyboard

Whether or not the application requires a hardware keyboard -" true"If it does, and" false"If not.

android:reqKeyboardType

The type of keyboard the application requires, if any at all. this attribute does not distinguish between hardware and softwarekeyboards. if a hardware keyboard of a certain type is required, specify the type here and also set reqHardKeyboardAttributeto" true".

The value must be one of the following strings:

Value	Description
"undefined"	The application does not require a keyboard. (A keyboard requirement is not defined.) This is the default value.
"nokeys"	The application does not require a keyboard.
"qwerty"	The application requires a standard QWERTY keyboard.
"twelvekey"	The application requires a twelve-key keypad, like those on most phones-with keys for the digits from0Through9Plus star (*) And pound (#) Keys.

android:reqNavigation

The navigation device required by the application, if any. The valuemust be one of the following strings:

Value	Description
"undefined"	The application does not require any type of navigation control. (The navigation requirement is not defined.) This is the default value.
"nonav"	The application does not require a navigation control.
"dpad"	The application requires a D-pad (directional pad) for navigation.
"trackball"	The application requires a trackball for navigation.
"wheel"	The application requires a navigation wheel.

If an application requires a navigational control, but the exact type ofcontrol doesn' t matter, it can setreqFiveWayNavAttribute"true"Rather than set this one.

android:reqTouchScreen

The type of touch screen the application requires, if any at all. The value must be one of the following strings:

Value	Description
"undefined"	The application doesn't require a touch screen. (The touch screen requirement is undefined.) This is the default value.
"notouch"	The application doesn't require a touch screen.
"stylus"	The application requires a touch screen that's operated with a stylus.
"finger"	The application requires a touch screen that can be operated with a finger. Note:If some type of touch input is required for your app, you shoshould instead use<uses-feature>Tag to declare the required touchscreen type, beginning"android.hardware.faketouch"For basic touch-style events.

Introduced in:

API Level 3

See also:

• configChangesAttribute of<activity>Element

ConfigurationInfo