blob: 2b955dc92c4a09b9f1acb35186fa60aa25276b54 [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-->
Sudheer Shanka16acbdd2016-02-08 14:23:04 +000016<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
Brian Muramatsu70a9e3f2010-06-25 15:27:09 -070017 <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>
Tyler Gunn177db3a2017-03-30 21:17:42 -070041 <string name="test_category_telecom">Telecom</string>
Ta-wei Yen3f78d2e2016-11-16 10:45:50 -080042 <string name="test_category_telephony">Telephony</string>
Wonsik Kim18aa5752014-10-30 00:47:57 +090043 <string name="test_category_tv">TV</string>
Brian Muramatsu78d2c1d2010-08-16 15:22:30 -070044 <string name="test_category_other">Other</string>
Brian Muramatsuac007372010-08-18 11:02:28 -070045 <string name="clear">Clear</string>
Nicholas Sauer5eba4292016-10-30 21:16:04 -070046 <string name="test_results_clear_title">Remove all test results?</string>
47 <string name="test_results_clear_yes">Yes</string>
48 <string name="test_results_clear_cancel">Cancel</string>
Brian Muramatsuac007372010-08-18 11:02:28 -070049 <string name="test_results_cleared">Test results cleared.</string>
Brian Muramatsu52f3b6f2011-09-23 12:09:59 -070050 <string name="view">View</string>
Brian Muramatsu82ab52a2011-06-27 14:02:12 -070051 <string name="test_results_error">Couldn\'t create test results report.</string>
Nicholas Sauer8cf9bdb2015-08-23 13:49:53 -070052 <string name="runtime_permissions_error">Cannot continue. Please grant runtime permissions</string>
Jeff Davidson4c3bbd82011-08-02 11:51:43 -070053 <string name="export">Export</string>
54 <string name="no_storage">Cannot save report to external storage, see log for details.</string>
55 <string name="report_saved">Report saved to: %s</string>
Dan Morrill5df275b2010-08-11 12:19:19 -070056
Damien Bargiacchia433c272017-01-31 16:34:22 -080057 <!-- Strings for IntentDrivenTestActivity -->
58 <string name="intent_not_resolved">Intent Not Resolved</string>
59 <string name="intent_not_resolved_info">The following intent could not be resolved: %1$s</string>
60
Brian Muramatsu52f3b6f2011-09-23 12:09:59 -070061 <!-- Strings for ReportViewerActivity -->
62 <string name="report_viewer">Report Viewer</string>
63
Anna Galusza33061232016-02-02 14:46:55 -080064 <!-- String shared between BackupTestActivity and BackupAccessibilityTestActivity -->
65 <string name="bu_loading">Loading...</string>
66 <string name="bu_generate_error">Error occurred while generating test data...</string>
67 <string name="bu_settings">Settings</string>
68
Brian Muramatsu0ac3cdf2011-08-03 11:47:10 -070069 <!-- Strings for BackupTestActivity -->
70 <string name="backup_test">Data Backup Test</string>
Jeff Davidson112f2792011-08-22 09:46:46 -070071 <string name="backup_info">This test checks that data backup and automatic restore works
Brian Muramatsu0ac3cdf2011-08-03 11:47:10 -070072 properly. The test activity lists some preferences and files that are backed up and
73 restored by the CTS Verifier. If backup and restore is working properly, these values
74 should be restored after running the backup manager, uninstalling the app, and reinstalling
75 the CTS Verifier.
76 \n\nPress the \"Generate Test Data\" to populate these values
77 and then follow the on screen instructions to finish the test.
78 </string>
Anna Galusza33061232016-02-02 14:46:55 -080079 <string name="bu_generate">Generate Test Data</string>
Brian Muramatsu0ac3cdf2011-08-03 11:47:10 -070080 <string name="bu_preferences">Preferences</string>
81 <string name="bu_files">Files</string>
Brian Muramatsu0ac3cdf2011-08-03 11:47:10 -070082 <string name="bu_instructions">Random values for the preferences and files have been saved.
83 \n\nFollow the instructions below to check that the data backup and restore works:
Jeff Davidson112f2792011-08-22 09:46:46 -070084 \n\n1. Make sure backup and automatic restore are enabled in settings. Depending on the
85 backup transport supported by the device you may need to do additional steps. For instance
Takayuki Hoshi7af0e6c2014-11-14 17:07:40 +090086 you may need to set a Google account as the backup account for the device. If you cannot
87 find the corresponding setting options on your device, run \"adb shell bmgr enable true\"
88 to enable the backup manager. You can check its status by executing \"adb shell bmgr
89 enabled\".
Brian Muramatsu0ac3cdf2011-08-03 11:47:10 -070090 \n\n2. Run the backup manager: adb shell bmgr run
91 \n\n3. Uninstall the program: adb uninstall com.android.cts.verifier
92 \n\n4. Reinstall the CTS Verifier and verify that the values are still the same.
93 </string>
Anna Galusza33061232016-02-02 14:46:55 -080094
95 <!-- Strings for BackupAccessibilityTestActivity -->
96 <string name="backup_accessibility_test">Backup Accessibility Settings Test</string>
97 <string name="backup_accessibility_info">This test checks that data backup and automatic restore
98 of Accessibility-related settings works properly. If backup and restore is working properly,
99 these values should be restored after running the backup manager, removing your Google
100 account, changing the accessibility settings values, and re-adding your Google account.
101 \n\nPress \"Generate Test Data\" to generate test values for accessibility settings and then
102 follow the on screen instructions to finish the test.
103 </string>
104 <string name="bua_settings">General Accessibility Settings</string>
105 <string name="bua_settings_color_correction">Color Correction Settings</string>
106 <string name="bua_settings_accessibility_services">Accessibility Service Settings</string>
107 <string name="bua_settings_captions">Captions Settings</string>
108 <string name="bua_settings_tts">TTS Settings</string>
109 <string name="bua_settings_system">Other System Settings</string>
110 <string name="bua_instructions">You will need two devices for this test.
111 \n\nFollow the instructions below to check that the data backup and restore of
112 accessibility-related settings works properly:
113 \n\n1. Make sure backup and automatic restore are enabled in settings. If you cannot find
114 the corresponding setting options on your device, run \"adb shell bmgr enable true\" to
115 enable the backup manager. You can check its status by executing \"adb shell bmgr enabled\".
116 You will also need to set a Google account as the backup account for the device.
117 \n\n2. Press \"Read Current Values\" and note the default values for the listed settings.
118 Values that are either \"0\" or \"null\" will appear in green. Note: Some default values are
119 neither \"0\", nor \"null\", so you still need to pay attention to the default setting
120 values that are not highlighted.
121 \n\n3. Change the values of the listed settings to something other than their default value.
122 \n\n4. Return to the CtsVerifier and press \"Read Current Values\". Make sure that you have
123 changed all of the settings.
124 \n\n5. Run the backup manager: adb shell bmgr run
125 \n\n6. Factory reset data on the second device. While going through the Setup Wizard,
126 restore all data from the account on your first device. When prompted, choose to restore all
127 settings from your first device.
128 \n\n7. Install CtsVerifier on your new device and make sure that the values read on the
129 second device match the values on your first device.
130 </string>
131 <string name="bua_show_instructions">Show Instructions</string>
132 <string name="bua_read_settings">Read Current Values</string>
Brian Muramatsu0ac3cdf2011-08-03 11:47:10 -0700133
Brian Muramatsu713049d2011-06-23 18:35:36 -0700134 <!-- Strings for Device Administration tests -->
135 <string name="da_policy_serialization_test">Policy Serialization Test</string>
136 <string name="da_policy_serialization_info">This test checks that a device policy is properly
137 saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create
138 a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the
139 device and verify that all rows in the policy list are green. Red items indicate policy
140 settings that were not loaded properly.
141 </string>
Harsh Modi0d3062d2015-06-02 15:59:39 -0700142 <string name="car_dock_test">Car Dock Test</string>
143 <string name="car_dock_test_desc">This test ensures that car mode opens the app associated with
Harsh Modi565526d2015-07-21 17:40:33 -0700144 car dock when going into car mode.\n\n
145 Click on "Enable Car Mode" to start the test. Clicking on the button will either bring up a
146 disambiguation dialog asking which app to open or immediately open the CAR_DOCK application.
147 Select the "CTS Verifier" app and then "Always" if the dialog pops up.
148 This will open the CAR_DOCK application.\n\n
149 In the CAR_DOCK application, press the home button, which will enable the pass button if the
150 framework correctly tries to open the CAR_DOCK app again.</string>
Harsh Modi0d3062d2015-06-02 15:59:39 -0700151 <string name="car_mode_enable">Enable Car Mode</string>
152 <string name="car_dock_activity_text">Press the Home button</string>
Brian Muramatsu713049d2011-06-23 18:35:36 -0700153 <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device
154 policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your
155 device and return to this test in the CTS Verifier.
156 </string>
157 <string name="da_generate_policy">Generate Policy</string>
158 <string name="da_apply_policy">Apply Policy</string>
159 <string name="da_random_policy">Random policy generated.</string>
160 <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string>
161 <string name="da_password_quality">Password Quality</string>
162 <string name="da_password_quality_alphabetic">Alphabetic</string>
163 <string name="da_password_quality_alphanumeric">Alphanumeric</string>
164 <string name="da_password_quality_numeric">Numeric</string>
165 <string name="da_password_quality_something">Something</string>
Brian Muramatsu713049d2011-06-23 18:35:36 -0700166 <string name="da_password_minimum_length">Minimum Password Length</string>
167 <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string>
168 <string name="da_maximum_time_to_lock">Maximum Time to Lock</string>
169 <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string>
170
171 <string name="da_screen_lock_test">Screen Lock Test</string>
172 <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow
173 method immediately locks the screen. It should lock the screen immediately despite any
Christine Chen523d04c2011-09-22 11:45:50 -0700174 settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen.
Brian Muramatsu76c50252011-06-29 17:12:29 -0700175 Your screen should be locked and require the password to be entered.
Brian Muramatsu713049d2011-06-23 18:35:36 -0700176 </string>
Ahmet Kerim SENOL9fa97c22015-10-12 15:29:11 +0100177 <string name="da_kg_disabled_features_test">Keyguard Disabled Features Test</string>
178 <string name="rn_kg_disabled_features_test">Redacted Notifications Keyguard Disabled Features Test</string>
Brian Muramatsu713049d2011-06-23 18:35:36 -0700179 <string name="da_force_lock">Force Lock</string>
Brian Muramatsu713049d2011-06-23 18:35:36 -0700180 <string name="da_lock_success">It appears the screen was locked successfully!</string>
181 <string name="da_lock_error">It does not look like the screen was locked...</string>
182
Andres Morales469db8a2015-07-22 10:47:13 -0700183 <!-- Strings for lock bound keys test -->
184 <string name="sec_lock_bound_key_test">Lock Bound Keys Test</string>
185 <string name="sec_lock_bound_key_test_info">
186 This test ensures that Keystore cryptographic keys that are bound to lock screen authentication
187 are unusable without a recent enough authentication. You need to set up a screen lock in order to
188 complete this test. If available, this test should be run by using fingerprint authentication
189 as well as PIN/pattern/password authentication.
190 </string>
Andres Morales626bb612015-07-22 16:01:15 -0700191 <string name="sec_fingerprint_bound_key_test">Fingerprint Bound Keys Test</string>
192 <string name="sec_fingerprint_bound_key_test_info">
193 This test ensures that Keystore cryptographic keys that are bound to fingerprint authentication
194 are unusable without an authentication. You need to set up a fingerprint order to
195 complete this test.
196 </string>
197 <string name="sec_fp_dialog_message">Authenticate now with fingerprint</string>
198 <string name="sec_fp_auth_failed">Authentication failed</string>
Andres Morales469db8a2015-07-22 10:47:13 -0700199 <string name="sec_start_test">Start Test</string>
200
Brian Muramatsue891acb2011-05-19 16:02:39 -0700201 <!-- Strings for BluetoothActivity -->
202 <string name="bluetooth_test">Bluetooth Test</string>
Satomi1dfcc1c2016-08-08 17:07:22 +0900203 <string name="bluetooth_test_info">
204 The Bluetooth Control tests check whether or not the device
205 can disable and enable Bluetooth properly.
206 \n\nThe Bluetooth tests require two devices, and Bluetooth data is exchanged between them.
207 \nThere are two types of connections: Insecure and Secure. There are two types of roles: Server and Client. You must pass all connection and role combinations.
208 \nThis is a list of the tests:
209 \nThis Device x Other Device
210 \n\n\"Bluetooth LE Insecure Client Test\" x \"Bluetooth LE Insecure Server Test\"
211 \n\n\"Bluetooth LE Insecure Server Test\" x \"Bluetooth LE Insecure Client Test\"
212 \n\n\"Bluetooth LE Secure Client Test\" x \"Bluetooth LE Secure Server Test\"
213 \n\n\"Bluetooth LE Secure Server Test\" x \"Bluetooth LE Secure Client Test\"
214 \n\nThe Device Communication tests require two
Brian Muramatsue891acb2011-05-19 16:02:39 -0700215 devices to pair and exchange messages. The two devices must be:
216 \n\n1. a candidate device implementation running the software build to be tested
Satomi1dfcc1c2016-08-08 17:07:22 +0900217 \n\n2. a separate device implementation already known to be compatible
218 </string>
Brian Muramatsue891acb2011-05-19 16:02:39 -0700219
Brian Muramatsue891acb2011-05-19 16:02:39 -0700220 <string name="bt_control">Bluetooth Control</string>
221 <string name="bt_device_communication">Device Communication</string>
Satomi1dfcc1c2016-08-08 17:07:22 +0900222 <string name="bt_le">Bluetooth LE</string>
Brian Muramatsue891acb2011-05-19 16:02:39 -0700223
224 <string name="bt_toggle_bluetooth">Toggle Bluetooth</string>
225 <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string>
226 <string name="bt_enable_bluetooth">Enable Bluetooth</string>
227 <string name="bt_disable_bluetooth">Disable Bluetooth</string>
228 <string name="bt_disabling">Disabling Bluetooth...</string>
229 <string name="bt_disabling_error">Could not disable Bluetooth...</string>
230
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700231 <string name="bt_connection_access_server">Connection Access Server</string>
232 <string name="bt_connection_access_client">Connection Access Client</string>
233 <string name="bt_connection_access_server_info">
234 Start the CTS Verifier on another device, start the Bluetooth test, and choose
destradaa65c7cdb2013-10-28 16:36:12 -0700235 \"Connection Access Client\" to setup the test.
236 \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700237 using the \"Make Discoverable\" and \"Pick Server\" buttons.
238 \n\nA connection access request should appear on the server and enable the pass button.
239 </string>
240 <string name="bt_connection_access_client_info">
241 Start the CTS Verifier on another device, start the Bluetooth test, and choose
destradaa65c7cdb2013-10-28 16:36:12 -0700242 \"Connection Access Server\" to complete the test.
243 \n\nMake the device acting as the server discoverable and connect to it via the
244 \"Pick Server\" button. Check that the server displays the connection access request
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700245 dialog. The client device does not need to do anything else.
246 </string>
247 <string name="bt_ca_dialog">Was the connection access request dialog shown?</string>
248 <string name="bt_ca_tips">
249 Tap the \"Bluetooth Settings\" button and check that both devices are not paired
250 before running the test.
251 \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth
252 devices together and start the test.
253 </string>
254
Brian Muramatsue891acb2011-05-19 16:02:39 -0700255 <string name="bt_secure_server">Secure Server</string>
256 <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>
257 <string name="bt_insecure_server">Insecure Server</string>
258 <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>
259 <string name="bt_waiting">Waiting for client...</string>
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700260 <string name="bt_listening">Listening...</string>
Brian Muramatsue891acb2011-05-19 16:02:39 -0700261 <string name="bt_connecting">Connecting...</string>
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700262 <string name="bt_connected">Connected</string>
Brian Muramatsue891acb2011-05-19 16:02:39 -0700263 <string name="bt_received_messages">Received Messages</string>
264 <string name="bt_sent_messages">Sent Messages</string>
265 <string name="bt_no_messages">No messages</string>
266 <string name="bt_make_discoverable">Make Discoverable</string>
Brian Muramatsu0822bf42011-09-12 12:29:32 -0700267 <string name="bt_pick_server">Pick Server</string>
Brian Muramatsu8b98f7c2011-06-08 14:50:24 -0700268 <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string>
269 <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string>
Satomi1dfcc1c2016-08-08 17:07:22 +0900270 <string name="bt_advertise_unsupported_title">Advertising is not supported</string>
271 <string name="bt_advertise_unsupported_message">Advertising is not supported on this device.\nTest finishes.</string>
272 <string name="bt_open_failed_title">BLE open failed</string>
273 <string name="bt_open_failed_message">Cannot open BLE GattService.\nTest finishes.</string>
274 <string name="bt_add_service_failed_title">Add service failed</string>
275 <string name="bt_add_service_failed_message">Failed to add services.\nTest finishes.</string>
Brian Muramatsue891acb2011-05-19 16:02:39 -0700276
277 <string name="bt_secure_client">Secure Client</string>
278 <string name="bt_insecure_client">Insecure Client</string>
279
280 <string name="bt_device_picker">Device Picker</string>
281 <string name="bt_paired_devices">Paired Devices</string>
282 <string name="bt_new_devices">New Devices</string>
283 <string name="bt_no_devices">No devices</string>
284 <string name="bt_scan">Scan for Devices</string>
285 <string name="bt_scanning">Scanning...</string>
286 <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>
287 <string name="bt_settings">Bluetooth Settings</string>
288
John Du73462362013-07-26 12:28:28 -0700289 <!-- BLE client side strings -->
290 <string name="ble_client_service_name">Bluetooth LE GATT Client Handler Service</string>
Satomi1dfcc1c2016-08-08 17:07:22 +0900291 <string name="ble_client_test_name">01 Bluetooth LE Client Test</string>
292 <string name="ble_client_connect_name">Bluetooth LE Client Connect</string>
293 <string name="ble_discover_service_name">Bluetooth LE Discover Service</string>
294 <string name="ble_read_characteristic_name">Bluetooth LE Read Characteristic</string>
295 <string name="ble_write_characteristic_name">Bluetooth LE Write Characteristic</string>
296 <string name="ble_reliable_write_name">Bluetooth LE Reliable Write</string>
297 <string name="ble_reliable_write_bad_resp_name">Bluetooth LE Reliable Write (receive bad response)</string>
298 <string name="ble_notify_characteristic_name">Bluetooth LE Notify Characteristic</string>
299 <string name="ble_read_descriptor_name">Bluetooth LE Read Descriptor</string>
300 <string name="ble_write_descriptor_name">Bluetooth LE Write Descriptor</string>
301 <string name="ble_read_rssi_name">Bluetooth LE Read RSSI</string>
302 <string name="ble_client_disconnect_name">Bluetooth LE Client Disconnect</string>
303 <string name="ble_client_test_info">
304 The Bluetooth LE test must be done simultaneously on two devices. This device is the client.
305 All tests listed here must be done with out pairing.
306 </string>
John Du73462362013-07-26 12:28:28 -0700307 <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>
308 <string name="ble_discover_service_info">Verify that the service is discovered when you press the "Discover Service" button.</string>
309 <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>
310 <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>
311 <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>
312 <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>
313 <string name="ble_client_disconnect_info">Verify that the device is disconnected when you press the "Disconnect" button</string>
314 <string name="ble_address">Bluetooth address</string>
315 <string name="ble_connect">Connect</string>
316 <string name="ble_discover_service">Discover service</string>
317 <string name="ble_write_hint">Nothing to write yet</string>
318 <string name="ble_read_hint">Nothing read yet</string>
319 <string name="ble_write">Write</string>
320 <string name="ble_read">Read</string>
321 <string name="ble_begin_write">Begin write</string>
322 <string name="ble_execute_write">Execute write</string>
323 <string name="ble_begin_notification">Begin notification</string>
324 <string name="ble_stop_notification">Stop notification</string>
325 <string name="ble_waiting_notification">Waiting on notification</string>
326 <string name="ble_read_rssi">Read RSSI</string>
327 <string name="ble_disconnect">Disconnect</string>
Yicheng Fanc8882202014-11-10 12:10:10 -0800328 <string name="ble_test_text">TEST</string>
Satomi1dfcc1c2016-08-08 17:07:22 +0900329 <string name="ble_test_finished">Test finished</string>
330 <string name="ble_test_next">Next</string>
331 <string name="ble_test_running">Test Running</string>
332 <string name="ble_test_running_message">This test requires a few minutes. Don\'t interrupt the test.</string>
333 <string name="ble_mtu_23_name">Bluetooth LE Request MTU(23bytes)</string>
334 <string name="ble_mtu_512_name">Bluetooth LE Request MTU(512bytes)</string>
John Du73462362013-07-26 12:28:28 -0700335
336 <!-- BLE server side strings -->
337 <string name="ble_server_service_name">Bluetooth LE GATT Server Handler Service</string>
Satomi1dfcc1c2016-08-08 17:07:22 +0900338 <string name="ble_server_start_name">01 Bluetooth LE Server Test</string>
339 <string name="ble_server_start_info">
340 The Bluetooth LE test must be done simultaneously on two devices, a server device and a client device. This device is the server.
341 </string>
342 <string name="ble_server_receiving_connect">Waiting on connection from Bluetooth LE client.</string>
343 <string name="ble_server_add_service">Adding service to Bluetooth LE server.</string>
John Du73462362013-07-26 12:28:28 -0700344 <string name="ble_server_write_characteristic">Waiting on write characteristic request</string>
345 <string name="ble_server_read_characteristic">Waiting on read characteristic request</string>
346 <string name="ble_server_write_descriptor">Waiting on write descriptor request</string>
347 <string name="ble_server_read_descriptor">Waiting on read descriptor request</string>
348 <string name="ble_server_reliable_write">Waiting on reliable write from client</string>
Satomi1dfcc1c2016-08-08 17:07:22 +0900349 <string name="ble_server_reliable_write_bad_resp">Waiting on reliable write from client (send bad response)</string>
350 <string name="ble_server_receiving_disconnect">Waiting on disconnection from Bluetooth LE client</string>
351 <string name="ble_connection_priority_server_name">02 Bluetooth LE Connection Priority Server Test</string>
352 <string name="ble_connection_priority_server_info">Bluetooth LE Connection Priority Server receive message from message in 3 different priority.</string>
353 <string name="ble_server_notify_characteristic">Waiting on notify characteristic request</string>
354 <string name="ble_server_write_characteristic_without_permission">Waiting on write characteristic request without permission</string>
355 <string name="ble_server_read_characteristic_without_permission">Waiting on read characteristic request without permission</string>
356 <string name="ble_server_write_descriptor_without_permission">Waiting on write descriptor request without permission</string>
357 <string name="ble_server_read_descriptor_without_permission"> Waiting on read descriptor request without permission</string>
358 <string name="ble_server_write_characteristic_need_encrypted">Waiting on write encrypted characteristic request</string>
359 <string name="ble_server_read_characteristic_need_encrypted">Waiting on read encryptedcharacteristic request</string>
360 <string name="ble_server_write_descriptor_need_encrypted">Waiting on write encrypted descriptor request</string>
361 <string name="ble_server_read_descriptor_need_encrypted"> Waiting on read encrypted descriptor request</string>
362 <string name="ble_server_indicate_characteristic">Waiting on indicate characteristic request</string>
363 <string name="ble_server_mtu_23bytes">Waiting on MTU request(23 bytes)</string>
364 <string name="ble_server_mtu_512bytes">Waiting on MTU request(512 bytes)</string>
365 <string name="ble_encrypted_server_name">03 Bluetooth LE Encrypted Server Test</string>
366 <string name="ble_encrypted_server_info">Bluetooth LE Encrypted Server Waiting on read/write characteristic and descriptor request need encrypted.</string>
367 <string name="ble_insecure_server_enctypted_info">Bluetooth LE Server is in operation.\nThis test does not change server state.\n\nIf Bluetooth pairing request was notified by system, you must cancel it.\n\nOnce the client tests are all successful, please change the state of the server-side to the "success".</string>
368 <string name="ble_insecure_server_test_list_name">Bluetooth LE Insecure Server Test</string>
369 <string name="ble_insecure_server_test_list_info">
370 This test is mostly automated, but requires some user interaction.
371 Once the list items below have check marks, the test is complete.
372 \n\nTap \"01 Bluetooth LE Server Test\" on this device, then tap \"01 Bluetooth LE Client Test\" on the other device.
373 \nWhen the test is complete, move to the next item. You must complete all tests.
374 </string>
375 <string name="ble_secure_server_test_list_name">Bluetooth LE Secure Server Test</string>
376 <string name="ble_secure_server_test_list_info">
377 This test is mostly automated, but requires some user interaction.
378 You can pass this test once the list items below are checked.
379 \n\nTap \"01 Bluetooth LE Server Test\" on this device, then tap \"01 Bluetooth LE Client Test \"on other device.
380 \nTest completed, then test next item. You must be done all tests.
381 </string>
John Du73462362013-07-26 12:28:28 -0700382
Yicheng Fana6736922014-07-08 14:53:55 -0700383 <!-- BLE advertiser side strings -->
Satomi1dfcc1c2016-08-08 17:07:22 +0900384 <string name="ble_advertiser_test_name">Bluetooth LE Advertiser Test</string>
385 <string name="ble_advertiser_test_info">
386 The Bluetooth LE Advertiser Test and Scanner Test is a paired test.
387 \nTap \"Bluetooth LE Advertiser Test\" on this device. Once it is passed, tap \"Bluetooth LE Scanner Test\".
388 \nTap \"Bluetooth LE Scanner Test\" on this device. Once it is passed, tap \"Bluetooth LE Advertiser Test\".
389 </string>
Yicheng Fana6736922014-07-08 14:53:55 -0700390 <string name="ble_advertiser_service_name">Bluetooth LE Advertiser Handler Service</string>
Satomi1dfcc1c2016-08-08 17:07:22 +0900391 <string name="ble_privacy_mac_name">Bluetooth LE Privacy Mac</string>
392 <string name="ble_privacy_mac_info">Bluetooth LE Advertiser should advertise in non-repeating MAC address.</string>
393 <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 Bluetooth LE advertising.</string>
394 <string name="ble_power_level_name">Bluetooth LE Tx Power Level</string>
395 <string name="ble_power_level_info">Bluetooth LE Advertiser advertises in 4 different power levels. Scanner should receive them in different strength of Rssi, cannot receive weak signals beyond several feet.</string>
396 <string name="ble_advertiser_power_level_instruction">
397 Click start to start multi-advertising. Data packets are advertised in 4 different power levels.
398 You may receive a message that this device does not support multi-advertising.
399 If the advertiser does not advertise in 4 power levels, and you do not receive an error message,
400 you may not have stopped advertising in the previous test, or this device may not support 4 advertisers at the same time.
401 Try rebooting the device and running the test again to free those advertisers in use.
402 </string>
403 <string name="ble_advertiser_scan_filter_name">Bluetooth LE Hardware Scan Filter</string>
404 <string name="ble_advertiser_scan_filter_info">Bluetooth LE 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 -0700405 <string name="ble_advertiser_scannable">Scannable advertising</string>
Yicheng Fan994d1dd2014-09-24 16:02:35 -0700406 <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 -0700407 <string name="ble_advertiser_unscannable">Unscannble advertising</string>
Yicheng Fan994d1dd2014-09-24 16:02:35 -0700408 <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 -0700409 <string name="ble_advertiser_start">Start</string>
410 <string name="ble_advertiser_stop">Stop</string>
Yicheng Fana6736922014-07-08 14:53:55 -0700411
412 <!-- BLE scanner side strings -->
Satomi1dfcc1c2016-08-08 17:07:22 +0900413 <string name="ble_scanner_test_name">Bluetooth LE Scanner Test</string>
Yicheng Fana6736922014-07-08 14:53:55 -0700414 <string name="ble_scanner_service_name">Bluetooth LE Scanner Handler Service</string>
Satomi1dfcc1c2016-08-08 17:07:22 +0900415 <string name="ble_scanner_test_info">The Bluetooth LE 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 -0700416 <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 -0700417 <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 -0700418 <string name="ble_ultra_low">Ultra low</string>
419 <string name="ble_low">Low</string>
420 <string name="ble_medium">Medium</string>
421 <string name="ble_high">High</string>
Marco Nelissena8308402017-01-26 15:41:56 -0800422 <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 mac address.</string>
423 <string name="ble_scanner_scan_filter_name">BLE Hardware Scan Filter</string>
Yicheng Fancb7cbc62014-08-13 18:11:30 -0700424 <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 -0700425 <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 -0700426 <string name="ble_scan_with_filter">Scan with filter</string>
427 <string name="ble_scan_without_filter">Scan without filter</string>
Yicheng Fanc8882202014-11-10 12:10:10 -0800428 <string name="ble_scan_start">Start scan</string>
429 <string name="ble_scan_stop">Stop scan</string>
Yicheng Fana6736922014-07-08 14:53:55 -0700430
Satomi1dfcc1c2016-08-08 17:07:22 +0900431 <!-- BLE connection priority test strings -->
432 <string name="ble_client_connection_priority">Testing priority: </string>
433 <string name="ble_connection_priority_balanced">BALANCED</string>
434 <string name="ble_connection_priority_high">HIGH</string>
435 <string name="ble_connection_priority_low">LOW</string>
436 <string name="ble_server_connection_priority_result_passed">All test passed</string>
437 <string name="ble_server_connection_priority_result_failed">Test failed.</string>
438 <string name="ble_server_connection_priority_result_intervals">
439 Transfer interval time (msec):\nHIGH=%1$d\nBALANCED=%2$d\nLOW=%3$d\n\nRequirements:\n HIGH &lt;= BALANCED &lt;= LOW
440 </string>
441
442 <!-- BLE Test Name -->
443 <string name="ble_secure_client_test_name">Bluetooth LE Secure Client Test</string>
444 <string name="ble_insecure_client_test_name">Bluetooth LE Insecure Client Test</string>
445 <string name="ble_secure_server_test_name">Bluetooth LE Secure Server Test</string>
446 <string name="ble_insecure_server_test_name">Bluetooth LE Insecure Server Test</string>
447
448 <string name="ble_read_characteristic_nopermission_name">Bluetooth LE Read Characteristic Without Perrmission</string>
449 <string name="ble_write_characteristic_nopermission_name">Bluetooth LE Write Characteristic Without Permission</string>
450 <string name="ble_read_descriptor_nopermission_name">Bluetooth LE Read Descriptor Without Perrmission</string>
451 <string name="ble_write_descriptor_nopermission_name">Bluetooth LE Write Descriptor Without Permission</string>
452 <string name="ble_connection_priority_client_name">02 Bluetooth LE Connection Priority Client Test</string>
453 <string name="ble_connection_priority_client_info">Bluetooth LE Connection Priority Client send message in 3 different priority.</string>
454 <string name="ble_read_authenticated_characteristic_name">Bluetooth LE Read Encrypted Characteristic</string>
455 <string name="ble_write_authenticated_characteristic_name">Bluetooth LE Write Encrypted Characteristic</string>
456 <string name="ble_read_authenticated_descriptor_name">Bluetooth LE Read Encrypted Descriptor</string>
457 <string name="ble_write_authenticated_descriptor_name">Bluetooth LE Write Encrypted Descriptor</string>
458 <string name="ble_connection_priority_client_high">Bluetooth LE Send With CONNECTION_PRIORITY_HIGH</string>
459 <string name="ble_connection_priority_client_low">Bluetooth LE Send With CONNECTION_PRIORITY_LOW_POWER</string>
460 <string name="ble_connection_priority_client_balanced">Bluetooth LE Send With CONNECTION_PRIORITY_BALANCED</string>
461 <string name="ble_indicate_characteristic_name">Bluetooth LE Indicate Characteristic</string>
462 <string name="ble_encrypted_client_name">03 Bluetooth LE Encrypted Client Test</string>
463 <string name="ble_encrypted_client_info">Bluetooth LE Encrypted Client read/write on characteristic and descriptor need encrypted.</string>
464 <string name="ble_insecure_client_test_list_name">Bluetooth LE Insecure Client Test</string>
465 <string name="ble_insecure_client_test_list_info">
466 The Bluetooth LE test must be done simultaneously on two devices. This device is the client.
467 All tests listed here must be done without pairing. Tap \"Bluetooth LE Insecure Server Test\" on the other device.
468 \n\nTap \"01 Bluetooth LE Client Test\" on this device, then tap \"01 Bluetooth LE Server Test\" on the other device.
469 \nWhen the test is complete, move to the next item. You must complete all tests.
470 </string>
471 <string name="ble_secure_client_test_list_name">Bluetooth LE Secure Client Test</string>
472 <string name="ble_secure_client_test_list_info">
473 The Bluetooth LE test must be done simultaneously on two devices.
474 This device is the client. All tests listed here must be done with pairing.
475 \n\nTap \"01 Bluetooth LE Client Test\" on this device, then tap \"01 Bluetooth LE Server Test\" on the other device.
476 \nWhen the test is complete, move to the next item. You must complete all tests.
477 </string>
478 <string name="ble_encrypted_client_no_encrypted_characteristic">Error!\nThe Characteristics unencrypted.</string>
479 <string name="ble_encrypted_client_no_encrypted_descriptor">Error!\nThe Descriptor unencrypted.</string>
480 <string name="ble_encrypted_client_fail_write_encrypted_characteristic">It failed to write to Characteristic.</string>
481 <string name="ble_encrypted_client_fail_write_encrypted_descriptor">It failed to write to Descriptor.</string>
482 <string name="ble_encrypted_client_fail_read_encrypted_characteristic">It failed to read the Characteristic.</string>
483 <string name="ble_encrypted_client_fail_read_encrypted_descriptor">It failed to read the Descriptor.</string>
484 <string name="ble_secure_client_test_info">
485 The Bluetooth LE test must be done simultaneously on two devices. This device is the client.
486 All tests listed here must be done with pairing.
487 </string>
488
489 <string name="ble_bluetooth_disable_title">Bluetooth Disable!</string>
490 <string name="ble_bluetooth_disable_message">Please set bluetooth enable.</string>
491
492 <string name="ble_bluetooth_mismatch_title">Bluetooth pairing state is a mismatch!</string>
493 <string name="ble_bluetooth_mismatch_secure_message">
494 And even though it has already been trying to run a test of Secure, the device has not been paired.
495 \nGo setting mode, set Bluetooth to pair other device.
496 </string>
497 <string name="ble_bluetooth_mismatch_insecure_message">
498 And even though it has already been trying to run a test of Insecure, the device has already been paired.
499 \nGo setting mode, set Bluetooth to unpair other device.
500 </string>
501
502 <string name="ble_mtu_mismatch_message">MTU is not correct.(Request:%1$d, Actual:%2$d)</string>
503 <string name="ble_mtu_fail_message">MTU test: failed to receive data</string>
504
Brian Muramatsuaccc6842010-08-11 18:57:27 -0700505 <!-- Strings for FeatureSummaryActivity -->
Dan Morrill5df275b2010-08-11 12:19:19 -0700506 <string name="feature_summary">Hardware/Software Feature Summary</string>
Brian Muramatsu14e1cbb2010-09-13 18:33:39 -0700507 <string name="feature_summary_info">This is a test for...</string>
Dan Morrill5df275b2010-08-11 12:19:19 -0700508 <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string>
509 <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string>
510 <string name="fs_no_data">No data.</string>
Dan Morrill71351d82010-10-20 15:26:00 -0700511 <string name="fs_legend_good">standard feature reported by device</string>
512 <string name="fs_legend_indeterminate">optional feature not reported by device</string>
513 <string name="fs_legend_warning">non-standard feature reported by device</string>
514 <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string>
515
Dan Morrill5df275b2010-08-11 12:19:19 -0700516 <string name="empty"></string>
517
Raymond054a4412015-03-17 20:51:23 -0700518 <!-- Strings for HifiUltrasoundTestActivity -->
Raymondf15f8162015-05-19 11:58:43 -0700519 <string name="hifi_ultrasound_test">Hifi Ultrasound Microphone Test</string>
Raymond84218672015-05-13 11:58:12 -0700520 <string name="hifi_ultrasound_test_info">
Raymondf15f8162015-05-19 11:58:43 -0700521 This is a test for near-ultrasound (18500Hz - 20000Hz) microphone response.\n
Raymond84218672015-05-13 11:58:12 -0700522 This test requires two devices.\n</string>
523 <string name="hifi_ultrasound_test_play">PLAY</string>
Raymond054a4412015-03-17 20:51:23 -0700524 <string name="hifi_ultrasound_test_record">RECORD</string>
Raymond054a4412015-03-17 20:51:23 -0700525 <string name="hifi_ultrasound_test_plot">PLOT</string>
526 <string name="hifi_ultrasound_test_dismiss">DISMISS</string>
Raymondf15f8162015-05-19 11:58:43 -0700527 <string name="hifi_ultrasound_test_ok">OK</string>
Raymond054a4412015-03-17 20:51:23 -0700528 <string name="hifi_ultrasound_test_instruction1">
Raymondf15f8162015-05-19 11:58:43 -0700529 Open Hifi Ultrasound Microphone Test on the test device and the reference device.\n
530 Set the media volume of the reference device at 70% and hold it with one hand.\n
Raymond84218672015-05-13 11:58:12 -0700531 Hold the testing device with the other hand\n
532 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 -0700533 After the test, report result on the testing (recording) device.\n</string>
Raymond054a4412015-03-17 20:51:23 -0700534 <string name="hifi_ultrasound_test_pass">PASS</string>
535 <string name="hifi_ultrasound_test_fail">FAIL</string>
Raymond84218672015-05-13 11:58:12 -0700536 <string name="hifi_ultrasound_test_default_false_string">false</string>
Raymond84218672015-05-13 11:58:12 -0700537 <string name="hifi_ultrasound_test_mic_no_support">
538 Device does not support near-ultrasound recording.\n
Raymond236f9862015-10-26 13:59:46 -0700539 Please report PASS.\n</string>
Raymond84218672015-05-13 11:58:12 -0700540 <string name="hifi_ultrasound_test_spkr_no_support">
541 Device does not support near-ultrasound playback.\n
542 If this is your reference device, please use a different reference device.\n</string>
543
Raymondf15f8162015-05-19 11:58:43 -0700544 <string name="hifi_ultrasound_speaker_test">Hifi Ultrasound Speaker Test</string>
Raymond84218672015-05-13 11:58:12 -0700545 <string name="hifi_ultrasound_speaker_test_info">
Raymondf15f8162015-05-19 11:58:43 -0700546 This is a test for near-ultrasound (18500Hz - 20000Hz) speaker response.\n
Raymond84218672015-05-13 11:58:12 -0700547 This test requires two devices.\n</string>
548 <string name="hifi_ultrasound_speaker_test_instruction1">
Raymondf15f8162015-05-19 11:58:43 -0700549 Open Hifi Ultrasound Speaker Test on the test device and the reference device.\n
550 Set the media volume of the testing device at 70% and hold it with one hand.\n
Raymond84218672015-05-13 11:58:12 -0700551 Hold the reference device with the other hand\n
552 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 -0700553 After the test, report result on the testing (playback) device.\n</string>
Raymond84218672015-05-13 11:58:12 -0700554 <string name="hifi_ultrasound_speaker_test_mic_no_support">
555 Device does not support near-ultrasound recording.\n
556 If this is your reference device, please use a different reference device.\n</string>
557 <string name="hifi_ultrasound_speaker_test_spkr_no_support">
558 Device does not support near-ultrasound playback.\n
Raymond236f9862015-10-26 13:59:46 -0700559 Please report PASS.\n</string>
Raymondf15f8162015-05-19 11:58:43 -0700560 <string name="hifi_ultrasound_speaker_test_test_side">
561 Please wait for the result on the reference device then report here.</string>
562 <string name="hifi_ultrasound_speaker_test_reference_side">
563 Please report on the testing device.\n</string>
Raymond054a4412015-03-17 20:51:23 -0700564
Nick Pelly1fe08972012-05-14 17:35:58 -0700565 <!-- Strings for Location tests -->
566 <string name="location_gps_test">GPS Test</string>
567 <string name="location_gps_test_info">This test verifies basic GPS behavior
568 and callback scheduling.
569 Make sure the device has line of sight to GPS satellites
570 (for example, outside, or near a window)
571 and then press OK to run the automated tests.</string>
Zoltan Szatmary-Banbfdde072016-01-15 13:24:07 +0000572 <string name="location_listener_activity">Location listener</string>
Nick Pelly1fe08972012-05-14 17:35:58 -0700573
Sumit Kumare1046842016-03-31 16:09:09 -0700574 <!-- Strings for Location GNSS tests -->
Sumit Kumar73346082016-04-12 20:18:45 -0700575 <string name="location_gnss_constellation_type_test">GNSS Measurement Constellation Test</string>
Wyatt Rileyb7bd8e52016-08-10 13:23:55 -0700576 <string name="location_gnss_measure_no_location_test">GNSS Measurement Before Location Test</string>
Sumit Kumare1046842016-03-31 16:09:09 -0700577 <string name="location_gnss_reg_test">GNSS Measurement Registration Test</string>
578 <string name="location_gnss_value_test">GNSS Measurement Values Test</string>
579 <string name="location_gnss_nav_msg_test">GNSS Navigation Message Test</string>
Yu Liu2d25bb52016-10-24 17:53:09 -0700580 <string name="location_gnss_status_test">GNSS Status Test</string>
Sumit Kumare1046842016-03-31 16:09:09 -0700581 <string name="location_gnss_test_info">This test verifies basic GNSS behavior.
582 Make sure the device has line of sight to GNSS satellites
583 (for example, stationary on a windowsill. If needed, try again, outside, also with the
584 device stationary, and with at least some view of the sky.) and then press Next to run
585 the automated tests.</string>
Sumit Kumara2a00c32016-04-06 16:50:29 -0700586 <string name="location_gnss_test_retry_info">If this test fails, please make sure the device
587 has line of sight to GNSS satellites (for example, stationary on a windowsill. If needed,
588 try again, outside, also with the device stationary, with as much view of the sky as
589 possible.) </string>
Sumit Kumare1046842016-03-31 16:09:09 -0700590
Erik Kline4018b0b2015-11-30 10:22:47 +0900591 <!-- Strings for net.ConnectivityScreenOffTestActivity -->
592 <string name="network_screen_off_test">Network Connectivity Screen Off Test</string>
593 <string name="network_screen_off_test_instructions">
594 This test verifies that IPv6 network connectivity continues to work
595 when the screen is off.\n\n
596
597 1. Join a Wi-Fi network with IPv6 Internet access.\n
598 2. If the device has battery power, disconnect all power connectors.\n
599 3. Turn the screen off.\n
600 4. Wait until the screen turns on (it will take at least two minutes).\n
601 5. If necessary, unlock the device.\n
602 6. Please mark the test according to the result status indicated.\n
603 </string>
604 <string name="network_screen_off_test_start">Start</string>
605
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700606 <!-- Strings for NfcTestActivity -->
607 <string name="nfc_test">NFC Test</string>
608 <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with
609 NFC enabled to exchange messages. One device must be the candidate device running the
610 software build to be tested, while the other device must be an implementation already
611 known to be compatible.\n\nThe Tag Verification tests check that your
612 device can properly read and write to tags of different technologies. The MIFARE
613 Ultralight test is only applicable for devices that support it.
Martijn Coenen109d7622013-09-24 07:09:29 -0700614 \n\nThe Host-based card emulation tests check that your device has properly implemented
615 host-based card emulation.
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700616 </string>
617
618 <string name="nfc_not_enabled">NFC is not enabled!</string>
destradaa65c7cdb2013-10-28 16:36:12 -0700619 <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700620 button below to goto Settings and enable it.</string>
621 <string name="nfc_settings">NFC Settings</string>
622
Nick Pellya9631ce2011-10-31 14:18:46 -0700623 <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string>
624 <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled.
625 Click the button below to goto NFC Sharing Settings and enable it.</string>
626 <string name="ndef_push_settings">NFC Sharing Settings</string>
627
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700628 <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string>
629 <string name="nfc_ndef_push_sender">NDEF Push Sender</string>
630 <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string>
Martijn Coenenbe6dfed2015-06-11 14:52:13 +0200631 <string name="nfc_llcp_version_check">LLCP version check</string>
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700632
633 <string name="nfc_tag_verification">Tag Verification</string>
634 <string name="nfc_ndef">NDEF</string>
635 <string name="nfc_mifare_ultralight">MIFARE Ultralight</string>
636
637 <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on
638 another device and touch the devices back to back. The receiver should show a
639 dialog indicating it has successfully received the correct message!</string>
640 <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another
641 device running the \"CTS Verifier NDEF Receiver\"...</string>
642
643 <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on
644 another device and touch the devices back to back. The receiver should show a
645 dialog indicating it has successfully received the correct message!</string>
646 <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another
647 device running the \"CTS Verifier NDEF Sender\"...</string>
648 <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push
649 message.</string>
destradaa65c7cdb2013-10-28 16:36:12 -0700650 <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700651 message.</string>
652
Martijn Coenenbe6dfed2015-06-11 14:52:13 +0200653 <string name="nfc_llcp_version_check_info">This test requires two candidate devices
654 with NFC enabled to exchange P2P messages. Start the \"LLCP version check\" test on
655 the other candidate device also, and touch the devices back to back. This test
656 then verifies that the candidate device correctly advises the LLCP version as 1.2</string>
657 <string name="nfc_llcp_version_check_failure">The candidate devices does not report LLCP
658 version 1.2 or higher.</string>
659 <string name="nfc_llcp_version_check_success">The candidate device has a valid LLCP version.</string>
Brian Muramatsu984b78b2011-09-23 12:37:28 -0700660 <string name="nfc_tag_verifier">NFC Tag Verifier</string>
661 <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read
662 a tag of the chosen technology.</string>
663
664 <string name="nfc_scan_tag">Place device on a writable %s tag...</string>
665 <string name="nfc_write_tag_title">Writable tag discovered!</string>
666 <string name="nfc_write_tag_message">Press OK to write to this tag...</string>
667 <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string>
668 <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string>
669 <string name="nfc_no_tech">No tag technologies detected...</string>
670
671 <string name="nfc_writing_tag">Writing NFC tag...</string>
672 <string name="nfc_writing_tag_error">Error writing NFC tag...</string>
673 <string name="nfc_reading_tag">Reading NFC tag...</string>
674 <string name="nfc_reading_tag_error">Error reading NFC tag...</string>
675
676 <string name="nfc_result_success">Test passed!</string>
677 <string name="nfc_result_failure">Test failed!</string>
678
679 <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string>
680 <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string>
681
Martijn Coenen109d7622013-09-24 07:09:29 -0700682 <string name="nfc_hce">Host-based card emulation</string>
Martijn Coenen6fc35802016-02-02 12:06:30 +0100683 <string name="nfc_hce_f">Host-based Felica card emulation</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700684 <string name="nfc_hce_reader_tests">HCE reader tests</string>
Martijn Coenen6fc35802016-02-02 12:06:30 +0100685 <string name="nfc_hce_f_reader_tests">HCE Felica reader tests</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700686 <string name="nfc_hce_emulator_tests">HCE emulator tests</string>
Martijn Coenen6fc35802016-02-02 12:06:30 +0100687 <string name="nfc_hce_f_emulator_tests">HCE Felica emulator tests</string>
688 <string name="nfc_hce_f_emulator">HCE Felica emulator</string>
689 <string name="nfc_hce_f_reader">HCE Felica reader</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700690 <string name="nfc_hce_emulator_test_info">The host-based card emulation
691 tests require two devices to be completed. The HCE emulator tests are used
692 to actually test the host-based card emulation feature of the device-under-test. So the
693 device running the emulator tests must be the candidate device running the software
694 to be tested. \n\nFor each emulator test, there is a corresponding "reader test"
695 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS
Martijn Coenen0cf0c962014-02-28 14:22:15 -0800696 and makes sure the device-under-test implements card emulation correctly.</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700697 <string name="nfc_hce_reader_test_info">The host-based card emulation
698 tests require two devices to be completed. The HCE emulator tests are used
699 to actually test the host-based card emulation feature of the device-under-test. So the
700 device running the emulator tests must be the candidate device running the software
701 to be tested. \n\nFor each emulator test, there is a corresponding "reader test"
702 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS
703 and makes sure the device-under-test implements card emulation correctly.
704 </string>
Martijn Coenen0cf0c962014-02-28 14:22:15 -0800705 <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 -0700706 <string name="nfc_hce_please_wait">Please wait</string>
707 <string name="nfc_hce_setting_up">Setting up card emulation services...</string>
Martijn Coenenc94c0122013-10-21 14:44:54 -0700708
709 <string name="nfc_hce_default_route_emulator">Default route (Emulator)</string>
710 <string name="nfc_hce_default_route_reader">Default route (Reader)</string>
711 <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>
712
713 <string name="nfc_hce_protocol_params_emulator">Protocol parameters (Emulator)</string>
714 <string name="nfc_hce_protocol_params_reader">Protocol parameters (Reader)</string>
Martijn Coenen7294e322013-11-13 10:36:05 -0800715 <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 -0700716
Martijn Coenen109d7622013-09-24 07:09:29 -0700717 <string name="nfc_hce_single_payment_emulator">Single payment (Emulator)</string>
718 <string name="nfc_hce_single_payment_reader">Single payment (Reader)</string>
719
720 <string name="nfc_hce_dual_payment_emulator">Two payment services (Emulator)</string>
721 <string name="nfc_hce_dual_payment_reader">Two payment services (Reader)</string>
722
723 <string name="nfc_hce_change_default_emulator">Change default payment service (Emulator)</string>
724 <string name="nfc_hce_change_default_reader">Change default payment service (Reader)</string>
725
726 <string name="nfc_hce_tap_reader_title">Tap reader</string>
727 <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>
728
729 <string name="nfc_hce_single_non_payment_emulator">Single non-payment (Emulator)</string>
730 <string name="nfc_hce_single_non_payment_reader">Single non-payment (Reader)</string>
731
732 <string name="nfc_hce_dual_non_payment_emulator">Two non-payment services (Emulator)</string>
733 <string name="nfc_hce_dual_non_payment_reader">Two non-payment services (Reader)</string>
734
735 <string name="nfc_hce_conflicting_non_payment_emulator">Two conflicting non-payment services (Emulator)</string>
736 <string name="nfc_hce_conflicting_non_payment_reader">Two conflicting non-payment services (Reader)</string>
737
Martijn Coenene71e3742014-05-23 16:35:55 -0700738 <string name="nfc_hce_foreground_non_payment_emulator">Foreground override non-payment services (Emulator)</string>
739 <string name="nfc_hce_foreground_non_payment_reader">Foreground override non-payment services (Reader)</string>
740 <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>
741
742 <string name="nfc_hce_foreground_payment_emulator">Foreground override payment services (Emulator)</string>
743 <string name="nfc_hce_foreground_payment_reader">Foreground override payment services (Reader)</string>
744 <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>
Martijn Coenen1b0a2fd2016-03-02 11:42:10 +0100745 <string name="nfc_hce_change_favor_foreground">This test requires the \"Use default\" setting to be set to \"Except when another payment app is open\". Tap OK to go to Tap and Pay settings and make sure the \"Use default\" setting is set to \"Except when another payment app is open\".</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700746 <string name="nfc_hce_offhost_service_emulator">Off-host service (Emulator)</string>
747 <string name="nfc_hce_offhost_service_reader">Off-host service (Reader)</string>
748 <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>
749
750 <string name="nfc_hce_on_and_offhost_service_emulator">On and off-host services (Emulator)</string>
751 <string name="nfc_hce_on_and_offhost_service_reader">On and off-host services (Reader)</string>
752 <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>
753
754 <string name="nfc_hce_tap_test_emulator">50 successful taps test (Emulator)</string>
755 <string name="nfc_hce_tap_test_reader">50 successful taps test (Reader)</string>
756 <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>
757 <string name="nfc_hce_throughput_emulator">HCE throughput test (Emulator)</string>
758 <string name="nfc_hce_throughput_reader">HCE throughput test (Reader)</string>
759 <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 -0700760 <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 -0700761 <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>
762 <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 -0700763
764 <string name="nfc_hce_payment_dynamic_aids_emulator">Dynamic payment AIDs (Emulator)</string>
765 <string name="nfc_hce_payment_dynamic_aids_reader">Dynamic payment AIDs (Reader)</string>
766 <string name="nfc_hce_payment_dynamic_aids_help">This test tries to register dynamic AIDs for a payment service.</string>
767
Martijn Coenen7459cf22014-12-17 16:57:23 -0800768 <string name="nfc_hce_large_num_aids_emulator">Large number of AIDs (Emulator)</string>
769 <string name="nfc_hce_large_num_aids_reader">Large number of AIDs (Reader)</string>
770 <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>
771
Martijn Coenene71e3742014-05-23 16:35:55 -0700772 <string name="nfc_hce_payment_prefix_aids_emulator">Payment prefix AIDs (Emulator)</string>
773 <string name="nfc_hce_payment_prefix_aids_reader">Payment prefix AIDs (Reader)</string>
774 <string name="nfc_hce_payment_prefix_aids_help">This test statically registers prefix AIDs for a payment service.</string>
775
776 <string name="nfc_hce_payment_prefix_aids_emulator_2">Payment prefix AIDs 2 (Emulator)</string>
777 <string name="nfc_hce_payment_prefix_aids_reader_2">Payment prefix AIDs 2 (Reader)</string>
778
779 <string name="nfc_hce_other_prefix_aids_emulator">Other prefix AIDs (Emulator)</string>
780 <string name="nfc_hce_other_prefix_aids_reader">Other prefix AIDs (Reader)</string>
781 <string name="nfc_hce_other_prefix_aids_help">This test dynamically registers prefix AIDs for a non-payment service.</string>
782
783 <string name="nfc_hce_other_conflicting_prefix_aids_emulator">Conflicting non-payment prefix AIDs (Emulator)</string>
784 <string name="nfc_hce_other_conflicting_prefix_aids_reader">Conflicting non-payment prefix AIDs (Reader)</string>
785 <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>
786
Martijn Coenen109d7622013-09-24 07:09:29 -0700787 <string name="nfc_payment_service_desc">NFC Payment service</string>
788 <string name="ppse">PPSE</string>
789 <string name="mastercard">MasterCard</string>
Martijn Coenene71e3742014-05-23 16:35:55 -0700790 <string name="visa">Visa</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700791 <string name="paymentService1">Payment Service #1</string>
792 <string name="paymentService2">Payment Service #2</string>
793 <string name="transportService1">TransportService #1</string>
794 <string name="transportService2">TransportService #2</string>
795 <string name="accessService">AccessService</string>
796 <string name="offhostService">OffhostService</string>
Martijn Coenen6fc35802016-02-02 12:06:30 +0100797 <string name="felicaservice">Felica Service</string>
Martijn Coenen109d7622013-09-24 07:09:29 -0700798
destradaa65c7cdb2013-10-28 16:36:12 -0700799 <!-- Strings for Sensor Test Activities -->
destradaa0dcd7102014-09-23 14:22:54 -0700800 <string name="snsr_device_admin_receiver">Sensor Tests Device Admin Receiver</string>
destradaa9732fb12014-08-15 10:40:50 -0700801 <string name="snsr_test_summary">Tests passed: %1$d, Tests skipped: %2$d, Tests failed: %3$d</string>
destradaa2581a9e2014-09-26 13:25:19 -0700802 <string name="snsr_test_complete">Test completed without errors.</string>
Peng Xu7254e7d2016-12-16 00:59:37 -0800803 <string name="snsr_test_complete_with_errors">Test completed with errors which indicates
804 the device does not meet Android compatibility requirement.
805 This will degrade user experience and cause applications to misbehave.
806 To help debugging, please take a bug report and back up contents under
807 /sdcard/sensorTests of the device under test.
808 </string>
destradaa9732fb12014-08-15 10:40:50 -0700809 <string name="snsr_test_pass">PASS</string>
810 <string name="snsr_test_skipped">SKIPPED</string>
811 <string name="snsr_test_fail">FAIL</string>
destradaafd031b92014-10-10 10:45:51 -0700812 <string name="snsr_execution_time">Test execution time %1$s sec</string>
Peng Xu6133d242015-09-22 21:50:47 -0700813 <string name="snsr_rvcvxchk_test">Rotation Vector CV Crosscheck</string>
814 <string name="snsr_rvcvxchk_test_rec">Rotation Vector CV Recording</string>
destradaa9732fb12014-08-15 10:40:50 -0700815
816 <!-- Strings to interact with users in Sensor Tests -->
817 <string name="snsr_test_play_sound">A sound will be played once the verification is complete...</string>
destradaafc687ea2014-08-27 14:47:59 -0700818 <string name="snsr_no_interaction">Leave the device on top of a flat surface.</string>
819 <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 -0700820 <string name="snsr_device_steady">Keep the device steady.</string>
destradaafc687ea2014-08-27 14:47:59 -0700821 <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 -0700822 <string name="snsr_wait_for_user">Press \'Next\' to continue.</string>
destradaaa0b3bbc2014-09-03 14:08:00 -0700823 <string name="snsr_wait_to_begin">Press \'Next\' to begin.</string>
destradaa9732fb12014-08-15 10:40:50 -0700824 <string name="snsr_on_complete_return">After completing the task, go back to this test.</string>
destradaa139500e2014-08-22 16:01:52 -0700825 <string name="snsr_movement_expected">Movement was expected during the test. Found=%1$b.</string>
destradaaa26b12c2014-10-10 17:22:11 -0700826 <string name="snsr_sensor_feature_deactivation">Turn off any special features installed in the
827 device that register for sensors. Once you are done, you can begin the test.</string>
John Rusnak7ceff362014-08-04 15:49:51 -0700828 <string name="snsr_setting_mode_request">You will be redirected to set \'%1$s\' to: %2$s.</string>
829 <string name="snsr_setting_mode_set">\'%1$s\' set to: %2$s.</string>
830 <string name="snsr_setting_mode_not_set">\'%1$s\' not set to: %2$s.</string>
destradaa3dccf1f02014-08-22 18:11:36 -0700831 <string name="snsr_setting_airplane_mode">Airplane mode</string>
832 <string name="snsr_setting_screen_brightness_mode">Adaptive Brightness</string>
833 <string name="snsr_setting_auto_rotate_screen_mode">Auto-rotate screen</string>
destradaafc687ea2014-08-27 14:47:59 -0700834 <string name="snsr_setting_keep_screen_on">Stay awake</string>
destradaa3dccf1f02014-08-22 18:11:36 -0700835 <string name="snsr_setting_location_mode">Location</string>
destradaa4d4efc82014-10-17 14:50:37 -0700836 <string name="snsr_setting_ambient_display">Ambient Display</string>
destradaa2581a9e2014-09-26 13:25:19 -0700837 <string name="snsr_pass_on_error">Pass Anyway</string>
destradaa2d3dc7d2014-09-26 16:52:06 -0700838 <string name="snsr_run_automated_tests">The screen will be turned off to execute the tests,
839 when tests complete, the device will vibrate and the screen will be turned back on.</string>
destradaa9732fb12014-08-15 10:40:50 -0700840
destradaa65c7cdb2013-10-28 16:36:12 -0700841 <!-- Accelerometer -->
Dan Morrill5df275b2010-08-11 12:19:19 -0700842 <string name="snsr_accel_test">Accelerometer Test</string>
Dan Morrill71351d82010-10-20 15:26:00 -0700843 <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 -0700844 <string name="snsr_accel_m_test">Accelerometer Measurement Tests</string>
destradaa31f57432014-09-26 14:47:28 -0700845 <string name="snsr_accel_test_face_up">Place the device on a flat surface with the screen
846 facing the ceiling.</string>
847 <string name="snsr_accel_test_face_down">Place the device on a flat surface with the screen
848 facing it.</string>
destradaa16203b42014-09-29 13:26:51 -0700849 <string name="snsr_accel_test_right_side">Place the device in a flat surface resting vertically
850 on its right side.</string>
851 <string name="snsr_accel_test_left_side">Place the device in a flat surface resting vertically
852 on its left side.</string>
853 <string name="snsr_accel_test_top_side">Place the device in a flat surface resting vertically
854 on its top side.</string>
855 <string name="snsr_accel_test_bottom_side">Place the device in a flat surface resting vertically
856 on its bottom side.</string>
Brian Muramatsu729de482011-05-12 12:26:58 -0700857
destradaa65c7cdb2013-10-28 16:36:12 -0700858 <!-- Gyroscope -->
Brian Muramatsu729de482011-05-12 12:26:58 -0700859 <string name="snsr_gyro_test">Gyroscope Test</string>
860 <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>
861 <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string>
862 <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string>
863 <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>
864 <string name="snsr_gyro_test_degrees_title">Wrong units?</string>
865 <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 -0700866 <string name="snsr_gyro_m_test">Gyroscope Measurement Test</string>
destradaa9732fb12014-08-15 10:40:50 -0700867 <string name="snsr_gyro_device_placement">Place the device in a flat surface with the screen
destradaa31f57432014-09-26 14:47:28 -0700868 facing the ceiling. Read the instructions for each scenario, before you perform the
869 test.</string>
destradaa9732fb12014-08-15 10:40:50 -0700870 <string name="snsr_gyro_device_static">Leave the device static.</string>
destradaa31f57432014-09-26 14:47:28 -0700871 <string name="snsr_gyro_rotate_device">Once you begin the test, you will need to rotate the
872 device 360deg (one time) in the direction show by the animation, then place it back on the
873 flat surface.</string>
destradaa65c7cdb2013-10-28 16:36:12 -0700874
Vinod Krishnan20d67252014-04-30 11:12:01 -0700875 <!-- Heart Rate -->
876 <string name="snsr_heartrate_test">Heart Rate Test</string>
Vinod Krishnan7b6bdeb2014-05-13 16:19:44 -0700877 <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 -0700878 <string name="snsr_heartrate_test_no_heartrate_title">No heart rate monitor?</string>
879 <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>
880
destradaa65c7cdb2013-10-28 16:36:12 -0700881 <!-- Magnetic Field -->
882 <string name="snsr_mag_m_test">Magnetic Field Measurement Tests</string>
destradaa9732fb12014-08-15 10:40:50 -0700883 <string name="snsr_mag_verify_norm">Verifying the Norm...</string>
884 <string name="snsr_mag_verify_std_dev">Verifying the Standard Deviation...</string>
destradaa37286b42014-10-02 13:46:05 -0700885 <string name="snsr_mag_verify_calibrated_uncalibrated">Verifying the relationship between
886 calibrated and uncalibrated measurements...</string>
destradaa9732fb12014-08-15 10:40:50 -0700887 <string name="snsr_mag_calibration_description">Please calibrate the Magnetometer by moving
888 it in 8 shapes in different orientations.</string>
destradaa7bed8102014-09-24 13:18:16 -0700889 <string name="snsr_mag_calibration_complete">When done, leave the device in a flat surface, far
890 from all metallic objects (if the test does not pass, try re-running it outdoors).</string>
destradaa37286b42014-10-02 13:46:05 -0700891 <string name="snsr_mag_measurement">-&gt; (%1$.2f, %2$.2f, %3$.2f) : %4$.2f uT</string>
Brian Muramatsuaccc6842010-08-11 18:57:27 -0700892
Jim Steele0c4d08a2014-08-03 00:49:59 -0700893 <!-- Sensor Value Accuracy -->
Jim Steele0c4d08a2014-08-03 00:49:59 -0700894 <string name="snsr_rot_vec_test">Rotation Vector Accuracy Test</string>
destradaaa7714542014-09-04 16:23:03 -0700895 <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 -0700896 <string name="snsr_event_value">Sensor(%3$s). Event value[0] expected to be of value=%1$f. Found=%2$f.</string>
897 <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 -0700898
899 <!-- Sensor Batching -->
Peng Xu90f3f5c2016-12-15 20:43:56 -0800900 <string name="snsr_batch_test">Sensor Batching Manual Tests</string>
destradaa16203b42014-09-29 13:26:51 -0700901 <string name="snsr_batching_walking_needed">Once the test begins, you will have to take the
902 device in your hand and walk.</string>
Jim Steele0c4d08a2014-08-03 00:49:59 -0700903
904 <!-- Sensor Synchronization -->
905 <string name="snsr_synch_test">Sensor Synchronization Test</string>
906
Jim Steeleb292a9f2014-07-13 23:29:56 -0700907 <!-- Step Counter and Detector -->
908 <string name="snsr_step_counter_test">Step Counter and Detector Tests</string>
destradaa139500e2014-08-22 16:01:52 -0700909 <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 -0700910 <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 -0700911 <string name="snsr_step_counter_expected_steps">At least %1$d steps are expected to be reported. Reported=%2$d.</string>
912 <string name="snsr_step_counter_detected_reported">Steps reported by user=%1$d. Steps counted=%2$d. Delta=%3$d. Tolerance=%4$d.</string>
913 <string name="snsr_step_detector_detected_reported">Steps reported by user=%1$d. Steps detected=%2$d. Delta=%3$d. Tolerance=%4$d.</string>
914 <string name="snsr_step_counter_event_changed">Step counter expected to increase monotonically, with a delta > 0. Found=%1$d. Timestamp=%2$d.</string>
915 <string name="snsr_step_reported">%1$d | User reported step.</string>
916 <string name="snsr_step_counter_event">%1$d | Step Counter event. count=%2$d.</string>
917 <string name="snsr_step_detector_event">%1$d | Step Detector event.</string>
Jim Steeleb292a9f2014-07-13 23:29:56 -0700918
Aravind Akelladbc95c52015-06-09 10:22:16 -0700919 <!-- Device suspend tests -->
920 <string name="snsr_device_suspend_test">Device Suspend Tests</string>
921 <string name="snsr_device_did_not_go_into_suspend">Device did not go into suspend mode during test execution </string>
922 <string name="snsr_batch_did_not_arrive_at_expected_time">Batch did not arrive at the expected time estimatedBatchArrivalMs=%1$d
923 firstEventReceivedMs=%2$d diffMs=%3$d toleranceMs=%4$d </string>
924 <string name="snsr_device_suspend_test_instr">One you begin the test, disconnect USB, turn off the display and allow
925 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>
926
Jim Steelec57c8432014-05-24 09:53:32 -0700927 <!-- Significant Motion -->
928 <string name="snsr_significant_motion_test">Significant Motion Tests</string>
destradaaa7714542014-09-04 16:23:03 -0700929 <string name="snsr_significant_motion_event_arrival">Event expected to trigger. Triggered=%1$s.</string>
930 <string name="snsr_significant_motion_event_type">Event expected to be of type=%1$d. Found=%2$d.</string>
931 <string name="snsr_significant_motion_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string>
destradaaa07a7a22014-08-21 17:09:03 -0700932 <string name="snsr_significant_motion_disable_info">Significant Motion is expected to disable itself after it triggers once.</string>
933 <string name="snsr_significant_motion_test_trigger">Once you begin the test, you will need to walk for Significant Motion to be detected.</string>
934 <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>
935 <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>
936 <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>
937 <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>
938 <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 -0700939 <string name="snsr_significant_motion_registration">Expected to be able to register for TriggerSensor. Found=%1$b.</string>
destradaaa07a7a22014-08-21 17:09:03 -0700940 <string name="snsr_significant_motion_cancelation">Expected to be able to cancel TriggerSensor. Found=%b.</string>
Aravind Akelladbc95c52015-06-09 10:22:16 -0700941 <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.
942 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>
943 <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 -0700944
Nick Vaccarodf7b8e12017-01-18 17:14:27 -0800945 <!-- Low Latency Off-Body Detect -->
946 <string name="snsr_offbody_sensor_test">Off Body Sensor Tests</string>
947 <string name="snsr_offbody_sensor_registration">Registration failed for low latency offbody detect sensor.\n</string>
948 <string name="snsr_offbody_event_arrival">Expected to receive a low latency offbody detect event. Found=%b.</string>
949 <string name="snsr_offbody_event_type">Event expected to be of type=%1$d. Found=%2$d.</string>
950 <string name="snsr_offbody_event_invalid_value">Invalid value received for offbody state; Expected value %1$d or %2$d. Found=%2$d.</string>
951 <string name="snsr_offbody_event_wrong_value">Expected to receive an event having value=%1$d. Found=%2$d.</string>
952 <string name="snsr_offbody_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string>
953 <string name="snsr_offbody_response_timing_violation">%1$s event maximum allowed latency is %2$d. Found=%3$d ms.</string>
954 <string name="snsr_offbody_state_change">Offbody state changed to %1$d. Timestamp=%2$d.</string>
955 <string name="snsr_start_offbody_sensor_test_instr">Put watch on your wrist and then click Next button.</string>
956 <string name="snsr_start_onbody_sensor_test_instr">Remove the watch from your wrist and then click Next button.</string>
957 <string name="snsr_offbody_detect_test_instr">Click Next button, then immediate remove the watch from your wrist.</string>
958 <string name="snsr_onbody_detect_test_instr">Click Next button, then immediately attach the watch on your wrist.</string>
959 <string name="snsr_ap_wake_offbody_detect_test_instr">Click Next button, then palm the screen. Wait a few seconds after screen blackens, then remove watch from wrist.</string>
960
destradaaa0b3bbc2014-09-03 14:08:00 -0700961 <!-- Strings for Sensor CTS tests inside CtsVerifier -->
962 <string name="snsr_single_sensor_tests">CTS Single Sensor Tests</string>
963 <string name="snsr_sensor_integration_tests">CTS Sensor Integration Tests</string>
964 <string name="snsr_sensor_test">CTS Sensor Test</string>
destradaa774c0152014-09-15 17:00:37 -0700965 <string name="snsr_sensor_batching_tests">CTS Sensor Batching Tests</string>
destradaaa0b3bbc2014-09-03 14:08:00 -0700966
Peng Xuc4469cd2016-03-29 17:55:54 -0700967 <!-- String for DynamicSensorDiscoveryTest -->
968 <string name="snsr_dynamic_sensor_discovery_test">Dynamic Sensor Discovery Test</string>
969
Stuart Scottba898162014-01-17 13:18:14 -0800970 <!-- Strings for Sample Test Activities -->
971 <string name="share_button_text">Share</string>
972 <string name="sample_framework_test">Sample Framework Test</string>
973 <string name="sample_test">Sample Test</string>
974 <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>
975
James Painterfa2e1662012-09-13 15:37:58 -0700976 <!-- Strings for Camera Orientation -->
977 <string name="camera_orientation">Camera Orientation</string>
James Painter6cdb8682012-10-02 08:22:39 -0700978 <string name="co_info">This test verifies the orientation capabilities of
979 camera preview and capture.\n - The left view shows a preview window rotated
980 clockwise by a given magnitude of degrees.\n - The right view, after taking
981 a photo, shows the captured image.\n - For each camera and orientation, both
982 the left and right views should appear rotated clockwise by the amount of
983 degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose
984 \"Fail\".\n - For front-facing cameras, the test will horizontally mirror
985 the captured image prior to rotation, in attempt to make the left and right
986 views appear the same.\n - The physical orientation of the device does not
987 matter.\n - Read the message above the \"Take Photo\" button for
988 step-by-step instructions.
James Painter738030a2012-09-26 00:31:30 -0700989 </string>
James Painterfa2e1662012-09-13 15:37:58 -0700990 <string name="co_preview_label">Camera preview</string>
991 <string name="co_format_label">Oriented photo</string>
992 <string name="co_camera_label">Camera:</string>
993 <string name="co_orientation_label">Orientation</string>
James Painter738030a2012-09-26 00:31:30 -0700994 <string name="co_orientation_direction_label">clockwise</string>
James Painterfa2e1662012-09-13 15:37:58 -0700995 <string name="co_instruction_heading_label">Instruction:</string>
996 <string name="co_instruction_text_photo_label">Take a photo</string>
James Painter6cdb8682012-10-02 08:22:39 -0700997 <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>
998 <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 -0700999 <string name="co_photo_button_caption">Take Photo</string>
Eino-Ville Talvalae56ae2a2012-04-27 19:18:41 -07001000
Igor Murashkin48f86e72012-10-17 18:12:59 -07001001 <!-- Strings for Camera Intents -->
1002 <string name="camera_intents">Camera Intents</string>
1003 <string name="ci_info">
1004 This test verifies that the default camera app is firing intents
1005 after pictures/videos are taken. It also verifies that when the
1006 default camera app is invoked via intents, the launch intents work,
1007 and the broadcast intents are received when appropriate per the SDK
1008 documentation.\n\n
1009 - Read the message above the \"Start Test\" button for
1010 step-by-step instructions.
1011 </string>
1012 <string name="ci_preview_label">Camera preview</string>
1013 <string name="ci_format_label">Oriented photo</string>
1014 <string name="ci_camera_label">Camera:</string>
1015 <string name="ci_intents_label">Intents Test</string>
1016 <string name="ci_intents_direction_label">clockwise</string>
1017 <string name="ci_instruction_heading_label">Instructions:</string>
1018 <string name="ci_instruction_text_photo_label">READ BEFORE STARTING TEST</string>
1019 <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>
1020 <string name="ci_instruction_text_app_picture_label">\n
1021 1. Click Start Test. \n
1022 2. Go to home screen (HOME key). \n
1023 3. Launch Camera application. \n
Yin-Chia Yeha9dd8682016-05-04 17:49:14 -07001024 4. Capture photo within 1 minute. \n
Igor Murashkin48f86e72012-10-17 18:12:59 -07001025 5. Return to CTS verifier app. \n
Yin-Chia Yeha9dd8682016-05-04 17:49:14 -07001026 6. Pass button will light up if URI trigger was fired.\n
Igor Murashkin48f86e72012-10-17 18:12:59 -07001027 7. Click "Pass" if possible.
1028 </string>
1029 <string name="ci_instruction_text_app_video_label">\n
1030 1. Click Start Test. \n
1031 2. Go to home screen (HOME key). \n
1032 3. Launch Camera application. \n
Yin-Chia Yeha9dd8682016-05-04 17:49:14 -07001033 4. Capture video within 1 minute. \n
Igor Murashkin48f86e72012-10-17 18:12:59 -07001034 5. Return to CTS verifier app. \n
Yin-Chia Yeha9dd8682016-05-04 17:49:14 -07001035 6. Pass button will light up if URI trigger was fired.\n
Igor Murashkin48f86e72012-10-17 18:12:59 -07001036 7. Click "Pass" if possible.
1037 </string>
1038 <string name="ci_instruction_text_intent_picture_label">\n
1039 1. Click Start Test.\n
1040 2. Camera app will launch, prompting to take photo.\n
Yin-Chia Yeha9dd8682016-05-04 17:49:14 -07001041 3. Capture/confirm photo using camera app controls within 1 minute.\n
1042 4. Pass button will light up if URI trigger was NOT received.\n
Igor Murashkin48f86e72012-10-17 18:12:59 -07001043 5. Click "Pass" if possible.
1044 </string>
1045 <string name="ci_instruction_text_intent_video_label">\n
1046 1. Click Start Test.\n
1047 2. Camera app will launch, prompting to take video.\n
Yin-Chia Yeha9dd8682016-05-04 17:49:14 -07001048 3. Capture/confirm video using camera app controls within 1 minute.\n
1049 4. Pass button will light up if URI trigger was received.\n
Igor Murashkin48f86e72012-10-17 18:12:59 -07001050 5. Click "Pass" if possible.
1051 </string>
1052 <string name="ci_start_test_button_caption">Start Test</string>
1053
James Painterfa2e1662012-09-13 15:37:58 -07001054 <!-- Strings for Camera Formats -->
Eino-Ville Talvalae56ae2a2012-04-27 19:18:41 -07001055 <string name="camera_format">Camera Formats</string>
1056 <string name="cf_info">This test checks that all the supported
1057 output formats for camera preview callbacks work correctly, and
1058 that the mandatory formats are available. \n - The left view shows
1059 a standard preview window. \n - The right view shows the output
1060 processed from camera preview callbacks. \n - For each camera,
1061 resolution, and format combination in the dropdowns, the right
1062 view should look the same as the left, and neither should have
1063 streaks, lines, or other artifacts. \n - For front-facing cameras,
1064 the right view must be horizontally mirrored relative to the left
1065 view.\n - Note that the frame rate of the right view may be much
1066 lower than on the left; this is not an indication of a failed
1067 test.
1068 </string>
1069 <string name="cf_preview_label">Normal preview</string>
1070 <string name="cf_format_label">Processed callback data</string>
1071
Jianing Wei636f9032013-10-03 10:00:25 -07001072 <!-- Strings for Camera Video -->
1073 <string name="record_button_text">Test</string>
1074 <string name="camera_video">Camera Video</string>
1075 <string name="video_info"> This test checks video capture
1076 at different resolutions. \n - The left view window shows the preview.
1077 \n - Pressing the test button will trigger three
1078 seconds of video recording. Playback will show up in the right view
1079 window after recording is complete. \n - Use the spinners to choose
1080 camera and resolution combinations. The playback should be similar
1081 to what you saw in preview. \n - After all possible combinations
1082 are tested, the pass button will be enabled. You may press the pass
1083 button to indicate a pass. \n - You may press fail button any time during
1084 the test to indicate failure.
1085 </string>
1086 <string name="video_capture_label">Video capture</string>
1087 <string name="video_playback_label">Video playback</string>
1088 <string name="dialog_fail_test">Test failed</string>
1089 <string name="fail_quit">Fail and quit</string>
1090 <string name="cancel">Cancel</string>
1091 <string name="status_ready">Ready</string>
1092 <string name="status_recording">Recording</string>
1093 <string name="status_playback">Playing back</string>
1094
Brian Muramatsu12c86912011-07-21 17:26:46 -07001095 <!-- Strings for USB accessory test activity -->
1096 <string name="usb_accessory_test">USB Accessory Test</string>
1097 <string name="usb_accessory_test_info">
Philip P. Moltmann14e298e2016-11-01 15:49:36 -07001098 1. Install the Cts Verifier USB Companion app on a separate helper device.
1099 \n\n2. Start the accessory test companion in the Cts Verifier USB Companion.
1100 \n\n3. Connect the two devices. If using a OTG adapter make sure the adapter is directly connected to the helper device. If using an Type-C cable make sure that the helper device is set as "supply power to the attached device".
1101 \n\n4. Confirm access to the USB device on the helper device.
1102 \n\n5. Confirm access to the USB accessory on this device
1103 \n\n6. Confirm access to the USB device on the helper again.
1104 \n\n7. Test will run and complete automatically in a less than 30 seconds.
1105 \n\n8. Cancel all further dialogs on this device
Brian Muramatsu12c86912011-07-21 17:26:46 -07001106 </string>
Philip P. Moltmann14e298e2016-11-01 15:49:36 -07001107 <string name="usb_accessory_test_step1">
1108 In this specific order:
1109 \n1. Install the Cts Verifier USB Companion app on a separate helper device.
1110 \n2. Start the accessory test companion in the Cts Verifier USB Companion.
1111 \n3. Connect the two devices. If using a OTG adapter make sure the adapter is directly connected to the helper device. If using an Type-C cable make sure that the helper device is set as "supply power to the attached device".
1112 \n4. Confirm access to the USB device on the helper device. Only confirm once.
1113 \n5. Confirm access to the USB accessory on this device.
1114 \n6. Confirm access to the USB device on the helper device again.
1115 \n\nResult: A progress indicator should appear or test will finish.
1116 </string>
1117 <string name="usb_accessory_test_step2">
1118 Test is running and will complete automatically in less than 30 seconds.
1119 </string>
Brian Muramatsu12c86912011-07-21 17:26:46 -07001120
Philip P. Moltmanncdc09182016-09-16 17:49:25 -07001121 <!-- String for the USB device test activity -->
1122 <string name="usb_device_test">USB Device Test</string>
1123 <string name="usb_device_test_info">
1124 1. Install the Cts Verifier USB Companion app on a separate helper device.
1125 \n\n2. Start the device test companion in the Cts Verifier USB Companion.
Philip P. Moltmann6e047ae2016-09-22 16:16:24 -07001126 \n\n3. Connect the two devices. If using a OTG adapter make sure the adapter is directly connected to this device. If using an Type-C cable make sure that this device is set as "supply power to the attached device".
Philip P. Moltmanncdc09182016-09-16 17:49:25 -07001127 \n\n4. Confirm access to the USB device on this device.
Philip P. Moltmann14e298e2016-11-01 15:49:36 -07001128 \n\n5. Confirm access to the USB accessory on the helper device.
Philip P. Moltmanncdc09182016-09-16 17:49:25 -07001129 \n\n6. Confirm access to the USB device on this device again.
Jim Kaye12507db2016-11-07 11:24:54 -08001130 \n\n7. Test will run and complete automatically in less than 30 seconds.
Philip P. Moltmann14e298e2016-11-01 15:49:36 -07001131 \n\n8. Cancel all further dialogs on the helper device.
1132 </string>
1133 <string name="usb_device_test_step1">
1134 In this specific order:
1135 \n1. Install the Cts Verifier USB Companion app on a separate helper device.
1136 \n2. Start the device test companion in the Cts Verifier USB Companion.
1137 \n3. Connect the two devices. If using a OTG adapter make sure the adapter is directly connected to this device. If using an Type-C cable make sure that this device is set as "supply power to the attached device".
1138 \n\nResult: A dialog should show up on this device asking for access to a USB device.
1139 </string>
1140 <string name="usb_device_test_step2">
1141 Confirm access to the USB device on this device.
1142 \n\nResult: Dialogs should show up on this device and on the helper device asking for access to a USB device/accessory.
1143 </string>
1144 <string name="usb_device_test_step3">
1145 1. Confirm access to the USB accessory on the helper device.
1146 \n2. Confirm access to the USB device on this device again.
1147 \n\nResult: A progress indicator should appear or test will finish.
1148 </string>
1149 <string name="usb_device_test_step4">
1150 Test is running and will complete automatically in a less than 30 seconds.
Philip P. Moltmanncdc09182016-09-16 17:49:25 -07001151 </string>
Philip P. Moltmann6e047ae2016-09-22 16:16:24 -07001152 <string name="usb_device_unexpected">Usb companion device is not as expected %1$s. Please retry test.</string>
Philip P. Moltmanncdc09182016-09-16 17:49:25 -07001153
Daichi Hirono0ac59fc2016-04-11 03:36:27 +00001154 <!-- Strings for MTP host test activity -->
1155 <string name="mtp_host_test">MTP Host Test</string>
Daichi Hironoa16d4a42016-04-11 03:37:07 +00001156 <string name="mtp_host_test_info">The CTS-verifier tests the MTP host feature with another Android device. Please connect another Android device to this Android device by using OTG cable or USB type C cable, then follow the instructions on this screen. Note the test creates/deletes files in the connected Android device.</string>
1157 <string name="mtp_host_device_lookup_message">Connect MTP device.\nPlease connect another Android device to this device by using USB OTG cable or USB type C cable.\nOpen \"Use USB for\" dialog from the notification in the other Android device and choose \"File Transfer\" option.\nThen press the next button.</string>
1158 <string name="mtp_host_grant_permission_message">Grant permission.\nReply a dialog asking device permission.</string>
1159 <string name="mtp_host_test_read_event_message">Test MtpDevice#readEvent.\nTake a picture at the connected device.</string>
1160 <string name="mtp_host_test_send_object_message">Test MtpDevice#sendObject.</string>
1161 <string name="mtp_host_test_notification_message">Test MTP notification.\nCheck if there is an notification on this device saying the other MTP device is connected to this device. Also check if it opens the UI to browse files in the connected device by tapping the notification.</string>
Daichi Hirono0ac59fc2016-04-11 03:36:27 +00001162
Ruben Brunk370e2432014-10-14 18:33:23 -07001163 <!-- Strings for the Camera ITS test activity -->
1164 <string name="camera_its_test">Camera ITS Test</string>
1165 <string name="camera_its_test_info">
1166 1. Connect your Android device to a computer with adb installed via a USB cable.
1167 \n\n2. Setup the CameraITS test environment by following the setup instructions in the
1168 README file found in the CameraITS directory included in the CTS Verifier bundle
1169 (cd CameraITS; source build/envsetup.sh;).
1170 \n\n3. Setup the test scene described in the CameraITS README file, and aim the camera
1171 at it.
Yin-Chia Yeha2277d02014-10-20 15:50:23 -07001172 \n\n4. Run the full ITS test suite on all possible camera Ids.
Yin-Chia Yehab98ada2015-03-05 13:28:53 -08001173 (cd CameraITS; python tools/run_all_tests.py). Once all
Ruben Brunk370e2432014-10-14 18:33:23 -07001174 of the tests have been run, the \'PASS\' button will be enabled if all of the tests have
Yin-Chia Yehd6396fb2016-05-25 12:00:05 -07001175 succeeded. Please note that these tests can take more than 2 hours to run on some devices.
Ruben Brunk370e2432014-10-14 18:33:23 -07001176 </string>
1177 <string name="no_camera_manager">
1178 No camera manager exists! This test device is in a bad state.
1179 </string>
1180 <string name="all_legacy_devices">
Yin-Chia Yehfc60c4c2015-04-08 16:59:42 -07001181 All cameras on this device are LEGACY mode only - ITS tests are only required on LIMITED
1182 or better devices. Pass.
Ruben Brunk370e2432014-10-14 18:33:23 -07001183 </string>
1184 <string name="its_test_passed">All Camera ITS tests passed. Pass button enabled!</string>
1185 <string name="its_test_failed">Some Camera ITS tests failed.</string>
Yin-Chia Yeh02eeffb2016-08-16 15:28:03 -07001186 <string name="its_version_mismatch">
1187 CtsVerifier and ITS script version mismatch. Please update CtsVerifier and ITS script.
1188 </string>
1189 <string name="its_test_progress">ITS test progress will be shown here.</string>
Ruben Brunk370e2432014-10-14 18:33:23 -07001190
Chien-Yu Chen3e5b7202015-03-05 11:09:56 -08001191 <!-- Strings for the Camera Flashlight test activity -->
1192 <string name="camera_flashlight_test">Camera Flashlight</string>
1193 <string name="camera_flashlight_info">
1194 This test checks the flashlight functionality. It will turn on and off the flashlight of
1195 each camera device that has a flash unit. Follow the instructions on screen and observe the
1196 flashlight status changing.
1197 </string>
1198 <string name="camera_flashlight_start_button">Start</string>
1199 <string name="camera_flashlight_next_button">Next</string>
1200 <string name="camera_flashlight_done_button">Done</string>
1201 <string name="camera_flashlight_on_button">On</string>
1202 <string name="camera_flashlight_off_button">Off</string>
1203 <string name="camera_flashlight_start_text">Press Start to start flashlight test.</string>
1204 <string name="camera_flashlight_question_text">Is Camera %1$s flashlight on or off?</string>
1205 <string name="camera_flashlight_next_text">Ok. Press next.</string>
1206 <string name="camera_flashlight_failed_text">Test failed. Press Done or Fail button.</string>
1207 <string name="camera_flashlight_passed_text">All tests passed. Press Done or Pass button.
1208 </string>
1209
Jeff Davidson112f2792011-08-22 09:46:46 -07001210 <!-- Strings for StreamingVideoActivity -->
1211 <string name="streaming_video">Streaming Video Quality Verifier</string>
1212 <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>
1213 <string name="sv_no_data">No videos.</string>
1214 <string name="sv_failed_title">Test Failed</string>
1215 <string name="sv_failed_message">Unable to play stream. See log for details.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001216
1217 <!-- Strings for P2pTestActivity -->
1218 <string name="p2p_test">Wi-Fi Direct Test</string>
1219 <string name="p2p_test_info">
1220 The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange
1221 messages. One device must be the candidate device running the software build to
1222 be tested, while the other device must be an implementation already known to be
1223 compatible.\n\nOne device should start the requester test, and the other should
1224 start the responder test. Your device must pass both requester and responder
1225 tests.
1226 </string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001227 <string name="p2p_group_formation">Group Formation</string>
1228 <string name="p2p_join">Group Join</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001229 <string name="p2p_service_discovery">Service Discovery</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001230
1231 <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string>
1232 <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string>
1233 <string name="p2p_group_owner_test">Group Owner Test</string>
1234 <string name="p2p_group_client_test">Group Client Test</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001235 <string name="p2p_service_discovery_responder_test">
1236 Service Discovery Responder Test</string>
1237 <string name="p2p_service_discovery_requester_test">
1238 Service Discovery Requester Test</string>
1239
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001240 <string name="p2p_go_neg_responder">GO Negotiation Responder</string>
1241 <string name="p2p_go_neg_requester">GO Negotiation Requester</string>
1242 <string name="p2p_accept_client">Group Owner</string>
1243 <string name="p2p_join_go">Group Client</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001244 <string name="p2p_service_discovery_responder">Service Discovery Responder</string>
1245 <string name="p2p_service_discovery_requester">Service Discovery Requester</string>
1246
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001247 <string name="p2p_go_neg_responder_info">
Paul Stewart29ce53b2016-05-26 20:53:33 -07001248 Go to the Wi-Fi settings and forget all remembered networks. Then
1249 start the \"GO Negotiation Requester Test\" on the other device and follow
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001250 the instructions.</string>
1251 <string name="p2p_accept_client_info">
Paul Stewart29ce53b2016-05-26 20:53:33 -07001252 Go to the Wi-Fi settings and forget all remembered networks. Then
1253 start the \"Group Client Test\" on the other device and follow
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001254 the instructions.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001255 <string name="p2p_service_discovery_responder_info">
1256 Start the \"Service Discovery Requester Test\" on the other device and follow
1257 the instructions.</string>
1258
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001259 <string name="p2p_go_neg_requester_info">
Paul Stewart29ce53b2016-05-26 20:53:33 -07001260 Go to the Wi-Fi settings and forget all remembered networks. Then
1261 start the \"GO Negotiation Responder Test\" on the other device.
Jim Kaye12507db2016-11-07 11:24:54 -08001262 Then run each test individually by clicking on its name.</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001263 <string name="p2p_join_go_info">
Paul Stewart29ce53b2016-05-26 20:53:33 -07001264 Go to the Wi-Fi settings and forget all remembered networks. Then
1265 start the \"Group Owner Test\" on the other device.
Jim Kaye12507db2016-11-07 11:24:54 -08001266 Then run each test individually by clicking on its name.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001267 <string name="p2p_service_discovery_requester_info">
Paul Stewart29ce53b2016-05-26 20:53:33 -07001268 Go to the Wi-Fi settings and forget all remembered networks. Then
1269 start the \"Service Discovery Responder Test\" on the other device.
Jim Kaye12507db2016-11-07 11:24:54 -08001270 Then run each test individually by clicking on its name.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001271
1272 <string name="p2p_not_enabled">Wi-Fi is not enabled</string>
1273 <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled.
1274 Click the button below to go to system settings and enable Wi-Fi.</string>
1275 <string name="p2p_settings">Wi-Fi Direct Settings</string>
1276
1277 <string name="p2p_result_success">Test passed successfully.</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001278
1279 <string name="p2p_go_neg_responder_ready">
Paul Stewart29ce53b2016-05-26 20:53:33 -07001280 The go negotiation responder is now ready to start.
1281 Go to the Wi-Fi settings and forget all remembered networks. Then
1282 start the \"GO Negotiation Requester Test\" on the other device.
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001283 Keep the screen here until all tests on the other device are
1284 finished.</string>
1285 <string name="p2p_go_ready">
Paul Stewart29ce53b2016-05-26 20:53:33 -07001286 The group owner is now ready to start.
1287 Go to the Wi-Fi settings and forget all remembered networks. Then
1288 start the \"Join Group Test\" on the other device.
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001289 Keep the screen here until all tests on the other device are
1290 finished.</string>
1291 <string name="p2p_service_responder_ready">
Paul Stewart29ce53b2016-05-26 20:53:33 -07001292 The service responder is now ready to start.
1293 Go to the Wi-Fi settings and forget all remembered networks. Then
1294 start the \"Service Discovery Requester Test\" on the other device.
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001295 Keep the screen here until all tests on the other device are
1296 finished.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001297
1298 <string name="p2p_setup_error">
1299 Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string>
1300 <string name="p2p_unexpected_error">
1301 Test failed.\n\nUnexpected error. Check logcat.</string>
1302 <string name="p2p_add_local_service_error">
1303 Test failed.\n\nFailed to add local service.</string>
1304 <string name="p2p_add_service_request_error">
1305 Test failed.\n\nFailed to add service request.</string>
1306 <string name="p2p_remove_service_request_error">
1307 Test failed.\n\nFailed to remove service request.</string>
1308 <string name="p2p_clear_service_requests_error">
1309 Test failed.\n\nFailed to clear service requests.</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001310 <string name="p2p_connect_error">
1311 Test failed.\n\nFailed to start a p2p connection to the target device.</string>
1312 <string name="p2p_remove_group_error">
1313 Test failed.\n\nFailed to remove a p2p group.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001314 <string name="p2p_discover_peers_error">
1315 Test failed.\n\nFailed to discover peers.</string>
1316 <string name="p2p_discover_services_error">
1317 Test failed.\n\nFailed to discover services.</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001318 <string name="p2p_ceate_group_error">
1319 Test failed.\n\nFailed to start up group owner.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001320 <string name="p2p_no_service_requests_error">
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001321 Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001322 <string name="p2p_receive_invalid_response_error">
1323 Test failed.\n\nReceived an invalid message or could not receive
1324 the expected message.\n\n</string>
1325 <string name="p2p_target_not_found_error">Test failed.\n\n
1326 The target responder device was NOT found. Start up the responder
1327 test on the other device, then run the test again.</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001328 <string name="p2p_target_invalid_role_error">Test failed.\n\n
1329 The target responder must be p2p device. However, the target responder
1330 device was group owner. Check the test case on the other device.</string>
1331 <string name="p2p_target_invalid_role_error2">Test failed.\n\n
1332 The target responder must be group owner. However, the target responder
1333 device was p2p device. Check the test case on the other device.</string>
1334 <string name="p2p_connection_error">
1335 Test failed.\n\nFailed to establish a p2p connection.</string>
1336 <string name="p2p_detect_disconnection_error">
1337 Test failed.\n\nFailed to detect client disconnection.</string>
1338 <string name="p2p_disconnect_error">
1339 Test failed.\n\nFailed to disconnect a p2p connection.</string>
Yoshihiko Ikenagaf2bfc972012-04-11 22:45:03 +09001340
1341 <string name="p2p_search_target">Search Target</string>
1342 <string name="p2p_searching_target">Searching for target device ...</string>
Yoshihiko Ikenaga395214c2012-05-10 20:19:35 +09001343 <string name="p2p_checking_serv_capab">Checking the service discovery
1344 capability ...</string>
1345 <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n
1346 Click the \"OK\" button on the other device to accept the connection
1347 request from this device.</string>
1348 <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n
1349 Enter the pin number on the other device.</string>
1350 <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to
1351 connect ...</string>
1352 <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer
1353 to disconnect ...</string>
Angus Konga0216882013-03-06 17:51:11 -08001354
Etan Cohenc4f972a2017-03-15 15:57:35 -07001355 <!-- Strings for TestListActivity -->
1356 <string name="aware_test">Wi-Fi Aware Test</string>
1357 <string name="aware_test_info">
1358 The Wi-Fi Aware tests require two devices with Wi-Fi enabled. One device must
1359 be the candidate device running the software build to be tested, while the other
1360 device must be an implementation already known to be compatible.\n\nThere are
1361 tests for Publisher and Subscriber, Responder and Initiator. One device should
1362 start in a role, and the other should start in the complementary
1363 role. Your device must pass the tests in all roles.
1364 </string>
1365 <string name="aware_not_enabled">Wi-Fi is not enabled</string>
1366 <string name="aware_not_enabled_message">These tests require Wi-Fi to be enabled.
1367 Click the button below to go to system settings and enable Wi-Fi.</string>
1368 <string name="aware_settings">Wi-Fi Settings</string>
1369 <string name="aware_setup_error">
1370 Test failed.\n\nSet up error. Check whether Wi-Fi is enabled.</string>
1371 <string name="aware_unexpected_error">
1372 Test failed.\n\nUnexpected error. Check logcat.</string>
1373
1374 <string name="aware_dp_ib_open_unsolicited">Data Path: Open: Unsolicited/Passive</string>
1375 <string name="aware_publish">Publish</string>
1376 <string name="aware_subscribe">Subscribe</string>
1377
1378 <string name="aware_data_path_open_unsolicited_publish">Data Path: Open: Unsolicited Publish</string>
1379 <string name="aware_data_path_open_unsolicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: Open: Unsolicited/Passive\' / \'Subscribe\' test.</string>
1380 <string name="aware_data_path_open_passive_subscribe">Data Path: Open: Passive Subscribe</string>
1381
Angus Konga0216882013-03-06 17:51:11 -08001382 <string name="camera_fov_calibration">Camera FOV Calibration</string>
1383 <string name="camera_fov_calibration_done">Done</string>
1384 <string name="camera_fov_general_settings">General settings</string>
1385 <string name="camera_fov_label_options">Settings</string>
1386 <string name="camera_fov_tap_to_take_photo">Tap to calibrate</string>
1387 <string name="camera_fov_marker_distance">Marker distance (in cm)</string>
1388 <string name="camera_fov_marker_distance_description">The distance in centimeters between
1389 the solid lines on the target pattern.</string>
1390 <string name="camera_fov_target_distance">Target distance (in cm)</string>
1391 <string name="camera_fov_target_distance_description">The distance in centimeters from the
1392 device to the target pattern.</string>
1393 <string name="camera_fov_settings_button_text">Setup</string>
Sascha Haeberling28cb27c2013-05-03 18:19:07 -07001394 <string name="camera_fov_change_preview_sizes_button_text">Preview Sizes</string>
1395 <string name="camera_fov_choose_preview_size_for_camera">Choose preview size for camera %1$s</string>
Angus Konga0216882013-03-06 17:51:11 -08001396 <string name="camera_fov_displayed_fov_label">Displayed FOV : </string>
1397 <string name="camera_fov_reported_fov_label">Reported FOV : </string>
Sascha Haeberling117c60c2013-06-11 13:26:42 -07001398 <string name="camera_fov_reported_fov_problem">Reported FOV problem</string>
1399 <string name="camera_fov_reported_fov_problem_message">The reported FOV before takePicture() is
1400 different from when onPictureTaken() is called.\nAs picture size has not been changed, the
1401 reported FOV should be identical at both times.\n\nFOV before/after: %1$f / %2$f</string>
1402
Angus Konga0216882013-03-06 17:51:11 -08001403 <string name="camera_fov_panorama_wallpaper_title">Photo Sphere Live Wallpaper</string>
1404 <string name="camera_fov_panorama_wallpaper_description">This live wallapper displays photo
1405 spheres.</string>
1406 <string name="camera_fov_select_panorama">Select panorama</string>
1407 <string name="camera_fov_select_panorama_description">Select a panorama to display in the
1408 live wallpaper.</string>
1409 <string name="camera_fov_reset_panorama">Reset panorama</string>
1410 <string name="camera_fov_reset_panorama_description">Resets the panorama to show the demo
1411 file.</string>
1412 <string name="camera_fov_enable_compass_mode">Enable compass mode</string>
1413 <string name="camera_fov_enable_compass_mode_description">If enabled, the panorama orients
1414 itself according to the current rotation of the device.</string>
1415
Chris Wrenf102e542013-04-30 17:52:57 -04001416 <string name="test_category_notifications">Notifications</string>
Chris Wrenf9509802014-11-18 17:42:36 -05001417 <string name="package_priority_test">Notification Package Priority Test</string>
1418 <string name="package_priority_info">This test checks that the NotificationManagerService respects
1419 user preferences about relative package priorities.
1420 </string>
Chris Wren7b75fe22015-01-13 09:54:34 -05001421 <string name="package_priority_bot">Verifying that the CTS Robot helper package is installed.</string>
Chris Wren7dc9a9e2016-04-27 15:47:14 -04001422 <string name="package_priority_high">Find \"%s\" in the \"Notifications\" settings panel, and allow it to Override Do Not Disturb.</string>
1423 <string name="package_priority_default">Find \"%s\" in the \"Notifications\" settings panel, and disallow it to Override Do Not Disturb.</string>
Chris Wrenf9509802014-11-18 17:42:36 -05001424 <string name="package_priority_user_order">Check that ranker respects user priorities.</string>
1425
Makoto Onuki40510a92016-09-14 15:52:57 -07001426 <string name="shortcut_reset_test">Shortcut Reset Rate-limiting Test</string>
1427 <string name="shortcut_reset_info">This test checks that when an inline-reply happens, ShortcutManager\'s rate-limiting
1428 is reset.</string>
1429 <string name="shortcut_reset_bot">Verifying that the CTS Robot helper package is installed.</string>
1430 <string name="shortcut_reset_start">Showing the notification.</string>
1431 <string name="shortcut_reset_prompt_inline_reply">Open the notification shade,
1432 find the \"Shortcut Reset Rate-limiting Test\" notification, type something in the inline-reply field and
1433 press the send button.</string>
1434 <string name="shortcut_reset_check_result">Check ShortcutManager rate-limit has been reset.</string>
1435
Chris Wrenbcdef182014-09-22 17:56:38 -04001436 <string name="attention_test">Notification Attention Management Test</string>
1437 <string name="attention_info">This test checks that the NotificationManagerService is
1438 respecting user preferences about notification ranking and filtering.
1439 </string>
1440 <string name="attention_ready">I\'m done</string>
Chris Wrend12fd342015-08-03 17:16:36 -04001441 <string name="attention_filter_all">Please disable \"Do not disturb\" by tapping the Quick Settings tile.</string>
1442 <string name="attention_filter_priority">Please select \"Priority only\" in the dialog that appears
1443 when you tap the \"Do not disturb\" tile in Quick Settings, and customize the setting to allow messages from
1444 starred contacts only by tapping "More settings".</string>
1445 <string name="attention_filter_none">Please select \"Total silence\" in the dialog that appears
1446 when you tap the \"Do not disturb\" tile in Quick Settings.</string>
Chris Wrenbcdef182014-09-22 17:56:38 -04001447 <string name="attention_create_contacts">Create contacts for notification annotations.</string>
1448 <string name="attention_delete_contacts">Delete test contacts.</string>
1449 <string name="attention_default_order">Check that ranker defaults to time order.</string>
1450 <string name="attention_priority_order">Check that ranker respects developers priorities.</string>
1451 <string name="attention_ambient_bit">Check that the ambient bit is set appropriately.</string>
1452 <string name="attention_lookup_order">Check that ranker respects Lookup URIs for contacts.</string>
1453 <string name="attention_email_order">Check that ranker respects mailto URIs for contacts.</string>
1454 <string name="attention_phone_order">Check that ranker respects telephone URIs for contacts.</string>
1455 <string name="attention_interruption_order">Check that ranker temporarily boosts interruptions.
Chris Wren30c0ebd2016-04-28 10:15:37 -04001456 This test takes 30 seconds to complete.</string>
Chris Wrenbcdef182014-09-22 17:56:38 -04001457 <string name="attention_none_are_filtered">Check that \"All\" mode doesn\'t filter any notifications.</string>
1458 <string name="attention_some_are_filtered">Check that \"Priority\" mode doesn\'t filter priority notifications.</string>
1459 <string name="attention_all_are_filtered">Check that \"None\" mode filters all notifications.</string>
Chris Wrenf102e542013-04-30 17:52:57 -04001460 <string name="nls_test">Notification Listener Test</string>
Julia Reynolds236c28c2016-11-10 09:53:30 -05001461 <string name="nas_test">Notification Assistant Test</string>
Chris Wrenf102e542013-04-30 17:52:57 -04001462 <string name="nls_service_name">Notification Listener for CTS Verifier</string>
1463 <string name="nls_info">This test checks that a NotificationListenerService can be enabled
Chris Wrenbcdef182014-09-22 17:56:38 -04001464 and disabled, and that once enabled the service is able to receive notifications and
Chris Wrenf102e542013-04-30 17:52:57 -04001465 dismiss them.
1466 </string>
Julia Reynolds236c28c2016-11-10 09:53:30 -05001467 <string name="nas_service_name">Notification Assistant for CTS Verifier</string>
1468 <string name="nas_info">This test checks that a NotificationAssistantService can be enabled
1469 and disabled, and that once enabled the service is able to receive notifications and
1470 dismiss them.
1471 </string>
Shane Brennan7083e642017-03-14 11:02:25 -07001472 <string name="msg_extras_preserved">Check that Message extras Bundle was preserved.</string>
Ruben Brunk95a3ece2015-12-17 16:29:45 -08001473 <string name="vr_tests">VR Tests</string>
1474 <string name="test_category_vr">VR</string>
1475 <string name="vr_test_title">VR Listener Test</string>
1476 <string name="vr_service_name">VR Listener for CTS Verifier</string>
1477 <string name="vr_info">This test checks that a VrListenerService can be enabled and disabled, and
1478 and that it receives the correct lifecycle callbacks when entering and exiting VR mode.
1479 </string>
1480 <string name="vr_start_settings">Launch Settings</string>
1481 <string name="vr_start_vr_activity">Launch VR mode activity</string>
1482 <string name="vr_start_double_vr_activity">Launch Two VR mode activities</string>
1483 <string name="vr_start_vr_activity_desc">Click the button to launch the VR mode activity.</string>
1484 <string name="vr_start_vr_double_activity_desc">Click the button to launch two consecutive VR mode activities.</string>
1485 <string name="vr_check_disabled">Check that the CTS VR helper service is disabled by default.</string>
1486 <string name="vr_enable_service">Please enable \"VR Listener for CTS Verifier\"
1487 under Apps > Gear Icon > Special Access > VR Helper Services and return here.</string>
1488 <string name="vr_disable_service">Please disable \"VR Listener for CTS Verifier\"
1489 under Apps > Gear Icon > Special Access > VR Helper Services and return here.</string>
Julia Reynolds236c28c2016-11-10 09:53:30 -05001490 <string name="nas_enable_service">Please enable \"Notification Assistant for CTS Verifier\"
1491 under Apps > Gear Icon > Default > Notification Assistant and return here.</string>
1492 <string name="nas_disable_service">Please disable \"Notification Assistant for CTS Verifier\"
1493 under Apps > Gear Icon > Default > Notification Assistant and return here.</string>
destradaa65c7cdb2013-10-28 16:36:12 -07001494 <string name="nls_enable_service">Please enable \"Notification Listener for CTS Verifier\"
Chris Wren7dc9a9e2016-04-27 15:47:14 -04001495 under Apps > Gear Icon > Special Access > Notification Access and return here.</string>
destradaa65c7cdb2013-10-28 16:36:12 -07001496 <string name="nls_disable_service">Please disable \"Notification Listener for CTS Verifier\"
Chris Wren7dc9a9e2016-04-27 15:47:14 -04001497 under Apps > Gear Icon > Special Access > Notification Access and return here.</string>
Chris Wrenf102e542013-04-30 17:52:57 -04001498 <string name="nls_start_settings">Launch Settings</string>
1499 <string name="nls_service_started">Service should start once enabled.</string>
Julia Reynolds236c28c2016-11-10 09:53:30 -05001500 <string name="nas_note_enqueued_received">Check that notification was enqueued.</string>
Chris Wrenf102e542013-04-30 17:52:57 -04001501 <string name="nls_note_received">Check that notification was received.</string>
1502 <string name="nls_payload_intact">Check that notification payload was intact.</string>
Julia Reynolds63c27d42016-12-06 15:31:04 -05001503 <string name="nas_adjustment_payload_intact">Check that the Assistant can adjust notifications.</string>
Julia Reynolds8e952d32017-01-04 16:37:59 -05001504 <string name="nas_adjustment_enqueue_payload_intact">Check that the Assistant can adjust notifications on enqueue.</string>
Julia Reynolds85838db2016-12-09 15:36:48 -05001505 <string name="nas_create_channel">Check that the Assistant can create a Notification Channel for another app.</string>
1506 <string name="nas_update_channel">Check that the Assistant can update a Notification Channel for another app.</string>
Julia Reynolds58c08602016-12-16 15:56:53 -05001507 <string name="nas_block_channel">Check that the Assistant can block a Notification Channel.</string>
Julia Reynolds85838db2016-12-09 15:36:48 -05001508 <string name="nas_delete_channel">Check that the Assistant can delete a Notification Channel for another app.</string>
Julia Reynoldsadbbb822017-01-10 11:35:55 -05001509 <string name="nas_snooze_context">Check that the Assistant can snooze a notification until a given context.</string>
Chris Wrenf102e542013-04-30 17:52:57 -04001510 <string name="nls_clear_one">Check that service can clear a notification.</string>
Julia Reynolds236c28c2016-11-10 09:53:30 -05001511 <string name="nls_clear_one_reason">Check that service can clear a notification and receive the correct reason for dismissal.</string>
Chris Wrenf102e542013-04-30 17:52:57 -04001512 <string name="nls_clear_all">Check that service can clear all notifications.</string>
1513 <string name="nls_service_stopped">Service should stop once disabled.</string>
1514 <string name="nls_note_missed">Check that notification was not received.</string>
Julia Reynoldsd4096ac2016-11-22 09:28:09 -05001515 <string name="nls_snooze">Check the service can be snoozed.</string>
1516 <string name="nls_unsnooze">Check the service can be unsnoozed.</string>
1517 <string name="nls_hints">Check that the listener can set hints.</string>
1518 <string name="nls_snooze_one">Check that service can snooze a notification.</string>
1519 <string name="nls_snooze_one_time">Check that service can snooze a notification for a given time.</string>
Julia Reynoldsb24327d2017-01-24 15:52:28 -05001520 <string name="nls_get_snoozed">Check that service can retrieve snoozed notifications.</string>
Julia Reynoldsd4096ac2016-11-22 09:28:09 -05001521 <string name="nls_unsnooze_one">Check that service can unsnooze a notification.</string>
Julia Reynolds236c28c2016-11-10 09:53:30 -05001522 <string name="nas_note_missed_enqueued">Check that notification was not enqueued.</string>
Julia Reynoldsae110332015-11-02 15:19:15 -05001523 <string name="cp_test">Condition Provider test</string>
1524 <string name="cp_service_name">Condition Provider for CTS Verifier</string>
1525 <string name="cp_info">This test checks that a ConditionProviderService can be enabled
1526 and disabled, and that once enabled the service is able to create, query, edit, and delete
1527 automatic zen rules.
1528 </string>
1529 <string name="cp_enable_service">Please enable \"CTS Verifier\" under Do Not Disturb access and return here.</string>
1530 <string name="cp_disable_service">Please disable \"CTS Verifier\" under Do Not Disturb access and return here.</string>
1531 <string name="cp_start_settings">Launch Settings</string>
1532 <string name="cp_create_rule">Creating Automatic Zen Rule</string>
Julia Reynolds24d8f982016-06-24 09:30:16 -04001533 <string name="cp_update_rule">Updating Automatic Zen Rule</string>
Julia Reynoldsae110332015-11-02 15:19:15 -05001534 <string name="cp_subscribe_rule">Subscribing to Automatic Zen Rule</string>
1535 <string name="cp_service_started">Service should start once enabled.</string>
1536 <string name="cp_service_stopped">Service should stop once disabled.</string>
1537 <string name="cp_unsubscribe_rule">Unsubscribing to Automatic Zen Rule</string>
1538 <string name="cp_delete_rule">Deleting Automatic Zen Rule</string>
1539 <string name="cp_get_rules">Retrieving Automatic Zen Rules</string>
1540 <string name="cp_get_rule">Retrieving Automatic Zen Rule</string>
destradaa65c7cdb2013-10-28 16:36:12 -07001541
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001542 <string name="location_mode_high_accuracy_test">High Accuracy Mode Test</string>
1543 <string name="location_mode_high_accuracy_info">
1544 This test checks that the Location Mode API is consistent with the
1545 Location Provider API when the device is in High Accuracy location mode.
1546 </string>
1547 <string name="location_mode_select_high_accuracy">
Tom O'Neill45599512015-04-23 10:19:06 -07001548 Please select the \"High accuracy\" mode at Settings > Location
1549 (hint: tap the "Mode" item) and return here.
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001550 </string>
1551 <string name="location_mode_battery_saving_test">Battery Saving Mode Test</string>
1552 <string name="location_mode_battery_saving_info">
1553 This test checks that the Location Mode API is consistent with the
1554 Location Provider API when the device is in Battery Saving location mode.
1555 </string>
1556 <string name="location_mode_select_battery_saving">
Tom O'Neill45599512015-04-23 10:19:06 -07001557 Please select the \"Battery Saving\" mode at Settings > Location
1558 (hint: tap the "Mode" item) and return here.
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001559 </string>
Tom O'Neill9e56d272013-12-16 12:48:30 -08001560 <string name="location_mode_device_only_test">Device Only Mode Test</string>
1561 <string name="location_mode_device_only_info">
1562 This test checks that the Location Mode API is consistent with the
1563 Location Provider API when the device is in Device Only location mode.
1564 </string>
1565 <string name="location_mode_select_device_only">
1566 Please select the \"Device Only\" mode at
Tom O'Neill45599512015-04-23 10:19:06 -07001567 Settings > Location (hint: tap the "Mode" item) and return here.
Tom O'Neill9e56d272013-12-16 12:48:30 -08001568 </string>
1569 <string name="location_mode_off_test">Location Mode Off Test</string>
1570 <string name="location_mode_off_info">
1571 This test checks that the Location Mode API is consistent with the
1572 Location Provider API when the device is in the Off location mode.
1573 </string>
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001574
1575 <string name="location_mode_start_settings">Launch Settings</string>
1576 <string name="location_mode_turn_on">
Tom O'Neill9e56d272013-12-16 12:48:30 -08001577 Please turn ON location access (the switch at the top of Settings > Location)
1578 and return here.
1579 </string>
1580 <string name="location_mode_turn_off">
1581 Please turn OFF location access (the switch at the top of Settings > Location)
1582 and return here.
Tom O'Neillcd4fa022013-12-13 17:27:46 -08001583 </string>
1584 <string name="location_mode_secure_gps_on">GPS provider should be ON in secure settings.</string>
1585 <string name="location_mode_secure_gps_off">GPS provider should be OFF in secure settings.</string>
1586 <string name="location_mode_secure_nlp_on">Network location provider should be ON in secure settings.</string>
1587 <string name="location_mode_secure_nlp_off">Network location provider should be OFF in secure settings.</string>
1588 <string name="location_mode_manager_gps_on">GPS provider should be ON in LocationManager.</string>
1589 <string name="location_mode_manager_gps_off">GPS provider should be OFF in LocationManager.</string>
1590 <string name="location_mode_manager_nlp_on">Network location provider should be ON in LocationManager.</string>
1591 <string name="location_mode_manager_nlp_off">Network location provider should be OFF in LocationManager.</string>
1592
Maggie Benthall3278c022013-10-04 18:50:51 -04001593 <string name="cacert_test">CA Cert Notification Test</string>
1594 <string name="cacert_info">This test checks that when a CA Certificate is installed, the user is notified.</string>
1595 <string name="cacert_do_something">Do it</string>
1596 <string name="cacert_done">Done</string>
Robin Lee7dbe9de2016-05-18 11:44:54 +01001597 <string name="cacert_install_cert">Use the CertInstaller to install the certificate "MyCA.cer" from device storage. When it opens, choose any name and tap "Okay". If this button does nothing, pass the test and move on.</string>
Maggie Benthall3278c022013-10-04 18:50:51 -04001598 <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>
Robin Lee35476202016-05-03 09:39:04 +01001599 <string name="cacert_remove_screen_lock">You may have been prompted to set a screen lock when installing the certificate. If so, remove it. If not, you may skip this step.</string>
1600 <string name="cacert_check_notification">Look at the system notifications. Confirm that:\n
16011. There is a notification saying a certificate authority is installed.\n
16022. Tapping that notification brings up a more detailed explanation and a button to check trusted credentials.\n
16033. Tapping that button brings up the Trusted Credentials page you just visited.</string>
Robin Lee7dbe9de2016-05-18 11:44:54 +01001604 <string name="cacert_dismiss_notification">Open the notification and follow the link to remove CA certificates. If removing CA certificates does not dismiss the notification, fail the test.</string>
Maggie Benthall3278c022013-10-04 18:50:51 -04001605
1606 <string name="caboot_test">CA Cert Notification on Boot test</string>
1607 <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>
1608 <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>
1609 <string name="caboot_check_creds">Check Credentials</string>
1610 <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>
1611 <string name="caboot_install_cert">Install credential</string>
1612 <string name="caboot_reboot_desc">Please reboot the device and return to this test.</string>
1613 <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>
1614
Robin Leeb4be0a92015-06-15 19:13:00 -07001615 <!-- Strings for KeyChain -->
1616 <string name="keychain_test">KeyChain Storage Test</string>
1617 <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>
1618 <string name="keychain_reset">Reset</string>
1619 <string name="keychain_skip">Skip</string>
1620 <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
Kevin Ma346cdde2016-03-16 16:29:25 -07001621 Tap \'Next\' to begin.</string>
1622 <string name="keychain_install_desc">Credentials generated. Tap \'Next\' to install them to the system keychain.\n\n
Robin Leeb4be0a92015-06-15 19:13:00 -07001623The container for the credentials will not be protected with a password; if prompted for one, leave that field blank.\n\n
1624During installation you may be prompted for a name - accept the default suggestion.\n\n
1625In the case that these credentials were already installed, you may skip this step.</string>
1626 <string name="keychain_https_desc">The last test involves setting up an HTTPS connection using credentials from the KeyChain.\n\n
1627You should be prompted to select credentials; choose the ones you just installed in the previous step.</string>
Kevin Ma346cdde2016-03-16 16:29:25 -07001628 <string name="keychain_reset_desc">Before marking this test as passed, tap \'Next\' to open security settings and reset the following items:\n
Robin Leeb4be0a92015-06-15 19:13:00 -07001629 1. Clear device credentials.\n
1630 2. Change the lock screen type to \'None\'.</string>
1631
Adam Cohen8ae96702013-05-17 14:21:23 -07001632 <!-- Strings for Widget -->
1633 <string name="widget_framework_test">Widget Framework Test</string>
1634 <string name="widget_framework_test_info">This test checks some basic features of the widget
1635 framework. In order to perform the test, press the Home button. Add the widget
1636 titled "CTS Verifier" to the home screen. Follow the instructions in the widget.</string>
1637 <string name="widget_name">Widget Framework Test</string>
1638 <string name="widget_pass">Pass</string>
1639 <string name="widget_fail">Fail</string>
Alon Albert4106ff12013-10-01 12:36:02 -07001640
Robin Lee020f1852015-01-15 11:56:05 +00001641 <string name="provisioning_byod_nonmarket_allow">Enable non-market apps</string>
1642 <string name="provisioning_byod_nonmarket_allow_info">
1643 This test verifies that non-market apps can be installed if permitted.\n
1644 1. A package installation UI should appear.\n
Suprabh Shukla2b1e4b62017-03-22 18:38:06 -07001645 2. If \'Cts Verifier\' is not allowed to install apps, a warning dialog will appear
1646 blocking the install. In this case go to step 3, else skip to step 4.\n
1647 3. Allow \'Cts Verifier\' to install apps. Return to package installer.\n
1648 4. Accept the package and verify that it installs.
Robin Lee020f1852015-01-15 11:56:05 +00001649 </string>
1650
1651 <string name="provisioning_byod_nonmarket_deny">Disable non-market apps</string>
1652 <string name="provisioning_byod_nonmarket_deny_info">
1653 This test verifies that non-market apps cannot be installed unless permitted.\n
1654 1. A package installation UI should appear.\n
1655 2. Verify that the installation of the package is refused.
1656 </string>
1657
Sander Alewijnse7e24fda2015-03-26 17:41:57 +00001658 <string name="provisioning_byod_capture_image_support">Camera support cross profile image capture</string>
1659 <string name="provisioning_byod_capture_image_support_info">
1660 This test verifies that images can be captured from the managed profile using the primary profile camera.\n
1661 1. Capture a picture using the camera.\n
1662 2. Verify that the captured picture is shown.\n
1663 3. Click on the close button.
1664 </string>
Ricky Wai872e7a22016-03-04 10:35:09 +00001665 <string name="provisioning_byod_capture_video_support_with_extra_output">Camera support cross profile video capture (with extra output path)</string>
Sander Alewijnse7e24fda2015-03-26 17:41:57 +00001666 <string name="provisioning_byod_capture_video_support_info">
1667 This test verifies that videos can be captured from the managed profile using the primary profile camera.\n
1668 1. Capture a video using the camera.\n
1669 2. Click on the play button.\n
1670 3. Verify that the captured video is played.\n
1671 4. Click on the close button.
1672 </string>
Ricky Wai872e7a22016-03-04 10:35:09 +00001673 <string name="provisioning_byod_capture_video_support_without_extra_output">Camera support cross profile video capture (without extra output path)</string>
Sander Alewijnse7e24fda2015-03-26 17:41:57 +00001674 <string name="provisioning_byod_capture_audio_support">Sound recorder support cross profile audio capture</string>
1675 <string name="provisioning_byod_capture_audio_support_info">
1676 This test verifies that audio can be captured from the managed profile using the primary profile sound recorder.\n
1677 1. Capture audio.\n
1678 2. Click on the play button.\n
1679 3. Verify that the captured audio is played.\n
1680 4. Click on the close button.\n
1681 </string>
1682 <string name="provisioning_byod_dismiss_result_dialog">Close</string>
1683 <string name="provisioning_byod_play">Play</string>
1684 <string name="provisioning_byod_verify_image_title">Verify captured image</string>
1685 <string name="provisioning_byod_verify_video_title">Verify captured video</string>
1686 <string name="provisioning_byod_verify_audio_title">Verify captured audio</string>
1687 <string name="provisioning_byod_no_image_capture_resolver">No image capture app present. Skip test.</string>
1688 <string name="provisioning_byod_no_video_capture_resolver">No video capture app present. Skip test.</string>
1689 <string name="provisioning_byod_no_audio_capture_resolver">No audio capture app present. Skip test.</string>
1690 <string name="provisioning_byod_capture_media_error">Error while capturing media from managed profile.</string>
Daniel Xiea41d4972015-10-19 15:35:16 -07001691 <string name="provisioning_byod_capture_image_error">Error while capturing image from managed profile.</string>
Sander Alewijnse7e24fda2015-03-26 17:41:57 +00001692
Jim Kaye12507db2016-11-07 11:24:54 -08001693 <string name="provisioning_byod_auth_bound_key">Authentication-bound keys</string>
Daniel Xiea41d4972015-10-19 15:35:16 -07001694 <string name="provisioning_byod_auth_bound_key_info">
1695 This test verifies keystore cryptographic keys can be bound to device credentials.
1696 These keys should only be available if there was a recent enough authentication.
1697 </string>
1698 <string name="provisioning_byod_auth_bound_key_instruction">
1699 This test verifies keystore cryptographic keys can be bound to device lockscreen challenge or fingerprints (if available).
1700 These keys should only be available if there was a recent enough authentication. \n
1701
1702 1. Press "Set up" to open Security settings. Create a lockscreen password and if available, enroll a fingerprint.\n
1703 2. Go through the list of tests.\n
1704 3. Mark the overall test pass or fail.\n
1705 4. Once the set of tests are completed, remove the lockscreen challenge.
1706 </string>
1707 <string name="provisioning_byod_auth_bound_key_set_up">Set up</string>
1708 <string name="provisioning_byod_lockscreen_bound_key">Lockscreen-bound key test</string>
1709 <string name="provisioning_byod_fingerprint_bound_key">Fingerprint-bound key test</string>
Jim Kaye12507db2016-11-07 11:24:54 -08001710 <string name="provisioning_byod_vpn">VPN test</string>
Mahaver Choprae0611982016-05-03 10:53:33 +01001711 <string name="provisioning_byod_select_work_challenge">Select work lock test</string>
Benjamin Franzd3a27092016-01-22 14:02:36 +00001712 <string name="provisioning_byod_select_work_challenge_description">
Mahaver Choprae0611982016-05-03 10:53:33 +01001713 This test verifies that a work lock can be chosen.\n
Benjamin Franzd3a27092016-01-22 14:02:36 +00001714
Mahaver Choprae0611982016-05-03 10:53:33 +01001715 1. Verify that you get sent to the page for Choosing a new work lock.\n
1716 2. Set a new work lock.
Benjamin Franzd3a27092016-01-22 14:02:36 +00001717 </string>
Mahaver Choprae0611982016-05-03 10:53:33 +01001718 <string name="provisioning_byod_confirm_work_credentials">Confirm work lock test</string>
Benjamin Franzd3a27092016-01-22 14:02:36 +00001719 <string name="provisioning_byod_confirm_work_credentials_description">
Mahaver Choprae0611982016-05-03 10:53:33 +01001720 This test verifies that work lock is shown when opening a work app,
1721 the work lock was set correctly and it is customized according to
Mahaver Chopra8835de32016-04-20 13:32:00 +01001722 the policies set. You can only do this test after you have done the previous test.\n
Benjamin Franzd3a27092016-01-22 14:02:36 +00001723
Mahaver Chopra8835de32016-04-20 13:32:00 +01001724 1. Open a work app.\n
1725 2. Verify that a screen asking you for your work credentials is shown.\n
1726 3. Verify that the background image contains an orange suitcase.\n
1727 4. Verify that the background color of the remaining image is blue.\n
1728 5. Verify that the header text says \"CtsVerifier\".\n
1729 6. Confirm your credentials and verify that the credentials you entered previously work.
Benjamin Franzd3a27092016-01-22 14:02:36 +00001730 </string>
1731 <string name="provisioning_byod_confirm_work_credentials_header">
1732 CtsVerifier
1733 </string>
Robin Lee0bdfd142016-12-15 16:38:55 +00001734
1735 <string name="provisioning_byod_recents">Recents redaction test</string>
1736 <string name="provisioning_byod_recents_info">
1737 This test verifies that if a work profile is locked with a separate password, Recents views
1738 for applications in the work profile are redacted.
1739 </string>
1740 <string name="provisioning_byod_recents_instructions">
1741 This test verifies that if a work profile is locked with a separate password, Recents views
1742 for applications in the work profile are redacted.\n
1743 Some devices may not lock as soon as the screen is turned off by default. On such devices,
1744 use the button below when requested to lock the work profile.
1745 </string>
1746 <string name="provisioning_byod_recents_lock_now">Lock now</string>
1747
1748 <string name="provisioning_byod_recents_verify_redacted">
1749 Verify recents are redacted when locked.
1750 </string>
1751 <string name="provisioning_byod_recents_verify_redacted_instruction">
1752 1) Follow the instructions on-screen to set a work password.\n
1753 2) Turn the screen off and on again, or use the "lock now" button, to lock the work profile.\n
1754 3) Open Recents.\n
1755 4) Confirm that this "CTS Verifier" activity is shown in Recents.\n
1756 5) Confirm that the contents of the activity <b>are</b> hidden.\n
1757 6) Return to this page and pass the test.
1758 </string>
1759 <string name="provisioning_byod_recents_verify_not_redacted">
1760 Verify recents are not redacted when unlocked.
1761 </string>
1762 <string name="provisioning_byod_recents_verify_not_redacted_instruction">
1763 1) Follow the instructions on-screen to remove the work password.\n
1764 2) Open Recents.\n
1765 3) Confirm that this "CTS Verifier" activity is shown in Recents.\n
1766 4) Confirm that the contents of the activity <b>are not</b> hidden.\n
1767 5) Return to this page and pass the test.
1768 </string>
1769 <string name="provisioning_byod_recents_remove_password">
1770 The work profile still has a separate password. Please remove this before continuing.
1771 </string>
1772
Alon Albert4106ff12013-10-01 12:36:02 -07001773 <!-- Strings for DeskClock -->
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001774 <string name="deskclock_tests">Alarms and Timers Tests</string>
Alon Albert4106ff12013-10-01 12:36:02 -07001775 <string name="deskclock_tests_info">
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001776 The Alarms and Timers tests verify that the Clock app implements the AlarmClock API properly.
Alon Albert4106ff12013-10-01 12:36:02 -07001777 </string>
1778 <string name="deskclock_group_alarms">Alarms</string>
1779 <string name="deskclock_group_timers">Timers</string>
1780
1781 <string name="dc_show_alarms_test">Show Alarms Test</string>
1782 <string name="dc_show_alarms_test_info">
1783 This test verifies that the SHOW_ALARMS API works.\n
1784 1. Press the "Show Alarms" button.\n
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001785 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 -07001786 </string>
1787 <string name="dc_show_alarms_button">Show Alarms</string>
1788
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001789 <string name="dc_set_alarm_with_ui_test">Set Alarm Test</string>
1790 <string name="dc_set_alarm_with_ui_test_info">
1791 This test verifies that the ACTION_SET_ALARM with no parameters API works.\n
1792 1. Press the "Set Alarm" button.\n
1793 2. Verify that the clock app is launched and displays a UI to manage alarms.\n
1794 </string>
1795 <string name="dc_set_alarm_button">Set Alarm</string>
1796 <string name="dc_set_alarm_verify_button">Verify</string>
Alon Albert4106ff12013-10-01 12:36:02 -07001797
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001798 <string name="dc_start_alarm_test">Start Alarm Test</string>
1799 <string name="dc_start_alarm_test_info">
1800 This test verifies that the ACTION_SET_ALARM API actually starts an alarm.\n
1801 1. Press the "Start Alarm" button.\n
1802 2. Make sure the alarms UI is NOT shown\n
1803 3. Wait for the alarm to fire (may take up to 2 minutes)\n
1804 4. Verify that the alarm title is: "Start Alarm Test",\n
1805 the alarm is silent and vibrating (if the device supports vibrate).\n
1806 5. Dismiss the alarm.\n
1807 6. Verify that the alarm is not in the Clock\'s alarms list. The Verify button opens
1808 the alarm view.\n
1809 </string>
1810 <string name="dc_start_alarm_button">Start Alarm</string>
1811
1812 <string name="dc_full_alarm_test">Full Alarm Test</string>
1813 <string name="dc_full_alarm_test_info">
1814 This test verifies that the ACTION_SET_ALARM API supports all extras.\n
1815 1. Press the "Create Alarm" button.\n
1816 2. Verify that you see one alarm with the following information:\n
1817 Name of alarm: Create Alarm Test. \n
Justin Klaassen0d059db2015-12-02 14:52:33 -08001818 Vibrate: on. (if the device supports vibrate).\n
1819 Ringtone: silent. (if the device has a speaker).\n
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001820 Time: 01:23. \n
1821 Repeating on: Monday and Wednesday. \n
1822 </string>
1823 <string name="dc_full_alarm_button">Create Alarm</string>
destradaa65c7cdb2013-10-28 16:36:12 -07001824
Isaac Katzenelsond96d0662013-10-02 17:06:28 -07001825 <string name="dc_set_timer_with_ui_test">Set Timer Test</string>
1826 <string name="dc_set_timer_with_ui_test_info">
1827 This test verifies that the ACTION_SET_TIMER API with no paramters open the UI\n
1828 1. Press the "Set Timer" button.\n
1829 2. Verify that the an app is launched and displays a UI to manage timers.\n
1830 </string>
1831 <string name="dc_set_timer_with_ui_button">Set Timer</string>
1832
1833 <string name="dc_start_timer_test">Start Timer Test</string>
1834 <string name="dc_start_timer_test_info">
1835 This test verifies that the ACTION_SET_TIMER API actually starts a timer\n
1836 1. Press the "Start Timer" button.\n
1837 2. Verify that a timer is started and NO timers UI is shown.\n
1838 3. Verify that the timer named "Start Timer Test" rings after 30 seconds. Dismiss it.\n
1839 4. Verify that the timer is deleted after the dismissal.\n
1840 </string>
1841 <string name="dc_start_timer_button">Start Timer</string>
1842
1843 <string name="dc_start_timer_with_ui_test">Start Timer With UI Test</string>
1844 <string name="dc_start_timer_with_ui_test_info">
1845 This test verifies that the ACTION_SET_TIMER API actually starts a timer with UI\n
1846 1. Press the "Start Timer" button.\n
1847 2. Verify that a timer is started and the timers UI is shown with a timer named "Start Timer Test".\n
1848 3. Verify that the timer rings after 30 seconds.\n
1849 </string>
Amith Yamasani0e2d6d92014-02-19 10:13:23 -08001850 <!-- Strings for LockConfirmBypassTest -->
1851 <string name="lock_confirm_test_title">Keyguard Password Verification</string>
1852 <string name="lock_set_button_text">Set password</string>
1853 <string name="lock_change_button_text">Change password</string>
1854 <string name="lock_confirm_message">
1855 This test verifies that the user is prompted for the current keyguard password before prompting for a new password.\n
1856 \nClick the \"Set password\" button if you currently don\'t have a password set.\n
1857 \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.
1858 </string>
1859
Harsh Modife5933d2014-08-12 16:52:16 -07001860 <!-- String for Projection Tests -->
1861 <string name="test_category_projection">Projection Tests</string>
1862 <string name="projection_service_name">Projection Service</string>
1863 <string name="pca_info">This tests whether or not OpenGL projection works.\n
Jim Kaye144105e2016-11-07 11:24:54 -08001864 You should see two "tumbling cubes." Tapping the screen should cause the cubes to explode.</string>
Harsh Modife5933d2014-08-12 16:52:16 -07001865 <string name="pca_test">Projection Cube Test</string>
1866 <string name="pwa_info">This tests whether or displaying widets and keyfocus navigation works.\n
1867 You should see four buttons on the bottom of the screen.\n
1868 Pressing the "up" and "down" buttons should highlight different buttons.\n
David Stevens1d7230b2016-05-02 17:35:37 -07001869 Furthermore, the highlight should disappear when any button is touched, and the touched button should behave as usual.\n</string>
Harsh Modife5933d2014-08-12 16:52:16 -07001870 <string name="pwa_test">Projection Widget Test</string>
1871 <string name="pwa_button_up">Up</string>
1872 <string name="pwa_button_down">Down</string>
Harsh Modife5933d2014-08-12 16:52:16 -07001873 <string name="pwa_button">Button</string>
1874 <string name="pla_test">Projection Scrolling List Test</string>
1875 <string name="pla_info">This tests whether a projected list view will scroll properly\n
1876 You should see 50 list items and be able to scroll up and down the list</string>
1877 <string name="pva_test">Projection Video Playback Test</string>
1878 <string name="pva_info">This tests whether video playback works when projected.\n
1879 You should see a blinking white box and here a beep that is synchronized with each blink</string>
1880 <string name="pta_test">Projection Multitouch Test</string>
1881 <string name="pta_info">This tests whether multitouch works.\n
1882 Touching the screen should render a dot at the location you touched.\n
1883 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 -07001884 <string name="poa_test">Projection Offscreen Activity</string>
1885 <string name="poa_info">This tests whether a virtual display will continue to respond to and render even when the screen is off.\n
1886 Simply follow the instructions and the test will detect the pass conditions.\n
1887 Note that turning on the screen too early will result in a failure.</string>
Harsh Modife5933d2014-08-12 16:52:16 -07001888
Jim Steele0c4d08a2014-08-03 00:49:59 -07001889 <!-- Strings for RotationVectorTest and GameRotationVectorTest -->
1890 <string name="rotation_vector_test">Rotation Vector Accuracy Test</string>
destradaa58e36812014-08-20 14:53:21 -07001891 <string name="snsr_rotation_vector_set_reference">
1892 Place the mobile device in a reference position. Note: to provide an accurate reference,
1893 align the device along one edge of a notebook laying on a table.</string>
1894 <string name="snsr_rotation_vector_reference_set">Reference position set.</string>
1895 <string name="snsr_rotation_vector_move_info">Move, shake, and rotate the device.</string>
1896 <string name="snsr_rotation_vector_set_final">Place the device back to the reference position.</string>
1897 <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>
1898
Ahmet Kerim SENOL9fa97c22015-10-12 15:29:11 +01001899 <!-- Strings for device admin tests -->
1900 <string name="device_admin_notification">This is device admin notification</string>
1901 <string name="device_admin_keyguard_disable_camera">Disable camera</string>
1902 <string name="device_admin_keyguard_disable_camera_instruction">
1903 Please press the Go button to lock the screen. Then try to open the camera
1904 from the lower right corner of the screen. Expected result is you cannot
1905 open the camera from lock screen and it will ask for password instead.
1906 </string>
1907 <string name="device_admin_disable_notifications">Disable notifications</string>
1908 <string name="device_admin_disable_notifications_instruction">
1909 Please press the Go button to lock the screen. Wait a few seconds to see
1910 if a notification appears. Expected result is no notifications appear.
1911 You should be able to see one after unlocking.
1912 </string>
1913 <string name="device_admin_disable_unredacted_notifications">Disable unredacted notifications</string>
1914 <string name="device_admin_disable_unredacted_notifications_instruction">
1915 Please press the Go button to lock the screen. Wait a few seconds to see
1916 if a notification appears. Expected result is a notification appear with
1917 its content hidden. You should be able to see the content after unlocking.
1918 </string>
1919
Zoltan Szatmary-Ban9a2b13e2015-06-15 17:05:04 +01001920 <!-- Strings common for BYOD and DO managed provisioning tests. -->
Ahmet Kerim SENOL9fa97c22015-10-12 15:29:11 +01001921 <string name="afw_device_admin">CTS Verifier</string>
Zoltan Szatmary-Ban9a2b13e2015-06-15 17:05:04 +01001922
Nicolas Prevot695fc612015-12-10 17:54:32 +00001923 <string name="provisioning_tests_byod">BYOD Provisioning tests</string>
1924
1925 <string name="provisioning_tests_byod_custom_color"> Custom provisioning color </string>
1926 <string name="provisioning_tests_byod_custom_color_info">
1927 Please press the Go button to start the provisioning.
Victor Changcdb425d2017-01-23 17:15:11 +00001928 Check that the top status bar and "Accept and continue" button are colorized in green.
Nicolas Prevot695fc612015-12-10 17:54:32 +00001929 Then hit back and stop the provisioning.
1930 </string>
Nicolas Prevotb18f8572016-01-04 13:16:20 +00001931 <string name="provisioning_tests_byod_custom_image"> Custom provisioning image </string>
1932 <string name="provisioning_tests_byod_custom_image_info">
Victor Chang4ffa4b52017-01-25 17:59:25 +00001933 1. Please press the Go button to start the provisioning.\n
1934 2. Press \"Accept and continue\" button to start work profile provisioning\n
1935 3. Check that the CtsVerifier logo is displayed during provisioning\n
1936 4. After successful provisioning, you should be automatically redirected back to this page
Nicolas Prevotb18f8572016-01-04 13:16:20 +00001937 </string>
Victor Chang93e13192017-01-23 18:21:17 +00001938 <string name="provisioning_tests_byod_custom_terms">Custom terms</string>
1939 <string name="provisioning_tests_byod_custom_terms_instructions">
1940 1. Please press the Go button to start the provisioning.\n
1941 2. Click \"View Terms\" button\n
1942 3. Expand \"Company ABC\" section. Verify the section content is \"Company Terms Content.\"\n
1943 4. Then hit back twice and stop the provisioning.
1944 </string>
1945 <string name="provisioning_tests_byod_custom_term_header1">Company ABC</string>
Nicolas Prevot695fc612015-12-10 17:54:32 +00001946
1947 <!-- Strings for BYOD managed provisioning (ByodFlowTestActivity) -->
Rubin Xu55d22d42014-09-24 19:56:58 +01001948 <string name="test_category_managed_provisioning">Managed Provisioning</string>
Rubin Xu55d22d42014-09-24 19:56:58 +01001949 <string name="provisioning_byod">BYOD Managed Provisioning</string>
1950 <string name="provisioning_byod_info">
1951 This test exercises the BYOD managed provisioning flow.
1952 Start by pressing the button on screen and follow instructions to finish the managed provisioning process.
1953 If your device has not been encrypted before, it will be encrypted and rebooted.
1954 After the provisioning process completes, return to this page and carry out further verifications.
Rubin Xu1dcb3e32014-12-16 16:36:13 +00001955 Note: the device will remain encrypted after the test which can only be disabled by factory reset.
Rubin Xu55d22d42014-09-24 19:56:58 +01001956 </string>
1957 <string name="provisioning_byod_start">Start BYOD provisioning flow</string>
1958 <string name="provisioning_byod_instructions">
1959 1. Press the button below to start the managed provisioning flow.
1960 If your device has not been encrypted before, it will reboot to apply encryption.
1961 After reboot follow instructions in the notification area to complete the provisioning.\n
1962 2. After successful provisioning, you should be automatically redirected back to this page.
1963 Please press through the following verification steps.
Rubin Xu1dcb3e32014-12-16 16:36:13 +00001964 Allow a few seconds after returning from provisioning, as the profile owner test should automatically pass.\n
1965 \n
1966 If the device is being encrypted during step 1, it will remain encrypted After this test.
1967 The only way to disable the encryption is to factory reset the device.
Rubin Xu55d22d42014-09-24 19:56:58 +01001968 </string>
1969 <string name="provisioning_byod_profileowner">Profile owner installed</string>
1970 <string name="provisioning_byod_diskencryption">Full disk encryption enabled</string>
Rubin Xuc2b00d82015-02-02 11:30:26 +00001971 <string name="provisioning_byod_profile_visible">Profile-aware accounts settings</string>
1972 <string name="provisioning_byod_admin_visible">Profile-aware device administrator settings</string>
Rubin Xu55d22d42014-09-24 19:56:58 +01001973 <string name="provisioning_byod_workapps_visible">Badged work apps visible in Launcher</string>
Daniel Xiea41d4972015-10-19 15:35:16 -07001974 <string name="provisioning_byod_cross_profile_from_personal">Open app cross profiles from the personal side</string>
1975 <string name="provisioning_byod_cross_profile_from_work">Open app cross profiles from the work side</string>
1976 <string name="provisioning_app_linking">App links from the work side</string>
1977 <string name="provisioning_byod_cross_profile_app_personal">You selected the personal option.</string>
Alexandra Gherghinaaa24ed72014-10-08 01:11:32 +01001978 <string name="provisioning_byod_cross_profile_app_work">You selected the Work option.</string>
Daniel Xiea41d4972015-10-19 15:35:16 -07001979 <string name="provisioning_byod_cross_profile_app_ctsverifier"> You selected the ctsverifier option </string>
1980 <string name="provisioning_byod_cross_profile_from_personal_instruction">
Alexandra Gherghinaaa24ed72014-10-08 01:11:32 +01001981 Please press the Go button to start an action.\n
1982 \n
1983 You should be asked to choose either \"CTS Verifier\" or \"Work\" to complete the action.
1984 Pressing either should bring up a page stating your choice.\n
1985 \n
1986 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly.
1987 </string>
Daniel Xiea41d4972015-10-19 15:35:16 -07001988 <string name="provisioning_byod_cross_profile_from_work_instruction">
1989 Please press the Go button to start an action.\n
1990 \n
1991 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action.
1992 Pressing either should bring up a page stating your choice.\n
1993 \n
1994 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly.
1995 </string>
1996 <string name="provisioning_byod_app_linking_instruction">
1997 Please press the Go button to start an action.\n
1998 \n
1999 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action.\n
2000 - If you choose \"CTS Verifier\", you should see a page stating your chose \"CTS Verifier\".\n
2001 - If you choose \"Personal\", you should be presented with another dialog between \"CTS Verifier\"
2002 and some other apps. In this case, you should choose \"CTS verifier\".\n
2003 You should then see a page stating you chose \"Personal\".\n
2004 \n
2005 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly.
2006 </string>
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01002007 <string name="provisioning_byod_keyguard_disabled_features">Keyguard disabled features</string>
2008 <string name="provisioning_byod_keyguard_disabled_features_info">
2009 This test exercises Keyguard Disabled Features. Follow instructions above.
2010 </string>
2011 <string name="provisioning_byod_keyguard_disabled_features_instruction">
Zoltan Szatmary-Ban0592ee52015-08-24 13:31:41 +01002012 Please go to Settings &gt; Security &gt; Device administrators and set
Ahmet Kerim SENOL9fa97c22015-10-12 15:29:11 +01002013 \"CTS Verifier\" as active admin.\n
Ricky Wai8caba372016-04-27 16:52:12 +01002014 After that please go to Settings &gt; Security &gt; Screen lock and set
2015 your screen lock password to \"testpassword\".\n
2016 Then please press the \"Prepare test\" button to disable trust agents.\n
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01002017 Then please press through the following verification steps.\n
Ricky Wai8caba372016-04-27 16:52:12 +01002018 Note: After leaving the screen active admin status will be cleared.
2019 Please go to Settings &gt; Security &gt; Screen lock and set your
2020 password type to \"None\".
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01002021 </string>
2022 <string name="provisioning_byod_keyguard_disabled_features_prepare_button">Prepare test</string>
Zoltan Szatmary-Ban0592ee52015-08-24 13:31:41 +01002023 <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 +01002024 <string name="provisioning_byod_disable_trust_agents">Disable trust agents</string>
2025 <string name="provisioning_byod_disable_trust_agents_instruction">
2026 Please press the Go button to go to Settings > Security. Then go to Trusted agents and\n
2027 check if the agents are shown as disabled by the administrator.
2028 Then please press Back and mark the test as \"Pass\" or \"Fail\".
2029 </string>
2030 <string name="provisioning_byod_fingerprint_disabled_in_settings">Fingerprint is disabled in Settings</string>
2031 <string name="provisioning_byod_fingerprint_disabled_in_settings_instruction">
2032 Please press the Go button to go to Settings > Security. Then go to Fingerprint and\n
Ahmet Kerim SENOL9fa97c22015-10-12 15:29:11 +01002033 check if the disclaimer at the bottom of screen is altered to warn the users for\n
2034 fingerprint being disabled in lock screen. Then please press Back and mark the \n
2035 test as \"Pass\" or \"Fail\".
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01002036 </string>
2037 <string name="provisioning_byod_disable_fingerprint">Fingerprint disabled on keyguard</string>
2038 <string name="provisioning_byod_disable_fingerprint_instruction">
2039 Please press the Go button to lock the screen. Then try to log in using the fingerprint reader.\n
2040 Expected result is you cannot log in using your fingerprint.\n
2041 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\".
2042 </string>
Ahmet Kerim SENOL9fa97c22015-10-12 15:29:11 +01002043 <string name="provisioning_byod_disable_unredacted_notifications">Unredacted notifications disabled on keyguard</string>
2044 <string name="provisioning_byod_disable_unredacted_notifications_instruction">
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01002045 Please press the Go button to lock the screen. Wait a couple of seconds and look out for a
2046 notification from CtsVerifier.\n
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002047 Expected result is the notification is shown as \"Contents hidden by policy\", you can not see the contents
Ahmet Kerim SENOL9fa97c22015-10-12 15:29:11 +01002048 (Which would read \"This is a notification\"). You should be seeing a work badge.\n
Zoltan Szatmary-Ban46b5ceb2015-07-24 12:28:19 +01002049 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\".
2050 </string>
Alexandra Gherghina2c672b72015-01-22 11:20:23 +00002051 <string name="provisioning_byod_work_notification">Work notification is badged</string>
2052 <string name="provisioning_byod_work_notification_instruction">
2053 Please press the Go button to trigger a notification.\n
2054 \n
2055 Verify that the notification is badged (see sample badge below). Then mark this test accordingly.
2056 </string>
Ahmet Kerim SENOL9fa97c22015-10-12 15:29:11 +01002057 <string name="provisioning_byod_notification_title">This is a notification</string>
Zoltan Szatmary-Band265a1e2015-12-31 18:32:10 +00002058
2059 <string name="provisioning_byod_disallow_apps_control">Disallow apps control</string>
2060 <string name="provisioning_byod_disallow_apps_control_info">
2061 This test exercises Disallow Apps Control. Follow instructions above.
2062 </string>
2063 <string name="provisioning_byod_disallow_apps_control_instruction">
2064 Please press the \"Prepare test\" button to disallow apps control for managed apps.\n
2065 Then please press through the following verification steps.\n
2066 Note: After leaving the screen disallow apps control restriction will be cleared.
2067 </string>
2068 <string name="provisioning_byod_disallow_apps_control_prepare_button">Prepare test</string>
2069 <string name="provisioning_byod_disabled_uninstall_button">Disabled uninstall button</string>
2070 <string name="provisioning_byod_disabled_uninstall_button_instruction">
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002071 Please press the Go button to go to Settings > Apps. Choose a managed app. Check that performing either \"Uninstall\" or \"Disable\" is not possible and triggers a support message when trying to do so.
Zoltan Szatmary-Band265a1e2015-12-31 18:32:10 +00002072 Then please press Back and mark the test as \"Pass\" or \"Fail\".
2073 </string>
2074 <string name="provisioning_byod_disabled_force_stop_button">Disabled force stop button</string>
2075 <string name="provisioning_byod_disabled_force_stop_button_instruction">
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002076 Please press the Go button to go to Settings > Apps. Choose a managed app. Check that performing \"Force stop\" is not possible and triggers a support message when trying to do so.
Zoltan Szatmary-Band265a1e2015-12-31 18:32:10 +00002077 Then please press Back and mark the test as \"Pass\" or \"Fail\".
2078 </string>
2079 <string name="provisioning_byod_disabled_app_storage_buttons">Disabled app storage buttons</string>
2080 <string name="provisioning_byod_disabled_app_storage_buttons_instruction">
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002081 Please press the Go button to go to Settings > Apps. Choose a managed (badged) app. Select \"Storage\". Check that performing \"Clear Data\" and \"Clear Cache\" is not possible and triggers a support message when trying to do so.
Zoltan Szatmary-Band265a1e2015-12-31 18:32:10 +00002082 Note: if an app has no data then tapping the clear data button has no effect anyway. Make sure you have selected
2083 the badged version of app with non-zero app data. Badged \"Settings\" may be a good candidate.
2084 Then please press Back and mark the test as \"Pass\" or \"Fail\".
2085 </string>
2086
Kenny Guy68e7df92015-05-29 15:26:28 +01002087 <string name="provisioning_byod_work_status_icon">Work status icon is displayed</string>
2088 <string name="provisioning_byod_work_status_icon_instruction">
2089 Verify that the current status bar does not have a work status icon (see sample icon below).
2090 \n\n
2091 Please press the Go button to launch a work activity.
2092 \n\n
2093 Verify that the status bar now has a work status icon. Then mark this test accordingly.
2094 </string>
2095 <string name="provisioning_byod_work_status_icon_activity">
2096 Verify that the current status bar has a work status notification.
2097 \n\n
2098 Please press finish to return to the tests and then mark this test accordingly.
2099 </string>
2100 <string name="provisioning_byod_work_status_toast">Work status toast is displayed</string>
2101 <string name="provisioning_byod_work_status_toast_instruction">
2102 Please press the Go button to launch a work activity.
2103 \n\n
2104 Follow instructions and then return and mark this test accordingly.
2105 </string>
2106 <string name="provisioning_byod_work_status_toast_activity">
2107 Turn off the screen and wait a few seconds then turn on the screen again.
2108 \n\n
2109 Verify that a toast was displayed saying you are in the work profile.
2110 \n\n
2111 Please press finish to return to the tests and then mark this test accordingly.
2112 </string>
Rubin Xu55d22d42014-09-24 19:56:58 +01002113 <string name="provisioning_byod_profile_visible_instruction">
2114 Please press the Go button to open the Settings page.
2115 Navigate to Accounts and confirm that:\n
2116 \n
2117 - Both Personal and Work categories exist.\n
2118 - \"Remove work profile\" exists under the Work category.\n
2119 \n
Esteban Talaverab7501de2017-03-22 18:10:19 +00002120 Furthermore, verify that:\n
2121 - There are two auto-sync options present, one for personal and one for work data (either on the screen or in the overflow menu).\n
Michal Karpinskiad58cb92015-08-21 12:22:12 +01002122 - De-selecting either option prompts a warning dialog.\n
2123 \n
Rubin Xu55d22d42014-09-24 19:56:58 +01002124 Use the Back button to return to this page.
2125 </string>
2126 <string name="provisioning_byod_admin_visible_instruction">
2127 Please press the Go button to open the Security page in Settings.
Esteban Talaverab7501de2017-03-22 18:10:19 +00002128 Navigate to Device admin apps and confirm that:\n
Rubin Xu55d22d42014-09-24 19:56:58 +01002129 \n
Michal Karpinski915eeaf2016-03-04 12:28:52 +00002130 - Device administrators outside of the work profile (if any) appear in the list, and the managed profile administrators are badged correctly.\n
Kenny Guyc9bd7162016-06-03 15:47:20 +01002131 - A badged \"CTS Verifier\" exists, and is activated.\n
Esteban Talaverab7501de2017-03-22 18:10:19 +00002132 - There is no option to deactivate the badged \"CTS Verifier\" version, only an option to \"Remove work profile\".\n
Rubin Xu55d22d42014-09-24 19:56:58 +01002133 \n
2134 Use the Back button to return to this page.
2135 </string>
2136 <string name="provisioning_byod_workapps_visible_instruction">
2137 Please press the Go button to start the launcher.
2138 Go to All Apps screen and scroll through it to confirm that:\n
2139 \n
2140 - A new set of work apps including CTS Verifier appear in the list.\n
Alexandra Gherghina9c1c5a52014-12-09 12:55:23 +00002141 - Work badge overlay appears on work app\'s icon (see example icon below).\n
Rubin Xu55d22d42014-09-24 19:56:58 +01002142 \n
2143 Then navigate back to this screen using Recents button.
2144 </string>
Rubin Xuc2b00d82015-02-02 11:30:26 +00002145
2146 <string name="provisioning_byod_app_settings">Profile-aware app settings</string>
2147 <string name="provisioning_byod_app_settings_instruction">
2148 Please press the Go button to open Apps page in settings.\n
2149 \n
2150 Verify that work profile exists in the dropdown list and selecting it will
2151 bring up apps setting in the work profile.\n
2152 \n
2153 Then use the Back button to return to this test and mark accordingly.
2154 </string>
2155
2156 <string name="provisioning_byod_location_settings">Profile-aware location settings</string>
2157 <string name="provisioning_byod_location_settings_instruction">
2158 Please press the Go button to open Location page in settings.\n
2159 \n
Zoltan Szatmary-Banbfdde072016-01-15 13:24:07 +00002160 Verify that work profile entry exists in the page and it has a toggleable switch.\n
2161 Switch the main location switch at the top of the screen off. You should see the work profile location switch go disabled and into \'off\' state.\n
2162 Then switch the main location switch on again. You should see the work profile location switch go enabled and into its previous state.\n
Rubin Xuc2b00d82015-02-02 11:30:26 +00002163 \n
2164 Then use the Back button to return to this test and mark accordingly.
2165 </string>
2166
Michal Karpinski880246b2016-05-03 12:39:19 +01002167 <string name="provisioning_byod_wifi_data_usage_settings">Profile-aware data usage settings (Wi-Fi)</string>
2168 <string name="provisioning_byod_wifi_data_usage_settings_instruction">
Michal Karpinskibb5c5332015-08-12 16:15:31 +01002169 Please press the Go button to open the Settings page.\n
2170 \n
Michal Karpinski880246b2016-05-03 12:39:19 +01002171 Navigate to \"Data usage\" page and then into the \"Wi-Fi data usage\" category.\n
Esteban Talaverab7501de2017-03-22 18:10:19 +00002172 Confirm that \"All work apps\" section is present and that it is possible to see the data usage for work (badged) apps.\n
Michal Karpinski880246b2016-05-03 12:39:19 +01002173 \n
2174 Then use the Back button to return to this test and mark accordingly.
2175 </string>
2176
2177 <string name="provisioning_byod_cellular_data_usage_settings">Profile-aware data usage settings (Cellular)</string>
2178 <string name="provisioning_byod_cellular_data_usage_settings_instruction">
2179 Please disable Wi-Fi connection on your device.\n
2180 Please make sure you have added a SIM card with data plan to your phone, have enabled data over cellular and in case of dual SIM devices, have selected the right SIM for data connection.\n
2181 Please carry out operations that will use mobile data using both badged and unbadged apps (e.g. visit a page in a browser).\n
2182 \n
2183 Please press the Go button to open the Settings page.\n
2184 \n
2185 Navigate to \"Data usage\" page and then into the \"Cellular data usage\" category.\n
Esteban Talaverab7501de2017-03-22 18:10:19 +00002186 Confirm that \"All work apps\" section is present and that it is possible to see the data usage for work (badged) apps.\n
Michal Karpinskibb5c5332015-08-12 16:15:31 +01002187 \n
2188 Then use the Back button to return to this test and mark accordingly.
2189 </string>
2190
Rubin Xuc2b00d82015-02-02 11:30:26 +00002191 <string name="provisioning_byod_cred_settings">Profile-aware trusted credential settings</string>
2192 <string name="provisioning_byod_cred_settings_instruction">
2193 Please press the Go button to open the Security settings.
2194 Navigate to "Trusted credentials" and wait for the UI to load.
2195 After the list is loaded, confirm that:\n
2196 \n
2197 The page list credentials for both "Personal" and "Work" profiles.\n
2198 \n
2199 Then use the Back button to return to this test and mark accordingly.
2200 </string>
2201
2202 <string name="provisioning_byod_print_settings">Profile-aware printing settings</string>
2203 <string name="provisioning_byod_print_settings_instruction">
2204 Please press the Go button to open the Printing settings.
2205 \n
2206 Verify that work profile exists in the dropdown list and selecting it will
2207 bring up printing setting in the work profile.\n
2208 \n
2209 Then use the Back button to return to this test and mark accordingly.
2210 </string>
2211
Sudheer Shanka98ff0002015-03-26 16:32:59 +00002212 <string name="provisioning_byod_cross_profile_intent_filters">Cross profile intent filters are set</string>
Alex Chau4c990c32015-08-14 15:55:18 +01002213
Alex Chauc7ef16d2015-07-30 18:01:30 +01002214 <string name="provisioning_byod_nfc_beam">Disable Nfc beam</string>
2215 <string name="provisioning_byod_nfc_beam_allowed_instruction">
2216 Please press the Go button to test if Nfc beam can be triggered in the work profile.\n
2217 \n
2218 For the first test, press \"Send manual beam\" to trigger a beam, then bump into another device to send the file. Verify that the file is successfully received.\n
2219 \n
2220 For the second test, press \"Send share intent\" to trigger a beam, then bump into another device to send the file. Verify that the file is successfully received.\n
2221 \n
2222 Then use the Back button to return to this test and mark accordingly.
2223 </string>
2224 <string name="provisioning_byod_nfc_beam_disallowed_instruction">
2225 Please press the Go button to test if Nfc beam is disallowed by policy
2226 \n
2227 Verify that Nfc beam is not triggered when pressing the button.\n
2228 \n
2229 Then use the Back button to return to this test and mark accordingly.
2230 </string>
2231 <string name="provisioning_byod_send_manual_beam">Send manual beam</string>
2232 <string name="provisioning_byod_send_share_intent">Send share intent</string>
2233 <string name="provisioning_byod_cannot_resolve_beam_activity">Cannot find beam activity</string>
2234
Daniel Xiea41d4972015-10-19 15:35:16 -07002235 <string name="test_failed_cannot_start_intent">Cannot start the given intent.</string>
Rubin Xu55d22d42014-09-24 19:56:58 +01002236 <string name="provisioning_byod_no_activity">Cannot communicate with activity in the work profile.</string>
2237 <string name="provisioning_byod_delete_profile">Initiate deletion of work profile.</string>
2238 <string name="provisioning_byod_profile_deleted">Work profile deleted.</string>
2239 <string name="provisioning_byod_disabled">Device provisioning is not enabled.</string>
Alexandra Gherghinaaa24ed72014-10-08 01:11:32 +01002240 <string name="provisioning_button_finish">Finish</string>
2241 <string name="provisioning_cross_profile_chooser">Choose an app to complete action</string>
Rubin Xua458f302014-10-03 16:09:23 +01002242
Haiming Baod001dbc2015-11-11 14:37:19 +00002243 <string name="provisioning_byod_no_gps_location_feature">No GPS feature present. Skip test.</string>
2244 <string name="provisioning_byod_location_mode_enable">Enable location</string>
2245 <string name="provisioning_byod_location_mode_enable_toast_location_change">Location changed</string>
2246 <string name="provisioning_byod_location_mode_enable_instruction">
2247 This test verifies that the location updates can be enabled for the managed profile apps.\n
Zoltan Szatmary-Banbfdde072016-01-15 13:24:07 +00002248 1. Press the go button to go to the location settings page, set both the main location switch and the work profile location switch enabled.\n
Haiming Baod001dbc2015-11-11 14:37:19 +00002249 2. Move your position a little bit, verify that location updates toast comes up.\n
2250 Please wait until the location updates or timeout toast message shows up before going back to the cts-verifier tests.\n
2251 3. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n
2252 </string>
2253
2254 <string name="provisioning_byod_location_mode_disable">Disable location</string>
2255 <string name="provisioning_byod_location_mode_time_out_toast">Timeout waiting for gps location change</string>
2256 <string name="provisioning_byod_location_mode_disable_instruction">
Zoltan Szatmary-Banbfdde072016-01-15 13:24:07 +00002257 This test verifies that the location updates can be disabled for the managed profile apps through the main location switch.\n
2258 1. Press the go button to go to the location settings page, set the main location switch disabled.\n
2259 2. Move your position a little bit, verify that no location updates toast come up and that the timeout message show up after around 15 seconds.
Haiming Baod001dbc2015-11-11 14:37:19 +00002260 Please wait until the timeout or location updates toast message shows up before going back to the cts-verifier tests.\n
2261 3. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n
2262 </string>
2263
Zoltan Szatmary-Banbfdde072016-01-15 13:24:07 +00002264 <string name="provisioning_byod_work_location_mode_disable">Disable location for work profile</string>
2265 <string name="provisioning_byod_work_location_mode_disable_instruction">
2266 This test verifies that the location updates can be disabled for the managed profile apps through work profile location switch.\n
2267 1. Press the go button to go to the location settings page, set the work location switch disabled while the main location switch is still enabled.\n
2268 2. Move your position a little bit, verify that no location updates toast come up and that the timeout message show up after around 15 seconds.
2269 Please wait until the timeout or location updates toast message shows up before going back to the cts-verifier tests.\n
2270 3. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n
2271 </string>
2272 <string name="provisioning_byod_primary_location_when_work_disabled">Primary receives updates while work location is disabled</string>
2273 <string name="provisioning_byod_primary_location_when_work_disabled_instruction">
2274 This test verifies that location updates are still received by primary profile when location updates are disabled for managed profile apps through work profile location switch.\n
2275 1. Press the go button to go to the location settings page, set the work location switch disabled while the main location switch is still enabled.\n
2276 2. Move your position a little bit, verify that location updates toast comes up.\n
2277 Please wait until the location updates or timeout toast message shows up before going back to the cts-verifier tests.\n
2278 3. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n
2279 </string>
2280
Rubin Xuc9c73fe2016-05-03 18:26:30 +01002281 <string name="provisioning_byod_turn_off_work">Turn off work mode</string>
Jim Kaye12507db2016-11-07 11:24:54 -08002282 <string name="provisioning_byod_turn_off_work_info">This test verifies device behaviors when turning off work mode.</string>
Rubin Xuc9c73fe2016-05-03 18:26:30 +01002283 <string name="provisioning_byod_turn_off_work_instructions">
Jim Kaye12507db2016-11-07 11:24:54 -08002284 This test verifies the device behavior when work profile is turned off.\n
Rubin Xuc9c73fe2016-05-03 18:26:30 +01002285 Please exercise the following tests in sequence.\n
2286 The button below can be used to open the Settings page where you can toggle work mode.
Nicolas Prevot6e7d08e2016-01-27 12:41:31 +00002287 </string>
Rubin Xuc9c73fe2016-05-03 18:26:30 +01002288 <string name="provisioning_byod_turn_off_work_prepare_button">Open Settings to toggle work mode</string>
2289
2290 <string name="provisioning_byod_turn_off_work_prepare_notifications">Prepare a work notification</string>
2291 <string name="provisioning_byod_turn_off_work_prepare_notifications_instruction">
2292 This is a test setup step.\n
2293 1. Press the go button to send a work notification.\n
2294 2. Verify that the notification is displayed and mark this test as passed.\n
2295 (Note: in the following test, you will be asked to verify the notification disappears after work mode is turned off.)
2296 </string>
2297
2298 <string name="provisioning_byod_turn_off_work_turned_off">Please turn off work mode</string>
2299 <string name="provisioning_byod_turn_off_work_turned_off_toast">Open settings to turn off work mode, using the button above.</string>
2300
2301 <string name="provisioning_byod_turn_off_work_notifications">Notifications when work mode is off</string>
2302 <string name="provisioning_byod_turn_off_work_notifications_instruction">
2303 Verify that the previously-shown work notification has now disappeared.
2304 </string>
2305
2306 <string name="provisioning_byod_turn_off_work_icon">Status bar icon when work mode is off</string>
2307 <string name="provisioning_byod_turn_off_work_icon_instruction">
2308 Now that work mode is off, please verify that the status bar shows an icon indicating that work mode is off.\n
2309 </string>
2310
Nicolas Prevot6e7d08e2016-01-27 12:41:31 +00002311 <string name="provisioning_byod_turn_off_work_launcher">Starting work apps when work mode is off</string>
2312 <string name="provisioning_byod_turn_off_work_launcher_instruction">
2313 This test verifies that work applications cannot be started if work mode is off.\n
Rubin Xuc9c73fe2016-05-03 18:26:30 +01002314 1. Press home to go to the launcher.\n
2315 2. Verify that work applications are greyed out.\n
2316 3. Tap on a work application.\n
2317 4. Verify that the application does not start.\n
Nicolas Prevot6e7d08e2016-01-27 12:41:31 +00002318 </string>
Rubin Xuc9c73fe2016-05-03 18:26:30 +01002319
2320 <string name="provisioning_byod_turn_off_work_turned_on">Please turn work mode back on</string>
2321 <string name="provisioning_byod_turn_off_work_turned_on_toast">Open settings to turn work mode back on, using the button above.</string>
2322
2323 <string name="provisioning_byod_turn_on_work_icon">Status bar icon when work mode is on</string>
2324 <string name="provisioning_byod_turn_on_work_icon_instruction">
2325 Now that work mode is back on, please verify that the status bar icon for work mode off is no longer visible.
Nicolas Prevot6e7d08e2016-01-27 12:41:31 +00002326 </string>
Rubin Xuc9c73fe2016-05-03 18:26:30 +01002327
2328 <string name="provisioning_byod_turn_on_work_launcher">Starting work apps when work mode is on</string>
2329 <string name="provisioning_byod_turn_on_work_launcher_instruction">
2330 Now that work mode is back on, please go to the launcher and verify that you can start a work application.
2331 </string>
2332
Mahaver Choprab49c4ec2016-03-17 15:11:27 +00002333 <string name="provisioning_byod_organization_info">Organization Info</string>
2334 <string name="provisioning_byod_organization_name_hint">Name</string>
2335 <string name="provisioning_byod_organization_color_hint">#FF00FF</string>
2336 <string name="provisioning_byod_set_organization_info_button_text">Set</string>
2337 <string name="provisioning_byod_organization_info_instructions">
2338 This test verifies that the Organization Info was set correctly.
Mahaver Choprae0611982016-05-03 10:53:33 +01002339 You can only do this test after you have done "select work lock" test.\n
Mahaver Choprab49c4ec2016-03-17 15:11:27 +00002340 1. Enter your organization name.\n
2341 2. Enter a valid color code.\n
2342 3. Press the Set button to set organization Info.\n
2343 4. Press the Go button to open a dialog to confirm work credentials.\n
2344 5. Verify that the background color of the resulting dialog is as set by you.\n
2345 6. Verify that the header text has organization name as set by you.\n
2346 </string>
Mahaver Chopra8835de32016-04-20 13:32:00 +01002347 <string name="provisioning_byod_parent_profile_password">Personal password test</string>
2348 <string name="provisioning_byod_parent_profile_password_description">
2349 This test verifies that the password on the personal side can be chosen from within a managed profile.\n
2350
2351 1. Press the Go button to set a new password for the personal side.\n
2352 2. Lock and unlock the screen to verify that the personal side password was set correctly.\n
2353 </string>
Nicolas Prevot6e7d08e2016-01-27 12:41:31 +00002354
Bartosz Fabianowski4dbb1eb2016-12-01 19:13:33 +01002355 <!-- Strings for DeviceOwnerNegativeTestActivity -->
2356 <string name="negative_device_owner">No Device Owner Tests</string>
2357 <string name="device_owner_negative_category">No Device Owner Tests</string>
2358 <string name="device_owner_provisioning_negative">Device owner provisioning</string>
2359 <string name="device_owner_provisioning_negative_info">The device owner provisioning test verifies that setting up a corporate owned device can only be done on a factory reset device.\n\nPlease 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 +01002360 <string name="start_device_owner_provisioning_button">Start provisioning</string>
Bartosz Fabianowski4dbb1eb2016-12-01 19:13:33 +01002361 <string name="enterprise_privacy_quick_settings_negative">Quick settings disclosure</string>
2362 <string name="enterprise_privacy_quick_settings_negative_info">
2363 Please do the following:\n
2364 1) Open and fully expand Quick Settings.\n
2365 2) Verify that at the bottom of Quick Settings, you are not told the device is managed.\n
2366 3) Close Quick Settings.
2367 </string>
2368 <string name="enterprise_privacy_keyguard_negative">Keyguard disclosure</string>
2369 <string name="enterprise_privacy_keyguard_negative_info">
2370 Please do the following:\n
2371 1) Press the Go button to open Settings.\n
2372 2) Navigate to \"Security\" &gt; \"Screen lock\" and select the first screen lock type that is not \"None\".\n
2373 3) Use the Back button to return to this page.\n
2374 4) Lock the device.\n
2375 5) Verify that on the lock screen, you are not told the device is managed.\n
2376 6) Unlock the device.\n
2377 7) Repeat steps (1) through (6) for each screen lock type other than \"None\".
2378 </string>
Bartosz Fabianowski006d06b2017-01-18 17:31:18 +01002379 <string name="enterprise_privacy_add_account_negative">Add account disclosure</string>
2380 <string name="enterprise_privacy_add_account_negative_info">
2381 Please do the following:\n
2382 1) Press the Go button to open Settings.\n
2383 2) In the screen that opens, verify that you are not told that the device is managed.\n
2384 3) Use the Back button to return to this page.
2385 </string>
Bartosz Fabianowski4dbb1eb2016-12-01 19:13:33 +01002386
2387 <!-- Strings for DeviceOwnerPositiveTestActivity -->
Zoltan Szatmary-Ban9a2b13e2015-06-15 17:05:04 +01002388 <string name="positive_device_owner">Device Owner Tests</string>
2389 <string name="device_owner_positive_tests">Device Owner positive tests</string>
2390 <string name="device_owner_positive_tests_instructions">
2391 The positive device owner tests verify policies on a corporate owned device.\n
2392 Press below button first, follow steps described in the dialog that pops up,
2393 then proceed to the test cases.\n
2394 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n
2395 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should
2396 be run last so that it does not interfere with other tests.
2397 </string>
2398 <string name="device_owner_positive_tests_info">
2399 The positive device owner tests verify policies on a corporate owned device.\n
2400 Press below button first, follow steps described in the dialog that pops up,
2401 then proceed to the test cases.\n
2402 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n
2403 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should
2404 be run last so that it does not interfere with other tests.
2405 </string>
2406 <string name="device_owner_positive_category">Device Owner Tests</string>
2407 <string name="set_device_owner_button_label">Set up device owner</string>
2408 <string name="set_device_owner_dialog_title">Set up device owner</string>
2409 <string name="set_device_owner_dialog_text">
2410 Please set the device owner by enabling USB debugging on the device and issuing the following command on the host:\n
2411 adb shell dpm set-device-owner \'com.android.cts.verifier/com.android.cts.verifier.managedprovisioning.DeviceAdminTestReceiver\'
2412 </string>
2413 <string name="device_owner_remove_device_owner_test">Remove device owner</string>
2414 <string name="device_owner_remove_device_owner_test_info">
2415 Please check in Settings &gt; Security &gt; Device Administrators if CTSVerifier is
2416 Device Owner. Then press the button below, and check that CTSVerifier is NOT Device
2417 Owner anymore.
2418 </string>
2419 <string name="remove_device_owner_button">Remove device owner</string>
2420 <string name="device_owner_check_device_owner_test">Check device owner</string>
2421 <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 +01002422 <string name="device_owner_wifi_lockdown_test">WiFi configuration lockdown</string>
2423 <string name="device_owner_wifi_lockdown_info">
2424 Please enter the SSID and auth method of an available WiFi Access Point and press the button to create a
2425 WiFi configuration. This configuration can be seen on Settings &gt; WiFi. The test cases
Mahaver Choprac0f70ce2015-10-16 12:40:39 +01002426 are going to use this config. Please go through test cases in order (from top to bottom).
Zoltan Szatmary-Ban01ce4542015-06-22 11:14:47 +01002427 </string>
2428 <string name="switch_wifi_lockdown_off_button">WiFi config lockdown off</string>
2429 <string name="switch_wifi_lockdown_on_button">WiFi config lockdown on</string>
2430 <string name="wifi_lockdown_go_settings_wifi_button">Go to WiFi Settings</string>
2431 <string name="device_owner_wifi_key_management_none_button">None</string>
2432 <string name="device_owner_wifi_key_management_wpa_button">WPA</string>
2433 <string name="device_owner_wifi_key_management_wep_button">WEP</string>
2434 <string name="create_wifi_config_button_label">Create WiFi configuration</string>
2435 <string name="wifi_lockdown_add_network_failed_dialog_title">WiFi configuration could not be created</string>
2436 <string name="wifi_lockdown_add_network_failed_dialog_text">
2437 There was an error during creation of WiFi configuration. Check if WiFi is switched on.
2438 </string>
2439 <string name="device_owner_wifi_config_unlocked_modification_test">Unlocked config is modifiable in Settings</string>
2440 <string name="device_owner_wifi_config_unlocked_modification_test_info">
2441 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to
2442 Settings &gt; WiFi and see if the CTSVerifier created WiFi configuration can be edited.
2443 Please make sure you can connect to it. The test is successful if the config is editable
2444 and can be connected to.
2445 </string>
2446 <string name="device_owner_wifi_config_locked_modification_test">Locked config is not modifiable in Settings</string>
2447 <string name="device_owner_wifi_config_locked_modification_test_info">
2448 Please press the button to ensure WiFi config lockdown is in effect. Then go to
2449 Settings &gt; WiFi and see if the CTSVerifier created WiFi configuration can NOT be edited
2450 or removed. The test is successful if the config is NOT modifiable.
2451 </string>
2452 <string name="device_owner_wifi_config_locked_connection_test">Locked config can be connected to</string>
2453 <string name="device_owner_wifi_config_locked_connection_test_info">
2454 Please press the button to ensure WiFi config lockdown is in effect. Then go to
2455 Settings &gt; WiFi and see if the CTSVerifier created WiFi configuration can be connected
2456 to manually. The test is successful if the connection can be established.
2457 </string>
2458 <string name="device_owner_wifi_config_unlocked_removal_test">Unlocked config can be forgotten in Settings</string>
2459 <string name="device_owner_wifi_config_unlocked_removal_test_info">
2460 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to
2461 Settings &gt; WiFi and see if the CTSVerifier created WiFi configuration can be forgotten.
2462 The test is successful if the config could be forgotten and is removed from the list of saved configs.
2463 </string>
Benjamin Franz89e40fc2015-07-01 15:35:57 +01002464 <string name="device_owner_disable_statusbar_test">Disable status bar</string>
2465 <string name="device_owner_disable_statusbar_test_info">
2466 Please press the below button to disable the status bar and verify that quick settings, notifications
2467 and the assist gesture are no longer available.\n
2468 Next, press the button to reenable the status bar and verify that quick settings, notification
2469 and the assist gesture are available again.\n
2470 Please mark the test accordingly.
2471 </string>
2472 <string name="device_owner_disable_statusbar_button">Disable status bar</string>
2473 <string name="device_owner_reenable_statusbar_button">Reenable status bar</string>
2474 <string name="device_owner_disable_keyguard_test">Disable keyguard</string>
2475 <string name="device_owner_disable_keyguard_test_info">
2476 Note that any device passwords that you might have set will be deleted during this test.\n
2477 Please press the below button to disable the keyguard. Press the power button on your device to
2478 switch off the screen. Then press the power button to switch the screen back on and verify that
2479 no keyguard was shown.\n
2480 Next, press the button to reenable the keyguard and repeat the above steps, this time verifying that
2481 a keyguard was shown again.\n
2482 Please mark the test accordingly.
2483 </string>
2484 <string name="device_owner_disable_keyguard_button">Disable keyguard</string>
2485 <string name="device_owner_reenable_keyguard_button">Reenable keyguard</string>
Sudheer Shanka72ba56a2015-07-17 18:30:44 +01002486 <string name="device_profile_owner_permission_lockdown_test">Permissions lockdown</string>
2487 <string name="device_profile_owner_permission_lockdown_test_instructions">
2488 Select each of the three grant states for the permission shown below in turn.\n
Jim Kaye12507db2016-11-07 11:24:54 -08002489 Now open application settings, select Permissions, and verify if the following behavior is observed.\n
2490 <b>Grant:</b> Permission is granted to the app and cannot be changed through the settings UI. Trying to change it triggers a support message.\n
Sudheer Shanka72ba56a2015-07-17 18:30:44 +01002491 <b>Let user decide:</b> Permission state can be changed through the settings UI.\n
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002492 <b>Deny:</b> Permission is denied to the app and cannot be changed through the settings UI. Trying to change it triggers a support message.\n
Sudheer Shanka72ba56a2015-07-17 18:30:44 +01002493 Please mark the test accordingly.
2494 </string>
2495 <string name="device_owner_permission_lockdown_test_info">
2496 This test checks if the permissions state in settings UI is locked down according to the state set by the device owner.
2497 </string>
Zoltan Szatmary-Band265a1e2015-12-31 18:32:10 +00002498 <string name="device_owner_disallow_usb_file_transfer_test">Disallow USB file transfer</string>
2499 <string name="device_owner_disallow_usb_file_transfer_test_info">
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002500 Please press below button to set the \"disallow USB file transfer\" restriction.\n
Nimrod Gileadi89cbc1b2016-11-01 10:23:05 +00002501 If a USB notification appears, open the notification and check that the
2502 \"Transfer files (MTP)\" and \"Transfer photos (PTP)\" cannot be selected and trigger a
2503 support message when trying to select them.\n
2504 Check if you can mount the device as a USB drive on your desktop computer. The test is
2505 successful if you cannot mount the device, and files from your phone cannot be
2506 downloaded through USB.\n
Zoltan Szatmary-Band265a1e2015-12-31 18:32:10 +00002507 Please mark the test accordingly.
2508 </string>
Nicolas Prevot9d80fa42016-03-01 17:24:06 +00002509 <string name="device_owner_set_user_icon">Setting the user icon</string>
2510 <string name="device_owner_set_user_icon_instruction">
2511 This test verifies that the user icon can be set.\n
2512 1. Press the set user icon button.\n
2513 2. Press the go button to go to Settings.\n
2514 3a. If there is a \"users\" section in Settings, check that the icon of the user \"owner\" is the CtsVerifier one and mark this test accordingly.\n
2515 3b. If there is no \"users\" section, mark this test as passed.\n
2516 </string>
2517 <string name="device_owner_set_user_icon_button">Set user icon</string>
2518
Sudheer Shanka72ba56a2015-07-17 18:30:44 +01002519 <string name="profile_owner_permission_lockdown_test_info">
2520 <b>
2521 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
2522 </b>
2523 This test checks if the permissions state in settings UI is locked down correctly depending on the state set by the profile owner.
2524 </string>
2525 <string name="package_not_found">You must install %s (aka CtsPermissionApp).</string>
2526 <string name="permission_allow">Grant</string>
2527 <string name="permission_default">Let user decide</string>
2528 <string name="permission_deny">Deny</string>
2529 <string name="not_profile_owner">%s is not profile owner.</string>
2530 <string name="not_device_owner">%s is not device owner.</string>
2531 <string name="activity_not_found">No activity found to handle intent: %s</string>
2532 <string name="open_settings_button_label">Open Application Settings</string>
2533 <string name="finish_button_label">Finish</string>
Benjamin Franz2e9fd732015-08-10 15:43:42 +01002534 <string name="device_owner_device_admin_visible">Device administrator settings</string>
2535 <string name="device_owner_device_admin_visible_info">
2536 Please press the Go button to open the Security page in Settings.
2537 Navigate to Device administrators and confirm that:\n
2538 \n
Ahmet Kerim SENOL9fa97c22015-10-12 15:29:11 +01002539 - \"CTS Verifier\" exists and is activated.\n
2540 - \"CTS Verifier\" cannot be disabled.\n
Benjamin Franz2e9fd732015-08-10 15:43:42 +01002541 \n
2542 Use the Back button to return to this page.
2543 </string>
Benjamin Franz1c8defc2015-08-10 16:52:56 +01002544 <string name="device_owner_disallow_config_bt">Disallow configuring Bluetooth</string>
2545 <string name="device_owner_disallow_config_bt_info">
2546 Please press the Set restriction button to set the user restriction.
2547 Then press Go to open the Bluetooth page in Settings.
2548 Confirm that:\n
2549 \n
2550 - You cannot view Bluetooth devices in range.\n
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002551 - Trying to edit, add or remove any already paired devices triggers a support message.\n
Benjamin Franz1c8defc2015-08-10 16:52:56 +01002552 \n
2553 Use the Back button to return to this page.
2554 </string>
2555 <string name="device_owner_disallow_config_wifi">Disallow configuring WiFi</string>
2556 <string name="device_owner_disallow_config_wifi_info">
2557 Please press the Set restriction button to set the user restriction.
2558 Then press Go to open the WiFi page in Settings.
Mahaver Choprabc1764e2016-05-11 18:31:19 +01002559 Confirm that:\n\n
Benjamin Franz1c8defc2015-08-10 16:52:56 +01002560 - You cannot view WiFi networks in range.\n
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002561 - Trying to edit, add or remove any existing WiFi configs triggers a support message.\n
Benjamin Franz1c8defc2015-08-10 16:52:56 +01002562 \n
2563 Use the Back button to return to this page.
2564 </string>
Mahaver Choprad4994a12016-01-04 14:22:29 +00002565 <string name="device_owner_disallow_data_roaming">Disallow data roaming</string>
2566 <string name="device_owner_disallow_data_roaming_info">
Mahaver Chopraaee92cf2016-04-21 13:52:11 +01002567 Device should have a sim card to perform this test.
Mahaver Choprad4994a12016-01-04 14:22:29 +00002568 Please press the Set restriction button to set the user restriction.
2569 Then press Go to open the Cellular network page in Settings.
Mahaver Choprabc1764e2016-05-11 18:31:19 +01002570 Confirm that:\n\n
Mahaver Choprad4994a12016-01-04 14:22:29 +00002571 - Data roaming is disabled.\n
Mahaver Choprabc1764e2016-05-11 18:31:19 +01002572 - Enabling data roaming is not possible and triggers a support message.\n\n
Mahaver Choprad4994a12016-01-04 14:22:29 +00002573 Use the Back button to return to this page.
2574 </string>
Mahaver Choprabc1764e2016-05-11 18:31:19 +01002575 <string name="device_owner_disallow_factory_reset">Disallow factory reset</string>
2576 <string name="device_owner_disallow_factory_reset_info">
2577 Please press the Set button to set the user restriction.\n
2578 1. Go to the factory reset settings. It is often located in \"Backup &amp; reset\" settings.\n
2579 Confirm that:\n
2580 - Factory data reset is disabled.\n
2581 - Pressing factory data reset is not possible and triggers a support message.\n\n
2582 2. Go to OEM unlocking settings, if this device has this Settings option. It is often located under \"Developer options\".\n
2583 Confirm that:\n
2584 - Oem Unlocking is disabled.\n
2585 - Enabling Oem unlocking is not possible and triggers a support message.\n\n
2586 Return back to this page.
2587 </string>
Benjamin Franz1c8defc2015-08-10 16:52:56 +01002588 <string name="device_owner_user_restriction_set">Set restriction</string>
2589 <string name="device_owner_settings_go">Go</string>
Matthew Williams547b8162014-10-15 10:18:11 -07002590
Mahaver Chopra77128812015-11-17 10:05:33 +00002591 <string name="device_owner_vpn_connection">
Jim Kaye12507db2016-11-07 11:24:54 -08002592 VPN connection has been established.\n
Mahaver Chopra77128812015-11-17 10:05:33 +00002593 This is not as expected.\n
2594 Mark this test as failed.\n
2595 </string>
2596 <string name="device_owner_vpn_connection_close_failed">
2597 Established vpn connection cannot be closed.\n
2598 This is not as expected.\n
2599 Mark this test as failed.\n
2600 </string>
2601 <string name="device_owner_no_vpn_connection">
2602 Cannot establish a VPN connection.\n
2603 This was expected.\n
2604 Mark this test as passed.\n
2605 </string>
Mahaver Chopra77128812015-11-17 10:05:33 +00002606 <string name="device_owner_vpn_test">Check VPN</string>
Jim Kaye12507db2016-11-07 11:24:54 -08002607 <string name="device_owner_vpn_info_default">VPN test message</string>
Mahaver Chopra77128812015-11-17 10:05:33 +00002608
Mahaver Choprac0f70ce2015-10-16 12:40:39 +01002609 <string name="device_owner_disallow_config_vpn">Disallow configuring VPN</string>
2610 <string name="device_owner_disallow_config_vpn_info">
2611 Please press the Set VPN restriction button to set the VPN restriction.
Mahaver Chopra77128812015-11-17 10:05:33 +00002612 Perform tests in order. Mark test as passed if both test cases pass\n\n
Damien Bargiacchia433c272017-01-31 16:34:22 -08002613 1. Press Go to attempt to open the VPN settings page.\n
2614 You should either see (a) the VPN settings page or (b) that the Intent
2615 android.settings.VPN_SETTINGS fails to resolve.\n
2616 In the case of (a), confirm that:\n
Damien Bargiacchia433c272017-01-31 16:34:22 -08002617 - Trying to perform any of the above actions will trigger a support message.\n
2618 In the case of (b) this step is successful.\n\n
Mahaver Chopra77128812015-11-17 10:05:33 +00002619 2. Press Check VPN to check programmatic Vpn test.\n
Robin Leed4804f72016-10-14 17:12:23 +01002620 - Check Vpn setup is not allowed\n
2621 - If prompted to allow a VPN connection, press OK.\n\n
Mahaver Choprac0f70ce2015-10-16 12:40:39 +01002622 Use the Back button to return to this page.
2623 </string>
2624 <string name="device_owner_user_vpn_restriction_set">Set VPN restriction</string>
2625
Michal Karpinskid75827d2016-03-09 15:40:50 +00002626 <!-- Strings for DeviceOwnerBugreportTest -->
2627 <string name="device_owner_requesting_bugreport_tests">Device Owner Requesting Bugreport Tests</string>
2628 <string name="device_owner_requesting_bugreport_category">Device Owner Requesting Bugreport Tests</string>
2629 <string name="device_owner_requesting_bugreport_tests_info">
2630 The device owner requesting bugreport tests verify that a bugreport can be requested on a corporate owned device.\n
2631 Press below button first, follow steps described in the dialog that pops up,
2632 then proceed to the test cases.\n
2633 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n
2634 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should
2635 be run last so that it does not interfere with other tests.
2636 </string>
2637 <string name="device_owner_request_bugreport">Request bugreport</string>
Michal Karpinski10ce8652016-03-09 18:34:12 +00002638 <string name="bugreport_sharing_declined">Bugreport sharing declined</string>
2639 <string name="bugreport_shared_successfully">Bugreport shared successfully</string>
Michal Karpinskid0243652016-04-22 14:09:48 +01002640 <string name="bugreport_already_in_progress">Bugreport is already being collected on this device</string>
2641 <string name="bugreport_failed_completing">Bugreport collection operation failed</string>
Michal Karpinskid75827d2016-03-09 15:40:50 +00002642 <string name="device_owner_bugreport_sharing_declined_while_being_taken">Sharing of requested bugreport declined while being taken</string>
2643 <string name="device_owner_bugreport_sharing_declined_while_being_taken_info">
2644 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation.
2645 Open the notifications panel and verify that:\n
2646 \n
2647 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n
Michal Karpinskid0243652016-04-22 14:09:48 +01002648 \n
2649 Press the \"Request bugreport\" button again to try to invoke a second bugreport sharing operation.
2650 Open the notifications panel and verify that:\n
2651 \n
2652 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport is already being collected on this device\" is present. Dismiss that notification.\n
Michal Karpinski10ce8652016-03-09 18:34:12 +00002653 - Tapping on the \"Taking bugreport...\" notification opens a dialog titled \"Share bug report?\", that contains a message \"Your IT admin requested a bug report to help troubleshoot this device. Apps and data may be shared, and your device may temporarily slow down.\" and two buttons - \"DECLINE\" and \"SHARE\".\n
Michal Karpinskid75827d2016-03-09 15:40:50 +00002654 \n
2655 Tap the \"DECLINE\" button and verify that:\n
2656 \n
2657 - \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n
2658 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport sharing declined\" is present.\n
2659 \n
2660 Dismiss the notifications and mark test as passed or failed.
2661 </string>
Michal Karpinski10ce8652016-03-09 18:34:12 +00002662 <string name="device_owner_bugreport_sharing_accepted_while_being_taken">Sharing of requested bugreport accepted while being taken</string>
2663 <string name="device_owner_bugreport_sharing_accepted_while_being_taken_info">
2664 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation.
2665 Open the notifications panel and verify that:\n
2666 \n
2667 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n
2668 - Tapping on the \"Taking bugreport...\" notification opens a dialog titled \"Share bug report?\", that contains a message \"Your IT admin requested a bug report to help troubleshoot this device. Apps and data may be shared, and your device may temporarily slow down.\" and two buttons - \"DECLINE\" and \"SHARE\".\n
2669 \n
2670 Tap the \"SHARE\" button and verify that:\n
2671 \n
2672 - \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n
2673 - Notification titled \"Sharing bugreport...\" with an indefinite progress bar is present.\n
2674 - After a few minutes (time necessary to wait for bugreport being collected) notification titled \"Sharing bugreport...\" is automatically dismissed and notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport shared successfully\" is present.\n
2675 \n
2676 Dismiss the notifications and mark test as passed or failed.
2677 </string>
2678 <string name="device_owner_bugreport_sharing_declined_after_having_been_taken">Sharing of requested bugreport declined after having been taken</string>
2679 <string name="device_owner_bugreport_sharing_declined_after_having_been_taken_info">
2680 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation.
2681 Open the notifications panel and verify that:\n
2682 \n
2683 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n
2684 \n
2685 Wait for a few minutes (time necessary for bugreport to be collected) and verify that:\n
2686 \n
2687 - \"Taking bugreport...\" notification with an indefinite progress bar is dismissed.\n
2688 - Notification titled \"Share bug report?\", that contains a message \"Your IT admin requested a bug report to help troubleshoot this device. Apps and data may be shared.\" and two buttons - \"DECLINE\" and \"SHARE\" is shown.\n
2689 \n
2690 Tap the \"DECLINE\" button and verify that:\n
2691 \n
2692 - Notification titled \"Share bug report?\" is dismissed.\n
2693 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport sharing declined\" is present.\n
2694 \n
2695 Dismiss the notifications and mark test as passed or failed.
2696 </string>
2697 <string name="device_owner_bugreport_sharing_accepted_after_having_been_taken">Sharing of requested bugreport accepted after having been taken</string>
2698 <string name="device_owner_bugreport_sharing_accepted_after_having_been_taken_info">
2699 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation.
2700 Open the notifications panel and verify that:\n
2701 \n
2702 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n
2703 \n
2704 Wait for a few minutes (time necessary for bugreport to be collected) and verify that:\n
2705 \n
2706 - \"Taking bugreport...\" notification with an indefinite progress bar is dismissed.\n
2707 - Notification titled \"Share bug report?\", that contains a message \"Your IT admin requested a bug report to help troubleshoot this device. Apps and data may be shared.\" and two buttons - \"DECLINE\" and \"SHARE\" is shown.\n
2708 \n
2709 Tap the \"SHARE\" button and verify that:\n
2710 \n
2711 - Notification titled \"Share bug report?\" is dismissed.\n
2712 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport shared successfully\" is present.\n
2713 \n
2714 Dismiss the notifications and mark test as passed or failed.
2715 </string>
Michal Karpinskid75827d2016-03-09 15:40:50 +00002716
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002717 <!-- Strings used for policy transparency test -->
2718 <string name="device_profile_owner_policy_transparency_test">Policy transparency test</string>
2719 <string name="device_profile_owner_policy_transparency_test_info">
2720 This test checks that if an admin has enforced a policy, we let the user know about this.\nSet the short and long support messages before proceeding with the tests.
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002721 </string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002722 <string name="policy_transparency_open_settings_label">Open settings</string>
2723 <string name="policy_transparency_short_support_msg_label">Set short support message</string>
2724 <string name="policy_transparency_long_support_msg_label">Set long support message</string>
2725 <string name="policy_transparency_set_msg">Set message</string>
2726 <string name="policy_transparency_clear_msg">Clear message</string>
2727 <string name="policy_transparency_set_default_msg">Set default message</string>
2728 <string name="policy_transparency_default_short_msg">
2729 This action is disabled by your administrator. Contact someone@example.com for support.
2730 </string>
2731 <string name="policy_transparency_default_long_msg">
2732 This profile or device is managed by CtsVerifier. You can contact tech
2733 support on:\n\n
2734 America: +1 555-0100\n\n
2735 APAC: +1 555-0100\n\n
2736 Europe: +1 555-0100\n\n
2737 Email: someone@example.com
2738 </string>
2739 <string name="policy_transparency_update_button_label">Update</string>
2740 <string name="dummy_input_method_label">Dummy input method</string>
2741 <string name="dummy_accessibility_service_label">Dummy accessibility service</string>
2742 <string name="policy_transparency_test_instructions">
2743 1. <xliff:g id="set_step" example="Set policy by turning the switch on">%1$s</xliff:g>\n
2744 2. Open Settings app by clicking the "Open settings" button below.\n
2745 3. Verify that performing the following action will trigger a support dialog:\n
2746 <xliff:g id="user_action" example="Adding an account">%2$s</xliff:g>.\n
2747 4. Verify that the support dialog displays the short support message set earlier.\n
2748 5. Verify that clicking the "More details" link will redirect to Device administrators
2749 page in Settings app which displays the long support message set earlier.\n
2750 </string>
2751 <string name="user_restriction_set_step">
2752 Set \'%s\' user restriction by turning on the switch below.
2753 </string>
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002754 <string name="disallow_add_user">Disallow add user</string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002755 <string name="disallow_add_user_action">Adding a new user</string>
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002756 <string name="disallow_adjust_volume">Disallow adjust volume</string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002757 <string name="disallow_adjust_volume_action">Adjusting the volume</string>
2758 <string name="disallow_apps_control">Disallow controlling apps</string>
2759 <string name="disallow_apps_control_action">DISABLE/UNINSTALL/FORCE STOP-ing any app in the managed device/profile other than CtsVerifier</string>
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002760 <string name="disallow_config_cell_broadcasts">Disallow config cell broadcasts</string>
2761 <string name="disallow_config_cell_broadcasts_action">Configuring cell broadcasts</string>
2762 <string name="disallow_config_credentials">Disallow config credentials</string>
2763 <string name="disallow_config_credentials_action">Configuring user credentials</string>
2764 <string name="disallow_config_mobile_networks">Disallow config mobile networks</string>
2765 <string name="disallow_config_mobile_networks_action">Configuring mobile networks</string>
2766 <string name="disallow_config_tethering">Disallow config tethering</string>
2767 <string name="disallow_config_tethering_action">Configuring tethering and portable hotspots</string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002768 <string name="disallow_config_wifi">Disallow config Wi-Fi</string>
2769 <string name="disallow_config_wifi_action">Modifying Wi-Fi configuration</string>
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002770 <string name="disallow_debugging_features">Disallow debugging features</string>
2771 <string name="disallow_debugging_features_action">Enabling developer options</string>
2772 <string name="disallow_factory_reset">Disallow factory reset</string>
2773 <string name="disallow_factory_reset_action">Factory resetting the device</string>
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002774 <string name="disallow_fun">Disallow fun</string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002775 <string name="disallow_fun_action">Opening android easter egg game by tapping repeatedly on the \'Android version\' option</string>
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002776 <string name="disallow_install_unknown_sources">Disallow install unknown sources</string>
Suprabh Shukla903d7a32017-03-22 17:00:24 -07002777 <string name="disallow_install_unknown_sources_action">Enabling \'Cts Verifier\' to install apps</string>
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002778 <string name="disallow_modify_accounts">Disallow modify accounts</string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002779 <string name="disallow_modify_accounts_action">Adding an account or removing an account (if you have already added one)</string>
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002780 <string name="disallow_network_reset">Disallow network reset</string>
2781 <string name="disallow_network_reset_action">Resetting network settings</string>
2782 <string name="disallow_outgoing_beam">Disallow outgoing beam</string>
2783 <string name="disallow_outgoing_beam_action">Switching on android beam</string>
2784 <string name="disallow_remove_user">Disallow remove user</string>
2785 <string name="disallow_remove_user_action">Removing other users</string>
Nicolas Prevotdcc81a32017-02-02 14:10:28 +00002786 <string name="disallow_remove_managed_profile">Disallow remove managed profile</string>
2787 <string name="disallow_remove_managed_profile_action">Removing the work profile. It shouldn\'t be possible neither from the Accounts screen nor the Device Administrators screen (after selecting the Device Administrator that corresponds to the badged version of \"CTS Verifier\")</string>
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002788 <string name="disallow_share_location">Disallow share location</string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002789 <string name="disallow_share_location_action">Turning on location sharing</string>
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002790 <string name="disallow_uninstall_apps">Disallow uninstall apps</string>
2791 <string name="disallow_uninstall_apps_action">Uninstalling applications other CtsVerifier</string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002792 <string name="disallow_keyguard_unredacted_notifications">Disallow lockscreen unredacted notification</string>
2793 <string name="disallow_keyguard_unredacted_notifications_set_step">Disallow unredacted notifications when device is locked by turning on the switch below</string>
2794 <string name="disallow_keyguard_unredacted_notifications_action">Selecting show all notification content when device is locked</string>
2795 <string name="disallow_keyguard_unredacted_notifications_widget_label">@string/disallow_keyguard_unredacted_notifications</string>
Sudheer Shanka43c57a52016-02-11 00:04:28 +00002796 <string name="set_auto_time_required">Set auto (network) time required</string>
2797 <string name="auto_time_required_set_step">Set auto time required policy by turning on the switch below</string>
2798 <string name="set_auto_time_required_action">Modifying date and time</string>
2799 <string name="set_auto_time_required_widget_label">@string/set_auto_time_required</string>
2800 <string name="set_lock_screen_info">Set lock screen info</string>
2801 <string name="lock_screen_info_set_step">Select a lock screen info by setting a non-empty message in the edittext below.</string>
2802 <string name="set_lock_screen_info_action">Modifying lock screen message</string>
2803 <string name="set_lock_screen_info_widget_label">@string/set_lock_screen_info</string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002804 <string name="set_maximum_time_to_lock">Set maximum time to lock</string>
2805 <string name="maximum_time_to_lock_set_step">
2806 Select a non-zero maximum time to lock value by setting a value in the edittext box below.
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002807 </string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002808 <string name="set_maximum_time_to_lock_action">Selecting maximum time to lock greater than the set value below</string>
2809 <string name="set_maximum_time_to_lock_widget_label">Set maximum time to lock (in Sec):</string>
2810 <string name="set_password_quality">Set password quality</string>
2811 <string name="password_quality_set_step">Set minimum password quality by selecting an option in the spinner below.</string>
2812 <string name="set_password_quality_action">Setting a password which does not meet the requirements of the password quality selected</string>
2813 <string name="set_password_quality_widget_label">@string/set_password_quality</string>
2814 <string name="password_quality_unspecified">Unspecified</string>
2815 <string name="password_quality_something">Something</string>
2816 <string name="password_quality_numeric">Numeric</string>
2817 <string name="password_quality_numeric_complex">Numeric (Complex)</string>
2818 <string name="password_quality_alphabetic">Alphabetic</string>
2819 <string name="password_quality_alphanumeric">Alphanumeric</string>
2820 <string name="password_quality_complex">Complex</string>
2821 <string name="set_permitted_accessibility_services">Set permitted accessibility services</string>
2822 <string name="permitted_accessibility_services_set_step">
Sudheer Shankad7df6ba2016-11-09 18:43:36 -08002823 Check that \'Dummy Accessibility service\' is not enabled in Settings and disallow \'Dummy Accessibility service\' from permitted accessibility services by turning on
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002824 the switch below.
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002825 </string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002826 <string name="set_permitted_accessibility_services_action">
2827 Enabling \'Dummy Accessibility service\' in the list of accessibility services
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002828 </string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002829 <string name="set_permitted_accessibility_services_widget_label">
2830 Allow only system accessibility services:
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002831 </string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002832 <string name="set_permitted_input_methods">Set permitted input methods</string>
2833 <string name="permitted_input_methods_set_step">
Sudheer Shankad7df6ba2016-11-09 18:43:36 -08002834 Check that \'Dummy Input method\' is not enabled in Settings and disallow \'Dummy Input method\' from permitted input methods by turning on the switch below.
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002835 </string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002836 <string name="set_permitted_input_methods_action">
Jim Kaye12507db2016-11-07 11:24:54 -08002837 Enabling \'Dummy Input method\' in the list of accessibility services
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002838 </string>
Sudheer Shanka16acbdd2016-02-08 14:23:04 +00002839 <string name="set_permitted_input_methods_widget_label">
2840 Allow only system input methods:
Mahaver Chopraf1279f52016-01-25 16:22:44 +00002841 </string>
2842
Bartosz Fabianowski4dbb1eb2016-12-01 19:13:33 +01002843 <!-- Strings used for enterprise privacy tests -->
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002844 <string name="enterprise_privacy_test">Managed device info tests</string>
2845 <string name="enterprise_privacy_page">Managed device info page</string>
Bartosz Fabianowski4dbb1eb2016-12-01 19:13:33 +01002846 <string name="enterprise_privacy_page_info">
2847 Please press the Go button to open Settings. Verify that:\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002848 1) There is an entry for managed device information.\n
Bartosz Fabianowskif8c45ef2017-01-20 19:34:31 +01002849 2) Tapping that entry opens a screen.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002850 3) In this screen, at a minimum, you are told your organization can:\n
Bartosz Fabianowskif8c45ef2017-01-20 19:34:31 +01002851 * Change settings on this device.\n
2852 * See data associated with your work account.\n
2853 * See the list of all apps on your device.\n
2854 * See usage of each app on your device.\n
2855 * Lock the device and change the password.\n
2856 * Wipe the device.\n
Bartosz Fabianowski4dbb1eb2016-12-01 19:13:33 +01002857 \n
2858 Use the Back button to return to this page.
2859 </string>
2860 <string name="enterprise_privacy_open_settings">Open Settings</string>
2861 <string name="enterprise_privacy_network_logging">Retrieve traffic logs</string>
2862 <string name="enterprise_privacy_network_logging_info">
2863 Please do the following:\n
2864 1) Press the Retrieve Traffic Logs button and record the time at which you did this.\n
2865 2) Wait one minute.\n
2866 3) Press the Open Settings button.\n
2867 4) In the screen that opens, verify that you are told traffic logs were last retrieved at the time you pressed the Retrieve Traffic Logs button in step (1).\n
2868 \n
2869 Use the Back button to return to this page.
2870 </string>
2871 <string name="enterprise_privacy_retrieve_network_logs">Retrieve Traffic Logs</string>
2872 <string name="enterprise_privacy_bug_report">Request bug report</string>
2873 <string name="enterprise_privacy_bug_report_info">
2874 Please do the following:\n
2875 1) Press the Request Bug Report button and record the time at which you did this.\n
2876 2) Wait one minute.\n
2877 3) Press the Open Settings button.\n
2878 4) In the screen that opens, verify that you are told a bug report was last requested at the time you pressed the Request Bug Report button in step (1).\n
2879 \n
2880 Use the Back button to return to this page.
2881 </string>
2882 <string name="enterprise_privacy_request_bug_report">Request Bug Report</string>
2883 <string name="enterprise_privacy_security_logging">Retrieve security logs</string>
2884 <string name="enterprise_privacy_security_logging_info">
2885 Please do the following:\n
2886 1) Press the Retrieve Security Logs button and record the time at which you did this.\n
2887 2) Wait one minute.\n
2888 3) Press the Open Settings button.\n
2889 4) In the screen that opens, verify that you are told security logs were last retrieved at the time you pressed the Retrieve Security Logs button in step (1).\n
2890 \n
2891 Use the Back button to return to this page.
2892 </string>
2893 <string name="enterprise_privacy_retrieve_security_logs">Retrieve Security Logs</string>
2894 <string name="enterprise_privacy_clear_organization">Clear Org</string>
2895 <string name="enterprise_privacy_set_organization">Set Org</string>
Bartosz Fabianowskic5716cc2017-01-13 21:13:42 +01002896 <string name="enterprise_privacy_enterprise_installed_apps">Enterprise-installed apps</string>
2897 <string name="enterprise_privacy_enterprise_installed_apps_info">
2898 Please do the following:\n
2899 1) You should have received NotificationBot.apk together with the CTS verifier. If you built the CTS verifier yourself, build the NotificationBot.apk by issuing the following command on the host:\n
2900 make NotificationBot\n
2901 2) Upload the NotificationBot.apk to your device by issuing the following command on the host:\n
2902 adb push /path/to/NotificationBot.apk /sdcard\n
2903 3) Press the Uninstall button.\n
2904 4) Press the Open Settings button.\n
2905 5) In the screen that opens, verify that you are not told that your administrator installed any apps.\n
2906 6) Use the Back button to return to this page.\n
2907 7) Press the Install button.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002908 8) Repeat steps (4) through (6), verifying that in step (5), you are told now that your administrator installed at least one app.\n
Bartosz Fabianowskic5716cc2017-01-13 21:13:42 +01002909 9) Press the Uninstall button.\n
2910 10) Issue the following command on the host:\n
2911 adb shell rm /sdcard/NotificationBot.apk
2912 </string>
2913 <string name="enterprise_privacy_install">Install</string>
2914 <string name="enterprise_privacy_uninstall">Uninstall</string>
Bartosz Fabianowski1d492ad72017-01-16 21:27:39 +01002915 <string name="enterprise_privacy_admin_granted_location_access">Location access permission</string>
2916 <string name="enterprise_privacy_admin_granted_location_access_info">
2917 Please do the following:\n
2918 1) Press the Reset button.\n
2919 2) Press the Open Settings button.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002920 3) In the screen that opens, verify that you are not told that your administrator has granted location access to any apps.\n
Bartosz Fabianowski1d492ad72017-01-16 21:27:39 +01002921 4) Use the Back button to return to this page.\n
2922 5) Press the Grant button.\n
Denis Kuznetsovecfd9b72017-03-10 16:41:14 +01002923 6) Press the Open Settings button.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002924 7) In the screen that opens, verify that you are told now that your administrator has granted location access to at least one app.\n
2925 8) Tap on that information. Verify that a list of apps which have location access shows.\n
2926 9) Verify that the list indicates CTS Verifier\'s location access was enabled by your administrator.\n
2927 10) Use the Back button to return to this page.\n
2928 11) Press the Reset button.
Bartosz Fabianowski1d492ad72017-01-16 21:27:39 +01002929 </string>
2930 <string name="enterprise_privacy_reset">Reset</string>
2931 <string name="enterprise_privacy_grant">Grant</string>
2932 <string name="enterprise_privacy_admin_granted_microphone_access">Microphone access permission</string>
2933 <string name="enterprise_privacy_admin_granted_microphone_access_info">
2934 Please do the following:\n
2935 1) Press the Reset button.\n
2936 2) Press the Open Settings button.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002937 3) In the screen that opens, verify that you are not told that your administrator has granted microphone access to any apps.\n
Bartosz Fabianowski1d492ad72017-01-16 21:27:39 +01002938 4) Use the Back button to return to this page.\n
2939 5) Press the Grant button.\n
Denis Kuznetsovecfd9b72017-03-10 16:41:14 +01002940 6) Press the Open Settings button.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002941 7) In the screen that opens, verify that you are told now that your administrator has granted microphone access to at least one app.\n
2942 8) Tap on that information. Verify that a list of apps that have microphone access shows.\n
2943 9) Verify that the list indicates CTS Verifier\'s microphone access was enabled by your administrator.\n
2944 10) Use the Back button to return to this page.\n
2945 11) Press the Reset button.
Bartosz Fabianowski1d492ad72017-01-16 21:27:39 +01002946 </string>
2947 <string name="enterprise_privacy_admin_granted_camera_access">Camera access permission</string>
2948 <string name="enterprise_privacy_admin_granted_camera_access_info">
2949 Please do the following:\n
2950 1) Press the Reset button.\n
2951 2) Press the Open Settings button.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002952 3) In the screen that opens, verify that you are not told that your administrator has granted camera access to any apps.\n
Bartosz Fabianowski1d492ad72017-01-16 21:27:39 +01002953 4) Use the Back button to return to this page.\n
2954 5) Press the Grant button.\n
Denis Kuznetsovecfd9b72017-03-10 16:41:14 +01002955 6) Press the Open Settings button.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01002956 7) In the screen that opens, verify that you are told now that your administrator has granted camera access to at least one app.\n
2957 8) Tap on that information. Verify that a list of apps that have camera access shows.\n
2958 9) Verify that the list indicates CTS Verifier\'s camera access was enabled by your administrator.\n
2959 10) Use the Back button to return to this page.\n
2960 11) Press the Reset button.
Bartosz Fabianowski1d492ad72017-01-16 21:27:39 +01002961 </string>
Bartosz Fabianowskif4603ae2017-01-20 13:53:48 +01002962 <string name="enterprise_privacy_default_apps">Default apps</string>
2963 <string name="enterprise_privacy_default_apps_info">
2964 Please do the following:\n
2965 1) Press the Reset button.\n
2966 2) Press the Open Settings button.\n
2967 3) In the screen that opens, verify that you are not told that your administrator set any default apps.\n
2968 4) Use the Back button to return to this page.\n
2969 5) Press the Set Default Apps button.\n
2970 6) Repeat steps (2) through (4), verifying that in step (3), you are told now that your administrator has set seven default apps.\n
2971 7) Press the Reset button.
2972 </string>
2973 <string name="enterprise_privacy_set_default_apps">Set Default Apps</string>
Bartosz Fabianowski9ce96032017-02-17 16:53:02 +01002974 <string name="enterprise_privacy_default_ime">Default keyboard</string>
2975 <string name="enterprise_privacy_default_ime_info">
2976 Please do the following:\n
2977 1) Press the Open Settings button.\n
2978 2) In the screen that opens, verify that you are not told the default keyboard has been set.\n
2979 3) Use the Back button to return to this page.\n
2980 4) Press the Set Keyboard button to set the default keyboard.\n
2981 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that the default keyboard has been set to CTS Verifier.\n
2982 6) Press the Finish button to clear the default keyboard.
2983 </string>
2984 <string name="enterprise_privacy_set_keyboard">Set Keyboard</string>
2985 <string name="enterprise_privacy_finish">Finish</string>
Bartosz Fabianowskib2a1d2d2017-01-09 20:33:02 +01002986 <string name="enterprise_privacy_always_on_vpn">Always-on VPN</string>
2987 <string name="enterprise_privacy_always_on_vpn_info">
2988 Please do the following:\n
2989 1) Press the Open Settings button.\n
2990 2) In the screen that opens, verify that you are not told that an always-on VPN is set.\n
2991 3) Use the Back button to return to this page.\n
2992 4) Press the Set VPN button to set an always-on VPN.\n
2993 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that an always-on VPN is set.\n
2994 6) Press the Finish button to clear the always-on VPN.
2995 </string>
2996 <string name="enterprise_privacy_set_always_on_vpn">Set VPN</string>
Bartosz Fabianowskib2a1d2d2017-01-09 20:33:02 +01002997 <string name="enterprise_privacy_comp_always_on_vpn">Always-on VPN (managed profile)</string>
2998 <string name="enterprise_privacy_comp_always_on_vpn_info">
2999 Please do the following:\n
3000 1) Press the Start button to create a work profile.\n
3001 2) Press the Open Settings button.\n
3002 3) In the screen that opens, verify that you are not told that an always-on VPN is set.\n
3003 4) Use the Back button to return to this page.\n
3004 5) Press the Set VPN button to set an always-on VPN in your work profile.\n
3005 6) Repeat steps (2) through (4), verifying that in step (3), you are told now that an always-on VPN is set in your work profile.\n
3006 7) Press the Finish button to remove the work profile and always-on VPN.
3007 </string>
3008 <string name="enterprise_privacy_start">Start</string>
Bartosz Fabianowskib45d6782017-01-11 14:39:12 +01003009 <string name="enterprise_privacy_global_http_proxy">Global HTTP Proxy</string>
3010 <string name="enterprise_privacy_global_http_proxy_info">
3011 Please do the following:\n
3012 1) Press the Open Settings button.\n
3013 2) In the screen that opens, verify that you are not told that a global HTTP proxy has been set.\n
3014 3) Use the Back button to return to this page.\n
3015 4) Press the Set Proxy button.\n
3016 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that a global HTTP proxy has been set.\n
3017 6) Press the Clear Proxy button.
3018 </string>
Bartosz Fabianowskid477b722017-03-08 10:45:26 +01003019 <string name="enterprise_privacy_ca_certs">Trusted CA certs</string>
3020 <string name="enterprise_privacy_ca_certs_info">
3021 Please do the following:\n
3022 1) Press the Open Settings button.\n
3023 2) In the screen that opens, verify that you are not told that your administrator installed trusted CA certs.\n
3024 3) Use the Back button to return to this page.\n
3025 4) Press the Install Cert button to install a trusted CA cert.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01003026 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that the administrator has installed at least one trusted CA cert.\n
Bartosz Fabianowskid477b722017-03-08 10:45:26 +01003027 6) Press the Finish button to clear the cert.
3028 </string>
3029 <string name="enterprise_privacy_install_cert">Install Cert</string>
3030 <string name="enterprise_privacy_comp_ca_certs">Trusted CA certs (managed profile)</string>
3031 <string name="enterprise_privacy_comp_ca_certs_info">
3032 Please do the following:\n
3033 1) Press the Start button to create a work profile.\n
3034 2) Press the Settings button.\n
3035 3) In the screen that opens, verify that you are not told that your administrator installed trusted CA certs.\n
3036 4) Use the Back button to return to this page.\n
3037 5) Press the Install Cert button to install a trusted CA cert in your work profile.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01003038 6) Repeat steps (2) through (4), verifying that in step (3), you are told now that the administrator has installed at least one trusted CA cert in your work profile.\n
Bartosz Fabianowskid477b722017-03-08 10:45:26 +01003039 7) Press the Finish button to remove the work profile and cert.
3040 </string>
3041 <string name="enterprise_privacy_settings">Settings</string>
Bartosz Fabianowskib45d6782017-01-11 14:39:12 +01003042 <string name="enterprise_privacy_set_proxy">Set Proxy</string>
3043 <string name="enterprise_privacy_clear_proxy">Clear Proxy</string>
Bartosz Fabianowskic573bc72017-02-15 15:17:31 +01003044 <string name="enterprise_privacy_failed_password_wipe">Wipe on authentication failure</string>
3045 <string name="enterprise_privacy_failed_password_wipe_info">
3046 Please do the following:\n
3047 1) Press the Open Settings button.\n
3048 2) In the screen that opens, verify that you are not told all device data will be deleted if you mistype your password too many times.\n
3049 3) Use the Back button to return to this page.\n
3050 4) Press the Set Limit button to set the maximum number of password attempts.\n
3051 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that all device data will be deleted if you mistype your password 100 times.\n
3052 6) Press the Finish button to clear the maximum number of password attempts.
3053 </string>
3054 <string name="enterprise_privacy_set_limit">Set Limit</string>
3055 <string name="enterprise_privacy_comp_failed_password_wipe">Wipe on authentication failure (managed profile)</string>
3056 <string name="enterprise_privacy_comp_failed_password_wipe_info">
3057 Please do the following:\n
3058 1) Press the Start button to create a work profile.\n
3059 2) Press the Open Settings button.\n
3060 3) In the screen that opens, verify that you are not told work profile data will be deleted if you mistype your password too many times.\n
3061 4) Use the Back button to return to this page.\n
3062 5) Press the Set Limit button to set the maximum number of password attempts.\n
Bartosz Fabianowski14ab6492017-03-24 12:09:35 +01003063 6) Repeat steps (2) through (4), verifying that in step (3), you are told now that work profile data will be deleted if you mistype your password 100 times.\n
Bartosz Fabianowskic573bc72017-02-15 15:17:31 +01003064 7) Press the Finish button to remove the work profile.
3065 </string>
Bartosz Fabianowski4dbb1eb2016-12-01 19:13:33 +01003066 <string name="enterprise_privacy_quick_settings">Quick settings disclosure</string>
3067 <string name="enterprise_privacy_quick_settings_info">
3068 Please do the following:\n
3069 1) Press the Clear Org button.\n
3070 2) Open and fully expand Quick Settings.\n
3071 3) Verify that at the bottom of Quick Settings, you are told the device is managed.\n
3072 4) Close Quick Settings.\n
3073 5) Press the Set Org button.\n
3074 6) Open and fully expand Quick Settings.\n
3075 7) Verify that at the bottom of Quick Settings, you are told the device is managed by \"Foo, Inc.\".\n
3076 8) Tap on the information.\n
3077 9) Verify that a dialog informing you about device monitoring opens.\n
3078 10) Tap the \"Learn more\" link.\n
3079 11) Verify that a screen informing you what your managing organization can do is shown.\n
3080 \n
3081 Use the Back button to return to this page.
3082 </string>
3083 <string name="enterprise_privacy_keyguard">Keyguard disclosure</string>
3084 <string name="enterprise_privacy_keyguard_info">
3085 Please do the following:\n
3086 1) Press the Open Settings button to open Settings.\n
3087 2) Navigate to \"Security\" &gt; \"Screen lock\" and select the first screen lock type that is not \"None\".\n
3088 3) Use the Back button to return to this page.\n
3089 4) Press the Clear Org button.\n
3090 5) Lock the device.\n
3091 6) Verify that on the lock screen, you are told the device is managed.\n
3092 7) Unlock the device.\n
3093 8) Press the Set Org button.\n
3094 9) Lock the device.\n
3095 10) Verify that on the lock screen, you are told the device is managed by \"Foo, Inc.\".\n
3096 11) Unlock the device.\n
3097 12) Repeat steps (1) through (11) for each screen lock type other than \"None\".
3098 </string>
Bartosz Fabianowski006d06b2017-01-18 17:31:18 +01003099 <string name="enterprise_privacy_add_account">Add account disclosure</string>
3100 <string name="enterprise_privacy_add_account_info">
3101 Please do the following:\n
3102 1) Press the Clear Org button.\n
3103 2) Press the Open Settings button.\n
3104 3) In the screen that opens, verify that you are told that the device is managed.\n
3105 4) Use the Back button to return to this page.\n
3106 5) Press the Set Org button.\n
3107 6) Press the Open Settings button.\n
3108 7) In the screen that opens, verify that you are told that the device is managed by \"Foo, Inc.\".\n
3109 8) Tap the \"Learn more\" link.\n
3110 9) Verify that a screen informing you what your managing organization can do is shown.\n
3111 11) Use the Back button to return to this page.
3112 </string>
Bartosz Fabianowskif4603ae2017-01-20 13:53:48 +01003113 <string name="enterprise_privacy_default_app">CTS Verifier Test</string>
Bartosz Fabianowski4dbb1eb2016-12-01 19:13:33 +01003114
phweiss82870092016-12-20 20:03:02 +01003115 <!-- Strings for Network Logging Tests -->
3116 <string name="device_owner_network_logging_ui">Network Logging UI</string>
3117 <string name="device_owner_network_logging_ui_info">Please do the following:\n
3118 1) Open and fully expand Quick Settings.\n
3119 2) Check that you are told that your device is managed.\n
3120 3) Close Quick Settings.\n
3121 4) Enable network logging by tapping on the left button below.\n
3122 5) Open Quick Settings again. Check that an icon appeared next to the text about device management.\n
3123 6) Verify that a notification including the same icon popped up, informing you that network logging has been enabled.\n
3124 7) Tap the notification.\n
3125 8) Verify that a dialog about device monitoring opens, and informs you about: the name of the app that manages this device, details about the device owner\'s capabilities, and information that the admin has activated network logging and can see all network traffic.\n
3126 9) Close the dialog.\n
3127 10) Tap the right button below to disable network logging.\n
3128 11) Verify that the notification disappeared.\n
3129 </string>
3130 <string name="device_owner_enable_network_logging_button">Enable Network Logging</string>
3131 <string name="device_owner_disable_network_logging_button">Disable Network Logging</string>
3132
Nicolas Prevotdcc81a32017-02-02 14:10:28 +00003133 <string name="comp_test">Corporate Owned Managed Profile</string>
3134 <string name="comp_provision_profile_dialog_title">Provision work profile</string>
3135 <string name="comp_provision_profile_dialog_text">Press the OK button to start the managed provisioning flow, and complete the flow to create a work profile</string>
3136
Matthew Williams547b8162014-10-15 10:18:11 -07003137 <!-- Strings for JobScheduler Tests -->
3138 <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>
3139
3140 <string name="js_idle_test">Idle Mode Constraints</string>
3141 <string name="js_start_test_text">Start test</string>
Jim Kaye12507db2016-11-07 11:24:54 -08003142 <string name="js_idle_instructions">Verify the behavior of the JobScheduler API for when the device is in idle mode. Simply follow the on-screen instructions.</string>
Matthew Williams547b8162014-10-15 10:18:11 -07003143 <string name="js_idle_description_1">Turn the screen off and then back on in order to begin.</string>
Shreyas Basarge52013e12015-11-05 17:02:27 +00003144 <string name="js_idle_continue_instruction">
3145 Switch off screen and wait for it to turn on to continue.
3146 </string>
Matthew Williams547b8162014-10-15 10:18:11 -07003147 <string name="js_idle_item_idle_off">Idle job does not execute when device is not idle.</string>
3148 <string name="js_idle_item_idle_on">Idle job does execute when device is forced into idle.</string>
3149
3150 <string name="js_charging_test">Charging Constraints</string>
Jim Kaye12507db2016-11-07 11:24:54 -08003151 <string name="js_charging_instructions">Verify the behavior of the JobScheduler API for when the device is on power and unplugged from power. Simply follow the on-screen instructions.</string>
Shreyas Basarge2c439012015-11-16 23:10:34 +00003152 <string name="js_charging_description_1">Plug in the charger if it isn\'t already plugged in.</string>
Matthew Williams547b8162014-10-15 10:18:11 -07003153 <string name="js_charging_off_test">Device not charging will not execute a job with a charging constraint.</string>
3154 <string name="js_charging_on_test">Device when charging will execute a job with a charging constraint.</string>
Shreyas Basarge2c439012015-11-16 23:10:34 +00003155 <string name="js_charging_description_2">After the above test has passed, remove the charger to continue. If the above failed, you can simply fail this test.</string>
Jim Kaye12507db2016-11-07 11:24:54 -08003156 <string name="js_charging_description_3">Device is plugged in. Please wait while it gets into stable charging state.</string>
Christopher Tate4bd92822017-03-06 17:44:39 -08003157 <string name="js_charging_description_4">There seems to be a problem with your charger. Please try again.</string>
Matthew Williams547b8162014-10-15 10:18:11 -07003158
3159 <string name="js_connectivity_test">Connectivity Constraints</string>
Jim Kaye12507db2016-11-07 11:24:54 -08003160 <string name="js_connectivity_instructions">Verify the behavior of the JobScheduler API for when the device has no access to data connectivity. Simply follow the on-screen instructions.</string>
Matthew Williams547b8162014-10-15 10:18:11 -07003161 <string name="js_connectivity_description_1">Disable WiFi and Cellular data to begin.</string>
3162 <string name="js_unmetered_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string>
3163 <string name="js_any_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string>
3164 <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 -04003165
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003166 <!-- String for the bundled TV app Tests -->
Wonsik Kim18aa5752014-10-30 00:47:57 +09003167
Dongwon Kang83efe7e2015-07-17 15:01:35 -07003168 <string name="tv_input_discover_test">3rd-party TV input test</string>
Wonsik Kimf16680b2014-11-20 23:11:16 +09003169 <string name="tv_input_discover_test_info">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003170 Verify that the bundled TV app launches via Intent and calls the proper API to discover
Dongwon Kang83efe7e2015-07-17 15:01:35 -07003171 3rd-party TV inputs.
Wonsik Kimf16680b2014-11-20 23:11:16 +09003172 </string>
Wonsik Kim18aa5752014-10-30 00:47:57 +09003173 <string name="tv_input_discover_test_go_to_setup">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003174 Select the \"Launch TV app\" button and set up the newly installed TV input:
Wonsik Kimf16680b2014-11-20 23:11:16 +09003175 \"CTS Verifier\".
Wonsik Kim18aa5752014-10-30 00:47:57 +09003176 </string>
3177 <string name="tv_input_discover_test_verify_setup">
3178 Setup activity must have been started.
3179 </string>
3180 <string name="tv_input_discover_test_tune_to_channel">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003181 Select the \"Launch TV app\" button and tune to the \"Dummy\" channel from \"CTS Verifier\"
3182 input. If necessary, configure the channel to be visible.
Wonsik Kim18aa5752014-10-30 00:47:57 +09003183 </string>
3184 <string name="tv_input_discover_test_verify_tune">
3185 Tune command must be called.
3186 </string>
Dongwon Kangf58fc082014-12-01 15:51:03 +09003187 <string name="tv_input_discover_test_verify_overlay_view">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003188 Verify that the overlay appears and displays the text \"Overlay View Dummy Text\" when you tune
3189 to the \"Dummy\" channel.
Dongwon Kangf58fc082014-12-01 15:51:03 +09003190 </string>
shubangb54c9ff2016-05-06 13:37:49 -07003191 <string name="tv_input_discover_test_verify_size_changed">
3192 Verify that video layout changes correctly according to the provided video track information,
3193 including pixel aspect ratio.
3194 </string>
Dongwon Kangaa1e8032015-06-01 15:13:06 +09003195 <string name="tv_input_discover_test_verify_global_search">
Dongwon Kang83efe7e2015-07-17 15:01:35 -07003196 Verify the TV app provides query results for 3rd-party input\'s channels and programs in
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003197 global search results.
Dongwon Kangaa1e8032015-06-01 15:13:06 +09003198 </string>
Dongwon Kang2ad14c92015-05-13 18:46:13 +09003199 <string name="tv_input_discover_test_go_to_epg">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003200 Select the \"Launch EPG\" button and locate the \"Dummy\" channel.
Dongwon Kang2ad14c92015-05-13 18:46:13 +09003201 </string>
3202 <string name="tv_input_discover_test_verify_epg">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003203 Do you see the programs named \"Dummy Program\" and their descriptions
Dongwon Kang2ad14c92015-05-13 18:46:13 +09003204 "Dummy Program Description" in the EPG?
3205 </string>
Jiabin4f532592016-03-30 16:41:33 +09003206 <string name="tv_input_discover_test_trigger_setup">
3207 Select the \"Launch setup\" button and verify if the bundled TV app shows the list of installed
3208 TV inputs for setup.
3209 </string>
3210 <string name="tv_input_discover_test_verify_trigger_setup">
3211 Do you see the \"CTS Verifier\" input in the list?
3212 </string>
Wonsik Kim18aa5752014-10-30 00:47:57 +09003213
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003214 <string name="tv_parental_control_test">TV app parental controls test</string>
Wonsik Kimf16680b2014-11-20 23:11:16 +09003215 <string name="tv_parental_control_test_info">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003216 Verify that the bundled TV app calls the parental controls API.
Wonsik Kimf16680b2014-11-20 23:11:16 +09003217 </string>
3218 <string name="tv_parental_control_test_turn_on_parental_control">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003219 Select the \"Launch TV app\" button and turn on the parental controls. If parental controls are
3220 on already, turn it off and on again.
Wonsik Kimf16680b2014-11-20 23:11:16 +09003221 </string>
3222 <string name="tv_parental_control_test_verify_receive_broadcast1">
3223 TV input service must have received ACTION_PARENTAL_CONTROLS_ENABLED_CHANGED broadcast.
3224 </string>
shubang07530b82016-04-13 10:11:03 -07003225 <string name="tv_parental_control_test_check_parental_controls_switch">
3226 Is there an option to turn off parental controls on this device?
3227 </string>
Wonsik Kimf16680b2014-11-20 23:11:16 +09003228 <string name="tv_parental_control_test_block_tv_ma">
Dongwon Kang98a61e22016-08-11 18:02:12 -07003229 Select the \"Launch TV app\" button and block the \"Custom Rating\" for \"CtsVerifier\" rating
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003230 system in the parental control settings. If the rating system is disabled by default, enable it.
Dongwon Kang98a61e22016-08-11 18:02:12 -07003231 If the \"Custom Rating\" is already blocked, unblock it, save, and then block again.
Wonsik Kimf16680b2014-11-20 23:11:16 +09003232 </string>
3233 <string name="tv_parental_control_test_verify_receive_broadcast2">
3234 TV input service must have received ACTION_BLOCKED_RATINGS_CHANGED broadcast.
3235 </string>
3236 <string name="tv_parental_control_test_block_unblock">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003237 Select the \"Launch TV app\" button; verify that the channel is blocked.
3238 Try to unblock the screen by entering PIN; verify that it\'s unblocked.
Wonsik Kimf16680b2014-11-20 23:11:16 +09003239 </string>
3240
shubang07530b82016-04-13 10:11:03 -07003241 <string name="tv_parental_control_turn_off_disabled">No</string>
3242 <string name="tv_parental_control_turn_off_enabled">Yes</string>
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003243 <string name="tv_launch_tv_app">Launch TV app</string>
Dongwon Kang2ad14c92015-05-13 18:46:13 +09003244 <string name="tv_launch_epg">Launch EPG</string>
Jiabin4f532592016-03-30 16:41:33 +09003245 <string name="tv_launch_setup">Launch setup</string>
Wonsik Kimf16680b2014-11-20 23:11:16 +09003246 <string name="tv_channel_not_found">
3247 CtsVerifier channel is not set up. Please set up before proceeding.
3248 </string>
3249
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003250 <string name="tv_multiple_tracks_test">TV app closed captions and multi-audio test</string>
Wonsik Kimf5707312014-12-03 15:01:33 +09003251 <string name="tv_multiple_tracks_test_info">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003252 Verify that the bundled TV app calls the multi-track API.
Wonsik Kimf5707312014-12-03 15:01:33 +09003253 </string>
3254 <string name="tv_multiple_tracks_test_select_subtitle">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003255 Select the \"Launch TV app\" button. Verify that closed captions are off by default. Set closed
3256 caption language to English.
Wonsik Kimf5707312014-12-03 15:01:33 +09003257 </string>
3258 <string name="tv_multiple_tracks_test_verify_set_caption_enabled">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003259 Captions are enabled.
Wonsik Kimf5707312014-12-03 15:01:33 +09003260 </string>
3261 <string name="tv_multiple_tracks_test_verify_select_subtitle">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003262 The English closed caption track should be selected.
Wonsik Kimf5707312014-12-03 15:01:33 +09003263 </string>
3264 <string name="tv_multiple_tracks_test_select_audio">
Dongwon Kange1a4ddad2015-06-24 17:31:14 -07003265 Select the \"Launch TV app\" button. Verify that the audio track is English by default.
Wonsik Kimf5707312014-12-03 15:01:33 +09003266 Select Spanish audio track.
3267 </string>
3268 <string name="tv_multiple_tracks_test_verify_select_audio">
3269 The Spanish audio track should be selected.
3270 </string>
3271
Chulwoo Lee19815cb2015-06-19 14:53:37 -07003272 <string name="tv_time_shift_test">TV app time shift test</string>
3273 <string name="tv_time_shift_test_info">
3274 This test verifies that the TV app invokes proper time shift APIs in the framwork.
3275 </string>
3276 <string name="tv_time_shift_test_pause_resume">
3277 Press the \"Launch TV app\" button. Verify that the playback control is available.
3278 Pause the playback and then resume it.
3279 </string>
3280 <string name="tv_time_shift_test_verify_resume_after_pause">
Chulwoo Lee5bea9ee2015-12-16 09:34:00 -08003281 The playback should resume after pause.
Chulwoo Lee19815cb2015-06-19 14:53:37 -07003282 </string>
3283 <string name="tv_time_shift_test_verify_position_tracking">
3284 The playback position tracking should be activated.
3285 </string>
3286 <string name="tv_time_shift_test_speed_rate">
3287 Press the \"Launch TV app\" button. Verify that the playback control is available.
3288 Rewind the playback and in a few seconds fast-forward it.
3289 </string>
3290 <string name="tv_time_shift_test_verify_rewind">
Chulwoo Lee5bea9ee2015-12-16 09:34:00 -08003291 The playback should rewind.
Chulwoo Lee19815cb2015-06-19 14:53:37 -07003292 </string>
3293 <string name="tv_time_shift_test_verify_fast_forward">
Chulwoo Lee5bea9ee2015-12-16 09:34:00 -08003294 The playback should fast-forward.
Chulwoo Lee19815cb2015-06-19 14:53:37 -07003295 </string>
3296 <string name="tv_time_shift_test_seek">
3297 Press the \"Launch TV app\" button. Verify that the playback control is available.
3298 Seek to previous and then seek to next.
3299 </string>
3300 <string name="tv_time_shift_test_verify_seek_to_previous">
3301 The playback position should be moved to the previous position.
3302 </string>
3303 <string name="tv_time_shift_test_verify_seek_to_next">
3304 The playback position should be moved to the next position.
3305 </string>
3306
Daniel Xiea41d4972015-10-19 15:35:16 -07003307 <string name="tv_app_link_test">TV app app-link test</string>
3308 <string name="tv_app_link_test_info">
Chulwoo Lee5bea9ee2015-12-16 09:34:00 -08003309 Verify that the bundled TV app supports linking to channel apps. If a TV input service provides
3310 links for its specific channels, the TV app should show the links in a proper format.
Daniel Xiea41d4972015-10-19 15:35:16 -07003311 </string>
3312 <string name="tv_app_link_test_select_app_link">
3313 Select the \"Launch TV app\" button, then check if you can see a menu with \"Cts App-Link Text\"
3314 text in red background. If you see the link, select it to follow the link.
3315 </string>
3316 <string name="tv_app_link_test_verify_link_clicked">
3317 The app-link must have been clicked and the activity should be changed correctly.
3318 </string>
3319 <string name="tv_input_link_test_verify_link_interface">
3320 Do you see the app-link card similar to the image on the left?\n
Chulwoo Lee5bea9ee2015-12-16 09:34:00 -08003321 1) You should see the poster art image, but the color may be different.\n
Daniel Xiea41d4972015-10-19 15:35:16 -07003322 2) You should see the text \"Cts App-Link Text\".\n
3323 </string>
3324
Dongwon Kangf58fc082014-12-01 15:51:03 +09003325 <string name="overlay_view_text">Overlay View Dummy Text</string>
Dongwon Kang98a61e22016-08-11 18:02:12 -07003326 <string name="custom_rating">Example of input app specific custom rating.</string>
Wonsik Kim18aa5752014-10-30 00:47:57 +09003327
Chris Wren451834f2014-10-28 14:32:45 -04003328 <!-- A list of fully-qualified test classes that should not be run. -->
3329 <string-array name="disabled_tests" />
Jason Monk5ece9982015-01-21 15:17:20 -05003330
3331 <!-- Strings for screen pinning test -->
3332 <string name="screen_pinning_test">Screen Pinning Test</string>
3333 <string name="screen_pin_instructions">Pressing next will prompt you to enter screen pinning, allow this app to enter screen pinning.</string>
3334 <string name="screen_pin_check_pinned">Press Next to verify the app is pinned.</string>
3335 <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>
3336 <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>
3337 <string name="screen_pinning_done">All tests completed successfully.</string>
3338
3339 <string name="error_screen_no_longer_pinned">The screen was no longer pinned.</string>
3340 <string name="error_screen_already_pinned">Cannot start the test with the screen already pinned.</string>
3341 <string name="error_screen_pinning_did_not_start">Screen was not pinned.</string>
3342 <string name="error_screen_pinning_did_not_exit">Screen was not unpinned.</string>
3343 <string name="error_screen_pinning_couldnt_exit">Could not exit screen pinning through API.</string>
Paul McLean365be3a2015-06-04 12:40:18 -07003344
Daniel Xiea41d4972015-10-19 15:35:16 -07003345 <!-- Audio Devices Notifcations Tests -->
3346 <string name="audio_out_devices_notifications_test">Audio Output Devices Notifications Test</string>
3347 <string name="audio_out_devices_notification_instructions">
Paul McLean365be3a2015-06-04 12:40:18 -07003348 Click the "Clear Messages" button then connect and disconnect a wired headset.
3349 Note if the appropriate notification messages appear below.
3350 </string>
Daniel Xiea41d4972015-10-19 15:35:16 -07003351 <string name="audio_in_devices_notifications_test">Audio Input Devices Notifications Test</string>
3352 <string name="audio_in_devices_notification_instructions">
3353 Click the "Clear Messages" button then connect and disconnect a microphone or wired headset.
3354 Note if the appropriate notification messages appear below.
3355 </string>
Paul McLean365be3a2015-06-04 12:40:18 -07003356 <string name="audio_dev_notification_clearmsgs">Clear Messages</string>
3357 <string name="audio_dev_notification_connectMsg">CONNECT DETECTED</string>
3358 <string name="audio_dev_notification_disconnectMsg">DISCONNECT DETECTED</string>
Paul McLeanaf80c872015-06-05 07:48:15 -07003359
Daniel Xiea41d4972015-10-19 15:35:16 -07003360 <string name="audio_input_routingnotifications_test">Audio Input Routing Notifications Test</string>
3361 <string name="audio_input_routingnotification_instructions">
3362 Click on the "Record" button in the AudioRecord Routing Notifications section below to
3363 start recording. Insert a wired headset or microphone. Observe a message acknowledging the
3364 rerouting event below. Remove the wired headset and observe the new routing message.
3365 Click on the "Stop" button to stop recording.\n
3366 </string>
3367 <string name="audio_output_routingnotifications_test">Audio Output Routing Notifications Test</string>
3368 <string name="audio_output_routingnotification_instructions">
3369 Click on the "Play" button in the AudioTrack Routing Notifications section below to
Paul McLeanaf80c872015-06-05 07:48:15 -07003370 start (silent) playback. Insert a wired headset. Observe a message acknowledging the
3371 rerouting event below. Remove the wired headset and observe the new routing message.
3372 Click on the "Stop" button to stop playback.\n
Paul McLeanaf80c872015-06-05 07:48:15 -07003373 </string>
3374 <string name="audio_routingnotification_playBtn">Play</string>
3375 <string name="audio_routingnotification_playStopBtn">Stop</string>
3376 <string name="audio_routingnotification_recBtn">Record</string>
3377 <string name="audio_routingnotification_recStopBtn">Stop</string>
3378 <string name="audio_routingnotification_playHeader">AudioTrack Routing Notifications</string>
3379 <string name="audio_routingnotification_recHeader">AudioRecord Routing Notifications</string>
3380 <string name="audio_routingnotification_trackRoutingMsg">AudioTrack rerouting</string>
3381 <string name="audio_routingnotification_recordRoutingMsg">AudioRecord rerouting</string>
Ricardo Garciae908b092015-07-13 19:10:50 -07003382
Paul McLeanc713de72017-01-12 15:21:16 -07003383 <!-- USB Audio Peripheral Tests -->
3384 <string name="profileLabel">Profile</string>
3385 <string name="connectedPeripheral">Connected Peripheral</string>
3386 <string name="audio_uap_attribs_test">USB Audio Peripheral Attributes Test</string>
3387 <string name="uapPeripheralProfileStatus">Peripheral Profile Status</string>
3388
3389 <string name="audio_uap_play_test">USB Audio Peripheral Play Test</string>
Paul McLeanfaf9ad62017-03-09 12:38:37 -07003390 <string name="uapPlayTestInstructions">Connect the USB Audio Interface Peripheral and press the
3391 PLAY button below. Verify that a tone is correctly played.</string>
Paul McLeanc713de72017-01-12 15:21:16 -07003392 <string name="audio_uap_play_playBtn">Play</string>
3393 <string name="audio_uap_play_stopBtn">Stop</string>
3394
3395 <string name="audio_uap_record_test">USB Audio Peripheral Record Test</string>
3396 <string name="uapRecordTestInstructions">Connect the USB Audio Peripheral and press the RECORD or
3397 RECORD LOOPBACK button below. Verify that a tone is correctly played.</string>
3398 <string name="audio_uap_record_recordBtn">Record</string>
3399 <string name="audio_uap_record_recordLoopbackBtn">Record Loopback</string>
3400 <string name="audio_uap_record_stopBtn">Stop</string>
3401
3402 <string name="audio_uap_buttons_test">USB Audio Peripheral Buttons Test</string>
3403 <string name="uapButtonTestInstructions">Connect the USB Audio headset with buttons
3404 and press each transport/media button in turn.</string>
3405
3406 <string name="uapButtonsBtnALbl">Button A - play/pause</string>
3407 <string name="uapButtonsBtnBLbl">Button B - volume up (+)</string>
3408 <string name="uapButtonsBtnCLbl">Button C - volume down (-)</string>
3409 <string name="uapButtonsBtnDLbl">Button D - voice assist</string>
3410 <string name="uapButtonsRecognized">Recognized</string>
3411 <string name="uapButtonsNotRecognized">Not Recognized</string>
3412
Daniel Xiea41d4972015-10-19 15:35:16 -07003413 <!-- Audio general text -->
3414 <string name="audio_general_headset_port_exists">Does this device have a headset port?</string>
3415 <string name="audio_general_headset_no">No</string>
3416 <string name="audio_general_headset_yes">Yes</string>
Ricardo Garciae8a13b12015-10-30 14:14:29 -07003417 <string name="audio_general_deficiency_found">WARNING: Some results show potential deficiencies on the system.
3418 Please consider addressing them for a future release.</string>
Ricardo Garcia8cdf0172016-08-29 17:45:04 -07003419 <string name="audio_general_test_passed">Test Result: Successful</string>
ragob0d570c2016-05-16 14:48:34 -07003420 <string name="audio_general_test_failed">Test Result: Not Optimal</string>
rago86df6412015-12-02 11:44:26 -08003421 <string name="audio_general_default_false_string">false</string>
3422 <string name="audio_general_default_true_string">true</string>
ragobf40d842016-05-04 18:23:57 -07003423 <string name="audio_general_warning">Warning</string>
3424 <string name="audio_general_ok">Ok</string>
3425 <string name="audio_general_level_not_max">Audio Level is not maximum. Please check your device
3426 is set to max level for audio playback.</string>
Daniel Xiea41d4972015-10-19 15:35:16 -07003427
Ricardo Garciae908b092015-07-13 19:10:50 -07003428 <!-- Audio Loopback Latency Test -->
3429 <string name="audio_loopback_test">Audio Loopback Latency Test</string>
3430 <string name="audio_loopback_info">
Daniel Xiea41d4972015-10-19 15:35:16 -07003431 This test requires the Loopback Plug. Please connect a Loopback Plug into the headset
Ricardo Garciae908b092015-07-13 19:10:50 -07003432 connector, and proceed with the instructions on the screen.
3433 The system will measure the input-output audio latency by injecting a pulse on the output,
3434 and computing the distance between replicas of the pulse.
Daniel Xiea41d4972015-10-19 15:35:16 -07003435 You can vary the Audio Level slider to ensure the pulse will feed back at adequate levels.
Ricardo Garciae908b092015-07-13 19:10:50 -07003436 Repeat until a confidence level >= 0.6 is achieved.
3437 </string>
3438 <string name="audio_loopback_instructions">
3439 Please connect a "Loopback Plug" and press "Loopback Plug Ready".
3440 </string>
3441 <string name="audio_loopback_plug_ready_btn">Loopback Plug Ready</string>
3442 <string name="audio_loopback_instructions2">
3443 Set the audio level to a suitable value, then press Test button.
3444 It might require multiple tries until a confidence >= 0.6 is achieved.
3445 </string>
3446 <string name="audio_loopback_level_text">Audio Level</string>
3447 <string name="audio_loopback_test_btn">Test</string>
3448 <string name="audio_loopback_results_text">Results...</string>
3449
Ricardo Garcia9b2e1682015-07-29 15:36:05 -07003450 <!-- Audio Frequency Line Test -->
3451 <string name="audio_frequency_line_test">Audio Frequency Line Test</string>
3452 <string name="audio_frequency_line_info">
Nicholas Sauer8cf9bdb2015-08-23 13:49:53 -07003453 The system will measure the frequency response of the left and right line outputs,
Ricardo Garciaea8dd5d2015-08-07 19:10:18 -07003454 by feeding them back thru the microphone conection with the loopback jack.
Ricardo Garcia9b2e1682015-07-29 15:36:05 -07003455 This test requires the Loopback Plug. Please connect a Loopback Plug on the headset
3456 connector, and proceed with the instructions on the screen.
Ricardo Garciaea8dd5d2015-08-07 19:10:18 -07003457 </string>
Ricardo Garcia9b2e1682015-07-29 15:36:05 -07003458 <string name="audio_frequency_line_instructions">
3459 Please connect a "Loopback Plug" and press "Loopback Plug Ready".
3460 </string>
3461 <string name="audio_frequency_line_plug_ready_btn">Loopback Plug Ready</string>
3462
3463 <string name="audio_frequency_line_test_btn">Test</string>
3464 <string name="audio_frequency_line_results_text">Results...</string>
Ricardo Garciaa01018e2015-08-13 10:20:18 -05003465
Ricardo Garciaea8dd5d2015-08-07 19:10:18 -07003466 <!-- Audio Frequency Speaker Test -->
3467 <string name="audio_frequency_speaker_test">Audio Frequency Speaker Test</string>
3468 <string name="audio_frequency_speaker_info">
3469 This test requires an external USB reference microphone. Please connect the USB microphone and proceed with the instructions on the screen.
Daniel Xiea41d4972015-10-19 15:35:16 -07003470 The system will measure frequency response of the left and right speakers (if there are two speakers), or the response of the mono speaker twice.
Ricardo Garciaea8dd5d2015-08-07 19:10:18 -07003471 </string>
3472 <string name="audio_frequency_speaker_instructions">
Ricardo Garciaa01018e2015-08-13 10:20:18 -05003473 Please connect an USB reference microphone and press "USB Reference microphone ready"
Ricardo Garciaea8dd5d2015-08-07 19:10:18 -07003474 </string>
3475 <string name="audio_frequency_speaker_usb_status">Waiting for USB microphone...</string>
3476 <string name="audio_frequency_speaker_mic_ready_btn">USB Reference microphone ready</string>
Ricardo Garciaa01018e2015-08-13 10:20:18 -05003477 <string name="audio_frequency_speaker_mic_ready_text">USB Audio device detected\n\nPlease set up Device Under test
Ricardo Garciaea8dd5d2015-08-07 19:10:18 -07003478 in quiet room, and Microphone 20 cms perpendicular to center of screen, then press TEST</string>
3479 <string name="audio_frequency_speaker_mic_not_ready_text">"No USB Audio device detected. Please reconnect."</string>
3480 <string name="audio_frequency_speaker_test_btn">Test</string>
3481 <string name="audio_frequency_speaker_results_text">Results...</string>
Ricardo Garciaa01018e2015-08-13 10:20:18 -05003482
3483 <!-- Audio Frequency Microphone Test -->
3484 <string name="audio_frequency_mic_test">Audio Frequency Microphone Test</string>
3485 <string name="audio_frequency_mic_info">
3486 This test requires an external USB reference microphone and external speakers.
3487 Please use the headphone connector to connect external speakers. Position the device 40 cms
3488 from the speakers and proceed with the instructions on the screen.
3489 The system will measure frequency response of the built in microphone.
3490 </string>
3491 <string name="audio_frequency_mic_instructions">
3492 Please connect external speakers using the headphone connector. Please unplug any USB audio device (if any)
3493 </string>
3494 <string name="audio_frequency_mic_speakers_ready_btn">External speakers ready</string>
3495 <string name="audio_frequency_mic_speakers_ready_status">...</string>
3496 <string name="audio_frequency_mic_instructions2">
3497 Please position the speakers 40 cms from the device under test and press TEST 1
3498 </string>
3499 <string name="audio_frequency_mic_test1_btn">Test 1</string>
3500 <string name="audio_frequency_mic_usb_status">Waiting for USB microphone...</string>
3501 <string name="audio_frequency_mic_connect_mic">Please Connect USB microphone, position it next to
3502 the built in microphone in the device and press USB reference microphone</string>
3503 <string name="audio_frequency_mic_mic_ready_btn">USB Reference microphone ready</string>
3504 <string name="audio_frequency_mic_mic_ready_text">USB Audio device detected\n\nPlease set up Device Under test
3505 in quiet room, and Microphone 20 cms perpendicular to center of screen, then press TEST</string>
3506 <string name="audio_frequency_mic_mic_not_ready_text">"No USB Audio device detected. Please reconnect."</string>
3507 <string name="audio_frequency_mic_test2_btn">Test 2</string>
3508 <string name="audio_frequency_mic_results_text">Results...</string>
Ricardo Garcia9b2e1682015-07-29 15:36:05 -07003509
rago86df6412015-12-02 11:44:26 -08003510 <!-- Audio Frequency Unprocessed Test -->
3511 <string name="audio_frequency_unprocessed_test">Audio Frequency Unprocessed Test</string>
3512 <string name="audio_frequency_unprocessed_info">
Ricardo Garcia8cdf0172016-08-29 17:45:04 -07003513 This test requires an external USB reference microphone, external speakers and a Sound Pressure Level meter.
3514 You can play the test signals from the device under test or from a secondary device.
3515 Follow the instructions on the screen to measure the frequency response for the built in microphone
3516 using UNPROCESSED audio source.
3517 If the Audio Frequency Unprocessed feature is defined in this system, success in all tests is mandatory to pass.
3518 If the feature is not defined, measurements are still needed, but success in all of them is not mandatory to pass.
rago86df6412015-12-02 11:44:26 -08003519 </string>
Ricardo Garcia8cdf0172016-08-29 17:45:04 -07003520 <string name="audio_frequency_unprocessed_defined">Audio Frequency Unprocessed feature is defined. Success in all tests is mandatory to pass</string>
3521 <string name="audio_frequency_unprocessed_not_defined">Audio Frequency Unprocessed feature is NOT defined. Success in all test is NOT mandatory to pass</string>
3522
3523 <string name="unprocessed_play">Play</string>
3524 <string name="unprocessed_stop">Stop</string>
3525
3526 <string name="unprocessed_test_tone_instructions">TEST TONE: Press [PLAY] to play tone at 1 Khz. Measure sound SPL to be 94 dB
3527 right next to microphone under test. Press [TEST]</string>
3528 <string name="unprocessed_test_tone_btn">Test</string>
3529 <string name="unprocessed_test_tone_result">Results...</string>
3530
3531 <string name="unprocessed_test_noise_instructions">TEST NOISE: Position speakers 40 cms from device under test.
3532 Press [PLAY] to play broadband white noise. Press [TEST]</string>
3533 <string name="unprocessed_test_noise_btn">Test</string>
3534 <string name="unprocessed_test_noise_result">Results...</string>
3535
3536 <string name="unprocessed_test_usb_background_instructions">TEST USB BACKGROUND: Connect USB microphone and position it right next to microphone under test.
3537 No source of noise should be active during this test. Press [TEST]</string>
3538 <string name="unprocessed_test_usb_background_btn">Test</string>
3539 <string name="unprocessed_test_usb_background_result">Results...</string>
3540
phweiss82870092016-12-20 20:03:02 +01003541 <string name="unprocessed_test_usb_noise_instructions">TEST USB NOISE: Connect USB microphone and position it right next to microphone under test.
Ricardo Garcia8cdf0172016-08-29 17:45:04 -07003542 Position speakers 40 cms from device under test. Press [PLAY] to play broadband white noise. Press [TEST]</string>
3543 <string name="unprocessed_test_usb_noise_btn">Test</string>
3544 <string name="unprocessed_test_usb_noise_result">Results...</string>
3545
3546 <string name="unprocessed_test_global_result">Global Results...</string>
rago86df6412015-12-02 11:44:26 -08003547
clchen@google.com293c5962016-05-27 13:20:29 -07003548 <!-- Strings for 6DoF test -->
3549 <string name="six_dof_test">6DoF Test</string>
3550 <string name="action_settings">Settings</string>
3551 <string name="start">Start</string>
3552 <string name="motion_tracking_permission">"Motion Tracking permission needed!"</string>
3553 <string name="translations">Translations:</string>
3554 <string name="rotations">Rotations:</string>
3555 <string name="action_place_marker">Place Marker</string>
3556 <string name="markers">Markers:\n</string>
3557 <string name="title_activity_cts">CTSActivity</string>
3558 <string name="stop">Stop!</string>
3559 <string name="stop_message">Mark where you are standing with something like a piece of card and
3560 then press ready to record this waypoint
3561 </string>
3562 <string name="ready">Ready</string>
3563 <string name="initial">First Waypoint</string>
3564 <string name="phase1_initial_message">When you are ready to place your first waypoint, place a
3565 marker at the devices current location. Use something that will allow you to put the device
3566 in the exact same position and orientation on the second lap. Then, while the device is on
3567 the marker, click the turquoise action button to record the first waypoint.\n\nStart walking
3568 in a direction. The button will appear again when you have walked far enough. Place a marker
3569 at the device\'s location and press the button to record a waypoint. You cannot place
3570 waypoints in a straight line, so for your 3rd waypoint turn 90 degrees and walk in a
3571 direction that will make a triangle out of your 3 waypoints.
3572 </string>
3573 <string name="phase2_initial_message">You now need to visit each waypoint, clicking the
3574 turquoise action button at each one. You need to reach each waypoint in 20 seconds. While
3575 you are on your way to the waypoints, the camera preview will rotate. You will need to
3576 rotate the device to match the rotation of the camera preview. A box will be shown to help
Jim Kaye12507db2016-11-07 11:24:54 -08003577 you. It shows the device\'s current rotation and will change color based on whether you are
clchen@google.com293c5962016-05-27 13:20:29 -07003578 close enough to the required rotation. Red if you are failing, green if you are passing.
Jim Kaye12507db2016-11-07 11:24:54 -08003579 When you have reached the next waypoint, the device can be returned to its original
clchen@google.com293c5962016-05-27 13:20:29 -07003580 rotation.
3581 </string>
3582 <string name="last">Go back to the first waypoint</string>
3583 <string name="last_message">Now go back to the first waypoint and press ready to finish the
3584 first lap.
3585 </string>
3586 <string name="got_it">Got it!</string>
3587 <string name="lap2_instructions">Now, go to each waypoint (including your initial
3588 one) and click the turquoise action button. Then move on to the next waypoint and do the
3589 same.\nThe last waypoint should be the first waypoint again.
3590 </string>
3591 <string name="test1_pass2">Pass 2</string>
3592 <string name="results">Results</string>
3593 <string name="overall_instructions">These tests are designed to verify the correctness and
3594 accuracy of a 6DoF enabled device. There will be 3 phases to these tests, each testing a
Jim Kaye12507db2016-11-07 11:24:54 -08003595 different part of 6DoF functionality.
clchen@google.com293c5962016-05-27 13:20:29 -07003596 </string>
3597 <string name="phase1_description">This first test will test the accuracy of the device. It will
3598 ask you to mark out 4 waypoints and then return to the original waypoint to complete the
3599 lap. After this you will then need to do another lap without any HUD information. At the
3600 end, the pairs of waypoints and the path you travelled will be compared and you will be
3601 given a result.
3602 </string>
3603 <string name="phase2_description">This test will test the robustness of the device. Using the
3604 same 4 waypoints as before, you will need to do a lap, reaching each waypoint in the
3605 allotted time.\nWhile you are on your way to the waypoints, the camera preview will rotate.
3606 You will need to rotate the device to match the rotation of the camera preview. A box will
Jim Kaye12507db2016-11-07 11:24:54 -08003607 be shown to help you. It shows the device\'s current rotation and will change color based
clchen@google.com293c5962016-05-27 13:20:29 -07003608 on whether you are close enough to the required rotation. Red if you are failing, green if
3609 you are passing. When you have reached the next waypoint, the device can be returned to
Jim Kaye12507db2016-11-07 11:24:54 -08003610 its original rotation.
clchen@google.com293c5962016-05-27 13:20:29 -07003611 </string>
3612 <string name="phase3_description">Now we will test the AR capability of the device. Again, you
3613 will need to do a lap of the waypoints, but this time between each waypoint the device will
3614 overlay hoops that you must pass the device through as you go along.
3615 </string>
3616 <string name="distance">Distance from last waypoint:</string>
3617 <string name="obj_return_to_initial_waypoint">Return to initial waypoint</string>
3618 <string name="waypointPlaced">Waypoint placed!</string>
3619 <string name="undo">undo</string>
3620 <string name="distance_remaining">Distance Remaining:\n</string>
3621 <string name="waypoint_differences">Waypoints</string>
3622 <string name="path_differences">Paths</string>
3623 <string name="error_distance">Not far away enough from other waypoints!</string>
3624 <string name="error_area">Not enough area covered.</string>
3625 <string name="passed">Passed!</string>
3626 <string name="failed">Failed!</string>
3627 <string name="test_failed">Test Failed!</string>
3628 <string name="error_start_point">Not close enough to initial waypoint!</string>
3629 <string name="waypoint_distance">Waypoint %1$s: %2$s</string>
3630 <string name="total">Total %1$s</string>
3631 <string name="path">Path %1$s: %2$s</string>
3632 <string name="fail">Fail</string>
3633 <string name="pass">Pass</string>
3634 <string name="info">Info</string>
3635 <string name="coming_soon">Coming soon!</string>
3636 <string name="motion_tracking_invalid_state">Motion Tracking has entered an invalid state
3637 </string>
3638 <string name="action_xml">XML</string>
3639 <string name="error_null_fragment">UI fragment was null, couldn\'t do callback to listener
3640 </string>
3641 <string name="error_retained_fragment_null">DataFragment is null</string>
3642 <string name="time_remaining">%1$s seconds remaining to get to next waypoint</string>
3643 <string name="action_skip_to_2nd">Skip to 2nd Test</string>
3644 <string name="failed_pause_resume">Test Failed because Test Activity was paused</string>
3645 <string name="action_overlapping_outlines">Overlapping Outlines</string>
3646 <string name="action_overlapping_filled">Overlapping Filled</string>
3647 <string name="time">Time</string>
3648 <string name="rotation_result">Rotation</string>
3649 <string name="action_separate_outlines">Separate Outlines</string>
3650 <string name="action_separate_filled">Separate Filled</string>
3651 <string name="action_one">One Rectangle</string>
3652 <string name="rotation_mode">Change rotation mode</string>
3653 <string name="phase3_initial_message">Go through the rings as you visit waypoints.</string>
3654 <string name="rings">Rings</string>
3655 <string name="rings_entered">Rings collected %1$s/%2$s</string>
3656 <string name="error_rings_not_entered">You haven\'t collected all the rings in this path!
3657 </string>
3658 <string name="save">Save</string>
3659
3660 <string-array name="initial_waypoint">
3661 <item>Find a place for your first waypoint</item>
3662 <item>Go to initial waypoint</item>
3663 </string-array>
3664
3665 <string-array name="next_waypoint">
3666 <item>Find a suitable place for waypoint 0</item>
3667 <item>Go to waypoint 0</item>
3668 </string-array>
3669
3670 <string-array name="phase">
3671 <item>Phase 1</item>
3672 <item>Phase 2</item>
3673 <item>Phase 3</item>
3674 </string-array>
3675
3676 <string-array name="phase_descriptions">
3677 <item>@string/phase1_description</item>
3678 <item>@string/phase2_description</item>
3679 <item>@string/phase3_description</item>
3680 </string-array>
3681
Ta-wei Yen87b76232016-12-15 15:42:34 -08003682 <!-- Strings for setting and restoring default dialer for voicemail tests -->
Ta-wei Yen3f78d2e2016-11-16 10:45:50 -08003683 <string name="voicemail_restore_default_dialer_description">(Optional) restore the default dialer setting</string>
3684 <string name="voicemail_restore_default_dialer_no_default_description">(Optional) restore the default dialer by going to settings-> apps -> cogwheel -> Phone app</string>
3685 <string name="voicemail_restore_default_dialer_button">Restore the default dialer"</string>
3686 <string name="voicemail_default_dialer_already_set">Default dialer already set</string>
3687 <string name="voicemail_default_dialer_already_restored">Default dialer already restored</string>
Ta-wei Yen87b76232016-12-15 15:42:34 -08003688 <string name="voicemail_set_default_dialer_description">Before the test, the CTS verifier should be set to the default dialer</string>
3689 <string name="voicemail_set_default_dialer_button">Set CTS verifier as default dialer"</string>
3690
3691 <!-- Strings for voicemail broadcast test -->
3692 <string name="voicemail_broadcast_test">Voicemail Broadcast Test</string>
3693 <string name="voicemail_broadcast_instructions">This test verifies that the default dialer can intercept the voicemail notification. The test must be conducted on a SIM with visual voicemail disabled</string>
3694 <string name="voicemail_leave_voicemail">Send a voicemail to the device, CTS verifier should receive a voicemail notification broadcast</string>
3695 <string name="voicemail_broadcast_received">Voicemail broadcast Received</string>
3696
3697 <!-- Strings for VisualVoicemailService test -->
3698 <string name="visual_voicemail_service_test">VisualVoicemailService Test</string>
3699 <string name="visual_voicemail_service_instructions">This test verifies that the VisualVoicemailService can receive SIM inserted and removed events</string>
3700 <string name="visual_voicemail_service_remove_sim_before_test">Removed the SIM before starting the test. This test only applies to devices with hotswap-able SIM</string>
3701 <string name="visual_voicemail_service_remove_sim_ok">Ok</string>
3702 <string name="visual_voicemail_service_remove_sim_not_applicable">Not applicable</string>
3703 <string name="visual_voicemail_service_insert_sim">Insert SIM</string>
3704 <string name="visual_voicemail_service_insert_sim_received">Service connection event received</string>
3705 <string name="visual_voicemail_service_remove_sim">Remove SIM</string>
3706 <string name="visual_voicemail_service_remove_sim_received">SIM removal event received</string>
3707
Ta-wei Yen5fa1b102017-01-24 19:55:01 -08003708 <!-- Strings for CallSettingsCheck test -->
3709 <string name="call_settings_check_test">Hide voicemail in call settings test</string>
3710 <string name="call_settings_check_instructions">This test verifies that the default dialer can
3711 hide voicemail settings in the call settings menu by using
3712 TelephonyManager.METADATA_HIDE_VOICEMAIL_SETTINGS_MENU
3713 </string>
3714 <string name="open_call_settings_explanation">Tap the button, and verify that \"voicemail\" does
3715 not exist in the call settings
3716 </string>
3717 <string name="open_call_settings">Open call settings</string>
3718 <string name="voicemail_hidden">\"Voicemail\" does not exist</string>
3719 <string name="voicemail_not_hidden">\"Voicemail\" exists</string>
3720
3721
3722 <!-- Strings for VoicemailSettingsCheck test -->
3723 <string name="ringtone_settings_check_test">Hide settings in voicemail test</string>
3724 <string name="ringtone_settings_check_instructions">This test verifies that voicemail settings
3725 accessible with public API can be hidden when launching
3726 TelephonyManager.ACTION_CONFIGURE_VOICEMAIL with EXTRA_HIDE_PUBLIC_SETTINGS.
3727 </string>
3728 <string name="open_voicemail_settings_explanation">Tap the button, ringtone and virbration
3729 settings does not exist in the voicemail settings.
3730 </string>
3731 <string name="open_voicemail_settings">Open voicemail settings</string>
3732 <string name="ringtone_hidden">Ringtone settings does not exist</string>
3733 <string name="ringtone_not_hidden">Ringtone settings exists</string>
Ta-wei Yen3f78d2e2016-11-16 10:45:50 -08003734
Paul McLeanfaf9ad62017-03-09 12:38:37 -07003735 <!-- USB Audio Peripheral Tests -->
3736 <string name="usbaudio_results_text">Results...</string>
3737
3738 <!-- USB Audio Peripheral Attributes Test -->
3739 <string name="usbaudio_attribs_test"> USB Audio Peripheral Attributes Test</string>
3740 <string name="usbaudio_attribs_info">
3741 This test requires that you have connected a mandated USB Audio Interface peripheral.
3742 If the discovered attributes of the peripheral matches the known attributes of the
3743 peripheral the test passes and the \"pass\" button will be enabled.
3744 </string>
3745
3746 <!-- USB Audio Peripheral Play Test -->
3747 <string name="usbaudio_play_test"> USB Audio Peripheral Play Test</string>
3748 <string name="usbaudio_play_info">
3749 This test requires that you have connected a mandated USB Audio Interface peripheral and
3750 some way to monitor the output. Press the \"Play\" button and verify that a tone is produced.
3751 </string>
3752
3753 <!-- USB Audio Peripheral Record Test -->
3754 <string name="usbaudio_record_test"> USB Audio Peripheral Record Test</string>
3755 <string name="usbaudio_record_info">
3756 This test requires that you have connected a mandated USB Audio Interface peripheral.
3757 Connect the outputs to the inputs (with patch cables). Start playback by pressing the
3758 \"Record Loopback\" button and verify that the recorded signal is displayed in the wave
3759 display view. ()It may be necessary to adjust the input controls on the peripheral).
3760 </string>
3761
3762 <!-- USB Audio Peripheral Buttons Test -->
3763 <string name="usbaudio_buttons_test"> USB Audio Peripheral Buttons Test</string>
3764 <string name="usbaudio_buttons_info">
3765 This test requires that you have connected a mandated USB Audio headset. Press each
3766 \"transport\" button and verify that it is recognized by the test.
3767 </string>
Tyler Gunn177db3a2017-03-30 21:17:42 -07003768
3769 <!-- Telecom tests -->
3770 <string name="telecom_enable_phone_account_test"> Telecom Enable Phone Account Test</string>
3771 <string name="telecom_enable_phone_account_info">
3772 This test verifies that a third party ConnectionService can be enabled by the user.
3773 </string>
3774 <string name="telecom_enable_phone_account_step_1">
3775 Click the button below to register a test PhoneAccount and ConnectionService.
3776 </string>
3777 <string name="telecom_enable_phone_account_register_button">Register Phone Account</string>
3778 <string name="telecom_enable_phone_account_step_2">
3779 In the Calling accounts settings, choose "All calling accounts" and enable the "CTS Verifier Test" account.
3780 On AOSP this is accessible from: Phone app > Settings > Calls > Calling Accounts.
3781 Once you have completed this step, return here and click the Confirm button.
3782 </string>
3783 <string name="telecom_enable_phone_account_confirm_button">Confirm</string>
Brian Muramatsu70a9e3f2010-06-25 15:27:09 -07003784</resources>