Related
Hi ALL,
I just got my ZW yesterday and although there was a fair amount of frustration initially I think I'm getting the hang of it. I do have small wrists so its kind of big, but I think its livable. I have a few questions I hoping to get some answers to.
It is paired with an LG Volt running Kit Kat 4.4.2 and the ZW got updates to Android OS 5.1.1.
1. Part of the frustration I had yesterday was in connecting to my phone. I had already installed the Android Wear and Zenwatch apps on my phone and I started both and then turned the ZW on for the first time and it did connect reasonably soon. It updated and then I played with it for a while powering both down to see what would happen. But then I had hard time re-connecting and ultimately had to do a factory reset and the ZW updated again and at least it did connect. Now when I want to use the ZW I power on the phone, start the A-Wear app and then power up the ZW. The last several times it did connect but took a minute or so. My question is this all normal operation for the ZW and have others had to do a factory reset?
2. One thing that really bothered me was that when the ZW was connected all the sounds on the phone (like the sound when you tap on an icon) were very low, almost silent. Even when I powered down the ZW the sounds were still very low. I had to restart the phone to restore the proper sound level. BUT . . . this morning I tried everything out before writing this and the ZW connected and the tapping sounds on the phone are FINE!!! This is not what it was doing yesterday! Has anyone seen this behavior?
3. When an incoming call comes in the ZW displays the caller ID and if its in my contacts their name and picture - this is what I really wanted in a watch. Then you can swipe to the red to send the call to voice mail or swipe to the green to connect the call. Once connected there are three screens: Mic, Speaker and Hang up. Tapping on the Mic draws a line though it and mutes the mic. But tapping the Speaker also draws a line through it but that TURNS ON THE SPEAKER, just the opposite of the Mic. Is this a bug?
4. Lastly, from the clock face, when I swipe to the left the first screen are the apps. The third screen is the Google Now stuff. But the second screen says: No contacts found - Add contacts to contacts app on phone. But I have plenty of contacts in the app on the phone and when a call comes in the ZW correctly shows the called ID info from my contacts. Is there another place I have to enter the contacts on the phone?
Thanks in advance for anyone who can help me out!!
Gerry
1. I definitely have seen some delay between connecting the Zenwatch and my phone (Zenfone 2), sometimes I have to fully close the Android Wear app and reset the BT connection before it reconnects, usually if I reboot either the watch or phone, or if I separate the pair too far, and the connection is dropped. I did, at one point have to do a system wipe, but it's gotten better over the updates.
2. It might be that your phone is trying to route sounds to the ZW as an audio device (not too sure about this one, since I leave my phone on vibrate at almost all times).
3. The call control is pretty buggy, since it's not Android Wear native, it's an Asus made app. It's kind of weird, if I tap the speaker button, it doesn't reflect it on my phone, but it turns on speaker anyways, and if speaker was already on, it also draws a line through the icon on the watch. Hopefully they fix this in a future update.
4. I believe you need to have your contacts synced with your Google account, because I think incoming calls just read off of what the phone says.
Hi itechnoguy,
Thanks for the input. First off I just wanted to say that I ordered the Zenwatch 2, but not for its new features. My wrist is kind of small and the original ZW was just way to big on it. So I ordered the smaller ZW 2 and I'm hoping it fits better.
As far as my questions:
1. Before I decided to get the ZW 2 and was still playing with the ZW it did seem to connect more reliably. So maybe the ZW 2 will connect even better!
2. I don't know why it did that but the last several times that the ZW connected the phone's sounds were normal!! Strange!
3. Yeah, I kind of figured that.
4. Once I get settled with thee ZW 2 I'll play with Google some more to see if that helps.
Again, thanks very much for your comments.
Gerry
hi
i got ZW yesterday and it syn to my lg g2 mobile but the contacts it says" add contacts to contacts app on phone" .all my contacts are in my phone tho
can you help me please
dharmateja said:
hi
i got ZW yesterday and it syn to my lg g2 mobile but the contacts it says" add contacts to contacts app on phone" .all my contacts are in my phone tho
can you help me please
Click to expand...
Click to collapse
I have the same problem. But I've gotten answers from several people that the contacts on you phone are NOT the contacts that will show up in the contacts on the watch. It seems that you have to add contacts into Google somewhere and frankly I really haven't looked into it any further. I think if you go into you Gmail account on the web there is some place to enter contacts and perhaps they will then show up on the watch.
Gerry
Hi,
about 2 day ago my SW3 stopped displaying notificaions like Facebook Messenger, SMS (stock application), calls. I tried reinstalling everything - factory reset, reinstalling Android Wear application etc. It helped for some time but after few hours it stopped displaying notifications again.
Google Now works, Coffee (SMS) works but stock SMS or calls or Messenger aren't display on my wrist.
I'm not 100% sure (I tried new ROM) but I believe that I wasn't changed anything. Android Wear application was upgraded twice and it's name was changed, could it be the reason?
I haven't install any new application.
Aby idea?
Thanks.
P.S. I have Samsung S6 with custom ROM. SW3 is on stock.
Are the notifications displaying on the phone in the Notification bar?? If not, then it's a problem with the phone and the ROM. New ROM may be blocking notifications. I have Notification Manager in my Settings which allows me to change notifications. The watch will only display notifications that appear on the phone.
Did you make sure to enable Notification Access in the phone's settings?
The designer can disable notifications in the watchface, could that be it?
Sent from my KFTHWI using Tapatalk
I could see the notification in the bar and everything was enabled.
Now, although I didn't made any change it started working again well. I don't understand...
Thanks for trying to help.
Guessing its the rom
It sounds similar to the problems I am experiencing. Everything works fine for a few hours after a factory reset, but then I am stuck with no notifications from Gmail, Hangouts stops syncing new messages, no remote controls for Play Music, etc. There is still connection with the phone... Find My Phone still works, Ghostracer still syncs my runs (eventually).
I've tried several factory resets and still it happens every time. The watch was working great until a few weeks ago, very frustrating.
I have exactly the same problems as above.
Smartwatch 3 and Note 4 - both stock. They work for a few hours together after a reboot and then the notifications stop appearing on the phone.
I turn off notifications to android wear and turn it back on again and its ok for a little while and then stops working again.
Anyone got any ideas?
A bit of an update to this. I've now managed to get mine back up and running reasonably well - to the point its been running ok for 2 days. Previously it would only be an hour or two until it stopped sending notifications to the watch.
I deleted the Android Wear App
I performed a factory reset on the watch
Re-install android wear.
Pair watch
It then went through and installed all my apps and since then has worked fine.
I've figured it out. It was caused by restoring nandroid backup in TWRP.
Solution: go to the application manager on the phone, all applications. Find Google services and delete all data including wear storage.
The watch will be forgotted and you have to pair it again but everything should work well.
I was just about to reply to this again as although above I said it was working fine I managed to get it to break again.
The only difference was that I had changed to a non sony watchface.
As soon as i started using a 3rd party one i was getting the same problems again
I've been back on a builtin watchface for a while and its been working fine.
I've just swapped back to a 3rd party one to see how long it works for.
For the last week or so I've noticed that when I get a text, I get the preview pop up of the text, and then it disappears - along with the notification of the text. It will either disappear immediately or soon after. Sometimes if I have multiple text notifications - and I touch one - the rest will disappear. It also removes the 'unread' badge count on my Nova Launcher bar. This has never happened before, and I'm unsure what could be happening now to cause it. I normally use Textra, but I switched to Android Messages to see if it was an app error but the same thing continued.
I was aware of the Oreo issue where text messages weren't being received, but I'm definitely receiving them. I'm on a Pixel 2 XL now, but this was happening with my Pixel XL last week also. I've tried turning off the battery optimization in case it was acting funky, but that hasn't changed anything. Any ideas?
I am having the same issue. I'm on a Verizon Pixel 2 XL. I get a text, the notification starts to play and then cuts off, not showing an unread notification. I'm getting the text, if I go into Textra it shows the new message, its just marked as read.
Coincidentally, I'm also having an occasional issue where my screen won't wake up and I have to reboot the phone to get the screen to turn back on. Haven't seen anyone having that issue yet either.
I have noticed the same thing on my Nexus 6. I haven't noticed an update to the messages app that corresponds to when this started, but the android wear app updated around the same time, so I was curious if it had something to do with that.
---------- Post added at 09:02 AM ---------- Previous post was at 08:48 AM ----------
I just uninstalled the wear app and my notifications don't disappear any more. Unfortunately, I can't use my watch now
Messages notifications are disappearing on my Pixel 2 (non-XL) also. Sometimes they disappear so quickly that I don't even get the partial sound, just a short vibration from the phone.
I also have a Wear device. Haven't tried removing the Wear app, because all other notifications are working correctly, and I depend on them much more than the occasional text I receive these days.
I'm getting this on my Galaxy S8 as well; I was finally able to track this back to the Android Wear app, but as I haven't told it to silence notifications on my phone when connected to my watch, I'm not sure exactly what is causing this bug...
Sent from my Galaxy S8 using XDA Labs
benmeroff said:
I'm getting this on my Galaxy S8 as well; I was finally able to track this back to the Android Wear app, but as I haven't told it to silence notifications on my phone when connected to my watch, I'm not sure exactly what is causing this bug...
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
I just noticed that I'm having this problem as well after a few people asked me why I hadn't responded to their texts. I'm sure this used to work fine. Maybe it was broken in a recent update of messages?
Good catch tracking it to Wear. I have figured out the following:
If the watch is on, the text notification gets "eaten up" by the watch and does not show on the phone
If the watch is off, the notification does remain on the phone
If the watch is on but I set it to ignore the "Messages" app notifications, the message shows on the phone
This is pretty annoying as I do like getting notifications on the watch, but of course I don't want them to disappear from the phone. It seems like for the moment, I have to choose between one device or the other.
I opened a bug report at https://issuetracker.google.com/issues/70808796
So I actually think I may have figured out what's happening on my end but still don't know exactly why... I had AT&T NumberSync enabled for my LG Watch Urbane 2nd Edition, and after disabling that all my text notifications persist like they used to; basically my watch now functions tethered to my phone through a traditional Android Wear connection and will only get notifications once "passed on" from my phone, versus catching the texts via the AT&T network directly with NumberSync.
Sent from my Galaxy S8 using XDA Labs
I have the issue on Nexus 6 and Android wear also. Any solutions to keep both going?
In the Wear app on the phone check to see if "Silence phone while wearing watch" is enabled.
benmeroff said:
So I actually think I may have figured out what's happening on my end but still don't know exactly why... I had AT&T NumberSync enabled for my LG Watch Urbane 2nd Edition, and after disabling that all my text notifications persist like they used to; basically my watch now functions tethered to my phone through a traditional Android Wear connection and will only get notifications once "passed on" from my phone, versus catching the texts via the AT&T network directly with NumberSync.
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
You are a genius! Thanks. This solved my problem (although I think the underlying issue might be different since you are on AT&T).
The winning combo for me (I'm using T-Mobile with "DIGITS with Paired Data") is:
On the watch, settings --> connectivity --> cellular --> advanced --> watch shares number with phone --> calls: on, text messages: off
On the watch, settings --> apps & notifications --> app notifications --> show all --> messages --> off
Since TMo already handles having the watch SIM share my main SIM's number on the network side, there's no need to tell the watch about this. I've confirmed that the following work:
Incoming texts appear (and stay in the notifications) on the phone and watch
I can reply to texts from either device and the "from" number is correct (my main number)
I do not get duplicate notifications on the watch (the watch's messages app's notifications are disabled)
I can place a call from the watch and the correct "from" number appears on caller ID
I can receive a call placed to my main number on either the phone or the watch
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.
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!