On Jul 1, 9:29 am, Dianne Hackborn hack...@android.com wrote:
Pending services work fine. However currently for the alarm manager I would
recommend always first sending to a receiver, since there is a limitation in
the system where the wakelock it holds will be released too early when
Like the guy below suggests, I use different actions that the
Broadcast Reciever processes:
Intent one = new Intent(register.alarm.ONE);
Intent two = new Intent(register.alarm.TWO);
As the broadcast receiver gets each message, it registers, cancels
alarms, as needed
I know it sounds silly
I have not tried a pending service yet, but a quick workaround would
be to send a pending broadcast intent to yourself (broadcast
receiver), and launch the service from there.
Regardless of this workaround, it would be nice to know whether there
are issues with pending service intents, or
Hi!
This code works for me: (although I initialize the alarm in the same
service which I want to wake up with the alarmmanager).
AlarmManager alarmManager = (AlarmManager) getSystemService
(ALARM_SERVICE);
Intent intent = new Intent(TrackerService.this, TrackerService.class);
Pending services work fine. However currently for the alarm manager I would
recommend always first sending to a receiver, since there is a limitation in
the system where the wakelock it holds will be released too early when
delivering to a service. So if you want to be sure you receive the
Thanks, but how do you send multiple Pending's to the same service and
are still able to differentiate between them, i.e. like 3 alarms for
different times?
On Jul 1, 6:29 pm, Dianne Hackborn hack...@android.com wrote:
Pending services work fine. However currently for the alarm manager I would
Use different actions, data, type, categories, or the request code to create
different distinct objects.
On Wed, Jul 1, 2009 at 11:13 AM, Veroland marius.ven...@gmail.com wrote:
Thanks, but how do you send multiple Pending's to the same service and
are still able to differentiate between
7 matches
Mail list logo
