May System update there then gone?

cporta

Well-known member
Sep 22, 2010
85
1
0
Hi, I had a notification this morning that there was a system update available on my 5X. But before I was able to install it the notification went away. I went to check for an update manually, but it says I'm up to date? Any ideas of what happened? I'm still showing on the April 2 update. Thanks.

Posted via the Android Central App
 
re:

Likely Google pulled the update because they noticed something last minute. OR they are doing a rolling release, and you got your notice BEFORE the file was actually available. Just keep checking it should be available to you soon. :)

If you MUST have it right now, here's a guide from one of our Editor's that explains how to do a manual update....

http://www.androidcentral.com/how-manually-upgrade-your-nexus
 
Same happened to me today. But I actually downloaded the update, about 27.x MB I believe. When I hit "Reboot And Install" it looked as if it was going to do it but then went to the check for updates screen, and says my system is up to date.

Posted via the Android Central App
 
Anyone know the 'logic' behind the update roll out process?


You roll out an update over time so the server does not get overwhelmed with people downloading the update. Think of it like when you are in line waiting to get in the hottest night club in town. They only let a few people in at a time, and then as people leave they let in more.
 
I never could understand the logic, my s7 edge gets the may security before my 5x crazy right lol

Posted via the Android Central App
 
I got the May security update today on a 5X, though I did have Android N loaded and switched back this morning. After switching, I originally had the March version of Android; followed quickly by April and then May. My phone currently shows the May 1 Security patch, Build MTC19T. We have a Nexus 5, which received the OTA patch earlier this week, I'm still waiting for the update on my 6P.

Allegedly, the reason for the rollout is to prevent an overload on the various cellular networks from people all trying to download the OTA at the same time.
 
...
Allegedly, the reason for the rollout is to prevent an overload on the various cellular networks from people all trying to download the OTA at the same time.

I hope that's not the true reasoning Google has. I always update on a charger, and by Wi-Fi, regardless of MBs . My paranoia lies in the possibility that my cellular connection drops and the download gets corrupted.
 
Allegedly, the reason for the rollout is to prevent an overload on the various cellular networks from people all trying to download the OTA at the same time.

You roll out an update over time so the server does not get overwhelmed with people downloading the update. Think of it like when you are in line waiting to get in the hottest night club in town. They only let a few people in at a time, and then as people leave they let in more.

I'm not buying either of these reasons. This is Google we're talking about. Google has massive server farms that handle billions (probably more) of queries every day. They're serving up cached images. They're running their own app engine (similar to AWS). If anyone has server infrastructure that can handle over-the-air updates to Nexus devices (which aren't nearly as popular as Samsung Galaxy S# ones, let's face it), it's Google.

And the cellular networks should have nothing to do with it. If I'm remembering correctly, Google won't even let me download the update unless I'm connected to wireless (and if it that's not the case, maybe it should be if they're worried about the carriers).

In any case, we're talking about 20 MB or 60 MB updates. People are now paying for data (unless you're grandparented in on an unlimited plan), so if you pay for that 60 MB of data, the carrier should deliver, and they shouldn't care if it's an OTA or Netflix streaming—data is data.

The most plausible explanation is that Google isn't sure if updates are ready when they're "ready" and so wants to do a slow rollout. Even then, I think they should allow users to opt in (sure, don't pull the update automatically for everyone, but if a user manually selects to check for updates, it should check and pull the latest update).

tl;dr there is no valid reason for Google to withhold released updates from users checking for the updates manually.
 
I'm not buying either of these reasons. This is Google we're talking about. Google has massive server farms that handle billions (probably more) of queries every day. They're serving up cached images. They're running their own app engine (similar to AWS). If anyone has server infrastructure that can handle over-the-air updates to Nexus devices (which aren't nearly as popular as Samsung Galaxy S# ones, let's face it), it's Google.

And the cellular networks should have nothing to do with it. If I'm remembering correctly, Google won't even let me download the update unless I'm connected to wireless (and if it that's not the case, maybe it should be if they're worried about the carriers).

In any case, we're talking about 20 MB or 60 MB updates. People are now paying for data (unless you're grandparented in on an unlimited plan), so if you pay for that 60 MB of data, the carrier should deliver, and they shouldn't care if it's an OTA or Netflix streaming—data is data.

The most plausible explanation is that Google isn't sure if updates are ready when they're "ready" and so wants to do a slow rollout. Even then, I think they should allow users to opt in (sure, don't pull the update automatically for everyone, but if a user manually selects to check for updates, it should check and pull the latest update).

tl;dr there is no valid reason for Google to withhold released updates from users checking for the updates manually.

Actually, many of the updates are larger, over 100 MBs -- and these are the relatively new monthly security updates. An upgrade to a new Android named version (such as Lollipop to Marshmallow) can be a couple of GB. Granted, that likely isn't a huge issue but... my guess is this is largely an outdated policy that Google hasn't updated. Google does allow carrier downloads; though for large updates it may require WiFi to get the update, for a short period (short as in a week or two, trying to get most people to update over WiFi). Remember that LTE has only been around for a few years, and Apple still does not allow updates over cellular data (unless I've missed something).

It may now be outdated but it is a reason why it Google has been doing it. I suspect part of the reason they continue doing it, as others have stated, is that it allows them to stop an update, if there is an issue, while only a few users have updated.
 
my guess is this is largely an outdated policy that Google hasn't updated.
I fully agree. It probably made sense in 2009 or even 2011. Now in 2016, it makes no sense. Do automatic rollouts however you want. If users manually check for an update and are on wireless, there's absolutely no good reason to have released updates not appear.
 
I'm not buying either of these reasons. This is Google we're talking about. Google has massive server farms that handle billions (probably more) of queries every day. They're serving up cached images. They're running their own app engine (similar to AWS). If anyone has server infrastructure that can handle over-the-air updates to Nexus devices (which aren't nearly as popular as Samsung Galaxy S# ones, let's face it), it's Google.

And the cellular networks should have nothing to do with it. If I'm remembering correctly, Google won't even let me download the update unless I'm connected to wireless (and if it that's not the case, maybe it should be if they're worried about the carriers).

In any case, we're talking about 20 MB or 60 MB updates. People are now paying for data (unless you're grandparented in on an unlimited plan), so if you pay for that 60 MB of data, the carrier should deliver, and they shouldn't care if it's an OTA or Netflix streaming—data is data.

The most plausible explanation is that Google isn't sure if updates are ready when they're "ready" and so wants to do a slow rollout. Even then, I think they should allow users to opt in (sure, don't pull the update automatically for everyone, but if a user manually selects to check for updates, it should check and pull the latest update).

tl;dr there is no valid reason for Google to withhold released updates from users checking for the updates manually.

It COULD be partially this, BUT also keep in mind there is a huge difference between a google search and the data that consumes and the download of a very large file. Apple releases their updates all at once and I NEVER get it first couple days because I know their servers are getting hammered.
 
It COULD be partially this, BUT also keep in mind there is a huge difference between a google search and the data that consumes and the download of a very large file. Apple releases their updates all at once and I NEVER get it first couple days because I know their servers are getting hammered.
Yeah, the download is actually easier on the servers, because it's just bandwidth. The search query actually uses processing power to do all the relevant queries. Google has both processing power and bandwidth in abundance. Don't tell me Nexus device OTA downloads get anywhere close to the amount of bandwidth Google has to serve up with YouTube streaming.
 
Yeah, the download is actually easier on the servers, because it's just bandwidth. The search query actually uses processing power to do all the relevant queries. Google has both processing power and bandwidth in abundance. Don't tell me Nexus device OTA downloads get anywhere close to the amount of bandwidth Google has to serve up with YouTube streaming.

Well in any event ANYONE can get the update right now following these instructions....

How to manually update your Nexus | Android Central