Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)
Frans1897 said:
Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)
Click to expand...
Click to collapse
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?
xprzs said:
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?
Click to expand...
Click to collapse
Hey! Thanks for the answer, I can confirm we have the exact same issue. I also have the same brightness issue you described
Anyway, I have always used fingerprint unlock though so I don't know what to answer you.. I only recently noticed the weird behavior. I did a couple things to test and I found out that enabling the "fingerprint" icon showing in the always on display seems to "fix" the issue of the flicker but not the one of the brightness change (after enabling it i've yet to see the problem occur), you should try it and let me know if you see any improvement. It's probably on samsung's end though and hopefully we get it fixed with android 10 or earlier
I'll take this chance to ask you another question; two weeks ago I received a software update and ever since that day I noticed my battery to be lasting waaaay less than it used to, did you update your phone as well? Did you notice a battery drain?
I have the issue both of you talking about.
hello, I had this same issue and what I did was turn the phone off, and booting it up while pressing "Volume Up", after entering a black screen with many options, I selected wipe cache. It has worked without a flaw since then. There's lots of bugs with this phone. I recently had a problem where the USB port will detect a device and "plugged and unplugged" it, making my phone unable to dim. Thankfully I was helpful.
Related
first i thought it was launcher pro's fault, but after changing launcher and rom release i'm pretty sure it's something else i haven't tracked down yet.
just after a reboot phone works as usual: screen lock runs after 30 seconds or by clicking the power button
after a while (days or even hours sometimes), the screen lock does not kick-in anymore: the screen just turns off and when you press the power button the phone is already unlocked.
i noticed that when the phone is in this "lock-bug" mode the notification led constantly shows a faint red light (you can barely notice it in the dark because it's really faint).
tested with:
launcher pro
go launcher
factory rom 2.21
blurless 2.34
I used to have the faint red light on after flashing a new rom.
It disapeared after I changed display setting to not automatic brightness.
It seems that the faint red light is the light sensor.
But I know nothing about your screen lock problem.
I have run into the same thing. I have not yet noticed the light, but I've had the screen lock stop working on my phone twice (I bought 3 phones 5 days ago for work). Like you, a simple reboot fixed the problem. I also tried toggling screen lock in the settings, and setting up a lock code, to see if the screen lock would start up. Both of my times, the first I noticed the issue was when I received a phone call and didn't have to swipe to answer, but that could have just been coincidence.
It isn't really a big deal for me or the employees, but it is a nuisance.
Happened to me as well, twice. First time it was just annoying that I had to reboot, second time it drained the s**t out of my battery in three hours.
So it's a bug allright.
Sent from my MB525 using Tapatalk
same here.. it just stops working.. any fixes yet?
This bug deserved a new thread.
If you've updated your phone to cm12, 5.0.2 then DO NOT DO THE FOLLOWING:
1. in Settings>Display and lights DO NOT keep "Adaptive Brightness" and "Color Enhancement" switched on at the same time. If you do, and then EVER try to manually reduce the screen brightness to minimum, YOUR SCREEN WILL BO BLANK. PERMANENTLY. Not kidding.
AND IT WILL NOT RETURN TO WORKING CONDITION without a factory reset.
Things that won't work:
1. Pulling out the battery and trying to reboot it. Nope. Been there, done that.
Hope CM takes note of this.
AS a Public Service.....
AyanReborn said:
This bug deserved a new thread.
If you've updated your phone to cm12, 5.0.2 then DO NOT DO THE FOLLOWING:
1. in Settings>Display and lights DO NOT keep "Adaptive Brightness" and "Color Enhancement" switched on at the same time. If you do, and then EVER try to manually reduce the screen brightness to minimum, YOUR SCREEN WILL BO BLANK. PERMANENTLY. Not kidding.
AND IT WILL NOT RETURN TO WORKING CONDITION without a factory reset.
Things that won't work:
1. Pulling out the battery and trying to reboot it. Nope. Been there, done that.
Hope CM takes note of this.
AS a Public Service.....
Click to expand...
Click to collapse
This happened to you???
yep. Currently using the phone without color enhancement enabled.
yesterday I faced the same problem
Yesterday My screen became black as I have enabled adaptive display & color correction it was not immediately it became black after 5 to 6 hours later after I set the setting & it was not displaying any thing I tried removing battery but it did not got fix.I did clear cache & factory reset then it started back.
Then you guys can do bug report to CYANOGENMODE or Here YU Forums
Got Hard Bricked no fastboot just dead thn join this petition
https://www.change.org/p/yu-yureka-provide-customer-care-service
Cure for it
well i have experienced it. but to avoid it you can choose the option
setting>status bar> and check Adjust brightness by sliding across the status bar.
so whenever the screen turned off you can swipe on the top from left to right so that brightness can be adjusted again!
you dont have to reset your phone.
AyanReborn said:
This bug deserved a new thread.
If you've updated your phone to cm12, 5.0.2 then DO NOT DO THE FOLLOWING:
1. in Settings>Display and lights DO NOT keep "Adaptive Brightness" and "Color Enhancement" switched on at the same time. If you do, and then EVER try to manually reduce the screen brightness to minimum, YOUR SCREEN WILL BO BLANK. PERMANENTLY. Not kidding.
AND IT WILL NOT RETURN TO WORKING CONDITION without a factory reset.
Things that won't work:
1. Pulling out the battery and trying to reboot it. Nope. Been there, done that.
Hope CM takes note of this.
AS a Public Service.....
Click to expand...
Click to collapse
I faced this today only.... screen went completely blank for a few sec, although I was not aware of this bug, but the brightness slider on status bar saved me....
So many bugs in this CM12.... huh...
and the screen off effects are gone as well after CM12 ugrade...
rahulbasu2013 said:
I faced this today only.... screen went completely blank for a few sec, although I was not aware of this bug, but the brightness slider on status bar saved me....
So many bugs in this CM12.... huh...
and the screen off effects are gone as well after CM12 ugrade...
Click to expand...
Click to collapse
Yupp ur right there is lots of bug in cm12..i didnt find any silent mode..there is only vibration mode is available..
kenil89 said:
Yupp ur right there is lots of bug in cm12..i didnt find any silent mode..there is only vibration mode is available..
Click to expand...
Click to collapse
ya silent mode not available... you have to go tosettings and uncheck the "vibrate to ring" option
even auto brightness dont work all the time... lollipop is really bad... not worth the upgrade...
---------- Post added at 06:11 AM ---------- Previous post was at 06:10 AM ----------
happened to me also.... I thought it was a problem with a theme... so i initially rated it 2 stars on play store, but after i saw it was a problem with cm, i went back and gave that theme a 5 star rating...
SOLUTION!!!!
It is still possible to take control over your phone in this situation. If your screen goes blank, this doesn't means that your phone has stopped working, the phone is still functional and you just have to find a way to increase the brightness. If you ever encounter this problem just swipe the screen twice from top to bottom to open the status bar and then slide your fingers on the screen where the brightness controller is present. This will surely solve your problem without any factory reset bull****. Please note that during this complete process the screen will remain blank. I have tested it a hundred times and it works 100%.
this works ... instead of factory reset
shamsiareeb said:
It is still possible to take control over your phone in this situation. If your screen goes blank, this doesn't means that your phone has stopped working, the phone is still functional and you just have to find a way to increase the brightness. If you ever encounter this problem just swipe the screen twice from top to bottom to open the status bar and then slide your fingers on the screen where the brightness controller is present. This will surely solve your problem without any factory reset bull****. Please note that during this complete process the screen will remain blank. I have tested it a hundred times and it works 100%.
Click to expand...
Click to collapse
Not fixed still
Please someone take this in lights to cynogen devlopers
how to set the display contrast
or colour enhancement
in yu yureka
Just install vysor in your pc and plug your phone to the pc. Now control your phone using your pc and increase the brightness same wy you reduced it. No need for any factory reset. Hope this helps.
you should Try this
Facing The Phone to Direct Sunlight or if in the night. face it near to the bulb. It will adapt light from the bulb and screen works then you can turn off adaptive brightness. That's works for me.
As many of you know, this annoying bug still isn't fixed in any AOSP rom for the G3 after all this time. For me, it's worse than the slightly worse camera issue, because after a few days, I always give up and go back to stock because it's really annoying when, for example, I have to make a call in a hurry and this happens, very frustrating.
Some findings about it:
- Doesn't happen in all the calls, seems to be random, but longer calls seem to produce the bug more frequently
- Enabling touch feedback in dev settings shows what the problem is: there's a ghost touch present on the screen (sometimes more than one) after taking the phone from our face, which makes it seem the screen is being pressed while it's not in reality
- Swiping the screen with 2-5 fingers in any direction makes those ghost stucked touches go away
- Brightness is decreased when this happens
Possible fixes I tried and none worked:
- Enable immersive mode for the dialer and disabling swiping on the status bar to change brightness - makes the brightness bug go away but not the stuck screen.
- Disabling proximity sensor in calls - works, but the screen is still on, sometimes I disconnect the call with my face by mistake.
- Some combination of llama or tasker profiles - Could work but I don't know how to. My solution would be "when in a call, and turn off and lock the screen - then, when we take the phone off our face, turn on and unlock the screen. This would theoretically work, don't know.
So, any ideas?
I seem to be having an issue with the screen turning on at random. I have Always-on screen set to ON and tilt-to-wake set to OFF, but the screen will turn on sometimes seemingly at random and multiple times in a row. I have done Factory Reset a couple of times and it does not help.
Is there anyone else with this occurance and is there a fix for it?
Sent from my VS980 4G using Tapatalk
I have this issue too. I've tried several configurations and it keeps doing it.
Sent from my SM-N910V using Tapatalk
Any apps that send a lot of notifications or any notifications that are automatically dismissed/very briefly show up? Can't think of anything else that would wake your watch.
No, not on mine.
Sent from my SM-N910V using Tapatalk
I have the exact same issue. At first I thought it was tilt-to-wake having poor gesture recognition so I turned it off. However I noticed without touching the screen it would turn on and then turn off after the stand-by time. To verify that was the case I left it sitting on my desk all day and observed that it would in fact randomly turn on and off. I also noticed that when the issue occurs the battery life decreases rapidly.
Also this issue will continue to occur even in theater mode.
Have you find a solution yet? My smartwatch 3 does the screen turn on randomly and then also touch screen issue occurs, and it makes random touches, swipes going into settings and so on, without touching the screen. I'am on the latest wear version mwd49b.
For more info search on youtube for my video about this problem: Sony SmartWatch 3 screen problem.
I recently began having the same problem. The screen does not turn off after it randomly turns on - I have to manually press the button to turn it off. Needless to say, this tend to run down the battery. I did a factory reset this morning, but the problem persists.
EDITING POST JULY 20:
After factory reset, I actually had the watch doubly connected to the phone, so I have corrected that now. However the problem with the random turn-ons began occurring well before the factory reset. I'm not sure what triggers it, or what stops it, but when it begins to happen, it drains the battery very quickly. The problem only began recently (within the past few weeks), so I'm not sure what changed to bring this on.
A bug in Android Alarm Clock keep the watch active after alarm ring. Just corrected yesterday by an update on Google Alarm/Clock app.
On the phone > android wear app > settings icon on top right > device settings (smartwatch 3) >tilt to wake set to off
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Not So Pro said:
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Click to expand...
Click to collapse
Is AOD on or off? What happens when it's on?
Badger50 said:
Is AOD on or off? What happens when it's on?
Click to expand...
Click to collapse
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Not So Pro said:
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Click to expand...
Click to collapse
Quite possibly so. I know nothing about snap face, snap chat, or whatever these social media apps do. Although, you may try clearing the app data and cache on said app to see if it helps. No guarantees though. As is the case with many things android! ??
I've had the same issue ever since I installed, I believe, the nav bar immersive mod. Not sure, around same time. I was able to hurt power button twice for camera and that would pull it up and u could switch back to screen. I don't have xposed or Snapchat, so I don't think either of those are it. It's random when it happens to me.
I've had similar issues. I'm not rooted and have never used Snapchat or AOD. I do use immersive mode for some apps so I've thought that might be causing it. Like stated above, I can get the screen to come on my double tap to open the camera or just holding the phone face down and tap the back a couple times then flip back over and the screen comes on.
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
shmity said:
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
Click to expand...
Click to collapse
Ok so a little more testing. When Ambient display is set to always on, I have no issue, maybe a slight lag when waking/unlocking. When ambient is set to tap or pick up i get issues, when ambient display is set to off at all times, i have no issue. Plugging the phone in to charge seems to force the issue to happen.
Edit: Seems that even with ambient display off totally the issue pops up. Strange thing is if i unlock the phone and take a screen shot, its totally black.
I to have this happen and like sportytony I use camera to wake device. Sometimes that too takes a bit. Most of the time when it finally does wake there will be a notification that systemui isn't responding. So I wonder if it's related.
Ok, I've been having this issue happen multiple times a day. I use this immersive app: https://play.google.com/store/apps/details?id=in.tsdo.elw
Since I have turned all ambient display options off and made sure that System UI is unchecked in the immersive app i haven't had an issue at all.
Its definitely related to system UI, com.android.systemui to be precise
i used to try to set up Power Nap on this device, but it can't find System UI in app list, make me unable to whitelist it, thus causing same issue like yours,
Screen wont turn on after sleep, since System UI wake up is blocked
I was using hide navbars and had this issue
I uninstalled and never had that problem again
Sent from my Google Pixel 2 XL using XDA Labs
Didn't expect all these replies but I'm going to try to untick system UI and see what happens. Thank you all!