Related
hi,
from time to time I experience the folowing:
Suddenly, soemone call me to other phone becuase he's trying to contact me. I see my artemis and it's OK, switched on and signal bars at 90%. I dont know why when someone try to call me appears like the phone is switched off.
I make a soft reset and strat to receive missed calls + sms's.
I have Vanilla 4.02 ROM and I use very often the wifi connection....
br.
im with you there, this is the reason why i went back to my aging nokia 6280. ive tried about 10 different roms and it would never pick up the signal unless rebooted. what happens with mine and a few of my friends was on london underground you would lose the signal obviously underground, when you came out the phone would pick up the signal but never recieve a call or sms. also the gprs wouldnt connect unless it was rebooted. ive had a few htcs in the past but because of this poor show i wont ever purchase another one.
my phone done this from day one of ownership, tmobile told me that firmware upgrades would fix this annoying problem, but it never did.
maybe you should try updating your radio ROMs
flashing different ROMs wont help
done half a dozen of them as well on my phone.
audiobookman said:
done half a dozen of them as well on my phone.
Click to expand...
Click to collapse
Even, I had the same problem, but since I moved to Radio version 3.21.XX, everything is just fine, no problems since then. Even 3.24.XX is out now, you should definitely give it a try. Hope it works for you!!
Cheers!
Same problem
Thanks for posting. I have the same problem with the same ROM. I'll change radio rom.
Radio Rom changed
Radio Rom changed 3.34.90 . No problems and good quality
I've been seeing this problem for a few weeks now, with several different ROMs, including the original rooted stock ROM now. In nearly all of my recent calls, I get disconnected one or more times with the message "Call disconnected" and a "Dismiss" button. I'm thinking that this is because of my EVO and not the other side, since usually if they accidentally hang up or something the call just ends without a message box. As far as I can tell, I have good reception (at least according to the bars), and this is happening at home, where I've not had the problem before.
Does anyone know what could be causing this? My wife's EVO is not rooted, and she does not seem to be having this problem. But then again, I've not had the problem until fairly recently either. I've tried updating my profile and PRL with each new ROM, but it doesn't seem to have made a difference. Anyone have any suggestions as to how to stop this from happening?
Go into the settings menu andbupdate both your PRL and your profile. That *should* help with reception related issues.
posting & replying via the XDA Premium app.
Unfortunately, I've tried both of those things. I just did some testing today, and it seems that my phone is unable to stay connected during a phone call for more than five minutes before disconnecting, even if I don't touch the phone and just leave it sitting on a table.
Any other ideas? As far as I know, I haven't ever flashed my radio away from its default (2.15.00.11.19), and I'm currently using the leaked stock gingerbread ROM (build number 4.12.651.1 CL41771 release-keys and kernel 2.6.35.10-gaa602b7 [email protected] #1).
Maybe it's time to unroot and contact Sprint?
You can try downgrading from 2.15.00.11.19 to 2.15.00.09.01. You can download it from http://www.mediafire.com/file/jyedjkp1bm5amwm/EVO_Radio_2.15.00.09.01.zip
Afterwards, go into recovery, wipe cache & dalvik cache then flash the zip. You will be taken to the radio update screen and appear to hang. don't worry or get impatient. After it is finished, you will reboot into recovery and see the words "clearing cache" at the top of the screen. Simply select reboot and then you will boot to your homescreen. The initial boot will take a tad longer since it will be rebuilding the dalvik.
Hmm... I'm hesitant to downgrade my radio because my wife has an EVO with the same radio version number and hers doesn't have this problem. Granted, she is not rooted...
I understand. I've downgraded and upgraded everything several times for testing purposes and troubleshooting purposes and have never had a problem. The only hing about flashing radios is patience and not to pull the battery. Anyway, you can always call Sprint and see if they can troubleshoot it for you from their end.
posting & replying via the XDA Premium app.
I would contact sprint @ 877-809-6696 (advanced tech supp). Ask them to push a full reprovision to your device. See if that helps any. I was having issues when when on the airave, I was unable to receive incoming calls. This corrected it. I did try all the other steps listed above without any success.
This is interesting. I unrooted to test things out before calling Sprint, and the problem went away. I was able to stay connected for an hour (where before I couldn't last longer than 10-15 minutes). Yay, fixed, right? So, I rooted again and didn't install any ROMs or anything, just rooted, and the problem came back.
So, I have a solution, but I don't like it very much because it means I need to stay unrooted. Anyone have any idea why simply rooting the phone with Unrevoked 3 (and doing nothing else) could cause calls to disconnect? I'd love to be able to root again, but I can't deal with a phone that randomly disconnects all the time.
I am interested in this as well as I am rooted using unrevoked and get disconnected as well. I do find that it mainly happens though talking to people who have service on AT&T.. Quite wierd. All I hear is a beep then disconnected. This happens when I first place a call and it rings once or twice then beep, disconnected...
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
KingFunderberk said:
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
Click to expand...
Click to collapse
So whats the final call on this ..?
Is it Rooting , Is it network .. i am too getting psyche with this .
I'm pretty sure it is not rooting. But I don't yet know for certain what it is. Sprint thought there might be something wrong with the antenna on my phone, but they had already replaced the phone, so I think that is unlikely. They gave me a femtocell range extender to use in my house. Basically, I plug it into my broadband connection, and it is like having a mini cell tower in my house, giving me a very strong connection. Sure enough, when connected to that, I haven't had any calls drop. However, my phone still sometimes doesn't connect to the femtocell and instead connects to some other tower for some reason. My wife's phone doesn't do this, so I still think there is something wrong with my phone. I may contact Sprint again about this. ...sigh...
What is your area some area evo don't work properly like on rahim yar khan in this time connection don't work properly some signal drop and some time up i sure after few day signal work properly then problems will be solve.
My phone EVO is doing this now as well. Has anyone heard/read a solution?
greg_99 said:
My phone EVO is doing this now as well. Has anyone heard/read a solution?
Click to expand...
Click to collapse
I am having the same issue, out of the blue. No problems up until a few days ago. I'm wondering if it is maybe an issue with a certain version of the Evo. I have a version 002. Thoughts?
Greg_99 any progress on what might be causing this issue?
So, around 11am this morning, I tried calling a conference line for work, and didn't get a dial tone, but the phone said I had three bars. I decided to reboot, just in case, and what do you know, I had three text messages waiting, and missed a call.
It looks like I lost the connection somewhere between 6pm and 10pm last night, but I have no way of knowing when. I haven't used my LoS tool for a long time because it hasn't seemed necessary, but it looks like I should reinstall it.
So my question is: have any of you had a similar problem in the last few weeks/months? It's pretty clear to me that the EL29 OTA + modem does not, in fact, fix LoS permanently, or at least Sprint/Samsung can't seem to fix ghost LoS.
If there's enough interest, I'll start updating my LoS Daemon again.
No where near as much compared to when I got this phone. It's maybe once a week now if that. I'm on gb still running FE16 if that matters to you
Sent from my iPhone killer.
I had this same problem for several weeks. Well, not the same exact problem. I could make calls, recieve texts but not recieve incoming calls. Callers would go straight to voicemail and I wouldn't get the notification for a while either. People would text me 'did you get my VM?' I even started testing this by calling myself from the office phone (full signal btw).
I ended up calling sprint and totally reprovisioning the phone and haven't had any problems since. I posted how I did that here:
http://forum.xda-developers.com/showthread.php?t=1332837
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.
Hey All,
So, I'm having a weird issue with my T-989. I get intermittent audio loss upon making and receiving calls. Refer to the following examples:
Call comes in; I swipe to answer..."Hello...Hello...Hello....-__-" I can not hear the person on the other end of the call and they are un able to hear me. I've asked countless people that call me on a daily basis on their experience when this happens. They say the call connects but no audio; they then get confused and hang up if I don't end the call my self. Normally I'm the one that ends the call now and I'll call back....sometimes I hear ringing and I know that it'll work ok.
Sometimes, the call log counter starts....but I hear no ringing, HOWEVER the person I'm calling is actually being called and tries to answer the phone...but because I don't hear the ringing...I don't even realize that the phone has established a connection.
Sometimes....everything works fine. I'll answer the phone and it'll work like a charm or I'll make a call and it'll work like a charm. Two hours later...same weird issue.
I wanted to know if people had similar problems.
It's getting increasingly annoying at this point. At first I thought maybe it was my service. Then I thought it was my ROM / Radio. Honestly, I know people who have the same service and plan as me.
Phone is running P.A.C 22.0.1
This issue happened on older versions of which I completed wiped and re installed newer versions of P.A.C; it happened on AOKP; happened on Paranoid Android.....
I'm guessing the only thing I haven't tried changing is the Radio that comes with each ROM.
I am on the T-Mobile Pre Paid Unlimited Talk / Text w/ 500mb Data plan. [I work in data centers, unlimited INTERWEBS!]
Anyone else have similar symptoms? I'll be getting the S4 soon, but I wanted to resolve this issue before hand because I'll be giving it to a friend.
Thanks in advance for any help! :victory::highfive:
I have been living that same issue for months, between several ROMs and kernels and radios. Ive learned to use this process......answer call, wait 3 seconds, then saying "hello". I know, its silly.
I have noticed its seems worse when answering calls from others running aosp (cm10)roms.
I've have not tried any touchwiz ROMs
Sent from my cm_tenderloin using xda premium
Waiting 3 seconds and then saying hello works? For me the issue happens when placing calls as well. I installed the newest P.A.C last night when I posted the OP, so far no problems. I'll update again if I have any issues moving forward.
What radio are you using?
Now - UVMC6
As I said, as of yet, I haven't had any issues. Let's see over the next couple of days....