Database Develop

Touch Screen has stopped working

Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.

Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.

Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.

When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.

Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks

gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night

Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.

Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.

screen issue

Hello all,
Just yesterday, I noticed something in my screen which I thought that it was a foggy screen from inside, so I thought that I'd leave the screen for the night, and let it dry. However, I woke up the next morning only to realize my screen stopped functioning, touch screen stopped working (please see attached files). Did someone experience a similar issue? Good thing I though squaretrade warrently when I bought the phone. I'm just worried they'll think its a physical damage. btw, should I restore everything to manufacturer settings? I installed ENERGY ROM. However, I wouldn't know how to do it since the touchscreen does not work.
Thanks in advance...

First, this looks like a collapsed digitizer.
You can try to pull the top layer away with duct tape, that might get you running again.
For warrant, if they refuse, fight them because it is a common issue with the Topaz. Search for "Newton Rings" or "Oil under screen" for many more posts related to this hardware failure.
You may want to flash back to stock before returning it, just to make sure they don't try to claim its software related.
To do this you would need to flash back to your stock ROM first, then go the the HSPL thread and and flash the relocker. You can do this without using your screen.
I would also take a good look at your warranty and if you can get away with permanently disabling it for a new device.

I'm glad I never bought the good looking TD2 and avoided all of this. There are tons of people complaining about this on the forum

Me too, I've only seen one Pure with this issue, but about 30% of Topaz with repeated failures even after repair.

[Q] Touch screen dead spots

This may be a problem beyond the scope of android, but seeing as I'm running it, I thought I'd try here first.
I've noticed that the lower left hand side of my screen has a "dead spot" where touch is simply not registered. To illustrate, I went to screen calibration's test screen and drew a straight line along the edge of the screen. (See Attachment)
I've tried recalibrating the screen (manually and resetting to default calibration) as well as wiping data and reinstalling the system. Reinstalling the system worked once, but then the problem came back and subsequent reinstalls did not fix the issue.
I'm running Incubus26jc super froyo [RLS 12] on the 15-07-10 340X480 Froyo Kernel.
Anyone else seen anything like this? As far as I can tell, the problem is not getting any worse. Currently, it's only a hindrance when trying to use keys in that region, but I can work around it by switching to and from landscape. It's a bit of a hassle, so I'm hoping someone may be able to shed some light on the situation.
I was sure it was hardware until the system reinstall fixed it, but am now baffled as I can no longer replicate the fix.
I have not tried reinstalling the kernel but will at some point in the next day or so. I'd like to avoid switching back to WM to check if the problem persists, but may have to... we'll see. Doing everything I can to make this phone last until the Incredible month of February when I'm up for an upgrade.

dont know the issue resolution... but i have the same with my touch vogue.. and in the same 'area' apparently as well.
hard for me to hit the 'a' key on my keyboard. hehe

I'm glad to see I'm not the only one... anyone else?

Bottom right corner for me... I was able to calibrate around it but it took a few tries.
Sent from my Full Android on Vogue using XDA App

The sensitivity across my screen was inconsistent some time ago. I found that years of my abuse had taken a tole on the exterior of my phone. It eventually got worse and I bought a new housing (with a new digitizer) on ebay for a reasonable price. If it is hardware then it really isn't that hard to fix if you like taking things apart.
If you're sure that win mo accepts input from that part of the screen then nevermind my post. I would play with a painting app though and investigate the hardware further.
I may be talking a little out my a$$ with this part but.. is it possible that in calibrating your screen the os may change it's settings on how hard you have to press and such also. that may be how you got it working.
In any case, my investment in a hew housing was well worth it considering how modern my old phone has become thanks to the developers here.

gooph said:
I may be talking a little out my a$$ with this part but.. is it possible that in calibrating your screen the os may change it's settings on how hard you have to press and such also. that may be how you got it working.
Click to expand...
Click to collapse
In my case, no - when drawing a straight line down or across the screen, the line starts 'moving' away from the stylus (like the picture in the OP).

Gah... now it's shutting itself off randomly and the dead spot has grown. Not good at all.

Yeah, mine was better for a while then 'slid' again. I ended up swapping the digitizer with my other Vogue and things are back to normal.
Sent from my Full Android on Vogue using XDA App

I have another vogue, but am weary of doing anything like that. How hard was it to get done?

All you need to do is switch the front half of the housing rather than the digitizer itself- it's not hard. There's a teardown guide somewhere in the forum, Google Vogue teardown and it should be at the top.
Sent from my Full Android on Vogue using XDA App

The only thing that worries me is that my spare vogue exists because it was dropped in a muddy puddle. I'm hoping the water damage isn't too bad. Guess we'll just have to see.

it is really annoying
I have the exact same problem and I too thought it was a hardware issue till I saw this Thread. I was ignoring it till two days ago when it started really bugging me. Now, I don't even need to press any button and it automatically gets pressed around the curve and I have a google search box there, so it keeps on searching for eee or sss randomly and started draining my battery. Is there a proper fix for this?

I thought I'd chime in too... I could never seem to calibrate the touchscreen properly in either Android or Debian. Changing the screen resolution (i.e. msmfb scaling) seems to have no effect, whether it's 240x320 or 640x480. Any area within 5mm or so of the edges of the LCD will register as the edge, making "A" and several other keys on the virtual keyboard impossible to hit. Passing calibration values to the kernel didn't seem to fix anything, but it's possible I was using them the wrong way...

i have the same kind of problem on my Kaiser... i think its realted to hardware... either the housing or the digitizer...

I am experiencing the same problem on X10 mini pro. the same screen spot exactly, i have to try very hard to get z or x or shift to work. Sometimes when I try locking the screen and unlocking it back, it works.

update
so after a very long time with this problem i decided to change the digitizer and problem is gonne. visualy the broken digitizer had nothing wrong with it. The fix was fairly easy though, there is no glued parts involved into getting a new digitizer on the u20i.

Touch Screen
I just bought a brand new Cubot One and it looks more than perfect! It has just a little problem with the touch screen ( I think its the software, need ROM change). There is a dead line on the right side of the screen that touch doesn't work at all. Any solutions? Anyone faced that before? Can I fix it myself or do I have to send it back for replacement? Is there any video or guide that shows its done?
I uploaded a video on YouTube to show the problem but i cant post it yet.. (new member)
You can write "Cubot One touch screen problem" and it's the 1st one.
Thank You!

[Q] Broken Screen

Hi there, I know there are other threads on this, but I've got two questions;
I might be able to claim a repair on insurance - the policy doesn't state anything about rooting voiding it, but I'd want to play it safe and flash back the original RUU - now, the digitizer works on my phone, but the LCD is totally shot, can't read anything.
It's been a while since I flashed the RUU, so is there any point where you have to press a button or something on your phone to advance? is it possible to use ddms while flashing the RUU to see what you're doing?
Also, if I can't claim this on insurance, how hard is it to replace the screen yourself? I've seen a "genuine" (hmm.) LCD/tools set on ebay for about the same amount as my insurance excess, so this seems like it could work (if it's easy enough!).
Thanks!!

laughingcavalier said:
is it possible to use ddms while flashing the RUU to see what you're doing?
Also, if I can't claim this on insurance, how hard is it to replace the screen yourself? I've seen a "genuine" (hmm.) LCD/tools set on ebay for about the same amount as my insurance excess, so this seems like it could work (if it's easy enough!).
Thanks!!
Click to expand...
Click to collapse
I've not done it personally but I have seen the guys in the phone shops doing it.
It's not that hard, but you have to know what and where to remove. Just go slow first.
pardon this but what is ddms?

Hi,
I have flashed RUU for my Tattoo at least twice. And as far as i remember there is no point you have to do anything on your phone. It will reboot (into fastboot i think). You will se progress on computer screen.
By the way, how can the LCD be broken and the digitizer not? Is the lcd shattered?
This is against laws of physics!

Oh, maybe I got the letters wrong but ddms is part of the android sdk, so you can take screenshots on your computer - also handy if you've broken your screen and need to know where to press.
As for defying the laws of physics, I guess the Tattoo is more special than we thought! the lcd is showing up loads of black/white cracked patterns (but a small it at the bottom works, so I can just about make out my dock. )
Thanks, insurance guys seem to be a bit more helpful now, so hoepfully won't have to resort to doing it myself.

Just in case anyone else has this problem, found this nice photo-guide to unscrewing everything: http://translate.google.com/transla...acenter.ru/razborka/htc_tattoo/&prev=_t&twu=1
haven't got round to it yet, but should do after exams.

Thanks useful info.

I have opened and dismentled everything my tattoo 3-4 times refering the guidlines. It is really helpful.
I was trying to resolve a touch screen problem. My phone acted like something is always touching at a point of the screen, so, I couldnot able to select a thing correctly and it is worst while typing using screen keyboard. So, I disassembled my tattoo and clean everything inside and assembled again. It seems working correctly for few hours then the problem reoccurred. And I disassembled again and again.
Atlast, I found out the problem was just on the screen protector, I have removed it and resolved the problem. Funny problem but it is worth all those efforts.

Bad Digitiser
Recently the Digitiser of my phone went bad. I tried flashing back the Stock RUU but did not succeed since it was not able to detect my phone. Then I just flashed back the backup of the stock ROM and took it to the Service Center. To my surprise the person didn't even check whether the phone was rooted lr not. Since it was out of warranty I still had to pay I still had to pay $45.

search button glich

Hey all, recently my search button randomly presses itself. No, I dont see the color flash or what ever you see when you press a button but at least 2 or 3 times a minuet it will act as if I have pressed the button and search will come up... Some sort of new glich? or is my phone going defective? What do you think?
ROM firefly 3.0 that i have been using since it came out, so like a month with NO problems what so ever. Reinstalled FF, still did it, will try a new flash, if that doesnt work will go to stock. and if that doesnt fix it I will get it warranty replaced.... but Im hoping its not hardware...
???

This happened to me! Try reflashing the kernel, or using a different one. Might help

I noticed that when my cappy has a fingerprint or smudge on the search key, it magically will press itself. I also had to modify my invisi-shield to not cover the touch buttons. It happens less now that its not on them, but it still happens.
It was happening over and over and I looked at it and theres a smudge, wipe it clean and viola! This was quite annoying when I was using a rom with the camera mod that redirects it to the search key. The camera was constantly opening, had to run the "fix" to revert it back.
Hope its just as easy as that for you, I was able to duplicate the problem on 3 cappys so far.

this could be a moisture issue. yank the battery and drop the phone in a bag of rice for a day see if that helps. if it still happens flash to stock if it still does it after that its a hardware issue and you should get a warranty replacement if thats an option.
a search would've answered this as i personally have answered this question a few times, also this is a question, for future knowledge those are posted in the Q&A section.

by that do you mean put it in a bad ontop of rice or literally stick it into a pile of rice ( wouldnt that get into the phone)? sorry for such a noob question.

Put the phone in the rice. None if it is small enough to get into the inner workings of the phone but it is AMAZING at soaking up all little bits of moisture.

Would be willing to bet it is a moisture issue. I have the same problem no mayer what rom I am using
Sent from my GT-I9000 using XDA App

Mine does this quite a lot as well. Most often when the phone is warm while charging. I've noticed holding it in a different position helps diffuse the problem as well. Must be a hardware defect. :-\

so are the chances good that the rice will take care of it? Strange, I never shower or use my phone in wet area's.....
I have squaretrade... do they swap it out or what is the precedure for getting a new phone from them if it doesnt work if you know by chance, if not, Ill just google it on the website