Database Develop

Cincinnati Bell HTC One could skip Android 4.2, go straight to 4.3

http://www.androidcentral.com/cincinnati-bell-htc-one-could-skip-android-42-go-straight-43
If true this COULD happen On the major carriers as well, hence the "small" update recently.

I saw that article, and while I wouldn't really mind, I'm not sure if I believe it. Other countries have already gotten 4.2.2 for the GSM One.

nerv8765 said:
I saw that article, and while I wouldn't really mind, I'm not sure if I believe it. Other countries have already gotten 4.2.2 for the GSM One.
Click to expand...
Click to collapse
I am not familiar with the carrier, are they GSM or CDMA?

Kraizk said:
I am not familiar with the carrier, are they GSM or CDMA?
Click to expand...
Click to collapse
Pretty much everywhere but America
Sent from my HTCONE using Tapatalk 2

It does seem strange to me that we haven't seen 4.2.2 on the sprint htc one... As I recall on the HTC 4glte the update to 4.1 came fairly quick. I think HTC just said fk it let's release 4.3 which has back end features that we benefit from. 4.2 isn't such a big deal when HTC has highly customized version of android.
Sent from my HTCONE using xda premium

tsdeaton said:
Pretty much everywhere but America
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
No no sorry, I meant is Cincinnati Bell GSM or CDMA. BTW it appears they are GSM so why the delay I am unsure....

Kraizk said:
No no sorry, I meant is Cincinnati Bell GSM or CDMA. BTW it appears they are GSM so why the delay I am unsure....
Click to expand...
Click to collapse
No GSM carriers in the US have updated to 4.2.2. But, Europe and Asia have gotten the update, which does work on ALL GSM phones, in any country.
However, there are no CDMA carriers (maybe a few, but it's a very small number) outside of the US, so the CDMA version (Sprint) has no update yet.

nerv8765 said:
No GSM carriers in the US have updated to 4.2.2. But, Europe and Asia have gotten the update, which does work on ALL GSM phones, in any country.
However, there are no CDMA carriers (maybe a few, but it's a very small number) outside of the US, so the CDMA version (Sprint) has no update yet.
Click to expand...
Click to collapse
Yes I know this, My question initially was if anyone knew if Cincinnati Bell was GSM or CDMA. If they were CDMA I could see HTC saying the same for us. That is not the case, they are GSM which means skipping the update for them seems rather weird.

They are gsm
From My TweakedOut ONE

I would imagine that HTC has 4.3 and probably has probably had it for months now. I'm wondering who they're working with to release it to, as far as carriers are concerned.

NORCALkID said:
It does seem strange to me that we haven't seen 4.2.2 on the sprint htc one... As I recall on the HTC 4glte the update to 4.1 came fairly quick. I think HTC just said fk it let's release 4.3 which has back end features that we benefit from. 4.2 isn't such a big deal when HTC has highly customized version of android.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
This is exactly why I have been wondering why people are pissed about a lack of 4.2.2 on the Sprint HTC One. There aren't that many new features to justify the outrage and there aren't any performance enhancements... 4.2.2 is barely a step up from 4.1.2 (the main improvements relate to tablets).

numus said:
This is exactly why I have been wondering why people are pissed about a lack of 4.2.2 on the Sprint HTC One. There aren't that many new features to justify the outrage and there aren't any performance enhancements... 4.2.2 is barely a step up from 4.1.2 (the main improvements relate to tablets).
Click to expand...
Click to collapse
I disagree (regarding tablets), but that's mainly due to how fast Google's native implementation of quick toggles grew on me. It makes more Sense though for a 4.3 update, given that a fairly long time has already passed since the last point release and the relatively minor changes (compared to 4.0->4.1).
Then again, I'm also mildly concerned that the real story here is that Sprint's carrier testing is taking longer than it should and we'll just get a delayed 4.2.2 update instead.

Rirere said:
I disagree (regarding tablets), but that's mainly due to how fast Google's native implementation of quick toggles grew on me. It makes more Sense though for a 4.3 update, given that a fairly long time has already passed since the last point release and the relatively minor changes (compared to 4.0->4.1).
Then again, I'm also mildly concerned that the real story here is that Sprint's carrier testing is taking longer than it should and we'll just get a delayed 4.2.2 update instead.
Click to expand...
Click to collapse
If you want quick toggles, just installed ViperRom... The changes aren't important enough to justify spending a lot of resources into upgrading the OS. The main changes in 4.1.2 -> 4.2.2 are in tablets, specifically multiple user implementation in the tablet environment.
http://developer.android.com/about/versions/android-4.2.html
Multiple Users
--------------------------------------------------------------------------------
Android now allows multiple user spaces on shareable devices such as tablets. Each user on a device has his or her own set of accounts, apps, system settings, files, and any other user-associated data.
Click to expand...
Click to collapse

numus said:
If you want quick toggles, just installed ViperRom... The changes aren't important enough to justify spending a lot of resources into upgrading the OS.
Click to expand...
Click to collapse
Exactly what I wrote as far as corporate resources. As for ViperROM, I really don't think you're reading posts before you hit "reply."
but that's mainly due to how fast Google's native implementation of quick toggles grew on me
Click to expand...
Click to collapse
I use Power Toggles for any devices not running 4.2, but I've come to prefer this method. The EQS included in ViperROM frankly makes my eyes bleed.
numus said:
The main changes in 4.1.2 -> 4.2.2 are in tablets, specifically multiple user implementation in the tablet environment.
http://developer.android.com/about/versions/android-4.2.html
Click to expand...
Click to collapse
Granted. Again, I don't think you read my post very carefully. Your original post contended that there weren't any marked changes for phones, which is what I disagreed with-- not that the majority of changes went to tablets.

Rirere said:
Exactly what I wrote as far as corporate resources. As for ViperROM, I really don't think you're reading posts before you hit "reply."
I use Power Toggles for any devices not running 4.2, but I've come to prefer this method. The EQS included in ViperROM frankly makes my eyes bleed.
Granted. Again, I don't think you read my post very carefully. Your original post contended that there weren't any marked changes for phones, which is what I disagreed with-- not that the majority of changes went to tablets.
Click to expand...
Click to collapse
I disagree (regarding tablets), but that's mainly due to how fast Google's native implementation of quick toggles grew on me.
Click to expand...
Click to collapse
I don't think you wrote what you thought you wrote, or else you need to look up the word regarding... You specifically said you disagree with my assessment on tables.
As for quick toggling, I think you are overestimating the percentage of users who care to turn features off once they are turned on.

numus said:
I don't think you wrote what you thought you wrote, or else you need to look up the word regarding... You specifically said you disagree with my assessment on tables.
As for quick toggling, I think you are overestimating the percentage of users who care to turn features off once they are turned on.
Click to expand...
Click to collapse
I think you need to reread your post for the context.
(the main improvements relate to tablets)
Click to expand...
Click to collapse
FTFY.

And I think Cincinnati Bell is a joke as far as a wireless carrier is concerned. I live in the Cincinnati area, and their service is terrible. I don't see them getting an upgrade to 4.3 before anyone else. They usually trail behind everyone else in their release of phones.

Android Revolution HD with Wi-Fi Calling on T-Mobile

I downloaded the version back in late Spring or early summer (might be 52.0) and remember that I couldn't find Wi-fi calling in it despite it being mentioned somewhere in the change logs. Is the latest version (81.0) supporting it now?

Cloudrift said:
I downloaded the version back in late Spring or early summer (might be 52.0) and remember that I couldn't find Wi-fi calling in it despite it being mentioned somewhere in the change logs. Is the latest version (81.0) supporting it now?
Click to expand...
Click to collapse
Read Post #3 FAQ #5. If it doesn't specifically state so in the OP then it probably is not supported. However, you might check out this Add-On from the T-Mobile HTC One Forum.

Cloudrift said:
I downloaded the version back in late Spring or early summer (might be 52.0) and remember that I couldn't find Wi-fi calling in it despite it being mentioned somewhere in the change logs. Is the latest version (81.0) supporting it now?
Click to expand...
Click to collapse
In short, NO, the last version to support T-Mobile WiFi calling (and coincidentally also Sprint phones) is ARHD 31.6

Interesting. Is there a reason why the feature was removed?

Cloudrift said:
Interesting. Is there a reason why the feature was removed?
Click to expand...
Click to collapse
i honestly don't know, technically it was never "removed", it was just not added in later releases... at first due to lack of OTA updates, but later on, maybe the person doing the t-mo stuff was no longer supporting it
since mike is nowhere close to T-Mo US, he pretty much has very little chance to test it, and if he was getting support for T-Mo then maybe that person moved on.
is the 4.4.3 T-Mo OTA update out? if it's not, i'm pretty sure it won't be implemented in 8x.x series until the official 4.4.3 T-Mo OTA is out.

Thanks for the information. Didn't know about all of this.

Can We Get a Carrier Specific Rom List Please

Here is the reasoning behind my request.
I am on Tmob and have a N6. I was fine stock rooted on 5.0 then 5.0.1. Then I decided to try a few roms. One that said it was for ALL carriers, didn't allow me to get calls unless I was only in 3g.
T-mobile is the ONLY one using a 47m ROM. All others are at 47i, why is there a difference? The radios most likely. I am 95r and 98r doesn't work on TMobile very well.
Can we get a Thread for EACH Carrier? They aren't all the same, at least from my experience. Sprint, VZW are different and have problems. I hear VZW users need to use 98r for "best results"
Go ahead, blast away. Just waiting for the "senior ops" to go to town on this one!

I'm on vzw and every ROM I've tried is fine. Have you updated to the latest image from google. Or are you still on 5.0.1

navyvet420 said:
Here is the reasoning behind my request.
I am on Tmob and have a N6. I was fine stock rooted on 5.0 then 5.0.1. Then I decided to try a few roms. One that said it was for ALL carriers, didn't allow me to get calls unless I was only in 3g.
T-mobile is the ONLY one using a 47m ROM. All others are at 47i, why is there a difference? The radios most likely. I am 95r and 98r doesn't work on TMobile very well.
Can we get a Thread for EACH Carrier? They aren't all the same, at least from my experience. Sprint, VZW are different and have problems. I hear VZW users need to use 98r for "best results"
Go ahead, blast away. Just waiting for the "senior ops" to go to town on this one!
Click to expand...
Click to collapse
With many phones, Samsung in particular - there are massive hardware differences that require several separate forums to manage.
With the nexus 6, the hardware is identical on all of them.
There are 2 specific builds that are slightly different and as you mentioned, they are M and I.
What we think is (but unproven) that M is for T-Mobile USA and I is for Australia. We have no concrete proof of that. Nor am I sure what the differences are. If you're using stock-based ROMs, try to stick to M builds.
As for AOSP, I'm not sure anyone knows what the difference is for T-mo. Maybe one day we'll find out.

rootSU said:
With many phones, Samsung in particular - there are massive hardware differences that require several separate forums to manage.
With the nexus 6, the hardware is identical on all of them.
There are 2 specific builds that are slightly different and as you mentioned, they are M and I.
What we think is (but unproven) that M is for T-Mobile USA and I is for Australia. We have no concrete proof of that. Nor am I sure what the differences are. If you're using stock-based ROMs, try to stick to M builds.
As for AOSP, I'm not sure anyone knows what the difference is for T-mo. Maybe one day we'll find out.
Click to expand...
Click to collapse
Thank You for the Reply.. I would agree with the thinking about M. Like I stated a non-M build killed the incoming calls unless my phone was on 3g with Enhanced 4g unchecked.
I was just asking for a Carrier Specific Rom thread thats all.

toknitup420 said:
I'm on vzw and every ROM I've tried is fine. Have you updated to the latest image from google. Or are you still on 5.0.1
Click to expand...
Click to collapse
Im on a 5.1 with 95r and 47M is my Build (nocturnal rom) its a Tmobile N6.. All other roms killed incoming calls unless I was stock rooted. CleanRom 2.0 and 2.1 with either 98r or 95r had same results. I like @scrosler roms, but can't live without getting business calls.

navyvet420 said:
Thank You for the Reply.. I would agree with the thinking about M. Like I stated a non-M build killed the incoming calls unless my phone was on 3g with Enhanced 4g unchecked.
I was just asking for a Carrier Specific Rom thread thats all.
Click to expand...
Click to collapse
Yeah. I think its a good idea to have a thread that lists all t-mo compatible ROMs, but first we need to learn what the actual difference is. Perhaps its just a RIL or something. In which case, there may just be a flashable zip required.
I just think we need to know more at this stage.
@efrant, do you know the differences? @simms22?

the aosp roms were missing code that made the tmobile devices not receive calls on lte, that has been fixed and should be in all roms that have been recently updated. i use terminus, which includes the code, so tmobile users get calls on lte, and volte is working. besides that issue that has been fixed, all carriers will work on any aosp rom. theres no such thing as a carrier specific nexus rom.

simms22 said:
the aosp roms were missing code that made the tmobile devices not receive calls on lte, that has been fixed and should be in all roms that have been recently updated. i use terminus, which includes the code, so tmobile users get calls on lte, and volte is working. besides that issue that has been fixed, all carriers will work on any aosp rom. theres no such thing as a carrier specific nexus rom.
Click to expand...
Click to collapse
Was the code added to aosp by Google? Or is it a community commit?

rootSU said:
Was the code added to aosp by Google? Or is it a community commit?
Click to expand...
Click to collapse
AOSP contains only Android OS nothing proprietary (proprietaries are included as a standalone) but when Google provided the binaries--proprietary libraries, applications were missing which caused VoLTE not to work properly. Myself and Sykopompos worked on the blobs and having VoLTE working, they were pulled from the factory image / deodexed OTA.

zephiK said:
AOSP contains only Android OS nothing proprietary (proprietaries are included as a standalone) but when Google provided the binaries--proprietary libraries, applications were missing which caused VoLTE not to work properly. Myself and Sykopompos worked on the blobs and having VoLTE working, they were pulled from the factory image / deodexed OTA.
Click to expand...
Click to collapse
this

Been away a while, couple questions...

Good evening XDA community!
It's been a while since I've been active on the forums, and I'm back with a couple questions. I've historically been an HTC guy, but my last few phones have been branching out. After my Sensation and Evo3D, my wife and I decided to see what all the Samsung hoopla was about and got S4s. Terrible decision. I bought Oneplus Ones out of pocket to replace the Samsung crap, and they have been great phones. Due to some new geographical and housing circumstances, we are able to once again be Tmo customers and need wifi calling (no signal inside our house). Although our Oneplusses work great on Tmo's network, they do not have the ability to use wifi calling (that I was able to deduce). We opted to go with LG this time, and so here we are. I've done some preliminary searching, however I know that info can become outdated pretty quick in some cases and I'm looking to ensure I'm finding up to date info before I move forward.
Our phones as they are out of the box:
LG-H811
Baseband: MPSS.BO.2.5.c3-00109-M8992FAAAANAZM-1
Kernel: 3.10.84
Build: MRA58K
Software Version: H81120i
1) I've never seen the OEM unlock option in the developer menu before. I see that this is part of the rooting process, but can someone put in simple terms what this does? Is it exactly what it sounds like (carrier unlock)?
2) This thread appears to be the proper (only?) method to unlock the bootloader and root the phone, please confirm or point me in the right direction. http://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
3) I don't think rooting and putting a new rom on will break wifi calling, but I'd like to be sure, please confirm.
4) Is the CM13 at this thread stable? (http://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588) I've always preferred Cyanogenmod, but their website says it's still in nightly phase. If stable, does this have Wifi calling capability?
Thanks in advance for all the help.

jdelforge5684 said:
Good evening XDA community!
It's been a while since I've been active on the forums, and I'm back with a couple questions. I've historically been an HTC guy, but my last few phones have been branching out. After my Sensation and Evo3D, my wife and I decided to see what all the Samsung hoopla was about and got S4s. Terrible decision. I bought Oneplus Ones out of pocket to replace the Samsung crap, and they have been great phones. Due to some new geographical and housing circumstances, we are able to once again be Tmo customers and need wifi calling (no signal inside our house). Although our Oneplusses work great on Tmo's network, they do not have the ability to use wifi calling (that I was able to deduce). We opted to go with LG this time, and so here we are. I've done some preliminary searching, however I know that info can become outdated pretty quick in some cases and I'm looking to ensure I'm finding up to date info before I move forward.
Our phones as they are out of the box:
LG-H811
Baseband: MPSS.BO.2.5.c3-00109-M8992FAAAANAZM-1
Kernel: 3.10.84
Build: MRA58K
Software Version: H81120i
1) I've never seen the OEM unlock option in the developer menu before. I see that this is part of the rooting process, but can someone put in simple terms what this does? Is it exactly what it sounds like (carrier unlock)?
2) This thread appears to be the proper (only?) method to unlock the bootloader and root the phone, please confirm or point me in the right direction. http://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
3) I don't think rooting and putting a new rom on will break wifi calling, but I'd like to be sure, please confirm.
4) Is the CM13 at this thread stable? (http://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588) I've always preferred Cyanogenmod, but their website says it's still in nightly phase. If stable, does this have Wifi calling capability?
Thanks in advance for all the help.
Click to expand...
Click to collapse
1.to unlock bootloader you need special key lock.bin from LG..
not sure how i got mine locked. ... why. because of the bootloop issue.. and unlocking bootloader will void warranty so says LG on their website..'
2.like i said never tried unlocking. am itching to..
3. i think as long as you are in a stock based rom.. not
aosp or CM youll have wificalling.
4. cm is nice but alot of bugs not good camera quality.. i would only go CM if i ever wanted to try new android version.. why go CM when you get MM.?

jdelforge5684 said:
Good evening XDA community!
It's been a while since I've been active on the forums, and I'm back with a couple questions. I've historically been an HTC guy, but my last few phones have been branching out. After my Sensation and Evo3D, my wife and I decided to see what all the Samsung hoopla was about and got S4s. Terrible decision. I bought Oneplus Ones out of pocket to replace the Samsung crap, and they have been great phones. Due to some new geographical and housing circumstances, we are able to once again be Tmo customers and need wifi calling (no signal inside our house). Although our Oneplusses work great on Tmo's network, they do not have the ability to use wifi calling (that I was able to deduce). We opted to go with LG this time, and so here we are. I've done some preliminary searching, however I know that info can become outdated pretty quick in some cases and I'm looking to ensure I'm finding up to date info before I move forward.
Our phones as they are out of the box:
LG-H811
Baseband: MPSS.BO.2.5.c3-00109-M8992FAAAANAZM-1
Kernel: 3.10.84
Build: MRA58K
Software Version: H81120i
1) I've never seen the OEM unlock option in the developer menu before. I see that this is part of the rooting process, but can someone put in simple terms what this does? Is it exactly what it sounds like (carrier unlock)?
2) This thread appears to be the proper (only?) method to unlock the bootloader and root the phone, please confirm or point me in the right direction. http://forum.xda-developers.com/tmobile-g4/general/how-to-unlock-bootloader-flash-twrp-t3344421
3) I don't think rooting and putting a new rom on will break wifi calling, but I'd like to be sure, please confirm.
4) Is the CM13 at this thread stable? (http://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588) I've always preferred Cyanogenmod, but their website says it's still in nightly phase. If stable, does this have Wifi calling capability?
Thanks in advance for all the help.
Click to expand...
Click to collapse
Follow this guide.you lose wifi calling if not on stock rom.there are custom stock roms that are very good.my favorite is from turbo2012(just my opinion)that are slim and optimized.
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its the same if you are on 20o.just follow the guide you dont need any special key from lg.

custom roms???

this device has amazing specs but lack of software support. it would be amazing some custom pie or 10 roms
i don't need asus own features
i really like a pixel experience,los or omnirom the most stock android feeling rom( +120hz you will get a more buttery smooth experience)
please somebody create one
sources are available
even zenfone 6 has custom roms

Yes please !

Alessandro999 said:
this device has amazing specs but lack of software support. it would be amazing some custom pie or 10 roms
i don't need asus own features
i really like a pixel experience,los or omnirom the most stock android feeling rom( +120hz you will get a more buttery smooth experience)
please somebody create one
sources are available
even zenfone 6 has custom roms
Click to expand...
Click to collapse
one problem is TWRP hasn't even been created... Yet. And yes there really is no software support... Yet

Swarai said:
one problem is TWRP hasn't even been created... Yet. And yes there really is no software support... Yet
Click to expand...
Click to collapse
yes exactly i really hope somebody create a tpwr and rom because sources are out

It will be nice if this phone receives TWRP and custom roms.
Sent from my iPad using Tapatalk

Didn't it JUST launch globally today?
Let's give it some time.

i really hope somebody create a stable tpwr since sources are available and the most stable rom out there like omnirom or pixel experience
preferred omnirom

IMO I don't believe it will receive support anytime soon. Unless ROG was able to convince your standard Android enthusiast that this isn't just a gaming device. People that purchase this phone are mainly interested in one thing, gaming, not development. So, ROG has to convince those types that this device is just as good as those others.

It will be interesting to have custom roms for rog. waiting also

ZeroKool76 said:
IMO I don't believe it will receive support anytime soon. Unless ROG was able to convince your standard Android enthusiast that this isn't just a gaming device. People that purchase this phone are mainly interested in one thing, gaming, not development. So, ROG has to convince those types that this device is just as good as those others.
Click to expand...
Click to collapse
My thoughts exactly. Custom roms are awesome but they are generally made or ported to be used by a majority of the phones out there. If we got a custom rom ie. AOSP, who would code in the air triggers from scratch?
Having said that, the stock rom is quite good. I don't have the need to root it like I did with my Mate 20X to shrink down the gigantic icons/screen because by default Asus allows a lot of customization.

n1tro said:
My thoughts exactly. Custom roms are awesome but they are generally made or ported to be used by a majority of the phones out there. If we got a custom rom ie. AOSP, who would code in the air triggers from scratch?
Having said that, the stock rom is quite good. I don't have the need to root it like I did with my Mate 20X to shrink down the gigantic icons/screen because by default Asus allows a lot of customization.
Click to expand...
Click to collapse
Apparently the American version doesn't have volte or voWi-Fi as well.. that, along with the fact that it doesn't support band 71, are big reasons why your normal or typical Android enthusiast/ developer is not going to purchase this device

ZeroKool76 said:
Apparently the American version doesn't have volte or voWi-Fi as well.. that, along with the fact that it doesn't support band 71, are big reasons why your normal or typical Android enthusiast/ developer is not going to purchase this device
Click to expand...
Click to collapse
So does this apply to the Tengent games (CN) version too? I am getting the cheaper CN version and then going to flash the WW (Global) Rom, so essentially I guess I am asking is this a hardware omission, or is it ROM (software) based?
And how does this typically affect say a normal phone user?

It might get an update. As for band 71, I personally don't care because I won't use it all.

jkeener88 said:
So does this apply to the Tengent games (CN) version too? I am getting the cheaper CN version and then going to flash the WW (Global) Rom, so essentially I guess I am asking is this a hardware omission, or is it ROM (software) based?
And how does this typically affect say a normal phone user?
Click to expand...
Click to collapse
As I understand it, it doesn't have to do with software or hardware, they just simply don't support volte of vowifi. In China, they do. So, it's not the device, but the companies choice. May be some restrictions that we aren't aware of, otherwise it doesn't seem like a very smart decision. I was all in until I heard this. 3G is going to be removed from our networks in the next few years, so voLTE is kind of mandatory. Even now, if I don't have voLTE, I can't make or receive calls. VoWiFi, that's beneficial if you're cell signal is low for whatever reason. Maybe you work below ground or in Faraday cage style buildings. Plenty of uses for it. As far as band 71, no, I probably don't need it. But that doesn't mean I wouldn't want it just in case. Always better to have and not need, than to need and not have.

ZeroKool76 said:
As I understand it, it doesn't have to do with software or hardware, they just simply don't support volte of vowifi. In China, they do. So, it's not the device, but the companies choice. May be some restrictions that we aren't aware of, otherwise it doesn't seem like a very smart decision. I was all in until I heard this. 3G is going to be removed from our networks in the next few years, so voLTE is kind of mandatory. Even now, if I don't have voLTE, I can't make or receive calls. VoWiFi, that's beneficial if you're cell signal is low for whatever reason. Maybe you work below ground or in Faraday cage style buildings. Plenty of uses for it. As far as band 71, no, I probably don't need it. But that doesn't mean I wouldn't want it just in case. Always better to have and not need, than to need and not have.
Click to expand...
Click to collapse
This is wrong for TMO. It's in the SW. There's an option for volte carrier check on xiaomis phones. A simple dialer code disables this check, and volte works on TMO. I'm hoping there's a way we can do this on the rog 2. That, or a build.prop edit to enable it. There has to be a setting hidden that disables volte in us.

suzook said:
This is wrong for TMO. It's in the SW. There's an option for volte carrier check on xiaomis phones. A simple dialer code disables this check, and volte works on TMO. I'm hoping there's a way we can do this on the rog 2. That, or a build.prop edit to enable it. There has to be a setting hidden that disables volte in us.
Click to expand...
Click to collapse
I've just been reading a little bit more up on it, and apparently, ASUS didn't pay the cell carriers in North America for provisioning costs. That's why it won't work. So, regardless of software, hardware or any other type of hackery, it won't work in North America.

ZeroKool76 said:
I've just been reading a little bit more up on it, and apparently, ASUS didn't pay the cell carriers in North America for provisioning costs. That's why it won't work. So, regardless of software, hardware or any other type of hackery, it won't work in North America.
Click to expand...
Click to collapse
So is this just a bad/dumb move by Asus or what? I mean I honestly don't know if these omissions will affect me, all I know is I still own a Samsung until I get the Asus and was always able to use my Samsung phone how I wanted to use it