When I press on the very bottom of the screen (edge of the glass), it acts as a click to about 1/3 the way up the screen. This is annoying by its self (and doesn't seem ROM related) but also my screen sometimes locks up, with a point at about 1/3 the way up the screen, and horizontally in the middle, and I can't do anything until I lock the screen and leave it off for a second. More recently, but related to this issue, the keyboard when typing hasn't been accurate. I've tried to type 'a' but got caps or 'q' instead, and I get letters I didn't press.
This is not ROM related, as it started happening on CM6 about a week ago, and I've flashed Ava V9, Myn's 2.2, FrEaKy Evo, and CM6, and I have tried stock kernels, and Kings. It seems to lock up more when plugged in also. I've been watching the forums and I haven't seen anyone else post about this, is it just me? It seems very hardware related, but if there is a fix for it that someone knows about, please let me know.
If I get around to it I might take a video of what I'm talking about, but probably only if it's requested.
I'm currently running Myn's Two-Point-Two with King's CFS #11 and am still getting the issues. I've rebooted, and wiped cache/dalvik, flashed new roms, reflashed, nothing.
I am having the exact problem, except that the spot that keeps getting phantom clicks is at the very top of the screen, so the drop down bar starts freaking out. I downloaded the program 'dotty' and it is showing that a touch is being registered in the expect spot, so I'm pretty sure it is just an issue with the screen hardware. I want to take it to a sprint store and see if they can replace just the screen instead of getting a brand new phone because I have so much stuff downloaded on it and I don't want to lose data/settings.
It happens a lot, but then I will have days at a time that it stops happening...its just very strange.
Its good to hear that I'm not the only one with this problem. Currently running rooted stock froyo. unrevoked forever. Original June 7th release device.
same here...was happening witht he W/q as well...but when your viewing a white page you can see a light on the screen brighter than the rest...
mrjeancw said:
same here...was happening witht he W/q as well...but when your viewing a white page you can see a light on the screen brighter than the rest...
Click to expand...
Click to collapse
W/q? what are you talking about there?
also the light bright spot is completely unrelated: evo developing a light spot in middle of screen
Screen burn possibly due to overclock
Bright spot in the lower right of screen
bhughes3 said:
I am having the exact problem, except that the spot that keeps getting phantom clicks is at the very top of the screen, so the drop down bar starts freaking out. I downloaded the program 'dotty' and it is showing that a touch is being registered in the expect spot, so I'm pretty sure it is just an issue with the screen hardware.
Click to expand...
Click to collapse
I downloaded dotty, and it's saying my spot is at:
X: 159.6
Y: 363.5
and P which I'm assuming is the size of the area being touched at .937.
I tested P and it does seem to be how big of an area you're touching but the biggest that I could get using my thumb was only .235, so it's a huge area and constantly in the same spot. Some times it gives me two points or one a bit up and to the left.
hi, had my desire z about a year now, since ive had it, quite rarely ive had a problem of it seeming to have a mind of its own, for example, icons may be selected, or the home screen will slide accross by itself etc. ive always put this down to a trackpad problem.
the other day (after having a miui rom installed for about 2-3 weeks, which was fine untill now), it started acting up strangely, the above problem started happening, but more severe, also the touch screen and softkey buttons would stop working for periods of time (or stop completely untill reset), but screen rotation etc would still be working, which shows that the O/S has not frose and is still working behind the scenes (making me think its a hardware problem).
now, i think ive worked out that this seems to be triggered (mostly) when i open the keyboard. (as also, when the touchscreen stops working etc, sometimes, sliding the keyboard open and close several times, will sometimes seem to unfreeze the touchscreen etc, and will be back to normal, for a while). ive tried doing full wipe and reflashing etc, but i still have the same problems mainly when using the slide out keyboard, which again, makes me think its hardware (possibly keyboard ribbon cable?)
i really dont want to send it off as that means getting it all back to stock etc, and last time i needed the screen replaced, took 6 weeks to get it back!
if anyone could pinpoint the likely source of the problem, id rather replace the part myself..
would anyone have any ideas, as they would be very much appriciated... Thanks...
anyone at all?
I got 2 Zs meanwhile but dont have any problem with the keyboard.
But sometimes when its charging i got the same issues like you - no touch is working and the screens are sliding nearly automatically.
I think this has nothing to do with the keyboard...
Hope this had helped you a bit
Sent from my HTC Vision using XDA Premium App
thanks for the reply, unfortunately im still no closer to finding source of the problem, its intermittant, happened lots yesterday, not so much today, maybe the digitiser? its like there is another invisible finger touching the screen..
This would happen when i was on stock froyo, like it would cause the home screen to hang, but if i was ion an app it worked fine. I would use it to refresh of sorts when my phone was hung up or i need to reload my apps from sd lol. Sounds weird I know, but even with stock froyo i had problems with my keyboard but with the prerooted GB its as smooth as butter...
still going on, and getting more frequent, i dont think it is to do with the keyboard anymore. im now guessing it is the digitizer, its like someone is pressing an invisible finger on the screen, roughly in the center. it comes and goes, it happens for about 3 days, then goes away for a couple of days etc.
also there is very little info anywhere on the net that can help, including replaceing the digitizer itself
anyone ever replaced one on a disire z/g2?
So for the entire year and a half I have had my T-mobile G2 (aka HTC Desire Z) my touch screen has had issues.
It seems to happen mostly when I am doing something memory intensive, but not always.
My screen either goes completely unresponsive to touches or acts like only 1 touch is performing “pinch to zoom”.
To remediate this issue I have to hit my top power button to turn the screen off and then back on, but this is just a temporary fix.
It does seem to last a little bit longer before starting this behavior if I do a complete reboot.
My phone is still usable but this is an ultra-annoying issue that I believe should be able to be fixed. I have used task killers and messed with the performance options in cyanogenmod to no avail.
This has happened on the stock ROM and every other rom I have ever run. I am currently on Andromadus Alpha (http://forum.xda-developers.com/showthread.php?t=1349864).
Thanks for any help in advance.
I have the same problem since its new.
It does it when the screen is dirty too.
Makes a huge difference when I'm using my old moto milestone, the screen is more responsive.
Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to
Your hands are really dirty or really dry. Try moisturizer or something.
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.
@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.
I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.
I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus
gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.
I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk
Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...
I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA
I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.
I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!