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
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.
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.
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?
Hey Folks,
i ran into some really weird, yet strange Problems with my Honor 7. Let me tell you what happend:
I used my Phone on B140 for more than 2 Years without any Problems. Now i upgraded to B396 (Removed Root+ChineseTWRP, Full Update to B396, then installed TWRP+SuperSU), and used it afterwards without any Problems for like a Week or so.
Then, i was on my Way, looked something on on Facebook, turned it off, after 2 mins wanted to turn it on again - no Reaction. Totally nothing Tried booting it up Normally, to Recovery, To Fastboot - with and without plugged USB to PC, absolutely nothing happend. Had it on Power for like half an Hour, nope. I was shure it died.
The morning after, i just pressed the Powerbutton as a way 2 say goodbye - Empty Battery Sign! Wtf?! I was able to charge and use it again. Unfortunatly with some minor Problems.
- Whatever i try, when calling, i can clearly hear the other person, but the other part cant hear me. I tried it both with headsets and normal, in- or outgoing call, doesnt matter. Generally the mic is working, though. Was able to record my voice and play it back.
- Bluetooth aint working anymore. When i try to turn it on, the switch stays in the right position (doesnt change the color anyway), and afterwords its flipping back. Oh, and when i look at the "about"Section, under Bluetooth Mac it states "not available".
So. What the h*** is going on there?! Like i said, after upgrading to B396, it was working for at least a week without any problems, without the problems described above. So i highly doubt its a general problem with the upgrade/flashing. But what else?
And, any advice how to a) fix and b) prevent further failures?
Of course it would be best to know what initially caused those problems, but i really cant tell. Anyone any ideas?
Like anyone else of course, one needs a reliable phone. I mean, im happy that i can at least communicate over IM (yes, 3G/4G works without any Problems). But i'd love to make calls again, to e.g. tell my boss id be slightly belated or let mum know everythings alright :laugh:
So, any Idea what caused that, how to solve and prevent that is highly appreciated!
Greetings and Thankin u in advance!
Folks, i still have that strange Issue/Behaviour (though, of course, in the Meantime im using another Phone ).
But think that should be possible to totally, absolutely, reset the Phone, and trying to get rid of those Problems. Too Sad to see the Phone collecting dust, where it might be a great Device for a Friend.
What i did by now:
Unroot
Reflash Fastboot recovery, boot, cust, system.
Factory Reset
Update.zip in dload
But there is still no Bluetooth-Adress available, when calling i cant hear the other Person.
It somehow seems not to completely reset the phone - there are still user-data on the Phone.
As i really dont care about those data - is there something else i can do above fastboot flashing those files mentioned above, to absolutely start from a scratch?