Vybijanie baterky

[niky79]

Ja galarm zkusmo vyhodil a fakt se mi zda, ze ta vydrz je vetsi.

[Aspire]

Mam stejnou zkusenost, jako Martin Nanek. Mam G-Alarm 2.2 a nemohu si stezovat. Baterku setrim vypnutim vyhledevani pozice a nastavenim podstviceni.

(U G-Alarmu mne stve jen to, ze se v 0:00 zapne telefon. Svetlo mne vzdycky vzbudi. )

[Martin Nanek]

2Aspire: ... zapnutí mobilu o půlnoci se dá lehce vyřešit, je to ale kvůli následujícímu (skopírováno ze stránek výrobce g-alarmu)

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
________________________________________________________________
nebo toto úplně vypnout: Don't wakeup at midnight

Because of the Windows alarm bug, G-Alarm wakes the device at midnight so Windows Mobile can rebuild its notification queue. If you turn this off by changing or adding following registry value, it may happen that an alarm doesn't go off:

registry in "HKEY_CURRENT_USER\Software\ageye\G-Alarm".
MidnightWakeUp: False

[Aspire]

Diky Martine, vyzkousim a napisi. Verim, ze to pomuze.