Problem receiving calls - Galaxy S III Mini Q&A, Help & Troubleshooting

Hi, I’ve got a Samsung galaxy s3 mini and Orange hiro ( Alcatel one touch mini idol ) both purchased from orange .
When I receive a call from Hiro to S3, in some places the dialer/phone app shows person who is calling me but when I press to answer the app freezes and I do not hear anything and the other person can’t hear anything .
After this incident the S3 has no sound anywhere in any browser , youtube , music / video player as if it does not have a speaker. If I restart the S3 sound works again until the Hiro calls me.
Weird is that when I call the Hiro there is no problem.
After some investigation I discovered that if I switch on the GSM mode S3 I don’t have this problem and I can get calls from Hiro. As you know on gsm the network speed is a few kb compared to wcdma.
I also did some tests and when outdoors with WCDMA mode the problem does not occur.
Also if I set Hiro on GSM and mine on WCDMA/GSM or just WCDMA there is no problem with my phone.
Both phones weren’t rooted or other interventions that would void the warranty , their firmware is up to date.
I do not understand why the S3 is unable to perform a basic function.
I tried the 2 sim cards in other phones but there is no problem, the problem only occurs when Hiro phone calls mine.
So far I have tried:
Reset to factory.
Clearing data from Dialer/phone app.
What is frustrating is that sometimes the connection between two works fine but when it doesn’t my phone ends up disabled with no sound.
Thanks.

Update:
I sent the phone 4 times to warranty and got the motherboard+battery replaced, the problem persists. I don't know what to do anymore.

Related

[Q] Weird voice call problem

Hi,
I have a really strange problem..
I've got my new HTC Incredible S one month ago, and everything was fine.
Recently, people were telling me that in the middle of a call, my voice turns out into a noisy voice!
I tried to make calls to my phone from another phone, and after few minutes, the voice really changed into a weird voice (really different than my own voice) plus a lot of background noise (it looks like the phone has switched to the voice cancellation mic instead of the regular mic).
During the call, when this problem happens and when I switch to headset or turn on the speaker phone, the problem is fixed. few minutes later, it comes back again.
I checked for viruses, no add-on or 3th party phone applications installed.
Shall I do a factory reset?
I don't wanna lose my apps, settings, contacts and data
Please help!!!
Same here.
Maybe this one helps:
http://forum.xda-developers.com/showthread.php?t=1081356
didn't try (couldn't try), because no root here....
My phone is not rooted neither.
Any solutions?
Have you tried to do a factory reset?
I don't think it's a hardware issue; because it's been working fine for one month with no trouble.
No, didn't try a factory reset.
And i also think, this is a software issue, but no clue what could be the reason for this behavior. Sometimes voice call just works fine and sometimes it doesn't...
Yeah same here. Sometimes It goes fine & sometimes not. I think I will do a factory reset soon and will let you know the result.
Sent from my HTC Incredible S using XDA App
Hi,
I did a factory reset (or what they call a Hard Reset).. the same problem still happening!
I event went to the telecom company, and they replaced my SIM card, but still the same
Any clues????
Could it be a defect handset ?
Now I just figured it out!
It was a problem with the GSM provider!!!
They told me to switch to 2G instead of 3G, and it really worked with no troubles.
I'm happy now that my phone has no defect
thanx. will try that. but do you know what exatly was the problem with the gsm?
I think the problem is in the GSM tower that is close to my house (this is what the communication company said).
My big brother has HTC Incredible S too, and when he switched to 3G, he suffered from exactly the same problem!!!
I don't think the two phones are defective; since we bought the first one from USA and the second from here.
Just try to force the phone to use 2G instead of 3G. you can do that from:
Settings >> Mobile & Networks >> Network Mode >> GSM only.
Selecting GSM only = 2G
Selecting WCDMA = 3G
Thanx again. I will give this a try
I had this problem once but after changing to 2G as u referred it worked just fine
There is widget on market called "2g-3g on off" for faster changing between these two modes. Very useful when you need 3g for faster web
aaaaaand. it seems to work. strange. unfortunately its 2g and not 3g....

[Q] Samsung Captivate calling problem on the 3 (Three) Network

I have brought two phones to the UK. Both of them are Samsung Captivates, one of which has Eclair, and the other has Froyo. I recently purchased a SIM card from the 3 (Three) Network and except for a small APN problem. Everything seemed to be working fine. Recently, I've been periodically unable to make calls from either of the phones. Text messaging and internet over the 3G network work fine, but when I try to call, it looks as though it connects, but I can't hear anyone and they can't hear me. If a friend calls me, I do see an incoming call on my phone, but when I pick up, we can't hear each other. I've noticed that when I reboot my phone after having the SIM card removed for a while, it connects for the first call made, and both people can hear each other, but after that first call, it goes back to not working. Has anyone here had a similar issue, or have any idea what could be causing this?
By the way, I was on the phone with 3 (Three) customer support, and they had me completely reset one of the phones, and the problem still happened. Also, I put in a SIM card that I knew was working, so it seems to me that it must be some weird compatibility issue with the Captivate, although I can't imagine why, because it's a phone almost exactly like the i9000 in Europe and the UK, and should be able to work fine with any network.

"Call ended" right after dialing

First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
640k said:
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
Click to expand...
Click to collapse
Hmm, it doesn't seems like poor performance. I ended up every task and it still happened.
However, I noticed that when I check the "2G ONLY" option it comes back to work. Maybe it's something with the HSPA/HSPA+ connection.
it could be completely carrier dependent then. my experience has been with vzw.
Moto X "Call Ended"
I have experienced this same problem in Houston on the T-Mobile network after switching over to Android. My T-Mobile rep told me they have had towers vandalized for copper which has impacted service for them, I believe he said it was about 15 towers and 10K a pop to get things corrected. What gets me is I was on a Bold 9900 and while I had signal problems in the affected areas of town I didn't not experience the "call ended" issue. I can also call other T-Mobile phones from those same areas but not land lines so to me this seems like a possible network routing issue which I have seen before between specific carriers.
If the problem does continue I may have to switch carriers. T-Mobiles service was previously outstanding in Houston but recently had not been great after the 4G LTE upgrades. I support multiple hospitals and need service to work correctly and will work with the T-Mobile Engineers to see if I can make headway on that front. I noticed another MotoX user reporting he only had the issue when flying in to Houston for work and that everything worked for him outside of Houston. His solution was to operate in 2G mode which for me is really not an option. I have to handle a lot of tasks over the network while on calls.
Anyways I would appreciate it if others could post if they are experiencing these issues and give as many details as possible so we can try to isolate the root cause of this problem and if found to be a carrier issue we can escalate with them. Thanks
dicarli said:
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
Click to expand...
Click to collapse
Call Ended Issue Resolved
Hi All,
I see this Call Ended Issue in many brands. So I assume the error is a combination of the Network along with the SimSlot.
I tried various combinations for my Moto-E mobile.
Before i post the solution i found, Let me provide a brief about the problem.
I use Vodafone network on sim1 slot and Uninor network on Sim2 slot. I started facing the call ended issue on my sim 1 vodafone network.
I inter changed the sim's and found the network working absolutely fine. This makes me to understand that the sim1 slot with the vodafone carrier has some network issue where that IMEI code has some problem.
i tried to place the vodafone sim again on the sim 1 slot and found the problem persists. So i came to that conclusion.
Hope this might help you and provide a instantaneous and temporary resolution.
Thanks,
Praveen.
Call Ended problem still going...
Hey,
I just rooted my Moto X (XT 1053), like 5 min ago, in the hope to fix this same problem. I`m no programer/developer and have nothing against rooting, I just don`t think I`m that kind of user. Anyway, about a week ago my phone started to drop my calls right after dialing. I restored factory settings, updated it and nothing worked. I took it for service and they offered to charge me 150 bucks to restore factory settings and update the software. So I was kinda forced to root and try to fix it this way. The problem is that I probably don`t understand half of what you guys say, so if there are any kind souls out there, please help me out.
To sum it up:
- No Sim Card error
- I get carrier services and can use mobile internet (3G because 4G is still too explensive here in Brazil)
- Directly drops my calls
- Won't receive calls
- Won't send or receive text messages via carrier (just over 3G or wifi)
I`ve tried another carrier's Sim Card, no go.
I`ve tried my Sim Card on another phone and it worked just dandy, so I really don`t think it`s carrier related.
I`m running Android 4.4.3, as the other updates weren`t available for my phone via Motorola. I thought maybe updating to a newer version of Android might do the trick. I just have no clue on how to do that on a rooted phone... or on a non rooted phone for that matter.
Can anyone give me any tips/pointers/etc... ?
Thanks!
I have the same issue with my moto x on Verizon. Have you been able to figure it out?

[Q] S4 Active call errror!!

Hello everybody. I just got a Samsung S4 Active phone. I have a big problem with it... When i call somebody i can not hear even the beeps and even the voices.. I need to recall somebody 3-4 time. Then i can talk . And when somebody calls me, we can't hear anything. I tried soft,hard, every resets. I even upgraded from 4.2.2 to 4.4.2 but nothing. The mic is working, i can record everything. The speaker up on the phone is working tooo. Call barring is off,forwarding is off, network mode is gsm only(not works even on the other settings..) i don't think that is a hardware problem.. any helps or everything is welcome.. you can even email me([email protected]) . PLEEEASE HEELP!!

Ear-speaker sounds high pitched in calls issue

Hello . I am long time follower of your forums but now i decide to make an account cause I got some troubles with my Note 5 .
I have a Note 5 model n920-c (Arab Emirates) but I live in Romania .My problem is that from time to time when I make or receive a call, the in-call sound from my ear-speaker is high-pitched almost screetching(but still manageable and understandable) ....
If I put the call on speaker the sound is normal...
This is happening to me only 2-3 times a day and it seems to happen only with calls made in my network(ORANGE RO)...In every other calls(whatsapp , facebook , skype) the ear-speaker sound levels are just normal...
Just to mention I also fave HD voice active for my network calls...
Its is a network provider issues ?Is it a hardware issues?Did some of you experienced such thing on your unit?
Happy to be a part of your forum from now on ! Looking forward for answers
Not even a tought? :crying:
Same problem here. Also n920c and also on orange ro. Problem apear when i call on orange and vodafone. And another problem today: while on lte i have full signal, i can call without problems but when someone tries to call me enter the voicemail. Switching to 3g solves the problem. Switching back to lte the problem reapears. Some ideas anyone? Thanks

Categories

Resources