Out of nowhere, my phone's screen has tarted to flicker. The brightness flickers and is very distracting. I've already tried to flash the latest OxygenOS available, but it hasn't worked.
Thing is, it flickers in both OOS and TWRP but it doesn't when booting up and in the bootloader.
Is it a hardware issue or there's a software fix?
kami_sama said:
Out of nowhere, my phone's screen has tarted to flicker. The brightness flickers and is very distracting. I've already tried to flash the latest OxygenOS available, but it hasn't worked.
Thing is, it flickers in both OOS and TWRP but it doesn't when booting up and in the bootloader.
Is it a hardware issue or there's a software fix?
Click to expand...
Click to collapse
I've the same issue...out of the blue it started flickerin and is very annoying...half of the screen (dx side) is slightly more yellow...Have you found any fix for this?
afarnedi said:
I've the same issue...out of the blue it started flickerin and is very annoying...half of the screen (dx side) is slightly more yellow...Have you found any fix for this?
Click to expand...
Click to collapse
Nope, in the end I had to RMA the phone.
I had to go through the hops from support, but they were certain it was a hardware fault, I had it fixed at no cost.
There can be two things, one's Adaptive Brightness which usually does that, check if you have it enabled, disable it.
Second thing can be CABC (Content Adaptive Backlight Control) which works as opt's lcd throttler. It throttles, i.e. puts the brightness to a bare minimum when the temperature of the screen exceeds a particular value.
Now disabling this isn't very productive and/or practical. But if you want it disabled you can flash cm13 (a custom rom). On cm13 I've realised it works only on temperatures more than 65-70*.
I suggest you to keep your opt cool as long as you can.
Mine started flickering just after I made a change in Settings, and it was Turning OFF Adaptive Brightness
Mine just started flickering after I didn't change anything at all. Never used adaptive brightness in my life.
Related
My backlight keeps adjusting itself. Even with auto brightness off.
I don't really want to call it flicker, because it doesn't seem like flickering. It's more like pulsing slightly brighter and then slightly dimmer. It's most noticeable on light colored backgrounds, like the browser or the play store. As I said, I have auto brightness turned off, so I would think that there'd be absolutely no change in brightness when bringing up a bright window.
Any ideas on what can be done to fix this? I am rooted, but I have not installed any custom roms. I'm running stock 4.2.1.
Thanks
Its a well known bug with jellybean
davidoff59 said:
Its a well known bug with jellybean
Click to expand...
Click to collapse
Any fix? If necessary, I'm willing to load a custom ROM and/or Kernel. I just haven't gotten around to it yet.
usmaak said:
Any fix? If necessary, I'm willing to load a custom ROM and/or Kernel. I just haven't gotten around to it yet.
Click to expand...
Click to collapse
If you're rooted there is a solution here....
http://forum.xda-developers.com/showthread.php?t=1815414
The essence of which is as follows...
Run this command using terminal emulator (https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en)...
To Disable SmartDimmer ...(to prevent 'flicker').
Code:
su
echo "0" > /sys/devices/tegradc.0/smartdimmer/enable
You can set this up as a script to be executed at boot using ScriptManager (https://play.google.com/store/apps/details?id=os.tools.scriptmanager).
Set it as ROOT and BOOT... you won't need the 'su' command in the script, as ScriptManager will already be granted su permissions.
This has totally eradicated the screen brightness fluctuations (not as pithy as 'flicker' but I think a more accurate description) for me .
Rgrds,
Ged.
Thanks so much! I did this and the flickering went away. I even undid it to make sure. When I shut it off, the flickering returned. Turn it on, flickering gone. I even checked at different brightness, and no flickering. Originally I thought this was just another defective unit. After spending a bit of time looking around the web, turns out it is a common problem. I am glad that there's a simple solution, at least for us rooted folks.
And I agree that flicker isn't exactly right. To me, flicker is more random. This is more of a rhythmic pulsing of the backlight, between brighter and dimmer. And I can readily reproduce it by shutting down chrome and going back in.
When video recording for over 20secs, the screen will go dim and when u go into brightness settings i will get a message saying the device is overheating if you try to change the brightness back to full, this normal?
It happens on both 5.0.1 and 4.4.4..
I checked the temp straight after and it was only at 40c.. I have literally just bought the phone and never experienced screen dimming on the note 3, possible bug, faulty phone?
christoph_2013 said:
When video recording for over 20secs, the screen will go dim and when u go into brightness settings i will get a message saying the device is overheating if you try to change the brightness back to full, this normal?
It happens on both 5.0.1 and 4.4.4..
I checked the temp straight after and it was only at 40c.. I have literally just bought the phone and never experienced screen dimming on the note 3, possible bug, faulty phone?
Click to expand...
Click to collapse
Not experiencing that on both version even when recording 4K. Maybe you're encountering the issue below.
http://forum.xda-developers.com/note-4/general/upper-screen-getting-hot-t3103904
f4vr said:
Not experiencing that on both version even when recording 4K. Maybe you're encountering the issue below.
http://forum.xda-developers.com/note-4/general/upper-screen-getting-hot-t3103904
Click to expand...
Click to collapse
Yes i do notice the top half of the phone getting really hot, but ive only had the phone since saturday and dont want to root the phone just incase i have to take it back, any other options?
EDIT: Got the phone replaced, using the samsung stock camera the screen will dim a tiny bit and in the brightness settings it will say device is overheating even though phone not warm must be a safety feature to stop phone from overheating itself, downloaded snap camera and there was no screen dimming or warnings in settings. Checked my old note 3 and the same thing is there with the dimming and warning.
I read somewhere about knox being a culprit so i will look into that due to all the security features etc.
Hey, i updated to the latest firmware that came out today 9. april 2016. Firmware version : G935FXXU1APD1/G935FNEE1APC5/G935FXXU1APD1. My Phone is a Nordic Edition S7E with Carrier Telenor Norway.
after the update everything works like it should except the Always on Display. The AoD works but its always on the lowest brightness... it moves around, shows what i ask etc but it wont get brighter when i go outside or shine something at it, auto brightness works fine on the screen when its on. my question is: does this happen to anyone else? this has to be a software bug within the AoS app or the OS itself :/ cheers
What version does it show in the AOD settings ( About AOD)
Version 1.1.14
I guess its a change, this is the version i have. Im on fw PB6
it seems like it does work tho much slower than before, i think they tweaked the sensitivity on the brightness, because before it changed waaaaaay to easy, now it stays on the right brightness for the area you are in, tho if you go from a dark room to a bright room it takes waaaaaaaaay to long for it to change, and when you take it out of you're pocket it will still be on the lowest brightness for some reason... so AoD is now useless outdoors if its sunny out, ill guess they will change it again since i think they over did it.
it is not a problem it is intended to reduce power uage.
antenehnile said:
it is not a problem it is intended to reduce power uage.
Click to expand...
Click to collapse
iknow that, but the point of AoD is that you should not need to turn ON your display, now you have to if you are outside, since the update rate it so low on the brightness. for indoor use its awesome tho.
Zychic said:
iknow that, but the point of AoD is that you should not need to turn ON your display, now you have to if you are outside, since the update rate it so low on the brightness. for indoor use its awesome tho.
Click to expand...
Click to collapse
Idk about the brightness, mine bases itself off of lighting around me. As for it moving, that is to save your screen from AMOLED burn in.
I have a real problem with AOD, after the latest T-Mobile April security update, AOD doesn't move and it should to prevent burn in. I currently have it turned off until it's fixed.
My AOD version 1.1.17
Sent Via My Samsung S7 Edge
Rydah805 said:
Idk about the brightness, mine bases itself off of lighting around me. As for it moving, that is to save your screen from AMOLED burn in.
I have a real problem with AOD, after the latest T-Mobile April security update, AOD doesn't move and it should to prevent burn in. I currently have it turned off until it's fixed.
My AOD version 1.1.17
Sent Via My Samsung S7 Edge
Click to expand...
Click to collapse
i know it has to move the issue is that it takes so long for the brightness to increase/decrease after the update when the light changes in the room/place you are, so when you are outside and take your phone out its on the lowest brightness, so you cant see anything, it takes over 20 sec before it increases the brightness. but why there is so many " latest version" of the AoD is weird if you ask me. it worked before the firmware update tho it increased the brightness to the max much easier before, so it used a lot of battery, i think they tried to fix this but overdid it. that is why i'm asking if its happening to anyone else.
Zychic said:
i know it has to move the issue is that it takes so long for the brightness to increase/decrease after the update when the light changes in the room/place you are, so when you are outside and take your phone out its on the lowest brightness, so you cant see anything, it takes over 20 sec before it increases the brightness. but why there is so many " latest version" of the AoD is weird if you ask me. it worked before the firmware update tho it increased the brightness to the max much easier before, so it used a lot of battery, i think they tried to fix this but overdid it. that is why i'm asking if its happening to anyone else.
Click to expand...
Click to collapse
Oh, sorry I misread that. I thought you were having multiple issues. Yes, mine takes forever too.
I don't know why they just don't put it in the Galaxy App Store so that all can have the latest version.
Sent Via My Samsung S7 Edge
Rydah805 said:
Oh, sorry I misread that. I thought you were having multiple issues. Yes, mine takes forever too.
I don't know why they just don't put it in the Galaxy App Store so that all can have the latest version.
Sent Via My Samsung S7 Edge
Click to expand...
Click to collapse
Yeah they really should put it in the app store, just like they did with the edge features, but i didnt receive the new updates yet, so im waiting for it
i did a test now, it only changes brightness when the AoD moves for me, i guess that is how it should work, i don't remember how often i did back on the PB4 firmware but it was much more sensitive that is for sure.
latest firmware did break AOD for me too, T-Mobile US. AOD no longer moves. Not sure if I noticed before but waking the screen up now with power or home button, the screen fades in somewhat. It's a very quick fade in but noticeable because it's not instant.
I am seeing some serious problems with the AOD- I even asked for an exchange thinking something was defective. I got my new phone today and it reacts in the exact same way: AOD brightness changes completely at random ie I am not able to see any sort of correlation between how dark/light it is where I am. AOD version is 1.1.06, while the firmware version is PB9.
The other issue I am seeing is with GPS- worst that I have seen until now. I tried it with GMaps and a couple similar apps- the arrow that shows the direction does not move around based on which way the phone is pointing. This was the exact same on the phone that I sent back in exchange for the new one this morning..
NYanakiev1 said:
I am seeing some serious problems with the AOD- I even asked for an exchange thinking something was defective. I got my new phone today and it reacts in the exact same way: AOD brightness changes completely at random ie I am not able to see any sort of correlation between how dark/light it is where I am. AOD version is 1.1.06, while the firmware version is PB9.
The other issue I am seeing is with GPS- worst that I have seen until now. I tried it with GMaps and a couple similar apps- the arrow that shows the direction does not move around based on which way the phone is pointing. This was the exact same on the phone that I sent back in exchange for the new one this morning..
Click to expand...
Click to collapse
How do You change Your phone ? What arguments You have for a phone change ? I just wonder how people exchange their phones so easily.
Monkey Slut said:
How do You change Your phone ? What arguments You have for a phone change ? I just wonder how people exchange their phones so easily.
Click to expand...
Click to collapse
Well, I got the phone on my new contract less than 30 days ago ie I am entitled to an exchange as opposed to having to send the phone in for repairs.
Has the latest update enabled displaying all notifications, not only calls and sms messages ? If not, better turn it off and be done with it. It's useless.
Cst79 said:
Has the latest update enabled displaying all notifications, not only calls and sms messages ? If not, better turn it off and be done with it. It's useless.
Click to expand...
Click to collapse
Nah its still as useless. I disabled, it jjst drains battery
Mine is now showing a grey background. Anyone has this issue? I can't get it to go back to black.
bsm123 said:
Mine is now showing a grey background. Anyone has this issue? I can't get it to go back to black.
Click to expand...
Click to collapse
Help? Anyone?
Update
Lenovo fixed the issue in the latest update with my initial method which was switching off the CABC in the backlight controller which gives us a brightness boost. So obviously it is not dangerous.
Old Message:
So having achieved root, I was looking into the easiest of the issues. Some call it flickering. The "feature" is called CABC and is supposed to save battery. But obviously this comes at a cost of the display constantly adapting the brightness to the content which can cause flickering depending on what you have on the screen.
With root this can be switched off. Alternatively a new kernel could solve this without root. In both cases an unlocked bootloader is still required.
Instructions:
Use a build.prop editor form the Playstore
Edit the variable "ro.qualcomm.cabl=2" and set it to 0. CAUTION this modifies the system partition. If you want to receive OTAs in the future you will have to flash the system partition with an original image or backup.
Reboot
Technical details:
There are three places where CABC can be switched off:
In the build.prop
In the device tree blob in the boot image/kernel. Specifically the DSI switch on commands in the LCD panel description contain the enabling of CABC
In the LCD backlight driver /sys/devices/soc.0/78b6000.i2c/i2c-2/2-002c -> could be dangerous because it increases brightness and the voltages in the backlight controller
matshias said:
So having achieved root, I was looking into the easiest of the issues. Some call it flickering. The "feature" is called CABC and is supposed to save battery. But obviously this comes at a cost of the display constantly adapting the brightness to the content which can cause flickering depending on what you have on the screen.
With root this can be switched off. Alternatively a new kernel could solve this without root. In both cases an unlocked bootloader is still required.
I attached an Automate flow which disables CABC and guess what we get a brightness bump of about 20%. Now the maximum brightness of the display is even a bit brighter than my old Yoga Tab 2 and should be on par with the 3 pro
Make sure that Automate runs on system startup and has root enabled.
Technical details:
There are two places where CABC can be switched off:
In the device tree blob in the boot image/kernel. Specifically the DSI switch on commands in the LCD panel description contain the enabling of CABC
In the LCD backlight driver /sys/devices/soc.0/78b6000.i2c/i2c-2/2-002c
It turns out that if you disable the latter CABC is off even without modifying the former. Of course this requires ROOT to change. This could also be done in the kernel, but would need either a recompile or modifying the init.rd
Click to expand...
Click to collapse
Thanks Now only audio sync issues left for me and tablet will be perfect.
Have you compared the battery performance with and without CABC disabled?
Ashili said:
Have you compared the battery performance with and without CABC disabled?
Click to expand...
Click to collapse
No, these battery life tests take a long time, which I don't have Time is better spent looking into the other issues. It shouldn't be too much of a difference.
matshias said:
No, these battery life tests take a long time, which I don't have Time is better spent looking into the other issues. It shouldn't be too much of a difference.
Click to expand...
Click to collapse
Yap, I think so. The battery life is long enough. Thank you.
I would think as long as you manually adjust brightness to match your content, you'd get similar results.
I modified the thread to use a less invasive method. I am having issues with my tablet. I am not sure it was caused by this mod but just to be safe I recommend everyone not to use it any longer.
what kind of problem?
chuwq1038 said:
what kind of problem?
Click to expand...
Click to collapse
Everything works (also the display) but the battery drains and the back of the tablet gets warm even when the tablet is switched off. Could be completely unrelated to the mod, but who knows.
With latest official update I have a battery drain issue too. 15% down overnight...
This is afix to screen burn issue some of our devices have
Download bluescreen filter and change the opacity 5 %
Thus you temporarily fixed the screen burn.
https://www.youtube.com/watch?v=kOFQ1-ewMOY
watch the video .
Comment in case of queries :good:
If rooted ..Just download a kernel management app...Ex kernel manager or kernel auditor (misspelt)..Go to Color management and reduce all 3 rgb to 200 and set apply on boot...This way you'll face no extra distorted Colors .
ad_anu143 said:
If rooted ..Just download a kernel management app...Ex kernel manager or kernel auditor (misspelt)..Go to Color management and reduce all 3 rgb to 200 and set apply on boot...This way you'll face no extra distorted Colors .
Click to expand...
Click to collapse
This method requires no root .
Nothing gets "burned" in the screen, it's called "screen retention" because it disappears in time.
My XT1644 started to have it. I had applied the last OTA (14-4) and it was still there. Then my phone locked-up in a boot loop and I decided to go back to 14. Well... no more screen retention now!
I used Sfilter Lite, it consumed less baterry and worked well, nowdays I'm rooted and got my colors fixed with XKernel Manager.
---------- Post added at 04:43 PM ---------- Previous post was at 04:42 PM ----------
SoNic67 said:
Nothing gets "burned" in the screen, it's called "screen retention" because it disappears in time.
My XT1644 started to have it. I had applied the last OTA (14-4) and it was still there. Then my phone locked-up in a boot loop and I decided to go back to 14. Well... no more screen retention now!
Click to expand...
Click to collapse
are you saying it has to do with the android version?
It might have to be related with the actual firmware that they are pushing. I was kind of pissed when I noticed the retention, because before I never had it, but now is completely gone.
I have rooted it with ElementalX every time and adjusting the RGB levels didn't help, retention was still there.
Now, I don't even have a Kernel Manager installed anymore. And retention it's gone ¯\_(ツ)_/¯
SoNic67 said:
It might have to be related with the actual firmware that they are pushing. I was kind of pissed when I noticed the retention, because before I never had it, but now is completely gone.
I have rooted it with ElementalX every time and adjusting the RGB levels didn't help, retention was still there.
Now, I don't even have a Kernel Manager installed anymore. And retention it's gone ¯\_(ツ)_/¯
Click to expand...
Click to collapse
I hope the " screen retention" you were talking about is a hardware issue. I dont think software updates or downgrades can fix them.
Only changing the LCD panel can permenently fix them.
I can be wrong btw.
I could see the hour, battery symbol and cell strength indicator when pulling down the top drawer, retained and faded on the grey area. Now they are not there anymore.
If I was taking a screenshot, the retention was not in the screenshot, so it wasn't kept in the video memory. Probably it was in the LCD controller somehow.
Don't know what to say maybe the firmware adjusted the RGB values to less than 256 (what we can do also with the custom kernel).
Which version are you on exactly?
SoNic67 said:
I could see the hour, battery symbol and cell strength indicator when pulling down the top drawer, retained and faded on the grey area. Now they are not there anymore.
If I was taking a screenshot, the retention was not in the screenshot, so it wasn't kept in the video memory. Probably it was in the LCD controller somehow.
Don't know what to say maybe the firmware adjusted the RGB values to less than 256 (what we can do also with the custom kernel).
Click to expand...
Click to collapse
I agree with this. Its not a hardware side issue, because, different screen instances show different image retentions... Its annoying as f*ck, but at least its not hardware... They probably need to update the LCD firmware...
Hardware Issue!!!
It's an hardware issue!!! I had the same problem with my Moto G4 Plus. I unlocked the bootloader to try the ex kernel manager method but didn't work then i took it to the service centre and they changed the lcd panel. And now no screen burn issue!!!
There is a method which I remember one Xdian used to tackle screen burning issue...go to colour calibration in Live display option and put all the values to 95%..
Done