Confession: as a web writer who has to constantly research new stories, keep an eye on social networks, stay in contact with my coworkers, and see if that jerk on eBay has outbid me for the LEGO T-rex from the Dino Defense HQ set, I often have dozens and dozens of Chrome tabs open on my desktop by the end of the day. That sort of wanton disregard for computer memory doesn't really translate over to mobile, where the single screen limits multitasking to a certain degree. But Google is going to enable my bad habits on Android phones and tablets soon: in the third developer preview of Android N, users can open Chrome windows side by side.
Joaomgcd hates touching his phone. At least that's what I think the drive behind all of these apps he keeps developing and improving is. He's truly the man who wants to make automation as attainable of a goal as possible, and to that extent, he has built apps like AutoNotification and AutoInput that allow you to create plenty of new actions that the famous Tasker app can make use of in its automation profiles.
Joao has been working on AutoNotification and AutoInput to add plenty of new features enabled by the additional APIs brought in Android N. AutoNotification is getting custom Quick Settings tiles (feature explanation) and Quick Reply in notifications and Notification Groups (feature explanation).
Quick settings is the site of major improvements in Android N—there's a new row of five toggles along the top of the notification shade, the quick settings can be rearranged, and you can even add new tiles. The latest Android N Dev Preview 3 brings more improvements and tweaks to quick settings.
We've got another tidbit from our time at Google's Android office hours here at I/O, and you're probably not going to like it, Nexus owners. Speaking to Dan Sandler, we were told that night mode and the dark theme were both simply not up to the standard of performance and polish that Google wants to see of features in this release. As such, according to Dan, it is very unlikely either feature will ship when N is released in final form later this year.
We've received dozens of tips about the night mode and dark theme disappearing in Android N Developer Preview 3 (kind of, it still lives on in the quick settings tiles), and it sounds like the reason it's gone is indeed because Google isn't planning to ship it.
Speaking to Google at the Android team's office hours event, we learned that Android N's new seamless update feature, borrowed from Chrome OS, will not be introduced on any current Nexus devices. While the benefits of seamless updates' usage of dual system partitions to allow OS updates to proceed in the background are substantial, they're also a bit of a technical bear to put on existing smartphones. Implementing seamless updates on the Nexus 5X or 6P, for example, would require repartitioning the entire phone, and wouldn't be possible for an end user to complete without hooking the phone up to a computer, allegedly - it would just be a pain, in short.
Google added Daydream to Android way back in Android 4.2, and Google proceeded to do absolutely nothing with it. Well, almost nothing. It's used on Android TV more than on phones and tablets. With the announcement of the new Daydream VR platform, we were wondering what would become of the "old" Daydream. We didn't have to wait long to find out; they changed the name in dev preview 3.
The third developer preview of Android N is now in the wild, and there are lots of interesting tweaks to see. Just for fun, Google threw in four new wallpapers along with the standard pink sky image that came with the last two. We've got them all ready for download below.
You know how when you use your phone or tablet for long periods of time, it gets a little warm? Sometimes it even goes toasty — hi, Snapdragon 810! — and app performance suffers: you start seeing lags and stutters and things don't work as smoothly or as reliably as they should. That's because the system throttles the SoC when it risks reaching its limit temperature. This is the kind of performance issues that the new Sustained Performance Mode aims to solve.
There's a new 'Sustained Performance API' in the latest Android N Developer Preview 3. It works based on feedback provided by OEMs regarding each device and its performance for long-running apps.
The first two N Developer Previews were alpha releases, so naturally a good number of things didn't work correctly. One of the apps that purposely did not work as intended was Android Pay, which produced a screen saying it was disabled until a future release. As Developer Preview 3 is now officially a beta, the Android team has seemingly seen fit to restore Android Pay to working order.
The reason Android Pay now works is because Compatibility Test Suite (CTS) is now approved. This also means other apps that depend on CTS should work too. On Developer Preview 1 and 2, this was not approved, and so Android Pay did not work.