Happy Holidays: Heads-Up on Alarms and Battery Drain

M

make me a sandwitch!!!

New member
Happy Holidays Everyone!

Just wanted to remind everyone that if you have a Birthday/Event/Task in early January that is scheduled to trigger a Reminder or Alarm in December that you will need to attend to this by moving the reminder/alarm into the same calendar year as the Birthday/Event/Task.

If you don't do this you may be wondering why your device keeps turning itself on or your battery is draining unexpectedly.

Not sure if this has been addressed in new device models introduced in 2006 (Treo 700p and Treo 680).
 
Err... actually the thread entitled 'Why PDABach Should Stay Out Of The Ladies' Restrooms at rabroad' probably saved you the most trouble in the long run. The location of which temporarily escapes me. :)
 
All:
I removed the off topic part, DT was correct with her remark this thread should be clutter free for those desperate in need.
I trust you all understand and will respect this decision ;)
 
I'm sorry but, could someone explain why this happens and which models should be warned? I couldn't locate any thread posted last year regarding this issue. I've used several Palm devices for about 7 years, but I have never experienced this occasion although I have lots of reminder/alarm set in my Calendar and Task.

Thanks and happy holidays to all. :)
 
ds2dys, here's another thread on the subject, courtesy of Dick Tracy. Unfortunately, the threads linked to in THAT thread seem to be gone:

http://forum.rabroad.com/showthread.php?t=96819

I'm not exactly sure which models are affected, though I know my Tungsten E2 has had problems in this fashion. In essence, you cannot make a reminder to take place in December about an event that will occur in January. So I cannot set a two-week reminder for my sister-in-law, whose birthday is January 5th, without this bug happening.

Why it happens is something beyond my capacity to understand!
 
doogie, thank you very much for your prompt reply and the link.
Well, as you said, the links in that thread have gone to nowhere.

If I understand correctly, an event in the first week of January with a reminder set dated in December will cause this problem. Am I right?
I checked my calendar and fortunately there was no event in the first week of January. This explains why I haven't noticed this bug before.

Happy holidays!
 
Yes, as I understand it, your description will cause the problem. I'm not sure if it's related to a January event specifically or if it's simply an alarm reminder set for the year before the event is to take place. People noticed the problem because of January events, but I'm not up on the specifics of what exactly triggers this behavior.
 
OK, I think I understand what causes the problem, and if I give myself a 1-week reminder on my son's January 2 birthday, I'm going to get hit. But I'm not clear on what "the problem" itself is. What will happen if I do that? Apparently, the earlier threads explained this, but they're no longer available.

By the way, thanks for the warning. This one's new to me.
 
I haven't had it happen for over a year, thanks to DT, but the problem was that the PDA kept turning itself on to remind me about it so that the batteries drained in the 16 or so hours I was out of hearing of the alarms one day. (I remember--but only vaguely--because I have a cousin with an early January birthday.)
 
I did some search and found many threads regarding this issue. I'm surprised I haven't noticed these threads before. Anyway, here are some links among those, one, two, three ,four, and more.

Throughout those posts, apparently, Dick Tracy is the one who has good knowledge for this issue and has a reminder to remind rabroad members to correct it every year. Thank you so much for your effort, Dick Tracy. :)

In summary, if you have any event within the first week of January, you should set the reminder between January 1 and the day of event, not December.
 
You're welcome ds2dys.

I started doing this reminder as I observed many threads popping up for the same seasonal issue.

Another tip, should you need the lead time, is to stick an Event on your Calendar (to order the birthday cake, mail the package, etc.) on the date the Alert normally would trigger. I have two early January birthdays and have set the reminders as repeating events occurring every year in that last week of December. I have also unselected Alarm for those particular birthdays.

Hope this helps.
 
No. I had intended to wait until Christmas eve (and there is no event or alarm anywhere in my electronic brain) then saw a post regarding spontaneous turn-ons, challenging my assumption that most people use the default settings. :eek:
 
As best I can understand there is a bug or limitation in Alarms that is unable to span calendar years, triggering notification loop. Have not done extensive searching but suspect this is limited to devices with extended PIMs and may have relation to hooks to legacy PIMs. As I no longer have OS4 or prior models in-hand not able to test this theory. Wonder if CESD has a work-around in Datebk6.

Disclaimer: last time DT coded or debugged anything was pre-Zoomer.
 
To my knowledge, DB6 ITSELF does not have this problem ;)
BUT ... DB6 uses the same Calendar and Contacts databases, so the built-in Calendar and Contacts will still pick up this problem (last time this happened, TX was affected as well, just found back a post on the yahoo group indicating this).

I don't use Birthday from Contacts (use annual repeat in DB6, much more powerful), I do not use reminders on it either (I use DB6-advance floats, much more powerful and not affected by this bug :D )
 
Back
Top