- Google Play Filtering
+
+ Google Play Filtering
Google Play uses the <uses-feature>
- elements declared in your app manifest to filter your app from devices
+ elements declared in your app manifest to filter your app from devices
that do not meet it's hardware and software feature requirements.
By specifying the features that your application requires, @@ -98,7 +98,7 @@ application requires.
Declared <uses-feature> elements are informational only, meaning
that the Android system itself does not check for matching feature support on
the device before installing an application. However, other services
-(such as Google Play) or applications may check your application's
+(such as Google Play) or applications may check your application's
<uses-feature> declarations as part of handling or interacting
with your application. For this reason, it's very important that you declare all of
the features (from the list below) that your application uses.
If you don't want Google Play to filter based on a specific implied
feature, you can disable that behavior. To do so, declare the feature explicitly
-in a <uses-feature> element and include an
+in a <uses-feature> element and include an
android:required="false" attribute. For example, to disable
filtering derived from the CAMERA permission, you would declare
the feature as shown below.
android.hardware.cameraandroid.hardware.type.television<uses-feature> element.
| Feature | -Attribute Value | +Attribute Value | Description | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Category | This Permission... | Implies This Feature Requirement | diff --git a/docs/html/training/training_toc.cs b/docs/html/training/training_toc.cs index 00eca7c604e48..082f5fffc63d9 100644 --- a/docs/html/training/training_toc.cs +++ b/docs/html/training/training_toc.cs @@ -978,6 +978,12 @@ include the action bar on devices running Android 2.1 or higher." description="How to build Live TV apps."> Building Live TV Apps + +Touchscreen | {@code android.hardware.touchscreen} |
|---|---|---|---|---|
| Touchscreen emulator | +{@code android.hardware.faketouch} | +|||
| Telephony | {@code android.hardware.telephony} | @@ -96,6 +99,10 @@ if (uiModeManager.getCurrentModeType() == Configuration.UI_MODE_TYPE_TELEVISION)Camera | {@code android.hardware.camera} | |
| Bluetooth | +{@code android.hardware.bluetooth} | +|||
| Near Field Communications (NFC) | {@code android.hardware.nfc} | @@ -105,11 +112,26 @@ if (uiModeManager.getCurrentModeType() == Configuration.UI_MODE_TYPE_TELEVISION){@code android.hardware.location.gps} | ||
| Microphone | +Microphone [1] | {@code android.hardware.microphone} | ||
| Sensors | +{@code android.hardware.sensor} | +
+ [1] Some TV controllers have a microphone, which is + not the same as the microphone hardware feature described here. The controller microphone is fully + supported. +
+ ++ See the + Features Reference for a complete list of features, subfeatures, and their descriptors. +
+Declaring hardware requirements for TV
@@ -131,18 +153,29 @@ if (uiModeManager.getCurrentModeType() == Configuration.UI_MODE_TYPE_TELEVISION)
<uses-feature android:name="android.hardware.touchscreen"
android:required="false"/>
+<uses-feature android:name="android.hardware.faketouch"
+ android:required="false"/>
<uses-feature android:name="android.hardware.telephony"
android:required="false"/>
<uses-feature android:name="android.hardware.camera"
android:required="false"/>
+<uses-feature android:name="android.hardware.bluetooth"
+ android:required="false"/>
<uses-feature android:name="android.hardware.nfc"
android:required="false"/>
<uses-feature android:name="android.hardware.gps"
android:required="false"/>
<uses-feature android:name="android.hardware.microphone"
android:required="false"/>
+<uses-feature android:name="android.hardware.sensor"
+ android:required="false"/>
+Note: Some features have subfeatures like {@code android.hardware.camera.front}, + as described in the + Feature Reference. Be sure to mark as {@code required="false"} any subfeatures also used in + your app.
+All apps intended for use on TV devices must declare that the touch screen feature is not required as described in Get Started with @@ -207,7 +240,7 @@ if (uiModeManager.getCurrentModeType() == Configuration.UI_MODE_TYPE_TELEVISION)
- For a complete list of permission requests that imply a hardware feature requirement, see + For a complete list of permission requests that imply a hardware feature requirement, see the {@code uses-feature} guide. If your app requests one of the features listed above, include a {@code uses-feature} @@ -246,7 +279,8 @@ if (getPackageManager().hasSystemFeature("android.hardware.touchscreen")) {
Since most TVs do not have touch screens, Android does not support touch screen interaction for TV devices. Furthermore, using a touch screen is not consistent with a viewing environment where - the user is seated 10 feet away from the display. + the user is seated 10 feet away from the display. Make sure that your UI elements and text do not + require or imply the use of a touchscreen.
diff --git a/docs/html/training/tv/start/layouts.jd b/docs/html/training/tv/start/layouts.jd index a390702d7369d..177ea7ad6cd02 100644 --- a/docs/html/training/tv/start/layouts.jd +++ b/docs/html/training/tv/start/layouts.jd @@ -16,6 +16,7 @@ trainingnavtop=true
You should also read
-
@@ -258,3 +259,17 @@ trainingnavtop=true
For more information on getting the best performance when working with images, see
Displaying Bitmaps Efficiently.
+
+
- - Surfacing Content on TV - With all the - content choices at users' fingertips, helping them find content they enjoy is almost as important - as providing that content. This training discusses how to surface your content on TV devices. + Helping Users Find Your Content on TV - + With all the content choices at users' fingertips, helping them find content they enjoy is almost + as important as providing that content. This training discusses how to surface your content on + TV devices.
- Games for TV - TV devices are a great
Provide Effective Advertising
+ +Advertising on Android TV must always be full-screen. Ads must not appear alongside or over +content. The user must be able to dismiss an advertisement with the D-pad controller. Video ads must +be dismissible within 30 seconds of their start time.
+ +Android TV does not provide a web browser. Your ads must not attempt to launch a web browser or +redirect to the Google Play Store.
+ ++ Note: You can use the {@link android.webkit.WebView} class for logins to + services like Google+ and Facebook. +
\ No newline at end of file diff --git a/docs/html/training/tv/start/start.jd b/docs/html/training/tv/start/start.jd index e3b92c6b70f03..2766e90a39a59 100644 --- a/docs/html/training/tv/start/start.jd +++ b/docs/html/training/tv/start/start.jd @@ -1,6 +1,5 @@ page.title=Get Started with TV Apps -page.tags=tv, leanback, recyclerview -helpoutsWidget=true +page.tags="leanback","recyclerview","launcher" trainingnavtop=true startpage=true @@ -145,6 +144,22 @@ startpage=true "{@docRoot}training/tv/start/layouts.html">Building TV Layouts. +Declare Leanback support
+ ++ Declare that your app uses the Leanback user interface required by Android TV. If you are developing + an app that runs on mobile (phones, wearables, tablets, etc.) as well as Android TV, set the + {@code required} attribute value to {@code false}. If you set the {@code required} attribute value + to {@code true}, your app will run only on devices that use the Leanback UI. +
+ ++<manifest> + <uses-feature android:name="android.software.leanback" + android:required="false" /> + ... +</manifest> +
Declare touchscreen not required
@@ -158,8 +173,8 @@ startpage=true
<manifest>
- <uses-feature android:name="android.hardware.touchscreen"
- android:required="false" />
+ <uses-feature android:name="android.hardware.touchscreen"
+ android:required="false" />
...
</manifest>
@@ -173,9 +188,9 @@ startpage=true
Provide a home screen banner
- An application must provide a home screen banner if it includes a Leanback launcher intent - filter. The banner is the app launch point that appears on the home screen in the apps and - games rows. Desribe the banner in the manifest as follows: + An application must provide a home screen banner for each localization if it includes a Leanback + launcher intent filter. The banner is the app launch point that appears on the home screen in the + apps and games rows. Desribe the banner in the manifest as follows:
@@ -263,9 +278,10 @@ startpage=true
TV apps that play videos and music, and let users browse for the content they want.