Problem in using RTimer

[DemiDI]

I used RTimer::At() in my application, and RunL() received timer request status. But I received KErrAbort in RunL() every half an hour.
I have read "At-Timer Issues": KErrAbort means that the timer was aborted because the system time changed. The system time can change when, for example, automatic time and date update from the network is enabled and a new time is received from network, or when changing time zone or the daylight saving setting. Also, the system time can be changed by any application at any time by using User::SetHomeTime(). In all of these cases all the active At-timers will complete immediately with KErrAbort.
And I didn't do anything like above in my codes. I don't know why, Could anyone help me?
Thanks!

[amitkankani]

First, which phone are you trying this on ?

there is a setting called automatic update of time, DISABLE it and see, but i suggest this will not be a solution as you cannot ask customers to do this ...

what is the reason for RTimer::At() usage ?

[DemiDI]

Hello, amitkankani,

I tried this application in N70 for S60 2nd, and the setting called automatic update of time in my phone was disabled.

I want to realize the function that something will be done half an hour after the phone is booting, and expired-time(only minutes) in every day. I used an auto-start application, it will probably start the application with RTimer::At() two minutes after phone-booting, and RTimer is set to half an hour later, when time is expired, I set time-point to the next day. The above instance is occured...
Thank you very much!

First, which phone are you trying this on ?

there is a setting called automatic update of time, DISABLE it and see, but i suggest this will not be a solution as you cannot ask customers to do this ...

what is the reason for RTimer::At() usage ?

[DemiDI]

http://www.newlc.com/topic-5076?destination=node%2F5849
The problem in above link is similar to mine, but it seems no one can answer it authoritily...

[amitkankani]

as i understand from the link, there is no reliable solution till date, and as the last tab said it, u need to handle KErrAbort and do a new RTimer.At every time u get KErrAbort...

thats the only way i guess... !

[BETEP.OK]

I tested my programm on 5800XM and N95.
On the 5800XM the KErrAbort happens every 5 minutes.
On the N95 the KErrAbort happens every 30 minutes.

Thus, this issue can be a reason of the battery discarge if you code in a RunL consumes a lot of a processor recource.

[wizard_hu_]

It happens because you have enabled synchronizing the time on your device to Internet time or something.

[amitkankani]

yes, but that any user could enable and the RTimer Logic will anyways not work ...

so how does one do that with time updatable from internet !

[wizard_hu_]

Since you should store the TTime for RTimer::At anyway, it is possible to re-issue the request, perhaps after some sanity check.