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 xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2"> 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_telecom">Telecom</string> 42 <string name="test_category_telephony">Telephony</string> 43 <string name="test_category_tv">TV</string> 44 <string name="test_category_other">Other</string> 45 <string name="clear">Clear</string> 46 <string name="test_results_clear_title">Remove all test results?</string> 47 <string name="test_results_clear_yes">Yes</string> 48 <string name="test_results_clear_cancel">Cancel</string> 49 <string name="test_results_cleared">Test results cleared.</string> 50 <string name="view">View</string> 51 <string name="test_results_error">Couldn\'t create test results report.</string> 52 <string name="runtime_permissions_error">Cannot continue. Please grant runtime permissions</string> 53 <string name="export">Export</string> 54 <string name="no_storage">Cannot save report to external storage, see log for details.</string> 55 <string name="report_saved">Report saved to: %s</string> 56 57 <!-- Strings for IntentDrivenTestActivity --> 58 <string name="intent_not_resolved">Intent Not Resolved</string> 59 <string name="intent_not_resolved_info">The following intent could not be resolved: %1$s</string> 60 61 <!-- Strings for ReportViewerActivity --> 62 <string name="report_viewer">Report Viewer</string> 63 64 <!-- String shared between BackupTestActivity and BackupAccessibilityTestActivity --> 65 <string name="bu_loading">Loading...</string> 66 <string name="bu_generate_error">Error occurred while generating test data...</string> 67 <string name="bu_settings">Settings</string> 68 69 <!-- Strings for Device Administration tests --> 70 <string name="da_policy_serialization_test">Policy Serialization Test</string> 71 <string name="da_policy_serialization_info">This test checks that a device policy is properly 72 saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create 73 a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the 74 device and verify that all rows in the policy list are green. Red items indicate policy 75 settings that were not loaded properly. 76 </string> 77 <string name="da_uninstall_test">Device Admin Uninstall Test</string> 78 <string name="da_uninstall_test_info">This test checks that an active device administrator 79 can be easily uninstalled from the application details screen in a way similar to other 80 apps. This test requires CtsEmptyDeviceAdmin.apk to be installed on the device. 81 </string> 82 <string name="da_tapjacking_test">Device Admin Tapjacking Test</string> 83 <string name="da_tapjacking_test_info">This test checks that an activity cannot tapjack the 84 user by obscuring the device admin details while prompting the user to activate the admin. 85 </string> 86 <string name="car_dock_test">Car Dock Test</string> 87 <string name="car_dock_test_desc">This test ensures that car mode opens the app associated with 88 car dock when going into car mode.\n\n 89 Click on "Enable Car Mode" to start the test. Clicking on the button will either bring up a 90 disambiguation dialog asking which app to open or immediately open the CAR_DOCK application. 91 Select the "CTS Verifier" app and then "Always" if the dialog pops up. 92 This will open the CAR_DOCK application.\n\n 93 In the CAR_DOCK application, press the home button, which will enable the pass button if the 94 framework correctly tries to open the CAR_DOCK app again.</string> 95 <string name="car_mode_enable">Enable Car Mode</string> 96 <string name="car_dock_activity_text">Press the Home button</string> 97 <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device 98 policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your 99 device and return to this test in the CTS Verifier. 100 </string> 101 <string name="da_generate_policy">Generate Policy</string> 102 <string name="da_apply_policy">Apply Policy</string> 103 <string name="da_random_policy">Random policy generated.</string> 104 <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string> 105 <string name="da_password_quality">Password Quality</string> 106 <string name="da_password_quality_alphabetic">Alphabetic</string> 107 <string name="da_password_quality_alphanumeric">Alphanumeric</string> 108 <string name="da_password_quality_numeric">Numeric</string> 109 <string name="da_password_quality_something">Something</string> 110 <string name="da_password_minimum_length">Minimum Password Length</string> 111 <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string> 112 <string name="da_maximum_time_to_lock">Maximum Time to Lock</string> 113 <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string> 114 115 <string name="da_screen_lock_test">Screen Lock Test</string> 116 <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow 117 method immediately locks the screen. It should lock the screen immediately despite any 118 settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen. 119 Your screen should be locked and require the password to be entered. 120 </string> 121 <string name="da_kg_disabled_features_test">Keyguard Disabled Features Test</string> 122 <string name="rn_kg_disabled_features_test">Redacted Notifications Keyguard Disabled Features Test</string> 123 <string name="da_force_lock">Force Lock</string> 124 <string name="da_lock_success">It appears the screen was locked successfully!</string> 125 <string name="da_lock_error">It does not look like the screen was locked...</string> 126 127 <string name="da_install_admin_instructions"> 128 Please install the \'Test Device Admin\' app (packaged as CtsEmptyDeviceAdmin.apk) on the device. 129 </string> 130 <string name="da_admin_installed_status_text">\'Test Device Admin\' installed on the device.</string> 131 <string name="da_enable_admin_instructions">Add \'Test Device Admin\' as an active administrator on the device. 132 Tap the button below to review the device admin details and activate the administrator. 133 </string> 134 <string name="da_enable_admin_button_text">Enable admin</string> 135 <string name="da_uninstall_admin_instructions">Attempt to uninstall the app from the application details page of the \'Test Device Admin\' app. 136 You should see another screen showing the device admin details before you can uninstall the app from the device. 137 Wait till the app is uninstalled before returning to this page. 138 </string> 139 <string name="da_uninstall_admin_button_text">Launch settings</string> 140 141 <string name="da_tapjacking_overlay_app_description">This activity attempts to tapjack the activity below.\n 142 Any security sensitive controls below should not respond to taps as long as this activity is visible.</string> 143 <string name="da_tapjacking_instructions"> 144 1. Launch the device admin add screen by pressing the button below.\n 145 2. Wait for an overlaying transparent activity to show up obscuring the device admin details window.\n 146 3. The button to activate the admin should be disabled and should not register any taps.\n 147 4. Press \'back\' to exit the overlaying transparent activity.\n 148 5. Press \'back\' to exit the device admin details and return to this screen.\n 149 Pass the test if the device admin could not be activated while the details 150 window was being obscured. 151 </string> 152 <string name="da_tapjacking_button_text">Enable device admin</string> 153 154 <!-- Strings for lock bound keys test --> 155 <string name="sec_lock_bound_key_test">Lock Bound Keys Test</string> 156 <string name="sec_lock_bound_key_test_info"> 157 This test ensures that Keystore cryptographic keys that are bound to lock screen authentication 158 are unusable without a recent enough authentication. You need to set up a screen lock in order to 159 complete this test. If available, this test should be run by using fingerprint authentication 160 as well as PIN/pattern/password authentication. 161 </string> 162 <string name="sec_fingerprint_bound_key_test">Fingerprint Bound Keys Test</string> 163 <string name="sec_fingerprint_bound_key_test_info"> 164 This test ensures that Keystore cryptographic keys that are bound to fingerprint authentication 165 are unusable without an authentication. You need to set up a fingerprint order to 166 complete this test. 167 </string> 168 <string name="sec_fp_dialog_message">Authenticate now with fingerprint</string> 169 <string name="sec_fp_auth_failed">Authentication failed</string> 170 <string name="sec_start_test">Start Test</string> 171 <string name="sec_fingerprint_dialog_bound_key_test">Fingerprint Bound Keys Test (System Dialog)</string> 172 173 <!-- Strings for BluetoothActivity --> 174 <string name="bluetooth_test">Bluetooth Test</string> 175 <string name="bluetooth_test_info"> 176 The Bluetooth Control tests check whether or not the device 177 can disable and enable Bluetooth properly. 178 \n\nThe Bluetooth tests require two devices, and Bluetooth data is exchanged between them. 179 \nThere are two types of connections: Insecure and Secure. There are two types of roles: Server and Client. You must pass all connection and role combinations. 180 \nThis is a list of the tests: 181 \nThis Device x Other Device 182 \n\n\"Bluetooth LE Insecure Client Test\" x \"Bluetooth LE Insecure Server Test\" 183 \n\n\"Bluetooth LE Insecure Server Test\" x \"Bluetooth LE Insecure Client Test\" 184 \n\n\"Bluetooth LE Secure Client Test\" x \"Bluetooth LE Secure Server Test\" 185 \n\n\"Bluetooth LE Secure Server Test\" x \"Bluetooth LE Secure Client Test\" 186 \n\nThe Device Communication tests require two 187 devices to pair and exchange messages. The two devices must be: 188 \n\n1. a candidate device implementation running the software build to be tested 189 \n\n2. a separate device implementation already known to be compatible 190 </string> 191 192 <string name="bt_control">Bluetooth Control</string> 193 <string name="bt_device_communication">Device Communication</string> 194 <string name="bt_le">Bluetooth LE</string> 195 <string name="bt_hid">Bluetooth HID</string> 196 197 <string name="bt_toggle_bluetooth">Toggle Bluetooth</string> 198 <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string> 199 <string name="bt_enable_bluetooth">Enable Bluetooth</string> 200 <string name="bt_disable_bluetooth">Disable Bluetooth</string> 201 <string name="bt_disabling">Disabling Bluetooth...</string> 202 <string name="bt_disabling_error">Could not disable Bluetooth...</string> 203 204 <string name="bt_connection_access_server">Connection Access Server</string> 205 <string name="bt_connection_access_client">Connection Access Client</string> 206 <string name="bt_connection_access_server_info"> 207 Start the CTS Verifier on another device, start the Bluetooth test, and choose 208 \"Connection Access Client\" to setup the test. 209 \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together 210 using the \"Make Discoverable\" and \"Pick Server\" buttons. 211 \n\nA connection access request should appear on the server and enable the pass button. 212 </string> 213 <string name="bt_connection_access_client_info"> 214 Start the CTS Verifier on another device, start the Bluetooth test, and choose 215 \"Connection Access Server\" to complete the test. 216 \n\nMake the device acting as the server discoverable and connect to it via the 217 \"Pick Server\" button. Check that the server displays the connection access request 218 dialog. The client device does not need to do anything else. 219 </string> 220 <string name="bt_ca_dialog">Was the connection access request dialog shown?</string> 221 <string name="bt_ca_tips"> 222 Tap the \"Bluetooth Settings\" button and check that both devices are not paired 223 before running the test. 224 \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth 225 devices together and start the test. 226 </string> 227 228 <!-- Strings for HidHost and HidDevice activity --> 229 <string name="bt_hid_host_test_name">Bluetooth HID Host Test</string> 230 <string name="bt_hid_host_test_info"> 231 Start the CTS Verifier on another device, start the Bluetooth test, and choose 232 \"Bluetooth HID Device\" to complete the test. 233 \n\nClick \"Register app\" and \"Make discoverable\" on another device first, and click 234 \"Select device\". Choose the device from device picker. If the remote device is already 235 paired, unpair it first from system Settings. 236 \n\nAfter the remote device completes the \"Send_report\" command, text \"bluetooth\" should 237 appear in the EditText. Mark the test as passed. 238 \n\n If the device under test (DUT) does not have Bluetooth HID Host service or HID Device 239 service enabled, mark the test as passed. 240 </string> 241 <string name="bt_hid_host">Bluetooth HID Host</string> 242 <string name="bt_hid_host_select_device">Select device</string> 243 244 <string name="bt_hid_device_test_name">Bluetooth HID Device Test</string> 245 <string name="bt_hid_device_test_info"> 246 Start the CTS Verifier on another device, start the Bluetooth test, and choose 247 \"Bluetooth HID Host\" to complete the test. 248 \n\nFirst, click the \"Register app\" button, and click the \"Make discoverable\" button. 249 \n\nThen, on another device, click the \"Select device" button, and choose this device. 250 \n\nWait until the dialog shows up for pairing two devices. 251 \n\nFinally, click the \"Test send_report\", \"Test reply_report\", \"Test report_error\". 252 \n\nIf all the commands are successful, then click \"Unregister app\" and mark the test as 253 passed. 254 \n\n If the device under test (DUT) does not have Bluetooth HID Host service or HID Device 255 service enabled, mark the test as passed. 256 </string> 257 258 <string name="bt_hid_device">Bluetooth HID Device</string> 259 <string name="bt_hid_device_register">Register app</string> 260 <string name="bt_hid_device_unregister">Unregister app</string> 261 <string name="bt_hid_device_send_report">Test Send_report</string> 262 <string name="bt_hid_device_reply_report">Test Reply_report</string> 263 <string name="bt_hid_device_report_error">Test Report_error</string> 264 265 266 <string name="bt_secure_server">Secure Server</string> 267 <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> 268 <string name="bt_insecure_server">Insecure Server</string> 269 <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> 270 <string name="bt_waiting">Waiting for client...</string> 271 <string name="bt_listening">Listening...</string> 272 <string name="bt_connecting">Connecting...</string> 273 <string name="bt_connected">Connected</string> 274 <string name="bt_received_messages">Received Messages</string> 275 <string name="bt_sent_messages">Sent Messages</string> 276 <string name="bt_no_messages">No messages</string> 277 <string name="bt_make_discoverable">Make Discoverable</string> 278 <string name="bt_pick_server">Pick Server</string> 279 <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string> 280 <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string> 281 <string name="bt_advertise_unsupported_title">Advertising is not supported</string> 282 <string name="bt_advertise_unsupported_message">Advertising is not supported on this device.\nTest finishes.</string> 283 <string name="bt_open_failed_title">BLE open failed</string> 284 <string name="bt_open_failed_message">Cannot open BLE GattService.\nTest finishes.</string> 285 <string name="bt_add_service_failed_title">Add service failed</string> 286 <string name="bt_add_service_failed_message">Failed to add services.\nTest finishes.</string> 287 288 <string name="bt_secure_client">Secure Client</string> 289 <string name="bt_insecure_client">Insecure Client</string> 290 291 <string name="bt_device_picker">Device Picker</string> 292 <string name="bt_paired_devices">Paired Devices</string> 293 <string name="bt_new_devices">New Devices</string> 294 <string name="bt_no_devices">No devices</string> 295 <string name="bt_scan">Scan for Devices</string> 296 <string name="bt_scanning">Scanning...</string> 297 <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> 298 <string name="bt_settings">Bluetooth Settings</string> 299 300 <!-- BLE client side strings --> 301 <string name="ble_client_service_name">Bluetooth LE GATT Client Handler Service</string> 302 <string name="ble_client_test_name">01 Bluetooth LE Client Test</string> 303 <string name="ble_client_connect_name">Bluetooth LE Client Connect</string> 304 <string name="ble_discover_service_name">Bluetooth LE Discover Service</string> 305 <string name="ble_read_characteristic_name">Bluetooth LE Read Characteristic</string> 306 <string name="ble_write_characteristic_name">Bluetooth LE Write Characteristic</string> 307 <string name="ble_reliable_write_name">Bluetooth LE Reliable Write</string> 308 <string name="ble_reliable_write_bad_resp_name">Bluetooth LE Reliable Write (receive bad response)</string> 309 <string name="ble_notify_characteristic_name">Bluetooth LE Notify Characteristic</string> 310 <string name="ble_read_descriptor_name">Bluetooth LE Read Descriptor</string> 311 <string name="ble_write_descriptor_name">Bluetooth LE Write Descriptor</string> 312 <string name="ble_read_rssi_name">Bluetooth LE Read RSSI</string> 313 <string name="ble_client_disconnect_name">Bluetooth LE Client Disconnect</string> 314 <string name="ble_insecure_client_test_info"> 315 The Bluetooth LE test must be done simultaneously on two devices. This device is the client. 316 All tests listed here must be done without pairing. 317 </string> 318 <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> 319 <string name="ble_discover_service_info">Verify that the service is discovered when you press the "Discover Service" button.</string> 320 <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> 321 <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> 322 <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> 323 <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> 324 <string name="ble_client_disconnect_info">Verify that the device is disconnected when you press the "Disconnect" button</string> 325 <string name="ble_address">Bluetooth address</string> 326 <string name="ble_connect">Connect</string> 327 <string name="ble_discover_service">Discover service</string> 328 <string name="ble_write_hint">Nothing to write yet</string> 329 <string name="ble_read_hint">Nothing read yet</string> 330 <string name="ble_write">Write</string> 331 <string name="ble_read">Read</string> 332 <string name="ble_begin_write">Begin write</string> 333 <string name="ble_execute_write">Execute write</string> 334 <string name="ble_begin_notification">Begin notification</string> 335 <string name="ble_stop_notification">Stop notification</string> 336 <string name="ble_waiting_notification">Waiting on notification</string> 337 <string name="ble_read_rssi">Read RSSI</string> 338 <string name="ble_disconnect">Disconnect</string> 339 <string name="ble_test_text">TEST</string> 340 <string name="ble_test_finished">Test finished</string> 341 <string name="ble_test_next">Next</string> 342 <string name="ble_test_running">Test Running</string> 343 <string name="ble_test_running_message">This test requires a few minutes. Don\'t interrupt the test.</string> 344 <string name="ble_mtu_23_name">Bluetooth LE Request MTU(23bytes)</string> 345 <string name="ble_mtu_512_name">Bluetooth LE Request MTU(512bytes)</string> 346 347 <!-- BLE server side strings --> 348 <string name="ble_server_service_name">Bluetooth LE GATT Server Handler Service</string> 349 <string name="ble_server_start_name">01 Bluetooth LE Server Test</string> 350 <string name="ble_server_start_info"> 351 The Bluetooth LE test must be done simultaneously on two devices, a server device and a client device. This device is the server. 352 </string> 353 <string name="ble_server_receiving_connect">Waiting on connection from Bluetooth LE client.</string> 354 <string name="ble_server_add_service">Adding service to Bluetooth LE server.</string> 355 <string name="ble_server_write_characteristic">Waiting on write characteristic request</string> 356 <string name="ble_server_read_characteristic">Waiting on read characteristic request</string> 357 <string name="ble_server_write_descriptor">Waiting on write descriptor request</string> 358 <string name="ble_server_read_descriptor">Waiting on read descriptor request</string> 359 <string name="ble_server_reliable_write">Waiting on reliable write from client</string> 360 <string name="ble_server_reliable_write_bad_resp">Waiting on reliable write from client (send bad response)</string> 361 <string name="ble_server_receiving_disconnect">Waiting on disconnection from Bluetooth LE client</string> 362 <string name="ble_connection_priority_server_name">02 Bluetooth LE Connection Priority Server Test</string> 363 <string name="ble_connection_priority_server_info">Bluetooth LE Connection Priority Server receive message from message in 3 different priority.</string> 364 <string name="ble_server_notify_characteristic">Waiting on notify characteristic request</string> 365 <string name="ble_server_write_characteristic_without_permission">Waiting on write characteristic request without permission</string> 366 <string name="ble_server_read_characteristic_without_permission">Waiting on read characteristic request without permission</string> 367 <string name="ble_server_write_descriptor_without_permission">Waiting on write descriptor request without permission</string> 368 <string name="ble_server_read_descriptor_without_permission"> Waiting on read descriptor request without permission</string> 369 <string name="ble_server_write_characteristic_need_encrypted">Waiting on write encrypted characteristic request</string> 370 <string name="ble_server_read_characteristic_need_encrypted">Waiting on read encryptedcharacteristic request</string> 371 <string name="ble_server_write_descriptor_need_encrypted">Waiting on write encrypted descriptor request</string> 372 <string name="ble_server_read_descriptor_need_encrypted"> Waiting on read encrypted descriptor request</string> 373 <string name="ble_server_indicate_characteristic">Waiting on indicate characteristic request</string> 374 <string name="ble_server_mtu_23bytes">Waiting on MTU request(23 bytes)</string> 375 <string name="ble_server_mtu_512bytes">Waiting on MTU request(512 bytes)</string> 376 <string name="ble_encrypted_server_name">03 Bluetooth LE Encrypted Server Test</string> 377 <string name="ble_encrypted_server_info">Bluetooth LE Encrypted Server Waiting on read/write characteristic and descriptor request need encrypted.</string> 378 <string name="ble_insecure_server_enctypted_info">Bluetooth LE Server is in operation.\nThis test does not change server state.\n\nIf Bluetooth pairing request was notified by system, you must cancel it.\n\nOnce the client tests are all successful, please change the state of the server-side to the "success".</string> 379 <string name="ble_insecure_server_test_list_name">Bluetooth LE Insecure Server Test</string> 380 <string name="ble_insecure_server_test_list_info"> 381 This test is mostly automated, but requires some user interaction. 382 Once the list items below have check marks, the test is complete. 383 \n\nTap \"01 Bluetooth LE Server Test\" on this device, then tap \"01 Bluetooth LE Client Test\" on the other device. 384 \nWhen the test is complete, move to the next item. You must complete all tests. 385 </string> 386 <string name="ble_secure_server_test_list_name">Bluetooth LE Secure Server Test</string> 387 <string name="ble_secure_server_test_list_info"> 388 This test is mostly automated, but requires some user interaction. 389 You can pass this test once the list items below are checked. 390 \n\nTap \"01 Bluetooth LE Server Test\" on this device, then tap \"01 Bluetooth LE Client Test \"on other device. 391 \nTest completed, then test next item. You must be done all tests. 392 </string> 393 394 <!-- BLE advertiser side strings --> 395 <string name="ble_advertiser_test_name">Bluetooth LE Advertiser Test</string> 396 <string name="ble_advertiser_test_info"> 397 The Bluetooth LE Advertiser Test and Scanner Test is a paired test. 398 \nTap \"Bluetooth LE Advertiser Test\" on this device. Once it is passed, tap \"Bluetooth LE Scanner Test\". 399 \nTap \"Bluetooth LE Scanner Test\" on this device. Once it is passed, tap \"Bluetooth LE Advertiser Test\". 400 </string> 401 <string name="ble_advertiser_service_name">Bluetooth LE Advertiser Handler Service</string> 402 <string name="ble_privacy_mac_name">Bluetooth LE Privacy Mac</string> 403 <string name="ble_privacy_mac_info">Bluetooth LE Advertiser should advertise in non-repeating MAC address.</string> 404 <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 Bluetooth LE advertising.</string> 405 <string name="ble_power_level_name">Bluetooth LE Tx Power Level</string> 406 <string name="ble_power_level_info">Bluetooth LE Advertiser advertises in 4 different power levels. Scanner should receive them in different strength of Rssi, cannot receive weak signals beyond several feet.</string> 407 <string name="ble_advertiser_power_level_instruction"> 408 Click start to start multi-advertising. Data packets are advertised in 4 different power levels. 409 You may receive a message that this device does not support multi-advertising. 410 If the advertiser does not advertise in 4 power levels, and you do not receive an error message, 411 you may not have stopped advertising in the previous test, or this device may not support 4 advertisers at the same time. 412 Try rebooting the device and running the test again to free those advertisers in use. 413 </string> 414 <string name="ble_advertiser_scan_filter_name">Bluetooth LE Hardware Scan Filter</string> 415 <string name="ble_advertiser_scan_filter_info">Bluetooth LE 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> 416 <string name="ble_advertiser_scannable">Scannable advertising</string> 417 <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> 418 <string name="ble_advertiser_unscannable">Unscannble advertising</string> 419 <string name="ble_advertiser_unscannable_instruction">Start unscannable advertising, expect scanner stay calm on Monsoon monitor, no log of GattService from scanner logcat.</string> 420 <string name="ble_advertiser_start">Start</string> 421 <string name="ble_advertiser_stop">Stop</string> 422 423 <!-- BLE scanner side strings --> 424 <string name="ble_scanner_test_name">Bluetooth LE Scanner Test</string> 425 <string name="ble_scanner_service_name">Bluetooth LE Scanner Handler Service</string> 426 <string name="ble_scanner_test_info">The Bluetooth LE test must be done simultaneously on two devices, an advertiser and a scanner. This device is the scanner.</string> 427 <string name="ble_scanner_privacy_mac">Hold for 15 min to see if receive a different MAC address from advertiser.</string> 428 <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> 429 <string name="ble_ultra_low">Ultra low</string> 430 <string name="ble_low">Low</string> 431 <string name="ble_medium">Medium</string> 432 <string name="ble_high">High</string> 433 <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 mac address.</string> 434 <string name="ble_scanner_scan_filter_name">BLE Hardware Scan Filter</string> 435 <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> 436 <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> 437 <string name="ble_scan_with_filter">Scan with filter</string> 438 <string name="ble_scan_without_filter">Scan without filter</string> 439 <string name="ble_scan_start">Start scan</string> 440 <string name="ble_scan_stop">Stop scan</string> 441 442 <!-- BLE connection priority test strings --> 443 <string name="ble_client_connection_priority">Testing priority: </string> 444 <string name="ble_connection_priority_balanced">BALANCED</string> 445 <string name="ble_connection_priority_high">HIGH</string> 446 <string name="ble_connection_priority_low">LOW</string> 447 <string name="ble_server_connection_priority_result_passed">All test passed</string> 448 <string name="ble_server_connection_priority_result_failed">Test failed.</string> 449 <string name="ble_server_connection_priority_result_intervals"> 450 Transfer interval time (msec):\nHIGH=%1$d\nBALANCED=%2$d\nLOW=%3$d\n\nRequirements:\n HIGH <= BALANCED <= LOW 451 </string> 452 453 <!-- BLE Test Name --> 454 <string name="ble_secure_client_test_name">Bluetooth LE Secure Client Test</string> 455 <string name="ble_insecure_client_test_name">Bluetooth LE Insecure Client Test</string> 456 <string name="ble_secure_server_test_name">Bluetooth LE Secure Server Test</string> 457 <string name="ble_insecure_server_test_name">Bluetooth LE Insecure Server Test</string> 458 459 <string name="ble_read_characteristic_nopermission_name">Bluetooth LE Read Characteristic Without Perrmission</string> 460 <string name="ble_write_characteristic_nopermission_name">Bluetooth LE Write Characteristic Without Permission</string> 461 <string name="ble_read_descriptor_nopermission_name">Bluetooth LE Read Descriptor Without Perrmission</string> 462 <string name="ble_write_descriptor_nopermission_name">Bluetooth LE Write Descriptor Without Permission</string> 463 <string name="ble_connection_priority_client_name">02 Bluetooth LE Connection Priority Client Test</string> 464 <string name="ble_connection_priority_client_info">Bluetooth LE Connection Priority Client send message in 3 different priority.</string> 465 <string name="ble_read_authenticated_characteristic_name">Bluetooth LE Read Encrypted Characteristic</string> 466 <string name="ble_write_authenticated_characteristic_name">Bluetooth LE Write Encrypted Characteristic</string> 467 <string name="ble_read_authenticated_descriptor_name">Bluetooth LE Read Encrypted Descriptor</string> 468 <string name="ble_write_authenticated_descriptor_name">Bluetooth LE Write Encrypted Descriptor</string> 469 <string name="ble_connection_priority_client_high">Bluetooth LE Send With CONNECTION_PRIORITY_HIGH</string> 470 <string name="ble_connection_priority_client_low">Bluetooth LE Send With CONNECTION_PRIORITY_LOW_POWER</string> 471 <string name="ble_connection_priority_client_balanced">Bluetooth LE Send With CONNECTION_PRIORITY_BALANCED</string> 472 <string name="ble_indicate_characteristic_name">Bluetooth LE Indicate Characteristic</string> 473 <string name="ble_encrypted_client_name">03 Bluetooth LE Encrypted Client Test</string> 474 <string name="ble_encrypted_client_info">Bluetooth LE Encrypted Client read/write on characteristic and descriptor need encrypted.</string> 475 <string name="ble_insecure_client_test_list_name">Bluetooth LE Insecure Client Test</string> 476 <string name="ble_insecure_client_test_list_info"> 477 The Bluetooth LE test must be done simultaneously on two devices. This device is the client. 478 All tests listed here must be done without pairing. Tap \"Bluetooth LE Insecure Server Test\" on the other device. 479 \n\nTap \"01 Bluetooth LE Client Test\" on this device, then tap \"01 Bluetooth LE Server Test\" on the other device. 480 \nWhen the test is complete, move to the next item. You must complete all tests. 481 </string> 482 <string name="ble_secure_client_test_list_name">Bluetooth LE Secure Client Test</string> 483 <string name="ble_secure_client_test_list_info"> 484 The Bluetooth LE test must be done simultaneously on two devices. 485 This device is the client. All tests listed here must be done with pairing. 486 \n\nTap \"01 Bluetooth LE Client Test\" on this device, then tap \"01 Bluetooth LE Server Test\" on the other device. 487 \nWhen the test is complete, move to the next item. You must complete all tests. 488 </string> 489 <string name="ble_encrypted_client_no_encrypted_characteristic">Error!\nThe Characteristics unencrypted.</string> 490 <string name="ble_encrypted_client_no_encrypted_descriptor">Error!\nThe Descriptor unencrypted.</string> 491 <string name="ble_encrypted_client_fail_write_encrypted_characteristic">It failed to write to Characteristic.</string> 492 <string name="ble_encrypted_client_fail_write_encrypted_descriptor">It failed to write to Descriptor.</string> 493 <string name="ble_encrypted_client_fail_read_encrypted_characteristic">It failed to read the Characteristic.</string> 494 <string name="ble_encrypted_client_fail_read_encrypted_descriptor">It failed to read the Descriptor.</string> 495 <string name="ble_secure_client_test_info"> 496 The Bluetooth LE test must be done simultaneously on two devices. This device is the client. 497 All tests listed here must be done with pairing. 498 </string> 499 500 <string name="ble_bluetooth_disable_title">Bluetooth Disable!</string> 501 <string name="ble_bluetooth_disable_message">Please set bluetooth enable.</string> 502 503 <string name="ble_bluetooth_mismatch_title">Bluetooth pairing state is a mismatch!</string> 504 <string name="ble_bluetooth_mismatch_secure_message"> 505 And even though it has already been trying to run a test of Secure, the device has not been paired. 506 \nGo setting mode, set Bluetooth to pair other device. 507 </string> 508 <string name="ble_bluetooth_mismatch_insecure_message"> 509 And even though it has already been trying to run a test of Insecure, the device has already been paired. 510 \nGo setting mode, set Bluetooth to unpair other device. 511 </string> 512 513 <string name="ble_mtu_mismatch_message">MTU is not correct.(Request:%1$d, Actual:%2$d)</string> 514 <string name="ble_mtu_fail_message">MTU test: failed to receive data</string> 515 516 <string name="companion_test">Companion Device Test</string> 517 <string name="companion_test_info"> 518 This test checks that APIs to manage companion devices are working correctly, 519 including showing the dialog to the user to verify a device, as well as updating an internal 520 record once the user made the choice and then removing it.\n\n 521 Before proceeding, make sure you have a bluetooth device nearby and discoverable. 522 Also, make sure that bluetooth is turned on on this device. 523 Once you press the button, wait for a dialog to pop up and select your device from the list. 524 </string> 525 526 <!-- Strings for FeatureSummaryActivity --> 527 <string name="feature_summary">Hardware/Software Feature Summary</string> 528 <string name="feature_summary_info">This is a test for...</string> 529 <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string> 530 <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string> 531 <string name="fs_no_data">No data.</string> 532 <string name="fs_legend_good">standard feature reported by device</string> 533 <string name="fs_legend_indeterminate">optional feature not reported by device</string> 534 <string name="fs_legend_warning">non-standard feature reported by device</string> 535 <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string> 536 537 <string name="empty"></string> 538 539 <!-- Strings for HifiUltrasoundTestActivity --> 540 <string name="hifi_ultrasound_test">Hifi Ultrasound Microphone Test</string> 541 <string name="hifi_ultrasound_test_info"> 542 This is a test for near-ultrasound (18500Hz - 20000Hz) microphone response.\n 543 This test requires two devices.\n</string> 544 <string name="hifi_ultrasound_test_play">PLAY</string> 545 <string name="hifi_ultrasound_test_record">RECORD</string> 546 <string name="hifi_ultrasound_test_plot">PLOT</string> 547 <string name="hifi_ultrasound_test_dismiss">DISMISS</string> 548 <string name="hifi_ultrasound_test_ok">OK</string> 549 <string name="hifi_ultrasound_test_instruction1"> 550 Open Hifi Ultrasound Microphone Test on the test device and the reference device.\n 551 Set the media volume of the reference device at 70% and hold it with one hand.\n 552 Hold the testing device with the other hand\n 553 Press the RECORD button on the testing device, then the PLAY button on the reference device within one second.\n 554 After the test, report result on the testing (recording) device.\n</string> 555 <string name="hifi_ultrasound_test_pass">PASS</string> 556 <string name="hifi_ultrasound_test_fail">FAIL</string> 557 <string name="hifi_ultrasound_test_default_false_string">false</string> 558 <string name="hifi_ultrasound_test_mic_no_support"> 559 Device does not support near-ultrasound recording.\n 560 Please report PASS.\n</string> 561 <string name="hifi_ultrasound_test_spkr_no_support"> 562 Device does not support near-ultrasound playback.\n 563 If this is your reference device, please use a different reference device.\n</string> 564 565 <string name="hifi_ultrasound_speaker_test">Hifi Ultrasound Speaker Test</string> 566 <string name="hifi_ultrasound_speaker_test_info"> 567 This is a test for near-ultrasound (18500Hz - 20000Hz) speaker response.\n 568 This test requires two devices.\n</string> 569 <string name="hifi_ultrasound_speaker_test_instruction1"> 570 Open Hifi Ultrasound Speaker Test on the test device and the reference device.\n 571 Set the media volume of the testing device at 70% and hold it with one hand.\n 572 Hold the reference device with the other hand\n 573 Press the RECORD button on the reference device, then the PLAY button on the testing device within one second.\n 574 After the test, report result on the testing (playback) device.\n</string> 575 <string name="hifi_ultrasound_speaker_test_mic_no_support"> 576 Device does not support near-ultrasound recording.\n 577 If this is your reference device, please use a different reference device.\n</string> 578 <string name="hifi_ultrasound_speaker_test_spkr_no_support"> 579 Device does not support near-ultrasound playback.\n 580 Please report PASS.\n</string> 581 <string name="hifi_ultrasound_speaker_test_test_side"> 582 Please wait for the result on the reference device then report here.</string> 583 <string name="hifi_ultrasound_speaker_test_reference_side"> 584 Please report on the testing device.\n</string> 585 586 <!-- Strings for Location tests --> 587 <string name="location_gps_test">GPS Test</string> 588 <string name="location_gps_test_info">This test verifies basic GPS behavior 589 and callback scheduling. 590 Make sure the device has line of sight to GPS satellites 591 (for example, outside, or near a window) 592 and then press OK to run the automated tests.</string> 593 <string name="location_listener_activity">Location listener</string> 594 595 <!-- Strings for Location GNSS tests --> 596 <string name="location_gnss_constellation_type_test">GNSS Measurement Constellation Test</string> 597 <string name="location_gnss_measure_no_location_test">GNSS Measurement Before Location Test</string> 598 <string name="location_gnss_reg_test">GNSS Measurement Registration Test</string> 599 <string name="location_gnss_value_test">GNSS Measurement Values Test</string> 600 <string name="location_pseudorange_value_test">GNSS Pseudorange Test</string> 601 <string name="location_gnss_ttff_test">GNSS TTFF Test</string> 602 <string name="location_gnss_nav_msg_test">GNSS Navigation Message Test</string> 603 <string name="location_gnss_status_test">GNSS Status Test</string> 604 <string name="location_gnss_test_info">This test verifies basic GNSS behavior. 605 Make sure the device has line of sight to GNSS satellites 606 (for example, stationary on a windowsill. If needed, try again, outside, also with the 607 device stationary, and with at least some view of the sky.) and then press Next to run 608 the automated tests.</string> 609 <string name="location_emergency_call_test_info">This test verifies whether basic features 610 (wifi, sms, gps) works correctly during the emergency call. Make sure the device is using 611 a special white listed sim card. The wifi and GPS should be on and have internet connection. 612 Press the pass button to skip this test if outside US/Canada. 613 </string> 614 <string name="emergency_call_confirm_info">This test will dial 911! Please make sure to use a 615 whitelisted sim card to run this test! 616 </string> 617 <string name="emergency_call_skip_info">Current device doesn\'t support cellular network. Skipping the Test. 618 </string> 619 <string name="emergency_call_emergency_number_hint_text"> 620 Emergency Number: 621 </string> 622 <string name="emergency_call_current_number_hint_text"> 623 Current Number: 624 </string> 625 <string name="emergency_call_dial_text"> 626 Dial 911 627 </string> 628 <string name="emergency_call_emergency_number_text"> 629 911 630 </string> 631 <string name="location_gnss_test_retry_info">If this test fails, please make sure the device 632 has line of sight to GNSS satellites (for example, stationary on a windowsill. If needed, 633 try again, outside, also with the device stationary, with as much view of the sky as 634 possible.) </string> 635 <string name="location_emergency_call_gps_test">Emergency Call GPS Test</string> 636 <string name="location_emergency_call_message_test">Emergency Call Message Test</string> 637 <string name="location_emergency_call_wifi_test">Emergency Call Wifi Test</string> 638 639 <!-- Strings for ConnectivityBackgroundTestActivity --> 640 <string name="network_background_test">Network Background Connectivity Test</string> 641 <string name="network_background_test_instructions"> 642 This test verifies that IPv6 network connectivity continues to work 643 when the screen is off or is idle for some time.\n\n 644 645 1. Join a Wi-Fi network with IPv6 Internet access.\n 646 2. If the device has battery power, disconnect all power connectors.\n 647 3. Turn the screen off if possible.\n 648 4. Wait until the screen turns on or the test result is displayed (it will take at least two minutes).\n 649 5. If necessary, unlock the device.\n 650 6. Please mark the test according to the result status indicated.\n 651 </string> 652 <string name="network_background_test_start">Start</string> 653 654 <!-- Strings for net.MultiNetworkConnectivityTestActivity --> 655 <string name="multinetwork_connectivity_test">Multinetwork connectivity Test</string> 656 <string name="multinetwork_connectivity_test_instructions"> 657 This test verifies that, when a phone has internet connectivity via mobile network 658 is connected to a Wi-Fi access point that doesn\'t have internet or loses internet access, 659 it restores the internet activity over the mobile cell network, while connected to the 660 Wi-Fi access point. \n\n 661 662 1. Setup a wireless access point with ability to turn on and off internet access. 663 2. Have SIM or cellular data connectivity on the phone being tested. 664 3. Execute the tests with the instructions outlined in the test 665 4. When the test completes, it will finish and mark it passed. If it fails, it will mark it \n 666 as failed. 667 668 </string> 669 <string name="multinetwork_connectivity_test_pre_requisites">Prerequisite - Setup a Wi-Fi access point with WPA PSK in which we can turn on or off internet access. </string> 670 <string name="multinetwork_connectivity_test_start">Start</string> 671 <string name="multinetwork_connectivity_test_ap_name">Wi-Fi SSID</string> 672 <string name="multinetwork_connectivity_test_ap_passphrase">WPA 2 passphrase</string> 673 <string name="multinetwork_connectivity_test_continue">Confirm and continue with test.</string> 674 <string name="multinetwork_connectivity_test_rerun">Completed. Re-run.</string> 675 <string name="multinetwork_connectivity_test_running">Running.</string> 676 <string name="multinetwork_connectivity_test_connect_cellular">Connecting to cellular network.</string> 677 <string name="multinetwork_connectivity_test_connect_wifi">Connecting to Wi-Fi network.</string> 678 <string name="multinetwork_connectivity_test_complete">Test completed.</string> 679 <string name="multinetwork_connectivity_test_progress_1">Waiting for Wi-Fi to lose connectivity.</string> 680 <string name="multinetwork_connectivity_test_progress_2">Waiting to check connectivity.</string> 681 <string name="multinetwork_connectivity_test_progress_3">Waiting to make sure Wi-Fi has connectivity.</string> 682 <string name="multinetwork_connectivity_test_1_desc">Test 1 - Connect to Wi-Fi with no internet doesnt disable current connectivity</string> 683 <string name="multinetwork_connectivity_test_2_desc">Test 2 - When connected to Wi-Fi, on losing connectivity, restores mobile connectivity</string> 684 <string name="multinetwork_status_wifi_connect_success">Wi-Fi connect success.</string> 685 <string name="multinetwork_status_mobile_connect_success">Mobile net connect success.</string> 686 <string name="multinetwork_status_wifi_connect_timed_out">Wi-Fi connect timed out.</string> 687 <string name="multinetwork_status_wifi_connect_wrong_ap">Wi-Fi connected to wrong access point.</string> 688 <string name="multinetwork_status_mobile_connect_timed_out">Mobile network connect timed out.</string> 689 <string name="multinetwork_status_mobile_restore_success">Mobile restore succeeded.</string> 690 <string name="multinetwork_status_mobile_restore_failed">Mobile restore failed.</string> 691 <string name="multinetwork_connectivity_test_1_prereq">Make sure that the Hotspot does not have internet access.</string> 692 <string name="multinetwork_connectivity_test_2_prereq_1">Make sure that the Hotspot has internet access.</string> 693 <string name="multinetwork_connectivity_test_2_prereq_2">Make sure that the Hotspot does not have internet access. When prompted to go back to using mobile data, choose ok.</string> 694 <string name="multinetwork_connectivity_test_all_prereq_1">Looks like your device does not support telephony or mobile data. If yes, you can mark test passed and proceed.</string> 695 <string name="multinetwork_connectivity_test_all_prereq_2">Need mobile data to proceed. Please insert a mobile data capable sim and repeat the test. By marking test as passed, you acknowledge that the device cannot do mobile data.</string> 696 <string name="multinetwork_status_wifi_connectivity_failed">Wi-Fi connectivity failed.</string> 697 698 <!-- Strings for NfcTestActivity --> 699 <string name="nfc_test">NFC Test</string> 700 <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with 701 NFC enabled to exchange messages. One device must be the candidate device running the 702 software build to be tested, while the other device must be an implementation already 703 known to be compatible.\n\nThe Tag Verification tests check that your 704 device can properly read and write to tags of different technologies. The MIFARE 705 Ultralight test is only applicable for devices that support it. 706 \n\nThe Host-based card emulation tests check that your device has properly implemented 707 host-based card emulation. 708 </string> 709 710 <string name="nfc_not_enabled">NFC is not enabled!</string> 711 <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the 712 button below to goto Settings and enable it.</string> 713 <string name="nfc_settings">NFC Settings</string> 714 715 <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string> 716 <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled. 717 Click the button below to goto NFC Sharing Settings and enable it.</string> 718 <string name="ndef_push_settings">NFC Sharing Settings</string> 719 720 <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string> 721 <string name="nfc_ndef_push_sender">NDEF Push Sender</string> 722 <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string> 723 <string name="nfc_llcp_version_check">LLCP version check</string> 724 725 <string name="nfc_tag_verification">Tag Verification</string> 726 <string name="nfc_ndef">NDEF</string> 727 <string name="nfc_mifare_ultralight">MIFARE Ultralight</string> 728 729 <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on 730 another device and touch the devices back to back. The receiver should show a 731 dialog indicating it has successfully received the correct message!</string> 732 <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another 733 device running the \"CTS Verifier NDEF Receiver\"...</string> 734 735 <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on 736 another device and touch the devices back to back. The receiver should show a 737 dialog indicating it has successfully received the correct message!</string> 738 <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another 739 device running the \"CTS Verifier NDEF Sender\"...</string> 740 <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push 741 message.</string> 742 <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push 743 message.</string> 744 745 <string name="nfc_llcp_version_check_info">This test requires two candidate devices 746 with NFC enabled to exchange P2P messages. Start the \"LLCP version check\" test on 747 the other candidate device also, and touch the devices back to back. This test 748 then verifies that the candidate device correctly advises the LLCP version as 1.2</string> 749 <string name="nfc_llcp_version_check_failure">The candidate devices does not report LLCP 750 version 1.2 or higher.</string> 751 <string name="nfc_llcp_version_check_success">The candidate device has a valid LLCP version.</string> 752 <string name="nfc_tag_verifier">NFC Tag Verifier</string> 753 <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read 754 a tag of the chosen technology.</string> 755 756 <string name="nfc_scan_tag">Place device on a writable %s tag...</string> 757 <string name="nfc_write_tag_title">Writable tag discovered!</string> 758 <string name="nfc_write_tag_message">Press OK to write to this tag...</string> 759 <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string> 760 <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string> 761 <string name="nfc_no_tech">No tag technologies detected...</string> 762 763 <string name="nfc_writing_tag">Writing NFC tag...</string> 764 <string name="nfc_writing_tag_error">Error writing NFC tag...</string> 765 <string name="nfc_reading_tag">Reading NFC tag...</string> 766 <string name="nfc_reading_tag_error">Error reading NFC tag...</string> 767 768 <string name="nfc_result_success">Test passed!</string> 769 <string name="nfc_result_failure">Test failed!</string> 770 771 <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string> 772 <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string> 773 774 <string name="nfc_hce">Host-based card emulation</string> 775 <string name="nfc_hce_f">Host-based Felica card emulation</string> 776 <string name="nfc_hce_reader_tests">HCE reader tests</string> 777 <string name="nfc_hce_f_reader_tests">HCE Felica reader tests</string> 778 <string name="nfc_hce_emulator_tests">HCE emulator tests</string> 779 <string name="nfc_hce_f_emulator_tests">HCE Felica emulator tests</string> 780 <string name="nfc_hce_f_emulator">HCE Felica emulator</string> 781 <string name="nfc_hce_f_reader">HCE Felica reader</string> 782 <string name="nfc_hce_emulator_test_info">The host-based card emulation 783 tests require two devices to be completed. The HCE emulator tests are used 784 to actually test the host-based card emulation feature of the device-under-test. So the 785 device running the emulator tests must be the candidate device running the software 786 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 787 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 788 and makes sure the device-under-test implements card emulation correctly.</string> 789 <string name="nfc_hce_reader_test_info">The host-based card emulation 790 tests require two devices to be completed. The HCE emulator tests are used 791 to actually test the host-based card emulation feature of the device-under-test. So the 792 device running the emulator tests must be the candidate device running the software 793 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 794 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 795 and makes sure the device-under-test implements card emulation correctly. 796 </string> 797 <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> 798 <string name="nfc_hce_please_wait">Please wait</string> 799 <string name="nfc_hce_setting_up">Setting up card emulation services...</string> 800 801 <string name="nfc_hce_default_route_emulator">Default route (Emulator)</string> 802 <string name="nfc_hce_default_route_reader">Default route (Reader)</string> 803 <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> 804 805 <string name="nfc_hce_protocol_params_emulator">Protocol parameters (Emulator)</string> 806 <string name="nfc_hce_protocol_params_reader">Protocol parameters (Reader)</string> 807 <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> 808 809 <string name="nfc_hce_single_payment_emulator">Single payment (Emulator)</string> 810 <string name="nfc_hce_single_payment_reader">Single payment (Reader)</string> 811 812 <string name="nfc_hce_dual_payment_emulator">Two payment services (Emulator)</string> 813 <string name="nfc_hce_dual_payment_reader">Two payment services (Reader)</string> 814 815 <string name="nfc_hce_change_default_emulator">Change default payment service (Emulator)</string> 816 <string name="nfc_hce_change_default_reader">Change default payment service (Reader)</string> 817 818 <string name="nfc_hce_tap_reader_title">Tap reader</string> 819 <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> 820 821 <string name="nfc_hce_single_non_payment_emulator">Single non-payment (Emulator)</string> 822 <string name="nfc_hce_single_non_payment_reader">Single non-payment (Reader)</string> 823 824 <string name="nfc_hce_dual_non_payment_emulator">Two non-payment services (Emulator)</string> 825 <string name="nfc_hce_dual_non_payment_reader">Two non-payment services (Reader)</string> 826 827 <string name="nfc_hce_conflicting_non_payment_emulator">Two conflicting non-payment services (Emulator)</string> 828 <string name="nfc_hce_conflicting_non_payment_reader">Two conflicting non-payment services (Reader)</string> 829 830 <string name="nfc_hce_foreground_non_payment_emulator">Foreground override non-payment services (Emulator)</string> 831 <string name="nfc_hce_foreground_non_payment_reader">Foreground override non-payment services (Reader)</string> 832 <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> 833 834 <string name="nfc_hce_foreground_payment_emulator">Foreground override payment services (Emulator)</string> 835 <string name="nfc_hce_foreground_payment_reader">Foreground override payment services (Reader)</string> 836 <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> 837 <string name="nfc_hce_change_favor_foreground">This test requires the \"Use default\" setting to be set to \"Except when another payment app is open\". Tap OK to go to Tap and Pay settings and make sure the \"Use default\" setting is set to \"Except when another payment app is open\".</string> 838 <string name="nfc_hce_offhost_service_emulator">Off-host service (Emulator)</string> 839 <string name="nfc_hce_offhost_service_reader">Off-host service (Reader)</string> 840 <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> 841 842 <string name="nfc_hce_on_and_offhost_service_emulator">On and off-host services (Emulator)</string> 843 <string name="nfc_hce_on_and_offhost_service_reader">On and off-host services (Reader)</string> 844 <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> 845 846 <string name="nfc_hce_tap_test_emulator">50 successful taps test (Emulator)</string> 847 <string name="nfc_hce_tap_test_reader">50 successful taps test (Reader)</string> 848 <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> 849 <string name="nfc_hce_throughput_emulator">HCE throughput test (Emulator)</string> 850 <string name="nfc_hce_throughput_reader">HCE throughput test (Reader)</string> 851 <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> 852 <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> 853 <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> 854 <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> 855 856 <string name="nfc_hce_payment_dynamic_aids_emulator">Dynamic payment AIDs (Emulator)</string> 857 <string name="nfc_hce_payment_dynamic_aids_reader">Dynamic payment AIDs (Reader)</string> 858 <string name="nfc_hce_payment_dynamic_aids_help">This test tries to register dynamic AIDs for a payment service.</string> 859 860 <string name="nfc_hce_large_num_aids_emulator">Large number of AIDs (Emulator)</string> 861 <string name="nfc_hce_large_num_aids_reader">Large number of AIDs (Reader)</string> 862 <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> 863 864 <string name="nfc_hce_payment_prefix_aids_emulator">Payment prefix AIDs (Emulator)</string> 865 <string name="nfc_hce_payment_prefix_aids_reader">Payment prefix AIDs (Reader)</string> 866 <string name="nfc_hce_payment_prefix_aids_help">This test statically registers prefix AIDs for a payment service.</string> 867 868 <string name="nfc_hce_payment_prefix_aids_emulator_2">Payment prefix AIDs 2 (Emulator)</string> 869 <string name="nfc_hce_payment_prefix_aids_reader_2">Payment prefix AIDs 2 (Reader)</string> 870 871 <string name="nfc_hce_other_prefix_aids_emulator">Other prefix AIDs (Emulator)</string> 872 <string name="nfc_hce_other_prefix_aids_reader">Other prefix AIDs (Reader)</string> 873 <string name="nfc_hce_other_prefix_aids_help">This test dynamically registers prefix AIDs for a non-payment service.</string> 874 875 <string name="nfc_hce_other_conflicting_prefix_aids_emulator">Conflicting non-payment prefix AIDs (Emulator)</string> 876 <string name="nfc_hce_other_conflicting_prefix_aids_reader">Conflicting non-payment prefix AIDs (Reader)</string> 877 <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> 878 879 <string name="nfc_payment_service_desc">NFC Payment service</string> 880 <string name="ppse">PPSE</string> 881 <string name="mastercard">MasterCard</string> 882 <string name="visa">Visa</string> 883 <string name="paymentService1">Payment Service #1</string> 884 <string name="paymentService2">Payment Service #2</string> 885 <string name="transportService1">TransportService #1</string> 886 <string name="transportService2">TransportService #2</string> 887 <string name="accessService">AccessService</string> 888 <string name="offhostService">OffhostService</string> 889 <string name="felicaservice">Felica Service</string> 890 891 <!-- Strings for Sensor Test Activities --> 892 <string name="snsr_device_admin_receiver">Sensor Tests Device Admin Receiver</string> 893 <string name="snsr_test_summary">Tests passed: %1$d, Tests skipped: %2$d, Tests failed: %3$d</string> 894 <string name="snsr_test_complete">Test completed without errors.</string> 895 <string name="snsr_test_complete_with_errors">Test completed with errors which indicates 896 the device does not meet Android compatibility requirement. 897 This will degrade user experience and cause applications to misbehave. 898 To help debugging, please take a bug report and back up contents under 899 /sdcard/sensorTests of the device under test. 900 </string> 901 <string name="snsr_test_pass">PASS</string> 902 <string name="snsr_test_skipped">SKIPPED</string> 903 <string name="snsr_test_fail">FAIL</string> 904 <string name="snsr_execution_time">Test execution time %1$s sec</string> 905 <string name="snsr_rvcvxchk_test">Rotation Vector CV Crosscheck</string> 906 <string name="snsr_rvcvxchk_test_rec">Rotation Vector CV Recording</string> 907 908 <!-- Strings to interact with users in Sensor Tests --> 909 <string name="snsr_test_play_sound">A sound will be played once the verification is complete...</string> 910 <string name="snsr_no_interaction">Leave the device on top of a flat surface.</string> 911 <string name="snsr_interaction_needed">Once the test begins, you will have to wave your hand over the front of the device.</string> 912 <string name="snsr_device_steady">Keep the device steady.</string> 913 <string name="snsr_keep_device_rotating_clockwise">Once the test begins, you will have to keep rotating the device clockwise.</string> 914 <string name="snsr_wait_for_user">Press \'Next\' to continue.</string> 915 <string name="snsr_wait_to_begin">Press \'Next\' to begin.</string> 916 <string name="snsr_on_complete_return">After completing the task, go back to this test.</string> 917 <string name="snsr_movement_expected">Movement was expected during the test. Found=%1$b.</string> 918 <string name="snsr_sensor_feature_deactivation">IMPORTANT NOTE: Please also turn off any special features in the 919 device that use sensors (wake up gestures, motion triggered events, moves, etc). 920 Not doing so is expected to cause test failures. Once you are done, you can begin the test.</string> 921 <string name="snsr_setting_mode_request">You will be redirected to set \'%1$s\' to: %2$s.</string> 922 <string name="snsr_setting_mode_set">\'%1$s\' set to: %2$s.</string> 923 <string name="snsr_setting_mode_not_set">\'%1$s\' not set to: %2$s.</string> 924 <string name="snsr_setting_airplane_mode">Airplane mode</string> 925 <string name="snsr_setting_screen_brightness_mode">Adaptive Brightness</string> 926 <string name="snsr_setting_auto_rotate_screen_mode">Auto-rotate screen</string> 927 <string name="snsr_setting_keep_screen_on">Stay awake</string> 928 <string name="snsr_setting_location_mode">Location</string> 929 <string name="snsr_setting_ambient_display">Ambient Display</string> 930 <string name="snsr_pass_on_error">Pass Anyway</string> 931 <string name="snsr_run_automated_tests">The screen will be turned off to execute the tests, 932 when tests complete, the device will vibrate and the screen will be turned back on.</string> 933 934 <!-- Accelerometer --> 935 <string name="snsr_accel_test">Accelerometer Test</string> 936 <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> 937 <string name="snsr_accel_m_test">Accelerometer Measurement Tests</string> 938 <string name="snsr_accel_test_face_up">Place the device on a flat surface with the screen 939 facing the ceiling.</string> 940 <string name="snsr_accel_test_face_down">Place the device on a flat surface with the screen 941 facing it.</string> 942 <string name="snsr_accel_test_right_side">Place the device in a flat surface resting vertically 943 on its right side.</string> 944 <string name="snsr_accel_test_left_side">Place the device in a flat surface resting vertically 945 on its left side.</string> 946 <string name="snsr_accel_test_top_side">Place the device in a flat surface resting vertically 947 on its top side.</string> 948 <string name="snsr_accel_test_bottom_side">Place the device in a flat surface resting vertically 949 on its bottom side.</string> 950 951 <!-- Gyroscope --> 952 <string name="snsr_gyro_test">Gyroscope Test</string> 953 <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> 954 <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string> 955 <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string> 956 <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> 957 <string name="snsr_gyro_test_degrees_title">Wrong units?</string> 958 <string name="snsr_gyro_test_degrees_message">These values looks like degrees per second. These should be radians per second!</string> 959 <string name="snsr_gyro_m_test">Gyroscope Measurement Test</string> 960 <string name="snsr_gyro_device_placement">Place the device in a flat surface with the screen 961 facing the ceiling. Read the instructions for each scenario, before you perform the 962 test.</string> 963 <string name="snsr_gyro_device_static">Leave the device static.</string> 964 <string name="snsr_gyro_rotate_device">Once you begin the test, you will need to rotate the 965 device 360deg (one time) in the direction show by the animation, then place it back on the 966 flat surface.</string> 967 968 <!-- Heart Rate --> 969 <string name="snsr_heartrate_test">Heart Rate Test</string> 970 <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> 971 <string name="snsr_heartrate_test_no_heartrate_title">No heart rate monitor?</string> 972 <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> 973 974 <!-- Magnetic Field --> 975 <string name="snsr_mag_m_test">Magnetic Field Measurement Tests</string> 976 <string name="snsr_mag_verify_norm">Verifying the Norm...</string> 977 <string name="snsr_mag_verify_std_dev">Verifying the Standard Deviation...</string> 978 <string name="snsr_mag_verify_calibrated_uncalibrated">Verifying the relationship between 979 calibrated and uncalibrated measurements...</string> 980 <string name="snsr_mag_calibration_description">Please calibrate the Magnetometer by moving 981 it in 8 shapes in different orientations. Click \"Next\" to start and click \"Next\" once again to end calibration.</string> 982 <string name="snsr_mag_calibration_complete">When done, leave the device in a flat surface, far 983 from all metallic objects (if the test does not pass, try re-running it outdoors).</string> 984 <string name="snsr_mag_measurement">-> (%1$.2f, %2$.2f, %3$.2f) : %4$.2f uT</string> 985 986 <!-- Sensor Value Accuracy --> 987 <string name="snsr_rot_vec_test">Rotation Vector Accuracy Test</string> 988 <string name="snsr_event_length">Sensor(%3$s). Event values expected to have size=%1$d. Found=%2$d.</string> 989 <string name="snsr_event_value">Sensor(%3$s). Event value[0] expected to be of value=%1$f. Found=%2$f.</string> 990 <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> 991 992 <!-- Sensor Batching --> 993 <string name="snsr_batch_test">Sensor Batching Manual Tests</string> 994 <string name="snsr_batching_walking_needed">Once the test begins, you will have to take the 995 device in your hand and walk.</string> 996 997 <!-- Sensor Synchronization --> 998 <string name="snsr_synch_test">Sensor Synchronization Test</string> 999 1000 <!-- Step Counter and Detector --> 1001 <string name="snsr_step_counter_test">Step Counter and Detector Tests</string> 1002 <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> 1003 <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> 1004 <string name="snsr_step_counter_expected_steps">At least %1$d steps are expected to be reported. Reported=%2$d.</string> 1005 <string name="snsr_step_counter_detected_reported">Steps reported by user=%1$d. Steps counted=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 1006 <string name="snsr_step_detector_detected_reported">Steps reported by user=%1$d. Steps detected=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 1007 <string name="snsr_step_counter_event_changed">Step counter expected to increase monotonically, with a delta > 0. Found=%1$d. Timestamp=%2$d.</string> 1008 <string name="snsr_step_reported">%1$d | User reported step.</string> 1009 <string name="snsr_step_counter_event">%1$d | Step Counter event. count=%2$d.</string> 1010 <string name="snsr_step_detector_event">%1$d | Step Detector event.</string> 1011 1012 <!-- Device suspend tests --> 1013 <string name="snsr_device_suspend_test">Device Suspend Tests</string> 1014 <string name="snsr_device_did_not_go_into_suspend">Device did not go into suspend mode during test execution </string> 1015 <string name="snsr_batch_did_not_arrive_at_expected_time">Batch did not arrive at the expected time estimatedBatchArrivalMs=%1$d 1016 firstEventReceivedMs=%2$d diffMs=%3$d toleranceMs=%4$d </string> 1017 <string name="snsr_device_suspend_test_instr">One you begin the test, disconnect USB, turn off the display and allow 1018 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> 1019 1020 <!-- Significant Motion --> 1021 <string name="snsr_significant_motion_test">Significant Motion Tests</string> 1022 <string name="snsr_significant_motion_event_arrival">Event expected to trigger. Triggered=%1$s.</string> 1023 <string name="snsr_significant_motion_event_type">Event expected to be of type=%1$d. Found=%2$d.</string> 1024 <string name="snsr_significant_motion_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string> 1025 <string name="snsr_significant_motion_disable_info">Significant Motion is expected to disable itself after it triggers once.</string> 1026 <string name="snsr_significant_motion_test_trigger">Once you begin the test, you will need to walk for Significant Motion to be detected.</string> 1027 <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> 1028 <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> 1029 <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> 1030 <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> 1031 <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> 1032 <string name="snsr_significant_motion_registration">Expected to be able to register for TriggerSensor. Found=%1$b.</string> 1033 <string name="snsr_significant_motion_cancelation">Expected to be able to cancel TriggerSensor. Found=%b.</string> 1034 <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. 1035 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> 1036 <string name="snsr_device_did_not_wake_up_at_trigger">Device did not wakeup at trigger time. wakeTime=%1$d ms triggerTime=%2$d ms</string> 1037 1038 <!-- Event sanitization for idle UIDs --> 1039 <string name="snsr_event_sanitization_test">Event sanitization for idle UID test</string> 1040 <string name="snsr_event_sanitization_test_setup">Run the \'adb shell cmd sensorservice set-uid-state com.android.cts.verifier idle\' shell command 1041 to emulate the CtsVerifier UID being idle.</string> 1042 <string name="snsr_event_sanitization_test_cleanup">Run the \'adb shell cmd sensorservice reset-uid-state com.android.cts.verifier\' shell command 1043 to stop emulating the CtsVerifier UID being idle. Failing to do that would lead to other tests failing!</string> 1044 <string name="snsr_significant_motion_test_uid_idle">Move around with the device to try triggering significant motion</string> 1045 <string name="snsr_significant_motion_test_uid_idle_expectation">No trigger events should be generated while idle</string> 1046 <string name="snsr_proximity_test_uid_idle">Touch the proximity sensor to try triggering it</string> 1047 <string name="snsr_proximity_test_uid_idle_expectation">No on-change events should be generated while idle</string> 1048 1049 <!-- Low Latency Off-Body Detect --> 1050 <string name="snsr_offbody_sensor_test">Off Body Sensor Tests</string> 1051 <string name="snsr_offbody_sensor_registration">Registration failed for low latency offbody detect sensor.\n</string> 1052 <string name="snsr_offbody_event_arrival">Expected to receive a low latency offbody detect event. Found=%b.</string> 1053 <string name="snsr_offbody_event_type">Event expected to be of type=%1$d. Found=%2$d.</string> 1054 <string name="snsr_offbody_event_invalid_value">Invalid value received for offbody state; Expected value %1$d or %2$d. Found=%2$d.</string> 1055 <string name="snsr_offbody_event_wrong_value">Expected to receive an event having value=%1$d. Found=%2$d.</string> 1056 <string name="snsr_offbody_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string> 1057 <string name="snsr_offbody_response_timing_violation">%1$s event maximum allowed latency is %2$d. Found=%3$d ms.</string> 1058 <string name="snsr_offbody_state_change">Offbody state changed to %1$d. Timestamp=%2$d.</string> 1059 <string name="snsr_start_offbody_sensor_test_instr">Put watch on your wrist and then click Next button.</string> 1060 <string name="snsr_start_onbody_sensor_test_instr">Remove the watch from your wrist and then click Next button.</string> 1061 <string name="snsr_offbody_detect_test_instr">Click Next button, then immediate remove the watch from your wrist after the countdown reaches 0.</string> 1062 <string name="snsr_offbody_detect_test_countdown">Countdown: %1$d.</string> 1063 <string name="snsr_onbody_detect_test_instr">Click Next button, then immediately attach the watch on your wrist.</string> 1064 <string name="snsr_ap_wake_offbody_detect_test_instr">Click Next button, then palm the screen. Wait a few seconds after screen blackens, then remove watch from wrist.</string> 1065 1066 <!-- Strings for Sensor CTS tests inside CtsVerifier --> 1067 <string name="snsr_single_sensor_tests">CTS Single Sensor Tests</string> 1068 <string name="snsr_sensor_integration_tests">CTS Sensor Integration Tests</string> 1069 <string name="snsr_sensor_test">CTS Sensor Test</string> 1070 <string name="snsr_sensor_batching_tests">CTS Sensor Batching Tests</string> 1071 1072 <!-- String for DynamicSensorDiscoveryTest --> 1073 <string name="snsr_dynamic_sensor_discovery_test">Dynamic Sensor Discovery Test</string> 1074 1075 <!-- Strings for Sample Test Activities --> 1076 <string name="share_button_text">Share</string> 1077 <string name="sample_framework_test">Sample Framework Test</string> 1078 <string name="sample_test">Sample Test</string> 1079 <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> 1080 1081 <!-- Strings for UsbDebuggingDialogTapjackingTest --> 1082 <string name="usb_tapjacking_button_text">Show overlay</string> 1083 <string name="usb_tapjacking_test">Usb Debugging Dialog Tapjacking Test</string> 1084 <string name="usb_tapjacking_test_info">This test verifies that tapjacking on the usb dialog is not possible by disallowing users from accepting usb debugging pemissions when dialog is obscured.</string> 1085 <string name="usb_tapjacking_test_instructions"> 1086 1. Connect device via usb to computer.\n 1087 2. Click \"Show overlay\" button. Settings may appear if the CTS Verifier app doesn\'t have display over apps permission. Enable this permission and then click back to navigate back to the app.\n 1088 3. Trigger USB debugging dialog (from computer terminal): \"adb shell am start -e fingerprints placeholder -e key placeholder com.android.systemui/.UsbDebuggingActivityAlias\"\n 1089 4. USB debugging dialog should appear with the overlay on top saying \"This message covers the USB debugging RSA prompt\" to appear.\n 1090 5. Try clicking OK. \n 1091 Test pass if you cannot click OK when the text quoted above is on top of the USB debugging dialog. Toast should appear saying there is an overlay so Settings cannot verify your response. \n 1092 Note: Fake message overlay may remain on screen until you leave the test. This is working as intended. \n 1093 </string> 1094 <string name="usb_tapjacking_overlay_message">This message covers the USB debugging RSA prompt</string> 1095 <string name="usb_tapjacking_error_toast">Please restart the application and try again.</string> 1096 <string name="usb_tapjacking_error_toast2">Please enable display over apps permission for this application before proceeding.</string> 1097 1098 <!-- Strings for Camera Orientation --> 1099 <string name="camera_orientation">Camera Orientation</string> 1100 <string name="co_info">This test verifies the orientation capabilities of 1101 camera preview and capture.\n - The left view shows a preview window rotated 1102 clockwise by a given magnitude of degrees.\n - The right view, after taking 1103 a photo, shows the captured image.\n - For each camera and orientation, both 1104 the left and right views should appear rotated clockwise by the amount of 1105 degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose 1106 \"Fail\".\n - For front-facing cameras, the test will horizontally mirror 1107 the captured image prior to rotation, in attempt to make the left and right 1108 views appear the same.\n - The physical orientation of the device does not 1109 matter.\n - Read the message above the \"Take Photo\" button for 1110 step-by-step instructions. 1111 </string> 1112 <string name="co_preview_label">Camera preview</string> 1113 <string name="co_format_label">Oriented photo</string> 1114 <string name="co_camera_label">Camera:</string> 1115 <string name="co_orientation_label">Orientation</string> 1116 <string name="co_orientation_direction_label">clockwise</string> 1117 <string name="co_instruction_heading_label">Instruction:</string> 1118 <string name="co_instruction_text_photo_label">Take a photo</string> 1119 <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> 1120 <string name="co_instruction_text_extra_label">(mirrored horizontally prior to rotation, since camera is front-facing)</string> 1121 <string name="co_photo_button_caption">Take Photo</string> 1122 1123 <!-- Strings for Camera Intents --> 1124 <string name="camera_intents">Camera Intents</string> 1125 <string name="ci_info"> 1126 This test verifies that the default camera app is firing intents 1127 after pictures/videos are taken. It also verifies that when the 1128 default camera app is invoked via intents, the launch intents work, 1129 and the broadcast intents are received when appropriate per the SDK 1130 documentation.\n\n 1131 - Read the message above the \"Start Test\" button for 1132 step-by-step instructions. 1133 </string> 1134 <string name="ci_preview_label">Camera preview</string> 1135 <string name="ci_format_label">Oriented photo</string> 1136 <string name="ci_camera_label">Camera:</string> 1137 <string name="ci_intents_label">Intents Test</string> 1138 <string name="ci_intents_direction_label">clockwise</string> 1139 <string name="ci_instruction_heading_label">Instructions:</string> 1140 <string name="ci_instruction_text_photo_label">READ BEFORE STARTING TEST</string> 1141 <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> 1142 <string name="ci_instruction_text_app_picture_label">\n 1143 1. Click Start Test. \n 1144 2. Go to home screen (HOME key). \n 1145 3. Launch Camera application. \n 1146 4. Capture photo within 1 minute. \n 1147 5. Return to CTS verifier app. \n 1148 6. Pass button will light up if URI trigger was fired.\n 1149 7. Click "Pass" if possible. 1150 </string> 1151 <string name="ci_instruction_text_app_video_label">\n 1152 1. Click Start Test. \n 1153 2. Go to home screen (HOME key). \n 1154 3. Launch Camera application. \n 1155 4. Capture video within 1 minute. \n 1156 5. Return to CTS verifier app. \n 1157 6. Pass button will light up if URI trigger was fired.\n 1158 7. Click "Pass" if possible. 1159 </string> 1160 <string name="ci_instruction_text_intent_picture_label">\n 1161 1. Click Start Test.\n 1162 2. Camera app will launch, prompting to take photo.\n 1163 3. Capture/confirm photo using camera app controls within 1 minute.\n 1164 4. Pass button will light up if URI trigger was NOT received.\n 1165 5. Click "Pass" if possible. 1166 </string> 1167 <string name="ci_instruction_text_intent_video_label">\n 1168 1. Click Start Test.\n 1169 2. Camera app will launch, prompting to take video.\n 1170 3. Capture/confirm video using camera app controls within 1 minute.\n 1171 4. Pass button will light up if URI trigger was received.\n 1172 5. Click "Pass" if possible. 1173 </string> 1174 <string name="ci_start_test_button_caption">Start Test</string> 1175 1176 <!-- Strings for Camera Formats --> 1177 <string name="camera_format">Camera Formats</string> 1178 <string name="cf_info">This test checks that all the supported 1179 output formats for camera preview callbacks work correctly, and 1180 that the mandatory formats are available. \n - The left view shows 1181 a standard preview window. \n - The right view shows the output 1182 processed from camera preview callbacks. \n - For each camera, 1183 resolution, and format combination in the dropdowns, the right 1184 view should look the same as the left, and neither should have 1185 streaks, lines, or other artifacts. \n - For front-facing cameras, 1186 the right view must be horizontally mirrored relative to the left 1187 view.\n - Note that the frame rate of the right view may be much 1188 lower than on the left; this is not an indication of a failed 1189 test. 1190 </string> 1191 <string name="cf_preview_label">Normal preview</string> 1192 <string name="cf_format_label">Processed callback data</string> 1193 1194 <!-- Strings for Camera Video --> 1195 <string name="record_button_text">Test</string> 1196 <string name="camera_video">Camera Video</string> 1197 <string name="video_info"> This test checks video capture 1198 at different resolutions. \n - The left view window shows the preview. 1199 \n - Pressing the test button will trigger three 1200 seconds of video recording. Playback will show up in the right view 1201 window after recording is complete. \n - Use the spinners to choose 1202 camera and resolution combinations. The playback should be similar 1203 to what you saw in preview. \n - After all possible combinations 1204 are tested, the pass button will be enabled. You may press the pass 1205 button to indicate a pass. \n - You may press fail button any time during 1206 the test to indicate failure. 1207 </string> 1208 <string name="video_capture_label">Video capture</string> 1209 <string name="video_playback_label">Video playback</string> 1210 <string name="dialog_fail_test">Test failed</string> 1211 <string name="fail_quit">Fail and quit</string> 1212 <string name="cancel">Cancel</string> 1213 <string name="status_ready">Ready</string> 1214 <string name="status_recording">Recording</string> 1215 <string name="status_playback">Playing back</string> 1216 1217 <!-- Strings for USB accessory test activity --> 1218 <string name="usb_accessory_test">USB Accessory Test</string> 1219 <string name="usb_accessory_test_info"> 1220 1. Install the Cts Verifier USB Companion app on a separate helper device. 1221 \n\n2. Start the accessory test companion in the Cts Verifier USB Companion. 1222 \n\n3. Connect the two devices. If using a OTG adapter make sure the adapter is directly connected to the helper device. If using an Type-C cable make sure that the helper device is set as "supply power to the attached device". 1223 \n\n4. Confirm access to the USB device on the helper device. 1224 \n\n5. Confirm access to the USB accessory on this device 1225 \n\n6. Confirm access to the USB device on the helper again. 1226 \n\n7. Test will run and complete automatically in less than 30 seconds. 1227 \n\n8. Cancel all further dialogs on this device 1228 </string> 1229 <string name="usb_accessory_test_step1"> 1230 In this specific order: 1231 \n1. Install the Cts Verifier USB Companion app on a separate helper device. 1232 \n2. Start the accessory test companion in the Cts Verifier USB Companion. 1233 \n3. Connect the two devices. If using a OTG adapter make sure the adapter is directly connected to the helper device. If using an Type-C cable make sure that the helper device is set as "supply power to the attached device". 1234 \n4. Confirm access to the USB device on the helper device. Only confirm once. 1235 \n5. Confirm access to the USB accessory on this device. 1236 \n6. Confirm access to the USB device on the helper device again. 1237 \n\nResult: A progress indicator should appear or test will finish. 1238 </string> 1239 <string name="usb_accessory_test_step2"> 1240 Test is running and will complete automatically in less than 30 seconds. 1241 </string> 1242 1243 <!-- String for the USB device test activity --> 1244 <string name="usb_device_test">USB Device Test</string> 1245 <string name="usb_device_test_info"> 1246 1. Install the Cts Verifier USB Companion app on a separate helper device. 1247 \n\n2. Start the device test companion in the Cts Verifier USB Companion. 1248 \n\n3. Connect the two devices. If using a OTG adapter make sure the adapter is directly connected to this device. If using an Type-C cable make sure that this device is set as "supply power to the attached device". 1249 \n\n4. Confirm access to the USB device on this device. 1250 \n\n5. Confirm access to the USB accessory on the helper device. 1251 \n\n6. Confirm access to the USB device on this device again. 1252 \n\n7. Test will run and complete automatically in less than 30 seconds. 1253 \n\n8. Cancel all further dialogs on the helper device. 1254 </string> 1255 <string name="usb_device_test_step1"> 1256 In this specific order: 1257 \n1. Install the Cts Verifier USB Companion app on a separate helper device. 1258 \n2. Start the device test companion in the Cts Verifier USB Companion. 1259 \n3. Connect the two devices. If using a OTG adapter make sure the adapter is directly connected to this device. If using an Type-C cable make sure that this device is set as "supply power to the attached device". 1260 \n\nResult: A dialog should show up on this device asking for access to a USB device. 1261 </string> 1262 <string name="usb_device_test_step2"> 1263 Confirm access to the USB device on this device. 1264 \n\nResult: Dialogs should show up on this device and on the helper device asking for access to a USB device/accessory. 1265 </string> 1266 <string name="usb_device_test_step3"> 1267 1. Confirm access to the USB accessory on the helper device. 1268 \n2. Confirm access to the USB device on this device again. 1269 \n\nResult: A progress indicator should appear or test will finish. 1270 </string> 1271 <string name="usb_device_test_step4"> 1272 Test is running and will complete automatically in a less than 30 seconds. 1273 </string> 1274 <string name="usb_device_unexpected">Usb companion device is not as expected %1$s. Please retry test.</string> 1275 1276 <!-- Strings for MTP host test activity --> 1277 <string name="mtp_host_test">MTP Host Test</string> 1278 <string name="mtp_host_test_info">The CTS-verifier tests the MTP host feature with another Android device. Please connect another Android device to this Android device by using OTG cable or USB type C cable, then follow the instructions on this screen. Note the test creates/deletes files in the connected Android device.</string> 1279 <string name="mtp_host_device_lookup_message">Connect MTP device.\nPlease connect another Android device to this device by using USB OTG cable or USB type C cable.\nOpen \"Use USB for\" dialog from the notification in the other Android device and choose \"File Transfer\" option.\nThen press the next button.</string> 1280 <string name="mtp_host_grant_permission_message">Grant permission.\nReply a dialog asking device permission.</string> 1281 <string name="mtp_host_test_read_event_message">Test MtpDevice#readEvent.\nTake a picture at the connected device.</string> 1282 <string name="mtp_host_test_send_object_message">Test MtpDevice#sendObject.</string> 1283 <string name="mtp_host_test_file_browse_message">Test MTP file browsing.\nCheck if the UI to browse files in the connected devices was shown automatically. If not, tap a notification on this device saying the other MTP device is connected. If different application launched, go to the applicaiton settings by clicking the App Settings button, open the detailes settings page of the app, clear the default action settings, and retry. </string> 1284 <string name="mtp_app_settings">App Settings</string> 1285 1286 <!-- Strings for the Camera ITS test activity --> 1287 <string name="camera_its_test">Camera ITS Test</string> 1288 <string name="camera_its_test_info"> 1289 1. Connect your Android device to a computer with adb installed via a USB cable. 1290 \n\n2. Setup the CameraITS test environment by following the setup instructions in the 1291 README file found in the CameraITS directory included in the CTS Verifier bundle 1292 (cd CameraITS; source build/envsetup.sh;). 1293 \n\n3. Setup the test scene described in the CameraITS README file, and aim the camera 1294 at it. 1295 \n\n4. Run the full ITS test suite on all possible camera Ids. 1296 (cd CameraITS; python tools/run_all_tests.py). Once all 1297 of the tests have been run, the \'PASS\' button will be enabled if all of the tests have 1298 succeeded. Please note that these tests can take more than 2 hours to run on some devices. 1299 </string> 1300 <string name="no_camera_manager"> 1301 No camera manager exists! This test device is in a bad state. 1302 </string> 1303 <string name="all_legacy_devices"> 1304 All cameras on this device are LEGACY mode only - ITS tests are only required on LIMITED 1305 or better devices. Pass. 1306 </string> 1307 <string name="its_test_passed">All Camera ITS tests passed. Pass button enabled!</string> 1308 <string name="its_test_failed">Some Camera ITS tests failed.</string> 1309 <string name="its_version_mismatch"> 1310 CtsVerifier and ITS script version mismatch. Please update CtsVerifier and ITS script. 1311 </string> 1312 <string name="its_test_progress">ITS test progress will be shown here.</string> 1313 1314 <!-- Strings for the Camera Flashlight test activity --> 1315 <string name="camera_flashlight_test">Camera Flashlight</string> 1316 <string name="camera_flashlight_info"> 1317 This test checks the flashlight functionality. It will turn on and off the flashlight of 1318 each camera device that has a flash unit. Follow the instructions on screen and observe the 1319 flashlight status changing. 1320 </string> 1321 <string name="camera_flashlight_start_button">Start</string> 1322 <string name="camera_flashlight_next_button">Next</string> 1323 <string name="camera_flashlight_done_button">Done</string> 1324 <string name="camera_flashlight_on_button">On</string> 1325 <string name="camera_flashlight_off_button">Off</string> 1326 <string name="camera_flashlight_start_text">Press Start to start flashlight test.</string> 1327 <string name="camera_flashlight_question_text">Is Camera %1$s flashlight on or off?</string> 1328 <string name="camera_flashlight_next_text">Ok. Press next.</string> 1329 <string name="camera_flashlight_failed_text">Test failed. Press Done or Fail button.</string> 1330 <string name="camera_flashlight_passed_text">All tests passed. Press Done or Pass button. 1331 </string> 1332 1333 <!-- Strings for StreamingVideoActivity --> 1334 <string name="streaming_video">Streaming Video Quality Verifier</string> 1335 <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> 1336 <string name="sv_no_data">No videos.</string> 1337 <string name="sv_failed_title">Test Failed</string> 1338 <string name="sv_failed_message">Unable to play stream. See log for details.</string> 1339 1340 <!-- Strings for P2pTestActivity --> 1341 <string name="p2p_test">Wi-Fi Direct Test</string> 1342 <string name="p2p_test_info"> 1343 The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange 1344 messages. One device must be the candidate device running the software build to 1345 be tested, while the other device must be an implementation already known to be 1346 compatible.\n\nOne device should start the requester test, and the other should 1347 start the responder test. Your device must pass both requester and responder 1348 tests. 1349 </string> 1350 <string name="p2p_group_formation">Group Formation</string> 1351 <string name="p2p_join">Group Join</string> 1352 <string name="p2p_service_discovery">Service Discovery</string> 1353 1354 <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string> 1355 <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string> 1356 <string name="p2p_group_owner_test">Group Owner Test</string> 1357 <string name="p2p_group_client_test">Group Client Test</string> 1358 <string name="p2p_service_discovery_responder_test"> 1359 Service Discovery Responder Test</string> 1360 <string name="p2p_service_discovery_requester_test"> 1361 Service Discovery Requester Test</string> 1362 1363 <string name="p2p_go_neg_responder">GO Negotiation Responder</string> 1364 <string name="p2p_go_neg_requester">GO Negotiation Requester</string> 1365 <string name="p2p_accept_client">Group Owner</string> 1366 <string name="p2p_join_go">Group Client</string> 1367 <string name="p2p_service_discovery_responder">Service Discovery Responder</string> 1368 <string name="p2p_service_discovery_requester">Service Discovery Requester</string> 1369 1370 <string name="p2p_go_neg_responder_info"> 1371 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 1372 Wi-Fi settings and forget all remembered networks. Then start the \"GO Negotiation 1373 Requester Test\" on the other device and follow 1374 the instructions.</string> 1375 <string name="p2p_accept_client_info"> 1376 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 1377 Wi-Fi settings and forget all remembered networks. Then start the \"Group Client Test\" on 1378 the other device and follow 1379 the instructions.</string> 1380 <string name="p2p_service_discovery_responder_info"> 1381 Start the \"Service Discovery Requester Test\" on the other device and follow 1382 the instructions.</string> 1383 1384 <string name="p2p_go_neg_requester_info"> 1385 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 1386 Wi-Fi settings and forget all remembered networks. Then start the \"GO Negotiation 1387 Responder Test\" on the other device. 1388 Then run each test individually by clicking on its name.</string> 1389 <string name="p2p_join_go_info"> 1390 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 1391 Wi-Fi settings and forget all remembered networks. Then start the \"Group Owner Test\" on 1392 the other device. 1393 Then run each test individually by clicking on its name.</string> 1394 <string name="p2p_service_discovery_requester_info"> 1395 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 1396 Wi-Fi settings and forget all remembered networks. Then start the \"Service Discovery 1397 Responder Test\" on the other device. 1398 Then run each test individually by clicking on its name.</string> 1399 1400 <string name="p2p_not_enabled">Wi-Fi is not enabled</string> 1401 <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled. 1402 Click the button below to go to system settings and enable Wi-Fi.</string> 1403 <string name="p2p_settings">Wi-Fi Direct Settings</string> 1404 1405 <string name="p2p_result_success">Test passed successfully.</string> 1406 1407 <string name="p2p_go_neg_responder_ready"> 1408 The go negotiation responder is now ready to start. 1409 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 1410 Wi-Fi settings and forget all remembered networks. Then start the \"GO Negotiation 1411 Requester Test\" on the other device. 1412 Keep the screen here until all tests on the other device are 1413 finished.</string> 1414 <string name="p2p_go_ready"> 1415 The group owner is now ready to start. 1416 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 1417 Wi-Fi settings and forget all remembered networks. Then start the \"Join Group Test\" on 1418 the other device. 1419 Keep the screen here until all tests on the other device are 1420 finished.</string> 1421 <string name="p2p_service_responder_ready"> 1422 The service responder is now ready to start. 1423 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 1424 Wi-Fi settings and forget all remembered networks. Then start the \"Service Discovery 1425 Requester Test\" on the other device. 1426 Keep the screen here until all tests on the other device are 1427 finished.</string> 1428 1429 <string name="p2p_setup_error"> 1430 Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string> 1431 <string name="p2p_unexpected_error"> 1432 Test failed.\n\nUnexpected error. Check logcat.</string> 1433 <string name="p2p_add_local_service_error"> 1434 Test failed.\n\nFailed to add local service.</string> 1435 <string name="p2p_add_service_request_error"> 1436 Test failed.\n\nFailed to add service request.</string> 1437 <string name="p2p_remove_service_request_error"> 1438 Test failed.\n\nFailed to remove service request.</string> 1439 <string name="p2p_clear_service_requests_error"> 1440 Test failed.\n\nFailed to clear service requests.</string> 1441 <string name="p2p_connect_error"> 1442 Test failed.\n\nFailed to start a p2p connection to the target device.</string> 1443 <string name="p2p_remove_group_error"> 1444 Test failed.\n\nFailed to remove a p2p group.</string> 1445 <string name="p2p_discover_peers_error"> 1446 Test failed.\n\nFailed to discover peers.</string> 1447 <string name="p2p_discover_services_error"> 1448 Test failed.\n\nFailed to discover services.</string> 1449 <string name="p2p_ceate_group_error"> 1450 Test failed.\n\nFailed to start up group owner.</string> 1451 <string name="p2p_no_service_requests_error"> 1452 Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string> 1453 <string name="p2p_receive_invalid_response_error"> 1454 Test failed.\n\nReceived an invalid message or could not receive 1455 the expected message.\n\n</string> 1456 <string name="p2p_target_not_found_error">Test failed.\n\n 1457 The target responder device was NOT found. Start up the responder 1458 test on the other device, then run the test again.</string> 1459 <string name="p2p_target_invalid_role_error">Test failed.\n\n 1460 The target responder must be p2p device. However, the target responder 1461 device was group owner. Check the test case on the other device.</string> 1462 <string name="p2p_target_invalid_role_error2">Test failed.\n\n 1463 The target responder must be group owner. However, the target responder 1464 device was p2p device. Check the test case on the other device.</string> 1465 <string name="p2p_connection_error"> 1466 Test failed.\n\nFailed to establish a p2p connection.</string> 1467 <string name="p2p_detect_disconnection_error"> 1468 Test failed.\n\nFailed to detect client disconnection.</string> 1469 <string name="p2p_disconnect_error"> 1470 Test failed.\n\nFailed to disconnect a p2p connection.</string> 1471 1472 <string name="p2p_search_target">Search Target</string> 1473 <string name="p2p_searching_target">Searching for target device ...</string> 1474 <string name="p2p_checking_serv_capab">Checking the service discovery 1475 capability ...</string> 1476 <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n 1477 Click the \"OK\" button on the other device to accept the connection 1478 request from this device.</string> 1479 <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n 1480 Enter the pin number on the other device.</string> 1481 <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to 1482 connect ...</string> 1483 <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer 1484 to disconnect ...</string> 1485 1486 <!-- Strings for TestListActivity --> 1487 <string name="aware_test">Wi-Fi Aware Test</string> 1488 <string name="aware_test_info"> 1489 The Wi-Fi Aware tests require two devices with Wi-Fi enabled. One device must 1490 be the candidate device running the software build to be tested, while the other 1491 device must be an implementation already known to be compatible.\n\nThere are 1492 tests for Publisher and Subscriber, Responder and Initiator. One device should 1493 start in a role, and the other should start in the complementary 1494 role. Your device must pass the tests in all roles. 1495 </string> 1496 <string name="aware_not_enabled">Wi-Fi / Location Mode is not enabled</string> 1497 <string name="aware_not_enabled_message">These tests require Wi-Fi and Location Mode to be enabled. 1498 Click the button below to go to system settings and enable Wi-Fi and Location Mode.</string> 1499 <string name="aware_settings">Wi-Fi Settings</string> 1500 <string name="aware_setup_error"> 1501 Test failed.\n\nSet up error. Check whether Wi-Fi is enabled.</string> 1502 <string name="aware_unexpected_error"> 1503 Test failed.\n\nUnexpected error. Check logcat.</string> 1504 1505 <string name="aware_dp_ib_open_unsolicited">Data Path: Open: Unsolicited/Passive</string> 1506 <string name="aware_dp_ib_passphrase_unsolicited">Data Path: Passphrase: Unsolicited/Passive</string> 1507 <string name="aware_dp_ib_open_solicited">Data Path: Open: Solicited/Active</string> 1508 <string name="aware_dp_ib_passphrase_solicited">Data Path: Passphrase: Solicited/Active</string> 1509 <string name="aware_discovery_ranging">Discovery with Ranging</string> 1510 <string name="aware_publish">Publish</string> 1511 <string name="aware_subscribe">Subscribe</string> 1512 1513 <string name="aware_dp_oob_open">Data Path (OOB): Open</string> 1514 <string name="aware_dp_oob_passphrase">Data Path (OOB): Passphrase</string> 1515 <string name="aware_responder">Responder</string> 1516 <string name="aware_initiator">Initiator</string> 1517 1518 <string name="aware_status_attached">Attached ...</string> 1519 <string name="aware_status_attach_fail">Attach failure!</string> 1520 <string name="aware_status_attach_timeout">Attach failure - timed out!</string> 1521 <string name="aware_status_identity">Discovery (Identity) MAC address: %1$s ...</string> 1522 <string name="aware_status_identity_fail">Identity listener failure - timed out!</string> 1523 <string name="aware_status_subscribe_started">Subscribe discovery session started ...</string> 1524 <string name="aware_status_subscribe_failed">Subscribe failure!</string> 1525 <string name="aware_status_subscribe_timeout">Subscribe failure - timed out!</string> 1526 <string name="aware_status_subscribe_null_session">Subscribe failure - null session!</string> 1527 <string name="aware_status_publish_started">Publish discovery session started ...</string> 1528 <string name="aware_status_publish_failed">Publish failure!</string> 1529 <string name="aware_status_publish_timeout">Publish failure - timed out!</string> 1530 <string name="aware_status_publish_null_session">Publish failure - null session!</string> 1531 <string name="aware_status_discovery">Service discovered ...</string> 1532 <string name="aware_status_discovery_with_info">Service discovered ... peer MAC : %1$s</string> 1533 <string name="aware_status_discovery_timeout">Service discovery failure - timed out!</string> 1534 <string name="aware_status_discovery_fail">Service discovery failure - parameter mismatch!</string> 1535 <string name="aware_status_send_success">Sent message successfully ...</string> 1536 <string name="aware_status_send_failed">Send message failure!</string> 1537 <string name="aware_status_send_timeout">Send message failure - timed out!</string> 1538 <string name="aware_status_send_fail_parameter">Send message failure - mismatched ids!</string> 1539 <string name="aware_status_received">Received message ...</string> 1540 <string name="aware_status_starting_rtt">Starting RTT operations ...</string> 1541 <string name="aware_status_waiting_for_peer_rtt">Pausing to let other device perform RTT ...</string> 1542 <string name="aware_status_received_peer_rtt_done">Other device done with RTT ...</string> 1543 <string name="aware_status_received_mac">Received peer MAC address: %1$s ...</string> 1544 <string name="aware_status_receive_timeout">Receive message failure - timed out!</string> 1545 <string name="aware_status_receive_failure">Receive message failure - didn\'t receive expected message!</string> 1546 <string name="aware_status_network_requested">Network requested ...</string> 1547 <string name="aware_status_network_success">Network formed ...</string> 1548 <string name="aware_status_network_failed">Network request failure - timed out!</string> 1549 <string name="aware_status_sleeping_wait_for_responder">Pausing to let Responder time to set up ...</string> 1550 <string name="aware_status_ranging_peer_failure">Ranging to PeerHandle failure: %1$d failures of %2$d attempts!</string> 1551 <string name="aware_status_ranging_mac_failure">Ranging to MAC address failure: %1$d failures of %2$d attempts!</string> 1552 <string name="aware_status_ranging_peer_success">Ranging to PeerHandle success: %1$d successes of %2$d attempts!</string> 1553 <string name="aware_status_ranging_mac_success">Ranging to MAC address success: %1$d successes of %2$d attempts!</string> 1554 <string name="aware_status_lifecycle_failed">Discovery lifecycle FAILURE!</string> 1555 <string name="aware_status_lifecycle_ok">Discovery lifecycle validated!</string> 1556 1557 <string name="aware_data_path_open_unsolicited_publish">Data Path: Open: Unsolicited Publish</string> 1558 <string name="aware_data_path_open_unsolicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: Open: Unsolicited/Passive\' / \'Subscribe\' test.</string> 1559 <string name="aware_data_path_open_passive_subscribe">Data Path: Open: Passive Subscribe</string> 1560 1561 <string name="aware_data_path_passphrase_unsolicited_publish">Data Path: Passphrase: Unsolicited Publish</string> 1562 <string name="aware_data_path_passphrase_unsolicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: Passphrase: Unsolicited/Passive\' / \'Subscribe\' test.</string> 1563 <string name="aware_data_path_passphrase_passive_subscribe">Data Path: Passphrase: Passive Subscribe</string> 1564 1565 <string name="aware_data_path_open_solicited_publish">Data Path: Open: Solicited Publish</string> 1566 <string name="aware_data_path_open_solicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: Open: Solicited/Active\' / \'Subscribe\' test.</string> 1567 <string name="aware_data_path_open_active_subscribe">Data Path: Open: Active Subscribe</string> 1568 1569 <string name="aware_data_path_passphrase_solicited_publish">Data Path: Passphrase: Solicited Publish</string> 1570 <string name="aware_data_path_passphrase_solicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: Passphrase: Solicited/Active\' / \'Subscribe\' test.</string> 1571 <string name="aware_data_path_passphrase_active_subscribe">Data Path: Passphrase: Active Subscribe</string> 1572 1573 <string name="aware_data_path_oob_open_responder">Data Path (OOB): Open: Responder</string> 1574 <string name="aware_data_path_oob_open_responder_info">The responder is now ready.\n\nOn the other device: start the \'Data Path (OOB): Open\' / \'Initiator\' test.</string> 1575 <string name="aware_data_path_oob_open_initiator">Data Path (OOB): Open: Initiator</string> 1576 1577 <string name="aware_data_path_oob_passphrase_responder">Data Path (OOB): Passphrase: Responder</string> 1578 <string name="aware_data_path_oob_passphrase_responder_info">The responder is now ready.\n\nOn the other device: start the \'Data Path (OOB): Passphrase\' / \'Initiator\' test.</string> 1579 <string name="aware_data_path_oob_passphrase_initiator">Data Path (OOB): Passphrase: Initiator</string> 1580 1581 <string name="aware_discovery_ranging_publish">Discovery with Ranging: Publish</string> 1582 <string name="aware_discovery_ranging_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Discovery with Ranging\' / \'Subscribe\' test.</string> 1583 <string name="aware_discovery_ranging_subscribe">Discovery with Ranging: Subscribe</string> 1584 1585 <string name="camera_fov_calibration">Camera FOV Calibration</string> 1586 <string name="camera_fov_calibration_done">Done</string> 1587 <string name="camera_fov_general_settings">General settings</string> 1588 <string name="camera_fov_label_options">Settings</string> 1589 <string name="camera_fov_tap_to_take_photo">Tap to calibrate</string> 1590 <string name="camera_fov_marker_distance">Marker distance (in cm)</string> 1591 <string name="camera_fov_marker_distance_description">The distance in centimeters between 1592 the solid lines on the target pattern.</string> 1593 <string name="camera_fov_target_distance">Target distance (in cm)</string> 1594 <string name="camera_fov_target_distance_description">The distance in centimeters from the 1595 device to the target pattern.</string> 1596 <string name="camera_fov_settings_button_text">Setup</string> 1597 <string name="camera_fov_change_preview_sizes_button_text">Preview Sizes</string> 1598 <string name="camera_fov_choose_preview_size_for_camera">Choose preview size for camera %1$s</string> 1599 <string name="camera_fov_displayed_fov_label">Displayed FOV : </string> 1600 <string name="camera_fov_reported_fov_label">Reported FOV : </string> 1601 <string name="camera_fov_reported_fov_problem">Reported FOV problem</string> 1602 <string name="camera_fov_reported_fov_problem_message">The reported FOV before takePicture() is 1603 different from when onPictureTaken() is called.\nAs picture size has not been changed, the 1604 reported FOV should be identical at both times.\n\nFOV before/after: %1$f / %2$f</string> 1605 1606 <string name="camera_fov_panorama_wallpaper_title">Photo Sphere Live Wallpaper</string> 1607 <string name="camera_fov_panorama_wallpaper_description">This live wallapper displays photo 1608 spheres.</string> 1609 <string name="camera_fov_select_panorama">Select panorama</string> 1610 <string name="camera_fov_select_panorama_description">Select a panorama to display in the 1611 live wallpaper.</string> 1612 <string name="camera_fov_reset_panorama">Reset panorama</string> 1613 <string name="camera_fov_reset_panorama_description">Resets the panorama to show the demo 1614 file.</string> 1615 <string name="camera_fov_enable_compass_mode">Enable compass mode</string> 1616 <string name="camera_fov_enable_compass_mode_description">If enabled, the panorama orients 1617 itself according to the current rotation of the device.</string> 1618 1619 <string name="test_category_notifications">Notifications</string> 1620 <string name="package_priority_test">Notification Package Priority Test</string> 1621 <string name="package_priority_info">This test checks that the NotificationManagerService respects 1622 user preferences about relative package priorities. 1623 </string> 1624 <string name="package_priority_bot">Verifying that the CTS Robot helper package is installed.</string> 1625 <string name="package_priority_high">Find \"%s\" in the \"Notifications\" settings panel, and allow it to Override Do Not Disturb.</string> 1626 <string name="package_priority_default">Find \"%s\" in the \"Notifications\" settings panel, and disallow it to Override Do Not Disturb.</string> 1627 <string name="package_priority_user_order">Check that ranker respects user priorities.</string> 1628 1629 <string name="shortcut_reset_test">Shortcut Reset Rate-limiting Test</string> 1630 <string name="shortcut_reset_info">This test checks that when an inline-reply happens, ShortcutManager\'s rate-limiting 1631 is reset.</string> 1632 <string name="shortcut_reset_bot">Verifying that the CTS Robot helper package is installed.</string> 1633 <string name="shortcut_reset_start">Showing the notification.</string> 1634 <string name="shortcut_reset_prompt_inline_reply">Open the notification shade, 1635 find the \"Shortcut Reset Rate-limiting Test\" notification, type something in the inline-reply field and 1636 press the send button.</string> 1637 <string name="shortcut_reset_check_result">Check ShortcutManager rate-limit has been reset.</string> 1638 1639 <string name="attention_test">Notification Attention Management Test</string> 1640 <string name="attention_info">This test checks that the NotificationManagerService is 1641 respecting user preferences about notification ranking and filtering. 1642 </string> 1643 <string name="ringer_mode_tests">Ringer Mode Tests</string> 1644 <string name="ringer_mode_info">This test checks that Audio manager functionality that requires 1645 particular ringer mode states works properly. 1646 </string> 1647 <string name="ringer_mode_pass_test">These tests are handled by CTS.</string> 1648 <string name="test_sound_effects">Test sound effects</string> 1649 <string name="test_vibrate_notification">Test vibrate notification</string> 1650 <string name="test_vibrate_ringer">Test vibrate ringer</string> 1651 <string name="test_access_ringer_mode">Test access ringer mode</string> 1652 <string name="test_ringer_mode_policy_access">Test ringer mode policy access</string> 1653 <string name="test_volume_dnd_affected_stream">Test volume change</string> 1654 <string name="test_mute_dnd_affected_streams">Test mute streams</string> 1655 <string name="test_ringer_manager">Test RingtoneManager</string> 1656 <string name="enable_sound_effects">Please enable sound effects in Sound settings.</string> 1657 <string name="attention_ready">I\'m done</string> 1658 <string name="attention_filter_any">Please enable \"Do not disturb\" by tapping the Quick Settings tile.</string> 1659 <string name="attention_filter_all">Please disable \"Do not disturb\" by tapping the Quick Settings tile.</string> 1660 <string name="attention_filter_priority">Please enable \"Do not disturb\" by tapping the Quick 1661 Settings tile. Then, long press the same tile and customize the setting to allow messages 1662 from starred contacts only.</string> 1663 <string name="attention_filter_priority_mimic_alarms_only">Please enable Priority-Only \"Do not disturb\" 1664 by tapping the Quick Settings tile. Then, long press the same tile and customize the setting to allow sounds 1665 from Alarms and Media (if applicable) only.</string> 1666 <string name="attention_create_contacts">Create contacts for notification annotations.</string> 1667 <string name="attention_delete_contacts">Delete test contacts.</string> 1668 <string name="attention_default_order">Check that ranker defaults to time order.</string> 1669 <string name="attention_priority_order">Check that ranker respects developers priorities.</string> 1670 <string name="attention_ambient_bit">Check that the ambient bit is set appropriately.</string> 1671 <string name="attention_lookup_order">Check that ranker respects Lookup URIs for contacts.</string> 1672 <string name="attention_email_order">Check that ranker respects mailto URIs for contacts.</string> 1673 <string name="attention_phone_order">Check that ranker respects telephone URIs for contacts.</string> 1674 <string name="attention_interruption_order">Check that ranker temporarily boosts interruptions. 1675 This test takes 30 seconds to complete.</string> 1676 <string name="attention_none_are_filtered_messages">Check that \"All\" mode doesn\'t filter any notifications (messages).</string> 1677 <string name="attention_none_are_filtered_diff_categories">Check that \"All\" mode doesn\'t filter any notifications (event, reminder, alarm).</string> 1678 <string name="attention_some_are_filtered_messages">Check that \"Priority\" mode doesn\'t filter priority notifications (messages from starred contacts).</string> 1679 <string name="attention_some_are_filtered_alarms">Check that \"Priority\" mode doesn\'t filter priority notifications (alarms).</string> 1680 <string name="attention_some_are_filtered_media_system_other">Check that \"Priority\" mode doesn\'t filter priority notifications (media, system, other).</string> 1681 <string name="attention_all_are_filtered">Check that \"None\" mode filters all notifications.</string> 1682 <string name="attention_cannot_disallow_alarms_or_media">Check that apps targeted with Pre-P SDK can\'t disallow alarms or media from bypassing DND.</string> 1683 <string name="nls_test">Notification Listener Test</string> 1684 <string name="nas_test">Notification Assistant Test</string> 1685 <string name="nls_service_name">Notification Listener for CTS Verifier</string> 1686 <string name="nls_info">This test checks that a NotificationListenerService can be enabled 1687 and disabled, and that once enabled the service is able to receive notifications and 1688 dismiss them. 1689 </string> 1690 <string name="nas_service_name">Notification Assistant for CTS Verifier</string> 1691 <string name="nas_info">This test checks that a NotificationAssistantService can be enabled 1692 and disabled, and that once enabled the service is able to receive notifications and 1693 dismiss them. 1694 </string> 1695 <string name="msg_extras_preserved">Check that Message extras Bundle was preserved.</string> 1696 <string name="vr_tests">VR Tests</string> 1697 <string name="test_category_vr">VR</string> 1698 <string name="vr_test_title">VR Listener Test</string> 1699 <string name="vr_service_name">VR Listener for CTS Verifier</string> 1700 <string name="vr_info">This test checks that a VrListenerService can be enabled and disabled, and 1701 and that it receives the correct lifecycle callbacks when entering and exiting VR mode. 1702 </string> 1703 <string name="vr_start_settings">Launch Settings</string> 1704 <string name="vr_start_vr_activity">Launch VR mode activity</string> 1705 <string name="vr_start_double_vr_activity">Launch Two VR mode activities</string> 1706 <string name="vr_start_vr_activity_desc">Click the button to launch the VR mode activity.</string> 1707 <string name="vr_start_vr_double_activity_desc">Click the button to launch two consecutive VR mode activities.</string> 1708 <string name="vr_check_disabled">Check that the CTS VR helper service is disabled by default.</string> 1709 <string name="vr_enable_service">Please enable \"VR Listener for CTS Verifier\" 1710 under Apps > Gear Icon > Special Access > VR Helper Services and return here.</string> 1711 <string name="vr_disable_service">Please disable \"VR Listener for CTS Verifier\" 1712 under Apps > Gear Icon > Special Access > VR Helper Services and return here.</string> 1713 <string name="nas_enable_service">Please enable \"Notification Assistant for CTS Verifier\" 1714 under Apps > Gear Icon > Default > Notification Assistant and return here.</string> 1715 <string name="nas_disable_service">Please disable \"Notification Assistant for CTS Verifier\" 1716 under Apps > Gear Icon > Default > Notification Assistant and return here.</string> 1717 <string name="nls_enable_service">Please enable \"Notification Listener for CTS Verifier\" 1718 under Apps > Gear Icon > Special Access > Notification Access and return here.</string> 1719 <string name="nls_block_app">Please block the linked application and return here.</string> 1720 <string name="nls_unblock_app">Please unblock the linked application and return here.</string> 1721 <string name="nls_block_channel">Please block the linked notification channel and return here.</string> 1722 <string name="nls_block_group">Please block the linked notification channel group and return here.</string> 1723 <string name="nls_cannot_enable_service">Please make sure you cannot enable 1724 \"Notification Listener for CTS Verifier\" and return here.</string> 1725 <string name="nls_disable_service">Please disable \"Notification Listener for CTS Verifier\" 1726 under Apps > Gear Icon > Special Access > Notification Access and return here.</string> 1727 <string name="nls_start_settings">Launch Settings</string> 1728 <string name="nls_service_started">Service should start once enabled.</string> 1729 <string name="nas_note_enqueued_received">Check that notification was enqueued.</string> 1730 <string name="nls_note_received">Check that notification was received.</string> 1731 <string name="nls_payload_intact">Check that notification payload was intact.</string> 1732 <string name="nas_adjustment_payload_intact">Check that the Assistant can adjust notifications.</string> 1733 <string name="nas_adjustment_enqueue_payload_intact">Check that the Assistant can adjust notifications on enqueue.</string> 1734 <string name="nas_create_channel">Check that the Assistant can create a Notification Channel for another app.</string> 1735 <string name="nas_update_channel">Check that the Assistant can update a Notification Channel for another app.</string> 1736 <string name="nas_block_channel">Check that the Assistant can block a Notification Channel.</string> 1737 <string name="nas_delete_channel">Check that the Assistant can delete a Notification Channel for another app.</string> 1738 <string name="nas_snooze_context">Check that the Assistant can snooze a notification until a given context.</string> 1739 <string name="nls_clear_one">Check that service can clear a notification.</string> 1740 <string name="nls_clear_one_reason">Check that service can clear a notification and receive the correct reason for dismissal.</string> 1741 <string name="nls_clear_one_stats">Check that service does not receive notification stats.</string> 1742 <string name="nls_clear_all">Check that service can clear all notifications.</string> 1743 <string name="nls_service_stopped">Service should stop once disabled.</string> 1744 <string name="nls_note_missed">Check that notification was not received.</string> 1745 <string name="nls_snooze">Check the service can be snoozed.</string> 1746 <string name="nls_unsnooze">Check the service can be unsnoozed.</string> 1747 <string name="nls_hints">Check that the listener can set hints.</string> 1748 <string name="nls_snooze_one">Check that service can snooze a notification.</string> 1749 <string name="nls_snooze_one_time">Check that service can snooze a notification for a given time.</string> 1750 <string name="nls_get_snoozed">Check that service can retrieve snoozed notifications.</string> 1751 <string name="nls_unsnooze_one">Check that service can unsnooze a notification.</string> 1752 <string name="nas_note_missed_enqueued">Check that notification was not enqueued.</string> 1753 <string name="cp_test">Condition Provider test</string> 1754 <string name="cp_service_name">Condition Provider for CTS Verifier</string> 1755 <string name="cp_info">This test checks that on non-low ram a ConditionProviderService can be enabled 1756 and disabled, and that once enabled the service is able to create, query, edit, and delete 1757 automatic zen rules. On low ram devices condition providers should not be bound. 1758 </string> 1759 <string name="cp_cannot_enable_service">Please make sure you cannot enable \"CTS Verifier\" under Do Not Disturb access and return here.</string> 1760 <string name="cp_enable_service">Please enable \"CTS Verifier\" under Do Not Disturb access and return here.</string> 1761 <string name="cp_disable_service">Please disable \"CTS Verifier\" under Do Not Disturb access and return here.</string> 1762 <string name="cp_start_settings">Launch Settings</string> 1763 <string name="cp_create_rule">Creating Automatic Zen Rule</string> 1764 <string name="cp_update_rule">Updating Automatic Zen Rule</string> 1765 <string name="cp_subscribe_rule">Subscribing to Automatic Zen Rule</string> 1766 <string name="cp_service_started">Service should start once enabled.</string> 1767 <string name="cp_service_stopped">Service should stop once disabled.</string> 1768 <string name="cp_unsubscribe_rule">Unsubscribing to Automatic Zen Rule</string> 1769 <string name="cp_delete_rule">Deleting Automatic Zen Rule</string> 1770 <string name="cp_get_rules">Retrieving Automatic Zen Rules</string> 1771 <string name="cp_get_rule">Retrieving Automatic Zen Rule</string> 1772 1773 <string name="cacert_test">CA Cert Notification Test</string> 1774 <string name="cacert_info">This test checks that when a CA Certificate is installed, the user is notified.</string> 1775 <string name="cacert_do_something">Do it</string> 1776 <string name="cacert_done">Done</string> 1777 <string name="cacert_install_cert">Use the CertInstaller to install the certificate "MyCA.cer" from device storage. When it opens, choose any name and tap "Okay". If this button does nothing, pass the test and move on.</string> 1778 <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> 1779 <string name="cacert_remove_screen_lock">You may have been prompted to set a screen lock when installing the certificate. If so, remove it. If not, you may skip this step.</string> 1780 <string name="cacert_check_notification">Look at the system notifications. Confirm that:\n 1781 1. There is a notification saying a certificate authority is installed.\n 1782 2. Tapping that notification brings up a more detailed explanation and a button to check trusted credentials.\n 1783 3. Tapping that button brings up the Trusted Credentials page you just visited.</string> 1784 <string name="cacert_dismiss_notification">Open the notification and follow the link to remove CA certificates. If removing CA certificates does not dismiss the notification, fail the test.</string> 1785 1786 <string name="caboot_test">CA Cert Notification on Boot test</string> 1787 <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> 1788 <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> 1789 <string name="caboot_check_creds">Check Credentials</string> 1790 <string name="caboot_if_not_installed">Only if there is no credential currently installed, install one.</string> 1791 <string name="caboot_install_cert">Install credential</string> 1792 <string name="caboot_remove_screen_lock">Remove screen lock</string> 1793 <string name="caboot_reboot_desc">Please reboot the device and return to this test.</string> 1794 <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> 1795 1796 <!-- Strings for KeyChain --> 1797 <string name="keychain_test">KeyChain Storage Test</string> 1798 <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> 1799 <string name="keychain_reset">Reset</string> 1800 <string name="keychain_skip">Skip</string> 1801 <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 1802 Tap \'Next\' to begin.</string> 1803 <string name="keychain_install_desc">Credentials generated. Tap \'Next\' to install them to the system keychain.\n\n 1804 The container for the credentials will not be protected with a password; if prompted for one, leave that field blank.\n\n 1805 During installation you may be prompted for a name - accept the default suggestion.\n\n 1806 In the case that these credentials were already installed, you may skip this step.</string> 1807 <string name="keychain_https_desc">The last test involves setting up an HTTPS connection using credentials from the KeyChain.\n\n 1808 You should be prompted to select credentials; choose the ones you just installed in the previous step.</string> 1809 <string name="keychain_reset_desc">Before marking this test as passed, tap \'Next\' to open security settings and reset the following items:\n 1810 1. Clear device credentials.\n 1811 2. Change the lock screen type to \'None\'.</string> 1812 1813 <!-- Strings for Widget --> 1814 <string name="widget_framework_test">Widget Framework Test</string> 1815 <string name="widget_framework_test_info">This test checks some basic features of the widget 1816 framework. In order to perform the test, press the Home button. Add the widget 1817 titled "CTS Verifier" to the home screen. Follow the instructions in the widget.</string> 1818 <string name="widget_name">Widget Framework Test</string> 1819 <string name="widget_pass">Pass</string> 1820 <string name="widget_fail">Fail</string> 1821 1822 <string name="provisioning_byod_nonmarket_allow">Enable non-market apps</string> 1823 <string name="provisioning_byod_nonmarket_allow_info"> 1824 This test verifies that non-market apps can be installed if permitted.\n 1825 1. A package installation UI should appear.\n 1826 2. If \'Cts Verifier\' is not allowed to install apps, a warning dialog will appear 1827 blocking the install. In this case go to step 3, else skip to step 4.\n 1828 3. Allow \'Cts Verifier\' to install apps. Return to package installer.\n 1829 4. Accept the installation and verify that it succeeds (no error message is displayed). 1830 </string> 1831 1832 <string name="provisioning_byod_nonmarket_deny">Disable non-market apps</string> 1833 <string name="provisioning_byod_nonmarket_deny_info"> 1834 This test verifies that non-market apps cannot be installed unless permitted.\n 1835 1. A package installation UI should appear.\n 1836 2. Verify that the installation of the package is refused. 1837 </string> 1838 1839 <string name="provisioning_byod_capture_image_support">Camera support cross profile image capture</string> 1840 <string name="provisioning_byod_capture_image_support_info"> 1841 This test verifies that images can be captured from the managed profile using the primary profile camera.\n 1842 1. Capture a picture using the camera.\n 1843 2. Verify that the captured picture is shown.\n 1844 3. Click on the close button. 1845 </string> 1846 <string name="provisioning_byod_capture_video_support_with_extra_output">Camera support cross profile video capture (with extra output path)</string> 1847 <string name="provisioning_byod_capture_video_support_info"> 1848 This test verifies that videos can be captured from the managed profile using the primary profile camera.\n 1849 1. Capture a video using the camera.\n 1850 2. Click on the play button.\n 1851 3. Verify that the captured video is played.\n 1852 4. Click on the close button. 1853 </string> 1854 <string name="provisioning_byod_capture_video_support_without_extra_output">Camera support cross profile video capture (without extra output path)</string> 1855 <string name="provisioning_byod_capture_audio_support">Sound recorder support cross profile audio capture</string> 1856 <string name="provisioning_byod_capture_audio_support_info"> 1857 This test verifies that audio can be captured from the managed profile using the primary profile sound recorder.\n 1858 1. Capture audio.\n 1859 2. Click on the play button.\n 1860 3. Verify that the captured audio is played.\n 1861 4. Click on the close button.\n 1862 </string> 1863 <string name="provisioning_byod_dismiss_result_dialog">Close</string> 1864 <string name="provisioning_byod_play">Play</string> 1865 <string name="provisioning_byod_verify_image_title">Verify captured image</string> 1866 <string name="provisioning_byod_verify_video_title">Verify captured video</string> 1867 <string name="provisioning_byod_verify_audio_title">Verify captured audio</string> 1868 <string name="provisioning_byod_no_image_capture_resolver">No image capture app present. Skip test.</string> 1869 <string name="provisioning_byod_no_video_capture_resolver">No video capture app present. Skip test.</string> 1870 <string name="provisioning_byod_no_audio_capture_resolver">No audio capture app present. Skip test.</string> 1871 <string name="provisioning_byod_capture_media_error">Error while capturing media from managed profile.</string> 1872 <string name="provisioning_byod_capture_image_error">Error while capturing image from managed profile.</string> 1873 1874 <string name="provisioning_byod_auth_bound_key">Authentication-bound keys</string> 1875 <string name="provisioning_byod_auth_bound_key_info"> 1876 This test verifies keystore cryptographic keys can be bound to device credentials. 1877 These keys should only be available if there was a recent enough authentication. 1878 </string> 1879 <string name="provisioning_byod_auth_bound_key_instruction"> 1880 This test verifies keystore cryptographic keys can be bound to device lockscreen challenge or fingerprints (if available). 1881 These keys should only be available if there was a recent enough authentication. \n 1882 1883 1. Press "Set up" to open Security settings. (If this device has a separate app for work 1884 settings, ignore this button and open that app manually from the launcher.) Create a 1885 lockscreen password and if available, enroll a fingerprint under "Work profile security".\n 1886 2. Go through the list of tests.\n 1887 3. Mark the overall test pass or fail.\n 1888 4. Once the set of tests are completed, remove the lockscreen challenge. 1889 </string> 1890 <string name="provisioning_byod_auth_bound_key_set_up">Set up</string> 1891 <string name="provisioning_byod_lockscreen_bound_key">Lockscreen-bound key test</string> 1892 <string name="provisioning_byod_fingerprint_bound_key">Fingerprint-bound key test</string> 1893 <string name="provisioning_byod_vpn">VPN test</string> 1894 <string name="provisioning_byod_always_on_vpn">Always-on VPN Settings</string> 1895 <string name="provisioning_byod_always_on_vpn_info"> 1896 In this test, you\'ll verify that the Settings UI for always-on VPN is correct for different 1897 VPN apps. 1898 </string> 1899 <string name="provisioning_byod_always_on_vpn_instruction"> 1900 In this test, you\'ll verify the Settings UI for always-on VPN for different VPN apps. 1901 You should have received three VPN app apks with this CTS Verifier package. 1902 They\'re named in the form of \"CtsVpnFirewallApp*.apk\".\n 1903 1904 1. Before the test, make sure CtsVpnFirewallApp isn\'t installed on your device. You can 1905 uninstall either by UI, or by\n 1906 \"adb uninstall com.android.cts.vpnfirewall\"\n 1907 1908 2. Install the first test app, by running\n 1909 \"adb install /path/to/CtsVpnFirewallAppApi23.apk\"\n 1910 1911 3. Tap \"Prepare VPN\" button below and consent to the VPN connection.\n 1912 1913 4. Finish all three test cases listed below.\n 1914 1915 5. Repeat step 1 to remove CtsVpnFirewallApp. 1916 </string> 1917 <string name="provisioning_byod_always_on_vpn_prepare_button">Prepare VPN</string> 1918 <string name="provisioning_byod_always_on_vpn_vpn_not_found_note"> 1919 Can\'t find VPN app. Did you install it correctly? 1920 </string> 1921 <string name="provisioning_byod_always_on_vpn_api23">VPN app targeting SDK 23</string> 1922 <string name="provisioning_byod_always_on_vpn_api23_instruction"> 1923 1. Re-install CtsVpnFirewallAppApi23.apk (skip this if you already have the correct version 1924 installed):\n 1925 \"adb install -r /path/to/CtsVpnFirewallAppApi23.apk\"\n 1926 2. Tap \"Go\" button below to go to the VPN settings page.\n 1927 3. Open configuration details page for CtsVpnFirewallApp.\n 1928 4. Confirm the \"Always-on VPN\" and \"Block connections without VPN\" switches are both off 1929 and disabled.\n 1930 </string> 1931 <string name="provisioning_byod_always_on_vpn_api24">VPN app targeting SDK 24</string> 1932 <string name="provisioning_byod_always_on_vpn_api24_instruction"> 1933 1. Re-install CtsVpnFirewallAppApi24.apk (skip this if you already have the correct version 1934 installed):\n 1935 \"adb install -r /path/to/CtsVpnFirewallAppApi24.apk\"\n 1936 2. Tap \"Go\" button below to go to the VPN settings page.\n 1937 3. Open configuration details page for CtsVpnFirewallApp.\n 1938 4. Confirm\n 1939 4.1. \"Always-on VPN\" switch is enabled and in off position\n 1940 4.2. \"Block connections without VPN\" switch is disabled and in off position\n 1941 4.3. \"Block connections without VPN\" becomes enabled once the \"Always-on VPN\" switch 1942 is turned on\n 1943 </string> 1944 <string name="provisioning_byod_always_on_vpn_not_always_on">VPN app with opt-out</string> 1945 <string name="provisioning_byod_always_on_vpn_not_always_on_instruction"> 1946 1. Re-install CtsVpnFirewallAppNotAlwaysOn.apk (skip this if you already have the correct 1947 version installed):\n 1948 \"adb install -r /path/to/CtsVpnFirewallAppNotAlwaysOn.apk\"\n 1949 2. Tap \"Go\" button below to go to the VPN settings page.\n 1950 3. Open configuration details page for CtsVpnFirewallApp.\n 1951 4. Confirm the \"Always-on VPN\" and \"Block connections without VPN\" switches are both off 1952 and disabled.\n 1953 </string> 1954 <string name="provisioning_byod_select_work_challenge">Select work lock test</string> 1955 <string name="provisioning_byod_select_work_challenge_description"> 1956 This test verifies that a work lock can be chosen.\n 1957 1958 1. Verify that you get sent to the page for Choosing a new work lock.\n 1959 2. Set a new work lock. 1960 </string> 1961 <string name="provisioning_byod_confirm_work_credentials">Confirm work lock test</string> 1962 <string name="provisioning_byod_confirm_work_credentials_description"> 1963 This test verifies that work lock is shown when opening a work app, 1964 the work lock was set correctly and it is customized according to 1965 the policies set. You can only do this test after you have done the previous test.\n 1966 Before running this test press the power button to turn the screen off and then back on and 1967 swipe to unlock.\n 1968 1969 1. Open a work app.\n 1970 2. Verify that a screen asking you for your work credentials is shown.\n 1971 3. Verify that the background image contains a suitcase.\n 1972 4. Verify that the background color of the remaining image is blue.\n 1973 5. Verify that the header text says \"CtsVerifier\".\n 1974 6. Confirm your credentials and verify that the credentials you entered previously work. 1975 7. The work app should be launched. 1976 </string> 1977 <string name="provisioning_byod_confirm_work_credentials_header"> 1978 CtsVerifier 1979 </string> 1980 1981 <string name="provisioning_byod_recents">Recents redaction test</string> 1982 <string name="provisioning_byod_recents_info"> 1983 This test verifies that if a work profile is locked with a separate password, Recents views 1984 for applications in the work profile are redacted. 1985 </string> 1986 <string name="provisioning_byod_recents_instructions"> 1987 This test verifies that if a work profile is locked with a separate password, Recents views 1988 for applications in the work profile are redacted.\n 1989 Some devices may not lock as soon as the screen is turned off by default. On such devices, 1990 use the button below when requested to lock the work profile. Please skip these tests if 1991 "Recents" is absent. 1992 </string> 1993 <string name="provisioning_byod_recents_lock_now">Lock now</string> 1994 1995 <string name="provisioning_byod_recents_verify_redacted"> 1996 Verify recents are redacted when locked. 1997 </string> 1998 <string name="provisioning_byod_recents_verify_redacted_instruction"> 1999 1) Follow the instructions on-screen to set a work password.\n 2000 2) Turn the screen off and on again, or use the "lock now" button, to lock the work profile.\n 2001 3) Open Recents.\n 2002 4) Confirm that this "CTS Verifier" activity is shown in Recents.\n 2003 5) Confirm that the contents of the activity <b>are</b> hidden.\n 2004 6) Return to this page and pass the test. 2005 </string> 2006 <string name="provisioning_byod_recents_verify_not_redacted"> 2007 Verify recents are not redacted when unlocked. 2008 </string> 2009 <string name="provisioning_byod_recents_verify_not_redacted_instruction"> 2010 1) Follow the instructions on-screen to remove the work password.\n 2011 2) Open Recents.\n 2012 3) Confirm that this "CTS Verifier" activity is shown in Recents.\n 2013 4) Confirm that the contents of the activity <b>are not</b> hidden.\n 2014 5) Return to this page and pass the test. 2015 </string> 2016 <string name="provisioning_byod_recents_remove_password"> 2017 The work profile still has a separate password. Please remove this before continuing. 2018 </string> 2019 2020 <string name="provisioning_byod_keychain">KeyChain test</string> 2021 <string name="provisioning_byod_keychain_info_start"> 2022 In this test, you\'ll verify that keys generated by KeyChain keys are as usable as keys 2023 installed into KeyChain and that they can be hidden from users.\n 2024 The test has two parts:\n 2025 1) Testing that a generated key can be selectable by the user.\n 2026 2) Testing that a generated key can be hidden from users.\n 2027 \n 2028 Tap \"Prepare Test\" button below to begin.\n 2029 \n 2030 NOTE: A screen lock must be configured for this test. Otherwise, test preparation 2031 will fail to generate a key for use by the test. 2032 </string> 2033 <string name="provisioning_byod_keychain_info_first_test"> 2034 Once you press \'Go\', a prompt titled \"Choose certificate\" should appear.\n 2035 Verify that the list in this dialog has one item, starting with \'cts-verifier-gen\'. 2036 Press \'Select\' to select it.\n 2037 If the test passes, you\'ll see the text \"Second test ready\" at the bottom.\n 2038 \n 2039 Press \'Go\'.\n 2040 </string> 2041 <string name="provisioning_byod_keychain_info_second_test"> 2042 Once you press \'Run 2nd test\', the same prompt should appear again.\n 2043 This time, verify that the title is \"No certificates found\" and the list is empty, 2044 then press \'Cancel\'.\n 2045 \n 2046 Mark the test as passed if the text at the bottom shows \"PASSED (2/2)\"\n 2047 </string> 2048 2049 <!-- Strings for DeskClock --> 2050 <string name="deskclock_tests">Alarms and Timers Tests</string> 2051 <string name="deskclock_tests_info"> 2052 The Alarms and Timers tests verify that the Clock app implements the AlarmClock API properly. 2053 </string> 2054 <string name="deskclock_group_alarms">Alarms</string> 2055 <string name="deskclock_group_timers">Timers</string> 2056 2057 <string name="dc_show_alarms_test">Show Alarms Test</string> 2058 <string name="dc_show_alarms_test_info"> 2059 This test verifies that the SHOW_ALARMS API works.\n 2060 1. Press the "Show Alarms" button.\n 2061 2. Verify that a UI of the clock app is launched and displays the list of alarms\n 2062 </string> 2063 <string name="dc_show_alarms_button">Show Alarms</string> 2064 2065 <string name="dc_set_alarm_with_ui_test">Set Alarm Test</string> 2066 <string name="dc_set_alarm_with_ui_test_info"> 2067 This test verifies that the ACTION_SET_ALARM with no parameters API works.\n 2068 1. Press the "Set Alarm" button.\n 2069 2. Verify that the clock app is launched and displays a UI to manage alarms.\n 2070 </string> 2071 <string name="dc_set_alarm_button">Set Alarm</string> 2072 <string name="dc_set_alarm_verify_button">Verify</string> 2073 2074 <string name="dc_start_alarm_test">Start Alarm Test</string> 2075 <string name="dc_start_alarm_test_info"> 2076 This test verifies that the ACTION_SET_ALARM API actually starts an alarm.\n 2077 1. Press the "Start Alarm" button.\n 2078 2. Make sure the alarms UI is NOT shown\n 2079 3. Wait for the alarm to fire (may take up to 2 minutes)\n 2080 4. Verify that the alarm title is: "Start Alarm Test",\n 2081 the alarm is silent and vibrating (if the device supports vibrate).\n 2082 5. Dismiss the alarm.\n 2083 6. Verify that the alarm is not in the Clock\'s alarms list. The Verify button opens 2084 the alarm view.\n 2085 </string> 2086 <string name="dc_start_alarm_button">Start Alarm</string> 2087 2088 <string name="dc_full_alarm_test">Full Alarm Test</string> 2089 <string name="dc_full_alarm_test_info"> 2090 This test verifies that the ACTION_SET_ALARM API supports all extras.\n 2091 1. Press the "Create Alarm" button.\n 2092 2. Verify that you see one alarm with the following information:\n 2093 Name of alarm: Create Alarm Test. \n 2094 Vibrate: on. (if the device supports vibrate).\n 2095 Ringtone: silent. (if the device has a speaker).\n 2096 Time: 01:23. \n 2097 Repeating on: Monday and Wednesday. \n 2098 </string> 2099 <string name="dc_full_alarm_button">Create Alarm</string> 2100 2101 <string name="dc_set_timer_with_ui_test">Set Timer Test</string> 2102 <string name="dc_set_timer_with_ui_test_info"> 2103 This test verifies that the ACTION_SET_TIMER API with no paramters open the UI\n 2104 1. Press the "Set Timer" button.\n 2105 2. Verify that the an app is launched and displays a UI to manage timers.\n 2106 </string> 2107 <string name="dc_set_timer_with_ui_button">Set Timer</string> 2108 2109 <string name="dc_start_timer_test">Start Timer Test</string> 2110 <string name="dc_start_timer_test_info"> 2111 This test verifies that the ACTION_SET_TIMER API actually starts a timer\n 2112 1. Press the "Start Timer" button.\n 2113 2. Verify that a timer is started and NO timers UI is shown.\n 2114 3. Verify that the timer named "Start Timer Test" rings after 30 seconds. Dismiss it.\n 2115 4. Verify that the timer is deleted after the dismissal.\n 2116 </string> 2117 <string name="dc_start_timer_button">Start Timer</string> 2118 2119 <string name="dc_start_timer_with_ui_test">Start Timer With UI Test</string> 2120 <string name="dc_start_timer_with_ui_test_info"> 2121 This test verifies that the ACTION_SET_TIMER API actually starts a timer with UI\n 2122 1. Press the "Start Timer" button.\n 2123 2. Verify that a timer is started and the timers UI is shown with a timer named "Start Timer Test".\n 2124 3. Verify that the timer rings after 30 seconds.\n 2125 </string> 2126 <!-- Strings for LockConfirmBypassTest --> 2127 <string name="lock_confirm_test_title">Keyguard Password Verification</string> 2128 <string name="lock_set_button_text">Set password</string> 2129 <string name="lock_change_button_text">Change password</string> 2130 <string name="lock_confirm_message"> 2131 This test verifies that the user is prompted for the current keyguard password before prompting for a new password.\n 2132 \nClick the \"Set password\" button if you currently don\'t have a password set.\n 2133 \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. 2134 </string> 2135 2136 <!-- String for Projection Tests --> 2137 <string name="test_category_projection">Projection Tests</string> 2138 <string name="projection_service_name">Projection Service</string> 2139 <string name="pca_info">This tests whether or not OpenGL projection works.\n 2140 You should see two "tumbling cubes." Tapping the screen should cause the cubes to explode.</string> 2141 <string name="pca_test">Projection Cube Test</string> 2142 <string name="pwa_info">This tests whether or displaying widgets and keyfocus navigation works.\n 2143 You should see four buttons on the bottom of the screen.\n 2144 Pressing the "up" and "down" buttons should highlight different buttons.\n 2145 Furthermore, the highlight should disappear when any button is touched, and the touched button should behave as usual.\n</string> 2146 <string name="pwa_test">Projection Widget Test</string> 2147 <string name="pwa_button_up">Up</string> 2148 <string name="pwa_button_down">Down</string> 2149 <string name="pwa_button">Button</string> 2150 <string name="pla_test">Projection Scrolling List Test</string> 2151 <string name="pla_info">This tests whether a projected list view will scroll properly\n 2152 You should see 50 list items and be able to scroll up and down the list</string> 2153 <string name="pva_test">Projection Video Playback Test</string> 2154 <string name="pva_info">This tests whether video playback works when projected.\n 2155 You should see a blinking white box and here a beep that is synchronized with each blink</string> 2156 <string name="pta_test">Projection Multitouch Test</string> 2157 <string name="pta_info">This tests whether multitouch works.\n 2158 Touching the screen should render a dot at the location you touched.\n 2159 Touching with additional fingers will render additoinal dots and you should be able to drag them around.</string> 2160 <string name="poa_test">Projection Offscreen Activity</string> 2161 <string name="poa_info">This tests whether a virtual display will continue to respond to and render even when the screen is off.\n 2162 Simply follow the instructions and the test will detect the pass conditions.\n 2163 Note that turning on the screen too early will result in a failure.</string> 2164 2165 <!-- Strings for RotationVectorTest and GameRotationVectorTest --> 2166 <string name="rotation_vector_test">Rotation Vector Accuracy Test</string> 2167 <string name="snsr_rotation_vector_set_reference"> 2168 Place the mobile device in a reference position. Note: to provide an accurate reference, 2169 align the device along one edge of a notebook laying on a table.</string> 2170 <string name="snsr_rotation_vector_reference_set">Reference position set.</string> 2171 <string name="snsr_rotation_vector_move_info">Move, shake, and rotate the device.</string> 2172 <string name="snsr_rotation_vector_set_final">Place the device back to the reference position.</string> 2173 <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> 2174 2175 <!-- Strings for device admin tests --> 2176 <string name="device_admin_notification">This is device admin notification</string> 2177 <string name="device_admin_keyguard_disable_camera">Disable camera</string> 2178 <string name="device_admin_keyguard_disable_camera_instruction"> 2179 Please press the Go button to lock the screen. Then try to open the camera 2180 from the lower right corner of the screen. Expected result is you cannot 2181 open the camera from lock screen and it will ask for password instead.\n 2182 Also, it shouldn\'t be possible to open the camera on the lockscreen by 2183 any other device specific gesture (such as double press on power button). 2184 </string> 2185 <string name="device_admin_disable_notifications">Disable notifications</string> 2186 <string name="device_admin_disable_notifications_instruction"> 2187 Please press the Go button to lock the screen. Wait a few seconds to see 2188 if a notification appears. Expected result is no notifications appear. 2189 You should be able to see one after unlocking. 2190 </string> 2191 <string name="device_admin_disable_unredacted_notifications">Disable unredacted notifications</string> 2192 <string name="device_admin_disable_unredacted_notifications_instruction"> 2193 Please press the Go button to lock the screen. Wait a few seconds to see 2194 if a notification appears. Expected result is a notification appear with 2195 its content hidden. You should be able to see the content after unlocking. 2196 </string> 2197 2198 <!-- Strings common for BYOD and DO managed provisioning tests. --> 2199 <string name="afw_device_admin">CTS Verifier</string> 2200 2201 <string name="provisioning_tests_byod">BYOD Provisioning tests</string> 2202 2203 <string name="provisioning_tests_byod_custom_color"> Custom provisioning color </string> 2204 <string name="provisioning_tests_byod_custom_color_info"> 2205 Please press the Go button to start the provisioning. 2206 Check that the top status bar and "Accept and continue" button are colorized in green. 2207 Then hit back and stop the provisioning. 2208 </string> 2209 <string name="provisioning_tests_byod_custom_image"> Custom provisioning image </string> 2210 <string name="provisioning_tests_byod_custom_image_info"> 2211 1. Please press the Go button to start the provisioning.\n 2212 2. Press \"Accept and continue\" button to start work profile provisioning\n 2213 3. Check that the CtsVerifier logo is displayed during provisioning\n 2214 4. After successful provisioning, you should be automatically redirected back to this page 2215 </string> 2216 <string name="provisioning_tests_byod_custom_terms">Custom terms</string> 2217 <string name="provisioning_tests_byod_custom_terms_instructions"> 2218 1. Please press the Go button to start the provisioning.\n 2219 2. Click \"View Terms\" button\n 2220 3. Expand \"Company ABC\" section. Verify the section content is \"Company Terms Content.\"\n 2221 4. Then hit back twice and stop the provisioning. 2222 </string> 2223 <string name="provisioning_tests_byod_custom_term_header1">Company ABC</string> 2224 2225 <!-- Strings for BYOD managed provisioning (ByodFlowTestActivity) --> 2226 <string name="test_category_managed_provisioning">Managed Provisioning</string> 2227 <string name="provisioning_byod">BYOD Managed Provisioning</string> 2228 <string name="provisioning_byod_info"> 2229 This test exercises the BYOD managed provisioning flow. 2230 Start by pressing the button on screen and follow instructions to finish the managed provisioning process. 2231 If your device has not been encrypted before, it will be encrypted and rebooted. 2232 After the provisioning process completes, return to this page and carry out further verifications. 2233 Note: the device will remain encrypted after the test which can only be disabled by factory reset. 2234 </string> 2235 <string name="provisioning_byod_start">Start BYOD provisioning flow</string> 2236 <string name="provisioning_byod_instructions"> 2237 1. Press the button below to start the managed provisioning flow. 2238 If your device has not been encrypted before, it will reboot to apply encryption. 2239 After reboot follow instructions in the notification area to complete the provisioning.\n 2240 2. After successful provisioning, you should be automatically redirected back to this page. 2241 Please press through the following verification steps. 2242 Allow a few seconds after returning from provisioning, as the profile owner test should automatically pass.\n 2243 \n 2244 If the device is being encrypted during step 1, it will remain encrypted After this test. 2245 The only way to disable the encryption is to factory reset the device. 2246 </string> 2247 <string name="provisioning_byod_profileowner">Profile owner installed</string> 2248 <string name="provisioning_byod_disk_encryption">Full disk encryption enabled</string> 2249 <string name="provisioning_byod_disk_encryption_default_key_toast"> 2250 Cannot secure device with screen lock. Please re-run the test if you forgot to select 2251 the \"require PIN to boot\" option. 2252 </string> 2253 <string name="provisioning_byod_disk_encryption_no_pin_toast"> 2254 No PIN is detected. Please re-run the test if you forgot to set a PIN. 2255 </string> 2256 <string name="provisioning_byod_set_screen_lock_dialog_message"> 2257 Next, you will be asked to set a screen lock for the device.\n 2258 \n 2259 Please set \"1111\" as the new PIN (or any other PIN that you can memorize). 2260 You have to enter this PIN again later in order to finish the test.\n 2261 \n 2262 You may be asked whether the PIN should be required to boot the device. Please answer yes.\n 2263 \n 2264 Tap Go button to set a new screen lock. 2265 </string> 2266 <string name="provisioning_byod_remove_screen_lock_dialog_message"> 2267 The test is almost finished. \n 2268 \n 2269 Next, you will be asked to remove the screen lock that you just set. Please enter \"1111\" 2270 (or your own PIN) when prompted for the old PIN, and do not set any new screen lock. This 2271 is to make sure that the device returns to the initial state after this test.\n 2272 \n 2273 Tap Go button to remove existing screen lock. 2274 </string> 2275 <string name="provisioning_byod_profile_visible">Profile-aware accounts settings</string> 2276 <string name="provisioning_byod_admin_visible">Profile-aware device administrator settings</string> 2277 <string name="provisioning_byod_workapps_visible">Badged work apps visible in Launcher</string> 2278 <string name="provisioning_byod_cross_profile_from_personal">Open app cross profiles from the personal side</string> 2279 <string name="provisioning_byod_cross_profile_from_work">Open app cross profiles from the work side</string> 2280 <string name="provisioning_app_linking">App links from the work side</string> 2281 <string name="provisioning_byod_cross_profile_app_personal">You selected the personal option.</string> 2282 <string name="provisioning_byod_cross_profile_app_work">You selected the Work option.</string> 2283 <string name="provisioning_byod_cross_profile_app_ctsverifier"> You selected the ctsverifier option </string> 2284 <string name="provisioning_byod_cross_profile_from_personal_instruction"> 2285 Please press the Go button to start an action.\n 2286 \n 2287 You should be asked to choose either \"CTS Verifier\" or \"Work\" to complete the action. 2288 Pressing either should bring up a page stating your choice.\n 2289 \n 2290 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 2291 </string> 2292 <string name="provisioning_byod_cross_profile_from_work_instruction"> 2293 Please press the Go button to start an action.\n 2294 \n 2295 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action. 2296 Pressing either should bring up a page stating your choice.\n 2297 \n 2298 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 2299 </string> 2300 <string name="provisioning_byod_app_linking_instruction"> 2301 Please press the Go button to start an action.\n 2302 \n 2303 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action.\n 2304 - If you choose \"CTS Verifier\", you should see a page stating your chose \"CTS Verifier\".\n 2305 - If you choose \"Personal\", you should be presented with another dialog between \"CTS Verifier\" 2306 and some other apps. In this case, you should choose \"CTS verifier\".\n 2307 You should then see a page stating you chose \"Personal\".\n 2308 \n 2309 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 2310 </string> 2311 <string name="provisioning_byod_keyguard_disabled_features">Keyguard disabled features</string> 2312 <string name="provisioning_byod_keyguard_disabled_features_info"> 2313 This test exercises Keyguard Disabled Features. Follow instructions above. 2314 </string> 2315 <string name="provisioning_byod_keyguard_disabled_features_instruction"> 2316 Please go to Settings > Security > Device administrators and set 2317 \"CTS Verifier\" as active admin.\n 2318 After that please go to Settings > Security > Screen lock and set 2319 your screen lock password to \"testpassword\".\n 2320 Then please press the \"Prepare test\" button to disable trust agents.\n 2321 Then please press through the following verification steps.\n 2322 Note: After leaving the screen active admin status will be cleared. 2323 Please go to Settings > Security > Screen lock and set your 2324 password type to \"None\". 2325 </string> 2326 <string name="provisioning_byod_keyguard_disabled_features_prepare_button">Prepare test</string> 2327 <string name="provisioning_byod_keyguard_disabled_features_not_admin">CtsVerifier is not active admin. Please follow instructions.</string> 2328 <string name="provisioning_byod_disable_trust_agents">Disable trust agents</string> 2329 <string name="provisioning_byod_disable_trust_agents_instruction"> 2330 Please press the Go button to go to Settings > Security. Then go to Trusted agents and\n 2331 check if the agents are shown as disabled by the administrator. 2332 Then please press Back and mark the test as \"Pass\" or \"Fail\". 2333 </string> 2334 <string name="provisioning_byod_fingerprint_disabled_in_settings">Fingerprint is disabled in Settings</string> 2335 <string name="provisioning_byod_fingerprint_disabled_in_settings_instruction"> 2336 Please press the Go button to go to Settings > Security. Then go to Fingerprint and\n 2337 check if the disclaimer at the bottom of screen is altered to warn the users for\n 2338 fingerprint being disabled in lock screen. Then please press Back and mark the \n 2339 test as \"Pass\" or \"Fail\". 2340 </string> 2341 <string name="provisioning_byod_disable_fingerprint">Fingerprint disabled on keyguard</string> 2342 <string name="provisioning_byod_disable_fingerprint_instruction"> 2343 Please press the Go button to lock the screen. Then try to log in using the fingerprint reader.\n 2344 Expected result is you cannot log in using your fingerprint.\n 2345 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\". 2346 </string> 2347 <string name="provisioning_byod_disable_unredacted_notifications">Unredacted notifications disabled on keyguard</string> 2348 <string name="provisioning_byod_disable_unredacted_notifications_instruction"> 2349 Please press the Go button to lock the screen. Wait a couple of seconds and look out for a 2350 notification from CtsVerifier.\n 2351 Expected result is the notification is shown as \"Contents hidden by policy\", you can not see the contents 2352 (Which would read \"This is a notification\"). You should be seeing a work badge.\n 2353 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\". 2354 </string> 2355 <string name="provisioning_byod_work_notification">Work notification is badged</string> 2356 <string name="provisioning_byod_work_notification_instruction"> 2357 Please press the Go button to trigger a notification.\n 2358 \n 2359 Verify that the notification is badged (see sample badge below). Then mark this test accordingly. 2360 </string> 2361 <string name="provisioning_byod_notification_title">This is a notification</string> 2362 <string name="provisioning_byod_notification_public_title">Contents hidden by policy</string> 2363 2364 <string name="provisioning_byod_disallow_apps_control">Disallow apps control</string> 2365 <string name="provisioning_byod_disallow_apps_control_info"> 2366 This test exercises Disallow Apps Control. Follow instructions above. 2367 </string> 2368 <string name="provisioning_byod_disallow_apps_control_instruction"> 2369 Please press the \"Prepare test\" button to disallow apps control for managed apps.\n 2370 Then please press through the following verification steps.\n 2371 Note: After leaving the screen disallow apps control restriction will be cleared. 2372 </string> 2373 <string name="provisioning_byod_disallow_apps_control_prepare_button">Prepare test</string> 2374 <string name="provisioning_byod_disabled_uninstall_button">Disabled uninstall button</string> 2375 <string name="provisioning_byod_disabled_uninstall_button_instruction"> 2376 Please press the Go button to go to Settings > Apps. 2377 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 2378 Choose a managed app. Check that performing either \"Uninstall\" or \"Disable\" is not possible and triggers a support message when trying to do so. 2379 Then please press Back (or navigate back to this app using Recents) and mark the test as \"Pass\" or \"Fail\". 2380 </string> 2381 <string name="provisioning_byod_disabled_force_stop_button">Disabled force stop button</string> 2382 <string name="provisioning_byod_disabled_force_stop_button_instruction"> 2383 Please press the Go button to go to Settings > Apps. 2384 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 2385 Choose a managed app. Check that performing \"Force stop\" is not possible and triggers a support message when trying to do so. 2386 Then please press Back (or navigate back to this app using Recents) and mark the test as \"Pass\" or \"Fail\". 2387 </string> 2388 <string name="provisioning_byod_disabled_app_storage_buttons">Disabled app storage buttons</string> 2389 <string name="provisioning_byod_disabled_app_storage_buttons_instruction"> 2390 Please press the Go button to go to Settings > Apps. 2391 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 2392 Choose a managed (badged) app. Select \"Storage\". Check that performing \"Clear Data\" and \"Clear Cache\" is not possible and triggers a support message when trying to do so. 2393 Note: if an app has no data then tapping the clear data button has no effect anyway. Make sure you have selected 2394 the badged version of app with non-zero app data. Badged \"Settings\" may be a good candidate. 2395 Then please press Back (or navigate back to this app using Recents) and mark the test as \"Pass\" or \"Fail\". 2396 </string> 2397 2398 <string name="provisioning_byod_work_status_icon">Work status icon is displayed</string> 2399 <string name="provisioning_byod_work_status_icon_instruction"> 2400 Verify that the current status bar does not have a work status icon (see sample icon below). 2401 \n\n 2402 Please press the Go button to launch a work activity. 2403 \n\n 2404 Verify that the status bar now has a work status icon. Then mark this test accordingly. 2405 </string> 2406 <string name="provisioning_byod_work_status_icon_activity"> 2407 Verify that the current status bar has a work status notification. 2408 \n\n 2409 Please press finish to return to the tests and then mark this test accordingly. 2410 </string> 2411 <string name="provisioning_byod_work_status_toast">Work status toast is displayed</string> 2412 <string name="provisioning_byod_work_status_toast_instruction"> 2413 Please press the Go button to launch a work activity. 2414 \n\n 2415 Follow instructions and then return and mark this test accordingly. 2416 </string> 2417 <string name="provisioning_byod_work_status_toast_activity"> 2418 Turn off the screen and wait a few seconds then turn on the screen again. 2419 \n\n 2420 Verify that a toast was displayed saying you are in the work profile. 2421 \n\n 2422 Please press finish to return to the tests and then mark this test accordingly. 2423 </string> 2424 <string name="provisioning_byod_profile_visible_instruction"> 2425 Please press the Go button to open the Settings page. 2426 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 2427 Navigate to Accounts and confirm that:\n 2428 \n 2429 - Both Personal and Work categories exist.\n 2430 - \"Remove work profile\" or \"Uninstall\" exists under the Work category.\n 2431 \n 2432 Use the Back button (or navigate back to this app using Recents) to return to this page. 2433 </string> 2434 <string name="provisioning_byod_user_settings">Profile-aware user settings</string> 2435 <string name="provisioning_byod_user_settings_instruction"> 2436 Please press the Go button to open the Settings page. 2437 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher.)\n 2438 Navigate to Users (or \"Multiple Users\") and confirm that:\n 2439 - There are two auto-sync options present, one for personal and one for work data (either on the screen or in the overflow menu).\n 2440 - De-selecting either option prompts a warning dialog.\n 2441 \n 2442 Use the Back button (or navigate back to this app using Recents) to return to this page. 2443 </string> 2444 <string name="provisioning_byod_admin_visible_instruction"> 2445 Please press the Go button to open the Security page in Settings. 2446 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 2447 Navigate to Device admin apps and confirm that:\n 2448 \n 2449 - Device administrators outside of the work profile (if any) appear in the list, and the managed profile administrators are badged correctly.\n 2450 - A badged \"CTS Verifier\" exists, and is activated.\n 2451 - There is no option to deactivate the badged \"CTS Verifier\" version, only an option to \"Remove work profile\".\n 2452 \n 2453 Use the Back button (or navigate back to this app using Recents) to return to this page. 2454 </string> 2455 <string name="provisioning_byod_workapps_visible_instruction"> 2456 Please press the Go button to start the launcher. 2457 Go to All Apps screen and scroll through it to confirm that:\n 2458 \n 2459 - A new set of work apps including CTS Verifier appear in the list.\n 2460 - Work badge overlay appears on work app\'s icon (see example icon below, color and style may vary).\n 2461 \n 2462 Then navigate back to this screen using Recents button. 2463 </string> 2464 2465 <string name="provisioning_byod_app_settings">Profile-aware app settings</string> 2466 <string name="provisioning_byod_app_settings_instruction"> 2467 Please press the Go button to open Apps page in settings. 2468 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 2469 \n 2470 Verify that work profile exists in the dropdown list and selecting it will 2471 bring up apps setting in the work profile.\n 2472 \n 2473 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 2474 </string> 2475 2476 <string name="provisioning_byod_location_settings">Profile-aware location settings</string> 2477 <string name="provisioning_byod_location_settings_instruction"> 2478 Please press the Go button to open Location page in settings. 2479 (If this device has a separate app for work settings, ignore the Go button and navigate to that app manually, if necessary).\n 2480 \n 2481 Verify that work profile entry exists in the page and it has a toggleable switch.\n 2482 Switch the main location switch at the top of the screen off. You should see the work profile location switch go disabled and into \'off\' state.\n 2483 Then switch the main location switch on again. You should see the work profile location switch go enabled and into its previous state.\n 2484 \n 2485 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 2486 </string> 2487 2488 <string name="provisioning_byod_wifi_data_usage_settings">Profile-aware data usage settings (Wi-Fi)</string> 2489 <string name="provisioning_byod_wifi_data_usage_settings_instruction"> 2490 Please press the Go button to open the Settings page. 2491 (If this device has a separate app for work settings, ignore the Go button and navigate to that app manually).\n 2492 \n 2493 Navigate to \"Data usage\" page and then into the \"Wi-Fi data usage\" category.\n 2494 Confirm that \"All work apps\" section is present and that it is possible to see the data usage for work (badged) apps.\n 2495 \n 2496 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 2497 </string> 2498 2499 <string name="provisioning_byod_cellular_data_usage_settings">Profile-aware data usage settings (Mobile)</string> 2500 <string name="provisioning_byod_cellular_data_usage_settings_instruction"> 2501 Please disable Wi-Fi connection on your device.\n 2502 Please make sure you have added a SIM card with data plan to your phone, have enabled data over mobile and in case of dual SIM devices, have selected the right SIM for data connection.\n 2503 Please carry out operations that will use mobile data using both badged and unbadged apps (e.g. visit a page in a browser).\n 2504 \n 2505 Please press the Go button to open the Settings page. 2506 (If this device has a separate app for work settings, ignore the Go button and navigate to that app manually).\n 2507 \n 2508 Navigate to \"Data usage\" page and then into the \"Mobile data usage\" category.\n 2509 Confirm that \"All work apps\" section is present and that it is possible to see the data usage for work (badged) apps.\n 2510 \n 2511 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 2512 </string> 2513 2514 <string name="provisioning_byod_cred_settings">Profile-aware trusted credential settings</string> 2515 <string name="provisioning_byod_cred_settings_instruction"> 2516 Please press the Go button to open the Security settings. 2517 Navigate to "Trusted credentials" and wait for the UI to load. 2518 After the list is loaded, confirm that:\n 2519 \n 2520 The page list credentials for both "Personal" and "Work" profiles.\n 2521 \n 2522 Then use the Back button to return to this test and mark accordingly. 2523 </string> 2524 2525 <string name="provisioning_byod_print_settings">Profile-aware printing settings</string> 2526 <string name="provisioning_byod_print_settings_instruction"> 2527 Please press the Go button to open the Printing settings. 2528 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 2529 \n 2530 Verify that work profile exists in the dropdown list and selecting it will 2531 bring up printing setting in the work profile.\n 2532 \n 2533 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 2534 </string> 2535 2536 <string name="provisioning_byod_cross_profile_intent_filters">Cross profile intent filters are set</string> 2537 2538 <string name="provisioning_byod_nfc_beam">Disable Nfc beam</string> 2539 <string name="provisioning_byod_nfc_beam_allowed_instruction"> 2540 Please press the Go button to test if Nfc beam can be triggered in the work profile.\n 2541 \n 2542 For the first test, press \"Send manual beam\" to trigger a beam, then bump into another device to send the tag. Verify that the tag is successfully received.\n 2543 \n 2544 For the second test, press \"Send share intent\" to trigger a beam, then bump into another device to send the tag. Verify that the tag is successfully received.\n 2545 \n 2546 Then use the Back button to return to this test and mark accordingly. 2547 </string> 2548 <string name="provisioning_byod_nfc_beam_disallowed_instruction"> 2549 Please press the Go button to test if Nfc beam is disallowed by policy 2550 \n 2551 Verify that Nfc beam is not triggered when pressing the button.\n 2552 \n 2553 Then use the Back button to return to this test and mark accordingly. 2554 </string> 2555 <string name="provisioning_byod_send_manual_beam">Send manual beam</string> 2556 <string name="provisioning_byod_send_share_intent">Send share intent</string> 2557 <string name="provisioning_byod_cannot_resolve_beam_activity">Cannot find beam activity</string> 2558 2559 <string name="test_failed_cannot_start_intent">Cannot start the given intent.</string> 2560 <string name="provisioning_byod_no_activity">Cannot communicate with activity in the work profile.</string> 2561 <string name="provisioning_byod_delete_profile">Initiate deletion of work profile.</string> 2562 <string name="provisioning_byod_profile_deleted">Work profile deleted.</string> 2563 <string name="provisioning_byod_disabled">Device provisioning is not enabled.</string> 2564 <string name="provisioning_button_finish">Finish</string> 2565 <string name="provisioning_cross_profile_chooser">Choose an app to complete action</string> 2566 2567 <string name="provisioning_byod_no_gps_location_feature">No GPS feature present. Skip test.</string> 2568 <string name="provisioning_byod_location_mode_enable">Enable location</string> 2569 <string name="provisioning_byod_location_mode_enable_toast_location_change">Location changed</string> 2570 <string name="provisioning_byod_location_mode_enable_instruction"> 2571 This test verifies that the location updates can be enabled for the managed profile apps.\n 2572 1. Press the go button to go to the location settings page, set both the main location switch and the work profile location switch enabled.\n 2573 2. Move your position a little bit, verify that location updates toast comes up.\n 2574 Please wait until the location updates or timeout toast message shows up before going back to the cts-verifier tests.\n 2575 3. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n 2576 </string> 2577 2578 <string name="provisioning_byod_location_mode_disable">Disable location</string> 2579 <string name="provisioning_byod_location_mode_time_out_toast">Timeout waiting for gps location change</string> 2580 <string name="provisioning_byod_location_mode_disable_instruction"> 2581 This test verifies that the location updates can be disabled for the managed profile apps through the main location switch.\n 2582 1. Press the go button to go to the location settings page, set the main location switch disabled.\n 2583 2. Move your position a little bit, verify that no location updates toast come up and that the timeout message show up after around 15 seconds. 2584 Please wait until the timeout or location updates toast message shows up before going back to the cts-verifier tests.\n 2585 3. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n 2586 </string> 2587 2588 <string name="provisioning_byod_work_location_mode_disable">Disable location for work profile</string> 2589 <string name="provisioning_byod_work_location_mode_disable_instruction"> 2590 This test verifies that the location updates can be disabled for the managed profile apps through work profile location switch.\n 2591 1. Press the go button to go to the location settings page, set the work location switch disabled while the main location switch is still enabled.\n 2592 2. Move your position a little bit, verify that no location updates toast come up and that the timeout message show up after around 15 seconds. 2593 Please wait until the timeout or location updates toast message shows up before going back to the cts-verifier tests.\n 2594 3. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n 2595 </string> 2596 <string name="provisioning_byod_primary_location_when_work_disabled">Primary receives updates while work location is disabled</string> 2597 <string name="provisioning_byod_primary_location_when_work_disabled_instruction"> 2598 This test verifies that location updates are still received by primary profile when location updates are disabled for managed profile apps through work profile location switch.\n 2599 1. Press the go button to go to the location settings page, set the work location switch disabled while the main location switch is still enabled.\n 2600 2. Move your position a little bit, verify that location updates toast comes up.\n 2601 Please wait until the location updates or timeout toast message shows up before going back to the cts-verifier tests.\n 2602 3. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n 2603 </string> 2604 2605 <string name="provisioning_byod_turn_off_work">Turn off work profile</string> 2606 <string name="provisioning_byod_turn_off_work_info">This test verifies device behaviors when turning off work profile.</string> 2607 <string name="provisioning_byod_turn_off_work_instructions"> 2608 This test verifies the device behavior when work profile is turned off.\n 2609 Please exercise the following tests in sequence.\n 2610 The button below can be used to open the Settings page where you can toggle work profile.\n 2611 (If this device has a separate app for work settings, ignore the button and open that app manually from the launcher).\n 2612 </string> 2613 <string name="provisioning_byod_turn_off_work_prepare_button">Open Settings to toggle work profile</string> 2614 2615 <string name="provisioning_byod_turn_off_work_prepare_notifications">Prepare a work notification</string> 2616 <string name="provisioning_byod_turn_off_work_prepare_notifications_instruction"> 2617 This is a test setup step.\n 2618 1. Press the go button to send a work notification.\n 2619 2. Verify that the notification is displayed and mark this test as passed.\n 2620 (Note: in the following test, you will be asked to verify the notification disappears after work profile is turned off.) 2621 </string> 2622 2623 <string name="provisioning_byod_turn_off_work_turned_off">Please turn off work profile</string> 2624 <string name="provisioning_byod_turn_off_work_turned_off_toast">Open settings to turn off work profile, using the button above.</string> 2625 2626 <string name="provisioning_byod_turn_off_work_notifications">Notifications when work profile is off</string> 2627 <string name="provisioning_byod_turn_off_work_notifications_instruction"> 2628 Verify that the previously-shown work notification has now disappeared. 2629 </string> 2630 2631 <string name="provisioning_byod_turn_off_work_launcher">Starting work apps when work profile is off</string> 2632 <string name="provisioning_byod_turn_off_work_launcher_instruction"> 2633 This test verifies that work applications cannot be started if work profile is off.\n 2634 1. Press home to go to the launcher.\n 2635 2. Verify that work applications are greyed out.\n 2636 3. Tap on a work application.\n 2637 4. Verify that the application does not start.\n 2638 </string> 2639 2640 <string name="provisioning_byod_turn_off_work_turned_on">Please turn work profile back on</string> 2641 <string name="provisioning_byod_turn_off_work_turned_on_toast">Open settings to turn work profile back on, either manually or using the button above.</string> 2642 2643 <string name="provisioning_byod_turn_on_work_icon">Status bar icon when work profile is on</string> 2644 <string name="provisioning_byod_turn_on_work_icon_instruction"> 2645 Now that work profile is back on, please verify that the status bar icon for work profile off is no longer visible. 2646 </string> 2647 2648 <string name="provisioning_byod_turn_on_work_launcher">Starting work apps when work profile is on</string> 2649 <string name="provisioning_byod_turn_on_work_launcher_instruction"> 2650 Now that work profile is back on, please go to the launcher and verify that you can start a work application. 2651 </string> 2652 2653 <string name="provisioning_byod_organization_info">Organization Info</string> 2654 <string name="provisioning_byod_organization_name_hint">Name</string> 2655 <string name="provisioning_byod_organization_color_hint">#FF00FF</string> 2656 <string name="provisioning_byod_set_organization_info_button_text">Set</string> 2657 <string name="provisioning_byod_organization_info_instructions"> 2658 This test verifies that the Organization Info was set correctly. 2659 You can only do this test after you have done "select work lock" test.\n 2660 1. Enter your organization name.\n 2661 2. Enter a valid color code.\n 2662 3. Press the Set button to set organization Info.\n 2663 4. Press the Go button to open a dialog to confirm work credentials.\n 2664 (If this device has a separate app for work settings, ignore the Go button and open the work lock screen manually to confirm, if necessary.)\n 2665 5. Verify that the background color of the resulting dialog is as set by you.\n 2666 6. Verify that the header text has organization name as set by you.\n 2667 </string> 2668 2669 <string name="provisioning_byod_no_secure_lockscreen">No work lockscreen password set. Please run \"Select work lock test\" and rerun this test</string> 2670 2671 <string name="provisioning_byod_parent_profile_password">Personal password test</string> 2672 <string name="provisioning_byod_parent_profile_password_description"> 2673 This test verifies that the password on the personal side can be chosen from within a managed profile.\n 2674 2675 1. Press the Go button to set a new password for the personal side.\n 2676 2. Lock and unlock the screen to verify that the personal side password was set correctly.\n 2677 </string> 2678 <string name="provisioning_byod_work_profile_widget">Work profile widget</string> 2679 <string name="provisioning_byod_work_profile_widget_info">Verify that work profile widget can be added into launcher</string> 2680 <string name="provisioning_byod_work_profile_widget_description"> 2681 This test verifies that the widget in work profile can be added into Launcher.\n 2682 2683 1. Go to home screen.\n 2684 2. Add the widget titled \"CTS Verifier\" and badged with work profile briefcase to the home screen.\n 2685 3. If you can add the widget to the home screen, please select \"pass\". Otherwise, select \"fail\". 2686 </string> 2687 2688 <!-- Strings for DeviceOwnerNegativeTestActivity --> 2689 <string name="negative_device_owner">No Device Owner Tests</string> 2690 <string name="device_owner_negative_category">No Device Owner Tests</string> 2691 <string name="device_owner_provisioning_negative">Device owner provisioning</string> 2692 <string name="device_owner_provisioning_negative_info">The device owner provisioning test verifies that setting up a corporate owned device can only be done on a factory reset device.\n\nPlease click the "Start provisioning" button, and when you see a warning dialog telling the device can\'t be set up, select "pass". Otherwise, select "fail".</string> 2693 <string name="start_device_owner_provisioning_button">Start provisioning</string> 2694 <string name="enterprise_privacy_quick_settings_negative">Quick settings disclosure</string> 2695 <string name="enterprise_privacy_quick_settings_negative_info"> 2696 Please do the following:\n 2697 1) Open and fully expand Quick Settings.\n 2698 2) Verify that at the bottom of Quick Settings, you are not told the device is managed.\n 2699 3) Close Quick Settings. 2700 </string> 2701 <string name="enterprise_privacy_keyguard_negative">Keyguard disclosure</string> 2702 <string name="enterprise_privacy_keyguard_negative_info"> 2703 Please do the following:\n 2704 1) Press the Go button to open Settings.\n 2705 2) Navigate to \"Security\" > \"Screen lock\" and select the first screen lock type that is not \"None\".\n 2706 3) Use the Back button to return to this page.\n 2707 4) Lock the device.\n 2708 5) Verify that on the lock screen, you are not told the device is managed.\n 2709 6) Unlock the device.\n 2710 7) Repeat steps (1) through (6) for each screen lock type other than \"None\". 2711 </string> 2712 <string name="enterprise_privacy_add_account_negative">Add account disclosure</string> 2713 <string name="enterprise_privacy_add_account_negative_info"> 2714 Please do the following:\n 2715 1) Press the Go button to open Settings.\n 2716 2) In the screen that opens, verify that you are not told that the device is managed.\n 2717 3) Use the Back button to return to this page. 2718 </string> 2719 2720 <!-- Strings for DeviceOwnerPositiveTestActivity --> 2721 <string name="positive_device_owner">Device Owner Tests</string> 2722 <string name="device_owner_positive_tests">Device Owner positive tests</string> 2723 <string name="device_owner_positive_tests_instructions"> 2724 The positive device owner tests verify policies on a corporate owned device.\n 2725 Press below button first, follow steps described in the dialog that pops up, 2726 then proceed to the test cases.\n 2727 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 2728 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 2729 be run last so that it does not interfere with other tests. 2730 </string> 2731 <string name="device_owner_positive_tests_info"> 2732 The positive device owner tests verify policies on a corporate owned device.\n 2733 Press below button first, follow steps described in the dialog that pops up, 2734 then proceed to the test cases.\n 2735 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 2736 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 2737 be run last so that it does not interfere with other tests. 2738 </string> 2739 <string name="device_owner_positive_category">Device Owner Tests</string> 2740 <string name="set_device_owner_button_label">Set up device owner</string> 2741 <string name="set_device_owner_dialog_title">Set up device owner</string> 2742 <string name="set_device_owner_dialog_text"> 2743 This test requires CtsEmptyDeviceOwner.apk to be installed on the device. 2744 Please set the device owner by enabling USB debugging on the device and issuing the following command on the host:\n 2745 adb shell dpm set-device-owner com.android.cts.emptydeviceowner/.EmptyDeviceAdmin 2746 </string> 2747 <string name="device_owner_remove_device_owner_test">Remove device owner</string> 2748 <string name="device_owner_remove_device_owner_test_info"> 2749 Please check in Settings > Security > Device Administrators if CTSVerifier is 2750 Device Owner. Then press the button below, and check that CTSVerifier is NOT Device 2751 Owner anymore. 2752 </string> 2753 <string name="remove_device_owner_button">Remove device owner</string> 2754 <string name="device_owner_check_device_owner_test">Check device owner</string> 2755 <string name="device_owner_incorrect_device_owner">Missing or incorrect device owner: CTSVerifier is not DO!</string> 2756 <string name="device_owner_wifi_lockdown_test">WiFi configuration lockdown</string> 2757 <string name="device_owner_wifi_lockdown_info"> 2758 Please enter the SSID and auth method of an available WiFi Access Point and press the button to create a 2759 WiFi configuration. This configuration can be seen on Settings > WiFi. The test cases 2760 are going to use this config. Please go through test cases in order (from top to bottom). 2761 </string> 2762 <string name="switch_wifi_lockdown_off_button">WiFi config lockdown off</string> 2763 <string name="switch_wifi_lockdown_on_button">WiFi config lockdown on</string> 2764 <string name="wifi_lockdown_go_settings_wifi_button">Go to WiFi Settings</string> 2765 <string name="device_owner_wifi_key_management_none_button">None</string> 2766 <string name="device_owner_wifi_key_management_wpa_button">WPA</string> 2767 <string name="device_owner_wifi_key_management_wep_button">WEP</string> 2768 <string name="create_wifi_config_button_label">Create WiFi configuration</string> 2769 <string name="wifi_lockdown_add_network_failed_dialog_title">WiFi configuration could not be created</string> 2770 <string name="wifi_lockdown_add_network_failed_dialog_text"> 2771 There was an error during creation of WiFi configuration. Check if WiFi is switched on. 2772 </string> 2773 <string name="device_owner_wifi_config_unlocked_modification_test">Unlocked config is modifiable in Settings</string> 2774 <string name="device_owner_wifi_config_unlocked_modification_test_info"> 2775 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 2776 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be edited. 2777 Please make sure you can connect to it. The test is successful if the config is editable 2778 and can be connected to. 2779 </string> 2780 <string name="device_owner_wifi_config_locked_modification_test">Locked config is not modifiable in Settings</string> 2781 <string name="device_owner_wifi_config_locked_modification_test_info"> 2782 Please press the button to ensure WiFi config lockdown is in effect. Then go to 2783 Settings > WiFi and see if the CTSVerifier created WiFi configuration can NOT be edited 2784 or removed. The test is successful if the config is NOT modifiable. 2785 </string> 2786 <string name="device_owner_wifi_config_locked_connection_test">Locked config can be connected to</string> 2787 <string name="device_owner_wifi_config_locked_connection_test_info"> 2788 Please press the button to ensure WiFi config lockdown is in effect. Then go to 2789 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be connected 2790 to manually. The test is successful if the connection can be established. 2791 </string> 2792 <string name="device_owner_wifi_config_unlocked_removal_test">Unlocked config can be forgotten in Settings</string> 2793 <string name="device_owner_wifi_config_unlocked_removal_test_info"> 2794 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 2795 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be forgotten. 2796 The test is successful if the config could be forgotten and is removed from the list of saved configs. 2797 </string> 2798 <string name="device_owner_disable_statusbar_test">Disable status bar</string> 2799 <string name="device_owner_disable_statusbar_test_info"> 2800 Please press the below button to disable the status bar and verify that quick settings, notifications 2801 and the assist gesture are no longer available.\n 2802 Next, press the button to reenable the status bar and verify that quick settings, notification 2803 and the assist gesture are available again.\n 2804 Please mark the test accordingly. 2805 </string> 2806 <string name="device_owner_disable_statusbar_button">Disable status bar</string> 2807 <string name="device_owner_reenable_statusbar_button">Reenable status bar</string> 2808 <string name="device_owner_disable_keyguard_test">Disable keyguard</string> 2809 <string name="device_owner_disable_keyguard_test_info"> 2810 Before running this test, please make sure you have not set any device lockscreen password.\n 2811 Please press the below button to disable the keyguard. Press the power button on your device to 2812 switch off the screen. Then press the power button to switch the screen back on and verify that 2813 no keyguard was shown.\n 2814 Next, press the button to reenable the keyguard and repeat the above steps, this time verifying that 2815 a keyguard was shown again.\n 2816 Please mark the test accordingly. 2817 </string> 2818 <string name="device_owner_disable_keyguard_button">Disable keyguard</string> 2819 <string name="device_owner_reenable_keyguard_button">Reenable keyguard</string> 2820 <string name="device_owner_lock_task_ui_test">LockTask UI</string> 2821 <string name="device_owner_lock_task_ui_test_info"> 2822 The following tests verify the configurable UI during LockTask, a special mode that 2823 prevents the user from leaving the current application.\n\n 2824 Please make sure the lock screen is turned on before the test. Press the button below to 2825 start LockTask mode. Then mark each item as \'pass\' or \'fail\' according to the 2826 instructions.\n\n 2827 Finally, execute the last test item to leave LockTask mode. 2828 </string> 2829 <string name="start_lock_task_button_label">Start LockTask mode</string> 2830 <string name="device_owner_lock_task_ui_default_test">Default LockTask UI</string> 2831 <string name="device_owner_lock_task_ui_default_test_info"> 2832 Press the button below to reset to default LockTask UI. 2833 Observe the following UI restrictions. Mark the test as \'pass\' only if ALL of the 2834 requirements below are met.\n\n 2835 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 2836 battery status, clock, etc.\n 2837 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 2838 for the status bar.\n 2839 3) The Home button is hidden.\n 2840 4) The Overview button is hidden and the Overview gesture (swipe-up) does not work.\n 2841 5) Long-press the power button. The power button menu, which usually shows the power-off 2842 button, etc., isn\'t shown.\n 2843 6) Press the power button to turn off the screen, and press it again to turn the screen 2844 back on. Lock screen shouldn\'t be shown.\n 2845 7) The assist gesture isn\'t available. 2846 </string> 2847 <string name="device_owner_lock_task_ui_system_info_test">Enable system info</string> 2848 <string name="device_owner_lock_task_ui_system_info_test_info"> 2849 Press the button below to enable system info. Observe the system info area of the status 2850 bar is now enabled. This includes the clock, connectivity info, battery info, etc.\n\n 2851 The rest of the UI restrictions should still apply:\n 2852 1) Notification icons are still hidden on the status bar.\n 2853 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 2854 for the status bar.\n 2855 3) The Home button is hidden.\n 2856 4) The Overview button is hidden and the Overview gesture (swipe-up) does not work.\n 2857 5) Long-press the power button. The power button menu, which usually shows the power-off 2858 button, etc., isn\'t shown.\n 2859 6) Press the power button to turn off the screen, and press it again to turn the screen 2860 back on. Lock screen shouldn\'t be shown.\n 2861 7) The assist gesture isn\'t available.\n\n 2862 Mark the test as \'pass\' only if ALL of the above requirements are met. 2863 </string> 2864 <string name="device_owner_lock_task_ui_notifications_test">Enable notifications</string> 2865 <string name="device_owner_lock_task_ui_notifications_test_info"> 2866 Press the button below to enable notifications. Observe the notification icons on the 2867 status bar are now enabled and the Home button is shown. The status bar can also be 2868 expanded to show the notifications. However, all Settings UI should remain invisible, 2869 including Quick Settings and any link to the Settings app.\n\n 2870 The rest of the UI restrictions should still apply:\n 2871 1) System info area is still hidden on the status bar.\n 2872 2) The Overview button is hidden and the Overview gesture (swipe-up) does not work.\n 2873 3) Holding the Home button and swiping to the right does not bring up other tasks.\n 2874 4) Long-press the power button. The power button menu, which usually shows the power-off 2875 button, etc., isn\'t shown.\n 2876 5) Press the power button to turn off the screen, and press it again to turn the screen 2877 back on. Lock screen shouldn\'t be shown.\n 2878 6) The assist gesture isn\'t available.\n\n 2879 Mark the test as \'pass\' only if ALL of the above requirements are met. 2880 </string> 2881 <string name="device_owner_lock_task_ui_home_test">Enable Home button</string> 2882 <string name="device_owner_lock_task_ui_home_test_info"> 2883 Press the button below to enable the Home button. Observe the Home button is now 2884 enabled.\n\n 2885 The rest of the UI restrictions should still apply:\n 2886 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 2887 battery status, clock, etc.\n 2888 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 2889 for the status bar.\n 2890 3) The Overview button is hidden and the Overview gesture (swipe-up) does not work.\n 2891 4) Holding the Home button and swiping to the right does not bring up other tasks.\n 2892 5) Long-press the power button. The power button menu, which usually shows the power-off 2893 button, etc., isn\'t shown.\n 2894 6) Press the power button to turn off the screen, and press it again to turn the screen 2895 back on. Lock screen shouldn\'t be shown.\n 2896 7) The assist gesture isn\'t available.\n\n 2897 Mark the test as \'pass\' only if ALL of the above requirements are met. 2898 </string> 2899 <string name="device_owner_lock_task_ui_recents_test">Enable Overview button</string> 2900 <string name="device_owner_lock_task_ui_recents_test_info"> 2901 Press the button below to enable the Overview button. Observe the Home button is now 2902 enabled. Press the Overview button or perform the Overview gesture 2903 (swipe up) and verify the Overview view can be opened.\n\n 2904 The rest of the UI restrictions should still apply:\n 2905 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 2906 battery status, clock, etc.\n 2907 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 2908 for the status bar.\n 2909 3) Long-press the power button. The power button menu, which usually shows the power-off 2910 button, etc., isn\'t shown.\n 2911 4) Press the power button to turn off the screen, and press it again to turn the screen 2912 back on. Lock screen shouldn\'t be shown.\n 2913 5) The assist gesture isn\'t available.\n\n 2914 Mark the test as \'pass\' only if ALL of the above requirements are met. 2915 </string> 2916 <string name="device_owner_lock_task_ui_global_actions_test">Enable global actions</string> 2917 <string name="device_owner_lock_task_ui_global_actions_test_info"> 2918 Press the button below to enable global actions (a.k.a. power button menu). Long-press 2919 the power button and verify a menu containing power-off and restart buttons is shown. 2920 This menu can\'t contain any UI that allows the user to change system settings (such as 2921 airplane mode switch) or access the Settings app.\n\n 2922 The rest of the UI restrictions should still apply:\n 2923 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 2924 battery status, clock, etc.\n 2925 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 2926 for the status bar.\n 2927 3) The Home button is hidden.\n 2928 4) The Overview button is hidden and the Overview gesture (swipe-up) does not work.\n 2929 5) Press the power button to turn off the screen, and press it again to turn the screen 2930 back on. Lock screen shouldn\'t be shown.\n 2931 6) The assist gesture isn\'t available.\n\n 2932 Mark the test as \'pass\' only if ALL of the above requirements are met. 2933 </string> 2934 <string name="device_owner_lock_task_ui_keyguard_test">Enable keyguard</string> 2935 <string name="device_owner_lock_task_ui_keyguard_test_info"> 2936 Press the button below to enable keyguard. Press the power button to turn off the screen 2937 and press it again to turn the screen back on. Verify that the lock screen is shown.\n\n 2938 The rest of the UI restrictions should still apply, both on the lock screen and after 2939 the lock screen is dismissed:\n 2940 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 2941 battery status, clock, etc.\n 2942 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 2943 for the status bar, even on the lock screen.\n 2944 3) The Home button is hidden.\n 2945 4) The Overview button is hidden and the Overview gesture (swipe-up) does not work.\n 2946 5) Long-press the power button. The power button menu, which usually shows the power-off 2947 button, etc., isn\'t shown.\n 2948 6) The assist gesture isn\'t available.\n\n 2949 Mark the test as \'pass\' only if ALL of the above requirements are met. 2950 </string> 2951 <string name="device_owner_lock_task_ui_stop_lock_task_test">Stop LockTask mode</string> 2952 <string name="device_owner_lock_task_ui_stop_lock_task_test_info"> 2953 Press the button below to exit LockTask mode.\n\n 2954 Observe that the UI has returned to the normal, unrestricted state, and is no longer 2955 subject to any LockTask restriction.\n\n 2956 Mark the test as \'pass\' or \'fail\' accordingly. 2957 </string> 2958 <string name="device_owner_lockscreen_secure">Please remove lockscreen password</string> 2959 <string name="device_profile_owner_permission_lockdown_test">Permissions lockdown</string> 2960 <string name="device_profile_owner_permission_lockdown_test_instructions"> 2961 Select each of the three grant states for the permission shown below in turn.\n 2962 Now open application settings, select Permissions, and verify if the following behavior is observed.\n 2963 <b>Grant:</b> Permission is granted to the app and cannot be changed through the settings UI. Trying to change it triggers a support message.\n 2964 <b>Let user decide:</b> Permission state can be changed through the settings UI.\n 2965 <b>Deny:</b> Permission is denied to the app and cannot be changed through the settings UI. Trying to change it triggers a support message.\n 2966 Please mark the test accordingly. 2967 </string> 2968 <string name="device_owner_permission_lockdown_test_info"> 2969 This test checks if the permissions state in settings UI is locked down according to the state set by the device owner. 2970 </string> 2971 <string name="device_owner_disallow_usb_file_transfer_test">Disallow USB file transfer</string> 2972 <string name="device_owner_disallow_usb_file_transfer_test_info"> 2973 Please press below button to set the \"disallow USB file transfer\" restriction.\n 2974 If a USB notification appears, open the notification and check that the 2975 \"Transfer files (MTP)\" and \"Transfer photos (PTP)\" cannot be selected and trigger a 2976 support message when trying to select them.\n 2977 Check if you can mount the device as a USB drive on your desktop computer. The test is 2978 successful if you cannot mount the device, and files from your phone cannot be 2979 downloaded through USB.\n 2980 Please mark the test accordingly. 2981 </string> 2982 <string name="device_owner_set_user_icon">Setting the user icon</string> 2983 <string name="device_owner_set_user_icon_instruction"> 2984 This test verifies that the user icon can be set.\n 2985 1. Press the set user icon button.\n 2986 2. Press the go button to go to Settings.\n 2987 3a. If there is a \"users\" section in Settings, check that the icon of the user \"owner\" is the CtsVerifier one and mark this test accordingly.\n 2988 3b. If there is no \"users\" section, mark this test as passed.\n 2989 </string> 2990 <string name="device_owner_set_user_icon_button">Set user icon</string> 2991 2992 <string name="profile_owner_permission_lockdown_test_info"> 2993 <b> 2994 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 2995 </b> 2996 This test checks if the permissions state in settings UI is locked down correctly depending on the state set by the profile owner. 2997 </string> 2998 <string name="package_not_found">You must install %s (aka CtsPermissionApp).</string> 2999 <string name="permission_allow">Grant</string> 3000 <string name="permission_default">Let user decide</string> 3001 <string name="permission_deny">Deny</string> 3002 <string name="not_profile_owner">%s is not profile owner.</string> 3003 <string name="not_device_owner">%s is not device owner.</string> 3004 <string name="activity_not_found">No activity found to handle intent: %s</string> 3005 <string name="open_settings_button_label">Open Application Settings</string> 3006 <string name="finish_button_label">Finish</string> 3007 <string name="device_owner_device_admin_visible">Device administrator settings</string> 3008 <string name="device_owner_device_admin_visible_info"> 3009 Please press the Go button to open the Security page in Settings. 3010 Navigate to Device administrators and confirm that:\n 3011 \n 3012 - \"CTS Verifier\" exists and is activated.\n 3013 - \"CTS Verifier\" cannot be disabled.\n 3014 \n 3015 Use the Back button to return to this page. 3016 </string> 3017 <string name="device_owner_disallow_config_bt">Disallow configuring Bluetooth</string> 3018 <string name="device_owner_disallow_config_bt_info"> 3019 Please press the Set restriction button to set the user restriction. 3020 Then press Go to open the Bluetooth page in Settings. 3021 Confirm that:\n 3022 \n 3023 - You cannot view Bluetooth devices in range.\n 3024 - Trying to edit, add or remove any already paired devices triggers a support message.\n 3025 \n 3026 Use the Back button to return to this page. 3027 </string> 3028 <string name="device_owner_disallow_config_wifi">Disallow configuring WiFi</string> 3029 <string name="device_owner_disallow_config_wifi_info"> 3030 Please press the Set restriction button to set the user restriction. 3031 Then press Go to open the WiFi page in Settings. 3032 Confirm that:\n\n 3033 - You cannot view WiFi networks in range.\n 3034 - Trying to edit, add or remove any existing WiFi configs triggers a support message.\n 3035 \n 3036 Use the Back button to return to this page. 3037 </string> 3038 <string name="device_owner_disallow_data_roaming">Disallow data roaming</string> 3039 <string name="device_owner_disallow_data_roaming_info"> 3040 Device should have a sim card to perform this test. 3041 Please press the Set restriction button to set the user restriction. 3042 Then press Go to open the Mobile network page in Settings. 3043 Confirm that:\n\n 3044 - Data roaming is disabled.\n 3045 - Enabling data roaming is not possible and triggers a support message.\n\n 3046 Use the Back button to return to this page. 3047 </string> 3048 <string name="device_owner_disallow_factory_reset">Disallow factory reset</string> 3049 <string name="device_owner_disallow_factory_reset_info"> 3050 Please press the Set button to set the user restriction.\n 3051 1. Go to the factory reset settings. It is often located in \"Backup & reset\" settings.\n 3052 Confirm that:\n 3053 - Factory data reset is disabled.\n 3054 - Pressing factory data reset is not possible and triggers a support message.\n\n 3055 2. Go to OEM unlocking settings, if this device has this Settings option. It is often located under \"Developer options\".\n 3056 Confirm that:\n 3057 - Oem Unlocking is disabled.\n 3058 - Enabling Oem unlocking is not possible and triggers a support message.\n\n 3059 Return back to this page. 3060 </string> 3061 <string name="device_owner_user_restriction_set">Set restriction</string> 3062 <string name="device_owner_settings_go">Go</string> 3063 3064 <string name="device_owner_vpn_connection"> 3065 VPN connection has been established.\n 3066 This is not as expected.\n 3067 Mark this test as failed.\n 3068 </string> 3069 <string name="device_owner_vpn_connection_close_failed"> 3070 Established vpn connection cannot be closed.\n 3071 This is not as expected.\n 3072 Mark this test as failed.\n 3073 </string> 3074 <string name="device_owner_no_vpn_connection"> 3075 Cannot establish a VPN connection.\n 3076 This was expected.\n 3077 Mark this test as passed.\n 3078 </string> 3079 <string name="device_owner_vpn_test">Check VPN</string> 3080 <string name="device_owner_vpn_info_default">VPN test message</string> 3081 3082 <string name="device_owner_disallow_config_vpn">Disallow configuring VPN</string> 3083 <string name="device_owner_disallow_config_vpn_info"> 3084 Please press the Set VPN restriction button to set the VPN restriction. 3085 Perform tests in order. Mark test as passed if both test cases pass\n\n 3086 1. Press Go to attempt to open the VPN settings page.\n 3087 You should either see (a) the VPN settings page or (b) that the Intent 3088 android.settings.VPN_SETTINGS fails to resolve.\n 3089 In the case of (a), confirm that:\n 3090 - Trying to perform any of the above actions will trigger a support message.\n 3091 In the case of (b) this step is successful.\n\n 3092 2. Press Check VPN to check programmatic Vpn test.\n 3093 - Check Vpn setup is not allowed\n 3094 - If prompted to allow a VPN connection, press OK.\n\n 3095 Use the Back button to return to this page. 3096 </string> 3097 <string name="device_owner_user_vpn_restriction_set">Set VPN restriction</string> 3098 3099 <!-- Strings for DeviceOwnerBugreportTest --> 3100 <string name="device_owner_requesting_bugreport_tests">Device Owner Requesting Bugreport Tests</string> 3101 <string name="device_owner_requesting_bugreport_category">Device Owner Requesting Bugreport Tests</string> 3102 <string name="device_owner_requesting_bugreport_tests_info"> 3103 The device owner requesting bugreport tests verify that a bugreport can be requested on a corporate owned device.\n 3104 Press below button first, follow steps described in the dialog that pops up, 3105 then proceed to the test cases.\n 3106 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 3107 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 3108 be run last so that it does not interfere with other tests. 3109 </string> 3110 <string name="device_owner_request_bugreport">Request bugreport</string> 3111 <string name="bugreport_sharing_declined">Bugreport sharing declined</string> 3112 <string name="bugreport_shared_successfully">Bugreport shared successfully</string> 3113 <string name="bugreport_already_in_progress">Bugreport is already being collected on this device</string> 3114 <string name="bugreport_failed_completing">Bugreport collection operation failed</string> 3115 <string name="device_owner_bugreport_sharing_declined_while_being_taken">Sharing of requested bugreport declined while being taken</string> 3116 <string name="device_owner_bugreport_sharing_declined_while_being_taken_info"> 3117 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 3118 Open the notifications panel and verify that:\n 3119 \n 3120 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 3121 \n 3122 Press the \"Request bugreport\" button again to try to invoke a second bugreport sharing operation. 3123 Open the notifications panel and verify that:\n 3124 \n 3125 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport is already being collected on this device\" is present. Dismiss that notification.\n 3126 - Tapping on the \"Taking bugreport...\" notification opens a dialog titled \"Share bug report?\", that contains a message \"Your IT admin requested a bug report to help troubleshoot this device. Apps and data may be shared, and your device may temporarily slow down.\" and two buttons - \"DECLINE\" and \"SHARE\".\n 3127 \n 3128 Tap the \"DECLINE\" button and verify that:\n 3129 \n 3130 - \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n 3131 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport sharing declined\" is present.\n 3132 \n 3133 Dismiss the notifications and mark test as passed or failed. 3134 </string> 3135 <string name="device_owner_bugreport_sharing_accepted_while_being_taken">Sharing of requested bugreport accepted while being taken</string> 3136 <string name="device_owner_bugreport_sharing_accepted_while_being_taken_info"> 3137 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 3138 Open the notifications panel and verify that:\n 3139 \n 3140 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 3141 - Tapping on the \"Taking bugreport...\" notification opens a dialog titled \"Share bug report?\", that contains a message \"Your IT admin requested a bug report to help troubleshoot this device. Apps and data may be shared, and your device may temporarily slow down.\" and two buttons - \"DECLINE\" and \"SHARE\".\n 3142 \n 3143 Tap the \"SHARE\" button and verify that:\n 3144 \n 3145 - \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n 3146 - Notification titled \"Sharing bugreport...\" with an indefinite progress bar is present.\n 3147 - After a few minutes (time necessary to wait for bugreport being collected) notification titled \"Sharing bugreport...\" is automatically dismissed and notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport shared successfully\" is present.\n 3148 \n 3149 Dismiss the notifications and mark test as passed or failed. 3150 </string> 3151 <string name="device_owner_bugreport_sharing_declined_after_having_been_taken">Sharing of requested bugreport declined after having been taken</string> 3152 <string name="device_owner_bugreport_sharing_declined_after_having_been_taken_info"> 3153 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 3154 Open the notifications panel and verify that:\n 3155 \n 3156 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 3157 \n 3158 Wait for a few minutes (time necessary for bugreport to be collected) and verify that:\n 3159 \n 3160 - \"Taking bugreport...\" notification with an indefinite progress bar is dismissed.\n 3161 - Notification titled \"Share bug report?\", that contains a message \"Your IT admin requested a bug report to help troubleshoot this device. Apps and data may be shared.\" and two buttons - \"DECLINE\" and \"SHARE\" is shown.\n 3162 \n 3163 Tap the \"DECLINE\" button and verify that:\n 3164 \n 3165 - Notification titled \"Share bug report?\" is dismissed.\n 3166 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport sharing declined\" is present.\n 3167 \n 3168 Dismiss the notifications and mark test as passed or failed. 3169 </string> 3170 <string name="device_owner_bugreport_sharing_accepted_after_having_been_taken">Sharing of requested bugreport accepted after having been taken</string> 3171 <string name="device_owner_bugreport_sharing_accepted_after_having_been_taken_info"> 3172 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 3173 Open the notifications panel and verify that:\n 3174 \n 3175 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 3176 \n 3177 Wait for a few minutes (time necessary for bugreport to be collected) and verify that:\n 3178 \n 3179 - \"Taking bugreport...\" notification with an indefinite progress bar is dismissed.\n 3180 - Notification titled \"Share bug report?\", that contains a message \"Your IT admin requested a bug report to help troubleshoot this device. Apps and data may be shared.\" and two buttons - \"DECLINE\" and \"SHARE\" is shown.\n 3181 \n 3182 Tap the \"SHARE\" button and verify that:\n 3183 \n 3184 - Notification titled \"Share bug report?\" is dismissed.\n 3185 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport shared successfully\" is present.\n 3186 \n 3187 Dismiss the notifications and mark test as passed or failed. 3188 </string> 3189 3190 <!-- Strings used for policy transparency test --> 3191 <string name="device_profile_owner_policy_transparency_test">Policy transparency test</string> 3192 <string name="device_profile_owner_policy_transparency_test_info"> 3193 This test checks that if an admin has enforced a policy, we let the user know about this.\nSet the short and long support messages before proceeding with the tests. 3194 </string> 3195 <string name="policy_transparency_open_settings_label">Open settings</string> 3196 <string name="policy_transparency_short_support_msg_label">Set short support message</string> 3197 <string name="policy_transparency_long_support_msg_label">Set long support message</string> 3198 <string name="policy_transparency_set_msg">Set message</string> 3199 <string name="policy_transparency_clear_msg">Clear message</string> 3200 <string name="policy_transparency_set_default_msg">Set default message</string> 3201 <string name="policy_transparency_default_short_msg"> 3202 This action is disabled by your administrator. Contact someone (a] example.com for support. 3203 </string> 3204 <string name="policy_transparency_default_long_msg"> 3205 This profile or device is managed by CtsVerifier. You can contact tech 3206 support on:\n\n 3207 America: +1 555-0100\n\n 3208 APAC: +1 555-0100\n\n 3209 Europe: +1 555-0100\n\n 3210 Email: someone (a] example.com 3211 </string> 3212 <string name="policy_transparency_update_button_label">Update</string> 3213 <string name="dummy_input_method_label">Dummy input method</string> 3214 <string name="dummy_accessibility_service_label">Dummy accessibility service</string> 3215 <string name="policy_transparency_test_instructions"> 3216 1. <xliff:g id="set_step" example="Set policy by turning the switch on">%1$s</xliff:g>\n 3217 2. Open Settings app by clicking the "Open settings" button below. (If this device has a separate app for work settings, ignore the button and open that app manually from the launcher, if necessary)\n 3218 3. Verify that performing the following action will trigger a support dialog:\n 3219 <xliff:g id="user_action" example="Adding an account">%2$s</xliff:g>.\n 3220 4. Verify that the support dialog displays the short support message set earlier.\n 3221 5. Verify that clicking the "Learn more" link will redirect to Device administrators 3222 page in Settings app which displays the long support message set earlier.\n 3223 </string> 3224 <string name="user_restriction_set_step"> 3225 Set \'%s\' user restriction by turning on the switch below. 3226 </string> 3227 <string name="disallow_add_user">Disallow add user</string> 3228 <string name="disallow_add_user_action">Adding a new user</string> 3229 <string name="disallow_adjust_volume">Disallow adjust volume</string> 3230 <string name="disallow_adjust_volume_action">Adjusting the volume</string> 3231 <string name="disallow_config_date_time">Disallow config date and time settings</string> 3232 <string name="disallow_config_date_time_action">Configuring auto time, time, auto date or date</string> 3233 <string name="disallow_config_location">Disallow config location</string> 3234 <string name="disallow_config_location_action">Enabling or disabling location in settings or quick settings</string> 3235 <string name="disallow_airplane_mode">Disallow airplane mode</string> 3236 <string name="disallow_airplane_mode_action">Toggling airplane mode switch bar or changing airplane mode state in quick settings</string> 3237 <string name="disallow_config_screen_timeout">Disallow config sleep options settings</string> 3238 <string name="disallow_config_screen_timeout_action">Configuring sleep options in Display or Battery page.</string> 3239 <string name="disallow_config_brightness">Disallow config brightness settings</string> 3240 <string name="disallow_config_brightness_action">Configuring brightness level or adaptive brightness in Display or Battery page, or toggling brightness slider in quick settings</string> 3241 <string name="disallow_ambient_display">Disallow ambient display</string> 3242 <string name="disallow_ambient_display_action">Configuring ambient display in Display or Battery page</string> 3243 <string name="disallow_apps_control">Disallow controlling apps</string> 3244 <string name="disallow_apps_control_action">DISABLE/UNINSTALL/FORCE STOP-ing any app in the managed device/profile other than CtsVerifier</string> 3245 <string name="disallow_config_cell_broadcasts">Disallow config cell broadcasts</string> 3246 <string name="disallow_config_cell_broadcasts_action">Configuring emergency alerts(cell broadcasts)</string> 3247 <string name="disallow_config_credentials">Disallow config credentials</string> 3248 <string name="disallow_config_credentials_action">Configuring user credentials</string> 3249 <string name="disallow_config_mobile_networks">Disallow config mobile networks</string> 3250 <string name="disallow_config_mobile_networks_action">Configuring mobile networks</string> 3251 <string name="disallow_config_tethering">Disallow config tethering</string> 3252 <string name="disallow_config_tethering_action">Configuring tethering and portable hotspots</string> 3253 <string name="disallow_config_wifi">Disallow config Wi-Fi</string> 3254 <string name="disallow_config_wifi_action">Modifying Wi-Fi configuration</string> 3255 <string name="disallow_debugging_features">Disallow debugging features</string> 3256 <string name="disallow_debugging_features_action">Enabling developer options</string> 3257 <string name="disallow_factory_reset">Disallow factory reset</string> 3258 <string name="disallow_factory_reset_action">Factory resetting the device</string> 3259 <string name="disallow_fun">Disallow fun</string> 3260 <string name="disallow_fun_action">Opening android easter egg game by tapping repeatedly on the \'Android version\' option</string> 3261 <string name="disallow_install_unknown_sources">Disallow install unknown sources</string> 3262 <string name="disallow_install_unknown_sources_action">Enabling \'Cts Verifier\' to install apps</string> 3263 <string name="disallow_modify_accounts">Disallow modify accounts</string> 3264 <string name="disallow_modify_accounts_action">Adding an account or removing an account (if you have already added one)</string> 3265 <string name="disallow_network_reset">Disallow network reset</string> 3266 <string name="disallow_network_reset_action">Resetting network settings</string> 3267 <string name="disallow_outgoing_beam">Disallow outgoing beam</string> 3268 <string name="disallow_outgoing_beam_action">Switching on android beam</string> 3269 <string name="disallow_remove_user">Disallow remove user</string> 3270 <string name="disallow_remove_user_action">Removing other users (please create a user and attempt to remove it to verify)</string> 3271 <string name="disallow_remove_managed_profile">Disallow remove managed profile</string> 3272 <string name="disallow_remove_managed_profile_action">Removing the work profile. It shouldn\'t be possible neither from the Accounts screen nor the Device Administrators screen (after selecting the Device Administrator that corresponds to the badged version of \"CTS Verifier\")</string> 3273 <string name="disallow_share_location">Disallow share location</string> 3274 <string name="disallow_share_location_action">Turning on location sharing</string> 3275 <string name="disallow_uninstall_apps">Disallow uninstall apps</string> 3276 <string name="disallow_uninstall_apps_action">Uninstalling applications from the work profile (badged applications) other than CtsVerifier</string> 3277 <string name="disallow_unified_challenge">Disallow unified challenge</string> 3278 <string name="disallow_unified_challenge_action">Setting one lock for both personal and work profiles. IMPORTANT: Separate work lock should be set prior to this test in Set work lock test</string> 3279 <string name="disallow_keyguard_unredacted_notifications">Disallow lockscreen unredacted notification</string> 3280 <string name="disallow_keyguard_unredacted_notifications_set_step">Disallow unredacted notifications when device is locked by turning on the switch below</string> 3281 <string name="disallow_keyguard_unredacted_notifications_action">Selecting show all notification content when device is locked</string> 3282 <string name="disallow_keyguard_unredacted_notifications_widget_label">@string/disallow_keyguard_unredacted_notifications</string> 3283 <string name="set_auto_time_required">Set auto (network) time required</string> 3284 <string name="auto_time_required_set_step">Set auto time required policy by turning on the switch below</string> 3285 <string name="set_auto_time_required_action">Modifying date and time</string> 3286 <string name="set_auto_time_required_widget_label">@string/set_auto_time_required</string> 3287 <string name="set_lock_screen_info">Set lock screen info</string> 3288 <string name="lock_screen_info_set_step">Select a lock screen info by setting a non-empty message in the edittext below.</string> 3289 <string name="set_lock_screen_info_action">Modifying lock screen message</string> 3290 <string name="set_lock_screen_info_widget_label">@string/set_lock_screen_info</string> 3291 <string name="set_maximum_time_to_lock">Set maximum time to lock</string> 3292 <string name="maximum_time_to_lock_set_step"> 3293 Select a non-zero maximum time to lock value by setting a value in the edittext box below. 3294 </string> 3295 <string name="set_maximum_time_to_lock_action">Selecting maximum time to lock greater than the set value below</string> 3296 <string name="set_maximum_time_to_lock_widget_label">Set maximum time to lock (in Sec):</string> 3297 <string name="set_password_quality">Set password quality</string> 3298 <string name="password_quality_set_step">Set minimum password quality by selecting an option in the spinner below.</string> 3299 <string name="set_password_quality_action">Setting a password which does not meet the requirements of the password quality selected</string> 3300 <string name="set_password_quality_widget_label">@string/set_password_quality</string> 3301 <string name="password_quality_unspecified">Unspecified</string> 3302 <string name="password_quality_something">Something</string> 3303 <string name="password_quality_numeric">Numeric</string> 3304 <string name="password_quality_numeric_complex">Numeric (Complex)</string> 3305 <string name="password_quality_alphabetic">Alphabetic</string> 3306 <string name="password_quality_alphanumeric">Alphanumeric</string> 3307 <string name="password_quality_complex">Complex</string> 3308 <string name="set_permitted_accessibility_services">Set permitted accessibility services</string> 3309 <string name="permitted_accessibility_services_set_step"> 3310 Check that \'Dummy Accessibility service\' is not enabled in Settings and disallow \'Dummy Accessibility service\' from permitted accessibility services by turning on 3311 the switch below. 3312 </string> 3313 <string name="set_permitted_accessibility_services_action"> 3314 Enabling \'Dummy Accessibility service\' in the list of accessibility services 3315 </string> 3316 <string name="set_permitted_accessibility_services_widget_label"> 3317 Allow only system accessibility services: 3318 </string> 3319 <string name="set_permitted_input_methods">Set permitted input methods</string> 3320 <string name="permitted_input_methods_set_step"> 3321 Check that \'Dummy Input method\', along with all other non-system apps, are not enabled in Settings. Then disallow \'Dummy Input method\' from permitted input methods by turning on the switch below. 3322 </string> 3323 <string name="set_permitted_input_methods_action"> 3324 Enabling \'Dummy Input method\' in the list of input methods 3325 </string> 3326 <string name="set_permitted_input_methods_widget_label"> 3327 Allow only system input methods: 3328 </string> 3329 3330 <!-- Strings used for enterprise privacy tests --> 3331 <string name="enterprise_privacy_test">Managed device info tests</string> 3332 <string name="enterprise_privacy_page">Managed device info page</string> 3333 <string name="enterprise_privacy_page_info"> 3334 Please press the Go button to open Settings. Verify that:\n 3335 1) One of the Settings screens contains an entry for managed device information.\n 3336 2) Tapping that entry opens a screen.\n 3337 3) In this screen, at a minimum, you are told your organization can:\n 3338 * Change settings on this device.\n 3339 * See data associated with your work account.\n 3340 * See the list of all apps on your device.\n 3341 * See usage of each app on your device.\n 3342 * Lock the device and change the password.\n 3343 * Wipe the device.\n 3344 \n 3345 Use the Back button to return to this page. 3346 </string> 3347 <string name="enterprise_privacy_open_settings">Open Settings</string> 3348 <string name="enterprise_privacy_network_logging">Retrieve traffic logs</string> 3349 <string name="enterprise_privacy_network_logging_info"> 3350 Please do the following:\n 3351 1) Press the Retrieve Traffic Logs button and record the time at which you did this.\n 3352 2) Wait one minute.\n 3353 3) Press the Open Settings button.\n 3354 4) In the screen that opens, verify that you are told traffic logs were last retrieved at the time you pressed the Retrieve Traffic Logs button in step (1).\n 3355 \n 3356 Use the Back button to return to this page. 3357 </string> 3358 <string name="enterprise_privacy_retrieve_network_logs">Retrieve Traffic Logs</string> 3359 <string name="enterprise_privacy_bug_report">Request bug report</string> 3360 <string name="enterprise_privacy_bug_report_info"> 3361 Please do the following:\n 3362 1) Press the Request Bug Report button and record the time at which you did this.\n 3363 2) Wait one minute.\n 3364 3) Press the Open Settings button.\n 3365 4) In the screen that opens, verify that you are told a bug report was last requested at the time you pressed the Request Bug Report button in step (1).\n 3366 \n 3367 Use the Back button to return to this page. 3368 </string> 3369 <string name="enterprise_privacy_request_bug_report">Request Bug Report</string> 3370 <string name="enterprise_privacy_security_logging">Retrieve security logs</string> 3371 <string name="enterprise_privacy_security_logging_info"> 3372 Please do the following:\n 3373 1) Press the Retrieve Security Logs button and record the time at which you did this.\n 3374 2) Wait one minute.\n 3375 3) Press the Open Settings button.\n 3376 4) In the screen that opens, verify that you are told security logs were last retrieved at the time you pressed the Retrieve Security Logs button in step (1).\n 3377 \n 3378 Use the Back button to return to this page. 3379 </string> 3380 <string name="enterprise_privacy_retrieve_security_logs">Retrieve Security Logs</string> 3381 <string name="enterprise_privacy_clear_organization">Clear Org</string> 3382 <string name="enterprise_privacy_set_organization">Set Org</string> 3383 <string name="enterprise_privacy_enterprise_installed_apps">Enterprise-installed apps</string> 3384 <string name="enterprise_privacy_enterprise_installed_apps_info"> 3385 Please do the following:\n 3386 1) You should have received NotificationBot.apk together with the CTS verifier. If you built the CTS verifier yourself, build the NotificationBot.apk by issuing the following command on the host:\n 3387 make NotificationBot\n 3388 2) Upload the NotificationBot.apk to your device by issuing the following command on the host:\n 3389 adb push /path/to/NotificationBot.apk /sdcard\n 3390 3) Press the Uninstall button.\n 3391 4) Press the Open Settings button.\n 3392 5) In the screen that opens, verify that you are not told that your administrator installed any apps.\n 3393 6) Use the Back button to return to this page.\n 3394 7) Press the Install button.\n 3395 8) Press the Open Settings button.\n 3396 9) In the screen that opens, verify that you are told now that your administrator installed at least one app.\n 3397 10) Tap on that information. Verify that a list of apps installed shows.\n 3398 11) Verify that the list contains the CTS Robot app.\n 3399 12) Use the Back button to return to this page.\n 3400 13) Press the Uninstall button.\n 3401 14) Issue the following command on the host:\n 3402 adb shell rm /sdcard/NotificationBot.apk 3403 </string> 3404 <string name="enterprise_privacy_install">Install</string> 3405 <string name="enterprise_privacy_uninstall">Uninstall</string> 3406 <string name="enterprise_privacy_admin_granted_location_access">Location access permission</string> 3407 <string name="enterprise_privacy_admin_granted_location_access_info"> 3408 Please do the following:\n 3409 1) Press the Reset button.\n 3410 2) Press the Open Settings button.\n 3411 3) In the screen that opens, verify that you are not told that your administrator has granted location access to any apps.\n 3412 4) Use the Back button to return to this page.\n 3413 5) Press the Grant button.\n 3414 6) Press the Open Settings button.\n 3415 7) In the screen that opens, verify that you are told now that your administrator has granted location access to at least one app.\n 3416 8) Tap on that information. Verify that a list of apps which have location access shows.\n 3417 9) Verify that the list contains the CTS Verifier app.\n 3418 10) Use the Back button to return to this page.\n 3419 11) Press the Reset button. 3420 </string> 3421 <string name="enterprise_privacy_reset">Reset</string> 3422 <string name="enterprise_privacy_grant">Grant</string> 3423 <string name="enterprise_privacy_admin_granted_microphone_access">Microphone access permission</string> 3424 <string name="enterprise_privacy_admin_granted_microphone_access_info"> 3425 Please do the following:\n 3426 1) Press the Reset button.\n 3427 2) Press the Open Settings button.\n 3428 3) In the screen that opens, verify that you are not told that your administrator has granted microphone access to any apps.\n 3429 4) Use the Back button to return to this page.\n 3430 5) Press the Grant button.\n 3431 6) Press the Open Settings button.\n 3432 7) In the screen that opens, verify that you are told now that your administrator has granted microphone access to at least one app.\n 3433 8) Tap on that information. Verify that a list of apps that have microphone access shows.\n 3434 9) Verify that the list contains the CTS Verifier app.\n 3435 10) Use the Back button to return to this page.\n 3436 11) Press the Reset button. 3437 </string> 3438 <string name="enterprise_privacy_admin_granted_camera_access">Camera access permission</string> 3439 <string name="enterprise_privacy_admin_granted_camera_access_info"> 3440 Please do the following:\n 3441 1) Press the Reset button.\n 3442 2) Press the Open Settings button.\n 3443 3) In the screen that opens, verify that you are not told that your administrator has granted camera access to any apps.\n 3444 4) Use the Back button to return to this page.\n 3445 5) Press the Grant button.\n 3446 6) Press the Open Settings button.\n 3447 7) In the screen that opens, verify that you are told now that your administrator has granted camera access to at least one app.\n 3448 8) Tap on that information. Verify that a list of apps that have camera access shows.\n 3449 9) Verify that the list contains the CTS Verifier app.\n 3450 10) Use the Back button to return to this page.\n 3451 11) Press the Reset button. 3452 </string> 3453 <string name="enterprise_privacy_default_apps">Default apps</string> 3454 <string name="enterprise_privacy_default_apps_info"> 3455 Please do the following:\n 3456 1) When a default browser is set, you must clear it by step (2), (3) and (4).\n 3457 2) Confirm default browser by "Settings > Apps & notifications > Default apps > Browser app".\n 3458 3) Tap default browser app in the "Settings > Apps & notifications > App info".\n 3459 4) Tap "Open by default" and Tap "CLEAR DEFAULTS"\n 3460 5) Press the Reset button.\n 3461 6) Press the Open Settings button.\n 3462 7) In the screen that opens, verify that you are not told that your administrator set any default apps.\n 3463 8) Use the Back button to return to this page.\n 3464 9) Press the Set Default Apps button.\n 3465 10) Press the Open Settings button.\n 3466 11) In the screen that opens, verify that you are now told that your administrator has set 7 default apps.\n 3467 12) Tap on that information. Verify that a list of default apps shows, with 7 elements in it.\n 3468 13) Verify that each element shows the CTS Verifier is the default app.\n 3469 14) Use the Back button to return to this page.\n 3470 15) Press the Reset button. 3471 </string> 3472 <string name="enterprise_privacy_set_default_apps">Set Default Apps</string> 3473 <string name="enterprise_privacy_default_ime">Default keyboard</string> 3474 <string name="enterprise_privacy_default_ime_info"> 3475 Please do the following:\n 3476 1) Press the Open Settings button.\n 3477 2) In the screen that opens, verify that you are not told the default keyboard has been set.\n 3478 3) Use the Back button to return to this page.\n 3479 4) Press the Set Keyboard button to set the default keyboard.\n 3480 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that the default keyboard has been set to CTS Verifier.\n 3481 6) Press the Finish button to clear the default keyboard. 3482 </string> 3483 <string name="enterprise_privacy_set_keyboard">Set Keyboard</string> 3484 <string name="enterprise_privacy_finish">Finish</string> 3485 <string name="enterprise_privacy_always_on_vpn">Always-on VPN</string> 3486 <string name="enterprise_privacy_always_on_vpn_info"> 3487 Please do the following:\n 3488 1) Press the Open Settings button.\n 3489 2) In the screen that opens, verify that you are not told that an always-on VPN is set.\n 3490 3) Use the Back button to return to this page.\n 3491 4) Press the Set VPN button to set an always-on VPN.\n 3492 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that an always-on VPN is set.\n 3493 6) Press the Finish button to clear the always-on VPN. 3494 </string> 3495 <string name="enterprise_privacy_set_always_on_vpn">Set VPN</string> 3496 <string name="enterprise_privacy_comp_always_on_vpn">Always-on VPN (managed profile)</string> 3497 <string name="enterprise_privacy_comp_always_on_vpn_info"> 3498 Please do the following:\n 3499 1) Press the Start button to create a work profile.\n 3500 2) Press the Open Settings button.\n 3501 3) In the screen that opens, verify that you are not told that an always-on VPN is set.\n 3502 4) Use the Back button to return to this page.\n 3503 5) Press the Set VPN button to set an always-on VPN in your work profile.\n 3504 6) Repeat steps (2) through (4), verifying that in step (3), you are told now that an always-on VPN is set in your work profile.\n 3505 7) Press the Finish button to remove the work profile and always-on VPN. 3506 </string> 3507 <string name="enterprise_privacy_start">Start</string> 3508 <string name="enterprise_privacy_global_http_proxy">Global HTTP Proxy</string> 3509 <string name="enterprise_privacy_global_http_proxy_info"> 3510 Please do the following:\n 3511 1) Press the Open Settings button.\n 3512 2) In the screen that opens, verify that you are not told that a global HTTP proxy has been set.\n 3513 3) Use the Back button to return to this page.\n 3514 4) Press the Set Proxy button.\n 3515 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that a global HTTP proxy has been set.\n 3516 6) Press the Clear Proxy button. 3517 </string> 3518 <string name="enterprise_privacy_ca_certs">Trusted CA certs</string> 3519 <string name="enterprise_privacy_ca_certs_info"> 3520 Please do the following:\n 3521 1) Press the Open Settings button.\n 3522 2) In the screen that opens, verify that you are not told that your administrator installed trusted CA certs.\n 3523 3) Use the Back button to return to this page.\n 3524 4) Press the Install Cert button to install a trusted CA cert.\n 3525 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that the administrator has installed at least one trusted CA cert.\n 3526 6) Press the Finish button to clear the cert. 3527 </string> 3528 <string name="enterprise_privacy_install_cert">Install Cert</string> 3529 <string name="enterprise_privacy_comp_ca_certs">Trusted CA certs (managed profile)</string> 3530 <string name="enterprise_privacy_comp_ca_certs_info"> 3531 Please do the following:\n 3532 1) Press the Start button to create a work profile.\n 3533 2) Press the Settings button.\n 3534 3) In the screen that opens, verify that you are not told that your administrator installed trusted CA certs.\n 3535 4) Use the Back button to return to this page.\n 3536 5) Press the Install Cert button to install a trusted CA cert in your work profile.\n 3537 6) Repeat steps (2) through (4), verifying that in step (3), you are told now that the administrator has installed at least one trusted CA cert in your work profile.\n 3538 7) Press the Finish button to remove the work profile and cert. 3539 </string> 3540 <string name="enterprise_privacy_settings">Settings</string> 3541 <string name="enterprise_privacy_set_proxy">Set Proxy</string> 3542 <string name="enterprise_privacy_clear_proxy">Clear Proxy</string> 3543 <string name="enterprise_privacy_failed_password_wipe">Wipe on authentication failure</string> 3544 <string name="enterprise_privacy_failed_password_wipe_info"> 3545 Please do the following:\n 3546 1) Press the Open Settings button.\n 3547 2) In the screen that opens, verify that you are not told all device data will be deleted if you mistype your password too many times.\n 3548 3) Use the Back button to return to this page.\n 3549 4) Press the Set Limit button to set the maximum number of password attempts.\n 3550 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that all device data will be deleted if you mistype your password 100 times.\n 3551 6) Press the Finish button to clear the maximum number of password attempts. 3552 </string> 3553 <string name="enterprise_privacy_set_limit">Set Limit</string> 3554 <string name="enterprise_privacy_comp_failed_password_wipe">Wipe on authentication failure (managed profile)</string> 3555 <string name="enterprise_privacy_comp_failed_password_wipe_info"> 3556 Please do the following:\n 3557 1) Press the Start button to create a work profile.\n 3558 2) Press the Open Settings button.\n 3559 3) In the screen that opens, verify that you are not told work profile data will be deleted if you mistype your password too many times.\n 3560 4) Use the Back button to return to this page.\n 3561 5) Press the Set Limit button to set the maximum number of password attempts.\n 3562 6) Repeat steps (2) through (4), verifying that in step (3), you are told now that work profile data will be deleted if you mistype your password 100 times.\n 3563 7) Press the Finish button to remove the work profile. 3564 </string> 3565 <string name="enterprise_privacy_quick_settings">Quick settings disclosure</string> 3566 <string name="enterprise_privacy_quick_settings_info"> 3567 Please do the following:\n 3568 1) Press the Clear Org button.\n 3569 2) Open and fully expand Quick Settings.\n 3570 3) Verify that at the bottom of Quick Settings, you are told the device is managed.\n 3571 4) Close Quick Settings.\n 3572 5) Press the Set Org button.\n 3573 6) Open and fully expand Quick Settings.\n 3574 7) Verify that at the bottom of Quick Settings, you are told the device is managed by \"Foo, Inc.\".\n 3575 8) Tap on the information.\n 3576 9) Verify that a dialog informing you about device monitoring opens.\n 3577 10) Tap the \"Learn more\" link.\n 3578 11) Verify that a screen informing you what your managing organization can do is shown.\n 3579 \n 3580 Use the Back button to return to this page. 3581 </string> 3582 <string name="enterprise_privacy_keyguard">Keyguard disclosure</string> 3583 <string name="enterprise_privacy_keyguard_info"> 3584 Please do the following:\n 3585 1) Press the Open Settings button to open Settings.\n 3586 2) Navigate to \"Security\" > \"Screen lock\" and select the first screen lock type that is not \"None\".\n 3587 3) Use the Back button to return to this page.\n 3588 4) Press the Clear Org button.\n 3589 5) Lock the device.\n 3590 6) Verify that on the lock screen, you are told the device is managed.\n 3591 7) Unlock the device.\n 3592 8) Press the Set Org button.\n 3593 9) Lock the device.\n 3594 10) Verify that on the lock screen, you are told the device is managed by \"Foo, Inc.\".\n 3595 11) Unlock the device.\n 3596 12) Repeat steps (1) through (11) for each screen lock type other than \"None\". 3597 </string> 3598 <string name="enterprise_privacy_add_account">Add account disclosure</string> 3599 <string name="enterprise_privacy_add_account_info"> 3600 Please do the following:\n 3601 1) Press the Clear Org button.\n 3602 2) Press the Open Settings button.\n 3603 3) In the screen that opens, verify that you are told that the device is managed.\n 3604 4) Use the Back button to return to this page.\n 3605 5) Press the Set Org button.\n 3606 6) Press the Open Settings button.\n 3607 7) In the screen that opens, verify that you are told that the device is managed by \"Foo, Inc.\".\n 3608 8) Tap the \"Learn more\" link.\n 3609 9) Verify that a screen informing you what your managing organization can do is shown.\n 3610 11) Use the Back button to return to this page. 3611 </string> 3612 <string name="enterprise_privacy_default_app">CTS Verifier Test</string> 3613 3614 <!-- Strings for Network Logging Tests --> 3615 <string name="device_owner_network_logging_ui">Network Logging UI</string> 3616 <string name="device_owner_network_logging_ui_info">Please do the following:\n 3617 1) Open and fully expand Quick Settings.\n 3618 2) Check that you are told that your device is managed.\n 3619 3) Close Quick Settings.\n 3620 4) Enable network logging by tapping on the left button below.\n 3621 5) Open Quick Settings again. Check that an icon appeared next to the text about device management.\n 3622 6) Verify that a notification including the same icon popped up, informing you that network logging has been enabled.\n 3623 7) Tap the notification.\n 3624 8) Verify that a dialog about device monitoring opens, and informs you about: the name of the app that manages this device, details about the device owner\'s capabilities, and information that the admin has activated network logging and can see all network traffic.\n 3625 9) Close the dialog.\n 3626 10) Tap the right button below to disable network logging.\n 3627 11) Verify that the notification disappeared.\n 3628 </string> 3629 <string name="device_owner_enable_network_logging_button">Enable Network Logging</string> 3630 <string name="device_owner_disable_network_logging_button">Disable Network Logging</string> 3631 3632 <string name="comp_test">Corporate Owned Managed Profile</string> 3633 <string name="comp_provision_profile_dialog_title">Provision work profile</string> 3634 <string name="comp_provision_profile_dialog_text">Press the OK button to start the managed provisioning flow, and complete the flow to create a work profile</string> 3635 3636 <string name="managed_user_test">Managed User</string> 3637 <string name="managed_user_positive_tests">Managed User positive tests</string> 3638 <string name="managed_user_positive_tests_instructions"> 3639 The positive managed user tests verify policies on a managed user created by a device owner. 3640 \n 3641 Press Go button to create a managed user, and you will be switched to the managed user 3642 automatically. Dismiss the keyguard and a \'Managed User Tests\' should launch.\n 3643 Follow the test instructions and press \'pass\' or \'fail\' to return to this screen.\n 3644 </string> 3645 <string name="managed_user_positive_tests_info"> 3646 The positive managed user tests verify policies on a managed user created by a device owner. 3647 Proceed to the test cases, then press \'pass\' or \'fail\' to finish this test. 3648 </string> 3649 <string name="managed_user_positive_category">Managed User Tests</string> 3650 <string name="managed_user_check_managed_user_test">Check affiliated profile owner</string> 3651 <string name="managed_user_incorrect_managed_user">Missing or incorrect affiliated profile owner: CTSVerifier is not affilaited PO!</string> 3652 3653 <string name="device_owner_disallow_user_switch">Disallow user switch</string> 3654 <string name="device_owner_disallow_user_switch_info"> 3655 Press \'Create uninitialized user\' to create a user that is not setup. 3656 Then press Set restriction button to set the user restriction. 3657 Then press Go to open the Settings, and manually find and open user settings section. 3658 Confirm that:\n 3659 \n 3660 - Selecting uninitialized user should not trigger user switch.\n 3661 \n 3662 In additional, if quick settings is available, confirm that user switcher is hidden or 3663 disabled. 3664 Use the Back button to return to this page. 3665 </string> 3666 <string name="device_owner_disallow_user_switch_create_user">Create uninitialized user</string> 3667 3668 <string name="device_owner_user_switcher_message">User switcher message</string> 3669 <string name="device_owner_user_switcher_message_info"> 3670 1. Please press the \'With user switcher message\' button to set the user switcher message. 3671 You will then be automatically switched to a secondary user. If a user switcher dialog shows 3672 up, it should read \'Start user session\'. Wait until you are automatically switched back to 3673 primary, if a user switcher dialog shows up, it should read \'End user session\'. 3674 3675 \n 3676 2. Please press the \'Without user switcher message\' button to clear the user switcher 3677 message. You will then be automatically switched to a secondary user. If a user switcher 3678 dialog shows up, it should read \'Switching to managed user\'. Wait until you are 3679 automatically switched back to primary, if a user switcher dialog shows up, it should read 3680 \'Switching to (name of primary user)\'. 3681 </string> 3682 <string name="device_owner_with_user_switcher_message">With user switcher message</string> 3683 <string name="device_owner_without_user_switcher_message">Without user switcher message</string> 3684 3685 <string name="device_owner_enable_logout">Logout</string> 3686 <string name="device_owner_enable_logout_info"> 3687 Please press the Go button to enable logout. You will then be switched to a newly created 3688 user. 3689 Look for a way to logout the current user without unlocking the lock screen. The control is 3690 usually named \'End session\'.\n 3691 The location may vary depending on manufacturer, typical locations are:\n 3692 - In power button menu by long pressing power button.\n 3693 - On the lock screen.\n 3694 \n 3695 When successfully logout and switched back to primary user, confirm that the logout control 3696 is not available in primary user. 3697 </string> 3698 3699 <!-- Strings for JobScheduler Tests --> 3700 <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> 3701 3702 <string name="js_idle_test">Idle Mode Constraints</string> 3703 <string name="js_start_test_text">Start test</string> 3704 <string name="js_idle_instructions">Verify the behavior of the JobScheduler API for when the device is in idle mode. Simply follow the on-screen instructions.</string> 3705 <string name="js_idle_description_1">Turn the screen off and then back on in order to begin.</string> 3706 <string name="js_idle_continue_instruction"> 3707 Switch off screen and wait for it to turn on to continue. 3708 </string> 3709 <string name="js_idle_item_idle_off">Idle job does not execute when device is not idle.</string> 3710 <string name="js_idle_item_idle_on">Idle job does execute when device is forced into idle.</string> 3711 3712 <string name="js_charging_test">Charging Constraints</string> 3713 <string name="js_charging_instructions">Verify the behavior of the JobScheduler API for when the device is on power and unplugged from power. Simply follow the on-screen instructions.</string> 3714 <string name="js_charging_description_1">Plug in the charger if it isn\'t already plugged in.</string> 3715 <string name="js_charging_off_test">Device not charging will not execute a job with a charging constraint.</string> 3716 <string name="js_charging_on_test">Device when charging will execute a job with a charging constraint.</string> 3717 <string name="js_charging_description_2">After the above test has passed, remove the charger to continue. If the above failed, you can simply fail this test.</string> 3718 <string name="js_charging_description_3">Device is plugged in. Please wait while it gets into stable charging state.</string> 3719 <string name="js_charging_description_4">There seems to be a problem with your charger. Please try again.</string> 3720 3721 <string name="js_connectivity_test">Connectivity Constraints</string> 3722 <string name="js_connectivity_instructions">Verify the behavior of the JobScheduler API for when the device has no access to data connectivity. Simply follow the on-screen instructions.</string> 3723 <string name="js_connectivity_description_1">Disable WiFi and Mobile data to begin.</string> 3724 <string name="js_unmetered_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 3725 <string name="js_any_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 3726 <string name="js_no_connectivity_test">Device with no connectivity will still execute a job with no connectivity constraints.</string> 3727 3728 <!-- String for the bundled TV app Tests --> 3729 3730 <string name="tv_input_discover_test">3rd-party TV input test</string> 3731 <string name="tv_input_discover_test_info"> 3732 Verify that the bundled TV app launches via Intent and calls the proper API to discover 3733 3rd-party TV inputs. 3734 </string> 3735 <string name="tv_input_discover_test_third_party_tif_input_support"> 3736 Does the bundled TV app support third-party TV inputs? 3737 </string> 3738 <string name="tv_input_discover_test_go_to_setup"> 3739 Select the \"Launch TV app\" button and set up the newly installed TV input: 3740 \"CTS Verifier\". 3741 </string> 3742 <string name="tv_input_discover_test_verify_setup"> 3743 Setup activity must have been started. 3744 </string> 3745 <string name="tv_input_discover_test_tune_to_channel"> 3746 Select the \"Launch TV app\" button and tune to the \"Dummy\" channel from \"CTS Verifier\" 3747 input. If necessary, configure the channel to be visible. 3748 </string> 3749 <string name="tv_input_discover_test_verify_tune"> 3750 Tune command must be called. 3751 </string> 3752 <string name="tv_input_discover_test_verify_overlay_view"> 3753 Verify that the overlay appears and displays the text \"Overlay View Dummy Text\" when you tune 3754 to the \"Dummy\" channel. 3755 </string> 3756 <string name="tv_input_discover_test_verify_size_changed"> 3757 Verify that video layout changes correctly according to the provided video track information, 3758 including pixel aspect ratio. 3759 </string> 3760 <string name="tv_input_discover_test_verify_global_search"> 3761 Verify the TV app provides query results for 3rd-party input\'s channels and programs in 3762 global search results. 3763 </string> 3764 <string name="tv_input_discover_test_go_to_epg"> 3765 Select the \"Launch EPG\" button and locate the \"Dummy\" channel. 3766 </string> 3767 <string name="tv_input_discover_test_verify_epg"> 3768 Do you see the programs named \"Dummy Program\" and their descriptions 3769 "Dummy Program Description" in the EPG? 3770 </string> 3771 <string name="tv_input_discover_test_trigger_setup"> 3772 Select the \"Launch setup\" button and verify if the bundled TV app shows the list of installed 3773 TV inputs for setup. 3774 </string> 3775 <string name="tv_input_discover_test_verify_trigger_setup"> 3776 Do you see the \"CTS Verifier\" input in the list? 3777 </string> 3778 3779 <string name="tv_parental_control_test">TV app parental controls test</string> 3780 <string name="tv_parental_control_test_info"> 3781 Verify that the bundled TV app calls the parental controls API. 3782 </string> 3783 <string name="tv_parental_control_test_turn_on_parental_control"> 3784 Select the \"Launch TV app\" button and turn on the parental controls. If parental controls are 3785 on already, turn it off and on again. 3786 </string> 3787 <string name="tv_parental_control_test_verify_receive_broadcast1"> 3788 TV input service must have received ACTION_PARENTAL_CONTROLS_ENABLED_CHANGED broadcast. 3789 </string> 3790 <string name="tv_parental_control_test_check_parental_controls_switch"> 3791 Is there an option to turn off parental controls on this device? 3792 </string> 3793 <string name="tv_parental_control_test_block_tv_ma"> 3794 Select the \"Launch TV app\" button and block the \"Custom Rating\" for \"CtsVerifier\" rating 3795 system in the parental control settings. If the rating system is disabled by default, enable it. 3796 If the \"Custom Rating\" is already blocked, unblock it, save, and then block again. 3797 </string> 3798 <string name="tv_parental_control_test_verify_receive_broadcast2"> 3799 TV input service must have received ACTION_BLOCKED_RATINGS_CHANGED broadcast. 3800 </string> 3801 <string name="tv_parental_control_test_block_unblock"> 3802 Select the \"Launch TV app\" button; verify that the channel is blocked. 3803 Try to unblock the screen by entering PIN; verify that it\'s unblocked. 3804 </string> 3805 3806 <string name="tv_yes">Yes</string> 3807 <string name="tv_no">No</string> 3808 <string name="tv_launch_tv_app">Launch TV app</string> 3809 <string name="tv_launch_epg">Launch EPG</string> 3810 <string name="tv_launch_setup">Launch setup</string> 3811 <string name="tv_channel_not_found"> 3812 CtsVerifier channel is not set up. Please set up before proceeding. 3813 </string> 3814 3815 <string name="tv_multiple_tracks_test">TV app closed captions and multi-audio test</string> 3816 <string name="tv_multiple_tracks_test_info"> 3817 Verify that the bundled TV app calls the multi-track API. 3818 </string> 3819 <string name="tv_multiple_tracks_test_select_subtitle"> 3820 Select the \"Launch TV app\" button. Verify that closed captions are off by default. Set closed 3821 caption language to English. 3822 </string> 3823 <string name="tv_multiple_tracks_test_verify_set_caption_enabled"> 3824 Captions are enabled. 3825 </string> 3826 <string name="tv_multiple_tracks_test_verify_select_subtitle"> 3827 The English closed caption track should be selected. 3828 </string> 3829 <string name="tv_multiple_tracks_test_select_audio"> 3830 Select the \"Launch TV app\" button. Verify that the audio track is English by default. 3831 Select Spanish audio track. 3832 </string> 3833 <string name="tv_multiple_tracks_test_verify_select_audio"> 3834 The Spanish audio track should be selected. 3835 </string> 3836 3837 <string name="tv_time_shift_test">TV app time shift test</string> 3838 <string name="tv_time_shift_test_info"> 3839 This test verifies that the TV app invokes proper time shift APIs in the framwork. 3840 </string> 3841 <string name="tv_time_shift_test_pause_resume"> 3842 Press the \"Launch TV app\" button. Verify that the playback control is available. 3843 Pause the playback and then resume it. 3844 </string> 3845 <string name="tv_time_shift_test_verify_resume_after_pause"> 3846 The playback should resume after pause. 3847 </string> 3848 <string name="tv_time_shift_test_verify_position_tracking"> 3849 The playback position tracking should be activated. 3850 </string> 3851 <string name="tv_time_shift_test_speed_rate"> 3852 Press the \"Launch TV app\" button. Verify that the playback control is available. 3853 Rewind the playback and in a few seconds fast-forward it. 3854 </string> 3855 <string name="tv_time_shift_test_verify_rewind"> 3856 The playback should rewind. 3857 </string> 3858 <string name="tv_time_shift_test_verify_fast_forward"> 3859 The playback should fast-forward. 3860 </string> 3861 <string name="tv_time_shift_test_seek"> 3862 Press the \"Launch TV app\" button. Verify that the playback control is available. 3863 Seek to previous and then seek to next. 3864 </string> 3865 <string name="tv_time_shift_test_verify_seek_to_previous"> 3866 The playback position should be moved to the previous position. 3867 </string> 3868 <string name="tv_time_shift_test_verify_seek_to_next"> 3869 The playback position should be moved to the next position. 3870 </string> 3871 3872 <string name="tv_app_link_test">TV app app-link test</string> 3873 <string name="tv_app_link_test_info"> 3874 Verify that the bundled TV app supports linking to channel apps. If a TV input service provides 3875 links for its specific channels, the TV app should show the links in a proper format. 3876 </string> 3877 <string name="tv_app_link_test_select_app_link"> 3878 Select the \"Launch TV app\" button, then check if you can see a menu with \"Cts App-Link Text\" 3879 text in red background. If you see the link, select it to follow the link. 3880 </string> 3881 <string name="tv_app_link_test_verify_link_clicked"> 3882 The app-link must have been clicked and the activity should be changed correctly. 3883 </string> 3884 <string name="tv_input_link_test_verify_link_interface"> 3885 Do you see the app-link card similar to the image on the left?\n 3886 1) You should see the poster art image, but the color may be different.\n 3887 2) You should see the text \"Cts App-Link Text\".\n 3888 </string> 3889 3890 <string name="tv_microphone_device_test">Microphone device test</string> 3891 <string name="tv_microphone_device_test_info"> 3892 This test checks if InputDevice.hasMicrophone of the Media API reports a 3893 correct value on every input device (including remote controls). 3894 </string> 3895 <string name="tv_microphone_device_test_prep_question"> 3896 Before continuing, please make sure that you pair all primary input 3897 devices intended to be used by the device, including bluetooth 3898 remotes and companion remote-control apps such as the Android TV Remote Control. 3899 Have you paired every primary input device with the device under test (DUT)? 3900 </string> 3901 <string name="tv_microphone_device_test_mic_question"> 3902 Does input device \"%1$s\" have a microphone? 3903 </string> 3904 <string name="tv_microphone_device_test_negative_mismatch"> 3905 InputDevice.hasMicrophone reports that this input device DOES have a 3906 microphone whereas you selected that it does not. Please correct it by 3907 declaring \"audio.mic = 0\" in the device\'s input device configuration 3908 (.idc) file. 3909 </string> 3910 <string name="tv_microphone_device_test_positive_mismatch"> 3911 InputDevice.hasMicrophone reports that this input device does NOT have a 3912 microphone whereas you selected that it does. Please correct it by 3913 declaring \"audio.mic = 1\" in the device\'s input device configuration 3914 (.idc) file and make sure that relevant files such as key layout (.kl) 3915 and key character map (.kcm) files are found by the system accordingly. 3916 </string> 3917 <string name="tv_microphone_device_test_no_input_devices">No input devices found.</string> 3918 3919 <string name="overlay_view_text">Overlay View Dummy Text</string> 3920 <string name="custom_rating">Example of input app specific custom rating.</string> 3921 3922 <!-- A list of fully-qualified test classes that should not be run. --> 3923 <string-array name="disabled_tests" /> 3924 3925 <!-- Strings for screen pinning test --> 3926 <string name="screen_pinning_test">Screen Pinning Test</string> 3927 <string name="screen_pin_instructions">Pressing next will prompt you to enter screen pinning, allow this app to enter screen pinning.</string> 3928 <string name="screen_pin_check_pinned">Press Next to verify the app is pinned.</string> 3929 <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> 3930 <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> 3931 <string name="screen_pinning_done">All tests completed successfully.</string> 3932 3933 <string name="error_screen_no_longer_pinned">The screen was no longer pinned.</string> 3934 <string name="error_screen_already_pinned">Cannot start the test with the screen already pinned.</string> 3935 <string name="error_screen_pinning_did_not_start">Screen was not pinned.</string> 3936 <string name="error_screen_pinning_did_not_exit">Screen was not unpinned.</string> 3937 <string name="error_screen_pinning_couldnt_exit">Could not exit screen pinning through API.</string> 3938 3939 <!-- Audio Devices Notifcations Tests --> 3940 <string name="audio_out_devices_notifications_test">Audio Output Devices Notifications Test</string> 3941 <string name="audio_out_devices_notification_instructions"> 3942 Click the "Clear Messages" button then connect and disconnect a wired headset. 3943 Note if the appropriate notification messages appear below. 3944 </string> 3945 <string name="audio_in_devices_notifications_test">Audio Input Devices Notifications Test</string> 3946 <string name="audio_in_devices_notification_instructions"> 3947 Click the "Clear Messages" button then connect and disconnect a microphone or wired headset. 3948 Note if the appropriate notification messages appear below. 3949 </string> 3950 <string name="audio_dev_notification_clearmsgs">Clear Messages</string> 3951 <string name="audio_dev_notification_connectMsg">CONNECT DETECTED</string> 3952 <string name="audio_dev_notification_disconnectMsg">DISCONNECT DETECTED</string> 3953 3954 <string name="audio_input_routingnotifications_test">Audio Input Routing Notifications Test</string> 3955 <string name="audio_input_routingnotification_instructions"> 3956 Click on the "Record" button in the AudioRecord Routing Notifications section below to 3957 start recording. Insert a wired headset or microphone. Observe a message acknowledging the 3958 rerouting event below. Remove the wired headset and observe the new routing message. 3959 Click on the "Stop" button to stop recording.\n 3960 </string> 3961 <string name="audio_output_routingnotifications_test">Audio Output Routing Notifications Test</string> 3962 <string name="audio_output_routingnotification_instructions"> 3963 Click on the "Play" button in the AudioTrack Routing Notifications section below to 3964 start (silent) playback. Insert a wired headset. Observe a message acknowledging the 3965 rerouting event below. Remove the wired headset and observe the new routing message. 3966 Click on the "Stop" button to stop playback.\n 3967 </string> 3968 <string name="audio_routingnotification_playBtn">Play</string> 3969 <string name="audio_routingnotification_playStopBtn">Stop</string> 3970 <string name="audio_routingnotification_recBtn">Record</string> 3971 <string name="audio_routingnotification_recStopBtn">Stop</string> 3972 <string name="audio_routingnotification_playHeader">AudioTrack Routing Notifications</string> 3973 <string name="audio_routingnotification_recHeader">AudioRecord Routing Notifications</string> 3974 <string name="audio_routingnotification_trackRoutingMsg">AudioTrack rerouting</string> 3975 <string name="audio_routingnotification_recordRoutingMsg">AudioRecord rerouting</string> 3976 3977 <!-- USB Audio Peripheral Tests --> 3978 <string name="profileLabel">Profile</string> 3979 <string name="connectedPeripheral">Connected Peripheral</string> 3980 <string name="audio_uap_attribs_test">USB Audio Peripheral Attributes Test</string> 3981 <string name="uapPeripheralProfileStatus">Peripheral Profile Status</string> 3982 3983 <string name="audio_uap_play_test">USB Audio Peripheral Play Test</string> 3984 <string name="uapPlayTestInstructions">Connect the USB Audio Interface Peripheral and press the 3985 PLAY button below. Verify that a tone is correctly played.</string> 3986 <string name="audio_uap_play_playBtn">Play</string> 3987 <string name="audio_uap_play_stopBtn">Stop</string> 3988 3989 <string name="audio_uap_record_test">USB Audio Peripheral Record Test</string> 3990 <string name="uapRecordTestInstructions">Connect the USB Audio Peripheral and press the RECORD or 3991 RECORD LOOPBACK button below. Verify that a tone is correctly played.</string> 3992 <string name="audio_uap_record_recordBtn">Record</string> 3993 <string name="audio_uap_record_recordLoopbackBtn">Record Loopback</string> 3994 <string name="audio_uap_record_stopBtn">Stop</string> 3995 3996 <string name="audio_uap_buttons_test">USB Audio Peripheral Buttons Test</string> 3997 <string name="uapButtonTestInstructions">Connect the USB Audio headset with buttons 3998 and press each transport/media button in turn.</string> 3999 4000 <string name="uapButtonsBtnALbl">Button A - play/pause</string> 4001 <string name="uapButtonsBtnBLbl">Button B - volume up (+)</string> 4002 <string name="uapButtonsBtnCLbl">Button C - volume down (-)</string> 4003 <string name="uapButtonsBtnDLbl">Button D - voice assist</string> 4004 <string name="uapButtonsRecognized">Recognized</string> 4005 <string name="uapButtonsNotRecognized">Not Recognized</string> 4006 4007 <!-- Audio general text --> 4008 <string name="audio_general_headset_port_exists">Does this device have a headset port?</string> 4009 <string name="audio_general_headset_no">No</string> 4010 <string name="audio_general_headset_yes">Yes</string> 4011 <string name="audio_general_deficiency_found">WARNING: Some results show potential deficiencies on the system. 4012 Please consider addressing them for a future release.</string> 4013 <string name="audio_general_test_passed">Test Result: Successful</string> 4014 <string name="audio_general_test_failed">Test Result: Not Optimal</string> 4015 <string name="audio_general_default_false_string">false</string> 4016 <string name="audio_general_default_true_string">true</string> 4017 <string name="audio_general_warning">Warning</string> 4018 <string name="audio_general_ok">Ok</string> 4019 <string name="audio_general_level_not_max">Audio Level is not maximum. Please check your device 4020 is set to max level for audio playback.</string> 4021 4022 <!-- Audio Loopback Latency Test --> 4023 <string name="audio_loopback_test">Audio Loopback Latency Test</string> 4024 <string name="audio_loopback_info"> 4025 This test requires the Loopback Plug. Please connect a Loopback Plug into the headset 4026 connector, and proceed with the instructions on the screen. 4027 The system will measure the input-output audio latency by injecting a pulse on the output, 4028 and computing the distance between replicas of the pulse. 4029 You can vary the Audio Level slider to ensure the pulse will feed back at adequate levels. 4030 Repeat until a confidence level >= 0.6 is achieved. 4031 </string> 4032 <string name="audio_loopback_instructions"> 4033 Please connect a "Loopback Plug" and press "Loopback Plug Ready". 4034 </string> 4035 <string name="audio_loopback_plug_ready_btn">Loopback Plug Ready</string> 4036 <string name="audio_loopback_instructions2"> 4037 Set the audio level to a suitable value, then press Test button. 4038 It might require multiple tries until a confidence >= 0.6 is achieved. 4039 </string> 4040 <string name="audio_loopback_level_text">Audio Level</string> 4041 <string name="audio_loopback_test_btn">Test</string> 4042 <string name="audio_loopback_results_text">Results...</string> 4043 4044 <!-- Audio Frequency Line Test --> 4045 <string name="audio_frequency_line_test">Audio Frequency Line Test</string> 4046 <string name="audio_frequency_line_info"> 4047 The system will measure the frequency response of the left and right line outputs, 4048 by feeding them back thru the microphone conection with the loopback jack. 4049 This test requires the Loopback Plug. Please connect a Loopback Plug on the headset 4050 connector, and proceed with the instructions on the screen. 4051 </string> 4052 <string name="audio_frequency_line_instructions"> 4053 Please connect a "Loopback Plug" and press "Loopback Plug Ready". 4054 </string> 4055 <string name="audio_frequency_line_plug_ready_btn">Loopback Plug Ready</string> 4056 4057 <string name="audio_frequency_line_test_btn">Test</string> 4058 <string name="audio_frequency_line_results_text">Results...</string> 4059 4060 <!-- Audio Frequency Speaker Test --> 4061 <string name="audio_frequency_speaker_test">Audio Frequency Speaker Test</string> 4062 <string name="audio_frequency_speaker_info"> 4063 This test requires an external USB reference microphone. Please connect the USB microphone and proceed with the instructions on the screen. 4064 The system will measure frequency response of the left and right speakers (if there are two speakers), or the response of the mono speaker twice. 4065 </string> 4066 <string name="audio_frequency_speaker_instructions"> 4067 Please connect an USB reference microphone and press "USB Reference microphone ready" 4068 </string> 4069 <string name="audio_frequency_speaker_usb_status">Waiting for USB microphone...</string> 4070 <string name="audio_frequency_speaker_mic_ready_btn">USB Reference microphone ready</string> 4071 <string name="audio_frequency_speaker_mic_ready_text">USB Audio device detected\n\nPlease set up Device Under test 4072 in quiet room, and Microphone 20 cms perpendicular to center of screen, then press TEST</string> 4073 <string name="audio_frequency_speaker_mic_not_ready_text">"No USB Audio device detected. Please reconnect."</string> 4074 <string name="audio_frequency_speaker_test_btn">Test</string> 4075 <string name="audio_frequency_speaker_results_text">Results...</string> 4076 4077 <!-- Audio Frequency Microphone Test --> 4078 <string name="audio_frequency_mic_test">Audio Frequency Microphone Test</string> 4079 <string name="frequency_mic_info"> 4080 This test requires an external USB reference microphone and external speakers. 4081 The test signals can be played from the device under test (DUT) or from a secondary device (e.g. when your DUT cant support a USB microphone and external speakers simultaneously, or DUT does not have headphone output). 4082 Follow the instructions on the screen to measure the frequency response for the built in microphone. 4083 </string> 4084 4085 <string name="frequency_mic_play">Play</string> 4086 <string name="frequency_mic_stop">Stop</string> 4087 <string name="frequency_mic_noise_instructions">TEST NOISE: Position speakers 40 cms from device under test. 4088 Press [PLAY] to play broadband white noise. Press [TEST] 4089 </string> 4090 <string name="frequency_mic_test_noise_btn">Test</string> 4091 <string name="frequency_mic_test_noise_result">Results...</string> 4092 4093 <string name="frequency_mic_test_usb_background_instructions">TEST USB BACKGROUND: Connect USB microphone and position it right next to microphone under test. 4094 No source of noise should be active during this test. Press [TEST]</string> 4095 <string name="frequency_mic_test_usb_background_btn">Test</string> 4096 <string name="frequency_mic_test_usb_background_result">Results...</string> 4097 4098 <string name="frequency_mic_test_usb_noise_instructions">TEST USB NOISE: Connect USB microphone and position it right next to microphone under test. 4099 Position speakers 40 cms from device under test. Press [PLAY] to play broadband white noise. Press [TEST]</string> 4100 <string name="frequency_mic_test_usb_noise_btn">Test</string> 4101 <string name="frequency_mic_test_usb_noise_result">Results...</string> 4102 4103 <string name="frequency_mic_test_global_result">Global Results...</string> 4104 4105 <!-- Audio Frequency Unprocessed Test --> 4106 <string name="audio_frequency_unprocessed_test">Audio Frequency Unprocessed Test</string> 4107 <string name="audio_frequency_unprocessed_info"> 4108 This test requires an external USB reference microphone, external speakers and a Sound Pressure Level meter. 4109 You can play the test signals from the device under test or from a secondary device. 4110 Follow the instructions on the screen to measure the frequency response for the built in microphone 4111 using UNPROCESSED audio source. 4112 If the Audio Frequency Unprocessed feature is defined in this system, success in all tests is mandatory to pass. 4113 If the feature is not defined, measurements are still needed, but success in all of them is not mandatory to pass. 4114 </string> 4115 <string name="audio_frequency_unprocessed_defined">Audio Frequency Unprocessed feature is defined. Success in all tests is mandatory to pass</string> 4116 <string name="audio_frequency_unprocessed_not_defined">Audio Frequency Unprocessed feature is NOT defined. Success in all test is NOT mandatory to pass</string> 4117 4118 <string name="unprocessed_play">Play</string> 4119 <string name="unprocessed_stop">Stop</string> 4120 4121 <string name="unprocessed_test_tone_instructions">TEST TONE: Press [PLAY] to play tone at 1 Khz. Measure sound SPL to be 94 dB 4122 right next to microphone under test. Press [TEST]</string> 4123 <string name="unprocessed_test_tone_btn">Test</string> 4124 <string name="unprocessed_test_tone_result">Results...</string> 4125 4126 <string name="unprocessed_test_noise_instructions">TEST NOISE: Position speakers 40 cms from device under test. 4127 Press [PLAY] to play broadband white noise. Press [TEST]</string> 4128 <string name="unprocessed_test_noise_btn">Test</string> 4129 <string name="unprocessed_test_noise_result">Results...</string> 4130 4131 <string name="unprocessed_test_usb_background_instructions">TEST USB BACKGROUND: Connect USB microphone and position it right next to microphone under test. 4132 No source of noise should be active during this test. Press [TEST]</string> 4133 <string name="unprocessed_test_usb_background_btn">Test</string> 4134 <string name="unprocessed_test_usb_background_result">Results...</string> 4135 4136 <string name="unprocessed_test_usb_noise_instructions">TEST USB NOISE: Connect USB microphone and position it right next to microphone under test. 4137 Position speakers 40 cms from device under test. Press [PLAY] to play broadband white noise. Press [TEST]</string> 4138 <string name="unprocessed_test_usb_noise_btn">Test</string> 4139 <string name="unprocessed_test_usb_noise_result">Results...</string> 4140 4141 <string name="unprocessed_test_global_result">Global Results...</string> 4142 4143 <!-- Strings for 6DoF test --> 4144 <string name="six_dof_test">6DoF Test</string> 4145 <string name="action_settings">Settings</string> 4146 <string name="start">Start</string> 4147 <string name="motion_tracking_permission">"Motion Tracking permission needed!"</string> 4148 <string name="translations">Translations:</string> 4149 <string name="rotations">Rotations:</string> 4150 <string name="action_place_marker">Place Marker</string> 4151 <string name="markers">Markers:\n</string> 4152 <string name="title_activity_cts">CTSActivity</string> 4153 <string name="stop">Stop!</string> 4154 <string name="stop_message">Mark where you are standing with something like a piece of card and 4155 then press ready to record this waypoint 4156 </string> 4157 <string name="ready">Ready</string> 4158 <string name="initial">First Waypoint</string> 4159 <string name="phase1_initial_message">When you are ready to place your first waypoint, place a 4160 marker at the devices current location. Use something that will allow you to put the device 4161 in the exact same position and orientation on the second lap. Then, while the device is on 4162 the marker, click the turquoise action button to record the first waypoint.\n\nStart walking 4163 in a direction. The button will appear again when you have walked far enough. Place a marker 4164 at the device\'s location and press the button to record a waypoint. You cannot place 4165 waypoints in a straight line, so for your 3rd waypoint turn 90 degrees and walk in a 4166 direction that will make a triangle out of your 3 waypoints. 4167 </string> 4168 <string name="phase2_initial_message">You now need to visit each waypoint, clicking the 4169 turquoise action button at each one. You need to reach each waypoint in 20 seconds. While 4170 you are on your way to the waypoints, the camera preview will rotate. You will need to 4171 rotate the device to match the rotation of the camera preview. A box will be shown to help 4172 you. It shows the device\'s current rotation and will change color based on whether you are 4173 close enough to the required rotation. Red if you are failing, green if you are passing. 4174 When you have reached the next waypoint, the device can be returned to its original 4175 rotation. 4176 </string> 4177 <string name="last">Go back to the first waypoint</string> 4178 <string name="last_message">Now go back to the first waypoint and press ready to finish the 4179 first lap. 4180 </string> 4181 <string name="got_it">Got it!</string> 4182 <string name="lap2_instructions">Now, go to each waypoint (including your initial 4183 one) and click the turquoise action button. Then move on to the next waypoint and do the 4184 same.\nThe last waypoint should be the first waypoint again. 4185 </string> 4186 <string name="test1_pass2">Pass 2</string> 4187 <string name="results">Results</string> 4188 <string name="overall_instructions">These tests are designed to verify the correctness and 4189 accuracy of a 6DoF enabled device. There will be 3 phases to these tests, each testing a 4190 different part of 6DoF functionality. 4191 </string> 4192 <string name="phase1_description">This first test will test the accuracy of the device. It will 4193 ask you to mark out 4 waypoints and then return to the original waypoint to complete the 4194 lap. After this you will then need to do another lap without any HUD information. At the 4195 end, the pairs of waypoints and the path you travelled will be compared and you will be 4196 given a result. 4197 </string> 4198 <string name="phase2_description">This test will test the robustness of the device. Using the 4199 same 4 waypoints as before, you will need to do a lap, reaching each waypoint in the 4200 allotted time.\nWhile you are on your way to the waypoints, the camera preview will rotate. 4201 You will need to rotate the device to match the rotation of the camera preview. A box will 4202 be shown to help you. It shows the device\'s current rotation and will change color based 4203 on whether you are close enough to the required rotation. Red if you are failing, green if 4204 you are passing. When you have reached the next waypoint, the device can be returned to 4205 its original rotation. 4206 </string> 4207 <string name="phase3_description">Now we will test the AR capability of the device. Again, you 4208 will need to do a lap of the waypoints, but this time between each waypoint the device will 4209 overlay hoops that you must pass the device through as you go along. 4210 </string> 4211 <string name="distance">Distance from last waypoint:</string> 4212 <string name="obj_return_to_initial_waypoint">Return to initial waypoint</string> 4213 <string name="waypointPlaced">Waypoint placed!</string> 4214 <string name="undo">undo</string> 4215 <string name="distance_remaining">Distance Remaining:\n</string> 4216 <string name="waypoint_differences">Waypoints</string> 4217 <string name="path_differences">Paths</string> 4218 <string name="error_distance">Not far away enough from other waypoints!</string> 4219 <string name="error_area">Not enough area covered.</string> 4220 <string name="passed">Passed!</string> 4221 <string name="failed">Failed!</string> 4222 <string name="test_failed">Test Failed!</string> 4223 <string name="error_start_point">Not close enough to initial waypoint!</string> 4224 <string name="waypoint_distance">Waypoint %1$s: %2$s</string> 4225 <string name="total">Total %1$s</string> 4226 <string name="path">Path %1$s: %2$s</string> 4227 <string name="fail">Fail</string> 4228 <string name="pass">Pass</string> 4229 <string name="info">Info</string> 4230 <string name="coming_soon">Coming soon!</string> 4231 <string name="motion_tracking_invalid_state">Motion Tracking has entered an invalid state 4232 </string> 4233 <string name="action_xml">XML</string> 4234 <string name="error_null_fragment">UI fragment was null, couldn\'t do callback to listener 4235 </string> 4236 <string name="error_retained_fragment_null">DataFragment is null</string> 4237 <string name="time_remaining">%1$s seconds remaining to get to next waypoint</string> 4238 <string name="action_skip_to_2nd">Skip to 2nd Test</string> 4239 <string name="failed_pause_resume">Test Failed because Test Activity was paused</string> 4240 <string name="action_overlapping_outlines">Overlapping Outlines</string> 4241 <string name="action_overlapping_filled">Overlapping Filled</string> 4242 <string name="time">Time</string> 4243 <string name="rotation_result">Rotation</string> 4244 <string name="action_separate_outlines">Separate Outlines</string> 4245 <string name="action_separate_filled">Separate Filled</string> 4246 <string name="action_one">One Rectangle</string> 4247 <string name="rotation_mode">Change rotation mode</string> 4248 <string name="phase3_initial_message">Go through the rings as you visit waypoints.</string> 4249 <string name="rings">Rings</string> 4250 <string name="rings_entered">Rings collected %1$s/%2$s</string> 4251 <string name="error_rings_not_entered">You haven\'t collected all the rings in this path! 4252 </string> 4253 <string name="save">Save</string> 4254 4255 <string-array name="initial_waypoint"> 4256 <item>Find a place for your first waypoint</item> 4257 <item>Go to initial waypoint</item> 4258 </string-array> 4259 4260 <string-array name="next_waypoint"> 4261 <item>Find a suitable place for waypoint 0</item> 4262 <item>Go to waypoint 0</item> 4263 </string-array> 4264 4265 <string-array name="phase"> 4266 <item>Phase 1</item> 4267 <item>Phase 2</item> 4268 <item>Phase 3</item> 4269 </string-array> 4270 4271 <string-array name="phase_descriptions"> 4272 <item>@string/phase1_description</item> 4273 <item>@string/phase2_description</item> 4274 <item>@string/phase3_description</item> 4275 </string-array> 4276 4277 <!-- Strings for setting and restoring default dialer for voicemail tests --> 4278 <string name="voicemail_restore_default_dialer_description">Restore the default dialer setting</string> 4279 <string name="voicemail_restore_default_dialer_no_default_description">Restore the default dialer by going to settings-> apps -> cogwheel -> Phone app</string> 4280 <string name="voicemail_restore_default_dialer_button">Restore the default dialer"</string> 4281 <string name="voicemail_default_dialer_already_set">Default dialer already set</string> 4282 <string name="voicemail_default_dialer_already_restored">Default dialer already restored</string> 4283 <string name="voicemail_set_default_dialer_description">Before the test, the CTS verifier should be set to the default dialer</string> 4284 <string name="voicemail_set_default_dialer_button">Set CTS verifier as default dialer"</string> 4285 4286 <!-- Strings for voicemail broadcast test --> 4287 <string name="voicemail_broadcast_test">Voicemail Broadcast Test</string> 4288 <string name="voicemail_broadcast_instructions">This test verifies that the default dialer can intercept the voicemail notification. The test must be conducted on a SIM with visual voicemail disabled</string> 4289 <string name="voicemail_broadcast_no_carrier_support">The carrier does not support voicemail, this test is not applicable.</string> 4290 <string name="voicemail_leave_voicemail">Send a voicemail to the device, CTS verifier should receive a voicemail notification broadcast</string> 4291 <string name="voicemail_broadcast_received">Voicemail broadcast Received</string> 4292 4293 <!-- Strings for VisualVoicemailService test --> 4294 <string name="visual_voicemail_service_test">VisualVoicemailService Test</string> 4295 <string name="visual_voicemail_service_instructions">This test verifies that the VisualVoicemailService can receive SIM inserted and removed events</string> 4296 <string name="visual_voicemail_service_remove_sim_before_test">Removed the SIM before starting the test. This test only applies to devices with hotswap-able SIM</string> 4297 <string name="visual_voicemail_service_remove_sim_ok">Ok</string> 4298 <string name="visual_voicemail_service_remove_sim_not_applicable">Not applicable</string> 4299 <string name="visual_voicemail_service_insert_sim">Insert SIM</string> 4300 <string name="visual_voicemail_service_insert_sim_received">Service connection event received</string> 4301 <string name="visual_voicemail_service_remove_sim">Remove SIM</string> 4302 <string name="visual_voicemail_service_remove_sim_received">SIM removal event received</string> 4303 4304 <!-- Strings for CallSettingsCheck test --> 4305 <string name="call_settings_check_test">Hide voicemail in call settings test</string> 4306 <string name="call_settings_check_instructions">This test verifies that the default dialer can 4307 hide voicemail settings in the call settings menu by using 4308 TelephonyManager.METADATA_HIDE_VOICEMAIL_SETTINGS_MENU 4309 </string> 4310 <string name="open_call_settings_explanation">Tap the button, and verify that \"voicemail\" does 4311 not exist in the call settings 4312 </string> 4313 <string name="open_call_settings">Open call settings</string> 4314 <string name="voicemail_hidden">\"Voicemail\" does not exist</string> 4315 <string name="voicemail_not_hidden">\"Voicemail\" exists</string> 4316 4317 <!-- Strings for DialerIncomingCall test --> 4318 <string name="dialer_incoming_call_test">Dialer Receives Incoming Call</string> 4319 <string name="dialer_incoming_call_test_instructions">This test verifies that the default dialer 4320 can receive incoming calls after it has been set. 4321 </string> 4322 <string name="dialer_incoming_call_detected">Detected the incoming call. Activity passed.</string> 4323 <string name="dialer_check_incoming_call_explanation">Call the device.</string> 4324 <string name="dialer_check_incoming_call">Verify Call Received</string> 4325 4326 <!-- Strings for VoicemailSettingsCheck test --> 4327 <string name="ringtone_settings_check_test">Hide settings in voicemail test</string> 4328 <string name="ringtone_settings_check_instructions">This test verifies that voicemail settings 4329 accessible with public API can be hidden when launching 4330 TelephonyManager.ACTION_CONFIGURE_VOICEMAIL with EXTRA_HIDE_PUBLIC_SETTINGS. 4331 </string> 4332 <string name="open_voicemail_settings_explanation">Tap the button, ringtone and virbration 4333 settings does not exist in the voicemail settings. 4334 </string> 4335 <string name="open_voicemail_settings">Open voicemail settings</string> 4336 <string name="ringtone_hidden">Ringtone settings does not exist</string> 4337 <string name="ringtone_not_hidden">Ringtone settings exists</string> 4338 4339 <!-- Strings for DialerShowsHunOnIncomingCallActivity test --> 4340 <string name="dialer_shows_hun_test">Dialer Shows HUN on Incoming Call</string> 4341 <string name="dialer_shows_hun_test_instructions">This test verifies that the default dialer 4342 shows a heads up notification on incoming call, and that only one notification is shown. 4343 </string> 4344 <string name="dialer_shows_hun_explanation">Call the device. 4345 Check the box if the heads up notification was shown containing the text 4346 \"CTS Incoming Call Notification\", and only one incoming call notification was shown. 4347 </string> 4348 <string name="dialer_shows_hun_check_box">HUN shown and meets criteria specified above.</string> 4349 <string name="dialer_incoming_call_hun_teaser">Incoming Call</string> 4350 <string name="dialer_incoming_call_hun_desc">CTS Incoming Call Notification</string> 4351 4352 <!-- Strings for DialerImplementsTelecomIntentsActivity test --> 4353 <string name="dialer_telecom_intents_test">System Implements Telecom Intents</string> 4354 <string name="dialer_telecom_intents_test_instructions">This test verifies that the system handles 4355 the specified Telecom Intents. 4356 </string> 4357 <string name="dialer_check_intents_implemented_explanation">Press the buttons below to launch settings activities. 4358 Check the associated box if the activity loads and was launched succesfully.</string> 4359 <string name="dialer_telecom_intents_call_settings">Launch call settings</string> 4360 <string name="dialer_telecom_intents_short_sms">Launch short sms answer settings</string> 4361 <string name="dialer_telecom_intents_calling_accounts">Launch calling accounts settings</string> 4362 <string name="dialer_telecom_intents_accessibility_settings">Launch accessibility settings</string> 4363 <string name="dialer_check_intents_check_box">Setting Launched</string> 4364 4365 <!-- USB Audio Peripheral Tests --> 4366 <string name="usbaudio_results_text">Results...</string> 4367 4368 <!-- USB Audio Peripheral Attributes Test --> 4369 <string name="usbaudio_attribs_test"> USB Audio Peripheral Attributes Test</string> 4370 <string name="usbaudio_attribs_info"> 4371 This test requires that you have connected a mandated USB Audio Interface peripheral. 4372 If the discovered attributes of the peripheral matches the known attributes of the 4373 peripheral the test passes and the \"pass\" button will be enabled. 4374 </string> 4375 4376 <!-- USB Audio Peripheral Play Test --> 4377 <string name="usbaudio_play_test"> USB Audio Peripheral Play Test</string> 4378 <string name="usbaudio_play_info"> 4379 This test requires that you have connected a mandated USB Audio Interface peripheral and 4380 some way to monitor the output. Press the \"Play\" button and verify that a tone is produced. 4381 </string> 4382 4383 <!-- USB Audio Peripheral Record Test --> 4384 <string name="usbaudio_record_test"> USB Audio Peripheral Record Test</string> 4385 <string name="usbaudio_record_info"> 4386 This test requires that you have connected a mandated USB Audio Interface peripheral. 4387 Connect the outputs to the inputs (with patch cables). Start playback by pressing the 4388 \"Record Loopback\" button and verify that the recorded signal is displayed in the wave 4389 display view. (It may be necessary to adjust the input controls on the peripheral). 4390 </string> 4391 4392 <!-- USB Audio Peripheral Buttons Test --> 4393 <string name="usbaudio_buttons_test"> USB Audio Peripheral Buttons Test</string> 4394 <string name="usbaudio_buttons_info"> 4395 This test requires that you have connected a mandated USB Audio headset. Press each 4396 \"transport\" button and verify that it is recognized by the test. 4397 </string> 4398 4399 <!-- Telecom tests --> 4400 <string name="telecom_enable_phone_account_test"> Telecom Enable Phone Account Test</string> 4401 <string name="telecom_enable_phone_account_info"> 4402 This test verifies that a third party ConnectionService can be enabled by the user. 4403 </string> 4404 <string name="telecom_enable_phone_account_step_1"> 4405 Click the button below to register a test PhoneAccount and ConnectionService. 4406 </string> 4407 <string name="telecom_enable_phone_account_register_button">Register Phone Account</string> 4408 <string name="telecom_enable_phone_account_step_2"> 4409 In the Calling accounts settings, choose "All calling accounts" and enable the "CTS Verifier Test" account. 4410 On AOSP this is accessible from: Phone app > Settings > Calls > Calling Accounts. 4411 Once you have completed this step, return here and click the Confirm button. 4412 </string> 4413 <string name="telecom_enable_phone_account_confirm_button">Confirm</string> 4414 4415 <string name="telecom_outgoing_call_test">Telecom Outgoing Call Test</string> 4416 <string name="telecom_outgoing_call_test_info">This test verifies that the default 4417 dialer on the system is able to make a call using a third-party ConnectionService.</string> 4418 <string name="telecom_outgoing_call_step_1"> 4419 Click the button below to register a test PhoneAccount and ConnectionService. You will be 4420 taken to the phone account selection screen. Please enable the "CTS Verifier Test" 4421 account and select it as the default account for outgoing calls. Once you have completed 4422 this step, return here and click the "Confirm Phone Account" button. 4423 </string> 4424 <string name="telecom_outgoing_call_register_enable_phone_account_button"> 4425 Register and Enable Phone Account 4426 </string> 4427 <string name="telecom_outgoing_call_confirm_register_button">Confirm Phone Account</string> 4428 <string name="telecom_outgoing_call_step_2"> 4429 Click the button below to dial an outgoing call. This will populate the default dialer 4430 app with a dummy phone number. Initiate the phone call from the dialer app, then return 4431 to this screen while the call is still in progress. 4432 </string> 4433 <string name="telecom_outgoing_call_dial_button">Dial</string> 4434 <string name="telecom_outgoing_call_step_3"> 4435 Click the button below to confirm that the ongoing outgoing call was correctly made. 4436 </string> 4437 <string name="telecom_outgoing_call_confirm_button">Confirm</string> 4438 4439 <string name="telecom_incoming_call_test">Telecom Incoming Call Test</string> 4440 <string name="telecom_incoming_call_test_info">This test verifies that the default 4441 dialer on the system is able to receive a call from a third-party connection service. 4442 </string> 4443 <string name="telecom_incoming_call_step_1"> 4444 Click the button below to register a test PhoneAccount and ConnectionService. You will be 4445 taken to the phone account selection screen. Please enable the "CTS Verifier Test" 4446 account. Once you have completed this step, return here and click the 4447 "Confirm Phone Account" button. 4448 </string> 4449 <string name="telecom_incoming_call_register_enable_phone_account_button"> 4450 Register and Enable Phone Account 4451 </string> 4452 <string name="telecom_incoming_call_confirm_register_button">Confirm Phone Account</string> 4453 <string name="telecom_incoming_call_step_2"> 4454 Click the button below to initiate an incoming call. The phone should start ringing. 4455 Answer the call, confirm that you can hear an audio clip with Eisenhower\'s voice, then 4456 return to this screen while the call is still ongoing. 4457 </string> 4458 <string name="telecom_incoming_call_dial_button">Dial</string> 4459 <string name="telecom_incoming_call_step_3"> 4460 Click the button below to confirm that the ongoing incoming call was properly answered and 4461 that audio is audible. 4462 </string> 4463 <string name="telecom_incoming_call_confirm_button">Confirm</string> 4464 <string name="telecom_incoming_self_mgd_test"> Incoming Self-Managed Connection Test</string> 4465 <string name="telecom_incoming_self_mgd_info"> 4466 This test verifies that incoming calls from a Self-Managed Connection Service will trigger 4467 a Telecom-managed incoming call UI when there is already an ongoing call on the device. 4468 </string> 4469 <string name="telecom_incoming_self_mgd_step_1"> 4470 Click the button below to register a test self-managed ConnectionService. 4471 </string> 4472 <string name="telecom_incoming_self_mgd_register_button">Register Self-Managed ConnectionService</string> 4473 <string name="telecom_incoming_self_mgd_step_2"> 4474 Click the button below to test that the system incoming call notification shows. When the 4475 notification shows, "answer" the call. 4476 </string> 4477 <string name="telecom_incoming_self_mgd_show_ui_button">Show System Incoming UI</string> 4478 <string name="telecom_incoming_self_mgd_step_3"> 4479 Click the button below to confirm that the incoming call was answered. 4480 </string> 4481 <string name="telecom_incoming_self_mgd_confirm_answer_button">Confirm Answer</string> 4482 </resources> 4483
