So I recently just rooted my droid and I'm running the evileris firmware atm I'm really happy with everything except that my phone can no longer make phone calls. The sound during phone calls does not work and I think it may not work sometimes in the music player as well. It works when I plug in the headphones but when i take them out no sound.
Airplane mode and resetting do not fix this problem and the updates that I've tried flashing from [FIX] Audiofix. NEED TESTERS FOR NEW KERNEL in the Hero CDMA forum do not work either.
This phone worked fine before rooting and flashing and the problem is present on all the roms I've used. The update above simply hangs my phone at the bootscreen, no matter which one I use. (Maybe its written just for hero?)
Anyways I was hoping one of you guys could have a fix or maybe have also had this same problem? Thanks!
(from what I've read in the thread above it seems the issue is a bad kernel that hangs up or fails to reset so you have to do it manually, but resetting doesn't fix the issue for my. My problem is constant phone call audio loss)
UPDATE: I have done some more experimenting and it seems the only problem is from the in-cal speaker, because when I put speakerphone on it works fine. The problem lies with the front speaker (part that goes to your ear).
maybe your phone is broken?
I went back down to 1.5 root, works fine. Its an issue with 2.1 :/ So currently I have 2 nandroid backups, 1 of 1.5 and 1 of 2.1 so I'm just switching in between the two.
did you try....
Did you wipe before flashing? After flashing did you try *228 opt 1? This may help as it sorted my audio issues with another Rom.
im having this same problem and i have no clue why i have tried everything knows possible to fix this.
I wipe before each flash as well as each recovery haha. atm my setup is 2.1 evil eris for the weekends and 1.5root for the weekday when i actually need to make calls
*228 opt 1 did not work btw
I just make a new backup at the end of the week and recover to the other one, works like a dual-boot pc or a bootcamp mac. It works, but its getting kidna old I'd rather just have 2.1 for good haha.
Longtime lurker.....1st time poster....I just installed leak v2 (I was one of those that was too impatient to wait for root)...I had the same problem that everything worked fine except the phone had no in call sound. went through all the setting and found that TTY was set to full...I unchecked it and the sound came back. I know this may be simple...but it worked for me.
brianwin33 said:
longtime lurker.....1st time poster....i just installed leak v2 (i was one of those that was too impatient to wait for root)...i had the same problem that everything worked fine except the phone had no in call sound. Went through all the setting and found that tty was set to full...i unchecked it and the sound came back. I know this may be simple...but it worked for me.
Click to expand...
Click to collapse
yesss thank you this worked for me.
BrianWin33 said:
Longtime lurker.....1st time poster....I just installed leak v2 (I was one of those that was too impatient to wait for root)...I had the same problem that everything worked fine except the phone had no in call sound. went through all the setting and found that TTY was set to full...I unchecked it and the sound came back. I know this may be simple...but it worked for me.
Click to expand...
Click to collapse
I'm having the same problem... During a phone call, I get no sound / can't hear the person I am calling from the "internal speakers" (i.e. the one you hold to your ear during a call). If I switch to external speakers (i.e. loudspeakers) I can hear the person I'm calling...
What is this "TTY" setting that fixed this problem for you? Where can I find it and uncheck it?
My SGS2 stopped vibrating. Tried flashing, un-rooting, restoring stock and factory settings. None of these worked.
I am inclined to think that it is a hardware problem.
Has anyone else been dealing with issue? I read some posts on XDA regarding this matter but they were software related as opposed to hardware. Can anyone post instructions on how to fix it or provide any solutions for this issue?
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
UpInTheAir said:
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
Click to expand...
Click to collapse
Cannot get jig in Palestine. Bought the phone from the UK. Sending it back will be problematic. I will look for a repair shop.
Thanks for the quick reply
That's a "bummer" (bad luck). You could make a jig, but as you said that it would be problematic to return. Hope you can sort it easily. Sorry, can't think of anything of use right now.
Sent from my GT-I9100 using xda premium
hey there,
i got the same problem. no more vibrating at all. not with calls or notifications and not as haptic feedback. it started today (was still working in the morning), though i did not drop the phone or anything.
i am still hoping too find that it's a sw-problem. but all potential solutions i find do not help. so i guess i have to contact samsung.
but before i do that i have to get rid of all "hacking".
could you plz tell me what i have to do?
i have now cm9 20120402 nightly.
but i still have a cwm-recovery-backup of the original touchwiz (gingerbread).
-so first i make a backup of my current rom via cwm and of all my apps via titanium and store everything on my pc.
-i flash my touchwiz-backup
-i get one of those: http://www.amazon.de/s/ref=nb_sb_no...ld-keywords=Samsung+Galaxy+S2+USB+Jig&x=0&y=0 , plug it in, wait til its done and remove it again.
after that, samsung will never know i "messed" with the phone??
or do i have to consider/do something else?
tyvm!!
kws
I have the same issue.
When I was on my stock 2.3.5, I found a workaround:
- go into test mode (dial *#0*#)
- find the vibrate button, when you press it, it shouldn't work like you expect
- go back
- plug in your headphones and push the cable a bit to the left
- test vibrate again - this time it should work
- pull the cable out while vibrating, still pushed to the left, vibrations should stay on
I know it sounds crazy but it seems the hardware part that controls the vibrations is near to the jack port - excessive use of headphones, like it was case, must have damaged it somehow.
However, now I'm on CM9, so no test mode for me, I'm achieving the same effect by bashing the back button, so I get semi-constant vibration. I know, It's ridiculous.
Have the same problem here, I think it's software related because the shut down vibration stopped working when I flashed CM9 ICS, I can't remember if it was working anywhere else though. But now I'm back to 2.3.5 and it's not working at all. Did a Factory Reset, Cleaned Cache before and after the flash. Also used the Jig to reset my counter. Any clues?
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
dajomas said:
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
Click to expand...
Click to collapse
I saw something similar on CM9 thread, they said it could be a "bad flash", not a corrupted rom but the lack of proper cleanup before and after the flash. But I cleaned up everything before and after and I don't like reconfiguring the whole phone again for nothing.
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
kweso said:
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
Click to expand...
Click to collapse
I assume since your posting in xda developers that you are rooted?
If so, just back up data with titanium backup app and factory reset, setup system and then restore USER apps and data only.
Sent from my GT-I9300 using xda premium
kweso said:
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
Click to expand...
Click to collapse
Did you install another rom?
My vibration for example didn't work with some cm10.1 nightlies
it started in cm10.1 20130203. then i tried wipe cache and dalvik. nothing. then i updated to 0206 (wiped cache and dalvik again) > still nothing. went to bed. got up. everything ok! its vibration again! i am 100% sure, it did not work, when i left it on my desk last night. this morning, i checked for missed calls and it took a moment until i realized: i got haptik feedback back on patternunlock and keystrokes! checked ringtone-vibration: fine as well!
dont ask me how! would still like to know for myself.
thx,
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
call me stupid!
suddenly this evening my phone stopped vibrating again. then i realized: quiet hours! i turned off haptik feedback at night.
could slap myself. at least ill find this thread again, next time i screw it again....
nite,
kws...
...tapatalking
Girls can use it again then. Good news for them!
Sent from the little guy
So I have run in to a bit of a snag, and though I doubt it is ROM specific, I thought I'd start by asking here to see if anyone else has run across this and might have a fix
I first noticed it when I was running ShiftAO5P 3.2, and though I didnt specifically think 3.2.1 would fix it, I tried that, and now the problem has come back.
The gist of the issue is that if I havent used my phone to talk to someone for some unspecified length of time, when I call someone, they cant hear me. I can hear them just fine, but they can't hear anything from my end. If I hang up, and call right back, then it all works fine. Also, it is fine if they call me - works right away without having to re-make the call.
Like I said, I did a complete reload to get to 3.2.1(full wipe, and even reformatted sd card), and since I suspected the tiamat kernel and the call recorder app I had been using under 3.2, I didnt reload those pieces and stuck with just the stock 3.2.1
Everything seemed OK for about the first week or so, but now it is doing the same thing again.
I am guessing it is some app, but I have no idea how to try to chase it down.
I have a logcat that I just dumped right after the problem happened, but dont really know what process to look for.
Any suggestions? TIA!!!
Does anyone ever have issues with the phone/dialer app?
If I try to call someone from contacts, I swipe on their name to the right and nothing happens, if I try again, I notice the contacts app has frozen OR I try to swipe again and nothing happens again. Eventually it might work after 2 or 3 goes.
Then I'll hang up after finally getting it to make the call and the phone immediately tries to make the calls I tried to make earlier... This happens fairly often but not all the time.
OR – (this happens rarely but does happen)
Phone rings, try to swipe the green answer thingo and it just bounces back to where it was, try to swipe/answer again nothing. I can't answer the call. Happened today, really pissed me off. Phone app crashed and refused to make a call after that for about a minute.
Sound familiar to anyone?
Using Android 2.3.5 Vodafone (Australia) stock unrooted.
Anyone?
Would love some help on this.
Yes I am facing the same issues as you.
A few observations:
problems exist on stock dialer app as well as third party dialer apps
It's an intermittent problem i.e. sometimes the problem shows and other times it does not
I was facing the same problem a couple months ago too, since i was running 2.3.3 so i had just upgraded to 2.3.6 and the problem had disappeared. But out of the blue it has again started now while i am running 2.3.6
Currently i am running on stock rom, cf rooted, latest modem.
Am looking for a permanent solution and will post a solution if i find one, in any case hope the official ICS release (due on the 15th) should solve the problem anyways.
Anyone else facing the same problem?
Updates
Usually clearing the cache and calvik cache does not help resolve the issue.
After posting the above post I had just created a ClockWork mod backup and Restored to the same. Dunno how but that resolved the issue, or to be exact, the issue did not surface for a couple days.
Today the issue actually became too much for me to be able to handle.
So I again cleared both cache and dalvik cache and then fixed permissions via CLockWork recovery menu.
Since then I am not facing the issue yet. Hope it works for you too.
(But this is just a preliminary observation and maybe the issue shall resurface with long term use)
p.s. really hoping that the impending ICS update will permanently fix said issue.
I bought my S4 with VRUAMDK firmware used hence no warranty
when I got it it tested fine I made calls
after rooting it just stopped making any sounds or phone calls, (I'm pretty certain I followed the rooting instructions correctly)
tried unrooting, going back to stock and rerooting and trying several ROMS I still have no sound whatsoever no headphones nothing, it does eventually detect the headphone if plugged in, even in the diagnostic menu sound doesnt work
I can browse using mobile data I can attempt a call and the other phone rings but the dialer doesnt work after placing the call the phone hangs or restarts sometimes.
everything else works I can send and receive text messages, emails, cameras work. etc
if this is a hardware issue what needs to be replaced? any idea whats the best way to get this fixed? and probable cost?
I read other threads that were similar which suggested unrooting and resetting and tried that