c_c wrote:
> Hi,
> 
> @Marco Trevisan (Treviño) - From what I can see what you're doing is :-
>   
>   a) vibrating and playing the notify sound every 120 seconds if the phone
> is awake.

Yes. For doing this you just need an ecore_timer and few dbus calls to
play the sound and vibrate (if you don't want to use other
methods/dependencies).
However, in my idea, the user should have been able to set these values
(enable notifications and seconds/minutes to wait) from the settings.
In your launcher this would be quite easy by adding few sliders
controlled by a pair of checkboxes ;)

>   b) waking up the phone using rtc-clock through an atd-alarm 

Yes.

>   Will implement a) real soon. b) might take a little time - 'cause I need
> to understand the rtc-clock method. Thanks for the idea though :-)

The rtc-clock method is quite easy... Practically you can set ONE time
in wich the rtc clock will send an interrupt to the PMU to wake-up (if
needed) the phone.
Atd does this work by parsing its configuration files and setting the
very next job as the next rtc-alarm.
My workaround uses atd to wake-up, notify and sleep again the phone
every X minutes.

I figure this is something that the FSO stack should support by itself,
but actually I think that this is the only way to get this.

-- 
Treviño's World - Life and Linux
http://www.3v1n0.net/

_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user

Reply via email to