Live data from Hacker News

Taking the final wrapper off of Android 7.0 Nougat

android-developers.blogspot.com

11–20 of 250 posts

Re: Taking the final wrapper off of Android 7.0 Nougat

#11

No nexus 5 (not 5x) OTA Update ='(

Not really surprising given the device's age, but still disappointing given the presumably rather large number of Nexus 5 still in use.

The bigger story may be the inability to come up with a compelling reason for N5 users to upgrade, other than getting the latest OS revision. The N5's compactness in particular makes the 5X (and the impending successor, codenamed "Sailfish") a tough sell.

Re: Taking the final wrapper off of Android 7.0 Nougat

#12
post #7

> Multi-Window support lets users run two apps at the same time (click the Multi-Window support link) > If your app targets API level 23 or lower and the user attempts to use the app in multi-window mode, the system forcibly resizes the app unless the app declares a fixed orientation. > If your app does not declare a fixed orientation, you should launch your app on a device running Android 7.0 or higher and attempt t…

This will only break the user experience if the app happens to have a bad experience in this mode and if the user happens to request to use it in this mode. It is hard to know for how many apps this would be the case.

There is no way that they could guarantee that the experience would be perfect for every scenario, so that left them with two options:

1. Make the feature only work for apps that declare support for it. This would significantly degrade the user experience for some apps that would work just fine but have not been updated.

2. Make it work for everything with reasonable defaults that every app should be able to handle. Leave it up to the user to accept the degradation for the ones that don't (or to just not use those applications in those modes).

From a user perspective, it isn't clear to me that option #1 was the wrong choice.

Re: Taking the final wrapper off of Android 7.0 Nougat

#14
post #11

No nexus 5 (not 5x) OTA Update ='(

Not really surprising given the device's age, but still disappointing given the presumably rather large number of Nexus 5 still in use. The bigger story may be the inability to come up with a compelling reason for N5 users to upgrade, other than getting the latest OS revision. The N5's compactness in particular makes the 5X (and the impending successor, codenamed "Sailfish") a tough sell.

It'll be a bummer not using latest android for the first time in many years (HTC G2 -> Nexus 4 -> Nexus 5), but I really can't imagine anything compelling me to pay hundreds of dollars for a new phone for a couple more years. The Nexus 5 has been practically the perfect phone for me.

Re: Taking the final wrapper off of Android 7.0 Nougat

#15
post #7

> Multi-Window support lets users run two apps at the same time (click the Multi-Window support link) > If your app targets API level 23 or lower and the user attempts to use the app in multi-window mode, the system forcibly resizes the app unless the app declares a fixed orientation. > If your app does not declare a fixed orientation, you should launch your app on a device running Android 7.0 or higher and attempt t…

If your app doesn't work on smaller screens or in landscape, you should be declaring that. Otherwise, your app is probably already running on devices with tiny, landscape screens and giving users the same experience as those with larger split screens.

Re: Taking the final wrapper off of Android 7.0 Nougat

#16

Is there a way to force update to Android 7 on Nexus 6P now?

I read that the following works:

1. Sign up for the Android beta programme: g.co/androidbeta

2. Enroll your Nexus

3. Unenroll after you have been updated to Android 7

Make sure you are actually on Android 7 before unenrolling. Going out of a regular beta will wipe your phone!

Cheers

Edit: Copy/Paste sandGorgon’s warning from below.

Re: Taking the final wrapper off of Android 7.0 Nougat

#17
post #7

> Multi-Window support lets users run two apps at the same time (click the Multi-Window support link) > If your app targets API level 23 or lower and the user attempts to use the app in multi-window mode, the system forcibly resizes the app unless the app declares a fixed orientation. > If your app does not declare a fixed orientation, you should launch your app on a device running Android 7.0 or higher and attempt t…

My uninformed guess would say that a sampling of a significant number of apps showed that they rendered fine, and they deemed it worth the trade-off that some may not. The logic probably went along the lines of: it's better for the user to have this feature that works with X% of what they already have installed than to force them to wait for the developers of each and every app to decide if/when they want to get arou…

> a sampling of a significant number of apps showed that they rendered fine

The problem is they break the API all the time, and this leaves Google Play strewn with broken apps. This may break 1% of apps, the next release breaks another 1%, after 10 releases, 10% of the apps not updated are broken.

Here's an example, I go to Google Play and search for "ringtone maker" ( https://play.google.com/store/search?q=ringtone%20maker ). The #3 result for me (which can vary by location) is https://play.google.com/store/apps/details?id=com.anbu.ringt... . So I download the app, click the microphone, say something, hit stop and - "java.io.IOException: Unknown file format".

This is their 3rd result for ringtone maker, has over 5 million downloads and yet their record feature is broken. It used to work but Google changed the API. You can look at the app source code ( https://github.com/malizadehq/ringdroid ) to see where this app broke if you want. This is just one example which comes to mind, I can think of many.

They claim they don't break the API going forward but they do all the time.

Re: Taking the final wrapper off of Android 7.0 Nougat

#18
post #11

No nexus 5 (not 5x) OTA Update ='(

Not really surprising given the device's age, but still disappointing given the presumably rather large number of Nexus 5 still in use. The bigger story may be the inability to come up with a compelling reason for N5 users to upgrade, other than getting the latest OS revision. The N5's compactness in particular makes the 5X (and the impending successor, codenamed "Sailfish") a tough sell.

That's a pretty crappy excuse, I've had laptops that last for 7 years just fine running Linux.

Re: Taking the final wrapper off of Android 7.0 Nougat

#19
post #18
post #11

Earlier quoted context omitted.

Not really surprising given the device's age, but still disappointing given the presumably rather large number of Nexus 5 still in use. The bigger story may be the inability to come up with a compelling reason for N5 users to upgrade, other than getting the latest OS revision. The N5's compactness in particular makes the 5X (and the impending successor, codenamed "Sailfish") a tough sell.

That's a pretty crappy excuse, I've had laptops that last for 7 years just fine running Linux.

Laptops aren't mobile phones though. Phones have seen much, much more change in the past seven years than laptops have.

Re: Taking the final wrapper off of Android 7.0 Nougat

#20
post #4
post #3

Personally, I don't care for any [0] of the new features. This is the greatest feature, because it means Android is mature now. [0] Sure, better performance is always nice, but I don't care for Vulkan, VR Mode, or Multi-Window.

The Doze improvements look nice to me.

This is the most significant update, way way overdue.
Post reply on HN