This has been an age-old issue on multiple devices and still can't find a solution.
When the screen is unlocked the display is dim to a very low brightness hardly enough to use for a few seconds, roughly about 5s, and it turns on to the normal brightness. I find this issue reported to have been occurring since 2105? or earlier on phones from OnePlus and others.
I have Nova launcher as default, altered it's settings, just in case, in vain. After tinkering with many options in the settings i couldn't find a proper solution. Then I found that after the phone is booted, the problem didn't occur for some time, under a minute. So i Disabled multiple apps from startup, yet, nothing changed. It was also noted that the display was not fully dim though, whilst the home screen was dim, the status and the notification drop down stayed lit with normal brightness. Afterall, it seems the fingerprint might the thing causing the issue that the phone doesn't show a problem when screen unlock is performed via other methods like pin. Apparently, it's all BBK phones that's having this issue? Even though this is not a big problem, the experience is pretty annoying. And, it wasn't there when i first used the phone.
So, is there a workaround for this issue other than disabling fingerprint or using other login methods? Or could it be a bug that's to be resolved in an OS update? Any help is appreciated.
Edit: vivo pushed an OTA update today, and after installing that, it seems the issue has been resolved. There's no mention of such an issue in the bugs fix list, let's still assume it was a bug.
Edit 2: Well, the problem persists (also deleted attached image of update which did not help resolve the issue).
daftdrift said:
This has been an age-old issue on multiple devices and still can't find a solution.
When the screen is unlocked the display is dim to a very low brightness hardly enough to use for a few seconds, roughly about 5s, and it turns on to the normal brightness. I find this issue reported to have been occurring since 2105? or earlier on phones from OnePlus and others.
I have Nova launcher as default, altered it's settings, just in case, in vain. After tinkering with many options in the settings i couldn't find a proper solution. Then I found that after the phone is booted, the problem didn't occur for some time, under a minute. So i Disabled multiple apps from startup, yet, nothing changed. It was also noted that the display was not fully dim though, whilst the home screen was dim, the status and the notification drop down stayed lit with normal brightness. Afterall, it seems the fingerprint might the thing causing the issue that the phone doesn't show a problem when screen unlock is performed via other methods like pin. Apparently, it's all BBK phones that's having this issue? Even though this is not a big problem, the experience is pretty annoying. And, it wasn't there when i first used the phone.
So, is there a workaround for this issue other than disabling fingerprint or using other login methods? Or could it be a bug that's to be resolved in an OS update? Any help is appreciated.
Click to expand...
Click to collapse
Just try NOT to set auto brightness ON and see things can improve.
rnjsx100 said:
Just try NOT to set auto brightness ON and see things can improve.
Click to expand...
Click to collapse
Sorry i did not mention I did try that method in the first place of all. We could tell it isn't the auto brightness causing the issue if the status bar and notifications are displaying in normal brightness.
The issue was resolved with an update.
Edit: not really. Sick.
Related
Off late I'm noticing that whenever I turn on the display, it goes completely bright for maybe 5 seconds before adaptive brightness kicks in. Today I completely reset my phone and reflashed the latest factory image (MRA58R, I was on MRA58N previously). It was fine for a while (for a few hours) and now it has started behaving the same way. It works fine if I turn off adaptive display. This happens 90% of the time.
Has anyone else faced this?
---
I have filed a bug report, please star it.
https://code.google.com/p/android/issues/detail?id=196048
I've got the same issue on 6.0 stock not rooted. I've been fiddling around with lux trying to get it to stop going to max bright in low light settings... And it seems that the light sensor is getting incorrect readings in low light and it takes a few seconds for the sensor to start showing accurate levels for the light conditions. I would love to have adaptive brightness work as it used to - don't know what changed.
Same issue here.
Woah. I'm not alone. So for all you guys, it started just recently?
yeah. I noticed it a little less than a week ago
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
foxnutz said:
yeah. I noticed it a little less than a week ago
Click to expand...
Click to collapse
Hmm. Same here. Started last week. Will have to dig out what the root cause is.
altimax98 said:
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
Click to expand...
Click to collapse
Nope. I'm running completely stock, no root, even locked bootloader (for device protection feature).
I am running completely stock marshmallow no root, boot loader is locked, no gravity box. Same problem.
Is there any program we can use to monitor the readings at the light sensor is receiving?
I have tried two apps but that doesn't seem to gather data while running in background; only works when the app is opened. Still trying to find one that does background logging.
I have the same issue.
And I thought it was Gravity Box.... now I wonder if it's the November patch? Since there is report from people who never root and using stock?
Ok, so I found an app that can log data while in background. It's called Androsensor. It also has a companion app (Androsensor Keep Awake) which helps to hold a wakelock to gather more data. I tried it and I feel it's definitely not the sensor or it's driver/binary malfunctioning, it seems to be reporting proper values. Maybe more people can try it and report back.
i just bought my phone (brand new) update it right away to 6.0 and used it and having thesame issue!
that means this is google firmware problem!
The reason I believed it to be the sensor was because I used lux to try and fix this and noticed when the bug was occurring, as the screen just turned on and went to max brightness, lux showed the values from the sensor above 20000. Oddly enough if I had lux update every 3 sec it would sometimes capture the actual light levels on the second update and adjust accordingly. I'll check out the app you mentioned and see what shakes out.
I'm having it too, also completely stock and unrooted, first noticed it a few days ago. A friend of mine also has it. He is also stock, I'm not sure about his root status though.
Ok got some interesting results this morning using androsensor. First of all I was unable to recreate the bug while using the keep awake helper app... Which leads me to believe that there may be some issue with the sensor values being calculated/averaged by the autobrightness code/program as the device wakes up from sleep. perhaps android is shutting off the light sensor when the device goes to sleep and this causes a reset? So it appears that it's not getting wrong values rather, that the data being drawn from the sensor is reset or perhaps recalculated as the device wakes back up. Almost as if it can't remember the last light level that was observed. I uninstalled the wake lock helper and was able to recreate the bug by letting the device "sleep" (leaving the screen off for maybe 5 seconds). So while the sensor showed readings of 2 lux the screen brightness was increased erroneously until the auto brightness refreshed and then after a few updates on the sensor the correct brightness was applied to the screen. Curious results. Can anyone else try to recreate the bug using androsensor and the wakelock helper program? I'm hoping I didn't run into some user error there.
I too tried without the wakelock helper and got the same result which made me believe it's not the sensor that's causing it. Will try the same with the helper app and report back.
Just tried Androsensor with the helper and I was unable to reproduce the bug, exactly what foxnutz faced.
Alright so we got some results! Just for the sake of being thorough, can anyone else replicate these results that andr0idfreak and myself saw? It seems holding a wakelock on the sensor stops this bug.
Now where do we go from here? It's been an awfully long time since I've done anything with logcat... But I think that may be our best bet to find out what's really going on here. I'll have to do some homework before proceeding. Will report back.
I think we should file a bug report here.
https://code.google.com/p/android/issues/list
I think a bug report is probably worthwhile. I thought it was some combo of xposed and gravitybox as well but I flashed my stock system back and it's doing the same thing.
So after this much anticipated Oreo release, my display has been left faded looking. It's as though you have the brightness turned all the way up which washes out the color, but even when it's turned down. It's rather frustrating & sRGB is not ticked. Please tell me this isn't the new display & what I could possibly do to change it.
Edit: Also just realized when I change my screen mode in display settings, nothing happens. I can even turn the red, green and blue all the way down with no effect. Anyone else experiencing this issue with Oreo?
Have to say no, that has not happened for me. Display looks the same and changing display settings changes the screen for me. Perhaps a reboot might help...
Do a Full reset, sounds like the ota bugged your settings out.
I've been on Oreo since the release and haven't had any issues with screen color or resolution.
Did you proceed to do the above posted steps? I myself would also say to factory reset the system.
If so, would you mind letting us know how it went and if it fixed the issue at hand.
The only place I've noticed something like this, is when using Google Maps through Android Auto, with my Vehicles display. I get the faded or Ghosting on the display. If I change from maps, to phone and back to maps it's fine again. But it's only temporary. This all started after I got the Oreo update. I'm still actively troubleshooting to find out if the cable is the problem or if it's related to the phone.
after 2 resets im good. started device as new and bo restoration of apps/go from there
Hi everyone,
Got my Pixel 4 XL on the 23rd and been playing around with it since then. I am now settling into a rhythm and noticed a very concerning glitch with the display when the phone is in dark mode. Basically, when the phone is in dark mode I noticed that typing in Gboard or tapping anywhere on screen in apps that are not pure black (such as Messages, Phone, etc.) will shift the screen colour from blueish-black to greenish-black. This happens every time, even after rebooting the device. There is no visible colour shifting in apps that use pure-black such as Settings (however, parts of Settings like the search bar that are the "gray" dark colour also shift). Once I noticed this happening now I cannot stop noticing it everywhere. I am looking to find out from you whether you are seeing the same thing or whether this may be a device problem. Note that the same issue shows up in dark apps even if dark mode is not enabled. It also has nothing to do with Ambient EQ, Automatic Brightness, or anything else of similar nature. Occasionally the problem stops, but if I pull up Gboard and start typing (say to search in the Recent section of the phone app) the problem immediately comes back.
I am looking for serious feedback here from those willing to look closely. This does seem like a software glitch to me, rather than hardware, especially since I am not seeing this behaviour with any other colours and so far it definitely has something to do with physical interaction with the screen when tapping on it. As I said, it also seems to be universally triggered by Gboard when in apps running in dark mode.
I appreciate any feedback you can provide.
Edit: Looks like what I'm observing is related to the switching colour profiles when the display is going back and forth between 60Hz and 90Hz. Turning off the smooth display function or forcing the display into permanent 90Hz mode appears to stop the problem from happening. Google really messed this one up. I hope their 90Hz fix they promised clears up this issue. Very annoyed ?
Thanks,
Dejan
Btw, since you are using forced 90hz display make sure to have always on display on. If you don't your greys will be purple and lower brightness as well as lots of black smear/crush. I don't know how turning on always on display solved that issue (someone posted this fix in another thread). So it indeed doesn't seem to be hardware but software related and hopefully they will tune this over time.
zetsumeikuro said:
Btw, since you are using forced 90hz display make sure to have always on display on. If you don't your greys will be purple and lower brightness as well as lots of black smear/crush. I don't know how turning on always on display solved that issue (someone posted this fix in another thread). So it indeed doesn't seem to be hardware but software related and hopefully they will tune this over time.
Click to expand...
Click to collapse
Yeah, I saw that thread. Some funky stuff going on with display calibration and 90Hz. Since I know that the HW is not defective and the SW is the source of the issue I am less bothered now (I cannot stand exchanging HW). I haven't specifically observed that effect on my phone and while I did try forcing 90Hz, I actually went back to the stock setting since I noticed that forced 90Hz further sucked down the battery that already is not particularly stellar despite this being the XL version. I presume Google will refine the 90Hz calibration and function over the next few months. I will say though that I am a bit confused why they need to have different calibration at different refresh rates. I calibrate all of my desktop monitors and despite the fact that I have a 100Hz monitor I never have to change calibration with refresh rate. Maybe an OLED thing :shrug:
dhorgas said:
Hi everyone,
Got my Pixel 4 XL on the 23rd and been playing around with it since then. I am now settling into a rhythm and noticed a very concerning glitch with the display when the phone is in dark mode. Basically, when the phone is in dark mode I noticed that typing in Gboard or tapping anywhere on screen in apps that are not pure black (such as Messages, Phone, etc.) will shift the screen colour from blueish-black to greenish-black. This happens every time, even after rebooting the device. There is no visible colour shifting in apps that use pure-black such as Settings (however, parts of Settings like the search bar that are the "gray" dark colour also shift). Once I noticed this happening now I cannot stop noticing it everywhere. I am looking to find out from you whether you are seeing the same thing or whether this may be a device problem. Note that the same issue shows up in dark apps even if dark mode is not enabled. It also has nothing to do with Ambient EQ, Automatic Brightness, or anything else of similar nature. Occasionally the problem stops, but if I pull up Gboard and start typing (say to search in the Recent section of the phone app) the problem immediately comes back.
I am looking for serious feedback here from those willing to look closely. This does seem like a software glitch to me, rather than hardware, especially since I am not seeing this behaviour with any other colours and so far it definitely has something to do with physical interaction with the screen when tapping on it. As I said, it also seems to be universally triggered by Gboard when in apps running in dark mode.
I appreciate any feedback you can provide.
Edit: Looks like what I'm observing is related to the switching colour profiles when the display is going back and forth between 60Hz and 90Hz. Turning off the smooth display function or forcing the display into permanent 90Hz mode appears to stop the problem from happening. Google really messed this one up. I hope their 90Hz fix they promised clears up this issue. Very annoyed ?
Thanks,
Dejan
Click to expand...
Click to collapse
I just noticed this on my pixel 4 xl tonight. But It only happens when the proximity sensor is triggered. Ex: like after making a phone call except it made everything on the screen seem over saturated on the screen and well as the same color shift you had stated. It seems to go away once I lock the device and unlock it again. It did it with smooth display on and off as well as force 90hz on and off.
There are a couple threads discussing this. Here's one of them:
https://forum.xda-developers.com/pixel-4-xl/how-to/smooth-display-colour-issues-t4000087
And another:
https://forum.xda-developers.com/showthread.php?t=3998907
Sent from my Pixel 4 XL using Tapatalk
Hi,
I have a Problem with my mi8.
The Display flash
https://youtu.be/cLJ4-46QTsI
I think its a Hardware Problem
What you think ?
toniq1 said:
Hi,
I have a Problem with my mi8.
The Display flash
I think its a Hardware Problem
What you think ?
Click to expand...
Click to collapse
Turn off aod
Aod ?
toniq1 said:
Aod ?
Click to expand...
Click to collapse
Always on display. Sametimes it's help but it's probably fault of ambient light sensor or screen.
It is the same If aod Off
Not good
That's a common thing with faulty oled screens, it is a hardware issue
I have the same flashing screen when I turn the screen off before the aod is displayed. It does not happen all the time. Turning off aod does not help. I doubt that it is a hardware issue as the flashing started after updating to MIUI 11 - at least for me.
I have also this problem, started a while ago when I was on MIUI 10 after I installed some kind of dark theme
This indeed looks like a AOD fault cause turning it off solves the problem, and the latest version of AOD with custom picture customization, reduced this issue for me
But it also seems like it mostly happens when the ambient light is low so the automatic brightness reduces the screen light and AOD starts to flash
I hope it won't be a hardware problem
One other thing that I want to mention is sometimes it goes really bad and the screen starts flashing for a long time, in this case phone seems to become unresponsive as not touch and not the fingerprint sensor and infrared camera doesn't work at all
navzahed said:
I have also this problem, started a while ago when I was on MIUI 10 after I installed some kind of dark theme
This indeed looks like a AOD fault cause turning it off solves the problem, and the latest version of AOD with custom picture customization, reduced this issue for me
But it also seems like it mostly happens when the ambient light is low so the automatic brightness reduces the screen light and AOD starts to flash
I hope it won't be a hardware problem
One other thing that I want to mention is sometimes it goes really bad and the screen starts flashing for a long time, in this case phone seems to become unresponsive as not touch and not the fingerprint sensor and infrared camera doesn't work at all
Click to expand...
Click to collapse
ago是什么意思
beibei2 said:
ago是什么意思
Click to expand...
Click to collapse
It is used for past time if you're asking
So a little update on the flashing screen situation
I disabled auto brightness and set the brightness a little below middle of brightness bar and so far so good. No flashing here for a while
Also disabling the AOD completely solves the problem
Another update on the state of this flashing issue, after Android 10 update haven't seen any flashing so far, AOD display works fine, light sensor and automatic brightness work just fine.
I guess it was a software issue after all
I hope you have solved it. Do you have the anti-flick on?
Nikos kouk said:
I hope you have solved it. Do you have the anti-flick on?
Click to expand...
Click to collapse
Nope I don't
Anyone else who has this issue:
Try disabling hardware overlays in developer options, also check to see if the Game driver option within Developer options is set to default. Although its possible that this could be the beginnings of a hardware issue, it could also be a software related issue.
If none of the things that I mentioned work, i would try reflashing the stock fastboot rom. ( must be fastboot version)
Similar happened to me but i think this is not recoverable.
https :// youtu(dot)be / u1dnIb9SoAw
No matter what i do, it only flashes and nothing else is visible. Device purchased about 1.5 years ago.
koudy66 said:
Similar happened to me but i think this is not recoverable.
https :// youtu(dot)be / u1dnIb9SoAw
No matter what i do, it only flashes and nothing else is visible. Device purchased about 1.5 years ago.
Click to expand...
Click to collapse
You need to return to stock using a fastboot rom, using a recovery rom will not work.
Most likely you have corrupted files. but sure it could be an hardware issue, especially if you have dropped the phone or installed something to increase the refresh rate. If you flashed a refresh rate mod, then you need to flash the DBTO image from the fastboot stock rom.
tsongming said:
You need to return to stock using a fastboot rom, using a recovery rom will not work.
Most likely you have corrupted files. but sure it could be an hardware issue, especially if you have dropped the phone or installed something to increase the refresh rate. If you flashed a refresh rate mod, then you need to flash the DBTO image from the fastboot stock rom.
Click to expand...
Click to collapse
I have TWRP installed and thought of checking it out but it simply flashes there as well. Right now i have the display on, set never sleep in Developer options and simply keeping it up until new phone arrives. Once i am on new phone, i will try factory reset on this first and go from there i think. Not sure how to get to fastboot when display is not working.
Due to such weird nature that nothing really helps i tend to think that this is HW issue.
EDIT : Turned off display by accident (because phone call happened) and now it's back to flashing disco with absolutely nothing working. Fastboot (power + lower volume key together) is of course flashing as well so inacessible.
Happened to me too. Turned off AoD, restarted, turned on and it was ok for a while. Now flashed again. Dont know what is causing this :/
Odesláno z mého MI 8 pomocí Tapatalk
I also got the same issue on my dipper. The only solution that works perfect is by flashing to LineageOS 17.1. I know it's an OLED screen faulty but Lineage really fixes it. Been using Lineage for a few months and never have this display issue again. Other custom ROMs can't fix this display issue.
Hello XDA Community,
I'm seeking assistance with a peculiar problem I've been encountering with my OnePlus 10 Pro.
The issue manifests as a persistent black clock display whenever the phone is locked. This display seems to prevent the screen from turning off as it should when the device is not in use. This not only affects the phone's battery life but also my overall user experience.
Additionally, I've observed a concerning correlation between this black clock screen and the device's charging speed. When the black clock screen is active, my OnePlus 10 Pro doesn't seem to charge at the speed I've come to expect from this device. This is particularly problematic as I rely heavily on the phone's acclaimed quick charging feature.
Has anyone else encountered this issue or can offer any advice? I would greatly appreciate any insights or potential solutions.
This screen is probably "ambient display" but on screen option I have disabled this in Wallpapers & style and always-on display is disabled.
Thank you in advance for your help.
I have had this with the fingerprint button showing after the screen is off, I got around it by turning it on then rebooting and retesting then changing the feature to off and then rebooting then testing again...
The problem occured after a firmware update, so if you've changed region or performed an update then that may be why.
Definitely something that shouldn't be happening.
I don't have "wise charging" turned on or wireless charging, or any kind of AOD feature, cycling and rebooting between each change should help, least it did for me.
I google this case and this can be ambient display by google but I dont have any option to disable it
meliorus said:
I google this case and this can be ambient display by google but I dont have any option to disable it
Click to expand...
Click to collapse
Again, just cycle AOD to on then reboot.. then turn it off then reboot.
Then retest.
It simply shouldn't be on at all, so did you update recently?
dladz said:
Again, just cycle AOD to on then reboot.. then turn it off then reboot.
Then retest.
It simply shouldn't be on at all, so did you update recently?
Click to expand...
Click to collapse
I try this but this not working.... Someone in internet communities notify about this is latest update bug...
One plus is sux ...
meliorus said:
I try this but this not working.... Someone in internet communities notify about this is latest update bug...
One plus is sux ...
Click to expand...
Click to collapse
Weird, I don't have it.
Factory wipe if needed...should work.