[Q] There are a way to test touchscreen? - G2 and Desire Z Q&A, Help & Troubleshooting

Hi,
I started to have some issues with my touchscreen by surprise.
Yesterday my phone was working pretty good, I turned off because I had very low battery and today I charged and turned on again.
After a few hours of use, the touchscreen stop working.. It's work randomly, sometimes works pretty well without problem, but then stop work.
I made a hard reset, and re-install the ROM (I have the virtuous sense). After that the phone was working fine, but now again the same problem.
When I lock the phone then takes long to know that I pressing the screen, but a few seconds the screen start to work normally
How can I test the touch screen, to know if it's a hardware or software problem?? Anyone have any idea..
I dropped the phone a few times, but I don't remember any issue the lastest four days. I don't have warranty, because I bought the phone in Canada and now I am in Chile...any suggest?
Thanks
PS: I was using the same ROM since 4 month ago.

Chances are its the main flex cable causing your problems, the only way I know how to test the digitizer or flex cable is to swap it for one I know that works, if someone knows of an easier test id be glad to know as well, but I doubt it.
If wiping full and flashing a known working rom won't fix your problems than almost certainly its hardware failing
Sent from my HTC Vision using xda premium

Related

Anyone's touchscreen ever failed??

My desire z is going back for warranty tomorrow ...
The touchscreen and the buttons just under it stopped working without any warning.
Anyone else had similar issues??
Now unrooted with the latest ruu.
Back to my magic
Sent from my HTC Magic using XDA App
When you say it stopped working, did you by any chance have the phone on a worktop? or was you holding it in your hand?
There are reported issues with phones not working all the time when on a worktop, however mine always works when its in my hand.
When my phone is laying flat on any surface the screen just refuses to respond... however if I angle it just slightly it works just fine, or if I pick it up.
I have the same issue when its in the car dock. I didn't have the issue when I was running the stock bell rom this only happened when I installed cyanogen 6.1
My g2's touchscreen gets super lllaagggyyy, like laggy as crap whenever it is connected to the charger @ near full charge. It's random...yet it's not, like for instance..I can put it on the charger and initially it's very responsive. Then, after a few minutes charging the screen *seems* to be unresponsive, I just have to swipe it slowly and it jerks by @ like..5fps seemingly. This has happened on every rom ive tried so far from stock to CM.
Just installed MIUI and haven't had a chance to test..i'm assuming it's hardware related though.
When I First got my G2, The TMo Rep asked me to open it up at the store since i was getting the first one from that store and the touch screen didnt work at all, we turned it off and on and nada. So they replaced it with another one and it worked just fine. Other than that little problem i never had a issue on my G2 as far as touch screen freezing goes
Seems like shoddy hardware to me... I've never dropped the phone.. its always been in a protective cover.
Although I couldn't help thinking.. maybe all the extreme overclocking / general heating up of the phone may have contributed??
Sent from my HTC Magic using XDA App
I have never OC my desire Z (not G2) but I have noticed the exact same symptoms of an unresponsive touch screen after flashing cyanogen 6.1.
I returned back to my stock rom and everything is back to normal.
I haven't had a problem since..
yes, when its on a worktop (table, desk, anything not my hand) and in a dock -- its not as responsive as you'd expect. I have to hold it and caress it with my warm loving hands to get it to respond.
now ---
this is not related to CM 6.1. at all. Ive flashed a lot of things since visionary and its happened on every single rom.
Id go get that phone out of the mail if I were you OP.
I have also noticed the problem with touch screen responsiveness when my G2 is mounted in a car holder.
I have figured that you just have to keep one finger on the aluminium body and the problem is gone. I have to admit that this is somewhat bizarre and I have never had this problem before with my G1 using the same car holder. Seems that there is an issue with electric isolation? I don't exactly understand how capacitive touchscreen works so can't really explain where the dog lies buried.
Maybe this is a feature. Protection and saves battery.
vision...
squbel said:
I have also noticed the problem with touch screen responsiveness when my G2 is mounted in a car holder.
I have figured that you just have to keep one finger on the aluminium body and the problem is gone. I have to admit that this is somewhat bizarre and I have never had this problem before with my G1 using the same car holder. Seems that there is an issue with electric isolation? I don't exactly understand how capacitive touchscreen works so can't really explain where the dog lies buried.
Click to expand...
Click to collapse
The same for my DZ - it is kinda weird, because if the phone is for example in the car holder it is impossible to use the touchscreen unless I put another finger on the phones housing. I tried different roms already, but the 'error' is still there.
It would be interesting if all users have the same problem or if it is just a few examples of phones out there.
Thanks,
Robert
Wow,.... only just noticed this a few days ago. Along with it not vibrating on incoming SMS, i'm starting to get slightly ticked off.
yeah happens to mine too =P
happens to mine also, nothing we can do about this?

CDMA galaxy nexus - unresponsive to touch

Hello everyone,
Basically went to unlock my phone today and touch screen is not responding, however the hardware buttons work fine. Now i've done some research and found other posts of people with the same problem, however their touchscreen problems seem to be fixed(temporarily, at least) with a battery pull.. mine however is still unresponsive after half a day and multiple battery pulls.
Id rather not have to send in for certified to replace an otherwise perfectly working phone.
Any ideas/suggestions would be greatly appreciated!
bigdeezer20 said:
Hello everyone,
Basically went to unlock my phone today and touch screen is not responding, however the hardware buttons work fine. Now i've done some research and found other posts of people with the same problem, however their touchscreen problems seem to be fixed(temporarily, at least) with a battery pull.. mine however is still unresponsive after half a day and multiple battery pulls.
Id rather not have to send in for certified to replace an otherwise perfectly working phone.
Any ideas/suggestions would be greatly appreciated!
Click to expand...
Click to collapse
are u undervolting?
Nope, sorry forgot to say. Completely stock never unlocked or rooted.
Also i tried getting into recovery to try and do a factory reset but when i select recovery i just get the android on his back with the red triangle..
so instead i just went through the steps and unlocked the bootloader and booted up (in order to give me the factory reset without having to touch the screen)
It unlocked and booted up fine but still no response..
No new recent app installed and never had this happen before.
Mine did this after a few days of owning it, and luckily the store took it back and swapped it out with a perfectly working unit. Is yours within a few weeks of purchase?
Figured this out randomly. Remove battery cover. With phone turned on, press on the area to the to the left of the camera lens until the screen is responsive. My screen becomes unresponsive when the phone is dropped and this fixes it.
dailong said:
Figured this out randomly. Remove battery cover. With phone turned on, press on the area to the to the left of the camera lens until the screen is responsive. My screen becomes unresponsive when the phone is dropped and this fixes it.
Click to expand...
Click to collapse
hrmm this does not seem to fix either. I also have never dropped my phone, although this seems to be worrisome if the issue is hardware related.
@ tmellen i purchased the phone from amazon and am a few days past my return date :-/
Guess ill just give them a call and hope for the best. Thanks for the ideas everyone.
(update) called amazon and they are sending me a brand new phone.
Knowing this i thought i'd try dailong's method again only this time i was quite a bit more "rough" with pressing down on that area, and it actually worked!
Ill still be taking the new phone once it gets here but for anyone who is having this problem there's a sweet spot on the left edge of the phone towards the top (looking at it with the back cover off) there should be a circle shape. press on that area really hard and it should fix.. weird
Experienced the same on my GSM version a few minutes ago. I had to call my mobile to get it to respond. After that it worked again as normal. I'll see if I get this issue again in the next few days. Hope it's just random
Had the same happen earlier to mine and I was on AOKP. I've had this happen to other phone before, shouldn't be a a cause for alarm unless it happens very frequently. Btw, next time it happens to me I'll give that left side of the camera trick a try.
mine got fixed by removing battery.

one v screeen issue

I am facing an issue with the touch screeen on my one v.... scrolling on the touch screen causes inadvertent clicking of app shortcuts ... this happens only occasionally and most of the time the screen works fine.... sometimes the phone goes haywire and likes to start every app available on the screen at the time.... any guesses to what this could be... this problem started about a month after buying the phone
anyone?
loche said:
I am facing an issue with the touch screeen on my one v.... scrolling on the touch screen causes inadvertent clicking of app shortcuts ... this happens only occasionally and most of the time the screen works fine.... sometimes the phone goes haywire and likes to start every app available on the screen at the time.... any guesses to what this could be... this problem started about a month after buying the phone
Click to expand...
Click to collapse
If you use a 3rd party cable and/or charger it can cause this error, when plugged in. Other that it is digitizer malfunction probably.
Sent from my ONE V with CM10
thanks for the reply ,
I dont use any 3rd party accessories..
would a digitizer malfuction cause this problem to appear only occasionally?
Try just touching your stove when phone is acting up with your free hand or the water faucet even.
I'm wondering if you're building up a load of static electricity and causing it yourself inadvertently.
Long shot, but worth knowing an ruling out.
WR
Sent from a CleanRom-V OneX
Can static electricity really cause this? I tried what you suggested but it did not help when the phone was acting up.
Twas a long shot that it might be building a surface charge on the phone, sorry it didn't help.
WR
Sent from a CleanRom-V OneX
loche said:
Can static electricity really cause this? I tried what you suggested but it did not help when the phone was acting up.
Click to expand...
Click to collapse
It can, but really unlikeley. Stacic charge discharges quite quicly, so it will be a second for the phone to recover from it.
The most possible problem I think will be at the digitizer chip. It is earthed, an protected by a farraday-cage (i think at least), but if the galvan connection is out (means it is not soldered in place good), the phones electro-magnetic field can cause malfunction. I'm not in posession of a detailed blueprint so I don't know how it is earthed. If the phone is stock as it can be (so not unlocked) try the service.
I happened to have this error in my former Samsung Galaxy Spica, but it was a software error first, then the digitizer itself gave in, but changed it, it works even now.

Strip of touchscren not working

Hi guys. I know many of you have had touchscreen problems and whatnot, i searched but it seems like this one is a bit different from usual. Yesterday the phone was totally fine; i woke up this morning and it had a lot of touchscreen problems: at first it registered touches without me doing anything, but after a couple of reboots it was just unresponsive. After another reboot and some messagging, the problem reduced to a strip on the screen simply not working. The strip is located exactly where the first notification on the status bar is (like when you receive a message and you click on that notification). I have the trueancestor stats bar buttons, so that zone is a tad more down than usual. Anyway, all I did yesterday was a quick game. I think it may be the flex cable not working because of the sliding, but it happened all of a sudden, not gradually. I must say that some weeks ago I had the same "registers touches by itself" issue when typing, but a simple reboot was enough. I tried doing factory reset, but nothing so far. Also I can't use pc companion to flash everything stock back (I unlocked bootloader months ago, even though I relocked it; I dunno if it's locked or not right now), and I can't seem to find a working flashtool download link -_-. I don't think that would help much, it probably is a hardware problem, but who knows. I'm on true ancestor 1.6 LE, stock kernel.
Any help would be great, as I fear the phone will get refused in assistance because of bootloader unlocking.
Did your phone had contact with water? When my screen had contact with water it registered touches randomly.
it didn't. it has a screen protector anyway; but that's not the problem for sure. it doesn't register randomly, simply a strip doesn't work now...
Hardware problem. Could be flex cable or digitizer.
Today there were two moments it began to work again, but a few minutes after each one the problem came back. Sigh...
Mine does that when the screen is moist or my hands are too oily. Are you sure you're working in a dry environment?
mhh... exactly that? I dunno, my hands are dry and i think the screen is too; it has a quite thick screen protector (the skinomi one), so even if it got moist that shouldn't be a problem, right? I'm now living in a different town and that may have changed something, but the problem didn't show up until now, and it was sudden.
Also, I noticed that using gamekeyboard on a certain profile I had buttons placed on the strip, and pressing hardware keys mapped to those buttons actually works. This restricts the problem just to the actual finger-touch-detecting mechanism. Does anyone know anything about this?
Edit: lol I heated the phone up a bit with a hair dryer. It works now. I hope it will last and I'll not have to do this again over and over

[Q] Graphics Issues + Crash while charging

Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!
a_p3rson said:
Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!
Click to expand...
Click to collapse
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)
lorddavid said:
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)
Click to expand...
Click to collapse
Superoneclick? That's the closest I found, and it doesn't say that it supports the Glide. And, I am running a fully stock version of 4.0.4, unrooted and everything. I might need a little more help here, haha.
I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms
lorddavid said:
I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms
Click to expand...
Click to collapse
Isn't that a different version though? The build number on that is UCLG9, not UCKJ3 (which is what I have right now).
I am not sure, but, if with that your problem persist, maybe is hardware, but I only do that. When I did it, that was the latest version, now there is another version but not sure what is it
I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be
davidpartay said:
I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be
Click to expand...
Click to collapse
I really was hoping it was a OS issue, as it hadn't ever done this on GB. If I flash a new rom then, it would be fixed?
Also, I too noticed that my phone is abnormally warm when it does this. I do have a cover on my phone, but I noticed that it seems to be centered about on the horizontal center of the phone, about a half-inch below the camera. If this is related, what do you think it is?
My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.
Exxon02 said:
My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.
Click to expand...
Click to collapse
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?
a_p3rson said:
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?
Click to expand...
Click to collapse
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)
Exxon02 said:
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)
Click to expand...
Click to collapse
Your issue sounds similar, but slightly different. Mine only happens while I am charging it, and it has only done it since a while after I made the upgrade to 4.0.4. Although, they sound similar, and my phone also gets concerningly warm, so I have no idea if it is the same thing or not...
If it's out of warranty, then you have nothing to lose by doing a backup and a clean ROM installation, which is what I would do. I guess if you do it when fully charged and while the phone is cold you should be fairly safe, especially if you use a small ROM. I've found the latest M3 10.1 ROM installs fairly quickly, so that might be worth a shot even just to see if it fixes the problem.
The only risk you're taking is that the phone might die and get bricked in the process if it's a hardware fault, so I guess it's really your call.
EDIT: On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things
davidpartay said:
On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things
Click to expand...
Click to collapse
I like that idea, as it should fix the overheating issue. However, the times that it actually has this malady aren't regular - it seems to happen more at night, but not every night. I could try putting it in the freezer when it does it though, and see if it works. If it is overheating, could it be a hardware issue then? I also noticed that my battery that I have in my phone does appear to have a slight dent near the bottom, and it is only happening when it is charging, so I am wondering if it could be a problem with the battery? When I pull the battery out after it has done this, the battery itself isn't that warm, but the phone is, so I'm thinking it isn't the battery, but does anyone else have any ideas?

Categories

Resources