So I spent the last hour or so searching for answers and have yet to find any so I figured ask all of you for some help diagnosing my Tilt. Last week it started to exhibit the following problems, what I need help determining is if the concensis is that I may have gotten the internals damp or if I have a hardware issue.
Symptoms;
1. Down D-pad button no longer functions, down track wheel works fine.
2. Sliding out the keyboard causes the phone to beep 10-20 times before you can actually start to type.
3. Random results when using the touch screen. it works 90% of the time but the other 10% if I try to say open an email by touching "in box" actually opens SMS inbox and starts to scroll through all the existing SMS messages.
I am thinking there could be a problem with the ribbon cable that connects the keyboard to the touch screen, or again, it could be wet.
Idea on a solution or further t-shooting to figure this out?
Related
Recently, my Tilt started "locking up" unexpectedly -- it is non-responsive to key or button presses, or touch screen presses, but the bluetooth and wireless lights blink occasionally so it appears to be still "alive". I have to take out the battery to reset it.
This started happening about the time I started wearing it in a belt case. I suspect I am somehow pressing some combination of buttons or partly sliding open the keyboard hwen I take it out of the case, but I'm not sure (obviously). It doesn't happen every time, in fact only about one out of fifty times I remove it from the case, but it is still bothersome.
Perhaps someone else has experienced this or can guess as to the case? Or, perhaps there is a way to turn off all external controls so they cannot be accidentally pressed - while still giving me a way to quickly answer calls/texts?
...................hmmm
[email protected] said:
Recently, my Tilt started "locking up" unexpectedly -- it is non-responsive to key or button presses, or touch screen presses, but the bluetooth and wireless lights blink occasionally so it appears to be still "alive". I have to take out the battery to reset it.
This started happening about the time I started wearing it in a belt case. I suspect I am somehow pressing some combination of buttons or partly sliding open the keyboard hwen I take it out of the case, but I'm not sure (obviously). It doesn't happen every time, in fact only about one out of fifty times I remove it from the case, but it is still bothersome.
Perhaps someone else has experienced this or can guess as to the case? Or, perhaps there is a way to turn off all external controls so they cannot be accidentally pressed - while still giving me a way to quickly answer calls/texts?
Click to expand...
Click to collapse
Steve - If after following the help Harkadenn gave you you are still puzzled - please read the threads on lockups on the Tilt. You wil find these in the ROM sections.
Now - it is going to be necessary to know some if not all of the following information:
1. where are you - US - SE - NW - Italy?
2. what is your carrier?
3. what ROM version are you running
4. have you flashed any other ROMs? or are you running the original
5. what programs have you loaded?
I suspect that you are NOT pushing any buttons - that this is actually locking up on you.
Bill
i thought at first it was me, then i thought, it was the invisible shield i have on my kaiser, but no... it turned out to be HTC's rom that was freezing up.
I flashed dutty's rom, and hey presto, everythings quicker, no lock ups, touch screen reponds 100%!
Even flipping the keyboard out, the rotation is instant!
I've been using my HTC Diamond for about 2 weeks now.
Bought it from www.plemix.com and it came unlocked , and I had no trouble at all using it and installing the HardSPL's / updating ROM (Dutty's Diamond v1.6) .
Today I ran the TomTom Navigator 7, and after a while it started to make continuous sound - the default sound when a button is pressed or touchscreen is tapped- , so I did soft reset a few times, didn't solve it, touchscreen was kinda jammed, and I took out the battery. A minute after I put it back, and it worked fine, I took some photos right after, and everything was working fine.
Then two hours later, I took out my phone from pocket to check the time, I see it's halted on the photo screen, and no response at all. So I just turned the phone off by taking out the battery, and just left it off until I came home.
Now the touchscreen is not responding to any taps or clicks, except that it seems that it still detects any sort of tap/click, because the backlight comes on from dim state when I try to tap it.
So it definitely means the touchscreen is not completely dead, but it's just not functional most part.
Hardware buttons works fine, but I'm stuck at the initial "Tap your screen to begin configuring your Windows Mobile" after hard reset. I even updated the ROM to Dutty's Diamond v1.8 just now.
Since I can't do anything and just leave it idle, it goes to [ Align Screen ] page, and still I can't press any cross, since the touchscreen is completely not responding.
Anyone had this screen death problem? Any method of solving it?
---Updated---
Just now the touchscreen worked for 30 seconds, i could actually align the screen, then it showed me the Date/Time setting page, where I could scroll the cities , but then it stopped working again. So i'm still at Date/Screen page...
--Updated--
The touchscreen works for 2 minutes after I do a soft reset / power on&off, or I should say, it works until you press some hardware key on the bottom (volume up/down buttons doesnt affect this).
After I press any of those buttons at the bottom, the touchscreen stops working.
Also, after I turn on the device, enters WM, and runs TouchFLO3D, for the entire time touchscreen works, it's constantly pressing the tasklist dropdown (upper right corner of the screen), making it constantly pop down the task list.
have you tried a hard reset?
Yes, like 3 times. Wiped everything, OS, ROM, NANDFlash.
Also updated the ROM from 1.6 to Dutty's 1.8 ROM. Everythingn works fine except for the Touchscreen.
Right now, when I turn on, the touch screen seems to be pressing all the time at the task manager part of the screen (where the [X] is), its popping up all the time the task list, then after a while, like say, 2 minutes, touchscreen again ceases to work.
Not really promising, but you could try to remove the screen-protector. Perhaps this releases any tension onto the screen.
Thanks. I've thought of that, maybe I'll try later on.
For now i'm suspecting that maybe water went in through, so I've put the phone upside down to maybe take out the water using gravity for 2 days.
It seems like it's working better now, with longer hours of normal functioning..
I'll wait and see one more night... if water is the cause of the problem, it should dry up in say 3-4 days.
It may sound strange, but pit it face down on the carpet and rub it around for a while. Its how I fixed mine. Don't ask me why it works but I had the same thing happen. I think somehow the electrical charge got dissipated from the screen and the static from the carpet recharged it.
Actually your words makes a lot of sense
My Diamond was acting completely alright today, used GPS for 2 hours and called a few people along with many weather updates.
Seems to be working fine now...
But I think what you said is pretty reasonable, since when I rubbed my dead screen , after a few rubs it started to work (2 days ago).
Thanks
yeah this had happened to me about a week ago exactly the same thing I had hardspl mine and updated radio to .05 and then a few days after I had the identical problem. However I took a shortcut and sent the phone back in and requested a replacement claiming it was defective they agreeded and sent a new one however this one already has .05 radio on it so I didn't have to hardspl it. I can't say any of these things would have worked form me as I did not try them byt symptoms are identical. my .02
After replacing the screen and reinstalling the HTC Rom I am having the most frustrating keyboard/button issue.
When I turn it on everything works great, it's like a new phone. No problems.
When the screen shuts off, either manually or automatically and I turn it back on is when the problem arises. When using the phone with the keyboard, the phone seems to randomly after any key (only on the keyboard) push the center button the front.
Lets say I'm typing in Word, after the 3rd character for example it will save and quit. In SMS it will make a new line. In explorer it will bring up the context menu. Each time the buttons on the from of the phone will turn on, which they shouldn't be doing.
I can use the buttons on the front to do what ever and the problem wont come up, only with the keyboard.
What could I have screwed up while replacing the screen? The thing I don't get is the correlation with the screen shutting off.
Fixed
I fixed it and I'm posting here in case someone else has the same problem.
The faulty part was the scroll wheel and it's little PCB board. I replaced that and now it works. I also discovered that if that piece is missing, you will have the same problem.
When my battery falls below 50% my touchscreen begins to act weird. No matter what I select it chooses whatever option is at the bottom of the screen. I can occasionally get it to work if I reboot the device or open and close the keyboard about 10 times. Once it has been corrected it falls back to the odd behavior within about five minutes. I have established that this doesn't happen if the batter is above 50%, and if I charge the phone up only a few percent then the issue goes away.
The phone currently has Cyanogen 4.2.15.1
I'm stumped as to what could be causing this and was unable to find any similar postings on the forum. If this issue has been addressed in another thread I would greatly appreciate a link to said thread.
Any suggestions would be great. Thanks!
My G1 also has similar problem, the touch screen is totally not functioning, I still finding the cause but it's so annoying. When the touch screen is not working, I can't invoke the "Dialer" function, that means I can't dial. Also, when there's incoming calls, the dialer function can't pop up too. That makes my G1 can't be worked as a phone when touch screen is not working.
Is anyone else experiencing the occasional mixup when hitting the back button? As not always, but many times regardless of the application thats open, I'll hit the back button and the search will come up and I wondering whether thats a common problem or a sensor in my phone is defective and I need to exchange it for a new one...
Thanks in advance
im having a different problem with the buttons. a lot of times my first touch wont register and i have to press it multiple times for it to be recognized.
I've noticed that my touch buttons aren't as sensitive as the touchscreen, and that I need to use a lot of pressure to get them to activate on the first try.
not alone there.. same issue here. I have a clear screen protector over them though.. though it shouldn't be a problem.. I've had the issue even before the protector so..
I have a problem with the back button too, not the other ones. However, when I press a spot a little to the left of the back button and not exactly over the button, it seems to register the press correctly.
I have found that the buttons just do not like any other finger than the index finger try to use the thumb and it will go to search or do nothing.I also returned my first phone as the buttons were terrible 80 percent of the time they would not work.So there maybe be a flaw in some of the phones as this one works fine even with the phantom skins on.The first phone would not even register a response with the skin on.
The buttons on the Captivate suck.
Buttons, as a construct, are well known.
The functional priority of the button is not a mystery and hasn't been for 100 years.
It has to click or otherwise give the user an indication the button has been pressed far enough to take effect.
It has to be tacticle. You have to have some way of knowing that your finger is on the button before you press it.
You have to have some leverage to put enough force on the button to make it move.
It has to be about the size of a finger tip.
It has to be visible. If you can't see it you can't press it.
It has to be different than other buttons that are millimeters from it.
It has to react the first time you press it, or you will naturally press it again, achieving unwanted results.
In all of the above, the Captivate fails.
The T-Mobile Galaxy has more a lot more real estate below the buttons to allow your fingers to get on to them, and a raised ridge on the rear surface of the phone exactly to give your other fingers something to grip against to increase aim and pressure.
But the Captivate has a nice lot of space at the top OH YEAH!
The only problem I have with the buttons is that I can't see them in a dark room
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm getting something similar. Sometimes when I hit the home button the search button blinks as if I had pressed it, then brings up the search screen. On my first captivate (mfg. date 7/16) sometimes it would happen once out of every hundred presses and sometimes it would happen 3 out of 5, very inconsistent. I traded that one in for one with a later manufacturing date (8/10), and my new one does it too but maybe only 1 out of every 100-200 presses. The fact that the search button blinks makes me think it's some kind of short/hardware issue. The back button has only triggered a search for me once, and that was on my first phone.
So this is a hardware issue or a software issue?
My back button on my phone must be pressed 4-5 times sometimes before it will register. The phone did not have the issue when I got it, and a friend of mine who has the Captivate as well does not have this issue.
It may be my imagination, but the phone seems to register touches better after I run a task killer or after restarting the phone, but tends to have issues when multiple apps are up and running.
I was having a button problem as well but fixed it by upgrading to JH3. h t t p://forum.xda-developers.com/showthread.php?t=767666
Your mileage may vary but it worked for me.
May be my imagination, but it seemed to be more isolated to back button on JH3 than JF6 on my machine. My perception is that if I take an additional half-second pause before pushing back button it registers more often. Do not believe it is hardware though. I believe that your home page(button), settings (button), and search(button) all reference something that resides in permanent memory(ROM) whereas the back(button) is trying to recall something that is in temporary memory (RAM) and possibly similar to lag issues may be related to Samsungs somewhat proprietary file allocation system. I am by no means computer literate enough to ponder concept any deeper than just mentioned.
I was having a problem with pushing the home button and the search would come up. I took it to a AT&T store and because I was still in the first 30 days they swapped it out for me.
i'm having a completely different issue with my touch buttons. my back button will register multiple button presses even when i'm nowhere near it. it's quite frustrating to be in the middle of an app and all of a sudden the back button goes off 3 or 4 times and gets you back to the home screen. i've tried searching the forums for some resolution or to see if someone else has had this, but not yet.
Edit: I must not have searched thoroughly enough, found another thread on this issue. http://forum.xda-developers.com/showthread.php?t=858873&highlight=back+button+issue&page=2