<br><br><div class="gmail_quote">On Tue, Jan 11, 2011 at 11:47 AM, Al Johnson <span dir="ltr"><<a href="mailto:openmoko@mazikeen.demon.co.uk">openmoko@mazikeen.demon.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Tuesday 11 January 2011, Davide Scaini wrote:<br>
> i'm experiencing the same problem: clock is stuck during suspend and<br>
> it takes some time to update correctly when resumed. This has the side<br>
> effect to make ffalarms useless ...<br>
> any hint is welcome<br>
> d<br>
<br>
</div>More details please. The rtc is meant to be powered by the main battery during<br>
suspend, so the backup battery shouldn't have any effect, hence the belief<br>
that it's a software bug. ffalarms (via fso) is supposed to set the rtc to<br>
generate an interrupt to wake the phone at the specified time if necessary. It<br>
is possible the rtc isn't being set, or that ffalarms isn't being called on<br>
wake among other things.<br>
<br>
Does the phone wake but not sound the alarm?<br>
If you wake the phone and immediately run 'date' in the terminal do you see<br>
the correct time, or the time when the phone suspended?<br></blockquote><div><br>the phone does not wake neither during suspend nor when shutdown (if i set an alarm).<br>date is working correctly, but the illume gadget is not. I thought this was related to the malfunctioning of ffalarms (but Lucasz says it's only a gui problem).<br>
d<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5"><br>
> On 12/22/10, Al Johnson <<a href="mailto:openmoko@mazikeen.demon.co.uk">openmoko@mazikeen.demon.co.uk</a>> wrote:<br>
> > On Tuesday 21 December 2010, Rui Miguel Silva Seabra wrote:<br>
> >> Em 21-12-2010 12:55, Gay, John (GE Energy Services, Non-GE) escreveu:<br>
> >> > The last time my FreeRunner's battery died, the clock reset to epoch.<br>
> >> > Now, it no longer keeps time during suspend either. I'm guessing this<br>
> >> > means the clock battery has finally died.<br>
> >> ><br>
> >> > Someone recently commented that they replaced their battery with a<br>
> >> > pair of super caps. I just wanted to confirm my diagnosis before I<br>
> >> > take a soldering iron to my phone.<br>
> >> ><br>
> >> > Cheers,<br>
> >> ><br>
> >> > John Gay<br>
> >><br>
> >> So that's why my clock...?<br>
> >><br>
> >> a) goes back to 2000 without a battery<br>
> ><br>
> > Probably<br>
> ><br>
> >> b) takes so long to update the clock in the toolbar and idle screen of<br>
> >><br>
> >> SHR<br>
> ><br>
> > Unlikely - even in suspend the rtc is powered from the main battery, not<br>
> > the backup. The lack of update is most likely a software bug not a<br>
> > hardware problem.<br>
> ><br>
> >> Damn, any instructions on how to do this properly?<br>
> ><br>
> > Just the post to the list.<br>
> ><br>
> > _______________________________________________<br>
> > Openmoko community mailing list<br>
> > <a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
> > <a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
><br>
> _______________________________________________<br>
> Openmoko community mailing list<br>
> <a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
> <a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
<br>
<br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br>