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
Related
IF somebody know the inverse option on photoshop when black comes as white and same for all colors it happens to my hd2 after a while when I unlock is cuz I press harder on it or is a soft problem?
I've seen a few people reporting this, luckily haven't experienced it myself. Nobody seems to have figured the cause as yet, but a reboot solves the issue (until the next time of course).
I had inverted colours recently. Was weird... I was on the phone when it dialed another number (possibly i did it with my cheek cos i'd been switching back and forth from keypad and loudspeaker settings). When i hung up my phone went strange with the 'inverted' look.
I'd love to know why because it's the only stability issue I have now.
Regards
sp33dy_gtx said:
IF somebody know the inverse option on photoshop when black comes as white and same for all colors it happens to my hd2 after a while when I unlock is cuz I press harder on it or is a soft problem?
Click to expand...
Click to collapse
This happened to me as well. I had to give it a restart. It happened after I waked the phone from screen off. It would be nice to find a fix for this.
Edit: we are not alone: http://forum.xda-developers.com/showthread.php?p=10851646
+1
Hope it is just a soft prob and not a sign of hardware fail.
TheATHEiST said:
+1
Hope it is just a soft prob and not a sign of hardware fail.
Click to expand...
Click to collapse
Haven't tried it myself, but they say taking a screenshot creates a normal looking one.
So I'm afraid it is a sign of hardware fail. The bad thing is my phone is barely 2-3 months old.
edi: could you all please post the kernel you have. From what I've read, it seems an MDJ kernel problem. I used MDJ 0.2oc
I had this a few times before Xmas on one of Darkstones SD builds, only did it 4 or 5 times though. Taking a screenshot didn't work, just got a normal screen.
Since using NAND builds I've not come across this problem once, so I'm guessing the problem is Software/Kernel related rather than Hardware, which should come as a relief.
Sent from my HTC HD2 using XDA App
Did anyone find a fix for this?
I am using prj Clean Desire v0.3.2 (NAND) [Kernel: prj v0.4] and am getting the same issue, unlock the phone and everything is inverted but taking a screenshot with drocap2 comes out perfectly normal. It is happening every few days now.
I am going to try a different ROM and see if it still occurs.
Never had inverted colors in WinMo, with first Android SD releases I've had that problem quite often. But since flashed NAND Android 45 days ago haven't seen any inverted colors yet.
Sent from my HTC HD2 using Tapatalk
Had this problem today for the first time while in a call. A reboot put it back to normal...
Any known reason?
hyperdroid 2.1.0
I get this error occasionly on hyperdroid 2.1.0 but it happened to me again today.... its also happened on miui. No one found a solution or cause?
I have had this on various occasions and there i various topics on it but with no resolution of any answer as to possible cause.
Hey,
I've got the HD2 running extremely smoothly with the NexusHD2-Gingerbread v2.2 build.
Since moving to android and trying out WP7 I have been experiencing an issue where after a whole day of running perfectly I will turn the screen on to find everything is washed in white - it's like the screen turns greyscale but in white so everything is still visible and works but in white.
i don't seem to be able to find this problem anywhere else but it has happened with all the android nand roms and the WP7 rom - a soft reset fixes the issue. I'm currently using radio Radio_Leo_2.15.50.14 and have switched around but haven't found one that fixes the problem...
Any thoughts on what could be causing the problem??
Thanks, Luke.
I have the same problem sometimes. Will be glad if someone can explain!
Ive also experienced this, disappears after reboot or sometimes if i turn the screen on-off a couple of times, kinda weird.
Glad to see others are having this problem - seems to be so rare but I cannot find a solution. Would be interested to see if it still occurs now with standard wm6.5.
Anyone else experiencing this or have some idea of a fix?
i too have this problem.many times screen just go off like greyscale.can anyone help?
One more with the same problem...
Never had it with my currentrom (Hyperdroid) until I've read this thread.
Bump for wisdom.
Are you morons really that stupid
Get the screen out of the sun and away from hot surfaces you dumb bastards and it wont happen, it isn't a nand but a screen issue.
With stupidity like that you will be admins of XDA in no time
ALL_XDA_MODS_R_C*NTS said:
Get the screen out of the sun and away from hot surfaces you dumb bastards and it wont happen, it isn't a nand but a screen issue.
With stupidity like that you will be admins of XDA in no time
Click to expand...
Click to collapse
Erm what the f*ck? No need for that. Any actually, it's not a screen issue, it's an issue in earlier ROM's (well from what I've experienced). Like flash Cotulla's Desire ROM and it happens a lot. I presume you don't really like XDA due to your username? Banned maybe? Why would you even bother making a new account and just trollin'? That's sad, lol.
I only had it when the first batch of ROM's came out. Never withing the past month and a half.
It's like the screen goes negative.
But yeah, there isn't a clear fix for it AFAIK, you should back-up everything on your ROM and try an up-to-date ROM and see if it's still happening. I doubt it.
having the same problem as well
usually happens after i wake up, so during its idle time which is kinda strange
i also noticed it started happening after i installed cracked widget locker, any of you using that?
It happenes to my phone quite regulary but only running android roms, i think around september 2010 it happened the first time. I suspeced my phone, but even after getting a new hd2 it happens sometimes. It usually just happens randomly, not after specific actions. Sometimes it stays only for some minutes and sometimes it can be only fixed with a reboot.
I'd really like to know when this bug will be fixed.
I was having exacly the same issues with my old build. But since im using CoreDroid this problem has dissappeard.
+1 I've only experience this twice, and not since December, but I found it weird both times. I think both times were during a phone-call. A reset worked.
ALL_XDA_MODS_R_C*NTS said:
Get the screen out of the sun and away from hot surfaces you dumb bastards and it wont happen, it isn't a nand but a screen issue.
With stupidity like that you will be admins of XDA in no time
Click to expand...
Click to collapse
Wow...another keyboard hero....you are so brave typing that, we are all in awe of how awesome and manly and strong and tough you are!!
ANYWAY......STFU...it's not a screen problem.
I too have this problem, and it is my 2nd HD2 and happens VERY rarely, but does happen and has happend on both of them.
OH, and Mr Tough Guy....I live in the UK...VERY rarely get warm weather over here, so it AINT the sun.
You, Sir = FAIL.
Matt
Same here happens once or twice a month no big deal though
Sent from my HD2
I'm currently running imilka's RAM Desire HD v2.0 since a month or so, the pale screen appears sometimes up to 2-3 times on one day and then not for several days. A reboot allways fixes it, sometimes it fixes itself after some minutes.
But i really find it annoying.
This happened to me in most desire/desire hd sense builds.
Now, I use the official hd2 MIUI and gingerbread seems to solve the issue.
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
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.
Now it started to annoy me. I have francos kernel and Pa. Also installed the touch screen mod.
My nexus is restrarting sometimes not responding many times in a day. Restarting happens after installing an app, while playing a game, while browsing... I cant tell an exact thing. And sometimes after locking the screen it doesnt respond and reboots with holding lock button after a few seconds. Installed antivirus and nothing found. Havent tried factory reset.
Also i broke my front screen 3 months ago sent to lg and they send me my phone with new screen.
If you look your screen carefully under light you can see small circles. Mine is now different. Any ideas?
Are you undervolting too much? Increase it by +25 - +50 and see how it goes.
Sent from my Nexus 4 using Tapatalk 2
I don't think LG repairing the screen has to do with the restarts. Maybe you should get a log cat and post it on PA's bug site. I did that and the devs reply pretty quickly. Use Catlog from the app store have it recording and when a crash happens boot up your phone and save the logcat and upload it to PA.
Trying +25 voltage
Peirs said:
Trying +25 voltage
Click to expand...
Click to collapse
Did you even have it undervolted to begin with??
I noticed you said that you have the touch screen mod, I'm assuming that you are referring to the older Synaptics driver, E015. I had a random reboot the one time I tried it (unless that was because I was simultaneously doing UV testing). If changing your voltages doesn't fix it, try reverting to the current driver. You can do this by removing the script that you are using to install it after every reboot.
+25 volt and uninstalling the mod didnt help. Restarted again while playing with drum app.
Installing log cat
Peirs said:
Now it started to annoy me. I have francos kernel and Pa. Also installed the touch screen mod.
My nexus is restrarting sometimes not responding many times in a day. Restarting happens after installing an app, while playing a game, while browsing... I cant tell an exact thing. And sometimes after locking the screen it doesnt respond and reboots with holding lock button after a few seconds. Installed antivirus and nothing found. Havent tried factory reset.
Also i broke my front screen 3 months ago sent to lg and they send me my phone with new screen.
If you look your screen carefully under light you can see small circles. Mine is now different. Any ideas?
Click to expand...
Click to collapse
Try going back to stock ROM and kernel with no apps/mods and see if the problem persists, if it does you might need an RMA, if not its a software issue
Sent from my Nexus 4