android-alarms

I have a fairly standard Service which I wish to trigger using an alarm. Here's the initiation section of the service: class MyService extends Service { private Context context; private AlarmManager alarmManager = null; private final String startReason = "com.stuff.myreason"; private final int REASON_NO_INTENT = 0; private final int REASON_ALARM = 1; private final int REASON_X = 2; // and so on. @Override void onCreate() { super.onCreate(); context = getApplicationContext(); alarmManager = (AlarmManager)getSystemService(ALARM_SERVICE); // do onCreate stuff } @Override int onStartCommand

In my app I want to run some code every day at a specific time using an AlarmManager . In the android documentation I found this: Registered alarms are retained while the device is asleep [...] but will be cleared if it is turned off and rebooted. And that is the problem. I want to run the code even if the user reboots the phone. If the user reboots the phone he currently has to relaunch my app to start alarms again. How can I prevent this? Is there a better mechanism I should use instead? Create Boot Receiver using following code : public class BootBroadcastReceiver extends BroadcastReceiver

We are currently developing an Android app that is a fitness-tracker application. It runs constantly in the background, and it works fine on most devices, but we've been having issues with the application dying completely on some Samsung devices. After some investigation, it seems like some Samsung devices has a completely custom "App Optimisation" feature ( http://forums.androidcentral.com/samsung-galaxy-s6/599408-app-optimisation-after-updating.html ), which is basically a (very) primitive version of the Doze feature that exists in later versions of Android which basically just murders apps

I want to run some task (i.e. get my web site news page) periodically (once a week/ a day), even if my application is closed. Is it possible? Graham Smith Yes it is, you need to look at the AlarmManager to setup a reoccurring "Alarm". This is better for battery life on the device, as unlike a service it does not run constantly in the background. The Alarm triggers a broadcast receiver which will execute your custom code. As a final note - there are enum values for the timing of the Alarm including daily, half daily and many more although you can just set an actual value. A good example can be