Related
I know this is my first post here but I've done my best to search the forums and I haven't found anything that looks like it helps me.
I just got my AT&T Tilt yesterday. It came unlocked (I'm using it with T-Mobile) and has an HTC ROM installed as well as various other apps (Ms. Pacman, TomTom 6, SuperDoku, etc.). I had some issues with it locking up yesterday (similar to what I'm experiencing now but to a much, much lesser degree) when I was playing around with it but those issues somehow corrected themselves.
This morning I installed the Tilt keyboard fix that TaurusBullba posted on here back in June to fix some mapping issues. Since I installed and soft reseted, everything has been going kinda haywire. The Wi-Fi turned itself off and I can't turn it back on. When I slide out the keyboard the orientation stays in portrait mode. When I try to shut down the phone using the power button it hangs forever. Now, actually, half the time I press the power button nothing happens at all.
I've tried uninstalling the CAB but that didn't fix anything at all. I'm afraid to try a hard reset because, from my understanding, I'm going to lose everything that came pre-installed on my phone for me. I should probably also add that last night I installed the Google Maps CAB with no problems whatsoever. Is there some simple solution I'm overlooking? Thanks much!
I would advise that if you have tried soft resets to try and resolve the issues and it hasn't worked, then perhaps a hard reset?
It sounds as if the software you have installed as either caused the problems or exacberated them (ie made them worse).
With hard reset it wipes everything back to when you got it. If you are able I would suggest that you plug it into the computer and make sure ActiveSync backups up your contents. You may also want to use this get all the files on the main memory either to the storage card or to you're PC.
As this is yo're first post I don't know how au fait you are with the above that I have mentioned
The preloaded apps will be reloaded again. You won't have an empty ROM if you do a hard reset. It will be as if you just flashed the ROM again.
Thanks for the replies guys. I went ahead and did a hard reset and it looks like the only thing I lost (or at least the only thing I miss) was TomTom. I've already reinstalled that using a link I found on here, and everything seems to be good to go.
I still have no idea what might have caused the problems though, so I'm afraid that they might come back or I might repeat some dumb mistake I made. I guess I'll just have to live with that for now.
clear storage / hard resets no big deal, just expect to do it every other week while you're finding all the cabs that work (or dont work) for you..
I generally clear storaged every week when i first got my tilt until I found all the app's I liked that didn't have side effects
Have my att tilt for over a week now and i noticed I need to perform soft reset at least twice a day. I am not sure if that's normal but I think it's annoying since I rely on it for reminders. This morning I had to do a soft reset because it froze during the night. I am not sure if I want to use it as alarm clock.
I am using the Dutty's V4 RTM and Radio 1.27.12.11.
Is there something I can do or do i need to get used to it?
Other than that and the bluetooth not working with my infiniti g35, i love it.
No problems for me, never had to do an softreset because of freezing up. Only because of my battery problem.
I soft reset a couple of times a week - just for good measure (after running memmaid or something to assure good operations). Don't think I've ever "needed" to other than during flashing and installations. Using Dutty's V2 (medium), but moments from flashing Q-Mobile 1.2. I tend to avoid things like cubes and S2U and such (justified or not, I see them as unnecessary resource hogs), but am hardly minimalistic as far as installing programs.
Perhaps you'd be happier with a "liter" ROM? I'm still testing to find the one I want to stick with. That being said, I love the V2 medium - just looking to appease my inner flashing addict.
i love it when ppl use cooked ROMs and then complain about issues...No offense to anybody. I used cooked ROMs on the Hermes as well. Not on my TILT. I do not have to reset the Tilt, but when I do is because a third party program freezes.
And also remember, any program that you install, might cause issues, because crappy programming...It's not necessary the OS...
Using Qmobile 1.2 for about a week. Might have had to soft rest once or twice. Not too bad. I think mainly because of Navizon though...
I never really had to soft reset due to crashes, but i normally do softresets after configuring registries that require soft resets. Otherwise, its on 24/7!!
I soft reset when I find my phone getting a little sluggish. It's like a computer, I figure, and I restart my computer multiple times a week. Either way, I don't think there's any harm in soft resetting too much.
I find I have to soft reset fairly often. Probably every day. I am using stock ROM but have installed a bunch of stuff, so I am suspicious of that.
I do have a Cube installed, and am considering dropping it off. Not sure if that will help or not.
I find that there are a lot of posts about various quirks on Tilt. And I will say, "Gee, that doesn't happen to me", and of course next thing you know it does. Some of the stuff is just me still learing how I can get myself into trouble. For example today my sound quit and I couldn't hear music from WMP. But it turned out that the problem was that sometime I had hit that little speaker at the top which opend the volume control, and before getting it closed I had deactivated sound. So even with volume at 100%, no sound. Interesting...
Anyway, as some said, I suspect combination of installing stuff causes issues. The more you install the more likely it will be problematic. But then, for me anyway, one reason I have this unit is so I can put stuff on it to make it productive. But then, after all, it is a version of Windows, so after a while, probably need to reload from scratch (hard reset).
yea most likely its the stuff u put on the stock? o men do some upgade.
I do soft reset about once in 14 days. I usually do it when my available RAM approaches 40 MB. Don't remember it has ever crashed on me except for a few times when usiing opera mobile.
Actually I after using the TyTn II for 3 months now I am starting to believe that the instability issues we relate with windows mobile are becoming more of a myth than a reality
I guess I soft reset too often? I do it about 15 times a day. By choice, though.
mick2021 said:
Have my att tilt for over a week now and i noticed I need to perform soft reset at least twice a day. I am not sure if that's normal but I think it's annoying since I rely on it for reminders. This morning I had to do a soft reset because it froze during the night. I am not sure if I want to use it as alarm clock.
I am using the Dutty's V4 RTM and Radio 1.27.12.11.
Is there something I can do or do i need to get used to it?
Other than that and the bluetooth not working with my infiniti g35, i love it.
Click to expand...
Click to collapse
just hard reset, it may help
I normally do a soft reset every morning when I disconnect my Tilt from the computer, since Active Sync kicks in every so often during the night and drains the RAM by running. . . but it's still between 50 - 55MB, even at that. Other than that, the only time I've had to soft reset is when an app would freeze up -- which isn't very often.
most of the times i soft reset is after installing a program or vice versa when it tells me it needs to do so...rarely will i have to do it cuz it froze or whatnot
I'm in exactly the same boat as bapssystupr3m3, I only soft reset it when an installed application tells me i need to do so.
Other than that, I frequently make sure I close all the apps that are just running in the background and my kaiser appears fine.
Only soft resets when schedule back up comes up daily. Other than the scheduled backup, no resets (so far *knock on wood*).
what's wrong with resetting the phone? It doesn't hurt..
I'm using the stock HTC rom, and can only remember one time when something locked up on me (a third party app) and I ended up soft-resetting, the only other times I've done it have been after installing/configuring new things. I guess in the normal course of things I maybe reset... once a week? Sometimes more, but never for any negative reason.
I'd say the uptime on this device is at least as good as my last Symbian-based phone, and the myth of Windows Mobile being unstable is just that - a myth.
I'm using the stock Tilt rom with just a few things installed and have to reset most days. Yesterday when I woke up I discovered my phone had crashed at 11:30 the previous evening when someone had called me. Today when I woke up an hour late I reset the phone because my alarms hadn't worked nor were the notifications for messages...
I soft-reset once everyday (in the morning). It's part of my daily routine now. I use ClearTemp program to clear everything (start menu, cache, etc.) and then soft-reset using that program as well.
Hi,
Had my Diamond about a month now, flashed a few Roms and have stuck with whats in my signiture.
The problem i have is that occasionaly it decides to do a soft reset while it is in the middle of being used! i have Hard SPL 1.40 Dev edition. It does it no matter which ROM i'm using.
any ideas?
Cheers,
no one????
***BUMP***
Well I had a glitch here or there, but sorted all that now.
If you keep getting soft resets with the original firmware then suggest RMA.
RMA...?
i have flashed different ROMs/SPLs and always had the same problem.
Do you have any processes loaded at startup that can be responsible for this? Or perhaps a tweak you always use?
no i dont ever do the same thing, all i do is flash a ROM, have contacts from Sim card.... never back anything up lol
In about 5 weeks of use (stock ROM) the phone did reset once or twice, but that's about it.
If yours is doing that often, then perhaps it has a hardware problem, considering that it happens with different ROMs.
yeh, returning to stock ROM/SPL etc now to return to HTC....
And then they have a look at it, don't see a soft-reset occuring, flash the phone and return it to you... If the failure is hard to reproduce don't send it back. You will get your phone back after three weeks and nothing happened.
Soft resets looks more like a software problem, not a hardware.
I got my diamond yesterday and didnt flash a new rom. Still stuck with the old one, but it also has done some softresets randomly. I didnt even install any apps. Any ideas?
Suddenly my Sprint HTC Touch Diamond is running extremely slow. TouchFlo 3D will not start. Various things runs extremely slowly like tapping on the start menu takes like 20-30 seconds to come up.
Rebooted several times. Turned off TouchFlo. Phone's still as slow as molasses?
What to do? Flash the ROM? If so, which I'd hate to do, where do I get the original Sprint based ROM?
Update: For some reason \Windows\manilla.exe never gets run. If I run it by hand then Touch Flo comes up. But it's still kinda slow.
Who/What starts manilla.exe?
Simply do a hard reset, this will reset everything back to original rom as in a factory reset.
http://www.hardreset.eu/htc_touch_diamond_hard_reset_soft_reset_en.html
That would be wonderful if I didn't customize things. But I have - heavily. And I'll need to reinstall all my apps. I was hoping not to do that...
defaria said:
That would be wonderful if I didn't customize things. But I have - heavily. And I'll need to reinstall all my apps. I was hoping not to do that...
Click to expand...
Click to collapse
But this is the most likely reason it is running slowly... Needs a hard reset and start again - and be judicious with what you re-install.
Before doing a hard reset, have you tried a soft reset??
A soft reset for heavy users is almost required dally in some cases to release the memory from being attached to programs and the OS which is consider to be called "Memory Leaks." A typical problem for all 6.1 Roms.
This slow and sometimes unresponsive behaviour was what also experience as well. There are programs that help memory find it's home but sometimes a good old fashion soft reset is what's needed.
Last thing: Make sure that when you have flashed a new ROM to ALWAYS do a HARD RESET immediately. Not sure if you followed that procedure in your last flash. IF not, I'm afraid a soft reset might not be sufficient to remedy this issue for you.
Riker88 said:
But this is the most likely reason it is running slowly... Needs a hard reset and start again - and be judicious with what you re-install.
Click to expand...
Click to collapse
This is exactly what I was trying to avoid. A computer doesn't suddenly go from running OK to dog slow when you have not changed anything (I only rebooted/soft reset). The running of manilla.exe doesn't suddenly disappear.
Everything I install I install for a reason.
band27 said:
Before doing a hard reset, have you tried a soft reset??
Click to expand...
Click to collapse
Daily! If not hourly. WinMo is not known for being stable.
A soft reset for heavy users is almost required dally in some cases to release the memory from being attached to programs and the OS which is consider to be called "Memory Leaks." A typical problem for all 6.1 Roms.
Click to expand...
Click to collapse
I'm well versed in what memory leaks are. 'Round here we call them bugs. Being in the business for some 30 years now I can tell you that having to reboot an OS periodically is a sign of an extremely buggy OS. Unfortunately that's what WinMo is.
This slow and sometimes unresponsive behaviour was what also experience as well. There are programs that help memory find it's home but sometimes a good old fashion soft reset is what's needed.
Click to expand...
Click to collapse
There's a big difference between being slow and being suddenly SLOOOOOOOOOWWWWW.
Last thing: Make sure that when you have flashed a new ROM to ALWAYS do a HARD RESET immediately. Not sure if you followed that procedure in your last flash. IF not, I'm afraid a soft reset might not be sufficient to remedy this issue for you.
Click to expand...
Click to collapse
I've yet to flash this phone. I was hoping to avoid it. There are so many ROMs to choose from, some better than others. And I'm not looking forward to having to reapply all my customizations...
i get a problem like this occasionally after a restart. I need to hit the green dial key to get it to ask my PIN. after i enter my pin everything is back to normal.
just an idea
sprite backup
What you should do is when you hard-reset the phone and you have installed all your must-have apps (and the phone still runs smoothly) use Sprite Backup to make an image. This way when things go bad again, just restore the Sprite image to that wonderful time when everything still worked smoothly and you won't have to install all the apps again. Only the apps you installed after the image ofcourse... depends how often you backup
Works like a charm.
Be careful though, when you flash another rom, you CAN'T use the Sprite image anymore!! You have to make a new image then.
Hope this helps.
** 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)