Diese Seite ist nur in englischer Sprache verfügbar

Online Manual

Know limitations

1. Issues with S2U2

If you have problems with G-Alarm and S2U2 on your device (e.g. no alarm goes off) try following solutions:

• G-Alarm advanced options: check "Add to S2U2`s exception list"
• S2U2 options:
  • Lock when screen is blank > off
  • Lock when backlight turns off > off
  • Power off in > off
  • But blank screen only > off
  • Blank screen on talk > off
  • Please check those settings on both "On battery power" and "On external power"

2. Windows alarm bug

Windows Mobile has on some devices a strange behaviour: Although an alarm is successfully added to the WM notification queue (it's like a scheduler) it doesn't go off.
Searching the web gave me following information:
At midnight WM rebuilds the notification queue, therefore it wakes up for about 15 seconds. If the notification queue is too big or the device too slow WM goes to sleep again before it could finish building the queue for the next day.
If you force WM too stay awake for a longer time, it should successfully build the queue on at least more devices.

If you start G-Alarm and it complains about the Windows alarm bug, you've got the default WM settings (15 seconds WakeUpTime). If you press "Yes" G-Alarm changes it to 120 seconds which should be enough.

Here are the registry values G-Alarm changes:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts\ACResumingSuspendTimeout
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts\BattResumingSuspendTimeout

3. Daylight saving bug

On some devices in some countries there is a Windows Mobile bug that the notification fire up one hour too early / too late if there is a daylight saving time change.

Download the bugfix from the Microsoft site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=0D6FC192-3142-4473-B435-B514E4B360A5&displaylang=en