Brian Muramatsu | 70a9e3f | 2010-06-25 15:27:09 -0700 | [diff] [blame] | 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 |
Jeff Davidson | 112f279 | 2011-08-22 09:46:46 -0700 | [diff] [blame] | 7 | |
Brian Muramatsu | 70a9e3f | 2010-06-25 15:27:09 -0700 | [diff] [blame] | 8 | http://www.apache.org/licenses/LICENSE-2.0 |
Jeff Davidson | 112f279 | 2011-08-22 09:46:46 -0700 | [diff] [blame] | 9 | |
Brian Muramatsu | 70a9e3f | 2010-06-25 15:27:09 -0700 | [diff] [blame] | 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> |
Isaac Katzenelson | d96d066 | 2013-10-02 17:06:28 -0700 | [diff] [blame] | 18 | |
Brian Muramatsu | da429d7 | 2012-06-14 12:45:22 -0700 | [diff] [blame] | 19 | <string name="title_version">CTS Verifier %1$s</string> |
Brian Muramatsu | e118187 | 2010-08-20 12:59:39 -0700 | [diff] [blame] | 20 | |
Brian Muramatsu | ff1038f | 2010-08-26 14:37:08 -0700 | [diff] [blame] | 21 | <string name="pass_button_text">Pass</string> |
Brian Muramatsu | 14e1cbb | 2010-09-13 18:33:39 -0700 | [diff] [blame] | 22 | <string name="info_button_text">Info</string> |
Brian Muramatsu | ff1038f | 2010-08-26 14:37:08 -0700 | [diff] [blame] | 23 | <string name="fail_button_text">Fail</string> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 24 | <string name="next_button_text">Next</string> |
Brian Muramatsu | ff1038f | 2010-08-26 14:37:08 -0700 | [diff] [blame] | 25 | |
Brian Muramatsu | 78d2c1d | 2010-08-16 15:22:30 -0700 | [diff] [blame] | 26 | <!-- Strings for TestListActivity --> |
Brian Muramatsu | f894620 | 2010-11-09 13:43:39 -0800 | [diff] [blame] | 27 | <string name="test_category_audio">Audio</string> |
Brian Muramatsu | 1f54980 | 2011-06-09 15:25:28 -0700 | [diff] [blame] | 28 | <string name="test_category_camera">Camera</string> |
Brian Muramatsu | 713049d | 2011-06-23 18:35:36 -0700 | [diff] [blame] | 29 | <string name="test_category_device_admin">Device Administration</string> |
Brian Muramatsu | 12c8691 | 2011-07-21 17:26:46 -0700 | [diff] [blame] | 30 | <string name="test_category_hardware">Hardware</string> |
Brian Muramatsu | e891acb | 2011-05-19 16:02:39 -0700 | [diff] [blame] | 31 | <string name="test_category_networking">Networking</string> |
Brian Muramatsu | 78d2c1d | 2010-08-16 15:22:30 -0700 | [diff] [blame] | 32 | <string name="test_category_sensors">Sensors</string> |
Tom O'Neill | cd4fa02 | 2013-12-13 17:27:46 -0800 | [diff] [blame] | 33 | <string name="test_category_location">Location</string> |
Brian Muramatsu | 78d2c1d | 2010-08-16 15:22:30 -0700 | [diff] [blame] | 34 | <string name="test_category_security">Security</string> |
Jeff Davidson | 112f279 | 2011-08-22 09:46:46 -0700 | [diff] [blame] | 35 | <string name="test_category_streaming">Streaming</string> |
Brian Muramatsu | 78d2c1d | 2010-08-16 15:22:30 -0700 | [diff] [blame] | 36 | <string name="test_category_features">Features</string> |
Isaac Katzenelson | d96d066 | 2013-10-02 17:06:28 -0700 | [diff] [blame] | 37 | <string name="test_category_deskclock">Clock</string> |
Brian Muramatsu | 78d2c1d | 2010-08-16 15:22:30 -0700 | [diff] [blame] | 38 | <string name="test_category_other">Other</string> |
Brian Muramatsu | ac00737 | 2010-08-18 11:02:28 -0700 | [diff] [blame] | 39 | <string name="clear">Clear</string> |
| 40 | <string name="test_results_cleared">Test results cleared.</string> |
Brian Muramatsu | 52f3b6f | 2011-09-23 12:09:59 -0700 | [diff] [blame] | 41 | <string name="view">View</string> |
Brian Muramatsu | 82ab52a | 2011-06-27 14:02:12 -0700 | [diff] [blame] | 42 | <string name="test_results_error">Couldn\'t create test results report.</string> |
Jeff Davidson | 4c3bbd8 | 2011-08-02 11:51:43 -0700 | [diff] [blame] | 43 | <string name="export">Export</string> |
| 44 | <string name="no_storage">Cannot save report to external storage, see log for details.</string> |
| 45 | <string name="report_saved">Report saved to: %s</string> |
Dan Morrill | 5df275b | 2010-08-11 12:19:19 -0700 | [diff] [blame] | 46 | |
Brian Muramatsu | 52f3b6f | 2011-09-23 12:09:59 -0700 | [diff] [blame] | 47 | <!-- Strings for ReportViewerActivity --> |
| 48 | <string name="report_viewer">Report Viewer</string> |
| 49 | |
Brian Muramatsu | 0ac3cdf | 2011-08-03 11:47:10 -0700 | [diff] [blame] | 50 | <!-- Strings for BackupTestActivity --> |
| 51 | <string name="backup_test">Data Backup Test</string> |
Jeff Davidson | 112f279 | 2011-08-22 09:46:46 -0700 | [diff] [blame] | 52 | <string name="backup_info">This test checks that data backup and automatic restore works |
Brian Muramatsu | 0ac3cdf | 2011-08-03 11:47:10 -0700 | [diff] [blame] | 53 | properly. The test activity lists some preferences and files that are backed up and |
| 54 | restored by the CTS Verifier. If backup and restore is working properly, these values |
| 55 | should be restored after running the backup manager, uninstalling the app, and reinstalling |
| 56 | the CTS Verifier. |
| 57 | \n\nPress the \"Generate Test Data\" to populate these values |
| 58 | and then follow the on screen instructions to finish the test. |
| 59 | </string> |
| 60 | <string name="bu_preferences">Preferences</string> |
| 61 | <string name="bu_files">Files</string> |
| 62 | <string name="bu_loading">Loading...</string> |
| 63 | <string name="bu_generate">Generate Test Data</string> |
| 64 | <string name="bu_generate_error">Error occurred while generating test data...</string> |
| 65 | <string name="bu_instructions">Random values for the preferences and files have been saved. |
| 66 | \n\nFollow the instructions below to check that the data backup and restore works: |
Jeff Davidson | 112f279 | 2011-08-22 09:46:46 -0700 | [diff] [blame] | 67 | \n\n1. Make sure backup and automatic restore are enabled in settings. Depending on the |
| 68 | backup transport supported by the device you may need to do additional steps. For instance |
Brian Muramatsu | 0ac3cdf | 2011-08-03 11:47:10 -0700 | [diff] [blame] | 69 | you may need to set a Google account as the backup account for the device. |
| 70 | \n\n2. Run the backup manager: adb shell bmgr run |
| 71 | \n\n3. Uninstall the program: adb uninstall com.android.cts.verifier |
| 72 | \n\n4. Reinstall the CTS Verifier and verify that the values are still the same. |
| 73 | </string> |
| 74 | <string name="bu_settings">Settings</string> |
| 75 | |
Brian Muramatsu | 713049d | 2011-06-23 18:35:36 -0700 | [diff] [blame] | 76 | <!-- Strings for Device Administration tests --> |
| 77 | <string name="da_policy_serialization_test">Policy Serialization Test</string> |
| 78 | <string name="da_policy_serialization_info">This test checks that a device policy is properly |
| 79 | saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create |
| 80 | a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the |
| 81 | device and verify that all rows in the policy list are green. Red items indicate policy |
| 82 | settings that were not loaded properly. |
| 83 | </string> |
| 84 | <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device |
| 85 | policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your |
| 86 | device and return to this test in the CTS Verifier. |
| 87 | </string> |
| 88 | <string name="da_generate_policy">Generate Policy</string> |
| 89 | <string name="da_apply_policy">Apply Policy</string> |
| 90 | <string name="da_random_policy">Random policy generated.</string> |
| 91 | <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string> |
| 92 | <string name="da_password_quality">Password Quality</string> |
| 93 | <string name="da_password_quality_alphabetic">Alphabetic</string> |
| 94 | <string name="da_password_quality_alphanumeric">Alphanumeric</string> |
| 95 | <string name="da_password_quality_numeric">Numeric</string> |
| 96 | <string name="da_password_quality_something">Something</string> |
Brian Muramatsu | 713049d | 2011-06-23 18:35:36 -0700 | [diff] [blame] | 97 | <string name="da_password_minimum_length">Minimum Password Length</string> |
| 98 | <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string> |
| 99 | <string name="da_maximum_time_to_lock">Maximum Time to Lock</string> |
| 100 | <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string> |
| 101 | |
| 102 | <string name="da_screen_lock_test">Screen Lock Test</string> |
| 103 | <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow |
| 104 | method immediately locks the screen. It should lock the screen immediately despite any |
Christine Chen | 523d04c | 2011-09-22 11:45:50 -0700 | [diff] [blame] | 105 | settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen. |
Brian Muramatsu | 76c5025 | 2011-06-29 17:12:29 -0700 | [diff] [blame] | 106 | Your screen should be locked and require the password to be entered. |
Brian Muramatsu | 713049d | 2011-06-23 18:35:36 -0700 | [diff] [blame] | 107 | </string> |
| 108 | <string name="da_force_lock">Force Lock</string> |
Brian Muramatsu | 713049d | 2011-06-23 18:35:36 -0700 | [diff] [blame] | 109 | <string name="da_lock_success">It appears the screen was locked successfully!</string> |
| 110 | <string name="da_lock_error">It does not look like the screen was locked...</string> |
| 111 | |
Brian Muramatsu | e891acb | 2011-05-19 16:02:39 -0700 | [diff] [blame] | 112 | <!-- Strings for BluetoothActivity --> |
| 113 | <string name="bluetooth_test">Bluetooth Test</string> |
Jeff Davidson | 112f279 | 2011-08-22 09:46:46 -0700 | [diff] [blame] | 114 | <string name="bluetooth_test_info">The Bluetooth Control tests check whether or not the device |
Brian Muramatsu | e891acb | 2011-05-19 16:02:39 -0700 | [diff] [blame] | 115 | can disable and enable Bluetooth properly.\n\nThe Device Communication tests require two |
| 116 | devices to pair and exchange messages. The two devices must be: |
| 117 | \n\n1. a candidate device implementation running the software build to be tested |
| 118 | \n\n2. a separate device implementation already known to be compatible</string> |
| 119 | |
Brian Muramatsu | e891acb | 2011-05-19 16:02:39 -0700 | [diff] [blame] | 120 | <string name="bt_control">Bluetooth Control</string> |
| 121 | <string name="bt_device_communication">Device Communication</string> |
John Du | 7346236 | 2013-07-26 12:28:28 -0700 | [diff] [blame] | 122 | <string name="bt_le">Bluetooth Low Energy</string> |
Brian Muramatsu | e891acb | 2011-05-19 16:02:39 -0700 | [diff] [blame] | 123 | |
| 124 | <string name="bt_toggle_bluetooth">Toggle Bluetooth</string> |
| 125 | <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string> |
| 126 | <string name="bt_enable_bluetooth">Enable Bluetooth</string> |
| 127 | <string name="bt_disable_bluetooth">Disable Bluetooth</string> |
| 128 | <string name="bt_disabling">Disabling Bluetooth...</string> |
| 129 | <string name="bt_disabling_error">Could not disable Bluetooth...</string> |
| 130 | |
Brian Muramatsu | 0822bf4 | 2011-09-12 12:29:32 -0700 | [diff] [blame] | 131 | <string name="bt_connection_access_server">Connection Access Server</string> |
| 132 | <string name="bt_connection_access_client">Connection Access Client</string> |
| 133 | <string name="bt_connection_access_server_info"> |
| 134 | Start the CTS Verifier on another device, start the Bluetooth test, and choose |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 135 | \"Connection Access Client\" to setup the test. |
| 136 | \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together |
Brian Muramatsu | 0822bf4 | 2011-09-12 12:29:32 -0700 | [diff] [blame] | 137 | using the \"Make Discoverable\" and \"Pick Server\" buttons. |
| 138 | \n\nA connection access request should appear on the server and enable the pass button. |
| 139 | </string> |
| 140 | <string name="bt_connection_access_client_info"> |
| 141 | Start the CTS Verifier on another device, start the Bluetooth test, and choose |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 142 | \"Connection Access Server\" to complete the test. |
| 143 | \n\nMake the device acting as the server discoverable and connect to it via the |
| 144 | \"Pick Server\" button. Check that the server displays the connection access request |
Brian Muramatsu | 0822bf4 | 2011-09-12 12:29:32 -0700 | [diff] [blame] | 145 | dialog. The client device does not need to do anything else. |
| 146 | </string> |
| 147 | <string name="bt_ca_dialog">Was the connection access request dialog shown?</string> |
| 148 | <string name="bt_ca_tips"> |
| 149 | Tap the \"Bluetooth Settings\" button and check that both devices are not paired |
| 150 | before running the test. |
| 151 | \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth |
| 152 | devices together and start the test. |
| 153 | </string> |
| 154 | |
Brian Muramatsu | e891acb | 2011-05-19 16:02:39 -0700 | [diff] [blame] | 155 | <string name="bt_secure_server">Secure Server</string> |
| 156 | <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> |
| 157 | <string name="bt_insecure_server">Insecure Server</string> |
| 158 | <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> |
| 159 | <string name="bt_waiting">Waiting for client...</string> |
Brian Muramatsu | 0822bf4 | 2011-09-12 12:29:32 -0700 | [diff] [blame] | 160 | <string name="bt_listening">Listening...</string> |
Brian Muramatsu | e891acb | 2011-05-19 16:02:39 -0700 | [diff] [blame] | 161 | <string name="bt_connecting">Connecting...</string> |
Brian Muramatsu | 0822bf4 | 2011-09-12 12:29:32 -0700 | [diff] [blame] | 162 | <string name="bt_connected">Connected</string> |
Brian Muramatsu | e891acb | 2011-05-19 16:02:39 -0700 | [diff] [blame] | 163 | <string name="bt_received_messages">Received Messages</string> |
| 164 | <string name="bt_sent_messages">Sent Messages</string> |
| 165 | <string name="bt_no_messages">No messages</string> |
| 166 | <string name="bt_make_discoverable">Make Discoverable</string> |
Brian Muramatsu | 0822bf4 | 2011-09-12 12:29:32 -0700 | [diff] [blame] | 167 | <string name="bt_pick_server">Pick Server</string> |
Brian Muramatsu | 8b98f7c | 2011-06-08 14:50:24 -0700 | [diff] [blame] | 168 | <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string> |
| 169 | <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string> |
Brian Muramatsu | e891acb | 2011-05-19 16:02:39 -0700 | [diff] [blame] | 170 | |
| 171 | <string name="bt_secure_client">Secure Client</string> |
| 172 | <string name="bt_insecure_client">Insecure Client</string> |
| 173 | |
| 174 | <string name="bt_device_picker">Device Picker</string> |
| 175 | <string name="bt_paired_devices">Paired Devices</string> |
| 176 | <string name="bt_new_devices">New Devices</string> |
| 177 | <string name="bt_no_devices">No devices</string> |
| 178 | <string name="bt_scan">Scan for Devices</string> |
| 179 | <string name="bt_scanning">Scanning...</string> |
| 180 | <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> |
| 181 | <string name="bt_settings">Bluetooth Settings</string> |
| 182 | |
John Du | 7346236 | 2013-07-26 12:28:28 -0700 | [diff] [blame] | 183 | <!-- BLE client side strings --> |
| 184 | <string name="ble_client_service_name">Bluetooth LE GATT Client Handler Service</string> |
| 185 | <string name="ble_client_test_name">BLE Client Test</string> |
| 186 | <string name="ble_client_connect_name">1. BLE Client Connect</string> |
| 187 | <string name="ble_discover_service_name">2. BLE Discover Service</string> |
| 188 | <string name="ble_client_characteristic_name">3. BLE Read/Write Characteristic</string> |
| 189 | <string name="ble_reliable_write_name">4. BLE Reliable Write</string> |
| 190 | <string name="ble_notify_characteristic_name">5. BLE Notify Characteristic</string> |
| 191 | <string name="ble_client_descriptor_name">6. BLE Read/Write Descriptor</string> |
| 192 | <string name="ble_read_rssi_name">7. BLE Read RSSI</string> |
| 193 | <string name="ble_client_disconnect_name">8. BLE Client Disconnect</string> |
| 194 | <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> |
| 195 | <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> |
| 196 | <string name="ble_discover_service_info">Verify that the service is discovered when you press the "Discover Service" button.</string> |
| 197 | <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> |
| 198 | <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> |
| 199 | <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> |
| 200 | <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> |
| 201 | <string name="ble_client_disconnect_info">Verify that the device is disconnected when you press the "Disconnect" button</string> |
| 202 | <string name="ble_address">Bluetooth address</string> |
| 203 | <string name="ble_connect">Connect</string> |
| 204 | <string name="ble_discover_service">Discover service</string> |
| 205 | <string name="ble_write_hint">Nothing to write yet</string> |
| 206 | <string name="ble_read_hint">Nothing read yet</string> |
| 207 | <string name="ble_write">Write</string> |
| 208 | <string name="ble_read">Read</string> |
| 209 | <string name="ble_begin_write">Begin write</string> |
| 210 | <string name="ble_execute_write">Execute write</string> |
| 211 | <string name="ble_begin_notification">Begin notification</string> |
| 212 | <string name="ble_stop_notification">Stop notification</string> |
| 213 | <string name="ble_waiting_notification">Waiting on notification</string> |
| 214 | <string name="ble_read_rssi">Read RSSI</string> |
| 215 | <string name="ble_disconnect">Disconnect</string> |
| 216 | |
| 217 | <!-- BLE server side strings --> |
| 218 | <string name="ble_server_service_name">Bluetooth LE GATT Server Handler Service</string> |
| 219 | <string name="ble_server_start_name">BLE Server Test</string> |
| 220 | <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> |
| 221 | <string name="ble_server_receiving_connect">Waiting on connection from BLE client.</string> |
| 222 | <string name="ble_server_add_service">Adding service to BLE server.</string> |
| 223 | <string name="ble_server_write_characteristic">Waiting on write characteristic request</string> |
| 224 | <string name="ble_server_read_characteristic">Waiting on read characteristic request</string> |
| 225 | <string name="ble_server_write_descriptor">Waiting on write descriptor request</string> |
| 226 | <string name="ble_server_read_descriptor">Waiting on read descriptor request</string> |
| 227 | <string name="ble_server_reliable_write">Waiting on reliable write from client</string> |
| 228 | <string name="ble_server_receiving_disconnect">Waiting on disconnection from BLE client</string> |
| 229 | |
Yicheng Fan | a673692 | 2014-07-08 14:53:55 -0700 | [diff] [blame] | 230 | <!-- BLE advertiser side strings --> |
| 231 | <string name="ble_advertiser_test_name">BLE Advertiser Test</string> |
| 232 | <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> |
| 233 | <string name="ble_advertiser_service_name">Bluetooth LE Advertiser Handler Service</string> |
Yicheng Fan | a673692 | 2014-07-08 14:53:55 -0700 | [diff] [blame] | 234 | <string name="ble_privacy_mac_name">BLE Privacy Mac</string> |
| 235 | <string name="ble_privacy_mac_info">BLE Advertiser should advertise in non-repeating MAC address.</string> |
Yicheng Fan | 036fc0c | 2014-07-21 19:47:02 -0700 | [diff] [blame] | 236 | <string name="ble_power_level_name">BLE Tx Power Level</string> |
| 237 | <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> |
Yicheng Fan | cb7cbc6 | 2014-08-13 18:11:30 -0700 | [diff] [blame] | 238 | <string name="ble_advertiser_scan_filter_name">BLE Hardware Scan Filter</string> |
| 239 | <string name="ble_advertiser_scan_filter_info">BLE Advertiser advertises with 2 different data separately. One can wake up the scanner, the other cannot.</string> |
| 240 | <string name="ble_advertiser_scannable">Scannable advertising</string> |
| 241 | <string name="ble_advertiser_unscannable">Unscannble advertising</string> |
| 242 | <string name="ble_advertiser_start">Start</string> |
| 243 | <string name="ble_advertiser_stop">Stop</string> |
Yicheng Fan | a673692 | 2014-07-08 14:53:55 -0700 | [diff] [blame] | 244 | |
| 245 | <!-- BLE scanner side strings --> |
Yicheng Fan | 036fc0c | 2014-07-21 19:47:02 -0700 | [diff] [blame] | 246 | <string name="ble_scanner_test_name">BLE Scanner Test</string> |
Yicheng Fan | a673692 | 2014-07-08 14:53:55 -0700 | [diff] [blame] | 247 | <string name="ble_scanner_service_name">Bluetooth LE Scanner Handler Service</string> |
Yicheng Fan | 036fc0c | 2014-07-21 19:47:02 -0700 | [diff] [blame] | 248 | <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> |
Yicheng Fan | a673692 | 2014-07-08 14:53:55 -0700 | [diff] [blame] | 249 | <string name="ble_scanner_privacy_mac">Hold for 15 min to see if receive a different MAC address from advertiser.</string> |
Yicheng Fan | 036fc0c | 2014-07-21 19:47:02 -0700 | [diff] [blame] | 250 | <string name="ble_ultra_low">Ultra low</string> |
| 251 | <string name="ble_low">Low</string> |
| 252 | <string name="ble_medium">Medium</string> |
| 253 | <string name="ble_high">High</string> |
Yicheng Fan | cb7cbc6 | 2014-08-13 18:11:30 -0700 | [diff] [blame] | 254 | <string name="ble_scanner_scan_filter_name">BLE Hardware Scan Filter</string> |
| 255 | <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> |
| 256 | <string name="ble_scan_with_filter">Scan with filter</string> |
| 257 | <string name="ble_scan_without_filter">Scan without filter</string> |
Yicheng Fan | a673692 | 2014-07-08 14:53:55 -0700 | [diff] [blame] | 258 | |
Brian Muramatsu | accc684 | 2010-08-11 18:57:27 -0700 | [diff] [blame] | 259 | <!-- Strings for FeatureSummaryActivity --> |
Dan Morrill | 5df275b | 2010-08-11 12:19:19 -0700 | [diff] [blame] | 260 | <string name="feature_summary">Hardware/Software Feature Summary</string> |
Brian Muramatsu | 14e1cbb | 2010-09-13 18:33:39 -0700 | [diff] [blame] | 261 | <string name="feature_summary_info">This is a test for...</string> |
Dan Morrill | 5df275b | 2010-08-11 12:19:19 -0700 | [diff] [blame] | 262 | <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string> |
| 263 | <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string> |
| 264 | <string name="fs_no_data">No data.</string> |
Dan Morrill | 71351d8 | 2010-10-20 15:26:00 -0700 | [diff] [blame] | 265 | <string name="fs_legend_good">standard feature reported by device</string> |
| 266 | <string name="fs_legend_indeterminate">optional feature not reported by device</string> |
| 267 | <string name="fs_legend_warning">non-standard feature reported by device</string> |
| 268 | <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string> |
| 269 | |
Dan Morrill | 5df275b | 2010-08-11 12:19:19 -0700 | [diff] [blame] | 270 | <string name="empty"></string> |
| 271 | |
Nick Pelly | 1fe0897 | 2012-05-14 17:35:58 -0700 | [diff] [blame] | 272 | <!-- Strings for Location tests --> |
| 273 | <string name="location_gps_test">GPS Test</string> |
| 274 | <string name="location_gps_test_info">This test verifies basic GPS behavior |
| 275 | and callback scheduling. |
| 276 | Make sure the device has line of sight to GPS satellites |
| 277 | (for example, outside, or near a window) |
| 278 | and then press OK to run the automated tests.</string> |
| 279 | |
Brian Muramatsu | 984b78b | 2011-09-23 12:37:28 -0700 | [diff] [blame] | 280 | <!-- Strings for NfcTestActivity --> |
| 281 | <string name="nfc_test">NFC Test</string> |
| 282 | <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with |
| 283 | NFC enabled to exchange messages. One device must be the candidate device running the |
| 284 | software build to be tested, while the other device must be an implementation already |
| 285 | known to be compatible.\n\nThe Tag Verification tests check that your |
| 286 | device can properly read and write to tags of different technologies. The MIFARE |
| 287 | Ultralight test is only applicable for devices that support it. |
Martijn Coenen | 109d762 | 2013-09-24 07:09:29 -0700 | [diff] [blame] | 288 | \n\nThe Host-based card emulation tests check that your device has properly implemented |
| 289 | host-based card emulation. |
Brian Muramatsu | 984b78b | 2011-09-23 12:37:28 -0700 | [diff] [blame] | 290 | </string> |
| 291 | |
| 292 | <string name="nfc_not_enabled">NFC is not enabled!</string> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 293 | <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the |
Brian Muramatsu | 984b78b | 2011-09-23 12:37:28 -0700 | [diff] [blame] | 294 | button below to goto Settings and enable it.</string> |
| 295 | <string name="nfc_settings">NFC Settings</string> |
| 296 | |
Nick Pelly | a9631ce | 2011-10-31 14:18:46 -0700 | [diff] [blame] | 297 | <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string> |
| 298 | <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled. |
| 299 | Click the button below to goto NFC Sharing Settings and enable it.</string> |
| 300 | <string name="ndef_push_settings">NFC Sharing Settings</string> |
| 301 | |
Brian Muramatsu | 984b78b | 2011-09-23 12:37:28 -0700 | [diff] [blame] | 302 | <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string> |
| 303 | <string name="nfc_ndef_push_sender">NDEF Push Sender</string> |
| 304 | <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string> |
| 305 | |
| 306 | <string name="nfc_tag_verification">Tag Verification</string> |
| 307 | <string name="nfc_ndef">NDEF</string> |
| 308 | <string name="nfc_mifare_ultralight">MIFARE Ultralight</string> |
| 309 | |
| 310 | <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on |
| 311 | another device and touch the devices back to back. The receiver should show a |
| 312 | dialog indicating it has successfully received the correct message!</string> |
| 313 | <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another |
| 314 | device running the \"CTS Verifier NDEF Receiver\"...</string> |
| 315 | |
| 316 | <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on |
| 317 | another device and touch the devices back to back. The receiver should show a |
| 318 | dialog indicating it has successfully received the correct message!</string> |
| 319 | <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another |
| 320 | device running the \"CTS Verifier NDEF Sender\"...</string> |
| 321 | <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push |
| 322 | message.</string> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 323 | <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push |
Brian Muramatsu | 984b78b | 2011-09-23 12:37:28 -0700 | [diff] [blame] | 324 | message.</string> |
| 325 | |
| 326 | <string name="nfc_tag_verifier">NFC Tag Verifier</string> |
| 327 | <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read |
| 328 | a tag of the chosen technology.</string> |
| 329 | |
| 330 | <string name="nfc_scan_tag">Place device on a writable %s tag...</string> |
| 331 | <string name="nfc_write_tag_title">Writable tag discovered!</string> |
| 332 | <string name="nfc_write_tag_message">Press OK to write to this tag...</string> |
| 333 | <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string> |
| 334 | <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string> |
| 335 | <string name="nfc_no_tech">No tag technologies detected...</string> |
| 336 | |
| 337 | <string name="nfc_writing_tag">Writing NFC tag...</string> |
| 338 | <string name="nfc_writing_tag_error">Error writing NFC tag...</string> |
| 339 | <string name="nfc_reading_tag">Reading NFC tag...</string> |
| 340 | <string name="nfc_reading_tag_error">Error reading NFC tag...</string> |
| 341 | |
| 342 | <string name="nfc_result_success">Test passed!</string> |
| 343 | <string name="nfc_result_failure">Test failed!</string> |
| 344 | |
| 345 | <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string> |
| 346 | <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string> |
| 347 | |
Martijn Coenen | 109d762 | 2013-09-24 07:09:29 -0700 | [diff] [blame] | 348 | <string name="nfc_hce">Host-based card emulation</string> |
Martijn Coenen | 109d762 | 2013-09-24 07:09:29 -0700 | [diff] [blame] | 349 | <string name="nfc_hce_reader_tests">HCE reader tests</string> |
| 350 | <string name="nfc_hce_emulator_tests">HCE emulator tests</string> |
| 351 | <string name="nfc_hce_emulator_test_info">The host-based card emulation |
| 352 | tests require two devices to be completed. The HCE emulator tests are used |
| 353 | to actually test the host-based card emulation feature of the device-under-test. So the |
| 354 | device running the emulator tests must be the candidate device running the software |
| 355 | to be tested. \n\nFor each emulator test, there is a corresponding "reader test" |
| 356 | in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS |
Martijn Coenen | 0cf0c96 | 2014-02-28 14:22:15 -0800 | [diff] [blame] | 357 | and makes sure the device-under-test implements card emulation correctly.</string> |
Martijn Coenen | 109d762 | 2013-09-24 07:09:29 -0700 | [diff] [blame] | 358 | <string name="nfc_hce_reader_test_info">The host-based card emulation |
| 359 | tests require two devices to be completed. The HCE emulator tests are used |
| 360 | to actually test the host-based card emulation feature of the device-under-test. So the |
| 361 | device running the emulator tests must be the candidate device running the software |
| 362 | to be tested. \n\nFor each emulator test, there is a corresponding "reader test" |
| 363 | in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS |
| 364 | and makes sure the device-under-test implements card emulation correctly. |
| 365 | </string> |
Martijn Coenen | 0cf0c96 | 2014-02-28 14:22:15 -0800 | [diff] [blame] | 366 | <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> |
Martijn Coenen | 109d762 | 2013-09-24 07:09:29 -0700 | [diff] [blame] | 367 | <string name="nfc_hce_please_wait">Please wait</string> |
| 368 | <string name="nfc_hce_setting_up">Setting up card emulation services...</string> |
Martijn Coenen | c94c012 | 2013-10-21 14:44:54 -0700 | [diff] [blame] | 369 | |
| 370 | <string name="nfc_hce_default_route_emulator">Default route (Emulator)</string> |
| 371 | <string name="nfc_hce_default_route_reader">Default route (Reader)</string> |
| 372 | <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> |
| 373 | |
| 374 | <string name="nfc_hce_protocol_params_emulator">Protocol parameters (Emulator)</string> |
| 375 | <string name="nfc_hce_protocol_params_reader">Protocol parameters (Reader)</string> |
Martijn Coenen | 7294e32 | 2013-11-13 10:36:05 -0800 | [diff] [blame] | 376 | <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> |
Martijn Coenen | c94c012 | 2013-10-21 14:44:54 -0700 | [diff] [blame] | 377 | |
Martijn Coenen | 109d762 | 2013-09-24 07:09:29 -0700 | [diff] [blame] | 378 | <string name="nfc_hce_single_payment_emulator">Single payment (Emulator)</string> |
| 379 | <string name="nfc_hce_single_payment_reader">Single payment (Reader)</string> |
| 380 | |
| 381 | <string name="nfc_hce_dual_payment_emulator">Two payment services (Emulator)</string> |
| 382 | <string name="nfc_hce_dual_payment_reader">Two payment services (Reader)</string> |
| 383 | |
| 384 | <string name="nfc_hce_change_default_emulator">Change default payment service (Emulator)</string> |
| 385 | <string name="nfc_hce_change_default_reader">Change default payment service (Reader)</string> |
| 386 | |
| 387 | <string name="nfc_hce_tap_reader_title">Tap reader</string> |
| 388 | <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> |
| 389 | |
| 390 | <string name="nfc_hce_single_non_payment_emulator">Single non-payment (Emulator)</string> |
| 391 | <string name="nfc_hce_single_non_payment_reader">Single non-payment (Reader)</string> |
| 392 | |
| 393 | <string name="nfc_hce_dual_non_payment_emulator">Two non-payment services (Emulator)</string> |
| 394 | <string name="nfc_hce_dual_non_payment_reader">Two non-payment services (Reader)</string> |
| 395 | |
| 396 | <string name="nfc_hce_conflicting_non_payment_emulator">Two conflicting non-payment services (Emulator)</string> |
| 397 | <string name="nfc_hce_conflicting_non_payment_reader">Two conflicting non-payment services (Reader)</string> |
| 398 | |
| 399 | <string name="nfc_hce_offhost_service_emulator">Off-host service (Emulator)</string> |
| 400 | <string name="nfc_hce_offhost_service_reader">Off-host service (Reader)</string> |
| 401 | <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> |
| 402 | |
| 403 | <string name="nfc_hce_on_and_offhost_service_emulator">On and off-host services (Emulator)</string> |
| 404 | <string name="nfc_hce_on_and_offhost_service_reader">On and off-host services (Reader)</string> |
| 405 | <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> |
| 406 | |
| 407 | <string name="nfc_hce_tap_test_emulator">50 successful taps test (Emulator)</string> |
| 408 | <string name="nfc_hce_tap_test_reader">50 successful taps test (Reader)</string> |
| 409 | <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> |
| 410 | <string name="nfc_hce_throughput_emulator">HCE throughput test (Emulator)</string> |
| 411 | <string name="nfc_hce_throughput_reader">HCE throughput test (Reader)</string> |
| 412 | <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> |
Martijn Coenen | a54e342 | 2014-02-28 12:42:51 -0800 | [diff] [blame] | 413 | <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 Payment Service #1 or #2 the default app. Select yes.</string> |
Martijn Coenen | 109d762 | 2013-09-24 07:09:29 -0700 | [diff] [blame] | 414 | <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> |
| 415 | <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> |
| 416 | <string name="nfc_payment_service_desc">NFC Payment service</string> |
| 417 | <string name="ppse">PPSE</string> |
| 418 | <string name="mastercard">MasterCard</string> |
| 419 | <string name="paymentService1">Payment Service #1</string> |
| 420 | <string name="paymentService2">Payment Service #2</string> |
| 421 | <string name="transportService1">TransportService #1</string> |
| 422 | <string name="transportService2">TransportService #2</string> |
| 423 | <string name="accessService">AccessService</string> |
| 424 | <string name="offhostService">OffhostService</string> |
| 425 | |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 426 | <!-- Strings for Sensor Test Activities --> |
| 427 | <!-- Accelerometer --> |
Dan Morrill | 5df275b | 2010-08-11 12:19:19 -0700 | [diff] [blame] | 428 | <string name="snsr_accel_test">Accelerometer Test</string> |
Dan Morrill | 71351d8 | 2010-10-20 15:26:00 -0700 | [diff] [blame] | 429 | <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> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 430 | <string name="snsr_accel_m_test">Accelerometer Measurement Tests</string> |
Brian Muramatsu | 729de48 | 2011-05-12 12:26:58 -0700 | [diff] [blame] | 431 | |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 432 | <!-- Gyroscope --> |
Brian Muramatsu | 729de48 | 2011-05-12 12:26:58 -0700 | [diff] [blame] | 433 | <string name="snsr_gyro_test">Gyroscope Test</string> |
| 434 | <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> |
| 435 | <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string> |
| 436 | <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string> |
| 437 | <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> |
| 438 | <string name="snsr_gyro_test_degrees_title">Wrong units?</string> |
| 439 | <string name="snsr_gyro_test_degrees_message">These values looks like degrees per second. These should be radians per second!</string> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 440 | <string name="snsr_gyro_m_test">Gyroscope Measurement Test</string> |
| 441 | |
Vinod Krishnan | 20d6725 | 2014-04-30 11:12:01 -0700 | [diff] [blame] | 442 | <!-- Heart Rate --> |
| 443 | <string name="snsr_heartrate_test">Heart Rate Test</string> |
Vinod Krishnan | 7b6bdeb | 2014-05-13 16:19:44 -0700 | [diff] [blame] | 444 | <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> |
Vinod Krishnan | 20d6725 | 2014-04-30 11:12:01 -0700 | [diff] [blame] | 445 | <string name="snsr_heartrate_test_no_heartrate_title">No heart rate monitor?</string> |
| 446 | <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> |
| 447 | |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 448 | <!-- Magnetic Field --> |
| 449 | <string name="snsr_mag_m_test">Magnetic Field Measurement Tests</string> |
Brian Muramatsu | accc684 | 2010-08-11 18:57:27 -0700 | [diff] [blame] | 450 | |
Jim Steele | 0c4d08a | 2014-08-03 00:49:59 -0700 | [diff] [blame] | 451 | <!-- Sensor Value Accuracy --> |
| 452 | <string name="snsr_val_acc_test">Sensor Value Accuracy Tests</string> |
| 453 | <string name="snsr_rot_vec_test">Rotation Vector Accuracy Test</string> |
| 454 | |
| 455 | <!-- Sensor Batching --> |
| 456 | <string name="snsr_batch_test">Sensor Batching Tests</string> |
| 457 | |
| 458 | <!-- Sensor Synchronization --> |
| 459 | <string name="snsr_synch_test">Sensor Synchronization Test</string> |
| 460 | |
Jim Steele | b292a9f | 2014-07-13 23:29:56 -0700 | [diff] [blame] | 461 | <!-- Step Counter and Detector --> |
| 462 | <string name="snsr_step_counter_test">Step Counter and Detector Tests</string> |
| 463 | |
Jim Steele | c57c843 | 2014-05-24 09:53:32 -0700 | [diff] [blame] | 464 | <!-- Significant Motion --> |
| 465 | <string name="snsr_significant_motion_test">Significant Motion Tests</string> |
| 466 | |
Stuart Scott | ba89816 | 2014-01-17 13:18:14 -0800 | [diff] [blame] | 467 | <!-- Strings for Sample Test Activities --> |
| 468 | <string name="share_button_text">Share</string> |
| 469 | <string name="sample_framework_test">Sample Framework Test</string> |
| 470 | <string name="sample_test">Sample Test</string> |
| 471 | <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> |
| 472 | |
Brian Muramatsu | accc684 | 2010-08-11 18:57:27 -0700 | [diff] [blame] | 473 | <!-- Strings for SuidFilesActivity --> |
Brian Muramatsu | 14e1cbb | 2010-09-13 18:33:39 -0700 | [diff] [blame] | 474 | <string name="suid_files">SUID File Scanner</string> |
| 475 | <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> |
Brian Muramatsu | ac00737 | 2010-08-18 11:02:28 -0700 | [diff] [blame] | 476 | <string name="scanning_directory">Scanning directory...</string> |
Brian Muramatsu | 2233072 | 2010-08-13 14:48:36 -0700 | [diff] [blame] | 477 | <string name="file_status">User: %1$s\nGroup: %2$s\nPermissions: %3$s\nPath: %4$s</string> |
Brian Muramatsu | accc684 | 2010-08-11 18:57:27 -0700 | [diff] [blame] | 478 | <string name="no_file_status">Could not stat file...</string> |
| 479 | <string name="congratulations">Congratulations!</string> |
| 480 | <string name="no_suid_files">No unauthorized suid files detected!</string> |
Brian Muramatsu | f894620 | 2010-11-09 13:43:39 -0800 | [diff] [blame] | 481 | |
Brian Muramatsu | 1f54980 | 2011-06-09 15:25:28 -0700 | [diff] [blame] | 482 | <!-- Strings for Camera Analyzer --> |
| 483 | <string name="camera_analyzer">Camera Analyzer</string> |
Eino-Ville Talvala | c0b150c | 2012-04-12 17:26:57 -0700 | [diff] [blame] | 484 | <string name="ca_find_checkerboard_label">Find target</string> |
| 485 | <string name="ca_check_formats_label">Output formats</string> |
| 486 | <string name="ca_exposure_test_label">Exposure Comp.</string> |
Christine Chen | 523d04c | 2011-09-22 11:45:50 -0700 | [diff] [blame] | 487 | <string name="ca_result_label">Results will be here</string> |
Eino-Ville Talvala | c0b150c | 2012-04-12 17:26:57 -0700 | [diff] [blame] | 488 | <string name="ca_wb_test_label">White Balance</string> |
| 489 | <string name="ca_lock_test_label">AE Lock</string> |
| 490 | <string name="ca_metering_label">Metering Area</string> |
| 491 | <string name="ca_focus_modes_label">Focus Modes</string> |
Christine Chen | 523d04c | 2011-09-22 11:45:50 -0700 | [diff] [blame] | 492 | <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> |
Jeff Davidson | 2b1c549 | 2011-08-23 10:49:12 -0700 | [diff] [blame] | 493 | |
James Painter | fa2e166 | 2012-09-13 15:37:58 -0700 | [diff] [blame] | 494 | <!-- Strings for Camera Orientation --> |
| 495 | <string name="camera_orientation">Camera Orientation</string> |
James Painter | 6cdb868 | 2012-10-02 08:22:39 -0700 | [diff] [blame] | 496 | <string name="co_info">This test verifies the orientation capabilities of |
| 497 | camera preview and capture.\n - The left view shows a preview window rotated |
| 498 | clockwise by a given magnitude of degrees.\n - The right view, after taking |
| 499 | a photo, shows the captured image.\n - For each camera and orientation, both |
| 500 | the left and right views should appear rotated clockwise by the amount of |
| 501 | degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose |
| 502 | \"Fail\".\n - For front-facing cameras, the test will horizontally mirror |
| 503 | the captured image prior to rotation, in attempt to make the left and right |
| 504 | views appear the same.\n - The physical orientation of the device does not |
| 505 | matter.\n - Read the message above the \"Take Photo\" button for |
| 506 | step-by-step instructions. |
James Painter | 738030a | 2012-09-26 00:31:30 -0700 | [diff] [blame] | 507 | </string> |
James Painter | fa2e166 | 2012-09-13 15:37:58 -0700 | [diff] [blame] | 508 | <string name="co_preview_label">Camera preview</string> |
| 509 | <string name="co_format_label">Oriented photo</string> |
| 510 | <string name="co_camera_label">Camera:</string> |
| 511 | <string name="co_orientation_label">Orientation</string> |
James Painter | 738030a | 2012-09-26 00:31:30 -0700 | [diff] [blame] | 512 | <string name="co_orientation_direction_label">clockwise</string> |
James Painter | fa2e166 | 2012-09-13 15:37:58 -0700 | [diff] [blame] | 513 | <string name="co_instruction_heading_label">Instruction:</string> |
| 514 | <string name="co_instruction_text_photo_label">Take a photo</string> |
James Painter | 6cdb868 | 2012-10-02 08:22:39 -0700 | [diff] [blame] | 515 | <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> |
| 516 | <string name="co_instruction_text_extra_label">(mirrored horizontally prior to rotation, since camera is front-facing)</string> |
James Painter | fa2e166 | 2012-09-13 15:37:58 -0700 | [diff] [blame] | 517 | <string name="co_photo_button_caption">Take Photo</string> |
Eino-Ville Talvala | e56ae2a | 2012-04-27 19:18:41 -0700 | [diff] [blame] | 518 | |
Igor Murashkin | 48f86e7 | 2012-10-17 18:12:59 -0700 | [diff] [blame] | 519 | <!-- Strings for Camera Intents --> |
| 520 | <string name="camera_intents">Camera Intents</string> |
| 521 | <string name="ci_info"> |
| 522 | This test verifies that the default camera app is firing intents |
| 523 | after pictures/videos are taken. It also verifies that when the |
| 524 | default camera app is invoked via intents, the launch intents work, |
| 525 | and the broadcast intents are received when appropriate per the SDK |
| 526 | documentation.\n\n |
| 527 | - Read the message above the \"Start Test\" button for |
| 528 | step-by-step instructions. |
| 529 | </string> |
| 530 | <string name="ci_preview_label">Camera preview</string> |
| 531 | <string name="ci_format_label">Oriented photo</string> |
| 532 | <string name="ci_camera_label">Camera:</string> |
| 533 | <string name="ci_intents_label">Intents Test</string> |
| 534 | <string name="ci_intents_direction_label">clockwise</string> |
| 535 | <string name="ci_instruction_heading_label">Instructions:</string> |
| 536 | <string name="ci_instruction_text_photo_label">READ BEFORE STARTING TEST</string> |
| 537 | <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> |
| 538 | <string name="ci_instruction_text_app_picture_label">\n |
| 539 | 1. Click Start Test. \n |
| 540 | 2. Go to home screen (HOME key). \n |
| 541 | 3. Launch Camera application. \n |
| 542 | 4. Capture photo. \n |
| 543 | 5. Return to CTS verifier app. \n |
| 544 | 6. Pass button will light up if intent was received.\n |
| 545 | 7. Click "Pass" if possible. |
| 546 | </string> |
| 547 | <string name="ci_instruction_text_app_video_label">\n |
| 548 | 1. Click Start Test. \n |
| 549 | 2. Go to home screen (HOME key). \n |
| 550 | 3. Launch Camera application. \n |
| 551 | 4. Capture video. \n |
| 552 | 5. Return to CTS verifier app. \n |
| 553 | 6. Pass button will light up if intent was received.\n |
| 554 | 7. Click "Pass" if possible. |
| 555 | </string> |
| 556 | <string name="ci_instruction_text_intent_picture_label">\n |
| 557 | 1. Click Start Test.\n |
| 558 | 2. Camera app will launch, prompting to take photo.\n |
| 559 | 3. Capture/confirm photo using camera app controls.\n |
| 560 | 4. Pass button will light up if intent was NOT received.\n |
| 561 | 5. Click "Pass" if possible. |
| 562 | </string> |
| 563 | <string name="ci_instruction_text_intent_video_label">\n |
| 564 | 1. Click Start Test.\n |
| 565 | 2. Camera app will launch, prompting to take video.\n |
| 566 | 3. Capture/confirm video using camera app controls.\n |
| 567 | 4. Pass button will light up if intent was received.\n |
| 568 | 5. Click "Pass" if possible. |
| 569 | </string> |
| 570 | <string name="ci_start_test_button_caption">Start Test</string> |
| 571 | |
James Painter | fa2e166 | 2012-09-13 15:37:58 -0700 | [diff] [blame] | 572 | <!-- Strings for Camera Formats --> |
Eino-Ville Talvala | e56ae2a | 2012-04-27 19:18:41 -0700 | [diff] [blame] | 573 | <string name="camera_format">Camera Formats</string> |
| 574 | <string name="cf_info">This test checks that all the supported |
| 575 | output formats for camera preview callbacks work correctly, and |
| 576 | that the mandatory formats are available. \n - The left view shows |
| 577 | a standard preview window. \n - The right view shows the output |
| 578 | processed from camera preview callbacks. \n - For each camera, |
| 579 | resolution, and format combination in the dropdowns, the right |
| 580 | view should look the same as the left, and neither should have |
| 581 | streaks, lines, or other artifacts. \n - For front-facing cameras, |
| 582 | the right view must be horizontally mirrored relative to the left |
| 583 | view.\n - Note that the frame rate of the right view may be much |
| 584 | lower than on the left; this is not an indication of a failed |
| 585 | test. |
| 586 | </string> |
| 587 | <string name="cf_preview_label">Normal preview</string> |
| 588 | <string name="cf_format_label">Processed callback data</string> |
| 589 | |
Jianing Wei | 636f903 | 2013-10-03 10:00:25 -0700 | [diff] [blame] | 590 | <!-- Strings for Camera Video --> |
| 591 | <string name="record_button_text">Test</string> |
| 592 | <string name="camera_video">Camera Video</string> |
| 593 | <string name="video_info"> This test checks video capture |
| 594 | at different resolutions. \n - The left view window shows the preview. |
| 595 | \n - Pressing the test button will trigger three |
| 596 | seconds of video recording. Playback will show up in the right view |
| 597 | window after recording is complete. \n - Use the spinners to choose |
| 598 | camera and resolution combinations. The playback should be similar |
| 599 | to what you saw in preview. \n - After all possible combinations |
| 600 | are tested, the pass button will be enabled. You may press the pass |
| 601 | button to indicate a pass. \n - You may press fail button any time during |
| 602 | the test to indicate failure. |
| 603 | </string> |
| 604 | <string name="video_capture_label">Video capture</string> |
| 605 | <string name="video_playback_label">Video playback</string> |
| 606 | <string name="dialog_fail_test">Test failed</string> |
| 607 | <string name="fail_quit">Fail and quit</string> |
| 608 | <string name="cancel">Cancel</string> |
| 609 | <string name="status_ready">Ready</string> |
| 610 | <string name="status_recording">Recording</string> |
| 611 | <string name="status_playback">Playing back</string> |
| 612 | |
Brian Muramatsu | 12c8691 | 2011-07-21 17:26:46 -0700 | [diff] [blame] | 613 | <!-- Strings for USB accessory test activity --> |
| 614 | <string name="usb_accessory_test">USB Accessory Test</string> |
| 615 | <string name="usb_accessory_test_info"> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 616 | 1. Connect your Android device to a computer and run the \'cts-usb-accessory\' program |
Brian Muramatsu | dd2bf71 | 2011-08-12 12:46:07 -0700 | [diff] [blame] | 617 | included with the CTS Verifier bundle. |
Brian Muramatsu | 12c8691 | 2011-07-21 17:26:46 -0700 | [diff] [blame] | 618 | \n\n2. If you have not started the CTS Verifier, press \'OK\' when asked to open the CTS |
| 619 | Verifier when the accessory is connected. \n\nIf you are already in this test, |
| 620 | then you can press \'Cancel\' but press \'OK\' in the next dialog asking whether to allow |
| 621 | CTS Verifier to access the accessory. |
| 622 | \n\n3. You should see the accessory and the CTS Verifier display a series of messages |
| 623 | which indicates that the accessory support is working properly. |
| 624 | </string> |
| 625 | <string name="usb_not_available_title">USB accessory feature is not available?</string> |
| 626 | <string name="usb_not_available_message">If your device is supposed to support USB accessories, your API implementation is not behaving correctly!</string> |
| 627 | <string name="usb_received_messages">Received Messages</string> |
| 628 | <string name="usb_sent_messages">Sent Messages</string> |
| 629 | <string name="usb_no_messages">No messages</string> |
| 630 | <string name="usb_message_thread_started">Starting message processing...</string> |
| 631 | <string name="usb_message_thread_exception">Exception occurred while processing a message...</string> |
| 632 | <string name="usb_message_thread_ended">Stopping message processing...</string> |
| 633 | <string name="usb_test_passed">Received all expected messages. Pass button enabled!</string> |
| 634 | <string name="usb_file_descriptor_error">Could not open file descriptor for USB accessory... try reconnecting and restarting the accessory?</string> |
| 635 | |
Jeff Davidson | 112f279 | 2011-08-22 09:46:46 -0700 | [diff] [blame] | 636 | <!-- Strings for StreamingVideoActivity --> |
| 637 | <string name="streaming_video">Streaming Video Quality Verifier</string> |
| 638 | <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> |
| 639 | <string name="sv_no_data">No videos.</string> |
| 640 | <string name="sv_failed_title">Test Failed</string> |
| 641 | <string name="sv_failed_message">Unable to play stream. See log for details.</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 642 | |
| 643 | <!-- Strings for P2pTestActivity --> |
| 644 | <string name="p2p_test">Wi-Fi Direct Test</string> |
| 645 | <string name="p2p_test_info"> |
| 646 | The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange |
| 647 | messages. One device must be the candidate device running the software build to |
| 648 | be tested, while the other device must be an implementation already known to be |
| 649 | compatible.\n\nOne device should start the requester test, and the other should |
| 650 | start the responder test. Your device must pass both requester and responder |
| 651 | tests. |
| 652 | </string> |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 653 | <string name="p2p_group_formation">Group Formation</string> |
| 654 | <string name="p2p_join">Group Join</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 655 | <string name="p2p_service_discovery">Service Discovery</string> |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 656 | |
| 657 | <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string> |
| 658 | <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string> |
| 659 | <string name="p2p_group_owner_test">Group Owner Test</string> |
| 660 | <string name="p2p_group_client_test">Group Client Test</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 661 | <string name="p2p_service_discovery_responder_test"> |
| 662 | Service Discovery Responder Test</string> |
| 663 | <string name="p2p_service_discovery_requester_test"> |
| 664 | Service Discovery Requester Test</string> |
| 665 | |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 666 | <string name="p2p_go_neg_responder">GO Negotiation Responder</string> |
| 667 | <string name="p2p_go_neg_requester">GO Negotiation Requester</string> |
| 668 | <string name="p2p_accept_client">Group Owner</string> |
| 669 | <string name="p2p_join_go">Group Client</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 670 | <string name="p2p_service_discovery_responder">Service Discovery Responder</string> |
| 671 | <string name="p2p_service_discovery_requester">Service Discovery Requester</string> |
| 672 | |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 673 | <string name="p2p_go_neg_responder_info"> |
| 674 | Start the \"GO Negotiation Requester Test\" on the other device and follow |
| 675 | the instructions.</string> |
| 676 | <string name="p2p_accept_client_info"> |
| 677 | Start the \"Group Client Test\" on the other device and follow |
| 678 | the instructions.</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 679 | <string name="p2p_service_discovery_responder_info"> |
| 680 | Start the \"Service Discovery Requester Test\" on the other device and follow |
| 681 | the instructions.</string> |
| 682 | |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 683 | <string name="p2p_go_neg_requester_info"> |
| 684 | Start the \"GO Negotiation Responder Test\" on the other device. |
| 685 | Then run each test individually by clicking on it\'s name.</string> |
| 686 | <string name="p2p_join_go_info"> |
| 687 | Start the \"Group Owner Test\" on the other device. |
| 688 | Then run each test individually by clicking on it\'s name.</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 689 | <string name="p2p_service_discovery_requester_info"> |
| 690 | Start the \"Service Discovery Responder Test\" on the other device. |
| 691 | Then run each test individually by clicking on it\'s name.</string> |
| 692 | |
| 693 | <string name="p2p_not_enabled">Wi-Fi is not enabled</string> |
| 694 | <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled. |
| 695 | Click the button below to go to system settings and enable Wi-Fi.</string> |
| 696 | <string name="p2p_settings">Wi-Fi Direct Settings</string> |
| 697 | |
| 698 | <string name="p2p_result_success">Test passed successfully.</string> |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 699 | |
| 700 | <string name="p2p_go_neg_responder_ready"> |
| 701 | The go negotiation responder is now ready to start. Start |
| 702 | the \"GO Negotiation Requester Test\" on the other device. |
| 703 | Keep the screen here until all tests on the other device are |
| 704 | finished.</string> |
| 705 | <string name="p2p_go_ready"> |
| 706 | The group owner is now ready to start. Start the \"Join |
| 707 | Group Test\" on the other device. |
| 708 | Keep the screen here until all tests on the other device are |
| 709 | finished.</string> |
| 710 | <string name="p2p_service_responder_ready"> |
| 711 | The service responder is now ready to start. Start the |
| 712 | \"Service Discovery Requester Test\" on the other device. |
| 713 | Keep the screen here until all tests on the other device are |
| 714 | finished.</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 715 | |
| 716 | <string name="p2p_setup_error"> |
| 717 | Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string> |
| 718 | <string name="p2p_unexpected_error"> |
| 719 | Test failed.\n\nUnexpected error. Check logcat.</string> |
| 720 | <string name="p2p_add_local_service_error"> |
| 721 | Test failed.\n\nFailed to add local service.</string> |
| 722 | <string name="p2p_add_service_request_error"> |
| 723 | Test failed.\n\nFailed to add service request.</string> |
| 724 | <string name="p2p_remove_service_request_error"> |
| 725 | Test failed.\n\nFailed to remove service request.</string> |
| 726 | <string name="p2p_clear_service_requests_error"> |
| 727 | Test failed.\n\nFailed to clear service requests.</string> |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 728 | <string name="p2p_connect_error"> |
| 729 | Test failed.\n\nFailed to start a p2p connection to the target device.</string> |
| 730 | <string name="p2p_remove_group_error"> |
| 731 | Test failed.\n\nFailed to remove a p2p group.</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 732 | <string name="p2p_discover_peers_error"> |
| 733 | Test failed.\n\nFailed to discover peers.</string> |
| 734 | <string name="p2p_discover_services_error"> |
| 735 | Test failed.\n\nFailed to discover services.</string> |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 736 | <string name="p2p_ceate_group_error"> |
| 737 | Test failed.\n\nFailed to start up group owner.</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 738 | <string name="p2p_no_service_requests_error"> |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 739 | Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 740 | <string name="p2p_receive_invalid_response_error"> |
| 741 | Test failed.\n\nReceived an invalid message or could not receive |
| 742 | the expected message.\n\n</string> |
| 743 | <string name="p2p_target_not_found_error">Test failed.\n\n |
| 744 | The target responder device was NOT found. Start up the responder |
| 745 | test on the other device, then run the test again.</string> |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 746 | <string name="p2p_target_invalid_role_error">Test failed.\n\n |
| 747 | The target responder must be p2p device. However, the target responder |
| 748 | device was group owner. Check the test case on the other device.</string> |
| 749 | <string name="p2p_target_invalid_role_error2">Test failed.\n\n |
| 750 | The target responder must be group owner. However, the target responder |
| 751 | device was p2p device. Check the test case on the other device.</string> |
| 752 | <string name="p2p_connection_error"> |
| 753 | Test failed.\n\nFailed to establish a p2p connection.</string> |
| 754 | <string name="p2p_detect_disconnection_error"> |
| 755 | Test failed.\n\nFailed to detect client disconnection.</string> |
| 756 | <string name="p2p_disconnect_error"> |
| 757 | Test failed.\n\nFailed to disconnect a p2p connection.</string> |
Yoshihiko Ikenaga | f2bfc97 | 2012-04-11 22:45:03 +0900 | [diff] [blame] | 758 | |
| 759 | <string name="p2p_search_target">Search Target</string> |
| 760 | <string name="p2p_searching_target">Searching for target device ...</string> |
Yoshihiko Ikenaga | 395214c | 2012-05-10 20:19:35 +0900 | [diff] [blame] | 761 | <string name="p2p_checking_serv_capab">Checking the service discovery |
| 762 | capability ...</string> |
| 763 | <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n |
| 764 | Click the \"OK\" button on the other device to accept the connection |
| 765 | request from this device.</string> |
| 766 | <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n |
| 767 | Enter the pin number on the other device.</string> |
| 768 | <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to |
| 769 | connect ...</string> |
| 770 | <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer |
| 771 | to disconnect ...</string> |
Angus Kong | a021688 | 2013-03-06 17:51:11 -0800 | [diff] [blame] | 772 | |
| 773 | <string name="camera_fov_calibration">Camera FOV Calibration</string> |
| 774 | <string name="camera_fov_calibration_done">Done</string> |
| 775 | <string name="camera_fov_general_settings">General settings</string> |
| 776 | <string name="camera_fov_label_options">Settings</string> |
| 777 | <string name="camera_fov_tap_to_take_photo">Tap to calibrate</string> |
| 778 | <string name="camera_fov_marker_distance">Marker distance (in cm)</string> |
| 779 | <string name="camera_fov_marker_distance_description">The distance in centimeters between |
| 780 | the solid lines on the target pattern.</string> |
| 781 | <string name="camera_fov_target_distance">Target distance (in cm)</string> |
| 782 | <string name="camera_fov_target_distance_description">The distance in centimeters from the |
| 783 | device to the target pattern.</string> |
| 784 | <string name="camera_fov_settings_button_text">Setup</string> |
Sascha Haeberling | 28cb27c | 2013-05-03 18:19:07 -0700 | [diff] [blame] | 785 | <string name="camera_fov_change_preview_sizes_button_text">Preview Sizes</string> |
| 786 | <string name="camera_fov_choose_preview_size_for_camera">Choose preview size for camera %1$s</string> |
Angus Kong | a021688 | 2013-03-06 17:51:11 -0800 | [diff] [blame] | 787 | <string name="camera_fov_displayed_fov_label">Displayed FOV : </string> |
| 788 | <string name="camera_fov_reported_fov_label">Reported FOV : </string> |
Sascha Haeberling | 117c60c | 2013-06-11 13:26:42 -0700 | [diff] [blame] | 789 | <string name="camera_fov_reported_fov_problem">Reported FOV problem</string> |
| 790 | <string name="camera_fov_reported_fov_problem_message">The reported FOV before takePicture() is |
| 791 | different from when onPictureTaken() is called.\nAs picture size has not been changed, the |
| 792 | reported FOV should be identical at both times.\n\nFOV before/after: %1$f / %2$f</string> |
| 793 | |
Angus Kong | a021688 | 2013-03-06 17:51:11 -0800 | [diff] [blame] | 794 | <string name="camera_fov_panorama_wallpaper_title">Photo Sphere Live Wallpaper</string> |
| 795 | <string name="camera_fov_panorama_wallpaper_description">This live wallapper displays photo |
| 796 | spheres.</string> |
| 797 | <string name="camera_fov_select_panorama">Select panorama</string> |
| 798 | <string name="camera_fov_select_panorama_description">Select a panorama to display in the |
| 799 | live wallpaper.</string> |
| 800 | <string name="camera_fov_reset_panorama">Reset panorama</string> |
| 801 | <string name="camera_fov_reset_panorama_description">Resets the panorama to show the demo |
| 802 | file.</string> |
| 803 | <string name="camera_fov_enable_compass_mode">Enable compass mode</string> |
| 804 | <string name="camera_fov_enable_compass_mode_description">If enabled, the panorama orients |
| 805 | itself according to the current rotation of the device.</string> |
| 806 | |
Chris Wren | f102e54 | 2013-04-30 17:52:57 -0400 | [diff] [blame] | 807 | <string name="test_category_notifications">Notifications</string> |
| 808 | <string name="nls_test">Notification Listener Test</string> |
| 809 | <string name="nls_service_name">Notification Listener for CTS Verifier</string> |
| 810 | <string name="nls_info">This test checks that a NotificationListenerService can be enabled |
| 811 | and disabled, and that once enabled the service is able to receive notificaitons and |
| 812 | dismiss them. |
| 813 | </string> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 814 | <string name="nls_enable_service">Please enable \"Notification Listener for CTS Verifier\" |
Chris Wren | f102e54 | 2013-04-30 17:52:57 -0400 | [diff] [blame] | 815 | under Security > Notification Access and return here.</string> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 816 | <string name="nls_disable_service">Please disable \"Notification Listener for CTS Verifier\" |
Chris Wren | f102e54 | 2013-04-30 17:52:57 -0400 | [diff] [blame] | 817 | under Security > Notification Access and return here.</string> |
| 818 | <string name="nls_start_settings">Launch Settings</string> |
| 819 | <string name="nls_service_started">Service should start once enabled.</string> |
| 820 | <string name="nls_note_received">Check that notification was received.</string> |
| 821 | <string name="nls_payload_intact">Check that notification payload was intact.</string> |
| 822 | <string name="nls_clear_one">Check that service can clear a notification.</string> |
| 823 | <string name="nls_clear_all">Check that service can clear all notifications.</string> |
| 824 | <string name="nls_service_stopped">Service should stop once disabled.</string> |
| 825 | <string name="nls_note_missed">Check that notification was not received.</string> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 826 | |
Tom O'Neill | cd4fa02 | 2013-12-13 17:27:46 -0800 | [diff] [blame] | 827 | <string name="location_mode_high_accuracy_test">High Accuracy Mode Test</string> |
| 828 | <string name="location_mode_high_accuracy_info"> |
| 829 | This test checks that the Location Mode API is consistent with the |
| 830 | Location Provider API when the device is in High Accuracy location mode. |
| 831 | </string> |
| 832 | <string name="location_mode_select_high_accuracy"> |
| 833 | Please select the \"High accuracy\" mode at Settings > Location and return here. |
| 834 | </string> |
| 835 | <string name="location_mode_battery_saving_test">Battery Saving Mode Test</string> |
| 836 | <string name="location_mode_battery_saving_info"> |
| 837 | This test checks that the Location Mode API is consistent with the |
| 838 | Location Provider API when the device is in Battery Saving location mode. |
| 839 | </string> |
| 840 | <string name="location_mode_select_battery_saving"> |
| 841 | Please select the \"Battery Saving\" mode at Settings > Location and return here. |
| 842 | </string> |
Tom O'Neill | 9e56d27 | 2013-12-16 12:48:30 -0800 | [diff] [blame] | 843 | <string name="location_mode_device_only_test">Device Only Mode Test</string> |
| 844 | <string name="location_mode_device_only_info"> |
| 845 | This test checks that the Location Mode API is consistent with the |
| 846 | Location Provider API when the device is in Device Only location mode. |
| 847 | </string> |
| 848 | <string name="location_mode_select_device_only"> |
| 849 | Please select the \"Device Only\" mode at |
| 850 | Settings > Location and return here. |
| 851 | </string> |
| 852 | <string name="location_mode_off_test">Location Mode Off Test</string> |
| 853 | <string name="location_mode_off_info"> |
| 854 | This test checks that the Location Mode API is consistent with the |
| 855 | Location Provider API when the device is in the Off location mode. |
| 856 | </string> |
Tom O'Neill | cd4fa02 | 2013-12-13 17:27:46 -0800 | [diff] [blame] | 857 | |
| 858 | <string name="location_mode_start_settings">Launch Settings</string> |
| 859 | <string name="location_mode_turn_on"> |
Tom O'Neill | 9e56d27 | 2013-12-16 12:48:30 -0800 | [diff] [blame] | 860 | Please turn ON location access (the switch at the top of Settings > Location) |
| 861 | and return here. |
| 862 | </string> |
| 863 | <string name="location_mode_turn_off"> |
| 864 | Please turn OFF location access (the switch at the top of Settings > Location) |
| 865 | and return here. |
Tom O'Neill | cd4fa02 | 2013-12-13 17:27:46 -0800 | [diff] [blame] | 866 | </string> |
| 867 | <string name="location_mode_secure_gps_on">GPS provider should be ON in secure settings.</string> |
| 868 | <string name="location_mode_secure_gps_off">GPS provider should be OFF in secure settings.</string> |
| 869 | <string name="location_mode_secure_nlp_on">Network location provider should be ON in secure settings.</string> |
| 870 | <string name="location_mode_secure_nlp_off">Network location provider should be OFF in secure settings.</string> |
| 871 | <string name="location_mode_manager_gps_on">GPS provider should be ON in LocationManager.</string> |
| 872 | <string name="location_mode_manager_gps_off">GPS provider should be OFF in LocationManager.</string> |
| 873 | <string name="location_mode_manager_nlp_on">Network location provider should be ON in LocationManager.</string> |
| 874 | <string name="location_mode_manager_nlp_off">Network location provider should be OFF in LocationManager.</string> |
| 875 | |
Maggie Benthall | 3278c02 | 2013-10-04 18:50:51 -0400 | [diff] [blame] | 876 | <string name="cacert_test">CA Cert Notification Test</string> |
| 877 | <string name="cacert_info">This test checks that when a CA Certificate is installed, the user is notified.</string> |
| 878 | <string name="cacert_do_something">Do it</string> |
| 879 | <string name="cacert_done">Done</string> |
| 880 | <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> |
| 881 | <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> |
| 882 | <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> |
| 883 | <string name="cacert_dismiss_notification">Dismiss the notification. If it cannot be dismissed, fail the test.</string> |
| 884 | |
| 885 | <string name="caboot_test">CA Cert Notification on Boot test</string> |
| 886 | <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> |
| 887 | <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> |
| 888 | <string name="caboot_check_creds">Check Credentials</string> |
| 889 | <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> |
| 890 | <string name="caboot_install_cert">Install credential</string> |
| 891 | <string name="caboot_reboot_desc">Please reboot the device and return to this test.</string> |
| 892 | <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> |
| 893 | |
Adam Cohen | 8ae9670 | 2013-05-17 14:21:23 -0700 | [diff] [blame] | 894 | <!-- Strings for Widget --> |
| 895 | <string name="widget_framework_test">Widget Framework Test</string> |
| 896 | <string name="widget_framework_test_info">This test checks some basic features of the widget |
| 897 | framework. In order to perform the test, press the Home button. Add the widget |
| 898 | titled "CTS Verifier" to the home screen. Follow the instructions in the widget.</string> |
| 899 | <string name="widget_name">Widget Framework Test</string> |
| 900 | <string name="widget_pass">Pass</string> |
| 901 | <string name="widget_fail">Fail</string> |
Alon Albert | 4106ff1 | 2013-10-01 12:36:02 -0700 | [diff] [blame] | 902 | |
| 903 | <!-- Strings for DeskClock --> |
Isaac Katzenelson | d96d066 | 2013-10-02 17:06:28 -0700 | [diff] [blame] | 904 | <string name="deskclock_tests">Alarms and Timers Tests</string> |
Alon Albert | 4106ff1 | 2013-10-01 12:36:02 -0700 | [diff] [blame] | 905 | <string name="deskclock_tests_info"> |
Isaac Katzenelson | d96d066 | 2013-10-02 17:06:28 -0700 | [diff] [blame] | 906 | The Alarms and Timers tests verify that the Clock app implements the AlarmClock API properly. |
Alon Albert | 4106ff1 | 2013-10-01 12:36:02 -0700 | [diff] [blame] | 907 | </string> |
| 908 | <string name="deskclock_group_alarms">Alarms</string> |
| 909 | <string name="deskclock_group_timers">Timers</string> |
| 910 | |
| 911 | <string name="dc_show_alarms_test">Show Alarms Test</string> |
| 912 | <string name="dc_show_alarms_test_info"> |
| 913 | This test verifies that the SHOW_ALARMS API works.\n |
| 914 | 1. Press the "Show Alarms" button.\n |
Isaac Katzenelson | d96d066 | 2013-10-02 17:06:28 -0700 | [diff] [blame] | 915 | 2. Verify that a UI of the clock app is launched and displays the list of alarms\n |
Alon Albert | 4106ff1 | 2013-10-01 12:36:02 -0700 | [diff] [blame] | 916 | </string> |
| 917 | <string name="dc_show_alarms_button">Show Alarms</string> |
| 918 | |
Isaac Katzenelson | d96d066 | 2013-10-02 17:06:28 -0700 | [diff] [blame] | 919 | <string name="dc_set_alarm_with_ui_test">Set Alarm Test</string> |
| 920 | <string name="dc_set_alarm_with_ui_test_info"> |
| 921 | This test verifies that the ACTION_SET_ALARM with no parameters API works.\n |
| 922 | 1. Press the "Set Alarm" button.\n |
| 923 | 2. Verify that the clock app is launched and displays a UI to manage alarms.\n |
| 924 | </string> |
| 925 | <string name="dc_set_alarm_button">Set Alarm</string> |
| 926 | <string name="dc_set_alarm_verify_button">Verify</string> |
Alon Albert | 4106ff1 | 2013-10-01 12:36:02 -0700 | [diff] [blame] | 927 | |
Isaac Katzenelson | d96d066 | 2013-10-02 17:06:28 -0700 | [diff] [blame] | 928 | <string name="dc_start_alarm_test">Start Alarm Test</string> |
| 929 | <string name="dc_start_alarm_test_info"> |
| 930 | This test verifies that the ACTION_SET_ALARM API actually starts an alarm.\n |
| 931 | 1. Press the "Start Alarm" button.\n |
| 932 | 2. Make sure the alarms UI is NOT shown\n |
| 933 | 3. Wait for the alarm to fire (may take up to 2 minutes)\n |
| 934 | 4. Verify that the alarm title is: "Start Alarm Test",\n |
| 935 | the alarm is silent and vibrating (if the device supports vibrate).\n |
| 936 | 5. Dismiss the alarm.\n |
| 937 | 6. Verify that the alarm is not in the Clock\'s alarms list. The Verify button opens |
| 938 | the alarm view.\n |
| 939 | </string> |
| 940 | <string name="dc_start_alarm_button">Start Alarm</string> |
| 941 | |
| 942 | <string name="dc_full_alarm_test">Full Alarm Test</string> |
| 943 | <string name="dc_full_alarm_test_info"> |
| 944 | This test verifies that the ACTION_SET_ALARM API supports all extras.\n |
| 945 | 1. Press the "Create Alarm" button.\n |
| 946 | 2. Verify that you see one alarm with the following information:\n |
| 947 | Name of alarm: Create Alarm Test. \n |
| 948 | Vibrate: on.\n |
| 949 | Ringtone: silent.\n |
| 950 | Time: 01:23. \n |
| 951 | Repeating on: Monday and Wednesday. \n |
| 952 | </string> |
| 953 | <string name="dc_full_alarm_button">Create Alarm</string> |
destradaa | 65c7cdb | 2013-10-28 16:36:12 -0700 | [diff] [blame] | 954 | |
Isaac Katzenelson | d96d066 | 2013-10-02 17:06:28 -0700 | [diff] [blame] | 955 | <string name="dc_set_timer_with_ui_test">Set Timer Test</string> |
| 956 | <string name="dc_set_timer_with_ui_test_info"> |
| 957 | This test verifies that the ACTION_SET_TIMER API with no paramters open the UI\n |
| 958 | 1. Press the "Set Timer" button.\n |
| 959 | 2. Verify that the an app is launched and displays a UI to manage timers.\n |
| 960 | </string> |
| 961 | <string name="dc_set_timer_with_ui_button">Set Timer</string> |
| 962 | |
| 963 | <string name="dc_start_timer_test">Start Timer Test</string> |
| 964 | <string name="dc_start_timer_test_info"> |
| 965 | This test verifies that the ACTION_SET_TIMER API actually starts a timer\n |
| 966 | 1. Press the "Start Timer" button.\n |
| 967 | 2. Verify that a timer is started and NO timers UI is shown.\n |
| 968 | 3. Verify that the timer named "Start Timer Test" rings after 30 seconds. Dismiss it.\n |
| 969 | 4. Verify that the timer is deleted after the dismissal.\n |
| 970 | </string> |
| 971 | <string name="dc_start_timer_button">Start Timer</string> |
| 972 | |
| 973 | <string name="dc_start_timer_with_ui_test">Start Timer With UI Test</string> |
| 974 | <string name="dc_start_timer_with_ui_test_info"> |
| 975 | This test verifies that the ACTION_SET_TIMER API actually starts a timer with UI\n |
| 976 | 1. Press the "Start Timer" button.\n |
| 977 | 2. Verify that a timer is started and the timers UI is shown with a timer named "Start Timer Test".\n |
| 978 | 3. Verify that the timer rings after 30 seconds.\n |
| 979 | </string> |
Amith Yamasani | 0e2d6d9 | 2014-02-19 10:13:23 -0800 | [diff] [blame] | 980 | <!-- Strings for LockConfirmBypassTest --> |
| 981 | <string name="lock_confirm_test_title">Keyguard Password Verification</string> |
| 982 | <string name="lock_set_button_text">Set password</string> |
| 983 | <string name="lock_change_button_text">Change password</string> |
| 984 | <string name="lock_confirm_message"> |
| 985 | This test verifies that the user is prompted for the current keyguard password before prompting for a new password.\n |
| 986 | \nClick the \"Set password\" button if you currently don\'t have a password set.\n |
| 987 | \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. |
| 988 | </string> |
| 989 | |
Harsh Modi | fe5933d | 2014-08-12 16:52:16 -0700 | [diff] [blame] | 990 | <!-- String for Projection Tests --> |
| 991 | <string name="test_category_projection">Projection Tests</string> |
| 992 | <string name="projection_service_name">Projection Service</string> |
| 993 | <string name="pca_info">This tests whether or not OpenGL projection works.\n |
| 994 | You should see two "tumbling cubes." Tapping the screen should case the cubes to explode.</string> |
| 995 | <string name="pca_test">Projection Cube Test</string> |
| 996 | <string name="pwa_info">This tests whether or displaying widets and keyfocus navigation works.\n |
| 997 | You should see four buttons on the bottom of the screen.\n |
| 998 | Pressing the "up" and "down" buttons should highlight different buttons.\n |
| 999 | Further, you should also be able to touch them and they should highlight as ususual.</string> |
| 1000 | <string name="pwa_test">Projection Widget Test</string> |
| 1001 | <string name="pwa_button_up">Up</string> |
| 1002 | <string name="pwa_button_down">Down</string> |
| 1003 | <string name="pwa_button_left">Left</string> |
| 1004 | <string name="pwa_button_right">Right</string> |
| 1005 | <string name="pwa_button">Button</string> |
| 1006 | <string name="pla_test">Projection Scrolling List Test</string> |
| 1007 | <string name="pla_info">This tests whether a projected list view will scroll properly\n |
| 1008 | You should see 50 list items and be able to scroll up and down the list</string> |
| 1009 | <string name="pva_test">Projection Video Playback Test</string> |
| 1010 | <string name="pva_info">This tests whether video playback works when projected.\n |
| 1011 | You should see a blinking white box and here a beep that is synchronized with each blink</string> |
| 1012 | <string name="pta_test">Projection Multitouch Test</string> |
| 1013 | <string name="pta_info">This tests whether multitouch works.\n |
| 1014 | Touching the screen should render a dot at the location you touched.\n |
| 1015 | Touching with additional fingers will render additoinal dots and you should be able to drag them around.</string> |
| 1016 | |
Jim Steele | 0c4d08a | 2014-08-03 00:49:59 -0700 | [diff] [blame] | 1017 | <!-- Strings for RotationVectorTest and GameRotationVectorTest --> |
| 1018 | <string name="rotation_vector_test">Rotation Vector Accuracy Test</string> |
| 1019 | <string name="game_rotation_vector_test">Game Rotation Vector Accuracy Test</string> |
| 1020 | <string name="rotation_vector_test_info"> |
| 1021 | This test verifies that mobile device can detect its orientation in space quickly and repeatably.\n\n |
| 1022 | Instructions:\n |
| 1023 | \n |
| 1024 | 1. Place the mobile device in a reference position and note the arrow orientation.\n |
| 1025 | 2. Move, shake, and rotate the device for about 30 seconds.\n |
| 1026 | 3. Place the mobile device back to the reference position.\n |
| 1027 | 4. Pass if it returns to the original arrow orientation within one second.\n |
| 1028 | </string> |
| 1029 | |
Brian Muramatsu | 70a9e3f | 2010-06-25 15:27:09 -0700 | [diff] [blame] | 1030 | </resources> |