Does anyone else has a problem with ambient always on display not working? Most of the time it is there, but even if I turn off the Scheduler, sometimes off for hours, just the black screen. 10.3.10 MIUI
Yes, the same issue for me. Little annoying, but I hope it will be fixed in the next update. Maybe I will for now just turn off the always-on display.
You should read the description
Could you be more specific please?
"To reduce power consumption, items won't be displayed in the following situations:
1. When your device lies in dark for a long time.
2. When DND mode is on"
Haha, didn't saw that, but still, my room wasn't dark at all and it still went off. For now I have just disabled that option, and if that is only big bug I will be super happy.
Related
Hi,
i have a problem with my three days old HD. Besides the fact it seems to be much slower than it should be, the problem is the screen goes dim after a while. I'm not talking about it going black after a while, like it's supposed to, but in normal working mode it just kinda becomes darker, kinda like notebook screen goes a little dim when you unplug it from power. When i turn it on, it looks ok, but after a while, mostly after it first time goes black due to inactivity, the screen looks dimmed, no matter what i do, and after a few minutes it returns to normal, without any apparent reason, kinda random. At first i thought it might be something in HDTweak, so i did the factory reset, but it's happening again. Any ideas?
Try disabling the light sensor. It is supposed to adjust the screen brightness automatically, depending on the external light conditions. You can disable it in 'Energy', under Start -> Settings.
Well, it sort of works. When i disable the light sensor, i get the screen for adjusting the light on battery and AC. When i adjust the slider for battery, the screen lights up and it's ok. But, the moment the device locks itself (via HDTweak setting, the only thing i adjusted in HDTweak, it dims, and when i unlock it, it's still dimmed. Then when i again go into light sensor setting and press on the slider, it lights up. I don't understand what's going on. Faulty device maybe?
Also try changing the settings in the advanced tab.
Adding a minute or reducing a minute here seems to kickstart the device - and the annoying screen dimming goes away.
r
Andrew
Hi everyone
I want to share a workaround to all of us who owns a defective S5
Symptom: You unlock your phone and it doesn't show anything. Actually, the phone is working. Capacitive buttons light up and you may heard some activity in the phone
Your phone has a defective screen. There are a lot S5 which have this problem, according to several forums. After several tries, unlock and lock over and over, the screen light up and you are able to use your phone. The problem is when you receive a call and you want to know who is calling you, the screen doesn't illuminate and you won’t be able to know who is.
Here's a workaround which makes your powerful S5 usable and take out from your drawer.
Solution:
The more effective way to fix it is: change defective screen! But sometimes it could cost as much as a new phone, or simply you can't afford it, and it's better to change your phone instead, and you put your S5 in a drawer.
The technical explanation of this problem is: Screen doesn't receive enough electrical current at low brightness levels (maybe the flex is defective, get old, etc)
Most probably the wake up problem exist together with screen flicker at low brightness levels
The wake up problem rises up more in dark environment, when light sensor make low bright screen
The lock screen light up screen, with a dim effect: when you lock the phone, it slowly turn screen off, and when you unlock, it make and effect of dim screen.
When you are is in dark environment, the effect is very slow, preventing the screen illuminate because the technical problem explained before.
When you are in very light environment, you lock screen and sensor light make the screen very brilliant and chances are you defective phone wakes up correctly.
We can use an app which give us complete control over brightness subsystem. I use an app called Velis AutoBrightness:
Once installed from Play Store, it shows a Setting Wizard. Follow the instructions. Below are some notes
• 1/7: Welcome Screen
• 2/7: How bright... Most probably is your phone always have flicker in low brightness. Choose "AMOLED" or "AMOLED bright". By the way choosing any one of those cure always minimum brightness failure!
• 3/7: Choose High sensitivity
• 4/7: On, if you want additional brightness when charging. Irrelevant for this thead. Choose your favorite setting
• 5/7: Same of 4/7
• 6/7: Choose enable: That enable the app
• 7/7: Some additional notes: Press Done
Now important settings: go to Menu > Settings > General: Settings Mode > Advanced
Service Activation settings:
• Disable system handler > ON: When you use Power saving mode, you surely noted screen flicker, which is very annoying, and make unusable power saving mode. By set this ON: Android doesn't set screen too dim; instead Velis have a minimum of brightness set by Wizard 2/7. (Surely you find out that you avoid screen flicker, by setting autobrightness off and slider in 8-10%)
Sensors settings:
• Screen-on sensor value override: Set this value to 30000. Read below this post if you want technical explanation of this setting
After you establish these settings, you'll be able to unlock your phone all the time!
This is the trick: When you unlock your phone, you'll note that the screen is very bright (because Screen-on to 30000) and quickly adjust to the environment light. The failure is that electrical current to screen is defective, and when exterior light is dark, the screen make a dim effect and doesn't light up.
Note to Marshmallow users:
• This app make use of Screen overlay permisions: And marshmallow is very restrict with this kind of app. This is specially true when you are installing an app. All you have to do is deactivate the app in notification screen: press "OFF" button, adjust system brightness upper enough to not flicker the screen, install your app, and activate Velis Autobrightness again
• Because of Doze mode, wake up from this mode may avoid your screen light up, the first time you use your phone. Let 10-15 seconds your phone wake up, lock again, and unlock again, and velis will make its work!
I hope this post make your smartphone usable. I barely apply this trick to two phones, but I think this is a good workaround!
I used this app & the flickering is still available
What worked for me is downgrading the firmware on my g900f all the way back to Android 4.0. My phone came with version 5.0 and I noticed the problem only after I kept installing samsung's system updates. Will report if the problem starts up again but I'm running rooted and running nougat just fine so I don't see a reason to keep upgrading the firmware.
Edit: nevermind, this didn't work
Reyse said:
The technical explanation of this problem is: Screen doesn't receive enough electrical current at low brightness levels (maybe the flex is defective, get old, etc)
Click to expand...
Click to collapse
Does anyone know for sure if it's the flex cable or some capacitors? I notice only the lower half of my screen flickers.. I bet there's a simple electrical fix for it instead of replacing the whoooole display
fbs said:
Does anyone know for sure if it's the flex cable or some capacitors? I notice only the lower half of my screen flickers.. I bet there's a simple electrical fix for it instead of replacing the whoooole display
Click to expand...
Click to collapse
Hello,
Have you change jour battery? If it s old it could cause some issues...
But try to buy a genuine one, I think that your battery must be old now.
Bye
cedouic said:
Hello,
Have you change jour battery? If it s old it could cause some issues...
But try to buy a genuine one, I think that your battery must be old now.
Bye
Click to expand...
Click to collapse
it doesn't make any sense. the lower half of the screen flickers in green even on charger
fbs said:
it doesn't make any sense. the lower half of the screen flickers in green even on charger
Click to expand...
Click to collapse
I noticed that screen only flickers at low brightness when using Boeffla kernel for LOS14 and others based on it.
No issue for the same device with LOS or Stock based kernels.
zlazaar said:
I noticed that screen only flickers at low brightness when using Boeffla kernel for LOS14 and others based on it.
No issue for the same device with LOS or Stock based kernels.
Click to expand...
Click to collapse
you're wrong
I was using los16 with stock kernel for months with flicker everyday
fbs said:
you're wrong
I was using los16 with stock kernel for months with flicker everyday
Click to expand...
Click to collapse
+1 to that , i even went back to stock and the screen flicker appeared and such issues are well known already with samsung amoled panels back in 2014-even some panels from 2018 . So def not kernel related.
I was using los 15.1 and this problem got worse. The phone was barely usable as mentioned by the op. In my case, the screen would start flickering below 60%. Then I switched back to stock marshmallow. I noticed that 100% brightness in los 15.1 is actually only about 70% in the stock rom.
I have been using the phone at 80% brightness for some weeks now and the problem has significantly reduced. But not completely gone, it's much much better. Also, you might want to avoid using dark wallpapers.
I would take a video of this issue, but I don't have a good enough camera. It's really, really hard to capture unless you have good video recording tech, which I don't have. :crying:
My issue is that, when I set the brightness to its lowest level on my Zenfone 3, the screen starts flickering. This is especially noticeable with white backgrounds. You can tell that the screen is flickering (perhaps refreshing?) rapidly and it makes the phone painful to look at.
Someone actually created a thread about this issue here on XDA a few months ago, with a video showing this issue, but unfortunately, the video doesn't capture the flickering properly. Here: https://forum.xda-developers.com/zenfone-3/help/ze520kl-low-screen-light-level-20-t3603502
How to reproduce:
-Turn auto-brightness off
-Slide brightness bar all the way to the left (AKA to the lowest level)
-Open a white background/grayish background or blank page in Chrome
-Screen starts flickering
It happens across the phone, and intermittently. Sometimes it happens, sometimes it doesn't. In Chrome, in games, whatever. I once thought it could be related to charging the phone, but the screen has flickered on low brightness even when my phone wasn't plugged in, and at 70-80% battery. I might try resetting the phone to see if it's a software defect; I really hope it is.
Turning off hardware overlays in Developer Options does not resolve this issue.
I'm currently on ASUS stock Nougat, unrooted. I can't root right now. I don't have any screen overlays apart from CF.Lumen, which isn't set to come on during the day, when the flickering happens, and I don't use any screen color modes apart from the default settings. I also always have auto-brightness turned off.
Just wondering if anyone else is having this issue. I might try recording it one day.
Thanks.
Update 1: Removed my 64GB SD Card from the phone to see if that made a difference. It didn't. So the flickering isn't related to power management, AFAIK.
Next step is to wipe the phone completely, including its cache partition from stock recovery, and set the phone up as new again. It might be a hardware issue, but my fingers are crossed.
I've had this issue since I got the phone, ZE552KL. Turning off auto brightness fixes it for me, so I have a feeling it has more to do with ASUS' auto brightness algorithms than anything else.
sensi277 said:
I've had this issue since I got the phone, ZE552KL. Turning off auto brightness fixes it for me, so I have a feeling it has more to do with ASUS' auto brightness algorithms than anything else.
Click to expand...
Click to collapse
I always have auto-brightness turned off. I think it might have to do with the ambient light sensor. I've tested it using SMMI and it works just fine. But I wish there was a way to disable it, since I don't need it. I'm kind of disappointed in this phone.
I'm going to try a full reset, and perhaps a custom ROM to see if it's a hardware or software issue.
Hi,
I have this phone for little over 2 years. For over 1 week now I'm experiencing my phone not being able to wake up when I use the power button/home button. Whenever I push the button, the screen flashes for like 1s blue color, you can also see that the notification panel is blacked out and part of it green and it doesn't wake up. Sometimes it doesn't even flash. It used to take about 10 tries to wake it up but today I couldn't wake it up. I performed soft reset, I couldn't see the booting animation at all but it rebooted, buttons lit up and I was able to get in. It's like the phone is working fine in the background but the screen doesn't light up. I can turn down/up the volume, take a screenshot, get into settings, open apps, write a message but the screen is black. Even my alarm went off this morning but I couldn't dismiss it.
I downloaded an Always On Display app. Although I don't actually see the screensaver when it's locked, it's still on and it's easy to get in beacuse of it.
It all started with the screen flickering on minimum brightness. In February this year I had the screen replaced for the same issue but this time it's worse because of the blacked out screen.
Any ideas what it could be? Faulty display again?
Thank you
tessicorn said:
Hi,
I have this phone for little over 2 years. For over 1 week now I'm experiencing my phone not being able to wake up when I use the power button/home button. Whenever I push the button, the screen flashes for like 1s blue color, you can also see that the notification panel is blacked out and part of it green and it doesn't wake up. Sometimes it doesn't even flash. It used to take about 10 tries to wake it up but today I couldn't wake it up. I performed soft reset, I couldn't see the booting animation at all but it rebooted, buttons lit up and I was able to get in. It's like the phone is working fine in the background but the screen doesn't light up. I can turn down/up the volume, take a screenshot, get into settings, open apps, write a message but the screen is black. Even my alarm went off this morning but I couldn't dismiss it.
I downloaded an Always On Display app. Although I don't actually see the screensaver when it's locked, it's still on and it's easy to get in beacuse of it.
It all started with the screen flickering on minimum brightness. In February this year I had the screen replaced for the same issue but this time it's worse because of the blacked out screen.
Any ideas what it could be? Faulty display again?
Thank you
Click to expand...
Click to collapse
It's over to have this phone for little over 2 years now you should have to change
TIP:
Flash a new stock rom of your phone from sammobile via ODIN.
Sophia.xda said:
It's over to have this phone for little over 2 years now you should have to change
TIP:
Flash a new stock rom of your phone from sammobile via ODIN.
Click to expand...
Click to collapse
That would be great, but I'm not a person that buys new phone every 2 years. I was thinking about it though .
When it comes to flashing. Do you think that would help? I don't want to end up with a black screen unable to set the phone up again. Cause overall it's working great .
Hi, i have the same problem, i'm from Belgium, and I have blinking screen problem and wake up screen problem :s
is it a software issue (nougat???)
before the big update (marshmallow i dont have any problem)
i'm on firmware A510FXXS7CRJ6_A510FLUX7CRJ1_A510FXXU7CRJ6_HOME.tar.md5
Turn screen brightness up abit to stop the blinking of screen. It's an issue of the screen hardware itself at low brightness after wear and tear. As for the hanging issue, maybe it has to do with your AOD app? Try uninstalling the AOD app OR flashing a stock Rom OR custom rom OR factory reset and use your phone at a higher brightness that the screen does not blink and see whether it still persists.
conanDO98 said:
Turn screen brightness up abit to stop the blinking of screen. It's an issue of the screen hardware itself at low brightness after wear and tear. As for the hanging issue, maybe it has to do with your AOD app? Try uninstalling the AOD app OR flashing a stock Rom OR custom rom OR factory reset and use your phone at a higher brightness that the screen does not blink and see whether it still persists.
Click to expand...
Click to collapse
Thanks, because of my past experience with the same problem earlier this year I know about that "solution". Unfortunately, it makes the battery die faster as expected. Which is sad because I used it mainly on low brightness. So it's really not a solution at all.
I got rid of the AOD app because I found out that the phone lights up on 2nd try. AOD didn't work at all. I have to wake it up, put it to sleep and wake it up again which is always successful and the screen lights up. The screen flashes white about 3 times in a row now otherwise it works.
I haven't flashed it yet although I wanted to. But I will see what can I do. Thank you though!
I'm having the exact same issue using LineageOS.
It's already been 2 years, but since this thread is one of the first results on Google, I'll gladly add a solution.
Exact same problem for me, went through two screen repairs under warranty, and it would always come back a year later. No difference between Samsung OS and LineageOS, though I haven't tried rooting it.
Found on Ifixit: this issue is related to the AMOLED screen technology used by Samsung (among others). You can look it up, apparently there is a bad (?) voltage management in low brightness which worsen with time.
I could fix it with the "OLED Saver" application on Play Store. It works around this voltage management and allows you to reduce the brightness without the green flickering.
I still got white flashes after the installation, but not anymore the day after. I could even disable this application without the issue coming back.
I don't know what kind of magic cleanup this app performed, but it really is a (screen) life saver.
Hey guys,
so far I’m really happy with my new 6T. But I’ve found one bug which I’d like to see fixed.
I like to use either the sRGB or the DCI-P3 color profile as the standard color profile is just too saturated and contrasty for my liking. And at night, I’d like to use the display night mode, to reduce blue light. Unfortunately, if the screen is off and I wake up the phone, (doesn’t matter if it’s via face unlock or screen unlock) the screen changes itself to Standard color profile and you can slowly see the night mode take effect – but on top of the standard color profile which is, as mentioned above, not my cup of tea. It happens with both sRGB and DCI-P3 profiles and night mode enabled.
Only if you then turn night mode off again, you can literally see the colors jump back to your original set profile. Which obviously cannot and should not be the intended way night mode works, as night mode also reduces contrast and saturation. This can be seen if you have set the color profile to Standard in the first place and then turn on night mode, which basically shifts the colors to sRGB. Curiously enough, if you then lock the phone and wake it up, everything is as it should be and as I'd like it to be when sRGB is the set profile, meaning the color profile stays sRGB like and night mode is in effect.
I’m running completely stock Oxygen OS 9.0.5., no root, didn’t unlock bootloader or anything.
Does anyone else experience this behavior? Any help or suggestions are greatly appreciated!
Thanks!
I've been trying to find an answer to this issue since I got the phone. It is appalling that both ambient display and the lock screen are not affected by night mode. It is completely counteractive to how night mode should work.
And I have no idea why they disable color profiles when in night mode. In the settings menu, once you enable night mode, the screen calibration option is greyed out. But it is clearly not a technical limitation because enabling sRGB and then night mode produces the proper effect of a night-shifted sRGB color space. Waking the phone at night turns night mode off on the lock screen, and puts it in standard profile, then shifts to night-shifted standard profile after unlocking. I hate it.
If you come across an answer, please post it back here so others (and I) can find it.
Also, small technical note: night mode does not affect saturation or contrast or color space, only color temperature. sRGB is an entirely different color space with different saturation and gamma curves.
rriegner said:
I've been trying to find an answer to this issue since I got the phone. It is appalling that both ambient display and the lock screen are not affected by night mode. It is completely counteractive to how night mode should work.
And I have no idea why they disable color profiles when in night mode. In the settings menu, once you enable night mode, the screen calibration option is greyed out. But it is clearly not a technical limitation because enabling sRGB and then night mode produces the proper effect of a night-shifted sRGB color space. Waking the phone at night turns night mode off on the lock screen, and puts it in standard profile, then shifts to night-shifted standard profile after unlocking. I hate it.
If you come across an answer, please post it back here so others (and I) can find it.
Also, small technical note: night mode does not affect saturation or contrast or color space, only color temperature. sRGB is an entirely different color space with different saturation and gamma curves.
Click to expand...
Click to collapse
Thanks for your reply. Glad I'm at least not the only one noticing this issue.
As to your last statement, I would've thought so too. But this does not seem to be the case here. If you set the color profile to standard and then turn on night mode, the color space gets changed to sRGB, at least from what I can see. It looks completely different than the falsely activated night shifted standard profile, and looks exactly like the night mode in top of the sRGB mode, so less saturation and contrast (gamma). I don't know if this is intentional but makes it all the more confusing, because it retains the combination of sRGB + night mode even after locking and unlocking.
ef_x said:
Thanks for your reply. Glad I'm at least not the only one noticing this issue.
As to your last statement, I would've thought so too. But this does not seem to be the case here. If you set the color profile to standard and then turn on night mode, the color space gets changed to sRGB, at least from what I can see. It looks completely different than the falsely activated night shifted standard profile, and looks exactly like the night mode in top of the sRGB mode, so less saturation and contrast (gamma). I don't know if this is intentional but makes it all the more confusing, because it retains the combination of sRGB + night mode even after locking and unlocking.
Click to expand...
Click to collapse
Wow, you are exactly right. I never thought to try that method, but I agree with your assessment. In standard calibration, night mode also toggles sRGB on and off. This is not affected by lock.
In both sRGB and DCI-P3, toggling night mode does not change calibration, but waking from lock leaves it stuck in standard calibration until you toggle night mode again.
And in all scenarios, the lock screen is never in night mode. Also, the add fingerprint page disables night mode and sticks you back into standard calibration with night mode, no matter which calibration you had selected. So the add fingerprint page acts exactly like the lock screen. This leads me to believe that the fingerprint sensor needs a very specific color of light to operate. But that doesn't excuse the fact that calibration keeps switching and getting stuck. I would think they can override that though.
I just made a post about this on reddit. Maybe up vote it to help increase visibility as this is the first mention I've seen about this issue other than this reddit post.
https://www.reddit.com/r/oneplus/comments/9wkkgj/_/
The whole night mode issues and ambient display going max brightness are super frustrating. This is my first non Nexus/pixel since the oneplus 1, and these small issues are making me question if leaving for a less stable manufacturer was a good idea
After doing some more testing, I've determined this whole ordeal is tied to the fingerprint sensor. Deleting all my fingerprints (disabling it entirely) has resolved all the issues of switching calibrations an night mode toggling. Everything works as it should, except ambient display never is night mode. But the lock screen is in night mode.
I'm personally ok with this for now. Face unlock is very quick, and smart lock keeps my phone unlocked at home at night. Hopefully this gets fixed for real in a future update.
rriegner said:
After doing some more testing, I've determined this whole ordeal is tied to the fingerprint sensor. Deleting all my fingerprints (disabling it entirely) has resolved all the issues of switching calibrations an night mode toggling. Everything works as it should, except ambient display never is night mode. But the lock screen is in night mode.
I'm personally ok with this for now. Face unlock is very quick, and smart lock keeps my phone unlocked at home at night. Hopefully this gets fixed for real in a future update.
Click to expand...
Click to collapse
Exactly what i discover. Night mode not works when fingerprint senor is active which means on screen lock and app lock.Don't know weather they do it intentionally(to work fp sensor fine) on not but this is seriously irritating and painful to eyes.