Google Play and function-based filtering (4)

Software function reference

The following table lists the software function descriptors supported by most released Android platforms. The Android: Name attribute must be used in the <uses-feature> element of the Application List to declare a single function or function.

Function	Attribute Value	Description	Note
Live Wallpaper	Android. Software. live_wallpaper	The application uses or provides live wallpapers
Sip/VoIP	Android. Software. Sip	The application must use the SIP service on the device.
	Android. Software. Sip. VoIP	Sub-function. Applications must use the SIP-based VoIP service on the device.	Declaring this sub-function implies declaring the Android. Software. Sip parent function, unless the Android: required = "false"

 

Permission required for implied functionality

In some functional constants listed above, it is valid for the application only after the corresponding API is released. For example, Android. Hardware. Bluetooth function constant is added to android2.2 (API Level 8), but the Bluetooth API it points to is added in android2.0 (API Level 5. As a result, some applications can use these Apis before being able to declare the required API functions through the <uses-feature> element.

To prevent some functions from being inadvertently valid for applications, Google Play assumes the permissions of some related hardware to specify the underlying hardware functions required by default. For example, an application that uses the Bluetooth function must apply for the Bluetooth permission in the <uses-Permission> element. For an earlier application, Google Play assumes that the permission is declared, this means that the application requires the underlying android. hardware. the Bluetooth function is used to filter applications.

The permission for the implied functional requirements listed in the following table is equivalent to those declared in the <uses-feature> element. Note that the <uses-feature> statement containing the Android: Required attribute has a higher priority than the functional requirements implied in the following table.

For any permission in the following table, you can use the <uses-feature> element with the Android: required = "false" attribute to explicitly prohibit filtering based on the implied function. For example, to disable any Filtering Based on the camera permission, you can add the following <uses-feature> element declaration to the configuration file:

<Uses-featureandroid: Name = "android. Hardware. Camera" Android: required = "false"/>

Category	Permission	Implied functional requirements
Bluetooth	Bluetooth	Android. Hardware. Bluetooth (See Special Handling for Bluetooth feature For details .)
	Bluetooth_admin	Android. Hardware. Bluetooth
Camera	Camera	Android. Hardware. CameraAnd Android. Hardware. Camera. Autofocus
Location	Access_mock_location	Android. Hardware. Location
	Access_location_extra_commands	Android. Hardware. Location
	Install_location_provider	Android. Hardware. Location
	Access_coarse_location	Android. Hardware. Location. NetworkAnd Android. Hardware. Location
	Access_fine_location	Android. Hardware. Location. GPSAnd Android. Hardware. Location
Microphone	Record_audio	Android. Hardware. Microphone
Telephony	Call_phone	Android. Hardware. Telephony
	Call_privileged	Android. Hardware. Telephony
	Modify_phone_state	Android. Hardware. Telephony
	Process_outgoing_cils	Android. Hardware. Telephony
	Read_sms	Android. Hardware. Telephony
	Receive_sms	Android. Hardware. Telephony
	Receive_mms	Android. Hardware. Telephony
	Receive_wap_push	Android. Hardware. Telephony
	Send_sms	Android. Hardware. Telephony
	Write_apn_settings	Android. Hardware. Telephony
	Write_sms	Android. Hardware. Telephony
WiFi	Access_wifi_state	Android. Hardware. WiFi
	Change_wifi_state	Android. Hardware. WiFi
	Change_wifi_multicast_state	Android. Hardware. WiFi