Related
Why my phone keep vibrate while screen off?
Google changed things around with 4.2. Now the phone will always vibrate on silent if it had a sound notification. From what I've heard, its not a bug.
Sent from my Nexus 4 using xda premium
KiNG OMaR said:
Google changed things around with 4.2. Now the phone will always vibrate on silent if it had a sound notification. From what I've heard, its not a bug.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That's a really terrible idea if this isn't a bug. The fact that it vibrates when I get new mail on my g-mail account is really bugging me. My g-mail is highly active and it vibrates every few minutes. I've tried everything and can't disable it. Really annoying.
Hi, i am not sure if this issue is just on my phone or if its a known issue at the moment thats affecting all android phones.
basically, i have downloaded bbm for android onto my s4, regardless of whether i have vibrate set to on or off my phone still always vibrates on getting a msg, is this happening with everyone elses?
thanks
james
Doesn't happen with me. Its proper for me.
Although I have never kept vibrate on since the beginning
Sent from my GT-I9500 using xda premium
did you check to see if your phone set to vibrate in app?
Oniyuri said:
did you check to see if your phone set to vibrate in app?
Click to expand...
Click to collapse
Yes it's set to off in the app
Yes.. At time my nexus simply loses its notification sounds.
Media sounds still works just the notifying sound disappears.
And after a reboot it works fine.
Its the 3rd time I've faced such bug.
Has anyone else faced such bug ?
Sent from my Nexus 6P using Tapatalk
So its only me who is facing this issue ?
Shall i factory reset my device ?
Any suggestion you guys want to give me ?
Sent from my Nexus 6P using Tapatalk
eefo said:
So its only me who is facing this issue ?
Shall i factory reset my device ?
Any suggestion you guys want to give me ?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I noticed same bug as well. You not the only one
Sent from my Nexus 6P
anglerstock said:
I noticed same bug as well. You not the only one
Sent from my Nexus 6P
Click to expand...
Click to collapse
just updated my device. let see what happens.
Sent from my Nexus 5 using Tapatalk
eefo said:
just updated my device. let see what happens.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I jsut received the update too. Will see how it goes.
anglerstock said:
I jsut received the update too. Will see how it goes.
Click to expand...
Click to collapse
I'm on version M and still having the same problem.
Count me in as well. Mine does the same thing. I wonder if it has to do with the doze features
Sent from my Nexus 6P using Tapatalk
I switched back to the stock messaging app today and so far it hasn't missed any notification sounds. It may have something to do with 3rd party apps not being optimized for marshmallow. I'm going to try and turn off battery optimization on my preferred messaging app and see if that helps.
murphyjasonc said:
I switched back to the stock messaging app today and so far it hasn't missed any notification sounds. It may have something to do with 3rd party apps not being optimized for marshmallow. I'm going to try and turn off battery optimization on my preferred messaging app and see if that helps.
Click to expand...
Click to collapse
But mine doesn't notify anything:/
WhatsApp, Viber, text messages, calls..
Nothing at all..
Were you in same situation or only messaging app was giving problem?
Sent from my Nexus 6P using Tapatalk
eefo said:
But mine doesn't notify anything:/
WhatsApp, Viber, text messages, calls..
Nothing at all..
Were you in same situation or only messaging app was giving problem?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yeah I have been having the same problem with the messenger app, Gmail, as well as my 3rd party apps... I also use a moto 360 and that won't notify me either so Idk what's going on... It's annoying though especially with text messages...
Sent from my Nexus 6P using XDA Free mobile app
eefo said:
But mine doesn't notify anything:/
WhatsApp, Viber, text messages, calls..
Nothing at all..
Were you in same situation or only messaging app was giving problem?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
For me it seems to be only 3rd party apps. Stock apps are coming through fine.
not sure if this will work for anyone else, but twice now i have had my notifications and alarms silenced. i figured out that both times it was after connecting to a bluetooth decice (once a speaker and once a ear bud) - even though i turned bluetooth off, and it showed as off, it was still trying to send the sounds to the bluetooth device. i turned bluetooth on and then off again and sounds worked.
I have the same issue, and I can confirm that it is bluetooth related for me as well. It seems to happen every time I connect with my car or my bluetooth earphones. I'd have to then turn off/on bluetooth or reboot to start getting audio for alarms and notifications.
FWIW, this doesn't seem to be the only bluetooth issue with this phone(or maybe Android M). I also have an issue with bluetooth causing wakelocks and preventing doze from kicking in (there's a thread on that as well).
I have the same issue and I think mine is related to bluetooth as well. After I started using a smartwatch that syncs with the phone via bluetooth, I started having the issue. Alarms, phone calls, messages etc don't lose sound. I have to turn the phone off and back on in order for notifications to work again. At times, sound from the keyboard of media works, but not notifications. At times media doesn't have any sound neither. I don't know if it's the Nexus 6P's problem or Android M's but this blows.
I'm having same issue but I don't use Bluetooth. Randomly lose all notification sounds. All stock apps, even ringtone and key sounds. Rebooting phone resolves it. But just now it's happened again, I then went into settings, sounds, and turned key sounds off then on again and bingo, all notification sounds are back to normal.
Sent from my Nexus 6P using Tapatalk
mickyw1980 said:
I'm having same issue but I don't use Bluetooth. Randomly lose all notification sounds. All stock apps, even ringtone and key sounds. Rebooting phone resolves it. But just now it's happened again, I then went into settings, sounds, and turned key sounds off then on again and bingo, all notification sounds are back to normal.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Same thing for me. I couldn't even go into system settings to modify the sound. It just hangs and eventually crashes. A reboot always fixes it. I did use bluetooth. Any notifications with vibration still vibrates though. Not rooted, or running exposed.
Just a quick update from my post earlier. Since I posted regarding my same issue I have since disabled the nexus imprint lock screen, which I had setup to unlock my phone, and a day has passed and all is good. Maybe a coincidence, I don't know but I've got all my notifications working as they should be.
Sent from my Nexus 6P using Tapatalk
Same issue here... This needs to be fix asap. Can't risk my alarm not having sound.
Snorbro said:
Same thing for me. I couldn't even go into system settings to modify the sound. It just hangs and eventually crashes. A reboot always fixes it. I did use bluetooth. Any notifications with vibration still vibrates though. Not rooted, or running exposed.
Click to expand...
Click to collapse
Update to my complaint, it still fails after sometime even when I don't use bluetooth.
Attached screenshot indicates it's related to the media storage permissions maybe?
This is pretty bad since I won't hear my calls or any other notifications!
Snorbro said:
Update to my complaint, it still fails after sometime even when I don't use bluetooth.
Attached screenshot indicates it's related to the media storage permissions maybe?
This is pretty bad since I won't hear my calls or any other notifications!
Click to expand...
Click to collapse
Same here. At first I thought it was related to bluetooth but after disabling bluetooth and rebooting the phone, getting notifications and the losing them again, I can say that the issue doesn't seem to be related to bluetooth.
I've missed alarms and of course calls and messages. This blows!
Using stock dialer, on Oreo. (Had the same problem on Nougat.)
When a call comes in, it does not allow me to answer the call. If I drag up on the ball for "answer", it simply bounces back. It won't "answer".
However, this only happens when the phone is "cold". After answering a call the phone answers normally for future calls
Any ideas?
This doesn't seem to be a dead spot in the touch screen, as I can suspend the ball at the apex for an indefinite time.
The problem seems to be that it doesn't trigger the "call answer". It isn't accepting it as an input.
This is repeatable, but once it has "answered" a call, it will generally answer the next few calls accurately.
I have the same thing on Nougat and Oreo too can be pretty annoying at times
Sent from my PH-1 using Tapatalk
Pucksr said:
Using stock dialer, on Oreo. (Had the same problem on Nougat.)
When a call comes in, it does not allow me to answer the call. If I drag up on the ball for "answer", it simply bounces back. It won't "answer".
However, this only happens when the phone is "cold". After answering a call the phone answers normally for future calls
Any ideas?
This doesn't seem to be a dead spot in the touch screen, as I can suspend the ball at the apex for an indefinite time.
The problem seems to be that it doesn't trigger the "call answer". It isn't accepting it as an input.
This is repeatable, but once it has "answered" a call, it will generally answer the next few calls accurately.
Click to expand...
Click to collapse
me too. very frustrating....thinking of buying a different phone.
Pucksr said:
Using stock dialer, on Oreo. (Had the same problem on Nougat.)
When a call comes in, it does not allow me to answer the call. If I drag up on the ball for "answer", it simply bounces back. It won't "answer".
However, this only happens when the phone is "cold". After answering a call the phone answers normally for future calls
Any ideas?
This doesn't seem to be a dead spot in the touch screen, as I can suspend the ball at the apex for an indefinite time.
The problem seems to be that it doesn't trigger the "call answer". It isn't accepting it as an input.
This is repeatable, but once it has "answered" a call, it will generally answer the next few calls accurately.
Click to expand...
Click to collapse
dandan2980 said:
I have the same thing on Nougat and Oreo too can be pretty annoying at times
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I am on T-Mobile and have not seen this happen. Any of you using WiFi Calling, if not try and see if it makes a difference.
Don't swipe up from the icon.
Swipe up from higher up, near the contact picture.
Just like the rest of the google apps, google doesn't use a proper viewport and the coordinates are messed up the essential phone.
Charkatak said:
I am on T-Mobile and have not seen this happen. Any of you using WiFi Calling, if not try and see if it makes a difference.
Click to expand...
Click to collapse
I'm on Metro Pcs which is on the same network as T-Mobile. Some times it takes like 3-4 swipes to get it answer sometimes on the first one and I've actually missed phone calls because it wouldn't answer
I'm not using WiFi calling either
Sent from my PH-1 using Tapatalk
dandan2980 said:
I'm on Metro Pcs which is on the same network as T-Mobile. Some times it takes like 3-4 swipes to get it answer sometimes on the first one and I've actually missed phone calls because it wouldn't answer
I'm not using WiFi calling either
Click to expand...
Click to collapse
This is my second headset and the first one was without this issue. If you have any one with another carrier, try their sim card. This is what I have done with another phone brand when there was an unrelated to your issue.
JCBomb said:
Don't swipe up from the icon.
Swipe up from higher up, near the contact picture.
Just like the rest of the google apps, google doesn't use a proper viewport and the coordinates are messed up the essential phone.
Click to expand...
Click to collapse
It works!! swipe up from near the contact picture.
thanks for the advice.
Pointmaine said:
It works!! swipe up from near the contact picture.
thanks for the advice.
Click to expand...
Click to collapse
Or anywhere in the middle of the screen: swipe up to answer or down to reject a call.
can't answer calls on oreo now
anyone got a fix or workaround ??
This happens to me too. Does the same thing to ignore. I also have problems where I can't hear the person for a good 30 seconds, even though it gives me the ringtone when the call is placed. Sprint says it's not on their end... I've pretty much decided to sell this.
Before this I had Moto G5 Plus which was highly rated as the best budget and it had a ton of issues too. I may buy an iPhone for the first time. I'm just tired of always having an issue with something on an Android device. I just want a product that works 100% of the time.
Pointmaine said:
anyone got a fix or workaround ??
Click to expand...
Click to collapse
I go home and the phone call should appear on the top, then I click answer to get the call
work around from essential
Pointmaine said:
anyone got a fix or workaround ??
Click to expand...
Click to collapse
If you start in the middle of the screen and swipe UP in short strokes, doe this resolve your issue.
I've seen this come up a few times on here and the subreddit and haven't had an issue answering or declining calls :S
Not sure why but after the last system update the phone will only come out of black screen sleep mode if I use the fingerprint sensor when theres an incoming call.
Any Ideas ?
This happened to me today too.
Hello, me too! Oreo Beta 2
Anyone ?
going_home said:
Anyone ?
Click to expand...
Click to collapse
Not me, I've never experienced this issue since I got the phone from N then updated to OB2, and now OB3.
Sounds like the proximity sensor may have an issue.
Do you have a screen protector or case?
I don't have that issue with a screen protector and Tudia case and B3.
It's a bug in the latest Google Dialer app. I fixed it be deinstalling the new version/updates then clearing cache and data in the dialer app. It's affecting the Pixel2 XL running 8.1 also. Fixed my issue and I won't let it install the newer dialer version from the play store
In Beta 3, I haven't experienced that problem. I did heavily on 7.1.1
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
going_home said:
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
Click to expand...
Click to collapse
happened to me last week too.. it only happened after I locked the phone, 5-10 minutes later incoming call or when unlocking the phone the phone shows back screen only for a few seconds then it went back to normal.
the problem went away after I turned off the bluetooth radio.
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
DrvLikHell said:
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
Click to expand...
Click to collapse
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
I tried two other dialers and it didn't make a difference on my phone. Drupe did work to make the screen show who's calling again, but wow, Drupe has too much.... just, everything. All I want in a dialer is basic functions in a standard format. Drupe is like a carnival of a dialer. I'll keep trying dialers though, since that one did work, maybe another one will too. Thanks for the suggestion.
Yeah, if you just take the Drupe dialer phone icon and put that on your home screen, whenever you select it you'll go right to the normal looking dialer. :good:You may want to try ExDialer. That used to be one I'd use a lot.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Sent from my PH-1 using Tapatalk
rignfool said:
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Click to expand...
Click to collapse
10 million downloads...good enough for me. I've used it for a long time and it's been better for me than the stock dialer. Just my opinion, no one has to use it but it sure beats a black screen when the phone rings.
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Sent from my Pixel 2 XL using Tapatalk
I read about some people being able to fix it by uninstalling dialer updates. Unfortunately, the Essential doesn't have any to uninstall. I'm working around it by using Drupe as my default dialer, but setting the stock dialer as the default app for dialing, if that makes any sense (When an event pops up that requires the dialer, it asks which dialer to use, I selected the stock dialer and told it always use that.) This way incoming calls trigger Drupe, which acts the way it's supposed to on Bluetooth, but I can still use the stock app for making calls and missed calls and such.
bricky23 said:
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Click to expand...
Click to collapse
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Jank4AU said:
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Click to expand...
Click to collapse
My volume buttons always work fine, BT or otherwise. Stock 7.1.1. Your issue could very well be related to OB3. I had a little bit of an issue connecting/reconnecting to some BT devices at first, but not lately, so it must have been fixed in the last few patches.