The engineering staff in the back of Android O at Google held an AMA on reddit these days, tackling lots of questions that poured in from the Android neighborhood.
As they asked, lots of the questions revolved round developer stuff, akin to API issues and different subjects we don’t talk about closely right here on DL. Alternatively, there have been a couple of fascinating tidbits we needed to proportion with you all.
Under, we’ll position the query, adopted via the staff’s solution(s). If you wish to see the total AMA, a hyperlink to the subreddit can also be discovered under.
How do you organize to make stronger battery lifestyles with each new free up of Android?
A big staff of people who find themselves mavens on many facets of the OS began via having a look at the entire information we had, and then brainstormed an enormous listing of alternatives and then began systematically inspecting to look what lets do. All of those options have been the outcome: Play Console Dashboards for Android Vitals, background execution limits, background location limits, Android Studio efficiency profilers for CPU, reminiscence and community, and extra. We nonetheless really feel just like the battery lifestyles can recuperate so we’ll stay running on it.
What's being finished to shore up the Bluetooth audio resolution?
(Editor’s Word: This can be a shortened model of the solution.) The Android Bluetooth, audio, and efficiency groups in reality did numerous paintings to make stronger BT audio in O. We flipped the transfer internally since the latest developer preview as a result of we wanted a bit of extra time to ensure that issues have been strong, so that you haven’t observed the end result of that exertions reasonably but. Our checking out displays that BT audio reliability is tremendously higher vs N as a result of those adjustments. We’re pleased with the way it’s grew to become out, and we are hoping you spot the similar more or less enhancements.
Is there a programming impediment to complete theming (a l. a. TouchWiz or MiUI) or is it one thing the Android staff doesn’t assume is correct but?
TL;DR Theming isn't laborious. Dependable and constant theming is difficult. There are technical and logistical problems with theming. The technical aspect is in large part solved in O with RRO fortify (thank you Sony!); alternatively, we nonetheless don’t have strong APIs for describing what can also be themed or ok tactics to ensure that current packages correctly fortify theming.
You could be mindful a gloomy theme making temporary appearances in earlier releases — since we already had a gloomy Subject material theme, we didn’t have to fret about APIs to explain the themeable houses; alternatively, we have been not able to transform each current app (ex. Calendar, Pictures, different bundled and core apps — even Settings was once a problem) to fortify darkish Subject material theme and examine that it was once correctly supported.
For those who had, say, a brilliant crimson “Hi Kitty” theme that’s now not a easy brightness inversion, you run into much more difficult instances of making sure minimal distinction ranges for accessibility, choosing affordable secondary and tertiary colours, and many others.
Why couldn’t you enforce Night time Mild in Nexus 6P?
Night time Mild calls for a unique implementation of the HAL utilized by the window compositor. With focal point on more moderen units, Nexus 6P didn't obtain an implementation of the brand new HAL interface.
Will Android O do anything else for Android Wear? With Android Wear 2.0 taking ceaselessly to roll out, and as soon as it did, being plagued with problems with slowness, flat-out non-responsiveness, and UI/UX problems that in reality have an effect on customers, it kind of feels like Google was once seeking to kill AW with that free up.
Android O will most commonly be a technical improve for Android Wear. For instance, Wear gets background limits which is able to lend a hand maintain battery with O and customers can be expecting extra controls over notifications by means of notification channels. As well as, we've got added new equipment for developers to lend a hand enforce headaches and construct watch pleasant UIs.
On Android Wear 2.0, we've got made some technical adjustments in order that updates to machine elements won't at all times want an OS update. For instance, the watch face picker and notification streams have now been decoupled from the OS and can also be up to date extra continuously and independently. We welcome comments on any problems you'll have.
Are we able to be expecting a pc mode for Android with home windows, very similar to what Samsung introduced with S8, in AOSP in a close to long run?
We don’t have any plans to announce at this level. Window control enhancements is an spaces we're nonetheless very in and will proceed to paintings on in the longer term. The point of interest for right here in O was once the brand new PIP characteristic.
With Mission Treble in Android O method higher and more straightforward machine update for OEM. My query is how lengthy are we able to be expecting the Google Pixel and the longer term Google good phone be supported in the longer term?
Units launching with Android O will come Treble-enabled out of the field.
How some distance alongside are you from of completion at the go back of Pill UI?
In truth, I don’t assume capsules is an area the place we will be able to meaningfully discuss “of completion.” It’s extra about working out what the following motive force of innovation shall be for this type issue. We're proceeding to take a position in productiveness use instances (keyboard-driven UI, multiwindow, and many others) but additionally — together with a lot of people in the business — running on what the following evolution of capsules will have to be. For Android, there are some fascinating overlaps with capsules given the expanding luck of Chromebooks and the hot addition of the facility to run Android apps on Chrome OS. We're running to make the Android developer tales for each shape elements (capsules, Chromebooks) equivalent.
Is the white notification coloration a glitch? What came about to the theming engine?
For Android O the entire objective was once to align the lighter notification surface with fast settings. As a outcome we did transfer the default theme of fast settings and made it extra constant. The theming engine remains to be in Android O and it's as much as the software producer to offer other subject matters.
And there you've it, a number of the excellent responses in the AMA. If you wish to see complete and entire solutions, plus all the AMA, practice the hyperlink under!