Screen Touch Response Issue - HTC Aria General

Hey, I'm new to the forum here, and would like your feedback on this aria issue I'm having. Here it is: when my aria is plugged into the wall to charge, the touch response of the phone is drastically changed. If I tap my finger on the screen, or any of the four buttons, it double clicks - in other words I can't do a long click (click and hold) nor can I operate the phone very easily, it also won't really follow my finger if I drag it across the screen. My phone isn't rooted, rommed, or anything, just plain stock. I haven't dropped it, scratched it, I honestly don't know what I could have done to trigger this.
I've attempted the following to fix it (obviously each yielded an unsuccesful result):
1. Restarting (both plugged in and unplugged)
2. Shutting down, removing the battery and sim, and starting up
Does anyone else have this issue? Anyone have any remedies for me? Thanks for your help.

I've only had mine for about 3 hours, but I haven't noticed any issues with the screen when the phone is plugged in (and it was plugged in the whole time).
Maybe you got a lemon?

You may want to take it back for an exchange if that keeps up. Mine has been flawless since I got it on launch day.

Might just have to. I tried doing a factory reset - that didn't work either.

It sounds to me like some sort of grounding issue that is screwing with the capacitive touch screen.

Good call tshooter. I tried a different plug and voila, no issue. The charger is only 2 pronged (no ground) so I don't know why this would have been an issue, but I'm no electrical engineer.
I'm happy as long as it keeps working.

Related

Touch Response Problem

I have a Sprint Touch [Vogue]. It has served me very well up until recently.
One day, I was using my phone normally when the battery died. No big deal right?
Well, I charge my phone and reboot it. For some reason, Windows is EXTREMELY slow and unresponsive. I figure that something vital had been corrupted by the battery's death, and that it was nothing that a hard reset couldn't fix.
I performed a hard reset.
I let the utilities for the first boot run to customize the phone. Everything seemed pretty much normal. I configured my settings, re-added my contacts, etc. Then I turned the screen off [with the power button].
I turn it back on later to do something. I touch the screen. It immediately and accurately detects the touch's location, but it continues detecting a touch. For 20-30 seconds, after the input has stopped.
It was strange, so I soft reset the device. It booted, with the same problem. So I performed another hard reset. I did some configuration [the response acting normal at this point], and then turned the screen off. Turning it back on brought the same problem back.
This problem still exists on my phone, even after numerous hard resets and even ROM flashes.
A better description of the problem: When the device is first turned back on [meaning brought out of standby], its touch response is messed up. It will immediately and accurately detect any touch input, but it will continue to detect the input for up to 30 seconds AFTER it has been released, as if you were holding it the whole time.
WHY is this???? My phone is almost unusable because of this!!!! I can still place/ receive calls, using the navigation buttons and the red and green buttons. But the touch response is screwed!
Can someone please shed some light on this problem I'm having?
Phone specs: Windows Mobile 6.1, HTC / Sprint customized. Minimal third party software is currently installed.
[I've already determined that third party software is not the problem, because i haven't installed any!]
Possible solution
Hi,
today I experienced something similar to your description - no touch response when I tried to pickup a call. The strange thing is that last night everything was working and no settings were modified nor programs were added/removed. The screen suddenly 'died'. At the moment I am using it through a program MyMobiler which brings the mobile display to the PC and I can use the mouse to control the phone (it is like VNC for the phone screen, the phone is connected with ActiveSync).
This is temporary solution untill I finish my backups of files, programs, settings. I didnot performed hard reset yet, hope this will solve my problem
In the following link there is a 'magical' solution - to remove the screen protector:
http://www.htcwiki.com/thread/1112981/LCD+or+Touch+screen+not+working
P.S. I had removed the screen protector and voilá - the screen is now touch responsive. The root cause of the problem obviously is the dust between the screen and the protector which results in constant screen pressing - and as a result no accepting my finger presses.
I hope this will work for you and others with similar problem.
I had a similar experience with an old Vogue.....In my case, there was no battery death precursor, but it just started acting up. Not too long thereafter, I noticed the screen/digitizer was forming what looked like an air bubble between the digitizer and the LCD on one place of the screen. The screen was becoming defective. I eventually had to buy another Vogue from a friend who didn't have a clue of the 6900's potential, and didn't want his anymore, so I got it cheap.
Sounds like your screen/digitizer may be on it's last leg.

Omnia 7 camera button issues

Hi all,
I've had an Omnia7 since launch and other than having issues with my headphone jack tripping the media controls on occasion, i've not had a problem.
Recently, however, when the camera button has become randomly unresponsive. That in itself is not too big a problem but last night it escalated from just being unresponsive to acting like the button was being pressed repeatedly when it wasn't being touched. In the middle of the night it woke itself up, went to the camera app from the lockscreen (as if the button had a long press) and started repeatedly taking very close up pictures of the surface it was sat on. Pressing the button all the way down stopped this happening, but the moment I let go it would start again. I eventually managed to stop it by repeatedly hitting the button with quite some force, though that isn't something I'd want to be doing regularly if it happens again.
It seems to be a hardware issue, but I thought I'd check if it was a known, fixable problem or is it a unique hardware failure?
I've had a similar issue with mine (sometimes would act like yours, other times to take a picture I had to put some strength on it). Solved it with electric contacts cleaning spray.
Ahh, fair enough, thanks for the info. Dirty contacts makes sense. I might get some spray and trying cleaning them.
I need to get the phone working again first though, as it decided to brick itself today. The battery ran out, I plugged it into my computer to charge and it booted to the screen with the nice diagram telling me to connect to a PC and Zune loaded on Windows saying it couldn't perform a restore. It just boots to that screen constantly now, which is a bit bizarre as I literally had done nothing with it for a couple of days. At least it had good timing dying 6 days after I bought a Lumia 920 rather than before.
Thanks for the information.
My Camera Button is not working anymore, it feels normal but does not do anything. I sprayed some CRC there but it did not do anything. I need to get to MAGLDR so I need the camera button.
Maybe internal contacts broken, try open the Phone is very simple just to reach the side buttons.

[Q] LCD not working, screen and digitizer fine, what could be the problem?

Hello all!
I would like your opinions/knowledge on how likely you think it is that my problem is a simple disconnected cable, and if it would be worth it to take apart my phone (I've never done it before.. but I'm careful) to see if I can just reconnect it.
I woke up one morning and my screen would not turn on =( I did not drop it or get water on it, although it had been very humid. The screen is not cracked and it is still responsive to touch (vibrates when touched on the soft keys on the bottom) but it is completely black, no flickers, no faint images, no nothing. I also have not seen the LED light up since this has happened, when charging or plugged into my computer or anything. My computer DOES recognize the phone, and I have used the Motorola utility to update my phone since this has happened, but that did not fix it. I have tried all of the key combinations and I have successfully rebooted it (I can hear the droid start up noise, the camera sound when I hold power and down volume at the same time, and it sounded like I almost accidentally made a call when messing with it last night).
I have not yet been able to factory restore it or anything like that from recovery, as I am flying blind, but I'm thinking this is a hardware problem with the LCD?
The phone is not rooted and boot loader is not unlocked. It's only a few months old but I bought it used online so there's no returning it or anything like that.
I just don't know enough about any of this to know how to proceed next. Any help would be appreciated! Thank you for your time!
SunLilac said:
Hello all!
I would like your opinions/knowledge on how likely you think it is that my problem is a simple disconnected cable, and if it would be worth it to take apart my phone (I've never done it before.. but I'm careful) to see if I can just reconnect it.
I woke up one morning and my screen would not turn on =( I did not drop it or get water on it, although it had been very humid. The screen is not cracked and it is still responsive to touch (vibrates when touched on the soft keys on the bottom) but it is completely black, no flickers, no faint images, no nothing. I also have not seen the LED light up since this has happened, when charging or plugged into my computer or anything. My computer DOES recognize the phone, and I have used the Motorola utility to update my phone since this has happened, but that did not fix it. I have tried all of the key combinations and I have successfully rebooted it (I can hear the droid start up noise, the camera sound when I hold power and down volume at the same time, and it sounded like I almost accidentally made a call when messing with it last night).
I have not yet been able to factory restore it or anything like that from recovery, as I am flying blind, but I'm thinking this is a hardware problem with the LCD?
The phone is not rooted and boot loader is not unlocked. It's only a few months old but I bought it used online so there's no returning it or anything like that.
I just don't know enough about any of this to know how to proceed next. Any help would be appreciated! Thank you for your time!
Click to expand...
Click to collapse
it would still be under warranty by motorola - especially if you accepted the OTA recently (May 2013).
otherwise, I would try leaving it plugged in for awhile (30-60 minutes), then try rebooting it (hold down all 3 buttons)
Thank you for replying!
jco23 said:
otherwise, I would try leaving it plugged in for awhile (30-60 minutes), then try rebooting it (hold down all 3 buttons)
Click to expand...
Click to collapse
I have tried this.. I can hear it booting up but still no screen =(
it would still be under warranty by motorola - especially if you accepted the OTA recently (May 2013).
Click to expand...
Click to collapse
How do I go about collecting the warranty on a phone that I bought used? And what would happen if it showed water damage? I swear I have not gotten any water/liquids on it, but this did happen after it was very humid out for a while, and I have read that high humidity is enough to spread the red dye (regardless of whether or not high humidity actually caused the problem)
SunLilac said:
Thank you for replying!
I have tried this.. I can hear it booting up but still no screen =(
How do I go about collecting the warranty on a phone that I bought used? And what would happen if it showed water damage? I swear I have not gotten any water/liquids on it, but this did happen after it was very humid out for a while, and I have read that high humidity is enough to spread the red dye (regardless of whether or not high humidity actually caused the problem)
Click to expand...
Click to collapse
call motorola (or go to their website and bring up a chat session in their online support section)
Try tapping it somehat hard with your finger all around the phone to see if it flashes the screen.
scottocs said:
Try tapping it somehat hard with your finger all around the phone to see if it flashes the screen.
Click to expand...
Click to collapse
No luck =( I've already tried "pinching" the phone somewhat hard all over too... Thank you for the input though!

Generic chinese head unit; touch screen sometimes unresponsive!

I would greatly appreciate your help. I have this generic Chinese made car Head unit (running android jellybean 4.2.2). I've had it for about a year and a half or so. A couple of months ago, the screen began to be unresponsive - after boot up. It is quite frustrating, as the unit itself is actually working.. but the screen just does not respond. This happens randomly! Sometimes you have to restart it several times before it works normally. And it does work normally sometimes, though there is no way to know for sure when it will work or not. So it just seems to happen randomly. Sometimes it will not work at all after several reboots. Sometimes it will just work the first time it's turned on!
. It seems to just be quite random. I tried using one of the screen calibration apps from the appstore. It seemed to make a very minor difference (or perhaps not!). The problem is still very much there.
Sometimes, while it's unresponsive, if you touch an app icon and leave the unit alone, after some time the app would eventually open - though the time it takes to do that greatly varies. At this point, the screen may then work - sometimes normally, but in many cases, abnormally or unpredictably. In some cases it will not work at all.
Please does anyone know what is responsible for this and if/how it can possibly be fixed?
One more thing I should add is that I suspect this started to happen as a result of an unsuccessful attempt to root the device. Could that be the reason... and/or is there any hope... i.e. can it possibly be fixed?
I have also done a factory restore.. but it still does this! Please help
Did you ever get any answer to this?
Best thing I would recommend would be to disassemble the unit remove the ribbon cables carefully be very careful removing the latches the plastic latches on the Zero Force connections and then make sure they're clean reinstall when it boots plays Five Fingers flat on the screen for about 10 seconds and it'll give you the touch calibration screen with four dots touch the dots from one then two then three then four then it'll give you the option automatically to save it and then let you calibrate the touchscreen hit configure start and then do each button one at a time touch the screen and then the left side touch buttons starting with power and then ending with volume down and that

Ghost Touches

My tablet suddenly started to suffer from "ghost touches". I already factory reset it and removed it's (great) screen protector, but to no avail.
Any thoughts besides service it?
Thank you!
Leo
Updated 1: problem solved rebooting to safe mode.
Update 2: see my post (#8) dated 10/10/18.
Does the problem occur all the time or only with the charger plugged in?
The reason I ask is that my Android YB has a similar problem with the Halo keyboard. Pressing and holding the shift or backspace key generates random characters. It happens only when plugged in and (interestingly) only in one room of the house. I've yet to find a reason, so I just unplug the power and run on battery while typing.
Another thought: my old Nexus 7 sometimes does the same thing (random touches) or becomes non-responsive. Turning it off and then gently squeezing around the edges and the middle of the screen fixes the problem for several months. I'm guessing that some internal connector is going bad (loose or corroded). It's one of those "can't hurt to try" things.
tjupille said:
Does the problem occur all the time or only with the charger plugged in?
The reason I ask is that my Android YB has a similar problem with the Halo keyboard. Pressing and holding the shift or backspace key generates random characters. It happens only when plugged in and (interestingly) only in one room of the house. I've yet to find a reason, so I just unplug the power and run on battery while typing.
Another thought: my old Nexus 7 sometimes does the same thing (random touches) or becomes non-responsive. Turning it off and then gently squeezing around the edges and the middle of the screen fixes the problem for several months. I'm guessing that some internal connector is going bad (loose or corroded). It's one of those "can't hurt to try" things.
Click to expand...
Click to collapse
Never tried plugged.
But I found the solution: just like Windows (!?) I rebooted to safe mode and... ...it's fine now. Seems that it was some weird driver error that a factory reset alone could not fix.
Thank you very much for your help!!
I just got a "refurbished" one from Amazon. What a nightmare! The random ghost touches are so bad I can't use this damn tablet! Now I have to send it back, get a refund and buy another. Ughhhh.
You rebooted into safe mode and then what?
Sent from my Self
Hi any updates to this? glad I found your post yes it is only when plugged in! must be a known problem.
Unplugged, fine
elcidroyale said:
You rebooted into safe mode and then what?
Click to expand...
Click to collapse
After a few days the ghost touches came back from the grave...
adamz2013 said:
Hi any updates to this? glad I found your post yes it is only when plugged in! must be a known problem.
Unplugged, fine
Click to expand...
Click to collapse
Tried another cable and charger?
I've found a workaround that made de Yoga usable again. In short:
1. Find where are the ghost touches using (developer options -> show taps). If you're lucky as I am they will be confined in just a few pixels is some border.
2. Root the device following this link:
https://forum.xda-developers.com/yoga-book/how-to/root-yb1-x90l-how-to-t3534268
3. Use some "screen resizer" from Google Play in order to disable the faulty row or column. In my case I started disabling the first 20 pixels. Now I'm with 10 and the Yoga is still usable.

Categories

Resources