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">Verifier %1$s</string> 21 <string name="version_number_format">Version #: %d</string> 22 23 <string name="pass_button_text">Pass</string> 24 <string name="info_button_text">Info</string> 25 <string name="fail_button_text">Fail</string> 26 <string name="next_button_text">Next</string> 27 <string name="go_button_text">Go</string> 28 <string name="present_button_text">Device Present</string> 29 <string name="gone_button_text">Device Gone</string> 30 <string name="tests_completed_successfully">All tests completed successfully.</string> 31 32 <string name="retry_button_text">Retry</string> 33 <string name="finish_button_text">Finish</string> 34 <string name="fail_and_next_button_text">Fail and Next</string> 35 <string name="yes_string">Yes</string> 36 <string name="no_string">No</string> 37 <string name="search_label">TestListActivity</string> 38 <string name="search_hint">Search Tests</string> 39 <string name="search_title">Search</string> 40 <string name="system">System</string> 41 <string name="system_on">ON</string> 42 <string name="system_off">OFF</string> 43 44 <!-- Strings for CtsReportLog warning --> 45 <string name="reportlog_warning_title">CTS-Verifier Report Log</string> 46 <string name="reportlog_warning_body">Can\'t create folder for CTS-Verifier Report Logs. 47 \n\nPlease enable Report Log creation by exiting CTS Verifier and running the following commands: 48 \n\n<code>adb shell appops set com.android.cts.verifier android:read_device_identifiers allow</code> 49 \n\n<code>adb shell appops set com.android.cts.verifier MANAGE_EXTERNAL_STORAGE 0</code> 50 \n\nTest instructions are found in the \"Using CTS Verifier\" document found at 51 <a href="https://source.android.com/compatibility/cts/verifier">https://source.android.com/compatibility/cts/verifier</a> 52 </string> 53 54 <!-- Strings for non-SDK interfaces accessibility warning --> 55 <string name="nonsdk_interfaces_warning_title">CTS-Verifier non-SDK interfaces accessibility</string> 56 <string name="nonsdk_interfaces_warning_body">Can\'t access non-SDK interfaces. 57 \n\nPlease allow CTS Verifier to access non-SDK interfaces by running the following commands: 58 \n\n<code>adb shell settings put global hidden_api_policy 1</code> 59 \n\nTest instructions are found in the \"Using CTS Verifier\" document found at 60 <a href="https://source.android.com/compatibility/cts/verifier">https://source.android.com/compatibility/cts/verifier</a> 61 \n\nAfter setting up the CTS test environment, please relaunch the CTS Verifier app to rerun the test. 62 </string> 63 64 <!-- Strings for TestListActivity --> 65 <string name="test_category_audio">Audio</string> 66 <string name="test_category_camera">Camera</string> 67 <string name="test_category_car">Car</string> 68 <string name="test_category_device_admin">Device Administration</string> 69 <string name="test_category_hardware">Hardware</string> 70 <string name="test_category_networking">Networking</string> 71 <string name="test_category_sensors">Sensors</string> 72 <string name="test_category_location">Location</string> 73 <string name="test_category_security">Security</string> 74 <string name="test_category_streaming">Streaming</string> 75 <string name="test_category_features">Features</string> 76 <string name="test_category_deskclock">Clock</string> 77 <string name="test_category_jobscheduler">Job Scheduler</string> 78 <string name="test_category_telecom">Telecom</string> 79 <string name="test_category_telephony">Telephony</string> 80 <string name="test_category_tunnel">Tunnel Mode</string> 81 <string name="test_category_tv">TV</string> 82 <string name="test_category_instant_apps">Instant Apps</string> 83 <string name="test_category_logcat">Read Logs</string> 84 <string name="test_category_display_cutout">DisplayCutout</string> 85 <string name="test_category_other">Other</string> 86 <string name="test_category_device_controls">Device controls</string> 87 <string name="test_category_multidevice">Multi Device</string> 88 <string name="clear">Clear</string> 89 <string name="test_results_clear_title">Remove all test results?</string> 90 <string name="test_results_clear_yes">Yes</string> 91 <string name="test_results_clear_cancel">Cancel</string> 92 <string name="test_results_cleared">Test results cleared.</string> 93 <string name="view">View</string> 94 <string name="test_results_error">Couldn\'t create test results report. Try running the 95 following command if you haven\'t yet.\n\"adb shell appops set com.android.cts.verifier 96 android:read_device_identifiers allow\" </string> 97 <string name="runtime_permissions_error">Please grant runtime permissions, otherwise, tests might fail.</string> 98 <string name="export">Export</string> 99 <string name="report_log_folder_name">ctsv-report-logs</string> 100 <string name="no_storage">Cannot save report to external storage, see log for details.</string> 101 <string name="no_storage_io_parser_exception">Cannot save report to external 102 storage, see log for details. Or try running the following command if 103 you haven\'t yet.\n\"adb shell appops set com.android.cts.verifier 104 MANAGE_EXTERNAL_STORAGE 0\"</string> 105 <string name="report_saved">Report saved to: %s</string> 106 107 <!-- Strings for IntentDrivenTestActivity --> 108 <string name="intent_not_resolved">Intent Not Resolved</string> 109 <string name="intent_not_resolved_info">The following intent could not be resolved: %1$s</string> 110 111 <!-- Strings for ReportViewerActivity --> 112 <string name="report_viewer">Report Viewer</string> 113 114 <string name="result_success">Test passed!</string> 115 <string name="result_failure">Test failed!</string> 116 117 <!-- String shared between BackupTestActivity and BackupAccessibilityTestActivity --> 118 <string name="bu_loading">Loading...</string> 119 <string name="bu_generate_error">Error occurred while generating test data...</string> 120 <string name="bu_settings">Settings</string> 121 122 <!-- Strings for BatterySaverTestActivity --> 123 <string name="battery_saver_test">Battery Saver Test</string> 124 <string name="battery_saver_test_info"> 125 This test verifies that the device provides a user affordance to enable and disable 126 Battery Saver feature. 127 </string> 128 <string name="battery_saver_test_no_battery_detected"> 129 No battery detected. This test will only work on devices that contain a battery. 130 </string> 131 <string name="battery_saver_test_unplug"> 132 Unplug the device or run \"adb shell dumpsys battery unplug\". 133 </string> 134 <string name="battery_saver_test_device_plugged_in"> 135 The device is still plugged in. 136 </string> 137 <string name="battery_saver_test_enable_bs"> 138 Look for a button that allows you to turn Battery Saver on and off. The button may be in the 139 Quick Settings section or on the Battery page of device settings. Use the button to turn 140 Battery Saver on. 141 </string> 142 <string name="battery_saver_test_disable_bs"> 143 Now use the button to turn Battery Saver off. 144 </string> 145 <string name="battery_saver_test_start_turn_bs_off"> 146 Turn Battery Saver off to begin the test. 147 </string> 148 <string name="battery_saver_test_bs_on">Battery Saver is on.</string> 149 <string name="battery_saver_test_bs_off">Battery Saver is off.</string> 150 151 <!-- Strings for Device Administration tests --> 152 <string name="da_policy_serialization_test">Policy Serialization Test</string> 153 <string name="da_policy_serialization_info">This test checks that a device policy is properly 154 saved and loaded across reboots.\n\nPress the \"Generate Policy\" button to create 155 a random policy. Then press the \"Apply Policy\" button to apply the policy. Reboot the 156 device and verify that all rows in the policy list are green. Red items indicate policy 157 settings that were not loaded properly. 158 </string> 159 <string name="da_uninstall_test">Device Admin Uninstall Test</string> 160 <string name="da_uninstall_test_info">This test checks that an active device administrator 161 can be easily uninstalled from the application details screen in a way similar to other 162 apps. This test requires CtsEmptyDeviceAdmin.apk to be installed on the device. 163 </string> 164 <string name="da_tapjacking_test">Device Admin Tapjacking Test</string> 165 <string name="da_tapjacking_test_info">This test checks that an activity cannot tapjack the 166 user by obscuring the device admin details while prompting the user to activate the admin. 167 </string> 168 <string name="car_enable_garage_monitor">Enable Garage Mode Monitor</string> 169 <string name="car_garage_mode_test">Garage Mode Test</string> 170 <string name="car_garage_mode_test_desc"> 171 This test verifies that Garage Mode runs at the end of a drive.\n\n 172 <b>Important: Please enable Wi-Fi or other connectivity for test to pass.\n\n </b> 173 Touch "Enable Garage Mode Monitor" to launch the Garage Mode verifier.\n\n 174 Turn the vehicle off and exit the vehicle (or take the proprietary action that 175 initiates shut-down of the system).\n\n 176 Do not enter or disturb the vehicle for at least 15 minutes.\n\n 177 Enter the vehicle. Re-launch the CTS-Verifier app if it is not running.\n\n 178 If Garage Mode ran as required, the pass button will be enabled.</string> 179 <string name="car_component_power_on_policy_check">Verify Component Power On Policy</string> 180 <string name="car_component_power_off_policy_check">Verify Component Power Off Policy</string> 181 <string name="car_power_policy_test">Car Power Policy Test</string> 182 <string name="car_power_policy_test_desc"> 183 This test verifies that Wi-Fi, Bluetooth and Location settings UI behaviors with respect 184 to their power policy. If the policy sets components power off, the component settings UI 185 shall be disabled. Otherwise, the settings UI shall be enabled as default.\n\n 186 First execute the\n 187 " adb shell cmd car_service apply-cts-verifier-power-off-policy"\n 188 adb shell command first and then sequentialy click first 4 buttons to check each component 189 settings UI are disabled.\n\n 190 Then, execute the\n 191 " adb shell cmd car_service apply-cts-verifier-power-on-policy"\n 192 shell command and sequential click the remaining 4 buttons to check if each component 193 settings UI is enabled.\n\n 194 For the detailed instructions, please refer to\n 195 " https://source.android.com/compatibility/cts/power-policy". 196 </string> 197 <string name="car_wifi_settings">Go to Wi-Fi settings</string> 198 <string name="car_wifi_settings_disable">Check Wi-Fi Settings Disabled</string> 199 <string name="car_bluetooth_settings_disable">Check Bluetooth Settings Disabled</string> 200 <string name="car_location_settings_disable">Check Location Settings Disabled</string> 201 <string name="car_wifi_settings_enable">Check Wi-Fi Settings Enabled</string> 202 <string name="car_bluetooth_settings_enable">Check Bluetooth Settings Enabled</string> 203 <string name="car_location_settings_enable">Check Location Settings Enabled</string> 204 <string name="car_dock_test">Car Dock Test</string> 205 <string name="car_dock_test_desc">This test ensures that car mode opens the app associated with 206 car dock when going into car mode.\n\n 207 Click on "Enable Car Mode" to start the test. Clicking on the button will either bring up a 208 disambiguation dialog asking which app to open or immediately open the CAR_DOCK application. 209 Select the "CTS Verifier" app and then "Always" if the dialog pops up. 210 This will open the CAR_DOCK application.\n\n 211 In the CAR_DOCK application, press the home button, which will enable the pass button if the 212 framework correctly tries to open the CAR_DOCK app again.</string> 213 <string name="car_mode_enable">Enable Car Mode</string> 214 <string name="car_dock_activity_text">Press the Home button</string> 215 <string name="car_launcher_test">Car Launcher Test</string> 216 <string name="car_launcher_test_desc">This test ensures that the car launcher lists apps 217 disabled by car service due to system resource overuse.\n\n 218 <b> 219 Before proceeding, check if \'com.android.cts.car.watchdog_companionapp\' 220 (aka CtsCarWatchdogCompanionApp) is installed by going to Settings > Apps. If not, 221 please install the app before proceeding.\n\n 222 </b> 223 1. Check if the CtsCarWatchdogCompanionApp is visible in car launcher\'s app grid view. If 224 it is not listed, pass the test.\n 225 2. Run the 226 \'adb shell cmd car_service watchdog-resource-overuse-kill com.android.cts.car.watchdog_companionapp\' 227 shell command to disable the app because of system resource overuse.\n 228 3. Click on \"Open Launcher\". Make sure the CtsCarWatchdogCompanionApp is displayed. If it 229 is not listed, fail the test.\n 230 4. Open CtsCarWatchdogCompanionApp from the launcher.\n\n 231 Pass the test only if the companion app opened successfully.</string> 232 <string name="car_launcher_test_button_label">Open Launcher</string> 233 <string name="gear_selection_test">Gear Selection Test</string> 234 <string name="gear_selection_test_desc">This test ensures that the 235 GEAR_SELECTION property is implemented correctly.\n\nShift the car\'s 236 gear to the expected gear value. If it is able to shift to all the 237 implemented gears then the pass button will be enabled.</string> 238 <string name="expected_gear_selection_title">Expected Gear Selection</string> 239 <string name="current_gear_selection_title">Current Gear Selection</string> 240 <string name="parking_brake_on_test">PARKING_BRAKE_ON Test</string> 241 <string name="parking_brake_on_test_desc">This test ensures that the 242 PARKING_BRAKE_ON property is implemented correctly.\n\nFollow the 243 instructions on the screen to engage and disengage the parking brake. When 244 the instructions are completed, the pass button will be enabled.</string> 245 <string name="current_parking_brake_on_value_title">Current PARKING_BRAKE_ON Value:</string> 246 <string name="da_no_policy">1. Press the \"Generate Policy\" to create a random device 247 policy\n\n2. Press \"Apply Policy\" to put the policy into effect.\n\n3. Reboot your 248 device and return to this test in the CTS Verifier. 249 </string> 250 <string name="da_generate_policy">Generate Policy</string> 251 <string name="da_apply_policy">Apply Policy</string> 252 <string name="da_random_policy">Random policy generated.</string> 253 <string name="da_policy_reboot">Reboot your device and return to this CTS Verifier test.</string> 254 <string name="da_password_quality">Password Quality</string> 255 <string name="da_password_quality_alphabetic">Alphabetic</string> 256 <string name="da_password_quality_alphanumeric">Alphanumeric</string> 257 <string name="da_password_quality_numeric">Numeric</string> 258 <string name="da_password_quality_something">Something</string> 259 <string name="da_password_minimum_length">Minimum Password Length</string> 260 <string name="da_maximum_failed_passwords_for_wipe">Maximum Failed Passwords for Wipe</string> 261 <string name="da_maximum_time_to_lock">Maximum Time to Lock</string> 262 <string name="da_policy_info">Expected value: %1$s\nActual value: %2$s</string> 263 264 <string name="da_screen_lock_test">Screen Lock Test</string> 265 <string name="da_screen_lock_info">This test checks that the DevicePolicyManager\'s lockNow 266 method immediately locks the screen. It should lock the screen immediately despite any 267 settings that may specify a timeout.\n\nClick the \"Force Lock\" button to lock the screen. 268 Your screen should be locked and require the password to be entered. 269 </string> 270 <string name="da_force_lock">Force Lock</string> 271 <string name="da_lock_success">It appears the screen was locked successfully!</string> 272 <string name="da_lock_error">It does not look like the screen was locked...</string> 273 274 <string name="da_install_admin_instructions"> 275 Please install the \'Test Device Admin\' app (packaged as CtsEmptyDeviceAdmin.apk) on the device. 276 </string> 277 <string name="da_admin_installed_status_text">\'Test Device Admin\' installed on the device.</string> 278 <string name="da_enable_admin_instructions">Add \'Test Device Admin\' as an active administrator on the device. 279 Tap the button below to review the device admin details and activate the administrator. 280 </string> 281 <string name="da_enable_admin_button_text">Enable admin</string> 282 <string name="da_uninstall_admin_instructions">Attempt to uninstall the app from the application details page of the \'Test Device Admin\' app. 283 You should see another screen showing the device admin details before you can uninstall the app from the device. 284 Wait till the app is uninstalled before returning to this page. 285 </string> 286 <string name="da_uninstall_admin_button_text">Launch settings</string> 287 288 <string name="da_tapjacking_overlay_app_description">This activity attempts to tapjack the activity below.\n 289 Any security sensitive controls below should not respond to taps as long as this activity is visible.</string> 290 <string name="da_tapjacking_instructions"> 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. Press \'back\' to exit the overlaying transparent activity.\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_instructions" product="automotive"> 300 1. Launch the device admin add screen by pressing the button below.\n 301 2. Wait for an overlaying transparent activity to show up obscuring the device admin details window.\n 302 3. The button to activate the admin should be disabled and should not register any taps.\n 303 4. Wait for the overlaying activity to finish.\n 304 5. Press \'back\' to exit the device admin details and return to this screen.\n 305 Pass the test if the device admin could not be activated while the details 306 window was being obscured. 307 </string> 308 <string name="da_tapjacking_instructions" product="tv"> 309 1. Launch the device admin add screen by pressing the button below.\n 310 2. Wait for an overlaying transparent activity to show up obscuring the device admin details window.\n 311 3. The button to activate the admin should be disabled and should not register any taps.\n 312 4. Wait for the overlaying activity to finish.\n 313 5. Press \'back\' to exit the device admin details and return to this screen.\n 314 Pass the test if the device admin could not be activated while the details 315 window was being obscured. 316 </string> 317 <string name="da_tapjacking_button_text">Enable device admin</string> 318 319 <!-- Strings for RecentTaskRemovalTestActivity --> 320 <string name="remove_from_recents_test">Recent Task Removal Test</string> 321 <string name="remove_from_recents_test_info"> 322 This test verifies that an app whose task is removed from recents is not also force-stopped 323 without explicit user consent. This test requires CtsForceStopHelper.apk to be installed. 324 </string> 325 <string name="fs_test_app_install_instructions">Please install the \'Force stop helper app\' on the device.</string> 326 <string name="fs_test_app_installed_text">\'Force stop helper app\' installed on device. Proceed to the following steps.</string> 327 <string name="fs_test_app_launch_instructions"> 328 Tap the button to launch the helper activity. Then return to this screen. 329 </string> 330 <string name="fs_launch_test_app_button_text">Launch test activity</string> 331 <string name="fs_test_app_recents_instructions"> 332 Open recents and remove the task of the activity started in the previous step and return to this screen. 333 Deny any dialog that is shown asking for permission to force-stop or kill the app. 334 </string> 335 <string name="fs_force_stop_verification_pending">Verifying... Please wait.</string> 336 337 <!-- Strings for ClipboardPreviewTest --> 338 <string name="clipboard_preview_test">Clipboard Preview Test</string> 339 <string name="clipboard_preview_test_info"> 340 This test verifies that clipboard contents are visible to the user when copied. 341 </string> 342 <string name="clipboard_preview_test_instructions"> 343 Press the \'Copy\' button to copy the secret code to the clipboard. 344 \n\nDo not press any other buttons or tap the clipboard UI after you press the \'Copy\' button. 345 \n\n If you see the word "FAIL" appear on screen, press Fail. 346 \n\n If you see a confirmation that content has been copied to the clipboard, press Pass. 347 \n\n If nothing happens, press Fail if this is a handheld device, otherwise press Pass. 348 </string> 349 <string name="clipboard_preview_test_secret">FAIL</string> 350 <string name="clipboard_preview_test_copy_button">Copy</string> 351 352 <!-- Strings for BiometricTest --> 353 <string name="biometric_test">Biometric Tests</string> 354 355 <string name="biometric_test_category_credential">1) Credential Tests</string> 356 <string name="biometric_test_category_strong">2) Strong Biometric Tests</string> 357 <string name="biometric_test_category_weak">3) Weak Biometric Tests</string> 358 <string name="biometric_test_category_combination">4) setUserAuthParams Tests</string> 359 360 <string name="biometric_test_credential_crypto_label">1a: Credential Crypto</string> 361 <string name="biometric_test_credential_crypto_instructions">This test checks that PIN/Pattern/Password successfully unlocks the relevant KeyStore operations. Please 362 ensure that you have a PIN/Pattern/Password set up.</string> 363 <string name="biometric_test_credential_crypto_timed_key_strongbox">Create and unlock timed key (StrongBox)</string> 364 <string name="biometric_test_credential_crypto_timed_key_no_strongbox">Create and unlock timed key</string> 365 366 <string name="biometric_test_ui_instruction_dialog_title">Instructions</string> 367 <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> 368 <string name="biometric_test_ui_instruction_dialog_continue">Continue</string> 369 <string name="biometric_test_ui_verification_dialog_title">Please enter your recorded contents</string> 370 <string name="biometric_test_ui_verification_dialog_check">Check</string> 371 372 <string name="biometric_test_reject_continues_instruction_title">Instructions</string> 373 <string name="biometric_test_reject_continues_instruction_contents">Please authenticate with a non-enrolled biometric before authenticating with the actual enrolled biometric.</string> 374 <string name="biometric_test_reject_continues_instruction_continue">Continue</string> 375 376 <string name="biometric_test_strong_label">2a: Strong Biometrics + Crypto</string> 377 <string name="biometric_test_strong_instructions">This test checks that the Settings.ACTION_BIOMETRIC_ENROLL and its corresponding 378 EXTRA_BIOMETRIC_AUTHENTICATOR_REQUIREMENTS APIs enroll only a STRONG biometric. Please ensure that the device 379 does NOT have ANY biometrics enrolled before starting this test. After passing the first part of the test, it will check various use cases 380 when authentication is invoked with the STRONG biometric.</string> 381 <string name="biometric_test_strong_check_and_enroll_button">Start enrollment</string> 382 <string name="biometric_test_strong_authenticate_no_strongbox_button">Authenticate Crypto (without StrongBox)</string> 383 <string name="biometric_test_strong_authenticate_strongbox_button">Authenticate Crypto (with StrongBox)</string> 384 <string name="biometric_test_strong_authenticate_invalidated_button">Authenticate Key Invalidated</string> 385 <string name="biometric_test_strong_authenticate_invalidated_instruction_title">Instructions</string> 386 <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> 387 <string name="biometric_test_strong_authenticate_invalidated_instruction_continue">Continue</string> 388 389 <string name="biometric_test_weak_label">3a: Weak Biometrics</string> 390 <string name="biometric_test_weak_instructions">This test checks that the Settings.ACTION_BIOMETRIC_ENROLL and its corresponding 391 EXTRA_BIOMETRIC_AUTHENTICATOR_REQUIREMENTS APIs enroll a biometric that meets or exceeds WEAK. Please ensure that the device 392 does NOT have ANY biometrics enrolled before starting this test. After passing the first part of the test, it will check various use cases 393 when authentication is invoked.</string> 394 <string name="biometric_test_weak_enroll">Start enrollment</string> 395 396 <string name="biometric_test_set_user_authentication_credential_cipher_label">4a: Cipher, Credential</string> 397 <string name="biometric_test_set_user_authentication_biometric_cipher_label">4b: Cipher, Biometric</string> 398 <string name="biometric_test_set_user_authentication_biometric_credential_cipher_label">4c: Cipher, Biometric|Credential</string> 399 <string name="biometric_test_set_user_authentication_credential_signature_label">4d: Signature, Credential</string> 400 <string name="biometric_test_set_user_authentication_biometric_signature_label">4e: Signature, Biometric</string> 401 <string name="biometric_test_set_user_authentication_biometric_or_credential_signature_label">4f: Signature, Biometric|Credential</string> 402 <string name="biometric_test_set_user_authentication_credential_mac_label">4g: MAC, Credential</string> 403 <string name="biometric_test_set_user_authentication_biometric_mac_label">4h: MAC, Biometric</string> 404 <string name="biometric_test_set_user_authentication_biometric_or_credential_mac_label">4i: MAC, Biometric|Credential</string> 405 <string name="biometric_test_set_user_authentication_credential_aead_cipher_label">4j: Aead Cipher, Credential</string> 406 <string name="biometric_test_set_user_authentication_biometric_aead_cipher_label">4k: Aead Cipher, Biometric</string> 407 <string name="biometric_test_set_user_authentication_biometric_credential_aead_cipher_label">4l: Aead Cipher, Biometric or Credential</string> 408 <string name="biometric_test_set_user_authentication_credential_key_agreement_label">4m: Key Agreement, Credential</string> 409 <string name="biometric_test_set_user_authentication_biometric_key_agreement_label">4n: Key Agreement, Biometric</string> 410 <string name="biometric_test_set_user_authentication_biometric_or_credential_key_agreement_label">4o: Key Agreement, Biometric or Credential</string> 411 <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. 412 Buttons for completed tasks will become invisible. It\'s normal for buttons to be disabled for a few seconds during this test.</string> 413 <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. 414 Buttons for completed tasks will become invisible. It\'s normal for buttons to be disabled for a few seconds during this test.</string> 415 <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. 416 Buttons for completed tasks will become invisible. It\'s normal for buttons to be disabled for a few seconds during this test.</string> 417 <!-- no strongbox--> 418 <string name="biometric_test_set_user_authentication_credential_per_use_auth_with_credential">auth-per-use key with credential</string> 419 <string name="biometric_test_set_user_authentication_credential_duration_auth_with_credential">time-based key with credential</string> 420 <string name="biometric_test_set_user_authentication_credential_per_use_auth_with_biometric">auth-per-use key with biometric</string> 421 <string name="biometric_test_set_user_authentication_credential_duration_auth_with_biometric">time-based key with biometric</string> 422 <!-- strongbox --> 423 <string name="biometric_test_set_user_authentication_credential_per_use_auth_with_credential_strongbox">auth-per-use key with credential (strongbox)</string> 424 <string name="biometric_test_set_user_authentication_credential_duration_auth_with_credential_strongbox">time-based key with credential (strongbox)</string> 425 <string name="biometric_test_set_user_authentication_credential_per_use_auth_with_biometric_strongbox">auth-per-use key with biometric (strongbox)</string> 426 <string name="biometric_test_set_user_authentication_credential_duration_auth_with_biometric_strongbox">time-based key with biometric (strongbox)</string> 427 428 <!-- Strings for user consent for logs test --> 429 <string name="read_logs_text">User Consent for Device Logs Test</string> 430 <string name="read_logs_fg_allow_text">User Consent for Device Logs Allow in Foreground Test</string> 431 <string name="read_logs_fg_deny_text">User Consent for Device Logs Deny in Foreground Test</string> 432 <string name="read_logs_bg_text">User Consent for Device Logs in Instrumentation Test</string> 433 <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> 434 435 <!-- Strings for lskf bound keys test --> 436 <string name="sec_lskf_bound_key_test">LSKF Bound Keys Test</string> 437 <string name="sec_lskf_bound_key_test_info"> 438 This test ensures that Keystore cryptographic keys that are bound to LSKF authentication 439 are unusable without a recent enough authentication. You need to set up a screen lock in order to 440 complete this test. If available, this test should be run by using fingerprint authentication 441 as well as PIN/pattern/password authentication. 442 </string> 443 444 <string name="sec_fingerprint_bound_key_test">Fingerprint Bound Keys Test</string> 445 <string name="sec_fingerprint_bound_key_test_info"> 446 This test ensures that Keystore cryptographic keys that are bound to fingerprint authentication 447 are unusable without an authentication. You need to set up a fingerprint order to 448 complete this test. 449 </string> 450 <string name="sec_fp_dialog_message">Authenticate now with fingerprint</string> 451 <string name="sec_fp_auth_failed">Authentication failed</string> 452 <string name="sec_start_test">Start Test</string> 453 454 <!-- Strings for protected confirmation test --> 455 <string name="sec_protected_confirmation_test">Android Protected Confirmation Test</string> 456 <string name="sec_protected_confirmation_test_info"> 457 This test ensures that - if Android Protected Confirmation is supported by the device under 458 test - the user is able to see the confirmation message and confirm it. It also assures that 459 Keymaster signs a message with a confirmation key only if the message was previously 460 confirmed by the user. 461 </string> 462 <string name="sec_protected_confirmation_not_supported_title">Not Supported</string> 463 <string name="sec_protected_confirmation_not_supported_info"> 464 Android Protected Confirmation is not implemented by this device. This is okay because this 465 is an optional feature. Set this test to passed and continue. 466 </string> 467 <string name="sec_protected_confirmation_message">This is a CtsVerifier test message!</string> 468 <string name="sec_protected_confirmation_tee_test">Start Tee Test</string> 469 <string name="sec_protected_confirmation_strongbox_test">Start Strongbox Test</string> 470 <string name="sec_protected_confirmation_tee_negative_test">Start Tee Negative Test</string> 471 <string name="sec_protected_confirmation_strongbox_negative_test">Start Strongbox Negative Test</string> 472 473 <!-- Strings for IdentityAuthPerPresenation --> 474 <string name="sec_identity_credential_authentication_test">Identity Credential Authentication</string> 475 <string name="sec_identity_credential_authentication_test_info"> 476 This test ensures that data elements in Identity Credential documents protected by user 477 authentication with timeout 0 can only be accessed once per reader session. 478 </string> 479 480 <!-- Strings for IdentityAuthPerPresenationMultiDocument --> 481 <string name="sec_identity_credential_authentication_multi_document_test">Identity Credential Authentication Multi-Document</string> 482 <string name="sec_identity_credential_authentication_multi_document_test_info"> 483 This test is for Identity Credential presentations with multiple documents. 484 </string> 485 486 <string name="sec_unlocked_device_required_keys_test">Unlocked Device Required Keys Test</string> 487 <string name="sec_unlocked_device_required_keys_test_info"> 488 This test ensures that keys created with setUnlockedDeviceRequired are usable when the 489 screen is unlocked but not when it is locked. 490 </string> 491 492 <!-- Strings for HasVibratorVerifierActivity --> 493 <string name="has_vibrator_test_description">This test validates the Vibrator#HasVibrator API response.</string> 494 <string name="has_vibrator_response_label">Does this device say it has a vibrator?</string> 495 <string name="has_vibrator_start_test_label">To start the test, hold the device in your hand and click the vibrate button.</string> 496 <string name="has_vibrator_did_device_vibrate_label">Did the device vibrate?</string> 497 <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> 498 <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> 499 <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> 500 <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> 501 <string name="has_vibrator_test_running_text">Test will end in %d</string> 502 <string name="has_vibrator_test_vibrate_button_text">Vibrate</string> 503 504 <!-- Strings for BluetoothActivity --> 505 <string name="bluetooth_test">Bluetooth Test</string> 506 <string name="bluetooth_test_info"> 507 The Bluetooth Control tests check whether or not the device 508 can disable and enable Bluetooth properly. 509 \n\nThe Bluetooth tests require two devices, and Bluetooth data is exchanged between them. 510 \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. 511 \nThis is a list of the tests: 512 \nThis Device x Other Device 513 \n\n\"Bluetooth LE Insecure Client Test\" x \"Bluetooth LE Insecure Server Test\" 514 \n\n\"Bluetooth LE Insecure Server Test\" x \"Bluetooth LE Insecure Client Test\" 515 \n\n\"Bluetooth LE Secure Client Test\" x \"Bluetooth LE Secure Server Test\" 516 \n\n\"Bluetooth LE Secure Server Test\" x \"Bluetooth LE Secure Client Test\" 517 \n\n\"Bluetooth LE CoC Insecure Server Test\" x \"Bluetooth LE CoC Insecure Client Test\" 518 \n\n\"Bluetooth LE CoC Insecure Client Test\" x \"Bluetooth LE CoC Insecure Server Test\" 519 \n\n\"Bluetooth LE CoC Secure Server Test\" x \"Bluetooth LE CoC Secure Client Test\" 520 \n\n\"Bluetooth LE CoC Secure Client Test\" x \"Bluetooth LE CoC Secure Server Test\" 521 \n\nThe Device Communication tests require two 522 devices to pair and exchange messages. The two devices must be: 523 \n\n1. a candidate device implementation running the software build to be tested 524 \n\n2. a separate device implementation already known to be compatible 525 </string> 526 527 <string name="bt_control">Bluetooth Control</string> 528 <string name="bt_device_communication">Device Communication</string> 529 <string name="bt_le">Bluetooth LE</string> 530 <string name="bt_hid">Bluetooth HID</string> 531 <string name="bt_le_coc">Bluetooth LE CoC</string> 532 533 <string name="bt_toggle_bluetooth">Toggle Bluetooth</string> 534 <string name="bt_toggle_instructions">Disable and enable Bluetooth to successfully complete this test.</string> 535 <string name="bt_enable_bluetooth">Enable Bluetooth</string> 536 <string name="bt_disable_bluetooth">Disable Bluetooth</string> 537 <string name="bt_disabling">Disabling Bluetooth...</string> 538 <string name="bt_disabling_error">Could not disable Bluetooth...</string> 539 540 <string name="ble_coc_insecure_client_test_list_name">Bluetooth LE CoC Insecure Client Test</string> 541 <string name="ble_coc_insecure_client_test_list_info"> 542 The Bluetooth LE CoC test must be done simultaneously on two devices. This device is the client. 543 All tests listed here must be done without pairing. Tap \"Bluetooth LE CoC Insecure Server Test\" on the other device. 544 \n\nTap \"01 Bluetooth LE CoC Client Test\" on this device, then tap \"01 Bluetooth LE CoC Server Test\" on the other device. 545 \nWhen the test is complete, move to the next item. You must complete all tests. 546 </string> 547 <string name="ble_coc_insecure_client_test_info"> 548 The Bluetooth LE CoC test must be done simultaneously on two devices. This device is the client. 549 All tests listed here must be done without pairing. 550 </string> 551 <string name="ble_coc_insecure_server_test_list_name">Bluetooth LE CoC Insecure Server Test</string> 552 <string name="ble_coc_insecure_server_test_list_info"> 553 This test is mostly automated, but requires some user interaction. 554 Once the list items below have check marks, the test is complete. 555 \n\nTap \"01 Bluetooth LE CoC Server Test\" on this device, then tap \"01 Bluetooth LE CoC Client Test\" on the other device. 556 \nWhen the test is complete, move to the next item. You must complete all tests. 557 </string> 558 559 <string name="ble_coc_secure_client_test_list_name">Bluetooth LE CoC Secure Client Test</string> 560 <string name="ble_coc_secure_client_test_list_info"> 561 The Bluetooth LE CoC test must be done simultaneously on two devices. This device is the client. 562 All tests listed here must be done with pairing. Tap \"Bluetooth LE CoC Secure Server Test\" on the other device. 563 \n\nTap \"01 Bluetooth LE CoC Client Test\" on this device, then tap \"01 Bluetooth LE CoC Server Test\" on the other device. 564 \nWhen the test is complete, move to the next item. You must complete all tests. 565 </string> 566 <string name="ble_coc_secure_client_test_info"> 567 The Bluetooth LE CoC test must be done simultaneously on two devices. This device is the client. 568 All tests listed here must be done with pairing. 569 </string> 570 <string name="ble_coc_secure_server_test_list_name">Bluetooth LE CoC Secure Server Test</string> 571 <string name="ble_coc_secure_server_test_list_info"> 572 This test is mostly automated, but requires some user interaction. 573 Once the list items below have check marks, the test is complete. 574 \n\nTap \"01 Bluetooth LE CoC Server Test\" on this device, then tap \"01 Bluetooth LE CoC Client Test\" on the other device. 575 \nWhen the test is complete, move to the next item. You must complete all tests. 576 </string> 577 578 <!-- BLE CoC client side strings --> 579 <string name="ble_coc_client_test_name">01 Bluetooth LE CoC Client Test</string> 580 <string name="ble_coc_client_le_connect">Bluetooth LE Client Connect</string> 581 <string name="ble_coc_client_get_psm">Get peer PSM value</string> 582 <string name="ble_coc_client_coc_connect">LE CoC client Connect</string> 583 <string name="ble_coc_client_check_connection_type">Check connection type</string> 584 <string name="ble_coc_client_send_data_8bytes">Send 8 bytes</string> 585 <string name="ble_coc_client_receive_data_8bytes">Receive 8 bytes</string> 586 <string name="ble_coc_client_data_exchange">Send and receive large data buffer</string> 587 588 <!-- BLE CoC server side strings --> 589 <string name="ble_coc_server_start_name">01 Bluetooth LE CoC Server Test</string> 590 <string name="ble_coc_server_le_connect">Bluetooth LE Server Connect</string> 591 <string name="ble_coc_server_create_listener">Create LE CoC listener</string> 592 <string name="ble_coc_server_psm_read">Waiting on PSM to be read</string> 593 <string name="ble_coc_server_connection">Waiting on LE CoC connection</string> 594 <string name="ble_coc_server_check_connection_type">Check connection type</string> 595 <string name="ble_coc_server_receive_data_8bytes">Waiting to receive 8 bytes</string> 596 <string name="ble_coc_server_send_data_8bytes">Sending 8 bytes</string> 597 <string name="ble_coc_server_data_exchange">Send and receive large data buffer</string> 598 599 <string name="bt_connection_access_server">Connection Access Server</string> 600 <string name="bt_connection_access_client">Connection Access Client</string> 601 <string name="bt_connection_access_server_info"> 602 Start the CTS Verifier on another device, start the Bluetooth test, and choose 603 \"Connection Access Client\" to setup the test. 604 \n\nFirst, unpair the devices via Bluetooth settings. Then connect the devices together 605 using the \"Make Discoverable\" and \"Pick Server\" buttons. 606 \n\nA connection access request should appear on the server and enable the pass button. 607 </string> 608 <string name="bt_connection_access_client_info"> 609 Start the CTS Verifier on another device, start the Bluetooth test, and choose 610 \"Connection Access Server\" to complete the test. 611 \n\nMake the device acting as the server discoverable and connect to it via the 612 \"Pick Server\" button. Check that the server displays the connection access request 613 dialog. The client device does not need to do anything else. 614 </string> 615 <string name="bt_ca_dialog">Was the connection access request dialog shown?</string> 616 <string name="bt_ca_tips"> 617 Tap the \"Bluetooth Settings\" button and check that both devices are not paired 618 before running the test. 619 \n\nUse the \"Make Discoverable\" and \"Pick Server\" buttons to connect the two Bluetooth 620 devices together and start the test. 621 </string> 622 623 <!-- Strings for HidHost and HidDevice activity --> 624 <string name="bt_hid_host_test_name">Bluetooth HID Host Test</string> 625 <string name="bt_hid_host_test_info"> 626 Start the CTS Verifier on another device, start the Bluetooth test, and choose 627 \"Bluetooth HID Device\" to complete the test. 628 \n\nClick \"Register app\" and \"Make discoverable\" on another device first, and click 629 \"Select device\". Choose the device from device picker. If the remote device is already 630 paired, unpair it first from system Settings. 631 \n\nAfter the remote device completes the \"Send_report\" command, text \"bluetooth\" should 632 appear in the EditText. Mark the test as passed. 633 \n\n If the device under test (DUT) does not have Bluetooth HID Host service or HID Device 634 service enabled, mark the test as passed. 635 </string> 636 <string name="bt_hid_host">Bluetooth HID Host</string> 637 <string name="bt_hid_host_select_device">Select device</string> 638 639 <string name="bt_hid_device_test_name">Bluetooth HID Device Test</string> 640 <string name="bt_hid_device_test_info"> 641 Start the CTS Verifier on another device, start the Bluetooth test, and choose 642 \"Bluetooth HID Host\" to complete the test. 643 \n\nFirst, click the \"Register app\" button, and click the \"Make discoverable\" button. 644 \n\nThen, on another device, click the \"Select device" button, and choose this device. 645 \n\nWait until the dialog shows up for pairing two devices. 646 \n\nFinally, click the \"Test send_report\", \"Test reply_report\", \"Test report_error\". 647 \n\nIf all the commands are successful, then click \"Unregister app\" and mark the test as 648 passed. 649 \n\n If the device under test (DUT) does not have Bluetooth HID Host service or HID Device 650 service enabled, mark the test as passed. 651 </string> 652 653 <string name="bt_hid_device">Bluetooth HID Device</string> 654 <string name="bt_hid_device_register">Register app</string> 655 <string name="bt_hid_device_unregister">Unregister app</string> 656 <string name="bt_hid_device_send_report">Test Send_report</string> 657 <string name="bt_hid_device_reply_report">Test Reply_report</string> 658 <string name="bt_hid_device_report_error">Test Report_error</string> 659 660 661 <string name="bt_secure_server">Secure Server</string> 662 <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> 663 <string name="bt_insecure_server">Insecure Server</string> 664 <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> 665 <string name="bt_waiting">Waiting for client...</string> 666 <string name="bt_listening">Listening...</string> 667 <string name="bt_connecting">Connecting...</string> 668 <string name="bt_connected">Connected</string> 669 <string name="bt_received_messages">Received Messages</string> 670 <string name="bt_sent_messages">Sent Messages</string> 671 <string name="bt_no_messages">No messages</string> 672 <string name="bt_make_discoverable">Make Discoverable</string> 673 <string name="bt_pick_server">Pick Server</string> 674 <string name="bt_insecure_pairing_error_title">Pairing dialog shown?</string> 675 <string name="bt_insecure_pairing_error_message">Insecure connections should not show the pairing dialog!</string> 676 <string name="bt_advertise_unsupported_title">Advertising is not supported</string> 677 <string name="bt_advertise_unsupported_message">Advertising is not supported on this device.\nTest finishes.</string> 678 <string name="bt_open_failed_title">BLE open failed</string> 679 <string name="bt_open_failed_message">Cannot open BLE GattService.\nTest finishes.</string> 680 <string name="bt_add_service_failed_title">Add service failed</string> 681 <string name="bt_add_service_failed_message">Failed to add services.\nTest finishes.</string> 682 683 <string name="bt_secure_client">Secure Client</string> 684 <string name="bt_insecure_client">Insecure Client</string> 685 686 <string name="bt_device_picker">Device Picker</string> 687 <string name="bt_paired_devices">Paired Devices</string> 688 <string name="bt_new_devices">New Devices</string> 689 <string name="bt_no_devices">No devices</string> 690 <string name="bt_scan">Scan for Devices</string> 691 <string name="bt_scanning">Scanning...</string> 692 <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> 693 <string name="bt_settings">Bluetooth Settings</string> 694 695 <!-- BLE client side strings --> 696 <string name="ble_client_service_name">Bluetooth LE GATT Client Handler Service</string> 697 <string name="ble_client_test_name">01 Bluetooth LE Client Test</string> 698 <string name="ble_client_connect_name">Bluetooth LE Client Connect</string> 699 <string name="ble_discover_service_name">Bluetooth LE Discover Service</string> 700 <string name="ble_read_characteristic_name">Bluetooth LE Read Characteristic</string> 701 <string name="ble_write_characteristic_name">Bluetooth LE Write Characteristic</string> 702 <string name="ble_reliable_write_name">Bluetooth LE Reliable Write</string> 703 <string name="ble_reliable_write_bad_resp_name">Bluetooth LE Reliable Write (receive bad response)</string> 704 <string name="ble_notify_characteristic_name">Bluetooth LE Notify Characteristic</string> 705 <string name="ble_read_descriptor_name">Bluetooth LE Read Descriptor</string> 706 <string name="ble_write_descriptor_name">Bluetooth LE Write Descriptor</string> 707 <string name="ble_read_rssi_name">Bluetooth LE Read RSSI</string> 708 <string name="ble_read_phy_name">Bluetooth LE Read PHY</string> 709 <string name="ble_set_preferred_phy_name">Bluetooth LE Set Preferred PHY</string> 710 <string name="ble_on_service_changed">Bluetooth LE On Service Changed</string> 711 <string name="ble_client_disconnect_name">Bluetooth LE Client Disconnect</string> 712 <string name="ble_insecure_client_test_info"> 713 The Bluetooth LE test must be done simultaneously on two devices. This device is the client. 714 All tests listed here must be done without pairing. 715 </string> 716 <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> 717 <string name="ble_discover_service_info">Verify that the service is discovered when you press the "Discover Service" button.</string> 718 <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> 719 <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> 720 <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> 721 <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> 722 <string name="ble_client_disconnect_info">Verify that the device is disconnected when you press the "Disconnect" button</string> 723 <string name="ble_address">Bluetooth address</string> 724 <string name="ble_connect">Connect</string> 725 <string name="ble_discover_service">Discover service</string> 726 <string name="ble_write_hint">Nothing to write yet</string> 727 <string name="ble_read_hint">Nothing read yet</string> 728 <string name="ble_write">Write</string> 729 <string name="ble_read">Read</string> 730 <string name="ble_begin_write">Begin write</string> 731 <string name="ble_execute_write">Execute write</string> 732 <string name="ble_begin_notification">Begin notification</string> 733 <string name="ble_stop_notification">Stop notification</string> 734 <string name="ble_waiting_notification">Waiting on notification</string> 735 <string name="ble_read_rssi">Read RSSI</string> 736 <string name="ble_disconnect">Disconnect</string> 737 <string name="ble_test_text">TEST</string> 738 <string name="ble_test_finished">Test finished</string> 739 <string name="ble_test_next">Next</string> 740 <string name="ble_test_running">Test Running</string> 741 <string name="ble_test_running_message">This test requires a few minutes. Don\'t interrupt the test.</string> 742 <string name="ble_mtu_23_name">Bluetooth LE Request MTU(23bytes)</string> 743 <string name="ble_mtu_512_name">Bluetooth LE Request MTU(512bytes)</string> 744 745 <!-- BLE server side strings --> 746 <string name="ble_server_service_name">Bluetooth LE GATT Server Handler Service</string> 747 <string name="ble_server_start_name">01 Bluetooth LE Server Test</string> 748 <string name="ble_server_start_info"> 749 The Bluetooth LE test must be done simultaneously on two devices, a server device and a client device. This device is the server. 750 </string> 751 <string name="ble_server_receiving_connect">Waiting on connection from Bluetooth LE client.</string> 752 <string name="ble_server_add_service">Adding service to Bluetooth LE server.</string> 753 <string name="ble_server_write_characteristic">Waiting on write characteristic request</string> 754 <string name="ble_server_read_characteristic">Waiting on read characteristic request</string> 755 <string name="ble_server_write_descriptor">Waiting on write descriptor request</string> 756 <string name="ble_server_read_descriptor">Waiting on read descriptor request</string> 757 <string name="ble_server_reliable_write">Waiting on reliable write from client</string> 758 <string name="ble_server_reliable_write_bad_resp">Waiting on reliable write from client (send bad response)</string> 759 <string name="ble_server_service_changed_indication">Waiting on service changed indication</string> 760 <string name="ble_server_receiving_disconnect">Waiting on disconnection from Bluetooth LE client</string> 761 <string name="ble_connection_priority_server_name">02 Bluetooth LE Connection Priority Server Test</string> 762 <string name="ble_connection_priority_server_info">Bluetooth LE Connection Priority Server receive message from message in 3 different priority.</string> 763 <string name="ble_server_notify_characteristic">Waiting on notify characteristic request</string> 764 <string name="ble_server_write_characteristic_without_permission">Waiting on write characteristic request without permission</string> 765 <string name="ble_server_read_characteristic_without_permission">Waiting on read characteristic request without permission</string> 766 <string name="ble_server_write_descriptor_without_permission">Waiting on write descriptor request without permission</string> 767 <string name="ble_server_read_descriptor_without_permission"> Waiting on read descriptor request without permission</string> 768 <string name="ble_server_write_characteristic_need_encrypted">Waiting on write encrypted characteristic request</string> 769 <string name="ble_server_read_characteristic_need_encrypted">Waiting on read encryptedcharacteristic request</string> 770 <string name="ble_server_write_descriptor_need_encrypted">Waiting on write encrypted descriptor request</string> 771 <string name="ble_server_read_descriptor_need_encrypted"> Waiting on read encrypted descriptor request</string> 772 <string name="ble_server_indicate_characteristic">Waiting on indicate characteristic request</string> 773 <string name="ble_server_mtu_23bytes">Waiting on MTU request(23 bytes)</string> 774 <string name="ble_server_mtu_512bytes">Waiting on MTU request(512 bytes)</string> 775 <string name="ble_encrypted_server_name">03 Bluetooth LE Encrypted Server Test</string> 776 <string name="ble_encrypted_server_info">Bluetooth LE Encrypted Server Waiting on read/write characteristic and descriptor request need encrypted.</string> 777 <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> 778 <string name="ble_insecure_server_test_list_name">Bluetooth LE Insecure Server Test</string> 779 <string name="ble_insecure_server_test_list_info"> 780 This test is mostly automated, but requires some user interaction. 781 Once the list items below have check marks, the test is complete. 782 \n\nTap \"01 Bluetooth LE Server Test\" on this device, then tap \"01 Bluetooth LE Client Test\" on the other device. 783 \nWhen the test is complete, move to the next item. You must complete all tests. 784 </string> 785 <string name="ble_secure_server_test_list_name">Bluetooth LE Secure Server Test</string> 786 <string name="ble_secure_server_test_list_info"> 787 This test is mostly automated, but requires some user interaction. 788 You can pass this test once the list items below are checked. 789 \n\nTap \"01 Bluetooth LE Server Test\" on this device, then tap \"01 Bluetooth LE Client Test \"on other device. 790 \nTest completed, then test next item. You must be done all tests. 791 </string> 792 793 <!-- BLE advertiser side strings --> 794 <string name="ble_advertiser_test_name">Bluetooth LE Advertiser Test</string> 795 <string name="ble_advertiser_test_info"> 796 The Bluetooth LE Advertiser Test and Scanner Test is a paired test. 797 \nTap \"Bluetooth LE Advertiser Test\" on this device. Once it is passed, tap \"Bluetooth LE Scanner Test\". 798 \nTap \"Bluetooth LE Scanner Test\" on this device. Once it is passed, tap \"Bluetooth LE Advertiser Test\". 799 </string> 800 <string name="ble_advertiser_service_name">Bluetooth LE Advertiser Handler Service</string> 801 <string name="ble_privacy_mac_name">Bluetooth LE Privacy Mac</string> 802 <string name="ble_privacy_mac_info">Bluetooth LE Advertiser should advertise in non-repeating MAC address.</string> 803 <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> 804 <string name="ble_power_level_name">Bluetooth LE Tx Power Level</string> 805 <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> 806 <string name="ble_advertiser_power_level_instruction"> 807 Click start to start multi-advertising. Data packets are advertised in 4 different power levels. 808 You may receive a message that this device does not support multi-advertising. 809 If the advertiser does not advertise in 4 power levels, and you do not receive an error message, 810 you may not have stopped advertising in the previous test, or this device may not support 4 advertisers at the same time. 811 Try rebooting the device and running the test again to free those advertisers in use. 812 </string> 813 <string name="ble_advertiser_scan_filter_name">Bluetooth LE Hardware Scan Filter</string> 814 <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> 815 <string name="ble_advertiser_scannable">Scannable advertising</string> 816 <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> 817 <string name="ble_advertiser_unscannable">Unscannble advertising</string> 818 <string name="ble_advertiser_unscannable_instruction">Start unscannable advertising, expect scanner stay calm on Monsoon monitor, no log of GattService from scanner logcat.</string> 819 <string name="ble_advertiser_start">Start</string> 820 <string name="ble_advertiser_stop">Stop</string> 821 822 <!-- BLE scanner side strings --> 823 <string name="ble_scanner_test_name">Bluetooth LE Scanner Test</string> 824 <string name="ble_scanner_service_name">Bluetooth LE Scanner Handler Service</string> 825 <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> 826 <string name="ble_scanner_privacy_mac">Hold for 15 min to see if receive a different MAC address from advertiser.</string> 827 <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> 828 <string name="ble_ultra_low">Ultra low</string> 829 <string name="ble_low">Low</string> 830 <string name="ble_medium">Medium</string> 831 <string name="ble_high">High</string> 832 <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> 833 <string name="ble_scanner_scan_filter_name">BLE Hardware Scan Filter</string> 834 <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> 835 <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> 836 <string name="ble_scan_with_filter">Scan with filter</string> 837 <string name="ble_scan_without_filter">Scan without filter</string> 838 <string name="ble_scan_start">Start scan</string> 839 <string name="ble_scan_stop">Stop scan</string> 840 841 <!-- BLE Advertising Set test strings --> 842 <string name="ble_advertising_set_test_name">Bluetooth LE Advertising Set Test</string> 843 <string name="ble_advertising_set_test_info">Bluetooth LE Advertising Set tests AdvertisingSet and AdvertisingSetCallback APIs.</string> 844 <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> 845 <string name="ble_advertising_set_start_test">Start Test</string> 846 <string name="ble_advertising_set_running_test">Running Test...</string> 847 <string name="ble_advertising_set_finished_test">Finished Test</string> 848 <string name="ble_advertising_set_start">Starting advertising set.</string> 849 <string name="ble_advertising_set_enable_disable">Enabling/Disabling advertising set.</string> 850 <string name="ble_advertising_set_advertising_data">Setting advertising data.</string> 851 <string name="ble_advertising_set_advertising_params">Setting advertising parameters.</string> 852 <string name="ble_advertising_set_periodic_advertising_data">Setting periodic advertising data.</string> 853 <string name="ble_advertising_set_periodic_advertising_enabled_disabled">Enabling/Disabling periodic advertising.</string> 854 <string name="ble_advertising_set_periodic_advertising_params">Setting periodic advertising parameters.</string> 855 <string name="ble_advertising_set_scan_response_data">Setting scan response data.</string> 856 <string name="ble_advertising_set_stop">Stopping advertising set.</string> 857 858 <!-- BLE connection priority test strings --> 859 <string name="ble_client_connection_priority">Testing connection priority switching </string> 860 <string name="ble_server_connection_priority_result_passed">All test passed</string> 861 <string name="ble_server_connection_priority_result_failed">Test failed.</string> 862 <string name="ble_server_connection_priority_result_intervals"> 863 Transfer interval time (msec):\nHIGH=%1$d\nBALANCED=%2$d\nLOW=%3$d\n\nRequirements:\n HIGH <= BALANCED <= LOW 864 </string> 865 866 <!-- BLE Test Name --> 867 <string name="ble_secure_client_test_name">Bluetooth LE Secure Client Test</string> 868 <string name="ble_insecure_client_test_name">Bluetooth LE Insecure Client Test</string> 869 <string name="ble_secure_server_test_name">Bluetooth LE Secure Server Test</string> 870 <string name="ble_insecure_server_test_name">Bluetooth LE Insecure Server Test</string> 871 872 <string name="ble_coc_secure_client_test_name">Bluetooth LE CoC Secure Client Test</string> 873 <string name="ble_coc_insecure_client_test_name">Bluetooth LE CoC Insecure Client Test</string> 874 <string name="ble_coc_secure_server_test_name">Bluetooth LE CoC Secure Server Test</string> 875 <string name="ble_coc_insecure_server_test_name">Bluetooth LE CoC Insecure Server Test</string> 876 877 <string name="ble_read_characteristic_nopermission_name">Bluetooth LE Read Characteristic Without Perrmission</string> 878 <string name="ble_write_characteristic_nopermission_name">Bluetooth LE Write Characteristic Without Permission</string> 879 <string name="ble_read_descriptor_nopermission_name">Bluetooth LE Read Descriptor Without Perrmission</string> 880 <string name="ble_write_descriptor_nopermission_name">Bluetooth LE Write Descriptor Without Permission</string> 881 <string name="ble_connection_priority_client_name">02 Bluetooth LE Connection Priority Client Test</string> 882 <string name="ble_connection_priority_client_info">Bluetooth LE Connection Priority Client send message in 3 different priority.</string> 883 <string name="ble_read_authenticated_characteristic_name">Bluetooth LE Read Encrypted Characteristic</string> 884 <string name="ble_write_authenticated_characteristic_name">Bluetooth LE Write Encrypted Characteristic</string> 885 <string name="ble_read_authenticated_descriptor_name">Bluetooth LE Read Encrypted Descriptor</string> 886 <string name="ble_write_authenticated_descriptor_name">Bluetooth LE Write Encrypted Descriptor</string> 887 <string name="ble_connection_priority_client_description">Client Switching Connection Priority</string> 888 <string name="ble_indicate_characteristic_name">Bluetooth LE Indicate Characteristic</string> 889 <string name="ble_encrypted_client_name">03 Bluetooth LE Encrypted Client Test</string> 890 <string name="ble_encrypted_client_info">Bluetooth LE Encrypted Client read/write on characteristic and descriptor need encrypted.</string> 891 <string name="ble_insecure_client_test_list_name">Bluetooth LE Insecure Client Test</string> 892 <string name="ble_insecure_client_test_list_info"> 893 The Bluetooth LE test must be done simultaneously on two devices. This device is the client. 894 All tests listed here must be done without pairing. Tap \"Bluetooth LE Insecure Server Test\" on the other device. 895 \n\nTap \"01 Bluetooth LE Client Test\" on this device, then tap \"01 Bluetooth LE Server Test\" on the other device. 896 \nWhen the test is complete, move to the next item. You must complete all tests. 897 </string> 898 <string name="ble_secure_client_test_list_name">Bluetooth LE Secure Client Test</string> 899 <string name="ble_secure_client_test_list_info"> 900 The Bluetooth LE test must be done simultaneously on two devices. 901 This device is the client. All tests listed here must be done with pairing. 902 \n\nTap \"01 Bluetooth LE Client Test\" on this device, then tap \"01 Bluetooth LE Server Test\" on the other device. 903 \nWhen the test is complete, move to the next item. You must complete all tests. 904 </string> 905 <string name="ble_encrypted_client_no_encrypted_characteristic">Error!\nThe Characteristics unencrypted.</string> 906 <string name="ble_encrypted_client_no_encrypted_descriptor">Error!\nThe Descriptor unencrypted.</string> 907 <string name="ble_encrypted_client_fail_write_encrypted_characteristic">It failed to write to Characteristic.</string> 908 <string name="ble_encrypted_client_fail_write_encrypted_descriptor">It failed to write to Descriptor.</string> 909 <string name="ble_encrypted_client_fail_read_encrypted_characteristic">It failed to read the Characteristic.</string> 910 <string name="ble_encrypted_client_fail_read_encrypted_descriptor">It failed to read the Descriptor.</string> 911 <string name="ble_secure_client_test_info"> 912 The Bluetooth LE test must be done simultaneously on two devices. This device is the client. 913 All tests listed here must be done with pairing. 914 </string> 915 916 <string name="ble_bluetooth_disable_title">Bluetooth Disable!</string> 917 <string name="ble_bluetooth_disable_message">Please set bluetooth enable.</string> 918 919 <string name="ble_bluetooth_mismatch_title">Bluetooth pairing state is a mismatch!</string> 920 <string name="ble_bluetooth_mismatch_secure_message"> 921 And even though it has already been trying to run a test of Secure, the device has not been paired. 922 \nGo setting mode, set Bluetooth to pair other device. 923 </string> 924 <string name="ble_bluetooth_mismatch_insecure_message"> 925 And even though it has already been trying to run a test of Insecure, the device has already been paired. 926 \nGo setting mode, set Bluetooth to unpair other device. 927 </string> 928 929 <string name="ble_mtu_unexpected_message">Unexpected MTU request</string> 930 <string name="ble_mtu_mismatch_message">MTU is not correct.(Request:%1$d, Actual:%2$d)</string> 931 <string name="ble_mtu_fail_message">MTU test: failed to receive data</string> 932 933 <!-- Strings for CompanionDeviceTestActivity --> 934 <string name="companion_test">Companion Device Test</string> 935 <string name="companion_test_info"> 936 This test checks that APIs to manage companion devices are working correctly, 937 including showing the dialog to the user to verify a device, as well as updating an internal 938 record once the user made the choice and then removing it.\n\n 939 Before proceeding, make sure you have a bluetooth device nearby and discoverable. 940 Also, make sure that bluetooth is turned on for this device. 941 Once you press the button, wait for a dialog to pop up and select your device from the list. 942 </string> 943 944 <!-- Strings for CompanionDeviceServiceTestActivity --> 945 <string name="companion_service_associate_button">Associate</string> 946 <string name="companion_service_associate_title">Device Association</string> 947 <string name="companion_service_associate_text"> 948 Press the "Associate" button. Wait for a dialog to pop up and select your device from the 949 list. 950 </string> 951 <string name="companion_service_bluetooth_feature_title">Bluetooth Feature Supported</string> 952 <string name="companion_service_bluetooth_feature_text"> 953 PackageManager.FEATURE_BLUETOOTH not supported. This test is not applicable. 954 </string> 955 <string name="companion_service_disassociate_button">Disassociate</string> 956 <string name="companion_service_disassociate_title">Device Disassociation</string> 957 <string name="companion_service_disassociate_text"> 958 Press the "Disassociate" button. Wait for the device to disassociate. 959 </string> 960 <string name="companion_service_present_title">Device Present</string> 961 <string name="companion_service_present_text"> 962 Make your Bluetooth device reachable (this should already be the case from the previous step). 963 Wait until your Bluetooth device is detected by CDM. This may take up to 2 minutes. 964 </string> 965 <string name="companion_service_gone_title">Device Gone</string> 966 <string name="companion_service_gone_text"> 967 Make your Bluetooth device unreachable by placing your bluetooth device inside an RF Bag or 968 powering it off. 969 Wait until your Bluetooth device disappears. This may take up to 2 minutes. 970 </string> 971 <string name="companion_service_test">Companion Device Service Test</string> 972 <string name="companion_service_test_info"> 973 This test checks that APIs to notify the companion app of its associated device going in and 974 out of Bluetooth range are working correctly.\n\n 975 Before proceeding, make sure that you have a Bluetooth LE device nearby and 976 discoverable. Also, make sure that bluetooth is turned on. (Note: the nearby device cannot 977 be a phone) 978 </string> 979 <string name="companion_service_test_summary_title">Test Complete</string> 980 <string name="companion_service_test_summary">Every test passed successfully.</string> 981 982 <!-- Strings for FeatureSummaryActivity --> 983 <string name="feature_summary">Hardware/Software Feature Summary</string> 984 <string name="feature_summary_info">This is a test for...</string> 985 <string name="fs_disallowed">WARNING: device reports a disallowed feature name</string> 986 <string name="fs_missing_wifi_telephony">WARNING: device reports neither WiFi nor telephony</string> 987 <string name="fs_no_data">No data.</string> 988 <string name="fs_legend_good">standard feature reported by device</string> 989 <string name="fs_legend_indeterminate">optional feature not reported by device</string> 990 <string name="fs_legend_warning">non-standard feature reported by device</string> 991 <string name="fs_legend_error">required feature not reported, or forbidden feature reported</string> 992 993 <string name="empty"></string> 994 995 <!-- Strings for HifiUltrasoundTestActivity --> 996 <string name="hifi_ultrasound_test">Hifi Ultrasound Microphone Test</string> 997 <string name="hifi_ultrasound_test_info"> 998 This is a test for near-ultrasound (18500Hz - 20000Hz) microphone response.\n 999 This test requires two devices.\n</string> 1000 <string name="hifi_ultrasound_test_play">PLAY</string> 1001 <string name="hifi_ultrasound_test_record">RECORD</string> 1002 <string name="hifi_ultrasound_test_plot">PLOT</string> 1003 <string name="hifi_ultrasound_test_dismiss">DISMISS</string> 1004 <string name="hifi_ultrasound_test_ok">OK</string> 1005 <string name="hifi_ultrasound_test_instruction1"> 1006 Open Hifi Ultrasound Microphone Test on the test device and the reference device.\n 1007 Set the media volume of the reference device at 70% and hold it with one hand.\n 1008 Hold the testing device with the other hand\n 1009 Press the RECORD button on the testing device, then the PLAY button on the reference device within one second.\n 1010 After the test, report result on the testing (recording) device.\n</string> 1011 <string name="hifi_ultrasound_test_pass">PASS</string> 1012 <string name="hifi_ultrasound_test_fail">FAIL</string> 1013 <string name="hifi_ultrasound_test_default_false_string">false</string> 1014 <string name="hifi_ultrasound_test_mic_no_support"> 1015 Device does not support near-ultrasound recording.\n 1016 Please report PASS.\n</string> 1017 <string name="hifi_ultrasound_test_spkr_no_support"> 1018 Device does not support near-ultrasound playback.\n 1019 If this is your reference device, please use a different reference device.\n</string> 1020 1021 <string name="hifi_ultrasound_speaker_test">Hifi Ultrasound Speaker Test</string> 1022 <string name="hifi_ultrasound_speaker_test_info"> 1023 This is a test for near-ultrasound (18500Hz - 20000Hz) speaker response.\n 1024 This test requires two devices.\n</string> 1025 <string name="hifi_ultrasound_speaker_test_instruction1"> 1026 Open Hifi Ultrasound Speaker Test on the test device and the reference device.\n 1027 Set the media volume of the testing device at 70% and hold it with one hand.\n 1028 Hold the reference device with the other hand\n 1029 Press the RECORD button on the reference device, then the PLAY button on the testing device within one second.\n 1030 After the test, report result on the testing (playback) device.\n</string> 1031 <string name="hifi_ultrasound_speaker_test_mic_no_support"> 1032 Device does not support near-ultrasound recording.\n 1033 If this is your reference device, please use a different reference device.\n</string> 1034 <string name="hifi_ultrasound_speaker_test_spkr_no_support"> 1035 Device does not support near-ultrasound playback.\n 1036 Please report PASS.\n</string> 1037 <string name="hifi_ultrasound_speaker_test_test_side"> 1038 Please wait for the result on the reference device then report here.</string> 1039 <string name="hifi_ultrasound_speaker_test_reference_side"> 1040 Please report on the testing device.\n</string> 1041 1042 <!-- Strings for IgnoreBatteryOptimizationsTestActivity --> 1043 <string name="ibo_test">Ignore Battery Optimizations Test</string> 1044 <string name="ibo_test_info"> 1045 This test verifies that the device provides a user affordance to ask the user if the system 1046 should disable battery optimizations for an app and to allow a user to remove the app from 1047 the exemption list. 1048 </string> 1049 <string name="ibo_auto_power_modes_enabled">Auto power modes enabled.</string> 1050 <string name="ibo_test_start_unexempt_app"> 1051 Remove the test app from the ignore battery optimizations list to begin the test. (Try going 1052 to the App Info page and make sure the system is optimizing battery for the app.) 1053 </string> 1054 <string name="ibo_exempt_app_request"> 1055 Click Next to have the test request the exemption. Grant the exemption when prompted. 1056 </string> 1057 <string name="ibo_next_to_confirm">Press next to confirm.</string> 1058 <string name="ibo_app_not_exempted">The app is not exempted from battery optimizations.</string> 1059 <string name="ibo_unexempt_app"> 1060 Remove the test app from the ignore battery optimizations list. (Either run \"adb shell cmd 1061 deviceidle whitelist -com.android.cts.verifier\" or open the list of apps and their 1062 exemption statuses. Find the test app in the list and remove the app\'s exemption.) 1063 </string> 1064 <string name="ibo_app_is_exempted">The app is exempted from battery optimizations.</string> 1065 <string name="ibo_exempt_app_list"> 1066 Click Next to have the test open the list of apps and their exemption statuses. Find the 1067 test app in the list and exempt it. 1068 </string> 1069 <string name="ibo_unexempt_app_list"> 1070 Click Next to have the test open the list of apps and their exemption statuses. Find the 1071 test app in the list and remove the app\'s exemption. 1072 </string> 1073 1074 <!-- Strings for Location tests --> 1075 <string name="location_gps_test">GPS Test</string> 1076 <string name="location_gps_test_info">This test verifies basic GPS behavior 1077 and callback scheduling. 1078 Make sure the device has line of sight to GPS satellites 1079 (for example, outside, or near a window) 1080 and then press OK to run the automated tests.</string> 1081 1082 <!-- Strings for Location GNSS tests --> 1083 <string name="location_gnss_constellation_type_test">GNSS Measurement Constellation Test</string> 1084 <string name="location_gnss_measure_no_location_test">GNSS Measurement Before Location Test</string> 1085 <string name="location_gnss_reg_test">GNSS Measurement Registration Test</string> 1086 <string name="location_gnss_value_test">GNSS Measurement Values Test</string> 1087 <string name="location_pseudorange_value_test">GNSS Pseudorange Test</string> 1088 <string name="location_gnss_ttff_test">GNSS TTFF Test</string> 1089 <string name="location_gnss_nav_msg_test">GNSS Navigation Message Test</string> 1090 <string name="location_gnss_status_test">GNSS Status Test</string> 1091 <string name="location_gnss_test_info">This test verifies basic GNSS behavior. 1092 Make sure the device has line of sight to GNSS satellites 1093 (for example, stationary on a windowsill. If needed, try again, outside, also with the 1094 device stationary, and with at least some view of the sky.) and then press Next to run 1095 the automated tests.</string> 1096 <string name="location_emergency_call_test_info">This test verifies whether basic features 1097 (wifi, sms, gps) works correctly during the emergency call. Make sure the device is using 1098 a special white listed sim card. The wifi and GPS should be on and have internet connection. 1099 Press the pass button to skip this test if outside US/Canada. 1100 </string> 1101 <string name="emergency_call_confirm_info">This test will dial 911! Please make sure to use a 1102 whitelisted sim card to run this test! 1103 </string> 1104 <string name="emergency_call_skip_info">Current device doesn\'t support cellular network. Skipping the Test. 1105 </string> 1106 <string name="emergency_call_emergency_number_hint_text"> 1107 Emergency Number: 1108 </string> 1109 <string name="emergency_call_current_number_hint_text"> 1110 Current Number: 1111 </string> 1112 <string name="emergency_call_dial_text"> 1113 Dial 911 1114 </string> 1115 <string name="emergency_call_emergency_number_text"> 1116 911 1117 </string> 1118 <string name="location_gnss_test_retry_info">If this test fails, please make sure the device 1119 has line of sight to GNSS satellites (for example, stationary on a windowsill. If needed, 1120 try again, outside, also with the device stationary, with as much view of the sky as 1121 possible.) </string> 1122 <string name="location_emergency_call_gps_test">Emergency Call GPS Test</string> 1123 <string name="location_emergency_call_message_test">Emergency Call Message Test</string> 1124 <string name="location_emergency_call_wifi_test">Emergency Call Wifi Test</string> 1125 1126 <!-- Strings for ConnectivityBackgroundTestActivity --> 1127 <string name="network_background_test">Network Background Connectivity Test</string> 1128 <string name="network_background_test_instructions"> 1129 This test verifies that IPv6 network connectivity continues to work 1130 when the screen is off or is idle for some time.\n\n 1131 1132 1. Join a Wi-Fi network with IPv6 Internet access.\n 1133 2. If the device has battery power, disconnect all power connectors.\n 1134 3. Turn the screen off if possible.\n 1135 4. Wait until the screen turns on or the test result is displayed (it will take at least two minutes).\n 1136 5. If necessary, unlock the device.\n 1137 6. Please mark the test according to the result status indicated.\n 1138 </string> 1139 <string name="network_background_test_start">Start</string> 1140 1141 <!-- Strings for net.MultiNetworkConnectivityTestActivity --> 1142 <string name="multinetwork_connectivity_test">Multinetwork connectivity Test</string> 1143 <string name="multinetwork_connectivity_test_instructions"> 1144 This test verifies that, when a phone has internet connectivity via mobile network 1145 is connected to a Wi-Fi access point that doesn\'t have internet or loses internet access, 1146 it restores the internet activity over the mobile cell network, while connected to the 1147 Wi-Fi access point. \n\n 1148 1149 1. Setup a wireless access point with ability to turn on and off internet access. 1150 2. Have SIM or cellular data connectivity on the phone being tested. 1151 3. Execute the tests with the instructions outlined in the test 1152 4. When the test completes, it will finish and mark it passed. If it fails, it will mark it \n 1153 as failed. 1154 1155 </string> 1156 <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> 1157 <string name="multinetwork_connectivity_test_start">Start</string> 1158 <string name="multinetwork_connectivity_test_ap_name">Wi-Fi SSID</string> 1159 <string name="multinetwork_connectivity_test_ap_passphrase">WPA 2 passphrase</string> 1160 <string name="multinetwork_connectivity_test_continue">Confirm and continue with test.</string> 1161 <string name="multinetwork_connectivity_test_rerun">Completed. Re-run.</string> 1162 <string name="multinetwork_connectivity_test_running">Running.</string> 1163 <string name="multinetwork_connectivity_test_connect_cellular">Connecting to cellular network.</string> 1164 <string name="multinetwork_connectivity_test_connect_wifi">Connecting to Wi-Fi network.</string> 1165 <string name="multinetwork_connectivity_test_complete">Test completed.</string> 1166 <string name="multinetwork_connectivity_test_progress_1">Waiting for Wi-Fi to lose connectivity.</string> 1167 <string name="multinetwork_connectivity_test_progress_2">Waiting to check connectivity.</string> 1168 <string name="multinetwork_connectivity_test_progress_3">Waiting to make sure Wi-Fi has connectivity.</string> 1169 <string name="multinetwork_connectivity_test_1_desc">Test 1 - Connect to Wi-Fi with no internet doesnt disable current connectivity (new API)</string> 1170 <string name="multinetwork_connectivity_test_2_desc">Test 2 - Connect to Wi-Fi with no internet doesnt disable current connectivity (legacy API)</string> 1171 <string name="multinetwork_connectivity_test_3_desc">Test 3 - When connected to Wi-Fi, on losing connectivity, restores mobile connectivity (legacy API)</string> 1172 <string name="multinetwork_status_wifi_connect_success">Wi-Fi connect success.</string> 1173 <string name="multinetwork_status_mobile_connect_success">Mobile net connect success.</string> 1174 <string name="multinetwork_status_wifi_connect_timed_out">Wi-Fi connect timed out.</string> 1175 <string name="multinetwork_status_wifi_connect_wrong_ap">Wi-Fi connected to wrong access point.</string> 1176 <string name="multinetwork_status_unable_to_toggle_wifi">User did not toggle wifi on and off.</string> 1177 <string name="multinetwork_status_mobile_connect_timed_out">Mobile network connect timed out.</string> 1178 <string name="multinetwork_status_mobile_restore_success">Mobile restore succeeded.</string> 1179 <string name="multinetwork_status_mobile_restore_failed">Mobile restore failed.</string> 1180 <string name="multinetwork_connectivity_test_1_prereq">Make sure that the Hotspot does not have internet access.</string> 1181 <string name="multinetwork_connectivity_test_2_prereq_1">Make sure that the Hotspot has internet access.</string> 1182 <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> 1183 <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> 1184 <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> 1185 <string name="multinetwork_status_wifi_connectivity_failed">Wi-Fi connectivity failed.</string> 1186 <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> 1187 <string name="multinetwork_connectivity_overlay_permission_positive">Settings</string> 1188 <string name="multinetwork_connectivity_overlay_permission_negative">Cancel</string> 1189 <string name="multinetwork_connectivity_turn_wifi_on">Please turn Wi-Fi on.</string> 1190 <string name="multinetwork_connectivity_turn_wifi_off">Please turn Wi-Fi off.</string> 1191 <string name="multinetwork_connectivity_turn_wifi_positive">OK</string> 1192 <string name="multinetwork_connectivity_turn_wifi_negative">Cancel</string> 1193 <string name="multinetwork_connectivity_connect_to_target_ap_positive">OK</string> 1194 <string name="multinetwork_connectivity_connect_to_target_ap">Connect to configured SSID: %s</string> 1195 <!-- Strings for NfcTestActivity --> 1196 <string name="nfc_test">NFC Test</string> 1197 <string name="nfc_test_info">The Peer-to-Peer Data Exchange tests require two devices with 1198 NFC enabled to exchange messages. One device must be the candidate device running the 1199 software build to be tested, while the other device must be an implementation already 1200 known to be compatible.\n\nThe Tag Verification tests check that your 1201 device can properly read and write to tags of different technologies. The MIFARE 1202 Ultralight test is only applicable for devices that support it. 1203 \n\nThe Host-based card emulation tests check that your device has properly implemented 1204 host-based card emulation. 1205 </string> 1206 1207 <string name="nfc_not_enabled">NFC is not enabled!</string> 1208 <string name="nfc_not_enabled_message">These tests require NFC to be enabled. Click the 1209 button below to goto Settings and enable it.</string> 1210 <string name="nfc_settings">NFC Settings</string> 1211 <string name="secure_nfc_enabled">\"Require device unlock for NFC\" is enabled!</string> 1212 <string name="secure_nfc_enabled_message">These tests require \"Require device unlock for NFC\" 1213 to be disabled. Click the button below to goto Settings and disable it.</string> 1214 1215 <string name="ndef_push_not_enabled">NDEF Push is not enabled!</string> 1216 <string name="ndef_push_not_enabled_message">These tests require Android Beam to be enabled. 1217 Click the button below to goto NFC Sharing Settings and enable it.</string> 1218 <string name="ndef_push_settings">NFC Sharing Settings</string> 1219 1220 <string name="nfc_pee_2_pee">Peer-to-Peer Data Exchange</string> 1221 <string name="nfc_ndef_push_sender">NDEF Push Sender</string> 1222 <string name="nfc_ndef_push_receiver">NDEF Push Receiver</string> 1223 <string name="nfc_llcp_version_check">LLCP version check</string> 1224 1225 <string name="nfc_tag_verification">Tag Verification</string> 1226 <string name="nfc_ndef">NDEF</string> 1227 <string name="nfc_mifare_ultralight">MIFARE Ultralight</string> 1228 1229 <string name="nfc_ndef_push_sender_info">Start the \"CTS Verifier NDEF Receiver\" test on 1230 another device and touch the devices back to back. The receiver should show a 1231 dialog indicating it has successfully received the correct message!</string> 1232 <string name="nfc_ndef_push_sender_instructions">Touch this device to the back of another 1233 device running the \"CTS Verifier NDEF Receiver\"...</string> 1234 1235 <string name="nfc_ndef_push_receiver_info">Start the \"CTS Verifier NDEF Sender\" test on 1236 another device and touch the devices back to back. The receiver should show a 1237 dialog indicating it has successfully received the correct message!</string> 1238 <string name="nfc_ndef_push_receiver_instructions">Touch this device to the back of another 1239 device running the \"CTS Verifier NDEF Sender\"...</string> 1240 <string name="nfc_ndef_push_receive_success">Successfully received the correct NDEF push 1241 message.</string> 1242 <string name="nfc_ndef_push_receive_failure">Failed to receive the correct NDEF push 1243 message.</string> 1244 1245 <string name="nfc_llcp_version_check_info">This test requires two candidate devices 1246 with NFC enabled to exchange P2P messages. Start the \"LLCP version check\" test on 1247 the other candidate device also, and touch the devices back to back. This test 1248 then verifies that the candidate device correctly advises the LLCP version as 1.2</string> 1249 <string name="nfc_llcp_version_check_failure">The candidate devices does not report LLCP 1250 version 1.2 or higher.</string> 1251 <string name="nfc_llcp_version_check_success">The candidate device has a valid LLCP version.</string> 1252 <string name="nfc_tag_verifier">NFC Tag Verifier</string> 1253 <string name="nfc_tag_verifier_info">Follow the on-screen instructions to write and read 1254 a tag of the chosen technology.</string> 1255 1256 <string name="nfc_scan_tag">Place device on a writable %s tag...</string> 1257 <string name="nfc_write_tag_title">Writable tag discovered!</string> 1258 <string name="nfc_write_tag_message">Press OK to write to this tag(or auto write to this tag after 3s)...</string> 1259 <string name="nfc_scan_tag_again">Tap the same %s tag again to confirm that its contents match...</string> 1260 <string name="nfc_wrong_tag_title">Wrong type of tag scanned</string> 1261 <string name="nfc_no_tech">No tag technologies detected...</string> 1262 1263 <string name="nfc_writing_tag">Writing NFC tag...</string> 1264 <string name="nfc_writing_tag_error">Error writing NFC tag...</string> 1265 <string name="nfc_reading_tag">Reading NFC tag...</string> 1266 <string name="nfc_reading_tag_error">Error reading NFC tag...</string> 1267 1268 <string name="nfc_result_message">Written data:\n%1$s\n\nRead data:\n%2$s</string> 1269 <string name="nfc_ndef_content">Id: %1$s\nMime: %2$s\nPayload: %3$s</string> 1270 1271 <string name="nfc_hce_f">Host-based Felica card emulation</string> 1272 <string name="nfc_hce_f_reader_tests">HCE Felica reader tests</string> 1273 <string name="nfc_hce_f_emulator_tests">HCE Felica emulator tests</string> 1274 <string name="nfc_hce_f_emulator">HCE Felica emulator</string> 1275 <string name="nfc_hce_f_reader">HCE Felica reader</string> 1276 <string name="nfc_hce_emulator_test_info">The host-based card emulation 1277 tests require two devices to be completed. The HCE emulator tests are used 1278 to actually test the host-based card emulation feature of the device-under-test. So the 1279 device running the emulator tests must be the candidate device running the software 1280 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 1281 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 1282 and makes sure the device-under-test implements card emulation correctly.</string> 1283 <string name="nfc_hce_reader_test_info">The host-based card emulation 1284 tests require two devices to be completed. The HCE emulator tests are used 1285 to actually test the host-based card emulation feature of the device-under-test. So the 1286 device running the emulator tests must be the candidate device running the software 1287 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 1288 in the "HCE reader tests" section. The "reader test" acts as a NFC terminal/POS 1289 and makes sure the device-under-test implements card emulation correctly. 1290 </string> 1291 1292 <string name="felicaservice">Felica Service</string> 1293 <string name="UiccTransactionEventService">Uicc Transaction Event Service</string> 1294 1295 <string name="nfc_offhost_uicc">Offhost UICC-based card emulation</string> 1296 <string name="nfc_offhost_uicc_emulator_tests">Offhost card emulation emulator tests</string> 1297 <string name="nfc_offhost_uicc_reader_tests">Offhost card emulation reader tests</string> 1298 <string name="nfc_offhost_uicc_transaction_event1_emulator">Offhost transaction event-field off (Emulator)</string> 1299 <string name="nfc_offhost_uicc_transaction_event1_reader">Offhost transaction event-field off (Reader)</string> 1300 <string name="nfc_offhost_uicc_transaction_event2_emulator">Offhost transaction event-deselect (Emulator)</string> 1301 <string name="nfc_offhost_uicc_transaction_event2_reader">Offhost transaction event-deselect (Reader)</string> 1302 <string name="nfc_offhost_uicc_transaction_event3_emulator">Offhost transaction event-HCI CMD (Emulator)</string> 1303 <string name="nfc_offhost_uicc_transaction_event3_reader">Offhost transaction event-HCI CMD (Reader)</string> 1304 1305 <string name="nfc_offhost_uicc_emulator_test_info">The offhost-based card emulation 1306 tests require two devices to be completed. The emulator tests are used 1307 to actually test the off-based card emulation feature of the device-under-test. So the 1308 device running the emulator tests must be the candidate device running the software 1309 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 1310 in the "Offhost reader tests" section. The "reader test" acts as a NFC terminal/POS 1311 and makes sure the device-under-test implements card emulation correctly 1312 </string> 1313 <string name="nfc_offhost_uicc_reader_test_info">The offhost-based card emulation 1314 tests require two devices to be completed. The emulator tests are used 1315 to actually test the off-based card emulation feature of the device-under-test. So the 1316 device running the emulator tests must be the candidate device running the software 1317 to be tested. \n\nFor each emulator test, there is a corresponding "reader test" 1318 in the "Offhost card emulation reader tests" section. The "reader test" acts as a NFC terminal/POS 1319 and makes sure the device-under-test implements card emulation correctly. 1320 </string> 1321 <string name="nfc_offhost_uicc_type_selection">By default Offhost card emulation applications run on type A. 1322 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> 1323 <string name="nfc_offhost_please_wait">Please wait</string> 1324 <string name="nfc_offhost_setting_up">Setting up card emulation services...</string> 1325 <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> 1326 1327 <!-- Strings for Sensor Test Activities --> 1328 <string name="snsr_device_admin_receiver">Sensor Tests Device Admin Receiver</string> 1329 <string name="snsr_test_summary">Tests passed: %1$d, Tests skipped: %2$d, Tests failed: %3$d</string> 1330 <string name="snsr_test_complete">Test completed without errors.</string> 1331 <string name="snsr_test_complete_with_errors">Test completed with errors which indicates 1332 the device does not meet Android compatibility requirement. 1333 This will degrade user experience and cause applications to misbehave. 1334 To help debugging, please take a bug report and back up contents under 1335 /sdcard/sensorTests of the device under test. 1336 </string> 1337 <string name="snsr_test_pass">PASS</string> 1338 <string name="snsr_test_skipped">SKIPPED</string> 1339 <string name="snsr_test_fail">FAIL</string> 1340 <string name="snsr_execution_time">Test execution time %1$s sec</string> 1341 <string name="snsr_rvcvxchk_test">Rotation Vector CV Crosscheck</string> 1342 <string name="snsr_rvcvxchk_test_rec">Rotation Vector CV Recording</string> 1343 1344 <!-- Strings to interact with users in Sensor Tests --> 1345 <string name="snsr_test_play_sound">A sound will be played once the verification is complete...</string> 1346 <string name="snsr_no_interaction">Leave the device on top of a flat surface.</string> 1347 <string name="snsr_interaction_needed">Once the test begins, you will have to wave your hand over the front of the device.</string> 1348 <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> 1349 <string name="snsr_device_steady">Keep the device steady.</string> 1350 <string name="snsr_keep_device_rotating_clockwise">Once the test begins, you will have to keep rotating the device clockwise.</string> 1351 <string name="snsr_wait_for_user">Press \'Next\' to continue.</string> 1352 <string name="snsr_wait_to_begin">Press \'Next\' to begin.</string> 1353 <string name="snsr_wait_to_retry">Press \'Retry\' to rerun or \'Fail and Next\' to skip to next.</string> 1354 <string name="snsr_wait_to_finish">Press \'Retry\' to rerun or \'Finish\' to end.</string> 1355 <string name="snsr_on_complete_return">After completing the task, go back to this test.</string> 1356 <string name="snsr_movement_expected">Movement was expected during the test. Found=%1$b.</string> 1357 <string name="snsr_sensor_feature_deactivation">IMPORTANT NOTE: Please also turn off any special features in the 1358 device that use sensors (wake up gestures, motion triggered events, moves, etc). 1359 Not doing so is expected to cause test failures. Once you are done, you can begin the test.</string> 1360 <string name="snsr_setting_mode_request">You will be redirected to set \'%1$s\' to: %2$s.</string> 1361 <string name="snsr_setting_mode_set">\'%1$s\' set to: %2$s.</string> 1362 <string name="snsr_setting_mode_not_set">\'%1$s\' not set to: %2$s.</string> 1363 <string name="snsr_setting_airplane_mode">Airplane mode</string> 1364 <string name="snsr_setting_screen_brightness_mode">Adaptive Brightness</string> 1365 <string name="snsr_setting_auto_rotate_screen_mode">Auto-rotate screen</string> 1366 <string name="snsr_setting_keep_screen_on">Stay awake</string> 1367 <string name="snsr_setting_location_mode">Location</string> 1368 <string name="snsr_setting_ambient_display">Ambient Display</string> 1369 <string name="snsr_pass_on_error">Pass Anyway</string> 1370 <string name="snsr_run_automated_tests">The screen will be turned off to execute the tests, 1371 when tests complete, the device will vibrate and the screen will be turned back on.</string> 1372 1373 <!-- Accelerometer --> 1374 <string name="snsr_accel_test">Accelerometer Test</string> 1375 <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> 1376 <string name="snsr_accel_m_test">Accelerometer Measurement Tests</string> 1377 <string name="snsr_accel_test_face_up">Place the device on a flat surface with the screen 1378 facing the ceiling.</string> 1379 <string name="snsr_accel_test_face_down">Place the device on a flat surface with the screen 1380 facing it.</string> 1381 <string name="snsr_accel_test_right_side">Place the device in a flat surface resting vertically 1382 on its right side.</string> 1383 <string name="snsr_accel_test_left_side">Place the device in a flat surface resting vertically 1384 on its left side.</string> 1385 <string name="snsr_accel_test_top_side">Place the device in a flat surface resting vertically 1386 on its top side.</string> 1387 <string name="snsr_accel_test_bottom_side">Place the device in a flat surface resting vertically 1388 on its bottom side.</string> 1389 1390 <!-- Gyroscope --> 1391 <string name="snsr_gyro_test">Gyroscope Test</string> 1392 <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> 1393 <string name="snsr_gyro_test_progress">Test %1$d of %2$d</string> 1394 <string name="snsr_gyro_test_no_gyro_title">No gyroscope?</string> 1395 <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> 1396 <string name="snsr_gyro_test_degrees_title">Wrong units?</string> 1397 <string name="snsr_gyro_test_degrees_message">These values looks like degrees per second. These should be radians per second!</string> 1398 <string name="snsr_gyro_m_test">Gyroscope Measurement Test</string> 1399 <string name="snsr_gyro_device_placement">Place the device in a flat surface with the screen 1400 facing the ceiling. Read the instructions for each scenario, before you perform the 1401 test.</string> 1402 <string name="snsr_gyro_device_static">Leave the device static.</string> 1403 <string name="snsr_gyro_rotate_device">Once you begin the test, you will need to rotate the 1404 device 360deg (one time) in the direction show by the animation, then place it back on the 1405 flat surface.</string> 1406 1407 <!-- Heart Rate --> 1408 <string name="snsr_heartrate_test">Heart Rate Test</string> 1409 <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> 1410 <string name="snsr_heartrate_test_no_heartrate_title">No heart rate monitor?</string> 1411 <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> 1412 1413 <!-- Hinge Angle --> 1414 <string name="snsr_hinge_angle_test">Hinge Angle Test</string> 1415 <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> 1416 <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. 1417 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> 1418 1419 <!-- Magnetic Field --> 1420 <string name="snsr_mag_m_test">Magnetic Field Measurement Tests</string> 1421 <string name="snsr_mag_verify_norm">Verifying the Norm...</string> 1422 <string name="snsr_mag_verify_offset">Verifying the Offset...</string> 1423 <string name="snsr_mag_verify_std_dev">Verifying the Standard Deviation...</string> 1424 <string name="snsr_mag_verify_calibrated_uncalibrated">Verifying the relationship between 1425 calibrated and uncalibrated measurements...</string> 1426 <string name="snsr_mag_calibration_description">Please calibrate the Magnetometer by moving 1427 it in 8 shapes in different orientations. Click \"Next\" to start and click \"Next\" once again to end calibration.</string> 1428 <string name="snsr_mag_calibration_complete">When done, leave the device in a flat surface, far 1429 from all metallic objects (if the test does not pass, try re-running it outdoors).</string> 1430 <string name="snsr_mag_measurement">-> (%1$.2f, %2$.2f, %3$.2f) : %4$.2f uT</string> 1431 <string name="snsr_mag_move_outside">Unable to acquire location. Please move outside to allow a location fix.</string> 1432 <string name="snsr_mag_no_location">Failed to acquire location. Using default magnetic field of %1$.2f uT.</string> 1433 1434 <!-- Sensor Value Accuracy --> 1435 <string name="snsr_rot_vec_test">Rotation Vector Accuracy Test</string> 1436 <string name="snsr_event_length">Sensor(%3$s). Event values expected to have size=%1$d. Found=%2$d.</string> 1437 <string name="snsr_event_value">Sensor(%3$s). Event value[0] expected to be of value=%1$f. Found=%2$f.</string> 1438 <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> 1439 1440 <!-- Sensor Batching --> 1441 <string name="snsr_batch_test">Sensor Batching Manual Tests</string> 1442 <string name="snsr_batching_walking_needed">Once the test begins, you will have to take the 1443 device in your hand and walk.</string> 1444 1445 <!-- Sensor Synchronization --> 1446 <string name="snsr_synch_test">Sensor Synchronization Test</string> 1447 1448 <!-- Step Counter and Detector --> 1449 <string name="snsr_step_counter_test">Step Counter and Detector Tests</string> 1450 <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> 1451 <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> 1452 <string name="snsr_step_counter_expected_steps">At least %1$d steps are expected to be reported. Reported=%2$d.</string> 1453 <string name="snsr_step_counter_detected_reported">Steps reported by user=%1$d. Steps counted=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 1454 <string name="snsr_step_detector_detected_reported">Steps reported by user=%1$d. Steps detected=%2$d. Delta=%3$d. Tolerance=%4$d.</string> 1455 <string name="snsr_step_counter_event_changed">Step counter expected to increase monotonically, with a delta > 0. Found=%1$d. Timestamp=%2$d.</string> 1456 <string name="snsr_step_reported">%1$d | User reported step.</string> 1457 <string name="snsr_step_counter_event">%1$d | Step Counter event. count=%2$d.</string> 1458 <string name="snsr_step_detector_event">%1$d | Step Detector event.</string> 1459 1460 <!-- Step Counter and Detector Permission --> 1461 <string name="snsr_step_permission_test">Step Permission Test</string> 1462 <string name="snsr_step_permission_disable">Please change the \'Physical Activity\' permission for CtsVerifier to \'Deny\'</string> 1463 <string name="snsr_step_permission_enable">Please change the \'Physical Activity\' permission for CtsVerifier to \'Allow\'</string> 1464 <string name="snsr_step_permission_walk">Please begin walking while holding the device. A sound will play when you may stop walking</string> 1465 1466 <!-- Device suspend tests --> 1467 <string name="snsr_device_suspend_test">Device Suspend Tests</string> 1468 <string name="snsr_device_did_not_go_into_suspend">Device did not go into suspend mode during test execution </string> 1469 <string name="snsr_batch_did_not_arrive_at_expected_time">Batch did not arrive at the expected time estimatedBatchArrivalMs=%1$d 1470 firstEventReceivedMs=%2$d diffMs=%3$d toleranceMs=%4$d </string> 1471 <string name="snsr_device_suspend_test_instr">One you begin the test, disconnect USB, turn off the display and allow 1472 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> 1473 <string name="snsr_device_suspend_service">Device Suspend Service</string> 1474 <string name="snsr_device_suspend_service_active">Device Suspend Test Active</string> 1475 <string name="snsr_device_suspend_service_notification">Device Suspend Test is using sensors.</string> 1476 1477 <!-- Significant Motion --> 1478 <string name="snsr_significant_motion_test">Significant Motion Tests</string> 1479 <string name="snsr_significant_motion_event_arrival">Event expected to trigger. Triggered=%1$s.</string> 1480 <string name="snsr_significant_motion_event_type">Event expected to be of type=%1$d. Found=%2$d.</string> 1481 <string name="snsr_significant_motion_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string> 1482 <string name="snsr_significant_motion_disable_info">Significant Motion is expected to disable itself after it triggers once.</string> 1483 <string name="snsr_significant_motion_test_trigger">Once you begin the test, you will need to walk for Significant Motion to be detected.</string> 1484 <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> 1485 <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> 1486 <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> 1487 <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> 1488 <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> 1489 <string name="snsr_significant_motion_registration">Expected to be able to register for TriggerSensor. Found=%1$b.</string> 1490 <string name="snsr_significant_motion_cancelation">Expected to be able to cancel TriggerSensor. Found=%b.</string> 1491 <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. 1492 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> 1493 <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> 1494 1495 <!-- Event sanitization for idle UIDs --> 1496 <string name="snsr_event_sanitization_test">Event sanitization for idle UID test</string> 1497 <string name="snsr_event_sanitization_test_setup">Run the \'adb shell cmd sensorservice set-uid-state com.android.cts.verifier idle\' shell command 1498 to emulate the CtsVerifier UID being idle.</string> 1499 <string name="snsr_event_sanitization_test_cleanup">Run the \'adb shell cmd sensorservice reset-uid-state com.android.cts.verifier\' shell command 1500 to stop emulating the CtsVerifier UID being idle. Failing to do that would lead to other tests failing!</string> 1501 <string name="snsr_significant_motion_test_uid_idle">Move around with the device to try triggering significant motion</string> 1502 <string name="snsr_significant_motion_test_uid_idle_expectation">No trigger events should be generated while idle</string> 1503 <string name="snsr_proximity_test_uid_idle">Touch the proximity sensor to try triggering it</string> 1504 <string name="snsr_proximity_test_uid_idle_expectation">No on-change events should be generated while idle</string> 1505 1506 <!-- Low Latency Off-Body Detect --> 1507 <string name="snsr_offbody_sensor_test">Off Body Sensor Tests</string> 1508 <string name="snsr_offbody_sensor_registration">Registration failed for low latency offbody detect sensor.\n</string> 1509 <string name="snsr_offbody_event_arrival">Expected to receive a low latency offbody detect event. Found=%b.</string> 1510 <string name="snsr_offbody_event_type">Event expected to be of type=%1$d. Found=%2$d.</string> 1511 <string name="snsr_offbody_event_invalid_value">Invalid value received for offbody state; Expected value %1$d or %2$d. Found=%2$d.</string> 1512 <string name="snsr_offbody_event_wrong_value">Expected to receive an event having value=%1$d. Found=%2$d.</string> 1513 <string name="snsr_offbody_event_unexpected">Event not expected to trigger. Triggered=%1$s.</string> 1514 <string name="snsr_offbody_response_timing_violation">%1$s event maximum allowed latency is %2$d. Found=%3$d ms.</string> 1515 <string name="snsr_offbody_state_change">Offbody state changed to %1$d. Timestamp=%2$d.</string> 1516 <string name="snsr_start_offbody_sensor_test_instr">Put watch on your wrist and then click Next button.</string> 1517 <string name="snsr_start_onbody_sensor_test_instr">Remove the watch from your wrist and then click Next button.</string> 1518 <string name="snsr_offbody_detect_test_instr">Click Next button, then immediate remove the watch from your wrist after the countdown reaches 0.</string> 1519 <string name="snsr_offbody_detect_test_countdown">Countdown: %1$d.</string> 1520 <string name="snsr_onbody_detect_test_instr">Click Next button, then immediately attach the watch on your wrist.</string> 1521 <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> 1522 1523 <!-- Strings for Sensor CTS tests inside CtsVerifier --> 1524 <string name="snsr_single_sensor_tests">CTS Single Sensor Tests</string> 1525 <string name="snsr_sensor_integration_tests">CTS Sensor Integration Tests</string> 1526 <string name="snsr_sensor_test">CTS Sensor Test</string> 1527 <string name="snsr_sensor_batching_tests">CTS Sensor Batching Tests</string> 1528 1529 <!-- String for DynamicSensorDiscoveryTest --> 1530 <string name="snsr_dynamic_sensor_discovery_test">Dynamic Sensor Discovery Test</string> 1531 1532 <!-- Strings for Sample Test Activities --> 1533 <string name="share_button_text">Share</string> 1534 <string name="sample_framework_test">Sample Framework Test</string> 1535 <string name="sample_test">Sample Test</string> 1536 <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> 1537 1538 <!-- Strings for Camera Orientation --> 1539 <string name="camera_orientation">Camera Orientation</string> 1540 <string name="co_info">This test verifies the orientation capabilities of 1541 camera preview and capture.\n - The left view shows a preview window rotated 1542 by a given magnitude of degrees.\n - The right view, after taking 1543 a photo, shows the captured image.\n - For each camera and orientation, both 1544 the left and right views should appear rotated by the amount of 1545 degrees specified. Choose \"Pass\" if this is the case. Otherwise, choose 1546 \"Fail\".\n - For front-facing cameras, the test will horizontally mirror 1547 the captured image prior to rotation, in attempt to make the left and right 1548 views appear the same.\n - The physical orientation of the device does not 1549 matter.\n - Read the message above the \"Take Photo\" button for 1550 step-by-step instructions. 1551 </string> 1552 <string name="co_preview_label">Camera preview</string> 1553 <string name="co_format_label">Oriented photo</string> 1554 <string name="co_camera_label">Camera:</string> 1555 <string name="co_orientation_label">Orientation</string> 1556 <string name="co_instruction_heading_label">Instruction:</string> 1557 <string name="co_instruction_text_photo_label">Take a photo</string> 1558 <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> 1559 <string name="co_instruction_text_extra_label">(mirrored horizontally prior to rotation, since camera is front-facing)</string> 1560 <string name="co_photo_button_caption">Take Photo</string> 1561 1562 <!-- Strings for Camera Intents --> 1563 <string name="camera_intents">Camera Intents</string> 1564 <string name="ci_info"> 1565 This test verifies that the default camera app is firing intents 1566 after pictures/videos are taken. It also verifies that when the 1567 default camera app is invoked via intents, the launch intents work, 1568 ,broadcast intents are received when appropriate per the SDK 1569 documentation and also, that the intent results do not have location 1570 information in them. Before starting with the tests, please go to the 1571 Settings app and deny location permissions to the CtsVerifier app, and 1572 after finishing with the camera intent tests, please go to the Settings app and 1573 restore location permissions, otherwise, other tests may fail.\n\n 1574 - Read the message above the \"Start Test\" button for 1575 step-by-step instructions. 1576 </string> 1577 <string name="ci_preview_label">Camera preview</string> 1578 <string name="ci_format_label">Oriented photo</string> 1579 <string name="ci_camera_label">Camera:</string> 1580 <string name="ci_intents_label">Intents Test</string> 1581 <string name="ci_intents_direction_label">clockwise</string> 1582 <string name="ci_instruction_heading_label">Instructions:</string> 1583 <string name="ci_location_permissions_error">Please give CTS Verifier location permissions before clicking on the pass / fail button</string> 1584 <string name="ci_location_permissions_fail_error">Please give CTS Verifier location permissions if the fail button needs to be clicked</string> 1585 <string name="ci_directory_creation_error">CTS Verifier debug directory could not be created, please try again</string> 1586 <string name="ci_instruction_text_photo_label">READ BEFORE STARTING TEST</string> 1587 <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> 1588 <string name="ci_instruction_text_app_picture_label">\n 1589 1590 1. Click Open Settings and deny location permissions to CTS Verifier and return. \n 1591 2. Click Start Test. \n 1592 3. Go to home screen (HOME key). \n 1593 4. Launch Camera application. \n 1594 5. Capture photo within 1 minute. \n 1595 6. Return to CTS verifier app. \n 1596 7. Pass button will light up if intent and URI triggers were fired.\n 1597 8. Click "Pass" if possible, otherwise open settings app, allow location again and click "Fail". 1598 </string> 1599 <string name="ci_instruction_text_app_video_label">\n 1600 1. Click Start Test. \n 1601 2. Go to home screen (HOME key). \n 1602 3. Launch Camera application. \n 1603 4. Capture video within 1 minute. \n 1604 5. Return to CTS verifier app. \n 1605 6. Pass button will light up if intent and URI triggers were fired.\n 1606 7. Click "Pass" if possible, otherwise open settings app, allow location again and click "Fail". 1607 </string> 1608 <string name="ci_instruction_text_intent_picture_label">\n 1609 1. Click Start Test.\n 1610 2. Camera app will launch, prompting to take photo.\n 1611 3. Capture/confirm photo using camera app controls within 1 minute.\n 1612 4. Pass button will light up if intent and URI trigger were NOT received.\n 1613 5. Click "Pass" if possible, otherwise open settings app, allow location again and click "Fail". 1614 </string> 1615 <string name="ci_instruction_text_intent_picture_secure_label">\n 1616 1. Click Start Test.\n 1617 2. Camera app will launch, prompting to take photo.\n 1618 3. Capture/confirm photo using camera app controls within 1 minute.\n 1619 4. Pass button will light up if intent and URI trigger were NOT received.\n 1620 5. Click "Pass" if possible, otherwise open settings app, allow location again and click "Fail". 1621 </string> 1622 <string name="ci_instruction_text_intent_video_label">\n 1623 1. Click Start Test.\n 1624 2. Camera app will launch, prompting to take video.\n 1625 3. Capture/confirm video using camera app controls within 1 minute.\n 1626 4. Return to the CTS Verifier app. Click Open Settings and give back CTS Verifier location permissions \n 1627 (Note this must be done before clicking on Pass / Fail).\n 1628 5. Click "Pass" if possible. 1629 </string> 1630 <string name="ci_start_test_button_caption">Start Test</string> 1631 <string name="ci_settings_button_caption">Open Settings</string> 1632 1633 <!-- Strings for Camera Formats --> 1634 <string name="camera_format">Camera Formats</string> 1635 <string name="cf_info">This test checks that all the supported 1636 output formats for camera preview callbacks work correctly, and 1637 that the mandatory formats are available. \n - The left view shows 1638 a standard preview window. \n - The right view shows the output 1639 processed from camera preview callbacks. \n - For each camera, 1640 resolution, and format combination in the dropdowns, the right 1641 view should look the same as the left, and neither should have 1642 streaks, lines, or other artifacts. \n - For front-facing cameras, 1643 the right view must be horizontally mirrored relative to the left 1644 view.\n - Note that the frame rate of the right view may be much 1645 lower than on the left; this is not an indication of a failed 1646 test.\n - The next button triggers the next resolution and format 1647 combination of the current camera to show; this is optional. 1648 </string> 1649 <string name="cf_preview_label">Normal preview</string> 1650 <string name="cf_format_label">Processed callback data</string> 1651 1652 <!-- Strings for Camera Video --> 1653 <string name="record_button_text">Test</string> 1654 <string name="camera_video">Camera Video</string> 1655 <string name="video_info"> This test checks video capture 1656 at different resolutions. \n - The left view window shows the preview. 1657 \n - Pressing the test button will trigger three 1658 seconds of video recording. Playback will show up in the right view 1659 window after recording is complete. \n - Use the spinners to choose 1660 camera and resolution combinations. The playback should be similar 1661 to what you saw in preview. \n - The next button triggers test for the next 1662 untested resolution of the currently selected camera. - After all possible 1663 combinations are tested, the pass button will be enabled. You may press the 1664 pass button to indicate a pass. \n - You may press fail button any time 1665 during the test to indicate failure. \n 1666 </string> 1667 <string name="video_capture_label">Video capture</string> 1668 <string name="video_playback_label">Video playback</string> 1669 <string name="dialog_fail_test">Test failed</string> 1670 <string name="fail_quit">Fail and quit</string> 1671 <string name="cancel">Cancel</string> 1672 <string name="status_ready">Ready</string> 1673 <string name="status_recording">Recording</string> 1674 <string name="status_playback">Playing back</string> 1675 1676 <!-- Strings for USB accessory test activity --> 1677 <string name="usb_accessory_test">USB Accessory Test</string> 1678 <string name="usb_accessory_test_info"> 1679 1. Install the Cts Verifier USB Companion app on a separate helper device. 1680 \n\n2. Start the accessory test companion in the Cts Verifier USB Companion. 1681 \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". 1682 \n\n4. Confirm access to the USB device on the helper device. 1683 \n\n5. Confirm access to the USB accessory on this device 1684 \n\n6. Confirm access to the USB device on the helper again. 1685 \n\n7. Test will run and complete automatically in less than 30 seconds. 1686 \n\n8. Cancel all further dialogs on this device 1687 </string> 1688 <string name="usb_accessory_test_step1"> 1689 In this specific order: 1690 \n1. Install the Cts Verifier USB Companion app on a separate helper device. 1691 \n2. Start the accessory test companion in the Cts Verifier USB Companion. 1692 \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". 1693 \n4. Confirm access to the USB device on the helper device. Only confirm once. 1694 \n5. Confirm access to the USB accessory on this device. 1695 \n6. Confirm access to the USB device on the helper device again. 1696 \n\nResult: A progress indicator should appear or test will finish. 1697 </string> 1698 <string name="usb_accessory_test_step2"> 1699 Test is running and will complete automatically in less than 30 seconds. 1700 </string> 1701 1702 <!-- String for the USB device test activity --> 1703 <string name="usb_device_test">USB Device Test</string> 1704 <string name="usb_device_test_info"> 1705 1. Install the Cts Verifier USB Companion app on a separate helper device. 1706 \n\n2. Start the device test companion in the Cts Verifier USB Companion. 1707 \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". 1708 \n\n4. Confirm access to the USB device on this device. Do <u>not</u> make this app the default app for the device. 1709 \n\n5. Confirm access to the USB accessory on the helper device. 1710 \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. 1711 \n\n7. Test will run and complete automatically in less than 30 seconds. 1712 \n\n8. Cancel all further dialogs on the helper device. 1713 </string> 1714 <string name="usb_device_test_step1"> 1715 In this specific order: 1716 \n1. Install the Cts Verifier USB Companion app on a separate helper device. 1717 \n2. Start the device test companion in the Cts Verifier USB Companion. 1718 \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". 1719 \n\nResult: A dialog should show up on this device asking for access to a USB device. 1720 </string> 1721 <string name="usb_device_test_step2"> 1722 Confirm access to the USB device on this device. Do <u>not</u> make this app the default app for the device. 1723 \n\nResult: Dialogs should show up on this device and on the helper device asking for access to a USB device/accessory. 1724 </string> 1725 <string name="usb_device_test_step3"> 1726 1. Confirm access to the USB accessory on the helper device. 1727 \n2. Confirm access to the USB device on this device again. Do <u>not</u> make this app the default app for the device. 1728 \n\nResult: A progress indicator should appear or test will finish. 1729 </string> 1730 <string name="usb_device_test_step4"> 1731 Test is running and will complete automatically in a less than 30 seconds. 1732 </string> 1733 <string name="usb_device_unexpected">Usb companion device is not as expected %1$s. Please retry test.</string> 1734 1735 <!-- Strings for MTP host test activity --> 1736 <string name="mtp_host_test">MTP Host Test</string> 1737 <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> 1738 <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> 1739 <string name="mtp_host_grant_permission_message">Grant permission.\nReply a dialog asking device permission.</string> 1740 <string name="mtp_host_test_read_event_message">Test MtpDevice#readEvent.\nTake a picture at the connected device.</string> 1741 <string name="mtp_host_test_send_object_message">Test MtpDevice#sendObject.</string> 1742 <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> 1743 <string name="mtp_app_settings">App Settings</string> 1744 1745 <!-- Strings for the Camera ITS test activity --> 1746 <string name="camera_its_test">Camera ITS Test</string> 1747 <string name="camera_its_test_info"> 1748 1. Connect your Android device to a computer with adb installed via a USB cable. 1749 \n\n2. Setup the CameraITS test environment by following the setup instructions in the 1750 README file found in the CameraITS directory included in the CTS Verifier bundle 1751 (cd CameraITS; source build/envsetup.sh;). 1752 \n\n3. Setup the test scene described in the CameraITS README file, and aim the camera 1753 at it. 1754 \n\n4. Run the full ITS test suite on all possible camera Ids. 1755 (cd CameraITS; python tools/run_all_tests.py). Once all 1756 of the tests have been run, the \'PASS\' button will be enabled if all of the tests have 1757 succeeded. Please note that these tests can take more than 2 hours to run on some devices. 1758 </string> 1759 <string name="no_camera_manager"> 1760 No camera manager exists! This test device is in a bad state. 1761 </string> 1762 <string name="all_exempted_devices"> 1763 All cameras on this device are exempted from ITS - Pass. 1764 </string> 1765 <string name="its_test_passed">All Camera ITS tests passed. Pass button enabled!</string> 1766 <string name="its_test_failed">Some Camera ITS tests failed.</string> 1767 <string name="its_version_mismatch"> 1768 CtsVerifier and ITS script version mismatch. Please update CtsVerifier and ITS script. 1769 </string> 1770 <string name="its_test_progress">ITS test progress will be shown here.</string> 1771 1772 <!-- Strings for the Camera Webcam test activity --> 1773 <string name="camera_webcam_test">Camera Webcam Test</string> 1774 <string name="camera_webcam_test_info"> 1775 This test verifies the FPS rates the device advertises as a webcam. It also 1776 includes manual verification on the functionality of the webcam stream. 1777 1778 \n\nInstructions for Test Run: 1779 \n1. Connect your Android device to a computer with adb installed via a USB cable. 1780 \n\n2. Setup the Camera Webcam test environment by following the setup instructions in the 1781 README file found in the DeviceAsWebcam directory 1782 (packages/services/DeviceAsWebcam/tests). 1783 1784 \n\n3. Ensure the camera is aimed at a bright scene to get the most accurate FPS reading. 1785 \n\n4. Run the test script. 1786 (python run_webcam_test.py -c config.yml). 1787 Once the test has been run, the \'Yes\' and \'No\' buttons will be enabled. Confirm if the frames 1788 from the webcam service were okay. Then, click \'Done\'. The \'PASS\' will be enabled 1789 if the script results passed and the frames contained no issues. 1790 </string> 1791 1792 <string name="camera_webcam_frames_pass">Yes</string> 1793 <string name="camera_webcam_frames_fail">No</string> 1794 <string name="camera_webcam_done_button">Done</string> 1795 <string name="camera_webcam_start_text">Run the test script to begin.</string> 1796 <string name="camera_webcam_confirm_frames_text">Webcam testing complete. Confirm if the frames from webcam stream were okay.</string> 1797 <string name="camera_webcam_results_pass_frames_fail_text">Script results passed but frames contained errors. Test failed. Click Done to complete.</string> 1798 <string name="camera_webcam_results_pass_frames_pass_text">Script results passed and frames were normal. Test passed Click Done to complete.</string> 1799 <string name="camera_webcam_results_fail_frames_pass_text">Script results failed but frames were normal. Test failed. Click Done to complete.</string> 1800 <string name="camera_webcam_results_fail_frames_fail_text">Script results failed and frames contained errors. Test failed. Click Done to complete.</string> 1801 <string name="camera_webcam_not_supported_text">Webcam feature not supported. Test skipped. Click Done to complete.</string> 1802 1803 <!-- Strings for the Camera Flashlight test activity --> 1804 <string name="camera_flashlight_test">Camera Flashlight</string> 1805 <string name="camera_flashlight_info"> 1806 This test checks the flashlight functionality. It will turn on and off the flashlight of 1807 each camera device that has a flash unit. Follow the instructions on screen and observe the 1808 flashlight status changing. 1809 </string> 1810 <string name="camera_flashlight_start_button">Start</string> 1811 <string name="camera_flashlight_next_button">Next</string> 1812 <string name="camera_flashlight_done_button">Done</string> 1813 <string name="camera_flashlight_on_button">On</string> 1814 <string name="camera_flashlight_off_button">Off</string> 1815 <string name="camera_flashlight_start_text">Press Start to start flashlight test.</string> 1816 <string name="camera_flashlight_question_text">Is Camera %1$s flashlight on or off?</string> 1817 <string name="camera_flashlight_next_text">Ok. Press next.</string> 1818 <string name="camera_flashlight_failed_text">Test failed. Press Done or Fail button.</string> 1819 <string name="camera_flashlight_passed_text">All tests passed. Press Done or Pass button. 1820 </string> 1821 1822 <!-- Strings for the Camera Performance test activity --> 1823 <string name="camera_performance_test">Camera Performance</string> 1824 <string name="camera_performance_test_info"> 1825 This activity will run performance test cases. For optimal and consistent results please 1826 make sure that all camera sensors are pointing in a direction with sufficiently bright 1827 light source. 1828 </string> 1829 <string name="camera_performance_spinner_text">Running CTS performance test case...</string> 1830 <string name="camera_performance_result_title">Test Result</string> 1831 1832 <!-- Strings for StreamingVideoActivity --> 1833 <string name="streaming_video">Streaming Video Quality Verifier</string> 1834 <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> 1835 <string name="sv_no_data">No videos.</string> 1836 <string name="sv_failed_title">Test Failed</string> 1837 <string name="sv_failed_message">Unable to play stream. See log for details.</string> 1838 1839 <!-- Strings for MediaCodecFlushActivity --> 1840 <string name="media_codec_flush">Video codec flushing in Tunnel Mode</string> 1841 1842 <!-- Strings for VolumeLevelChangesActivity --> 1843 <string name="volume_level_changes">Volume level changes</string> 1844 <string name="volume_level_changes_title">This test is for verifying that the Volume level 1845 changes are reflected when playback occurs with and without tunnel mode playback for 1846 PCM audio.</string> 1847 <string name="increase_volume_level"> Increase the volume until you can clearly recognize the 1848 audio, and then press OK button.</string> 1849 <string name="ok_button_volume_level">OK</string> 1850 <string name="decrease_volume_level"> Decrease the volume until you can no longer recognize the 1851 audio, and then press OK button.</string> 1852 <string name="yes_button_volume_level">Yes</string> 1853 <string name="no_button_volume_level">No</string> 1854 <string name="is_same_volume"> "Is the volume still the same as what you had set?"</string> 1855 <string name="volume_level_changes_failure_tunnel_to_non_tunnel"> 1856 "The volume change was not maintained when switching from tunnel mode to non-tunnel mode." 1857 </string> 1858 <string name="volume_level_changes_failure_non_tunnel_to_tunnel"> 1859 "The volume change was not maintained when switching from non-tunnel mode to tunnel mode." 1860 </string> 1861 1862 <!-- Strings for the Camera Bokeh mode test activity --> 1863 <string name="camera_bokeh_test">Camera Bokeh</string> 1864 <string name="camera_bokeh_test_info"> 1865 This test checks camera bokeh mode functionality. It enumerates supported bokeh modes, and 1866 makes sure each non-OFF bokeh mode works correctly. For optimal and consistent results, 1867 please make sure the camera device is pointing to a well-lit scene with a human face in 1868 the center at least 1 meter away, and the rest of the scene is further away in the 1869 background. 1870 </string> 1871 <string name="camera_bokeh_no_support"> 1872 None of the camera devices support bokeh modes. Please click the Test Passed button. 1873 </string> 1874 1875 <!-- Strings for TestListActivity --> 1876 <string name="wifi_test">Wi-Fi Test</string> 1877 <string name="wifi_test_info"> 1878 The Wi-Fi tests requires an open or PSK access point in the environment along with the DUT. 1879 \nPlease perform a network settings reset between each test to reset platform\'s internal state which 1880 might interfere with the test flow.\nNavigate to \"Settings -> System -> Reset Options -> Reset Bluetooth 1881 & Wi-Fi\" to perform a network settings reset. 1882 </string> 1883 <string name="wifi_location_not_enabled">Wi-Fi / Location Mode is not enabled</string> 1884 <string name="wifi_location_not_enabled_message">These tests require Wi-Fi and Location Mode to be enabled. 1885 Click the button below to go to system settings and enable Wi-Fi and Location Mode.</string> 1886 <string name="wifi_settings">Wi-Fi Settings</string> 1887 <string name="location_settings">Location Settings</string> 1888 <string name="wifi_setup_error">Test failed with set up error.</string> 1889 <string name="wifi_unexpected_error">Test failed with unexpected error. Check logcat.</string> 1890 1891 <string name="wifi_ssid_label">SSID for network</string> 1892 <string name="wifi_psk_label">Passphrase for network (leave empty for open network)</string> 1893 <string name="wifi_start_test_label">Start test</string> 1894 1895 <string name="wifi_status_need_psk">Need a psk network for this test.</string> 1896 <string name="wifi_status_initiating_scan">Initiating scan.</string> 1897 <string name="wifi_status_scan_failure">Unable to initiate scan or find matching network in scan results.</string> 1898 <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> 1899 <string name="wifi_status_initiating_network_request">Initiating network request.</string> 1900 <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> 1901 <string name="wifi_status_network_available">"Connected to network."</string> 1902 <string name="wifi_status_network_available_error">Connected to network unexpectedly.</string> 1903 <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> 1904 <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> 1905 <string name="wifi_status_network_unavailable">"Did not connect to any network."</string> 1906 <string name="wifi_status_network_wait_for_lost">Ensuring device does not disconnect from the network until the request is released.</string> 1907 <string name="wifi_status_network_lost">Disconnected from the network.</string> 1908 <string name="wifi_status_network_cb_timeout">Network callback timed out.</string> 1909 1910 <string name="wifi_status_suggestion_add">Adding suggestions to the device.</string> 1911 <string name="wifi_status_suggestion_add_failure">Failed to add suggestions.</string> 1912 <string name="wifi_status_suggestion_get_failure">Failed to get suggestions.</string> 1913 <string name="wifi_status_suggestion_remove">Removing suggestions from the device.</string> 1914 <string name="wifi_status_suggestion_remove_failure">Failed to remove suggestions.</string> 1915 <string name="wifi_status_suggestion_wait_for_connect">Waiting for network connection.</string> 1916 <string name="wifi_status_suggestion_ensure_no_connect">Ensuring no network connection.</string> 1917 <string name="wifi_status_suggestion_connect">Connected to the network.</string> 1918 <string name="wifi_status_suggestion_not_connected">Did not connect to the network.</string> 1919 <string name="wifi_status_suggestion_wait_for_post_connect_bcast">Waiting for post connection broadcast.</string> 1920 <string name="wifi_status_suggestion_post_connect_bcast">Received post connection broadcast.</string> 1921 <string name="wifi_status_suggestion_post_connect_bcast_failure">Failed to receive post connection broadcast.</string> 1922 <string name="wifi_status_suggestion_wait_for_connection_status">Waiting for connection status.</string> 1923 <string name="wifi_status_suggestion_connection_status">Received connection status.</string> 1924 <string name="wifi_status_suggestion_connection_status_failure">Failed to receive connection status.</string> 1925 <string name="wifi_status_suggestion_wait_for_disconnect">Ensuring device does disconnect from the network after removing suggestions.</string> 1926 <string name="wifi_status_suggestion_metered_change">Marking the network metered.</string> 1927 <string name="wifi_status_suggestion_metered_check_failed">Network meteredness check failed.</string> 1928 <string name="wifi_status_suggestion_metered_changed">Network marked metered successfully.</string> 1929 <string name="wifi_status_suggestion_capabilities_not_changed">Network capabilities did not change.</string> 1930 <string name="wifi_status_suggestion_not_disconnected">Did not disconnect from the network.</string> 1931 <string name="wifi_status_suggestion_disconnected">Disconnected from the network.</string> 1932 <string name="wifi_status_suggestion_add_user_approval_status_listener_failure">Failed to add user approval status listener</string> 1933 <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> 1934 <string name="wifi_status_suggestion_user_approval_status_failure">Failed to receive user approval status change</string> 1935 <string name="wifi_status_suggestion_user_approve_failure">Failed to get user approval</string> 1936 1937 <string name="wifi_status_test_success">Test completed successfully!</string> 1938 <string name="wifi_status_test_failed">Test failed!</string> 1939 1940 <string name="wifi_test_network_request">Network Request tests</string> 1941 <string name="wifi_test_network_request_specific">Network Request with a specific SSID and BSSID.</string> 1942 <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> 1943 <string name="wifi_test_network_request_pattern">Network Request with a SSID and BSSID pattern.</string> 1944 <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> 1945 <string name="wifi_test_network_request_unavailable">Network Request with a specific network that is unavailable.</string> 1946 <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> 1947 <string name="wifi_test_network_request_invalid_credential">Network Request with a specific network with wrong credential.</string> 1948 <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> 1949 1950 <string name="wifi_test_network_suggestion">Network Suggestion tests</string> 1951 <string name="wifi_test_network_suggestion_ssid">Network suggestion with SSID.</string> 1952 <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> 1953 <string name="wifi_test_network_suggestion_ssid_bssid">Network suggestion with SSID and BSSID.</string> 1954 <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> 1955 <string name="wifi_test_network_suggestion_ssid_post_connect">Network suggestion with SSID and post connection broadcast.</string> 1956 <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> 1957 <string name="wifi_test_network_suggestion_connection_failure">Network suggestion connection failure.</string> 1958 <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> 1959 <string name="wifi_test_network_suggestion_modification_in_place">Network suggestion modification in place.</string> 1960 <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> 1961 1962 <!-- Strings for P2pTestActivity --> 1963 <string name="p2p_test">Wi-Fi Direct Test</string> 1964 <string name="p2p_test_info"> 1965 The Wi-Fi Direct tests require two devices with Wi-Fi Direct enabled to exchange 1966 messages. One device must be the candidate device running the software build to 1967 be tested, while the other device must be an implementation already known to be 1968 compatible.\n\nOne device should start the requester test, and the other should 1969 start the responder test. Your device must pass both requester and responder 1970 tests. 1971 </string> 1972 <string name="p2p_group_formation">Group Formation</string> 1973 <string name="p2p_join">Group Join</string> 1974 <string name="p2p_service_discovery">Service Discovery</string> 1975 1976 <string name="p2p_go_neg_responder_test">GO Negotiation Responder Test</string> 1977 <string name="p2p_go_neg_requester_test">GO Negotiation Requester Test</string> 1978 <string name="p2p_group_owner_test">Group Owner Test</string> 1979 <string name="p2p_join_with_config">Group Join with Config</string> 1980 <string name="p2p_join_with_config_2g_band">Group Join with Config 2G Band</string> 1981 <string name="p2p_join_with_config_fixed_frequency"> 1982 Group Join with Config Fixed Frequency</string> 1983 <string name="p2p_group_owner_with_config_test">Group Owner With Config Test</string> 1984 <string name="p2p_group_owner_with_config_2g_band_test"> 1985 Group Owner With Config 2G Band Test</string> 1986 <string name="p2p_group_owner_with_config_fixed_frequency_test"> 1987 Group Owner With Config Fixed Frequency Test</string> 1988 <string name="p2p_group_client_test">Group Client Test</string> 1989 <string name="p2p_group_client_with_config_test">Group Client With Config Test</string> 1990 <string name="p2p_group_client_with_config_2g_band_test"> 1991 Group Client With Config 2G Band Test</string> 1992 <string name="p2p_group_client_with_config_fixed_frequency_test"> 1993 Group Client With Config Fixed Frequency Test</string> 1994 <string name="p2p_service_discovery_responder_test"> 1995 Service Discovery Responder Test</string> 1996 <string name="p2p_service_discovery_requester_test"> 1997 Service Discovery Requester Test</string> 1998 1999 <string name="p2p_go_neg_responder">GO Negotiation Responder</string> 2000 <string name="p2p_go_neg_requester">GO Negotiation Requester</string> 2001 <string name="p2p_accept_client">Group Owner</string> 2002 <string name="p2p_join_go">Group Client</string> 2003 <string name="p2p_service_discovery_responder">Service Discovery Responder</string> 2004 <string name="p2p_service_discovery_requester">Service Discovery Requester</string> 2005 2006 <string name="p2p_go_neg_responder_info"> 2007 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2008 Wi-Fi settings and forget all remembered networks. Then start the \"GO Negotiation 2009 Requester Test\" on the other device and follow 2010 the instructions.</string> 2011 <string name="p2p_accept_client_info"> 2012 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2013 Wi-Fi settings and forget all remembered networks. Then start the \"Group Client Test\" on 2014 the other device and follow 2015 the instructions.</string> 2016 <string name="p2p_service_discovery_responder_info"> 2017 Start the \"Service Discovery Requester Test\" on the other device and follow 2018 the instructions.</string> 2019 2020 <string name="p2p_go_neg_requester_info"> 2021 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2022 Wi-Fi settings and forget all remembered networks. Then start the \"GO Negotiation 2023 Responder Test\" on the other device. 2024 Then run each test individually by clicking on its name.</string> 2025 <string name="p2p_join_go_info"> 2026 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2027 Wi-Fi settings and forget all remembered networks. Then start the \"Group Owner Test\" on 2028 the other device. 2029 Then run each test individually by clicking on its name.</string> 2030 <string name="p2p_service_discovery_requester_info"> 2031 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2032 Wi-Fi settings and forget all remembered networks. Then start the \"Service Discovery 2033 Responder Test\" on the other device. 2034 Then run each test individually by clicking on its name.</string> 2035 2036 <string name="p2p_not_enabled">Wi-Fi is not enabled</string> 2037 <string name="p2p_not_enabled_message">These tests require Wi-Fi to be enabled. 2038 Click the button below to go to system settings and enable Wi-Fi.</string> 2039 <string name="p2p_settings">Wi-Fi Direct Settings</string> 2040 2041 <string name="p2p_result_success">Test passed successfully.</string> 2042 2043 <string name="p2p_go_neg_responder_ready"> 2044 The go negotiation responder is now ready to start. 2045 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2046 Wi-Fi settings and forget all remembered networks. Then start the \"GO Negotiation 2047 Requester Test\" on the other device. 2048 Keep the screen here until all tests on the other device are 2049 finished.</string> 2050 <string name="p2p_go_ready"> 2051 The group owner is now ready to start. 2052 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2053 Wi-Fi settings and forget all remembered networks. Then start the \"Join Group Test\" on 2054 the other device. 2055 Keep the screen here until all tests on the other device are 2056 finished.</string> 2057 <string name="p2p_service_responder_ready"> 2058 The service responder is now ready to start. 2059 Go to the Security and Location settings and ensure that Location is enabled. Then go to the 2060 Wi-Fi settings and forget all remembered networks. Then start the \"Service Discovery 2061 Requester Test\" on the other device. 2062 Keep the screen here until all tests on the other device are 2063 finished.</string> 2064 2065 <string name="p2p_setup_error"> 2066 Test failed.\n\nSet up error. Check whether Wi-Fi can be enabled.</string> 2067 <string name="p2p_unexpected_error"> 2068 Test failed.\n\nUnexpected error. Check logcat.</string> 2069 <string name="p2p_add_local_service_error"> 2070 Test failed.\n\nFailed to add local service.</string> 2071 <string name="p2p_add_service_request_error"> 2072 Test failed.\n\nFailed to add service request.</string> 2073 <string name="p2p_remove_service_request_error"> 2074 Test failed.\n\nFailed to remove service request.</string> 2075 <string name="p2p_clear_service_requests_error"> 2076 Test failed.\n\nFailed to clear service requests.</string> 2077 <string name="p2p_connect_error"> 2078 Test failed.\n\nFailed to start a p2p connection to the target device.</string> 2079 <string name="p2p_remove_group_error"> 2080 Test failed.\n\nFailed to remove a p2p group.</string> 2081 <string name="p2p_discover_peers_error"> 2082 Test failed.\n\nFailed to discover peers.</string> 2083 <string name="p2p_discover_services_error"> 2084 Test failed.\n\nFailed to discover services.</string> 2085 <string name="p2p_ceate_group_error"> 2086 Test failed.\n\nFailed to start up group owner.</string> 2087 <string name="p2p_no_service_requests_error"> 2088 Test failed.\n\n\"NO_SERVICE_REQUESTS\" error did not occur.</string> 2089 <string name="p2p_receive_invalid_response_error"> 2090 Test failed.\n\nReceived an invalid message or could not receive 2091 the expected message.\n\n</string> 2092 <string name="p2p_target_not_found_error">Test failed.\n\n 2093 The target responder device was NOT found. Start up the responder 2094 test on the other device, then run the test again.</string> 2095 <string name="p2p_target_invalid_role_error">Test failed.\n\n 2096 The target responder must be p2p device. However, the target responder 2097 device was group owner. Check the test case on the other device.</string> 2098 <string name="p2p_target_invalid_role_error2">Test failed.\n\n 2099 The target responder must be group owner. However, the target responder 2100 device was p2p device. Check the test case on the other device.</string> 2101 <string name="p2p_connection_error"> 2102 Test failed.\n\nFailed to establish a p2p connection.</string> 2103 <string name="p2p_detect_disconnection_error"> 2104 Test failed.\n\nFailed to detect client disconnection.</string> 2105 <string name="p2p_disconnect_error"> 2106 Test failed.\n\nFailed to disconnect a p2p connection.</string> 2107 2108 <string name="p2p_search_target">Search Target</string> 2109 <string name="p2p_searching_target">Searching for target device ...</string> 2110 <string name="p2p_checking_serv_capab">Checking the service discovery 2111 capability ...</string> 2112 <string name="p2p_connecting_with_pbc">Trying to connect the target device ...\n\n 2113 Click the \"OK\" button on the other device to accept the connection 2114 request from this device.</string> 2115 <string name="p2p_connecting_with_pin">Trying to connect the target device ...\n\n 2116 Enter the pin number on the other device.</string> 2117 <string name="p2p_waiting_for_peer_to_connect">Waiting for peer to 2118 connect ...</string> 2119 <string name="p2p_waiting_for_peer_to_disconnect">Waiting for peer 2120 to disconnect ...</string> 2121 2122 <!-- Strings for TestListActivity --> 2123 <string name="aware_test">Wi-Fi Aware Test</string> 2124 <string name="aware_test_info"> 2125 The Wi-Fi Aware tests require two devices with Wi-Fi enabled. One device must 2126 be the candidate device running the software build to be tested, while the other 2127 device must be an implementation already known to be compatible.\n\nThere are 2128 tests for Publisher and Subscriber, Responder and Initiator. One device should 2129 start in a role, and the other should start in the complementary 2130 role. Your device must pass the tests in all roles. 2131 </string> 2132 <string name="aware_not_enabled">Wi-Fi / Location Mode is not enabled</string> 2133 <string name="aware_not_enabled_message">These tests require Wi-Fi and Location Mode to be enabled. 2134 Click the button below to go to system settings and enable Wi-Fi and Location Mode.</string> 2135 <string name="aware_settings">Wi-Fi Settings</string> 2136 <string name="aware_setup_error"> 2137 Test failed.\n\nSet up error. Check whether Wi-Fi is enabled.</string> 2138 <string name="aware_unexpected_error"> 2139 Test failed.\n\nUnexpected error. Check logcat.</string> 2140 2141 <string name="aware_dp_ib_open_unsolicited">Data Path: Open: Unsolicited/Passive</string> 2142 <string name="aware_dp_ib_passphrase_unsolicited">Data Path: Passphrase: Unsolicited/Passive</string> 2143 <string name="aware_dp_ib_pmk_unsolicited">Data Path: PMK: Unsolicited/Passive</string> 2144 <string name="aware_dp_ib_open_solicited">Data Path: Open: Solicited/Active</string> 2145 <string name="aware_dp_ib_passphrase_solicited">Data Path: Passphrase: Solicited/Active</string> 2146 <string name="aware_dp_ib_pmk_solicited">Data Path: PMK: Solicited/Active</string> 2147 <string name="aware_dp_ib_open_unsolicited_accept_any">Data Path: Open: Unsolicited/Passive: accept any peer</string> 2148 <string name="aware_dp_ib_passphrase_unsolicited_accept_any">Data Path: Passphrase: Unsolicited/Passive: accept any peer</string> 2149 <string name="aware_dp_ib_pmk_unsolicited_accept_any">Data Path: PMK: Unsolicited/Passive: accept any peer</string> 2150 <string name="aware_dp_ib_open_solicited_accept_any">Data Path: Open: Solicited/Active: accept any peer</string> 2151 <string name="aware_dp_ib_passphrase_solicited_accept_any">Data Path: Passphrase: Solicited/Active: accept any peer</string> 2152 <string name="aware_dp_ib_pmk_solicited_accept_any">Data Path: PMK: Solicited/Active: accept any peer</string> 2153 <string name="aware_dp_ib_force_channel_setup">Data Path: force channel setup</string> 2154 <string name="aware_discovery_ranging">Discovery with Ranging</string> 2155 <string name="aware_publish">Publish</string> 2156 <string name="aware_subscribe">Subscribe</string> 2157 2158 <string name="aware_dp_oob_open">Data Path (OOB): Open</string> 2159 <string name="aware_dp_oob_passphrase">Data Path (OOB): Passphrase</string> 2160 <string name="aware_responder">Responder</string> 2161 <string name="aware_initiator">Initiator</string> 2162 2163 <string name="aware_status_attached">Attached ...</string> 2164 <string name="aware_status_attach_fail">Attach failure!</string> 2165 <string name="aware_status_attach_timeout">Attach failure - timed out!</string> 2166 <string name="aware_status_identity">Discovery (Identity) MAC address: %1$s ...</string> 2167 <string name="aware_status_identity_fail">Identity listener failure - timed out!</string> 2168 <string name="aware_status_subscribe_started">Subscribe discovery session started ...</string> 2169 <string name="aware_status_subscribe_failed">Subscribe failure!</string> 2170 <string name="aware_status_subscribe_timeout">Subscribe failure - timed out!</string> 2171 <string name="aware_status_subscribe_null_session">Subscribe failure - null session!</string> 2172 <string name="aware_status_publish_started">Publish discovery session started ...</string> 2173 <string name="aware_status_publish_failed">Publish failure!</string> 2174 <string name="aware_status_publish_timeout">Publish failure - timed out!</string> 2175 <string name="aware_status_publish_null_session">Publish failure - null session!</string> 2176 <string name="aware_status_discovery">Service discovered ...</string> 2177 <string name="aware_status_discovery_with_info">Service discovered ... peer MAC : %1$s</string> 2178 <string name="aware_status_discovery_timeout">Service discovery failure - timed out!</string> 2179 <string name="aware_status_discovery_fail">Service discovery failure - parameter mismatch!</string> 2180 <string name="aware_status_send_success">Sent message successfully ...</string> 2181 <string name="aware_status_send_failed">Send message failure!</string> 2182 <string name="aware_status_send_timeout">Send message failure - timed out!</string> 2183 <string name="aware_status_send_fail_parameter">Send message failure - mismatched ids!</string> 2184 <string name="aware_status_received">Received message ...</string> 2185 <string name="aware_status_starting_rtt">Starting RTT operations ...</string> 2186 <string name="aware_status_waiting_for_peer_rtt">Pausing to let other device perform RTT ...</string> 2187 <string name="aware_status_received_peer_rtt_done">Other device done with RTT ...</string> 2188 <string name="aware_status_received_mac">Received peer MAC address: %1$s ...</string> 2189 <string name="aware_status_receive_timeout">Receive message failure - timed out!</string> 2190 <string name="aware_status_receive_failure">Receive message failure - didn\'t receive expected message!</string> 2191 <string name="aware_status_network_requested">Network requested ...</string> 2192 <string name="aware_status_network_success">Network formed ...</string> 2193 <string name="aware_status_network_failed">Network request failure - timed out!</string> 2194 <string name="aware_status_network_failed_leak">Failure: Network request success - but leaked information!</string> 2195 <string name="aware_status_sleeping_wait_for_responder">Pausing to let Responder time to set up ...</string> 2196 <string name="aware_status_ranging_peer_failure">Ranging to PeerHandle failure: %1$d failures of %2$d attempts!</string> 2197 <string name="aware_status_ranging_mac_failure">Ranging to MAC address failure: %1$d failures of %2$d attempts!</string> 2198 <string name="aware_status_ranging_peer_success">Ranging to PeerHandle success: %1$d successes of %2$d attempts!</string> 2199 <string name="aware_status_ranging_mac_success">Ranging to MAC address success: %1$d successes of %2$d attempts!</string> 2200 <string name="aware_status_lifecycle_failed">Discovery lifecycle FAILURE!</string> 2201 <string name="aware_status_lifecycle_ok">Discovery lifecycle validated!</string> 2202 2203 <string name="aware_status_socket_failure">Failure on socket connection setup!</string> 2204 <string name="aware_status_socket_server_socket_started">ServerSocket started on port %1$d!</string> 2205 <string name="aware_status_socket_server_info_rx">Peer server info: IPv6=%1$s @ port=%2$d!</string> 2206 <string name="aware_status_socket_server_message_from_peer">Message from peer: \'%1$s\'</string> 2207 2208 <string name="aware_data_path_open_unsolicited_publish">Data Path: Open: Unsolicited Publish</string> 2209 <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> 2210 <string name="aware_data_path_open_passive_subscribe">Data Path: Open: Passive Subscribe</string> 2211 2212 <string name="aware_data_path_passphrase_unsolicited_publish">Data Path: Passphrase: Unsolicited Publish</string> 2213 <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> 2214 <string name="aware_data_path_passphrase_passive_subscribe">Data Path: Passphrase: Passive Subscribe</string> 2215 2216 <string name="aware_data_path_pmk_unsolicited_publish">Data Path: PMK: Unsolicited Publish</string> 2217 <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> 2218 <string name="aware_data_path_pmk_passive_subscribe">Data Path: PMK: Passive Subscribe</string> 2219 2220 <string name="aware_data_path_open_solicited_publish">Data Path: Open: Solicited Publish</string> 2221 <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> 2222 <string name="aware_data_path_open_active_subscribe">Data Path: Open: Active Subscribe</string> 2223 2224 <string name="aware_data_path_passphrase_solicited_publish">Data Path: Passphrase: Solicited Publish</string> 2225 <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> 2226 <string name="aware_data_path_passphrase_active_subscribe">Data Path: Passphrase: Active Subscribe</string> 2227 2228 <string name="aware_data_path_pmk_solicited_publish">Data Path: PMK: Solicited Publish</string> 2229 <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> 2230 <string name="aware_data_path_pmk_active_subscribe">Data Path: PMK: Active Subscribe</string> 2231 2232 <string name="aware_data_path_oob_open_responder">Data Path (OOB): Open: Responder</string> 2233 <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> 2234 <string name="aware_data_path_oob_open_initiator">Data Path (OOB): Open: Initiator</string> 2235 2236 <string name="aware_data_path_oob_passphrase_responder">Data Path (OOB): Passphrase: Responder</string> 2237 <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> 2238 <string name="aware_data_path_oob_passphrase_initiator">Data Path (OOB): Passphrase: Initiator</string> 2239 2240 <string name="aware_discovery_ranging_publish">Discovery with Ranging: Publish</string> 2241 <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> 2242 <string name="aware_discovery_ranging_subscribe">Discovery with Ranging: Subscribe</string> 2243 2244 <string name="aware_data_path_force_channel_setup_publish">Data Path: force channel setup Publish</string> 2245 <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> 2246 <string name="aware_data_path_force_channel_setup_subscribe">Data Path: force channel setup Subscribe</string> 2247 2248 <string name="camera_fov_calibration">Camera FOV Calibration</string> 2249 <string name="camera_fov_calibration_done">Done</string> 2250 <string name="camera_fov_general_settings">General settings</string> 2251 <string name="camera_fov_label_options">Settings</string> 2252 <string name="camera_fov_tap_to_take_photo">Tap to calibrate</string> 2253 <string name="camera_fov_marker_distance">Marker distance (in cm)</string> 2254 <string name="camera_fov_marker_distance_description">The distance in centimeters between 2255 the solid lines on the target pattern.</string> 2256 <string name="camera_fov_target_distance">Target distance (in cm)</string> 2257 <string name="camera_fov_target_distance_description">The distance in centimeters from the 2258 device to the target pattern.</string> 2259 <string name="camera_fov_settings_button_text">Setup</string> 2260 <string name="camera_fov_change_preview_sizes_button_text">Preview Sizes</string> 2261 <string name="camera_fov_choose_preview_size_for_camera">Choose preview size for camera %1$s</string> 2262 <string name="camera_fov_displayed_fov_label">Displayed FOV : </string> 2263 <string name="camera_fov_reported_fov_label">Reported FOV : </string> 2264 <string name="camera_fov_reported_fov_problem">Reported FOV problem</string> 2265 <string name="camera_fov_reported_fov_problem_message">The reported FOV before takePicture() is 2266 different from when onPictureTaken() is called.\nAs picture size has not been changed, the 2267 reported FOV should be identical at both times.\n\nFOV before/after: %1$f / %2$f</string> 2268 2269 <string name="camera_fov_panorama_wallpaper_title">Photo Sphere Live Wallpaper</string> 2270 <string name="camera_fov_panorama_wallpaper_description">This live wallapper displays photo 2271 spheres.</string> 2272 <string name="camera_fov_select_panorama">Select panorama</string> 2273 <string name="camera_fov_select_panorama_description">Select a panorama to display in the 2274 live wallpaper.</string> 2275 <string name="camera_fov_reset_panorama">Reset panorama</string> 2276 <string name="camera_fov_reset_panorama_description">Resets the panorama to show the demo 2277 file.</string> 2278 <string name="camera_fov_enable_compass_mode">Enable compass mode</string> 2279 <string name="camera_fov_enable_compass_mode_description">If enabled, the panorama orients 2280 itself according to the current rotation of the device.</string> 2281 2282 <string name="test_category_notifications">Notifications</string> 2283 <string name="test_category_tiles">Tiles</string> 2284 <string name="package_priority_test">Notification Package Priority Test</string> 2285 <string name="package_priority_info">This test checks that the NotificationManagerService respects 2286 user preferences about relative package priorities. 2287 </string> 2288 <string name="package_priority_bot">Verifying that the CTS Robot helper package is installed.</string> 2289 <string name="package_priority_high">Find \"%s\" in the \"Notifications\" settings panel, and allow it to Override Do Not Disturb.</string> 2290 <string name="package_priority_default">Find \"%s\" in the \"Notifications\" settings panel, and disallow it to Override Do Not Disturb.</string> 2291 <string name="package_priority_user_order">Check that ranker respects user priorities.</string> 2292 2293 <string name="test_category_vibrations">Vibrations</string> 2294 <string name="test_title_has_vibrator">Has Vibrator Test</string> 2295 2296 <string name="shortcut_reset_test">Shortcut Reset Rate-limiting Test</string> 2297 <string name="shortcut_reset_info">This test checks that when an inline-reply happens, ShortcutManager\'s rate-limiting 2298 is reset. Please grant access to show notification when prompted.</string> 2299 <string name="shortcut_reset_bot">Verifying that the CTS Robot helper package is installed.</string> 2300 <string name="shortcut_reset_start">Showing the notification.</string> 2301 <string name="shortcut_reset_prompt_inline_reply">Open the notification shade, 2302 find the \"Shortcut Reset Rate-limiting Test\" notification, type something in the inline-reply field and 2303 press the send button.</string> 2304 <string name="shortcut_reset_check_result">Check ShortcutManager rate-limit has been reset.</string> 2305 2306 <string name="ringer_mode_tests">Ringer Mode Tests</string> 2307 <string name="ringer_mode_info">This test checks that Audio manager functionality that requires 2308 particular ringer mode states works properly. 2309 </string> 2310 <string name="ringer_mode_pass_test">These tests are handled by CTS.</string> 2311 <string name="test_sound_effects">Test Tap & click sounds</string> 2312 <string name="test_vibrate_notification">Test vibrate notification</string> 2313 <string name="test_vibrate_ringer">Test vibrate ringer</string> 2314 <string name="test_access_ringer_mode">Test access ringer mode</string> 2315 <string name="test_ringer_mode_policy_access">Test ringer mode policy access</string> 2316 <string name="test_volume_dnd_affected_stream">Test volume change</string> 2317 <string name="test_volume_stream_1">Test volume change part 1</string> 2318 <string name="test_volume_stream_2">Test volume change part 2</string> 2319 <string name="test_volume_stream_3">Test volume change part 3</string> 2320 <string name="test_mute_dnd_affected_streams">Test mute streams</string> 2321 <string name="test_ringer_manager">Test RingtoneManager</string> 2322 <string name="enable_sound_effects">Please enable Tap & click sounds in Sound settings.</string> 2323 <string name="attention_ready">I\'m done</string> 2324 <string name="attention_filter_any">Please enable \"Do not disturb\" by tapping the Quick Settings tile.</string> 2325 <string name="attention_filter_all">Please disable \"Do not disturb\" by tapping the Quick Settings tile.</string> 2326 <string name="attention_filter_priority">Please enable \"Do not disturb\" by tapping the Quick 2327 Settings tile. Then, long press the same tile and customize the setting to allow messages 2328 from starred contacts only.</string> 2329 <string name="attention_filter_priority_mimic_alarms_only">Please enable Priority-Only \"Do not disturb\" 2330 by tapping the Quick Settings tile. Then, long press the same tile and customize the setting to allow sounds 2331 from Alarms and Media (if applicable) only.</string> 2332 <string name="attention_create_contacts">Create contacts for notification annotations.</string> 2333 <string name="attention_delete_contacts">Delete test contacts.</string> 2334 <string name="attention_default_order">Check that ranker defaults to time order.</string> 2335 <string name="attention_priority_order">Check that ranker respects developers priorities.</string> 2336 <string name="attention_ambient_bit">Check that the ambient bit is set appropriately.</string> 2337 <string name="attention_lookup_order">Check that ranker respects Lookup URIs for contacts.</string> 2338 <string name="attention_email_order">Check that ranker respects mailto URIs for contacts.</string> 2339 <string name="attention_phone_order">Check that ranker respects telephone URIs for contacts.</string> 2340 <string name="attention_interruption_order">Check that ranker temporarily boosts interruptions. 2341 This test takes 30 seconds to complete.</string> 2342 <string name="attention_none_are_filtered_messages">Check that \"All\" mode doesn\'t filter any notifications (messages).</string> 2343 <string name="attention_none_are_filtered_diff_categories">Check that \"All\" mode doesn\'t filter any notifications (event, reminder, alarm).</string> 2344 <string name="attention_some_are_filtered_messages">Check that \"Priority\" mode doesn\'t filter priority notifications (messages from starred contacts).</string> 2345 <string name="attention_some_are_filtered_alarms">Check that \"Priority\" mode doesn\'t filter priority notifications (alarms).</string> 2346 <string name="attention_some_are_filtered_media_system_other">Check that \"Priority\" mode doesn\'t filter priority notifications (media, system, other).</string> 2347 <string name="attention_all_are_filtered">Check that \"None\" mode filters all notifications.</string> 2348 <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> 2349 <string name="nls_test">Notification Listener Test</string> 2350 <string name="nas_test">Notification Assistant Test</string> 2351 <string name="nls_service_name">Notification Listener for CTS Verifier</string> 2352 <string name="nls_info">This test checks that a NotificationListenerService can be enabled 2353 and disabled, and that once enabled the service is able to receive notifications and 2354 dismiss them. 2355 </string> 2356 <string name="nas_service_name">Notification Assistant for CTS Verifier</string> 2357 <string name="nas_info">This test checks that a NotificationAssistantService can be enabled 2358 and disabled, and that once enabled the service is able to receive notifications and 2359 dismiss them. 2360 </string> 2361 <string name="nls_anr">This test checks that notifications are not sent with content that is 2362 too long. If this test causes the test app to ANR, the test has failed. 2363 </string> 2364 <string name="action_not_sent">SecureActionOnLockScreenTest</string> 2365 <string name="action_received">Action Sent - SecureActionOnLockScreenTest</string> 2366 <string name="action_test_title">Action</string> 2367 <string name="nls_visibility">Please change the lock screen setting to hide sensitive content 2368 on the lockscreen</string> 2369 <string name="nls_restore_visibility">Please change the lock screen setting to show all 2370 content on the lockscreen</string> 2371 <string name="add_screen_lock">Add a secure screen lock of any type.\nLet all notification content be shown.</string> 2372 <string name="set_global_visibility_public">Update notification settings to ensure that all notification content is shown.</string> 2373 <string name="set_global_visibility_private">Update notification settings to ensure that sensitive notification content is shown only when unlocked.</string> 2374 <string name="set_global_visibility_secret">Update notification settings to ensure that all notifications are hidden on the lock screen.</string> 2375 <string name="remove_screen_lock">Remove the added screen lock</string> 2376 <string name="secure_action_lockscreen">Lock the screen and find the SecureActionOnLockScreenTest 2377 notification. Tap on its action. Verify that the keyguard displays on tap, and that the 2378 notification text does not update until the passcode is entered. Ensure that the notification 2379 text does update once the device is unlocked.</string> 2380 <string name="nd_test">Notification Dismiss Test</string> 2381 <string name="nd_test_info">This test checks if Notifications can only be 2382 dismissed, when it is allowed.</string> 2383 <string name="nd_notif_title">NotifDismissTest</string> 2384 <string name="dismiss_notif_from_the_shade">Open the shade while the device is unlocked and find the NotifDismissTest notification.\n 2385 Swipe it to either side to dismiss it.\n 2386 Pass the test if it can be dismissed.</string> 2387 <string name="dismiss_notif_from_the_ls">Lock the screen and find the NotifDismissTest notification.\n 2388 Swipe it to either side to dismiss it.\n 2389 Pass the test if it can be dismissed from the lock screen.</string> 2390 <string name="non_dismissable_notif_from_the_ls">Lock the screen and find the NotifDismissTest notification.\n 2391 Swipe it to either side to dismiss it. Verify that it is non-dismissible.\n 2392 Fail the test if it could be dismissed from the lock screen.</string> 2393 <string name="fsi_test">Notification Full Screen Intent Test</string> 2394 <string name="fsi_test_info">This test checks the behavior of Notifications 2395 with Full Screen Intents.</string> 2396 <string name="fsi_lockscreen_without_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2397 After clicking, lock the screen and press the power button as quickly as possible to go to the lock screen.\n 2398 Wait for a heads up notification to appear first in the list with a pill button.\n 2399 Unlock screen to return to this page after seeing the notification or after 5 seconds.\n 2400 Fail the test if the notification does not appear as described. 2401 </string> 2402 <string name="fsi_lockscreen_with_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2403 After clicking, lock the screen and press the power button as quickly as possible to go to the lock screen.\n 2404 Wait for a page to automatically launch and display the message \"This page is a full screen intent.\".\n 2405 Unlock screen to return to this page after seeing the page or after 5 seconds.\n 2406 Fail the test if the page does not launch as described. 2407 </string> 2408 <string name="fsi_screen_off_without_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2409 After clicking, press the power button as quickly as possible to turn off the screen.\n 2410 Wait for a notification to appear on the screen with a pill button.\n 2411 Unlock screen to return to this page after seeing the notification or after 5 seconds.\n 2412 Fail the test if the notification does not appear as described. 2413 </string> 2414 <string name="fsi_screen_off_with_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2415 After clicking, press the power button as quickly as possible to turn off the screen.\n 2416 Wait for a page to automatically launch and display the message \"This page is a full screen intent.\".\n 2417 Unlock screen to return to this page after seeing the page or after 5 seconds.\n 2418 Fail the test if the page does not launch as described. 2419 </string> 2420 <string name="fsi_aod_with_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2421 After clicking, press the power button as quickly as possible to go to Always on Display.\n 2422 Wait for a page to automatically launch and display the message \"This page is a full screen intent.\".\n 2423 Unlock screen to return to this page after seeing the page or after 5 seconds.\n 2424 Fail the test if the page does not launch as described. 2425 </string> 2426 <string name="fsi_aod_without_permission_instruction">Click the \"I\'m done\" button when you are ready.\n 2427 After clicking, press the power button as quickly as possible to go to Always on Display.\n 2428 Wait for a notification to appear on the screen with a pill button.\n 2429 Unlock screen to return to this page after seeing the notification or after 5 seconds.\n 2430 Fail the test if the notification does not show as described. 2431 </string> 2432 <string name="fsi_turn_on_aod">Turn on Always on Display by toggling on \"Always show time and info\" in Lockscreen Settings.</string> 2433 <string name="fsi_turn_off_aod">Turn off Always on Display by toggling off \"Always show time and info\" in Lockscreen Settings.</string> 2434 <string name="fsi_notif_title">NotifFsiTest</string> 2435 <string name="fsi_mock_call_desc">This page is a full screen intent (e.g. a call).\n 2436 Pass the test if you see this page.\n 2437 To return to the test, use the back button or gesture and unlock the screen. 2438 </string> 2439 <string name="fsi_notif_content">Fsi Notif Content Fsi Notif Content Fsi Notif Content \n 2440 Fsi Notif Content Fsi Notif Content Fsi Notif Content</string> 2441 <string name="fsi_grant_permission">Please toggle on the full screen intents permission for CTSVerifier.</string> 2442 <string name="fsi_deny_permission">Please toggle off the full screen intents permission for CTSVerifier</string> 2443 <string name="fsi_sticky_hun">There should be a sticky Heads Up Notification on the screen.\n 2444 It would not be automatically cleared out.\n 2445 Fail the test if it doesn\'t show or disappears within 60s.</string> 2446 <string name="fsi_sticky_hun_60s">There should be a Heads Up Notification on the screen.\n 2447 It would show for 60s.\n 2448 Fail the test if it doesn\'t show or disappears within 60s.</string> 2449 <string name="notification_style_test">Notification Styles Test</string> 2450 <string name="notification_style_test_info">This test checks that Notification Styles are rendered as expected.</string> 2451 <string name="ns_custom_content_instructions">A notification with custom (app-provided) content was posted. Open the notification shade, collapse the notification (if it\'s expanded) and verify that: 2452 \n\u2022 There is appropriate padding between the blue section and all other visual elements. 2453 \n\u2022 The small icon (A) is clearly visible outside the blue region. 2454 \n\u2022 If an expand/collapse affordance is present, it is clearly visible outside the blue region. 2455 \nIt should look approximately like the image below (when factoring for theme, dynamic color, etc). </string> 2456 <string name="ns_custom_big_content_instructions">A notification with custom (app-provided) content was posted. Open the notification shade, expand the notification (if it\'s collapsed), and verify that: 2457 \n\u2022 There is appropriate padding between the blue section and all other visual elements. 2458 \n\u2022 The small icon (B) is clearly visible outside the blue region. 2459 \n\u2022 The App Name (\"CTS Verifier\") is clearly visible outside the blue region. 2460 \n\u2022 If an expand/collapse affordance is present, it is clearly visible outside the blue region. 2461 \nIt should look approximately like the image below (when factoring for theme, dynamic color, etc). </string> 2462 <string name="ns_custom_heads_up_content_instructions">A notification with custom (app-provided) content was shown in heads-up. While in this state, verify that: 2463 \n\u2022 There is appropriate padding between the blue section and all other visual elements. 2464 \n\u2022 The small icon (C) is clearly visible outside the blue region. 2465 \n\u2022 If an expand/collapse affordance is present, it is clearly visible outside the blue region. 2466 \nIt should look approximately like the image below (when factoring for theme, dynamic color, etc). </string> 2467 <string name="notification_custom_layout_text">Custom content here!</string> 2468 <string name="ns_custom_content_alt_text">This is the expanded version of the notification.\nPlease collapse it to check the custom content view.</string> 2469 <string name="ns_custom_big_content_alt_text">This is the collapsed version of the notification.\nPlease expand it to check the custom big content view.</string> 2470 <string name="ns_custom_heads_up_content_alt_text">This is the expanded version of the notification.\nPlease collapse it (while it\'s showing as heads-up, not in the shade) to check the heads-up content view.</string> 2471 <string name="ns_bigpicture_animated_instructions">A notification with an animated BigPicture was posted. Expand it, and verify that the image is indeed animated.</string> 2472 <string name="np_start_channel_settings">Launch Channel Settings</string> 2473 <string name="np_start_security_settings">Launch Security Settings</string> 2474 <string name="np_start_notif_settings">Launch Notification Settings</string> 2475 <string name="np_start_lockscreen_settings">Launch Lock Screen Settings</string> 2476 <string name="np_when_locked_see_redacted">Lock the screen and find the NotifPrivacyTest notification.\n 2477 Pass the test if the notification content is REDACTED.</string> 2478 <string name="np_when_locked_see_private">Lock the screen and find the NotifPrivacyTest notification.\n 2479 Pass the test if the notification content is EXPOSED.</string> 2480 <string name="np_when_locked_hidden">Lock the screen and look for the NotifPrivacyTest notification.\n 2481 Fail the test if it can be found without unlocking the device.</string> 2482 <string name="np_start_occluding">Launch CallSimulator</string> 2483 <string name="np_occluding_instructions">Launch the CallSimulator and follow the instructions on that screen.</string> 2484 <string name="np_occluding_see_redacted">CallSimulator 2485 \n\n(Like a call, this screen will be visible even when the device is locked.) 2486 \n\nLock the screen, then come back here without unlocking. 2487 \nPull down the notification shade and find the NotifPrivacyTest notification. 2488 \nPass the test if the notification content is REDACTED. 2489 \n\nGo back when ready to Pass/Fail the step.</string> 2490 <string name="np_occluding_see_private">CallSimulator 2491 \n\n(Like a call, this screen will be visible even when the device is locked.) 2492 \n\nLock the screen, then come back here without unlocking. 2493 \nPull down the notification shade and find the NotifPrivacyTest notification. 2494 \nPass the test if the notification content is EXPOSED. 2495 \n\nGo back when ready to Pass/Fail the step.</string> 2496 <string name="np_occluding_hidden">CallSimulator 2497 \n\n(Like a call, this screen will be visible even when the device is locked.) 2498 \n\nLock the screen, then come back here without unlocking. 2499 \nPull down the notification shade and look for the NotifPrivacyTest notification. 2500 \nFail the test if it can be found without unlocking the device. 2501 \n\nGo back when ready to Pass/Fail the step.</string> 2502 <string name="np_public_version_text">NotifPrivacyTest: REDACTED</string> 2503 <string name="np_private_version_text">NotifPrivacyTest: EXPOSED</string> 2504 <string name="notif_privacy_test">Notification Privacy Test</string> 2505 <string name="notif_privacy_info">This test checks that Notification privacy is correctly 2506 handled on the insecure and secure lockscreen. 2507 </string> 2508 <string name="msg_extras_preserved">Check that Message extras Bundle was preserved.</string> 2509 <string name="conversation_section_ordering">Fully expand the notification display and verify 2510 that the \"Person A\" notification appears before the "\Non-Person Notification\". 2511 If this is not a 'handheld' device and does not support conversation notifications or does 2512 not group them together, press Pass.</string> 2513 <string name="hun_display">If this device supports heads-up notifications, 2514 verify that a notification just peeked on screen, displaying all of the following: small 2515 icon, large icon, notification title, notification text, and two action buttons. 2516 If this device does not support heads-up notifications, press Pass.</string> 2517 <string name="action">Action %1$d</string> 2518 <string name="no_test_items">No tests available for this device.</string> 2519 <string name="tile_service_name">Tile Service for CTS Verifier</string> 2520 <string name="tiles_test">Tile Service Test</string> 2521 <string name="tiles_info">This test checks that a Tile Service added by a third party 2522 application is not immediately added to the current Quick Settings tiles but can be added 2523 by the user. 2524 </string> 2525 <string name="tiles_adding_tile">Check that Tile Service is enabled</string> 2526 <string name="tiles_not_added">Open Quick Settings and check that the Tile Service for CTS 2527 Verifier is not visible in any page</string> 2528 <string name="tiles_in_customizer">Open Quick Settings and click the button to customize Quick 2529 Settings. Check that the Tile Service for CTS Verifier is available to be added</string> 2530 <string name="tiles_removing_tile">Check that Tile Service is disabled</string> 2531 <string name="tile_request_service_name">Request Tile Service</string> 2532 <string name="tile_request_helper_app_name">CtsTileServiceApp</string> 2533 <string name="tiles_request_test">Tile Service Request Test</string> 2534 <string name="tiles_request_info">This test checks that a request to add a TileService is 2535 shown correctly to the user and the correct answer is relayed to the app.</string> 2536 <string name="tiles_request_uninstall">This will verify that the helper app is not installed. 2537 If that is correct, the test will pass automatically. If the app is installed, press the button 2538 and you will be prompted for confirmation to uninstall the app.</string> 2539 <string name="tiles_request_install">You should have received a helper app apk with this CTS 2540 Verifier package. Its name is \"CtsTileServiceApp\". Install the test app, by running\n 2541 \"adb install /path/to/CtsTileServiceApp.apk\".\n 2542 Pass the test if the install was successful. Fail it otherwise. 2543 </string> 2544 <string name="tiles_request_install_verify">This will automatically verify that the helper app 2545 is correctly installed.</string> 2546 <string name="tiles_request_tile_not_present">Open Quick Settings and pass this test 2547 if there are no tiles named %1$s in any page.</string> 2548 <string name="tiles_request_dismissed">After pressing \"Start request\", a dialog will appear 2549 requesting to add a quick settings tile. When it appears, dismiss it by tapping outside of 2550 it, or going back.</string> 2551 <string name="tiles_request_correct_info">After pressing \"Start request\", a dialog will appear 2552 requesting to add a quick settings tile. When it appears, verify the following information 2553 in the dialog:\n 2554 1. The name of the app requesting to add the tile is %1$s.\n 2555 2. The label in the tile is %2$s.\n 2556After verifying, tap the option in the dialog to not add the tile.\n 2557When the buttons are enabled, pass this test if the information in the dialog was correct. 2558 </string> 2559 <string name="tiles_request_answer_yes">After pressing \"Start request\", a dialog will appear 2560 requesting to add a quick settings tile. When it appears, tap the option in the dialog to 2561 add the tile. 2562 </string> 2563 <string name="tiles_request_tile_present">Open Quick Settings and pass this test if a tile named 2564 %1$s is visible in some page. 2565 </string> 2566 <string name="tiles_request_check_tile_already_added">Checking tile already added response 2567 </string> 2568 <string name="vr_tests">VR Tests</string> 2569 <string name="test_category_vr">VR</string> 2570 <string name="vr_test_title">VR Listener Test</string> 2571 <string name="vr_service_name">VR Listener for CTS Verifier</string> 2572 <string name="vr_info">This test checks that a VrListenerService can be enabled and disabled, and 2573 and that it receives the correct lifecycle callbacks when entering and exiting VR mode. 2574 </string> 2575 <string name="vr_start_settings">Launch Settings</string> 2576 <string name="vr_start_vr_activity">Launch VR mode activity</string> 2577 <string name="vr_start_double_vr_activity">Launch Two VR mode activities</string> 2578 <string name="vr_start_vr_activity_desc">Click the button to launch the VR mode activity.</string> 2579 <string name="vr_start_vr_double_activity_desc">Click the button to launch two consecutive VR mode activities.</string> 2580 <string name="vr_check_disabled">Check that the CTS VR helper service is disabled by default.</string> 2581 <string name="vr_enable_service">Please enable \"VR Listener for CTS Verifier\" 2582 under Apps > Gear Icon > Special Access > VR Helper Services and return here.</string> 2583 <string name="vr_disable_service">Please disable \"VR Listener for CTS Verifier\" 2584 under Apps > Gear Icon > Special Access > VR Helper Services and return here.</string> 2585 <string name="nas_enable_service">Please enable \"Notification Assistant for CTS Verifier\" 2586 under Apps > Gear Icon > Default > Notification Assistant and return here.</string> 2587 <string name="nas_disable_service">Please disable \"Notification Assistant for CTS Verifier\" 2588 under Apps > Gear Icon > Default > Notification Assistant and return here.</string> 2589 <string name="nls_enable_service">Please enable \"Notification Listener for CTS Verifier\" 2590 under Apps > Gear Icon > Special Access > Notification Access and return here.</string> 2591 <string name="nls_block_app">Please block the linked application and return here.</string> 2592 <string name="nls_unblock_app">Please unblock the linked application and return here.</string> 2593 <string name="nls_block_channel">Please block the linked notification channel and return here.</string> 2594 <string name="nls_block_group">Please block the linked notification channel group and return here.</string> 2595 <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> 2596 <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> 2597 <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> 2598 <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> 2599 <string name="nls_disable_service">Please disable \"Notification Listener for CTS Verifier\" 2600 under Apps > Gear Icon > Special Access > Notification Access and return here.</string> 2601 <string name="nls_start_settings">Launch Settings</string> 2602 <string name="nls_service_started">Service should start once enabled.</string> 2603 <string name="nas_note_enqueued_received">Check that notification was enqueued.</string> 2604 <string name="nls_note_received">Check that notification was received.</string> 2605 <string name="nls_payload_intact">Check that notification payload was intact.</string> 2606 <string name="nls_audibly_alerted">Check that notification audibly alerting was reported correctly.</string> 2607 <string name="nas_adjustment_payload_intact">Check that the Assistant can adjust notifications.</string> 2608 <string name="nas_adjustment_enqueue_payload_intact">Check that the Assistant can adjust notifications on enqueue.</string> 2609 <string name="nas_create_channel">Check that the Assistant can create a Notification Channel for another app.</string> 2610 <string name="nas_update_channel">Check that the Assistant can update a Notification Channel for another app.</string> 2611 <string name="nas_block_channel">Check that the Assistant can block a Notification Channel.</string> 2612 <string name="nas_delete_channel">Check that the Assistant can delete a Notification Channel for another app.</string> 2613 <string name="nas_snooze_context">Check that the Assistant can snooze a notification until a given context.</string> 2614 <string name="nls_clear_one">Check that service can clear a notification.</string> 2615 <string name="nls_clear_one_reason">Check that service can clear a notification and receive the correct reason for dismissal.</string> 2616 <string name="nls_clear_one_stats">Check that service does not receive notification stats.</string> 2617 <string name="nls_clear_all">Check that service can clear all notifications that are not ongoing.</string> 2618 <string name="nls_clear_ongoing">Check that service cannot clear an ongoing notification.</string> 2619 <string name="nls_service_stopped">Service should stop once disabled.</string> 2620 <string name="nls_note_missed">Check that notification was not received.</string> 2621 <string name="nls_snooze">Check the service can be snoozed.</string> 2622 <string name="nls_unsnooze">Check the service can be unsnoozed.</string> 2623 <string name="nls_hints">Check that the listener can set hints.</string> 2624 <string name="nls_snooze_one">Check that service can snooze a notification.</string> 2625 <string name="nls_snooze_one_time">Check that service can snooze a notification for a given time.</string> 2626 <string name="nls_get_snoozed">Check that service can retrieve snoozed notifications.</string> 2627 <string name="nls_unsnooze_one">Check that service can unsnooze a notification.</string> 2628 <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> 2629 <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> 2630 <string name="nls_filter_test">Checking that an alerting notification is received and a silent one is not</string> 2631 <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> 2632 <string name="nls_reset_app_filter">Go to settings and allow this listener to see notifications from all apps, and then return here.</string> 2633 <string name="nls_confirm_filter_selection">Confirm that the type and app filters are updated</string> 2634 <string name="nls_confirm_notification_not_visible">Checking visibility of notification from CTSVerifier</string> 2635 <string name="nas_note_missed_enqueued">Check that notification was not enqueued.</string> 2636 <string name="cp_test">Condition Provider test</string> 2637 <string name="cp_service_name">Condition Provider for CTS Verifier</string> 2638 <string name="cp_info">This test checks that ConditionProviderService can be enabled 2639 and disabled, and that once enabled the service is able to create, query, edit, and delete 2640 automatic zen rules. 2641 </string> 2642 <string name="cp_enable_service">Please enable \"CTS Verifier\" under Do Not Disturb access and return here.</string> 2643 <string name="cp_disable_service">Please disable \"CTS Verifier\" under Do Not Disturb access and return here.</string> 2644 <string name="cp_start_settings">Launch Settings</string> 2645 <string name="cp_create_rule">Creating Automatic Zen Rule</string> 2646 <string name="cp_create_rule_with_zen_policy">Creating Automatic Zen Rule with Zen Policy</string> 2647 <string name="cp_update_rule">Updating Automatic Zen Rule</string> 2648 <string name="cp_update_rule_use_zen_policy">Updating Automatic Rule to Use Zen Policy</string> 2649 <string name="cp_subscribe_rule">Subscribing to Automatic Zen Rule</string> 2650 <string name="cp_service_started">Service should start once enabled.</string> 2651 <string name="cp_service_stopped">Service should stop once disabled.</string> 2652 <string name="cp_unsubscribe_rule">Unsubscribing to Automatic Zen Rule</string> 2653 <string name="cp_delete_rule">Deleting Automatic Zen Rule via api</string> 2654 <string name="cp_get_rules">Retrieving Automatic Zen Rules</string> 2655 <string name="cp_get_rule">Retrieving Automatic Zen Rule</string> 2656 <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> 2657 <string name="cp_show_rules_verification">Was the automatic rule screen shown?</string> 2658 <string name="cp_disable_rule">Please disable rule "123" and return here.</string> 2659 <string name="cp_enable_rule">Please enable rule "123" and return here.</string> 2660 <string name="cp_delete_rule_broadcast">Please delete rule "123" and return here.</string> 2661 <string name="cp_rule_type">CTS rule</string> 2662 <string name="iva_pass">Pass</string> 2663 <string name="iva_fail">Fail</string> 2664 2665 <string name="cacert_test">CA Cert Notification Test</string> 2666 <string name="cacert_info">This test checks that when a CA Certificate is installed, the user is notified.</string> 2667 <string name="cacert_do_something">Do it</string> 2668 <string name="cacert_done">Done</string> 2669 <string name="cacert_install_cert_title">Tap to install a CA certificate</string> 2670 <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> 2671 <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> 2672 <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> 2673 <string name="cacert_check_notification">Look at the system notifications. Confirm that:\n 26741. There is a notification saying a certificate authority is installed.\n 26752. Tapping that notification brings up a more detailed explanation and a button to check trusted credentials.\n 26763. Tapping that button brings up the Trusted Credentials page you just visited.</string> 2677 <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> 2678 2679 <string name="caboot_test">CA Cert Notification on Boot test</string> 2680 <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> 2681 <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> 2682 <string name="caboot_check_creds">Check Credentials</string> 2683 <string name="caboot_if_not_installed">Only if there is no credential currently installed, install one.</string> 2684 <string name="caboot_install_cert">Install credential</string> 2685 <string name="caboot_remove_screen_lock">Remove screen lock</string> 2686 <string name="caboot_reboot_desc">Please reboot the device and return to this test.</string> 2687 <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> 2688 2689 <!-- Strings for KeyChain --> 2690 <string name="keychain_test">KeyChain Storage Test</string> 2691 <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> 2692 <string name="keychain_reset">Reset</string> 2693 <string name="keychain_skip">Skip</string> 2694 <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 2695 Tap \'Next\' to begin.</string> 2696 <string name="keychain_install_desc">Credentials generated. Tap \'Next\' to install them to the system keychain.\n\n 2697The container for the credentials will not be protected with a password; if prompted for one, leave that field blank.\n\n 2698During installation you may be prompted for a name - accept the default suggestion.\n\n 2699In the case that these credentials were already installed, you may skip this step.</string> 2700 <string name="keychain_https_desc">The last test involves setting up an HTTPS connection using credentials from the KeyChain.\n\n 2701You should be prompted to select credentials; choose the ones you just installed in the previous step.</string> 2702 <string name="keychain_reset_desc">Before marking this test as passed, tap \'Next\' to open security settings to clear credentials:\n 2703 1. Open Encryption and credentials.\n 2704 2. Tap Clear credentials.</string> 2705 2706 <!-- Strings for CA cert installation via intent test --> 2707 <string name="cacert_install_via_intent">CA Cert install via intent</string> 2708 <string name="cacert_install_via_intent_title">This test attempts to install a CA certificate via an intent.</string> 2709 <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> 2710 2711 <!-- Strings for credential management test --> 2712 <string name="credential_management_app_test">Credential Management App Test</string> 2713 <string name="credential_management_app_info">This test requests to manage the user\'s KeyChain credentials and become the credential management app.</string> 2714 <string name="request_manage_credentials">Request to manage credentials</string> 2715 <string name="is_credential_management_app">Check is credential management app</string> 2716 <string name="credential_management_app_policy">Check correct authentication policy is set</string> 2717 <string name="generate_key_pair">Generate key pair</string> 2718 <string name="create_and_install_certificate">Create and install certificate</string> 2719 <string name="request_certificate_authentication">Request certificate for authentication</string> 2720 <string name="sign_data_with_key">Sign data with the private key</string> 2721 <string name="verify_signature">Verify signature with the public key</string> 2722 <string name="remove_credential_management_app">Remove credential management app</string> 2723 2724 <!-- Strings for Widget --> 2725 <string name="widget_framework_test">Widget Framework Test</string> 2726 <string name="widget_framework_test_info">This test checks some basic features of the widget 2727 framework. In order to perform the test, press the Home button. Add the widget 2728 titled "CTS Verifier" to the home screen. Follow the instructions in the widget.</string> 2729 <string name="widget_name">Widget Framework Test</string> 2730 <string name="widget_pass">Pass</string> 2731 <string name="widget_fail">Fail</string> 2732 <string name="widget_generated_previews_test">Widget Generated Previews Test</string> 2733 <string name="widget_generated_previews_test_info">This test checks that the widget picker 2734 displays the generated preview for a widget if it is available. In order to perform the 2735 test, press the Home button and open the widget picker. Scroll to find the widget titled 2736 \"Generated Previews\", and verify that the widget preview displays the text 2737 \"This is a generated preview\".</string> 2738 <string name="widget_generated_previews_widget_name">Generated Previews</string> 2739 <string name="widget_generated_previews_default_preview_text">static previewLayout preview</string> 2740 <string name="widget_generated_previews_generated_preview_text">This is a generated preview</string> 2741 2742 <string name="provisioning_byod_non_market_apps">Non-market app installation restrictions</string> 2743 <string name="provisioning_byod_non_market_apps_info"> 2744 This test exercises user restrictions on installation of non-market apps. Follow 2745 instructions in each test. 2746 </string> 2747 2748 <string name="provisioning_byod_nonmarket_allow">Enable non-market apps</string> 2749 <string name="provisioning_byod_nonmarket_allow_info"> 2750 This test verifies that non-market apps can be installed if permitted.\n 2751 1. A package installation UI should appear.\n 2752 2. If \'Cts Verifier\' is not allowed to install apps, a warning dialog will appear 2753 blocking the install. In this case go to step 3, else skip to step 4.\n 2754 3. Allow \'Cts Verifier\' to install apps. Return to package installer.\n 2755 4. Accept the installation and verify that it succeeds (no error message is displayed). 2756 </string> 2757 2758 <string name="provisioning_byod_nonmarket_deny">Disable non-market apps</string> 2759 <string name="provisioning_byod_nonmarket_deny_info"> 2760 This test verifies that non-market apps cannot be installed unless permitted.\n 2761 1. A package installation UI should appear.\n 2762 2. Verify that the installation of the package is refused. 2763 </string> 2764 2765 <string name="provisioning_byod_nonmarket_allow_global">Enable non-market apps (global restriction)</string> 2766 <string name="provisioning_byod_nonmarket_allow_global_info"> 2767 This test verifies that non-market apps can be installed if permitted by device-wide block.\n 2768 1. A package installation UI should appear.\n 2769 2. If \'Cts Verifier\' is not allowed to install apps, a warning dialog will appear 2770 blocking the install. In this case go to step 3, else skip to step 4.\n 2771 3. Allow \'Cts Verifier\' to install apps. Return to package installer.\n 2772 4. Accept the installation and verify that it succeeds (no error message is displayed). 2773 </string> 2774 2775 <string name="provisioning_byod_nonmarket_deny_global">Disable non-market apps (global restriction)</string> 2776 <string name="provisioning_byod_nonmarket_deny_global_info"> 2777 This test verifies that non-market apps cannot be installed unless permitted by device-wide block.\n 2778 1. A package installation UI should appear.\n 2779 2. Verify that the installation of the package is refused. 2780 </string> 2781 2782 <string name="provisioning_byod_nonmarket_allow_global_primary">Enable primary user non-market apps (global restriction)</string> 2783 <string name="provisioning_byod_nonmarket_allow_global_primary_info"> 2784 This test verifies that non-market apps from the primary user can be installed if permitted.\n 2785 1. You should have received NotificationBot.apk together with the CTS verifier. If you built 2786 the CTS verifier yourself, build the NotificationBot.apk by issuing the following command on 2787 the host:\n 2788 make NotificationBot\n 2789 2. Upload the NotificationBot.apk to your device by issuing the following command on the 2790 host:\n 2791 adb push /path/to/NotificationBot.apk /data/local/tmp/\n 2792 3. Press \"Go\" to install NotificationBot.apk in your personal profile. A package 2793 installation UI should appear.\n 2794 4. If \'Cts Verifier\' is not allowed to install apps, a warning dialog will appear 2795 blocking the install. In this case go to step 5, else skip to step 6.\n 2796 5. Allow \'Cts Verifier\' to install apps. Return to package installer.\n 2797 6. Accept the installation and verify that it succeeds (no error message is displayed). 2798 </string> 2799 2800 <string name="provisioning_byod_nonmarket_deny_global_primary">Disable primary user non-market apps (global restriction)</string> 2801 <string name="provisioning_byod_nonmarket_deny_global_primary_info"> 2802 This test verifies that non-market apps from the primary user cannot be installed unless permitted.\n 2803 1. You should have received NotificationBot.apk together with the CTS verifier. If you built 2804 the CTS verifier yourself, build the NotificationBot.apk by issuing the following command on 2805 the host:\n 2806 make NotificationBot\n 2807 2. Upload the NotificationBot.apk to your device by issuing the following command on the 2808 host:\n 2809 adb push /path/to/NotificationBot.apk /data/local/tmp/\n 2810 3. Press \"Go\" to install NotificationBot.apk in your personal profile. A package 2811 installation UI should appear.\n 2812 4. Verify that the installation of the package is refused. 2813 </string> 2814 2815 <string name="provisioning_byod_capture_image_support">Camera support cross profile image capture</string> 2816 <string name="provisioning_byod_capture_image_support_info"> 2817 This test verifies that images can be captured from the managed profile using the primary profile camera.\n 2818 If prompted, accept the camera permission after pressing go.\n 2819 1. Capture a picture using the camera.\n 2820 2. Verify that the captured picture is shown.\n 2821 3. Click on the close button. 2822 </string> 2823 <string name="provisioning_byod_capture_video_support_with_extra_output">Camera support cross profile video capture (with extra output path)</string> 2824 <string name="provisioning_byod_capture_video_support_info"> 2825 This test verifies that videos can be captured from the managed profile using the primary profile camera.\n 2826 If prompted, accept the camera permission after pressing go.\n 2827 1. Capture a video using the camera.\n 2828 2. Click on the play button.\n 2829 3. Verify that the captured video is played.\n 2830 4. Click on the close button. 2831 </string> 2832 <string name="provisioning_byod_capture_video_support_without_extra_output">Camera support cross profile video capture (without extra output path)</string> 2833 <string name="provisioning_byod_capture_audio_support">Sound recorder support cross profile audio capture</string> 2834 <string name="provisioning_byod_capture_audio_support_info"> 2835 This test verifies that audio can be captured from the managed profile using the primary profile sound recorder.\n 2836 1. Capture audio.\n 2837 2. Click on the play button.\n 2838 3. Verify that the captured audio is played.\n 2839 4. Click on the close button.\n 2840 If this device does not support audio recording, please skip this test and mark it passing.\n 2841 </string> 2842 <string name="provisioning_byod_dismiss_result_dialog">Close</string> 2843 <string name="provisioning_byod_play">Play</string> 2844 <string name="provisioning_byod_verify_image_title">Verify captured image</string> 2845 <string name="provisioning_byod_verify_video_title">Verify captured video</string> 2846 <string name="provisioning_byod_verify_audio_title">Verify captured audio</string> 2847 <string name="provisioning_byod_no_image_capture_resolver">No image capture app present. Skip test.</string> 2848 <string name="provisioning_byod_no_video_capture_resolver">No video capture app present. Skip test.</string> 2849 <string name="provisioning_byod_no_audio_capture_resolver">No audio capture app present. Skip test.</string> 2850 <string name="provisioning_byod_capture_media_error">Error while capturing media from managed profile.</string> 2851 <string name="provisioning_byod_capture_image_error">Error while capturing image from managed profile.</string> 2852 2853 <string name="provisioning_byod_auth_bound_key">Authentication-bound keys</string> 2854 <string name="provisioning_byod_auth_bound_key_info"> 2855 This test verifies keystore cryptographic keys can be bound to device credentials. 2856 These keys should only be available if there was a recent enough authentication. 2857 </string> 2858 <string name="provisioning_byod_auth_bound_key_instruction"> 2859 This test verifies keystore cryptographic keys can be bound to device lockscreen challenge or fingerprints (if available). 2860 These keys should only be available if there was a recent enough authentication. \n 2861 2862 1. Press "Set up" to open Security settings. (If this device has a separate app for work 2863 settings, ignore this button and open that app manually from the launcher.) Create a 2864 lockscreen password and if available, enroll a fingerprint under "Work profile security".\n 2865 2. Go through the list of tests.\n 2866 3. Mark the overall test pass or fail.\n 2867 4. Once the set of tests are completed, remove the lockscreen challenge. 2868 </string> 2869 <string name="provisioning_byod_auth_bound_key_set_up">Set up</string> 2870 <string name="provisioning_byod_lockscreen_bound_key">Lockscreen-bound key test</string> 2871 <string name="provisioning_byod_fingerprint_bound_key">Fingerprint-bound key test</string> 2872 <string name="provisioning_byod_vpn">VPN test</string> 2873 <string name="provisioning_byod_always_on_vpn">Always-on VPN Settings</string> 2874 <string name="provisioning_byod_always_on_vpn_info"> 2875 In this test, you\'ll verify that the Settings UI for always-on VPN is correct for different 2876 VPN apps. 2877 </string> 2878 <string name="provisioning_byod_always_on_vpn_instruction"> 2879 In this test, you\'ll verify the Settings UI for always-on VPN for different VPN apps. 2880 You should have received three VPN app apks with this CTS Verifier package. 2881 They\'re named in the form of \"CtsVpnFirewallApp*.apk\".\n 2882 2883 1. Before the test, make sure CtsVpnFirewallApp isn\'t installed on your device. You can 2884 uninstall either by UI, or by\n 2885 \"adb uninstall com.android.cts.vpnfirewall\"\n 2886 2887 2. Install the first test app, by running\n 2888 \"adb install --bypass-low-target-sdk-block /path/to/CtsVpnFirewallAppApi23.apk\"\n 2889 2890 3. Tap \"Prepare VPN\" button below and consent to the VPN connection.\n 2891 2892 4. Once connected, verify that the system shows disclosure (on some devices this is shown in 2893 the notification area) that network traffic is being routed through the VPN app.\n 2894 2895 5. Finish all three test cases listed below.\n 2896 2897 6. Repeat step 1 to remove CtsVpnFirewallApp. 2898 </string> 2899 <string name="provisioning_byod_allow_nondismissible_notification_channel">Non-Dismissible Notification Channel</string> 2900 <string name="provisioning_byod_allow_nondismissible_notification_title">Non-Dismissible Notification</string> 2901 <string name="provisioning_byod_allow_nondismissible_notification_text">This is a notification</string> 2902 <string name="provisioning_byod_allow_nondismissible_notification">Non-Dismissible notification</string> 2903 <string name="provisioning_byod_allow_nondismissible_notification_instructions"> 2904 In this test, you\'ll verify that you are unable to dismiss a notification.\n 2905 2906 1. Grant the non-dismissible exemption by running\n 2907 \"adb shell appops set com.android.cts.verifier android:system_exempt_from_dismissible_notifications allow\".\n 2908 2909 2. Now hit \"Go\" and you will see a notification pop up.\n 2910 2911 3. Scroll from the top to see the notification and verify you are unable to dismiss it.\n 2912 2913 4. To then remove the notification you must revoke the exemption by running\n 2914 \"adb shell appops set com.android.cts.verifier android:system_exempt_from_dismissible_notifications default\".\n 2915 2916 5. Now hit \"Go\" again and dismiss the notification.\n 2917 2918 6. Mark test as pass\n 2919 </string> 2920 <string name="provisioning_byod_always_on_vpn_prepare_button">Prepare VPN</string> 2921 <string name="provisioning_byod_always_on_vpn_vpn_not_found_note"> 2922 Can\'t find VPN app. Did you install it correctly? 2923 </string> 2924 <string name="provisioning_byod_always_on_vpn_api23">VPN app targeting SDK 23</string> 2925 <string name="provisioning_byod_always_on_vpn_api23_instruction"> 2926 1. Re-install CtsVpnFirewallAppApi23.apk (skip this if you already have the correct version 2927 installed):\n 2928 \"adb install -r --bypass-low-target-sdk-block /path/to/CtsVpnFirewallAppApi23.apk\"\n 2929 2. Tap \"Go\" button below to go to the VPN settings page.\n 2930 3. Open configuration details page for CtsVpnFirewallApp.\n 2931 4. Confirm the \"Always-on VPN\" and \"Block connections without VPN\" switches are both off 2932 and disabled.\n 2933 </string> 2934 <string name="provisioning_byod_always_on_vpn_api24">VPN app targeting SDK 24</string> 2935 <string name="provisioning_byod_always_on_vpn_api24_instruction"> 2936 1. Re-install CtsVpnFirewallAppApi24.apk (skip this if you already have the correct version 2937 installed):\n 2938 \"adb install -r /path/to/CtsVpnFirewallAppApi24.apk\"\n 2939 2. Tap \"Go\" button below to go to the VPN settings page.\n 2940 3. Open configuration details page for CtsVpnFirewallApp.\n 2941 4. Confirm\n 2942 4.1. \"Always-on VPN\" switch is enabled and in off position\n 2943 4.2. \"Block connections without VPN\" switch is disabled and in off position\n 2944 4.3. \"Block connections without VPN\" becomes enabled once the \"Always-on VPN\" switch 2945 is turned on\n 2946 </string> 2947 <string name="provisioning_byod_always_on_vpn_not_always_on">VPN app with opt-out</string> 2948 <string name="provisioning_byod_always_on_vpn_not_always_on_instruction"> 2949 1. Re-install CtsVpnFirewallAppNotAlwaysOn.apk (skip this if you already have the correct 2950 version installed):\n 2951 \"adb install -r /path/to/CtsVpnFirewallAppNotAlwaysOn.apk\"\n 2952 2. Tap \"Go\" button below to go to the VPN settings page.\n 2953 3. Open configuration details page for CtsVpnFirewallApp.\n 2954 4. Confirm the \"Always-on VPN\" and \"Block connections without VPN\" switches are both off 2955 and disabled.\n 2956 </string> 2957 <string name="provisioning_byod_select_work_challenge">Select work lock test</string> 2958 <string name="provisioning_byod_select_work_challenge_description"> 2959 This test verifies that a work lock can be chosen.\n 2960 2961 1. Verify that you get sent to the page for Choosing a new work lock.\n 2962 2. Set a new work lock. 2963 </string> 2964 <string name="provisioning_byod_confirm_work_credentials">Confirm work lock test</string> 2965 <string name="provisioning_byod_confirm_work_credentials_description"> 2966 This test verifies that work lock is shown when opening a work app, 2967 the work lock was set correctly and it is customized according to 2968 the policies set. You can only do this test after you have done the previous test.\n 2969 Before running this test press the power button to turn the screen off and then back on and 2970 swipe to unlock.\n 2971 2972 1. Open a work app.\n 2973 2. Verify that a screen asking you for your work credentials is shown.\n 2974 3. Verify that the icon is a briefcase.\n 2975 4. Verify that the header text says \"CtsVerifier\".\n 2976 5. Confirm your credentials and verify that the credentials you entered previously work.\n 2977 6. The work app should be launched. 2978 </string> 2979 <string name="provisioning_byod_confirm_work_credentials_header"> 2980 CtsVerifier 2981 </string> 2982 <string name="provisioning_byod_pattern_work_challenge">Confirm pattern lock test</string> 2983 <string name="provisioning_byod_pattern_work_challenge_description"> 2984 This test verifies that when a work pattern lock is set, a work app can open correctly.\n 2985 2986 1. Verify that you get sent to the page for Choosing a new work lock.\n 2987 2. Set a pattern lock.\n 2988 Some devices have the pattern lock option disabled and it will not show up in the list.\n 2989 If that\'s the case then mark the test as passed.\n 2990 3. Press the power button to turn the screen off and then back on and swipe to unlock.\n 2991 4. Open a work app.\n 2992 5. Verify that a screen asking you for your work credentials is shown.\n 2993 6. Confirm your credentials and verify that the credentials you entered previously work.\n 2994 7. The work app should be launched. 2995 </string> 2996 <string name="provisioning_byod_recents">Recents redaction test</string> 2997 <string name="provisioning_byod_recents_info"> 2998 This test verifies that if a work profile is locked with a separate password, Recents views 2999 for applications in the work profile are redacted. 3000 </string> 3001 <string name="provisioning_byod_recents_instructions"> 3002 This test verifies that if a work profile is locked with a separate password, Recents views 3003 for applications in the work profile are redacted.\n 3004 Some devices may not lock as soon as the screen is turned off by default. On such devices, 3005 use the button below when requested to lock the work profile. Please skip these tests if 3006 "Recents" is absent. 3007 </string> 3008 <string name="provisioning_byod_recents_lock_now">Lock now</string> 3009 3010 <string name="provisioning_byod_recents_verify_redacted"> 3011 Verify recents are redacted when locked. 3012 </string> 3013 <string name="provisioning_byod_recents_verify_redacted_instruction"> 3014 1) Follow the instructions on-screen to set a work password.\n 3015 2) Turn the screen off and on again, or use the "lock now" button, to lock the work profile.\n 3016 3) Go to home screen and then open Recents.\n 3017 4) Confirm that this "CTS Verifier" activity is shown in Recents.\n 3018 5) Confirm that the contents of the activity <b>are</b> hidden.\n 3019 6) Return to this page and pass the test. 3020 </string> 3021 <string name="provisioning_byod_recents_verify_not_redacted"> 3022 Verify recents are not redacted when unlocked. 3023 </string> 3024 <string name="provisioning_byod_recents_verify_not_redacted_instruction"> 3025 1) Press the Go button to go to security settings.\n 3026 2) Make work profile use one lock with personal profile.\n 3027 3) Open Recents.\n 3028 4) Confirm that this "CTS Verifier" activity is shown in Recents.\n 3029 5) Confirm that the contents of the activity <b>are not</b> hidden.\n 3030 6) Return to this page and pass the test. 3031 </string> 3032 <string name="provisioning_byod_recents_remove_password"> 3033 The work profile still has a separate password. Please make it use one lock with the 3034 personal profile. 3035 </string> 3036 3037 <string name="provisioning_byod_keychain">KeyChain test</string> 3038 <string name="provisioning_byod_keychain_info_start"> 3039 In this test, you\'ll verify that keys generated by KeyChain keys are as usable as keys 3040 installed into KeyChain and that they can be hidden from users.\n 3041 The test has two parts:\n 3042 1) Testing that a generated key can be selectable by the user.\n 3043 2) Testing that a generated key can be hidden from users.\n 3044 \n 3045 Tap \"Prepare Test\" button below to begin.\n 3046 </string> 3047 <string name="provisioning_byod_keychain_info_first_test"> 3048 Once you press \'Go\', a prompt titled \"Choose certificate\" should appear.\n 3049 Verify that the list in this dialog has one item, starting with \'cts-verifier-gen\'. 3050 Press \'Select\' to select it.\n 3051 If the test passes, you\'ll see the text \"Second test ready\" at the bottom.\n 3052 \n 3053 Press \'Go\'.\n 3054 </string> 3055 <string name="provisioning_byod_keychain_info_second_test"> 3056 Once you press \'Run 2nd test\', the prompt should NOT appear.\n 3057 Verify that the prompt does not appear at all.\n 3058 Mark the test as passed if the text at the bottom shows \"PASSED (2/2)\"\n 3059 </string> 3060 3061 <string name="provisioning_byod_screenshot">Work profile Screenshot Test</string> 3062 <string name="provisioning_byod_screenshot_info"> 3063 This test verifies how screenshots are saved when using work profile apps.\n 3064 \n 3065 Whenever a screenshot is taken while a work application is in the foreground,\n 3066 the resulting image should:\n 3067 \n 3068 * include only the work application\n 3069 * be saved to the work profile 3070 </string> 3071 <string name="provisioning_byod_screenshot_start"> 3072 Press \'Open Work App\', to launch an activity in the work profile.\n 3073 </string> 3074 <string name="provisioning_byod_screenshot_open">Open Work App</string> 3075 <string name="provisioning_byod_screenshot_work_app">Work App</string> 3076 <string name="provisioning_byod_screenshot_capture">Capture Screenshot</string> 3077 <string name="provisioning_byod_screenshot_verify"> 3078 Examine the screenshot image contained within the checkerboard area below.\n 3079 \n 3080 Verify the image contains only the work app and does not contain:\n 3081 \t* any other application windows\n 3082 \t* foreground status or navigation bar content (back, home, clock, battery, signal)\n 3083 \n 3084 If these conditions are met, pass the test.\n 3085 </string> 3086 <string name="provisioning_byod_screenshot_capture_title"> Take a screenshot now using the device\'s physical buttons.</string> 3087 <string name="provisioning_byod_screenshot_capture_open">Choose Screenshot</string> 3088 <string name="provisioning_byod_screenshot_capture_cancel">Cancel Test</string> 3089 <string name="provisioning_byod_screenshot_select_title">A screenshot was detected.</string> 3090 <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> 3091 3092 <!-- Strings for DeskClock --> 3093 <string name="deskclock_tests">Alarms and Timers Tests</string> 3094 <string name="deskclock_tests_info"> 3095 The Alarms and Timers tests verify that the Clock app implements the AlarmClock API properly. 3096 </string> 3097 <string name="deskclock_group_alarms">Alarms</string> 3098 <string name="deskclock_group_timers">Timers</string> 3099 3100 <string name="dc_show_alarms_test">Show Alarms Test</string> 3101 <string name="dc_show_alarms_test_info"> 3102 This test verifies that the SHOW_ALARMS API works.\n 3103 1. Press the "Show Alarms" button.\n 3104 2. Verify that a UI of the clock app is launched and displays the list of alarms\n 3105 </string> 3106 <string name="dc_show_alarms_button">Show Alarms</string> 3107 3108 <string name="dc_set_alarm_with_ui_test">Set Alarm Test</string> 3109 <string name="dc_set_alarm_with_ui_test_info"> 3110 This test verifies that the ACTION_SET_ALARM with no parameters API works.\n 3111 1. Press the "Set Alarm" button.\n 3112 2. Verify that the clock app is launched and displays a UI to manage alarms.\n 3113 </string> 3114 <string name="dc_set_alarm_button">Set Alarm</string> 3115 <string name="dc_set_alarm_verify_button">Verify</string> 3116 3117 <string name="dc_start_alarm_test">Start Alarm Test</string> 3118 <string name="dc_start_alarm_test_info"> 3119 This test verifies that the ACTION_SET_ALARM API actually starts an alarm.\n 3120 1. Press the "Start Alarm" button.\n 3121 2. Make sure the alarms UI is NOT shown\n 3122 3. Wait for the alarm to fire (may take up to 2 minutes)\n 3123 4. Verify that the alarm title is: "Start Alarm Test",\n 3124 the alarm is silent and vibrating (if the device supports vibrate).\n 3125 5. Dismiss the alarm.\n 3126 6. Verify that the alarm is not in the Clock\'s alarms list. The Verify button opens 3127 the alarm view.\n 3128 </string> 3129 <string name="dc_start_alarm_button">Start Alarm</string> 3130 3131 <string name="dc_full_alarm_test">Full Alarm Test</string> 3132 <string name="dc_full_alarm_test_info"> 3133 This test verifies that the ACTION_SET_ALARM API supports all extras.\n 3134 1. Press the "Create Alarm" button.\n 3135 2. Verify that you see one alarm with the following information:\n 3136 Name of alarm: Create Alarm Test. \n 3137 Vibrate: on. (if the device supports vibrate).\n 3138 Ringtone: silent. (if the device has a speaker).\n 3139 Time: 01:23. \n 3140 Repeating on: Monday and Wednesday. \n 3141 </string> 3142 <string name="dc_full_alarm_button">Create Alarm</string> 3143 3144 <string name="dc_set_timer_with_ui_test">Set Timer Test</string> 3145 <string name="dc_set_timer_with_ui_test_info"> 3146 This test verifies that the ACTION_SET_TIMER API with no paramters open the UI\n 3147 1. Press the "Set Timer" button.\n 3148 2. Verify that the an app is launched and displays a UI to manage timers.\n 3149 </string> 3150 <string name="dc_set_timer_with_ui_button">Set Timer</string> 3151 3152 <string name="dc_start_timer_test">Start Timer Test</string> 3153 <string name="dc_start_timer_test_info"> 3154 This test verifies that the ACTION_SET_TIMER API actually starts a timer\n 3155 1. Press the "Start Timer" button.\n 3156 2. Verify that a timer is started and NO timers UI is shown.\n 3157 3. Verify that the timer named "Start Timer Test" rings after 30 seconds. Dismiss it.\n 3158 4. Verify that the timer is deleted after the dismissal.\n 3159 </string> 3160 <string name="dc_start_timer_button">Start Timer</string> 3161 3162 <string name="dc_start_timer_with_ui_test">Start Timer With UI Test</string> 3163 <string name="dc_start_timer_with_ui_test_info"> 3164 This test verifies that the ACTION_SET_TIMER API actually starts a timer with UI\n 3165 1. Press the "Start Timer" button.\n 3166 2. Verify that a timer is started and the timers UI is shown with a timer named "Start Timer Test".\n 3167 3. Verify that the timer rings after 30 seconds.\n 3168 </string> 3169 <!-- Strings for LockConfirmBypassTest --> 3170 <string name="lock_confirm_test_title">Keyguard Password Verification</string> 3171 <string name="lock_set_button_text">Set password</string> 3172 <string name="lock_change_button_text">Change password</string> 3173 <string name="lock_confirm_message"> 3174 This test verifies that the user is prompted for the current keyguard password before prompting for a new password.\n 3175 \nClick the \"Set password\" button if you currently don\'t have a password set.\n 3176 \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. 3177 </string> 3178 3179 <!-- Strings for NFC Tests. --> 3180 <string name="nfc_tests_title">NFC Tests</string> 3181 <string name="nfc_tests_dialog_title">NFC Tests Dialog</string> 3182 <string name="nfc_tests_dialog_content"> 3183 The NFC tests.\n 3184 The DUT \"must\" be connected to a host to run these tests.\n 3185 Please follow the detailed instruction of the tests to execute scripts and get results.\n 3186 The tests will be set as passing if the DUT is not supported with NFC.\n 3187 See the instruction in the following link.\n 3188 https://source.android.com/docs/compatibility/cts/ctsv-multidevice 3189 </string> 3190 3191 <!-- String for Projection Tests --> 3192 <string name="test_category_projection">Projection Tests</string> 3193 <string name="projection_service_name">Projection Service</string> 3194 <string name="pca_info">This tests whether or not OpenGL projection works.\n 3195 You should see two "tumbling cubes." Tapping the screen should cause the cubes to explode.</string> 3196 <string name="pca_test">Projection Cube Test</string> 3197 <string name="pwa_info">This tests whether or displaying widgets and keyfocus navigation works.\n 3198 You should see four buttons on the bottom of the screen.\n 3199 Pressing the "up" and "down" buttons should highlight different buttons.\n 3200 Furthermore, the highlight should disappear when any button is touched, and the touched button should behave as usual.\n</string> 3201 <string name="pwa_test">Projection Widget Test</string> 3202 <string name="pwa_button_up">Up</string> 3203 <string name="pwa_button_down">Down</string> 3204 <string name="pwa_button">Button</string> 3205 <string name="pla_test">Projection Scrolling List Test</string> 3206 <string name="pla_info">This tests whether a projected list view will scroll properly\n 3207 You should see 50 list items and be able to scroll up and down the list</string> 3208 <string name="pva_test">Projection Video Playback Test</string> 3209 <string name="pva_info">This tests whether video playback works when projected.\n 3210 You should see a blinking white box and here a beep that is synchronized with each blink</string> 3211 <string name="pta_test">Projection Multitouch Test</string> 3212 <string name="pta_info">This tests whether multitouch works.\n 3213 Touching the screen should render a dot at the location you touched.\n 3214 Touching with additional fingers will render additoinal dots and you should be able to drag them around.</string> 3215 <string name="poa_test">Projection Offscreen Activity</string> 3216 <string name="poa_info">This tests whether a virtual display will continue to respond to and render even when the screen is off.\n 3217 Simply follow the instructions and the test will detect the pass conditions.\n 3218 Note that turning on the screen too early will result in a failure.</string> 3219 3220 <!-- Strings for RotationVectorTest and GameRotationVectorTest --> 3221 <string name="rotation_vector_test">Rotation Vector Accuracy Test</string> 3222 <string name="snsr_rotation_vector_set_reference"> 3223 Place the mobile device in a reference position. Note: to provide an accurate reference, 3224 align the device along one edge of a notebook laying on a table.</string> 3225 <string name="snsr_rotation_vector_reference_set">Reference position set.</string> 3226 <string name="snsr_rotation_vector_move_info">Move, shake, and rotate the device.</string> 3227 <string name="snsr_rotation_vector_set_final">Place the device back to the reference position.</string> 3228 <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> 3229 3230 <!-- Strings for device admin tests --> 3231 <string name="device_admin_notification">This is device admin notification</string> 3232 <string name="device_admin_keyguard_disable_camera">Disable camera</string> 3233 <string name="device_admin_keyguard_disable_camera_instruction"> 3234 Please press the Go button to lock the screen. Expected result is you cannot 3235 see the camera icon on the lower right corner of the screen, or if there is one, you cannot 3236 open the camera using it before you are asked for a password.\n 3237 Also, it shouldn\'t be possible to open the camera on the lockscreen by 3238 any other device specific gesture (such as double press on power button). 3239 </string> 3240 <string name="device_admin_disable_notifications">Disable notifications</string> 3241 <string name="device_admin_disable_notifications_instruction"> 3242 Please press the Go button to lock the screen. Wait a few seconds to see 3243 if a notification appears. Expected result is no notifications appear. 3244 You should be able to see one after unlocking. 3245 </string> 3246 <string name="device_admin_disable_unredacted_notifications">Disable unredacted notifications</string> 3247 <string name="device_admin_disable_unredacted_notifications_instruction"> 3248 Please press the Go button to lock the screen. Wait a few seconds to see 3249 if a notification appears. Expected result is a notification appear with 3250 its content hidden. You should be able to see the content after unlocking. 3251 </string> 3252 3253 <!-- Strings common for BYOD and DO managed provisioning tests. --> 3254 <string name="afw_device_admin">CTS Verifier</string> 3255 3256 <string name="provisioning_tests_byod">BYOD Provisioning tests</string> 3257 3258 <string name="provisioning_tests_byod_custom_terms">Custom terms</string> 3259 <string name="provisioning_tests_byod_custom_terms_instructions"> 3260 1. Please press the Go button to start the provisioning.\n 3261 2. Click \"View Terms\" button\n 3262 3. Expand \"Company ABC\" section. Verify the section content is \"Company Terms Content.\"\n 3263 4. Then hit back twice and stop the provisioning. 3264 </string> 3265 <string name="provisioning_tests_byod_custom_term_header1">Company ABC</string> 3266 3267 <!-- Strings for BYOD managed provisioning (ByodFlowTestActivity) --> 3268 <string name="test_category_managed_provisioning">Managed Provisioning</string> 3269 <string name="provisioning_byod">BYOD Managed Provisioning</string> 3270 <string name="provisioning_byod_info"> 3271 This test exercises the BYOD managed provisioning flow. 3272 Start by pressing the button on screen and follow instructions to finish the managed provisioning process. 3273 If your device has not been encrypted before, it will be encrypted and rebooted. 3274 After the provisioning process completes, return to this page and carry out further verifications. 3275 Note: the device will remain encrypted after the test which can only be disabled by factory reset. 3276 </string> 3277 <string name="provisioning_byod_start">Start BYOD provisioning flow</string> 3278 <string name="provisioning_byod_instructions"> 3279 1. Press the button below to start the managed provisioning flow. 3280 If your device has not been encrypted before, it will reboot to apply encryption. 3281 After reboot follow instructions in the notification area to complete the provisioning.\n 3282 2. After successful provisioning, come back to this page. You might need to press a button on the final provisioning screen. 3283 Please press through the following verification steps. 3284 Allow a few seconds after returning from provisioning, as the profile owner test should automatically pass.\n 3285 \n 3286 If the device is being encrypted during step 1, it will remain encrypted After this test. 3287 The only way to disable the encryption is to factory reset the device. 3288 </string> 3289 <string name="provisioning_byod_profileowner">Profile owner installed</string> 3290 <string name="provisioning_byod_disk_encryption">Full disk encryption enabled</string> 3291 <string name="provisioning_byod_disk_encryption_default_key_toast"> 3292 Cannot secure device with screen lock. Please re-run the test if you forgot to select 3293 the \"require PIN to boot\" option. 3294 </string> 3295 <string name="provisioning_byod_disk_encryption_no_pin_toast"> 3296 No PIN is detected. Please re-run the test if you forgot to set a PIN. 3297 </string> 3298 <string name="provisioning_byod_set_screen_lock_dialog_message"> 3299 Next, you will be asked to set a screen lock for the device.\n 3300 \n 3301 Please set \"1111\" as the new PIN (or any other PIN that you can memorize). 3302 You have to enter this PIN again later in order to finish the test.\n 3303 \n 3304 You may be asked whether the PIN should be required to boot the device. Please answer yes.\n 3305 \n 3306 Tap Go button to set a new screen lock. 3307 </string> 3308 <string name="provisioning_byod_remove_screen_lock_dialog_message"> 3309 The test is almost finished. \n 3310 \n 3311 Next, you will be asked to remove the screen lock that you just set. Please enter \"1111\" 3312 (or your own PIN) when prompted for the old PIN, and do not set any new screen lock. This 3313 is to make sure that the device returns to the initial state after this test.\n 3314 \n 3315 Tap Go button to remove existing screen lock. 3316 </string> 3317 <string name="provisioning_byod_workapps_visible">Badged work apps visible in Launcher</string> 3318 <string name="provisioning_byod_cross_profile_from_personal">Open app cross profiles from the personal side</string> 3319 <string name="provisioning_byod_cross_profile_from_work">Open app cross profiles from the work side</string> 3320 <string name="provisioning_app_linking">App links from the work side</string> 3321 <string name="provisioning_byod_cross_profile_app_personal">You selected the personal option.</string> 3322 <string name="provisioning_byod_cross_profile_app_work">You selected the Work option.</string> 3323 <string name="provisioning_byod_cross_profile_app_ctsverifier"> You selected the ctsverifier option </string> 3324 <string name="provisioning_byod_cross_profile_from_personal_instruction"> 3325 Please press the Go button to start an action.\n 3326 \n 3327 You should be asked to choose either \"CTS Verifier\" or \"Work\" to complete the action. 3328 Pressing either should bring up a page stating your choice.\n 3329 \n 3330 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 3331 </string> 3332 <string name="provisioning_byod_cross_profile_from_work_instruction"> 3333 Please press the Go button to start an action.\n 3334 \n 3335 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action. 3336 Pressing either should bring up a page stating your choice.\n 3337 \n 3338 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 3339 </string> 3340 <string name="provisioning_byod_cross_profile_permission_control">Cross profile permission control</string> 3341 <string name="provisioning_byod_cross_profile_permission_control_info"> 3342 This test exercises cross profile permission controls. Follow instructions above. 3343 </string> 3344 <string name="provisioning_byod_cross_profile_permission_control_instruction"> 3345 For this test you need to install CrossProfileTestApp.apk by running 3346 adb install -r -t /path/to/CrossProfileTestApp.apk. Make sure the app is installed 3347 on both the personal and work profiles.\n 3348 Press the \"Prepare test\" button to enable configuring cross profile for the test app.\n 3349 Then press through the following verification steps.\n 3350 Mark the test as passed if all the following test cases are verified. 3351 </string> 3352 <string name="provisioning_byod_cross_profile_permission_control_prepare_button">Prepare test</string> 3353 <string name="provisioning_byod_cross_profile_permission_disabled_by_default">Cross profile permission disabled by default</string> 3354 <string name="provisioning_byod_cross_profile_permission_disabled_by_default_instruction"> 3355 Press the Go button to go to Settings > Apps & notifications > Special app access >\n 3356 Connected work and personal apps.\n 3357 Choose the \"Cross profile test app\" from the list and check that the switch is disabled.\n 3358 Go back to CTS Verifier and mark the test as \"Pass\" or \"Fail\". 3359 </string> 3360 <string name="provisioning_byod_cross_profile_permission_enabled">Cross profile permission enabled</string> 3361 <string name="provisioning_byod_cross_profile_permission_enabled_instruction"> 3362 Press the Go button to open the \"Cross Profile Test App\".\n 3363 Press the \"Open Settings\" button to go to Settings > Apps & notifications > Special app access > 3364 Connected work and personal apps > Cross profile test app, then enable the switch.\n 3365 Verify that when you go back it takes you to the \"Cross Profile Test App\".\n 3366 Now verify that it shows \"INTERACTING ACROSS PROFILES ALLOWED\" message.\n 3367 Go back to CTS Verifier and mark the test as \"Pass\" or \"Fail\". 3368 </string> 3369 <string name="provisioning_byod_cross_profile_permission_disabled">Cross profile permission disabled</string> 3370 <string name="provisioning_byod_cross_profile_permission_disabled_instruction"> 3371 Press the Go button to open the \"Cross Profile Test App\".\n 3372 Press the \"Open Settings\" button to go to Settings > Apps & notifications > Special app access > 3373 Connected work and personal apps > Cross profile test app, then disable the switch.\n 3374 Verify that when you go back it takes you to the \"Cross Profile Test App\".\n 3375 Now verify that it shows \"INTERACTING ACROSS PROFILES NOT ALLOWED\" message.\n 3376 Go back to CTS Verifier and mark the test as \"Pass\" or \"Fail\". 3377 </string> 3378 <string name="provisioning_byod_app_linking_instruction"> 3379 Please press the Go button to start an action.\n 3380 \n 3381 You should be asked to choose either \"CTS Verifier\" or \"Personal\" to complete the action.\n 3382 - If you choose \"CTS Verifier\", you should see a page stating your chose \"CTS Verifier\".\n 3383 - If you choose \"Personal\", you should be presented with another dialog between \"CTS Verifier\" 3384 and some other apps. In this case, you should choose \"CTS verifier\".\n 3385 You should then see a page stating you chose \"Personal\".\n 3386 \n 3387 Verify that you are prompted with the above choices and both options work as intended. Then mark this test accordingly. 3388 </string> 3389 <string name="provisioning_byod_keyguard_disabled_features">Keyguard disabled features</string> 3390 <string name="provisioning_byod_keyguard_disabled_features_info"> 3391 This test exercises Keyguard Disabled Features. Follow instructions above. 3392 </string> 3393 <string name="provisioning_byod_keyguard_disabled_features_instruction"> 3394 Please go to Settings > Security > Device administrators and set 3395 \"CTS Verifier\" as active admin.\n 3396 After that please go to Settings > Security > Screen lock and set 3397 your screen lock password to \"testpassword\".\n 3398 Then please press the \"Prepare test\" button to disable trust agents.\n 3399 Then please press through the following verification steps.\n 3400 Note: After leaving the screen active admin status will be cleared. 3401 Please go to Settings > Security > Screen lock and set your 3402 password type to \"None\". 3403 </string> 3404 <string name="provisioning_byod_keyguard_disabled_features_prepare_button">Prepare test</string> 3405 <string name="provisioning_byod_keyguard_disabled_features_not_admin">CtsVerifier is not active admin. Please follow instructions.</string> 3406 <string name="provisioning_byod_disable_trust_agents">Disable trust agents</string> 3407 <string name="provisioning_byod_disable_trust_agents_instruction"> 3408 Please press the Go button to go to Settings > Security. Then go to Trusted agents and\n 3409 check if the agents are shown as disabled by the administrator. 3410 Then please press Back and mark the test as \"Pass\" or \"Fail\". 3411 </string> 3412 <string name="provisioning_byod_fingerprint_disabled_in_settings">Fingerprint is disabled in Settings</string> 3413 <string name="provisioning_byod_fingerprint_disabled_in_settings_instruction"> 3414 Please press the Go button to go to Settings > Security. Then go to Fingerprint and\n 3415 check if the disclaimer at the bottom of screen is altered to warn the users for\n 3416 fingerprint being disabled in lock screen. Then please press Back and mark the \n 3417 test as \"Pass\" or \"Fail\". 3418 </string> 3419 <string name="provisioning_byod_disable_fingerprint">Fingerprint disabled on keyguard</string> 3420 <string name="provisioning_byod_disable_fingerprint_instruction"> 3421 Please press the Go button to lock the screen. Then try to log in using the fingerprint reader.\n 3422 Expected result is you cannot log in using your fingerprint.\n 3423 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\". 3424 </string> 3425 <string name="provisioning_byod_disable_unredacted_notifications">Unredacted notifications disabled on keyguard</string> 3426 <string name="provisioning_byod_disable_unredacted_notifications_instruction"> 3427 Please press the Go button to lock the screen. Wait a couple of seconds and look out for a 3428 notification from CtsVerifier.\n 3429 Expected result is the notification is shown as \"Contents hidden by policy\", you can not see the contents 3430 (Which would read \"This is a notification\"). You should be seeing a work badge.\n 3431 After you log back in, please navigate back to CtsVerifier and mark the test as \"Pass\" or \"Fail\". 3432 </string> 3433 <string name="provisioning_byod_notification_title">This is a notification</string> 3434 <string name="provisioning_byod_notification_public_title">Contents hidden by policy</string> 3435 3436 <string name="provisioning_byod_disallow_apps_control">Disallow apps control</string> 3437 <string name="provisioning_byod_disallow_apps_control_info"> 3438 This test exercises Disallow Apps Control. Follow instructions above. 3439 </string> 3440 <string name="provisioning_byod_disallow_apps_control_instruction"> 3441 Please press the \"Prepare test\" button to disallow apps control for managed apps.\n 3442 Then please press through the following verification steps.\n 3443 Note: After leaving the screen disallow apps control restriction will be cleared. 3444 </string> 3445 <string name="provisioning_byod_disallow_apps_control_prepare_button">Prepare test</string> 3446 <string name="provisioning_byod_disabled_uninstall_button">Disabled uninstall button</string> 3447 <string name="provisioning_byod_disabled_uninstall_button_instruction"> 3448 Please press the Go button to go to Settings > Apps. 3449 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3450 Choose a managed app. Check that performing either \"Uninstall\" or \"Disable\" is not possible and triggers a support message when trying to do so. 3451 Then please press Back (or navigate back to this app using Recents) and mark the test as \"Pass\" or \"Fail\". 3452 </string> 3453 <string name="provisioning_byod_disabled_force_stop_button">Disabled force stop button</string> 3454 <string name="provisioning_byod_disabled_force_stop_button_instruction"> 3455 Please press the Go button to go to Settings > Apps. 3456 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3457 Choose a managed app. Check that performing \"Force stop\" is not possible and triggers a support message when trying to do so. 3458 Then please press Back (or navigate back to this app using Recents) and mark the test as \"Pass\" or \"Fail\". 3459 </string> 3460 <string name="provisioning_byod_disabled_app_storage_buttons">Disabled app storage buttons</string> 3461 <string name="provisioning_byod_disabled_app_storage_buttons_instruction"> 3462 Please press the Go button to go to Settings > Apps. 3463 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3464 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. 3465 Note: if an app has no data then tapping the clear data button has no effect anyway. Make sure you have selected 3466 the badged version of app with non-zero app data. Badged \"Settings\" may be a good candidate. 3467 Then please press Back (or navigate back to this app using Recents) and mark the test as \"Pass\" or \"Fail\". 3468 </string> 3469 3470 <string name="provisioning_byod_work_status_toast">Work status toast is displayed</string> 3471 <string name="provisioning_byod_work_status_toast_instruction"> 3472 Please press the Go button to launch a work activity. 3473 \n\n 3474 Follow instructions and then return and mark this test accordingly. 3475 </string> 3476 <string name="provisioning_byod_work_status_toast_activity"> 3477 Turn off the screen and wait a few seconds then turn on the screen again. 3478 \n\n 3479 Verify that a toast was displayed saying you are in the work profile. 3480 \n\n 3481 Please press finish to return to the tests and then mark this test accordingly. 3482 </string> 3483 <string name="provisioning_byod_user_settings">Profile-aware user settings</string> 3484 <string name="provisioning_byod_user_settings_instruction"> 3485 Please press the Go button to open the Settings page. 3486 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher.)\n 3487 Navigate to Accounts and confirm that:\n 3488 - 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 3489 - De-selecting either option prompts a warning dialog.\n 3490 \n 3491 Use the Back button (or navigate back to this app using Recents) to return to this page. 3492 </string> 3493 <string name="provisioning_byod_workapps_visible_instruction"> 3494 Please press the Go button to start the launcher. 3495 Go to All Apps screen and scroll through it to confirm that:\n 3496 \n 3497 - A new set of work apps including CTS Verifier appear in the list.\n 3498 - Work badge overlay appears on work app\'s icon (see example icon below, color and style may vary).\n 3499 - The work badge overlay has the same size and position on each work app\'s icon. 3500 \n 3501 Then navigate back to this screen using Recents button. 3502 </string> 3503 3504 <string name="provisioning_byod_app_settings">Profile-aware app settings</string> 3505 <string name="provisioning_byod_app_settings_instruction"> 3506 Please press the Go button to open Apps page in settings. 3507 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3508 \n 3509 Verify that Personal and Work exists in the dropdown list(or UI has Personal and Work tab). When selecting Work it will 3510 bring up apps setting in the work profile.\n 3511 \n 3512 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3513 </string> 3514 3515 <string name="provisioning_byod_location_settings">Profile-aware location settings</string> 3516 <string name="provisioning_byod_location_settings_instruction"> 3517 Please press the Go button to open Location page in settings. 3518 (If this device has a separate app for work settings, ignore the Go button and navigate to that app manually, if necessary).\n 3519 \n 3520 Verify that work profile entry exists in the page(or in Work tab) and it has a toggleable switch.\n 3521 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 3522 Then switch the main location switch on again. You should see the work profile location switch go enabled and into its previous state.\n 3523 \n 3524 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3525 </string> 3526 <string name="provisioning_byod_location_failed">Failed to obtain location from any provider</string> 3527 <string name="provisioning_byod_location_no_provider">Cannot obtain location: no providers available.</string> 3528 <string name="provisioning_byod_location_trying">Trying to obtain location using providers: %1$s</string> 3529 <string name="provisioning_byod_location_obtained">Location has been obtained.</string> 3530 <string name="provisioning_byod_pass_message">PASS: %1$s</string> 3531 <string name="provisioning_byod_fail_message">FAIL: %1$s</string> 3532 <string name="provisioning_byod_location_test_activity">Location listener</string> 3533 <string name="provisioning_byod_location_checker_activity">Location checker</string> 3534 3535 3536 <string name="provisioning_byod_wifi_data_usage_settings">Profile-aware data usage settings (Wi-Fi)</string> 3537 <string name="provisioning_byod_wifi_data_usage_settings_instruction"> 3538 Please press the Go button to open the Settings page. 3539 (If this device has a separate app for work settings, ignore the Go button and navigate to that app manually).\n 3540 \n 3541 Navigate to the \"Network & Internet\" page and then click on \"Wi-Fi\" and then \"Wi-Fi data usage\".\n 3542 Confirm that \"All work apps\" section is present and that it is possible to see the data usage for work (badged) apps.\n 3543 (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 3544 \n 3545 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3546 </string> 3547 3548 <string name="provisioning_byod_cellular_data_usage_settings">Profile-aware data usage settings (Mobile)</string> 3549 <string name="provisioning_byod_cellular_data_usage_settings_instruction"> 3550 Please disable Wi-Fi connection on your device.\n 3551 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 3552 Please carry out operations that will use mobile data using both badged and unbadged apps (e.g. visit a page in a browser).\n 3553 \n 3554 Please press the Go button to open the Settings page. 3555 (If this device has a separate app for work settings, ignore the Go button and navigate to that app manually).\n 3556 \n 3557 Navigate to the \"Network & Internet\" page and then click on \"Mobile network\" and then \"App data usage\".\n 3558 Confirm that \"All work apps\" section is present and that it is possible to see the data usage for work (badged) apps.\n 3559 \n 3560 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3561 </string> 3562 3563 <string name="provisioning_byod_cred_settings">Profile-aware trusted credential settings</string> 3564 <string name="provisioning_byod_cred_settings_instruction"> 3565 Please press the Go button to open the Security settings. 3566 Navigate to "Trusted credentials" and wait for the UI to load. 3567 After the list is loaded, confirm that:\n 3568 \n 3569 The page list credentials for both "Personal" and "Work" profiles.\n 3570 \n 3571 Then use the Back button to return to this test and mark accordingly. 3572 </string> 3573 3574 <string name="provisioning_byod_print_settings">Profile-aware printing settings</string> 3575 <string name="provisioning_byod_print_settings_instruction"> 3576 Please press the Go button to open the Printing settings. 3577 (If this device has a separate app for work settings, ignore the Go button and open that app manually from the launcher).\n 3578 \n 3579 Verify that work profile exists in the dropdown list and selecting it will 3580 bring up printing setting in the work profile.\n 3581 \n 3582 Then use the Back button (or navigate back to this app using Recents) to return to this test and mark accordingly. 3583 </string> 3584 3585 <string name="provisioning_byod_cross_profile_intent_filters">Cross profile intent filters are set</string> 3586 3587 <string name="test_failed_cannot_start_intent">Cannot start the given intent.</string> 3588 <string name="provisioning_byod_no_activity">Cannot communicate with activity in the work profile.</string> 3589 <string name="provisioning_byod_delete_profile">Initiate deletion of work profile.</string> 3590 <string name="provisioning_byod_profile_deleted">Work profile deleted.</string> 3591 <string name="provisioning_byod_disabled">Device provisioning is not enabled.</string> 3592 <string name="provisioning_button_finish">Finish</string> 3593 <string name="provisioning_cross_profile_chooser">Choose an app to complete action</string> 3594 3595 <string name="provisioning_byod_no_gps_location_feature">No GPS feature present. Skip test.</string> 3596 <string name="provisioning_byod_location_mode_enable">Enable location</string> 3597 <string name="provisioning_byod_location_mode_enable_missing_permission">Permission missing</string> 3598 <string name="provisioning_byod_location_mode_enable_instruction"> 3599 This test verifies that the location can be enabled for the managed profile apps.\n 3600 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 3601 2. Return using back button and press Go button to check if location is available. If prompted, accept the location permission.\n 3602 3. Check the result message below and mark the test accordingly.\n 3603 \n 3604 If the test fails to obtain location, try to enable as many location services as possible and move outside to make GPS work. 3605 </string> 3606 3607 <string name="provisioning_byod_location_mode_disable">Disable location</string> 3608 <string name="provisioning_byod_location_mode_time_out_toast">Timeout waiting for gps location change</string> 3609 <string name="provisioning_byod_location_mode_disable_instruction"> 3610 This test verifies that the location can be disabled for the managed profile apps through the main location switch.\n 3611 1. Press the \"Prepare Test\" button to go to the location settings page, set the main location switch disabled.\n 3612 2. Return using back button and press Go button to check if location is available. If prompted, accept the location permission.\n 3613 3. Check the result message below and mark the test accordingly.\n 3614 </string> 3615 3616 <string name="provisioning_byod_work_location_mode_disable">Disable location for work profile</string> 3617 <string name="provisioning_byod_work_location_mode_disable_instruction"> 3618 This test verifies that the location can be disabled for the managed profile apps through work profile location switch.\n 3619 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 3620 2. Return using back button and press Go button to check if location is available. If prompted, accept the location permission.\n 3621 3. Check the result message below and mark the test accordingly.\n 3622 </string> 3623 <string name="provisioning_byod_primary_location_when_work_disabled">Primary receives updates while work location is disabled</string> 3624 <string name="provisioning_byod_primary_location_when_work_disabled_instruction"> 3625 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 3626 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 3627 2. Return using back button and press Go button to check if location is available. If prompted, accept the location permission.\n 3628 3. Check the result message below and mark the test accordingly.\n 3629 \n 3630 If the test fails to obtain location, try to enable as many location services as possible and move outside to make GPS work. 3631 </string> 3632 3633 <string name="provisioning_byod_personal_ringtones">Personal ringtones</string> 3634 <string name="provisioning_byod_personal_ringtones_instruction"> 3635 This test verifies that personal ringtones can be changed independently of work profile ringtones.\n 3636 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 3637 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 3638 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 3639 corresponding work profile setting."\n 3640 4. Verify that the work sounds are different to the personal values just set.\n 3641 5. Go back to the cts-verifier tests using the back button, then mark the test accordingly.\n 3642 </string> 3643 3644 <string name="provisioning_byod_uninstall_work_app">Uninstall work app from launcher</string> 3645 <string name="provisioning_byod_uninstall_work_app_instruction"> 3646 This test verifies that work profile apps can be uninstalled.\n 3647 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 3648 make NotificationBot\n 3649 2. Upload the NotificationBot.apk to your device by issuing the following command on the host:\n 3650 adb push /path/to/NotificationBot.apk /data/local/tmp/\n 3651 3. Pres \"Go\" to install NotificationBot.apk on your work profile.\n 3652 4. If you are presented with a dialog to allow installing of unknown apps, enable that option.\n 3653 5. Go to home screen.\n 3654 6. Verify that the newly installed app, \"CTS Robot\", can successfully be uninstalled from the launcher.\n 3655 </string> 3656 <string name="provisioning_byod_uninstall_work_app_install_work_app">Install work app</string> 3657 3658 <string name="provisioning_byod_launch_work_tab">Launch work tab in launcher</string> 3659 <string name="provisioning_byod_launch_work_tab_instruction"> 3660 This test verifies that the work tab (if tabs are supported) can be launched.\n 3661 1. Press \"Go\".\n 3662 2. If this device supports tabs, verify that you have landed on the work tab.\n 3663 3. If this device doesn\'t support tabs, verify that you have landing on the all apps page .\n 3664 </string> 3665 3666 <string name="provisioning_byod_turn_off_work">Turn off work profile</string> 3667 <string name="provisioning_byod_turn_off_work_info">This test verifies device behaviors when turning off work profile.</string> 3668 <string name="provisioning_byod_turn_off_work_instructions"> 3669 This test verifies the device behavior when work profile is turned off.\n 3670 Please exercise the following tests in sequence.\n 3671 The button below can be used to open the Settings page where you can toggle work profile.\n 3672 (If this device has a separate app for work settings, ignore the button and open that app manually from the launcher).\n 3673 </string> 3674 <string name="provisioning_byod_turn_off_work_prepare_button">Open Settings to toggle work profile</string> 3675 3676 <string name="provisioning_byod_turn_off_work_prepare_notifications">Prepare a work notification</string> 3677 <string name="provisioning_byod_turn_off_work_prepare_notifications_instruction"> 3678 This is a test setup step.\n 3679 1. Press the go button to send a work notification. (if a permission is requested, grant it and press the go button again). \n 3680 2. Verify that the notification is displayed and mark this test as passed.\n 3681 (Note: in the following test, you will be asked to verify the notification disappears after work profile is turned off.) 3682 </string> 3683 3684 <string name="provisioning_byod_turn_off_work_turned_off">Please turn off work profile</string> 3685 <string name="provisioning_byod_turn_off_work_turned_off_toast">Open settings to turn off work profile, using the button above.</string> 3686 3687 <string name="provisioning_byod_turn_off_work_notifications">Notifications when work profile is off</string> 3688 <string name="provisioning_byod_turn_off_work_notifications_instruction"> 3689 Verify that the previously-shown work notification has now disappeared. 3690 </string> 3691 3692 <string name="provisioning_byod_turn_off_work_launcher">Starting work apps when work profile is off</string> 3693 <string name="provisioning_byod_turn_off_work_launcher_instruction"> 3694 This test verifies that work applications cannot be started if work profile is off.\n 3695 1. Open settings to turn work profile back on, either manually or using the "Open Settings to toggle work" on the previous page.\n 3696 2. Add a work app to your home screen.\n 3697 3. Turn work profile off from Settings.\n 3698 4. Press home to go to the launcher.\n 3699 5. Verify that the work app is greyed out.\n 3700 6. Tap on the work app.\n 3701 7. Verify that the application does not start.\n 3702 </string> 3703 3704 <string name="provisioning_byod_turn_off_work_turned_on">Please turn work profile back on</string> 3705 <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> 3706 3707 <string name="provisioning_byod_turn_on_work_icon">Status bar icon when work profile is on</string> 3708 <string name="provisioning_byod_turn_on_work_icon_instruction"> 3709 Now that work profile is back on, please verify that the status bar icon for work profile off is no longer visible. 3710 </string> 3711 3712 <string name="provisioning_byod_turn_on_work_launcher">Starting work apps when work profile is on</string> 3713 <string name="provisioning_byod_turn_on_work_launcher_instruction"> 3714 Now that work profile is back on, please go to the launcher and verify that you can start a work application. 3715 </string> 3716 3717 <string name="provisioning_byod_organization_info">Organization Info</string> 3718 <string name="provisioning_byod_organization_name_hint">Name</string> 3719 <string name="provisioning_byod_set_organization_info_button_text">Set</string> 3720 <string name="provisioning_byod_organization_info_instructions"> 3721 This test verifies that the Organization Info was set correctly. 3722 You can only do this test after you have done "select work lock" test.\n 3723 1. Enter your organization name.\n 3724 2. Press the Set button to set organization Info.\n 3725 3. Press the Go button to open a dialog to confirm work credentials.\n 3726 (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 3727 4. Verify that the header text has organization name as set by you.\n 3728 </string> 3729 3730 <string name="provisioning_byod_no_secure_lockscreen">No work lockscreen password set. Please run \"Select work lock test\" and rerun this test</string> 3731 3732 <string name="provisioning_byod_parent_profile_password">Personal password test</string> 3733 <string name="provisioning_byod_parent_profile_password_description"> 3734 This test verifies that the password on the personal side can be chosen from within a managed profile.\n 3735 3736 1. Press the Go button to set a new password for the personal side.\n 3737 2. Lock and unlock the screen to verify that the personal side password was set correctly.\n 3738 </string> 3739 <string name="provisioning_byod_work_profile_widget">Work profile widget</string> 3740 <string name="provisioning_byod_work_profile_widget_info">Verify that work profile widget can be added into launcher</string> 3741 <string name="provisioning_byod_work_profile_widget_description"> 3742 This test verifies that the widget in work profile can be added into Launcher.\n 3743 3744 1. Go to home screen.\n 3745 2. Add the widget titled \"CTS Verifier\" and badged with work profile briefcase to the home screen.\n 3746 3. If you can add the widget to the home screen, please select \"pass\". Otherwise, select \"fail\". 3747 </string> 3748 3749 <!-- Strings for DeviceOwnerNegativeTestActivity --> 3750 <string name="negative_device_owner">No Device Owner Tests</string> 3751 <string name="device_owner_negative_category">No Device Owner Tests</string> 3752 <string name="device_owner_provisioning_negative">Device owner provisioning</string> 3753 <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> 3754 <string name="start_device_owner_provisioning_button">Start provisioning</string> 3755 <string name="enterprise_privacy_quick_settings_negative">Quick settings disclosure</string> 3756 <string name="enterprise_privacy_quick_settings_negative_info"> 3757 Please do the following:\n 3758 1) Open and fully expand Quick Settings.\n 3759 2) Verify that at the bottom of Quick Settings, you are not told the device is managed.\n 3760 3) Close Quick Settings.\n 3761 \n 3762 If this device does not have quick settings, please skip this test and mark it passing 3763 </string> 3764 <string name="enterprise_privacy_keyguard_negative">Keyguard disclosure</string> 3765 <string name="enterprise_privacy_keyguard_negative_info"> 3766 Please do the following:\n 3767 1) Press the Go button to open Settings.\n 3768 2) Navigate to \"Security\" > \"Screen lock\" and select the first screen lock type that is not \"None\".\n 3769 3) Use the Back button to return to this page.\n 3770 4) Lock the device.\n 3771 5) Verify that on the lock screen, you are not told the device is managed.\n 3772 6) Unlock the device.\n 3773 7) Repeat steps (1) through (6) for each screen lock type other than \"None\". 3774 </string> 3775 <string name="enterprise_privacy_add_account_negative">Add account disclosure</string> 3776 <string name="enterprise_privacy_add_account_negative_info"> 3777 Please do the following:\n 3778 1) Press the Go button to open Settings.\n 3779 2) In the screen that opens, verify that you are not told that the device is managed.\n 3780 3) Use the Back button to return to this page. 3781 </string> 3782 3783 <!-- Strings for DeviceOwnerPositiveTestActivity --> 3784 <string name="positive_device_owner">Device Owner Tests</string> 3785 <string name="device_owner_positive_tests">Device Owner positive tests</string> 3786 <string name="device_owner_positive_tests_instructions"> 3787 The positive device owner tests verify policies on a corporate owned device.\n 3788 Press below button first, follow steps described in the dialog that pops up, 3789 then proceed to the test cases.\n 3790 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 3791 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 3792 be run last so that it does not interfere with other tests. 3793 </string> 3794 <string name="device_owner_positive_tests_info"> 3795 The positive device owner tests verify policies on a corporate owned device.\n 3796 Press below button first, follow steps described in the dialog that pops up, 3797 then proceed to the test cases.\n 3798 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 3799 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 3800 be run last so that it does not interfere with other tests. 3801 </string> 3802 <string name="device_owner_positive_category">Device Owner Tests</string> 3803 <string name="set_device_owner_button_label">Set up device owner</string> 3804 <string name="set_device_owner_dialog_title">Set up device owner</string> 3805 <string name="grant_headless_system_user_permissions"> 3806 For this test you need to grant some permissions to CtsVerifier by running\n 3807 adb shell pm grant --user current com.android.cts.verifier android.permission.INTERACT_ACROSS_USERS\n 3808 adb shell pm grant --user 0 com.android.cts.verifier android.permission.INTERACT_ACROSS_USERS\n 3809 adb shell am compat enable ALLOW_TEST_API_ACCESS com.android.cts.verifier\n\n 3810 </string> 3811 <string name="set_device_owner_dialog_text"> 3812 For this test you need to install CtsEmptyDeviceOwner.apk by running\n 3813 adb install -r -t /path/to/CtsEmptyDeviceOwner.apk\n 3814 Then you need to set this app as the device owner by running\n 3815 adb shell dpm set-device-owner --user 0 com.android.cts.emptydeviceowner/.EmptyDeviceAdmin 3816 </string> 3817 <string name="set_device_owner_headless_dialog_text"> 3818 For this test you need to set the device owner by running\n 3819 adb shell dpm set-device-owner --user 0 com.android.cts.verifier/.managedprovisioning.DeviceAdminTestReceiver 3820 </string> 3821 <string name="device_owner_remove_device_owner_test">Remove device owner</string> 3822 <string name="device_owner_remove_device_owner_test_info"> 3823 Please press the Go button to check whether CTSVerifier is Device Owner. Then press the Remove Device Owner button, 3824 and check that CTSVerifier is NOT Device Owner anymore. 3825 </string> 3826 <string name="remove_device_owner_button">Remove device owner</string> 3827 <string name="device_owner_check_device_owner_test">Check device owner</string> 3828 <string name="device_owner_check_profile_owner_test">Check profile owner</string> 3829 <string name="device_owner_check_user_affiliation_test">Check user affiliation</string> 3830 <string name="device_owner_incorrect_device_owner">Missing or incorrect device owner: CTSVerifier is not DO for user %1$d!</string> 3831 <string name="device_owner_incorrect_profile_owner">Missing or incorrect profile owner: CTSVerifier is not PO for user %1$d!</string> 3832 <string name="device_owner_user_not_affiliated">User %1$d! is not affiliated</string> 3833 <string name="device_owner_wifi_lockdown_test">WiFi configuration lockdown</string> 3834 <string name="device_owner_wifi_lockdown_info"> 3835 Please enter the SSID and auth method of an available WiFi Access Point and press the button to create a 3836 WiFi configuration. This configuration must NOT EXIST yet (you can use Settings > WiFi to verify - if it exists, 3837 then select the option to forget it). If the Wifi requires a password, wait for the \'Could not connect to the wifi network\' 3838 notification, tap the notification, set the password and connect to the network. 3839 The test cases are going to use this config. Please go through test cases in order (from top to bottom). 3840 </string> 3841 <string name="switch_wifi_lockdown_off_button">WiFi config lockdown off</string> 3842 <string name="switch_wifi_lockdown_on_button">WiFi config lockdown on</string> 3843 <string name="wifi_lockdown_go_settings_wifi_button">Go to WiFi Settings</string> 3844 <string name="device_owner_wifi_key_management_none_button">None</string> 3845 <string name="device_owner_wifi_key_management_wpa_button">WPA</string> 3846 <string name="device_owner_wifi_key_management_wep_button">WEP</string> 3847 <string name="create_wifi_config_button_label">Create WiFi configuration</string> 3848 <string name="wifi_lockdown_add_network_failed_dialog_title">WiFi configuration could not be created</string> 3849 <string name="wifi_lockdown_add_network_failed_dialog_text"> 3850 There was an error during creation of WiFi configuration. Check if WiFi is switched on. 3851 </string> 3852 <string name="device_owner_wifi_config_unlocked_modification_test">Unlocked config is modifiable in Settings</string> 3853 <string name="device_owner_wifi_config_unlocked_modification_test_info"> 3854 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 3855 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be edited. 3856 Please make sure you can connect to it. The test is successful if the config is editable 3857 and can be connected to. 3858 </string> 3859 <string name="device_owner_wifi_config_unlocked_modification_test_info" product="automotive"> 3860 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 3861 Settings > WiFi and see if the CTSVerifier created WiFi configuration is editable 3862 (it\'s ok if it\'s not editable, but then take note so the next test can be skipped). 3863 Please make sure you can connect to it. The test is successful if the config can be 3864 connected to. 3865 </string> 3866 <string name="device_owner_wifi_config_locked_modification_test">Locked config is not modifiable in Settings</string> 3867 <string name="device_owner_wifi_config_locked_modification_test_info"> 3868 Please press the button to ensure WiFi config lockdown is in effect. Then go to 3869 Settings > WiFi and see if the CTSVerifier created WiFi configuration can NOT be edited 3870 or removed. The test is successful if the config is NOT modifiable. 3871 </string> 3872 <string name="device_owner_wifi_config_locked_modification_test_info" product="automotive"> 3873 NOTE: if the WiFi was not editable in the previous step, please skip this test. 3874 Please press the button to ensure WiFi config lockdown is in effect. Then go to 3875 Settings > WiFi and see if the CTSVerifier created WiFi configuration can NOT be edited 3876 or removed. The test is successful if the config is NOT modifiable. 3877 </string> 3878 <string name="device_owner_wifi_config_locked_connection_test">Locked config can be connected to</string> 3879 <string name="device_owner_wifi_config_locked_connection_test_info"> 3880 Please press the button to ensure WiFi config lockdown is in effect. Then go to 3881 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be connected 3882 to manually. The test is successful if the connection can be established. 3883 </string> 3884 <string name="device_owner_wifi_config_unlocked_removal_test">Unlocked config can be forgotten in Settings</string> 3885 <string name="device_owner_wifi_config_unlocked_removal_test_info"> 3886 Please press the button to ensure WiFi config lockdown is NOT in effect. Then go to 3887 Settings > WiFi and see if the CTSVerifier created WiFi configuration can be forgotten. 3888 The test is successful if the config could be forgotten and is removed from the list of saved configs. 3889 </string> 3890 <string name="device_owner_disable_statusbar_test">Disable status bar</string> 3891 <string name="device_owner_disable_statusbar_test_info"> 3892 Please press the below button to disable the status bar and verify that quick settings and notifications 3893 are no longer available.\n 3894 Next, press the button to reenable the status bar and verify that quick settings and notifications 3895 are available again.\n 3896 Please mark the test accordingly. 3897 </string> 3898 <string name="device_owner_disable_statusbar_button">Disable status bar</string> 3899 <string name="device_owner_reenable_statusbar_button">Reenable status bar</string> 3900 <string name="device_owner_disable_keyguard_test">Disable keyguard</string> 3901 <string name="device_owner_disable_keyguard_test_info"> 3902 Before running this test, please make sure you have not set any device lockscreen password.\n 3903 Please press the below button to disable the keyguard. Press the power button on your device to 3904 switch off the screen. Then press the power button to switch the screen back on and verify that 3905 no keyguard was shown.\n 3906 Next, press the button to reenable the keyguard and repeat the above steps, this time verifying that 3907 a keyguard was shown.\n 3908 Please mark the test accordingly. 3909 </string> 3910 <string name="device_owner_disable_keyguard_button">Disable keyguard</string> 3911 <string name="device_owner_reenable_keyguard_button">Reenable keyguard</string> 3912 <string name="device_owner_lock_task_ui_test">LockTask UI</string> 3913 <string name="device_owner_lock_task_ui_test_info"> 3914 The following tests verify the configurable UI during LockTask, a special mode that 3915 prevents the user from leaving the current application.\n\n 3916 Please make sure the lock screen is turned on before the test. Press the button below to 3917 start LockTask mode. Then mark each item as \'pass\' or \'fail\' according to the 3918 instructions.\n\n 3919 Finally, execute the last test item to leave LockTask mode. 3920 </string> 3921 <string name="start_lock_task_button_label">Start LockTask mode</string> 3922 <string name="device_owner_lock_task_ui_default_test">Default LockTask UI</string> 3923 <string name="device_owner_lock_task_ui_default_test_info"> 3924 Press the button below to reset to default LockTask UI. 3925 Observe the following UI restrictions. Mark the test as \'pass\' only if ALL of the 3926 requirements below are met.\n\n 3927 1) If the device under test (DUT) has a status bar: nothing is shown in the status bar, 3928 including notification icons, connectivity icons, battery status, clock, etc.\n 3929 2) If the device under test (DUT) has a status bar: the status bar can\'t be expanded. 3930 That is, the \'swipe-down\' gesture doesn\'t work for the status bar.\n 3931 3) The software Home button is hidden.\n 3932 4) If the device under test (DUT) supports Overview: the software Overview button is 3933 hidden and the Overview gesture (swipe-up) does not work.\n 3934 5) Long-press the power button. The power button menu, which usually shows the power-off 3935 button, etc., isn\'t shown.\n 3936 6) Press the power button to turn off the screen, and press it again to turn the screen 3937 back on. Lock screen shouldn\'t be shown.\n 3938 7) The assistant gesture isn\'t available.\n\n 3939 </string> 3940 <string name="device_owner_lock_task_ui_system_info_test">Enable system info</string> 3941 <string name="device_owner_lock_task_ui_system_info_test_info"> 3942 Press the button below to enable system info. Observe the system info area of the status 3943 bar is now enabled. This includes the clock, connectivity info, battery info, etc.\n\n 3944 The rest of the UI restrictions should still apply:\n 3945 1) If the device under test (DUT) has a status bar: notification icons are still hidden 3946 on the status bar.\n 3947 2) If the device under test (DUT) has a status bar: the status bar can\'t be expanded. 3948 That is, the \'swipe-down\' gesture doesn\'t work for the status bar.\n 3949 3) The software Home button is hidden.\n 3950 4) If the device under test (DUT) supports Overview: the software Overview button is 3951 hidden and the Overview gesture (swipe-up) does not work.\n 3952 5) Long-press the power button. The power button menu, which usually shows the power-off 3953 button, etc., isn\'t shown.\n 3954 6) Press the power button to turn off the screen, and press it again to turn the screen 3955 back on. Lock screen shouldn\'t be shown.\n 3956 7) The assistant gesture isn\'t available.\n\n 3957 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 3958 </string> 3959 <string name="device_owner_lock_task_ui_notifications_test">Enable notifications</string> 3960 <string name="device_owner_lock_task_ui_notifications_test_info"> 3961 Press the button below to enable notifications. Observe the notification icons on the 3962 status bar are now enabled and the Home button is shown. The status bar can also be 3963 expanded to show the notifications. However, all Settings UI should remain invisible, 3964 including Quick Settings and any link to the Settings app.\n\n 3965 The rest of the UI restrictions should still apply:\n 3966 1) If the device under test (DUT) has a status bar: system info area is still hidden on 3967 the status bar.\n 3968 2) If the device under test (DUT) supports Overview: the software Overview button is 3969 hidden and the Overview gesture (swipe-up) does not work.\n 3970 3) Holding the Home button and swiping to the right does not bring up other tasks.\n 3971 4) Long-press the power button. The power button menu, which usually shows the power-off 3972 button, etc., isn\'t shown.\n 3973 5) Press the power button to turn off the screen, and press it again to turn the screen 3974 back on. Lock screen shouldn\'t be shown.\n 3975 6) The assistant gesture isn\'t available.\n\n 3976 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 3977 </string> 3978 <string name="device_owner_lock_task_ui_home_test">Enable Home button</string> 3979 <string name="device_owner_lock_task_ui_home_test_info"> 3980 Press the button below to enable the Home button. Observe the Home button is now 3981 enabled.\n\n 3982 The rest of the UI restrictions should still apply:\n 3983 1) If the device under test (DUT) has a status bar: nothing is shown in the status bar, 3984 including notification icons, connectivity icons, battery status, clock, etc.\n 3985 2) If the device under test (DUT) has a status bar: the status bar can\'t be expanded. 3986 That is, the \'swipe-down\' gesture doesn\'t work for the status bar.\n 3987 3) 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 4) Holding the Home button and swiping to the right does not bring up other tasks.\n 3990 5) Long-press the power button. The power button menu, which usually shows the power-off 3991 button, etc., isn\'t shown.\n 3992 6) Press the power button to turn off the screen, and press it again to turn the screen 3993 back on. Lock screen shouldn\'t be shown.\n 3994 7) The assistant gesture isn\'t available.\n\n 3995 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 3996 </string> 3997 <string name="device_owner_lock_task_ui_recents_test">Enable Overview button</string> 3998 <string name="device_owner_lock_task_ui_recents_test_info"> 3999 If the device under test (DUT) does not support Overview: mark this test as \'pass\'.\n 4000 Otherwise:\n 4001 Press the button below to enable the Overview button. Observe the Home button is now 4002 enabled. Press the Overview button or perform the Overview gesture 4003 (swipe up) and verify the Overview view can be opened.\n\n 4004 The rest of the UI restrictions should still apply:\n 4005 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 4006 battery status, clock, etc.\n 4007 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 4008 for the status bar.\n 4009 3) Long-press the power button. The power button menu, which usually shows the power-off 4010 button, etc., isn\'t shown.\n 4011 4) Press the power button to turn off the screen, and press it again to turn the screen 4012 back on. Lock screen shouldn\'t be shown.\n 4013 5) The assistant gesture isn\'t available.\n\n 4014 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 4015 </string> 4016 <string name="device_owner_lock_task_ui_global_actions_test">Enable global actions</string> 4017 <string name="device_owner_lock_task_ui_global_actions_test_info"> 4018 If the device under test (DUT) does not support global actions: mark this 4019 test as \'pass\'.\n 4020 Otherwise:\n 4021 Press the button below to enable global actions (a.k.a. power button menu). Long-press 4022 the power button and verify a menu containing power-off and restart buttons is shown. 4023 This menu can\'t contain any UI that allows the user to change system settings (such as 4024 airplane mode switch) or access the Settings app.\n\n 4025 The rest of the UI restrictions should still apply:\n 4026 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 4027 battery status, clock, etc.\n 4028 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 4029 for the status bar.\n 4030 3) The software Home button is hidden.\n 4031 4) The software Overview button is hidden and the Overview gesture (swipe-up) does not 4032 work.\n 4033 5) Press the power button to turn off the screen, and press it again to turn the screen 4034 back on. Lock screen shouldn\'t be shown.\n 4035 6) The assistant gesture isn\'t available.\n\n 4036 Mark the test as \'pass\' only if ALL of the above requirements are met.\n 4037 </string> 4038 <string name="device_owner_lock_task_ui_keyguard_test">Enable keyguard</string> 4039 <string name="device_owner_lock_task_ui_keyguard_test_info"> 4040 Press the button below to enable keyguard. Press the power button to turn off the screen 4041 and press it again to turn the screen back on. Verify that the lock screen is shown.\n\n 4042 The rest of the UI restrictions should still apply, both on the lock screen and after 4043 the lock screen is dismissed:\n 4044 1) Nothing is shown in the status bar, including notification icons, connectivity icons, 4045 battery status, clock, etc.\n 4046 2) The status bar can\'t be expanded. That is, the \'swipe-down\' gesture doesn\'t work 4047 for the status bar, even on the lock screen.\n 4048 3) The software Home button is hidden.\n 4049 4) The software Overview button is hidden and the Overview gesture (swipe-up) does not 4050 work.\n 4051 5) Long-press the power button. The power button menu, which usually shows the power-off 4052 button, etc., isn\'t shown.\n 4053 6) The assistant gesture isn\'t available.\n\n 4054 Mark the test as \'pass\' only if ALL of the above requirements are met. 4055 </string> 4056 <string name="device_owner_lock_task_ui_stop_lock_task_test">Stop LockTask mode</string> 4057 <string name="device_owner_lock_task_ui_stop_lock_task_test_info"> 4058 Press the button below to exit LockTask mode.\n\n 4059 Observe that the UI has returned to the normal, unrestricted state, and is no longer 4060 subject to any LockTask restriction.\n\n 4061 Mark the test as \'pass\' or \'fail\' accordingly. 4062 </string> 4063 <string name="device_owner_lockscreen_secure">Please remove lockscreen password</string> 4064 <string name="device_profile_owner_permission_lockdown_test">Permissions lockdown</string> 4065 <string name="device_profile_owner_permission_lockdown_test_instructions"> 4066 Select each of the three grant states for the permission shown below in turn.\n 4067 Now open application settings, select Permissions, and verify if the following behavior is observed.\n 4068 <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 4069 <b>Let user decide:</b> Permission state can be changed through the settings UI.\n 4070 <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 4071 Please mark the test accordingly. 4072 </string> 4073 <string name="device_owner_permission_lockdown_test_info"> 4074 This test checks if the permissions state in settings UI is locked down according to the state set by the device owner. 4075 </string> 4076 <string name="device_owner_disallow_usb_file_transfer_test">Disallow USB file transfer</string> 4077 <string name="device_owner_disallow_usb_file_transfer_test_info"> 4078 Please press below button to set the \"disallow USB file transfer\" restriction.\n 4079 If a USB notification appears, open the notification and check that the 4080 \"Transfer files (MTP)\" and \"Transfer photos (PTP)\" options either are not displayed, 4081 or they trigger a support message when trying to select them.\n 4082 Check if you can mount the device as a USB drive on your desktop computer. The test is 4083 successful if you cannot mount the device, and files from your phone cannot be 4084 downloaded through USB.\n 4085 Please mark the test accordingly. 4086 </string> 4087 <string name="device_owner_set_user_icon">Setting the user icon</string> 4088 <string name="device_owner_set_user_icon_instruction"> 4089 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 4090 1. Press the \"Set user icon 1\" button.\n 4091 2. Press the \"Go\" button to go to Settings.\n 4092 3. If there is no \"users\" section, mark this test as passed.\n 4093 4. If the icon of the user \"owner\" is not \"1\", mark this test as failed.\n 4094 5. Press the \"Disallow set user icon\" button.\n 4095 6. Press the \"Set user icon 2\" button.\n 4096 7. Press the \"Go\" button to go to Settings. Verify that the icon can\'t be changed manually.\n 4097 8. Check that the icon of the user \"owner\" is \"2\", and mark this test accordingly. 4098 </string> 4099 <string name="device_owner_set_user_icon_button">Set user icon 1</string> 4100 <string name="device_owner_set_user_icon2_button">Set user icon 2</string> 4101 4102 <string name="profile_owner_permission_lockdown_test_info"> 4103 <b> 4104 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 4105 </b> 4106 This test checks if the permissions state in settings UI is locked down correctly depending on the state set by the profile owner. 4107 </string> 4108 <string name="package_not_found">You must install %s (aka CtsPermissionApp).</string> 4109 <string name="permission_allow">Grant</string> 4110 <string name="permission_default">Let user decide</string> 4111 <string name="permission_deny">Deny</string> 4112 <string name="not_profile_owner">%s is not profile owner.</string> 4113 <string name="not_device_owner">%s is not device owner.</string> 4114 <string name="activity_not_found">No activity found to handle intent: %s</string> 4115 <string name="open_settings_button_label">Open Application Settings</string> 4116 <string name="finish_button_label">Finish</string> 4117 <string name="device_owner_device_admin_visible">Device administrator settings</string> 4118 <string name="device_owner_device_admin_visible_info"> 4119 Please press the Go button to open the Security page in Settings. 4120 Navigate to Device administrators and confirm that:\n 4121 \n 4122 - \"CTS Verifier\" exists and is activated.\n 4123 - \"CTS Verifier\" cannot be disabled.\n 4124 \n 4125 Use the Back button to return to this page. 4126 </string> 4127 <string name="device_owner_disallow_config_bt">Disallow configuring Bluetooth</string> 4128 <string name="device_owner_disallow_config_bt_info"> 4129 Please press the Set restriction button to set the user restriction. 4130 Then press Go, you should either see (a) the Bluetooth settings page or (b) trigger a support message directly.\n 4131 In the case of (a), confirm that:\n 4132 - You cannot view Bluetooth devices in range.\n 4133 - Trying to edit, add or remove any already paired devices triggers a support message.\n 4134 \n 4135 In the case of (b) this step is successful.\n 4136 \n 4137 Use the Back button to return to this page. 4138 </string> 4139 <string name="device_owner_disallow_config_wifi">Disallow configuring WiFi</string> 4140 <string name="device_owner_disallow_config_wifi_info"> 4141 Please press the Set restriction button to set the user restriction. 4142 Then press Go to open the WiFi page in Settings. 4143 Confirm that:\n\n 4144 - You cannot view WiFi networks in range.\n 4145 - Trying to edit, add or remove any existing WiFi configs triggers a support message.\n 4146 \n 4147 Use the Back button to return to this page. 4148 </string> 4149 <string name="device_owner_disallow_add_wifi_config">Disallow adding WiFi config</string> 4150 <string name="device_owner_disallow_add_wifi_config_info"> 4151 Please press the Set restriction button to set the user restriction. 4152 Then press Go to open the WiFi page in Settings. 4153 Confirm that:\n\n 4154 - You cannot add a new WiFi configuration.\n 4155 - Tapping on the disabled network shows a dialog explaining the admin restriction.\n 4156 \n 4157 Use the Back button to return to this page. 4158 </string> 4159 <string name="device_owner_disallow_sharing_admin_configure_wifi">Disallow sharing admin configured WiFi config</string> 4160 <string name="device_owner_disallow_sharing_admin_configure_wifi_info"> 4161 Please press the Set restriction button to set the user restriction. 4162 Then press Go to open the WiFi page in Settings. 4163 Confirm that:\n\n 4164 - You cannot share an admin configured WiFi config.\n 4165 - Sharing option is disabled in Settings.\n 4166 \n 4167 Use the Back button to return to this page.\n 4168 NOTE: If the device does not support Wi-Fi sharing please skip this test and mark it as passing. 4169 </string> 4170 <string name="device_owner_wifi_security_level_restriction">Set WiFi security level restriction</string> 4171 <string name="device_owner_wifi_security_level_restriction_info"> 4172 This test verifies that minimum WiFi security level restriction can be set by the device owner. 4173 The levels below are listed in an increasing order of security.\n 4174 1. Connect to any network.\n 4175 2. Pick a security level greater than the currently connected network (if unsure pick Enterprise 192).\n 4176 3. Verify that current network gets disconnected.\n 4177 4. Press Go to open the WiFi page in Settings.\n 4178 5. Confirm that you cannot connect to any network that does not meet the security level restriction.\n 4179 6. Use the Back button to return to this page.\n 4180 7. Set the security level to Open to remove the restriction.\n 4181 8. Press Go to open the WiFi page in Settings.\n 4182 9. Confirm that you can connect to any network. 4183 </string> 4184 <string name="set_wifi_security_level_open">Set WiFi security level to Open</string> 4185 <string name="set_wifi_security_level_personal">Set WiFi security level to Personal</string> 4186 <string name="set_wifi_security_level_enterprise_eap">Set WiFi security level to Enterprise EAP</string> 4187 <string name="set_wifi_security_level_enterprise_192">Set WiFi security level to Enterprise 192</string> 4188 <string name="device_owner_ssid_restriction">Set WiFi SSID restriction</string> 4189 <string name="device_owner_ssid_restriction_info"> 4190 This test verifies that WiFi SSID restriction can be set by the device owner.\n 4191 1. Connect to any network.\n 4192 2. Enter the SSID of the network you are currently connected to.\n 4193 3. Set the SSID denylist.\n 4194 4. Verify that current network gets disconnected.\n 4195 5. Press Go to open the WiFi page in Settings.\n 4196 6. Confirm that only the SSID from the denylist is restricted from connection.\n 4197 7. Use the Back button to return to this page.\n 4198 8. Enter the same SSID and set the SSID allowlist.\n 4199 9. Press Go to open the WiFi page in Settings.\n 4200 10. Confirm that you can only connect to the SSID from the allowlist.\n 4201 11. Use the Back button to return to this page.\n 4202 12. Leave the SSID field blank and set the allowlist to remove restriction.\n 4203 13. Press Go to open the WiFi page in Settings.\n 4204 14. Confirm that you can connect to any network. 4205 </string> 4206 <string name="device_owner_ssid_restriction_hint">Enter SSID</string> 4207 <string name="device_owner_set_ssid_allowlist_button">Set SSID allowlist</string> 4208 <string name="device_owner_set_ssid_denylist_button">Set SSID denylist</string> 4209 <string name="device_owner_ssid_restriction_removing_toast">Removing SSID restriction</string> 4210 <string name="device_owner_disallow_ambient_display">Disallow ambient display</string> 4211 <string name="device_owner_disallow_ambient_display_info"> 4212 Please press the Set restriction button to set the user restriction. 4213 Then press Go to open the Display page in Settings. 4214 Mark this test as passed if one of the following:\n\n 4215 - There is no ambient display setting in Display Settings.\n 4216 - Ambient display setting is disabled with an info icon on it. Clicking on it triggers a support dialog.\n 4217 \n 4218 Use the Back button to return to this page. 4219 </string> 4220 <string name="device_owner_disallow_data_roaming">Disallow data roaming</string> 4221 <string name="device_owner_disallow_data_roaming_info"> 4222 Device should have a sim card to perform this test. 4223 Please press the Set restriction button to set the user restriction. 4224 Then press Go to open the Mobile network page in Settings. 4225 Confirm that:\n\n 4226 - Data roaming is disabled.\n 4227 - Enabling data roaming is not possible and triggers a support message.\n\n 4228 Use the Back button to return to this page. 4229 </string> 4230 <string name="device_owner_disallow_factory_reset">Disallow factory reset</string> 4231 <string name="device_owner_disallow_factory_reset_info"> 4232 Please press the Set button to set the user restriction.\n 4233 1. Go to the factory reset settings. It is often located in \"Backup & reset\" settings.\n 4234 Confirm that:\n 4235 - Factory data reset is disabled.\n 4236 - Pressing factory data reset is not possible and triggers a support message.\n\n 4237 2. Go to OEM unlocking settings, if this device has this Settings option. It is often located under \"Developer options\".\n 4238 Confirm that:\n 4239 - Oem Unlocking is disabled.\n 4240 - Enabling Oem unlocking is not possible, and pressing the button or menu option to enable it triggers a support message (if pressing is possible).\n\n 4241 Return back to this page. 4242 </string> 4243 <string name="device_owner_user_restriction_set">Set restriction</string> 4244 <string name="device_owner_user_restriction_unset">Clear restriction (before leaving test)</string> 4245 <string name="device_owner_settings_go">Go</string> 4246 4247 <string name="device_owner_vpn_connection"> 4248 VPN connection has been established.\n 4249 This is not as expected.\n 4250 Mark this test as failed.\n 4251 </string> 4252 <string name="device_owner_vpn_connection_close_failed"> 4253 Established vpn connection cannot be closed.\n 4254 This is not as expected.\n 4255 Mark this test as failed.\n 4256 </string> 4257 <string name="device_owner_no_vpn_connection"> 4258 Cannot establish a VPN connection.\n 4259 This was expected.\n 4260 Mark this test as passed.\n 4261 </string> 4262 <string name="device_owner_vpn_test">Check VPN</string> 4263 <string name="device_owner_vpn_info_default">VPN test message</string> 4264 4265 <string name="device_owner_disallow_config_vpn">Disallow configuring VPN</string> 4266 <string name="device_owner_disallow_config_vpn_info"> 4267 Please press the Set VPN restriction button to set the VPN restriction. 4268 Perform tests in order. Mark test as passed if both test cases pass\n\n 4269 1. Press Go to attempt to open the VPN settings page.\n 4270 You should either see (a) the VPN settings page or (b) that the Intent 4271 android.settings.VPN_SETTINGS fails to resolve.\n 4272 In the case of (a), confirm that:\n 4273 - Trying to perform any of the above actions will trigger a support message.\n 4274 In the case of (b) this step is successful.\n\n 4275 2. Press Check VPN to check programmatic Vpn test.\n 4276 - Check Vpn setup is not allowed\n 4277 - If prompted to allow a VPN connection, press OK.\n\n 4278 Use the Back button to return to this page. 4279 </string> 4280 <string name="device_owner_user_vpn_restriction_set">Set VPN restriction</string> 4281 4282 <!-- Strings for DeviceOwnerBugreportTest --> 4283 <string name="device_owner_requesting_bugreport_tests">Device Owner Requesting Bugreport Tests</string> 4284 <string name="device_owner_requesting_bugreport_category">Device Owner Requesting Bugreport Tests</string> 4285 <string name="device_owner_requesting_bugreport_tests_info"> 4286 The device owner requesting bugreport tests verify that a bugreport can be requested on a corporate owned device.\n 4287 Press below button first, follow steps described in the dialog that pops up, 4288 then proceed to the test cases.\n 4289 Pressing \'back\', \'pass\' or \'fail\' on this test page will remove the device owner.\n 4290 Alternatively, you can run the \'Remove device owner\' test. Ideally, that test should 4291 be run last so that it does not interfere with other tests. 4292 </string> 4293 <string name="device_owner_request_bugreport">Request bugreport</string> 4294 <string name="bugreport_sharing_declined">Bugreport sharing declined</string> 4295 <string name="bugreport_shared_successfully">Bugreport shared successfully</string> 4296 <string name="bugreport_already_in_progress">Bugreport is already being collected on this device</string> 4297 <string name="bugreport_failed_completing">Bugreport collection operation failed</string> 4298 <string name="device_owner_bugreport_sharing_declined_while_being_taken">Sharing of requested bugreport declined while being taken</string> 4299 <string name="device_owner_bugreport_sharing_declined_while_being_taken_info"> 4300 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 4301 Open the notifications panel and verify that:\n 4302 \n 4303 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 4304 \n 4305 Press the \"Request bugreport\" button again to try to invoke a second bugreport sharing operation. 4306 Open the notifications panel and verify that:\n 4307 \n 4308 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport is already being collected on this device\" is present. Dismiss that notification.\n 4309 - 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 4310 \n 4311 Tap the \"DECLINE\" button and verify that:\n 4312 \n 4313 <!-- Disabled in U due to b/317738856 --> 4314 <!-- \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n --> 4315 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport sharing declined\" is present.\n 4316 \n 4317 Dismiss the notifications and mark test as passed or failed. 4318 </string> 4319 <string name="device_owner_bugreport_sharing_accepted_while_being_taken">Sharing of requested bugreport accepted while being taken</string> 4320 <string name="device_owner_bugreport_sharing_accepted_while_being_taken_info"> 4321 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 4322 Open the notifications panel and verify that:\n 4323 \n 4324 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 4325 - 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 4326 \n 4327 Tap the \"SHARE\" button and verify that:\n 4328 \n 4329 <!-- Disabled in U due to b/317738856 --> 4330 <!-- \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n --> 4331 - Notification titled \"Sharing bugreport...\" with an indefinite progress bar is present.\n 4332 - 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 4333 \n 4334 Dismiss the notifications and mark test as passed or failed. 4335 </string> 4336 <string name="device_owner_bugreport_sharing_declined_after_having_been_taken">Sharing of requested bugreport declined after having been taken</string> 4337 <string name="device_owner_bugreport_sharing_declined_after_having_been_taken_info"> 4338 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 4339 Open the notifications panel and verify that:\n 4340 \n 4341 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 4342 \n 4343 Wait for a few minutes (time necessary for bugreport to be collected) and verify that:\n 4344 \n 4345 <!-- Disabled in U due to b/317738856 --> 4346 <!-- \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n --> 4347 - 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 4348 \n 4349 Tap the \"DECLINE\" button and verify that:\n 4350 \n 4351 - Notification titled \"Share bug report?\" is dismissed.\n 4352 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport sharing declined\" is present.\n 4353 \n 4354 Dismiss the notifications and mark test as passed or failed. 4355 </string> 4356 <string name="device_owner_bugreport_sharing_accepted_after_having_been_taken">Sharing of requested bugreport accepted after having been taken</string> 4357 <string name="device_owner_bugreport_sharing_accepted_after_having_been_taken_info"> 4358 Please press the \"Request bugreport\" button to invoke the bugreport sharing operation. 4359 Open the notifications panel and verify that:\n 4360 \n 4361 - Notification titled \"Taking bugreport...\" with an indefinite progress bar is present.\n 4362 \n 4363 Wait for a few minutes (time necessary for bugreport to be collected) and verify that:\n 4364 \n 4365 <!-- Disabled in U due to b/317738856 --> 4366 <!-- \"Taking bugreport...\" notification with an indefinite progress bar is no longer present.\n --> 4367 - 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 4368 \n 4369 Tap the \"SHARE\" button and verify that:\n 4370 \n 4371 - Notification titled \"Share bug report?\" is dismissed.\n 4372 - Notification titled \"Device Owner Requesting Bugreport Tests\" with message \"Bugreport shared successfully\" is present.\n 4373 \n 4374 Dismiss the notifications and mark test as passed or failed. 4375 </string> 4376 4377 <!-- Strings used for policy transparency test --> 4378 <string name="device_profile_owner_policy_transparency_test">Policy transparency test</string> 4379 <string name="device_profile_owner_policy_transparency_test_info"> 4380 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. 4381 </string> 4382 <string name="policy_transparency_open_settings_label">Open settings</string> 4383 <string name="policy_transparency_short_support_msg_label">Set short support message</string> 4384 <string name="policy_transparency_long_support_msg_label">Set long support message</string> 4385 <string name="policy_transparency_set_msg">Set message</string> 4386 <string name="policy_transparency_clear_msg">Clear message</string> 4387 <string name="policy_transparency_set_default_msg">Set default message</string> 4388 <string name="policy_transparency_default_short_msg"> 4389 This action is disabled by your administrator. Contact someone@example.com for support. 4390 </string> 4391 <string name="policy_transparency_default_long_msg"> 4392 This profile or device is managed by CtsVerifier. You can contact tech 4393 support on:\n\n 4394 America: +1 555-0100\n\n 4395 APAC: +1 555-0100\n\n 4396 Europe: +1 555-0100\n\n 4397 Email: someone@example.com 4398 </string> 4399 <string name="policy_transparency_update_button_label">Update</string> 4400 <string name="test_input_method_label">Test input method</string> 4401 <string name="test_accessibility_service_label">Test accessibility service</string> 4402 <string name="policy_transparency_test_instructions"> 4403 1. <xliff:g id="set_step" example="Set policy by turning the switch on">%1$s</xliff:g>\n 4404 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 4405 3. Verify that performing the following action will trigger a support dialog:\n 4406 <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 4407 4. Verify that the support dialog displays the short support message set earlier.\n 4408 </string> 4409 <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> 4410 <string name="user_restriction_set_step"> 4411 Set \'%s\' user restriction by turning on the switch below. 4412 </string> 4413 <string name="disallow_add_user">Disallow add user</string> 4414 <string name="disallow_add_user_action">Accessing the multiple users settings page, or if the device allows access to the page, then attempting to enable the feature </string> 4415 <string name="disallow_adjust_volume">Disallow adjust volume</string> 4416 <string name="disallow_adjust_volume_action">Adjusting the volume\n 4417 NOTE: If the device does not support volume adjustment in Settings app please skip this test and mark it as passing.\n</string> 4418 <string name="disallow_config_date_time">Disallow config date time</string> 4419 <string name="disallow_config_date_time_action">Configuring auto time, time, auto date or date</string> 4420 <string name="disallow_config_location">Disallow config location</string> 4421 <string name="disallow_config_location_action">Enabling or disabling location, \'Bluetooth Scanning\' or \'WiFi Scanning\' in settings or quick settings</string> 4422 <string name="disallow_airplane_mode">Disallow airplane mode</string> 4423 <string name="disallow_airplane_mode_action">Toggling airplane mode switch bar or changing airplane mode state in quick settings</string> 4424 <string name="disallow_config_screen_timeout">Disallow config screen timeout</string> 4425 <string name="disallow_config_screen_timeout_action">Configuring sleep options in Display settings</string> 4426 <string name="disallow_config_brightness">Disallow config brightness</string> 4427 <string name="disallow_config_brightness_action">Configuring brightness level or adaptive brightness in Display settings, or toggling brightness slider in quick settings</string> 4428 <string name="disallow_apps_control">Disallow controlling apps</string> 4429 <string name="disallow_apps_control_action">DISABLE/UNINSTALL/FORCE STOP-ing any app in the managed device/profile other than CtsVerifier</string> 4430 <string name="disallow_config_cell_broadcasts">Disallow config cell broadcasts</string> 4431 <string name="disallow_config_cell_broadcasts_action">Configuring emergency alerts(cell broadcasts)</string> 4432 <string name="disallow_config_credentials">Disallow config credentials</string> 4433 <string name="disallow_config_credentials_action">Configuring user credentials</string> 4434 <string name="disallow_config_mobile_networks">Disallow config mobile networks</string> 4435 <string name="disallow_config_mobile_networks_action">Configuring mobile networks</string> 4436 <string name="disallow_config_tethering">Disallow config tethering</string> 4437 <string name="disallow_config_tethering_action"> 4438 Configuring tethering and portable hotspots.\n 4439 NOTE: If the device does not support tethering please skip this test and mark it as passing.\n 4440 </string> 4441 <string name="disallow_config_wifi">Disallow config Wi-Fi</string> 4442 <string name="disallow_config_wifi_action">Modifying Wi-Fi configuration</string> 4443 <string name="disallow_debugging_features">Disallow debugging features</string> 4444 <string name="disallow_debugging_features_action">Enabling developer options</string> 4445 <string name="disallow_factory_reset">Disallow factory reset</string> 4446 <string name="disallow_factory_reset_action">Factory resetting the device</string> 4447 <string name="disallow_fun">Disallow fun</string> 4448 <string name="disallow_fun_action">Opening android easter egg game by tapping repeatedly on the \'Android version\' option</string> 4449 <string name="disallow_install_unknown_sources">Disallow install unknown sources</string> 4450 <string name="disallow_install_unknown_sources_action">Enabling \'Cts Verifier\' to install apps</string> 4451 <string name="disallow_install_unknown_sources_globally">Disallow install unknown sources globally</string> 4452 <string name="disallow_install_unknown_sources_globally_action">Enabling \'Cts Verifier\' to install apps device-wide</string> 4453 <string name="disallow_modify_accounts">Disallow modify accounts</string> 4454 <string name="disallow_modify_accounts_action">Adding an account, and also removing an account (after you have previously added one)</string> 4455 <string name="disallow_network_reset">Disallow network reset</string> 4456 <string name="disallow_network_reset_action">Resetting network settings\n 4457 NOTE: If the device does not support network reset please skip this test and mark it as passing.\n</string> 4458 <string name="disallow_outgoing_beam">Disallow outgoing beam</string> 4459 <string name="disallow_outgoing_beam_action">Switching on android beam</string> 4460 <string name="disallow_remove_user">Disallow remove user</string> 4461 <string name="check_new_user_disclaimer">Check new user disclaimer</string> 4462 <string name="check_new_user_disclaimer_info"> 4463 Please do the following: \n\n 4464 1. Check persistent notification for managed device \n\n 4465 a). Open the notification UI, verify that there is a notification saying the device is managed.\n 4466 b). Tap the notification\n 4467 c). It should show a dialog explaining the device is managed and asking the user to accept \n 4468 d). Don\'t accept initially and tap outside the dialog \n 4469 e). Open the notification UI again, verify that the managed device notification is still shown \n 4470 \n 4471 f). Click \"Set Org\", and open the notification UI again, verify that the organization name 4472 \"Foo, Inc\" is shown on the dialog \n 4473 \n\n 4474 2. Check adding account is restricted\n\n 4475 a) Click \"Go\" to launch the \"Profiles & accounts\" setting \n 4476 b) navigate to \"Add account\" \n 4477 \n 4478 Expected: \n 4479 - \"Add account\" is disabled \n 4480 - Click the button will launch the new user disclaimer dialog\n 4481 \n 4482 c) Click accept button\n 4483 \n 4484 Expected: \n 4485 - the screen will be dismissed \n 4486 - \"Add account\" will be enabled\n 4487 - Click the button will take user to the screen to add account \n 4488 </string> 4489 <string name="device_owner_disallow_remove_user_info"> 4490 Please press \'Create uninitialized user\' to create a user that is not set up. Then press the 4491 \'Set restriction\' button to set the user restriction. 4492 Then press \'Go\' to open \'Multiple users\' setting. \n 4493 Click the managed user to open settings.\n\n 4494 4495 Mark this test as passed if:\n\n 4496 - \"Delete User\" is disabled.\n 4497 - Tapping \"Delete user\" shows an \"Action not allowed\" dialog.\n 4498 \n 4499 Use the Back button to return to this page. 4500 </string> 4501 <string name="managed_user_disallow_remove_user_info"> 4502 Please press the \'Set restriction\' button to set the user restriction. 4503 Then press \'Go\' to open \'Multiple users\' setting. \n\n 4504 4505 Mark this test as passed if all of the following conditions are met:\n\n 4506 - The \"Delete managed user from this device\" option in the overflow menu is disabled\n 4507 - Clicking \"Delete managed user from this device\" in the overflow menu results in an \"Action not allowed\" dialog.\n 4508 \n 4509 Use the Back button to return to this page. 4510 </string> 4511 <string name="device_owner_disallow_remove_user_create_user">Create uninitialized user</string> 4512 <string name="device_owner_remove_secondary_user">Remove uninitialized user</string> 4513 <string name="disallow_remove_managed_profile">Disallow remove managed profile</string> 4514 <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> 4515 <string name="disallow_share_location">Disallow share location</string> 4516 <string name="disallow_share_location_action">Turning on location sharing</string> 4517 <string name="disallow_set_user_icon">Disallow set user icon</string> 4518 <string name="disallow_uninstall_apps">Disallow uninstall apps</string> 4519 <string name="disallow_uninstall_apps_action"> 4520 a. If testing in work profile: uninstall applications from the work profile (badged applications) other than CtsVerifier and system apps. \n 4521 b. Otherwise: uninstall applications other than CtsVerifier and system apps 4522 </string> 4523 <string name="disallow_unified_challenge">Disallow unified challenge</string> 4524 <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> 4525 <string name="disallow_keyguard_unredacted_notifications">Disallow lockscreen unredacted notification</string> 4526 <string name="disallow_keyguard_unredacted_notifications_set_step">Disallow unredacted notifications when device is locked by turning on the switch below</string> 4527 <string name="disallow_keyguard_unredacted_notifications_action">Selecting show all notification content when device is locked</string> 4528 <string name="disallow_keyguard_unredacted_notifications_widget_label">@string/disallow_keyguard_unredacted_notifications</string> 4529 <string name="set_auto_time_required">Set auto (network) time required</string> 4530 <string name="auto_time_required_set_step">Set auto time required policy by turning on the switch below</string> 4531 <string name="set_auto_time_required_action">Modifying date and time</string> 4532 <string name="set_auto_time_required_widget_label">@string/set_auto_time_required</string> 4533 <string name="set_lock_screen_info">Set lock screen info</string> 4534 <string name="lock_screen_info_set_step">Select a lock screen info by setting a non-empty message in the edittext below.</string> 4535 <string name="set_lock_screen_info_action">Modifying lock screen message</string> 4536 <string name="set_lock_screen_info_widget_label">@string/set_lock_screen_info</string> 4537 <string name="set_maximum_time_to_lock">Set maximum time to lock</string> 4538 <string name="maximum_time_to_lock_set_step"> 4539 Select a non-zero maximum time to lock value by setting a value in the edittext box below. 4540 </string> 4541 <string name="set_maximum_time_to_lock_action">Selecting maximum time to lock greater than the set value below</string> 4542 <string name="set_maximum_time_to_lock_widget_label">Set maximum time to lock (in Sec):</string> 4543 <string name="set_permitted_accessibility_services">Set permitted accessibility services</string> 4544 <string name="permitted_accessibility_services_set_step"> 4545 Check that \'Test Accessibility service\' is not enabled in Settings and disallow \'Test Accessibility service\' from permitted accessibility services by turning on 4546 the switch below. 4547 </string> 4548 <string name="set_permitted_accessibility_services_action"> 4549 Enabling \'Test Accessibility service\' in the list of accessibility services 4550 </string> 4551 <string name="set_permitted_accessibility_services_widget_label"> 4552 Allow only system accessibility services: 4553 </string> 4554 <string name="set_permitted_input_methods">Set permitted input methods</string> 4555 <string name="permitted_input_methods_set_step"> 4556 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. 4557 </string> 4558 <string name="set_permitted_input_methods_action"> 4559 Enabling \'Test Input method\' in the list of input methods (make sure you are enabling it for the managed profile, not primary profile) 4560 </string> 4561 <string name="set_permitted_input_methods_widget_label"> 4562 Allow only system input methods: 4563 </string> 4564 4565 <!-- Strings used for enterprise privacy tests --> 4566 <string name="enterprise_privacy_test">Managed device info tests</string> 4567 <string name="enterprise_privacy_page">Managed device info page</string> 4568 <string name="enterprise_privacy_page_info"> 4569 Please press the Go button to open Settings. Verify that:\n 4570 1) One of the Settings screens contains an entry for managed device information.\n 4571 2) Tapping that entry opens a screen.\n 4572 3) In this screen, at a minimum, you are told your organization can:\n 4573 * Change settings on this device.\n 4574 * See data associated with your work account.\n 4575 * See the list of all apps on your device.\n 4576 * See usage of each app on your device.\n 4577 * Lock the device and change the password.\n 4578 * Wipe the device.\n 4579 \n 4580 Use the Back button to return to this page. 4581 </string> 4582 <string name="enterprise_privacy_open_settings">Open Settings</string> 4583 <string name="enterprise_privacy_network_logging">Retrieve traffic logs</string> 4584 <string name="enterprise_privacy_network_logging_info"> 4585 Please do the following:\n 4586 1) Press the Retrieve Traffic Logs button and record the time at which you did this.\n 4587 2) Wait one minute.\n 4588 3) Press the Open Settings button.\n 4589 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 4590 \n 4591 Use the Back button to return to this page. 4592 </string> 4593 <string name="enterprise_privacy_retrieve_network_logs">Retrieve Traffic Logs</string> 4594 <string name="enterprise_privacy_bug_report">Request bug report</string> 4595 <string name="enterprise_privacy_bug_report_info"> 4596 Please do the following:\n 4597 1) Press the Request Bug Report button and record the time at which you did this.\n 4598 2) Wait one minute.\n 4599 3) Press the Open Settings button.\n 4600 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 4601 \n 4602 Use the Back button to return to this page. 4603 </string> 4604 <string name="enterprise_privacy_request_bug_report">Request Bug Report</string> 4605 <string name="enterprise_privacy_security_logging">Retrieve security logs</string> 4606 <string name="enterprise_privacy_security_logging_info"> 4607 Please do the following:\n 4608 1) Press the Retrieve Security Logs button and record the time at which you did this.\n 4609 2) Wait one minute.\n 4610 3) Press the Open Settings button.\n 4611 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 4612 \n 4613 Use the Back button to return to this page. 4614 </string> 4615 <string name="enterprise_privacy_retrieve_security_logs">Retrieve Security Logs</string> 4616 <string name="enterprise_privacy_clear_organization">Clear Org</string> 4617 <string name="enterprise_privacy_set_organization">Set Org</string> 4618 <string name="enterprise_privacy_enterprise_installed_apps">Enterprise-installed apps</string> 4619 <string name="enterprise_privacy_enterprise_installed_apps_info"> 4620 Please do the following:\n 4621 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 4622 make NotificationBot\n 4623 2) Grant MANAGE_EXTERNAL_STORAGE by issuing the following command on the host:\n 4624 adb shell appops set com.android.cts.verifier MANAGE_EXTERNAL_STORAGE 0\n 4625 3) Upload the NotificationBot.apk to your device by issuing the following command on the host:\n 4626 adb push /path/to/NotificationBot.apk /sdcard\n 4627 4) Press the Uninstall button.\n 4628 5) Press the Open Settings button.\n 4629 6) In the screen that opens, verify that you are not told that your administrator installed any apps.\n 4630 7) Use the Back button to return to this page.\n 4631 8) Press the Install button.\n 4632 9) Press the Open Settings button.\n 4633 10) In the screen that opens, verify that you are told now that your administrator installed at least one app.\n 4634 11) Tap on that information. Verify that a list of apps installed shows.\n 4635 12) Verify that the list contains the CTS Robot app.\n 4636 13) Use the Back button to return to this page.\n 4637 14) Press the Uninstall button.\n 4638 15) Issue the following command on the host:\n 4639 adb shell rm /sdcard/NotificationBot.apk 4640 </string> 4641 <string name="enterprise_privacy_enterprise_installed_apps_info_headless_system_user"> 4642 Please do the following:\n 4643 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 4644 \tmake NotificationBot\n 4645 2) Install the NotificationBot for <b>user 0 only</b>. For example:\n 4646 \tadb install --user 0 $ANDROID_PRODUCT_OUT/testcases/NotificationBot/*/NotificationBot.apk\n 4647 3) Make sure the app is <b>not</b> installed for the current user:\n 4648 \tadb shell pm list packages --user cur |grep com.android.cts.robot || echo \'Not installed\'\n 4649 4) Press the Open Settings button.\n 4650 5) In the screen that opens, verify that you are not told that your administrator installed any apps (other than CtsVerifier itself).\n 4651 6) Use the Back button to return to this page.\n 4652 7) Press the Install button.\n 4653 8) Press the Open Settings button.\n 4654 9) In the screen that opens, verify that you are told now that your administrator installed at least one app.\n 4655 10) Tap on that information. Verify that a list of apps installed shows.\n 4656 11) Verify that the list contains the CTS Robot app.\n 4657 12) Use the Back button to return to this page.\n 4658 13) Press the Uninstall button.\n 4659 14) Issue the following command on the host:\n 4660 \tadb uninstall --user all com.android.cts.robot\n 4661 </string> 4662 <string name="enterprise_privacy_install">Install</string> 4663 <string name="enterprise_privacy_uninstall">Uninstall</string> 4664 <string name="enterprise_privacy_admin_granted_location_access">Location access permission</string> 4665 <string name="enterprise_privacy_admin_granted_location_access_info"> 4666 Please do the following:\n 4667 1) Press the Reset button.\n 4668 2) Press the Open Settings button.\n 4669 3) In the screen that opens, verify that you are not told that your administrator has granted location access to any apps.\n 4670 4) Use the Back button to return to this page.\n 4671 5) Press the Grant button.\n 4672 6) Press the Open Settings button.\n 4673 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 4674 8) Tap on that information. Verify that a list of apps which have location access shows.\n 4675 9) Verify that the list contains the CTS Verifier app.\n 4676 10) Use the Back button to return to this page.\n 4677 11) Press the Reset button. 4678 </string> 4679 <string name="enterprise_privacy_reset">Reset</string> 4680 <string name="enterprise_privacy_grant">Grant</string> 4681 <string name="enterprise_privacy_admin_granted_microphone_access">Microphone access permission</string> 4682 <string name="enterprise_privacy_admin_granted_microphone_access_info"> 4683 Please do the following:\n 4684 1) Press the Reset button.\n 4685 2) Press the Open Settings button.\n 4686 3) In the screen that opens, verify that you are not told that your administrator has granted microphone access to any apps.\n 4687 4) Use the Back button to return to this page.\n 4688 5) Press the Grant button.\n 4689 6) Press the Open Settings button.\n 4690 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 4691 8) Tap on that information. Verify that a list of apps that have microphone access shows.\n 4692 9) Verify that the list contains the CTS Verifier app.\n 4693 10) Use the Back button to return to this page.\n 4694 11) Press the Reset button. 4695 </string> 4696 <string name="enterprise_privacy_admin_granted_camera_access">Camera access permission</string> 4697 <string name="enterprise_privacy_admin_granted_camera_access_info"> 4698 Please do the following:\n 4699 1) Press the Reset button.\n 4700 2) Press the Open Settings button.\n 4701 3) In the screen that opens, verify that you are not told that your administrator has granted camera access to any apps.\n 4702 4) Use the Back button to return to this page.\n 4703 5) Press the Grant button.\n 4704 6) Press the Open Settings button.\n 4705 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 4706 8) Tap on that information. Verify that a list of apps that have camera access shows.\n 4707 9) Verify that the list contains the CTS Verifier app.\n 4708 10) Use the Back button to return to this page.\n 4709 11) Press the Reset button. 4710 </string> 4711 <string name="enterprise_privacy_default_apps">Default apps</string> 4712 <string name="enterprise_privacy_default_apps_info"> 4713 Please do the following:\n 4714 1) Press the Reset button.\n 4715 2) Press the Open Settings button.\n 4716 3) In the screen that opens, verify that you are not told that your administrator set any default apps.\n 4717 4) Use the Back button to return to this page.\n 4718 5) Press the Set Default Apps button.\n 4719 6) Press the Open Settings button.\n 4720 7) In the screen that opens, verify that you are now told that your administrator has set 6 default apps.\n 4721 8) Tap on that information. Verify that a list of default apps shows, with 6 elements in it.\n 4722 9) Verify that each element shows the CTS Verifier is the default app.\n 4723 10) Use the Back button to return to this page.\n 4724 11) Press the Reset button. 4725 </string> 4726 <string name="enterprise_privacy_set_default_apps">Set Default Apps</string> 4727 <string name="enterprise_privacy_default_ime">Default keyboard</string> 4728 <string name="enterprise_privacy_default_ime_info"> 4729 Please do the following:\n 4730 1) Press the Open Settings button.\n 4731 2) In the screen that opens, verify that you are not told the default keyboard has been set.\n 4732 3) Use the Back button to return to this page.\n 4733 4) Press the Set Keyboard button to set the default keyboard.\n 4734 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 4735 6) Press the Finish button to clear the default keyboard. 4736 </string> 4737 <string name="enterprise_privacy_set_keyboard">Set Keyboard</string> 4738 <string name="enterprise_privacy_finish">Finish</string> 4739 <string name="enterprise_privacy_always_on_vpn">Always-on VPN</string> 4740 <string name="enterprise_privacy_always_on_vpn_info"> 4741 Please do the following:\n 4742 1) Press the Open Settings button.\n 4743 2) In the screen that opens, verify that you are not told that an always-on VPN is set.\n 4744 3) Use the Back button to return to this page.\n 4745 4) Press the Set VPN button to set an always-on VPN.\n 4746 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that an always-on VPN is set.\n 4747 6) Press the Finish button to clear the always-on VPN. 4748 </string> 4749 <string name="enterprise_privacy_set_always_on_vpn">Set VPN</string> 4750 <string name="enterprise_privacy_start">Start</string> 4751 <string name="enterprise_privacy_global_http_proxy">Global HTTP Proxy</string> 4752 <string name="enterprise_privacy_global_http_proxy_info"> 4753 Please do the following:\n 4754 1) Press the Open Settings button.\n 4755 2) In the screen that opens, verify that you are not told that a global HTTP proxy has been set.\n 4756 3) Use the Back button to return to this page.\n 4757 4) Press the Set Proxy button.\n 4758 5) Repeat steps (1) through (3), verifying that in step (2), you are told now that a global HTTP proxy has been set.\n 4759 6) Press the Clear Proxy button. 4760 </string> 4761 <string name="enterprise_privacy_ca_certs">Trusted CA certs</string> 4762 <string name="enterprise_privacy_ca_certs_info"> 4763 Please do the following:\n 4764 1) Press the Open Settings button.\n 4765 2) In the screen that opens, verify that you are not told that your administrator installed trusted CA certs.\n 4766 3) Use the Back button to return to this page.\n 4767 4) Press the Install Cert button to install a trusted CA cert.\n 4768 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 4769 6) Press the Finish button to clear the cert. 4770 </string> 4771 <string name="enterprise_privacy_install_cert">Install Cert</string> 4772 <string name="enterprise_privacy_settings">Settings</string> 4773 <string name="enterprise_privacy_set_proxy">Set Proxy</string> 4774 <string name="enterprise_privacy_clear_proxy">Clear Proxy</string> 4775 <string name="enterprise_privacy_failed_password_wipe">Wipe on authentication failure</string> 4776 <string name="enterprise_privacy_failed_password_wipe_info"> 4777 Please do the following:\n 4778 1) Press the Open Settings button.\n 4779 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 4780 3) Use the Back button to return to this page.\n 4781 4) Press the Set Limit button to set the maximum number of password attempts.\n 4782 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 4783 6) Press the Finish button to clear the maximum number of password attempts. 4784 </string> 4785 <string name="enterprise_privacy_set_limit">Set Limit</string> 4786 <string name="enterprise_privacy_quick_settings">Quick settings disclosure</string> 4787 <string name="enterprise_privacy_quick_settings_info"> 4788 Please do the following:\n 4789 1) Press the Clear Org button.\n 4790 2) Open and fully expand Quick Settings.\n 4791 3) Verify that at the bottom of Quick Settings, you are told the device is managed.\n 4792 4) Close Quick Settings.\n 4793 5) Press the Set Org button.\n 4794 6) Open and fully expand Quick Settings.\n 4795 7) Verify that at the bottom of Quick Settings, you are told the device is managed by \"Foo, Inc.\".\n 4796 8) Tap on the information.\n 4797 9) Verify that a dialog informing you about device monitoring opens.\n 4798 10) Tap the \"View Policies\" button.\n 4799 11) Verify that a screen informing you what your managing organization can do is shown.\n 4800 \n 4801 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. 4802 </string> 4803 <string name="enterprise_privacy_keyguard">Keyguard disclosure</string> 4804 <string name="enterprise_privacy_keyguard_info"> 4805 Please do the following:\n 4806 1) Press the Open Settings button to open Settings.\n 4807 2) Navigate to \"Security\" > \"Screen lock\" and select the first screen lock type that is not \"None\".\n 4808 3) Use the Back button to return to this page.\n 4809 4) Press the Clear Org button.\n 4810 5) Lock the device.\n 4811 6) Verify that on the lock screen, you are told the device is managed.\n 4812 7) Unlock the device.\n 4813 8) Press the Set Org button.\n 4814 9) Lock the device.\n 4815 10) Verify that on the lock screen, you are told the device is managed by \"Foo, Inc.\".\n 4816 11) Unlock the device.\n 4817 12) Repeat steps (1) through (11) for each screen lock type other than \"None\". 4818 </string> 4819 <string name="enterprise_privacy_add_account">Add account disclosure</string> 4820 <string name="enterprise_privacy_add_account_info"> 4821 Please do the following:\n 4822 1) Press the Clear Org button.\n 4823 2) Press the Open Settings button.\n 4824 3) In the screen that opens, verify that you are told that the device is managed.\n 4825 4) Use the Back button to return to this page.\n 4826 5) Press the Set Org button.\n 4827 6) Press the Open Settings button.\n 4828 7) In the screen that opens, verify that you are told that the device is managed by \"Foo, Inc.\".\n 4829 8) Tap the \"Learn more\" link.\n 4830 9) Verify that a screen informing you what your managing organization can do is shown.\n 4831 11) Use the Back button to return to this page. 4832 </string> 4833 <string name="enterprise_privacy_default_app">CTS Verifier Test</string> 4834 4835 <!-- Strings for Network Logging Tests --> 4836 <string name="device_owner_network_logging_ui">Network Logging UI</string> 4837 <string name="device_owner_network_logging_ui_info">Please do the following:\n 4838 1) Open and fully expand Quick Settings.\n 4839 2) Check that you are told that your device is managed.\n 4840 3) Close Quick Settings.\n 4841 4) Enable network logging by tapping on the left button below.\n 4842 5) Open Quick Settings again. Check that an icon appeared next to the text about device management.\n 4843 6) Verify that a notification including the same icon popped up, informing you that network logging has been enabled.\n 4844 7) Tap the notification.\n 4845 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 4846 9) Close the dialog.\n 4847 10) Tap the right button below to disable network logging.\n 4848 11) Verify that the notification disappeared.\n 4849 \n 4850 If this device does not have quick settings, please skip this test and mark it passing. 4851 </string> 4852 <string name="device_owner_enable_network_logging_button">Enable Network Logging</string> 4853 <string name="device_owner_disable_network_logging_button">Disable Network Logging</string> 4854 4855 <!-- Strings for Customize Lock Screen Message --> 4856 <string name="device_owner_customize_lockscreen_message">Customize Lock Screen Message</string> 4857 <string name="device_owner_customize_lockscreen_message_info">Please do the following:\n 4858 1) Press the \"Go\" button to go to Settings\n 4859 2) Find the \"Screen lock\" option and set it to \"Swipe\"\n 4860 3) Use the Back button to return to this page\n 4861 4) In the field below, write a lock screen message.\n 4862 5) Press the \"Set lock screen message\" button\n 4863 6) Press Power button once to lock the screen.\n 4864 7) Press Power button again to reveal the lock screen.\n 4865 8) Verify that the message from step 1) appears on the lock screen.\n 4866 9) Unlock the screen and return to this page.\n 4867 10) Press the \"Go\" button to go to Settings\n 4868 11) Find the \"Lock screen message\" option\n 4869 12) Verify that you cannot modify the setting.\n 4870 13) Use the Back button to return to this page.\n 4871 14) Press the \"Go\" button to go to Settings\n 4872 15) Find the \"Screen lock\" option and set it to \"None\"\n 4873 16) Use the Back button to return to this page 4874 </string> 4875 <string name="device_owner_set_lockscreen_message_button">Set lock screen message</string> 4876 <string name="device_owner_set_lockscreen_message_hint">My lock screen message</string> 4877 <string name="device_owner_lockscreen_message_cannot_be_empty">Lock screen message cannot be empty.</string> 4878 4879 <string name="device_owner_disable_usb_data_signaling_test">Disable USB data signaling</string> 4880 <string name="device_owner_disable_usb_data_signaling_test_info"> 4881 This test verifies that USB data signaling can be disabled by the device owner.\n 4882 1. Press the \"Go\" button to go to Settings. Go to Connected devices > USB and select use 4883 USB for \"File transfer/Android Auto\". Verify that you can mount the device as a USB drive 4884 on your desktop computer and access files from your phone through USB.\n 4885 2. Press the \"Disable USB data signaling\" button to disable USB data signaling on 4886 the device. When disabled, all USB data connections (except from charging functions) 4887 are prohibited.\n 4888 3. Press the \"Go\" button to go to Settings and confirm that the "USB" preferences in 4889 \"System > Developer Options\" cannot be selected and "USB" preference in 4890 \"Connected devices\" has disappeared.:\n 4891 - Connected devices > USB\n 4892 - System > Developer Options > USB debugging\n 4893 - System > Developer Options > Default USB configuration\n 4894 - System > Developer Options > Disable USB audio routing\n 4895 4. Verify that you cannot mount the device as a USB drive on your desktop computer and 4896 cannot access files from your phone through USB.\n 4897 5. Press the \"Enable USB data signaling\" button to re-enable USB data signaling and 4898 replug USB cable in the device. After that the "USB" preferences in 4899 \"System > Developer Options\" can be selected and "USB" preference in 4900 \"Connected devices\" has appeared.\n 4901 Please mark the test accordingly. 4902 </string> 4903 <string name="device_owner_enable_usb_data_signaling_test">Enable USB data signaling</string> 4904 4905 <string name="device_owner_required_password_complexity_test">Set required password complexity</string> 4906 <string name="device_owner_required_password_complexity_test_info"> 4907 This test verifies that required password complexity can be set by the device owner.\n 4908 1. Press the \"Set low required password complexity\" button.\n 4909 2. Press the \"Go\" button to go to Settings > Security > Screen lock. Verify that 4910 you have to set a pattern, PIN or password.\n 4911 3. Press the \"Set medium required password complexity\" button.\n 4912 4. Press the \"Go\" button to go to Settings > Security > Screen lock. Verify that 4913 you have to set a PIN without repeating (4444) or ordered (1234, 4321, 2468) sequences 4914 with a length of at least 4; or you have to set an alphabetic or alphanumeric password with 4915 a length of at least 4.\n 4916 5. Press the \"Set high required password complexity\" button.\n 4917 6. Press the \"Go\" button to go to Settings > Security > Screen lock. Verify that 4918 you have to set a PIN without repeating (4444) or ordered (1234, 4321, 2468) sequences 4919 with a length of at least 8; or you have to set an alphabetic or alphanumeric password with 4920 a length of at least 6.\n 4921 7. Press the \"Remove required password complexity\" button.\n 4922 8. Press the \"Go\" button to go to Settings > Security > Screen lock. Verify that 4923 you don\'t have to set a pattern, PIN or password.\n 4924 Please mark the test accordingly. 4925 </string> 4926 <string name="set_low_required_password_complexity">Set low required password complexity</string> 4927 <string name="set_medium_required_password_complexity">Set medium required password complexity</string> 4928 <string name="set_high_required_password_complexity">Set high required password complexity</string> 4929 <string name="remove_required_password_complexity">Remove required password complexity</string> 4930 4931 <string name="managed_user_test">Managed User</string> 4932 <string name="managed_user_positive_tests">Managed User positive tests</string> 4933 <string name="managed_user_positive_tests_instructions"> 4934 The positive managed user tests verify policies on a managed user created by a device owner. 4935 \n 4936 Press Go button to create a managed user, and you will be switched to the managed user 4937 automatically. Dismiss the keyguard and a \'Managed User Tests\' should launch.\n 4938 Follow the test instructions and press \'pass\' or \'fail\' to return to this screen.\n 4939 </string> 4940 <string name="managed_user_positive_tests_instructions" product="automotive"> 4941 The positive managed user tests verify policies on a managed user created by a device owner. 4942 \n 4943 Press Go button to create a managed user, and you will be switched to the managed user 4944 automatically; a \'Managed User Tests\' should launch.\n 4945 Follow the test instructions and press \'pass\' or \'fail\' to return to this screen.\n 4946 </string> 4947 <string name="managed_user_positive_tests_info"> 4948 The positive managed user tests verify policies on a managed user created by a device owner. 4949 Proceed to the test cases, then press \'pass\' or \'fail\' to finish this test. 4950 </string> 4951 <string name="managed_user_positive_category">Managed User Tests</string> 4952 <string name="managed_user_check_managed_user_test">Check affiliated profile owner</string> 4953 <string name="managed_user_incorrect_managed_user">Missing or incorrect affiliated profile owner: CTSVerifier is not affilaited PO!</string> 4954 4955 <string name="device_owner_disallow_user_switch">Disallow user switch</string> 4956 <string name="device_owner_disallow_user_switch_info"> 4957 Press \'Create uninitialized user\' to create a user that is not setup. 4958 Then press \'Set restriction\' button to set the user restriction. 4959 Then press \'Go\' to open multiple users settings. 4960 Confirm that:\n 4961 \n 4962 - Main switch is disabled and in off position\n 4963 \n 4964 In additional, if quick settings is available, confirm that user switcher is hidden or 4965 disabled. 4966 Use the Back button to return to this page. 4967 </string> 4968 <string name="device_owner_disallow_user_switch_create_user">Create uninitialized user</string> 4969 4970 <string name="device_owner_user_switcher_message">User switcher message</string> 4971 <string name="device_owner_user_switcher_message_info"> 4972 1. Please press the \'With user switcher message\' button to set the user switcher message. 4973 You will then be automatically switched to a secondary user. If a user switcher dialog shows 4974 up, it should read \'Start user session\'. Wait until you are automatically switched back to 4975 primary, if a user switcher dialog shows up, it should read \'End user session\'. 4976 4977 \n 4978 2. Please press the \'Without user switcher message\' button to clear the user switcher 4979 message. You will then be automatically switched to a secondary user. If a user switcher 4980 dialog shows up, it should read \'Switching to managed user\'. Wait until you are 4981 automatically switched back to primary, if a user switcher dialog shows up, it should read 4982 \'Switching to (name of primary user)\'. 4983 </string> 4984 <string name="device_owner_with_user_switcher_message">With user switcher message</string> 4985 <string name="device_owner_without_user_switcher_message">Without user switcher message</string> 4986 4987 <string name="device_owner_enable_logout">Logout</string> 4988 <string name="device_owner_enable_logout_info"> 4989 Please press the Go button to enable logout. You will then be switched to a newly created 4990 user. 4991 Look for a way to logout the current user without unlocking the lock screen. The control is 4992 usually named \'End session\'.\n 4993 The location may vary depending on manufacturer, typical locations are:\n 4994 - In power button menu by long pressing power button.\n 4995 - On the lock screen.\n 4996 \n 4997 When successfully logout and switched back to primary user, confirm that the logout control 4998 is not available in primary user. 4999 </string> 5000 5001 <!-- Strings for JobScheduler Tests --> 5002 <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> 5003 5004 <string name="js_idle_test">Idle Mode Constraints</string> 5005 <string name="js_start_test_text">Start test</string> 5006 <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> 5007 <string name="js_idle_description_1">Turn the screen off and then back on in order to begin.</string> 5008 <string name="js_idle_continue_instruction"> 5009 Switch off screen and wait for it to turn on to continue. 5010 </string> 5011 <string name="js_idle_item_idle_off">Idle job does not execute when device is not idle.</string> 5012 <string name="js_idle_item_idle_on">Idle job does execute when device is forced into idle.</string> 5013 5014 <string name="js_charging_test">Charging Constraints</string> 5015 <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> 5016 <string name="js_charging_description_1">Plug in the charger if it isn\'t already plugged in.</string> 5017 <string name="js_charging_off_test">Device not charging will not execute a job with a charging constraint.</string> 5018 <string name="js_charging_on_test">Device when charging will execute a job with a charging constraint.</string> 5019 <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> 5020 <string name="js_charging_description_3">Device is plugged in. Please wait while it gets into stable charging state.</string> 5021 <string name="js_charging_description_4">There seems to be a problem with your charger. Please try again.</string> 5022 5023 <string name="js_connectivity_test">Connectivity Constraints</string> 5024 <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> 5025 <string name="js_connectivity_description_1">Disable WiFi and Mobile data to begin.</string> 5026 <string name="js_unmetered_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 5027 <string name="js_any_connectivity_test">Device with no connectivity will not execute a job with an unmetered connectivity constraint.</string> 5028 <string name="js_no_connectivity_test">Device with no connectivity will still execute a job with no connectivity constraints.</string> 5029 5030 <!-- String for the bundled TV app Tests --> 5031 5032 <string name="tv_input_discover_test">3rd-party TV input test</string> 5033 <string name="tv_input_discover_test_info"> 5034 Verify that the bundled TV app launches via Intent and calls the proper API to discover 5035 3rd-party TV inputs. 5036 </string> 5037 <string name="tv_input_discover_test_third_party_tif_input_support"> 5038 Does the bundled TV app support third-party TV inputs? 5039 </string> 5040 <string name="tv_input_discover_test_go_to_setup"> 5041 Select the \"Launch TV app\" button and set up the newly installed TV input: 5042 \"CTS Verifier\". 5043 </string> 5044 <string name="tv_input_discover_test_verify_setup"> 5045 Setup activity must have been started. 5046 </string> 5047 <string name="tv_input_discover_test_tune_to_channel"> 5048 Select the \"Launch TV app\" button and tune to the \"Placeholder\" channel from \"CTS Verifier\" 5049 input. If necessary, configure the channel to be visible. 5050 </string> 5051 <string name="tv_input_discover_test_verify_tune"> 5052 Tune command must be called. 5053 </string> 5054 <string name="tv_input_discover_test_verify_overlay_view"> 5055 Verify that the overlay appears and displays the text \"Overlay View Placeholder Text\" when you tune 5056 to the \"Placeholder\" channel. 5057 </string> 5058 <string name="tv_input_discover_test_verify_size_changed"> 5059 Verify that video layout changes correctly according to the provided video track information, 5060 including pixel aspect ratio. 5061 </string> 5062 <string name="tv_input_discover_test_verify_global_search"> 5063 Verify the TV app provides query results for 3rd-party input\'s channels and programs in 5064 global search results. 5065 </string> 5066 <string name="tv_input_discover_test_go_to_epg"> 5067 Select the \"Launch EPG\" button and locate the \"Placeholder\" channel. 5068 </string> 5069 <string name="tv_input_discover_test_verify_epg"> 5070 Do you see the programs named \"Placeholder Program\" and their descriptions 5071 "Placeholder Program Description" in the EPG? 5072 </string> 5073 <string name="tv_input_discover_test_trigger_setup"> 5074 Select the \"Launch setup\" button and verify if the bundled TV app shows the list of installed 5075 TV inputs for setup. 5076 </string> 5077 <string name="tv_input_discover_test_verify_trigger_setup"> 5078 Do you see the \"CTS Verifier\" input in the list? 5079 </string> 5080 5081 <string name="tv_parental_control_test">TV app parental controls test</string> 5082 <string name="tv_parental_control_test_info"> 5083 Verify that the bundled TV app calls the parental controls API. 5084 </string> 5085 <string name="tv_parental_control_test_turn_on_parental_control"> 5086 Select the \"Launch TV app\" button and turn on the parental controls. If parental controls are 5087 on already, turn it off and on again. 5088 </string> 5089 <string name="tv_parental_control_test_verify_receive_broadcast1"> 5090 TV input service must have received ACTION_PARENTAL_CONTROLS_ENABLED_CHANGED broadcast. 5091 </string> 5092 <string name="tv_parental_control_test_check_parental_controls_switch"> 5093 Is there an option to turn off parental controls on this device? 5094 </string> 5095 <string name="tv_parental_control_test_block_tv_ma"> 5096 Select the \"Launch TV app\" button and block the \"Custom Rating\" for \"CtsVerifier\" rating 5097 system in the parental control settings. If the rating system is disabled by default, enable it. 5098 If the \"Custom Rating\" is already blocked, unblock it, save, and then block again. 5099 </string> 5100 <string name="tv_parental_control_test_verify_receive_broadcast2"> 5101 TV input service must have received ACTION_BLOCKED_RATINGS_CHANGED broadcast. 5102 </string> 5103 <string name="tv_parental_control_test_block_unblock"> 5104 Select the \"Launch TV app\" button; verify that the channel is blocked. 5105 Try to unblock the screen by entering PIN; verify that it\'s unblocked. 5106 </string> 5107 5108 <string name="tv_yes">Yes</string> 5109 <string name="tv_no">No</string> 5110 <string name="tv_none">None</string> 5111 <string name="tv_launch_tv_app">Launch TV app</string> 5112 <string name="tv_launch_epg">Launch EPG</string> 5113 <string name="tv_launch_setup">Launch setup</string> 5114 <string name="tv_channel_not_found"> 5115 CtsVerifier channel is not set up. Please set up before proceeding. 5116 </string> 5117 5118 <string name="tv_multiple_tracks_test">TV app closed captions and multi-audio test</string> 5119 <string name="tv_multiple_tracks_test_info"> 5120 Verify that the bundled TV app calls the multi-track API. 5121 </string> 5122 <string name="tv_multiple_tracks_test_select_subtitle"> 5123 Select the \"Launch TV app\" button. Verify that closed captions are off by default. Set closed 5124 caption language to English. 5125 </string> 5126 <string name="tv_multiple_tracks_test_verify_set_caption_enabled"> 5127 Captions are enabled. 5128 </string> 5129 <string name="tv_multiple_tracks_test_verify_select_subtitle"> 5130 The English closed caption track should be selected. 5131 </string> 5132 <string name="tv_multiple_tracks_test_select_audio"> 5133 Select the \"Launch TV app\" button. Verify that the audio track is English by default. 5134 Select Spanish audio track. 5135 </string> 5136 <string name="tv_multiple_tracks_test_verify_select_audio"> 5137 The Spanish audio track should be selected. 5138 </string> 5139 5140 <string name="tv_time_shift_test">TV app time shift test</string> 5141 <string name="tv_time_shift_test_info"> 5142 This test verifies that the TV app invokes proper time shift APIs in the framwork. 5143 </string> 5144 <string name="tv_time_shift_test_pause_resume"> 5145 Press the \"Launch TV app\" button. Verify that the playback control is available. 5146 Pause the playback and then resume it. 5147 </string> 5148 <string name="tv_time_shift_test_verify_resume_after_pause"> 5149 The playback should resume after pause. 5150 </string> 5151 <string name="tv_time_shift_test_verify_position_tracking"> 5152 The playback position tracking should be activated. 5153 </string> 5154 <string name="tv_time_shift_test_speed_rate"> 5155 Press the \"Launch TV app\" button. Verify that the playback control is available. 5156 Rewind the playback and in a few seconds fast-forward it. 5157 </string> 5158 <string name="tv_time_shift_test_verify_rewind"> 5159 The playback should rewind. 5160 </string> 5161 <string name="tv_time_shift_test_verify_fast_forward"> 5162 The playback should fast-forward. 5163 </string> 5164 <string name="tv_time_shift_test_seek"> 5165 Press the \"Launch TV app\" button. Verify that the playback control is available. 5166 Seek to previous and then seek to next. 5167 </string> 5168 <string name="tv_time_shift_test_verify_seek_to_previous"> 5169 The playback position should be moved to the previous position. 5170 </string> 5171 <string name="tv_time_shift_test_verify_seek_to_next"> 5172 The playback position should be moved to the next position. 5173 </string> 5174 5175 <string name="tv_app_link_test">TV app app-link test</string> 5176 <string name="tv_app_link_test_info"> 5177 Verify that the bundled TV app supports linking to channel apps. If a TV input service provides 5178 links for its specific channels, the TV app should show the links in a proper format. 5179 </string> 5180 <string name="tv_app_link_test_select_app_link"> 5181 Select the \"Launch TV app\" button, then check if you can see a menu with \"Cts App-Link Text\" 5182 text in red background. If you see the link, select it to follow the link. 5183 </string> 5184 <string name="tv_app_link_test_verify_link_clicked"> 5185 The app-link must have been clicked and the activity should be changed correctly. 5186 </string> 5187 <string name="tv_input_link_test_verify_link_interface"> 5188 Do you see the app-link card similar to the image on the left?\n 5189 1) You should see the poster art image, but the color may be different.\n 5190 2) You should see the text \"Cts App-Link Text\".\n 5191 </string> 5192 5193 <string name="tv_microphone_device_test">Microphone device test</string> 5194 <string name="tv_microphone_device_test_info"> 5195 This test checks if InputDevice.hasMicrophone of the Media API reports a 5196 correct value on every input device (including remote controls). 5197 </string> 5198 <string name="tv_microphone_device_test_prep_question"> 5199 Before continuing, please make sure that you pair all primary input 5200 devices intended to be used by the device, including bluetooth 5201 remotes and companion remote-control apps such as the Android TV Remote Control. 5202 Have you paired every primary input device with the device under test (DUT)? 5203 </string> 5204 <string name="tv_microphone_device_test_mic_question"> 5205 Does input device \"%1$s\" have a microphone? 5206 </string> 5207 <string name="tv_microphone_device_test_negative_mismatch"> 5208 InputDevice.hasMicrophone reports that this input device DOES have a 5209 microphone whereas you selected that it does not. Please correct it by 5210 declaring \"audio.mic = 0\" in the device\'s input device configuration 5211 (.idc) file. 5212 </string> 5213 <string name="tv_microphone_device_test_positive_mismatch"> 5214 InputDevice.hasMicrophone reports that this input device does NOT have a 5215 microphone whereas you selected that it does. Please correct it by 5216 declaring \"audio.mic = 1\" in the device\'s input device configuration 5217 (.idc) file and make sure that relevant files such as key layout (.kl) 5218 and key character map (.kcm) files are found by the system accordingly. 5219 </string> 5220 <string name="tv_microphone_device_test_no_input_devices">No input devices found.</string> 5221 5222 <!-- Common strings for the TV Display tests --> 5223 <string name="tv_start_test">Start Test</string> 5224 <string name="tv_done">Done</string> 5225 5226 <!-- Hotplug Test --> 5227 <string name="tv_hotplug_test">Hotplug Test</string> 5228 <string name="tv_hotplug_test_info">This test checks whether DisplayManager responds correctly 5229 to plugging and unplugging the HDMI cable. 5230 </string> 5231 <string name="tv_hotplug_disconnect_display"> 5232 Press the "%1$s" button, disconnect the HDMI cable, wait 2 seconds and then connect the HDMI 5233 cable again. 5234 </string> 5235 5236 <!-- Mode Switching Test --> 5237 <string name="tv_mode_switching_test">Mode switching test</string> 5238 <string name="tv_mode_switching_test_step_instruction"> 5239 Click "Start Test" and then observe the video below. Testing transition from %1$s to %2$s. 5240 </string> 5241 <string name="tv_mode_switching_test_black_screen_question"> 5242 Did the video playback experience an interruption, for example, a black or solid color 5243 screen? 5244 </string> 5245 <string name="tv_mode_switching_test_is_video_ok"> 5246 Does the video look okay? Click "No" if the video is not playing, there was a snow screen, 5247 audio static, wrong colors, the video is displaced compared to before running the test or 5248 if the video is not playing. Keep in mind that some stutter is expected when the video does 5249 not match the refresh rate. 5250 </string> 5251 <string name="tv_mode_switching_test_mode_switch_step">Mode switch step</string> 5252 5253 <string name="overlay_view_text">Overlay View Placeholder Text</string> 5254 <string name="custom_rating">Example of input app specific custom rating.</string> 5255 5256 <!-- A list of fully-qualified test classes that should not be run. --> 5257 <string-array name="disabled_tests"> 5258 <item>com.android.cts.verifier.telecom.CtsVerifierInCallUi</item> 5259 <item>com.android.cts.verifier.car.CarDockActivity</item> 5260 <item>com.android.cts.verifier.car.CarDockTestActivity</item> 5261 </string-array> 5262 5263 <!-- Strings for screen pinning test --> 5264 <string name="screen_pinning_test">Screen Pinning Test</string> 5265 <string name="screen_pin_instructions">Pressing next will prompt you to enter screen pinning, allow this app to enter screen pinning.</string> 5266 <string name="screen_pin_check_pinned">Press Next to verify the app is pinned.</string> 5267 <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> 5268 <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> 5269 5270 <string name="error_screen_no_longer_pinned">The screen was no longer pinned.</string> 5271 <string name="error_screen_already_pinned">Cannot start the test with the screen already pinned.</string> 5272 <string name="error_screen_pinning_did_not_start">Screen was not pinned.</string> 5273 <string name="error_screen_pinning_did_not_exit">Screen was not unpinned.</string> 5274 <string name="error_screen_pinning_couldnt_exit">Could not exit screen pinning through API.</string> 5275 5276 <!-- Audio Devices Notifications Tests --> 5277 <string name="audio_devices_notification_instructions"> 5278 Connect and disconnect a wired headset. 5279 Note if the appropriate notification messages appear below. 5280 The \"Pass\" button will be enabled if device connect and disconnect messages are received. 5281 </string> 5282 <string name="audio_dev_notification_clearmsgs">Clear Messages</string> 5283 <string name="audio_dev_notification_connectMsg">CONNECT DETECTED - %1$S</string> 5284 <string name="audio_dev_notification_disconnectMsg">DISCONNECT DETECTED - %1$S</string> 5285 5286 <string name="audio_out_devices_notifications_test">Audio Output Devices Notifications Test</string> 5287 <string name="audio_out_devices_infotext">Tests whether wired output peripheral 5288 connect/disconnect notifications are correctly sent when output peripherals are 5289 connected or disconnected. A \"wired output peripheral\" can be a headset or headphones 5290 connected to an analog 3.5mm jack or the USB port or a USB audio interface connected to 5291 the USB port. 5292 \n\nTest Setup: 5293 \nDisconnect any wired audio peripherals. 5294 \n\nTest Process: 5295 \n1. Verify that the DUT supports USB or Analog audio peripherals. 5296 \n2. Press the \"Clear Messages\" button to clear any previously sent \"sticky\" notifications. 5297 \n3. Connect a wired output peripheral. A connect message should appear. Disconnect the 5298 audio peripheral. A disconnect message should appear. 5299 \n\nTest Criteria: 5300 \nThe test passes if either the device DOES NOT support wired output peripherals, or both 5301 the connect and disconnect notifications are received. 5302 </string> 5303 5304 <string name="audio_in_devices_notifications_test">Audio Input Devices Notifications Test</string> 5305 <string name="audio_in_devices_infotext">Tests whether wired input peripheral 5306 connect/disconnect notifications are correctly sent when input peripherals are 5307 connected or disconnected. A \"wired input peripheral\" can be a headset connected to an 5308 analog 3.5mm jack or the USB port or a USB audio interface connected to the USB port. 5309 \n\nTest Setup: 5310 \nDisconnect any wired audio peripherals. 5311 \n\nTest Process: 5312 \n1. Verify that the DUT supports USB or Analog audio peripherals. 5313 \n2. Press the \"Clear Messages\" button to clear any previously sent \"sticky\" notifications. 5314 \n3. Connect a wired output peripheral. A connect message should appear. Disconnect the 5315 audio peripheral. A disconnect message should appear. 5316 \n\nTest Criteria: 5317 \nThe test passes if either the device DOES NOT support wired output peripherals, or both 5318 the connect and disconnect notifications are received. 5319 </string> 5320 5321 <string name="audio_input_routingnotifications_test">Audio Input Routing Notifications Test</string> 5322 <string name="audio_input_routingnotification_instructions"> 5323 Test whether appropriate routing notifications are sent when audio input peripherals are 5324 connected to the device. 5325 \n\nTest Setup: 5326 \nDisconnect any wired audio peripherals. 5327 \n\nTest Process: 5328 \n1. Connect a wired input peripheral. A connection routing message should appear. 5329 \n\nTest Criteria: 5330 \nThe test passes if either the device DOES NOT support wired input peripherals, or 5331 the routing notifications are received. 5332 </string> 5333 <string name="audio_output_routingnotifications_test">Audio Output Routing Notifications Test</string> 5334 <string name="audio_output_routingnotification_instructions"> 5335 Test whether appropriate routing notifications are sent when audio output peripherals are 5336 connected to the device. 5337 \n\nTest Setup: 5338 \nDisconnect any wired audio peripherals. 5339 \n\nTest Process: 5340 \n1. Connect a wired output peripheral. A connection routing message should appear. 5341 \n\nTest Criteria: 5342 \nThe test passes if either the device DOES NOT support wired output peripherals, or 5343 the routing notifications are received. 5344 </string> 5345 <string name="audio_routingnotification_header">Routing Notifications:</string> 5346 <string name="audio_routingnotification_trackRoutingMsg">AudioTrack rerouting</string> 5347 <string name="audio_routingnotification_recordRoutingMsg">AudioRecord rerouting</string> 5348 <string name="audio_routingnotification_nosupport">No Support</string> 5349 <string name="audio_routingnotification_supported">Supported</string> 5350 <string name="audio_routingnotification_supportundetermined">Support Undetermined</string> 5351 <string name="audio_routingnotification_devicesupportcr">Device Support\n</string> 5352 <string name="audio_routingnotification_analogheadsetcolon">Analog Headset: </string> 5353 <string name="audio_routingnotification_usbheadsetcolon">USB Headset: </string> 5354 <string name="audio_routingnotification_usbdevicecolon">USB Device: </string> 5355 <string name="audio_routingnotification_connected">Connected</string> 5356 <string name="audio_routingnotification_passmessage">Test PASSES - Routing notification received</string> 5357 5358 <!-- USB Audio Peripheral Tests --> 5359 <string name="profileLabel">Profile</string> 5360 <string name="connectedPeripheral">Connected Peripheral</string> 5361 <string name="audio_uap_attribs_test">USB Audio Peripheral Attributes Test</string> 5362 <string name="audio_uap_notifications_test">USB Audio Peripheral Notifications Test</string> 5363 <string name="uapPeripheralProfileAttributes">USB Audio Peripheral Attributes</string> 5364 <string name="audio_uap_play_test">USB Audio Peripheral Play Test</string> 5365 <string name="uapPlayStopTestInstructions">Connect the USB Audio Interface Peripheral and press the 5366 PLAY button below. Verify that a tone is correctly played. Then press the STOP button. 5367 </string> 5368 <string name="audio_uap_play_playBtn">Play</string> 5369 <string name="audio_uap_play_stopBtn">Stop</string> 5370 5371 <string name="audio_uap_record_test">USB Audio Peripheral Record Test</string> 5372 <string name="audio_uap_record_recordBtn">Record</string> 5373 <string name="audio_uap_record_recordLoopbackBtn">Record Loopback</string> 5374 <string name="audio_uap_record_stopBtn">Stop</string> 5375 5376 <string name="audio_uap_buttons_test">USB Audio Peripheral Buttons Test</string> 5377 <string name="uapButtonTestInstructions">Connect the USB Audio headset with buttons 5378 and press each button on the headset to verify recognition.</string> 5379 5380 <string name="uapNotificationsTestInfo"> 5381 This test verifies that the correct notifications and Intents are sent when a USB audio 5382 peripheral is connected to the Android device. First USB headset peripheral should be 5383 connected and the test will acknowledge the USB headset device notifications and plug intent. 5384 Next a non-headset / headphones USB peripheral should be connected and the test will 5385 acknowlege the USB device notifications. If all notifications and Intents are received 5386 the test passes. 5387 </string> 5388 5389 <string name="audio_usb_restrict_record_test">USB Audio Restrict Record Access Test</string> 5390 <string name="audio_usb_restrict_record_entry"> 5391 Tests whether the appropriate warning message is displayed when an app which has 5392 not been granted RECORD permission could potentially record audio through the raw USB API. 5393 \n\nTest Setup: 5394 \n1. Exit CTS-Verifier with the Home button 5395 \n2. Go to Android Settings 5396 \n3. Select Apps & notifications 5397 \n4. Select CTS Verifier 5398 \n5. Select Permissions 5399 \n6. Deny Microphone permission 5400 \n7. Start CTS Verifier. Ignore the \"Please grant all permissions\" message by clicking on the 5401 face of the CTS Verifier (not in the dialog). 5402 \n8. Run this test 5403 \n\nTest Process: 5404 \nConnect a USB peripheral with CAPTURE capability and press the \"Test\" button. 5405 \n\nTest Criteria: 5406 \nThe access permission API should present a warning message about potential dangerous 5407 access. If so, the test passes. If you do not see this warning, the test fails. 5408 \n\nPost-test completion: 5409 \n1. Exit CTS-Verifier with the Home button 5410 \n2. Reenable Microphone permission in Android Settings 5411 </string> 5412 5413 <string name="audio_usb_restrict_permission_info"> 5414 The test can only be run with Microphone permission DENIED. 5415 \n\nTo run this test: 5416 \n1. Exit CTS-Verifier with the Home button 5417 \n2. Go to Android Settings 5418 \n3. Select Apps & notifications 5419 \n4. Select CTS Verifier 5420 \n5. Select Permissions 5421 \n6. Deny Microphone permission 5422 \n7. Start CTS Verifier. Ignore the \"Please grant all permissions\" message by clicking on the 5423 ace of the CTS Verifier (not in the dialog). 5424 \n8. Run this test 5425 \n\nWhen complete: 5426 \n1. Exit CTS-Verifier with the Home button 5427 \n2. Reenable Microphone permission in Android Settings 5428 </string> 5429 5430 <string name="usb_restrictrecord_instructions"> 5431 Permissions for CTS Verifier are correctly set to run this test.\n\n 5432 Connect a USB peripheral with CAPTURE capability. Press the "Test" button and verify that 5433 a warning is shown in the device access UI. 5434 </string> 5435 5436 <string name="uapButtonsBtnALbl">Button A - play/pause</string> 5437 <string name="uapButtonsBtnBLbl">Button B - volume up (+)</string> 5438 <string name="uapButtonsBtnCLbl">Button C - volume down (-)</string> 5439 <string name="uapButtonsBtnDLbl">Button D - voice assist</string> 5440 <string name="uapButtonsRecognized">Recognized</string> 5441 <string name="uapButtonsNotRecognized">Not Recognized</string> 5442 <string name="uapButtonsDisableAssistantTitle">Disable Google Assistant</string> 5443 <string name="uapButtonsDisableAssistant">For this test to succeed it may be necessary 5444 to disable the Google Assistant (Settings / Google / Search / Google Assistant Settings / 5445 Devices / <device name> / Google Assistant)</string> 5446 5447 <!-- Pro Audio Tests --> 5448 <string name="pro_audio_latency_test">Pro Audio Test</string> 5449 5450 <string name="proAudioHasProAudiolbl">Has Pro Audio:</string> 5451 <string name="proAudioHasLLAlbl">Has Low-Latency Audio:</string> 5452 <string name="audioLoopbackInputLbl">Audio Input:</string> 5453 <string name="audioLoopbackOutputLbl">Audio Output:</string> 5454 <string name="proAudioMidiHasMIDILbl">Has MIDI Support:</string> 5455 <string name="proAudioMidiHasUSBHostLbl">USB Host Mode:</string> 5456 <string name="proAudioMidiHasUSBPeripheralLbl">USB Peripheral Mode:</string> 5457 <string name="proAudioHDMISupportLbl">HDMI Support:</string> 5458 <string name="proAudioHasHDMICheckBox">Has HDMI Support</string> 5459 5460 <string name="audio_proaudio_NA">N/A</string> 5461 <string name="audio_proaudio_hdmiPending">pending...</string> 5462 <string name="audio_proaudio_hdmiNotFound">No HDMI detected.</string> 5463 5464 <string name="audio_proaudio_nopa_title">Pro Audio Test</string> 5465 <string name="audio_proaudio_nopa_message">This device does not set the FEATURE_AUDIO_PRO 5466 flag and therefore does not need to run this test.</string> 5467 5468 <string name="hdmi_insufficient">The Connected HDMI device does not meet CDD requirements</string> 5469 5470 <!-- Various test status strings --> 5471 <string name="audio_proaudio_pass">Pass</string> 5472 <string name="audio_proaudio_latencytoohigh">Latency is too high</string> 5473 <string name="audio_proaudio_confidencetoolow">"Insufficient Confidence value"</string> 5474 <string name="audio_proaudio_midinotreported">"No MIDI support reported"</string> 5475 <string name="audio_proaudio_usbhostnotreported">"No USB Host Mode support reported"</string> 5476 <string name="audio_proaudio_usbperipheralnotreported">"No USB Peripheral Mode support reported"</string> 5477 5478 <!-- MIDI Test --> 5479 <string name="midi_test">MIDI Test</string> 5480 <string name="midi_java_test">Java MIDI Test</string> 5481 <string name="midi_native_test">Native MIDI Test</string> 5482 5483 <string name="midi_info"> 5484 Tests for basic MIDI functionality. 5485 \n\n1. Test Setup - USB MIDI: 5486 \nConnect a supported USB Audio Peripheral device that has standard MIDI 5-pin, DIN (round) 5487 connectors and a standard MIDI cable. The cable must be connected to the MIDI input and 5488 output jacks on the peripheral. 5489 \n\n2. Test Setup - Bluetooth MIDI: 5490 \na. Download and install the "MIDI+BTLE" app from the Play Store. 5491 \nb. Connect a supported USB Audio Peripheral device that has standard MIDI 5-pin, DIN (round) 5492 connectors and connect the MIDI ports to a Bluetooth MIDI adapter (such as the Yamaha 5493 MD-BT01). Be sure to connect the MD-BT01 so that the arrow on the MD-BT01 plug points away 5494 from the Output jack on the USB peripheral. The other plug should have an arrow pointing 5495 towards the Input jack. 5496 \nc. Run the \"MIDI+BTLE\" app, click on "Bluetooth Scan" and select the Bluetooth MIDI adapter 5497 connected to the USB Audio Peripheral. Note that the \"Test Bluetooth MIDI Interface\" 5498 button will be enabled. 5499 \n\n2. Test Setup - Virtual MIDI: 5500 \nThe Virtual MIDI test does not require any MIDI interface hardware. 5501 \n\nTest Process: 5502 \n1. Follow instructions for \"Test Setup - USB MIDI\" 5503 \n2. Press the \"Test US MIDI Interface\" button. Note test results. 5504 \n3. Press the \"Test Virtual MIDI Interface\" button. Note test results. 5505 \n4. Follow instructions for \"Test Setup - Bluetooth MIDI\" 5506 \n5. Press the \"Test Bluetooth MIDI Interface\" button. Note test results. 5507 \n\nTest Criteria: 5508 \nAll sub-tests must pass for this test to pass. 5509 </string> 5510 <string name="analog_headset_test_info_tv">This test tests the following functionality with respect to wired analog headsets.\n 5511 1. Correct audio playback.\n 5512 2. Plug intents.\n 5513 \nTo execute test:\n 5514 1. Plug in an Android-compatible, analog headset. Verify connection/recognition.\n 5515 2. Play test tone and verify correct behavior.\n 5516 \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 5517 \n(see <a href="https://source.android.com/devices/accessories/headset/plug-headset-spec">3.5 mm Headset: Accessory Specification</a> and 5518 <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>) 5519 </string> 5520 5521 <string name="usb_midi_audio_test">USB MIDI and Audio Test</string> 5522 <string name="usb_midi_audio_info"> 5523 Connect a supported USB Audio Peripheral device that has standard MIDI 5-pin, DIN (round) 5524 connectors and a standard MIDI cable. The cable must be connected to the MIDI input and 5525 output jacks on the peripheral. 5526 \nPlease attach a wired headset with a 3.5mm jack to the audio output of this peripheral. 5527 \nTest the USB MIDI interface first. Then, press the PLAY to button test audio. Verify 5528 that a tone is correctly played. 5529 </string> 5530 <string name="midiUSBAudioTestLbl">USB Audio Playback Test:</string> 5531 5532 <string name="midiHasMIDILbl">Has MIDI Support</string> 5533 5534 <string name="midiUSBTestLbl">USB MIDI Loopback Test:</string> 5535 <string name="usbMidiInputLbl">USB Input:</string> 5536 <string name="usbMidiOutputLbl">USB Output:</string> 5537 <string name="midiTestUSBInterfaceBtn">Test USB MIDI Interface</string> 5538 5539 <string name="midiVirtTestLbl">Virtual MIDI Loopback Test:</string> 5540 <string name="midiVirtInputLbl">Virtual Input:</string> 5541 <string name="midiVirtOutputLbl">Virtual Output:</string> 5542 <string name="midiTestVirtInterfaceBtn">Test Virtual MIDI Interface</string> 5543 5544 <string name="midiBTTestLbl">Bluetooth MIDI Loopback Test:</string> 5545 <string name="midiBTInputLbl">Bluetooth Input:</string> 5546 <string name="midiBTOutputLbl">Bluetooth Output:</string> 5547 <string name="midiTestBTInterfaceBtn">Test Bluetooth MIDI Interface</string> 5548 5549 <string name="midiStatusLbl">Status</string> 5550 <string name="midiNotRunLbl">Not Run.</string> 5551 <string name="midiPassedLbl">Passed.</string> 5552 <string name="midiFailedMismatchLbl">Failed - Data Mismatch.</string> 5553 <string name="midiFailedTimeoutLbl">Failed - Timeout.</string> 5554 <string name="midiFailedOverrunLbl">Failed - Data Overrun.</string> 5555 <string name="midiFailedDeviceLbl">Failed - Device Error.</string> 5556 <string name="midiFailedJNILbl">Failed - JNI Error.</string> 5557 <string name="midiFailedSetupLbl">Failed - Error in Setup.</string> 5558 <string name="midiFailedSendLbl">Failed - Error during Send.</string> 5559 5560 <!-- Audio general text --> 5561 <string name="audio_wired_exists">Does this device support wired USB or Analog audio peripherals?</string> 5562 <string name="audio_wired_no">No</string> 5563 <string name="audio_wired_yes">Yes</string> 5564 <string name="audio_general_deficiency_found">WARNING: Some results show potential deficiencies on the system. 5565 Please consider addressing them for a future release.</string> 5566 <string name="audio_general_test_passed">Test Result: Successful</string> 5567 <string name="audio_general_test_failed">Test Result: Not Optimal</string> 5568 <string name="audio_general_default_false_string">false</string> 5569 <string name="audio_general_default_true_string">true</string> 5570 <string name="audio_general_warning">Warning</string> 5571 <string name="audio_general_level_not_max">Audio Level is not maximum. Please check your device 5572 is set to max level for audio playback.</string> 5573 5574 <string name="audio_general_no">No</string> 5575 <string name="audio_general_yes">Yes</string> 5576 <string name="audio_general_info">Info</string> 5577 <string name="audio_general_ok">Ok</string> 5578 <string name="audio_general_start">Start</string> 5579 <string name="audio_general_stop">Stop</string> 5580 <string name="audio_general_done">Done</string> 5581 <string name="audio_general_close">Close</string> 5582 <string name="audio_general_status">Status</string> 5583 <string name="audio_general_pass">PASS</string> 5584 <string name="audio_general_teststatus_pass">Test Status: PASS</string> 5585 <string name="audio_general_fail">FAIL</string> 5586 <string name="audio_general_teststatus_fail">Test Status: FAIL</string> 5587 <string name="audio_general_not_tested">Not Tested</string> 5588 <string name="audio_general_not_required">Please Test If Supported</string> 5589 <string name="audio_general_required">Required</string> 5590 <string name="audio_general_nohardware">No supporting hardware.</string> 5591 <string name="audio_general_unknownhardware">Unknown hardware support. Please test if supported.</string> 5592 <string name="audio_general_run">Run</string> 5593 <string name="audio_general_cancel">Cancel</string> 5594 <string name="audio_general_left">Left</string> 5595 <string name="audio_general_right">Right</string> 5596 <string name="audio_general_Input">Input</string> 5597 <string name="audio_general_inputcolon">Input:</string> 5598 <string name="audio_general_Output">Output</string> 5599 <string name="audio_general_outputcolon">Output:</string> 5600 5601 <string name="audio_general_record">Record</string> 5602 <string name="audio_general_play">Play</string> 5603 5604 <string name="audio_general_JavaApi">Java API</string> 5605 <string name="audio_general_NativeApi">Native API</string> 5606 5607 <string name="audio_general_clear_results">Clear Results</string> 5608 5609 <string name="audio_general_test_not_run">Test Not Run</string> 5610 <string name="audio_general_testnotcompleted">Test not completed.</string> 5611 5612 <string name="audio_general_reportlogtest">[Can\'t Write ReportLog]</string> 5613 5614 <string name="audio_general_play_colon"> play:</string> 5615 <string name="audio_general_record_colon"> record:</string> 5616 5617 <string name="audio_general_results">Results</string> 5618 5619 <string name="audio_general_supporteddevices">Supported Devices</string> 5620 <string name="audio_general_availabledevices">Available Devices</string> 5621 <string name="audio_general_inputscolon">Inputs:</string> 5622 <string name="audio_general_outputscolon">Outputs:</string> 5623 5624 <!-- Audio Data Paths Test--> 5625 <string name="audio_datapaths_clearresults">Clear Results</string> 5626 <string name="audio_datapaths_legacy">Legacy</string> 5627 <string name="audio_datapaths_mmap_shared">MMAP Shared</string> 5628 <string name="audio_datapaths_mmap_exclusive">MMAP Exclusive</string> 5629 <string name="audio_datapaths_invalid_transfer">Invalid Transfer Type</string> 5630 5631 <string name="audio_datapaths_calibrate">Calibrate Audio</string> 5632 <string name="audio_datapaths_devices">Audio Devices</string> 5633 <string name="audio_datapaths_calibratetitle">Calibrate Loopback Audio</string> 5634 5635 <string name="audio_devicesupport_title">Audio Devices</string> 5636 <string name="audio_devicesupport_cantdetermine">Audio device support could not be determined.</string> 5637 5638 <string name="audio_supported_devices_explain">This is a list of audio devices which are 5639 supported by the hardware of this Android device. This includes both built-in 5640 devices and audio peripherals that can be connected. A given audio device may or may 5641 not be available, i.e. an audio peripheral device may or may not be actually connected 5642 to the Android device. 5643 </string> 5644 5645 <string name="audio_available_devices_explain">This is a list of currently available audio devices. 5646 It contains both built-in audio devices and any audio peripherals that are currently connected 5647 to this Android device. The contents of this list will change as audio peripherals are connected 5648 and disconnected. 5649 </string> 5650 5651 <string name="audio_exempt_nonhandheld">This is a non-handheld device and is exempt from this test. 5652 Press the \"Pass\" button (below) to continue.</string> 5653 5654 <string name="audio_datapaths_speakermic_test">Audio Data Paths Speaker/Mic Test</string> 5655 <string name="audio_datapaths_speakermic_info">This test verifies basic functionality over a set of audio routes 5656 \n\nTest Setup: 5657 \n • It may be necessary to go to the \"Sound & vibration\" settings panel to set the volume level for the output device. 5658 \n With no audio peripherals connected, adjust the \"Media volume\" to max. 5659 \n The test will display valid data paths with an asterisk appended to the data path name. 5660 \n\nTest Execution: 5661 \n • Place the device on a flat surface in a quiet room. 5662 \n • Select the \"Native API\" button. 5663 \n • Press the \"Start\" button. The test will step through the list of valid data paths playing a tone and noting its presence or absence. 5664 \n • Select the \"Java API\" button. 5665 \n • Press the \"Start\" button to repeat each data path test for the Java API. 5666 \n\nTest Completion: 5667 \n • Once each of the data paths and APIs have been measured, the test can be marked successful. 5668 </string> 5669 5670 <string name="audio_datapaths_mic">Mic:</string> 5671 <string name="audio_datapaths_speaker">Speaker:</string> 5672 <string name="audio_datapaths_MMAP">MMAP:"</string> 5673 <string name="audio_datapaths_MMAP_exclusive">MMAP Exclusive:"</string> 5674 <string name="audio_datapaths_analog_test">Audio Data Paths Analog Jack Test</string> 5675 <string name="audio_datapaths_analog_info">This test verifies basic functionality over a set of audio routes 5676 \n\nNote that if the DUT does not have an analog headset port, this test can be skipped. 5677 \n\nTest Setup: 5678 \n • It may be necessary to go to the \"Sound & vibration\" settings panel to set the volume level for each output device. 5679 \n • Insert the analog loopback adapter into the 3.5mm headset jack and adjust the \"Media volume\" to max. 5680 \n • Leave the loopback adapter in the jack. (See the \"Audio Loopback Latency Test\" for a description). 5681 \n The test will display valid data paths with an asterisk appended to the data path name. 5682 \n\nTest Execution: 5683 \n • Select the \"Native API\" button. 5684 \n • Press the \"Start\" button. The test will step through the list of valid data paths playing a tone and noting its presence or absence. 5685 \n • Select the \"Java API\" button. 5686 \n • Press the \"Start\" button to repeat each data path test for the Java API. 5687 \n\nTest Completion: 5688 \n • Once each of the data paths and APIs have been measured, the test can be marked successful. 5689 </string> 5690 5691 <string name="audio_datapaths_analog_nodevices">There are no peripherals currently available for this test. 5692 Please insert an Analog Loopback Plug into the Analog Headset Jack and run the test.</string> 5693 5694 <string name="audio_datapaths_analog_noanalogjack">This device does not have an Analog Headset Jack. A PASS is automatically granted.</string> 5695 <string name="audio_datapaths_analog_headsetundetermined">Support for an Analog Headset Jack could not be determined. 5696 If an Analog Headset Jack is available, please insert an Analog Loopback Plug and run the test.</string> 5697 <string name="audio_datapaths_analog_autopass">Non-Handheld device. A PASS is automatically granted.</string> 5698 5699 <string name="audio_datapaths_USB_test">Audio Data Paths USB Test</string> 5700 <string name="audio_datapaths_USB_info">This test verifies basic functionality over a set of audio routes 5701 \nTest Setup: 5702 \n • It may be necessary to go to the \"Sound & vibration\" settings panel to set the volume level for each output device. 5703 \n • Connect a USB audio interface with loopback cabling and adjust the \"Media volume\" to max. 5704 \n The test will display valid data paths with an asterisk appended to the data path name. 5705 \n\nTest Execution: 5706 \n • Select the \"Native API\" button. 5707 \n • Press the \"Start\" button. The test will step through the list of valid data paths playing a tone and noting its presence or absence. 5708 \n • Select the \"Java API\" button. 5709 \n • Press the \"Start\" button to repeat each data path test for the Java API. 5710 \n\nTest Completion: 5711 \n • Once each of the data paths and APIs have been measured, the test can be marked successful. 5712 </string> 5713 <string name="audio_datapaths_usb_nodevices">There are no peripherals currently available for this test. 5714 Please connect each type of USB Audio Peripheral and run the test for each type.</string> 5715 <string name="audio_datapaths_usb_nextperipheral">Please connect the next USB peripheral to be tested and 5716 run the test again.</string> 5717 5718 <string name="audio_datapaths_usb_nosupport">This device does not have a host-mode USB port. A PASS is automatically granted.</string> 5719 <string name="audio_datapaths_usb_undetermined">Support for host-mode USB could not be determined. 5720 If available, connect each type of USB Audio Peripheral and run the test for each type.</string> 5721 5722 <string name="audio_datapaths_noio">"No valid datapaths. PASS."</string> 5723 <string name="audio_datapaths_results">%1$s\n%2$s -> %3$s</string> 5724 5725 <string name="audio_loopback_calibrate_default">Default</string> 5726 <string name="audio_loopback_running">Running…</string> 5727 5728 <!-- USB Device Warning Dialog --> 5729 <string name="usbwarning_message_caption">USB Headset Adapter Warning</string> 5730 <string name="usbwarning_message_heading">Unvalidated USB Audio Adapter</string> 5731 <string name="usbwarning_paragraph_0">The connected USB audio device has not been verified for 5732 use in this test.</string> 5733 <string name="usbwarning_paragraph_1_1">The test may pass using this USB peripheral. 5734 However, some adapters have been seen to implement noise 5735 suppression and/or echo cancellation, or introduce significant latency that 5736 may cause the test to fail. If the test does not pass with this adapter, 5737 you should obtain the</string> 5738 <string name="usbwarning_googadapter">Google USB-C to 3.5mm Adapter</string> 5739 <string name="usbwarning_paragraph_1_2">for use in this test.</string> 5740 5741 <!-- Immersive Audio Test --> 5742 <string name="immersive_audio_test">Immersive Audio Test</string> 5743 <string name="immersive_audio_test_info">This test verifies that the Immersive Audio Test has 5744 been run on the associated test fixture and includes the results in the CTS Verifier report 5745 sent to Google. 5746 If you are not testing an Immersive audio device on the associated fixture, you are not 5747 required to run this test and so can simply press the PASS button. 5748 </string> 5749 <string name="immersive_audio_onscreen_instructions">Invoke this test from the Immersive Audio test fixture. 5750 If you are not testing an Immersive Audio device, and the DUT DOES NOT support low-latency head tracking, 5751 simply press the PASS button. If you are not testing an Immersive Audio device, and the DUT DOES support 5752 low-latency head tracking, you must exit by pressing the BACK button. 5753 </string> 5754 <string name="immersive_audio_noheadtracking">"This Android device does not support low-latency headtracking."</string> 5755 5756 <!-- Audio Loopback Latency Test --> 5757 <string name="audio_loopback_latency_test">Audio Loopback Latency Test</string> 5758 <string name="audio_loopback_info">This test verifies that the DUT can achieve the required or 5759 recommended loopback latency as defined by CDD § 5.6 (Audio Latency) and 5760 § 5.10 (Professional Audio). 5761 \nTo pass the test, the DUT needs to meet the latency requirement on ALL 3 of the 5762 following audio paths (if present): 5763 \n- the internal speaker and microphone. 5764 \n- a <a href="https://source.android.com/devices/audio/latency/loopback">Loopback Plug</a> connected to a 3.5mm headset jack. 5765 \n- a <a href="https://source.android.com/devices/audio/latency/loopback">Loopback Plug</a> connected to a USB audio adapter. 5766 (or alternatively USB interface with patch cords connecting the input and output jacks). 5767 \nPlease connect these Loopback mechanisms (the same Loopback Plug can be used at different times 5768 for the headset jack and USB audio adapter) and proceed with the instructions 5769 on the screen. The volume may need to be adjusted for each audio path. 5770 \nNote that for the Speaker/Microphone path, it may be necessary to remove any phone case on the device. 5771 \nThe system will measure the input-output audio latency by injecting an audio signal into 5772 the output and compute the time between generating the signal and recording it back. 5773 You can vary the Audio Level slider to ensure the pulse will feed back at adequate levels. 5774 Repeat until a sufficient confidence is achieved. When each route test is completed, the 5775 measured and required latencies will be displayed. 5776 \nWhen all test routes have passed, the test as a whole can be passed. 5777 </string> 5778 <string name="audio_loopback_instructions"> 5779 Please connect a "Loopback Plug" and press "Loopback Plug Ready". 5780 </string> 5781 <string name="audio_loopback_plug_ready_btn">Loopback Plug Ready</string> 5782 5783 <string name="audio_loopback_calibrate_button">Calibrate Audio</string> 5784 <string name="audio_loopback_devsupport_button">Audio Devices</string> 5785 5786 <string name="audio_loopback_level_text">Audio Level</string> 5787 <string name="audio_loopback_test_btn">Test</string> 5788 <string name="audio_loopback_results_text">Results...</string> 5789 <string name="audio_loopback_test_all_paths">Please test all supported paths.</string> 5790 <string name="audio_loopback_test_not_required">Test not required for this device.</string> 5791 <string name="audio_loopback_test_non_handheld">This device is not a phone. Test can pass.</string> 5792 <string name="audio_loopback_test_internal_devices">Speaker/Mic</string> 5793 <string name="audio_loopback_speakermicpath_instructions">Place the DUT flat on a table 5794 in a quiet room. Press the \"Start\" button and allow the test to proceed.</string> 5795 5796 <string name="audio_loopback_headsetpath_instructions">Insert the loopback plug 5797 into the headset jack. Press the \"Start\" button and allow the test to proceed.</string> 5798 5799 <string name="audio_loopback_usbpath_instructions">Connect the USB 5800 port to an appropriate USB audio test peripheral with loopback set up. Press the \"Start\" 5801 button and allow the test to proceed.</string> 5802 5803 <string name="audio_loopback_failure">FAILURE - Could not allocate analyzer thread.</string> 5804 <string name="audio_loopback_automobile">Automobile:</string> 5805 <string name="audio_loopback_handheld">Handheld:</string> 5806 <string name="audio_loopback_tv">TV:</string> 5807 <string name="audio_loopback_watch">Watch:</string> 5808 <string name="audio_loopback_mmapexclusive">MMAP Exclusive:</string> 5809 <string name="audio_loopback_mmap">MMAP:</string> 5810 <string name="audio_loopback_mcp">MPC:</string> 5811 <string name="audio_loopback_lowlatency">Low Latency:</string> 5812 <string name="audio_loopback_proaudio">Pro Audio:</string> 5813 <string name="audio_loopback_speakermic">Speaker/Mic</string> 5814 <string name="audio_loopback_headsetjack">Headset Jack</string> 5815 <string name="audio_loopback_usb">USB</string> 5816 5817 <!-- result codes --> 5818 <string name="audio_loopback_resultcode_none">Result: None.</string> 5819 <string name="audio_loopback_resultcode_pass">Result: Pass.</string> 5820 <string name="audio_loopback_resultcode_nointernal">Result: Fail - Speaker/Mic path not tested.</string> 5821 <string name="audio_loopback_notmet">not met.</string> 5822 <string name="audio_loopback_resultcode_failbasic">Result: Fail - Basic latency</string> 5823 <string name="audio_loopback_resultcode_failmpc">Result: Fail - Media Performance Class latency</string> 5824 <string name="audio_loopback_resultcode_failpro">Result: Fail - Pro Audio max latency on one path</string> 5825 <string name="audio_loopback_resultcode_failproanalog">Result: Fail - Pro Audio analog latency</string> 5826 <string name="audio_loopback_resultcode_failprousb">Result: Fail - Pro Audio USB latency</string> 5827 <string name="audio_loopback_resultcode_fail24bit">Result: Fail - 24-bit playback requirement no met.</string> 5828 <string name="audio_loopback_resultcode_failproaudiowired">Result: Fail - Pro Audio latency. At least one wired path must be tested.</string> 5829 <string name="audio_loopback_resultcode_warningtimestamp">Result: Warning - Timestamp latency accuracy not met.</string> 5830 <string name="audio_loopback_resultcode_invalid">Result: Invalid result code.</string> 5831 5832 <!-- Status Strings --> 5833 <string name="audio_loopback_noanalog">The DUT does not support an Analog Headset Jack. This Test phase is automatically PASSED.</string> 5834 <string name="audio_loopback_unknownanalog">Support for an Analog Headset Jack could not be determined. If supported, insert the loopback plug 5835 into the headset jack. Press the Start button and allow the test to proceed.</string> 5836 <string name="audio_loopback_nousb">The DUT does not support a USB Audio Port. This Test phase is automatically PASSED.</string> 5837 <string name="audio_loopback_unknownusb">Support for USB Audio could not be determined. If USB Audio is supported, Connect the USB 5838 port to an appropriate USB audio test peripheral with loopback set up. Press the Start 5839 button and allow the test to proceed.</string> 5840 5841 <!-- Multichannel Mixdown Test --> 5842 <string name="audio_multichannel_mixdown_test">Multichannel Mixdown Test</string> 5843 <string name="audio_multichannel_mixdown_info"> 5844 This test verifies that for High Channel Count Positional Playback (QUAD, 5.1, 7.1, 7.1.4), 5845 all playback channels are represented in a stereo mix. It does not verify placement 5846 in the output field. 5847 \n\nThis test requires a 2-channel loopback device such as a 2-channel USB audio interface 5848 correctly configured for audio loopback (see the Audio Loopback Latency test for more 5849 information). 5850 \n\nSince this is a new test, at this time the test process need only be executed for 5851 each required route and the test will be allowed to pass even if incorrect 5852 multi-channel playback is noted. 5853 </string> 5854 <string name="audio_mixdown_clearresults">Clear Results</string> 5855 <string name="audio_mixdown_calibrate">Calibrate Audio</string> 5856 <string name="audio_mixdown_devices">Audio Devices</string> 5857 5858 <string name="audio_mixdown_stereo">Stereo</string> 5859 <string name="audio_mixdown_quad">Quad</string> 5860 <string name="audio_mixdown_sevendotone">7.1</string> 5861 <string name="audio_mixdown_fivedotone">5.1</string> 5862 <string name="audio_mixdown_sevendotonedotfour">7.1.4</string> 5863 5864 <!-- Mixdown Route Names --> 5865 <string name="audio_mixdown_micspeaker">Mic/Speaker</string> 5866 <string name="audio_mixdown_analogheadset">Analog Headset Jack + Loopback</string> 5867 <string name="audio_mixdown_usbdevice">USB Interface + Loopback</string> 5868 <string name="audio_mixdown_usbheadset">USB Headset Adapter + Looback</string> 5869 5870 <!-- Mixdown status strings --> 5871 <string name="audio_mixdown_invalidinput">Invalid Input.</string> 5872 <string name="audio_mixdown_invalidoutput">Invalid Output.</string> 5873 <string name="audio_mixdown_testcanceled">Test Canceled.</string> 5874 <string name="audio_mixdown_cantstart">Couldn\'t Start Duplex Audio.</string> 5875 5876 <string name="audio_mixdown_required">Required</string> 5877 <string name="audio_mixdown_completed">Completed</string> 5878 <string name="audio_mixdown_not_completed">Not Completed</string> 5879 5880 <string name="audio_mixdown_req">required</string> 5881 <string name="audio_mixdown_done">done</string> 5882 5883 <!-- Channel Position Names --> 5884 <string name="audio_channel_mask_left">Left</string> 5885 <string name="audio_channel_mask_right">Right</string> 5886 <string name="audio_channel_mask_center">Center</string> 5887 <string name="audio_channel_mask_sideleft">Side Left</string> 5888 <string name="audio_channel_mask_sideright">Side Right</string> 5889 <string name="audio_channel_mask_backleft">Back Left</string> 5890 <string name="audio_channel_mask_backright">Back Right</string> 5891 <string name="audio_channel_mask_lowfreq">Low Freq</string> 5892 <string name="audio_channel_mask_topfrontleft">Top Front Left</string> 5893 <string name="audio_channel_mask_topfrontright">Top Front Right</string> 5894 <string name="audio_channel_mask_topbackleft">Top Back Left</string> 5895 <string name="audio_channel_mask_topbackright">Top Back Right</string> 5896 5897 <!-- Audio Cold-Start Latency Test --> 5898 <string name="audio_coldstart_out_latency_test">Audio Cold Start Output Latency Test</string> 5899 <string name="audio_coldstart_in_latency_test">Audio Cold Start Input Latency Test</string> 5900 5901 <string name="audio_coldstart_output_info"> 5902 This test measures the time required to play audio from a suspended \"cold\" audio system. 5903 This time is defined as the \"cold start latency\". To pass this test, a maximum 5904 cold start latency time of 500ms or less is REQUIRED, while a time of 100ms or less 5905 is STRONGLY RECOMMENDED. (See <a href="https://source.android.com/compatibility/android-cdd#5_6_audio_latency">Android CDD § 5.6. Audio Latency</a>) 5906 \n\nTo run this test, it is required to have Tap & click sounds disabled in the device 5907 \"Sound & Vibration\" settings panel. Note that in some versions of Android, this setting 5908 may be called \"Touch sounds\". 5909 \n\nThe \"Java API\" and \"Native API\" allow for capturing performance data from the 5910 two streaming APIs. The cold start latency measurement need only pass for one API. 5911 The Native API generally gives the best performance. 5912 \n\nAlthough not part of the pass criteria, the test will also report \"open\" & 5913 \"start\" times. Open time is the time taken to allocate and prepare the player for the 5914 specified stream attributes. Start time is the time taken to start playing audio on an 5915 open stream. 5916 </string> 5917 <string name="audio_coldstart_input_info"> 5918 This test measures the time required to record audio from a suspended \"cold\" audio system. 5919 This time is defined as the \"cold start latency\". To pass this test, a maximum 5920 cold start latency time of 500ms or less is REQUIRED, while a time of 100ms or less 5921 is STRONGLY RECOMMENDED. (See <a href="https://source.android.com/compatibility/android-cdd#5_6_audio_latency">Android CDD § 5.6. Audio Latency</a>) 5922 \n\nThe \"Java API\" and \"Native API\" allow for capturing performance data from the 5923 two streaming APIs. The cold start latency measurement need only pass for one API. 5924 The Native API generally gives the best performance. 5925 \n\nAlthough not part of the pass criteria, the test will also report \"open\" & 5926 \"start\" times. Open time is the time taken to allocate and prepare the recorder for the 5927 specified stream attributes. Start time is the time taken to start recording audio on an 5928 open stream. 5929 </string> 5930 <string name="audio_coldstart_outputlbl">Output Cold Start Latency</string> 5931 <string name="audio_coldstart_inputlbl">Input Cold Start Latency</string> 5932 <string name="audio_coldstart_touchsounds_message"> 5933 Tap & click sounds are ENABLED. Please DISABLE Tap & click in the \"Sound & Vibration\" settings panel. 5934 \nNote that in some versions of Android, this setting may be called \"Touch sounds\". 5935 </string> 5936 <string name="audio_coldstart_notouchsounds_message">Tap & click sounds are DISABLED.</string> 5937 5938 <!-- Audio Frequency Line Test --> 5939 <string name="audio_frequency_line_test">Audio Frequency Line Test</string> 5940 <string name="audio_frequency_line_info"> 5941 The system will measure the frequency response of the left and right line outputs, 5942 by feeding them back thru the microphone conection with the loopback jack. 5943 This test requires the Loopback Plug. Please connect a Loopback Plug on the headset 5944 connector, and proceed with the instructions on the screen. 5945 </string> 5946 <string name="audio_frequency_line_instructions"> 5947 Please connect a "Loopback Plug" and press "Loopback Plug Ready". 5948 </string> 5949 <string name="audio_frequency_line_plug_ready_btn">Loopback Plug Ready</string> 5950 5951 <string name="audio_frequency_line_test_btn">Test</string> 5952 <string name="audio_frequency_line_results_text">Results...</string> 5953 5954 <!-- Audio Frequency Speaker Test --> 5955 <string name="audio_frequency_speaker_test">Audio Frequency Speaker Test</string> 5956 <string name="audio_frequency_speaker_info"> 5957 This test requires an external USB reference microphone. Please connect the USB microphone and proceed with the instructions on the screen. 5958 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. 5959 </string> 5960 <string name="audio_frequency_speaker_instructions"> 5961 Please connect an USB reference microphone and press "USB Reference microphone ready" 5962 </string> 5963 <string name="audio_frequency_speaker_usb_status">Waiting for USB microphone...</string> 5964 <string name="audio_frequency_speaker_mic_ready_btn">USB Reference microphone ready</string> 5965 <string name="audio_frequency_speaker_mic_ready_text">USB Audio device detected\n\nPlease set up Device Under test 5966 in quiet room, and Microphone 20 cms perpendicular to center of screen, then press TEST</string> 5967 <string name="audio_frequency_speaker_mic_not_ready_text">"No USB Audio device detected. Please reconnect."</string> 5968 <string name="audio_frequency_speaker_test_btn">Test</string> 5969 <string name="audio_frequency_speaker_results_text">Results...</string> 5970 5971 <!-- Audio Frequency Microphone Test --> 5972 <string name="audio_frequency_mic_test">Audio Frequency Microphone Test</string> 5973 <string name="frequency_mic_info"> 5974 This test requires an external USB reference microphone and external speakers. 5975 The test signals should be played from a secondary device connected to either analog speakers connected 5976 to the analog headset jack, or USB speakers connected to the USB port of the secondary device. 5977 Follow the instructions on the screen to measure the frequency response for the built in microphone. 5978 </string> 5979 5980 <string name="frequency_mic_play">Play</string> 5981 <string name="frequency_mic_stop">Stop</string> 5982 <string name="frequency_mic_noise_instructions">TEST NOISE: Position speakers 40 cms from device under test. 5983 Press [PLAY] to play broadband white noise. Press [TEST] 5984 </string> 5985 <string name="frequency_mic_test_noise_btn">Test</string> 5986 <string name="frequency_mic_test_noise_result">Results...</string> 5987 5988 <string name="frequency_mic_test_usb_background_instructions">TEST USB BACKGROUND: Connect USB microphone and position it right next to microphone under test. 5989 No source of noise should be active during this test. Press [TEST]</string> 5990 <string name="frequency_mic_test_usb_background_btn">Test</string> 5991 <string name="frequency_mic_test_usb_background_result">Results...</string> 5992 5993 <string name="frequency_mic_test_usb_noise_instructions">TEST USB NOISE: Connect USB microphone and position it right next to microphone under test. 5994 Position speakers 40 cms from device under test. Press [PLAY] to play broadband white noise. Press [TEST]</string> 5995 <string name="frequency_mic_test_usb_noise_btn">Test</string> 5996 <string name="frequency_mic_test_usb_noise_result">Results...</string> 5997 5998 <string name="frequency_mic_test_global_result">Global Results...</string> 5999 6000 <!-- Audio Frequency Unprocessed Test --> 6001 <string name="audio_frequency_unprocessed_test">Audio Frequency Unprocessed Test</string> 6002 <string name="audio_frequency_unprocessed_info"> 6003 This test requires an external USB reference microphone, external speakers and a Sound Pressure Level meter. 6004 You can play the test signals from the device under test or from a secondary device. 6005 Follow the instructions on the screen to measure the frequency response for the built in microphone 6006 using UNPROCESSED audio source. 6007 If the Audio Frequency Unprocessed feature is defined in this system, success in all tests is mandatory to pass. 6008 If the feature is not defined, measurements are still needed, but success in all of them is not mandatory to pass. 6009 </string> 6010 <string name="audio_frequency_unprocessed_defined">Audio Frequency Unprocessed feature is defined. Success in all tests is mandatory to pass</string> 6011 <string name="audio_frequency_unprocessed_not_defined">Audio Frequency Unprocessed feature is NOT defined. Success in all test is NOT mandatory to pass</string> 6012 6013 <string name="unprocessed_play">Play</string> 6014 <string name="unprocessed_stop">Stop</string> 6015 6016 <string name="unprocessed_test_tone_instructions">TEST TONE: Press [PLAY] to play tone at 1 Khz. Measure sound SPL to be 94 dB 6017 right next to microphone under test. Press [TEST]</string> 6018 <string name="unprocessed_test_tone_btn">Test</string> 6019 <string name="unprocessed_test_tone_result">Results...</string> 6020 6021 <string name="unprocessed_test_noise_instructions">TEST NOISE: Position speakers 40 cms from device under test. 6022 Press [PLAY] to play broadband white noise. Press [TEST]</string> 6023 <string name="unprocessed_test_noise_btn">Test</string> 6024 <string name="unprocessed_test_noise_result">Results...</string> 6025 6026 <string name="unprocessed_test_usb_background_instructions">TEST USB BACKGROUND: Connect USB microphone and position it right next to microphone under test. 6027 No source of noise should be active during this test. Press [TEST]</string> 6028 <string name="unprocessed_test_usb_background_btn">Test</string> 6029 <string name="unprocessed_test_usb_background_result">Results...</string> 6030 6031 <string name="unprocessed_test_usb_noise_instructions">TEST USB NOISE: Connect USB microphone and position it right next to microphone under test. 6032 Position speakers 40 cms from device under test. Press [PLAY] to play broadband white noise. Press [TEST]</string> 6033 <string name="unprocessed_test_usb_noise_btn">Test</string> 6034 <string name="unprocessed_test_usb_noise_result">Results...</string> 6035 6036 <string name="unprocessed_test_global_result">Global Results...</string> 6037 6038 <!-- Audio Frequency Voice_Recognition Test --> 6039 <string name="audio_frequency_voice_recognition_test">Audio Frequency Voice Recognition Test</string> 6040 <string name="audio_frequency_voice_recognition_info"> 6041 This test requires an external USB reference microphone, external speakers and a Sound Pressure Level meter. 6042 You can play the test signals from the device under test or from a secondary device. 6043 Follow the instructions on the screen to measure the frequency response for the built in microphone 6044 using VOICE_RECOGNITION audio source. 6045 </string> 6046 <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> 6047 <string name="vr_test_noise_instructions">TEST NOISE: Position speakers 40 cms from device under test. 6048 Press [PLAY] to play broadband white noise. Press [TEST]</string> 6049 <string name="vr_test_usb_background_instructions">TEST USB BACKGROUND: Connect USB microphone and position it right next to microphone under test. 6050 No source of noise should be active during this test. Press [TEST]</string> 6051 <string name="vr_test_usb_noise_instructions">TEST USB NOISE: Connect USB microphone and position it right next to microphone under test. 6052 Position speakers 40 cms from device under test. Press [PLAY] to play broadband white noise. Press [TEST]</string> 6053 6054 <!-- Analog Headset Test --> 6055 <string name="audio_headset_audio_test">Analog Headset Audio Test</string> 6056 <string name="analog_headset_query">Does this Android device have an analog headset jack?</string> 6057 <string name="analog_headset_play">Play</string> 6058 <string name="analog_headset_stop">Stop</string> 6059 <string name="analog_headset_playback_prompt">Play a test tone and verify correct playback</string> 6060 <string name="analog_headset_playback_query">Was the audio correctly played through the headset?</string> 6061 <string name="analog_headset_keycodes_label">Headset key codes</string> 6062 <string name="analog_headset_headsethook">HEADSETHOOK</string> 6063 <string name="analog_headset_volup">VOLUME_UP</string> 6064 <string name="analog_headset_voldown">VOLUME_DOWN</string> 6065 <string name="analog_headset_test">Analog Headset Test</string> 6066 <string name="analog_headset_pass_noheadset">"PASS - No headset port available"</string> 6067 <string name="analog_headset_headset_unknown">FAIL - Headset State Unknown</string> 6068 <string name="analog_headset_pass">PASS</string> 6069 <string name="analog_headset_port_detected">"Headset port detected"</string> 6070 <string name="analog_headset_press_buttons">Press each button on the headset verify recognition</string> 6071 <string name="analog_headset_no_buttons">No buttons detected</string> 6072 <string name="analog_headset_headset_connected">Analog headset connected</string> 6073 <string name="analog_headset_no_headset">No Analog Headset - Connect headset to 3.5mm jack</string> 6074 <string name="analog_headset_action_received">ACTION_HEADSET_PLUG received - </string> 6075 <string name="analog_headset_unplugged">Unplugged</string> 6076 <string name="analog_headset_plugged">Plugged</string> 6077 <string name="analog_headset_mic"> [mic]</string> 6078 <string name="analog_headset_reportnojack">No analog Jack. PASS</string> 6079 <string name="analog_headset_no_jack">No analog jack detected. Please connect a headset, or PASS</string> 6080 <string name="analog_headset_connect_headset">Please connect an analog headset</string> 6081 <string name="analog_headset_play_audio">Please test audio through the analog headset</string> 6082 <string name="analog_headset_test_buttons">Please test transport buttons</string> 6083 6084 <string name="analog_headset_test_info">This test tests the following functionality with respect to wired analog headsets.\n 6085 1. Correct audio playback.\n 6086 2. Plug intents.\n 6087 3. Headset keycodes.\n 6088 \nTo execute test:\n 6089 1. Plug in an Android-compatible, analog headset. Verify connection/recognition.\n 6090 2. Play test tone and verify correct behavior.\n 6091 3. Press headset buttons until all are recognized on the test screen.\n 6092 \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 6093 \n(see <a href="https://source.android.com/devices/accessories/headset/plug-headset-spec">3.5 mm Headset: Accessory Specification</a> and 6094 <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>) 6095 </string> 6096 <!-- Audio AEC Test --> 6097 <string name="audio_aec_test">Audio Acoustic Echo Cancellation (AEC) Test</string> 6098 <string name="audio_aec_info"> 6099 The recording source VOICE_COMMUNICATION will be tested with/without the Acoustic Echo Canceller effect engaged. 6100 The Acoustic Coupling Factor (ACF) will be computed for each case. A successful test expects ACF less than 0.4 for AEC ON, 6101 and ACF greater than 0.6 for AEC OFF. 6102 This test requires a quiet environment, and no headphones or similar connected. 6103 This test must pass on any device which implements AEC. 6104 </string> 6105 <string name="audio_aec_instructions">Press [TEST] to play a voice recording twice with different parameters.</string> 6106 <string name="audio_aec_mandatory_test">Is AEC mandatory in this device?</string> 6107 <string name="audio_aec_no_aec_support">No AEC Support.</string> 6108 <string name="audio_aec_no_aec_pass">AEC is not supported on this device. Test may pass.</string> 6109 6110 <!-- Audio Connection Test --> 6111 <string name="audio_disconnect_test">Audio Stream Disconnect Test</string> 6112 <string name="audio_disconnect_info"> 6113 Tests that audio streams generate the correct stream disconnection events. Note that this 6114 test is only required for devices that support wired headset. 6115 \n\nTest Requirements 6116 \nA wired (analog or USB) headset peripheral, or analog loopback adapter. 6117 \n\nTest Process: 6118 \n1. Press the \"Start\" button. 6119 \n2. For each tested audio route: 6120 \n a. Connect the headset peripheral when instructed. 6121 \n b. Disconnect the headset peripheral when instructed. 6122 \n\nTest Criteria: 6123 \nThe test passes if all routes demonstrate the correct stream disconnection behavior. 6124 </string> 6125 <string name="audio_disconnect_wired_prompt">Does this device support an analog or USB audio peripheral?</string> 6126 <string name="audio_disconnect_port_detected">"Wired device support detected"</string> 6127 6128 <!--Audio Frequency Global strings --> 6129 <string name="af_button_play">Play</string> 6130 <string name="af_button_stop">Stop</string> 6131 6132 <string name="af_button_test">Test</string> 6133 <string name="af_test_results">Results...</string> 6134 <string name="af_global_test_results">Global Results...</string> 6135 <string name="af_no">No</string> 6136 <string name="af_yes">Yes</string> 6137 6138 <!-- AudioTap2Tone test --> 6139 <string name="audio_tap2tone">Audio Tap To Tone Test</string> 6140 <string name="audio_tap2tone_info">This tests the latency from a screen interaction to a 6141 resulting tone. This time is a combination of touch screen latency and audio latency.\nThis 6142 test is best conducted in a quiet room with the device laying on a table. 6143 \n\nTo execute test: 6144 \n1. Disconnect any wired or Bluetooth audio peripherals from the DUT. The Tap To Tone Test 6145 measures the time between a tap on the screen to a tone generated on the internal speaker. 6146 The internal microphone is used to detect both. 6147 \n2. Select the Audio API to test (\"Native\" has the lowest latency) and press the \"Start\" button. 6148 The test needs to pass for ONLY ONE API. 6149 \n3. Use your FINGERNAIL to tap ONCE on the field below to trigger the test tone. DO NOT leave 6150 the finger resting on the test field. A strong \"tick\" sound from the fingernail striking 6151 the display is necessary to register the start of the test process. 6152 \n4. After tapping ONCE, wait until the results are displayed in the field above the 6153 waveform display before tapping for the next test run. 6154 \nFive successful tests runs are required to determine if the test as a whole succeeds. 6155 \n5. Press the \"Stop\" button to conclude the test. The results will be displayed along with the passing/failing measurement and requirement. 6156 \n\n(see <a href="https://source.android.com/compatibility/12/android-12-cdd#56_audio_latency">Android CDD § 5.6. Audio Latency</a>) 6157 </string> 6158 <string name="audio_tap2tone_too_few">Not enough edges. Use fingernail.</string> 6159 <string name="audio_tap2tone_too_many">Too many edges. Use fingernail. Ensure there is 6160 no background noise.</string> 6161 <string name="audio_tap2tone_buffer_frames">Buffer Frames: </string> 6162 <string name="audio_tap2tone_bad_streams">Can\'t open streams.</string> 6163 <string name="audio_tap2tone_noio">No mic and/or speaker. PASS</string> 6164 6165 <!-- Strings for 6DoF test --> 6166 <string name="six_dof_test">6DoF Test</string> 6167 <string name="action_settings">Settings</string> 6168 <string name="start">Start</string> 6169 <string name="motion_tracking_permission">"Motion Tracking permission needed!"</string> 6170 <string name="translations">Translations:</string> 6171 <string name="rotations">Rotations:</string> 6172 <string name="action_place_marker">Place Marker</string> 6173 <string name="markers">Markers:\n</string> 6174 <string name="title_activity_cts">CTSActivity</string> 6175 <string name="stop">Stop!</string> 6176 <string name="stop_message">Mark where you are standing with something like a piece of card and 6177 then press ready to record this waypoint 6178 </string> 6179 <string name="ready">Ready</string> 6180 <string name="initial">First Waypoint</string> 6181 <string name="phase1_initial_message">When you are ready to place your first waypoint, place a 6182 marker at the devices current location. Use something that will allow you to put the device 6183 in the exact same position and orientation on the second lap. Then, while the device is on 6184 the marker, click the turquoise action button to record the first waypoint.\n\nStart walking 6185 in a direction. The button will appear again when you have walked far enough. Place a marker 6186 at the device\'s location and press the button to record a waypoint. You cannot place 6187 waypoints in a straight line, so for your 3rd waypoint turn 90 degrees and walk in a 6188 direction that will make a triangle out of your 3 waypoints. 6189 </string> 6190 <string name="phase2_initial_message">You now need to visit each waypoint, clicking the 6191 turquoise action button at each one. You need to reach each waypoint in 20 seconds. While 6192 you are on your way to the waypoints, the camera preview will rotate. You will need to 6193 rotate the device to match the rotation of the camera preview. A box will be shown to help 6194 you. It shows the device\'s current rotation and will change color based on whether you are 6195 close enough to the required rotation. Red if you are failing, green if you are passing. 6196 When you have reached the next waypoint, the device can be returned to its original 6197 rotation. 6198 </string> 6199 <string name="last">Go back to the first waypoint</string> 6200 <string name="last_message">Now go back to the first waypoint and press ready to finish the 6201 first lap. 6202 </string> 6203 <string name="got_it">Got it!</string> 6204 <string name="lap2_instructions">Now, go to each waypoint (including your initial 6205 one) and click the turquoise action button. Then move on to the next waypoint and do the 6206 same.\nThe last waypoint should be the first waypoint again. 6207 </string> 6208 <string name="test1_pass2">Pass 2</string> 6209 <string name="results">Results</string> 6210 <string name="overall_instructions">These tests are designed to verify the correctness and 6211 accuracy of a 6DoF enabled device. There will be 3 phases to these tests, each testing a 6212 different part of 6DoF functionality. 6213 </string> 6214 <string name="phase1_description">This first test will test the accuracy of the device. It will 6215 ask you to mark out 4 waypoints and then return to the original waypoint to complete the 6216 lap. After this you will then need to do another lap without any HUD information. At the 6217 end, the pairs of waypoints and the path you travelled will be compared and you will be 6218 given a result. 6219 </string> 6220 <string name="phase2_description">This test will test the robustness of the device. Using the 6221 same 4 waypoints as before, you will need to do a lap, reaching each waypoint in the 6222 allotted time.\nWhile you are on your way to the waypoints, the camera preview will rotate. 6223 You will need to rotate the device to match the rotation of the camera preview. A box will 6224 be shown to help you. It shows the device\'s current rotation and will change color based 6225 on whether you are close enough to the required rotation. Red if you are failing, green if 6226 you are passing. When you have reached the next waypoint, the device can be returned to 6227 its original rotation. 6228 </string> 6229 <string name="phase3_description">Now we will test the AR capability of the device. Again, you 6230 will need to do a lap of the waypoints, but this time between each waypoint the device will 6231 overlay hoops that you must pass the device through as you go along. 6232 </string> 6233 <string name="distance">Distance from last waypoint:</string> 6234 <string name="obj_return_to_initial_waypoint">Return to initial waypoint</string> 6235 <string name="waypointPlaced">Waypoint placed!</string> 6236 <string name="undo">undo</string> 6237 <string name="distance_remaining">Distance Remaining:\n</string> 6238 <string name="waypoint_differences">Waypoints</string> 6239 <string name="path_differences">Paths</string> 6240 <string name="error_distance">Not far away enough from other waypoints!</string> 6241 <string name="error_area">Not enough area covered.</string> 6242 <string name="passed">Passed!</string> 6243 <string name="failed">Failed!</string> 6244 <string name="test_failed">Test Failed!</string> 6245 <string name="error_start_point">Not close enough to initial waypoint!</string> 6246 <string name="waypoint_distance">Waypoint %1$s: %2$s</string> 6247 <string name="total">Total %1$s</string> 6248 <string name="path">Path %1$s: %2$s</string> 6249 <string name="fail">Fail</string> 6250 <string name="pass">Pass</string> 6251 <string name="info">Info</string> 6252 <string name="coming_soon">Coming soon!</string> 6253 <string name="motion_tracking_invalid_state">Motion Tracking has entered an invalid state 6254 </string> 6255 <string name="action_xml">XML</string> 6256 <string name="error_null_fragment">UI fragment was null, couldn\'t do callback to listener 6257 </string> 6258 <string name="error_retained_fragment_null">DataFragment is null</string> 6259 <string name="time_remaining">%1$s seconds remaining to get to next waypoint</string> 6260 <string name="action_skip_to_2nd">Skip to 2nd Test</string> 6261 <string name="failed_pause_resume">Test Failed because Test Activity was paused</string> 6262 <string name="action_overlapping_outlines">Overlapping Outlines</string> 6263 <string name="action_overlapping_filled">Overlapping Filled</string> 6264 <string name="time">Time</string> 6265 <string name="rotation_result">Rotation</string> 6266 <string name="action_separate_outlines">Separate Outlines</string> 6267 <string name="action_separate_filled">Separate Filled</string> 6268 <string name="action_one">One Rectangle</string> 6269 <string name="rotation_mode">Change rotation mode</string> 6270 <string name="phase3_initial_message">Go through the rings as you visit waypoints.</string> 6271 <string name="rings">Rings</string> 6272 <string name="rings_entered">Rings collected %1$s/%2$s</string> 6273 <string name="error_rings_not_entered">You haven\'t collected all the rings in this path! 6274 </string> 6275 <string name="save">Save</string> 6276 6277 <string-array name="initial_waypoint"> 6278 <item>Find a place for your first waypoint</item> 6279 <item>Go to initial waypoint</item> 6280 </string-array> 6281 6282 <string-array name="next_waypoint"> 6283 <item>Find a suitable place for waypoint 0</item> 6284 <item>Go to waypoint 0</item> 6285 </string-array> 6286 6287 <string-array name="phase"> 6288 <item>Phase 1</item> 6289 <item>Phase 2</item> 6290 <item>Phase 3</item> 6291 </string-array> 6292 6293 <string-array name="phase_descriptions"> 6294 <item>@string/phase1_description</item> 6295 <item>@string/phase2_description</item> 6296 <item>@string/phase3_description</item> 6297 </string-array> 6298 6299 <!-- Strings for setting and restoring default dialer for voicemail tests --> 6300 <string name="voicemail_restore_default_dialer_description">Restore the default dialer setting by going to Default apps -> Phone app</string> 6301 <string name="voicemail_restore_default_dialer_button">Restore the default dialer"</string> 6302 <string name="voicemail_default_dialer_already_set">Default dialer already set</string> 6303 <string name="voicemail_default_dialer_already_restored">Default dialer already restored</string> 6304 <string name="voicemail_set_default_dialer_description">Before the test, the CTS verifier should be set to the default dialer</string> 6305 <string name="voicemail_set_default_dialer_button">Set CTS verifier as default dialer"</string> 6306 6307 <!-- Strings for voicemail broadcast test --> 6308 <string name="voicemail_broadcast_test">Voicemail Broadcast Test</string> 6309 <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> 6310 <string name="voicemail_broadcast_no_carrier_support">The carrier does not support voicemail, this test is not applicable.</string> 6311 <string name="voicemail_leave_voicemail">Send a voicemail to the device, CTS verifier should receive a voicemail notification broadcast</string> 6312 <string name="voicemail_broadcast_received">Voicemail broadcast Received</string> 6313 6314 <!-- Strings for VisualVoicemailService test --> 6315 <string name="visual_voicemail_service_test">VisualVoicemailService Test</string> 6316 <string name="visual_voicemail_service_instructions">This test verifies that the VisualVoicemailService can receive SIM inserted and removed events</string> 6317 <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> 6318 <string name="visual_voicemail_service_remove_sim_ok">Ok</string> 6319 <string name="visual_voicemail_service_remove_sim_not_applicable">Not applicable</string> 6320 <string name="visual_voicemail_service_insert_sim">Insert SIM</string> 6321 <string name="visual_voicemail_service_insert_sim_received">Service connection event received</string> 6322 <string name="visual_voicemail_service_remove_sim">Remove SIM</string> 6323 <string name="visual_voicemail_service_remove_sim_received">SIM removal event received</string> 6324 6325 <!-- Strings for CallSettingsCheck test --> 6326 <string name="call_settings_check_test">Hide voicemail in call settings test</string> 6327 <string name="call_settings_check_instructions">This test verifies that the default dialer can 6328 hide voicemail settings in the call settings menu by using 6329 TelephonyManager.METADATA_HIDE_VOICEMAIL_SETTINGS_MENU 6330 </string> 6331 <string name="open_call_settings_explanation">Tap the button, and verify that \"voicemail\" does 6332 not exist in the call settings 6333 </string> 6334 <string name="open_call_settings">Open call settings</string> 6335 <string name="voicemail_hidden">\"Voicemail\" does not exist</string> 6336 <string name="voicemail_not_hidden">\"Voicemail\" exists</string> 6337 6338 <!-- Strings for DialerIncomingCall test --> 6339 <string name="dialer_incoming_call_test">Dialer Receives Incoming Call</string> 6340 <string name="dialer_incoming_call_test_instructions">This test verifies that the default dialer 6341 can receive incoming calls after it has been set. 6342 </string> 6343 <string name="dialer_incoming_call_detected">Detected the incoming call. Activity passed.</string> 6344 <string name="dialer_check_incoming_call_explanation">Call the device and end the call in the 6345 pop up in-call UI.</string> 6346 <string name="dialer_check_incoming_call">Verify Call Received</string> 6347 6348 <!-- Strings for VoicemailSettingsCheck test --> 6349 <string name="ringtone_settings_check_test">Hide settings in voicemail test</string> 6350 <string name="ringtone_settings_check_instructions">This test verifies that voicemail settings 6351 accessible with public API can be hidden when launching 6352 TelephonyManager.ACTION_CONFIGURE_VOICEMAIL with EXTRA_HIDE_PUBLIC_SETTINGS. 6353 </string> 6354 <string name="open_voicemail_settings_explanation">Tap the button, ringtone and virbration 6355 settings does not exist in the voicemail settings. 6356 </string> 6357 <string name="open_voicemail_settings">Open voicemail settings</string> 6358 <string name="ringtone_hidden">Ringtone settings does not exist</string> 6359 <string name="ringtone_not_hidden">Ringtone settings exists</string> 6360 6361 <!-- Strings for DialerShowsHunOnIncomingCallActivity test --> 6362 <string name="dialer_shows_hun_test">Dialer Shows HUN on Incoming Call</string> 6363 <string name="dialer_shows_hun_test_instructions">This test verifies that the default dialer 6364 shows a heads up notification on incoming call, and that only one notification is shown. 6365 </string> 6366 <string name="dialer_shows_hun_explanation">Call the device. 6367 Check the box if the heads up notification was shown containing the text 6368 \"CTS Incoming Call Notification\", and only one incoming call notification was shown. 6369 Also a pop up CtsVerifier in call UI will show. 6370 </string> 6371 <string name="dialer_shows_hun_check_box">HUN shown and meets criteria specified above.</string> 6372 <string name="dialer_incoming_call_hun_teaser">Incoming Call</string> 6373 <string name="dialer_incoming_call_hun_desc">CTS Incoming Call Notification</string> 6374 6375 <!-- Strings for DialerImplementsTelecomIntentsActivity test --> 6376 <string name="dialer_telecom_intents_test">System Implements Telecom Intents</string> 6377 <string name="dialer_telecom_intents_test_instructions">This test verifies that the system handles 6378 the specified Telecom Intents. 6379 </string> 6380 <string name="dialer_check_intents_implemented_explanation">Press the buttons below to launch settings activities. 6381 Check the associated box if the activity loads and was launched succesfully.</string> 6382 <string name="dialer_telecom_intents_call_settings">Launch call settings</string> 6383 <string name="dialer_telecom_intents_short_sms">Launch short sms answer settings</string> 6384 <string name="dialer_telecom_intents_calling_accounts">Launch calling accounts settings</string> 6385 <string name="dialer_telecom_intents_accessibility_settings">Launch accessibility settings</string> 6386 <string name="dialer_check_intents_check_box">Setting Launched</string> 6387 6388 <!-- USB Audio Peripheral Tests --> 6389 <string name="usbaudio_results_text">Results...</string> 6390 6391 <!-- USB Audio Peripheral Attributes Test --> 6392 <string name="usbaudio_attribs_test"> USB Audio Peripheral Attributes Test</string> 6393 6394 <string name="usbaudio_attribs_info">This test tests that the USB Audio HAL returns the 6395 expected set of attributes for a well-known USB audio peripheral. See the 6396 <a href="https://source.android.com/compatibility/cts/usb-audio#recommended-peripherals"> 6397 Mandated Peripherals 6398 </a> 6399 section of the <a href="https://source.android.com/compatibility/cts/usb-audio"> 6400 USB Audio CTS Verifier Tests 6401 </a>. 6402 for a list of supported USB audio peripherals. The attributes of the supported 6403 peripherals are stored in the app in a set of \"Peripheral Profiles\".\n\n 6404 To execute the test:\n 6405 1. Specify whether or not the DUT supports USB host mode (CDD 5.10 C-1-3). If not the test 6406 simply passes. 6407 2. Plug in a supported USB Audio Peripheral.\nThe peripheral\'s attributes will be 6408 displayed along with the name of the associated profile. If the peripheral matches the 6409 profile, the test passes. If not, the mismatches are displayed. 6410 </string> 6411 6412 <!-- USB Audio Peripheral Buttons Test --> 6413 <string name="usbaudio_buttons_test"> USB Audio Peripheral Buttons Test</string> 6414 <string name="usbaudio_buttons_info"> 6415 This test requires that you have connected a USB Audio headset that supports the 6416 Android USB audio headset buttons specification. Press each 6417 \"transport\" button and verify that it is recognized by the test. When each of the 6418 buttons has been recognized the \"pass\" button will be enabled. 6419 </string> 6420 6421 <!-- Pro Audio Test --> 6422 <string name="proaudio_test">Pro Audio Test</string> 6423 <string name="proaudio_info">This tests that any device claiming \"Pro Audio\" meets the 6424 requirements specified in the 6425 <a href="https://source.android.com/compatibility/12/android-12-cdd#510_professional_audio"> 6426 CDD section 5.10. Professional Audio</a> 6427 \n\nTo execute the test: 6428 \n1. Note that all required flags report \"true\" 6429 \n2. If the DUT supports HDMI: 6430 \n a. Click the \"Has HDMI Support\" checkbox 6431 \n b. Connect an HDMI device to the DUT 6432 \n c. Verify that the reported HDMI attributes meet the specification. 6433 \n\nNote that the latency measurement for Pro Audio has been moved to the 6434 Audio Loopback Latency Test 6435 </string> 6436 <string name="proaudio_hdmi_infotitle">HDMI Support</string> 6437 <string name="proaudio_hdmi_message">Please connect an HDMI peripheral to validate 6438 HDMI output attributes. 6439 </string> 6440 6441 <!-- Telecom tests --> 6442 <string name="telecom_enable_phone_account_test"> Telecom Enable Phone Account Test</string> 6443 <string name="telecom_enable_phone_account_info"> 6444 This test verifies that a third party ConnectionService can be enabled by the user. 6445 </string> 6446 <string name="telecom_enable_phone_account_step_1"> 6447 Click the button below to register a test PhoneAccount and ConnectionService. 6448 </string> 6449 <string name="telecom_enable_phone_account_register_button">Register Phone Account</string> 6450 <string name="telecom_enable_phone_account_step_2"> 6451 In the Calling accounts settings, choose "All calling accounts" and enable the "CTS Verifier Test" account. 6452 On AOSP this is accessible from: Phone app > Settings > Calls > Calling Accounts. 6453 Once you have completed this step, return here and click the Confirm button. 6454 </string> 6455 <string name="telecom_enable_phone_account_confirm_button">Confirm</string> 6456 6457 <string name="telecom_outgoing_call_test">Telecom Outgoing Call Test</string> 6458 <string name="telecom_outgoing_call_test_info">This test verifies that the default 6459 dialer on the system is able to make a call using a third-party ConnectionService.</string> 6460 <string name="telecom_outgoing_call_step_1"> 6461 Click the button below to register a test PhoneAccount and ConnectionService. You will be 6462 taken to the phone account selection screen. Please enable the "CTS Verifier Test" 6463 account and select it as the default account for outgoing calls. Once you have completed 6464 this step, return here and click the "Confirm Phone Account" button. 6465 </string> 6466 <string name="telecom_outgoing_call_register_enable_phone_account_button"> 6467 Register and Enable Phone Account 6468 </string> 6469 <string name="telecom_outgoing_call_confirm_register_button">Confirm Phone Account</string> 6470 <string name="telecom_outgoing_call_step_2"> 6471 Click the button below to dial an outgoing call. This will populate the default dialer 6472 app with a dummy phone number. Initiate the phone call from the dialer app, then return 6473 to this screen while the call is still in progress. 6474 </string> 6475 <string name="telecom_outgoing_call_dial_button">Dial</string> 6476 <string name="telecom_outgoing_call_step_3"> 6477 Click the button below to confirm that the ongoing outgoing call was correctly made. 6478 </string> 6479 <string name="telecom_outgoing_call_confirm_button">Confirm</string> 6480 6481 <string name="telecom_audio_call_test">Telecom Call Audio Test</string> 6482 <string name="telecom_audio_call_test_info">This test verifies that there are no audio 6483 issues when starting a sim call while in an active self-managed call. Note, this test 6484 requires the device under test to have an active sim with service. 6485 </string> 6486 <string name="telecom_status_image_description"> The image represents the status of the step 6487 in the test. The start state is indeterminate which is a question mark image. If the test step 6488 passes a green check will be show. Otherwise, a red x will show which means the test failed at 6489 the step.</string> 6490 <string name="tel_as1_instructions">set default outgoing phone account to a SIM based account 6491 </string> 6492 <string name="tel_as2_instructions"> 6493 Click the button below to initiate a self-managed call. Once clicked, you should hear an 6494 audio clip looping in whichever audio route is active (e.g. earpiece). 6495 </string> 6496 <string name="tel_as3_instructions">Click the button below to confirm the audio from the 6497 self-managed call is audible. Hearing the audio means the self-managed call was created 6498 successfully. 6499 </string> 6500 <string name="tel_as4_instructions">Now, enter a valid phone number and start an active sim 6501 based call. Ensure call audio is working both ways and end the sim call. 6502 </string> 6503 <string name="tel_as5_instructions">verify there were no sim call audio issues 6504 </string> 6505 <string name="tel_as6_instructions"> The self-managed call should resume playing audio. 6506 Hold your ear to the phone and verify the call audio is playing. 6507 </string> 6508 <string name="tel_verify_self_managed_audio_text">verify self-managed audio</string> 6509 <string name="tel_verify_sim_audio_text">verify sim call audio</string> 6510 <string name="tel_dial_sim_call_text">dial sim call</string> 6511 <string name="tel_set_default_outgoing_account_text">set default (optional)</string> 6512 <string name="tel_verify_start_state">verify start state</string> 6513 <string name="tel_start_self_managed_call_text">start self-managed call</string> 6514 <string name="tel_enter_phone_number_text">Enter number here</string> 6515 <string name="tel_enter_phone_number_autofill_hints_text">phoneNumber</string> 6516 <string name="tel_go_back_to_test_text">Go back to test</string> 6517 6518 <string name="telecom_incoming_call_test">Telecom Incoming Call Test</string> 6519 <string name="telecom_incoming_call_test_info">This test verifies that the default 6520 dialer on the system is able to receive a call from a third-party connection service. 6521 </string> 6522 <string name="telecom_incoming_call_step_1"> 6523 Click the button below to register a test PhoneAccount and ConnectionService. You will be 6524 taken to the phone account selection screen. Please enable the "CTS Verifier Test" 6525 account. Once you have completed this step, return here and click the 6526 "Confirm Phone Account" button. 6527 </string> 6528 <string name="telecom_incoming_call_register_enable_phone_account_button"> 6529 Register and Enable Phone Account 6530 </string> 6531 <string name="telecom_incoming_call_confirm_register_button">Confirm Phone Account</string> 6532 <string name="telecom_incoming_call_step_2"> 6533 Click the button below to initiate an incoming call. The phone should start ringing. 6534 Answer the call, confirm that you can hear an audio clip with Eisenhower\'s voice, then 6535 return to this screen while the call is still ongoing. 6536 </string> 6537 <string name="telecom_incoming_call_dial_button">Dial</string> 6538 <string name="telecom_incoming_call_step_3"> 6539 Click the button below to confirm that the ongoing incoming call was properly answered and 6540 that audio is audible. 6541 </string> 6542 <string name="telecom_incoming_call_confirm_button">Confirm</string> 6543 <string name="telecom_incoming_self_mgd_test"> Incoming Self-Managed Connection Test</string> 6544 <string name="telecom_incoming_self_mgd_info"> 6545 This test verifies that an incoming call from a Self-Managed Connection Service will trigger 6546 a Telecom-managed incoming call UI when it is not possible to hold an ongoing call on the 6547 device. 6548 </string> 6549 <string name="telecom_incoming_self_mgd_step_1"> 6550 Click the button below to register a test self-managed ConnectionService. 6551 </string> 6552 <string name="telecom_incoming_self_mgd_register_button">Register Self-Managed ConnectionService</string> 6553 <string name="telecom_incoming_self_mgd_step_2"> 6554 Start two phone calls on the device under test; this generates a scenario where calls cannot 6555 be held when the incoming self-managed call is received. Click "verify calls" to confirm 6556 that the calls were started. 6557 </string> 6558 <string name="telecom_incoming_self_mgd_verify_call_button">Verify Calls</string> 6559 <string name="telecom_incoming_self_mgd_step_3"> 6560 Click the button below to start a test incoming self-managed call. Answer the call in the 6561 UI when prompted. 6562 </string> 6563 <string name="telecom_incoming_self_mgd_place_call_button">Start Self-Managed Call</string> 6564 <string name="telecom_default_dialer_test_title">Default Dialer Test</string> 6565 <string name="telecom_default_dialer_test_info"> 6566 This test verifies that a third party dialer can show an incoming call screen when the 6567 device is locked. 6568 </string> 6569 <string name="telecom_default_dialer_step_1"> 6570 Click the button below to set CtsVerifier as the default dialer. 6571 </string> 6572 <string name="telecom_default_dialer_set_third_party_dialer_button"> 6573 Set third party dialer 6574 </string> 6575 <string name="telecom_default_dialer_step_2"> 6576 Click the button to make sure that this phone is secured with a lock screen. 6577 </string> 6578 <string name="telecom_confirm_lock_screen">Confirm lock screen</string> 6579 <string name="telecom_default_dialer_step_3"> 6580 Click the button below to lock the phone and then call this device. Answer the incoming call 6581 in the UI when prompted without unlock the phone. 6582 </string> 6583 <string name="telecom_default_dialer_lock_button">Lock phone and dail</string> 6584 <string name="telecom_default_dialer_step_4"> 6585 Click the button below to confirm that the ongoing incoming call was answered when the 6586 device is locked. 6587 </string> 6588 <string name="telecom_default_dialer_end_button">End call and confirm</string> 6589 <string name="telecom_default_dialer_confirm_button">Confirm</string> 6590 <string name="telecom_in_call_ui_label">CtsVerifierInCallUi</string> 6591 <!-- Strings for SetNewPasswordComplexityTest --> 6592 <string name="set_complexity_test_title">Set New Password Complexity Test</string> 6593 <string name="set_complexity_test_message"> 6594 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 6595 \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. 6596 </string> 6597 <string name="set_complexity_high_txt">High</string> 6598 <string name="set_complexity_medium_txt">Medium</string> 6599 <string name="set_complexity_low_txt">Low</string> 6600 <string name="set_complexity_none_txt">None</string> 6601 <string name="set_complexity_high_desc"> 6602 PIN without repeating (4444) or ordered (1234, 4321, 2468) sequences, length at least 8; Or 6603 \nAlphabetic, length at least 6; Or 6604 \nAlphanumeric, length at least 6</string> 6605 <string name="set_complexity_medium_desc"> 6606 PIN without repeating (4444) or ordered (1234, 4321, 2468) sequences, length at least 4; Or 6607 \nAlphabetic, length at least 4; Or 6608 \nAlphanumeric, length at least 4</string> 6609 <string name="set_complexity_low_desc">Any pattern, PIN or password</string> 6610 <string name="set_complexity_none_desc">No restrictions</string> 6611 <!-- Strings for UnlockedDeviceRequiredKeysTest --> 6612 <string name="unlock_req_config_lock_screen">Secure lock screen has not been set up. Go to 6613 Settings -> Security to set up a lock screen.</string> 6614 <string name="unlock_req_config_lock_screen_and_biometrics">Secure lock screen has not been set 6615 up. Go to Settings -> Security to set up a lock screen and biometric unlock.</string> 6616 <string name="unlock_req_config_biometrics">Biometric unlock has not been set up. Go to Settings 6617 -> Security to set up biometric unlock.</string> 6618 <string name="unlock_req_biometric_lock">Lock the screen, wait 5 seconds, then unlock with 6619 biometrics.</string> 6620 <!-- This message should only be displayed briefly immediately after the user has unlocked 6621 the device; as soon as key access is verified this message will be updated. --> 6622 <string name="unlock_req_unlocked">Verifying the key is accessible after the unlock...</string> 6623 <string name="unlock_req_credential_lock">Lock the screen, wait 5 seconds, then unlock with 6624 credentials.</string> 6625 <string name="unlock_req_successful">Test completed successfully.</string> 6626 <string name="unlock_req_failed_key_available_when_locked">Test failed; the key was available 6627 when the device was locked.</string> 6628 <string name="unlock_req_failed_key_unavailable_when_unlocked">Test failed; the key was not 6629 available when the device was unlocked.</string> 6630 <!-- While this state should never be reached since all possible states are accounted for 6631 it is included just in case. --> 6632 <string name="unlock_req_unknown_state">The test is in an unexpected state; please dismiss 6633 this dialog and restart the test.</string> 6634 6635 <!-- Notification Bubble Tests--> 6636 <string name="bubbles_notification_title">Bubble Notification Tests</string> 6637 <string name="bubbles_test_title">Bubble Tests</string> 6638 <string name="bubbles_test_info">This set of tests checks the settings, UI, and behaviour of 6639 bubble notifications. Bubbles are special notifications that can appear as a floating button 6640 on the screen along with a notification in the notification shade. When the floating button 6641 is tapped an activity is opened in a contained view and the notification is hidden from the 6642 shade.</string> 6643 <!-- Default settings --> 6644 <string name="bubbles_test_check_defaults_title">Check Default Settings</string> 6645 <string name="bubbles_test_check_defaults_verify">This step verifies the default bubble 6646 settings on the device. \n\n 6647 Bubbles are enabled at a feature level and at a per-app level.\n\n 6648 By default, bubbles are enabled at a feature level, but off for apps until the user opts in. 6649 \n\nIf the default settings are correct, the test will indicate that the state is correct. 6650 </string> 6651 <!-- Bubble button --> 6652 <string name="bubbles_test_bubble_button_title">Bubble Button</string> 6653 <string name="bubbles_test_bubble_button_verify">1. Click the button below to send a bubble 6654 notification.\n\n 6655 2. Pull down the notification shade and press the bubble button on the bottom right of the 6656 notification.\n\n 6657 3. Pass this test if tapping the bubble button opens the bubble.</string> 6658 <string name="bubbles_test_bubble_button_button">Send notification</string> 6659 <!-- Bubble preference selected --> 6660 <string name="bubbles_test_app_selected_title">Check Settings After Bubble Button</string> 6661 <string name="bubbles_test_app_selected_verify">When a notification is turned into a bubble 6662 via the bubble button, the app setting for bubbles will change to allow selected 6663 notifications to bubble. If the settings are right, the test will indicate that the state 6664 is correct.</string> 6665 <!-- Disable at feature level --> 6666 <string name="bubbles_test_disable_title">Disable Bubbles Feature</string> 6667 <string name="bubbles_test_disable_verify">Click the button to open notification settings, 6668 find Bubbles and turn the feature off. When the setting is off, the test will indicate that 6669 the state is correct.</string> 6670 <string name="bubbles_test_disable_button">Open settings</string> 6671 <!-- App settings available when disabled --> 6672 <string name="bubbles_test_enable_title">Enable Bubbles for CTS Verifier</string> 6673 <string name="bubbles_test_enable_verify">1. Click the button below and enable bubbles for the 6674 verifier app on the resulting screen, select "All conversations can bubble".\n\n 6675 2. You will be prompted to turn on bubbles for the device, turn them on.\n\n 6676 Once this is done, the test will indicate that the state is correct.</string> 6677 <string name="bubbles_test_enable_button">Open bubble settings</string> 6678 <!-- Send bubble --> 6679 <string name="bubbles_test_send_bubble_title">Send bubble notification</string> 6680 <string name="bubbles_test_send_bubble_verify">Click the button below and verify that there is a 6681 bubble on the screen and a notification in the notification shade. 6682 </string> 6683 <string name="bubbles_test_send_bubble_button">Send bubble notification</string> 6684 <!-- Suppress notification --> 6685 <string name="bubbles_test_suppress_notif_title">Hide notification</string> 6686 <string name="bubbles_test_suppress_notif_verify">Click the button below and verify that the 6687 bubble is still on the screen, but the notification is now hidden from the notification 6688 shade. 6689 </string> 6690 <string name="bubbles_test_suppress_notif_button">Update bubble to hide notification</string> 6691 <!-- Add notification --> 6692 <string name="bubbles_test_add_notif_title">Show notification</string> 6693 <string name="bubbles_test_add_notif_verify">Click the button below and verify that the bubble 6694 is still on the screen, the notification is now visible in the notification shade, and the 6695 bubble has a dot indicating the new message. 6696 </string> 6697 <string name="bubbles_test_add_notif_button">Update bubble to show notification</string> 6698 <!-- Remove bubble metadata --> 6699 <string name="bubbles_test_remove_metadata_title">Remove bubble</string> 6700 <string name="bubbles_test_remove_metadata_verify">Click the button below and verify that the 6701 bubble is removed from the screen, and the notification is still visible in the notification 6702 shade.</string> 6703 <string name="bubbles_test_remove_metadata_button">Remove bubble</string> 6704 <!-- Add bubble metadata --> 6705 <string name="bubbles_test_add_metadata_title">Add bubble</string> 6706 <string name="bubbles_test_add_metadata_verify">Click the button below and verify that the 6707 bubble appears on the screen, and the notification is still visible in the notification 6708 shade.</string> 6709 <string name="bubbles_test_add_metadata_button">Add bubble</string> 6710 <!-- Expand bubble --> 6711 <string name="bubbles_test_expand_bubble_title">Open bubble</string> 6712 <string name="bubbles_test_expand_bubble_verify">Tap on the bubble to open it, then tap on the 6713 bubble again to collapse it and return to this screen. Verify that after opening the bubble, 6714 there is no longer a notification for it visible in the notification shade.</string> 6715 <!-- Dismiss bubble --> 6716 <string name="bubbles_test_dismiss_title">Drag and dismiss bubble</string> 6717 <string name="bubbles_test_dismiss_verify">Click the button below and verify that the bubble 6718 is still on screen, and the notification is visible in the notification shade.\n\n 6719 Drag the bubble, while dragging a UI affordance should show. Verify that: \n\n 6720 1. Dragging and dropping the bubble on that UI affordance removes it from the screen.\n\n 6721 2. The notification should remain in the notification shade.</string> 6722 <string name="bubbles_test_dismiss_button">Update bubble to show notification</string> 6723 <!-- Dismiss notification --> 6724 <string name="bubbles_test_dismiss_notif_title">Dismiss notification</string> 6725 <string name="bubbles_test_dismiss_notif_verify">Click the button below and verify that a bubble 6726 appears on screen, and the notification is visible in the notification shade.\n\n 6727 Dismiss the notification from the notification shade and verify that the bubble remains on 6728 screen.</string> 6729 <string name="bubbles_test_dismiss_notif_button">Send bubble notification</string> 6730 <!-- Auto expand bubble --> 6731 <string name="bubbles_test_autoexpand_title">Auto expand bubble</string> 6732 <string name="bubbles_test_autoexpand_verify">Click the button below and verify that a bubble 6733 appears on screen, auto-expanded.</string> 6734 <string name="bubbles_test_autoexpand_button">Send auto-expanded bubble notification</string> 6735 <!--Overflow exists --> 6736 <string name="bubbles_test_overflow_title">Bubble overflow (empty)</string> 6737 <string name="bubbles_test_overflow_verify">Tap the bubble to expand it and verify there is an 6738 affordance to see previous bubbles. It should be empty right now and show an empty state 6739 message.</string> 6740 <!-- Bubbles appear in overflow --> 6741 <string name="bubbles_test_bubbles_in_overflow_title">Bubble overflow (with bubbles)</string> 6742 <string name="bubbles_test_bubbles_in_overflow_verify">1. Press the button below to create 6743 several bubbles.\n\n 6744 2. Expand the stack and drag down two of the bubbles to dismiss them.\n\n 6745 3. Tap on the bubble overflow, pass this test if the two bubbles you dismissed are in 6746 the overflow. </string> 6747 <string name="bubbles_test_bubbles_in_overflow_button">Send several bubbles</string> 6748 <!-- Add bubble from overflow --> 6749 <string name="bubbles_test_add_from_overflow_title">Add bubble from overflow</string> 6750 <string name="bubbles_test_add_from_overflow_verify">1. Expand the stack and open the bubble 6751 overflow.\n\n 2. Tap on a bubble in the overflow, pass this test if that bubble is opened. 6752 </string> 6753 <!-- Cancel removes bubbles in overflow --> 6754 <string name="bubbles_test_cancel_overflow_title">Cancel removes overflowed bubbles</string> 6755 <string name="bubbles_test_cancel_overflow_verify">1. Press the button below, it will cancel all 6756 previous bubble notifications and post one more.\n\n 6757 2. Expand that bubble, navigate to the overflow and ensure that it is empty.</string> 6758 <string name="bubbles_test_cancel_overflow_verify2">1. Press the button below, it will cancel 6759 all previous bubble notifications and post one more.\n\n 6760 2. Expand that bubble, observe that there is no overflow button.</string> 6761 <string name="bubbles_test_cancel_overflow_button">Cancel previous bubbles and post a 6762 single bubble</string> 6763 <!-- Tap on notification with bubble in the overflow --> 6764 <string name="bubbles_test_tap_notif_with_overflow_title">Tap on notification opens bubble 6765 </string> 6766 <string name="bubbles_test_tap_notif_with_overflow_verify">1. Press the button to create a 6767 bubble.\n\n 6768 2. Dismiss the bubble without opening it.\n\n 6769 3. Tap on the notification. Pass this test if the notification opened as a bubble.</string> 6770 <string name="bubbles_test_tap_notif_with_overflow_button">Send bubble</string> 6771 <!-- Portrait & landscape positioning --> 6772 <string name ="bubbles_test_expanded_position_title">Portrait and landscape positioning</string> 6773 <string name="bubbles_test_expanded_position_phone_verify">1. While in portrait orientation, 6774 tap on the bubble to open it.\n\n 6775 2. Verify that the bubbles show at the top of the screen.\n\n 6776 3. Rotate the device to landscape orientation.\n\n 6777 3. Verify that the bubbles are aligned to the left or right edge of the screen.</string> 6778 <string name="bubbles_test_expanded_position_largescreen_verify"> 6779 1. Tap the bubble to open it.\n\n 6780 2. Verify that the bubbles are aligned to the left or right edge of the screen.\n\n 6781 3. Rotate the device.\n\n 6782 4. Verify that the bubbles are aligned to the left or right edge of the screen.</string> 6783 <!-- Expanded view scrim --> 6784 <string name="bubbles_test_expanded_scrim_title">Expanded state has scrim</string> 6785 <string name="bubbles_test_expanded_scrim_verify">Expand the bubble and pass this test if the 6786 area below the bubble is dimmed (like when a dialog is opened).</string> 6787 <!-- IME insets --> 6788 <string name="bubbles_test_ime_title">IME behavior</string> 6789 <string name="bubbles_test_ime_verify">1. Tap on the bubble to open it.\n\n 6790 2. Tap the edit text in the bubble to bring up the IME.\n\n 6791 3. Pass this test if the IME appears and the edit text is still visible.</string> 6792 <!-- Expanded view min height --> 6793 <string name="bubbles_test_min_height_title">Expanded view min height</string> 6794 <string name="bubbles_test_min_height_verify">1. Press the button below to update the bubble to 6795 have the smallest height.\n\n 6796 2. Open the bubble, it will tell you if the height is correct.</string> 6797 <string name="bubbles_test_min_height_button">Send small height bubble</string> 6798 <!-- Expanded view max height --> 6799 <string name="bubbles_test_max_height_title">Expanded view max height</string> 6800 <string name="bubbles_test_max_height_verify">1. Press the button below to update the bubble to 6801 have the maximum height.\n\n 6802 2. Open the bubble, it will tell you if the height is correct.</string> 6803 <string name="bubbles_test_max_height_button">Send max height bubble</string> 6804 <!-- Low ram --> 6805 <string name="bubbles_test_lowram_title">No bubbles on low memory device</string> 6806 <string name="bubbles_test_lowram_verify">Click the button below and verify that a 6807 bubble does NOT appear on screen. Verify that there is a notification in the notification 6808 shade.</string> 6809 <string name="bubbles_test_lowram_button">Add bubble</string> 6810 <!-- Disable bubbles by config_supportsBubble --> 6811 <string name="bubbles_test_disable_config_title">No bubbles on bubbles disabled device</string> 6812 <string name="bubbles_test_disable_config_verify">Click the button below and verify that a 6813 bubble does NOT appear on screen. Verify that there is a notification in the notification 6814 shade.</string> 6815 <string name="bubbles_test_disable_config_button">Add bubble</string> 6816 <!-- Bubbles end of test summary --> 6817 <string name="bubbles_test_summary_title">Test Complete</string> 6818 <string name="bubbles_test_summary">%1$d out of %2$d tests passed</string> 6819 <string name="bubble_activity_title">Bubble Activity</string> 6820 <string name="bubble_test_state_correct">State is correct, pass the test.</string> 6821 <string name="bubble_test_state_waiting">State is not correct, waiting for the correct state. 6822 </string> 6823 <string name="bubble_test_ime_hint">Tap for IME</string> 6824 <string name="bubble_test_expanded_view">Bubble expanded view</string> 6825 6826 <!-- Toast test --> 6827 <string name="toast_title">Toast test (may auto pass if CtsVerifier isn\'t targeting 6828 S+)</string> 6829 <string name="toast_info">This test checks the behavior for toasts for apps targeting 6830 sdk S+ (31). Toasts are short messages that appear as popups for a limited amount of time. 6831 </string> 6832 <string name="toast_instructions_pre_s">No cts requirement for toasts for apps targeting 6833 pre-s. Auto pass this test.</string> 6834 <string name="toast_instructions_s">Press the button below to post a toast. Pass this 6835 test if a toast appears and has:\n 6836 \n\t1. a maximum of two lines 6837 \n\t2. an application icon 6838 </string> 6839 <string name="toast_post_button_label">Post toast</string> 6840 <string name="toast_long_text">Lorem ipsum dolor sit amet, consectetur adipiscing elit. 6841 Nam luctus eros ac interdum tincidunt. Vestibulum dignissim, metus nec tempor mollis, 6842 tortor leo aliquam est, eget rutrum mi nisi ut ligula. Quisque enim justo, tempus at 6843 ligula ac, porta posuere odio. Proin et tortor tincidunt, tempus ligula id, 6844 vestibulum mauris. Vivamus blandit tristique tempus. Integer dignissim purus eu nibh 6845 faucibus, eget dignissim eros gravida. Sed sit amet erat quis leo pharetra euismod vel at 6846 purus. Duis blandit, diam eu imperdiet pulvinar, erat odio eleifend augue, nec luctus 6847 lectus erat ac nibh. Nullam id enim metus. 6848 </string> 6849 6850 <!-- Strings for Instant Apps --> 6851 <string name="ia_instruction_heading_label">Instructions:</string> 6852 <string name="ia_instruction_text_photo_label">READ BEFORE STARTING TEST</string> 6853 <string name="ia_start_test_button_caption">Start Test</string> 6854 <string name="ia_install_dialog_title">Install Instant App</string> 6855 <string name="ia_install_dialog_text"> 6856 For this test you need to install CtsVerifierInstantApp.apk by running \n 6857 adb install -r --instant /path/to/CtsVerifierInstantApp.apk \n\n 6858 CtsVerifierInstantApp.apk can be found in android-cts-verifier.zip that you have downloaded. 6859 </string> 6860 <string name="ia_notification">Instant Apps Notification Test</string> 6861 <string name="ia_notification_info"> 6862 This test verifies that Instant Apps notification is shown when an Instant App is at foreground.\n\n 6863 - Read the message above the \"Start Test\" button for 6864 step-by-step instructions. 6865 </string> 6866 <string name="ia_notification_instruction_label">\n 6867 1. Click Start Test. \n\n 6868 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 6869 3. Drag down the notification bar when the sample Instant App is at foreground. \n\n 6870 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 6871 5. Click Pass button if all checks in step 4 passed, otherwise click Fail button. 6872 </string> 6873 <string name="ia_recents">Instant Apps Recents Test</string> 6874 <string name="ia_recents_info"> 6875 This test verifies that Instant App can be accessed in Recent Apps screen.\n\n 6876 - Read the message above the \"Start Test\" button for 6877 step-by-step instructions. 6878 </string> 6879 <string name="ia_recents_instruction_label">\n 6880 1. Click Start Test. \n\n 6881 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 6882 3. Tap Recents button, verify the sample Instant App is shown in Recent Apps screen. \n\n 6883 4. Tap the sample Instant App in Recent Apps screen, verify the Instant App is opened in the foreground. \n\n 6884 5. Click Pass button if checks in step 3 and 4 passed, otherwise click Fail button. 6885 </string> 6886 <string name="ia_app_info">View/Delete Instant Apps Test</string> 6887 <string name="ia_app_info_info"> 6888 This test verifies that Instant App can be viewed and deleted in Settings.\n\n 6889 - Read the message above the \"Start Test\" button for 6890 step-by-step instructions. 6891 </string> 6892 <string name="ia_app_info_instruction_label">\n 6893 1. Click Start Test. \n\n 6894 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 6895 3. Open Settings App. \n\n 6896 4. Tap Apps & Notifications. \n\n 6897 5. Verify the sample Instant App can be found and it is shown as \"Instant App\". \n\n 6898 6. Verify there is an action allowing user to clear/delete app. \n\n 6899 7. Click Pass button if checks in step 5 and 6 passed, otherwise click Fail button. 6900 </string> 6901 6902 <string name="uap_test_no">No</string> 6903 <string name="uap_test_yes">Yes</string> 6904 <string name="uap_test_info">Info</string> 6905 <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> 6906 <string name="uap_refmic_question">Does this device allow for the connection of a USB reference microphone?</string> 6907 <string name="uap_test_hostmode_info_caption">USB Host Mode Audio Required</string> 6908 <string name="uap_test_hostmode_info_text">This test requires a USB audio peripheral be 6909 connected to the device. 6910 The DUT may not support USB Host Mode Audio, either because it does not have a 6911 USB port, or USB Host Mode Audio has been removed from the OS. In this case, the test can be 6912 passed by pressing the \"No\" button and indicating \"Test Pass\" at the bottom. 6913 \n\nNote: Handheld devices supporting USB host mode MUST support USB audio class (CDD 7.7 .2/H-1-1) 6914 \n\nNote: Devices declaring feature android.hardware.audio.pro MUST implement USB host mode (CDD 5.10 C-1-3). 6915 Devices that omit a 4 conductor 3.5mm audio jack MUST support USB audio class (CDD 5.10 C-3-1). 6916 </string> 6917 <string name="uap_test_playing">Playing. Now press stop.</string> 6918 6919 <string name="refmic_test_no">No</string> 6920 <string name="refmic_test_yes">Yes</string> 6921 <string name="refmic_test_info">Info</string> 6922 <string name="refmic_test_question">Does this device allow for the connection of a USB reference microphone?</string> 6923 <string name="ref_mic_dlg_caption">Reference Mic Required</string> 6924 <string name="ref_mic_dlg_text">This test requires a USB Reference Mic to be connected to the device. 6925 If the device under test does not support USB Host Mode Audio (either because it does not have a 6926 USB port, or USB Host Mode Audio has been removed from the OS) you can be granted a provisional 6927 pass on this test by pressing the \"No\" button and indicating \"Test Pass\" at the bottom.\n 6928 Note: Handheld devices supporting USB host mode MUST support USB audio class (CDD 7.7 .2/H-1-1)\n 6929 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) 6930 </string> 6931 6932 <string name="loopback_test_question">Does this device allow for the connection of a loopback audio peripheral?</string> 6933 <string name="loopback_dlg_caption">Loopback Peripheral Required</string> 6934 6935 <string name="display_cutout_test">DisplayCutout Test</string> 6936 <string name="display_cutout_test_instruction">\n 6937 This test is to make sure that the area inside the safe insets from the DisplayCutout should be:\n 6938 1. Visible\n 6939 2. Clickable.\n 6940 </string> 6941 6942 <!-- TTS Test Resources --> 6943 <string name="tts_test">TTS Test</string> 6944 <string name="tts_test_info"> 6945 1. Install the CtsTtsEngineSelectorTestHelper and CtsTtsEngineSelectorTestHelper2 apps on the device.\n 6946 2. Click on the "Go To Accessibility Settings" button.\n 6947 3. Go to Text-to-speech output > Preferred engine.\n 6948 4. Ensure that two engines are listed, both named "TTS CTS Test Helper App".\n 6949 5. Ensure that each engine can be selected. 6950 </string> 6951 <string name="tts_test_steps"> 6952 1. Install the CtsTtsEngineSelectorTestHelper and CtsTtsEngineSelectorTestHelper2 apps on the device.\n 6953 2. Click on the "Go To Accessibility Settings" button.\n 6954 3. Go to Text-to-speech output > Preferred engine.\n 6955 4. Ensure that two engines are listed, both named "TTS CTS Test Helper App".\n 6956 5. Ensure that each engine can be selected. 6957 </string> 6958 <string name="tts_accessibility_settings_button">Go To Accessibility Settings</string> 6959 6960 <!-- Strings for SecurityModeFeatureVerifierActivity test --> 6961 <string name="security_mode_feature_verifier_test">SecurityModeFeatureVerifier Test</string> 6962 <string name="security_mode_feature_verifier_instructions">This test verifies that the PackageManager.FEATURE_SECURITY_MODEL_COMPATIBLE feature is present.</string> 6963 <string name="handheld_or_tablet_text_before_test">Is this a handheld or tablet device?</string> 6964 <string name="handheld_or_tablet_yes">Yes</string> 6965 <string name="handheld_or_tablet_not_applicable">Not applicable</string> 6966 6967 <!-- AudioDescriptor Test --> 6968 <string name="audio_descriptor_test">Audio Descriptor Test</string> 6969 <string name="audio_descriptor_test_info"> 6970 This test tests if the reported AudioDescriptor is valid and necessary.\n 6971 AudioDescriptor must only be used to report audio device capabilities that are not able to 6972 describe by Android defined enums.\n 6973 \nTo execute test:\n 6974 1. Plug in HDMI cable if there is an HDMI port on the device.\n 6975 2. The test will run when clicking TEST button.\n 6976 </string> 6977 <string name="audio_descriptor_run_test">Test</string> 6978 <string name="audio_descriptor_HDMI_support_label">HDMI connection status:</string> 6979 <string name="audio_descriptor_has_hdmi_support">Has HDMI Port</string> 6980 <string name="audio_descriptor_hdmi_NA">N/A. HDMI support is not claimed.</string> 6981 <string name="audio_descriptor_hdmi_pending">No HDMI detected. Pending…</string> 6982 <string name="audio_descriptor_hdmi_connected">Connected.</string> 6983 <string name="audio_descriptor_pass">Pass</string> 6984 <string name="audio_descriptor_hdmi_claimed_but_not_connected"> 6985 HDMI is claimed as supported but not yet connected. 6986 </string> 6987 <string name="audio_descriptor_standard_none">Standard is none.</string> 6988 <string name="audio_descriptor_is_null">Audio descriptor is null.</string> 6989 <string name="audio_descriptor_unrecognized_standard">Standard %1$d is unrecognized.</string> 6990 <string name="audio_descriptor_length_error"> 6991 The length of short audio descriptor is %1$d, but it is expected to be 3. 6992 </string> 6993 <string name="audio_descriptor_cannot_get_hal_version">Cannot get audio HAL version</string> 6994 <string name="audio_descriptor_invalid_hal_version">Invalid audio HAL version %1$s</string> 6995 <string name="audio_descriptor_format_code_should_not_be_reported"> 6996 Format with format code as %1$d(%2$s) should not be reported by AudioDescriptor. 6997 Instead, it should be reported by Android defined enums. 6998 </string> 6999 <string name="audio_descriptor_format_extended_code_should_not_be_reported"> 7000 Format with format extended code as %1$d(%2$s) should not be reported by AudioDescriptor. 7001 Instead, it should be reported by Android defined enums. 7002 </string> 7003 <string name="audio_descriptor_format_extended_code_is_not_used"> 7004 Format extended code as %1$d is not used. 7005 </string> 7006 <string name="audio_descriptor_hdmi_info_title">HDMI Support</string> 7007 <string name="audio_descriptor_hdmi_message"> 7008 Please connect an HDMI peripheral to validate AudioDescriptor. 7009 </string> 7010 7011 <string name="uwb">Uwb</string> 7012 <string name="presence_test">Presence Test</string> 7013 <string name="presence_test_info"> 7014 The Presence tests check whether or not a device is properly calibrated for BLE, NAN and UWB based on Presence requirements. 7015 \nAll tests are required to pass on every device, if the radio technology is supported 7016 </string> 7017 <string name="presence_test_tv_info"> 7018 The Presence tests check whether or not a device is properly calibrated for BLE, NAN and UWB based on Presence requirements. 7019 \nAll tests are required to pass on all Android T+ launched TV devices, if the radio technology is supported. 7020 \nIf the TV device is launched on older Android letters, all tests will be disabled. Press Pass to pass this case. 7021 </string> 7022 <string name="is_reference_device_checkbox_text">Is Reference Device</string> 7023 <string name="is_manual_pass_text">Pass test manually after test completion</string> 7024 <string name="use_extended_advertisement_text">Use extended advertisement</string> 7025 <string name="uwb_precision">Uwb Precision Test</string> 7026 <string name="uwb_short_range">Uwb Short Range Test</string> 7027 <string name="uwb_precision_instruction"> 7028 1. Take 1000 measurements with DUT at 1m distance from the reference device in a non-reflective chamber. 7029 \n2. Sort the 1000 measurements and compute the range as 975th measurement - 25th measurement 7030 \n3. Report the range below - Must be within 30cm (distance) for tests to pass. 7031 </string> 7032 <string name="report_distance_range_cm">Report Range (cm)</string> 7033 <string name="uwb_short_range_instruction"> 7034 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 7035 \n2. Sort the values. 7036 \n3. Report the median (500th value) (must be within 0.75m and 1.25m to pass). 7037 \n4. Report the reference device used. 7038 </string> 7039 <string name="report_distance_median_meters">Report Median (meters)</string> 7040 <string name="report_reference_device">Report Reference Device</string> 7041 <string name="uwb_not_supported">Uwb is not supported on device. Finishing activity. </string> 7042 <string name="ble">BLE</string> 7043 <string name="start_test_presence">Start Test</string> 7044 <string name="stop_test_presence">Stop Test</string> 7045 <string name="start_advertising_presence">Start Advertising</string> 7046 <string name="stop_advertising_presence">Stop Advertising</string> 7047 <string name="device_id_info_presence">You are advertising with deviceId: %1$d</string> 7048 <string name="device_found_presence">Reference device found. %1$d of %2$d samples collected</string> 7049 <string name="result_pending_presence">Awaiting Rx RSSI median from reference device... </string> 7050 <string name="dut_test_result_info_presence">Tx RSSI median: %1$d. Rx RSSI median received from reference device: %2$d</string> 7051 <string name="ref_test_result_info_presence">Rx RSSI median computed: %1$d.</string> 7052 <string name="reference_device_id_input_presence">Enter the device ID displayed on the advertising device</string> 7053 <string name="tx_power_input_presence">Optional. Configure advertising TX power. Default is 1(TX_POWER_HIGH)</string> 7054 7055 <!-- Strings for BLE RSSI Precision Test --> 7056 <string name="ble_rssi_precision_name">BLE RSSI Precision Test</string> 7057 <string name="ble_rssi_precision_test_instructions"> 7058 Place the device under test (DUT) at 1m from the reference device (advertising device) in line of sight environment 7059 \nDUT instructions 7060 \n1. Ensure that the reference device is already advertising. 7061 \n2. Input the device ID of the reference device (displayed on the reference device) into the provided field and click "Start Test" 7062 \n3. The test is automatically stopped and passed (or failed )when all the required data is collected 7063 \nReference device instructions 7064 \n1. Ensure that the "Is reference device" checkbox is checked, then click, "Start Advertising" 7065 </string> 7066 7067 <!-- Strings for BLE Rx/Tx Offset Precision Test --> 7068 <string name="ble_rx_tx_offset_precision_name">BLE Rx/Tx Offset Precision Test</string> 7069 <string name="ble_rx_tx_offset_precision_test_instructions"> 7070 Place the device under test (DUT) at 1m from the reference device (advertising device) in line of sight environment 7071 \nDUT instructions 7072 \n1. Ensure that the test is already started on the reference device. 7073 \n2. Input the device ID of the reference device (displayed on the reference device) into the provided field and click "Start Test" 7074 \n3. The test is automatically stopped and passed (or failed) when all the required data is collected 7075 \n4. The test is passed if the median RSSI from both DUT and reference device is between -65dBm and -35dBm. 7076 \nReference device instructions 7077 \n1. Ensure that the "Is reference device" checkbox is checked, then click, "Start Advertising" 7078 </string> 7079 7080 <!-- Strings for NAN Accuracy Test --> 7081 <string name="nan_accuracy_test_instructions"> 7082 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" 7083 \n\nDUT instructions 7084 \n1. Ensure that the reference device is already publishing the NAN service. Enter the service ID displayed. 7085 \n2. Make sure that the toggle for the right test distance is checked. 7086 \n3. Click "Start Test". The display would be updated to show status "IN_PROGRESS" for the corresponding test distance. 7087 \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. 7088 \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. 7089 \n6. Repeat for the other distances by selecting the corresponding radio button. 7090 </string> 7091 <string name="nan_accuracy_test_name">Nan Accuracy Test</string> 7092 <string name="wifi_nan">WiFi NAN</string> 7093 <string name="start_publishing_presence">Start Publishing</string> 7094 <string name="stop_publishing_presence">Stop Publishing</string> 7095 <string name="select_test_distance_presence">Select Test Distance</string> 7096 <string name="distance_10cm_presence">10cm</string> 7097 <string name="distance_1m_presence">1m</string> 7098 <string name="distance_3m_presence">3m</string> 7099 <string name="distance_5m_presence">5m</string> 7100 <string name="service_id_info_presence">Your unique service ID is: %1$d</string> 7101 <string name="service_id_input_presence">Enter the service ID displayed on the publishing device</string> 7102 7103 <!-- Strings for AudioMicrophoneMuteToggleActivity --> 7104 <string name="audio_mic_toggle_test">Audio Microphone Hardware Toggle Mute Test</string> 7105 <string name="audio_mic_toggle_test_info"> 7106 This test verifies that devices which implement microphone hardware privacy toggles enforce sensor privacy when toggles are enabled. 7107 \nTo pass the test: 7108 \n - <a href="https://source.android.com/compatibility/android-cdd#9813_sensorprivacymanager">The audio stream should be muted</a>. 7109 \n - A dialog or notification should be shown that informs the user that the sensor privacy is enabled. 7110 </string> 7111 <string name="audio_mic_toggle_test_instruction1"> 7112 Mute the microphone using the hardware privacy toggle. 7113 \nPress the RECORD button. 7114 \nObserve a dialog with information regarding the microphone being blocked 7115 \nIgnore/cancel the dialog and wait for the recording to complete. 7116 \nThe pass button will be enabled if the test succeeded.</string> 7117 <string name="audio_mic_toggle_test_analyzing">Analyzing, please wait...\n</string> 7118 7119 <!-- Strings for CameraMuteToggleActivity --> 7120 <string name="camera_hw_toggle_test">Camera Hardware Toggle Mute Test</string> 7121 <string name="camera_hw_toggle_test_info"> 7122 This test verifies that devices which implement camera hardware privacy toggles enforce sensor privacy when toggles are enabled. 7123 \nTo pass the test: 7124 \n - <a href="https://source.android.com/compatibility/android-cdd#9813_sensorprivacymanager">The video stream should be muted</a>. 7125 \n - A dialog or notification should be shown that informs the user that the sensor privacy is enabled. 7126 </string> 7127 <string name="camera_hw_toggle_test_instruction"> 7128 Mute the camera using the hardware privacy toggle. 7129 \nObserve a dialog with information regarding the camera being blocked. 7130 \nCamera preview should show a blank feed. 7131 \nPress the Take Photo button. 7132 \nCaptured image should be black. 7133 \nMark the test as passing if the above conditions are met.</string> 7134 <string name="camera_hw_toggle_test_no_camera"> 7135 No available camera found. 7136 \nAdd or enable a camera and re-run this test. 7137 </string> 7138 7139 <!-- Strings for ControlsPanelVerifierActivity --> 7140 <string name="controls_panel_test">Controls Panel tests</string> 7141 <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> 7142 <string name="controls_panel_install_test">0. Install helper app</string> 7143 <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> 7144 <string name="controls_panel_install_test_instructions">You should have received a helper app apk with this CTS 7145 Verifier package. Its name is \"CtsDeviceControlsApp\". Install the test app, by running\n 7146 \"adb install /path/to/CtsDeviceControlsApp.apk\".\n 7147 Pass the test if the install was successful, or if the app was already installed. Fail it otherwise.</string> 7148 <string name="controls_panel_basic_test">1. Controls Panel visible test</string> 7149 <string name="controls_panel_basic_test_info">This test verifies that an app that uses the 7150 correct metadata will be able to show a panel (custom activity) in the device controls space.</string> 7151 <string name="controls_panel_general_test_instructions">Open the Device controls space in this device. 7152 This is the space that allows you to control individual home automation devices for many apps.\n\n 7153 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 7154 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. 7155 Once the app is selected, you should see a container with the title \"Cts controls\" 7156 and content that starts with \"This is a panel belonging to Cts controls\".\n\n</string> 7157 <string name="controls_panel_basic_test_instructions"> 7158 If you can observe this panel, pass this test. Otherwise fail this test. 7159 </string> 7160 <string name="controls_panel_setting_test_false">2a. Controls Panel setting in extra test false value</string> 7161 <string name="controls_panel_setting_test_true">2b. Controls Panel setting in extra test true value</string> 7162 <string name="controls_panel_dream_test_false">3a. Control Panel starting on keyguard test false value </string> 7163 <string name="controls_panel_dream_test_true">3b. Control Panel starting as a dream test true value </string> 7164 <string name="controls_panel_setting_test_info">This test verifies that an app that shows a 7165 panel in the device controls space will receive the correct value of the setting for controlling 7166 devices on the lock screen as part of their intent extras.\n\n 7167 For this test, you will need to have set up a screen lock.</string> 7168 <string name="controls_panel_settings_test_open_lockscreen_settings">Open Settings</string> 7169 <string name="controls_panel_setting_test_instructions">Using the button below, open Settings. 7170 Find the setting that allows you to control external devices from the lockscreen 7171 (you might need to enable other settings for it to be available). Set that setting to %1$s. 7172 \n Then, open the device controls space (instructions below the button) and verify that the 7173 text inside the panel indicates that the setting is %1$s 7174 </string> 7175 <string name="controls_panel_dream_true_test_instructions"> 7176 1 - Find the Home Control Panel \n 7177 - Open Settings, Search for "Screen Saver", find \"Home Controls\", \n\n 7178 2 - For Case When Dock is Available\n 7179 - Place the device on the dock and wait for the device to time out. \n\n 7180 3 - For Case When Dock is Not Available \n 7181 - Update \"When to start\" to \"While Charging\". \n 7182 - Press the preview button or wait for the device to time out to enter dream mode. \n\n 7183 4 - Verification of Hosting Status \n 7184 - Verify that the hosting status is \"Hosted in Dream Service\". 7185 </string> 7186 7187 <string name="controls_panel_dream_false_test_instructions"> 7188 Using the button below, open Settings. 7189 Find the setting that allows you to control external devices from the lockscreen 7190 (you might need to enable other settings for it to be available). Set that setting to true. 7191 \n Then, open the device controls space (instructions below the button) and verify that the 7192 hosting status is \"Not Hosted in Dream Service\" 7193 </string> 7194 7195 <!-- Strings for Input tests --> 7196 <string name="test_category_input">Input</string> 7197 <string name="usi_version_test">USI Version Test</string> 7198 <string name="usi_version_test_info">This test verifies that a device that supports a 7199 <a href="https://universalstylus.org">Universal Stylus Initiative (USI)</a> stylus through 7200 its built-in touchscreen correctly reports its supported USI version. 7201 </string> 7202 <string name="usi_version_yes">Yes</string> 7203 <string name="usi_version_no">No</string> 7204 <string name="usi_test_start">This test will ask you to verify that the reported 7205 <a href="https://universalstylus.org">Universal Stylus Initiative (USI)</a> protocol 7206 version is correct for each built-in display.\n 7207 To begin the test, please disconnect all external peripheral devices, such as mice, 7208 keyboards, or styluses that are connected through USB or Bluetooth.\n\n 7209 Found %1$d built-in display(s). Are you ready to proceed? 7210 </string> 7211 <string name="usi_test_verify_display_usi_support">Does the display \"%1$s\" support styluses 7212 that use the USI protocol? \n\n 7213 For more information about the Universal Stylus Initiative (USI) protocol, see: 7214 http://universalstylus.org 7215 </string> 7216 <string name="usi_test_verify_display_usi_version">The display \"%1$s\" reports its USI version 7217 as %2$s.\n\n 7218 Is this correct? 7219 </string> 7220 <string name="usi_test_passed">Test Passed\n\n 7221 Press Pass. 7222 </string> 7223 <string name="usi_test_failed">Test Failed\n\n 7224 Reason: %1$s 7225 </string> 7226 <string name="usi_fail_reason_not_ready">Not ready to check for USI stylus versions.</string> 7227 <string name="usi_fail_reason_version_not_found">The USI version for the display was not found. 7228 </string> 7229 <string name="usi_fail_reason_found_unexpected_version">The display reports support for a valid 7230 USI version, even though it does not support USI. 7231 </string> 7232 <string name="usi_fail_reason_incorrect_version">The reported USI version is incorrect. 7233 </string> 7234 7235 <!-- Strings for PreferredMixerAttributesTestActivity --> 7236 <string name="audio_preferred_mixer_attributes_test">Audio Preferred Mixer Attributes Test</string> 7237 <string name="audio_preferred_mixer_attributes_test_info"> 7238 This test verifies that apps can set preferred mixer attributes for USB devices. 7239 \nTo pass the test: 7240 \n - Connect a USB audio device to the Android device under test. 7241 \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. 7242 </string> 7243 <string name="audio_preferred_mixer_attributes_test_connect_usb_device">Please connect USB audio device</string> 7244 <string name="audio_preferred_mixer_attributes_test_usb_device_connected">USB device connected</string> 7245 <string name="audio_preferred_mixer_attributes_test_running">Running test, please wait…</string> 7246 <string name="audio_can_not_set_preferred_mixer_attributes">Cannot set preferred mixer attributes for USB device.</string> 7247 <string name="audio_set_preferred_mixer_attributes_failed">Set preferred mixer attributes failed.</string> 7248 <string name="audio_get_preferred_mixer_attributes_not_equal">Preferred mixer attributes are different from ones set.</string> 7249 <string name="audio_clear_preferred_mixer_attributes_failed">Clearing preferred mixer attributes failed.</string> 7250 <string name="audio_get_preferred_mixer_attributes_should_be_null">Preferred mixer attributes is not null after calling AudioManager#clearPreferredMixerAttributes.</string> 7251 <string name="audio_no_callback_for_preferred_mixer_attributes_changed">Callback is not called when preferred mixer attributes changed.</string> 7252 7253 <!-- Strings for Sharesheet tests --> 7254 <string name="category_sharesheet">Sharesheet</string> 7255 7256 <string name="sharesheet_payload_toggle_test">Sharesheet Payload Toggle Test</string> 7257 <string name="sharesheet_payload_toggle_test_info"> 7258 This test verifies that the system sharesheet properly handles the API that allows for shared items to be chosen from a larger set of optional items. 7259 \n\n 7260 1. Press the \"Share\" button below to launch the system sharesheet. 7261 \n\n 7262 2. In the system sharesheet, select all images and send them to the CTS verifier app. 7263 </string> 7264 <string name="sharesheet_payload_toggle_action_test">Sharesheet Payload Toggle Chooser Action Test</string> 7265 <string name="sharesheet_payload_toggle_chooser_action_test_info"> 7266 This test verifies that the system sharesheet properly handles the API that allows for chooser actions to be updated in response to a change in the set of shared items in the system sharesheet. 7267 \n\n 7268 1. Press the \"Share\" button below to launch the system sharesheet. 7269 \n\n 7270 2. In the system sharesheet, select all images and tap on the chooser action. 7271 </string> 7272 <string name="sharesheet_chooser_action">Test Action</string> 7273 <string name="sharesheet_wrong_intent_action">Wrong intent action; test failed.</string> 7274 <string name="sharesheet_wrong_intent_mime_type">Wrong intent mime type; test failed.</string> 7275 <string name="sharesheet_wrong_shared_items">Wrong set of shared items; test failed.</string> 7276 <string name="sharesheet_missing_result_intent_sender_invocation">Result intent sender was not invoked.</string> 7277 <string name="sharesheet_wrong_result_intent_sender_invocation">Incorrect result intent sender was invoked.</string> 7278 7279 <string name="sharesheet_album_test">Sharesheet Album Label Test</string> 7280 <string name="sharesheet_album_test_info">This test verifies that the system sharesheet responds to the \"album\" hint if provided by the app.</string> 7281 <string name="sharesheet_skipping_for_flag">Skipping the test due to disabled feature flag</string> 7282 <string name="sharesheet_share_label">Share</string> 7283 <string name="sharesheet_no_title_message">No title on sharesheet, test passed.</string> 7284 <string name="sharesheet_album_test_step_1">Press the \"Share\" button below to show the system sharesheet. 7285 When it\'s shown, look for a headline at the top saying something like \"Sharing text\". 7286 \n\nThen close the sharesheet and you\'ll be asked whether you saw a headline like that.</string> 7287 <string name="sharesheet_album_test_step_2">Did you see a title in the UI like \"Sharing Text\"?\n\nIf not sure, press Share again.</string> 7288 <string name="sharesheet_album_test_step_3">Now press the \"Share\" button again and see if the headline says something like \"Sharing album\" instead. 7289 \n\nIf the sharesheet indicates that it\'s an album being shared, pass the test, otherwise fail.</string> 7290 7291 <!-- Sharesheet ChooserResult test --> 7292 <string name="sharesheet_result_test_edit">Chooser Result: Edit</string> 7293 <string name="sharesheet_result_test_edit_info">This test verifies an app is notified taken the EDIT action is invoked within the Sharing UI.</string> 7294 <string name="sharesheet_result_test_edit_instructions">Tap the \"Share\" button below.\nWhen the Share UI opens, press the EDIT button.\n\nIf an EDIT button cannot be found, dismiss the UI to continue.</string> 7295 <string name="sharesheet_result_test_edit_instructions_short">Press Edit.</string> 7296 <string name="sharesheet_result_test_edit_pressed">The EDIT button was pressed</string> 7297 <string name="sharesheet_result_test_edit_not_found">The EDIT button could not be found</string> 7298 7299 <string name="sharesheet_result_test_copy">Chooser Result: Copy</string> 7300 <string name="sharesheet_result_test_copy_info">This test verifies an app is notified taken the COPY action is invoked within the Sharing UI.</string> 7301 <string name="sharesheet_result_test_copy_instructions">Tap the \"Share\" button below.\nWhen the Share UI open, press the COPY button.\n\nIf a COPY button cannot be found, dismiss the UI to continue.</string> 7302 <string name="sharesheet_result_test_copy_instructions_short">Press Copy .</string> 7303 <string name="sharesheet_result_test_copy_pressed">The COPY button was pressed</string> 7304 <string name="sharesheet_result_test_copy_not_found">The COPY button could not be found</string> 7305 7306 <string name="sharesheet_result_test_component">Chooser Result: Component</string> 7307 <string name="sharesheet_result_test_component_info">This test verifies an app is notified when a target component (APP) is selected in the Sharing UI.</string> 7308 <string name="sharesheet_result_test_component_instructions">Tap the \"Share\" button below.\nWhen the Share UI opens, tap the icon labeled \""CtsVerifier\".\n\nIf the \"CtsVerifier\" icon cannot be found, dismiss the UI to continue.</string> 7309 <string name="sharesheet_result_test_component_instructions_short">Tap the CtsVerifier Icon</string> 7310 <string name="sharesheet_result_test_component_selected">The CtsVerifier icon was selected</string> 7311 <string name="sharesheet_result_test_component_not_found">The CtsVerifier icon could not be found</string> 7312 7313 <string name="sharesheet_result_test_instructions_after_share">Choose from the options below:</string> 7314 7315 <string name="sharesheet_result_test_try_again">Try again</string> 7316 <string name="sharesheet_result_test_no_result_message">No result received - test failed</string> 7317 <string name="sharesheet_result_test_incorrect_result">Incorrect result received - test failed</string> 7318 <string name="sharesheet_result_test_no_button">Action not available - test passed</string> 7319 7320 <!-- Strings for CaptureContentForNotes test --> 7321 <string name="ccfn_tests">Capture Content For Notes Tests</string> 7322 <string name="ccfn_tests_info"> 7323 This test verifies the support for Content Capture For Notes APIs on devices that have the 7324 ROLE_NOTES enabled. 7325 7326 \n\nFor this test you need to install CtsDefaultNotesApp.apk and set it as the Default notes 7327 app. 7328 7329 \n\nFor some tests you will need to set up device owner. 7330 7331 \n\nPlease clear the device owner after all the test cases are run, if it was set up. 7332 </string> 7333 <string name="ccfn_tests_info_skip"> 7334 This test verifies the support for Content Capture For Notes APIs on devices that have the 7335 ROLE_NOTES enabled. 7336 7337 \n\nPlease mark this test as passed since ROLE_NOTES is not enabled on this device. 7338 </string> 7339 <!-- Dialogs --> 7340 <string name="set_default_notes_button_label">Set default notes app</string> 7341 <string name="set_default_notes_button_info"> 7342 For these tests you need to install CtsDefaultNotesApp.apk. 7343 \nThen you need to set it as the Default notes app setting through device settings app. 7344 \nThe Default notes app settings is generally under Apps -> Default apps -> Notes app. 7345 </string> 7346 <string name="setup_device_owner_button_label">Set up device owner</string> 7347 <string name="setup_device_owner_button_info"> 7348 Some tests require to set up device owner in order to enforce device manager policies. 7349 Please run: 7350 \nadb shell dpm set-device-owner --user 0 com.android.cts.verifier/.capturecontentfornotes.DeviceAdminTestReceiver 7351 </string> 7352 <!-- Error messages --> 7353 <string name="admin_policy_setup_failed"> 7354 Failed to set up device admin policy, is the device owner set up? 7355 </string> 7356 <!-- Toasts --> 7357 <string name="disable_screenshot_toast">Screenshots disabled successfully</string> 7358 <string name="enable_screenshot_toast">Screenshots enabled successfully</string> 7359 <string name="clear_device_owner_toast">Successfully cleared device owner</string> 7360 <string name="no_command_run_toast">No command run</string> 7361 <!-- Other button labels --> 7362 <string name="disable_screenshot_button_label">Disable screenshots</string> 7363 <string name="enable_screenshot_button_label">Enable screenshots</string> 7364 <string name="clear_device_owner_button_label">Clear device owner</string> 7365 <!-- Test titles and instructions --> 7366 <string name="ccfn_launch_and_add_test">Fire intent action then add screenshot</string> 7367 <string name="ccfn_launch_and_add_test_info"> 7368 1. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7369 \n2. Then tap on the Fire Intent Action button shown in the CtsDefaultNotesApp. 7370 \n3. Android SystemUI should show a UI with a button that lets you add the screenshot to the 7371 notes app, tap on this button. 7372 \n4. The CtsDefaultNotesApp should be back in focus informing that screenshot was received. 7373 \n5. If so, pass this test else fail. 7374 </string> 7375 <string name="ccfn_launch_and_cancel_test">Fire intent action then cancel screenshot</string> 7376 <string name="ccfn_launch_and_cancel_test_info"> 7377 1. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7378 \n2. Then tap on the Fire Intent Action button shown in the CtsDefaultNotesApp. 7379 \n3. Android SystemUI should show a UI with a button that lets you cancel, tap on this 7380 button. 7381 \n4. The CtsDefaultNotesApp should be back in focus informing that screenshot was not 7382 received. 7383 \n5. If so, pass this test else fail. 7384 </string> 7385 <string name="ccfn_launch_window_unsupported"> 7386 Fire intent action but window mode not supported 7387 </string> 7388 <string name="ccfn_launch_window_unsupported_info"> 7389 1. Open the CtsDefaultNotesApp using the app icon, this should launch the app in regular 7390 mode. 7391 \n2. Then tap on the Fire Intent Action button shown in the CtsDefaultNotesApp. 7392 \n3. Android SystemUI should not be shown, instead the CtsDefaultNotesApp should inform that 7393 window mode is unsupported. 7394 \n4. If so, pass this test else fail. 7395 </string> 7396 <string name="ccfn_launch_blocked_by_admin">Fire intent action but blocked by admin</string> 7397 <string name="ccfn_launch_blocked_blocked_by_admin_info"> 7398 1. Ensure device owner is set up by running: 7399 \nadb shell dpm set-device-owner --user 0 com.android.cts.verifier/.capturecontentfornotes.DeviceAdminTestReceiver 7400 \n2. Tap on the disable screenshot button shown below. 7401 \n3. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7402 \n4. Then tap on the Fire Intent Action button shown in the CtsDefaultNotesApp. 7403 \n5. Android SystemUI should not be shown, instead the CtsDefaultNotesApp should inform that 7404 screenshot blocked by admin. 7405 \n6. If so, pass this test else fail. 7406 \n7. Ensure to tap on enable screenshot button otherwise future tests would be impacted. 7407 </string> 7408 <string name="ccfn_call_can_use_api_true">Trigger can all API which returns true</string> 7409 <string name="ccfn_call_can_use_api_true_info"> 7410 1. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7411 \n2. Then tap on the Call Can Use API button. 7412 \n3. Verify the CtsDefaultNotesApp informs can use API returned true. 7413 \n4. If so, pass this test else fail. 7414 </string> 7415 <string name="ccfn_call_can_use_api_blocked_by_admin"> 7416 Trigger can call API but blocked by admin 7417 </string> 7418 <string name="ccfn_call_can_use_api_blocked_by_admin_info"> 7419 1. Ensure device owner is set up by running: 7420 \nadb shell dpm set-device-owner --user 0 com.android.cts.verifier/.capturecontentfornotes.DeviceAdminTestReceiver 7421 \n2. Tap on the disable screenshot button shown below. 7422 \n3. Open the CtsDefaultNotesApp using certain actions such as the stylus button click. 7423 \n4. Tap on the Call Can Use API button. 7424 \n5. Verify the CtsDefaultNotesApp informs can use API returned false. 7425 \n6. If so, pass this test else fail. 7426 \n7. Ensure to tap on enable screenshot button otherwise future tests would be impacted. 7427 </string> 7428 <string name="ccfn_call_can_use_api_window_unsupported"> 7429 Trigger can call API but window mode unsupported 7430 </string> 7431 <string name="ccfn_call_can_use_api_window_unsupported_info"> 7432 1. Open the CtsDefaultNotesApp using the app icon, this should launch the app in regular 7433 mode. 7434 \n2. Tap on the Call Can Use API button. 7435 \n3. Verify the CtsDefaultNotesApp informs can use API returned false. 7436 \n4. If so, pass this test else fail. 7437 </string> 7438 7439 <string name="notif_hiding_test">Notification Hiding Test</string> 7440 <string name="notif_hiding_shade_test">Notification Hiding In Notification Shade During Screen Recording Test</string> 7441 <string name="notif_hiding_app_test">Notification Triggers Hiding App Content During Screen Recording Test</string> 7442 <string name="notif_hiding_shade_partial_test">Notification Not Hiding In Notification Shade During Single-App Screen Recording Test</string> 7443 <string name="notif_hiding_launcher_test">Notification Hiding In Launcher During Screen Recording Test</string> 7444 <string name="notif_hiding_bubble_test">Notification Hiding In Bubbles During Screen Recording Test</string> 7445 <string name="notif_hiding_shade_local_screen_recorder_test">Notification Hiding In Notification Shade During Screen Recording From Local Screen Recorder Test</string> 7446 <string name="notif_hiding_app_local_screen_recorder_test">Notification Triggers Hiding App Content During Screen Recording From Local Screen Recorder Test</string> 7447 <string name="notif_hiding_shade_disable_protections_test">Notification Hiding In Notification Shade During Screen Recording With Protections Disabled Test</string> 7448 <string name="notif_hiding_app_disable_protections_test">Notification Triggers Hiding App Content During Screen Recording With Protections Disabled Test</string> 7449 <string name="notif_hiding_shade_test_instructions"> 7450 1. Press \"Start screen recording\", then select \"Entire screen\" in the resulting recording dialog, then select \"Start\". 7451 \n2. Open the notification shade, and verify there is a notification that includes the text \"FGS Running\". 7452 \n3. Press \"Send notification\". Verify the notification popup does not include the text \"Sensitive Text\". 7453 \n4. Open the notification shade, and verify there is no notification that includes the text \"Sensitive Text\". 7454 \n5. If there is no such notification, click \"Pass\", otherwise click \"Fail\". 7455 </string> 7456 <string name="notif_hiding_app_test_instructions"> 7457 1. Press \"Start screen recording\", then select \"Entire screen\" in the resulting recording dialog, then select \"Start\". 7458 \n2. Open the notification shade, and verify there is a notification that includes the text \"FGS Running\". 7459 \n3. Press \"Send notification\". Verify the notification popup does not include the text \"Sensitive Text\". 7460 \n4. Take a screenshot of CtsVerifier App, and verify the text \"Sensitive Text\" does not appear in the screenshot". 7461 \n5. If screenshot is blank, click \"Pass\", otherwise click \"Fail\". 7462 </string> 7463 <string name="notif_hiding_shade_partial_test_instructions"> 7464 1. Press \"Start screen recording\", then select \"A Single App\" in the resulting recording dialog, then select \"Start\", then pick \"Cts Verifier\" in the list of apps that shows. 7465 \n2. Press \"Send notification\". Verify the notification popup includes the text \"Sensitive Text\". 7466 \n3. Open the notification shade, and verify there is a notification that includes the text \"Sensitive Text\". 7467 \n4. If there is such a notification, click \"Pass\", otherwise click \"Fail\". 7468 </string> 7469 <string name="notif_hiding_launcher_test_instructions"> 7470 1. Press \"Start screen recording\", then select \"Entire screen\" in the resulting recording dialog, then select \"Start\". 7471 \n2. Press \"Send Notification\". 7472 \n3. Return to the home screen, open the app drawer, and drag \"CTS Verifier\" onto the launcher home screen. 7473 \n4. Long press \"CTS Verifier\" in the launcher. Verify that no message shows with the text \"Sensitive Text\". 7474 \n5. Return to the verifier app. If there was no such message when long pressing, click \"Pass\", otherwise click \"Fail\". 7475 </string> 7476 <string name="notif_hiding_bubble_test_instructions"> 7477 1. Press \"Send Notification\", then pull down the notification shade and press the bubble button on the bottom right of the notification. 7478 \n2. Exit the bubble activity by tapping on the bubble icon at the top of the screen 7479 \n3. Press \"Start screen recording\", then select \"Entire screen\" in the resulting recording dialog, then select \"Start\". 7480 \n4. Press \"Send Notification\", and verify that no message containing the text \"Sensitive Text\" shows next to the bubble. 7481 \n5. If no such message shows, click \"Pass\", otherwise click \"Fail\". 7482 </string> 7483 <string name="notif_hiding_shade_local_screen_recorder_test_instructions"> 7484 1. Start \"Screen record\", from Quick Settings then select \"Entire screen\" in the resulting recording dialog, then select \"Start\". 7485 \n2. Press \"Send notification\". Verify the notification popup includes the text \"Sensitive Text\". 7486 \n3. Open the notification shade, and verify there is a notification that includes the text \"Sensitive Text\". 7487 \n4. If there is such a notification, click \"Pass\", otherwise click \"Fail\". 7488 </string> 7489 <string name="notif_hiding_app_local_screen_recorder_test_instructions"> 7490 1. Start \"Screen record\", from Quick Settings then select \"Entire screen\" in the resulting recording dialog, then select \"Start\". 7491 \n2. Press \"Send notification\". Verify the notification popup includes the text \"Sensitive Text\". 7492 \n3. Take a screenshot of CtsVerifier App, and verify the text \"Sensitive Text\" appears in the screenshot". 7493 \n4. If screenshot is has content, click \"Pass\", otherwise (if blank) click \"Fail\". 7494 </string> 7495 <string name="notif_hiding_shade_disable_protections_test_instructions"> 7496 1. Go to the "Disable screen share protections" developer setting. It is often located under \"Developer options\". 7497 \nConfirm that: 7498 \n - "Disable screen share protections" is enabled. 7499 \nReturn back to this page. Remember to undo this after the test. 7500 \n2. Press \"Start screen recording\", then select \"Entire screen\" in the resulting recording dialog, then select \"Start\". 7501 \n3. Open the notification shade, and verify there is a notification that includes the text \"FGS Running\". 7502 \n2. Press \"Send notification\". Verify the notification popup includes the text \"Sensitive Text\". 7503 \n5. Open the notification shade, and verify there is a notification that includes the text \"Sensitive Text\". 7504 \n6. If there is such a notification, click \"Pass\", otherwise click \"Fail\". 7505 \n7. Remember to disable the "Disable screen share protections" developer options. 7506 </string> 7507 <string name="notif_hiding_app_disable_protections_test_instructions"> 7508 1. Go to the "Disable screen share protections" developer setting. It is often located under \"Developer options\". 7509 \nConfirm that: 7510 \n - "Disable screen share protections" is enabled. 7511 \nReturn back to this page. Remember to undo this after the test. 7512 \n2. Press \"Start screen recording\", then select \"Entire screen\" in the resulting recording dialog, then select \"Start\". 7513 \n3. Open the notification shade, and verify there is a notification that includes the text \"FGS Running\". 7514 \n2. Press \"Send notification\". Verify the notification popup includes the text \"Sensitive Text\". 7515 \n5. Take a screenshot of CtsVerifier App, and verify there is content in screenshot". 7516 \n6. If screenshot is has content, click \"Pass\", otherwise (if blank) click \"Fail\". 7517 \n7. Remember to disable the "Disable screen share protections" developer options. 7518 </string> 7519 <string name="notif_hiding_start_screen_recording">Start screen recording</string> 7520 <string name="notif_hiding_send_notification">Send notification</string> 7521 <string name="notif_hiding_success">No failures found, please press the green check mark</string> 7522 <string name="notif_hiding_failure">%1$d out of %2$d tests failed, please press the red \"!\"</string> 7523</resources> 7524