Device implementations MUST comply with all the requirements in this section. The managed Dalvik-based execution environment is the primary vehicle for Android applications. The Android application programming interface API is the set of Android platform interfaces exposed to applications running in the managed VM environment.
In addition to the managed APIs from Section 3. This section details the "soft" APIs and system behaviors required for compatibility with Android 2. Device implementations MUST meet all the requirements presented in this section.
Device implementers MUST support and enforce all permission constants as documented by the Permission reference page [ Resources, 5 ].
Note that Section 10 lists additional requirements related to the Android security model. The Android APIs include a number of constants on the android. Build class [ Resources, 6 ] that are intended to describe the current device. To provide consistent, meaningful values across device implementations, the table below includes additional restrictions on the formats of these values to which device implementations MUST conform.
Android uses Intents to achieve loosely-coupled integration between applications. This section describes requirements related to the Intent patterns that MUST be honored by device implementations. By "honored", it is meant that the device implementer MUST provide an Android Activity or Service that specifies a matching Intent filter and binds to and implements correct behavior for each specified Intent pattern.
The Android upstream project defines a number of core applications, such as a phone dialer, calendar, contacts book, music player, and so on. Device implementers MAY replace these applications with alternative versions. However, any such alternative versions MUST honor the same Intent patterns provided by the upstream project. For example, if a device contains an alternative music player, it must still honor the Intent pattern issued by third-party applications to pick a song.
The core Android system applications include various Activity, or Service components that are considered "public". That is, the attribute "android:exported" may be absent, or may have the value "true". For every Activity or Service defined in one of the core Android system apps that is not marked as non-public via an android:exported attribute with the value "false", device implementations MUST include a compontent of the same type implementing the same Intent filter patterns as the core Android system app.
In other words, a device implementation MAY replace core Android system apps; however, if it does, the device implementation MUST support all Intent patterns defined by each core Android system app being replaced. The upstream Android open source project allows this by default; device implementers MUST NOT attach special privileges to system applications' use of these Intent patterns, or prevent third-party applications from binding to and assuming control of these patterns. This prohibition specifically includes but is not limited to disabling the "Chooser" user interface which allows the user to select between multiple applications which all handle the same Intent pattern.
Third-party applications rely on the platform to broadcast certain Intents to notify them of changes in the hardware or software environment. Android-compatible devices MUST broadcast the public broadcast Intents in response to appropriate system events. Broadcast Intents are described in the SDK documentation. Managed code running in Dalvik can call into native code provided in the application. These libraries MUST be source-compatible i. If device implementers use a different implementation of these libraries, they MUST ensure header, binary, and behavioral compatibility.
Native code compatibility is challenging. For this reason, it should be repeated that device implementers are VERY strongly encouraged to use the upstream implementations of the libraries listed above to help ensure compatibility. Many developers and applications rely on the behavior of the android. WebView class [ Resources, 8 ] for their user interfaces, so the WebView implementation must be compatible across Android implementations.
Similarly, a full web experience is central to the Android user experience. Device implementations MUST include a version of android. Because it is not feasible to develop a comprehensive test suite for a web rendering system, device implementers MUST use the specific upstream build of WebKit in the WebView implementation. However, even if an alternate Browser application is shipped, the android. The behaviors of each of the API types managed, soft, native, and web must be consistent with the preferred implementation of the upstream Android open-source project [ Resources, 3 ].
Some specific areas of compatibility are:. The above list is not comprehensive, and the onus is on device implementers to ensure behavioral compatibility. The Compatibility Test Suite CTS tests significant portions of the platform for behavioral compatibility, but not all. It is the responsibility of the implementer to ensure behavioral compatibility with the Android Open Source Project.
Android follows the package and class namespace conventions defined by the Java programming language. To ensure compatibility with third-party applications, device implementers MUST NOT make any prohibited modifications see below to these package namespaces:.
A "publicly exposed element" is any construct which is not decorated with the " hide" marker in the upstream Android source code. Note that the restrictions above correspond to standard conventions for naming APIs in the Java programming language; this section simply aims to reinforce those conventions and make them binding through inclusion in this compatibility definition. Device implementations with screens classified as medium- or low-density MUST configure Dalvik to allocate at least 16MB of memory to each application.
Device implementations with screens classified as high-density MUST configure Dalvik to allocate at least 24MB of memory to each application. Note that device implementations MAY allocate more memory than these figures. The Android platform includes some developer APIs that allow developers to hook into the system user interface.
Android defines a component type and corresponding API and lifecycle that allows applications to expose an "AppWidget" to the end user [ Resources, 11 ]. The Android Open Source reference release includes a Launcher application that includes user interface elements allowing the user to add, view, and remove AppWidgets from the home screen.
Device implementers MAY substitute an alternative to the reference Launcher i. Alternative Launchers MAY omit these user interface elements; however, if they are omitted, the device implementer MUST provide a separate application accessible from the Launcher that allows users to add, configure, view, and remove AppWidgets. Android includes APIs that allow developers to notify users of notable events [ Resources, 12 ].
Device implementers MUST provide support for each class of notification so defined; specifically: sounds, vibration, light and status bar. Additionally, the implementation MUST correctly render all resources icons, sound files, etc.
Device implementers MAY provide an alternative user experience for notifications than that provided by the reference Android Open Source implementation; however, such alternative notification systems MUST support existing notification resources, as above. Android includes APIs [ Resources, 15 ] that allow developers to incorporate search into their applications, and expose their application's data into the global system search.
More from the IDG Network. What's in the latest Chrome update? Faster phishing site warnings, more Actions. Windows 10 Insider Previews: A guide to the builds. Google's 15 funniest flip-flops with Android, Chrome OS, and beyond. Android's underappreciated upgrade advantage. Android Versions Android versions: A living history from Show More.
What a long, strange trip it's been. Android versions 1. T-Mobile The Android 1. Android version 1. Android Versions. Currently reading. Android versions: A living history from 1.
Android Pie: 30 advanced tips and tricks. The idea was that Honeycomb would offer features that could not be handled by the smaller displays found on smartphones at the time. Even though Honeycomb was available, some tablets were still released with the smartphone-based Android 2.
In the end, Honeycomb ended up being a version of Android that did not see wide adoption. Google decided to integrate most of its features in its next major 4.
Released in October , the Ice Cream Sandwich version of Android brought a number of new features. It combined many of the options of the tablet-only Honeycomb version with the smartphone-oriented Gingerbread. That kind of biometric sign-in support has evolved and improved considerably since. Other notable changes with ICS included support for all on-screen buttons, swipe gestures to dismiss notifications and browser tabs, and the ability to monitor your data usage over mobile and Wi-Fi.
Google quickly released versions 4. Android 4. Instead, he decided to do something different. He contacted Nestle, the creators of the KitKat bar, and asked them if they could use the name for Android 4. Nestle agreed and KitKat became the name of the next Android version.
This allowed phone makers to use the latest version of Android on much cheaper handsets. First launched in the fall of , Android 5. It made liberal use of lighting and shadow effects, among other things, to simulate a paper-like look for the Android user interface.
The UI also got some other upgrades, including a revamped navigation bar, rich notifications for the lock screen, and much more. The subsequent Android 5. This included official support for dual-SIM, HD Voice calls, and Device Protection to keep thieves locked out of your phone even after a factory reset.
Released in the fall of , Android 6. It included features such as a new vertically scrolling app drawer, along with Google Now on Tap, native support for fingerprint biometric unlocking, USB Type-C support, the introduction of Android Pay now Google Pay , and much more. Version 7. Google made a number of big changes behind the scenes too. Google also used the release to make a bold push into the premium smartphone market. In March , Google officially announced and released the first developer preview for Android O, also known as Android 8.
Before that release, Hiroshi Lockheimer, the senior vice president of Android at Google, posted a GIF of an Oreo cake on Twitter — the first solid hint that Oreo, the popular cookie, would indeed be the official codename for Android 8.
In August, Google confirmed the cookie-inspired public name for Android 8. It was the second time in which the company chose a trademarked name for Android Oreo is owned by Nabisco. In a break from its tradition, Google showed off the Android Oreo mascot statue for the first time in a press event in New York City, rather than at its Googleplex headquarters.
The statue depicts the Android mascot as a flying superhero, complete with a cape. As far as features go, Android Oreo packed in lots of visual changes to the Settings menu, along with native support for picture-in-picture mode, notification channels, new autofill APIs for better management of passwords and fill data, and much more.
Google launched the first developer preview of the next major Android update, Android 9. On August 6, , the company officially launched the final version of Android 9. Android 9. One of them ditched the traditional navigation buttons in favor of one elongated button in the center, which became the new home button. Swiping up from it brings up Overview, with your most recently used apps, a search bar, and five app suggestions on the bottom.
Nougat offered support for Vulkan API for better graphics rendering along with a new app notification format. Android 8. Oreo was the first Android version to support Bluetooth 5.
Android 9 Pie got official on August 6, , with API 28 and it offered a refreshed material design with a new style of navigation buttons. Till today, a lot of smartphones are still based on Android 9 Pie.
Android 10 was released on September 3, , based on API This version was known as Android Q at the time of development and this is the first modern Android OS that doesn't have a dessert code name. It offered a complete full-screen user-interface with a redesigned navigation system, which is a bit similar to the modern iPhones. Android 11 was released on September 8, , and this version was based on API It comes with features like conversation notifications and this is also the first official Android version to offer a built-in screen recorder.
For Quick Alerts. Subscribe Now. India - 34,, World - ,, For Daily Alerts. Must Watch. Android Versions List and Names Features. By Vivek. Most Read Articles. Check Out Easy Fixes.
0コメント