Hi,
I tried 2 different versions of WM6 (Pdaviet and MuN) and both having issue with incosistency with alarm. Sometimes they would not fire at all and sometimes they would fire current alarm and missed alarm at the same time.
G
Common problem, even in WM5.
I use pocket wakeup, works every time:
http://www.pocketpcfreewares.com/en/index.php?soft=1299
I am using Faria's The Real Thing teamed with PhoneAlarm and haven't run into a problem yet.
I noticed that this will happen when you soft reset the device. Once you reset the device the HOme zone defaults to "Caracas, La Paz". Just make sure that your original time zone is set back to whatever you set it at originally and your alarms should go off as normal.
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
Anyone else finding that PhoneEx locks up on them after awile? Seems like a great program otherwise but 2 or three times a day I'll bring it up and it won't do anything other than hide and show itself. It won't navigate between favorits, calls, contacts, etc. It is completely unresponsive. Attempting to kill the process with MemMaid generally toasts the phone and I have to reset it.
Just wondering if I'm alone in this, or if anyone else has discovered a magic combination of things that may be leading to this.
AJ
Well I can possibly answer my own question. On a hunch, I disabled S2U2 from automatic startup and I haven't had PhoneEx lockup once since.
Would suck cause I like S2U2, with PhoneEx I can ditch about three other programs I've been using, so I guess if it continues to work I will have to do without S2U2. Or perhaps I will try fiddling with it to see if there's a particular setting in S2 that is causing this issue.
AJ
Although since removing S2U2 the PhoneEx lockups have diminished in freqeuncy, they haven't gone entirely. I woke up this morning to find that PhoneEx was unresponsive, but, as is always the case, the rest of the system works normally (I haven't yet received a call with it in this state - it will be interesting to find out what happens).
Has no one else experienced this problem, or does no one else use PhoneEx?
AJ
PhoneEx
I am... for about 4 days on two phones...nothing like that happend...yet and hopefully never does. love s2u2 and PhoneEx...i personally do not use phoneex to answer the incoming calls...i let the s2u2 to do all the job including the notifications....which is better to let s2u2 to deal with them so you won't get any conflicts...take care
Ps.
by the way a new version it's gonna pop up any day now 1.4 the russians done a new improved version it take about four times less memory(about 300kb instead of 1000 kb) and fixed some bugs to it...it's out there already but only in chirilic language...the only problem i have so far is that i can't use the speaker button it kinda do weird noise when activate as if the speaker it's to close to the mic.
PhoneEX
I does not lock up for me, although it took me 2 days to note that the keboard locks during a call and you have to unlock it to use the keyboard (could that be your problem?)
I do have another problem though and that is if I do a soft reset for whatever reason PhoneEx then spends 3 or 4 minutes "Intialising Contacts" before I can use my HTC Touch HD.
Anyone got a solution for this.
Sam
iconsoft.com (phoneEx)
phoneEx is a great program. my friend has it and he has never had a problem with it on his windows mobile device.PhoneEx is a great program people with a windows mobile device should definatly look in to the program . i am curenty using the trial i am about to get the program i am looking forward to it i canot wait i can already see its going to be great . my phone is doing great with this program i love it and thanks Iconsoft you guys are really smart for putting the program on there . you can get the program by going to www.iconsoft.com
i recomend it it is a great program
Installed PhoneEx (no to answer phone) on my Elf today after a week of using S2U2 - and had four lockups already. Any hope for this? *trying again with the "don't use keyboard lock " setting set to true as per another thread/post.
I have Gonzo's latest version (6.1) running on my Vox.
I enabled "Alarm 1" to occurr every weekday. It worked great for over a month. I have since changed the time of Alarm 1 from 6 AM to 7AM. However, Alarm 1 now goes off at BOTH 6 and 7 o'clock. I've restarted the phone, which did not fix the problem.
Setting the Alarm to Off only eliminates the new 7 AM alarm. It's like the 6 AM alarm won't get deleted for some reason.
Any insight would be much appreciated!
Thanks
getting the same problem in all the roms i tried including the OEM form HTC
yeah it's really a pain in the @$$... I don't want to reflash it again.. especially if i'm not positive that will fix the issue