Let's try to narrow this down...
If you have the issue, write down if it's dependent upon anything.
Does disabling "touch sounds" fix it?
How about disabling noise cancellation?
If you blast some quick bursts of compressed air at it, does it fix it?
If you mute all the volumes, does it help/fix it?
Could you freeze the audio controller app (don't recall the name atm) in system/app?
Continue discussion in this thread
http://forum.xda-developers.com/showthread.php?t=1996174
Closed
Related
does anyone know how to turn up the volume on the mic for the diamond? sometimes people can here me and sometimes they dont can it be raised via reg edits, or is this a common problem? where is the mic anyways
edit seen another thread about the 3 second lag please close
After updating to Froyo, my phone has no sound when playing media files. It is also without system sounds. Any ideas as to what's caused this and how to fix it?
EDIT: So when I have the headphones in, it plays through the speakers. Wtf?
http://forum.xda-developers.com/showthread.php?t=912932
i have a no sound issue as well, newter55 gave me the fix of taking the back cover off and gently pressing down the speaker.
Maybe this will solve your issues as well
did you ever get a fix to this... mine is doing the same
Same issue here with the Samsung/AT&T release of Froyo for Captivate. If I plug in headphones and then disconnect, that fixes the issue.
[edit - RESOLVED!]
I think I may have resolved this issue, hopefully will help others. I use an app ("Profile") to set ring tones and notifications for certain times. In Froyo, there is a new item in the settings menu (Settings-->Sound), top item = "Silent Mode" (at least I think it's new, I don't remember seeing it in 2.1, and definitely did not have this problem in 2.1). I had checked this box, and what I think happened is when my Profile app was either not running or had reverted to system settings, my phone then defaulted to the Froyo silent mode setting.
Might want to check this out instead of the somewhat dubious "remove back cover and press around the speaker" advice I saw when trying to resolve the problem.
froya no sound FIXED
i got this to work for me using the sony erricson x1 go into the settings menu and select sounds in the volume menu , i noticed after installing the latest froyo update my media volume was muted , after increasing media volume all is well
Possibly fatal phone situation here...
My Captivate has ceased to produce sound from the SPEAKER. No ring sound is delivered. No text notifications are heard. Selecting 'speaker' during a call leaves you hearing nothing out the speaker from the other person.
Vibrate still occurs on ring or txt notify.
I have checked all settings. Not on silent mode. Volume is at max, ringtones/notification tones are selected, etc. Checked multiple times...it is not a mistaken setting.
Running Cognition ROM 4.5.3. But my question for here is...is this most likely a hardware failure or something in the OS? And is there any way to tell without reloading the ROM as an attempt to fix, and having to do all the restoring of things due to that?
Thanks.
Further examination has shown that the speaker actually is producing the sound, but at a VERY, VERY, VEry low level even though vol setting is max in all cases. I have to put it up right next to my ear to hear it.
Also, I re-flashed the ROM (losing all my screen icons-ugh) and that did not solve the issue.
Search for both of these:
Captivate speaker problems
Captivate Speaker fix
Many people have had the same exact problem you reported. There are short term and long term fixes that you can do by yourself.
wwcjr91 said:
Search for both of these:
Captivate speaker problems
Captivate Speaker fix
Many people have had the same exact problem you reported. There are short term and long term fixes that you can do by yourself.
Click to expand...
Click to collapse
OK, thanks. will do that.
LATER: Excellent information you gave. The "press on the speaker" has returned the sound. Many said that did not hold as a permanent fix. The internal dismantle to reseat the speaker cable/connector I wil not undertake just yet--quite an involved process--but it is nce to know that alternative is there. This is the thread that set me in the right direction...
http://forum.xda-developers.com/showthread.php?t=778583
I just whacked mine on the table, taught it good. Hasn't tried to pull that B.S. ever since!
Sent from my SGH-T989 using xda premium
If you look at the thread I started called something like "I screwed up a speaker connection" you'll see what my long term fix was. You'll also see what happens when you're not careful.
It does take a lot of disassembly though. I would say try too see if loosening and tightening the screw helps first.
@SGA: I've given my captivate thumpings a plenty to get the speaker back.. but it's a stubborn little bugger and usually reoffends. I may have to take off my belt.
I am experiencing the intensely annoying sound cut out bug. This appears to occur under the following circumstances
1. Headphones plugged in only (not speakers or blue tooth)
2. The phone volume is fairly low 1-3
3. Music / Video is playing and there is a quiet passage e.g. music fading out, whispering in a film, sharp drop in volume of a song
The effect is that rather than playing the sound the sound completely cuts out.
My current suspicion is that it is something like a headphone amplifier power saving measure. Essentially cutting off the sound amplification if the system believes just white noise / hiss is coming through the headphones.
I have tons of music that triggers this issue (only permanently up tempo music such as dance and most pop do not trigger this issue), I have tested in Cyanogen, PA & SlimBean. Others have reported this issue in Stock ICS.
Does anyone know if the current Stock Samsung has this issue or not, before I attempt to get support from Samsung who presumably have done all their audio testing with Gungam Style and therefore have managed to miss this massive issue?
Been asking for a fix for this issue for ages, I'm either being ignored or nobody has a fix, thus can't be fixed.
Sent from my GT-N7000 using xda app-developers app
Sadly there's no real solution to this annoying 'noise gate' problem, which I've noticed since ICS on every Stock or Custom Rom that I have tried on the N7000.
The issue is also discussed here: http://code.google.com/p/android/issues/detail?id=35861
For now, you only have two workaround options:
1. Get a pair of headphones with inline analog volume control. Crank up the volume on your device and lower it within the headphones.
2. Program a Tasker profile to play an inaudible sound that keeps the noise gate open (http://forum.xda-developers.com/showpost.php?p=35047527&postcount=25)
I've used option 2 before, but decided a few weeks ago to switch to 1 (with the Sennheiser CX 400-II).
Also I've noticed that the problem does not occur when streaming media audio via Bluetooth.
This is good advice, I have an inline seinheisser controls somewhere
Sent from my GT-N7000 using xda app-developers app
Audio dropout
Tesmond said:
I am experiencing the intensely annoying sound cut out bug. This appears to occur under the following circumstances
1. Headphones plugged in only (not speakers or blue tooth)
2. The phone volume is fairly low 1-3
3. Music / Video is playing and there is a quiet passage e.g. music fading out, whispering in a film, sharp drop in volume of a song
The effect is that rather than playing the sound the sound completely cuts out.
My current suspicion is that it is something like a headphone amplifier power saving measure. Essentially cutting off the sound amplification if the system believes just white noise / hiss is coming through the headphones.
I have tons of music that triggers this issue (only permanently up tempo music such as dance and most pop do not trigger this issue), I have tested in Cyanogen, PA & SlimBean. Others have reported this issue in Stock ICS.
Does anyone know if the current Stock Samsung has this issue or not, before I attempt to get support from Samsung who presumably have done all their audio testing with Gungam Style and therefore have managed to miss this massive issue?
Click to expand...
Click to collapse
Hi - I have this problem too and so do many others.
To my ears, it sounds like there is a noise gate being used on the headphone output to mask off system noise at low levels. Noise gates will close when audio drops below a certain threshold and you can use them to eliminate background noise during periods of silence in music. However, in this instance, it shuts down during quiet passages - especially when listening to classical tracks with a wide dynamic range.
IF it is a noise gate, it is likely to be implemented in the hardware (doing it in firmware wouldn't mask noise generated by the phones circuitry - which is he whole point). Consequently, there might not be anything that can be done to resolve the problem. However, it is possible that the phones firmware configures the audio chip during boot-up. This being the case, an industrious programmer might be able to do a few tweaks and disable or modify the behaviour of the gate. I hope so because all my music is on my Galaxy Note and it is painful to listen to at times!
That's the real reason I am here: is there anyone on this forum who knows enough to be able to write a fix for this as it appears that Samsung aren't listening? Some people report this problem on the Note 2 as well.
A
Ahkatootin said:
Hi - I have this problem too and so do many others.
-snip -
Some people report this problem on the Note 2 as well.
A
Click to expand...
Click to collapse
Damn it -- sorry to hear that about the Note 2, as I was thinking of upgrading to that. Hopefully the Note 3 will have it fixed, or I just might have to go to the S4
Yes, this bugs me immensely -- it affects music with soft passages (classical) at any volume level, and of course is irritating when listening to music at night. What I'd like to do is to find or make a headset or cord that supports the microphone and includes an analog volume control.
My N7000 has also this problem with every kernel and rom I tried. With Android 2.3.6 and 4.0 it was only happening with the videos, but after 4.1, it happens with the music too. So I think it can be fixed by software (I mean actually fixed, not the inaudible sound solution).
It's very annoying, I bought the note fot its big screen, to watch videos and now I can't do it because the sound sucks. Also I can't lisent to music anymore in the night...
Solution for annoying noise suppression!
This seems to be the solution:
Start 'phone', go into settings, and disable 'noise suppression'!
Seems to be working...
There is a patch that fixes the problem for my N7000 with OmniROM:
github.com gustavoss android_kernel_samsung_smdk4412 commit 3019675d57c4046c30f82d04ce41913150df0d6e
(Sorry for the distorted link, as a new user I am not allowed to post links yet...)
The question is: How to get it into CM, OmniROM, and co.?
Also see:
jira.omnirom.org browse OMNI-561 ("Sound cuts off at low volume playback".
Kind regards
Clackwell
I was wondering if anyone else is noticing this:
Initial volume for ringtones, alarms, and notifications is very low and with sufficient repetition will eventually achieve its set volume.
This doesn't appear to be the case with music, video or any other 'in app' volume, which is working as expected.
Thanks for any responses.
Should be a setting for the volume to start low, then increase or disable that feature.
Hope they didn't take it out with lollipop.
Mine is like that too and I haven't found any settings to change it. Maybe it has something to do with the two speakers and its a safety feature.
Yep, appears to be a safety implementation. Still want to disable it. To the internet!
https://plus.google.com/117543140075851581295/posts/Zfp3tSp5Q7u
I have noticed this too.
dleonard1122 said:
I have noticed this too.
Click to expand...
Click to collapse
I am having this problem as well. I am surprised more people have not reported it.
This was driving me crazy. So I am not alone