Running CyanogenMod 6.1.2 - 0.10, fastboot with boot2.img, Go Launcher Ex.
Anybody has a problem with the top half of the screen being unresponsive? For example, I can't scroll between screen flicking on top half of the screen. But the bottom half would work.
The HW is fine, because if I tries to drag an icon from the bottom half, I can move it freely to the top half of the screen no problem.
In google map, I can rotate my device to landscape, and the problem rotates with it. I can't access any of the buttons on the top half of the program, but bottom half works fine.
I have only been able to reproduce using boot2 or boot5. I haven't seen this without swap. Restarting launcher does not fix it. I have seen cases where it fixes itself after a while (say 5 minutes).
Anybody seen the same problem? Thanks.
The same thing happens to me occasionally on Cyanogenmod 6.3 RC3. Putting it to sleep and waking up a few times usually solves it for me. A reboot will do it on the rare occasions sleep won't work.
Related
I got my replacement Fuze from AT&T and as soon as I did, I flashed WM6.5 on it. And now I noticed that a few things from landscape view are burned in on my screen, and you can only tell when its closed [portrait view]. The very bottom of the screen, just big enough for the left/right soft touch buttons, flashes constantly. And I can see the X for closing a window and the time burned in from when it was in landscape view.
It did this before and went away and now its back. What do I do to fix it? Get it replaced again?
im not sure what actually causes that but i dont think its real screen burn in. ive had it happen and go away. its something weird with tf3d maybe?
Sometimes I have seen 'Action' and 'Camera' burnt in at the bottom in portrait view, but it's not always visible, and don't see it often
Try turning teh screen brightness way down
fuze2011 said:
I got my replacement Fuze from AT&T and as soon as I did, I flashed WM6.5 on it. And now I noticed that a few things from landscape view are burned in on my screen, and you can only tell when its closed [portrait view]. The very bottom of the screen, just big enough for the left/right soft touch buttons, flashes constantly. And I can see the X for closing a window and the time burned in from when it was in landscape view.
It did this before and went away and now its back. What do I do to fix it? Get it replaced again?
Click to expand...
Click to collapse
I have only had this happen once and it was when I had the screen brightness all the way up. I turned the brightness way down and after about 30 minutes the ghost images went away (gradually).
Hope this helps.
Turn the phone off and take the battery out for a couple minutes. Worked for me.
It seems like a software issue to me, because also when I go to landscape view sometimes, the icons are all distorted. Looks like I'll be going back to WM6.1 for a bit, until I can find a stable 6.5.
I got nexus s (i9020T) recently and found the touch screen unresponsive sometimes. I've already tried several launchers(adw, lancherpro, go launcher ex), and it seems not launcher's problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
Later 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'm confused by the strange behavior, anyone experienced similar issue?
more info from test,
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 don't know kernel very well, so I cannot find the source code Any help please?
FYI. we are not alone.
http://code.google.com/p/android/issues/detail?id=13853
I got this problem too whenever my phone is in my pocket facing inward.
I have tried to open the calculator to see which part of the screen having problem. Mine is usually the "8" and "5" location unresponsive if my phone stayed in my pocket facing inwards for a certain period of time.
The problem will goes off after couple of mins when i can feel that the phone is cooler than my body temp.
I knew this happens to the Dell Streak as well.
I have listed my problem before but got no satisfactory solution so opened this topic...
I am on cm9 alpha 9 before this was on RemICS.
I have noticed that after about two days use the screen becomes less sensitive..No lags..just seems like the screen does not register my touch.scrolling with my right hand by thumb supported by Palm makes it easy..but scrolling unsupported is not possible .eg-keeping on table and scrolling.
Here's the weird part - restarting solves the issue only to recur in about two days.
Also i have noticed installing beats audio causes the issue in under one day
Can anyone help?? Many thanks...
Weird !
I sometimes experienced different issues after two days on almost all cm9 based Rom.
Sometimes the phone becomes unresponsive suddenly. The screen goes black, though the background is lit. Touch buttons keep lit.
Lock button also doesn't solve the issue. Locking-backlight off, unlocking-backlight on.but no screen. Returns after two to three minutes on its own.
I noticed yesterday that the upper left corner of the screen isn't registering touches.
Anything I can do to correct? Maybe my tempered glass screen protector is bugging something out?
Since my bootloader is unlocked, I'm guessing I'm up the creek without a paddle for a warranty fix or replacement?
Thoughts?
Disregard, a restart of the phone remedied... Go figure ?
I'm having the same issue
also having the same issue. restart does fix the problem, but then the issue returns after a few hours. it also does NOT seem to be a hardware issue, as even when I rotate the phone from portrait to landscape, the 'new' topleft corner (previously the top-right corner in portrait mode) will also become unresponsive. seems like a firmware bug or something? anybody have any longterm solution rather than restarting the phone every few hours?
I've noticed that if I rotate to landscape , that previously unresponsive spot on the screen works fine.
I've also noticed that if I tap on the status bar just above it, it works fine.
Very odd! Other than that small quirk, I love the phone!
Same thing
Same issue here.. Corrects after a restart... Other than that it's the best phone I've had.
Issue seems to have been resolved in Marshmallow, or at least so far been running all day without the problem !
So I recently dropped my phone (with a case) and a rock may have hit the screen directly. There is only a tiny, minor scratch on the top of the screen but the internal touch sensor on the bottom half seems to be messed up. Certain places of the screen will identify touches randomly to other places on the screen causing random swipes and taps when typing. I probably wouldn't be able to type this post on my phone without it tapping out of the keyboard or exiting chrome completely. I could barely swipe through developer tools without it randomly tapping the enable toggle countless times.
Now I know I probably can't fix this cause its a hardware issue but is there any way to make my experience any better for me until I can finally get an upgrade?
RIP, looks like it was just the crappy block I was using to charge the phone