Hello. Does anybody have an idea why there is no sound whenever I send/receive calls? Also, the UI/related app crashes whenever I do the same.
No problems when I uses SMS though, so I don't think it's a signal problem.
erickh0 said:
Hello. Does anybody have an idea why there is no sound whenever I send/receive calls? Also, the UI/related app crashes whenever I do the same.
No problems when I uses SMS though, so I don't think it's a signal problem.
Click to expand...
Click to collapse
Maybe a theme issue?
Nope. Just reformatted the phone and did not install any theme/launcher apps
Same issue
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
same here
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
Me too. Bumping in hopes of a fix.
Same. I'm running a custom ROM and haven't upgraded to 8.0 yet. Does the issue persist with 8.0? Google told me today to revert to stock and upgrade to see if that fixes it.
Sent from my Pixel using Tapatalk
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
Same thing started happening for me yesterday!
I was sending a voice message on Whatsapp.
The msg was sent but no audio was recorder.
I received a call but there was no audio (both in & out)
I tried making a call and the same happened.
The "Phone" app would even hang after hangup and would crash. I get a white screen with the G logo and a loading bar beneath it, then it would start.
Starting the phone app is also sluggish.
If I make a call (and get no audio) I try to switch to loudspeaker and I could hear the other party but for a couple seconds then it's muted, then comes back for a couple seconds, and keeps doing it intermittently.
Sound from music app and videos works fine.
SOMETIMES after a reboot phone audio&mic would return but temporarely.
SOMETIMES when I try rebooting and it doesn't work, I try safe mode and it work (not all the time though)
SOMETIMES switching from LTE to WCDMA only fixes it temporarly.
This is really unpredictable.
I reverted back to a 7.1.2 stock. At first the issue persisted then it was fixed for a couple hours.
I updated back to O and audio worked for some time but after a few minutes, the issue returned.
Now I am on a clean stock install of O. without any apps installed. The audio comes back for a few minutes, then it's gone for hours.
Hopefully this thread will grab the attention of someone who might be able to help
Having the same issue on a regular Google Pixel. Also Google Assistant is not working using the "Ok Google" voice command and the phone app - answering and ending calls lag - same issue mic and speaker do not work. In Safe work, they work but on rebooting same issue persists.
xbiggyl said:
Same thing started happening for me yesterday!
I was sending a voice message on Whatsapp.
The msg was sent but no audio was recorder.
I received a call but there was no audio (both in & out)
I tried making a call and the same happened.
The "Phone" app would even hang after hangup and would crash. I get a white screen with the G logo and a loading bar beneath it, then it would start.
Starting the phone app is also sluggish.
If I make a call (and get no audio) I try to switch to loudspeaker and I could hear the other party but for a couple seconds then it's muted, then comes back for a couple seconds, and keeps doing it intermittently.
Sound from music app and videos works fine.
SOMETIMES after a reboot phone audio&mic would return but temporarely.
SOMETIMES when I try rebooting and it doesn't work, I try safe mode and it work (not all the time though)
SOMETIMES switching from LTE to WCDMA only fixes it temporarly.
This is really unpredictable.
I reverted back to a 7.1.2 stock. At first the issue persisted then it was fixed for a couple hours.
I updated back to O and audio worked for some time but after a few minutes, the issue returned.
Now I am on a clean stock install of O. without any apps installed. The audio comes back for a few minutes, then it's gone for hours.
Hopefully this thread will grab the attention of someone who might be able to help
Click to expand...
Click to collapse
I've starting having this problem too... its very frustrating. Im on Stock O (OPR3.170623.008), Verizon,with unlocked bootloader.
me too
jasona08 said:
I've starting having this problem too... its very frustrating. Im on Stock O (OPR3.170623.008), Verizon,with unlocked bootloader.
Click to expand...
Click to collapse
stock O, Rogers.
bump - hoping someone has heard something somewhere.
Same here for my regular pixel, this is really annoyed. It just starts happening after almost 12 months since I got it.
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
I have been having these same issues with my phone. I noticed it happened after I downloaded the what's call app to make a WiFi call. I noticed another user had the problem after installing what's app to her phone. Could this somehow be the problem? I am not super tech savvy but I am convinced it is related to my downloading the what's call app. I have uninstalled the app. Still the problem remains. Any ideas? Thanks.
Has anyone that posted in this thread was able to resolve this issue? I also have this problem, I'm currently waiting for it to happen again so I can pull logcat but no idea what I should be looking for since I have no idea what can cause not being able to hear the caller so randomly.
I was originally suspecting V4A, but last night I flashed stock system img, did not install V4A and same issue occurred.
Related
I've been having a weird issue with my phone muting the mic during calls. This mute seems to be independent of the mute softkey on the phone (when it gets muted, the softkey is not lit, nor does toggling the softkey unmute the mic). This is incredibly annoying as once it mutes, the only way to continue the conversation is to hang up and redial. This issue occurs both using the phone normally (phone to ear), with a wired headset (so no possibility of cheek activating softkey), and with a bluetooth headset. In all 3 scenarios the mute will toggle on its own, seemingly randomly. I can go through a 40 minute call with no problems, yet sometimes it seems to mute right after I make the call.
Has anyone else had this issue?
This is what I have done to troubleshoot the issue:
1) With the original phone that I bought, I reset that phone back to factory settings and set it back up. Issue still persists.
2) Had the phone swapped out at the same Verizon store that I bought it at. Issue still persists.
3) Reset the new phone back to factory defaults. Issue still persists.
I will try the following:
Reset phone back to factory defaults and not install any apps whatsoever (running only apps that came with the phone, won't disable anything such as VZW Backup Assistant, etc either). Something tells me that this won't fix the problem either.
Does anybody know what I can do? This is a great phone but I'm a little miffed about not actually being able to make calls with it. I called VZW tech support and they are willing to replace the phone, but I basically have to go from a NEW phone to a certified like-new device (which VZW allows up to a maximum of 2 blemishes on the back, which I am not ok with) through no fault of my own.
See this thread on the Google Code bugtracker: (Hm.. I can't seem to post a link as a new forum member.. well its bug ID 24019 on the android bugtracker off of code.google.com) Don't want to munge up a link and piss off a mod or anything.. sorry guys :/
That im affraid is a nasty bug that is yet to be fixed.
Have you experienced this bug? I'd like to hear from members of this forum on if they have this issue, and how they resolved it (if at all). I was surprised that something so blaring isn't on the list of known GNex/ICS bugs (at least not on the one I saw on androidforums.com). I'm just uncomfortable with how the Verizon reps are pretending to not know about this issue...
//Edit: Oops. Found the other thread in this forum on this issue. It seems that I'm describing this as a mic muting issue, whereas other people are describing it with "mic cutting out" so I can never find their posts. Post ID 1403051 in Galaxy Nexus General.
Have AT&T Note 4 since launch. Stock, not rooted or anything like that. Not sure when this problem started because I don't regularly make calls, but I think within the last week or two, possibly after I got the update to COC6 (the update seemed to complete normally, though).
Every time I place or receive a phone call and attempt to use the phone normally (hold it to your head), the person on the other end cannot hear me at all. If I switch to speakerphone, they can hear me and it behaves normally, and if I connect to a Bluetooth device like my car, it also works fine, but if I try to use the phone normally, they cannot hear me. I can always hear them perfectly.
For what it's worth, Google won't pick up my "Ok Google" from the home screen anymore either. Also, I had previously had the option to wake the phone with "Ok Google" disabled, but when I try to enable it now, it hangs on listening to me say "OK Google" 3 times... as if it never hears me say it.
The microphone appears to be working completely normal for everything else I've tried, it's just acting like it's on mute when I'm in a call and not on speakerphone or Bluetooth, and the OK Google stuff isn't working either.
Any ideas? I'm trying not to factory reset... I've searched a lot and not found anything where anyone has solved the issue.
FWIW I had the same issue randomly with my rooted Note 2, and I believe I either fixed permissions or reinstalled the ROM to get it working (can't remember). I wish I could just reinstall the ROM or latest update (COC6) again so I don't have to factory reset. Is this an option at all?
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
pj_rage said:
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
Click to expand...
Click to collapse
Not gonna lie, I checked my mic hole as soon as I read this. XD
I tend to always put my pinky finger over that mic subconsciously. I don't mean to, but it's just how my hands want to hold the phone during a call. I constantly get people saying that they can't hear me though. Then I always notice that my stupid pinky is on the darn mic. Grrrrrr.
Sent from my SAMSUNG-SM-N910A using Tapatalk
So this just started a few days ago, I noticed that the notification sounds stopped working. Locking the phone stops making a sound and all notifications are silent. Watching videos and incoming calls are audible however.
A reboot fixes the issue, but it returns soon after.
I didn't install any new apps recently. Updated some, but nothing new.
Any ideas?
Same thing happened to me upon upgrading to 8.1 If I reboot it solves it for a little, but shortly afterwards no notification sounds again. Not sure if anyone has found a solution or are having the same issue?
Same exact problem here. Very annoying. I'm thinking of trying a factory reset.
If you do a factory reset let us know if it works, I've been thinking the same, if I do I'll let you know.
I thought I was the only one having this issue. Randomly comes on and off.
Sent from my [device_name] using XDA-Developers Legacy app
crazyd1721 said:
I thought I was the only one having this issue. Randomly comes on and off.
Click to expand...
Click to collapse
I checked the sound settings after updating to 8.1. All of them had changed to silent or something else you couldn't hear. I reset every sound, alarm, ringtone, notifications, etc.
I have to do this after every update. This is due to the fact, that I use the factory image to update.
So, I think this happens when I use a bluetooth device.
I notice that after I disable Bluetooth after using a headset for a bit, that the sounds stop. Anyone else can test this theory out?
You may be on to something. I use the bt with my car everyday. Noticed the same thing.
Squatrack Curler said:
So, I think this happens when I use a bluetooth device.
I notice that after I disable Bluetooth after using a headset for a bit, that the sounds stop. Anyone else can test this theory out?
Click to expand...
Click to collapse
notification problem
Squatrack Curler said:
So, I think this happens when I use a bluetooth device.
I notice that after I disable Bluetooth after using a headset for a bit, that the sounds stop. Anyone else can test this theory out?
Click to expand...
Click to collapse
After 8.1 on my pixel XL notification sounds have stopped working. I determined that it has something to do with the bluetooth. After connecting bluetooth and then turning it off that is when the problem happens. But, oddly enough, notifications sounds do work again when bluetooth is turned back on and connected....but stop again after bluetooth is turned off. A reboot fixes the problem but it happens again once bluetooth is used and turned off again. Please fix it Google.
Same for me but I only lose the Google Voice text message notification and a reboot fixes it.
It happened to me connected and not connected to Bluetooth. It would also happen to calls as well, missed some important phone calls because of it.
I am having the same problem. I'll check to see if BT connectivity is the trigger.
Same thing happening to me.. I use bluetooth daily too.
I am having the same issue. Any fixes? Has Google acknowledged?
Still happening with me. I have to reboot every few days to fix it. Very annoying.
Happening to me as well, specifically for text notifications. Sometimes the sound is triggered, sometimes it isn't.
I rebooted more than a week ago and it hasn't returned and I use a Bluetooth headset and Bluetooth in my car daily. I haven't gotten the January security patch, wondering if they slipped a fix in there?
Sent from my BTV-W09 using Tapatalk
I was having the same issue. I think it started after one of the security patches. I contacted google's support. they had me put it in safe mode and then see if it comes back. I did that, and it seemed to not break in safe mode. In theory, that means it is not a google issue, (Im sure they will play it that way) but Im not sure if it is caused by bluetooth, or something else. Anyone having the issues using a smart watch connected to it?
This is very annoying. I am still having this issue that started shortly after 8.1. Notification sounds stop working. A reboot fixes is it but the problem comes back shortly thereafter,,sometimes within 24 hours. Interestingly, the notifications still work while bluetooth is connected...not sure what to make of that. I am loathe to do a factory reset but if anyone has done it with success please let me know. Thank you.
Same thing here. I'm contacting Google regarding the issue. I've noticed a similar symptom since I've been using an android watch:
my watch gets notifications on time but my phone doesn't react. When i clear the notifications from my watch, my phone sets off multiple notifications in a row. Example: text, text, email, email, email, email, email, text, calendar. It's very annoying.
Now my phone makes no notifications. I've changed all notification sounds to full volume, I turn off bluetooth completely and my phone only vibrates for calls and doesn't make notification sounds or turn on the display as they come in.
While connected to a bluetooth device, the notifications come through that device but nothing or vibrate only on my phone.
Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls
*Copy/pasted from the Pixel 2 forum. Whoops!*
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.
I have noticed a similar problem that has cropped up recently - I cant make consecutive calls. If I hang up from a call and then try to make another the phone sits there. The phone button animates but doesn't do anything. If I try 20 seconds later it will sit there for about 10 seconds and then make the call. If I wait about two or so minutes it will work. Incoming calls are different.. if I am in that "period" of time, the phone will ring and if I am not in the phone app - meaning the incoming call screen pops up - I can answer it. If its a heads up incoming call I cant answer it. I must turn the screen off and then back on to get to the full screen to answer it. I am on 17.0.186697879 which I believe is the latest.
I've had the delayed calling problem for almost 2 months. The problem also includes sometimes not being able to answer a call from the notification shade when the screen was already on. Toggling airplane mode alleviates the problem temporarily.
There's a lengthy thread in the OG pixel threads with the many users with the problem. Also a lengthy thread on one of the Google support threads. Someone there suggested it had something to do with the mlb at bat app. I think that has since been debunked. I haven't found a solution yet and Google hasn't made an official acknowledgement yet.
This issue suddenly appeared on my Pixel 2 couple of days ago. Tried all the hacks and solution, but even turning off all the knobs in the phone permissions screen didn't help.
I have android 8.1.0
Build OPM1.171019.021
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
sb1893 said:
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
Click to expand...
Click to collapse
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
sb1893 said:
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
Click to expand...
Click to collapse
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
sb1893 said:
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
Click to expand...
Click to collapse
The saga continues. The issue occurs immediately after the first call I attempt when connected to my BMW bluetooth system. From that point on, I experience a 30 sec to 3 min delay between attempting to make a call and the Pixel XL actually initiating the call. The quickest way I have found to resolve the issue is to plug the phone into a charger for a few seconds and I am then again able to place calls. I have verified that the BMW bluetooth software is up to date and has not been updated in over a year. (Again - this issue just started happening yesterday...and I've been on Feb security patch for several weeks). I just cleared cache from within Titanium Backup. Will see if that improves the situation. Very weird. I also was just able to recreate the issue using just a simple Plantronics headset. So I continue to think it is something related to the Bluetooth stack on the phone. But I am not sure how to check to see if any of that has been updated via app update since I upgraded to Feb security patches. (I reproduced the issue at my desk using the headset after clearing cache.)
S
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Racermanz said:
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Click to expand...
Click to collapse
No - but I'm at least somewhat encouraged to know I am not the only one dealing with the issue. Today I flashed factory images (but preserved my data by removing the -w from the flash-all.bat)...that did not resolve. I've tried the reset app preferences, reboot suggestion I found elsewhere - no dice. Google pushed a new Phone app yesterday - that also did not resolve. I've even tried uninstalling Magisk completely and dropping back to 15.4 - also no help. I'm running out of ideas. I've taken to carrying a charging cable in my car...so if I absolutely need to make a call when the phone isn't behaving, I can just quickly plug it in...which does clear up the issue temporarily. Also keep a charging cable at my desk now...so I'm limping along..but for an issue that just appeared out of nowhere this week...it's been pretty frustating to deal with. Also - I no longer believe being currently connected to Bluetooth is related to the issue. I've been able to get the issue to occur today while not connected to any bluetooth devices.
Try
settings>system>developer options>media>disable USB audio routing
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Thanks bros. This is such a strange bug. Right now it works before I have turned off USB audio routing. I have turned off USB audio routing. I will report back if this DOESNT work. If I don't post again we can assume this works.
Thanks DR3W5K1, great name bro.
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Just tried to toggle on, which looks to mean Disable. Then rebooted. No luck. Issue still occurs. Thanks for the suggestion. Willing to try anything even to just eliminate as possibility at this point.
Well - I have found a better workaround. When you attempt a call, if you get no response, you can toggle Airplane mode "ON"....You will then see the call you attempted fail. When you turn Airplane mode back "Off" you can can successfully make calls again. Better than having to plug into a charger cable to get the attempted call "unstuck"....still no idea what is going on....but this workaround at least is more palatable, portable, and take a few seconds...hope someone can figure out root cause soon and a proper fix becomes available.
EDIT: Even better workaround. Toggling Mobile Data OFF and ON has the same effect of clearing the issue. And works better when connected to Bluetooth in car as those connections will be maintained vs. using Airplane mode toggle. So - issue seems to be related to Mobile Data somehow - but I have already had Advanced Calling / LTE, etc...turned off as one of my first steps in troubleshooting this issue.
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
The.Yield said:
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Click to expand...
Click to collapse
I have tried that. Sorry for not mentioning it in this thread. At one point I revoked "Phone" permission from all apps other than Phone, Carrier Services, and Contacts. Rebooted. Issue still occurred.
DR3W5K1 said:
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
Click to expand...
Click to collapse
Ahhh...I had forgotten about this secret menu. Looks like I could permanently toggle off VoLTE, WifiCalling, etc...here. But - not sure I want to go that route...I'm OK at present with Toggling Mobile Data via Quick Settings tile. And hopefully this issue eventually gets solved as mysteriously as it was introduced via some update.
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
tesla45 said:
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
Click to expand...
Click to collapse
Interesting....I'm on Verizon and I do believe that they route calls over Mobile data at times. I'm going to stay tuned, but likely done with much more deep investigation at the moment. I've spent enough time down this particular rabbit hole and the Mobile Data toggle is workable for me (not ideal, obviously)...hopefully a permanent fix materializes soon. Thanks to all for their suggestions and moral support. Much appreciated.
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Install the stock again clearing all the data. Don't restore anything with titanium or install any extra apps. Then make a call.
tesla45 said:
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Click to expand...
Click to collapse
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
sb1893 said:
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
Click to expand...
Click to collapse
Glad the workaround helps you too. My emphasis CAPS in my last post was clearly misleading, I was actually suggesting NOT to reinstall/factory reset because I don't believe that solves the problem long term and its a huge ask for a customer (when really Google should be solving this problem for us).
Based on this little workaround its clearly a software problem that Google needs to address, I've raised the issues on many threads in their product forums ... hope it gets to the right people ASAP because I believe lots of Pixel users are running into the problem (both Pixel 2 and 1st gen, another indication its NOT a HW problem).
Keep the workarounds coming folks!