diff options
Diffstat (limited to 'en/compatibility')
| -rw-r--r-- | en/compatibility/cts/camera-hal.html | 102 | ||||
| -rw-r--r-- | en/compatibility/cts/camera-its-box.html | 65 | ||||
| -rw-r--r-- | en/compatibility/cts/development.html | 26 | ||||
| -rw-r--r-- | en/compatibility/cts/downloads.html | 3 | ||||
| -rw-r--r-- | en/compatibility/cts/interpret.html | 10 | ||||
| -rw-r--r-- | en/compatibility/cts/setup.html | 6 | ||||
| -rw-r--r-- | en/compatibility/cts/verifier.html | 29 |
7 files changed, 127 insertions, 114 deletions
diff --git a/en/compatibility/cts/camera-hal.html b/en/compatibility/cts/camera-hal.html index 1c63ab7b..0b42a34f 100644 --- a/en/compatibility/cts/camera-hal.html +++ b/en/compatibility/cts/camera-hal.html @@ -102,10 +102,10 @@ tests.</p> <p>To set up these tests:</p> -<pre> -$ cd hardware/libhardware/tests/camera*/ -$ mm -$ adb remount; adb sync +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">cd hardware/libhardware/tests/camera*/</code> +<code class="devsite-terminal">mm</code> +<code class="devsite-terminal">adb remount; adb sync</code> </pre> <h3 id=hal_3_x_tests>[ ] 3.1. HAL 3.x tests</h3> @@ -115,8 +115,8 @@ $ adb remount; adb sync <p>To run all tests:</p> -<pre> -$ adb shell /data/nativetest/camera3_test/camera3_test +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell /data/nativetest/camera3_test/camera3_test </pre> <p>You receive an <strong>OK</strong> for each passed test. Errors are logged @@ -129,24 +129,22 @@ at the end of output along with a summary of tests passed.</p> <p>To run all tests:</p> -<pre> -$ adb shell /data/nativetest/camera3_test/camera3_test +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell /data/nativetest/camera3_test/camera3_test </pre> <p>To run a single test, pass the <code>--gtest_filter</code> argument and the test name, like so:</p> -<pre> -$ adb shell /data/nativetest/camera2_test/camera2_test \ ---gtest_filter=Camera2Test.OpenClose +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell /data/nativetest/camera2_test/camera2_test --gtest_filter=Camera2Test.OpenClose </pre> <p>To run a subset of tests, use a wildcard with the <code>--gtest_filter</code> argument, like so:</p> -<pre> -$ adb shell /data/nativetest/camera2_test/camera2_test \ ---gtest_filter=Camera2Test.* +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell /data/nativetest/camera2_test/camera2_test --gtest_filter=Camera2Test.* </pre> <h3 id=3_tests_that_interact_with_the_camera_service>[ ] 3.3. Tests that @@ -213,11 +211,11 @@ to communicate.</p> instructions on how to set up and run the tests. For setup: <code>make cts</code></p> -<pre> -$ extract root/out/host/linux-x86/cts-verfier/android-cts-verifier.zip -$ cd android-cts-verifier -$ adb install -r CtsVerifier.apk -$ cd CameraITS +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">extract root/out/host/linux-x86/cts-verfier/android-cts-verifier.zip</code> +<code class="devsite-terminal">cd android-cts-verifier</code> +<code class="devsite-terminal">adb install -r CtsVerifier.apk</code> +<code class="devsite-terminal">cd CameraITS</code> </pre> <p>See <code>tutorial.py</code> in the <code>tests</code> subdirectory for a @@ -338,9 +336,9 @@ to install the resulting .apk. Example commands are included below.</p> <p>To set up these tests:</p> -<pre> -$ make mediaframeworktest -$ adb install out/target/product/<em><name></em>/data/app/mediaframeworktest.apk +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">make mediaframeworktest</code> +<code class="devsite-terminal">adb install out/target/product/<em><name></em>/data/app/mediaframeworktest.apk</code> </pre> <p>Where the <em><code><name></code></em> variable represents the directory @@ -348,7 +346,7 @@ containing the vendor's product.</p> <p>Find all of the tests in the following directory or its subdirectories:</p> -<pre> +<pre class="devsite-click-to-copy"> frameworks/base/media/tests/MediaFrameworkTest/src/com/android/mediaframeworktest </pre> @@ -367,13 +365,13 @@ frameworks/base/media/tests/MediaFrameworkTest/src/com/android/mediaframeworktes <p>To see all of the available tests::</p> -<pre> -$ adb shell pm list instrumentation +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell pm list instrumentation </pre> <p>This will yield results resembling:</p> -<pre> +<pre class="devsite-click-to-copy"> instrumentation:com.android.mediaframeworktest/.MediaFrameworkIntegrationTestRunner (target=com.android.mediaframeworktest) instrumentation:com.android.mediaframeworktest/.MediaRecorderStressTestRunner @@ -392,7 +390,7 @@ The component is composed of the target package name <p>For instance:</p> -<pre> +<pre class="devsite-click-to-copy"> com.android.mediaframeworktest/.MediaFrameworkIntegrationTestRunner com.android.mediaframeworktest/.MediaRecorderStressTestRunner com.android.mediaframeworktest/.MediaFrameworkPerfTestRunner @@ -401,15 +399,14 @@ com.android.mediaframeworktest/.MediaFrameworkPowerTestRunner <p>You may then pass each component to <code>adb shell am instrument</code> like so:</p> -<pre> -$ adb shell am instrument -w <component.name> +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell am instrument -w <component.name> </pre> <p>Where the <component.name> equals the extracted value above. For example:</p> -<pre> -$ adb shell am instrument -w \ -com.android.mediaframeworktest/.MediaFrameworkIntegrationTestRunner +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell am instrument -w com.android.mediaframeworktest/.MediaFrameworkIntegrationTestRunner </pre> <p>Please note, while the class path is the Java package + class name, the @@ -420,19 +417,15 @@ name, not the Java package in which the test runner class resides.</p> <p>To run a single class of tests, pass the -e class <test-class> argument, like so:</p> -<pre> -$ adb shell am instrument -e class \ -com.android.mediaframeworktest.integration.CameraBinderTest -w \ -com.android.mediaframeworktest/.MediaFrameworkIntegrationTestRunner +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell am instrument -e class com.android.mediaframeworktest.integration.CameraBinderTest -w com.android.mediaframeworktest/.MediaFrameworkIntegrationTestRunner </pre> <p>To run only a single method in a test class, append a pound (#) sign and the method name (in this case, <code>testConnectPro</code>) to the class name, like so:</p> -<pre> -$ adb shell am instrument -e class \ -'com.android.mediaframeworktest.integration.CameraBinderTest#testConnectPro' -w -\ com.android.mediaframeworktest/.MediaFrameworkIntegrationTestRunner +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell am instrument -e class 'com.android.mediaframeworktest.integration.CameraBinderTest#testConnectPro' -w com.android.mediaframeworktest/.MediaFrameworkIntegrationTestRunner </pre> <h3 id=media_settings_functional_tests>[ ] 7.2. Media settings functional tests</h3> @@ -442,10 +435,8 @@ functionality of different combinations of camera settings. (ie, Flash, exposure, WB, scene, picture size and geoTag)</p> <p>Run the test command:</p> -<pre> -$ adb shell am instrument -w -r -e delay_msec 15 -e log true -e class \ -com.android.mediaframeworktest.functional.camera.CameraPairwiseTest \ -com.android.mediaframeworktest/com.android.mediaframeworktest.CameraStressTestRunner +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell am instrument -w -r -e delay_msec 15 -e log true -e class com.android.mediaframeworktest.functional.camera.CameraPairwiseTest com.android.mediaframeworktest/com.android.mediaframeworktest.CameraStressTestRunner </pre> <h3 id=media_integration_tests>[ ] 7.3. Media integration tests</h3> @@ -454,13 +445,13 @@ com.android.mediaframeworktest/com.android.mediaframeworktest.CameraStressTestRu mediaframeworktest/integration/CameraBinderTest.java and mediaframeworktest/CameraStressTestRunner.java:</p> -<pre> -$ adb shell am instrument -e class \ 'com.android.mediaframeworktest.<strong>integration</strong>.<strong>CameraBinderTest'</strong> -w \ 'com.android.mediaframeworktest/.<strong>CameraStressTestRunner'</strong> +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell am instrument -e class \ 'com.android.mediaframeworktest.<strong>integration</strong>.<strong>CameraBinderTest'</strong> -w \ 'com.android.mediaframeworktest/.<strong>CameraStressTestRunner'</strong> </pre> <p>If successful, this results in output resembling:</p> -<pre> +<pre class="devsite-click-to-copy"> ----- com.android.mediaframeworktest.integration.CameraBinderTest:........... @@ -480,10 +471,8 @@ and it will compare the memory usage different after 200 iterations. Test will fail If the difference is greater than 150kM.</p> <p>Run the test command:</p> -<pre> -$ adb shell am instrument -w -r -e class \ -com.android.mediaframeworktest.performance.MediaPlayerPerformance#testCameraPreviewMemoryUsage -\ com.android.mediaframeworktest/.MediaFrameworkPerfTestRunner +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell am instrument -w -r -e class com.android.mediaframeworktest.performance.MediaPlayerPerformance#testCameraPreviewMemoryUsage com.android.mediaframeworktest/.MediaFrameworkPerfTestRunner </pre> <p>More detailed output can be found in: @@ -494,10 +483,8 @@ com.android.mediaframeworktest.performance.MediaPlayerPerformance#testCameraPrev <p>The commands to run unit tests are all similar. For example, for CameraMetadataTest.java, the command would be:</p> -<pre> -$ adb shell am instrument -e class \ -'com.android.mediaframeworktest.unit.CameraMetadataTest' -w \ -'com.android.mediaframeworktest/.CameraStressTestRunner' +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell am instrument -e class 'com.android.mediaframeworktest.unit.CameraMetadataTest' -w 'com.android.mediaframeworktest/.CameraStressTestRunner' </pre> <h3 id=media_stress_tests>[ ] 7.6. Media stress tests</h3> @@ -506,9 +493,8 @@ $ adb shell am instrument -e class \ <p>Run the test command:</p> -<pre> -$ adb shell am instrument -w -com.google.android.camera.tests/com.android.camera.stress.CameraStressTestRunner +<pre class="devsite-terminal devsite-click-to-copy"> +adb shell am instrument -w com.google.android.camera.tests/com.android.camera.stress.CameraStressTestRunner </pre> <p>All tests should pass.</p> diff --git a/en/compatibility/cts/camera-its-box.html b/en/compatibility/cts/camera-its-box.html index b88b0b72..ac997536 100644 --- a/en/compatibility/cts/camera-its-box.html +++ b/en/compatibility/cts/camera-its-box.html @@ -110,7 +110,9 @@ charts on the tablet screen. <li>Position the tablet face-up on a table (do not attach the tablet to the back panel of the box)</li> <li>Run the following command: -<pre>$ python tools/run_all_tests.py device=$device_id camera=0 chart=$chart_id scenes=2,3</pre> +<pre class="devsite-terminal devsite-click-to-copy"> +python tools/run_all_tests.py device=$device_id camera=0 chart=$chart_id scenes=2,3 +</pre> Scenes 2 and 3 require the tablet to display an image, so the tablet prompts you to "Allow Drive to access photos, media, and files on your device?". Clear this prompt (and prevent future prompts) by pressing <strong>Allow</strong>.</li> @@ -135,25 +137,31 @@ hardware and software:</p> <ul> <li>One (1) Pixel NOF26W for the back camera(0) testing, S/N: FA6BM0305016. To install the CTS Verifier app, unzip android-cts-verifier.zip then run -<pre>$ adb -s FA6BM0305016 install -r android-cts-verifier/CtsVerifier.apk</pre></li> +<pre class="devsite-terminal devsite-click-to-copy"> +adb -s FA6BM0305016 install -r android-cts-verifier/CtsVerifier.apk +</pre></li> <li>One (1) Pixel NOF26W for the front camera(1) testing, S/N: FA6BM0305439. To install the CTS Verifier app, unzip android-cts-verifier.zip then run -<pre>$ adb -s FA6BM0305439 install -r android-cts-verifier/CtsVerifier.apk</pre></li> +<pre class="devsite-terminal devsite-click-to-copy"> +adb -s FA6BM0305439 install -r android-cts-verifier/CtsVerifier.apk +</pre> +</li> </ul> </li></ul> <h3 id=scenes-0-4>Running scenes 0-4</h3> <p>To run scenes 0-4 on the front and back camera in parallel:</p> -<pre>$ cd android-cts-verifier/CameraITS -$ . build/envsetup.sh -$ python tools/run_parallel_tests.py device0=FA6BM0305016 device1=FA6BM0305439 chart=5811000011 +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">cd android-cts-verifier/CameraITS</code> +<code class="devsite-terminal">. build/envsetup.sh</code> +<code class="devsite-terminal">python tools/run_parallel_tests.py device0=FA6BM0305016 device1=FA6BM0305439 chart=5811000011</code> </pre> <p>Examples:</p> <table> <tr> -<td ><img src=images/camera_its_cam0.png align="center"></td> -<td align="center"><img src=images/camera_its_cam0.png></td> +<td ><img src=/compatibility/cts/images/camera_its_cam0.png align="center"></td> +<td align="center"><img src=/compatibility/cts/images/camera_its_cam0.png></td> </tr> <tr> <td align="center"><p class=caption><strong>Figure 1</strong>. Camera 0 S/N: @@ -169,9 +177,15 @@ FA6BM0305439</p> <p>You can retry scenes for both front and back cameras or a single camera: <ul> <li>To retry scenes on front and back cameras in parallel: -<pre>$ python tools/run_parallel_tests.py device0=FA6BM0305016 device1=FA6BM0305439 chart=5811000011 scenes=3,4</pre></li> +<pre class="devsite-terminal devsite-click-to-copy"> +python tools/run_parallel_tests.py device0=FA6BM0305016 device1=FA6BM0305439 chart=5811000011 scenes=3,4 +</pre> +</li> <li>To retry scenes on a single camera: -<pre>$ python tools/run_all_tests.py device=FA6BM0305016 chart=5811000011 camera=1 scenes=3,4</pre></li> +<pre class="devsite-terminal devsite-click-to-copy"> +python tools/run_all_tests.py device=FA6BM0305016 chart=5811000011 camera=1 scenes=3,4 +</pre> +</li> </ul> <h3 id=scenes-0-4>Running scene 5</h3> @@ -180,12 +194,15 @@ CameraITS.pdf in the CTS Verifier download). You can run Scene 5 separately (outside of the box) to test two devices in parallel.</p> <ul> <li>To run Scene 5 on front and back cameras on two devices in parallel: -<pre>$ python tools/run_parallel_tests.py device0=FA6BM0305016 device1=FA6BM0305439 chart=5811000011 scenes=5</pre> -<br><img src=images/camera_its_scene5.png width="50%"><br> +<pre class="devsite-terminal devsite-click-to-copy"> +python tools/run_parallel_tests.py device0=FA6BM0305016 device1=FA6BM0305439 chart=5811000011 scenes=5 +</pre> +<br><img src=/compatibility/cts/images/camera_its_scene5.png width="50%"><br> <strong>Figure 3</strong>. Camera scene 5.</li> <li>To run Scene 5 for front and back cameras on a single device: -<pre>$ python tools/run_all_tests.py device=FA6BM0305016 camera=0 scenes=5 -$ python tools/run_all_tests.py device=FA6BM0305016 camera=1 scenes=5 +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">python tools/run_all_tests.py device=FA6BM0305016 camera=0 scenes=5</code> +<code class="devsite-terminal">python tools/run_all_tests.py device=FA6BM0305016 camera=1 scenes=5</code> </pre></li> </ul> @@ -199,21 +216,27 @@ have finished, so to view results during test execution you must use Android Device Monitor or <code>adb logcat</code> to verify progress and/or view screenshots.<br> <br>Example adb command: -<pre>$ adb -s FA6BM0305016 logcat -v time</pre> +<pre class="devsite-terminal devsite-click-to-copy"> +adb -s FA6BM0305016 logcat -v time +</pre> Example screenshots command: -<pre>$ adb -s FA6BM0305016 shell screencap -p /sdcard/screencap.png -$ adb -s FA6BM0305016 pull /sdcard/screencap.png -$ display ./screencap.png +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">adb -s FA6BM0305016 shell screencap -p /sdcard/screencap.png</code> +<code class="devsite-terminal">adb -s FA6BM0305016 pull /sdcard/screencap.png</code> +<code class="devsite-terminal">display ./screencap.png</code> </pre></li> <li><strong>View results</strong>. To save Camera ITS results as a report: <ol> <li>Press <strong>Pass</strong> and save the report: -<br><img src=images/camera_its_results.png width="50%"><br> +<br><img src=/compatibility/cts/images/camera_its_results.png width="50%"><br> <strong>Figure 4</strong>. Camera ITS report.</li> <li>Pull reports from the device: -<pre>$ adb -s FA6BM0305016 pull /sdcard/verifierReports</pre></li> +<pre class="devsite-terminal devsite-click-to-copy"> +adb -s FA6BM0305016 pull /sdcard/verifierReports +</pre> +</li> <li>Unzip the report file and view the test_result.xml. -<br><img src=images/camera_its_reports.png><br> +<br><img src=/compatibility/cts/images/camera_its_reports.png><br> <strong>Figure 5</strong>. Camera ITS reports.<br></li> </ol> </li> diff --git a/en/compatibility/cts/development.html b/en/compatibility/cts/development.html index 6e44d27f..ae4c6e7e 100644 --- a/en/compatibility/cts/development.html +++ b/en/compatibility/cts/development.html @@ -37,14 +37,16 @@ CTS console:</p> <p class="note"><strong>Note:</strong> You may supply one of these other values for <code>TARGET_PRODUCT</code> to build for different architectures: <code>aosp_x86_64</code> or <code>aosp_mips</code></p> -<pre><code>cd <em>/path/to/android/root</em> -make cts -j32 TARGET_PRODUCT=aosp_arm64 -cts-tradefed +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">cd <em>/path/to/android/root</em></code> +<code class="devsite-terminal">make cts -j32 TARGET_PRODUCT=aosp_arm64</code> +<code class="devsite-terminal">cts-tradefed</code> </code></pre> <p>At the cts-tf console, enter e.g.:</p> -<pre><code>run cts --plan CTS -</code></pre> +<pre class="devsite-click-to-copy"> +tf> run cts --plan CTS +</pre> <h2 id="writing-cts-tests">Writing CTS tests</h2> @@ -106,7 +108,7 @@ For Android 6.0 and earlier, use CTS v1. For CTS v1, the sample code is at <p> The directory structure in CTS v1 tests looks like this: </p> -<pre class="no-pretty-print"> +<pre class="devsite-click-to-copy"> cts/ tests/ tests/ @@ -120,7 +122,7 @@ cts/ cts/ SampleDeviceTest.java </pre> -<h4 id="cts-v2"><strong>CTS v2</strong></h4> +<h4 id="cts-v2">CTS v2</h4> <p> For Android 7.0 and later, use CTS v2. For details, see <a href="https://android.googlesource.com/platform/cts/+/master/tests/sample/">the @@ -130,7 +132,7 @@ sample test in AOSP</a>. The CTS v2 directory structure looks like this: </p> -<pre class="no-pretty-print"> +<pre class="devsite-click-to-copy"> cts/ tests/ <em>module-name</em>/ @@ -169,7 +171,7 @@ to quick start your new test module with following steps: <ol> <li>Run this command to create the test directory and copy sample files to it: - <pre class="no-pretty-print">$ mkdir cts/tests/<i>module-name</i> && cp -r cts/tests/sample/* cts/tests/<i>module-name</i></pre> + <pre class="devsite-terminal devsite-click-to-copy">mkdir cts/tests/<i>module-name</i> && cp -r cts/tests/sample/* cts/tests/<i>module-name</i></pre> <li>Navigate to <code>cts/tests/<em>module-name</em></code> and substitute all instances of "[Ss]ample" following the recommended naming convention from above. <li>Update <code>SampleDeviceActivity</code> to exercise the feature you're testing. @@ -177,7 +179,7 @@ to quick start your new test module with following steps: errors.</li> </ol> -<h4><strong>Additional directories</strong></h4> +<h4>Additional directories</h4> <p> Other Android directories such as <code>assets</code>, <code>jni</code>, <code>libs</code> and <code>res</code> can also be added. To add JNI code, @@ -187,7 +189,7 @@ code and an <code>Android.mk</code> in it.</p> <p> The makefile typically contains the following settings: </p> -<pre> +<pre class="devsite-click-to-copy"> LOCAL_PATH := $(call my-dir) include $(CLEAR_VARS) LOCAL_MODULE := libCtsSample_jni @@ -210,7 +212,7 @@ include $(BUILD_SHARED_LIBRARY) need to be modified to build the native code and depend on it, as shown below:</p> -<pre> +<pre class="devsite-click-to-copy"> # All tests should include android.test.runner. LOCAL_JAVA_LIBRARIES := android.test.runner diff --git a/en/compatibility/cts/downloads.html b/en/compatibility/cts/downloads.html index 32186e70..c71ccb7d 100644 --- a/en/compatibility/cts/downloads.html +++ b/en/compatibility/cts/downloads.html @@ -180,7 +180,7 @@ Android 4.0.3 is found in the 'android-4.0.3_r1' branch in the open source tree. </ul> <h2 id="android-23">Android 2.3</h2> <p>Android 2.3 is the release of the development milestone code-named -Gingerbread. Source code for Android 2.3 is found in the 'gingerbread' branch in +Gingerbread. Source code for Android 2.3 is found in the 'gingerbread' branch in the open source tree.</p> <ul> <li><a href="https://dl.google.com/dl/android/cts/android-cts-2.3_r13-linux_x86-arm.zip">Android 2.3 R13 Compatibility Test Suite (CTS)</a></li> @@ -211,6 +211,7 @@ in the 'donut' branch in the open source tree.</p> <h2 id="cts-media-files">CTS Media Files</h2> <p>These media files are required for the CTS media stress tests.</p> <ul> +<li><a href="https://dl.google.com/dl/android/cts/android-cts-media-1.3.zip">CTS Media 1.3</a></li> <li><a href="https://dl.google.com/dl/android/cts/android-cts-media-1.2.zip">CTS Media 1.2</a></li> <li><a href="https://dl.google.com/dl/android/cts/android-cts-media-1.1.zip">CTS Media 1.1</a></li> <li><a href="https://dl.google.com/dl/android/cts/android-cts-media-1.0.zip">CTS Media 1.0</a></li> diff --git a/en/compatibility/cts/interpret.html b/en/compatibility/cts/interpret.html index 42ec9414..75ada597 100644 --- a/en/compatibility/cts/interpret.html +++ b/en/compatibility/cts/interpret.html @@ -24,7 +24,7 @@ <p>The CTS test results are placed in the file:</p> -<pre> +<pre class="devsite-click-to-copy"> $CTS_ROOT/android-cts/repository/results/<start_time>.zip </pre> @@ -73,14 +73,14 @@ could not be executed.</p> <section class="expandable"> <h4 class="showalways">Show CTS v1 sample test summary</h4> - <img src="images/cts-test-summary.png" alt="CTS v1 test summary" id="figure1a" /> + <img src="/compatibility/cts/images/cts-test-summary.png" alt="CTS v1 test summary" id="figure1a" /> <p class="img-caption"><strong>Figure 1a.</strong> CTS v1 sample test summary </p> </section> <section class="expandable"> <h4 class="showalways">Show CTS v2 sample test summary</h4> - <img src="images/cts-v2-test-summary.png" alt="CTS v2 test summary" id="figure1b" /> + <img src="/compatibility/cts/images/cts-v2-test-summary.png" alt="CTS v2 test summary" id="figure1b" /> <p class="img-caption"><strong>Figure 1b.</strong> CTS v2 sample test summary </p> </section> @@ -104,13 +104,13 @@ for the <em><StackTrace></em> tag).</p> <section class="expandable"> <h4 class="showalways">Show CTS v1 sample test report</h4> - <img src="images/cts-test-report.png" alt="CTS v1 test report" id="figure2a" /> + <img src="/compatibility/cts/images/cts-test-report.png" alt="CTS v1 test report" id="figure2a" /> <p class="img-caption"><strong>Figure 2a.</strong> CTS v1 sample test report</p> </section> <section class="expandable"> <h4 class="showalways">Show CTS v2 sample test report</h4> - <img src="images/cts-v2-test-report.png" alt="CTS v2 test report" id="figure2b" /> + <img src="/compatibility/cts/images/cts-v2-test-report.png" alt="CTS v2 test report" id="figure2b" /> <p class="img-caption"><strong>Figure 2b.</strong> CTS v2 sample test report</p> </section> diff --git a/en/compatibility/cts/setup.html b/en/compatibility/cts/setup.html index e22f2fdd..65bd8480 100644 --- a/en/compatibility/cts/setup.html +++ b/en/compatibility/cts/setup.html @@ -68,8 +68,8 @@ the Stand-alone SDK Tools</a>.</p> following command assumes you've opened the package archive in your home directory:</p> <hr> -<pre> -$ export PATH=$PATH:$HOME/android-sdk-linux/build-tools/<version> +<pre class="devsite-terminal devsite-click-to-copy"> +export PATH=$PATH:$HOME/android-sdk-linux/build-tools/<version> </pre> <p class="note"><strong>Note:</strong> Please ensure your starting path and @@ -132,7 +132,7 @@ property is the first API level the device was commercially launched with.</p> <p>OEMs can add <code>PRODUCT_PROPERTY_OVERRIDES</code> into their device.mk file to set this property, as shown in the following example: </p> -<pre> +<pre class="devsite-click-to-copy"> #ro.product.first_api_level indicates the first api level, device has been commercially launched on. PRODUCT_PROPERTY_OVERRIDES +=\ ro.product.first_api_level=21 diff --git a/en/compatibility/cts/verifier.html b/en/compatibility/cts/verifier.html index ace9475e..212b2bf0 100644 --- a/en/compatibility/cts/verifier.html +++ b/en/compatibility/cts/verifier.html @@ -43,8 +43,8 @@ SDK</a> on the Linux computer <li>Download the appropriate <a href="downloads.html">CTS Verifier.apk</a> for the version of Android under test. - <li>Install CTS Verifier.apk to the <em>Device Under Test</em> (DUT). <br> - <code>adb install -r -g CtsVerifier.apk</code> + <li>Install CTS Verifier.apk to the <em>Device Under Test</em> (DUT). + <pre class="devsite-terminal devsite-click-to-copy">adb install -r -g CtsVerifier.apk</pre> <li>Ensure that the device has its system data and time set correctly. </ul> <h2 id=cts_test_procedure>CTS Verifier test procedure</h2> @@ -52,7 +52,7 @@ version of Android under test. <li>After the CTS Verifier.apk has been installed, launch the CTS Verifier application: -<img src="images/cts-verifier-icon.png" alt="CTS Verifier icon in launcher" id="figure1" /> +<img src="/compatibility/cts/images/cts-verifier-icon.png" alt="CTS Verifier icon in launcher" id="figure1" /> <p class="img-caption"> <strong>Figure 1.</strong> CTS Verifier icon </p> @@ -60,7 +60,7 @@ version of Android under test. <li>Once opened, the CTS Verifier displays a list of all test sets available for manual verification: -<img src="images/cts-verifier-menu.png" alt="CTS Verifier menu of tests" id="figure2" /> +<img src="/compatibility/cts/images/cts-verifier-menu.png" alt="CTS Verifier menu of tests" id="figure2" /> <p class="img-caption"> <strong>Figure 2.</strong> CTS Verifier menu of tests </p> @@ -76,7 +76,7 @@ version of Android under test. press the <strong>Fail</strong> button (！). </ul> -<img src="images/video-verifier.png" alt="Streaming video quality verifier" id="figure3" /> +<img src="/compatibility/cts/images/video-verifier.png" alt="Streaming video quality verifier" id="figure3" /> <p class="img-caption"> <strong>Figure 3.</strong> Video quality verifier </p> @@ -91,17 +91,17 @@ version of Android under test. <li>Connect the DUT to a computer. <li>Execute the cts-usb-accessory program on the computer found in the CTS Verifier package. + <pre class="devsite-terminal devsite-click-to-copy">./cts-usb-accessory</pre> <li>A popup message will appear on the DUT. Select <strong>OK</strong> and go into the USB Accessory Test in the CTS Verifier application. <br> -<img src="images/screen-lock-test.png" alt="CTS Verifier screen lock test" id="figure4" /> +<img src="/compatibility/cts/images/screen-lock-test.png" alt="CTS Verifier screen lock test" id="figure4" /> <p class="img-caption"> <strong>Figure 4.</strong> Screen lock test </p> <li>Output similar to below will appear on the computer’s console. </ol> -<pre> -out/host/linux-x86/cts-verifier/android-cts-verifier$ <strong>./cts-usb-accessory</strong> +<pre class="devsite-click-to-copy"> CTS USB Accessory Tester Found possible Android device (413c:2106) - attempting to switch to accessory mode... @@ -138,7 +138,7 @@ href="/compatibility/calibration-pattern.pdf">calibration-pattern.pdf</a> target file and mount it on a rigid backing. Print on 11” x 17” or A3. Orient the camera device and the printed target as shown in the diagram below:</p> -<img src="images/camera-printed-target.png" alt="Camera printed target" id="figure5" /> +<img src="/compatibility/cts/images/camera-printed-target.png" alt="Camera printed target" id="figure5" /> <p class="img-caption"> <strong>Figure 5.</strong> Camera printed target </p> @@ -177,11 +177,11 @@ ensure that the optical axis is orthogonal to the target.</p> <li> After all tests are completed, tap the <strong>Save (disk)</strong> icon. <br> - <img src="images/verifier-save-icon.png" alt="CTS Verifier Save icon" id="figure6" /> + <img src="/compatibility/cts/images/verifier-save-icon.png" alt="CTS Verifier Save icon" id="figure6" /> <p class="img-caption"> <strong>Figure 6.</strong> CTS Verifier Save icon. <em>Note:</em> In Android 7.0 and later, the preview feature is removed: - <img src="images/verifier-preview-icon.png" width="24" height="24"> + <img src="/compatibility/cts/images/verifier-preview-icon.png" width="24" height="24"> </p> </li> <li> @@ -202,9 +202,10 @@ ensure that the optical axis is orthogonal to the target.</p> <code>adb pull CTSVerifierReportPath</code> to download the report from the device. <ul> <li> - To download all reports run: <code>adb pull /sdcard/verifierReports</code> - <br/> - For Android 6.0 and earlier, run: <code>adb pull /mnt/sdcard/ctsVerifierReports/</code> + To download all reports run: + <pre class="devsite-terminal devsite-click-to-copy">adb pull /sdcard/verifierReports</pre> + For Android 6.0 and earlier, run: + <pre class="devsite-terminal devsite-click-to-copy">adb pull /mnt/sdcard/ctsVerifierReports/</pre> </li> <li> The name of the reports are time-stamped based on the DUT’s system time. |