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
I believe I have narrowed it down to the phone as the feature works after I reboot the phone. I noticed this when I got in the car and only the Media Audio led was lit on the receiver. When I go to the bluetooth menu on the phone and select the paired device (car receiver), Phone Audio is unchecked and I cannot re-check it. I have tried deleting the phone from teh car receiver and also the device from the phone and repairing and setting it up. It will connect and cannot select 'Phone Audio'. I also noted that after a reboot, bluetooth feature is turned off and needs to be turned back on. Once I turn it back on and click the gear on the BT device, I can turn on and off the Phone Audio and it will work for a while.
This is an 'all of a sudden' development as I have been running the same firmware and ROM for 9+ months. I am S-off and am running firmware 3.35.401.12 with the ViperOne 4.3 ROM. I have upgraded programs from the play store, but cannot figure out what might be causing this. Can anyone here help me fond a solution?
Thanks!
Keith
So just to clarify, you're using BOTH phone and media Bluetooth connections to the one single bluetooth media AND voice enabled head unit in the car?. One receiver?.
Do you have any apps running that will disable things when battery power gets low, like snapdragon battery guru?. Does your rom have any such features built in?.
Make sure both devices bluetooth lists are clear of old devices that no longer have access on resonable terms. Just to make sure its not scanning for another device as a primary.
Make sure you car audio system is running the latest firmware. It can usually be updated via cd/dvd/sdcard.
As mad as it seems, make sure the time is correctly set on both devices.
Beamed in by telepathy.
Yep, yep and yep.
Battery is full , I do not have battery guru installed. I did not change anything. It just now needs to be rebooted before it will connect to BT Phone Audio. Medial Audio connects and works properly, just as it always has.
I have a single Pioneer Premier head unit that I have used for years with multiple phones. If I reboot the phone before it tries to connect, it will connect and Phone Audio works. When it is 'locked out' (my term), I cannot select the block on the that is labeled 'Phone Audio' to check it. As the screenshot shows, it is 'unchecked' and no amount of touching it will check it. The only way to 'check' it is to reboot the phone. Oddly, it reboots with bluetooth turned off and when I turn it on, usually, it is already enabled (Phone Audio).
Thanks for the help,
Keith
After a little research it would appear that, apart from being right about the max enroled devices allowed is 3, "discoverable mode" is required.
Did you connect the phone to the radio or the radio to the phone?. Which discovered which for pairing?. Try pairing the other way from the way you did.
Can you access any options by holding or tapping on any of the fields in the picture above. Something to do with pbap if you can find it and turn it off, most likely under contact sharing. If not, dont worry.
Try turning contact sharing off or see if the stereo will copy them and store them so you can turn that feature off.
Other than that it could just be an incompatibility between the devices. It is not unknown for car audios to be crap hardware.
Beamed in by telepathy.
I am on teh same page of keithspg
I recently resetted my HTC M9 and as coinsequence I have been obligated to reinstall all BT devices (car, 2 headest, laptop)
It worked well (as in the past) for few days but now I have the same issue : I cannot switch on the audio phone !!!
Below the picture:
I could not find any other solution than to wipe the ROM and reinstall. I am now running viper 6.0. no problems. If you are not soff, you may want to ruu it. If you are soff you may want to wipe and install again whichever ROM you are running.
Keith
keithspg said:
I could not find any other solution than to wipe the ROM and reinstall. I am now running viper 6.0. no problems. If you are not soff, you may want to ruu it. If you are soff you may want to wipe and install again whichever ROM you are running.
Keith
Click to expand...
Click to collapse
I am S-On and completely stock
I cannot wipe my smartphone (it is a company smartphone)
I fixed the problem with a simple soft reboot
Inviato dal mio HTC One M9 utilizzando Tapatalk
I am also having the exact same issue. I still have not been able to track down which app is the one causing this conflict. I have also done a factory restore and that seems to have worked for a time but the issue started again. It may be unrelated but... Have you changed the themes? I think that's one of the last things I did before it stopped working. Also restarting the phone "fixes" the issue for one connect/disconnect, but after the bluetooth is disconnected it will no longer allow to use phone audio. I have gone into the settings for the "Paired Bluetoth devices" and I am unable to check "Phone audio". It is not grayed out but it doesn't work either. This issue is driving me crazy, I hate to have to restart the phone every time I get in and out of the car just because the bluetooth wont sync. That being said, I have another clue into the issue. Today I was using the bluetooth in the car while on a phone call and transitioned to my Jawbone Icon when I exited the car flawlessly. I turned off the car, turned on Jawbone (so there wouldn't be a conflict of the Jawbone trying to connect to the phone while it was still connected to the car) Immediately the Jawbone connected and I was able to carry on with the conversation. I was really happy about this. However, when I was done with my phone call I turned off the Bluetooth and turned off the Jawbone. About an hour later I received a video through Whatsapp and when I played it there was no volume. When I pressed the volume button on the phone the volume bar had the Bluetooth symbol!!! The Bluetooth had been off for quite a while now and there where no Bluetoth devices present.
Hopefully this gives some insight into this issue that will help resolve it. Thank you very much!
I have also tried the soft reset and the issue persists.
HTC One M9 Not Rooted
Android 6.0
Patch Lvl Dec 1, 2016
Sense 7.0
Software # 3.37.605.19
This is currently happening to me too. No fix yet. I tried this on other bluetooth devices that are hands-free capable like my portable speaker, and the same issue occurs.
HTC One M9
Android Revolution HD 20.0
Android 6.0
Sense 7.0
S-off
I am having the same issue
HTC One m9
Viperonem9 5.1.0
I have tried wiping / reflashing and still haven't resloved the issue.
this is super annoying I hope someone finds a fix soon
The issue is randomically annoying me too but , as I said few time ago, fortunately I am fixing always doing a restart
Inviato dal mio HTC One M9 utilizzando Tapatalk
I have recently had this problem on my stock ROM HTC 10. The HTC Australia website online chat actually gave me a solution which worked (!)
Settings > Apps > ... (menu) > Show system > Bluetooth Share > Storage > Clear Data
New findings on my phone.
I have an M9, rooted, unlocked and s-off. It has a stock ROM. I have had this issue for a while now. I don't know when or how it started. Everything used to apparently work fine. Could have been some update or an app I added at some point in time that possibly we all share. I had been restarting the phone as well to get the "phone audio" to work. That became excruciatingly tedious. I did find that, on my phone at least, placing the phone in airplane mode, waiting a moment for that to kick in, then starting up the Bluetooth, brought it up with "phone audio" checked. Then I would just turn airplane mode off.
Still a ridiculous way of getting it to work correctly. However, if this technique works for others as well, then I am thinking that airplane mode is disabling a service or something that is keeping it from connecting correctly. I will be looking into this as I hope some more savvy folks will be as well. If someone does figure it out, please share.
---------- Post added at 11:24 AM ---------- Previous post was at 10:30 AM ----------
I found another thing that might be causing the issue by reading other forums. I made the adjustment on my phone this morning and I believe it to be working at this time. (For now anyway). I think it might be related to location services accuracy settings. There are a couple of ways to get there. In Bluetooth settings when the Bluetooth is off, you might see a link to it on the initial Bluetooth page. Otherwise, I found them under, Settings/Location. I have my mode set to "Battery Saving". But under the triple dot should be Scanning. Here I turned off Bluetooth scanning and things seem to be doing okay thus far. Just seems like it takes a few seconds longer to connect to my devices. However, so far, no issues. I may be speaking too soon. If I find it didn't work, I will correct myself in another post.
Best Regards,
Lyndon
Same problem. Either after using my Fiat Car bluetooth system, or after my BLT bluetooth headset, my Phone audio stops and I have to restart my phone.
On my bluteooth headset I only use the "media" audio.
I am using a Samung galaxy 3 watch also.
Huib
Thank you!
[/COLOR]I found another thing that might be causing the issue by reading other forums. I made the adjustment on my phone this morning and I believe it to be working at this time. (For now anyway). I think it might be related to location services accuracy settings. There are a couple of ways to get there. In Bluetooth settings when the Bluetooth is off, you might see a link to it on the initial Bluetooth page. Otherwise, I found them under, Settings/Location. I have my mode set to "Battery Saving". But under the triple dot should be Scanning. Here I turned off Bluetooth scanning and things seem to be doing okay thus far. Just seems like it takes a few seconds longer to connect to my devices. However, so far, no issues. I may be speaking too soon. If I find it didn't work, I will correct myself in another post.
Best Regards,
Lyndon[/QUOTE]
Thanks - I believe this has fixed the issue for me!
Brett
Late post, but just ran into the same problem with my One M8 with final Viper ROM and my newly installed Pioneer BT head unit. Turning off BT scanning on the M8 worked for me as well.
Bluetooth audio and or media check boxes can't be checked
I was able to resolve the issue on my HTC One M9 by turning WiFi scanning and Bluetooth scanning off, updating the Bluetooth checkboxes for audio and media (both of which were unchecked and wouldn't allow me to check them), and turning the scanning back on.
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.
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!