Hi, I purchased this phone about a week ago and have loved it so far. I saw that Android 7 came out a day ago but when I search for updates I get the message that my device is up to date even though it's on 6.0.1. I have not rooted my phone yet (or even unlocked my bootloader), in short I have not messed with my phone yet, it's as it was when it came from the box (except for the OTAs installed).
All I can think the reason for this may be my region since I live in Pakistan. With my previous phone, I used to get the OTAs on time but this is my first nexus phone and I'm a bit disappointed that I'm not getting the update as soon as it is rolled out if that really is the case. Also, does anyone have an idea when I'll get my update?
this is called a staged rollout. it is to ensure the stability of the update servers as well as to grant google a chance to put an update on hold and safe the majority of the trouble, should critical errors come to light during the early phase of a rollout
Broken303 said:
this is called a staged rollout. it is to ensure the stability of the update servers as well as to grant google a chance to put an update on hold and safe the majority of the trouble, should critical errors come to light during the early phase of a rollout
Click to expand...
Click to collapse
Oh, so how long should it take given the staged rollout goes well.
Hadisultan said:
Oh, so how long should it take given the staged rollout goes well.
Click to expand...
Click to collapse
i believe up to two wrrks, but don't quote me on that. you could always make use of the beta-program to skip the line as i did. just look through some recent threads here or over at androidpolice
Hadisultan said:
Hi, I purchased this phone about a week ago and have loved it so far. I saw that Android 7 came out a day ago but when I search for updates I get the message that my device is up to date even though it's on 6.0.1. I have not rooted my phone yet (or even unlocked my bootloader), in short I have not messed with my phone yet, it's as it was when it came from the box (except for the OTAs installed).
All I can think the reason for this may be my region since I live in Pakistan. With my previous phone, I used to get the OTAs on time but this is my first nexus phone and I'm a bit disappointed that I'm not getting the update as soon as it is rolled out if that really is the case. Also, does anyone have an idea when I'll get my update?
Click to expand...
Click to collapse
You will get OTA update in first 2 weeks of the month, I always get about 15th day in the month, so don't worry.
How mate said, you can use android beta program, just you will get final update and after upgrade just leave android beta program
Sent from my Nexus 5X using XDA-Developers mobile app
Related
This happened with me on Lollipop as well, I never got the OTA until after Xmas, still not a sniff of Marshmallow. May be it is just me, but in theory you think owning a Nexus device means you get updates sooner but for me anyway the reality is by the time you get the OTA other manufacturers already have it out. My S5 got Lollipop before my Nexus 7 2013.
Anyone else have this issue?
I wish I knew the answer to your question. A co-worker got LP with in days of release and my tablet didn't see the update come down until 5.1 was out. Then oddly enough I saw MM with in three days of release and the small update that came after it the day it was posted.
I'm sure Google has some weird plan that only makes sense to them on when and what get the updates but it sure isn't any forum of logic I can understand. I think part of is they push the update to some devices and wait to see the telemetric data come back for a few days to see if there is any major bugs before pushing it out to "everyone." It's not like Google doesn't have the resources to just pump the update out for all to get at once like iOS does.
Has anyone gotten their April security OTA yet? I received the phone a few weeks ago and flashed the March OTA right away and relocked bootloader afterwards because I did not want to sit through several incremental updates. So I am wondering if something went wrong. Does it usually take this long after a new factory image is released for it to get pushed OTA? Sorry, this is my first Nexus since the Galaxy Nexus/Nexus S days.
I own an italian LG Nexus 5X (32 GB variant) and I have received no April update for my phone till now... still waiting
baffo92 said:
I own an italian LG Nexus 5X (32 GB variant) and I have received no April update for my phone till now... still waiting
Click to expand...
Click to collapse
Sometimes ive gotten then within a week sometimes not for 3 weeks ish. Seems fairly random.
Just read up on sideloading the OTA update via ADB, thats what I do now rather than wait. Doesnt need any bootloader unlocking or anything.
Same here: i suggest you to read this https://productforums.google.com/forum/#!topic/nexus/fOAWe8jMRsQ so you'll be more relaxed.
We get it when we get, that's all!
I'm on international variant of the 5x on AT&T here in US and I received the OTA already for April
I've got news!
My Nexus 5X received the OTA tonight at 8.00 PM
Got mine in UK at about 6pm tonight
Sent from my Nexus 5X using XDA-Developers mobile app
fabian.ecker said:
Has anyone gotten their April security OTA yet? I received the phone a few weeks ago and flashed the March OTA right away and relocked bootloader afterwards because I did not want to sit through several incremental updates. So I am wondering if something went wrong. Does it usually take this long after a new factory image is released for it to get pushed OTA? Sorry, this is my first Nexus since the Galaxy Nexus/Nexus S days.
Click to expand...
Click to collapse
I'm also waiting for the update to show up.
I'm also based in the UK and got mine already last week. One thing, though: I've noticed that after the update, the location icon will at one point start to show up permanently in the notification bar, and whenever that happens, my battery drains pretty quickly. Only solution I found was to turn off gps/location. Is anyone else also experiencing this?
got mine in ćzech at 13.april
Hi guys & gals,
I have a stock, unrooted, bootloader locked LG Nexus 5X, which can't find the OTA update to Android Nougat.
I wanted to give it some time, because I thought maybe the 5X updates came later, but it's been quite a few days already and I've read that most people have received their OTA updates already.
Do you have any idea what the problem could be? I check my system of updates a couple of times per day, but nothing, it keeps telling me it's up-to-date.
Could it be possible that the update will not come for weeks after the release?
Thanks!
I gave up waiting just enrolled in beta updated N then un enrolled from beta all good
Sent from my Nexus 5X using Tapatalk
Instead of enrolling in beta, I flashed with factory image after cleaning it i.e. factory reset.
So far, it's buttery smooth.
I hate waiting for OTA. I hope Google will change it to something smoother like getting it immediately as Apple is doing for years. Apple provides OTA updates almost instantly to millions on devices. How many Nexus devices are there...?
Yeah, that's what I was afraid of. The whole promise that Nexus devices would get the first updates went out of the window pretty fast.
My wife's got a Android One, which was upgraded to Android 7 over a week ago.
Well, I'll think about whether I'll upgrade manually or not. I don't like backing up without Titanium.
jordylicht said:
Hi guys & gals,
I have a stock, unrooted, bootloader locked LG Nexus 5X, which can't find the OTA update to Android Nougat.
I wanted to give it some time, because I thought maybe the 5X updates came later, but it's been quite a few days already and I've read that most people have received their OTA updates already.
Do you have any idea what the problem could be? I check my system of updates a couple of times per day, but nothing, it keeps telling me it's up-to-date.
Could it be possible that the update will not come for weeks after the release?
Thanks!
Click to expand...
Click to collapse
there is absolutely no problem apart from this being a nuisance for the imaptient. checking for updates more than once a day (which the system does automatically) does absolutely nothing to your position in the rollout-queue and since google sticks to their staged rollout policy, it is indeed not unlikely for a nexus to not officially receive an OTA until two or three weeks have past (unsure about the specifics).
shufal said:
I hate waiting for OTA. I hope Google will change it to something smoother like getting it immediately as Apple is doing for years. Apple provides OTA updates almost instantly to millions on devices. How many Nexus devices are there...?
Click to expand...
Click to collapse
sure, impatiently waiting for an update to reach one can be nerve wrecking. staged rollouts as google is practicing them are, besides other reasons, to ensure critical bugs that may have slipped through don't mess with every unit out there at once. it's not like google wouldn't have the bandwidth to provide the updates to every nexus at the same time.
you should also consider, that apple has not only full control over the hardware of their limited lineup of devices, but also is the only one working on their code, which is quite different to the way android is handled.
jordylicht said:
Yeah, that's what I was afraid of. The whole promise that Nexus devices would get the first updates went out of the window pretty fast.
My wife's got a Android One, which was upgraded to Android 7 over a week ago.
Well, I'll think about whether I'll upgrade manually or not. I don't like backing up without Titanium.
Click to expand...
Click to collapse
the update is out since the day N was officially released, no promise broken. it's simply not your turn yet to receive it automatically. android one devices, in terms of updates, work exactly like nexus devices afaik, so nothing to worry about when one gets the OTA earlier than a nexus. fortunately google made it quite simple this time to skip the line by enrolling in the beta program for a few minutes.
Broken303 said:
there is absolutely no problem apart from this being a nuisance for the imaptient. checking for updates more than once a day (which the system does automatically) does absolutely nothing to your position in the rollout-queue and since google sticks to their staged rollout policy, it is indeed not unlikely for a nexus to not officially receive an OTA until two or three weeks have past (unsure about the specifics).
sure, impatiently waiting for an update to reach one can be nerve wrecking. staged rollouts as google is practicing them are, besides other reasons, to ensure critical bugs that may have slipped through don't mess with every unit out there at once. it's not like google wouldn't have the bandwidth to provide the updates to every nexus at the same time.
you should also consider, that apple has not only full control over the hardware of their limited lineup of devices, but also is the only one working on their code, which is quite different to the way android is handled.
the update is out since the day N was officially released, no promise broken. it's simply not your turn yet to receive it automatically. android one devices, in terms of updates, work exactly like nexus devices afaik, so nothing to worry about when one gets the OTA earlier than a nexus. fortunately google made it quite simple this time to skip the line by enrolling in the beta program for a few minutes.
Click to expand...
Click to collapse
Who else work on 'Stock Android' besides Google? Samsung? LG? You are bull****ting when you say 'which is quite different to the way android is handled' when we are talking about Google releasing OTA for its own 'Nexus'.
By the way, I am tired of hearing Google ensuring critical bugs may slip through OTA but in reality that never happened. And even if OTA brings any bug, Google always fix it in the next schedule which sometimes took 6< months..
I love Nexus (already hating the branding of Pixel) and I will complain whatever I think Google has the ability to fix.
shufal said:
I hate waiting for OTA. I hope Google will change it to something smoother like getting it immediately as Apple is doing for years. Apple provides OTA updates almost instantly to millions on devices. How many Nexus devices are there...?
Click to expand...
Click to collapse
Those who want it immediately have a path to get it immediately. There was some friction over needing to unlock bootloader to get it immediately in the past because of the factory images, but now with the full (rather than differential) OTAs they provide, you no longer need to have unlocked bootloader.
So your complaint now boils down not to Google providing it immediately but how convenient their "immediate" format is.
IMO most people who want it immediately can be satisfied with the full OTA or factory image. A very small number of people that want it immediately won't be able to use one of those 2 methods and will just wait their turn.
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
jordylicht said:
Yeah, that's what I was afraid of. The whole promise that Nexus devices would get the first updates went out of the window pretty fast.
My wife's got a Android One, which was upgraded to Android 7 over a week ago.
Well, I'll think about whether I'll upgrade manually or not. I don't like backing up without Titanium.
Click to expand...
Click to collapse
Your Nexus 5x was among the first to have Android N available. You could have manually downloaded the full OTA or factory image if you wanted.
The "backup" complaint you have is a red-herring. You don't need to back up if you use the manual methods. The FULL (vs differential) OTA doesn't erase data and the factory image can be made not to erase data by removing one flag from the batch file. Now you might want to backup before the update installs, just to be safe, but that holds even for the differential OTA you get over the air, so it has nothing to do with manually downloading an update.
The scheduling of your automatic download is a separate issue. Nexus has always randomly scheduled downloads. It can take up to 3-4 weeks for everyone to see the update.
I'm sure you will agree that there is a big difference between having Android N available but not being scheduled to download it yet vs other platforms which may not make Android N available at all or won't have it available to download for *anybody* months after it was released.
Google is saying your phone will have the software available, not that their scheduler will have your phone download the update immediately upon availability. They however give you a method to download it immediately if you want to.
Do scheduled OTA update happen on weekends and holidays?
Sent from my Nexus 5X using XDA-Developers mobile app
agouracaguy said:
Do scheduled OTA update happen on weekends and holidays?
Click to expand...
Click to collapse
Yes, algorithm does some undefined random selection process. It doesn't care about weekends or holidays and there is no human involved that might care.
when checking for system updates it says that i am on the latest update 7.1. i dont have the option to update to 7.1.1. does anyone have this problem?
FLUFFYMANGOES said:
when checking for system updates it says that i am on the latest update 7.1. i dont have the option to update to 7.1.1. does anyone have this problem?
Click to expand...
Click to collapse
I'm on Verizon and I'm in the same boat. I wouldn't sweat it. I'm sure it will come soon, these roll outs are staggered. On my old 6p it seemed I was always about a week or two out before getting the update.
I assume there will have to be an update to the root method before we will be able to obtain root after installing the new build?
Have you tried removing sim, rebooting, and trying to search for update again on WiFi with the sim out? My last phone was an unlocked model and it seemed like Verizon didn't want me to get updates but the above tip worked.
Sent from my Pixel XL using Tapatalk
I believe the OTA just came out today.
On other Pure Nexus devices I may not receive the OTA for a few days.
If your not rooted then you just download the system image from the google developer site. Take out the -W command to wipe device and you will be fully updated.
because your pixel is not l33t
The update states that it could take time for the update to become available in each location...
You can side load the ota with fastboot. That's what I did and Im on Verizon.
Updates typically roll out over the course of a couple of weeks. Be patient or sideload the OTA yourself
the thing is that i got my pixel straight from google and my friend who lives in the same area got his pixel from verizon and already has his update. My father's 1 year old nexus 6p already has the update as well clearly google does not have their priorities straight.
FLUFFYMANGOES said:
the thing is that i got my pixel straight from google and my friend who lives in the same area got his pixel from verizon and already has his update. My father's 1 year old nexus 6p already has the update as well clearly google does not have their priorities straight.
Click to expand...
Click to collapse
Most likely gets rolled out by production number or something. Your buddy's phone was probably made before yours, and your father must've purchased his Nexus 6P right when it was released. Like someone else said, these things take time anyways. Be patient or take the time to sideload the OTA yourself.
Sent from my Pixel XL using Tapatalk
Funny my Pixel C got the update yesterday.
I had a strange issue - I hit "Check for Update" and my device began downloading the 263MB update. Once finished downloading, it went to step 2, however it never moved past Step 2. A restart didn't fix the issue. Anything I can do? I'd obviously still would like the update despite whatever strange bug this is. This is a Google Store bought Pixel, on T-Mobile.
Project Fi phone on "V" image.
So yesterday I restored to stock V image.
Wiped everything.
Installed factory V.
Didn't root, kernel or install TWRP.
Nada.
Then checked every hour or so for the O update.
Nothing.
Here I am, 24 hours and still no update available.
So I tried turning off WiFi.
Rebooted.
Waited 20 minutes and then checked and found an update.
Could just be coincidence or maybe enabling data (turning off WiFi) somehow triggered the update as being available.
Samsung apparently has sent out a final notification to all those enrolled in the Nougat Beta that there will be no more updates and that the beta ends officially on December 30th and that they will attempt to push out the official update to everyone in January. Hope this means they were able to quash all major bugs.
http://www.androidcentral.com/galaxy-s7-and-s7-edge-receive-nougat-update-january
And it is officially Android 7.1.1, at least for those in the US.
Hopefully we get it soon, I would love some Nougat. At this point I prefer to not have to root my phone to get updates because it's a hassle without being able to unlock the bootloader. I was rooted for awhile and IMHO stock runs butter unless you spend hours customizing it. I love debloating but I would prefer a fully unlocked/rooted phone to a partial solution.
I don't have high hopes for when we get this updated because of verizon but we eventually will, about 2 years after everyone else
JerseyDubbin said:
Hopefully we get it soon, I would love some Nougat. At this point I prefer to not have to root my phone to get updates because it's a hassle without being able to unlock the bootloader. I was rooted for awhile and IMHO stock runs butter unless you spend hours customizing it. I love debloating but I would prefer a fully unlocked/rooted phone to a partial solution.
I don't have high hopes for when we get this updated because of verizon but we eventually will, about 2 years after everyone else
Click to expand...
Click to collapse
I haven't been rooted for over a year. I was on an LG G3 before my S7 and so far, I haven't found a real need to root. Before, I rooted because I used TiBu to backup my apps, but with the G3, they had their own backup utility that worked just like TiBu, but it's only for LG devices.
But with how Google Play uploads settings now, that appears to work just fine for me as well, so at this point, I have no reason to root. Plus, I really love Samsung Pay so I don't want to lose that.
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
JediDru said:
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
Click to expand...
Click to collapse
Agree completely. The root process works well etc but I had to go through xposed and do a lot of tweaks to get it running well for really no gain over what I had stock.
JediDru said:
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
Click to expand...
Click to collapse
I completely agree. The G3 was the first phone I ended up not rooting. I did at first because I was just in that mode of, get a new phone, root, flash a custom ROM. But as I started getting used to a lot of the features, and found that the battery life wasn't bad, coupled with running Greenify in non-root mode, I could make the battery last 1.5 days. So, over the last year of the two years I owned it, I didn't root.
With the S7, no need to root. This is smoothest phone I've had yet. The quality of the phone itself is excellent. So, this phone will not be rooted.
It appears the official Nougat OTA is being pushed out, with beta testers getting it first.
Anyone on here that has gotten the Nougat OTA notification yet? I'm holding off on accepting until I know better on how it performs, etc.
http://www.androidcentral.com/stabl...ing-galaxy-s7-and-s7-edge-starting-beta-users
iBolski said:
It appears the official Nougat OTA is being pushed out, with beta testers getting it first.
Anyone on here that has gotten the Nougat OTA notification yet? I'm holding off on accepting until I know better on how it performs, etc.
http://www.androidcentral.com/stabl...ing-galaxy-s7-and-s7-edge-starting-beta-users
Click to expand...
Click to collapse
Nothing on my end yet.
Sent from my SM-G930V using XDA-Developers Legacy app
was there ever a second beta OTA sent out to Verizon testers? I didn't get into the beta but side loaded the only 7.0 beta build OTA that was floating around and my build number is NRD90M.G930VVRU4ZPK4. Was there an update to after that? Trying to figure out if the Nougate beta -> final OTA (assuming someone pulls it) will work on my phone or if I'll need to find the intermediary beta OTAs or else wipe clean and start from scratch.
sklarskyj said:
was there ever a second beta OTA sent out to Verizon testers? I didn't get into the beta but side loaded the only 7.0 beta build OTA that was floating around and my build number is NRD90M.G930VVRU4ZPK4. Was there an update to after that? Trying to figure out if the Nougate beta -> final OTA (assuming someone pulls it) will work on my phone or if I'll need to find the intermediary beta OTAs or else wipe clean and start from scratch.
Click to expand...
Click to collapse
I believe there were only two betas for VZW phones and then they cancelled the beta testing for VZW-based phones. Not sure why. Kind of sucks. Probably Big Red had something to do with it.
j0hnh0lmes said:
Nothing on my end yet.
Sent from my SM-G930V using XDA-Developers Legacy app
Click to expand...
Click to collapse
Same here, tried rebooting and checking again a few times and still nothing.
Oh well
I spoke to Verizon about this and they dont know when the update will be out.
SoerenHelmer said:
I spoke to Verizon about this and they dont know when the update will be out.
Click to expand...
Click to collapse
Of course they don't. They have to add crapware, disable a bunch of stuff and add backdoors.
Sent from my SM-G930V using XDA-Developers Legacy app
SoerenHelmer said:
I spoke to Verizon about this and they dont know when the update will be out.
Click to expand...
Click to collapse
That's their usual response.
I've read US-Based carriers have no ETA yet. Grr.
iBolski said:
I've read US-Based carriers have no ETA yet. Grr.
Click to expand...
Click to collapse
I swear searching around the interwebs for information on release dates has at least as much mis-information as looking for information on the election candidates during the election. So much trash.
But I haven't found anyone stating they heard definite dates. I'm thinking it will be late January at this point maybe early Feb before it hits our phones.
i have given up speculating anything that involves verizon. nothing would surprise me.
Take it where its coming from but it looks like some US non-beta testers are starting to see the update. "Unlocked" phones only but still....
http://www.theverge.com/2017/1/19/14321980/samsung-galaxy-s7-edge-android-nougat-update
I have an official unlocked US model, but nothing yet. I expect to see the update by the weekend. Crossing fingers.
lickwid said:
I have an official unlocked US model, but nothing yet. I expect to see the update by the weekend. Crossing fingers.
Click to expand...
Click to collapse
I believe unlocked models should be getting it before us on Verizon. But, there was a story out that stated OTAs for some reason have stopped being pushed out and Samsung has acknowledged this and is looking into why it happened.
http://www.droidviews.com/samsung-galaxy-s7-android-nougat-problems-firmware-delivery-stops/
Whether the "bug" is in the firmware itself or with the update process that sends out the notifications is not mentioned.