Linked by Thom Holwerda on Mon 22nd Aug 2016 17:43 UTC
Android

It's Android 7.0 Nougat day! Well, for the owners of a small number of Nexus devices, and even then, of a small subset of them, because of the staged rollout - well, for them, it's Android 7.0 Nougat day! If you have a Nexus 6, Nexus 5X, Nexus 6P, Nexus 9, Nexus Player, Pixel C or General Mobile 4G (Android One), you can try checking for updates starting today. Alternatively, you can manually install a factory image once they become available.

Since Nougat's been out as a developer preview for a while - I've been running it on my 6P for months - I doubt any of you will be surprised by what Nougat brings to the table. It's a relatively small release compared to some other Android releases, but it still brings a number of interesting refinements and new features - the biggest of which is probably the new multiwindow feature.

The Verge's got a review up, and mentions some of the less obvious features that I think are quite important:

A lot of what's new in Nougat are features you can't really see. I'm talking about deeply nerdy (but important) stuff like a JIT compiler for ART apps and support for the Vulkan API for 3D graphics. The former should provide some performance gains while the latter will help Android games look way better. Google also fixed up the way Android handles media so that it's more secure, added file-based encryption, and added some features for enterprise users.

Another important feature laying groundwork for the future: seamless updates. Starting with Nougat, Android will use two separate partitions so updates can be installed and applied in the background, so that the next time you reboot, it's ready to go.

As always - no idea when any of you will get to use Nougat, but it's out there now.

Thread beginning with comment 633522
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Comment by SaschaW
by dsmogor on Tue 23rd Aug 2016 16:16 UTC in reply to "RE[2]: Comment by SaschaW"
dsmogor
Member since:
2005-09-01

That's probably because Qualcomm has some better than default compilation technology and OEMs are demanding that it's supported.

Reply Parent Score: 1

RE[4]: Comment by SaschaW
by tylerdurden on Tue 23rd Aug 2016 17:29 in reply to "RE[3]: Comment by SaschaW"
tylerdurden Member since:
2009-03-17

It's more like Android is a multi platform/architecture system, something which iOS or WP are not. So in this case, what works for the single target goose, doesn't necessarily apply to the multi target gander...

Reply Parent Score: 5

RE[5]: Comment by SaschaW
by moondevil on Tue 23rd Aug 2016 17:36 in reply to "RE[4]: Comment by SaschaW"
moondevil Member since:
2005-07-08

WP surely is, as it makes use of UWP model.

iOS as well, because it both targets tvOS, watchOS both using different types of processors as the iPhone and iPad.

Both Apple and Microsoft are able to generate all possible combinations for downloading, Google could easily do the same.

Reply Parent Score: 2