Live data from Hacker News

Taking the final wrapper off of Android 7.0 Nougat

android-developers.blogspot.com

81–90 of 250 posts

Re: Taking the final wrapper off of Android 7.0 Nougat

#81

Earlier quoted context omitted.

> Not really surprising given the device's age Nexus 5 released late 2013, last major OS update in late 2015. Compare to the iPhone 4S, which came out late 2011 and still got iOS 9 (4 years later). Really not buying the "two years is plenty of updates" excuse, especially from the Nexus line.

Not entirely fair comparison since the 4S didn't get every feature; it was a paired down version. AFAIK, Google doesn't cherrypick features for older hardware - it's all our nothing. Also, the 4S ran terribly on ios9, to the point that two of my friends with 4S's just gave in and bought new iphones instead.

I ran it myself as a secondary device for phone app testing and didn't have that problem. Maybe as a daily driver I would have had more trouble?

In my experience, the bigger issue was designers assuming everyone has the taller iPhone 5 screen size (or worse, iPhone 6) and burning up 95% of the screen with keyboard + giant fixed header + fixed footer. Some apps would give you space for maybe two lines of content in between all that.

More of a complaint with 3rd party devs on that though.

Re: Taking the final wrapper off of Android 7.0 Nougat

#82
post #71

Earlier quoted context omitted.

I have been on Android Beta on Nexus 6p and if I turn off the Now Cards, the phone takes 2 days to go from ~95% to ~45%. I do have to pay attention to how I keep the phone charged though... I always try to not charge beyond 95% and never let it drop below 40%.

I assume you can cite no evidence that your battery charging regimen makes any difference whatsoever.

Yea there's a bit of a disconnect between the two "things" stated in my comment. I guess what I was trying to say was that if I was not anal about hi and lo watermarks of the charge and didn't mind it dropping below 40%, and with Now Cards disabled... the phone could keep going between 3 to 4 days without charging.

Re: Taking the final wrapper off of Android 7.0 Nougat

#83
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.

Yeah if people have followed the UI guidelines for Android that has existed since day one, their app will have the required resources for Android to resize and reshape it to fit whatever screen shape the split view will create.

Re: Taking the final wrapper off of Android 7.0 Nougat

#84

Earlier quoted context omitted.

khm, expensive? IIRC nexus 5 had great hardware for it's price.

Indeed. The Nexus 5 was not expensive relative to the iOS devices he is consider getting. 3 years worth of updates was just about worth the device's price. On another note I hated the Nexus 5 and that LCD screen always felt washed out!

N5 is very fast for that price, but camera sucks and plastic frame beaks easily. Not to mention how fragile are side buttons... And screen is quite hard to repair!

But hey, for 350 bucks, it's a good deal.

Re: Taking the final wrapper off of Android 7.0 Nougat

#85
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.

The biggest feature I'm looking for that the newer Nexuses don't have over my N5/N7 is Qi wireless charging. My Nexus 7's USB port has been broken for over a year now, and I've been using a wireless charger all this time. It just seems like a good idea to reduce the wear and tear on the USB ports if I want to continue using the phone for years.

Re: Taking the final wrapper off of Android 7.0 Nougat

#86
post #57
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.

There is one awesome new feature that is not mentioned on most "best new features" list: built-in night mode (blue light filter). Works much better than similar apps from the store - those work by placing a translucent overlay window on top of everything else, which gives everything (including black!) a reddish hue. The new built-in filter, on the other hand, just removes blue, and blacks remain black.

I don't think the blue light filter made it into the final release

Re: Taking the final wrapper off of Android 7.0 Nougat

#87
post #44

Meanwhile many phones (especially vendor-locked ones like the Droid Turbo...) are still stuck on Lollipop.

According† to https://developer.android.com/about/dashboards/index.html

    The recent Marshmallow has 15.2% market share

    Lollipop (14.1% + 21.4%) = 35.5% (the greatest share)

    KitKat has 29.2% (the next greatest share)

    Jelly Bean† still has (6.0% + 8.3% + 2.4%) = 16.7%
Earlier than Jelly Bean is 3.4% of the total share. Jelly Bean was first unveiled in June 2012, four years ago. I think given the development model: large ecosystem of hardware companies, alternative software stacks like Kindle and Cyanogen, a good chunk of it being open-source; given all that I'll forgive Google that we all can't upgrade to Nougat on the day of its release.

As a techie you have to know by now that if you want an up to date version of Android you ought to get a Nexus or a brand which has guaranteed frequent into the future updates. There's not much point in claiming that you're "stuck" at this point.

Data collected during a 7-day period ending on August 1, 2016.

Re: Taking the final wrapper off of Android 7.0 Nougat

#88
post #63

Earlier quoted context omitted.

The only thing I'd add here is that unfortunately the Nexus 5x is not an upgrade over the 5 in terms of performance. It might even be a downgrade (I own both). Because the 5x uses a 64-bit arch, it uses more RAM than the 5x (and both only have 2GB). Also, the SD808 (2GHz) cores in the 5x are hardly a step up from the SD800 (2.2GHz) cores. The only real upgrade the 5x gives you is the camera.

I'll be upgrading my 5 to get USB-C, that little connectivity feature for me is the upgrade clincher.

I guess, but I prefer the wireless charging of the Nexus 5 to the USB-C connector of the 5x. Of course it would be nice to have both. Hopefully this year's versions bring back the wireless charging.

Re: Taking the final wrapper off of Android 7.0 Nougat

#89
post #57
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.

There is one awesome new feature that is not mentioned on most "best new features" list: built-in night mode (blue light filter). Works much better than similar apps from the store - those work by placing a translucent overlay window on top of everything else, which gives everything (including black!) a reddish hue. The new built-in filter, on the other hand, just removes blue, and blacks remain black.

Unfortunately, it doesn't appear that this made it into the final version of N. I can't find it anywhere in the settings anyway.

Re: Taking the final wrapper off of Android 7.0 Nougat

#90
post #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.…

Apple went with option 1 for split screen and picture-in-picture video support on iOS, and a year later many major apps still don't support those features. Option 2 is definitely the way to go.
Post reply on HN