Long delay when attempting to make a phone call - just started - Google Pixel XL Questions & Answers

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!

Related

Eic 4g Touch Bugs Thread

I'm seeing many users notice different little bugs with the phone (me included) and instead of having multiple threads about it, maybe we can all post it in one place where later the devs can see it and work on them once the phone is rooted etc.. Good idea/bad idea? I come from an Evo 4g with Sense rom so I wonder how many of these might not really be "bugs" but just a different user experience.
I'll start..
Accu weather app not updating location automatically
apk files downloaded from the computer and then transferred to phone are not showing up (unknown sources, usb debugging checked)
No function when touching the clock widget. It does not launch me to alarm, world clock, time etc menu. Maybe this is just a touchwiz thing as I mentioned above, I come from a sense rom.
So far those are the ones on top of my head. As I use the phone more, I'm sure I'll spot more (hope not!).
Anyone else?
Phone dialer issues
I have to reboot my phone from time to time to make a call.
It just says call ended when i try to call out.
When i reboot it works fine for a few hours.
Mentioned above plus the following so far (except reboot for calling issue):
No landscape mode using TW (auto-rotate enabled)
Red LED only available notification color (REALLY?!)
Skype video calling is upside down when using in portrait mode.
Also, phone call is automatically in Speaker mode when calling after making a Skype video call.
*Occasional phone FREEZES. As in, one minute it is okay, and the next minute, you have to do a battery pull. Happened twice since I got it on launch day.
*Browser closing for no reason. Happened 4 times since launch day.
*When plugged in with Samsung charger, phone's screen will act real glitchy
*SWYPE does not work properly, no matter the settings. Have to type normally.
That's all the software bugs I've experienced. Hardware-wise, there are reports of problems with data, 3G, 4G, and WIFI....I haven't seen any word on Bluetooth yet.
Journeyjeans said:
*Occasional phone FREEZES. As in, one minute it is okay, and the next minute, you have to do a battery pull. Happened twice since I got it on launch day.
*Browser closing for no reason. Happened 4 times since launch day.
*When plugged in with Samsung charger, phone's screen will act real glitchy
*SWYPE does not work properly, no matter the settings. Have to type normally.
That's all the software bugs I've experienced. Hardware-wise, there are reports of problems with data, 3G, 4G, and WIFI....I haven't seen any word on Bluetooth yet.
Click to expand...
Click to collapse
Go exchange your phone -- sounds like a lemon. No other real complaints about freezing or auto-closing apps.
Erislover said:
Go exchange your phone -- sounds like a lemon. No other real complaints about freezing or auto-closing apps.
Click to expand...
Click to collapse
Actually, other's have experienced auto-closing apps and freezing. It's in a thread around here or at sprintusers.com, I forget which.
For the first three days I couldn't get data while roaming though the proper settings were checked. Sprint customer care reset my phone and after an hour of waiting it works.
All else its great (except for the above oddities with Touch Wiz) though I haven't checked GPS after encrypting the device.
Sent from my SPH-D710 using XDA App
humdrum2009 said:
I have to reboot my phone from time to time to make a call.
It just says call ended when i try to call out.
When i reboot it works fine for a few hours.
Click to expand...
Click to collapse
Can you elaborate on this issue?
Also, anyone else having similar issues, please chime in.
Are you seeing a circle with a slash through it (no service) when this happens?
Can you receive calls when this happens?
Do you lose 4G or WiFi? Or is it just Voice/3G?
Does it seem to happen sometime after making a call/text (~30min), or any other pattern you've noticed?
Are you rooted?
If yes, what kernel (zedomax or tanimn/shabbypenguin - trying to narrow down an issue with one of the current root kernels)?
Exchange Appt. Notification Bug
I have had multiple reminders pop up for from my Exchange calendar and i can't seem to dismiss or snooze them from the notification bar. The snooze and dismiss buttons are available but are non responsive. The only way I can get rid of the notification is with the "Clear" button which is for all notifications. Has anyone else noticed this?
Journeyjeans said:
*SWYPE does not work properly, no matter the settings. Have to type normally.
Click to expand...
Click to collapse
I know this may sound silly, and you may have already checked this, but check your language settings. I've read about some owners that were having problems with Swype discovered that their language was set to Spanish.
Also, on the LED notifications only being Red, I've been playing with an App called Light Flow. I've at least been able to change the notification colors to Blue using this App. Also, the App lets you use "White" as a color, which still shows a Red light, but blinks very fast if some of you prefer a faster blinking light.
I have had the roaming data issue as well. It does eventually work for me though, but on once occasion it took 10 minutes before data turned on after the roaming started. I will try calling Sprint as well.
Wifi signal is bad.. but speedtest says otherwise. I think the issue is with the amount of bars displayed and not the actual signal. I was standing 5 fee fromt he router and still didn't have full bars.
Ive been having problems today with dropping data connection. Toggling 4G off and on seems to restore it even in no 4G areas. I guess it resets the radio or something?
MadFlava said:
Ive been having problems today with dropping data connection. Toggling 4G off and on seems to restore it even in no 4G areas. I guess it resets the radio or something?
Click to expand...
Click to collapse
Try profile and prl update...
My data did cut in and out till i did the normal sprint updates
Sent from my SPH-D710 using XDA App
Just got this phone friday. So far the only bugs I am experiencing are roaming in places my evo got coverage and the security draw pattern having a mind of its own making it very hard to unlock the screen. Also the wifi reception is noticeably weaker than my evo
nate420 said:
Try profile and prl update...
My data did cut in and out till i did the normal sprint updates
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Ive done that already and it didnt help. Thanks, tho.
Luckily, no freezes or crashes here (knock on wood).
what i HAVE noticed is the rotate bug, for instance
when rotating the phone for texting or browsing, you have to kind of
bring it up to your chest @ about a 90 degree angle in order for it to rotate.
calibrated it all correctly & i still have to do that.
this is my first phone from the Epic/Galaxy company so im not sure if that was a problem in the original Epic 4g (non-touch) but it sure is kind of annoying :/
hopefully the dev's can tweak the gyro or SOMETHING.
Poor Wifi/3g Signal
Noticed lower bars on both wifi and 3g...when in same spot on my Evo 4g I had more...might be just how many bars its displaying and not the actual signal...but not for sure...actually went into roaming a few times when with my Evo 4g I never did (even with roaming was set to automatic...now I have it set to sprint only)
Hello. Has anyone tried updating through Kies? I tried and it says that this version of software cannot be updated. I just got my phone today. I did have problems installing the drivers. After I let it install say one or two drivers, one would error out. Once I unplugged it a few times and then plugged it back it, all of the drivers installed.
I hope this doesn't mean that Samsung is not going to upgrade to ICS or else I am taking this back. I have a Samsung Galaxy Tab 7" and it won't allow updating with rooting. Thanks for any input and have a great day/night!
analyst28 said:
I have had multiple reminders pop up for from my Exchange calendar and i can't seem to dismiss or snooze them from the notification bar. The snooze and dismiss buttons are available but are non responsive. The only way I can get rid of the notification is with the "Clear" button which is for all notifications. Has anyone else noticed this?
Click to expand...
Click to collapse
I noticed this too.
you have to check the check boxes next to the calender item. This is deceptive because the boxes have checks in them. But they should be green and not grey.
hope that helps

Silent mode goes on automatically during night

Sometime during night silent mode goes on, and it's on when I wake up. Then I have to use the slider to get the phone back on normal state. Quite annoying. Slider was in normal mode all the night. Anyone else? How to stop that behavior?
This happened to me too. Did you have Do Not Disturb settings set on your prior device and then restore the back up to your OP3? I have read that this is the cause of the problem - the old setting transfers over and there is no way to change them. I went into the global setting for app notifications and reset all apps. This worked for others and appears to have worked for me as well.
Having the same issue here.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Yes, actually I had it on on my OPO and I transferred apps from it to the OP3 using the installation wizard's nfc method. I did the reset, let's see if it did help..
I tested resetting notifications, did not help
Me too. Migrated from my old phone using the NFC transfer wizard. Old phone was setup to go to silent 10pm - 7am. It appears the setting is transferred over but at 7am the OP3 doesn't exit silent mode. I then have to toggle the switch to take the phone out of silent but still seem to have issues with notifications sounds afterwards.
I solved it by installing new custom rom and I didn't use restore function this time..
i too am having this issue. i attempted resetting all apps settings but that didn't work.
has anyone figured out how to fix this without factory reset or installing a custom rom?
Add me to the list and I set it up as a new device. Only had the phone a day before I applied the 3.2.0 update so I can't say if was happening before. Hope there is a fix for this soon.
IMO this is because Google is syncing the DND preferences from your Google account, regardless of whether you used the the whole "set up nearby device" thing
I have this issue except Silent mode automatically turns on throughout the day for me. I have factory reset my device and setup the device as new and the issue continues. Now I'm really unsure how to fix this.
Same issue and updating to 3.2.1 didn't fix it.
I've the same issue!
I've noticed that the sound (also from the notifications) can be turned on again (for that day) by switching off, and on the Alert Slider, and then adjusting the volume-sliders in settings.
I don't think it's a Google issue as I have 4 different phones on my account in the last month and none have done this. Just ordered another 6P while they were 20% off in warehouse deals so I'll swap over to this phone Monday and see if the issue follows. For now I'm playing with Tasker to reset all the volumes at 7am.
I've got the same issue. But I did not transfer any settings to my op3.
There's nothing in my "do not disturb" menu, and nowhere to set up automatic silent mode, as far as I can see.
Same issue faced, no solution or fix found up till now.
Me too facing the same problem.. Even in day time it goes automatically to silent mode. So incoming calls doesn't sound and it solves only when I restart the phone.. And after sometime the problem is occurring again and again.. Does anyone found the solution?
I had the same problem in my opo too..
Same here. Since the 3.2.1 update my OP3 sets to Silent overnight. Some has said it's True Caller Spam Blocker, but as I don't have this it's not a solution for me. Tried the usual reset but no luck. Really need a fix for this as I need to get important calls/texts overnight. Not a hardware problem that I can see as fine before update; broken afterwards, and the physical switch works very well.
Also, I've not used any restore function whist setting up.
It would be useful if people experiencing this problem could mention it on the OP support forum. I'm using the threads...
https://forums.oneplus.net/threads/do-not-disturb-notifications-problem.451989/page-7
https://forums.oneplus.net/threads/possible-bug-with-oxygen-3-2-1.455413/
yes - please do and add @oneplus to your answer to adresse OP team directly. Thanks.
This is related to OOS only, i installed custom rom CM based nd didn't face this issue. Then installed.OOS no restore setup as new device still same issue with no ringtone.
The fix should come from Oneplus

Bluetooth turning off since NMF26U

Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
nighcore said:
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
Click to expand...
Click to collapse
I also use a Huawei watch and the drive safe app. I'm gonna install an older version of the state farm app as it recently was updated now that I think of it.
Sent from my Pixel XL using Tapatalk
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
FWIW: I've had no Bluetooth issues. Only things I use it for are connecting to my two cars for phone, and Android Auto (which uses USB and Bluetooth connection).
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
millerd79 said:
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
Click to expand...
Click to collapse
Ever since I got the Gear S3, my Bluetooth will restart every single time I disconnect my Bluetooth headphones. It also never routes calls through my headsets unless I go into Bluetooth settings and uncheck and then recheck the phone audio option of those headphones every time I reconnect them. I've tried maybe 6 different BT headsets and it's the same case with all of them.
I have been having this issue since NMF26U as well. NOF26V actually seems even worse. It doesn't go off immediately upon connection or disconnecting from my car, but then randomly wile the BT lite will disappear while it is disconnected from any devices. Toggling it back on works as does a reboot that comes back on with BT activated even though it was off when rebooting. Hard to believe after this many updates that BT issues continue to be an issue with this phone.
Probably background tasks are getting killed aggressively. Despite being "not battery optimized", my VPN app gets killed too, if I don't touch my phone for too long. E.g. at night. And yes, I'm facing Bluetooth issue too.
Strange, Bluetooth hasn't turned off since my first post. ?
Sent from my Pixel XL using Tapatalk
I've had this issue and I'm not on the latest firmware. It's happened twice now. Very random, a week between. Maybe it was an update with the Google app, I've noticed a bunch of updates recently
I am having the same issue. The only thing I use my bluetooth for is my car. I have to turn it back on everyday when I start my commute.
I think I found a work around....
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Kokopelligod75 said:
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Click to expand...
Click to collapse
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
t3chfaith said:
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
Click to expand...
Click to collapse
Yeah I would be very curious if it works for you as well and hopefully it does. I was getting very frustrated with it but since I changed those settings it seems to be working fine now and I haven't really noticed any difference in battery performance either.... If you don't mind, keep me posted as I'm curious. Thanks!
Had the Bluetooth turn off on my XL before even entering my car (but I didn't see it happen except when I was about to get in the car and noticed no BT indicator). This was approximately an hour after a reboot and no BT devices had been paired though the indicator was on for some period after the reboot. Pretty hard to believe it was an optimization issue since I had run no apps after the reboot. While typing this, the BT icon disappeared again. Add this to getting a Verizon "Server Unreachable" error on my wife's Pixel yesterday and my XL this morning that both needed reboots to remedy. My frustration with this phone is pretty bad today. Both are unlocked BL, rooted with newest SU, running newest TWRP and newest Google version but otherwise stock. P.S. When you see about 4 Google play updates a day for about 2 weeks (with not very many apps installed other than the base) it is hard to guess what my be causing the issue. OK, rant over.
BT has definitely been a PITA since the latest security update. It's completely ruining the music experience on a car I bought days before the update came out. Since the update I constantly have to toggle bluetooth on then off again to get the phone to connect to the car. Then I have to open Google Play Music and start playback manually. This happens several times a day and is very annoying. Had not a single issue before the update.
I am having issues with Bluetooth disconnecting as well. Was bad on previous build but this most recent update, NOF26V build, is worse. I connect to my truck, watch, and speaker system in home and office. Happens randomly without notice. I have tried to test the "do not distrub" theory, after reboot, etc., so far I have not figured out a root cause or time.
Trying the optimized thing for the heck of it. I noticed that only share was listed and not MDI services. I wonder if that is only available on Google phones and not Verizon somehow or only shows if the BT is connected to the device, but I'm not in the car to check.
I too have a gear 3 frontier and since then I have to reconnect my pixels bluetooth, pretty much once everyday. very frustrating lol
Same BT problem
I have been having the same issue with BT switching itself off for about a week now. Never had any BT issues prior to that. Mine is a Verizon Pixel XL. I noticed it when it wouldn't connect to my car, but I quickly discovered that was because BT was off on the phone. I always leave BT on, so I knew something was funky and paid close attention after that. Once I turn it back on it connects to everything just fine and it stays on for the duration of me using it at that time. But when I go to use it the next time, it is off again. It can be a variable length of time in between when I use it, so I don't know how soon it turns off, but it has to be within just a few hours. This pattern suggests to me that something is turning it off, perhaps to save battery, if it goes without being used for a certain time period. I did not knowingly turn on any setting that does that, so it makes sense that an update changed something. I have not tried the workaround/fix mentioned above; I will do it and report back.

Verizon S8+ Bugs and Issues

Hi everyone,
I have 2 Galaxy S8+ from Verizon and here are my issues:
Past issues:
One of them did not come with the Galaxy Apps store (Not the plays store), and that phone also experienced the DQA issue
Current issues:
If I turn on Fingerprint gestures, the fingerprint sensor will stop working, this was an issue I had from the day I got the phone and has continued even through the updates. Here's a thread I made about it a while ago : https://forum.xda-developers.com/galaxy-s8+/help/fingerprint-sensor-t3595614
My internal speaker has detached, or at least I think that is the issue, as sometimes when I am in a phone call and shake the phone just a little bit, it will either start making a weird buzz sound or completely cut off the sound. Shaking it again will fix it, that's why I think it's a physical issue. I haven't dropped my phone and just in case I ever do, I have a case and a screen protector on it, and neither of them (phone, case, screen protector) have any damage marks on them.
The Biggest Issue: Currently this is the most annoying bug I am experiencing is that whenever I go to lock screen and security in the setting app, it crashes the settings app. I also can't use the search function in the settings app, as it crashes the app withing a few seconds. The lock screen and security is the only menu in which I experience this, I am 99% sure this is due to me turning on Secure startup. I had it turned on a few days after I got the phone and it worked great, I had to turn it off once, about a month ago in order to get a quicker boot. After that I was experiencing issues turning it back on (meaning I turned it on, rebooted the phone and it would not work) , after some persistence, I was able to get it to work and it has worked and still works.
One thing to mention is that I had done the most recent system update, I am not sure this issue was caused by at, since the inability so search in the setting menu has happened prior to the latest update.
I have tried everything other than a full factory reset (wiping all cache, wiping apps cache, reset setting, reset network settings), which I refuse to do, It is absolutely unacceptable for me to pay this much for this phone and have so many issues with it, I have factory resetted my phone (Samsung's recommendation) in order to fix the first issue listed above, multiple times and it did not work.
At this point I really don't know what to do, Samsung support has been useless in this, I don't wish to replace my phone right now as I need it to much to even give up for one day, If anyone has any advice/fix other than factory resetting, I'll happily try it.
Thank you,
GGgamer16
Sounds like a factory reset is needed. I just tried all you mentioned with zero problems on the newest update w/ navbar options and experienced none of that. Speaker problem is most likely hardware related.
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
*Hooligan* said:
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
Click to expand...
Click to collapse
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
brandonc0526 said:
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
Click to expand...
Click to collapse
Yeah I have tried changing channels. It didn't matter. I'm on 2.4 GHz.
I found a possible fix from another forum. I changed my wifi encryption from wpa2 AES/tkip to wpa2 tkip only last night and was rock solid after that point. I didn't have any more wifi issues... Just wanted to mention this change for other people. I usually got 5+disconnects every night. I'm gonna try just the AES option tonight and see how it acts.

Notification sounds stop working randomly - pixel XL android 8.1

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.

Categories

Resources