Okay. I have had this same problem at least once on three different devs' WM roms. It happened first with VJ's WM6 3.2, then again on 3.4, then again on 3.7. Then it happened once with Nitro's WM6. Now, just last night, it happened again on GnatGoSplat's WM6.1s.
I have no idea what causes it. I can't replicate the problem. I just notice it after it happens.
I'll get to where I'm going and take my phone out of the holster, switch it from Vibrate to Normal, and set it down. Then I'll either receive a call or message, or else I'll pick up the phone to send one, and notice that it's still on Vibrate. Oops, must've forgotten to put it on Normal. So I switch it to Normal. It says "Normal" for about a second, but the Vibrate icon stays put, and then it switches from "Normal" to "Vibrate" by itself.
When this happens, I can't figure out how to get it back into Normal mode. Soft reset, hard reset, pull-the-battery. Nothing. The only thing I can do is re-flash the ROM.
But here's where it gets interesting. After all this happens, when I plug the phone into the computer via USB (WinXP), ActiveSync starts up, connects, and then pops up a dialog box that says ActiveSync cannot synchronize with the device. The AS window still shows it as being "Connected" but not "Synchronized". I can explore, copy, move, whatever. I can even reflash the OS. Which I do.
And then all is well.
Until it happens again.
Kicker: When it happened to Nitro's WM6, it was the same day Gnat released his 6.1, so I flashed that instead. And when he updated it and fixed a few things, I flashed that one. And I used it 24-7 without even a soft reset from the day it was released until approximately a week ago, when I installed moalesipufos' 6.1Pro RC4, just to test it out. It lasted all of an hour until I decided I just couldn't figure out the interface and wanted my GGS6.1s back. So I reflashed Gnat's ROM onto the phone.
A week later I get this.
So that was a long and (probably) boring description of my problem, but as it is so random and confusing, I wanted to make it as clear as possible in the hopes that someone, anyone, would read it and have some clue what the problem is - including whether it's user error or an ID=10T error.
So. Anything?
Thanks a ton!
Related
i'm using a htc wizard with the tnt 5.0 rom, it's been running amazingly fast and smooth, i love it but all of the sudden in the past week, i can't really figure out why but, i reset(soft) my phone once and it sat there forever on the wm6 splash, so i pulled the battery for a few seconds, and reinserted and turned it on, it came on fine, the clock/calender is set to some random time and random day/month of 2006, and if i set the clock to correct date/time/year the hourglass type thing shows up and stays there for a while, i press end and it goes away, but the phone runs super slow, so i soft reset and then it sits there, at wm6 splash and never finished booting up even after 20 minutes, so i pull battery, and repeat, minus chanigng the clock and if i leave the date/time to 2006, it works fine, does this make any sense to anyone? how can i fix this possibly ?
Please make your text readable....
Have you tried to reflash your phone?
it makes vague sense but you need to work on your grammar a little
Reflash your phone, make sure you followed all the steps. Thats all i can recommend until you put more info in a reply
I'm going to try re-flashing it, but as far as working on my grammar, I don't see how anyone would have any problems understanding what I typed. lol. Unless of course english isn't your first language ?
Maybe the problem is so abnormal there isn't much more info I can include to make any more sense. I described exactly what the problems were.
sintax said:
but as far as working on my grammar, I don't see how anyone would have any problems understanding what I typed. lol. Unless of course english isn't your first language ?
Click to expand...
Click to collapse
Surely you Jest. There wasn't a single Period (.) in your entire first post. Apparently you realized and corrected that error in your second post. But to claim that there was nothing wrong with it was wrong.
Flash with an official ROM, that should take care of the issue
yeah it happened to me once or twice. I just reset the date.
No grammar problems. Very understandable for one single, long run-on sentence. Really this isn't Language Arts. I had NO PROBLEM understanding you.
I'd do a HARD reset before I resorted to reflashing.
Maybe you should pay a SINTAX for your lack of SYNTAX hehe
I understood because I encountered the same problem. Except I encountered it because my phone was CPU-scaled at a time I didn't know how and I had a heavy start-up program running.
So far the only solution was that I reflash to official ROM, then back to cooked ROM. And now every time I reboot my device, I'm mindful of the 3rd boot loading time.
Therefore I just believe that you have to be mindful about the stuff that's on your phone and see what contributes to a slow or non-responsive boot time. Our phone's are computers, and therefore computer's never last.
I can't understand for the life of me why some of are flaming this guy for making a run on sentence... Last time I checked this wasn't 12th grade english class, it was a forum for a bunch of WM fanatatics to gather together and create great things.... I mean come on...
And to reply to the first post, I could understand you 100% for the record.
I think you need to hard-reset your phone. Just hold the comm manager and voice button while resetting with your stylus and press the send key when it prompts you to. Simple enough.
sintax said:
i'm using a htc wizard with the tnt 5.0 rom, it's been running amazingly fast and smooth, i love it but all of the sudden in the past week, i can't really figure out why but, i reset(soft) my phone once and it sat there forever on the wm6 splash, so i pulled the battery for a few seconds, and reinserted and turned it on, it came on fine, the clock/calender is set to some random time and random day/month of 2006, and if i set the clock to correct date/time/year the hourglass type thing shows up and stays there for a while, i press end and it goes away, but the phone runs super slow, so i soft reset and then it sits there, at wm6 splash and never finished booting up even after 20 minutes, so i pull battery, and repeat, minus chanigng the clock and if i leave the date/time to 2006, it works fine, does this make any sense to anyone? how can i fix this possibly ?
Click to expand...
Click to collapse
eject your storage card before resetting, and put it back after your device started up completely...this will not always help, but it did work for me
I flashed my phone 2 days ago from on spv e650 to wm 6.1 gonzo and yesterday it was working fine (battery life was brilliant even with bluetooth, wifi, and checking for emails over gprs) I charged it last night and this morning the phone told me it was "roaming" with a little triangle beside the gprs logo, i switched it off and back on again and now, every 5 minutes my phone vibrates, theres no alerts on the screen or anything, ive turned all comms off, taken the battery out and back in and stopped my email from refreshing. theres no sound with the vibrate and the phone is not on silent. its driving me crazy, help me
its the vibrating alert script i guess
try removing it from the startup folder.
You have missed a call, or unred SMS/email, or appointment...
Check this first.
On my phone that thing got stucked and would vibrate even if there was no event to vibrate for. I ended up formatting it, but if you know there are no missed calls or anything that you may have missed try to delete all the call logs, and then make a call to the phone and wait until it vibrates past 5 minutes, then view the call to make it stop, and reboot the phone. Maybe it works for you
If you can wait a few days I can cook you a custom ROM based on Dr. G's but without the Notification script and wm5torage wich you will need to install seperately if you use it.
Roland
Thanks guys, as i had only just installed the new rom i decided just to do a hard reset and it fixed it as i wasnt going to lose anything
You just need to remove the script "notify.mscr" from the startup and reboot. That will solve your problem. You don't need to hard reset or flash your phone to stop this.
i had the same thing tomorrow. just turn it off... go to the startmenu->all progs->System folder->Config notification->"disable script"
done!!!!!
Greetings!
As mentioined in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=418150&highlight=issue+list I have encountered similar problems.
I own my TP for 3 days (2 nights) and on both mornings after being charged over the night the TP was absolutely unresponsive and only to be awakened by a soft reset. It couldn't receive calls, and the alarm of course didn't work also (so I missed one this morning - but wasn't late at work) Anyway, this is a serious issue to me, since it makes the phone absolutely unreliable. And I am not in favor of doing regular hard resets by the way ...
Help on this would be really appreciated.
Greetings, hugo
Mine does this everyday, but have you tried pressing one of the buttons like the home button, I know nothing happens for a minute but then it comes back to life with out the need for a soft reset
Haven't tried ...
Well, I haven't tried pressing a button and waiting, but this is not exactly the behavior, to expect from a phone of this kind. You see this wouldn't solve the Problem of not being reachable by phone and missing appointments. In fact I don't know, that how long I was unreachable on phone and in my profession this isn't just disturbing but unacceptable.
Hugo
I've had the same problem, not every time it's charged, but enough times to be a problem. I've switched off TF3D (Start, Settings, Today, Items, untick TouchFLO 3D, tick some standard items).
The problem has gone. Of course, so has TouchFLO.
Cheers,
Graham.
graham.hughes said:
The problem has gone. Of course, so has TouchFLO.
Click to expand...
Click to collapse
This could be of course a last resort, but TouchFlo is quite nice to use (although I cannot get TF to use PocketInformant as calendar app, although it is defined as standard - the original MS calendar app must be hardcoded somwhere ...). And of course as TF is one of the main features of this phone a great amount of it's costs are caused by that software. So if I couldn't use it, the phone would loose a lot of it's value.
Isn't there a sort of event log in wm6.1 to see, which event crashes the system?
Hugo
I get a similar problem in that I lose all sound overnight, so I too miss my alarms. I also get no sound through the earpiece so, although it vibrates when it is supposed to be ringing, I cannot speak on the phone as I cannot hear the other person, and it seems they cannot hear me either, so it obviously affects the microphone as well. I have done a hard reset but it still happens, so it's definitely a bug with TF3D. I know this because if I try to play one of my music tracks using the music tab in TF3D, it plays for about 5-6 seconds (obviously with no sound) and then it crashes TF3D and restarts itself, which sorts the sound issue out. No need for a soft reset here but it's still unacceptable as my alarms are useless, and for £500+ I don't expect such a stupid flaw in the software. Hopefully, a ROM upgrade will sort this out, but when that will be is anyone's guess at the moment.
matmaneyre said:
...so it's definitely a bug with TF3D.
Click to expand...
Click to collapse
That's also my conclusion.
matmaneyre said:
Hopefully, a ROM upgrade will sort this out
Click to expand...
Click to collapse
I think that's what we have to wait for. Until then, it's a choice between bland-but-working or cute-but-unreliable.
have you tried any of these little mem resident babys to get your ram back and kill bad things while it sleeps
http://forum.xda-developers.com/showthread.php?p=2136914
Hmm...I'm just wondering why not more people are reporting this? Anyone NOT experiencing this problem?
Not till now I didn't
Using Stock ROM
I am more and more convicee, that TF3D is quite a buggy piece of software (Aussen hui - innen pfui!). Additionaly to the described above, I got a "broken glass" effect yesterday.
I sure do hope, that HTC releases a ROM update soon, although up until now the Touch Pro isn't even listed on HTC's german support pages.
Maybe I'll give SPB mobile shell a try ...
Hugo
Having same problem, not all the time though.
koppee1 said:
Hmm...I'm just wondering why not more people are reporting this? Anyone NOT experiencing this problem?
Click to expand...
Click to collapse
I have the same problem...
A few times already... even this morning.
TP is totally unresponsive and had to soft reset it to get it back alive.
ROM 1.90.401.1 WWE
Radio 1.02.25.19
Protocol 52.33.25.17U
I've had the HTC Touch Pro for about three weeks now, and since then it's crashed or become unusable at least once a day. I do not believe for one second that these issues are restricted to my handset, and comments on this forum back that up.
Problems I've experienced:
1. TouchFlo 3D screen corruption - "broken glass effect". The TouchFlo interface appears fragmented and split - it continues to function, but is unwatchable. The OS and other applications are unaffected. Cause unknown. Cured by soft reset.
2. Complete screen corruption + freeze. The entire screen gets a still image that looks like 'white noise' - random black and white pixels. The device is completely locked. Cause unknown. Cured by soft reset.
3. Device fails to wake up. Screen has been powered down, either having been switched off manually, or by timeout. Device later fails to respond to Power button. Happens occasionally without warning, and frequently (almost 100%) during overnight charge. Note - leaving the Touch Flo interface on 'Programs' tab (i.e. not 'Home') during charge seems to alleviate this (I don't yet have enough evidence to back up this claim).
I like this phone and its touch interface, but am pretty disgusted by the reliability issues, which I would guess are largely connected to the TouchFlo 3D code and/or hardware drivers. HTC really need to sort this out.
I've had the alarm fail on two mornings so far, needed soft reset.
I'm going to try disabling touchflo I think. Be nice to have pocketbreeze running again anyway.
Just out of curiousity
Do you have your phone set to turn off the screen even if it is charging? I don't have the Pro... yet, but with my 6700 I used to have to ensure the screen stayed on over night if I wanted to have a chance at the phone actually being responsive in the morning so the alarm would go off. Otherwise it would be as your Pro's seem to be doing. Will not turn on or anything until a soft reset. (It is not a fix by any means, I am just curious if it is still the same patern.)
I never charge over night simply to avoid it being charged for 8 hours straight. I keep a charge kit at work, and charge during the day as needed. In less than an hour, I get full battery. Then, I sit it next to my bed at night with no failed alarms.
Maybe it doesn't like the long charges.
I'm trying DCS's ROM now to see if it makes any difference at all. I'll report back in a couple of days. Maybe if I didn't have to charge it so often it wouldn't be so bad!
Wether screen is on or not, it doesn't make a difference. (Why should it on a working phone?)
I sincerely hope, that if those strange behaviours are gone in non stock cooked roms, that there will be some in German language as well ...
I am looking forward to another night!
By the way, SPB Mobile Shell didn't quite meet my expectations. (eg. it has also the sucking MS calender hard coded)
Experienced the "non-responsive in the morning" problem 2 times in 3 days, without the phone being charged. Both times I had the white noise effect on the screen.
Turned off TF3D (I like the phone more without it, actually) and the problem didn't occur in the last 5 days since I did this. It's most likely a TF3D related issue and it will prolly be fixed by the next update.
-KickFlo
Hey folks,
I have been having a lot of problems with my X7510 lately. The screen keeps locking up in standby mode. When the device is in standby I turn it on and it prompts me for my password. After putting in my password I just get a black screen with the word "password" at the top. While the device is in this state I can still sync (and see all of the files on it) when I connect to my computer. The screen on the device, however, is locked up. This problem has been happening several times a day lately and I cannot receive calls when it happens (nor do I get any indication of missed calls). The only way to get the X7510 to work is to do a soft reset.
At first I thought it might have something to do with the password manager, so I turned the password off today. A couple of hours later I found it locked up anyway. When I pressed the power button it did not come on at all, though the GSM and BT/WIFI lights continued to flash.
Is anyone having this issue? Were you able to figure out what was causing the problem? I am very frustrated right now. My device locks up so much that it is practically unusable since I have to do a reset 2-4 times a day.
Yes- I'm seeing the same issue from time to time. Haven't had time to investigate yet.
Last time it happened was yesterday- Green and Amber lights were flashing, but all buttons unresponsive, and had to do a soft reset.
Running PocketPlus 4.03 as a front end.
That is probably a software issue. Better enumerate your softwares and find out the common one causing it. Usually start with the last one you installed prior to having the problem.
cktlcmd said:
That is probably a software issue. Better enumerate your softwares and find out the common one causing it. Usually start with the last one you installed prior to having the problem.
Click to expand...
Click to collapse
I agree it's definitely a software issue. The only recent addition for me has been Spb Keyboard. PP4.03 has been on since day one, and did not initially seem to be associated with lockups.
When I have time, I'll try and narrow it down a bit.
I have not installed any new software in over six weeks. The only thing that has changed in the last week is an update to IM+. I have uninstalled it completely and will see what happens. If this fails I am not sure what to do.
LocoHarami said:
I have not installed any new software in over six weeks. The only thing that has changed in the last week is an update to IM+. I have uninstalled it completely and will see what happens. If this fails I am not sure what to do.
Click to expand...
Click to collapse
Just for the record, I don't use any sort of Instant Messaging!
With my Advantage on the ultra-extreme blinks I suffered the tortures of the damned, tortures of the damned. No less than once every couple of hours I'd find my device locked up. Upon direction from my kind forum mates, I decided to uninstall the last software change on the not-so trusty X7510. After removing the IM+ software the PDA still locked up two more times that day. I gave up hope and decided to do an hard reset.
The next day, however, it did not hang up at all. The same goes for today, so after locking up five times a day for a week I have not locked up once in the last 48 hours. No hard reset and all is viddy well, little brother, Viddy well.
Unsure if it was the IM+ update or not, since it locked up twice after the uninstall, but I will not be reinstalling the IM+ update. In the name of science, I will install the original version this afternoon and see what happens.
Most gracious thanks to all those who took time out to reply to this thread.
I can concur that 3rd party software running in the background is usually the culprit.
In my case, I'm having an on-going saga with Hebrew localization bought from P.D.A.C. If I put the device to "sleep", with the email program set to download every 15 minutes (via wifi - no SIM installed), I come back to find a device that will turn on when the power button is pressed (a bit longer than usual), but then no response from any hardware button or screen - a soft reset via the hole in the back is the only way out.
I can in general say that the localization has other problems, like slowing the device down, and generally causing unpredictable hangs, but I'll save that for another thread.
To their credit, PDAC have taken a stab at trying to fix it, but since they don't have (and apparently don't intend to purchase) an HTC 7510 for testing, it's become a slow, hit-or-miss proposition.
One of the problems for gadget fiends like me who are not programmers is choosing a device that isn't massively popular - the support by third-party developers is not adequate. So here I find myself trying to learn how to fix what should work properly out-of-the-box.....and being frustrated by lack of background/knowledge.
-avi
Had this lockup problem since i received the device.
The other week in an attempt to fix this i have flashed to the latest 3.29 Rom from cmonex (thanks!) with ExtRom 3.29. As i have a Chinese x7510 version this ExtRom has fixed Opera text block problem, but still had constant lockup after putting unit into sleep mode.
Yesterday, i tried option 'Do not lock buttons' in Key Lock under Settings. Since I have not had one single lockup! Even having in sleep overnight, hit power button and up pops today screen. Normally i would have to soft reset.
This is what i have done so far. I'll have to start installing apps and see how it goes...
G'day from LA
Hi AvantX,
Another Aussie here, but living in LA for the last 7 years.
I loaded cmonex's hard SPL on to my x7510 some time ago, but so far I've been loathe to load an other ROM on to my x7510 as I have been unclear on the return path to the stock rom in the evet of a mishap. I've been hoping to see some ROM development on this forum similar to Kaiser & TyTN but so far we have not seen too much, other than the promise of AP4 amd MichyPrima's ROM somewhen.
Can you show here some screen shots of the 3.29 ROM? Does it look the same as the stock ROM and how does it run compared to the stock ROM? The stock ROM is 3.27.405.3 - is 3.29 an improvement? Does loading 3.29 affect the radio - mine is 1.58.
Thanks mate in advance.
ok, so heres my problem. i rcvd my TP2 yesterday about 10am. since i got it i have had a problem with it not coming out of standby when i press the power button or when calls come in. i can still answer calls however. ive done numerous hard resets and i have not installed anything other than my contacts. late last nite it just started working fine but as soon as i plugged it in this morning it started acting up again. i have noticed that when it does this i am able to get it to turn if i open the keyboard and tilt the screen up. it will come every time and will remain on when closed until goes back to sleep. i have also noticed that the backlight controls in system power management do not change the screens brighhtness either. i tried to install lumos to see if maybe that would help but couldnt get it to run as it says i need a newer netcf version but i cant seem to install it. has anyone run across this problemm and have any suggestions? btw. sorry for the lengthy post
This sounds like a job for Sprint tech support. Tell them everything you've done so far. In my experience, they're pretty good about warranty replacements.
ok, so i was able to get lumos installed and so far its good. Ive plugged it in, reset and it seems to be working fine now. will let it go the rest of the day without change and see if that fixes my issue. I am inclined to believe there is something wrong with my software that handles power management (duh) which is odd because it is brand spanking new. So just to recap: came off a fresh hard reset and issues persisted. Added my contacts, updated to NetCF 3.5 and installed Lumos to handle backlight. So far so good. I am trying to avoid calling sprint about it as much as possible
But, if anyone else has any ideas, let me know