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.
Related
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
I googled vibration not working galaxy s2.
Found this but I didn't watch it as I am not on wifi.
http://www.youtube.com/watch?v=3JA3PXNYjJM
gerbs said:
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
Click to expand...
Click to collapse
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
jcordova23 said:
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Yeah, already called att for a replacement and its on the way. Finally decided to give up after getting it back to 100% stock (kernel rom bl etc).
I literally tried everything. But in the end it makes sense that it is a hw problem since so many others have run into it too. Poop.
i watched the video you showed. i started to mess around with my settings while i inserted my headphones on. Somehow, everything is fixed but the vibration is not as strong as before.
Furthermore, my aux does not work with this phone sometimes. It would need to be connected a certain in order for it to work.
I probably dropped my phone while I was working out while i have my headphones on. The connector probably got messed up in the process.
I might need to send my phone in for a replacement. Since i'm not under warrenty, i might send my phone to a lab. I'm pretty sure they can do something about it.
iichrisphamii said:
I might need to send my phone in for a replacement.
Click to expand...
Click to collapse
The vibrator turned out to be a hardware issue for me as expected, fyi.
I haven't found any definite information on this issue so that's why I'm starting a thread.
Yesterday, I noticed during a call that I could hear nothing but saw for certain that I was connected to a call and that call volume was all the way up. When I tried speakerphone, everything was normal but as for the built-in earpeice, nothing. The same goes for Bluetooth, everything works normally, but once again, with the ear piece that you out to your head in a normal call, no luck.
WHEN I NOTICED THE ISSUE:
I have been using CM9 nightlies for quite some time (with h0tw1r3's kernel) and had no problems until yesterday when I flashed the Black Star stock ROM out of curiosity of stock functionality. I never made a call in the Black Star ROM to know for certain if the issue took place immediately after flashing it before I had already reverted back to CM9 where I found the issue for the first time.
WHAT I'VE TRIED:
I have already tried flashing three different ICS ROM's (including the Black Star ROM again) wiping EVERYTHING including not only /system, /data, /cache, and Dalvik, but even the internal SD and my external just to rule out any corrupt data that could be interfering. No luck...
Although I've personally never experienced any issues with audio since SGH-i717 development really began, I remember reading that a few people had some audio issues with ICS along the way and am wondering if this could be related. At this point though, I'm thinking it's a hardware issue and not software so I'm expecting to have to replace the phone, although this didn't happen until I flashed the Black Star ROM yesterday which is odd or coincidental if it is solely a hardware failure and not software.
I may try and see if I can get a warranty replacement by resetting the flash counter and leaving only the stock download mode with no third party recovery before I send it in.
But, before I go through the trouble, is there anyone who has encountered or is familiar with this issue that can propose a possible solution?? I'd be extremely grateful for any assistance and would gladly make a significant monetary contribution to anyone providing a solution.
***UPDATE***
Replacement SGH-i717 has been dispatched to me through Samsung warranty. They didn't have any issues or hesitations about replacing my phone for this issue which leads me to believe they've seen it a few times already so for those of you having the same issue, don't hesitate to call in a warranty replacement! I'll let everyone know if Jelly Bean runs better on my new device to answer the question or whether some Notes have defective GPU's that don't work with project Butter or not.
Thanks,
If it persists from rom to rom then logic would say it must be a hardware issue. Get your phone back to stock and get your replacement
Sent from my SAMSUNG-SGH-I717 using xda premium
jpoirier587 said:
If it persists from rom to rom then logic would say it must be a hardware issue. Get your phone back to stock and get your replacement
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I thought so too... On the phone with warranty now! Maybe my replacement will work better with the current Jelly Bean previews. As of right now, Jelly Bean runs less smooth than ICS for me.
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
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?
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...