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.

"Volume down"-key not working at all

Hey Guys,
I think I did a thorough research on that issue, but could not find any hints as how to solve it.
Background: I planned on flashing my ROM and thus first of all tried to get it on HardSPL. After some connection trouble I finally got it on (though the progress bar jumped from 0% to 100% instantly after like 1 minute instead of the indicated 10... is that normal?)
I then tried to reboot holding POWER+VOLUME DOWN, but it booted just regularly. Conclusion at this point: It is not on HardSPL. So I kept repeating, but never succeeded, until recently I noticed neither my VOLUME UP nor my VOLUME DOWN button works at all. Never, not matter how hard, gently or desperately I push - no reaction.
So apparently it is a physical problem. Does anymore know it? Ideas? In another forum I read that some Palm Pre users suffer from this issue on their devices. They advised to take out the battery and leave the phone in a bag of rice for 24 hours, as it is an issue of humidity.
Now if I think ahead - I do not even have a bill, but could probably get it form the seller - if I send it to SE as a case of warranty, they will certainly/probably see the HardSPL and send it right back.
Pretty srewed thing, huh? Anyone solved this problem so far?
Thanks in advance.

Frozen G1...Kinda

Hey all, long time reader first time poster regarding troubleshooting. I searched the site and couldn't locate anything regarding this, so I apologize if I fail at research. I have a T-Mobile G1, and the phone very oddly is running perfectly when the keyboard has been exposed but once closed the phone freezes. No touchscreen movement, trackball, camera button, ect; only the power button idles the screen to black. Now at first I got worried but I flipped the keyboard out and it functions perfectly again. I rebooted phone and it is the same case, the G1 start up and rom loading screen will remain frozen unless I slide open keyboard.
Is this a motherboard error? Seeing the touchscreen functions when open I eliminated that, but has this happened to anyone else? Thanks, and sorry for wall of text.

iRidill said:
Hey all, long time reader first time poster regarding troubleshooting. I searched the site and couldn't locate anything regarding this, so I apologize if I fail at research. I have a T-Mobile G1, and the phone very oddly is running perfectly when the keyboard has been exposed but once closed the phone freezes. No touchscreen movement, trackball, camera button, ect; only the power button idles the screen to black. Now at first I got worried but I flipped the keyboard out and it functions perfectly again. I rebooted phone and it is the same case, the G1 start up and rom loading screen will remain frozen unless I slide open keyboard.
Is this a motherboard error? Seeing the touchscreen functions when open I eliminated that, but has this happened to anyone else? Thanks, and sorry for wall of text.
Click to expand...
Click to collapse
Boot into recovery and see if the trackball works in there. If it does, then its simply a firmware issue and a full wipe should fix it. If it's not, then you probably dropped the phone or something and there is probably some sort of cable disconected/brocken inside the phone.

I completed a full wipe and am experiencing the same problems. I take very good care with my phone and was dropped once months back by someone bumping into me. Would it be possible for myself to self serve the phone and make sure all wires are secure? Or is it possibly anything else?

I have the same issue I've taken the phone apart along with many other G1s and have never seen this problem. I used this phone for almost 6 months lent it to a friend for a week and now it does this. So my guess is it's the flex cable between the screen and keyboard or would it have to do with the motherboard do you think?
I'm taking it apart as we speak I'll post what I find.

Did you have any luck, PlatinumMOTO?

HTC Hero CDMA Backlight

Has anyone ever had any issues with the backlight on the Hero?
Lately, sometimes, when I turn my phone on or something, it's as if there is no screen at all. It stays black, eventhough I know that the OS is running. I've even tried rebooting, taking out the battery, etc... I can tell it's booting normally because it does the little vibrate, and then vibrates once the OS is fully loaded, etc... cept, when this is occuring, I cannot see anyting on the screen. If I tilt it just right, I can JUST BARELY see the outline of a window or something (whatever is up on the screen at that time). Then after dealing with this issue for a couple of minutes, and rebooting a few times, it works itself out.
I'm thinking I'm starting to have some type of hardware failure, but really don't want that, because I'm due to upgrade to the EVO here in about a month and don't want a stupid replacement just so I can go buy a new phone a month later, ya know? Anyway, wondered if anyone has had the issue before and what, if anything, they may know to do to fix it.
Thanks guys!

Yes I get the same issue off and on. I think it has to do with CM6 and the brightness settings. Not sure though.

For some reason when I flash CM6 it sets the Automatically Adjust Backlight setting to be off. I figured it was just the nature of the rom, so everytime I flash a new one, I go and turn it on in Display settings.

Kcarpenter said:
For some reason when I flash CM6 it sets the Automatically Adjust Backlight setting to be off. I figured it was just the nature of the rom, so everytime I flash a new one, I go and turn it on in Display settings.
Click to expand...
Click to collapse
No man, I'm saying, even when I first turn on my phone, I dont even see the white HTC screen. It's completely black, but vibrates like normal when I press the power button to initially turn it on. It's fukd I'm pretty sure. I can't see a thing on it, not even in recovery. It's completely black, but vibrates at the correct times it should vibrate (when I first press power button to turn on, when the rom initially boots up, etc...)
I'm thinking my hero is dead....
I only had a little less than a month to go before I could get an EVO too.... damn phone.

Have you done any damage to it? Sprint might replace it for free.

derekwilkinson said:
Have you done any damage to it? Sprint might replace it for free.
Click to expand...
Click to collapse
Nope, I didn't do anything to it... unfortunately, I'm stuck with CM6 installed on it, because I can't see it to be able to switch back to the stock ruu... LoL
so I hope they don't notice and then say, well, too bad, u'r screwed because u rooted u'r phone. But no, my phone is still immaculate except the 'End' key is chipping off (the paint). That's about it
I'm hoping maybe they'll let me just upgrade to the EVO since I'm due in about a month anyway. I doubt it, but even if they give me a replacement (a new one) then I'd be okay with that.

Welp, they ended up replacing my phone with a replacement (refurbed) Hero... I pretty sure this one is 99% new though, not a single problem aesthetically and it seems to be running froyo quite smoothly. It basically feels like a brand new phone (which according to Sprint Reps, there's an 80% chance of getting a new replacement and 20% chance of getting a used replacement). I'm thinking I'm in the 80% range
Very happy thus far... just my touch screen is a little quirky right now b/c I installed a clear screen protector and believe some of the moisture is interfering with touches... which has been getting better as the hours go on. So that's' good!
Thanks guys on the info.... It's just fine for getting me through until Sept. 15th so I can upgrade meself on the EVO!!!!
We shall see if it holds up until then
Take ya'lls and thanks for all the replies

You should get the epic instead. Lol
(IMHO)
Sent from my HERO200 using XDA App

[Q] So upset, just bricked my 2 day old P1010.

Hey guys,
I'm really starting to think that my Tab is well and truly uber bricked. I tried (stupidly) to update it to gingerbread stock forgetting the flooping fact that the P1010 differs hugely to the P1000.
It was so weird, I got no error messages from Odin everything looked like it was going well, until I tried to get the device into download mode again. It won't turn on, I can't access recovery or download mode. It does try to come on when doing button combos but just shows a black/blank screen and turns off again as soon as power button is released. No icons or logos.
Another thing is that when off it flashes the creen every 10-15 seconds. Not sure what to try as battery will be running low by now and scared to let it go flat.
Anybody else got this, I feel like a right twat, don't even wanna know how much samsung will charge for repairing this.
If anyone has any more button combos to try please feel free to tell. I'm pretty deperate.

Josh at MobileTechVideos has helped me out when in similar circumstances.

sikodemon said:
Hey guys,
I'm really starting to think that my Tab is well and truly uber bricked. I tried (stupidly) to update it to gingerbread stock forgetting the flooping fact that the P1010 differs hugely to the P1000.
It was so weird, I got no error messages from Odin everything looked like it was going well, until I tried to get the device into download mode again. It won't turn on, I can't access recovery or download mode. It does try to come on when doing button combos but just shows a black/blank screen and turns off again as soon as power button is released. No icons or logos.
Another thing is that when off it flashes the creen every 10-15 seconds. Not sure what to try as battery will be running low by now and scared to let it go flat.
Anybody else got this, I feel like a right twat, don't even wanna know how much samsung will charge for repairing this.
If anyone has any more button combos to try please feel free to tell. I'm pretty deperate.
Click to expand...
Click to collapse
Edited due to pompous muppets
Sent from my GT-P1000 using XDA Premium App

Actually, that's the call...just return it and play dumb.
I forget the part that it was just a couple days.

I disagree with that advice. I hate dishonest people.

Just tell them the truth and see if theyvreplace it. What's the worst that can happen? They don't send you a new one. You won't be any worse off than you are now. Its worth a try.
Sent from my GT-P1000 using XDA Premium App

the best drama ever you can do
1- go and do not smile , chicken ..
2- be shocked all the time during you are talking and blame them
3- say , how come i sleep than i woke take out my tab from the charger i couldn't turn it on . is this can happen because of the ELEC ? ? Act like stupid ,
they will ask you did you try to update it via kies , say how i update ? ? ? after u say this , trust me , you'll get your tab in 3-5 work days

Wow, lots of dishonest people here. Use the de-bricking service, pay for YOUR mistakes, and chalk it up to a valuable lesson to read and pay attention to what you're doing in the future.

Just something i did when i thought my tab was bricked. I turned it on even though it wouldnt show anything on the screen. I then let the battery drain, next day I plugged it in and pwered it on, it worked.... is there any type of mode that you can get into?

GldRush98 said:
Wow, lots of dishonest people here. Use the de-bricking service, pay for YOUR mistakes, and chalk it up to a valuable lesson to read and pay attention to what you're doing in the future.
Click to expand...
Click to collapse
This is what I'm saying. Contact the guy from above and see if he can help you. You may pay for it, but some mistakes cost you money. If that doesn't work for you, then you're out $350 because of a mistake you made. If paying $350 for a mistake you made is the worse you end up paying in line, you're better off than most.

sikodemon said:
I tried (stupidly) to update it to gingerbread stock forgetting the flooping fact that the P1010 differs hugely to the P1000.
Click to expand...
Click to collapse
you didn't 'forget'... you didn't know. just nitpicking
I also support the return-it route. once it's back at samsung they can easily re-flash it to their proper software and sell it as a refurb.

I made your mistake today and I got the errors you've gotten ..
what did you do with your device , have you find a solution for it ?

I did this years back on the very first phone I flashed, a Sony 750i which I was trying to flash to 800i software. It usually would have worked as its same hardware but unfortunatley for me they had recently changed bootloader or something that made mine incompatible.
Since it was only a couple of days old from Orange shop I simply took it back to shop and played dumb, said I left it charging over night and now all I get is a white screen. At first they wanted to sent it off for repair and I kicked off because I didnt want to pay all that money for a faulty/repaired product, I kicked up a bit of stink in front of other potential customers and manager decided to give me full replacement.
Now I know that isnt honest but I meh I dont give a sh1t, Its not as if they would have had to pay for it, it would have simply got back to manufacturer.
If you have a new device and dont want to shell out a load of money or wait weeks/months just take it back and play dumb and if they refuse ask to speak to manager and kick off.

I PM'd you the details mate.

Same mistake here
Hi!
I know this is an old post, but this just happened to me today.
Just like you, i flashed a P1000 ROM to my P1010 galaxy tab.
The process went perfectly with no errors nor warnings in ODIN. When it tried to reboot, a black screen came up. The symptoms are the same you had. Black screen, no image of any kind, no possibility to put it in download nor recovery mode.
When i press the power button for about 5 seconds, backlight coms up, but still a black screen. When i let the power button go, the backlight goes out and the screen keeps black.
Could you please tell me how you solved this?
Thank you VERY much!

mattogodoy said:
Hi!
I know this is an old post, but this just happened to me today.
Just like you, i flashed a P1000 ROM to my P1010 galaxy tab.
The process went perfectly with no errors nor warnings in ODIN. When it tried to reboot, a black screen came up. The symptoms are the same you had. Black screen, no image of any kind, no possibility to put it in download nor recovery mode.
When i press the power button for about 5 seconds, backlight coms up, but still a black screen. When i let the power button go, the backlight goes out and the screen keeps black.
Could you please tell me how you solved this?
Thank you VERY much!
Click to expand...
Click to collapse
Try the same thing (Power +Volume down 5 seconds), but plug your tab to your PC before doing it and see if ODIN can pick it up. If odin can pick up your tab, flash the right ROM.

I think if black screen and then buttons lights up briefly when you touch, you somehow need to force it down first.
Try holding power button for at least 10 seconds to bring it down completely.
when it then doesn't response to touch, then do what yappoe said.
Hope your battery hasn't been drained by now.

I already tried both of the solutions you propose. I really appreciate that.
The screen keeps black, but the lights of the buttons doesn't turn on. Not even briefly.
I followed a guide that says i should tape the power button to keep the backlight on the entire night until the battery drains, so i can get out from an infinite loop. Then to plug the tab in the wall charger and the battery logo shoud appear. Then try to turn it on in download mode.
I did all that. Battery drained out, but at the moment of plugging the tab at the wall, it does not show the battery indicator. Screen is still black. No backlight, no nothing.
Do you think a JIG could work? any other ideas? it's kind of dead!
Sorry for my english and thanks again.

I don't know.. but you should assume it is still charging. Leave it for more than 4hr charging then try yappoe suggestion.
If all fails, then repair.
Next time only flash rom made for your device...
Sent from my GT-P1000 using xda app-developers app