Related
Hello All,
I have been looking around and seeing if anyone else is experiencing the same issue I have. But I have not had much luck. I have seen similar cases, but for whatever reason, some of the workarounds found that worked for others have not been successful for myself, or are temporary.
For the past three months, I have been experiencing an off and on issue where I am unable to receive texts, but I am able to send out text. And it is something that I would not realize until people actually notify me, or it is awkwardly silent on the "texting front", which makes me second guess myself. Almost every other week or two weeks this has occurred. At the time, I am running Darky's 8.8 [4.1.2] ROM for the i9300. I have tried rebooting, taking out the SIM, re-flashing Darky and re-flashing Stock (full wipe, etc), and replacing my old SIM with a new one. None have been successful thus far. The only success I have found is that inserting my SIM in a different phones allows the text to flow through almost immediately. I would then place the SIM back in the i9300 and any new texts sent I would receive immediately. After a week or two, it randomly just stops receiving text again, and the cycle continues.
I was wondering if whether this may be a bug with the Android OS itself? I have seen a few posts in regards to SMS being handled by Jelly Bean, but I am not 100% sure if my issue would fall in the same boat. Or if it is possibly faulty hardware? Or some kind of network issue. My network is AT&T, but I'm ruling out a network issue since I am able to receive text almost instantaneously on other phones.
Any information, advice, or help would be greatly appreciated.
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
JJEgan said:
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
Click to expand...
Click to collapse
I've verified that the MMS APNs and SMS settings are correctly configured to AT&Ts network. If it were incorrect from the beginning, I would not get text messages (or MMS) at all. But in this case, it is intermittent and only resolved when I get to "unload" the text messages on to another device.
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
b-eock said:
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
Click to expand...
Click to collapse
Ahh! Thank you b-eock! I don't mean this in the wrong way, but I'm glad that I'm not the only who has experienced this. When this occurred to you, were you on some version of 4.1.2? From what I can remember, this issue never came up until I upgraded from 4.1.1 to 4.1.2. Just trying to find some kind of trend here...
I have had to call up AT&T a number of times regarding this issue. And each time they were of no help. Although they were able to confirm that everything on their end of setup correctly, I got the same BS that you got. And they even gave me the whole baloney that I should upgrade so that they can help assist me better and that since it is not their branded phone, it may not be fully compatible.
I really do not want to give up on this. And I definitely want to find a solution. So I am hoping there is a lucky one out there that has tried different ways of getting fixed. Whether that be trying a new ROM, or downgrading from Jelly Bean to ICS, etc.
Came up a few weeks after I upgraded to 4.1.2 but there isn't really a connection between that. It worked before. Its just random crap. And them telling us everything is good on their end, that's complete BS. They don't know what's going on behind their computer screen.
Same exact thing happens to me. It's ROM dependent i'm thinking. Samsung roms from other countries do it the most for me. Has done it on AT&T and AT&T with StraightTalk. Experiencing it on Purelok HD v3.1 right now. I love this rom but im probably going to go AOSP/AOKP as I don't experience it on those kind of roms.
Camera just isn't the same without the Samsung software to me.
Ok so I (foolishly) bought a galaxy s4 with verizon even though I was moving overseas to Israel in two months. I made sure that the phone was world capable (like it can do cdma and gsm) and the guy at the store said it would handle foreign sims no problem. Once I arrived here I got a new sim. I figured out that it needed to be in gsm. From then on it had the service bar and confirmed it was connected to Orange. Since then I have been able to receive calls and texts, but not make them, every time I try to make a call before one ring I get a prerecorded message saying that my number cant be completed as dialed. I have tried several things already to fix this: to a cell phone repair person, to the local sim carrier where a lady tried using the sim of her own phone, customer service at verizon and samsung (who both told me to go see the other). I also did a factory reset which didnt do anything.
my phone is not rooted and is schi545 ME7. I will root if I have to, but if I dont I would prefer not to for the time being
Anyway I suspect the problem has something to do with the fact that I got the phone from verizon. Every time I start the phone I get the Verizon logo and after a minute I get a notification from the verizon set up wizard saying that I have a non verizon sim and that the sims source is unknown. I also tried disabling the verizon security and was able to make the notification go away but the problem persists.
Can someone with experience with this kind of stuff help me please? Thank you so very much:good:
Are you sim unlocked? I don't think the phone is unlocked. Talk to verizon to see if they'll unlock it.
According to verizon I am. I spoke with multiple representives from verizon and they said the phone was unlocked
medphratalon said:
According to verizon I am. I spoke with multiple representives from verizon and they said the phone was unlocked
Click to expand...
Click to collapse
Has any one told you if you have to change any apn, access point name? That may be the problem too. They can be specific to the carrier.
No, how do you configure that
medphratalon said:
No, how do you configure that
Click to expand...
Click to collapse
In system settings, network & wireless, more, mobile networks, access point name. It'll be specific to the carrier so i can't help you there.
all LTE Verizon phones after Galaxy Note 2 are factory unlocked it must be a APN issue. Try maybe to do a factory reset and as previous poster suggested do the steps he told you to change the APN or look into I think it's called HiApn in Play Store.
Also try to put it in global mode or GSM? play with the settings.
still having problems
Thanks for all the input everyone but my problem still persists
I downloaded HiApn and followed its instructions to which told me to set up 3 Apns. I noticed that only one of them can be active at the time. I tried with each one active and I still can not make phone calls. Does anyone have any other ideas?
medphratalon said:
Ok so I (foolishly) bought a galaxy s4 with verizon even though I was moving overseas to Israel in two months. I made sure that the phone was world capable (like it can do cdma and gsm) and the guy at the store said it would handle foreign sims no problem. Once I arrived here I got a new sim. I figured out that it needed to be in gsm. From then on it had the service bar and confirmed it was connected to Orange. Since then I have been able to receive calls and texts, but not make them, every time I try to make a call before one ring I get a prerecorded message saying that my number cant be completed as dialed. I have tried several things already to fix this: to a cell phone repair person, to the local sim carrier where a lady tried using the sim of her own phone, customer service at verizon and samsung (who both told me to go see the other). I also did a factory reset which didnt do anything.
my phone is not rooted and is schi545 ME7. I will root if I have to, but if I dont I would prefer not to for the time being
Anyway I suspect the problem has something to do with the fact that I got the phone from verizon. Every time I start the phone I get the Verizon logo and after a minute I get a notification from the verizon set up wizard saying that I have a non verizon sim and that the sims source is unknown. I also tried disabling the verizon security and was able to make the notification go away but the problem persists.
Can someone with experience with this kind of stuff help me please? Thank you so very much:good:
Click to expand...
Click to collapse
Go to Setting, call setting, disable the prefix international. I have done the same for using Verizon S4 in Indonesia.
Mine was not unlocked either, although I knew this before buying. This is a guide I tried (without success) to unlock it on my own.
Like the last poster, I reside in Indonesia, but I was never with Verizon. I rooted mine and have had no problems since.
Ok so I went to call settings and the closest I found was assisted dialing for international calls and the option to turn it on or off. I played with that for a bit and it didnt work.
I also tried the code and it said connection problem or invalid code
during my fiddling I came upon an app that showed promise of fixing my problem if I had adb shell. Does anyone have a good place to get that? I tried a few that didnt work out for me. There was another that showed promise but it wouldnt send a package no matter what I try
Thanks
If you want ADB, you need to download Android SDK and have Java Runtime Environment also installed. Then, it is just a matter of typing in "adb" into the command prompt of Windows.
Is there a serious conflict for you not rooting the device? The true benefit of doing this is to get SIM cards from anywhere to work, and to allow certain apps to work. Rooting is simply a matter of bypassing security parameters. As long as you follow instructions strictly, you won't have an issue using the phone as it should be used.
yea I suppose I could try to root it. Im just not great at that stuff and am worried about messing up my phone permanately
medphratalon said:
yea I suppose I could try to root it. Im just not great at that stuff and am worried about messing up my phone permanately
Click to expand...
Click to collapse
You don't need to root. You need to sim unlock. Get a hold of att international chat and adj them for an unlock code.
Hey guys thanks for all the help but I figured out that it was just a bad sim all along and that the first school screwed me over
But everything works now
I have the AT&T Galaxy Mega i527 I got the phone a little over a month ago and had it unlocked and running on T Mobile perfectly well a few days ago it stopped working so after calling Samsung and making a few more calls I'm being told im Blacklisted, so after paying The Unlock Pro's to fix this im getting full Data at over 10MBPS at all time and as far as I can tell my Text work but Calling Out/Receiving Calls has major issues! when it does(rarely does) call out it will take forever to start ringing and most of the time it will drop the call..please help!!
banks2878 said:
I have the AT&T Galaxy Mega i527 I got the phone a little over a month ago and had it unlocked and running on T Mobile perfectly well a few days ago it stopped working so after calling Samsung and making a few more calls I'm being told im Blacklisted, so after paying The Unlock Pro's to fix this im getting full Data at over 10MBPS at all time and as far as I can tell my Text work but Calling Out/Receiving Calls has major issues! when it does(rarely does) call out it will take forever to start ringing and most of the time it will drop the call..please help!!
Click to expand...
Click to collapse
If your getting full data you can use various apps to make and receive calls and text like mo+ or grooveip to name a few. I believe you need a google number to use the aforementioned. There are some that provide a number for you like talkatone.
cakegetter said:
If your getting full data you can use various apps to make and receive calls and text like mo+ or grooveip to name a few. I believe you need a google number to use the aforementioned. There are some that provide a number for you like talkatone.
Click to expand...
Click to collapse
Those will all stop working as of mid-May. Google will be disabling external VoIP functions then.
Another alternative is skype. I pay 2.99 a month for unlimited calling in the US, you can also receive calls from landlines through skype. I think that service is like $7 a month. Hopefully this will help with your problem.
Can you check on http://www.t-mobile.com/verifyIMEI.aspx ?
banks2878 said:
I have the AT&T Galaxy Mega i527 I got the phone a little over a month ago and had it unlocked and running on T Mobile perfectly well a few days ago it stopped working so after calling Samsung and making a few more calls I'm being told im Blacklisted, so after paying The Unlock Pro's to fix this im getting full Data at over 10MBPS at all time and as far as I can tell my Text work but Calling Out/Receiving Calls has major issues! when it does(rarely does) call out it will take forever to start ringing and most of the time it will drop the call..please help!!
Click to expand...
Click to collapse
Google for checkesnfree, can verify if phones are blacklisted there.
Possible 1)
Dial *#0011# with your sim card inside. Look for something called "IMEI CERT". If it says "Fail" (or not listed at all) then the problem is "The Unlock Pro's" have buggered your NVM. And without a proper backup of your original NVM, nothing to do.
Possible 2)
Flash the stock modem for your Mega (newest version only) and kernel only. Wipe data/factory reset, then reapply your APN settings. Make sure to do a manual select on the network.
Possible 3)
Dial *#06#, write down your IMEI, then pull your battery out and look at the sticker on back and see if the IMEI on the sticker matches. If it doesn't then they have altered your IMEI (which is illegal by the way), and put your IMEI to one that is in use by another phone.
thanks for all the reply's!!! do you guys kno where I could download the modem for this phone?? I had to download an re-install the modem on my Unlocked AT&T S3 I747 I had on Metro
just to give a update im still having the calling out/receiving calls problem , the company I paid 60 to fix the IMEI refuses to even respond to my e-mails.. I jus find it weird im still getting full data at all times and the phone has the 4G LTE sign at the top right of the screen until I go to make a call then it jus goes to a regular 4G sign with no LTE. also I've noticed the calling out/receiving calls feature works fine depending where im at like for instance I went to the hash bash in Ann Arbor the other day and everything was working fine.. im thinking im going to just send the phone to Joe The Android Rooter and see if he has luck getting it figured out. I'm jus sick of this thing being a money pitt..
SaHiLzZ said:
Can you check on http://www.t-mobile.com/verifyIMEI.aspx ?
Click to expand...
Click to collapse
Thanks. That was helpful thread in your promoted link.
I've got a rooted unlocked s-off AT&T M8. I took the 4.4.4 update, then promptly moved to ARHD 34.0. Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. What I'm trying to figure out is, how was I able to have my stock rom on AT&T in LTE mode and still receive a call?
I've checked all the APN settings and it all is set to recommended parameters on AT&T's website. Is this an Android Revolution HD issue? SIM issue? AT&T issue?
I'm going to have to back out of ARHD if there is no solution here, and that would suck.
thanks.
ARHD 34.0 is Android 5.0 based (software 4.16); not 4.4.4 (software 3.x). You might be experiencing this issue due to firmware mismatch. My advice would be to flash the US Dev Edition RUU or firmware zip to get on the 4.x based firmware, and see if that helps. You can try the Euro 4.16.401 firmware, but my experience the US Dev Edition (4.16.1540) plays better on AT&T (as its designed to work on AT&T's network).
Even with the proper firmware, some folks have also had some random network issues running an "international" based ROM on AT&T's network. Most notably losing Google services while on LTE (possibly due to build.prop differences). So its possible your LTE issue may be related. Not to knock the ROM developers, but devs from Europe and other regions often aren't that familiar with the nuances of AT&T's network.
So if being on the proper firmware still does not resolve the issue, it might be the ROM itself doesn't play well with AT&T in your location.
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Thanks again.
jeremyenos said:
Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. .
Click to expand...
Click to collapse
Voice over LTE (VoLTE) not being available yet should not be the cause. VoLTE is not currently available on most carrier worldwide. Its a very new technology, and deployment is still ongoing in most regions. Only a few Asian countries currently have VoLTE.
That being the case, voice calls should be kicking down to 3G. The lack of VoLTE should not prevent you from receiving calls. As mentioned, I believe the issue is either a firmware mismatch, or ROM not playing well on AT&T's network.
---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------
jeremyenos said:
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Click to expand...
Click to collapse
No, you don't need to convert to GPE to run Dev Edition RUU. Dev Ed not the same as GPE. Dev Ed is Sense, just without the AT&T branding. The US Dev Edition Lollipop ROM is actually pretty sweet (what I am currently on via RUU).
You won't likely brick the device with RUU unless you run an RUU for the wrong device.
Changing CID is safe as long as you type the command properly.
There is always some tiny risk of a brick if you mess with things s-off, and flashing hboot and radio. But I wouldn't say the risk is any more than installing the OTA (which also replaces hboot and radio) as long as you follow instructions carefully, and do the proper research, and take the proper care while performing the steps.
So thanks redpoint for the advice-
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Kind of surprised by this if I'm on the only one hitting the issue... all of the issues. To my knowledge, without a radio update, no AT&T m8 in America with ARHD 34 is going to be receiving incoming calls with LTE enabled. The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Maybe I've got this all wrong somehow... I can't be the only ARHD m8 AT&T LTE USA user that wants to have incoming calls right? How has anyone else accomplished this?
Stuck with Cyanogenmod for now... slower, less stable than ARHD.
jeremyenos said:
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Click to expand...
Click to collapse
You're still misunderstanding about Dev Edition (DE) versus GPE. Only GPE has different partitioning from Sense. DE is still Sense, and has the same partitioning scheme as the stock AT&T (and other carrier) Sense setup.
Don't know why you are having the issues restoring ARHD nandroid and even flashing ARHD. Wipe cache and try to re-install TWRP or try a different version. Then try a "clean install" (factory reset in TWRP) of ARHD.
Or you might have a case where the DE firmware does not play well with ARHD. You can try the 401 firmware, for which ARHD is based. But this might cause as many issues as it solves, as the US DE firmware usually plays better with AT&T's network than the international firmware. But it might be worth a try.
---------- Post added at 11:31 AM ---------- Previous post was at 11:27 AM ----------
jeremyenos said:
The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Click to expand...
Click to collapse
Since you are s-off, you can flash any carrier's M8 firmware, or flash the radio independently. Although a side note that you should stay away from flashing anything for CDMA (Sprint & VErizon) M8's or dual SIM M8.
If you mean there is no updated LP radio intended for AT&T, aside from the DE RUU that you are currently on; than yes that is correct.
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
redpoint had my problem pegged. Just had the wrong rom w/o the radio update I think. I needed to get the developer edition from here. After applying it, I could put ARHD back on and all was good. It's been awhile, but that's how I roughly remember it.
simpl3lang said:
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
Click to expand...
Click to collapse
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
thank you for the quick reply. i will call at&t right now. and i will throw in an update.
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
simpl3lang said:
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Click to expand...
Click to collapse
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
simpl3lang said:
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
Click to expand...
Click to collapse
Swapping radios or APNs probably won't help. Not sure about reverting to Kitkat.
redpoint73 said:
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
.
Click to expand...
Click to collapse
+1000000000000000000
i guess third time calling is the charm. the first 2 calls i made, they said they couldnt turn it off, saying it was restricted. but the third person i spoke to made me turn my phone off and when it restarted it worked. i can receive calls now.. he said he turned the hd lte off in his side by putting me back to the settings i had before hd voice was added.
thanks again.
edit:
i was actually looking at this prior to making my third call to at&t. maybe it could help others. worth a try? do it at your own risk...
If for some reason the HD Voice Calling option is disabled or inaccessible on your phone after updating to Android 5.1, then you can try the following steps to fix the issue.
Navigate to Settings > More > Cellular Networks and enable the toggle switch for Enhanced 4G LTE Mode. However, if the toggle is missing then follow the steps provided below:
1.Launch the Dialer app on your phone, and dial *#*#4636#*#*.
2.Choose Phone information.
3.Enable or select VoLTE Provisioned Flag.
4.Restart the phone.
5.Go to Settings " More " Cellular networks and toggle the switch for Enhanced 4G LTE Mode, and the HD Voice calling feature should now be activated on your device running Android 5.1.
i got as far as rebooting my phone but the toggle was still missing.
Was working on Insert Coin 4.4.4, flash to OTA 4.16 5.0.2 works fine then I flashed to latest Insert Coin 7.1.9 5.0.2 I tried the following step suggested on post #13 don't see option #3 after click Choose Phone Info.
By calling AT&T turn off HD Voice you'll sacrifice anything?
First call attempt, att technical rep had me turn off phone, 1min later turn it back on and it's working now! Yay!!!
Sent from my HTC One_M8 using Tapatalk
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
tc3sean said:
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
Click to expand...
Click to collapse
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
redpoint73 said:
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
Click to expand...
Click to collapse
I can confirm that getting AT&T to turn off HD Voice fixed the issue with me. I installed SkyDragon v10. I had to call twice and go through a lot of crap to get them to do it. The last guy told me he was going to put the "opt-out" code on my number, but that wasn't technically supposed to do it. He said he was putting in that I had "requested" to opt-out (I was taking the line that it just stopped working, as I didn't want to have to deal with any fallout about having rooted and flashed my phone, perhaps that wasn't necessary, idk). So, I think you might take the short cut by saying that you want to opt out of HD voice, and that your "Brother-in-law" just did it, so you know it works. If you stick to your guns, and ask for a technical person and don't let them say no to that, you can definitely get it done.
Thanks to all of the participants on this thread I am out of a tight spot and would like to offer up a few more observations that may be helpful to the next person.
I had an LG G3 running CM13 20160504 that became unstable and I had to replace with my wife's old HTC One m8 also running CM13 20160504 (also tried 20160510 and 20160511) which, like the other phones discussed in this thread, did not get incoming calls, in fact calls did not even roll over to my Google Voice number.
Thanks to this thread I tried forcing the phone to 3g, found that I got calls and then got AT&T to turn of VoLTE (aka HD Voice) and now I can get calls while running with LTE data.
Rather than a fire-hose of details I'll just say that it seems that the G3 would get incoming calls on LTE, and I would not get the first ring then it would ring on what the caller perceived as the second ring. Whenever I was on a call I would note that I was running in 3G, after the call it went back to LTE. I assumed that it was a bandwidth issue but now I think in that lag between the callers first ring and my first ring the phone was negotiating down to a 3G connection like an old school high speed modem negotiating a call with a slower modem (anyone remember those days?). It looks like my HTC does not have the ability to negotiate down or that it was been somehow hardwired not to as there is a flag in the test menu (*#*#4636#*#*) marked "TURN OFF VOLTE PROVISIONED FLAG" which has no effect, i.e. I can press it and the is a visible deflection indicating that the phone knows that the button was pressed but the button text does not change to indicate that a toggle has been effected, calls continue to not ring and even rebooting after pressing does not make any difference.
In summary, having AT&T turn off HD Voice has me working fine with the HTC On m8 on CM13 and I am grateful to all of you for the conversation that got me out of that corner.
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
Carrier texts should theoretically still work as they are "data". It's the "voice" part of VoLTE that won't work. That's why I can still receive carrier texts on my Galaxy Note 9 with AT&T -- which still has older firmware (so I can be rooted). A few months ago, I lost the ability to make/receive phone calls on my AT&T number when 3G towers were decommissioned in my area... But luckily I have Google Voice number, which also uses "data" (VoIP) so I make/receive all my Google Voice phone calls. (That's been my main phone number for years.)
However, I no longer can make/receive AT&T phone number calls -- which is fine. I switched Google Voice settings to data/Wi-Fi only instead of piggy backing on carrier phone number. Yet, I still receive AT&T texts, which is good because my bank insists on using a "real" (carrier) phone number for SMS security code confirmation.
Amer28 said:
Hello!
Can someone please help me with this?
Everything was fine until 2-3 days ago. When all of a sudden I was unable to send text messages or make phone calls. All the while I could access internet without any issues.
If I switch to 2G or EDGE for the Subnetwork, I can make calls and send SMS.
How can I fix this?
Could dropping the phone have caused this?
Click to expand...
Click to collapse
You are in Portland? What carrier are you using that still has 2G and Edge?
ChazzMatt said:
You are in Portland? What carrier are you using that still has 2G and Edge?
Click to expand...
Click to collapse
I'm with a company that uses T-Mobile towers. I connect just fine with 4G LTE, and get reasonably good speeds over it. But when I'm on 4G, I cannot make or receive calls or text. It says Emergency Calls Only.
So far, I've tried everything. I resettled network. I looked for different APN values that may fix the issue. When I couldn't think of anything else, I did a factory reset. (I mean, I wiped Data, and all other partitions in TWRP except for System and SD Card.) There have been no changes.
I'm starting to think the issue may be hardware, I did drop the phone a couple of times the day it stopped working. Though I usually end up dropping the phone once a day or every two days. I can't believe the screen hasn't cracked yet, at all. Could a drop from 3-4 feet on hard surface like tiles damage the antenna in such a way that only 4G data works?
I'm ready to give up and buy a new phone even though I can't really afford it. It would be awesome if I can get this to work.
schwinn8 said:
Dropping could certainly break something, of course, but let's assume that's not it.
What carrier? Is the phone officially supported by them (ie, IMEI matches the carrier)? Are you on their official ROM? Does/did your VOLTE work (before and after the "few days ago")?
Some carriers are switching over to VOLTE-only setups, so they may be testing that to see what works/doesn't before they make it final. In other words, maybe your phone is not "officially" supported by VOLTE on the carrier, which is why it's failing? Without VOLTE, I think text may fail as well (even if you're not actively on a call?)
That would be my first guess. In my case, for example, I was on a US998 phone (per IMEI) running VS996 on Verizon. Since the IMEI didn't match a VZ phone, they refused to say it was compatible (even though it worked fine for many years). The IMEI stuff is a bunch of BS, but that's a whole separate topic... but I wonder if this is what you're running into. It's the carrier's way to force you into "their" device, even though it's not any different from any other variant (when the proper ROM is installed).
Click to expand...
Click to collapse
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
I want to also mention that my carrier website has been talking about a data migration that would affect phones using their old SIM Card.
When I saw that, I called them and had them send me a new SIM. I thought surely this must be it, but the new SIM works exactly like the old one.
Perhaps the migration or whatever it is they did that required new SIM cards just doesn't work well with my phone? Even though, before putting the order in, the rep I spoke to did check my IMEI and said that my phone is compatible.
Agreed, it doesn't sound like an IMEI issue.
FWIW, I showed a 4G connection on a phone (I don't remember if it was my V30 or a Galaxy S10+ that I was going to replace it with). On that phone, at one point, but there was no actual connection. So, the indicators aren't always accurate. That's why I thought maybe the data isn't really working, and if data isn't working then VOLTE won't work... and with many of the carriers switching off non-VOLTE calling, that could kill the ability to make calls?
In your case, you said data worked... but if VOLTE was never enabled, and the carrier dropped non-VOLTE, then, again, you may lose calling.
In any case, these were my theories. I think you're on top of the situation but I don't have any other ideas for you to try...
Instead of buying a new phone, have you considered installing and setting up Google Voice, as ChazzMatt said? I recently had to do that because AT&T's 3G shutdown meant that I could no longer place or receive calls. My quick guide on doing that is here: https://forum.xda-developers.com/t/...-based-custom-roms-when.4138223/post-87342453
I don't know why you can't also send or receive texts, but the Google Voice app has the ability to do that, so maybe try using that after you've set it up.
Amer28 said:
I'm on T-Mobile towers with the US998. I don't think there is an issue with IMEI. How would I connect to data with 4G if that was the case?
I never had Volte on this phone. I do recall seeing it when I first got it but I'm running stock rooted Android 9.
When I say it used to work a few days ago, I mean it just stopped working at one point. I wanted to make a phone call, and all of a sudden, I couldn't. I noticed then that it says Emergency Only sign, so I walked around the house for about 15 mins to try to get signal. Then I went to my car and drove around, but nothing.
I messed around with Network settings, and figured out that Voice and TXT worked when I switch to a lower 'Sub-Network' setting that says, "GSM / GSPR / EDGE Only".
To get 4G Data back, I have to switch it back to "LTE/Legacy 3GPP multi"
These two are found under "GSM/UMTS Settings", after clicking on "System Select" in "Mobile Networks ".
Click to expand...
Click to collapse
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
ChazzMatt said:
There's been reports T-Mobile which is now merged with Sprint has borked the ability for VoLTE/VoWiFi calling on US998 firmware phones (native or Frankenstein'ed). Apparently they only allow it now on T-Mobile H932, whereas pre merger they were happy to give VoLTE and voWi-Fi calling to "US998" phones
First, it was reported with new SIM cards they were distributing earlier this year. Then people who kept their old SIM cards found they didn't work after a forced "security update."
This seems to have also trickled down to the T-Mobile MVNOs.
This is why we told someone else recently they should probably convert their phone from US998 on T-Mobile to Verizon VS996 firmware.
Then get a Verizon sim card or Verizon MVNO SIM card, and activate it in an old cracked screen Verizon phone off eBay, then put that already-activated SIM card into their "VS996" V30.
They will have VoLTE and VoWi-Fi calling.
Alternatively, if you really want to stick with T-Mobile network, you can do what @osprey00 suggested -- which is get a Google Voice number and use it as a tool to forward your carrier calls to it.
You can read his post, see his experiences, and see if this would apply to you.
For ME -- I've been using Google Voice for the past 10 years as my main phone number. I ported my carrier phone number at the time to Google Voice. Then got throwaway carrier numbers (whoever had cheapest plan) but never gave those to my friends. To my friends nothing ever changed. I've had the same "number" for the past two decades.
But within the past couple years, I had to start giving my bank and my cable company my carrier phone number for SMS security codes. Very annoying, because in the past they used my Google Voice number to text me with no problem.
So, even though under my current firmware (on my rooted Note 9) I cannot get carrier phone calls, I still have LTE data. And with the LTE data, I can use Google Voice (calls and texts) because it's VoIP. I also get AT&t carrier texts, as that is also data. It's just AT&T phone calls I cannot send or receive.
AT&T deactivated the SIM card in my native US998 V30+ and sent me a replacement phone, which is a Samsung Note 9. I'm staying with AT&T for a reason. Otherwise I would probably pull the "V30" Verizon trick also.
I bought both my wife and my elderly mother 64GB V35 phones -- which is basically an upgraded 64GB V30. (They previously had native US998 V30.) AT&T gives V35 VoLTE and WiFi calling, and for them there was nothing new to learn.
Click to expand...
Click to collapse
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Amer28 said:
I think it was a hardware problem, honestly.
No matter what I did, I even tried different ROM to ensure I didn't mess around with root settings and somehow enabled or disabled something that I should not have. I tried flashing stock radios, and no, nothing would fix it.
I took my brothers phone to see if the SIM card would work with his phone, an unlocked Google FI phone. As soon as I installed the SIM, and booted up the phone, I could tell it was working perfectly even on the lock screen. Right away the status showed the name of the wireless company, and active 5G data icon on the status.
I must have damaged the internal radio or the LTE data modem when I dropped the phone last. The screen of the phone never broke even though I dropped the phone countless times, though the back glass has cracked lines all over even if the surface is still smooth and the phone continued being waterproof (I tested).
Anyway, I have since bought a new phone and the Data/Text/Talk all work perfectly on it.
I'm not sure what I'll do with this phone, as selling it wouldn't be ethical. And I doubt anyone would buy a phone with the warning that service may not work.
Ah well, I may just keep and use it as a test device.
Thanks to all who tried to help.
Click to expand...
Click to collapse
tried a rom on a j7 2015 because android 6 is going to be left and I only get emergency calls on lte and on 3g, no problem. It's not imei problem maybe exynos processor. I went back to 6.0.1 and no problem with 4g lite. By the way, I'm not in the USA.