Related
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have the exact same issue. Very strange and rare. So the occasional reboot fixes it but annoying at times.
sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have come across the same today on the 2.05 revision. It started this afternoon, since I have had to reboot 5 times. The latest was only about an hour or so apart. When I make calls, I do not hear any sound, no ring tone, not the other person. Also adjusting the ring volume with the volume keys does not make any sounds. Even on my bluetooth headset I do not get any sound. No rings on incoming calls, no speaker phone ... absolutely nothing. This has become a huge issue an I'm going back to my 1.5 image at this point.
Actually, reading through threads about both ROMS, I'd say there are quite a few people starting to encounter this problem...has anyone with this issue gone back to 1.5 to see if it goes away then?
S
just a note, the people on the other end when making a call can't hear anything either but the call does go through. i had to use the g/f BB to call and my buddy thought it was his phone. I'm so mad because I thought this was a done deal but looks like I gotta go back to 1.5
+1 same issue on Fresh 2.0d
When it happened it affected incoming and outgoing calls, earpiece, speakerphone, microphone -- the works. Person on other end could not hear anything either. Fixed with reboot.
me and my coworker both have this issue with our heroes, he couldn't stand it and went back to fresh 1.1 and it went away
I still get the issue once a day, full reboot solves the issue.
I cant seem to pinpoint when it happens, it just happens.
it started with the first fresh 2.0 and then continued with every 2.1 i have tried
i couldn't find a post in this forum relating to a fix for this, unless someone can prove me me wrong and i hope someone does
+1 same issue on Fresh 2.0d and DCv1
Same as others, a reboot will fix it but by that point you just missed a call.
Or if the sound goes out you might miss a few calls from not being able to hear the phone ring.
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Avalaunchmods said:
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Click to expand...
Click to collapse
Thanks. You're speaking greek to me as far as the boot.img and all that but if you have an idea of what's going on I'm all ears on fixing it. If there is any sort of info we can provide just let us know.
Im here to help as well, If you need any testers I am willing to do what ever is needed! Anything to fix this problem!
Related?
10chars
http://forum.xda-developers.com/showthread.php?t=657244
Click to expand...
Click to collapse
DroidDhakan said:
Related?
10chars
Click to expand...
Click to collapse
Of course it is,its the fix(hopefully) for it
Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.
Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300
Have you tried to DISable the noise canceling feature?
No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app
I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?
BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app
just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?
Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:
the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course
change modem
Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?
avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas
I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...
I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.
I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app
Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium
I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.
Sometimes when I plug my earphones in, the music player shows it as playing, but there's no sound in the earphones. When i remove them, it works fine through the speakers. Tried using different earphones, but same result. Have to restart the phone to be able to use the earphones again.
I have been experiencing this problem since 3 days now.
Has anybody else experienced similar problems? Any solution?
I'm using stock Gingerbread on Moto Defy+.
Please ask all questions in Q&A. Thread moved there.
At first, I see only 2 options, despite trying another ROM:
1 - Try other music players.
2 - Be sure that you haven't changed any option in any Voice Search / Dialer. And if you have changed, try to reset to default options.
Lorenard said:
At first, I see only 2 options, despite trying another ROM:
1 - Try other music players.
2 - Be sure that you haven't changed any option in any Voice Search / Dialer. And if you have changed, try to reset to default options.
Click to expand...
Click to collapse
I have tried other players also. Same result.
And i haven't changed any such option recently.
neo.dcm said:
I have tried other players also. Same result.
And i haven't changed any such option recently.
Click to expand...
Click to collapse
Hmn... in tha case, there's still a lot of things to do.
If the problem is with the phone's jack, you can try to clean it with a blow or compressed air.
There's a bunch of apps, like Ringo Pro, that are known to cause some similar issues, as reported in this thread: https://forums.motorola.com/posts/6f261e8427?commentId=564506#564506
After all, if you'r not willing to root and flash other roms in your phone, you might also try bluetooth earphones.
Lorenard said:
Hmn... in tha case, there's still a lot of things to do.
If the problem is with the phone's jack, you can try to clean it with a blow or compressed air.
There's a bunch of apps, like Ringo Pro, that are known to cause some similar issues, as reported in this thread:
After all, if you'r not willing to root and flash other roms in your phone, you might also try bluetooth earphones.
Click to expand...
Click to collapse
If dust etc were the problem, it wouldnt have worked after restart.
I went through the forum in the link. I havent installed any such app recently. The post might be useful for future though, thanks for that.
Hi all,
I have a Galaxy S4 which I have recently flashed CM 10.1 onto, having used another JB custom ROM until then. I have a problem with the vibration. It seems to be working fine after every reboot, but then as I start typing messages and using other functions the intensity of each vibration seems to die a little bit more until it stops vibrating altogether (haptic, notifications, everything). A reboot will cause it to get back to normal again but the same thing seems to happen.
I can't recall if this was happening before first flashing/rooting the phone, so I'm not sure if it's a straight hardware issue. Any pointers?
Thanks
Try going back to stock via Odin and see if it's actually a hardware issue or just CM10.1. Have you tried reflashing CM10.1?
That's a strange issue.
Certain ROMs have "vibration intensity multipliers" as options, e.g. LiquidSmooth and I think ReVolt (both AOKP-based). These are helpful. That might not help you though, given that your vibration's dropping to zero (it won't matter if it's dropping from a higher level in that case).
But to rule out a hardware fault, I'd switch ROMs and see if that fixes the problem. (Because then you'd know it's software-related.)
Te3k said:
That's a strange issue.
Certain ROMs have "vibration intensity multipliers" as options, e.g. LiquidSmooth and I think ReVolt (both AOKP-based). These are helpful. That might not help you though, given that your vibration's dropping to zero (it won't matter if it's dropping from a higher level in that case).
But to rule out a hardware fault, I'd switch ROMs and see if that fixes the problem. (Because then you'd know it's software-related.)
Click to expand...
Click to collapse
emckai said:
Try going back to stock via Odin and see if it's actually a hardware issue or just CM10.1. Have you tried reflashing CM10.1?
Click to expand...
Click to collapse
I'm still new to this so it's a slow and somewhat painful process, but I just reflashed stock today and there doesn't seem to be an issue at all.
I stumbled across this thread where it appears it's a CM10.1 problem. Suggested fix is to disable haptic, reboot, enable haptic. When I get the patience to re-flash and set up my device again I'll give it a shot.
Dear xda friends,
I've been trying few AOSP rom on my N9005 always have the noise and crackling sound problem.
I tried to search but couldn't find solution to fix that.
Alan_Hill said:
Dear xda friends,
I've been trying few AOSP rom on my N9005 always have the noise and crackling sound problem.
I tried to search but couldn't find solution to fix that.
Click to expand...
Click to collapse
I have n-900. I had the same crackling sound problem coming from the bottom of my phone. I gave it to Samsung Agency they changed the speaker first. Same problem persisted after a few days.
So i gave the phone again and asked for a replacement. Thankfully, they changed the chipset. Now its fine. *Touchwood*
jakhan86 said:
I have n-900. I had the same crackling sound problem coming from the bottom of my phone. I gave it to Samsung Agency they changed the speaker first. Same problem persisted after a few days.
So i gave the phone again and asked for a replacement. Thankfully, they changed the chipset. Now its fine. *Touchwood*
Click to expand...
Click to collapse
But mine work with Samsung based rom without any issue like this one .
You tried a few AOSP roms, well ain't that cute.
But not once did you read the first posts or a few last posts of the rom thread. If you would, I'm sure you'd found at least a hint on this bug.
And do learn how to Google search !
Sent from my N9005
Had the same problem too, this issue is for all AOSP roms as I see .. but after some restart and charges he go away .. No worries to have man
Same problem. Been having it ever since I installed cm12.1. Most sounds work like they should, but certain apps only crackle. Like, my gf got a vanilla note3,and we both have the game "just get 10". To her, the sound is as it should be. To me it's horrible.
I've been using it ever since the unofficial ports, and been updating nightlies ever since. The problem still persist. If this could be fixed, it would be amazing!
I've also tried the equalizer ports of dsp mamager and audiofx, but no changes whatever I do.
Headphones, and Bluetooth headset works fine.
I too have experienced that allot. And have noticed that it occurs mostly when you use different sound drivers. Like if even on TW you flash beats audio mod or maxx audio you can hear the same crackling.
I suggest you use temasek rom. Its a solid and very stable one.
Hey thanks man, I'll do that
Edit, I've done did it and now everything works flawlessly. It's also a great rom, good battery. Thanks man.
This problem exists in all AOSP based ROMs and after some research I found the solution:
Go to settings -> apps manager -> select google app -> permissions -> disable the microphone permission.
Done
Worked on Galaxy S7 Edge