| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Version | 2024.Q2.3 | Pass | 38 | ||||||||||||||||||||||
2 | Device/Build details | Build fingerprint being tested: Use: adb shell getprop ro.build.fingerprint | Fail | 0 | ||||||||||||||||||||||
3 | Release Type | MR (Maintenance Release) | SKB/BFX_AT100/BFX-AT100:12/STTC.220724.001/15.542.50-20240509:userdebug/release-keys | N/A | 113 | |||||||||||||||||||||
4 | For more details, see: | https://docs.partner.android.com/tv/test/manual/smoke?hl=en | Review | 0 | ||||||||||||||||||||||
5 | Total | 151 | ||||||||||||||||||||||||
6 | ||||||||||||||||||||||||||
7 | Area | Lite test? | Test Name | Test Description | Test Instructions | Exclusions / Applicability | Test Result | Notes | ||||||||||||||||||
8 | Remote Control | rcu-design-approved | Design | 1) See Remote Control approval submission process 2) Enter the case number in the Notes Field for the Google approval of the remote control 3) Enter the URL to the Google approved remote control review checklist in the Notes Field 4) Verify that the remote control being tested with the DUT exactly matches what was approved by Google | Initial Releases Only. Not required for SOC reference designs. | N/A | Approval case number: Checklist URL: | |||||||||||||||||||
9 | rcu-general-navigation | General navigation | Verify: - Remote pairing procedure works (for Bluetooth capable remotes) - Device is responsive to remote control, including after long periods of inactivity. - HOME & BACK buttons and DPAD navigation works - DPAD buttons can be pressed twice within one second and two movements happen on screen. This must be tested in Bluetooth paired mode and IR mode, if supported by the remote. | N/A | ||||||||||||||||||||||
10 | rcu-apps-button | Apps button | If the optional Apps button is used, ensure it opens the Apps view/tab. | Android 8.0+ only | N/A | |||||||||||||||||||||
11 | rcu-home-button | Home button | ATV and GTV: Verify that from various places in the UI (i.e. navigate around launcher, launch apps, change input, etc), pressing the RCU Home button always brings you to the launcher UI. | N/A | ||||||||||||||||||||||
12 | rcu-long-press-on-home | Long press on Home | ATV Watson Standard Launcher: Ensure a long-press on Home button opens the Apps tab (internally this may be KEYCODE_ALL_APPS, or may be a long press of KEYCODE_HOME). GTV: Ensure a long-press on the Home button opens up the Dashboard | Android 8.0+ only, not required for operator custom launcher | N/A | |||||||||||||||||||||
13 | Yes | rcu-button-logos | Remote button logos and matching function | Verify that all buttons on the remote control work, and function according to their labeling. Note: some remote control buttons may only work during certain scenarios. For example, some buttons may only work when a Live TV APK is in the foreground, or in the case of DVR "Record" button, only when an external storage device is connected. In these cases, the relevant usage scenario should be exercised in order to validate these button functions. | Operator tier only: limited time non functional button(s) OK if proposed/accepted in remote review process Non Operator tier: must comply if not a SOC vendor reference design | Pass | ||||||||||||||||||||
14 | Yes | rcu-assistant-bt-voice-control-when-paired | Google Assistant bluetooth voice control when RCU is paired | 1: Go to setting and confirm the RCU is paired 2: Press Home button to return to the launcher 3: Press the Voice Search Assistant button 4: Verify that Google Assistant is launched and check a query such as "Search for Funny Shows" is recognized | Pass | |||||||||||||||||||||
15 | Yes | rcu-assistant-bt-voice-control-when-not-paired | Google Assistant bluetooth voice control when RCU is NOT paired. Confirms that auto pairing happens or manual pairing is prompted. | 1: Navigate to settings and confirm that the BT RCU is paired 2: If no BT RCU is paired, proceed to 3. If RCU is paired, manually un-pair the RCU via settings. If the DUT immediately displays pairing instructions after un-pairing, proceed to 4 3: Press Google Assistant button on the RCU. If the remote automatically re-pairs, then you may skip to 5. 4: If pairing instructions or places where the instructions can be found are displayed, follow those instructions and pair the remote, then press the Google Assistant button on the RCU once pairing is successfully completed. 5: Press Home button to return to the launcher 6: Verify that audio input from the remote to Google Assistant works by confirming that a query such as "Search for Funny Shows" is recognized | This test only applicable for ATV/GTV devices that ship with an embedded IR receiver and a combined Bluetooth and IR voice-enabled remote control | Pass | ||||||||||||||||||||
16 | rcu-ir-range-check | RCU IR Range Check | 1 : If the remote is Bluetooth-paired to the device, navigate to the Remotes and Accessories settings page to unpair the remote. 2: Stand 8 meters away and directly in front (0 degrees) of the TV/STB device. Point the remote straight towards the center of the TV/STB device and verify that the remote control can reliably send button presses and control the TV/STB device. 3: Remain standing 8 meters away and directly in front (0 degrees) of the device, point the remote 30 degrees (~4 meters) to the right of the center of the device and verify that the remote control can reliably send button presses. 4: Remain standing 8 meters away and directly in front (0 degrees) of the device, point the remote 30 degrees (~4 meters) to the left of the center of the device and verify that the remote control can reliably send button presses. 5 : Stand 8 meters away from the TV/STB device, 30 degrees (~4 meters) off axis to the right side of center of the TV/STB device (alternatively, TV/STB device under test can be rotated ~30 degrees to the left). Point the remote towards the center of the TV/STB device and verify that the remote control can reliably send button presses and control the TV/STB device. 6 : Stand 8 meters away from the TV/STB device, 30 degrees (~4 meters) off axis to the left side of center of the TV/STB device (alternatively, TV/STB device under test can be rotated ~30 degrees to the right). Point the remote towards the center of the TV/STB device and verify that the remote control can reliably send button presses and control the TV/STB device. | Skip if remote is Bluetooth only, no Infrared | N/A | |||||||||||||||||||||
17 | rcu-bt-range-check | RCU BT Range Check | 1 : Navigate to the Remotes and Accessories settings page to verify that the remote is paired to the device. If it is not, pair the remote to the device. 2: Stand 8 meters away and directly in front (0 degrees) of the device and verify that voice commands can reliably be sent to the device via the remote control microphone. 3: Stand 8 meters away from the device, 30 degrees (~4 meters) off axis to the right side of center and verify that voice commands can reliably be sent to the device via the remote control microphone. 4: Stand 8 meters away from the device, 30 degrees (~4 meters) off axis to the left side of center and verify that voice commands can reliably be sent to the device via the remote control microphone. | Skip if remote is Infrared only, no BT | N/A | |||||||||||||||||||||
18 | gtv-rcu-htt | GTV Remote Hold To Talk Check | 1. Verbally count to from 1 to 10 at a rate of 1 second per number. 2. Press the Assistant button on the remote control after saying "3" and release the button after saying "7": 1 2 3 <press> 4 5 6 7 <release> 8 9 10 3. Verify that the captured result is precisely "4 5 6 7". | GTV Only | N/A | |||||||||||||||||||||
19 | ||||||||||||||||||||||||||
20 | Bootup sequence and restart | boot-sequence-approved | Boot sequence review process | 1) See boot up sequence approval submission process 2) Enter the case number in the Notes Field for the Google approval of the proposed boot sequence 3) Enter the URL to the Google approved boot sequence review checklist (includes video URL) in the Notes Field 4) Verify that the boot sequence on the DUT exactly matches what was approved by Google in the video | Initial Releases Only | N/A | Approval case number: Checklist URL: | |||||||||||||||||||
21 | boot-restart-from-settings | Restart from Settings | 1) Restart device from Settings menu 2) Verify that the device reboots and functions normally after rebooting | N/A | ||||||||||||||||||||||
22 | ||||||||||||||||||||||||||
23 | Setup flow | Yes | setup-remote-pairing | Remote pairing | Bluetooth capable remote controls must be pre-paired from the factory, or the out of box Setup procedure must include a pairing sequence (with symbolic instructions or multiple languages based on device region/SKU) with the pairing sequence being the default path relative to an option to skip pairing if one is made available. | BT capable remote only | N/A | BT/IR capable | ||||||||||||||||||
24 | setup-flow-on-wifi | Setup flow on Wifi | Run through device Setup flow using a Wi-Fi connection (if supported) | Only if Wi-Fi supported | N/A | |||||||||||||||||||||
25 | setup-flow-on-ethernet | Setup flow on Ethernet | Run through device Setup flow using an Ethernet connection (if supported) | Only if Ethernet supported | N/A | |||||||||||||||||||||
26 | Yes | setup-quick-start | Quick Start | Set up device using phone/tablet, by using the Quick Start option ('Quickly set up your TV with your Android phone?' ) as shown here. | ATV: Only if Smart Setup is enabled. GTV: Not Applicable (Google Home based setup checked separately) | N/A | ||||||||||||||||||||
27 | setup-partner-screens | Partner screens ahead of Google login | 1 : Check if there are partner login before the Google login screen 2 : If Step 1 is no, mark this test as "Pass" 3 : If Step 1 is yes, mark this test as "Fail" except where specifically allowed for Operator Tier devices: https://docs.partner.android.com/tv/requirements/gtvs/android-11#a11-addl-login-screens | N/A | ||||||||||||||||||||||
28 | setup-pai-configuration | Play Auto Install (PAI) Configuration Screen | Verify Device includes a Play Auto Installs (PAI) configuration such that the Google recommended applications are presented to the user on the PAI screen of the Setup Wizard. See Figure 2 on Reference sheet for sample of PAI screen during setup which is sufficient to indicate that PAI is configured. Device MAY include additional mandatory and/or optional applications in their PAI configuration. | N/A | ||||||||||||||||||||||
29 | setup-tutorials | Tutorials | Verify all Tutorial content is appropriate for your device. Specifically Custom Launcher devices should not show the tutorial for the standard Android TV launcher | Android 8.0+ only | N/A | |||||||||||||||||||||
30 | setup-landing-screen | Landing screen after first boot | Verify user lands on the correct screen after the setup flow: - Retail devices (ATV and GTV) must land on the Android TV / Google TV launcher after first boot - Operator Tier devices with a Custom Launcher may land on a live TV channel, or Screen 0 - Operator Tier devices with the Standard Launcher may land on the launcher, or TV App. | N/A | ||||||||||||||||||||||
31 | rcu-assistant-bt-voice-control-when-not-paired | setup-flow-robustness | Setup flow robustness | Conduct robustness testing for Setup flow to ensure user can move back and forth between screens (especially to/from partner-specific extensions), without getting stuck on a given page (or blank screen). Ensure pressing back on each screen works as expected. | Pass | |||||||||||||||||||||
32 | ||||||||||||||||||||||||||
33 | Launcher Placement | launcher-app-placement-on-1st-boot | App placement on first boot | Verify out-of-the-box app placement requirements are met, according to Help Center Placement Requirements. For Android 8.0+ devices be sure to check the Apps tab as well as the Home Screen Favorites row. | ATV Standard Launcher devices only; Not Applicable for GTV devices | N/A | ||||||||||||||||||||
34 | launcher-channel-placement-on-1st-boot | Channel placement on first boot | Verify out-of-the-box Home screen Channel placement requirements are met, according to Help Center Placement Requirements. Note: Play Movies & TV channel placement after Setup not required to be verified. | Android 8.0+ only ATV Standard Launcher devices only; Not Applicable for GTV devices | N/A | |||||||||||||||||||||
35 | ||||||||||||||||||||||||||
36 | Shop Tab | Yes | shoptab-play-trailer | Play Trailer | Verify trailer can be played. Check A/V sync. | GTV, Custom Launchers: Not Applicable | N/A | Custom Launcher | ||||||||||||||||||
37 | Yes | shoptab-play-drm | Play DRMd HD and (and UHD if supported) movies | Verify DRM protected movies (paid content) by purchasing content, ensuring HD and UHD playback, and correct A/V sync for stereo and surround content. | UHD content n/a for FHD devices Not applicable for custom launchers GTV, Custom Launchers: Not Applicable | N/A | Custom Launcher | |||||||||||||||||||
38 | Yes | shoptab-general-usage | General usage together with launcher interaction, recommendations, power states, etc. | Verify: - Movies can be purchased/rented. - HD, UHD content can be purchased/played | UHD content n/a for FHD devices Not applicable for custom launchers GTV, Custom Launchers: Not Applicable | N/A | Custom Launcher | |||||||||||||||||||
39 | Yes | shoptab-power-standby-on-off | Power Standby On/Off test | 1 : Open the Shop tab and play any asset 2 : Put device into standby mode by pressing the power button 3 : Wait a few seconds (less than 30 seconds), then resume from standby mode by pressing the power button again 4 : Verify that Shop tab with the previously playing asset is in the foreground and is paused and requires pressing Play once to resume playback. 5 : If device doesn't resume to Shop tab, verify it resumes to an alternative allowed location, per the Help Center boot resume behavior table. | Not applicable for custom launchers GTV, Custom Launchers: Not Applicable | N/A | Custom Launcher | |||||||||||||||||||
40 | ||||||||||||||||||||||||||
41 | Play Games | Yes | pg-general-usage | General usage | Verify account login, games can be launched. | Pass | ||||||||||||||||||||
42 | ||||||||||||||||||||||||||
43 | Search/Assistant | Yes | sa-recorded-ga-search-query-1 | Verification of the recorded GA Search Query #1 | Step 1: Press Home button Step 2: Press Google Assistant button on RCU Step 3: Query: “What time is it" Step 4: Verify "What time is it" is correctly displayed on the GA window | Pass | ||||||||||||||||||||
44 | Yes | sa-recorded-ga-search-query-2 | Verification of the recorded GA Search Query #2 | 1: Press the Google Assistant button on RCU 2: Query: “Who am I talking to?" 3: Verify that a response that begins with "I'm your Google Assistant." is correctly displayed and spoken 4: Navigate to "Search" on the home launcher 5: Type the text input “Who am I talking to?" 6: Verify that a response that begins with "I'm your Google Assistant." is correctly displayed and spoken | Steps 1-3: Always Mandatory Steps 4-6: ATV Standard launcher or GTV : Mandatory Operator custom launcher: Only applicable when GA icon is present on launcher | Pass | Step 4-6: is not performed on custom launcher. | |||||||||||||||||||
45 | Yes | sa-recorded-ga-search-query-3 | Verification of the recorded GA Search Query #3 | 1: Press Home button 2: Press Google Assistant button on RCU 3: Query: “action movies" 4: Verify "Search results page with multiple rows of results should be correctly displayed on the GA window" | Pass | |||||||||||||||||||||
46 | Yes | sa-voice-search-in-launcher | Voice Search selected in launcher | Use D-pad to select Voice Search ( / Assistant) icon (if present), then OK to activate. Verify voice works. Query: "Where is the nearest Library" or "What is a Solar System" Note: This is ensuring the microphone can be activated from the Android TV device, without using the dedicated Mic button on the Remote control | Standard Watson launcher : Mandatory Operator custom launcher: Only applicable when the icon is available GoogleTV: Not Applicable | N/A | not performed on custom launcher. | |||||||||||||||||||
47 | sa-voice-search-in-play-store-on-screen-icon | Voice search in Play Store, using on-screen search icon | 1 : Launch Play Store 2 : Click search icon on-screen within Play Store 3 : Query: “Search for $APP_NAME", where $APP_NAME is any app supported on the device 4 : Verify the Play Store results are exclusively displayed | N/A | ||||||||||||||||||||||
48 | sa-voice-search-in-yt-on-screen-icon | Voice search in YouTube, using on-screen search icon | 1 : Launch YouTube 2 : Click search icon on-screen within YouTube 3 : Click Voice Search Icon 4 : Query: "Search for Discovery Movies" 5 : Verify the YouTube results are exclusively displayed | N/A | ||||||||||||||||||||||
49 | Yes | sa-voice-search-over-playback-yt | Voice search over Video playback - YouTube | 1 : Launch YouTube 2 : Play the "KUSHIRO Hokkaido Japan" (video ID CNeakmoER7Q) YouTube video with max resolution supported by the device (2K, 4K,or 8K) 3 : Submit the voice command "Search for Kids shows" and verify that voice search works and video playback is interrupted. 4 : Press Back button on remote control 5 : Verify that playback of the YouTube video can restart, either automatically (after pressing Back) or by pressing OK or Play. | Pass | |||||||||||||||||||||
50 | sa-device-control | Voice based device control | Using the Google Assistant button on the RCU, verify that the following device control commands function correctly. Note that for non panel TV devices, you may need to enable CEC function in settings before running this test. 1. Turn Off TV 2. Volume Up 3. Volume Down 4. Mute 5. Panel TV only: Switch to HDMI X (for each of the HDMI inputs available on the TV) | Skip and mark NA if "adb shell getprop ro.hdmi.device_type" contains the value '4'. | N/A | |||||||||||||||||||||
51 | sa-g-icon-in-settings | G icon in settings | Verify if there is a single "Google Assistant" entry in Settings with a monochrome Google G icon | Not Applicable for GTV Devices | N/A | |||||||||||||||||||||
52 | ||||||||||||||||||||||||||
53 | Keyboard search | Yes | keyboard-search-in-launcher | Keyboard search in launcher | If Launcher has a keyboard search affordance, select using dpad and verify keyboard Search UI is used. | ATV Standard launcher and GTV: Mandatory Operator Custom launcher: N/A if custom launcher does not provide keyboard based search | N/A | Operator Customer launcher, not implemented keyboard search | ||||||||||||||||||
54 | ||||||||||||||||||||||||||
55 | Voice actions | voice-actions-natral-language | Verify Voice actions with standard remote and natural language | 1. Press "Home" Button 2. Query: "Start YouTube." 3 : Verify the YouTube is successfully launched | N/A | |||||||||||||||||||||
56 | voice-actions-fixed-grammer | Verify Voice actions with standard remote and fixed grammer | 1. Press "Home" Button on RCU 2. Query: "Open YouTube." 3. Verify the YouTube is successfully launched 4. Press "Home" Button on RCU 5. Query: "Change input to HDMI1." 6. Verify the input source is changed to HDMI1 | Step 4-6 are only needed for DUT with HDMI inputs | N/A | |||||||||||||||||||||
57 | 5 | |||||||||||||||||||||||||
58 | Companion app These tests require installing the Google TV mobile phone app in order to be run: https://play.google.com/store/apps/details?id=com.google.android.videos | Yes | companion-via-network | Google TV phone app virtual remote over network | 1. Open the Google TV app on an Android smart phone. The phone must be on the same local network that the DUT is. 2. Press "Select a device" in the Google TV app 3. Verify that the DUT shows up as a device which can be selected 4. Connect to the DUT with the Google TV virtual remote 5. Verify that D-pad navigation, Home, Back, Volume Mute, Up, and Down work 6. Verify that you can use Google Assistant to send a voice command via the phone app 7. Verify that you can alternate between D-pad navigation with Google TV app and DUT remote control successfully 8. Verify that you can alternate between Google TV app assistant voice commands and the DUT remote control assistant voice commands successfully 9. Verify that, while YouTube is in foreground, voice search using the Google TV app mic function invokes the Google Assistant rather than YouTube's in-app search. | Pass | ||||||||||||||||||||
59 | ||||||||||||||||||||||||||
60 | Accessories | Yes | acc-pair-game-controller | Pair game controller | Use Settings -> Remote & accessories -> Add accessory to pair the game controller. Ensure successfully paired. Options for the game controller to use are: Sony DualShock 4 V2, Microsoft Xbox Wireless Controller, or Asus Nexus Player controller. Note: Asus Nexus Player controller will be removed from this list in a future update. Please use the Sony or Microsoft options listed above and report issues if any are found. | Pass | ||||||||||||||||||||
61 | acc-launcher-nav-with-gc | Navigate launcher with game controller | 1: Open Settings app. 2: Verify that using only the game controller, you can press Home to go to the launcher, then navigate around the Home Screen | N/A | ||||||||||||||||||||||
62 | acc-play-games-with-gc | Play games with game controller | Play a game downloaded from the Play Store that uses a paired game controller and verify that all buttons on the controller work as expected by the game. Any game can be used to verify this, but some possible options are listed here. Some games are not available on some devices, but find a game that is available and verify that all game controller buttons work. Possible examples (can use other games as well): - Crossy Road - Real Racing 3 - Asphalt 8 | N/A | ||||||||||||||||||||||
63 | acc-bt-audio | Bluetooth audio device support | 1. Use "adb shell dumpsys bluetooth_manager|grep Profile" 2. If "Profile: A2dpService" appears in the output, then proceed with the rest of this test. If it does not exist, then mark this test as "N/A". 3. Pair a Bluetooth audio device to the DUT. Confirm that pairing is successful. 4. Launch YouTube and play video ID ucZl6vQ_8Uo "Audio Video Sync Test". 5. Verify that audio is in sync with video to within + or - 0.3 seconds. 5. Adjust volume up and down using the Bluetooth audio device controls. Confirm that volume control works. 6. Pause and Play the asset using the Bluetooth audio device controls. Confirm that play/pause control works. 7. Press Next and Previous buttons on the Bluetooth audio device controls. Confirm that next/previous changes to a new video or rewinds the current video. | N/A | ||||||||||||||||||||||
64 | acc-bt-audio-re-pair | Bluetooth audio device previously paired device test | 1. Use "adb shell dumpsys bluetooth_manager|grep Profile" 2. If "Profile: A2dpService" appears in the output, then proceed with the rest of this test. If it does not exist, then mark this test as "N/A". 3. Pair a Bluetooth audio device to the DUT. Confirm that pairing is successful. 4. Start playing this YouTube video and verify sound coming from the paired Bluetooth audio device. 5. Turn off the paired Bluetooth audio device. Verify that either playback is paused, or playback continues with audio switching to the default audio output on the DUT. 6. Turn on the previously paired Bluetooth audio device. Verify that the device automatically reconnects to the DUT. 7. Start playing this YouTube video and verify sound coming from the paired Bluetooth audio device. 8. Walk with the paired Bluetooth audio device to go out of range from the DUT, or put it in a Faraday cage. Verify that the DUT automatically switches to play audio out of the default audio output. 9. Walk with the paired Bluetooth audio device to come back into range of the DUT. Verify that audio playback comes back to the headset and verify that audio is in sync with video to within + or - 0.3 seconds. | N/A | ||||||||||||||||||||||
65 | acc-bt-multi-device | Bluetooth multi device test | 1. Use "adb shell dumpsys bluetooth_manager|grep Profile" 2. If "Profile: A2dpService" appears in the output, then include a bluetooth audio device in the steps below. If "Profile: A2dpService" does not appear in the output then do not include a bluetooth audio device in the steps below. 3. Pair a Bluetooth audio device (headset or speaker), a Bluetooth game controller, and the devices' Bluetooth remote control (assuming device comes with a BT remote). 4. Interleave button press inputs between all 3 paired devices. 5. Verify that there are no audio artifacts in the Bluetooth audio playback. 6. Verify that there are no dropped or delayed inputs from RCU, headset/speaker, or game controller. | N/A | ||||||||||||||||||||||
66 | ||||||||||||||||||||||||||
67 | Partner Live TV app These tests are meant to exercise the "TV App", which is the application providing the user viewing environment for live TV, and/or an Operator's PayTV service. Only required if a Partner Live TV APP is either pre-bundled or downloaded via PAI | Yes | plivetv-view-nav-channels | Launch Partner Live TV app and view and navigate available TV channels | Basic test of partner TV service. Note: This depends on access to required service, and may not be possible in all locations. Where possible, tester should use a broadcast signal generator (i.e. DekTec) to generate a broadcast test signal. | Pass | ||||||||||||||||||||
68 | Yes | plivetv-display-launcher | Activate Launcher from Partner Live TV app | With the partner Live TV app in the foreground, press remote control Home key, and ensure launcher is displayed promptly | Pass | |||||||||||||||||||||
69 | plivetv-search-from-rcu | Search Partner Live TV app content with On-Device Search API | 1. If the partner Live TV app does not implement on device search via the On-Device Search API, then mark this test as N/A. If it does implement on device search then proceed to step 2. 2. Check that the partner Live TV app content is searchable as intended by searching for content, verifying that Partner Live TV App results are provided, and are correctly prioritized. | Only applicable if partner live TV app uses the On-Device Search API to surface content to Assistant/Search. | N/A | |||||||||||||||||||||
70 | plivetv-check-for-gtvs-apps | Ensure GTVS apps are not included in Partner Live TV app | Ensure GTVS apps are not included as launchable links in the Partner Live TV App (example: a YouTube app icon to launch the YouTube app), unless the device also has a Custom Launcher. Details in the 'TV App' section here: https://docs.partner.android.com/tv/requirements/gtvs/android-11?hl=en#a11-tv-app Note: Deep links to specific content (including trailers) in GTVS apps are allowed (example: to a specific YouTube or Play Movies video). | Not Applicable for Operator Custom Launchers | N/A | |||||||||||||||||||||
71 | plivetv-publish-channel-to-home | Ensure Partner Live TV app publishes at least one Channel to Home Screen | Ensure [non-operator] TV Apps publish at least one row of content ("Channel") onto the Home Screen, filling the row, and included in the out-of-the-box Home Screen channels list. Ref: https://docs.partner.android.com/tv/requirements/gtvs/android-11 | Not required for Operator Tier and GTV devices | N/A | |||||||||||||||||||||
72 | ||||||||||||||||||||||||||
73 | Custom Launchers | c-launcher-spec-check | Verify against Custom Launcher specification | Verify specification requirements in https://docs.partner.android.com/tv/build/operator/launcher-custom/reqs?hl=en Use the test guidance in https://docs.partner.android.com/tv/build/operator/launcher-custom/dev-test-update?hl=en Note: More comprehensive steps are in progress | Custom Launcher devices only; Not Applicable for ATV Watson or GTV | N/A | ||||||||||||||||||||
74 | c-launcher-approved | Custom Launcher review process | 1) See custom launcher approval submission process 2) Enter the case number in the Notes Field for the Google approval of the proposed custom launcher 3) Enter the URL to the Google approved custom launcher review checklist in the Notes Field 4) Verify that the custom launcher behavior on the DUT exactly matches what the responses entered on the approved custom launcher review checklist | Custom Launcher devices only; Not Applicable for ATV Watson or GTV Only Required for Initial Releases or When Customer Launcher Design Change | N/A | Approval case number: Checklist URL: | ||||||||||||||||||||
75 | Yes | c-launcher-apps-view | All Apps view on first boot | Verify the out-of-the-box ordering of the Apps on All Apps view met the requirement which is 1. Play Store, 2. Play Movies & TV, 3. YouTube, 4. YouTube Music, and 5. Play Games. Slot 2 and 3 may be used by the operator under 2 conditions: - MUST have Apps list directly on Screen 0 with no higher prominence Featured Apps list - MUST have the remaining 3 Google apps immediately following slot 2 and 3. (https://docs.partner.android.com/tv/build/operator/launcher-custom/reqs?hl=en) | Custom Launcher devices only; Not Applicable for ATV Watson or GTV | Pass | ||||||||||||||||||||
76 | c-launcher-notification-widget | Notification widget and panel | Verify custom launcher reqiurement 2.5 Notifications in https://docs.partner.android.com/tv/build/operator/launcher-custom/reqs?hl=en | Custom Launcher devices only; Not Applicable for ATV Watson or GTV | N/A | |||||||||||||||||||||
77 | c-launcher-offline-functionality | Offline functionality for App list | Verify custom launcher requirement 2.8 Offline functionality and service deprecation in https://docs.partner.android.com/tv/build/operator/launcher-custom/reqs?hl=en 1. Disconnect the network 2. Re-boot the device w/o network configuration 3. If the launcher is available, verify if you can access the Apps area and confirm you have access to installed Apps and Games 4. Verify you can access Network Settings to reconfigure the network (regardless of whether the main launcher is available) | Custom Launcher devices only; Not Applicable for ATV Watson or GTV | N/A | |||||||||||||||||||||
78 | Yes | c-launcher-notification-indicator-updates | Dynamic notification change | Verify the notification indicator is dynamically changed (i.e connect/disconnect USB stick, connect/disconnect ETH cable or Wi-Fi, Google account log in/out, etc) | Standard and Custom Launcher devices only; Not Applicable for GTV | Pass | ||||||||||||||||||||
79 | ||||||||||||||||||||||||||
80 | Cast | Yes | cast-mirror-screen | Screen | Verify you can mirror the screen from an Android phone device | Pass | ||||||||||||||||||||
81 | Yes | cast-yt-free-content | YouTube - free content | Verify you can Cast free content from YouTube. Verify A/V sync Note: YouTube uses a different connection mechanism from other apps, so it's important to test a variety of apps | Pass | |||||||||||||||||||||
82 | Yes | cast-yt-paid-content | YouTube - paid content | Verify you can Cast paid content from YouTube. Verify A/V sync Note: YouTube uses a different connection mechanism from other apps, so it's important to test a variety of apps | Pass | |||||||||||||||||||||
83 | cast-photos | Photos | Verify Casting from the Google Photos app | N/A | ||||||||||||||||||||||
84 | cast-vimeo | Casting from a Chrome tab on your laptop - Vimeo ( https://vimeo.com/ ) | Go to https://vimeo.com/ from chrome tab on your laptop. Sign-in, then go to "Watch" -> "Staff picks" and play a video . Click the 3 vertical dots on the top right corner of the browser and select cast. Choose the correct device from the list to cast. Verify Casting Vimeo in Chrome tab. Verify A/V sync. Note: This is to test chrome tab and VP8 codec functionality | N/A | ||||||||||||||||||||||
85 | Yes | cast-test-interactions | Casting interactions with launcher etc. (Recommend to use YouTube) | Verify switching from Cast to other use-cases: - Press Home while Casting, and ensure launcher opens and Casting stops. - Verify switching to other built-in apps with dedicated Remote Control buttons (such as the live TV service). - Verify a brief switching between apps will not cause any crash or unusual behavior on the Android TV side. | Pass | |||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | Standby etc | Yes | standby-resume | Resume from standby | 1 : Launch any application 2 : Put device into standby mode by pressing the power button 3 : Wait at least 30 seconds, then resume from standby mode by pressing the power button again 4 : Verify the device resumes per the table https://docs.partner.android.com/tv/requirements/gtvs/android-12#a12-boot-resume-behavior 5 : Press Home button 6 : Put device into standby mode by pressing the power button 7 : Wait a few seconds, then resume from standby mode by pressing the power button again 8 : Verify the devices resumes to the Android TV launcher 9: If not, verify it resumes to an alternative allowed location, per the table https://docs.partner.android.com/tv/requirements/gtvs/android-12#a12-boot-resume-behavior | Pass | ||||||||||||||||||||
88 | Yes | standby-dreams | Dreams | 1. Leave the device in the inactivity mode 2. Verify the Dreams screensaver is displayed as the default screensaver 3. Verify the device resumes correctly after long and short periods of Dreams after pressing the HOME button | Pass | |||||||||||||||||||||
89 | Yes | standby-wake-on-cast | Wake on cast | Verify wake-on-cast works when device is in standby. Verify after two hours As described on https://docs.partner.android.com/tv/build/platform/features/wake-on-packet?hl=en, in suspend mode, the device’s CPU is in an idle state, but the Wi-Fi, WLAN, ethernet, and Bluetooth MUST remain active. | Pass | wake on cast (2시간 방치) | ||||||||||||||||||||
90 | Yes | standby-wake-up-from-rcu | Power off/on with remote | Verify that device wakes up from remote after two hours | Pass | 2시간 방치 후 확인 | ||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | Audio | Yes | audio-verify-output | Audio output | Verify audio output. For panel TVs or other devices with built-in speakers, this means verifying the audio coming from the built in speakers while operating the device. For STBs or other devices without built-in speakers, this means verifying the audio coming from an external device (example: AVR, panel TV) connected via HDMI. | Pass | ||||||||||||||||||||
93 | Yes | audio-volume-control | Volume control | 1. Use "adb shell dumpsys audio | grep Fixed" 2. If "mUseFixedVolume=true" appears in the output, then mark the test N/A. If "mUseFixedVolume=false" appears in the output, then proceed to Step 3. 3. Verify volume control works to increase or decrease volume output by the device - or the connected audio output device via HDMI-CEC (if supported by remote control), including mute. | Only applicable for Android 9 (P) and later n/a for fixed volume devices | Pass | mUseFixedVolume=false mFixedVolumeDevices=0x1000,0x800,0x200000,0x40000,0x40001 | |||||||||||||||||||
94 | audio-volume-alignment | Volume alignment | Verify that volume is consistent across use-cases (specifically, ensure Live TV volume aligns with other apps such as YouTube) | N/A | ||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | HDMI CEC | hdmi-cec-nav-connected-tv-from-stb | Navigation from connected TV | (STB and OTT): Ensure device can be controlled using TV remote control for D-pad navigation, etc. | n/a for panel TVs | N/A | ||||||||||||||||||||
97 | hdmi-cec-nav-connected-stb-from-tv | Control of connected STB/OTT | (TV only): Ensure connected devices can be controlled using TV remote for D-pad navigation etc. | Panel TVs only | N/A | |||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | HDMI ARC | hdmi-arc-tv-to-receiver | Connect TV to Audio Receiver | Ensure audio routes to AVR when connected via ARC supported HDMI input, even when using other input sources (HDMI1, HDMI2, etc) | Only Required for Panel TV devices with an HDMI input with ARC support | N/A | ||||||||||||||||||||
100 | hdmi-arc-playback-movies-5-1-audio | Play content with Surround Audio | Play content from YouTube. Ensure all audio channels are played through all the speakers in Audio Video Receiver (Audio Amplifier) correctly. | Only Required for Panel TV devices with an HDMI input with ARC support | N/A | |||||||||||||||||||||