[Q] Short silence while in call - Galaxy S III Q&A, Help & Troubleshooting

Since I got my phone, this happens: I call someone, we talk for a couple of seconds, then the line goes completely silent for a second or two, and then it comes back.
I tried everything except flashing a whole new ROM and trying a different SIM card. Multiple modems are of no help.
Got tips?

Just to answer those who might have the same problem: I disabled the noise filtering stuff from calling properties, all works pretty much as it should now.

Related

Occasional No Dial Out/SMS Sending

Hi all,
Looking for a bit of help/advice.
On occasions, probably between 1-3 times a day, when I try to make a call on the Hero, the call appears to look like it is dialing out but it just sits there saying 'dialing' but never connects to the destination which can be any UK number / Orange 150 etc. Either rebooting the phone or leaving it for 10 mins or so fixes the problem, but it does become annoying!
At the same time as this happening, when I try to send an SMS, I get the error 'SMS not able to send' in the notification bar. Again, I have to keep trying and it sorts itself out.
A final problem and I am not sure if it is related or not is I have had numerous people try calling me at various times, my phone doesn't ring or display a missed call, nor do I get a missed call SMS but the person who tried calling me said the line was actually ringing first and then went through to voicemail. I have witnessed this myself by calling my phone, getting a ringing line but the phone doesn't respond?
Any ideas of help would be appreciated. This problem has existed on Modaco Roms 2.2, 2.8 and 3.0 - I'm on Orange UK.
Thanks,
Nick
I have the same problem with the Orange Poland. When I logged on to the 3G sometimes you can not call or send SMS. When I switch to the 2G network problem disappears.
Yeah, it is strange, I have done that too, turn off the 3G to 2G and back to 3G which sometimes cures it, but not all the time.
I've tried various things, made sure the apps aren't closed with Taskkiller or anything like that. There is no specific time or occasion it happens, it just does now and again.
Well I have tried everything. I recieved all the settings from my operator , changed over 10 ROMs and gone back to the original too, i tried what you said to turn 3G off , i reset to factory , i unrooted.....Nothing works for me. I just get "Unable to send". I also tried 4 SIMs from different operators !!!

I don't receive incoming calls!

So, with the stock root rom, with a few different roms, and even with different kernels and radios, I don't ever receive incoming calls (though if I make an outgoing phone call, it works just fine).
Anyone know if this is something I can fix? Or is it an issue on Verizon's side? They had to go through three 4G SIM cards before finding one that my phone could actually activate with, so I'm wondering if that's the problem.
Did you set up call forwarding? Try calling *73 as this disables all calls to be forwarded, and try again.
You know what? I think you might be right... before I got my Thunderbolt, I had an OG Droid set to forward calls to a different temporary number...
My phone is going through a restore right now, so the INSTANT it boots up, I'll be dialing *73.
EDIT
VICTORY! It must have kept the call forwarding on the line. Thank you SO MUCH.
you're welcome.

Sipdroid/PBXes.org problems

I've been using Sipdroid through PBXes.org for the past month or so without issue until yesterday. Calls were going through but I was getting no audio. The person on the other end couldn't hear me, I couldn't hear it dialing much less someone picking up. This was on both my phone and tablet (which I had set up a second extension for).
After trying it on a different wifi network this morning and getting the same thing I decided to delete my PBXes.org account, uninstall Sipdroid and start from scratch. After reinstalling exactly the way I did the first time, I'm getting a "Your call cannot be completed as dialed" error whenever I try to make any outgoing calls. Incoming calls I don't get at all.
Is anyone else's similar setup still working? Could it be an issue with PBXes.org?
Currently I'm having problem with my SIP (pbxes) account registering. It keeps failing on my device. Normally it works eventually, but it takes a little while. That just started happening yesterday. Before, it would always work the first time.
Edit: Just found a post where someone said they changed it to port 5061. I did that and it works. 5060 has always worked, but for whatever reason I guess I have to use 5061 now.

[Q] In Coming Calls and Screen

I have had my G3 for over a week now and there is one issue I can not seem to solve. Anytime I receive an in coming call the phone rings but the screen does not turn on and show me who is calling. I have to fiddle around on a blank screen to have it activate. Every and I mean every phone I have ever had over the years, the screen would always turn on during an in coming call to show who is calling. Am I missing a simple settings somewhere to activate this feature, any advise on this is welcome. Thank you.
Edit: Just to verify, Yes I have the option under Calls activated to have a Pop up on incoming calls, the issues is the screen is not turning on during the in coming call and I can not figure out why.
OK, 37 looks and no one has nothing, that scares me.

Continuous beeping in calls Ace 4 Lite G313ML

Hi,
My wife and mom both have new Galaxy Ace 4 Lite G313ML's; they're both new and unlocked. Most of the time when they make calls, the recipient hears repetitive beeping continuously when they're not talking. Sometimes after about a minute of being in the call, it stops. I think that after it stops, if they make a call again soon after, it is still gone. Both of them are on Straight Talk (on AT&T's network).
The beeping is not every few seconds or every minute; it occurs continuously while they're not talking (but it's still individual beeps, not a continuous tone).
I tried disabling various things that could be related to notifications or anything network-related, but I wasn't able to get rid of it. I thought that turning off Wi-Fi made a difference at first, but since then it has continued to happen with Wi-Fi off.
Has anyone experienced this problem before, or does anyone have any suggestions for was to fix or work around it?
Thanks!

Categories

Resources