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_other">Other</string> 36 <string name="clear">Clear</string> 37 <string name="test_results_cleared">Test results cleared.</string> 38 <string name="view">View</string> 39 <string name="test_results_error">Couldn\'t create test results report.</string> 40 <string name="export">Export</string> 41 <string name="no_storage">Cannot save report to external storage, see log for details.</string> 42 <string name="report_saved">Report saved to: %s</string> 43 44 <!-- Strings for ReportViewerActivity --> 45 <string name="report_viewer">Report Viewer</string> 46 47 <!-- Strings for BackupTestActivity --> 48 <string name="backup_test">Data Backup Test</string> 49 <string name="backup_info">This test checks that data backup and automatic restore works 50 properly. The test activity lists some preferences and files that are backed up and 51 restored by the CTS Verifier. If backup and restore is working properly, these values 52 should be restored after running the backup manager, uninstalling the app, and reinstalling 53 the CTS Verifier. 54 \n\nPress the \"Generate Test Data\" to populate these values 55 and then follow the on screen instructions to finish the test. 56 </string> 57 <string name="bu_preferences">Preferences</string> 58 <string name="bu_files">Files</string> 59 <string name="bu_loading">Loading...</string> 60 <string name="bu_generate">Generate Test Data</string> 61 <string name="bu_generate_error">Error occurred while generating test data...</string> 62 <string name="bu_instructions">Random values for the preferences and files have been saved. 63 \n\nFollow the instructions below to check that the data backup and restore works: 64 \n\n1. Make sure backup and automatic restore are enabled in settings. Depending on the 65 backup transport supported by the device you may need to do additional steps. For instance 66 you may need to set a Google account as the backup account for the device. 67 \n\n2. Run the backup manager: adb shell bmgr run 68 \n\n3. Uninstall the program: adb uninstall com.android.cts.verifier 69 \n\n4. Reinstall the CTS Verifier and verify that the values are still the same. 70 </string> 71 <string name="bu_settings">Settings</string> 72 73 <!-- Strings for Device Administration tests --> 74 <string name="da_policy_serialization_test">Policy Serialization Test</string> 75 <string name="da_policy_serialization_info">This test checks that a device policy is properly 76 saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create 77 a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the 78 device and verify that all rows in the policy list are green. Red items indicate policy 79 settings that were not loaded properly. 80 </string> 81 <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device 82 policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your 83 device and return to this test in the CTS Verifier. 84 </string> 85 <string name="da_generate_policy">Generate Policy</string> 86 <string name="da_apply_policy">Apply Policy</string> 87 <string name="da_random_policy">Random policy generated.</string> 88 <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string> 89 <string name="da_password_quality">Password Quality</string> 90 <string name="da_password_quality_alphabetic">Alphabetic</string> 91 <string name="da_password_quality_alphanumeric">Alphanumeric</string> 92 <string name="da_password_quality_numeric">Numeric</string> 93 <string name="da_password_quality_something">Something</string> 94 <string name="da_password_minimum_length">Minimum Password Length</string> 95 <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string> 96 <string name="da_maximum_time_to_lock">Maximum Time to Lock</string> 97 <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string> 98 99 <string name="da_screen_lock_test">Screen Lock Test</string> 100 <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow 101 method immediately locks the screen. It should lock the screen immediately despite any 102 settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen. 103 Your screen should be locked and require the password to be entered. 104 </string> 105 <string name="da_force_lock">Force Lock</string> 106 <string name="da_lock_success">It appears the screen was locked successfully!</string> 107 <string name="da_lock_error">It does not look like the screen was locked...</string> 108 109 <!-- Strings for BluetoothActivity --> 110 <string name="bluetooth_test">Bluetooth Test</string> 111 <string name="bluetooth_test_info">The Bluetooth Control tests check whether or not the device 112 can disable and enable Bluetooth properly.\n\nThe Device Communication tests require two 113 devices to pair and exchange messages. The two devices must be: 114 \n\n1. a candidate device implementation running the software build to be tested 115 \n\n2. a separate device implementation already known to be compatible</string> 116 117 <string name="bt_control">Bluetooth Control</string> 118 <string name="bt_device_communication">Device Communication</string> 119 120 <string name="bt_toggle_bluetooth">Toggle Bluetooth</string> 121 <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string> 122 <string name="bt_enable_bluetooth">Enable Bluetooth</string> 123 <string name="bt_disable_bluetooth">Disable Bluetooth</string> 124 <string name="bt_disabling">Disabling Bluetooth...</string> 125 <string name="bt_disabling_error">Could not disable Bluetooth...</string> 126 127 <string name="bt_connection_access_server">Connection Access Server</string> 128 <string name="bt_connection_access_client">Connection Access Client</string> 129 <string name="bt_connection_access_server_info"> 130 Start the CTS Verifier on another device, start the Bluetooth test, and choose 131 \"Connection Access Client\" to setup the test. 132 \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together 133 using the \"Make Discoverable\" and \"Pick Server\" buttons. 134 \n\nA connection access request should appear on the server and enable the pass button. 135 </string> 136 <string name="bt_connection_access_client_info"> 137 Start the CTS Verifier on another device, start the Bluetooth test, and choose 138 \"Connection Access Server\" to complete the test. 139 \n\nMake the device acting as the server discoverable and connect to it via the 140 \"Pick Server\" button. Check that the server displays the connection access request 141 dialog. The client device does not need to do anything else. 142 </string> 143 <string name="bt_ca_dialog">Was the connection access request dialog shown?</string> 144 <string name="bt_ca_tips"> 145 Tap the \"Bluetooth Settings\" button and check that both devices are not paired 146 before running the test. 147 \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth 148 devices together and start the test. 149 </string> 150 151 <string name="bt_secure_server">Secure Server</string> 152 <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> 153 <string name="bt_insecure_server">Insecure Server</string> 154 <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> 155 <string name="bt_waiting">Waiting for client...</string> 156 <string name="bt_listening">Listening...</string> 157 <string name="bt_connecting">Connecting...</string> 158 <string name="bt_connected">Connected</string> 159 <string name="bt_received_messages">Received Messages</string> 160 <string name="bt_sent_messages">Sent Messages</string> 161 <string name="bt_no_messages">No messages</string> 162 <string name="bt_make_discoverable">Make Discoverable</string> 163 <string name="bt_pick_server">Pick Server</string> 164 <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string> 165 <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string> 166 167 <string name="bt_secure_client">Secure Client</string> 168 <string name="bt_insecure_client">Insecure Client</string> 169 170 <string name="bt_device_picker">Device Picker</string> 171 <string name="bt_paired_devices">Paired Devices</string> 172 <string name="bt_new_devices">New Devices</string> 173 <string name="bt_no_devices">No devices</string> 174 <string name="bt_scan">Scan for Devices</string> 175 <string name="bt_scanning">Scanning...</string> 176 <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> 177 <string name="bt_settings">Bluetooth Settings</string> 178 179 <!-- Strings for FeatureSummaryActivity --> 180 <string name="feature_summary">Hardware/Software Feature Summary</string> 181 <string name="feature_summary_info">This is a test for...</string> 182 <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string> 183 <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string> 184 <string name="fs_no_data">No data.</string> 185 <string name="fs_legend_good">standard feature reported by device</string> 186 <string name="fs_legend_indeterminate">optional feature not reported by device</string> 187 <string name="fs_legend_warning">non-standard feature reported by device</string> 188 <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string> 189 190 <string name="empty"></string> 191 192 <!-- Strings for Location tests --> 193 <string name="location_gps_test">GPS Test</string> 194 <string name="location_gps_test_info">This test verifies basic GPS behavior 195 and callback scheduling. 196 Make sure the device has line of sight to GPS satellites 197 (for example, outside, or near a window) 198 and then press OK to run the automated tests.</string> 199 200 <!-- Strings for NfcTestActivity --> 201 <string name="nfc_test">NFC Test</string> 202 <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with 203 NFC enabled to exchange messages. One device must be the candidate device running the 204 software build to be tested, while the other device must be an implementation already 205 known to be compatible.\n\nThe Tag Verification tests check that your 206 device can properly read and write to tags of different technologies. The MIFARE 207 Ultralight test is only applicable for devices that support it. 208 </string> 209 210 <string name="nfc_not_enabled">NFC is not enabled!</string> 211 <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the 212 button below to goto Settings and enable it.</string> 213 <string name="nfc_settings">NFC Settings</string> 214 215 <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string> 216 <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled. 217 Click the button below to goto NFC Sharing Settings and enable it.</string> 218 <string name="ndef_push_settings">NFC Sharing Settings</string> 219 220 <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string> 221 <string name="nfc_ndef_push_sender">NDEF Push Sender</string> 222 <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string> 223 224 <string name="nfc_tag_verification">Tag Verification</string> 225 <string name="nfc_ndef">NDEF</string> 226 <string name="nfc_mifare_ultralight">MIFARE Ultralight</string> 227 228 <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on 229 another device and touch the devices back to back. The receiver should show a 230 dialog indicating it has successfully received the correct message!</string> 231 <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another 232 device running the \"CTS Verifier NDEF Receiver\"...</string> 233 234 <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on 235 another device and touch the devices back to back. The receiver should show a 236 dialog indicating it has successfully received the correct message!</string> 237 <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another 238 device running the \"CTS Verifier NDEF Sender\"...</string> 239 <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push 240 message.</string> 241 <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push 242 message.</string> 243 244 <string name="nfc_tag_verifier">NFC Tag Verifier</string> 245 <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read 246 a tag of the chosen technology.</string> 247 248 <string name="nfc_scan_tag">Place device on a writable %s tag...</string> 249 <string name="nfc_write_tag_title">Writable tag discovered!</string> 250 <string name="nfc_write_tag_message">Press OK to write to this tag...</string> 251 <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string> 252 <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string> 253 <string name="nfc_no_tech">No tag technologies detected...</string> 254 255 <string name="nfc_writing_tag">Writing NFC tag...</string> 256 <string name="nfc_writing_tag_error">Error writing NFC tag...</string> 257 <string name="nfc_reading_tag">Reading NFC tag...</string> 258 <string name="nfc_reading_tag_error">Error reading NFC tag...</string> 259 260 <string name="nfc_result_success">Test passed!</string> 261 <string name="nfc_result_failure">Test failed!</string> 262 263 <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string> 264 <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string> 265 266 <!-- Strings for AccelerometerTestActivity and GyroscopeTestActivity --> 267 <string name="snsr_accel_test">Accelerometer Test</string> 268 <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> 269 270 <string name="snsr_gyro_test">Gyroscope Test</string> 271 <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> 272 <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string> 273 <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string> 274 <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> 275 <string name="snsr_gyro_test_degrees_title">Wrong units?</string> 276 <string name="snsr_gyro_test_degrees_message">These values looks like degrees per second. These should be radians per second!</string> 277 278 <!-- Strings for SuidFilesActivity --> 279 <string name="suid_files">SUID File Scanner</string> 280 <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> 281 <string name="scanning_directory">Scanning directory...</string> 282 <string name="file_status">User: %1$s\nGroup: %2$s\nPermissions: %3$s\nPath: %4$s</string> 283 <string name="no_file_status">Could not stat file...</string> 284 <string name="congratulations">Congratulations!</string> 285 <string name="no_suid_files">No unauthorized suid files detected!</string> 286 287 <!-- Strings for Camera Analyzer --> 288 <string name="camera_analyzer">Camera Analyzer</string> 289 <string name="ca_find_checkerboard_label">Find target</string> 290 <string name="ca_check_formats_label">Output formats</string> 291 <string name="ca_exposure_test_label">Exposure Comp.</string> 292 <string name="ca_result_label">Results will be here</string> 293 <string name="ca_wb_test_label">White Balance</string> 294 <string name="ca_lock_test_label">AE Lock</string> 295 <string name="ca_metering_label">Metering Area</string> 296 <string name="ca_focus_modes_label">Focus Modes</string> 297 <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> 298 299 <!-- Strings for Camera Orientation --> 300 <string name="camera_orientation">Camera Orientation</string> 301 <string name="co_info">This test verifies the orientation capabilities of 302 camera preview and capture.\n - The left view shows a preview window rotated 303 clockwise by a given magnitude of degrees.\n - The right view, after taking 304 a photo, shows the captured image.\n - For each camera and orientation, both 305 the left and right views should appear rotated clockwise by the amount of 306 degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose 307 \"Fail\".\n - For front-facing cameras, the test will horizontally mirror 308 the captured image prior to rotation, in attempt to make the left and right 309 views appear the same.\n - The physical orientation of the device does not 310 matter.\n - Read the message above the \"Take Photo\" button for 311 step-by-step instructions. 312 </string> 313 <string name="co_preview_label">Camera preview</string> 314 <string name="co_format_label">Oriented photo</string> 315 <string name="co_camera_label">Camera:</string> 316 <string name="co_orientation_label">Orientation</string> 317 <string name="co_orientation_direction_label">clockwise</string> 318 <string name="co_instruction_heading_label">Instruction:</string> 319 <string name="co_instruction_text_photo_label">Take a photo</string> 320 <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> 321 <string name="co_instruction_text_extra_label">(mirrored horizontally prior to rotation, since camera is front-facing)</string> 322 <string name="co_photo_button_caption">Take Photo</string> 323 324 <!-- Strings for Camera Formats --> 325 <string name="camera_format">Camera Formats</string> 326 <string name="cf_info">This test checks that all the supported 327 output formats for camera preview callbacks work correctly, and 328 that the mandatory formats are available. \n - The left view shows 329 a standard preview window. \n - The right view shows the output 330 processed from camera preview callbacks. \n - For each camera, 331 resolution, and format combination in the dropdowns, the right 332 view should look the same as the left, and neither should have 333 streaks, lines, or other artifacts. \n - For front-facing cameras, 334 the right view must be horizontally mirrored relative to the left 335 view.\n - Note that the frame rate of the right view may be much 336 lower than on the left; this is not an indication of a failed 337 test. 338 </string> 339 <string name="cf_preview_label">Normal preview</string> 340 <string name="cf_format_label">Processed callback data</string> 341 342 <!-- Strings for USB accessory test activity --> 343 <string name="usb_accessory_test">USB Accessory Test</string> 344 <string name="usb_accessory_test_info"> 345 1. Connect your Android device to a computer and run the \'cts-usb-accessory\' program 346 included with the CTS Verifier bundle. 347 \n\n2. If you have not started the CTS Verifier, press \'OK\' when asked to open the CTS 348 Verifier when the accessory is connected. \n\nIf you are already in this test, 349 then you can press \'Cancel\' but press \'OK\' in the next dialog asking whether to allow 350 CTS Verifier to access the accessory. 351 \n\n3. You should see the accessory and the CTS Verifier display a series of messages 352 which indicates that the accessory support is working properly. 353 </string> 354 <string name="usb_not_available_title">USB accessory feature is not available?</string> 355 <string name="usb_not_available_message">If your device is supposed to support USB accessories, your API implementation is not behaving correctly!</string> 356 <string name="usb_received_messages">Received Messages</string> 357 <string name="usb_sent_messages">Sent Messages</string> 358 <string name="usb_no_messages">No messages</string> 359 <string name="usb_message_thread_started">Starting message processing...</string> 360 <string name="usb_message_thread_exception">Exception occurred while processing a message...</string> 361 <string name="usb_message_thread_ended">Stopping message processing...</string> 362 <string name="usb_test_passed">Received all expected messages. Pass button enabled!</string> 363 <string name="usb_file_descriptor_error">Could not open file descriptor for USB accessory... try reconnecting and restarting the accessory?</string> 364 365 <!-- Strings for StreamingVideoActivity --> 366 <string name="streaming_video">Streaming Video Quality Verifier</string> 367 <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> 368 <string name="sv_no_data">No videos.</string> 369 <string name="sv_failed_title">Test Failed</string> 370 <string name="sv_failed_message">Unable to play stream. See log for details.</string> 371 372 <!-- Strings for P2pTestActivity --> 373 <string name="p2p_test">Wi-Fi Direct Test</string> 374 <string name="p2p_test_info"> 375 The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange 376 messages. One device must be the candidate device running the software build to 377 be tested, while the other device must be an implementation already known to be 378 compatible.\n\nOne device should start the requester test, and the other should 379 start the responder test. Your device must pass both requester and responder 380 tests. 381 </string> 382 <string name="p2p_group_formation">Group Formation</string> 383 <string name="p2p_join">Group Join</string> 384 <string name="p2p_service_discovery">Service Discovery</string> 385 386 <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string> 387 <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string> 388 <string name="p2p_group_owner_test">Group Owner Test</string> 389 <string name="p2p_group_client_test">Group Client Test</string> 390 <string name="p2p_service_discovery_responder_test"> 391 Service Discovery Responder Test</string> 392 <string name="p2p_service_discovery_requester_test"> 393 Service Discovery Requester Test</string> 394 395 <string name="p2p_go_neg_responder">GO Negotiation Responder</string> 396 <string name="p2p_go_neg_requester">GO Negotiation Requester</string> 397 <string name="p2p_accept_client">Group Owner</string> 398 <string name="p2p_join_go">Group Client</string> 399 <string name="p2p_service_discovery_responder">Service Discovery Responder</string> 400 <string name="p2p_service_discovery_requester">Service Discovery Requester</string> 401 402 <string name="p2p_go_neg_responder_info"> 403 Start the \"GO Negotiation Requester Test\" on the other device and follow 404 the instructions.</string> 405 <string name="p2p_accept_client_info"> 406 Start the \"Group Client Test\" on the other device and follow 407 the instructions.</string> 408 <string name="p2p_service_discovery_responder_info"> 409 Start the \"Service Discovery Requester Test\" on the other device and follow 410 the instructions.</string> 411 412 <string name="p2p_go_neg_requester_info"> 413 Start the \"GO Negotiation Responder Test\" on the other device. 414 Then run each test individually by clicking on it\'s name.</string> 415 <string name="p2p_join_go_info"> 416 Start the \"Group Owner Test\" on the other device. 417 Then run each test individually by clicking on it\'s name.</string> 418 <string name="p2p_service_discovery_requester_info"> 419 Start the \"Service Discovery Responder Test\" on the other device. 420 Then run each test individually by clicking on it\'s name.</string> 421 422 <string name="p2p_not_enabled">Wi-Fi is not enabled</string> 423 <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled. 424 Click the button below to go to system settings and enable Wi-Fi.</string> 425 <string name="p2p_settings">Wi-Fi Direct Settings</string> 426 427 <string name="p2p_result_success">Test passed successfully.</string> 428 429 <string name="p2p_go_neg_responder_ready"> 430 The go negotiation responder is now ready to start. Start 431 the \"GO Negotiation Requester Test\" on the other device. 432 Keep the screen here until all tests on the other device are 433 finished.</string> 434 <string name="p2p_go_ready"> 435 The group owner is now ready to start. Start the \"Join 436 Group Test\" on the other device. 437 Keep the screen here until all tests on the other device are 438 finished.</string> 439 <string name="p2p_service_responder_ready"> 440 The service responder is now ready to start. Start the 441 \"Service Discovery Requester Test\" on the other device. 442 Keep the screen here until all tests on the other device are 443 finished.</string> 444 445 <string name="p2p_setup_error"> 446 Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string> 447 <string name="p2p_unexpected_error"> 448 Test failed.\n\nUnexpected error. Check logcat.</string> 449 <string name="p2p_add_local_service_error"> 450 Test failed.\n\nFailed to add local service.</string> 451 <string name="p2p_add_service_request_error"> 452 Test failed.\n\nFailed to add service request.</string> 453 <string name="p2p_remove_service_request_error"> 454 Test failed.\n\nFailed to remove service request.</string> 455 <string name="p2p_clear_service_requests_error"> 456 Test failed.\n\nFailed to clear service requests.</string> 457 <string name="p2p_connect_error"> 458 Test failed.\n\nFailed to start a p2p connection to the target device.</string> 459 <string name="p2p_remove_group_error"> 460 Test failed.\n\nFailed to remove a p2p group.</string> 461 <string name="p2p_discover_peers_error"> 462 Test failed.\n\nFailed to discover peers.</string> 463 <string name="p2p_discover_services_error"> 464 Test failed.\n\nFailed to discover services.</string> 465 <string name="p2p_ceate_group_error"> 466 Test failed.\n\nFailed to start up group owner.</string> 467 <string name="p2p_no_service_requests_error"> 468 Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string> 469 <string name="p2p_receive_invalid_response_error"> 470 Test failed.\n\nReceived an invalid message or could not receive 471 the expected message.\n\n</string> 472 <string name="p2p_target_not_found_error">Test failed.\n\n 473 The target responder device was NOT found. Start up the responder 474 test on the other device, then run the test again.</string> 475 <string name="p2p_target_invalid_role_error">Test failed.\n\n 476 The target responder must be p2p device. However, the target responder 477 device was group owner. Check the test case on the other device.</string> 478 <string name="p2p_target_invalid_role_error2">Test failed.\n\n 479 The target responder must be group owner. However, the target responder 480 device was p2p device. Check the test case on the other device.</string> 481 <string name="p2p_connection_error"> 482 Test failed.\n\nFailed to establish a p2p connection.</string> 483 <string name="p2p_detect_disconnection_error"> 484 Test failed.\n\nFailed to detect client disconnection.</string> 485 <string name="p2p_disconnect_error"> 486 Test failed.\n\nFailed to disconnect a p2p connection.</string> 487 488 <string name="p2p_search_target">Search Target</string> 489 <string name="p2p_searching_target">Searching for target device ...</string> 490 <string name="p2p_checking_serv_capab">Checking the service discovery 491 capability ...</string> 492 <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n 493 Click the \"OK\" button on the other device to accept the connection 494 request from this device.</string> 495 <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n 496 Enter the pin number on the other device.</string> 497 <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to 498 connect ...</string> 499 <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer 500 to disconnect ...</string> 501 </resources> 502
