Hey all! Anyone have an issue after hanging up from a call where the DND mode literally glitches on and off on and off.... Several times a second...
The icon just repeatedly flashes in my notification bar. Either rebooting the device or using my Asus Zen Watch 2 to turn DND off will cut it out. Anyone else see this type of issue?
Its been reset several times. Also now running Pure Nexus. It occurs on both stock and custom rom.
I know the "Server Unavailable" error when placing a call or answering is a known issue on these devices. This one tho I have not seen anything about it.
Thanks for any help guys!
same issue
Im having the same issue but im running a Nexus 6P 7.1.1 Dec Update and an ASUS Zenwatch 3
xxemoeskimoxx said:
Im having the same issue but im running a Nexus 6P 7.1.1 Dec Update and an ASUS Zenwatch 3
Click to expand...
Click to collapse
Have you noticed any difference while leaving the watch disconnected or powered off?
I didn't have the DND flashing on and off, but it would go into DND mode after almost every call. Someone suggested deleting the three default DND profiles in settings and that fixed it for me.
I have the same issue where the phone goes into DND mode after a call, thought it was just me.
JimSmith94 said:
I didn't have the DND flashing on and off, but it would go into DND mode after almost every call. Someone suggested deleting the three default DND profiles in settings and that fixed it for me.
Click to expand...
Click to collapse
Funny you say that! Last night I realized those profiles were there and deleted them. Will see if that fixes it.
Thanks for the help guys!
Glad were not the only ones seeing this.
if you hold down the volume button by accident it will turn on alarm only mode but turn it off by doing this I posted it here https://forum.xda-developers.com/pixel-xl/how-to/how-to-off-disturb-section-using-volume-t3598695
Related
At first I thought the rom I flashed on my GS2X was screwed so I flashed a stock rom and found the same was happening. Sometimes when a call comes in the phone does not ring and appears to be in silent mode when it is not?
Anyone know of some 'feature' that may be causing this?
jets76 said:
At first I thought the rom I flashed on my GS2X was screwed so I flashed a stock rom and found the same was happening. Sometimes when a call comes in the phone does not ring and appears to be in silent mode when it is not?
Anyone know of some 'feature' that may be causing this?
Click to expand...
Click to collapse
You could try something, and I know itl sound weird but,
Change your ringtone, I had it happen to me a few times when I tested some of the roms on here..
That usually helped for me.
Or simply to you have motion on? Lol if so turning it upside down mutes it lmfao
Go to settings>MOTION>turn over to mute xD
And if that is it, I'm not gonna pick on ye, my buddy was wining about the same thing couple months ago n it was that, he got it for a few weeks.. I had my fun..
Thanks. I use phoneweaver to automatically change ringers and volume levels based on location etc and I think the settings aren't 'sticking' properly. I have never had issues until now on this phone. I noticed when this app changes the screen brightness even though the new value is shown in settings it has not actually changed. Maybe the same thing was happening on the ringer? The last time a call came in with no ring I quickly rebooted without changes and it rang when I called the phone so who knows...
I'll test further.
I'm having issues, my phone goes into "Do Not Disturb" mode on it's own. I think it has something to do with the Android wear connection to my watch. I've reset the watch and checked to make sure it isn't set to turn on that mode. But still at random times my phone goes quiet. Curious to hear if anyone has had the same issue or a cure. Thanks!
yes i have the same issue with pixel xl & Huawei watch 🤔
Sent from my Pixel XL using XDA-Developers mobile app
I have the same issue as well. It also happens on calls.
It's a new feature in 7.1.1
You have to disable the automatic rules that are created in settings. I just deleted all the premade ones in there and my issue went away.
sassmk2 said:
You have to disable the automatic rules that are created in settings. I just deleted all the premade ones in there and my issue went away.
Click to expand...
Click to collapse
I have an Android Wear watch and have the same problem. Are you saying the deleting the built-in Weekend, Weeknight, and Event rules fixed it for you?
JimSmith94 said:
I have an Android Wear watch and have the same problem. Are you saying the deleting the built-in Weekend, Weeknight, and Event rules fixed it for you?
Click to expand...
Click to collapse
Yes, Fixed it for me
sassmk2 said:
Yes, Fixed it for me
Click to expand...
Click to collapse
Thanks, I just deleted mine, so we'll see if it helps me.
JimSmith94 said:
Thanks, I just deleted mine, so we'll see if it helps me.
Click to expand...
Click to collapse
I have done this too and my phone goes into DnD mode when I make or take phone calls. It becomes an issue when I get off the phone about 50% of the time it stays in DnD mode and I have to manually turn DnD mode off. Anyone found a work around for this yet?
I posted this to fix it. Its a hidden menu https://forum.xda-developers.com/pixel-xl/how-to/how-to-off-disturb-section-using-volume-t3598695
Has anyone solved this? My Pixel XL keeps turning DND on when I've manually turned it off. I do not use a smart watch or any other accessory. And I have already deleted the single Automatic Rule which I programmed (my phone didn't come with any pre-installed rules). I'm a doctor and keep missing super-important phone calls because my phone isn't ringing. (It's sitting in a cradle on my desk, charging -- so I know I'm not accidentally hitting the volume down button.)
Thanks!
Fitz
itfitz01 said:
Has anyone solved this? My Pixel XL keeps turning DND on when I've manually turned it off. I do not use a smart watch or any other accessory. And I have already deleted the single Automatic Rule which I programmed (my phone didn't come with any pre-installed rules). I'm a doctor and keep missing super-important phone calls because my phone isn't ringing. (It's sitting in a cradle on my desk, charging -- so I know I'm not accidentally hitting the volume down button.)
Thanks!
Fitz
Click to expand...
Click to collapse
The only sure fire way, if you're sure it's not an app you installed or setting you set, is to factory reset including wiping system OR flashing stock via fastboot. I mean technically if you had the time and you didn't wanna do all that you could boot the phone into safe mode, then wait and see if it does the same thing. If it doesn't , you know it's an app you have installed.
Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Maybe give a factory reset a go.
moralesd66 said:
Maybe give a factory reset a go.
Click to expand...
Click to collapse
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
tdetroit said:
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
Click to expand...
Click to collapse
Hard reset....As in power off and on right? Try booting into recovery mode and deleting cache and data.
tdetroit said:
Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Click to expand...
Click to collapse
My TMO one did that today, heard it ringing but screen remained off.
Sent from my SM-N950U using Tapatalk
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
tdetroit said:
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
Click to expand...
Click to collapse
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Maybe the setting for proximity...in pocket...turn off
Limeybastard said:
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
I've tossed the screen protector after 1 day because it kept making a clicking sound on the top corner. No case on it.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
tdetroit said:
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
Click to expand...
Click to collapse
Factory reset , if no go , replacement.
Sent from my SM-N950U using Tapatalk
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
tdetroit said:
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
Click to expand...
Click to collapse
they know absolutely **** about anything
I never use retail store
Another way to fix this is to call yourself on another phone while your Note 8 screen is on. When the call comes in, don't answer but slide down the notification bar and you will see your call. Adjust notifications to not block/be silent.
tdetroit said:
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
Click to expand...
Click to collapse
I went into Settings, Display, but nothing about double tap to wake-up. Samsung runs on AMOLED and that function is on other screens like Sony Xperias.
I do notice another thing going into Notifications settings and I see that the Phone app is Muted. I don't know how to get out of it.
The solution is the person who posted above. You call yourself, and swipe to unblock Silence notifications for your phone app. It's weird how it was set that way, but that's the best solution!
How do I unmute phone call notifications?
Thanks! My incomimg calls now appear on my screen!
I tired the unblock silence notifications and that still has not fixed it as well as a hard reset. Anyone else got any suggestions?
Thanks
Ian
Fix to dark screen on incoming call
Step 1: call youself
Step 2: swipe down on notification bar to view the call(usually how you would answer while dealing with this issue)
Step 3: swipe the call to the right and click the setting wheel.
Step 4: select "do not hide notifications"
Step 5: test call after doing this with the screen off, its should work.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
I turned "block accidental touches" off.
That worked for me!
THANKS
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
I agree surprised more are not annoyed...lol
Doublecore said:
Well it seems it's only happening when connected to Bluetooth. I hadn't noticed since I'm connected to my headset all day at work. Disconnected from Bluetooth and had my wife call me...screen popped right on. So it's another Bluetooth bug I guess.
Click to expand...
Click to collapse
I tested incoming phone calls with and without bluetooth, and came to the same result. Since it's very annoying for the screen to not turn on, I ended up making a macro with Macrodroid to turn the screen on when a call comes in. This workaround will be sufficient for me until Google fixes the bug.
I posted on this same issue last week. It's the last update to Google Phone app that broke this. I don't have the time to report it to them...so hopefully it gets fixed!
https://forum.xda-developers.com/pixel-2-xl/help/google-phone-update-bug-t3718424
*Edit- To fix(?), uninstall the phone app and it will remove the update. Should work then. Of course you won't be able to use Duo for video calling within the dialer...but I couldn't care less about that.
I just had this happen yesterday. Here is a work around with Tasker and Secure Task to wake screen on incoming call.
Import it in Profiles tab in Tasker and make sure you have Secure Task and have it configured with adb.
5150jpd said:
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
Click to expand...
Click to collapse
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Nope.. No protector on phone at all.
v12xke said:
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Click to expand...
Click to collapse
It started for me on the Google Phone update to version 15 on Dec. 14th. I never had this issue on 8.1 that I did the OTA sideload when I got my phone on Dec. 4.
My proximity sensor is fine. Even with always on display, AOD goes off in pocket and turns back on when I pull it out. On a phone call the screen blanks when I put it to my ear and wakes when I pull it away from my head.
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
jonstrong said:
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
Click to expand...
Click to collapse
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
JimSmith94 said:
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
Click to expand...
Click to collapse
Thanks. If this issue goes on much longer, I'll probably try that. Oddly enough, despite having played with custom Android ROMs and modding over the years, I never used Tasker -- concerned that having the add'l service(s) running in the background around the clock would be more of a battery drain.
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Is there a xposed module to disable the stupid proximity sensor? I'm having some issues with it. It does not wake my screen up when I pull it away from my face.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
JimSmith94 said:
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Click to expand...
Click to collapse
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Pkt_Lnt said:
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Click to expand...
Click to collapse
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
JimSmith94 said:
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
Click to expand...
Click to collapse
I can confirm V16 fixes the phone app and resolves this issue. It's being rolled out gradually, in waves. If you don't see the update on the Play Store, you can download it from APKmirror. Start here:
https://www.apkmirror.com/apk/google-inc/google-phone/
My issue is the exact opposite..
I answer a call on my bluetooth headset while the phone is in my pocket and buttons start being pressed so I have to take the phone out to lock the screen.
Any quick fixes on this issue?
I'm late to the party, but I fixed this on a Pixel 2 XL in our household. In the system's app settings I force stopped the phone app and cleared the app cache, then I disabled the "Flip to Shhh" feature in the phone app settings. If that fix works for you, please leave a reply so we can validate.
Hey,
My phone has been randomly vibrating as if I get a notification, which I don't. It will give 2 short vibrations. Last week it's been happening more often. Does anyone know how I could fix the problem?
Thanks!
jostaahh said:
Hey,
My phone has been randomly vibrating as if I get a notification, which I don't. It will give 2 short vibrations. Last week it's been happening more often. Does anyone know I could fix the problem?
Thanks!
Click to expand...
Click to collapse
Now that you mention it, I've had a couple of Phantom Notifications too. Once my phone vibrated while it was even in my hand but when I unlocked it there were no notifications. I went into settings and disabled vibration for a number of system apps and so far I haven't experienced the vibrations yet. It's hard to tell if I've actually fixed it, or if the timing's just random though.
NekoMichi said:
Now that you mention it, I've had a couple of Phantom Notifications too. Once my phone vibrated while it was even in my hand but when I unlocked it there were no notifications. I went into settings and disabled vibration for a number of system apps and so far I haven't experienced the vibrations yet. It's hard to tell if I've actually fixed it, or if the timing's just random though.
Click to expand...
Click to collapse
I had done that previously with some system apps, for a while it had gotten down. However, like I mentioned before, it had gotten a lot worse this week. I now turned off the sound and vibration for all (system) apps that I don't notifications from.
I'll let you know whether that fixes it or not.
Unfortunately, it didn't help