Guys, I'm reading mixed articles and opinions online and I'm returning to Android after a long time with iOS. The only incentive for me here would OTA updates the day of release. I'm thinking of getting the phone from Verizon and wondering if their updates arrive the same day as Google releasing them, or is there a delay?
Kind regards
Prasad
You will always have a little delay before yout get the OTA, because they are released by stages. I always download the OTA image from google and sideload it via stock recovery. Its the fastest way and you don't need an open bootloader or something.
hells
The way I get the OTA updates, is, I pop out my Sim, clear data from Google play store and Google play services, and then reboot. When I check for an update it will say up to date, but when I put my SIM back in and check again about 30 seconds later the update is already installing.
Only downfall to this method is you have to set up android pay again.
Otherwise you can download the OTA from googles website but it's a pain to do, and it's a big download.
The check for updates issue has been fixed in Google Play Services v12.2.09 or later which is still in beta but I believe a stable version will be released in March. I checked within 1 hour after the March security update was released and had the update available for download. I am running the beta GPS currently.
There is no delay. The pixel series receives their updates directly from Google and can update the day google releases.
Related
Everyone, I have a locked Verizon P2XL running Android P DP3. I've been on the DP train since it went live after I/O and I've had so few problems it's actually surprised me. But that all changed on Wednesday. I have been using Google Pay with no problems up until Wednesday night when I took my wife to Starbucks for a coffee and a chat. I was unable to pay for our products using Google Pay. Weird but okay, I just used my debit card and moved along. When I got home I checked into it. I saw that my device is listed as uncertified in Google Play Store app settings. This was not the case previously. I rebooted into the bootloader and my device states that it is indeed locked. I've already done 2 factory resets, this didn't fix or change anything except that now I have had to sideload Netflix as it won't install from the Play Store on an uncertified device. So that is problem #1, what could have caused this? Will it be fixed (best guesses please) when the DP4 OTA hits my phone? If not will the official release ROM for Android P correct this?
Problem #2 is that I can't get back to stock Android Oreo. I've tried doing it the official way by Opting Out on the DP webpage and taking the OTA. Installation fails with no indication as to why. I've also downloaded the latest official Oreo OTA and used adb sideload to install it. It also fails but using this method I actually get an error message stating that the OTA is older than the currently installed ROM so installation was aborted. I called Google about this, no help. But the support rep agreed with my current idea to try to rollback to Oreo when July's OTA is released as the timestamp will be newer than DP3 so Pixel downgrade protection will be circumvented. Or should be. Back to problem #1, will flashing the July Oreo OTA fix my device uncertified problem? I haven't had this phone very long so I'm disappointed with myself for effing around with the beta program before I really had a chance to use it (got the device in late April).
Thanks for any help.
Problem #1 has been fixed by following the advice of @Phazonclash here: https://forum.xda-developers.com/pixel-2-xl/help/google-pay-issue-t3810129
Problem #2 remains but I'm less eager to revert to Oreo now that the first problem is fixed.
Glad you got it sorted! Anyway, dp4 will be here soon....
Same thing happened to me. DP 3 was running great then out of nowhere the Android Pay was disabled.
I used the ADB commands and reflashed the Oreo Image. Now everything is back to normal. I have read on several forums the same problem.
Looked like some sort of timing issues that inactivates the Android pay after a certain date anticipitating a new build?
Cc
cc999 said:
Same thing happened to me. DP 3 was running great then out of nowhere the Android Pay was disabled.
I used the ADB commands and reflashed the Oreo Image. Now everything is back to normal. I have read on several forums the same problem.
Looked like some sort of timing issues that inactivates the Android pay after a certain date anticipitating a new build?
Cc
Click to expand...
Click to collapse
Which model phone do you have specifically and which Oreo image did you use? As I said I have a Vzw P2XL and I tried to flash the June OTA for the P2XL and it was a no go. I'd love to hear how you managed to do what I failed so miserably at.
Image
I have an unlocked Google version of the Pixel 2 XL. Download the image from the Google site. You can also download the Verizon version.
Cc
I updated my Google Edition Pixel 3XL to 10 two nights ago. Now today, I received a notification that an update failed to install.
I am thrown off because I turned off updates, but regardless of that, if I just updated to 10 two nights ago, what is with this update wanting to install in my device?
I am on vzw OG unlimited data plan, the build # of my currently installed Android version 10 is: QP1A.190711.020.C3. Anyone can enlighten me on this?
Thanks in advance
You're on andriod 10. But you're on the sept, 2019 update. So your phone is probably trying to update to a more current version.
statustray said:
I updated my Google Edition Pixel 3XL to 10 two nights ago. Now today, I received a notification that an update failed to install.
I am thrown off because I turned off updates, but regardless of that, if I just updated to 10 two nights ago, what is with this update wanting to install in my device?
I am on vzw OG unlimited data plan, the build # of my currently installed Android version 10 is: QP1A.190711.020.C3. Anyone can enlighten me on this?
Thanks in advance
Click to expand...
Click to collapse
If your bootloader is unlockable, look at this Guide:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Prerequisites: Factory Images
Then do #4 'keep data' to install the latest Factory image. Do #9 to root.
Thanks for the replies. I appreciate it
I have since updated my device again. I used the "OTA" method to do the update. All-in-all it took about 15 minutes or so. Now the security patch level is: October 5, 2019. I suspect that it will tell me sooner or later that there is an even newer update. Hmmm...
I'm still waiting in the even newer updates to come down to my device. I do like the fact though that I can install an ota with magisk and don't have to connect to a computer.
I just wish I could speed up the updates using that method too. I was thinking that it would install the latest/greatest the first time out of the gate. Lol
I'm still waiting in the even newer updates to come down to my device. I do like the fact though that I can install an ota with magisk and don't have to connect to a computer.
I just wish I could speed up the updates using that method too. I was thinking that it would install the latest/greatest the first time out of the gate. Lol
I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?
ptmuldoon said:
I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?
Click to expand...
Click to collapse
I also haven't received on the same device and version. So, it's seems like a slow rollout
If you manually check for updates in settings does it tell you you're up to date? If so, I'd just get the update from Oxygen Updater and do a local install. Some people did have issues with the first release of OOS12 (C36) but those should have all been resolved in the next one (C39). I never had any issues with the update personally.
Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.
ptmuldoon said:
Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.
Click to expand...
Click to collapse
Probably because C36 is the full update. If it won't let you download both C36 and C40 at the same time (before updating), I'd make sure you have access to wifi in case you're one of the lucky few affected by the mobile network issue in C36. But most likely you'll be fine, the other issues were very minor and you wouldn't even notice if you just install the second update right away.
Does Chrome auto fill work for you on 12? I heard that it was broken, but don't know whether it's been fixed with C40? Holding off on updating until someone can confirm. Thx
EDIT: Decided to bite the bullet and upgraded to C40 on my L2125. I actually like it quite a bit, but can confirm that for me, at least, Chrome auto-fill doesn't work. Other nit is you cannot put the battery percentage in the status bar AND remove the icon; either you have both, none, or just the icon. Also, Netflix is pre-loaded, but won't open or uninstall and update and when I go to the Play Store it shows as incompatible with my device?? (bootloader unlocked, but not re-rerooted yet). Also the power menu no longer gives you a recovery or bootloader option in rebooting. Good things include having more gestures (raise phone to answer) and a panel to control apps that auto-start or not. Also, somehow m yreboot sequence no longer includes the danger, your bootloader has been unlocked, screen (which I didn't think was possible to get rid of).
Rolling back to Android 11 for now. Also, many more root options still available there (like Gravity Box and JamesDSP)
Title says it all, is there a non root way to hurry up the update? I haven't had the popup to update android and was hoping there's a way to check for updates
Settings/system I believe, to check for updates or you can download and sideload the update.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.
Sideload the OTA
NippleSauce said:
Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.
Click to expand...
Click to collapse
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.
pcriz said:
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.
Click to expand...
Click to collapse
You're pretty much correct here. I suppose that Google was a bad example to use. But essentially, the carrier builds allow the applicable carrier to also push apks through when you pull the update OTA. They're not necessarily packaged within the factory image - so I had some horrible word choices in my initial post as they don't really modify the image lmao. But (when looking at the older builds) if you just install the stock build instead of flashing one of the carrier builds, then you won't have to worry about any carrier apps being pulled in along with your OTA update.
But heck, if you're rooted and want to maintain root (and are thus manually updating whilst having OTA disabled), then you wouldn't have to worry about this at all, haha.
Samsung phones were a better example of this, as whenever I would do an OTA update on my S21U, it would also install around 4-5 T-Mobile bloatware apps. But if you manually installed the stock image, that wouldn't happen anymore when updating OTA.
I installed the June '23 update but I don't see the matching factory images I need to extract the boot image in order to root. Anyone seen it anywhere?
I think I may have downloaded a beta by mistake. Is it possible to root a beta version?
June update AFAIK hasn't been released. Rooting beta versions is possible however.
Double check the version/security update level you're on. In my experience, carriers apparently can sneak in their OTAs even if you're on Google's version of the software.
I didn't realize the June was being withheld. I saw June updates on Android Flash Tool and figured second Monday but that doesn't mean much anymore. I hope June is made available as I'm having some issues with no screen response when clicking links using Chrome and Facebook.