![]() \nThe Virtual MIDI test does not require any MIDI interface hardware. + \nFor the USB Bluetooth test it is required that you connect a Yamaha MD-BT01 to the + correct MIDI plugs on the USB peripheral, the BT01 output jack to the USB interface + input jack and BT01 input plug to the USB interface output jack. \nFor the USB Bluetooth test it is required that you connect a Yamaha MT-BT301 to the - correct MIDI plugs on the USB peripheral, the BT301 output jack to the USB interface - input jack and BT301 input plug to the USB interface output jack. The cable must be connected to the MIDI input and output plugs on the peripheral. 4457,9 +4513,9 Peripheral device with standard MIDI 5-pin, DIN (round) connectors and a standard MIDI cable. + + Overlay View Dummy Text Example of input app specific custom rating. + + + Connect a 1080p display and press the "%s" button, below. + + No Display + 1080p Display + 2160p Display + Start Test + + Connect a 2160p display and press the "%s" button, below. ![]() Wait at least %3$d + seconds and then reconnect the display. + + + Press the "%1$s" button and disconnect the display within %2$d seconds. ![]() + + + + Display Modes Test + This test checks if Display.getSupportedModes() + and Display.getMode() are correctly reporting the supported screen modes. Wait at least %3$d seconds and then + reconnect the display. + + Press the "%1$s" button + and disconnect the display within %2$d seconds. + + Connect an HDR display and press + the "%s" button, below. + + Connect a non-HDR display and then + press the "%s" button, below. + + Start Test + + + HDR Capabilities Test + This test checks if + Display.getHdrCapabilities correctly reports the HDR capabilities of the display. + + This is a CtsVerifier test message! + Start Tee Test + Start Strongbox Test + Bluetooth Test -4330,6 +4347,45 No input devices found. This is okay because this + is an optional feature. ![]() + + Android Protected Confirmation not supported + + Android Protected Confirmation is not implemented by this device. It also assures that + Keymaster signs a message with a confirmation key only if the message was previously + confirmed by the user. + + Android Protected Confirmation Test + + This test ensures that - if Android Protected Confirmation is supported by the device under + test - the user is able to see the confirmation message and confirm it. +++ -217,6 +217,23 unusable without an authentication. a/apps/CtsVerifier/res/values/strings.xml +++ -50,4 +50,12 android:visibility="gone" /> + + diff -git a/apps/CtsVerifier/res/values/strings.xml b/apps/CtsVerifier/res/values/strings.xml a/apps/CtsVerifier/res/layout/tv_item.xml +++ -229,7 +229,7 - + diff -git a/apps/CtsVerifier/res/layout/sec_protected_confirmation_main.xml b/apps/CtsVerifier/res/layout/sec_protected_confirmation_main.xml a/apps/CtsVerifier/assets/report/compatibility_result.xsl +++ -57,6 +57,7 += LOCAL_JAVA_LIBRARIES += LOCAL_JAVA_LIBRARIES += voip-common +LOCAL_JAVA_LIBRARIES += truth-prebuilt LOCAL_PACKAGE_NAME := CtsVerifier LOCAL_PRIVATE_PLATFORM_APIS := true diff -git a/apps/CtsVerifier/AndroidManifest.xml b/apps/CtsVerifier/AndroidManifest.xml Merge "CTS secondary_user: CtsVoiceInteractionService" diff -git a/apps/CtsVerifier/Android.mk b/apps/CtsVerifier/Android.mk
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |