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.
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.
The only way for people to hear me is if I am on speaker or using a head set. I've tried many different roms all with same results except cm10 people can never hear me (not tested with headset, only speaker). I believe my phone is using the top mic (noise canceling one) as opposed to the one at the bottom. When I talk into the top mic I am being heard but I am still very hard to hear.
Does this sound crazy? Anyone have any idea how to fix or why this randomly happened?
Got the same problem but my speaker Mic doesn't work either. Gonna have to get me a Bluetooth cause I can't take it back to Sprint cause there's no RUU for 3.16
Wreaking havok from my EvoLTE CyanogenMod 10.1
S-on
Did you really have to make two threads for the same question. Bad etiquette!
But, did you do a "FULL" wipe before flashing a ROM? If yes, perhaps you should run RUU to go back to complete stock then start over. If that doesn't solve the problem, not sure.
wolfclan68 said:
Did you really have to make two threads for the same question. Bad etiquette!
But, did you do a "FULL" wipe before flashing a ROM? If yes, perhaps you should run RUU to go back to complete stock then start over. If that doesn't solve the problem, not sure.
Click to expand...
Click to collapse
I created a thread even before his addressing the same exact issue. My issue was a result of a faulty device replacement from sprint. I had to get another replacement from sprint to resolve the issue. I suggest you do the same, but you can try a clean wipe and flash a stock rooted rom and see if the problem persists. If it does I would take it to sprint and get a replacement.
P. S. Next time search first before posting because I did address the same exact issue about a 3 weeks ago
Sent from my Viper'd LTE
Well, I was running rootbox for i717 and everything was working fine for a month, Then suddenly out of no where for no reason at all my phone got super laggy, apps started crashing, and my sound stopped working, I mean completely not through the headset not through the speaker nothing!!! So my first thought was something was wrong with the rom, so I tried a factory data reset, I tried re-installing it, I tried 3 other roms, cynagenmod10, Jellybeer and xylon, Finally I did the farthest restore to my stock gingerbread rom, and still the problem priests, in fact its getting worse, I don't know what to do at this point I am completely out of ideas. Could this be a hardware issue? its the only conclusion I can come up with, but its still strange, because if it was just my speaker I would understand hardware issue, but my speaker, my earpiece, my headset, and Apps crashing, super Lag, I can barley even get my keyboard to pop-up then it dispersers. What is going on!!! Please help me oh great devs.
Well, assuming you did complete wipes and factory resets as you flashed each Rom, I'd say you eliminated software.
Did you leave the phone somewhere that let it overheat? Or used a non-OEM charger? Or overclocked it?
majicmazo said:
Well, I was running rootbox for i717 and everything was working fine for a month, Then suddenly out of no where for no reason at all my phone got super laggy, apps started crashing, and my sound stopped working, I mean completely not through the headset not through the speaker nothing!!! So my first thought was something was wrong with the rom, so I tried a factory data reset, I tried re-installing it, I tried 3 other roms, cynagenmod10, Jellybeer and xylon, Finally I did the farthest restore to my stock gingerbread rom, and still the problem priests, in fact its getting worse, I don't know what to do at this point I am completely out of ideas. Could this be a hardware issue? its the only conclusion I can come up with, but its still strange, because if it was just my speaker I would understand hardware issue, but my speaker, my earpiece, my headset, and Apps crashing, super Lag, I can barley even get my keyboard to pop-up then it dispersers. What is going on!!! Please help me oh great devs.
Click to expand...
Click to collapse
Your best bet is to go to RootzWiki where the dev work is done for those ROMs .. And post this in the threads... I myself am running root box .... Go there .. XDA doesn't support these roms anymore so that's where you need to go
Sent from my SGH-I717 using xda app-developers app
did you do the 3 wipe procedures when installing the firmware?
there is more than just 3 wipes you can do .....depending on a dirty flash or a clean install or a complete wipe and clean install...you also have android secure ...internal ....external
Sorry for the delayed response
Well, yes I did always do the 3 wipe method, I did the complete wipe as well, and I saw no need to talk to the rootbox dev, (whos name im terrified of mentioning on xda in fear of getting banned lol) because I tried other roms from other devs and the problem still persisted, then I went to the stock rom and still had the problem, then I unrooted the phone and did one last complete wipe, re-installed the stock gingerbread rom, and still had the issue, so finally i gave up and got in contact with the guy on ebay who sold me the phone, and luckily he was more then willing to give me a replacement, then I got the note2 and was (still am) busy trying to sell this one, so I really just forgot I had this post up until I logged in right now so that is why the long delay, Thanks for your help guys but in the end im still pretty sure it was a hardware issue, but since Its back in the hands of the seller and I have new one we will never know for sure
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.