Hi,
Currently, I have a Galaxy S4 Mini(GT-I9195) which is rooted and running CyanogenMod 10.2.1.1.
Sometimes, whenever a call comes through, I can answer it. However, when I try and talk the person on the other end cannot hear me.
Worse still, when I try and hang up, the phone just crashes altogether and restarts.
Sometimes, the phone app itself crashes. I can still make calls or receive them through an app called TuGo(an app from my current network).
What should I do to resolve this issue?
Please reply as soon as possible.
Talk soon,
Adi
Related
Hi all,
I just wanted to ask a question or to see if someone could help me out.
Ever since i have had the 4.0.4 upgrade randomly i send texts, they say they have sent and the end user never gets them, and vice versa if someone sends me a text randomly sometimes i wont receive them, I'm not 100% sure if its for everyone as i mainly text my girlfriend.
Is there anyway i could pinpoint the problem, with the phone?the software, the network?
Any special free tools i can run to check sms options or anything?
Btw my phone is not rooted.
Thanks.
most problems with sms seem to be related to the network, not the phone.
More than likely its the network... what carrier?
This is a common and recurring problem on sprint, its the main reason I dropped them 3 years ago
I upgraded to the Galaxy S III from the Vibrant. I had no problems with my Vibrant making or receiving WiFi calls on the secured WiFi networks at home and at the office. However, I am having serious problems with WiFi calling on the S III.
I can make calls (most of the time) and can send and receive texts in WiFi but I cannot answer a call. The phone either does not ring and the call goes straight to voicemail or I hear the phone ring, answer the call and can hear the other party, but they cannot hear me.
I called tech support who had me do a factory reset. That worked briefly, but within 24 hours, I was back where I started. My 911 location situation is sorted, so that is not the problem. I am also close enough to the routers that I do not believe that is the problem either.
My first suspicion was a bad sim card but another co-worker of mine who also has an S III cannot answer WiFi calls in the office either. Now, I suspect some network security issue is causing the problem on both networks I regularly use, but do not understand why considering my Vibrant had no problems at all.
I, too, cannot hear the other party when answering on Wi-Fi. It worked fine at first but now it doesn't. Anyone know of a fix?
Sent from my T-Mobile Samsung Galaxy S3 16gb Pebble Blue running Stock ROM
tiisai44 said:
I, too, cannot hear the other party when answering on Wi-Fi. It worked fine at first but now it doesn't. Anyone know of a fix?
Sent from my T-Mobile Samsung Galaxy S3 16gb Pebble Blue running Stock ROM
Click to expand...
Click to collapse
The other thing that happens when people call me is that the phone will ring once and then go to a busy signal.
I went to a T Mobile store and replaced the sim card. They also made some test calls to my phone without success. I also upgraded the firmware on my home wireless router. In the end, nothing worked and Tech Support is sending me a replacement phone.
My replacement phone arrived and it initially did not work either. After several hours of experimenting and getting results that weren't always easy to duplicate I have reached the following conclusions:
1. There was indeed something wrong with the original phone.
2. Both phones could answer WiFi calls straight out of the box, but as soon as I altered the Setup or downloaded apps, they wouldn't.
3. I strongly suspect that either the power saving settings or the voice cmd for apps settings are incompatible with receiving WiFi calls. I could not determine that any individual app caused a conflict. When I ran into troubles with the replacement phone, I could restart it and get it to work after altering the phone's settings. I never could get the original phone to do so, however.
4. WiFi calling is still wonkier than it should be compared to my Vibrant. I am still getting calls that go straight into voice mail without the phone ringing, or the caller will hear my phone ring once or twice before it goes to a fast busy signal. I at least feel comfortable that if I hear the phone ring I can answer it, where I couldn't do so before.
First of all I searched and didn't see anything on this, sorry if I missed it.
I am having a issue with my S3, it seems it randomly stops receiving calls and sms. The phone is only a week old and it has happened twice already.
A simple restart seems to fix this issue however I would prefer to have a device that I don't need to worry about restating daily to ensure I am getting my calls.
AT&T
4.1.1
Non Rooted - UCDLK3
Any help would be great & thanks in advance.
you didn't search properly, as there is a thread about this already. it is a known issue on AT&T's end, so everyone experiencing this problem needs to wait for them to fix it.
It is a problem with LTE service, using only 3G is the only current fix to this.
sent from my I747
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....
I had an aosp rom insatlled and all was working fine.
Then out of the blue with no warning...I can no longer receive nor make calls. When I attempt a call i hear no dial tone...and when the person picks up the timer starts running but I cant hear anything and they cant hear me..
I flashed other roms and same issue. I even did an odin flash to stock and the problem persist. Both speakers are working. I tested both.
I dont know what the problem can be. Any ideas anyone?? please help
thanks in advance
(PS: all other phone features work, sms, web, lte etc)
meshflesh said:
I had an aosp rom insatlled and all was working fine.
Then out of the blue with no warning...I can no longer receive nor make calls. When I attempt a call i hear no dial tone...and when the person picks up the timer starts running but I cant hear anything and they cant hear me..
I flashed other roms and same issue. I even did an odin flash to stock and the problem persist. Both speakers are working. I tested both.
I dont know what the problem can be. Any ideas anyone?? please help
thanks in advance
(PS: all other phone features work, sms, web, lte etc)
Click to expand...
Click to collapse
I had this happen with my rom. It was so strange. In my case it would let me dial three numbers then I could dial no more. Couldn't recieve or make a call.. I did however fix the situation with flashing the rom again. Haven't had any trouble since. In your case somehow your radio might have gotten changed. You might look into what the radio was before the rom and possibly download that radio again. Or you can try basic ics radios and see if any work for you. You have nothing to loose by trying. You can get the radios here on xda. On my last device a similar thing happened to me and I had to flash a new radio. It did restore my abilities. Its worth a try. It could be what's going on with your device. It certainly wont hurt to try. I wish you the best and do hope this helps you.
Happens to me occasionally, reboot fixes it.
Sent from my SGH-M919 using XDA Premium 4 mobile app
I had something similar happen to me with a AOSP rom. On Thursday I started having trouble with dropped calls and then yesterday it got worse and I was unable to make or receive calls at all. Right after dialing the phone would beep and the call would end. Data and SMS was fine.
After multiple reboots and a good amount of time it started working again. I'm not convinced I did anything to fix it. After reading about your problems I wonder if the cause was on the tmobile side.