1 <?xml version="1.0" encoding="utf-8"?> 2 <!-- Copyright (C) 2010 The Android Open Source Project 3 4 Licensed under the Apache License, Version 2.0 (the "License"); 5 you may not use this file except in compliance with the License. 6 You may obtain a copy of the License at 7 8 http://www.apache.org/licenses/LICENSE-2.0 9 10 Unless required by applicable law or agreed to in writing, software 11 distributed under the License is distributed on an "AS IS" BASIS, 12 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 13 See the License for the specific language governing permissions and 14 limitations under the License. 15 --> 16 <resources> 17 <string name="app_name">CTS Verifier</string> 18 19 <string name="title_version">CTS Verifier %1$s</string> 20 21 <string name="pass_button_text">Pass</string> 22 <string name="info_button_text">Info</string> 23 <string name="fail_button_text">Fail</string> 24 <string name="next_button_text">Next</string> 25 <string name="go_button_text">Go</string> 26 27 <!-- Strings for TestListActivity --> 28 <string name="test_category_audio">Audio</string> 29 <string name="test_category_camera">Camera</string> 30 <string name="test_category_car">Car</string> 31 <string name="test_category_device_admin">Device Administration</string> 32 <string name="test_category_hardware">Hardware</string> 33 <string name="test_category_networking">Networking</string> 34 <string name="test_category_sensors">Sensors</string> 35 <string name="test_category_location">Location</string> 36 <string name="test_category_security">Security</string> 37 <string name="test_category_streaming">Streaming</string> 38 <string name="test_category_features">Features</string> 39 <string name="test_category_deskclock">Clock</string> 40 <string name="test_category_jobscheduler">Job Scheduler</string> 41 <string name="test_category_tv">TV</string> 42 <string name="test_category_other">Other</string> 43 <string name="clear">Clear</string> 44 <string name="test_results_cleared">Test results cleared.</string> 45 <string name="view">View</string> 46 <string name="test_results_error">Couldn\'t create test results report.</string> 47 <string name="runtime_permissions_error">Cannot continue. Please grant runtime permissions</string> 48 <string name="export">Export</string> 49 <string name="no_storage">Cannot save report to external storage, see log for details.</string> 50 <string name="report_saved">Report saved to: %s</string> 51 52 <!-- Strings for ReportViewerActivity --> 53 <string name="report_viewer">Report Viewer</string> 54 55 <!-- Strings for BackupTestActivity --> 56 <string name="backup_test">Data Backup Test</string> 57 <string name="backup_info">This test checks that data backup and automatic restore works 58 properly. The test activity lists some preferences and files that are backed up and 59 restored by the CTS Verifier. If backup and restore is working properly, these values 60 should be restored after running the backup manager, uninstalling the app, and reinstalling 61 the CTS Verifier. 62 \n\nPress the \"Generate Test Data\" to populate these values 63 and then follow the on screen instructions to finish the test. 64 </string> 65 <string name="bu_preferences">Preferences</string> 66 <string name="bu_files">Files</string> 67 <string name="bu_loading">Loading...</string> 68 <string name="bu_generate">Generate Test Data</string> 69 <string name="bu_generate_error">Error occurred while generating test data...</string> 70 <string name="bu_instructions">Random values for the preferences and files have been saved. 71 \n\nFollow the instructions below to check that the data backup and restore works: 72 \n\n1. Make sure backup and automatic restore are enabled in settings. Depending on the 73 backup transport supported by the device you may need to do additional steps. For instance 74 you may need to set a Google account as the backup account for the device. If you cannot 75 find the corresponding setting options on your device, run \"adb shell bmgr enable true\" 76 to enable the backup manager. You can check its status by executing \"adb shell bmgr 77 enabled\". 78 \n\n2. Run the backup manager: adb shell bmgr run 79 \n\n3. Uninstall the program: adb uninstall com.android.cts.verifier 80 \n\n4. Reinstall the CTS Verifier and verify that the values are still the same. 81 </string> 82 <string name="bu_settings">Settings</string> 83 84 <!-- Strings for Device Administration tests --> 85 <string name="da_policy_serialization_test">Policy Serialization Test</string> 86 <string name="da_policy_serialization_info">This test checks that a device policy is properly 87 saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create 88 a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the 89 device and verify that all rows in the policy list are green. Red items indicate policy 90 settings that were not loaded properly. 91 </string> 92 <string name="car_dock_test">Car Dock Test</string> 93 <string name="car_dock_test_desc">This test ensures that car mode opens the app associated with 94 car dock when going into car mode.\n\n 95 Click on "Enable Car Mode" to start the test. Clicking on the button will either bring up a 96 disambiguation dialog asking which app to open or immediately open the CAR_DOCK application. 97 Select the "CTS Verifier" app and then "Always" if the dialog pops up. 98 This will open the CAR_DOCK application.\n\n 99 In the CAR_DOCK application, press the home button, which will enable the pass button if the 100 framework correctly tries to open the CAR_DOCK app again.</string> 101 <string name="car_mode_enable">Enable Car Mode</string> 102 <string name="car_dock_activity_text">Press the Home button</string> 103 <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device 104 policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your 105 device and return to this test in the CTS Verifier. 106 </string> 107 <string name="da_generate_policy">Generate Policy</string> 108 <string name="da_apply_policy">Apply Policy</string> 109 <string name="da_random_policy">Random policy generated.</string> 110 <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string> 111 <string name="da_password_quality">Password Quality</string> 112 <string name="da_password_quality_alphabetic">Alphabetic</string> 113 <string name="da_password_quality_alphanumeric">Alphanumeric</string> 114 <string name="da_password_quality_numeric">Numeric</string> 115 <string name="da_password_quality_something">Something</string> 116 <string name="da_password_minimum_length">Minimum Password Length</string> 117 <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string> 118 <string name="da_maximum_time_to_lock">Maximum Time to Lock</string> 119 <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string> 120 121 <string name="da_screen_lock_test">Screen Lock Test</string> 122 <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow 123 method immediately locks the screen. It should lock the screen immediately despite any 124 settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen. 125 Your screen should be locked and require the password to be entered. 126 </string> 127 <string name="da_force_lock">Force Lock</string> 128 <string name="da_lock_success">It appears the screen was locked successfully!</string> 129 <string name="da_lock_error">It does not look like the screen was locked...</string> 130 131 <!-- Strings for lock bound keys test --> 132 <string name="sec_lock_bound_key_test">Lock Bound Keys Test</string> 133 <string name="sec_lock_bound_key_test_info"> 134 This test ensures that Keystore cryptographic keys that are bound to lock screen authentication 135 are unusable without a recent enough authentication. You need to set up a screen lock in order to 136 complete this test. If available, this test should be run by using fingerprint authentication 137 as well as PIN/pattern/password authentication. 138 </string> 139 <string name="sec_fingerprint_bound_key_test">Fingerprint Bound Keys Test</string> 140 <string name="sec_fingerprint_bound_key_test_info"> 141 This test ensures that Keystore cryptographic keys that are bound to fingerprint authentication 142 are unusable without an authentication. You need to set up a fingerprint order to 143 complete this test. 144 </string> 145 <string name="sec_fp_dialog_message">Authenticate now with fingerprint</string> 146 <string name="sec_fp_auth_failed">Authentication failed</string> 147 <string name="sec_start_test">Start Test</string> 148 149 <!-- Strings for BluetoothActivity --> 150 <string name="bluetooth_test">Bluetooth Test</string> 151 <string name="bluetooth_test_info">The Bluetooth Control tests check whether or not the device 152 can disable and enable Bluetooth properly.\n\nThe Device Communication tests require two 153 devices to pair and exchange messages. The two devices must be: 154 \n\n1. a candidate device implementation running the software build to be tested 155 \n\n2. a separate device implementation already known to be compatible</string> 156 157 <string name="bt_control">Bluetooth Control</string> 158 <string name="bt_device_communication">Device Communication</string> 159 <string name="bt_le">Bluetooth Low Energy</string> 160 161 <string name="bt_toggle_bluetooth">Toggle Bluetooth</string> 162 <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string> 163 <string name="bt_enable_bluetooth">Enable Bluetooth</string> 164 <string name="bt_disable_bluetooth">Disable Bluetooth</string> 165 <string name="bt_disabling">Disabling Bluetooth...</string> 166 <string name="bt_disabling_error">Could not disable Bluetooth...</string> 167 168 <string name="bt_connection_access_server">Connection Access Server</string> 169 <string name="bt_connection_access_client">Connection Access Client</string> 170 <string name="bt_connection_access_server_info"> 171 Start the CTS Verifier on another device, start the Bluetooth test, and choose 172 \"Connection Access Client\" to setup the test. 173 \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together 174 using the \"Make Discoverable\" and \"Pick Server\" buttons. 175 \n\nA connection access request should appear on the server and enable the pass button. 176 </string> 177 <string name="bt_connection_access_client_info"> 178 Start the CTS Verifier on another device, start the Bluetooth test, and choose 179 \"Connection Access Server\" to complete the test. 180 \n\nMake the device acting as the server discoverable and connect to it via the 181 \"Pick Server\" button. Check that the server displays the connection access request 182 dialog. The client device does not need to do anything else. 183 </string> 184 <string name="bt_ca_dialog">Was the connection access request dialog shown?</string> 185 <string name="bt_ca_tips"> 186 Tap the \"Bluetooth Settings\" button and check that both devices are not paired 187 before running the test. 188 \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth 189 devices together and start the test. 190 </string> 191 192 <string name="bt_secure_server">Secure Server</string> 193 <string name="bt_secure_server_instructions">Start the CTS Verifier on another device, start the Bluetooth test, and choose \"Secure Client\" to complete the test.</string> 194 <string name="bt_insecure_server">Insecure Server</string> 195 <string name="bt_insecure_server_instructions">Start the CTS Verifier on another device, start the Bluetooth test, and choose \"Insecure Client\" to complete the test.</string> 196 <string name="bt_waiting">Waiting for client...</string> 197 <string name="bt_listening">Listening...</string> 198 <string name="bt_connecting">Connecting...</string> 199 <string name="bt_connected">Connected</string> 200 <string name="bt_received_messages">Received Messages</string> 201 <string name="bt_sent_messages">Sent Messages</string> 202 <string name="bt_no_messages">No messages</string> 203 <string name="bt_make_discoverable">Make Discoverable</string> 204 <string name="bt_pick_server">Pick Server</string> 205 <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string> 206 <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string> 207 208 <string name="bt_secure_client">Secure Client</string> 209 <string name="bt_insecure_client">Insecure Client</string> 210 211 <string name="bt_device_picker">Device Picker</string> 212 <string name="bt_paired_devices">Paired Devices</string> 213 <string name="bt_new_devices">New Devices</string> 214 <string name="bt_no_devices">No devices</string> 215 <string name="bt_scan">Scan for Devices</string> 216 <string name="bt_scanning">Scanning...</string> 217 <string name="bt_unpair">Device must be unpaired via Bluetooth settings before completing the test.\n\nUnpair the device in settings, make the server discoverable, and rescan to pick this device.</string> 218 <string name="bt_settings">Bluetooth Settings</string> 219 220 <!-- BLE client side strings --> 221 <string name="ble_client_service_name">Bluetooth LE GATT Client Handler Service</string> 222 <string name="ble_client_test_name">BLE Client Test</string> 223 <string name="ble_client_connect_name">BLE Client Connect</string> 224 <string name="ble_discover_service_name">BLE Discover Service</string> 225 <string name="ble_read_characteristic_name">BLE Read Characteristic</string> 226 <string name="ble_write_characteristic_name">BLE Write Characteristic</string> 227 <string name="ble_reliable_write_name">BLE Reliable Write</string> 228 <string name="ble_notify_characteristic_name">BLE Notify Characteristic</string> 229 <string name="ble_read_descriptor_name">BLE Read Descriptor</string> 230 <string name="ble_write_descriptor_name">BLE Write Descriptor</string> 231 <string name="ble_read_rssi_name">BLE Read RSSI</string> 232 <string name="ble_client_disconnect_name">BLE Client Disconnect</string> 233 <string name="ble_client_test_info">The BLE test must be done simultaneously on two devices. This device is the client. All tests listed here must be done in order.</string> 234 <string name="ble_client_send_connect_info">Type in the Bluetooth address of the remote device to connect to, and verify that the devices are connected.</string> 235 <string name="ble_discover_service_info">Verify that the service is discovered when you press the "Discover Service" button.</string> 236 <string name="ble_read_write_info">Write values to and read values from the server to verify that the write and read functionalities are working correctly.</string> 237 <string name="ble_reliable_write_info">A Reliable Write has two steps.\n\n1) Write to the device. This will trigger a callback from the server to verify that the value written was correct.\n2) Execute the write, if the value written is valid.</string> 238 <string name="ble_notify_characteristic_info">Start accepting notifications, and verify that notifications are being reported correctly. The server should be notifying this device with the time every second.</string> 239 <string name="ble_read_rssi_info">Press button to read the RSSI value. Verify that the RSSI changes as you move the two devices further apart or closer together.</string> 240 <string name="ble_client_disconnect_info">Verify that the device is disconnected when you press the "Disconnect" button</string> 241 <string name="ble_address">Bluetooth address</string> 242 <string name="ble_connect">Connect</string> 243 <string name="ble_discover_service">Discover service</string> 244 <string name="ble_write_hint">Nothing to write yet</string> 245 <string name="ble_read_hint">Nothing read yet</string> 246 <string name="ble_write">Write</string> 247 <string name="ble_read">Read</string> 248 <string name="ble_begin_write">Begin write</string> 249 <string name="ble_execute_write">Execute write</string> 250 <string name="ble_begin_notification">Begin notification</string> 251 <string name="ble_stop_notification">Stop notification</string> 252 <string name="ble_waiting_notification">Waiting on notification</string> 253 <string name="ble_read_rssi">Read RSSI</string> 254 <string name="ble_disconnect">Disconnect</string> 255 <string name="ble_test_text">TEST</string> 256 257 <!-- BLE server side strings --> 258 <string name="ble_server_service_name">Bluetooth LE GATT Server Handler Service</string> 259 <string name="ble_server_start_name">BLE Server Test</string> 260 <string name="ble_server_start_info">The BLE test must be done simultaneously on two devices, a server device and a client device. This device is the server.</string> 261 <string name="ble_server_receiving_connect">Waiting on connection from BLE client.</string> 262 <string name="ble_server_add_service">Adding service to BLE server.</string> 263 <string name="ble_server_write_characteristic">Waiting on write characteristic request</string> 264 <string name="ble_server_read_characteristic">Waiting on read characteristic request</string> 265 <string name="ble_server_write_descriptor">Waiting on write descriptor request</string> 266 <string name="ble_server_read_descriptor">Waiting on read descriptor request</string> 267 <string name="ble_server_reliable_write">Waiting on reliable write from client</string> 268 <string name="ble_server_receiving_disconnect">Waiting on disconnection from BLE client</string> 269 270 <!-- BLE advertiser side strings --> 271 <string name="ble_advertiser_test_name">BLE Advertiser Test</string> 272 <string name="ble_advertiser_test_info">The BLE test must be done simultaneously on two devices, an advertiser and a scanner. This device is the advertiser.</string> 273 <string name="ble_advertiser_service_name">Bluetooth LE Advertiser Handler Service</string> 274 <string name="ble_privacy_mac_name">BLE Privacy Mac</string> 275 <string name="ble_privacy_mac_info">BLE Advertiser should advertise in non-repeating MAC address.</string> 276 <string name="ble_advertiser_privacy_mac_instruction">Click start to start advertising, you can disconnect USB and lock the screen of advertiser. Counts and mac address will show on scanner. You may receive message that this device does not support BLE advertising.</string> 277 <string name="ble_power_level_name">BLE Tx Power Level</string> 278 <string name="ble_power_level_info">BLE Advertiser advertises in 4 different power levels. Scanner should receive them in different strength of Rssi, cannot receive weak signals beyond several feet.</string> 279 <string name="ble_advertiser_power_level_instruction">Click start to start multi-advertising. Data packets are advertised in 4 different power levels. You may receive message that this device does not support multi advertising. If advertiser does not advertise in 4 power levels, neither you receive the error message, you may not stop the advertising in previous test, or this device does not support 4 advertisers at the same time. Try rebooting the device and run the test to free those advertisers in use.</string> 280 <string name="ble_advertiser_scan_filter_name">BLE Hardware Scan Filter</string> 281 <string name="ble_advertiser_scan_filter_info">BLE Advertiser advertises with 2 different data separately. One can wake up the scanner, the other cannot. This test cares about behavior on scanner only.</string> 282 <string name="ble_advertiser_scannable">Scannable advertising</string> 283 <string name="ble_advertiser_scannable_instruction">Start scannable advertising, expect scanner consume more power on Monsoon monitor, or see log of GattService from scanner logcat.</string> 284 <string name="ble_advertiser_unscannable">Unscannble advertising</string> 285 <string name="ble_advertiser_unscannable_instruction">Start unscannable advertising, expect scanner stay calm on Monsoon monitor, no log of GattService from scanner logcat.</string> 286 <string name="ble_advertiser_start">Start</string> 287 <string name="ble_advertiser_stop">Stop</string> 288 289 <!-- BLE scanner side strings --> 290 <string name="ble_scanner_test_name">BLE Scanner Test</string> 291 <string name="ble_scanner_service_name">Bluetooth LE Scanner Handler Service</string> 292 <string name="ble_scanner_test_info">The BLE test must be done simultaneously on two devices, an advertiser and a scanner. This device is the scanner.</string> 293 <string name="ble_scanner_privacy_mac">Hold for 15 min to see if receive a different MAC address from advertiser.</string> 294 <string name="ble_scanner_privacy_mac_instruction">Mac address, counts are shown on screen. It should continuously receive data packet from advertiser. Every 15 min, a new mac address should show up, which prevents mac address disclosure.</string> 295 <string name="ble_ultra_low">Ultra low</string> 296 <string name="ble_low">Low</string> 297 <string name="ble_medium">Medium</string> 298 <string name="ble_high">High</string> 299 <string name="ble_scanner_power_level_instruction">Count: Ultra low < low < medium < high\nRssi: Ultra low < low < medium < high\nDistance to see count freezing: Ultra low < low < medium < high\nA common error is ultra low, low and medium behave similarly, with similar rssi, freeze at similar distance.\n\n All power level receive a different mac address. After 15 mins, a green text "Get a new Mac address" will show up.</string> 300 <string name="ble_scanner_scan_filter_name">BLE Hardware Scan Filter</string> 301 <string name="ble_scanner_scan_filter_info">Lock the screen of scanner, and connect to monsoon. It will not wake up when advertiser is advertising unscannable, and scanner is scanning with filter.</string> 302 <string name="ble_scanner_scan_filter_instruction">Scan filter is to scan data with service UUID = 0x6666 only. If you scan without scan filter, data with service UUID = 0x5555 and 0x6666 will show up on screen.\nFor monsoon test:\n\tClick scan with filter, lock the screen, connect to monsoon. It will not wake up when advertiser is advertising unscannable data packets, but will show a peak in power usage when advertiser is advertising scannable data.\nFor logcat test:\n\tClick scan with filter, logcat the scanner. No data will be received by GattService when advertiser is advertising unscannable data.</string> 303 <string name="ble_scan_with_filter">Scan with filter</string> 304 <string name="ble_scan_without_filter">Scan without filter</string> 305 <string name="ble_scan_start">Start scan</string> 306 <string name="ble_scan_stop">Stop scan</string> 307 308 <!-- Strings for FeatureSummaryActivity --> 309 <string name="feature_summary">Hardware/Software Feature Summary</string> 310 <string name="feature_summary_info">This is a test for...</string> 311 <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string> 312 <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string> 313 <string name="fs_no_data">No data.</string> 314 <string name="fs_legend_good">standard feature reported by device</string> 315 <string name="fs_legend_indeterminate">optional feature not reported by device</string> 316 <string name="fs_legend_warning">non-standard feature reported by device</string> 317 <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string> 318 319 <string name="empty"></string> 320 321 <!-- Strings for HifiUltrasoundTestActivity --> 322 <string name="hifi_ultrasound_test">Hifi Ultrasound Microphone Test</string> 323 <string name="hifi_ultrasound_test_info"> 324 This is a test for near-ultrasound (18500Hz - 20000Hz) microphone response.\n 325 This test requires two devices.\n</string> 326 <string name="hifi_ultrasound_test_play">PLAY</string> 327 <string name="hifi_ultrasound_test_record">RECORD</string> 328 <string name="hifi_ultrasound_test_plot">PLOT</string> 329 <string name="hifi_ultrasound_test_dismiss">DISMISS</string> 330 <string name="hifi_ultrasound_test_ok">OK</string> 331 <string name="hifi_ultrasound_test_instruction1"> 332 Open Hifi Ultrasound Microphone Test on the test device and the reference device.\n 333 Set the media volume of the reference device at 70% and hold it with one hand.\n 334 Hold the testing device with the other hand\n 335 Press the RECORD button on the testing device, then the PLAY button on the reference device within one second.\n 336 After the test, report result on the testing (recording) device.\n</string> 337 <string name="hifi_ultrasound_test_pass">PASS</string> 338 <string name="hifi_ultrasound_test_fail">FAIL</string> 339 <string name="hifi_ultrasound_test_default_false_string">false</string> 340 <string name="hifi_ultrasound_test_mic_no_support"> 341 Device does not support near-ultrasound recording.\n 342 All new phones and tablets MUST support near-ultrasound recording.\n 343 Report FAIL if this is a new device, report PASS if this is an updating device.\n</string> 344 <string name="hifi_ultrasound_test_spkr_no_support"> 345 Device does not support near-ultrasound playback.\n 346 If this is your reference device, please use a different reference device.\n</string> 347 348 <string name="hifi_ultrasound_speaker_test">Hifi Ultrasound Speaker Test</string> 349 <string name="hifi_ultrasound_speaker_test_info"> 350 This is a test for near-ultrasound (18500Hz - 20000Hz) speaker response.\n 351 This test requires two devices.\n</string> 352 <string name="hifi_ultrasound_speaker_test_instruction1"> 353 Open Hifi Ultrasound Speaker Test on the test device and the reference device.\n 354 Set the media volume of the testing device at 70% and hold it with one hand.\n 355 Hold the reference device with the other hand\n 356 Press the RECORD button on the reference device, then the PLAY button on the testing device within one second.\n 357 After the test, report result on the testing (playback) device.\n</string> 358 <string name="hifi_ultrasound_speaker_test_mic_no_support"> 359 Device does not support near-ultrasound recording.\n 360 If this is your reference device, please use a different reference device.\n</string> 361 <string name="hifi_ultrasound_speaker_test_spkr_no_support"> 362 Device does not support near-ultrasound playback.\n 363 All new phones and tablets MUST support near-ultrasound playback.\n 364 Report FAIL if this is a new device, report PASS if this is an updating device.\n</string> 365 <string name="hifi_ultrasound_speaker_test_test_side"> 366 Please wait for the result on the reference device then report here.</string> 367 <string name="hifi_ultrasound_speaker_test_reference_side"> 368 Please report on the testing device.\n</string> 369 370 <!-- Strings for Location tests --> 371 <string name="location_gps_test">GPS Test</string> 372 <string name="location_gps_test_info">This test verifies basic GPS behavior 373 and callback scheduling. 374 Make sure the device has line of sight to GPS satellites 375 (for example, outside, or near a window) 376 and then press OK to run the automated tests.</string> 377 378 <!-- Strings for NfcTestActivity --> 379 <string name="nfc_test">NFC Test</string> 380 <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with 381 NFC enabled to exchange messages. One device must be the candidate device running the 382 software build to be tested, while the other device must be an implementation already 383 known to be compatible.\n\nThe Tag Verification tests check that your 384 device can properly read and write to tags of different technologies. The MIFARE 385 Ultralight test is only applicable for devices that support it. 386 \n\nThe Host-based card emulation tests check that your device has properly implemented 387 host-based card emulation. 388 </string> 389 390 <string name="nfc_not_enabled">NFC is not enabled!</string> 391 <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the 392 button below to goto Settings and enable it.</string> 393 <string name="nfc_settings">NFC Settings</string> 394 395 <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string> 396 <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled. 397 Click the button below to goto NFC Sharing Settings and enable it.</string> 398 <string name="ndef_push_settings">NFC Sharing Settings</string> 399 400 <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string> 401 <string name="nfc_ndef_push_sender">NDEF Push Sender</string> 402 <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string> 403 <string name="nfc_llcp_version_check">LLCP version check</string> 404 405 <string name="nfc_tag_verification">Tag Verification</string> 406 <string name="nfc_ndef">NDEF</string> 407 <string name="nfc_mifare_ultralight">MIFARE Ultralight</string> 408 409 <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on 410 another device and touch the devices back to back. The receiver should show a 411 dialog indicating it has successfully received the correct message!</string> 412 <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another 413 device running the \"CTS Verifier NDEF Receiver\"...</string> 414 415 <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on 416 another device and touch the devices back to back. The receiver should show a 417 dialog indicating it has successfully received the correct message!</string> 418 <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another 419 device running the \"CTS Verifier NDEF Sender\"...</string> 420 <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push 421 message.</string> 422 <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push 423 message.</string> 424 425 <string name="nfc_llcp_version_check_info">This test requires two candidate devices 426 with NFC enabled to exchange P2P messages. Start the \"LLCP version check\" test on 427 the other candidate device also, and touch the devices back to back. This test 428 then verifies that the candidate device correctly advises the LLCP version as 1.2</string> 429 <string name="nfc_llcp_version_check_failure">The candidate devices does not report LLCP 430 version 1.2 or higher.</string> 431 <string name="nfc_llcp_version_check_success">The candidate device has a valid LLCP version.</string> 432 <string name="nfc_tag_verifier">NFC Tag Verifier</string> 433 <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read 434 a tag of the chosen technology.</string> 435 436 <string name="nfc_scan_tag">Place device on a writable %s tag...</string> 437 <string name="nfc_write_tag_title">Writable tag discovered!</string> 438 <string name="nfc_write_tag_message">Press OK to write to this tag...</string> 439 <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string> 440 <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string> 441 <string name="nfc_no_tech">No tag technologies detected...</string> 442 443 <string name="nfc_writing_tag">Writing NFC tag...</string> 444 <string name="nfc_writing_tag_error">Error writing NFC tag...</string> 445 <string name="nfc_reading_tag">Reading NFC tag...</string> 446 <string name="nfc_reading_tag_error">Error reading NFC tag...</string> 447 448 <string name="nfc_result_success">Test passed!</string> 449 <string name="nfc_result_failure">Test failed!</string> 450 451 <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string> 452 <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string> 453 454 <string name="nfc_hce">Host-based card emulation</string> 455 <string name="nfc_hce_reader_tests">HCE reader tests</string> 456 <string name="nfc_hce_emulator_tests">HCE emulator tests</string> 457 <string name="nfc_hce_emulator_test_info">The host-based card emulation 458 tests require two devices to be completed. The HCE emulator tests are used 459 to actually test the host-based card emulation feature of the device-under-test. So the 460 device running the emulator tests must be the candidate device running the software 461 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 462 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 463 and makes sure the device-under-test implements card emulation correctly.</string> 464 <string name="nfc_hce_reader_test_info">The host-based card emulation 465 tests require two devices to be completed. The HCE emulator tests are used 466 to actually test the host-based card emulation feature of the device-under-test. So the 467 device running the emulator tests must be the candidate device running the software 468 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 469 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 470 and makes sure the device-under-test implements card emulation correctly. 471 </string> 472 <string name="nfc_hce_type_selection">By default HCE applications must run on type A. If your device is restricted to type B (for example, because of a type B only UICC), select "Type B" from the drop-down box above. Note that all tests must be completed in the same mode (either "Type A" or "Type B").</string> 473 <string name="nfc_hce_please_wait">Please wait</string> 474 <string name="nfc_hce_setting_up">Setting up card emulation services...</string> 475 476 <string name="nfc_hce_default_route_emulator">Default route (Emulator)</string> 477 <string name="nfc_hce_default_route_reader">Default route (Reader)</string> 478 <string name="nfc_hce_default_route_emulator_help">This test verifies that the default route for ISO-DEP (ISO14443-4) frames is the host CPU. It does this by selecting an AID that any Android HCE phone will respond to if the select command is routed to the host. Please verify that there is no rule in the routing table that points this AID to the host. This test may be passed if the "PASS" button on the reader side lights up after tapping the devices together.</string> 479 480 <string name="nfc_hce_protocol_params_emulator">Protocol parameters (Emulator)</string> 481 <string name="nfc_hce_protocol_params_reader">Protocol parameters (Reader)</string> 482 <string name="nfc_hce_protocol_params_emulator_help">This test verifies that the Nfc-A and ISO-DEP protocol parameters are being set correctly. The test may be passed when no FAIL entries show up in the results below. Note that the reader device may be different from the device under test - the DUT itself does not need to be able to act as the reader for this test. \n\n Note that for each test there are 3 possible outcomes:\n1) OK -> test has passed;\n2) FAIL -> test has failed and this must be fixed;\n3) FAIL EMVCO -> this protocol parameter is deviating from the requirements in the EMV Contactless Communication Protocol specification.\n\nWhile it is allowed to ship a HCE implementation with EMVCo failures, it may not perform optimal when EMVco based payment HCE apps are run on the device.</string> 483 484 <string name="nfc_hce_single_payment_emulator">Single payment (Emulator)</string> 485 <string name="nfc_hce_single_payment_reader">Single payment (Reader)</string> 486 487 <string name="nfc_hce_dual_payment_emulator">Two payment services (Emulator)</string> 488 <string name="nfc_hce_dual_payment_reader">Two payment services (Reader)</string> 489 490 <string name="nfc_hce_change_default_emulator">Change default payment service (Emulator)</string> 491 <string name="nfc_hce_change_default_reader">Change default payment service (Reader)</string> 492 493 <string name="nfc_hce_tap_reader_title">Tap reader</string> 494 <string name="nfc_hce_tap_reader_message">Select the corresponding reader test on the remote device, click OK on this dialog, and tap devices together. The pass button will be enabled if the test passes.</string> 495 496 <string name="nfc_hce_single_non_payment_emulator">Single non-payment (Emulator)</string> 497 <string name="nfc_hce_single_non_payment_reader">Single non-payment (Reader)</string> 498 499 <string name="nfc_hce_dual_non_payment_emulator">Two non-payment services (Emulator)</string> 500 <string name="nfc_hce_dual_non_payment_reader">Two non-payment services (Reader)</string> 501 502 <string name="nfc_hce_conflicting_non_payment_emulator">Two conflicting non-payment services (Emulator)</string> 503 <string name="nfc_hce_conflicting_non_payment_reader">Two conflicting non-payment services (Reader)</string> 504 505 <string name="nfc_hce_foreground_non_payment_emulator">Foreground override non-payment services (Emulator)</string> 506 <string name="nfc_hce_foreground_non_payment_reader">Foreground override non-payment services (Reader)</string> 507 <string name="nfc_hce_foreground_non_payment_help">This test enables two non-payment services with conflicting AIDs. It then uses Androids API to allow the foreground app to set a preference for a specific service. This should prevent a popup dialog from showing. If you see a popup dialog during this asking you to select an app, this test has failed.</string> 508 509 <string name="nfc_hce_foreground_payment_emulator">Foreground override payment services (Emulator)</string> 510 <string name="nfc_hce_foreground_payment_reader">Foreground override payment services (Reader)</string> 511 <string name="nfc_hce_foreground_payment_help">This test enables two payment services, and asks you to set one as the default service. It then uses Androids API to allow the foreground app to set a preference for the non-default service. This will cause the non-default payment service to be invoked.</string> 512 <string name="nfc_hce_change_favor_foreground">This test requires the "Favor foreground app" setting to be enabled. Tap OK to go to Tap and Pay settings and check the Favor foreground app option</string> 513 <string name="nfc_hce_offhost_service_emulator">Off-host service (Emulator)</string> 514 <string name="nfc_hce_offhost_service_reader">Off-host service (Reader)</string> 515 <string name="nfc_hce_offhost_emulator_help">This tests enables a service that declares some AIDs to reside off-host. This test only needs to be passed if your device has a secure element (either embedded or UICC.). The responses from the secure element are not verified by the test - it is up to the tester to verify the responses are as expected.</string> 516 517 <string name="nfc_hce_on_and_offhost_service_emulator">On and off-host services (Emulator)</string> 518 <string name="nfc_hce_on_and_offhost_service_reader">On and off-host services (Reader)</string> 519 <string name="nfc_hce_on_and_offhost_emulator_help">This tests enables a service that declares some AIDs to reside off-host, and another service that runs on host. It then first sends an APDU sequence that goes off-host, and subsequently some APDUs that should go to the on-host service. This test only needs to be passed if your device has a secure element (either embedded or UICC.). The pass button will be enabled if the on-host sequence is performed as expected. The responses from the secure element are not verified by the test - it is up to the tester to verify the responses are as expected. </string> 520 521 <string name="nfc_hce_tap_test_emulator">50 successful taps test (Emulator)</string> 522 <string name="nfc_hce_tap_test_reader">50 successful taps test (Reader)</string> 523 <string name="nfc_hce_tap_test_emulator_help">This test requires you to complete at least 50 HCE taps, to ensure stability of the HCE feature. The NFC service and controller should not crash or hang during any of the 50 taps.</string> 524 <string name="nfc_hce_throughput_emulator">HCE throughput test (Emulator)</string> 525 <string name="nfc_hce_throughput_reader">HCE throughput test (Reader)</string> 526 <string name="nfc_hce_throughput_emulator_help">This tests verifies that your HCE implementation can reach a decent throughput. While Android does not have any requirements on HCE performance, many HCE applications such as transport and payment apps do. If the average APDU roundtrip time is more than 50ms, please take a look at your implementation to see where the delay is coming from.</string> 527 <string name="nfc_hce_change_preinstalled_wallet">The device has an installed payment application that is currently set as default. To complete the test, you will be asked whether you want to make another app the default app. Select yes.</string> 528 <string name="nfc_hce_change_default_help">You will now be asked whether you want to make Payment Service #1 the default app. Select yes.</string> 529 <string name="nfc_hce_conflicting_non_payment_help">When tapping the first time, you will be shown a dialog that asks you to choose between TransportService #1 and TransportService #2. Select TransportService #2. Verify a dialog is shown that asks you to tap again to complete. Now tap again, and if communication with TransportService #2 is successfull the pass button will be enabled."</string> 530 531 <string name="nfc_hce_payment_dynamic_aids_emulator">Dynamic payment AIDs (Emulator)</string> 532 <string name="nfc_hce_payment_dynamic_aids_reader">Dynamic payment AIDs (Reader)</string> 533 <string name="nfc_hce_payment_dynamic_aids_help">This test tries to register dynamic AIDs for a payment service.</string> 534 535 <string name="nfc_hce_large_num_aids_emulator">Large number of AIDs (Emulator)</string> 536 <string name="nfc_hce_large_num_aids_reader">Large number of AIDs (Reader)</string> 537 <string name="nfc_hce_large_num_aids_help">This test tries to register a large number of different AIDs, to make sure there are no limitations on the maximum amount of HCE apps on the device. Note that this test may take a few seconds to complete; please be patient.</string> 538 539 <string name="nfc_hce_payment_prefix_aids_emulator">Payment prefix AIDs (Emulator)</string> 540 <string name="nfc_hce_payment_prefix_aids_reader">Payment prefix AIDs (Reader)</string> 541 <string name="nfc_hce_payment_prefix_aids_help">This test statically registers prefix AIDs for a payment service.</string> 542 543 <string name="nfc_hce_payment_prefix_aids_emulator_2">Payment prefix AIDs 2 (Emulator)</string> 544 <string name="nfc_hce_payment_prefix_aids_reader_2">Payment prefix AIDs 2 (Reader)</string> 545 546 <string name="nfc_hce_other_prefix_aids_emulator">Other prefix AIDs (Emulator)</string> 547 <string name="nfc_hce_other_prefix_aids_reader">Other prefix AIDs (Reader)</string> 548 <string name="nfc_hce_other_prefix_aids_help">This test dynamically registers prefix AIDs for a non-payment service.</string> 549 550 <string name="nfc_hce_other_conflicting_prefix_aids_emulator">Conflicting non-payment prefix AIDs (Emulator)</string> 551 <string name="nfc_hce_other_conflicting_prefix_aids_reader">Conflicting non-payment prefix AIDs (Reader)</string> 552 <string name="nfc_hce_other_conflicting_prefix_aids_help">This test registers conflicting prefix AIDs and makes sure AID conflict detection with prefix AIDs works properly. When tapping the first time, you will be shown a dialog that asks you to choose between TransportService #1 and TransportService #2. Select TransportService #2. Verify a dialog is shown that asks you to tap again to complete. Now tap again, and if communication with TransportService #2 is successfull the pass button will be enabled."</string> 553 554 <string name="nfc_payment_service_desc">NFC Payment service</string> 555 <string name="ppse">PPSE</string> 556 <string name="mastercard">MasterCard</string> 557 <string name="visa">Visa</string> 558 <string name="paymentService1">Payment Service #1</string> 559 <string name="paymentService2">Payment Service #2</string> 560 <string name="transportService1">TransportService #1</string> 561 <string name="transportService2">TransportService #2</string> 562 <string name="accessService">AccessService</string> 563 <string name="offhostService">OffhostService</string> 564 565 <!-- Strings for Sensor Test Activities --> 566 <string name="snsr_device_admin_receiver">Sensor Tests Device Admin Receiver</string> 567 <string name="snsr_test_summary">Tests passed: %1$d, Tests skipped: %2$d, Tests failed: %3$d</string> 568 <string name="snsr_test_complete">Test completed without errors.</string> 569 <string name="snsr_test_complete_with_errors">Test completed with errors: those errors 570 might degrade the user experience and might cause some applications to misbehave. They are 571 not required for Android Compatibility at this time, but will in a future release.</string> 572 <string name="snsr_test_pass">PASS</string> 573 <string name="snsr_test_skipped">SKIPPED</string> 574 <string name="snsr_test_fail">FAIL</string> 575 <string name="snsr_execution_time">Test execution time %1$s sec</string> 576 <string name="snsr_rvcvxchk_test">Rotation Vector CV XCheck</string> 577 <string name="snsr_rvcvxchk_test_rec">Rotation Vector CV XCheck Recording</string> 578 579 <!-- Strings to interact with users in Sensor Tests --> 580 <string name="snsr_test_play_sound">A sound will be played once the verification is complete...</string> 581 <string name="snsr_no_interaction">Leave the device on top of a flat surface.</string> 582 <string name="snsr_interaction_needed">Once the test begins, you will have to wave your hand over the front of the device.</string> 583 <string name="snsr_device_steady">Keep the device steady.</string> 584 <string name="snsr_keep_device_rotating_clockwise">Once the test begins, you will have to keep rotating the device clockwise.</string> 585 <string name="snsr_wait_for_user">Press \'Next\' to continue.</string> 586 <string name="snsr_wait_to_begin">Press \'Next\' to begin.</string> 587 <string name="snsr_on_complete_return">After completing the task, go back to this test.</string> 588 <string name="snsr_movement_expected">Movement was expected during the test. Found=%1$b.</string> 589 <string name="snsr_sensor_feature_deactivation">Turn off any special features installed in the 590 device that register for sensors. Once you are done, you can begin the test.</string> 591 <string name="snsr_setting_mode_request">You will be redirected to set \'%1$s\' to: %2$s.</string> 592 <string name="snsr_setting_mode_set">\'%1$s\' set to: %2$s.</string> 593 <string name="snsr_setting_mode_not_set">\'%1$s\' not set to: %2$s.</string> 594 <string name="snsr_setting_airplane_mode">Airplane mode</string> 595 <string name="snsr_setting_screen_brightness_mode">Adaptive Brightness</string> 596 <string name="snsr_setting_auto_rotate_screen_mode">Auto-rotate screen</string> 597 <string name="snsr_setting_keep_screen_on">Stay awake</string> 598 <string name="snsr_setting_location_mode">Location</string> 599 <string name="snsr_setting_ambient_display">Ambient Display</string> 600 <string name="snsr_pass_on_error">Pass Anyway</string> 601 <string name="snsr_run_automated_tests">The screen will be turned off to execute the tests, 602 when tests complete, the device will vibrate and the screen will be turned back on.</string> 603 604 <!-- Accelerometer --> 605 <string name="snsr_accel_test">Accelerometer Test</string> 606 <string name="snsr_accel_test_info">This test verifies that the accelerometer is working properly. As you move the device around through space, the triangle should always point down (i.e. in the direction of gravity.) If it does not, the accelerometer is improperly configured.</string> 607 <string name="snsr_accel_m_test">Accelerometer Measurement Tests</string> 608 <string name="snsr_accel_test_face_up">Place the device on a flat surface with the screen 609 facing the ceiling.</string> 610 <string name="snsr_accel_test_face_down">Place the device on a flat surface with the screen 611 facing it.</string> 612 <string name="snsr_accel_test_right_side">Place the device in a flat surface resting vertically 613 on its right side.</string> 614 <string name="snsr_accel_test_left_side">Place the device in a flat surface resting vertically 615 on its left side.</string> 616 <string name="snsr_accel_test_top_side">Place the device in a flat surface resting vertically 617 on its top side.</string> 618 <string name="snsr_accel_test_bottom_side">Place the device in a flat surface resting vertically 619 on its bottom side.</string> 620 621 <!-- Gyroscope --> 622 <string name="snsr_gyro_test">Gyroscope Test</string> 623 <string name="snsr_gyro_test_info">This test verifies that the gyroscope is working properly.\n\nRotate your device as shown by the 3D block. A green background or a check mark indicates that the gyroscope\'s value is correct. A red background or a X mark indicates that the gyroscope\'s value is not right.\n\nThere are 6 parts of the test corresponding to each rotation. Press Pass for all the stages to complete this test.</string> 624 <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string> 625 <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string> 626 <string name="snsr_gyro_test_no_gyro_message">It doesn\'t seem like you have a gyroscope, so you don\'t need to run this test.</string> 627 <string name="snsr_gyro_test_degrees_title">Wrong units?</string> 628 <string name="snsr_gyro_test_degrees_message">These values looks like degrees per second. These should be radians per second!</string> 629 <string name="snsr_gyro_m_test">Gyroscope Measurement Test</string> 630 <string name="snsr_gyro_device_placement">Place the device in a flat surface with the screen 631 facing the ceiling. Read the instructions for each scenario, before you perform the 632 test.</string> 633 <string name="snsr_gyro_device_static">Leave the device static.</string> 634 <string name="snsr_gyro_rotate_device">Once you begin the test, you will need to rotate the 635 device 360deg (one time) in the direction show by the animation, then place it back on the 636 flat surface.</string> 637 638 <!-- Heart Rate --> 639 <string name="snsr_heartrate_test">Heart Rate Test</string> 640 <string name="snsr_heartrate_test_info">This test verifies that the heart rate monitor is working properly.\n\nWait for at least 1 minute before verifying.\n\nVerify that the resting heart rate is between 0 and 100.</string> 641 <string name="snsr_heartrate_test_no_heartrate_title">No heart rate monitor?</string> 642 <string name="snsr_heartrate_test_no_heartrate_message">It doesn\'t seem like you have a heart rate monitor, so you don\'t need to run this test.</string> 643 644 <!-- Magnetic Field --> 645 <string name="snsr_mag_m_test">Magnetic Field Measurement Tests</string> 646 <string name="snsr_mag_verify_norm">Verifying the Norm...</string> 647 <string name="snsr_mag_verify_std_dev">Verifying the Standard Deviation...</string> 648 <string name="snsr_mag_verify_calibrated_uncalibrated">Verifying the relationship between 649 calibrated and uncalibrated measurements...</string> 650 <string name="snsr_mag_calibration_description">Please calibrate the Magnetometer by moving 651 it in 8 shapes in different orientations.</string> 652 <string name="snsr_mag_calibration_complete">When done, leave the device in a flat surface, far 653 from all metallic objects (if the test does not pass, try re-running it outdoors).</string> 654 <string name="snsr_mag_measurement">-> (%1$.2f, %2$.2f, %3$.2f) : %4$.2f uT</string> 655 656 <!-- Sensor Value Accuracy --> 657 <string name="snsr_rot_vec_test">Rotation Vector Accuracy Test</string> 658 <string name="snsr_event_length">Sensor(%3$s). Event values expected to have size=%1$d. Found=%2$d.</string> 659 <string name="snsr_event_value">Sensor(%3$s). Event value[0] expected to be of value=%1$f. Found=%2$f.</string> 660 <string name="snsr_event_time">Sensor(%5$s). Event timestamp expected to be synchronized with SystemClock.elapsedRealtimeNanos(). Event received at=%1$d. Event timestamp=%2$d. Delta=%3$d. Threshold=%4$d.</string> 661 662 <!-- Sensor Batching --> 663 <string name="snsr_batch_test">Sensor Batching Tests</string> 664 <string name="snsr_batching_walking_needed">Once the test begins, you will have to take the 665 device in your hand and walk.</string> 666 667 <!-- Sensor Synchronization --> 668 <string name="snsr_synch_test">Sensor Synchronization Test</string> 669 670 <!-- Step Counter and Detector --> 671 <string name="snsr_step_counter_test">Step Counter and Detector Tests</string> 672 <string name="snsr_step_counter_test_walking">Once the test begins, you will need to walk, and tap on the screen with each step you take.</string> 673 <string name="snsr_step_counter_test_still">Once the test begins, you will need to remain still and hold the device still in your hand.</string> 674 <string name="snsr_step_counter_expected_steps">At least %1$d steps are expected to be reported. Reported=%2$d.</string> 675 <string name="snsr_step_counter_detected_reported">Steps reported by user=%1$d. Steps counted=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 676 <string name="snsr_step_detector_detected_reported">Steps reported by user=%1$d. Steps detected=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 677 <string name="snsr_step_counter_event_changed">Step counter expected to increase monotonically, with a delta > 0. Found=%1$d. Timestamp=%2$d.</string> 678 <string name="snsr_step_reported">%1$d | User reported step.</string> 679 <string name="snsr_step_counter_event">%1$d | Step Counter event. count=%2$d.</string> 680 <string name="snsr_step_detector_event">%1$d | Step Detector event.</string> 681 682 <!-- Device suspend tests --> 683 <string name="snsr_device_suspend_test">Device Suspend Tests</string> 684 <string name="snsr_device_did_not_go_into_suspend">Device did not go into suspend mode during test execution </string> 685 <string name="snsr_batch_did_not_arrive_at_expected_time">Batch did not arrive at the expected time estimatedBatchArrivalMs=%1$d 686 firstEventReceivedMs=%2$d diffMs=%3$d toleranceMs=%4$d </string> 687 <string name="snsr_device_suspend_test_instr">One you begin the test, disconnect USB, turn off the display and allow 688 the device to go into suspend mode. The screen will turn on and a sound will be played once all the tests are completed.</string> 689 690 <!-- Significant Motion --> 691 <string name="snsr_significant_motion_test">Significant Motion Tests</string> 692 <string name="snsr_significant_motion_event_arrival">Event expected to trigger. Triggered=%1$s.</string> 693 <string name="snsr_significant_motion_event_type">Event expected to be of type=%1$d. Found=%2$d.</string> 694 <string name="snsr_significant_motion_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string> 695 <string name="snsr_significant_motion_disable_info">Significant Motion is expected to disable itself after it triggers once.</string> 696 <string name="snsr_significant_motion_test_trigger">Once you begin the test, you will need to walk for Significant Motion to be detected.</string> 697 <string name="snsr_significant_motion_test_cancel">Once you begin the test, you will need to walk to ensure Significant Motion is not reported after trigger canceled.</string> 698 <string name="snsr_significant_motion_test_vibration">Leave the device in a level surface. Once you begin the test, the device will vibrate to ensure that Significant Motion is not triggered.</string> 699 <string name="snsr_significant_motion_test_in_hand">Once you begin the test, hold the device in your hand while you perform natural hand movements.</string> 700 <string name="snsr_significant_motion_test_sitting">Once you begin the test, keep the device in your pocket and move naturally while sitting in a chair.</string> 701 <string name="snsr_significant_motion_test_deactivation">Once you begin the test, you will need to walk to ensure Significant Motion triggers only once.</string> 702 <string name="snsr_significant_motion_registration">Expected to be able to register for TriggerSensor. Found=%1$b.</string> 703 <string name="snsr_significant_motion_cancelation">Expected to be able to cancel TriggerSensor. Found=%b.</string> 704 <string name="snsr_significant_motion_ap_suspend">One you begin the test, disconnect USB, turn off the display and allow the device to go into suspend. 705 You will need to walk to ensure that Significant Motion triggers. The screen will turn on and a sound will be played once the test completes.</string> 706 <string name="snsr_device_did_not_wake_up_at_trigger">Device did not wakeup at tigger time. wakeTime=%1$d ms triggerTime=%2$d ms</string> 707 708 <!-- Strings for Sensor CTS tests inside CtsVerifier --> 709 <string name="snsr_single_sensor_tests">CTS Single Sensor Tests</string> 710 <string name="snsr_sensor_integration_tests">CTS Sensor Integration Tests</string> 711 <string name="snsr_sensor_test">CTS Sensor Test</string> 712 <string name="snsr_sensor_batching_tests">CTS Sensor Batching Tests</string> 713 714 <!-- Strings for Sample Test Activities --> 715 <string name="share_button_text">Share</string> 716 <string name="sample_framework_test">Sample Framework Test</string> 717 <string name="sample_test">Sample Test</string> 718 <string name="sample_test_info">This test verifies that bluetooth sharing is working properly.\nThe test assumes the Device Under Test has bluetooth enabled and is already paired with a second device, also with bluetooth enabled.\nStart this test by clicking share, choose bluetooth from the options, and then select a device to share with.\nNote: This is a sample test, used to demonstrate how to write CTS Verifier tests, so just click pass.</string> 719 720 <!-- Strings for SuidFilesActivity --> 721 <string name="suid_files">SUID File Scanner</string> 722 <string name="suid_files_info">This test will attempt to find unauthorized SUID binaries, but it is not comprehensive due to permission restrictions.\n\nAuthorized SUID binaries will appear green, while unauthorized SUID binaries will appear red.\n\nPress OK to start the scan...</string> 723 <string name="scanning_directory">Scanning directory...</string> 724 <string name="file_status">User: %1$s\nGroup: %2$s\nPermissions: %3$s\nPath: %4$s</string> 725 <string name="no_file_status">Could not stat file...</string> 726 <string name="congratulations">Congratulations!</string> 727 <string name="no_suid_files">No unauthorized suid files detected!</string> 728 729 <!-- Strings for Camera Orientation --> 730 <string name="camera_orientation">Camera Orientation</string> 731 <string name="co_info">This test verifies the orientation capabilities of 732 camera preview and capture.\n - The left view shows a preview window rotated 733 clockwise by a given magnitude of degrees.\n - The right view, after taking 734 a photo, shows the captured image.\n - For each camera and orientation, both 735 the left and right views should appear rotated clockwise by the amount of 736 degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose 737 \"Fail\".\n - For front-facing cameras, the test will horizontally mirror 738 the captured image prior to rotation, in attempt to make the left and right 739 views appear the same.\n - The physical orientation of the device does not 740 matter.\n - Read the message above the \"Take Photo\" button for 741 step-by-step instructions. 742 </string> 743 <string name="co_preview_label">Camera preview</string> 744 <string name="co_format_label">Oriented photo</string> 745 <string name="co_camera_label">Camera:</string> 746 <string name="co_orientation_label">Orientation</string> 747 <string name="co_orientation_direction_label">clockwise</string> 748 <string name="co_instruction_heading_label">Instruction:</string> 749 <string name="co_instruction_text_photo_label">Take a photo</string> 750 <string name="co_instruction_text_passfail_label">Choose \"Pass\" if the left view is oriented the same as the right view. Otherwise, choose \"Fail\".</string> 751 <string name="co_instruction_text_extra_label">(mirrored horizontally prior to rotation, since camera is front-facing)</string> 752 <string name="co_photo_button_caption">Take Photo</string> 753 754 <!-- Strings for Camera Intents --> 755 <string name="camera_intents">Camera Intents</string> 756 <string name="ci_info"> 757 This test verifies that the default camera app is firing intents 758 after pictures/videos are taken. It also verifies that when the 759 default camera app is invoked via intents, the launch intents work, 760 and the broadcast intents are received when appropriate per the SDK 761 documentation.\n\n 762 - Read the message above the \"Start Test\" button for 763 step-by-step instructions. 764 </string> 765 <string name="ci_preview_label">Camera preview</string> 766 <string name="ci_format_label">Oriented photo</string> 767 <string name="ci_camera_label">Camera:</string> 768 <string name="ci_intents_label">Intents Test</string> 769 <string name="ci_intents_direction_label">clockwise</string> 770 <string name="ci_instruction_heading_label">Instructions:</string> 771 <string name="ci_instruction_text_photo_label">READ BEFORE STARTING TEST</string> 772 <string name="ci_instruction_text_passfail_label">Choose \"Pass\" if the right intent is fired after taking a photo from the camera app. Otherwise, choose \"Fail\".</string> 773 <string name="ci_instruction_text_app_picture_label">\n 774 1. Click Start Test. \n 775 2. Go to home screen (HOME key). \n 776 3. Launch Camera application. \n 777 4. Capture photo. \n 778 5. Return to CTS verifier app. \n 779 6. Pass button will light up if intent was received.\n 780 7. Click "Pass" if possible. 781 </string> 782 <string name="ci_instruction_text_app_video_label">\n 783 1. Click Start Test. \n 784 2. Go to home screen (HOME key). \n 785 3. Launch Camera application. \n 786 4. Capture video. \n 787 5. Return to CTS verifier app. \n 788 6. Pass button will light up if intent was received.\n 789 7. Click "Pass" if possible. 790 </string> 791 <string name="ci_instruction_text_intent_picture_label">\n 792 1. Click Start Test.\n 793 2. Camera app will launch, prompting to take photo.\n 794 3. Capture/confirm photo using camera app controls.\n 795 4. Pass button will light up if intent was NOT received.\n 796 5. Click "Pass" if possible. 797 </string> 798 <string name="ci_instruction_text_intent_video_label">\n 799 1. Click Start Test.\n 800 2. Camera app will launch, prompting to take video.\n 801 3. Capture/confirm video using camera app controls.\n 802 4. Pass button will light up if intent was received.\n 803 5. Click "Pass" if possible. 804 </string> 805 <string name="ci_start_test_button_caption">Start Test</string> 806 807 <!-- Strings for Camera Formats --> 808 <string name="camera_format">Camera Formats</string> 809 <string name="cf_info">This test checks that all the supported 810 output formats for camera preview callbacks work correctly, and 811 that the mandatory formats are available. \n - The left view shows 812 a standard preview window. \n - The right view shows the output 813 processed from camera preview callbacks. \n - For each camera, 814 resolution, and format combination in the dropdowns, the right 815 view should look the same as the left, and neither should have 816 streaks, lines, or other artifacts. \n - For front-facing cameras, 817 the right view must be horizontally mirrored relative to the left 818 view.\n - Note that the frame rate of the right view may be much 819 lower than on the left; this is not an indication of a failed 820 test. 821 </string> 822 <string name="cf_preview_label">Normal preview</string> 823 <string name="cf_format_label">Processed callback data</string> 824 825 <!-- Strings for Camera Video --> 826 <string name="record_button_text">Test</string> 827 <string name="camera_video">Camera Video</string> 828 <string name="video_info"> This test checks video capture 829 at different resolutions. \n - The left view window shows the preview. 830 \n - Pressing the test button will trigger three 831 seconds of video recording. Playback will show up in the right view 832 window after recording is complete. \n - Use the spinners to choose 833 camera and resolution combinations. The playback should be similar 834 to what you saw in preview. \n - After all possible combinations 835 are tested, the pass button will be enabled. You may press the pass 836 button to indicate a pass. \n - You may press fail button any time during 837 the test to indicate failure. 838 </string> 839 <string name="video_capture_label">Video capture</string> 840 <string name="video_playback_label">Video playback</string> 841 <string name="dialog_fail_test">Test failed</string> 842 <string name="fail_quit">Fail and quit</string> 843 <string name="cancel">Cancel</string> 844 <string name="status_ready">Ready</string> 845 <string name="status_recording">Recording</string> 846 <string name="status_playback">Playing back</string> 847 848 <!-- Strings for USB accessory test activity --> 849 <string name="usb_accessory_test">USB Accessory Test</string> 850 <string name="sensor_power_test">Sensor Power Test</string> 851 <string name="usb_accessory_test_info"> 852 1. Connect your Android device to a computer and run the \'cts-usb-accessory\' program 853 included with the CTS Verifier bundle. 854 \n\n2. If you have not started the CTS Verifier, press \'OK\' when asked to open the CTS 855 Verifier when the accessory is connected. \n\nIf you are already in this test, 856 then you can press \'Cancel\' but press \'OK\' in the next dialog asking whether to allow 857 CTS Verifier to access the accessory. 858 \n\n3. You should see the accessory and the CTS Verifier display a series of messages 859 which indicates that the accessory support is working properly. 860 </string> 861 <string name="usb_not_available_title">USB accessory feature is not available?</string> 862 <string name="usb_not_available_message">If your device is supposed to support USB accessories, your API implementation is not behaving correctly!</string> 863 <string name="usb_received_messages">Received Messages</string> 864 <string name="usb_sent_messages">Sent Messages</string> 865 <string name="usb_no_messages">No messages</string> 866 <string name="usb_message_thread_started">Starting message processing...</string> 867 <string name="usb_message_thread_exception">Exception occurred while processing a message...</string> 868 <string name="usb_message_thread_ended">Stopping message processing...</string> 869 <string name="usb_test_passed">Received all expected messages. Pass button enabled!</string> 870 <string name="usb_file_descriptor_error">Could not open file descriptor for USB accessory... try reconnecting and restarting the accessory?</string> 871 872 <!-- Strings for the Camera ITS test activity --> 873 <string name="camera_its_test">Camera ITS Test</string> 874 <string name="camera_its_test_info"> 875 1. Connect your Android device to a computer with adb installed via a USB cable. 876 \n\n2. Setup the CameraITS test environment by following the setup instructions in the 877 README file found in the CameraITS directory included in the CTS Verifier bundle 878 (cd CameraITS; source build/envsetup.sh;). 879 \n\n3. Setup the test scene described in the CameraITS README file, and aim the camera 880 at it. 881 \n\n4. Run the full ITS test suite on all possible camera Ids. 882 (cd CameraITS; python tools/run_all_tests.py). Once all 883 of the tests have been run, the \'PASS\' button will be enabled if all of the tests have 884 succeeded. Please note that these tests can take 20+ minutes to run. 885 </string> 886 <string name="no_camera_manager"> 887 No camera manager exists! This test device is in a bad state. 888 </string> 889 <string name="all_legacy_devices"> 890 All cameras on this device are LEGACY mode only - ITS tests are only required on LIMITED 891 or better devices. Pass. 892 </string> 893 <string name="its_test_passed">All Camera ITS tests passed. Pass button enabled!</string> 894 <string name="its_test_failed">Some Camera ITS tests failed.</string> 895 896 <!-- Strings for the Camera Flashlight test activity --> 897 <string name="camera_flashlight_test">Camera Flashlight</string> 898 <string name="camera_flashlight_info"> 899 This test checks the flashlight functionality. It will turn on and off the flashlight of 900 each camera device that has a flash unit. Follow the instructions on screen and observe the 901 flashlight status changing. 902 </string> 903 <string name="camera_flashlight_start_button">Start</string> 904 <string name="camera_flashlight_next_button">Next</string> 905 <string name="camera_flashlight_done_button">Done</string> 906 <string name="camera_flashlight_on_button">On</string> 907 <string name="camera_flashlight_off_button">Off</string> 908 <string name="camera_flashlight_start_text">Press Start to start flashlight test.</string> 909 <string name="camera_flashlight_question_text">Is Camera %1$s flashlight on or off?</string> 910 <string name="camera_flashlight_next_text">Ok. Press next.</string> 911 <string name="camera_flashlight_failed_text">Test failed. Press Done or Fail button.</string> 912 <string name="camera_flashlight_passed_text">All tests passed. Press Done or Pass button. 913 </string> 914 915 <!-- Strings for StreamingVideoActivity --> 916 <string name="streaming_video">Streaming Video Quality Verifier</string> 917 <string name="streaming_video_info">This is a test for assessing the quality of streaming videos. Play each stream and verify that the video is smooth and in sync with the audio, and that there are no quality problems.</string> 918 <string name="sv_no_data">No videos.</string> 919 <string name="sv_failed_title">Test Failed</string> 920 <string name="sv_failed_message">Unable to play stream. See log for details.</string> 921 922 <!-- Strings for P2pTestActivity --> 923 <string name="p2p_test">Wi-Fi Direct Test</string> 924 <string name="p2p_test_info"> 925 The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange 926 messages. One device must be the candidate device running the software build to 927 be tested, while the other device must be an implementation already known to be 928 compatible.\n\nOne device should start the requester test, and the other should 929 start the responder test. Your device must pass both requester and responder 930 tests. 931 </string> 932 <string name="p2p_group_formation">Group Formation</string> 933 <string name="p2p_join">Group Join</string> 934 <string name="p2p_service_discovery">Service Discovery</string> 935 936 <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string> 937 <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string> 938 <string name="p2p_group_owner_test">Group Owner Test</string> 939 <string name="p2p_group_client_test">Group Client Test</string> 940 <string name="p2p_service_discovery_responder_test"> 941 Service Discovery Responder Test</string> 942 <string name="p2p_service_discovery_requester_test"> 943 Service Discovery Requester Test</string> 944 945 <string name="p2p_go_neg_responder">GO Negotiation Responder</string> 946 <string name="p2p_go_neg_requester">GO Negotiation Requester</string> 947 <string name="p2p_accept_client">Group Owner</string> 948 <string name="p2p_join_go">Group Client</string> 949 <string name="p2p_service_discovery_responder">Service Discovery Responder</string> 950 <string name="p2p_service_discovery_requester">Service Discovery Requester</string> 951 952 <string name="p2p_go_neg_responder_info"> 953 Start the \"GO Negotiation Requester Test\" on the other device and follow 954 the instructions.</string> 955 <string name="p2p_accept_client_info"> 956 Start the \"Group Client Test\" on the other device and follow 957 the instructions.</string> 958 <string name="p2p_service_discovery_responder_info"> 959 Start the \"Service Discovery Requester Test\" on the other device and follow 960 the instructions.</string> 961 962 <string name="p2p_go_neg_requester_info"> 963 Start the \"GO Negotiation Responder Test\" on the other device. 964 Then run each test individually by clicking on it\'s name.</string> 965 <string name="p2p_join_go_info"> 966 Start the \"Group Owner Test\" on the other device. 967 Then run each test individually by clicking on it\'s name.</string> 968 <string name="p2p_service_discovery_requester_info"> 969 Start the \"Service Discovery Responder Test\" on the other device. 970 Then run each test individually by clicking on it\'s name.</string> 971 972 <string name="p2p_not_enabled">Wi-Fi is not enabled</string> 973 <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled. 974 Click the button below to go to system settings and enable Wi-Fi.</string> 975 <string name="p2p_settings">Wi-Fi Direct Settings</string> 976 977 <string name="p2p_result_success">Test passed successfully.</string> 978 979 <string name="p2p_go_neg_responder_ready"> 980 The go negotiation responder is now ready to start. Start 981 the \"GO Negotiation Requester Test\" on the other device. 982 Keep the screen here until all tests on the other device are 983 finished.</string> 984 <string name="p2p_go_ready"> 985 The group owner is now ready to start. Start the \"Join 986 Group Test\" on the other device. 987 Keep the screen here until all tests on the other device are 988 finished.</string> 989 <string name="p2p_service_responder_ready"> 990 The service responder is now ready to start. Start the 991 \"Service Discovery Requester Test\" on the other device. 992 Keep the screen here until all tests on the other device are 993 finished.</string> 994 995 <string name="p2p_setup_error"> 996 Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string> 997 <string name="p2p_unexpected_error"> 998 Test failed.\n\nUnexpected error. Check logcat.</string> 999 <string name="p2p_add_local_service_error"> 1000 Test failed.\n\nFailed to add local service.</string> 1001 <string name="p2p_add_service_request_error"> 1002 Test failed.\n\nFailed to add service request.</string> 1003 <string name="p2p_remove_service_request_error"> 1004 Test failed.\n\nFailed to remove service request.</string> 1005 <string name="p2p_clear_service_requests_error"> 1006 Test failed.\n\nFailed to clear service requests.</string> 1007 <string name="p2p_connect_error"> 1008 Test failed.\n\nFailed to start a p2p connection to the target device.</string> 1009 <string name="p2p_remove_group_error"> 1010 Test failed.\n\nFailed to remove a p2p group.</string> 1011 <string name="p2p_discover_peers_error"> 1012 Test failed.\n\nFailed to discover peers.</string> 1013 <string name="p2p_discover_services_error"> 1014 Test failed.\n\nFailed to discover services.</string> 1015 <string name="p2p_ceate_group_error"> 1016 Test failed.\n\nFailed to start up group owner.</string> 1017 <string name="p2p_no_service_requests_error"> 1018 Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string> 1019 <string name="p2p_receive_invalid_response_error"> 1020 Test failed.\n\nReceived an invalid message or could not receive 1021 the expected message.\n\n</string> 1022 <string name="p2p_target_not_found_error">Test failed.\n\n 1023 The target responder device was NOT found. Start up the responder 1024 test on the other device, then run the test again.</string> 1025 <string name="p2p_target_invalid_role_error">Test failed.\n\n 1026 The target responder must be p2p device. However, the target responder 1027 device was group owner. Check the test case on the other device.</string> 1028 <string name="p2p_target_invalid_role_error2">Test failed.\n\n 1029 The target responder must be group owner. However, the target responder 1030 device was p2p device. Check the test case on the other device.</string> 1031 <string name="p2p_connection_error"> 1032 Test failed.\n\nFailed to establish a p2p connection.</string> 1033 <string name="p2p_detect_disconnection_error"> 1034 Test failed.\n\nFailed to detect client disconnection.</string> 1035 <string name="p2p_disconnect_error"> 1036 Test failed.\n\nFailed to disconnect a p2p connection.</string> 1037 1038 <string name="p2p_search_target">Search Target</string> 1039 <string name="p2p_searching_target">Searching for target device ...</string> 1040 <string name="p2p_checking_serv_capab">Checking the service discovery 1041 capability ...</string> 1042 <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n 1043 Click the \"OK\" button on the other device to accept the connection 1044 request from this device.</string> 1045 <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n 1046 Enter the pin number on the other device.</string> 1047 <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to 1048 connect ...</string> 1049 <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer 1050 to disconnect ...</string> 1051 1052 <string name="camera_fov_calibration">Camera FOV Calibration</string> 1053 <string name="camera_fov_calibration_done">Done</string> 1054 <string name="camera_fov_general_settings">General settings</string> 1055 <string name="camera_fov_label_options">Settings</string> 1056 <string name="camera_fov_tap_to_take_photo">Tap to calibrate</string> 1057 <string name="camera_fov_marker_distance">Marker distance (in cm)</string> 1058 <string name="camera_fov_marker_distance_description">The distance in centimeters between 1059 the solid lines on the target pattern.</string> 1060 <string name="camera_fov_target_distance">Target distance (in cm)</string> 1061 <string name="camera_fov_target_distance_description">The distance in centimeters from the 1062 device to the target pattern.</string> 1063 <string name="camera_fov_settings_button_text">Setup</string> 1064 <string name="camera_fov_change_preview_sizes_button_text">Preview Sizes</string> 1065 <string name="camera_fov_choose_preview_size_for_camera">Choose preview size for camera %1$s</string> 1066 <string name="camera_fov_displayed_fov_label">Displayed FOV : </string> 1067 <string name="camera_fov_reported_fov_label">Reported FOV : </string> 1068 <string name="camera_fov_reported_fov_problem">Reported FOV problem</string> 1069 <string name="camera_fov_reported_fov_problem_message">The reported FOV before takePicture() is 1070 different from when onPictureTaken() is called.\nAs picture size has not been changed, the 1071 reported FOV should be identical at both times.\n\nFOV before/after: %1$f / %2$f</string> 1072 1073 <string name="camera_fov_panorama_wallpaper_title">Photo Sphere Live Wallpaper</string> 1074 <string name="camera_fov_panorama_wallpaper_description">This live wallapper displays photo 1075 spheres.</string> 1076 <string name="camera_fov_select_panorama">Select panorama</string> 1077 <string name="camera_fov_select_panorama_description">Select a panorama to display in the 1078 live wallpaper.</string> 1079 <string name="camera_fov_reset_panorama">Reset panorama</string> 1080 <string name="camera_fov_reset_panorama_description">Resets the panorama to show the demo 1081 file.</string> 1082 <string name="camera_fov_enable_compass_mode">Enable compass mode</string> 1083 <string name="camera_fov_enable_compass_mode_description">If enabled, the panorama orients 1084 itself according to the current rotation of the device.</string> 1085 1086 <string name="test_category_notifications">Notifications</string> 1087 <string name="package_priority_test">Notification Package Priority Test</string> 1088 <string name="package_priority_info">This test checks that the NotificationManagerService respects 1089 user preferences about relative package priorities. 1090 </string> 1091 <string name="package_priority_bot">Verifying that the CTS Robot helper package is installed.</string> 1092 <string name="package_priority_high">Find \"%s\" under \"App notifications\" in the \"Sound & notifications\" settings panel, and mark it as having notification priority.</string> 1093 <string name="package_priority_default">Find \"%s\" under \"App notifications\" in the \"Sound & notifications\" settings panel, and make sure it has default priority.</string> 1094 <string name="package_priority_user_order">Check that ranker respects user priorities.</string> 1095 1096 <string name="attention_test">Notification Attention Management Test</string> 1097 <string name="attention_info">This test checks that the NotificationManagerService is 1098 respecting user preferences about notification ranking and filtering. 1099 </string> 1100 <string name="attention_ready">I\'m done</string> 1101 <string name="attention_filter_all">Please disable \"Do not disturb\" by tapping the Quick Settings tile.</string> 1102 <string name="attention_filter_priority">Please select \"Priority only\" in the dialog that appears 1103 when you tap the \"Do not disturb\" tile in Quick Settings, and customize the setting to allow messages from 1104 starred contacts only by tapping "More settings".</string> 1105 <string name="attention_filter_none">Please select \"Total silence\" in the dialog that appears 1106 when you tap the \"Do not disturb\" tile in Quick Settings.</string> 1107 <string name="attention_create_contacts">Create contacts for notification annotations.</string> 1108 <string name="attention_delete_contacts">Delete test contacts.</string> 1109 <string name="attention_default_order">Check that ranker defaults to time order.</string> 1110 <string name="attention_priority_order">Check that ranker respects developers priorities.</string> 1111 <string name="attention_ambient_bit">Check that the ambient bit is set appropriately.</string> 1112 <string name="attention_lookup_order">Check that ranker respects Lookup URIs for contacts.</string> 1113 <string name="attention_email_order">Check that ranker respects mailto URIs for contacts.</string> 1114 <string name="attention_phone_order">Check that ranker respects telephone URIs for contacts.</string> 1115 <string name="attention_interruption_order">Check that ranker temporarily boosts interruptions. 1116 This test takes 15 seconds to complete.</string> 1117 <string name="attention_none_are_filtered">Check that \"All\" mode doesn\'t filter any notifications.</string> 1118 <string name="attention_some_are_filtered">Check that \"Priority\" mode doesn\'t filter priority notifications.</string> 1119 <string name="attention_all_are_filtered">Check that \"None\" mode filters all notifications.</string> 1120 <string name="nls_test">Notification Listener Test</string> 1121 <string name="nls_service_name">Notification Listener for CTS Verifier</string> 1122 <string name="nls_info">This test checks that a NotificationListenerService can be enabled 1123 and disabled, and that once enabled the service is able to receive notifications and 1124 dismiss them. 1125 </string> 1126 <string name="nls_enable_service">Please enable \"Notification Listener for CTS Verifier\" 1127 under Security > Notification Access and return here.</string> 1128 <string name="nls_disable_service">Please disable \"Notification Listener for CTS Verifier\" 1129 under Security > Notification Access and return here.</string> 1130 <string name="nls_start_settings">Launch Settings</string> 1131 <string name="nls_service_started">Service should start once enabled.</string> 1132 <string name="nls_note_received">Check that notification was received.</string> 1133 <string name="nls_payload_intact">Check that notification payload was intact.</string> 1134 <string name="nls_clear_one">Check that service can clear a notification.</string> 1135 <string name="nls_clear_all">Check that service can clear all notifications.</string> 1136 <string name="nls_service_stopped">Service should stop once disabled.</string> 1137 <string name="nls_note_missed">Check that notification was not received.</string> 1138 1139 <string name="location_mode_high_accuracy_test">High Accuracy Mode Test</string> 1140 <string name="location_mode_high_accuracy_info"> 1141 This test checks that the Location Mode API is consistent with the 1142 Location Provider API when the device is in High Accuracy location mode. 1143 </string> 1144 <string name="location_mode_select_high_accuracy"> 1145 Please select the \"High accuracy\" mode at Settings > Location 1146 (hint: tap the "Mode" item) and return here. 1147 </string> 1148 <string name="location_mode_battery_saving_test">Battery Saving Mode Test</string> 1149 <string name="location_mode_battery_saving_info"> 1150 This test checks that the Location Mode API is consistent with the 1151 Location Provider API when the device is in Battery Saving location mode. 1152 </string> 1153 <string name="location_mode_select_battery_saving"> 1154 Please select the \"Battery Saving\" mode at Settings > Location 1155 (hint: tap the "Mode" item) and return here. 1156 </string> 1157 <string name="location_mode_device_only_test">Device Only Mode Test</string> 1158 <string name="location_mode_device_only_info"> 1159 This test checks that the Location Mode API is consistent with the 1160 Location Provider API when the device is in Device Only location mode. 1161 </string> 1162 <string name="location_mode_select_device_only"> 1163 Please select the \"Device Only\" mode at 1164 Settings > Location (hint: tap the "Mode" item) and return here. 1165 </string> 1166 <string name="location_mode_off_test">Location Mode Off Test</string> 1167 <string name="location_mode_off_info"> 1168 This test checks that the Location Mode API is consistent with the 1169 Location Provider API when the device is in the Off location mode. 1170 </string> 1171 1172 <string name="location_mode_start_settings">Launch Settings</string> 1173 <string name="location_mode_turn_on"> 1174 Please turn ON location access (the switch at the top of Settings > Location) 1175 and return here. 1176 </string> 1177 <string name="location_mode_turn_off"> 1178 Please turn OFF location access (the switch at the top of Settings > Location) 1179 and return here. 1180 </string> 1181 <string name="location_mode_secure_gps_on">GPS provider should be ON in secure settings.</string> 1182 <string name="location_mode_secure_gps_off">GPS provider should be OFF in secure settings.</string> 1183 <string name="location_mode_secure_nlp_on">Network location provider should be ON in secure settings.</string> 1184 <string name="location_mode_secure_nlp_off">Network location provider should be OFF in secure settings.</string> 1185 <string name="location_mode_manager_gps_on">GPS provider should be ON in LocationManager.</string> 1186 <string name="location_mode_manager_gps_off">GPS provider should be OFF in LocationManager.</string> 1187 <string name="location_mode_manager_nlp_on">Network location provider should be ON in LocationManager.</string> 1188 <string name="location_mode_manager_nlp_off">Network location provider should be OFF in LocationManager.</string> 1189 1190 <string name="cacert_test">CA Cert Notification Test</string> 1191 <string name="cacert_info">This test checks that when a CA Certificate is installed, the user is notified.</string> 1192 <string name="cacert_do_something">Do it</string> 1193 <string name="cacert_done">Done</string> 1194 <string name="cacert_install_cert">Use the CertInstaller to install the certificate. When it opens, just tap "Okay". If this button does nothing, pass the test and move on.</string> 1195 <string name="cacert_check_cert_in_settings">Visit the user-installed trusted credentials page and confirm that the "Internet Widgits Pty Ltd" cert appears in the list.</string> 1196 <string name="cacert_check_notification">Please look at the new notification and confirm: It say the network may be monitored. Tapping it brings up a more detailed explanation and a button to check trusted credentials. Tapping that button brings up the Trusted Credentials page you just visited.</string> 1197 <string name="cacert_dismiss_notification">Dismiss the notification. If it cannot be dismissed, fail the test.</string> 1198 1199 <string name="caboot_test">CA Cert Notification on Boot test</string> 1200 <string name="caboot_info">This test is to confirm that when the user has installed a trusted credential, the system notifies the user when it boots.</string> 1201 <string name="caboot_check_cert_installed">Please check here to see whether a certificate is already installed. (If this button does nothing, pass the test and move on.)</string> 1202 <string name="caboot_check_creds">Check Credentials</string> 1203 <string name="caboot_if_not_installed">Only if there is no credential currently installed, install one. (If this button does nothing, pass the test and move on.)</string> 1204 <string name="caboot_install_cert">Install credential</string> 1205 <string name="caboot_reboot_desc">Please reboot the device and return to this test.</string> 1206 <string name="caboot_after_boot">AFTER REBOOTING: Check that there is a notification that the network may be monitored. Opening that notification should show a dialog box giving more information, with a button to check trusted credentials. This should open up the same view of trusted credentials that you get via the "Check credentials" button.</string> 1207 1208 <!-- Strings for KeyChain --> 1209 <string name="keychain_test">KeyChain Storage Test</string> 1210 <string name="keychain_info">This test checks that credentials installed to the system can be granted, retrieved, and used to create valid HTTPS connections.</string> 1211 <string name="keychain_reset">Reset</string> 1212 <string name="keychain_skip">Skip</string> 1213 <string name="keychain_setup_desc">The first step sets up an internal KeyStore and generates credentials to use for the remainder of the test.\n\n 1214 Touch \'Next\' to begin.</string> 1215 <string name="keychain_install_desc">Credentials generated. Touch \'Next\' to install them to the system keychain.\n\n 1216 The container for the credentials will not be protected with a password; if prompted for one, leave that field blank.\n\n 1217 During installation you may be prompted for a name - accept the default suggestion.\n\n 1218 In the case that these credentials were already installed, you may skip this step.</string> 1219 <string name="keychain_https_desc">The last test involves setting up an HTTPS connection using credentials from the KeyChain.\n\n 1220 You should be prompted to select credentials; choose the ones you just installed in the previous step.</string> 1221 <string name="keychain_reset_desc">Before marking this test as passed, touch \'Next\' to open security settings and reset the following items:\n 1222 1. Clear device credentials.\n 1223 2. Change the lock screen type to \'None\'.</string> 1224 1225 <!-- Strings for Widget --> 1226 <string name="widget_framework_test">Widget Framework Test</string> 1227 <string name="widget_framework_test_info">This test checks some basic features of the widget 1228 framework. In order to perform the test, press the Home button. Add the widget 1229 titled "CTS Verifier" to the home screen. Follow the instructions in the widget.</string> 1230 <string name="widget_name">Widget Framework Test</string> 1231 <string name="widget_pass">Pass</string> 1232 <string name="widget_fail">Fail</string> 1233 1234 <string name="provisioning_byod_nonmarket_allow">Enable non-market apps</string> 1235 <string name="provisioning_byod_nonmarket_allow_info"> 1236 This test verifies that non-market apps can be installed if permitted.\n 1237 1. A package installation UI should appear.\n 1238 2. Accept the package and verify that it installs. 1239 </string> 1240 1241 <string name="provisioning_byod_nonmarket_deny">Disable non-market apps</string> 1242 <string name="provisioning_byod_nonmarket_deny_info"> 1243 This test verifies that non-market apps cannot be installed unless permitted.\n 1244 1. A package installation UI should appear.\n 1245 2. Verify that the installation of the package is refused. 1246 </string> 1247 1248 <string name="provisioning_byod_capture_image_support">Camera support cross profile image capture</string> 1249 <string name="provisioning_byod_capture_image_support_info"> 1250 This test verifies that images can be captured from the managed profile using the primary profile camera.\n 1251 1. Capture a picture using the camera.\n 1252 2. Verify that the captured picture is shown.\n 1253 3. Click on the close button. 1254 </string> 1255 <string name="provisioning_byod_capture_video_support">Camera support cross profile video capture</string> 1256 <string name="provisioning_byod_capture_video_support_info"> 1257 This test verifies that videos can be captured from the managed profile using the primary profile camera.\n 1258 1. Capture a video using the camera.\n 1259 2. Click on the play button.\n 1260 3. Verify that the captured video is played.\n 1261 4. Click on the close button. 1262 </string> 1263 <string name="provisioning_byod_capture_audio_support">Sound recorder support cross profile audio capture</string> 1264 <string name="provisioning_byod_capture_audio_support_info"> 1265 This test verifies that audio can be captured from the managed profile using the primary profile sound recorder.\n 1266 1. Capture audio.\n 1267 2. Click on the play button.\n 1268 3. Verify that the captured audio is played.\n 1269 4. Click on the close button.\n 1270 </string> 1271 <string name="provisioning_byod_dismiss_result_dialog">Close</string> 1272 <string name="provisioning_byod_play">Play</string> 1273 <string name="provisioning_byod_verify_image_title">Verify captured image</string> 1274 <string name="provisioning_byod_verify_video_title">Verify captured video</string> 1275 <string name="provisioning_byod_verify_audio_title">Verify captured audio</string> 1276 <string name="provisioning_byod_no_image_capture_resolver">No image capture app present. Skip test.</string> 1277 <string name="provisioning_byod_no_video_capture_resolver">No video capture app present. Skip test.</string> 1278 <string name="provisioning_byod_no_audio_capture_resolver">No audio capture app present. Skip test.</string> 1279 <string name="provisioning_byod_capture_media_error">Error while capturing media from managed profile.</string> 1280 1281 <!-- Strings for DeskClock --> 1282 <string name="deskclock_tests">Alarms and Timers Tests</string> 1283 <string name="deskclock_tests_info"> 1284 The Alarms and Timers tests verify that the Clock app implements the AlarmClock API properly. 1285 </string> 1286 <string name="deskclock_group_alarms">Alarms</string> 1287 <string name="deskclock_group_timers">Timers</string> 1288 1289 <string name="dc_show_alarms_test">Show Alarms Test</string> 1290 <string name="dc_show_alarms_test_info"> 1291 This test verifies that the SHOW_ALARMS API works.\n 1292 1. Press the "Show Alarms" button.\n 1293 2. Verify that a UI of the clock app is launched and displays the list of alarms\n 1294 </string> 1295 <string name="dc_show_alarms_button">Show Alarms</string> 1296 1297 <string name="dc_set_alarm_with_ui_test">Set Alarm Test</string> 1298 <string name="dc_set_alarm_with_ui_test_info"> 1299 This test verifies that the ACTION_SET_ALARM with no parameters API works.\n 1300 1. Press the "Set Alarm" button.\n 1301 2. Verify that the clock app is launched and displays a UI to manage alarms.\n 1302 </string> 1303 <string name="dc_set_alarm_button">Set Alarm</string> 1304 <string name="dc_set_alarm_verify_button">Verify</string> 1305 1306 <string name="dc_start_alarm_test">Start Alarm Test</string> 1307 <string name="dc_start_alarm_test_info"> 1308 This test verifies that the ACTION_SET_ALARM API actually starts an alarm.\n 1309 1. Press the "Start Alarm" button.\n 1310 2. Make sure the alarms UI is NOT shown\n 1311 3. Wait for the alarm to fire (may take up to 2 minutes)\n 1312 4. Verify that the alarm title is: "Start Alarm Test",\n 1313 the alarm is silent and vibrating (if the device supports vibrate).\n 1314 5. Dismiss the alarm.\n 1315 6. Verify that the alarm is not in the Clock\'s alarms list. The Verify button opens 1316 the alarm view.\n 1317 </string> 1318 <string name="dc_start_alarm_button">Start Alarm</string> 1319 1320 <string name="dc_full_alarm_test">Full Alarm Test</string> 1321 <string name="dc_full_alarm_test_info"> 1322 This test verifies that the ACTION_SET_ALARM API supports all extras.\n 1323 1. Press the "Create Alarm" button.\n 1324 2. Verify that you see one alarm with the following information:\n 1325 Name of alarm: Create Alarm Test. \n 1326 Vibrate: on.\n 1327 Ringtone: silent.\n 1328 Time: 01:23. \n 1329 Repeating on: Monday and Wednesday. \n 1330 </string> 1331 <string name="dc_full_alarm_button">Create Alarm</string> 1332 1333 <string name="dc_set_timer_with_ui_test">Set Timer Test</string> 1334 <string name="dc_set_timer_with_ui_test_info"> 1335 This test verifies that the ACTION_SET_TIMER API with no paramters open the UI\n 1336 1. Press the "Set Timer" button.\n 1337 2. Verify that the an app is launched and displays a UI to manage timers.\n 1338 </string> 1339 <string name="dc_set_timer_with_ui_button">Set Timer</string> 1340 1341 <string name="dc_start_timer_test">Start Timer Test</string> 1342 <string name="dc_start_timer_test_info"> 1343 This test verifies that the ACTION_SET_TIMER API actually starts a timer\n 1344 1. Press the "Start Timer" button.\n 1345 2. Verify that a timer is started and NO timers UI is shown.\n 1346 3. Verify that the timer named "Start Timer Test" rings after 30 seconds. Dismiss it.\n 1347 4. Verify that the timer is deleted after the dismissal.\n 1348 </string> 1349 <string name="dc_start_timer_button">Start Timer</string> 1350 1351 <string name="dc_start_timer_with_ui_test">Start Timer With UI Test</string> 1352 <string name="dc_start_timer_with_ui_test_info"> 1353 This test verifies that the ACTION_SET_TIMER API actually starts a timer with UI\n 1354 1. Press the "Start Timer" button.\n 1355 2. Verify that a timer is started and the timers UI is shown with a timer named "Start Timer Test".\n 1356 3. Verify that the timer rings after 30 seconds.\n 1357 </string> 1358 <!-- Strings for LockConfirmBypassTest --> 1359 <string name="lock_confirm_test_title">Keyguard Password Verification</string> 1360 <string name="lock_set_button_text">Set password</string> 1361 <string name="lock_change_button_text">Change password</string> 1362 <string name="lock_confirm_message"> 1363 This test verifies that the user is prompted for the current keyguard password before prompting for a new password.\n 1364 \nClick the \"Set password\" button if you currently don\'t have a password set.\n 1365 \nThen click the \"Change password\" button to change it. You should be prompted for the current password first. If you are not, then mark the test as failed. 1366 </string> 1367 1368 <!-- String for Projection Tests --> 1369 <string name="test_category_projection">Projection Tests</string> 1370 <string name="projection_service_name">Projection Service</string> 1371 <string name="pca_info">This tests whether or not OpenGL projection works.\n 1372 You should see two "tumbling cubes." Tapping the screen should case the cubes to explode.</string> 1373 <string name="pca_test">Projection Cube Test</string> 1374 <string name="pwa_info">This tests whether or displaying widets and keyfocus navigation works.\n 1375 You should see four buttons on the bottom of the screen.\n 1376 Pressing the "up" and "down" buttons should highlight different buttons.\n 1377 Further, you should also be able to touch them and they should highlight as usual.</string> 1378 <string name="pwa_test">Projection Widget Test</string> 1379 <string name="pwa_button_up">Up</string> 1380 <string name="pwa_button_down">Down</string> 1381 <string name="pwa_button_left">Left</string> 1382 <string name="pwa_button_right">Right</string> 1383 <string name="pwa_button">Button</string> 1384 <string name="pla_test">Projection Scrolling List Test</string> 1385 <string name="pla_info">This tests whether a projected list view will scroll properly\n 1386 You should see 50 list items and be able to scroll up and down the list</string> 1387 <string name="pva_test">Projection Video Playback Test</string> 1388 <string name="pva_info">This tests whether video playback works when projected.\n 1389 You should see a blinking white box and here a beep that is synchronized with each blink</string> 1390 <string name="pta_test">Projection Multitouch Test</string> 1391 <string name="pta_info">This tests whether multitouch works.\n 1392 Touching the screen should render a dot at the location you touched.\n 1393 Touching with additional fingers will render additoinal dots and you should be able to drag them around.</string> 1394 <string name="poa_test">Projection Offscreen Activity</string> 1395 <string name="poa_info">This tests whether a virtual display will continue to respond to and render even when the screen is off.\n 1396 Simply follow the instructions and the test will detect the pass conditions.\n 1397 Note that turning on the screen too early will result in a failure.</string> 1398 1399 <!-- Strings for RotationVectorTest and GameRotationVectorTest --> 1400 <string name="rotation_vector_test">Rotation Vector Accuracy Test</string> 1401 <string name="snsr_rotation_vector_set_reference"> 1402 Place the mobile device in a reference position. Note: to provide an accurate reference, 1403 align the device along one edge of a notebook laying on a table.</string> 1404 <string name="snsr_rotation_vector_reference_set">Reference position set.</string> 1405 <string name="snsr_rotation_vector_move_info">Move, shake, and rotate the device.</string> 1406 <string name="snsr_rotation_vector_set_final">Place the device back to the reference position.</string> 1407 <string name="snsr_rotation_vector_verification">Angular deviation [%1$4.1f %2$4.1f %3$4.1f]. Current: %4$f deg. Max tolerated: %5$f.</string> 1408 1409 <!-- Strings common for BYOD and DO managed provisioning tests. --> 1410 <string name="afw_device_admin">CTS Verifier - AfW Admin</string> 1411 1412 <!-- Strings for BYOD managed provisioning tests (ByodFlowTestActivity) --> 1413 <string name="test_category_managed_provisioning">Managed Provisioning</string> 1414 <string name="provisioning_byod">BYOD Managed Provisioning</string> 1415 <string name="provisioning_byod_info"> 1416 This test exercises the BYOD managed provisioning flow. 1417 Start by pressing the button on screen and follow instructions to finish the managed provisioning process. 1418 If your device has not been encrypted before, it will be encrypted and rebooted. 1419 After the provisioning process completes, return to this page and carry out further verifications. 1420 Note: the device will remain encrypted after the test which can only be disabled by factory reset. 1421 </string> 1422 <string name="provisioning_byod_start">Start BYOD provisioning flow</string> 1423 <string name="provisioning_byod_instructions"> 1424 1. Press the button below to start the managed provisioning flow. 1425 If your device has not been encrypted before, it will reboot to apply encryption. 1426 After reboot follow instructions in the notification area to complete the provisioning.\n 1427 2. After successful provisioning, you should be automatically redirected back to this page. 1428 Please press through the following verification steps. 1429 Allow a few seconds after returning from provisioning, as the profile owner test should automatically pass.\n 1430 \n 1431 If the device is being encrypted during step 1, it will remain encrypted After this test. 1432 The only way to disable the encryption is to factory reset the device. 1433 </string> 1434 <string name="provisioning_byod_profileowner">Profile owner installed</string> 1435 <string name="provisioning_byod_diskencryption">Full disk encryption enabled</string> 1436 <string name="provisioning_byod_profile_visible">Profile-aware accounts settings</string> 1437 <string name="provisioning_byod_admin_visible">Profile-aware device administrator settings</string> 1438 <string name="provisioning_byod_workapps_visible">Badged work apps visible in Launcher</string> 1439 <string name="provisioning_byod_cross_profile_from_personal">Open app cross profiles from the personal side</string> 1440 <string name="provisioning_byod_cross_profile_from_work">Open app cross profiles from the work side</string> 1441 <string name="provisioning_app_linking">App links from the work side</string> 1442 <string name="provisioning_byod_cross_profile_app_personal">You selected the personal option.</string> 1443 <string name="provisioning_byod_cross_profile_app_work">You selected the Work option.</string> 1444 <string name="provisioning_byod_cross_profile_app_ctsverifier"> You selected the ctsverifier option </string> 1445 <string name="provisioning_byod_cross_profile_from_personal_instruction"> 1446 Please press the Go button to start an action.\n 1447 \n 1448 You should be asked to choose either \"CTS Verifier\" or \"Work\" to complete the action. 1449 Pressing either should bring up a page stating your choice.\n 1450 \n 1451 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 1452 </string> 1453 <string name="provisioning_byod_cross_profile_from_work_instruction"> 1454 Please press the Go button to start an action.\n 1455 \n 1456 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action. 1457 Pressing either should bring up a page stating your choice.\n 1458 \n 1459 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 1460 </string> 1461 <string name="provisioning_byod_app_linking_instruction"> 1462 Please press the Go button to start an action.\n 1463 \n 1464 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action.\n 1465 - If you choose \"CTS Verifier\", you should see a page stating your chose \"CTS Verifier\".\n 1466 - If you choose \"Personal\", you should be presented with another dialog between \"CTS Verifier\" 1467 and some other apps. In this case, you should choose \"CTS verifier\".\n 1468 You should then see a page stating you chose \"Personal\".\n 1469 \n 1470 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 1471 </string> 1472 <string name="provisioning_byod_keyguard_disabled_features">Keyguard disabled features</string> 1473 <string name="provisioning_byod_keyguard_disabled_features_info"> 1474 This test exercises Keyguard Disabled Features. Follow instructions above. 1475 </string> 1476 <string name="provisioning_byod_keyguard_disabled_features_instruction"> 1477 Please go to Settings > Security > Device administrators and set 1478 \"CTS Verifier - AfW Admin\" as active admin.\n 1479 After that please press the \"Prepare test\" button to disable trust agents.\n 1480 Then please press through the following verification steps.\n 1481 Note: Device password will be set to \"testpassword\". After leaving the screen device 1482 password and active admin status will be cleared. 1483 </string> 1484 <string name="provisioning_byod_keyguard_disabled_features_prepare_button">Prepare test</string> 1485 <string name="provisioning_byod_keyguard_disabled_features_not_admin">CtsVerifier is not active admin. Please follow instructions.</string> 1486 <string name="provisioning_byod_disable_trust_agents">Disable trust agents</string> 1487 <string name="provisioning_byod_disable_trust_agents_instruction"> 1488 Please press the Go button to go to Settings > Security. Then go to Trusted agents and\n 1489 check if the agents are shown as disabled by the administrator. 1490 Then please press Back and mark the test as \"Pass\" or \"Fail\". 1491 </string> 1492 <string name="provisioning_byod_fingerprint_disabled_in_settings">Fingerprint is disabled in Settings</string> 1493 <string name="provisioning_byod_fingerprint_disabled_in_settings_instruction"> 1494 Please press the Go button to go to Settings > Security. Then go to Fingerprint and\n 1495 check if the screen is shown as disabled by the administrator. 1496 Then please press Back and mark the test as \"Pass\" or \"Fail\". 1497 </string> 1498 <string name="provisioning_byod_disable_fingerprint">Fingerprint disabled on keyguard</string> 1499 <string name="provisioning_byod_disable_fingerprint_instruction"> 1500 Please press the Go button to lock the screen. Then try to log in using the fingerprint reader.\n 1501 Expected result is you cannot log in using your fingerprint.\n 1502 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\". 1503 </string> 1504 <string name="provisioning_byod_disable_notifications">Notifications disabled on keyguard</string> 1505 <string name="provisioning_byod_disable_notifications_instruction"> 1506 Please press the Go button to lock the screen. Wait a couple of seconds and look out for a 1507 notification from CtsVerifier.\n 1508 Expected result is the notification is shown as \"Contents hidden\", you can not see the contents 1509 (Which would read \"This is a work notification\").\n 1510 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\". 1511 </string> 1512 <string name="provisioning_byod_work_notification">Work notification is badged</string> 1513 <string name="provisioning_byod_work_notification_instruction"> 1514 Please press the Go button to trigger a notification.\n 1515 \n 1516 Verify that the notification is badged (see sample badge below). Then mark this test accordingly. 1517 </string> 1518 <string name="provisioning_byod_work_notification_title">This is a work notification</string> 1519 <string name="provisioning_byod_work_status_icon">Work status icon is displayed</string> 1520 <string name="provisioning_byod_work_status_icon_instruction"> 1521 Verify that the current status bar does not have a work status icon (see sample icon below). 1522 \n\n 1523 Please press the Go button to launch a work activity. 1524 \n\n 1525 Verify that the status bar now has a work status icon. Then mark this test accordingly. 1526 </string> 1527 <string name="provisioning_byod_work_status_icon_activity"> 1528 Verify that the current status bar has a work status notification. 1529 \n\n 1530 Please press finish to return to the tests and then mark this test accordingly. 1531 </string> 1532 <string name="provisioning_byod_work_status_toast">Work status toast is displayed</string> 1533 <string name="provisioning_byod_work_status_toast_instruction"> 1534 Please press the Go button to launch a work activity. 1535 \n\n 1536 Follow instructions and then return and mark this test accordingly. 1537 </string> 1538 <string name="provisioning_byod_work_status_toast_activity"> 1539 Turn off the screen and wait a few seconds then turn on the screen again. 1540 \n\n 1541 Verify that a toast was displayed saying you are in the work profile. 1542 \n\n 1543 Please press finish to return to the tests and then mark this test accordingly. 1544 </string> 1545 <string name="provisioning_byod_profile_visible_instruction"> 1546 Please press the Go button to open the Settings page. 1547 Navigate to Accounts and confirm that:\n 1548 \n 1549 - Both Personal and Work categories exist.\n 1550 - \"Remove work profile\" exists under the Work category.\n 1551 \n 1552 Furthermore, hit the action overflow button (3 dots) and verify that:\n 1553 - There are two auto-sync options present, one for personal and one for work data.\n 1554 - De-selecting either option prompts a warning dialog.\n 1555 \n 1556 Use the Back button to return to this page. 1557 </string> 1558 <string name="provisioning_byod_admin_visible_instruction"> 1559 Please press the Go button to open the Security page in Settings. 1560 Navigate to Device administrators and confirm that:\n 1561 \n 1562 - Both Personal and Work categories exist.\n 1563 - \"CTS Verifier - AfW Admin\" exists under the Work category, and is activated.\n 1564 \n 1565 Use the Back button to return to this page. 1566 </string> 1567 <string name="provisioning_byod_workapps_visible_instruction"> 1568 Please press the Go button to start the launcher. 1569 Go to All Apps screen and scroll through it to confirm that:\n 1570 \n 1571 - A new set of work apps including CTS Verifier appear in the list.\n 1572 - Work badge overlay appears on work app\'s icon (see example icon below).\n 1573 \n 1574 Then navigate back to this screen using Recents button. 1575 </string> 1576 1577 <string name="provisioning_byod_app_settings">Profile-aware app settings</string> 1578 <string name="provisioning_byod_app_settings_instruction"> 1579 Please press the Go button to open Apps page in settings.\n 1580 \n 1581 Verify that work profile exists in the dropdown list and selecting it will 1582 bring up apps setting in the work profile.\n 1583 \n 1584 Then use the Back button to return to this test and mark accordingly. 1585 </string> 1586 1587 <string name="provisioning_byod_location_settings">Profile-aware location settings</string> 1588 <string name="provisioning_byod_location_settings_instruction"> 1589 Please press the Go button to open Location page in settings.\n 1590 \n 1591 Verify that work profile entry exists in the page.\n 1592 \n 1593 Then use the Back button to return to this test and mark accordingly. 1594 </string> 1595 1596 <string name="provisioning_byod_battery_settings">Profile-aware battery settings</string> 1597 <string name="provisioning_byod_battery_settings_instruction"> 1598 Please press the Go button to open Battery page in settings.\n 1599 \n 1600 Verify that Battery page shows both badged and unbadged apps in the usage list.\n 1601 \n 1602 Note that the usage list only displays usage since last charge, 1603 so you may need to unplug your device and use a badged and unbadged app 1604 for a little while before they will appear in the list.\n 1605 \n 1606 Then use the Back button to return to this test and mark accordingly. 1607 </string> 1608 1609 <string name="provisioning_byod_data_usage_settings">Profile-aware data usage settings</string> 1610 <string name="provisioning_byod_data_usage_settings_instruction"> 1611 Please press the Go button to open the Settings page.\n 1612 \n 1613 Navigate to Data usage page and confirm that it includes a Work profile section, 1614 and that tapping it shows just work profile data usage.\n 1615 \n 1616 Then use the Back button to return to this test and mark accordingly. 1617 </string> 1618 1619 <string name="provisioning_byod_cred_settings">Profile-aware trusted credential settings</string> 1620 <string name="provisioning_byod_cred_settings_instruction"> 1621 Please press the Go button to open the Security settings. 1622 Navigate to "Trusted credentials" and wait for the UI to load. 1623 After the list is loaded, confirm that:\n 1624 \n 1625 The page list credentials for both "Personal" and "Work" profiles.\n 1626 \n 1627 Then use the Back button to return to this test and mark accordingly. 1628 </string> 1629 1630 <string name="provisioning_byod_print_settings">Profile-aware printing settings</string> 1631 <string name="provisioning_byod_print_settings_instruction"> 1632 Please press the Go button to open the Printing settings. 1633 \n 1634 Verify that work profile exists in the dropdown list and selecting it will 1635 bring up printing setting in the work profile.\n 1636 \n 1637 Then use the Back button to return to this test and mark accordingly. 1638 </string> 1639 1640 <string name="provisioning_byod_cross_profile_intent_filters">Cross profile intent filters are set</string> 1641 1642 <string name="provisioning_byod_nfc_beam">Disable Nfc beam</string> 1643 <string name="provisioning_byod_nfc_beam_allowed_instruction"> 1644 Please press the Go button to test if Nfc beam can be triggered in the work profile.\n 1645 \n 1646 For the first test, press \"Send manual beam\" to trigger a beam, then bump into another device to send the file. Verify that the file is successfully received.\n 1647 \n 1648 For the second test, press \"Send share intent\" to trigger a beam, then bump into another device to send the file. Verify that the file is successfully received.\n 1649 \n 1650 Then use the Back button to return to this test and mark accordingly. 1651 </string> 1652 <string name="provisioning_byod_nfc_beam_disallowed_instruction"> 1653 Please press the Go button to test if Nfc beam is disallowed by policy 1654 \n 1655 Verify that Nfc beam is not triggered when pressing the button.\n 1656 \n 1657 Then use the Back button to return to this test and mark accordingly. 1658 </string> 1659 <string name="provisioning_byod_send_manual_beam">Send manual beam</string> 1660 <string name="provisioning_byod_send_share_intent">Send share intent</string> 1661 <string name="provisioning_byod_cannot_resolve_beam_activity">Cannot find beam activity</string> 1662 1663 <string name="provisioning_byod_no_activity">Cannot communicate with activity in the work profile.</string> 1664 <string name="provisioning_byod_delete_profile">Initiate deletion of work profile.</string> 1665 <string name="provisioning_byod_profile_deleted">Work profile deleted.</string> 1666 <string name="provisioning_byod_disabled">Device provisioning is not enabled.</string> 1667 <string name="provisioning_button_finish">Finish</string> 1668 <string name="provisioning_cross_profile_chooser">Choose an app to complete action</string> 1669 1670 <!-- Strings for DeviceOwnerProvisioningTest --> 1671 <string name="provisioning_device_owner">Device Owner Provisioning</string> 1672 <string name="device_owner_provisioning_tests">Device Owner provisioning tests</string> 1673 <string name="device_owner_provisioning_tests_info">The device owner provisioning tests verify that setting up a corporate owned device can only be done on a factory reset device.</string> 1674 <string name="device_owner_provisioning_category">Device Owner Provisioning</string> 1675 <string name="device_owner_negative_test">Device owner negative test</string> 1676 <string name="device_owner_negative_test_info">Please click the "Start provisioning" button, and when you see a warning dialog telling the device is already set up, select "pass". Otherwise, select "fail".</string> 1677 <string name="start_device_owner_provisioning_button">Start provisioning</string> 1678 <string name="positive_device_owner">Device Owner Tests</string> 1679 <string name="device_owner_positive_tests">Device Owner positive tests</string> 1680 <string name="device_owner_positive_tests_instructions"> 1681 The positive device owner tests verify policies on a corporate owned device.\n 1682 Press below button first, follow steps described in the dialog that pops up, 1683 then proceed to the test cases.\n 1684 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 1685 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 1686 be run last so that it does not interfere with other tests. 1687 </string> 1688 <string name="device_owner_positive_tests_info"> 1689 The positive device owner tests verify policies on a corporate owned device.\n 1690 Press below button first, follow steps described in the dialog that pops up, 1691 then proceed to the test cases.\n 1692 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 1693 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 1694 be run last so that it does not interfere with other tests. 1695 </string> 1696 <string name="device_owner_positive_category">Device Owner Tests</string> 1697 <string name="set_device_owner_button_label">Set up device owner</string> 1698 <string name="set_device_owner_dialog_title">Set up device owner</string> 1699 <string name="set_device_owner_dialog_text"> 1700 Please set the device owner by enabling USB debugging on the device and issuing the following command on the host:\n 1701 adb shell dpm set-device-owner \'com.android.cts.verifier/com.android.cts.verifier.managedprovisioning.DeviceAdminTestReceiver\' 1702 </string> 1703 <string name="device_owner_remove_device_owner_test">Remove device owner</string> 1704 <string name="device_owner_remove_device_owner_test_info"> 1705 Please check in Settings > Security > Device Administrators if CTSVerifier is 1706 Device Owner. Then press the button below, and check that CTSVerifier is NOT Device 1707 Owner anymore. 1708 </string> 1709 <string name="remove_device_owner_button">Remove device owner</string> 1710 <string name="device_owner_check_device_owner_test">Check device owner</string> 1711 <string name="device_owner_incorrect_device_owner">Missing or incorrect device owner: CTSVerifier is not DO!</string> 1712 <string name="device_owner_wifi_lockdown_test">WiFi configuration lockdown</string> 1713 <string name="device_owner_wifi_lockdown_info"> 1714 Please enter the SSID and auth method of an available WiFi Access Point and press the button to create a 1715 WiFi configuration. This configuration can be seen on Settings > WiFi. The test cases 1716 are going use this config. Please go through test cases in order (from top to bottom). 1717 </string> 1718 <string name="switch_wifi_lockdown_off_button">WiFi config lockdown off</string> 1719 <string name="switch_wifi_lockdown_on_button">WiFi config lockdown on</string> 1720 <string name="wifi_lockdown_go_settings_wifi_button">Go to WiFi Settings</string> 1721 <string name="device_owner_wifi_key_management_none_button">None</string> 1722 <string name="device_owner_wifi_key_management_wpa_button">WPA</string> 1723 <string name="device_owner_wifi_key_management_wep_button">WEP</string> 1724 <string name="create_wifi_config_button_label">Create WiFi configuration</string> 1725 <string name="wifi_lockdown_add_network_failed_dialog_title">WiFi configuration could not be created</string> 1726 <string name="wifi_lockdown_add_network_failed_dialog_text"> 1727 There was an error during creation of WiFi configuration. Check if WiFi is switched on. 1728 </string> 1729 <string name="device_owner_wifi_config_unlocked_modification_test">Unlocked config is modifiable in Settings</string> 1730 <string name="device_owner_wifi_config_unlocked_modification_test_info"> 1731 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 1732 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be edited. 1733 Please make sure you can connect to it. The test is successful if the config is editable 1734 and can be connected to. 1735 </string> 1736 <string name="device_owner_wifi_config_locked_modification_test">Locked config is not modifiable in Settings</string> 1737 <string name="device_owner_wifi_config_locked_modification_test_info"> 1738 Please press the button to ensure WiFi config lockdown is in effect. Then go to 1739 Settings > WiFi and see if the CTSVerifier created WiFi configuration can NOT be edited 1740 or removed. The test is successful if the config is NOT modifiable. 1741 </string> 1742 <string name="device_owner_wifi_config_locked_connection_test">Locked config can be connected to</string> 1743 <string name="device_owner_wifi_config_locked_connection_test_info"> 1744 Please press the button to ensure WiFi config lockdown is in effect. Then go to 1745 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be connected 1746 to manually. The test is successful if the connection can be established. 1747 </string> 1748 <string name="device_owner_wifi_config_unlocked_removal_test">Unlocked config can be forgotten in Settings</string> 1749 <string name="device_owner_wifi_config_unlocked_removal_test_info"> 1750 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 1751 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be forgotten. 1752 The test is successful if the config could be forgotten and is removed from the list of saved configs. 1753 </string> 1754 <string name="device_owner_disable_statusbar_test">Disable status bar</string> 1755 <string name="device_owner_disable_statusbar_test_info"> 1756 Please press the below button to disable the status bar and verify that quick settings, notifications 1757 and the assist gesture are no longer available.\n 1758 Next, press the button to reenable the status bar and verify that quick settings, notification 1759 and the assist gesture are available again.\n 1760 Please mark the test accordingly. 1761 </string> 1762 <string name="device_owner_disable_statusbar_button">Disable status bar</string> 1763 <string name="device_owner_reenable_statusbar_button">Reenable status bar</string> 1764 <string name="device_owner_disable_keyguard_test">Disable keyguard</string> 1765 <string name="device_owner_disable_keyguard_test_info"> 1766 Note that any device passwords that you might have set will be deleted during this test.\n 1767 Please press the below button to disable the keyguard. Press the power button on your device to 1768 switch off the screen. Then press the power button to switch the screen back on and verify that 1769 no keyguard was shown.\n 1770 Next, press the button to reenable the keyguard and repeat the above steps, this time verifying that 1771 a keyguard was shown again.\n 1772 Please mark the test accordingly. 1773 </string> 1774 <string name="device_owner_disable_keyguard_button">Disable keyguard</string> 1775 <string name="device_owner_reenable_keyguard_button">Reenable keyguard</string> 1776 <string name="device_profile_owner_permission_lockdown_test">Permissions lockdown</string> 1777 <string name="device_profile_owner_permission_lockdown_test_instructions"> 1778 Select each of the three grant states for the permission shown below in turn.\n 1779 Now open application settings, select Permissions, and verify if the following behaviour is observed.\n 1780 <b>Allow:</b> Permission is granted to the app and cannot be changed through the settings UI.\n 1781 <b>Let user decide:</b> Permission state can be changed through the settings UI.\n 1782 <b>Deny:</b> Permission is denied to the app and cannot be changed through the settings UI.\n 1783 Please mark the test accordingly. 1784 </string> 1785 <string name="device_owner_permission_lockdown_test_info"> 1786 This test checks if the permissions state in settings UI is locked down according to the state set by the device owner. 1787 </string> 1788 <string name="profile_owner_permission_lockdown_test_info"> 1789 <b> 1790 Before proceeding, check if com.android.cts.permissionapp (aka CtsPermissionApp) is installed in work profile by going to Settings > Apps. If not, please install the app before proceeding.\n\n 1791 </b> 1792 This test checks if the permissions state in settings UI is locked down correctly depending on the state set by the profile owner. 1793 </string> 1794 <string name="package_not_found">You must install %s (aka CtsPermissionApp).</string> 1795 <string name="permission_allow">Grant</string> 1796 <string name="permission_default">Let user decide</string> 1797 <string name="permission_deny">Deny</string> 1798 <string name="not_profile_owner">%s is not profile owner.</string> 1799 <string name="not_device_owner">%s is not device owner.</string> 1800 <string name="activity_not_found">No activity found to handle intent: %s</string> 1801 <string name="open_settings_button_label">Open Application Settings</string> 1802 <string name="finish_button_label">Finish</string> 1803 <string name="device_owner_device_admin_visible">Device administrator settings</string> 1804 <string name="device_owner_device_admin_visible_info"> 1805 Please press the Go button to open the Security page in Settings. 1806 Navigate to Device administrators and confirm that:\n 1807 \n 1808 - \"CTS Verifier - AfW Admin\" exists and is activated.\n 1809 - \"CTS Verifier - AfW Admin\" cannot be disabled.\n 1810 \n 1811 Use the Back button to return to this page. 1812 </string> 1813 <string name="device_owner_disallow_config_bt">Disallow configuring Bluetooth</string> 1814 <string name="device_owner_disallow_config_bt_info"> 1815 Please press the Set restriction button to set the user restriction. 1816 Then press Go to open the Bluetooth page in Settings. 1817 Confirm that:\n 1818 \n 1819 - You cannot view Bluetooth devices in range.\n 1820 - You cannot edit, add or remove any already paired devices.\n 1821 \n 1822 Use the Back button to return to this page. 1823 </string> 1824 <string name="device_owner_disallow_config_wifi">Disallow configuring WiFi</string> 1825 <string name="device_owner_disallow_config_wifi_info"> 1826 Please press the Set restriction button to set the user restriction. 1827 Then press Go to open the WiFi page in Settings. 1828 Confirm that:\n 1829 \n 1830 - You cannot view WiFi networks in range.\n 1831 - You cannot edit, add or remove any existing WiFi configs.\n 1832 \n 1833 Use the Back button to return to this page. 1834 </string> 1835 <string name="device_owner_user_restriction_set">Set restriction</string> 1836 <string name="device_owner_settings_go">Go</string> 1837 1838 <!-- Strings for JobScheduler Tests --> 1839 <string name="js_test_description">This test is mostly automated, but requires some user interaction. You can pass this test once the list items below are checked.</string> 1840 1841 <string name="js_idle_test">Idle Mode Constraints</string> 1842 <string name="js_start_test_text">Start test</string> 1843 <string name="js_idle_instructions">Verify the behaviour of the JobScheduler API for when the device is in idle mode. Simply follow the on-screen instructions.</string> 1844 <string name="js_idle_description_1">Turn the screen off and then back on in order to begin.</string> 1845 <string name="js_idle_item_idle_off">Idle job does not execute when device is not idle.</string> 1846 <string name="js_idle_item_idle_on">Idle job does execute when device is forced into idle.</string> 1847 1848 <string name="js_charging_test">Charging Constraints</string> 1849 <string name="js_charging_instructions">Verify the behaviour of the JobScheduler API for when the device is on power and unplugged from power. Simply follow the on-screen instructions.</string> 1850 <string name="js_charging_description_1">Unplug the device in order to begin.</string> 1851 <string name="js_charging_off_test">Device not charging will not execute a job with a charging constraint.</string> 1852 <string name="js_charging_on_test">Device when charging will execute a job with a charging constraint.</string> 1853 <string name="js_charging_description_2">After the above test has passed, plug the device back in to continue. If the above failed, you can simply fail this test.</string> 1854 1855 <string name="js_connectivity_test">Connectivity Constraints</string> 1856 <string name="js_connectivity_instructions">Verify the behaviour of the JobScheduler API for when the device has no access to data connectivity. Simply follow the on-screen instructions.</string> 1857 <string name="js_connectivity_description_1">Disable WiFi and Cellular data to begin.</string> 1858 <string name="js_unmetered_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 1859 <string name="js_any_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 1860 <string name="js_no_connectivity_test">Device with no connectivity will still execute a job with no connectivity constraints.</string> 1861 1862 <!-- String for the bundled TV app Tests --> 1863 1864 <string name="tv_input_discover_test">3rd-party TV input test</string> 1865 <string name="tv_input_discover_test_info"> 1866 Verify that the bundled TV app launches via Intent and calls the proper API to discover 1867 3rd-party TV inputs. 1868 </string> 1869 <string name="tv_input_discover_test_go_to_setup"> 1870 Select the \"Launch TV app\" button and set up the newly installed TV input: 1871 \"CTS Verifier\". 1872 </string> 1873 <string name="tv_input_discover_test_verify_setup"> 1874 Setup activity must have been started. 1875 </string> 1876 <string name="tv_input_discover_test_tune_to_channel"> 1877 Select the \"Launch TV app\" button and tune to the \"Dummy\" channel from \"CTS Verifier\" 1878 input. If necessary, configure the channel to be visible. 1879 </string> 1880 <string name="tv_input_discover_test_verify_tune"> 1881 Tune command must be called. 1882 </string> 1883 <string name="tv_input_discover_test_verify_overlay_view"> 1884 Verify that the overlay appears and displays the text \"Overlay View Dummy Text\" when you tune 1885 to the \"Dummy\" channel. 1886 </string> 1887 <string name="tv_input_discover_test_verify_global_search"> 1888 Verify the TV app provides query results for 3rd-party input\'s channels and programs in 1889 global search results. 1890 </string> 1891 <string name="tv_input_discover_test_go_to_epg"> 1892 Select the \"Launch EPG\" button and locate the \"Dummy\" channel. 1893 </string> 1894 <string name="tv_input_discover_test_verify_epg"> 1895 Do you see the programs named \"Dummy Program\" and their descriptions 1896 "Dummy Program Description" in the EPG? 1897 </string> 1898 <string name="tv_input_discover_test_yes">Yes</string> 1899 1900 <string name="tv_parental_control_test">TV app parental controls test</string> 1901 <string name="tv_parental_control_test_info"> 1902 Verify that the bundled TV app calls the parental controls API. 1903 </string> 1904 <string name="tv_parental_control_test_turn_on_parental_control"> 1905 Select the \"Launch TV app\" button and turn on the parental controls. If parental controls are 1906 on already, turn it off and on again. 1907 </string> 1908 <string name="tv_parental_control_test_verify_receive_broadcast1"> 1909 TV input service must have received ACTION_PARENTAL_CONTROLS_ENABLED_CHANGED broadcast. 1910 </string> 1911 <string name="tv_parental_control_test_block_tv_ma"> 1912 Select the \"Launch TV app\" button and block the \"Fake\" rating for \"CtsVerifier\" rating 1913 system in the parental control settings. If the rating system is disabled by default, enable it. 1914 If the \"Fake\" rating is already blocked, unblock it, save, and then block again. 1915 </string> 1916 <string name="tv_parental_control_test_verify_receive_broadcast2"> 1917 TV input service must have received ACTION_BLOCKED_RATINGS_CHANGED broadcast. 1918 </string> 1919 <string name="tv_parental_control_test_block_unblock"> 1920 Select the \"Launch TV app\" button; verify that the channel is blocked. 1921 Try to unblock the screen by entering PIN; verify that it\'s unblocked. 1922 </string> 1923 1924 <string name="tv_launch_tv_app">Launch TV app</string> 1925 <string name="tv_launch_epg">Launch EPG</string> 1926 <string name="tv_channel_not_found"> 1927 CtsVerifier channel is not set up. Please set up before proceeding. 1928 </string> 1929 1930 <string name="tv_multiple_tracks_test">TV app closed captions and multi-audio test</string> 1931 <string name="tv_multiple_tracks_test_info"> 1932 Verify that the bundled TV app calls the multi-track API. 1933 </string> 1934 <string name="tv_multiple_tracks_test_select_subtitle"> 1935 Select the \"Launch TV app\" button. Verify that closed captions are off by default. Set closed 1936 caption language to English. 1937 </string> 1938 <string name="tv_multiple_tracks_test_verify_set_caption_enabled"> 1939 Captions are enabled. 1940 </string> 1941 <string name="tv_multiple_tracks_test_verify_select_subtitle"> 1942 The English closed caption track should be selected. 1943 </string> 1944 <string name="tv_multiple_tracks_test_select_audio"> 1945 Select the \"Launch TV app\" button. Verify that the audio track is English by default. 1946 Select Spanish audio track. 1947 </string> 1948 <string name="tv_multiple_tracks_test_verify_select_audio"> 1949 The Spanish audio track should be selected. 1950 </string> 1951 1952 <string name="tv_time_shift_test">TV app time shift test</string> 1953 <string name="tv_time_shift_test_info"> 1954 This test verifies that the TV app invokes proper time shift APIs in the framwork. 1955 </string> 1956 <string name="tv_time_shift_test_pause_resume"> 1957 Press the \"Launch TV app\" button. Verify that the playback control is available. 1958 Pause the playback and then resume it. 1959 </string> 1960 <string name="tv_time_shift_test_verify_resume_after_pause"> 1961 The playback should be resumed after pause. 1962 </string> 1963 <string name="tv_time_shift_test_verify_position_tracking"> 1964 The playback position tracking should be activated. 1965 </string> 1966 <string name="tv_time_shift_test_speed_rate"> 1967 Press the \"Launch TV app\" button. Verify that the playback control is available. 1968 Rewind the playback and in a few seconds fast-forward it. 1969 </string> 1970 <string name="tv_time_shift_test_verify_rewind"> 1971 The playback should be rewinded. 1972 </string> 1973 <string name="tv_time_shift_test_verify_fast_forward"> 1974 The playback should be fast-forwarded. 1975 </string> 1976 <string name="tv_time_shift_test_seek"> 1977 Press the \"Launch TV app\" button. Verify that the playback control is available. 1978 Seek to previous and then seek to next. 1979 </string> 1980 <string name="tv_time_shift_test_verify_seek_to_previous"> 1981 The playback position should be moved to the previous position. 1982 </string> 1983 <string name="tv_time_shift_test_verify_seek_to_next"> 1984 The playback position should be moved to the next position. 1985 </string> 1986 1987 <string name="overlay_view_text">Overlay View Dummy Text</string> 1988 <string name="fake_rating">Fake</string> 1989 1990 <!-- A list of fully-qualified test classes that should not be run. --> 1991 <string-array name="disabled_tests" /> 1992 1993 <!-- Strings for screen pinning test --> 1994 <string name="screen_pinning_test">Screen Pinning Test</string> 1995 <string name="screen_pin_instructions">Pressing next will prompt you to enter screen pinning, allow this app to enter screen pinning.</string> 1996 <string name="screen_pin_check_pinned">Press Next to verify the app is pinned.</string> 1997 <string name="screen_pin_no_exit">Try to leave the app without unpinning the screen. Press next once you have verified you cannot leave.</string> 1998 <string name="screen_pin_exit">Use interactions defined by your device to unpin such as long pressing the back and overview button, then press next.</string> 1999 <string name="screen_pinning_done">All tests completed successfully.</string> 2000 2001 <string name="error_screen_no_longer_pinned">The screen was no longer pinned.</string> 2002 <string name="error_screen_already_pinned">Cannot start the test with the screen already pinned.</string> 2003 <string name="error_screen_pinning_did_not_start">Screen was not pinned.</string> 2004 <string name="error_screen_pinning_did_not_exit">Screen was not unpinned.</string> 2005 <string name="error_screen_pinning_couldnt_exit">Could not exit screen pinning through API.</string> 2006 2007 <!-- Audio Devices Notifcations Test --> 2008 <string name="audio_devices_notifications_test">Audio Devices Notifications Test</string> 2009 <string name="audio_devices_notification_instructions"> 2010 Click the "Clear Messages" button then connect and disconnect a wired headset. 2011 Note if the appropriate notification messages appear below. 2012 </string> 2013 <string name="audio_dev_notification_clearmsgs">Clear Messages</string> 2014 <string name="audio_dev_notification_connectMsg">CONNECT DETECTED</string> 2015 <string name="audio_dev_notification_disconnectMsg">DISCONNECT DETECTED</string> 2016 2017 <!-- Audio Routing Notifcations Test --> 2018 <string name="audio_routingnotifications_test">Audio Routing Notifications Test</string> 2019 <string name="audio_dev_routingnotification_instructions"> 2020 Click on the "Play" button in the AudioTrack Routing Notifictions section below to 2021 start (silent) playback. Insert a wired headset. Observe a message acknowledging the 2022 rerouting event below. Remove the wired headset and observe the new routing message. 2023 Click on the "Stop" button to stop playback.\n 2024 Repeat the process with "Record" and "Stop" button in the AudioRecord Routing 2025 Notifications section below. 2026 </string> 2027 <string name="audio_routingnotification_playBtn">Play</string> 2028 <string name="audio_routingnotification_playStopBtn">Stop</string> 2029 <string name="audio_routingnotification_recBtn">Record</string> 2030 <string name="audio_routingnotification_recStopBtn">Stop</string> 2031 <string name="audio_routingnotification_playHeader">AudioTrack Routing Notifications</string> 2032 <string name="audio_routingnotification_recHeader">AudioRecord Routing Notifications</string> 2033 <string name="audio_routingnotification_trackRoutingMsg">AudioTrack rerouting</string> 2034 <string name="audio_routingnotification_recordRoutingMsg">AudioRecord rerouting</string> 2035 2036 <!-- Audio Loopback Latency Test --> 2037 <string name="audio_loopback_test">Audio Loopback Latency Test</string> 2038 <string name="audio_loopback_info"> 2039 This test requires the Loopback Plug. Please connect a Loopback Plug on the headset 2040 connector, and proceed with the instructions on the screen. 2041 The system will measure the input-output audio latency by injecting a pulse on the output, 2042 and computing the distance between replicas of the pulse. 2043 You can vary the Audio Level slider to ensure the pulse will feed back at adecuate levels. 2044 Repeat until a confidence level >= 0.6 is achieved. 2045 </string> 2046 <string name="audio_loopback_instructions"> 2047 Please connect a "Loopback Plug" and press "Loopback Plug Ready". 2048 </string> 2049 <string name="audio_loopback_plug_ready_btn">Loopback Plug Ready</string> 2050 <string name="audio_loopback_instructions2"> 2051 Set the audio level to a suitable value, then press Test button. 2052 It might require multiple tries until a confidence >= 0.6 is achieved. 2053 </string> 2054 <string name="audio_loopback_level_text">Audio Level</string> 2055 <string name="audio_loopback_test_btn">Test</string> 2056 <string name="audio_loopback_results_text">Results...</string> 2057 2058 <!-- Audio Frequency Line Test --> 2059 <string name="audio_frequency_line_test">Audio Frequency Line Test</string> 2060 <string name="audio_frequency_line_info"> 2061 The system will measure the frequency response of the left and right line outputs, 2062 by feeding them back thru the microphone conection with the loopback jack. 2063 This test requires the Loopback Plug. Please connect a Loopback Plug on the headset 2064 connector, and proceed with the instructions on the screen. 2065 </string> 2066 <string name="audio_frequency_line_instructions"> 2067 Please connect a "Loopback Plug" and press "Loopback Plug Ready". 2068 </string> 2069 <string name="audio_frequency_line_plug_ready_btn">Loopback Plug Ready</string> 2070 2071 <string name="audio_frequency_line_test_btn">Test</string> 2072 <string name="audio_frequency_line_results_text">Results...</string> 2073 2074 <!-- Audio Frequency Speaker Test --> 2075 <string name="audio_frequency_speaker_test">Audio Frequency Speaker Test</string> 2076 <string name="audio_frequency_speaker_info"> 2077 This test requires an external USB reference microphone. Please connect the USB microphone and proceed with the instructions on the screen. 2078 The system will measure frequency response of the left and right speakers (if there are two speakers), or twice the response of the mono speaker. 2079 </string> 2080 <string name="audio_frequency_speaker_instructions"> 2081 Please connect an USB reference microphone and press "USB Reference microphone ready" 2082 </string> 2083 <string name="audio_frequency_speaker_usb_status">Waiting for USB microphone...</string> 2084 <string name="audio_frequency_speaker_mic_ready_btn">USB Reference microphone ready</string> 2085 <string name="audio_frequency_speaker_mic_ready_text">USB Audio device detected\n\nPlease set up Device Under test 2086 in quiet room, and Microphone 20 cms perpendicular to center of screen, then press TEST</string> 2087 <string name="audio_frequency_speaker_mic_not_ready_text">"No USB Audio device detected. Please reconnect."</string> 2088 <string name="audio_frequency_speaker_test_btn">Test</string> 2089 <string name="audio_frequency_speaker_results_text">Results...</string> 2090 2091 <!-- Audio Frequency Microphone Test --> 2092 <string name="audio_frequency_mic_test">Audio Frequency Microphone Test</string> 2093 <string name="audio_frequency_mic_info"> 2094 This test requires an external USB reference microphone and external speakers. 2095 Please use the headphone connector to connect external speakers. Position the device 40 cms 2096 from the speakers and proceed with the instructions on the screen. 2097 The system will measure frequency response of the built in microphone. 2098 </string> 2099 <string name="audio_frequency_mic_instructions"> 2100 Please connect external speakers using the headphone connector. Please unplug any USB audio device (if any) 2101 </string> 2102 <string name="audio_frequency_mic_speakers_ready_btn">External speakers ready</string> 2103 <string name="audio_frequency_mic_speakers_ready_status">...</string> 2104 <string name="audio_frequency_mic_instructions2"> 2105 Please position the speakers 40 cms from the device under test and press TEST 1 2106 </string> 2107 <string name="audio_frequency_mic_test1_btn">Test 1</string> 2108 <string name="audio_frequency_mic_usb_status">Waiting for USB microphone...</string> 2109 <string name="audio_frequency_mic_connect_mic">Please Connect USB microphone, position it next to 2110 the built in microphone in the device and press USB reference microphone</string> 2111 <string name="audio_frequency_mic_mic_ready_btn">USB Reference microphone ready</string> 2112 <string name="audio_frequency_mic_mic_ready_text">USB Audio device detected\n\nPlease set up Device Under test 2113 in quiet room, and Microphone 20 cms perpendicular to center of screen, then press TEST</string> 2114 <string name="audio_frequency_mic_mic_not_ready_text">"No USB Audio device detected. Please reconnect."</string> 2115 <string name="audio_frequency_mic_test2_btn">Test 2</string> 2116 <string name="audio_frequency_mic_results_text">Results...</string> 2117 2118 </resources> 2119
