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.
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.
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.
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
Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?
Wow no wonder Ive been late to work all week. Phones doing the same thing.
Sent from my SCH-I605 using Tapatalk
As an update from my fiddling about this morning, it seems to only happen when the lock screen is set to the Swipe method. If set to a pattern, pin, anything else, this error doesn't occur. A temporary workaround at best, as this no longer allows me to access multiple lock screen widgets.
Wow man.. since my last post I wiped and am running a new rom, kernel, everything.. still doing it ?
Sent from my SCH-I605 using Tapatalk
I believe I've narrowed it down to a few possibilities, between it being the new ripple/ink effects on the lock screen or something to do with the multiple widgets. I can't believe we're the only ones dealing with this. Does anyone have any insight if even a complete reset, rom flash and kernel swap hasn't fixed it?
As another update, I appear to have been mistaken. While delayed slightly, the end result is no matter what, the alarm eventually silences itself after a few seconds, unknown why.
I had the same thing happen using n3bula (4.3) rom. Alarm would turn itself off. Didn't really have time to mess with it so I went back to beans 22 (4.1.2). If you figure anything out, let us know
Sent From My Sticky Note, Too?
As another update from yet more fiddling. I tested it this morning as it would normally be, hooked up to my computer charging, with my bluetooth headset on but also sitting on its charger. The alarm cut out even with pin set as the lock screen. When removed from the cable connecting it my computer and my headset on my ear, it didn't. Going to test further.
So, as yet another update, I believe I found the problem, a reply from prior posters experiencing the same thing would be helpful to see if it was the same issue. I have one of the original sony android smartwatches that connects through Bluetooth. On a hunch, I disabled Bluetooth on my phone before going to bed a few nights and wouldn't you know it, no problems. Did it again with the watch off and just the headset connected, again, no issues. Seems the watch is a bit too dated or butts heads with the MJ9 firmware driving the Bluetooth module.
So as to follow up. In my situation specifically, my music player is Poweramp and I noticed whenever my headset is connected and my alarm is going, it immediately tries to take over and start playing music, I think that's what caused my alarm to go silent. My headset is the Plantronics Voyager Legend, my smartwatch is the original Sony Smartwatch, I don't know if the combination of the three are relevant to the others in this thread having the problem.
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
ForcePhenomenon said:
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
Click to expand...
Click to collapse
when you wipe do you also format internal sd?
MunkinDrunky said:
when you wipe do you also format internal sd?
Click to expand...
Click to collapse
Correct, thought I'd noted that when I said clean wipe. I wiped internal storage, cache, everything you should when flashing a new rom, going to the point of doing it multiple times and even dirty flashing a few times to see if that would fix the problem (as it did fix some issues going on with n3bula and they actually recommend doing it.) But, nothing of the sort happened.
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
MunkinDrunky said:
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
Click to expand...
Click to collapse
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
ForcePhenomenon said:
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
Click to expand...
Click to collapse
have no idea but since it was a variable in this situation I thought to try to rule it out for certain.
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...