I've started to have touch screen issues the past few days.
Any idea what may cause it?
Sometimes, when I touch the screen, say in settings, I touch one item, but a different item is selected somewhere randomly on the screen.
Happens in TWRP as well. If I select options to wipe, it will select others, and then it doesn't swipe over to execute the action.
No ideas? What would make touches appear where I don't touch, even on TWRP?
I tried the keyboard calibration on HTC's keyboard.
Any ideas? Screen protector?
It comes and goes.
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
mcwups1 said:
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
Click to expand...
Click to collapse
I opened another thread about a similar issue I'm having after Lollipop. My gesture launch randomly stops working and I have to reboot. No other issues for me though. I have an anti-glare screen protector on mine, but had no issues before the update. I've thought about a factory reset to see if that would cure what ails.
I'm on tmo but have the same exact issues. This is what i've found so far...
I turned on the developer options and turned on show pointer. This will show you where the touches are landing.
If you scroll down slowly, you can see most of the touches are in line (up and down) and not random on the screen.
I've removed all programs that have screen overlays (screen filter, twilight etc)
I've removed the cases thinking they might be causing the issue, but removing them only slightly improved the issue I thought...
Sometimes its hard to reproduce the effect, its not consistent. So this leads me to believe that it could be a process that's running in the background that calls attention at the moment you're touching the screen, and then refocuses the screen to your point of contact. And in between it thinks you're moving your finger when you really aren't.
In any event, I can't find the exact cause of this. But, it definitely started after the update to lollipop. I had none of these issues before. I even got the phone exchanged because I believed the digitizer went bad or something. But this issue exists on my original phone, its replacement, and now on my wife's current phone and that phones replacement (across 4 phones).
I'm currently working on my wife's replacement (4 or 5 non-oem programs installed) and continue to have the problem. But it is not consistent as I can't readily reproduce it.
What i've done to try and learn more is when I see the screen pointer light up in random places, I keep pressure on the screen so I can observe where the screen is registering contact. It almost looks as if it's trying to pull down the shade. Whether it be because of the dual points of contact and it thinks we're swiping down, or because of another program that is stealing focus for whatever reason.
If anyone else has insights into this, please let us know as this is more than frustrating! I keep calling people in hanouts with a lot of people and they aren't happy about it lol.
Also for reference, we're using ADW ex launcher instead of Stock HTC Sense. But even when I remove ADW (uninstall) and run sense, it continues to happen. So it's not that.
Related
I know that this has been a fairly common complaint about the Nexus One but i'm wondering, roughly what percentage of people actually have this issue? To clarify, i mean the problem whereby touching the screen in one place is actually registering elsewhere on the screen.
I've had this problem since buying my n1 and having to constantly turn the screen off and back on again was driving me nuts. Finally i sent the unit back to Vodafone for repair and they in turn sent it to HTC to be fixed. So yesterday i got it back with an enclosed statement along the lines of "we have fixed your fault etc..".
Three minutes into using the damn thing and the fault crops up again. So much for that! To be fair to Vodafone they are sending out a replacement unit now but of course i'm concerned that even that will have the same issue.
What are the odds?
Here is the same.
To developers: the fact that resetting the screen fix the problem makes me to ask if there isn't a way to make the screen re-calibrate itself every X seconds/minutes, without shut off and on the screen every time. Seems to be until now the only solution to this extremely annoying issue.
It really is a bizarre one. I've seen people discussing whether it's a hardware or software issue but nobody seems to have a definitive answer. If it were a hardware problem, surely it would be constant/permanent? If it's a software issue i would have thought that somebody would have bug-fixed it by now? Especially as it seems so prevailant.
I'm stumped!
Other than this one problem though i am completely in love with this phone. The device itself feels solid, durable and pleasant to use. Android is improving all the time and it always impresses when you demonstrate to the un-initiated what the device is capable of. So close to perfect...but not quite!
EDIT... This from the wiki.. "- Q5: Sometimes my screen registers touches in incorrect places, and I need to turn the phone off and on to make it work correctly again
A: This is a hardware problem, nothing can be done about it. Nexus One's digitizer sucks.
Ho-Hum.
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
msavic6 said:
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That suggests a software problem although i have had it on 2.1, 2.2 and now 2.2.1. I would say that it has happened to me within three minutes of using the phone, 50% of the time within that three minute window. In other words it's cropped up in half the texts/emails i have sent where i have had to do the screen off/on thing to complete the message.
Very annoying.
It has to do mostly with the way people hold their phones, the possibility of registering false touches - including, for example, touching the screen with fingers that aren't completely dry. Some have the issue more than others.
HW issues still can have SW workarounds sometimes. I'm not sure if it's the case. HW and SW need to be analyzed to find one, if exists.
There is no "calibrating" capacitive touchscreen. Resetting its controller might have effects like missing touches and other random screen misbehavior (for example - if the controller is tracking fingers, resetting it would cause it to lose the tracking).
Since getting my phone back from 'repair' the issue is less frequent, suggesting that it's not a usage problem as i'm obviously still using the phone in the same manner as before. Instead it seems that various devices suffer from the problem in varying degrees.
I suppose if i knew what they had actually done to the phone while it was being tended to it might help us discover why the frequency of the problem has been reduced. I know that the digitizer wasn't replaced as the phone came back with the same screen protector on it as it had when i sent it off. That being said, they obviously did something. I just don't know what!
Most probably replaced the phone's MB.
Try upgrading to the latest radio - the issue will probably not be 100% solved, but now I only get it maybe once a month or so...
I may tell them not to bother sending out a replacement. It's happening far less often since it was returned and (going by the poll results), there's a good chance that the replacement could actually be worse than this one is now.
Perhaps the 2.3 update will jar something loose.
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
pyngwie said:
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
xyellx said:
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
Click to expand...
Click to collapse
I have already restored cyano 6.1.1.
However, about "multitouch issues" I mean inaccuracy, the fact that the touch is recognised in another point of the screen (particularly when you press the bottom part of the panel). I didn't verified the axes-inversion issue, but I'm almost sure that it persists.
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Jack_R1 said:
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Click to expand...
Click to collapse
I don't think so....I pay attentions when the screen goes crazy. I'm absolutely sure that (in charge for example) my touch is ONE.
The only times I was able to trigger the "screen nuts" effect, were when I was typing 2-fingered, and fast - making it register dual touches. Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Jack_R1 said:
Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Click to expand...
Click to collapse
I mean this....since I moved to MIUI this is not happened anymore.
Since I uninstalled Htcime the inaccuracy issues seem less so far! Almost only with the phone under charge ...much much better than before! Dunno why....
Sent from my Nexus One using XDA App
I've noticed the last few days that my nc has a hard time unlocking. I start to swipe my finger across the unlock and it moves about 1/10 of the screen then shoots back. If I do it a few times, I might get lucky and unlock it.
Does this sound like the digitizer is going out? It's one of the first production models (wife bought it for me for christmas right after they came into the store). So I don't know if there was an issue with them at all or not.
Everywhere else on the screen seems to be fine, but it doesn't do me much good if I can't open the thing to read the books inside.
*edit
Just did a test on the bottom row of books, and they seem to be working fine in that general area. Is anyone else seeing this only when trying to unlock the nc from sleep/off?
Do you have it plugged in?
Yeah it seems to happen on my girlfriends NC, at least when it was running 1.1 Stock, not sure I've noticed it since 1.2. It's not a bad digitizer assuming you have the same issue which was right after resuming from sleep it will SOMETIMES be a little pokey for the first 20 seconds or so but after that it slides smooth as butter. It never really bothered me since I just assumed it was reloading some software into memory. The only other common issues I know of are issues when plugged in as mentioned above and the seemingly obvious but often overlooked dirty screen.
I do notice in general that both NC's I use are a little less than perfect when touching the far corners (I often need to jab while making grunting sounds) but I figure it's an e-reader so they probably didn't spend a fortune on the capacitive part of the screen. If you are so inclined, loading up CM7 disables the lock screen by default and there might be a way to do it in stock as well although I suspect you will still occasionally need to give it it's 20 seconds to get things running again.
I've experienced some serious touch issues in the past two days. It's happened very randomly and I can't replicate the issues. The screen losses touch sensitivity and I can't do anything, then it randomly comes back after 10 seconds only to animate every touch I made during the 10 second lull.
Has anyone had any touch issues like me?
Edit: disregard this post. got the forums mixed up with another device.
bryancotton84 said:
I've experienced some serious touch issues in the past two days. It's happened very randomly and I can't replicate the issues. The screen losses touch sensitivity and I can't do anything, then it randomly comes back after 10 seconds only to animate every touch I made during the 10 second lull.
Has anyone had any touch issues like me?
Click to expand...
Click to collapse
sounds like a software glitch, is anything eating up the processor?
I'm on LRX210 out of the box. I haven't had any battery stat app running but nothing unusual is going on in the regular battery app
I have this issue as well. Drives me nuts when I'm playing clash of clans. Found a sprint forum post that says it could relate to screen protectors? I have an invisible shield on right now.
Mauk80 said:
I have this issue as well. Drives me nuts when I'm playing clash of clans. Found a sprint forum post that says it could relate to screen protectors? I have an invisible shield on right now.
Click to expand...
Click to collapse
I have a screen protector but I've never had issues with it before. The touchscreen is COMPLETELY unresponsive 100% of the time
cowkong said:
I have a screen protector but I've never had issues with it before. The touchscreen is COMPLETELY unresponsive 100% of the time
Click to expand...
Click to collapse
Have you updated to 5.1? Since 5.1, there were significant changes that appear to have been made to proximity sensor that seem to be affected by any sort of screen protector that may cover it. If your protector covers the sensor, then I suggest removing it.
I haven't. I currently have the notification on my lockscreen (since I can still use the power button and view that basic info). It simply just stopped working while I was using it. Going into the Sprint store early this afternoon
My N6 arrived yesterday and was immediately unusable. The keyboard filled in a ton of garbage when I was asked to first enter my name ... Power cycled to try again and have had nothing but reliability issues with typing at times the screen will lock while trying to type (no response) or assume I've clicked when I haven't which makes accurate data entry impossible.
wiped, reset and upgraded software from 5.0 to 5.01 to 5.1 - had to remove my ATT sim which initially blocked this process and reset. Issues are still present seems like the screen is defective.
Support has issued an RMA to return the device after suggesting they would replace. Not a great start.
im having the same issue with my nexus, i went back to stock, not even rooted anymore, still doing it, its driving me nuts..
RMA. It's quite obvious you have a hardware problem.
graydiggy said:
RMA. It's quite obvious you have a hardware problem.
Click to expand...
Click to collapse
I'm actually not so sure that it is. I've seen this issue intermittently across 3 different devices, but only on 5.1.1 firmwares.
semperfi123 said:
I'm actually not so sure that it is. I've seen this issue intermittently across 3 different devices, but only on 5.1.1 firmwares.
Click to expand...
Click to collapse
Although we're in an pls thread, I tend to agree. If it was a hardware issue, I don't think we'd see the OS acting out the touches later.. It means the hardware actually accepted the input but the OS didn't do any thing., Likely an OS hang or something.
bryancotton84 said:
I've experienced some serious touch issues in the past two days. It's happened very randomly and I can't replicate the issues. The screen losses touch sensitivity and I can't do anything, then it randomly comes back after 10 seconds only to animate every touch I made during the 10 second lull.
Has anyone had any touch issues like me?
Click to expand...
Click to collapse
I have a Samsung Tab 3 and recently the touch screen has gone haywire. I drop a troop at 12oc and heal spell drops randomly at 6oc or wherever. I click on the screen and the screen zooms in and out irradictly . Trying to do a raid must less a war attack is impossible. Anyone have the same issues?
[email protected] said:
I have a Samsung Tab 3 and recently the touch screen has gone haywire. I drop a troop at 12oc and heal spell drops randomly at 6oc or wherever. I click on the screen and the screen zooms in and out irradictly . Trying to do a raid must less a war attack is impossible. Anyone have the same issues?
Click to expand...
Click to collapse
This is a N6 thread [emoji4]
So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Just to weigh in I also have this issue not very often but enough to notice it. Especially since the last update also when I zoom with the stock camera it just freezes.
I'm having similar issues, camera fixes if i reboot but thats annoying if your trying to get a moving shot, also noticed it sometimes freezes switching to portrait mode.
For the screen freeze I have found if i use my finger print to unlock when the screen isnt responding its starts to work. but i didnt have the problem until i put on a crappy glass screen protector.
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
godsfilth said:
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
Click to expand...
Click to collapse
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
jonchance_84 said:
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
Click to expand...
Click to collapse
hmm maybe, i only had show new notifications turned on but ill try turning it off and see how it goes over the next couple days
Ok so since turning off my ambient display, no issues so far.
karlkarloff said:
So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Click to expand...
Click to collapse
I use Ambient Display and sometimes the screen behaves as you've described where it won't reach to touch, but I've always just given it time/pressed the power button repeatedly until the screen came on (or continued to tap the screen lightly)... never tried pressing down very hard.
Not to Necro a thread but I've experienced this aswell, infact it's happening right now as I type this.
Just retired my 2 XL and got a like-new 4 XL. Loving it so far, except one nagging issue.
Randomly the top 30-50% of the display stops registering taps (touch). It's easy to fix by turning the display off then back on, but I'm concerned it may be a hardware issue.
Interestingly, when this happens and something that is full screen and scrollable such as a contact list or app drawer is in the foreground, I can drag from below the "no touch area" to the top of the screen, but I can't start a drag at the top. So, it can sense touch in the troubled half, it just won't register taps.
I have done tons of searches. I see lots of people saying Android 12 had touch issues out of the gate, but was supposedly fixed. I disabled the block_untrusted_touches. I have checked any app that has draw over other apps permissions. I have tried with high touch sensitivity on and off. I have paid attention to running apps when it happens. I installed a LogCat reader looking for touch related issues when the problem occurs. I tried safe mode, but due to the intermittent nature of the problem, and the fact that safe mode disables most functionality, it really wasn't a good long term test.
I have yet to pinpoint this.
Sometimes it doesn't happen for a day, other times it's multiple times per day. So trial and error takes time because just when you think you licked the problem, it rears it's ugly head again.
I'm running LineageOS 19.1 at the moment (which I had also run on my 2XL with no issues). It is rooted. No apps force closing or crashing.
Has anyone else seen this on the 4XL?
Definitely interesting, never heard of that. I had some touch issues, specially if the display gets wet where it register touch, but poorly to the point I need to restart the device and dry out the screen. Though in my case the creen is completely cracked, so I suspect that's the cause as it didn't happened before.
Though I had a similar to yours but with the battery.
The problem was that the phone would randomly shut down, and that would happen more often when it was on my pocket.
This made the phone very un stable as sometimes I would have the phone completely off and didn't even know about it.
So I decided to open it and have a look at it. It turn out that the problem was the flex cable that connected the battery with the logic board, it was just slightly tore on one side, but just a tiny I couldn't nearly see it, I had to use another phone to zoom in.
As it was torn, depending on the way the phone was changed the force the gravity made over the cable, causing that sometimes it not enough energy got the phone, causing it to shut down.
Once I replaced it, it never happened again, not a single time.
Maybe you have a similar problem, though as you are rooted and using a custom ROM, that may be the reason, my case was extremely rare.
anyway, good luck