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 25 <!-- Strings for TestListActivity --> 26 <string name="test_category_audio">Audio</string> 27 <string name="test_category_camera">Camera</string> 28 <string name="test_category_device_admin">Device Administration</string> 29 <string name="test_category_hardware">Hardware</string> 30 <string name="test_category_networking">Networking</string> 31 <string name="test_category_sensors">Sensors</string> 32 <string name="test_category_security">Security</string> 33 <string name="test_category_streaming">Streaming</string> 34 <string name="test_category_features">Features</string> 35 <string name="test_category_deskclock">Clock</string> 36 <string name="test_category_other">Other</string> 37 <string name="clear">Clear</string> 38 <string name="test_results_cleared">Test results cleared.</string> 39 <string name="view">View</string> 40 <string name="test_results_error">Couldn\'t create test results report.</string> 41 <string name="export">Export</string> 42 <string name="no_storage">Cannot save report to external storage, see log for details.</string> 43 <string name="report_saved">Report saved to: %s</string> 44 45 <!-- Strings for ReportViewerActivity --> 46 <string name="report_viewer">Report Viewer</string> 47 48 <!-- Strings for BackupTestActivity --> 49 <string name="backup_test">Data Backup Test</string> 50 <string name="backup_info">This test checks that data backup and automatic restore works 51 properly. The test activity lists some preferences and files that are backed up and 52 restored by the CTS Verifier. If backup and restore is working properly, these values 53 should be restored after running the backup manager, uninstalling the app, and reinstalling 54 the CTS Verifier. 55 \n\nPress the \"Generate Test Data\" to populate these values 56 and then follow the on screen instructions to finish the test. 57 </string> 58 <string name="bu_preferences">Preferences</string> 59 <string name="bu_files">Files</string> 60 <string name="bu_loading">Loading...</string> 61 <string name="bu_generate">Generate Test Data</string> 62 <string name="bu_generate_error">Error occurred while generating test data...</string> 63 <string name="bu_instructions">Random values for the preferences and files have been saved. 64 \n\nFollow the instructions below to check that the data backup and restore works: 65 \n\n1. Make sure backup and automatic restore are enabled in settings. Depending on the 66 backup transport supported by the device you may need to do additional steps. For instance 67 you may need to set a Google account as the backup account for the device. 68 \n\n2. Run the backup manager: adb shell bmgr run 69 \n\n3. Uninstall the program: adb uninstall com.android.cts.verifier 70 \n\n4. Reinstall the CTS Verifier and verify that the values are still the same. 71 </string> 72 <string name="bu_settings">Settings</string> 73 74 <!-- Strings for Device Administration tests --> 75 <string name="da_policy_serialization_test">Policy Serialization Test</string> 76 <string name="da_policy_serialization_info">This test checks that a device policy is properly 77 saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create 78 a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the 79 device and verify that all rows in the policy list are green. Red items indicate policy 80 settings that were not loaded properly. 81 </string> 82 <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device 83 policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your 84 device and return to this test in the CTS Verifier. 85 </string> 86 <string name="da_generate_policy">Generate Policy</string> 87 <string name="da_apply_policy">Apply Policy</string> 88 <string name="da_random_policy">Random policy generated.</string> 89 <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string> 90 <string name="da_password_quality">Password Quality</string> 91 <string name="da_password_quality_alphabetic">Alphabetic</string> 92 <string name="da_password_quality_alphanumeric">Alphanumeric</string> 93 <string name="da_password_quality_numeric">Numeric</string> 94 <string name="da_password_quality_something">Something</string> 95 <string name="da_password_minimum_length">Minimum Password Length</string> 96 <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string> 97 <string name="da_maximum_time_to_lock">Maximum Time to Lock</string> 98 <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string> 99 100 <string name="da_screen_lock_test">Screen Lock Test</string> 101 <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow 102 method immediately locks the screen. It should lock the screen immediately despite any 103 settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen. 104 Your screen should be locked and require the password to be entered. 105 </string> 106 <string name="da_force_lock">Force Lock</string> 107 <string name="da_lock_success">It appears the screen was locked successfully!</string> 108 <string name="da_lock_error">It does not look like the screen was locked...</string> 109 110 <!-- Strings for BluetoothActivity --> 111 <string name="bluetooth_test">Bluetooth Test</string> 112 <string name="bluetooth_test_info">The Bluetooth Control tests check whether or not the device 113 can disable and enable Bluetooth properly.\n\nThe Device Communication tests require two 114 devices to pair and exchange messages. The two devices must be: 115 \n\n1. a candidate device implementation running the software build to be tested 116 \n\n2. a separate device implementation already known to be compatible</string> 117 118 <string name="bt_control">Bluetooth Control</string> 119 <string name="bt_device_communication">Device Communication</string> 120 121 <string name="bt_toggle_bluetooth">Toggle Bluetooth</string> 122 <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string> 123 <string name="bt_enable_bluetooth">Enable Bluetooth</string> 124 <string name="bt_disable_bluetooth">Disable Bluetooth</string> 125 <string name="bt_disabling">Disabling Bluetooth...</string> 126 <string name="bt_disabling_error">Could not disable Bluetooth...</string> 127 128 <string name="bt_connection_access_server">Connection Access Server</string> 129 <string name="bt_connection_access_client">Connection Access Client</string> 130 <string name="bt_connection_access_server_info"> 131 Start the CTS Verifier on another device, start the Bluetooth test, and choose 132 \"Connection Access Client\" to setup the test. 133 \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together 134 using the \"Make Discoverable\" and \"Pick Server\" buttons. 135 \n\nA connection access request should appear on the server and enable the pass button. 136 </string> 137 <string name="bt_connection_access_client_info"> 138 Start the CTS Verifier on another device, start the Bluetooth test, and choose 139 \"Connection Access Server\" to complete the test. 140 \n\nMake the device acting as the server discoverable and connect to it via the 141 \"Pick Server\" button. Check that the server displays the connection access request 142 dialog. The client device does not need to do anything else. 143 </string> 144 <string name="bt_ca_dialog">Was the connection access request dialog shown?</string> 145 <string name="bt_ca_tips"> 146 Tap the \"Bluetooth Settings\" button and check that both devices are not paired 147 before running the test. 148 \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth 149 devices together and start the test. 150 </string> 151 152 <string name="bt_secure_server">Secure Server</string> 153 <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> 154 <string name="bt_insecure_server">Insecure Server</string> 155 <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> 156 <string name="bt_waiting">Waiting for client...</string> 157 <string name="bt_listening">Listening...</string> 158 <string name="bt_connecting">Connecting...</string> 159 <string name="bt_connected">Connected</string> 160 <string name="bt_received_messages">Received Messages</string> 161 <string name="bt_sent_messages">Sent Messages</string> 162 <string name="bt_no_messages">No messages</string> 163 <string name="bt_make_discoverable">Make Discoverable</string> 164 <string name="bt_pick_server">Pick Server</string> 165 <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string> 166 <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string> 167 168 <string name="bt_secure_client">Secure Client</string> 169 <string name="bt_insecure_client">Insecure Client</string> 170 171 <string name="bt_device_picker">Device Picker</string> 172 <string name="bt_paired_devices">Paired Devices</string> 173 <string name="bt_new_devices">New Devices</string> 174 <string name="bt_no_devices">No devices</string> 175 <string name="bt_scan">Scan for Devices</string> 176 <string name="bt_scanning">Scanning...</string> 177 <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> 178 <string name="bt_settings">Bluetooth Settings</string> 179 180 <!-- Strings for FeatureSummaryActivity --> 181 <string name="feature_summary">Hardware/Software Feature Summary</string> 182 <string name="feature_summary_info">This is a test for...</string> 183 <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string> 184 <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string> 185 <string name="fs_no_data">No data.</string> 186 <string name="fs_legend_good">standard feature reported by device</string> 187 <string name="fs_legend_indeterminate">optional feature not reported by device</string> 188 <string name="fs_legend_warning">non-standard feature reported by device</string> 189 <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string> 190 191 <string name="empty"></string> 192 193 <!-- Strings for Location tests --> 194 <string name="location_gps_test">GPS Test</string> 195 <string name="location_gps_test_info">This test verifies basic GPS behavior 196 and callback scheduling. 197 Make sure the device has line of sight to GPS satellites 198 (for example, outside, or near a window) 199 and then press OK to run the automated tests.</string> 200 201 <!-- Strings for NfcTestActivity --> 202 <string name="nfc_test">NFC Test</string> 203 <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with 204 NFC enabled to exchange messages. One device must be the candidate device running the 205 software build to be tested, while the other device must be an implementation already 206 known to be compatible.\n\nThe Tag Verification tests check that your 207 device can properly read and write to tags of different technologies. The MIFARE 208 Ultralight test is only applicable for devices that support it. 209 \n\nThe Host-based card emulation tests check that your device has properly implemented 210 host-based card emulation. 211 </string> 212 213 <string name="nfc_not_enabled">NFC is not enabled!</string> 214 <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the 215 button below to goto Settings and enable it.</string> 216 <string name="nfc_settings">NFC Settings</string> 217 218 <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string> 219 <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled. 220 Click the button below to goto NFC Sharing Settings and enable it.</string> 221 <string name="ndef_push_settings">NFC Sharing Settings</string> 222 223 <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string> 224 <string name="nfc_ndef_push_sender">NDEF Push Sender</string> 225 <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string> 226 227 <string name="nfc_tag_verification">Tag Verification</string> 228 <string name="nfc_ndef">NDEF</string> 229 <string name="nfc_mifare_ultralight">MIFARE Ultralight</string> 230 231 <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on 232 another device and touch the devices back to back. The receiver should show a 233 dialog indicating it has successfully received the correct message!</string> 234 <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another 235 device running the \"CTS Verifier NDEF Receiver\"...</string> 236 237 <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on 238 another device and touch the devices back to back. The receiver should show a 239 dialog indicating it has successfully received the correct message!</string> 240 <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another 241 device running the \"CTS Verifier NDEF Sender\"...</string> 242 <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push 243 message.</string> 244 <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push 245 message.</string> 246 247 <string name="nfc_tag_verifier">NFC Tag Verifier</string> 248 <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read 249 a tag of the chosen technology.</string> 250 251 <string name="nfc_scan_tag">Place device on a writable %s tag...</string> 252 <string name="nfc_write_tag_title">Writable tag discovered!</string> 253 <string name="nfc_write_tag_message">Press OK to write to this tag...</string> 254 <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string> 255 <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string> 256 <string name="nfc_no_tech">No tag technologies detected...</string> 257 258 <string name="nfc_writing_tag">Writing NFC tag...</string> 259 <string name="nfc_writing_tag_error">Error writing NFC tag...</string> 260 <string name="nfc_reading_tag">Reading NFC tag...</string> 261 <string name="nfc_reading_tag_error">Error reading NFC tag...</string> 262 263 <string name="nfc_result_success">Test passed!</string> 264 <string name="nfc_result_failure">Test failed!</string> 265 266 <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string> 267 <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string> 268 269 <string name="nfc_hce">Host-based card emulation</string> 270 <string name="nfc_hce_default">Default route</string> 271 <string name="nfc_hce_reader_tests">HCE reader tests</string> 272 <string name="nfc_hce_emulator_tests">HCE emulator tests</string> 273 <string name="nfc_hce_emulator_test_info">The host-based card emulation 274 tests require two devices to be completed. The HCE emulator tests are used 275 to actually test the host-based card emulation feature of the device-under-test. So the 276 device running the emulator tests must be the candidate device running the software 277 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 278 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 279 and makes sure the device-under-test implements card emulation correctly. 280 </string> 281 <string name="nfc_hce_reader_test_info">The host-based card emulation 282 tests require two devices to be completed. The HCE emulator tests are used 283 to actually test the host-based card emulation feature of the device-under-test. So the 284 device running the emulator tests must be the candidate device running the software 285 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 286 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 287 and makes sure the device-under-test implements card emulation correctly. 288 </string> 289 <string name="nfc_hce_please_wait">Please wait</string> 290 <string name="nfc_hce_setting_up">Setting up card emulation services...</string> 291 <string name="nfc_hce_single_payment_emulator">Single payment (Emulator)</string> 292 <string name="nfc_hce_single_payment_reader">Single payment (Reader)</string> 293 294 <string name="nfc_hce_dual_payment_emulator">Two payment services (Emulator)</string> 295 <string name="nfc_hce_dual_payment_reader">Two payment services (Reader)</string> 296 297 <string name="nfc_hce_change_default_emulator">Change default payment service (Emulator)</string> 298 <string name="nfc_hce_change_default_reader">Change default payment service (Reader)</string> 299 300 <string name="nfc_hce_tap_reader_title">Tap reader</string> 301 <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> 302 303 <string name="nfc_hce_single_non_payment_emulator">Single non-payment (Emulator)</string> 304 <string name="nfc_hce_single_non_payment_reader">Single non-payment (Reader)</string> 305 306 <string name="nfc_hce_dual_non_payment_emulator">Two non-payment services (Emulator)</string> 307 <string name="nfc_hce_dual_non_payment_reader">Two non-payment services (Reader)</string> 308 309 <string name="nfc_hce_conflicting_non_payment_emulator">Two conflicting non-payment services (Emulator)</string> 310 <string name="nfc_hce_conflicting_non_payment_reader">Two conflicting non-payment services (Reader)</string> 311 312 <string name="nfc_hce_offhost_service_emulator">Off-host service (Emulator)</string> 313 <string name="nfc_hce_offhost_service_reader">Off-host service (Reader)</string> 314 <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> 315 316 <string name="nfc_hce_on_and_offhost_service_emulator">On and off-host services (Emulator)</string> 317 <string name="nfc_hce_on_and_offhost_service_reader">On and off-host services (Reader)</string> 318 <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> 319 320 <string name="nfc_hce_tap_test_emulator">50 successful taps test (Emulator)</string> 321 <string name="nfc_hce_tap_test_reader">50 successful taps test (Reader)</string> 322 <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> 323 <string name="nfc_hce_throughput_emulator">HCE throughput test (Emulator)</string> 324 <string name="nfc_hce_throughput_reader">HCE throughput test (Reader)</string> 325 <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> 326 <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> 327 <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> 328 <string name="nfc_payment_service_desc">NFC Payment service</string> 329 <string name="ppse">PPSE</string> 330 <string name="mastercard">MasterCard</string> 331 <string name="paymentService1">Payment Service #1</string> 332 <string name="paymentService2">Payment Service #2</string> 333 <string name="transportService1">TransportService #1</string> 334 <string name="transportService2">TransportService #2</string> 335 <string name="accessService">AccessService</string> 336 <string name="offhostService">OffhostService</string> 337 338 <!-- Strings for AccelerometerTestActivity and GyroscopeTestActivity --> 339 <string name="snsr_accel_test">Accelerometer Test</string> 340 <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> 341 342 <string name="snsr_gyro_test">Gyroscope Test</string> 343 <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> 344 <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string> 345 <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string> 346 <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> 347 <string name="snsr_gyro_test_degrees_title">Wrong units?</string> 348 <string name="snsr_gyro_test_degrees_message">These values looks like degrees per second. These should be radians per second!</string> 349 350 <!-- Strings for SuidFilesActivity --> 351 <string name="suid_files">SUID File Scanner</string> 352 <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> 353 <string name="scanning_directory">Scanning directory...</string> 354 <string name="file_status">User: %1$s\nGroup: %2$s\nPermissions: %3$s\nPath: %4$s</string> 355 <string name="no_file_status">Could not stat file...</string> 356 <string name="congratulations">Congratulations!</string> 357 <string name="no_suid_files">No unauthorized suid files detected!</string> 358 359 <!-- Strings for Camera Analyzer --> 360 <string name="camera_analyzer">Camera Analyzer</string> 361 <string name="ca_find_checkerboard_label">Find target</string> 362 <string name="ca_check_formats_label">Output formats</string> 363 <string name="ca_exposure_test_label">Exposure Comp.</string> 364 <string name="ca_result_label">Results will be here</string> 365 <string name="ca_wb_test_label">White Balance</string> 366 <string name="ca_lock_test_label">AE Lock</string> 367 <string name="ca_metering_label">Metering Area</string> 368 <string name="ca_focus_modes_label">Focus Modes</string> 369 <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> 370 371 <!-- Strings for Camera Orientation --> 372 <string name="camera_orientation">Camera Orientation</string> 373 <string name="co_info">This test verifies the orientation capabilities of 374 camera preview and capture.\n - The left view shows a preview window rotated 375 clockwise by a given magnitude of degrees.\n - The right view, after taking 376 a photo, shows the captured image.\n - For each camera and orientation, both 377 the left and right views should appear rotated clockwise by the amount of 378 degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose 379 \"Fail\".\n - For front-facing cameras, the test will horizontally mirror 380 the captured image prior to rotation, in attempt to make the left and right 381 views appear the same.\n - The physical orientation of the device does not 382 matter.\n - Read the message above the \"Take Photo\" button for 383 step-by-step instructions. 384 </string> 385 <string name="co_preview_label">Camera preview</string> 386 <string name="co_format_label">Oriented photo</string> 387 <string name="co_camera_label">Camera:</string> 388 <string name="co_orientation_label">Orientation</string> 389 <string name="co_orientation_direction_label">clockwise</string> 390 <string name="co_instruction_heading_label">Instruction:</string> 391 <string name="co_instruction_text_photo_label">Take a photo</string> 392 <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> 393 <string name="co_instruction_text_extra_label">(mirrored horizontally prior to rotation, since camera is front-facing)</string> 394 <string name="co_photo_button_caption">Take Photo</string> 395 396 <!-- Strings for Camera Intents --> 397 <string name="camera_intents">Camera Intents</string> 398 <string name="ci_info"> 399 This test verifies that the default camera app is firing intents 400 after pictures/videos are taken. It also verifies that when the 401 default camera app is invoked via intents, the launch intents work, 402 and the broadcast intents are received when appropriate per the SDK 403 documentation.\n\n 404 - Read the message above the \"Start Test\" button for 405 step-by-step instructions. 406 </string> 407 <string name="ci_preview_label">Camera preview</string> 408 <string name="ci_format_label">Oriented photo</string> 409 <string name="ci_camera_label">Camera:</string> 410 <string name="ci_intents_label">Intents Test</string> 411 <string name="ci_intents_direction_label">clockwise</string> 412 <string name="ci_instruction_heading_label">Instructions:</string> 413 <string name="ci_instruction_text_photo_label">READ BEFORE STARTING TEST</string> 414 <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> 415 <string name="ci_instruction_text_app_picture_label">\n 416 1. Click Start Test. \n 417 2. Go to home screen (HOME key). \n 418 3. Launch Camera application. \n 419 4. Capture photo. \n 420 5. Return to CTS verifier app. \n 421 6. Pass button will light up if intent was received.\n 422 7. Click "Pass" if possible. 423 </string> 424 <string name="ci_instruction_text_app_video_label">\n 425 1. Click Start Test. \n 426 2. Go to home screen (HOME key). \n 427 3. Launch Camera application. \n 428 4. Capture video. \n 429 5. Return to CTS verifier app. \n 430 6. Pass button will light up if intent was received.\n 431 7. Click "Pass" if possible. 432 </string> 433 <string name="ci_instruction_text_intent_picture_label">\n 434 1. Click Start Test.\n 435 2. Camera app will launch, prompting to take photo.\n 436 3. Capture/confirm photo using camera app controls.\n 437 4. Pass button will light up if intent was NOT received.\n 438 5. Click "Pass" if possible. 439 </string> 440 <string name="ci_instruction_text_intent_video_label">\n 441 1. Click Start Test.\n 442 2. Camera app will launch, prompting to take video.\n 443 3. Capture/confirm video using camera app controls.\n 444 4. Pass button will light up if intent was received.\n 445 5. Click "Pass" if possible. 446 </string> 447 <string name="ci_start_test_button_caption">Start Test</string> 448 449 <!-- Strings for Camera Formats --> 450 <string name="camera_format">Camera Formats</string> 451 <string name="cf_info">This test checks that all the supported 452 output formats for camera preview callbacks work correctly, and 453 that the mandatory formats are available. \n - The left view shows 454 a standard preview window. \n - The right view shows the output 455 processed from camera preview callbacks. \n - For each camera, 456 resolution, and format combination in the dropdowns, the right 457 view should look the same as the left, and neither should have 458 streaks, lines, or other artifacts. \n - For front-facing cameras, 459 the right view must be horizontally mirrored relative to the left 460 view.\n - Note that the frame rate of the right view may be much 461 lower than on the left; this is not an indication of a failed 462 test. 463 </string> 464 <string name="cf_preview_label">Normal preview</string> 465 <string name="cf_format_label">Processed callback data</string> 466 467 <!-- Strings for USB accessory test activity --> 468 <string name="usb_accessory_test">USB Accessory Test</string> 469 <string name="usb_accessory_test_info"> 470 1. Connect your Android device to a computer and run the \'cts-usb-accessory\' program 471 included with the CTS Verifier bundle. 472 \n\n2. If you have not started the CTS Verifier, press \'OK\' when asked to open the CTS 473 Verifier when the accessory is connected. \n\nIf you are already in this test, 474 then you can press \'Cancel\' but press \'OK\' in the next dialog asking whether to allow 475 CTS Verifier to access the accessory. 476 \n\n3. You should see the accessory and the CTS Verifier display a series of messages 477 which indicates that the accessory support is working properly. 478 </string> 479 <string name="usb_not_available_title">USB accessory feature is not available?</string> 480 <string name="usb_not_available_message">If your device is supposed to support USB accessories, your API implementation is not behaving correctly!</string> 481 <string name="usb_received_messages">Received Messages</string> 482 <string name="usb_sent_messages">Sent Messages</string> 483 <string name="usb_no_messages">No messages</string> 484 <string name="usb_message_thread_started">Starting message processing...</string> 485 <string name="usb_message_thread_exception">Exception occurred while processing a message...</string> 486 <string name="usb_message_thread_ended">Stopping message processing...</string> 487 <string name="usb_test_passed">Received all expected messages. Pass button enabled!</string> 488 <string name="usb_file_descriptor_error">Could not open file descriptor for USB accessory... try reconnecting and restarting the accessory?</string> 489 490 <!-- Strings for StreamingVideoActivity --> 491 <string name="streaming_video">Streaming Video Quality Verifier</string> 492 <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> 493 <string name="sv_no_data">No videos.</string> 494 <string name="sv_failed_title">Test Failed</string> 495 <string name="sv_failed_message">Unable to play stream. See log for details.</string> 496 497 <!-- Strings for P2pTestActivity --> 498 <string name="p2p_test">Wi-Fi Direct Test</string> 499 <string name="p2p_test_info"> 500 The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange 501 messages. One device must be the candidate device running the software build to 502 be tested, while the other device must be an implementation already known to be 503 compatible.\n\nOne device should start the requester test, and the other should 504 start the responder test. Your device must pass both requester and responder 505 tests. 506 </string> 507 <string name="p2p_group_formation">Group Formation</string> 508 <string name="p2p_join">Group Join</string> 509 <string name="p2p_service_discovery">Service Discovery</string> 510 511 <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string> 512 <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string> 513 <string name="p2p_group_owner_test">Group Owner Test</string> 514 <string name="p2p_group_client_test">Group Client Test</string> 515 <string name="p2p_service_discovery_responder_test"> 516 Service Discovery Responder Test</string> 517 <string name="p2p_service_discovery_requester_test"> 518 Service Discovery Requester Test</string> 519 520 <string name="p2p_go_neg_responder">GO Negotiation Responder</string> 521 <string name="p2p_go_neg_requester">GO Negotiation Requester</string> 522 <string name="p2p_accept_client">Group Owner</string> 523 <string name="p2p_join_go">Group Client</string> 524 <string name="p2p_service_discovery_responder">Service Discovery Responder</string> 525 <string name="p2p_service_discovery_requester">Service Discovery Requester</string> 526 527 <string name="p2p_go_neg_responder_info"> 528 Start the \"GO Negotiation Requester Test\" on the other device and follow 529 the instructions.</string> 530 <string name="p2p_accept_client_info"> 531 Start the \"Group Client Test\" on the other device and follow 532 the instructions.</string> 533 <string name="p2p_service_discovery_responder_info"> 534 Start the \"Service Discovery Requester Test\" on the other device and follow 535 the instructions.</string> 536 537 <string name="p2p_go_neg_requester_info"> 538 Start the \"GO Negotiation Responder Test\" on the other device. 539 Then run each test individually by clicking on it\'s name.</string> 540 <string name="p2p_join_go_info"> 541 Start the \"Group Owner Test\" on the other device. 542 Then run each test individually by clicking on it\'s name.</string> 543 <string name="p2p_service_discovery_requester_info"> 544 Start the \"Service Discovery Responder Test\" on the other device. 545 Then run each test individually by clicking on it\'s name.</string> 546 547 <string name="p2p_not_enabled">Wi-Fi is not enabled</string> 548 <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled. 549 Click the button below to go to system settings and enable Wi-Fi.</string> 550 <string name="p2p_settings">Wi-Fi Direct Settings</string> 551 552 <string name="p2p_result_success">Test passed successfully.</string> 553 554 <string name="p2p_go_neg_responder_ready"> 555 The go negotiation responder is now ready to start. Start 556 the \"GO Negotiation Requester Test\" on the other device. 557 Keep the screen here until all tests on the other device are 558 finished.</string> 559 <string name="p2p_go_ready"> 560 The group owner is now ready to start. Start the \"Join 561 Group Test\" on the other device. 562 Keep the screen here until all tests on the other device are 563 finished.</string> 564 <string name="p2p_service_responder_ready"> 565 The service responder is now ready to start. Start the 566 \"Service Discovery Requester Test\" on the other device. 567 Keep the screen here until all tests on the other device are 568 finished.</string> 569 570 <string name="p2p_setup_error"> 571 Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string> 572 <string name="p2p_unexpected_error"> 573 Test failed.\n\nUnexpected error. Check logcat.</string> 574 <string name="p2p_add_local_service_error"> 575 Test failed.\n\nFailed to add local service.</string> 576 <string name="p2p_add_service_request_error"> 577 Test failed.\n\nFailed to add service request.</string> 578 <string name="p2p_remove_service_request_error"> 579 Test failed.\n\nFailed to remove service request.</string> 580 <string name="p2p_clear_service_requests_error"> 581 Test failed.\n\nFailed to clear service requests.</string> 582 <string name="p2p_connect_error"> 583 Test failed.\n\nFailed to start a p2p connection to the target device.</string> 584 <string name="p2p_remove_group_error"> 585 Test failed.\n\nFailed to remove a p2p group.</string> 586 <string name="p2p_discover_peers_error"> 587 Test failed.\n\nFailed to discover peers.</string> 588 <string name="p2p_discover_services_error"> 589 Test failed.\n\nFailed to discover services.</string> 590 <string name="p2p_ceate_group_error"> 591 Test failed.\n\nFailed to start up group owner.</string> 592 <string name="p2p_no_service_requests_error"> 593 Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string> 594 <string name="p2p_receive_invalid_response_error"> 595 Test failed.\n\nReceived an invalid message or could not receive 596 the expected message.\n\n</string> 597 <string name="p2p_target_not_found_error">Test failed.\n\n 598 The target responder device was NOT found. Start up the responder 599 test on the other device, then run the test again.</string> 600 <string name="p2p_target_invalid_role_error">Test failed.\n\n 601 The target responder must be p2p device. However, the target responder 602 device was group owner. Check the test case on the other device.</string> 603 <string name="p2p_target_invalid_role_error2">Test failed.\n\n 604 The target responder must be group owner. However, the target responder 605 device was p2p device. Check the test case on the other device.</string> 606 <string name="p2p_connection_error"> 607 Test failed.\n\nFailed to establish a p2p connection.</string> 608 <string name="p2p_detect_disconnection_error"> 609 Test failed.\n\nFailed to detect client disconnection.</string> 610 <string name="p2p_disconnect_error"> 611 Test failed.\n\nFailed to disconnect a p2p connection.</string> 612 613 <string name="p2p_search_target">Search Target</string> 614 <string name="p2p_searching_target">Searching for target device ...</string> 615 <string name="p2p_checking_serv_capab">Checking the service discovery 616 capability ...</string> 617 <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n 618 Click the \"OK\" button on the other device to accept the connection 619 request from this device.</string> 620 <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n 621 Enter the pin number on the other device.</string> 622 <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to 623 connect ...</string> 624 <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer 625 to disconnect ...</string> 626 627 <string name="camera_fov_calibration">Camera FOV Calibration</string> 628 <string name="camera_fov_calibration_done">Done</string> 629 <string name="camera_fov_general_settings">General settings</string> 630 <string name="camera_fov_label_options">Settings</string> 631 <string name="camera_fov_tap_to_take_photo">Tap to calibrate</string> 632 <string name="camera_fov_marker_distance">Marker distance (in cm)</string> 633 <string name="camera_fov_marker_distance_description">The distance in centimeters between 634 the solid lines on the target pattern.</string> 635 <string name="camera_fov_target_distance">Target distance (in cm)</string> 636 <string name="camera_fov_target_distance_description">The distance in centimeters from the 637 device to the target pattern.</string> 638 <string name="camera_fov_settings_button_text">Setup</string> 639 <string name="camera_fov_change_preview_sizes_button_text">Preview Sizes</string> 640 <string name="camera_fov_choose_preview_size_for_camera">Choose preview size for camera %1$s</string> 641 <string name="camera_fov_displayed_fov_label">Displayed FOV : </string> 642 <string name="camera_fov_reported_fov_label">Reported FOV : </string> 643 <string name="camera_fov_reported_fov_problem">Reported FOV problem</string> 644 <string name="camera_fov_reported_fov_problem_message">The reported FOV before takePicture() is 645 different from when onPictureTaken() is called.\nAs picture size has not been changed, the 646 reported FOV should be identical at both times.\n\nFOV before/after: %1$f / %2$f</string> 647 648 <string name="camera_fov_panorama_wallpaper_title">Photo Sphere Live Wallpaper</string> 649 <string name="camera_fov_panorama_wallpaper_description">This live wallapper displays photo 650 spheres.</string> 651 <string name="camera_fov_select_panorama">Select panorama</string> 652 <string name="camera_fov_select_panorama_description">Select a panorama to display in the 653 live wallpaper.</string> 654 <string name="camera_fov_reset_panorama">Reset panorama</string> 655 <string name="camera_fov_reset_panorama_description">Resets the panorama to show the demo 656 file.</string> 657 <string name="camera_fov_enable_compass_mode">Enable compass mode</string> 658 <string name="camera_fov_enable_compass_mode_description">If enabled, the panorama orients 659 itself according to the current rotation of the device.</string> 660 661 <string name="test_category_notifications">Notifications</string> 662 <string name="nls_test">Notification Listener Test</string> 663 <string name="nls_service_name">Notification Listener for CTS Verifier</string> 664 <string name="nls_info">This test checks that a NotificationListenerService can be enabled 665 and disabled, and that once enabled the service is able to receive notificaitons and 666 dismiss them. 667 </string> 668 <string name="nls_enable_service">Please enable \"Notification Listener for CTS Verifier\" 669 under Security > Notification Access and return here.</string> 670 <string name="nls_disable_service">Please disable \"Notification Listener for CTS Verifier\" 671 under Security > Notification Access and return here.</string> 672 <string name="nls_start_settings">Launch Settings</string> 673 <string name="nls_service_started">Service should start once enabled.</string> 674 <string name="nls_note_received">Check that notification was received.</string> 675 <string name="nls_payload_intact">Check that notification payload was intact.</string> 676 <string name="nls_clear_one">Check that service can clear a notification.</string> 677 <string name="nls_clear_all">Check that service can clear all notifications.</string> 678 <string name="nls_service_stopped">Service should stop once disabled.</string> 679 <string name="nls_note_missed">Check that notification was not received.</string> 680 681 <string name="cacert_test">CA Cert Notification Test</string> 682 <string name="cacert_info">This test checks that when a CA Certificate is installed, the user is notified.</string> 683 <string name="cacert_do_something">Do it</string> 684 <string name="cacert_done">Done</string> 685 <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> 686 <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> 687 <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> 688 <string name="cacert_dismiss_notification">Dismiss the notification. If it cannot be dismissed, fail the test.</string> 689 690 <string name="caboot_test">CA Cert Notification on Boot test</string> 691 <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> 692 <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> 693 <string name="caboot_check_creds">Check Credentials</string> 694 <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> 695 <string name="caboot_install_cert">Install credential</string> 696 <string name="caboot_reboot_desc">Please reboot the device and return to this test.</string> 697 <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> 698 699 <!-- Strings for Widget --> 700 <string name="widget_framework_test">Widget Framework Test</string> 701 <string name="widget_framework_test_info">This test checks some basic features of the widget 702 framework. In order to perform the test, press the Home button. Add the widget 703 titled "CTS Verifier" to the home screen. Follow the instructions in the widget.</string> 704 <string name="widget_name">Widget Framework Test</string> 705 <string name="widget_pass">Pass</string> 706 <string name="widget_fail">Fail</string> 707 708 <!-- Strings for DeskClock --> 709 <string name="deskclock_tests">Alarms and Timers Tests</string> 710 <string name="deskclock_tests_info"> 711 The Alarms and Timers tests verify that the Clock app implements the AlarmClock API properly. 712 </string> 713 <string name="deskclock_group_alarms">Alarms</string> 714 <string name="deskclock_group_timers">Timers</string> 715 716 <string name="dc_show_alarms_test">Show Alarms Test</string> 717 <string name="dc_show_alarms_test_info"> 718 This test verifies that the SHOW_ALARMS API works.\n 719 1. Press the "Show Alarms" button.\n 720 2. Verify that a UI of the clock app is launched and displays the list of alarms\n 721 </string> 722 <string name="dc_show_alarms_button">Show Alarms</string> 723 724 <string name="dc_set_alarm_with_ui_test">Set Alarm Test</string> 725 <string name="dc_set_alarm_with_ui_test_info"> 726 This test verifies that the ACTION_SET_ALARM with no parameters API works.\n 727 1. Press the "Set Alarm" button.\n 728 2. Verify that the clock app is launched and displays a UI to manage alarms.\n 729 </string> 730 <string name="dc_set_alarm_button">Set Alarm</string> 731 <string name="dc_set_alarm_verify_button">Verify</string> 732 733 <string name="dc_start_alarm_test">Start Alarm Test</string> 734 <string name="dc_start_alarm_test_info"> 735 This test verifies that the ACTION_SET_ALARM API actually starts an alarm.\n 736 1. Press the "Start Alarm" button.\n 737 2. Make sure the alarms UI is NOT shown\n 738 3. Wait for the alarm to fire (may take up to 2 minutes)\n 739 4. Verify that the alarm title is: "Start Alarm Test",\n 740 the alarm is silent and vibrating (if the device supports vibrate).\n 741 5. Dismiss the alarm.\n 742 6. Verify that the alarm is not in the Clock\'s alarms list. The Verify button opens 743 the alarm view.\n 744 </string> 745 <string name="dc_start_alarm_button">Start Alarm</string> 746 747 <string name="dc_full_alarm_test">Full Alarm Test</string> 748 <string name="dc_full_alarm_test_info"> 749 This test verifies that the ACTION_SET_ALARM API supports all extras.\n 750 1. Press the "Create Alarm" button.\n 751 2. Verify that you see one alarm with the following information:\n 752 Name of alarm: Create Alarm Test. \n 753 Vibrate: on.\n 754 Ringtone: silent.\n 755 Time: 01:23. \n 756 Repeating on: Monday and Wednesday. \n 757 </string> 758 <string name="dc_full_alarm_button">Create Alarm</string> 759 760 <string name="dc_set_timer_with_ui_test">Set Timer Test</string> 761 <string name="dc_set_timer_with_ui_test_info"> 762 This test verifies that the ACTION_SET_TIMER API with no paramters open the UI\n 763 1. Press the "Set Timer" button.\n 764 2. Verify that the an app is launched and displays a UI to manage timers.\n 765 </string> 766 <string name="dc_set_timer_with_ui_button">Set Timer</string> 767 768 <string name="dc_start_timer_test">Start Timer Test</string> 769 <string name="dc_start_timer_test_info"> 770 This test verifies that the ACTION_SET_TIMER API actually starts a timer\n 771 1. Press the "Start Timer" button.\n 772 2. Verify that a timer is started and NO timers UI is shown.\n 773 3. Verify that the timer named "Start Timer Test" rings after 30 seconds. Dismiss it.\n 774 4. Verify that the timer is deleted after the dismissal.\n 775 </string> 776 <string name="dc_start_timer_button">Start Timer</string> 777 778 <string name="dc_start_timer_with_ui_test">Start Timer With UI Test</string> 779 <string name="dc_start_timer_with_ui_test_info"> 780 This test verifies that the ACTION_SET_TIMER API actually starts a timer with UI\n 781 1. Press the "Start Timer" button.\n 782 2. Verify that a timer is started and the timers UI is shown with a timer named "Start Timer Test".\n 783 3. Verify that the timer rings after 30 seconds.\n 784 </string> 785 </resources> 786
