Related
Ok, this is driving me nuts. Maybe someone has some additional ideas on what I could try out.
First of all, I am on Verizon in the SE Michigan area. At work I hover around 2-3bars 4G/full bars 3G. The same thing at my home. I am rooted and w/ 4.0.4.
I have tried the 4.0.4 radios, the hybrid 2 and hybrid 3 radios. For all of them I get similar behavior.
I would say almost half of the time when I request data (try to open a website, etc...) or if I try to place a call I get a total connection drop even though a stable connection (either 3g or 4g) is indicated. Call won't complete and/or data won't work - no bars and a little gray x. This is when I have a completely fine connection, it just seems to crap out when I request either data or a call. After about 30 seconds or so the connections automatically resets itself and it appears to be fine. Occasionally i need to restart my phone.
I've been getting this with 4.0.3 non rooted and 4.0.4 rooted with all the above radios. it's a massive pain in the ass. I had no such issues with my DInc and my gf has no such issues with her Razr.
Any ideas?
I would say you have bad signal, despite what your signal bars may show. No amount of data drops will stop a call from being completed unless it is a complete loss of signal.
The other possibility is something is causing the ril to crash. However without you supplying a logcat, there is no way to be sure.
So, do you think this may be a hardware problem? I am getting "no connection" when I try to make calls in areas where no one else appears to be having issues. Do I need to throw my phone against a wall and use my insurance for a new one?
Ok, ill run logcat and post when it happens again.
Sorry for borrowing your thread, but I also seem to face signal drops and don't know if it's because of carrier breakdowns or something else. I have the XXLA2 radio and run the latest AOKP.
My logcat is attached, if anyone wants to help me.
Theshawty said:
Sorry for borrowing your thread, but I also seem to face signal drops and don't know if it's because of carrier breakdowns or something else. I have the XXLA2 radio and run the latest AOKP.
My logcat is attached, if anyone wants to help me.
Click to expand...
Click to collapse
It wont be related, because this poster is on Verizon.
I believe I found my issue...i'm certainly not the only one...
Issue 24345 "Samsung Galaxy Nexus (CDMA/LTE) radio drops all data and voice"
(I cant post links yet)
mrthemike said:
I believe I found my issue...i'm certainly not the only one...
Issue 24345 "Samsung Galaxy Nexus (CDMA/LTE) radio drops all data and voice"
(I cant post links yet)
Click to expand...
Click to collapse
Does it happen to you on 4.0.2? You only mentioned 4.0.3 and 4.0.4 (the report is for 4.0.2).
adrynalyne said:
It wont be related, because this poster is on Verizon.
Click to expand...
Click to collapse
Ah, alrighty then.
Theshawty said:
Ah, alrighty then.
Click to expand...
Click to collapse
If you are on 4.0.4, it is a known issue for GSM users.
adrynalyne said:
Does it happen to you on 4.0.2? You only mentioned 4.0.3 and 4.0.4 (the report is for 4.0.2).
Click to expand...
Click to collapse
I haven't tried 4.0.2. I could try that, but i'm confident it will happen with those as well. The symptoms described in that report mirror exactly what happens with mine.
I did three speedtests with my phone, on the third one I lost data and voice. Tried to make a call and got a "Mobile network not available". Almost like something is completely crashing voice/data.
adrynalyne said:
If you are on 4.0.4, it is a known issue for GSM users.
Click to expand...
Click to collapse
A closer inspection has led me to believe that I do not have this error on the ROM I use, so I'm sorry for possibly wasting your time.
Thanks for the RIL crash suggestion adrynalyne, I requested a replacement phone as it appears that is the only fix.
Just got the Samsung Galaxy S3 for T-mobile and have been experiencing a few strange issues with general call quality. About 2 or 3 mins into a call via wifi-calling, sound from the other side will just cut out. The call is still connected and I am then forced to hang-up and redial. This has happened already on 3 separate occasions. Calls off wifi-calling did not experience this issue albeit I could hear an echo of myself =(. Redialing and asking the other party to call me did not resolve the echo issue. The other party did not hear the echo.
Anyone else experiencing these types of issues or know of any fixes? Since it's only my first day with the phone, I'm hoping these are only fluke occurrences...
Yeap has happened to me calling out of town and in town numbers. Sounds like a dead line, and then when u talk u get an echo. I was advised by the people on the other line that they could hear me. This has happened while on the network due to I don't use Wi-Fi calling.
Sent from my SGH-T999 using xda premium
Anyone else have any wificalling issues?
My issue is more on loosing connection to the server while the phone is in asleep. the wifi connection is not lost just the connection to the server is lost and then my battery gets lost on locating connection.any ideas on that ?
I normally use wifi calling, but today at work and at home (so two different connections and two different routers) I tried to answer an incoming call, but the caller could not here me. I pressed the end button, and the dialer froze for about a minute before saying the dialer stopped responding and requested me to close it. Tested several more times before wiping my phone and reloading my rom fresh. Did the same thing afterwords. Then I turned off wifi calling and the normal network calling worked fine. Maybe a tmo server issue?
moonfire711 said:
I normally use wifi calling, but today at work and at home (so two different connections and two different routers) I tried to answer an incoming call, but the caller could not here me. I pressed the end button, and the dialer froze for about a minute before saying the dialer stopped responding and requested me to close it. Tested several more times before wiping my phone and reloading my rom fresh. Did the same thing afterwords. Then I turned off wifi calling and the normal network calling worked fine. Maybe a tmo server issue?
Click to expand...
Click to collapse
word for word same issues im having, also 2 different routers.:crying:
Although I am not certain if this problem exited before rooting and flashing my phone, my WiFi Calling has not been working. I can place the call, but I cannot hear it ring or hear anything when calling. I can receive calls, but once I answer, I cannot hear anything. I am able to receive text messages normally.
I have resorted to switching to the cellular preferred only option. I hope there will be a remedy for this issue.
I'm on the FreeGS3 R3 rom with stock kernal.
d0gan said:
Just got the Samsung Galaxy S3 for T-mobile and have been experiencing a few strange issues with general call quality. About 2 or 3 mins into a call via wifi-calling, sound from the other side will just cut out. The call is still connected and I am then forced to hang-up and redial. This has happened already on 3 separate occasions. Calls off wifi-calling did not experience this issue albeit I could hear an echo of myself =(. Redialing and asking the other party to call me did not resolve the echo issue. The other party did not hear the echo.
Anyone else experiencing these types of issues or know of any fixes? Since it's only my first day with the phone, I'm hoping these are only fluke occurrences...
Click to expand...
Click to collapse
What Rom are you using? Im trying to conclude that the issue might be with the [ROM][GSM]{7.8.2012} Team Sonic Presents FreeGS3 R3 (Special FiveOhFox Edition).....I have noticed a few people in this thread have the issue using that ROM
justice26 said:
Yeap has happened to me calling out of town and in town numbers. Sounds like a dead line, and then when u talk u get an echo. I was advised by the people on the other line that they could hear me. This has happened while on the network due to I don't use Wi-Fi calling.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
What Rom are you using? Im trying to conclude that the issue might be with the [ROM][GSM]{7.8.2012} Team Sonic Presents FreeGS3 R3 (Special FiveOhFox Edition).....I have noticed a few people in this thread have the issue using that ROM
moonfire711 said:
I normally use wifi calling, but today at work and at home (so two different connections and two different routers) I tried to answer an incoming call, but the caller could not here me. I pressed the end button, and the dialer froze for about a minute before saying the dialer stopped responding and requested me to close it. Tested several more times before wiping my phone and reloading my rom fresh. Did the same thing afterwords. Then I turned off wifi calling and the normal network calling worked fine. Maybe a tmo server issue?
Click to expand...
Click to collapse
What Rom are you using? Im trying to conclude that the issue might be with the [ROM][GSM]{7.8.2012} Team Sonic Presents FreeGS3 R3 (Special FiveOhFox Edition).....I have noticed a few people in this thread have the issue using that ROM
I am running Whitehawks STOCK TVALUEM999 ROM with none of these issues. I am only on wifi as thats all I have available and I do not have an issues. It's possible that the removal of all the T-Mobile Bloatware, or some Mods done could be causing this. I have great battery life on that ROM and everything works fine. I am excited about this ROM, but am waiting to see another release come out and see how that works. ALSO, get ROM Manager, update to the newest CWM and try a data/dalvick cache, factory reset and install from zip from internal SD. Let me know how that works out
I use Wi-Fi calling exclusively when I'm at home. I'm rooted but still using Touchwiz.
I haven't had any echo problems. I think the quality overall is pretty bad though. For lack of being able to think of anything better atm, I'll just say it sounds rough. It was something that really bothered me at 1st, but I guess I'm kind of getting used to it. There are times I've thought the call was lost bc the call becomes so silent (clear and empty), but after a moment, I can hear them again and the call continues.
My husband switched over to T-Mobile about two weeks before I got the S3 and switched over from Verizon. While using the Wi-Fi calling, I've lost a call or two so far. My husband, who has an HTC One S, has also lost a call or two and he thinks the quality of his calls are fairly poor also.
I'm wondering if it's not necessarily a S3 thing, but perhaps a T-Mobile thing???
That being said... There are times he has full Wi-Fi bars and I have barely anything, and when I check the signal my laptop is getting, that's full as well. When I check the Battery from Settings, I always only have a yellow bar that is frequently dotted with sections of red.
The Wi-Fi issue, whatever the hell it is, is really the only bummer about the phone for me.
rowan fire said:
I use Wi-Fi calling exclusively when I'm at home. I'm rooted but still using Touchwiz.
I haven't had any echo problems. I think the quality overall is pretty bad though. For lack of being able to think of anything better atm, I'll just say it sounds rough. It was something that really bothered me at 1st, but I guess I'm kind of getting used to it. There are times I've thought the call was lost bc the call becomes so silent (clear and empty), but after a moment, I can hear them again and the call continues.
My husband switched over to T-Mobile about two weeks before I got the S3 and switched over from Verizon. While using the Wi-Fi calling, I've lost a call or two so far. My husband, who has an HTC One S, has also lost a call or two and he thinks the quality of his calls are fairly poor also.
I'm wondering if it's not necessarily a S3 thing, but perhaps a T-Mobile thing???
That being said... There are times he has full Wi-Fi bars and I have barely anything, and when I check the signal my laptop is getting, that's full as well. When I check the Battery from Settings, I always only have a yellow bar that is frequently dotted with sections of red.
The Wi-Fi issue, whatever the hell it is, is really the only bummer about the phone for me.
Click to expand...
Click to collapse
I am not sure if what to tell you, but I am in Afghanistan with the Samsung GS3 rooted, and I do not have a single issue with call quality with some of the crapiest internet connections you can ask for.. No echo, no dropped calls. Your internet connection quality can make a difference, when you make phone calls, any downloads going on can hinder the quality, also the type of router u have makes a difference. A wireless N router with 300MBS per second would be ideal...
It doesnt matter if your are using Touchwiz, the rom you are using matters, no other threads are stating this issue. I suggest you try another rom like redruM cause he just released a new update today, or Whitehaws STOCK. It performs great and has CIQ removed, zipalign on boot, some T-Mobile bloat removed, no force closes on any apps and good battery.. It doesn't have the crazy scripts and 4 in 1 reboot, however, if u dont care about that and you want stable and root, its a good option
According to T-Mobile technical support, they have escalated the issue of wifi-calling and wifi connectivity issues to Samsung and supposedly there is a team working on this. Supposedly they will be doing an over the air update.
it doesn't seem like a lot of us is having this problem, could it be the phone itself? i was fine until a couple of days ago. now i am having the same problems as some in this thread; i can hear them but they can't hear me. sometimes it freezes when i answer the call. now i'm thinking if rooting (phone is rooted only) was a probable cause, and if i should do a nandroid restore or system reset??
No wi-fi calling
MMakoto said:
it doesn't seem like a lot of us is having this problem, could it be the phone itself? i was fine until a couple of days ago. now i am having the same problems as some in this thread; i can hear them but they can't hear me. sometimes it freezes when i answer the call. now i'm thinking if rooting (phone is rooted only) was a probable cause, and if i should do a nandroid restore or system reset??
Click to expand...
Click to collapse
TMo - GS3
My phone is and has not ever been Rooted. I'm having the same issue that when wi-fi calling is active, if I receive a call, the caller cannot hear me, and then the app. hangs for a minute when I hit end or the caller hangs up. I tried it on a couple networks. I thought I was able to make wi-fi calls, but that seems to not work all the time, either.
I believe this is the first TMo ICS phone, right? I had a 4.0.3 custom (Passion) ROM on my Vibrant (GS1), but since there wasn't ICS TMo phone, there was no wi-fi calling app. on it.
I called T-Mo support and told them I found this thread with other users with the same problem, but they didn't say anything was in the works. Samsung support gave me their usual answer, of doing a factory reset, reinstalling and reconfiguring everything (yeah right).
I get the hang sometimes and I also get the problem of people not being able to hear me when I pick up. Annoying. I got rid of my amaze after the ICS update because it screwed up wifi calling(delay in voice 5-10sec). Piss poor. Wish it worked better because I don't get a cell signal in my house.
To get rid of the voice echo - disable the noise cancelation during a phone call in the in call menu. The noise cancelation uses two mics but unfortunately picks up the noise of the speaker as well, causing the echo effect.
when i first got my s3 i had the wifi calling on and i'd miss calls. people said that it didn't even ring just went right to voice mail. on the occasion that a call actually went through people couldn't hear me and for me they cut in and out. i gave up and stopped using it.
when i bought the phone i was told that when on wifi calling the minutes didn't count against my plan, but reading the manual i got the impression that they did. which is correct?
jknakes said:
when i first got my s3 i had the wifi calling on and i'd miss calls. people said that it didn't even ring just went right to voice mail. on the occasion that a call actually went through people couldn't hear me and for me they cut in and out. i gave up and stopped using it.
when i bought the phone i was told that when on wifi calling the minutes didn't count against my plan, but reading the manual i got the impression that they did. which is correct?
Click to expand...
Click to collapse
You have to have them add the free WiFi calling feature to your plan and then they don't count. Just tell them you want your minutes on wifi to be free. There is no extra charge after they add that code.
Sent from my SGH-T999 using xda app-developers app
I'm having the same issue, wifi calling does not work. No one on the other end when I answer incoming calls. Can't connect out.
For me it works sometimes and sometimes it doesn't I just turn it off, I use 200 minutes so far this month and today is the last day so I'm good with 500 minutes plan
Sent from my SGH-T999 using Tapatalk 2
Did any of you with the wifi calling problem install Skype? My first phone had the problem of no one hearing me and freezing when hanging up. I ended up returning it to Tmobile for another phone.
Right before I returned the old phone I did some testing. I flashed it back to stock and it didn't fix the problem, but when I wiped the data and cache in download mode, it seemed to help with the wifi calling, not sure how consistent it worked, but at least for the first call I can hear them and vice versa.
So I'm thinking something I installed may have played a factor, and right now my suspicion is that it's skype. I haven't installed it on my new phone since I don't want to screw the wifi calling on there.
Hi all, I don't know if it is my GS3 but wifi calling is not working rigth. It keeps disconnecting from time to time. Sometimes says its working and incoming calls are sent to voicemail without ringing, other times people say the phone didn't even ring and the call dropped. And sometimes the incoming calls came and the phone frezees when trying to answer it. And sometimes it just work fine...
The problem is that I had another GS3 which was working perfect but I cracked the screen and got another one (New), and this one started giving me those problems from the beggining. It was completely stock for a month after that I flashed a few ROMS and still had the problem. I tried searching online and found that other people are having the same issues and started complaining at the same time that I replaced my phome, so maybe its not the new phone?? And a tmobile problem?? I still have warranty on this one and can replace it again but first I would like to know if there are people that have the same problems or issues. Thanks in advance
Sent from my SGH-T999 using xda app-developers app
The last few days mine has dropped every few minutes, the service itself not a call because it's so sketchy I'm not even brave enough to attempt a call. I've tried everything I've found online and no improvement. Tmo really needs to work their s**t out.
Thank you I guess its not my phone then. Thanks!
Sent from my SGH-T999 using xda app-developers app
Same here!!!!!!!
Literally, in the last 5 minutes it's dropped and reconnected 3 or 4 times. I'm getting so frustrated with tmo. I wish they had email support because I really don't think I can keep my cool in real time.. it's just ridiculous.
It's been terrible since day one :/
can't anyone get to the bottom of the problem? i read somewhere that t-mobile decided to use a different platform for the wifi calls for some of the newer phones which includes the s3. i have no t-mobile coverage inside my house and depend on wifi calling. since i got my s3 my wifi calls drop repeatedly. it's completely unusable. we demand answers and a fix. i've found hundreds of users through google searches who've had this problem.
what's going on?
I noticed Skype 3.0 kept disappearing when WiFi calling would crash so I'm going back to 2.9 and pretending like it's gonna fix my problems. There's a HUGE thread in the GS forums over at tmo support this problem has been going on since our phones were released, and as far back as last year on other phones. They simply don't care enough to fix it.
---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------
Guess not.. went to send a text and it dropped AGAIN. Came back in <30 seconds wtf!!!!!
I had it work once but it wouldn't log in again until I "forgot" the network and reconnected.
Sent from my SGH-T999 using xda app-developers app
It's "working" now but my texts don't send. Just spin and spin and spin.
Wifi calling
fireboypr said:
Hi all, I don't know if it is my GS3 but wifi calling is not working rigth. It keeps disconnecting from time to time. Sometimes says its working and incoming calls are sent to voicemail without ringing, other times people say the phone didn't even ring and the call dropped. And sometimes the incoming calls came and the phone frezees when trying to answer it. And sometimes it just work fine...
The problem is that I had another GS3 which was working perfect but I cracked the screen and got another one (New), and this one started giving me those problems from the beggining. It was completely stock for a month after that I flashed a few ROMS and still had the problem. I tried searching online and found that other people are having the same issues and started complaining at the same time that I replaced my phome, so maybe its not the new phone?? And a tmobile problem?? I still have warranty on this one and can replace it again but first I would like to know if there are people that have the same problems or issues. Thanks in advance
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
WIFI calling sucked for me even before I rooted it. The quality was horrible!
luv4greenleaves said:
WIFI calling sucked for me even before I rooted it. The quality was horrible!
Click to expand...
Click to collapse
Yeah I know, but at least for me it was reliable, I used to received all the phone calls, etc..
WiFi icon is blue try to send a text, spin spin spin, failed, WiFi calling gone, 30 seconds later it's back. I am so unbelievably frustrated and don't know what to do. I have 0 service at my house and I'm watching my battery drain FAST.
psykhotic said:
WiFi icon is blue try to send a text, spin spin spin, failed, WiFi calling gone, 30 seconds later it's back. I am so unbelievably frustrated and don't know what to do. I have 0 service at my house and I'm watching my battery drain FAST.
Click to expand...
Click to collapse
+100!!!
Sent from my SGH-T999 using xda app-developers app
Just spent the last hour trying to send a text..... WiFi on and off, restarted a few times. Tried WEP instead of WPA, set port forwarding on the router. This is CRAZY. It seems like the first two weeks (first month?) I had the phone it was ROCK SOLID but since then it's only gotten worse day by day. I can't believe this s**t. The person at the tmo store said you have to wait a year before a new customer can get a free signal booster, not that it'd even help....
I want to call or live chat but I am so pissed I honestly don't think I can act like an adult
Do any of you people with problems have Comcast voice? Could their VoIP be messing it up?? I tried to run another modem but Comcast wouldn't let me activate it... what a crappy night!
Hey guys. I tried wifi calling again today and it has been working perfect all day. No disconnection, all texts and calls enter without any problems. I'm just wondering if anyone else is still having problems with wifi calling.
Sent from my SGH-T999 using xda app-developers app
I could not get my Wifi Calling to function properly at work. Text works great, sending and receiving. My phone rings when I receive a call, but I cannot hear anything, neither does the caller. Similarly, when I dial a number, the other phone rings, but no audio is heard on either end. This only happens at a coroporate network, not at home or an open network such as hotels or restaurants. T-Mobile is supposedly aware of the problem but no solution is in the works.
A couple days ago MMS over WiFi broke. I tried every setting possible so I ODIN'd back to ICS without root and things were 100000x better. Still got a few disconnects but nowhere near as horrible. Then I did the OTA on tmos server to JB. Seemed a little less stable but still useable for texts. Rooted last night and still seems stable but a few extra disconnects.
One thing I've noticed on a few disconnects, I saw the connected to WiFi network bottom of screen notification pop up. The WiFi indicator stayed full bars so I'm not sure if it actually disconnected or that bottom screen pop up was just WiFi calling reenabling.
I think the WiFi in our phone is less than great. My router gives my PC a 300/300mbps link, on my phone it's 65/150mbps.
For me all the problems are resolved except mms. But no disconnects, texts and calls work great. Used it the whole weekend without one single problem. I havent done anything with the phone, Im using sonic resurrection 7.1.1 ROM. Maybe tmobile is fixing the problem, slowly but fixing it.
Sent from my SGH-T999 using xda app-developers app
There are allllllllll these threads aboutwifi calling and NO SOLUTIONS posted from tmobile. What a pathetic joke of a company.
Both my data and WiFi have been acting very strange the past week. Both services will show me as connected but I will only get the upload arrow showing on each indicator and then sometimes the icons just go gray. It has been happening very often and I have changed both my ROM and kernel on clean installs and I still have the same issue. Any help would be appreciated.
Bump. Still have the problem.
Flashing back to stock should work
Posting your basics usually gets you better answers
Sent from my Galaxy Nexus using Tapatalk 2
czonin said:
Both my data and WiFi have been acting very strange the past week. Both services will show me as connected but I will only get the upload arrow showing on each indicator and then sometimes the icons just go gray. It has been happening very often and I have changed both my ROM and kernel on clean installs and I still have the same issue. Any help would be appreciated.
Click to expand...
Click to collapse
I started a thread here on a topic where my wifi and signal bars turn gray and the phone doesn't have data connectivity any more. sometimes this happens a dozen or more times a day and sometimes once or twice.
one response in that thread indicated that 4.2.2 made a positive impact on the problem.
I've been searching for a definite fix for this data/WiFi issue to no avail. I'm not entirely sure of when this issue began to occur but my phone (Toroplus) constantly loses WiFi signal. By losing signal I mean WiFi will turn off and on all by itself. And yes, WiFi sleep policy is set to stay on always. This issue alone made me go back to stock only to find the WiFi issue is present there too. I've also ruled out my router as the culprit. Im suspecting this is a Google issue. By the way, I talked to a sprint store employee who owned a galaxy nexus and after a few minutes of playing with his phone, which was completely stock and never rooted, I noticed his WiFi connection would turn off and on all by itself too. Any insight from anyone with knowledge to this would be appreciated.
Wi-Fi optimization off. If that does not fix it, I dunno.
Sent from my Galaxy Nexus using xda premium
Soldier 2.0 said:
Wi-Fi optimization off. If that does not fix it, I dunno.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion but that doesn't fix it. Are you not having this issue? What's your setup? What ROM do you use? I've basically used all of them and it never goes away. I'm thinking of going to the HTC One when it's released just in case it's a Samsung issue.
I have also experienced this problem, especially at work where the network uses some WPA Enterprise variant. I've digged through logcats and can't find the problem either. A few Google Code forum posts talk about a possible bug introduced by network adapter manufacturers, or wpa_supplicant configuration issues. Haven't found a workaround yet, so I had to go back to 4.1.2, which seems to be stable.
More info here:
http://code.google.com/p/android/issues/detail?id=34212
http://code.google.com/p/android/issues/detail?id=40023
The more I read on this subject the more I come to realize this is not specific to a certain device. The only common denominator that jumps out at me is jellybean. Seems like the issue is with Google, not hardware. Sucks that such a basic feature is not reliable out of the box. At least now I can understand why my buddy calls Android "buggy". Hopefully this is fixed sometime in the near future.
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.