Develop Bugs

Can't Send SMS; Can Receive SMS/MMS & Send MMS

Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?

The newest firmware from the latest OTA can be found in the 2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2485319
If you've already flashed the latest firmware then I'm not sure what to tell you... maybe ask your favorite rom developer to take a look at the latest OTA in regards to this issue?

If it has the stock rom and OTA update why not take it to the store and let them look at it. Something might be wrong with your account.

movieman999 said:
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
Click to expand...
Click to collapse
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.

DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...

DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
movieman999 said:
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
Click to expand...
Click to collapse
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.

dickenam said:
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
Click to expand...
Click to collapse
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.

movieman999 said:
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
Click to expand...
Click to collapse
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk

dickenam said:
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
IM getting it now. but not exactly the same. phone freezes without warning and I have to toggle airplane mode and restart to get it to unfreeze. this happened after the last OTA update. I am going to a custom ROM until I don't read anything about this for a while

No sound when making, or receiving calls, same for those being called...

Hello fellow galaxy users, I have this problem on my T-mobile Samsung galaxy s4 and it is when I make a call, I cant hear anybody on the like or the dial tone or anything, and when the other picks up my call they can't hear anything either. Also if I pick up a call I still cannot hear anything. It is just plain silence. NOW HERE IS THE WEIRD PART! If I turn on wifi calling, I can call and receive calls with out any problems, if I use skype I can hear from the speaker and everything. So my mic is working, my speakers are working, everything seems to be functioning... Till I make a call using data... My guess is its a T-mobile network issue? I called T-mobile and they didn't know what was wrong... I looked around google and many people are having the same problem with no solution... If anyone has any ideas or any solution and would like more info on this problem, please let me know!
Have a nice day !

im having the same exact problem! i have seen some fixes that people have posted with similar issue, leading them to believe its something with their bluetooth/ok google/s voice being involved. ive tried some of the fixes that have been posted, but no luck on fixing the issue on my end. but just like you if i go on wifi and make a call i have no issues what so ever! the sound also works just fine if i connect to a bluetooth device.

Are both of you on the full NH7 firmware?

Mismatched bootloader?
Pp.

fully stock rom, not rooted. OS 4.4.4, yes nh7
i will add that this is my first galaxy, that i haven't rooted or changed the rom on. i have yet to have a reason to root or change the rom on this phone, but if i have to, to get this fixed? i have no problem rooting and changing the rom.
also i have noticed that i drop LTE to 4g when ever i try to make a call. the wife has the same phone and is on tmobile as well but she has not had this issue.

Ok, since you are stone stock this could be a update issue, just out curiosity I would try a factory reset (hard reset ) it may solve the issue . If not I would go with stock rooted like ShinySide's rom not full custom until issue is solved.
Pp.

ive done a hard reset and the problem is still there. i guess ill go the ShinySide's rom way, until i get my s5 or wait for the rumored s6.

This by ShinySide will give you an option to flash a stock firmware if you choose to be stock again. Follow instructions using Odin.
http://forum.xda-developers.com/showthread.php?p=54155517
Pp.

Need HELP Microphone/Dialer

I have tried installing multiple different custom rom's and I have also had the stock JB rom.
I don't know why, I really don't, but Custom rom's that are 4.3 or above mess around with my t989.
The calling never works, so say I just turned on my phone, it's just booted, I can make a few calls and everything is fine, the minute I hang up, and wana call another person within the next 3-5 Minutes, it's gone. It doesn't work anymore.
I don't get why the calling does not work on any KITKAT ROM.
It doesn't work on CM 10.1.3, 10.2, 11, Liquid smooth and now hellkat... it's a shame.
After a while, when you try to make a call or when you receive one, You can't hear the other side and the other side cannot hear you either.
I have had this problem with custom roms, specially 4.3 and above. Hellkat seems to be worse than CM11 calling wise, even though as I see, they have the same dialer and hellkat uses most of CM builds but still.. this sucks. I feel like it's either a software/rom problem or something disabled maybe, i'm not sure. I know, I have great connection (T-mobile) Data working, full signal and everything seems to be fine. However, I don't know what to do to even try to solve/fix it. I hope someone here know's though or someone here can help.
FYI; This doesn't happen on the stock rom (JB 4.1.2) At all. It never happens on stock, just on custom rom's and the only custom rom it doesn't do this on and works fine is ( CM 9.1)
Any solutions anyone knows of?
Thank you.

Replied to you in the other thread. Unless you've played around with different radios, I'm near 90% sure it's snapchat. I don't know why it borks the roms, someone smarter than I will have to answer that. All I do know is that several people with the exact same symptoms uninstalled snapchat and everything went back to normal.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app

LG G3 back to JellyBean

This may have been posted, If so, sorry, I could not find it.
Now that that I have installed the T-mo Lollipoop update, my phone is a paperweight. As I don't suppose T-mo will replace it....
Is there anyway to roll the LG-G3 back to KitKat or whatever version it was on WHEN IT WORKED PERFECTLY?
Any help would be appreciated, it is useless as it is.

Gdraft1 said:
This may have been posted, If so, sorry, I could not find it.
Now that that I have installed the T-mo Lollipoop update, my phone is a paperweight. As I don't suppose T-mo will replace it....
Is there anyway to roll the LG-G3 back to KitKat or whatever version it was on WHEN IT WORKED PERFECTLY?
Any help would be appreciated, it is useless as it is.
Click to expand...
Click to collapse
I ask this when fixing computers, why is it a paper weight lol.. whats wrong with the phone ? we need moar nfo ...

Paperweight
No or Spotty Wi/Fi
Cell signal has almost vanished (it I stand next to a T-mo tower I can get 5 bars for a minute)
Cell signal keeps dropping so the phone is constantly searching for a signal
Due to constantly searching for signals, the battery drain is actually watchable on the notification screen, about 1% a minute.
Phone will not stay connected long enough to complete a call.
All of these Issues happened after Lollipoop.
Hence, is there a way do "Upgrade" it back to Kit Kat.
I could not find anything on her about it. I did find a video on Youtube, but it was for a Verizon unit, not sure if it would be the same or not
I have two phones, same issue on both phones.

Gdraft1 said:
No or Spotty Wi/Fi
Cell signal has almost vanished (it I stand next to a T-mo tower I can get 5 bars for a minute)
Cell signal keeps dropping so the phone is constantly searching for a signal
Due to constantly searching for signals, the battery drain is actually watchable on the notification screen, about 1% a minute.
Phone will not stay connected long enough to complete a call.
All of these Issues happened after Lollipoop.
Hence, is there a way do "Upgrade" it back to Kit Kat.
I could not find anything on her about it. I did find a video on Youtube, but it was for a Verizon unit, not sure if it would be the same or not
I have two phones, same issue on both phones.
Click to expand...
Click to collapse
Unfortunately from my experiences and other people's experiences downgrading to Kitkat after Lollipop with data issues, you will still have those data issues when you go back to Kitkat. It seems going back to Kitkat via KDZ or TOT does not restore the modem or it does but the modem still does not function correctly. The only way to fix LTE and data issues was to flash Blisspop 2.3 and determining that data sticks on that rom. If it does, your data and modem issues should be resolved and you can use stock lollipop again. If you want to try this route here is my thread on how to fix it. Make sure you are rooted with twrp
http://forum.xda-developers.com/tmobile-lg-g3/help/lte-lollipop-issue-fix-t3075637

vel0city said:
Unfortunately from my experiences and other people's experiences downgrading to Kitkat after Lollipop with data issues, you will still have those data issues when you go back to Kitkat. It seems going back to Kitkat via KDZ or TOT does not restore the modem or it does but the modem still does not function correctly. The only way to fix LTE and data issues was to flash Blisspop 2.3 and determining that data sticks on that rom. If it does, your data and modem issues should be resolved and you can use stock lollipop again. If you want to try this route here is my thread on how to fix it. Make sure you are rooted with twrp
http://forum.xda-developers.com/tmobile-lg-g3/help/lte-lollipop-issue-fix-t3075637
Click to expand...
Click to collapse
Once I do that I will lose WiFi calling won't I?
It is my understanding once you over write T-mo's Rom you lose that.

Gdraft1 said:
Once I do that I will lose WiFi calling won't I?
It is my understanding once you over write T-mo's Rom you lose that.
Click to expand...
Click to collapse
Yes and No flashing blisspop rom will just fixed your data and LTE issues, I'm not telling you to keep the rom, that is entirely up to you. Yes keeping custom roms that are not stock will lose wifi calling and all the tmobile stuff. After you can confirm that LTE and data works you can then flash back to stock or restore to stock. That way you can still have Wifi calling and have a stock rom.

[SOLVED] Can't receive calls.....but I can make them? (very detailed thread)

I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!

I'm wondering if after doing the RUU my radio or something isn't at a proper level. Attached is a screenshot of my current bootloader. Anyone see something out of the ordinary that needs updating?

Yeah, I would go ahead and check with ATT if there are any bars on your account. Sounds like more of a network issue than a phone issue.

downbringer said:
Yeah, I would go ahead and check with ATT if there are any bars on your account. Sounds like more of a network issue than a phone issue.
Click to expand...
Click to collapse
Thanks for the reply! What would lead you to believe it's a network issue? I can make calls just fine and if I'm on the phone and someone calls me it works as if it normally would. Only issue is when someone calls me and I'm NOT on the phone.

Try turning off LTE, and see if you can get calls.
Some folks have been having issues with "international" based Sense ROMs not playing well with AT&T's LTE network upgrades (in preparation for Voice Over LTE). Not sure if this affects AOSP ROMs, but I have a feeling this is the problem.

redpoint73 said:
Try turning off LTE, and see if you can get calls.
Some folks have been having issues with "international" based Sense ROMs not playing well with AT&T's LTE network upgrades (in preparation for Voice Over LTE). Not sure if this affects AOSP ROMs, but I have a feeling this is the problem.
Click to expand...
Click to collapse
Wow......You, you're good you lol. @redpoint73
Sooooo yeah, changing my mobile data to 3G all of a sudden allows calls to come through. What exactly is at play here and how do I fix it?

italynstylion said:
What exactly is at play here and how do I fix it?
Click to expand...
Click to collapse
As I already described, AT&T is upgrading their LTE network for Voice Over LTE (they call it "HD Voice") and something in that upgrade doesn't seem to be playing well for some people on international based custom ROMs. In addition to voice call problems, you will probably also find SMS messages won't work on LTE.
Curiously, the problem seems to be very location specific. I've been running Skydragon Sense and LeeDroid for a few months, and on AT&T network. And everything has been working fine for me at my home location, as well as a few other locations around the country (I travel pretty occasionally for work). These are some of the ROM that others have had AT&T LTE issues with; and at one point even in the same city as another user that was suffering this issue (Chicago area). But for me, everything seemed to work fine.
The only real fix is to go back to stock AT&T based ROM. Folks have tried to flash various radios, and other things with no luck. Team Venom (Viper ROM) also said they would look into it a few months ago; but I don't think anything ever came of that.
An ingenious workaround posted by another user (if you want to stay on an international ROM): call AT&T and ask them to turn off HD Voice for your account. So you can still use LTE for data, but the call bug won't occur.
Of course, the downside for this is that you won't be able to utilize HD Voice. But that is probably the lesser of evils, if you want to stay on the current ROM.

redpoint73 said:
As I already described, AT&T is upgrading their LTE network for Voice Over LTE (they call it "HD Voice") and something in that upgrade doesn't seem to be playing well for some people on international based custom ROMs.
The only real fix is to go back to stock AT&T based ROM. Folks have tried to flash various radios, and other things with no luck.
An ingenious workaround posted by another user (if you want to stay on an international ROM): call AT&T and ask them to turn off HD Voice for your account. So you can still use LTE for data, but the call bug won't occur.
Of course, the downside for this is that you won't be able to utilize HD Voice. But that is probably the lesser of evils, if you want to stay on the current ROM.
Click to expand...
Click to collapse
This is brilliant. I'll give it a shot. Thanks for your help!

italynstylion said:
This is brilliant. I'll give it a shot. Thanks for your help!
Click to expand...
Click to collapse
I agree, its a good workaround. Especially since HD Voice requires users on both ends of the call to have a phone that supports the feature; and few phones for the time being have it. So having HD Voice turned off on your account (even if its deployed in your area) is probably mostly irrelevant.
You're quite welcome. And if you have a chance, please click the "Thanks" button for any posts you found helpful!

redpoint73 said:
I agree, its a good workaround. Especially since HD Voice requires users on both ends of the call to have a phone that supports the feature; and few phones for the time being have it. So having HD Voice turned off on your account (even if its deployed in your area) is probably mostly irrelevant.
You're quite welcome. And if you have a chance, please click the "Thanks" button for any posts you found helpful!
Click to expand...
Click to collapse
Just got off the phone with AT&T and everything is just peachy again. I updated the first post with the solution/fix. Thanks so much for your help!

italynstylion said:
Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues.
Click to expand...
Click to collapse
Interesting. I wonder if HD Voice hasn't been activated on my account yet; and that is why I haven't had this issue while others have?

redpoint73 said:
Interesting. I wonder if HD Voice hasn't been activated on my account yet; and that is why I haven't had this issue while others have?
Click to expand...
Click to collapse
It's certainly possible. I live in Dallas which is a fairly large area. It wouldn't surprise me if we were one of the areas that got it first. Sucks being a guinea pig but I've left a trail of breadcrumbs for everyone else to follow.

italynstylion said:
It's certainly possible. I live in Dallas which is a fairly large area. It wouldn't surprise me if we were one of the areas that got it first. Sucks being a guinea pig but I've left a trail of breadcrumbs for everyone else to follow.
Click to expand...
Click to collapse
I'm in Boston area, and according to the AT&T maps, HD Voice is working here.
Although, I got the M8 long before it supported the feature (they added it with the 4.4.4 OTA). So I don't know how they decide when to activate it on your account; but if its device related, I can see how it might not be on mine yet.

italynstylion said:
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
Click to expand...
Click to collapse
Thanks for the post this helped me with my issue!!!

Have any of you tried to disable enhanced 4G LTE Mode in network settings instead of slowing you down to 3g?
goo.gl/photos/BX9N2b37Z2Wb1UeQA
[/QUOTE]
italynstylion said:
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
Click to expand...
Click to collapse

phgojiya said:
Have any of you tried to disable enhanced 4G LTE Mode in network settings instead of slowing you down to 3g?
goo.gl/photos/BX9N2b37Z2Wb1UeQA
Click to expand...
Click to collapse
[/QUOTE]
What ROM are you on? I dont have that option to turn off enhanced LTE on my network settings page

grafik2 said:
What ROM are you on? I dont have that option to turn off enhanced LTE on my network settings page
Click to expand...
Click to collapse
If you are on AT&T and suffering this problem, my advice would be to call AT&T and ask them to turn off HD Voice on your account. The enhanced LTE setting on the phone does nothing to help this problem.

redpoint73 said:
If you are on AT&T and suffering this problem, my advice would be to call AT&T and ask them to turn off HD Voice on your account. The enhanced LTE setting on the phone does nothing to help this problem.
Click to expand...
Click to collapse
Gotcha.
i had this happen to me once months ago maybe even a year ago and i called and they turned HD voice off and it worked. it started happening again last week I wonder if ATT reapplied the HD voice setting for some reason

italynstylion said:
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
Click to expand...
Click to collapse
Thank you so much! I've been looking everywhere for a solution after I installed the Resurrection Remix Rom 5.7.4 on a replacement HTC M8 that I bought new. Love these now 3+ year old phones but not recieving phone calls was crazy. I thought I would be forced to go back to stock.