Related
I have this problem when i lock the screen.. it started when I installed franco.Kernel [with kwiboo ICS rom], but after flashing BM ICS rom and a new kernel GLaDOS it's still there.. : /
Any help?
In the voodoo app. Reset all the color settings
Sent from my Nexus S 4G using XDA App
I turned screen on animation and it didn't do it again. Very weird.
noble69 said:
In the voodoo app. Reset all the color settings
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
You mean "Voodoo Control" from the market?
I reset everything in the color profile but i still get a flash.. not a green/yellowish, the clock and the "lock circle" flash..
And now the colors sucks. xD
do u have deep idle enabled??...i have the same issue when i have deep enabled..
Sent from my Nexus S 4G using XDA Premium App
neo_x22000 said:
do u have deep idle enabled??...i have the same issue when i have deep enabled..
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Where can i find it?
[noob here]
I'm on BM ICS Mix v4 with franco kernel.. I have exactly the same problem.. Messing with Voodoo App didn' help.. Flashing Glados kernel didn't help..
Same thing happen on Matr1x?
Sent from my Nexus S using XDA App
im sure everyone has this bug, but i just turned off window animations in spare parts for now, its much less noticable
Is this problem solved? I'm still getting it (the screen flash on screen off) with glados 2.4 nexus s 9020t..
Anyone know?
I get it while screen off, not on.
On neopolitan + glados 2.4
Im on crossbones and glados and it does the same thing.
I was having it too with GlaDOS. Just download Voodoo Control, go to Screen v1 gamma offset colors and set everything to 0.
ya just reset it to default 2.3.3
juliano + sceptor: The screen flash improves and happens less frequently after setting voodoo back to default 2.3.3 but it still happens. Also, if you use a live wallpaper, the greenish flash gets worse when turning off the phone (and yes, sometimes on). So with 2.3.3 default voodoo and a static wallpaper, I only get the flash 1 out of 5 times maybe...
But still.. anyone NEVER get that screen flash? I'm about to try official, signed google ics (instead of drewgaren ics) and then rooting and using glados 2.4 again.. But if anyone has already done that, please share your experience...
How can we get rid of that screen flash?
I was just playing with the stock ICS ROM earlier, not using any custom kernel or anything, and the screen started to exhibit the "green flash" after installing the Voodoo Sound drivers.
This really doesn't seem like it makes any sense at all, because this was the stock Android 4.0.3 kernel. It has no Voodoo Color support whatsoever. But up until I patched in the Voodoo Sound drivers, there was no flash.
After patching Voodoo Sound, green flash.
I have had the screen off flash on every ics rom / kernel I have used, u get the screen off animation, screen goes black, then I get a flash of what was displayed on screen before I hit the power button. This is with and without voodoo on my i9023. It happens a lot less with the kernel listed in my sig (speedy 2), but it is still present. Its very annoying and looks crap!
---------- Post added at 05:20 PM ---------- Previous post was at 04:57 PM ----------
Link to vid of screen off bug:
www.youtube.com/watch?v=kRub7rhwiZ0&feature=youtu.be
I noticed when I set the screen RGB multipliers /gamma to very low values the green flash occur during screen on & off animation, once I set it back to default or higher values the screen greenish flash goes away.
Hi.. I think I've found a working solution to this annoyance...
1) turn off auto brightness
2) manually adjust it to the lowest value
3) restart the phone
the flicker should be gone!
My setup:
Nexus S (T) 4.0.3 Stock
Static wallpaper
PIN code lock screen
If you can live with the 'dim' screen, you should be happy now just like me. Hope an official fix will land soon.
Doesn't work on mine, tried before, screen still flickers.
Running AOSP+ with Eugene's kernel.
theexel said:
Doesn't work on mine, tried before, screen still flickers.
Running AOSP+ with Eugene's kernel.
Click to expand...
Click to collapse
One of the sources for screen flicker is increased screen hz , combined with improper voodoo color configs and also some CPU govs cause it also
Sent from my Nexus S 4G using Tapatalk
Nexus HAL said:
Hi.. I think I've found a working solution to this annoyance...
1) turn off auto brightness
2) manually adjust it to the lowest value
3) restart the phone
Click to expand...
Click to collapse
Turning. Off auto brightness only resolves the green screen not the flicker when taking phone out of standby
Also no need to reboot.
Its color driver for voodoo with ICS
People here said supercurio working on voodoo color 2
Temp solution up your gamma settings with voodoo color plus or get a kernel that has "colorfix" gamma setting is locked at setting
the gamma setting required to get rid of this problem is too high for my taste
i can live with the millisecond flicker for all around better colors doesn't bother me its not going to damage anything
gamma too high makes colors less vibrant.
sorry guys... false alarm. apparently i jumped to the conclusion too early. the problem is back again since this morning
ps: i was running unrooted stock 4.0.3 but thanks for the technical details guys. it helped me understand what's actually happening under the hood. cheers!
matrix kernel 14.5 with lag free gov has eliminated this problem almost completely for me.
Also doesn't work on mine.
[v7][ROM] KANGYS | ICS | AOKP | Fastest & Most Stable | 15/01/2012 With Matrix 14.5 kernel.
Please try this rom / kernel combo, u will see the difference.
LOL guys that say that "Matrix fixed the issue".. You do realize that he deleted Voodoo completely right?
Doesn't work, running AOSP+ rom with Speedy.
Don't think its a voodoo issue as it happens on stock rom / kernel.
Lirankn said:
LOL guys that say that "Matrix fixed the issue".. You do realize that he deleted Voodoo completely right?
Click to expand...
Click to collapse
You do know that Supercurio himself has said that people should stop using Voodoo Colors?
EDIT: Steve Garen has also removed Voodoo colors and its freaking awesome.
*if you didn't wipe /system and /boot it is NOT A FULL WIPE*
Lirankn said:
LOL guys that say that "Matrix fixed the issue".. You do realize that he deleted Voodoo completely right?
Click to expand...
Click to collapse
if voodoo was removed completely from his kernels then we wouldn't be able to adjust any color setting in voodoo app not to mention the the settings wouldn't even be available
and that's not the case with both kernel version
like i said before lowering gamma will cause green flicker
Color fix kernel doesn't allow gamma adjustment thus no more green flicker granted not an actual fix but it is for his kernel and saves him from headaches from users who don't know how to troubleshoot themselves
The other color kernel gamma and RGB can be adjusted but expect green flicker when lowing gamma
actually there are 2 things ... one is the green flicker which is experienced when using Voodoo colors with low Gamma and another is just a quick flash of the screen when locking the phone i've seen it on my all stock ics too it happens sometimes not always just a split second after locking the device
removed my comment
ill take your word if its intermitting can be tricky to reproduce i didn't give enough time
haven't used stock for while that's why i had to test again so maybe it did before just don't remember
irizwan said:
actually there are 2 things ... one is the green flicker which is experienced when using Voodoo colors with low Gamma and another is just a quick flash of the screen when locking the phone i've seen it on my all stock ics too it happens sometimes not always just a split second after locking the device
Click to expand...
Click to collapse
Yeah, on SG's kernel I've got no green flash but I do get the slight flicker. It doesn't bother me like the green does though. Its really brief and since I use an all black background and keep the brightness low I hardly can notice it.
*if you didn't wipe /system and /boot it is NOT A FULL WIPE*
Wtf I never deleted voodoo xD
Sent from my Nexus S using XDA App
irizwan said:
actually there are 2 things ... one is the green flicker which is experienced when using Voodoo colors with low Gamma and another is just a quick flash of the screen when locking the phone i've seen it on my all stock ics too it happens sometimes not always just a split second after locking the device
Click to expand...
Click to collapse
Its the quick flash after locking is what In am in about, matrix fixes this 90% of the time.
And more specifically and as far as I can tell, if the phone is freshly booted then the functions listed above work. However, after several hours on I go to adjust the brightness and the screen does NOT change its brightness no matter whether i set auto-brightness or adjust it manually.
Let me preface this topic and let you all know that I still have my stock screen protectors attached and I've installed the light flow app if that matters.
Any ideas?
EDIT: I such at naming titles.
same here, just wiped. no clue what's causing it
Same for me I just noticed this. Hope its something fixable in an update.
Sent from my Nexus 4 using xda app-developers app
i don't have this problem, auto brightness and slider always work
Auto brightness doesn't work
I am having this problem too... Works for the first while, then doesnt work at all...
*** Ive commented on a logged issue with google, ISSUE 40378
https://code.google.com/p/android/i....2&colspec=ID Type Status Owner Summary Stars
I uninstalled ledblinker and it seems to solve the problem. Do you guys use lightflow? That might be the culprit
ceejay83 said:
I uninstalled ledblinker and it seems to solve the problem. Do you guys use lightflow? That might be the culprit
Click to expand...
Click to collapse
It doesn't make a difference if I use lightflow or not it just won't act right.
Sent from my Nexus 4 using xda app-developers app
Jefferyrbrown1983 said:
It doesn't make a difference if I use lightflow or not it just won't act right.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Have you tried wiping? I haven't had any issue since
Ugh never mind, brightness got stuck again.
Wow am i glad to have found this thread, i have been battling this problem since day one with this phone, and i have been trying to track it down with usb debugging but have been unsuccessful. What happens is that my screen will randomly shut off and be non responsive for 5 seconds and when i can turn the screen back on, i can no longer adjust the brightness and only a reboot will solve the issue. It also occurs when i am not using the phone so i think it is a hardware issue but i am uncertain.
Things i have tried to fix it:
Factory reset
Fastboot flash factory image
Flash cutom ROM & Kernel
Didn't realize it before but yes, my screen randomly turns off, then the brightness gets stuck. Thought it was timing out
---------- Post added at 03:52 PM ---------- Previous post was at 03:46 PM ----------
You guys use auto brightness? Maybe that might be it
This happens to me occasionally too, haven't been able to determine what triggers it. It's almost as much fun as the magical battery levels. Plugged in the other day, went from 4% to 100% in a nano second.
interesting...my auto and slider work just fine
ugh still getting this problem daily. does't matter if auto brightness is on
There is no solid way to reproduce the problem, so I am willing to bet its a hardware issue. I will be calling T-Mobile this week to replace it.
Sent from my Nexus S
Of the people who are experiencing it, how many have a notification drawer widget (Widgetsoid, Power Controls, et al?) and have a brightness toggle on it?
I've removed brightness from Widgetsoid to see if it's a conflict of some sort.
CMNein said:
Of the people who are experiencing it, how many have a notification drawer widget (Widgetsoid, Power Controls, et al?) and have a brightness toggle on it?
I've removed brightness from Widgetsoid to see if it's a conflict of some sort.
Click to expand...
Click to collapse
Yes I'm using power controls. Still does it even if I disable the brightness toggle
Hmmm...wonder if there's a submission on Gerrit, shall troll later.
Sent from my Nexus 4 using Tapatalk 2
CMNein said:
Hmmm...wonder if there's a submission on Gerrit, shall troll later.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Might be a hardware issue? If it was software I think a lot of people would be complaining about this.
Edit: ugh as I was typing this post, screen flashed and turned off with broken brightness. I just rebooted like 5 min ago too
ceejay83 said:
Might be a hardware issue? If it was software I think a lot of people would be complaining about this
Click to expand...
Click to collapse
Not sure. Here's one report on Google Code: http://code.google.com/p/android/issues/detail?id=40378
Edit: could just as easily be a OS issue, if it decides to stop polling the light sensor for some reason. Many people have the battery bug as well, which seems to stop polling the battery for some reason.
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
nmunro said:
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
Click to expand...
Click to collapse
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
brandonc0526 said:
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
Click to expand...
Click to collapse
I also sometimes get lag when I do manage to unlock, scrolling through my screens is very laggy for 5-10 seconds, then it is usually fine.
I have a problem with lockscreen lag on a phone with a quadcore CPU and 2 GB of RAM.
Flash a custom kernel. You'll be less likely to experience lag
Don't get any lockscreen lag on my stock Android.
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Have any recommendations?
nmunro said:
Have any recommendations?
Click to expand...
Click to collapse
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
username8611 said:
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
Click to expand...
Click to collapse
Trying this out now. I especially liked how it told me my system was corrupted once it finished flashing...
First thing I've noticed is that the colour is a lot different. Do I need to play with any settings, or do I only need to have the kernel installed?
Also how often do updates come out?
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
username8611 said:
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
Click to expand...
Click to collapse
The colours bothered me so I'm trying the latest franco nightly. It seems to be at the stock clock speed, no weird colours, and it makes the haptic feedback when unlocking feel more like the GNex.
I'm still having this issue with franco kernel. I've been looking around a bit and people seem to say this is related to auto brightness. I'm going to turn auto brightness off for a bit and see if it still happens.
Also, does anyone know if using a 3rd party app for auto brightness would make any difference?
Okay, turns out auto brightness wasn't the issue. Still getting lockscreen lag. Help please.
If I put 5 fingers on the screen (when the screen is off), then press the lock button, when the screen comes on it will be completely unresponsive, some of the time. I'm not always able to replicate this.
for me, some releases of Franco have lockscreen lag, some don`t, try flashing the M2 or other post r121 builds, they are all great performers and maybe you`ll get lucky with one.
if ur using paranoid android, then its a stability issue i guesa cause the same thing used to happen with me...... or else try franco kernel... or update franco kernel if ur using franco, cause an older version had the lockscreen bug, which is now fixed!!!
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Flash a stock kernel. You'll be less likely to experience lag
I'm running CM 10.1 and the latest version of franco's kernel.
I've tried using a rooted stock and I had the same issue with lag.
I'm going to try franco's milestone build, see if I still get issues.
Would increasing the minimum clock likely help at all?
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Good Guy Mark said:
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Click to expand...
Click to collapse
I'm thinking this may have been the issue.
How does the replacement process work?
If I save a nandroid backup of my phone, can I just unlock it and restore from there?
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
meangreenie said:
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
Click to expand...
Click to collapse
Can I just flash this with CWM? And then flash back to franco m2?
I actually just got an RMA for my phone, because of this issue and that the back glass panel is a little loose and makes creaking noises. When I send the phone back to google, if I follow all the steps here and lock the bootloader, it should be fine to send back to them?
Google's RMA process was amazing. Took me all of 10 minutes. They're shipping a new one in 3-5 days, and they pay for the return shipping of my old device. The replacement is brand-new, not a refurbished device. My dad's iPhone 4S had a bunch of issues and he would have to book an appointment at the Apple store, which happens to be an hour away, and they would only replace his device with a refurbished one.
Hi guys I have a problem on my s8.
Auto brightness always worked for me, but I just noticed that now it stopped working at all. Like, usually if i set brightness to max and then set autobrightness on, it auto reduces it to like 25%, meanwhile now it doesnt change the brightness ever. I have the feeling that auto brightness stopped working after i installed the last patch with odin (the UK unbranded one) since I patched it like 4 days ago and in the past weeks it worked fine. I dont think its a hardware problem because I tried sensor box app and in a black room it shows 0 while in a light one it goes to over 100 and next to a lamp over 2000.
Any idea what could be the problem? And how to fix it? I really would hate to do a hard reset since i'd lose too much stuff... could it be the patch that has a bug? Thanks in advance!
tharghan said:
Hi guys I have a problem on my s8.
Auto brightness always worked for me, but I just noticed that now it stopped working at all. Like, usually if i set brightness to max and then set autobrightness on, it auto reduces it to like 25%, meanwhile now it doesnt change the brightness ever. I have the feeling that auto brightness stopped working after i installed the last patch with odin (the UK unbranded one) since I patched it like 4 days ago and in the past weeks it worked fine. I dont think its a hardware problem because I tried sensor box app and in a black room it shows 0 while in a light one it goes to over 100 and next to a lamp over 2000.
Any idea what could be the problem? And how to fix it? I really would hate to do a hard reset since i'd lose too much stuff... could it be the patch that has a bug? Thanks in advance!
Click to expand...
Click to collapse
I have similar issue with my phone after latest update. I did hard reset without luck. All we have to do is to wait until new patch will be released and hopefully fix this issue. Regards
Sent from my SM-G950F using Tapatalk
ojkajoj said:
I have similar issue with my phone after latest update. I did hard reset without luck. All we have to do is to wait until new patch will be released and hopefully fix this issue. Regards
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
I'm really surprised that Samsung will go live with a firmware with bugs like this, I guess they really dont test anything.
I think is the same for me ! With AQG5 firmware (the last one) when you change the brightness with auto brightness on, the phone memorise the setting with the ambiant light condition : you can see it by doing the following : turn auto brightness on and then set brightness up or down. Then uncheck auto brightness of and place the curser at the opposite. At last put auto brightness back on and the brightness will jump where you put it before like the phone memorised it.
Also with auto brightness on you can put your thumb on the sensor in the upper left side of the phone to simulate darkness. The screens goes darker and as soon you remove your thonger he goes lighter.
I dont understand why just some of us have this problem. They should released a fix soon because its really annoying not to have it working, I dont want to have to wait a month or more like this...
It pissed me off so I downgraded to AQF7 : the issue is now gone =)
Same thing over here!
The AQF7 update was by far the best and most stable one to date. Now my home button problem is back and lag also!
Before it I had home button issues with response and lag whille scrolling. Whit the current update everything came back!
Samsung really needs to get their s*** together!
Well... when they released the AQH3 in the changelog it said they fixed the auto brightness thingie, yet I just installed it and guess what? I still have the same problem. Auto brightness still doesnt work, like in the firmware that came out a month ago.
Anyone else tested it? What the **** is Samsung doing?
No one tried yet?
I agree with you, the autobrightness still doesn't work.
Sent from my SM-G950F using Tapatalk
Any way to fix this? I am using an app called lux, but it's not perfect, still better than nothing
I have the same problem. I saw another thread that said it's not a bug. They made it that it learns your patterns, so it won't change when you hit the auto brightness button, but it still does become brighter when you go outside, and dimmer when you go inside.
I'm not happy with it though, as it worked perfectly for me before this update, and this is just very annoying.
Atomsk said:
Any way to fix this? I am using an app called lux, but it's not perfect, still better than nothing
Click to expand...
Click to collapse
What build/baseband/firmware are you running?