Microphone issues- cutting out while in call. - Google Pixel XL Questions & Answers

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?

Related

[Q] [SOLVED] Galaxy Nexus speakerphone mode

I dropped my phones while skiing and some snow must have got in because now, when making or receiving calls, I can not hear the other side and they can't hear me unless I use speakerphone.
No media sounds play any more, however the phone notifications and alarm still work. I understand that perhaps the media speaker has broken but why is the microphone still working only in speakerphone mode?
Is there an independent microphone/speaker set for speakerphone?
There is nothing else wrong with the phone.
[EDIT] Another side effect is that the Google voice search was not working.
Install this: https://market.android.com/details?id=com.seb.audiotoggle
I think it will actually solve your problem. It did for me when the exact same problems started to bother me today after skiing as well!
You need to start it at every boot as it don't stick between reboots. Consider using a startup manager.
The problem seems to be a mix of hardware and software in the headphone jack, but I have not examined it much yet.
Thanks for the reply. The app you suggest should be very useful and I will download it anyway. However, this to say that the phone had fixed itself this morning.
I put the phone on charge overnight, and this morning, it asked for my sim unlock code, which I thought was very strange! But I entered the code that I had received from my network provider and now everything is working as it should.
It was probably something do with the remaining water inside the phone or possibly the cold temperatures.
Good to know! Maybe my phone fixes itself during the night as well
Still working?
Has the issue remained fixed for you? I ask because I have the same thing - the symptoms are that I can't hear anyone and they can't hear me, all media sounds are off, and the phone can't hear me.
I ran Tasker to monitor things, and the phone keeps thinking I plugged in headphones (with a mic), so that explains all the behavior. Running the headphone toggle app works temporarily - sometimes only a few seconds.
After doing a factory reset, sound would still come and go. With my Nandroid backup back on, same thing. I want to return it, and so I put everything back to stock, and noticed that now the bootloader is locked again, the issue is gone (for now).
I just wanted to keep the discussion going because I can't even tell if it's hardware related or not, and other people probably have this problem, and it takes some snooping to realize it's the headphone connector (vs sound settings, speaker issues, etc.). It could be a short (my guess) but now that it's working today I can't return it as the tech would probably claim nothing's wrong. I also already used up the one return my stupid carrier allows, so I'd rather fix it myself if it's software-related, instead of sending it out for repair.
I still have this problem, even after cleaning the headphone plug. My guess is that this is a hardware problem affecting only a few. It makes the phone pretty much useless, as you can't hear the other part talking, so I made myself a software fix that resets the sound routing the the default speaker on every boot and incoming and outgoing call. I guess I can share the apk-file if anyone is interested.
Give it a try: ----
Can release source if you are interested, but I am currently in a car getting ready for a ski weekend
I am also having this problem with my Galaxy Nexus. I would be interested in seeing the source, if you are still up for releasing it.
VingInMedina said:
I am also having this problem with my Galaxy Nexus. I would be interested in seeing the source, if you are still up for releasing it.
Click to expand...
Click to collapse
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Thanks for posting the source. I was able to work with it fine.
I've replaced my Nexus with a new one under warranty. Hopefully this one won't have the same problem.
Melhouse said:
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Click to expand...
Click to collapse
Worked for me. Still hoping that Negri will replace my phone though.
Melhouse said:
I still have this problem, even after cleaning the headphone plug. My guess is that this is a hardware problem affecting only a few. It makes the phone pretty much useless, as you can't hear the other part talking, so I made myself a software fix that resets the sound routing the the default speaker on every boot and incoming and outgoing call. I guess I can share the apk-file if anyone is interested.
Can release source if you are interested, but I am currently in a car getting ready for a ski weekend
Click to expand...
Click to collapse
Thanks for releasing this! It works great!
I was going out of my mind trying to figure out what was going on. I was unlocked, rooted in stock 4.02 when this started to happen. I thought it was bad signal quality because i only noticed it when I stopped being able to make calls and use voice dialer. I only listen to music with a headset, so never even noticed that it wasn't working with the speaker til I tried to play a youtube video.
I actually upgraded to stock 4.04 with new FA2 radios and thought I had cured it, only to have it happen again. When I read this I tried resetting all my notification sounds (Handcent, et al) hoping somewhere there was a conflict, but still couldn't find it. I'm using NOVA launcher - wonder if there's something in there?
Anyhow, I gave up since your audiojack.apk works great! Someday when I have time I'll go back to troubleshooting to see where the problem is coming from.
Thanks again!
Works temporarily
Melhouse said:
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Click to expand...
Click to collapse
This worked, but the OS will eventually think the headphone is plugged in again and I have to press the "Force Speaker phone" button again. I wonder if there is an event that is fired every time the OS thinks the headphones were plugged in? If so, that event can be captured and code could look to see if the headphones are turned off by the user and ignore the event.
Wired Headphone Routing Fix
Melhouse said:
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Click to expand...
Click to collapse
If you want the same routing fix as audiojack but have it done automatically in a service try this.
There is an issue with a lot of Galaxy Nexus where the OS thinks the headphone is being plugged in and unplugged on its own. Try this free application to resolve it:
Search Google Play for Wired Headphone Routing Fix
The birth of SoundAbout...............................
dmwoods said:
If you want the same routing fix as audiojack but have it done automatically in a service try this.
There is an issue with a lot of Galaxy Nexus where the OS thinks the headphone is being plugged in and unplugged on its own. Try this free application to resolve it:
Search Google Play for Wired Headphone Routing Fix
Click to expand...
Click to collapse
Nice! What events do you listen for?
I have another problem. When i'm in a call and i swich to speakers the person i speak can't here me...if i switch back he can here me again. I don't know what is the problem i don't think that are two microfhones one for speakers mode and one for normal mode...Maybe a software problem but i wipe and flash another rom and kernel i tryed 2 or 3 roms and kernel and i have the same issue. Now i'm on AOKP B32 with Franco Kernel 135. Anyone have this problem?
android.intent.action.HEADSET_PLUG
Melhouse said:
Nice! What events do you listen for?
Click to expand...
Click to collapse
android.intent.action.HEADSET_PLUG
6jaipur6 said:
I have another problem. When i'm in a call and i swich to speakers the person i speak can't here me...if i switch back he can here me again. I don't know what is the problem i don't think that are two microfhones one for speakers mode and one for normal mode...Maybe a software problem but i wipe and flash another rom and kernel i tryed 2 or 3 roms and kernel and i have the same issue. Now i'm on AOKP B32 with Franco Kernel 135. Anyone have this problem?
Click to expand...
Click to collapse
I am having the exact problem that you are. I am running a different ROM though, but the same issue.
ddub1 said:
I am having the exact problem that you are. I am running a different ROM though, but the same issue.
Click to expand...
Click to collapse
Have you solve your problem?
can't install the audiojack.apk because I'm still on Android 4.0.2 and min SKD is 15, could anybody port it to sdk 14?
Melhouse said:
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Click to expand...
Click to collapse
Worked for me on Verizon GN. Verizon already has a replacement on the way... guess I should've done more extensive searching for a fix first!
Spoke too soon. Seems as though the screen doesn't shut off while I am on a call. Guess I'll give the replacement a try after all.

[Q] Potential Design Flaw / Dropped call or hang up

Hi All,
I got the Tmobile Note 2 couple days ago and have been slowing increasing my usage. I have discovered a problem that I would need to the community to help me resolve to identify if I have a bad phone, or it maybe a more serious design flaw.
First, I have repeatedly able to pinpoint the problem: If you are using the hotspot that T-mobile provides for you, and you are tethering with your device; when someone calls you and you accept the call, the chances of the phone hanging up on its own without any human interaction increases dramatically if there are connections using the hotspot, i.e. Another device connecting/disconnecting from the hotspot, or lots of data traffic, etc...
The dropped calls looks likes the phone just hung up the line in the middle of a phone call. To me, the "dropped call" can be anywhere between 5 seconds to 5 minutes. I was able to repeat this issue at least 10 times in a row already and thus my concern. I have identified and replicated this problem at many many different location with many many different signal strengths, indoor, outdoor, in the car, on the can... etc....
If you guys can repeat this problem, let us know, because I do not realize any limitation of simultaneous of using the hotspot feature and the voice calling radio.
thanks ALL!
Just wanted to report back:
I just got back from the tmobile store with a brand new Note 2, and when I tested in store, guess what?
It happened the same way on the new device!!!
I'm pretty sure that it is either the design flaw of the Note 2, or there is something wrong with the build of Tmobile or JB.
Nevertheless, I hope some experts can point out what can be done to resolve this, and maybe people who have flashed to the custom roms can see if they can replicate the problem.
Basically, turn on Hotspot, connect a tethering device to the hotspot, call the phone on another line, answer the call, then disconnect a device from the hotspot.
Chances are the phone will automatically hang up the call after the first couple of tries of connecting and disconnecting the tether devices.
Thank you!
similar problem
forexmaker said:
Just wanted to report back:
I just got back from the tmobile store with a brand new Note 2, and when I tested in store, guess what?
It happened the same way on the new device!!!
I'm pretty sure that it is either the design flaw of the Note 2, or there is something wrong with the build of Tmobile or JB.
Nevertheless, I hope some experts can point out what can be done to resolve this, and maybe people who have flashed to the custom roms can see if they can replicate the problem.
Basically, turn on Hotspot, connect a tethering device to the hotspot, call the phone on another line, answer the call, then disconnect a device from the hotspot.
Chances are the phone will automatically hang up the call after the first couple of tries of connecting and disconnecting the tether devices.
Thank you!
Click to expand...
Click to collapse
Hey, I bought my note 2 last Wednesday and since day one its been dropping calls, well kind off. when i answer a call few seconds or minutes the phone mutes, the call doesnt really drop but the sound on both sides of the line mutes. untill i hang up and call again. i can hace full bars and still happens... i believe its a software glitch or something. hopefully samsung fix this before i return this phone next week.
josuetrujo said:
Hey, I bought my note 2 last Wednesday and since day one its been dropping calls, well kind off. when i answer a call few seconds or minutes the phone mutes, the call doesnt really drop but the sound on both sides of the line mutes. untill i hang up and call again. i can hace full bars and still happens... i believe its a software glitch or something. hopefully samsung fix this before i return this phone next week.
Click to expand...
Click to collapse
There are some serious flaw in the software/hardware in this phone. I have been able to replicate this problem with 100% success. Just go and turn hotspot on, and tell someone to call you, soon enough the phone will hang up the call.
I'm thinking hard of just not needing such a big screen and go for a nexus 4 instead.
forexmaker said:
There are some serious flaw in the software/hardware in this phone. I have been able to replicate this problem with 100% success. Just go and turn hotspot on, and tell someone to call you, soon enough the phone will hang up the call.
I'm thinking hard of just not needing such a big screen and go for a nexus 4 instead.
Click to expand...
Click to collapse
I have experienced this problem with almost every network and phone.... Not necessarily the T-mobile app but tethering apps in general... Even if your device supports data and voice I have experienced this with pretty much all apps but I don't know if it's just me or what.... I don't really have a problem with it as I don't accept calls when I'm tethering anyways... Just my .02 cents
josuetrujo said:
Hey, I bought my note 2 last Wednesday and since day one its been dropping calls, well kind off. when i answer a call few seconds or minutes the phone mutes, the call doesnt really drop but the sound on both sides of the line mutes. untill i hang up and call again. i can hace full bars and still happens... i believe its a software glitch or something. hopefully samsung fix this before i return this phone next week.
Click to expand...
Click to collapse
I experience something similar. I got tmobile note 2 on att .after like 5 min talking .my mic mutes.i can hear the other person but they dont hear me ,till i put speaker
Sent from my SGH-T889 using xda app-developers app
Well, for me its slightly different....
1. Wifi calling enabled and activated (blue icon)
2. if someone calls me 5, 10 , 15 min etc... later, the caller hears silence and the phone does not ring.
3. happens every damn time. I plan on calling tmobile about this....
4. the only time it works is if i make an outbound call, and within a couple mins someone can call me.. but if the phone sits there for more than a few min.. nobody can call me.
I was in a call when someone else called in and the phone froze up happend several times im really considering returning this phone
Sent from my SGH-T889 using Tapatalk 2

[Q] Call quality - other person cannot hear me

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.

incoming calls instantly disconnected

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.

Low sound volume issue post AT&T Oreo update

Ever since I updated to 8.0 last week I have had to reboot the phone on a daily sometimes twice daily basis because all the sounds randomly become very low even though the volume for all sounds is at max. Very irritating. Anyone else experience this issue?
i have this exact same issue on my device i did a factory reset and it did not go away. this is why they need to unlock the bootloader so we can fix our our issues. im working on a flash script that i will test since i have others i can use if i need to rma this device.
You would think others will be chiming in here shortly after they update. I doubt we are the only ones that will notice this issue. I would hope and expect MOTO/Lenovo to push an update out to fix this and any other issues that may have been noticed in the Oreo update. This I can at least live with as annoying as it is, Unlike my issue with my GEAR S3 Frontier no longer charging post the Tizen 3.0 update!!!! Samsung has yet to address this bug rendering this product useless for now.
i called at&t and they are replacing the device since they dont have a way to revert the software or unlock the boot loader to allow me to fix this my self. once my rma shows up i will be doing some very risky mods to the device. lets see if we can get some traction on this device.
kipmast said:
Ever since I updated to 8.0 last week I have had to reboot the phone on a daily sometimes twice daily basis because all the sounds randomly become very low even though the volume for all sounds is at max. Very irritating. Anyone else experience this issue?
Click to expand...
Click to collapse
T-Mobile variant here. I notice this randomly too. As best I can recall it only occurs when I disconnect my Bluetooth headphones. Toggling Bluetooth on the phone seems to reset volume levels.
TheLooq said:
T-Mobile variant here. I notice this randomly too. As best I can recall it only occurs when I disconnect my Bluetooth headphones. Toggling Bluetooth on the phone seems to reset volume levels.
Click to expand...
Click to collapse
Nice! I will try this next time it happens- Much better than rebooting each time.
kipmast said:
Nice! I will try this next time it happens- Much better than rebooting each time.
Click to expand...
Click to collapse
I tried it and it worked! Much better than having to reboot the phone everytime the volume takes a dump.
Good to hear it works for you as well. Maybe Moto will fix that bug in the next update, there is a lot of talk on the Lenovo forums about Bluetooth issues since the Oreo update.

Categories

Resources