Related
So, i'm usually quiet on these forums. Just reading, trying roms, etc. But here is something that has me stumped. Last thursday my phone crapped out. When i woke up and looked at it (it was connected to my laptop/charging) Applications were opening left and right, i couldn't close any of them because stuff kept opening. I tried to soft reboot it and it didn't help. Once it rebooted stuff started opening itself at random again. I ended up pulling the SIM and battery out and leaving it for 5 minutes. When i put it back and powered it up the touch screen no longer worked, but apps weren't opening on their own.
What gives?
I have hard reset (which means it's waiting for me to touch the screen to setup my rom), i have also taken off the screen protector (in case it had something stuck under it. Neither of these things helped. Per the forums I got a new screen, just put it in, and the touch screen doesn't work still... I'm drawing a blank here can anyone give me some advice. Going back to my Prophet for the time being but I HATE not having a keyboard (and it's slower than molasses)
have you tried flashing a new rom via sd?
Check that the screen protector has not moved under the front bezel and keeps pressing your touchscreen.
Robert
I have totally removed the screen protector and even replaced the screen for that matter so I dont think that's it. I haven't tried flashing a new rom. I just found it odd that this has worked for so long and now I get what appears to be hardware problems. As for flashing Via SD memory, is that better than doing it via cable for some reason? I'd be willing to give it a go...
Any other suggestions?
fiddelm3742 said:
I have totally removed the screen protector and even replaced the screen for that matter so I dont think that's it. I haven't tried flashing a new rom. I just found it odd that this has worked for so long and now I get what appears to be hardware problems. As for flashing Via SD memory, is that better than doing it via cable for some reason? I'd be willing to give it a go...
Click to expand...
Click to collapse
Similar problem happened to my Kaiser phone, although no multiple files opened, the phone just won't react to any touching, not stylus pen either. So I first soft reset, then hard reset, none of them works, now the phone can Sync alright, but the screen just stands on the Window Mobile screen, saying "Tap the screen to set up your window mobile device"
I only have this new phone for <3 weeks.
I went to HTC site, want to download a latest ROM file from them, after typing in the S/N, it won't let me, saying that ROM is not suitable for my phone.
So now I am download ROM file from this site, will choose one to flash the phone, see whether it works.
I will call HTC tech support tomorrow after Thanksgiving, see what they suggest
Hope some gurus here can also make some suggestion, Thanks!
Well I replaced the LCD and the new LCD works great, but the screen still doesn't respond to touches. What gives?! I hard reset and I got past the windows screen alignment thing by creating a welcome.not file but it's still pretty much worthless w/o a touch screen. Anyone have any suggestions?
Whoa, i thought something odd was going on. Never mind i got entirely the wrong idea.
Ha, not the case.
Anyone know if a flex cable would fix my issue? I dont really know what the felx cable is for but i've seen posts about people replacing them w/ LCD problems. I don't know if it is touch screen related or not, and i'm kind of tired of buying parts that don't fix my problem
please just flash a new rom whch ever you want (for some reason i thought you said that it keeps restarting your device because if that was the case the only option you would have was to flash via sd as activesync would load long enough for you to get a connection to flash from the computer)..trust me just try it..what have you got to lose
I reflashed one yesterday actually. The newest HyperDragon (which is looks like a new one is available today) It wasn't rebooting but initially windows were popping open left and right so i restarted it a couple of times(which i first had the problem, not yesterday) Yesterday it worked like any normal rom w/o the ability to touch. Anywho, after the flash of a different rom. No luck. I'm thinking it's a hardware problem of some sort but as i've already replaced the LCD i have no idea what?
yah thats sounds funky..you can bring it in for a warranty exchange either at a local DSC or over the phone (that is if your with att) and if not call HTC..all devcies come with a 16 or 18 month warranty
Well I called ATT yesterday, apparently I purchased the phone On Oct 17th 2007 which means It's out of warranty (apparently it has a 12 month warranty?) So it sounds like I'm SOL. So, i guess I'm off to ebay to try and fine a phone that I can canibalize to try and get mine going again.
touch screen
this may sound dum but when you replaced the screen did you replace the touch part as this is different from the screen
Well I picked up this
http://www.blackberry8100parts.com/...B3-NEW-HTC-TyTN-II-KAISER-P4550-_p_35-70.html
which includes the digitizer (from what I know it's all one part when they send it to you) The screen has the digitizer built in. So i replaced the part they sent me.
I just stated having this issue. My touchscreen stopped responding to touches over the weekend while the keyboard was extended. I just took the phone apart to make sure everything was connected right & put it back together, & now the touchscreen doesn't work at all. This sucks!
Any news? i'm having the same problem: no response at all, stuck at "Tap the screen to set up Windows Mobile-based device"
An interesting problem with screen
well my tilt fell out of the car holster while using gps and i suspect the screen hit my gear shift. I didn't notice anything odd after i put the battery back in it (yeah it fell that hard lol). Later that night I went to check mail and noticed something not right. Turns out my screen seems to have been pushed in a bit. Well here's the issues I've noticed so far: All the touch responses seem fine except for 1) the screen alignment doesn't register taps, but otherwise the touchscreen works and 2) on the htc home screen, I can't tap the house icon unless I tap any other icon first.
Initially I thought there was some pressure or deformation right at that particular spot, but it reacts the exact same way in landscape mode. I can't tap the house icon first; I have to tap something else first, then the icon works fine until I open a program or something and go back to the home screen. Then I simply have to tap weather or something and then home.
I'd reflash the rom or do a hard reset, but the screen alignment didn't work when I tried it so I didn't want to get stuck at the "tap your screen to begin" part.
Any ideas or do I just need to buy another screen or maybe just the digitizer. the amount the screen seems recessed is maybe a millimeter at most. Just enough so that I noticed a difference when touching contacts just above the housing. I tried cleaning by using a business card and running between screen and housing. Ohh... and one more thing... when I open the cube and then close it, I get what I refer to a static frazzle for split second and it goes back to normal. That only happened a couple of times after the business card thing. Do you think I just loosened a connection? damn... I still haven't taken it apart yet. Think I need to. Any help appreciated.
If your screen does not work, you can still use your phone. There is an app that you use on your computer that acts as the touch screen. This also works when the screen craps out.
http://www.sparus-software.com/spip.php?page=download&lang=en&ref=at&t=tilt
(EveryWAN Remote Support Personal Edition - Free download)
yeah -- my touchscreen didn't crap out totally, it just got muffed up when I dropped it a bit. Well, i went ahead and installed codefreaks remote screen alignment thing and did a hard reset. Well, the hardreset did the trick w/out the need for anything else. The alignment worked and everything. So, i'm back in business. Everything seems to work properly, except that my screen is still recessed a tad; but, that's not a big deal really.
From what I've been able to find from searching, I think my Tilt is about to bite the dust, but thougth I'd post the symptoms and see if anyone has any good info.
My screen has been occasionally fading to white. Not sure how else to describe it. It just sort of starts getting white, and within 2-3 seconds will be completely white. It is still working, that is, I can place a call (using MS Voice Command); I can play music.
I have SPB Mobile Shell on it, and a button assigned to go to the home screen. I can press that, and it will go to the home screen and display normally. If it is a hardware problem, I find it interesting that I can go back to the main screen. I suspect it is close to gone.
Any thoughts?
If so, anyone know what it costs to repair, and where to do that?
Sounds like a software thing to me, I hate to say it but try a hard reset. Do you have a 6.5 rom?
I've been thinking of doing a hard reset anyway, My memory is about used up. I'm not quite sure why. Probably should get it cleaned up.
No, I'm not on 6.5. I've been reluctant to make the move. I did some rom updates some time ago, and then the person working it decided to stop. I decided to stay with MFGR based roms after that.
ewingr said:
I've been thinking of doing a hard reset anyway, My memory is about used up. I'm not quite sure why. Probably should get it cleaned up.
No, I'm not on 6.5. I've been reluctant to make the move. I did some rom updates some time ago, and then the person working it decided to stop. I decided to stay with MFGR based roms after that.
Click to expand...
Click to collapse
Good thinking.
Likely NOT software but hardware -- could be the screen is going bad, or perhaps just the ribbon cable than connects the screen is broken or not seated properly.
burtcom said:
Likely NOT software but hardware -- could be the screen is going bad, or perhaps just the ribbon cable than connects the screen is broken or not seated properly.
Click to expand...
Click to collapse
So the hardware problem is just scared of the button he has assigned?
I have SPB Mobile Shell on it, and a button assigned to go to the home screen. I can press that, and it will go to the home screen and display normally.
Click to expand...
Click to collapse
Try putting the phone in the bootloader screen and let it sit there, that should let it go around the software.
Erm, yeah -- I guess that wouldn't be indicative of a hardware problem
Well, I am doing the hard reset. So far, no white.
Hmmm...lordy...I have a lot of stuff I try to put on this phone.
I wonder how much memory, both types, I need to keep available.
Don't put anything on the phone that you REALLY REALLY don't need. This is a taste phase and you need the least amount of BS on there.
Well, I've got most of what I need loaded, and have 61MB storage, and 63MB of Program memory free. Much better than before.
But I am still getting the fade to white occasionally.
I'm thinking hardware.
Anyone know if checking the 'ribbon' cable is user capable thing? I don't see it easily. I'll so some searching in the meantime.
Also, any feedback on cost and where for a new screen? Or do I just trash it when it finally goes?
[EDIT]
I am noticing that it particularly does it when I click the Windows (lower left) hard button on the front. I'm thinking it is related to a problem with that button.
Could be when you press that button you are flexing the cable enough to make it lose connection and go white -- this could be good news -- there are instructions scattered in this forum on how to take the phone apart. I'd recommend doing that and makeing sure the cable is firmly seated -- you should also inspect it for cracks.
Hopefully it's just a loose cable and making sure its in all the way will fix it -- if not you'll have to track down a new one.
Thanks. I'll do some searching for those instructions.
In the meantime, I called HTC just to get their thoughts on repair. First thing they told me was to upgrade the rom to the latest which is 3.57.502.2 .
I haven't been following ROM discussions. I need to check that out too. I wish I had seen or thought of that before I just spent a day with the hard reset/reinstall
did this get resolved?
I have the same issue. was it the ribbon cable?
update. I loaded a stock rom, and this appears to have solved the fade to white
Sorry...beeen away a bit.
I have not resolved the issue. It is intermittent, and hasn't happened for a few days now.
I searched and have found some instructions about taking the screen apart, but have not tackled that yet.
In my case I can't imagine changing roms making any difference, as I've had this rom for many months and it is just recently starting this.
I have found new LCD screens for this for ~ $30. I'm wondering if replacing the screen may be an ultimate solution or, if it is possible/likely that it is somethign else hardware related.
Been busy, and don't have the tools yet, so it may be a bit (or when it goes permanenly white forcing action) before I get any further on this.
It is definitely a hardware issue, my wife's tilt did the same thing, then it went permanent white. I first took it all apart looking for a bad ribbon cable or connection because it had taken a few good falls. But that was not it. So I bought a screen for about 30.00 online and shazam that was it!
Thanks for that info. I was thinking of ordering the screen, but concerned it could be something other than the screen (even though logically it would make sense that it is the screen.)
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 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?
So its been about a year and half since I received this phone for my birthday, and from this moment on, I am 90% sure that these companies design these phones to fall apart after a while so you buy a new one.
Please to not be intimidated by the length of the problems, I really doent want to waste a $600 nice phone. Please help.....
List of problems:
So on one random day, while I was using my phone with EnergyROM sense 6.1 (Not even 6.5 (Windows 6.5.5)) the phone stopped rotating when I flipped the keyboard, as in the screen will not rotate when I try to use the keyboard. The touch screen also becomes uncalibrated, and even when I recalibrate it, it still acts very funky (have to click lower than button or higher, depending on its mood). I did absolutely nothing different with my phone that day, but I did not call my phone dead right away, so I decided to update the ROM with the latest sense 6.5 ROM to see if the OS is corrupt or over-cached. This did not fix the problem.
Also, another very weird thing is the phone's screen will illuminate (I guess backlight), but no picture will show when turned on after sleep mode, and I have to click the top button again to sleep and awake it to get a picture. When flipped, the screen doesn't even fully illuminate, and literally dies down to a black screen (half of the pixels are bright, and then it just fails).
Any help would be very appreciated. What I am thinking of is wiping the phone 100%, and not even leaving a rom on it. I heard there is a command that deletes the junk off your phone from a previous ROM to your updated ROM is clutter free. Any other suggestions?
Edit: I hard reset my phone, and nothing is fixed; I still cannot flip screen into landscape mode.
The "command" you are talking about is called "task 29", look for it in the ROM section.
It sounds like hardware problems, i've had mine for about 1 year and a half as well and no problems besides a couple of scratches.
The flex cable connecting LCD and board might be out of order.... I had the same issue.
palmwangja said:
The flex cable connecting LCD and board might be out of order.... I had the same issue.
Click to expand...
Click to collapse
Yeah I heard about that problem. I will first task 29 it, but are there any guides to take apart and fix the flex cable, or even just unplugging it and plugging it back in?
Also, what did you do with your broken phone? Did you buy a new one or get it fixed?
Thanks for the feed back both of you.
my X1 also aged same as yours and it still runs flawlessly now. so it might depends on how you used and keep it
as for the "wiping off the phone" its called task 29, and is encouraged to do before you flash a new ROM, have you did it before flashing energyROM?
rhadrio said:
my X1 also aged same as yours and it still runs flawlessly now. so it might depends on how you used and keep it
as for the "wiping off the phone" its called task 29, and is encouraged to do before you flash a new ROM, have you did it before flashing energyROM?
Click to expand...
Click to collapse
No, but I just did now, but it seems to be a hardware problem because nothing seems to be working properly still. This is some serious BS because I am very over protected with this phone, just to prevent stuff like this to happen. I have never dropped it ONCE, and it seemed to just wear out by itself. The lenses covering the camera is cracked also, and the screen is all screwed up, and I didnt do absolutely nothing abusive to it, I am 110% sure of this.
Any suggestions on how to fix hardware/ ribbon connected to the screen problem?
Order a new cable and replace it.
If you search on Youtube for the video on how to disassemble x1 there is a complete guide that shows you. Its pretty easy and all you need to do is, take the flex cable out and carefully plug it back in. Then carefully put your X1 back together and hopefully you issue will be fixed. If it still persist, then try and get the flex cable changed.