29-12-2005, 08:40 PM
ZeBoxx
Senior Member
Join Date: Dec 2005
Posts: 923
Just to add - this does indeed appear to still be a problem in Windows Mobile v5.
I have a QTek 9100 EN and it has had this problem out-of-the-box.
I posted some pretty useless information on this at the Dutch QTek forums - basically what it boils down to is this:
The symptom is that the device doesn't wake up when a notification tells it to (be it alarm clock, calendar event, etc.)
Yes, this is a known issue in WM2003+
No, Microsoft does not readily acknowledge it because:
No, it doesn't happen on all installs - it appears to be intermittent and sometimes even device specific
No, no concise cause was ever found.
Yes, some people suggest that it's either:
A. notifications database going whack
B. suspend > intermediate state > wake up|suspect going whack
C. you resetting/powering down before the device can save data ( not the case if you let it auto-poweroff )
D. other (PIM) database going whack
Yes, there are utilities* to possibly rectify all of these
No, they're not a perfect fix
*
To resolve A, you can use
Check Notifications and
WakeUp TweakTo resolve C - just don't reset/power off immediately after doing something. Consider it akin to hitting the reset button on your PC while working on your documents/downloading files/etc. Don't
To resolve D, you can use
FixAlarm. Beware, using that option also clears out your Appointment and means you'll have to re-pair pocket outlook/etc. to your desktop variant.\
As for why they're not a perfect fix... just the battery timeout stuff never did the trick for me. The option to bring the device to full power on does appear to work (so far - but the real test will be tomorrow morning, and whether I'll wake up at 8:00/8:10/8:15 like my QTek 9100 should, or at 8:30 when my Sagem my-V55's alarm goes (which has never failed - how funny is that)) - but it also causes, for some time after auto-power off, the screen to come back on, etc. I can only guess that there are some programs running - be they standard or not - that cause this. After some time, though, that behavior stops.
It does make me wonder, though, just how good these 'fixes' are. What I mean by that is this... does anybody know just how much power drain is -actually- saved when going into the standby mode ? I ask because...
1. obviously WM5 is still running in the background
1.1. it doesn't have to boot up
1.2. it still keeps track of incoming calls (GSM device is on)
1.3. it still keeps track of connections being made
1.4. it still keeps track of your other notifications
2. the problem is in getting the device to wake up from the standby mode
Thus if standby drains not all that much less than leaving the device on (but with the screen off) - then my money is on just never letting the thing go to standby mode. That way all alerts should 'just work', without side-effects of any of the 'fix' utilities, etc. A predictable down-side being that you don't get the password protect screen - maybe there's a good replacement utility for that thing anyway?
Qui Ago 02, 2007 3:48 pm 
