Archived:Inaccuracy in PushRegistry.registerAlarm() method (Known Issue)
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
The article is believed to be still valid for the original topic scope.
The article is believed to be still valid for the original topic scope.
Article Metadata
Tested with
Devices(s): All devices which support PushRegistry
Compatibility
Platform(s): S60 2nd Edition FP2 and FP3, S60 3rd Edition and S60 3rd Edition, FP1
Article
Created: User:Technical writer 1
(April 6, 2006, updated February 22, 2007)
Last edited: hamishwillee
(28 Jun 2012)
Contents |
Overview
A MIDlet can be launched automatically by using the PushRegistry.registerAlarm() method. You can set the time at which the MIDlet is to be executed. The launch time is not followed precisely in certain S60 devices.
Description
If the method PushRegistry.registerAlarm(myMIDlet, alarmtime) is used for automatic MIDlet execution, especially longer times do not work precisely.
How to reproduce
Use PushRegistry.registerAlarm(myMIDlet, alarmtime) for registering an alarm. The MIDlet might be launched at the wrong time. If a long enough alarm time (several hours) is used, the alarm might be totally ignored.
If the alarm time is longer than 30 minutes, the alarm occurs in much less time, in minutes.
Solution
This will be fixed in S60 3rd Edition, FP2.
(no comments yet)