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