Related
Has anyone else seen this on their screens or know how to fix this or why its happening?
Using Myns Rom, with Battery Tweak, etc etc
What?????????????????????
Actually no pic, the screen shot didnt get the vertical lines..
If the software isn't catching lines, then it's your screen.
Some hardware has lower tolerances with battery tweaks, voltages, etc. Try putting a stock kernel back on it and see if that fixes it.
Sent from my PC36100 using XDA App
i had this issue at first when i was running myns twopointtwo.
i'd boot up and have vertical lines everywhere. If i hit the power button to lock the screen, wait a sec, then hit it again to unlock it the screen would be fine. problem would not reappear at all. its like a momentary glitch i guess.
hope this helps
I have had this issue as well with various Roms lately. After turning the screen off and on it would go away. I've also had other issues such as the phone starting up in car dock mode after a reset, screen auto rotatating even though it's disabled and my media volume not going down after being turned all the way up. I have wiped data, cache, dalvik various times and even ran the latest RUU to start all over but the issues still continue. Anybody else having similar issues ?
nerdmanpap said:
i had this issue at first when i was running myns twopointtwo.
i'd boot up and have vertical lines everywhere. If i hit the power button to lock the screen, wait a sec, then hit it again to unlock it the screen would be fine. problem would not reappear at all. its like a momentary glitch i guess.
hope this helps
Click to expand...
Click to collapse
Same here. Lock the screen, wait a bit, unlock and it stops. Annoying but no big deal really.
Yeah Same thing with me, I turned off the screen and it went away, so weird but it fixed it for now
I forgot, after I saw that , I went into recovery and erased cache, dalvich, etc then I flashed Baked Snackk 1.8 on and still had the issue until I turned screen off then back on... weird
Seems like a lot of us are having the same issue wondering if anyone remmembers when they first saw this happen so we might narrow down the cause to this issue. Mine started after i flashed xxbabiboi228xx rom with kings kernal 11. At first i though it was due to the transition animations, but now i see it no matter what i flash. Not blaming xxbabiboi228xx rom, hes rom is bad ass. Am just pointing out when i first saw this happen.
Sent from my PC36100 using Tapatalk
nerdmanpap said:
i had this issue at first when i was running myns twopointtwo.
i'd boot up and have vertical lines everywhere. If i hit the power button to lock the screen, wait a sec, then hit it again to unlock it the screen would be fine. problem would not reappear at all. its like a momentary glitch i guess.
hope this helps
Click to expand...
Click to collapse
Had the same issue.
its the screen technology.
I JUST exchanged my evo for another brand new one (still within 30 days)
because i had lines going down my screen (Novatech screen).
They were faint yellow lines evenly spread. Got my New evo today and got a different screen (Epson). This screen also has vertical lines.
At the sprint store the 2 evo's on display had the lines however one of them was almost not visible unless u tried to look for it. The other Evo on display looked like mine.
So unless you guys know somethign i dont, i believe this is hardware related.
Theres other forums confirming this.
Both my evo's had hardware 003 but first one was a novatech and this one is a epson.
Novatech screen does look better.
Has anyone found what the issue with this is? I get vertical lines no matter what ROM I flash. I does not happen with the stock RRU ROM though. Got a replacement phone with an EPSON HW 003. Help!
I had the same problem and I found out its the kernal if you have hardware 003 like I do I just use the stock kernal from fresh
Sent from my PC36100 using XDA App
Weird, I have an 003 nova on Fresh 3.4.0.1 and tested the various kernel offerings on here, but been lucky enough not to see this. Is this kinda like the whole screen tearing issue with certain kernels?
mizzos4 said:
Weird, I have an 003 nova on Fresh 3.4.0.1 and tested the various kernel offerings on here, but been lucky enough not to see this. Is this kinda like the whole screen tearing issue with certain kernels?
Click to expand...
Click to collapse
Not sure. I had an 003 before also with an Epson screen which worked flawlessly with any ROM or Kernel I flashed on it. But I guess every phone is different.
Gotta learn to live with it..
mizzos4 said:
Weird, I have an 003 nova on Fresh 3.4.0.1 and tested the various kernel offerings on here, but been lucky enough not to see this. Is this kinda like the whole screen tearing issue with certain kernels?
Click to expand...
Click to collapse
I'm fairly certain the tearing and screen lines/corruption are related.
When I first got my phone a month or so ago, I tried a few different ROMs and kernels. All of the kingx and netarchy kernels I tried exhibited screen tearing, and would more than occasionally exhibit the screen lines/corruption you mentioned . . . sometimes even starting at the boot animation screen.
I was worried I got a bum phone (it was only the second day I had it, so I was a bit noobish) but I flashed the stock kernel (HTC #11) and never had the problem again.
Since then, I've tried a couple newer versions of those custom kernels, and wind up reverting back to an HTC kernel (also tried 10 and what's the latest one? 17?) due to the screen tearing. They just don't like my particular hardware I guess (003 with the Epson panel).
I am also having this same issue, but I am using a stock rom and a flashed kernel.
I had the momentary thing once, don't remember the circumstances, but screen lock / unlock fixed and it hasn't returned. Flashed cm6.1rc1 and after about 20 min. I got real bad, very uneven vert lines plus a flicker that persisted even after reboot. I nanded back to Azrael 2.5 and started using LPP instead of Sense - not CM, but better than the screen from hell! No screen trubs since.
Sent from my PC36100 using XDA App
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.
Hello Guys,
I am having strange issues with backlit of buttons of my Defy.
Backlight was working fine till I was having MS2Ginger ported on my Defy. Then one day i decided to port ICS on my defy. So went ahead and put Epy's CM9. That time backlight was high.
light worked correctly for around 10 days but then light of middle two keys(Home and back) went off... I thought i have burnt the LED's beneath... So i immediately lowered the brightness settings for keys. Then i ported Quarx CM10 in July... Again same case, both of those keys were still down.
This continued till last week when all of a sudden back-lit of Menu key also gone.. I was thinking to take it to Moto care but then again next morning to my surprise, middle two keys got backlit again but lost backlit of search keys... I was wondering what happen, then it started again....
So currently only 3 lights are working Home, Back and search....
Do anyone else have faced such issues?
Regards,
Sam
Get it to the SC. Its a hardware issue.
Needn't really be a hardware problem. Lots of people have reported this issue on Cm9. Could be a bug.
Defy+ 1.1GHz V6 SuperCharged
Running Quarx's CM9
ashoks89 said:
Needn't really be a hardware problem. Lots of people have reported this issue on Cm9. Could be a bug.
Defy+ 1.1GHz V6 SuperCharged
Running Quarx's CM9
Click to expand...
Click to collapse
It's no bug, since it still persists after a flash back to a stock rom.
The custom roms were likely using a higher brightness value and the backlights just died, which could have happened after a longer time on a stock rom as well.
My home button backlight isn't lit anymore either, but the button itself is still working. It's rather a cosmetic problem, so no reason for me to send it off to the repair service.
I bought a used Defy which seems to be also affected by this issue. There the "search" button is not backlit, the others are. It had the Stock ROM on it although I don't know what the previous owner did with it. In fact he only used the Stock ROM this might be a CM-unrelated hardware problem.
Kaffeekranz said:
It's no bug, since it still persists after a flash back to a stock rom.
The custom roms were likely using a higher brightness value and the backlights just died, which could have happened after a longer time on a stock rom as well.
My home button backlight isn't lit anymore either, but the button itself is still working. It's rather a cosmetic problem, so no reason for me to send it off to the repair service.
Click to expand...
Click to collapse
I agree with you!! My Green lens defy has the same issue as home button is almost the black and the back button has very light backlit, the other two keys works fine. I guess that this is because of the over brightness values set by some ROM. I tried flashing the Stock Froyo 2.2.2 ROM and the issue still the same. :good:
Any one have any other idea??
Rajneeshgadge17 said:
I agree with you!! My Green lens defy has the same issue as home button is almost the black and the back button has very light backlit, the other two keys works fine. I guess that this is because of the over brightness values set by some ROM. I tried flashing the Stock Froyo 2.2.2 ROM and the issue still the same. :good:
Any one have any other idea??
Click to expand...
Click to collapse
You can either send it to repair or replace (if you can) the LED's. Its a hardware issue n there could be a no. of reasons for that including high values.
Which means even my backlights have burnt out I was hoping against hope that it was a bug! But then again, it's just a cosmetic issue. I can deal with that. Cuz this phone's super cool!
Defy+ 1.1GHz V6 SuperCharged
Running Quarx's CM9
ashoks89 said:
Which means even my backlights have burnt out I was hoping against hope that it was a bug! But then again, it's just a cosmetic issue. I can deal with that. Cuz this phone's super cool!
Click to expand...
Click to collapse
I also though earlier that my backlights LED have burnt... But they are randomly working... Surprisingly from last 2 days all of my LED's are working fine....:good:
I was also reluctant to send my phone for MOTO SC for a week or two for such small issues....
Guys,I found that this is not really is a hardware issue as everytime i use 2nd init for flashing new nightly all light work properly....
when i tried to dim backlights in cm9 settings 2 months back all lights went off. after flashing some other rom and kernel all worked properly.
at present i am on cm10 and never touched backlight settings, its working fine.
my friend tried to reduce backlight on his defy on cm10, he also lost lights. after doing all exercise what i did, he never regained lights till today.
point to be noted - when we go to backlight settings and move the slider the lights are seen (1 with full intensity and 3 with low intensity) and after leaving settings they never lit.
so it might be some software issue.
good news! lights are working after flashing 2.9.2012 cm10 quarx mb525. try your luck !!!
sasays said:
good news! lights are working after flashing 2.9.2012 cm10 quarx mb525. try your luck !!!
Click to expand...
Click to collapse
Yes they were working for me as well but they were too bright..... So went to button brightness and messed things again....
Now again only two of them are working.....
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. Is there a way to bypass MIUI 9 color calibration? It probably resets my custom kernel color calibration each time when I'm unlocking the screen. I'm using kernel aduitor and colors are very dull despite the fact I set it to quite high values.
What kernel are you using? There are some and you mentioned none...
Also , it has nothing to do with miui's display color settings . It also happens on AOSP roms.
sorry for the necro but I have the same problem.
could it possibly be the issue on KA's end? since my phone is different than yours (I'm using a Mi MIX).
still hoping someone to chime in with a solution though...
CrySpy said:
sorry for the necro but I have the same problem.
could it possibly be the issue on KA's end? since my phone is different than yours (I'm using a Mi MIX).
still hoping someone to chime in with a solution though...
Click to expand...
Click to collapse
Apply on boot needs to be on...
Those are some settings that don't remain because are reseted every time the kernel boots...
It's not an issue , it's normal behavior.
alexmanu1 said:
Apply on boot needs to be on...
Those are some settings that don't remain because are reseted every time the kernel boots...
It's not an issue , it's normal behavior.
Click to expand...
Click to collapse
well of course I do.
the screen settings reset every time the screen is off. Had to actually go in through KA itself and adjust (at least) single value back and forth till it applies again.
CrySpy said:
well of course I do.
the screen settings reset every time the screen is off. Had to actually go in through KA itself and adjust (at least) single value back and forth till it applies again.
Click to expand...
Click to collapse
Oh, yeah...
Sorry , i didn't paid attention to the problem that much ?
It's clearly a bug , but i don't know how to solve it , sincerely...