ffalarms 0.2.1 and atd-over-fso (now works on SHR-testing)
timo.scheffler at uni-oldenburg.de
Tue Apr 28 17:12:40 CEST 2009
Wrong Link, here is the example:
# Wakeup in 60 seconds
system_bus = dbus.SystemBus()
rtc_object = system_bus.get_object('org.freesmartphone.odeviced',
rtc_interface = dbus.Interface(rtc_object,
Timo Scheffler schrieb:
> I suppose the "atd" doesn't wake the openmoko up at the right time (I
> used your ipk from the project site).
> I just tried waking the Openmoko up using the FSO api and was successful :)
> I think it would be great to abstract the scheduling part, so that you
> could use FSO api or at (to support 2008.12, SHR should be able to do
> FSO api?) to set the alarm?
> At least using FSO api you set a unix_timestamp, so alarms for tomorrow
> or the day after tomorrow are no problem... But you can't register more
> than one wakeup at a time (own handling would be necessary)...
> Just some thoughts... because I love your gui and would be willing to do
> something about using the FSO api (but also contribute to the main thing
> instead of doing my own version).
> Example of setting the wakeup time using FSO api can be found here .
> : http://wiki.openmoko.org/wiki/User:Sparrow
> Helge Hafting schrieb:
>> Timo Scheffler wrote:
>>> I installed ffalarms and love it, but the wakeup from suspend doesn't
>>> work... I use FSO 5 and the ffalarms 0.2.1 and atd-over-fso with python
>>> 2.6 package.
>>> Is there anything to configure, so that it might work?
>>> (At least my phone doesn't goes to sleep by itself, so thats no issue...
>>> but that's another problem with fso5 :D).
>> It wakes up from suspend for me - but that might be a difference between
>> FSO and the SHR that I use.
>> Helge Hafting
>> Openmoko community mailing list
>> community at lists.openmoko.org
> Openmoko community mailing list
> community at lists.openmoko.org
More information about the community