Greetings!
I have (2) unlocked Pixel 2's (not rooted) and neither have seen the OTA update to 8.1. Am I the only one experiencing this or are others still waiting for the push? I'm fully capable of grabbing and installing the new images but wanted to see how Google handles these. It seems a bit weird that this has been released but not pushed.
Thoughts?
The pushing out is always done in phases, with just a few getting it in first few days then a larger-scale rollout after that. Some have received it without taking any action themselves, but I think the majority haven't yet.
Large Hadron said:
The pushing out is always done in phases, with just a few getting it in first few days then a larger-scale rollout after that. Some have received it without taking any action themselves, but I think the majority haven't yet.
Click to expand...
Click to collapse
Ok.... Thank you. This confirms it isn't that i need to be too concerned with. A phased approach is better in catching problems early on without impacting majority.
Yeah it will take some time to arrive (totally random). If you want to rush this you have two options:
Option a) Download the full OTA and upload it using ADB from the PC to the Android Recovery.
Option b) Now that there's an official OTA from 8.1 DP2 to 8.1 stable. You can try enrolling into the beta, after doing this, there's a chance you receive the OTA to 8.1 stable because Google roll outs the OTA to all the enrolled people when released. If you receive the OTA to 8.1 DP2 unenroll before applying the OTA and keep waiting.
Sent from my Pixel 2
Will it come to rooted phones? And will I lose root after applying the OTA?
Sent from my [device_name] using XDA-Developers Legacy app
I received my Pixel 2, two days ago and after going through the usual setup, I was offered 8.1 update(size a little over 1GB). Phone came with September patch out of the box. From my previous experience, it may take up to 2 weeks to get the update, but average about 5-7 days.
Large Hadron said:
The pushing out is always done in phases, with just a few getting it in first few days then a larger-scale rollout after that. Some have received it without taking any action themselves, but I think the majority haven't yet.
Click to expand...
Click to collapse
thesebastian said:
Yeah it will take some time to arrive (totally random). If you want to rush this you have two options:
Option a) Download the full OTA and upload it using ADB from the PC to the Android Recovery.
Option b) Now that there's an official OTA from 8.1 DP2 to 8.1 stable. You can try enrolling into the beta, after doing this, there's a chance you receive the OTA to 8.1 stable because Google roll outs the OTA to all the enrolled people when released. If you receive the OTA to 8.1 DP2 unenroll before applying the OTA and keep waiting.
Sent from my Pixel 2
Click to expand...
Click to collapse
Thank you. I'm trying to be patient on this one. The only reason that I have questioned it is due to not being able to root my phone as is. I'm suspecting that with a fresh update to 8.1 the process steps will work correctly.
It's funny in that all i want to do is to block ads. LOL
That you again for your insites.
Weird. I own a Pixel 2 yet the December OTA offers an update for the Pixel 2 XL. Has anyone else experienced this? Should I avoid the update?
I got the update, something like ~600 MB. I haven't noticed any differences yet aside from the AR stickers in the camera, which are kind of fun.
I have a question in regards to getting the OTA updates.
I'm in Australia and got my pixel 2 xl on a plan with Telstra as they are the exclusive carrier here. But I use a Vodafone sim in the phone.
Will this cause me to not get the OTA updates?
Way too long time passed, and I'm still waiting. This is pretty annoying. Now I enrolled to beta to get it, but still nothing. -.-
Are OTA updates not possible for unlocked and rooted phones?
Everytime I try to install the OTA 8.1.0, my Pixel2 downloads the update and installation fails with the error message installation problems.
don't bother. 8.1 is trash. the battery has gone to complete crap on this phone now since 8.1
Sent from my Pixel 2 using Tapatalk
Related
Did anyone besides be get notified of an OTA after they activated their T-Bolt? Did you install it? I didn't for fear it will ruin our current root exploit even though it's not permaroot.
I didn't get it yet, I wish I did though, don't want anything to be wrong if I can't get OTA updates. Hopefully I'll get it later today.
Update: Tried to manually update, phone said I had the latest software.
you can go to settings and check for update.
Crap i just did it again and now it says i don't have one.
I have not been notified but I was told to expect one in the next few days. I was told it contains the fixes for battery life issues.
Sent from my Xoom using Tapatalk
Hello there, I tried to find an answer to this question but I was not able to!
Pixel XL, Project Fi everything is stock, not rooted and I didn't unlock the bootloader...
The first OTA update (the one with 60 mb) took like an hour to install (I thought that the device was stuck and I restarted it, but after reboot same thing, downloaded the file from scratch and took the same time!)
I got the 7.1.1 notification today, downloaded in no time, but installation took a lot of time!
Step 1 like an hour, and Step 2 still happening and didn't finish yet!! (more than an hour!)
I don't have any problem with the device, running smoothly (except this OTA thing)
Ideas?
Same here, installing the updates took a while. Plugging into power and using WiFi makes it faster but they still take a while.
donslade said:
Same here, installing the updates took a while. Plugging into power and using WiFi makes it faster but they still take a while.
Click to expand...
Click to collapse
so is it normal? the phone didn't finish Step 2 yet!
depending how many apps you have installed it can take a while... but you can use your phone normally....
this is the new feature that preloads your update to be ready for the next update... it eliminates the previous versions "android is upgrading" or "optimizing apps" that used to show up after updates
I'm not sure mine took an hour but I run a very lean set of apps it might have taken an hour from start to finish
Definitely intended to go slow. This is so you don't see any performance issues as you are able to use your phone normally.
Last update took my phone almost 2 hours to complete.
Updates are done differently than before. Remember before how after rebooting you'd have to wait forever for apps to prepare? All of that is now done in advance, kinda. Lots of changes but I think what you're seeing is due to the new way updates are installed. Overall it's a good change but the time delay is now before rebooting but at least the phone is very usable during this period.
That's great guys, thanks for sharing this! I didn't think it will take that much, but it took more than 2 hours!
What is the latest update version for Pixel phones?
7.1.1 with December 5 security updates
Charkatak said:
What is the latest update version for Pixel phones?
Click to expand...
Click to collapse
7.1.1 (NMF26Q)
You don't have to wait for the OTA, just download it when a new version is available.
https://developers.google.com/android/ota#sailfish
Install via: adb sideload
krelvinaz said:
7.1.1 (NMF26Q)
You don't have to wait for the OTA, just download it when a new version is available.
https://developers.google.com/android/ota#sailfish
Install via: adb sideload
Click to expand...
Click to collapse
Is this 7.1.1 (NMF26Q) build for US Pixel phones as well? I read somewhere that this update corrected some LTE issues for EU carrier.
Obviously lies
troy` said:
Definitely intended to go slow. This is so you don't see any performance issues as you are able to use your phone normally.
Click to expand...
Click to collapse
Yes there is something wrong with your phone. Your phone is supposed to update only once with the latest, not go through sequential updates that take forever. If you bought this on eBay, or especially a Chinese seller, It probably has some irremovable malware on it. Do not accept people's answers on the internet as a solution. If it's behaving abnormally and you notice it is behaving abnormally, there IS something wrong with it regardless of what people are saying on the internet because they probably know about this malware but are trying to disguise your symptoms.
AndroidInitiate said:
Yes there is something wrong with your phone. Your phone is supposed to update only once with the latest, not go through sequential updates that take forever. If you bought this on eBay, or especially a Chinese seller, It probably has some irremovable malware on it. Do not accept people's answers on the internet as a solution. If it's behaving abnormally and you notice it is behaving abnormally, there IS something wrong with it regardless of what people are saying on the internet because they probably know about this malware but are trying to disguise your symptoms.
Click to expand...
Click to collapse
Lol. Way to resurrect an old Post... You are delusional. This was the way they worked 2.5 years ago, and it's the way they still do things today. I've continued to use Pixel phones this whole time. 1, 2, and 3. All non XL models. Also, the Earth isn't flat.
troy` said:
Lol. Way to resurrect an old Post... You are delusional. This was the way they worked 2.5 years ago, and it's the way they still do things today. I've continued to use Pixel phones this whole time. 1, 2, and 3. All non XL models. Also, the Earth isn't flat.
Click to expand...
Click to collapse
This is because a malware used to run on android that had been reduced to the size of one pixel on the android screen, making it virtually undetectable to the human eye, hence the name, The Google Pixel. Regardless, it still performs poorly.
I know there was a delay with the Q beta 4 after Google released it but too many bad things happened to people's phones so they halted the OTA and then released it again after fixing. I can't remember if I sideloaded the update before I realized that it was problematic, but I haven't received any OTA notification update for the Q 5 even when forcing to check manually.
I know that Q 5 release has happened as I can see downloadable images from earlier this month, but has a similar problem happened this time around (that occurred with initial Q 4) and that's why I'm not being notified right now?
I was on a difference computer during the last release so I can't remember or have records if I sideloaded it, but is there a way to check if I did? I understand that if I sideloaded the update then I won't get future "automatic/transparent" OTA notifications or updates.
Wanted to clear things up since I would rather keep things easy rather than having to keep sideloading them until the official release.
q5 aint out yet
tonybhoy said:
q5 aint out yet
Click to expand...
Click to collapse
Oh man, I don't know how I was misreading things on the Android beta downloads. That's totally the case. Seriously my bad. I'll delete this post in a bit to keep the forum garbage post clean.
its out now
Is anyone else still waiting for the December update to be available for OTA download? Google Pixel 3, unlocked, not rooted, not happy. Never waited this long before.
Is it a Verizon phone? Verizon updates are supposed to roll out this week. The update for non-Verizon phones was available last Monday.
I don't get OTA updates on my rooted phone because of root. I don't know if just being unlocked prevents OTA. You can always download the factory image and manually update. The images are at https://developers.google.com/android/images.
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Fat fingers! 1st sentence intended to be "Thank you for the response".
BlackKeys said:
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Click to expand...
Click to collapse
In that case, you will have to apply the update manually. The factory image is at the URL I gave previously. Edit flash-all.bat/sh to remove the -w from the last line in the file so the phone is not wiped.
You could also apply just the OTA manually. The OTA images are at https://developers.google.com/android/ota. I have not done that - I use the factory image method.
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
BlackKeys said:
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
Click to expand...
Click to collapse
You can search for update errors in logcat. See https://forum.xda-developers.com/t/tutorial-how-to-logcat.1726238/ on how to get a logcat. If you did the manual "Check for update" look in the log at the time you did the check. Logs are kept for quite a while, so the info should still be available.
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
dcarvil said:
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
Click to expand...
Click to collapse
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
TonikJDK said:
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
Click to expand...
Click to collapse
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
dcarvil said:
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
Click to expand...
Click to collapse
That has always been there, very sure of that. A lot of us went done that rabbit hole with the Pixel 1 or 2. We never new for sure what it did, but I remember freezing it and had all kinds of connection problems.
Other carriers have those types of things too. They are built into the image and go live when the phone sees what carrier it is on.
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
T-Mobile I'd imagine. Just use Pixel Flasher or https://flash.android.com
I joined the beta program
BladeRunner said:
I joined the beta program
Click to expand...
Click to collapse
How is it? Stable enough to daily drive? I was stuck on the Nov. 22 patch as well until I sideloaded via ADB last night.
Nov 1 is the latest Play System Update afaik, at least thats what the QPR shows....
Google is having problems
This is one of those moments where it's not you it's them is actually true and not gaslighting . Play Updates are not rolling out properly
BladeRunner said:
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
Click to expand...
Click to collapse
Seems you are not alone.
T-Mobile is running way behind on Google Pixel security updates
Timely updates are supposed to be a prime Pixel perk
www.androidpolice.com
Yeah I am on December update very annoyed with Google nothing has changed
Deleted
That sucks and should not be the Pixel experience. I would call T-Mobile and ask them why you are on an old update?
I have had decent updates so far but would be rather upset if I had a security update that was older than other OEM as that is part of the reason for getting a Pixel.
Sign up for Beta and you'll get QPR2 Beta 2. In my experience, it is much more fluid and responsive than previous builds. It fixes the scrolling issues and seems to have improved battery compared to the December update.
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Colchiro said:
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Click to expand...
Click to collapse
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
EtherealRemnant said:
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
Click to expand...
Click to collapse
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Colchiro said:
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Click to expand...
Click to collapse
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Also mine show November as last play service update (I'm on the beta). Italian unlocked phone
Nov is the latest still for play system. There wasn't a Dec and Jan hasn't rolled out yet
EtherealRemnant said:
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Click to expand...
Click to collapse
There's also the indeterminate minutes, if/when something goes sideways...
This is being delayed for un-branded devices as well, such as mine purchased G-Store direct, based on some sort of carrier-block. I'm tempted to go dig through some dev-docs, to see if I can find this (could be an section not published for most, I suppose), but I figure to what end, mostly.
As you mention, easy side-load, but without knowing why this is being blocked for non-TMo (branded, so not gated by their release of their OTA) devices, it's a gamble of sorts...
I just posted in another thread that I think this is an odd situation. I use an MVNO Boost Mobile that uses T-Mobile and I got the update on the 5th. Maybe I got it before they pulled it? Why would they hold the update back to T-Mobile customers but not the MVNO?