Database Users

Vertical Lines on EVO.. Pic Inside

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

I can't unlock the screen with Gingerbread

I tried several ROMS on my Nexus, but there is a failure on all ROMS with Gingerbread. If the screen remains locked for a few minutes, I can not unlock it (do not turn on) and not let me restart or shut down the phone, I can only remove the battery and wait about 10/20 minutes to the phone automatically restarts.
I happened to CyanogenMod 7 (RC1 and RC2) and LeoGingerBread (both downloaded from this forum)

r0uzic said:
I tried several ROMS on my Nexus, but there is a failure on all ROMS with Gingerbread. If the screen remains locked for a few minutes, I can not unlock it (do not turn on) and not let me restart or shut down the phone, I can only remove the battery and wait about 10/20 minutes to the phone automatically restarts.
I happened to CyanogenMod 7 (RC1 and RC2) and LeoGingerBread (both downloaded from this forum)
Click to expand...
Click to collapse
Try one of the rooted stock ROMS. Make sure to do a complete wipe first.

Rod3 said:
Try one of the rooted stock ROMS. Make sure to do a complete wipe first.
Click to expand...
Click to collapse
Thanks, in a couple of hours notice if I have failed the stock rom

I just tried the stock rom GRI40 and I was not locked, so I guess it will be the kernel in CM7.

Not having that problem at all on stock GRI40; by the way, i'm having an odd issue with GRI40 & Gingerbread. The time to auto-lock the screen uses to change by itself; i think it's on 2' by default, but i changed it to 30' on screen settings and also on Widgetlocker settings...well, once a day, the time changes to 2' again. Anybody else having the same issue? Ideas?

Sounds to me like more of a hardware failure. I have never had any problems unlocking my screen.

This has happened to me a few times.
Possible reasons:
1)bad custom kernel where the buttons dont work. (menu to unlock)
2)bad setcpu setting. i.e. max cpu at 300MHz when the screen is off
3)cpu pegged at 100%, If its at 100% for a certain amount of time the system auto reboots. Happens many a time with CM7 build 14 and words with friends for me.

Make sure u wipe. I've had stock rooted GB and many Cyan nightlys and RC 1&2 and never had this problem. Do you use trackball wake? Configure lockscreen settings in cyan settings. They also use gestures as well if the problem persists. Hopefully one of these options helps u out. BTW I usually wipe everything.
Sent from my Nexus One

Know-Fear said:
Sounds to me like more of a hardware failure. I have never had any problems unlocking my screen.
Click to expand...
Click to collapse
britoso said:
This has happened to me a few times.
Possible reasons:
1)bad custom kernel where the buttons dont work. (menu to unlock)
2)bad setcpu setting. i.e. max cpu at 300MHz when the screen is off
3)cpu pegged at 100%, If its at 100% for a certain amount of time the system auto reboots. Happens many a time with CM7 build 14 and words with friends for me.
Click to expand...
Click to collapse
I doubt it is a hardware failure does not happen to me with Eclair, Froyo or Gingerbread stock, just happened with CM7
Buck Shot said:
Make sure u wipe. I've had stock rooted GB and many Cyan nightlys and RC 1&2 and never had this problem. Do you use trackball wake? Configure lockscreen settings in cyan settings. They also use gestures as well if the problem persists. Hopefully one of these options helps u out. BTW I usually wipe everything.
Sent from my Nexus One
Click to expand...
Click to collapse
I don't use trackball wake, but my nexus is completely blocked, even if I press the unlock button, and I wipe everything before to flash CM7

Slider unlock sometimes doesn't work with incoming call

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?

[Q] automatic brightness

Hey all, I searched but didn't come up with anything. I have an S4 Active and it is still on the AT&T bloatware. But its rooted and I used Titanium Backup to freeze a bunch of the AT&T bloat and Samsung stuff that I never use. I didn't freeze any google or com stuff, so I think it is unlikely I froze whatever controls it.
I only had the phone for a day before I did this, so it could be I never noticed it before and its done it since new.
But now, 5 days into owning the phone I notice that automatic brightness always sets the screen to the lowest brightness level, regardless of ambient light. I only noticed because I spent a lot of time in the sun Friday and Saturday and noticed I had issues seeing the screen until I turned off automatic brightness.
Is this a known bug with these? Is is possible I froze something that controls this?

OK, using the *#0*# dial screen shortcut I was able to verify that the light sensor is working as it should. I have tried rebooting, and factory reset isn't an option for me.

I've seen kernel functions mess up after rooting sometimes. Try flashing another kernel, maybe a custom kernel compatible for your phone.

ilabs said:
I've seen kernel functions mess up after rooting sometimes. Try flashing another kernel, maybe a custom kernel compatible for your phone.
Click to expand...
Click to collapse
Thanks for the feedback.
Not sure there is a custom kernel for this phone yet, as I'm not sure that the regular S4 kernels will work for it. But I'll look into it.

over2land said:
Thanks for the feedback.
Not sure there is a custom kernel for this phone yet, as I'm not sure that the regular S4 kernels will work for it. But I'll look into it.
Click to expand...
Click to collapse
Try going back to stock unrooted firmware and see if the issue still persists. I think it might be tied to root coz some other features like allshare also break with root, and root works at the kernel level. You could check on the thread from where you got the rooting method, maybe others are having the same issue.

Freezing issues/Best ROM similar to RR?

Recently I've been having a bit of issues with the Official MM RR rom, the BlackMix one. This happened after I decided to try a different kernel; I had been using the yarpiin kernel.
It started with apps slowing down and eventually crashing whenever I changed the volume with the volume keys. The app would freeze, and then eventually ask me if I wanted to close it. It went away after I changed the volume overlay dismiss time to a higher setting.
However, sometimes the device will just freeze for no reason, and refuse to respond to any inputs. It'll just hang at the screen I'm on, and then eventually the screen will just go black with the display still on. Then it will reboot. I think this is basically one of those random reboots people experience. Is this exclusive to RR? I had it back on my old Droid Turbo that was on RR too.
And then sometimes apps will also just freeze for no reason and refuse to respond to any navbar inputs. Pulling down the notification shade or locking and unlocking will fix it, but it happens frequently enough to be annoying.
So basically, my question is, is there another ROM similar to RR in terms of features and customization that I could try? Also, are there any fixes that I could try to alleviate these issues. My current ROM and kernel setup is absolutely perfect besides these issues and I would love to keep it this way if at all possible.

Latiken said:
Recently I've been having a bit of issues with the Official MM RR rom, the BlackMix one. This happened after I decided to try a different kernel; I had been using the yarpiin kernel.
It started with apps slowing down and eventually crashing whenever I changed the volume with the volume keys. The app would freeze, and then eventually ask me if I wanted to close it. It went away after I changed the volume overlay dismiss time to a higher setting.
However, sometimes the device will just freeze for no reason, and refuse to respond to any inputs. It'll just hang at the screen I'm on, and then eventually the screen will just go black with the display still on. Then it will reboot. I think this is basically one of those random reboots people experience. Is this exclusive to RR? I had it back on my old Droid Turbo that was on RR too.
And then sometimes apps will also just freeze for no reason and refuse to respond to any navbar inputs. Pulling down the notification shade or locking and unlocking will fix it, but it happens frequently enough to be annoying.
So basically, my question is, is there another ROM similar to RR in terms of features and customization that I could try? Also, are there any fixes that I could try to alleviate these issues. My current ROM and kernel setup is absolutely perfect besides these issues and I would love to keep it this way if at all possible.
Click to expand...
Click to collapse
Try Exodus. It's AOSP + CM based & the most stable MM rom I've tested.

B!Gguy said:
Try Exodus. It's AOSP + CM based & the most stable MM rom I've tested.
Click to expand...
Click to collapse
What kernel do you use for it? I'm gonna go ahead and try it.

Latiken said:
What kernel do you use for it? I'm gonna go ahead and try it.
Click to expand...
Click to collapse
No custom kernal. Stock one's good enough.