Since the phone was released, there has been three updates to the OS. I got the first one out of the box like most, but the following two have not graced my device.
Has anyone else gotten the OTA's for these builds?
I find it interesting on which devices get certain waves of the rollout of these OTA's.
Thanks!
-Roman
You sure there are 3 updates and not regional updates?
Sent from my Nexus 5X using Tapatalk
I am looking here: https://developers.google.com/android/nexus/images?hl=en#bullhead could these be regional ones?
Romanpower said:
I am looking here: https://developers.google.com/android/nexus/images?hl=en#bullhead could these be regional ones?
Click to expand...
Click to collapse
Those are not regional updates.
The original, the first post-release, and then the November security update. Not sure where to account for the fourth.
I'm surprised they didn't pull the first one since flashing its radio enables Band 12.
Ajfink said:
Those are not regional updates.
The original, the first post-release, and then the November security update. Not sure where to account for the fourth.
I'm surprised they didn't pull the first one since flashing its radio enables Band 12.
Click to expand...
Click to collapse
I really want to know what each of them adds and why I haven't received neither of them! Hmmm.
Do you or anyone know where a changelog would maybe be?
Romanpower said:
I really want to know what each of them adds and why I haven't received neither of them! Hmmm.
Do you or anyone know where a changelog would maybe be?
Click to expand...
Click to collapse
The first one disables Band 12, along with whatever else Google wanted to change. The most recent one just released today so you'll likely be prompted for an OTA shortly, and it's a security release.
There might be a changelog somewhere but I don't have a link to it on hand,
Ajfink said:
The first one disables Band 12, along with whatever else Google wanted to change. The most recent one just released today so you'll likely be prompted for an OTA shortly, and it's a security release.
There might be a changelog somewhere but I don't have a link to it on hand,
Click to expand...
Click to collapse
MDA89E was ship OS
MDB08I Disabled Band 12 and whatnot when it was delivered.
MDB08L is the one in question, what was this one?
MDB08M is the newest one that is a security release, that one is the one we are waiting on right now.
So what was the MDB09L release? Is it a real thing that people got? This is not complexly aimed at you, but to ask the questions to XDA as well. x3
Probably be better to ask Google.
Do you guys know if i have the latest update?
big_b0sss said:
Do you guys know if i have the latest update?
Click to expand...
Click to collapse
No you don't... See romanpower's post just a few above yours
Sent from my Nexus 5X using Tapatalk
Are the security updates patched independently of the main software update?
I am still on MDA89E
I have just been notified to download and install MDB08L, and have done. I'm currently in London, UK - on the EE network
Just checked, no update still, i am on EE too.
Nothing here at all on O2 - still on version it shipped with on launch day [emoji14]
MDB08I here. I just checked for updates and I don't have anything available yet.
Sent from my Nexus 5X using Tapatalk
Weird thing was, i went into system update, clicked the check now button/link and it said no updates available. Then went back to the launcher homepage and within 10 seconds i got the notification to download and install... maybe try that?
wow I don't have any updates besides the one it shipped with and when I check for updates it says I'm up to date. weird.
Methodikull said:
wow I don't have any updates besides the one it shipped with and when I check for updates it says I'm up to date. weird.
Click to expand...
Click to collapse
Same here, stuck on MDA89E on Verizon.. I've done a manual Check for Update every day for the past week, got nothing
I have one straight from Google. Funny thing though, I checked for updates and got a "welcome to your new nexus 5x email"
Methodikull said:
I have one straight from Google. Funny thing though, I checked for updates and got a "welcome to your new nexus 5x email"
Click to expand...
Click to collapse
I had the same thing occur - I've had my 5X for at least a week, so to get this email seems a bit late.
---------- Post added at 09:14 AM ---------- Previous post was at 09:13 AM ----------
Romanpower said:
I really want to know what each of them adds and why I haven't received neither of them! Hmmm.
Do you or anyone know where a changelog would maybe be?
Click to expand...
Click to collapse
For the security updates, you can see the changes here:
https://groups.google.com/forum/#!forum/android-security-updates
Related
Samsung are beginning to roll out the fix for the volume bug. https://twitter.com/#!/SamFirmware/status/140471495288823808
Any more info, like a date, when to expect the update?
Oh, wait, it's Samsung, so it will arrive "anytime soon", which means "by the end of November", which actually means "maybe November, but definitely in December"...
Nice, I should have my Nexus by Tues or Wednesday then.
Interesting it's a radio update, not Android or anything lower level.
How will the fix be delivered? direct to the handset via update or USB?
Too bad they don't seem to have a link to it.
rob6raham said:
How will the fix be delivered? direct to the handset via update or USB?
Click to expand...
Click to collapse
OTA to the handset.
Once someone gets the OTA - they can pull it from a logcat and get the URL - then anyone can download apply without waiting for their IMEI to be flagged to receive the update.
Hm, but this doesn't seem to be an official Twitter account / Website of Samsung.
MysteriousDiary said:
Hm, but this doesn't seem to be an official Twitter account / Website of Samsung.
Click to expand...
Click to collapse
It isn't. But they have good sources.
Chirality said:
Interesting it's a radio update, not Android or anything lower level.
Click to expand...
Click to collapse
How do you know it's radio only update?
omrij said:
How do you know it's radio only update?
Click to expand...
Click to collapse
because it's referencing an increment to the baseband version, and not mentioning anything about an Android version number.
that being said, we don't know what's going to happen yet...
let's see.
omrij said:
How do you know it's radio only update?
Click to expand...
Click to collapse
Because the name of the update is the name of the baseband,not Android.
I am pretty sure it will be more than just the radio, P3Droid tweeted on the 22nd about ICL52 and Adnroid 4.2 with a new baseband.... When though Samsung??!!
We were told the ICL53b update contained the fix, no mention of the baseband version. I can try to get more info but its a holiday weekend here so no idea if i will be able to reach him.
jms.flynn said:
I am pretty sure it will be more than just the radio, P3Droid tweeted on the 22nd about ICL52 and Adnroid 4.2 with a new baseband.... When though Samsung??!!
Click to expand...
Click to collapse
surely its google, not samsung... as a Nexus it is pure android so will come straight from Google and not via samsung
Whyt_e said:
surely its google, not samsung... as a Nexus it is pure android so will come straight from Google and not via samsung
Click to expand...
Click to collapse
As has been proven the bug occurs when the phone is in the bootloader, so it's nothing to do with Android.
The patch needs to be at a hardware level, so it will be firmware update. That comes from Samsung, not Google.
It might be the case that the patch for this particular problem was developed by Samsung but it'll still be released by Google not Samsung. So we are waiting for both but ultimately it'll be Googles decision when to push it. At least that's my understanding of the update process of a Nexus phone.
some people in this thread need to remember a few things:
1) Nexus handsets are made as a collaboration between Google and whoever the chosen manufacturer is.
2) Google push all unbranded Nexus updates, not the manufacturer.
in the case of this update, it will likely be pushed as an update to Android anyway - I have never seen a baseband change come through to an Android handset without it being with an incremental update to Android.
I've got to the stage when I don't care who does what - all I want is an update so that the phone is usable. I suspect many early adopters think the same.
I agree mate. I don't care if apple make the fix. For me this weekend staying in London my phone was unusable in certain parts. Grrrrrrrr
Sent from my Galaxy Nexus using xda premium
Has ANYONE gotten it yet? I feel like I've been reading "You should get the OTA any day now" stories online for a couple months now, and still NOTHING! I am curious if ANYONE has actually gotten it that's on T-Mobile in the US.
Elvis_Marmaduke said:
Has ANYONE gotten it yet? I feel like I've been reading "You should get the OTA any day now" stories online for a couple months now, and still NOTHING! I am curious if ANYONE has actually gotten it that's on T-Mobile in the US.
Click to expand...
Click to collapse
You can rest assured that if it were available there would be a version of it posted here on xda. When it is it will be on here within moments of the devs getting their hands on it or anyone for that matter.
Have you read the correct ones vause what ive seen says that us carriers wont start pushing anything till almost march
The Galaxy S5 got the lollipop 5.0 update in the USA. Thanks LG, while you're busy releasing the update for users in Nigeria, the enthusiasts in the USA are still stuck on KitKat... mine boggling......
Sent from my LG-D851
I'd not LG's fault. In the US the carriers test the software, have LG put their own software on the phone and then test done more. They are the cause if the delay, and with T-mobile they at have Wi-Fi calling so probably even more delay to test that.
Good to know, but I was wondering because I was going back to stock, but course leaving it rooted, but then there was an update. Was that the update that we're all waiting for? or is it just a minor update I think I saw something like 247MB don't know if thats correct but I was going to unroot my phone just to get that update, but thats not Lollipop right?
Alrighty then so... Thanks T-mobile....
Sent from my LG-D851
I think that tweet from LG USA was designed to put pressure on the carriers to hasten the release. Unfortunately for LG this may backfire on them. Most people think phone manufactueres are responsible for timely release of updates. US carriers need to add their bloatware and wi-fi calling in T-mobiles case to the new update. LG's part is done. Call your local branches and bug the crap out of them.
What is so great about lollipop? Xposed doesnt work with it among other things. I would not update even if it was available right now.
glcK23 said:
The Galaxy S5 got the lollipop 5.0 update in the USA. Thanks LG, while you're busy releasing the update for users in Nigeria, the enthusiasts in the USA are still stuck on KitKat... mine boggling......
Sent from my LG-D851
Click to expand...
Click to collapse
Personally, I find it mind boggling that you would blame LG and not T-Mobile. Talk about blaming the wrong party.
---------- Post added at 09:11 PM ---------- Previous post was at 09:11 PM ----------
bigcletus said:
What is so great about lollipop? Xposed doesnt work with it among other things. I would not update even if it was available right now.
Click to expand...
Click to collapse
I'm with you. I have no interest.
Okay then I blame everyone. Better?
Sent from my LG-D851
Just saw news , sprint is getting on Feb 16. We might get before that
So I flashed my phone back to the M version for our phone and did the OTA to R. It said the R update is only available until Feb. 10 so it'll probably be shortly after that.
Id think thay would be a fair assesment. So before mar 1 we could plan to see a roll out or at least definite word
bikrame said:
Just saw news , sprint is getting on Feb 16. We might get before that
Click to expand...
Click to collapse
That'd be nice
stratus1011 said:
So I flashed my phone back to the M version for our phone and did the OTA to R. It said the R update is only available until Feb. 10 so it'll probably be shortly after that.
Click to expand...
Click to collapse
I would think this means the update is hitting phones on the 10th or 11th. Normally they keep the old update rolling until they hot swap with the new one. I would imagine only hours of downtime for updates if they don't hot swap. Then again some people still haven't received the ota notification yet... Who knows?
stratus1011 said:
So I flashed my phone back to the M version for our phone and did the OTA to R. It said the R update is only available until Feb. 10 so it'll probably be shortly after that.
Click to expand...
Click to collapse
ThePagel said:
I would think this means the update is hitting phones on the 10th or 11th. Normally they keep the old update rolling until they hot swap with the new one. I would imagine only hours of downtime for updates if they don't hot swap. Then again some people still haven't received the ota notification yet... Who knows?
Click to expand...
Click to collapse
Sorry to kill the hype, but afaik that date doesn't mean anything.
http://www.androidpolice.com/2013/1...-otas-doesnt-mean-what-you-may-wish-it-meant/
And OTA rolls out in stages, that's why not everyone is getting the OTA notification.
HTC M8 is getting it on the 8th, so in this case the date mentioned sounds like it could be true
Sent from my LG-D851 using Tapatalk
qbanlinxx said:
HTC M8 is getting it on the 8th, so in this case the date mentioned sounds like it could be true
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
And yet there is no ETA for lollipop on the S5 (as for T-mobile variant). Judging the ETA for update for the LG G3 from the update intended for another device from another manufacturer is very immature.
Don't get me wrong, I would want 5.0 on my G3 asap, but I just want to point our that that date is irrelevant, just as the post from AP I linked suggested.
20hall said:
And yet there is no ETA for lollipop on the S5 (as for T-mobile variant). Judging the ETA for update for the LG G3 from the update intended for another device from another manufacturer is very immature.
Don't get me wrong, I would want 5.0 on my G3 asap, but I just want to point our that that date is irrelevant, just as the post from AP I linked suggested.
Click to expand...
Click to collapse
Nobody asked nor cares what your opinion is to my post.
Sent from my LG-D851 using Tapatalk
Has anyone gotten this yet? I see that a couple of Samsung phones from T-Mobile have updated. I thought the Google phones would be the first ones to get these.
Also curious because I heard the back and forth about who was handling updates (Verizon for my VZW model, or straight from Google). So, I was curious if you guys with Google store models have seen this update yet?
st3ph3nbr!tt said:
Has anyone gotten this yet? I see that a couple of Samsung phones from T-Mobile have updated. I thought the Google phones would be the first ones to get these.
Also curious because I heard the back and forth about who was handling updates (Verizon for my VZW model, or straight from Google). So, I was curious if you guys with Google store models have seen this update yet?
Click to expand...
Click to collapse
November security updates haven't been posted on the Google Dev site yet (https://developers.google.com/android/ota). They'll be there before they start pushing via OTA.
Regarding Samsung, I think that their "November" security update contains the bug fixes that Google pushed to Nexus/Pixel in October.
Arriving today according to Verizon.
http://www.droid-life.com/2016/11/07/verizon-pixel-xl-update-bluetooth-wifi-calling-november/
Security patches by Google are always released on the first Monday of the month. For November, the first Monday is today and as you can see on developers.google.com/android/images, the images are now available.
Whats the difference between builds NDE63U, NDE63V and NDE63X?
armandocorti said:
Whats the difference between builds NDE63U, NDE63V and NDE63X?
Click to expand...
Click to collapse
Answered in another thread but, it looks like they're different security patch levels.
http://source.android.com/security/bulletin/index.html
11/1, 11/5, and 11/6. Although after I flashed build X, it shows 11/5 security level so I'm not entirely sure what's up with that.
No OTA yet for my Verizon XL 128gb.
Got tired of waiting, side loaded NDE63X no issues
KMHartford said:
Got tired of waiting, side loaded NDE63X no issues
Click to expand...
Click to collapse
Yeah I used the google flash-all method which wipes userdata but whatever I don't care about that and I'm still unlocked.
Updated via adb sideload from P ---> X.
Unlocked on Verizon went smooth without a hitch. Just to confirm also.
SamuriHL said:
Answered in another thread but, it looks like they're different security patch levels.
http://source.android.com/security/bulletin/index.html
11/1, 11/5, and 11/6. Although after I flashed build X, it shows 11/5 security level so I'm not entirely sure what's up with that.
Click to expand...
Click to collapse
Actually its country/carrier based. U= Europe, X= Verizon, V= everyone else https://developers.google.com/android/images
xxfwmxx said:
Actually its country/carrier based. U= Europe, X= Verizon, V= everyone else https://developers.google.com/android/images
Click to expand...
Click to collapse
Yea I saw that later.
Sent from my Pixel XL using Tapatalk
I got updated to NDE63V on a Verizon Pixel XL.
mtran13 said:
I got updated to NDE63V on a Verizon Pixel XL.
Click to expand...
Click to collapse
OTA or sideload?
st3ph3nbr!tt said:
OTA or sideload?
Click to expand...
Click to collapse
OTA
Fyi, I got the 'X' update OTA in my Verizon model today. I don't care about bootloader unlock, so I took it.
Sent from my Pixel XL using Tapatalk
I don't care about unlock either, and I still haven't gotten the OTA. The other two ppl I know with Verizon models got the update today as well.
st3ph3nbr!tt said:
I don't care about unlock either, and I still haven't gotten the OTA. The other two ppl I know with Verizon models got the update today as well.
Click to expand...
Click to collapse
If you update your Google Play services to version 10.0.84 (440) and use the update menu in the settings the OTA will appear. :highfive:
kossiewossie said:
If you update your Google Play services to version 10.0.84 (440) and use the update menu in the settings the OTA will appear. :highfive:
Click to expand...
Click to collapse
This worked. Thanks! Why is step 2 of 2 taking an hour? Says installing update but my phone is booted. I've never seen this. Especially with such a small update.
When I look at Google play services to update it, both the disable button and force stop are greyed. I see no way to update the app. Any suggestions?
If nobody has, has anyone heard a timeframe?
Not yet, since Monday and today is Thursday, four days ago 8.0 came out. My Pixel XL came out last year with Nougat so this is the first big Platform Upgrade. I'm trying to remember if my former Nexus 5 took so many days to get a Platform Upgrade.
Sent from my Pixel XL using Tapatalk
My understanding from a few articles is that Google is rolling it out and anybody not in the beta program will get it "soon." I have a play store version using a Verizon SIM and I have it check under system update periodically and haven't had it pushed to my phone yet.
Sent from my BTV-W09 using Tapatalk
ahent said:
My understanding from a few articles is that Google is rolling it out and anybody not in the beta program will get it "soon." I have a play store version using a Verizon SIM and I have it check under system update periodically and haven't had it pushed to my phone yet.
Sent from my BTV-W09 using Tapatalk
Click to expand...
Click to collapse
They haven't even posted the actual OTA files yet. Most likely cause they(the public OTA release) are not finalized until after the release to beta users to catch any final issues....as they pulled the one they pushed it at first...then resent(signature issues). Quite a few users reporting O issues....so I would say it will be at best a week or 2 before Google works out the bugs and does public OTA.
Not from non-beta OTA, later I joined the beta, and it came.
Nope I check daily and nothing
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
Nope I check daily and nothing
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Same here man. I'm not expecting it until I see some images posted. And that might be 8.0.1 at this point. Multiple problems out there. No rush whatsoever for me.
Sent from my Pixel using XDA-Developers Legacy app
No OTAs here either, I flashed up from the 7.1.2 August build to the new OPR6 build.
Nothing here either. And like others said, there appear to be some issues with the current release, so I'm in no hurry to upgrade to 8.0. Let them iron out those initial bugs first before they push it to the general public.
jerryhou85 said:
Not from non-beta OTA, later I joined the beta, and it came.
Click to expand...
Click to collapse
I am on the Pixel XL and Nexus 6P with DP4 on both. I received one single ~59MB and ~36MB OTA file on each.
I thought that was really small since all the DP OTAs were ~1GB and so expected a similar size for the stable OTA. Can you share your OTA experience? What was the size and did you receive two files (small+big) as some others are reporting online?
makapav said:
I am on the Pixel XL and Nexus 6P with DP4 on both. I received one single ~59MB and ~36MB OTA file on each.
I thought that was really small since all the DP OTAs were ~1GB and so expected a similar size for the stable OTA. Can you share your OTA experience? What was the size and did you receive two files (small+big) as some others are reporting online?
Click to expand...
Click to collapse
mine was about 60 some mb, I got the OTA before it was pulled the first time and everything went smoothly for me. after reading other's experiences I'm wondering why mine worked.
makapav said:
I am on the Pixel XL and Nexus 6P with DP4 on both. I received one single ~59MB and ~36MB OTA file on each.
I thought that was really small since all the DP OTAs were ~1GB and so expected a similar size for the stable OTA. Can you share your OTA experience? What was the size and did you receive two files (small+big) as some others are reporting online?
Click to expand...
Click to collapse
I was on 7.1.2 and when I was checking system update, it only showed "system is up to date". And then I joined the Android Beta Program and I received a notification that Android O was ready to download, size about 950MB.
Then it proceeds like any other OTA. I didn't get any second package yet.
jerryhou85 said:
I was on 7.1.2 and when I was checking system update, it only showed "system is up to date". And then I joined the Android Beta Program and I received a notification that Android O was ready to download, size about 950MB.
Then it proceeds like any other OTA. I didn't get any second package yet.
Click to expand...
Click to collapse
In your case - you joined the Beta program after Oreo was released - so it makes sense that the OTA to final would be 900MB. Thanks for your response!
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
fatapia said:
mine was about 60 some mb, I got the OTA before it was pulled the first time and everything went smoothly for me. after reading other's experiences I'm wondering why mine worked.
Click to expand...
Click to collapse
OK so I guess the DP4 to final Android Oreo OTA is ~60MB. Thanks man! I will let other people in parallel forums know about it.
Pixel XL from Google Store/on VZ network (off contract). I was not on the DP but sources advised to sign up, get the OTA, and then unenroll. I did that yesterday and am now on OPR6.170523.012 which is stable and I understand the final. Working fine.
lewwill said:
Pixel XL from Google Store/on VZ network (off contract). I was not on the DP but sources advised to sign up, get the OTA, and then unenroll. I did that yesterday and am now on OPR6.170523.012 which is stable and I understand the final. Working fine.
Click to expand...
Click to collapse
On the T-Mobile SIM Pixel XL, from DP4 my current build number is: OPR6.170623.011
Google needs to get its sh*t together and start to clearly communicate what's going on and where we stand.
---------- Post added at 05:43 PM ---------- Previous post was at 05:17 PM ----------
fatapia said:
mine was about 60 some mb, I got the OTA before it was pulled the first time and everything went smoothly for me. after reading other's experiences I'm wondering why mine worked.
Click to expand...
Click to collapse
lewwill said:
Pixel XL from Google Store/on VZ network (off contract). I was not on the DP but sources advised to sign up, get the OTA, and then unenroll. I did that yesterday and am now on OPR6.170523.012 which is stable and I understand the final. Working fine.
Click to expand...
Click to collapse
Got the facts from the Pixel forum here.
If you're on the DP4 Android O, it is considered the final Release Candidate so only the smaller OTA is delivered to bring you in line with the stable release of Android Oreo.
jerryhou85 said:
I was on 7.1.2 and when I was checking system update, it only showed "system is up to date". And then I joined the Android Beta Program and I received a notification that Android O was ready to download, size about 950MB.
Then it proceeds like any other OTA. I didn't get any second package yet.
Click to expand...
Click to collapse
I see that that is a way to basically force the OTA to 8.0, but I'm still uncomfortable doing that without any system or OTA images available on the google site. There must be a reason no images have been posted for any carrier. So I'll sit it out for now and I do believe you will get an updated OTA once the images are released. Even though Oreo is "official" I still thinks it's just a later beta with all the issues they're having.
bobby janow said:
I see that that is a way to basically force the OTA to 8.0, but I'm still uncomfortable doing that without any system or OTA images available on the google site. There must be a reason no images have been posted for any carrier. So I'll sit it out for now and I do believe you will get an updated OTA once the images are released. Even though Oreo is "official" I still thinks it's just a later beta with all the issues they're having.
Click to expand...
Click to collapse
Correct, I have encountered some issues after beta-OTA process, like "Automatic Time Zone" always wrong and hidden wifi not connecting...
I plan to do a factory image flash, if issues persistent, I'll downgrade to 7.1.2 and wait for the real OTA...
bobby janow said:
I see that that is a way to basically force the OTA to 8.0, but I'm still uncomfortable doing that without any system or OTA images available on the google site. There must be a reason no images have been posted for any carrier. So I'll sit it out for now and I do believe you will get an updated OTA once the images are released. Even though Oreo is "official" I still thinks it's just a later beta with all the issues they're having.
Click to expand...
Click to collapse
This is where I am - now. I never normally do the beta stuff, but this time after Monday's announcement, I got excited and believed all the stories about how you could join the beta, just to get the OTA to the "final" release of 8.0 (I was stock, un-rooted, 7.1.2 on T-Mo). I did it, and it worked just as expected. I was first thrown by the naming convention for the build (OPR......., instead of just "OZKL4T" or something--I realize now that might be how they are named from now on). I have also since seen that there is still carrier testing to be conducted, plus other issues. Also, if it's "final", why aren't the images and OTA files here yet - https://developers.google.com/android/images ?? Being cautious, I decided to reflash the latest 7.1.2 image, and wait patiently for the "real" OTA. Not interested in beta testing (any more than we already do by being Nexus/Pixel stock owners). Happy for everyone that is running this latest build, but I'm only interested in the rock-solid, absolutely final images. Those are not here yet, in the form in which they have always come previously (and will almost certainly come again shortly).
Uh....I'm still on November 7.1.1, was about to upgrade August release but waited for the official O release from Google.lol
Sent from my Pixel XL using Tapatalk
Oreo Update for non beta users
http://www.droid-life.com/2017/08/29/verizon-pixel-android-oreo-update/
hello im new to xda and also new to pixel 2 xl ....i got it few days ago factory unlocked and when i set it up i got an update same day on may security update...today i refresh it manually and still on may update...im in uk and usin EE network..as far as i know is google that handles the updates in this case and not the carrier..i dunno why im stucked on may security patch....i went to few shops and their pixel 2 xl are still on may security patch ....any thoughts please?if i put another sim will in away push the july update?thank you.
Me too
Download the July OTA from Google and sideload it using ADB. Directions on how to do it are on the page I just linked to.
I know I can but why OTA doesn't come?
Ask Google. But really, does it matter why when you have the ability to fix the problem?
Because is strange that a brand new device stopped updating. But I know, a solution is a solution.
Not that strange. The rollout of OTAs if I recall is staged. It's possible you're one of the last to get it, or other issues such as network quality could affect it. The only people who would know for certain is Google. I couldn't tell you myself because I download the full OTA every month: I'm rooted and incremental OTAs cause issues.
thanx
Strephon Alkhalikoi said:
Ask Google. But really, does it matter why when you have the ability to fix the problem?
Click to expand...
Click to collapse
i have already contacted google twice
And what did they say? I bet they didn't mention the OTA images mentioned upthread, and I bet you've not taken advantage of it to actually get yourself updated. That of course is your call, but complaining won't get your phone updated any faster.
ok
Strephon Alkhalikoi said:
And what did they say? I bet they didn't mention the OTA images mentioned upthread, and I bet you've not taken advantage of it to actually get yourself updated. That of course is your call, but complaining won't get your phone updated any faster.
Click to expand...
Click to collapse
they said that its up to the carrier...also to clean my framework and playservices and try another that so the other carrier might push thru the update...none of em worked tho.
also to be connected and check it manually
thank u
siggey said:
Me too
Click to expand...
Click to collapse
sorry to hear.but i dont agree with flashing or side load an update
It's a perfectly viable solution, but you're only disagreeing because it isn't the answer you wanted to hear. I don't know who on this forum can give you the answer you want, especially if Google couldn't.
I'm outta here.
ok
Strephon Alkhalikoi said:
It's a perfectly viable solution, but you're only disagreeing because it isn't the answer you wanted to hear. I don't know who on this forum can give you the answer you want, especially if Google couldn't.
I'm outta here.
Click to expand...
Click to collapse
ok mate cu take care bye
tazddude79 said:
sorry to hear.but i dont agree with flashing or side load an update
Click to expand...
Click to collapse
Install a VPN, and try checking for an update. It worked once for me.
The VPN was Set to UK I think, If not USA.
thanx
JazonX said:
Install a VPN, and try checking for an update. It worked once for me.
The VPN was Set to UK I think, If not USA.
Click to expand...
Click to collapse
thanx a lot
JazonX said:
Install a VPN, and try checking for an update. It worked once for me.
The VPN was Set to UK I think, If not USA.
Click to expand...
Click to collapse
Tried but nothing, USA, UK, Canada.. I wait till the next security update, if nothing I'll sideload..
thank u
siggey said:
Tried but nothing, USA, UK, Canada.. I wait till the next security update, if nothing I'll sideload..
Click to expand...
Click to collapse
r u based in usa or europe pls?my huawei mate 10 is on june lol...it makes no sense for a pure android to b behind like that...google support told me carriers should send it to u...why is pure android tho.google sends it
tazddude79 said:
r u based in usa or europe pls?my huawei mate 10 is on june lol...it makes no sense for a pure android to b behind like that...google support told me carriers should send it to u...why is pure android tho.google sends it
Click to expand...
Click to collapse
Europe
Strephon Alkhalikoi said:
Not that strange. The rollout of OTAs if I recall is staged. It's possible you're one of the last to get it, or other issues such as network quality could affect it. The only people who would know for certain is Google. I couldn't tell you myself because I download the full OTA every month: I'm rooted and incremental OTAs cause issues.
Click to expand...
Click to collapse
True but that should only take like 2 weeks at the MOST. It should never take until after the next update is out. There have been two updates released since then. We are less than 2 weeks away from the August update.
thanx
siggey said:
Europe
Click to expand...
Click to collapse
u.k here