1 <?xml version="1.0" encoding="utf-8"?> 2 <!-- Copyright (C) 2010 The Android Open Source Project 3 4 Licensed under the Apache License, Version 2.0 (the "License"); 5 you may not use this file except in compliance with the License. 6 You may obtain a copy of the License at 7 8 http://www.apache.org/licenses/LICENSE-2.0 9 10 Unless required by applicable law or agreed to in writing, software 11 distributed under the License is distributed on an "AS IS" BASIS, 12 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 13 See the License for the specific language governing permissions and 14 limitations under the License. 15 --> 16 <resources> 17 <string name="app_name">CTS Verifier</string> 18 19 <string name="title_version">CTS Verifier %1$s</string> 20 21 <string name="pass_button_text">Pass</string> 22 <string name="info_button_text">Info</string> 23 <string name="fail_button_text">Fail</string> 24 <string name="next_button_text">Next</string> 25 26 <!-- Strings for TestListActivity --> 27 <string name="test_category_audio">Audio</string> 28 <string name="test_category_camera">Camera</string> 29 <string name="test_category_device_admin">Device Administration</string> 30 <string name="test_category_hardware">Hardware</string> 31 <string name="test_category_networking">Networking</string> 32 <string name="test_category_sensors">Sensors</string> 33 <string name="test_category_location">Location</string> 34 <string name="test_category_security">Security</string> 35 <string name="test_category_streaming">Streaming</string> 36 <string name="test_category_features">Features</string> 37 <string name="test_category_deskclock">Clock</string> 38 <string name="test_category_jobscheduler">Job Scheduler</string> 39 <string name="test_category_other">Other</string> 40 <string name="clear">Clear</string> 41 <string name="test_results_cleared">Test results cleared.</string> 42 <string name="view">View</string> 43 <string name="test_results_error">Couldn\'t create test results report.</string> 44 <string name="export">Export</string> 45 <string name="no_storage">Cannot save report to external storage, see log for details.</string> 46 <string name="report_saved">Report saved to: %s</string> 47 48 <!-- Strings for ReportViewerActivity --> 49 <string name="report_viewer">Report Viewer</string> 50 51 <!-- Strings for BackupTestActivity --> 52 <string name="backup_test">Data Backup Test</string> 53 <string name="backup_info">This test checks that data backup and automatic restore works 54 properly. The test activity lists some preferences and files that are backed up and 55 restored by the CTS Verifier. If backup and restore is working properly, these values 56 should be restored after running the backup manager, uninstalling the app, and reinstalling 57 the CTS Verifier. 58 \n\nPress the \"Generate Test Data\" to populate these values 59 and then follow the on screen instructions to finish the test. 60 </string> 61 <string name="bu_preferences">Preferences</string> 62 <string name="bu_files">Files</string> 63 <string name="bu_loading">Loading...</string> 64 <string name="bu_generate">Generate Test Data</string> 65 <string name="bu_generate_error">Error occurred while generating test data...</string> 66 <string name="bu_instructions">Random values for the preferences and files have been saved. 67 \n\nFollow the instructions below to check that the data backup and restore works: 68 \n\n1. Make sure backup and automatic restore are enabled in settings. Depending on the 69 backup transport supported by the device you may need to do additional steps. For instance 70 you may need to set a Google account as the backup account for the device. 71 \n\n2. Run the backup manager: adb shell bmgr run 72 \n\n3. Uninstall the program: adb uninstall com.android.cts.verifier 73 \n\n4. Reinstall the CTS Verifier and verify that the values are still the same. 74 </string> 75 <string name="bu_settings">Settings</string> 76 77 <!-- Strings for Device Administration tests --> 78 <string name="da_policy_serialization_test">Policy Serialization Test</string> 79 <string name="da_policy_serialization_info">This test checks that a device policy is properly 80 saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create 81 a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the 82 device and verify that all rows in the policy list are green. Red items indicate policy 83 settings that were not loaded properly. 84 </string> 85 <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device 86 policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your 87 device and return to this test in the CTS Verifier. 88 </string> 89 <string name="da_generate_policy">Generate Policy</string> 90 <string name="da_apply_policy">Apply Policy</string> 91 <string name="da_random_policy">Random policy generated.</string> 92 <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string> 93 <string name="da_password_quality">Password Quality</string> 94 <string name="da_password_quality_alphabetic">Alphabetic</string> 95 <string name="da_password_quality_alphanumeric">Alphanumeric</string> 96 <string name="da_password_quality_numeric">Numeric</string> 97 <string name="da_password_quality_something">Something</string> 98 <string name="da_password_minimum_length">Minimum Password Length</string> 99 <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string> 100 <string name="da_maximum_time_to_lock">Maximum Time to Lock</string> 101 <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string> 102 103 <string name="da_screen_lock_test">Screen Lock Test</string> 104 <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow 105 method immediately locks the screen. It should lock the screen immediately despite any 106 settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen. 107 Your screen should be locked and require the password to be entered. 108 </string> 109 <string name="da_force_lock">Force Lock</string> 110 <string name="da_lock_success">It appears the screen was locked successfully!</string> 111 <string name="da_lock_error">It does not look like the screen was locked...</string> 112 113 <!-- Strings for BluetoothActivity --> 114 <string name="bluetooth_test">Bluetooth Test</string> 115 <string name="bluetooth_test_info">The Bluetooth Control tests check whether or not the device 116 can disable and enable Bluetooth properly.\n\nThe Device Communication tests require two 117 devices to pair and exchange messages. The two devices must be: 118 \n\n1. a candidate device implementation running the software build to be tested 119 \n\n2. a separate device implementation already known to be compatible</string> 120 121 <string name="bt_control">Bluetooth Control</string> 122 <string name="bt_device_communication">Device Communication</string> 123 <string name="bt_le">Bluetooth Low Energy</string> 124 125 <string name="bt_toggle_bluetooth">Toggle Bluetooth</string> 126 <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string> 127 <string name="bt_enable_bluetooth">Enable Bluetooth</string> 128 <string name="bt_disable_bluetooth">Disable Bluetooth</string> 129 <string name="bt_disabling">Disabling Bluetooth...</string> 130 <string name="bt_disabling_error">Could not disable Bluetooth...</string> 131 132 <string name="bt_connection_access_server">Connection Access Server</string> 133 <string name="bt_connection_access_client">Connection Access Client</string> 134 <string name="bt_connection_access_server_info"> 135 Start the CTS Verifier on another device, start the Bluetooth test, and choose 136 \"Connection Access Client\" to setup the test. 137 \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together 138 using the \"Make Discoverable\" and \"Pick Server\" buttons. 139 \n\nA connection access request should appear on the server and enable the pass button. 140 </string> 141 <string name="bt_connection_access_client_info"> 142 Start the CTS Verifier on another device, start the Bluetooth test, and choose 143 \"Connection Access Server\" to complete the test. 144 \n\nMake the device acting as the server discoverable and connect to it via the 145 \"Pick Server\" button. Check that the server displays the connection access request 146 dialog. The client device does not need to do anything else. 147 </string> 148 <string name="bt_ca_dialog">Was the connection access request dialog shown?</string> 149 <string name="bt_ca_tips"> 150 Tap the \"Bluetooth Settings\" button and check that both devices are not paired 151 before running the test. 152 \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth 153 devices together and start the test. 154 </string> 155 156 <string name="bt_secure_server">Secure Server</string> 157 <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> 158 <string name="bt_insecure_server">Insecure Server</string> 159 <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> 160 <string name="bt_waiting">Waiting for client...</string> 161 <string name="bt_listening">Listening...</string> 162 <string name="bt_connecting">Connecting...</string> 163 <string name="bt_connected">Connected</string> 164 <string name="bt_received_messages">Received Messages</string> 165 <string name="bt_sent_messages">Sent Messages</string> 166 <string name="bt_no_messages">No messages</string> 167 <string name="bt_make_discoverable">Make Discoverable</string> 168 <string name="bt_pick_server">Pick Server</string> 169 <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string> 170 <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string> 171 172 <string name="bt_secure_client">Secure Client</string> 173 <string name="bt_insecure_client">Insecure Client</string> 174 175 <string name="bt_device_picker">Device Picker</string> 176 <string name="bt_paired_devices">Paired Devices</string> 177 <string name="bt_new_devices">New Devices</string> 178 <string name="bt_no_devices">No devices</string> 179 <string name="bt_scan">Scan for Devices</string> 180 <string name="bt_scanning">Scanning...</string> 181 <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> 182 <string name="bt_settings">Bluetooth Settings</string> 183 184 <!-- BLE client side strings --> 185 <string name="ble_client_service_name">Bluetooth LE GATT Client Handler Service</string> 186 <string name="ble_client_test_name">BLE Client Test</string> 187 <string name="ble_client_connect_name">1. BLE Client Connect</string> 188 <string name="ble_discover_service_name">2. BLE Discover Service</string> 189 <string name="ble_client_characteristic_name">3. BLE Read/Write Characteristic</string> 190 <string name="ble_reliable_write_name">4. BLE Reliable Write</string> 191 <string name="ble_notify_characteristic_name">5. BLE Notify Characteristic</string> 192 <string name="ble_client_descriptor_name">6. BLE Read/Write Descriptor</string> 193 <string name="ble_read_rssi_name">7. BLE Read RSSI</string> 194 <string name="ble_client_disconnect_name">8. BLE Client Disconnect</string> 195 <string name="ble_client_test_info">The BLE test must be done simultaneously on two devices. This device is the client. All tests listed here must be done in order.</string> 196 <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> 197 <string name="ble_discover_service_info">Verify that the service is discovered when you press the "Discover Service" button.</string> 198 <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> 199 <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> 200 <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> 201 <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> 202 <string name="ble_client_disconnect_info">Verify that the device is disconnected when you press the "Disconnect" button</string> 203 <string name="ble_address">Bluetooth address</string> 204 <string name="ble_connect">Connect</string> 205 <string name="ble_discover_service">Discover service</string> 206 <string name="ble_write_hint">Nothing to write yet</string> 207 <string name="ble_read_hint">Nothing read yet</string> 208 <string name="ble_write">Write</string> 209 <string name="ble_read">Read</string> 210 <string name="ble_begin_write">Begin write</string> 211 <string name="ble_execute_write">Execute write</string> 212 <string name="ble_begin_notification">Begin notification</string> 213 <string name="ble_stop_notification">Stop notification</string> 214 <string name="ble_waiting_notification">Waiting on notification</string> 215 <string name="ble_read_rssi">Read RSSI</string> 216 <string name="ble_disconnect">Disconnect</string> 217 218 <!-- BLE server side strings --> 219 <string name="ble_server_service_name">Bluetooth LE GATT Server Handler Service</string> 220 <string name="ble_server_start_name">BLE Server Test</string> 221 <string name="ble_server_start_info">The BLE test must be done simultaneously on two devices, a server device and a client device. This device is the server.</string> 222 <string name="ble_server_receiving_connect">Waiting on connection from BLE client.</string> 223 <string name="ble_server_add_service">Adding service to BLE server.</string> 224 <string name="ble_server_write_characteristic">Waiting on write characteristic request</string> 225 <string name="ble_server_read_characteristic">Waiting on read characteristic request</string> 226 <string name="ble_server_write_descriptor">Waiting on write descriptor request</string> 227 <string name="ble_server_read_descriptor">Waiting on read descriptor request</string> 228 <string name="ble_server_reliable_write">Waiting on reliable write from client</string> 229 <string name="ble_server_receiving_disconnect">Waiting on disconnection from BLE client</string> 230 231 <!-- BLE advertiser side strings --> 232 <string name="ble_advertiser_test_name">BLE Advertiser Test</string> 233 <string name="ble_advertiser_test_info">The BLE test must be done simultaneously on two devices, an advertiser and a scanner. This device is the advertiser.</string> 234 <string name="ble_advertiser_service_name">Bluetooth LE Advertiser Handler Service</string> 235 <string name="ble_privacy_mac_name">BLE Privacy Mac</string> 236 <string name="ble_privacy_mac_info">BLE Advertiser should advertise in non-repeating MAC address.</string> 237 <string name="ble_advertiser_privacy_mac_instruction">Click start to start advertising, you can disconnect USB and lock the screen of advertiser. Counts and mac address will show on scanner. You may receive message that this device does not support BLE advertising.</string> 238 <string name="ble_power_level_name">BLE Tx Power Level</string> 239 <string name="ble_power_level_info">BLE Advertiser advertises in 4 different power levels. Scanner should receive them in different strength of Rssi, cannot receive weak signals beyond several feet.</string> 240 <string name="ble_advertiser_power_level_instruction">Click start to start multi-advertising. Data packets are advertised in 4 different power levels. You may receive message that this device does not support multi advertising. If advertiser does not advertise in 4 power levels, neither you receive the error message, you may not stop the advertising in previous test, or this device does not support 4 advertisers at the same time. Try rebooting the device and run the test to free those advertisers in use.</string> 241 <string name="ble_advertiser_scan_filter_name">BLE Hardware Scan Filter</string> 242 <string name="ble_advertiser_scan_filter_info">BLE Advertiser advertises with 2 different data separately. One can wake up the scanner, the other cannot. This test cares about behavior on scanner only.</string> 243 <string name="ble_advertiser_scannable">Scannable advertising</string> 244 <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> 245 <string name="ble_advertiser_unscannable">Unscannble advertising</string> 246 <string name="ble_advertiser_unscannable_instruction">Start unscannable advertising, expect scanner stay calm on Monsoon monitor, no log of GattService from scanner logcat.</string> 247 <string name="ble_advertiser_start">Start</string> 248 <string name="ble_advertiser_stop">Stop</string> 249 250 <!-- BLE scanner side strings --> 251 <string name="ble_scanner_test_name">BLE Scanner Test</string> 252 <string name="ble_scanner_service_name">Bluetooth LE Scanner Handler Service</string> 253 <string name="ble_scanner_test_info">The BLE test must be done simultaneously on two devices, an advertiser and a scanner. This device is the scanner.</string> 254 <string name="ble_scanner_privacy_mac">Hold for 15 min to see if receive a different MAC address from advertiser.</string> 255 <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> 256 <string name="ble_ultra_low">Ultra low</string> 257 <string name="ble_low">Low</string> 258 <string name="ble_medium">Medium</string> 259 <string name="ble_high">High</string> 260 <string name="ble_scanner_power_level_instruction">Count: Ultra low < low < medium < high\nRssi: Ultra low < low < medium < high\nDistance to see count freezing: Ultra low < low < medium < high\nA common error is ultra low, low and medium behave similarly, with similar rssi, freeze at similar distance.\n\n All power level receive a different mac address. After 15 mins, a green text "Get a new Mac address" will show up.</string> 261 <string name="ble_scanner_scan_filter_name">BLE Hardware Scan Filter</string> 262 <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> 263 <string name="ble_scanner_scan_filter_instruction">For 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> 264 <string name="ble_scan_with_filter">Scan with filter</string> 265 <string name="ble_scan_without_filter">Scan without filter</string> 266 267 <!-- Strings for FeatureSummaryActivity --> 268 <string name="feature_summary">Hardware/Software Feature Summary</string> 269 <string name="feature_summary_info">This is a test for...</string> 270 <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string> 271 <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string> 272 <string name="fs_no_data">No data.</string> 273 <string name="fs_legend_good">standard feature reported by device</string> 274 <string name="fs_legend_indeterminate">optional feature not reported by device</string> 275 <string name="fs_legend_warning">non-standard feature reported by device</string> 276 <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string> 277 278 <string name="empty"></string> 279 280 <!-- Strings for Location tests --> 281 <string name="location_gps_test">GPS Test</string> 282 <string name="location_gps_test_info">This test verifies basic GPS behavior 283 and callback scheduling. 284 Make sure the device has line of sight to GPS satellites 285 (for example, outside, or near a window) 286 and then press OK to run the automated tests.</string> 287 288 <!-- Strings for NfcTestActivity --> 289 <string name="nfc_test">NFC Test</string> 290 <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with 291 NFC enabled to exchange messages. One device must be the candidate device running the 292 software build to be tested, while the other device must be an implementation already 293 known to be compatible.\n\nThe Tag Verification tests check that your 294 device can properly read and write to tags of different technologies. The MIFARE 295 Ultralight test is only applicable for devices that support it. 296 \n\nThe Host-based card emulation tests check that your device has properly implemented 297 host-based card emulation. 298 </string> 299 300 <string name="nfc_not_enabled">NFC is not enabled!</string> 301 <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the 302 button below to goto Settings and enable it.</string> 303 <string name="nfc_settings">NFC Settings</string> 304 305 <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string> 306 <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled. 307 Click the button below to goto NFC Sharing Settings and enable it.</string> 308 <string name="ndef_push_settings">NFC Sharing Settings</string> 309 310 <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string> 311 <string name="nfc_ndef_push_sender">NDEF Push Sender</string> 312 <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string> 313 314 <string name="nfc_tag_verification">Tag Verification</string> 315 <string name="nfc_ndef">NDEF</string> 316 <string name="nfc_mifare_ultralight">MIFARE Ultralight</string> 317 318 <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on 319 another device and touch the devices back to back. The receiver should show a 320 dialog indicating it has successfully received the correct message!</string> 321 <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another 322 device running the \"CTS Verifier NDEF Receiver\"...</string> 323 324 <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on 325 another device and touch the devices back to back. The receiver should show a 326 dialog indicating it has successfully received the correct message!</string> 327 <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another 328 device running the \"CTS Verifier NDEF Sender\"...</string> 329 <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push 330 message.</string> 331 <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push 332 message.</string> 333 334 <string name="nfc_tag_verifier">NFC Tag Verifier</string> 335 <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read 336 a tag of the chosen technology.</string> 337 338 <string name="nfc_scan_tag">Place device on a writable %s tag...</string> 339 <string name="nfc_write_tag_title">Writable tag discovered!</string> 340 <string name="nfc_write_tag_message">Press OK to write to this tag...</string> 341 <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string> 342 <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string> 343 <string name="nfc_no_tech">No tag technologies detected...</string> 344 345 <string name="nfc_writing_tag">Writing NFC tag...</string> 346 <string name="nfc_writing_tag_error">Error writing NFC tag...</string> 347 <string name="nfc_reading_tag">Reading NFC tag...</string> 348 <string name="nfc_reading_tag_error">Error reading NFC tag...</string> 349 350 <string name="nfc_result_success">Test passed!</string> 351 <string name="nfc_result_failure">Test failed!</string> 352 353 <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string> 354 <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string> 355 356 <string name="nfc_hce">Host-based card emulation</string> 357 <string name="nfc_hce_reader_tests">HCE reader tests</string> 358 <string name="nfc_hce_emulator_tests">HCE emulator tests</string> 359 <string name="nfc_hce_emulator_test_info">The host-based card emulation 360 tests require two devices to be completed. The HCE emulator tests are used 361 to actually test the host-based card emulation feature of the device-under-test. So the 362 device running the emulator tests must be the candidate device running the software 363 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 364 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 365 and makes sure the device-under-test implements card emulation correctly.</string> 366 <string name="nfc_hce_reader_test_info">The host-based card emulation 367 tests require two devices to be completed. The HCE emulator tests are used 368 to actually test the host-based card emulation feature of the device-under-test. So the 369 device running the emulator tests must be the candidate device running the software 370 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 371 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 372 and makes sure the device-under-test implements card emulation correctly. 373 </string> 374 <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> 375 <string name="nfc_hce_please_wait">Please wait</string> 376 <string name="nfc_hce_setting_up">Setting up card emulation services...</string> 377 378 <string name="nfc_hce_default_route_emulator">Default route (Emulator)</string> 379 <string name="nfc_hce_default_route_reader">Default route (Reader)</string> 380 <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> 381 382 <string name="nfc_hce_protocol_params_emulator">Protocol parameters (Emulator)</string> 383 <string name="nfc_hce_protocol_params_reader">Protocol parameters (Reader)</string> 384 <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> 385 386 <string name="nfc_hce_single_payment_emulator">Single payment (Emulator)</string> 387 <string name="nfc_hce_single_payment_reader">Single payment (Reader)</string> 388 389 <string name="nfc_hce_dual_payment_emulator">Two payment services (Emulator)</string> 390 <string name="nfc_hce_dual_payment_reader">Two payment services (Reader)</string> 391 392 <string name="nfc_hce_change_default_emulator">Change default payment service (Emulator)</string> 393 <string name="nfc_hce_change_default_reader">Change default payment service (Reader)</string> 394 395 <string name="nfc_hce_tap_reader_title">Tap reader</string> 396 <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> 397 398 <string name="nfc_hce_single_non_payment_emulator">Single non-payment (Emulator)</string> 399 <string name="nfc_hce_single_non_payment_reader">Single non-payment (Reader)</string> 400 401 <string name="nfc_hce_dual_non_payment_emulator">Two non-payment services (Emulator)</string> 402 <string name="nfc_hce_dual_non_payment_reader">Two non-payment services (Reader)</string> 403 404 <string name="nfc_hce_conflicting_non_payment_emulator">Two conflicting non-payment services (Emulator)</string> 405 <string name="nfc_hce_conflicting_non_payment_reader">Two conflicting non-payment services (Reader)</string> 406 407 <string name="nfc_hce_foreground_non_payment_emulator">Foreground override non-payment services (Emulator)</string> 408 <string name="nfc_hce_foreground_non_payment_reader">Foreground override non-payment services (Reader)</string> 409 <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> 410 411 <string name="nfc_hce_foreground_payment_emulator">Foreground override payment services (Emulator)</string> 412 <string name="nfc_hce_foreground_payment_reader">Foreground override payment services (Reader)</string> 413 <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> 414 <string name="nfc_hce_change_favor_foreground">This test requires the "Favor foreground app" setting to be enabled. Tap OK to go to Tap and Pay settings and check the Favor foreground app option</string> 415 <string name="nfc_hce_offhost_service_emulator">Off-host service (Emulator)</string> 416 <string name="nfc_hce_offhost_service_reader">Off-host service (Reader)</string> 417 <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> 418 419 <string name="nfc_hce_on_and_offhost_service_emulator">On and off-host services (Emulator)</string> 420 <string name="nfc_hce_on_and_offhost_service_reader">On and off-host services (Reader)</string> 421 <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> 422 423 <string name="nfc_hce_tap_test_emulator">50 successful taps test (Emulator)</string> 424 <string name="nfc_hce_tap_test_reader">50 successful taps test (Reader)</string> 425 <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> 426 <string name="nfc_hce_throughput_emulator">HCE throughput test (Emulator)</string> 427 <string name="nfc_hce_throughput_reader">HCE throughput test (Reader)</string> 428 <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> 429 <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> 430 <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> 431 <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> 432 433 <string name="nfc_hce_payment_dynamic_aids_emulator">Dynamic payment AIDs (Emulator)</string> 434 <string name="nfc_hce_payment_dynamic_aids_reader">Dynamic payment AIDs (Reader)</string> 435 <string name="nfc_hce_payment_dynamic_aids_help">This test tries to register dynamic AIDs for a payment service.</string> 436 437 <string name="nfc_hce_payment_prefix_aids_emulator">Payment prefix AIDs (Emulator)</string> 438 <string name="nfc_hce_payment_prefix_aids_reader">Payment prefix AIDs (Reader)</string> 439 <string name="nfc_hce_payment_prefix_aids_help">This test statically registers prefix AIDs for a payment service.</string> 440 441 <string name="nfc_hce_payment_prefix_aids_emulator_2">Payment prefix AIDs 2 (Emulator)</string> 442 <string name="nfc_hce_payment_prefix_aids_reader_2">Payment prefix AIDs 2 (Reader)</string> 443 444 <string name="nfc_hce_other_prefix_aids_emulator">Other prefix AIDs (Emulator)</string> 445 <string name="nfc_hce_other_prefix_aids_reader">Other prefix AIDs (Reader)</string> 446 <string name="nfc_hce_other_prefix_aids_help">This test dynamically registers prefix AIDs for a non-payment service.</string> 447 448 <string name="nfc_hce_other_conflicting_prefix_aids_emulator">Conflicting non-payment prefix AIDs (Emulator)</string> 449 <string name="nfc_hce_other_conflicting_prefix_aids_reader">Conflicting non-payment prefix AIDs (Reader)</string> 450 <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> 451 452 <string name="nfc_payment_service_desc">NFC Payment service</string> 453 <string name="ppse">PPSE</string> 454 <string name="mastercard">MasterCard</string> 455 <string name="visa">Visa</string> 456 <string name="paymentService1">Payment Service #1</string> 457 <string name="paymentService2">Payment Service #2</string> 458 <string name="transportService1">TransportService #1</string> 459 <string name="transportService2">TransportService #2</string> 460 <string name="accessService">AccessService</string> 461 <string name="offhostService">OffhostService</string> 462 463 <!-- Strings for Sensor Test Activities --> 464 <string name="snsr_device_admin_receiver">Sensor Tests Device Admin Receiver</string> 465 <string name="snsr_test_summary">Tests passed: %1$d, Tests skipped: %2$d, Tests failed: %3$d</string> 466 <string name="snsr_test_complete">Test completed without errors.</string> 467 <string name="snsr_test_complete_with_errors">Test completed with errors: those errors 468 might degrade the user experience and might cause some applications to misbehave. They are 469 not required for Android Compatibility at this time, but will in a future release.</string> 470 <string name="snsr_test_pass">PASS</string> 471 <string name="snsr_test_skipped">SKIPPED</string> 472 <string name="snsr_test_fail">FAIL</string> 473 <string name="snsr_execution_time">Test execution time %1$s sec</string> 474 475 <!-- Strings to interact with users in Sensor Tests --> 476 <string name="snsr_test_play_sound">A sound will be played once the verification is complete...</string> 477 <string name="snsr_no_interaction">Leave the device on top of a flat surface.</string> 478 <string name="snsr_interaction_needed">Once the test begins, you will have to wave your hand over the front of the device.</string> 479 <string name="snsr_device_steady">Keep the device steady.</string> 480 <string name="snsr_keep_device_rotating_clockwise">Once the test begins, you will have to keep rotating the device clockwise.</string> 481 <string name="snsr_wait_for_user">Press \'Next\' to continue.</string> 482 <string name="snsr_wait_to_begin">Press \'Next\' to begin.</string> 483 <string name="snsr_on_complete_return">After completing the task, go back to this test.</string> 484 <string name="snsr_movement_expected">Movement was expected during the test. Found=%1$b.</string> 485 <string name="snsr_sensor_feature_deactivation">Turn off any special features installed in the 486 device that register for sensors. Once you are done, you can begin the test.</string> 487 <string name="snsr_setting_mode_request">You will be redirected to set \'%1$s\' to: %2$s.</string> 488 <string name="snsr_setting_mode_set">\'%1$s\' set to: %2$s.</string> 489 <string name="snsr_setting_mode_not_set">\'%1$s\' not set to: %2$s.</string> 490 <string name="snsr_setting_airplane_mode">Airplane mode</string> 491 <string name="snsr_setting_screen_brightness_mode">Adaptive Brightness</string> 492 <string name="snsr_setting_auto_rotate_screen_mode">Auto-rotate screen</string> 493 <string name="snsr_setting_keep_screen_on">Stay awake</string> 494 <string name="snsr_setting_location_mode">Location</string> 495 <string name="snsr_setting_ambient_display">Ambient Display</string> 496 <string name="snsr_pass_on_error">Pass Anyway</string> 497 <string name="snsr_run_automated_tests">The screen will be turned off to execute the tests, 498 when tests complete, the device will vibrate and the screen will be turned back on.</string> 499 500 <!-- Accelerometer --> 501 <string name="snsr_accel_test">Accelerometer Test</string> 502 <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> 503 <string name="snsr_accel_m_test">Accelerometer Measurement Tests</string> 504 <string name="snsr_accel_test_face_up">Place the device on a flat surface with the screen 505 facing the ceiling.</string> 506 <string name="snsr_accel_test_face_down">Place the device on a flat surface with the screen 507 facing it.</string> 508 <string name="snsr_accel_test_right_side">Place the device in a flat surface resting vertically 509 on its right side.</string> 510 <string name="snsr_accel_test_left_side">Place the device in a flat surface resting vertically 511 on its left side.</string> 512 <string name="snsr_accel_test_top_side">Place the device in a flat surface resting vertically 513 on its top side.</string> 514 <string name="snsr_accel_test_bottom_side">Place the device in a flat surface resting vertically 515 on its bottom side.</string> 516 517 <!-- Gyroscope --> 518 <string name="snsr_gyro_test">Gyroscope Test</string> 519 <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> 520 <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string> 521 <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string> 522 <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> 523 <string name="snsr_gyro_test_degrees_title">Wrong units?</string> 524 <string name="snsr_gyro_test_degrees_message">These values looks like degrees per second. These should be radians per second!</string> 525 <string name="snsr_gyro_m_test">Gyroscope Measurement Test</string> 526 <string name="snsr_gyro_device_placement">Place the device in a flat surface with the screen 527 facing the ceiling. Read the instructions for each scenario, before you perform the 528 test.</string> 529 <string name="snsr_gyro_device_static">Leave the device static.</string> 530 <string name="snsr_gyro_rotate_device">Once you begin the test, you will need to rotate the 531 device 360deg (one time) in the direction show by the animation, then place it back on the 532 flat surface.</string> 533 534 <!-- Heart Rate --> 535 <string name="snsr_heartrate_test">Heart Rate Test</string> 536 <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> 537 <string name="snsr_heartrate_test_no_heartrate_title">No heart rate monitor?</string> 538 <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> 539 540 <!-- Magnetic Field --> 541 <string name="snsr_mag_m_test">Magnetic Field Measurement Tests</string> 542 <string name="snsr_mag_verify_norm">Verifying the Norm...</string> 543 <string name="snsr_mag_verify_std_dev">Verifying the Standard Deviation...</string> 544 <string name="snsr_mag_verify_calibrated_uncalibrated">Verifying the relationship between 545 calibrated and uncalibrated measurements...</string> 546 <string name="snsr_mag_calibration_description">Please calibrate the Magnetometer by moving 547 it in 8 shapes in different orientations.</string> 548 <string name="snsr_mag_calibration_complete">When done, leave the device in a flat surface, far 549 from all metallic objects (if the test does not pass, try re-running it outdoors).</string> 550 <string name="snsr_mag_measurement">-> (%1$.2f, %2$.2f, %3$.2f) : %4$.2f uT</string> 551 552 <!-- Sensor Value Accuracy --> 553 <string name="snsr_rot_vec_test">Rotation Vector Accuracy Test</string> 554 <string name="snsr_event_length">Sensor(%3$s). Event values expected to have size=%1$d. Found=%2$d.</string> 555 <string name="snsr_event_value">Sensor(%3$s). Event value[0] expected to be of value=%1$f. Found=%2$f.</string> 556 <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> 557 558 <!-- Sensor Batching --> 559 <string name="snsr_batch_test">Sensor Batching Tests</string> 560 <string name="snsr_batching_walking_needed">Once the test begins, you will have to take the 561 device in your hand and walk.</string> 562 563 <!-- Sensor Synchronization --> 564 <string name="snsr_synch_test">Sensor Synchronization Test</string> 565 566 <!-- Step Counter and Detector --> 567 <string name="snsr_step_counter_test">Step Counter and Detector Tests</string> 568 <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> 569 <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> 570 <string name="snsr_step_counter_expected_steps">At least %1$d steps are expected to be reported. Reported=%2$d.</string> 571 <string name="snsr_step_counter_detected_reported">Steps reported by user=%1$d. Steps counted=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 572 <string name="snsr_step_detector_detected_reported">Steps reported by user=%1$d. Steps detected=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 573 <string name="snsr_step_counter_event_changed">Step counter expected to increase monotonically, with a delta > 0. Found=%1$d. Timestamp=%2$d.</string> 574 <string name="snsr_step_reported">%1$d | User reported step.</string> 575 <string name="snsr_step_counter_event">%1$d | Step Counter event. count=%2$d.</string> 576 <string name="snsr_step_detector_event">%1$d | Step Detector event.</string> 577 578 <!-- Significant Motion --> 579 <string name="snsr_significant_motion_test">Significant Motion Tests</string> 580 <string name="snsr_significant_motion_event_arrival">Event expected to trigger. Triggered=%1$s.</string> 581 <string name="snsr_significant_motion_event_type">Event expected to be of type=%1$d. Found=%2$d.</string> 582 <string name="snsr_significant_motion_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string> 583 <string name="snsr_significant_motion_disable_info">Significant Motion is expected to disable itself after it triggers once.</string> 584 <string name="snsr_significant_motion_test_trigger">Once you begin the test, you will need to walk for Significant Motion to be detected.</string> 585 <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> 586 <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> 587 <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> 588 <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> 589 <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> 590 <string name="snsr_significant_motion_registration">Expected to be able to register for TriggerSensor. Found=%1$b.</string> 591 <string name="snsr_significant_motion_cancelation">Expected to be able to cancel TriggerSensor. Found=%b.</string> 592 593 <!-- Strings for Sensor CTS tests inside CtsVerifier --> 594 <string name="snsr_single_sensor_tests">CTS Single Sensor Tests</string> 595 <string name="snsr_sensor_integration_tests">CTS Sensor Integration Tests</string> 596 <string name="snsr_sensor_test">CTS Sensor Test</string> 597 <string name="snsr_sensor_batching_tests">CTS Sensor Batching Tests</string> 598 599 <!-- Strings for Sample Test Activities --> 600 <string name="share_button_text">Share</string> 601 <string name="sample_framework_test">Sample Framework Test</string> 602 <string name="sample_test">Sample Test</string> 603 <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> 604 605 <!-- Strings for SuidFilesActivity --> 606 <string name="suid_files">SUID File Scanner</string> 607 <string name="suid_files_info">This test will attempt to find unauthorized SUID binaries, but it is not comprehensive due to permission restrictions.\n\nAuthorized SUID binaries will appear green, while unauthorized SUID binaries will appear red.\n\nPress OK to start the scan...</string> 608 <string name="scanning_directory">Scanning directory...</string> 609 <string name="file_status">User: %1$s\nGroup: %2$s\nPermissions: %3$s\nPath: %4$s</string> 610 <string name="no_file_status">Could not stat file...</string> 611 <string name="congratulations">Congratulations!</string> 612 <string name="no_suid_files">No unauthorized suid files detected!</string> 613 614 <!-- Strings for Camera Analyzer --> 615 <string name="camera_analyzer">Camera Analyzer</string> 616 <string name="ca_find_checkerboard_label">Find target</string> 617 <string name="ca_check_formats_label">Output formats</string> 618 <string name="ca_exposure_test_label">Exposure Comp.</string> 619 <string name="ca_result_label">Results will be here</string> 620 <string name="ca_wb_test_label">White Balance</string> 621 <string name="ca_lock_test_label">AE Lock</string> 622 <string name="ca_metering_label">Metering Area</string> 623 <string name="ca_focus_modes_label">Focus Modes</string> 624 <string name="ca_info">This test checks the image quality of the camera of this device. It requires a MacBeth 4x6 color checker. With an ADK board and a lamp connected to it on the Relay 1 port, all tests can be run automatically. Without the ADK board, all the tests except the Auto Exposure Lock Test can be run automatically and the Auto Exposure Lock Test will require users to turn on/off a lamp according to the instruction given. </string> 625 626 <!-- Strings for Camera Orientation --> 627 <string name="camera_orientation">Camera Orientation</string> 628 <string name="co_info">This test verifies the orientation capabilities of 629 camera preview and capture.\n - The left view shows a preview window rotated 630 clockwise by a given magnitude of degrees.\n - The right view, after taking 631 a photo, shows the captured image.\n - For each camera and orientation, both 632 the left and right views should appear rotated clockwise by the amount of 633 degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose 634 \"Fail\".\n - For front-facing cameras, the test will horizontally mirror 635 the captured image prior to rotation, in attempt to make the left and right 636 views appear the same.\n - The physical orientation of the device does not 637 matter.\n - Read the message above the \"Take Photo\" button for 638 step-by-step instructions. 639 </string> 640 <string name="co_preview_label">Camera preview</string> 641 <string name="co_format_label">Oriented photo</string> 642 <string name="co_camera_label">Camera:</string> 643 <string name="co_orientation_label">Orientation</string> 644 <string name="co_orientation_direction_label">clockwise</string> 645 <string name="co_instruction_heading_label">Instruction:</string> 646 <string name="co_instruction_text_photo_label">Take a photo</string> 647 <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> 648 <string name="co_instruction_text_extra_label">(mirrored horizontally prior to rotation, since camera is front-facing)</string> 649 <string name="co_photo_button_caption">Take Photo</string> 650 651 <!-- Strings for Camera Intents --> 652 <string name="camera_intents">Camera Intents</string> 653 <string name="ci_info"> 654 This test verifies that the default camera app is firing intents 655 after pictures/videos are taken. It also verifies that when the 656 default camera app is invoked via intents, the launch intents work, 657 and the broadcast intents are received when appropriate per the SDK 658 documentation.\n\n 659 - Read the message above the \"Start Test\" button for 660 step-by-step instructions. 661 </string> 662 <string name="ci_preview_label">Camera preview</string> 663 <string name="ci_format_label">Oriented photo</string> 664 <string name="ci_camera_label">Camera:</string> 665 <string name="ci_intents_label">Intents Test</string> 666 <string name="ci_intents_direction_label">clockwise</string> 667 <string name="ci_instruction_heading_label">Instructions:</string> 668 <string name="ci_instruction_text_photo_label">READ BEFORE STARTING TEST</string> 669 <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> 670 <string name="ci_instruction_text_app_picture_label">\n 671 1. Click Start Test. \n 672 2. Go to home screen (HOME key). \n 673 3. Launch Camera application. \n 674 4. Capture photo. \n 675 5. Return to CTS verifier app. \n 676 6. Pass button will light up if intent was received.\n 677 7. Click "Pass" if possible. 678 </string> 679 <string name="ci_instruction_text_app_video_label">\n 680 1. Click Start Test. \n 681 2. Go to home screen (HOME key). \n 682 3. Launch Camera application. \n 683 4. Capture video. \n 684 5. Return to CTS verifier app. \n 685 6. Pass button will light up if intent was received.\n 686 7. Click "Pass" if possible. 687 </string> 688 <string name="ci_instruction_text_intent_picture_label">\n 689 1. Click Start Test.\n 690 2. Camera app will launch, prompting to take photo.\n 691 3. Capture/confirm photo using camera app controls.\n 692 4. Pass button will light up if intent was NOT received.\n 693 5. Click "Pass" if possible. 694 </string> 695 <string name="ci_instruction_text_intent_video_label">\n 696 1. Click Start Test.\n 697 2. Camera app will launch, prompting to take video.\n 698 3. Capture/confirm video using camera app controls.\n 699 4. Pass button will light up if intent was received.\n 700 5. Click "Pass" if possible. 701 </string> 702 <string name="ci_start_test_button_caption">Start Test</string> 703 704 <!-- Strings for Camera Formats --> 705 <string name="camera_format">Camera Formats</string> 706 <string name="cf_info">This test checks that all the supported 707 output formats for camera preview callbacks work correctly, and 708 that the mandatory formats are available. \n - The left view shows 709 a standard preview window. \n - The right view shows the output 710 processed from camera preview callbacks. \n - For each camera, 711 resolution, and format combination in the dropdowns, the right 712 view should look the same as the left, and neither should have 713 streaks, lines, or other artifacts. \n - For front-facing cameras, 714 the right view must be horizontally mirrored relative to the left 715 view.\n - Note that the frame rate of the right view may be much 716 lower than on the left; this is not an indication of a failed 717 test. 718 </string> 719 <string name="cf_preview_label">Normal preview</string> 720 <string name="cf_format_label">Processed callback data</string> 721 722 <!-- Strings for Camera Video --> 723 <string name="record_button_text">Test</string> 724 <string name="camera_video">Camera Video</string> 725 <string name="video_info"> This test checks video capture 726 at different resolutions. \n - The left view window shows the preview. 727 \n - Pressing the test button will trigger three 728 seconds of video recording. Playback will show up in the right view 729 window after recording is complete. \n - Use the spinners to choose 730 camera and resolution combinations. The playback should be similar 731 to what you saw in preview. \n - After all possible combinations 732 are tested, the pass button will be enabled. You may press the pass 733 button to indicate a pass. \n - You may press fail button any time during 734 the test to indicate failure. 735 </string> 736 <string name="video_capture_label">Video capture</string> 737 <string name="video_playback_label">Video playback</string> 738 <string name="dialog_fail_test">Test failed</string> 739 <string name="fail_quit">Fail and quit</string> 740 <string name="cancel">Cancel</string> 741 <string name="status_ready">Ready</string> 742 <string name="status_recording">Recording</string> 743 <string name="status_playback">Playing back</string> 744 745 <!-- Strings for USB accessory test activity --> 746 <string name="usb_accessory_test">USB Accessory Test</string> 747 <string name="sensor_power_test">Sensor Power Test</string> 748 <string name="usb_accessory_test_info"> 749 1. Connect your Android device to a computer and run the \'cts-usb-accessory\' program 750 included with the CTS Verifier bundle. 751 \n\n2. If you have not started the CTS Verifier, press \'OK\' when asked to open the CTS 752 Verifier when the accessory is connected. \n\nIf you are already in this test, 753 then you can press \'Cancel\' but press \'OK\' in the next dialog asking whether to allow 754 CTS Verifier to access the accessory. 755 \n\n3. You should see the accessory and the CTS Verifier display a series of messages 756 which indicates that the accessory support is working properly. 757 </string> 758 <string name="usb_not_available_title">USB accessory feature is not available?</string> 759 <string name="usb_not_available_message">If your device is supposed to support USB accessories, your API implementation is not behaving correctly!</string> 760 <string name="usb_received_messages">Received Messages</string> 761 <string name="usb_sent_messages">Sent Messages</string> 762 <string name="usb_no_messages">No messages</string> 763 <string name="usb_message_thread_started">Starting message processing...</string> 764 <string name="usb_message_thread_exception">Exception occurred while processing a message...</string> 765 <string name="usb_message_thread_ended">Stopping message processing...</string> 766 <string name="usb_test_passed">Received all expected messages. Pass button enabled!</string> 767 <string name="usb_file_descriptor_error">Could not open file descriptor for USB accessory... try reconnecting and restarting the accessory?</string> 768 769 <!-- Strings for StreamingVideoActivity --> 770 <string name="streaming_video">Streaming Video Quality Verifier</string> 771 <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> 772 <string name="sv_no_data">No videos.</string> 773 <string name="sv_failed_title">Test Failed</string> 774 <string name="sv_failed_message">Unable to play stream. See log for details.</string> 775 776 <!-- Strings for P2pTestActivity --> 777 <string name="p2p_test">Wi-Fi Direct Test</string> 778 <string name="p2p_test_info"> 779 The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange 780 messages. One device must be the candidate device running the software build to 781 be tested, while the other device must be an implementation already known to be 782 compatible.\n\nOne device should start the requester test, and the other should 783 start the responder test. Your device must pass both requester and responder 784 tests. 785 </string> 786 <string name="p2p_group_formation">Group Formation</string> 787 <string name="p2p_join">Group Join</string> 788 <string name="p2p_service_discovery">Service Discovery</string> 789 790 <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string> 791 <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string> 792 <string name="p2p_group_owner_test">Group Owner Test</string> 793 <string name="p2p_group_client_test">Group Client Test</string> 794 <string name="p2p_service_discovery_responder_test"> 795 Service Discovery Responder Test</string> 796 <string name="p2p_service_discovery_requester_test"> 797 Service Discovery Requester Test</string> 798 799 <string name="p2p_go_neg_responder">GO Negotiation Responder</string> 800 <string name="p2p_go_neg_requester">GO Negotiation Requester</string> 801 <string name="p2p_accept_client">Group Owner</string> 802 <string name="p2p_join_go">Group Client</string> 803 <string name="p2p_service_discovery_responder">Service Discovery Responder</string> 804 <string name="p2p_service_discovery_requester">Service Discovery Requester</string> 805 806 <string name="p2p_go_neg_responder_info"> 807 Start the \"GO Negotiation Requester Test\" on the other device and follow 808 the instructions.</string> 809 <string name="p2p_accept_client_info"> 810 Start the \"Group Client Test\" on the other device and follow 811 the instructions.</string> 812 <string name="p2p_service_discovery_responder_info"> 813 Start the \"Service Discovery Requester Test\" on the other device and follow 814 the instructions.</string> 815 816 <string name="p2p_go_neg_requester_info"> 817 Start the \"GO Negotiation Responder Test\" on the other device. 818 Then run each test individually by clicking on it\'s name.</string> 819 <string name="p2p_join_go_info"> 820 Start the \"Group Owner Test\" on the other device. 821 Then run each test individually by clicking on it\'s name.</string> 822 <string name="p2p_service_discovery_requester_info"> 823 Start the \"Service Discovery Responder Test\" on the other device. 824 Then run each test individually by clicking on it\'s name.</string> 825 826 <string name="p2p_not_enabled">Wi-Fi is not enabled</string> 827 <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled. 828 Click the button below to go to system settings and enable Wi-Fi.</string> 829 <string name="p2p_settings">Wi-Fi Direct Settings</string> 830 831 <string name="p2p_result_success">Test passed successfully.</string> 832 833 <string name="p2p_go_neg_responder_ready"> 834 The go negotiation responder is now ready to start. Start 835 the \"GO Negotiation Requester Test\" on the other device. 836 Keep the screen here until all tests on the other device are 837 finished.</string> 838 <string name="p2p_go_ready"> 839 The group owner is now ready to start. Start the \"Join 840 Group Test\" on the other device. 841 Keep the screen here until all tests on the other device are 842 finished.</string> 843 <string name="p2p_service_responder_ready"> 844 The service responder is now ready to start. Start the 845 \"Service Discovery Requester Test\" on the other device. 846 Keep the screen here until all tests on the other device are 847 finished.</string> 848 849 <string name="p2p_setup_error"> 850 Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string> 851 <string name="p2p_unexpected_error"> 852 Test failed.\n\nUnexpected error. Check logcat.</string> 853 <string name="p2p_add_local_service_error"> 854 Test failed.\n\nFailed to add local service.</string> 855 <string name="p2p_add_service_request_error"> 856 Test failed.\n\nFailed to add service request.</string> 857 <string name="p2p_remove_service_request_error"> 858 Test failed.\n\nFailed to remove service request.</string> 859 <string name="p2p_clear_service_requests_error"> 860 Test failed.\n\nFailed to clear service requests.</string> 861 <string name="p2p_connect_error"> 862 Test failed.\n\nFailed to start a p2p connection to the target device.</string> 863 <string name="p2p_remove_group_error"> 864 Test failed.\n\nFailed to remove a p2p group.</string> 865 <string name="p2p_discover_peers_error"> 866 Test failed.\n\nFailed to discover peers.</string> 867 <string name="p2p_discover_services_error"> 868 Test failed.\n\nFailed to discover services.</string> 869 <string name="p2p_ceate_group_error"> 870 Test failed.\n\nFailed to start up group owner.</string> 871 <string name="p2p_no_service_requests_error"> 872 Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string> 873 <string name="p2p_receive_invalid_response_error"> 874 Test failed.\n\nReceived an invalid message or could not receive 875 the expected message.\n\n</string> 876 <string name="p2p_target_not_found_error">Test failed.\n\n 877 The target responder device was NOT found. Start up the responder 878 test on the other device, then run the test again.</string> 879 <string name="p2p_target_invalid_role_error">Test failed.\n\n 880 The target responder must be p2p device. However, the target responder 881 device was group owner. Check the test case on the other device.</string> 882 <string name="p2p_target_invalid_role_error2">Test failed.\n\n 883 The target responder must be group owner. However, the target responder 884 device was p2p device. Check the test case on the other device.</string> 885 <string name="p2p_connection_error"> 886 Test failed.\n\nFailed to establish a p2p connection.</string> 887 <string name="p2p_detect_disconnection_error"> 888 Test failed.\n\nFailed to detect client disconnection.</string> 889 <string name="p2p_disconnect_error"> 890 Test failed.\n\nFailed to disconnect a p2p connection.</string> 891 892 <string name="p2p_search_target">Search Target</string> 893 <string name="p2p_searching_target">Searching for target device ...</string> 894 <string name="p2p_checking_serv_capab">Checking the service discovery 895 capability ...</string> 896 <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n 897 Click the \"OK\" button on the other device to accept the connection 898 request from this device.</string> 899 <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n 900 Enter the pin number on the other device.</string> 901 <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to 902 connect ...</string> 903 <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer 904 to disconnect ...</string> 905 906 <string name="camera_fov_calibration">Camera FOV Calibration</string> 907 <string name="camera_fov_calibration_done">Done</string> 908 <string name="camera_fov_general_settings">General settings</string> 909 <string name="camera_fov_label_options">Settings</string> 910 <string name="camera_fov_tap_to_take_photo">Tap to calibrate</string> 911 <string name="camera_fov_marker_distance">Marker distance (in cm)</string> 912 <string name="camera_fov_marker_distance_description">The distance in centimeters between 913 the solid lines on the target pattern.</string> 914 <string name="camera_fov_target_distance">Target distance (in cm)</string> 915 <string name="camera_fov_target_distance_description">The distance in centimeters from the 916 device to the target pattern.</string> 917 <string name="camera_fov_settings_button_text">Setup</string> 918 <string name="camera_fov_change_preview_sizes_button_text">Preview Sizes</string> 919 <string name="camera_fov_choose_preview_size_for_camera">Choose preview size for camera %1$s</string> 920 <string name="camera_fov_displayed_fov_label">Displayed FOV : </string> 921 <string name="camera_fov_reported_fov_label">Reported FOV : </string> 922 <string name="camera_fov_reported_fov_problem">Reported FOV problem</string> 923 <string name="camera_fov_reported_fov_problem_message">The reported FOV before takePicture() is 924 different from when onPictureTaken() is called.\nAs picture size has not been changed, the 925 reported FOV should be identical at both times.\n\nFOV before/after: %1$f / %2$f</string> 926 927 <string name="camera_fov_panorama_wallpaper_title">Photo Sphere Live Wallpaper</string> 928 <string name="camera_fov_panorama_wallpaper_description">This live wallapper displays photo 929 spheres.</string> 930 <string name="camera_fov_select_panorama">Select panorama</string> 931 <string name="camera_fov_select_panorama_description">Select a panorama to display in the 932 live wallpaper.</string> 933 <string name="camera_fov_reset_panorama">Reset panorama</string> 934 <string name="camera_fov_reset_panorama_description">Resets the panorama to show the demo 935 file.</string> 936 <string name="camera_fov_enable_compass_mode">Enable compass mode</string> 937 <string name="camera_fov_enable_compass_mode_description">If enabled, the panorama orients 938 itself according to the current rotation of the device.</string> 939 940 <string name="test_category_notifications">Notifications</string> 941 <string name="attention_test">Notification Attention Management Test</string> 942 <string name="attention_info">This test checks that the NotificationManagerService is 943 respecting user preferences about notification ranking and filtering. 944 </string> 945 <string name="attention_ready">I\'m done</string> 946 <string name="attention_filter_all">Please set the notification filter to \"All\" in the dialog 947 that appears when you change the device\'s volume.</string> 948 <string name="attention_filter_priority">Please set the notification filter to \"Priority\" in 949 the dialog that appears when you change the device\'s volume, and allow messages from 950 starred contacts.</string> 951 <string name="attention_filter_none">Please set the notification filter to \"None\" in the dialog 952 that appears when you change the device\'s volume.</string> 953 <string name="attention_create_contacts">Create contacts for notification annotations.</string> 954 <string name="attention_delete_contacts">Delete test contacts.</string> 955 <string name="attention_default_order">Check that ranker defaults to time order.</string> 956 <string name="attention_priority_order">Check that ranker respects developers priorities.</string> 957 <string name="attention_ambient_bit">Check that the ambient bit is set appropriately.</string> 958 <string name="attention_lookup_order">Check that ranker respects Lookup URIs for contacts.</string> 959 <string name="attention_email_order">Check that ranker respects mailto URIs for contacts.</string> 960 <string name="attention_phone_order">Check that ranker respects telephone URIs for contacts.</string> 961 <string name="attention_interruption_order">Check that ranker temporarily boosts interruptions. 962 This test takes 15 seconds to complete.</string> 963 <string name="attention_none_are_filtered">Check that \"All\" mode doesn\'t filter any notifications.</string> 964 <string name="attention_some_are_filtered">Check that \"Priority\" mode doesn\'t filter priority notifications.</string> 965 <string name="attention_all_are_filtered">Check that \"None\" mode filters all notifications.</string> 966 <string name="nls_test">Notification Listener Test</string> 967 <string name="nls_service_name">Notification Listener for CTS Verifier</string> 968 <string name="nls_info">This test checks that a NotificationListenerService can be enabled 969 and disabled, and that once enabled the service is able to receive notifications and 970 dismiss them. 971 </string> 972 <string name="nls_enable_service">Please enable \"Notification Listener for CTS Verifier\" 973 under Security > Notification Access and return here.</string> 974 <string name="nls_disable_service">Please disable \"Notification Listener for CTS Verifier\" 975 under Security > Notification Access and return here.</string> 976 <string name="nls_start_settings">Launch Settings</string> 977 <string name="nls_service_started">Service should start once enabled.</string> 978 <string name="nls_note_received">Check that notification was received.</string> 979 <string name="nls_payload_intact">Check that notification payload was intact.</string> 980 <string name="nls_clear_one">Check that service can clear a notification.</string> 981 <string name="nls_clear_all">Check that service can clear all notifications.</string> 982 <string name="nls_service_stopped">Service should stop once disabled.</string> 983 <string name="nls_note_missed">Check that notification was not received.</string> 984 985 <string name="location_mode_high_accuracy_test">High Accuracy Mode Test</string> 986 <string name="location_mode_high_accuracy_info"> 987 This test checks that the Location Mode API is consistent with the 988 Location Provider API when the device is in High Accuracy location mode. 989 </string> 990 <string name="location_mode_select_high_accuracy"> 991 Please select the \"High accuracy\" mode at Settings > Location and return here. 992 </string> 993 <string name="location_mode_battery_saving_test">Battery Saving Mode Test</string> 994 <string name="location_mode_battery_saving_info"> 995 This test checks that the Location Mode API is consistent with the 996 Location Provider API when the device is in Battery Saving location mode. 997 </string> 998 <string name="location_mode_select_battery_saving"> 999 Please select the \"Battery Saving\" mode at Settings > Location and return here. 1000 </string> 1001 <string name="location_mode_device_only_test">Device Only Mode Test</string> 1002 <string name="location_mode_device_only_info"> 1003 This test checks that the Location Mode API is consistent with the 1004 Location Provider API when the device is in Device Only location mode. 1005 </string> 1006 <string name="location_mode_select_device_only"> 1007 Please select the \"Device Only\" mode at 1008 Settings > Location and return here. 1009 </string> 1010 <string name="location_mode_off_test">Location Mode Off Test</string> 1011 <string name="location_mode_off_info"> 1012 This test checks that the Location Mode API is consistent with the 1013 Location Provider API when the device is in the Off location mode. 1014 </string> 1015 1016 <string name="location_mode_start_settings">Launch Settings</string> 1017 <string name="location_mode_turn_on"> 1018 Please turn ON location access (the switch at the top of Settings > Location) 1019 and return here. 1020 </string> 1021 <string name="location_mode_turn_off"> 1022 Please turn OFF location access (the switch at the top of Settings > Location) 1023 and return here. 1024 </string> 1025 <string name="location_mode_secure_gps_on">GPS provider should be ON in secure settings.</string> 1026 <string name="location_mode_secure_gps_off">GPS provider should be OFF in secure settings.</string> 1027 <string name="location_mode_secure_nlp_on">Network location provider should be ON in secure settings.</string> 1028 <string name="location_mode_secure_nlp_off">Network location provider should be OFF in secure settings.</string> 1029 <string name="location_mode_manager_gps_on">GPS provider should be ON in LocationManager.</string> 1030 <string name="location_mode_manager_gps_off">GPS provider should be OFF in LocationManager.</string> 1031 <string name="location_mode_manager_nlp_on">Network location provider should be ON in LocationManager.</string> 1032 <string name="location_mode_manager_nlp_off">Network location provider should be OFF in LocationManager.</string> 1033 1034 <string name="cacert_test">CA Cert Notification Test</string> 1035 <string name="cacert_info">This test checks that when a CA Certificate is installed, the user is notified.</string> 1036 <string name="cacert_do_something">Do it</string> 1037 <string name="cacert_done">Done</string> 1038 <string name="cacert_install_cert">Use the CertInstaller to install the certificate. When it opens, just tap "Okay". If this button does nothing, pass the test and move on.</string> 1039 <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> 1040 <string name="cacert_check_notification">Please look at the new notification and confirm: It say the network may be monitored. Tapping it brings up a more detailed explanation and a button to check trusted credentials. Tapping that button brings up the Trusted Credentials page you just visited.</string> 1041 <string name="cacert_dismiss_notification">Dismiss the notification. If it cannot be dismissed, fail the test.</string> 1042 1043 <string name="caboot_test">CA Cert Notification on Boot test</string> 1044 <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> 1045 <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> 1046 <string name="caboot_check_creds">Check Credentials</string> 1047 <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> 1048 <string name="caboot_install_cert">Install credential</string> 1049 <string name="caboot_reboot_desc">Please reboot the device and return to this test.</string> 1050 <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> 1051 1052 <!-- Strings for Widget --> 1053 <string name="widget_framework_test">Widget Framework Test</string> 1054 <string name="widget_framework_test_info">This test checks some basic features of the widget 1055 framework. In order to perform the test, press the Home button. Add the widget 1056 titled "CTS Verifier" to the home screen. Follow the instructions in the widget.</string> 1057 <string name="widget_name">Widget Framework Test</string> 1058 <string name="widget_pass">Pass</string> 1059 <string name="widget_fail">Fail</string> 1060 1061 <!-- Strings for DeskClock --> 1062 <string name="deskclock_tests">Alarms and Timers Tests</string> 1063 <string name="deskclock_tests_info"> 1064 The Alarms and Timers tests verify that the Clock app implements the AlarmClock API properly. 1065 </string> 1066 <string name="deskclock_group_alarms">Alarms</string> 1067 <string name="deskclock_group_timers">Timers</string> 1068 1069 <string name="dc_show_alarms_test">Show Alarms Test</string> 1070 <string name="dc_show_alarms_test_info"> 1071 This test verifies that the SHOW_ALARMS API works.\n 1072 1. Press the "Show Alarms" button.\n 1073 2. Verify that a UI of the clock app is launched and displays the list of alarms\n 1074 </string> 1075 <string name="dc_show_alarms_button">Show Alarms</string> 1076 1077 <string name="dc_set_alarm_with_ui_test">Set Alarm Test</string> 1078 <string name="dc_set_alarm_with_ui_test_info"> 1079 This test verifies that the ACTION_SET_ALARM with no parameters API works.\n 1080 1. Press the "Set Alarm" button.\n 1081 2. Verify that the clock app is launched and displays a UI to manage alarms.\n 1082 </string> 1083 <string name="dc_set_alarm_button">Set Alarm</string> 1084 <string name="dc_set_alarm_verify_button">Verify</string> 1085 1086 <string name="dc_start_alarm_test">Start Alarm Test</string> 1087 <string name="dc_start_alarm_test_info"> 1088 This test verifies that the ACTION_SET_ALARM API actually starts an alarm.\n 1089 1. Press the "Start Alarm" button.\n 1090 2. Make sure the alarms UI is NOT shown\n 1091 3. Wait for the alarm to fire (may take up to 2 minutes)\n 1092 4. Verify that the alarm title is: "Start Alarm Test",\n 1093 the alarm is silent and vibrating (if the device supports vibrate).\n 1094 5. Dismiss the alarm.\n 1095 6. Verify that the alarm is not in the Clock\'s alarms list. The Verify button opens 1096 the alarm view.\n 1097 </string> 1098 <string name="dc_start_alarm_button">Start Alarm</string> 1099 1100 <string name="dc_full_alarm_test">Full Alarm Test</string> 1101 <string name="dc_full_alarm_test_info"> 1102 This test verifies that the ACTION_SET_ALARM API supports all extras.\n 1103 1. Press the "Create Alarm" button.\n 1104 2. Verify that you see one alarm with the following information:\n 1105 Name of alarm: Create Alarm Test. \n 1106 Vibrate: on.\n 1107 Ringtone: silent.\n 1108 Time: 01:23. \n 1109 Repeating on: Monday and Wednesday. \n 1110 </string> 1111 <string name="dc_full_alarm_button">Create Alarm</string> 1112 1113 <string name="dc_set_timer_with_ui_test">Set Timer Test</string> 1114 <string name="dc_set_timer_with_ui_test_info"> 1115 This test verifies that the ACTION_SET_TIMER API with no paramters open the UI\n 1116 1. Press the "Set Timer" button.\n 1117 2. Verify that the an app is launched and displays a UI to manage timers.\n 1118 </string> 1119 <string name="dc_set_timer_with_ui_button">Set Timer</string> 1120 1121 <string name="dc_start_timer_test">Start Timer Test</string> 1122 <string name="dc_start_timer_test_info"> 1123 This test verifies that the ACTION_SET_TIMER API actually starts a timer\n 1124 1. Press the "Start Timer" button.\n 1125 2. Verify that a timer is started and NO timers UI is shown.\n 1126 3. Verify that the timer named "Start Timer Test" rings after 30 seconds. Dismiss it.\n 1127 4. Verify that the timer is deleted after the dismissal.\n 1128 </string> 1129 <string name="dc_start_timer_button">Start Timer</string> 1130 1131 <string name="dc_start_timer_with_ui_test">Start Timer With UI Test</string> 1132 <string name="dc_start_timer_with_ui_test_info"> 1133 This test verifies that the ACTION_SET_TIMER API actually starts a timer with UI\n 1134 1. Press the "Start Timer" button.\n 1135 2. Verify that a timer is started and the timers UI is shown with a timer named "Start Timer Test".\n 1136 3. Verify that the timer rings after 30 seconds.\n 1137 </string> 1138 <!-- Strings for LockConfirmBypassTest --> 1139 <string name="lock_confirm_test_title">Keyguard Password Verification</string> 1140 <string name="lock_set_button_text">Set password</string> 1141 <string name="lock_change_button_text">Change password</string> 1142 <string name="lock_confirm_message"> 1143 This test verifies that the user is prompted for the current keyguard password before prompting for a new password.\n 1144 \nClick the \"Set password\" button if you currently don\'t have a password set.\n 1145 \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. 1146 </string> 1147 1148 <!-- String for Projection Tests --> 1149 <string name="test_category_projection">Projection Tests</string> 1150 <string name="projection_service_name">Projection Service</string> 1151 <string name="pca_info">This tests whether or not OpenGL projection works.\n 1152 You should see two "tumbling cubes." Tapping the screen should case the cubes to explode.</string> 1153 <string name="pca_test">Projection Cube Test</string> 1154 <string name="pwa_info">This tests whether or displaying widets and keyfocus navigation works.\n 1155 You should see four buttons on the bottom of the screen.\n 1156 Pressing the "up" and "down" buttons should highlight different buttons.\n 1157 Further, you should also be able to touch them and they should highlight as usual.</string> 1158 <string name="pwa_test">Projection Widget Test</string> 1159 <string name="pwa_button_up">Up</string> 1160 <string name="pwa_button_down">Down</string> 1161 <string name="pwa_button_left">Left</string> 1162 <string name="pwa_button_right">Right</string> 1163 <string name="pwa_button">Button</string> 1164 <string name="pla_test">Projection Scrolling List Test</string> 1165 <string name="pla_info">This tests whether a projected list view will scroll properly\n 1166 You should see 50 list items and be able to scroll up and down the list</string> 1167 <string name="pva_test">Projection Video Playback Test</string> 1168 <string name="pva_info">This tests whether video playback works when projected.\n 1169 You should see a blinking white box and here a beep that is synchronized with each blink</string> 1170 <string name="pta_test">Projection Multitouch Test</string> 1171 <string name="pta_info">This tests whether multitouch works.\n 1172 Touching the screen should render a dot at the location you touched.\n 1173 Touching with additional fingers will render additoinal dots and you should be able to drag them around.</string> 1174 <string name="poa_test">Projection Offscreen Activity</string> 1175 <string name="poa_info">This tests whether a virtual display will continue to respond to and render even when the screen is off.\n 1176 Simply follow the instructions and the test will detect the pass conditions.\n 1177 Note that turning on the screen too early will result in a failure.</string> 1178 1179 <!-- Strings for RotationVectorTest and GameRotationVectorTest --> 1180 <string name="rotation_vector_test">Rotation Vector Accuracy Test</string> 1181 <string name="snsr_rotation_vector_set_reference"> 1182 Place the mobile device in a reference position. Note: to provide an accurate reference, 1183 align the device along one edge of a notebook laying on a table.</string> 1184 <string name="snsr_rotation_vector_reference_set">Reference position set.</string> 1185 <string name="snsr_rotation_vector_move_info">Move, shake, and rotate the device.</string> 1186 <string name="snsr_rotation_vector_set_final">Place the device back to the reference position.</string> 1187 <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> 1188 1189 <!-- Strings for BYOD managed provisioning tests (ByodFlowTestActivity) --> 1190 <string name="test_category_managed_provisioning">Managed Provisioning</string> 1191 <string name="provisioning_byod_device_admin">CTS Verifier - BYOD Admin</string> 1192 <string name="provisioning_byod">BYOD Managed Provisioning</string> 1193 <string name="provisioning_byod_info"> 1194 This test exercises the BYOD managed provisioning flow. 1195 Start by pressing the button on screen and follow instructions to finish the managed provisioning process. 1196 If your device has not been encrypted before, it will be encrypted and rebooted. 1197 After the provisioning process completes, return to this page and carry out further verifications. 1198 </string> 1199 <string name="provisioning_byod_start">Start BYOD provisioning flow</string> 1200 <string name="provisioning_byod_instructions"> 1201 1. Press the button below to start the managed provisioning flow. 1202 If your device has not been encrypted before, it will reboot to apply encryption. 1203 After reboot follow instructions in the notification area to complete the provisioning.\n 1204 2. After successful provisioning, you should be automatically redirected back to this page. 1205 Please press through the following verification steps. 1206 Allow a few seconds after returning from provisioning, as the profile owner test should automatically pass. 1207 </string> 1208 <string name="provisioning_byod_profileowner">Profile owner installed</string> 1209 <string name="provisioning_byod_diskencryption">Full disk encryption enabled</string> 1210 <string name="provisioning_byod_profile_visible">Work profile visible in Settings</string> 1211 <string name="provisioning_byod_admin_visible">Device administrator visible in Settings</string> 1212 <string name="provisioning_byod_workapps_visible">Badged work apps visible in Launcher</string> 1213 <string name="provisioning_byod_cross_profile">Open app cross profiles</string> 1214 <string name="provisioning_byod_cross_profile_app_personal"> 1215 You selected the CTS Verifier option. 1216 </string> 1217 <string name="provisioning_byod_cross_profile_app_work">You selected the Work option.</string> 1218 <string name="provisioning_byod_cross_profile_instruction"> 1219 Please press the Go button to start an action.\n 1220 \n 1221 You should be asked to choose either \"CTS Verifier\" or \"Work\" to complete the action. 1222 Pressing either should bring up a page stating your choice.\n 1223 \n 1224 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 1225 </string> 1226 <string name="provisioning_byod_profile_visible_instruction"> 1227 Please press the Go button to open the Settings page. 1228 Navigate to Accounts and confirm that:\n 1229 \n 1230 - Both Personal and Work categories exist.\n 1231 - \"Remove work profile\" exists under the Work category.\n 1232 \n 1233 Use the Back button to return to this page. 1234 </string> 1235 <string name="provisioning_byod_admin_visible_instruction"> 1236 Please press the Go button to open the Security page in Settings. 1237 Navigate to Device administrators and confirm that:\n 1238 \n 1239 - Both Personal and Work categories exist.\n 1240 - \"CTS Verifier - BYOD Admin\" exists under the Work category, and is activated.\n 1241 \n 1242 Use the Back button to return to this page. 1243 </string> 1244 <string name="provisioning_byod_workapps_visible_instruction"> 1245 Please press the Go button to start the launcher. 1246 Go to All Apps screen and scroll through it to confirm that:\n 1247 \n 1248 - A new set of work apps including CTS Verifier appear in the list.\n 1249 - Work badge overlay appears on work app\'s icon.\n 1250 \n 1251 Then navigate back to this screen using Recents button. 1252 </string> 1253 <string name="provisioning_byod_no_activity">Cannot communicate with activity in the work profile.</string> 1254 <string name="provisioning_byod_delete_profile">Initiate deletion of work profile.</string> 1255 <string name="provisioning_byod_profile_deleted">Work profile deleted.</string> 1256 <string name="provisioning_byod_disabled">Device provisioning is not enabled.</string> 1257 <string name="provisioning_byod_go">Go</string> 1258 <string name="provisioning_button_finish">Finish</string> 1259 <string name="provisioning_cross_profile_chooser">Choose an app to complete action</string> 1260 1261 <!-- Strings for DeviceOwnerProvisioningTest --> 1262 <string name="provisioning_device_owner">Device Owner Provisioning</string> 1263 <string name="device_owner_provisioning_tests">Device Owner provisioning tests</string> 1264 <string name="device_owner_provisioning_tests_info">The device owner provisioning tests verify that setting up a corporate owned device can only be done on a factory reset device.</string> 1265 <string name="device_owner_provisioning_category">Device Owner Provisioning</string> 1266 <string name="device_owner_negative_test">Device owner negative test</string> 1267 <string name="device_owner_negative_test_info">Device owner provisioning should only work on new or factory reset devices. Please click on the "Start provisioning" button and verify that you get a warning dialog telling you that the device is already set up. If that is the case, this test has passed.</string> 1268 <string name="start_device_owner_provisioning_button">Start provisioning</string> 1269 1270 <!-- Strings for JobScheduler Tests --> 1271 <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> 1272 1273 <string name="js_idle_test">Idle Mode Constraints</string> 1274 <string name="js_start_test_text">Start test</string> 1275 <string name="js_idle_instructions">Verify the behaviour of the JobScheduler API for when the device is in idle mode. Simply follow the on-screen instructions.</string> 1276 <string name="js_idle_description_1">Turn the screen off and then back on in order to begin.</string> 1277 <string name="js_idle_item_idle_off">Idle job does not execute when device is not idle.</string> 1278 <string name="js_idle_item_idle_on">Idle job does execute when device is forced into idle.</string> 1279 1280 <string name="js_charging_test">Charging Constraints</string> 1281 <string name="js_charging_instructions">Verify the behaviour of the JobScheduler API for when the device is on power and unplugged from power. Simply follow the on-screen instructions.</string> 1282 <string name="js_charging_description_1">Unplug the phone in order to begin.</string> 1283 <string name="js_charging_off_test">Device not charging will not execute a job with a charging constraint.</string> 1284 <string name="js_charging_on_test">Device when charging will execute a job with a charging constraint.</string> 1285 <string name="js_charging_description_2">After the above test has passed, plug the device back in to continue. If the above failed, you can simply fail this test.</string> 1286 1287 <string name="js_connectivity_test">Connectivity Constraints</string> 1288 <string name="js_connectivity_instructions">Verify the behaviour of the JobScheduler API for when the device has no access to data connectivity. Simply follow the on-screen instructions.</string> 1289 <string name="js_connectivity_description_1">Disable WiFi and Cellular data to begin.</string> 1290 <string name="js_unmetered_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 1291 <string name="js_any_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 1292 <string name="js_no_connectivity_test">Device with no connectivity will still execute a job with no connectivity constraints.</string> 1293 </resources> 1294
