am 84099f3d: Merge "Adding TV related updates." into ics-mr1

* commit '84099f3d788974169a8ea282f9413cb399d17012':
  Adding TV related updates.

docs/html/training/multiple-apks/api.jd

@@ -377,4 +377,8 @@ won’t be visible to very many devices.</p>
 <pre>
 &lt;uses-feature android:name="android.hardware.telephony" android:required="false" /&gt;
 </pre>
+<p>The <code>android.hardware.touchscreen</code> requirement is also implicitly added. If you want your APK to be visible on TVs which are non-touchscreen devices you should add the following to your manifest:</p>
+<pre>
+&lt;uses-feature android:name="android.hardware.touchscreen" android:required="false" /&gt;
+</pre>
 <p>Once you’ve completed the pre-launch checklist, upload your APKs to Google Play.  It may take a bit for the application to show up when browsing Google Play, but when it does, perform one last check.  Download the application onto any test devices you may have, to make sure that the APKs are targeting the intended devices.  Congratulations, you’re done!</p>

docs/html/training/multiple-apks/multiple.jd

@@ -473,5 +473,9 @@ will be invisible to most, if not all devices.</p>
 <pre>
 &lt;uses-feature android:name="android.hardware.telephony" android:required="false" /&gt;
 </pre>
+<p>The <code>android.hardware.touchscreen</code> requirement is also implicitly added. If you want your APK to be visible on TVs which are non-touchscreen devices you should add the following to your manifest:</p>
+<pre>
+&lt;uses-feature android:name="android.hardware.touchscreen" android:required="false" /&gt;
+</pre>
 
 <p>Once you’ve completed the pre-launch checklist, upload your APKs to Google Play.  It may take a bit for the application to show up when browsing Google Play, but when it does, perform one last check.  Download the application onto any test devices you may have to make sure that the APKs are targeting the intended devices. Congratulations, you’re done!</p>

docs/html/training/multiple-apks/screensize.jd

@@ -352,4 +352,9 @@ manifest:</p>
 <pre>
 &lt;uses-feature android:name="android.hardware.telephony" android:required="false" /&gt;
 </pre>
+<p>The <code>android.hardware.touchscreen</code> requirement is also implicitly added. If you want your APK to be visible on TVs which are non-touchscreen devices you should add the following to your manifest:</p>
+<pre>
+&lt;uses-feature android:name="android.hardware.touchscreen" android:required="false" /&gt;
+</pre>
+
 <p>Once you’ve completed the pre-launch checklist, upload your APKs to Google Play.  It may take a bit for the application to show up when browsing Google Play, but when it does, perform one last check.  Download the application onto any test devices you may have to make sure that the APKs are targeting the intended devices. Congratulations, you’re done!</p>

docs/html/training/multiple-apks/texture.jd

@@ -296,4 +296,9 @@ will be invisible to most, if not all devices.</p>
 <pre>
 &lt;uses-feature android:name="android.hardware.telephony" android:required="false" /&gt;
 </pre>
+<p>The <code>android.hardware.touchscreen</code> requirement is also implicitly added. If you want your APK to be visible on TVs which are non-touchscreen devices you should add the following to your manifest:</p>
+<pre>
+&lt;uses-feature android:name="android.hardware.touchscreen" android:required="false" /&gt;
+</pre>
+
 <p>Once you’ve completed the pre-launch checklist, upload your APKs to Google Play.  It may take a bit for the application to show up when browsing Google Play, but when it does, perform one last check.  Download the application onto any test devices you may have to make sure that the APKs are targeting the intended devices. Congratulations, you’re done!</p>