CeRunAppTime do not wake up device ?

  • Thread starter Thread starter xhyman
  • Start date Start date
X

xhyman

Hello,

To save energy, I use CeRunAppatTime and GwesPowerOff functions to suspend
and wake up the device.
This works very well on pocket PC WM6.0 ( despite i was obliged to force the
screen light on ), but I am now transferring my software on pure CE5.0 PND
and it doesn't work anymore.
If I use CeRunAppattime only without Gwespoweroff, the launched application
start only if I put small timing (10s) and in this case it start immediatly.
I guess it is due to timer accuracy. But If i ask 60 or 120s it doesn't start
anything.
In fact I have the feeling the notification system is not really installed
by OEM when platform was build ( my project is not yet big enougth to obtain
a customized platform and I have to developp with an existing one ).
Do you confirm that ?
Is there something to change on the registry to activate notification
function ?
thanks in advance
Best regards
 
The device OEM has not properly implemented the date/time alarm interrupt to
awaken the device. There's nothing you can do about it. They have to be
the ones to fix it. Can we presume that the CeRunAppAtTime() works when the
device is not suspended?

Paul T.
 
Are you *certain* it's not waking at all? Some devices wake to a low poer
state with the backlight/display off (unattended mode). Verify this is not
the case.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com
 
Hi Paul,

When device is not suspended Cerunappattime works only if I put short
timing (10s) but the application start immediatly. If I set 60 seconds or
more then nothing happen. That 's very strange!
regards
Guillaume
 
Not all that strange. There's a default minimum in the kernel code that
ships with CE. IIRC if it's < 11s then it doesn't set up a timer interrupt
but instead fires off immediately. You're seeing <10s working becasue it
never sets up a timer interrupt in the first place, so any bug or omission
in that wouldn't manifest itself.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com
 
Seems like the OEM broke it entirely, then. They are never firing real-time
clock alarm events, so your time-based events are never set, whether the
device is suspended or not. You'll have to talk to them...

Paul T.
 
Ok, it seems clear now, I must find an other way to save energy.
The problem of the device is that even when switching off ( setdevicepower )
the GPS COM7: port and the backlight BKL1, the lifetime is around only 100
minutes. In my mind those 2 devices are the biggest energy consumers. Am I
wrong ? Do you have idea which other device could I switch off ?
regards,
Guillaume
 
Back
Top