Right guys, I have been on the Original Development section asking similar questions and had good suggestions, but here is the problem in a lot more detail as I don't want to spam the section with the same problem and get literally no reply as people are busier with other things on there. Basically the phone has it's two speakers, the earpiece at the front and the speaker at the back both of which are working and functional. However the problem lies in the phone calls. I bought the phone on stock firmware, latest UK generic update it was and everything was fine. I decided to root the phone and flash PA 2.13.1. As soon as I did this I came across a few issues, one being NFC not working and the current and seemingly unfixable issue that I have with the phone calls where, as I receive a call and answer it the microphone doesn't work, I can't hear anyone and they can't hear me. Both on loud speaker and through the earpiece. It's as if they disable when a call comes through. But when I hang up or they hang up I can hear the end call tone, the beep coming through the earpiece. So I know that it works. The same goes for loud speaker, however I already knew that it still worked as I can play music through it cleanly. It's in perfect working order.
I've tried several solutions, including flashing new modems, RIL etc. Flashing 3 part software. I have yet to try flashing the 3 part software with a .PIT file, like mx.pit as I simply can't find that file (if someone would be as kind to link me it) anywhere. I'm currently back on stock XXALE8 UK firmware. The problem is still there. I STILL can't make a phone call without this annoying thing happening, and as I said, the problem wasn't there before I flashed PA. It's so f****** annoying as I followed the instructions perfectly, I mean, I've been using android since 2009 and rooting and flashing is nothing new to me. I've never had an issue as severe as this one.
Anyways, thanks in advance for any suggestions you guys can throw at me, I know you'll all agree when I say the GS3 kicks ass and you'll know my pain when I tell you it's being a broken piece of crap haha!
EDIT: Right, I have made another definite discovery with this problem! It's to do with my signal. When I answer a call or make a call, it appears to connect to the caller for roughly about 0.01 seconds as it says it's connected, but then it hangs silent for a while, about 13-15 seconds before disconnecting saying there is no service in the area. Give it another five seconds and the signal reconnects. It is the exact same effect you would have if you were on the phone on the train and went through a tunnel, it would say you were connected when you aren't. Does this make sense, anyone know what the cause of this could be?
Related
So this has been happening randomly on calls for about two weeks now. I'm still on Stock everything and would like to know if this is a known problem, if something is wrong with my phone, or if there is a fix? I'm past the point of returning and getting a new one and plus, I have grown atattched to this phone LOL.
I've tried hitting speaker and then turning it off but that doesn't work. Tried ticking mute and then unticking it, not working either. Reboot doesn't work. Resetting back to stock doesn't change it either.
Thanks to all.
AJ
Sounds like a typical ATT phone call. Would you and the person on the other end both happen to be on speaker phone? I cannot have a call via speaker to my wife if she is on speaker (which see insists on using) - there is too much voxing going on, I only hear every couple of syllables.
T
Sent from my SAMSUNG-SGH-I777 using XDA App
Not a speaker phone call. Seems like it happens mostly when I make calls from speed dial from my homepage screen. I can't conf
irm that last bit though lol.
Another question is this....I just turned my phone completely off and it had 42 % battery. When I turned it back on it now has 22% left.....what in the world is going on lol???
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
asjdwf said:
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
Click to expand...
Click to collapse
I need more details to say this for sure, but I THINK you may be having the same issue I had. Not many people seem to have this issue (only seen a handful across a variety of forums). So if you happen to be a fellow sufferer, then welcome to the club!
My problem was:
After the 2.3.6 update (UCKK6), the person on the other line had trouble hearing me because my voice cut in and out frequently, yet randomly. On my end though, they came in nice and clear. I often had to deal with people hanging up on me because they thought my call dropped or that I hung up, or had to deal with a lot of people repeating "hello? hello!? You there!?" as I helplessly tried responding and not being heard.
My Solution(s):
1) keep the 2.3.6 update, but flash just the 2.3.4 (UCKH7) modem. Everything on your phone will work fine, but you will get the following FALSE warnings (FALSE as in the phone says it can't do something, yet everything works fine anyways. These are only based on first-hand experience and may not happen to you.)
a) upon boot (not wake/unlock) there will be an error notification about you not being able to access your external memory card due to security reasons... don't worry, its bull.
b) when using your phone as a mass media storage device, you will get a notification about the mass storage function not being able to work... this message is also bull.
2) Or you can just completely return to 2.3.4 (UCKH7) and either ignore the update prompts or freeze the process until a newer update that hopefully fixes our problem (or ICS) is released.
I did (1) for about 2 weeks then did (2) after reading all the battery complaints blamed on UCKK6. It reverted just to play it safe with battery life (plus they say that "if it ain't broken, don't fix it" and for me, UCKH7 wasn't broken and the update definitely broke it).
Wow, that sounds identical to me except its they can hear me but I can't hear them LOL. I reverted last night with odin one click downloader and the stock kernel for battery life so we will see what's going to happen today. Is this a phone problem physically or is it software?
Thanks
AJ
For me, its a software issue (modem to be specific) because it only happens on UCKK6 (and the leaked UCKJ1, UCKJ2, and UCKJ4) and when on UCKH7, my calls are as clear as a LAN line.
I say that if the problem still exists now, then its hardware. In that case, try contacting Samsung for a replacement if your ATT warranty is up. You could try ATT too because its a defective phone and they may still do something.
Starting 5 days ago, I've had this issue. Googling it, it's extremely common and has no fix other than sending the phone to Samsung:
Symptoms:
- On making a call, starting from today (really yesterday), I get no audio going in or out. However both speakers are work fine, because the earpiece makes a beep sound to let me know call forwarding is active. The rear one works for everything.
- Headphones in call don't work either
- Sometimes I get sound for one call until I hang up, or it's very crackly and
useless.
- While ringing when dialing out (or rather, when you WOULD be hearing ringing if it was working), sometimes it'll cut the call and say "OUT OF SERVICE AREA", and then I'll get the circle with the line through it where signal is supposed to be. Signal is back seconds later.
- Data and texting work fine.
Things I've tried:
- I was on Omega ROM 13.1 with Siyah 1.5.3, although I've read online people have this issue bone stock, unrooted.
- Flashed stock insecure kernel
- Flashed several different modems
- ODIN'd back to the ROM that came with the phone (was originally a real-SIM-unlocked, Vodafone Germany i9300).
- Wiped everything possible
I'm willing to donate via Paypal to whoever has a definitive fix for this problem. It's really driving me insane that I don't have a working phone for calls. Worst case I'll call Samsung, but I expect they'll charge me an arm and a leg, if they even accept it considering it's from the UK originally (bought it off Amazon in June). This seems like a software issue, not a hardware issue consider both speakers still physically work fine. The issue is, what the hell is causing it if it came about completely randomly, and is happening across all ROMs, kernels, and modems that I flash?
Before you ask, no the Accessibility Setting for turning off all sounds is not on.
Thanks in advance for anyone that replies.
Click to expand...
Click to collapse
I have a feeling the area where the modem data is stored is corrupted. Odin 3.07 has a "NAND Erase All" option, but I don't think it's really safe without having a copy of the bootloader, in case that gets wiped to. So anyone have a copy or any suggestions? I really don't want to ship this phone to the UK to get it fixed. Here's a video of what it looks like (not my video):
http://www.youtube.com/watch?v=fo46OXWEcX0
Hi, this really has me stumped, and I can't figure out what could be the issue.
Any help would be appreciated.
My S3 (I9300) was running CyanogenMod nightlies, and suddenly I stopped being able to hear or produce sound in calls. I can initiate the calls, and can receive calls, but when I accept the call, there is no sound, and the other end cannot hear me either.
I thought this was an issue with the ROM, and since I was running an older nightly i installed a later one. The issue was still there.
So I did a full wipe and installed the latest M6 CM rom, and the issue still occured.
I did another wipe, and installed a different rom, still the same happened.
So i finally did a full wipe, and installed the stock 4.3 rom from SamMobile. This didn't help
I don't see how it can be a software issue, as my mic is working perfectly, and so is my speaker. It is only in the voice calls that they do not work.
Any ideas?
Thanks in advance
If it still the same on a fresh stock installation then it sounds like a hardware fault.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If it still the same on a fresh stock installation then it sounds like a hardware fault.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply
I would say it has to be a hardware fault, as I have wiped the phone several times.
However, I really can't see what could be wrong as all the separate things are working. The mic and speaker are fine, and I have full signal and can make and receive calls.
What part in the phone could need replacing?
Unfortunately, the motherboard -nobody replaces component parts anymore.
Sent from my GT-I9300 using Tapatalk
Mine does the same thing, it's a software/hardware problem, do you keep your phone on silent a lot?
Someone gave me a fix in another thread and I've not had the issue since. Basically there#s a software or possibly hardware error that causes this. If you try and make or receive a call without the phone having already played any sound since start up then you get this bug. I rarely restart my phone so for me on the odd time I do, once it's started up I just play a song for a second or two then stop it and calls work fine. Since doing this I've not had the bug. Others have automated a sound on start up with tasker or similar.
Sometime upper noice cancellation mic causes the problem. Little cleaning may fix. If u good @ opening phone then try yourself. Otherwise go to a technician.
My mom's S4 has been a good little workhorse for a year now, but recently it's started acting bizarrely. At random, when she dials, nothing will happen. It will say dialing, the call timer will start, but she can't hear a ringing tone, the caller, and the caller can't hear her. I've looked this up, and it seems to be a common enough problem for S4 users, with no solution that I've been able to find. I've tried to see if something is jamming the headphone slot, but nothing is in there. The only way we can get calls to work again is to reboot the phone, and that works only around half the time.
At the same time, any time this problem is present, Wifi won't auto-connect, or connect at all. It will recognize the hotspots around us, but it just marks them as "saved". If I try to connect, it attempts it, then reverts back to saved. This fixes itself after the reboot as well.
Does anyone know what's going on? Is this a hardware problem that I'll need to replace the handset because of? Will a factory wipe or a ROM fix this? I've been wanting to try a clean, easy ROM for her, so maybe this is the time? Any help would be greatly appreciated.
On the subject, any suggestions for ROMs? The Google Play Edition one looked nice, but I didn't know if that came with any significant down sides for her. Thanks in advance!
greycobalt said:
My mom's S4 has been a good little workhorse for a year now, but recently it's started acting bizarrely. At random, when she dials, nothing will happen. It will say dialing, the call timer will start, but she can't hear a ringing tone, the caller, and the caller can't hear her. I've looked this up, and it seems to be a common enough problem for S4 users, with no solution that I've been able to find. I've tried to see if something is jamming the headphone slot, but nothing is in there. The only way we can get calls to work again is to reboot the phone, and that works only around half the time.
At the same time, any time this problem is present, Wifi won't auto-connect, or connect at all. It will recognize the hotspots around us, but it just marks them as "saved". If I try to connect, it attempts it, then reverts back to saved. This fixes itself after the reboot as well.
Does anyone know what's going on? Is this a hardware problem that I'll need to replace the handset because of? Will a factory wipe or a ROM fix this? I've been wanting to try a clean, easy ROM for her, so maybe this is the time? Any help would be greatly appreciated.
On the subject, any suggestions for ROMs? The Google Play Edition one looked nice, but I didn't know if that came with any significant down sides for her. Thanks in advance!
Click to expand...
Click to collapse
Sounds like a factory data reset is long over due. It should fix any issues thats been going on. If not I would take it into Verizon to get looked at, or call to get a replacement.
Hello,
My problem is very weird and i couldnt find any solution for it yet. Some time ago when someone was calling me i couldn't hear the voice and the caller couldnt hear mine, when i turned speaker on it was all fine. I tried to work it out by installing and uninstalling certain things in the phone and'ive come to the stage where if i try to call someone or someone calls me my phone freeze (nothing can be done) and then restart itself.
My current ROM is latest nigthly CM 12.1.
What could possibly cause this? I wiped everything possible like 3 times already, made factory resets, installed rom again and again, nothing helped..
EDIT: Ive tried installing different ROMS, CM11, CM12.1, Stock Rom, still same issue.
Loading the backup (5gb) of the phone before flashing it and doing all the stuff didn't help...
I had a similar issue on my old S4. Turned out to be one too many "drops" by my baby, cracked the circuit board behind the glass. This caused issues with calls not going through, cant't hear people, it disconnects by itself, sporadic reboots, some force closes, and eventually me trading it in for the S5..lol That was my 2nd replaced board in that S4 in as many months. Needless to say, my daughter does not play with daddy's new phone any longer..lol That was my experience, hope it helps. Good Luck!
Thanks for the answer, but unfortunatly i treat my phone pretty good and it would be a big coincidence if something mechanicly broke inside it, as i said it happened the same day as i uninstalled Hangouts and something else with Root App Deleter...