Device implementers MUST test implementation compatibility using the following
open-source applications:
- Calculator (included in SDK)
- Lunar Lander (included in SDK)
- The "Apps for Android" applications.
Each app above MUST launch and behave correctly on the implementation, for the implementation to be considered compatible. Additionally, device implementations MUST test each menu item (including all sub-menus) of each of these smoke-test applications:
- ApiDemos (included in SDK)
- ManualSmokeTests (included in CTS)
Each test case in the applications above MUST run correctly on the device implementation.
Android Application Packaging Compatibility
Device implementations MUST install and run Android ".apk" files as generated by the "aapt" tool included in the official Android SDK. Devices implementations MUST NOT extend either the .apk, Android Manifest, or Dalvik bytecode formats in such a way that would prevent those files from installing and running correctly on other compatible devices. Device implementers SHOULD use the reference upstream implementation of Dalvik, and the reference implementation's package management system.
Device implemenations MUST support the following multimedia codecs. All of these codecs are provided as software implementations in the preferred Android implementation from the Android Open Source Project.
Please note that neither Google nor the Open Handset Alliance make any representation that these codecs are unencumbered by third-party patents. Those intending to use this source code in hardware or software products are advised that implementations of this code, including in open source software or shareware, may
require patent licenses from the relevant patent holders.
Note that the table above does not list specific bitrate requirements for most video codecs. The reason for this is that in practice, current device hardware does not necessarily support bitrates that map exactly to the required bitrates specified by the relevant standards. Instead, device implementations SHOULD support the
highest bitrate practical on the hardware, up to the limits defined by the specifications.
- Android Debug Bridge (known as adb) Device implementations MUST support all adb functions as documented in the Android SDK. The device-side adb daemon SHOULD be inactive by default, but
there MUST be a user-accessible mechanism to turn on the Android Debug Bridge.
- Dalvik Debug Monitor Service (known as ddms) Device implementations MUST support all ddms features as documented in the Android SDK. As ddms uses adb, support for ddms SHOULD be inactive by default, but MUST be supported whenever the user has activated the Android Debug Bridge,
as above.
- Monkey Device implementations MUST include the Monkey framework, and make it available for applications to use.
0 comments:
Post a Comment