1<?xml version="1.0" encoding="utf-8"?> 2<!-- Copyright (C) 2010 The Android Open Source Project 3 4 Licensed under the Apache License, Version 2.0 (the "License"); 5 you may not use this file except in compliance with the License. 6 You may obtain a copy of the License at 7 8 http://www.apache.org/licenses/LICENSE-2.0 9 10 Unless required by applicable law or agreed to in writing, software 11 distributed under the License is distributed on an "AS IS" BASIS, 12 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 13 See the License for the specific language governing permissions and 14 limitations under the License. 15--> 16<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2"> 17 <string name="app_name">CTS Verifier</string> 18 <string name="module_id">noabi CtsVerifier</string> 19 20 <string name="title_version">CTS Verifier %1$s</string> 21 22 <string name="pass_button_text">Pass</string> 23 <string name="info_button_text">Info</string> 24 <string name="fail_button_text">Fail</string> 25 <string name="next_button_text">Next</string> 26 <string name="go_button_text">Go</string> 27 <string name="present_button_text">Device Present</string> 28 <string name="gone_button_text">Device Gone</string> 29 <string name="tests_completed_successfully">All tests completed successfully.</string> 30 31 <string name="retry_button_text">Retry</string> 32 <string name="finish_button_text">Finish</string> 33 <string name="fail_and_next_button_text">Fail and Next</string> 34 <string name="yes_string">Yes</string> 35 <string name="no_string">No</string> 36 37 <!-- Strings for CtsReportLog warning --> 38 <string name="reportlog_warning_title">CTS-Verifier Report Log</string> 39 <string name="reportlog_warning_body">Can\'t create folder for CTS-Verifier Report Logs. 40 \n\nPlease enable Report Log creation by exiting CTS Verifier and running the following commands: 41 \n\n<code>adb shell appops set com.android.cts.verifier android:read_device_identifiers allow</code> 42 \n\n<code>adb shell appops set com.android.cts.verifier MANAGE_EXTERNAL_STORAGE 0</code> 43 \n\nTest instructions are found in the \"Using CTS Verifier\" document found at 44 <a href="https://source.android.com/compatibility/cts/verifier">https://source.android.com/compatibility/cts/verifier</a> 45 </string> 46 47 <!-- Strings for TestListActivity --> 48 <string name="test_category_audio">Audio</string> 49 <string name="test_category_camera">Camera</string> 50 <string name="test_category_car">Car</string> 51 <string name="test_category_device_admin">Device Administration</string> 52 <string name="test_category_hardware">Hardware</string> 53 <string name="test_category_networking">Networking</string> 54 <string name="test_category_sensors">Sensors</string> 55 <string name="test_category_location">Location</string> 56 <string name="test_category_security">Security</string> 57 <string name="test_category_streaming">Streaming</string> 58 <string name="test_category_features">Features</string> 59 <string name="test_category_deskclock">Clock</string> 60 <string name="test_category_jobscheduler">Job Scheduler</string> 61 <string name="test_category_telecom">Telecom</string> 62 <string name="test_category_telephony">Telephony</string> 63 <string name="test_category_tunnel">Tunnel Mode</string> 64 <string name="test_category_tv">TV</string> 65 <string name="test_category_instant_apps">Instant Apps</string> 66 <string name="test_category_logcat">Read Logs</string> 67 <string name="test_category_display_cutout">DisplayCutout</string> 68 <string name="test_category_other">Other</string> 69 <string name="test_category_device_controls">Device controls</string> 70 <string name="clear">Clear</string> 71 <string name="test_results_clear_title">Remove all test results?</string> 72 <string name="test_results_clear_yes">Yes</string> 73 <string name="test_results_clear_cancel">Cancel</string> 74 <string name="test_results_cleared">Test results cleared.</string> 75 <string name="view">View</string> 76 <string name="test_results_error">Couldn\'t create test results report. Try running the 77 following command if you haven\'t yet.\n\"adb shell appops set com.android.cts.verifier 78 android:read_device_identifiers allow\" </string> 79 <string name="runtime_permissions_error">Please grant runtime permissions, otherwise, tests might fail.</string> 80 <string name="export">Export</string> 81 <string name="report_log_folder_name">ctsv-report-logs</string> 82 <string name="no_storage">Cannot save report to external storage, see log for details.</string> 83 <string name="no_storage_io_parser_exception">Cannot save report to external 84 storage, see log for details. Or try running the following command if 85 you haven\'t yet.\n\"adb shell appops set com.android.cts.verifier 86 MANAGE_EXTERNAL_STORAGE 0\"</string> 87 <string name="report_saved">Report saved to: %s</string> 88 89 <!-- Strings for IntentDrivenTestActivity --> 90 <string name="intent_not_resolved">Intent Not Resolved</string> 91 <string name="intent_not_resolved_info">The following intent could not be resolved: %1$s</string> 92 93 <!-- Strings for ReportViewerActivity --> 94 <string name="report_viewer">Report Viewer</string> 95 96 <string name="result_success">Test passed!</string> 97 <string name="result_failure">Test failed!</string> 98 99 <!-- String shared between BackupTestActivity and BackupAccessibilityTestActivity --> 100 <string name="bu_loading">Loading...</string> 101 <string name="bu_generate_error">Error occurred while generating test data...</string> 102 <string name="bu_settings">Settings</string> 103 104 <!-- Strings for BatterySaverTestActivity --> 105 <string name="battery_saver_test">Battery Saver Test</string> 106 <string name="battery_saver_test_info"> 107 This test verifies that the device provides a user affordance to enable and disable 108 Battery Saver feature. 109 </string> 110 <string name="battery_saver_test_no_battery_detected"> 111 No battery detected. This test will only work on devices that contain a battery. 112 </string> 113 <string name="battery_saver_test_unplug"> 114 Unplug the device or run \"adb shell dumpsys battery unplug\". 115 </string> 116 <string name="battery_saver_test_device_plugged_in"> 117 The device is still plugged in. 118 </string> 119 <string name="battery_saver_test_enable_bs"> 120 Look for a button that allows you to turn Battery Saver on and off. The button may be in the 121 Quick Settings section or on the Battery page of device settings. Use the button to turn 122 Battery Saver on. 123 </string> 124 <string name="battery_saver_test_disable_bs"> 125 Now use the button to turn Battery Saver off. 126 </string> 127 <string name="battery_saver_test_start_turn_bs_off"> 128 Turn Battery Saver off to begin the test. 129 </string> 130 <string name="battery_saver_test_bs_on">Battery Saver is on.</string> 131 <string name="battery_saver_test_bs_off">Battery Saver is off.</string> 132 133 <!-- Strings for Device Administration tests --> 134 <string name="da_policy_serialization_test">Policy Serialization Test</string> 135 <string name="da_policy_serialization_info">This test checks that a device policy is properly 136 saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create 137 a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the 138 device and verify that all rows in the policy list are green. Red items indicate policy 139 settings that were not loaded properly. 140 </string> 141 <string name="da_uninstall_test">Device Admin Uninstall Test</string> 142 <string name="da_uninstall_test_info">This test checks that an active device administrator 143 can be easily uninstalled from the application details screen in a way similar to other 144 apps. This test requires CtsEmptyDeviceAdmin.apk to be installed on the device. 145 </string> 146 <string name="da_tapjacking_test">Device Admin Tapjacking Test</string> 147 <string name="da_tapjacking_test_info">This test checks that an activity cannot tapjack the 148 user by obscuring the device admin details while prompting the user to activate the admin. 149 </string> 150 <string name="car_enable_garage_monitor">Enable Garage Mode Monitor</string> 151 <string name="car_garage_mode_test">Garage Mode Test</string> 152 <string name="car_garage_mode_test_desc"> 153 This test verifies that Garage Mode runs at the end of a drive.\n\n 154 <b>Important: Please enable Wi-Fi or other connectivity for test to pass.\n\n </b> 155 Touch "Enable Garage Mode Monitor" to launch the Garage Mode verifier.\n\n 156 Turn the vehicle off and exit the vehicle (or take the proprietary action that 157 initiates shut-down of the system).\n\n 158 Do not enter or disturb the vehicle for at least 15 minutes.\n\n 159 Enter the vehicle. Re-launch the CTS-Verifier app if it is not running.\n\n 160 If Garage Mode ran as required, the pass button will be enabled.</string> 161 <string name="car_component_power_on_policy_check">Verify Component Power On Policy</string> 162 <string name="car_component_power_off_policy_check">Verify Component Power Off Policy</string> 163 <string name="car_power_policy_test">Car Power Policy Test</string> 164 <string name="car_power_policy_test_desc"> 165 This test verifies that Wi-Fi, Bluetooth and Location settings UI behaviors with respect 166 to their power policy. If the policy sets components power off, the component settings UI 167 shall be disabled. Otherwise, the settings UI shall be enabled as default.\n\n 168 First execute the\n 169 " adb shell cmd car_service apply-cts-verifier-power-off-policy"\n 170 adb shell command first and then sequentialy click first 4 buttons to check each component 171 settings UI are disabled.\n\n 172 Then, execute the\n 173 " adb shell cmd car_service apply-cts-verifier-power-on-policy"\n 174 shell command and sequential click the remaining 4 buttons to check if each component 175 settings UI is enabled.\n\n 176 For the detailed instructions, please refer to\n 177 " https://source.android.com/compatibility/cts/power-policy". 178 </string> 179 <string name="car_wifi_settings">Go to Wi-Fi settings</string> 180 <string name="car_wifi_settings_disable">Check Wi-Fi Settings Disabled</string> 181 <string name="car_bluetooth_settings_disable">Check Bluetooth Settings Disabled</string> 182 <string name="car_location_settings_disable">Check Location Settings Disabled</string> 183 <string name="car_wifi_settings_enable">Check Wi-Fi Settings Enabled</string> 184 <string name="car_bluetooth_settings_enable">Check Bluetooth Settings Enabled</string> 185 <string name="car_location_settings_enable">Check Location Settings Enabled</string> 186 <string name="car_dock_test">Car Dock Test</string> 187 <string name="car_dock_test_desc">This test ensures that car mode opens the app associated with 188 car dock when going into car mode.\n\n 189 Click on "Enable Car Mode" to start the test. Clicking on the button will either bring up a 190 disambiguation dialog asking which app to open or immediately open the CAR_DOCK application. 191 Select the "CTS Verifier" app and then "Always" if the dialog pops up. 192 This will open the CAR_DOCK application.\n\n 193 In the CAR_DOCK application, press the home button, which will enable the pass button if the 194 framework correctly tries to open the CAR_DOCK app again.</string> 195 <string name="car_mode_enable">Enable Car Mode</string> 196 <string name="car_dock_activity_text">Press the Home button</string> 197 <string name="car_launcher_test">Car Launcher Test</string> 198 <string name="car_launcher_test_desc">This test ensures that the car launcher lists apps 199 disabled by car service due to system resource overuse.\n\n 200 <b> 201 Before proceeding, check if \'com.android.cts.car.watchdog_companionapp\' 202 (aka CtsCarWatchdogCompanionApp) is installed by going to Settings > Apps. If not, 203 please install the app before proceeding.\n\n 204 </b> 205 1. Check if the CtsCarWatchdogCompanionApp is visible in car launcher\'s app grid view. If 206 it is not listed, pass the test.\n 207 2. Run the 208 \'adb shell cmd car_service watchdog-resource-overuse-kill com.android.cts.car.watchdog_companionapp\' 209 shell command to disable the app because of system resource overuse.\n 210 3. Click on \"Open Launcher\". Make sure the CtsCarWatchdogCompanionApp is displayed. If it 211 is not listed, fail the test.\n 212 4. Open CtsCarWatchdogCompanionApp from the launcher.\n\n 213 Pass the test only if the companion app opened successfully.</string> 214 <string name="car_launcher_test_button_label">Open Launcher</string> 215 <string name="gear_selection_test">Gear Selection Test</string> 216 <string name="gear_selection_test_desc">This test ensures that the 217 GEAR_SELECTION property is implemented correctly.\n\nShift the car\'s 218 gear to the expected gear value. If it is able to shift to all the 219 implemented gears then the pass button will be enabled.</string> 220 <string name="expected_gear_selection_title">Expected Gear Selection</string> 221 <string name="current_gear_selection_title">Current Gear Selection</string> 222 <string name="parking_brake_on_test">PARKING_BRAKE_ON Test</string> 223 <string name="parking_brake_on_test_desc">This test ensures that the 224 PARKING_BRAKE_ON property is implemented correctly.\n\nFollow the 225 instructions on the screen to engage and disengage the parking brake. When 226 the instructions are completed, the pass button will be enabled.</string> 227 <string name="current_parking_brake_on_value_title">Current PARKING_BRAKE_ON Value:</string> 228 <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device 229 policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your 230 device and return to this test in the CTS Verifier. 231 </string> 232 <string name="da_generate_policy">Generate Policy</string> 233 <string name="da_apply_policy">Apply Policy</string> 234 <string name="da_random_policy">Random policy generated.</string> 235 <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string> 236 <string name="da_password_quality">Password Quality</string> 237 <string name="da_password_quality_alphabetic">Alphabetic</string> 238 <string name="da_password_quality_alphanumeric">Alphanumeric</string> 239 <string name="da_password_quality_numeric">Numeric</string> 240 <string name="da_password_quality_something">Something</string> 241 <string name="da_password_minimum_length">Minimum Password Length</string> 242 <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string> 243 <string name="da_maximum_time_to_lock">Maximum Time to Lock</string> 244 <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string> 245 246 <string name="da_screen_lock_test">Screen Lock Test</string> 247 <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow 248 method immediately locks the screen. It should lock the screen immediately despite any 249 settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen. 250 Your screen should be locked and require the password to be entered. 251 </string> 252 <string name="da_force_lock">Force Lock</string> 253 <string name="da_lock_success">It appears the screen was locked successfully!</string> 254 <string name="da_lock_error">It does not look like the screen was locked...</string> 255 256 <string name="da_install_admin_instructions"> 257 Please install the \'Test Device Admin\' app (packaged as CtsEmptyDeviceAdmin.apk) on the device. 258 </string> 259 <string name="da_admin_installed_status_text">\'Test Device Admin\' installed on the device.</string> 260 <string name="da_enable_admin_instructions">Add \'Test Device Admin\' as an active administrator on the device. 261 Tap the button below to review the device admin details and activate the administrator. 262 </string> 263 <string name="da_enable_admin_button_text">Enable admin</string> 264 <string name="da_uninstall_admin_instructions">Attempt to uninstall the app from the application details page of the \'Test Device Admin\' app. 265 You should see another screen showing the device admin details before you can uninstall the app from the device. 266 Wait till the app is uninstalled before returning to this page. 267 </string> 268 <string name="da_uninstall_admin_button_text">Launch settings</string> 269 270 <string name="da_tapjacking_overlay_app_description">This activity attempts to tapjack the activity below.\n 271 Any security sensitive controls below should not respond to taps as long as this activity is visible.</string> 272 <string name="da_tapjacking_instructions"> 273 1. Launch the device admin add screen by pressing the button below.\n 274 2. Wait for an overlaying transparent activity to show up obscuring the device admin details window.\n 275 3. The button to activate the admin should be disabled and should not register any taps.\n 276 4. Press \'back\' to exit the overlaying transparent activity.\n 277 5. Press \'back\' to exit the device admin details and return to this screen.\n 278 Pass the test if the device admin could not be activated while the details 279 window was being obscured. 280 </string> 281 <string name="da_tapjacking_instructions" product="automotive"> 282 1. Launch the device admin add screen by pressing the button below.\n 283 2. Wait for an overlaying transparent activity to show up obscuring the device admin details window.\n 284 3. The button to activate the admin should be disabled and should not register any taps.\n 285 4. Wait for the overlaying activity to finish.\n 286 5. Press \'back\' to exit the device admin details and return to this screen.\n 287 Pass the test if the device admin could not be activated while the details 288 window was being obscured. 289 </string> 290 <string name="da_tapjacking_instructions" product="tv"> 291 1. Launch the device admin add screen by pressing the button below.\n 292 2. Wait for an overlaying transparent activity to show up obscuring the device admin details window.\n 293 3. The button to activate the admin should be disabled and should not register any taps.\n 294 4. Wait for the overlaying activity to finish.\n 295 5. Press \'back\' to exit the device admin details and return to this screen.\n 296 Pass the test if the device admin could not be activated while the details 297 window was being obscured. 298 </string> 299 <string name="da_tapjacking_button_text">Enable device admin</string> 300 301 <!-- Strings for RecentTaskRemovalTestActivity --> 302 <string name="remove_from_recents_test">Recent Task Removal Test</string> 303 <string name="remove_from_recents_test_info"> 304 This test verifies that an app whose task is removed from recents is not also force-stopped 305 without explicit user consent. This test requires CtsForceStopHelper.apk to be installed. 306 </string> 307 <string name="fs_test_app_install_instructions">Please install the \'Force stop helper app\' on the device.</string> 308 <string name="fs_test_app_installed_text">\'Force stop helper app\' installed on device. Proceed to the following steps.</string> 309 <string name="fs_test_app_launch_instructions"> 310 Tap the button to launch the helper activity. Then return to this screen. 311 </string> 312 <string name="fs_launch_test_app_button_text">Launch test activity</string> 313 <string name="fs_test_app_recents_instructions"> 314 Open recents and remove the task of the activity started in the previous step and return to this screen. 315 Deny any dialog that is shown asking for permission to force-stop or kill the app. 316 </string> 317 <string name="fs_force_stop_verification_pending">Verifying... Please wait.</string> 318 319 <!-- Strings for ClipboardPreviewTest --> 320 <string name="clipboard_preview_test">Clipboard Preview Test</string> 321 <string name="clipboard_preview_test_info"> 322 This test verifies that clipboard contents are visible to the user when copied. 323 </string> 324 <string name="clipboard_preview_test_instructions"> 325 Press the \'Copy\' button to copy the secret code to the clipboard. 326 \n\nDo not press any other buttons or tap the clipboard UI after you press the \'Copy\' button. 327 \n\n If you see the word "FAIL" appear on screen, press Fail. 328 \n\n If you see a confirmation that content has been copied to the clipboard, press Pass. 329 \n\n If nothing happens, press Fail if this is a handheld device, otherwise press Pass. 330 </string> 331 <string name="clipboard_preview_test_secret">FAIL</string> 332 <string name="clipboard_preview_test_copy_button">Copy</string> 333 334 <!-- Strings for BiometricTest --> 335 <string name="biometric_test">Biometric Tests</string> 336 337 <string name="biometric_test_category_credential">1) Credential Tests</string> 338 <string name="biometric_test_category_strong">2) Strong Biometric Tests</string> 339 <string name="biometric_test_category_weak">3) Weak Biometric Tests</string> 340 <string name="biometric_test_category_combination">4) setUserAuthParams Tests</string> 341 342 <string name="biometric_test_credential_crypto_label">1a: Credential Crypto</string> 343 <string name="biometric_test_credential_crypto_instructions">This test checks that PIN/Pattern/Password successfully unlocks the relevant KeyStore operations. Please 344 ensure that you have a PIN/Pattern/Password set up.</string> 345 <string name="biometric_test_credential_crypto_timed_key_strongbox">Create and unlock timed key (StrongBox)</string> 346 <string name="biometric_test_credential_crypto_timed_key_no_strongbox">Create and unlock timed key</string> 347 348 <string name="biometric_test_ui_instruction_dialog_title">Instructions</string> 349 <string name="biometric_test_ui_instruction_dialog_contents">For the following test, please remember or write down the numbers presented in the BiometricPrompt. After authenticating, please enter the contents in the test dialog.</string> 350 <string name="biometric_test_ui_instruction_dialog_continue">Continue</string> 351 <string name="biometric_test_ui_verification_dialog_title">Please enter your recorded contents</string> 352 <string name="biometric_test_ui_verification_dialog_check">Check</string> 353 354 <string name="biometric_test_reject_continues_instruction_title">Instructions</string> 355 <string name="biometric_test_reject_continues_instruction_contents">Please authenticate with a non-enrolled biometric before authenticating with the actual enrolled biometric.</string> 356 <string name="biometric_test_reject_continues_instruction_continue">Continue</string> 357 358 <string name="biometric_test_strong_label">2a: Strong Biometrics + Crypto</string> 359 <string name="biometric_test_strong_instructions">This test checks that the Settings.ACTION_BIOMETRIC_ENROLL and its corresponding 360 EXTRA_BIOMETRIC_AUTHENTICATOR_REQUIREMENTS APIs enroll only a STRONG biometric. Please ensure that the device 361 does NOT have ANY biometrics enrolled before starting this test. After passing the first part of the test, it will check various use cases 362 when authentication is invoked with the STRONG biometric.</string> 363 <string name="biometric_test_strong_check_and_enroll_button">Start enrollment</string> 364 <string name="biometric_test_strong_authenticate_no_strongbox_button">Authenticate Crypto (without StrongBox)</string> 365 <string name="biometric_test_strong_authenticate_strongbox_button">Authenticate Crypto (with StrongBox)</string> 366 <string name="biometric_test_strong_authenticate_invalidated_button">Authenticate Key Invalidated</string> 367 <string name="biometric_test_strong_authenticate_invalidated_instruction_title">Instructions</string> 368 <string name="biometric_test_strong_authenticate_invalidated_instruction_contents">Before starting the next test, please add another enrollment to your strong biometric sensor. If only one enrollment is supported, please remove the current enrollment, then enroll.</string> 369 <string name="biometric_test_strong_authenticate_invalidated_instruction_continue">Continue</string> 370 371 <string name="biometric_test_weak_label">3a: Weak Biometrics</string> 372 <string name="biometric_test_weak_instructions">This test checks that the Settings.ACTION_BIOMETRIC_ENROLL and its corresponding 373 EXTRA_BIOMETRIC_AUTHENTICATOR_REQUIREMENTS APIs enroll a biometric that meets or exceeds WEAK. Please ensure that the device 374 does NOT have ANY biometrics enrolled before starting this test. After passing the first part of the test, it will check various use cases 375 when authentication is invoked.</string> 376 <string name="biometric_test_weak_enroll">Start enrollment</string> 377 378 <string name="biometric_test_set_user_authentication_credential_cipher_label">4a: Cipher, Credential</string> 379 <string name="biometric_test_set_user_authentication_biometric_cipher_label">4b: Cipher, Biometric</string> 380 <string name="biometric_test_set_user_authentication_biometric_credential_cipher_label">4c: Cipher, Biometric|Credential</string> 381 <string name="biometric_test_set_user_authentication_credential_signature_label">4d: Signature, Credential</string> 382 <string name="biometric_test_set_user_authentication_biometric_signature_label">4e: Signature, Biometric</string> 383 <string name="biometric_test_set_user_authentication_biometric_or_credential_signature_label">4f: Signature, Biometric|Credential</string> 384 <string name="biometric_test_set_user_authentication_credential_mac_label">4g: MAC, Credential</string> 385 <string name="biometric_test_set_user_authentication_biometric_mac_label">4h: MAC, Biometric</string> 386 <string name="biometric_test_set_user_authentication_biometric_or_credential_mac_label">4i: MAC, Biometric|Credential</string> 387 <string name="biometric_test_set_user_authentication_credential_aead_cipher_label">4j: Aead Cipher, Credential</string> 388 <string name="biometric_test_set_user_authentication_biometric_aead_cipher_label">4k: Aead Cipher, Biometric</string> 389 <string name="biometric_test_set_user_authentication_biometric_credential_aead_cipher_label">4l: Aead Cipher, Biometric or Credential</string> 390 <string name="biometric_test_set_user_authentication_credential_instructions">This test checks the correctness of the KeyGenParameterSpec.Builder#setUserAuthenticationParameters(int, int) API for AUTH_DEVICE_CREDENTIAL. 391 Buttons for completed tasks will become invisible. It\'s normal for buttons to be disabled for a few seconds during this test.</string> 392 <string name="biometric_test_set_user_authentication_biometric_instructions">This test checks the correctness of the KeyGenParameterSpec.Builder#setUserAuthenticationParameters(int, int) API for AUTH_BIOMETRIC_STRONG. 393 Buttons for completed tasks will become invisible. It\'s normal for buttons to be disabled for a few seconds during this test.</string> 394 <string name="biometric_test_set_user_authentication_biometric_or_credential_instructions">This test checks the correctness of the KeyGenParameterSpec.Builder#setUserAuthenticationParameters(int, int) API for AUTH_BIOMETRIC_STRONG|AUTH_DEVICE_CREDENTIAL. 395 Buttons for completed tasks will become invisible. It\'s normal for buttons to be disabled for a few seconds during this test.</string> 396 <!-- no strongbox--> 397 <string name="biometric_test_set_user_authentication_credential_per_use_auth_with_credential">auth-per-use key with credential</string> 398 <string name="biometric_test_set_user_authentication_credential_duration_auth_with_credential">time-based key with credential</string> 399 <string name="biometric_test_set_user_authentication_credential_per_use_auth_with_biometric">auth-per-use key with biometric</string> 400 <string name="biometric_test_set_user_authentication_credential_duration_auth_with_biometric">time-based key with biometric</string> 401 <!-- strongbox --> 402 <string name="biometric_test_set_user_authentication_credential_per_use_auth_with_credential_strongbox">auth-per-use key with credential (strongbox)</string> 403 <string name="biometric_test_set_user_authentication_credential_duration_auth_with_credential_strongbox">time-based key with credential (strongbox)</string> 404 <string name="biometric_test_set_user_authentication_credential_per_use_auth_with_biometric_strongbox">auth-per-use key with biometric (strongbox)</string> 405 <string name="biometric_test_set_user_authentication_credential_duration_auth_with_biometric_strongbox">time-based key with biometric (strongbox)</string> 406 407 <!-- Strings for user consent for logs test --> 408 <string name="read_logs_text">User Consent for Device Logs Test</string> 409 <string name="read_logs_fg_allow_text">User Consent for Device Logs Allow in Foreground Test</string> 410 <string name="read_logs_fg_deny_text">User Consent for Device Logs Deny in Foreground Test</string> 411 <string name="read_logs_bg_text">User Consent for Device Logs in Instrumentation Test</string> 412 <string name="read_logs_test_info">This test verifies that user consent for per-use prompt is working properly.\nThe test assumes READ_LOGS permission is granted to the app.\nStart this test by clicking \"User Consent for Device Logs Allow in Foreground Test\" button.\nWhen the process is running in foreground, a user will see a prompt. Once a user clicks the prompt, users have an option to choose \"Allow one-time access\" or \"Don\'t Allow\". Choose \"Allow one-time access\" for the \"ALLOW\" test case and \"Don\'t Allow\" for the \"DENY\" test case.\nThe test results can be judged by the adb logcat prints from command \"adb logcat -b all -s ReadLogsTestActivity:*\"\n\"ReadLogsTestActivity: Logcat system allow log contains e.g.: true lineCount: 11 larger than: true\" shows the success of the \"ALLOW\" test case and\n\"ReadLogsTestActivity: Logcat system deny line count:0\" shows the success of the \"DENY\" test case.</string> 413 414 <!-- Strings for lock bound keys test --> 415 <string name="sec_lock_bound_key_test">Lock Bound Keys Test</string> 416 <string name="sec_lock_bound_key_test_info"> 417 This test ensures that Keystore cryptographic keys that are bound to lock screen authentication 418 are unusable without a recent enough authentication. You need to set up a screen lock in order to 419 complete this test. If available, this test should be run by using fingerprint authentication 420 as well as PIN/pattern/password authentication. 421 </string> 422 423 <string name="sec_fingerprint_bound_key_test">Fingerprint Bound Keys Test</string> 424 <string name="sec_fingerprint_bound_key_test_info"> 425 This test ensures that Keystore cryptographic keys that are bound to fingerprint authentication 426 are unusable without an authentication. You need to set up a fingerprint order to 427 complete this test. 428 </string> 429 <string name="sec_fp_dialog_message">Authenticate now with fingerprint</string> 430 <string name="sec_fp_auth_failed">Authentication failed</string> 431 <string name="sec_start_test">Start Test</string> 432 433 <!-- Strings for protected confirmation test --> 434 <string name="sec_protected_confirmation_test">Android Protected Confirmation Test</string> 435 <string name="sec_protected_confirmation_test_info"> 436 This test ensures that - if Android Protected Confirmation is supported by the device under 437 test - the user is able to see the confirmation message and confirm it. It also assures that 438 Keymaster signs a message with a confirmation key only if the message was previously 439 confirmed by the user. 440 </string> 441 <string name="sec_protected_confirmation_not_supported_title">Not Supported</string> 442 <string name="sec_protected_confirmation_not_supported_info"> 443 Android Protected Confirmation is not implemented by this device. This is okay because this 444 is an optional feature. Set this test to passed and continue. 445 </string> 446 <string name="sec_protected_confirmation_message">This is a CtsVerifier test message!</string> 447 <string name="sec_protected_confirmation_tee_test">Start Tee Test</string> 448 <string name="sec_protected_confirmation_strongbox_test">Start Strongbox Test</string> 449 <string name="sec_protected_confirmation_tee_negative_test">Start Tee Negative Test</string> 450 <string name="sec_protected_confirmation_strongbox_negative_test">Start Strongbox Negative Test</string> 451 452 <!-- Strings for IdentityAuthPerPresenation --> 453 <string name="sec_identity_credential_authentication_test">Identity Credential Authentication</string> 454 <string name="sec_identity_credential_authentication_test_info"> 455 This test ensures that data elements in Identity Credential documents protected by user 456 authentication with timeout 0 can only be accessed once per reader session. 457 </string> 458 459 <!-- Strings for IdentityAuthPerPresenationMultiDocument --> 460 <string name="sec_identity_credential_authentication_multi_document_test">Identity Credential Authentication Multi-Document</string> 461 <string name="sec_identity_credential_authentication_multi_document_test_info"> 462 This test is for Identity Credential presentations with multiple documents. 463 </string> 464 465 <string name="sec_unlocked_device_required_test">Unlocked Device Required</string> 466 <string name="sec_unlocked_device_required_test_info"> 467 This test ensures that keys created with setUnlockedDeviceRequired are usable when the 468 screen is unlocked but not when it is locked. 469 </string> 470 471 <!-- Strings for HasVibratorVerifierActivity --> 472 <string name="has_vibrator_test_description">This test validates the Vibrator#HasVibrator API response.</string> 473 <string name="has_vibrator_response_label">Does this device say it has a vibrator?</string> 474 <string name="has_vibrator_start_test_label">To start the test, hold the device in your hand and click the vibrate button.</string> 475 <string name="has_vibrator_did_device_vibrate_label">Did the device vibrate?</string> 476 <string name="has_vibrator_test_vibrate_and_pass_message">Feeling vibration indicates that the test passed. Click the pass button to register the result.</string> 477 <string name="has_vibrator_test_vibrate_and_fail_message">Not feeling vibration indicates that the test failed. Click the fail button to register the result.</string> 478 <string name="has_vibrator_test_no_vibrate_and_pass_message">Not feeling vibration indicates that the test passed. Click the pass button to register the result.</string> 479 <string name="has_vibrator_test_no_vibrate_and_fail_message">Feeling vibration indicates that the test failed. Click the fail button to register the result.</string> 480 <string name="has_vibrator_test_running_text">Test will end in %d</string> 481 <string name="has_vibrator_test_vibrate_button_text">Vibrate</string> 482 483 <!-- Strings for BluetoothActivity --> 484 <string name="bluetooth_test">Bluetooth Test</string> 485 <string name="bluetooth_test_info"> 486 The Bluetooth Control tests check whether or not the device 487 can disable and enable Bluetooth properly. 488 \n\nThe Bluetooth tests require two devices, and Bluetooth data is exchanged between them. 489 \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. 490 \nThis is a list of the tests: 491 \nThis Device x Other Device 492 \n\n\"Bluetooth LE Insecure Client Test\" x \"Bluetooth LE Insecure Server Test\" 493 \n\n\"Bluetooth LE Insecure Server Test\" x \"Bluetooth LE Insecure Client Test\" 494 \n\n\"Bluetooth LE Secure Client Test\" x \"Bluetooth LE Secure Server Test\" 495 \n\n\"Bluetooth LE Secure Server Test\" x \"Bluetooth LE Secure Client Test\" 496 \n\n\"Bluetooth LE CoC Insecure Server Test\" x \"Bluetooth LE CoC Insecure Client Test\" 497 \n\n\"Bluetooth LE CoC Insecure Client Test\" x \"Bluetooth LE CoC Insecure Server Test\" 498 \n\n\"Bluetooth LE CoC Secure Server Test\" x \"Bluetooth LE CoC Secure Client Test\" 499 \n\n\"Bluetooth LE CoC Secure Client Test\" x \"Bluetooth LE CoC Secure Server Test\" 500 \n\nThe Device Communication tests require two 501 devices to pair and exchange messages. The two devices must be: 502 \n\n1. a candidate device implementation running the software build to be tested 503 \n\n2. a separate device implementation already known to be compatible 504 </string> 505 506 <string name="bt_control">Bluetooth Control</string> 507 <string name="bt_device_communication">Device Communication</string> 508 <string name="bt_le">Bluetooth LE</string> 509 <string name="bt_hid">Bluetooth HID</string> 510 <string name="bt_le_coc">Bluetooth LE CoC</string> 511 512 <string name="bt_toggle_bluetooth">Toggle Bluetooth</string> 513 <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string> 514 <string name="bt_enable_bluetooth">Enable Bluetooth</string> 515 <string name="bt_disable_bluetooth">Disable Bluetooth</string> 516 <string name="bt_disabling">Disabling Bluetooth...</string> 517 <string name="bt_disabling_error">Could not disable Bluetooth...</string> 518 519 <string name="ble_coc_insecure_client_test_list_name">Bluetooth LE CoC Insecure Client Test</string> 520 <string name="ble_coc_insecure_client_test_list_info"> 521 The Bluetooth LE CoC test must be done simultaneously on two devices. This device is the client. 522 All tests listed here must be done without pairing. Tap \"Bluetooth LE CoC Insecure Server Test\" on the other device. 523 \n\nTap \"01 Bluetooth LE CoC Client Test\" on this device, then tap \"01 Bluetooth LE CoC Server Test\" on the other device. 524 \nWhen the test is complete, move to the next item. You must complete all tests. 525 </string> 526 <string name="ble_coc_insecure_client_test_info"> 527 The Bluetooth LE CoC test must be done simultaneously on two devices. This device is the client. 528 All tests listed here must be done without pairing. 529 </string> 530 <string name="ble_coc_insecure_server_test_list_name">Bluetooth LE CoC Insecure Server Test</string> 531 <string name="ble_coc_insecure_server_test_list_info"> 532 This test is mostly automated, but requires some user interaction. 533 Once the list items below have check marks, the test is complete. 534 \n\nTap \"01 Bluetooth LE CoC Server Test\" on this device, then tap \"01 Bluetooth LE CoC Client Test\" on the other device. 535 \nWhen the test is complete, move to the next item. You must complete all tests. 536 </string> 537 538 <string name="ble_coc_secure_client_test_list_name">Bluetooth LE CoC Secure Client Test</string> 539 <string name="ble_coc_secure_client_test_list_info"> 540 The Bluetooth LE CoC test must be done simultaneously on two devices. This device is the client. 541 All tests listed here must be done with pairing. Tap \"Bluetooth LE CoC Secure Server Test\" on the other device. 542 \n\nTap \"01 Bluetooth LE CoC Client Test\" on this device, then tap \"01 Bluetooth LE CoC Server Test\" on the other device. 543 \nWhen the test is complete, move to the next item. You must complete all tests. 544 </string> 545 <string name="ble_coc_secure_client_test_info"> 546 The Bluetooth LE CoC test must be done simultaneously on two devices. This device is the client. 547 All tests listed here must be done with pairing. 548 </string> 549 <string name="ble_coc_secure_server_test_list_name">Bluetooth LE CoC Secure Server Test</string> 550 <string name="ble_coc_secure_server_test_list_info"> 551 This test is mostly automated, but requires some user interaction. 552 Once the list items below have check marks, the test is complete. 553 \n\nTap \"01 Bluetooth LE CoC Server Test\" on this device, then tap \"01 Bluetooth LE CoC Client Test\" on the other device. 554 \nWhen the test is complete, move to the next item. You must complete all tests. 555 </string> 556 557 <!-- BLE CoC client side strings --> 558 <string name="ble_coc_client_test_name">01 Bluetooth LE CoC Client Test</string> 559 <string name="ble_coc_client_le_connect">Bluetooth LE Client Connect</string> 560 <string name="ble_coc_client_get_psm">Get peer PSM value</string> 561 <string name="ble_coc_client_coc_connect">LE CoC client Connect</string> 562 <string name="ble_coc_client_check_connection_type">Check connection type</string> 563 <string name="ble_coc_client_send_data_8bytes">Send 8 bytes</string> 564 <string name="ble_coc_client_receive_data_8bytes">Receive 8 bytes</string> 565 <string name="ble_coc_client_data_exchange">Send and receive large data buffer</string> 566 567 <!-- BLE CoC server side strings --> 568 <string name="ble_coc_server_start_name">01 Bluetooth LE CoC Server Test</string> 569 <string name="ble_coc_server_le_connect">Bluetooth LE Server Connect</string> 570 <string name="ble_coc_server_create_listener">Create LE CoC listener</string> 571 <string name="ble_coc_server_psm_read">Waiting on PSM to be read</string> 572 <string name="ble_coc_server_connection">Waiting on LE CoC connection</string> 573 <string name="ble_coc_server_check_connection_type">Check connection type</string> 574 <string name="ble_coc_server_receive_data_8bytes">Waiting to receive 8 bytes</string> 575 <string name="ble_coc_server_send_data_8bytes">Sending 8 bytes</string> 576 <string name="ble_coc_server_data_exchange">Send and receive large data buffer</string> 577 578 <string name="bt_connection_access_server">Connection Access Server</string> 579 <string name="bt_connection_access_client">Connection Access Client</string> 580 <string name="bt_connection_access_server_info"> 581 Start the CTS Verifier on another device, start the Bluetooth test, and choose 582 \"Connection Access Client\" to setup the test. 583 \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together 584 using the \"Make Discoverable\" and \"Pick Server\" buttons. 585 \n\nA connection access request should appear on the server and enable the pass button. 586 </string> 587 <string name="bt_connection_access_client_info"> 588 Start the CTS Verifier on another device, start the Bluetooth test, and choose 589 \"Connection Access Server\" to complete the test. 590 \n\nMake the device acting as the server discoverable and connect to it via the 591 \"Pick Server\" button. Check that the server displays the connection access request 592 dialog. The client device does not need to do anything else. 593 </string> 594 <string name="bt_ca_dialog">Was the connection access request dialog shown?</string> 595 <string name="bt_ca_tips"> 596 Tap the \"Bluetooth Settings\" button and check that both devices are not paired 597 before running the test. 598 \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth 599 devices together and start the test. 600 </string> 601 602 <!-- Strings for HidHost and HidDevice activity --> 603 <string name="bt_hid_host_test_name">Bluetooth HID Host Test</string> 604 <string name="bt_hid_host_test_info"> 605 Start the CTS Verifier on another device, start the Bluetooth test, and choose 606 \"Bluetooth HID Device\" to complete the test. 607 \n\nClick \"Register app\" and \"Make discoverable\" on another device first, and click 608 \"Select device\". Choose the device from device picker. If the remote device is already 609 paired, unpair it first from system Settings. 610 \n\nAfter the remote device completes the \"Send_report\" command, text \"bluetooth\" should 611 appear in the EditText. Mark the test as passed. 612 \n\n If the device under test (DUT) does not have Bluetooth HID Host service or HID Device 613 service enabled, mark the test as passed. 614 </string> 615 <string name="bt_hid_host">Bluetooth HID Host</string> 616 <string name="bt_hid_host_select_device">Select device</string> 617 618 <string name="bt_hid_device_test_name">Bluetooth HID Device Test</string> 619 <string name="bt_hid_device_test_info"> 620 Start the CTS Verifier on another device, start the Bluetooth test, and choose 621 \"Bluetooth HID Host\" to complete the test. 622 \n\nFirst, click the \"Register app\" button, and click the \"Make discoverable\" button. 623 \n\nThen, on another device, click the \"Select device" button, and choose this device. 624 \n\nWait until the dialog shows up for pairing two devices. 625 \n\nFinally, click the \"Test send_report\", \"Test reply_report\", \"Test report_error\". 626 \n\nIf all the commands are successful, then click \"Unregister app\" and mark the test as 627 passed. 628 \n\n If the device under test (DUT) does not have Bluetooth HID Host service or HID Device 629 service enabled, mark the test as passed. 630 </string> 631 632 <string name="bt_hid_device">Bluetooth HID Device</string> 633 <string name="bt_hid_device_register">Register app</string> 634 <string name="bt_hid_device_unregister">Unregister app</string> 635 <string name="bt_hid_device_send_report">Test Send_report</string> 636 <string name="bt_hid_device_reply_report">Test Reply_report</string> 637 <string name="bt_hid_device_report_error">Test Report_error</string> 638 639 640 <string name="bt_secure_server">Secure Server</string> 641 <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> 642 <string name="bt_insecure_server">Insecure Server</string> 643 <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> 644 <string name="bt_waiting">Waiting for client...</string> 645 <string name="bt_listening">Listening...</string> 646 <string name="bt_connecting">Connecting...</string> 647 <string name="bt_connected">Connected</string> 648 <string name="bt_received_messages">Received Messages</string> 649 <string name="bt_sent_messages">Sent Messages</string> 650 <string name="bt_no_messages">No messages</string> 651 <string name="bt_make_discoverable">Make Discoverable</string> 652 <string name="bt_pick_server">Pick Server</string> 653 <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string> 654 <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string> 655 <string name="bt_advertise_unsupported_title">Advertising is not supported</string> 656 <string name="bt_advertise_unsupported_message">Advertising is not supported on this device.\nTest finishes.</string> 657 <string name="bt_open_failed_title">BLE open failed</string> 658 <string name="bt_open_failed_message">Cannot open BLE GattService.\nTest finishes.</string> 659 <string name="bt_add_service_failed_title">Add service failed</string> 660 <string name="bt_add_service_failed_message">Failed to add services.\nTest finishes.</string> 661 662 <string name="bt_secure_client">Secure Client</string> 663 <string name="bt_insecure_client">Insecure Client</string> 664 665 <string name="bt_device_picker">Device Picker</string> 666 <string name="bt_paired_devices">Paired Devices</string> 667 <string name="bt_new_devices">New Devices</string> 668 <string name="bt_no_devices">No devices</string> 669 <string name="bt_scan">Scan for Devices</string> 670 <string name="bt_scanning">Scanning...</string> 671 <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> 672 <string name="bt_settings">Bluetooth Settings</string> 673 674 <!-- BLE client side strings --> 675 <string name="ble_client_service_name">Bluetooth LE GATT Client Handler Service</string> 676 <string name="ble_client_test_name">01 Bluetooth LE Client Test</string> 677 <string name="ble_client_connect_name">Bluetooth LE Client Connect</string> 678 <string name="ble_discover_service_name">Bluetooth LE Discover Service</string> 679 <string name="ble_read_characteristic_name">Bluetooth LE Read Characteristic</string> 680 <string name="ble_write_characteristic_name">Bluetooth LE Write Characteristic</string> 681 <string name="ble_reliable_write_name">Bluetooth LE Reliable Write</string> 682 <string name="ble_reliable_write_bad_resp_name">Bluetooth LE Reliable Write (receive bad response)</string> 683 <string name="ble_notify_characteristic_name">Bluetooth LE Notify Characteristic</string> 684 <string name="ble_read_descriptor_name">Bluetooth LE Read Descriptor</string> 685 <string name="ble_write_descriptor_name">Bluetooth LE Write Descriptor</string> 686 <string name="ble_read_rssi_name">Bluetooth LE Read RSSI</string> 687 <string name="ble_read_phy_name">Bluetooth LE Read PHY</string> 688 <string name="ble_set_preferred_phy_name">Bluetooth LE Set Preferred PHY</string> 689 <string name="ble_on_service_changed">Bluetooth LE On Service Changed</string> 690 <string name="ble_client_disconnect_name">Bluetooth LE Client Disconnect</string> 691 <string name="ble_insecure_client_test_info"> 692 The Bluetooth LE test must be done simultaneously on two devices. This device is the client. 693 All tests listed here must be done without pairing. 694 </string> 695 <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> 696 <string name="ble_discover_service_info">Verify that the service is discovered when you press the "Discover Service" button.</string> 697 <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> 698 <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> 699 <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> 700 <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> 701 <string name="ble_client_disconnect_info">Verify that the device is disconnected when you press the "Disconnect" button</string> 702 <string name="ble_address">Bluetooth address</string> 703 <string name="ble_connect">Connect</string> 704 <string name="ble_discover_service">Discover service</string> 705 <string name="ble_write_hint">Nothing to write yet</string> 706 <string name="ble_read_hint">Nothing read yet</string> 707 <string name="ble_write">Write</string> 708 <string name="ble_read">Read</string> 709 <string name="ble_begin_write">Begin write</string> 710 <string name="ble_execute_write">Execute write</string> 711 <string name="ble_begin_notification">Begin notification</string> 712 <string name="ble_stop_notification">Stop notification</string> 713 <string name="ble_waiting_notification">Waiting on notification</string> 714 <string name="ble_read_rssi">Read RSSI</string> 715 <string name="ble_disconnect">Disconnect</string> 716 <string name="ble_test_text">TEST</string> 717 <string name="ble_test_finished">Test finished</string> 718 <string name="ble_test_next">Next</string> 719 <string name="ble_test_running">Test Running</string> 720 <string name="ble_test_running_message">This test requires a few minutes. Don\'t interrupt the test.</string> 721 <string name="ble_mtu_23_name">Bluetooth LE Request MTU(23bytes)</string> 722 <string name="ble_mtu_512_name">Bluetooth LE Request MTU(512bytes)</string> 723 724 <!-- BLE server side strings --> 725 <string name="ble_server_service_name">Bluetooth LE GATT Server Handler Service</string> 726 <string name="ble_server_start_name">01 Bluetooth LE Server Test</string> 727 <string name="ble_server_start_info"> 728 The Bluetooth LE test must be done simultaneously on two devices, a server device and a client device. This device is the server. 729 </string> 730 <string name="ble_server_receiving_connect">Waiting on connection from Bluetooth LE client.</string> 731 <string name="ble_server_add_service">Adding service to Bluetooth LE server.</string> 732 <string name="ble_server_write_characteristic">Waiting on write characteristic request</string> 733 <string name="ble_server_read_characteristic">Waiting on read characteristic request</string> 734 <string name="ble_server_write_descriptor">Waiting on write descriptor request</string> 735 <string name="ble_server_read_descriptor">Waiting on read descriptor request</string> 736 <string name="ble_server_reliable_write">Waiting on reliable write from client</string> 737 <string name="ble_server_reliable_write_bad_resp">Waiting on reliable write from client (send bad response)</string> 738 <string name="ble_server_service_changed_indication">Waiting on service changed indication</string> 739 <string name="ble_server_receiving_disconnect">Waiting on disconnection from Bluetooth LE client</string> 740 <string name="ble_connection_priority_server_name">02 Bluetooth LE Connection Priority Server Test</string> 741 <string name="ble_connection_priority_server_info">Bluetooth LE Connection Priority Server receive message from message in 3 different priority.</string> 742 <string name="ble_server_notify_characteristic">Waiting on notify characteristic request</string> 743 <string name="ble_server_write_characteristic_without_permission">Waiting on write characteristic request without permission</string> 744 <string name="ble_server_read_characteristic_without_permission">Waiting on read characteristic request without permission</string> 745 <string name="ble_server_write_descriptor_without_permission">Waiting on write descriptor request without permission</string> 746 <string name="ble_server_read_descriptor_without_permission"> Waiting on read descriptor request without permission</string> 747 <string name="ble_server_write_characteristic_need_encrypted">Waiting on write encrypted characteristic request</string> 748 <string name="ble_server_read_characteristic_need_encrypted">Waiting on read encryptedcharacteristic request</string> 749 <string name="ble_server_write_descriptor_need_encrypted">Waiting on write encrypted descriptor request</string> 750 <string name="ble_server_read_descriptor_need_encrypted"> Waiting on read encrypted descriptor request</string> 751 <string name="ble_server_indicate_characteristic">Waiting on indicate characteristic request</string> 752 <string name="ble_server_mtu_23bytes">Waiting on MTU request(23 bytes)</string> 753 <string name="ble_server_mtu_512bytes">Waiting on MTU request(512 bytes)</string> 754 <string name="ble_encrypted_server_name">03 Bluetooth LE Encrypted Server Test</string> 755 <string name="ble_encrypted_server_info">Bluetooth LE Encrypted Server Waiting on read/write characteristic and descriptor request need encrypted.</string> 756 <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> 757 <string name="ble_insecure_server_test_list_name">Bluetooth LE Insecure Server Test</string> 758 <string name="ble_insecure_server_test_list_info"> 759 This test is mostly automated, but requires some user interaction. 760 Once the list items below have check marks, the test is complete. 761 \n\nTap \"01 Bluetooth LE Server Test\" on this device, then tap \"01 Bluetooth LE Client Test\" on the other device. 762 \nWhen the test is complete, move to the next item. You must complete all tests. 763 </string> 764 <string name="ble_secure_server_test_list_name">Bluetooth LE Secure Server Test</string> 765 <string name="ble_secure_server_test_list_info"> 766 This test is mostly automated, but requires some user interaction. 767 You can pass this test once the list items below are checked. 768 \n\nTap \"01 Bluetooth LE Server Test\" on this device, then tap \"01 Bluetooth LE Client Test \"on other device. 769 \nTest completed, then test next item. You must be done all tests. 770 </string> 771 772 <!-- BLE advertiser side strings --> 773 <string name="ble_advertiser_test_name">Bluetooth LE Advertiser Test</string> 774 <string name="ble_advertiser_test_info"> 775 The Bluetooth LE Advertiser Test and Scanner Test is a paired test. 776 \nTap \"Bluetooth LE Advertiser Test\" on this device. Once it is passed, tap \"Bluetooth LE Scanner Test\". 777 \nTap \"Bluetooth LE Scanner Test\" on this device. Once it is passed, tap \"Bluetooth LE Advertiser Test\". 778 </string> 779 <string name="ble_advertiser_service_name">Bluetooth LE Advertiser Handler Service</string> 780 <string name="ble_privacy_mac_name">Bluetooth LE Privacy Mac</string> 781 <string name="ble_privacy_mac_info">Bluetooth LE Advertiser should advertise in non-repeating MAC address.</string> 782 <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> 783 <string name="ble_power_level_name">Bluetooth LE Tx Power Level</string> 784 <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> 785 <string name="ble_advertiser_power_level_instruction"> 786 Click start to start multi-advertising. Data packets are advertised in 4 different power levels. 787 You may receive a message that this device does not support multi-advertising. 788 If the advertiser does not advertise in 4 power levels, and you do not receive an error message, 789 you may not have stopped advertising in the previous test, or this device may not support 4 advertisers at the same time. 790 Try rebooting the device and running the test again to free those advertisers in use. 791 </string> 792 <string name="ble_advertiser_scan_filter_name">Bluetooth LE Hardware Scan Filter</string> 793 <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> 794 <string name="ble_advertiser_scannable">Scannable advertising</string> 795 <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> 796 <string name="ble_advertiser_unscannable">Unscannble advertising</string> 797 <string name="ble_advertiser_unscannable_instruction">Start unscannable advertising, expect scanner stay calm on Monsoon monitor, no log of GattService from scanner logcat.</string> 798 <string name="ble_advertiser_start">Start</string> 799 <string name="ble_advertiser_stop">Stop</string> 800 801 <!-- BLE scanner side strings --> 802 <string name="ble_scanner_test_name">Bluetooth LE Scanner Test</string> 803 <string name="ble_scanner_service_name">Bluetooth LE Scanner Handler Service</string> 804 <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> 805 <string name="ble_scanner_privacy_mac">Hold for 15 min to see if receive a different MAC address from advertiser.</string> 806 <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> 807 <string name="ble_ultra_low">Ultra low</string> 808 <string name="ble_low">Low</string> 809 <string name="ble_medium">Medium</string> 810 <string name="ble_high">High</string> 811 <string name="ble_scanner_power_level_instruction">Count: Ultra low < low < medium < high\nRssi: Ultra low < low < medium < high\nDistance to see count freezing: Ultra low < low < medium < 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> 812 <string name="ble_scanner_scan_filter_name">BLE Hardware Scan Filter</string> 813 <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> 814 <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> 815 <string name="ble_scan_with_filter">Scan with filter</string> 816 <string name="ble_scan_without_filter">Scan without filter</string> 817 <string name="ble_scan_start">Start scan</string> 818 <string name="ble_scan_stop">Stop scan</string> 819 820 <!-- BLE Advertising Set test strings --> 821 <string name="ble_advertising_set_test_name">Bluetooth LE Advertising Set Test</string> 822 <string name="ble_advertising_set_test_info">Bluetooth LE Advertising Set tests AdvertisingSet and AdvertisingSetCallback APIs.</string> 823 <string name="ble_advertising_set_test_instruction">Press the \"Start Test\" button. UI thread may freeze for a few seconds while enabling/disabling bluetooth adapter.</string> 824 <string name="ble_advertising_set_start_test">Start Test</string> 825 <string name="ble_advertising_set_running_test">Running Test...</string> 826 <string name="ble_advertising_set_finished_test">Finished Test</string> 827 <string name="ble_advertising_set_start">Starting advertising set.</string> 828 <string name="ble_advertising_set_enable_disable">Enabling/Disabling advertising set.</string> 829 <string name="ble_advertising_set_advertising_data">Setting advertising data.</string> 830 <string name="ble_advertising_set_advertising_params">Setting advertising parameters.</string> 831 <string name="ble_advertising_set_periodic_advertising_data">Setting periodic advertising data.</string> 832 <string name="ble_advertising_set_periodic_advertising_enabled_disabled">Enabling/Disabling periodic advertising.</string> 833 <string name="ble_advertising_set_periodic_advertising_params">Setting periodic advertising parameters.</string> 834 <string name="ble_advertising_set_scan_response_data">Setting scan response data.</string> 835 <string name="ble_advertising_set_stop">Stopping advertising set.</string> 836 837 <!-- BLE connection priority test strings --> 838 <string name="ble_client_connection_priority">Testing connection priority switching </string> 839 <string name="ble_server_connection_priority_result_passed">All test passed</string> 840 <string name="ble_server_connection_priority_result_failed">Test failed.</string> 841 <string name="ble_server_connection_priority_result_intervals"> 842 Transfer interval time (msec):\nHIGH=%1$d\nBALANCED=%2$d\nLOW=%3$d\n\nRequirements:\n HIGH <= BALANCED <= LOW 843 </string> 844 845 <!-- BLE Test Name --> 846 <string name="ble_secure_client_test_name">Bluetooth LE Secure Client Test</string> 847 <string name="ble_insecure_client_test_name">Bluetooth LE Insecure Client Test</string> 848 <string name="ble_secure_server_test_name">Bluetooth LE Secure Server Test</string> 849 <string name="ble_insecure_server_test_name">Bluetooth LE Insecure Server Test</string> 850 851 <string name="ble_coc_secure_client_test_name">Bluetooth LE CoC Secure Client Test</string> 852 <string name="ble_coc_insecure_client_test_name">Bluetooth LE CoC Insecure Client Test</string> 853 <string name="ble_coc_secure_server_test_name">Bluetooth LE CoC Secure Server Test</string> 854 <string name="ble_coc_insecure_server_test_name">Bluetooth LE CoC Insecure Server Test</string> 855 856 <string name="ble_read_characteristic_nopermission_name">Bluetooth LE Read Characteristic Without Perrmission</string> 857 <string name="ble_write_characteristic_nopermission_name">Bluetooth LE Write Characteristic Without Permission</string> 858 <string name="ble_read_descriptor_nopermission_name">Bluetooth LE Read Descriptor Without Perrmission</string> 859 <string name="ble_write_descriptor_nopermission_name">Bluetooth LE Write Descriptor Without Permission</string> 860 <string name="ble_connection_priority_client_name">02 Bluetooth LE Connection Priority Client Test</string> 861 <string name="ble_connection_priority_client_info">Bluetooth LE Connection Priority Client send message in 3 different priority.</string> 862 <string name="ble_read_authenticated_characteristic_name">Bluetooth LE Read Encrypted Characteristic</string> 863 <string name="ble_write_authenticated_characteristic_name">Bluetooth LE Write Encrypted Characteristic</string> 864 <string name="ble_read_authenticated_descriptor_name">Bluetooth LE Read Encrypted Descriptor</string> 865 <string name="ble_write_authenticated_descriptor_name">Bluetooth LE Write Encrypted Descriptor</string> 866 <string name="ble_connection_priority_client_description">Client Switching Connection Priority</string> 867 <string name="ble_indicate_characteristic_name">Bluetooth LE Indicate Characteristic</string> 868 <string name="ble_encrypted_client_name">03 Bluetooth LE Encrypted Client Test</string> 869 <string name="ble_encrypted_client_info">Bluetooth LE Encrypted Client read/write on characteristic and descriptor need encrypted.</string> 870 <string name="ble_insecure_client_test_list_name">Bluetooth LE Insecure Client Test</string> 871 <string name="ble_insecure_client_test_list_info"> 872 The Bluetooth LE test must be done simultaneously on two devices. This device is the client. 873 All tests listed here must be done without pairing. Tap \"Bluetooth LE Insecure Server Test\" on the other device. 874 \n\nTap \"01 Bluetooth LE Client Test\" on this device, then tap \"01 Bluetooth LE Server Test\" on the other device. 875 \nWhen the test is complete, move to the next item. You must complete all tests. 876 </string> 877 <string name="ble_secure_client_test_list_name">Bluetooth LE Secure Client Test</string> 878 <string name="ble_secure_client_test_list_info"> 879 The Bluetooth LE test must be done simultaneously on two devices. 880 This device is the client. All tests listed here must be done with pairing. 881 \n\nTap \"01 Bluetooth LE Client Test\" on this device, then tap \"01 Bluetooth LE Server Test\" on the other device. 882 \nWhen the test is complete, move to the next item. You must complete all tests. 883 </string> 884 <string name="ble_encrypted_client_no_encrypted_characteristic">Error!\nThe Characteristics unencrypted.</string> 885 <string name="ble_encrypted_client_no_encrypted_descriptor">Error!\nThe Descriptor unencrypted.</string> 886 <string name="ble_encrypted_client_fail_write_encrypted_characteristic">It failed to write to Characteristic.</string> 887 <string name="ble_encrypted_client_fail_write_encrypted_descriptor">It failed to write to Descriptor.</string> 888 <string name="ble_encrypted_client_fail_read_encrypted_characteristic">It failed to read the Characteristic.</string> 889 <string name="ble_encrypted_client_fail_read_encrypted_descriptor">It failed to read the Descriptor.</string> 890 <string name="ble_secure_client_test_info"> 891 The Bluetooth LE test must be done simultaneously on two devices. This device is the client. 892 All tests listed here must be done with pairing. 893 </string> 894 895 <string name="ble_bluetooth_disable_title">Bluetooth Disable!</string> 896 <string name="ble_bluetooth_disable_message">Please set bluetooth enable.</string> 897 898 <string name="ble_bluetooth_mismatch_title">Bluetooth pairing state is a mismatch!</string> 899 <string name="ble_bluetooth_mismatch_secure_message"> 900 And even though it has already been trying to run a test of Secure, the device has not been paired. 901 \nGo setting mode, set Bluetooth to pair other device. 902 </string> 903 <string name="ble_bluetooth_mismatch_insecure_message"> 904 And even though it has already been trying to run a test of Insecure, the device has already been paired. 905 \nGo setting mode, set Bluetooth to unpair other device. 906 </string> 907 908 <string name="ble_mtu_unexpected_message">Unexpected MTU request</string> 909 <string name="ble_mtu_mismatch_message">MTU is not correct.(Request:%1$d, Actual:%2$d)</string> 910 <string name="ble_mtu_fail_message">MTU test: failed to receive data</string> 911 912 <!-- Strings for CompanionDeviceTestActivity --> 913 <string name="companion_test">Companion Device Test</string> 914 <string name="companion_test_info"> 915 This test checks that APIs to manage companion devices are working correctly, 916 including showing the dialog to the user to verify a device, as well as updating an internal 917 record once the user made the choice and then removing it.\n\n 918 Before proceeding, make sure you have a bluetooth device nearby and discoverable. 919 Also, make sure that bluetooth is turned on for this device. 920 Once you press the button, wait for a dialog to pop up and select your device from the list. 921 </string> 922 923 <!-- Strings for CompanionDeviceServiceTestActivity --> 924 <string name="companion_service_associate_button">Associate</string> 925 <string name="companion_service_associate_title">Device Association</string> 926 <string name="companion_service_associate_text"> 927 Press the "Associate" button. Wait for a dialog to pop up and select your device from the 928 list. 929 </string> 930 <string name="companion_service_bluetooth_feature_title">Bluetooth Feature Supported</string> 931 <string name="companion_service_bluetooth_feature_text"> 932 PackageManager.FEATURE_BLUETOOTH not supported. This test is not applicable. 933 </string> 934 <string name="companion_service_disassociate_button">Disassociate</string> 935 <string name="companion_service_disassociate_title">Device Disassociation</string> 936 <string name="companion_service_disassociate_text"> 937 Press the "Disassociate" button. Wait for the device to disassociate. 938 </string> 939 <string name="companion_service_present_title">Device Present</string> 940 <string name="companion_service_present_text"> 941 Make your Bluetooth device reachable (this should already be the case from the previous step). 942 Wait until your Bluetooth device is detected by CDM. This may take up to 2 minutes. 943 </string> 944 <string name="companion_service_gone_title">Device Gone</string> 945 <string name="companion_service_gone_text"> 946 Make your Bluetooth device unreachable by placing your bluetooth device inside an RF Bag or 947 powering it off. 948 Wait until your Bluetooth device disappears. This may take up to 2 minutes. 949 </string> 950 <string name="companion_service_test">Companion Device Service Test</string> 951 <string name="companion_service_test_info"> 952 This test checks that APIs to notify the companion app of its associated device going in and 953 out of Bluetooth range are working correctly.\n\n 954 Before proceeding, make sure that you have a Bluetooth LE device nearby and 955 discoverable. Also, make sure that bluetooth is turned on. (Note: the nearby device cannot 956 be a phone) 957 </string> 958 <string name="companion_service_test_summary_title">Test Complete</string> 959 <string name="companion_service_test_summary">Every test passed successfully.</string> 960 961 <!-- Strings for FeatureSummaryActivity --> 962 <string name="feature_summary">Hardware/Software Feature Summary</string> 963 <string name="feature_summary_info">This is a test for...</string> 964 <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string> 965 <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string> 966 <string name="fs_no_data">No data.</string> 967 <string name="fs_legend_good">standard feature reported by device</string> 968 <string name="fs_legend_indeterminate">optional feature not reported by device</string> 969 <string name="fs_legend_warning">non-standard feature reported by device</string> 970 <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string> 971 972 <string name="empty"></string> 973 974 <!-- Strings for HifiUltrasoundTestActivity --> 975 <string name="hifi_ultrasound_test">Hifi Ultrasound Microphone Test</string> 976 <string name="hifi_ultrasound_test_info"> 977 This is a test for near-ultrasound (18500Hz - 20000Hz) microphone response.\n 978 This test requires two devices.\n</string> 979 <string name="hifi_ultrasound_test_play">PLAY</string> 980 <string name="hifi_ultrasound_test_record">RECORD</string> 981 <string name="hifi_ultrasound_test_plot">PLOT</string> 982 <string name="hifi_ultrasound_test_dismiss">DISMISS</string> 983 <string name="hifi_ultrasound_test_ok">OK</string> 984 <string name="hifi_ultrasound_test_instruction1"> 985 Open Hifi Ultrasound Microphone Test on the test device and the reference device.\n 986 Set the media volume of the reference device at 70% and hold it with one hand.\n 987 Hold the testing device with the other hand\n 988 Press the RECORD button on the testing device, then the PLAY button on the reference device within one second.\n 989 After the test, report result on the testing (recording) device.\n</string> 990 <string name="hifi_ultrasound_test_pass">PASS</string> 991 <string name="hifi_ultrasound_test_fail">FAIL</string> 992 <string name="hifi_ultrasound_test_default_false_string">false</string> 993 <string name="hifi_ultrasound_test_mic_no_support"> 994 Device does not support near-ultrasound recording.\n 995 Please report PASS.\n</string> 996 <string name="hifi_ultrasound_test_spkr_no_support"> 997 Device does not support near-ultrasound playback.\n 998 If this is your reference device, please use a different reference device.\n</string> 999 1000 <string name="hifi_ultrasound_speaker_test">Hifi Ultrasound Speaker Test</string> 1001 <string name="hifi_ultrasound_speaker_test_info"> 1002 This is a test for near-ultrasound (18500Hz - 20000Hz) speaker response.\n 1003 This test requires two devices.\n</string> 1004 <string name="hifi_ultrasound_speaker_test_instruction1"> 1005 Open Hifi Ultrasound Speaker Test on the test device and the reference device.\n 1006 Set the media volume of the testing device at 70% and hold it with one hand.\n 1007 Hold the reference device with the other hand\n 1008 Press the RECORD button on the reference device, then the PLAY button on the testing device within one second.\n 1009 After the test, report result on the testing (playback) device.\n</string> 1010 <string name="hifi_ultrasound_speaker_test_mic_no_support"> 1011 Device does not support near-ultrasound recording.\n 1012 If this is your reference device, please use a different reference device.\n</string> 1013 <string name="hifi_ultrasound_speaker_test_spkr_no_support"> 1014 Device does not support near-ultrasound playback.\n 1015 Please report PASS.\n</string> 1016 <string name="hifi_ultrasound_speaker_test_test_side"> 1017 Please wait for the result on the reference device then report here.</string> 1018 <string name="hifi_ultrasound_speaker_test_reference_side"> 1019 Please report on the testing device.\n</string> 1020 1021 <!-- Strings for IgnoreBatteryOptimizationsTestActivity --> 1022 <string name="ibo_test">Ignore Battery Optimizations Test</string> 1023 <string name="ibo_test_info"> 1024 This test verifies that the device provides a user affordance to ask the user if the system 1025 should disable battery optimizations for an app and to allow a user to remove the app from 1026 the exemption list. 1027 </string> 1028 <string name="ibo_auto_power_modes_enabled">Auto power modes enabled.</string> 1029 <string name="ibo_test_start_unexempt_app"> 1030 Remove the test app from the ignore battery optimizations list to begin the test. (Try going 1031 to the App Info page and make sure the system is optimizing battery for the app.) 1032 </string> 1033 <string name="ibo_exempt_app_request"> 1034 Click Next to have the test request the exemption. Grant the exemption when prompted. 1035 </string> 1036 <string name="ibo_next_to_confirm">Press next to confirm.</string> 1037 <string name="ibo_app_not_exempted">The app is not exempted from battery optimizations.</string> 1038 <string name="ibo_unexempt_app"> 1039 Remove the test app from the ignore battery optimizations list. (Either run \"adb shell cmd 1040 deviceidle whitelist -com.android.cts.verifier\" or open the list of apps and their 1041 exemption statuses. Find the test app in the list and remove the app\'s exemption.) 1042 </string> 1043 <string name="ibo_app_is_exempted">The app is exempted from battery optimizations.</string> 1044 <string name="ibo_exempt_app_list"> 1045 Click Next to have the test open the list of apps and their exemption statuses. Find the 1046 test app in the list and exempt it. 1047 </string> 1048 <string name="ibo_unexempt_app_list"> 1049 Click Next to have the test open the list of apps and their exemption statuses. Find the 1050 test app in the list and remove the app\'s exemption. 1051 </string> 1052 1053 <!-- Strings for Location tests --> 1054 <string name="location_gps_test">GPS Test</string> 1055 <string name="location_gps_test_info">This test verifies basic GPS behavior 1056 and callback scheduling. 1057 Make sure the device has line of sight to GPS satellites 1058 (for example, outside, or near a window) 1059 and then press OK to run the automated tests.</string> 1060 1061 <!-- Strings for Location GNSS tests --> 1062 <string name="location_gnss_constellation_type_test">GNSS Measurement Constellation Test</string> 1063 <string name="location_gnss_measure_no_location_test">GNSS Measurement Before Location Test</string> 1064 <string name="location_gnss_reg_test">GNSS Measurement Registration Test</string> 1065 <string name="location_gnss_value_test">GNSS Measurement Values Test</string> 1066 <string name="location_pseudorange_value_test">GNSS Pseudorange Test</string> 1067 <string name="location_gnss_ttff_test">GNSS TTFF Test</string> 1068 <string name="location_gnss_nav_msg_test">GNSS Navigation Message Test</string> 1069 <string name="location_gnss_status_test">GNSS Status Test</string> 1070 <string name="location_gnss_test_info">This test verifies basic GNSS behavior. 1071 Make sure the device has line of sight to GNSS satellites 1072 (for example, stationary on a windowsill. If needed, try again, outside, also with the 1073 device stationary, and with at least some view of the sky.) and then press Next to run 1074 the automated tests.</string> 1075 <string name="location_emergency_call_test_info">This test verifies whether basic features 1076 (wifi, sms, gps) works correctly during the emergency call. Make sure the device is using 1077 a special white listed sim card. The wifi and GPS should be on and have internet connection. 1078 Press the pass button to skip this test if outside US/Canada. 1079 </string> 1080 <string name="emergency_call_confirm_info">This test will dial 911! Please make sure to use a 1081 whitelisted sim card to run this test! 1082 </string> 1083 <string name="emergency_call_skip_info">Current device doesn\'t support cellular network. Skipping the Test. 1084 </string> 1085 <string name="emergency_call_emergency_number_hint_text"> 1086 Emergency Number: 1087 </string> 1088 <string name="emergency_call_current_number_hint_text"> 1089 Current Number: 1090 </string> 1091 <string name="emergency_call_dial_text"> 1092 Dial 911 1093 </string> 1094 <string name="emergency_call_emergency_number_text"> 1095 911 1096 </string> 1097 <string name="location_gnss_test_retry_info">If this test fails, please make sure the device 1098 has line of sight to GNSS satellites (for example, stationary on a windowsill. If needed, 1099 try again, outside, also with the device stationary, with as much view of the sky as 1100 possible.) </string> 1101 <string name="location_emergency_call_gps_test">Emergency Call GPS Test</string> 1102 <string name="location_emergency_call_message_test">Emergency Call Message Test</string> 1103 <string name="location_emergency_call_wifi_test">Emergency Call Wifi Test</string> 1104 1105 <!-- Strings for ConnectivityBackgroundTestActivity --> 1106 <string name="network_background_test">Network Background Connectivity Test</string> 1107 <string name="network_background_test_instructions"> 1108 This test verifies that IPv6 network connectivity continues to work 1109 when the screen is off or is idle for some time.\n\n 1110 1111 1. Join a Wi-Fi network with IPv6 Internet access.\n 1112 2. If the device has battery power, disconnect all power connectors.\n 1113 3. Turn the screen off if possible.\n 1114 4. Wait until the screen turns on or the test result is displayed (it will take at least two minutes).\n 1115 5. If necessary, unlock the device.\n 1116 6. Please mark the test according to the result status indicated.\n 1117 </string> 1118 <string name="network_background_test_start">Start</string> 1119 1120 <!-- Strings for net.MultiNetworkConnectivityTestActivity --> 1121 <string name="multinetwork_connectivity_test">Multinetwork connectivity Test</string> 1122 <string name="multinetwork_connectivity_test_instructions"> 1123 This test verifies that, when a phone has internet connectivity via mobile network 1124 is connected to a Wi-Fi access point that doesn\'t have internet or loses internet access, 1125 it restores the internet activity over the mobile cell network, while connected to the 1126 Wi-Fi access point. \n\n 1127 1128 1. Setup a wireless access point with ability to turn on and off internet access. 1129 2. Have SIM or cellular data connectivity on the phone being tested. 1130 3. Execute the tests with the instructions outlined in the test 1131 4. When the test completes, it will finish and mark it passed. If it fails, it will mark it \n 1132 as failed. 1133 1134 </string> 1135 <string name="multinetwork_connectivity_test_pre_requisites">Prerequisite - Setup a Wi-Fi access point with WPA PSK in which we can turn on or off internet access. Delete that access point from this device if it exists already. </string> 1136 <string name="multinetwork_connectivity_test_start">Start</string> 1137 <string name="multinetwork_connectivity_test_ap_name">Wi-Fi SSID</string> 1138 <string name="multinetwork_connectivity_test_ap_passphrase">WPA 2 passphrase</string> 1139 <string name="multinetwork_connectivity_test_continue">Confirm and continue with test.</string> 1140 <string name="multinetwork_connectivity_test_rerun">Completed. Re-run.</string> 1141 <string name="multinetwork_connectivity_test_running">Running.</string> 1142 <string name="multinetwork_connectivity_test_connect_cellular">Connecting to cellular network.</string> 1143 <string name="multinetwork_connectivity_test_connect_wifi">Connecting to Wi-Fi network.</string> 1144 <string name="multinetwork_connectivity_test_complete">Test completed.</string> 1145 <string name="multinetwork_connectivity_test_progress_1">Waiting for Wi-Fi to lose connectivity.</string> 1146 <string name="multinetwork_connectivity_test_progress_2">Waiting to check connectivity.</string> 1147 <string name="multinetwork_connectivity_test_progress_3">Waiting to make sure Wi-Fi has connectivity.</string> 1148 <string name="multinetwork_connectivity_test_1_desc">Test 1 - Connect to Wi-Fi with no internet doesnt disable current connectivity (new API)</string> 1149 <string name="multinetwork_connectivity_test_2_desc">Test 2 - Connect to Wi-Fi with no internet doesnt disable current connectivity (legacy API)</string> 1150 <string name="multinetwork_connectivity_test_3_desc">Test 3 - When connected to Wi-Fi, on losing connectivity, restores mobile connectivity (legacy API)</string> 1151 <string name="multinetwork_status_wifi_connect_success">Wi-Fi connect success.</string> 1152 <string name="multinetwork_status_mobile_connect_success">Mobile net connect success.</string> 1153 <string name="multinetwork_status_wifi_connect_timed_out">Wi-Fi connect timed out.</string> 1154 <string name="multinetwork_status_wifi_connect_wrong_ap">Wi-Fi connected to wrong access point.</string> 1155 <string name="multinetwork_status_unable_to_toggle_wifi">User did not toggle wifi on and off.</string> 1156 <string name="multinetwork_status_mobile_connect_timed_out">Mobile network connect timed out.</string> 1157 <string name="multinetwork_status_mobile_restore_success">Mobile restore succeeded.</string> 1158 <string name="multinetwork_status_mobile_restore_failed">Mobile restore failed.</string> 1159 <string name="multinetwork_connectivity_test_1_prereq">Make sure that the Hotspot does not have internet access.</string> 1160 <string name="multinetwork_connectivity_test_2_prereq_1">Make sure that the Hotspot has internet access.</string> 1161 <string name="multinetwork_connectivity_test_2_prereq_2">Make sure that the Hotspot does not have internet access. When prompted to go back to using mobile data, choose ok.</string> 1162 <string name="multinetwork_connectivity_test_all_prereq_1">Looks like your device does not support telephony or mobile data. If yes, you can mark test passed and proceed.</string> 1163 <string name="multinetwork_connectivity_test_all_prereq_2">Need mobile data to proceed. Please insert a mobile data capable sim and repeat the test. By marking test as passed, you acknowledge that the device cannot do mobile data.</string> 1164 <string name="multinetwork_status_wifi_connectivity_failed">Wi-Fi connectivity failed.</string> 1165 <string name="multinetwork_connectivity_overlay_permission_message">This test requires the CTS verifier to have the system overlay permission, please locate CTS Verifier app in the next screen, then enable it.</string> 1166 <string name="multinetwork_connectivity_overlay_permission_positive">Settings</string> 1167 <string name="multinetwork_connectivity_overlay_permission_negative">Cancel</string> 1168 <string name="multinetwork_connectivity_turn_wifi_on">Please turn Wi-Fi on.</string> 1169 <string name="multinetwork_connectivity_turn_wifi_off">Please turn Wi-Fi off.</string> 1170 <string name="multinetwork_connectivity_turn_wifi_positive">OK</string> 1171 <string name="multinetwork_connectivity_turn_wifi_negative">Cancel</string> 1172 <!-- Strings for NfcTestActivity --> 1173 <string name="nfc_test">NFC Test</string> 1174 <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with 1175 NFC enabled to exchange messages. One device must be the candidate device running the 1176 software build to be tested, while the other device must be an implementation already 1177 known to be compatible.\n\nThe Tag Verification tests check that your 1178 device can properly read and write to tags of different technologies. The MIFARE 1179 Ultralight test is only applicable for devices that support it. 1180 \n\nThe Host-based card emulation tests check that your device has properly implemented 1181 host-based card emulation. 1182 </string> 1183 1184 <string name="nfc_not_enabled">NFC is not enabled!</string> 1185 <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the 1186 button below to goto Settings and enable it.</string> 1187 <string name="nfc_settings">NFC Settings</string> 1188 <string name="secure_nfc_enabled">\"Require device unlock for NFC\" is enabled!</string> 1189 <string name="secure_nfc_enabled_message">These tests require \"Require device unlock for NFC\" 1190 to be disabled. Click the button below to goto Settings and disable it.</string> 1191 1192 <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string> 1193 <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled. 1194 Click the button below to goto NFC Sharing Settings and enable it.</string> 1195 <string name="ndef_push_settings">NFC Sharing Settings</string> 1196 1197 <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string> 1198 <string name="nfc_ndef_push_sender">NDEF Push Sender</string> 1199 <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string> 1200 <string name="nfc_llcp_version_check">LLCP version check</string> 1201 1202 <string name="nfc_tag_verification">Tag Verification</string> 1203 <string name="nfc_ndef">NDEF</string> 1204 <string name="nfc_mifare_ultralight">MIFARE Ultralight</string> 1205 1206 <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on 1207 another device and touch the devices back to back. The receiver should show a 1208 dialog indicating it has successfully received the correct message!</string> 1209 <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another 1210 device running the \"CTS Verifier NDEF Receiver\"...</string> 1211 1212 <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on 1213 another device and touch the devices back to back. The receiver should show a 1214 dialog indicating it has successfully received the correct message!</string> 1215 <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another 1216 device running the \"CTS Verifier NDEF Sender\"...</string> 1217 <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push 1218 message.</string> 1219 <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push 1220 message.</string> 1221 1222 <string name="nfc_llcp_version_check_info">This test requires two candidate devices 1223 with NFC enabled to exchange P2P messages. Start the \"LLCP version check\" test on 1224 the other candidate device also, and touch the devices back to back. This test 1225 then verifies that the candidate device correctly advises the LLCP version as 1.2</string> 1226 <string name="nfc_llcp_version_check_failure">The candidate devices does not report LLCP 1227 version 1.2 or higher.</string> 1228 <string name="nfc_llcp_version_check_success">The candidate device has a valid LLCP version.</string> 1229 <string name="nfc_tag_verifier">NFC Tag Verifier</string> 1230 <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read 1231 a tag of the chosen technology.</string> 1232 1233 <string name="nfc_scan_tag">Place device on a writable %s tag...</string> 1234 <string name="nfc_write_tag_title">Writable tag discovered!</string> 1235 <string name="nfc_write_tag_message">Press OK to write to this tag...</string> 1236 <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string> 1237 <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string> 1238 <string name="nfc_no_tech">No tag technologies detected...</string> 1239 1240 <string name="nfc_writing_tag">Writing NFC tag...</string> 1241 <string name="nfc_writing_tag_error">Error writing NFC tag...</string> 1242 <string name="nfc_reading_tag">Reading NFC tag...</string> 1243 <string name="nfc_reading_tag_error">Error reading NFC tag...</string> 1244 1245 <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string> 1246 <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string> 1247 1248 <string name="nfc_hce">Host-based card emulation</string> 1249 <string name="nfc_hce_f">Host-based Felica card emulation</string> 1250 <string name="nfc_hce_reader_tests">HCE reader tests</string> 1251 <string name="nfc_hce_f_reader_tests">HCE Felica reader tests</string> 1252 <string name="nfc_hce_emulator_tests">HCE emulator tests</string> 1253 <string name="nfc_hce_f_emulator_tests">HCE Felica emulator tests</string> 1254 <string name="nfc_hce_f_emulator">HCE Felica emulator</string> 1255 <string name="nfc_hce_f_reader">HCE Felica reader</string> 1256 <string name="nfc_hce_emulator_test_info">The host-based card emulation 1257 tests require two devices to be completed. The HCE emulator tests are used 1258 to actually test the host-based card emulation feature of the device-under-test. So the 1259 device running the emulator tests must be the candidate device running the software 1260 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 1261 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 1262 and makes sure the device-under-test implements card emulation correctly.</string> 1263 <string name="nfc_hce_reader_test_info">The host-based card emulation 1264 tests require two devices to be completed. The HCE emulator tests are used 1265 to actually test the host-based card emulation feature of the device-under-test. So the 1266 device running the emulator tests must be the candidate device running the software 1267 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 1268 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 1269 and makes sure the device-under-test implements card emulation correctly. 1270 </string> 1271 <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> 1272 <string name="nfc_hce_please_wait">Please wait</string> 1273 <string name="nfc_hce_setting_up">Setting up card emulation services...</string> 1274 1275 <string name="nfc_hce_default_route_emulator">Default route (Emulator)</string> 1276 <string name="nfc_hce_default_route_reader">Default route (Reader)</string> 1277 <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> 1278 1279 <string name="nfc_hce_protocol_params_emulator">Protocol parameters (Emulator)</string> 1280 <string name="nfc_hce_protocol_params_reader">Protocol parameters (Reader)</string> 1281 <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> 1282 1283 <string name="nfc_hce_single_payment_emulator">Single payment (Emulator)</string> 1284 <string name="nfc_hce_single_payment_reader">Single payment (Reader)</string> 1285 1286 <string name="nfc_hce_dual_payment_emulator">Two payment services (Emulator)</string> 1287 <string name="nfc_hce_dual_payment_reader">Two payment services (Reader)</string> 1288 1289 <string name="nfc_hce_change_default_emulator">Change default payment service (Emulator)</string> 1290 <string name="nfc_hce_change_default_reader">Change default payment service (Reader)</string> 1291 1292 <string name="nfc_hce_tap_reader_title">Tap reader</string> 1293 <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> 1294 1295 <string name="nfc_hce_single_non_payment_emulator">Single non-payment (Emulator)</string> 1296 <string name="nfc_hce_single_non_payment_reader">Single non-payment (Reader)</string> 1297 1298 <string name="nfc_hce_dual_non_payment_emulator">Two non-payment services (Emulator)</string> 1299 <string name="nfc_hce_dual_non_payment_reader">Two non-payment services (Reader)</string> 1300 1301 <string name="nfc_hce_conflicting_non_payment_emulator">Two conflicting non-payment services (Emulator)</string> 1302 <string name="nfc_hce_conflicting_non_payment_reader">Two conflicting non-payment services (Reader)</string> 1303 1304 <string name="nfc_hce_foreground_non_payment_emulator">Foreground override non-payment services (Emulator)</string> 1305 <string name="nfc_hce_foreground_non_payment_reader">Foreground override non-payment services (Reader)</string> 1306 <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> 1307 1308 <string name="nfc_hce_foreground_payment_emulator">Foreground override payment services (Emulator)</string> 1309 <string name="nfc_hce_foreground_payment_reader">Foreground override payment services (Reader)</string> 1310 <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> 1311 <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> 1312 <string name="nfc_hce_offhost_service_emulator">Off-host service (Emulator)</string> 1313 <string name="nfc_hce_offhost_service_reader">Off-host service (Reader)</string> 1314 <string name="nfc_hce_offhost_emulator_help">This test 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> 1315 1316 <string name="nfc_hce_on_and_offhost_service_emulator">On and off-host services (Emulator)</string> 1317 <string name="nfc_hce_on_and_offhost_service_reader">On and off-host services (Reader)</string> 1318 <string name="nfc_hce_on_and_offhost_emulator_help">This test 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> 1319 1320 <string name="nfc_hce_tap_test_emulator">50 successful taps test (Emulator)</string> 1321 <string name="nfc_hce_tap_test_reader">50 successful taps test (Reader)</string> 1322 <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> 1323 <string name="nfc_hce_throughput_emulator">HCE throughput test (Emulator)</string> 1324 <string name="nfc_hce_throughput_reader">HCE throughput test (Reader)</string> 1325 <string name="nfc_hce_throughput_emulator_help">This test 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> 1326 <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> 1327 <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> 1328 <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> 1329 1330 <string name="nfc_hce_payment_dynamic_aids_emulator">Dynamic payment AIDs (Emulator)</string> 1331 <string name="nfc_hce_payment_dynamic_aids_reader">Dynamic payment AIDs (Reader)</string> 1332 <string name="nfc_hce_payment_dynamic_aids_help">This test tries to register dynamic AIDs for a payment service.</string> 1333 1334 <string name="nfc_hce_large_num_aids_emulator">Large number of AIDs (Emulator)</string> 1335 <string name="nfc_hce_large_num_aids_reader">Large number of AIDs (Reader)</string> 1336 <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> 1337 1338 <string name="nfc_hce_payment_prefix_aids_emulator">Payment prefix AIDs (Emulator)</string> 1339 <string name="nfc_hce_payment_prefix_aids_reader">Payment prefix AIDs (Reader)</string> 1340 <string name="nfc_hce_payment_prefix_aids_help">This test statically registers prefix AIDs for a payment service.</string> 1341 1342 <string name="nfc_hce_payment_prefix_aids_emulator_2">Payment prefix AIDs 2 (Emulator)</string> 1343 <string name="nfc_hce_payment_prefix_aids_reader_2">Payment prefix AIDs 2 (Reader)</string> 1344 1345 <string name="nfc_hce_other_prefix_aids_emulator">Other prefix AIDs (Emulator)</string> 1346 <string name="nfc_hce_other_prefix_aids_reader">Other prefix AIDs (Reader)</string> 1347 <string name="nfc_hce_other_prefix_aids_help">This test dynamically registers prefix AIDs for a non-payment service.</string> 1348 1349 <string name="nfc_hce_other_conflicting_prefix_aids_emulator">Conflicting non-payment prefix AIDs (Emulator)</string> 1350 <string name="nfc_hce_other_conflicting_prefix_aids_reader">Conflicting non-payment prefix AIDs (Reader)</string> 1351 <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> 1352 1353 <string name="nfc_screen_on_only_offhost_emulator">Screen on only Off-host Service (Emulator)</string> 1354 <string name="nfc_screen_on_only_offhost_reader">Screen on only Off-host Service (Reader)</string> 1355 <string name="nfc_screen_on_only_offhost_help">This test 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. 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. The expected behavior is the AID can be selected only when the device is in screen on state.</string> 1356 1357 <string name="nfc_screen_off_hce_payment_emulator">Screen off HCE Payment (Emulator)</string> 1358 <string name="nfc_screen_off_hce_payment_reader">Screen off HCE Payment (Reader)</string> 1359 <string name="nfc_screen_off_hce_payment_help">This test verifies emulator responds when device is in screen off state. Please put the emulator to screen off state.</string> 1360 1361 <string name="nfc_payment_service_desc">NFC Payment service</string> 1362 <string name="ppse">PPSE</string> 1363 <string name="mastercard">MasterCard</string> 1364 <string name="visa">Visa</string> 1365 <string name="paymentService1">Payment Service #1</string> 1366 <string name="paymentService2">Payment Service #2</string> 1367 <string name="transportService1">TransportService #1</string> 1368 <string name="transportService2">TransportService #2</string> 1369 <string name="accessService">AccessService</string> 1370 <string name="offhostService">OffhostService</string> 1371 <string name="felicaservice">Felica Service</string> 1372 <string name="UiccTransactionEventService">Uicc Transaction Event Service</string> 1373 <string name="screenOffPaymentService">Screen Off Payment Service</string> 1374 <string name="screenOnOnlyOffHostService">Screen On Only OffHost Service</string> 1375 1376 <string name="nfc_offhost_uicc">Offhost UICC-based card emulation</string> 1377 <string name="nfc_offhost_uicc_emulator_tests">Offhost card emulation emulator tests</string> 1378 <string name="nfc_offhost_uicc_reader_tests">Offhost card emulation reader tests</string> 1379 <string name="nfc_offhost_uicc_transaction_event1_emulator">Offhost transaction event-field off (Emulator)</string> 1380 <string name="nfc_offhost_uicc_transaction_event1_reader">Offhost transaction event-field off (Reader)</string> 1381 <string name="nfc_offhost_uicc_transaction_event2_emulator">Offhost transaction event-deselect (Emulator)</string> 1382 <string name="nfc_offhost_uicc_transaction_event2_reader">Offhost transaction event-deselect (Reader)</string> 1383 <string name="nfc_offhost_uicc_transaction_event3_emulator">Offhost transaction event-HCI CMD (Emulator)</string> 1384 <string name="nfc_offhost_uicc_transaction_event3_reader">Offhost transaction event-HCI CMD (Reader)</string> 1385 1386 <string name="nfc_offhost_uicc_emulator_test_info">The offhost-based card emulation 1387 tests require two devices to be completed. The emulator tests are used 1388 to actually test the off-based card emulation feature of the device-under-test. So the 1389 device running the emulator tests must be the candidate device running the software 1390 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 1391 in the "Offhost reader tests" section. The "reader test" acts as a NFC terminal/POS 1392 and makes sure the device-under-test implements card emulation correctly 1393 </string> 1394 <string name="nfc_offhost_uicc_reader_test_info">The offhost-based card emulation 1395 tests require two devices to be completed. The emulator tests are used 1396 to actually test the off-based card emulation feature of the device-under-test. So the 1397 device running the emulator tests must be the candidate device running the software 1398 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 1399 in the "Offhost card emulation reader tests" section. The "reader test" acts as a NFC terminal/POS 1400 and makes sure the device-under-test implements card emulation correctly. 1401 </string> 1402 <string name="nfc_offhost_uicc_type_selection">By default Offhost card emulation applications run on type A. 1403 If your device supports 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> 1404 <string name="nfc_offhost_please_wait">Please wait</string> 1405 <string name="nfc_offhost_setting_up">Setting up card emulation services...</string> 1406 <string name="nfc_offhost_uicc_transaction_event_emulator_help"> This is an optional test for Android version beofre S. This is okay to set this test to passed and continue. Switch application to background before starting tests. Successful transaction event will switch application to foreground with transaction event data.</string> 1407 1408 <!-- Strings for Sensor Test Activities --> 1409 <string name="snsr_device_admin_receiver">Sensor Tests Device Admin Receiver</string> 1410 <string name="snsr_test_summary">Tests passed: %1$d, Tests skipped: %2$d, Tests failed: %3$d</string> 1411 <string name="snsr_test_complete">Test completed without errors.</string> 1412 <string name="snsr_test_complete_with_errors">Test completed with errors which indicates 1413 the device does not meet Android compatibility requirement. 1414 This will degrade user experience and cause applications to misbehave. 1415 To help debugging, please take a bug report and back up contents under 1416 /sdcard/sensorTests of the device under test. 1417 </string> 1418 <string name="snsr_test_pass">PASS</string> 1419 <string name="snsr_test_skipped">SKIPPED</string> 1420 <string name="snsr_test_fail">FAIL</string> 1421 <string name="snsr_execution_time">Test execution time %1$s sec</string> 1422 <string name="snsr_rvcvxchk_test">Rotation Vector CV Crosscheck</string> 1423 <string name="snsr_rvcvxchk_test_rec">Rotation Vector CV Recording</string> 1424 1425 <!-- Strings to interact with users in Sensor Tests --> 1426 <string name="snsr_test_play_sound">A sound will be played once the verification is complete...</string> 1427 <string name="snsr_no_interaction">Leave the device on top of a flat surface.</string> 1428 <string name="snsr_interaction_needed">Once the test begins, you will have to wave your hand over the front of the device.</string> 1429 <string name="snsr_interaction_needed_prox">Once the test begins, if possible, flip the device so it is face down on a surface, then flip back to face up after a second or two. Otherwise, wave your hand over the front of the device.</string> 1430 <string name="snsr_device_steady">Keep the device steady.</string> 1431 <string name="snsr_keep_device_rotating_clockwise">Once the test begins, you will have to keep rotating the device clockwise.</string> 1432 <string name="snsr_wait_for_user">Press \'Next\' to continue.</string> 1433 <string name="snsr_wait_to_begin">Press \'Next\' to begin.</string> 1434 <string name="snsr_wait_to_retry">Press \'Retry\' to rerun or \'Fail and Next\' to skip to next.</string> 1435 <string name="snsr_wait_to_finish">Press \'Retry\' to rerun or \'Finish\' to end.</string> 1436 <string name="snsr_on_complete_return">After completing the task, go back to this test.</string> 1437 <string name="snsr_movement_expected">Movement was expected during the test. Found=%1$b.</string> 1438 <string name="snsr_sensor_feature_deactivation">IMPORTANT NOTE: Please also turn off any special features in the 1439 device that use sensors (wake up gestures, motion triggered events, moves, etc). 1440 Not doing so is expected to cause test failures. Once you are done, you can begin the test.</string> 1441 <string name="snsr_setting_mode_request">You will be redirected to set \'%1$s\' to: %2$s.</string> 1442 <string name="snsr_setting_mode_set">\'%1$s\' set to: %2$s.</string> 1443 <string name="snsr_setting_mode_not_set">\'%1$s\' not set to: %2$s.</string> 1444 <string name="snsr_setting_airplane_mode">Airplane mode</string> 1445 <string name="snsr_setting_screen_brightness_mode">Adaptive Brightness</string> 1446 <string name="snsr_setting_auto_rotate_screen_mode">Auto-rotate screen</string> 1447 <string name="snsr_setting_keep_screen_on">Stay awake</string> 1448 <string name="snsr_setting_location_mode">Location</string> 1449 <string name="snsr_setting_ambient_display">Ambient Display</string> 1450 <string name="snsr_pass_on_error">Pass Anyway</string> 1451 <string name="snsr_run_automated_tests">The screen will be turned off to execute the tests, 1452 when tests complete, the device will vibrate and the screen will be turned back on.</string> 1453 1454 <!-- Accelerometer --> 1455 <string name="snsr_accel_test">Accelerometer Test</string> 1456 <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> 1457 <string name="snsr_accel_m_test">Accelerometer Measurement Tests</string> 1458 <string name="snsr_accel_test_face_up">Place the device on a flat surface with the screen 1459 facing the ceiling.</string> 1460 <string name="snsr_accel_test_face_down">Place the device on a flat surface with the screen 1461 facing it.</string> 1462 <string name="snsr_accel_test_right_side">Place the device in a flat surface resting vertically 1463 on its right side.</string> 1464 <string name="snsr_accel_test_left_side">Place the device in a flat surface resting vertically 1465 on its left side.</string> 1466 <string name="snsr_accel_test_top_side">Place the device in a flat surface resting vertically 1467 on its top side.</string> 1468 <string name="snsr_accel_test_bottom_side">Place the device in a flat surface resting vertically 1469 on its bottom side.</string> 1470 1471 <!-- Gyroscope --> 1472 <string name="snsr_gyro_test">Gyroscope Test</string> 1473 <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> 1474 <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string> 1475 <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string> 1476 <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> 1477 <string name="snsr_gyro_test_degrees_title">Wrong units?</string> 1478 <string name="snsr_gyro_test_degrees_message">These values looks like degrees per second. These should be radians per second!</string> 1479 <string name="snsr_gyro_m_test">Gyroscope Measurement Test</string> 1480 <string name="snsr_gyro_device_placement">Place the device in a flat surface with the screen 1481 facing the ceiling. Read the instructions for each scenario, before you perform the 1482 test.</string> 1483 <string name="snsr_gyro_device_static">Leave the device static.</string> 1484 <string name="snsr_gyro_rotate_device">Once you begin the test, you will need to rotate the 1485 device 360deg (one time) in the direction show by the animation, then place it back on the 1486 flat surface.</string> 1487 1488 <!-- Heart Rate --> 1489 <string name="snsr_heartrate_test">Heart Rate Test</string> 1490 <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> 1491 <string name="snsr_heartrate_test_no_heartrate_title">No heart rate monitor?</string> 1492 <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> 1493 1494 <!-- Hinge Angle --> 1495 <string name="snsr_hinge_angle_test">Hinge Angle Test</string> 1496 <string name="snsr_hinge_angle_test_instructions">Place the device into its default position. Read the instructions for each scenario before you perform the test.</string> 1497 <string name="snsr_hinge_angle_test_exercise_hinge">Transition the device from its default position as far in one direction as the hinge sensor measures. 1498 Then, transition it in the other direction as far as it can measure. Lastly, return the device back to its default position. Once completed, press \"Next\" to finish the test.</string> 1499 1500 <!-- Magnetic Field --> 1501 <string name="snsr_mag_m_test">Magnetic Field Measurement Tests</string> 1502 <string name="snsr_mag_verify_norm">Verifying the Norm...</string> 1503 <string name="snsr_mag_verify_offset">Verifying the Offset...</string> 1504 <string name="snsr_mag_verify_std_dev">Verifying the Standard Deviation...</string> 1505 <string name="snsr_mag_verify_calibrated_uncalibrated">Verifying the relationship between 1506 calibrated and uncalibrated measurements...</string> 1507 <string name="snsr_mag_calibration_description">Please calibrate the Magnetometer by moving 1508 it in 8 shapes in different orientations. Click \"Next\" to start and click \"Next\" once again to end calibration.</string> 1509 <string name="snsr_mag_calibration_complete">When done, leave the device in a flat surface, far 1510 from all metallic objects (if the test does not pass, try re-running it outdoors).</string> 1511 <string name="snsr_mag_measurement">-> (%1$.2f, %2$.2f, %3$.2f) : %4$.2f uT</string> 1512 <string name="snsr_mag_move_outside">Unable to acquire location. Please move outside to allow a location fix.</string> 1513 <string name="snsr_mag_no_location">Failed to acquire location. Using default magnetic field of %1$.2f uT.</string> 1514 1515 <!-- Sensor Value Accuracy --> 1516 <string name="snsr_rot_vec_test">Rotation Vector Accuracy Test</string> 1517 <string name="snsr_event_length">Sensor(%3$s). Event values expected to have size=%1$d. Found=%2$d.</string> 1518 <string name="snsr_event_value">Sensor(%3$s). Event value[0] expected to be of value=%1$f. Found=%2$f.</string> 1519 <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> 1520 1521 <!-- Sensor Batching --> 1522 <string name="snsr_batch_test">Sensor Batching Manual Tests</string> 1523 <string name="snsr_batching_walking_needed">Once the test begins, you will have to take the 1524 device in your hand and walk.</string> 1525 1526 <!-- Sensor Synchronization --> 1527 <string name="snsr_synch_test">Sensor Synchronization Test</string> 1528 1529 <!-- Step Counter and Detector --> 1530 <string name="snsr_step_counter_test">Step Counter and Detector Tests</string> 1531 <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> 1532 <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> 1533 <string name="snsr_step_counter_expected_steps">At least %1$d steps are expected to be reported. Reported=%2$d.</string> 1534 <string name="snsr_step_counter_detected_reported">Steps reported by user=%1$d. Steps counted=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 1535 <string name="snsr_step_detector_detected_reported">Steps reported by user=%1$d. Steps detected=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 1536 <string name="snsr_step_counter_event_changed">Step counter expected to increase monotonically, with a delta > 0. Found=%1$d. Timestamp=%2$d.</string> 1537 <string name="snsr_step_reported">%1$d | User reported step.</string> 1538 <string name="snsr_step_counter_event">%1$d | Step Counter event. count=%2$d.</string> 1539 <string name="snsr_step_detector_event">%1$d | Step Detector event.</string> 1540 1541 <!-- Step Counter and Detector Permission --> 1542 <string name="snsr_step_permission_test">Step Permission Test</string> 1543 <string name="snsr_step_permission_disable">Please change the \'Physical Activity\' permission for CtsVerifier to \'Deny\'</string> 1544 <string name="snsr_step_permission_enable">Please change the \'Physical Activity\' permission for CtsVerifier to \'Allow\'</string> 1545 <string name="snsr_step_permission_walk">Please begin walking while holding the device. A sound will play when you may stop walking</string> 1546 1547 <!-- Device suspend tests --> 1548 <string name="snsr_device_suspend_test">Device Suspend Tests</string> 1549 <string name="snsr_device_did_not_go_into_suspend">Device did not go into suspend mode during test execution </string> 1550 <string name="snsr_batch_did_not_arrive_at_expected_time">Batch did not arrive at the expected time estimatedBatchArrivalMs=%1$d 1551 firstEventReceivedMs=%2$d diffMs=%3$d toleranceMs=%4$d </string> 1552 <string name="snsr_device_suspend_test_instr">One you begin the test, disconnect USB, turn off the display and allow 1553 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> 1554 <string name="snsr_device_suspend_service">Device Suspend Service</string> 1555 <string name="snsr_device_suspend_service_active">Device Suspend Test Active</string> 1556 <string name="snsr_device_suspend_service_notification">Device Suspend Test is using sensors.</string> 1557 1558 <!-- Significant Motion --> 1559 <string name="snsr_significant_motion_test">Significant Motion Tests</string> 1560 <string name="snsr_significant_motion_event_arrival">Event expected to trigger. Triggered=%1$s.</string> 1561 <string name="snsr_significant_motion_event_type">Event expected to be of type=%1$d. Found=%2$d.</string> 1562 <string name="snsr_significant_motion_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string> 1563 <string name="snsr_significant_motion_disable_info">Significant Motion is expected to disable itself after it triggers once.</string> 1564 <string name="snsr_significant_motion_test_trigger">Once you begin the test, you will need to walk for Significant Motion to be detected.</string> 1565 <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> 1566 <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> 1567 <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> 1568 <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> 1569 <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> 1570 <string name="snsr_significant_motion_registration">Expected to be able to register for TriggerSensor. Found=%1$b.</string> 1571 <string name="snsr_significant_motion_cancelation">Expected to be able to cancel TriggerSensor. Found=%b.</string> 1572 <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. 1573 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> 1574 <string name="snsr_device_did_not_wake_up_at_trigger">Device did not wakeup at trigger time. wakeTime=%1$d ms triggerTime=%2$d ms</string> 1575 1576 <!-- Event sanitization for idle UIDs --> 1577 <string name="snsr_event_sanitization_test">Event sanitization for idle UID test</string> 1578 <string name="snsr_event_sanitization_test_setup">Run the \'adb shell cmd sensorservice set-uid-state com.android.cts.verifier idle\' shell command 1579 to emulate the CtsVerifier UID being idle.</string> 1580 <string name="snsr_event_sanitization_test_cleanup">Run the \'adb shell cmd sensorservice reset-uid-state com.android.cts.verifier\' shell command 1581 to stop emulating the CtsVerifier UID being idle. Failing to do that would lead to other tests failing!</string> 1582 <string name="snsr_significant_motion_test_uid_idle">Move around with the device to try triggering significant motion</string> 1583 <string name="snsr_significant_motion_test_uid_idle_expectation">No trigger events should be generated while idle</string> 1584 <string name="snsr_proximity_test_uid_idle">Touch the proximity sensor to try triggering it</string> 1585 <string name="snsr_proximity_test_uid_idle_expectation">No on-change events should be generated while idle</string> 1586 1587 <!-- Low Latency Off-Body Detect --> 1588 <string name="snsr_offbody_sensor_test">Off Body Sensor Tests</string> 1589 <string name="snsr_offbody_sensor_registration">Registration failed for low latency offbody detect sensor.\n</string> 1590 <string name="snsr_offbody_event_arrival">Expected to receive a low latency offbody detect event. Found=%b.</string> 1591 <string name="snsr_offbody_event_type">Event expected to be of type=%1$d. Found=%2$d.</string> 1592 <string name="snsr_offbody_event_invalid_value">Invalid value received for offbody state; Expected value %1$d or %2$d. Found=%2$d.</string> 1593 <string name="snsr_offbody_event_wrong_value">Expected to receive an event having value=%1$d. Found=%2$d.</string> 1594 <string name="snsr_offbody_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string> 1595 <string name="snsr_offbody_response_timing_violation">%1$s event maximum allowed latency is %2$d. Found=%3$d ms.</string> 1596 <string name="snsr_offbody_state_change">Offbody state changed to %1$d. Timestamp=%2$d.</string> 1597 <string name="snsr_start_offbody_sensor_test_instr">Put watch on your wrist and then click Next button.</string> 1598 <string name="snsr_start_onbody_sensor_test_instr">Remove the watch from your wrist and then click Next button.</string> 1599 <string name="snsr_offbody_detect_test_instr">Click Next button, then immediate remove the watch from your wrist after the countdown reaches 0.</string> 1600 <string name="snsr_offbody_detect_test_countdown">Countdown: %1$d.</string> 1601 <string name="snsr_onbody_detect_test_instr">Click Next button, then immediately attach the watch on your wrist.</string> 1602 <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> 1603 1604 <!-- Strings for Sensor CTS tests inside CtsVerifier --> 1605 <string name="snsr_single_sensor_tests">CTS Single Sensor Tests</string> 1606 <string name="snsr_sensor_integration_tests">CTS Sensor Integration Tests</string> 1607 <string name="snsr_sensor_test">CTS Sensor Test</string> 1608 <string name="snsr_sensor_batching_tests">CTS Sensor Batching Tests</string> 1609 1610 <!-- String for DynamicSensorDiscoveryTest --> 1611 <string name="snsr_dynamic_sensor_discovery_test">Dynamic Sensor Discovery Test</string> 1612 1613 <!-- Strings for Sample Test Activities --> 1614 <string name="share_button_text">Share</string> 1615 <string name="sample_framework_test">Sample Framework Test</string> 1616 <string name="sample_test">Sample Test</string> 1617 <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> 1618 1619 <!-- Strings for Camera Orientation --> 1620 <string name="camera_orientation">Camera Orientation</string> 1621 <string name="co_info">This test verifies the orientation capabilities of 1622 camera preview and capture.\n - The left view shows a preview window rotated 1623 by a given magnitude of degrees.\n - The right view, after taking 1624 a photo, shows the captured image.\n - For each camera and orientation, both 1625 the left and right views should appear rotated by the amount of 1626 degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose 1627 \"Fail\".\n - For front-facing cameras, the test will horizontally mirror 1628 the captured image prior to rotation, in attempt to make the left and right 1629 views appear the same.\n - The physical orientation of the device does not 1630 matter.\n - Read the message above the \"Take Photo\" button for 1631 step-by-step instructions. 1632 </string> 1633 <string name="co_preview_label">Camera preview</string> 1634 <string name="co_format_label">Oriented photo</string> 1635 <string name="co_camera_label">Camera:</string> 1636 <string name="co_orientation_label">Orientation</string> 1637 <string name="co_instruction_heading_label">Instruction:</string> 1638 <string name="co_instruction_text_photo_label">Take a photo</string> 1639 <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> 1640 <string name="co_instruction_text_extra_label">(mirrored horizontally prior to rotation, since camera is front-facing)</string> 1641 <string name="co_photo_button_caption">Take Photo</string> 1642 1643 <!-- Strings for Camera Intents --> 1644 <string name="camera_intents">Camera Intents</string> 1645 <string name="ci_info"> 1646 This test verifies that the default camera app is firing intents 1647 after pictures/videos are taken. It also verifies that when the 1648 default camera app is invoked via intents, the launch intents work, 1649 ,broadcast intents are received when appropriate per the SDK 1650 documentation and also, that the intent results do not have location 1651 information in them. Before starting with the tests, please go to the 1652 Settings app and deny location permissions to the CtsVerifier app, and 1653 after finishing with the camera intent tests, please go to the Settings app and 1654 restore location permissions, otherwise, other tests may fail.\n\n 1655 - Read the message above the \"Start Test\" button for 1656 step-by-step instructions. 1657 </string> 1658 <string name="ci_preview_label">Camera preview</string> 1659 <string name="ci_format_label">Oriented photo</string> 1660 <string name="ci_camera_label">Camera:</string> 1661 <string name="ci_intents_label">Intents Test</string> 1662 <string name="ci_intents_direction_label">clockwise</string> 1663 <string name="ci_instruction_heading_label">Instructions:</string> 1664 <string name="ci_location_permissions_error">Please give CTS Verifier location permissions before clicking on the pass / fail button</string> 1665 <string name="ci_location_permissions_fail_error">Please give CTS Verifier location permissions if the fail button needs to be clicked</string> 1666 <string name="ci_directory_creation_error">CTS Verifier debug directory could not be created, please try again</string> 1667 <string name="ci_instruction_text_photo_label">READ BEFORE STARTING TEST</string> 1668 <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> 1669 <string name="ci_instruction_text_app_picture_label">\n 1670 1671 1. Click Open Settings and deny location permissions to CTS Verifier and return. \n 1672 2. Click Start Test. \n 1673 3. Go to home screen (HOME key). \n 1674 4. Launch Camera application. \n 1675 5. Capture photo within 1 minute. \n 1676 6. Return to CTS verifier app. \n 1677 7. Pass button will light up if intent and URI triggers were fired.\n 1678 8. Click "Pass" if possible, otherwise open settings app, allow location again and click "Fail". 1679 </string> 1680 <string name="ci_instruction_text_app_video_label">\n 1681 1. Click Start Test. \n 1682 2. Go to home screen (HOME key). \n 1683 3. Launch Camera application. \n 1684 4. Capture video within 1 minute. \n 1685 5. Return to CTS verifier app. \n 1686 6. Pass button will light up if intent and URI triggers were fired.\n 1687 7. Click "Pass" if possible, otherwise open settings app, allow location again and click "Fail". 1688 </string> 1689 <string name="ci_instruction_text_intent_picture_label">\n 1690 1. Click Start Test.\n 1691 2. Camera app will launch, prompting to take photo.\n 1692 3. Capture/confirm photo using camera app controls within 1 minute.\n 1693 4. Pass button will light up if intent and URI trigger were NOT received.\n 1694 5. Click "Pass" if possible, otherwise open settings app, allow location again and click "Fail". 1695 </string> 1696 <string name="ci_instruction_text_intent_picture_secure_label">\n 1697 1. Click Start Test.\n 1698 2. Camera app will launch, prompting to take photo.\n 1699 3. Capture/confirm photo using camera app controls within 1 minute.\n 1700 4. Pass button will light up if intent and URI trigger were NOT received.\n 1701 5. Click "Pass" if possible, otherwise open settings app, allow location again and click "Fail". 1702 </string> 1703 <string name="ci_instruction_text_intent_video_label">\n 1704 1. Click Start Test.\n 1705 2. Camera app will launch, prompting to take video.\n 1706 3. Capture/confirm video using camera app controls within 1 minute.\n 1707 4. Return to the CTS Verifier app. Click Open Settings and give back CTS Verifier location permissions \n 1708 (Note this must be done before clicking on Pass / Fail).\n 1709 5. Click "Pass" if possible. 1710 </string> 1711 <string name="ci_start_test_button_caption">Start Test</string> 1712 <string name="ci_settings_button_caption">Open Settings</string> 1713 1714 <!-- Strings for Camera Formats --> 1715 <string name="camera_format">Camera Formats</string> 1716 <string name="cf_info">This test checks that all the supported 1717 output formats for camera preview callbacks work correctly, and 1718 that the mandatory formats are available. \n - The left view shows 1719 a standard preview window. \n - The right view shows the output 1720 processed from camera preview callbacks. \n - For each camera, 1721 resolution, and format combination in the dropdowns, the right 1722 view should look the same as the left, and neither should have 1723 streaks, lines, or other artifacts. \n - For front-facing cameras, 1724 the right view must be horizontally mirrored relative to the left 1725 view.\n - Note that the frame rate of the right view may be much 1726 lower than on the left; this is not an indication of a failed 1727 test.\n - The next button triggers the next resolution and format 1728 combination of the current camera to show; this is optional. 1729 </string> 1730 <string name="cf_preview_label">Normal preview</string> 1731 <string name="cf_format_label">Processed callback data</string> 1732 1733 <!-- Strings for Camera Video --> 1734 <string name="record_button_text">Test</string> 1735 <string name="camera_video">Camera Video</string> 1736 <string name="video_info"> This test checks video capture 1737 at different resolutions. \n - The left view window shows the preview. 1738 \n - Pressing the test button will trigger three 1739 seconds of video recording. Playback will show up in the right view 1740 window after recording is complete. \n - Use the spinners to choose 1741 camera and resolution combinations. The playback should be similar 1742 to what you saw in preview. \n - The next button triggers test for the next 1743 untested resolution of the currently selected camera. - After all possible 1744 combinations are tested, the pass button will be enabled. You may press the 1745 pass button to indicate a pass. \n - You may press fail button any time 1746 during the test to indicate failure. \n 1747 </string> 1748 <string name="video_capture_label">Video capture</string> 1749 <string name="video_playback_label">Video playback</string> 1750 <string name="dialog_fail_test">Test failed</string> 1751 <string name="fail_quit">Fail and quit</string> 1752 <string name="cancel">Cancel</string> 1753 <string name="status_ready">Ready</string> 1754 <string name="status_recording">Recording</string> 1755 <string name="status_playback">Playing back</string> 1756 1757 <!-- Strings for USB accessory test activity --> 1758 <string name="usb_accessory_test">USB Accessory Test</string> 1759 <string name="usb_accessory_test_info"> 1760 1. Install the Cts Verifier USB Companion app on a separate helper device. 1761 \n\n2. Start the accessory test companion in the Cts Verifier USB Companion. 1762 \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". 1763 \n\n4. Confirm access to the USB device on the helper device. 1764 \n\n5. Confirm access to the USB accessory on this device 1765 \n\n6. Confirm access to the USB device on the helper again. 1766 \n\n7. Test will run and complete automatically in less than 30 seconds. 1767 \n\n8. Cancel all further dialogs on this device 1768 </string> 1769 <string name="usb_accessory_test_step1"> 1770 In this specific order: 1771 \n1. Install the Cts Verifier USB Companion app on a separate helper device. 1772 \n2. Start the accessory test companion in the Cts Verifier USB Companion. 1773 \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". 1774 \n4. Confirm access to the USB device on the helper device. Only confirm once. 1775 \n5. Confirm access to the USB accessory on this device. 1776 \n6. Confirm access to the USB device on the helper device again. 1777 \n\nResult: A progress indicator should appear or test will finish. 1778 </string> 1779 <string name="usb_accessory_test_step2"> 1780 Test is running and will complete automatically in less than 30 seconds. 1781 </string> 1782 1783 <!-- String for the USB device test activity --> 1784 <string name="usb_device_test">USB Device Test</string> 1785 <string name="usb_device_test_info"> 1786 1. Install the Cts Verifier USB Companion app on a separate helper device. 1787 \n\n2. Start the device test companion in the Cts Verifier USB Companion. 1788 \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". 1789 \n\n4. Confirm access to the USB device on this device. Do <u>not</u> make this app the default app for the device. 1790 \n\n5. Confirm access to the USB accessory on the helper device. 1791 \n\n6. Confirm access to the USB device on this device again. Do <u>not</u> make this app the default app for the device. 1792 \n\n7. Test will run and complete automatically in less than 30 seconds. 1793 \n\n8. Cancel all further dialogs on the helper device. 1794 </string> 1795 <string name="usb_device_test_step1"> 1796 In this specific order: 1797 \n1. Install the Cts Verifier USB Companion app on a separate helper device. 1798 \n2. Start the device test companion in the Cts Verifier USB Companion. 1799 \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". 1800 \n\nResult: A dialog should show up on this device asking for access to a USB device. 1801 </string> 1802 <string name="usb_device_test_step2"> 1803 Confirm access to the USB device on this device. Do <u>not</u> make this app the default app for the device. 1804 \n\nResult: Dialogs should show up on this device and on the helper device asking for access to a USB device/accessory. 1805 </string> 1806 <string name="usb_device_test_step3"> 1807 1. Confirm access to the USB accessory on the helper device. 1808 \n2. Confirm access to the USB device on this device again. Do <u>not</u> make this app the default app for the device. 1809 \n\nResult: A progress indicator should appear or test will finish. 1810 </string> 1811 <string name="usb_device_test_step4"> 1812 Test is running and will complete automatically in a less than 30 seconds. 1813 </string> 1814 <string name="usb_device_unexpected">Usb companion device is not as expected %1$s. Please retry test.</string> 1815 1816 <!-- Strings for MTP host test activity --> 1817 <string name="mtp_host_test">MTP Host Test</string> 1818 <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> 1819 <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> 1820 <string name="mtp_host_grant_permission_message">Grant permission.\nReply a dialog asking device permission.</string> 1821 <string name="mtp_host_test_read_event_message">Test MtpDevice#readEvent.\nTake a picture at the connected device.</string> 1822 <string name="mtp_host_test_send_object_message">Test MtpDevice#sendObject.</string> 1823 <string name="mtp_host_test_file_browse_message">Test MTP file browsing.\nCheck if the UI to browse files in the connected devices was shown automatically. If not, tap a notification on this device saying the other MTP device is connected. If different application launched, go to the applicaiton settings by clicking the App Settings button, open the detailes settings page of the app, clear the default action settings, and retry. </string> 1824 <string name="mtp_app_settings">App Settings</string> 1825 1826 <!-- Strings for the Camera ITS test activity --> 1827 <string name="camera_its_test">Camera ITS Test</string> 1828 <string name="camera_its_test_info"> 1829 1. Connect your Android device to a computer with adb installed via a USB cable. 1830 \n\n2. Setup the CameraITS test environment by following the setup instructions in the 1831 README file found in the CameraITS directory included in the CTS Verifier bundle 1832 (cd CameraITS; source build/envsetup.sh;). 1833 \n\n3. Setup the test scene described in the CameraITS README file, and aim the camera 1834 at it. 1835 \n\n4. Run the full ITS test suite on all possible camera Ids. 1836 (cd CameraITS; python tools/run_all_tests.py). Once all 1837 of the tests have been run, the \'PASS\' button will be enabled if all of the tests have 1838 succeeded. Please note that these tests can take more than 2 hours to run on some devices. 1839 </string> 1840 <string name="no_camera_manager"> 1841 No camera manager exists! This test device is in a bad state. 1842 </string> 1843 <string name="all_exempted_devices"> 1844 All cameras on this device are exempted from ITS - Pass. 1845 </string> 1846 <string name="its_test_passed">All Camera ITS tests passed. Pass button enabled!</string> 1847 <string name="its_test_failed">Some Camera ITS tests failed.</string> 1848 <string name="its_version_mismatch"> 1849 CtsVerifier and ITS script version mismatch. Please update CtsVerifier and ITS script. 1850 </string> 1851 <string name="its_test_progress">ITS test progress will be shown here.</string> 1852 1853 <!-- Strings for the Camera Webcam test activity --> 1854 <string name="camera_webcam_test">Camera Webcam Test</string> 1855 <string name="camera_webcam_test_info"> 1856 This test verifies the FPS rates the device advertises as a webcam. It also 1857 includes manual verification on the functionality of the webcam stream. 1858 1859 \n\nInstructions for Test Run: 1860 \n1. Connect your Android device to a computer with adb installed via a USB cable. 1861 \n\n2. Setup the Camera Webcam test environment by following the setup instructions in the 1862 README file found in the DeviceAsWebcam directory 1863 (packages/services/DeviceAsWebcam/tests). 1864 1865 \n\n3. Ensure the camera is aimed at a bright scene to get the most accurate FPS reading. 1866 \n\n4. Run the test script. 1867 (python run_webcam_test.py -c config.yml). 1868 Once the test has been run, the \'Yes\' and \'No\' buttons will be enabled. Confirm if the frames 1869 from the webcam service were okay. Then, click \'Done\'. The \'PASS\' will be enabled 1870 if the script results passed and the frames contained no issues. 1871 </string> 1872 1873 <string name="camera_webcam_frames_pass">Yes</string> 1874 <string name="camera_webcam_frames_fail">No</string> 1875 <string name="camera_webcam_done_button">Done</string> 1876 <string name="camera_webcam_start_text">Run the test script to begin.</string> 1877 <string name="camera_webcam_confirm_frames_text">Webcam testing complete. Confirm if the frames from webcam stream were okay.</string> 1878 <string name="camera_webcam_results_pass_frames_fail_text">Script results passed but frames contained errors. Test failed. Click Done to complete.</string> 1879 <string name="camera_webcam_results_pass_frames_pass_text">Script results passed and frames were normal. Test passed Click Done to complete.</string> 1880 <string name="camera_webcam_results_fail_frames_pass_text">Script results failed but frames were normal. Test failed. Click Done to complete.</string> 1881 <string name="camera_webcam_results_fail_frames_fail_text">Script results failed and frames contained errors. Test failed. Click Done to complete.</string> 1882 <string name="camera_webcam_not_supported_text">Webcam feature not supported. Test skipped. Click Done to complete.</string> 1883 1884 <!-- Strings for the Camera Flashlight test activity --> 1885 <string name="camera_flashlight_test">Camera Flashlight</string> 1886 <string name="camera_flashlight_info"> 1887 This test checks the flashlight functionality. It will turn on and off the flashlight of 1888 each camera device that has a flash unit. Follow the instructions on screen and observe the 1889 flashlight status changing. 1890 </string> 1891 <string name="camera_flashlight_start_button">Start</string> 1892 <string name="camera_flashlight_next_button">Next</string> 1893 <string name="camera_flashlight_done_button">Done</string> 1894 <string name="camera_flashlight_on_button">On</string> 1895 <string name="camera_flashlight_off_button">Off</string> 1896 <string name="camera_flashlight_start_text">Press Start to start flashlight test.</string> 1897 <string name="camera_flashlight_question_text">Is Camera %1$s flashlight on or off?</string> 1898 <string name="camera_flashlight_next_text">Ok. Press next.</string> 1899 <string name="camera_flashlight_failed_text">Test failed. Press Done or Fail button.</string> 1900 <string name="camera_flashlight_passed_text">All tests passed. Press Done or Pass button. 1901 </string> 1902 1903 <!-- Strings for the Camera Performance test activity --> 1904 <string name="camera_performance_test">Camera Performance</string> 1905 <string name="camera_performance_test_info"> 1906 This activity will run performance test cases. For optimal and consistent results please 1907 make sure that all camera sensors are pointing in a direction with sufficiently bright 1908 light source. 1909 </string> 1910 <string name="camera_performance_spinner_text">Running CTS performance test case...</string> 1911 <string name="camera_performance_result_title">Test Result</string> 1912 1913 <!-- Strings for StreamingVideoActivity --> 1914 <string name="streaming_video">Streaming Video Quality Verifier</string> 1915 <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> 1916 <string name="sv_no_data">No videos.</string> 1917 <string name="sv_failed_title">Test Failed</string> 1918 <string name="sv_failed_message">Unable to play stream. See log for details.</string> 1919 1920 <!-- Strings for MediaCodecFlushActivity --> 1921 <string name="media_codec_flush">Video codec flushing in Tunnel Mode</string> 1922 1923 <!-- Strings for VolumeLevelChangesActivity --> 1924 <string name="volume_level_changes">Volume level changes</string> 1925 <string name="volume_level_changes_title">This test is for verifying that the Volume level 1926 changes are reflected when playback occurs with and without tunnel mode playback for 1927 PCM audio.</string> 1928 <string name="increase_volume_level"> Increase the volume until you can clearly recognize the 1929 audio, and then press OK button.</string> 1930 <string name="ok_button_volume_level">OK</string> 1931 <string name="decrease_volume_level"> Decrease the volume until you can no longer recognize the 1932 audio, and then press OK button.</string> 1933 <string name="yes_button_volume_level">Yes</string> 1934 <string name="no_button_volume_level">No</string> 1935 <string name="is_same_volume"> "Is the volume still the same as what you had set?"</string> 1936 <string name="volume_level_changes_failure_tunnel_to_non_tunnel"> 1937 "The volume change was not maintained when switching from tunnel mode to non-tunnel mode." 1938 </string> 1939 <string name="volume_level_changes_failure_non_tunnel_to_tunnel"> 1940 "The volume change was not maintained when switching from non-tunnel mode to tunnel mode." 1941 </string> 1942 1943 <!-- Strings for the Camera Bokeh mode test activity --> 1944 <string name="camera_bokeh_test">Camera Bokeh</string> 1945 <string name="camera_bokeh_test_info"> 1946 This test checks camera bokeh mode functionality. It enumerates supported bokeh modes, and 1947 makes sure each non-OFF bokeh mode works correctly. For optimal and consistent results, 1948 please make sure the camera device is pointing to a well-lit scene with a human face in 1949 the center at least 1 meter away, and the rest of the scene is further away in the 1950 background. 1951 </string> 1952 <string name="camera_bokeh_no_support"> 1953 None of the camera devices support bokeh modes. Please click the Test Passed button. 1954 </string> 1955 1956 <!-- Strings for TestListActivity --> 1957 <string name="wifi_test">Wi-Fi Test</string> 1958 <string name="wifi_test_info"> 1959 The Wi-Fi tests requires an open or PSK access point in the environment along with the DUT. 1960 \nPlease perform a network settings reset between each test to reset platform\'s internal state which 1961 might interfere with the test flow.\nNavigate to \"Settings -> System -> Reset Options -> Reset Bluetooth 1962 & Wi-Fi\" to perform a network settings reset. 1963 </string> 1964 <string name="wifi_location_not_enabled">Wi-Fi / Location Mode is not enabled</string> 1965 <string name="wifi_location_not_enabled_message">These tests require Wi-Fi and Location Mode to be enabled. 1966 Click the button below to go to system settings and enable Wi-Fi and Location Mode.</string> 1967 <string name="wifi_settings">Wi-Fi Settings</string> 1968 <string name="location_settings">Location Settings</string> 1969 <string name="wifi_setup_error">Test failed with set up error.</string> 1970 <string name="wifi_unexpected_error">Test failed with unexpected error. Check logcat.</string> 1971 1972 <string name="wifi_ssid_label">SSID for network</string> 1973 <string name="wifi_psk_label">Passphrase for network (leave empty for open network)</string> 1974 <string name="wifi_start_test_label">Start test</string> 1975 1976 <string name="wifi_status_need_psk">Need a psk network for this test.</string> 1977 <string name="wifi_status_initiating_scan">Initiating scan.</string> 1978 <string name="wifi_status_scan_failure">Unable to initiate scan or find matching network in scan results.</string> 1979 <string name="wifi_status_connected_to_other_network">Connected to some other network on the device. Please ensure that there is no saved networks on the device.</string> 1980 <string name="wifi_status_initiating_network_request">Initiating network request.</string> 1981 <string name="wifi_status_network_wait_for_available">Waiting for network connection. Please click the network in the dialog that pops up for approving the request.</string> 1982 <string name="wifi_status_network_available">"Connected to network."</string> 1983 <string name="wifi_status_network_available_error">Connected to network unexpectedly.</string> 1984 <string name="wifi_status_network_wait_for_unavailable">"Ensuring device does not connect to any network. You should see an empty dialog that pops up for approving the request."</string> 1985 <string name="wifi_status_network_wait_for_unavailable_invalid_credential">"Ensuring device does not connect to the network. Please click the network in the dialog that pops up for approving the request."</string> 1986 <string name="wifi_status_network_unavailable">"Did not connect to any network."</string> 1987 <string name="wifi_status_network_wait_for_lost">Ensuring device does not disconnect from the network until the request is released.</string> 1988 <string name="wifi_status_network_lost">Disconnected from the network.</string> 1989 <string name="wifi_status_network_cb_timeout">Network callback timed out.</string> 1990 1991 <string name="wifi_status_suggestion_add">Adding suggestions to the device.</string> 1992 <string name="wifi_status_suggestion_add_failure">Failed to add suggestions.</string> 1993 <string name="wifi_status_suggestion_get_failure">Failed to get suggestions.</string> 1994 <string name="wifi_status_suggestion_remove">Removing suggestions from the device.</string> 1995 <string name="wifi_status_suggestion_remove_failure">Failed to remove suggestions.</string> 1996 <string name="wifi_status_suggestion_wait_for_connect">Waiting for network connection.</string> 1997 <string name="wifi_status_suggestion_ensure_no_connect">Ensuring no network connection.</string> 1998 <string name="wifi_status_suggestion_connect">Connected to the network.</string> 1999 <string name="wifi_status_suggestion_not_connected">Did not connect to the network.</string> 2000 <string name="wifi_status_suggestion_wait_for_post_connect_bcast">Waiting for post connection broadcast.</string> 2001 <string name="wifi_status_suggestion_post_connect_bcast">Received post connection broadcast.</string> 2002 <string name="wifi_status_suggestion_post_connect_bcast_failure">Failed to receive post connection broadcast.</string> 2003 <string name="wifi_status_suggestion_wait_for_connection_status">Waiting for connection status.</string> 2004 <string name="wifi_status_suggestion_connection_status">Received connection status.</string> 2005 <string name="wifi_status_suggestion_connection_status_failure">Failed to receive connection status.</string> 2006 <string name="wifi_status_suggestion_wait_for_disconnect">Ensuring device does disconnect from the network after removing suggestions.</string> 2007 <string name="wifi_status_suggestion_metered_change">Marking the network metered.</string> 2008 <string name="wifi_status_suggestion_metered_check_failed">Network meteredness check failed.</string> 2009 <string name="wifi_status_suggestion_metered_changed">Network marked metered successfully.</string> 2010 <string name="wifi_status_suggestion_capabilities_not_changed">Network capabilities did not change.</string> 2011 <string name="wifi_status_suggestion_not_disconnected">Did not disconnect from the network.</string> 2012 <string name="wifi_status_suggestion_disconnected">Disconnected from the network.</string> 2013 <string name="wifi_status_suggestion_add_user_approval_status_listener_failure">Failed to add user approval status listener</string> 2014 <string name="wifi_status_suggestion_wait_for_user_approval">Waiting for user approval. Please click \"Allow\" in the dialog that pops up for approving the app</string> 2015 <string name="wifi_status_suggestion_user_approval_status_failure">Failed to receive user approval status change</string> 2016 <string name="wifi_status_suggestion_user_approve_failure">Failed to get user approval</string> 2017 2018 <string name="wifi_status_test_success">Test completed successfully!</string> 2019 <string name="wifi_status_test_failed">Test failed!</string> 2020 2021 <string name="wifi_test_network_request">Network Request tests</string> 2022 <string name="wifi_test_network_request_specific">Network Request with a specific SSID and BSSID.</string> 2023 <string name="wifi_test_network_request_specific_info">Tests whether the API can be used to a connect to network with a specific SSID and BSSID specified in the request.</string> 2024 <string name="wifi_test_network_request_pattern">Network Request with a SSID and BSSID pattern.</string> 2025 <string name="wifi_test_network_request_pattern_info">Tests whether the API can be used to a connect to network with a SSID and BSSID pattern specified in the request.</string> 2026 <string name="wifi_test_network_request_unavailable">Network Request with a specific network that is unavailable.</string> 2027 <string name="wifi_test_network_request_unavailable_info">Tests that the API fails to connect when an unavailable network is specified in the request.</string> 2028 <string name="wifi_test_network_request_invalid_credential">Network Request with a specific network with wrong credential.</string> 2029 <string name="wifi_test_network_request_invalid_credential_info">Tests that the API fails to connect when a network with wrong credential is specified in the request.</string> 2030 2031 <string name="wifi_test_network_suggestion">Network Suggestion tests</string> 2032 <string name="wifi_test_network_suggestion_ssid">Network suggestion with SSID.</string> 2033 <string name="wifi_test_network_suggestion_ssid_info">Tests whether the API can be used to suggest a network with SSID to the device and the device connects to it.</string> 2034 <string name="wifi_test_network_suggestion_ssid_bssid">Network suggestion with SSID and BSSID.</string> 2035 <string name="wifi_test_network_suggestion_ssid_bssid_info">Tests whether the API can be used to suggest a network with SSID and specific BSSID to the device and the device connects to it.</string> 2036 <string name="wifi_test_network_suggestion_ssid_post_connect">Network suggestion with SSID and post connection broadcast.</string> 2037 <string name="wifi_test_network_suggestion_ssid_post_connect_info">Tests whether the API can be used to suggest a network with SSID to the device and the device connects to it and sends the post connect broadcast back to the app.</string> 2038 <string name="wifi_test_network_suggestion_connection_failure">Network suggestion connection failure.</string> 2039 <string name="wifi_test_network_suggestion_connection_failure_info">Tests whether the SuggestionConnectionStatusListener API can be used to listen to connection failures for suggested networks.</string> 2040 <string name="wifi_test_network_suggestion_modification_in_place">Network suggestion modification in place.</string> 2041 <string name="wifi_test_network_suggestion_modification_in_place_info">Tests whether the suggested network params can be modified in place when connected to it.</string> 2042 2043 <!-- Strings for P2pTestActivity --> 2044 <string name="p2p_test">Wi-Fi Direct Test</string> 2045 <string name="p2p_test_info"> 2046 The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange 2047 messages. One device must be the candidate device running the software build to 2048 be tested, while the other device must be an implementation already known to be 2049 compatible.\n\nOne device should start the requester test, and the other should 2050 start the responder test. Your device must pass both requester and responder 2051 tests. 2052 </string> 2053 <string name="p2p_group_formation">Group Formation</string> 2054 <string name="p2p_join">Group Join</string> 2055 <string name="p2p_service_discovery">Service Discovery</string> 2056 2057 <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string> 2058 <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string> 2059 <string name="p2p_group_owner_test">Group Owner Test</string> 2060 <string name="p2p_join_with_config">Group Join with Config</string> 2061 <string name="p2p_join_with_config_2g_band">Group Join with Config 2G Band</string> 2062 <string name="p2p_join_with_config_fixed_frequency"> 2063 Group Join with Config Fixed Frequency</string> 2064 <string name="p2p_group_owner_with_config_test">Group Owner With Config Test</string> 2065 <string name="p2p_group_owner_with_config_2g_band_test"> 2066 Group Owner With Config 2G Band Test</string> 2067 <string name="p2p_group_owner_with_config_fixed_frequency_test"> 2068 Group Owner With Config Fixed Frequency Test</string> 2069 <string name="p2p_group_client_test">Group Client Test</string> 2070 <string name="p2p_group_client_with_config_test">Group Client With Config Test</string> 2071 <string name="p2p_group_client_with_config_2g_band_test"> 2072 Group Client With Config 2G Band Test</string> 2073 <string name="p2p_group_client_with_config_fixed_frequency_test"> 2074 Group Client With Config Fixed Frequency Test</string> 2075 <string name="p2p_service_discovery_responder_test"> 2076 Service Discovery Responder Test</string> 2077 <string name="p2p_service_discovery_requester_test"> 2078 Service Discovery Requester Test</string> 2079 2080 <string name="p2p_go_neg_responder">GO Negotiation Responder</string> 2081 <string name="p2p_go_neg_requester">GO Negotiation Requester</string> 2082 <string name="p2p_accept_client">Group Owner</string> 2083 <string name="p2p_join_go">Group Client</string> 2084 <string name="p2p_service_discovery_responder">Service Discovery Responder</string> 2085 <string name="p2p_service_discovery_requester">Service Discovery Requester</string> 2086 2087 <string name="p2p_go_neg_responder_info"> 2088 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2089 Wi-Fi settings and forget all remembered networks. Then start the \"GO Negotiation 2090 Requester Test\" on the other device and follow 2091 the instructions.</string> 2092 <string name="p2p_accept_client_info"> 2093 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2094 Wi-Fi settings and forget all remembered networks. Then start the \"Group Client Test\" on 2095 the other device and follow 2096 the instructions.</string> 2097 <string name="p2p_service_discovery_responder_info"> 2098 Start the \"Service Discovery Requester Test\" on the other device and follow 2099 the instructions.</string> 2100 2101 <string name="p2p_go_neg_requester_info"> 2102 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2103 Wi-Fi settings and forget all remembered networks. Then start the \"GO Negotiation 2104 Responder Test\" on the other device. 2105 Then run each test individually by clicking on its name.</string> 2106 <string name="p2p_join_go_info"> 2107 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2108 Wi-Fi settings and forget all remembered networks. Then start the \"Group Owner Test\" on 2109 the other device. 2110 Then run each test individually by clicking on its name.</string> 2111 <string name="p2p_service_discovery_requester_info"> 2112 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2113 Wi-Fi settings and forget all remembered networks. Then start the \"Service Discovery 2114 Responder Test\" on the other device. 2115 Then run each test individually by clicking on its name.</string> 2116 2117 <string name="p2p_not_enabled">Wi-Fi is not enabled</string> 2118 <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled. 2119 Click the button below to go to system settings and enable Wi-Fi.</string> 2120 <string name="p2p_settings">Wi-Fi Direct Settings</string> 2121 2122 <string name="p2p_result_success">Test passed successfully.</string> 2123 2124 <string name="p2p_go_neg_responder_ready"> 2125 The go negotiation responder is now ready to start. 2126 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2127 Wi-Fi settings and forget all remembered networks. Then start the \"GO Negotiation 2128 Requester Test\" on the other device. 2129 Keep the screen here until all tests on the other device are 2130 finished.</string> 2131 <string name="p2p_go_ready"> 2132 The group owner is now ready to start. 2133 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2134 Wi-Fi settings and forget all remembered networks. Then start the \"Join Group Test\" on 2135 the other device. 2136 Keep the screen here until all tests on the other device are 2137 finished.</string> 2138 <string name="p2p_service_responder_ready"> 2139 The service responder is now ready to start. 2140 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2141 Wi-Fi settings and forget all remembered networks. Then start the \"Service Discovery 2142 Requester Test\" on the other device. 2143 Keep the screen here until all tests on the other device are 2144 finished.</string> 2145 2146 <string name="p2p_setup_error"> 2147 Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string> 2148 <string name="p2p_unexpected_error"> 2149 Test failed.\n\nUnexpected error. Check logcat.</string> 2150 <string name="p2p_add_local_service_error"> 2151 Test failed.\n\nFailed to add local service.</string> 2152 <string name="p2p_add_service_request_error"> 2153 Test failed.\n\nFailed to add service request.</string> 2154 <string name="p2p_remove_service_request_error"> 2155 Test failed.\n\nFailed to remove service request.</string> 2156 <string name="p2p_clear_service_requests_error"> 2157 Test failed.\n\nFailed to clear service requests.</string> 2158 <string name="p2p_connect_error"> 2159 Test failed.\n\nFailed to start a p2p connection to the target device.</string> 2160 <string name="p2p_remove_group_error"> 2161 Test failed.\n\nFailed to remove a p2p group.</string> 2162 <string name="p2p_discover_peers_error"> 2163 Test failed.\n\nFailed to discover peers.</string> 2164 <string name="p2p_discover_services_error"> 2165 Test failed.\n\nFailed to discover services.</string> 2166 <string name="p2p_ceate_group_error"> 2167 Test failed.\n\nFailed to start up group owner.</string> 2168 <string name="p2p_no_service_requests_error"> 2169 Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string> 2170 <string name="p2p_receive_invalid_response_error"> 2171 Test failed.\n\nReceived an invalid message or could not receive 2172 the expected message.\n\n</string> 2173 <string name="p2p_target_not_found_error">Test failed.\n\n 2174 The target responder device was NOT found. Start up the responder 2175 test on the other device, then run the test again.</string> 2176 <string name="p2p_target_invalid_role_error">Test failed.\n\n 2177 The target responder must be p2p device. However, the target responder 2178 device was group owner. Check the test case on the other device.</string> 2179 <string name="p2p_target_invalid_role_error2">Test failed.\n\n 2180 The target responder must be group owner. However, the target responder 2181 device was p2p device. Check the test case on the other device.</string> 2182 <string name="p2p_connection_error"> 2183 Test failed.\n\nFailed to establish a p2p connection.</string> 2184 <string name="p2p_detect_disconnection_error"> 2185 Test failed.\n\nFailed to detect client disconnection.</string> 2186 <string name="p2p_disconnect_error"> 2187 Test failed.\n\nFailed to disconnect a p2p connection.</string> 2188 2189 <string name="p2p_search_target">Search Target</string> 2190 <string name="p2p_searching_target">Searching for target device ...</string> 2191 <string name="p2p_checking_serv_capab">Checking the service discovery 2192 capability ...</string> 2193 <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n 2194 Click the \"OK\" button on the other device to accept the connection 2195 request from this device.</string> 2196 <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n 2197 Enter the pin number on the other device.</string> 2198 <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to 2199 connect ...</string> 2200 <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer 2201 to disconnect ...</string> 2202 2203 <!-- Strings for TestListActivity --> 2204 <string name="aware_test">Wi-Fi Aware Test</string> 2205 <string name="aware_test_info"> 2206 The Wi-Fi Aware tests require two devices with Wi-Fi enabled. One device must 2207 be the candidate device running the software build to be tested, while the other 2208 device must be an implementation already known to be compatible.\n\nThere are 2209 tests for Publisher and Subscriber, Responder and Initiator. One device should 2210 start in a role, and the other should start in the complementary 2211 role. Your device must pass the tests in all roles. 2212 </string> 2213 <string name="aware_not_enabled">Wi-Fi / Location Mode is not enabled</string> 2214 <string name="aware_not_enabled_message">These tests require Wi-Fi and Location Mode to be enabled. 2215 Click the button below to go to system settings and enable Wi-Fi and Location Mode.</string> 2216 <string name="aware_settings">Wi-Fi Settings</string> 2217 <string name="aware_setup_error"> 2218 Test failed.\n\nSet up error. Check whether Wi-Fi is enabled.</string> 2219 <string name="aware_unexpected_error"> 2220 Test failed.\n\nUnexpected error. Check logcat.</string> 2221 2222 <string name="aware_dp_ib_open_unsolicited">Data Path: Open: Unsolicited/Passive</string> 2223 <string name="aware_dp_ib_passphrase_unsolicited">Data Path: Passphrase: Unsolicited/Passive</string> 2224 <string name="aware_dp_ib_pmk_unsolicited">Data Path: PMK: Unsolicited/Passive</string> 2225 <string name="aware_dp_ib_open_solicited">Data Path: Open: Solicited/Active</string> 2226 <string name="aware_dp_ib_passphrase_solicited">Data Path: Passphrase: Solicited/Active</string> 2227 <string name="aware_dp_ib_pmk_solicited">Data Path: PMK: Solicited/Active</string> 2228 <string name="aware_dp_ib_open_unsolicited_accept_any">Data Path: Open: Unsolicited/Passive: accept any peer</string> 2229 <string name="aware_dp_ib_passphrase_unsolicited_accept_any">Data Path: Passphrase: Unsolicited/Passive: accept any peer</string> 2230 <string name="aware_dp_ib_pmk_unsolicited_accept_any">Data Path: PMK: Unsolicited/Passive: accept any peer</string> 2231 <string name="aware_dp_ib_open_solicited_accept_any">Data Path: Open: Solicited/Active: accept any peer</string> 2232 <string name="aware_dp_ib_passphrase_solicited_accept_any">Data Path: Passphrase: Solicited/Active: accept any peer</string> 2233 <string name="aware_dp_ib_pmk_solicited_accept_any">Data Path: PMK: Solicited/Active: accept any peer</string> 2234 <string name="aware_dp_ib_force_channel_setup">Data Path: force channel setup</string> 2235 <string name="aware_discovery_ranging">Discovery with Ranging</string> 2236 <string name="aware_publish">Publish</string> 2237 <string name="aware_subscribe">Subscribe</string> 2238 2239 <string name="aware_dp_oob_open">Data Path (OOB): Open</string> 2240 <string name="aware_dp_oob_passphrase">Data Path (OOB): Passphrase</string> 2241 <string name="aware_responder">Responder</string> 2242 <string name="aware_initiator">Initiator</string> 2243 2244 <string name="aware_status_attached">Attached ...</string> 2245 <string name="aware_status_attach_fail">Attach failure!</string> 2246 <string name="aware_status_attach_timeout">Attach failure - timed out!</string> 2247 <string name="aware_status_identity">Discovery (Identity) MAC address: %1$s ...</string> 2248 <string name="aware_status_identity_fail">Identity listener failure - timed out!</string> 2249 <string name="aware_status_subscribe_started">Subscribe discovery session started ...</string> 2250 <string name="aware_status_subscribe_failed">Subscribe failure!</string> 2251 <string name="aware_status_subscribe_timeout">Subscribe failure - timed out!</string> 2252 <string name="aware_status_subscribe_null_session">Subscribe failure - null session!</string> 2253 <string name="aware_status_publish_started">Publish discovery session started ...</string> 2254 <string name="aware_status_publish_failed">Publish failure!</string> 2255 <string name="aware_status_publish_timeout">Publish failure - timed out!</string> 2256 <string name="aware_status_publish_null_session">Publish failure - null session!</string> 2257 <string name="aware_status_discovery">Service discovered ...</string> 2258 <string name="aware_status_discovery_with_info">Service discovered ... peer MAC : %1$s</string> 2259 <string name="aware_status_discovery_timeout">Service discovery failure - timed out!</string> 2260 <string name="aware_status_discovery_fail">Service discovery failure - parameter mismatch!</string> 2261 <string name="aware_status_send_success">Sent message successfully ...</string> 2262 <string name="aware_status_send_failed">Send message failure!</string> 2263 <string name="aware_status_send_timeout">Send message failure - timed out!</string> 2264 <string name="aware_status_send_fail_parameter">Send message failure - mismatched ids!</string> 2265 <string name="aware_status_received">Received message ...</string> 2266 <string name="aware_status_starting_rtt">Starting RTT operations ...</string> 2267 <string name="aware_status_waiting_for_peer_rtt">Pausing to let other device perform RTT ...</string> 2268 <string name="aware_status_received_peer_rtt_done">Other device done with RTT ...</string> 2269 <string name="aware_status_received_mac">Received peer MAC address: %1$s ...</string> 2270 <string name="aware_status_receive_timeout">Receive message failure - timed out!</string> 2271 <string name="aware_status_receive_failure">Receive message failure - didn\'t receive expected message!</string> 2272 <string name="aware_status_network_requested">Network requested ...</string> 2273 <string name="aware_status_network_success">Network formed ...</string> 2274 <string name="aware_status_network_failed">Network request failure - timed out!</string> 2275 <string name="aware_status_network_failed_leak">Failure: Network request success - but leaked information!</string> 2276 <string name="aware_status_sleeping_wait_for_responder">Pausing to let Responder time to set up ...</string> 2277 <string name="aware_status_ranging_peer_failure">Ranging to PeerHandle failure: %1$d failures of %2$d attempts!</string> 2278 <string name="aware_status_ranging_mac_failure">Ranging to MAC address failure: %1$d failures of %2$d attempts!</string> 2279 <string name="aware_status_ranging_peer_success">Ranging to PeerHandle success: %1$d successes of %2$d attempts!</string> 2280 <string name="aware_status_ranging_mac_success">Ranging to MAC address success: %1$d successes of %2$d attempts!</string> 2281 <string name="aware_status_lifecycle_failed">Discovery lifecycle FAILURE!</string> 2282 <string name="aware_status_lifecycle_ok">Discovery lifecycle validated!</string> 2283 2284 <string name="aware_status_socket_failure">Failure on socket connection setup!</string> 2285 <string name="aware_status_socket_server_socket_started">ServerSocket started on port %1$d!</string> 2286 <string name="aware_status_socket_server_info_rx">Peer server info: IPv6=%1$s @ port=%2$d!</string> 2287 <string name="aware_status_socket_server_message_from_peer">Message from peer: \'%1$s\'</string> 2288 2289 <string name="aware_data_path_open_unsolicited_publish">Data Path: Open: Unsolicited Publish</string> 2290 <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> 2291 <string name="aware_data_path_open_passive_subscribe">Data Path: Open: Passive Subscribe</string> 2292 2293 <string name="aware_data_path_passphrase_unsolicited_publish">Data Path: Passphrase: Unsolicited Publish</string> 2294 <string name="aware_data_path_passphrase_unsolicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: Passphrase: Unsolicited/Passive\' / \'Subscribe\' test.</string> 2295 <string name="aware_data_path_passphrase_passive_subscribe">Data Path: Passphrase: Passive Subscribe</string> 2296 2297 <string name="aware_data_path_pmk_unsolicited_publish">Data Path: PMK: Unsolicited Publish</string> 2298 <string name="aware_data_path_pmk_unsolicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: PMK: Unsolicited/Passive\' / \'Subscribe\' test.</string> 2299 <string name="aware_data_path_pmk_passive_subscribe">Data Path: PMK: Passive Subscribe</string> 2300 2301 <string name="aware_data_path_open_solicited_publish">Data Path: Open: Solicited Publish</string> 2302 <string name="aware_data_path_open_solicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: Open: Solicited/Active\' / \'Subscribe\' test.</string> 2303 <string name="aware_data_path_open_active_subscribe">Data Path: Open: Active Subscribe</string> 2304 2305 <string name="aware_data_path_passphrase_solicited_publish">Data Path: Passphrase: Solicited Publish</string> 2306 <string name="aware_data_path_passphrase_solicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: Passphrase: Solicited/Active\' / \'Subscribe\' test.</string> 2307 <string name="aware_data_path_passphrase_active_subscribe">Data Path: Passphrase: Active Subscribe</string> 2308 2309 <string name="aware_data_path_pmk_solicited_publish">Data Path: PMK: Solicited Publish</string> 2310 <string name="aware_data_path_pmk_solicited_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: PMK: Solicited/Active\' / \'Subscribe\' test.</string> 2311 <string name="aware_data_path_pmk_active_subscribe">Data Path: PMK: Active Subscribe</string> 2312 2313 <string name="aware_data_path_oob_open_responder">Data Path (OOB): Open: Responder</string> 2314 <string name="aware_data_path_oob_open_responder_info">The responder is now ready.\n\nOn the other device: start the \'Data Path (OOB): Open\' / \'Initiator\' test.</string> 2315 <string name="aware_data_path_oob_open_initiator">Data Path (OOB): Open: Initiator</string> 2316 2317 <string name="aware_data_path_oob_passphrase_responder">Data Path (OOB): Passphrase: Responder</string> 2318 <string name="aware_data_path_oob_passphrase_responder_info">The responder is now ready.\n\nOn the other device: start the \'Data Path (OOB): Passphrase\' / \'Initiator\' test.</string> 2319 <string name="aware_data_path_oob_passphrase_initiator">Data Path (OOB): Passphrase: Initiator</string> 2320 2321 <string name="aware_discovery_ranging_publish">Discovery with Ranging: Publish</string> 2322 <string name="aware_discovery_ranging_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Discovery with Ranging\' / \'Subscribe\' test.</string> 2323 <string name="aware_discovery_ranging_subscribe">Discovery with Ranging: Subscribe</string> 2324 2325 <string name="aware_data_path_force_channel_setup_publish">Data Path: force channel setup Publish</string> 2326 <string name="aware_data_path_force_channel_setup_publish_info">The publisher is now ready.\n\nOn the other device: start the \'Data Path: force channel setup\' / \'Subscribe\' test.</string> 2327 <string name="aware_data_path_force_channel_setup_subscribe">Data Path: force channel setup Subscribe</string> 2328 2329 <string name="camera_fov_calibration">Camera FOV Calibration</string> 2330 <string name="camera_fov_calibration_done">Done</string> 2331 <string name="camera_fov_general_settings">General settings</string> 2332 <string name="camera_fov_label_options">Settings</string> 2333 <string name="camera_fov_tap_to_take_photo">Tap to calibrate</string> 2334 <string name="camera_fov_marker_distance">Marker distance (in cm)</string> 2335 <string name="camera_fov_marker_distance_description">The distance in centimeters between 2336 the solid lines on the target pattern.</string> 2337 <string name="camera_fov_target_distance">Target distance (in cm)</string> 2338 <string name="camera_fov_target_distance_description">The distance in centimeters from the 2339 device to the target pattern.</string> 2340 <string name="camera_fov_settings_button_text">Setup</string> 2341 <string name="camera_fov_change_preview_sizes_button_text">Preview Sizes</string> 2342 <string name="camera_fov_choose_preview_size_for_camera">Choose preview size for camera %1$s</string> 2343 <string name="camera_fov_displayed_fov_label">Displayed FOV : </string> 2344 <string name="camera_fov_reported_fov_label">Reported FOV : </string> 2345 <string name="camera_fov_reported_fov_problem">Reported FOV problem</string> 2346 <string name="camera_fov_reported_fov_problem_message">The reported FOV before takePicture() is 2347 different from when onPictureTaken() is called.\nAs picture size has not been changed, the 2348 reported FOV should be identical at both times.\n\nFOV before/after: %1$f / %2$f</string> 2349 2350 <string name="camera_fov_panorama_wallpaper_title">Photo Sphere Live Wallpaper</string> 2351 <string name="camera_fov_panorama_wallpaper_description">This live wallapper displays photo 2352 spheres.</string> 2353 <string name="camera_fov_select_panorama">Select panorama</string> 2354 <string name="camera_fov_select_panorama_description">Select a panorama to display in the 2355 live wallpaper.</string> 2356 <string name="camera_fov_reset_panorama">Reset panorama</string> 2357 <string name="camera_fov_reset_panorama_description">Resets the panorama to show the demo 2358 file.</string> 2359 <string name="camera_fov_enable_compass_mode">Enable compass mode</string> 2360 <string name="camera_fov_enable_compass_mode_description">If enabled, the panorama orients 2361 itself according to the current rotation of the device.</string> 2362 2363 <string name="test_category_notifications">Notifications</string> 2364 <string name="test_category_tiles">Tiles</string> 2365 <string name="package_priority_test">Notification Package Priority Test</string> 2366 <string name="package_priority_info">This test checks that the NotificationManagerService respects 2367 user preferences about relative package priorities. 2368 </string> 2369 <string name="package_priority_bot">Verifying that the CTS Robot helper package is installed.</string> 2370 <string name="package_priority_high">Find \"%s\" in the \"Notifications\" settings panel, and allow it to Override Do Not Disturb.</string> 2371 <string name="package_priority_default">Find \"%s\" in the \"Notifications\" settings panel, and disallow it to Override Do Not Disturb.</string> 2372 <string name="package_priority_user_order">Check that ranker respects user priorities.</string> 2373 2374 <string name="test_category_vibrations">Vibrations</string> 2375 <string name="test_title_has_vibrator">Has Vibrator Test</string> 2376 2377 <string name="shortcut_reset_test">Shortcut Reset Rate-limiting Test</string> 2378 <string name="shortcut_reset_info">This test checks that when an inline-reply happens, ShortcutManager\'s rate-limiting 2379 is reset. Please grant access to show notification when prompted.</string> 2380 <string name="shortcut_reset_bot">Verifying that the CTS Robot helper package is installed.</string> 2381 <string name="shortcut_reset_start">Showing the notification.</string> 2382 <string name="shortcut_reset_prompt_inline_reply">Open the notification shade, 2383 find the \"Shortcut Reset Rate-limiting Test\" notification, type something in the inline-reply field and 2384 press the send button.</string> 2385 <string name="shortcut_reset_check_result">Check ShortcutManager rate-limit has been reset.</string> 2386 2387 <string name="ringer_mode_tests">Ringer Mode Tests</string> 2388 <string name="ringer_mode_info">This test checks that Audio manager functionality that requires 2389 particular ringer mode states works properly. 2390 </string> 2391 <string name="ringer_mode_pass_test">These tests are handled by CTS.</string> 2392 <string name="test_sound_effects">Test Tap & click sounds</string> 2393 <string name="test_vibrate_notification">Test vibrate notification</string> 2394 <string name="test_vibrate_ringer">Test vibrate ringer</string> 2395 <string name="test_access_ringer_mode">Test access ringer mode</string> 2396 <string name="test_ringer_mode_policy_access">Test ringer mode policy access</string> 2397 <string name="test_volume_dnd_affected_stream">Test volume change</string> 2398 <string name="test_mute_dnd_affected_streams">Test mute streams</string> 2399 <string name="test_ringer_manager">Test RingtoneManager</string> 2400 <string name="enable_sound_effects">Please enable Tap & click sounds in Sound settings.</string> 2401 <string name="attention_ready">I\'m done</string> 2402 <string name="attention_filter_any">Please enable \"Do not disturb\" by tapping the Quick Settings tile.</string> 2403 <string name="attention_filter_all">Please disable \"Do not disturb\" by tapping the Quick Settings tile.</string> 2404 <string name="attention_filter_priority">Please enable \"Do not disturb\" by tapping the Quick 2405 Settings tile. Then, long press the same tile and customize the setting to allow messages 2406 from starred contacts only.</string> 2407 <string name="attention_filter_priority_mimic_alarms_only">Please enable Priority-Only \"Do not disturb\" 2408 by tapping the Quick Settings tile. Then, long press the same tile and customize the setting to allow sounds 2409 from Alarms and Media (if applicable) only.</string> 2410 <string name="attention_create_contacts">Create contacts for notification annotations.</string> 2411 <string name="attention_delete_contacts">Delete test contacts.</string> 2412 <string name="attention_default_order">Check that ranker defaults to time order.</string> 2413 <string name="attention_priority_order">Check that ranker respects developers priorities.</string> 2414 <string name="attention_ambient_bit">Check that the ambient bit is set appropriately.</string> 2415 <string name="attention_lookup_order">Check that ranker respects Lookup URIs for contacts.</string> 2416 <string name="attention_email_order">Check that ranker respects mailto URIs for contacts.</string> 2417 <string name="attention_phone_order">Check that ranker respects telephone URIs for contacts.</string> 2418 <string name="attention_interruption_order">Check that ranker temporarily boosts interruptions. 2419 This test takes 30 seconds to complete.</string> 2420 <string name="attention_none_are_filtered_messages">Check that \"All\" mode doesn\'t filter any notifications (messages).</string> 2421 <string name="attention_none_are_filtered_diff_categories">Check that \"All\" mode doesn\'t filter any notifications (event, reminder, alarm).</string> 2422 <string name="attention_some_are_filtered_messages">Check that \"Priority\" mode doesn\'t filter priority notifications (messages from starred contacts).</string> 2423 <string name="attention_some_are_filtered_alarms">Check that \"Priority\" mode doesn\'t filter priority notifications (alarms).</string> 2424 <string name="attention_some_are_filtered_media_system_other">Check that \"Priority\" mode doesn\'t filter priority notifications (media, system, other).</string> 2425 <string name="attention_all_are_filtered">Check that \"None\" mode filters all notifications.</string> 2426 <string name="attention_cannot_disallow_alarms_or_media">Check that apps targeted with Pre-P SDK can\'t disallow alarms or media from bypassing DND.</string> 2427 <string name="nls_test">Notification Listener Test</string> 2428 <string name="nas_test">Notification Assistant Test</string> 2429 <string name="nls_service_name">Notification Listener for CTS Verifier</string> 2430 <string name="nls_info">This test checks that a NotificationListenerService can be enabled 2431 and disabled, and that once enabled the service is able to receive notifications and 2432 dismiss them. 2433 </string> 2434 <string name="nas_service_name">Notification Assistant for CTS Verifier</string> 2435 <string name="nas_info">This test checks that a NotificationAssistantService can be enabled 2436 and disabled, and that once enabled the service is able to receive notifications and 2437 dismiss them. 2438 </string> 2439 <string name="nls_anr">This test checks that notifications are not sent with content that is 2440 too long. If this test causes the test app to ANR, the test has failed. 2441 </string> 2442 <string name="action_not_sent">SecureActionOnLockScreenTest</string> 2443 <string name="action_received">Action Sent - SecureActionOnLockScreenTest</string> 2444 <string name="action_test_title">Action</string> 2445 <string name="nls_visibility">Please change the lock screen setting to hide sensitive content 2446 on the lockscreen</string> 2447 <string name="nls_restore_visibility">Please change the lock screen setting to show all 2448 content on the lockscreen</string> 2449 <string name="add_screen_lock">Add a secure screen lock of any type.\nLet all notification content be shown.</string> 2450 <string name="set_global_visibility_public">Update notification settings to ensure that all notification content is shown.</string> 2451 <string name="set_global_visibility_private">Update notification settings to ensure that sensitive notification content is shown only when unlocked.</string> 2452 <string name="set_global_visibility_secret">Update notification settings to ensure that all notifications are hidden on the lock screen.</string> 2453 <string name="remove_screen_lock">Remove the added screen lock</string> 2454 <string name="secure_action_lockscreen">Lock the screen and find the SecureActionOnLockScreenTest 2455 notification. Tap on its action. Verify that the keyguard displays on tap, and that the 2456 notification text does not update until the passcode is entered. Ensure that the notification 2457 text does update once the device is unlocked.</string> 2458 <string name="nd_test">Notification Dismiss Test</string> 2459 <string name="nd_test_info">This test checks if Notifications can only be 2460 dismissed, when it is allowed.</string> 2461 <string name="nd_notif_title">NotifDismissTest</string> 2462 <string name="dismiss_notif_from_the_shade">Open the shade while the device is unlocked and find the NotifDismissTest notification.\n 2463 Swipe it to either side to dismiss it.\n 2464 Pass the test if it can be dismissed.</string> 2465 <string name="dismiss_notif_from_the_ls">Lock the screen and find the NotifDismissTest notification.\n 2466 Swipe it to either side to dismiss it.\n 2467 Pass the test if it can be dismissed from the lock screen.</string> 2468 <string name="non_dismissable_notif_from_the_ls">Lock the screen and find the NotifDismissTest notification.\n 2469 Try to dismiss it. Verify that it is non-dismissible.\n 2470 Fail the test if it could be dismissed from the lock screen.</string> 2471 <string name="fsi_test">Notification Full Screen Intent Test</string> 2472 <string name="fsi_test_info">This test checks the behavior of Notifications 2473 with Full Screen Intents.</string> 2474 <string name="fsi_lockscreen_without_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2475 After clicking, lock the screen and press the power button as quickly as possible to go to the lock screen.\n 2476 Wait for a heads up notification to appear first in the list with a pill button.\n 2477 Unlock screen to return to this page after seeing the notification or after 5 seconds.\n 2478 Fail the test if the notification does not appear as described. 2479 </string> 2480 <string name="fsi_lockscreen_with_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2481 After clicking, lock the screen and press the power button as quickly as possible to go to the lock screen.\n 2482 Wait for a page to automatically launch and display the message \"This page is a full screen intent.\".\n 2483 Unlock screen to return to this page after seeing the page or after 5 seconds.\n 2484 Fail the test if the page does not launch as described. 2485 </string> 2486 <string name="fsi_screen_off_without_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2487 After clicking, press the power button as quickly as possible to turn off the screen.\n 2488 Wait for a notification to appear on the screen with a pill button.\n 2489 Unlock screen to return to this page after seeing the notification or after 5 seconds.\n 2490 Fail the test if the notification does not appear as described. 2491 </string> 2492 <string name="fsi_screen_off_with_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2493 After clicking, press the power button as quickly as possible to turn off the screen.\n 2494 Wait for a page to automatically launch and display the message \"This page is a full screen intent.\".\n 2495 Unlock screen to return to this page after seeing the page or after 5 seconds.\n 2496 Fail the test if the page does not launch as described. 2497 </string> 2498 <string name="fsi_aod_with_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2499 After clicking, press the power button as quickly as possible to go to Always on Display.\n 2500 Wait for a page to automatically launch and display the message \"This page is a full screen intent.\".\n 2501 Unlock screen to return to this page after seeing the page or after 5 seconds.\n 2502 Fail the test if the page does not launch as described. 2503 </string> 2504 <string name="fsi_aod_without_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2505 After clicking, press the power button as quickly as possible to go to Always on Display.\n 2506 Wait for a notification to appear on the screen with a pill button.\n 2507 Unlock screen to return to this page after seeing the notification or after 5 seconds.\n 2508 Fail the test if the notification does not show as described. 2509 </string> 2510 <string name="fsi_turn_on_aod">Turn on Always on Display by toggling on \"Always show time and info\" in Lockscreen Settings.</string> 2511 <string name="fsi_turn_off_aod">Turn off Always on Display by toggling off \"Always show time and info\" in Lockscreen Settings.</string> 2512 <string name="fsi_notif_title">NotifFsiTest</string> 2513 <string name="fsi_mock_call_desc">This page is a full screen intent (e.g. a call).\n 2514 Pass the test if you see this page.\n 2515 To return to the test, use the back button or gesture and unlock the screen. 2516 </string> 2517 <string name="fsi_notif_content">Fsi Notif Content Fsi Notif Content Fsi Notif Content \n 2518 Fsi Notif Content Fsi Notif Content Fsi Notif Content</string> 2519 <string name="fsi_grant_permission">Please toggle on the full screen intents permission for CTSVerifier.</string> 2520 <string name="fsi_deny_permission">Please toggle off the full screen intents permission for CTSVerifier</string> 2521 <string name="fsi_sticky_hun">There should be a sticky Heads Up Notification on the screen.\n 2522 It would not be automatically cleared out.\n 2523 Fail the test if it doesn\'t show or disappears within 60s.</string> 2524 <string name="fsi_sticky_hun_60s">There should be a Heads Up Notification on the screen.\n 2525 It would show for 60s.\n 2526 Fail the test if it doesn\'t show or disappears within 60s.</string> 2527 <string name="np_start_channel_settings">Launch Channel Settings</string> 2528 <string name="np_start_security_settings">Launch Security Settings</string> 2529 <string name="np_start_notif_settings">Launch Notification Settings</string> 2530 <string name="np_start_lockscreen_settings">Launch Lock Screen Settings</string> 2531 <string name="np_when_locked_see_redacted">Lock the screen and find the NotifPrivacyTest notification.\n 2532 Pass the test if the notification content is REDACTED.</string> 2533 <string name="np_when_locked_see_private">Lock the screen and find the NotifPrivacyTest notification.\n 2534 Pass the test if the notification content is EXPOSED.</string> 2535 <string name="np_when_locked_hidden">Lock the screen and look for the NotifPrivacyTest notification.\n 2536 Fail the test if it can be found without unlocking the device.</string> 2537 <string name="np_start_occluding">Launch CallSimulator</string> 2538 <string name="np_occluding_instructions">Launch the CallSimulator and follow the instructions on that screen.</string> 2539 <string name="np_occluding_see_redacted">CallSimulator 2540 \n\n(Like a call, this screen will be visible even when the device is locked.) 2541 \n\nLock the screen, then come back here without unlocking. 2542 \nPull down the notification shade and find the NotifPrivacyTest notification. 2543 \nPass the test if the notification content is REDACTED. 2544 \n\nGo back when ready to Pass/Fail the step.</string> 2545 <string name="np_occluding_see_private">CallSimulator 2546 \n\n(Like a call, this screen will be visible even when the device is locked.) 2547 \n\nLock the screen, then come back here without unlocking. 2548 \nPull down the notification shade and find the NotifPrivacyTest notification. 2549 \nPass the test if the notification content is EXPOSED. 2550 \n\nGo back when ready to Pass/Fail the step.</string> 2551 <string name="np_occluding_hidden">CallSimulator 2552 \n\n(Like a call, this screen will be visible even when the device is locked.) 2553 \n\nLock the screen, then come back here without unlocking. 2554 \nPull down the notification shade and look for the NotifPrivacyTest notification. 2555 \nFail the test if it can be found without unlocking the device. 2556 \n\nGo back when ready to Pass/Fail the step.</string> 2557 <string name="np_public_version_text">NotifPrivacyTest: REDACTED</string> 2558 <string name="np_private_version_text">NotifPrivacyTest: EXPOSED</string> 2559 <string name="notif_privacy_test">Notification Privacy Test</string> 2560 <string name="notif_privacy_info">This test checks that Notification privacy is correctly 2561 handled on the insecure and secure lockscreen. 2562 </string> 2563 <string name="msg_extras_preserved">Check that Message extras Bundle was preserved.</string> 2564 <string name="conversation_section_ordering">Fully expand the notification display and verify 2565 that the \"Person A\" notification appears before the "\Non-Person Notification\". 2566 If this is not a 'handheld' device and does not support conversation notifications or does 2567 not group them together, press Pass.</string> 2568 <string name="hun_display">If this device supports heads-up notifications, 2569 verify that a notification just peeked on screen, displaying all of the following: small 2570 icon, large icon, notification title, notification text, and two action buttons. 2571 If this device does not support heads-up notifications, press Pass.</string> 2572 <string name="action">Action %1$d</string> 2573 <string name="no_test_items">No tests available for this device.</string> 2574 <string name="tile_service_name">Tile Service for CTS Verifier</string> 2575 <string name="tiles_test">Tile Service Test</string> 2576 <string name="tiles_info">This test checks that a Tile Service added by a third party 2577 application is not immediately added to the current Quick Settings tiles but can be added 2578 by the user. 2579 </string> 2580 <string name="tiles_adding_tile">Check that Tile Service is enabled</string> 2581 <string name="tiles_not_added">Open Quick Settings and check that the Tile Service for CTS 2582 Verifier is not visible in any page</string> 2583 <string name="tiles_in_customizer">Open Quick Settings and click the button to customize Quick 2584 Settings. Check that the Tile Service for CTS Verifier is available to be added</string> 2585 <string name="tiles_removing_tile">Check that Tile Service is disabled</string> 2586 <string name="tile_request_service_name">Request Tile Service</string> 2587 <string name="tile_request_helper_app_name">CtsTileServiceApp</string> 2588 <string name="tiles_request_test">Tile Service Request Test</string> 2589 <string name="tiles_request_info">This test checks that a request to add a TileService is 2590 shown correctly to the user and the correct answer is relayed to the app.</string> 2591 <string name="tiles_request_uninstall">This will verify that the helper app is not installed. 2592 If that is correct, the test will pass automatically. If the app is installed, press the button 2593 and you will be prompted for confirmation to uninstall the app.</string> 2594 <string name="tiles_request_install">You should have received a helper app apk with this CTS 2595 Verifier package. Its name is \"CtsTileServiceApp\". Install the test app, by running\n 2596 \"adb install /path/to/CtsTileServiceApp.apk\".\n 2597 Pass the test if the install was successful. Fail it otherwise. 2598 </string> 2599 <string name="tiles_request_install_verify">This will automatically verify that the helper app 2600 is correctly installed.</string> 2601 <string name="tiles_request_tile_not_present">Open Quick Settings and pass this test 2602 if there are no tiles named %1$s in any page.</string> 2603 <string name="tiles_request_dismissed">After pressing \"Start request\", a dialog will appear 2604 requesting to add a quick settings tile. When it appears, dismiss it by tapping outside of 2605 it, or going back.</string> 2606 <string name="tiles_request_correct_info">After pressing \"Start request\", a dialog will appear 2607 requesting to add a quick settings tile. When it appears, verify the following information 2608 in the dialog:\n 2609 1. The name of the app requesting to add the tile is %1$s.\n 2610 2. The label in the tile is %2$s.\n 2611After verifying, tap the option in the dialog to not add the tile.\n 2612When the buttons are enabled, pass this test if the information in the dialog was correct. 2613 </string> 2614 <string name="tiles_request_answer_yes">After pressing \"Start request\", a dialog will appear 2615 requesting to add a quick settings tile. When it appears, tap the option in the dialog to 2616 add the tile. 2617 </string> 2618 <string name="tiles_request_tile_present">Open Quick Settings and pass this test if a tile named 2619 %1$s is visible in some page. 2620 </string> 2621 <string name="tiles_request_check_tile_already_added">Checking tile already added response 2622 </string> 2623 <string name="vr_tests">VR Tests</string> 2624 <string name="test_category_vr">VR</string> 2625 <string name="vr_test_title">VR Listener Test</string> 2626 <string name="vr_service_name">VR Listener for CTS Verifier</string> 2627 <string name="vr_info">This test checks that a VrListenerService can be enabled and disabled, and 2628 and that it receives the correct lifecycle callbacks when entering and exiting VR mode. 2629 </string> 2630 <string name="vr_start_settings">Launch Settings</string> 2631 <string name="vr_start_vr_activity">Launch VR mode activity</string> 2632 <string name="vr_start_double_vr_activity">Launch Two VR mode activities</string> 2633 <string name="vr_start_vr_activity_desc">Click the button to launch the VR mode activity.</string> 2634 <string name="vr_start_vr_double_activity_desc">Click the button to launch two consecutive VR mode activities.</string> 2635 <string name="vr_check_disabled">Check that the CTS VR helper service is disabled by default.</string> 2636 <string name="vr_enable_service">Please enable \"VR Listener for CTS Verifier\" 2637 under Apps > Gear Icon > Special Access > VR Helper Services and return here.</string> 2638 <string name="vr_disable_service">Please disable \"VR Listener for CTS Verifier\" 2639 under Apps > Gear Icon > Special Access > VR Helper Services and return here.</string> 2640 <string name="nas_enable_service">Please enable \"Notification Assistant for CTS Verifier\" 2641 under Apps > Gear Icon > Default > Notification Assistant and return here.</string> 2642 <string name="nas_disable_service">Please disable \"Notification Assistant for CTS Verifier\" 2643 under Apps > Gear Icon > Default > Notification Assistant and return here.</string> 2644 <string name="nls_enable_service">Please enable \"Notification Listener for CTS Verifier\" 2645 under Apps > Gear Icon > Special Access > Notification Access and return here.</string> 2646 <string name="nls_block_app">Please block the linked application and return here.</string> 2647 <string name="nls_unblock_app">Please unblock the linked application and return here.</string> 2648 <string name="nls_block_channel">Please block the linked notification channel and return here.</string> 2649 <string name="nls_block_group">Please block the linked notification channel group and return here.</string> 2650 <string name="nls_channel_settings_with_filter_instructions">In the following dialog, please take a note of which channel settings are visible. Then turn on vibration for the channel and press \"Done\".</string> 2651 <string name="nls_channel_settings_with_filter_verification">Were the channel settings shown in a bottom sheet instead of the normal \"full-screen\" settings? Were sound and vibration the only available options?</string> 2652 <string name="nls_channel_settings_with_filter_instructions_no_vibrator">In the following dialog, please take a note of which channel settings are visible. Then add a sound for the channel and press \"Done\".</string> 2653 <string name="nls_channel_settings_with_filter_verification_no_vibrator">Were the channel settings shown in a bottom sheet instead of the normal \"full-screen\" settings? Was sound the only available option?</string> 2654 <string name="nls_disable_service">Please disable \"Notification Listener for CTS Verifier\" 2655 under Apps > Gear Icon > Special Access > Notification Access and return here.</string> 2656 <string name="nls_start_settings">Launch Settings</string> 2657 <string name="nls_service_started">Service should start once enabled.</string> 2658 <string name="nas_note_enqueued_received">Check that notification was enqueued.</string> 2659 <string name="nls_note_received">Check that notification was received.</string> 2660 <string name="nls_payload_intact">Check that notification payload was intact.</string> 2661 <string name="nls_audibly_alerted">Check that notification audibly alerting was reported correctly.</string> 2662 <string name="nas_adjustment_payload_intact">Check that the Assistant can adjust notifications.</string> 2663 <string name="nas_adjustment_enqueue_payload_intact">Check that the Assistant can adjust notifications on enqueue.</string> 2664 <string name="nas_create_channel">Check that the Assistant can create a Notification Channel for another app.</string> 2665 <string name="nas_update_channel">Check that the Assistant can update a Notification Channel for another app.</string> 2666 <string name="nas_block_channel">Check that the Assistant can block a Notification Channel.</string> 2667 <string name="nas_delete_channel">Check that the Assistant can delete a Notification Channel for another app.</string> 2668 <string name="nas_snooze_context">Check that the Assistant can snooze a notification until a given context.</string> 2669 <string name="nls_clear_one">Check that service can clear a notification.</string> 2670 <string name="nls_clear_one_reason">Check that service can clear a notification and receive the correct reason for dismissal.</string> 2671 <string name="nls_clear_one_stats">Check that service does not receive notification stats.</string> 2672 <string name="nls_clear_all">Check that service can clear all notifications that are not ongoing.</string> 2673 <string name="nls_clear_ongoing">Check that service cannot clear an ongoing notification.</string> 2674 <string name="nls_service_stopped">Service should stop once disabled.</string> 2675 <string name="nls_note_missed">Check that notification was not received.</string> 2676 <string name="nls_snooze">Check the service can be snoozed.</string> 2677 <string name="nls_unsnooze">Check the service can be unsnoozed.</string> 2678 <string name="nls_hints">Check that the listener can set hints.</string> 2679 <string name="nls_snooze_one">Check that service can snooze a notification.</string> 2680 <string name="nls_snooze_one_time">Check that service can snooze a notification for a given time.</string> 2681 <string name="nls_get_snoozed">Check that service can retrieve snoozed notifications.</string> 2682 <string name="nls_unsnooze_one">Check that service can unsnooze a notification.</string> 2683 <string name="nls_change_type_filter">Click this button to launch the settings page for this app\'s notification listener in settings. Note what types were checked and which were disabled before you make any changes. View the list of apps and note any that are not allowed. Change the filter types to allow everything except ongoing and silent notifications, and then return to this screen</string> 2684 <string name="nls_original_filter_verification">Were only alerting and silent notifications allowed? Was the Settings app not allowed? Was the ongoing option disabled? Are all only conversations and alerting notification types allowed now?</string> 2685 <string name="nls_filter_test">Checking that an alerting notification is received and a silent one is not</string> 2686 <string name="nls_reset_type_add_app_filter">Go to settings and allow all possible notification types, then turn off \"CTS Verifier\" in the app filter, and then return here.</string> 2687 <string name="nls_reset_app_filter">Go to settings and allow this listener to see notifications from all apps, and then return here.</string> 2688 <string name="nls_confirm_filter_selection">Confirm that the type and app filters are updated</string> 2689 <string name="nls_confirm_notification_not_visible">Checking visibility of notification from CTSVerifier</string> 2690 <string name="nas_note_missed_enqueued">Check that notification was not enqueued.</string> 2691 <string name="cp_test">Condition Provider test</string> 2692 <string name="cp_service_name">Condition Provider for CTS Verifier</string> 2693 <string name="cp_info">This test checks that ConditionProviderService can be enabled 2694 and disabled, and that once enabled the service is able to create, query, edit, and delete 2695 automatic zen rules. 2696 </string> 2697 <string name="cp_enable_service">Please enable \"CTS Verifier\" under Do Not Disturb access and return here.</string> 2698 <string name="cp_disable_service">Please disable \"CTS Verifier\" under Do Not Disturb access and return here.</string> 2699 <string name="cp_start_settings">Launch Settings</string> 2700 <string name="cp_create_rule">Creating Automatic Zen Rule</string> 2701 <string name="cp_create_rule_with_zen_policy">Creating Automatic Zen Rule with Zen Policy</string> 2702 <string name="cp_update_rule">Updating Automatic Zen Rule</string> 2703 <string name="cp_update_rule_use_zen_policy">Updating Automatic Rule to Use Zen Policy</string> 2704 <string name="cp_subscribe_rule">Subscribing to Automatic Zen Rule</string> 2705 <string name="cp_service_started">Service should start once enabled.</string> 2706 <string name="cp_service_stopped">Service should stop once disabled.</string> 2707 <string name="cp_unsubscribe_rule">Unsubscribing to Automatic Zen Rule</string> 2708 <string name="cp_delete_rule">Deleting Automatic Zen Rule via api</string> 2709 <string name="cp_get_rules">Retrieving Automatic Zen Rules</string> 2710 <string name="cp_get_rule">Retrieving Automatic Zen Rule</string> 2711 <string name="cp_show_rules">Click this button to launch the Automatic Zen Rule listing page in settings, and then return to this screen</string> 2712 <string name="cp_show_rules_verification">Was the automatic rule screen shown?</string> 2713 <string name="cp_disable_rule">Please disable rule "123" and return here.</string> 2714 <string name="cp_enable_rule">Please enable rule "123" and return here.</string> 2715 <string name="cp_delete_rule_broadcast">Please delete rule "123" and return here.</string> 2716 <string name="cp_rule_type">CTS rule</string> 2717 <string name="iva_pass">Pass</string> 2718 <string name="iva_fail">Fail</string> 2719 2720 <string name="cacert_test">CA Cert Notification Test</string> 2721 <string name="cacert_info">This test checks that when a CA Certificate is installed, the user is notified.</string> 2722 <string name="cacert_do_something">Do it</string> 2723 <string name="cacert_done">Done</string> 2724 <string name="cacert_install_cert_title">Tap to install a CA certificate</string> 2725 <string name="cacert_install_cert">Press the button to open Security settings. Navigate to \"Install a certificate\" (normally under \"Encryptions & credentials\") and select \"CA certificate\". Pick \"MyCA.cer\" from device storage and proceed with the installation. If this button does nothing, pass the test and move on.</string> 2726 <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> 2727 <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> 2728 <string name="cacert_check_notification">Look at the system notifications. Confirm that:\n 27291. There is a notification saying a certificate authority is installed.\n 27302. Tapping that notification brings up a more detailed explanation and a button to check trusted credentials.\n 27313. Tapping that button brings up the Trusted Credentials page you just visited.</string> 2732 <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> 2733 2734 <string name="caboot_test">CA Cert Notification on Boot test</string> 2735 <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> 2736 <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> 2737 <string name="caboot_check_creds">Check Credentials</string> 2738 <string name="caboot_if_not_installed">Only if there is no credential currently installed, install one.</string> 2739 <string name="caboot_install_cert">Install credential</string> 2740 <string name="caboot_remove_screen_lock">Remove screen lock</string> 2741 <string name="caboot_reboot_desc">Please reboot the device and return to this test.</string> 2742 <string name="caboot_after_boot">AFTER REBOOTING: Check that there is a notification saying a certificate authority is installed. 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> 2743 2744 <!-- Strings for KeyChain --> 2745 <string name="keychain_test">KeyChain Storage Test</string> 2746 <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> 2747 <string name="keychain_reset">Reset</string> 2748 <string name="keychain_skip">Skip</string> 2749 <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 2750 Tap \'Next\' to begin.</string> 2751 <string name="keychain_install_desc">Credentials generated. Tap \'Next\' to install them to the system keychain.\n\n 2752The container for the credentials will not be protected with a password; if prompted for one, leave that field blank.\n\n 2753During installation you may be prompted for a name - accept the default suggestion.\n\n 2754In the case that these credentials were already installed, you may skip this step.</string> 2755 <string name="keychain_https_desc">The last test involves setting up an HTTPS connection using credentials from the KeyChain.\n\n 2756You should be prompted to select credentials; choose the ones you just installed in the previous step.</string> 2757 <string name="keychain_reset_desc">Before marking this test as passed, tap \'Next\' to open security settings to clear credentials:\n 2758 1. Open Encryption and credentials.\n 2759 2. Tap Clear credentials.</string> 2760 2761 <!-- Strings for CA cert installation via intent test --> 2762 <string name="cacert_install_via_intent">CA Cert install via intent</string> 2763 <string name="cacert_install_via_intent_title">This test attempts to install a CA certificate via an intent.</string> 2764 <string name="cacert_install_via_intent_info">Attempt installing a CA certificate via an intent, which should not be possible. Tapping Go should show a dialog telling the user that CA certificates can put their privacy at risk and must be installed via Settings. If a any other dialog comes up, the test failed.</string> 2765 2766 <!-- Strings for credential management test --> 2767 <string name="credential_management_app_test">Credential Management App Test</string> 2768 <string name="credential_management_app_info">This test requests to manage the user\'s KeyChain credentials and become the credential management app.</string> 2769 <string name="request_manage_credentials">Request to manage credentials</string> 2770 <string name="is_credential_management_app">Check is credential management app</string> 2771 <string name="credential_management_app_policy">Check correct authentication policy is set</string> 2772 <string name="generate_key_pair">Generate key pair</string> 2773 <string name="create_and_install_certificate">Create and install certificate</string> 2774 <string name="request_certificate_authentication">Request certificate for authentication</string> 2775 <string name="sign_data_with_key">Sign data with the private key</string> 2776 <string name="verify_signature">Verify signature with the public key</string> 2777 <string name="remove_credential_management_app">Remove credential management app</string> 2778 2779 <!-- Strings for Widget --> 2780 <string name="widget_framework_test">Widget Framework Test</string> 2781 <string name="widget_framework_test_info">This test checks some basic features of the widget 2782 framework. In order to perform the test, press the Home button. Add the widget 2783 titled "CTS Verifier" to the home screen. Follow the instructions in the widget.</string> 2784 <string name="widget_name">Widget Framework Test</string> 2785 <string name="widget_pass">Pass</string> 2786 <string name="widget_fail">Fail</string> 2787 2788 <string name="provisioning_byod_non_market_apps">Non-market app installation restrictions</string> 2789 <string name="provisioning_byod_non_market_apps_info"> 2790 This test exercises user restrictions on installation of non-market apps. Follow 2791 instructions in each test. 2792 </string> 2793 2794 <string name="provisioning_byod_nonmarket_allow">Enable non-market apps</string> 2795 <string name="provisioning_byod_nonmarket_allow_info"> 2796 This test verifies that non-market apps can be installed if permitted.\n 2797 1. A package installation UI should appear.\n 2798 2. If \'Cts Verifier\' is not allowed to install apps, a warning dialog will appear 2799 blocking the install. In this case go to step 3, else skip to step 4.\n 2800 3. Allow \'Cts Verifier\' to install apps. Return to package installer.\n 2801 4. Accept the installation and verify that it succeeds (no error message is displayed). 2802 </string> 2803 2804 <string name="provisioning_byod_nonmarket_deny">Disable non-market apps</string> 2805 <string name="provisioning_byod_nonmarket_deny_info"> 2806 This test verifies that non-market apps cannot be installed unless permitted.\n 2807 1. A package installation UI should appear.\n 2808 2. Verify that the installation of the package is refused. 2809 </string> 2810 2811 <string name="provisioning_byod_nonmarket_allow_global">Enable non-market apps (global restriction)</string> 2812 <string name="provisioning_byod_nonmarket_allow_global_info"> 2813 This test verifies that non-market apps can be installed if permitted by device-wide block.\n 2814 1. A package installation UI should appear.\n 2815 2. If \'Cts Verifier\' is not allowed to install apps, a warning dialog will appear 2816 blocking the install. In this case go to step 3, else skip to step 4.\n 2817 3. Allow \'Cts Verifier\' to install apps. Return to package installer.\n 2818 4. Accept the installation and verify that it succeeds (no error message is displayed). 2819 </string> 2820 2821 <string name="provisioning_byod_nonmarket_deny_global">Disable non-market apps (global restriction)</string> 2822 <string name="provisioning_byod_nonmarket_deny_global_info"> 2823 This test verifies that non-market apps cannot be installed unless permitted by device-wide block.\n 2824 1. A package installation UI should appear.\n 2825 2. Verify that the installation of the package is refused. 2826 </string> 2827 2828 <string name="provisioning_byod_nonmarket_allow_global_primary">Enable primary user non-market apps (global restriction)</string> 2829 <string name="provisioning_byod_nonmarket_allow_global_primary_info"> 2830 This test verifies that non-market apps from the primary user can be installed if permitted.\n 2831 1. You should have received NotificationBot.apk together with the CTS verifier. If you built 2832 the CTS verifier yourself, build the NotificationBot.apk by issuing the following command on 2833 the host:\n 2834 make NotificationBot\n 2835 2. Upload the NotificationBot.apk to your device by issuing the following command on the 2836 host:\n 2837 adb push /path/to/NotificationBot.apk /data/local/tmp/\n 2838 3. Press \"Go\" to install NotificationBot.apk in your personal profile. A package 2839 installation UI should appear.\n 2840 4. If \'Cts Verifier\' is not allowed to install apps, a warning dialog will appear 2841 blocking the install. In this case go to step 5, else skip to step 6.\n 2842 5. Allow \'Cts Verifier\' to install apps. Return to package installer.\n 2843 6. Accept the installation and verify that it succeeds (no error message is displayed). 2844 </string> 2845 2846 <string name="provisioning_byod_nonmarket_deny_global_primary">Disable primary user non-market apps (global restriction)</string> 2847 <string name="provisioning_byod_nonmarket_deny_global_primary_info"> 2848 This test verifies that non-market apps from the primary user cannot be installed unless permitted.\n 2849 1. You should have received NotificationBot.apk together with the CTS verifier. If you built 2850 the CTS verifier yourself, build the NotificationBot.apk by issuing the following command on 2851 the host:\n 2852 make NotificationBot\n 2853 2. Upload the NotificationBot.apk to your device by issuing the following command on the 2854 host:\n 2855 adb push /path/to/NotificationBot.apk /data/local/tmp/\n 2856 3. Press \"Go\" to install NotificationBot.apk in your personal profile. A package 2857 installation UI should appear.\n 2858 4. Verify that the installation of the package is refused. 2859 </string> 2860 2861 <string name="provisioning_byod_capture_image_support">Camera support cross profile image capture</string> 2862 <string name="provisioning_byod_capture_image_support_info"> 2863 This test verifies that images can be captured from the managed profile using the primary profile camera.\n 2864 If prompted, accept the camera permission after pressing go.\n 2865 1. Capture a picture using the camera.\n 2866 2. Verify that the captured picture is shown.\n 2867 3. Click on the close button. 2868 </string> 2869 <string name="provisioning_byod_capture_video_support_with_extra_output">Camera support cross profile video capture (with extra output path)</string> 2870 <string name="provisioning_byod_capture_video_support_info"> 2871 This test verifies that videos can be captured from the managed profile using the primary profile camera.\n 2872 If prompted, accept the camera permission after pressing go.\n 2873 1. Capture a video using the camera.\n 2874 2. Click on the play button.\n 2875 3. Verify that the captured video is played.\n 2876 4. Click on the close button. 2877 </string> 2878 <string name="provisioning_byod_capture_video_support_without_extra_output">Camera support cross profile video capture (without extra output path)</string> 2879 <string name="provisioning_byod_capture_audio_support">Sound recorder support cross profile audio capture</string> 2880 <string name="provisioning_byod_capture_audio_support_info"> 2881 This test verifies that audio can be captured from the managed profile using the primary profile sound recorder.\n 2882 1. Capture audio.\n 2883 2. Click on the play button.\n 2884 3. Verify that the captured audio is played.\n 2885 4. Click on the close button.\n 2886 If this device does not support audio recording, please skip this test and mark it passing.\n 2887 </string> 2888 <string name="provisioning_byod_dismiss_result_dialog">Close</string> 2889 <string name="provisioning_byod_play">Play</string> 2890 <string name="provisioning_byod_verify_image_title">Verify captured image</string> 2891 <string name="provisioning_byod_verify_video_title">Verify captured video</string> 2892 <string name="provisioning_byod_verify_audio_title">Verify captured audio</string> 2893 <string name="provisioning_byod_no_image_capture_resolver">No image capture app present. Skip test.</string> 2894 <string name="provisioning_byod_no_video_capture_resolver">No video capture app present. Skip test.</string> 2895 <string name="provisioning_byod_no_audio_capture_resolver">No audio capture app present. Skip test.</string> 2896 <string name="provisioning_byod_capture_media_error">Error while capturing media from managed profile.</string> 2897 <string name="provisioning_byod_capture_image_error">Error while capturing image from managed profile.</string> 2898 2899 <string name="provisioning_byod_auth_bound_key">Authentication-bound keys</string> 2900 <string name="provisioning_byod_auth_bound_key_info"> 2901 This test verifies keystore cryptographic keys can be bound to device credentials. 2902 These keys should only be available if there was a recent enough authentication. 2903 </string> 2904 <string name="provisioning_byod_auth_bound_key_instruction"> 2905 This test verifies keystore cryptographic keys can be bound to device lockscreen challenge or fingerprints (if available). 2906 These keys should only be available if there was a recent enough authentication. \n 2907 2908 1. Press "Set up" to open Security settings. (If this device has a separate app for work 2909 settings, ignore this button and open that app manually from the launcher.) Create a 2910 lockscreen password and if available, enroll a fingerprint under "Work profile security".\n 2911 2. Go through the list of tests.\n 2912 3. Mark the overall test pass or fail.\n 2913 4. Once the set of tests are completed, remove the lockscreen challenge. 2914 </string> 2915 <string name="provisioning_byod_auth_bound_key_set_up">Set up</string> 2916 <string name="provisioning_byod_lockscreen_bound_key">Lockscreen-bound key test</string> 2917 <string name="provisioning_byod_fingerprint_bound_key">Fingerprint-bound key test</string> 2918 <string name="provisioning_byod_vpn">VPN test</string> 2919 <string name="provisioning_byod_always_on_vpn">Always-on VPN Settings</string> 2920 <string name="provisioning_byod_always_on_vpn_info"> 2921 In this test, you\'ll verify that the Settings UI for always-on VPN is correct for different 2922 VPN apps. 2923 </string> 2924 <string name="provisioning_byod_always_on_vpn_instruction"> 2925 In this test, you\'ll verify the Settings UI for always-on VPN for different VPN apps. 2926 You should have received three VPN app apks with this CTS Verifier package. 2927 They\'re named in the form of \"CtsVpnFirewallApp*.apk\".\n 2928 2929 1. Before the test, make sure CtsVpnFirewallApp isn\'t installed on your device. You can 2930 uninstall either by UI, or by\n 2931 \"adb uninstall com.android.cts.vpnfirewall\"\n 2932 2933 2. Install the first test app, by running\n 2934 \"adb install /path/to/CtsVpnFirewallAppApi23.apk\"\n 2935 2936 3. Tap \"Prepare VPN\" button below and consent to the VPN connection.\n 2937 2938 4. Once connected, verify that the system shows disclosure (on some devices this is shown in 2939 the notification area) that network traffic is being routed through the VPN app.\n 2940 2941 5. Finish all three test cases listed below.\n 2942 2943 6. Repeat step 1 to remove CtsVpnFirewallApp. 2944 </string> 2945 <string name="provisioning_byod_allow_nondismissible_notification_channel">Non-Dismissible Notification Channel</string> 2946 <string name="provisioning_byod_allow_nondismissible_notification_title">Non-Dismissible Notification</string> 2947 <string name="provisioning_byod_allow_nondismissible_notification_text">This is a notification</string> 2948 <string name="provisioning_byod_allow_nondismissible_notification">Non-Dismissible notification</string> 2949 <string name="provisioning_byod_allow_nondismissible_notification_instructions"> 2950 In this test, you\'ll verify that you are unable to dismiss a notification.\n 2951 2952 1. Grant the non-dismissible exemption by running\n 2953 \"adb shell appops set com.android.cts.verifier android:system_exempt_from_dismissible_notifications allow\".\n 2954 2955 2. Now hit \"Go\" and you will see a notification pop up.\n 2956 2957 3. Scroll from the top to see the notification and verify you are unable to dismiss it.\n 2958 2959 4. To then remove the notification you must revoke the exemption by running\n 2960 \"adb shell appops set com.android.cts.verifier android:system_exempt_from_dismissible_notifications default\".\n 2961 2962 5. Now hit \"Go\" again and dismiss the notification.\n 2963 2964 6. Mark test as pass\n 2965 </string> 2966 <string name="provisioning_byod_always_on_vpn_prepare_button">Prepare VPN</string> 2967 <string name="provisioning_byod_always_on_vpn_vpn_not_found_note"> 2968 Can\'t find VPN app. Did you install it correctly? 2969 </string> 2970 <string name="provisioning_byod_always_on_vpn_api23">VPN app targeting SDK 23</string> 2971 <string name="provisioning_byod_always_on_vpn_api23_instruction"> 2972 1. Re-install CtsVpnFirewallAppApi23.apk (skip this if you already have the correct version 2973 installed):\n 2974 \"adb install -r /path/to/CtsVpnFirewallAppApi23.apk\"\n 2975 2. Tap \"Go\" button below to go to the VPN settings page.\n 2976 3. Open configuration details page for CtsVpnFirewallApp.\n 2977 4. Confirm the \"Always-on VPN\" and \"Block connections without VPN\" switches are both off 2978 and disabled.\n 2979 </string> 2980 <string name="provisioning_byod_always_on_vpn_api24">VPN app targeting SDK 24</string> 2981 <string name="provisioning_byod_always_on_vpn_api24_instruction"> 2982 1. Re-install CtsVpnFirewallAppApi24.apk (skip this if you already have the correct version 2983 installed):\n 2984 \"adb install -r /path/to/CtsVpnFirewallAppApi24.apk\"\n 2985 2. Tap \"Go\" button below to go to the VPN settings page.\n 2986 3. Open configuration details page for CtsVpnFirewallApp.\n 2987 4. Confirm\n 2988 4.1. \"Always-on VPN\" switch is enabled and in off position\n 2989 4.2. \"Block connections without VPN\" switch is disabled and in off position\n 2990 4.3. \"Block connections without VPN\" becomes enabled once the \"Always-on VPN\" switch 2991 is turned on\n 2992 </string> 2993 <string name="provisioning_byod_always_on_vpn_not_always_on">VPN app with opt-out</string> 2994 <string name="provisioning_byod_always_on_vpn_not_always_on_instruction"> 2995 1. Re-install CtsVpnFirewallAppNotAlwaysOn.apk (skip this if you already have the correct 2996 version installed):\n 2997 \"adb install -r /path/to/CtsVpnFirewallAppNotAlwaysOn.apk\"\n 2998 2. Tap \"Go\" button below to go to the VPN settings page.\n 2999 3. Open configuration details page for CtsVpnFirewallApp.\n 3000 4. Confirm the \"Always-on VPN\" and \"Block connections without VPN\" switches are both off 3001 and disabled.\n 3002 </string> 3003 <string name="provisioning_byod_select_work_challenge">Select work lock test</string> 3004 <string name="provisioning_byod_select_work_challenge_description"> 3005 This test verifies that a work lock can be chosen.\n 3006 3007 1. Verify that you get sent to the page for Choosing a new work lock.\n 3008 2. Set a new work lock. 3009 </string> 3010 <string name="provisioning_byod_confirm_work_credentials">Confirm work lock test</string> 3011 <string name="provisioning_byod_confirm_work_credentials_description"> 3012 This test verifies that work lock is shown when opening a work app, 3013 the work lock was set correctly and it is customized according to 3014 the policies set. You can only do this test after you have done the previous test.\n 3015 Before running this test press the power button to turn the screen off and then back on and 3016 swipe to unlock.\n 3017 3018 1. Open a work app.\n 3019 2. Verify that a screen asking you for your work credentials is shown.\n 3020 3. Verify that the icon is a briefcase.\n 3021 4. Verify that the header text says \"CtsVerifier\".\n 3022 5. Confirm your credentials and verify that the credentials you entered previously work.\n 3023 6. The work app should be launched. 3024 </string> 3025 <string name="provisioning_byod_confirm_work_credentials_header"> 3026 CtsVerifier 3027 </string> 3028 <string name="provisioning_byod_pattern_work_challenge">Confirm pattern lock test</string> 3029 <string name="provisioning_byod_pattern_work_challenge_description"> 3030 This test verifies that when a work pattern lock is set, a work app can open correctly.\n 3031 3032 1. Verify that you get sent to the page for Choosing a new work lock.\n 3033 2. Set a pattern lock.\n 3034 Some devices have the pattern lock option disabled and it will not show up in the list.\n 3035 If that\'s the case then mark the test as passed.\n 3036 3. Press the power button to turn the screen off and then back on and swipe to unlock.\n 3037 4. Open a work app.\n 3038 5. Verify that a screen asking you for your work credentials is shown.\n 3039 6. Confirm your credentials and verify that the credentials you entered previously work.\n 3040 7. The work app should be launched. 3041 </string> 3042 <string name="provisioning_byod_recents">Recents redaction test</string> 3043 <string name="provisioning_byod_recents_info"> 3044 This test verifies that if a work profile is locked with a separate password, Recents views 3045 for applications in the work profile are redacted. 3046 </string> 3047 <string name="provisioning_byod_recents_instructions"> 3048 This test verifies that if a work profile is locked with a separate password, Recents views 3049 for applications in the work profile are redacted.\n 3050 Some devices may not lock as soon as the screen is turned off by default. On such devices, 3051 use the button below when requested to lock the work profile. Please skip these tests if 3052 "Recents" is absent. 3053 </string> 3054 <string name="provisioning_byod_recents_lock_now">Lock now</string> 3055 3056 <string name="provisioning_byod_recents_verify_redacted"> 3057 Verify recents are redacted when locked. 3058 </string> 3059 <string name="provisioning_byod_recents_verify_redacted_instruction"> 3060 1) Follow the instructions on-screen to set a work password.\n 3061 2) Turn the screen off and on again, or use the "lock now" button, to lock the work profile.\n 3062 3) Go to home screen and then open Recents.\n 3063 4) Confirm that this "CTS Verifier" activity is shown in Recents.\n 3064 5) Confirm that the contents of the activity <b>are</b> hidden.\n 3065 6) Return to this page and pass the test. 3066 </string> 3067 <string name="provisioning_byod_recents_verify_not_redacted"> 3068 Verify recents are not redacted when unlocked. 3069 </string> 3070 <string name="provisioning_byod_recents_verify_not_redacted_instruction"> 3071 1) Press the Go button to go to security settings.\n 3072 2) Make work profile use one lock with personal profile.\n 3073 3) Open Recents.\n 3074 4) Confirm that this "CTS Verifier" activity is shown in Recents.\n 3075 5) Confirm that the contents of the activity <b>are not</b> hidden.\n 3076 6) Return to this page and pass the test. 3077 </string> 3078 <string name="provisioning_byod_recents_remove_password"> 3079 The work profile still has a separate password. Please make it use one lock with the 3080 personal profile. 3081 </string> 3082 3083 <string name="provisioning_byod_keychain">KeyChain test</string> 3084 <string name="provisioning_byod_keychain_info_start"> 3085 In this test, you\'ll verify that keys generated by KeyChain keys are as usable as keys 3086 installed into KeyChain and that they can be hidden from users.\n 3087 The test has two parts:\n 3088 1) Testing that a generated key can be selectable by the user.\n 3089 2) Testing that a generated key can be hidden from users.\n 3090 \n 3091 Tap \"Prepare Test\" button below to begin.\n 3092 </string> 3093 <string name="provisioning_byod_keychain_info_first_test"> 3094 Once you press \'Go\', a prompt titled \"Choose certificate\" should appear.\n 3095 Verify that the list in this dialog has one item, starting with \'cts-verifier-gen\'. 3096 Press \'Select\' to select it.\n 3097 If the test passes, you\'ll see the text \"Second test ready\" at the bottom.\n 3098 \n 3099 Press \'Go\'.\n 3100 </string> 3101 <string name="provisioning_byod_keychain_info_second_test"> 3102 Once you press \'Run 2nd test\', the prompt should NOT appear.\n 3103 Verify that the prompt does not appear at all.\n 3104 Mark the test as passed if the text at the bottom shows \"PASSED (2/2)\"\n 3105 </string> 3106 3107 <string name="provisioning_byod_screenshot">Work profile Screenshot Test</string> 3108 <string name="provisioning_byod_screenshot_info"> 3109 This test verifies how screenshots are saved when using work profile apps.\n 3110 \n 3111 Whenever a screenshot is taken while a work application is in the foreground,\n 3112 the resulting image should:\n 3113 \n 3114 * include only the work application\n 3115 * be saved to the work profile 3116 </string> 3117 <string name="provisioning_byod_screenshot_start"> 3118 Press \'Open Work App\', to launch an activity in the work profile.\n 3119 </string> 3120 <string name="provisioning_byod_screenshot_open">Open Work App</string> 3121 <string name="provisioning_byod_screenshot_work_app">Work App</string> 3122 <string name="provisioning_byod_screenshot_capture">Capture Screenshot</string> 3123 <string name="provisioning_byod_screenshot_verify"> 3124 Examine the screenshot image contained within the checkerboard area below.\n 3125 \n 3126 Verify the image contains only the work app and does not contain:\n 3127 \t* any other application windows\n 3128 \t* foreground status or navigation bar content (back, home, clock, battery, signal)\n 3129 \n 3130 If these conditions are met, pass the test.\n 3131 </string> 3132 <string name="provisioning_byod_screenshot_capture_title"> Take a screenshot now using the device\'s physical buttons.</string> 3133 <string name="provisioning_byod_screenshot_capture_open">Choose Screenshot</string> 3134 <string name="provisioning_byod_screenshot_capture_cancel">Cancel Test</string> 3135 <string name="provisioning_byod_screenshot_select_title">A screenshot was detected.</string> 3136 <string name="provisioning_byod_screenshot_select_message">Press the button to choose the screenshot image just captured. If no images appear, press \'Back\' to cancel this and fail the test.</string> 3137 3138 <!-- Strings for DeskClock --> 3139 <string name="deskclock_tests">Alarms and Timers Tests</string> 3140 <string name="deskclock_tests_info"> 3141 The Alarms and Timers tests verify that the Clock app implements the AlarmClock API properly. 3142 </string> 3143 <string name="deskclock_group_alarms">Alarms</string> 3144 <string name="deskclock_group_timers">Timers</string> 3145 3146 <string name="dc_show_alarms_test">Show Alarms Test</string> 3147 <string name="dc_show_alarms_test_info"> 3148 This test verifies that the SHOW_ALARMS API works.\n 3149 1. Press the "Show Alarms" button.\n 3150 2. Verify that a UI of the clock app is launched and displays the list of alarms\n 3151 </string> 3152 <string name="dc_show_alarms_button">Show Alarms</string> 3153 3154 <string name="dc_set_alarm_with_ui_test">Set Alarm Test</string> 3155 <string name="dc_set_alarm_with_ui_test_info"> 3156 This test verifies that the ACTION_SET_ALARM with no parameters API works.\n 3157 1. Press the "Set Alarm" button.\n 3158 2. Verify that the clock app is launched and displays a UI to manage alarms.\n 3159 </string> 3160 <string name="dc_set_alarm_button">Set Alarm</string> 3161 <string name="dc_set_alarm_verify_button">Verify</string> 3162 3163 <string name="dc_start_alarm_test">Start Alarm Test</string> 3164 <string name="dc_start_alarm_test_info"> 3165 This test verifies that the ACTION_SET_ALARM API actually starts an alarm.\n 3166 1. Press the "Start Alarm" button.\n 3167 2. Make sure the alarms UI is NOT shown\n 3168 3. Wait for the alarm to fire (may take up to 2 minutes)\n 3169 4. Verify that the alarm title is: "Start Alarm Test",\n 3170 the alarm is silent and vibrating (if the device supports vibrate).\n 3171 5. Dismiss the alarm.\n 3172 6. Verify that the alarm is not in the Clock\'s alarms list. The Verify button opens 3173 the alarm view.\n 3174 </string> 3175 <string name="dc_start_alarm_button">Start Alarm</string> 3176 3177 <string name="dc_full_alarm_test">Full Alarm Test</string> 3178 <string name="dc_full_alarm_test_info"> 3179 This test verifies that the ACTION_SET_ALARM API supports all extras.\n 3180 1. Press the "Create Alarm" button.\n 3181 2. Verify that you see one alarm with the following information:\n 3182 Name of alarm: Create Alarm Test. \n 3183 Vibrate: on. (if the device supports vibrate).\n 3184 Ringtone: silent. (if the device has a speaker).\n 3185 Time: 01:23. \n 3186 Repeating on: Monday and Wednesday. \n 3187 </string> 3188 <string name="dc_full_alarm_button">Create Alarm</string> 3189 3190 <string name="dc_set_timer_with_ui_test">Set Timer Test</string> 3191 <string name="dc_set_timer_with_ui_test_info"> 3192 This test verifies that the ACTION_SET_TIMER API with no paramters open the UI\n 3193 1. Press the "Set Timer" button.\n 3194 2. Verify that the an app is launched and displays a UI to manage timers.\n 3195 </string> 3196 <string name="dc_set_timer_with_ui_button">Set Timer</string> 3197 3198 <string name="dc_start_timer_test">Start Timer Test</string> 3199 <string name="dc_start_timer_test_info"> 3200 This test verifies that the ACTION_SET_TIMER API actually starts a timer\n 3201 1. Press the "Start Timer" button.\n 3202 2. Verify that a timer is started and NO timers UI is shown.\n 3203 3. Verify that the timer named "Start Timer Test" rings after 30 seconds. Dismiss it.\n 3204 4. Verify that the timer is deleted after the dismissal.\n 3205 </string> 3206 <string name="dc_start_timer_button">Start Timer</string> 3207 3208 <string name="dc_start_timer_with_ui_test">Start Timer With UI Test</string> 3209 <string name="dc_start_timer_with_ui_test_info"> 3210 This test verifies that the ACTION_SET_TIMER API actually starts a timer with UI\n 3211 1. Press the "Start Timer" button.\n 3212 2. Verify that a timer is started and the timers UI is shown with a timer named "Start Timer Test".\n 3213 3. Verify that the timer rings after 30 seconds.\n 3214 </string> 3215 <!-- Strings for LockConfirmBypassTest --> 3216 <string name="lock_confirm_test_title">Keyguard Password Verification</string> 3217 <string name="lock_set_button_text">Set password</string> 3218 <string name="lock_change_button_text">Change password</string> 3219 <string name="lock_confirm_message"> 3220 This test verifies that the user is prompted for the current keyguard password before prompting for a new password.\n 3221 \nClick the \"Set password\" button if you currently don\'t have a password set.\n 3222 \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. 3223 </string> 3224 3225 <!-- String for Projection Tests --> 3226 <string name="test_category_projection">Projection Tests</string> 3227 <string name="projection_service_name">Projection Service</string> 3228 <string name="pca_info">This tests whether or not OpenGL projection works.\n 3229 You should see two "tumbling cubes." Tapping the screen should cause the cubes to explode.</string> 3230 <string name="pca_test">Projection Cube Test</string> 3231 <string name="pwa_info">This tests whether or displaying widgets and keyfocus navigation works.\n 3232 You should see four buttons on the bottom of the screen.\n 3233 Pressing the "up" and "down" buttons should highlight different buttons.\n 3234 Furthermore, the highlight should disappear when any button is touched, and the touched button should behave as usual.\n</string> 3235 <string name="pwa_test">Projection Widget Test</string> 3236 <string name="pwa_button_up">Up</string> 3237 <string name="pwa_button_down">Down</string> 3238 <string name="pwa_button">Button</string> 3239 <string name="pla_test">Projection Scrolling List Test</string> 3240 <string name="pla_info">This tests whether a projected list view will scroll properly\n 3241 You should see 50 list items and be able to scroll up and down the list</string> 3242 <string name="pva_test">Projection Video Playback Test</string> 3243 <string name="pva_info">This tests whether video playback works when projected.\n 3244 You should see a blinking white box and here a beep that is synchronized with each blink</string> 3245 <string name="pta_test">Projection Multitouch Test</string> 3246 <string name="pta_info">This tests whether multitouch works.\n 3247 Touching the screen should render a dot at the location you touched.\n 3248 Touching with additional fingers will render additoinal dots and you should be able to drag them around.</string> 3249 <string name="poa_test">Projection Offscreen Activity</string> 3250 <string name="poa_info">This tests whether a virtual display will continue to respond to and render even when the screen is off.\n 3251 Simply follow the instructions and the test will detect the pass conditions.\n 3252 Note that turning on the screen too early will result in a failure.</string> 3253 3254 <!-- Strings for RotationVectorTest and GameRotationVectorTest --> 3255 <string name="rotation_vector_test">Rotation Vector Accuracy Test</string> 3256 <string name="snsr_rotation_vector_set_reference"> 3257 Place the mobile device in a reference position. Note: to provide an accurate reference, 3258 align the device along one edge of a notebook laying on a table.</string> 3259 <string name="snsr_rotation_vector_reference_set">Reference position set.</string> 3260 <string name="snsr_rotation_vector_move_info">Move, shake, and rotate the device.</string> 3261 <string name="snsr_rotation_vector_set_final">Place the device back to the reference position.</string> 3262 <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> 3263 3264 <!-- Strings for device admin tests --> 3265 <string name="device_admin_notification">This is device admin notification</string> 3266 <string name="device_admin_keyguard_disable_camera">Disable camera</string> 3267 <string name="device_admin_keyguard_disable_camera_instruction"> 3268 Please press the Go button to lock the screen. Expected result is you cannot 3269 see the camera icon on the lower right corner of the screen, or if there is one, you cannot 3270 open the camera using it before you are asked for a password.\n 3271 Also, it shouldn\'t be possible to open the camera on the lockscreen by 3272 any other device specific gesture (such as double press on power button). 3273 </string> 3274 <string name="device_admin_disable_notifications">Disable notifications</string> 3275 <string name="device_admin_disable_notifications_instruction"> 3276 Please press the Go button to lock the screen. Wait a few seconds to see 3277 if a notification appears. Expected result is no notifications appear. 3278 You should be able to see one after unlocking. 3279 </string> 3280 <string name="device_admin_disable_unredacted_notifications">Disable unredacted notifications</string> 3281 <string name="device_admin_disable_unredacted_notifications_instruction"> 3282 Please press the Go button to lock the screen. Wait a few seconds to see 3283 if a notification appears. Expected result is a notification appear with 3284 its content hidden. You should be able to see the content after unlocking. 3285 </string> 3286 3287 <!-- Strings common for BYOD and DO managed provisioning tests. --> 3288 <string name="afw_device_admin">CTS Verifier</string> 3289 3290 <string name="provisioning_tests_byod">BYOD Provisioning tests</string> 3291 3292 <string name="provisioning_tests_byod_custom_terms">Custom terms</string> 3293 <string name="provisioning_tests_byod_custom_terms_instructions"> 3294 1. Please press the Go button to start the provisioning.\n 3295 2. Click \"View Terms\" button\n 3296 3. Expand \"Company ABC\" section. Verify the section content is \"Company Terms Content.\"\n 3297 4. Then hit back twice and stop the provisioning. 3298 </string> 3299 <string name="provisioning_tests_byod_custom_term_header1">Company ABC</string> 3300 3301 <!-- Strings for BYOD managed provisioning (ByodFlowTestActivity) --> 3302 <string name="test_category_managed_provisioning">Managed Provisioning</string> 3303 <string name="provisioning_byod">BYOD Managed Provisioning</string> 3304 <string name="provisioning_byod_info"> 3305 This test exercises the BYOD managed provisioning flow. 3306 Start by pressing the button on screen and follow instructions to finish the managed provisioning process. 3307 If your device has not been encrypted before, it will be encrypted and rebooted. 3308 After the provisioning process completes, return to this page and carry out further verifications. 3309 Note: the device will remain encrypted after the test which can only be disabled by factory reset. 3310 </string> 3311 <string name="provisioning_byod_start">Start BYOD provisioning flow</string> 3312 <string name="provisioning_byod_instructions"> 3313 1. Press the button below to start the managed provisioning flow. 3314 If your device has not been encrypted before, it will reboot to apply encryption. 3315 After reboot follow instructions in the notification area to complete the provisioning.\n 3316 2. After successful provisioning, come back to this page. You might need to press a button on the final provisioning screen. 3317 Please press through the following verification steps. 3318 Allow a few seconds after returning from provisioning, as the profile owner test should automatically pass.\n 3319 \n 3320 If the device is being encrypted during step 1, it will remain encrypted After this test. 3321 The only way to disable the encryption is to factory reset the device. 3322 </string> 3323 <string name="provisioning_byod_profileowner">Profile owner installed</string> 3324 <string name="provisioning_byod_disk_encryption">Full disk encryption enabled</string> 3325 <string name="provisioning_byod_disk_encryption_default_key_toast"> 3326 Cannot secure device with screen lock. Please re-run the test if you forgot to select 3327 the \"require PIN to boot\" option. 3328 </string> 3329 <string name="provisioning_byod_disk_encryption_no_pin_toast"> 3330 No PIN is detected. Please re-run the test if you forgot to set a PIN. 3331 </string> 3332 <string name="provisioning_byod_set_screen_lock_dialog_message"> 3333 Next, you will be asked to set a screen lock for the device.\n 3334 \n 3335 Please set \"1111\" as the new PIN (or any other PIN that you can memorize). 3336 You have to enter this PIN again later in order to finish the test.\n 3337 \n 3338 You may be asked whether the PIN should be required to boot the device. Please answer yes.\n 3339 \n 3340 Tap Go button to set a new screen lock. 3341 </string> 3342 <string name="provisioning_byod_remove_screen_lock_dialog_message"> 3343 The test is almost finished. \n 3344 \n 3345 Next, you will be asked to remove the screen lock that you just set. Please enter \"1111\" 3346 (or your own PIN) when prompted for the old PIN, and do not set any new screen lock. This 3347 is to make sure that the device returns to the initial state after this test.\n 3348 \n 3349 Tap Go button to remove existing screen lock. 3350 </string> 3351 <string name="provisioning_byod_workapps_visible">Badged work apps visible in Launcher</string> 3352 <string name="provisioning_byod_cross_profile_from_personal">Open app cross profiles from the personal side</string> 3353 <string name="provisioning_byod_cross_profile_from_work">Open app cross profiles from the work side</string> 3354 <string name="provisioning_app_linking">App links from the work side</string> 3355 <string name="provisioning_byod_cross_profile_app_personal">You selected the personal option.</string> 3356 <string name="provisioning_byod_cross_profile_app_work">You selected the Work option.</string> 3357 <string name="provisioning_byod_cross_profile_app_ctsverifier"> You selected the ctsverifier option </string> 3358 <string name="provisioning_byod_cross_profile_from_personal_instruction"> 3359 Please press the Go button to start an action.\n 3360 \n 3361 You should be asked to choose either \"CTS Verifier\" or \"Work\" to complete the action. 3362 Pressing either should bring up a page stating your choice.\n 3363 \n 3364 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 3365 </string> 3366 <string name="provisioning_byod_cross_profile_from_work_instruction"> 3367 Please press the Go button to start an action.\n 3368 \n 3369 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action. 3370 Pressing either should bring up a page stating your choice.\n 3371 \n 3372 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 3373 </string> 3374 <string name="provisioning_byod_cross_profile_permission_control">Cross profile permission control</string> 3375 <string name="provisioning_byod_cross_profile_permission_control_info"> 3376 This test exercises cross profile permission controls. Follow instructions above. 3377 </string> 3378 <string name="provisioning_byod_cross_profile_permission_control_instruction"> 3379 For this test you need to install CrossProfileTestApp.apk by running 3380 adb install -r -t /path/to/CrossProfileTestApp.apk. Make sure the app is installed 3381 on both the personal and work profiles.\n 3382 Press the \"Prepare test\" button to enable configuring cross profile for the test app.\n 3383 Then press through the following verification steps.\n 3384 Mark the test as passed if all the following test cases are verified. 3385 </string> 3386 <string name="provisioning_byod_cross_profile_permission_control_prepare_button">Prepare test</string> 3387 <string name="provisioning_byod_cross_profile_permission_disabled_by_default">Cross profile permission disabled by default</string> 3388 <string name="provisioning_byod_cross_profile_permission_disabled_by_default_instruction"> 3389 Press the Go button to go to Settings > Apps & notifications > Special app access >\n 3390 Connected work and personal apps.\n 3391 Choose the \"Cross profile test app\" from the list and check that the switch is disabled.\n 3392 Go back to CTS Verifier and mark the test as \"Pass\" or \"Fail\". 3393 </string> 3394 <string name="provisioning_byod_cross_profile_permission_enabled">Cross profile permission enabled</string> 3395 <string name="provisioning_byod_cross_profile_permission_enabled_instruction"> 3396 Press the Go button to open the \"Cross Profile Test App\".\n 3397 Press the \"Open Settings\" button to go to Settings > Apps & notifications > Special app access > 3398 Connected work and personal apps > Cross profile test app, then enable the switch.\n 3399 Verify that when you go back it takes you to the \"Cross Profile Test App\".\n 3400 Now verify that it shows \"INTERACTING ACROSS PROFILES ALLOWED\" message.\n 3401 Go back to CTS Verifier and mark the test as \"Pass\" or \"Fail\". 3402 </string> 3403 <string name="provisioning_byod_cross_profile_permission_disabled">Cross profile permission disabled</string> 3404 <string name="provisioning_byod_cross_profile_permission_disabled_instruction"> 3405 Press the Go button to open the \"Cross Profile Test App\".\n 3406 Press the \"Open Settings\" button to go to Settings > Apps & notifications > Special app access > 3407 Connected work and personal apps > Cross profile test app, then disable the switch.\n 3408 Verify that when you go back it takes you to the \"Cross Profile Test App\".\n 3409 Now verify that it shows \"INTERACTING ACROSS PROFILES NOT ALLOWED\" message.\n 3410 Go back to CTS Verifier and mark the test as \"Pass\" or \"Fail\". 3411 </string> 3412 <string name="provisioning_byod_app_linking_instruction"> 3413 Please press the Go button to start an action.\n 3414 \n 3415 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action.\n 3416 - If you choose \"CTS Verifier\", you should see a page stating your chose \"CTS Verifier\".\n 3417 - If you choose \"Personal\", you should be presented with another dialog between \"CTS Verifier\" 3418 and some other apps. In this case, you should choose \"CTS verifier\".\n 3419 You should then see a page stating you chose \"Personal\".\n 3420 \n 3421 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 3422 </string> 3423 <string name="provisioning_byod_keyguard_disabled_features">Keyguard disabled features</string> 3424 <string name="provisioning_byod_keyguard_disabled_features_info"> 3425 This test exercises Keyguard Disabled Features. Follow instructions above. 3426 </string> 3427 <string name="provisioning_byod_keyguard_disabled_features_instruction"> 3428 Please go to Settings > Security > Device administrators and set 3429 \"CTS Verifier\" as active admin.\n 3430 After that please go to Settings > Security > Screen lock and set 3431 your screen lock password to \"testpassword\".\n 3432 Then please press the \"Prepare test\" button to disable trust agents.\n 3433 Then please press through the following verification steps.\n 3434 Note: After leaving the screen active admin status will be cleared. 3435 Please go to Settings > Security > Screen lock and set your 3436 password type to \"None\". 3437 </string> 3438 <string name="provisioning_byod_keyguard_disabled_features_prepare_button">Prepare test</string> 3439 <string name="provisioning_byod_keyguard_disabled_features_not_admin">CtsVerifier is not active admin. Please follow instructions.</string> 3440 <string name="provisioning_byod_disable_trust_agents">Disable trust agents</string> 3441 <string name="provisioning_byod_disable_trust_agents_instruction"> 3442 Please press the Go button to go to Settings > Security. Then go to Trusted agents and\n 3443 check if the agents are shown as disabled by the administrator. 3444 Then please press Back and mark the test as \"Pass\" or \"Fail\". 3445 </string> 3446 <string name="provisioning_byod_fingerprint_disabled_in_settings">Fingerprint is disabled in Settings</string> 3447 <string name="provisioning_byod_fingerprint_disabled_in_settings_instruction"> 3448 Please press the Go button to go to Settings > Security. Then go to Fingerprint and\n 3449 check if the disclaimer at the bottom of screen is altered to warn the users for\n 3450 fingerprint being disabled in lock screen. Then please press Back and mark the \n 3451 test as \"Pass\" or \"Fail\". 3452 </string> 3453 <string name="provisioning_byod_disable_fingerprint">Fingerprint disabled on keyguard</string> 3454 <string name="provisioning_byod_disable_fingerprint_instruction"> 3455 Please press the Go button to lock the screen. Then try to log in using the fingerprint reader.\n 3456 Expected result is you cannot log in using your fingerprint.\n 3457 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\". 3458 </string> 3459 <string name="provisioning_byod_disable_unredacted_notifications">Unredacted notifications disabled on keyguard</string> 3460 <string name="provisioning_byod_disable_unredacted_notifications_instruction"> 3461 Please press the Go button to lock the screen. Wait a couple of seconds and look out for a 3462 notification from CtsVerifier.\n 3463 Expected result is the notification is shown as \"Contents hidden by policy\", you can not see the contents 3464 (Which would read \"This is a notification\"). You should be seeing a work badge.\n 3465 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\". 3466 </string> 3467 <string name="provisioning_byod_notification_title">This is a notification</string> 3468 <string name="provisioning_byod_notification_public_title">Contents hidden by policy</string> 3469 3470 <string name="provisioning_byod_disallow_apps_control">Disallow apps control</string> 3471 <string name="provisioning_byod_disallow_apps_control_info"> 3472 This test exercises Disallow Apps Control. Follow instructions above. 3473 </string> 3474 <string name="provisioning_byod_disallow_apps_control_instruction"> 3475 Please press the \"Prepare test\" button to disallow apps control for managed apps.\n 3476 Then please press through the following verification steps.\n 3477 Note: After leaving the screen disallow apps control restriction will be cleared. 3478 </string> 3479 <string name="provisioning_byod_disallow_apps_control_prepare_button">Prepare test</string> 3480 <string name="provisioning_byod_disabled_uninstall_button">Disabled uninstall button</string> 3481 <string name="provisioning_byod_disabled_uninstall_button_instruction"> 3482 Please press the Go button to go to Settings > Apps. 3483 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3484 Choose a managed app. Check that performing either \"Uninstall\" or \"Disable\" is not possible and triggers a support message when trying to do so. 3485 Then please press Back (or navigate back to this app using Recents) and mark the test as \"Pass\" or \"Fail\". 3486 </string> 3487 <string name="provisioning_byod_disabled_force_stop_button">Disabled force stop button</string> 3488 <string name="provisioning_byod_disabled_force_stop_button_instruction"> 3489 Please press the Go button to go to Settings > Apps. 3490 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3491 Choose a managed app. Check that performing \"Force stop\" is not possible and triggers a support message when trying to do so. 3492 Then please press Back (or navigate back to this app using Recents) and mark the test as \"Pass\" or \"Fail\". 3493 </string> 3494 <string name="provisioning_byod_disabled_app_storage_buttons">Disabled app storage buttons</string> 3495 <string name="provisioning_byod_disabled_app_storage_buttons_instruction"> 3496 Please press the Go button to go to Settings > Apps. 3497 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3498 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. 3499 Note: if an app has no data then tapping the clear data button has no effect anyway. Make sure you have selected 3500 the badged version of app with non-zero app data. Badged \"Settings\" may be a good candidate. 3501 Then please press Back (or navigate back to this app using Recents) and mark the test as \"Pass\" or \"Fail\". 3502 </string> 3503 3504 <string name="provisioning_byod_work_status_toast">Work status toast is displayed</string> 3505 <string name="provisioning_byod_work_status_toast_instruction"> 3506 Please press the Go button to launch a work activity. 3507 \n\n 3508 Follow instructions and then return and mark this test accordingly. 3509 </string> 3510 <string name="provisioning_byod_work_status_toast_activity"> 3511 Turn off the screen and wait a few seconds then turn on the screen again. 3512 \n\n 3513 Verify that a toast was displayed saying you are in the work profile. 3514 \n\n 3515 Please press finish to return to the tests and then mark this test accordingly. 3516 </string> 3517 <string name="provisioning_byod_user_settings">Profile-aware user settings</string> 3518 <string name="provisioning_byod_user_settings_instruction"> 3519 Please press the Go button to open the Settings page. 3520 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher.)\n 3521 Navigate to Accounts and confirm that:\n 3522 - There are two auto-sync options present, one for personal and one for work data (on the screen or in the overflow menu or in different tab).\n 3523 - De-selecting either option prompts a warning dialog.\n 3524 \n 3525 Use the Back button (or navigate back to this app using Recents) to return to this page. 3526 </string> 3527 <string name="provisioning_byod_workapps_visible_instruction"> 3528 Please press the Go button to start the launcher. 3529 Go to All Apps screen and scroll through it to confirm that:\n 3530 \n 3531 - A new set of work apps including CTS Verifier appear in the list.\n 3532 - Work badge overlay appears on work app\'s icon (see example icon below, color and style may vary).\n 3533 - The work badge overlay has the same size and position on each work app\'s icon. 3534 \n 3535 Then navigate back to this screen using Recents button. 3536 </string> 3537 3538 <string name="provisioning_byod_app_settings">Profile-aware app settings</string> 3539 <string name="provisioning_byod_app_settings_instruction"> 3540 Please press the Go button to open Apps page in settings. 3541 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3542 \n 3543 Verify that Personal and Work exists in the dropdown list(or UI has Personal and Work tab). When selecting Work it will 3544 bring up apps setting in the work profile.\n 3545 \n 3546 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3547 </string> 3548 3549 <string name="provisioning_byod_location_settings">Profile-aware location settings</string> 3550 <string name="provisioning_byod_location_settings_instruction"> 3551 Please press the Go button to open Location page in settings. 3552 (If this device has a separate app for work settings, ignore the Go button and navigate to that app manually, if necessary).\n 3553 \n 3554 Verify that work profile entry exists in the page(or in Work tab) and it has a toggleable switch.\n 3555 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 3556 Then switch the main location switch on again. You should see the work profile location switch go enabled and into its previous state.\n 3557 \n 3558 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3559 </string> 3560 <string name="provisioning_byod_location_failed">Failed to obtain location from any provider</string> 3561 <string name="provisioning_byod_location_no_provider">Cannot obtain location: no providers available.</string> 3562 <string name="provisioning_byod_location_trying">Trying to obtain location using providers: %1$s</string> 3563 <string name="provisioning_byod_location_obtained">Location has been obtained.</string> 3564 <string name="provisioning_byod_pass_message">PASS: %1$s</string> 3565 <string name="provisioning_byod_fail_message">FAIL: %1$s</string> 3566 <string name="provisioning_byod_location_test_activity">Location listener</string> 3567 <string name="provisioning_byod_location_checker_activity">Location checker</string> 3568 3569 3570 <string name="provisioning_byod_wifi_data_usage_settings">Profile-aware data usage settings (Wi-Fi)</string> 3571 <string name="provisioning_byod_wifi_data_usage_settings_instruction"> 3572 Please press the Go button to open the Settings page. 3573 (If this device has a separate app for work settings, ignore the Go button and navigate to that app manually).\n 3574 \n 3575 Navigate to the \"Network & Internet\" page and then click on \"Wi-Fi\" and then \"Wi-Fi data usage\".\n 3576 Confirm that \"All work apps\" section is present and that it is possible to see the data usage for work (badged) apps.\n 3577 (If the section is not present, this might be because work apps have not used Wi-Fi data yet. Ensure that you have used Wi-Fi data on a work app, then repeat these instructions.)\n 3578 \n 3579 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3580 </string> 3581 3582 <string name="provisioning_byod_cellular_data_usage_settings">Profile-aware data usage settings (Mobile)</string> 3583 <string name="provisioning_byod_cellular_data_usage_settings_instruction"> 3584 Please disable Wi-Fi connection on your device.\n 3585 Please make sure you have added a SIM card with data plan to your phone, have enabled data over mobile and in case of dual SIM devices, have selected the right SIM for data connection.\n 3586 Please carry out operations that will use mobile data using both badged and unbadged apps (e.g. visit a page in a browser).\n 3587 \n 3588 Please press the Go button to open the Settings page. 3589 (If this device has a separate app for work settings, ignore the Go button and navigate to that app manually).\n 3590 \n 3591 Navigate to the \"Network & Internet\" page and then click on \"Mobile network\" and then \"App data usage\".\n 3592 Confirm that \"All work apps\" section is present and that it is possible to see the data usage for work (badged) apps.\n 3593 \n 3594 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3595 </string> 3596 3597 <string name="provisioning_byod_cred_settings">Profile-aware trusted credential settings</string> 3598 <string name="provisioning_byod_cred_settings_instruction"> 3599 Please press the Go button to open the Security settings. 3600 Navigate to "Trusted credentials" and wait for the UI to load. 3601 After the list is loaded, confirm that:\n 3602 \n 3603 The page list credentials for both "Personal" and "Work" profiles.\n 3604 \n 3605 Then use the Back button to return to this test and mark accordingly. 3606 </string> 3607 3608 <string name="provisioning_byod_print_settings">Profile-aware printing settings</string> 3609 <string name="provisioning_byod_print_settings_instruction"> 3610 Please press the Go button to open the Printing settings. 3611 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3612 \n 3613 Verify that work profile exists in the dropdown list and selecting it will 3614 bring up printing setting in the work profile.\n 3615 \n 3616 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3617 </string> 3618 3619 <string name="provisioning_byod_cross_profile_intent_filters">Cross profile intent filters are set</string> 3620 3621 <string name="provisioning_byod_nfc_beam">Disable Nfc beam</string> 3622 <string name="provisioning_byod_nfc_beam_allowed_instruction"> 3623 Please press the Go button to test if Nfc beam can be triggered in the work profile.\n 3624 \n 3625 For the first test, press \"Send manual beam\" to trigger a beam, then bump into another device to send the tag. Verify that the tag is successfully received.\n 3626 \n 3627 For the second test, press \"Send share intent\" to trigger a beam, then bump into another device to send the tag. Verify that the tag is successfully received.\n 3628 \n 3629 Then use the Back button to return to this test and mark accordingly. 3630 </string> 3631 <string name="provisioning_byod_nfc_beam_disallowed_instruction"> 3632 Please press the Go button to test if Nfc beam is disallowed by policy 3633 \n 3634 Verify that Nfc beam is not triggered when pressing the button.\n 3635 \n 3636 Then use the Back button to return to this test and mark accordingly. 3637 </string> 3638 <string name="provisioning_byod_send_manual_beam">Send manual beam</string> 3639 <string name="provisioning_byod_send_share_intent">Send share intent</string> 3640 <string name="provisioning_byod_cannot_resolve_beam_activity">Cannot find beam activity</string> 3641 3642 <string name="test_failed_cannot_start_intent">Cannot start the given intent.</string> 3643 <string name="provisioning_byod_no_activity">Cannot communicate with activity in the work profile.</string> 3644 <string name="provisioning_byod_delete_profile">Initiate deletion of work profile.</string> 3645 <string name="provisioning_byod_profile_deleted">Work profile deleted.</string> 3646 <string name="provisioning_byod_disabled">Device provisioning is not enabled.</string> 3647 <string name="provisioning_button_finish">Finish</string> 3648 <string name="provisioning_cross_profile_chooser">Choose an app to complete action</string> 3649 3650 <string name="provisioning_byod_no_gps_location_feature">No GPS feature present. Skip test.</string> 3651 <string name="provisioning_byod_location_mode_enable">Enable location</string> 3652 <string name="provisioning_byod_location_mode_enable_missing_permission">Permission missing</string> 3653 <string name="provisioning_byod_location_mode_enable_instruction"> 3654 This test verifies that the location can be enabled for the managed profile apps.\n 3655 1. Press the \"Prepare Test\" button to go to the location settings page, set both the main location switch and the work profile location switch enabled.\n 3656 2. Return using back button and press Go button to check if location is available. If prompted, accept the location permission.\n 3657 3. Check the result message below and mark the test accordingly.\n 3658 \n 3659 If the test fails to obtain location, try to enable as many location services as possible and move outside to make GPS work. 3660 </string> 3661 3662 <string name="provisioning_byod_location_mode_disable">Disable location</string> 3663 <string name="provisioning_byod_location_mode_time_out_toast">Timeout waiting for gps location change</string> 3664 <string name="provisioning_byod_location_mode_disable_instruction"> 3665 This test verifies that the location can be disabled for the managed profile apps through the main location switch.\n 3666 1. Press the \"Prepare Test\" button to go to the location settings page, set the main location switch disabled.\n 3667 2. Return using back button and press Go button to check if location is available. If prompted, accept the location permission.\n 3668 3. Check the result message below and mark the test accordingly.\n 3669 </string> 3670 3671 <string name="provisioning_byod_work_location_mode_disable">Disable location for work profile</string> 3672 <string name="provisioning_byod_work_location_mode_disable_instruction"> 3673 This test verifies that the location can be disabled for the managed profile apps through work profile location switch.\n 3674 1. Press the \"Prepare Test\" button to go to the location settings page, set the work location switch disabled while the main location switch is still enabled.\n 3675 2. Return using back button and press Go button to check if location is available. If prompted, accept the location permission.\n 3676 3. Check the result message below and mark the test accordingly.\n 3677 </string> 3678 <string name="provisioning_byod_primary_location_when_work_disabled">Primary receives updates while work location is disabled</string> 3679 <string name="provisioning_byod_primary_location_when_work_disabled_instruction"> 3680 This test verifies that location is still available by primary profile when location updates are disabled for managed profile apps through work profile location switch.\n 3681 1. Press the \"Prepare Test\" button to go to the location settings page, set the work location switch disabled while the main location switch is still enabled.\n 3682 2. Return using back button and press Go button to check if location is available. If prompted, accept the location permission.\n 3683 3. Check the result message below and mark the test accordingly.\n 3684 \n 3685 If the test fails to obtain location, try to enable as many location services as possible and move outside to make GPS work. 3686 </string> 3687 3688 <string name="provisioning_byod_personal_ringtones">Personal ringtones</string> 3689 <string name="provisioning_byod_personal_ringtones_instruction"> 3690 This test verifies that personal ringtones can be changed independently of work profile ringtones.\n 3691 1. Press the go button to go to the sound settings page. Under \"Work profile sounds\" turn off the \"use personal profile sounds\" switch.\n 3692 2. Change the personal \"Phone ringtone\", \"Default notification sound\", and \"Default alarm sound\" settings to different values. Skip any of these settings that do not exist.\n 3693 3. Read the values displayed under \"Work phone ringtone\", \"Default work notification sound\", and \"Default work alarm sound\". If any of the settings in #2 did not exist, skip the\n 3694 corresponding work profile setting."\n 3695 4. Verify that the work sounds are different to the personal values just set.\n 3696 5. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n 3697 </string> 3698 3699 <string name="provisioning_byod_uninstall_work_app">Uninstall work app from launcher</string> 3700 <string name="provisioning_byod_uninstall_work_app_instruction"> 3701 This test verifies that work profile apps can be uninstalled.\n 3702 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 3703 make NotificationBot\n 3704 2. Upload the NotificationBot.apk to your device by issuing the following command on the host:\n 3705 adb push /path/to/NotificationBot.apk /data/local/tmp/\n 3706 3. Pres \"Go\" to install NotificationBot.apk on your work profile.\n 3707 4. If you are presented with a dialog to allow installing of unknown apps, enable that option.\n 3708 5. Go to home screen.\n 3709 6. Verify that the newly installed app, \"CTS Robot\", can successfully be uninstalled from the launcher.\n 3710 </string> 3711 <string name="provisioning_byod_uninstall_work_app_install_work_app">Install work app</string> 3712 3713 <string name="provisioning_byod_launch_work_tab">Launch work tab in launcher</string> 3714 <string name="provisioning_byod_launch_work_tab_instruction"> 3715 This test verifies that the work tab (if tabs are supported) can be launched.\n 3716 1. Press \"Go\".\n 3717 2. If this device supports tabs, verify that you have landed on the work tab.\n 3718 3. If this device doesn\'t support tabs, verify that you have landing on the all apps page .\n 3719 </string> 3720 3721 <string name="provisioning_byod_turn_off_work">Turn off work profile</string> 3722 <string name="provisioning_byod_turn_off_work_info">This test verifies device behaviors when turning off work profile.</string> 3723 <string name="provisioning_byod_turn_off_work_instructions"> 3724 This test verifies the device behavior when work profile is turned off.\n 3725 Please exercise the following tests in sequence.\n 3726 The button below can be used to open the Settings page where you can toggle work profile.\n 3727 (If this device has a separate app for work settings, ignore the button and open that app manually from the launcher).\n 3728 </string> 3729 <string name="provisioning_byod_turn_off_work_prepare_button">Open Settings to toggle work profile</string> 3730 3731 <string name="provisioning_byod_turn_off_work_prepare_notifications">Prepare a work notification</string> 3732 <string name="provisioning_byod_turn_off_work_prepare_notifications_instruction"> 3733 This is a test setup step.\n 3734 1. Press the go button to send a work notification. (if a permission is requested, grant it and press the go button again). \n 3735 2. Verify that the notification is displayed and mark this test as passed.\n 3736 (Note: in the following test, you will be asked to verify the notification disappears after work profile is turned off.) 3737 </string> 3738 3739 <string name="provisioning_byod_turn_off_work_turned_off">Please turn off work profile</string> 3740 <string name="provisioning_byod_turn_off_work_turned_off_toast">Open settings to turn off work profile, using the button above.</string> 3741 3742 <string name="provisioning_byod_turn_off_work_notifications">Notifications when work profile is off</string> 3743 <string name="provisioning_byod_turn_off_work_notifications_instruction"> 3744 Verify that the previously-shown work notification has now disappeared. 3745 </string> 3746 3747 <string name="provisioning_byod_turn_off_work_launcher">Starting work apps when work profile is off</string> 3748 <string name="provisioning_byod_turn_off_work_launcher_instruction"> 3749 This test verifies that work applications cannot be started if work profile is off.\n 3750 1. Open settings to turn work profile back on, either manually or using the "Open Settings to toggle work" on the previous page.\n 3751 2. Add a work app to your home screen.\n 3752 3. Turn work profile off from Settings.\n 3753 4. Press home to go to the launcher.\n 3754 5. Verify that the work app is greyed out.\n 3755 6. Tap on the work app.\n 3756 7. Verify that the application does not start.\n 3757 </string> 3758 3759 <string name="provisioning_byod_turn_off_work_turned_on">Please turn work profile back on</string> 3760 <string name="provisioning_byod_turn_off_work_turned_on_toast">Open settings to turn work profile back on, either manually or using the button above.</string> 3761 3762 <string name="provisioning_byod_turn_on_work_icon">Status bar icon when work profile is on</string> 3763 <string name="provisioning_byod_turn_on_work_icon_instruction"> 3764 Now that work profile is back on, please verify that the status bar icon for work profile off is no longer visible. 3765 </string> 3766 3767 <string name="provisioning_byod_turn_on_work_launcher">Starting work apps when work profile is on</string> 3768 <string name="provisioning_byod_turn_on_work_launcher_instruction"> 3769 Now that work profile is back on, please go to the launcher and verify that you can start a work application. 3770 </string> 3771 3772 <string name="provisioning_byod_organization_info">Organization Info</string> 3773 <string name="provisioning_byod_organization_name_hint">Name</string> 3774 <string name="provisioning_byod_set_organization_info_button_text">Set</string> 3775 <string name="provisioning_byod_organization_info_instructions"> 3776 This test verifies that the Organization Info was set correctly. 3777 You can only do this test after you have done "select work lock" test.\n 3778 1. Enter your organization name.\n 3779 2. Press the Set button to set organization Info.\n 3780 3. Press the Go button to open a dialog to confirm work credentials.\n 3781 (If this device has a separate app for work settings, ignore the Go button and open the work lock screen manually to confirm, if necessary.)\n 3782 4. Verify that the header text has organization name as set by you.\n 3783 </string> 3784 3785 <string name="provisioning_byod_no_secure_lockscreen">No work lockscreen password set. Please run \"Select work lock test\" and rerun this test</string> 3786 3787 <string name="provisioning_byod_parent_profile_password">Personal password test</string> 3788 <string name="provisioning_byod_parent_profile_password_description"> 3789 This test verifies that the password on the personal side can be chosen from within a managed profile.\n 3790 3791 1. Press the Go button to set a new password for the personal side.\n 3792 2. Lock and unlock the screen to verify that the personal side password was set correctly.\n 3793 </string> 3794 <string name="provisioning_byod_work_profile_widget">Work profile widget</string> 3795 <string name="provisioning_byod_work_profile_widget_info">Verify that work profile widget can be added into launcher</string> 3796 <string name="provisioning_byod_work_profile_widget_description"> 3797 This test verifies that the widget in work profile can be added into Launcher.\n 3798 3799 1. Go to home screen.\n 3800 2. Add the widget titled \"CTS Verifier\" and badged with work profile briefcase to the home screen.\n 3801 3. If you can add the widget to the home screen, please select \"pass\". Otherwise, select \"fail\". 3802 </string> 3803 3804 <!-- Strings for DeviceOwnerNegativeTestActivity --> 3805 <string name="negative_device_owner">No Device Owner Tests</string> 3806 <string name="device_owner_negative_category">No Device Owner Tests</string> 3807 <string name="device_owner_provisioning_negative">Device owner provisioning</string> 3808 <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> 3809 <string name="start_device_owner_provisioning_button">Start provisioning</string> 3810 <string name="enterprise_privacy_quick_settings_negative">Quick settings disclosure</string> 3811 <string name="enterprise_privacy_quick_settings_negative_info"> 3812 Please do the following:\n 3813 1) Open and fully expand Quick Settings.\n 3814 2) Verify that at the bottom of Quick Settings, you are not told the device is managed.\n 3815 3) Close Quick Settings.\n 3816 \n 3817 If this device does not have quick settings, please skip this test and mark it passing 3818 </string> 3819 <string name="enterprise_privacy_keyguard_negative">Keyguard disclosure</string> 3820 <string name="enterprise_privacy_keyguard_negative_info"> 3821 Please do the following:\n 3822 1) Press the Go button to open Settings.\n 3823 2) Navigate to \"Security\" > \"Screen lock\" and select the first screen lock type that is not \"None\".\n 3824 3) Use the Back button to return to this page.\n 3825 4) Lock the device.\n 3826 5) Verify that on the lock screen, you are not told the device is managed.\n 3827 6) Unlock the device.\n 3828 7) Repeat steps (1) through (6) for each screen lock type other than \"None\". 3829 </string> 3830 <string name="enterprise_privacy_add_account_negative">Add account disclosure</string> 3831 <string name="enterprise_privacy_add_account_negative_info"> 3832 Please do the following:\n 3833 1) Press the Go button to open Settings.\n 3834 2) In the screen that opens, verify that you are not told that the device is managed.\n 3835 3) Use the Back button to return to this page. 3836 </string> 3837 3838 <!-- Strings for DeviceOwnerPositiveTestActivity --> 3839 <string name="positive_device_owner">Device Owner Tests</string> 3840 <string name="device_owner_positive_tests">Device Owner positive tests</string> 3841 <string name="device_owner_positive_tests_instructions"> 3842 The positive device owner tests verify policies on a corporate owned device.\n 3843 Press below button first, follow steps described in the dialog that pops up, 3844 then proceed to the test cases.\n 3845 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 3846 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 3847 be run last so that it does not interfere with other tests. 3848 </string> 3849 <string name="device_owner_positive_tests_info"> 3850 The positive device owner tests verify policies on a corporate owned device.\n 3851 Press below button first, follow steps described in the dialog that pops up, 3852 then proceed to the test cases.\n 3853 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 3854 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 3855 be run last so that it does not interfere with other tests. 3856 </string> 3857 <string name="device_owner_positive_category">Device Owner Tests</string> 3858 <string name="set_device_owner_button_label">Set up device owner</string> 3859 <string name="set_device_owner_dialog_title">Set up device owner</string> 3860 <string name="grant_headless_system_user_permissions"> 3861 For this test you need to grant some permissions to CtsVerifier by running\n 3862 adb shell pm grant --user current com.android.cts.verifier android.permission.INTERACT_ACROSS_USERS\n 3863 adb shell pm grant --user 0 com.android.cts.verifier android.permission.INTERACT_ACROSS_USERS\n 3864 adb shell am compat enable ALLOW_TEST_API_ACCESS com.android.cts.verifier\n\n 3865 </string> 3866 <string name="set_device_owner_dialog_text"> 3867 For this test you need to install CtsEmptyDeviceOwner.apk by running\n 3868 adb install -r -t /path/to/CtsEmptyDeviceOwner.apk\n 3869 Then you need to set this app as the device owner by running\n 3870 adb shell dpm set-device-owner --user 0 com.android.cts.emptydeviceowner/.EmptyDeviceAdmin 3871 </string> 3872 <string name="set_device_owner_headless_dialog_text"> 3873 For this test you need to set the device owner by running\n 3874 adb shell dpm set-device-owner --user 0 com.android.cts.verifier/.managedprovisioning.DeviceAdminTestReceiver 3875 </string> 3876 <string name="device_owner_remove_device_owner_test">Remove device owner</string> 3877 <string name="device_owner_remove_device_owner_test_info"> 3878 Please press the Go button to check whether CTSVerifier is Device Owner. Then press the Remove Device Owner button, 3879 and check that CTSVerifier is NOT Device Owner anymore. 3880 </string> 3881 <string name="remove_device_owner_button">Remove device owner</string> 3882 <string name="device_owner_check_device_owner_test">Check device owner</string> 3883 <string name="device_owner_check_profile_owner_test">Check profile owner</string> 3884 <string name="device_owner_check_user_affiliation_test">Check user affiliation</string> 3885 <string name="device_owner_incorrect_device_owner">Missing or incorrect device owner: CTSVerifier is not DO for user %1$d!</string> 3886 <string name="device_owner_incorrect_profile_owner">Missing or incorrect profile owner: CTSVerifier is not PO for user %1$d!</string> 3887 <string name="device_owner_user_not_affiliated">User %1$d! is not affiliated</string> 3888 <string name="device_owner_wifi_lockdown_test">WiFi configuration lockdown</string> 3889 <string name="device_owner_wifi_lockdown_info"> 3890 Please enter the SSID and auth method of an available WiFi Access Point and press the button to create a 3891 WiFi configuration. This configuration must NOT EXIST yet (you can use Settings > WiFi to verify - if it exists, 3892 then select the option to forget it). If the Wifi requires a password, wait for the \'Could not connect to the wifi network\' 3893 notification, tap the notification, set the password and connect to the network. 3894 The test cases are going to use this config. Please go through test cases in order (from top to bottom). 3895 </string> 3896 <string name="switch_wifi_lockdown_off_button">WiFi config lockdown off</string> 3897 <string name="switch_wifi_lockdown_on_button">WiFi config lockdown on</string> 3898 <string name="wifi_lockdown_go_settings_wifi_button">Go to WiFi Settings</string> 3899 <string name="device_owner_wifi_key_management_none_button">None</string> 3900 <string name="device_owner_wifi_key_management_wpa_button">WPA</string> 3901 <string name="device_owner_wifi_key_management_wep_button">WEP</string> 3902 <string name="create_wifi_config_button_label">Create WiFi configuration</string> 3903 <string name="wifi_lockdown_add_network_failed_dialog_title">WiFi configuration could not be created</string> 3904 <string name="wifi_lockdown_add_network_failed_dialog_text"> 3905 There was an error during creation of WiFi configuration. Check if WiFi is switched on. 3906 </string> 3907 <string name="device_owner_wifi_config_unlocked_modification_test">Unlocked config is modifiable in Settings</string> 3908 <string name="device_owner_wifi_config_unlocked_modification_test_info"> 3909 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 3910 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be edited. 3911 Please make sure you can connect to it. The test is successful if the config is editable 3912 and can be connected to. 3913 </string> 3914 <string name="device_owner_wifi_config_unlocked_modification_test_info" product="automotive"> 3915 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 3916 Settings > WiFi and see if the CTSVerifier created WiFi configuration is editable 3917 (it\'s ok if it\'s not editable, but then take note so the next test can be skipped). 3918 Please make sure you can connect to it. The test is successful if the config can be 3919 connected to. 3920 </string> 3921 <string name="device_owner_wifi_config_locked_modification_test">Locked config is not modifiable in Settings</string> 3922 <string name="device_owner_wifi_config_locked_modification_test_info"> 3923 Please press the button to ensure WiFi config lockdown is in effect. Then go to 3924 Settings > WiFi and see if the CTSVerifier created WiFi configuration can NOT be edited 3925 or removed. The test is successful if the config is NOT modifiable. 3926 </string> 3927 <string name="device_owner_wifi_config_locked_modification_test_info" product="automotive"> 3928 NOTE: if the WiFi was not editable in the previous step, please skip this test. 3929 Please press the button to ensure WiFi config lockdown is in effect. Then go to 3930 Settings > WiFi and see if the CTSVerifier created WiFi configuration can NOT be edited 3931 or removed. The test is successful if the config is NOT modifiable. 3932 </string> 3933 <string name="device_owner_wifi_config_locked_connection_test">Locked config can be connected to</string> 3934 <string name="device_owner_wifi_config_locked_connection_test_info"> 3935 Please press the button to ensure WiFi config lockdown is in effect. Then go to 3936 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be connected 3937 to manually. The test is successful if the connection can be established. 3938 </string> 3939 <string name="device_owner_wifi_config_unlocked_removal_test">Unlocked config can be forgotten in Settings</string> 3940 <string name="device_owner_wifi_config_unlocked_removal_test_info"> 3941 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 3942 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be forgotten. 3943 The test is successful if the config could be forgotten and is removed from the list of saved configs. 3944 </string> 3945 <string name="device_owner_disable_statusbar_test">Disable status bar</string> 3946 <string name="device_owner_disable_statusbar_test_info"> 3947 Please press the below button to disable the status bar and verify that quick settings and notifications 3948 are no longer available.\n 3949 Next, press the button to reenable the status bar and verify that quick settings and notifications 3950 are available again.\n 3951 Please mark the test accordingly. 3952 </string> 3953 <string name="device_owner_disable_statusbar_button">Disable status bar</string> 3954 <string name="device_owner_reenable_statusbar_button">Reenable status bar</string> 3955 <string name="device_owner_disable_keyguard_test">Disable keyguard</string> 3956 <string name="device_owner_disable_keyguard_test_info"> 3957 Before running this test, please make sure you have not set any device lockscreen password.\n 3958 Please press the below button to disable the keyguard. Press the power button on your device to 3959 switch off the screen. Then press the power button to switch the screen back on and verify that 3960 no keyguard was shown.\n 3961 Next, press the button to reenable the keyguard and repeat the above steps, this time verifying that 3962 a keyguard was shown.\n 3963 Please mark the test accordingly. 3964 </string> 3965 <string name="device_owner_disable_keyguard_button">Disable keyguard</string> 3966 <string name="device_owner_reenable_keyguard_button">Reenable keyguard</string> 3967 <string name="device_owner_lock_task_ui_test">LockTask UI</string> 3968 <string name="device_owner_lock_task_ui_test_info"> 3969 The following tests verify the configurable UI during LockTask, a special mode that 3970 prevents the user from leaving the current application.\n\n 3971 Please make sure the lock screen is turned on before the test. Press the button below to 3972 start LockTask mode. Then mark each item as \'pass\' or \'fail\' according to the 3973 instructions.\n\n 3974 Finally, execute the last test item to leave LockTask mode. 3975 </string> 3976 <string name="start_lock_task_button_label">Start LockTask mode</string> 3977 <string name="device_owner_lock_task_ui_default_test">Default LockTask UI</string> 3978 <string name="device_owner_lock_task_ui_default_test_info"> 3979 Press the button below to reset to default LockTask UI. 3980 Observe the following UI restrictions. Mark the test as \'pass\' only if ALL of the 3981 requirements below are met.\n\n 3982 1) If the device under test (DUT) has a status bar: nothing is shown in the status bar, 3983 including notification icons, connectivity icons, battery status, clock, etc.\n 3984 2) If the device under test (DUT) has a status bar: the status bar can\'t be expanded. 3985 That is, the \'swipe-down\' gesture doesn\'t work for the status bar.\n 3986 3) The software Home button is hidden.\n 3987 4) If the device under test (DUT) supports Overview: the software Overview button is 3988 hidden and the Overview gesture (swipe-up) does not work.\n 3989 5) Long-press the power button. The power button menu, which usually shows the power-off 3990 button, etc., isn\'t shown.\n 3991 6) Press the power button to turn off the screen, and press it again to turn the screen 3992 back on. Lock screen shouldn\'t be shown.\n 3993 7) The assistant gesture isn\'t available.\n\n 3994 </string> 3995 <string name="device_owner_lock_task_ui_system_info_test">Enable system info</string> 3996 <string name="device_owner_lock_task_ui_system_info_test_info"> 3997 Press the button below to enable system info. Observe the system info area of the status 3998 bar is now enabled. This includes the clock, connectivity info, battery info, etc.\n\n 3999 The rest of the UI restrictions should still apply:\n 4000 1) If the device under test (DUT) has a status bar: notification icons are still hidden 4001 on the status bar.\n 4002 2) If the device under test (DUT) has a status bar: the status bar can\'t be expanded. 4003 That is, the \'swipe-down\' gesture doesn\'t work for the status bar.\n 4004 3) The software Home button is hidden.\n 4005 4) If the device under test (DUT) supports Overview: the software Overview button is 4006 hidden and the Overview gesture (swipe-up) does not work.\n 4007 5) Long-press the power button. The power button menu, which usually shows the power-off 4008 button, etc., isn\'t shown.\n 4009 6) Press the power button to turn off the screen, and press it again to turn the screen 4010 back on. Lock screen shouldn\'t be shown.\n 4011 7) The assistant gesture isn\'t available.\n\n 4012 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 4013 </string> 4014 <string name="device_owner_lock_task_ui_notifications_test">Enable notifications</string> 4015 <string name="device_owner_lock_task_ui_notifications_test_info"> 4016 Press the button below to enable notifications. Observe the notification icons on the 4017 status bar are now enabled and the Home button is shown. The status bar can also be 4018 expanded to show the notifications. However, all Settings UI should remain invisible, 4019 including Quick Settings and any link to the Settings app.\n\n 4020 The rest of the UI restrictions should still apply:\n 4021 1) If the device under test (DUT) has a status bar: system info area is still hidden on 4022 the status bar.\n 4023 2) If the device under test (DUT) supports Overview: the software Overview button is 4024 hidden and the Overview gesture (swipe-up) does not work.\n 4025 3) Holding the Home button and swiping to the right does not bring up other tasks.\n 4026 4) Long-press the power button. The power button menu, which usually shows the power-off 4027 button, etc., isn\'t shown.\n 4028 5) Press the power button to turn off the screen, and press it again to turn the screen 4029 back on. Lock screen shouldn\'t be shown.\n 4030 6) The assistant gesture isn\'t available.\n\n 4031 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 4032 </string> 4033 <string name="device_owner_lock_task_ui_home_test">Enable Home button</string> 4034 <string name="device_owner_lock_task_ui_home_test_info"> 4035 Press the button below to enable the Home button. Observe the Home button is now 4036 enabled.\n\n 4037 The rest of the UI restrictions should still apply:\n 4038 1) If the device under test (DUT) has a status bar: nothing is shown in the status bar, 4039 including notification icons, connectivity icons, battery status, clock, etc.\n 4040 2) If the device under test (DUT) has a status bar: the status bar can\'t be expanded. 4041 That is, the \'swipe-down\' gesture doesn\'t work for the status bar.\n 4042 3) If the device under test (DUT) supports Overview: the software Overview button is 4043 hidden and the Overview gesture (swipe-up) does not work.\n 4044 4) Holding the Home button and swiping to the right does not bring up other tasks.\n 4045 5) Long-press the power button. The power button menu, which usually shows the power-off 4046 button, etc., isn\'t shown.\n 4047 6) Press the power button to turn off the screen, and press it again to turn the screen 4048 back on. Lock screen shouldn\'t be shown.\n 4049 7) The assistant gesture isn\'t available.\n\n 4050 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 4051 </string> 4052 <string name="device_owner_lock_task_ui_recents_test">Enable Overview button</string> 4053 <string name="device_owner_lock_task_ui_recents_test_info"> 4054 If the device under test (DUT) does not support Overview: mark this test as \'pass\'.\n 4055 Otherwise:\n 4056 Press the button below to enable the Overview button. Observe the Home button is now 4057 enabled. Press the Overview button or perform the Overview gesture 4058 (swipe up) and verify the Overview view can be opened.\n\n 4059 The rest of the UI restrictions should still apply:\n 4060 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 4061 battery status, clock, etc.\n 4062 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 4063 for the status bar.\n 4064 3) Long-press the power button. The power button menu, which usually shows the power-off 4065 button, etc., isn\'t shown.\n 4066 4) Press the power button to turn off the screen, and press it again to turn the screen 4067 back on. Lock screen shouldn\'t be shown.\n 4068 5) The assistant gesture isn\'t available.\n\n 4069 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 4070 </string> 4071 <string name="device_owner_lock_task_ui_global_actions_test">Enable global actions</string> 4072 <string name="device_owner_lock_task_ui_global_actions_test_info"> 4073 If the device under test (DUT) does not support global actions: mark this 4074 test as \'pass\'.\n 4075 Otherwise:\n 4076 Press the button below to enable global actions (a.k.a. power button menu). Long-press 4077 the power button and verify a menu containing power-off and restart buttons is shown. 4078 This menu can\'t contain any UI that allows the user to change system settings (such as 4079 airplane mode switch) or access the Settings app.\n\n 4080 The rest of the UI restrictions should still apply:\n 4081 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 4082 battery status, clock, etc.\n 4083 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 4084 for the status bar.\n 4085 3) The software Home button is hidden.\n 4086 4) The software Overview button is hidden and the Overview gesture (swipe-up) does not 4087 work.\n 4088 5) Press the power button to turn off the screen, and press it again to turn the screen 4089 back on. Lock screen shouldn\'t be shown.\n 4090 6) The assistant gesture isn\'t available.\n\n 4091 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 4092 </string> 4093 <string name="device_owner_lock_task_ui_keyguard_test">Enable keyguard</string> 4094 <string name="device_owner_lock_task_ui_keyguard_test_info"> 4095 Press the button below to enable keyguard. Press the power button to turn off the screen 4096 and press it again to turn the screen back on. Verify that the lock screen is shown.\n\n 4097 The rest of the UI restrictions should still apply, both on the lock screen and after 4098 the lock screen is dismissed:\n 4099 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 4100 battery status, clock, etc.\n 4101 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 4102 for the status bar, even on the lock screen.\n 4103 3) The software Home button is hidden.\n 4104 4) The software Overview button is hidden and the Overview gesture (swipe-up) does not 4105 work.\n 4106 5) Long-press the power button. The power button menu, which usually shows the power-off 4107 button, etc., isn\'t shown.\n 4108 6) The assistant gesture isn\'t available.\n\n 4109 Mark the test as \'pass\' only if ALL of the above requirements are met. 4110 </string> 4111 <string name="device_owner_lock_task_ui_stop_lock_task_test">Stop LockTask mode</string> 4112 <string name="device_owner_lock_task_ui_stop_lock_task_test_info"> 4113 Press the button below to exit LockTask mode.\n\n 4114 Observe that the UI has returned to the normal, unrestricted state, and is no longer 4115 subject to any LockTask restriction.\n\n 4116 Mark the test as \'pass\' or \'fail\' accordingly. 4117 </string> 4118 <string name="device_owner_lockscreen_secure">Please remove lockscreen password</string> 4119 <string name="device_profile_owner_permission_lockdown_test">Permissions lockdown</string> 4120 <string name="device_profile_owner_permission_lockdown_test_instructions"> 4121 Select each of the three grant states for the permission shown below in turn.\n 4122 Now open application settings, select Permissions, and verify if the following behavior is observed.\n 4123 <b>Grant:</b> Permission is granted to the app and cannot be changed through the settings UI. A support message is available through an accessible mechanism, such as by attempting to change it or via an information button.\n 4124 <b>Let user decide:</b> Permission state can be changed through the settings UI.\n 4125 <b>Deny:</b> Permission is denied to the app and cannot be changed through the settings UI. A support message is available through an accessible mechanism, such as by attempting to change it or via an information button.\n 4126 Please mark the test accordingly. 4127 </string> 4128 <string name="device_owner_permission_lockdown_test_info"> 4129 This test checks if the permissions state in settings UI is locked down according to the state set by the device owner. 4130 </string> 4131 <string name="device_owner_disallow_usb_file_transfer_test">Disallow USB file transfer</string> 4132 <string name="device_owner_disallow_usb_file_transfer_test_info"> 4133 Please press below button to set the \"disallow USB file transfer\" restriction.\n 4134 If a USB notification appears, open the notification and check that the 4135 \"Transfer files (MTP)\" and \"Transfer photos (PTP)\" options either are not displayed, 4136 or they trigger a support message when trying to select them.\n 4137 Check if you can mount the device as a USB drive on your desktop computer. The test is 4138 successful if you cannot mount the device, and files from your phone cannot be 4139 downloaded through USB.\n 4140 Please mark the test accordingly. 4141 </string> 4142 <string name="device_owner_set_user_icon">Setting the user icon</string> 4143 <string name="device_owner_set_user_icon_instruction"> 4144 This test verifies that the user icon can be set by the device owner, depending on whether the user restriction is set or not.\n 4145 1. Press the \"Set user icon 1\" button.\n 4146 2. Press the \"Go\" button to go to Settings.\n 4147 3. If there is no \"users\" section, mark this test as passed.\n 4148 4. If the icon of the user \"owner\" is not \"1\", mark this test as failed.\n 4149 5. Press the \"Disallow set user icon\" button.\n 4150 6. Press the \"Set user icon 2\" button.\n 4151 7. Press the \"Go\" button to go to Settings. Verify that the icon can\'t be changed manually.\n 4152 8. Check that the icon of the user \"owner\" is \"2\", and mark this test accordingly. 4153 </string> 4154 <string name="device_owner_set_user_icon_button">Set user icon 1</string> 4155 <string name="device_owner_set_user_icon2_button">Set user icon 2</string> 4156 4157 <string name="profile_owner_permission_lockdown_test_info"> 4158 <b> 4159 Before proceeding, check if com.android.cts.permissionapp (aka CtsPermissionApp) is installed in work profile by going to Settings > Apps. If not, please install the app before proceeding.\n\n 4160 </b> 4161 This test checks if the permissions state in settings UI is locked down correctly depending on the state set by the profile owner. 4162 </string> 4163 <string name="package_not_found">You must install %s (aka CtsPermissionApp).</string> 4164 <string name="permission_allow">Grant</string> 4165 <string name="permission_default">Let user decide</string> 4166 <string name="permission_deny">Deny</string> 4167 <string name="not_profile_owner">%s is not profile owner.</string> 4168 <string name="not_device_owner">%s is not device owner.</string> 4169 <string name="activity_not_found">No activity found to handle intent: %s</string> 4170 <string name="open_settings_button_label">Open Application Settings</string> 4171 <string name="finish_button_label">Finish</string> 4172 <string name="device_owner_device_admin_visible">Device administrator settings</string> 4173 <string name="device_owner_device_admin_visible_info"> 4174 Please press the Go button to open the Security page in Settings. 4175 Navigate to Device administrators and confirm that:\n 4176 \n 4177 - \"CTS Verifier\" exists and is activated.\n 4178 - \"CTS Verifier\" cannot be disabled.\n 4179 \n 4180 Use the Back button to return to this page. 4181 </string> 4182 <string name="device_owner_disallow_config_bt">Disallow configuring Bluetooth</string> 4183 <string name="device_owner_disallow_config_bt_info"> 4184 Please press the Set restriction button to set the user restriction. 4185 Then press Go, you should either see (a) the Bluetooth settings page or (b) trigger a support message directly.\n 4186 In the case of (a), confirm that:\n 4187 - You cannot view Bluetooth devices in range.\n 4188 - Trying to edit, add or remove any already paired devices triggers a support message.\n 4189 \n 4190 In the case of (b) this step is successful.\n 4191 \n 4192 Use the Back button to return to this page. 4193 </string> 4194 <string name="device_owner_disallow_config_wifi">Disallow configuring WiFi</string> 4195 <string name="device_owner_disallow_config_wifi_info"> 4196 Please press the Set restriction button to set the user restriction. 4197 Then press Go to open the WiFi page in Settings. 4198 Confirm that:\n\n 4199 - You cannot view WiFi networks in range.\n 4200 - Trying to edit, add or remove any existing WiFi configs triggers a support message.\n 4201 \n 4202 Use the Back button to return to this page. 4203 </string> 4204 <string name="device_owner_disallow_add_wifi_config">Disallow adding WiFi config</string> 4205 <string name="device_owner_disallow_add_wifi_config_info"> 4206 Please press the Set restriction button to set the user restriction. 4207 Then press Go to open the WiFi page in Settings. 4208 Confirm that:\n\n 4209 - You cannot add a new WiFi configuration.\n 4210 - Tapping on the disabled network shows a dialog explaining the admin restriction.\n 4211 \n 4212 Use the Back button to return to this page. 4213 </string> 4214 <string name="device_owner_disallow_sharing_admin_configure_wifi">Disallow sharing admin configured WiFi config</string> 4215 <string name="device_owner_disallow_sharing_admin_configure_wifi_info"> 4216 Please press the Set restriction button to set the user restriction. 4217 Then press Go to open the WiFi page in Settings. 4218 Confirm that:\n\n 4219 - You cannot share an admin configured WiFi config.\n 4220 - Sharing option is disabled in Settings.\n 4221 \n 4222 Use the Back button to return to this page.\n 4223 NOTE: If the device does not support Wi-Fi sharing please skip this test and mark it as passing. 4224 </string> 4225 <string name="device_owner_wifi_security_level_restriction">Set WiFi security level restriction</string> 4226 <string name="device_owner_wifi_security_level_restriction_info"> 4227 This test verifies that minimum WiFi security level restriction can be set by the device owner. 4228 The levels below are listed in an increasing order of security.\n 4229 1. Connect to any network.\n 4230 2. Pick a security level greater than the currently connected network (if unsure pick Enterprise 192).\n 4231 3. Verify that current network gets disconnected.\n 4232 4. Press Go to open the WiFi page in Settings.\n 4233 5. Confirm that you cannot connect to any network that does not meet the security level restriction.\n 4234 6. Use the Back button to return to this page.\n 4235 7. Set the security level to Open to remove the restriction.\n 4236 8. Press Go to open the WiFi page in Settings.\n 4237 9. Confirm that you can connect to any network. 4238 </string> 4239 <string name="set_wifi_security_level_open">Set WiFi security level to Open</string> 4240 <string name="set_wifi_security_level_personal">Set WiFi security level to Personal</string> 4241 <string name="set_wifi_security_level_enterprise_eap">Set WiFi security level to Enterprise EAP</string> 4242 <string name="set_wifi_security_level_enterprise_192">Set WiFi security level to Enterprise 192</string> 4243 <string name="device_owner_ssid_restriction">Set WiFi SSID restriction</string> 4244 <string name="device_owner_ssid_restriction_info"> 4245 This test verifies that WiFi SSID restriction can be set by the device owner.\n 4246 1. Connect to any network.\n 4247 2. Enter the SSID of the network you are currently connected to.\n 4248 3. Set the SSID denylist.\n 4249 4. Verify that current network gets disconnected.\n 4250 5. Press Go to open the WiFi page in Settings.\n 4251 6. Confirm that only the SSID from the denylist is restricted from connection.\n 4252 7. Use the Back button to return to this page.\n 4253 8. Enter the same SSID and set the SSID allowlist.\n 4254 9. Press Go to open the WiFi page in Settings.\n 4255 10. Confirm that you can only connect to the SSID from the allowlist.\n 4256 11. Use the Back button to return to this page.\n 4257 12. Leave the SSID field blank and set the allowlist to remove restriction.\n 4258 13. Press Go to open the WiFi page in Settings.\n 4259 14. Confirm that you can connect to any network. 4260 </string> 4261 <string name="device_owner_ssid_restriction_hint">Enter SSID</string> 4262 <string name="device_owner_set_ssid_allowlist_button">Set SSID allowlist</string> 4263 <string name="device_owner_set_ssid_denylist_button">Set SSID denylist</string> 4264 <string name="device_owner_ssid_restriction_removing_toast">Removing SSID restriction</string> 4265 <string name="device_owner_disallow_ambient_display">Disallow ambient display</string> 4266 <string name="device_owner_disallow_ambient_display_info"> 4267 Please press the Set restriction button to set the user restriction. 4268 Then press Go to open the Display page in Settings. 4269 Mark this test as passed if one of the following:\n\n 4270 - There is no ambient display setting in Display Settings.\n 4271 - Ambient display setting is disabled with an info icon on it. Clicking on it triggers a support dialog.\n 4272 \n 4273 Use the Back button to return to this page. 4274 </string> 4275 <string name="device_owner_disallow_data_roaming">Disallow data roaming</string> 4276 <string name="device_owner_disallow_data_roaming_info"> 4277 Device should have a sim card to perform this test. 4278 Please press the Set restriction button to set the user restriction. 4279 Then press Go to open the Mobile network page in Settings. 4280 Confirm that:\n\n 4281 - Data roaming is disabled.\n 4282 - Enabling data roaming is not possible and triggers a support message.\n\n 4283 Use the Back button to return to this page. 4284 </string> 4285 <string name="device_owner_disallow_factory_reset">Disallow factory reset</string> 4286 <string name="device_owner_disallow_factory_reset_info"> 4287 Please press the Set button to set the user restriction.\n 4288 1. Go to the factory reset settings. It is often located in \"Backup & reset\" settings.\n 4289 Confirm that:\n 4290 - Factory data reset is disabled.\n 4291 - Pressing factory data reset is not possible and triggers a support message.\n\n 4292 2. Go to OEM unlocking settings, if this device has this Settings option. It is often located under \"Developer options\".\n 4293 Confirm that:\n 4294 - Oem Unlocking is disabled.\n 4295 - Enabling Oem unlocking is not possible and triggers a support message.\n\n 4296 Return back to this page. 4297 </string> 4298 <string name="device_owner_user_restriction_set">Set restriction</string> 4299 <string name="device_owner_user_restriction_unset">Clear restriction (before leaving test)</string> 4300 <string name="device_owner_settings_go">Go</string> 4301 4302 <string name="device_owner_vpn_connection"> 4303 VPN connection has been established.\n 4304 This is not as expected.\n 4305 Mark this test as failed.\n 4306 </string> 4307 <string name="device_owner_vpn_connection_close_failed"> 4308 Established vpn connection cannot be closed.\n 4309 This is not as expected.\n 4310 Mark this test as failed.\n 4311 </string> 4312 <string name="device_owner_no_vpn_connection"> 4313 Cannot establish a VPN connection.\n 4314 This was expected.\n 4315 Mark this test as passed.\n 4316 </string> 4317 <string name="device_owner_vpn_test">Check VPN</string> 4318 <string name="device_owner_vpn_info_default">VPN test message</string> 4319 4320 <string name="device_owner_disallow_config_vpn">Disallow configuring VPN</string> 4321 <string name="device_owner_disallow_config_vpn_info"> 4322 Please press the Set VPN restriction button to set the VPN restriction. 4323 Perform tests in order. Mark test as passed if both test cases pass\n\n 4324 1. Press Go to attempt to open the VPN settings page.\n 4325 You should either see (a) the VPN settings page or (b) that the Intent 4326 android.settings.VPN_SETTINGS fails to resolve.\n 4327 In the case of (a), confirm that:\n 4328 - Trying to perform any of the above actions will trigger a support message.\n 4329 In the case of (b) this step is successful.\n\n 4330 2. Press Check VPN to check programmatic Vpn test.\n 4331 - Check Vpn setup is not allowed\n 4332 - If prompted to allow a VPN connection, press OK.\n\n 4333 Use the Back button to return to this page. 4334 </string> 4335 <string name="device_owner_user_vpn_restriction_set">Set VPN restriction</string> 4336 4337 <!-- Strings for DeviceOwnerBugreportTest --> 4338 <string name="device_owner_requesting_bugreport_tests">Device Owner Requesting Bugreport Tests</string> 4339 <string name="device_owner_requesting_bugreport_category">Device Owner Requesting Bugreport Tests</string> 4340 <string name="device_owner_requesting_bugreport_tests_info"> 4341 The device owner requesting bugreport tests verify that a bugreport can be requested on a corporate owned device.\n 4342 Press below button first, follow steps described in the dialog that pops up, 4343 then proceed to the test cases.\n 4344 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 4345 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 4346 be run last so that it does not interfere with other tests. 4347 </string> 4348 <string name="device_owner_request_bugreport">Request bugreport</string> 4349 <string name="bugreport_sharing_declined">Bugreport sharing declined</string> 4350 <string name="bugreport_shared_successfully">Bugreport shared successfully</string> 4351 <string name="bugreport_already_in_progress">Bugreport is already being collected on this device</string> 4352 <string name="bugreport_failed_completing">Bugreport collection operation failed</string> 4353 <string name="device_owner_bugreport_sharing_declined_while_being_taken">Sharing of requested bugreport declined while being taken</string> 4354 <string name="device_owner_bugreport_sharing_declined_while_being_taken_info"> 4355 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 4356 Open the notifications panel and verify that:\n 4357 \n 4358 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 4359 \n 4360 Press the \"Request bugreport\" button again to try to invoke a second bugreport sharing operation. 4361 Open the notifications panel and verify that:\n 4362 \n 4363 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport is already being collected on this device\" is present. Dismiss that notification.\n 4364 - 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 4365 \n 4366 Tap the \"DECLINE\" button and verify that:\n 4367 \n 4368 - \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n 4369 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport sharing declined\" is present.\n 4370 \n 4371 Dismiss the notifications and mark test as passed or failed. 4372 </string> 4373 <string name="device_owner_bugreport_sharing_accepted_while_being_taken">Sharing of requested bugreport accepted while being taken</string> 4374 <string name="device_owner_bugreport_sharing_accepted_while_being_taken_info"> 4375 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 4376 Open the notifications panel and verify that:\n 4377 \n 4378 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 4379 - 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 4380 \n 4381 Tap the \"SHARE\" button and verify that:\n 4382 \n 4383 - \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n 4384 - Notification titled \"Sharing bugreport...\" with an indefinite progress bar is present.\n 4385 - 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 4386 \n 4387 Dismiss the notifications and mark test as passed or failed. 4388 </string> 4389 <string name="device_owner_bugreport_sharing_declined_after_having_been_taken">Sharing of requested bugreport declined after having been taken</string> 4390 <string name="device_owner_bugreport_sharing_declined_after_having_been_taken_info"> 4391 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 4392 Open the notifications panel and verify that:\n 4393 \n 4394 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 4395 \n 4396 Wait for a few minutes (time necessary for bugreport to be collected) and verify that:\n 4397 \n 4398 - \"Taking bugreport...\" notification with an indefinite progress bar is dismissed.\n 4399 - 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 4400 \n 4401 Tap the \"DECLINE\" button and verify that:\n 4402 \n 4403 - Notification titled \"Share bug report?\" is dismissed.\n 4404 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport sharing declined\" is present.\n 4405 \n 4406 Dismiss the notifications and mark test as passed or failed. 4407 </string> 4408 <string name="device_owner_bugreport_sharing_accepted_after_having_been_taken">Sharing of requested bugreport accepted after having been taken</string> 4409 <string name="device_owner_bugreport_sharing_accepted_after_having_been_taken_info"> 4410 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 4411 Open the notifications panel and verify that:\n 4412 \n 4413 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 4414 \n 4415 Wait for a few minutes (time necessary for bugreport to be collected) and verify that:\n 4416 \n 4417 - \"Taking bugreport...\" notification with an indefinite progress bar is dismissed.\n 4418 - 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 4419 \n 4420 Tap the \"SHARE\" button and verify that:\n 4421 \n 4422 - Notification titled \"Share bug report?\" is dismissed.\n 4423 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport shared successfully\" is present.\n 4424 \n 4425 Dismiss the notifications and mark test as passed or failed. 4426 </string> 4427 4428 <!-- Strings used for policy transparency test --> 4429 <string name="device_profile_owner_policy_transparency_test">Policy transparency test</string> 4430 <string name="device_profile_owner_policy_transparency_test_info"> 4431 This test checks that if an admin has enforced a policy, we let the user know about this.\nSet the short support message before proceeding with the tests. 4432 </string> 4433 <string name="policy_transparency_open_settings_label">Open settings</string> 4434 <string name="policy_transparency_short_support_msg_label">Set short support message</string> 4435 <string name="policy_transparency_long_support_msg_label">Set long support message</string> 4436 <string name="policy_transparency_set_msg">Set message</string> 4437 <string name="policy_transparency_clear_msg">Clear message</string> 4438 <string name="policy_transparency_set_default_msg">Set default message</string> 4439 <string name="policy_transparency_default_short_msg"> 4440 This action is disabled by your administrator. Contact someone@example.com for support. 4441 </string> 4442 <string name="policy_transparency_default_long_msg"> 4443 This profile or device is managed by CtsVerifier. You can contact tech 4444 support on:\n\n 4445 America: +1 555-0100\n\n 4446 APAC: +1 555-0100\n\n 4447 Europe: +1 555-0100\n\n 4448 Email: someone@example.com 4449 </string> 4450 <string name="policy_transparency_update_button_label">Update</string> 4451 <string name="test_input_method_label">Test input method</string> 4452 <string name="test_accessibility_service_label">Test accessibility service</string> 4453 <string name="policy_transparency_test_instructions"> 4454 1. <xliff:g id="set_step" example="Set policy by turning the switch on">%1$s</xliff:g>\n 4455 2. Open Settings app by clicking the "Open settings" button below. Note that this will open the personal Settings app. If this device has the work settings in a different app or screen, then navigate there, ignoring the button if necessary.\n 4456 3. Verify that performing the following action will trigger a support dialog:\n 4457 <xliff:g id="user_action" example="Adding an account">%2$s</xliff:g>.<xliff:g id="exception_node" example="NOTE: if the device doesn't support the action...">%3$s</xliff:g>\n 4458 4. Verify that the support dialog displays the short support message set earlier.\n 4459 </string> 4460 <string name="optional_policy_transparency_test_note">\n\t<b>NOTE</b>: if the device doesn\'t support this action please skip this test and mark it as passing.</string> 4461 <string name="user_restriction_set_step"> 4462 Set \'%s\' user restriction by turning on the switch below. 4463 </string> 4464 <string name="disallow_add_user">Disallow add user</string> 4465 <string name="disallow_add_user_action">Accessing the multiple users settings page, or if the device allows access to the page, then attempting to add a new user </string> 4466 <string name="disallow_adjust_volume">Disallow adjust volume</string> 4467 <string name="disallow_adjust_volume_action">Adjusting the volume\n 4468 NOTE: If the device does not support volume adjustment in Settings app please skip this test and mark it as passing.\n</string> 4469 <string name="disallow_config_date_time">Disallow config date time</string> 4470 <string name="disallow_config_date_time_action">Configuring auto time, time, auto date or date</string> 4471 <string name="disallow_config_location">Disallow config location</string> 4472 <string name="disallow_config_location_action">Enabling or disabling location, \'Bluetooth Scanning\' or \'WiFi Scanning\' in settings or quick settings</string> 4473 <string name="disallow_airplane_mode">Disallow airplane mode</string> 4474 <string name="disallow_airplane_mode_action">Toggling airplane mode switch bar or changing airplane mode state in quick settings</string> 4475 <string name="disallow_config_screen_timeout">Disallow config screen timeout</string> 4476 <string name="disallow_config_screen_timeout_action">Configuring sleep options in Display settings</string> 4477 <string name="disallow_config_brightness">Disallow config brightness</string> 4478 <string name="disallow_config_brightness_action">Configuring brightness level or adaptive brightness in Display settings, or toggling brightness slider in quick settings</string> 4479 <string name="disallow_apps_control">Disallow controlling apps</string> 4480 <string name="disallow_apps_control_action">DISABLE/UNINSTALL/FORCE STOP-ing any app in the managed device/profile other than CtsVerifier</string> 4481 <string name="disallow_config_cell_broadcasts">Disallow config cell broadcasts</string> 4482 <string name="disallow_config_cell_broadcasts_action">Configuring emergency alerts(cell broadcasts)</string> 4483 <string name="disallow_config_credentials">Disallow config credentials</string> 4484 <string name="disallow_config_credentials_action">Configuring user credentials</string> 4485 <string name="disallow_config_mobile_networks">Disallow config mobile networks</string> 4486 <string name="disallow_config_mobile_networks_action">Configuring mobile networks</string> 4487 <string name="disallow_config_tethering">Disallow config tethering</string> 4488 <string name="disallow_config_tethering_action"> 4489 Configuring tethering and portable hotspots.\n 4490 NOTE: If the device does not support tethering please skip this test and mark it as passing.\n 4491 </string> 4492 <string name="disallow_config_wifi">Disallow config Wi-Fi</string> 4493 <string name="disallow_config_wifi_action">Modifying Wi-Fi configuration</string> 4494 <string name="disallow_debugging_features">Disallow debugging features</string> 4495 <string name="disallow_debugging_features_action">Enabling developer options</string> 4496 <string name="disallow_factory_reset">Disallow factory reset</string> 4497 <string name="disallow_factory_reset_action">Factory resetting the device</string> 4498 <string name="disallow_fun">Disallow fun</string> 4499 <string name="disallow_fun_action">Opening android easter egg game by tapping repeatedly on the \'Android version\' option</string> 4500 <string name="disallow_install_unknown_sources">Disallow install unknown sources</string> 4501 <string name="disallow_install_unknown_sources_action">Enabling \'Cts Verifier\' to install apps</string> 4502 <string name="disallow_install_unknown_sources_globally">Disallow install unknown sources globally</string> 4503 <string name="disallow_install_unknown_sources_globally_action">Enabling \'Cts Verifier\' to install apps device-wide</string> 4504 <string name="disallow_modify_accounts">Disallow modify accounts</string> 4505 <string name="disallow_modify_accounts_action">Adding an account, and also removing an account (after you have previously added one)</string> 4506 <string name="disallow_network_reset">Disallow network reset</string> 4507 <string name="disallow_network_reset_action">Resetting network settings\n 4508 NOTE: If the device does not support network reset please skip this test and mark it as passing.\n</string> 4509 <string name="disallow_outgoing_beam">Disallow outgoing beam</string> 4510 <string name="disallow_outgoing_beam_action">Switching on android beam</string> 4511 <string name="disallow_remove_user">Disallow remove user</string> 4512 <string name="check_new_user_disclaimer">Check new user disclaimer</string> 4513 <string name="check_new_user_disclaimer_info"> 4514 Please do the following: \n\n 4515 1. Check persistent notification for managed device \n\n 4516 a). Open the notification UI, verify that there is a notification saying the device is managed.\n 4517 b). Tap the notification\n 4518 c). It should show a dialog explaining the device is managed and asking the user to accept \n 4519 d). Don\'t accept initially and tap outside the dialog \n 4520 e). Open the notification UI again, verify that the managed device notification is still shown \n 4521 \n 4522 f). Click \"Set Org\", and open the notification UI again, verify that the organization name 4523 \"Foo, Inc\" is shown on the dialog \n 4524 \n\n 4525 2. Check adding account is restricted\n\n 4526 a) Click \"Go\" to launch the \"Profiles & accounts\" setting \n 4527 b) navigate to \"Add account\" \n 4528 \n 4529 Expected: \n 4530 - \"Add account\" is disabled \n 4531 - Click the button will launch the new user disclaimer dialog\n 4532 \n 4533 c) Click accept button\n 4534 \n 4535 Expected: \n 4536 - the screen will be dismissed \n 4537 - \"Add account\" will be enabled\n 4538 - Click the button will take user to the screen to add account \n 4539 </string> 4540 <string name="device_owner_disallow_remove_user_info"> 4541 Please press \'Create uninitialized user\' to create a user that is not set up. Then press the 4542 \'Set restriction\' button to set the user restriction. 4543 Then press \'Go\' to open \'Multiple users\' setting. \n 4544 Click the managed user to open settings.\n\n 4545 4546 Mark this test as passed if:\n\n 4547 - \"Delete User\" is disabled.\n 4548 - Tapping \"Delete user\" shows an \"Action not allowed\" dialog.\n 4549 \n 4550 Use the Back button to return to this page. 4551 </string> 4552 <string name="managed_user_disallow_remove_user_info"> 4553 Please press the \'Set restriction\' button to set the user restriction. 4554 Then press \'Go\' to open \'Multiple users\' setting. \n\n 4555 4556 Mark this test as passed if all of the following conditions are met:\n\n 4557 - The \"Delete managed user from this device\" option in the overflow menu is disabled\n 4558 - Clicking \"Delete managed user from this device\" in the overflow menu results in an \"Action not allowed\" dialog.\n 4559 \n 4560 Use the Back button to return to this page. 4561 </string> 4562 <string name="device_owner_disallow_remove_user_create_user">Create uninitialized user</string> 4563 <string name="device_owner_remove_secondary_user">Remove uninitialized user</string> 4564 <string name="disallow_remove_managed_profile">Disallow remove managed profile</string> 4565 <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> 4566 <string name="disallow_share_location">Disallow share location</string> 4567 <string name="disallow_share_location_action">Turning on location sharing</string> 4568 <string name="disallow_set_user_icon">Disallow set user icon</string> 4569 <string name="disallow_uninstall_apps">Disallow uninstall apps</string> 4570 <string name="disallow_uninstall_apps_action"> 4571 a. If testing in work profile: uninstall applications from the work profile (badged applications) other than CtsVerifier and system apps. \n 4572 b. Otherwise: uninstall applications other than CtsVerifier and system apps 4573 </string> 4574 <string name="disallow_unified_challenge">Disallow unified challenge</string> 4575 <string name="disallow_unified_challenge_action">Setting one lock for both personal and work profiles. IMPORTANT: Separate work lock should be set prior to this test in Set work lock test</string> 4576 <string name="disallow_keyguard_unredacted_notifications">Disallow lockscreen unredacted notification</string> 4577 <string name="disallow_keyguard_unredacted_notifications_set_step">Disallow unredacted notifications when device is locked by turning on the switch below</string> 4578 <string name="disallow_keyguard_unredacted_notifications_action">Selecting show all notification content when device is locked</string> 4579 <string name="disallow_keyguard_unredacted_notifications_widget_label">@string/disallow_keyguard_unredacted_notifications</string> 4580 <string name="set_auto_time_required">Set auto (network) time required</string> 4581 <string name="auto_time_required_set_step">Set auto time required policy by turning on the switch below</string> 4582 <string name="set_auto_time_required_action">Modifying date and time</string> 4583 <string name="set_auto_time_required_widget_label">@string/set_auto_time_required</string> 4584 <string name="set_lock_screen_info">Set lock screen info</string> 4585 <string name="lock_screen_info_set_step">Select a lock screen info by setting a non-empty message in the edittext below.</string> 4586 <string name="set_lock_screen_info_action">Modifying lock screen message</string> 4587 <string name="set_lock_screen_info_widget_label">@string/set_lock_screen_info</string> 4588 <string name="set_maximum_time_to_lock">Set maximum time to lock</string> 4589 <string name="maximum_time_to_lock_set_step"> 4590 Select a non-zero maximum time to lock value by setting a value in the edittext box below. 4591 </string> 4592 <string name="set_maximum_time_to_lock_action">Selecting maximum time to lock greater than the set value below</string> 4593 <string name="set_maximum_time_to_lock_widget_label">Set maximum time to lock (in Sec):</string> 4594 <string name="set_permitted_accessibility_services">Set permitted accessibility services</string> 4595 <string name="permitted_accessibility_services_set_step"> 4596 Check that \'Test Accessibility service\' is not enabled in Settings and disallow \'Test Accessibility service\' from permitted accessibility services by turning on 4597 the switch below. 4598 </string> 4599 <string name="set_permitted_accessibility_services_action"> 4600 Enabling \'Test Accessibility service\' in the list of accessibility services 4601 </string> 4602 <string name="set_permitted_accessibility_services_widget_label"> 4603 Allow only system accessibility services: 4604 </string> 4605 <string name="set_permitted_input_methods">Set permitted input methods</string> 4606 <string name="permitted_input_methods_set_step"> 4607 Check that \'Test Input method\', along with all other non-system apps, are not enabled in Settings for the managed profile (they may be enabled for the primary profile). Then disallow \'Test Input method\' from permitted input methods by turning on the switch below. 4608 </string> 4609 <string name="set_permitted_input_methods_action"> 4610 Enabling \'Test Input method\' in the list of input methods (make sure you are enabling it for the managed profile, not primary profile) 4611 </string> 4612 <string name="set_permitted_input_methods_widget_label"> 4613 Allow only system input methods: 4614 </string> 4615 4616 <!-- Strings used for enterprise privacy tests --> 4617 <string name="enterprise_privacy_test">Managed device info tests</string> 4618 <string name="enterprise_privacy_page">Managed device info page</string> 4619 <string name="enterprise_privacy_page_info"> 4620 Please press the Go button to open Settings. Verify that:\n 4621 1) One of the Settings screens contains an entry for managed device information.\n 4622 2) Tapping that entry opens a screen.\n 4623 3) In this screen, at a minimum, you are told your organization can:\n 4624 * Change settings on this device.\n 4625 * See data associated with your work account.\n 4626 * See the list of all apps on your device.\n 4627 * See usage of each app on your device.\n 4628 * Lock the device and change the password.\n 4629 * Wipe the device.\n 4630 \n 4631 Use the Back button to return to this page. 4632 </string> 4633 <string name="enterprise_privacy_open_settings">Open Settings</string> 4634 <string name="enterprise_privacy_network_logging">Retrieve traffic logs</string> 4635 <string name="enterprise_privacy_network_logging_info"> 4636 Please do the following:\n 4637 1) Press the Retrieve Traffic Logs button and record the time at which you did this.\n 4638 2) Wait one minute.\n 4639 3) Press the Open Settings button.\n 4640 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 4641 \n 4642 Use the Back button to return to this page. 4643 </string> 4644 <string name="enterprise_privacy_retrieve_network_logs">Retrieve Traffic Logs</string> 4645 <string name="enterprise_privacy_bug_report">Request bug report</string> 4646 <string name="enterprise_privacy_bug_report_info"> 4647 Please do the following:\n 4648 1) Press the Request Bug Report button and record the time at which you did this.\n 4649 2) Wait one minute.\n 4650 3) Press the Open Settings button.\n 4651 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 4652 \n 4653 Use the Back button to return to this page. 4654 </string> 4655 <string name="enterprise_privacy_request_bug_report">Request Bug Report</string> 4656 <string name="enterprise_privacy_security_logging">Retrieve security logs</string> 4657 <string name="enterprise_privacy_security_logging_info"> 4658 Please do the following:\n 4659 1) Press the Retrieve Security Logs button and record the time at which you did this.\n 4660 2) Wait one minute.\n 4661 3) Press the Open Settings button.\n 4662 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 4663 \n 4664 Use the Back button to return to this page. 4665 </string> 4666 <string name="enterprise_privacy_retrieve_security_logs">Retrieve Security Logs</string> 4667 <string name="enterprise_privacy_clear_organization">Clear Org</string> 4668 <string name="enterprise_privacy_set_organization">Set Org</string> 4669 <string name="enterprise_privacy_enterprise_installed_apps">Enterprise-installed apps</string> 4670 <string name="enterprise_privacy_enterprise_installed_apps_info"> 4671 Please do the following:\n 4672 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 4673 make NotificationBot\n 4674 2) Grant MANAGE_EXTERNAL_STORAGE by issuing the following command on the host:\n 4675 adb shell appops set com.android.cts.verifier MANAGE_EXTERNAL_STORAGE 0\n 4676 3) Upload the NotificationBot.apk to your device by issuing the following command on the host:\n 4677 adb push /path/to/NotificationBot.apk /sdcard\n 4678 4) Press the Uninstall button.\n 4679 5) Press the Open Settings button.\n 4680 6) In the screen that opens, verify that you are not told that your administrator installed any apps.\n 4681 7) Use the Back button to return to this page.\n 4682 8) Press the Install button.\n 4683 9) Press the Open Settings button.\n 4684 10) In the screen that opens, verify that you are told now that your administrator installed at least one app.\n 4685 11) Tap on that information. Verify that a list of apps installed shows.\n 4686 12) Verify that the list contains the CTS Robot app.\n 4687 13) Use the Back button to return to this page.\n 4688 14) Press the Uninstall button.\n 4689 15) Issue the following command on the host:\n 4690 adb shell rm /sdcard/NotificationBot.apk 4691 </string> 4692 <string name="enterprise_privacy_enterprise_installed_apps_info_headless_system_user"> 4693 Please do the following:\n 4694 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 4695 \tmake NotificationBot\n 4696 2) Install the NotificationBot for <b>user 0 only</b>. For example:\n 4697 \tadb install --user 0 $ANDROID_PRODUCT_OUT/testcases/NotificationBot/*/NotificationBot.apk\n 4698 3) Make sure the app is <b>not</b> installed for the current user:\n 4699 \tadb shell pm list packages --user cur |grep com.android.cts.robot || echo \'Not installed\'\n 4700 4) Press the Open Settings button.\n 4701 5) In the screen that opens, verify that you are not told that your administrator installed any apps (other than CtsVerifier itself).\n 4702 6) Use the Back button to return to this page.\n 4703 7) Press the Install button.\n 4704 8) Press the Open Settings button.\n 4705 9) In the screen that opens, verify that you are told now that your administrator installed at least one app.\n 4706 10) Tap on that information. Verify that a list of apps installed shows.\n 4707 11) Verify that the list contains the CTS Robot app.\n 4708 12) Use the Back button to return to this page.\n 4709 13) Press the Uninstall button.\n 4710 14) Issue the following command on the host:\n 4711 \tadb uninstall --user all com.android.cts.robot\n 4712 </string> 4713 <string name="enterprise_privacy_install">Install</string> 4714 <string name="enterprise_privacy_uninstall">Uninstall</string> 4715 <string name="enterprise_privacy_admin_granted_location_access">Location access permission</string> 4716 <string name="enterprise_privacy_admin_granted_location_access_info"> 4717 Please do the following:\n 4718 1) Press the Reset button.\n 4719 2) Press the Open Settings button.\n 4720 3) In the screen that opens, verify that you are not told that your administrator has granted location access to any apps.\n 4721 4) Use the Back button to return to this page.\n 4722 5) Press the Grant button.\n 4723 6) Press the Open Settings button.\n 4724 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 4725 8) Tap on that information. Verify that a list of apps which have location access shows.\n 4726 9) Verify that the list contains the CTS Verifier app.\n 4727 10) Use the Back button to return to this page.\n 4728 11) Press the Reset button. 4729 </string> 4730 <string name="enterprise_privacy_reset">Reset</string> 4731 <string name="enterprise_privacy_grant">Grant</string> 4732 <string name="enterprise_privacy_admin_granted_microphone_access">Microphone access permission</string> 4733 <string name="enterprise_privacy_admin_granted_microphone_access_info"> 4734 Please do the following:\n 4735 1) Press the Reset button.\n 4736 2) Press the Open Settings button.\n 4737 3) In the screen that opens, verify that you are not told that your administrator has granted microphone access to any apps.\n 4738 4) Use the Back button to return to this page.\n 4739 5) Press the Grant button.\n 4740 6) Press the Open Settings button.\n 4741 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 4742 8) Tap on that information. Verify that a list of apps that have microphone access shows.\n 4743 9) Verify that the list contains the CTS Verifier app.\n 4744 10) Use the Back button to return to this page.\n 4745 11) Press the Reset button. 4746 </string> 4747 <string name="enterprise_privacy_admin_granted_camera_access">Camera access permission</string> 4748 <string name="enterprise_privacy_admin_granted_camera_access_info"> 4749 Please do the following:\n 4750 1) Press the Reset button.\n 4751 2) Press the Open Settings button.\n 4752 3) In the screen that opens, verify that you are not told that your administrator has granted camera access to any apps.\n 4753 4) Use the Back button to return to this page.\n 4754 5) Press the Grant button.\n 4755 6) Press the Open Settings button.\n 4756 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 4757 8) Tap on that information. Verify that a list of apps that have camera access shows.\n 4758 9) Verify that the list contains the CTS Verifier app.\n 4759 10) Use the Back button to return to this page.\n 4760 11) Press the Reset button. 4761 </string> 4762 <string name="enterprise_privacy_default_apps">Default apps</string> 4763 <string name="enterprise_privacy_default_apps_info"> 4764 Please do the following:\n 4765 1) Press the Reset button.\n 4766 2) Press the Open Settings button.\n 4767 3) In the screen that opens, verify that you are not told that your administrator set any default apps.\n 4768 4) Use the Back button to return to this page.\n 4769 5) Press the Set Default Apps button.\n 4770 6) Press the Open Settings button.\n 4771 7) In the screen that opens, verify that you are now told that your administrator has set 6 default apps.\n 4772 8) Tap on that information. Verify that a list of default apps shows, with 6 elements in it.\n 4773 9) Verify that each element shows the CTS Verifier is the default app.\n 4774 10) Use the Back button to return to this page.\n 4775 11) Press the Reset button. 4776 </string> 4777 <string name="enterprise_privacy_set_default_apps">Set Default Apps</string> 4778 <string name="enterprise_privacy_default_ime">Default keyboard</string> 4779 <string name="enterprise_privacy_default_ime_info"> 4780 Please do the following:\n 4781 1) Press the Open Settings button.\n 4782 2) In the screen that opens, verify that you are not told the default keyboard has been set.\n 4783 3) Use the Back button to return to this page.\n 4784 4) Press the Set Keyboard button to set the default keyboard.\n 4785 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 4786 6) Press the Finish button to clear the default keyboard. 4787 </string> 4788 <string name="enterprise_privacy_set_keyboard">Set Keyboard</string> 4789 <string name="enterprise_privacy_finish">Finish</string> 4790 <string name="enterprise_privacy_always_on_vpn">Always-on VPN</string> 4791 <string name="enterprise_privacy_always_on_vpn_info"> 4792 Please do the following:\n 4793 1) Press the Open Settings button.\n 4794 2) In the screen that opens, verify that you are not told that an always-on VPN is set.\n 4795 3) Use the Back button to return to this page.\n 4796 4) Press the Set VPN button to set an always-on VPN.\n 4797 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that an always-on VPN is set.\n 4798 6) Press the Finish button to clear the always-on VPN. 4799 </string> 4800 <string name="enterprise_privacy_set_always_on_vpn">Set VPN</string> 4801 <string name="enterprise_privacy_start">Start</string> 4802 <string name="enterprise_privacy_global_http_proxy">Global HTTP Proxy</string> 4803 <string name="enterprise_privacy_global_http_proxy_info"> 4804 Please do the following:\n 4805 1) Press the Open Settings button.\n 4806 2) In the screen that opens, verify that you are not told that a global HTTP proxy has been set.\n 4807 3) Use the Back button to return to this page.\n 4808 4) Press the Set Proxy button.\n 4809 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that a global HTTP proxy has been set.\n 4810 6) Press the Clear Proxy button. 4811 </string> 4812 <string name="enterprise_privacy_ca_certs">Trusted CA certs</string> 4813 <string name="enterprise_privacy_ca_certs_info"> 4814 Please do the following:\n 4815 1) Press the Open Settings button.\n 4816 2) In the screen that opens, verify that you are not told that your administrator installed trusted CA certs.\n 4817 3) Use the Back button to return to this page.\n 4818 4) Press the Install Cert button to install a trusted CA cert.\n 4819 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 4820 6) Press the Finish button to clear the cert. 4821 </string> 4822 <string name="enterprise_privacy_install_cert">Install Cert</string> 4823 <string name="enterprise_privacy_settings">Settings</string> 4824 <string name="enterprise_privacy_set_proxy">Set Proxy</string> 4825 <string name="enterprise_privacy_clear_proxy">Clear Proxy</string> 4826 <string name="enterprise_privacy_failed_password_wipe">Wipe on authentication failure</string> 4827 <string name="enterprise_privacy_failed_password_wipe_info"> 4828 Please do the following:\n 4829 1) Press the Open Settings button.\n 4830 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 4831 3) Use the Back button to return to this page.\n 4832 4) Press the Set Limit button to set the maximum number of password attempts.\n 4833 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 4834 6) Press the Finish button to clear the maximum number of password attempts. 4835 </string> 4836 <string name="enterprise_privacy_set_limit">Set Limit</string> 4837 <string name="enterprise_privacy_quick_settings">Quick settings disclosure</string> 4838 <string name="enterprise_privacy_quick_settings_info"> 4839 Please do the following:\n 4840 1) Press the Clear Org button.\n 4841 2) Open and fully expand Quick Settings.\n 4842 3) Verify that at the bottom of Quick Settings, you are told the device is managed.\n 4843 4) Close Quick Settings.\n 4844 5) Press the Set Org button.\n 4845 6) Open and fully expand Quick Settings.\n 4846 7) Verify that at the bottom of Quick Settings, you are told the device is managed by \"Foo, Inc.\".\n 4847 8) Tap on the information.\n 4848 9) Verify that a dialog informing you about device monitoring opens.\n 4849 10) Tap the \"View Policies\" button.\n 4850 11) Verify that a screen informing you what your managing organization can do is shown.\n 4851 \n 4852 Use the Back button to return to this page. If this device does not have quick settings, please skip this test and mark it passing. 4853 </string> 4854 <string name="enterprise_privacy_keyguard">Keyguard disclosure</string> 4855 <string name="enterprise_privacy_keyguard_info"> 4856 Please do the following:\n 4857 1) Press the Open Settings button to open Settings.\n 4858 2) Navigate to \"Security\" > \"Screen lock\" and select the first screen lock type that is not \"None\".\n 4859 3) Use the Back button to return to this page.\n 4860 4) Press the Clear Org button.\n 4861 5) Lock the device.\n 4862 6) Verify that on the lock screen, you are told the device is managed.\n 4863 7) Unlock the device.\n 4864 8) Press the Set Org button.\n 4865 9) Lock the device.\n 4866 10) Verify that on the lock screen, you are told the device is managed by \"Foo, Inc.\".\n 4867 11) Unlock the device.\n 4868 12) Repeat steps (1) through (11) for each screen lock type other than \"None\". 4869 </string> 4870 <string name="enterprise_privacy_add_account">Add account disclosure</string> 4871 <string name="enterprise_privacy_add_account_info"> 4872 Please do the following:\n 4873 1) Press the Clear Org button.\n 4874 2) Press the Open Settings button.\n 4875 3) In the screen that opens, verify that you are told that the device is managed.\n 4876 4) Use the Back button to return to this page.\n 4877 5) Press the Set Org button.\n 4878 6) Press the Open Settings button.\n 4879 7) In the screen that opens, verify that you are told that the device is managed by \"Foo, Inc.\".\n 4880 8) Tap the \"Learn more\" link.\n 4881 9) Verify that a screen informing you what your managing organization can do is shown.\n 4882 11) Use the Back button to return to this page. 4883 </string> 4884 <string name="enterprise_privacy_default_app">CTS Verifier Test</string> 4885 4886 <!-- Strings for Network Logging Tests --> 4887 <string name="device_owner_network_logging_ui">Network Logging UI</string> 4888 <string name="device_owner_network_logging_ui_info">Please do the following:\n 4889 1) Open and fully expand Quick Settings.\n 4890 2) Check that you are told that your device is managed.\n 4891 3) Close Quick Settings.\n 4892 4) Enable network logging by tapping on the left button below.\n 4893 5) Open Quick Settings again. Check that an icon appeared next to the text about device management.\n 4894 6) Verify that a notification including the same icon popped up, informing you that network logging has been enabled.\n 4895 7) Tap the notification.\n 4896 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 4897 9) Close the dialog.\n 4898 10) Tap the right button below to disable network logging.\n 4899 11) Verify that the notification disappeared.\n 4900 \n 4901 If this device does not have quick settings, please skip this test and mark it passing. 4902 </string> 4903 <string name="device_owner_enable_network_logging_button">Enable Network Logging</string> 4904 <string name="device_owner_disable_network_logging_button">Disable Network Logging</string> 4905 4906 <!-- Strings for Customize Lock Screen Message --> 4907 <string name="device_owner_customize_lockscreen_message">Customize Lock Screen Message</string> 4908 <string name="device_owner_customize_lockscreen_message_info">Please do the following:\n 4909 1) Press the \"Go\" button to go to Settings\n 4910 2) Find the \"Screen lock\" option and set it to \"Swipe\"\n 4911 3) Use the Back button to return to this page\n 4912 4) In the field below, write a lock screen message.\n 4913 5) Press the \"Set lock screen message\" button\n 4914 6) Press Power button once to lock the screen.\n 4915 7) Press Power button again to reveal the lock screen.\n 4916 8) Verify that the message from step 1) appears on the lock screen.\n 4917 9) Unlock the screen and return to this page.\n 4918 10) Press the \"Go\" button to go to Settings\n 4919 11) Find the \"Lock screen message\" option\n 4920 12) Verify that you cannot modify the setting.\n 4921 13) Use the Back button to return to this page.\n 4922 14) Press the \"Go\" button to go to Settings\n 4923 15) Find the \"Screen lock\" option and set it to \"None\"\n 4924 16) Use the Back button to return to this page 4925 </string> 4926 <string name="device_owner_set_lockscreen_message_button">Set lock screen message</string> 4927 <string name="device_owner_set_lockscreen_message_hint">My lock screen message</string> 4928 <string name="device_owner_lockscreen_message_cannot_be_empty">Lock screen message cannot be empty.</string> 4929 4930 <string name="device_owner_disable_usb_data_signaling_test">Disable USB data signaling</string> 4931 <string name="device_owner_disable_usb_data_signaling_test_info"> 4932 This test verifies that USB data signaling can be disabled by the device owner.\n 4933 1. Press the \"Go\" button to go to Settings. Go to Connected devices > USB and select use 4934 USB for \"File transfer/Android Auto\". Verify that you can mount the device as a USB drive 4935 on your desktop computer and access files from your phone through USB.\n 4936 2. Press the \"Disable USB data signaling\" button to disable USB data signaling on 4937 the device. When disabled, all USB data connections (except from charging functions) 4938 are prohibited.\n 4939 3. Press the \"Go\" button to go to Settings and confirm that the "USB" preferences in 4940 \"System > Developer Options\" cannot be selected and "USB" preference in 4941 \"Connected devices\" has disappeared.:\n 4942 - Connected devices > USB\n 4943 - System > Developer Options > USB debugging\n 4944 - System > Developer Options > Default USB configuration\n 4945 - System > Developer Options > Disable USB audio routing\n 4946 4. Verify that you cannot mount the device as a USB drive on your desktop computer and 4947 cannot access files from your phone through USB.\n 4948 5. Press the \"Enable USB data signaling\" button to re-enable USB data signaling and 4949 replug USB cable in the device. After that the "USB" preferences in 4950 \"System > Developer Options\" can be selected and "USB" preference in 4951 \"Connected devices\" has appeared.\n 4952 Please mark the test accordingly. 4953 </string> 4954 <string name="device_owner_enable_usb_data_signaling_test">Enable USB data signaling</string> 4955 4956 <string name="device_owner_required_password_complexity_test">Set required password complexity</string> 4957 <string name="device_owner_required_password_complexity_test_info"> 4958 This test verifies that required password complexity can be set by the device owner.\n 4959 1. Press the \"Set low required password complexity\" button.\n 4960 2. Press the \"Go\" button to go to Settings > Security > Screen lock. Verify that 4961 you have to set a pattern, PIN or password.\n 4962 3. Press the \"Set medium required password complexity\" button.\n 4963 4. Press the \"Go\" button to go to Settings > Security > Screen lock. Verify that 4964 you have to set a PIN without repeating (4444) or ordered (1234, 4321, 2468) sequences 4965 with a length of at least 4; or you have to set an alphabetic or alphanumeric password with 4966 a length of at least 4.\n 4967 5. Press the \"Set high required password complexity\" button.\n 4968 6. Press the \"Go\" button to go to Settings > Security > Screen lock. Verify that 4969 you have to set a PIN without repeating (4444) or ordered (1234, 4321, 2468) sequences 4970 with a length of at least 8; or you have to set an alphabetic or alphanumeric password with 4971 a length of at least 6.\n 4972 7. Press the \"Remove required password complexity\" button.\n 4973 8. Press the \"Go\" button to go to Settings > Security > Screen lock. Verify that 4974 you don\'t have to set a pattern, PIN or password.\n 4975 Please mark the test accordingly. 4976 </string> 4977 <string name="set_low_required_password_complexity">Set low required password complexity</string> 4978 <string name="set_medium_required_password_complexity">Set medium required password complexity</string> 4979 <string name="set_high_required_password_complexity">Set high required password complexity</string> 4980 <string name="remove_required_password_complexity">Remove required password complexity</string> 4981 4982 <string name="managed_user_test">Managed User</string> 4983 <string name="managed_user_positive_tests">Managed User positive tests</string> 4984 <string name="managed_user_positive_tests_instructions"> 4985 The positive managed user tests verify policies on a managed user created by a device owner. 4986 \n 4987 Press Go button to create a managed user, and you will be switched to the managed user 4988 automatically. Dismiss the keyguard and a \'Managed User Tests\' should launch.\n 4989 Follow the test instructions and press \'pass\' or \'fail\' to return to this screen.\n 4990 </string> 4991 <string name="managed_user_positive_tests_instructions" product="automotive"> 4992 The positive managed user tests verify policies on a managed user created by a device owner. 4993 \n 4994 Press Go button to create a managed user, and you will be switched to the managed user 4995 automatically; a \'Managed User Tests\' should launch.\n 4996 Follow the test instructions and press \'pass\' or \'fail\' to return to this screen.\n 4997 </string> 4998 <string name="managed_user_positive_tests_info"> 4999 The positive managed user tests verify policies on a managed user created by a device owner. 5000 Proceed to the test cases, then press \'pass\' or \'fail\' to finish this test. 5001 </string> 5002 <string name="managed_user_positive_category">Managed User Tests</string> 5003 <string name="managed_user_check_managed_user_test">Check affiliated profile owner</string> 5004 <string name="managed_user_incorrect_managed_user">Missing or incorrect affiliated profile owner: CTSVerifier is not affilaited PO!</string> 5005 5006 <string name="device_owner_disallow_user_switch">Disallow user switch</string> 5007 <string name="device_owner_disallow_user_switch_info"> 5008 Press \'Create uninitialized user\' to create a user that is not setup. 5009 Then press \'Set restriction\' button to set the user restriction. 5010 Then press \'Go\' to open multiple users settings. 5011 Confirm that:\n 5012 \n 5013 - Main switch is disabled and in off position\n 5014 \n 5015 In additional, if quick settings is available, confirm that user switcher is hidden or 5016 disabled. 5017 Use the Back button to return to this page. 5018 </string> 5019 <string name="device_owner_disallow_user_switch_create_user">Create uninitialized user</string> 5020 5021 <string name="device_owner_user_switcher_message">User switcher message</string> 5022 <string name="device_owner_user_switcher_message_info"> 5023 1. Please press the \'With user switcher message\' button to set the user switcher message. 5024 You will then be automatically switched to a secondary user. If a user switcher dialog shows 5025 up, it should read \'Start user session\'. Wait until you are automatically switched back to 5026 primary, if a user switcher dialog shows up, it should read \'End user session\'. 5027 5028 \n 5029 2. Please press the \'Without user switcher message\' button to clear the user switcher 5030 message. You will then be automatically switched to a secondary user. If a user switcher 5031 dialog shows up, it should read \'Switching to managed user\'. Wait until you are 5032 automatically switched back to primary, if a user switcher dialog shows up, it should read 5033 \'Switching to (name of primary user)\'. 5034 </string> 5035 <string name="device_owner_with_user_switcher_message">With user switcher message</string> 5036 <string name="device_owner_without_user_switcher_message">Without user switcher message</string> 5037 5038 <string name="device_owner_enable_logout">Logout</string> 5039 <string name="device_owner_enable_logout_info"> 5040 Please press the Go button to enable logout. You will then be switched to a newly created 5041 user. 5042 Look for a way to logout the current user without unlocking the lock screen. The control is 5043 usually named \'End session\'.\n 5044 The location may vary depending on manufacturer, typical locations are:\n 5045 - In power button menu by long pressing power button.\n 5046 - On the lock screen.\n 5047 \n 5048 When successfully logout and switched back to primary user, confirm that the logout control 5049 is not available in primary user. 5050 </string> 5051 5052 <!-- Strings for JobScheduler Tests --> 5053 <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> 5054 5055 <string name="js_idle_test">Idle Mode Constraints</string> 5056 <string name="js_start_test_text">Start test</string> 5057 <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> 5058 <string name="js_idle_description_1">Turn the screen off and then back on in order to begin.</string> 5059 <string name="js_idle_continue_instruction"> 5060 Switch off screen and wait for it to turn on to continue. 5061 </string> 5062 <string name="js_idle_item_idle_off">Idle job does not execute when device is not idle.</string> 5063 <string name="js_idle_item_idle_on">Idle job does execute when device is forced into idle.</string> 5064 5065 <string name="js_charging_test">Charging Constraints</string> 5066 <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> 5067 <string name="js_charging_description_1">Plug in the charger if it isn\'t already plugged in.</string> 5068 <string name="js_charging_off_test">Device not charging will not execute a job with a charging constraint.</string> 5069 <string name="js_charging_on_test">Device when charging will execute a job with a charging constraint.</string> 5070 <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> 5071 <string name="js_charging_description_3">Device is plugged in. Please wait while it gets into stable charging state.</string> 5072 <string name="js_charging_description_4">There seems to be a problem with your charger. Please try again.</string> 5073 5074 <string name="js_connectivity_test">Connectivity Constraints</string> 5075 <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> 5076 <string name="js_connectivity_description_1">Disable WiFi and Mobile data to begin.</string> 5077 <string name="js_unmetered_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 5078 <string name="js_any_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 5079 <string name="js_no_connectivity_test">Device with no connectivity will still execute a job with no connectivity constraints.</string> 5080 5081 <!-- String for the bundled TV app Tests --> 5082 5083 <string name="tv_input_discover_test">3rd-party TV input test</string> 5084 <string name="tv_input_discover_test_info"> 5085 Verify that the bundled TV app launches via Intent and calls the proper API to discover 5086 3rd-party TV inputs. 5087 </string> 5088 <string name="tv_input_discover_test_third_party_tif_input_support"> 5089 Does the bundled TV app support third-party TV inputs? 5090 </string> 5091 <string name="tv_input_discover_test_go_to_setup"> 5092 Select the \"Launch TV app\" button and set up the newly installed TV input: 5093 \"CTS Verifier\". 5094 </string> 5095 <string name="tv_input_discover_test_verify_setup"> 5096 Setup activity must have been started. 5097 </string> 5098 <string name="tv_input_discover_test_tune_to_channel"> 5099 Select the \"Launch TV app\" button and tune to the \"Placeholder\" channel from \"CTS Verifier\" 5100 input. If necessary, configure the channel to be visible. 5101 </string> 5102 <string name="tv_input_discover_test_verify_tune"> 5103 Tune command must be called. 5104 </string> 5105 <string name="tv_input_discover_test_verify_overlay_view"> 5106 Verify that the overlay appears and displays the text \"Overlay View Placeholder Text\" when you tune 5107 to the \"Placeholder\" channel. 5108 </string> 5109 <string name="tv_input_discover_test_verify_size_changed"> 5110 Verify that video layout changes correctly according to the provided video track information, 5111 including pixel aspect ratio. 5112 </string> 5113 <string name="tv_input_discover_test_verify_global_search"> 5114 Verify the TV app provides query results for 3rd-party input\'s channels and programs in 5115 global search results. 5116 </string> 5117 <string name="tv_input_discover_test_go_to_epg"> 5118 Select the \"Launch EPG\" button and locate the \"Placeholder\" channel. 5119 </string> 5120 <string name="tv_input_discover_test_verify_epg"> 5121 Do you see the programs named \"Placeholder Program\" and their descriptions 5122 "Placeholder Program Description" in the EPG? 5123 </string> 5124 <string name="tv_input_discover_test_trigger_setup"> 5125 Select the \"Launch setup\" button and verify if the bundled TV app shows the list of installed 5126 TV inputs for setup. 5127 </string> 5128 <string name="tv_input_discover_test_verify_trigger_setup"> 5129 Do you see the \"CTS Verifier\" input in the list? 5130 </string> 5131 5132 <string name="tv_parental_control_test">TV app parental controls test</string> 5133 <string name="tv_parental_control_test_info"> 5134 Verify that the bundled TV app calls the parental controls API. 5135 </string> 5136 <string name="tv_parental_control_test_turn_on_parental_control"> 5137 Select the \"Launch TV app\" button and turn on the parental controls. If parental controls are 5138 on already, turn it off and on again. 5139 </string> 5140 <string name="tv_parental_control_test_verify_receive_broadcast1"> 5141 TV input service must have received ACTION_PARENTAL_CONTROLS_ENABLED_CHANGED broadcast. 5142 </string> 5143 <string name="tv_parental_control_test_check_parental_controls_switch"> 5144 Is there an option to turn off parental controls on this device? 5145 </string> 5146 <string name="tv_parental_control_test_block_tv_ma"> 5147 Select the \"Launch TV app\" button and block the \"Custom Rating\" for \"CtsVerifier\" rating 5148 system in the parental control settings. If the rating system is disabled by default, enable it. 5149 If the \"Custom Rating\" is already blocked, unblock it, save, and then block again. 5150 </string> 5151 <string name="tv_parental_control_test_verify_receive_broadcast2"> 5152 TV input service must have received ACTION_BLOCKED_RATINGS_CHANGED broadcast. 5153 </string> 5154 <string name="tv_parental_control_test_block_unblock"> 5155 Select the \"Launch TV app\" button; verify that the channel is blocked. 5156 Try to unblock the screen by entering PIN; verify that it\'s unblocked. 5157 </string> 5158 5159 <string name="tv_yes">Yes</string> 5160 <string name="tv_no">No</string> 5161 <string name="tv_none">None</string> 5162 <string name="tv_launch_tv_app">Launch TV app</string> 5163 <string name="tv_launch_epg">Launch EPG</string> 5164 <string name="tv_launch_setup">Launch setup</string> 5165 <string name="tv_channel_not_found"> 5166 CtsVerifier channel is not set up. Please set up before proceeding. 5167 </string> 5168 5169 <string name="tv_multiple_tracks_test">TV app closed captions and multi-audio test</string> 5170 <string name="tv_multiple_tracks_test_info"> 5171 Verify that the bundled TV app calls the multi-track API. 5172 </string> 5173 <string name="tv_multiple_tracks_test_select_subtitle"> 5174 Select the \"Launch TV app\" button. Verify that closed captions are off by default. Set closed 5175 caption language to English. 5176 </string> 5177 <string name="tv_multiple_tracks_test_verify_set_caption_enabled"> 5178 Captions are enabled. 5179 </string> 5180 <string name="tv_multiple_tracks_test_verify_select_subtitle"> 5181 The English closed caption track should be selected. 5182 </string> 5183 <string name="tv_multiple_tracks_test_select_audio"> 5184 Select the \"Launch TV app\" button. Verify that the audio track is English by default. 5185 Select Spanish audio track. 5186 </string> 5187 <string name="tv_multiple_tracks_test_verify_select_audio"> 5188 The Spanish audio track should be selected. 5189 </string> 5190 5191 <string name="tv_time_shift_test">TV app time shift test</string> 5192 <string name="tv_time_shift_test_info"> 5193 This test verifies that the TV app invokes proper time shift APIs in the framwork. 5194 </string> 5195 <string name="tv_time_shift_test_pause_resume"> 5196 Press the \"Launch TV app\" button. Verify that the playback control is available. 5197 Pause the playback and then resume it. 5198 </string> 5199 <string name="tv_time_shift_test_verify_resume_after_pause"> 5200 The playback should resume after pause. 5201 </string> 5202 <string name="tv_time_shift_test_verify_position_tracking"> 5203 The playback position tracking should be activated. 5204 </string> 5205 <string name="tv_time_shift_test_speed_rate"> 5206 Press the \"Launch TV app\" button. Verify that the playback control is available. 5207 Rewind the playback and in a few seconds fast-forward it. 5208 </string> 5209 <string name="tv_time_shift_test_verify_rewind"> 5210 The playback should rewind. 5211 </string> 5212 <string name="tv_time_shift_test_verify_fast_forward"> 5213 The playback should fast-forward. 5214 </string> 5215 <string name="tv_time_shift_test_seek"> 5216 Press the \"Launch TV app\" button. Verify that the playback control is available. 5217 Seek to previous and then seek to next. 5218 </string> 5219 <string name="tv_time_shift_test_verify_seek_to_previous"> 5220 The playback position should be moved to the previous position. 5221 </string> 5222 <string name="tv_time_shift_test_verify_seek_to_next"> 5223 The playback position should be moved to the next position. 5224 </string> 5225 5226 <string name="tv_app_link_test">TV app app-link test</string> 5227 <string name="tv_app_link_test_info"> 5228 Verify that the bundled TV app supports linking to channel apps. If a TV input service provides 5229 links for its specific channels, the TV app should show the links in a proper format. 5230 </string> 5231 <string name="tv_app_link_test_select_app_link"> 5232 Select the \"Launch TV app\" button, then check if you can see a menu with \"Cts App-Link Text\" 5233 text in red background. If you see the link, select it to follow the link. 5234 </string> 5235 <string name="tv_app_link_test_verify_link_clicked"> 5236 The app-link must have been clicked and the activity should be changed correctly. 5237 </string> 5238 <string name="tv_input_link_test_verify_link_interface"> 5239 Do you see the app-link card similar to the image on the left?\n 5240 1) You should see the poster art image, but the color may be different.\n 5241 2) You should see the text \"Cts App-Link Text\".\n 5242 </string> 5243 5244 <string name="tv_microphone_device_test">Microphone device test</string> 5245 <string name="tv_microphone_device_test_info"> 5246 This test checks if InputDevice.hasMicrophone of the Media API reports a 5247 correct value on every input device (including remote controls). 5248 </string> 5249 <string name="tv_microphone_device_test_prep_question"> 5250 Before continuing, please make sure that you pair all primary input 5251 devices intended to be used by the device, including bluetooth 5252 remotes and companion remote-control apps such as the Android TV Remote Control. 5253 Have you paired every primary input device with the device under test (DUT)? 5254 </string> 5255 <string name="tv_microphone_device_test_mic_question"> 5256 Does input device \"%1$s\" have a microphone? 5257 </string> 5258 <string name="tv_microphone_device_test_negative_mismatch"> 5259 InputDevice.hasMicrophone reports that this input device DOES have a 5260 microphone whereas you selected that it does not. Please correct it by 5261 declaring \"audio.mic = 0\" in the device\'s input device configuration 5262 (.idc) file. 5263 </string> 5264 <string name="tv_microphone_device_test_positive_mismatch"> 5265 InputDevice.hasMicrophone reports that this input device does NOT have a 5266 microphone whereas you selected that it does. Please correct it by 5267 declaring \"audio.mic = 1\" in the device\'s input device configuration 5268 (.idc) file and make sure that relevant files such as key layout (.kl) 5269 and key character map (.kcm) files are found by the system accordingly. 5270 </string> 5271 <string name="tv_microphone_device_test_no_input_devices">No input devices found.</string> 5272 5273 <!-- Common strings for the TV Display tests --> 5274 <string name="tv_start_test">Start Test</string> 5275 <string name="tv_done">Done</string> 5276 5277 <!-- Hotplug Test --> 5278 <string name="tv_hotplug_test">Hotplug Test</string> 5279 <string name="tv_hotplug_test_info">This test checks whether DisplayManager responds correctly 5280 to plugging and unplugging the HDMI cable. 5281 </string> 5282 <string name="tv_hotplug_disconnect_display"> 5283 Press the "%1$s" button, disconnect the HDMI cable, wait 2 seconds and then connect the HDMI 5284 cable again. 5285 </string> 5286 5287 <!-- Mode Switching Test --> 5288 <string name="tv_mode_switching_test">Mode switching test</string> 5289 <string name="tv_mode_switching_test_step_instruction"> 5290 Click "Start Test" and then observe the video below. Testing transition from %1$s to %2$s. 5291 </string> 5292 <string name="tv_mode_switching_test_black_screen_question"> 5293 Did the video playback experience an interruption, for example, a black or solid color 5294 screen? 5295 </string> 5296 <string name="tv_mode_switching_test_is_video_ok"> 5297 Does the video look okay? Click "No" if the video is not playing, there was a snow screen, 5298 audio static, wrong colors, the video is displaced compared to before running the test or 5299 if the video is not playing. Keep in mind that some stutter is expected when the video does 5300 not match the refresh rate. 5301 </string> 5302 <string name="tv_mode_switching_test_mode_switch_step">Mode switch step</string> 5303 5304 <string name="overlay_view_text">Overlay View Placeholder Text</string> 5305 <string name="custom_rating">Example of input app specific custom rating.</string> 5306 5307 <!-- A list of fully-qualified test classes that should not be run. --> 5308 <string-array name="disabled_tests"> 5309 <item>com.android.cts.verifier.telecom.CtsVerifierInCallUi</item> 5310 <item>com.android.cts.verifier.car.CarDockActivity</item> 5311 <item>com.android.cts.verifier.car.CarDockTestActivity</item> 5312 </string-array> 5313 5314 <!-- Strings for screen pinning test --> 5315 <string name="screen_pinning_test">Screen Pinning Test</string> 5316 <string name="screen_pin_instructions">Pressing next will prompt you to enter screen pinning, allow this app to enter screen pinning.</string> 5317 <string name="screen_pin_check_pinned">Press Next to verify the app is pinned.</string> 5318 <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> 5319 <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> 5320 5321 <string name="error_screen_no_longer_pinned">The screen was no longer pinned.</string> 5322 <string name="error_screen_already_pinned">Cannot start the test with the screen already pinned.</string> 5323 <string name="error_screen_pinning_did_not_start">Screen was not pinned.</string> 5324 <string name="error_screen_pinning_did_not_exit">Screen was not unpinned.</string> 5325 <string name="error_screen_pinning_couldnt_exit">Could not exit screen pinning through API.</string> 5326 5327 <!-- Audio Devices Notifications Tests --> 5328 <string name="audio_devices_notification_instructions"> 5329 Connect and disconnect a wired headset. 5330 Note if the appropriate notification messages appear below. 5331 The \"Pass\" button will be enabled if device connect and disconnect messages are received. 5332 </string> 5333 <string name="audio_dev_notification_clearmsgs">Clear Messages</string> 5334 <string name="audio_dev_notification_connectMsg">CONNECT DETECTED - %1$S</string> 5335 <string name="audio_dev_notification_disconnectMsg">DISCONNECT DETECTED - %1$S</string> 5336 5337 <string name="audio_out_devices_notifications_test">Audio Output Devices Notifications Test</string> 5338 <string name="audio_out_devices_infotext">Tests whether wired output peripheral 5339 connect/disconnect notifications are correctly sent when output peripherals are 5340 connected or disconnected. A \"wired output peripheral\" can be a headset or headphones 5341 connected to an analog 3.5mm jack or the USB port or a USB audio interface connected to 5342 the USB port. 5343 \n\nTest Setup: 5344 \nDisconnect any wired audio peripherals. 5345 \n\nTest Process: 5346 \n1. Verify that the DUT supports USB or Analog audio peripherals. 5347 \n2. Press the \"Clear Messages\" button to clear any previously sent \"sticky\" notifications. 5348 \n3. Connect a wired output peripheral. A connect message should appear. Disconnect the 5349 audio peripheral. A disconnect message should appear. 5350 \n\nTest Criteria: 5351 \nThe test passes if either the device DOES NOT support wired output peripherals, or both 5352 the connect and disconnect notifications are received. 5353 </string> 5354 5355 <string name="audio_in_devices_notifications_test">Audio Input Devices Notifications Test</string> 5356 <string name="audio_in_devices_infotext">Tests whether wired input peripheral 5357 connect/disconnect notifications are correctly sent when input peripherals are 5358 connected or disconnected. A \"wired input peripheral\" can be a headset connected to an 5359 analog 3.5mm jack or the USB port or a USB audio interface connected to the USB port. 5360 \n\nTest Setup: 5361 \nDisconnect any wired audio peripherals. 5362 \n\nTest Process: 5363 \n1. Verify that the DUT supports USB or Analog audio peripherals. 5364 \n2. Press the \"Clear Messages\" button to clear any previously sent \"sticky\" notifications. 5365 \n3. Connect a wired output peripheral. A connect message should appear. Disconnect the 5366 audio peripheral. A disconnect message should appear. 5367 \n\nTest Criteria: 5368 \nThe test passes if either the device DOES NOT support wired output peripherals, or both 5369 the connect and disconnect notifications are received. 5370 </string> 5371 5372 <string name="audio_input_routingnotifications_test">Audio Input Routing Notifications Test</string> 5373 <string name="audio_input_routingnotification_instructions"> 5374 Test whether appropriate routing notifications are sent when audio input peripherals are 5375 connected to the device. 5376 \n\nTest Setup: 5377 \nDisconnect any wired audio peripherals. 5378 \n\nTest Process: 5379 \n1. Verify that the DUT supports USB or Analog audio peripherals. 5380 \n2. Press the \"Record\" button. 5381 \n3. Connect a wired input peripheral. A connect routing message should appear. 5382 \n4. Press the \"Stop\" button. 5383 \n\nTest Criteria: 5384 \nThe test passes if either the device DOES NOT support wired input peripherals, or 5385 the routing notifications are received. 5386 </string> 5387 <string name="audio_output_routingnotifications_test">Audio Output Routing Notifications Test</string> 5388 <string name="audio_output_routingnotification_instructions"> 5389 Test whether appropriate output routing notifications are sent when audio output peripherals are 5390 connected to the device. 5391 \n\nTest Setup: 5392 \nDisconnect any wired audio peripherals. 5393 \n\nTest Process: 5394 \n1. Verify that the DUT supports USB or Analog audio peripherals. 5395 \n2. Press the \"Play\" button. 5396 \n3. Connect a wired output peripheral. A connect routing message should appear. 5397 \n4. Press the \"Stop\" button. 5398 \n\nTest Criteria: 5399 \nThe test passes if either the device DOES NOT support wired output peripherals, or 5400 the routing notifications are received. 5401 </string> 5402 <string name="audio_routingnotification_playHeader">AudioTrack Routing Notifications</string> 5403 <string name="audio_routingnotification_recHeader">AudioRecord Routing Notifications</string> 5404 <string name="audio_routingnotification_trackRoutingMsg">AudioTrack rerouting</string> 5405 <string name="audio_routingnotification_recordRoutingMsg">AudioRecord rerouting</string> 5406 5407 <!-- USB Audio Peripheral Tests --> 5408 <string name="profileLabel">Profile</string> 5409 <string name="connectedPeripheral">Connected Peripheral</string> 5410 <string name="audio_uap_attribs_test">USB Audio Peripheral Attributes Test</string> 5411 <string name="audio_uap_notifications_test">USB Audio Peripheral Notifications Test</string> 5412 <string name="uapPeripheralProfileAttributes">USB Audio Peripheral Attributes</string> 5413 <string name="audio_uap_play_test">USB Audio Peripheral Play Test</string> 5414 <string name="uapPlayTestInstructions">Connect the USB Audio Interface Peripheral and press the 5415 PLAY button below. Verify that a tone is correctly played.</string> 5416 <string name="uapPlayStopTestInstructions">Connect the USB Audio Interface Peripheral and press the 5417 PLAY button below. Verify that a tone is correctly played. Then press the STOP button. 5418 </string> 5419 <string name="audio_uap_play_playBtn">Play</string> 5420 <string name="audio_uap_play_stopBtn">Stop</string> 5421 5422 <string name="audio_uap_record_test">USB Audio Peripheral Record Test</string> 5423 <string name="uapRecordTestInstructions">Connect the USB Audio Peripheral and press the RECORD or 5424 RECORD LOOPBACK button below. Verify that a tone is correctly played.</string> 5425 <string name="audio_uap_record_recordBtn">Record</string> 5426 <string name="audio_uap_record_recordLoopbackBtn">Record Loopback</string> 5427 <string name="audio_uap_record_stopBtn">Stop</string> 5428 5429 <string name="audio_uap_buttons_test">USB Audio Peripheral Buttons Test</string> 5430 <string name="uapButtonTestInstructions">Connect the USB Audio headset with buttons 5431 and press each button on the headset to verify recognition.</string> 5432 5433 <string name="uapNotificationsTestInfo"> 5434 This test verifies that the correct notifications and Intents are sent when a USB audio 5435 peripheral is connected to the Android device. First USB headset peripheral should be 5436 connected and the test will acknowledge the USB headset device notifications and plug intent. 5437 Next a non-headset / headphones USB peripheral should be connected and the test will 5438 acknowlege the USB device notifications. If all notifications and Intents are received 5439 the test passes. 5440 </string> 5441 5442 <string name="audio_usb_restrict_record_test">USB Audio Restrict Record Access Test</string> 5443 <string name="audio_usb_restrict_record_entry"> 5444 Tests whether the appropriate warning message is displayed when an app which has 5445 not been granted RECORD permission could potentially record audio through the raw USB API. 5446 \n\nTest Setup: 5447 \n1. Exit CTS-Verifier with the Home button 5448 \n2. Go to Android Settings 5449 \n3. Select Apps & notifications 5450 \n4. Select CTS Verifier 5451 \n5. Select Permissions 5452 \n6. Deny Microphone permission 5453 \n7. Start CTS Verifier. Ignore the \"Please grant all permissions\" message by clicking on the 5454 face of the CTS Verifier (not in the dialog). 5455 \n8. Run this test 5456 \n\nTest Process: 5457 \nConnect a USB peripheral with CAPTURE capability and press the \"Test\" button. 5458 \n\nTest Criteria: 5459 \nThe access permission API should present a warning message about potential dangerous 5460 access. If so, the test passes. If you do not see this warning, the test fails. 5461 \n\nPost-test completion: 5462 \n1. Exit CTS-Verifier with the Home button 5463 \n2. Reenable Microphone permission in Android Settings 5464 </string> 5465 5466 <string name="audio_usb_restrict_permission_info"> 5467 The test can only be run with Microphone permission DENIED. 5468 \n\nTo run this test: 5469 \n1. Exit CTS-Verifier with the Home button 5470 \n2. Go to Android Settings 5471 \n3. Select Apps & notifications 5472 \n4. Select CTS Verifier 5473 \n5. Select Permissions 5474 \n6. Deny Microphone permission 5475 \n7. Start CTS Verifier. Ignore the \"Please grant all permissions\" message by clicking on the 5476 ace of the CTS Verifier (not in the dialog). 5477 \n8. Run this test 5478 \n\nWhen complete: 5479 \n1. Exit CTS-Verifier with the Home button 5480 \n2. Reenable Microphone permission in Android Settings 5481 </string> 5482 5483 <string name="usb_restrictrecord_instructions"> 5484 Permissions for CTS Verifier are correctly set to run this test.\n\n 5485 Connect a USB peripheral with CAPTURE capability. Press the "Test" button and verify that 5486 a warning is shown in the device access UI. 5487 </string> 5488 5489 <string name="uapButtonsBtnALbl">Button A - play/pause</string> 5490 <string name="uapButtonsBtnBLbl">Button B - volume up (+)</string> 5491 <string name="uapButtonsBtnCLbl">Button C - volume down (-)</string> 5492 <string name="uapButtonsBtnDLbl">Button D - voice assist</string> 5493 <string name="uapButtonsRecognized">Recognized</string> 5494 <string name="uapButtonsNotRecognized">Not Recognized</string> 5495 <string name="uapButtonsDisableAssistantTitle">Disable Google Assistant</string> 5496 <string name="uapButtonsDisableAssistant">For this test to succeed it may be necessary 5497 to disable the Google Assistant (Settings / Google / Search / Google Assistant Settings / 5498 Devices / <device name> / Google Assistant)</string> 5499 5500 <!-- Pro Audio Tests --> 5501 <string name="pro_audio_latency_test">Pro Audio Test</string> 5502 5503 <string name="proAudioHasProAudiolbl">Has Pro Audio:</string> 5504 <string name="proAudioHasLLAlbl">Has Low-Latency Audio:</string> 5505 <string name="audioLoopbackInputLbl">Audio Input:</string> 5506 <string name="audioLoopbackOutputLbl">Audio Output:</string> 5507 <string name="proAudioMidiHasMIDILbl">Has MIDI Support:</string> 5508 <string name="proAudioMidiHasUSBHostLbl">USB Host Mode:</string> 5509 <string name="proAudioMidiHasUSBPeripheralLbl">USB Peripheral Mode:</string> 5510 <string name="proAudioHDMISupportLbl">HDMI Support:</string> 5511 <string name="proAudioHasHDMICheckBox">Has HDMI Support</string> 5512 5513 <string name="audio_proaudio_NA">N/A</string> 5514 <string name="audio_proaudio_hdmiPending">pending...</string> 5515 <string name="audio_proaudio_hdmiNotFound">No HDMI detected.</string> 5516 5517 <string name="audio_proaudio_nopa_title">Pro Audio Test</string> 5518 <string name="audio_proaudio_nopa_message">This device does not set the FEATURE_AUDIO_PRO 5519 flag and therefore does not need to run this test.</string> 5520 5521 <string name="hdmi_insufficient">The Connected HDMI device does not meet CDD requirements</string> 5522 5523 <!-- Various test status strings --> 5524 <string name="audio_proaudio_pass">Pass</string> 5525 <string name="audio_proaudio_latencytoohigh">Latency is too high</string> 5526 <string name="audio_proaudio_confidencetoolow">"Insufficient Confidence value"</string> 5527 <string name="audio_proaudio_midinotreported">"No MIDI support reported"</string> 5528 <string name="audio_proaudio_usbhostnotreported">"No USB Host Mode support reported"</string> 5529 <string name="audio_proaudio_usbperipheralnotreported">"No USB Peripheral Mode support reported"</string> 5530 5531 <!-- MIDI Test --> 5532 <string name="midi_test">MIDI Test</string> 5533 <string name="midi_java_test">Java MIDI Test</string> 5534 <string name="midi_native_test">Native MIDI Test</string> 5535 5536 <string name="midi_info"> 5537 Tests for basic MIDI functionality. 5538 \n\n1. Test Setup - USB MIDI: 5539 \nConnect a supported USB Audio Peripheral device that has standard MIDI 5-pin, DIN (round) 5540 connectors and a standard MIDI cable. The cable must be connected to the MIDI input and 5541 output jacks on the peripheral. 5542 \n\n2. Test Setup - Bluetooth MIDI: 5543 \na. Download and install the "MIDI+BTLE" app from the Play Store. 5544 \nb. Connect a supported USB Audio Peripheral device that has standard MIDI 5-pin, DIN (round) 5545 connectors and connect the MIDI ports to a Bluetooth MIDI adapter (such as the Yamaha 5546 MD-BT01). Be sure to connect the MD-BT01 so that the arrow on the MD-BT01 plug points away 5547 from the Output jack on the USB peripheral. The other plug should have an arrow pointing 5548 towards the Input jack. 5549 \nc. Run the \"MIDI+BTLE\" app, click on "Bluetooth Scan" and select the Bluetooth MIDI adapter 5550 connected to the USB Audio Peripheral. Note that the \"Test Bluetooth MIDI Interface\" 5551 button will be enabled. 5552 \n\n2. Test Setup - Virtual MIDI: 5553 \nThe Virtual MIDI test does not require any MIDI interface hardware. 5554 \n\nTest Process: 5555 \n1. Follow instructions for \"Test Setup - USB MIDI\" 5556 \n2. Press the \"Test US MIDI Interface\" button. Note test results. 5557 \n3. Press the \"Test Virtual MIDI Interface\" button. Note test results. 5558 \n4. Follow instructions for \"Test Setup - Bluetooth MIDI\" 5559 \n5. Press the \"Test Bluetooth MIDI Interface\" button. Note test results. 5560 \n\nTest Criteria: 5561 \nAll sub-tests must pass for this test to pass. 5562 </string> 5563 <string name="analog_headset_test_info_tv">This test tests the following functionality with respect to wired analog headsets.\n 5564 1. Correct audio playback.\n 5565 2. Plug intents.\n 5566 \nTo execute test:\n 5567 1. Plug in an Android-compatible, analog headset. Verify connection/recognition.\n 5568 2. Play test tone and verify correct behavior.\n 5569 \nTo run this test it is necessary to have an Android device with a 3.5mm analog headset jack and a compatible analog headset.\n 5570 \n(see <a href="https://source.android.com/devices/accessories/headset/plug-headset-spec">3.5 mm Headset: Accessory Specification</a> and 5571 <a href="https://source.android.com/compatibility/android-cdd#7_8_2_1_analog_audio_ports">Android CDD § 7.8.2.1. Analog Audio Ports</a>) 5572 </string> 5573 5574 <string name="usb_midi_audio_test">USB MIDI and Audio Test</string> 5575 <string name="usb_midi_audio_info"> 5576 Connect a supported USB Audio Peripheral device that has standard MIDI 5-pin, DIN (round) 5577 connectors and a standard MIDI cable. The cable must be connected to the MIDI input and 5578 output jacks on the peripheral. 5579 \nPlease attach a wired headset with a 3.5mm jack to the audio output of this peripheral. 5580 \nTest the USB MIDI interface first. Then, press the PLAY to button test audio. Verify 5581 that a tone is correctly played. 5582 </string> 5583 <string name="midiUSBAudioTestLbl">USB Audio Playback Test:</string> 5584 5585 <string name="midiHasMIDILbl">Has MIDI Support</string> 5586 5587 <string name="midiUSBTestLbl">USB MIDI Loopback Test:</string> 5588 <string name="usbMidiInputLbl">USB Input:</string> 5589 <string name="usbMidiOutputLbl">USB Output:</string> 5590 <string name="midiTestUSBInterfaceBtn">Test USB MIDI Interface</string> 5591 5592 <string name="midiVirtTestLbl">Virtual MIDI Loopback Test:</string> 5593 <string name="midiVirtInputLbl">Virtual Input:</string> 5594 <string name="midiVirtOutputLbl">Virtual Output:</string> 5595 <string name="midiTestVirtInterfaceBtn">Test Virtual MIDI Interface</string> 5596 5597 <string name="midiBTTestLbl">Bluetooth MIDI Loopback Test:</string> 5598 <string name="midiBTInputLbl">Bluetooth Input:</string> 5599 <string name="midiBTOutputLbl">Bluetooth Output:</string> 5600 <string name="midiTestBTInterfaceBtn">Test Bluetooth MIDI Interface</string> 5601 5602 <string name="midiStatusLbl">Status</string> 5603 <string name="midiNotRunLbl">Not Run.</string> 5604 <string name="midiPassedLbl">Passed.</string> 5605 <string name="midiFailedMismatchLbl">Failed - Data Mismatch.</string> 5606 <string name="midiFailedTimeoutLbl">Failed - Timeout.</string> 5607 <string name="midiFailedOverrunLbl">Failed - Data Overrun.</string> 5608 <string name="midiFailedDeviceLbl">Failed - Device Error.</string> 5609 <string name="midiFailedJNILbl">Failed - JNI Error.</string> 5610 5611 <!-- Audio general text --> 5612 <string name="audio_wired_exists">Does this device support wired USB or Analog audio peripherals?</string> 5613 <string name="audio_wired_no">No</string> 5614 <string name="audio_wired_yes">Yes</string> 5615 <string name="audio_general_deficiency_found">WARNING: Some results show potential deficiencies on the system. 5616 Please consider addressing them for a future release.</string> 5617 <string name="audio_general_test_passed">Test Result: Successful</string> 5618 <string name="audio_general_test_failed">Test Result: Not Optimal</string> 5619 <string name="audio_general_default_false_string">false</string> 5620 <string name="audio_general_default_true_string">true</string> 5621 <string name="audio_general_warning">Warning</string> 5622 <string name="audio_general_level_not_max">Audio Level is not maximum. Please check your device 5623 is set to max level for audio playback.</string> 5624 5625 <string name="audio_general_no">No</string> 5626 <string name="audio_general_yes">Yes</string> 5627 <string name="audio_general_info">Info</string> 5628 <string name="audio_general_ok">Ok</string> 5629 <string name="audio_general_start">Start</string> 5630 <string name="audio_general_stop">Stop</string> 5631 <string name="audio_general_status">Status</string> 5632 <string name="audio_general_pass">PASS</string> 5633 <string name="audio_general_teststatus_pass">Test Status: PASS</string> 5634 <string name="audio_general_fail">FAIL</string> 5635 <string name="audio_general_teststatus_fail">Test Status: FAIL</string> 5636 <string name="audio_general_not_tested">Not Tested</string> 5637 <string name="audio_general_not_required">Please Test If Supported</string> 5638 <string name="audio_general_required">Required</string> 5639 <string name="audio_general_run">Run</string> 5640 <string name="audio_general_cancel">Cancel</string> 5641 5642 <string name="audio_general_Input">Input</string> 5643 <string name="audio_general_Output">Output</string> 5644 5645 <string name="audio_general_record">Record</string> 5646 <string name="audio_general_play">Play</string> 5647 5648 <string name="audio_general_JavaApi">Java API</string> 5649 <string name="audio_general_NativeApi">Native API</string> 5650 5651 <string name="audio_general_clear_results">Clear Results</string> 5652 5653 <string name="audio_general_test_not_run">Test Not Run</string> 5654 <string name="audio_general_testnotcompleted">Test not completed.</string> 5655 5656 <string name="audio_general_reportlogtest">[Can\'t Write ReportLog]</string> 5657 5658 <string name="audio_general_play_colon"> play:</string> 5659 <string name="audio_general_record_colon"> record:</string> 5660 5661 <!-- Audio Data Paths Test--> 5662 <string name="audio_datapaths_test">Audio Data Paths Test</string> 5663 <string name="audio_datapaths_info">This test verifies basic functionality over a set of audio routes 5664 \nTest Setup: 5665 \n - It may be necessary to go to the \"Sound & vibration\" settings panel to set the volume level for each output device. 5666 \n 1. With no audio peripherals connected, adjust the \"Media volume\" to max. 5667 \n 2. (If applicable) insert the analog loopback adapter into the 3.5mm headset jack and adjust the \"Media volume\" to max. 5668 \n 3. (If applicable) connect a USB audio interface and adjust the \"Media volume\" to max. 5669 \n - If the device has a 3.5mm headset jack, insert a loopback adapter in the jack. (See the \"Audio Loopback Latency Test\" for a description). 5670 \n - If the device supports audio over USB, connect a USB audio interface with loopback cables. (See the \"Audio Loopback Latency Test\" for a description). 5671 \n The test will display valid data paths with an asterix appended to the data path name. 5672 \nTest Execution: 5673 \n - Place the device on a flat surface in a quiet room. 5674 \n - Select the \"Native API\" button. 5675 \n - Press the \"Start\" button. The test will step through the list of valid data paths playing a tone and recording it\'s presence or absence. 5676 Be aware that the test will play tones through the internal speaker even if an analog loopback plug and/or USB loopback device is connected. 5677 \n - Select the \"Java API\" button. 5678 \n - Press the \"Start\" button to repeat each data path test for the Java API. 5679 \nTest Completion: 5680 \n - Once each of the data paths and APIs have been measured, the test can be marked successful. 5681 </string> 5682 <string name="audio_datapaths_noio">"No valid datapaths. PASS."</string> 5683 <string name="audio_datapaths_results">%1$s\n%2$s -> %3$s</string> 5684 5685 <!-- Audio Loopback Latency Test --> 5686 <string name="audio_loopback_latency_test">Audio Loopback Latency Test</string> 5687 <string name="audio_loopback_info">This test verifies that the DUT can achieve the required or 5688 recommended loopback latency as defined by CDD § 5.6 (Audio Latency) and 5689 § 5.10 (Professional Audio). 5690 \nTo pass the test, the DUT needs to meet the latency requirement on ALL 3 of the 5691 following audio paths (if present): 5692 \n- the internal speaker and microphone. 5693 \n- a <a href="https://source.android.com/devices/audio/latency/loopback">Loopback Plug</a> connected to a 3.5mm headset jack. 5694 \n- a <a href="https://source.android.com/devices/audio/latency/loopback">Loopback Plug</a> connected to a USB audio adapter. 5695 (or alternatively USB interface with patch cords connecting the input and output jacks). 5696 \nPlease connect these Loopback mechanisms (the same Loopback Plug can be used at different times 5697 for the headset jack and USB audio adapter) and proceed with the instructions 5698 on the screen. The volume may need to be adjusted for each audio path. 5699 \nNote that for the Speaker/Microphone path, it may be necessary to remove any phone case on the device. 5700 \nThe system will measure the input-output audio latency by injecting an audio signal into 5701 the output and compute the time between generating the signal and recording it back. 5702 You can vary the Audio Level slider to ensure the pulse will feed back at adequate levels. 5703 Repeat until a sufficient confidence is achieved. When each route test is completed, the 5704 measured and required latencies will be displayed. 5705 \nWhen all test routes have passed, the test as a whole can be passed. 5706 </string> 5707 <string name="audio_loopback_instructions"> 5708 Please connect a "Loopback Plug" and press "Loopback Plug Ready". 5709 </string> 5710 <string name="audio_loopback_plug_ready_btn">Loopback Plug Ready</string> 5711 <string name="audio_loopback_instructions2"> 5712 Set the audio level to a suitable value, then press Test button. 5713 It might require multiple tries until a sufficient confidence is achieved. 5714 </string> 5715 <string name="audio_loopback_level_text">Audio Level</string> 5716 <string name="audio_loopback_test_btn">Test</string> 5717 <string name="audio_loopback_results_text">Results...</string> 5718 <string name="audio_loopback_test_all_paths">Please test all supported paths.</string> 5719 <string name="audio_loopback_test_not_required">Test not required for this device.</string> 5720 <string name="audio_loopback_test_non_handheld">This device is not a phone. Test can pass.</string> 5721 <string name="audio_loopback_test_internal_devices">Speaker/Mic</string> 5722 <string name="audio_loopback_speakermicpath_instructions">Place the DUT flat on a table 5723 in a quiet room. Press the Start button and allow the test to proceed.</string> 5724 5725 <string name="audio_loopback_headsetpath_instructions">If supported, insert the loopback plug 5726 into the headset jack. Press the Start button and allow the test to proceed.</string> 5727 5728 <string name="audio_loopback_usbpath_instructions">If USB Audio supported, Connect the USB 5729 port to an appropriate USB audio test peripheral with loopback set up. Press the Start 5730 button and allow the test to proceed.</string> 5731 5732 <string name="audio_loopback_failure">FAILURE - Could not allocate analyzer thread.</string> 5733 <string name="audio_loopback_automobile">Automobile:</string> 5734 <string name="audio_loopback_handheld">Handheld:</string> 5735 <string name="audio_loopback_tv">TV:</string> 5736 <string name="audio_loopback_watch">Watch:</string> 5737 <string name="audio_loopback_mmapexclusive">MMAP Exclusive:</string> 5738 <string name="audio_loopback_mmap">MMAP:</string> 5739 <string name="audio_loopback_mcp">MPC:</string> 5740 <string name="audio_loopback_lowlatency">Low Latency:</string> 5741 <string name="audio_loopback_proaudio">Pro Audio:</string> 5742 <string name="audio_loopback_speakermic">Speaker/Mic</string> 5743 <string name="audio_loopback_headsetjack">Headset Jack</string> 5744 <string name="audio_loopback_usb">USB</string> 5745 5746 <!-- result codes --> 5747 <string name="audio_loopback_resultcode_none">Result: None.</string> 5748 <string name="audio_loopback_resultcode_pass">Result: Pass.</string> 5749 <string name="audio_loopback_resultcode_nointernal">Result: Fail - Speaker/Mic path not tested.</string> 5750 <string name="audio_loopback_resultcode_failbasic">Result: Fail - Basic latency not met.</string> 5751 <string name="audio_loopback_resultcode_failmpc">Result: Fail - Media Performance Class latency not met.</string> 5752 <string name="audio_loopback_resultcode_failpro">Result: Fail - Pro Audio max latency on one path not met.</string> 5753 <string name="audio_loopback_resultcode_failproanalog">Result: Fail - Pro Audio analog latency not met.</string> 5754 <string name="audio_loopback_resultcode_failprousb">Result: Fail - Pro Audio USB latency not met.</string> 5755 <string name="audio_loopback_resultcode_fail24bit">Result: Fail - 24-bit playback requirement no met.</string> 5756 <string name="audio_loopback_resultcode_failproaudiowired">Result: Fail - Pro Audio latency for wired path not met.</string> 5757 <string name="audio_loopback_resultcode_invalid">Result: Invalid result code.</string> 5758 5759 <!-- Audio Cold-Start Latency Test --> 5760 <string name="audio_coldstart_out_latency_test">Audio Cold Start Output Latency Test</string> 5761 <string name="audio_coldstart_in_latency_test">Audio Cold Start Input Latency Test</string> 5762 5763 <string name="audio_coldstart_output_info"> 5764 This test measures the time required to play audio from a suspended \"cold\" audio system. 5765 This time is defined as the \"cold start latency\". To pass this test, a maximum 5766 cold start latency time of 500ms or less is REQUIRED, while a time of 100ms or less 5767 is STRONGLY RECOMMENDED. (See <a href="https://source.android.com/compatibility/android-cdd#5_6_audio_latency">Android CDD § 5.6. Audio Latency</a>) 5768 \n\nTo run this test, it is required to have Tap & click sounds disabled in the device 5769 \"Sound & Vibration\" settings panel. Note that in some versions of Android, this setting 5770 may be called \"Touch sounds\". 5771 \n\nThe \"Java API\" and \"Native API\" allow for capturing performance data from the 5772 two streaming APIs. The cold start latency measurement need only pass for one API. 5773 The Native API generally gives the best performance. 5774 \n\nAlthough not part of the pass criteria, the test will also report \"open\" & 5775 \"start\" times. Open time is the time taken to allocate and prepare the player for the 5776 specified stream attributes. Start time is the time taken to start playing audio on an 5777 open stream. 5778 </string> 5779 <string name="audio_coldstart_input_info"> 5780 This test measures the time required to record audio from a suspended \"cold\" audio system. 5781 This time is defined as the \"cold start latency\". To pass this test, a maximum 5782 cold start latency time of 500ms or less is REQUIRED, while a time of 100ms or less 5783 is STRONGLY RECOMMENDED. (See <a href="https://source.android.com/compatibility/android-cdd#5_6_audio_latency">Android CDD § 5.6. Audio Latency</a>) 5784 \n\nThe \"Java API\" and \"Native API\" allow for capturing performance data from the 5785 two streaming APIs. The cold start latency measurement need only pass for one API. 5786 The Native API generally gives the best performance. 5787 \n\nAlthough not part of the pass criteria, the test will also report \"open\" & 5788 \"start\" times. Open time is the time taken to allocate and prepare the recorder for the 5789 specified stream attributes. Start time is the time taken to start recording audio on an 5790 open stream. 5791 </string> 5792 <string name="audio_coldstart_outputlbl">Output Cold Start Latency</string> 5793 <string name="audio_coldstart_inputlbl">Input Cold Start Latency</string> 5794 <string name="audio_coldstart_touchsounds_message"> 5795 Tap & click sounds are ENABLED. Please DISABLE Tap & click in the \"Sound & Vibration\" settings panel. 5796 \nNote that in some versions of Android, this setting may be called \"Touch sounds\". 5797 </string> 5798 <string name="audio_coldstart_notouchsounds_message">Tap & click sounds are DISABLED.</string> 5799 5800 <!-- Audio Frequency Line Test --> 5801 <string name="audio_frequency_line_test">Audio Frequency Line Test</string> 5802 <string name="audio_frequency_line_info"> 5803 The system will measure the frequency response of the left and right line outputs, 5804 by feeding them back thru the microphone conection with the loopback jack. 5805 This test requires the Loopback Plug. Please connect a Loopback Plug on the headset 5806 connector, and proceed with the instructions on the screen. 5807 </string> 5808 <string name="audio_frequency_line_instructions"> 5809 Please connect a "Loopback Plug" and press "Loopback Plug Ready". 5810 </string> 5811 <string name="audio_frequency_line_plug_ready_btn">Loopback Plug Ready</string> 5812 5813 <string name="audio_frequency_line_test_btn">Test</string> 5814 <string name="audio_frequency_line_results_text">Results...</string> 5815 5816 <!-- Audio Frequency Speaker Test --> 5817 <string name="audio_frequency_speaker_test">Audio Frequency Speaker Test</string> 5818 <string name="audio_frequency_speaker_info"> 5819 This test requires an external USB reference microphone. Please connect the USB microphone and proceed with the instructions on the screen. 5820 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. 5821 </string> 5822 <string name="audio_frequency_speaker_instructions"> 5823 Please connect an USB reference microphone and press "USB Reference microphone ready" 5824 </string> 5825 <string name="audio_frequency_speaker_usb_status">Waiting for USB microphone...</string> 5826 <string name="audio_frequency_speaker_mic_ready_btn">USB Reference microphone ready</string> 5827 <string name="audio_frequency_speaker_mic_ready_text">USB Audio device detected\n\nPlease set up Device Under test 5828 in quiet room, and Microphone 20 cms perpendicular to center of screen, then press TEST</string> 5829 <string name="audio_frequency_speaker_mic_not_ready_text">"No USB Audio device detected. Please reconnect."</string> 5830 <string name="audio_frequency_speaker_test_btn">Test</string> 5831 <string name="audio_frequency_speaker_results_text">Results...</string> 5832 5833 <!-- Audio Frequency Microphone Test --> 5834 <string name="audio_frequency_mic_test">Audio Frequency Microphone Test</string> 5835 <string name="frequency_mic_info"> 5836 This test requires an external USB reference microphone and external speakers. 5837 The test signals can be played from the device under test (DUT) or from a secondary device (e.g. when your DUT can’t support a USB microphone and external speakers simultaneously, or DUT does not have headphone output). 5838Follow the instructions on the screen to measure the frequency response for the built in microphone. 5839 </string> 5840 5841 <string name="frequency_mic_play">Play</string> 5842 <string name="frequency_mic_stop">Stop</string> 5843 <string name="frequency_mic_noise_instructions">TEST NOISE: Position speakers 40 cms from device under test. 5844 Press [PLAY] to play broadband white noise. Press [TEST] 5845 </string> 5846 <string name="frequency_mic_test_noise_btn">Test</string> 5847 <string name="frequency_mic_test_noise_result">Results...</string> 5848 5849 <string name="frequency_mic_test_usb_background_instructions">TEST USB BACKGROUND: Connect USB microphone and position it right next to microphone under test. 5850 No source of noise should be active during this test. Press [TEST]</string> 5851 <string name="frequency_mic_test_usb_background_btn">Test</string> 5852 <string name="frequency_mic_test_usb_background_result">Results...</string> 5853 5854 <string name="frequency_mic_test_usb_noise_instructions">TEST USB NOISE: Connect USB microphone and position it right next to microphone under test. 5855 Position speakers 40 cms from device under test. Press [PLAY] to play broadband white noise. Press [TEST]</string> 5856 <string name="frequency_mic_test_usb_noise_btn">Test</string> 5857 <string name="frequency_mic_test_usb_noise_result">Results...</string> 5858 5859 <string name="frequency_mic_test_global_result">Global Results...</string> 5860 5861 <!-- Audio Frequency Unprocessed Test --> 5862 <string name="audio_frequency_unprocessed_test">Audio Frequency Unprocessed Test</string> 5863 <string name="audio_frequency_unprocessed_info"> 5864 This test requires an external USB reference microphone, external speakers and a Sound Pressure Level meter. 5865 You can play the test signals from the device under test or from a secondary device. 5866 Follow the instructions on the screen to measure the frequency response for the built in microphone 5867 using UNPROCESSED audio source. 5868 If the Audio Frequency Unprocessed feature is defined in this system, success in all tests is mandatory to pass. 5869 If the feature is not defined, measurements are still needed, but success in all of them is not mandatory to pass. 5870 </string> 5871 <string name="audio_frequency_unprocessed_defined">Audio Frequency Unprocessed feature is defined. Success in all tests is mandatory to pass</string> 5872 <string name="audio_frequency_unprocessed_not_defined">Audio Frequency Unprocessed feature is NOT defined. Success in all test is NOT mandatory to pass</string> 5873 5874 <string name="unprocessed_play">Play</string> 5875 <string name="unprocessed_stop">Stop</string> 5876 5877 <string name="unprocessed_test_tone_instructions">TEST TONE: Press [PLAY] to play tone at 1 Khz. Measure sound SPL to be 94 dB 5878 right next to microphone under test. Press [TEST]</string> 5879 <string name="unprocessed_test_tone_btn">Test</string> 5880 <string name="unprocessed_test_tone_result">Results...</string> 5881 5882 <string name="unprocessed_test_noise_instructions">TEST NOISE: Position speakers 40 cms from device under test. 5883 Press [PLAY] to play broadband white noise. Press [TEST]</string> 5884 <string name="unprocessed_test_noise_btn">Test</string> 5885 <string name="unprocessed_test_noise_result">Results...</string> 5886 5887 <string name="unprocessed_test_usb_background_instructions">TEST USB BACKGROUND: Connect USB microphone and position it right next to microphone under test. 5888 No source of noise should be active during this test. Press [TEST]</string> 5889 <string name="unprocessed_test_usb_background_btn">Test</string> 5890 <string name="unprocessed_test_usb_background_result">Results...</string> 5891 5892 <string name="unprocessed_test_usb_noise_instructions">TEST USB NOISE: Connect USB microphone and position it right next to microphone under test. 5893 Position speakers 40 cms from device under test. Press [PLAY] to play broadband white noise. Press [TEST]</string> 5894 <string name="unprocessed_test_usb_noise_btn">Test</string> 5895 <string name="unprocessed_test_usb_noise_result">Results...</string> 5896 5897 <string name="unprocessed_test_global_result">Global Results...</string> 5898 5899 <!-- Audio Frequency Voice_Recognition Test --> 5900 <string name="audio_frequency_voice_recognition_test">Audio Frequency Voice Recognition Test</string> 5901 <string name="audio_frequency_voice_recognition_info"> 5902 This test requires an external USB reference microphone, external speakers and a Sound Pressure Level meter. 5903 You can play the test signals from the device under test or from a secondary device. 5904 Follow the instructions on the screen to measure the frequency response for the built in microphone 5905 using VOICE_RECOGNITION audio source. 5906 </string> 5907 <string name="vr_test_tone_instructions">TEST TONE: Press [PLAY] to play tone at 1 Khz. Measure sound to be 90 dB SPL right next to microphone under test. Press [TEST]</string> 5908 <string name="vr_test_noise_instructions">TEST NOISE: Position speakers 40 cms from device under test. 5909 Press [PLAY] to play broadband white noise. Press [TEST]</string> 5910 <string name="vr_test_usb_background_instructions">TEST USB BACKGROUND: Connect USB microphone and position it right next to microphone under test. 5911 No source of noise should be active during this test. Press [TEST]</string> 5912 <string name="vr_test_usb_noise_instructions">TEST USB NOISE: Connect USB microphone and position it right next to microphone under test. 5913 Position speakers 40 cms from device under test. Press [PLAY] to play broadband white noise. Press [TEST]</string> 5914 5915 <!-- Analog Headset Test --> 5916 <string name="audio_headset_audio_test">Analog Headset Audio Test</string> 5917 <string name="analog_headset_query">Does this Android device have an analog headset jack?</string> 5918 <string name="analog_headset_play">Play</string> 5919 <string name="analog_headset_stop">Stop</string> 5920 <string name="analog_headset_playback_prompt">Play a test tone and verify correct playback</string> 5921 <string name="analog_headset_playback_query">Was the audio correctly played through the headset?</string> 5922 <string name="analog_headset_keycodes_label">Headset key codes</string> 5923 <string name="analog_headset_headsethook">HEADSETHOOK</string> 5924 <string name="analog_headset_volup">VOLUME_UP</string> 5925 <string name="analog_headset_voldown">VOLUME_DOWN</string> 5926 <string name="analog_headset_test">Analog Headset Test</string> 5927 <string name="analog_headset_pass_noheadset">"PASS (No headset port available)"</string> 5928 <string name="analog_headset_pass">PASS</string> 5929 <string name="analog_headset_port_detected">"Analog port detected"</string> 5930 <string name="analog_headset_press_buttons">Press each button on the headset verify recognition</string> 5931 <string name="analog_headset_no_buttons">No buttons detected</string> 5932 <string name="analog_headset_headset_connected">Headset connected</string> 5933 <string name="analog_headset_no_headset">No Headset - Connect headset to 3.5mm analog jack</string> 5934 <string name="analog_headset_action_received">ACTION_HEADSET_PLUG received - </string> 5935 <string name="analog_headset_unplugged">Unplugged</string> 5936 <string name="analog_headset_plugged">Plugged</string> 5937 <string name="analog_headset_mic"> [mic]</string> 5938 <string name="analog_headset_reportnojack">No analog Jack. PASS</string> 5939 <string name="analog_headset_no_jack">No analog jack detected. Please connect a headset, or PASS</string> 5940 <string name="analog_headset_connect_headset">Please connect a headset</string> 5941 <string name="analog_headset_play_audio">Please test audio through the headset</string> 5942 <string name="analog_headset_test_buttons">Please test transport buttons</string> 5943 5944 <string name="analog_headset_test_info">This test tests the following functionality with respect to wired analog headsets.\n 5945 1. Correct audio playback.\n 5946 2. Plug intents.\n 5947 3. Headset keycodes.\n 5948 \nTo execute test:\n 5949 1. Plug in an Android-compatible, analog headset. Verify connection/recognition.\n 5950 2. Play test tone and verify correct behavior.\n 5951 3. Press headset buttons until all are recognized on the test screen.\n 5952 \nTo run this test it is necessary to have an Android device with a 3.5mm analog headset jack and a compatible analog headset with Hook, Volume Up and Volume Down buttons.\n 5953 \n(see <a href="https://source.android.com/devices/accessories/headset/plug-headset-spec">3.5 mm Headset: Accessory Specification</a> and 5954 <a href="https://source.android.com/compatibility/android-cdd#7_8_2_1_analog_audio_ports">Android CDD § 7.8.2.1. Analog Audio Ports</a>) 5955 </string> 5956 <!-- Audio AEC Test --> 5957 <string name="audio_aec_test">Audio Acoustic Echo Cancellation (AEC) Test</string> 5958 <string name="audio_aec_info"> 5959 The recording source VOICE_COMMUNICATION will be tested with/without the Acoustic Echo Canceller effect engaged. 5960 The Acoustic Coupling Factor (ACF) will be computed for each case. A successful test expects ACF less than 0.4 for AEC ON, 5961 and ACF greater than 0.6 for AEC OFF. 5962 This test requires a quiet environment, and no headphones or similar connected. 5963 This test must pass on any device which implements AEC. 5964 </string> 5965 <string name="audio_aec_instructions">Press [TEST] to play a voice recording twice with different parameters.</string> 5966 <string name="audio_aec_mandatory_test">Is AEC mandatory in this device?</string> 5967 <string name="audio_aec_no_aec_support">No AEC Support.</string> 5968 <string name="audio_aec_no_aec_pass">AEC is not supported on this device. Test may pass.</string> 5969 5970 <!-- Audio Connection Test --> 5971 <string name="audio_disconnect_test">Audio Stream Disconnect Test</string> 5972 <string name="audio_disconnect_info"> 5973 Tests that audio streams generate the correct stream disconnection events. Note that this 5974 test is only required for devices that support wired headset. 5975 \n\nTest Requirements 5976 \nA wired (analog or USB) headset peripheral, or analog loopback adapter. 5977 \n\nTest Process: 5978 \n1. Press the \"Start\" button. 5979 \n2. For each tested audio route: 5980 \n a. Connect the headset peripheral when instructed. 5981 \n b. Disconnect the headset peripheral when instructed. 5982 \n\nTest Criteria: 5983 \nThe test passes if all routes demonstrate the correct stream disconnection behavior. 5984 </string> 5985 <string name="audio_disconnect_wired_prompt">Does this device support an analog or USB audio peripheral?</string> 5986 <!--Audio Frequency Global strings --> 5987 <string name="af_button_play">Play</string> 5988 <string name="af_button_stop">Stop</string> 5989 5990 <string name="af_button_test">Test</string> 5991 <string name="af_test_results">Results...</string> 5992 <string name="af_global_test_results">Global Results...</string> 5993 <string name="af_no">No</string> 5994 <string name="af_yes">Yes</string> 5995 5996 <!-- AudioTap2Tone test --> 5997 <string name="audio_tap2tone">Audio Tap To Tone Test</string> 5998 <string name="audio_tap2tone_info">This tests the latency from a screen interaction to a 5999 resulting tone. This time is a combination of touch screen latency and audio latency.\nThis 6000 test is best conducted in a quiet room with the device laying on a table. 6001 \n\nTo execute test: 6002 \n1. Disconnect any wired or Bluetooth audio peripherals from the DUT. The Tap To Tone Test 6003 measures the time between a tap on the screen to a tone generated on the internal speaker. 6004 The internal microphone is used to detect both. 6005 \n2. Select the Audio API to test (\"Native\" has the lowest latency) and press the \"Start\" button. 6006 The test needs to pass for ONLY ONE API. 6007 \n3. Use your FINGERNAIL to tap ONCE on the field below to trigger the test tone. DO NOT leave 6008 the finger resting on the test field. A strong \"tick\" sound from the fingernail striking 6009 the display is necessary to register the start of the test process. 6010 \n4. After tapping ONCE, wait until the results are displayed in the field above the 6011 waveform display before tapping for the next test run. 6012 \nFive successful tests runs are required to determine if the test as a whole succeeds. 6013 \n5. Press the \"Stop\" button to conclude the test. The results will be displayed along with the passing/failing measurement and requirement. 6014 \n\n(see <a href="https://source.android.com/compatibility/12/android-12-cdd#56_audio_latency">Android CDD § 5.6. Audio Latency</a>) 6015 </string> 6016 <string name="audio_tap2tone_too_few">Not enough edges. Use fingernail.</string> 6017 <string name="audio_tap2tone_too_many">Too many edges. Use fingernail. Ensure there is 6018 no background noise.</string> 6019 <string name="audio_tap2tone_buffer_frames">Buffer Frames: </string> 6020 <string name="audio_tap2tone_bad_streams">Can\'t open streams.</string> 6021 <string name="audio_tap2tone_noio">No mic and/or speaker. PASS</string> 6022 6023 <!-- Strings for 6DoF test --> 6024 <string name="six_dof_test">6DoF Test</string> 6025 <string name="action_settings">Settings</string> 6026 <string name="start">Start</string> 6027 <string name="motion_tracking_permission">"Motion Tracking permission needed!"</string> 6028 <string name="translations">Translations:</string> 6029 <string name="rotations">Rotations:</string> 6030 <string name="action_place_marker">Place Marker</string> 6031 <string name="markers">Markers:\n</string> 6032 <string name="title_activity_cts">CTSActivity</string> 6033 <string name="stop">Stop!</string> 6034 <string name="stop_message">Mark where you are standing with something like a piece of card and 6035 then press ready to record this waypoint 6036 </string> 6037 <string name="ready">Ready</string> 6038 <string name="initial">First Waypoint</string> 6039 <string name="phase1_initial_message">When you are ready to place your first waypoint, place a 6040 marker at the devices current location. Use something that will allow you to put the device 6041 in the exact same position and orientation on the second lap. Then, while the device is on 6042 the marker, click the turquoise action button to record the first waypoint.\n\nStart walking 6043 in a direction. The button will appear again when you have walked far enough. Place a marker 6044 at the device\'s location and press the button to record a waypoint. You cannot place 6045 waypoints in a straight line, so for your 3rd waypoint turn 90 degrees and walk in a 6046 direction that will make a triangle out of your 3 waypoints. 6047 </string> 6048 <string name="phase2_initial_message">You now need to visit each waypoint, clicking the 6049 turquoise action button at each one. You need to reach each waypoint in 20 seconds. While 6050 you are on your way to the waypoints, the camera preview will rotate. You will need to 6051 rotate the device to match the rotation of the camera preview. A box will be shown to help 6052 you. It shows the device\'s current rotation and will change color based on whether you are 6053 close enough to the required rotation. Red if you are failing, green if you are passing. 6054 When you have reached the next waypoint, the device can be returned to its original 6055 rotation. 6056 </string> 6057 <string name="last">Go back to the first waypoint</string> 6058 <string name="last_message">Now go back to the first waypoint and press ready to finish the 6059 first lap. 6060 </string> 6061 <string name="got_it">Got it!</string> 6062 <string name="lap2_instructions">Now, go to each waypoint (including your initial 6063 one) and click the turquoise action button. Then move on to the next waypoint and do the 6064 same.\nThe last waypoint should be the first waypoint again. 6065 </string> 6066 <string name="test1_pass2">Pass 2</string> 6067 <string name="results">Results</string> 6068 <string name="overall_instructions">These tests are designed to verify the correctness and 6069 accuracy of a 6DoF enabled device. There will be 3 phases to these tests, each testing a 6070 different part of 6DoF functionality. 6071 </string> 6072 <string name="phase1_description">This first test will test the accuracy of the device. It will 6073 ask you to mark out 4 waypoints and then return to the original waypoint to complete the 6074 lap. After this you will then need to do another lap without any HUD information. At the 6075 end, the pairs of waypoints and the path you travelled will be compared and you will be 6076 given a result. 6077 </string> 6078 <string name="phase2_description">This test will test the robustness of the device. Using the 6079 same 4 waypoints as before, you will need to do a lap, reaching each waypoint in the 6080 allotted time.\nWhile you are on your way to the waypoints, the camera preview will rotate. 6081 You will need to rotate the device to match the rotation of the camera preview. A box will 6082 be shown to help you. It shows the device\'s current rotation and will change color based 6083 on whether you are close enough to the required rotation. Red if you are failing, green if 6084 you are passing. When you have reached the next waypoint, the device can be returned to 6085 its original rotation. 6086 </string> 6087 <string name="phase3_description">Now we will test the AR capability of the device. Again, you 6088 will need to do a lap of the waypoints, but this time between each waypoint the device will 6089 overlay hoops that you must pass the device through as you go along. 6090 </string> 6091 <string name="distance">Distance from last waypoint:</string> 6092 <string name="obj_return_to_initial_waypoint">Return to initial waypoint</string> 6093 <string name="waypointPlaced">Waypoint placed!</string> 6094 <string name="undo">undo</string> 6095 <string name="distance_remaining">Distance Remaining:\n</string> 6096 <string name="waypoint_differences">Waypoints</string> 6097 <string name="path_differences">Paths</string> 6098 <string name="error_distance">Not far away enough from other waypoints!</string> 6099 <string name="error_area">Not enough area covered.</string> 6100 <string name="passed">Passed!</string> 6101 <string name="failed">Failed!</string> 6102 <string name="test_failed">Test Failed!</string> 6103 <string name="error_start_point">Not close enough to initial waypoint!</string> 6104 <string name="waypoint_distance">Waypoint %1$s: %2$s</string> 6105 <string name="total">Total %1$s</string> 6106 <string name="path">Path %1$s: %2$s</string> 6107 <string name="fail">Fail</string> 6108 <string name="pass">Pass</string> 6109 <string name="info">Info</string> 6110 <string name="coming_soon">Coming soon!</string> 6111 <string name="motion_tracking_invalid_state">Motion Tracking has entered an invalid state 6112 </string> 6113 <string name="action_xml">XML</string> 6114 <string name="error_null_fragment">UI fragment was null, couldn\'t do callback to listener 6115 </string> 6116 <string name="error_retained_fragment_null">DataFragment is null</string> 6117 <string name="time_remaining">%1$s seconds remaining to get to next waypoint</string> 6118 <string name="action_skip_to_2nd">Skip to 2nd Test</string> 6119 <string name="failed_pause_resume">Test Failed because Test Activity was paused</string> 6120 <string name="action_overlapping_outlines">Overlapping Outlines</string> 6121 <string name="action_overlapping_filled">Overlapping Filled</string> 6122 <string name="time">Time</string> 6123 <string name="rotation_result">Rotation</string> 6124 <string name="action_separate_outlines">Separate Outlines</string> 6125 <string name="action_separate_filled">Separate Filled</string> 6126 <string name="action_one">One Rectangle</string> 6127 <string name="rotation_mode">Change rotation mode</string> 6128 <string name="phase3_initial_message">Go through the rings as you visit waypoints.</string> 6129 <string name="rings">Rings</string> 6130 <string name="rings_entered">Rings collected %1$s/%2$s</string> 6131 <string name="error_rings_not_entered">You haven\'t collected all the rings in this path! 6132 </string> 6133 <string name="save">Save</string> 6134 6135 <string-array name="initial_waypoint"> 6136 <item>Find a place for your first waypoint</item> 6137 <item>Go to initial waypoint</item> 6138 </string-array> 6139 6140 <string-array name="next_waypoint"> 6141 <item>Find a suitable place for waypoint 0</item> 6142 <item>Go to waypoint 0</item> 6143 </string-array> 6144 6145 <string-array name="phase"> 6146 <item>Phase 1</item> 6147 <item>Phase 2</item> 6148 <item>Phase 3</item> 6149 </string-array> 6150 6151 <string-array name="phase_descriptions"> 6152 <item>@string/phase1_description</item> 6153 <item>@string/phase2_description</item> 6154 <item>@string/phase3_description</item> 6155 </string-array> 6156 6157 <!-- Strings for setting and restoring default dialer for voicemail tests --> 6158 <string name="voicemail_restore_default_dialer_description">Restore the default dialer setting by going to Default apps -> Phone app</string> 6159 <string name="voicemail_restore_default_dialer_button">Restore the default dialer"</string> 6160 <string name="voicemail_default_dialer_already_set">Default dialer already set</string> 6161 <string name="voicemail_default_dialer_already_restored">Default dialer already restored</string> 6162 <string name="voicemail_set_default_dialer_description">Before the test, the CTS verifier should be set to the default dialer</string> 6163 <string name="voicemail_set_default_dialer_button">Set CTS verifier as default dialer"</string> 6164 6165 <!-- Strings for voicemail broadcast test --> 6166 <string name="voicemail_broadcast_test">Voicemail Broadcast Test</string> 6167 <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> 6168 <string name="voicemail_broadcast_no_carrier_support">The carrier does not support voicemail, this test is not applicable.</string> 6169 <string name="voicemail_leave_voicemail">Send a voicemail to the device, CTS verifier should receive a voicemail notification broadcast</string> 6170 <string name="voicemail_broadcast_received">Voicemail broadcast Received</string> 6171 6172 <!-- Strings for VisualVoicemailService test --> 6173 <string name="visual_voicemail_service_test">VisualVoicemailService Test</string> 6174 <string name="visual_voicemail_service_instructions">This test verifies that the VisualVoicemailService can receive SIM inserted and removed events</string> 6175 <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> 6176 <string name="visual_voicemail_service_remove_sim_ok">Ok</string> 6177 <string name="visual_voicemail_service_remove_sim_not_applicable">Not applicable</string> 6178 <string name="visual_voicemail_service_insert_sim">Insert SIM</string> 6179 <string name="visual_voicemail_service_insert_sim_received">Service connection event received</string> 6180 <string name="visual_voicemail_service_remove_sim">Remove SIM</string> 6181 <string name="visual_voicemail_service_remove_sim_received">SIM removal event received</string> 6182 6183 <!-- Strings for CallSettingsCheck test --> 6184 <string name="call_settings_check_test">Hide voicemail in call settings test</string> 6185 <string name="call_settings_check_instructions">This test verifies that the default dialer can 6186 hide voicemail settings in the call settings menu by using 6187 TelephonyManager.METADATA_HIDE_VOICEMAIL_SETTINGS_MENU 6188 </string> 6189 <string name="open_call_settings_explanation">Tap the button, and verify that \"voicemail\" does 6190 not exist in the call settings 6191 </string> 6192 <string name="open_call_settings">Open call settings</string> 6193 <string name="voicemail_hidden">\"Voicemail\" does not exist</string> 6194 <string name="voicemail_not_hidden">\"Voicemail\" exists</string> 6195 6196 <!-- Strings for DialerIncomingCall test --> 6197 <string name="dialer_incoming_call_test">Dialer Receives Incoming Call</string> 6198 <string name="dialer_incoming_call_test_instructions">This test verifies that the default dialer 6199 can receive incoming calls after it has been set. 6200 </string> 6201 <string name="dialer_incoming_call_detected">Detected the incoming call. Activity passed.</string> 6202 <string name="dialer_check_incoming_call_explanation">Call the device and end the call in the 6203 pop up in-call UI.</string> 6204 <string name="dialer_check_incoming_call">Verify Call Received</string> 6205 6206 <!-- Strings for VoicemailSettingsCheck test --> 6207 <string name="ringtone_settings_check_test">Hide settings in voicemail test</string> 6208 <string name="ringtone_settings_check_instructions">This test verifies that voicemail settings 6209 accessible with public API can be hidden when launching 6210 TelephonyManager.ACTION_CONFIGURE_VOICEMAIL with EXTRA_HIDE_PUBLIC_SETTINGS. 6211 </string> 6212 <string name="open_voicemail_settings_explanation">Tap the button, ringtone and virbration 6213 settings does not exist in the voicemail settings. 6214 </string> 6215 <string name="open_voicemail_settings">Open voicemail settings</string> 6216 <string name="ringtone_hidden">Ringtone settings does not exist</string> 6217 <string name="ringtone_not_hidden">Ringtone settings exists</string> 6218 6219 <!-- Strings for DialerShowsHunOnIncomingCallActivity test --> 6220 <string name="dialer_shows_hun_test">Dialer Shows HUN on Incoming Call</string> 6221 <string name="dialer_shows_hun_test_instructions">This test verifies that the default dialer 6222 shows a heads up notification on incoming call, and that only one notification is shown. 6223 </string> 6224 <string name="dialer_shows_hun_explanation">Call the device. 6225 Check the box if the heads up notification was shown containing the text 6226 \"CTS Incoming Call Notification\", and only one incoming call notification was shown. 6227 Also a pop up CtsVerifier in call UI will show. 6228 </string> 6229 <string name="dialer_shows_hun_check_box">HUN shown and meets criteria specified above.</string> 6230 <string name="dialer_incoming_call_hun_teaser">Incoming Call</string> 6231 <string name="dialer_incoming_call_hun_desc">CTS Incoming Call Notification</string> 6232 6233 <!-- Strings for DialerImplementsTelecomIntentsActivity test --> 6234 <string name="dialer_telecom_intents_test">System Implements Telecom Intents</string> 6235 <string name="dialer_telecom_intents_test_instructions">This test verifies that the system handles 6236 the specified Telecom Intents. 6237 </string> 6238 <string name="dialer_check_intents_implemented_explanation">Press the buttons below to launch settings activities. 6239 Check the associated box if the activity loads and was launched succesfully.</string> 6240 <string name="dialer_telecom_intents_call_settings">Launch call settings</string> 6241 <string name="dialer_telecom_intents_short_sms">Launch short sms answer settings</string> 6242 <string name="dialer_telecom_intents_calling_accounts">Launch calling accounts settings</string> 6243 <string name="dialer_telecom_intents_accessibility_settings">Launch accessibility settings</string> 6244 <string name="dialer_check_intents_check_box">Setting Launched</string> 6245 6246 <!-- USB Audio Peripheral Tests --> 6247 <string name="usbaudio_results_text">Results...</string> 6248 6249 <!-- USB Audio Peripheral Attributes Test --> 6250 <string name="usbaudio_attribs_test"> USB Audio Peripheral Attributes Test</string> 6251 6252 <string name="usbaudio_attribs_info">This test tests that the USB Audio HAL returns the 6253 expected set of attributes for a well-known USB audio peripheral. See the 6254 <a href="https://source.android.com/compatibility/cts/usb-audio#recommended-peripherals"> 6255 Mandated Peripherals 6256 </a> 6257 section of the <a href="https://source.android.com/compatibility/cts/usb-audio"> 6258 USB Audio CTS Verifier Tests 6259 </a>. 6260 for a list of supported USB audio peripherals. The attributes of the supported 6261 peripherals are stored in the app in a set of \"Peripheral Profiles\".\n\n 6262 To execute the test:\n 6263 1. Specify whether or not the DUT supports USB host mode (CDD 5.10 C-1-3). If not the test 6264 simply passes. 6265 2. Plug in a supported USB Audio Peripheral.\nThe peripheral\'s attributes will be 6266 displayed along with the name of the associated profile. If the peripheral matches the 6267 profile, the test passes. If not, the mismatches are displayed. 6268 </string> 6269 6270 <!-- USB Audio Peripheral Play Test --> 6271 <string name="usbaudio_play_test"> USB Audio Peripheral Play Test</string> 6272 <string name="usbaudio_play_info"> 6273 This test requires that you have connected a USB Audio Interface peripheral and 6274 some way to monitor the output. Press the \"Play\" button and verify that a tone is produced. 6275 </string> 6276 6277 <!-- USB Audio Peripheral Record Test --> 6278 <string name="usbaudio_record_test"> USB Audio Peripheral Record Test</string> 6279 <string name="usbaudio_record_info"> 6280 This test requires that you have connected a USB Audio Interface peripheral. 6281 Connect the outputs to the inputs (with patch cables). Start playback by pressing the 6282 \"Record Loopback\" button and verify that the recorded signal is displayed in the wave 6283 display view. (It may be necessary to adjust the input controls on the peripheral). 6284 </string> 6285 6286 <!-- USB Audio Peripheral Buttons Test --> 6287 <string name="usbaudio_buttons_test"> USB Audio Peripheral Buttons Test</string> 6288 <string name="usbaudio_buttons_info"> 6289 This test requires that you have connected a USB Audio headset that supports the 6290 Android USB audio headset buttons specification. Press each 6291 \"transport\" button and verify that it is recognized by the test. When each of the 6292 buttons has been recognized the \"pass\" button will be enabled. 6293 </string> 6294 6295 <!-- Pro Audio Test --> 6296 <string name="proaudio_test">Pro Audio Test</string> 6297 <string name="proaudio_info">This tests that any device claiming \"Pro Audio\" meets the 6298 requirements specified in the 6299 <a href="https://source.android.com/compatibility/12/android-12-cdd#510_professional_audio"> 6300 CDD section 5.10. Professional Audio</a> 6301 \n\nTo execute the test: 6302 \n1. Note that all required flags report \"true\" 6303 \n2. If the DUT supports HDMI: 6304 \n a. Click the \"Has HDMI Support\" checkbox 6305 \n b. Connect an HDMI device to the DUT 6306 \n c. Verify that the reported HDMI attributes meet the specification. 6307 \n\nNote that the latency measurement for Pro Audio has been moved to the 6308 Audio Loopback Latency Test 6309 </string> 6310 <string name="proaudio_hdmi_infotitle">HDMI Support</string> 6311 <string name="proaudio_hdmi_message">Please connect an HDMI peripheral to validate 6312 HDMI output attributes. 6313 </string> 6314 6315 <!-- Telecom tests --> 6316 <string name="telecom_enable_phone_account_test"> Telecom Enable Phone Account Test</string> 6317 <string name="telecom_enable_phone_account_info"> 6318 This test verifies that a third party ConnectionService can be enabled by the user. 6319 </string> 6320 <string name="telecom_enable_phone_account_step_1"> 6321 Click the button below to register a test PhoneAccount and ConnectionService. 6322 </string> 6323 <string name="telecom_enable_phone_account_register_button">Register Phone Account</string> 6324 <string name="telecom_enable_phone_account_step_2"> 6325 In the Calling accounts settings, choose "All calling accounts" and enable the "CTS Verifier Test" account. 6326 On AOSP this is accessible from: Phone app > Settings > Calls > Calling Accounts. 6327 Once you have completed this step, return here and click the Confirm button. 6328 </string> 6329 <string name="telecom_enable_phone_account_confirm_button">Confirm</string> 6330 6331 <string name="telecom_outgoing_call_test">Telecom Outgoing Call Test</string> 6332 <string name="telecom_outgoing_call_test_info">This test verifies that the default 6333 dialer on the system is able to make a call using a third-party ConnectionService.</string> 6334 <string name="telecom_outgoing_call_step_1"> 6335 Click the button below to register a test PhoneAccount and ConnectionService. You will be 6336 taken to the phone account selection screen. Please enable the "CTS Verifier Test" 6337 account and select it as the default account for outgoing calls. Once you have completed 6338 this step, return here and click the "Confirm Phone Account" button. 6339 </string> 6340 <string name="telecom_outgoing_call_register_enable_phone_account_button"> 6341 Register and Enable Phone Account 6342 </string> 6343 <string name="telecom_outgoing_call_confirm_register_button">Confirm Phone Account</string> 6344 <string name="telecom_outgoing_call_step_2"> 6345 Click the button below to dial an outgoing call. This will populate the default dialer 6346 app with a dummy phone number. Initiate the phone call from the dialer app, then return 6347 to this screen while the call is still in progress. 6348 </string> 6349 <string name="telecom_outgoing_call_dial_button">Dial</string> 6350 <string name="telecom_outgoing_call_step_3"> 6351 Click the button below to confirm that the ongoing outgoing call was correctly made. 6352 </string> 6353 <string name="telecom_outgoing_call_confirm_button">Confirm</string> 6354 6355 <string name="telecom_audio_call_test">Telecom Call Audio Test</string> 6356 <string name="telecom_audio_call_test_info">This test verifies that there are no audio 6357 issues when starting a sim call while in an active self-managed call. Note, this test 6358 requires the device under test to have an active sim with service. 6359 </string> 6360 <string name="telecom_status_image_description"> The image represents the status of the step 6361 in the test. The start state is indeterminate which is a question mark image. If the test step 6362 passes a green check will be show. Otherwise, a red x will show which means the test failed at 6363 the step.</string> 6364 <string name="tel_as1_instructions">set default outgoing phone account to a SIM based account 6365 </string> 6366 <string name="tel_as2_instructions"> 6367 Click the button below to initiate a self-managed call. Once clicked, you should hear an 6368 audio clip looping in whichever audio route is active (e.g. earpiece). 6369 </string> 6370 <string name="tel_as3_instructions">Click the button below to confirm the audio from the 6371 self-managed call is audible. Hearing the audio means the self-managed call was created 6372 successfully. 6373 </string> 6374 <string name="tel_as4_instructions">Now, enter a valid phone number and start an active sim 6375 based call. Ensure call audio is working both ways and end the sim call. 6376 </string> 6377 <string name="tel_as5_instructions">verify there were no sim call audio issues 6378 </string> 6379 <string name="tel_as6_instructions"> The self-managed call should resume playing audio. 6380 Hold your ear to the phone and verify the call audio is playing. 6381 </string> 6382 <string name="tel_verify_self_managed_audio_text">verify self-managed audio</string> 6383 <string name="tel_verify_sim_audio_text">verify sim call audio</string> 6384 <string name="tel_dial_sim_call_text">dial sim call</string> 6385 <string name="tel_set_default_outgoing_account_text">set default (optional)</string> 6386 <string name="tel_verify_start_state">verify start state</string> 6387 <string name="tel_start_self_managed_call_text">start self-managed call</string> 6388 <string name="tel_enter_phone_number_text">Enter number here</string> 6389 <string name="tel_enter_phone_number_autofill_hints_text">phoneNumber</string> 6390 <string name="tel_go_back_to_test_text">Go back to test</string> 6391 6392 <string name="telecom_incoming_call_test">Telecom Incoming Call Test</string> 6393 <string name="telecom_incoming_call_test_info">This test verifies that the default 6394 dialer on the system is able to receive a call from a third-party connection service. 6395 </string> 6396 <string name="telecom_incoming_call_step_1"> 6397 Click the button below to register a test PhoneAccount and ConnectionService. You will be 6398 taken to the phone account selection screen. Please enable the "CTS Verifier Test" 6399 account. Once you have completed this step, return here and click the 6400 "Confirm Phone Account" button. 6401 </string> 6402 <string name="telecom_incoming_call_register_enable_phone_account_button"> 6403 Register and Enable Phone Account 6404 </string> 6405 <string name="telecom_incoming_call_confirm_register_button">Confirm Phone Account</string> 6406 <string name="telecom_incoming_call_step_2"> 6407 Click the button below to initiate an incoming call. The phone should start ringing. 6408 Answer the call, confirm that you can hear an audio clip with Eisenhower\'s voice, then 6409 return to this screen while the call is still ongoing. 6410 </string> 6411 <string name="telecom_incoming_call_dial_button">Dial</string> 6412 <string name="telecom_incoming_call_step_3"> 6413 Click the button below to confirm that the ongoing incoming call was properly answered and 6414 that audio is audible. 6415 </string> 6416 <string name="telecom_incoming_call_confirm_button">Confirm</string> 6417 <string name="telecom_incoming_self_mgd_test"> Incoming Self-Managed Connection Test</string> 6418 <string name="telecom_incoming_self_mgd_info"> 6419 This test verifies that an incoming call from a Self-Managed Connection Service will trigger 6420 a Telecom-managed incoming call UI when it is not possible to hold an ongoing call on the 6421 device. 6422 </string> 6423 <string name="telecom_incoming_self_mgd_step_1"> 6424 Click the button below to register a test self-managed ConnectionService. 6425 </string> 6426 <string name="telecom_incoming_self_mgd_register_button">Register Self-Managed ConnectionService</string> 6427 <string name="telecom_incoming_self_mgd_step_2"> 6428 Start two phone calls on the device under test; this generates a scenario where calls cannot 6429 be held when the incoming self-managed call is received. Click "verify calls" to confirm 6430 that the calls were started. 6431 </string> 6432 <string name="telecom_incoming_self_mgd_verify_call_button">Verify Calls</string> 6433 <string name="telecom_incoming_self_mgd_step_3"> 6434 Click the button below to start a test incoming self-managed call. Answer the call in the 6435 UI when prompted. 6436 </string> 6437 <string name="telecom_incoming_self_mgd_place_call_button">Start Self-Managed Call</string> 6438 <string name="telecom_default_dialer_test_title">Default Dialer Test</string> 6439 <string name="telecom_default_dialer_test_info"> 6440 This test verifies that a third party dialer can show an incoming call screen when the 6441 device is locked. 6442 </string> 6443 <string name="telecom_default_dialer_step_1"> 6444 Click the button below to set CtsVerifier as the default dialer. 6445 </string> 6446 <string name="telecom_default_dialer_set_third_party_dialer_button"> 6447 Set third party dialer 6448 </string> 6449 <string name="telecom_default_dialer_step_2"> 6450 Click the button to make sure that this phone is secured with a lock screen. 6451 </string> 6452 <string name="telecom_confirm_lock_screen">Confirm lock screen</string> 6453 <string name="telecom_default_dialer_step_3"> 6454 Click the button below to lock the phone and then call this device. Answer the incoming call 6455 in the UI when prompted without unlock the phone. 6456 </string> 6457 <string name="telecom_default_dialer_lock_button">Lock phone and dail</string> 6458 <string name="telecom_default_dialer_step_4"> 6459 Click the button below to confirm that the ongoing incoming call was answered when the 6460 device is locked. 6461 </string> 6462 <string name="telecom_default_dialer_end_button">End call and confirm</string> 6463 <string name="telecom_default_dialer_confirm_button">Confirm</string> 6464 <string name="telecom_in_call_ui_label">CtsVerifierInCallUi</string> 6465 <!-- Strings for SetNewPasswordComplexityTest --> 6466 <string name="set_complexity_test_title">Set New Password Complexity Test</string> 6467 <string name="set_complexity_test_message"> 6468 This test verifies that when an app prompts users to set a new screen lock of a certain complexity level, users cannot set a screen lock weaker than the specified complexity.\n 6469 \nClick the complexity level buttons one by one and make sure you can only set a screen lock not weaker than the types and minimum length specified on the right of each button. 6470 </string> 6471 <string name="set_complexity_high_txt">High</string> 6472 <string name="set_complexity_medium_txt">Medium</string> 6473 <string name="set_complexity_low_txt">Low</string> 6474 <string name="set_complexity_none_txt">None</string> 6475 <string name="set_complexity_high_desc"> 6476 PIN without repeating (4444) or ordered (1234, 4321, 2468) sequences, length at least 8; Or 6477 \nAlphabetic, length at least 6; Or 6478 \nAlphanumeric, length at least 6</string> 6479 <string name="set_complexity_medium_desc"> 6480 PIN without repeating (4444) or ordered (1234, 4321, 2468) sequences, length at least 4; Or 6481 \nAlphabetic, length at least 4; Or 6482 \nAlphanumeric, length at least 4</string> 6483 <string name="set_complexity_low_desc">Any pattern, PIN or password</string> 6484 <string name="set_complexity_none_desc">No restrictions</string> 6485 <!-- Strings for UnlockedDeviceRequiredTest --> 6486 <string name="unlock_req_config_lock_screen">Secure lock screen has not been set up. Go to 6487 Settings -> Security to set up a lock screen.</string> 6488 <string name="unlock_req_config_lock_screen_and_biometrics">Secure lock screen has not been set 6489 up. Go to Settings -> Security to set up a lock screen and biometric unlock.</string> 6490 <string name="unlock_req_config_biometrics">Biometric unlock has not been set up. Go to Settings 6491 -> Security to set up biometric unlock.</string> 6492 <string name="unlock_req_biometric_lock">Lock the screen, wait 5 seconds, then unlock with 6493 biometrics.</string> 6494 <!-- This message should only be displayed briefly immediately after the user has unlocked 6495 the device; as soon as key access is verified this message will be updated. --> 6496 <string name="unlock_req_unlocked">Verifying the key is accessible after the unlock...</string> 6497 <string name="unlock_req_credential_lock">Lock the screen, wait 5 seconds, then unlock with 6498 credentials.</string> 6499 <string name="unlock_req_successful">Test completed successfully.</string> 6500 <string name="unlock_req_failed_key_available_when_locked">Test failed; the key was available 6501 when the device was locked.</string> 6502 <string name="unlock_req_failed_key_unavailable_when_unlocked">Test failed; the key was not 6503 available when the device was unlocked.</string> 6504 <!-- While this state should never be reached since all possible states are accounted for 6505 it is included just in case. --> 6506 <string name="unlock_req_unknown_state">The test is in an unexpected state; please dismiss 6507 this dialog and restart the test.</string> 6508 6509 <!-- Notification Bubble Tests--> 6510 <string name="bubbles_notification_title">Bubble Notification Tests</string> 6511 <string name="bubbles_test_title">Bubble Tests</string> 6512 <string name="bubbles_test_info">This set of tests checks the settings, UI, and behaviour of 6513 bubble notifications. Bubbles are special notifications that can appear as a floating button 6514 on the screen along with a notification in the notification shade. When the floating button 6515 is tapped an activity is opened in a contained view and the notification is hidden from the 6516 shade.</string> 6517 <!-- Default settings --> 6518 <string name="bubbles_test_check_defaults_title">Check Default Settings</string> 6519 <string name="bubbles_test_check_defaults_verify">This step verifies the default bubble 6520 settings on the device. \n\n 6521 Bubbles are enabled at a feature level and at a per-app level.\n\n 6522 By default, bubbles are enabled at a feature level, but off for apps until the user opts in. 6523 \n\nIf the default settings are correct, the test will indicate that the state is correct. 6524 </string> 6525 <!-- Bubble button --> 6526 <string name="bubbles_test_bubble_button_title">Bubble Button</string> 6527 <string name="bubbles_test_bubble_button_verify">1. Click the button below to send a bubble 6528 notification.\n\n 6529 2. Pull down the notification shade and press the bubble button on the bottom right of the 6530 notification.\n\n 6531 3. Pass this test if tapping the bubble button opens the bubble.</string> 6532 <string name="bubbles_test_bubble_button_button">Send notification</string> 6533 <!-- Bubble preference selected --> 6534 <string name="bubbles_test_app_selected_title">Check Settings After Bubble Button</string> 6535 <string name="bubbles_test_app_selected_verify">When a notification is turned into a bubble 6536 via the bubble button, the app setting for bubbles will change to allow selected 6537 notifications to bubble. If the settings are right, the test will indicate that the state 6538 is correct.</string> 6539 <!-- Disable at feature level --> 6540 <string name="bubbles_test_disable_title">Disable Bubbles Feature</string> 6541 <string name="bubbles_test_disable_verify">Click the button to open notification settings, 6542 find Bubbles and turn the feature off. When the setting is off, the test will indicate that 6543 the state is correct.</string> 6544 <string name="bubbles_test_disable_button">Open settings</string> 6545 <!-- App settings available when disabled --> 6546 <string name="bubbles_test_enable_title">Enable Bubbles for CTS Verifier</string> 6547 <string name="bubbles_test_enable_verify">1. Click the button below and enable bubbles for the 6548 verifier app on the resulting screen, select "All conversations can bubble".\n\n 6549 2. You will be prompted to turn on bubbles for the device, turn them on.\n\n 6550 Once this is done, the test will indicate that the state is correct.</string> 6551 <string name="bubbles_test_enable_button">Open bubble settings</string> 6552 <!-- Send bubble --> 6553 <string name="bubbles_test_send_bubble_title">Send bubble notification</string> 6554 <string name="bubbles_test_send_bubble_verify">Click the button below and verify that there is a 6555 bubble on the screen and a notification in the notification shade. 6556 </string> 6557 <string name="bubbles_test_send_bubble_button">Send bubble notification</string> 6558 <!-- Suppress notification --> 6559 <string name="bubbles_test_suppress_notif_title">Hide notification</string> 6560 <string name="bubbles_test_suppress_notif_verify">Click the button below and verify that the 6561 bubble is still on the screen, but the notification is now hidden from the notification 6562 shade. 6563 </string> 6564 <string name="bubbles_test_suppress_notif_button">Update bubble to hide notification</string> 6565 <!-- Add notification --> 6566 <string name="bubbles_test_add_notif_title">Show notification</string> 6567 <string name="bubbles_test_add_notif_verify">Click the button below and verify that the bubble 6568 is still on the screen, the notification is now visible in the notification shade, and the 6569 bubble has a dot indicating the new message. 6570 </string> 6571 <string name="bubbles_test_add_notif_button">Update bubble to show notification</string> 6572 <!-- Remove bubble metadata --> 6573 <string name="bubbles_test_remove_metadata_title">Remove bubble</string> 6574 <string name="bubbles_test_remove_metadata_verify">Click the button below and verify that the 6575 bubble is removed from the screen, and the notification is still visible in the notification 6576 shade.</string> 6577 <string name="bubbles_test_remove_metadata_button">Remove bubble</string> 6578 <!-- Add bubble metadata --> 6579 <string name="bubbles_test_add_metadata_title">Add bubble</string> 6580 <string name="bubbles_test_add_metadata_verify">Click the button below and verify that the 6581 bubble appears on the screen, and the notification is still visible in the notification 6582 shade.</string> 6583 <string name="bubbles_test_add_metadata_button">Add bubble</string> 6584 <!-- Expand bubble --> 6585 <string name="bubbles_test_expand_bubble_title">Open bubble</string> 6586 <string name="bubbles_test_expand_bubble_verify">Tap on the bubble to open it, then tap on the 6587 bubble again to collapse it and return to this screen. Verify that after opening the bubble, 6588 there is no longer a notification for it visible in the notification shade.</string> 6589 <!-- Dismiss bubble --> 6590 <string name="bubbles_test_dismiss_title">Drag and dismiss bubble</string> 6591 <string name="bubbles_test_dismiss_verify">Click the button below and verify that the bubble 6592 is still on screen, and the notification is visible in the notification shade.\n\n 6593 Drag the bubble, while dragging a UI affordance should show. Verify that: \n\n 6594 1. Dragging and dropping the bubble on that UI affordance removes it from the screen.\n\n 6595 2. The notification should remain in the notification shade.</string> 6596 <string name="bubbles_test_dismiss_button">Update bubble to show notification</string> 6597 <!-- Dismiss notification --> 6598 <string name="bubbles_test_dismiss_notif_title">Dismiss notification</string> 6599 <string name="bubbles_test_dismiss_notif_verify">Click the button below and verify that a bubble 6600 appears on screen, and the notification is visible in the notification shade.\n\n 6601 Dismiss the notification from the notification shade and verify that the bubble remains on 6602 screen.</string> 6603 <string name="bubbles_test_dismiss_notif_button">Send bubble notification</string> 6604 <!-- Auto expand bubble --> 6605 <string name="bubbles_test_autoexpand_title">Auto expand bubble</string> 6606 <string name="bubbles_test_autoexpand_verify">Click the button below and verify that a bubble 6607 appears on screen, auto-expanded.</string> 6608 <string name="bubbles_test_autoexpand_button">Send auto-expanded bubble notification</string> 6609 <!--Overflow exists --> 6610 <string name="bubbles_test_overflow_title">Bubble overflow (empty)</string> 6611 <string name="bubbles_test_overflow_verify">Tap the bubble to expand it and verify there is an 6612 affordance to see previous bubbles. It should be empty right now and show an empty state 6613 message.</string> 6614 <!-- Bubbles appear in overflow --> 6615 <string name="bubbles_test_bubbles_in_overflow_title">Bubble overflow (with bubbles)</string> 6616 <string name="bubbles_test_bubbles_in_overflow_verify">1. Press the button below to create 6617 several bubbles.\n\n 6618 2. Expand the stack and drag down two of the bubbles to dismiss them.\n\n 6619 3. Tap on the bubble overflow, pass this test if the two bubbles you dismissed are in 6620 the overflow. </string> 6621 <string name="bubbles_test_bubbles_in_overflow_button">Send several bubbles</string> 6622 <!-- Add bubble from overflow --> 6623 <string name="bubbles_test_add_from_overflow_title">Add bubble from overflow</string> 6624 <string name="bubbles_test_add_from_overflow_verify">1. Expand the stack and open the bubble 6625 overflow.\n\n 2. Tap on a bubble in the overflow, pass this test if that bubble is opened 6626 and removed from the overflow.</string> 6627 <!-- Cancel removes bubbles in overflow --> 6628 <string name="bubbles_test_cancel_overflow_title">Cancel removes overflowed bubbles</string> 6629 <string name="bubbles_test_cancel_overflow_verify">1. Press the button below, it will cancel all 6630 previous bubble notifications and post one more.\n\n 6631 2. Expand that bubble, navigate to the overflow and ensure that it is empty.</string> 6632 <string name="bubbles_test_cancel_overflow_button">Cancel previous bubbles and post a 6633 single bubble</string> 6634 <!-- Tap on notification with bubble in the overflow --> 6635 <string name="bubbles_test_tap_notif_with_overflow_title">Tap on notification opens bubble 6636 </string> 6637 <string name="bubbles_test_tap_notif_with_overflow_verify">1. Press the button to create a 6638 bubble.\n\n 6639 2. Dismiss the bubble without opening it.\n\n 6640 3. Tap on the notification. Pass this test if the notification opened as a bubble.</string> 6641 <string name="bubbles_test_tap_notif_with_overflow_button">Send bubble</string> 6642 <!-- Portrait & landscape positioning --> 6643 <string name ="bubbles_test_expanded_position_title">Portrait and landscape positioning</string> 6644 <string name="bubbles_test_expanded_position_phone_verify">1. While in portrait orientation, 6645 tap on the bubble to open it.\n\n 6646 2. Verify that the bubbles show at the top of the screen.\n\n 6647 3. Rotate the device to landscape orientation.\n\n 6648 3. Verify that the bubbles are aligned to the left or right edge of the screen.</string> 6649 <string name="bubbles_test_expanded_position_largescreen_verify"> 6650 1. Tap the bubble to open it.\n\n 6651 2. Verify that the bubbles are aligned to the left or right edge of the screen.\n\n 6652 3. Rotate the device.\n\n 6653 4. Verify that the bubbles are aligned to the left or right edge of the screen.</string> 6654 <!-- Expanded view scrim --> 6655 <string name="bubbles_test_expanded_scrim_title">Expanded state has scrim</string> 6656 <string name="bubbles_test_expanded_scrim_verify">Expand the bubble and pass this test if the 6657 area below the bubble is dimmed (like when a dialog is opened).</string> 6658 <!-- IME insets --> 6659 <string name="bubbles_test_ime_title">IME behavior</string> 6660 <string name="bubbles_test_ime_verify">1. Tap on the bubble to open it.\n\n 6661 2. Tap the edit text in the bubble to bring up the IME.\n\n 6662 3. Pass this test if the IME appears and the edit text is still visible.</string> 6663 <!-- Expanded view min height --> 6664 <string name="bubbles_test_min_height_title">Expanded view min height</string> 6665 <string name="bubbles_test_min_height_verify">1. Press the button below to update the bubble to 6666 have the smallest height.\n\n 6667 2. Open the bubble, it will tell you if the height is correct.</string> 6668 <string name="bubbles_test_min_height_button">Send small height bubble</string> 6669 <!-- Expanded view max height --> 6670 <string name="bubbles_test_max_height_title">Expanded view max height</string> 6671 <string name="bubbles_test_max_height_verify">1. Press the button below to update the bubble to 6672 have the maximum height.\n\n 6673 2. Open the bubble, it will tell you if the height is correct.</string> 6674 <string name="bubbles_test_max_height_button">Send max height bubble</string> 6675 <!-- Low ram --> 6676 <string name="bubbles_test_lowram_title">No bubbles on low memory device</string> 6677 <string name="bubbles_test_lowram_verify">Click the button below and verify that a 6678 bubble does NOT appear on screen. Verify that there is a notification in the notification 6679 shade.</string> 6680 <string name="bubbles_test_lowram_button">Add bubble</string> 6681 <!-- Disable bubbles by config_supportsBubble --> 6682 <string name="bubbles_test_disable_config_title">No bubbles on bubbles disabled device</string> 6683 <string name="bubbles_test_disable_config_verify">Click the button below and verify that a 6684 bubble does NOT appear on screen. Verify that there is a notification in the notification 6685 shade.</string> 6686 <string name="bubbles_test_disable_config_button">Add bubble</string> 6687 <!-- Bubbles end of test summary --> 6688 <string name="bubbles_test_summary_title">Test Complete</string> 6689 <string name="bubbles_test_summary">%1$d out of %2$d tests passed</string> 6690 <string name="bubble_activity_title">Bubble Activity</string> 6691 <string name="bubble_test_state_correct">State is correct, pass the test.</string> 6692 <string name="bubble_test_state_waiting">State is not correct, waiting for the correct state. 6693 </string> 6694 <string name="bubble_test_ime_hint">Tap for IME</string> 6695 <string name="bubble_test_expanded_view">Bubble expanded view</string> 6696 6697 <!-- Toast test --> 6698 <string name="toast_title">Toast test (may auto pass if CtsVerifier isn\'t targeting 6699 S+)</string> 6700 <string name="toast_info">This test checks the behavior for toasts for apps targeting 6701 sdk S+ (31). Toasts are short messages that appear as popups for a limited amount of time. 6702 </string> 6703 <string name="toast_instructions_pre_s">No cts requirement for toasts for apps targeting 6704 pre-s. Auto pass this test.</string> 6705 <string name="toast_instructions_s">Press the button below to post a toast. Pass this 6706 test if a toast appears and has:\n 6707 \n\t1. a maximum of two lines 6708 \n\t2. an application icon 6709 </string> 6710 <string name="toast_post_button_label">Post toast</string> 6711 <string name="toast_long_text">Lorem ipsum dolor sit amet, consectetur adipiscing elit. 6712 Nam luctus eros ac interdum tincidunt. Vestibulum dignissim, metus nec tempor mollis, 6713 tortor leo aliquam est, eget rutrum mi nisi ut ligula. Quisque enim justo, tempus at 6714 ligula ac, porta posuere odio. Proin et tortor tincidunt, tempus ligula id, 6715 vestibulum mauris. Vivamus blandit tristique tempus. Integer dignissim purus eu nibh 6716 faucibus, eget dignissim eros gravida. Sed sit amet erat quis leo pharetra euismod vel at 6717 purus. Duis blandit, diam eu imperdiet pulvinar, erat odio eleifend augue, nec luctus 6718 lectus erat ac nibh. Nullam id enim metus. 6719 </string> 6720 6721 <!-- Strings for Instant Apps --> 6722 <string name="ia_instruction_heading_label">Instructions:</string> 6723 <string name="ia_instruction_text_photo_label">READ BEFORE STARTING TEST</string> 6724 <string name="ia_start_test_button_caption">Start Test</string> 6725 <string name="ia_install_dialog_title">Install Instant App</string> 6726 <string name="ia_install_dialog_text"> 6727 For this test you need to install CtsVerifierInstantApp.apk by running \n 6728 adb install -r --instant /path/to/CtsVerifierInstantApp.apk \n\n 6729 CtsVerifierInstantApp.apk can be found in android-cts-verifier.zip that you have downloaded. 6730 </string> 6731 <string name="ia_notification">Instant Apps Notification Test</string> 6732 <string name="ia_notification_info"> 6733 This test verifies that Instant Apps notification is shown when an Instant App is at foreground.\n\n 6734 - Read the message above the \"Start Test\" button for 6735 step-by-step instructions. 6736 </string> 6737 <string name="ia_notification_instruction_label">\n 6738 1. Click Start Test. \n\n 6739 2. An alert dialog with install instruction will be shown if the sample Instant App has not been installed, otherwise, the sample Instant App will be opened automatically. \n\n 6740 3. Drag down the notification bar when the sample Instant App is at foreground. \n\n 6741 4. Check if Instant App is shown in notifciation area with the following (Please expand the notification if it is collapsed): \n 6742 \u0020\u0020\u0020a. It provides information about Instant Apps not requiring installation and an action that provides more information about the Instant App. \n 6743 \u0020\u0020\u0020b. It provides an action allowing the user to launch the associated link with web browser. \n\n 6744 5. Click Pass button if all checks in step 4 passed, otherwise click Fail button. 6745 </string> 6746 <string name="ia_notification_instruction_label_no_app_market_version">\n 6747 1. Click Start Test. \n\n 6748 2. An alert dialog with install instruction will be shown if the sample Instant App has not been installed, otherwise, the sample Instant App will be opened automatically. \n\n 6749 3. Drag down the notification bar when the sample Instant App is at foreground. \n\n 6750 4. Check if Instant App is shown in notification area with information about Instant Apps not requiring installation and an action that provides more information about the Instant App (Please expand the notification if it is collapsed) \n\n 6751 5. Click Pass button if all checks in step 4 passed, otherwise click Fail button. 6752 </string> 6753 <string name="ia_recents">Instant Apps Recents Test</string> 6754 <string name="ia_recents_info"> 6755 This test verifies that Instant App can be accessed in Recent Apps screen.\n\n 6756 - Read the message above the \"Start Test\" button for 6757 step-by-step instructions. 6758 </string> 6759 <string name="ia_recents_instruction_label">\n 6760 1. Click Start Test. \n\n 6761 2. An alert dialog with install instruction will be shown if the sample Instant App has not been installed, otherwise, the sample Instant App will be opened automatically. \n\n 6762 3. Tap Recents button, verify the sample Instant App is shown in Recent Apps screen. \n\n 6763 4. Tap the sample Instant App in Recent Apps screen, verify the Instant App is opened in the foreground. \n\n 6764 5. Click Pass button if checks in step 3 and 4 passed, otherwise click Fail button. 6765 </string> 6766 <string name="ia_app_info">View/Delete Instant Apps Test</string> 6767 <string name="ia_app_info_info"> 6768 This test verifies that Instant App can be viewed and deleted in Settings.\n\n 6769 - Read the message above the \"Start Test\" button for 6770 step-by-step instructions. 6771 </string> 6772 <string name="ia_app_info_instruction_label">\n 6773 1. Click Start Test. \n\n 6774 2. An alert dialog with install instruction will be shown if the sample Instant App has not been installed, otherwise, the sample Instant App will be opened automatically. \n\n 6775 3. Open Settings App. \n\n 6776 4. Tap Apps & Notifications. \n\n 6777 5. Verify the sample Instant App can be found and it is shown as \"Instant App\". \n\n 6778 6. Verify there is an action allowing user to clear/delete app. \n\n 6779 7. Click Pass button if checks in step 5 and 6 passed, otherwise click Fail button. 6780 </string> 6781 6782 <string name="uap_test_no">No</string> 6783 <string name="uap_test_yes">Yes</string> 6784 <string name="uap_test_info">Info</string> 6785 <string name="uap_test_question">Does this device allow for the connection of a USB audio peripheral?\nNote: phones and tablets generally do, watches and automobiles generally do not.</string> 6786 <string name="uap_refmic_question">Does this device allow for the connection of a USB reference microphone?</string> 6787 <string name="uap_test_hostmode_info_caption">USB Host Mode Audio Required</string> 6788 <string name="uap_test_hostmode_info_text">This test requires a USB audio peripheral be 6789 connected to the device. 6790 The DUT may not support USB Host Mode Audio, either because it does not have a 6791 USB port, or USB Host Mode Audio has been removed from the OS. In this case, the test can be 6792 passed by pressing the \"No\" button and indicating \"Test Pass\" at the bottom. 6793 \n\nNote: Handheld devices supporting USB host mode MUST support USB audio class (CDD 7.7 .2/H-1-1) 6794 \n\nNote: Devices declaring feature android.hardware.audio.pro MUST implement USB host mode (CDD 5.10 C-1-3). 6795 Devices that omit a 4 conductor 3.5mm audio jack MUST support USB audio class (CDD 5.10 C-3-1). 6796 </string> 6797 <string name="uap_test_playing">Playing. Now press stop.</string> 6798 6799 <string name="refmic_test_no">No</string> 6800 <string name="refmic_test_yes">Yes</string> 6801 <string name="refmic_test_info">Info</string> 6802 <string name="refmic_test_question">Does this device allow for the connection of a USB reference microphone?</string> 6803 <string name="ref_mic_dlg_caption">Reference Mic Required</string> 6804 <string name="ref_mic_dlg_text">This test requires a USB Reference Mic to be connected to the device. 6805 If the device under test does not support USB Host Mode Audio (either because it does not have a 6806 USB port, or USB Host Mode Audio has been removed from the OS) you can be granted a provisional 6807 pass on this test by pressing the \"No\" button and indicating \"Test Pass\" at the bottom.\n 6808 Note: Handheld devices supporting USB host mode MUST support USB audio class (CDD 7.7 .2/H-1-1)\n 6809 Note: Devices declaring feature android.hardware.audio.pro MUST implement USB host mode (CDD 5.10 C-1-3) and if they omit a 4 conductor 3.5mm audio jack MUST support USB audio class (CDD 5.10 C-3-1) 6810 </string> 6811 6812 <string name="loopback_test_question">Does this device allow for the connection of a loopback audio peripheral?</string> 6813 <string name="loopback_dlg_caption">Loopback Peripheral Required</string> 6814 6815 <string name="display_cutout_test">DisplayCutout Test</string> 6816 <string name="display_cutout_test_instruction">\n 6817 This test is to make sure that the area inside the safe insets from the DisplayCutout should be:\n 6818 1. Visible\n 6819 2. Clickable.\n 6820 </string> 6821 6822 <!-- TTS Test Resources --> 6823 <string name="tts_test">TTS Test</string> 6824 <string name="tts_test_info"> 6825 1. Install the CtsTtsEngineSelectorTestHelper and CtsTtsEngineSelectorTestHelper2 apps on the device.\n 6826 2. Click on the "Go To Accessibility Settings" button.\n 6827 3. Go to Text-to-speech output > Preferred engine.\n 6828 4. Ensure that two engines are listed, both named "TTS CTS Test Helper App".\n 6829 5. Ensure that each engine can be selected. 6830 </string> 6831 <string name="tts_test_steps"> 6832 1. Install the CtsTtsEngineSelectorTestHelper and CtsTtsEngineSelectorTestHelper2 apps on the device.\n 6833 2. Click on the "Go To Accessibility Settings" button.\n 6834 3. Go to Text-to-speech output > Preferred engine.\n 6835 4. Ensure that two engines are listed, both named "TTS CTS Test Helper App".\n 6836 5. Ensure that each engine can be selected. 6837 </string> 6838 <string name="tts_accessibility_settings_button">Go To Accessibility Settings</string> 6839 6840 <!-- Strings for SecurityModeFeatureVerifierActivity test --> 6841 <string name="security_mode_feature_verifier_test">SecurityModeFeatureVerifier Test</string> 6842 <string name="security_mode_feature_verifier_instructions">This test verifies that the PackageManager.FEATURE_SECURITY_MODEL_COMPATIBLE feature is present.</string> 6843 <string name="handheld_or_tablet_text_before_test">Is this a handheld or tablet device?</string> 6844 <string name="handheld_or_tablet_yes">Yes</string> 6845 <string name="handheld_or_tablet_not_applicable">Not applicable</string> 6846 6847 <!-- AudioDescriptor Test --> 6848 <string name="audio_descriptor_test">Audio Descriptor Test</string> 6849 <string name="audio_descriptor_test_info"> 6850 This test tests if the reported AudioDescriptor is valid and necessary.\n 6851 AudioDescriptor must only be used to report audio device capabilities that are not able to 6852 describe by Android defined enums.\n 6853 \nTo execute test:\n 6854 1. Plug in HDMI cable if HDMI is supported on the device.\n 6855 2. The test will execute automatically and verify the reported AudioDescriptor when the 6856 activity is created and when audio device connection is changed. 6857 </string> 6858 <string name="audio_descriptor_HDMI_support_label">HDMI support:</string> 6859 <string name="audio_descriptor_has_hdmi_support">Has HDMI support</string> 6860 <string name="audio_descriptor_NA">N/A</string> 6861 <string name="audio_descriptor_hdmi_pending">No HDMI detected. Pending…</string> 6862 <string name="audio_descriptor_pass">Pass</string> 6863 <string name="audio_descriptor_hdmi_not_reported">No HDMI device connected</string> 6864 <string name="audio_descriptor_standard_none">Standard is none.</string> 6865 <string name="audio_descriptor_is_null">Audio descriptor is null.</string> 6866 <string name="audio_descriptor_unrecognized_standard">Standard %1$d is unrecognized.</string> 6867 <string name="audio_descriptor_length_error"> 6868 The length of short audio descriptor is %1$d, but it is expected to be 3. 6869 </string> 6870 <string name="audio_descriptor_cannot_get_hal_version">Cannot get audio HAL version</string> 6871 <string name="audio_descriptor_invalid_hal_version">Invalid audio HAL version %1$s</string> 6872 <string name="audio_descriptor_format_code_should_not_be_reported"> 6873 Format with format code as %1$d(%2$s) should not be reported by AudioDescriptor. 6874 Instead, it should be reported by Android defined enums. 6875 </string> 6876 <string name="audio_descriptor_format_extended_code_should_not_be_reported"> 6877 Format with format extended code as %1$d(%2$s) should not be reported by AudioDescriptor. 6878 Instead, it should be reported by Android defined enums. 6879 </string> 6880 <string name="audio_descriptor_format_extended_code_is_not_used"> 6881 Format extended code as %1$d is not used. 6882 </string> 6883 <string name="audio_descriptor_hdmi_info_title">HDMI Support</string> 6884 <string name="audio_descriptor_hdmi_message"> 6885 Please connect an HDMI peripheral to validate AudioDescriptor. 6886 </string> 6887 <string name="uwb">Uwb</string> 6888 <string name="presence_test">Presence Test</string> 6889 <string name="presence_test_info"> 6890 The Presence tests check whether or not a device is properly calibrated for BLE, NAN and UWB based on Presence requirements. 6891 \nAll tests are required to pass on every device, if the radio technology is supported 6892 </string> 6893 <string name="presence_test_tv_info"> 6894 The Presence tests check whether or not a device is properly calibrated for BLE, NAN and UWB based on Presence requirements. 6895 \nAll tests are required to pass on all Android T+ launched TV devices, if the radio technology is supported. 6896 \nIf the TV device is launched on older Android letters, all tests will be disabled. Press Pass to pass this case. 6897 </string> 6898 <string name="is_reference_device_checkbox_text">Is Reference Device</string> 6899 <string name="is_manual_pass_text">Pass test manually after test completion</string> 6900 <string name="uwb_precision">Uwb Precision Test</string> 6901 <string name="uwb_short_range">Uwb Short Range Test</string> 6902 <string name="uwb_precision_instruction"> 6903 1. Take 1000 measurements with DUT at 1m distance from the reference device in a non-reflective chamber. 6904 \n2. Sort the 1000 measurements and compute the range as 975th measurement - 25th measurement 6905 \n3. Report the range below - Must be within 30cm (distance) for tests to pass. 6906 </string> 6907 <string name="report_distance_range_cm">Report Range (cm)</string> 6908 <string name="uwb_short_range_instruction"> 6909 1. Take 1000 measurements with DUT being 1m apart from the reference device, where ground truth distance is measured from the top edge of the DUT, held face up and tilted 45 degrees 6910 \n2. Sort the values. 6911 \n3. Report the median (500th value) (must be within 0.75m and 1.25m to pass). 6912 \n4. Report the reference device used. 6913 </string> 6914 <string name="report_distance_median_meters">Report Median (meters)</string> 6915 <string name="report_reference_device">Report Reference Device</string> 6916 <string name="uwb_not_supported">Uwb is not supported on device. Finishing activity. </string> 6917 <string name="ble">BLE</string> 6918 <string name="start_test_presence">Start Test</string> 6919 <string name="stop_test_presence">Stop Test</string> 6920 <string name="start_advertising_presence">Start Advertising</string> 6921 <string name="stop_advertising_presence">Stop Advertising</string> 6922 <string name="device_id_info_presence">You are advertising with deviceId: %1$d</string> 6923 <string name="device_found_presence">Reference device found. %1$d of %2$d samples collected</string> 6924 <string name="result_pending_presence">Awaiting Rx RSSI median from reference device... </string> 6925 <string name="dut_test_result_info_presence">Tx RSSI median: %1$d. Rx RSSI median received from reference device: %2$d</string> 6926 <string name="ref_test_result_info_presence">Rx RSSI median computed: %1$d.</string> 6927 <string name="reference_device_id_input_presence">Enter the device ID displayed on the advertising device</string> 6928 6929 <!-- Strings for BLE RSSI Precision Test --> 6930 <string name="ble_rssi_precision_name">BLE RSSI Precision Test</string> 6931 <string name="ble_rssi_precision_test_instructions"> 6932 Place the device under test (DUT) at 1m from the reference device (advertising device) in line of sight environment 6933 \nDUT instructions 6934 \n1. Ensure that the reference device is already advertising. 6935 \n2. Input the device ID of the reference device (displayed on the reference device) into the provided field and click "Start Test" 6936 \n3. The test is automatically stopped and passed (or failed )when all the required data is collected 6937 \nReference device instructions 6938 \n1. Ensure that the "Is reference device" checkbox is checked, then click, "Start Advertising" 6939 </string> 6940 6941 <!-- Strings for BLE Rx/Tx Offset Precision Test --> 6942 <string name="ble_rx_tx_offset_precision_name">BLE Rx/Tx Offset Precision Test</string> 6943 <string name="ble_rx_tx_offset_precision_test_instructions"> 6944 Place the device under test (DUT) at 1m from the reference device (advertising device) in line of sight environment 6945 \nDUT instructions 6946 \n1. Ensure that the test is already started on the reference device. 6947 \n2. Input the device ID of the reference device (displayed on the reference device) into the provided field and click "Start Test" 6948 \n3. The test is automatically stopped and passed (or failed) when all the required data is collected 6949 \n4. The test is passed if the median RSSI from both DUT and reference device is between -65dBm and -45dBm. 6950 \nReference device instructions 6951 \n1. Ensure that the "Is reference device" checkbox is checked, then click, "Start Advertising" 6952 </string> 6953 6954 <!-- Strings for NAN Accuracy Test --> 6955 <string name="nan_accuracy_test_instructions"> 6956 Place the device under test (DUT) at the test distance (either 10cm, 1m, 3m, or 5m) away from the reference device, in a line of sight environment. On the reference device, ensure that the "Is reference device" checkbox is checked, then click "Start Publishing" 6957 \n\nDUT instructions 6958 \n1. Ensure that the reference device is already publishing the NAN service. Enter the service ID displayed. 6959 \n2. Make sure that the toggle for the right test distance is checked. 6960 \n3. Click "Start Test". The display would be updated to show status "IN_PROGRESS" for the corresponding test distance. 6961 \n4. When all the required data is collected at the test distance, the display would be updated to show the status of the test, either PASSED or FAILED. 6962 \n5. The test is passed if more than 68% of the results are in the required range for the test distance (x). Where range is in [x-2,x+2]. E.g. for 5m, range is 3m to 7m. 6963 \n6. Repeat for the other distances by selecting the corresponding radio button. 6964 </string> 6965 <string name="nan_accuracy_test_name">Nan Accuracy Test</string> 6966 <string name="wifi_nan">WiFi NAN</string> 6967 <string name="start_publishing_presence">Start Publishing</string> 6968 <string name="stop_publishing_presence">Stop Publishing</string> 6969 <string name="select_test_distance_presence">Select Test Distance</string> 6970 <string name="distance_10cm_presence">10cm</string> 6971 <string name="distance_1m_presence">1m</string> 6972 <string name="distance_3m_presence">3m</string> 6973 <string name="distance_5m_presence">5m</string> 6974 <string name="service_id_info_presence">Your unique service ID is: %1$d</string> 6975 <string name="service_id_input_presence">Enter the service ID displayed on the publishing device</string> 6976 6977 <!-- Strings for AudioMicrophoneMuteToggleActivity --> 6978 <string name="audio_mic_toggle_test">Audio Microphone Hardware Toggle Mute Test</string> 6979 <string name="audio_mic_toggle_test_info"> 6980 This test verifies that devices which implement microphone hardware privacy toggles enforce sensor privacy when toggles are enabled. 6981 \nTo pass the test: 6982 \n - <a href="https://source.android.com/compatibility/android-cdd#9813_sensorprivacymanager">The audio stream should be muted</a>. 6983 \n - A dialog or notification should be shown that informs the user that the sensor privacy is enabled. 6984 </string> 6985 <string name="audio_mic_toggle_test_instruction1"> 6986 Mute the microphone using the hardware privacy toggle. 6987 \nPress the RECORD button. 6988 \nObserve a dialog with information regarding the microphone being blocked 6989 \nIgnore/cancel the dialog and wait for the recording to complete. 6990 \nThe pass button will be enabled if the test succeeded.</string> 6991 <string name="audio_mic_toggle_test_analyzing">Analyzing, please wait...\n</string> 6992 6993 <!-- Strings for CameraMuteToggleActivity --> 6994 <string name="camera_hw_toggle_test">Camera Hardware Toggle Mute Test</string> 6995 <string name="camera_hw_toggle_test_info"> 6996 This test verifies that devices which implement camera hardware privacy toggles enforce sensor privacy when toggles are enabled. 6997 \nTo pass the test: 6998 \n - <a href="https://source.android.com/compatibility/android-cdd#9813_sensorprivacymanager">The video stream should be muted</a>. 6999 \n - A dialog or notification should be shown that informs the user that the sensor privacy is enabled. 7000 </string> 7001 <string name="camera_hw_toggle_test_instruction"> 7002 Mute the camera using the hardware privacy toggle. 7003 \nObserve a dialog with information regarding the camera being blocked. 7004 \nCamera preview should show a blank feed. 7005 \nPress the Take Photo button. 7006 \nCaptured image should be black. 7007 \nMark the test as passing if the above conditions are met.</string> 7008 <string name="camera_hw_toggle_test_no_camera"> 7009 No available camera found. 7010 \nAdd or enable a camera and re-run this test. 7011 </string> 7012 7013 <!-- Strings for ControlsPanelVerifierActivity --> 7014 <string name="controls_panel_test">Controls Panel tests</string> 7015 <string name="controls_panel_not_supported">This feature is not supported in this device due to multi-window not being supported. Pass this test.</string> 7016 <string name="controls_panel_install_test">0. Install helper app</string> 7017 <string name="controls_panel_install_test_info">This test helps install the helper app that will be used for all subsequent tests in this group.</string> 7018 <string name="controls_panel_install_test_instructions">You should have received a helper app apk with this CTS 7019 Verifier package. Its name is \"CtsDeviceControlsApp\". Install the test app, by running\n 7020 \"adb install /path/to/CtsDeviceControlsApp.apk\".\n 7021 Pass the test if the install was successful, or if the app was already installed. Fail it otherwise.</string> 7022 <string name="controls_panel_basic_test">1. Controls Panel visible test</string> 7023 <string name="controls_panel_basic_test_info">This test verifies that an app that uses the 7024 correct metadata will be able to show a panel (custom activity) in the device controls space.</string> 7025 <string name="controls_panel_general_test_instructions">Open the Device controls space in this device. 7026 This is the space that allows you to control individual home automation devices for many apps.\n\n 7027 Once there, you should see a header with the name \"Cts controls\" and the icon [ICON]. If you don\'t see it, there may be a drop-down 7028 to select that app. Alternatively, there may be a menu that allows you to add this app before it\'s visible in the drop-down. 7029 Once the app is selected, you should see a container with the title \"Cts controls\" 7030 and content that starts with \"This is a panel belonging to Cts controls\".\n\n</string> 7031 <string name="controls_panel_basic_test_instructions"> 7032 If you can observe this panel, pass this test. Otherwise fail this test. 7033 </string> 7034 <string name="controls_panel_setting_test_false">2a. Controls Panel setting in extra test false value</string> 7035 <string name="controls_panel_setting_test_true">2b. Controls Panel setting in extra test true value</string> 7036 <string name="controls_panel_setting_test_info">This test verifies that an app that shows a 7037 panel in the device controls space will receive the correct value of the setting for controlling 7038 devices on the lock screen as part of their intent extras.\n\n 7039 For this test, you will need to have set up a screen lock.</string> 7040 <string name="controls_panel_settings_test_open_lockscreen_settings">Open Settings</string> 7041 <string name="controls_panel_setting_test_instructions">Using the button below, open Settings. 7042 Find the setting that allows you to control external devices from the lockscreen 7043 (you might need to enable other settings for it to be available). Set that setting to %1$s. 7044 \n Then, open the device controls space (instructions below the button) and verify that the 7045 text inside the panel indicates that the setting is %1$s 7046 </string> 7047 7048 <!-- Strings for Input tests --> 7049 <string name="test_category_input">Input</string> 7050 <string name="usi_version_test">USI Version Test</string> 7051 <string name="usi_version_test_info">This test verifies that a device that supports a 7052 <a href="https://universalstylus.org">Universal Stylus Initiative (USI)</a> stylus through 7053 its built-in touchscreen correctly reports its supported USI version. 7054 </string> 7055 <string name="usi_version_yes">Yes</string> 7056 <string name="usi_version_no">No</string> 7057 <string name="usi_test_start">This test will ask you to verify that the reported 7058 <a href="https://universalstylus.org">Universal Stylus Initiative (USI)</a> protocol 7059 version is correct for each built-in display.\n 7060 To begin the test, please disconnect all external peripheral devices, such as mice, 7061 keyboards, or styluses that are connected through USB or Bluetooth.\n\n 7062 Found %1$d built-in display(s). Are you ready to proceed? 7063 </string> 7064 <string name="usi_test_verify_display_usi_version">The display \"%1$s\" reports its USI version 7065 as %2$s.\n\n 7066 Is this correct? 7067 </string> 7068 <string name="usi_version_not_supported">not supported</string> 7069 <string name="usi_test_passed">Test Passed\n\n 7070 Press Pass. 7071 </string> 7072 <string name="usi_test_failed">Test Failed\n\n 7073 Reason: %1$s 7074 </string> 7075 <string name="usi_fail_reason_not_ready">Not ready to check for USI stylus versions.</string> 7076 <string name="usi_fail_reason_incorrect_version">The USI version was incorrectly reported. 7077 </string> 7078 7079 <!-- Strings for PreferredMixerAttributesTestActivity --> 7080 <string name="audio_preferred_mixer_attributes_test">Audio Preferred Mixer Attributes Test</string> 7081 <string name="audio_preferred_mixer_attributes_test_info"> 7082 This test verifies that apps can set preferred mixer attributes for USB devices. 7083 \nTo pass the test: 7084 \n - Connect a USB audio device to the Android device under test. 7085 \n - The test will automatically run by setting preferred mixer attributes. If the test passes, the pass button will be clickable. Otherwise, the failure message will show. 7086 </string> 7087 <string name="audio_preferred_mixer_attributes_test_connect_usb_device">Please connect USB audio device</string> 7088 <string name="audio_preferred_mixer_attributes_test_usb_device_connected">USB device connected</string> 7089 <string name="audio_preferred_mixer_attributes_test_running">Running test, please wait…</string> 7090 <string name="audio_can_not_set_preferred_mixer_attributes">Cannot set preferred mixer attributes for USB device.</string> 7091 <string name="audio_set_preferred_mixer_attributes_failed">Set preferred mixer attributes failed.</string> 7092 <string name="audio_get_preferred_mixer_attributes_not_equal">Preferred mixer attributes are different from ones set.</string> 7093 <string name="audio_clear_preferred_mixer_attributes_failed">Clearing preferred mixer attributes failed.</string> 7094 <string name="audio_get_preferred_mixer_attributes_should_be_null">Preferred mixer attributes is not null after calling AudioManager#clearPreferredMixerAttributes.</string> 7095 <string name="audio_no_callback_for_preferred_mixer_attributes_changed">Callback is not called when preferred mixer attributes changed.</string> 7096 7097 <!-- Strings for CaptureContentForNotes test --> 7098 <string name="ccfn_tests">Capture Content For Notes Tests</string> 7099 <string name="ccfn_tests_info"> 7100 This test verifies the support for Content Capture For Notes APIs on devices that have the 7101 ROLE_NOTES enabled. 7102 7103 \n\nIf the ROLE_NOTES is not enabled, no test should be shown in the list below, and you 7104 should mark the CTS test as passed. 7105 7106 \n\nFor this test you need to install CtsDefaultNotesApp.apk and set it as the Default notes 7107 app. 7108 7109 \n\nFor some tests you will need to set up device owner. 7110 7111 \n\nPlease clear the device owner after all the test cases are run, if it was set up. 7112 </string> 7113 <!-- Dialogs --> 7114 <string name="set_default_notes_button_label">Set default notes app</string> 7115 <string name="set_default_notes_button_info"> 7116 For these tests you need to install CtsDefaultNotesApp.apk. 7117 \nThen you need to set it as the Default notes app setting through device settings app. 7118 \nThe Default notes app settings is generally under Apps -> Default apps -> Notes app. 7119 </string> 7120 <string name="setup_device_owner_button_label">Set up device owner</string> 7121 <string name="setup_device_owner_button_info"> 7122 Some tests require to set up device owner in order to enforce device manager policies. 7123 Please run: 7124 \nadb shell dpm set-device-owner --user 0 com.android.cts.verifier/.capturecontentfornotes.DeviceAdminTestReceiver 7125 </string> 7126 <!-- Error messages --> 7127 <string name="admin_policy_setup_failed"> 7128 Failed to set up device admin policy, is the device owner set up? 7129 </string> 7130 <!-- Toasts --> 7131 <string name="disable_screenshot_toast">Screenshots disabled successfully</string> 7132 <string name="enable_screenshot_toast">Screenshots enabled successfully</string> 7133 <string name="clear_device_owner_toast">Successfully cleared device owner</string> 7134 <string name="no_command_run_toast">No command run</string> 7135 <!-- Other button labels --> 7136 <string name="disable_screenshot_button_label">Disable screenshots</string> 7137 <string name="enable_screenshot_button_label">Enable screenshots</string> 7138 <string name="clear_device_owner_button_label">Clear device owner</string> 7139 <!-- Test titles and instructions --> 7140 <string name="ccfn_launch_and_add_test">Fire intent action then add screenshot</string> 7141 <string name="ccfn_launch_and_add_test_info"> 7142 1. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7143 \n2. Then tap on the Fire Intent Action button shown in the CtsDefaultNotesApp. 7144 \n3. Android SystemUI should show a UI with a button that lets you add the screenshot to the 7145 notes app, tap on this button. 7146 \n4. The CtsDefaultNotesApp should be back in focus informing that screenshot was received. 7147 \n5. If so, pass this test else fail. 7148 </string> 7149 <string name="ccfn_launch_and_cancel_test">Fire intent action then cancel screenshot</string> 7150 <string name="ccfn_launch_and_cancel_test_info"> 7151 1. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7152 \n2. Then tap on the Fire Intent Action button shown in the CtsDefaultNotesApp. 7153 \n3. Android SystemUI should show a UI with a button that lets you cancel, tap on this 7154 button. 7155 \n4. The CtsDefaultNotesApp should be back in focus informing that screenshot was not 7156 received. 7157 \n5. If so, pass this test else fail. 7158 </string> 7159 <string name="ccfn_launch_window_unsupported"> 7160 Fire intent action but window mode not supported 7161 </string> 7162 <string name="ccfn_launch_window_unsupported_info"> 7163 1. Open the CtsDefaultNotesApp using the app icon, this should launch the app in regular 7164 mode. 7165 \n2. Then tap on the Fire Intent Action button shown in the CtsDefaultNotesApp. 7166 \n3. Android SystemUI should not be shown, instead the CtsDefaultNotesApp should inform that 7167 window mode is unsupported. 7168 \n4. If so, pass this test else fail. 7169 </string> 7170 <string name="ccfn_launch_blocked_by_admin">Fire intent action but blocked by admin</string> 7171 <string name="ccfn_launch_blocked_blocked_by_admin_info"> 7172 1. Ensure device owner is set up by running: 7173 \nadb shell dpm set-device-owner --user 0 com.android.cts.verifier/.capturecontentfornotes.DeviceAdminTestReceiver 7174 \n2. Tap on the disable screenshot button shown below. 7175 \n3. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7176 \n4. Then tap on the Fire Intent Action button shown in the CtsDefaultNotesApp. 7177 \n5. Android SystemUI should not be shown, instead the CtsDefaultNotesApp should inform that 7178 screenshot blocked by admin. 7179 \n6. If so, pass this test else fail. 7180 \n7. Ensure to tap on enable screenshot button otherwise future tests would be impacted. 7181 </string> 7182 <string name="ccfn_call_can_use_api_true">Trigger can all API which returns true</string> 7183 <string name="ccfn_call_can_use_api_true_info"> 7184 1. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7185 \n2. Then tap on the Call Can Use API button. 7186 \n3. Verify the CtsDefaultNotesApp informs can use API returned true. 7187 \n4. If so, pass this test else fail. 7188 </string> 7189 <string name="ccfn_call_can_use_api_blocked_by_admin"> 7190 Trigger can call API but blocked by admin 7191 </string> 7192 <string name="ccfn_call_can_use_api_blocked_by_admin_info"> 7193 1. Ensure device owner is set up by running: 7194 \nadb shell dpm set-device-owner --user 0 com.android.cts.verifier/.capturecontentfornotes.DeviceAdminTestReceiver 7195 \n2. Tap on the disable screenshot button shown below. 7196 \n3. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7197 \n4. Tap on the Call Can Use API button. 7198 \n5. Verify the CtsDefaultNotesApp informs can use API returned false. 7199 \n6. If so, pass this test else fail. 7200 \n7. Ensure to tap on enable screenshot button otherwise future tests would be impacted. 7201 </string> 7202 <string name="ccfn_call_can_use_api_window_unsupported"> 7203 Trigger can call API but window mode unsupported 7204 </string> 7205 <string name="ccfn_call_can_use_api_window_unsupported_info"> 7206 1. Open the CtsDefaultNotesApp using the app icon, this should launch the app in regular 7207 mode. 7208 \n2. Tap on the Call Can Use API button. 7209 \n3. Verify the CtsDefaultNotesApp informs can use API returned false. 7210 \n4. If so, pass this test else fail. 7211 </string> 7212</resources> 7213