Lines Matching full:broadcast
30 <p>The framework does not seek to implement TV standards or regional requirements, but does make it easier for device manufacturers to meet regional digital TV broadcast standards without re-implementation. Documentation in this section might also be useful to third-party app developers who want to create custom TV Inputs.</p>
100 <p>The TV Provider maps "broadcast genre" to "canonical genre" internally. TV
101 Inputs are responsible for populating "broadcast genre" with the value in the
102 underlying broadcast standard, and the "canonical genre" field will
103 automatically be populated with the correct associated genre from <code>android.provider.TvContract.Genres</code>. For example, with broadcast standard ATSC A/65 and program with genre 0x25
104 (meaning ?Sports?), the TV Input will populate the ?broadcast genre? with the
273 broadcast apps. For example, you might use these broadcast apps to access
276 <p>See the <em>Broadcast app</em> section to learn how broadcast apps interact with the TV App.</p>
285 broadcast app.
286 <li>TV input consumes <code>KeyEvents</code> as <code>InputEvents</code> and the broadcast app is the focus and handles <code>InputEvents</code> until dismissed.
649 <h3 id="broadcast_app">Broadcast app</h3>
651 <p>Because each country has broadcast-specific requirements (MHEG, Teletext,
653 the broadcast app, for example:</p>
666 <p>Here?s how the broadcast app and TV App interact:</p>
673 activates broadcast apps.
674 <li>A broadcast app takes focus in the TV App and handles user actions.
677 <p>For voice search/recommendation, the broadcast app may support In-app search
