I have had my S3 rooted and flashed several roms over the last 2 years and this has never been an issue before now. I cannot call any automated systems: It rings once then just echos anything I say. This issue started out with it not recognizing my DTMF with Slimkat so I moved back to CM11. After reading that it might be a kernel issue I went back to stock and still have the same issue. I have tried several different numbers as well. Any help would be awesome. Thanks!
Related
So, this is my short story:
I've had this phone for 6 months. I've had it rooted for about 5 months. I've used tons of Roms, and have had no problems whatsoever. I have several Nandroid backups as well, each dating around 2 months a part (each).
/End Story
Problem:
All of the sudden, I called a friend to find that the in-call volume was EXTREMELY low. I turn it up all the way and could only faintly hear him. He sounded a mile away. I had to turn it on speakerphone to finally make out what he was trying to say.
Things I've Tried:
I've tried going back to each of my Nandroid's, when the sound was working, and nothing was fixed. I've tried Factory Reset with no results. I've wiped cache/dalvik cache - nothing. I've tried messing with Hearing Aid settings - nothing. I've tried turning the volume all the way down in the call, and then turn it all the way up to see if it fixes it - no results.
Currently I'm running the Infected Rom 3.5. But I tried calling people on MIUI, Sense 3.0, etc, with no results thus far.
Question:
WHAT could possibly be causing this? It's not like I blew a speaker, I've never done any volume adjustments on my phone with an app or anything. The receiver still works, as I can hear them, but they sound near non-existent until I switch to speakerphone.
Any guesses/suggestions?
Diabetic said:
So, this is my short story:
I've had this phone for 6 months. I've had it rooted for about 5 months. I've used tons of Roms, and have had no problems whatsoever. I have several Nandroid backups as well, each dating around 2 months a part (each).
/End Story
Problem:
All of the sudden, I called a friend to find that the in-call volume was EXTREMELY low. I turn it up all the way and could only faintly hear him. He sounded a mile away. I had to turn it on speakerphone to finally make out what he was trying to say.
Things I've Tried:
I've tried going back to each of my Nandroid's, when the sound was working, and nothing was fixed. I've tried Factory Reset with no results. I've wiped cache/dalvik cache - nothing. I've tried messing with Hearing Aid settings - nothing. I've tried turning the volume all the way down in the call, and then turn it all the way up to see if it fixes it - no results.
Currently I'm running the Infected Rom 3.5. But I tried calling people on MIUI, Sense 3.0, etc, with no results thus far.
Question:
WHAT could possibly be causing this? It's not like I blew a speaker, I've never done any volume adjustments on my phone with an app or anything. The receiver still works, as I can hear them, but they sound near non-existent until I switch to speakerphone.
Any guesses/suggestions?
Click to expand...
Click to collapse
As with more abnormal issues such as this, the best recommendation, in my opinion, is to revert to a stock ROM, kernel and clear the /data partition.
This will ensure the device is running 100% stock software. If the issue still persists with stock ROM, kernel and a cleared /data partition (test before loading 3rd party apps) the final conclusion would be a hardware related issue. At this point, should be able to take the device in for service.
If the issue disappears on a stock setup, then you can start eliminating possibilities such as a specific ROM, kernel or 3rd party apps which could be impacting the volume.
Hope that helps!
^
I pretty much did as suggestion, but I decided to put on an almost-stock ROM (with some visual differences) to sprint first. When I told the technician the problem, he noticed the rooted phone and said that it was because of my software. I knew it wasn't, because of all the resetting I had done, different nandroids, etc, and that it was the in-call receiver. He stated he was 100% sure it wasn't.
I went home, went back to full stock. Same problem. Took it to a different sprint store and they said that there was a connector issue, and since they didn't have the part - they will order me a new phone for 38 dollars (I didn't have a warranty).
Not too bad. Too bad the d*ck at the sprint store couldn't have looked at it first, as he would have seen that. But oh well. Whatchya gonna do?
Decided to post this in case someone has similar issues.
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 am on jivy's ICScrewed 2.1 ROM running Siyah's last GB kernel. From time to time, my phone will suddenly become unable to receive text messages. I found this: http://forum.xda-developers.com/showthread.php?t=891427. I do believe it's the same issue, but I was wondering if anyone knows the cause. I have been using this ROM for a while now, and this never happened. Only a couple months ago did this start occuring. Then lately, it's been happening more frequently. Instead of having to wipe and recover maybe once every 3 months, it's been turning into every month, then every 2 weeks, and twice within one week this week. It's just a pain in the ass to have to keep doing this. I'm not sure if it's the ROM itself. If it was, then wouldn't I have been experiencing this when I first started using the ROM? If anyone has a (permanent) fix for this, I'd appreciate it. I hate waking up to no texts. Makes me feel lonely.
simplicityy said:
I am on jivy's ICScrewed 2.1 ROM running Siyah's last GB kernel. From time to time, my phone will suddenly become unable to receive text messages. I found this: http://forum.xda-developers.com/showthread.php?t=891427. I do believe it's the same issue, but I was wondering if anyone knows the cause. I have been using this ROM for a while now, and this never happened. Only a couple months ago did this start occuring. Then lately, it's been happening more frequently. Instead of having to wipe and recover maybe once every 3 months, it's been turning into every month, then every 2 weeks, and twice within one week this week. It's just a pain in the ass to have to keep doing this. I'm not sure if it's the ROM itself. If it was, then wouldn't I have been experiencing this when I first started using the ROM? If anyone has a (permanent) fix for this, I'd appreciate it. I hate waking up to no texts. Makes me feel lonely.
Click to expand...
Click to collapse
I've been having the same problem intermittently. I had it today and 2 days ago. The temporary fix is to take the SIM card out of my phone and put it in my old BB Bold 9700 to get the missed texts then put the SIM back into my SGS2. Then the texting works again. But the problem eventually comes back. It's not a ROM problem. I'm rooted and using a Gingerbread ROM. I don't know what causes this. I've tried wiping the Dalvik cache and deleteing old text messages and this didn't seem to work. The SIM switching seems to be the only trick. I haven't called ATT. (They are usually in denial when there is some kind of issue on their end.)
If you find a solution then please post it!!!
I have had the same problem. Running the same ROM for a long problem then recently (~last 2 months) it started happening. I was running Sashir's Aberration ROM but it was the old (pre Dec. 2012) version.
One time I contacted at&t and they said my sim was an old outdated version so they gave me a new one which fixed the problem... for a couple weeks. I may go several days receiving no texts (send works fine) then all the sudden I get them all in one batch. After that it will receive texts fine until it eventually happens again.
I just flashed the new Aberration and hopefully it stops happening.
Sent from my SGH-I777 using xda app-developers app
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.
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...