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...
Related
Hello all,
I'm just wondering, do you guys notice or know of any real difference b/t the unlocked/non-carrier firmware that's out there and the carrier-specific firmware from T-Mobile for the M8? Is one considered better than the other?
Please share your thoughts with us!
Thank You,
RockStar2005
RockStar2005 said:
Hello all,
I'm just wondering, do you guys notice or know of any real difference b/t the unlocked/non-carrier firmware that's out there and the carrier-specific firmware from T-Mobile for the M8? Is one considered better than the other?
Please share your thoughts with us!
Thank You,
RockStar2005
Click to expand...
Click to collapse
Non carrier get updates faster (wwe) and carrier specific tend to need to wait sometime for the lastest update. Correct me if I'm wrong haha. But carrier specific usually comes with bloatware .
Sent from my HTC ONE M8 HK
Steven How said:
Non carrier get updates faster (wwe) and carrier specific tend to need to wait sometime for the lastest update. Correct me if I'm wrong haha. But carrier specific usually comes with bloatware .
Sent from my HTC ONE M8 HK
Click to expand...
Click to collapse
That's correct. In case of the TMOB M8 (as I got this) the EPSM was missing even after the OTA to 1.70.111.x. so I decided to change CID/MID to WWE and reverted my M8 to the WWE variant using a stock backup as well as the FW of 2.22.401.4. Now all is fine and lately I even received the OTA "2.22.401.4 > 2.22.401.5" containing a GPS fix.
Sent from my HTC One_M8 using XDA Free mobile app
RockStar2005 said:
Hello all,
I'm just wondering, do you guys notice or know of any real difference b/t the unlocked/non-carrier firmware that's out there and the carrier-specific firmware from T-Mobile for the M8? Is one considered better than the other?
Please share your thoughts with us!
Thank You,
RockStar2005
Click to expand...
Click to collapse
If you are talking about Firmware as in files in firmware.zip
ie
hboot
radio.img
modem_st1.img
rcdata.img
rconfig.img
rpm.img
etc......
then
radio is different for every major carrier which enables or disables specific radio bands.
true for US region.
Steven How said:
Non carrier get updates faster (wwe) and carrier specific tend to need to wait sometime for the lastest update. Correct me if I'm wrong haha. But carrier specific usually comes with bloatware .
Sent from my HTC ONE M8 HK
Click to expand...
Click to collapse
I see.
Well I know the phones come with bloatware vs unlocked/international ones......... but the firmware comes with it too? lol
RockStar2005
HTCNerdYoda said:
That's correct. In case of the TMOB M8 (as I got this) the EPSM was missing even after the OTA to 1.70.111.x. so I decided to change CID/MID to WWE and reverted my M8 to the WWE variant using a stock backup as well as the FW of 2.22.401.4. Now all is fine and lately I even received the OTA "2.22.401.4 > 2.22.401.5" containing a GPS fix.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Hello again HTC,
What's EPSM? And WWE?
Wow really?? The T-Mobile OTA was actually missing stuff the non-carrier one wasn't?? That's crazy. And here I was asking this cuz I was worried that by downloading the non-carrier variant of the firmware that I was perhaps missing things my phone would need to work at optimal level. Sounds like it's actually the opposite! lol I use the ViperOne M8 rom by Team Venom and they're VERY good about including all the important M8 updates for my phone (and some nice extras, like letting notif light still blink while charging for new msgs, turning off annoying high volume warning, etc), and they seem to have them out before T-Mobile does (see below). Yeah the newest firmware I got (not from Venon, but from here: http://www.renovate-themes.de/index.php?s=firmware) was necessary for Venom's OTA to work, but I did notice that when I finally got Venom's OTA that it mentioned a GPS fix too, so they got that in there as well.
I just wish T-Mobile would hurry up and get VoLTE activated for the M8. I know it's capable of VoLTE, but an OTA will be needed to activate it. Once it's activated, and ur in a VoLTE-activated area/city, the calls won't revert back to 4G but instead will stay at 4G LTE, and will be better quality and less likely to drop.
ViperOne prob beat T-Mo by 2 days on that GPS fix, but in reality, from what u said, I dunno if T-Mo's even has it yet or not(?) as it's not mentioned in their super vague description:
ViperOneM8 2.2.0 (August 19)
ADDED full T-Mobile carrier support
FIXED T-Mobile WIFI calling
FIXED Locked IPV4/6 Settings
FIXED AOSP incoming call workaround not working
ViperOneM8 2.1.0 (August 16)
Merged with HTC OTA 2.22.401.5
Added new stock kernel from OTA (Only full ROM)
GPS improvements and fixes from HTC
Workaround white gap in dialer when having custom stock navbar size
Fixed Notification icon color
Added longpress power custom actions
vs. T-Mobile:
Beginning August 18, the HTC One (M8) received a software update 2.22.531.5 (or firmware 2.22.401.4 or .5?).
Software version
Android version 4.4.3/ Software 2.22.531.5- Current version
Version
Android version 4.4.3/Software 2.22.531.5
Approved 08/18/14
Features
User experience improvements
Prerequisites
Device software is not rooted
50% battery life
Wi-Fi connection
And I can't even confirm if T-Mobile actually deployed it to my area on the 18th or not as I've been on ViperOne for weeks now, and so because of that, I wouldn't get the OTA notification anymore.
RockStar2005
smokin901 said:
If you are talking about Firmware as in files in firmware.zip
ie
hboot
radio.img
modem_st1.img
rcdata.img
rconfig.img
rpm.img
etc......
then
radio is different for every major carrier which enables or disables specific radio bands.
true for US region.
Click to expand...
Click to collapse
Smokin,
Ok. I'm just trying to pinpoint the pros and cons of downloading firmware or even regular OTA updates on a T-Mobile M8 vs a non-carrier specific M8. I def get that the radio bands will differ from one carrier to the next, but is there any gain or loss of quality etc in downloading a carrier-specific firmware or OTA, or no difference at all? The posts so far have suggested a difference in favor of the non-carrier versions.
RockStar2005
RockStar2005 said:
Hello again HTC,
What's EPSM? And WWE?
Wow really?? The T-Mobile OTA was actually missing stuff the non-carrier one wasn't?? That's crazy.
Click to expand...
Click to collapse
Actually I think it is very sad that those things were still missing, when I debranded mine, as all non-carrier devices got the EPSM with the day one update to give an example.
RockStar2005 said:
T-Mobile:
Beginning August 18, the HTC One (M8) received a software update 2.22.531.5 (or firmware 2.22.401.4 or .5?).
Software version
Android version 4.4.3/ Software 2.22.531.5- Current version
Version
Android version 4.4.3/Software 2.22.531.5
Approved 08/18/14
Features
User experience improvements
Prerequisites
Device software is not rooted
50% battery life
Wi-Fi connection
Click to expand...
Click to collapse
And reading the quote above I wouldn't put my ass on the line that the GPS fix realy is inclueded.
But maybe some T-MOB101 users could tell if this update finally got the EPSM, as well as the GPS fix!?
HTCNerdYoda said:
Actually I think it is very sad that those things were still missing, when I debranded mine, as all non-carrier devices got the EPSM with the day one update to give an example.
And reading the quote above I wouldn't put my ass on the line that the GPS fix realy is inclueded.
But maybe some T-MOB101 users could tell if this update finally got the EPSM, as well as the GPS fix!?
Click to expand...
Click to collapse
I see. But what's EPSM though? And WWE? Not sure I'm following on the "day one update"......do u mean the non-carrier devices got EPSM on the same day it was set to be released?
Yeah........ I mean, the carriers deploy the updates by regions over a set period of time. And note that it was APPROVED on August 18th by T-Mobile. I don't know if that was the same date they started deploying or not too. And since their description is so vague, I again can't say if that GPS fix was included or not. To me, the GPS on phones still aren't 100% perfect, so ANY fix that a company (phone maker or even carrier) can put out there that improves GPS quality is important. Just 2 weeks ago my GPS SLIGHTLY took me off course until I reset my phone, then all was fine. Wasted about 10 minutes of my time because of it. Not a big deal, but still relevant. Maybe had I already had that fix back then that wouldn't have happened? I mean, u still should reset your phone once or twice a week anyway I think, but these fixes help increase the chance of success w/o HAVING to reboot.
RockStar2005
RockStar2005 said:
I see. But what's EPSM though? And WWE? Not sure I'm following on the "day one update"......do u mean the non-carrier devices got EPSM on the same day it was set to be released?
Yeah........ I mean, the carriers deploy the updates by regions over a set period of time. And note that it was APPROVED on August 18th by T-Mobile. I don't know if that was the same date they started deploying or not too. And since their description is so vague, I again can't say if that GPS fix was included or not. To me, the GPS on phones still aren't 100% perfect, so ANY fix that a company (phone maker or even carrier) can put out there that improves GPS quality is important. Just 2 weeks ago my GPS SLIGHTLY took me off course until I reset my phone, then all was fine. Wasted about 10 minutes of my time because of it. Not a big deal, but still relevant. Maybe had I already had that fix back then that wouldn't have happened? I mean, u still should reset your phone once or twice a week anyway I think, but these fixes help increase the chance of success w/o HAVING to reboot.
RockStar2005
Click to expand...
Click to collapse
EPSM is the ExtremePowerSavingMode introduced by HTC and yes the update came out on the day the One M8 got released. At least it did for the WWE (World Wide English) variants of the HTC - which are the official HTC variants without any - if just like here - software branding by the providers.
In my opinion that's what leeds to long period between HTC own OTAs and carrier OTAs of any smartphone. The carriers - be it T-Mobile, Vodafone or some others - try to integrate their own bloatware into those updates. T-Mob e.g. says there are still issues with the EPSM, but asking me those problems are likely to be triggered by T-Mobiles own bloatware.
And well fixes for e.g. GPS just arrive much later on carrier-branded devices ....
RockStar2005 said:
Smokin,
is there any gain or loss of quality etc in downloading a carrier-specific firmware or OTA, or no difference at all?
Click to expand...
Click to collapse
Quality of what? It seems like a very subjective question. Fixes and other updates are almost always going to come out sooner on the "international" unbranded version. That much is "better". But some folks like carrier-specific features. For example, doesn't T-Mob have WiFi calling? Some AT&T folks like Visual Voicemail and ISIS (payment system), while I (just personally) can care less for such things.
As far as band support, having your carrier's radio (or one that is at least compatible with your carrier) plus the custom ROM of your choice should take care of any band compatibility issues.
HTCNerdYoda said:
EPSM is the ExtremePowerSavingMode introduced by HTC and yes the update came out on the day the One M8 got released. At least it did for the WWE (World Wide English) variants of the HTC - which are the official HTC variants without any - if just like here - software branding by the providers.
In my opinion that's what leeds to long period between HTC own OTAs and carrier OTAs of any smartphone. The carriers - be it T-Mobile, Vodafone or some others - try to integrate their own bloatware into those updates. T-Mob e.g. says there are still issues with the EPSM, but asking me those problems are likely to be triggered by T-Mobiles own bloatware.
And well fixes for e.g. GPS just arrive much later on carrier-branded devices ....
Click to expand...
Click to collapse
Yoda,
Oh yeah........ ok, EPSM. Got it. Yeah that came out weeks later on T-Mobile, but ok that's cool that HTC released it the same day the M8 was released. Yeah, I guess that makes sense b/c they're adding more into it, but not anything important. But I'm still not getting how bloatware fits in to the firmware? I understand bloatware like all the T-Mobile-specific apps that come with the phone, but what bloatware comes in the updates??
Yeah that's definitely a possibility........... like perhaps certain parts of their "firmware bloatware" are interfering or not compatible with the EPSM.
Well that's not good. Those fixes should be deployed before anything else. Google Maps is only as good as the phone's GPS capabilities.
Thanks,
RockStar2005
RockStar2005 said:
Yoda,
Oh yeah........ ok, EPSM. Got it. Yeah that came out weeks later on T-Mobile, but ok that's cool that HTC released it the same day the M8 was released. Yeah, I guess that makes sense b/c they're adding more into it, but not anything important. But I'm still not getting how bloatware fits in to the firmware? I understand bloatware like all the T-Mobile-specific apps that come with the phone, but what bloatware comes in the updates??
Yeah that's definitely a possibility........... like perhaps certain parts of their "firmware bloatware" are interfering or not compatible with the EPSM.
Well that's not good. Those fixes should be deployed before anything else. Google Maps is only as good as the phone's GPS capabilities.
Thanks,
RockStar2005
Click to expand...
Click to collapse
You're welcome RockStar!
Firmware (such as ICS, Jelly Bean, KitKat) on your phone is the core system. The ROM IS just the OS on top of it. But the OS is configured to perform with a specific core, meaning that a carrier OS version is programmed to work with a specially designed firmware. Thus firmware for e.g. a T-Mobile ROM (OS) is a little bit altered compared to the one for a pure HTC ROM, as it has to fit the ROM altered by T-Mobile.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
You're welcome RockStar!
Firmware (such as ICS, Jelly Bean, KitKat) on your phone is the core system. The ROM IS just the OS on top of it. But the OS is configured to perform with a specific core, meaning that a carrier OS version is programmed to work with a specially designed firmware. Thus firmware for e.g. a T-Mobile ROM (OS) is a little bit altered compared to the one for a pure HTC ROM, as it has to fit the ROM altered by T-Mobile.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yoda,
I see. Well right now I use ViperOne M8, and although the last firmware was from T-Mo, the one I just got (2.22) was not carrier-specific (http://www.renovate-themes.de/index.php?s=firmware). Though I believe ViperOne M8 is designed to be compatible with all variants?
I see what you're saying better now, but I don't know if I'd call the T-Mobile firmware & ROM "bloatware". But I guess to really know how to refer to it, I'd have to ask: What kind of changes do they make to the carrier one?
Thanks,
RockStar2005
RockStar2005 said:
Yoda,
I see. Well right now I use ViperOne M8, and although the last firmware was from T-Mo, the one I just got (2.22) was not carrier-specific (http://www.renovate-themes.de/index.php?s=firmware). Though I believe ViperOne M8 is designed to be compatible with all variants?
I see what you're saying better now, but I don't know if I'd call the T-Mobile firmware & ROM "bloatware". But I guess to really know how to refer to it, I'd have to ask: What kind of changes do they make to the carrier one?
Thanks,
RockStar2005
Click to expand...
Click to collapse
Yes, the one you got is the WWE firmware. And yes again, ViperOne works with most 2.22.xxx.x firmwares, but is build upon 2.22.401.5.
Changes are as @redpoint73 already said e.g. Wifi calling in case of the T-Mobile firmware.
redpoint73 said:
Quality of what? It seems like a very subjective question. Fixes and other updates are almost always going to come out sooner on the "international" unbranded version. That much is "better". But some folks like carrier-specific features. For example, doesn't T-Mob have WiFi calling? Some AT&T folks like Visual Voicemail and ISIS (payment system), while I (just personally) can care less for such things.
As far as band support, having your carrier's radio (or one that is at least compatible with your carrier) plus the custom ROM of your choice should take care of any band compatibility issues.
Click to expand...
Click to collapse
Red,
I just meant quality of how the phone interacts with the network, etc.
Yes that is true. Though ROMs like the one I have, ViperOne M8, have managed to include things like Wi-Fi Calling in their options. Since ViperOne is fully compatible with T-Mobile M8s, and they have been good about offering the same things T-Mo does, then it seems to be all good. I think Six was just saying it's really only an issue when you use one carrier's phone on another carrier's network.
Thanks,
RockStar2005
HTCNerdYoda said:
Yes, the one you got is the WWE firmware. And yes again, ViperOne works with most 2.22.xxx.x firmwares, but is build upon 2.22.401.5.
Changes are as @redpoint73 already said e.g. Wifi calling in case of the T-Mobile firmware.
Click to expand...
Click to collapse
Yoda,
Ok. I just said int'l, but I guess WWE is the same thing. Good to know.
Yeah. ViperOne didn't have Wi-Fi Calling for a lil while but as of last week the most recent update re-enabled it on my M8. I never use it though b/c it totally blocks incoming/outgoing MMS (though not regular SMS) messages. Even one customer service rep lady at T-Mobile told me she has the same issue, and has for years. I would only use it if I was in another country and wanted to make a free call and had access to Wi-Fi. But I'd shut it off the second I was done with that call. lol
Thanks,
RockStar2005
RockStar2005 said:
Red,
I just meant quality of how the phone interacts with the network, etc.
Click to expand...
Click to collapse
Its not normally a function of the ROM. As long as you are on a T-Mob compatible radio, it shouldn't matter what ROM you are on.
Although there is the other complication that has been mentioned: with any 2.xx based custom ROM (ViperOne included) you need to be using updated firmware (not to be confused with the ROM). So you will want a firmware that plays well with the 2.xx ROM, and one that plays well with T-Mobile's network.
---------- Post added at 03:33 PM ---------- Previous post was at 03:26 PM ----------
RockStar2005 said:
the one I just got (2.22) was not carrier-specific (http://www.renovate-themes.de/index.php?s=firmware). Though I believe ViperOne M8 is designed to be compatible with all variants?
Click to expand...
Click to collapse
2.22.401 firmware is for the unbranded "international" variant. Its not specifically designed for use in the US, and at least for AT&T, it has caused reception issues from dodgy reception, to no service whatsoever (solution was to flash 2.22.1540 firmware). So not sure how this will play out on the T-Mob network.
Best bet would be to flash the firmware from the new T-Mob OTA rolling out, but I don't think its been posted here yet.
Yeah, though I was referring more to the firmware than the ROM.
Yes..... true. Yeah the firmware is just the various data and ROM is like the interface. I believe the 2.22.401.5 firmware is fully compatible. If you believe it's not, please let me know.
---------- Post added at 03:33 PM ---------- Previous post was at 03:26 PM ----------
[/COLOR]
2.22.401 firmware is for the unbranded "international" variant. Its not specifically designed for use in the US, and at least for AT&T, it has caused reception issues from dodgy reception, to no service whatsoever (solution was to flash 2.22.1540 firmware). So not sure how this will play out on the T-Mob network.
Best bet would be to flash the firmware from the new T-Mob OTA rolling out, but I don't think its been posted here yet.[/QUOTE]
The firmware I have is 2.22.401.5. And ViperOne M8 offers (using 2.22.401.5 as a base) full T-Mo functionality:
ViperOneM8 2.2.0 (August 19)
ADDED full T-Mobile carrier support
FIXED T-Mobile WIFI calling
FIXED Locked IPV4/6 Settings
FIXED AOSP incoming call workaround not working
ViperOneM8 2.1.0 (August 16)
Merged with HTC OTA 2.22.401.5
Added new stock kernel from OTA (Only full ROM)
GPS improvements and fixes from HTC
Workaround white gap in dialer when having custom stock navbar size
Fixed Notification icon color
Added longpress power custom actions
So after reading that, would you say I'm at the equivalent of T-Mo's OTA, or T-Mo's is still better? I just hate waiting on T-Mo, esp if their OTAs are not perfect either (see Yoda's posts in this thread). Team Venom (who makes ViperOne) has told me they base their updates on T-Mobile's, but tweak them to work better with ViperOne. So I guess their's aren't pure HTC either. lol
Thank You,
RockStar2005
I have a TMO version of the M8 and was curious about the importance of firmware versions when using custom ROMs. I notice that all the ROMs are based on firmware version 3.28.401.9, but the latest TMO version is 3.32.531.2. Am I correct in assuming that the TMO, being that it has a higher number, contains the same, or newer, changes/fixes that the other firmware contains? If so, why don't they base it on the higher one instead? Also, is there any benefit for me to use the firmware that the ROMs are based on?
There isn't a clear cut answer on this. Yes, technically the higher software/firmware number (firmware itself does not really have a "number" but we merely associate it with the software that it deployed with) the "newer" it is. But it just might be carrier specific changes, and often there are no significant upgrades beyond that (for versions numbers that are close together). I'm no dev, and can't really speak for them. But my hunch would be that its usually preferable to base a custom ROM on an unbranded base, as too much carrier meddling can cause some issues and headaches (and I've seen this problem rear its head on previous devices).
I'd tend to suggest that using the firmware for your carrier/region is best. But this might not be the best for everyone, everywhere. And there is even some trial and error involved.
redpoint73 said:
There isn't a clear cut answer on this. Yes, technically the higher software/firmware number (firmware itself does not really have a "number" but we merely associate it with the software that it deployed with) the "newer" it is. But it just might be carrier specific changes, and often there are no significant upgrades beyond that (for versions numbers that are close together). I'm no dev, and can't really speak for them. But my hunch would be that its usually preferable to base a custom ROM on an unbranded base, as too much carrier meddling can cause some issues and headaches (and I've seen this problem rear its head on previous devices).
I'd tend to suggest that using the firmware for your carrier/region is best. But this might not be the best for everyone, everywhere. And there is even some trial and error involved.
Click to expand...
Click to collapse
@tkoreaper
The different numbers are a CDMA vs GSM thing.
The 328 is GSM, 332 is CDMA.
T-Mo is CDMA.
xunholyx said:
@tkoreaper
The different numbers are a CDMA vs GSM thing.
The 328 is GSM, 332 is CDMA.
T-Mo is CDMA.
Click to expand...
Click to collapse
Ummm, no... TMO and AT&T are GSM. Sprint and VZ are CDMA. TMO is the only one with 3.32 I believe.
tkoreaper said:
Ummm, no... TMO and AT&T are GSM. Sprint and VZ are CDMA. TMO is the only one with 3.32 I believe.
Click to expand...
Click to collapse
Okay. I'm mistaken. I'm not American. But, the latest GSM firmware is the .9
Americans are weird.
I knew AT&T was GSM, but always thought T-mo wasn't. Thanks for correcting me.
Perhaps it's a WWE thing? I'm newish to HTC. Well......maybe 5 months isn't exactly new, but HTC is sure a lot different than Samsung.
EDIT: If you can wait till tomorrow, I can get a solid answer to this. My HTC firmware expert guy is in Germany and probably sleeping right now.
He'll have a definitive answer that I can pass along.
xunholyx said:
Okay. I'm mistaken. I'm not American. But, the latest GSM firmware is the .9
Americans are weird.
Click to expand...
Click to collapse
Firmware/software numbers are always chronological. 3.32.531.2 is newer than 3.28.401.9. But whether there are any significant software changes beyond carrier customizations, is the question. Or for that matter, if the firmware is even different.
redpoint73 said:
Firmware/software numbers are always chronological. 3.32.531.2 is newer than 3.28.401.9. But whether there are any significant software changes beyond carrier customizations, is the question. Or for that matter, if the firmware is even different.
Click to expand...
Click to collapse
But that wasn't the case with the WWE vs T-Mobile(Poland). WWE International was 1.54.401.x T-Mobile was 1.57.118.x <But didn't even have the extreme power saving mode.
It could probably be argued that carriers add their own number there for their changes, then again, the unbranded Asian(Hong Kong) variant also uses 3.32.xxx.x . Don't know why they number it that way, but it doesn't necessarily mean it's "newer" or "better" (Like the T-Mobile vs WWE example).
O2, 3, T-Mobile, AT&T, Bell, Telus/Rogers they all use different numbers there.
BerndM14 said:
But that wasn't the case with the WWE vs T-Mobile(Poland). WWE International was 1.54.401.x T-Mobile was 1.57.118.x <But didn't even have the extreme power saving mode.
Click to expand...
Click to collapse
Are you saying that 1.57 came out before 1.54?
BerndM14 said:
It could probably be argued that carriers add their own number there for their changes, then again, the unbranded Asian(Hong Kong) variant also uses 3.32.xxx.x .
Click to expand...
Click to collapse
Carriers don't make any of the updates. They all come from HTC, based on customizations directed by the carrier.
redpoint73 said:
Are you saying that 1.57 came out before 1.54?
Click to expand...
Click to collapse
Of course not. But what exactly about that update was newer/better than what we got from the 1.54 ?
That's what makes the way they number these software versions so strange. Even though it's logical that a move from 3.28 to 3.57(For example) would mean a newer version with improvements, it was definitely not the case for T-Mobile(Poland) by being on 1.57 vs our 1.54.
Then of course the International Version got the 3.28 much sooner than the Dev edition yet the Dev edition is also 3.28 where as the Bell release that came out recently is 3.34 yet the update is the same as the one we got on International/Dev Edition with the exception of carrier bloated nonsense and changes.
That's why I say it's a weird way to number the software, they could all have rolled out as 3.28 and just have the x.xx.region-code.x be different.
Carriers don't make any of the updates. They all come from HTC, based on customizations directed by the carrier.
Click to expand...
Click to collapse
Oh ok, I figured that HTC creates the package for the carrier, sends it over to them, they make any local changes they want and then roll out the package to their customers. Thought that they would then "change" the software number based on their own structure/build.
BerndM14 said:
Of course not. But what exactly about that update was newer/better than what we got from the 1.54 ?
Click to expand...
Click to collapse
I never said anything was "better". Newer doesn't always mean better. The fact the "newer" software is not necessarily better is exactly the point I've been trying to make.
A "newer" software may even be worse. For instance, AT&T released 4.4.3 later than most other versions (version 2.23). But suffered a power drain bug (that I don't believe other versions suffered) and was subsequently pulled.
I still believe that the higher firmware number is "newer". But that "new" may just mean carrier customizations, as I mentioned several times already. If they make any changes, they use a different software number, a number higher than the last one they used. Just normal software version control.
Of course, there are other variables at play that may affect version number vs. release date. A software version might get sent over to the carrier and be delayed in testing for months (AT&T is notorious for this) and other software might get released on other carriers in the meantime.
redpoint73 said:
I never said anything was "better". Newer doesn't always mean better. The fact the "newer" software is not necessarily better is exactly the point I've been trying to make.
I still believe that the higher firmware number is "newer". But that "new" may just mean carrier customizations, as I mentioned several times already. If they make any changes, they use a different software number, a number higher than the last one they used. Just normal software version control.
Of course, there are other variables at play that may affect version number vs. release date. A software version might get sent over to the carrier and be delayed in testing for months (AT&T is notorious for this) and other software might get released on other carriers in the meantime.
Click to expand...
Click to collapse
Exactly, I didn't make my post to argue against your point, I made it to show the OP that a higher number doesn't necessarily mean it's "better" or perhaps, contradictory as it sounds, "newer". Hence why I used the T-Mobile(Poland) roll-out as an example.
It must be carrier specific though(to some extent at least).
20 October , Vodafone roll out 3.29.161.5 342.4 MB
21 October , T-Mobile roll out 3.32.111.3 361.79 MB
The same update, HTC Eye, Face Tracking, Split Capture etc, file sizes differ by a rather big amount and it was only 1 day difference, yet there was a couple of days between International and Dev and it still had the same roll out version 3.28. Which is why I figured that even though the number might be higher it was more to do with carriers. Perhaps it's also linked to something else at HTC's side for releasing builds don't know... Either way though.
Was just trying to point out that it doesn't necessarily mean that his 3.32 is "newer" than the 3.28. Why the developers use the 3.28.401.x as their base is also not known to me, perhaps just easier that way.
Anyways...
BerndM14 said:
It must be carrier specific though(to some extent at least).
Click to expand...
Click to collapse
It seems to me that the number after the second decimal is carrier/region specific. The numbers before that are the main "version" number, and a minor change will increase the last number.
BerndM14 said:
Was just trying to point out that it doesn't necessarily mean that his 3.32 is "newer" than the 3.28.
Click to expand...
Click to collapse
I still think it does (aside from some variables like carrier delay, like I mentioned). Newer, but not by any means necessarily better.
BerndM14 said:
Why the developers use the 3.28.401.x as their base is also not known to me, perhaps just easier that way.
Click to expand...
Click to collapse
Every ROM and situation is different. But unbranded is often the best base for a custom ROM. I've seen carrier customizations cause havoc when used as a base for custom ROMs.
How is the nexus 5X on Verizon? I'm coming from the HTC One M8, and I've never had an unlocked phone before. Since the M8 has a nano sim i've heard that you can just pop it in the 5X and be up and running.
I've found no issue with my 5X on Verizon. I was previously using a 2013 Moto X so I simply removed the nano SIM from my Moto X and popped it into my 5X. It connected right up to Verizon's network and I was able to make/receive calls and use the Internet as expected. I've not attempted to setup HD Voice or simultaneous voice/data - but it's currently doing everything my Moto X was doing before the SIM swap.
Came from an S6, and I've had no issues so far. Just popped my nano sim in and I was up and running. There's an option under Cellular Network Settings called Enhanced 4G LTE Mode, which activates VoLTE and it works great. Only thing I've noticed is that it looks like VZW is blocking the latest OTA's...they can easily be sideloaded, but it's still annoying.
Mine works perfectly, in fact data has been more consistent than my old phone I bought that was locked to verizon. I did have to get a new sim card but I got it set up and it hasn't had any problems whatsoever.
I was trying 5x and moto x pure (2015) side by side and moto x reported better signal consistently. I even RMAed the 5x thinking there was a hardware issue, but the second unit had similar signal strength.
The moto x was on lollipop so there could have been a difference in the reporting of signal ? (Not sure) But the 5x did however drop to 3g more often than the moto x, but the 5x quickly regained lte.
Sent from my Nexus 5X using Tapatalk
Thanks for the feedback everyone! My 5X should arrive in a few days, can't wait lol
So Verizon is no longer blocking any phone that has an ESN that isn't in their system already?
Correct
I'm on my 3rd device now on vzw. My problem has been 100% software however. The phone has struggled and failed to receive mms (primarily group messaging) on both previous devices. On the device I got today I didn't insert my sim until the device was set up and the device had an OTA waiting. I installed the software update and viola, no more mms problems. It is worth noting that my previous device was on an older build and reported no updates so I would recommend setting up on WiFi before popping the sim in
Ok so I have never owned a Nexus device but am seriously thinking about replacing my Moto X 2014 with a 5X. This may be a dumb question but does buying the 5X for use on Verizon result in any of the crappy lockdowns/restrictions/bloatware from Verizon ending up on the phone? I ask because even though I bought my MX14 (not an upgrade) directly from Moto it still ended up with vzw bloatware, no tethering, no updates etc. due to it being a Verizon device. Are the Nexus phones "immune" to this? After the Verizon/Moto flap over not updating the MX14 I am looking for a phone that will get updates and bug fixes in a timely manner not whenever Verizon feels like it.
JoeHockey said:
Ok so I have never owned a Nexus device but am seriously thinking about replacing my Moto X 2014 with a 5X. This may be a dumb question but does buying the 5X for use on Verizon result in any of the crappy lockdowns/restrictions/bloatware from Verizon ending up on the phone? I ask because even though I bought my MX14 (not an upgrade) directly from Moto it still ended up with vzw bloatware, no tethering, no updates etc. due to it being a Verizon device. Are the Nexus phones "immune" to this? After the Verizon/Moto flap over not updating the MX14 I am looking for a phone that will get updates and bug fixes in a timely manner not whenever Verizon feels like it.
Click to expand...
Click to collapse
I don't know that I would say it is "immune"; but I initially used my 5X on Verizon, and I do not recall any of the Verizon-related apps being installed on my 5X.
JoeHockey said:
Ok so I have never owned a Nexus device but am seriously thinking about replacing my Moto X 2014 with a 5X. This may be a dumb question but does buying the 5X for use on Verizon result in any of the crappy lockdowns/restrictions/bloatware from Verizon ending up on the phone? I ask because even though I bought my MX14 (not an upgrade) directly from Moto it still ended up with vzw bloatware, no tethering, no updates etc. due to it being a Verizon device. Are the Nexus phones "immune" to this? After the Verizon/Moto flap over not updating the MX14 I am looking for a phone that will get updates and bug fixes in a timely manner not whenever Verizon feels like it.
Click to expand...
Click to collapse
I just received my N5X yesterday and activated it on Verizon. Since it is the exact same phone that is used for all carriers, there is not a single app related to Verizon pre-installed on this thing.
I turned it on and got an update prompt as soon as I got to the home screen, but I wanted to manually flash the latest release anyways so I didn't bother to see what version it was trying to upgrade me to.
With the Nexus devices, Google will release the updates publicly, so I would recommend learning how to apply them yourself rather than waiting for an OTA on the phone.
cambunch said:
I just received my N5X yesterday and activated it on Verizon. Since it is the exact same phone that is used for all carriers, there is not a single app related to Verizon pre-installed on this thing.
I turned it on and got an update prompt as soon as I got to the home screen, but I wanted to manually flash the latest release anyways so I didn't bother to see what version it was trying to upgrade me to.
With the Nexus devices, Google will release the updates publicly, so I would recommend learning how to apply them yourself rather than waiting for an OTA on the phone.
Click to expand...
Click to collapse
Not taking OTA updates is an interesting thought. That would not have occurred to me. Do the OTA's come from Google or VZW?
JoeHockey said:
Not taking OTA updates is an interesting thought. That would not have occurred to me. Do the OTA's come from Google or VZW?
Click to expand...
Click to collapse
The OTAs would come from Google. Verizon is very hands-off on this device (they don't even have a thumbnail image for it under your account page on their website).
JoeHockey said:
This may be a dumb question but does buying the 5X for use on Verizon result in any of the crappy lockdowns/restrictions/bloatware from Verizon ending up on the phone? I ask because even though I bought my MX14 (not an upgrade) directly from Moto it still ended up with vzw bloatware, no tethering, no updates etc. due to it being a Verizon device. Are the Nexus phones "immune" to this?
Click to expand...
Click to collapse
You'd order the 5X from Google (or whoever) and it will be the general U.S. device -- same one you would use on AT&T, etc. All you need to do is put a VZW nano sim w/ NFC in it (either a preexisting one you have, or a corporate store will give you one for free if you are a current customer). So, there will be no pre-installed VZW bloat. The only thing I would be careful of is the Play Store -- it will have a record of all prior apps installed, some of which (unless your remove them from your account history) will be VZW bloat. I would be careful to set up your phone as a new device during initial set up and also be careful about what you allow the Play Store to do automatically. Presumably if it did install bloat from your account history you could just uninstall but why risk it.
JoeHockey said:
Not taking OTA updates is an interesting thought. That would not have occurred to me. Do the OTA's come from Google or VZW?
Click to expand...
Click to collapse
They come from Google. Carriers have a limited ability to delay Android version updates but not security updates. Google's official policy statement is here (scroll down to "Timing for software updates" | "Nexus devices"). For what it is worth, I am on VZW and I received the March update over-the-air on the first or second day it was available. You can always sideload via stock recovery in any event -- you don't need to be rooted or unlock your bootloader, but you do need a USB A-to-C cable (unless your computer has a USB C port).
No doubt I am guilty of resurrecting an old thread but this is the question I have. The N5X has a few different model numbers and I need to make sure I buy one that works on Verizon, or a Verizon MVNO. The inclusive list is: H790 (TD-LTE), H791 (TD-LTE), H791F (LTE-A), and the H798 (TD-LTE). The 790 & 798 feature CDMA bands so I suspect it is these...
People selling these have no clue...
Can anyone help me answer this question?
I haven't completely thought this through, so I'm not sure if this will make sense or not, so bear with me.
I've been looking around the internet and getting mixed responses about the verizon variant of the pixel. I want to be able to have an unlocked BL (which I'm pretty sure is possible with depixel8) and root. I normally would be all for the Google model, but they're out of stock and I could get the verizon model within a few hours rather than waiting for a restock. My main concern is if the verizon model will cause some annoyances in the future, because Verizon might pull something out of nowhere that would make having the verizon model dreadful. Basically, does anyone think that there will be any issues (especially in the future) if I just got the verizon model and unlocked the bootloader and just flashed the stock software, sort of de-verizoning it, or would I honestly just be better off waiting for Google to get more stock
Epsilon827 said:
I haven't completely thought this through, so I'm not sure if this will make sense or not, so bear with me.
I've been looking around the internet and getting mixed responses about the verizon variant of the pixel. I want to be able to have an unlocked BL (which I'm pretty sure is possible with depixel8) and root. I normally would be all for the Google model, but they're out of stock and I could get the verizon model within a few hours rather than waiting for a restock. My main concern is if the verizon model will cause some annoyances in the future, because Verizon might pull something out of nowhere that would make having the verizon model dreadful. Basically, does anyone think that there will be any issues (especially in the future) if I just got the verizon model and unlocked the bootloader and just flashed the stock software, sort of de-verizoning it, or would I honestly just be better off waiting for Google to get more stock
Click to expand...
Click to collapse
No, no, no. Patience is your friend.
Epsilon827 said:
I haven't completely thought this through, so I'm not sure if this will make sense or not, so bear with me.
I've been looking around the internet and getting mixed responses about the verizon variant of the pixel. I want to be able to have an unlocked BL (which I'm pretty sure is possible with depixel8) and root. I normally would be all for the Google model, but they're out of stock and I could get the verizon model within a few hours rather than waiting for a restock. My main concern is if the verizon model will cause some annoyances in the future, because Verizon might pull something out of nowhere that would make having the verizon model dreadful. Basically, does anyone think that there will be any issues (especially in the future) if I just got the verizon model and unlocked the bootloader and just flashed the stock software, sort of de-verizoning it, or would I honestly just be better off waiting for Google to get more stock
Click to expand...
Click to collapse
If you do get it from Verizon, unlock the bootloader immediately, and NEVER re-lock it. You can't really "de-verizon" it. Once you boot with a Verizon sim, the next update will push you to the Verizon version of the firmware, which is not a big deal, just different radios optimized to Verizons network. Any Verizon apps can be uninstalled.
Sent from my Pixel XL using XDA Premium HD app
I was in the same boat as you. I went with the verizon version. Unlocked the bootloader, and popped my sim in. It downloaded the latest non verizion ota. I say go for it.
Project Fi had all variants in stock as of a few days ago. My XL is due next week from them. I'm already a Fi customer and expect to be for the foreseeable future, so their finance option at zero interest was an easy sell. You could probably start service and cancel it after you receive your phone if you have another carrier.
Dude, I bought mine from Google store and vzw still pushed 63X on mine :crying:
Good thing I unlocked it before taking in the update.
n3far1us said:
Dude, I bought mine from Google store and vzw still pushed 63X on mine :crying:
Good thing I unlocked it before taking in the update.
Click to expand...
Click to collapse
Wait you should still be able to unlock no matter what update they push correct? It is just radios not a new bootloader
Sent from my Pixel XL using Tapatalk
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.