Hi, started this thread to see if anyone had the same problem I'm having with my screen.
I have a Galaxy S4 GT-I9500 (Octa-core variation), it is running 4.4.2, rooted, stock Touchwiz.
The problem is that the screen starts to flicker almost as if it would want to turn off, when in low light conditions and auto-brightness on, it continues to flicker unless I set the brightness between +2 and +5. I can reproduce the issue without auto-brightness setting the brightness to the lowest, one notch above the lowest and there is no flickering. It is noticeable in white backgrounds and also when swiping down the notification center, that's the most noticeable instance but you can see it in the home screen and in any app.
I started noticing it when I had 4.2.2 Jelly bean (rooted), and I updated to Kitkat hoping it would be solved but it is the same, I updated through Kies and rooted, no Factory reset, I want to try that as last resort.
Funny thing I discovered is when I set Juice Defender to control my brightness it does not flicker even in -60% brightness, but when the dimming happens before the screen turns off it does flicker (and the dimming thing is controlled by the OS I think, not Juice Defender).
I wish I could put up a video but I don't have another phone to film it.
Anyone know if this is software or hardware? What can I do?
I'd like to add, that I changed the battery, disabled overlays in developers option, forced GPU rendering, tried Pimp my rom and played with all the settings, checked and unchecked every option in Display settings and it still flickered given the low brightness conditions.
I think I've found the best solution out there for most annoying screen flickering issues... Done a substential amount of digging and finally discovered the app "Twillight" works like a charm by enabling backlight control feature... Try it out first, then thank me and share your experience here ...
Related
Ever since as long as I can remember, my phones brightness will dim to a brightness so dark you just can't see it. Even if you manually set the brightness, once you lock and wake the screen, it's fine then suddenly switches to dark.
I've used multiple ROMs and they all do it. Is it a device issue, or could it be a kernel issue? I've not screwed with kernels so I don't know if it could be it. If it's a device issue, I'll be getting a replacement ASAP.
Any help is appreciated!
Now that I'm able to Google, I realize it's a common problem with the S4.
Sent from my SGH-I337 using Tapatalk 4
Serfma said:
Ever since as long as I can remember, my phones brightness will dim to a brightness so dark you just can't see it. Even if you manually set the brightness, once you lock and wake the screen, it's fine then suddenly switches to dark.
I've used multiple ROMs and they all do it. Is it a device issue, or could it be a kernel issue? I've not screwed with kernels so I don't know if it could be it. If it's a device issue, I'll be getting a replacement ASAP.
Any help is appreciated!
Click to expand...
Click to collapse
The only time I had the screen go dim like you describe is I remember once following a phone call. It goes dark when you put the handset to your ear like it's supposed to, and lights back up when I pull it away from my head. I was stepping out of a truck into the broad daylight when I tried to hang up my phone, I couldn't see the screen very well. The other party ended the call, and my screen timed out while I was squinting at it. I pushed the home button and it lit right back up nice.
You got something going on, and if you tried all those different roms, say... can you nandroid back to stock? Did you try that?
I'd try everything I could on the outside chance of repair instead of replacement. If you get a replacement you might be stuck with that MF3 where you cannot install a custom recovery.
fukenbiker said:
The only time I had the screen go dim like you describe is I remember once following a phone call. It goes dark when you put the handset to your ear like it's supposed to, and lights back up when I pull it away from my head. I was stepping out of a truck into the broad daylight when I tried to hang up my phone, I couldn't see the screen very well. The other party ended the call, and my screen timed out while I was squinting at it. I pushed the home button and it lit right back up nice.
You got something going on, and if you tried all those different roms, say... can you nandroid back to stock? Did you try that?
I'd try everything I could on the outside chance of repair instead of replacement. If you get a replacement you might be stuck with that MF3 where you cannot install a custom recovery.
Click to expand...
Click to collapse
Mf3? Is that something new with the S4s to prevent custom ROMs?
It does not go pitch black. It goes very dim every time I wake the device. If you Google S4 screen dimming it's a wide problem.
Once you wake it, it's fine for 2 seconds and dims quite dark. It is not screen timeout/sleep/etc since I can still see the screen.
Sent from my SGH-I337 using Tapatalk 4
I'm on MDJ and don't get any auto dimming of any sorts. Auto brightness is off, brightness controls about 1/3 brightness (indoors), but Power Saving mode is on with all three options on.
My S4 is MDL. I found out the problem (More than likely) was the Paranoid Android ROM. I was on ver. 3.69 and since switched to CM 10.2 Nightlies, latest as of today, and no screen dimming. I will install my usual apps and use it as normal and if it happens, it's probably an app. However, the only apps I use are ones such as SwiftKey, LightFlow, ASTRO, Chrome, and Dashclock.
I'm on stock MDL. It has only been occurring since I upgraded from MDB 3 days ago, and is a huge PITA because brightness controls are unresponsive during this time - I go into settings to adjust brightness since I have removed all the brightness controls from the notification panel as they've always worked just fine, and turn off auto brightness, scale it all the way to max, and it is still dim as crap.... Only fix I've seen is to reboot, which is obviously not ideal in most situations when I need to wake the device! I'm using STOCK kernel, STOCK ODEXED ROM as well, nothing crazy should be going on to screw with brightness settings being unresponsive either!
KryptosXLayer2 said:
I'm on stock MDL. It has only been occurring since I upgraded from MDB 3 days ago, and is a huge PITA because brightness controls are unresponsive during this time - I go into settings to adjust brightness since I have removed all the brightness controls from the notification panel as they've always worked just fine, and turn off auto brightness, scale it all the way to max, and it is still dim as crap.... Only fix I've seen is to reboot, which is obviously not ideal in most situations when I need to wake the device! I'm using STOCK kernel, STOCK ODEXED ROM as well, nothing crazy should be going on to screw with brightness settings being unresponsive either!
Click to expand...
Click to collapse
Do you by chance use Light Flow?
I solved the problem. I had "lcd_backlight" control flipped on in the settings of Light Flow. It fixed it. To tell if it's an app problem, just factory reset and try, once you boot up, to lock and wake the device to see if it happens. If it doesn't, it's an app problem more than likely, or even a general setting. Troubleshoot for the win!
Serfma said:
Do you by chance use Light Flow?
I solved the problem. I had "lcd_backlight" control flipped on in the settings of Light Flow. It fixed it. To tell if it's an app problem, just factory reset and try, once you boot up, to lock and wake the device to see if it happens. If it doesn't, it's an app problem more than likely, or even a general setting. Troubleshoot for the win!
Click to expand...
Click to collapse
I do use Light Flow, but I don't have either one of the LCD Backlight controls enabled, never have and never will, so I don't know how that could be affecting my phone at all.... That's a good start for some, but not for me, unfortunately! Good catch though
Sent from my Samsung Galaxy S 4 using the XDA app
Serfma said:
Ever since as long as I can remember, my phones brightness will dim to a brightness so dark you just can't see it. Even if you manually set the brightness, once you lock and wake the screen, it's fine then suddenly switches to dark.
I've used multiple ROMs and they all do it. Is it a device issue, or could it be a kernel issue? I've not screwed with kernels so I don't know if it could be it. If it's a device issue, I'll be getting a replacement ASAP.
Any help is appreciated!
Click to expand...
Click to collapse
I had this issue before on my Galaxy S3. I ended up replacing the front glass because of a dead pixel. Come to find out I had a sensor issue and that was causing my brightness auto going to whatever level it wanted.
Perhaps you're experiencing that too. Haven't heard or read of any sensor issues yet with the S4 but you could be the lucky winner!
So I tossed LP on over the weekend using the FlashFire method so I'm rooted and things seem to be working well. My only real issue is that the auto-brightness seems dimmer to me than at 4.4.4. It works, that is I see the screen brightness automatically change when ambient light levels change, but inside, in a "normally" lit room in a house (no overhead florescent lighting) it is definitely dimmer than before.
Does anyone know of a tweak for this besides just turning off auto-brightness, which I'd prefer not to do?
my only other complaint about LP is the owner info not showing on the lock screen if you have the notifications enabled...
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.
Has anyone noticed Display keeps flickering when auto brightness is on. Even if phone is kept at a fixed position & same amount of light is exposed to the sensor it still keeps flickering. I mean if I'm watching movie it automatically dems or increases the brightness. please confirm how many user experiencing this problem! as per i know it was not resolved from 301 to till 331 update. is it manufacturing defect particularly with specific variant ?
I wouldn't call it it a flicker. More like the auto-brightness feature is so badly programmed that it doesn't transition from dim to bright and vice versa in a smooth, gradual or dynamic manner, like in older and cheaper phones.
My eyes get a shock every few seconds, trying to adjust to the sudden jumps in screen brightness. It's a real pain.
And yes, the issue has persisted through all the OTA updates without any sign of improvement.
Instead of addressing this most basic and "glaring" issue, Asus seems to be intent on introducing bloatware and EIS for the phone and announce it like it's the second coming.
The latest update was supposed to bring with it, system optimization but I don't see any form of basic optimization, let alone calibration, with the screwy display.
I can only guess at Asus' sense of priorities. Or if they're actually blind and/or stupid.
May be it was true that autobrightness was programmed badly manner it was not transist smoothly from dim to bright. But afterall we are facing it at serious level and uptill now asus has not solved yet. I just want to confirm that How many user experiencing screen flicker issue after enabling auto brightness or it was particularly manufacturing defect with specific varient.
its an autobrightness calibration issue,software update will fix it in future,lets hope so
Hello everybody! I found a bug: brightness is flickering even when "auto brightness" ("adaptive brightness") is disabled. Brightness can encrease for few seconds and then decrease to previous level. I read in some reviews that max pro m1 has adaptive brightness which changes depending on content on the screen. I tried to change a lot of display settings, developer settings, i tried to adjust CABC (Content Adaptive Brightness Control) through Nova Launcher (but later I read that CABC controls only autobrightness), and even hard reset. I flashed custom ROMs but it didn't help. Only Lux Dash app helps avoid this bug. But it is not very comfort to use it and I think there must be desicion on firmware level. Did anybody has this problem and any solution? May be somebody has this issue and found custom ROM without flickering brightness?
Sorry for my English, it's not my first language. And thank you for answers!