So both my sister and I have the same model unlocked Pixel 5 and are using our phones on T-Mobile's network as well.
I've noticed that on my phone I get the Google Play system update (not to be confused with the main phone/security update) whenever I do a manual check for it and a new one's available (Settings, Security, Google Play system update, tap on "Check for update"). But when I do the same thing on her phone, it doesn't update it, even after I restart and ensure that the Google Play Store app is up-to-date as well.
Eventually her phone finally got the December 1 update a couple weeks ago after I tried again, but then now there's a January 1 update and once again mine let me download it right away, but her phone refuses to update that regardless of what I do (main update it does do just fine though).
I'm guessing it will update it soon enough, but why the delay? Can anyone explain why two IDENTICAL phones won't update this at the same time when manually prompted?
Download and install latest Version here
Main components APKs - APKMirror
Main components APKs - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Hey Saturday Night,
Thanks for the link. However, even if it does work for her phone, I still would rather not use it b/c doing so doesn't solve the actual issue of why it's not updating it automatically, or at the very least, when I attempt to update it manually (by doing a recheck).
It seems to update eventually, but I just find it annoying that my phone will do it when I recheck, but not her's. Makes no sense since again we have the same model phone and are on the same carrier.
RockStar2005 said:
Hey Saturday Night,
Thanks for the link. However, even if it does work for her phone, I still would rather not use it b/c doing so doesn't solve the actual issue of why it's not updating it automatically, or at the very least, when I attempt to update it manually (by doing a recheck).
It seems to update eventually, but I just find it annoying that my phone will do it when I recheck, but not her's. Makes no sense since again we have the same model phone and are on the same carrier.
Click to expand...
Click to collapse
Same thing happens to me but in reverse. My wife P5 gets it and then about a month later I get it on my P5. I don't really think about it since it really doesn't affect anything. Is there a reason you feel you need it?
bobby janow said:
Same thing happens to me but in reverse. My wife P5 gets it and then about a month later I get it on my P5. I don't really think about it since it really doesn't affect anything. Is there a reason you feel you need it?
Click to expand...
Click to collapse
Hey Bobby,
Ok, so it's not JUST me. Good to know. lol
No, not really. As I'd mentioned, it's really not a big deal. I just hope it doesn't indicate that there might be a deeper issue present with her phone. Also, I just hate that I can't explain why it happens at all. lol
RockStar2005 said:
Hey Bobby,
Ok, so it's not JUST me. Good to know. lol
No, not really. As I'd mentioned, it's really not a big deal. I just hope it doesn't indicate that there might be a deeper issue present with her phone. Also, I just hate that I can't explain why it happens at all. lol
Click to expand...
Click to collapse
The only thing I can think of is that it's a staged rollout and a random one at that. I update my phone's apps more often than she does so I figured that might be it and then forgot about it. A month later it popped up. I believe the monthlies are way more critical and those come at the same time.
bobby janow said:
The only thing I can think of is that it's a staged rollout and a random one at that.
Click to expand...
Click to collapse
You are correct. It's a scattered release.
xunholyx said:
You are correct. It's a scattered release.
Click to expand...
Click to collapse
Yes. I agree with you both. This answer seems to make the most sense, and so therefore I'm going to consider this issue resolved.
Thank you all so much for your posts!!
saturday_night said:
Download and install latest Version here
Main components APKs - APKMirror
Main components APKs - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Click to expand...
Click to collapse
That's not really an update but more of a place holder. The real update is much larger and can't be installed with an apk. It will change the date to make it look up to date but that's it.
Related
So this is a well-known trick that has worked since the N4 but I wanted to share it anyway. If you go to check for the update and it still says up to date, try this method as it has just worked for my N5 and my N7:
Settings>Apps>All Tab>Google Services Framework>Clear Data>Go back to check update and it should work, if not try the steps again.
Like I said, this has worked for my previous N4, N5, and N7(2013). Each time, I tried the check update button alone at least 5 times in a row with no luck, then trying the trick and checking it worked for each device.
Oh and BTW, this trick if done EXACTLY like this DOES NOT invalidate the tokens like some claim. My play store and GMAIL are completely fine on both devices.
PS: Do this at your own risk/if your new to Android (Butthurt syndrome cured)
A Google employee also explained why you should not do this: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp
Oh no you didn't.
myorks1127 said:
So this is a well-known trick that has worked since the N4 but I wanted to share it anyway. If you go to check for the update and it still says up to date, try this method as it has just worked for my N5 and my N7:
Settings>Apps>All Tab>Google Services Framework>Clear Data>Go back to check update and it should work, if not try the steps again.
Like I said, this has worked for my previous N4, N5, and N7(2013). Each time, I tried the check update button alone at least 5 times in a row with no luck, then trying the trick and checking it worked for each device.
Oh and BTW, this trick if done EXACTLY like this DOES NOT invalidate the tokens like some claim. My play store and GMAIL are completely fine on both devices.
Click to expand...
Click to collapse
You're wrong, you shouldn't do that. A quick Google will tell you why
bozzykid said:
A Google employee also explained why you should not do this: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp
Click to expand...
Click to collapse
I read that post before and have yet to find a single issue with my devices and never had an issue for my N4 when I did it so I don't see what the big deal is...there is another very similar method that does indeed mess up the tokens but it IS NOT the same by any means.
Please prove me wrong, I will check anything on my phone that you think isn't working now because I did this the quick and easy way instead of wasting my time sideloading...
myorks1127 said:
I read that post before and have yet to find a single issue with my devices and never had an issue for my N4 when I did it so I don't see what the big deal is...there is another very similar method that does indeed mess up the tokens but it IS NOT the same by any means.
Please prove me wrong, I will check anything on my phone that you think isn't working now because I did this the quick and easy way instead of wasting my time sideloading...
Click to expand...
Click to collapse
i'm going to go out on a limb and guess that you don't work for Google, specifically the Android/Mobile division. but since you don't see what the big deal is (going against what a Google engineer says) we should all believe you.
this may not mess up your phone, but it wrecks havoc on the back end of Google's servers... when a Google engineer tells us all not to do something, then thoroughly explains why, it's probably best to heed his advice.
Tried this, took five data clears and it gave me the update. Thanks!
Sent from my Nexus 5 using xda app-developers app
Lucke said:
i'm going to go out on a limb and guess that you don't work for Google, specifically the Android/Mobile division. but since you don't see what the big deal is (going against what a Google engineer says) we should all believe you.
this may not mess up your phone, but it wrecks havoc on the back end of Google's servers... when a Google engineer tells us all not to do something, then thoroughly explains why, it's probably best to heed his advice.
Click to expand...
Click to collapse
It doesn't wreak havok on my end so why would I care?
I'll go out on a limb and say if it caused that much grief for Google the clear data feature would have been gone a long time ago.
Its worked since the nexus s btw
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
I've done it with every update since ICS and never had an issue...and its always worked
Sent from my Nexus 5 using xda app-developers app
Glad I finally have some people backing me up lol, my brother is an engineer for Amazon and he thinks he knows everything too...
And this is how people who don't know better come here to XDA and mess up their devices because they follow bad advice that they read. Don't do this. It can have unintended consequences and according to Google has absolutely no effect on when you will receive an OTA.
muyoso said:
And this is how people who don't know better come here to XDA and mess up their devices because they follow bad advice that they read. Don't do this. It can have unintended consequences and according to Google has absolutely no effect on when you will receive an OTA.
Click to expand...
Click to collapse
People who don't follow the exact directions you mean..and are you saying that this trick worked for 3 Nexus devices I own completely by chance after trying to update over 5 times each before doing the trick and then it working after the trick?
myorks1127 said:
People who don't follow the exact directions you mean..and are you saying that this trick worked for 3 Nexus devices I own completely by chance after trying to update over 5 times each before doing the trick and then it working after the trick?
Click to expand...
Click to collapse
What I am saying is that it doesn't matter how many people like you swear that it works. The people who actually work on Android say it doesn't and that it can have bad consequences. And anyone who actually wants the update can simply sideload it with absolutely no ill effects if they want to force the update onto their devices early. There is absolutely zero reason to do what you swear works.
muyoso said:
What I am saying is that it doesn't matter how many people like you swear that it works. The people who actually work on Android say it doesn't and that it can have bad consequences. And anyone who actually wants the update can simply sideload it with absolutely no ill effects if they want to force the update onto their devices early. There is absolutely zero reason to do what you swear works.
Click to expand...
Click to collapse
The reason to do it is to save time and hassle of doing all the steps needed for side loading, but no worries, I got the update faster and easier than anyone who side loaded with ZERO consequences to me..:good:, your Google knee pads must be pretty worn out by now huh?
Or you can just wait for the update. I'm still on 4.4 and happy about it. 4.4.1 brought radio issues, and 4.4.2 also seems to have a few bugs. Hopefully by the time I get the OTA, the bugs will be fixed.
myorks1127 said:
The reason to do it is to save time and hassle of doing all the steps needed for side loading, but no worries, I got the update faster and easier than anyone who side loaded with ZERO consequences to me..:good:, your Google knee pads must be pretty worn out by now huh?
Click to expand...
Click to collapse
Yes, I am sucking Google's **** because I am telling users who don't know better that Google specifically said not to do this. You got me. My secret is out.
myorks1127 said:
It doesn't wreak havok on my end so why would I care?
Click to expand...
Click to collapse
The problem is you don't know if it does. Because the GCM id changes, things like push messages from different apps will likely stop working (maybe permanently if they don't properly handle a changing id). You might not of noticed this much in the past because not a lot of apps utilized GCM push messages. However, more and more apps are using them today.
It's amazing that people will ignore advice from the people that have written the actual software. Just don't do it. The worst part about doing it is that you may not even know that something has messed up because its not obvious.
Thanks worked for me
Took me straight from 4,4 to 4,4.2 after 4 attempts
Lucky me, just got my Note 4 yesterday and checked for software updates just now and low and behold I'm receiving Lollipop, its a 1161.38mb download..
you sure it's lollipop? i know my note 4 received two updates in the past month.
Getting an update on SM-N10A(stock. not rooted) on ATT network. . Its a 1161.38 MB file. Will update on which version does it get updated to shortly.
Update 1: 2.20PM CT: LOL. Installation failed. Try again in 21 hours. Sigh!
SeraldoBabalu said:
you sure it's lollipop? i know my note 4 received two updates in the past month.
Click to expand...
Click to collapse
AT&T started rolling out 5.0.1 this morning to Note 4.
Stupid me
I checked for an update last night and now have to wait 9hrs before being able to check again. Oh well. At work anyways.
sherpa said:
AT&T started rolling out 5.0.1 this morning to Note 4.
Click to expand...
Click to collapse
nice. hopefully not much longer for the canadian releases.
SeraldoBabalu said:
nice. hopefully not much longer for the canadian releases.
Click to expand...
Click to collapse
Just sent a tweet to Rogers telling them AT&T rolled it out now and asking how long it will take for us to get it. I'm not holding out much hope for a reply.
spexwood said:
Stupid me
I checked for an update last night and now have to wait 9hrs before being able to check again. Oh well. At work anyways.
Click to expand...
Click to collapse
You can manually change your date/time to sometime tomorrow and get the update today.
TheIgster said:
Just sent a tweet to Rogers telling them AT&T rolled it out now and asking how long it will take for us to get it. I'm not holding out much hope for a reply.
Click to expand...
Click to collapse
They will just point you here.
HTML:
http://communityforums.rogers.com/html/assets/OSUpgrade.html
And tell you it's TBD. My old co-worker who now works at Rogers looked into it and apparently Samsung isn't releasing that information. As he said it's policy it classify devices that don't get support as TBD as to not piss off customers. Aka it's a coin toss if they are going to release it.
AT&T isn't the same as our devices. The closest we can get is T-Mobile. If and when TMO gets the update we won't be far behind. At least we shouldn't.
Yeah, I know of that link and they have pointed me there before. I've had a dialog going with them actually. I would like to rattle their cages "in public" as much as possible and Twitter is a good way to do that. I really was surprised to just get the Note 4 about 2 weeks ago, thinking it was the current flagship phone and then find out they have no idea when they are going to release Lollipop on it. Just bizarre.
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
TheIgster said:
Yeah, I know of that link and they have pointed me there before. I've had a dialog going with them actually. I would like to rattle their cages "in public" as much as possible and Twitter is a good way to do that. I really was surprised to just get the Note 4 about 2 weeks ago, thinking it was the current flagship phone and then find out they have no idea when they are going to release Lollipop on it. Just bizarre.
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
Click to expand...
Click to collapse
What are these phone updates of which you speak? Yes, I'm on Verizon.
cyprian64 said:
What are these phone updates of which you speak? Yes, I'm on Verizon.
Click to expand...
Click to collapse
lol...yeah, I guess it's not just those of us in Canada. Really missing my Nexus 5 right now with updates right away straight from Google.
TheIgster said:
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
Click to expand...
Click to collapse
I was referring to the 5.0.1 update. It's very possible they will just lazily skip it and go for 5.1
If thats the case we most likely won't see a LP update this year. Remember Samsung had the oportunity to start LP in June and it has taken them 9 months just to get to this point. Considering no Canadian Carriers have been informed of the update even arriving, meaning they have not tested them and that in turn could create another month or two of testing. It's also been disclosed that Samsung has no plans on working on 5.1 at the moment. Let's assume that they wait to give us 5.1 instead of pushing 5.0.1 out. Since they have not even started 5.1 we can assume they might start in two months (Highly doubt it would be that quick). Then if we take the first time frame we add another 9 months plus the fact they wait a month after they build (check the build logs) we are at a total time frame of 12 months out for a single update. Skipping 5.0.1 would mean a total of 21 months of development time before the first actual LP update.
Of course remember this is all assumptions and theory based on what we have seen so far and I could be totally off. At least I hope I am.
airwa1kin7 said:
Of course remember this is all assumptions and theory based on what we have seen so far and I could be totally off. At least I hope I am.
Click to expand...
Click to collapse
Sure hope you're wrong. LOL. I would be pretty pissed off if they don't send out a Lollipop update this year.
SeraldoBabalu said:
you sure it's lollipop? i know my note 4 received two updates in the past month.
Click to expand...
Click to collapse
Yep, it sure was
Showing as Android version 5.0.1
TheIgster said:
Yeah, I know of that link and they have pointed me there before. I've had a dialog going with them actually. I would like to rattle their cages "in public" as much as possible and Twitter is a good way to do that. I really was surprised to just get the Note 4 about 2 weeks ago, thinking it was the current flagship phone and then find out they have no idea when they are going to release Lollipop on it. Just bizarre.
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
Click to expand...
Click to collapse
You'd think that right
How can one of the newest flagships not be on a higher priority?
Sent from my SM-N910W8 using Tapatalk
Are more bloatwares included in this update?
sherpa said:
You can manually change your date/time to sometime tomorrow and get the update today.
Click to expand...
Click to collapse
Oh I know. It's OK though. I was at work with no wifi anyways (and I dont work a desk job either). I have the update downloading now though.
LTE-X said:
Are more bloatwares included in this update?
Click to expand...
Click to collapse
Just the usual AT&T crap... Google Service needs to be updated after Lollipop installs, GS took multiple attempts to finally install, otherwise you keep getting a notice that the update is required.. Not sure if was just me but I had to reboot a few times to finally get the Install option to pop up..
So far I'm liking Lollipop, Visually much more appealing..
Captpt said:
Just the usual AT&T crap... Google Service needs to be updated after Lollipop installs, GS took multiple attempts to finally install, otherwise you keep getting a notice that the update is required.. Not sure if was just me but I had to reboot a few times to finally get the Install option to pop up..
So far I'm liking Lollipop, Visually much more appealing..
Click to expand...
Click to collapse
Just updated to lollipop and I am experiencing memory leak. I performed a factory reset and is doing much better now.
The stories said LG committed to May and it is May 29th- Anybody heard anything new lately?
aaronc_98 said:
The stories said LG committed to May and it is May 29th- Anybody heard anything new lately?
Click to expand...
Click to collapse
Nope...... still waiting..... and waiting
angry
anybody else ticked off that the urbane has 2.0 but not the v2....what kind of crap is that?
predheadtx said:
anybody else ticked off that the urbane has 2.0 but not the v2....what kind of crap is that?
Click to expand...
Click to collapse
Not really, the complaint level of AW2 is so high, of laggy performance, we may be having a favor done for us as tuning is being done before we get. There was an update for earlier released watches this last day which is getting positive feedback. So that is making me think we'll get it very soon now, I think tomorrow.
nigelhealy said:
Not really, the complaint level of AW2 is so high, of laggy performance, we may be having a favor done for us as tuning is being done before we get. There was an update for earlier released watches this last day which is getting positive feedback. So that is making me think we'll get it very soon now, I think tomorrow.
Click to expand...
Click to collapse
Lol swing and a miss. The wear 2.0 developer preview got taken down though, so either its coming soonish or we're just getting f***** on this one. All the indications are there.why would we buy the watch sport if we can flash the 2.0 developer preview?
tooandrew said:
Lol swing and a miss. The wear 2.0 developer preview got taken down though, so either its coming soonish or we're just getting f***** on this one. All the indications are there.why would we buy the watch sport if we can flash the 2.0 developer preview?
Click to expand...
Click to collapse
I downloaded and saved the most recent AW1.5 and AW2 DP. I tried AW2 DP and it was awful, so went back to AW1.5 which I saved in case when AW2 officially released it is still awful.
We're being done a favor getting AW2 late but now I see happy noises on the June release, I'm seeing less reason to wait. But if there is a reason its no bad thing. The only thing I can't do is Android Pay.
If anyone does have the time to try AW2 then by all means flash DP and realize its a totally different everything interface, as I've been on AW now >2 years I find it awkward interface, noobs would take less retraining.
Someone likely has the googleapis link, I just have the file locally backedup.
Android Wear 2.0 fow the W200* is finaly here (well via OTA in Korea... For us via adb sideload )
Here it is the file: http://android.googleapis.com/packa.../af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip
P.S. It works perfectly! Android pay too!!!
Anyone tried the Korean firmware ? I didn't think 2.0 was that bad at all. Few things to fix but added a lot.
SuperlativeB said:
Anyone tried the Korean firmware ? I didn't think 2.0 was that bad at all. Few things to fix but added a lot.
Click to expand...
Click to collapse
I updated earlier today. Made my first successful Android Pay purchase this afternoon. I never tried the preview so I'm still learning all the tricks/quirks of 2.0.
Sweet . Very cool , are you a US model though ? And did you use an OTA update or use PC with unlocked bootloader to flash it ?
SuperlativeB said:
Sweet . Very cool , are you a US model though ? And did you use an OTA update or use PC with unlocked bootloader to flash it ?
Click to expand...
Click to collapse
Yes I have the AT&T model, W200A. I used the minimal adb and fastboot tool to sideload the zip file from my PC. I didn't have to unlock the bootloader.
i updated my w200a today with the korea version. however it felt more like another preview than a final release. Lag is present like on the preview, overheats somewhat easily and the battery drains way faster when you are using it than when you are on 1.5. At least this is my case on the w200a. I did a fsctory reset to see if that solved but no. Same result.
I have the at&t urbane 2 LTE (unlocked)
Until today I was running developer preview (nemo-nvf41u-factory-e269c504)
I had an update come through which has given me:
build number NXH20E
(ANDROID WEAR 2.0.0.159006699)
with security patch 1st May 2017.
The top and bottom buttons are working (re programmed through the options)
Android pay works.
I am in the UK.
furfuxacheman said:
I have the at&t urbane 2 LTE (unlocked)
build number NXH20E
(ANDROID WEAR 2.0.0.159006699)
with security patch 1st May 2017.
The top and bottom buttons are working (re programmed through the options)
Android pay works.
Click to expand...
Click to collapse
I'm in the US and I updated using ADB and the file captured from the ota in Korea and these numbers match exactly to mine.
Found any bugs/issues yet? I've had an occasional lag or two. Android Pay is working and I've successfully tracked runs with GPS using ghostracer paired to the phone through cell data (my main usage requirement).
Not found any bugs on mine.
I have a few side loaded apps that may have been causing the odd glitch now and again whilst on the developer preview, but nothing since the update.
(Side loaded es file explorer so I could use MP3 ringtone on the watch & Google drive to download / upload)
I'm in the US with ATT version. Just got OTA last night. So far so good.
Dont see a specific thread for this.
Pls merge if there is or relink me.
Btw there is an update on note 9 the day i got my phone. 2 days from this post, havent updated it since i dont like being updated to it nowadays bec of issue's i had with updates before.
Wondering how is it for those who did it
wawaweewa said:
Dont see a specific thread for this.
Pls merge if there is or relink me.
Btw there is an update on note 9 the day i got my phone. 2 days from this post, havent updated it since i dont like being updated to it nowadays bec of issue's i had with updates before.
Wondering how is it for those who did it
Click to expand...
Click to collapse
That update has been on pause since day 1 for me as well. I'm......hopelessly......holding out for....root ?
Jammol said:
That update has been on pause since day 1 for me as well. I'm......hopelessly......holding out for....root [emoji848]
Click to expand...
Click to collapse
Thank you not much excited about root. Just want a steady daily driver for me lol. Have you find a way to make it hidden or gone from notification
I updated straight away. Not a single hiccup for me.
wawaweewa said:
Thank you not much excited about root. Just want a steady daily driver for me lol. Have you find a way to make it hidden or gone from notification
Click to expand...
Click to collapse
Download Package Disabler Pro + (Samsung). I think it was $1.99, but it's worth having. Once installed, search "Update" and check the second Software Update from the list.
bsims85 said:
Download Package Disabler Pro + (Samsung). I think it was $1.99, but it's worth having. Once installed, search "Update" and check the second Software Update from the list.
Click to expand...
Click to collapse
wawaweewa said:
Thank you not much excited about root. Just want a steady daily driver for me lol. Have you find a way to make it hidden or gone from notification
Click to expand...
Click to collapse
Yeah that's pretty much the only way to get rid of it for good. Mine is now to the point where it's no longer giving me the option to select "Later." Lol. I just hit the back button and it goes away, then I set it to ignore for 2 hours in notification panel. Why the heck is that the only option Google?!
I should've held off updating since I'm not sure if the night / low light shots being yellow/warm is from the update.
bsims85 said:
Download Package Disabler Pro + (Samsung). I think it was $1.99, but it's worth having. Once installed, search "Update" and check the second Software Update from the list.
Click to expand...
Click to collapse
Ooohh thanks ill try it outt
Anyone updqted theirs yet
wawaweewa said:
Anyone updqted theirs yet
Click to expand...
Click to collapse
Nope. I flashed the U1 version but will have to go back to T-Mobile version because of cell issues.
Jammol said:
Nope. I flashed the U1 version but will have to go back to T-Mobile version because of cell issues.
Click to expand...
Click to collapse
I did mine it was causing some wierd issues with multiple email not showing up and my mic etc. All good for now
I understand the rollout of Android 11 to pixel 4 follows a phased approach. But the days later... Just tell me I am impatient and you also haven't received the OTA upgrade yet. :silly:
Thanks.
riskseeker said:
I understand the rollout of Android 11 to pixel 4 follows a phased approach. But the days later... Just tell me I am impatient and you also haven't received the OTA upgrade yet. :silly:
Thanks.
Click to expand...
Click to collapse
T=Your username says risk seeker.
Take risk, manually flash factory images or adb sideload full ota zip.
indian84 said:
T=Your username says risk seeker.
Take risk, manually flash factory images or adb sideload full ota zip.
Click to expand...
Click to collapse
I would, have custom ROMs on a couple of devices. Not that I wouldn't dare to.
But this Pixel of mine is a company owned device. Don't want to mess around here too much. :angel:
lol just manually checked and mine is downloading now
They (Google) say rollout takes up to two weeks. It's not that I need the upgrade, phone is great. Really.
riskseeker said:
They (Google) say rollout takes up to two weeks. It's not that I need the upgrade, phone is great. Really.
Click to expand...
Click to collapse
I haven't noticed a huge difference. It took a while for it to stop defaulting to Pixel Home, even though I kept setting Nova as default, and at one point yesterday, I stopped getting texts, getting a response from saying "Hey Google" or hitting the Google Assistant button on my Bluetooth but a reboot fixed that. I haven't played with the new features yet, but this update has the least amount of "new" on the surface that I've seen
Still waiting...
kappadappa said:
Still waiting...
Click to expand...
Click to collapse
Same here. Good to know you're not alone. And add said, might take up to two weeks since release.
Strange though, that even manual check doesn't help.
Definitely strange, especially considering that Google emailed me back on Sept 8th telling me "Your Pixel just got turned up to 11" and detailing how to check manually, with no mention that it might take a few days or weeks to show up.
indian84 said:
T=Your username says risk seeker.
Take risk, manually flash factory images or adb sideload full ota zip.
Click to expand...
Click to collapse
OK, damn it. Been there, done that now. Sideload worked without resetting all my data.
Let's hope the monthly security updates will work again as smoothly as before.
The Android 11 update never showed up on my phone but I ended up needing to get a warranty replacement for some problems that showed up (battery indicator stuck at 50%, random shutdowns, phantom screen taps and swipes). I got the replacement yesterday and it updated to Android 11 right away. Not sure if the problems with my old phone were blocking the update.