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