31–40 of 250 posts
Earlier quoted context omitted.
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.
We're going through the same technology change with mobiles now, but that even seems to be tapering off now.
> 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…
> 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 feature should be turned on for all apps; you shouldn't make every user wait for every app ever made to be updated because three people on the Android developer team made a new feature and were too afraid to break things, so they turn it off by default for legacy (pre-Nougat targeted) apps.
EDIT: I should read the whole thread before posting. GrinningFool made the same argument:
Earlier quoted context omitted.
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%…
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.
> 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.
No Android 7 on my Nexus 5 might just be what pushes me to iOS. I've gone from being an Android evangelist to being an Android apologist ("Yeah, battery life sucks. Google has failed to fix it after X years") to now being, frankly, pissed off that my expensive phone is going to be left behind.
Earlier quoted context omitted.
This is the most significant update, way way overdue.
Seriously. I switched back to an iPhone from Lollipop earlier this year, and the difference in battery life is staggering, even though the iPhone has a smaller battery than the Android phone I used to have. I'm glad that Google has signaled that they are going to further tighten the restrictions on background app activities in future releases. I hope they follow through with it.
Anything you can do with an app you can do as well with a website.
Any actual app, not just a website in form of an app, which did computational task, data recording, or kept services available, is impossible to create now.
Run tracking app that doesn’t require you uploading your GPS data to Google Fit? Impossible.
Messaging app that doesn’t route all your private messages through Google Cloud Messaging? Impossible.
EDIT: before downvoting, read the comment below from morsch, he and I explained there pretty well the issues.
Is there a way to force update to Android 7 on Nexus 6P now?
It looks like the 6P image is available: http://www.androidpolice.com/2016/08/22/flash-all-the-things...
Download it to your device, and either flash it in TWRP or use adb sideload. Note that if you've modified your /system, you'll need to reflash that partition with the stock image first (there are guides on XDA).
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.
> 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.