Related
hey guys, i have an unlocked tilt, flashed with the htc rom, and for some reason it randomly locks up.. i especially notice it with PIE, but also with other programs. i usually have to wait 5-6 seconds, and then it works again. the weird thing is that from what i remember when windows mobile freezes up, and you click a bunch of different buttons, as soon as it un-freezes, all those buttons are pushed, however in this case, no matter what i press, when it un-freezes, it just stays where it is.. im beginning to wonder if i just have a defective screen or something, but i dont remember this happening with the tilt rom tho... any help? thanks
omar
I have the exact same problems...
same here, did it when i had the att rom on it also.
I *had* the same problem. I did a Clear Storage, and everything is fine now. I sware my problems started after I loaded the HTC Home plug-in. After I did the clear storage, my problems went away.
I'm running the Tilt on the Cingular ROM at this time for what it's worth.
I didn't run the HTC ROM long enough to see if it did it also.
Clear Storage
What does clear storage really do?
fredm said:
What does clear storage really do?
Click to expand...
Click to collapse
Basically resets it back to how it was when you first turned it on...no contacts, no apps (other than what it shipped with), etc. Basically a factory reset.
If you used kaiser tweak to set your ie temp files to storage card, this will make your kaiser freeze. set back to default.
My problems happend with the HTC rom, and are still happening (although the freeze time is shorter) with the Helmi ROM. I didn't have the ATT rom on long enough to notice it.
Are any of you guys using the Shogun threaded SMS app?
Threaded app works great. Its most likely that you tried to set your Pocket IE storage cache to your storage card. this is a known issue. I believe there's a fix around, but without that fix, you can't put your IE cache on the Storage Card. Set it back to your main memory and you should be OK.
jomo25 said:
Threaded app works great. Its most likely that you tried to set your Pocket IE storage cache to your storage card. this is a known issue. I believe there's a fix around, but without that fix, you can't put your IE cache on the Storage Card. Set it back to your main memory and you should be OK.
Click to expand...
Click to collapse
Thats not likely, seeing as how I've *never* done that... ever. And the problem happens outside of IE also.
BoostedSR20 said:
Thats not likely, seeing as how I've *never* done that... ever. And the problem happens outside of IE also.
Click to expand...
Click to collapse
Are you using the HTC home screen? I'm wondering if that may be a culprit in more than one issue I'm seeing...
Are you using blackberry connect? I was using version 4.0.0.90 then switched to 4.0.0.84 and my random freezing went away.
HTC home screen = always
Blackberry connect = never
Every rom I used with my 8525 had the HTC home screen, never had freezing issues this bad. Although I do remember having some...
OK, did you use the official HTC ROM? Or one of the cooked variants?
I have witnessed this problem on ATT ROM, HTC ROM, and a cooked ROM. I wonder what is causing this.
jomo25 said:
OK, did you use the official HTC ROM? Or one of the cooked variants?
Click to expand...
Click to collapse
All of the above.
Same here with Helmi's Big Storage Clean Rom.
My ATT Rom with schen's HTC homescreen plug-in freezes too, although I think it did before I put it on. It won't accept screen taps for maybe 10 seconds or so, then resumes running fine.
I just performed a hard reset and am starting from scratch. My problems are directly related to PIE and large websites. I did that webview.dll hack thatI just did it to try it out, but I think that is when my major issues started happening. I'll see how things go now with the stock AT&T Rom without customization.
I've been noticing the same behavior, but I noticed it when I was running the stock AT&T ROM, so I'm not 100% positive it's related to HTC Home.
At first I thought it was just really crappy screen recognition, but I've been noticing it with the hard buttons as well, so I don't think it's related to the screen.
Okay, so to those of us who have problems with screen ignoring/being very slow with screen taps and/or buttons, read on.
I flashed ROMeOS ROM and started having problems where I would tap on something, and it would ignore it. I would keep tapping and tapping, but nothing happened. Sometimes, even hardware buttons were ignored, about 40% of the clicks. I never had that problem with Dutty's Diamond ROM or WM6 ROMs. Issue seems to be related to latest 6.1 builds... or so it seemed at the time.
After pulling out half of my hair, reflashing all kinds of ROMs, reflashing to latest HardSPL, etc etc... I almost threw my kaiser at the wall.
First I thought it's TouchFLO, then I thought that it's the latest 6.1 ROMs.. then I thought it's related to 3.56 HardSPL.. well eliminating those factors one by one DID NOT fix the problem. Right now I went 100% to stock ROM (one it came with) and AT&T's original SPL. I started having sound problems (w/e radio I tried did not work) so I flashed Hyperdragon Wm6.1 ROM.
About 90% of the problem is phone ignoring ANY kind of touchscreen taps/drags.
About 10% of the time its the hardware buttons that have the problem - for example I push "call" (or any other softkey) button, and nothing happens, while touchscreen could be working fine at that time. In about 10 seconds, hardware buttons would start working again.
Some information that was gathered from this thread and personal research:
It looks like problem is NOT related to the following:
- POWER. Connecting phone to AC power does not solve the problem. Subjectively, it may improve it a little.
- BLUETOOTH/WIFI. Problem persists with EVERYTHING disabled and phone being in Airplane mode.
- PARTICULAR 6.1 ROM. I had this problem on ANY 6.1 ROM I tested (and I tested all the way from AT&T almost-official WM6.1).. maybe that's why they didn't release it?
- OPERA browser. Some people never had Opera and they still have this problem (please confirm this!).
- SPB/WISBAR interface software. Although having Wisbar stuff does make it a lot worse for me.. and I still have the problem without SPB or WISBAR installed.
- S2U2 screen lock. Still had the problem w/o S2U2 installed.
- iGo 2006 or iGo 8. Many users with this problem never used iGo.
Problem MAY be related to the following (needs more research, please help):
- Original SPL versus HARDSPL 3.XX
- WM6.0 versus WM6.1 (I don't think I had any problems running original AT&T 6.0 ROM, but I did have sound (radio) problems, so had to flash 6.1). Several users report that WM6.0 is immune to this problem.
- A combination of running WM6.1 with latest HardSPL?
- Custom ROM VS Original ROM. Perhaps problem is in the tweaks to the registry.
- Simple things like overtime connection weakening in touchscreen connection to the mainboard. Whoever can open a Kaiser could try to replug/clean it and report back to us.
- Radio version. Should be easy to test, just need to reflash all kinds of older radios and see if problem persists.
Please make sure that you test your phone with some touchscreen intensive games/software a lot for AT LEAST 3-4 days. I had it happen several times where it would be fine after reflash for about a day or so, and then it would come back in full force.
BRICK?
In my case, running HTC WM6.0 ROM with HTC SPL DID NOT fix the problem, I can even say it made it worse. Touchscreen would respond to about 10% of the screen taps. Tap pressure doesn't make any difference.
Also, running AT&T stock shipped ROM with stock shipped radio and SPL did not fix it. I guess at this point, nothing will. Waiting for replacement tilt.
Hope nobody else will get it as bad as I did. All I can say is... make those relfashes count.
Hmm isn't Touch Flo one of the cool things with the Kaiser??? How do you navigate in programs now it's disabeled?
DarkDvr said:
Okay, so to those of us who have problems with screen ignoring/being very slow with screen taps - I think I've found a fix. Here's a little background:
I flashed ROMeOS ROM and started having problems where I would tap on something, and it would ignore it. I would keep tapping and tapping, but nothing happened. Sometimes, even hardware buttons were ignored, about 40% of the clicks. I never had that problem with Dutty's Diamond ROM or WM6 ROMs. Issue seems to be related only to latest 6.1 builds.
After pulling out half of my hair, reflashing all kinds of ROMs, reflashing to latest HardSPL, etc etc... I almost threw my kaiser at the wall.
So if you have similar problems - try using Shnaps' Advanced Config to disable the TouchFLO altogether.
Another thing that I've used is PocketMechanic to clean up the notification queue. After fresh install of HypreDragon (latest as of Aug 5), I had 46 duplicate notifications. Removing those seemed to ease the problem, but NOT fix it. Disabling TouchFLO seemed to finally fix it.
I hope this helps somebody. I'll update this thread if I keep having this problem..
Click to expand...
Click to collapse
Thanks for the head's up! I'll definately try that tomorrow (danish time).
Foxhunter123 said:
Hmm isn't Touch Flo one of the cool things with the Kaiser??? How do you navigate in programs now it's disabeled?
Click to expand...
Click to collapse
Never really caled for it, I use my hardware buttons (D-pad) to scroll, I find TouchFLO to be too unreliable... maybe it's just me, but nothing beats a hardware button which you actually "PUSH".
spip72 said:
Thanks for the head's up! I'll definately try that tomorrow (danish time).
Click to expand...
Click to collapse
Do you have the same problem?
Hello,
First off thak you for the post. Ive got two identical Tilts both with the exact same radio/boot/roms. One has this issue and the other doesnt. I will be disabling it on the one havong the issue and report back! Thanks much!!!
I was also having this problem. my biggest complaint was my keyboard was all over the place. Sometimes it wouldnt see key strokes at all, other times one key hit would register as 3 or 4.
Sent a few test messages and This seems to have helped.
THANK YOU!!!
My Kaiser was getting close to being flashed back to a WM6 rom or quite possibly embedded in a wall.
where do you find cab for touchflo? I was looking for that but could not find it.
tamkhanh said:
where do you find cab for touchflo? I was looking for that but could not find it.
Click to expand...
Click to collapse
seek and you shall find.
It's all over the place.
Try playing around with the TouchFLO sensitivity options in KaiserTweak
i upgraded to official 6.1 about two weeks ago...
i recently started having the "missed taps" problem...
i have a feeling that KaiserTweak has something to do with the issue...if memory serves, i don't remember experiencing the issue BEFORE i played with the "TouchFLO->Sensitivity" and "TouchFLO->Finger Pressure" options...i just launched KaiserTweak right now and its showing those values as set to defaults where as i could've sworn i changed them to the advised settings a day or two ago approximately when i started experiencing the issue...just a point to clarify, i was only playing around for no particular reason and my taps were not problematic before
i've just changed them to the advised settings and did a soft reset to see if these are the kind of settings that are forgotten after a soft reset...but they stuck...so i'm gonna observe this for a couple of days with the advised settings effective and see if they have reverted to defaults on first sight of the issue...i'll report back here if that happens because that would be a pretty strong correlation...almost enough to prove cause and effect
Well, problem is, last time I've used KaiserTweak was like a year ago, so my touchscreen problems cannot be linked to KaiserTweak. I don't even have it on my tilt.
Also, it's definitelly not a touchscreen itself, since this problem is application-dependent. Once again, S2U2 and Opera are immune to this problem. Windows' build-in apps (file explorer, bottom bar, etc) all suffer from it.
I've noticed this too, but I've found a slightly longer tap seems to make things reliable for me.. Instead of a quick 'jab' if I sort of touch it, it seems to be better.
and keyboard too I've noticed.. I mostly notice it with the hard keys rather than the keyboard, but I don't use the keyboard a lot.
I'll try looking for duplicate notifications, what else will do that besides MemMaid? I might reinstall it, it was handy. I previously found phoneAlarm would grow notifications over time, I suppose I need to watch for that anyway.
khaytsus said:
I've noticed this too, but I've found a slightly longer tap seems to make things reliable for me.. Instead of a quick 'jab' if I sort of touch it, it seems to be better.
Click to expand...
Click to collapse
True, if I keep pushing on the screen button, in about 5 seconds it will be clicked. But that's ridiculous, i gotta say.
I'll try looking for duplicate notifications, what else will do that besides MemMaid?
Click to expand...
Click to collapse
I use PocketMechanic - good stuff. Has lots of useful functions, including notification queue cleanup and analysis.
Just had another "seizure" - touchscreen would not respond AT ALL for several minutes. No matter what or how I tap - complete ignore.
After couple of minutes it started working again.
Interesting that S2U2 worked fine. Seems that windows just chooses to ignore touchscreen input.
I'm forced to return to WM6.0 ROM...
Please, anybody look into this.. phone is becoming to be unusable - I can't even enter a phone number.
DarkDvr said:
Do you have the same problem?
Click to expand...
Click to collapse
Yeah it's really bad here. I've tried all sorts of tricks, including:
Re-install 6.1
Re-install 6.1 with the recent radio update found on the e-club
Install SPL 3.56
Disable HTC today screen
Kaisertweaks - tweaks on and off
Disable radio completely (seems to help, but makes the device useless)
Disable activesync
Disable quickgps
For now, I've done 2 things that seems to help:
- Disable the HTC task manager - improves the responsiveness
- Kill the MSTLI.EXE process - improves on the number of freezes
But I still experience freezes, and it's really getting to me. I need a responsive device, not this c****
ASCIIker said:
i upgraded to official 6.1 about two weeks ago...
i recently started having the "missed taps" problem...
i have a feeling that KaiserTweak has something to do with the issue...if memory serves, i don't remember experiencing the issue BEFORE i played with the "TouchFLO->Sensitivity" and "TouchFLO->Finger Pressure" options...i just launched KaiserTweak right now and its showing those values as set to defaults where as i could've sworn i changed them to the advised settings a day or two ago approximately when i started experiencing the issue...just a point to clarify, i was only playing around for no particular reason and my taps were not problematic before
i've just changed them to the advised settings and did a soft reset to see if these are the kind of settings that are forgotten after a soft reset...but they stuck...so i'm gonna observe this for a couple of days with the advised settings effective and see if they have reverted to defaults on first sight of the issue...i'll report back here if that happens because that would be a pretty strong correlation...almost enough to prove cause and effect
Click to expand...
Click to collapse
My device is currently without kaisertweaks, and I still have the freezing issues.
DarkDvr said:
Well, problem is, last time I've used KaiserTweak was like a year ago, so my touchscreen problems cannot be linked to KaiserTweak. I don't even have it on my tilt.
Also, it's definitelly not a touchscreen itself, since this problem is application-dependent. Once again, S2U2 and Opera are immune to this problem. Windows' build-in apps (file explorer, bottom bar, etc) all suffer from it.
Click to expand...
Click to collapse
I concur, it is application specific. I tried to run the "Task manager" from Fdcsoft to see if it was related to a process eating up all the CPU. But the problem doesn't occur while the application is focused.
DarkDvr said:
Never really caled for it, I use my hardware buttons (D-pad) to scroll, I find TouchFLO to be too unreliable... maybe it's just me, but nothing beats a hardware button which you actually "PUSH".
Click to expand...
Click to collapse
TouchFlo is way too unreliable to me too.
DarkDvr said:
True, if I keep pushing on the screen button, in about 5 seconds it will be clicked. But that's ridiculous, i gotta say.
I use PocketMechanic - good stuff. Has lots of useful functions, including notification queue cleanup and analysis.
Click to expand...
Click to collapse
Oh wow, not a LONG PRESS, literally a 'touch' vs a 'tap'. What you describe would be seriously annoying.
Thanks for the suggestion, I'll look at it
I can't get the phone outta sleep mode (I think it is sleep mode), where the screen goes black while being carried, about 50% I can tap the power button and it awakes, all is fine. BUT the half I gotta remove the battery or sim and then press power on button.
Any ideas?
Also how can we run an AV on the phone, my comp don't see it as a drive....
Thanks!
SJ
sleep settings are off.........any ideas?
sleepyjim said:
I can't get the phone outta sleep mode (I think it is sleep mode),
Click to expand...
Click to collapse
Please provide full details of which phone, which ROM/Radio/SPL other software installed etc as these things may help others to recognise what you're experiencing otherwise it's a bit like saying why won't my car start with no other details provided.... so some more detail will help.
When I was running the latest UK HTC WWE WM 6.1 ROM on my HTC Branded TyTN II I sometimes found it took longer than usual to come out of sleep so thinking I'd not pushed the button hard enough, I pushed it again - only to find the screen would briefly flash as it came out of powersaving mode and then it went black again as it went back in - could this be whats happening and how long are you waiting after pushing the button?
Sorry, I got an HTC TyTNII. ROM 1.81.415.4wwe, ROM Date 10/29/2007, Radio 1.27.15.32, Protocol 22.51.88.13H.
Most of the time the sleep mode ends easily, but if I leave the phone to charge it sometimes will give me the issues........
Jim
Funny, that happens to me quite often too. I have Dutty's WM6.1 WWE installed. Also I have the slide2unlock installed on it. The radio version is 1.58.25.17. Even when I don't have the phone on charge at times it does it. I have another AT&T Tilt that only has the Slide2Unlock on it the rest is factory, but sometimes I see that does it also.. Another thing I also experience is that sometimes it'll just restart by itself, but maybe that's to clear up memory or something?
aurfawce said:
Funny, that happens to me quite often too. I have Dutty's WM6.1 WWE installed. Also I have the slide2unlock installed on it. The radio version is 1.58.25.17. Even when I don't have the phone on charge at times it does it. I have another AT&T Tilt that only has the Slide2Unlock on it the rest is factory, but sometimes I see that does it also.. Another thing I also experience is that sometimes it'll just restart by itself, but maybe that's to clear up memory or something?
Click to expand...
Click to collapse
Search for 'Standby of death'. There is a while thread where people are discussing it. I htink mine may have been caused by some offending software, as I get it much less now once I have uninstalled it.
Thanks kevin!
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2where the resolution was to get a new SIM
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
nlel, please stop going to every "Standby of Death" thread and adding your answer to it. Adding it to one thread is enough, three or more is just overkill, especially when the threads you've been posting to have been dead for months. Thanks,
Dave
I recently falshed the new WM6.1 ROM from the HTC website. The only problem I can't seem to get around is when the phone is locked and put in sleep mode, a few seconds later the screen will flash white for a second. And then periodically blink white. Mainly I don't want to waist precious battery life. Its now driving me insane. I've looked and searched for hours on hours and can't find anything like this.
I've hard reset, soft rest. Got rid of the bloatware. But still got this blink.
Any help would be greatly appreciated!
Thanks in advance!
I've came across this several times with many 6.1 roms. I am not sure if a fix exists. However, this has never bothered me. I simply click the power button twice and the blinking stops. Hope this does the same for you.
All The Best.
Same thing happens to me. I will be watching to see what the response is. Bugs me too. No idea how many times that's happening while it's in my pocket or something - not good for battery life and can't be good for the screen either...
Empire101 said:
I've looked and searched for hours on hours and can't find anything like this.
I've hard reset, soft rest. Got rid of the bloatware. But still got this blink
Click to expand...
Click to collapse
As already mentioned several WM 6.1 ROMs suffers from screen flashes relating to power management issues. Using the latest HTC WWE WM 6.1 ROM the TyTN II will occasionally require two button presses to come out of power saving mode.
If you were happy/happier with the WM 6.0 ROM complain to your ROM provider and if necessary request it be reverted (or read up here and once you know whats required, do it yourself). I don't see any 'new' official ROMs coming for this device now it's comparitively elderly, so I think it'll be up to you to come up with a solution.
HTC has provided an HotFix for that issue at :
AT&T Tilt WM 6.1 Backlight HotFix
But Truely speaking, I installed and it didn't worked for me.
It might work for you, so just give a try.
Regards,
Thanks guys. I'll try the double push of the power button and see if it works, if not I live with it a little longer, till I go mad.
If I can't take it anymore I'll just re-flash to a different ROM.
Once again, thanks for the replies.
By the way the BACKLIGHT HotFix didn't work for me either. I think thats mainly to fix issues with the backlight timer always reverting back to 10 seconds, no matter what the user setting is.
Ever sense I had this X1 (My second one now) some times when its in stand by and I try just waking it up by pressing the power button one time nothing happens...
I try holding it down nothing happens wont shot off wont wake up wont even wake up if I plug-it in to the computer I just have to restart it.
It has done it on every single ROM so far I have tried and 2 different radios.
Some times if some one calls it will ring through but I have to answer it with the hard keys.
I am at a loss here any one have any ideas?
So no one has had this issue?
Could it be hardware?
Mine does that too :-(
Hi,
I've had that same problem for a month or so. Can't think what the problem is but I believe its only been happening since I changed my rom.
I'll let you know if I discover anything!
omg this started happening to me recently i keep pressing it loads of times before it comes on and i am on generic uk stock rom!
its messing up -could this be a hardware issue? because if so thats not good >.<
I have smiler issue but it only happens with a Leo roms, never had it with any other rom (stock or custom)
At least I dont feel alone on this =P
I have only tested WM 6.5 on this one so I guess it could be Leo roms causing this. Any maybe some one can pin down a fix for it =D
I've had this problem ever since I've had this dreaded phone. And it normally follows by 100 attempts of pressing the power button, and finally a response, only to see a process has crashed and terminated... i cant remember which process though.
I used to have this. It has to do with a process crashing, then no key inputs respond and you have to restart the device. I can't remember which process but i think it was services.exe or device.exe