Google Android Compatibility Definition: Android 1.6 Manual do Utilizador

Android Compatibility Definition: Android 1.6Android 1.6 r2Google [email protected]

◦ The "<device name>" string MUST be the same as the value forandroid.os.Build.MODEL◦ The "<build ID>" string MUST be

• Device implementers MAY modify the underlying implementation of the APIs, but suchmodifications MUST NOT impact the stated behavior and Java-languag

3.8.2. NotificationsAndroid includes APIs that allow developers to notify users of notable events [Resources, 15]. Deviceimplementers MUST provide sup

considered compatible.5. Application Packaging CompatibilityDevice implementations MUST install and run Android ".apk" files as generated by

Support for ringtone formatsRTTTL/RTX, OTA, and iMelodyand iMelody (.imy)Ogg VorbisX.oggPCM X8- and 16-bit linear PCM (rates upto limit of hardware)WA

• Monkey [Resources, 23]Device implementations MUST include the Monkey framework, and make it available forapplications to use.8. Hardware Compatibili

• Device implementations MUST interpret any resources that are present as defaulting to"medium" (known as "mdpi" in the SDK docume

8.4. Screen OrientationCompatible devices MUST support dynamic orientation by applications to either portrait or landscapescreen orientation. That is,

8.9. CameraDevice implementations MUST include a camera. The included camera:• MUST have a resolution of at least 2 megapixels• SHOULD have either har

8.11. CompassDevice implementations MUST include a 3-axis compass and MUST be able to deliver events at at least10 Hz. The coordinate system used by t

Table of Contents1. Introduction ... 4

ApplicationLaunch TimeThe following applicationsshould launch within thespecified time.Browser: less than 1300msMMS/SMS: less than 700msAlarmClock: le

10.3. Filesystem PermissionsDevice implementations MUST support the Android file access permissions model as defined in asdefined in the Security and

Appendix A: Required Application IntentsNOTE: this list is provisional, and will be updated in the future.Application Actions Schemes MIME TypesBrowse

android.intent.action.PICKvnd.android.cursor.dir/personvnd.android.cursor.dir/phonevnd.android.cursor.dir/postal-addressandroid.intent.action.GET_CONT

PackageInstallerandroid.intent.action.VIEWcontentfilepackageandroid.intent.action.PACKAGE_INSTALLfilehttphttpsandroid.intent.action.ALL_APPSSettingsan

shown when prompting user aboutcreating a new contact.EXTRA_FORCE_CREATEUsedwith SHOW_OR_CREATE_CONTACT toforce creating a new contact if nomatching c

Appendix B: Required Broadcast IntentsNOTE: this list is provisional, and will beupdated in the future.Intent Action DescriptionACTION_BOOT_COMPLETEDB

ACTION_MEDIA_SCANNER_STARTEDBroadcast Action: The media scanner has startedscanning a directory.ACTION_MEDIA_SHAREDBroadcast Action: External media is

ACTION_UMS_DISCONNECTEDBroadcast Action: The device has exited USBMass Storage mode.ACTION_USER_PRESENTBroadcast Action: Sent when the user is present

12. Contact Us ... 21Appendix A: Require

Appendix C: Future Considerations This appendix clarifies certain portions of this Android1.6 Compatibility Definition, and in some cases discusses an

6. PerformanceFuture versions of CTS will also measure the CPU utilization and performance of the followingcomponents of an implementation:• 2D graphi

1. IntroductionThis document enumerates the requirements that must be met in order for mobile phones to becompatible with Android 1.6. This definition

13. Dalvik Virtual Machine specification, found in the dalvik/docs directory of a source codecheckout; also available at http://android.git.kernel.org

Device implementations MUST NOT omit any managed APIs, alter API interfaces or signatures, deviatefrom the documented behavior, or include no-ops, exc

and/or carrier who sold the device. There are no requirements on thespecific format of this field, except that it MUST NOT be null or the emptystring

3.2.3. Intent CompatibilityAndroid uses Intents to achieve loosely-coupled integration between applications. This section describesrequirements relate

3.2.3.4. Broadcast IntentsThird-party applications rely on the platform to broadcast certain Intents to notify them of changes in thehardware or softw