I'm using the Voodoo App to set some custom colors for my screen. (i've changed the gamma hack and the multipliers). Now, whenever my screen times out to go to the locked state, during those 2 seconds of screen backlight dimming, the colors get messed up, with a sort of greenish mist all over the screen. This disappears upon touching the screen again.
I either want to know how to disable those 2 seconds of light dimming or how to avoid the issue altogether.
Using Brainmaster's MIUI and T1.44 kernel.
Can't think of anything but you could try a different kernel, or flash a newer version of trinity. Brainmaster posts them on his thread (second post)
dinuvali said:
I'm using the Voodoo App to set some custom colors for my screen. (i've changed the gamma hack and the multipliers). Now, whenever my screen times out to go to the locked state, during those 2 seconds of screen backlight dimming, the colors get messed up, with a sort of greenish mist all over the screen. This disappears upon touching the screen again.
I either want to know how to disable those 2 seconds of light dimming or how to avoid the issue altogether.
Using Brainmaster's MIUI and T1.44 kernel.
Click to expand...
Click to collapse
Here's a fix for the Galaxy S. Should also work for the NS.
http://forum.xda-developers.com/showthread.php?t=1172649
Sent from my -=Nexus MV=- powered Nexus S c",)
Thanks for your replies but neither worked
I changed the settings under gamma hack in Voodoo and my issue doesn't occur anymore.
dinuvali said:
Thanks for your replies but neither worked
I changed the settings under gamma hack in Voodoo and my issue doesn't occur anymore.
Click to expand...
Click to collapse
what setting do you changed?
Raise your screen dim level if you're on CM7 or lower your voodoo color values.
Sent from my Nexus S 4G
obsanity said:
Raise your screen dim level if you're on CM7 or lower your voodoo color values.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
the green dims will disappear when my gamma setting back old 2.3.3 which is 0 for red,blue,green
Odd green screen solved but my color is poor..like a old phone..
Sent from my Nexus S using xda premium
Related
Hi guys, if you think how the power button will break sometime because it feels so fragile, maybe you want to use this app. I made this app for personal use, but I do want to share with you.
This app basically only make the screen brightness to 0 (zero), and you gotta wait for 10 seconds to let Android call the lock screen.
nb:
if you didn't wait till time out (10 secs), you are still basically locking it manually. that means you have to press the hardware button twice to wake the screen up
Is it possible to change this in a way you can control how bright the screen is? The lowest setting is '12' that i can get and even that is nearly too bright indoors for me
I havent seen an all that does that
Sent from my Transformer TF101 using Tapatalk
madpuma13 said:
Is it possible to change this in a way you can control how bright the screen is? The lowest setting is '12' that i can get and even that is nearly too bright indoors for me
I havent seen an all that does that
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You should try an app called LUX. It will allow you to drop the brightness below the standard brightness.
madpuma13 said:
Is it possible to change this in a way you can control how bright the screen is? The lowest setting is '12' that i can get and even that is nearly too bright indoors for me
I havent seen an all that does that
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
yup there's an application for that already.
AcIdC0R3 said:
You should try an app called LUX. It will allow you to drop the brightness below the standard brightness.
Click to expand...
Click to collapse
Lux is a pay app and reading description in market says nothing about dimming below stock settings.
Screen adjust otoh actually can lower brightness to zero can also modify color and contrast too. Best of all it's free. Been looking forever for something like this that works in honeycomb as lowest stock brightness is still too bright for nighttime reading for me.
When I unlock my phone (as in push the unlock button) the screen remains black but lightly lit. The bottom four buttons remains lit when the screen is touched. Currently I'm using Eaglesblood 1.5 Rom with latest Trinity 1.1 GHz. I tried using the latest CM7 Kangs and the stable 201 rom with both trinity and faux with and with out overclock and the same thing still happens. Even with a clean wipe it still happens. Currently I have Juicedefender, AdAway, KeyboardManager Launcher, Go Launcher (have used ADW and ADW Ex) running. I have advanced task killer as well but it's not set to autokill.
Does anyone have any suggestions as to what I should do to remedy this problem? If not i'm stuck with the usual battery pull each time the screen goes black. Also I don't think it's a sleep of death because the phone is not frozen as the touchscreen and side buttons are responsive. It should also be noted that the battery is NOT hot when the screen is black.
Also, I'm using an overclock widget that's set to 432000-1100000 screen on, and 432000-750000 screen off. I have tried varying the frequencies too. Should I change my values?
Try uninstalling juice defender. I had issues with a similar app.
Sent from my LG-P999 using XDA App
Overclocking can be handy, but if you set it too high or overclock your phone too much, it could damage the phone itself. I uninstalled my "SetCPU" once I learned that. However, it could just be that there is a hardware fault within the phone that is causing the screen to be black. Maybe the LCD or backlight?
Happens to me too sometimes on both weapon and cm7.2.
I just do a battery pull and hopefully it doesn't happen soon again.
Uninstalling juicedfender seemed to have fixed it for me thanks so much!
jim.k.yee said:
Uninstalling juicedfender seemed to have fixed it for me thanks so much!
Click to expand...
Click to collapse
Awesome. Glad I could help.
Sent from my LG-P999 using XDA App
My nexus has recently been randomly rebooting but not in the normal sense. It will turn off and then when it goes to the reboot screen, the boot animation will have a very dark green tint to it. then after some time the boot animation turns to it's normal colors but them never actually turns on the os, it just stays at the boot animation and I'm actually able to turn the screen on and off during this time. I've tried searching but couldn't find anyone with a similar problem. It seems to me like a problem with my voodoo settings? Anyone have this issue? Currently running cm7.2 with matrix kernel.
Try raising all voltages by +15-25 sounds like your phone doesn't like the undervolt
Sent from my ice cream powered Nexus S
I actually did try this because I was getting a daily reboot (without green screen) before raising all voltages by 50. Will try raising them a little more. Thanks for feedback.
ijrod21i said:
I actually did try this because I was getting a daily reboot (without green screen) before raising all voltages by 50. Will try raising them a little more. Thanks for feedback.
Click to expand...
Click to collapse
If that doesn't work try a different kernel, if its still there it could be a hardware problem
Sent from my ice cream powered Nexus S
Did you also check your INT voltages are high enough?
kernels ; battery ; ROM ; gov/sched
Hi all. Currently running the 10.25 nightly, and I have noticed a couple strange bugs. I would have posted in the big CM10 question thread, but it seems sort of dead at this point.
First, when I turn the screen on when the phone is locked, it starts off dim for a couple seconds and then goes to the correct brightness. Not a huge problem, but definitely annoying.
Second, when scrolling through tabs or windows, and sometimes swiping up and down, I see flashses on the screen of what looks like code or the matrix or something. This is especially pronounced when using Handcent, where whenever I push a key I see the keyboard flash on the screen above the normal keyboard, making scrolling through messages and the message list quite annoying.
Any help would be greatly appreciated.
Are you using auto brightness?
And, is the second thing you are talking about screen tearing?
Are you using a custom kernel or stock
Sent from my HTC One XL
ul49 said:
First, when I turn the screen on when the phone is locked, it starts off dim for a couple seconds and then goes to the correct brightness. Not a huge problem, but definitely annoying.
Click to expand...
Click to collapse
I'm mostly a Sense guy. But the AOSP base ROMs I've tried all do this. When you turn the screen on, it kinda "fades in" instead of turning on right away to the set brightness (this is with auto brightness turned off). Seems completely intentional, and I personally couldn't find a way to turn it off (as I don't like it either).
absolutelygrim said:
Are you using auto brightness?
And, is the second thing you are talking about screen tearing?
Are you using a custom kernel or stock
Sent from my HTC One XL
Click to expand...
Click to collapse
Yes I am using auto brightness. I'm using the custom kernel that comes with CM10. It's sort of like screen tearing, but it's more of a flicker in the background and is not always noticeable. Much more obvious in Handcent, though that might be a separate issue since it's the keyboard flashing in the background.
Hello,
I've run many different AOSP roms and so far each one has given me lock screen issues. When I press either the power button or the home button to unlock, the phone screen stays black but the hardware keys glow. This will keep happening for almost a minute and then it will work normally. Battery pull always fixes it temporarily. Is there an obvious answer to this? Thanks!
Sent from my SCH-I535 using xda premium
Danno131313 said:
Hello,
I've run many different AOSP roms and so far each one has given me lock screen issues. When I press either the power button or the home button to unlock, the phone screen stays black but the hardware keys glow. This will keep happening for almost a minute and then it will work normally. Battery pull always fixes it temporarily. Is there an obvious answer to this? Thanks!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I find I have this problem whenever I'm using a battery saving governor ...such as ktoonservative, smartass etc. Changing to wheatley or pegasusq seems to solve it. Also if I try to set my minimum CPU below 384 it does it along with screen flicker. But that's just me.