The Palm caveat about the notifications not being sent is for the low or missing battery case. All other situations, the notifications should occur.
To add to what Tom says, the sysNotifyLateWakeupEvent is supposed to be sent only when the device has decided to wake completely. I've noticed, most recently on TX and 700p, that I always get the event, even for proc alarms, which are specifically not supposed to fully wake the device. My assumption is that with recent devices (since OS5), the Palm Whomever dev teams have either forgotten or simple ignored the purpose of the power management notifications. Where once we were able to tell if the device is dreaming or actually awake, we can no longer know for certain. I have a threading library that was able to schedule threads based on attributes such as 'can wake device', but this is no longer possible without jumping through very inefficient or undocumented hoops. On 9/23/07, Thomas Ward <[EMAIL PROTECTED]> wrote: > Hi, > > One of our apps displays some UI when the device is turned on. For many > years, we've used sysNotifyLateWakeupEvent to get notifications of when this > happens. Things worked fine until the 755p, but on that device, 95% of the > time, that app doesn't seem to get the sysNotifyLateWakeupEvent. > > The strange thing is that in both the Debug and Release 755p simulators, the > sysNotifyLateWakeupEvent is received every time, and the application works > just fine. But not on the real device. > > I went back to look at the APIs, in case anything has been added. Nothing new > is there, but it still says: > > "IMPORTANT: This notification is not guaranteed to be broadcast. Thus, it is > unsuitable for applications where external hardware must be powered on when > the device wakes up." > > The doc says that one of the reasons you might not get the notification is if > the user removes the battery. I know this is not the case in my tests, are > there other reasons why it might not be sent? I can't find any other details > in the doc. > > I've searched the archives, and a few people reported similar problems with > the 680, but I couldn't find a definitive answer. Any advice on what's > changed would be appreciated, but I guess my problems comes down to two > questions: > > 1. Did something change with sysNotifyLateWakeupEvent, and is there something > that can be done so that it always gets sent? > > 2. Is there some better method my application should use to know when the > power is turned on? > > Thanks in advance. > > Tom > -- > For information on using the ACCESS Developer Forums, or to unsubscribe, > please see http://www.access-company.com/developers/forums/ > -- [Jeff Loucks] -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
