Related
Hey Guys,
I have figured out how to get rid of the ugly green screen issues with 3rd party kernels for MIUI.
Goto Settings
Display Settings
Turn automatic brightness on
Adjust the slider until the screen is at the lowest (before it turns green)
Go into advanced mode
Turn on Use Custom under Light levels
Light level to dim - set to 10
This should fix all the issues with green screens!
I never had any green screen on miui, with official or neo/vorbeth/glitch kernels.
I was curious and tried what you posted above, and I can't do step 4
3. Turn automatic brightness on
4. Adjust the slider until the screen is at the lowest (before it turns green)
If auto brightness is set to "on", I can't slide..
filou75 said:
I never had any green screen on miui, with official or neo/vorbeth/glitch kernels.
I was curious and tried what you posted above, and I can't do step 4
3. Turn automatic brightness on
4. Adjust the slider until the screen is at the lowest (before it turns green)
If auto brightness is set to "on", I can't slide..
Click to expand...
Click to collapse
That's odd, maybe the new versions fixed this problem. I guess coming over from cm7 if you have custom brightness it will turn to green with miui
Sent from my Xoom using Tapatalk
it worked, thanks! my dim level was set to 5, changing it to 10 worked perfectly.
strange... never had this issue when i was on miui and that was yesterday.
i have the same problem, i went at a local repair store, and the guys overthere told me that the colour module is broken !!! anyone knows something about this???
they say that in my case i need to replace the screen in order to fix this issue... if anybody have other idea...
thanks in advance !
phone samsung galaxy s1 gt-i9000 stock rom not rooted
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!
UPDATE: The official Lux plugin for Nexus 5 is out now. Please use the official plugin instead. You can get it here: https://play.google.com/store/apps/details?id=com.vitocassisi.lux.plugin.nexus5
So what does this plugin offer?
Higher quality astronomer/night modes and subzero adjustment
On screen buttons are adjusted
Screenshots are no longer discoloured
Improved contrast
No more screen overlay means slightly less cpu usage
Instructions & important information
This plug-in can only be used on rooted Nexus 5 devices using Lux Auto Brightness v1.3 or higher!
You must enable plug-in support under the Advanced section of Lux preferences for it to work.
Should you decide to uninstall the plugin, it's strongly recommended that you reboot your device.
Notes
Astronomer/night modes require kernel RGB display calibration support (Franco Kernel R37 and newer and maybe other kernels. Check with your kernel developer). I have only tested this on Franco Kernel R37. Backup your ROM before installing.
Download:
Removed. Please use official plugin.
Nice plugin, testing it now.
Testing now
Sent from my Nexus 5
I've just read in the Franco kernel thread where you mention your plug in and a comment about working around KitKat limitations. I'm curious what the limitations are so please elaborate.
Thanks
Sent from my Nexus 10 using XDA Premium HD app
When my screen is close to timing out at 30, screen dims until screen turns off (which is normal). But the screen stays dimmed even after I tapped it before the timeout. Have to pull down notifications and either add or minus brightness to lux for it to go back to its supposed brightness.
Edit: not sure what happened, but its working normally now
Sent from my Nexus 5 using Tapatalk
My screen keeps flashing like the brightness goes to max for a split second then back down to where it should be. Weird. Running on Franco's r37
Sent from my Nexus 5 using Tapatalk
Edit: it seems to be connectet to screen dimming before it automatically turns off. If I interact with the screen during this time period the backlight turns on and stays on and I have to manually turn brightness down.
Jermehh said:
My screen keeps flashing like the brightness goes to max for a split second then back down to where it should be. Weird. Running on Franco's r37
Sent from my Nexus 5 using Tapatalk
Edit: it seems to be connectet to screen dimming before it automatically turns off. If I interact with the screen during this time period the backlight turns on and stays on and I have to manually turn brightness down.
Click to expand...
Click to collapse
Mine was completely the opposite but it's still tied to the screen dimmer. I'm sure this problem is fixable with a line of code.
Sent from my Nexus 5 using Tapatalk
DroneDoom said:
When my screen is close to timing out at 30, screen dims until screen turns off (which is normal). But the screen stays dimmed even after I tapped it before the timeout. Have to pull down notifications and either add or minus brightness to lux for it to go back to its supposed brightness.
Edit: not sure what happened, but its working normally now
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same thing, fixed after a reboot.
However my night profile doesn't seem to work. It doesn't go to a sub-zero value.
I'm on r38. The color balance is a little different from before the plug in, probably due to switching to rgb. The colors seem cooler.
I too also have my screen turn suddenly bright when the phone does the auto brightness reduction when it is about to time out. Maybe that's a Franco kernel thing. I would love to use this plugin with r36 because I had much better battery life with that kernel compared to r37 or 38, but I guess the plugin doesn't work with the kernels that don't support rgb. I haven't tried it yet though.
Lux also has to often times before manually reset to adjust the brightness even if I have it set to auto and dynamic. In other words, I'll have to go to the notification panel and either hit the refresh button, or click on the percentage and once the pop up window appears on screen, the light sensor picks up the ambient light and adjusts as usual. maybe this is a sensitivity thing? maybe it wont trigger the change unless there has been a large enough change in lumens?
I have a tasker profile that turns off lux temporarily and sets brightness to 100% when using camera and gallery, and turns lux back on when closing the app. This is a little buggy with the n5 plugin installed I have seen. The phone sometimes can't decide to stay at full brightness or go back to almost illegible screen when the cam app is open. It seems to falter back and forth for some reason?
Once I close camera, lux kicks back in and it usually works at adjusting the brightness to respectable levels, but I wonder if that wonkiness inbetween is lux, or the kernel I'm using?
Sent from my Nexus 5 using xda app-developers app
anmar21 said:
Same thing, fixed after a reboot.
However my night profile doesn't seem to work. It doesn't go to a sub-zero value.
Click to expand...
Click to collapse
I think that's a bug of Lux. Basically when you tune your brightness to a sub-zero value lux adds a semi-transparent overlay to your screen to make it darker. However when Lux detects a plugin is installed, it removes the overlay and so sub-zero values won't work.
xybur said:
I'm on r38. The color balance is a little different from before the plug in, probably due to switching to rgb. The colors seem cooler.
I too also have my screen turn suddenly bright when the phone does the auto brightness reduction when it is about to time out. Maybe that's a Franco kernel thing. I would love to use this plugin with r36 because I had much better battery life with that kernel compared to r37 or 38, but I guess the plugin doesn't work with the kernels that don't support rgb. I haven't tried it yet though.
Lux also has to often times before manually reset to adjust the brightness even if I have it set to auto and dynamic. In other words, I'll have to go to the notification panel and either hit the refresh button, or click on the percentage and once the pop up window appears on screen, the light sensor picks up the ambient light and adjusts as usual. maybe this is a sensitivity thing? maybe it wont trigger the change unless there has been a large enough change in lumens?
I have a tasker profile that turns off lux temporarily and sets brightness to 100% when using camera and gallery, and turns lux back on when closing the app. This is a little buggy with the n5 plugin installed I have seen. The phone sometimes can't decide to stay at full brightness or go back to almost illegible screen when the cam app is open. It seems to falter back and forth for some reason?
Once I close camera, lux kicks back in and it usually works at adjusting the brightness to respectable levels, but I wonder if that wonkiness inbetween is lux, or the kernel I'm using?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I'm currently looking into this bug. It's caused by a work around to get the plugin to work with nexus 5. Otherwise your backlight stays on even after you turn your screen off, which is way worse than the fluctuation
anmar21 said:
However my night profile doesn't seem to work. It doesn't go to a sub-zero value.
Click to expand...
Click to collapse
I have this with the stock rom. No sub-zero values and no color temperature adjustment.
Awesome work! I wish I could help test but I'm stuck between a rock and a hard place in that I'm using the CM11 nightlies, which apparently don't work with the Franco kernel right now, but I really want the Lux root features! Anybody know if the CM kernel supports colour changes?
I think that's a bug of Lux. Basically when you tune your brightness to a sub-zero value lux adds a semi-transparent overlay to your screen to make it darker. However when Lux detects a plugin is installed, it removes the overlay and so sub-zero values won't work.
Click to expand...
Click to collapse
I'm not sure that is a bug of Lux. Up until a couple of days ago I was using a Galaxy Nexus with the Lux root plugin and that let me use sub-zero settings just fine.
The plug-in is in the playstore now. I use the carbon rom, with the kernel it comes with. Is 3.4.75-Slim4.4.2-kk-build4.1-beta a faux or Franco kernel?
augoza said:
The plug-in is in the playstore now. I use the carbon rom, with the kernel it comes with. Is 3.4.75-Slim4.4.2-kk-build4.1-beta a faux or Franco kernel?
Click to expand...
Click to collapse
Your question doesn't make sense. If you're asking what kernel to use try them both and see what you prefer.
Sent from my Nexus 5 using Tapatalk
Savant said:
Your question doesn't make sense. If you're asking what kernel to use try them both and see what you prefer.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Because I don't want to change my kernel. I want to stay stock carbon right now. Anyway I've just been using the new Nexus 5 light sensor fix module for xposed. Works great. You can use any kernel. Even stock N5 kernel
Edit: Actually the module is okay.
Please don't upload my apk's without permission. This plug-in was not written by the OP, it was written by myself. It might seem harmless, but you've diverted support from my official channels into here. That's not cool.
Cyb3rGlitch said:
Please don't upload my apk's without permission. This plug-in was not written by the OP, it was written by myself. It might seem harmless, but you've diverted support from my official channels into here. That's not cool.
Click to expand...
Click to collapse
Actually, I wrote this plugin using your source for Nexus 4 as a template. I decided to write it because at the time your plugin for Nexus 5 is not out yet. I can upload the source as proof if you want.
Either way I should probably link to your official plugin since it's out now
kevdliu said:
Actually, I wrote this plugin using your source for Nexus 4 as a template. I decided to write it because at the time your plugin for Nexus 5 is not out yet. I can upload the source as proof if you want.
Either way I should probably link to your official plugin since it's out now
Click to expand...
Click to collapse
Okay, well please don't use my market description and app icon, since it makes the distinction unclear. Thanks.
Ooops...
NEXUS 5
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 ...
When I'm in a light room the screen goes brighter but if I walk into a darker room, the screen doesn't dim unless I lock and then unlock the screen.
Anyone else having similar issues?
Yep got the same here. Thought I had a faulty ambient light sensor but obviously not.
Sent from my SM-G935F using Tapatalk
Just tried it by covering the light sensor to make sure, no problem here (G935F). My only concern related to brightness is that the s7 just has auto brightness, but no adaptive brightness.
Uncheck the auto box and recheck. Then don't touch the slider. It's usually because in marshmallow the slider moves with the auto bright and most people touch it which makes it hold position.
jackdforme said:
Uncheck the auto box and recheck. Then don't touch the slider. It's usually because in marshmallow the slider moves with the auto bright and most people touch it which makes it hold position.
Click to expand...
Click to collapse
There seems to be a bug somewhere still. I just tried to move the slider while auto brightness is ticked and to cover the light sensor afterwards again and it still worked and to my surprise it even took into account that I lowered the brightness and took also a lower brightness at the covered state and took my initial setting after uncovering, pretty nice, so there is indeed still adaptive brightness. After ticking und unticking auto it went back taking the default steps for brightness as before.
Having the same issue here
Definately not touched the slider.
Also, I have tested the light sensor and it appears to work fine so definately a software issue. Though I imagine we will see some software updates to fix bugs shortly after the official release date.
So you can adjust the slider with the box checked and get various levels of auto? Does it learn?
jackdforme said:
So you can adjust the slider with the box checked and get various levels of auto? Does it learn?
Click to expand...
Click to collapse
Yes.
I can't tell for sure, when I change further steps the previous seems to stick, at least to some extend so there is a logic behind it, but I can't tell for sure if it really is based on each step and sets it accordingly or if it's just changes the range it operates in. Anyways I'm a happy camper.
Also, I could reproduce the device not changing the brightness, when I put it to full at darkness it won't move anymore in auto. But as soon as I lower it again it will also change accordingly again, maybe at those with the stuck brightness the min brightness is only raised, but not lowered anymore, but just an assumption and doesn't help anyone atm unfortunately.
Use lux in play store
Sent from my SM-N920W8 using Tapatalk
https://play.google.com/store/apps/details?id=com.velis.auto.brightness
This is the first Galaxy phone I had, that Auto brightness actually works the way I like it.
It seems to be working fine now. It just takes a few seconds for the screen to dim (maybe I was being impatient).
After testing it further it's actually really good auto brightness.
It works, just takes some time to adjust to the lighting. Maybe the default settings are set to a certain time. Maybe with root we can adjust this..
AngioNicholai said:
It works, just takes some time to adjust to the lighting. Maybe the default settings are set to a certain time. Maybe with root we can adjust this..
Click to expand...
Click to collapse
It seems to only do it quickly when the device is lay down (as 954wrecker said). Maybe Samsung did that so it doesn't annoy you when using your phone.
this is definitely a bug imo... the auto brightness doesn't change for me either...
CuBz90 said:
When I'm in a light room the screen goes brighter but if I walk into a darker room, the screen doesn't dim unless I lock and then unlock the screen.
Anyone else having similar issues?
Click to expand...
Click to collapse
I also have an auto briteness issue, when I disable AutoBrite and set it manually about half my apps override the setting and enable AutoBriteness in the app's screen usually dimming the screen? SpadesFree one example and I do not see an override in the app.
Confimed that I'm having same issue, auto brightness not adjusting and slider not movingoing. Have to move it manually
Same issue. It needs to be fixed manually by editing services.jar (root needed)
Nothing else will work. None of google play apps will help with that issue. Does not matter what you do, it will always dimming if you don't fix it in framework.jar
Try it out: http://forum.xda-developers.com/s7-edge/development/auto-brightness-bug-try-fix-t3339858