The third developer preview was released on June 8, 2017 and offered a finalized version of the API.
[12] DP3 finalized the release's API to API level 26,
[12] changed the camera UI, reverted the Wi-Fi and cellular connectivity levels in the status bar back to Wi-Fi left, added themed notifications, added a battery animation in Settings: Battery, a new icon and darker background for the Clock app, and a teardrop icon shape for apps.
[13]
On July 24, 2017, a fourth developer preview was released which included the final system behaviors and the latest bug fixes and optimizations.
[14]
On August 18, 2017, Google launched an eclipse-themed teaser website, stating the release date and name unveiling of Android O as August 21, coinciding with the
solar eclipse in the US.
[15] The name ultimately turned out to be "
Oreo", as a partnership between Google and
Nabisco, the producers of the world-famous cookie.
[16] Factory images were made available for compatible
Nexus and
Pixel devices later that day.
[17]
Android Oreo adds support for Neighborhood Aware Networking (NAN) for
Wi-Fi based on
Wi-Fi Aware,
[31] wide
color gamuts in apps,
[32] an
API for
autofillers, multiprocess and
Google Safe Browsing support for WebViews, an API to allow system-level integration for
VoIP apps, and launching activities on remote displays.
[7] Android Runtime (ART) features performance improvements
[7] and better cache handling.
[33] Android Oreo contains additional limits on apps' background activities in order to improve battery life.
[34] Apps can specify "adaptive icons" for differently-shaped containers specified by themes, such as circles, squares, and
squircles.
[35]
Android Oreo supports new
emoji that were included in the
Unicode 10 standard. A new emoji font was also introduced, which notably redesigns its face figures to use a traditional circular shape, as opposed to the "blob" design that was introduced on
Android "KitKat".
[36][37]
The underlying architecture of Android was revised so that low-level, vendor-specific code for supporting a device's hardware is separated from the Android OS framework using a
hardware abstraction layer known as the "vendor interface". Vendor interfaces must be made
forward compatible with future versions of Android; theoretically, OEMs would only need to perform their necessary modifications to the OS framework and bundled apps to update a device to a future version of Android, while maintaining the same vendor interface.
[38]The "seamless updates" concept introduced in Android 7.0 is updated to download update files directly to the system partition, rather than requiring them to be downloaded to the user partition first, thus reducing storage space requirements for system updates.
[39]
Android Oreo introduces a new automatic repair system known as "Rescue Party"; if the operating system detects that core system components are persistently crashing during startup, it will automatically perform a series of escalating repair steps. If all automatic repair steps are exhausted, the device will reboot into recovery mode and offer to perform a factory reset.
[40][41]
A tailored distribution for low-end devices known as Android Go is also being made available, which will be used on all devices with 1 GB of RAM or less. These devices will ship with platform optimizations designed to reduce mobile data usage (including enabling Data Saver mode by default), and a special suite of
Google Mobile Services designed to be less resource- and bandwidth-intensive.
Google Play Store will also highlight lightweight apps suited for these devices.
[42][43]
No comments:
Post a Comment
Note: only a member of this blog may post a comment.