Randomly when I make calls or receive calls I have no sound. I can't hear them and they can't hear me. Rebooting the phone will fix the issue for a short while. I have been able to reproduce this by connecting to my cars blue tooth and making a call. The 1st call works however all calls after the first call I have no sound again. When the phone in the no sound state (Phone Call) Bluetooth media still works just no sound while in a call. The speakers work because I can play music and the mic still works because I can still record sound. This issue seams to be related to the phone app its self???
My phone is a Samsung S4 (AT&T) with Android 4.4.2 (Rooted via Towelroot) with SuperSU by chain-fire installed.
Here is some of the trouble shooting I have already done.
1. Factory Rest the Phone via Stock Recovery (Still can reproduce the issue)
2. Played around with various settings i.e. Google Now Bluetooth options. Un-paired all Bluetooth devices and then re-paired one to try (Still having same issue)
3. Cleaned out all app cache (Still having same issue)
4. Re-installed pre-installed apps that I removed once rooted.
Long story short, this one has be baffled. The only thing that fixes the issue is re-starting the phone.
Thanks in advance for any assistance
AG007
Same Problem Here, I may have figured it out:
After I rooted I used some apps to auto kill some running, supposedly non-essential apps. This caused my phone call problems, same exact issue as you're having. A reboot fixed it for me as well. I will let you know if it happens again without closing any apps.......
Related
Hello Everyone,
I'm having some odd problems that seemed to have started when I updated to CRB43. There are 2 consistant things I've noticed so far and these all happen when a headset adapter device is plugged into the phone.
1. If I'm listening to music in my car and a phone call comes in, the music stops (as it should), but there is no ring, just vibrate. When I try to unplug the adapter and answer the call, there is silence and the call goes to voicemail even though the phone appears to be in the call.
2. While listening to music, if I get any kind of notification, the sound goes dead even though the music is still playing.
In both cases I have to reboot the phone to get back to normal.
Any ideas?
Thanks,
Tim
I had the same problem.
Use Lucid's script and restore the Audio to stock.
If that doesn't work, reinstall the radio from HTC.
I finally got mine working by doing both on the same reboot, so I'm not sure which one fixed it when I was using JF's rom. Whichever, the combo of both did the trick for me.
I must have not done the radio update, because that's what worked for me, it's working good now. Thanks for the reply!
Super.
Glad it worked.
I'm not exactly sure how mine got overwritten either. But I figure it was one those causing the problems.
Now...
I've been trying the audio hack, and I simply cannot get it to work. No combination of versions work without phone calls and notifications completely stopping the audio server. Regardless of the build I choose. Luckily, I don't give up
Hi everyone,
First off, I'd like to start by wishing to everyone happy Holidays!
I have been literally searching all over the Internet for any information regarding the issue I am about to describe in detail and since no solutiuon was found, there's nothing left for me to do but ask for help, and hopefully get the right answer. That's why I want to be as specific and informative as I can.
The problem I am having is this; I recently purchased a new Jabra Motion bluetooth headset and decided to start using the voice dialing function on my Galaxy S4, since it works very well (when it works) and is really a breeze, especially while driving.
In short, the problem is that the S4 completely loses audio (other party hears nothing as well) after initiating a call, via voice dial commands through any bluetooth headset (I'll get to that). When that happens, the phone has no in-call audio whatsoever (with headset on or off, with speakerphone or earpiece on), no matter how many times I start or receive a call and nothing brings audio back, except a reboot from the i9505's power button menu. All other audio works, like videos, unlock sounds, ringtone, music, even the little chirp right before the other party's phone starts ringing and the hangup chirp can also be heard. The worst part is, that it occurs completely at random, it can happen on the 1st time I voice dial or the 10th time, for example. The problem has not shown itself, when initiating a call normally or picking up with a headset connected, before audio gets lost.
Before purchasing the Jabra Motion I've been using an earliest model Jawbone Icon and had never even tried the voice dialing feature on any previous phones or the S4. After encountering this problem I tried to test whether or not it would happen when using that headset, the result was yes, so it is safe to say it will happen when using any bluetooth headset, with the same randomness.
This is what both headsets launch on the phone, when attempting to voice dial:
View attachment 2474439
The phone itself is a completely stock and un-rooted 16GB Galaxy S4 i9505, running the latest available Jelly Bean 4.3, build: XXUEMJ7.
The headsets are always connected to 2 devices simultaneously (in case that might shed some light)
What I've tried so far (no difference made, at all):
- Toggled bluetooth off and on
- Tried unpairing and re-pairing both headsets on both phones, or only on i9505
- Tried factory resetting both headsets
- Tried to toggle, while in call, between speakerphone, earpiece, headset, turning off headset and all possible combinations
- Removed Jabra companion app and services app, then reinstalled, then tried without the apps installed.
- Cleared cache from both Jabra apps.
- Cleared cache from system apps such as dialer, bluetooth and Google Search.
- Contacted support of both Samsung and Jabra (huge waste of time)
Sorry for the very long post, but I want to be clear and comprehensive as possible. Any help would be highly appreciated.
Please no factory reset suggestions, I am aware of that possibility, but do not want to go through all the trouble to set up tons of apps and stuff again.
Thanks in advance to anyone willing to help!
Anyone?
Please?
Hello,
I have a galaxy S4 (canadian version) and have only been having troubles with it within the last couple days. I do develop so I'm not new when it comes to phones but this issue has me at a lose.
Problem:
When I make or receive a phone call there is absolutely no audio on my end, I cannot hear the dial tones or the other person's voice. The only thing I can here is the call connect and disconnect beeps. The person on the other end hears a very loud buzzing/white noise. This noise becomes intermittent slightly when I speak into the problematic device.
It is only when making/receiving a phone call that the audio does not work. All speakers are functioning in all other apps (music player/skype etc.) the mic is also working without a problem when used for other apps.
When the problem first started I was running 4.2.2 firmware. I was making a phone call when the audio cut out unexpectedly having assumed it was a dropped call I made an other attempt but there was no sound at all. I restarted the device and that very briefly fixed the issue. However every time since restarting the phone has done nothing.
WiFi is working fine as well.
Attempts at Solutions:
Restarting the device (with headphone connected and without)
Factory resetting the device (with headphone connected and without)
Flashing updated (and older) stock firmware on to the device
Flashing custom ROMs on to the device
Dialer apps
SoundAbout app
Making calls with headphone connected / speaker phone
All settings have been checked to ensure in call volume has not been disabled
About Device:Currently running: Gummy version M1.02-25-14-NIGHTLY (Please note that when the phone first started messing up I was running stock 4.2.2 and there was no audio during a call between either phone. The Gummy ROM has made some improvement)
Current android version: 4.4.2
Phone Model #: SGH-I337M (Canadian S4)
Baseband version: I337MVLUAMDJ
Any help is appreciated!
Thank-you
I'm having a similar issue with my ATT SGS4. It started happening randomly...the person on the other end hears beeps and I hear nothing. Speaker/headset with mic don't work either. Only thing that works is Bluetooth oddly enough...but as soon as I switch to speaker, it goes back to not working.
A reboot fixes it temporarily, but then it comes back randomly..either right away or later on in the day.
If Bluetooth works fine for voice calls then I would guess that it's a physical hardware issue. Perhaps the ADC / DAC for onboard mic and headset is malfunctioning?
For Bluetooth I would also guess that A to D conversion happens within the Bluetooth chip which seems to be working fine.
It would be nice to see a schematic.
Edit: I found a block diagram of the circuit. and this link https://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947
So it looks like the audio codec goes straight into the modem but the Bluetooth goes through the Snapdragon CPU before going to the modem. Based on this my original assumption seems to be correct and your mic codec is malfunctioning or there is a physical connection problem.
Hope this helps in any way.
Does this explain why a restart fixes the issue though? If it were solely a connection/hardware issue, a restart wouldn't do crap (unless it re-initializes the circuit and then something causes it to go derp again).
saj222 said:
If Bluetooth works fine for voice calls then I would guess that it's a physical hardware issue. Perhaps the ADC / DAC for onboard mic and headset is malfunctioning?
For Bluetooth I would also guess that A to D conversion happens within the Bluetooth chip which seems to be working fine.
It would be nice to see a schematic.
Edit: I found a block diagram of the circuit. and this link https://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947
So it looks like the audio codec goes straight into the modem but the Bluetooth goes through the Snapdragon CPU before going to the modem. Based on this my original assumption seems to be correct and your mic codec is malfunctioning or there is a physical connection problem.
Hope this helps in any way.
Click to expand...
Click to collapse
Same thing happened to me, the incall audio chip as gone bad. I had to buy a S4 with a cracked screen off craigslist and swap mother boards and the phone works perfectly now.
SOLUTION: Samsung Galaxy S4 I337 no audio sound during phone call.
SOLUTION: Samsung Galaxy S4 I337 no audio sound during phone call.
For me it was a bad SIM Card Reader or Module IF. But it could be a bad SIM card so try a new SIM before doing this repair or at least take it out and in.
My Service Repair Statement said it replaced two things:
Part Number Description
GH59-13279A Unit-SIM SD SOCKET; SGH-I377, 10-0013-0278
GH59-13111A MODULE-IF SUB FPCB(SGH-I337);SGH-I337,10
Called 800-726-7864 told them what the symptoms were and that the support line said it was the SIM Card Reader and they gave me a quote of $70.36 and seemed confident that the phone would be fixed. Sent to Samsung Repair Facility in Texas, total cost $70.36, and was without it for 9 days. It’s been working for 2 weeks now with no problems.
First I took it to an AT&T Service Center and all they really did was try a new SIM Card, next called Samsung Service 888-987-4357 and went thru a series of tests and they said it was a bad SIM card reader and gave me the repair center number.
Symptoms:
No audio / sound during a phone call on either side (caller or receiver)
Call connects everything is working, just no sound.
Sound for all other functions and apps works (music, voice recording, video audio).
You can tell it is going to happen when you make a call and you don’t hear any ringing just a click sound then nothing. If you hear ringing then the call will work.
Rebooting usual works for a call or two. Messing with some settings may get it to work for a period of time. But for me none of any of the other suggested fixes worked except rebooting and turning airplane mode on and off but it only fixed it for awhile.
I have used the phone for 1.5 years and never had a single hardware problem, didn’t have it heavily loaded (RAM or Memory). It just started one day out of the blue and drove me crazy.
jade77angel said:
Hello,
I have a galaxy S4 (canadian version) and have only been having troubles with it within the last couple days. I do develop so I'm not new when it comes to phones but this issue has me at a lose.
Problem:
When I make or receive a phone call there is absolutely no audio on my end, I cannot hear the dial tones or the other person's voice. The only thing I can here is the call connect and disconnect beeps. The person on the other end hears a very loud buzzing/white noise. This noise becomes intermittent slightly when I speak into the problematic device.
It is only when making/receiving a phone call that the audio does not work. All speakers are functioning in all other apps (music player/skype etc.) the mic is also working without a problem when used for other apps.
When the problem first started I was running 4.2.2 firmware. I was making a phone call when the audio cut out unexpectedly having assumed it was a dropped call I made an other attempt but there was no sound at all. I restarted the device and that very briefly fixed the issue. However every time since restarting the phone has done nothing.
WiFi is working fine as well.
Attempts at Solutions:
Restarting the device (with headphone connected and without)
Factory resetting the device (with headphone connected and without)
Flashing updated (and older) stock firmware on to the device
Flashing custom ROMs on to the device
Dialer apps
SoundAbout app
Making calls with headphone connected / speaker phone
All settings have been checked to ensure in call volume has not been disabled
About Device:Currently running: Gummy version M1.02-25-14-NIGHTLY (Please note that when the phone first started messing up I was running stock 4.2.2 and there was no audio during a call between either phone. The Gummy ROM has made some improvement)
Current android version: 4.4.2
Phone Model #: SGH-I337M (Canadian S4)
Baseband version: I337MVLUAMDJ
Any help is appreciated!
Thank-you
Click to expand...
Click to collapse
i have the same issue no audio in calls and i rehot the audio codec ic wcd9310 and that worked completely
Hi,
My Safestrap rooted phone started having call audio problems soon or immediately after upgrading from 4.4.2 to 4.4.4 (I337UCUFNJ4 ATT stock rooted ROM). I also installed Wanam Xposed and DroidWall and a few other utilities at the time. I since disabled Wanam Xposed in the framework. I finally figured out how to duplicate the problem reliably:
1. Reboot phone to start from known state. NOTE: failure even happens in Safe Mode!
2. Connect to bluetooth car stereo or Motorola earpiece (Media and Phone)
3. Make a call and everything works normally. Hang up.
4. Make or receive a second call. There is no audio in either direction. However, if I press a number key, I can hear a beep over the bluetooth and the other end hears a tone.
• I have not been able to find any way to get the Phone audio to start working again without rebooting. (ex: I turn bluetooth off and there is still no Phone audio.)
• Turning cellular radio off/on doesn't bring audio back.
• Media audio apps like Music player continue to work.
• It appears I can make calls all day long without bluetooth.
• "OK Google" detection often quits working, but in my short test above it seems to keep working even though Phone audio is not. I'm not 100% sure this is related.
Anybody know what's going on or have debugging suggestions?
Nevermind for now
I bricked my phone trying to restore a Safestrap backup, so for now I've reverted back to 4.4.2. My battery life was horrible in 4.4.4 anyway.
I had the same problem. Go to Google app , menu, settings, voice, ok google detection, turn off from any screen.
Hello gals and guys, you are my last hope.
I have a Galyxy S7 Edge G935F bought in Germany with no sim lock, i got it with G935FXXU1APAW, updated to G395FXXU1APC8. Yesterday i rooted it with CF-Auto-Root-hero2lte-hero2ltexx-smg935f based on XXU1APBF. I still have stock recovery.
The Problem:
Sometimes, while sleeping, the phone disables all sound.
This happens mostly while recharging, but it happened also while simply sleeping and not recharging. It is not reliably reproducable, sometimes the phone works for 2 or 3 days without the error occurring. Which makes the error very hard to find of course.
Sound off means: No media output is working (games, video, music), notifications are not sounding only vibrate, the phone doesn't ring when someone calls, just vibrates. No calls and notifications means, this is very severe.
When i plug in earphones or headphones, there is also no sound on the headphones. Putting in and pulling out the headphones does not reactivate the sound, so it seems not to be a problem with the headphone jack. The jack is very loose, though, doesnt hold the headphones strongly; but thats another problem.
The sound can be reactivated by the following:
- rebooting
- calling someone (i used to call my provider) or getting called (the first call gets lost, but when i get a second call, it works again)
- i installed an app called SoundAbout, which lets me route the sound to different outputs. I must first route media output to "earpiece" (the small loudspeaker you hold on your ear during calls) and then route the media back to "Speaker". Only this combination reactivates the sound again. Just activating "Speaker" or any other combination like for example first "Wired Phones" and then "Speaker" does not work. It must be "earpiece" and then "Speaker".
What i tried, without success:
- deleted all bluetooth devices
- disabled bluetooth
- enabled "prevent USB audio routing" in dev options
- uninstalled all kinds of apps having to do with sound or lockscreen
- played with all kinds of settings having to do with sound or lockscreen
I searched everywhere. A call to Samsung was not very helpful either. I might have to try a factory reset after all, but even if its good at factory, i still won't know the culprit.
But since the problem can be solved via software, i suspect it is software related or is at least diagnoseable via software.
Of course, it would be insanely awesome when someone could just present me the solution, but i would do all the debugging myself, if i only could.
I am a developer myself, but only on windows. My experiences on linux don't go much further than doing an "ls -la" on commandline and i am a total noob on android. I will not be afraid of using a terminal or adb, as long as i am guided a bit.
I hope, somebody can point me out how to diagnose and this thing.
Can one diagnose the current state of audio routing ? Can i manipulate it via commandline ? Are there other relevant components which i need to query ?
Could i write a script that pulls those queries every minute or so ?
And finally, if the wrong settings are found, are there log files which can point out who messed with those settings. Which apps would you recommend for those actions ?
Thanks to everyone in advance ...
Correction
just getting called doesn't fix anything. Only when i accept the call it gets fixed and then the next call rings again, of course. So this means, while the bug is active, i miss all calls.