Database Develop

Tilt locks up unexepectedly

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!

Touchscreen Not Responding / Malfunction

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

Screen lighting issue.

XDA-Dev:
I hope this finds you in high spirits and good health. Just a day ago my phone started acting peculiar regarding the lighting of the touchscreen.
Firmware: 1.6 // Build: DRC83 // Rooted: No
Damage: Slightly scratched hard plastic from dropping 2-3 times. Otherwise, outwardly pristine
Upon purchasing the phone, I immediately noticed that the screen would creak if it was pressed on the bottom right hand side (by the send button). The right side of the screen also protrudes slightly higher than the left when in the open position. I have owned the device for about 7-8 months now and have noticed that on the rear, when in open position, there is a scratch where the sliding mechanism moves. The paint is stripped and the underlying metal is displayed in those areas. And now on to the issue at hand:
When the phone is closed (touchscreen only):
- When pressing MENU, or any key that would normally illuminate the screen, this does not happen. The screen stays dim, yet the lights on the buttons bellow it brighten.
- If I slide out the keyboard while the screen is supposed to be on (meaning the buttons are lit up), nothing happens.
When the phone is open (keyboard presented):
- And the screen is off, if I press MENU, the screen comes right up with no brightness issues.
- At this point, if I close the keyboard, the backlight disables itself. The screen is NOT completely blank. If I reflect the light of the room off of it, I can just barely make out that it is indeed displaying whatever task it was that was open, but if I were in a dark room, there would be no chance of recognising what is being presented.
- Continuing from above, once the screen's backlight is disabled and I reopen the keyboard, it does not turn back on. I must turn off the screen and turn it back on for the backlight to resume normal functioning.
One would think that if the issue lies in a loose wire that once the keyboard is extended that the backlight would regain normal functioning. Because this is not happening and that it is only working under certain circumstances, I cannot accurately ascertain whether this is a software or hardware problem.
Attempted remedies:
- Soft reset (both rebooting the phone by powering off and on and by going into the reset menu)
- Hard reset (by going into the reset menu and hitting ALT+W, etc)
Neither of these attempts succeeded in restoring functionality of the backlight. I've also search high and low through the settings, but see nothing other than 'Brightness' under 'Sound & Display.'
It may be noteworthy that I have the paid application 'Power Manager' installed. Though, perhaps not since this issue was still occurring AFTER the factory reset when no foreign applications were installed.
If you require any additional details, feel free to give a reply with any questions. I'm sincerely hoping I don't have to deal with T-Mobile or HTC to have this repaired. Any tips, ideas or possible solutions would be greatly appreciated!
Regards,
Ian

Update on issue:
On the way home from work, as the battery was on it's last leg (less than 10%), I turned off the screen while the device was in the open position after finishing a text. Upon attempting to re-activate the screen, it would not do so. As always, the side buttons lit up, but the screen was blank no matter what I did. I could hear the vibration from receiving texts and the red 'omg I\'m dying LED' was still flashing, so the device had not died.
Returning home, I gave it a reboot by removing and replacing the battery. I've kept it in the open position since it has been plugged in and am quite afraid of manipulating the slide mechanism any further.
I'll be calling t-mobile to get their opinion on any further troubleshooting momentarily and report back.

Sorry for opening an older thread. do you remember what t-mobile said was the problem? i am having the same issue.

simplewhite said:
Sorry for opening an older thread. do you remember what t-mobile said was the problem? i am having the same issue.
Click to expand...
Click to collapse
The ribbon wire in the slide mechanism is either broken or pulled out of socket.

[Q] Call Issues

Hello. I've had this device for awhile now and it's probably the best phone I've ever had.. except I started to have problems with regards to calls just recently. I actually rooted the device about 2 months ago and am currently using the Rombie mod v2 (JPC), if that helps. Anyway, the problem happens in the middle of a conversation, where the proximity sensor somehow disappears and the speaker mode is activated on its own (or maybe it gets in contact to my skin, I'm not sure, since the screen is supposed to remain blank). After that, the device becomes unresponsive: the touch sensitive menu and back keys don't work, and neither does the screen itself..but the hard key home button works and I could still hear the other caller via loudspeaker. I force a reset and everything goes back to normal (I mean this call issue doesn't happen all the time). I don't have any screen protector to affect the performance of the sensor. Anyone can help me out with this? Thanks!

screen doesn't come back on after call (proximity sensor issue)

Hi. my UK note (baseband N7000XXKK5, 2.6.35.7.N7000XXKKA, CF-root, stock ROM) has recently stopped turning the screen back on after a call (or during a call when I take the phone away from my ear to use the dial pad, go on speaker, etc.).
Normally the only way I can get the screen back is to hold the power key in until the phone reboots (though I've randomly managed to get it back sometimes, possibly when the other party hangs up and/or I'm pressing the power or home keys to try and get it back).
I've turned off the proximity sensor in settings meantime, and calls are fine in that state - but I don't want to waste battery and/or risk pressing stuff on screen with my head/cheek so I'm looking for a fix. Anyone else got this problem or suggestions for a solution?
I used the *#0*# test menu and chose "sensor". This gives a value of 0.0 for proximity until I put my hand within a few cm's of the sensor, at which point the screen goes green, the phone vibrates constantly and the reading changes to 1.0. Once in that state it stays that way when I remove my hand and doesn't change until I hit the back key.
Is the proximity sensor test intended to be a one-shot affair, or should it register 0.0 once I remove my hand?

My galaxy note is having a similar issue, however when I run the sensor test from *#0*#, I observed a different behaviour, where the proximity output says "1.0" and constantly vibrates all the time (which would explain the screen went black when a call comes in even if I put it on the table, as the phone constantly detects something)

sounds like yours is likely a hardware fault then. I ended up just leaving the proximity sensor disabled for calls and I don't really miss it. The only other thought I had was that my front cam has a load of dust built up under the display glass and it's adjacent to the sensor. I wonder if a layer of dust could trigger it?

actually I just re-ran the sensor test and it now toggles between 0.0 and 1.0 each time I move my hand over the sensor - so looks like in my case I have an intermittant problem. At least now I know how that test is designed to work. I will run it periodically to see whether anything specific is triggering my sensor to stop working.

OK, the following steps resolved my problem:
1. Remove microSD card and turn on the unit
2. Goto *#0*#, sensor test and verify that the issue is resolved
3. Put back in the microSD card
4. Repeat step to and now everything should be back to normal
Just rebooting the unit does not help (as I tried this before), but the above steps have fixed my problem.