Related
Though this phone is capable of VOLTE it has not, as of yet, functioned on my carrier AT&T. My line is supposedly provisioned properly in their system for VOLTE however the agent I spoke with informed me that an IMEI must be whitelisted on their servers before it will actually work. Basically this means that normally only the phones you buy from them are VOLTE capable because of their whitelisting system. Now this agent supposedly filed a case to get my IMEI added to this list which should supposedly allow for the VOLTE to then function on the AT&T network. And so if this actually ends up working I will report back so others can do the same if they wish to use VOLTE on AT&T.
Cool.... I tried the same but did not get offered to try and get my imei white listed.
Sent from my XT1575 using Tapatalk
timde9 said:
Though this phone is capable of VOLTE it has not, as of yet, functioned on my carrier AT&T. My line is supposedly provisioned properly in their system for VOLTE however the agent I spoke with informed me that an IMEI must be whitelisted on their servers before it will actually work. Basically this means that normally only the phones you buy from them are VOLTE capable because of their whitelisting system. Now this agent supposedly filed a case to get my IMEI added to this list which should supposedly allow for the VOLTE to then function on the AT&T network. And so if this actually ends up working I will report back so others can do the same if they wish to use VOLTE on AT&T.
Click to expand...
Click to collapse
This support doc from ATT mentions needing a specific SIM to be able to access voLTE. Did you make sure yours was indeed a UICC-G SIM card ?
https://www.att.com/esupport/article.jsp?sid=KB425890&cv=820
Yeah but that's not the problem this sim came right out of my att galaxy s6 which the VOLTE worked very well on. I'm gonna call back later today after work and see if my case went anywhere
Crappyvate said:
This support doc from ATT mentions needing a specific SIM to be able to access voLTE. Did you make sure yours was indeed a UICC-G SIM card ?
https://www.att.com/esupport/article.jsp?sid=KB425890&cv=820
Click to expand...
Click to collapse
I have a Pure on ATT, with a brand new NanoSIM card (picked it up from the AT&T store just after I picked up the phone); the 9th and 10th digits of the ICCID are '27', so it is a UICC-G SIM.. I was bummed to see that VoLTE wouldn't work on the device; all my investigation led me to the phone not being whitelisted in ATT's database. The 'Enhanced 4G LTE Mode' setting doesn't show up at all under Cellular Networks. I ran across a page that says to do the '*#*#4636#*#*' trick, go to 'Phone Info', and make sure that the toggle shows 'TURN OFF VOLTE PROVISIONED FLAG' (versus 'Turn On').. on my phone it showed it as provisioned to start with, but the option to enable Enhanced 4G LTE still is gone.
Apparently with Verizon customers, if the provisioned flag is on, but that menu option is missing, they need to log into their Verizon account and enable the 'HD Voice' flag on their account, at which point the option to enable it will show up. I'm guessing that basically whitelists their devices IMEI, which is the part we're apparently missing with ATT. :/
---------- Post added at 02:02 PM ---------- Previous post was at 01:57 PM ----------
timde9 said:
Yeah but that's not the problem this sim came right out of my att galaxy s6 which the VOLTE worked very well on. I'm gonna call back later today after work and see if my case went anywhere
Click to expand...
Click to collapse
Hopefully it will, or else they will figure out that they need to let people who want this enable it and make it an account setting we can change! Verizon allows BYOD HD Voice, why can't ATT?!
natecarlson said:
I have a Pure on ATT, with a brand new NanoSIM card (picked it up from the AT&T store just after I picked up the phone); the 9th and 10th digits of the ICCID are '27', so it is a UICC-G SIM.. I was bummed to see that VoLTE wouldn't work on the device; all my investigation led me to the phone not being whitelisted in ATT's database. The 'Enhanced 4G LTE Mode' setting doesn't show up at all under Cellular Networks. I ran across a page that says to do the '*#*#4636#*#*' trick, go to 'Phone Info', and make sure that the toggle shows 'TURN OFF VOLTE PROVISIONED FLAG' (versus 'Turn On').. on my phone it showed it as provisioned to start with, but the option to enable Enhanced 4G LTE still is gone.
Apparently with Verizon customers, if the provisioned flag is on, but that menu option is missing, they need to log into their Verizon account and enable the 'HD Voice' flag on their account, at which point the option to enable it will show up. I'm guessing that basically whitelists their devices IMEI, which is the part we're apparently missing with ATT. :/
---------- Post added at 02:02 PM ---------- Previous post was at 01:57 PM ----------
Hopefully it will, or else they will figure out that they need to let people who want this enable it and make it an account setting we can change! Verizon allows BYOD HD Voice, why can't ATT?!
Click to expand...
Click to collapse
I will follow up with ATT as well as they assure me that voLTE was available in my area..
Your APN also needs to point the the correct server.
APN: nxtgenphone
MMSC: http://mmsc.mobile.att.net
MMS Proxy: proxy.mobile.att.net
MMS Port: 80
APN Type: default,mms,supl,hipri,fota
My question is how to tell when you are on VOLTE?
goolac said:
My question is how to tell when you are on VOLTE?
Click to expand...
Click to collapse
If you can see the "Enhanced 4G LTE Mode" setting, and it's turned on, in theory it should work.
Then, when you place a call, your status bar's cell signal icon should still show 'LTE' instead of falling back to 'HSPA'.
I ordered this phone via Moto Maker and expect to have it in my hands next week. I currently have an older AT&T sim from my Samsung Galaxy S4, and imagine that I would need a new one to utilize VoLTE. Thanks to all of you trying to figure this out.
I found out from another at&t rep that the guy who told me about creating a case apparently did nothing but keep me on hold for a long time because she couldn't locate this apparent case anywhere. After asking her some hard questions I have gotten her to divulge that hdvoice and VOLTE are operating on lte band 2 or 1900 frequency. If I'm not mistaken this phone is already capable of that band right now even without marshmallow so there is almost certainly some sort of white list on at&ts part. Honestly I will probably write to the President about this because its not like its a security issue its just an absurdity
I asked a friend of mine that works as a manager at a corporate store here in town if he knew anything about it... He said it would be something to ask tech support, but he's not heard of a whitelist for VoLTE services. He did also say that most of what they do is just adding IMEI's to the system, and that they don't get BYOD cases very often...
I also work for AT&T, but not in the mobility side... Currently no contacts in the tech side of mobility either.
/scratches head
Am I the only one thinking that this really shouldn't be such a big mystery?
Especially for actual AT&T Wireless reps?
Here is a link to the ATT HD Voice info page... Turns out I have a goPhone plan and so HD is restricted.
http://www.att.com/esupport/article.html#!/wireless/KM1046250
It says in my online account that I am provisioned for VOLTE and from what I discovered from tech support the VOLTE operates on a frequency band that is fully supported by this phone. A whitelisting approach is then the only possible explanation at this point and I will be writing, the President to figure out why
It seems that VOLTE is not yet available on our phones. This is what I was told:
"Enrique: At the moment, VOLTE is only compatible with your Samsung S5 for the Moto X Pure, we are still waiting for a firmware update from Motroloa to have the feature enabled."
and then
"Enrique: Actually when the firmware is released, VOLTE will automatically be enabled on the Moto X, all you need to do is turn it on by heading over to Settings > More Networks > Mobile Networks > VoLTE"
So it seems we need a firmware update from Motorola. Maybe I missed something on this, though?
I called AT&T yesterday and they also confirmed that your account must be 'enabled' for VoLTE, but their "advanced' engineers (whatever this means) also need to provision your device on the back end. My ticket has an SLA of 12/22. I suspect it should be done much sooner than this and will also update everyone on my findings/results.
Just FYI, volte works perfectly on my MXPE on Verizon. I did have to call and have the feature added. Rebooted the phone, and it was enabled. The firmware DOES fully support it so the problem is likely on AT&T's end. Please keep us updated.
Update from ATT Advanced Tech Support.
"April: At this time we only support VOLTE for AT&T devices."
---------- Post added at 08:44 AM ---------- Previous post was at 08:24 AM ----------
So upon further discussion with ATT Advanced Tech Support, the MXPE is NOT on their list of approved VOLTE devices because it's not an ATT device.
That sucks.
Yep, AT&T is the worst carrier because they are one of the largest (just behind Verizon) and aren't bound to any regulation such as the C-block agreement that Verizon must adhere to. So, that means that AT&T services can be restricted to AT&T devices and only those devices. Verizon and T-Mobile have opened up VoLTE to unlocked phones, however Wifi calling seems to be another story. T-Mobile makes Wifi calling available to Nexus devices, and I'm not sure if agreements are needed between the carrier and phone manufacturer (or proxy for Nexuses - Google). Verizon will definitely limit Wifi calling to Verizon devices too, I'm sure of it, at least at the start. They'll make up some technical or security reason for disallowing unlocked phones.
I wouldn't worry about it too much though. VoLTE is more of a necessity for Verizon because they can't do simultaneous voice/data when on a CDMA call (2013 Moto X can). HSPA/HSPA+ supports voice and data. VoLTE often comes with other issues too, depending on network congestion. Unfortunately, carriers are struggling to keep up with demand for data, and VoLTE is no exception to that as calls are data packets.
VoLTE and VoWifi (Wifi calling) are part of the IMS services framework, and it is up to the carrier to allow access to that framework.
timde9 said:
I found out from another at&t rep that the guy who told me about creating a case apparently did nothing but keep me on hold for a long time because she couldn't locate this apparent case anywhere. After asking her some hard questions I have gotten her to divulge that hdvoice and VOLTE are operating on lte band 2 or 1900 frequency. If I'm not mistaken this phone is already capable of that band right now even without marshmallow so there is almost certainly some sort of white list on at&ts part. Honestly I will probably write to the President about this because its not like its a security issue its just an absurdity
Click to expand...
Click to collapse
This isn't surprising. I recently had a HORRIBLE experience with AT&T U-Verse (yes I know, different department but same company). They sold me "fiber" Internet which turned out to be DSL and talked me into switching from 60MBPS Charter cable. Long story short, one of the many lies I was told is that I could cancel within the first month without paying any service or installation charges.
....so I cancelled in July only a couple weeks after starting service. I was told by a rep that I would receive a bill only because it's issued before the adjustments are issued and that the account will be zeroed out. The following month I called back when I got another bill. And I've called every month since (several times a month) and received the same story from every rep I've talked to. Each rep says they've zeroed the account but they can't e-mail or fax out any confirmation. I've even been told this by managers. Some of the reps are too lazy for this lie and they'll pretend I've called the wrong department and transfer me to a dead extension, which disconnects the call.
Yesterday I received a collection notice for this. That's going to ding my 809 credit score! AT&T is a shady company! As a long time Verizon Wireless customer I can say that I've never received this kind of service from any tier of their support. I'd highly recommend anyone having issues with AT&T to make the switch. What company can't send external communications? I've had Verizon reps send me e-mails, call me back, or even send official texts while on a call. AT&T is a garbage company and I pity any soul trying to get them to do anything other than bill you.
Sent from my XT1575 using Tapatalk
I'm performing research into an odd issue that may affect custom ROMs across multiple devices, and I'm hoping a few people can help me.
If you're here, you probably know that Sprint is a CDMA carrier. The SIM card is for LTE only, and so removing it should not affect ability to make calls, and the phone should still get 3G data just fine.
On my stock Lollipop Note 3, it works as expected; a notification bugging me to insert a SIM, but otherwise works fine with 3G.
I had a Samsung rep take the SIM out of his Sprint Marshmallow S6, expecting it would work the same... but instead it completely killed the cell radio. No connection at all, no phone calls, no Mobile Networks option in Settings.
On ports of Note 5 firmware, the phone will connect to the network for phone calls, but absolutely not allow mobile data to turn on. However, this seems to be because the source ROM is GSM only - the Sprint kernel and modem allow it to use CDMA, but the UI still can not fathom having mobile data without a SIM and simply disables the option. The same happens with an S7 ROM port (also from GSM-only source). With a lot of command line %&$#ery, I managed to make it use 3G, but only for about 10 minutes before it catches on and the phone has to reboot.
Now the question I seek to answer is whether the ROM port issue occurs because the source ROM was GSM, or because Samsung just removed the capacity for CDMA-only data from more modern phones. Once I know that, I can work toward fixing it. As such, I humbly request that a few people boot their Sprint Note 5's on stock(-ish) firmware without a SIM card, and let me know if they can use 3G like that.
Cheers! :fingers-crossed:
Newer phones have different hardware. The S6 and Note 5 need the SIM card to authenticate with LTE and with CDMA/EVDO. A rom change will never fix this. This is the next way phone manufacturers and Sprint want new phones to be built. The CDMA and LTE are one authentication.
Your Note 3 had the old way of authentication, where the CDMA portion was separate from LTE. Hence, when the SIM card was removed, 3G worked because the CDMA authentication was embedded into the device.
New phones will not allow this, and honestly, the only reason you were able to use Sprint CDMA without the SIM card is because Sprint has your device ID and let it authenticate for a bit, but then the network itself rejected you because there was no authentication mechanism.
That's... all really a wonderful theory, but the whole point is that current research is indicating it doesn't work the way anyone thinks it does. Even the Samsung rep was shocked that his phone behaved the way it did.
As of right now, I have located one Marshmallow ROM that will allow 3G to work perfectly without a SIM, but have not heard back from the dev on how; it's based off CM, which in my experience will not. The ROMs that don't, don't stop because of authentication issues, they stop purely because of a UI trigger. Otherwise just rebooting wouldn't allow it to be fine for another 10 minutes.
Hence, research. I know all about what it ought to do. And why, and how. I could write a paper on it. I want to know what it does. For that, I ask only for some kind soul to boot their phone without a SIM for two minutes.
That's because its not a theory. It's reality.
In a cdmaOne/CDMA2000 ("CDMA") network, the UICC contains a CSIM application, in addition to 3GPP USIM and SIM applications. A card with all 3 features is called a removable user identity card, or R-UIM. Thus, the R-UIM card can be inserted into CDMA, GSM, or UMTS handsets, and will work in all three cases.
Click to expand...
Click to collapse
Source
I fried my SIM card when I first got the phone by using QPST to try to flash a custom PRL. Not only did the phone power cycle every 5 minutes, but it lost its entire connection to the network. No 3G, no LTE, no 1x. When i went to replace the SIM card, the rep went through about 5 cards until he found one that was actually a UICC card, as the others were ordinary SIM cards just for LTE.
Also, please don't tout research on XDA. Your research is at best an observation with one ROM, and my guess it was a fluke where Sprint didn't reject your connection. Research requires actual proof and peer review. One ROM working one time doesn't warrant research. This isn't an issue with a "UI Trigger" as you put it, but its just the new way phones are authenticated.
Try removing a UICC card from a recent Nexus device (6,5X,6P), it will lose all connection as well. Why? Not because of a UI Trigger, but because new phones need the UICC to authenticate both CDMA and LTE.
Finally, unless that Samsung rep was a Samsung engineer, he is just a salesman with little tech knowledge past what is needed to sell the device.
Similar issue Sprint Note 3
DejitaruJin said:
I'm performing research into an odd issue that may affect custom ROMs across multiple devices, and I'm hoping a few people can help me.
If you're here, you probably know that Sprint is a CDMA carrier. The SIM card is for LTE only, and so removing it should not affect ability to make calls, and the phone should still get 3G data just fine.
On my stock Lollipop Note 3, it works as expected; a notification bugging me to insert a SIM, but otherwise works fine with 3G.
I had a Samsung rep take the SIM out of his Sprint Marshmallow S6, expecting it would work the same... but instead it completely killed the cell radio. No connection at all, no phone calls, no Mobile Networks option in Settings.
On ports of Note 5 firmware, the phone will connect to the network for phone calls, but absolutely not allow mobile data to turn on. However, this seems to be because the source ROM is GSM only - the Sprint kernel and modem allow it to use CDMA, but the UI still can not fathom having mobile data without a SIM and simply disables the option. The same happens with an S7 ROM port (also from GSM-only source). With a lot of command line %&$#ery, I managed to make it use 3G, but only for about 10 minutes before it catches on and the phone has to reboot.
Now the question I seek to answer is whether the ROM port issue occurs because the source ROM was GSM, or because Samsung just removed the capacity for CDMA-only data from more modern phones. Once I know that, I can work toward fixing it. As such, I humbly request that a few people boot their Sprint Note 5's on stock(-ish) firmware without a SIM card, and let me know if they can use 3G like that.
Cheers! :fingers-crossed:
Click to expand...
Click to collapse
Similar issue with HLTESPR (Sprint Note3) moved to Lineage OS 5.8.2 can not make calls with SIM card inserted. Remove the card and the 4 works fine (no LTE). APN and Carrier show up in settings.
Replace the SIM card no APN's no carrier, no phone unless on WiFi.
I've done what I thought was a good amount of research before buying the ROG Phone 5. Everything I have been able to find is it will work on AT&T's network. Specifically I bought model 1005DC which was described as the "Global" version as well as the NON Tencent Games version. AT&T's own site says they support the ROG 5 model 1005D, 1005DA and 1005DC but I have not had any luck. The phone recognizes the SIM card but I get no cellular data and am unable to make phone calls. Is there something I'm missing or is there a specific model that is 100% confirmed to work on AT&T?
Did you buy it from the Asus store for your country? That would be the one that's confirmed to work.
The Asus store for my country is and has been sold out like everything else. I bought it from a 3rd party retailer that operates and ships from my country but it still didn't work.
You might not have a compatible model. It's common with third-party sellers.
It may also have a faulty SIM reader. That's been going around. Make sure you are using slot 1 with a single card.
Assuming you have the correct device to operate on US bands with ATT, make sure you are using the proper APN. The ones that works best for me phone is "nxtgenphone"
After you set APN, reboot device and wait a few minutes. If that does not work, reset your network information (Settings>System>Reset Options> Reset Wifi, mobile and Bluetooth) and see if that helps.
Your last option would be to call ATT and make sure they have proper IMEI etc for your device, and ask them to repovision as a last resort.
5G APN Collection
Warning: Setting an APN will NOT make 5G work if your carrier does not support your hardware frequencies. These are carrier settings, not magic beans. T-Mobile (US) APN Name T-Mobile US APN fast.t-mobile.com Proxy Not set Port Not set...
forum.xda-developers.com
I had actually done all of that already short of calling AT&T. I ended up giving up on trying to get it to work, returned the phone and got a ROG 3 instead. Worked perfectly right out of the box. Thank you all for the help.
The g100/edge s are listed as no Verizon support, but I was wondering if anyone has tried. They have most of the Verizon 4g bands and 2 of the 5g bands
If anyone is curious about this I have not confirmed but I did find a post where someone tried on reddit. Everything worked except receiving texts. Verizon was unable to troubleshoot because the IMEI was not white listed in their system. After doing some reading this leads me to believe cdmaless needs to be programmed on the SIM prior to putting it in the g100/edge s and it may work. This would require a cdmaless "mule" phone to preprogram the sim prior to installation. If I can find a phone to borrow I may purchase one and give it a shot.
Same problem here. I love the g100, amazing phone especially for the price, but cannot receive texts and Verizon refuses to help with an "unsupported" phone, even though it supports all the bands necessary for operation. 4G works, calls work, and sending SMS and MMS work. I'm willing to try whatever ideas to get this going. Been riding off my old phone as a hotspot for the g100 lately.
ah nice to see I'm not the only one in this situation. You already pulled the trigger though! If you can find a whitelisted gsm phone to swap your sim into and reprogram first you might be up and running. I've been trying to find the cheapest mule to try this with. Will update if a come up with one.
I'm not sure I follow. Why would another phone make this one work?
And I guess what are the requirements of the other phone? I could probably convince a friend to let me swap if it'll work
I'm not 100% sure but I think the issue you are having is the way the line is provisioned. It is most likely set to use the old CDMA radios (the g100 does not have them). Verizon has a cdmaless provisioning setting to get around this, but they can/will only do it for CDMAless phones they have added to their white list (while having compatible 4g and one 5g band the g100 is not on the list). If you put your sim in a white listed CDMAless phone you can get the proper provisioning put on by Verizon before putting it in the g100. This should fix in bound text
Ooh very interesting. I did find stuff for 'cdmaless' in my search to get it working, but asking Verizon to add it yielded terrible results.
So it seems like the cheapest options for this might be the Moto E (2020) or the Moto G Power (2021). I might try to pick one up next week to see if this theory works.
nice! My brother has a s21 which I think will work. Trying to find one that doesn't take 2 months to get
So I ordered a G Power, swapped sim cards and it couldn't receive texts. Activated on the Verizon website, which needed to text me a verification code, hilarious.
Anyway, it added the feature
Code:
CDMA-LESS DEVICE PROVISIONING
to the sim, popped it back into the G100 and... it works!
Great suggestion, drock3260
So when I originally tried to get this to work on Verizon and they insisted that CDMA-less doesn't exist, well, I guess they lied.
So uh, does anyone want to borrow a G Power for 5 mins?
3diord said:
Anyway, it added the feature
Code:
CDMA-LESS DEVICE PROVISIONING
to the sim, popped it back into the G100 and... it works!
Click to expand...
Click to collapse
Thanks for posting about this! I am on V and strongly considering importing an Edge 20 Fusion. This thread gives me hope that it will actually work.
yeah according to kimovil it has compatible bands. If you are still thinking of pulling the trigger good luck.
What about MVNOs using Verizon towers? I plan to use US Mobile SuperLTE. Will text messages work?
It only has the one main 5g band so no I don't believe Verizon mvnos are gonna work. I didn't really care about 5g as there are few towers around me, but I have had great 4g coverage with text messaging
I can give you the best and most accurate answer. I live in America I have a moto g100 there's only one way to get this phone and that is to purchase it through Motorola USA one model option only and that's a blue Moto g100 with 8 gigs of RAM 128 gigs of memory model number xt2125-4 the name of the firmware is North American retail absolutely no bloatware because it's straight from the manufacturer not a cell phone carrier and for absolutely everything to work on the phone 4G 5G the only cell phone carrier that works on is the T-Mobile network. You can use it on the AT&t network but you're not going to get Wi-Fi calling or the 5G Network. It is a GSM only. Absolutely no CDMA nothing will work on the Verizon network. It is the only phone on the American market that dual SIM. It does have NFC. A dedicated Google Assistant button with the fingerprint scanner on the side. One issue though the North American retail will probably be the last one to receive Android 12 but because this is the United States the Android 12 version we get will be very stable
I recently got a Chinese 8/128 Edge S (XT2125-4), and 4G calls/data/sms all just work for me on Verizon.
I had previously activated my SIM card in a OnePlus 8 Pro. So in my case it was already set up for CDMA-less / LTE-only service, and I just had to move the SIM card over to the Edge S and it started working right away.
I've never noticed the phone say it was connected to 5G, but I'm not sure if I need a new sim card, or if there aren't any 5G towers in my area (or both.)
If a VoLTE capable phone has the mbn files updated to use those of an AT&T white listed phone what would need to happen to get the phone active on AT&T's network?
healerdan said:
If a VoLTE capable phone has the mbn files updated to use those of an AT&T white listed phone what would need to happen to get the phone active on AT&T's network?
Click to expand...
Click to collapse
The same as any other device, SIM/carrier unlock the device then activate the device on AT&T using an AT&T SIM.
I know what white list means but I don't understand what that has to do with what you are asking.
Also, just because the device is VoLTE capable, that does not necessarily mean you will be able to use the VoLTE feature on the AT&T network, even if you successfully activate the device on AT&T. VoLTE is controlled and regulated by the carrier, you will not be able to use VoLTE unless AT&T offers VoLTE support for your specific device, if they do not offer VoLTE support for your specific model number, you will not be able to use VoLTE on the AT&T network.
OP, it would help to know which model of phone.
My unlocked N10+ has no issues on AT&T.
Works identically to my AT&T N10+ variant.
Try talking to AT&T advanced technical support.
Droidriven said:
The same as any other device, SIM/carrier unlock the device then activate the device on AT&T using an AT&T SIM.
I know what white list means but I don't understand what that has to do with what you are asking.
Also, just because the device is VoLTE capable, that does not necessarily mean you will be able to use the VoLTE feature on the AT&T network, even if you successfully activate the device on AT&T. VoLTE is controlled and regulated by the carrier, you will not be able to use VoLTE unless AT&T offers VoLTE support for your specific device, if they do not offer VoLTE support for your specific model number, you will not be able to use VoLTE on the AT&T network.
Click to expand...
Click to collapse
Right. So VoLTE is a software program which must be present in the firmware of the phone. When AT&T developed their whitelist, they charged manufacturers to "certify" their VoLTE software on the AT&T network. The manufacturer of my phone (ASUS) along with many other manufacturers chose not to pay AT&T for the privilege of AT&T's customers continuing to use their (sometimes) relatively new devices (mine is barely two years old now, and I purchased it outright with the intention of using it for 5-6 years.)
So the software which runs VoLTE from my phone can be altered to work like one of AT&T's 'whitelisted' phones. This is discussed in this guide (as well as others) in which the final few steps has us replace the VoLTE programming with that of a phone from a different manufacturer.
My question is, supposing I can comfortably flash the .mbn file from a phone on AT&T's whitelist AND it works, what other information does AT&T have on my phone which might prevent my phone from connecting to their network? I believe that when I spoke to them and activated my IMEI they asked what phone I had. I think that based on the model information which I told them, it has been disabled*. If I were to tell them "oh, yeah, it's actually a Pixel 4" would there be any other checks which I'd have to spoof/bypass to continue using my phone?
*Also, I'm sure that my phone tried to make a 3g call which their system could have flagged. I'm working to reprogram my phone to only operate with VoLTE, so when I reactivate my phone that flag wouldn't reappear.
blackhawk said:
OP, it would help to know which model of phone.
My unlocked N10+ has no issues on AT&T.
Works identically to my AT&T N10+ variant.
Try talking to AT&T advanced technical support.
Click to expand...
Click to collapse
I didn't feel that my specific model was relevant and figured there's plenty of others wondering a similar thing as AT&T's actions are causing many perfectly good phones to go to disuse. I wanted this thread to generally discuss VoLTE programming and what, if any, recourse a power user might have to program their own non-whitelisted phone to conform with AT&T's network demands.
As you asked, and I would certainly appreciate any personalized assistance, I am using an ASUS ROG ii. The phone is VoLTE capable, and is functional on T-mobile's network, but ASUS apparently didn't want to pay AT&T to "certify" the phone on AT&T's network. I know no stock firmware coming from ASUS will allow me to connect to AT&T's network, but a procedure described in this guide ends with us flashing the .mbn file of a different phone onto ours to utilize "known working" VoLTE software.
I'm sure finding an .mbn that matches both the ROG ii's hardware AND is compatible with AT&T's network isn't going to be a breeze, but assuming that's possible - what other hurdles might I face with AT&T? If I call them to have my phone activated and tell them it's a pixel 4 what happens if I've programmed my phone to communicate on their network as though it were a pixel 4?
I don't think AT&T really cares that much as they're making a killing on the service.
The worst they will do unless it's illegal or specified in writing is to not support the device as far as troubleshooting it. Oddly some techs there will go out of their way sometimes to help you find out of box solutions.
Once you update it you may have to ask them to do a network reset on their end.
I always try to verify a device I'm getting is 100% compatible with their network, if not I return it.
That's one of the first shake down tests I do with a new phone.
This is why
healerdan said:
I didn't feel that my specific model was relevant and figured there's plenty of others wondering a similar thing as AT&T's actions are causing many perfectly good phones to go to disuse. I wanted this thread to generally discuss VoLTE programming and what, if any, recourse a power user might have to program their own non-whitelisted phone to conform with AT&T's network demands.
As you asked, and I would certainly appreciate any personalized assistance, I am using an ASUS ROG ii. The phone is VoLTE capable, and is functional on T-mobile's network, but ASUS apparently didn't want to pay AT&T to "certify" the phone on AT&T's network. I know no stock firmware coming from ASUS will allow me to connect to AT&T's network, but a procedure described in this guide ends with us flashing the .mbn file of a different phone onto ours to utilize "known working" VoLTE software.
I'm sure finding an .mbn that matches both the ROG ii's hardware AND is compatible with AT&T's network isn't going to be a breeze, but assuming that's possible - what other hurdles might I face with AT&T? If I call them to have my phone activated and tell them it's a pixel 4 what happens if I've programmed my phone to communicate on their network as though it were a pixel 4?
Click to expand...
Click to collapse
No, telling them you have a different phone isn't going to work. Your phone actually identifies itself to the network based upon a combination of hardware and software information that the network detects or receives from the device remotely, their job on the other end is to set their network up to provide service to the identified device and to identify the device and the service as yours. If you tell them that you have a Pixel 4 and they configure the network on their end to make VoLTE work with Pixel 4 then VoLTE more than likely will not work on your device because the system thinks you have Pixel 4 hardware and software when you actually don't. That is like asking a car parts store for a starter for a Ford engine when you actually need a starter for a Nissan engine, they'll give you what you ask for but it doesn't mean the Ford starter will actually work on the Nissan engine.
Trying to trick them into enabling VoLTE probably won't work, if their system does not offer VoLTE support for your hardware itself, you will not be able to use VoLTE.
It basically boils down to this, control of whether VoLTE will work for you or not is completely in their hands, not yours, it is all done from their end, there isn't really anything you can do from your end.
If you want to use VoLTE on their network, then you need to get a device that is compatible with their VoLTE service and is actually supported by their network.
Even if you find a shortcut to make VoLTE work, somehow, someway, you will not be satisfied with the end result.
Droidriven said:
If you tell them that you have a Pixel 4 and they configure the network on their end to make VoLTE work with Pixel 4 then VoLTE more than likely will not work on your device because the system thinks you have Pixel 4 hardware and software when you actually don't.
Click to expand...
Click to collapse
I think you are missing the part where I am using (in this example) programming and hardware from a pixel 4. this is only partly a hardware problem, but there's not as wide an array of different hardware types as you seem to think. a cursory search shows my device utilizes a snapdragon 855, and an X50 modem. The Oneplus 6T, which is permitted on AT&T's network utilizes the exact same hardware. The difference between the two phones is that Oneplus was ready to pay AT&T to check their software engineer's work.
Droidriven said:
That is like asking a car parts store for a starter for a Ford engine when you actually need a starter for a Nissan engine, they'll give you what you ask for but it doesn't mean the Ford starter will actually work on the Nissan engine.
Click to expand...
Click to collapse
If you want a car analogy it would be more like... I purchased an after market starter which has the same bolt& spindle pattern, and electrical configuration BUT when I connected everything ford's on-board diagnostics refused to start using a non-ford component. In this scenario, I have already done the starter installation and software patch, and know that these two things are operating as they should. I am now reaching out to the modder's forum to see if anyone knows of any other checks the OBD does to verify the starter which I should take into account while designing my patch before I turn on my car.
Droidriven said:
Trying to trick them into enabling VoLTE probably won't work, if their system does not offer VoLTE support for your hardware itself, you will not be able to use VoLTE.
Click to expand...
Click to collapse
See first response - the communications hardware is the same between my phone and other phones on their whitelist.
Droidriven said:
It basically boils down to this, control of whether VoLTE will work for you or not is completely in their hands, not yours, it is all done from their end, there isn't really anything you can do from your end.
Click to expand...
Click to collapse
VoLTE is just like any other communications protocol, it requires both devices to be able to communicate, and is a matter of both software and hardware. The thing that is lacking in my case is software, not hardware. and as the guide which I linked previously shows the software can be altered.
Droidriven said:
Your phone actually identifies itself to the network based upon a combination of hardware and software information that the network detects or receives from the device remotely, their job on the other end is to set their network up to provide service to the identified device and to identify the device and the service as yours.
Click to expand...
Click to collapse
This seems to be getting at what I'm actually asking. I'm trying to see what other items are involved in the "handshake" between my device and the network which might cause a flag. do you know what the "combination of hardware and software information" which the carrier's network uses to identify my phone would be, specifically?
healerdan said:
I think you are missing the part where I am using (in this example) programming and hardware from a pixel 4. this is only partly a hardware problem, but there's not as wide an array of different hardware types as you seem to think. a cursory search shows my device utilizes a snapdragon 855, and an X50 modem. The Oneplus 6T, which is permitted on AT&T's network utilizes the exact same hardware. The difference between the two phones is that Oneplus was ready to pay AT&T to check their software engineer's work.
If you want a car analogy it would be more like... I purchased an after market starter which has the same bolt& spindle pattern, and electrical configuration BUT when I connected everything ford's on-board diagnostics refused to start using a non-ford component. In this scenario, I have already done the starter installation and software patch, and know that these two things are operating as they should. I am now reaching out to the modder's forum to see if anyone knows of any other checks the OBD does to verify the starter which I should take into account while designing my patch before I turn on my car.
See first response - the communications hardware is the same between my phone and other phones on their whitelist.
VoLTE is just like any other communications protocol, it requires both devices to be able to communicate, and is a matter of both software and hardware. The thing that is lacking in my case is software, not hardware. and as the guide which I linked previously shows the software can be altered.
This seems to be getting at what I'm actually asking. I'm trying to see what other items are involved in the "handshake" between my device and the network which might cause a flag. do you know what the "combination of hardware and software information" which the carrier's network uses to identify my phone would be, specifically?
Click to expand...
Click to collapse
Actually, my car analogy was accurate, I don't think I explained why as well as I could have. The hardware/software differences that I'm referring to equate to the differing parts having the same purpose and same function but having differening bolt patterns the same as a Ford/Nissan starter sharing the same purpose and function but have differing bolt patterns.
Yes, another device might share the same hardware components and be approved but that doesn't necessarily mean that there is cross compatibility because the two devices have other differences that come into play.
When I say "if they support your hardware", I am not referring to ONLY the radio hardware, I mean the whole device being different hardware, which means differences in kernel also because kernel and hardware are very closely related which comes into play because these components also play a part in identifying the device remotely. Using a kernel from another device won't work either because the "other" hardware differences between the devices would cause the kernel from another device to brick your device.
You can modify software and you can emulate software but emulation at the hardware level isn't really feasible for android.
Some of the "handshakes" that identify your device come from things that if you modify them to make the network see your device as a different device, it may cause your device to lose functionality, other parts are illegal in certain places so they can't be discussed here.
It is such a rabbit hole that it is just all around more sensible to just use a device that is compatible without modifying. If you want to use VoLTE on AT&T, you'll have more success by playing their game because they hold the cards.
Why AT&T are shutting down all not AT&T phones on their Network | AT&T Community Forums
Why AT&T are shutting down all not AT&T phones on their Network?. Even if phones are working perfectly on AT&T network now and are 4G with VoLTE, Video Calling and WiFi calling capabil...
forums.att.com
List of supported unlocked phones and services available: