I was curious what build numbers you all have received! I heard there are different build numbers based on where you are located in the world. I personally received one with the build number NDE63L being here in the US.
NDE63P. I'm in Florida.
Sent from my Pixel XL using Tapatalk
NDE63P in mn
Sent from my Pixel XL using XDA-Developers mobile app
NDE63H in Germany
NDE63P. Also in Florida.
NDE63H in the UK (EE network)
Odd that I'm seeing most US (so far) have the P variant when I received one with the L variant. I've been having issues with receiving calls on Sprint network as well as data connection (at times). I just flashed the P variant onto my phone from Google's factory images. Hopefully that'll sort out my issue as the baseband versions are different but bootloaders are identical.
blaz4710 said:
Odd that I'm seeing most US (so far) have the P variant when I received one with the L variant. I've been having issues with receiving calls on Sprint network as well as data connection (at times). I just flashed the P variant onto my phone from Google's factory images. Hopefully that'll sort out my issue as the baseband versions are different but bootloaders are identical.
Click to expand...
Click to collapse
Interesting. I have the L variant as well and I'm in NJ on AT&T. I have noticed that sometimes my txt's don't come in. Then all of a sudden I get 2 or 3 in a row as if they were backed up.
NDE63L in Colorado on Google Fi purchased from the Google Store
mdecker79 said:
Interesting. I have the L variant as well and I'm in NJ on AT&T. I have noticed that sometimes my txt's don't come in. Then all of a sudden I get 2 or 3 in a row as if they were backed up.
Click to expand...
Click to collapse
Although sad to hear you are having issues, I am also glad I am no the only one. I wonder if it has something to do with the new Doze as I've noticed the phone call issue is when the phone as been idle for awhile.
NDE63P uk ee
blaz4710 said:
Although sad to hear you are having issues, I am also glad I am no the only one. I wonder if it has something to do with the new Doze as I've noticed the phone call issue is when the phone as been idle for awhile.
Click to expand...
Click to collapse
Yes I can agree with the Doze on the go "issue". Some of my push emails using Nine or Gmail don't come in right away. I'm ok with this because of the extra battery life. It's really only a few minutes delayed so its not that bad.
Anybody have NDE63P on tmo in the us?
mcrumps said:
Anybody have NDE63P on tmo in the us?
Click to expand...
Click to collapse
I believe P is Verizon build. It's not just location US vs international but carrier with Vzw's exclusivity and custom build
NDE63L FL as well
NDE63L, PR
mcrumps said:
Anybody have NDE63P on tmo in the us?
Click to expand...
Click to collapse
Yes
NDE63L. California, purchased from the Google Store.
XX63L. T-Mobile. California. First batch
All the builds are the same from the looks of the kernel date, so might just be region based. We'll find out when the next release hits
P on Google Store purchased phone with Verizon service. VA
Related
Hi all,
I have a VZW 10 running 1.19. I'm interested in knowing if the connectivity issues, specifically Wi-Fi, have been fixed. The patch notes for 1.53 do address it, but has it been fixed.
I know there are workarounds, but this is a $550 phone. Wi-Fi should work out of the box.
Thanks for your help.
Sent from my HTC6545LVW using Tapatalk
dn.lck said:
Hi all,
I have a VZW 10 running 1.19. I'm interested in knowing if the connectivity issues, specifically Wi-Fi, have been fixed. The patch notes for 1.53 do address it, but has it been fixed.
I know there are workarounds, but this is a $550 phone. Wi-Fi should work out of the box.
Thanks for your help.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
1.53 is for general US unlocked and not VZW. 1.53 needs non VZW firmware to work properly.
1.19 is a very old build (US launched with 1.21) so I'd expect a VZW update sometime in the next 30 days.
Sent from my HTC One using Tapatalk
datafoo said:
1.53 is for general US unlocked and not VZW. 1.53 needs non VZW firmware to work properly.
1.19 is a very old build (US launched with 1.21) so I'd expect a VZW update sometime in the next 30 days.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm on 1.19 as well shipped from Verizon. no update was available to 1.21 for me. I'm currently using viper now with 1.19 still, hoping to see something pop up on here :fingers-crossed:
I seem to have wifi issues using standard wifi, but if I use the wifi-5G connection It works flawless
afuller42 said:
I'm on 1.19 as well shipped from Verizon. no update was available to 1.21 for me. I'm currently using viper now with 1.19 still, hoping to see something pop up on here :fingers-crossed:
I seem to have wifi issues using standard wifi, but if I use the wifi-5G connection It works flawless
Click to expand...
Click to collapse
Correct, 1.21 is ONLY for general unlocked versions and not VZW. You won't see a 1.21.617.* or 1.53.617.* update as those are not for your device. In fact you shouldn't use any *.617.* build as the 617 indicates it's not for your carrier but general unlocked.
You must use a VZW build because of firmware and custom VZW settings. Your only choice right now is to wait for VZW to push their build update.
Sent from my HTC One using Tapatalk
My wifi was fine on 1.21, then was horrible with the 1.53 update. It's mostly alright now with a couple tweaks.
datafoo said:
Correct, 1.21 is ONLY for general unlocked versions and not VZW. You won't see a 1.21.617.* or 1.53.617.* update as those are not for your device. In fact you shouldn't use any *.617.* build as the 617 indicates it's not for your carrier but general unlocked.
You must use a VZW build because of firmware and custom VZW settings. Your only choice right now is to wait for VZW to push their build update.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Interesting. How will future firmware updates work? Will we receive the same but with .605 at the end?
regalpimpin said:
My wifi was fine on 1.21, then was horrible with the 1.53 update. It's mostly alright now with a couple tweaks.
Click to expand...
Click to collapse
Sent from my HTC6545LVW using Tapatalk
dn.lck said:
Interesting. How will future firmware updates work? Will we receive the same but with .605 at the end?
Click to expand...
Click to collapse
The build identifiers work like this = 1.53.617.5 <--- current gen unlocked build.
1.53 = primary build ID
.617. = is the carrier specific ID
5 = minor build revision ID
You're partly right. A VZW build would look like (taken from an M9 build) 3.37.605.7 where .605. is the VZW carrier ID. More than likely when they release the update it'll be higher than 1.53.*.*
If you're stock recovery and system then you'll get an OTA notification from VZW whenever their updates are available. There may be an RUU available once the updates are pushed and settled.
The OTA will have a new radio, firmware and system updates for your carrier. You must use matching firmware/system build in order to get the best performance. The firmware is the hardware layer while the system is the software/OS layer.
You should not use new system with old firmware or new firmware with old system files.
Great. Thank you. That helps. I will wait patiently for HTC and Verizon to fix this issue.
Sent from my HTC6545LVW using Tapatalk
dn.lck said:
Great. Thank you. That helps. I will wait patiently for HTC and Verizon to fix this issue.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I know it's a tough spot and being patient can be hard.
I really don't think it'll be long before we see an update for you. The UK and US updates were about 3 weeks apart and we just got our US 1.53.* update a week or so ago. Give it a couple more weeks to pass the carrier approval stage and it'll get pushed out.
For sure, there will be an update. Try to be patient
dn.lck said:
Hi all,
I have a VZW 10 running 1.19. I'm interested in knowing if the connectivity issues, specifically Wi-Fi, have been fixed. The patch notes for 1.53 do address it, but has it been fixed.
I know there are workarounds, but this is a $550 phone. Wi-Fi should work out of the box.
Thanks for your help.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I haven't experienced this exact issue but what I have experienced as a general drop in signal strength on the 10. I have a side-by-side comparison of signal with my m9 versus the 10 and there's a big difference. I'm on prepaid service so I'm planning on switching to AT&T next month just to see if their service is any better. So far no one from T-Mobile has been able to tell me why my service is so bad considering I have two towers less than 1 mile away from where I live, and when I first started service with T-Mobile about five years ago it was fantastic but I would say in the last six months to a year it has started to go downhill
M9
http://dl-1.va.us.xda-developers.co....png?key=SvrxjxJxKPdYWm6IDOupUg&ts=1464048854
10
http://dl-1.va.us.xda-developers.co....png?key=vZKJ8ZMn6jtMzpo2mugVyw&ts=1464049167
Mark112887 said:
I haven't experienced this exact issue but what I have experienced as a general drop in signal strength on the 10. I have a side-by-side comparison of signal with my m9 versus the 10 and there's a big difference. I'm on prepaid service so I'm planning on switching to AT&T next month just to see if their service is any better. So far no one from T-Mobile has been able to tell me why my service is so bad considering I have two towers less than 1 mile away from where I live, and when I first started service with T-Mobile about five years ago it was fantastic but I would say in the last six months to a year it has started to go downhill
M9
http://dl-1.va.us.xda-developers.co....png?key=SvrxjxJxKPdYWm6IDOupUg&ts=1464048854
10
http://dl-1.va.us.xda-developers.co....png?key=vZKJ8ZMn6jtMzpo2mugVyw&ts=1464049167
Click to expand...
Click to collapse
Your answer is simple. It's T-Mobile
Refarmed network and spectrum.
datafoo said:
Your answer is simple. It's T-Mobile
Refarmed network and spectrum.
Click to expand...
Click to collapse
lol
My XL 32gig unlocked is coming in this Monday (originally Nov 18-21) . I have AT&T as my carrier and wanted to know how things are working with the pixel. Any comments ?concerns ?things to fix ?Please share .Thank You !
Sent from my SAMSUNG-SM-T817A using Tapatalk
Am I am using my unlocked one on AT&T and there are the typical minor annoyances... No HD Voice/VoLTE, no wifi calling, and no built in visual voicemail option in the pixel dialer. But those are AT&T's fault.. all of the mentioned things work fine with my Verizon sim...
crowsnestitsupport said:
Am I am using my unlocked one on AT&T and there are the typical minor annoyances... No HD Voice/VoLTE, no wifi calling, and no built in visual voicemail option in the pixel dialer. But those are AT&T's fault.. all of the mentioned things work fine with my Verizon sim...
Click to expand...
Click to collapse
Does AT&T have any plans to introduce the features you mentioned?
garyHal said:
Does AT&T have any plans to introduce the features you mentioned?
Click to expand...
Click to collapse
No. They wont for unlocked devices at all. If you want to use those features you would need to go to verizon or Tmobile.
If you use Google voice, you can have visual voicemail.
Sent from my Nexus 6P using Tapatalk
garyHal said:
Does AT&T have any plans to introduce the features you mentioned?
Click to expand...
Click to collapse
Been an AT&T customer a long time and I seriously doubt it... They enjoy screwing Android and unlocked phones in general and cater to iOS..... The only non AT&T Android phone that has VoLTE is the HTC 10. They have never given any of those features to any of the unlocked Nexus so it's a fair bet they won't on the pixel either..
mastaofdacat said:
My XL 32gig unlocked is coming in this Monday (originally Nov 18-21) . I have AT&T as my carrier and wanted to know how things are working with the pixel. Any comments ?concerns ?things to fix ?Please share .Thank You ! Sent from my SAMSUNG-SM-T817A using Tapatalk
Click to expand...
Click to collapse
I pulled my ATT SIM card out of my N6 and put it into my Pixel XL when it came on Thursday. I have only made a few phone calls, but haven't had any problems. I have used it to watch many Youtube videos off ATT data. I also use a ATT Microcell at home since I live off the beaten path and it connects to that without problems while at home.
The Pixel does check for tethering permissions once you insert an ATT SIM card. There is a hotspot / Verizon thread for the Pixel that talks about an easy work around for that. The main post is http://forum.xda-developers.com/showpost.php?p=69229666&postcount=35
drwx said:
If you use Google voice, you can have visual voicemail.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I always setup Google Voice on my phones. I don't use it for calling, but have it handle my voice mail to get Visual Voice mail. That and I have an old ATT 100 test messages for $5 plan so I do almost all of my texting through Google Voice.
I tested it with ATT with my 6p SIM. I then put the Project Fi car in the Pixel and the ATT back in the 6p. I am doing a test over the next few weeks with a trip to Germany, Sicily and then a 2,000 mile drive in the US from Maine to Texas. That should confirm the choice. In Maine, US Cellular beats ATT. In Texas I don't know.
I do have Google Voice but the uncertainty of android apps (ie: Hangouts being phased out, Google Voice app not being updated) wished there was something definitive to integrate with.
I've seen a few people say they got a system update after getting the phone. I have not seen one. Do I have what everyone else has?
Most likely those who bought unlocked version and activated on VZW.
VZW version is 012. All others are 010.
Here's the link to the full image. The last 3 digit only indicates which carries goes with. 010 is all other carriers, 011 is Telstra. There are 2 012, one for Rogers/Fido and one for Verizon.
mngdew said:
Most likely those who bought unlocked version and activated on VZW.
VZW version is 012. All others are 010.
Click to expand...
Click to collapse
I bought unlocked from Google store and activated on vzw..didnt get no updates
Using November for example, among others, there is the generic image and Verizon-specific image:
8.0.0 (OPD1.170816.025, Nov 2017)
8.0.0 (OPD3.170816.023, Nov 2017, Verizon)
Note the differences in build numbers. Pixel (1) and Pixel 2s also have similar branches.
I regularly switch SIMs and have always ran the non-Verizon build. In the current case, WiFi calling and enhanced LTE features all work fine.
Question: What do the Verizon builds include, or how are they different than the generic builds?
Also, are they meant for the VZ-branded Pixels or are they meant to be used with VZ SIMs, regardless of VZ-sold or Google-sold?
Lastly, are there differences in the packaged radio? (I can't download them to compare right now.)
Thanks.
That should be the only difference between the generic and the vzw specific images, the radio.
Lawlrus said:
That should be the only difference between the generic and the vzw specific images, the radio.
Click to expand...
Click to collapse
Do you or does anyone know the optimization/differences between the generic and VZ radio?
I wonder if it is better to run the VZ radio w/ other carriers or generic radio w/ VZ? I am running the generic radio w/ VZ now and it seems to work fine (as mentioned in OP). Since I switch to ATT and other carriers and back to VZ, it would be nice to know which radio would work better.
snovvman said:
Do you or does anyone know the optimization/differences between the generic and VZ radio?
I wonder if it is better to run the VZ radio w/ other carriers or generic radio w/ VZ? I am running the generic radio w/ VZ now and it seems to work fine (as mentioned in OP). Since I switch to ATT and other carriers and back to VZ, it would be nice to know which radio would work better.
Click to expand...
Click to collapse
Not sure it's listed anywhere what changes if any they make. I would assume that it would only really matter with their bands, which att does not use as vzw is still currently cdma.
Of all the years of using Nexus devices on vzw, I think an updated radio was an upgrade db wise one time. It's been worse more than better, and I can't remember the last time I updated a radio.
It's rare you can have other system issues from a non updated radio, but unless that happens, I'm a firm believer in not fixing what isn't broken.
I think the other consideration with the Vz version is updates, I wouldn't want Vz getting/delaying updates as you know they will and my understanding is Vz issues the updates for the Vz models.
Delete
SWBgHz said:
I think the other consideration with the Vz version is updates, I wouldn't want Vz getting/delaying updates as you know they will and my understanding is Vz issues the updates for the Vz models.
Click to expand...
Click to collapse
Verizon didn't delay or withhold any update for the original Pixels, what makes you think that they'll do it here? Everyone was delayed for the first update, but I believe Verizon users were the first to start getting the OTA en masse.
Sent from my Pixel 2 XL using Tapatalk
FWIW, I ordered directly from the Google store (the only way to order these devices, lol), and the moment I popped in a VZW SIM I had a 50-some MB update. Afterwards my build number shows the VZW build number per the Google factory images page. So it's clearly tied to SIM cards what it tries to put you on, and although I'm not sure what the difference between the normal and VZW builds are, Verizon delaying updates has nothing to do with it. That's only if you bought your phone through VZW that that would even be a possibility, and honestly they did pretty well with the OG Pixels, afaik
ohlin5 said:
FWIW, I ordered directly from the Google store (the only way to order these devices, lol), and the moment I popped in a VZW SIM I had a 50-some MB update. Afterwards my build number shows the VZW build number per the Google factory images page. So it's clearly tied to SIM cards what it tries to put you on, and although I'm not sure what the difference between the normal and VZW builds are, Verizon delaying updates has nothing to do with it. That's only if you bought your phone through VZW that that would even be a possibility, and honestly they did pretty well with the OG Pixels, afaik
Click to expand...
Click to collapse
I've read the same elsewhere--that the SIM determines the build. I wonder if before the next update, an ATT or TMo SIM is inserted, if the generic build will then be downloaded.
It would be nice to know if the VZ build adds something VZ specific for better support, but still works just the same with other carriers.
imnuts said:
Verizon didn't delay or withhold any update for the original Pixels, what makes you think that they'll do it here? Everyone was delayed for the first update, but I believe Verizon users were the first to start getting the OTA en masse.
Click to expand...
Click to collapse
Don't trust Verizon, plain and simple. 1000 reasons.
snovvman said:
I've read the same elsewhere--that the SIM determines the build. I wonder if before the next update, an ATT or TMo SIM is inserted, if the generic build will then be downloaded.
It would be nice to know if the VZ build adds something VZ specific for better support, but still works just the same with other carriers.
Click to expand...
Click to collapse
My guess would be that (at least Google store ordered devices) start with the generic build, and IF a VZW SIM is inserted then it downloads the differential (~50MB was what mine was) to adjust to the VZW build. I have no way of confirming this as I unfortunately didn't look at the build number prior to SIM insertion and update, but in my simple mind it seems like it could make sense I could be totally off though lol
ohlin5 said:
My guess would be that (at least Google store ordered devices) start with the generic build, and IF a VZW SIM is inserted then it downloads the differential (~50MB was what mine was) to adjust to the VZW build. I have no way of confirming this as I unfortunately didn't look at the build number prior to SIM insertion and update, but in my simple mind it seems like it could make sense I could be totally off though lol
Click to expand...
Click to collapse
Yeah, this is how it works. Multiple people have reported the same. As far as anyone can tell, the only difference between the VZW and the regular firmware is different modem and radio images.
Mine started with OPD1 build. First security update put me at an OPD3 build.
Yeah I don't think any of us are hundred percent sure on this. However I will tell you that I have an unlocked phone from the Google Play Store running on the Verizon network at first I sideload the official Google update and then Just For Kicks When I updated to the November version side-loaded the Verizon specific one. I don't know if it's truly an total but I do think that my network coverage has been maybe just a little bit better than it was previously. Could also be a placebo effect
I wonder if the last 2 Builds, which have separate builds for TMO, contain LTE Band 71...
So I just purchased a new pixel 2 XL, an I'm getting ready to update my phone to the latest 8.1 OTA firmware from Google developer section (pie looks to have too many problems that are unacceptable to me), and I'm seeing T-Mobile firmware. I am on T-Mobile in the US, but I'm wondering if this is firmware for European market or something weird.
Should I use the T-Mobile firmware, or the non-specified OTA?
Soured Lie said:
So I just purchased a new pixel 2 XL, an I'm getting ready to update my phone to the latest 8.1 OTA firmware from Google developer section (pie looks to have too many problems that are unacceptable to me), and I'm seeing T-Mobile firmware. I am on T-Mobile in the US, but I'm wondering if this is firmware for European market or something weird.
Should I use the T-Mobile firmware, or the non-specified OTA?
Click to expand...
Click to collapse
Go into settings/system/about phone. Look at the build number at the bottom. Choose the firmware that correspond with that number.
Eg: OPM2.
Chance Ill said:
Go into settings/system/about phone. Look at the build number at the bottom. Choose the firmware that correspond with that number.
Eg: OPM2.
Click to expand...
Click to collapse
Thank you for answering, unfortunately the only update that corresponds with OPD1 for my device is the firmware I am currently on. There are also multiple firmwares with the same date for other similar numbers (there is an OPD1 for Rogers, as well as one for Telstra and another with no signifier and so on). I'm not seeing anything that really correlates to my device in particular. Not for updates anyways. The build numbers have changed.
In my mind it is only logical that they have Google images and Verizon images as they never released model that was carrier specific outside of those two.
Soured Lie said:
Thank you for answering, unfortunately the only update that corresponds with OPD1 for my device is the firmware I am currently on. There are also multiple firmwares with the same date for other similar numbers (there is an OPD1 for Rogers, as well as one for Telstra and another with no signifier and so on). I'm not seeing anything that really correlates to my device in particular. Not for updates anyways. The build numbers have changed.
In my mind it is only logical that they have Google images and Verizon images as they never released model that was carrier specific outside of those two.
Click to expand...
Click to collapse
What model do you have? Verizon, Telstra, Rogers, etc
Chance Ill said:
What model do you have? Verizon, Telstra, Rogers, etc
Click to expand...
Click to collapse
I have an unlocked Google edition 2xl running on t-mobile network.
When did they ever make a Rogers or T-Mobile version?
Soured Lie said:
I have an unlocked Google edition 2xl running on t-mobile network.
When did they ever make a Rogers or T-Mobile version?
Click to expand...
Click to collapse
Some carriers like Verizon sell (not make) the Pixel thus the .img files correlates with that network for compatibility. I also use my device on T-Mobile US but us the OPM2 firmware because TMobile firmware (OPM4) caused modem issues
Chance Ill said:
Some carriers like Verizon sell (not make) the Pixel thus the .img files correlates with that network for compatibility. I also use my device on T-Mobile US but us the OPM2 firmware because TMobile firmware (OPM4) caused modem issues
Click to expand...
Click to collapse
I really appreciate your help. I am on stock firmware and have really good connectivity, so I think I'll do what you have done and stick to similar firmware.
I have one last question. I'm about to sideloaded this, the instructions say to make sure there are no pending updates before proceeding. I have pending pie update which I have not downloaded, is this going to cause issues? I can't see why it would. I guess at worst it will reject my sideloaded at worst if it was expecting something else?
Soured Lie said:
I really appreciate your help. I am on stock firmware and have really good connectivity, so I think I'll do what you have done and stick to similar firmware.
I have one last question. I'm about to sideloaded this, the instructions say to make sure there are no pending updates before proceeding. I have pending pie update which I have not downloaded, is this going to cause issues? I can't see why it would. I guess at worst it will reject my sideloaded at worst if it was expecting something else?
Click to expand...
Click to collapse
As long as you haven't downloaded the ota, you should be fine.
Chance Ill said:
As long as you haven't downloaded the ota, you should be fine.
Click to expand...
Click to collapse
Already updated. Everything is smooth so far. Thank you for taking the time to help. I used to make ROMs when ICS was out, but everything has changed. Partition scheming and the whole 9. I'm a newbie all over again. I forgot how much I enjoyed Android. Very liberating after being on iOS for so long. Anyhow, have a good day.
Soured Lie said:
Already updated. Everything is smooth so far. Thank you for taking the time to help. I used to make ROMs when ICS was out, but everything has changed. Partition scheming and the whole 9. I'm a newbie all over again. I forgot how much I enjoyed Android. Very liberating after being on iOS for so long. Anyhow, have a good day.
Click to expand...
Click to collapse
Lol. Yeah, much has changed since the good ole days. Welcome home! ?
Can some one confirm what OTA should I download for T-Mobile US on Pixel XL 2 for 9.0 ? Thank you
The one NOT for Telstra.
I'm hoping they release an update for TMobile. I'm having serious signal issues since moving to Pie... Once the signal drops a bit I immediately drop to 3G or even H+... Never had that issue with the TMobile release for Oreo.