Hi, I have a Lex727 with eui s21 stock and when a notification arrive the screen don't turn on, I have to unlock with the fingerprint sensor to see the notification.
It any way to change that?
Hmm. Never heard of that problem. I'm on 20s. Maybe try some things from this thread: https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-past-notification-issue-eui-t3497530
You ought to switch to a custom ROM. eUI notifications are just royally screwed up in general.
sk8223 said:
Hmm. Never heard of that problem. I'm on 20s. Maybe try some things from this thread: https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-past-notification-issue-eui-t3497530
You ought to switch to a custom ROM. eUI notifications are just royally screwed up in general.
Click to expand...
Click to collapse
I already tried everything they say on that link and the notifications arrive but I have to turn on the screen to see them. I know that Android 6 does not bring ambient display but I thought that I could see the notifications without having to unlock the screen, my previous phone has Android 8 so I have to get used to this previous version.
Thanks for your help!!
Related
Bug fix ??
When updated to 4.4 on verizon I noticed that the screen doesnt lock or go back to the slide setting I set it to after a missed call. This is a headache because screen stays on, it makes me accidentally open apps and make calls, and runs battery fast because screen stays on. For those who have updated already does 4.4.2 fix this? Also is the lowest brightness still super high? Or did it get fixed back to how it was on 4.2.2? Thanks in advance.
...
You post your question, and then minutes later post ..... as if we don't care about you. Pipe-down, please.
To answer your question, I haven't had the issue you're saying. The screen locks back automatically on mine, and furthermore, the Active Notifications shows I've missed a call. Check your dialer settings, reboot your phone, and worst case scenario, FR the phone.
flacco40 said:
...
Click to expand...
Click to collapse
I cannot find a solution for this but the issue is when I miss a phone call when the phone is in my pocket, it automatically unlocks, and drains my battery.
I'm running 4.4.2 rooted on my AT&T Moto X, and I thought 4.4.2 would fix it. I do not have a screen lock
Any help is appreciated.
Thanks!
97vulcan said:
I cannot find a solution for this but the issue is when I miss a phone call when the phone is in my pocket, it automatically unlocks, and drains my battery.
I'm running 4.4.2 rooted on my AT&T Moto X, and I thought 4.4.2 would fix it. I do not have a screen lock
Any help is appreciated.
Thanks!
Click to expand...
Click to collapse
Hmm sounds like a strange issue...
You mean you don't have a screen pin/code/password, or that you don't have even the sliding unlock button?
Have a look in Settings > Display
What timeout do you have listed under sleep? The default is 30seconds, but it goes all the way up to 30min (which I would expect could definitely drain some battery...
Let us know and we may be able to help you further...
samwathegreat said:
Hmm sounds like a strange issue...
You mean you don't have a screen pin/code/password, or that you don't have even the sliding unlock button?
Have a look in Settings > Display
What timeout do you have listed under sleep? The default is 30seconds, but it goes all the way up to 30min (which I would expect could definitely drain some battery...
Let us know and we may be able to help you further...
Click to expand...
Click to collapse
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
97vulcan said:
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
Click to expand...
Click to collapse
Ok, that is definitely not normal. Are you BL unlocked, or are you using the Pie root exploit? Or Safestrap?
I would suggest flashing the entire 4.4.2 AT&T SBF file using the manual method as described in the Return to Stock thread:
DO NOT DO THIS IF YOU ARE USING SAFESTRAP
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 AT&T SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
As I seem to be telling people often, the only way to fix a corrupted filesystem (OR modifications made by previous exploits like Pwn/SlapMyMoto and MotoWpNoMo) is to flash the entire SBF file. Performing a "factory reset" cannot repair a damaged filesystem.
Often, it will fix ALL of your problems.
Good Luck
Did you install any apps, that plays with those settings after rooting?
thanks for the replies guys...I don't think so on the apps after root. IIRC, it did this before rooting the phone, so I thought it was a 4.4 issue.
it will unlock to the home page after every call, unless I answer, or ignore the call.
I'm using Xposed with these modules:
App Settings
GravityBox
HideCarrierMotoX
MinMinGuard
SoftkeysFadeMod
Twisty Switch
Xblast Tools
XPrivacy.
Again, I do not have a lock screen..when I try to enable one it does something funky with my electronic buttons, even after reboot. Not sure if it's because of SoftKeysFadeMod, or what..
I'm surprised others have not had this issue.
Thanks for you help.
97vulcan said:
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
Click to expand...
Click to collapse
May I ask if I understand correctly? You have no security setting, only active display enabled. If this is the case, this seems like normal behavior.
You screen turns on when you get a call, you don't answer. Until the screen time out kicks in, you see your home screen.
Once it goes dark, you should have an active display notification.
What Am i missing or what behavior are you expecting?
rtm1102 said:
May I ask if I understand correctly? You have no security setting, only active display enabled. If this is the case, this seems like normal behavior.
You screen turns on when you get a call, you don't answer. Until the screen time out kicks in, you see your home screen.
Once it goes dark, you should have an active display notification.
What Am i missing or what behavior are you expecting?
Click to expand...
Click to collapse
you pretty much hit it on the head...I was hoping the phone's display would not unlock to my desktop if I miss a call, but rather show the missed call on the active display.
I'm going to enable a security setting, and see if this changes the outcome.
Thanks
After enabling the swipe to unlock, I no longer have an issue with my phone unlocking when I miss a call. That seems to be the solution.
Thanks for your help
So for the last couple of days my HTC One M7 would recieve a notification and the screen would just stay on the entire time for no apparent reason. Im on latest OmniROM and its starting to bug me. Like for instance I get new mail on Gmail in the middle of the night. The screen turns on, it show the notification, and it doesnt turn off until I turn it off. If I restart, its fine for a few hours, but as soon as I get a notification, the problem reappears.
Nobody, seriously?
Sinistersky said:
Nobody, seriously?
Click to expand...
Click to collapse
Dude, you took less than 24 hours before bumping. Not everyone checks the forums regularly.
Also, per the FAQ, bug reports belong on jira.omnirom.org
However the behavior you describe is a feature in Omni. Let me guess - you turned on Active Display and forgot about it? (Since it's off by default, and the behavior you describe is not something I've ever seen on any device when AD was disabled.)
Entropy512 said:
Dude, you took less than 24 hours before bumping. Not everyone checks the forums regularly.
Also, per the FAQ, bug reports belong on jira.omnirom.org
However the behavior you describe is a feature in Omni. Let me guess - you turned on Active Display and forgot about it? (Since it's off by default, and the behavior you describe is not something I've ever seen on any device when AD was disabled.)
Click to expand...
Click to collapse
Nope.
Just to note, I am seeing the same thing on my nexus 5 running the 10/13 nightly. AD is disabled and I have never enabled it. I was wondering why sometimes I would pull my phone out of my pocket and the display would be on. Since reading this I have verified that this happens when I get a notification. I will submit a bug report on jira.omnirom.org.
eta: oops, I just realized you need an account for jira.omnirom.org.
VFO said:
Just to note, I am seeing the same thing on my nexus 5 running the 10/13 nightly. AD is disabled and I have never enabled it. I was wondering why sometimes I would pull my phone out of my pocket and the display would be on. Since reading this I have verified that this happens when I get a notification. I will submit a bug report on jira.omnirom.org.
eta: oops, I just realized you need an account for jira.omnirom.org.
Click to expand...
Click to collapse
This doesn't occur on any of my devices, including a Nexus 5.
Are you running some sort of notification customization app of some sort?
Define "screen on" - Lockscreen? Blank with backlight on?
Entropy512 said:
This doesn't occur on any of my devices, including a Nexus 5.
Are you running some sort of notification customization app of some sort?
Define "screen on" - Lockscreen? Blank with backlight on?
Click to expand...
Click to collapse
I am not running any notification customization apps just straight Omni nightlies. It happens with any notification that I receive. It goes to the lock screen and stays on until I unlock it. I am going to wipe and reinstall the ROM and try and determine if it's an app issue.
VFO said:
I am not running any notification customization apps just straight Omni nightlies. It happens with any notification that I receive. It goes to the lock screen and stays on until I unlock it. I am going to wipe and reinstall the ROM and try and determine if it's an app issue.
Click to expand...
Click to collapse
Do you have "screen stays on while charging" enabled? Even then, it shouldn't be turning on for a notification in the first place.
None of my devices turn on for a notification in any situation, and the screen always shuts off quickly (faster than the screen timeout setting) when it's at the lock screen unless "screen stays on when charging" is set in Developer Options.
With 6.1.1 I was able to stop notifications from turning on my screen. Since the update to 7.0, no matter what my settings, text messages (using Textra) always turn on the screen.
Does anybody know how to stop this?
Seems like I remember the exact same thing happened with my HTC A9 when it updated to 7.0 as well. But, I was able to stop it. For some reason, the Axon 7 will not stop, no matter what settings. Unless of course I'm missing something.
Thanks!
bubsnews said:
With 6.1.1 I was able to stop notifications from turning on my screen. Since the update to 7.0, no matter what my settings, text messages (using Textra) always turn on the screen.
Does anybody know how to stop this?
Seems like I remember the exact same thing happened with my HTC A9 when it updated to 7.0 as well. But, I was able to stop it. For some reason, the Axon 7 will not stop, no matter what settings. Unless of course I'm missing something.
Thanks!
Click to expand...
Click to collapse
I have the exact same issue. Posted on official Axon 7 forum but no help so far.
Has anyone else experienced sporadic notifications since updating to 8.1? Unrooted, and ever since the update, my notifications will only vibrate when the screen is off, but will go audible if the screens on.... or ill get a few hours of normal functionality, then back to whatever it wants to do... Ill get delayed text notifications or even doubling them up. Ive never had this issue before. Any help or direction would be greatly appreciated
Lemmiwinx said:
Has anyone else experienced sporadic notifications since updating to 8.1? Unrooted, and ever since the update, my notifications will only vibrate when the screen is off, but will go audible if the screens on.... or ill get a few hours of normal functionality, then back to whatever it wants to do... Ill get delayed text notifications or even doubling them up. Ive never had this issue before. Any help or direction would be greatly appreciated
Click to expand...
Click to collapse
I have the same issue. Orea 8.1 unrooted.
Have you tried removing the apps that need immediate notifications from battery optimization? Oreo is more aggressive stopping the background activity of apps than Nougat was. it's an intentional battery saving feature.
Lemmiwinx said:
Has anyone else experienced sporadic notifications since updating to 8.1? Unrooted, and ever since the update, my notifications will only vibrate when the screen is off, but will go audible if the screens on.... or ill get a few hours of normal functionality, then back to whatever it wants to do... Ill get delayed text notifications or even doubling them up. Ive never had this issue before. Any help or direction would be greatly appreciated
Click to expand...
Click to collapse
I've noticed this too, and literally just came on XDA to post this same question!!
It seems to take away notification sounds for most apps until I restart the phone. Based on the timing, maybe it has to do with going into a deeper sleep mode or something. Seems more like a glitch than a feature to me, since the notifications don't come back until I restart.
I'll try the battery optimization thing mentioned above, but I don't want WhatsApp draining my battery.
jhs39 said:
Have you tried removing the apps that need immediate notifications from battery optimization? Oreo is more aggressive stopping the background activity of apps than Nougat was. it's an intentional battery saving feature.
Click to expand...
Click to collapse
Good tip, Thanks. I was unaware they automatically optimized the apps for battery in the update. what a pain in the a$$. Ive changed the setting for messenger and telegram, Ill report back if i see an improvement.
Hmmm. I changed my battery optimization do exclude Google Voice and Android Messages... it worked for a small amount of time, now I just get vibration, but no sound for notifications.
Oreo 8.1 release.
Rick
I was using Nova Launcher when I had this issue. I switched to the default launcher and haven't had the issue since.
priyamjani said:
I was using Nova Launcher when I had this issue. I switched to the default launcher and haven't had the issue since.
Click to expand...
Click to collapse
The hero we needed