Google has just introduced the availability of the fourth and final Android O Developer Preview.
As regular, the preview is to be had for the Pixel, Pixel XL, Pixel C, Nexus 5X, Nexus 6P, Nexus Player, and the Android Emulator.
Like the 1/3 preview, we are not anticipating a good deal in UI adjustments on this launch. It will make an effort to discover, but this preview is a bit more strong and performant than the 0.33 release with any luck. Right now, our Pixel XL test tool has an amazing-gradual digicam, frequent crashes, and plenty of Bluetooth issues strolling the third preview.
The Android O APIs had been stable considering launch three, so the important news with these launch seems to be a stable release of version 26 of the Android Support Library. Despite the call, the Android Support Library is genuinely a collection of libraries developers can upload to their apps to deliver some of the present days Android capabilities to an app, regardless of the host OS model. Support Library 26 brings new physics-based animations, downloadable fonts and emojis, and a car-sizing TextView.
This preview seems a bit past due. Google’s schedule has previews pegged for each month, but they have come at the start or center of the month. With the fourth preview, Google simplest has some more days left in July. Next up is the reputable Android 8.0 “O” launch, which Google says can be out “later this summertime.”
First Android O beta (and 2nd preview overall) formally launched.
MOUNTAIN VIEW, Calif.—Google I/O is just getting started, and Google has announced the second Android O device preview. This model is formally a “beta,” which means it will robotically go out to everyone enrolled in the Android Beta Program. Like the primary preview, the beta runs on recent Nexus and Pixel gadgets: the Nexus 5X, Nexus 6P, Nexus Player, Pixel C, Pixel, and Pixel XL.
The first preview of Android O released all of the manner lower back in March, bringing a new settings page, snoozeable notifications, a heritage processing lockdown, and a gaggle of different capabilities. Google additionally sooner or later separated the OS from the hardware and wrapped the Android OS in a modular base called “Project Treble.” While the enterprise didn’t highlight many new capabilities onstage at I/O, it did point out Android Go, a new configuration for Android O phones with 1GB or much less RAM.
The preliminary Android O preview roadmap still holds: Android O can have a Q3 2017 release, with two extra preview releases between now and then. We’ll be putting in the beta and digging deeper later this week.
Android O Developer Preview 3 releases, finalizes APIs.
Less than a month after the discharge of the second Android O developer preview, Google is returned, dropping yet every other version of the OS on us. The 0.33 developer preview should be rolling out to beta gadgets now, and together with an update to the Android Studio SDK, it finalizes the APIs for Android O.
Android O brings a revamp of the notification panel with snooze notifications and a whole new settings app. There’s less difficult updating with Project Treble, definitely redesigned emoji, and a low-cease telephone configuration called “Android Go.” Phones get picture-in-image mode, Android TV receives a brand new home display screen, and quicker boot instances should help each version, but motors with Android must mainly take advantage of it.
The Android O APIs are now formally finalized as “API level 26.” With the finalized APIs, Google says developers must be checking out apps to make sure they still work after the modifications to heritage limits, networking, and protection. The Play Store is also ready to take API Level 26 apps and begin sending them out to users.
The Android O release timeline. We’re getting near very last!
Enlarge / The Android O release timeline. We’re getting close to very last!
The O Developer Preview is available for the Pixel, Pixel XL, Pixel C, Nexus 5X, Nexus 6P, and Nexus Player. Users signed up for the Android Beta Program ought to be receiving a replacement any day now. There are also updated system photos for guide flashing. We’re nevertheless due for one extra preview in July, and Google says the patron launch could be “later in the summer season.”
Google is operating on a brand new Android camera API, supports Camera RAW.
The Nexus 5 camera was a large disappointment, particularly after remarks from high-ranking Googler Vic Gundotra declaring that “we’re dedicated to making Nexus phones insanely super cameras. You wait and see.”
That became nine months ago. We waited and saw, and what confirmed up on the Nexus five wasn’t excellent. There may be an explanation for this, although. According to commits within the public Android source code, which have been first noticed by Josh Brown on Google+, Google is operating on a new digital camera API for Android. Work on the new API started in December 2012, making it appear centered for KitKat. Still, approximately a month before the new OS’s release, the API became pulled from Android’s framework code. The devote that eliminated the API from the discharge. Android code is here, with the remark pronouncing:
DO NOT MERGE: Hide new camera API.
Not yet geared up.
This devotes become pushed on October eleven, about a month earlier than the discharge of KitKat. A month before launch changed into possibly “feature freeze” time, wherein paintings on new capabilities stop, and everyone focuses on fixing insects in time for release. The camera revamp did not make it and became changed with the original digital camera API.
The really proper stuff is the initial commit, which incorporates lots of documentation approximately the brand new digicam setup. There is a new API magnificence called “Android.Hardware.Pictures” (the modern-day camera functionality lives underneath “android.Hardware.Digital camera”), and with the fancier name comes fancier abilities:
Full-capability gadgets allow for consistent with-body control of capture hardware and publish-processing parameters at high frame quotes. They additionally provide output data at high resolution in uncompressed formats, further to compressed JPEG output.
The new digicam API has a backward-compatibility mode for older devices; however, “full-capability” devices now have admission to 3 new picture codecs. The only new photo layout listed that isn’t present in Jelly Bean appears to be helpful for camera RAW:
General RAW camera sensor photo format, usually representing a single-channel Bayer-mosaic photo. Each pixel color sample is stored with 16 bits of precision.
The coloration mosaic format, the maximum and minimal encoding values of the RAW pixel facts, the shaded area of the image, and all different needed records to interpret a RAW sensor photo need to be queried from the @link android.Hardware.Photography.CameraDevice which produced the photo.
Smartphone cameras normally output JPEG documents, which can be compressed, usually finalized images. RAW is minimally compressed and unprocessed, so shooting in RAW gives the photographer an awful lot of extra flexibility after the photograph is shot. Programs like Photoshop can do tons extra with a RAW file than with a JPEG.
Camera RAW isn’t always completely remarkable on a mobile smartphone; Nokia’s upcoming Lumia 1520 might be able to shoot RAW, for instance. Besides making Photoshoppers very happy, the RAW record can be handed to an even more effective onboard image editor, which Google seems very keen on building into Android and Google+.
The new API additionally helps face detection. This feature includes bounding containers around faces and center coordinates for the eyes and mouth. In addition to the face-awareness abilities, the machine can assign precise IDs to each face (provided they live on the display screen), so developers should do things like assign stupid hats to multiple faces in a video feed. While you may have visible face detection on some Android devices, the ones had been all solutions constructed by way of Android OEMs.
There’s help for burst mode, too—some other feature you would swear turned into already protected in Android but is not. On Nexus devices, the best “burst mode” entails the consumer urgent the shutter button without a doubt fast.
The camera device is detachable and disconnected from the Android device, or the digicam service has close down the relationship due to a better-precedence get right of entry to request the digicam tool.
The strangest new feature probably guides for a removable digicam. We cannot remember a single Android device of any type with a detachable camera, so experience loose to go away your recommendations inside the remarks.
The most vital possible improvement that wouldn’t be seen within the source code: photograph fine. Android cameras arguably lag in the back of the iPhone is nice so that this new API may be Google’s option to that problem. Android’s subpar photograph best appears to be throughout-the-board trouble, so perhaps the difficulty sincerely is as low-stage because of the digicam API. There’s no manner to be sure, even though, until we get finished software and devices in our arms. With documentation of the usage of terms like “substantially progressed skills” and “excellent-grain control,” it sincerely appears like Google is out to restore Android’s digital-imaging woes.