[Q] Please help in solving this interesting and strange audio problem. - Galaxy S 4 Q&A, Help & Troubleshooting

Hi Friends!
I am having a strange problem in my samsung galaxy s4 (Gt-i9500).
I was on stock 4.4.2. Unrooted. One day suddenly my Device is muted. Means no audio on music/video Player. No audio on notification. No touch sound. No screen lock sound. No sound on call. Caller can't hear me too. No sounds on headset too.
I tried reboot, reset, format, removed SD card, Flashed Stock firmware in Odin, Flashed Custom Roms but nothing worked.
Visited Samsung service centre . They tried flashing the firmware. Then said they need to change the motherbord. Because my Device is out of warranty they said it will cost me around Rs 7000/-. I don't want to spend that much because i know that this is not a hardware problem. How do i know that??
Now the intresting and strange part of the problem. Every time When i switch on my Device in morning sound works properly. Everything works including calls. There is a small lag in calling interfere. When i touch mute or Speaker phone there is a lag of 1 or 2 second in activation. Same while receiving calls. But Sounds works perfectly. For weeks . UNTIL i reboot or switch off. After reboot again same problem of no audio.
To solve this i have to switch off my Device for a whole night and switch it on in morning. Every time this works. In every ROM this works.. I wonder what is the reason behind the problem and solution.
Please help me to solve the problem Permanently .

try flashing another rom

ipois0n1 said:
try flashing another rom
Click to expand...
Click to collapse
He said that he flashed custom roms.
I don't really know what to say since it happens on different roms. That means it can't be a software problem. Unless it's cause by software unaffected by flashing other roms

You have clearly established that it is a hardware issue because you are getting consistent results in software across roms. Everyone else can state to you most highly elusive issues in roms are solved by clearing dalvik cache and factory reset and in extreme cases deleting user data from the recovery. That hasn't worked so it can't be a software issue. Your audio processor is even lagging as you say even when it is operating within its manufacturer specifications in a newly installed rom. Unless you can trace back what you could have changed unknowingly on a hardware level, trying to do it on a software level is futile, its not meant to be as complicated as your thought line makes it. Surely..... you took it to as Samsung Service Centre, unless you can prove that you ran hardware lab tests showing clearly that your individual audio hardware components aren't failing by showing that they are yielding manufacturer hardware specifications at every test, you are going round in circles.
Hardware failure occurs on 3 levels:-
1) Total instant failure with no temporary workarounds
2) Noise suppression failure (Introduction of noise)
3) Waning hardware performance.
Yours seems to fall in the 3rd option. The unfortunate bit is that the audio hardware processor is located on the larger board (motherboard) as a fused component and not on the easily replaceable flex daughter board below the speaker. Unfortunately you might end up forking out that Rs7k eventually. Samsung should have designed the phone in such a way that you don't need to replace the entire mobo for such an issue.

That's the detailed and informed explanation. I am impressed by your knowledge. Thanks for replying .

Related

HTC working to fix voice calling fault on HTC One M7 and mabye M8

Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls.
A HTC spokesperson confirmed the problem to TechRadar, with a recent HTC Service Pack downloaded from the Google Play Store the presumed (but unconfirmed) culprit.
The firm says resolving the problem, which could also be affecting One M8 users, is its number one priority and has told customers to expect the roll out in the coming days.
The statement says: “We are aware that some HTC One M7 (and possibly some M8) users have recently been experiencing audio issues making network calls on their devices.
“WiFi calling does not seem to be impacted at this time. We're working around the clock with our technical teams and partners to resolve the issue as a number one priority.
“We will provide further updates as soon as we can. For anyone experiencing this issue with your HTC One (M7 or M8), you may want to try WiFi calling, and we ask that you please contact your local Customer Care: www.htc.com/support."
Speculation suggests the Service Pack may have caused the instability, but HTC isn’t offering up that information at this stage. As the original report points out, if you haven’t downloaded the update yet, it may be wise not to do so.
jkolner said:
Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls..
Click to expand...
Click to collapse
This might explain the issues I have been experiencing since the 5.01 OTA. Call recording has failed with every SW I have tried. Sound quality during calls has crackling and is very poor.
This makes a lot of sense, in the last couple of days mine has had the same problem as was told by HTC that it was a hardware issue, but if this is the case may just hold back and wait for an update.
I've had mine recently producing no audio at either end when answering a call, a reboot seems to sort it out for a while. Hopefully this is all it is and they can sort it out fairly soon, I'm in the middle of buying my first home and trying to talk to lawyers and stuff gets a bit embarrassing when this happens.
Oh my a God.
Thought was mine only!
Sent from my HTC One using XDA Free mobile app
I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.
Pavlova said:
I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.
Click to expand...
Click to collapse
On M8 Original GPE, HTC service pack was installed with 5.01 OTA update. No choice on whether to install or not - it appeared on the list of updated apps.
Apart from sound issues (which I suspect come from HTC/Google disabling features at the Kernel level), I am now experiencing delayed touch response.
Yes, but as I remeber, it was updated also after initial startup. Last update of the Service Pack (on Sense) in Play Store was from 11th December. Anyway, on T-Mo firmware 3.29.118.9 call quality is much better. Also ringtones and notifications are more clear.
Just got a service pack update.
for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching
Andrew149 said:
Just got a service pack update.
Click to expand...
Click to collapse
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
RedBlackPellet said:
for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching
Click to expand...
Click to collapse
Can you pls give a little more details as to what specifically you uninstalled. Thanks.
Roadrunner100 said:
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
Can you pls give a little more details as to what specifically you uninstalled. Thanks.
Click to expand...
Click to collapse
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related
RedBlackPellet said:
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related
Click to expand...
Click to collapse
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1
Roadrunner100 said:
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1
Click to expand...
Click to collapse
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution
RedBlackPellet said:
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution
Click to expand...
Click to collapse
Like you I'm trying to find out what's going on. I can confirm issues with the proximity sensor. I have further issues like skype not gaining access to camera, voice call issues like loud speaker switching on by itself during a call.. etc. What's clear at the moment is that this GPE release is screwed up big time. Like you I've reset the device a few times, but noting changes. Same problems reappear.
I think that finding out more is difficult since there are no specific Forums or threads dedicated to non converted stock GPE's. So finding out more about issues specific to this version is very hard... I have two other colleagues with Original GPE's (mine is a very early device, their's purchased recently) that have the exact same issues, so I can only assume that this is not HW related, but due to Google disabling certain features and getting it badly wrong or HTC's service Pack at fault. In the office there are three other Sense M8's, which don't have any of these issues, but none of them are on Lollipop yet, so I cannot compare until they get HTC's update.
I have a OEM gpe m8, running mrjaydee82's lollipop gpe ROM. I've seen no weirdness besides memory leak.

Nexus 4 major issues with no sound at all and no youtube

Nexus 4.
Android 5.1.1
Kernel version 3.4.0-perf-gdffc258
I have had this phone for over 2 years. For last 6 months it has given some problems.
I had an issue 3 months ago where it would stall at the welcome screen for Android.
Factory reset worked on this occasion.
NOW I have major issues with
1. No sound heard. (neither speaker nor headphones)
2. Using the volume key slows the systems right down and no effect on sound (i.e. still cant hear anything)
3. Whatsap call cant be placed or received (if i try it hangs the system)
4. Normal phone calls have the same issue but I can still hear sometimes and the mic also does work but interrupted and laggy.
5. Youtube open but does not play video or audio at all.
6. Spotify can play but no music is heard
7. Screen dims out at times totally
8. After reboot it gives error "Launcher is not responding" . I use the basic version no fancy launchers.
I HAVE tried clearing the cache and resetting to factory but nothing works at all !
Is this a hardware issue or software ? Any tips how to fix it. Thanks
Possible loose connection inside the phone? Was the phone ever dropped or exposed to moisture?
audit13 said:
Possible loose connection inside the phone? Was the phone ever dropped or exposed to moisture?
Click to expand...
Click to collapse
It has been dropped but not from a great distance and also it has a good case. It can be that there was some problems with moisture given there was incessant rain recently and I might have used it for a sec or so.
Would such a problem cause even the software to be slow or hang ? (like whatsapp, calling, youtube)
What do u suggest in this case ?
Did the problems appear shortly after the drop or after slight exposure to moisture?
I suggest removing the back of the phone and check the moisture sensors and look for residue on the circuit boards.
Before doing troubleshooting on the hardware, I would try a full flash back to pure stock lollipop and KitKat, to see if that solves the problem. If that is a no-go, then it would be time to inspect the hardware.
Thanks ! Could u please point me to as to how to get it back to pure stock Is. Thanks

BIG problem, help me. Suddenly don't play any sound, nor input, nor phone calling

Hi folks, stuck in this problem for 3 days, begin to lose hope.
Problem: Saw cell didn't allow input voice , suddenly. Nor in whatsapp, nor video filming (only pics). Either phone calling is REALLY lagging, then I can't talk anyway. Everytime it says "Not succesfull", or "rec is not configurable at the moment", etc., even nothing. [translation from ita].
Neither plays any sound. Nor ringing, not alarms. Not music.
I've tried: Three different ROM. One Marshmallow, Two Lolly. Everytime DEEPLY WIPED internal (also wipe DATA). Put off external card. Tried installing google TTS, and so.
It seems an hardware problem. Seen around world some people got quite same problem, but no solutions till now.
Do you think something hardware have broken ? Some Media controller ?
What model do you have .
Have you flashed stock rom ??
did you ever find a solution to this? It sounds similar to a problem I currently have too...

Audio Crashing

I apologize if this ends up being long winded, I want to lay out all the details.
So I recently purchased (what I had believed to be) second hand Nexus 6P. It is in perfect physical condition however, no signs of ever being used. Battery is great, performance is great, speakers are great, camera amazing, and screen is perfect. However two odd things started to occur which I believe stems from the same issue. When hanging up phone calls the hanging up process would hang for a long while and either eventually hang up or the system would soft reboot. After reboot notifications are still set to priority only "call management", although it is easy to adjust and bring it out of that. However no audio/mic works at all (Play Music and YouTube give an error that they cannot play). No audio from speaker, or from headphone jack. I could however connect to a Bluetooth speaker and audio plays just fine. I then went to do a proper shutdown of the phone (using the power button menu), and when I manually booted it back up all audio works find again. I plug in headphones and start listening to music on Play Music. After a while however, playback fails and all the audio on the phone is once again dead...queue soft reboot. And repeat the whole process again. If I'm listening to headphones and I do anything to activate the microphone, audio crashes and go through the whole process again.
So I decided to make sure it was all up to date all the way to OTA 7.1.2. Once I did and I tested, the same issues above occurred over time. So then I thought maybe if I used Nexus Root Toolkit and did a full manual wipe and reinstall of 7.1.2 factory image from Google. Phone issue initially went away, but audio playback through headphones persisted and eventually the phone issue manifested itself again.
Today I decided that I do a full wipe again and try and install Pure Nexus 7.1.2, non rooted with BeanGapps and vender image (following the entire process here to a T.) I have not been able to replicate phone issues, however the audio playback and headphones issues are easily repeatable.
TL;DR - So this leaves me with a few things;
1. I can use the phone by never connecting it to external audio source perfectly fine, no problems at all.
2. Phones calls may sometimes get stuck at hanging up, and the result is a crashed audio system.
3. The only way to temporarily solve this issues is to shutdown via holding down lock button and Power-off using the menu that appears. And then manually starting the phone back up again.
So I'm not sure if this is a hardware or software issue. The fact that it persists between full wipes and reinstall of different roms makes me think it to be hardware. Although the temporarily fix of proper shutdown and manually start back up makes me think the OS/Kernal is somehow "clearing a buffer" or something in it's proper shutdown process. Which without doing leads to the audio system being completely down. Therefore on soft/dirty reboots the audio system is still down.
As an added bonus my sim card was a Micro SIM, before I opted to take the scissors to it instead of buying a nano sim. It works (so I thought), it just doesn't fit in the tray quite right. I tested recently with a proper nano sim from a different phone, and everything worked perfect. Then I swapped my franken sim back in and...it worked perfectly fine.
I did search for this issues in previous posts but all I could find was this. The issue (s)he describes is exactly the same issue as me, but his/her solution does not seemed to have worked. I am inclined to try doing a full wipe again and flashing completely stock older version though.
Any help, suggestions, etc are greatly appreciated. And thanks to the developers of Pure Nexus, it seems to be very polished and I'd love to use it daily driver.
Since you are having the issue after a clean install of stock and a clean install of Pure Nexus I don't see how it could be anything but a hardware issue. You could try to flash a custom kernel if you really think the kernel is an issue but I doubt that it will do much good. You could also try a clean flash of a different rom (I recommend Dirty Unicorns which is very smooth and stable) but again I doubt that it will do much good since you seem to have a hardware issue. You might have bad memory which is getting cleared when you reboot the phone.
I fear you may be correct. When you talk about bad memory, I don't want to misconstrud what your trying to say. Would there be a buffer for the DAC for example that is bad? Or do you mean the RAM or the flash memory itself?
It is very disappointing. This phone is perfect otherwise. I'd like another 6P, but I am concerned I then get one with battery issues.

Weird problems with nexus 6p

Hello.
My friend got a nexus 6p one year ago. One month ago he started to have problem. He was on stock rom
-First when he pressed the touch screen he heard small weird noises (hard to describe)
Then progressively :
-Speaker stopped working
-he could not play youtube video in you tube app : a weird error message (every time different) appeared. Gallery videos don't work as well
-But weirdly enough video played in the web browser including youtube videos, works, still without sound.
-He cannot make calls
-Jack plug doesn't works either, but he can use his Bluetooth headphones
We tried to install a custom rom (lineage os). We succeeded, but the above problem appeared again.
Then we flashed the factory image [url]https://developers.google.com/android/images[/URL] for nexus 6p. We also succeed but the above problem appeared again.
Thanks in advance for your help
ilininja said:
Hello.
My friend got a nexus 6p one year ago. One month ago he started to have problem. He was on stock rom
-First when he pressed the touch screen he heard small weird noises (hard to describe)
Then progressively :
-Speaker stopped working
-he could not play youtube video in you tube app : a weird error message (every time different) appeared. Gallery videos don't work as well
-But weirdly enough video played in the web browser including youtube videos, works, still without sound.
-He cannot make calls
-Jack plug doesn't works either, but he can use his Bluetooth headphones
We tried to install a custom rom (lineage os). We succeeded, but the above problem appeared again.
Then we flashed the factory image [url]https://developers.google.com/android/images[/URL] for nexus 6p. We also succeed but the above problem appeared again. Thanks in advance for your help
Click to expand...
Click to collapse
The 6P has two speakers, and they wouldn't both fail at the same time. Sounds like he's damaged the phone somehow. The audio jack and speaker output both not working seem to back this up. I've seen the headphone jack part available separately, and there are guides available to replace it. Before flagging it as a hardware issue and opening the phone up, you want to make sure you wiped the phone completely by formatting the partitions (system, userdata, cache) and use the flash-all.bat included with the full Google image. There is a remote chance it is software related, but I doubt it.
You could always flash a custom kernel, use a kernel manager app to turn off the large core cpu and see if the problems go away. If they do its related to the build problem that causes the 6P to boot loop but those particular symptoms aren't familiar. It's still worth a try if flashing the stock image doesn't fix the problem.
jhs39 said:
You could always flash a custom kernel, use a kernel manager app to turn off the large core cpu and see if the problems go away. If they do its related to the build problem that causes the 6P to boot loop but those particular symptoms aren't familiar. It's still worth a try if flashing the stock image doesn't fix the problem.
Click to expand...
Click to collapse
You mean disabling the big CPU ?
ilininja said:
You mean disabling the big CPU ?
Click to expand...
Click to collapse
Yes. You can always turn it back on but turning it off apparently fixes the permanent boot loop problem on the Nexus 6P. If the problems you are describing are related to the same build problem then turning it off might make them go away. Sometimes people's phones would start acting odd before going into the permanent bootloop. That phone could be on its way there.
this is purely a guess but the problem may be hardware related with the headphone jack. it could have a physical short somewhere. if thats the case the device may think a headphone jack is being used and wont play through speakers because its being told its plugged in. But wont play because of some physical short or an open.

Categories

Resources