blob: 7e9cc6aa1c86e840b4fa61dd90ce0576f9e15fbc [file] [log] [blame]
Brian Muramatsu70a9e3f2010-06-25 15:27:09 -07001<?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 Davidson112f2792011-08-22 09:46:46 -07007
Brian Muramatsu70a9e3f2010-06-25 15:27:09 -07008 http://www.apache.org/licenses/LICENSE-2.0
Jeff Davidson112f2792011-08-22 09:46:46 -07009
Brian Muramatsu70a9e3f2010-06-25 15:27:09 -070010 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 Katzenelsond96d0662013-10-02 17:06:28 -070018
Brian Muramatsuda429d72012-06-14 12:45:22 -070019 <string name="title_version">CTS Verifier %1$s</string>
Brian Muramatsue1181872010-08-20 12:59:39 -070020
Brian Muramatsuff1038f2010-08-26 14:37:08 -070021 <string name="pass_button_text">Pass</string>
Brian Muramatsu14e1cbb2010-09-13 18:33:39 -070022 <string name="info_button_text">Info</string>
Brian Muramatsuff1038f2010-08-26 14:37:08 -070023 <string name="fail_button_text">Fail</string>
destradaa65c7cdb2013-10-28 16:36:12 -070024 <string name="next_button_text">Next</string>
Zoltan Szatmary-Ban27a2bb52015-07-23 11:58:49 +010025 <string name="go_button_text">Go</string>
Brian Muramatsuff1038f2010-08-26 14:37:08 -070026
Brian Muramatsu78d2c1d2010-08-16 15:22:30 -070027 <!-- Strings for TestListActivity -->
Brian Muramatsuf8946202010-11-09 13:43:39 -080028 <string name="test_category_audio">Audio</string>
Brian Muramatsu1f549802011-06-09 15:25:28 -070029 <string name="test_category_camera">Camera</string>
Harsh Modi0d3062d2015-06-02 15:59:39 -070030 <string name="test_category_car">Car</string>
Brian Muramatsu713049d2011-06-23 18:35:36 -070031 <string name="test_category_device_admin">Device Administration</string>
Brian Muramatsu12c86912011-07-21 17:26:46 -070032 <string name="test_category_hardware">Hardware</string>
Brian Muramatsue891acb2011-05-19 16:02:39 -070033 <string name="test_category_networking">Networking</string>
Brian Muramatsu78d2c1d2010-08-16 15:22:30 -070034 <string name="test_category_sensors">Sensors</string>
Tom O'Neillcd4fa022013-12-13 17:27:46 -080035 <string name="test_category_location">Location</string>
Brian Muramatsu78d2c1d2010-08-16 15:22:30 -070036 <string name="test_category_security">Security</string>
Jeff Davidson112f2792011-08-22 09:46:46 -070037 <string name="test_category_streaming">Streaming</string>
Brian Muramatsu78d2c1d2010-08-16 15:22:30 -070038 <string name="test_category_features">Features</string>
Isaac Katzenelsond96d0662013-10-02 17:06:28 -070039 <string name="test_category_deskclock">Clock</string>
Matthew Williams547b8162014-10-15 10:18:11 -070040 <string name="test_category_jobscheduler">Job Scheduler</string>
Wonsik Kim18aa5752014-10-30 00:47:57 +090041 <string name="test_category_tv">TV</string>
Brian Muramatsu78d2c1d2010-08-16 15:22:30 -070042 <string name="test_category_other">Other</string>
Brian Muramatsuac007372010-08-18 11:02:28 -070043 <string name="clear">Clear</string>
44 <string name="test_results_cleared">Test results cleared.</string>
Brian Muramatsu52f3b6f2011-09-23 12:09:59 -070045 <string name="view">View</string>
Brian Muramatsu82ab52a2011-06-27 14:02:12 -070046 <string name="test_results_error">Couldn\'t create test results report.</string>
Jeff Davidson4c3bbd82011-08-02 11:51:43 -070047 <string name="export">Export</string>
48 <string name="no_storage">Cannot save report to external storage, see log for details.</string>
49 <string name="report_saved">Report saved to: %s</string>
Dan Morrill5df275b2010-08-11 12:19:19 -070050
Brian Muramatsu52f3b6f2011-09-23 12:09:59 -070051 <!-- Strings for ReportViewerActivity -->
52 <string name="report_viewer">Report Viewer</string>
53
Brian Muramatsu0ac3cdf2011-08-03 11:47:10 -070054 <!-- Strings for BackupTestActivity -->
55 <string name="backup_test">Data Backup Test</string>
Jeff Davidson112f2792011-08-22 09:46:46 -070056 <string name="backup_info">This test checks that data backup and automatic restore works
Brian Muramatsu0ac3cdf2011-08-03 11:47:10 -070057 properly. The test activity lists some preferences and files that are backed up and
58 restored by the CTS Verifier. If backup and restore is working properly, these values
59 should be restored after running the backup manager, uninstalling the app, and reinstalling
60 the CTS Verifier.
61 \n\nPress the \"Generate Test Data\" to populate these values
62 and then follow the on screen instructions to finish the test.
63 </string>
64 <string name="bu_preferences">Preferences</string>
65 <string name="bu_files">Files</string>
66 <string name="bu_loading">Loading...</string>
67 <string name="bu_generate">Generate Test Data</string>
68 <string name="bu_generate_error">Error occurred while generating test data...</string>
69 <string name="bu_instructions">Random values for the preferences and files have been saved.
70 \n\nFollow the instructions below to check that the data backup and restore works:
Jeff Davidson112f2792011-08-22 09:46:46 -070071 \n\n1. Make sure backup and automatic restore are enabled in settings. Depending on the
72 backup transport supported by the device you may need to do additional steps. For instance
Takayuki Hoshi7af0e6c2014-11-14 17:07:40 +090073 you may need to set a Google account as the backup account for the device. If you cannot
74 find the corresponding setting options on your device, run \"adb shell bmgr enable true\"
75 to enable the backup manager. You can check its status by executing \"adb shell bmgr
76 enabled\".
Brian Muramatsu0ac3cdf2011-08-03 11:47:10 -070077 \n\n2. Run the backup manager: adb shell bmgr run
78 \n\n3. Uninstall the program: adb uninstall com.android.cts.verifier
79 \n\n4. Reinstall the CTS Verifier and verify that the values are still the same.
80 </string>
81 <string name="bu_settings">Settings</string>
82
Brian Muramatsu713049d2011-06-23 18:35:36 -070083 <!-- Strings for Device Administration tests -->
84 <string name="da_policy_serialization_test">Policy Serialization Test</string>
85 <string name="da_policy_serialization_info">This test checks that a device policy is properly
86 saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create
87 a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the
88 device and verify that all rows in the policy list are green. Red items indicate policy
89 settings that were not loaded properly.
90 </string>
Harsh Modi0d3062d2015-06-02 15:59:39 -070091 <string name="car_dock_test">Car Dock Test</string>
92 <string name="car_dock_test_desc">This test ensures that car mode opens the app associated with
Harsh Modi565526d2015-07-21 17:40:33 -070093 car dock when going into car mode.\n\n
94 Click on "Enable Car Mode" to start the test. Clicking on the button will either bring up a
95 disambiguation dialog asking which app to open or immediately open the CAR_DOCK application.
96 Select the "CTS Verifier" app and then "Always" if the dialog pops up.
97 This will open the CAR_DOCK application.\n\n
98 In the CAR_DOCK application, press the home button, which will enable the pass button if the
99 framework correctly tries to open the CAR_DOCK app again.</string>
Harsh Modi0d3062d2015-06-02 15:59:39 -0700100 <string name="car_mode_enable">Enable Car Mode</string>
101 <string name="car_dock_activity_text">Press the Home button</string>
Brian Muramatsu713049d2011-06-23 18:35:36 -0700102 <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device
103 policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your
104 device and return to this test in the CTS Verifier.
105 </string>
106 <string name="da_generate_policy">Generate Policy</string>
107 <string name="da_apply_policy">Apply Policy</string>
108 <string name="da_random_policy">Random policy generated.</string>
109 <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string>
110 <string name="da_password_quality">Password Quality</string>
111 <string name="da_password_quality_alphabetic">Alphabetic</string>
112 <string name="da_password_quality_alphanumeric">Alphanumeric</string>
113 <string name="da_password_quality_numeric">Numeric</string>
114 <string name="da_password_quality_something">Something</string>
Brian Muramatsu713049d2011-06-23 18:35:36 -0700115 <string name="da_password_minimum_length">Minimum Password Length</string>
116 <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string>
117 <string name="da_maximum_time_to_lock">Maximum Time to Lock</string>
118 <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string>
119
120 <string name="da_screen_lock_test">Screen Lock Test</string>
121 <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow
122 method immediately locks the screen. It should lock the screen immediately despite any
Christine Chen523d04c2011-09-22 11:45:50 -0700123 settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen.
Brian Muramatsu76c50252011-06-29 17:12:29 -0700124 Your screen should be locked and require the password to be entered.
Brian Muramatsu713049d2011-06-23 18:35:36 -0700125 </string>
126 <string name="da_force_lock">Force Lock</string>
Brian Muramatsu713049d2011-06-23 18:35:36 -0700127 <string name="da_lock_success">It appears the screen was locked successfully!</string>
128 <string name="da_lock_error">It does not look like the screen was locked...</string>
129
Andres Morales469db8a2015-07-22 10:47:13 -0700130 <!-- Strings for lock bound keys test -->
131 <string name="sec_lock_bound_key_test">Lock Bound Keys Test</string>
132 <string name="sec_lock_bound_key_test_info">
133 This test ensures that Keystore cryptographic keys that are bound to lock screen authentication
134 are unusable without a recent enough authentication. You need to set up a screen lock in order to
135 complete this test. If available, this test should be run by using fingerprint authentication
136 as well as PIN/pattern/password authentication.
137 </string>
Andres Morales626bb612015-07-22 16:01:15 -0700138 <string name="sec_fingerprint_bound_key_test">Fingerprint Bound Keys Test</string>
139 <string name="sec_fingerprint_bound_key_test_info">
140 This test ensures that Keystore cryptographic keys that are bound to fingerprint authentication
141 are unusable without an authentication. You need to set up a fingerprint order to
142 complete this test.
143 </string>
144 <string name="sec_fp_dialog_message">Authenticate now with fingerprint</string>
145 <string name="sec_fp_auth_failed">Authentication failed</string>
Andres Morales469db8a2015-07-22 10:47:13 -0700146 <string name="sec_start_test">Start Test</string>
147
Brian Muramatsue891acb2011-05-19 16:02:39 -0700148 <!-- Strings for BluetoothActivity -->
149 <string name="bluetooth_test">Bluetooth Test</string>
Jeff Davidson112f2792011-08-22 09:46:46 -0700150 <string name="bluetooth_test_info">The Bluetooth Control tests check whether or not the device
Brian Muramatsue891acb2011-05-19 16:02:39 -0700151 can disable and enable Bluetooth properly.\n\nThe Device Communication tests require two
152 devices to pair and exchange messages. The two devices must be:
153 \n\n1. a candidate device implementation running the software build to be tested
154 \n\n2. a separate device implementation already known to be compatible</string>
155
Brian Muramatsue891acb2011-05-19 16:02:39 -0700156 <string name="bt_control">Bluetooth Control</string>
157 <string name="bt_device_communication">Device Communication</string>
John Du73462362013-07-26 12:28:28 -0700158 <string name="bt_le">Bluetooth Low Energy</string>
Brian Muramatsue891acb2011-05-19 16:02:39 -0700159
160 <string name="bt_toggle_bluetooth">Toggle Bluetooth</string>
161 <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string>
162 <string name="bt_enable_bluetooth">Enable Bluetooth</string>
163 <string name="bt_disable_bluetooth">Disable Bluetooth</string>
164 <string name="bt_disabling">Disabling Bluetooth...</string>
165 <string name="bt_disabling_error">Could not disable Bluetooth...</string>
166
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700167 <string name="bt_connection_access_server">Connection Access Server</string>
168 <string name="bt_connection_access_client">Connection Access Client</string>
169 <string name="bt_connection_access_server_info">
170 Start the CTS Verifier on another device, start the Bluetooth test, and choose
destradaa65c7cdb2013-10-28 16:36:12 -0700171 \"Connection Access Client\" to setup the test.
172 \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700173 using the \"Make Discoverable\" and \"Pick Server\" buttons.
174 \n\nA connection access request should appear on the server and enable the pass button.
175 </string>
176 <string name="bt_connection_access_client_info">
177 Start the CTS Verifier on another device, start the Bluetooth test, and choose
destradaa65c7cdb2013-10-28 16:36:12 -0700178 \"Connection Access Server\" to complete the test.
179 \n\nMake the device acting as the server discoverable and connect to it via the
180 \"Pick Server\" button. Check that the server displays the connection access request
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700181 dialog. The client device does not need to do anything else.
182 </string>
183 <string name="bt_ca_dialog">Was the connection access request dialog shown?</string>
184 <string name="bt_ca_tips">
185 Tap the \"Bluetooth Settings\" button and check that both devices are not paired
186 before running the test.
187 \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth
188 devices together and start the test.
189 </string>
190
Brian Muramatsue891acb2011-05-19 16:02:39 -0700191 <string name="bt_secure_server">Secure Server</string>
192 <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>
193 <string name="bt_insecure_server">Insecure Server</string>
194 <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>
195 <string name="bt_waiting">Waiting for client...</string>
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700196 <string name="bt_listening">Listening...</string>
Brian Muramatsue891acb2011-05-19 16:02:39 -0700197 <string name="bt_connecting">Connecting...</string>
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700198 <string name="bt_connected">Connected</string>
Brian Muramatsue891acb2011-05-19 16:02:39 -0700199 <string name="bt_received_messages">Received Messages</string>
200 <string name="bt_sent_messages">Sent Messages</string>
201 <string name="bt_no_messages">No messages</string>
202 <string name="bt_make_discoverable">Make Discoverable</string>
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700203 <string name="bt_pick_server">Pick Server</string>
Brian Muramatsu8b98f7c2011-06-08 14:50:24 -0700204 <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string>
205 <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string>
Brian Muramatsue891acb2011-05-19 16:02:39 -0700206
207 <string name="bt_secure_client">Secure Client</string>
208 <string name="bt_insecure_client">Insecure Client</string>
209
210 <string name="bt_device_picker">Device Picker</string>
211 <string name="bt_paired_devices">Paired Devices</string>
212 <string name="bt_new_devices">New Devices</string>
213 <string name="bt_no_devices">No devices</string>
214 <string name="bt_scan">Scan for Devices</string>
215 <string name="bt_scanning">Scanning...</string>
216 <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>
217 <string name="bt_settings">Bluetooth Settings</string>
218
John Du73462362013-07-26 12:28:28 -0700219 <!-- BLE client side strings -->
220 <string name="ble_client_service_name">Bluetooth LE GATT Client Handler Service</string>
221 <string name="ble_client_test_name">BLE Client Test</string>
Yicheng Fan24bf0102014-11-24 16:17:58 -0800222 <string name="ble_client_connect_name">BLE Client Connect</string>
223 <string name="ble_discover_service_name">BLE Discover Service</string>
224 <string name="ble_read_characteristic_name">BLE Read Characteristic</string>
225 <string name="ble_write_characteristic_name">BLE Write Characteristic</string>
226 <string name="ble_reliable_write_name">BLE Reliable Write</string>
227 <string name="ble_notify_characteristic_name">BLE Notify Characteristic</string>
228 <string name="ble_read_descriptor_name">BLE Read Descriptor</string>
229 <string name="ble_write_descriptor_name">BLE Write Descriptor</string>
230 <string name="ble_read_rssi_name">BLE Read RSSI</string>
231 <string name="ble_client_disconnect_name">BLE Client Disconnect</string>
John Du73462362013-07-26 12:28:28 -0700232 <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>
233 <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>
234 <string name="ble_discover_service_info">Verify that the service is discovered when you press the "Discover Service" button.</string>
235 <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>
236 <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>
237 <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>
238 <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>
239 <string name="ble_client_disconnect_info">Verify that the device is disconnected when you press the "Disconnect" button</string>
240 <string name="ble_address">Bluetooth address</string>
241 <string name="ble_connect">Connect</string>
242 <string name="ble_discover_service">Discover service</string>
243 <string name="ble_write_hint">Nothing to write yet</string>
244 <string name="ble_read_hint">Nothing read yet</string>
245 <string name="ble_write">Write</string>
246 <string name="ble_read">Read</string>
247 <string name="ble_begin_write">Begin write</string>
248 <string name="ble_execute_write">Execute write</string>
249 <string name="ble_begin_notification">Begin notification</string>
250 <string name="ble_stop_notification">Stop notification</string>
251 <string name="ble_waiting_notification">Waiting on notification</string>
252 <string name="ble_read_rssi">Read RSSI</string>
253 <string name="ble_disconnect">Disconnect</string>
Yicheng Fanc8882202014-11-10 12:10:10 -0800254 <string name="ble_test_text">TEST</string>
John Du73462362013-07-26 12:28:28 -0700255
256 <!-- BLE server side strings -->
257 <string name="ble_server_service_name">Bluetooth LE GATT Server Handler Service</string>
258 <string name="ble_server_start_name">BLE Server Test</string>
259 <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>
260 <string name="ble_server_receiving_connect">Waiting on connection from BLE client.</string>
261 <string name="ble_server_add_service">Adding service to BLE server.</string>
262 <string name="ble_server_write_characteristic">Waiting on write characteristic request</string>
263 <string name="ble_server_read_characteristic">Waiting on read characteristic request</string>
264 <string name="ble_server_write_descriptor">Waiting on write descriptor request</string>
265 <string name="ble_server_read_descriptor">Waiting on read descriptor request</string>
266 <string name="ble_server_reliable_write">Waiting on reliable write from client</string>
267 <string name="ble_server_receiving_disconnect">Waiting on disconnection from BLE client</string>
268
Yicheng Fana6736922014-07-08 14:53:55 -0700269 <!-- BLE advertiser side strings -->
270 <string name="ble_advertiser_test_name">BLE Advertiser Test</string>
271 <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>
272 <string name="ble_advertiser_service_name">Bluetooth LE Advertiser Handler Service</string>
Yicheng Fana6736922014-07-08 14:53:55 -0700273 <string name="ble_privacy_mac_name">BLE Privacy Mac</string>
274 <string name="ble_privacy_mac_info">BLE Advertiser should advertise in non-repeating MAC address.</string>
Yicheng Fan994d1dd2014-09-24 16:02:35 -0700275 <string name="ble_advertiser_privacy_mac_instruction">Click start to start advertising, you can disconnect USB and lock the screen of advertiser. Counts and mac address will show on scanner. You may receive message that this device does not support BLE advertising.</string>
Yicheng Fan036fc0cb12014-07-21 19:47:02 -0700276 <string name="ble_power_level_name">BLE Tx Power Level</string>
277 <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 Fan994d1dd2014-09-24 16:02:35 -0700278 <string name="ble_advertiser_power_level_instruction">Click start to start multi-advertising. Data packets are advertised in 4 different power levels. You may receive message that this device does not support multi advertising. If advertiser does not advertise in 4 power levels, neither you receive the error message, you may not stop the advertising in previous test, or this device does not support 4 advertisers at the same time. Try rebooting the device and run the test to free those advertisers in use.</string>
Yicheng Fancb7cbc62014-08-13 18:11:30 -0700279 <string name="ble_advertiser_scan_filter_name">BLE Hardware Scan Filter</string>
Yicheng Fan63b5d502014-10-03 16:38:54 -0700280 <string name="ble_advertiser_scan_filter_info">BLE Advertiser advertises with 2 different data separately. One can wake up the scanner, the other cannot. This test cares about behavior on scanner only.</string>
Yicheng Fancb7cbc62014-08-13 18:11:30 -0700281 <string name="ble_advertiser_scannable">Scannable advertising</string>
Yicheng Fan994d1dd2014-09-24 16:02:35 -0700282 <string name="ble_advertiser_scannable_instruction">Start scannable advertising, expect scanner consume more power on Monsoon monitor, or see log of GattService from scanner logcat.</string>
Yicheng Fancb7cbc62014-08-13 18:11:30 -0700283 <string name="ble_advertiser_unscannable">Unscannble advertising</string>
Yicheng Fan994d1dd2014-09-24 16:02:35 -0700284 <string name="ble_advertiser_unscannable_instruction">Start unscannable advertising, expect scanner stay calm on Monsoon monitor, no log of GattService from scanner logcat.</string>
Yicheng Fancb7cbc62014-08-13 18:11:30 -0700285 <string name="ble_advertiser_start">Start</string>
286 <string name="ble_advertiser_stop">Stop</string>
Yicheng Fana6736922014-07-08 14:53:55 -0700287
288 <!-- BLE scanner side strings -->
Yicheng Fan036fc0cb12014-07-21 19:47:02 -0700289 <string name="ble_scanner_test_name">BLE Scanner Test</string>
Yicheng Fana6736922014-07-08 14:53:55 -0700290 <string name="ble_scanner_service_name">Bluetooth LE Scanner Handler Service</string>
Yicheng Fan036fc0cb12014-07-21 19:47:02 -0700291 <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 Fana6736922014-07-08 14:53:55 -0700292 <string name="ble_scanner_privacy_mac">Hold for 15 min to see if receive a different MAC address from advertiser.</string>
Yicheng Fan994d1dd2014-09-24 16:02:35 -0700293 <string name="ble_scanner_privacy_mac_instruction">Mac address, counts are shown on screen. It should continuously receive data packet from advertiser. Every 15 min, a new mac address should show up, which prevents mac address disclosure.</string>
Yicheng Fan036fc0cb12014-07-21 19:47:02 -0700294 <string name="ble_ultra_low">Ultra low</string>
295 <string name="ble_low">Low</string>
296 <string name="ble_medium">Medium</string>
297 <string name="ble_high">High</string>
Yicheng Fan63b5d502014-10-03 16:38:54 -0700298 <string name="ble_scanner_power_level_instruction">Count: Ultra low &lt; low &lt; medium &lt; high\nRssi: Ultra low &lt; low &lt; medium &lt; high\nDistance to see count freezing: Ultra low &lt; low &lt; medium &lt; high\nA common error is ultra low, low and medium behave similarly, with similar rssi, freeze at similar distance.\n\n All power level receive a different mac address. After 15 mins, a green text "Get a new Mac address" will show up.</string>
Yicheng Fancb7cbc62014-08-13 18:11:30 -0700299 <string name="ble_scanner_scan_filter_name">BLE Hardware Scan Filter</string>
300 <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>
Yicheng Fan63310ee2014-10-27 11:26:28 -0700301 <string name="ble_scanner_scan_filter_instruction">Scan filter is to scan data with service UUID = 0x6666 only. If you scan without scan filter, data with service UUID = 0x5555 and 0x6666 will show up on screen.\nFor monsoon test:\n\tClick scan with filter, lock the screen, connect to monsoon. It will not wake up when advertiser is advertising unscannable data packets, but will show a peak in power usage when advertiser is advertising scannable data.\nFor logcat test:\n\tClick scan with filter, logcat the scanner. No data will be received by GattService when advertiser is advertising unscannable data.</string>
Yicheng Fancb7cbc62014-08-13 18:11:30 -0700302 <string name="ble_scan_with_filter">Scan with filter</string>
303 <string name="ble_scan_without_filter">Scan without filter</string>
Yicheng Fanc8882202014-11-10 12:10:10 -0800304 <string name="ble_scan_start">Start scan</string>
305 <string name="ble_scan_stop">Stop scan</string>
Yicheng Fana6736922014-07-08 14:53:55 -0700306
Brian Muramatsuaccc6842010-08-11 18:57:27 -0700307 <!-- Strings for FeatureSummaryActivity -->
Dan Morrill5df275b2010-08-11 12:19:19 -0700308 <string name="feature_summary">Hardware/Software Feature Summary</string>
Brian Muramatsu14e1cbb2010-09-13 18:33:39 -0700309 <string name="feature_summary_info">This is a test for...</string>
Dan Morrill5df275b2010-08-11 12:19:19 -0700310 <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string>
311 <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string>
312 <string name="fs_no_data">No data.</string>
Dan Morrill71351d82010-10-20 15:26:00 -0700313 <string name="fs_legend_good">standard feature reported by device</string>
314 <string name="fs_legend_indeterminate">optional feature not reported by device</string>
315 <string name="fs_legend_warning">non-standard feature reported by device</string>
316 <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string>
317
Dan Morrill5df275b2010-08-11 12:19:19 -0700318 <string name="empty"></string>
319
Raymond054a4412015-03-17 20:51:23 -0700320 <!-- Strings for HifiUltrasoundTestActivity -->
Raymondf15f8162015-05-19 11:58:43 -0700321 <string name="hifi_ultrasound_test">Hifi Ultrasound Microphone Test</string>
Raymond84218672015-05-13 11:58:12 -0700322 <string name="hifi_ultrasound_test_info">
Raymondf15f8162015-05-19 11:58:43 -0700323 This is a test for near-ultrasound (18500Hz - 20000Hz) microphone response.\n
Raymond84218672015-05-13 11:58:12 -0700324 This test requires two devices.\n</string>
325 <string name="hifi_ultrasound_test_play">PLAY</string>
Raymond054a4412015-03-17 20:51:23 -0700326 <string name="hifi_ultrasound_test_record">RECORD</string>
Raymond054a4412015-03-17 20:51:23 -0700327 <string name="hifi_ultrasound_test_plot">PLOT</string>
328 <string name="hifi_ultrasound_test_dismiss">DISMISS</string>
Raymondf15f8162015-05-19 11:58:43 -0700329 <string name="hifi_ultrasound_test_ok">OK</string>
Raymond054a4412015-03-17 20:51:23 -0700330 <string name="hifi_ultrasound_test_instruction1">
Raymondf15f8162015-05-19 11:58:43 -0700331 Open Hifi Ultrasound Microphone Test on the test device and the reference device.\n
332 Set the media volume of the reference device at 70% and hold it with one hand.\n
Raymond84218672015-05-13 11:58:12 -0700333 Hold the testing device with the other hand\n
334 Press the RECORD button on the testing device, then the PLAY button on the reference device within one second.\n
Raymondf15f8162015-05-19 11:58:43 -0700335 After the test, report result on the testing (recording) device.\n</string>
Raymond054a4412015-03-17 20:51:23 -0700336 <string name="hifi_ultrasound_test_pass">PASS</string>
337 <string name="hifi_ultrasound_test_fail">FAIL</string>
Raymond84218672015-05-13 11:58:12 -0700338 <string name="hifi_ultrasound_test_default_false_string">false</string>
Raymond84218672015-05-13 11:58:12 -0700339 <string name="hifi_ultrasound_test_mic_no_support">
340 Device does not support near-ultrasound recording.\n
Raymondf15f8162015-05-19 11:58:43 -0700341 All new phones and tablets MUST support near-ultrasound recording.\n
342 Report FAIL if this is a new device, report PASS if this is an updating device.\n</string>
Raymond84218672015-05-13 11:58:12 -0700343 <string name="hifi_ultrasound_test_spkr_no_support">
344 Device does not support near-ultrasound playback.\n
345 If this is your reference device, please use a different reference device.\n</string>
346
Raymondf15f8162015-05-19 11:58:43 -0700347 <string name="hifi_ultrasound_speaker_test">Hifi Ultrasound Speaker Test</string>
Raymond84218672015-05-13 11:58:12 -0700348 <string name="hifi_ultrasound_speaker_test_info">
Raymondf15f8162015-05-19 11:58:43 -0700349 This is a test for near-ultrasound (18500Hz - 20000Hz) speaker response.\n
Raymond84218672015-05-13 11:58:12 -0700350 This test requires two devices.\n</string>
351 <string name="hifi_ultrasound_speaker_test_instruction1">
Raymondf15f8162015-05-19 11:58:43 -0700352 Open Hifi Ultrasound Speaker Test on the test device and the reference device.\n
353 Set the media volume of the testing device at 70% and hold it with one hand.\n
Raymond84218672015-05-13 11:58:12 -0700354 Hold the reference device with the other hand\n
355 Press the RECORD button on the reference device, then the PLAY button on the testing device within one second.\n
Raymondf15f8162015-05-19 11:58:43 -0700356 After the test, report result on the testing (playback) device.\n</string>
Raymond84218672015-05-13 11:58:12 -0700357 <string name="hifi_ultrasound_speaker_test_mic_no_support">
358 Device does not support near-ultrasound recording.\n
359 If this is your reference device, please use a different reference device.\n</string>
360 <string name="hifi_ultrasound_speaker_test_spkr_no_support">
361 Device does not support near-ultrasound playback.\n
Raymondf15f8162015-05-19 11:58:43 -0700362 All new phones and tablets MUST support near-ultrasound playback.\n
363 Report FAIL if this is a new device, report PASS if this is an updating device.\n</string>
364 <string name="hifi_ultrasound_speaker_test_test_side">
365 Please wait for the result on the reference device then report here.</string>
366 <string name="hifi_ultrasound_speaker_test_reference_side">
367 Please report on the testing device.\n</string>
Raymond054a4412015-03-17 20:51:23 -0700368
Nick Pelly1fe08972012-05-14 17:35:58 -0700369 <!-- Strings for Location tests -->
370 <string name="location_gps_test">GPS Test</string>
371 <string name="location_gps_test_info">This test verifies basic GPS behavior
372 and callback scheduling.
373 Make sure the device has line of sight to GPS satellites
374 (for example, outside, or near a window)
375 and then press OK to run the automated tests.</string>
376
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700377 <!-- Strings for NfcTestActivity -->
378 <string name="nfc_test">NFC Test</string>
379 <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with
380 NFC enabled to exchange messages. One device must be the candidate device running the
381 software build to be tested, while the other device must be an implementation already
382 known to be compatible.\n\nThe Tag Verification tests check that your
383 device can properly read and write to tags of different technologies. The MIFARE
384 Ultralight test is only applicable for devices that support it.
Martijn Coenen109d7622013-09-24 07:09:29 -0700385 \n\nThe Host-based card emulation tests check that your device has properly implemented
386 host-based card emulation.
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700387 </string>
388
389 <string name="nfc_not_enabled">NFC is not enabled!</string>
destradaa65c7cdb2013-10-28 16:36:12 -0700390 <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700391 button below to goto Settings and enable it.</string>
392 <string name="nfc_settings">NFC Settings</string>
393
Nick Pellya9631ce2011-10-31 14:18:46 -0700394 <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string>
395 <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled.
396 Click the button below to goto NFC Sharing Settings and enable it.</string>
397 <string name="ndef_push_settings">NFC Sharing Settings</string>
398
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700399 <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string>
400 <string name="nfc_ndef_push_sender">NDEF Push Sender</string>
401 <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string>
Martijn Coenenbe6dfed2015-06-11 14:52:13 +0200402 <string name="nfc_llcp_version_check">LLCP version check</string>
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700403
404 <string name="nfc_tag_verification">Tag Verification</string>
405 <string name="nfc_ndef">NDEF</string>
406 <string name="nfc_mifare_ultralight">MIFARE Ultralight</string>
407
408 <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on
409 another device and touch the devices back to back. The receiver should show a
410 dialog indicating it has successfully received the correct message!</string>
411 <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another
412 device running the \"CTS Verifier NDEF Receiver\"...</string>
413
414 <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on
415 another device and touch the devices back to back. The receiver should show a
416 dialog indicating it has successfully received the correct message!</string>
417 <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another
418 device running the \"CTS Verifier NDEF Sender\"...</string>
419 <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push
420 message.</string>
destradaa65c7cdb2013-10-28 16:36:12 -0700421 <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700422 message.</string>
423
Martijn Coenenbe6dfed2015-06-11 14:52:13 +0200424 <string name="nfc_llcp_version_check_info">This test requires two candidate devices
425 with NFC enabled to exchange P2P messages. Start the \"LLCP version check\" test on
426 the other candidate device also, and touch the devices back to back. This test
427 then verifies that the candidate device correctly advises the LLCP version as 1.2</string>
428 <string name="nfc_llcp_version_check_failure">The candidate devices does not report LLCP
429 version 1.2 or higher.</string>
430 <string name="nfc_llcp_version_check_success">The candidate device has a valid LLCP version.</string>
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700431 <string name="nfc_tag_verifier">NFC Tag Verifier</string>
432 <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read
433 a tag of the chosen technology.</string>
434
435 <string name="nfc_scan_tag">Place device on a writable %s tag...</string>
436 <string name="nfc_write_tag_title">Writable tag discovered!</string>
437 <string name="nfc_write_tag_message">Press OK to write to this tag...</string>
438 <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string>
439 <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string>
440 <string name="nfc_no_tech">No tag technologies detected...</string>
441
442 <string name="nfc_writing_tag">Writing NFC tag...</string>
443 <string name="nfc_writing_tag_error">Error writing NFC tag...</string>
444 <string name="nfc_reading_tag">Reading NFC tag...</string>
445 <string name="nfc_reading_tag_error">Error reading NFC tag...</string>
446
447 <string name="nfc_result_success">Test passed!</string>
448 <string name="nfc_result_failure">Test failed!</string>
449
450 <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string>
451 <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string>
452
Martijn Coenen109d7622013-09-24 07:09:29 -0700453 <string name="nfc_hce">Host-based card emulation</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700454 <string name="nfc_hce_reader_tests">HCE reader tests</string>
455 <string name="nfc_hce_emulator_tests">HCE emulator tests</string>
456 <string name="nfc_hce_emulator_test_info">The host-based card emulation
457 tests require two devices to be completed. The HCE emulator tests are used
458 to actually test the host-based card emulation feature of the device-under-test. So the
459 device running the emulator tests must be the candidate device running the software
460 to be tested. \n\nFor each emulator test, there is a corresponding "reader test"
461 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS
Martijn Coenen0cf0c962014-02-28 14:22:15 -0800462 and makes sure the device-under-test implements card emulation correctly.</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700463 <string name="nfc_hce_reader_test_info">The host-based card emulation
464 tests require two devices to be completed. The HCE emulator tests are used
465 to actually test the host-based card emulation feature of the device-under-test. So the
466 device running the emulator tests must be the candidate device running the software
467 to be tested. \n\nFor each emulator test, there is a corresponding "reader test"
468 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS
469 and makes sure the device-under-test implements card emulation correctly.
470 </string>
Martijn Coenen0cf0c962014-02-28 14:22:15 -0800471 <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 Coenen109d7622013-09-24 07:09:29 -0700472 <string name="nfc_hce_please_wait">Please wait</string>
473 <string name="nfc_hce_setting_up">Setting up card emulation services...</string>
Martijn Coenenc94c0122013-10-21 14:44:54 -0700474
475 <string name="nfc_hce_default_route_emulator">Default route (Emulator)</string>
476 <string name="nfc_hce_default_route_reader">Default route (Reader)</string>
477 <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>
478
479 <string name="nfc_hce_protocol_params_emulator">Protocol parameters (Emulator)</string>
480 <string name="nfc_hce_protocol_params_reader">Protocol parameters (Reader)</string>
Martijn Coenen7294e322013-11-13 10:36:05 -0800481 <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 Coenenc94c0122013-10-21 14:44:54 -0700482
Martijn Coenen109d7622013-09-24 07:09:29 -0700483 <string name="nfc_hce_single_payment_emulator">Single payment (Emulator)</string>
484 <string name="nfc_hce_single_payment_reader">Single payment (Reader)</string>
485
486 <string name="nfc_hce_dual_payment_emulator">Two payment services (Emulator)</string>
487 <string name="nfc_hce_dual_payment_reader">Two payment services (Reader)</string>
488
489 <string name="nfc_hce_change_default_emulator">Change default payment service (Emulator)</string>
490 <string name="nfc_hce_change_default_reader">Change default payment service (Reader)</string>
491
492 <string name="nfc_hce_tap_reader_title">Tap reader</string>
493 <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>
494
495 <string name="nfc_hce_single_non_payment_emulator">Single non-payment (Emulator)</string>
496 <string name="nfc_hce_single_non_payment_reader">Single non-payment (Reader)</string>
497
498 <string name="nfc_hce_dual_non_payment_emulator">Two non-payment services (Emulator)</string>
499 <string name="nfc_hce_dual_non_payment_reader">Two non-payment services (Reader)</string>
500
501 <string name="nfc_hce_conflicting_non_payment_emulator">Two conflicting non-payment services (Emulator)</string>
502 <string name="nfc_hce_conflicting_non_payment_reader">Two conflicting non-payment services (Reader)</string>
503
Martijn Coenene71e3742014-05-23 16:35:55 -0700504 <string name="nfc_hce_foreground_non_payment_emulator">Foreground override non-payment services (Emulator)</string>
505 <string name="nfc_hce_foreground_non_payment_reader">Foreground override non-payment services (Reader)</string>
506 <string name="nfc_hce_foreground_non_payment_help">This test enables two non-payment services with conflicting AIDs. It then uses Androids API to allow the foreground app to set a preference for a specific service. This should prevent a popup dialog from showing. If you see a popup dialog during this asking you to select an app, this test has failed.</string>
507
508 <string name="nfc_hce_foreground_payment_emulator">Foreground override payment services (Emulator)</string>
509 <string name="nfc_hce_foreground_payment_reader">Foreground override payment services (Reader)</string>
510 <string name="nfc_hce_foreground_payment_help">This test enables two payment services, and asks you to set one as the default service. It then uses Androids API to allow the foreground app to set a preference for the non-default service. This will cause the non-default payment service to be invoked.</string>
511 <string name="nfc_hce_change_favor_foreground">This test requires the "Favor foreground app" setting to be enabled. Tap OK to go to Tap and Pay settings and check the Favor foreground app option</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700512 <string name="nfc_hce_offhost_service_emulator">Off-host service (Emulator)</string>
513 <string name="nfc_hce_offhost_service_reader">Off-host service (Reader)</string>
514 <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>
515
516 <string name="nfc_hce_on_and_offhost_service_emulator">On and off-host services (Emulator)</string>
517 <string name="nfc_hce_on_and_offhost_service_reader">On and off-host services (Reader)</string>
518 <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>
519
520 <string name="nfc_hce_tap_test_emulator">50 successful taps test (Emulator)</string>
521 <string name="nfc_hce_tap_test_reader">50 successful taps test (Reader)</string>
522 <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>
523 <string name="nfc_hce_throughput_emulator">HCE throughput test (Emulator)</string>
524 <string name="nfc_hce_throughput_reader">HCE throughput test (Reader)</string>
525 <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 Coenene71e3742014-05-23 16:35:55 -0700526 <string name="nfc_hce_change_preinstalled_wallet">The device has an installed payment application that is currently set as default. To complete the test, you will be asked whether you want to make another app the default app. Select yes.</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700527 <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>
528 <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>
Martijn Coenene71e3742014-05-23 16:35:55 -0700529
530 <string name="nfc_hce_payment_dynamic_aids_emulator">Dynamic payment AIDs (Emulator)</string>
531 <string name="nfc_hce_payment_dynamic_aids_reader">Dynamic payment AIDs (Reader)</string>
532 <string name="nfc_hce_payment_dynamic_aids_help">This test tries to register dynamic AIDs for a payment service.</string>
533
Martijn Coenen7459cf22014-12-17 16:57:23 -0800534 <string name="nfc_hce_large_num_aids_emulator">Large number of AIDs (Emulator)</string>
535 <string name="nfc_hce_large_num_aids_reader">Large number of AIDs (Reader)</string>
536 <string name="nfc_hce_large_num_aids_help">This test tries to register a large number of different AIDs, to make sure there are no limitations on the maximum amount of HCE apps on the device. Note that this test may take a few seconds to complete; please be patient.</string>
537
Martijn Coenene71e3742014-05-23 16:35:55 -0700538 <string name="nfc_hce_payment_prefix_aids_emulator">Payment prefix AIDs (Emulator)</string>
539 <string name="nfc_hce_payment_prefix_aids_reader">Payment prefix AIDs (Reader)</string>
540 <string name="nfc_hce_payment_prefix_aids_help">This test statically registers prefix AIDs for a payment service.</string>
541
542 <string name="nfc_hce_payment_prefix_aids_emulator_2">Payment prefix AIDs 2 (Emulator)</string>
543 <string name="nfc_hce_payment_prefix_aids_reader_2">Payment prefix AIDs 2 (Reader)</string>
544
545 <string name="nfc_hce_other_prefix_aids_emulator">Other prefix AIDs (Emulator)</string>
546 <string name="nfc_hce_other_prefix_aids_reader">Other prefix AIDs (Reader)</string>
547 <string name="nfc_hce_other_prefix_aids_help">This test dynamically registers prefix AIDs for a non-payment service.</string>
548
549 <string name="nfc_hce_other_conflicting_prefix_aids_emulator">Conflicting non-payment prefix AIDs (Emulator)</string>
550 <string name="nfc_hce_other_conflicting_prefix_aids_reader">Conflicting non-payment prefix AIDs (Reader)</string>
551 <string name="nfc_hce_other_conflicting_prefix_aids_help">This test registers conflicting prefix AIDs and makes sure AID conflict detection with prefix AIDs works properly. When tapping the first time, you will be shown a dialog that asks you to choose between TransportService #1 and TransportService #2. Select TransportService #2. Verify a dialog is shown that asks you to tap again to complete. Now tap again, and if communication with TransportService #2 is successfull the pass button will be enabled."</string>
552
Martijn Coenen109d7622013-09-24 07:09:29 -0700553 <string name="nfc_payment_service_desc">NFC Payment service</string>
554 <string name="ppse">PPSE</string>
555 <string name="mastercard">MasterCard</string>
Martijn Coenene71e3742014-05-23 16:35:55 -0700556 <string name="visa">Visa</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700557 <string name="paymentService1">Payment Service #1</string>
558 <string name="paymentService2">Payment Service #2</string>
559 <string name="transportService1">TransportService #1</string>
560 <string name="transportService2">TransportService #2</string>
561 <string name="accessService">AccessService</string>
562 <string name="offhostService">OffhostService</string>
563
destradaa65c7cdb2013-10-28 16:36:12 -0700564 <!-- Strings for Sensor Test Activities -->
destradaa0dcd7102014-09-23 14:22:54 -0700565 <string name="snsr_device_admin_receiver">Sensor Tests Device Admin Receiver</string>
destradaa9732fb12014-08-15 10:40:50 -0700566 <string name="snsr_test_summary">Tests passed: %1$d, Tests skipped: %2$d, Tests failed: %3$d</string>
destradaa2581a9e2014-09-26 13:25:19 -0700567 <string name="snsr_test_complete">Test completed without errors.</string>
568 <string name="snsr_test_complete_with_errors">Test completed with errors: those errors
569 might degrade the user experience and might cause some applications to misbehave. They are
570 not required for Android Compatibility at this time, but will in a future release.</string>
destradaa9732fb12014-08-15 10:40:50 -0700571 <string name="snsr_test_pass">PASS</string>
572 <string name="snsr_test_skipped">SKIPPED</string>
573 <string name="snsr_test_fail">FAIL</string>
destradaafd031b92014-10-10 10:45:51 -0700574 <string name="snsr_execution_time">Test execution time %1$s sec</string>
Peng Xuc14f0122015-04-28 18:38:38 -0700575 <string name="snsr_rvcvxchk_test">Rotation Vector CV XCheck</string>
576 <string name="snsr_rvcvxchk_test_rec">Rotation Vector CV XCheck Recording</string>
destradaa9732fb12014-08-15 10:40:50 -0700577
578 <!-- Strings to interact with users in Sensor Tests -->
579 <string name="snsr_test_play_sound">A sound will be played once the verification is complete...</string>
destradaafc687ea2014-08-27 14:47:59 -0700580 <string name="snsr_no_interaction">Leave the device on top of a flat surface.</string>
581 <string name="snsr_interaction_needed">Once the test begins, you will have to wave your hand over the front of the device.</string>
destradaa9732fb12014-08-15 10:40:50 -0700582 <string name="snsr_device_steady">Keep the device steady.</string>
destradaafc687ea2014-08-27 14:47:59 -0700583 <string name="snsr_keep_device_rotating_clockwise">Once the test begins, you will have to keep rotating the device clockwise.</string>
destradaa9732fb12014-08-15 10:40:50 -0700584 <string name="snsr_wait_for_user">Press \'Next\' to continue.</string>
destradaaa0b3bbc2014-09-03 14:08:00 -0700585 <string name="snsr_wait_to_begin">Press \'Next\' to begin.</string>
destradaa9732fb12014-08-15 10:40:50 -0700586 <string name="snsr_on_complete_return">After completing the task, go back to this test.</string>
destradaa139500e2014-08-22 16:01:52 -0700587 <string name="snsr_movement_expected">Movement was expected during the test. Found=%1$b.</string>
destradaaa26b12c2014-10-10 17:22:11 -0700588 <string name="snsr_sensor_feature_deactivation">Turn off any special features installed in the
589 device that register for sensors. Once you are done, you can begin the test.</string>
John Rusnak7ceff362014-08-04 15:49:51 -0700590 <string name="snsr_setting_mode_request">You will be redirected to set \'%1$s\' to: %2$s.</string>
591 <string name="snsr_setting_mode_set">\'%1$s\' set to: %2$s.</string>
592 <string name="snsr_setting_mode_not_set">\'%1$s\' not set to: %2$s.</string>
destradaa3dccf1f02014-08-22 18:11:36 -0700593 <string name="snsr_setting_airplane_mode">Airplane mode</string>
594 <string name="snsr_setting_screen_brightness_mode">Adaptive Brightness</string>
595 <string name="snsr_setting_auto_rotate_screen_mode">Auto-rotate screen</string>
destradaafc687ea2014-08-27 14:47:59 -0700596 <string name="snsr_setting_keep_screen_on">Stay awake</string>
destradaa3dccf1f02014-08-22 18:11:36 -0700597 <string name="snsr_setting_location_mode">Location</string>
destradaa4d4efc82014-10-17 14:50:37 -0700598 <string name="snsr_setting_ambient_display">Ambient Display</string>
destradaa2581a9e2014-09-26 13:25:19 -0700599 <string name="snsr_pass_on_error">Pass Anyway</string>
destradaa2d3dc7d2014-09-26 16:52:06 -0700600 <string name="snsr_run_automated_tests">The screen will be turned off to execute the tests,
601 when tests complete, the device will vibrate and the screen will be turned back on.</string>
destradaa9732fb12014-08-15 10:40:50 -0700602
destradaa65c7cdb2013-10-28 16:36:12 -0700603 <!-- Accelerometer -->
Dan Morrill5df275b2010-08-11 12:19:19 -0700604 <string name="snsr_accel_test">Accelerometer Test</string>
Dan Morrill71351d82010-10-20 15:26:00 -0700605 <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>
destradaa65c7cdb2013-10-28 16:36:12 -0700606 <string name="snsr_accel_m_test">Accelerometer Measurement Tests</string>
destradaa31f57432014-09-26 14:47:28 -0700607 <string name="snsr_accel_test_face_up">Place the device on a flat surface with the screen
608 facing the ceiling.</string>
609 <string name="snsr_accel_test_face_down">Place the device on a flat surface with the screen
610 facing it.</string>
destradaa16203b42014-09-29 13:26:51 -0700611 <string name="snsr_accel_test_right_side">Place the device in a flat surface resting vertically
612 on its right side.</string>
613 <string name="snsr_accel_test_left_side">Place the device in a flat surface resting vertically
614 on its left side.</string>
615 <string name="snsr_accel_test_top_side">Place the device in a flat surface resting vertically
616 on its top side.</string>
617 <string name="snsr_accel_test_bottom_side">Place the device in a flat surface resting vertically
618 on its bottom side.</string>
Brian Muramatsu729de482011-05-12 12:26:58 -0700619
destradaa65c7cdb2013-10-28 16:36:12 -0700620 <!-- Gyroscope -->
Brian Muramatsu729de482011-05-12 12:26:58 -0700621 <string name="snsr_gyro_test">Gyroscope Test</string>
622 <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>
623 <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string>
624 <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string>
625 <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>
626 <string name="snsr_gyro_test_degrees_title">Wrong units?</string>
627 <string name="snsr_gyro_test_degrees_message">These values looks like degrees per second. These should be radians per second!</string>
destradaa65c7cdb2013-10-28 16:36:12 -0700628 <string name="snsr_gyro_m_test">Gyroscope Measurement Test</string>
destradaa9732fb12014-08-15 10:40:50 -0700629 <string name="snsr_gyro_device_placement">Place the device in a flat surface with the screen
destradaa31f57432014-09-26 14:47:28 -0700630 facing the ceiling. Read the instructions for each scenario, before you perform the
631 test.</string>
destradaa9732fb12014-08-15 10:40:50 -0700632 <string name="snsr_gyro_device_static">Leave the device static.</string>
destradaa31f57432014-09-26 14:47:28 -0700633 <string name="snsr_gyro_rotate_device">Once you begin the test, you will need to rotate the
634 device 360deg (one time) in the direction show by the animation, then place it back on the
635 flat surface.</string>
destradaa65c7cdb2013-10-28 16:36:12 -0700636
Vinod Krishnan20d67252014-04-30 11:12:01 -0700637 <!-- Heart Rate -->
638 <string name="snsr_heartrate_test">Heart Rate Test</string>
Vinod Krishnan7b6bdeb2014-05-13 16:19:44 -0700639 <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 Krishnan20d67252014-04-30 11:12:01 -0700640 <string name="snsr_heartrate_test_no_heartrate_title">No heart rate monitor?</string>
641 <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>
642
destradaa65c7cdb2013-10-28 16:36:12 -0700643 <!-- Magnetic Field -->
644 <string name="snsr_mag_m_test">Magnetic Field Measurement Tests</string>
destradaa9732fb12014-08-15 10:40:50 -0700645 <string name="snsr_mag_verify_norm">Verifying the Norm...</string>
646 <string name="snsr_mag_verify_std_dev">Verifying the Standard Deviation...</string>
destradaa37286b42014-10-02 13:46:05 -0700647 <string name="snsr_mag_verify_calibrated_uncalibrated">Verifying the relationship between
648 calibrated and uncalibrated measurements...</string>
destradaa9732fb12014-08-15 10:40:50 -0700649 <string name="snsr_mag_calibration_description">Please calibrate the Magnetometer by moving
650 it in 8 shapes in different orientations.</string>
destradaa7bed8102014-09-24 13:18:16 -0700651 <string name="snsr_mag_calibration_complete">When done, leave the device in a flat surface, far
652 from all metallic objects (if the test does not pass, try re-running it outdoors).</string>
destradaa37286b42014-10-02 13:46:05 -0700653 <string name="snsr_mag_measurement">-&gt; (%1$.2f, %2$.2f, %3$.2f) : %4$.2f uT</string>
Brian Muramatsuaccc6842010-08-11 18:57:27 -0700654
Jim Steele0c4d08a2014-08-03 00:49:59 -0700655 <!-- Sensor Value Accuracy -->
Jim Steele0c4d08a2014-08-03 00:49:59 -0700656 <string name="snsr_rot_vec_test">Rotation Vector Accuracy Test</string>
destradaaa7714542014-09-04 16:23:03 -0700657 <string name="snsr_event_length">Sensor(%3$s). Event values expected to have size=%1$d. Found=%2$d.</string>
destradaaa7714542014-09-04 16:23:03 -0700658 <string name="snsr_event_value">Sensor(%3$s). Event value[0] expected to be of value=%1$f. Found=%2$f.</string>
659 <string name="snsr_event_time">Sensor(%5$s). Event timestamp expected to be synchronized with SystemClock.elapsedRealtimeNanos(). Event received at=%1$d. Event timestamp=%2$d. Delta=%3$d. Threshold=%4$d.</string>
Jim Steele0c4d08a2014-08-03 00:49:59 -0700660
661 <!-- Sensor Batching -->
662 <string name="snsr_batch_test">Sensor Batching Tests</string>
destradaa16203b42014-09-29 13:26:51 -0700663 <string name="snsr_batching_walking_needed">Once the test begins, you will have to take the
664 device in your hand and walk.</string>
Jim Steele0c4d08a2014-08-03 00:49:59 -0700665
666 <!-- Sensor Synchronization -->
667 <string name="snsr_synch_test">Sensor Synchronization Test</string>
668
Jim Steeleb292a9f2014-07-13 23:29:56 -0700669 <!-- Step Counter and Detector -->
670 <string name="snsr_step_counter_test">Step Counter and Detector Tests</string>
destradaa139500e2014-08-22 16:01:52 -0700671 <string name="snsr_step_counter_test_walking">Once the test begins, you will need to walk, and tap on the screen with each step you take.</string>
destradaaa7714542014-09-04 16:23:03 -0700672 <string name="snsr_step_counter_test_still">Once the test begins, you will need to remain still and hold the device still in your hand.</string>
destradaa139500e2014-08-22 16:01:52 -0700673 <string name="snsr_step_counter_expected_steps">At least %1$d steps are expected to be reported. Reported=%2$d.</string>
674 <string name="snsr_step_counter_detected_reported">Steps reported by user=%1$d. Steps counted=%2$d. Delta=%3$d. Tolerance=%4$d.</string>
675 <string name="snsr_step_detector_detected_reported">Steps reported by user=%1$d. Steps detected=%2$d. Delta=%3$d. Tolerance=%4$d.</string>
676 <string name="snsr_step_counter_event_changed">Step counter expected to increase monotonically, with a delta > 0. Found=%1$d. Timestamp=%2$d.</string>
677 <string name="snsr_step_reported">%1$d | User reported step.</string>
678 <string name="snsr_step_counter_event">%1$d | Step Counter event. count=%2$d.</string>
679 <string name="snsr_step_detector_event">%1$d | Step Detector event.</string>
Jim Steeleb292a9f2014-07-13 23:29:56 -0700680
Aravind Akelladbc95c52015-06-09 10:22:16 -0700681 <!-- Device suspend tests -->
682 <string name="snsr_device_suspend_test">Device Suspend Tests</string>
683 <string name="snsr_device_did_not_go_into_suspend">Device did not go into suspend mode during test execution </string>
684 <string name="snsr_batch_did_not_arrive_at_expected_time">Batch did not arrive at the expected time estimatedBatchArrivalMs=%1$d
685 firstEventReceivedMs=%2$d diffMs=%3$d toleranceMs=%4$d </string>
686 <string name="snsr_device_suspend_test_instr">One you begin the test, disconnect USB, turn off the display and allow
687 the device to go into suspend mode. The screen will turn on and a sound will be played once all the tests are completed.</string>
688
Jim Steelec57c8432014-05-24 09:53:32 -0700689 <!-- Significant Motion -->
690 <string name="snsr_significant_motion_test">Significant Motion Tests</string>
destradaaa7714542014-09-04 16:23:03 -0700691 <string name="snsr_significant_motion_event_arrival">Event expected to trigger. Triggered=%1$s.</string>
692 <string name="snsr_significant_motion_event_type">Event expected to be of type=%1$d. Found=%2$d.</string>
693 <string name="snsr_significant_motion_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string>
destradaaa07a7a22014-08-21 17:09:03 -0700694 <string name="snsr_significant_motion_disable_info">Significant Motion is expected to disable itself after it triggers once.</string>
695 <string name="snsr_significant_motion_test_trigger">Once you begin the test, you will need to walk for Significant Motion to be detected.</string>
696 <string name="snsr_significant_motion_test_cancel">Once you begin the test, you will need to walk to ensure Significant Motion is not reported after trigger canceled.</string>
697 <string name="snsr_significant_motion_test_vibration">Leave the device in a level surface. Once you begin the test, the device will vibrate to ensure that Significant Motion is not triggered.</string>
698 <string name="snsr_significant_motion_test_in_hand">Once you begin the test, hold the device in your hand while you perform natural hand movements.</string>
699 <string name="snsr_significant_motion_test_sitting">Once you begin the test, keep the device in your pocket and move naturally while sitting in a chair.</string>
700 <string name="snsr_significant_motion_test_deactivation">Once you begin the test, you will need to walk to ensure Significant Motion triggers only once.</string>
destradaa91553992014-09-19 17:50:15 -0700701 <string name="snsr_significant_motion_registration">Expected to be able to register for TriggerSensor. Found=%1$b.</string>
destradaaa07a7a22014-08-21 17:09:03 -0700702 <string name="snsr_significant_motion_cancelation">Expected to be able to cancel TriggerSensor. Found=%b.</string>
Aravind Akelladbc95c52015-06-09 10:22:16 -0700703 <string name="snsr_significant_motion_ap_suspend">One you begin the test, disconnect USB, turn off the display and allow the device to go into suspend.
704 You will need to walk to ensure that Significant Motion triggers. The screen will turn on and a sound will be played once the test completes.</string>
705 <string name="snsr_device_did_not_wake_up_at_trigger">Device did not wakeup at tigger time. wakeTime=%1$d ms triggerTime=%2$d ms</string>
Jim Steelec57c8432014-05-24 09:53:32 -0700706
destradaaa0b3bbc2014-09-03 14:08:00 -0700707 <!-- Strings for Sensor CTS tests inside CtsVerifier -->
708 <string name="snsr_single_sensor_tests">CTS Single Sensor Tests</string>
709 <string name="snsr_sensor_integration_tests">CTS Sensor Integration Tests</string>
710 <string name="snsr_sensor_test">CTS Sensor Test</string>
destradaa774c0152014-09-15 17:00:37 -0700711 <string name="snsr_sensor_batching_tests">CTS Sensor Batching Tests</string>
destradaaa0b3bbc2014-09-03 14:08:00 -0700712
Stuart Scottba898162014-01-17 13:18:14 -0800713 <!-- Strings for Sample Test Activities -->
714 <string name="share_button_text">Share</string>
715 <string name="sample_framework_test">Sample Framework Test</string>
716 <string name="sample_test">Sample Test</string>
717 <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>
718
Brian Muramatsuaccc6842010-08-11 18:57:27 -0700719 <!-- Strings for SuidFilesActivity -->
Brian Muramatsu14e1cbb2010-09-13 18:33:39 -0700720 <string name="suid_files">SUID File Scanner</string>
721 <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 Muramatsuac007372010-08-18 11:02:28 -0700722 <string name="scanning_directory">Scanning directory...</string>
Brian Muramatsu22330722010-08-13 14:48:36 -0700723 <string name="file_status">User: %1$s\nGroup: %2$s\nPermissions: %3$s\nPath: %4$s</string>
Brian Muramatsuaccc6842010-08-11 18:57:27 -0700724 <string name="no_file_status">Could not stat file...</string>
725 <string name="congratulations">Congratulations!</string>
726 <string name="no_suid_files">No unauthorized suid files detected!</string>
Brian Muramatsuf8946202010-11-09 13:43:39 -0800727
James Painterfa2e1662012-09-13 15:37:58 -0700728 <!-- Strings for Camera Orientation -->
729 <string name="camera_orientation">Camera Orientation</string>
James Painter6cdb8682012-10-02 08:22:39 -0700730 <string name="co_info">This test verifies the orientation capabilities of
731 camera preview and capture.\n - The left view shows a preview window rotated
732 clockwise by a given magnitude of degrees.\n - The right view, after taking
733 a photo, shows the captured image.\n - For each camera and orientation, both
734 the left and right views should appear rotated clockwise by the amount of
735 degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose
736 \"Fail\".\n - For front-facing cameras, the test will horizontally mirror
737 the captured image prior to rotation, in attempt to make the left and right
738 views appear the same.\n - The physical orientation of the device does not
739 matter.\n - Read the message above the \"Take Photo\" button for
740 step-by-step instructions.
James Painter738030a2012-09-26 00:31:30 -0700741 </string>
James Painterfa2e1662012-09-13 15:37:58 -0700742 <string name="co_preview_label">Camera preview</string>
743 <string name="co_format_label">Oriented photo</string>
744 <string name="co_camera_label">Camera:</string>
745 <string name="co_orientation_label">Orientation</string>
James Painter738030a2012-09-26 00:31:30 -0700746 <string name="co_orientation_direction_label">clockwise</string>
James Painterfa2e1662012-09-13 15:37:58 -0700747 <string name="co_instruction_heading_label">Instruction:</string>
748 <string name="co_instruction_text_photo_label">Take a photo</string>
James Painter6cdb8682012-10-02 08:22:39 -0700749 <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>
750 <string name="co_instruction_text_extra_label">(mirrored horizontally prior to rotation, since camera is front-facing)</string>
James Painterfa2e1662012-09-13 15:37:58 -0700751 <string name="co_photo_button_caption">Take Photo</string>
Eino-Ville Talvalae56ae2a2012-04-27 19:18:41 -0700752
Igor Murashkin48f86e72012-10-17 18:12:59 -0700753 <!-- Strings for Camera Intents -->
754 <string name="camera_intents">Camera Intents</string>
755 <string name="ci_info">
756 This test verifies that the default camera app is firing intents
757 after pictures/videos are taken. It also verifies that when the
758 default camera app is invoked via intents, the launch intents work,
759 and the broadcast intents are received when appropriate per the SDK
760 documentation.\n\n
761 - Read the message above the \"Start Test\" button for
762 step-by-step instructions.
763 </string>
764 <string name="ci_preview_label">Camera preview</string>
765 <string name="ci_format_label">Oriented photo</string>
766 <string name="ci_camera_label">Camera:</string>
767 <string name="ci_intents_label">Intents Test</string>
768 <string name="ci_intents_direction_label">clockwise</string>
769 <string name="ci_instruction_heading_label">Instructions:</string>
770 <string name="ci_instruction_text_photo_label">READ BEFORE STARTING TEST</string>
771 <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>
772 <string name="ci_instruction_text_app_picture_label">\n
773 1. Click Start Test. \n
774 2. Go to home screen (HOME key). \n
775 3. Launch Camera application. \n
776 4. Capture photo. \n
777 5. Return to CTS verifier app. \n
778 6. Pass button will light up if intent was received.\n
779 7. Click "Pass" if possible.
780 </string>
781 <string name="ci_instruction_text_app_video_label">\n
782 1. Click Start Test. \n
783 2. Go to home screen (HOME key). \n
784 3. Launch Camera application. \n
785 4. Capture video. \n
786 5. Return to CTS verifier app. \n
787 6. Pass button will light up if intent was received.\n
788 7. Click "Pass" if possible.
789 </string>
790 <string name="ci_instruction_text_intent_picture_label">\n
791 1. Click Start Test.\n
792 2. Camera app will launch, prompting to take photo.\n
793 3. Capture/confirm photo using camera app controls.\n
794 4. Pass button will light up if intent was NOT received.\n
795 5. Click "Pass" if possible.
796 </string>
797 <string name="ci_instruction_text_intent_video_label">\n
798 1. Click Start Test.\n
799 2. Camera app will launch, prompting to take video.\n
800 3. Capture/confirm video using camera app controls.\n
801 4. Pass button will light up if intent was received.\n
802 5. Click "Pass" if possible.
803 </string>
804 <string name="ci_start_test_button_caption">Start Test</string>
805
James Painterfa2e1662012-09-13 15:37:58 -0700806 <!-- Strings for Camera Formats -->
Eino-Ville Talvalae56ae2a2012-04-27 19:18:41 -0700807 <string name="camera_format">Camera Formats</string>
808 <string name="cf_info">This test checks that all the supported
809 output formats for camera preview callbacks work correctly, and
810 that the mandatory formats are available. \n - The left view shows
811 a standard preview window. \n - The right view shows the output
812 processed from camera preview callbacks. \n - For each camera,
813 resolution, and format combination in the dropdowns, the right
814 view should look the same as the left, and neither should have
815 streaks, lines, or other artifacts. \n - For front-facing cameras,
816 the right view must be horizontally mirrored relative to the left
817 view.\n - Note that the frame rate of the right view may be much
818 lower than on the left; this is not an indication of a failed
819 test.
820 </string>
821 <string name="cf_preview_label">Normal preview</string>
822 <string name="cf_format_label">Processed callback data</string>
823
Jianing Wei636f9032013-10-03 10:00:25 -0700824 <!-- Strings for Camera Video -->
825 <string name="record_button_text">Test</string>
826 <string name="camera_video">Camera Video</string>
827 <string name="video_info"> This test checks video capture
828 at different resolutions. \n - The left view window shows the preview.
829 \n - Pressing the test button will trigger three
830 seconds of video recording. Playback will show up in the right view
831 window after recording is complete. \n - Use the spinners to choose
832 camera and resolution combinations. The playback should be similar
833 to what you saw in preview. \n - After all possible combinations
834 are tested, the pass button will be enabled. You may press the pass
835 button to indicate a pass. \n - You may press fail button any time during
836 the test to indicate failure.
837 </string>
838 <string name="video_capture_label">Video capture</string>
839 <string name="video_playback_label">Video playback</string>
840 <string name="dialog_fail_test">Test failed</string>
841 <string name="fail_quit">Fail and quit</string>
842 <string name="cancel">Cancel</string>
843 <string name="status_ready">Ready</string>
844 <string name="status_recording">Recording</string>
845 <string name="status_playback">Playing back</string>
846
Brian Muramatsu12c86912011-07-21 17:26:46 -0700847 <!-- Strings for USB accessory test activity -->
848 <string name="usb_accessory_test">USB Accessory Test</string>
John Rusnakddf82c12014-08-04 15:49:51 -0700849 <string name="sensor_power_test">Sensor Power Test</string>
Brian Muramatsu12c86912011-07-21 17:26:46 -0700850 <string name="usb_accessory_test_info">
destradaa65c7cdb2013-10-28 16:36:12 -0700851 1. Connect your Android device to a computer and run the \'cts-usb-accessory\' program
Brian Muramatsudd2bf712011-08-12 12:46:07 -0700852 included with the CTS Verifier bundle.
Brian Muramatsu12c86912011-07-21 17:26:46 -0700853 \n\n2. If you have not started the CTS Verifier, press \'OK\' when asked to open the CTS
854 Verifier when the accessory is connected. \n\nIf you are already in this test,
855 then you can press \'Cancel\' but press \'OK\' in the next dialog asking whether to allow
856 CTS Verifier to access the accessory.
857 \n\n3. You should see the accessory and the CTS Verifier display a series of messages
858 which indicates that the accessory support is working properly.
859 </string>
860 <string name="usb_not_available_title">USB accessory feature is not available?</string>
861 <string name="usb_not_available_message">If your device is supposed to support USB accessories, your API implementation is not behaving correctly!</string>
862 <string name="usb_received_messages">Received Messages</string>
863 <string name="usb_sent_messages">Sent Messages</string>
864 <string name="usb_no_messages">No messages</string>
865 <string name="usb_message_thread_started">Starting message processing...</string>
866 <string name="usb_message_thread_exception">Exception occurred while processing a message...</string>
867 <string name="usb_message_thread_ended">Stopping message processing...</string>
868 <string name="usb_test_passed">Received all expected messages. Pass button enabled!</string>
869 <string name="usb_file_descriptor_error">Could not open file descriptor for USB accessory... try reconnecting and restarting the accessory?</string>
870
Ruben Brunk370e2432014-10-14 18:33:23 -0700871 <!-- Strings for the Camera ITS test activity -->
872 <string name="camera_its_test">Camera ITS Test</string>
873 <string name="camera_its_test_info">
874 1. Connect your Android device to a computer with adb installed via a USB cable.
875 \n\n2. Setup the CameraITS test environment by following the setup instructions in the
876 README file found in the CameraITS directory included in the CTS Verifier bundle
877 (cd CameraITS; source build/envsetup.sh;).
878 \n\n3. Setup the test scene described in the CameraITS README file, and aim the camera
879 at it.
Yin-Chia Yeha2277d02014-10-20 15:50:23 -0700880 \n\n4. Run the full ITS test suite on all possible camera Ids.
Yin-Chia Yehab98ada2015-03-05 13:28:53 -0800881 (cd CameraITS; python tools/run_all_tests.py). Once all
Ruben Brunk370e2432014-10-14 18:33:23 -0700882 of the tests have been run, the \'PASS\' button will be enabled if all of the tests have
883 succeeded. Please note that these tests can take 20+ minutes to run.
884 </string>
885 <string name="no_camera_manager">
886 No camera manager exists! This test device is in a bad state.
887 </string>
888 <string name="all_legacy_devices">
Yin-Chia Yehfc60c4c2015-04-08 16:59:42 -0700889 All cameras on this device are LEGACY mode only - ITS tests are only required on LIMITED
890 or better devices. Pass.
Ruben Brunk370e2432014-10-14 18:33:23 -0700891 </string>
892 <string name="its_test_passed">All Camera ITS tests passed. Pass button enabled!</string>
893 <string name="its_test_failed">Some Camera ITS tests failed.</string>
894
Chien-Yu Chen3e5b7202015-03-05 11:09:56 -0800895 <!-- Strings for the Camera Flashlight test activity -->
896 <string name="camera_flashlight_test">Camera Flashlight</string>
897 <string name="camera_flashlight_info">
898 This test checks the flashlight functionality. It will turn on and off the flashlight of
899 each camera device that has a flash unit. Follow the instructions on screen and observe the
900 flashlight status changing.
901 </string>
902 <string name="camera_flashlight_start_button">Start</string>
903 <string name="camera_flashlight_next_button">Next</string>
904 <string name="camera_flashlight_done_button">Done</string>
905 <string name="camera_flashlight_on_button">On</string>
906 <string name="camera_flashlight_off_button">Off</string>
907 <string name="camera_flashlight_start_text">Press Start to start flashlight test.</string>
908 <string name="camera_flashlight_question_text">Is Camera %1$s flashlight on or off?</string>
909 <string name="camera_flashlight_next_text">Ok. Press next.</string>
910 <string name="camera_flashlight_failed_text">Test failed. Press Done or Fail button.</string>
911 <string name="camera_flashlight_passed_text">All tests passed. Press Done or Pass button.
912 </string>
913
Jeff Davidson112f2792011-08-22 09:46:46 -0700914 <!-- Strings for StreamingVideoActivity -->
915 <string name="streaming_video">Streaming Video Quality Verifier</string>
916 <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>
917 <string name="sv_no_data">No videos.</string>
918 <string name="sv_failed_title">Test Failed</string>
919 <string name="sv_failed_message">Unable to play stream. See log for details.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +0900920
921 <!-- Strings for P2pTestActivity -->
922 <string name="p2p_test">Wi-Fi Direct Test</string>
923 <string name="p2p_test_info">
924 The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange
925 messages. One device must be the candidate device running the software build to
926 be tested, while the other device must be an implementation already known to be
927 compatible.\n\nOne device should start the requester test, and the other should
928 start the responder test. Your device must pass both requester and responder
929 tests.
930 </string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +0900931 <string name="p2p_group_formation">Group Formation</string>
932 <string name="p2p_join">Group Join</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +0900933 <string name="p2p_service_discovery">Service Discovery</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +0900934
935 <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string>
936 <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string>
937 <string name="p2p_group_owner_test">Group Owner Test</string>
938 <string name="p2p_group_client_test">Group Client Test</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +0900939 <string name="p2p_service_discovery_responder_test">
940 Service Discovery Responder Test</string>
941 <string name="p2p_service_discovery_requester_test">
942 Service Discovery Requester Test</string>
943
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +0900944 <string name="p2p_go_neg_responder">GO Negotiation Responder</string>
945 <string name="p2p_go_neg_requester">GO Negotiation Requester</string>
946 <string name="p2p_accept_client">Group Owner</string>
947 <string name="p2p_join_go">Group Client</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +0900948 <string name="p2p_service_discovery_responder">Service Discovery Responder</string>
949 <string name="p2p_service_discovery_requester">Service Discovery Requester</string>
950
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +0900951 <string name="p2p_go_neg_responder_info">
952 Start the \"GO Negotiation Requester Test\" on the other device and follow
953 the instructions.</string>
954 <string name="p2p_accept_client_info">
955 Start the \"Group Client Test\" on the other device and follow
956 the instructions.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +0900957 <string name="p2p_service_discovery_responder_info">
958 Start the \"Service Discovery Requester Test\" on the other device and follow
959 the instructions.</string>
960
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +0900961 <string name="p2p_go_neg_requester_info">
962 Start the \"GO Negotiation Responder Test\" on the other device.
963 Then run each test individually by clicking on it\'s name.</string>
964 <string name="p2p_join_go_info">
965 Start the \"Group Owner Test\" on the other device.
966 Then run each test individually by clicking on it\'s name.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +0900967 <string name="p2p_service_discovery_requester_info">
968 Start the \"Service Discovery Responder Test\" on the other device.
969 Then run each test individually by clicking on it\'s name.</string>
970
971 <string name="p2p_not_enabled">Wi-Fi is not enabled</string>
972 <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled.
973 Click the button below to go to system settings and enable Wi-Fi.</string>
974 <string name="p2p_settings">Wi-Fi Direct Settings</string>
975
976 <string name="p2p_result_success">Test passed successfully.</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +0900977
978 <string name="p2p_go_neg_responder_ready">
979 The go negotiation responder is now ready to start. Start
980 the \"GO Negotiation Requester Test\" on the other device.
981 Keep the screen here until all tests on the other device are
982 finished.</string>
983 <string name="p2p_go_ready">
984 The group owner is now ready to start. Start the \"Join
985 Group Test\" on the other device.
986 Keep the screen here until all tests on the other device are
987 finished.</string>
988 <string name="p2p_service_responder_ready">
989 The service responder is now ready to start. Start the
990 \"Service Discovery Requester Test\" on the other device.
991 Keep the screen here until all tests on the other device are
992 finished.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +0900993
994 <string name="p2p_setup_error">
995 Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string>
996 <string name="p2p_unexpected_error">
997 Test failed.\n\nUnexpected error. Check logcat.</string>
998 <string name="p2p_add_local_service_error">
999 Test failed.\n\nFailed to add local service.</string>
1000 <string name="p2p_add_service_request_error">
1001 Test failed.\n\nFailed to add service request.</string>
1002 <string name="p2p_remove_service_request_error">
1003 Test failed.\n\nFailed to remove service request.</string>
1004 <string name="p2p_clear_service_requests_error">
1005 Test failed.\n\nFailed to clear service requests.</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001006 <string name="p2p_connect_error">
1007 Test failed.\n\nFailed to start a p2p connection to the target device.</string>
1008 <string name="p2p_remove_group_error">
1009 Test failed.\n\nFailed to remove a p2p group.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001010 <string name="p2p_discover_peers_error">
1011 Test failed.\n\nFailed to discover peers.</string>
1012 <string name="p2p_discover_services_error">
1013 Test failed.\n\nFailed to discover services.</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001014 <string name="p2p_ceate_group_error">
1015 Test failed.\n\nFailed to start up group owner.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001016 <string name="p2p_no_service_requests_error">
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001017 Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001018 <string name="p2p_receive_invalid_response_error">
1019 Test failed.\n\nReceived an invalid message or could not receive
1020 the expected message.\n\n</string>
1021 <string name="p2p_target_not_found_error">Test failed.\n\n
1022 The target responder device was NOT found. Start up the responder
1023 test on the other device, then run the test again.</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001024 <string name="p2p_target_invalid_role_error">Test failed.\n\n
1025 The target responder must be p2p device. However, the target responder
1026 device was group owner. Check the test case on the other device.</string>
1027 <string name="p2p_target_invalid_role_error2">Test failed.\n\n
1028 The target responder must be group owner. However, the target responder
1029 device was p2p device. Check the test case on the other device.</string>
1030 <string name="p2p_connection_error">
1031 Test failed.\n\nFailed to establish a p2p connection.</string>
1032 <string name="p2p_detect_disconnection_error">
1033 Test failed.\n\nFailed to detect client disconnection.</string>
1034 <string name="p2p_disconnect_error">
1035 Test failed.\n\nFailed to disconnect a p2p connection.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001036
1037 <string name="p2p_search_target">Search Target</string>
1038 <string name="p2p_searching_target">Searching for target device ...</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001039 <string name="p2p_checking_serv_capab">Checking the service discovery
1040 capability ...</string>
1041 <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n
1042 Click the \"OK\" button on the other device to accept the connection
1043 request from this device.</string>
1044 <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n
1045 Enter the pin number on the other device.</string>
1046 <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to
1047 connect ...</string>
1048 <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer
1049 to disconnect ...</string>
Angus Konga0216882013-03-06 17:51:11 -08001050
1051 <string name="camera_fov_calibration">Camera FOV Calibration</string>
1052 <string name="camera_fov_calibration_done">Done</string>
1053 <string name="camera_fov_general_settings">General settings</string>
1054 <string name="camera_fov_label_options">Settings</string>
1055 <string name="camera_fov_tap_to_take_photo">Tap to calibrate</string>
1056 <string name="camera_fov_marker_distance">Marker distance (in cm)</string>
1057 <string name="camera_fov_marker_distance_description">The distance in centimeters between
1058 the solid lines on the target pattern.</string>
1059 <string name="camera_fov_target_distance">Target distance (in cm)</string>
1060 <string name="camera_fov_target_distance_description">The distance in centimeters from the
1061 device to the target pattern.</string>
1062 <string name="camera_fov_settings_button_text">Setup</string>
Sascha Haeberling28cb27c2013-05-03 18:19:07 -07001063 <string name="camera_fov_change_preview_sizes_button_text">Preview Sizes</string>
1064 <string name="camera_fov_choose_preview_size_for_camera">Choose preview size for camera %1$s</string>
Angus Konga0216882013-03-06 17:51:11 -08001065 <string name="camera_fov_displayed_fov_label">Displayed FOV : </string>
1066 <string name="camera_fov_reported_fov_label">Reported FOV : </string>
Sascha Haeberling117c60c2013-06-11 13:26:42 -07001067 <string name="camera_fov_reported_fov_problem">Reported FOV problem</string>
1068 <string name="camera_fov_reported_fov_problem_message">The reported FOV before takePicture() is
1069 different from when onPictureTaken() is called.\nAs picture size has not been changed, the
1070 reported FOV should be identical at both times.\n\nFOV before/after: %1$f / %2$f</string>
1071
Angus Konga0216882013-03-06 17:51:11 -08001072 <string name="camera_fov_panorama_wallpaper_title">Photo Sphere Live Wallpaper</string>
1073 <string name="camera_fov_panorama_wallpaper_description">This live wallapper displays photo
1074 spheres.</string>
1075 <string name="camera_fov_select_panorama">Select panorama</string>
1076 <string name="camera_fov_select_panorama_description">Select a panorama to display in the
1077 live wallpaper.</string>
1078 <string name="camera_fov_reset_panorama">Reset panorama</string>
1079 <string name="camera_fov_reset_panorama_description">Resets the panorama to show the demo
1080 file.</string>
1081 <string name="camera_fov_enable_compass_mode">Enable compass mode</string>
1082 <string name="camera_fov_enable_compass_mode_description">If enabled, the panorama orients
1083 itself according to the current rotation of the device.</string>
1084
Chris Wrenf102e542013-04-30 17:52:57 -04001085 <string name="test_category_notifications">Notifications</string>
Chris Wrenf9509802014-11-18 17:42:36 -05001086 <string name="package_priority_test">Notification Package Priority Test</string>
1087 <string name="package_priority_info">This test checks that the NotificationManagerService respects
1088 user preferences about relative package priorities.
1089 </string>
Chris Wren7b75fe22015-01-13 09:54:34 -05001090 <string name="package_priority_bot">Verifying that the CTS Robot helper package is installed.</string>
Chris Wrenf9509802014-11-18 17:42:36 -05001091 <string name="package_priority_high">Find \"%s\" under \"App notifications\" in the \"Sound &amp; notifications\" settings panel, and mark it as having notification priority.</string>
1092 <string name="package_priority_default">Find \"%s\" under \"App notifications\" in the \"Sound &amp; notifications\" settings panel, and make sure it has default priority.</string>
1093 <string name="package_priority_user_order">Check that ranker respects user priorities.</string>
1094
Chris Wrenbcdef182014-09-22 17:56:38 -04001095 <string name="attention_test">Notification Attention Management Test</string>
1096 <string name="attention_info">This test checks that the NotificationManagerService is
1097 respecting user preferences about notification ranking and filtering.
1098 </string>
1099 <string name="attention_ready">I\'m done</string>
Chris Wrend12fd342015-08-03 17:16:36 -04001100 <string name="attention_filter_all">Please disable \"Do not disturb\" by tapping the Quick Settings tile.</string>
1101 <string name="attention_filter_priority">Please select \"Priority only\" in the dialog that appears
1102 when you tap the \"Do not disturb\" tile in Quick Settings, and customize the setting to allow messages from
1103 starred contacts only by tapping "More settings".</string>
1104 <string name="attention_filter_none">Please select \"Total silence\" in the dialog that appears
1105 when you tap the \"Do not disturb\" tile in Quick Settings.</string>
Chris Wrenbcdef182014-09-22 17:56:38 -04001106 <string name="attention_create_contacts">Create contacts for notification annotations.</string>
1107 <string name="attention_delete_contacts">Delete test contacts.</string>
1108 <string name="attention_default_order">Check that ranker defaults to time order.</string>
1109 <string name="attention_priority_order">Check that ranker respects developers priorities.</string>
1110 <string name="attention_ambient_bit">Check that the ambient bit is set appropriately.</string>
1111 <string name="attention_lookup_order">Check that ranker respects Lookup URIs for contacts.</string>
1112 <string name="attention_email_order">Check that ranker respects mailto URIs for contacts.</string>
1113 <string name="attention_phone_order">Check that ranker respects telephone URIs for contacts.</string>
1114 <string name="attention_interruption_order">Check that ranker temporarily boosts interruptions.
1115 This test takes 15 seconds to complete.</string>
1116 <string name="attention_none_are_filtered">Check that \"All\" mode doesn\'t filter any notifications.</string>
1117 <string name="attention_some_are_filtered">Check that \"Priority\" mode doesn\'t filter priority notifications.</string>
1118 <string name="attention_all_are_filtered">Check that \"None\" mode filters all notifications.</string>
Chris Wrenf102e542013-04-30 17:52:57 -04001119 <string name="nls_test">Notification Listener Test</string>
1120 <string name="nls_service_name">Notification Listener for CTS Verifier</string>
1121 <string name="nls_info">This test checks that a NotificationListenerService can be enabled
Chris Wrenbcdef182014-09-22 17:56:38 -04001122 and disabled, and that once enabled the service is able to receive notifications and
Chris Wrenf102e542013-04-30 17:52:57 -04001123 dismiss them.
1124 </string>
destradaa65c7cdb2013-10-28 16:36:12 -07001125 <string name="nls_enable_service">Please enable \"Notification Listener for CTS Verifier\"
Chris Wrenf102e542013-04-30 17:52:57 -04001126 under Security > Notification Access and return here.</string>
destradaa65c7cdb2013-10-28 16:36:12 -07001127 <string name="nls_disable_service">Please disable \"Notification Listener for CTS Verifier\"
Chris Wrenf102e542013-04-30 17:52:57 -04001128 under Security > Notification Access and return here.</string>
1129 <string name="nls_start_settings">Launch Settings</string>
1130 <string name="nls_service_started">Service should start once enabled.</string>
1131 <string name="nls_note_received">Check that notification was received.</string>
1132 <string name="nls_payload_intact">Check that notification payload was intact.</string>
1133 <string name="nls_clear_one">Check that service can clear a notification.</string>
1134 <string name="nls_clear_all">Check that service can clear all notifications.</string>
1135 <string name="nls_service_stopped">Service should stop once disabled.</string>
1136 <string name="nls_note_missed">Check that notification was not received.</string>
destradaa65c7cdb2013-10-28 16:36:12 -07001137
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001138 <string name="location_mode_high_accuracy_test">High Accuracy Mode Test</string>
1139 <string name="location_mode_high_accuracy_info">
1140 This test checks that the Location Mode API is consistent with the
1141 Location Provider API when the device is in High Accuracy location mode.
1142 </string>
1143 <string name="location_mode_select_high_accuracy">
Tom O'Neill45599512015-04-23 10:19:06 -07001144 Please select the \"High accuracy\" mode at Settings > Location
1145 (hint: tap the "Mode" item) and return here.
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001146 </string>
1147 <string name="location_mode_battery_saving_test">Battery Saving Mode Test</string>
1148 <string name="location_mode_battery_saving_info">
1149 This test checks that the Location Mode API is consistent with the
1150 Location Provider API when the device is in Battery Saving location mode.
1151 </string>
1152 <string name="location_mode_select_battery_saving">
Tom O'Neill45599512015-04-23 10:19:06 -07001153 Please select the \"Battery Saving\" mode at Settings > Location
1154 (hint: tap the "Mode" item) and return here.
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001155 </string>
Tom O'Neill9e56d272013-12-16 12:48:30 -08001156 <string name="location_mode_device_only_test">Device Only Mode Test</string>
1157 <string name="location_mode_device_only_info">
1158 This test checks that the Location Mode API is consistent with the
1159 Location Provider API when the device is in Device Only location mode.
1160 </string>
1161 <string name="location_mode_select_device_only">
1162 Please select the \"Device Only\" mode at
Tom O'Neill45599512015-04-23 10:19:06 -07001163 Settings > Location (hint: tap the "Mode" item) and return here.
Tom O'Neill9e56d272013-12-16 12:48:30 -08001164 </string>
1165 <string name="location_mode_off_test">Location Mode Off Test</string>
1166 <string name="location_mode_off_info">
1167 This test checks that the Location Mode API is consistent with the
1168 Location Provider API when the device is in the Off location mode.
1169 </string>
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001170
1171 <string name="location_mode_start_settings">Launch Settings</string>
1172 <string name="location_mode_turn_on">
Tom O'Neill9e56d272013-12-16 12:48:30 -08001173 Please turn ON location access (the switch at the top of Settings > Location)
1174 and return here.
1175 </string>
1176 <string name="location_mode_turn_off">
1177 Please turn OFF location access (the switch at the top of Settings > Location)
1178 and return here.
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001179 </string>
1180 <string name="location_mode_secure_gps_on">GPS provider should be ON in secure settings.</string>
1181 <string name="location_mode_secure_gps_off">GPS provider should be OFF in secure settings.</string>
1182 <string name="location_mode_secure_nlp_on">Network location provider should be ON in secure settings.</string>
1183 <string name="location_mode_secure_nlp_off">Network location provider should be OFF in secure settings.</string>
1184 <string name="location_mode_manager_gps_on">GPS provider should be ON in LocationManager.</string>
1185 <string name="location_mode_manager_gps_off">GPS provider should be OFF in LocationManager.</string>
1186 <string name="location_mode_manager_nlp_on">Network location provider should be ON in LocationManager.</string>
1187 <string name="location_mode_manager_nlp_off">Network location provider should be OFF in LocationManager.</string>
1188
Maggie Benthall3278c022013-10-04 18:50:51 -04001189 <string name="cacert_test">CA Cert Notification Test</string>
1190 <string name="cacert_info">This test checks that when a CA Certificate is installed, the user is notified.</string>
1191 <string name="cacert_do_something">Do it</string>
1192 <string name="cacert_done">Done</string>
1193 <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>
1194 <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>
1195 <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>
1196 <string name="cacert_dismiss_notification">Dismiss the notification. If it cannot be dismissed, fail the test.</string>
1197
1198 <string name="caboot_test">CA Cert Notification on Boot test</string>
1199 <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>
1200 <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>
1201 <string name="caboot_check_creds">Check Credentials</string>
1202 <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>
1203 <string name="caboot_install_cert">Install credential</string>
1204 <string name="caboot_reboot_desc">Please reboot the device and return to this test.</string>
1205 <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>
1206
Robin Leeb4be0a92015-06-15 19:13:00 -07001207 <!-- Strings for KeyChain -->
1208 <string name="keychain_test">KeyChain Storage Test</string>
1209 <string name="keychain_info">This test checks that credentials installed to the system can be granted, retrieved, and used to create valid HTTPS connections.</string>
1210 <string name="keychain_reset">Reset</string>
1211 <string name="keychain_skip">Skip</string>
1212 <string name="keychain_setup_desc">The first step sets up an internal KeyStore and generates credentials to use for the remainder of the test.\n\n
1213 Touch \'Next\' to begin.</string>
1214 <string name="keychain_install_desc">Credentials generated. Touch \'Next\' to install them to the system keychain.\n\n
1215The container for the credentials will not be protected with a password; if prompted for one, leave that field blank.\n\n
1216During installation you may be prompted for a name - accept the default suggestion.\n\n
1217In the case that these credentials were already installed, you may skip this step.</string>
1218 <string name="keychain_https_desc">The last test involves setting up an HTTPS connection using credentials from the KeyChain.\n\n
1219You should be prompted to select credentials; choose the ones you just installed in the previous step.</string>
1220 <string name="keychain_reset_desc">Before marking this test as passed, touch \'Next\' to open security settings and reset the following items:\n
1221 1. Clear device credentials.\n
1222 2. Change the lock screen type to \'None\'.</string>
1223
Adam Cohen8ae96702013-05-17 14:21:23 -07001224 <!-- Strings for Widget -->
1225 <string name="widget_framework_test">Widget Framework Test</string>
1226 <string name="widget_framework_test_info">This test checks some basic features of the widget
1227 framework. In order to perform the test, press the Home button. Add the widget
1228 titled "CTS Verifier" to the home screen. Follow the instructions in the widget.</string>
1229 <string name="widget_name">Widget Framework Test</string>
1230 <string name="widget_pass">Pass</string>
1231 <string name="widget_fail">Fail</string>
Alon Albert4106ff12013-10-01 12:36:02 -07001232
Robin Lee020f1852015-01-15 11:56:05 +00001233 <string name="provisioning_byod_nonmarket_allow">Enable non-market apps</string>
1234 <string name="provisioning_byod_nonmarket_allow_info">
1235 This test verifies that non-market apps can be installed if permitted.\n
1236 1. A package installation UI should appear.\n
1237 2. Accept the package and verify that it installs.
1238 </string>
1239
1240 <string name="provisioning_byod_nonmarket_deny">Disable non-market apps</string>
1241 <string name="provisioning_byod_nonmarket_deny_info">
1242 This test verifies that non-market apps cannot be installed unless permitted.\n
1243 1. A package installation UI should appear.\n
1244 2. Verify that the installation of the package is refused.
1245 </string>
1246
Sander Alewijnse7e24fda2015-03-26 17:41:57 +00001247 <string name="provisioning_byod_capture_image_support">Camera support cross profile image capture</string>
1248 <string name="provisioning_byod_capture_image_support_info">
1249 This test verifies that images can be captured from the managed profile using the primary profile camera.\n
1250 1. Capture a picture using the camera.\n
1251 2. Verify that the captured picture is shown.\n
1252 3. Click on the close button.
1253 </string>
1254 <string name="provisioning_byod_capture_video_support">Camera support cross profile video capture</string>
1255 <string name="provisioning_byod_capture_video_support_info">
1256 This test verifies that videos can be captured from the managed profile using the primary profile camera.\n
1257 1. Capture a video using the camera.\n
1258 2. Click on the play button.\n
1259 3. Verify that the captured video is played.\n
1260 4. Click on the close button.
1261 </string>
1262 <string name="provisioning_byod_capture_audio_support">Sound recorder support cross profile audio capture</string>
1263 <string name="provisioning_byod_capture_audio_support_info">
1264 This test verifies that audio can be captured from the managed profile using the primary profile sound recorder.\n
1265 1. Capture audio.\n
1266 2. Click on the play button.\n
1267 3. Verify that the captured audio is played.\n
1268 4. Click on the close button.\n
1269 </string>
1270 <string name="provisioning_byod_dismiss_result_dialog">Close</string>
1271 <string name="provisioning_byod_play">Play</string>
1272 <string name="provisioning_byod_verify_image_title">Verify captured image</string>
1273 <string name="provisioning_byod_verify_video_title">Verify captured video</string>
1274 <string name="provisioning_byod_verify_audio_title">Verify captured audio</string>
1275 <string name="provisioning_byod_no_image_capture_resolver">No image capture app present. Skip test.</string>
1276 <string name="provisioning_byod_no_video_capture_resolver">No video capture app present. Skip test.</string>
1277 <string name="provisioning_byod_no_audio_capture_resolver">No audio capture app present. Skip test.</string>
1278 <string name="provisioning_byod_capture_media_error">Error while capturing media from managed profile.</string>
1279
Alon Albert4106ff12013-10-01 12:36:02 -07001280 <!-- Strings for DeskClock -->
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001281 <string name="deskclock_tests">Alarms and Timers Tests</string>
Alon Albert4106ff12013-10-01 12:36:02 -07001282 <string name="deskclock_tests_info">
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001283 The Alarms and Timers tests verify that the Clock app implements the AlarmClock API properly.
Alon Albert4106ff12013-10-01 12:36:02 -07001284 </string>
1285 <string name="deskclock_group_alarms">Alarms</string>
1286 <string name="deskclock_group_timers">Timers</string>
1287
1288 <string name="dc_show_alarms_test">Show Alarms Test</string>
1289 <string name="dc_show_alarms_test_info">
1290 This test verifies that the SHOW_ALARMS API works.\n
1291 1. Press the "Show Alarms" button.\n
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001292 2. Verify that a UI of the clock app is launched and displays the list of alarms\n
Alon Albert4106ff12013-10-01 12:36:02 -07001293 </string>
1294 <string name="dc_show_alarms_button">Show Alarms</string>
1295
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001296 <string name="dc_set_alarm_with_ui_test">Set Alarm Test</string>
1297 <string name="dc_set_alarm_with_ui_test_info">
1298 This test verifies that the ACTION_SET_ALARM with no parameters API works.\n
1299 1. Press the "Set Alarm" button.\n
1300 2. Verify that the clock app is launched and displays a UI to manage alarms.\n
1301 </string>
1302 <string name="dc_set_alarm_button">Set Alarm</string>
1303 <string name="dc_set_alarm_verify_button">Verify</string>
Alon Albert4106ff12013-10-01 12:36:02 -07001304
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001305 <string name="dc_start_alarm_test">Start Alarm Test</string>
1306 <string name="dc_start_alarm_test_info">
1307 This test verifies that the ACTION_SET_ALARM API actually starts an alarm.\n
1308 1. Press the "Start Alarm" button.\n
1309 2. Make sure the alarms UI is NOT shown\n
1310 3. Wait for the alarm to fire (may take up to 2 minutes)\n
1311 4. Verify that the alarm title is: "Start Alarm Test",\n
1312 the alarm is silent and vibrating (if the device supports vibrate).\n
1313 5. Dismiss the alarm.\n
1314 6. Verify that the alarm is not in the Clock\'s alarms list. The Verify button opens
1315 the alarm view.\n
1316 </string>
1317 <string name="dc_start_alarm_button">Start Alarm</string>
1318
1319 <string name="dc_full_alarm_test">Full Alarm Test</string>
1320 <string name="dc_full_alarm_test_info">
1321 This test verifies that the ACTION_SET_ALARM API supports all extras.\n
1322 1. Press the "Create Alarm" button.\n
1323 2. Verify that you see one alarm with the following information:\n
1324 Name of alarm: Create Alarm Test. \n
1325 Vibrate: on.\n
1326 Ringtone: silent.\n
1327 Time: 01:23. \n
1328 Repeating on: Monday and Wednesday. \n
1329 </string>
1330 <string name="dc_full_alarm_button">Create Alarm</string>
destradaa65c7cdb2013-10-28 16:36:12 -07001331
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001332 <string name="dc_set_timer_with_ui_test">Set Timer Test</string>
1333 <string name="dc_set_timer_with_ui_test_info">
1334 This test verifies that the ACTION_SET_TIMER API with no paramters open the UI\n
1335 1. Press the "Set Timer" button.\n
1336 2. Verify that the an app is launched and displays a UI to manage timers.\n
1337 </string>
1338 <string name="dc_set_timer_with_ui_button">Set Timer</string>
1339
1340 <string name="dc_start_timer_test">Start Timer Test</string>
1341 <string name="dc_start_timer_test_info">
1342 This test verifies that the ACTION_SET_TIMER API actually starts a timer\n
1343 1. Press the "Start Timer" button.\n
1344 2. Verify that a timer is started and NO timers UI is shown.\n
1345 3. Verify that the timer named "Start Timer Test" rings after 30 seconds. Dismiss it.\n
1346 4. Verify that the timer is deleted after the dismissal.\n
1347 </string>
1348 <string name="dc_start_timer_button">Start Timer</string>
1349
1350 <string name="dc_start_timer_with_ui_test">Start Timer With UI Test</string>
1351 <string name="dc_start_timer_with_ui_test_info">
1352 This test verifies that the ACTION_SET_TIMER API actually starts a timer with UI\n
1353 1. Press the "Start Timer" button.\n
1354 2. Verify that a timer is started and the timers UI is shown with a timer named "Start Timer Test".\n
1355 3. Verify that the timer rings after 30 seconds.\n
1356 </string>
Amith Yamasani0e2d6d92014-02-19 10:13:23 -08001357 <!-- Strings for LockConfirmBypassTest -->
1358 <string name="lock_confirm_test_title">Keyguard Password Verification</string>
1359 <string name="lock_set_button_text">Set password</string>
1360 <string name="lock_change_button_text">Change password</string>
1361 <string name="lock_confirm_message">
1362 This test verifies that the user is prompted for the current keyguard password before prompting for a new password.\n
1363 \nClick the \"Set password\" button if you currently don\'t have a password set.\n
1364 \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.
1365 </string>
1366
Harsh Modife5933d2014-08-12 16:52:16 -07001367 <!-- String for Projection Tests -->
1368 <string name="test_category_projection">Projection Tests</string>
1369 <string name="projection_service_name">Projection Service</string>
1370 <string name="pca_info">This tests whether or not OpenGL projection works.\n
1371 You should see two "tumbling cubes." Tapping the screen should case the cubes to explode.</string>
1372 <string name="pca_test">Projection Cube Test</string>
1373 <string name="pwa_info">This tests whether or displaying widets and keyfocus navigation works.\n
1374 You should see four buttons on the bottom of the screen.\n
1375 Pressing the "up" and "down" buttons should highlight different buttons.\n
Takayuki Hoshi58ede6c2014-10-14 13:33:04 +09001376 Further, you should also be able to touch them and they should highlight as usual.</string>
Harsh Modife5933d2014-08-12 16:52:16 -07001377 <string name="pwa_test">Projection Widget Test</string>
1378 <string name="pwa_button_up">Up</string>
1379 <string name="pwa_button_down">Down</string>
1380 <string name="pwa_button_left">Left</string>
1381 <string name="pwa_button_right">Right</string>
1382 <string name="pwa_button">Button</string>
1383 <string name="pla_test">Projection Scrolling List Test</string>
1384 <string name="pla_info">This tests whether a projected list view will scroll properly\n
1385 You should see 50 list items and be able to scroll up and down the list</string>
1386 <string name="pva_test">Projection Video Playback Test</string>
1387 <string name="pva_info">This tests whether video playback works when projected.\n
1388 You should see a blinking white box and here a beep that is synchronized with each blink</string>
1389 <string name="pta_test">Projection Multitouch Test</string>
1390 <string name="pta_info">This tests whether multitouch works.\n
1391 Touching the screen should render a dot at the location you touched.\n
1392 Touching with additional fingers will render additoinal dots and you should be able to drag them around.</string>
Harsh Modi0975db12014-08-19 18:46:07 -07001393 <string name="poa_test">Projection Offscreen Activity</string>
1394 <string name="poa_info">This tests whether a virtual display will continue to respond to and render even when the screen is off.\n
1395 Simply follow the instructions and the test will detect the pass conditions.\n
1396 Note that turning on the screen too early will result in a failure.</string>
Harsh Modife5933d2014-08-12 16:52:16 -07001397
Jim Steele0c4d08a2014-08-03 00:49:59 -07001398 <!-- Strings for RotationVectorTest and GameRotationVectorTest -->
1399 <string name="rotation_vector_test">Rotation Vector Accuracy Test</string>
destradaa58e36812014-08-20 14:53:21 -07001400 <string name="snsr_rotation_vector_set_reference">
1401 Place the mobile device in a reference position. Note: to provide an accurate reference,
1402 align the device along one edge of a notebook laying on a table.</string>
1403 <string name="snsr_rotation_vector_reference_set">Reference position set.</string>
1404 <string name="snsr_rotation_vector_move_info">Move, shake, and rotate the device.</string>
1405 <string name="snsr_rotation_vector_set_final">Place the device back to the reference position.</string>
1406 <string name="snsr_rotation_vector_verification">Angular deviation [%1$4.1f %2$4.1f %3$4.1f]. Current: %4$f deg. Max tolerated: %5$f.</string>
1407
Zoltan Szatmary-Ban9a2b13e2015-06-15 17:05:04 +01001408 <!-- Strings common for BYOD and DO managed provisioning tests. -->
1409 <string name="afw_device_admin">CTS Verifier - AfW Admin</string>
1410
Rubin Xu55d22d42014-09-24 19:56:58 +01001411 <!-- Strings for BYOD managed provisioning tests (ByodFlowTestActivity) -->
1412 <string name="test_category_managed_provisioning">Managed Provisioning</string>
Rubin Xu55d22d42014-09-24 19:56:58 +01001413 <string name="provisioning_byod">BYOD Managed Provisioning</string>
1414 <string name="provisioning_byod_info">
1415 This test exercises the BYOD managed provisioning flow.
1416 Start by pressing the button on screen and follow instructions to finish the managed provisioning process.
1417 If your device has not been encrypted before, it will be encrypted and rebooted.
1418 After the provisioning process completes, return to this page and carry out further verifications.
Rubin Xu1dcb3e32014-12-16 16:36:13 +00001419 Note: the device will remain encrypted after the test which can only be disabled by factory reset.
Rubin Xu55d22d42014-09-24 19:56:58 +01001420 </string>
1421 <string name="provisioning_byod_start">Start BYOD provisioning flow</string>
1422 <string name="provisioning_byod_instructions">
1423 1. Press the button below to start the managed provisioning flow.
1424 If your device has not been encrypted before, it will reboot to apply encryption.
1425 After reboot follow instructions in the notification area to complete the provisioning.\n
1426 2. After successful provisioning, you should be automatically redirected back to this page.
1427 Please press through the following verification steps.
Rubin Xu1dcb3e32014-12-16 16:36:13 +00001428 Allow a few seconds after returning from provisioning, as the profile owner test should automatically pass.\n
1429 \n
1430 If the device is being encrypted during step 1, it will remain encrypted After this test.
1431 The only way to disable the encryption is to factory reset the device.
Rubin Xu55d22d42014-09-24 19:56:58 +01001432 </string>
1433 <string name="provisioning_byod_profileowner">Profile owner installed</string>
1434 <string name="provisioning_byod_diskencryption">Full disk encryption enabled</string>
Rubin Xuc2b00d82015-02-02 11:30:26 +00001435 <string name="provisioning_byod_profile_visible">Profile-aware accounts settings</string>
1436 <string name="provisioning_byod_admin_visible">Profile-aware device administrator settings</string>
Rubin Xu55d22d42014-09-24 19:56:58 +01001437 <string name="provisioning_byod_workapps_visible">Badged work apps visible in Launcher</string>
Alexandra Gherghinaaa24ed72014-10-08 01:11:32 +01001438 <string name="provisioning_byod_cross_profile">Open app cross profiles</string>
1439 <string name="provisioning_byod_cross_profile_app_personal">
1440 You selected the CTS Verifier option.
1441 </string>
1442 <string name="provisioning_byod_cross_profile_app_work">You selected the Work option.</string>
1443 <string name="provisioning_byod_cross_profile_instruction">
1444 Please press the Go button to start an action.\n
1445 \n
1446 You should be asked to choose either \"CTS Verifier\" or \"Work\" to complete the action.
1447 Pressing either should bring up a page stating your choice.\n
1448 \n
1449 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly.
1450 </string>
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01001451 <string name="provisioning_byod_keyguard_disabled_features">Keyguard disabled features</string>
1452 <string name="provisioning_byod_keyguard_disabled_features_info">
1453 This test exercises Keyguard Disabled Features. Follow instructions above.
1454 </string>
1455 <string name="provisioning_byod_keyguard_disabled_features_instruction">
Zoltan Szatmary-Ban0592ee52015-08-24 13:31:41 +01001456 Please go to Settings &gt; Security &gt; Device administrators and set
1457 \"CTS Verifier - AfW Admin\" as active admin.\n
1458 After that please press the \"Prepare test\" button to disable trust agents.\n
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01001459 Then please press through the following verification steps.\n
Zoltan Szatmary-Ban0592ee52015-08-24 13:31:41 +01001460 Note: Device password will be set to \"testpassword\". After leaving the screen device
1461 password and active admin status will be cleared.
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01001462 </string>
1463 <string name="provisioning_byod_keyguard_disabled_features_prepare_button">Prepare test</string>
Zoltan Szatmary-Ban0592ee52015-08-24 13:31:41 +01001464 <string name="provisioning_byod_keyguard_disabled_features_not_admin">CtsVerifier is not active admin. Please follow instructions.</string>
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01001465 <string name="provisioning_byod_disable_trust_agents">Disable trust agents</string>
1466 <string name="provisioning_byod_disable_trust_agents_instruction">
1467 Please press the Go button to go to Settings > Security. Then go to Trusted agents and\n
1468 check if the agents are shown as disabled by the administrator.
1469 Then please press Back and mark the test as \"Pass\" or \"Fail\".
1470 </string>
1471 <string name="provisioning_byod_fingerprint_disabled_in_settings">Fingerprint is disabled in Settings</string>
1472 <string name="provisioning_byod_fingerprint_disabled_in_settings_instruction">
1473 Please press the Go button to go to Settings > Security. Then go to Fingerprint and\n
1474 check if the screen is shown as disabled by the administrator.
1475 Then please press Back and mark the test as \"Pass\" or \"Fail\".
1476 </string>
1477 <string name="provisioning_byod_disable_fingerprint">Fingerprint disabled on keyguard</string>
1478 <string name="provisioning_byod_disable_fingerprint_instruction">
1479 Please press the Go button to lock the screen. Then try to log in using the fingerprint reader.\n
1480 Expected result is you cannot log in using your fingerprint.\n
1481 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\".
1482 </string>
1483 <string name="provisioning_byod_disable_notifications">Notifications disabled on keyguard</string>
1484 <string name="provisioning_byod_disable_notifications_instruction">
1485 Please press the Go button to lock the screen. Wait a couple of seconds and look out for a
1486 notification from CtsVerifier.\n
1487 Expected result is the notification is shown as \"Contents hidden\", you can not see the contents
1488 (Which would read \"This is a work notification\").\n
1489 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\".
1490 </string>
Alexandra Gherghina2c672b72015-01-22 11:20:23 +00001491 <string name="provisioning_byod_work_notification">Work notification is badged</string>
1492 <string name="provisioning_byod_work_notification_instruction">
1493 Please press the Go button to trigger a notification.\n
1494 \n
1495 Verify that the notification is badged (see sample badge below). Then mark this test accordingly.
1496 </string>
1497 <string name="provisioning_byod_work_notification_title">This is a work notification</string>
Kenny Guy68e7df92015-05-29 15:26:28 +01001498 <string name="provisioning_byod_work_status_icon">Work status icon is displayed</string>
1499 <string name="provisioning_byod_work_status_icon_instruction">
1500 Verify that the current status bar does not have a work status icon (see sample icon below).
1501 \n\n
1502 Please press the Go button to launch a work activity.
1503 \n\n
1504 Verify that the status bar now has a work status icon. Then mark this test accordingly.
1505 </string>
1506 <string name="provisioning_byod_work_status_icon_activity">
1507 Verify that the current status bar has a work status notification.
1508 \n\n
1509 Please press finish to return to the tests and then mark this test accordingly.
1510 </string>
1511 <string name="provisioning_byod_work_status_toast">Work status toast is displayed</string>
1512 <string name="provisioning_byod_work_status_toast_instruction">
1513 Please press the Go button to launch a work activity.
1514 \n\n
1515 Follow instructions and then return and mark this test accordingly.
1516 </string>
1517 <string name="provisioning_byod_work_status_toast_activity">
1518 Turn off the screen and wait a few seconds then turn on the screen again.
1519 \n\n
1520 Verify that a toast was displayed saying you are in the work profile.
1521 \n\n
1522 Please press finish to return to the tests and then mark this test accordingly.
1523 </string>
Rubin Xu55d22d42014-09-24 19:56:58 +01001524 <string name="provisioning_byod_profile_visible_instruction">
1525 Please press the Go button to open the Settings page.
1526 Navigate to Accounts and confirm that:\n
1527 \n
1528 - Both Personal and Work categories exist.\n
1529 - \"Remove work profile\" exists under the Work category.\n
1530 \n
1531 Use the Back button to return to this page.
1532 </string>
1533 <string name="provisioning_byod_admin_visible_instruction">
1534 Please press the Go button to open the Security page in Settings.
1535 Navigate to Device administrators and confirm that:\n
1536 \n
1537 - Both Personal and Work categories exist.\n
Zoltan Szatmary-Ban9a2b13e2015-06-15 17:05:04 +01001538 - \"CTS Verifier - AfW Admin\" exists under the Work category, and is activated.\n
Rubin Xu55d22d42014-09-24 19:56:58 +01001539 \n
1540 Use the Back button to return to this page.
1541 </string>
1542 <string name="provisioning_byod_workapps_visible_instruction">
1543 Please press the Go button to start the launcher.
1544 Go to All Apps screen and scroll through it to confirm that:\n
1545 \n
1546 - A new set of work apps including CTS Verifier appear in the list.\n
Alexandra Gherghina9c1c5a52014-12-09 12:55:23 +00001547 - Work badge overlay appears on work app\'s icon (see example icon below).\n
Rubin Xu55d22d42014-09-24 19:56:58 +01001548 \n
1549 Then navigate back to this screen using Recents button.
1550 </string>
Rubin Xuc2b00d82015-02-02 11:30:26 +00001551
1552 <string name="provisioning_byod_app_settings">Profile-aware app settings</string>
1553 <string name="provisioning_byod_app_settings_instruction">
1554 Please press the Go button to open Apps page in settings.\n
1555 \n
1556 Verify that work profile exists in the dropdown list and selecting it will
1557 bring up apps setting in the work profile.\n
1558 \n
1559 Then use the Back button to return to this test and mark accordingly.
1560 </string>
1561
1562 <string name="provisioning_byod_location_settings">Profile-aware location settings</string>
1563 <string name="provisioning_byod_location_settings_instruction">
1564 Please press the Go button to open Location page in settings.\n
1565 \n
1566 Verify that work profile entry exists in the page.\n
1567 \n
1568 Then use the Back button to return to this test and mark accordingly.
1569 </string>
1570
1571 <string name="provisioning_byod_cred_settings">Profile-aware trusted credential settings</string>
1572 <string name="provisioning_byod_cred_settings_instruction">
1573 Please press the Go button to open the Security settings.
1574 Navigate to "Trusted credentials" and wait for the UI to load.
1575 After the list is loaded, confirm that:\n
1576 \n
1577 The page list credentials for both "Personal" and "Work" profiles.\n
1578 \n
1579 Then use the Back button to return to this test and mark accordingly.
1580 </string>
1581
1582 <string name="provisioning_byod_print_settings">Profile-aware printing settings</string>
1583 <string name="provisioning_byod_print_settings_instruction">
1584 Please press the Go button to open the Printing settings.
1585 \n
1586 Verify that work profile exists in the dropdown list and selecting it will
1587 bring up printing setting in the work profile.\n
1588 \n
1589 Then use the Back button to return to this test and mark accordingly.
1590 </string>
1591
Sudheer Shanka98ff0002015-03-26 16:32:59 +00001592 <string name="provisioning_byod_cross_profile_intent_filters">Cross profile intent filters are set</string>
Rubin Xu55d22d42014-09-24 19:56:58 +01001593 <string name="provisioning_byod_no_activity">Cannot communicate with activity in the work profile.</string>
1594 <string name="provisioning_byod_delete_profile">Initiate deletion of work profile.</string>
1595 <string name="provisioning_byod_profile_deleted">Work profile deleted.</string>
1596 <string name="provisioning_byod_disabled">Device provisioning is not enabled.</string>
Alexandra Gherghinaaa24ed72014-10-08 01:11:32 +01001597 <string name="provisioning_button_finish">Finish</string>
1598 <string name="provisioning_cross_profile_chooser">Choose an app to complete action</string>
Rubin Xua458f302014-10-03 16:09:23 +01001599
1600 <!-- Strings for DeviceOwnerProvisioningTest -->
1601 <string name="provisioning_device_owner">Device Owner Provisioning</string>
1602 <string name="device_owner_provisioning_tests">Device Owner provisioning tests</string>
1603 <string name="device_owner_provisioning_tests_info">The device owner provisioning tests verify that setting up a corporate owned device can only be done on a factory reset device.</string>
1604 <string name="device_owner_provisioning_category">Device Owner Provisioning</string>
1605 <string name="device_owner_negative_test">Device owner negative test</string>
Unsuk Jung35fac2c2014-11-06 23:16:42 -08001606 <string name="device_owner_negative_test_info">Please click the "Start provisioning" button, and when you see a warning dialog telling the device is already set up, select "pass". Otherwise, select "fail".</string>
Rubin Xua458f302014-10-03 16:09:23 +01001607 <string name="start_device_owner_provisioning_button">Start provisioning</string>
Zoltan Szatmary-Ban9a2b13e2015-06-15 17:05:04 +01001608 <string name="positive_device_owner">Device Owner Tests</string>
1609 <string name="device_owner_positive_tests">Device Owner positive tests</string>
1610 <string name="device_owner_positive_tests_instructions">
1611 The positive device owner tests verify policies on a corporate owned device.\n
1612 Press below button first, follow steps described in the dialog that pops up,
1613 then proceed to the test cases.\n
1614 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n
1615 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should
1616 be run last so that it does not interfere with other tests.
1617 </string>
1618 <string name="device_owner_positive_tests_info">
1619 The positive device owner tests verify policies on a corporate owned device.\n
1620 Press below button first, follow steps described in the dialog that pops up,
1621 then proceed to the test cases.\n
1622 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n
1623 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should
1624 be run last so that it does not interfere with other tests.
1625 </string>
1626 <string name="device_owner_positive_category">Device Owner Tests</string>
1627 <string name="set_device_owner_button_label">Set up device owner</string>
1628 <string name="set_device_owner_dialog_title">Set up device owner</string>
1629 <string name="set_device_owner_dialog_text">
1630 Please set the device owner by enabling USB debugging on the device and issuing the following command on the host:\n
1631 adb shell dpm set-device-owner \'com.android.cts.verifier/com.android.cts.verifier.managedprovisioning.DeviceAdminTestReceiver\'
1632 </string>
1633 <string name="device_owner_remove_device_owner_test">Remove device owner</string>
1634 <string name="device_owner_remove_device_owner_test_info">
1635 Please check in Settings &gt; Security &gt; Device Administrators if CTSVerifier is
1636 Device Owner. Then press the button below, and check that CTSVerifier is NOT Device
1637 Owner anymore.
1638 </string>
1639 <string name="remove_device_owner_button">Remove device owner</string>
1640 <string name="device_owner_check_device_owner_test">Check device owner</string>
1641 <string name="device_owner_incorrect_device_owner">Missing or incorrect device owner: CTSVerifier is not DO!</string>
Zoltan Szatmary-Ban01ce4542015-06-22 11:14:47 +01001642 <string name="device_owner_wifi_lockdown_test">WiFi configuration lockdown</string>
1643 <string name="device_owner_wifi_lockdown_info">
1644 Please enter the SSID and auth method of an available WiFi Access Point and press the button to create a
1645 WiFi configuration. This configuration can be seen on Settings &gt; WiFi. The test cases
1646 are going use this config. Please go through test cases in order (from top to bottom).
1647 </string>
1648 <string name="switch_wifi_lockdown_off_button">WiFi config lockdown off</string>
1649 <string name="switch_wifi_lockdown_on_button">WiFi config lockdown on</string>
1650 <string name="wifi_lockdown_go_settings_wifi_button">Go to WiFi Settings</string>
1651 <string name="device_owner_wifi_key_management_none_button">None</string>
1652 <string name="device_owner_wifi_key_management_wpa_button">WPA</string>
1653 <string name="device_owner_wifi_key_management_wep_button">WEP</string>
1654 <string name="create_wifi_config_button_label">Create WiFi configuration</string>
1655 <string name="wifi_lockdown_add_network_failed_dialog_title">WiFi configuration could not be created</string>
1656 <string name="wifi_lockdown_add_network_failed_dialog_text">
1657 There was an error during creation of WiFi configuration. Check if WiFi is switched on.
1658 </string>
1659 <string name="device_owner_wifi_config_unlocked_modification_test">Unlocked config is modifiable in Settings</string>
1660 <string name="device_owner_wifi_config_unlocked_modification_test_info">
1661 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to
1662 Settings &gt; WiFi and see if the CTSVerifier created WiFi configuration can be edited.
1663 Please make sure you can connect to it. The test is successful if the config is editable
1664 and can be connected to.
1665 </string>
1666 <string name="device_owner_wifi_config_locked_modification_test">Locked config is not modifiable in Settings</string>
1667 <string name="device_owner_wifi_config_locked_modification_test_info">
1668 Please press the button to ensure WiFi config lockdown is in effect. Then go to
1669 Settings &gt; WiFi and see if the CTSVerifier created WiFi configuration can NOT be edited
1670 or removed. The test is successful if the config is NOT modifiable.
1671 </string>
1672 <string name="device_owner_wifi_config_locked_connection_test">Locked config can be connected to</string>
1673 <string name="device_owner_wifi_config_locked_connection_test_info">
1674 Please press the button to ensure WiFi config lockdown is in effect. Then go to
1675 Settings &gt; WiFi and see if the CTSVerifier created WiFi configuration can be connected
1676 to manually. The test is successful if the connection can be established.
1677 </string>
1678 <string name="device_owner_wifi_config_unlocked_removal_test">Unlocked config can be forgotten in Settings</string>
1679 <string name="device_owner_wifi_config_unlocked_removal_test_info">
1680 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to
1681 Settings &gt; WiFi and see if the CTSVerifier created WiFi configuration can be forgotten.
1682 The test is successful if the config could be forgotten and is removed from the list of saved configs.
1683 </string>
Benjamin Franz89e40fc2015-07-01 15:35:57 +01001684 <string name="device_owner_disable_statusbar_test">Disable status bar</string>
1685 <string name="device_owner_disable_statusbar_test_info">
1686 Please press the below button to disable the status bar and verify that quick settings, notifications
1687 and the assist gesture are no longer available.\n
1688 Next, press the button to reenable the status bar and verify that quick settings, notification
1689 and the assist gesture are available again.\n
1690 Please mark the test accordingly.
1691 </string>
1692 <string name="device_owner_disable_statusbar_button">Disable status bar</string>
1693 <string name="device_owner_reenable_statusbar_button">Reenable status bar</string>
1694 <string name="device_owner_disable_keyguard_test">Disable keyguard</string>
1695 <string name="device_owner_disable_keyguard_test_info">
1696 Note that any device passwords that you might have set will be deleted during this test.\n
1697 Please press the below button to disable the keyguard. Press the power button on your device to
1698 switch off the screen. Then press the power button to switch the screen back on and verify that
1699 no keyguard was shown.\n
1700 Next, press the button to reenable the keyguard and repeat the above steps, this time verifying that
1701 a keyguard was shown again.\n
1702 Please mark the test accordingly.
1703 </string>
1704 <string name="device_owner_disable_keyguard_button">Disable keyguard</string>
1705 <string name="device_owner_reenable_keyguard_button">Reenable keyguard</string>
Sudheer Shanka72ba56a2015-07-17 18:30:44 +01001706 <string name="device_profile_owner_permission_lockdown_test">Permissions lockdown</string>
1707 <string name="device_profile_owner_permission_lockdown_test_instructions">
1708 Select each of the three grant states for the permission shown below in turn.\n
1709 Now open application settings, select Permissions, and verify if the following behaviour is observed.\n
1710 <b>Allow:</b> Permission is granted to the app and cannot be changed through the settings UI.\n
1711 <b>Let user decide:</b> Permission state can be changed through the settings UI.\n
1712 <b>Deny:</b> Permission is denied to the app and cannot be changed through the settings UI.\n
1713 Please mark the test accordingly.
1714 </string>
1715 <string name="device_owner_permission_lockdown_test_info">
1716 This test checks if the permissions state in settings UI is locked down according to the state set by the device owner.
1717 </string>
1718 <string name="profile_owner_permission_lockdown_test_info">
1719 <b>
1720 Before proceeding, check if com.android.cts.permissionapp (aka CtsPermissionApp) is installed in work profile by going to Settings &gt; Apps. If not, please install the app before proceeding.\n\n
1721 </b>
1722 This test checks if the permissions state in settings UI is locked down correctly depending on the state set by the profile owner.
1723 </string>
1724 <string name="package_not_found">You must install %s (aka CtsPermissionApp).</string>
1725 <string name="permission_allow">Grant</string>
1726 <string name="permission_default">Let user decide</string>
1727 <string name="permission_deny">Deny</string>
1728 <string name="not_profile_owner">%s is not profile owner.</string>
1729 <string name="not_device_owner">%s is not device owner.</string>
1730 <string name="activity_not_found">No activity found to handle intent: %s</string>
1731 <string name="open_settings_button_label">Open Application Settings</string>
1732 <string name="finish_button_label">Finish</string>
Benjamin Franz2e9fd732015-08-10 15:43:42 +01001733 <string name="device_owner_device_admin_visible">Device administrator settings</string>
1734 <string name="device_owner_device_admin_visible_info">
1735 Please press the Go button to open the Security page in Settings.
1736 Navigate to Device administrators and confirm that:\n
1737 \n
1738 - \"CTS Verifier - AfW Admin\" exists and is activated.\n
1739 - \"CTS Verifier - AfW Admin\" cannot be disabled.\n
1740 \n
1741 Use the Back button to return to this page.
1742 </string>
Benjamin Franz1c8defc2015-08-10 16:52:56 +01001743 <string name="device_owner_disallow_config_bt">Disallow configuring Bluetooth</string>
1744 <string name="device_owner_disallow_config_bt_info">
1745 Please press the Set restriction button to set the user restriction.
1746 Then press Go to open the Bluetooth page in Settings.
1747 Confirm that:\n
1748 \n
1749 - You cannot view Bluetooth devices in range.\n
1750 - You cannot edit, add or remove any already paired devices.\n
1751 \n
1752 Use the Back button to return to this page.
1753 </string>
1754 <string name="device_owner_disallow_config_wifi">Disallow configuring WiFi</string>
1755 <string name="device_owner_disallow_config_wifi_info">
1756 Please press the Set restriction button to set the user restriction.
1757 Then press Go to open the WiFi page in Settings.
1758 Confirm that:\n
1759 \n
1760 - You cannot view WiFi networks in range.\n
1761 - You cannot edit, add or remove any existing WiFi configs.\n
1762 \n
1763 Use the Back button to return to this page.
1764 </string>
1765 <string name="device_owner_user_restriction_set">Set restriction</string>
1766 <string name="device_owner_settings_go">Go</string>
Matthew Williams547b8162014-10-15 10:18:11 -07001767
1768 <!-- Strings for JobScheduler Tests -->
1769 <string name="js_test_description">This test is mostly automated, but requires some user interaction. You can pass this test once the list items below are checked.</string>
1770
1771 <string name="js_idle_test">Idle Mode Constraints</string>
1772 <string name="js_start_test_text">Start test</string>
1773 <string name="js_idle_instructions">Verify the behaviour of the JobScheduler API for when the device is in idle mode. Simply follow the on-screen instructions.</string>
1774 <string name="js_idle_description_1">Turn the screen off and then back on in order to begin.</string>
1775 <string name="js_idle_item_idle_off">Idle job does not execute when device is not idle.</string>
1776 <string name="js_idle_item_idle_on">Idle job does execute when device is forced into idle.</string>
1777
1778 <string name="js_charging_test">Charging Constraints</string>
1779 <string name="js_charging_instructions">Verify the behaviour of the JobScheduler API for when the device is on power and unplugged from power. Simply follow the on-screen instructions.</string>
Matthew Williamsdb6a3a82014-11-07 11:06:40 -08001780 <string name="js_charging_description_1">Unplug the device in order to begin.</string>
Matthew Williams547b8162014-10-15 10:18:11 -07001781 <string name="js_charging_off_test">Device not charging will not execute a job with a charging constraint.</string>
1782 <string name="js_charging_on_test">Device when charging will execute a job with a charging constraint.</string>
1783 <string name="js_charging_description_2">After the above test has passed, plug the device back in to continue. If the above failed, you can simply fail this test.</string>
1784
1785 <string name="js_connectivity_test">Connectivity Constraints</string>
1786 <string name="js_connectivity_instructions">Verify the behaviour of the JobScheduler API for when the device has no access to data connectivity. Simply follow the on-screen instructions.</string>
1787 <string name="js_connectivity_description_1">Disable WiFi and Cellular data to begin.</string>
1788 <string name="js_unmetered_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string>
1789 <string name="js_any_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string>
1790 <string name="js_no_connectivity_test">Device with no connectivity will still execute a job with no connectivity constraints.</string>
Chris Wren451834f2014-10-28 14:32:45 -04001791
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001792 <!-- String for the bundled TV app Tests -->
Wonsik Kim18aa5752014-10-30 00:47:57 +09001793
Dongwon Kang83efe7e2015-07-17 15:01:35 -07001794 <string name="tv_input_discover_test">3rd-party TV input test</string>
Wonsik Kimf16680b2014-11-20 23:11:16 +09001795 <string name="tv_input_discover_test_info">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001796 Verify that the bundled TV app launches via Intent and calls the proper API to discover
Dongwon Kang83efe7e2015-07-17 15:01:35 -07001797 3rd-party TV inputs.
Wonsik Kimf16680b2014-11-20 23:11:16 +09001798 </string>
Wonsik Kim18aa5752014-10-30 00:47:57 +09001799 <string name="tv_input_discover_test_go_to_setup">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001800 Select the \"Launch TV app\" button and set up the newly installed TV input:
Wonsik Kimf16680b2014-11-20 23:11:16 +09001801 \"CTS Verifier\".
Wonsik Kim18aa5752014-10-30 00:47:57 +09001802 </string>
1803 <string name="tv_input_discover_test_verify_setup">
1804 Setup activity must have been started.
1805 </string>
1806 <string name="tv_input_discover_test_tune_to_channel">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001807 Select the \"Launch TV app\" button and tune to the \"Dummy\" channel from \"CTS Verifier\"
1808 input. If necessary, configure the channel to be visible.
Wonsik Kim18aa5752014-10-30 00:47:57 +09001809 </string>
1810 <string name="tv_input_discover_test_verify_tune">
1811 Tune command must be called.
1812 </string>
Dongwon Kangf58fc082014-12-01 15:51:03 +09001813 <string name="tv_input_discover_test_verify_overlay_view">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001814 Verify that the overlay appears and displays the text \"Overlay View Dummy Text\" when you tune
1815 to the \"Dummy\" channel.
Dongwon Kangf58fc082014-12-01 15:51:03 +09001816 </string>
Dongwon Kangaa1e8032015-06-01 15:13:06 +09001817 <string name="tv_input_discover_test_verify_global_search">
Dongwon Kang83efe7e2015-07-17 15:01:35 -07001818 Verify the TV app provides query results for 3rd-party input\'s channels and programs in
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001819 global search results.
Dongwon Kangaa1e8032015-06-01 15:13:06 +09001820 </string>
Dongwon Kang2ad14c92015-05-13 18:46:13 +09001821 <string name="tv_input_discover_test_go_to_epg">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001822 Select the \"Launch EPG\" button and locate the \"Dummy\" channel.
Dongwon Kang2ad14c92015-05-13 18:46:13 +09001823 </string>
1824 <string name="tv_input_discover_test_verify_epg">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001825 Do you see the programs named \"Dummy Program\" and their descriptions
Dongwon Kang2ad14c92015-05-13 18:46:13 +09001826 "Dummy Program Description" in the EPG?
1827 </string>
1828 <string name="tv_input_discover_test_yes">Yes</string>
Wonsik Kim18aa5752014-10-30 00:47:57 +09001829
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001830 <string name="tv_parental_control_test">TV app parental controls test</string>
Wonsik Kimf16680b2014-11-20 23:11:16 +09001831 <string name="tv_parental_control_test_info">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001832 Verify that the bundled TV app calls the parental controls API.
Wonsik Kimf16680b2014-11-20 23:11:16 +09001833 </string>
1834 <string name="tv_parental_control_test_turn_on_parental_control">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001835 Select the \"Launch TV app\" button and turn on the parental controls. If parental controls are
1836 on already, turn it off and on again.
Wonsik Kimf16680b2014-11-20 23:11:16 +09001837 </string>
1838 <string name="tv_parental_control_test_verify_receive_broadcast1">
1839 TV input service must have received ACTION_PARENTAL_CONTROLS_ENABLED_CHANGED broadcast.
1840 </string>
1841 <string name="tv_parental_control_test_block_tv_ma">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001842 Select the \"Launch TV app\" button and block the \"Fake\" rating for \"CtsVerifier\" rating
1843 system in the parental control settings. If the rating system is disabled by default, enable it.
1844 If the \"Fake\" rating is already blocked, unblock it, save, and then block again.
Wonsik Kimf16680b2014-11-20 23:11:16 +09001845 </string>
1846 <string name="tv_parental_control_test_verify_receive_broadcast2">
1847 TV input service must have received ACTION_BLOCKED_RATINGS_CHANGED broadcast.
1848 </string>
1849 <string name="tv_parental_control_test_block_unblock">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001850 Select the \"Launch TV app\" button; verify that the channel is blocked.
1851 Try to unblock the screen by entering PIN; verify that it\'s unblocked.
Wonsik Kimf16680b2014-11-20 23:11:16 +09001852 </string>
1853
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001854 <string name="tv_launch_tv_app">Launch TV app</string>
Dongwon Kang2ad14c92015-05-13 18:46:13 +09001855 <string name="tv_launch_epg">Launch EPG</string>
Wonsik Kimf16680b2014-11-20 23:11:16 +09001856 <string name="tv_channel_not_found">
1857 CtsVerifier channel is not set up. Please set up before proceeding.
1858 </string>
1859
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001860 <string name="tv_multiple_tracks_test">TV app closed captions and multi-audio test</string>
Wonsik Kimf5707312014-12-03 15:01:33 +09001861 <string name="tv_multiple_tracks_test_info">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001862 Verify that the bundled TV app calls the multi-track API.
Wonsik Kimf5707312014-12-03 15:01:33 +09001863 </string>
1864 <string name="tv_multiple_tracks_test_select_subtitle">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001865 Select the \"Launch TV app\" button. Verify that closed captions are off by default. Set closed
1866 caption language to English.
Wonsik Kimf5707312014-12-03 15:01:33 +09001867 </string>
1868 <string name="tv_multiple_tracks_test_verify_set_caption_enabled">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001869 Captions are enabled.
Wonsik Kimf5707312014-12-03 15:01:33 +09001870 </string>
1871 <string name="tv_multiple_tracks_test_verify_select_subtitle">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001872 The English closed caption track should be selected.
Wonsik Kimf5707312014-12-03 15:01:33 +09001873 </string>
1874 <string name="tv_multiple_tracks_test_select_audio">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07001875 Select the \"Launch TV app\" button. Verify that the audio track is English by default.
Wonsik Kimf5707312014-12-03 15:01:33 +09001876 Select Spanish audio track.
1877 </string>
1878 <string name="tv_multiple_tracks_test_verify_select_audio">
1879 The Spanish audio track should be selected.
1880 </string>
1881
Chulwoo Lee19815cb2015-06-19 14:53:37 -07001882 <string name="tv_time_shift_test">TV app time shift test</string>
1883 <string name="tv_time_shift_test_info">
1884 This test verifies that the TV app invokes proper time shift APIs in the framwork.
1885 </string>
1886 <string name="tv_time_shift_test_pause_resume">
1887 Press the \"Launch TV app\" button. Verify that the playback control is available.
1888 Pause the playback and then resume it.
1889 </string>
1890 <string name="tv_time_shift_test_verify_resume_after_pause">
1891 The playback should be resumed after pause.
1892 </string>
1893 <string name="tv_time_shift_test_verify_position_tracking">
1894 The playback position tracking should be activated.
1895 </string>
1896 <string name="tv_time_shift_test_speed_rate">
1897 Press the \"Launch TV app\" button. Verify that the playback control is available.
1898 Rewind the playback and in a few seconds fast-forward it.
1899 </string>
1900 <string name="tv_time_shift_test_verify_rewind">
1901 The playback should be rewinded.
1902 </string>
1903 <string name="tv_time_shift_test_verify_fast_forward">
1904 The playback should be fast-forwarded.
1905 </string>
1906 <string name="tv_time_shift_test_seek">
1907 Press the \"Launch TV app\" button. Verify that the playback control is available.
1908 Seek to previous and then seek to next.
1909 </string>
1910 <string name="tv_time_shift_test_verify_seek_to_previous">
1911 The playback position should be moved to the previous position.
1912 </string>
1913 <string name="tv_time_shift_test_verify_seek_to_next">
1914 The playback position should be moved to the next position.
1915 </string>
1916
Dongwon Kangf58fc082014-12-01 15:51:03 +09001917 <string name="overlay_view_text">Overlay View Dummy Text</string>
Wonsik Kimf16680b2014-11-20 23:11:16 +09001918 <string name="fake_rating">Fake</string>
Wonsik Kim18aa5752014-10-30 00:47:57 +09001919
Chris Wren451834f2014-10-28 14:32:45 -04001920 <!-- A list of fully-qualified test classes that should not be run. -->
1921 <string-array name="disabled_tests" />
Jason Monk5ece9982015-01-21 15:17:20 -05001922
1923 <!-- Strings for screen pinning test -->
1924 <string name="screen_pinning_test">Screen Pinning Test</string>
1925 <string name="screen_pin_instructions">Pressing next will prompt you to enter screen pinning, allow this app to enter screen pinning.</string>
1926 <string name="screen_pin_check_pinned">Press Next to verify the app is pinned.</string>
1927 <string name="screen_pin_no_exit">Try to leave the app without unpinning the screen. Press next once you have verified you cannot leave.</string>
1928 <string name="screen_pin_exit">Use interactions defined by your device to unpin such as long pressing the back and overview button, then press next.</string>
1929 <string name="screen_pinning_done">All tests completed successfully.</string>
1930
1931 <string name="error_screen_no_longer_pinned">The screen was no longer pinned.</string>
1932 <string name="error_screen_already_pinned">Cannot start the test with the screen already pinned.</string>
1933 <string name="error_screen_pinning_did_not_start">Screen was not pinned.</string>
1934 <string name="error_screen_pinning_did_not_exit">Screen was not unpinned.</string>
1935 <string name="error_screen_pinning_couldnt_exit">Could not exit screen pinning through API.</string>
Paul McLean365be3a2015-06-04 12:40:18 -07001936
1937 <!-- Audio Devices Notifcations Test -->
1938 <string name="audio_devices_notifications_test">Audio Devices Notifications Test</string>
1939 <string name="audio_devices_notification_instructions">
1940 Click the "Clear Messages" button then connect and disconnect a wired headset.
1941 Note if the appropriate notification messages appear below.
1942 </string>
1943 <string name="audio_dev_notification_clearmsgs">Clear Messages</string>
1944 <string name="audio_dev_notification_connectMsg">CONNECT DETECTED</string>
1945 <string name="audio_dev_notification_disconnectMsg">DISCONNECT DETECTED</string>
Paul McLeanaf80c872015-06-05 07:48:15 -07001946
1947 <!-- Audio Routing Notifcations Test -->
1948 <string name="audio_routingnotifications_test">Audio Routing Notifications Test</string>
1949 <string name="audio_dev_routingnotification_instructions">
1950 Click on the "Play" button in the AudioTrack Routing Notifictions section below to
1951 start (silent) playback. Insert a wired headset. Observe a message acknowledging the
1952 rerouting event below. Remove the wired headset and observe the new routing message.
1953 Click on the "Stop" button to stop playback.\n
1954 Repeat the process with "Record" and "Stop" button in the AudioRecord Routing
1955 Notifications section below.
1956 </string>
1957 <string name="audio_routingnotification_playBtn">Play</string>
1958 <string name="audio_routingnotification_playStopBtn">Stop</string>
1959 <string name="audio_routingnotification_recBtn">Record</string>
1960 <string name="audio_routingnotification_recStopBtn">Stop</string>
1961 <string name="audio_routingnotification_playHeader">AudioTrack Routing Notifications</string>
1962 <string name="audio_routingnotification_recHeader">AudioRecord Routing Notifications</string>
1963 <string name="audio_routingnotification_trackRoutingMsg">AudioTrack rerouting</string>
1964 <string name="audio_routingnotification_recordRoutingMsg">AudioRecord rerouting</string>
Ricardo Garciae908b092015-07-13 19:10:50 -07001965
1966 <!-- Audio Loopback Latency Test -->
1967 <string name="audio_loopback_test">Audio Loopback Latency Test</string>
1968 <string name="audio_loopback_info">
1969 This test requires the Loopback Plug. Please connect a Loopback Plug on the headset
1970 connector, and proceed with the instructions on the screen.
1971 The system will measure the input-output audio latency by injecting a pulse on the output,
1972 and computing the distance between replicas of the pulse.
1973 You can vary the Audio Level slider to ensure the pulse will feed back at adecuate levels.
1974 Repeat until a confidence level >= 0.6 is achieved.
1975 </string>
1976 <string name="audio_loopback_instructions">
1977 Please connect a "Loopback Plug" and press "Loopback Plug Ready".
1978 </string>
1979 <string name="audio_loopback_plug_ready_btn">Loopback Plug Ready</string>
1980 <string name="audio_loopback_instructions2">
1981 Set the audio level to a suitable value, then press Test button.
1982 It might require multiple tries until a confidence >= 0.6 is achieved.
1983 </string>
1984 <string name="audio_loopback_level_text">Audio Level</string>
1985 <string name="audio_loopback_test_btn">Test</string>
1986 <string name="audio_loopback_results_text">Results...</string>
1987
Ricardo Garcia9b2e1682015-07-29 15:36:05 -07001988 <!-- Audio Frequency Line Test -->
1989 <string name="audio_frequency_line_test">Audio Frequency Line Test</string>
1990 <string name="audio_frequency_line_info">
Ricardo Garciaea8dd5d2015-08-07 19:10:18 -07001991 The system will measure the frequency response of the left and right line outputs,
1992 by feeding them back thru the microphone conection with the loopback jack.
Ricardo Garcia9b2e1682015-07-29 15:36:05 -07001993 This test requires the Loopback Plug. Please connect a Loopback Plug on the headset
1994 connector, and proceed with the instructions on the screen.
Ricardo Garciaea8dd5d2015-08-07 19:10:18 -07001995 </string>
Ricardo Garcia9b2e1682015-07-29 15:36:05 -07001996 <string name="audio_frequency_line_instructions">
1997 Please connect a "Loopback Plug" and press "Loopback Plug Ready".
1998 </string>
1999 <string name="audio_frequency_line_plug_ready_btn">Loopback Plug Ready</string>
2000
2001 <string name="audio_frequency_line_test_btn">Test</string>
2002 <string name="audio_frequency_line_results_text">Results...</string>
Ricardo Garciaea8dd5d2015-08-07 19:10:18 -07002003
2004 <!-- Audio Frequency Speaker Test -->
2005 <string name="audio_frequency_speaker_test">Audio Frequency Speaker Test</string>
2006 <string name="audio_frequency_speaker_info">
2007 This test requires an external USB reference microphone. Please connect the USB microphone and proceed with the instructions on the screen.
2008 The system will measure frequency response of the left and right speakers (if there are two speakers), or twice the response of the mono speaker.
2009 </string>
2010 <string name="audio_frequency_speaker_instructions">
2011 Please connect an USB reference microphone and press "USB Reference microphone ready".
2012 </string>
2013 <string name="audio_frequency_speaker_usb_status">Waiting for USB microphone...</string>
2014 <string name="audio_frequency_speaker_mic_ready_btn">USB Reference microphone ready</string>
2015 <string name="audio_frequency_speaker_mic_ready_text">USB Audio device detected\n\nPlease set up Device Under test
2016 in quiet room, and Microphone 20 cms perpendicular to center of screen, then press TEST</string>
2017 <string name="audio_frequency_speaker_mic_not_ready_text">"No USB Audio device detected. Please reconnect."</string>
2018 <string name="audio_frequency_speaker_test_btn">Test</string>
2019 <string name="audio_frequency_speaker_results_text">Results...</string>
2020
Ricardo Garcia9b2e1682015-07-29 15:36:05 -07002021
Brian Muramatsu70a9e3f2010-06-25 15:27:09 -07002022</resources>