Hey there,
A bit new, just finished loading Duttys WM6.1.5.2.1972_Hybrid_V2_1_65.14.06[CubeV2] Rom. Seems great at first. Had to download Goodlink for the corporate stuff. It works fine for a bit, but as soon as an Outlook reminder pops up, suddenly the touch screen is completely dead. Tried all buttons etc on the front. The keyboard works and the buttons can be used as the menu choices, but it took a hard reset to fix it. Which then I had to reload Goodlink and it happened again.
Any patches or settings anyone can think of? Goodllink is the only add in I put in. Any other ROM's recommended perhaps? Thanks all!
Borg7of9 said:
Hey there,
A bit new, just finished loading Duttys WM6.1.5.2.1972_Hybrid_V2_1_65.14.06[CubeV2] Rom. Seems great at first. Had to download Goodlink for the corporate stuff. It works fine for a bit, but as soon as an Outlook reminder pops up, suddenly the touch screen is completely dead. Tried all buttons etc on the front. The keyboard works and the buttons can be used as the menu choices, but it took a hard reset to fix it. Which then I had to reload Goodlink and it happened again.
Any patches or settings anyone can think of? Goodllink is the only add in I put in. Any other ROM's recommended perhaps? Thanks all!
Click to expand...
Click to collapse
I notice this is your fisrt post so welcome. There is a great deal of helpful experience here to help but it does certainly pay to pose questions in the correct place. If you ever have a question about a ROM then post your question in that area and you will be far more likely to get the helpful anser that you want. People are also sometimes too quick to 'Flame' people making such errors - but not me so hopefully this will help:
I am on that same ROM and have noticed that after initial ROM installation that the touch screen is initially 'prone' to what appear to be freezes. In fact I noticed on my device that I had to press quite hard to get any interaction with the screen and sometimes it did not respond.
Cannot say why but this has now completely gone and did so with each ROM install. It took a few soft resets to see the screen working correctly but it is great now! So it may not be your additional software. Just try sticking with it for longer and some soft resets. You might also try tweaking the sensitivity of the screen.
Suggest you search within the correct area and you'll see few comments about this kind of thing (but not many).
Regards
Thanks Tony. My first time posting so wasnt sure where to put it. Have done all you suggested. Worse case, back to the ATT rom, oh well. Will search also and try posting in the right location. Thanks!
Borg7of9 said:
Thanks Tony. My first time posting so wasnt sure where to put it. Have done all you suggested. Worse case, back to the ATT rom, oh well. Will search also and try posting in the right location. Thanks!
Click to expand...
Click to collapse
i just reviewed the software online and i can make several predictions why this is conflicting with the rom. 1) htc home
go to settings>personal>today>items>and uncheck htc home.
let me know if goodlink works thereafter if not I have a few more predictions to why it doesn't operate correctly.
Oh, and i just noticed you had a cube version, which could also be conflicting.
Thanks for the input Red. Tried that to no avail. Even tried soft reset afterwards. It is dead before goodlink even starts. BTW, this will be worth a Pint or two if you get me working.
I thought it might be the Cube version so after several hard resets(storage clearing), I went ahead and flashed it with Dutty's Non Cube version just to see if that was it and it wasn't. I tried tuning the touch screen too, bumping sensitivity up to 200, didnt help either. Tried loading the tweaks program, but nothing there either helped(actually cant even use it when frozen). The keypad, buttons all work, but the touch screen is dead. Hard reset fixes it, loading Goodlink, which I have to have for its a corp phone, kills the touch screen. I believe it worked for a few minutes, then locked up. I need to reverify that just to make sure it didnt happen immediately with Goodlink install. Very strange.
I have searched and found some thread's about this sort of this but not exactly the same problem. I am using GARMIN'S FINAL ROM which I must say it awesome. Stable and the fastest I have seen yet but I am still have one problem, at certain point's my phone doesn't respond to touch, clicking of the front key's and even sometime I have to press button's on the keyboard 3 or 4 time's just to get it to type. I thought it could just be lag but even when I give the phone a few second's to do it's thing (load fully) it doesn't work properly? I mean even sometime's when I press the end key the friggin button's don't even light up.
I hope there is some help because I just got the Tilt and it seem's like a great phone but this is just getting to be stupid.
Thank's ahead of time.
i have the same issue with hyper dragon rom. and no, im not running any programs, memory usage is 48% (running nothing) however the screen wont respond to touchs, the keyboard wont respond etc but the cursor still blinks, animations still play etc.
ive already tried all of the "keyboard" fix's, adjusted the settings manually etc yes i calibrated the screen multiple times *waits for somebody to reflash even though i did that *
I was having that problem and I found the only way to workaround it was to re-align The screen in the Start>Settings>System>Screen menu. But, I have not had it since installing SJ's 15 November 08] HyperDragon III Raphael version here
http://forum.xda-developers.com/showthread.php?t=397121
I strongly recommend it. All you need to do is remember to install Opera 9 last per Notes at the top of the post.
Hope that helps.
I am going to try that out, it look's cool but it look's like there is way to much stuff for it to run fast? Also if I don't use Opera I don't need to install it correct?
bump! Any other idea's?
I have the same problem but mostly notice it when the phone comes out of sleep. The phone will work right then slow to a stop and not allow any input via the screen or keys. 10 seconds later it's good to go.
Edit
OK the fix I can confirm that woks is that you have to sim unlock your phone with the newer 6.1 roms. I did it and it completely fixed my lag problem. Use the kaiser unlocker to do it and it can be found with a simple search. Make sure you have a the right SPL and newer radio to make sure everything is compatible.
This is one big PITA with the crappy ATT ROM image. I have to press the power button twice to get the phone out of sleep mode. Once just isn't enough for the wonderfully tested ATT image. This never happened with the 6.0 image, or with any of the cooked images.
So what is the fix? I've seen several threads complaining about this, but none offer a fix. I do not want to flash another non-std "cooked" image, but registry or DLL replacements are OK by me.
here - http://tinyurl.com/d8wfg9
bwnotredame06 said:
here - http://tinyurl.com/d8wfg9
Click to expand...
Click to collapse
If you don't know then there's no need to post.
Potential fix
ButtonBoy said:
This never happened with the 6.0 image, or with any of the cooked images.
So what is the fix? I've seen several threads complaining about this, but none offer a fix. I do not want to flash another non-std "cooked" image
Click to expand...
Click to collapse
So a cooked ROM is out and I suspect a reg entry won't cover something like this (just a hunch, no proof) but you haven't ruled out going back to WM 6.0 (which never had the problem) - you have a potential fix. The screen flashes coming out of powersaving mode were just one of many reasons why I reverted my TyTN II back to WM 6.0. Although that OS also has a few bugs, they're far less of a PITA than WM 6.1s so I haven't looked back
This is a common problem with the majority of the later 6.1 builds, and depending on who you talk to, it is either a great feature ,built in to 6.1 to keep the phone from accidently turning on in your pocket and draining your battery and scrambling your settings and calling people by accident. ......Or it is a really annoying feature that makes you press twice or one long press to get your phone out of sleep. Shall I put 1 vote in the annoying column for you ?
There is no fix. Two quick presses or one long press ? How annoying is it really ? Two quick presses is about as long as it takes to slide to unlock.
I had no such issues with any HyperDragon release. They all had the correct behavior, and none of the "fit-full sleep" issues either. Oh well. Soon enough I will migrate to a better device, and this time I won't tolerate any of ATT's brilliant engineering.
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)