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
Seems when im on a call and another call comes in, the screen remains off so I cant see the number or switch over... I have to hit the power button on the side to wake up the screen.. it takes a couple of presses before the screen wakes up... anyone else have this issue?.. any fix?
You're not the only one experiencing this. I noticed this started happening before I even starting installing custom ROMs, and I hoped with Bionix Fusion, it would fix it. Like you, any help would be appreciated from the community.
Sent from my SGH-T959 using XDA App
If you are using the puzzle lock screen, that is the cause.
I actually didnt have this problem until the J16 update. i was considering reverting back, but later decided to wait cause im sure someone in the nerdfarm would find a fix. I await this knight in shinning armor.
I've been having this issue regardless of rom, lock type, and device. Along with a slow or nonresponsive proximity based wake action if I happen to look at the screen during a call. Why is this?
Sent from my SGH-T959 using Tapatalk
beren28 said:
If you are using the puzzle lock screen, that is the cause.
Click to expand...
Click to collapse
I changed the lock screen from puzzle to Android and im still having this 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?
Dear all,
i have a Dell Streak 5, with following specs:
Android Version: 2.2.2
Kernel Version: 2.6.32.9-perf
Build Nr: 15609
The issues are:
- If i use the phone on my pocket with screen to my leg, when i need to unlock screen, i usualy can't, its kind of crashed...
- If i have the wireless ON, and go out from home, usually phone crashes , and when i go to use it, i see there was a reset. Seems that this wireless is kind of instable and make mobile phone crash.
I would like to upgrade something to try to solve this small issues, can anybody help me?
Thank you
Tiago
I forgot:
Baseband Version: GAUSB1A135100-EU
thanks.
I don't know what to tell you as far as wifi crashing your phone. That's never happened to me. As far as the other issue, seems pretty common. I think the recommended "fix" is to not carry it with screen facing your leg. I'm sure that's not what you want to hear....but its the best I got.
i can't explain why you wifi makes your phone crash, but for the impossibility to unlock the screen. i had the same problem, and somebody told me the problem was the heat of the leg that makes the screen tilt. so i bought an otterbox case with a belt clip, so with the screen untouched it works perfectly.
for the screen against leg issue, I just toggle the power off then on and it works.
yes, i agree to lordmorphous, don't face your screen to your leg..
just in case, you may try to calibrate it, or if the problem still, maybe you can re-flash to another latest stock rom.
I have never experienced the screen issues involved with facing the screen towards my leg, and I always put my Streak in my pocket with the screen facing my leg. I guess so far I've gotten lucky.
Strephon Alkhalikoi said:
I have never experienced the screen issues involved with facing the screen towards my leg, and I always put my Streak in my pocket with the screen facing my leg. I guess so far I've gotten lucky.
Click to expand...
Click to collapse
+1......never had screen issue
Guendaline said:
+1......never had screen issue
Click to expand...
Click to collapse
+1 same here..
I had got such issue that can't unlock the screen when I used the official ROM.
But there is not such problem when I use the Power Rom V1.1 now...
Masterzer0 said:
+1 same here..
Click to expand...
Click to collapse
+1 same here
briantamhk said:
I had got such issue that can't unlock the screen when I used the official ROM. But there is not such problem when I use the Power Rom V1.1 now...
Click to expand...
Click to collapse
The ROM makes no difference. I run 360 on my Streak.
I met a guy in a train station, and since there are not a lot ppl with such mob, i decided to ask. In fact, with screen faced outside, the issue finished. Strange..
Related with stock ROM, i think this is my next step: upgrade! the process dell.com.blablabla is always crashing, and sometimes i need to wait to use the phone. awww, not to say that i can't synch with my outlook
I am a bit disappointed with this phone/tab, i was expecting that it could work better.
Any tips on ROM? I am actually trying to use titanum backup to backup data, but it says again cannot root! How i root it?
Thanks again.
Tiago
Everything You Always Wanted To Know About The Streak But Were Too Busy Bricking It
That link there is your first step, for it explains how to root and how to do various other things. Now...I tend NOT to recommend using Titanium Backup since in my experience it screws up when restoring items. Your mileage may vary.
As to a ROM, stick with a stock ROM for now until you are comfortable with the rooting process. I have attempted to use GingerStreak but had a problem with the camera app so I had to go back. Flashing a ROM could fix your issues since a bad flash has been known to be source of the force closes.
Hi again,
finaly i tried a simple method: the gingerbreak, and rooted. Now that is rooted, i want try a diff Android version (from 2.2 to 2.3?).
Is there any recommendation?
Of course first i would like to backup all the data (already from the SDCard) but i am talking about the ContactList (i tried to use the simple: export, but onde again i got an error :/)
Any tips?
Thanks for all the help.
KR
Tiago
I've been having lots of little problems too.
My device randomnly decideds to restart time to time. There doesn't seem to be a pattern to it that I've worked out yet. But it's crashing right now and I have to soft reset it.
Another thing, if I have it in normal landscape mode but turn it on while holding it portrait mode or the screen isn't in the same orientation that it was before the screen turned off, Dell Stage often crashes.
SuperKeeper said:
I've been having lots of little problems too.
My device randomnly decideds to restart time to time. There doesn't seem to be a pattern to it that I've worked out yet. But it's crashing right now and I have to soft reset it.
Another thing, if I have it in normal landscape mode but turn it on while holding it portrait mode or the screen isn't in the same orientation that it was before the screen turned off, Dell Stage often crashes.
Click to expand...
Click to collapse
Exactly, mine restart very often too, but i think i know why. Try disable wireless before leaving your "home network"... in my case, it solves that crashings... only crash if dell stage crashes too... but most of times, its solved.
The only "bugs" i have are: camera button does not work, and when i turn screen on, the "unlock slide button" is ALWAYS in the portrait position.
I wonder, if this is solved with a new android version, or dell "libraries" update?
Thanks.
Tiago
for all those who think the problem does show up when u put it in the pocket facing your leg ..... i had the same view two weeks ago when suddenly i ran into this problem. i think best solution is calibrating the screen .....
zeeshan2341 said:
for all those who think the problem does show up when u put it in the pocket facing your leg ..... i had the same view two weeks ago when suddenly i ran into this problem. i think best solution is calibrating the screen .....
Click to expand...
Click to collapse
Calibrating the screen was what i've done when i could not unlock my mob phone for 1 week, i was desperate
After that, i solved all the screen issues using screen outside and not against leg.
Tiago
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Obscure Reference said:
Hey guys
As most of you probably know, as soon as you select for instance a pin for your lock screen the S4 disables the possibility for lock screen widgets. I'm currently getting around it with xposed and SamsungMultipleWidgets KitKat.
Just curious if there's any way around this limitation without xposed, or maybe even without root? I'm guessing that it's not possible, still.. I'm curious.
Click to expand...
Click to collapse
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
fivecheebs said:
Some ROMs have this feature baked in. SlimKat for instance. I dont believe there is a way whilst using a stock rom without using xposed, at least i never found one, and I looked hard!
Click to expand...
Click to collapse
Yeah, I know.. I had it built in while running CM. Just had an urge to go back to stock for a while and was just wondering what features I wanted actually required root (and xposed).
If anyone else knows of a way, please let us know.
Hi gys, slightly different issue here, but would appreciate any help.
basically the PIN lock does not activate until 30 seconds or so after the phone boots up. So there is no securuty on initial boot up.
Its there if I do a reboot. But not there if I do a startup from fully off.
It used to work but at some point a few ROMs ago t stopped working.
I was told it was the kernel but I have tried 4 and all with the same result and have tried several roms.,