I'm currently on LMY48P but I use mine on Verizon. Any ideas why VZW SIMs get an extra update? I'm debating skipping it.
opie4624 said:
I'm currently on LMY48P but I use mine on Verizon. Any ideas why VZW SIMs get an extra update? I'm debating skipping it.
Click to expand...
Click to collapse
It's the October security update. Everything that's changed is here: https://groups.google.com/forum/#!topic/android-security-updates/_Rm-lKnS2M8. As for why, well, the best answer is "because Verizon." It's happening with the Nexus 6 too. Nexus 6s with Verizon SIMs are getting LMY48W instead of Marshmallow. Why? Google is basically pushing the October security update while we wait for the Verizon approval process to play out on the Marshmallow update.
Either way, as long as there's a Verizon SIM in your N7 LTE, you're not going to get the Marshmallow OTA until it's approved. So, there is a direct LMY48P -> MRA58K Marshmallow OTA that you can sideload manually if you need Marshmallow that badly, but otherwise just accept the LMY48U OTA when it comes and just settle in. Marshmallow isn't giving you much that Lollipop doesn't.
Bought a Pixel XL from Bestbuy. I unlocked the bootloader and disabled updates. Having second thoughts about keeping over the Google Store version. Since it's unlocked would you just keep it or flash stock, relock, and return and wait out google on my Note 3? I like flashing custom roms but don't want to have issues down the road with a bad flash and trying to fix a bootloop.
I do have a small scuff on the corner so I'm not sure if Bestbuy would even take it back.
Well, I bought mine from google store in hope for it to stay untouched from the corporate greedy hands of vzw, but unfortunately the first update I installed was vzw-exclusive update pushed to my google bought XL
On the other hand, fortunately, I already unlocked it before taking in the update, so for now I am safe. After doing a little research, it turns out that I am not the only one bought from google/fi and received vzw's 63X update.
So, pixel phones (whether bought from google/fi/bb/vzw) on vzw network is like your first used car(vzw exclusive update), you don't want it, but daddy's (vzw) gonna give it to you anyway! Therefore, personally I don't think it would be beneficial to return bb and buy from google since you gonna get the same updates anyway.
n3far1us said:
Well, I bought mine from google store in hope for it to stay untouched from the corporate greedy hands of vzw, but unfortunately the first update I installed was vzw-exclusive update pushed to my google bought XL
On the other hand, fortunately, I already unlocked it before taking in the update, so for now I am safe. After doing a little research, it turns out that I am not the only one bought from google/fi and received vzw's 63X update.
So, pixel phones (whether bought from google/fi/bb/vzw) on vzw network is like your first used car(vzw exclusive update), you don't want it, but daddy's (vzw) gonna give it to you anyway! Therefore, personally I don't think it would be beneficial to return bb and buy from google since you gonna get the same updates anyway.
Click to expand...
Click to collapse
If you put in Vzw sim you will get a Vzw version of the update. It's nothing sinister apparently. Just fine tunes your device to work more efficiently with the VZW network. Mostly the radios. Also you may get several VZW applications that you are free to remove or use. So chillax and enjoy. If you put in AT&T sim you will get the GSM version of the updates instead.
I have done some search over the Internet and got different answers from different people
1. What's the difference between the unlocked and the Verizon phone sold in the Google store? Is the Verizon version bootloader or SIM locked and not unlockable? What's the difference if you buy an unlocked phone and got a SIM from Verizon separately, vs you buy a Verizon version?
2. What's the difference between the two OTA versions:
8.0.0 (OPD1.170816.025, Nov 2017, EMR)
8.0.0 (OPD3.170816.023, Nov 2017, Verizon EMR)
Some says there are some verizon apps included if you download that version. Is it the only difference?
cescman said:
I have done some search over the Internet and got different answers from different people
1. What's the difference between the unlocked and the Verizon phone sold in the Google store? Is the Verizon version bootloader or SIM locked and not unlockable? What's the difference if you buy an unlocked phone and got a SIM from Verizon separately, vs you buy a Verizon version?
2. What's the difference between the two OTA versions:
8.0.0 (OPD1.170816.025, Nov 2017, EMR)
8.0.0 (OPD3.170816.023, Nov 2017, Verizon EMR)
Some says there are some verizon apps included if you download that version. Is it the only difference?
Click to expand...
Click to collapse
Verizon version bootloader is locked and can't be unlocked
google version can be unlocked if you want
google + version sim or any sim will work (no contract :good
8.0.0 (OPD1.170816.025, Nov 2017, EMR)
8.0.0 (OPD3.170816.023, Nov 2017, Verizon EMR)
the same
the only different version apps are disabled by default on the first and enabled on the second
Then why would anyone buy the Verizon version phone?
cescman said:
Then why would anyone buy the Verizon version phone?
Click to expand...
Click to collapse
I guess maybe because of contracts or contract extensions or of discounts at verizon.
cescman said:
Then why would anyone buy the Verizon version phone?
Click to expand...
Click to collapse
Because people want a top tier phone when they can't afford it. So payment plans and kick backs from vzw
Lawlrus said:
Because people want a top tier phone when they can't afford it. So payment plans and kick backs from vzw
Click to expand...
Click to collapse
I thought they cost the same at Google store?
cescman said:
I thought they cost the same at Google store?
Click to expand...
Click to collapse
Vzw offers better prices on trade ins, a payment plan like Google does, plus they offer promos sometimes where Google does not
The radio.img is different on the Verizon build as well.
If you have a Pixel 2 XL from the Google Store and use it on Verizon, which OTA should you use for sideloading? I want the November patch and am considering sideloading it since it's not showing up for me yet, but I don't want to apply the wrong one. (Would it let me?)
abogrhen said:
Verizon version bootloader is locked and can't be unlocked
google version can be unlocked if you want
google + version sim or any sim will work (no contract :good
8.0.0 (OPD1.170816.025, Nov 2017, EMR)
8.0.0 (OPD3.170816.023, Nov 2017, Verizon EMR)
the same
the only different version apps are disabled by default on the first and enabled on the second
Click to expand...
Click to collapse
I have to disagree with most of the respondents here; I'm on Verizon. I bought an unlocked version from google (without sim card); my phone is unlocked. When my phone received the November update it was 8.0.0 (OPD3.170816.023, Nov 2017, Verizon EMR). There were no verizon apps in the update.
Herohtar said:
If you have a Pixel 2 XL from the Google Store and use it on Verizon, which OTA should you use for sideloading? I want the November patch and am considering sideloading it since it's not showing up for me yet, but I don't want to apply the wrong one. (Would it let me?)
Click to expand...
Click to collapse
If you bought it from the Google store, use EMR. Don't use Verizon. You cannot apply the wrong one. The OTA will fail if it cannot confirm that it is the correct device.
Wifi calling. Carriers have had the policy of only allowing Wifi calling on their own phones, not unlocked versions.
Herohtar said:
If you have a Pixel 2 XL from the Google Store and use it on Verizon, which OTA should you use for sideloading? I want the November patch and am considering sideloading it since it's not showing up for me yet, but I don't want to apply the wrong one. (Would it let me?)
Click to expand...
Click to collapse
I have the Google Store unlocked Pix 2 XL, and it runs either version of November software. Gets good Verizon signal on both.
I decided to stay with the Verizon version. Remember to update Android Tools before you do this.
jlokos said:
I have to disagree with most of the respondents here; I'm on Verizon. I bought an unlocked version from google (without sim card); my phone is unlocked. When my phone received the November update it was 8.0.0 (OPD3.170816.023, Nov 2017, Verizon EMR). There were no verizon apps in the update.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2-xl/how-to/mysterious-frozen-disabled-items-apps-t3701958
on Verizon version these apps are enabled
on google version they are disabled
when you set up the phone it was disabled
if you apply an update any disabled app will stay the same
If you have a Verizon SIM, I would go with the OPD3. This recommendation is based off the Verizon OPD3 having a different radio than OPD1. My guess, OPD3 is tuned for Verizon somehow.
I actually created a standalone thread with some information and findings, feel free to take a look...
https://forum.xda-developers.com/pixel-2-xl/how-to/testing-performed-factual-information-t3702662
jedil1c1ous said:
Wifi calling. Carriers have had the policy of only allowing Wifi calling on their own phones, not unlocked versions.
Click to expand...
Click to collapse
Verizon wifi calling works just fine on the Google store unlocked Pixel 2 XL. I've done it many times. But you're right, this is different from the norm.
TheSt33v said:
Verizon wifi calling works just fine on the Google store unlocked Pixel 2 XL. I've done it many times. But you're right, this is different from the norm.
Click to expand...
Click to collapse
How did you get wifi calling to work on unlocked phone with verizon?
EDIT: I figured it out. It says unable to activate.... so it is still not working for me. How did you activate?
jedil1c1ous said:
Wifi calling. Carriers have had the policy of only allowing Wifi calling on their own phones, not unlocked versions.
Click to expand...
Click to collapse
@rester555
This fixes that. Even though that specific thread is for the og pixel xl the same adb commands work on the 2 xl.
bigblueshock said:
If you have a Verizon SIM, I would go with the OPD3. This recommendation is based off the Verizon OPD3 having a different radio than OPD1. My guess, OPD3 is tuned for Verizon somehow.
I actually created a standalone thread with some information and findings, feel free to take a look...
https://forum.xda-developers.com/pixel-2-xl/how-to/testing-performed-factual-information-t3702662
Click to expand...
Click to collapse
Good post about Verizon sims and Google Unlocked version. Have you by any chance relocked and then unlocked your
Px2 XL bootloader when using Verizon sim and software? I could not do that on similar original PixelXL.
Thanks.
rester555 said:
How did you get wifi calling to work on unlocked phone with verizon?
EDIT: I figured it out. It says unable to activate.... so it is still not working for me. How did you activate?
Click to expand...
Click to collapse
I just enabled the setting and it worked. It worked on both the stock out of the box firmware and on 8.1 dev preview. I'm not sure if the latest OTA broke it or not because I won't have my replacement phone until this evening.
Just a quick question, but will I get security updates on my Pixel 2xl the day they're released (ie. today) while being on Koodo? Or will they block it and I'll need to flash it myself?
jordan.harris01 said:
Just a quick question, but will I get security updates on my Pixel 2xl the day they're released (ie. today) while being on Koodo? Or will they block it and I'll need to flash it myself?
Click to expand...
Click to collapse
I don't know anything about the Koodo MVNO, but Security updates are always on a phased roll out schedule by IMEI over the course of 2-3 weeks. You could get it today... or 3 weeks from now, or never. Maybe this will help you decide. The full factory image for September is waiting for you HERE right now. Or you can just read about it HERE.
v12xke said:
I don't know anything about the Koodo MVNO, but Security updates are always on a phased roll out schedule by IMEI over the course of 2-3 weeks. You could get it today... or 3 weeks from now, or never. Maybe this will help you decide. The full factory image for September is waiting for you HERE right now. Or you can just read about it HERE.
Click to expand...
Click to collapse
Do you know if AT&T Prepaid plans delay updates?
.......sorry posted on wrong topic.
He's saying that it's not carrier controlled for the updates. So the answer would be no. If you can't wait a day or few, learn to sideload the OTA. It's literally to commands and it's installed in a few minutes. That what I just did this morning.
qtpa2tnh said:
Do you know if AT&T Prepaid plans delay updates?
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
I'm on Koodo but bought directly from Google. Got update OTA same afternoon it was released.
I got my Pixel 6 Pro directly from Google and have seen it mentioned that there should have been a system update right off the bat. Is this true? If not when does the November Update get released?
It's already released. Did you check your buildnumber?
Are you on an unlocked version on Verizon because I saw someone on the Pixel Superfans group complaining he had to ADB load the update because of being on Verizon. Don't know the validity to that.
I am on VZ, same issue. Had to sideload it. Lots of reports of this on VZ. OP, check your build number in about phone. It should end in .036 for phones not on VZ. If it is being used on VZ it should end in .036.A8.
If it doesn't, sideload the update.
TonikJDK said:
I am on VZ, same issue. Had to sideload it. Lots of reports of this on VZ. OP, check your build number in about phone. It should end in .036 for phones not on VZ. If it is being used on VZ it should end in .036.A8.
If it doesn't, sideload the update.
Click to expand...
Click to collapse
My build number is: SD1A.210817.019.C2
I'm still in the October update.
TonikJDK said:
I am on VZ, same issue. Had to sideload it. Lots of reports of this on VZ. OP, check your build number in about phone. It should end in .036 for phones not on VZ. If it is being used on VZ it should end in .036.A8.
If it doesn't, sideload the update.
Click to expand...
Click to collapse
Same. I think the issue is the publishing date on the VZW update. On their website the November 4th patch is listed as October 28th even though it's really the Google November one. Maybe that's why it's not getting pushed out. Our devices are waiting for a Nov update from Verizon which will not come.
Mine hasn't had an update either but pretty sure it came with the current build, SD1A.210817.036.
bobby janow said:
Same. I think the issue is the publishing date on the VZW update. On their website the November 4th patch is listed as October 28th even though it's really the Google November one. Maybe that's why it's not getting pushed out. Our devices are waiting for a Nov update from Verizon which will not come.
Click to expand...
Click to collapse
Mine is the Oct 5 update.
airmaxx23 said:
Mine is the Oct 5 update.
Click to expand...
Click to collapse
Then you might want to update via adb.