does anybody have this issue? Every time I receive a phone call, and I hit answer, it immediately disconnects. I can make a phone call right back, but I can't answer calls. I flashed a new rom two days ago, and that is when it start doing it. I completely wiped, went back to stock rooted, and the issue is still here.
I have this same problem and it seemed to come about after flashing to a custom ROM as well. I have tried flashing several ROMs to see if that might fix this, but the phone still disconnects instantly when calls are answered. Im back to stock thru the Kies program now and it still disconnects right away. Tried different phone answer/call apps with no luck as well. Calling out has no problems. This is very frustrating, I barely bought the phone 2 weeks ago. Please post a solution if there is one, would appreciate that.
I have this same problem and I posted it here.
http://forum.xda-developers.com/showthread.php?t=3098358
I thought it was just on bluetooth but it happens without my bluetooth headset connected.
I wiped my phone including internal storage and flashed the debloated stock rom and I still have this problem....
The issue doesn't always happen, it happens most of the time basically intermittent.
I was using cm12 for a month and the problem didn't exist with cm12. Only with TouchWiz roms.
---------- Post added at 02:05 PM ---------- Previous post was at 01:49 PM ----------
GuitarJesus said:
does anybody have this issue? Every time I receive a phone call, and I hit answer, it immediately disconnects. I can make a phone call right back, but I can't answer calls. I flashed a new rom two days ago, and that is when it start doing it. I completely wiped, went back to stock rooted, and the issue is still here.
Click to expand...
Click to collapse
I see that you went back to rooted stock but have you tried staying unrooted?
Google Voice
I had the same issue and contacted sprint. Turns out google voice was causing the issue. Turned off google voice and has not happened again.
angler909 said:
I had the same issue and contacted sprint. Turns out google voice was causing the issue. Turned off google voice and has not happened again.
Click to expand...
Click to collapse
Thank you. That seemed to fix it.
angler909 said:
I had the same issue and contacted sprint. Turns out google voice was causing the issue. Turned off google voice and has not happened again.
Click to expand...
Click to collapse
Too many "Voices" in the kitchen, between S-Voice and Google Voice it's no wonder there's conflicts.
I call someone talk and hang up.the person gets a call and it playes my leave a message .like they called me.
Related
After 30 minutes of going through posts in this forum trying to look for a solution, and apparently I couldn't find what I was looking for, I've decided to create this post.
Something really weird started happening to my arc recently. Whenever there's an incoming call (call waiting) while I'm talking on the phone, everything gets muted immediately. I cannot hear the other party, and vice versa. Even though I answer the call waiting call, we couldn't hear each other at all. I had to reject the call waiting call in order to be "connected" with the current call again. At first I thought it was some carrier, reception issues, but it's not. The bars were full and I've tried restarting the phone, but it didn't help. I was wondering if anyone has the same issue after upgrading to 2.3.3 and how did you fix this? I didn't notice anything like this before I upgraded. Any help is appreciated!
jerrytea said:
After 30 minutes of going through posts in this forum trying to look for a solution, and apparently I couldn't find what I was looking for, I've decided to create this post.
Something really weird started happening to my arc recently. Whenever there's an incoming call (call waiting) while I'm talking on the phone, everything gets muted immediately. I cannot hear the other party, and vice versa. Even though I answer the call waiting call, we couldn't hear each other at all. I had to reject the call waiting call in order to be "connected" with the current call again. At first I thought it was some carrier, reception issues, but it's not. The bars were full and I've tried restarting the phone, but it didn't help. I was wondering if anyone has the same issue after upgrading to 2.3.3 and how did you fix this? I didn't notice anything like this before I upgraded. Any help is appreciated!
Click to expand...
Click to collapse
I have the same problem. really annoying!
AmitPeri said:
I have the same problem. really annoying!
Click to expand...
Click to collapse
are we the only 2 that has this problem?!
Don't know if it helps but I just wanted to let you guys know I don't have the problem
( open bootloader, flashed prerooted global generic )
jerrytea said:
are we the only 2 that has this problem?!
Click to expand...
Click to collapse
Do you have the Viber app installed? I saw somewhere that some phones react like this because of Viber.
Sorry I don't seem to have noticed that either and I recieved a call waiting bleep while I was on a call just yesterday
I can confirm its the Viber app, I just uninstalled it and the problem is gone!
AmitPeri said:
I can confirm its the Viber app, I just uninstalled it and the problem is gone!
Click to expand...
Click to collapse
Yes, I can confirm this as well, but the problem is fixed on the latest version of Viber. Happy with regular call and Viber now. Thanks to everyone who tried to help
After I updated to stock Froyo, my phone started muting during calls. No face pressing of buttons, and the mute button wasn't on. It just muted itself, and the only way for me to fix it was to turn speakerphone on and off. I thought rooting the phone and putting a custom ROM (Syndicate Frozen) on the phone might help, so I did just that. The problem is still on-going.
Does anyone else have this problem? Is there any solution? My Epic is my main phone and it's done this on a few very important phone calls a few times already. Before I take it into Sprint I just was curious if there's a simple, less having-to-deal-with-face-to-face-tech-support kind of way.
Thank you. I apologize if this has been answered already.
Is the phone muting your voice so that the caller can't hear you, but you can still hear the caller?
I had the exact same thing happen with my Epic and I ended up having Sprint exchange it for another phone.
Out of curiosity, what happens if you turn on speakerphone?
Ahh, yes that's exactly what happens. They can't hear me, but I hear them perfectly fine. Usually what I hear is, "Are you there? Hey, are you there?" a few times before I realized what happened, and no matter how many times I tell my mom to just stay on the line and I'll fix the problem in two seconds after it dawns on me what happened, she always hangs up in a huff.
When I turn on speakerphone they can hear me right away, then I just turn it back off and everything is fine the rest of the call. It doesn't even happen every call, which is the best part. I'll be in the middle of a 10 minute conversation and it will mute itself, then the next phone call will last 45 minutes with no problems.
Does the mute icon show it's on? Did you try backing up and simply switching roms? If there's too much trouble, odin ec05 and take it in to repair if the problem still exists.
Joel
When using odin
joells1 said:
Does the mute icon show it's on? Did you try backing up and simply switching roms? If there's too much trouble, odin ec05 and take it in to repair if the problem still exists.
Joel
Click to expand...
Click to collapse
BTW, when using ODIN start from having the phone off and connected to the computer. hit the power and number 1...
Use the instructions on the odin page
TAKE OUT THE BATTERY BEFORE STARTING
mine always got stuck unless i took the battery out.
Joel
Thank you for the tips, ya'll. I'm going to first update the ROM I'm using now (as there is an update out). If that doesn't help it's off to Sprint I go.
Thanks again.
Adorialea said:
Thank you for the tips, ya'll. I'm going to first update the ROM I'm using now (as there is an update out). If that doesn't help it's off to Sprint I go.
Thanks again.
Click to expand...
Click to collapse
when you go make sure its a corporate store they have the techs and tell them you already called customer service (dont bother calling them there gonna tell you to factory reset...........every time i have called i can hear that that most if not all are reading from a scrip) then the tech will try to get out of helping you by saying its the towers (bull sh$%) that the most popular answer you will get........ And for the bad news the phone that u will get is a referb
did you try to updat the PRL and profile?
AND FOR GOD SAKES if your rooted got back to stock 2.2 EC05
My phone did the same thing after the upgrade. It is random though. The phone mutes during calls randomly but mute button doesn't light and my face hasn't hit it. I've been trying to find out how to correct the problem, but my Epic was working fine until the upgrade.
I installed CM9 beta 0 on Sat. Working great without any issues until now...My phone rings and I answer the call. I cannot hear the other person (or know if I actually connected even though the screen says I am).
ALSO...when I call out the phone actually places 2 outgoing calls (I found this out by calling my office phone and 2 lines ring) While I am calling out my phone shows the call screen but I do not hear any ringing. Sometimes the person can answer, sometimes it just goes to voicemail.
I have only install a few apps. The only one I can think that might have something to do with this is Google Voice. BUT my phone was working just fine with all these apps for 2 days and many phone calls. I have not installed anything today.
Anyone else have this happen, and any advice? Thanks!
I am trying to learn this stuff as I go, but this is my first post...so thank you all for the help!
biznuts81 said:
I installed CM9 beta 0 on Sat. Working great without any issues until now...My phone rings and I answer the call. I cannot hear the other person (or know if I actually connected even though the screen says I am).
ALSO...when I call out the phone actually places 2 outgoing calls (I found this out by calling my office phone and 2 lines ring) While I am calling out my phone shows the call screen but I do not hear any ringing. Sometimes the person can answer, sometimes it just goes to voicemail.
I have only install a few apps. The only one I can think that might have something to do with this is Google Voice. BUT my phone was working just fine with all these apps for 2 days and many phone calls. I have not installed anything today.
Anyone else have this happen, and any advice? Thanks!
I am trying to learn this stuff as I go, but this is my first post...so thank you all for the help!
Click to expand...
Click to collapse
That's a pretty weird issue! So I am not sure if I can be that much help but have you tried to go into cwm and clear cache and dalvik. The only other thing that I can think of would be to try wiping day day reflashing the rom
Sent from my SPH-D700 using xda premium
Thanks. I uninstalled Google Voice and it went away. I wasnt big on GV anyway so didn't mind letting go of it. Haven't had the problem again. Dont know what went wrong but might have just been a quick glitch.
biz, why not update to beta1?
http://epiccm.blogspot.com/2012/03/cm9-beta1-for-epic-4g-released.html
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
try the replacement handset. I've had my G3 since it came out with no problems whatsoever.
steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
Wow, my G3 just started doing this too. I've had it for 6 months and it's just been the past week that I've been having issues. It's hit or miss, but about 90% of the time I get complaints that the other person can't hear me or that I sound very faint. It's been driving me crazy. I've figured out that I can toggle speaker mode and it fixes it. Can you try that out see if it's the same for you?
I noticed this about a week ago, interesting. Wonder if it's something on tmobile's network.
This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
---------- Post added at 09:48 AM ---------- Previous post was at 09:04 AM ----------
madmanjsm said:
This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
Click to expand...
Click to collapse
I'm now running in safe mode and a couple test calls to my Google Hangout sound fine. Don't think it's a hardware issue.
I've started to experience this too. It's really annoying. I hope it gets fixed soon. Though, I am glad to know it's not just me. I really didn't want to dig around in my apps to find the offender.
Question: Do any of you guys have the Nova Launcher Beta running? I think I started having issues around then.
Sent from my LG-D851 using Tapatalk
I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you
bryanwny said:
I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you
Click to expand...
Click to collapse
Thanks! I downgraded and installed Google App 4.1.29 here http://www.apkmirror.com/apk/google-inc/google-search/google-app-4-1-29-1706998-arm-android-apk-download/. Also disabled auto-update for Google Apps so it doesn't update to 4.2.16.87075793. I'll test it out and see what happens.
I also have had the same problem lately, just twice. A reboot fixed it
This is affecting me as well. I'm also in Los Angeles and the phone was fine until some time last week. I'm trying to the google apps downgrade now...
I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.
Lookatthemonkeys said:
I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.
Click to expand...
Click to collapse
Try downgrading the Google app. Worked fine for me.
Downgraded, seems better. Are people also recommending not to use voice activated Google now?
How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.
tippingvan said:
How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.
Click to expand...
Click to collapse
In the play store for the Google search app click the uninstall button. That will return the app to it's factory version. Then just install the version that's linked earlier in this thread. Make sure you have automatic updates turned off for the app or it will keep updating.
Sent from my LG-D851 using Tapatalk
Same thing happens to me. I had my phone for about 2 months now and sometimes people cant hear me or i sound like a transformer. i restart my phone and it fixes the problem but still does it after a couple days. I'm not rooted or anything like that. I also have a problem when I'm on a call. my volume bare goes up and down if i wanna lower and or raise it and the volume sounds the same even on speaker phone it does it too..
I had the problem turn off ok google from any screen and reboot and problem with voice calls fixed
I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.
JohnnyDanger said:
I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.
Click to expand...
Click to collapse
I was gonna do a factory reset and if that didn't work i was gonna get a replacement . Hopefully this fixed the problem. The only issue I seem to be having is. when I'm on speaker phone or have it to my ear. and when i go to adjust the volume it doesn't change it. like i see the meter go up and down but the volume stays the same. its weird
I can confirm that after enabling voice activation for google now from any screen was the culprit of Mt audio issues. I was told I sounded far away or like a robot far away. Reset my device numerous times and reinstalled all apps and made calls. Once I enabled OK google from google now the issue came back. Disabled it and BOOM it worked fine. Haven't had an issue since.
I have been having trouble with my microphone shutting off while I am on a phone call. This issue seems to happen after 5 to 10 minutes randomly. I have tried toggling the mute button and the speakerphone button, this does not seem to work. The only solution I have found is to end the call and redial. Has anyone else been experiencing this issue and does anyone have any input on solving this problem?
Thanks.
crygon said:
I have been having trouble with my microphone shutting off while I am on a phone call. This issue seems to happen after 5 to 10 minutes randomly. I have tried toggling the mute button and the speakerphone button, this does not seem to work. The only solution I have found is to end the call and redial. Has anyone else been experiencing this issue and does anyone have any input on solving this problem?
Thanks.
Click to expand...
Click to collapse
Yes actually this just happened to me twice today. Once after about 20 minutes into a call and then again 40 minutes into a call. I can hear them just fine but they can't hear me.
Are u on Project Fi?
I'm on Verizon and this has happened twice
Interesting....
This has been reported on Project Fi since April on Nexus 6, 6p, and now on Pixel
I contacted Verizon they said that it is a software issue and to expect an update. I am not sold on the waiting it out for an update, might just get a replacement.
crygon said:
I contacted Verizon they said that it is a software issue and to expect an update. I am not sold on the waiting it out for an update, might just get a replacement.
Click to expand...
Click to collapse
Not sure replacement will fix anything. Ive had this issue (and many others) on Fi for a long time. It's the first time I hear Verizon people have this as well.
I am not sure about update either, there is no fix for this since April as I said before.
I don't think it's on all calls...maybe landline only? Also not on international calls. I tend to notice this while making long 800 calls mostly, and it always cuts out at around 30 minutes
I'm having this problem randomly as well. A couple things to note:
I had to replace my Pixel 5" already due to a stuck volume down button and the muted call problem happens on the new phone as well.
Nothing solves this once the caller stops hearing you. You have to end the call and call them back and then things work just fine.
It's not related to Project Fi as I'm on a Verizon sim card and have experienced this with landline and cell calls.
I read somewhere that someone tried not optimizing all phone related apps/frameworks. I've tried this and thought it fixed it but it didn't as I just had it happen 20 minutes ago.
I'm at a loss as to why the mic cuts out in the middle of longer calls. It's never happened during quick 5-10 minute calls for me.
I have the same issue with my Pixel XL. Verizon has already replaced the phone once. The replacement phone does the same thing. It seems to happen with those who I am talking with on an iPhone. I have tried all of the above fixes and nothing works. Other than this, this is a great phone. Hopefully Google figures it out fast, I don't want to go back to a different phone.
I don't believe it has anything to do with calling or receiving calls from iPhone users. The person it most frequently cuts off with me is calling from a Samsung G7 or landline. It's gotta be a software issue. I still think it has something to do with the length of the call and the phone somehow going into doze or something. I'm not trying to remember to pull the phone away from my face every 10 minutes or so to wake up the screen if I'm on a long call to see if that "solves" it.
Just started happening to me after two weeks...
Happened 3 times (after 3 minutes on the call).... All were incoming calls from a landline...
Verizon Users
Not saying this may be a solution but I changed to Franco Kernel r5 and I have not seen this issue occur since that time. Could be coincidence or ??
Could be placebo effect but I feel I'm getting better battery life which I didn't think would be possible :good:
Update Nov 24 - it's got to be the kernel that's causing this issue. Since I went to FK r5 I've not had a single dropped call (or more precisely a muted microphone). I haven't tried flashing back to stock to make the problem reoccur but I'm pretty confident a kernel change (Franco or perhaps ElementalX) would solve this issue.
Same issue for me. On Verizon. Does seems I do have the most problems with iPhone users on AT & T service, although that is not conclusive. A replacement from Verizon did not solve the problem.
Sounds like mine. Mic started cutting out first, then the earpiece speaker next. Eventually neither would work at all. VZW shipped a replacement.
Can anyone else confirm that a kernel change fixes the microphone issues? I'm unlocked on Verizon(completely stock at the moment) and don't wanna have to exchange my phone.
Update: fk r6 kernel did not fix my microphone issue.
jguy said:
Can anyone else confirm that a kernel change fixes the microphone issues? I'm unlocked on Verizon(completely stock at the moment) and don't wanna have to exchange my phone.
Update: fk r6 kernel did not fix my microphone issue.
Click to expand...
Click to collapse
Did u try r5?
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
fyyzer said:
Not saying this may be a solution but I changed to Franco Kernel r5 and I have not seen this issue occur since that time. Could be coincidence or ??
Could be placebo effect but I feel I'm getting better battery life which I didn't think would be possible :good:
Update Nov 24 - it's got to be the kernel that's causing this issue. Since I went to FK r5 I've not had a single dropped call (or more precisely a muted microphone). I haven't tried flashing back to stock to make the problem reoccur but I'm pretty confident a kernel change (Franco or perhaps ElementalX) would solve this issue.
Click to expand...
Click to collapse
Any update on changing the kernel
junweigu said:
Did u try r5?
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
Any update on changing the kernel
Click to expand...
Click to collapse
I can't say for certain the kernel affects it one way or the other. I can say that since I've been on Franco's kernels I've had this issue pop up no more than once every 3 weeks rather than sometimes multiple times per day. Kernel swap doesn't appear to be a solution but I believe it's helped me.
I have not tried r5, but my issue has gone away. I don't think it is kernel related. I suspect it might have been inserting a wired headset into the jack may have done it for me. Whether it was hardware of software I think it made something switch. Good luck.
junweigu said:
Did u try r5?
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
Any update on changing the kernel
Click to expand...
Click to collapse
Verizon user here with same issue. It happened to me within one week of the pixel release.
The problem first occurred when stock, and has continued throughout multiple updates, mods, kernels, etc.
I'm also having this exact same issue on Verizon. Here's some observations I've made, maybe some of you can confirm or deny these?
-Seems to happen almost exclusively on non-HD calls, like to landlines, almost never happens on HD calls to other Verizon users.
-Happens with or without using bluetooth, so isn't an issue with the Pixel's microphone.
-Is getting worse, I got my pixel in November and I don't remember it happening during the first month or so. Now it's happening almost every day.
-I noticed it more after I enabled wifi calling, but it still happens when I turn wifi calling back off.
-I called google support and they want to know if it happens in safe mode. I don't really want to stay in safe mode all day waiting to see if it happens, has anyone else done this?