Super weird....
All of a sudden, I'll be sitting having a conversation and the person on the other line will not be able to hear me. I can hear them just fine. I don't hear any beeps, clicks...Nothing that would suggest that I'm doing something wrong. Switching to speaker doesn't help, neither does switching to my bluetooth headset. I am rooted, but other than that completely stock. It's been happening for a while, but now it seems to be happening more frequently on calls that last more than a few minutes.
I am running the latest version of Android with the latest update. I rooted using the NRT and have never had any issues with doing that. Before I wipe completely, just wondering if I shouldn't waste my time before just getting a replacement. I am using Google Fi.
i had that problem. had to reboot and call back. think a clean wipe fixed it. good luck
Related
I've got the Samsung Captivate not even 30 days used and just yesterday the sound for calls stopped working completely. when I make or receive a call I can't hear the other person and they can't hear me and there is no dial tone during the calling process. The speakers work fine, the microphone works fine and the speakerphone speaker all work fine I have no idea whats causing this. If anyone, anyone at all, could help me figure this out. I've tried resetting the phone as well as hard reset. I've messed with all the settings and am running everything stock except that the phone is rooted which was done 2 weeks ago so obviously not the problem. I've googled this for 2 hours and looked everywhere and am getting sick and tired of this. Please if anyone can help me I would be more appreciative than you could imagine. Thanks.
It's difficult to say what exactly is causing your loss of sound with only phone calls. I suppose it could be a number of things. I read the software update AT&T is pushing out this week is fixing some issues such as that; however, from just looking at the forums people are having major trouble with that update. The easiest fix I can think of is to turn up the voice call volume. During you next phone call use the volume rocker to turn it up. It may have somehow been turned all the way down. I hope that helps.
Yea i tried the volume rocker, I am just going to return it to the store since it's still in the first 30 days. I can't figure out what the heck it is, probably just a defect :-/
I tried unrooting it, reseting to factory defaults, and still the same problem. The speakers work fine for music, the phone is in amazing condition and everything is fine, it's just the darn voice calls, incoming and outgoing just don't work, the other person gets the call and it registers but no sound comes out. Just wondering if anyone else has encountered this before I go back to the at&t store, it's quite far from where I live and living on campus makes it a bit hard to get there.
Ebicoustic said:
I've got the Samsung Captivate not even 30 days used and just yesterday the sound for calls stopped working completely. when I make or receive a call I can't hear the other person and they can't hear me and there is no dial tone during the calling process. The speakers work fine, the microphone works fine and the speakerphone speaker all work fine I have no idea whats causing this. If anyone, anyone at all, could help me figure this out. I've tried resetting the phone as well as hard reset. I've messed with all the settings and am running everything stock except that the phone is rooted which was done 2 weeks ago so obviously not the problem. I've googled this for 2 hours and looked everywhere and am getting sick and tired of this. Please if anyone can help me I would be more appreciative than you could imagine. Thanks.
Click to expand...
Click to collapse
Well, I just got the same problem too. I was unable to listen anything on voice call and the other person can't hear anything too but the call is connected. I noticed that I could make phone call and hear the voice call but as long as the call ends, I can't hear other person if I make another call again. Please help. Thanks!
I have a rooted Captivate running 2.2 stock. It is also unlocked and I am currently using the phone in the UK with a pay as you go sim card from Orange. I therefore updated to 2.2 through Kies Mini. All was well.
Then all of a sudden, I would make or get a call, and could hear nothing. Not even the ringing as it was connecting to them. And on the other end of the line, they couldn't hear me either. It is as if the Captivate was connecting the call, but the rest of it'd hardware (mic and speaker) was turned off.
This doesn't always happen, probably 1 out of every 2 calls. I've learned that by restarting the phone I can normally make a working call. However, sometimes, all I will hear is muffled static, as if the sound coming from the other person was all distorted. I will hang up and call back to no sound whatsoever.
I'm really not sure what the problem is, it's very odd. Everything else functions as it should.
Any suggestions? Many thanks in advance!
Try going back to stock and starting over? It sounds like it is something with the software since it was working before the update.
Sent from my Nexus One using XDA Premium App
Hello fellas,
I just installed ICS from this link
The sound works fine when playing music or notifications or whatever I do.
But when I'm making or receiving a call, my sound doesnt work. My phone doesnt ring or hear it ring when making a call and nor can they hear me at all.
The only way I can make a phone call is through bluetooth which makes me think that the speaker on the phone isnt configured correctly.
If the ROM is the issue which rom do you recommend for my DROID 3?
Thanks for your help!
This is known issue people are experience with CM9, Gummy, and AOKP. MotoBlur + Android 4.0.4 is based of AOKP inheriting its issues. Usually a restart or two fixes the issue, but it is somewhat random. I believe the issue involves bluetooth but I guess no one really knows. I heard toggling bluetooth sometimes fixes it as well.
However you say it doesn't even ring, I have never had it not ring. But have experienced the rest.
Tried that
I've tried restarting several times, doing it again as I type.
When I've also tried to toggle bluetooth off during a call but it didnt work.
Should I reinstall the ROM?
Ok so I deleted all data and cache.
Re-installed the ROM again and it turns out that bluetooth is messing with my in-call sound. My phone rings now (by default there was no ringtone selected) but when I toggle bluetooth on I cannot hear anyone or anyone hear me.
Band aid: Keep bluetooth turned off until it gets fixed.
Thanks for your help Senate9690.
Is there a different rom out there for Droid 3?
About that band-aid
I run into a the no sound on calls as well. I'm running ICS and have always left the Bluetooth off. For me it seems to happen occasionally after I interrupt music/audio playback by removing the wired headphones from the jack or incoming call.
Just flushing the cache and rebooting letting the cache rebuild seems to fix it without the need to a re flash or factory reset. It is good to hear I'm not the only one experiencing the issue.
I ran into that issue with cm9 (selfkang) as well. Usually just toggling bluetooth off did the trick, and when it didn't, rebooting always worked. The sound issues were only in-call related, and notifications/ringtones worked just fine. I switched to Axiom and aside from the know in-call issues, toggling bt off works perfectly without rebooting.
In my opinion, Axiom is an excellent rom. My only drawback is the amount of battery sucked dry when the screen is on/keyboard out, however under very minimal use it has lasted well into the next day. Hash's original cm9 has prevailed as the battery king in my ICS D3 testing, but Axiom has made me a happy camper. I didn't spend much time with Gummy or the original AOKP though. That's the beauty in rom choices; different strokes for different folks
Sent from my XT862 using XDA
magedassad said:
Hello fellas,
I just installed ICS from this link
The sound works fine when playing music or notifications or whatever I do.
But when I'm making or receiving a call, my sound doesnt work. My phone doesnt ring or hear it ring when making a call and nor can they hear me at all.
The only way I can make a phone call is through bluetooth which makes me think that the speaker on the phone isnt configured correctly.
If the ROM is the issue which rom do you recommend for my DROID 3?
Thanks for your help!
Click to expand...
Click to collapse
A lot of Android phones are having this issue. Try this app and see if it works. The Pro version lets you route sound during phone calls too!
http://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix
Bluetooth Share?
Hi,
This is my first post, but I have encountered an issue similar to this before. I work for a company that makes Bluetooth headsets, primarily for truckers, and this is a fairly often related experience. I would describe it as "dead air" on a phone call. Often, if the headset supports it, the A2DP stream will be fine. I don't know why, or where we found this from, but we have found that often if a user goes into their application settings, to "All" apps, there will be an app there titled "Bluetooth Share". Sometimes there is more than one, but only one with show an amount of data. Going into this, clearing that data, then restarting the phone has been reported to help resolve this issue.
Try it, and see what happens. Not just Motorola phones do this either, but it seems to be associated with Android 4.0.x and up.
Thanks,
Alex.
I belive this rom has a bug where the speaker/earpiece doesn't work if Bluetooth is on.
Sent from my XT860 using xda premium
Make sure bluetooth is off
my Gnote 3 is for my business and everything else....it's my only device. being self-employed, i NEED to be able to make and take sales/service calls. sometimes, like today, i will receive a call and no sound comes through or goes out. i then call them back and same thing, UNLESS, i turn on the speaker phone. then i hear everything and they can hear me. as a last resort, i've backed everything up to the "CM Backup" app in the Playstore and i'm ready to take this un-rooted phone back to it's stock state.
are there any other things i can try before going back to stock? i've installed CCleaner and run that, just in case....but it hasn't changed anything.
thanks for ANY ideas
bump
I have a recurring problem on my new Pixel 5, running on T-Mobile (but usually on wifi calling), running released OTA Android no mods or beta.
When I call out all works.
When an inbound call is received, when I answer normally (expecting to have audio in my ear on the handset speaker) I get silence. Not low volume, silence. The calling party hears me.
I can then switch to either a headset (USB) or the speakerphone and it works fine.
This is frequent but intermittent -- it does not happen every single call, but I cannot see a pattern.
Outbound calls work fine. It's not a broken speaker, it's a software issue.
Is anyone having similar issues? All the searching I do end up with broken speakers and similar, or no audio at all. This is specific to the handset only.
Any ideas?
Linwood
PS. I call it new, but this has gone on for about 3 months, so has persisted against the last 2 (at least) OTA updates.
My sister recently got a Pixel 5 and has had this issue. I also have a Pixel 5 and have not had this issue. We're both on t-mobile. Did this ever resolve? I advised her to switch to the esim, in case it was her sim card. Not sure if she's done it yet. Are you using a regular sim?
Actually I made progress.
First, it got worse, and I had no earpiece audio at all.
Then I called Google, planning a repair or see what they had, they had me put it in safe mode. It started working.
So I was then going to try one application after another to see which 3rd party app was breaking it and.... it never failed again.
So I have no idea. I have hardly any apps on the phone, certainly few that do audio. But in theory if it worked with safe mode but not without (and it would not work without even after a reboot), then it should have been a 3rd party app that did it. However, I've been out of safe mode for 3 weeks, did not uninstall anything, and it still works.
So... no idea. Some software glitch somewhere. Try safe mode.
Linwood.Ferguson said:
Actually I made progress.
First, it got worse, and I had no earpiece audio at all.
Then I called Google, planning a repair or see what they had, they had me put it in safe mode. It started working.
So I was then going to try one application after another to see which 3rd party app was breaking it and.... it never failed again.
So I have no idea. I have hardly any apps on the phone, certainly few that do audio. But in theory if it worked with safe mode but not without (and it would not work without even after a reboot), then it should have been a 3rd party app that did it. However, I've been out of safe mode for 3 weeks, did not uninstall anything, and it still works.
So... no idea. Some software glitch somewhere. Try safe mode.
Click to expand...
Click to collapse
Thanks! I'll let my sister know.