For instance, cameras that lack autofocus MUST still call any registered android. AutoFocusCallback instances even though this has no relevance to a non-autofocus camera. Device implementations MUST recognize and honor each parameter name defined as a constant on the android. Parameters class, if the underlying hardware supports the feature. If the device hardware does not support a feature, the API must behave as documented.
Device implementations MAY include a front-facing camera. That is, the camera API in Android 2. Camera or Camera. Parameters subclass is provided to support front-facing cameras, it MUST NOT be located in an existing namespace, as described by sections 3. Note that the inclusion of a front-facing camera does not meet the requirement that devices include a rear-facing camera.
That is, Android 2. The 92MB MUST be in addition to any memory dedicated to hardware components such as radio, memory, and so on that is not under the kernel's control.
Beyond the requirements above, device implementations SHOULD have at least MB of memory available to kernel and userspace, in addition to any memory dedicated to hardware components that is not under the kernel's control. Note that these higher requirements are planned to become hard minimums in a future version of Android.
Device implementations are strongly encouraged to meet these requirements now, or else they may not be eligible for compatibility for a future version of Android. Device implementations MUST offer shared storage for applications. Device implementations MUST be configured with shared storage mounted by default, "out of the box". Device implementations MUST enforce as documented the android. Shared storage MUST otherwise be writable by any application that obtains that permission.
Device implementations MAY have hardware for user-accessible removable storage, such as a Secure Digital card. Alternatively, device implementations MAY allocate internal non-removable storage as shared storage for apps. It is illustrative to consider two common examples. Device implementations that include multiple shared storage paths such as both an SD card slot and shared internal storage SHOULD modify the core applications such as the media scanner and ContentProvider to transparently support files placed in both locations.
However, since Bluetooth is a communications protocol between devices, it cannot be fully tested by unit tests running on a single device. One of the goals of the Android Compatibility Program is to enable consistent application experience to consumers. Compatible implementations must ensure not only that applications simply run correctly on the device, but that they do so with reasonable performance and overall good user experience.
Device implementations MUST implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs [ Resources, 29 ] in the Android developer documentation.
Specifically, compatible devices MUST support the security mechanisms described in the follow sub-sections. Specifically, implementations MUST enforce each permission defined as described in the SDK documentation; no permissions may be omitted, altered, or ignored.
Implementations MAY add additional permissions, provided the new permission ID strings are not in the android. Device implementations MUST support running multiple applications as the same Linux user ID, provided that the applications are properly signed and constructed, as defined in the Security and Permissions reference [ Resources, 29 ].
Device implementations MUST support the Android file access permissions model as defined in as defined in the Security and Permissions reference [ Resources, 29 ]. Device implementations MAY include runtime environments that execute applications using some other software or technology than the Dalvik virtual machine or native code.
However, such alternate execution environments MUST NOT compromise the Android security model or the security of installed Android applications, as described in this section. Alternate runtimes MUST themselves be Android applications, and abide by the standard Android security model, as described elsewhere in Section When installing applications, alternate runtimes MUST obtain user consent for the Android permissions used by the application.
That is, if an application needs to make use of a device resource for which there is a corresponding Android permission such as Camera, GPS, etc. If the runtime environment does not record application capabilities in this manner, the runtime environment MUST list all permissions held by the runtime itself when installing any application using that runtime. The CTS is designed to be run on an actual device.
Like any software, the CTS may itself contain bugs. Device implementations MUST include a mechanism to replace the entirety of the system software. The mechanism need not perform "live" upgrades -- that is, a device restart MAY be required. Any method can be used, provided that it can replace the entirety of the software preinstalled on the device. For instance, any of the following approaches will satisfy this requirement:.
The update mechanism used MUST support updates without wiping user data. Note that the upstream Android software includes an update mechanism that satisfies this requirement. If an error is found in a device implementation after it has been released but within its reasonable product lifetime that is determined in consultation with the Android Compatibility Team to affect the compatibility of thid-party applications, the device implementer MUST correct the error via a software update available that can be applied per the mechanism just described.
You can contact the document authors at compatibility android. Consequently, device implementations MUST also pass the human-driven Bluetooth test procedure described below. The test procedure is based on the BluetoothChat sample app included in the Android open-source project tree.
The procedure requires two devices:. The test procedure below refers to these devices as the "candidate" and "known good" devices, respectively. Note: the above tests have some cases which end a test section by using Home, and some using Back.
These tests are not redundant and are not optional: the objective is to verify that the Bluetooth API and stack works correctly both when Activities are explicitly terminated via the user pressing Back, which calls finish , and implicitly sent to background via the user pressing Home. Each test sequence MUST be performed as described. Introduction 2. Resources 3. Software 3. Managed API Compatibility 3.
Soft API Compatibility 3. Permissions 3. Build Parameters 3. Intent Compatibility 3. Core Application Intents 3. Intent Overrides 3. Intent Namespaces 3. Broadcast Intents. WebView Compatibility 3. Browser Compatibility. Widgets 3.
Notifications 3. Search 3. Toasts 3. Live Wallpapers. Media Codecs 6. Audio Recording 6. Audio Latency. Display 8. Non-Standard Display Configurations 8. Display Metrics 8. With Honeycomb acting as the bridge from old to new, Ice Cream Sandwich — also released in — served as the platform's official entry into the era of modern design. The release refined the visual concepts introduced with Honeycomb and reunited tablets and phones with a single, unified UI vision.
ICS dropped much of Honeycomb's "holographic" appearance but kept its use of blue as a system-wide highlight. And it carried over core system elements like on-screen buttons and a card-like appearance for app-switching. Android 4. And it started the slow process of bringing a standardized design framework — known as "Holo" — all throughout the OS and into Android's app ecosystem.
Spread across three impactful Android versions, and 's Jelly Bean releases took ICS's fresh foundation and made meaningful strides in fine-tuning and building upon it. The releases added plenty of poise and polish into the operating system and went a long way in making Android more inviting for the average user. Visuals aside, Jelly Bean brought about our first taste of Google Now — the spectacular predictive-intelligence utility that's sadly since devolved into a glorified news feed.
It gave us expandable and interactive notifications, an expanded voice search system, and a more advanced system for displaying search results in general, with a focus on card-based results that attempted to answer questions directly. Multiuser support also came into play, albeit on tablets only at this point, and an early version of Android's Quick Settings panel made its first appearance. Jelly Bean ushered in a heavily hyped system for placing widgets on your lock screen , too — one that, like so many Android features over the years , quietly disappeared a couple years later.
Late's KitKat release marked the end of Android's dark era, as the blacks of Gingerbread and the blues of Honeycomb finally made their way out of the operating system. Lighter backgrounds and more neutral highlights took their places, with a transparent status bar and white icons giving the OS a more contemporary appearance. The release was Google's first foray into claiming a full panel of the home screen for its services, too — at least, for users of its own Nexus phones and those who chose to download its first-ever standalone launcher.
Here are the latest Insider stories. More Insider Sign Out. Sign In Register. Sign Out Sign In Register. Latest Insider. Check out the latest Insider stories here. More from the IDG Network. The next release after Froyo, Android 2. The most popular software remains Android Lollipop with Android 5 taking up Android 6 Marshmallow is also popular with Last year's Android 7 Nougat release still only makes up 0.
James is Phones Editor for TechRadar, and he has covered smartphones for the best part of a decade bringing you news on all the big announcements from top manufacturers making mobile phones.
0コメント