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.
I'm not sure if I am the only one but searching hasn't really helped me find any answers. Basically, since updating (rather, doing a clean install of 4.2 tajku) to 4.2 Jellybean, I often have an issue where despite the fact that the proximity sensor blacks out the screen, the dial pad when pulled up still detects key hits. Hence, my cheek is randomly pressing buttons. Happens during voicemail since the dial pad is needed to get through menus and/or during calls which have a menu system.
Any else have this problem or have any ideas how I can resolve it?
Same here
Glad I'm not going crazy. Seems to also be happening without the dial pad, per say. I say that because it appears during a call, I was pressing something so I removed from proximity to be greeted by the lock screen (number pad). So I wonder if it has something to do with that. I am going to disable pin lock for awhile to see if that alleviates the problem.
Do you have something similar with SKype?
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.
MenaMAKS said:
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.
Click to expand...
Click to collapse
No Skype. And the screen goes off due to the proximity sensor - but the buttons and/or dial pad are still active. I'll try changing my power button back from "end call" to just screen off and see if that helps.
Anyway, a quick update. Seems like a couple of factory resets did the job. So something with Titanium Backup did not translate over well to 4.2 (from 4.1.2). On top of that, I can no longer seem to do a full restore, causes my device to go into boot loop. Don't know why it worked the first time. At any rate, just re-downloaded all my apps and so far so good. Just have to try and restore individual app data one by one and see if I can get it to stick without fudging up the dial pad again.
EDIT: Scratch that, it's going it again. What the hell... 4.2 is such a @#@#@ in the ass.
Still having same issue. Glad you came back with an update, bc I was about to re-flash and re-download all of my apps. I know you say that you experience it even without the keypad pulled up, but I have not. Usually happens when I call an automated system, and my call gets sent to every extension possible!
Sent from my Galaxy Nexus using xda app-developers app
Alright, I think I have it working. I did factory reset... made sure any phantom directories (i.e. storage(sdcard)/0/0/0/0 etc) were deleted.
1) By default, I tested by calling voice mail then rolling my cheek against the screen. So far so good.
2) I downloaded StickMount, Titanium Backup Pro, NTFS mounter (for ntfs driver) and ES File Explorer. Tested again as per above. OK.
3) Used Titanium Backup to restore missing apps + data. Did a test, still good.
4) Used Titanium Backup to restore only select system data (i.e. call logs, SMS log, alarm, etc). Still tests fine.
5) Enabled PGM free. Did test and BOOM, problem.
So it seems like with 4.2 there is something screwy with PGM which is essentially keeping the screen "awake" even though it's off due to sensor. Don't know why I didn't think of it earlier.
EDIT: Checked the PGM thread and it appears the author has already fixed it though only the paid version is updated atm. Says will update the free version soon if the paid version doesn't have any new bugs.
Awesome, nice work! Will see of it works for me too and report back.
Sent from my Galaxy Nexus using xda app-developers app
Edit Uninstalled PGM, reboot and its solved! Thanks for your hard work!
I was going crazy with this issue too .. it's good that it's not only me .. i will disable PGM and try
My brother's nexus has this issue without pgm installed on full stock 4.2.1 rom.
I have watched the serial code and production date is c9,or rather september 2012.
What I have to do to fix this very annoying issue?
edit: no one has this issue?It's a common problem of latest batch sold in Italy.
Hey so my speaker phone is always on whenever I make or receive a call. I've gone through every single setting, made sure no apps are installed making it default to be on (voice recorders, GPS apps, ect) yet it is always on?
Anyone know how to fix this? Is there some app that I can install that can force it stay off unless I turn it on?
Some people say its the phone thinking its in dock mode. Is there any way to disable that?
This is driving me nuts. I've tried pulling the battery, rebooting and nothing is working.
Thanks for the help!
Is there some app that I can install that can force it stay off unless I turn it on?
Click to expand...
Click to collapse
You shouldn't need an app to do what the phone already natively "normally" does. More than likely, some app you installed is causing your problem. Even if you disable apps to not have speaker on by default, perhaps the app cache settings are still affecting your phone.
If you're still agonizing over this problem by the time you read this... I would clear all the app cache, clear data on each installed app, disable all installed apps (force stop), and if that doesn't work, back up your data and factory reset. More than likely a factory reset will get your phone working correctly again. A pain, I know, but... better than going nuts! Good luck!
Yeah I've gone through every conceivable app that would have anything to do with my speakerphone and it hasn't helped. I'm afraid to do a factory reset because I honestly don't think it is going to fix it. I'm starting to think more and more that it is a hardware issue with the USB port and not a software issue. I may have to go to a Verizon store and see what they say. I'm sure once the guy can't figure it out he will tell me that I have to factory reset it at which point I want to make say if it doesn't fix it, I'll need a new phone.
So annoyed it's not even funny.....
UPDATE:
Ok so I still can't figure out what it is, I've cleared all data and cache on all apps (including the phone app) but nothing seems to help.
For ****s and grins I wanted to see if I plugged in my headphones what it would do. When I plugged them in and tried to make a call, this time the speakerphone button is NOT illuminated BUT.........IT STILL PLAYS THROUGH THE SPEAKER PHONE AND NOT THE HEADPHONES????
I know, mind...blown.
Now if I push the speakerphone button, it turns green (on) and the sound still comes through the speaker phone but if I push it again, it turns off and now the sound plays through the headsets.
What on earth is possibly going on??? Can the phone dialer app be corrupted? What else can I try other than a hard reset? Is there a way I can reinstall the phone dialer app?
I know you stated you looked at all the apps you could, but did you look into the S Voice settings to see if Auto start Speakerphone is enabled? Supposedly it'll be used only when S Voice is used, but who knows when something might be corrupted.
Already tried that, didn't fix it. Even tried disabling Svoice.
I also booted up in safe mode and it still was doing it so I know it isn't any installed app that I have that is doing it.
At this point I think have no choice but to do a hard reset unfortunately. SO incredibly annoying.
Well, I hope you solve the problem. At least with the hard reset you'll get a clean start. Nah... nothing good about a hard reset! Damn annoying! Let us know how you solved it once you get it going.
It doesn't seem to be much of a secret that BT gets roundly hosed by the 7.0 OTA t-mo update. I'm just adding my own experience for reference. I'll start with a very odd "feature" that my phone now has.
If I'm in a call, regardless of whether it's speaker, BT, or handset, turning on the screen (pressing the power button) mutes the caller. They can hear me, but I cannot hear them. Pressing the power button again to turn off the screen re-establishes the audio. it's insanity and I have no idea why/how this could be so specifically broken.
Second, the typical BT issues with the M9 and 7.0. If someone calls me and I'm using BT, no audio. I turn off BT while the call is still going, and I get audio from the handset. Turn on BT again, headset connects and no audio. However, if I initiate the call, no problems.
I don't have much hope that t-mo will fix this, so I'm going to factory reset my phone to get it back to 6.x, then run the RUU from HTC to get back to 7 and see if that's any better. if not, I'll need to find a ROM that will let me keep wi-fi calling as it's quite useful to me.
Orrrr..... someone here has a suggestion for how to fix one/both of these issues.
Cheers!
You never mentioned if your phone has been modified beyond just the update.
Presuming you didn't, factory reset is the first thing after rebooting the device (have you turned it off and on again!).
Failing that it'd make sense to flash the firmware again but the difference between ota and full flash is factory wipe so in essence you'll just end up at the same place.
The problem could just as easily be a rogue app. Anything that uses call or Bluetooth would be on my **** list for deletion.
Beamed in by telepathy.
A solid point about not providing info re: the ROM state. In fact, all stock and still boot-locked. And get this: I figured it out! Well, HTC support helped.
I factory reset the phone yesterday and much to my chagrin, it was still wonky when it came back to life. I called HTC and the gentleman I talked to suggested that I clear the cache. I have no idea why, but that sorted it out immediately.
And to summarize for anyone else that might be experiencing a similar problem and searching for a resolution:
HTC ONE M9 inbound voice muted while screen is on
and seriously, after some t-shoot, that's the exact behavior. I thought it was a bluetooth-only issue, but that was not the case. Any inbound voice, regardless of the bidi communication method (handset, BT, or speaker) would mute when the screen was on. and it was totally binary. Hit the power button during a call and turn on the screen, inbound voice muted. Press it again to turn off the screen, inbound unmuted.
So weird...
shivadow said:
You never mentioned if your phone has been modified beyond just the update.
Presuming you didn't, factory reset is the first thing after rebooting the device (have you turned it off and on again!).
Failing that it'd make sense to flash the firmware again but the difference between ota and full flash is factory wipe so in essence you'll just end up at the same place.
The problem could just as easily be a rogue app. Anything that uses call or Bluetooth would be on my **** list for deletion.
Beamed in by telepathy.
Click to expand...
Click to collapse
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!