0

I have created an On Boot Receiver to repeatedly call a wakeful intent service every 5 minutes but cannot figure out how to start the service immediately when the app is installed..? I do not want to rely on the user rebooting their device before it starts to run!

Here is my code so far :

public class OnBootReceiver extends BroadcastReceiver {
private static final int PERIOD = 300000; // check every 5 minutes

@Override
public void onReceive(Context context, Intent intent) {
    AlarmManager mgr = (AlarmManager) context.getSystemService(Context.ALARM_SERVICE);
    Intent i = new Intent(context, OnAlarmReceiver.class);
    PendingIntent pi = PendingIntent.getBroadcast(context, 0, i, 0);

    mgr.setRepeating(AlarmManager.ELAPSED_REALTIME_WAKEUP, SystemClock.elapsedRealtime() + 60000, PERIOD, pi);
}}

Can anyone help me out pls? :)

Mike
  • 369
  • 1
  • 6
  • 24

2 Answers2

0

If you want to set an alarmmanager to start your service when the app is installed, then it's not possible. It's a OS limitation, security if you will. But if you want to start the service in the moment the app starts, just call it, it will keep runing.

AlfredoVR
  • 4,069
  • 3
  • 25
  • 33
  • thanks alfa but I am using the alarmmanager solution to ensure my service runs in standby (sleep) mode without using a Partial Wake Lock as this drains battery life.. is there really no event on application install? :/ – Mike Dec 13 '11 at 16:54
  • beware that some devices enter something called deep sleep, in which no matter what method you use, it will not wake up. What i meant is that you just need to file a new alarmmanager schedule to start the service. – AlfredoVR Dec 13 '11 at 17:14
0

Essentially, since the Application object is created when the application is started and when the BOOT_COMPLETED Intent is received, you could register with the AlarmManager in the onCreate method in your custom Application class. Just be aware that the Application object is instantiated every time the process starts, which includes cases where the process is temporarily killed to save resources. But if you don't change the PendingIntent in any way, it should be no problem to register over and over again.

However, it is not possible to start the application when it is installed, there has to be some user interaction first.

David Burström
  • 1,592
  • 14
  • 14
  • What if the application has no GUI? I.e., it only ever runs as a service, thus does not permit user interaction. – user2768 Nov 12 '15 at 11:00