Compatibility Test Suite
(CTS)
User Manual
Open Handset Alliance
revision 8
1
Contents
1. Why build compatible Android devices?
2. How can I become compatible?
2.1. Comply with Android Compatibility Definition document
2.2. Pass the Compatibility Test Suite (CTS)
3. Running the automated CTS
3.1. Setting up your host machine
3.2. Storage requirements
3.3. Setting up your device
3.4. Copying media files to the device
3.5. Using the CTS
3.6. Selecting CTS plans
4. Interpreting the test results
5. CTS Verifier instructions
5.1. Test Preparation
5.1.1. Hardware requirements
5.1.2. Setup
5.2. CTS test procedure
5.3. Specific test requirements
5.3.1. USB Accessory
5.3.2. Camera field of view calibration
5.4. Exporting test reports
6. Release notes
7. Appendix: CTS Console command reference
2
1. Why build compatible Android devices?
Users want a customizable device.
A mobile phone is a highly personal, always-on, always-present gateway to the
Internet. We haven't met a user yet who didn't want to customize it by extending its
functionality. That's why Android was designed as a robust platform for running
after-market applications.
Developers outnumber us all.
No device manufacturer can hope to write all the software that a person could
conceivably need. We need third-party developers to write the apps users want, so the
Android Open Source Project aims to make it as easy and open as possible for
developers to build apps.
Everyone needs a common ecosystem.
Every line of code developers write to work around a particular phone's bug is a line of
code that didn't add a new feature. The more compatible phones there are, the more
apps there will be. By building a fully compatible Android device, you benefit from the
huge pool of apps written for Android, while increasing the incentive for developers to
build more of those apps.
Android compatibility is free, and it's easy.
See the Android Compatibility program introduction for more information:
3
http://source.android.com/compatibility/index.html
2. How can I become compatible?
2.1. Comply with Android Compatibility Definition document
To start, read the Android Compatibility overview, which describes the goals and
components of the program:
http://source.android.com/compatibility/overview.html
Then review the Android Compatibility Definition Document (CDD) for the
requirements of and policies associated with compatible devices:
http://source.android.com/compatibility/android-cdd.pdf
The CDD's role is to codify and clarify specific requirements, and eliminate ambiguity.
The CDD does not attempt to be comprehensive. Since Android is a single corpus of
open-source code, the code itself is the comprehensive "specification" of the
platform and its APIs.
2.2. Pass the Compatibility Test Suite (CTS)
The Android Compatibility Test Suite (CTS) is a downloadable open-source testing
harness you can use as you develop your handset; for example, you could use the CTS
to do continuous self-testing during your development work.
For more about the CTS and the compatibility report that it generates, see the
Compatibility Test Suite introduction:
http://source.android.com/compatibility/cts-intro.html
For the latest instructions on using the CTS, visit the following link:
http://source.android.com/compatibility/android-cts-manual.pdf
3. Running the automated CTS
4
3.1. Setting up your host machine
Note: the steps to configure and run CTS have changed in the 4.0 release.
Before running CTS, make sure you have a recent version of Android Debug Bridge
(adb) installed and the 'adb' location added to the system path of your machine.
To install adb, download Android SDK tools , and set up an existing IDE:
http://developer.android.com/sdk/index.html#ExistingIDE
http://developer.android.com/sdk/installing/index.html
Ensure 'adb' is in your system path:
export
PATH=$PATH:/home/myuser/androidsdklinux_x86/platformtoo
ls
3.2. Storage requirements
The CTS media stress tests require video clips to be on external storage (/sdcard).
Most of the clips are from Big Buck Bunny which is copyrighted by the Blender
Foundation ( http://www.bigbuckbunny.org) under the Creative Commons Attribution
3.0 license:
http://creativecommons.org/licenses/by/3.0/
The required space depends on the maximum video playback resolution supported by
the device. By default, 176x144 and 480x360 SHOULD be supported. Note that the
video playback capabilities of the device under test will be checked via the
android.media.CamcorderProfile APIs.
Here are the storage requirements by maximum video playback resolution:
● 480x360: 91.4MB
● 720x480: 151.9MB
● 1280x720: 401.6MB
● 1920x1080: 1008.2MB
5
评论0
最新资源