>In my software I give special treatment to vchrLowBattery for various >reasons. I was very surprised when I saw that after a short time of >running my app on a OS 3.3 device it received a vchrLowBattery. A while >later it received another one, and so on. The intervals between these >events seem to be random, but not too long (2-10 seconds).
This is a timing problem. If you take too long to pass a vchrLowBattery to the system, another one will be enqueued. (This is because the code watching the battery has decided that its previous warning must have been lost or something.) So you mustn't put in a big delay, but rather hand it along to the system as soon as you can. The randomness is probably because you're right at the threshold where it might send another one, depending on various factors and thread scheduling and such. I think I also remember that vchrLowBattery might be sent even when the battery isn't low, that it was used as a signal to a different part of the system to check the battery, but I could be mistaken. -David Fedor Palm, Inc. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
