As Google took the date to release the first developer preview of its next Android OS version 8.0 factory image files to developers with compatible Nexus and Pixel devices. Those eligible members on Android Beta Program can easily download Android 8.0 O Developer Preview 1 for Nexus 6P, Nexus 5X, Pixel, Pixel XL, Pixel C and the Nexus Player devices. Before yu go grab it and flash Android O DP1 on your devices, you will need to have a clear view on what are the new features you will be receiving and bring the latest version onto your Android devices. Here are the seven features in Android O that you’ll actually care about, detailed below.
What’s new in Android O-MG?
Everything you need to know is placed with an ease. Although the latest and greatest version of Androd OS brings several changes to existing features as well as all new additions. I don;t want to waste time anymore, the mobile space is always evolving and Android has evolved along with it so it could meet the needs of people like us who use it every day.
With the first Android O developer preview released, we get a glimpse of some of the new features, also Google details, we can expect when it’s released later this year. Google also tells us that this is just a few of the things we can expect more with the next version of Android 8.0.
Here are those 7 high points in Android O Developer Preview 1 to consider the best, of course for now:
1. Background Limits
Starting with Android 7.0 Nougat, Android can restrict certain activities an application wants to do while it’s in the background. With Android O builds in early stage places top priority on saving power and improving battery life without the user having to do anything or install anything. The new found inside Android O developer preview 1 is the Background Limits: Additional automatic limits will be put on apps running in the background.
Better battery life and performance
Particularly in terms of background services and location updates. New limits on implicit broadcasts (sending “signals” for other apps or activities to act upon) background services (activities of an app that continue to run when it’s not on the screen) and location updates (checking to see where you are using Android’s location services), all are automatic now, meaning that it’s easier to build apps that don’t have an impact on battery life and the user don’t even have to manage anything. These changes made available will let developers create apps that have less impact on performance and battery and making things better.
With Android O, users will be able to manage notification channels, simply choose which kinds of notifications come from each app, rather than controlling all notifications for that app the same way. This same feature on Android N brought a new framework for notifications and ways to developers to use it so we get more information in a space where real estate is at a premium.
Now, Google is introducing new Notification Channels: grouping notifications together by their type. How granular the controls are will be defined by the app developer. There are also new visual changes to grouping of similar notifications that make “easier for users to see what’s going on” when receiving messages or glancing at the shade. Notifications on Android O are still managed by the app that delivers them, but users can control how things are displayed on a per-channel basis. This simply way can decide things like how a news app notifies us or a music player shows a persistent notification. Notification channels is a new way for us to control the rich notifications that Android apps bring to us.
3. High-Quality Bluetooth Audio
Thanks to a partnership with Sony, Google si somewhat be integrating new Bluetooth technologies into Android O, which allow for high-quality wireless music. Given the fact that the current trend of axing headphone jacks, anything that makes Bluetooth music sync better is good news, and Sony’s tech is something of the best in this business.
The major big deal is LDAC support. LDAC is a proprietary Sony encoding system that promises better, higher bitrate music transmission over a regular Bluetooth connection. Indeed, it does require hardware that supports LDAC, that actually means Sony headphons and speakers at this point. But with free integration into Android, there’s a good chance that we’ll start seeing more LDAC headphones thrive into the market in the near future.
However, Apple’s AirPods, the newest wireless headphones have quick-connection features that don’t exactly support or work on Android devices. If Android devices start supporting proprietary encoding methods that don’t work on iOS, it’s easy to see the currently-universal Bluetooth system devolving into a mess of competing codecs and compatibility, which would result a shame.
4. Autofill APIs
Platform support for autofill means better security and a more powerful way for an application to store repetitive information. Users can choose an “autofill” app similarly to gow you currently choose a default keyboard. Password managers will be able to work with this autofill settings to surface usernames and passwords that you can enter into apps without erven switching to the password manager.
With the new Autofill API, you will be able to choose a source for autofill data, and apps that need to store and retrieve this sort of data no linger will need to act as an Accessibility service. An app like password manager can bundle its own activity for using the autofill API and we can choose it when we need it like choosing a new keyboard. An app could also be built that acts as a global storage for autofill data without being associated with any one specific program.
5. Picture-in-Picture Videos
Google is moving PiP display support to Android phones. If you’ve used the YouTube app on any of yuour devices in the last year, you’ll be familiar with picture-in-picture viewing. Currently, Android TV has a native PiP display functionality but handsets use a standard multi-window view versus an overlay.
With the new way of doing this, and apps can be designed so that the supplementary window is strictly for content and controls or other bits of app chrome can be placed elsewhere. Basically, this PiP feature lets you resize a video to a small box in the corner while you’re still able to browse around the device. So Google is making it possible for videos system-wide. This also brings a new way to handle screen overlays and methods for a device to launch an app or activity on a remote display.
6. Adaptive icons
The Google Pixel Launcher brought the trend of adaptive icons, and now Android supports them systemwide and natively. Developers can create adaptive icons that can change based on how the system wants to display them, so they fit in on different phones with different interface looks. New icons can be animated in various parts of the interface when interacted with. Options can be given for different shaped masks that define the outside border and icons can be customized to be anumated. Adaptive icons will be supported in the launcher, shortcuts, device Settings app, sharing dialogs, and the app overview screen.
7. Wide-gamut color of apps
Developers building applications for Android O on devices that support wide-gamut color can now leverage those displays. Apps like photo editors and image viewers can make use of this, and the participants simply need to enable a setting letting the system know the app is wide-gamut color aware and embed a wide color profile. Some of the support profiles are AdobeRGB, Pro Photo RGB, and DCI-P3.
8. Much better VOIP apps
Release notes about a “telecom framework”, which will let VOIP apps act like the device’s main telephone app. Currently, only the conventional phone app can trigger most of the features associated with voice calls, but this framework will enable any (authorized) app to work as the main phone app.
This would be one of the huge upgrade who uses a VOIP app over a data plan to make phone calls. For instance, Google Hangouts offers free calling to any number in the US or Canada, so many use that to avoid any long-distance fees, or to make much cheaper overseas calls. The telecoms framework should mean more VOIP apps fill out with features, and more people can ditch their carrier-provided number.
New APIs now support apps that don’t need to use the universal system phone app to display calling info and this data can be displayed and controlled over Bluetooth.
Other welcome changes includes:
* High-quality Bluetooth audio through the Sony LDAC codec. Listen to your favorite music that will sound ever better through Bluetooth connections.
* Connectivity: NAN (Neighborhood Aware Networking) connectivity using the Wi-Fi Aware specification. Devices with supported hardware can easily communicate with each other using Wi-Fi without a central access point.
The first Android O Developer Preview is available today in the form of a factory image file. The Android O Dev Preview is not expected to be bumped to revision 2 until mid-May, with Dev Preview 3 landing in mid-June and a Dev Preview 4 landing shortly before final release in Q3 2017, according to Google’s Android Developers website.
Factory images of Android O Developer Preview 1 for supported devices are here to grab:
Don’t miss to check out: