I've had my G1 since last October, so it's a bit old.
Last month it started to play up. The recognition of the touch screen goes a bit haywire from time to time. The screen thinks I'm touching it when I'm not. Or it misplaces where I pressed, so it will think I pressed an icon 2 below the one I did. Also it thinks I'm pressing with 2 fingers when actually I'm only using 1, this is very annoying in the browser now I've upgraded my ROM.
I thought it was a software problem and so it was the primary reason I rooted and put a modded ROM on, but it has started again. Consequently I reckon it's a hardware issue.
Has anyone else experienced this problem? If so, have you cured it and how?
I believe that if you have a contract with tmo they insure your phone for a year (not entirely sure, I bought mine on ebay ), so you can simply unroot it and they should replace it for free. If you had the same problem before and after rooting then it's deffinitely a hardware issue.
I did wonder if it might be due to static.
Is that a possibility?
Related
I have done a reasonable amount of searching on this and have not found anything specific to my problem so figured I should post a question.
I have an issue with my Dimaond when it gets hot generally either using Wifi or Phone Data connection that the screen goes out. Basically everything goes to the left side of the phone so if you hit the Task Icon in the top right corner you get the Start Menu. Phone is basically useless at this point and you have to wait for it to cool down. Has happened since day one and is generally worse when using it when charging. I was watching Utube on it the other night 5min video while on AC charge and it went out. I am running Dutty 2.5 Rom and 25.07 radio have tryed 25.08 and 25.05 no difference was happening when the phone had orginal HTC ROM as well. Also will happen on a long call if the screen is on.
Basically feel issue is hardware related and maybe faulty screen still under warrenty so wanted to know peoples opinion on weather I should send back. Problem is will take a couple of weeks and I don't really wnat to wait that long if I can help it. Also assume it would be best to flash standard ROM back, should I do anything with HARDSPL eg should this be changed back as well if I send it back.
And before anyone says it I have tryed searching this topic and have found lots about HOT dimaonds but nothing related to screen going out at the same time :-(
Thanks
I had this issue in my JasJam (Hermes) whre the screen would simply go white after a while of use and I would have to leave it for a while for it to work again.
Unfortunately it sa hardware issue and you should claim a warranty repair on it
I can't see how this could be a software problem so I figured it must be the screen eg hardware related. Would be nice to know if anyone has had the same issue with a dimaond... Seems we may be spending some time apart, just hope it doesn't take long to fix..
I've had the same issue
http://forum.xda-developers.com/showthread.php?t=428976
My first device had been replaced recently (i.e. today) by my network provider (o2) and the new device seems to work without any problems now even if it's "hot".
(i.e. default screen adjustment + creating heat by activating the phone, wlan, bt + recharging it)
I sent an email to HTC regarding the fault and they said it would have to go back for a warrenty repair. I brought it through a resellar so has to go back to HK from NZ so will be away three weeks uurggghhh... Just seems odd I don't have any physical damage on the screen but hte problem has been around since day one as I remember having the problem the first day I got it. Juyst seems to be getting worse and is easily reproduced by usiung utube over wifi gets hot and it is all over. Just wondering if I should put an offical ROM from HTC back on the device before I send it back as I currenty am running Dutty ROM, what do you think....
i put the original rom back on and they still found out the the rom had been flashed, and would not repair on warranty
yep, i also asked about this problem
http://forum.xda-developers.com/showthread.php?t=438733
there are some youtube video's of how the phone behaves
my phone seems to do it less frequently since stopping using panosha's rom
im using alpha zero 7 at the moment..
i've also noticed that it isnt necessarily a heat issue, my phone does it completely at random
yesterday i found though, that when the phone did the alignment issue, i gave it a good shake.. and hey.. its all aligned again?!
maybe it was just a fluke, it hasnt freaked out since..
holding thumbs
Hey,
I also have the same screen problem, but my Alignment goes to right.
If I press on the left side, a press on the right side is recognized.
Good to know that Im not the only one with this problem.
greets doena
I got my phone back a week ago replaced the screen has been away for over two months, complete disaster, anyway all sorted now and I have not had the problem since....
I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.
Minus-1 said:
I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.
Click to expand...
Click to collapse
Hardware's fault ? Most likely not. I will give u an example of why I think it was software related. My device ran hot as well but I simply switched roms and now it's the complete opposite. Your most recent device most likely come with a different Rom in the phone.
About 2 months ago I was drunk and fell down with my phone in my pocket. I cracked the screen and that seemed to be the only damage. Touch screen still worked fine.
I had just gotten layed off about 2 weeks before so I didn't want to pay the copay/deductible whatever you wanna call it to get it replaced for just cosmetic damage.
Well not too long afterwards I realized my phone wouldn't mount via usb and I had an odd issue of when I slid the keyboard open while with an active text entry box the leeter 'x' would appear.
I upgraded my rom and both issues ended up disappearing (although they didn't appear with the same rom for weeks until the incident). Well now with cyanogens latest rom the problem with the x appearing is back. No one has mentioned in any of the cyanogen threads the same problem.
So basically, without trying to clutter his thread, has anyone else had similar problems? To me it seems like it is just time to pay for drinking too much and get it replaced, but if its a certain problem that happens randomly I can still deal with just some cosmetic damage.
I had the problem running cm 4.2.1 and now with 4.4 it seems to not have the issue anymore. This is just messing with my mind, I can't tell if it is a hardware issue or rom specific for me. No one seems to have the problem but it comes and goes with the builds I use.
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.
Hey
I am currently running 2.1 on my Samsung Galaxy S the only thing ive done to it is root it, so its running the normal firmware and I'm waiting till the end of september ti get the official 2.2 before I look at flashing something custom onto it, anyway...
I have an odd problem with the phone where the touchscreen part of the phone will become unresponsive for no real reason, sometimes playing a game, sometimes just sending a text or browsing the market. My actuall hard buttons like the homescreen or volume control still work during this and the only way to make my phone un-freeze is to press my power button once to turn the screen blank, then press it again and slide to unlock the phone, then it works fine.
No clue how to fix this... anyone got any ideas?
Thanks in advance..
Sounds like hardware issue. Get it fixed
Thanks for the response (know it was a while ago)
I've had the phone 2 months now in a contract with T-Mobile UK through Carphone Warehouse... Does anyone know what my return rights are? Talking to them later just want to know where I stand when asking for a replacement.
Thanks
Sent from my GT-I9000 using XDA App
hello, i have same issue. Did you fix this problem?
Thanks
This comes really long after. But did anyone find out the reason for this?
I've got an Galaxy S that works fine most of the time. But from time to time the screen will become unresponsive. If I press power button to lock the screen and unlock it again, it goes away. So it seems that it is a software problem.
Another peculiarity is that the keys on the Samsung keyboard are very inaccurate to respond to touch from time to time. Sometimes it is just impossible to hit a letter in the mid row and pressing "s" can put "wz" on the screen.
I was thinking to just put CM on it anyway. But it will void the guarantee in case it is a hardware problem. So I want to make sure that it is software related.
Did anyone manage to fix this either by returning the phone or removing TouchWiz. I am not living in the same country as I bought the phone. So returning it for a checkup will take some effort.
For what ever it is worth
I took the phone to an unofficial service center that flashed the phone with a brand new Android 2.3.3 (the phone came with 2.3.5). A downgrade, which normally isn't a very good deal. But the dead areas on the screen are gone. The phone is much more responsive and the keyboard is not acting funny anymore.
So... if you are experiencing the same. Try getting rid of the TouchWiz before you start taking the phone apart.
Good luck!
I get it occasionally but I've grown to live with it, mine tends to be the kernel recently flashed devils for 4.0.3 but after fiddling with volts mine stops.
Sent from my GT-I9000 using xda premium
Hello,
I bought a used Z1 almost a year ago. Everything was working perfectly, I was very content with my purchase but I broke the display shortly after. I got it changed at a local repairman but ever since then, my screen acts weirdly.
1. When I use the phone for 10-15minutes, it gets a little warm and so do my fingers and then the touchscreen starts acting weird and pressing stuff on its own. If I lock/unlock it, the problem is solved.
2. Same thing happens when the phone is turned sideways for a few minutes and when I flip it vertically, the touchscreen starts acting weird. Lock/unlock fixes the issue again.
The fact that lock/unlock fixes it leads me to believe that it's not a hardware problem. I started a research and found this topic - https://forum.xda-developers.com/showthread.php?t=2691849 , however it's a bit outdated and is already edited saying not to try the fix. I'm not proficient enough at this so I cannot really grasp the idea behind the topic mentioned earlier and can't get myself to try it cause it might brick my phone or something.
Any suggestions would be helpful.
Regards:good:
sorry to say you friend but it's a hardware problem it's something related whut the screen contrast I've tried everything the only thing left it's to get an original screen replacement and I haven't been able to get one in my country
Generic Screen, that's the problem, i would never recommend to buy a "new" screen, always buy an used one or a phone with broken motherboard and swap them imo
tbh, your problem is weird to, may be a bad installation, i had the same problem in a z1 that i use for games, disassembly all the phone and now I'm using the screen without gluing to the base and the problem was "solved"