Related
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
Since upgrading to the AT&T 6.1 ROM I have 2 recurring issues. First, the device seems to have "busy" times when it will not respond to screen taps. If I turn off the phone radio the problem goes away. Second, the on/off/sleep button on the side will occasionaly turn on the phone from sleep for less than the second. The screen flashes and then back off. The next press of the button will turn the phone on.
I have seen these problems posted on other forums but not here and have not seen any solutions posted. Has anyone else seen these problems and are there any fixes?
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
The power button issue seems to be related to WM 6.1 (it's been present in every 6.1 ROM I've used). I've read several comments about it in several different threads. NotATreoFan (NATF) posted a 'workaround' in his ROM thread which has worked perfectly for me. Simply hold the power button for a very short time instead of just pushing it - .5 second works fine.
The power button issue has been revealed as a "feature" AT&T added to their 6.1 ROM. It is intended to prevent accidental powering on when the phone is in your pocket.
NotATreoFan said:
The power button issue has been revealed as a "feature" AT&T added to their 6.1 ROM. It is intended to prevent accidental powering on when the phone is in your pocket.
Click to expand...
Click to collapse
Some "Feature"
Kuschelweich said:
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
Click to expand...
Click to collapse
I had the previous stock ROM installed and whatever SPL version that was. The power switch is an interesting feature, I guess now that I know it, it makes sense. The Tilt power switch is so hard to press that it seems unnecessary.
Has anyone else experienced the lag. It is very noticable when I am playing a game like solitaire. The phone will work fine for 2 or 3 minutes then be unresponsive for 10 or 15 seconds and then be good again. I haven't installed any 3rd party apps yet, just run them from my SD card.
I gave up on the official ROM, and had to be selective on which ones to load up. My favorites were the basic naked ROMs (NATF-it will be missed, yes yes, go Phillies-That old dude sounded like a rock star, and AthineOS). Added applications (not all at once) to be able to see what programs would mess up the speed or even the sound (found out that a certain version of SRSWOW would render the volume control and anything having to do with sound as useless). Ended up with what I think is a completely functioning, lag free WinMo phone. Yes, it took a little while, but worth the effort. So far have over 35 different programs/customizations along with Igo8 and Manilla 2D (w/o Youtube or GoogleMaps) working together beautifully. To save me the trouble of having to load cabs one by one I installed SASHIMI to my storage card and, voila! Almost automated reloading of all cabs...
I've experienced the lag across some new cooked roms I've been trying. I'll have to go back and figure out the SPL situation to see if that fixes it. The lag is super annoying though.
Kuschelweich said:
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
Click to expand...
Click to collapse
Yup that was exactly my problem. I still had V1, what a huge difference, no more lag. Thank you!
TracyD follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=433835
Lev00 said:
Yup that was exactly my problem. I still had V1, what a huge difference, no more lag. Thank you!
TracyD follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=433835
Click to expand...
Click to collapse
I ran through the tutorial and updated the SPL but that did not fix the lag. I ran the unlocker and that seemed to do the trick. No more lag. I had already determined that I could stop the lag by putting the phone in flight mode. There must be a problem with the stock ATT Radio.
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.
Hi Guys,
I suppose one good thing to come out of me constantly finding my HD dead after it being on standby for a few hours (it seems intermittent) is that it seems many others are having similar issues.
Can people post their findings to the following question so we can help the community at large narrow down the issue:
When your device hangs/freezes, is it in standby or in use?
If the unit is in Standby, are you using Manila 2.5 or an earlier version?
Which WM version are you using? (6.1 of 6.5)
Have you unticked the "Today timeout" on the Today Settings screen?
My experiences are as follows:
I have only seen this since I have been using a 6.5 ROM
I have only seen this since I have been using Manila 2.5 (i think)
I install only a small number of applications
I have used both MyPhone and PIM Backup to restore info
oh and finally, it's bloody annoying!!!
If anyone has any information as to what could be causing this please post. I'm sure we'd all give our left nut to get this fixed?
This does seem to be an issue that effects some and not others, I had it happen a few times but after flashing back to an official ROM then back to custom (including SPL) I have using custom ROMs for a while now without this occuring again.
Flashmore, thanks for your input. Can you state what steps you followed for others?
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
xboxhalo said:
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
Click to expand...
Click to collapse
I'm attempting to systematically find out what the problem is by installing the same programs each flash with the exception of one. The first attempt was to move back to Manila 2.1 - so far so good but I'm expecting the same to happen at some point.
I want a good ROM, but I'm more bothered about not missing an emergency phone call because my phone is dead!
Hi all.
I'm not sure if this is actually related since when I experienced these so called "lock ups" my phone hard reset and corrupted the SD card as well. This happened two times with HD and once with Diamond2. Both phones with WM6.5.
I'm using corporate exchange and get enforced a device lock policy. I noticed that each time the device froze it was displaying the "classic" device lock number keyboard although the "default" (the new wm6.5) lock was selected.
Anyway, both phones have been working perfectly with WM6.5 and manilla 2.5 after I have started to use the ugly "classic" lock screen.
E
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
gallegus said:
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
Click to expand...
Click to collapse
That's interesting. I might try that.
I have been on Manila 2.1 for a few days and so far so good though.
I'm on WM 6.5 w/ Manila 2.1 for a couple of days and it has happened to me too.
I just tried disabling the options for turning off backlight and turning off phone. Hopefully this "fixes" the problem.
Check this thread, same subject, more details !
K
As said by Kostas66 above me. I guess this thread will soon get a lock...
As per post#10 & 11, please use this thread for future posts
Thread closed
** Please check post #2 first. It looks like we have found a solution. **
We don't reprimand anyone for asking questions, so feel free to ask (preferably after reading or searching the thread) if you have doubts.
I'm starting this thread in the hope that we can determine and find a cure for the lockup issue some of us have been dealing with in the later Manila 2.5 version ROMs.
This is something I've been trying to deal with for some time now and it seems more widespread than people realize from the number of posts by users who have had this issue.
Let me explain my definition of "lockup":
1- It always happens when the device is in sleep mode, never while it's used.
2- Never happens with stock ROM or Manila 2.1, only on Manila 2.5.
3- It's random, could happen any time of the day, in any frequency.
4- It's more likely to happen with some ROMs than others, leading me to believe it is related to the ingredients used in the kitchen (that is: operating system/software ) The "lockups" will start within the first 24 hours and possibly become more frequent over time.
5- It's highly unlikely that any sw installation is responsible for this (NeoS2007_Driverpack_3 excluded, I haven't done sufficient testing with it)
6- When the "lockup" occurs, the screen lights up (you can see it does in the dark) but the device is unresponsive. If you wait for a while, the home screen appears but the device is unresponsive. The only way out is taking the battery out or doing a soft reset.
7- Using MTTY or flashing a stock ROM may help fix other problems but does not help for this specific case, the "lockup" will still occur.
8- It's entirely possible (but hard to determine) that hardware may be an issue here. The fact that some people always have this problem and others don't, may be due to different hardware revisions, if there are any.
9- This problem is very specific and never leads to a hard reset.
10- When the lockup has occurred, people calling may hear the phone ringing but the HD remains unresponsive and there is no call logged, so at least the radio section is working.
Please post you experience with this issue, including the ROM involved, and any action you have taken that leads to a solution.
Please also mention whether you flash using SD card or from the PC. Since none of my SD cards work, I always have to flash using my PC, so that is something I need more info on.
Please read this post to be uptodate on the latest situation with this issue
Quite a number of new sys versions seem to be causing lockups on most HDs. This is a sys problem and is not related to the lockup with the video drivers but is related to the OS version. If you are using a ROM with a new sys version and are having lockups, just switch to another ROM with a different sys version.
As the number of pages in the thread started to increase, I want to post a summary of our findings here.
As stated numerous times, not everyone suffers from this problem but the number of people who do suffer seems to be much more than I originally thought.
Please remember that we are talking about a very specific kind of lockup here as explained in post #1.
So far, our findings indicate that it is a combination of conditions that cause this issue. If Manila 2.5 and the Neo's Driver pack are used together, this lockup will occur on those HDs that are prone to this issue.
mnet has prepared a cab that effectively deletes the driver pack and restores stock drivers. If you are having this problem on a Manila 2.5 ROM, you should try this. Needless to say, before trying this, you should have already tried the recommended cures, like flashing a stock ROM or using MTTY.
You can't actually delete the files cooked in the ROM, only replace them...Some dlls from Neos drivers remain in the windows folder, however they are no longer used due to registry modifications.
Several users who have been suffering from this lockup have confirmed that after applying mnet's cab to uninstall the Neo's Driver Pack, the lockups have stopped. So, it's a definite cure.
Cab to remove Neo's Driver Pack.
Also, please check this post. It may be worth giving it a try if you have unexplained lockups.
The Topaz D3DM drivers also seem to be causing lockups, confirmed by other users.
Mikenificent BlackStone TestDrivers seem to be safe. I tested for a few days and no lockups occurred.
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?
Fallen Spartan said:
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.
I only had this with Dutty and Miri's 21xxx series with Manila 2.5.
Once I went to 28xxx series, from PDAViet, Energy etc, this hasn't happend again.
So I'm guessing its WM6.5 21xxx and 23xxx related rather then manila.
Also, it happens far less when you use a lightweight (short and low bitrate) sound for notification.
It seemed to happen for me whenever the "new mail" or "new sms" notification was supposed to sound.
When putting a very short sound, it stopped freezing. When putting back a long sound, it would freeze up more often.
bobsbbq said:
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.
Click to expand...
Click to collapse
A number of people have stated that they get issues with cooked roms (while others don't) if they are constant flashers, and the common solution would be to flash a shipped rom and then back to cooked. As I stated above I've been fortunate enough not to experience this so haven't had the need to flash a shipped rom. But from reading users issues this isn't a clear cut problem as it doesn't affect everyone
homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
I've ruled that out. I always install the same set of applications, same email etc.
Never have this issue on stock ROM or Manila 2.1 ROM, only on later M2.5 ROMs, so it has to be related to M2.5 somehow.
Xannytech has been very helpful, comparing ROMs where I had this issue with a few ROMs where I don't have it, it seems that the problematic ROMs are larger in size. So perhaps there is a problem with the NAND memory and the bigger size ROMs use it whereas the smaller size ROMs do not use it. This is the reason why I mentioned hw revision as a possible cause.
Fallen Spartan said:
Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
It does happen on a bare ROM, no data sync, no SD card, no applications installed. Just flash a new ROM and wait, it will happen.
I guess it would be OK to mention here that currently the only ROMs where I don't have this issue is with Miri's ROMs (which are smaller in size than others).
wow.. luckily i came through this topic before i sent my HD for repairs.. and i thought it was the touch screen that has malfunctioned..
u are right, it only happens when the device wakes up from sleep.. if ur lucky, u could press half the screen and re-calibrate the screen.. if ur not, then hard reset is the only way for u to re-calibrate ur screen..
currently using;
GridLeo 1.7 (1.2.5.30),
OS (5.2.21869)
Manila 2.5.19201130.0,
Radio (1.14.25.24)
termignoni said:
wow.. luckily i came through this topic before i sent my HD for repairs.. and i thought it was the touch screen that has malfunctioned..
u are right, it only happens when the device wakes up from sleep.. if ur lucky, u could press half the screen and re-calibrate the screen.. if ur not, then hard reset is the only way for u to re-calibrate ur screen..
Click to expand...
Click to collapse
This doesn't appear to be the same issue. If you take the battery out and restart your HD, things should get back to normal - for a while. This never leads to a hard reset.
For your case, I suggest you flash a stock ROM and test with it for a while.
makbil said:
This doesn't appear to be the same issue. If you take the battery out and restart your HD, things should get back to normal - for a while. This never leads to a hard reset.
For your case, I suggest you flash a stock ROM and test with it for a while.
Click to expand...
Click to collapse
As you say, removing the battery or soft reset resolves the issue, but not for long before it happens again (unresponsive screen after sleep, but backlight lights up when i tap the screen)..
this is what is going on with my HD.. until one day, even after soft reset, i could not enter my pin or even access the calibration screen as i could only "tap" the top half of the screen..
after many soft resets, i could only "tap" the top half.. hard reset resolved my problem until a couple of days back, where the problem seems to start again.. this has been going on since last month, and out of the blue..
termignoni said:
As you say, removing the battery or soft reset resolves the issue, but not for long before it happens again (unresponsive screen after sleep, but backlight lights up when i tap the screen)..
Click to expand...
Click to collapse
I never got as far as having to do a hard reset but I guess it is possible after extended use.
I recommend you flash a stock ROM, use it for a while. When you are sure you don't get the lockups any more, flash your favorite custom ROM again. This should prove that the culprit is ROM related and not a hw problem with your HD.
makbil said:
I never got as far as having to do a hard reset but I guess it is possible after extended use.
I recommend you flash a stock ROM, use it for a while. When you are sure you don't get the lockups any more, flash your favorite custom ROM again. This should prove that the culprit is ROM related and not a hw problem with your HD.
Click to expand...
Click to collapse
i suspect it's a ROM issue as well, as i never had this issue with any other ROMs with the old Manila.. i'm gonna flash to the stock ROM tonite and see how things go.. but even so, i might take more than a week before it's showing signs of mis-calibration..
termignoni said:
i'm gonna flash to the stock ROM tonite and see how things go.. but even so, i might take more than a week before it's showing signs of mis-calibration..
Click to expand...
Click to collapse
If you do have this problem on a stock ROM, then definitely it's a different problem. Just remember to flash the stock ROM by running the executable and not through running the BlackstoneRUUWrapper + nbh file manually.
I've had this problem for the past couple of months whatever Rom i use and whatever software i install.However, I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
http://forum.xda-developers.com/showthread.php?t=540290
bodgeman said:
I've had this problem for the past couple of months whatever Rom i use and whatever software i install.However, I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
Click to expand...
Click to collapse
any reference to this "MTTY thing" u did? i might give a try 1st..
bodgeman said:
I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
Click to expand...
Click to collapse
I also did the MTTY thing but had the lockup within 24 hours on Xanny's Evo 1.6. Keep a close eye on this, if you don't have it within a few days your problem may have been cured
Didi you flash from SD card or from the PC?
termignoni said:
any reference to this "MTTY thing" u did? i might give a try 1st..
Click to expand...
Click to collapse
Here . My results are on page 50.
makbil said:
Here . My results are on page 50.
Click to expand...
Click to collapse
thank you..
btw, this time i flashed using PC instead of the SD card..
one more thing to add, the first time i did my hard reset, i restored my device using PIMBackup (restored everything).. within 24hrs, it happened again..
the 2nd hard reset, i restored only my Contacts and till now (after 3weeks), only it's starting to happen again..
i don't know bout u, but this is how it's happening to me..
- at first, u'll notice a slight mis-calibration while typing an sms or selecting something (after screen calibration, everything went fine)
- then, after a few days, same thing happens (can't tap the bottom part, soft reset and screen calibration solved this)
- and today, after my device woke up on sms, i could not unlock (using the default WM6.5 lock screen - had to soft reset twice, then calibrate screen)