Android :: Stopping AlarmManager.
Apr 5, 2010
I have a AppWidget, after I delete it from HomeScreen it seems not stopping the AlarmManager attached with it. I have supported it with the AlarmManger, that call the ProviderImplementation class every 1 minute and in onReceive I put the code to call onUpdate. and in onDelete I explicitly stop the alarm, but it seems it is running continously and not stopping. any cure of it ?
I have stopped it with cancel(pendingintent) function.
View 2 Replies
Jul 20, 2010
I am currently setting an alarm to fire off a background service every 2 minutes in order to check my server for certain updates. Now if I start the app and my screen is on and not locked the phone plays the sound I need it to play and opens the activity. Thats great. But the way I need it to happen is if the screen is off and the phone locked I still need it to check every two minutes and I need it to play that sound and open the activity that is needed. This does not happen for some reason. Could someone explain to me why the alarm doesn't function when my app is not "running" (by this i mean the app is marked as a running process but not actually visible to the user) and the screen is off? The code for the timer is below: CODE:.............
View 4 Replies
View Related
Mar 10, 2010
I am using alarmmanager in my app. It works perfectly for Nexus One and wakes the phone up everytime the alarm fires. But for droid it seems that the phone doesn't wakeup, is there an extra setting on the phone which can prevent the phone from waking up?
View 22 Replies
View Related
Jun 14, 2009
alarms.set(AlarmManager.RTC_WAKEUP, getTime(), alarmIntent);
I have set a alarm,but now i want to delete it? how can i make it.
View 3 Replies
View Related
Feb 24, 2010
I think I'm reading some conflicting statements about the AlarmManager on the Android docs website. The following statements both exist on this page:
http://developer.android.com/reference/android/app/AlarmManager.html
[at the top]
"Registered alarms are retained while the device is asleep (and can optionally wake the device up if they go off during that time), but will be cleared if it is turned off and rebooted."
- and -
[under setRepeating()]
"This alarm continues repeating until explicitly removed with cancel(PendingIntent)"
So, the question is, do I need to register a BootReceiver that re-sets my Alarms when the phone turns on. The first statement makes me think I do, but the second statement is worded in a way that would lead one to believe that it would live forever, unless a cancel() call on that Intent is called.
So, which statement do I believe or am I misinterpreting one of the statements? I suppose when the power is turned off or back on, Android itself could call the cancel() function on all alarms. I guess it would help if it said that after the second sentence.
View 2 Replies
View Related
Jul 4, 2009
Show me some sample code on how to use an AlarmManager in android.
I have been playing around with some code for a few days and it just won't work...
I need to trigger a block of code after 20 minutes from the AlarmManager being set.
View 1 Replies
View Related
Mar 3, 2010
I changed AlarmController.java in ApiDemo a little bit, so I want the alarm not to go off when the phone is sleeping by using AlarmManager.RTC.
CODE:.................
The receiver code is like below:
CODE:..............
I ran the modified app, but I still see many log messages as below after the phone wento sleep (the screen was black):
CODE:...............
This means the flag AlarmManager.RTC didn't work.
View 1 Replies
View Related
Jul 22, 2010
I have a service that I need to execute every two minutes. Would it be more efficient to use an alarm or a timer?
View 3 Replies
View Related
Aug 7, 2010
I am trying to create intents that will be set using alarmmanager. Currently, I can do this with one intent, add extra data to it (strings, but i send them as one string with a seperator), and everything works fine and goes off at the correct time. However, when I try to send multiple intents like this, they are overwritten and only one goes off at the correct time. How can i structure my intents so that they appear different to the alarmmanager (i think they are getting deleted when filterIntent() is run).
long story short- putExtra() makes all the intents look the same still... how can i make them look different so they wont get deleted (and keep track of them in case i want to delete a specific one)
View 2 Replies
View Related
Sep 6, 2010
I've created a simple app widget for personal use that queries a site from the internet, parses the XML received and displays some info from it. I'm using a Droid X, if that makes a difference; both in the emulator and as physical hardware, developing in the Android version of the MotoDev IDE.
No matter what I put in updatePeriodMillis, the shortest refresh time I can get is 30 minutes (I thought this was a 1.6 only bug but apparently not since I'm running 2.1) and I want it to refresh every 5 minutes, with some caveats. I don't want the widget to refresh when the screen is off and I want it to refresh immediately upon waking up the screen. My search for information says to set updatePeriodMillis to 0 and use the AlarmManager instead, but I can't find any complete code examples on just how to do this.
Obviously, I'm new to Android development, and Java in general actually, but I've been a developer for a very long time with experience in just about every other language. Currently working in C#, so I thought I'd be able to jump in fairly easily. Can anyone point me to sample code or an open source project that does what I'm looking for? I have other questions, but until I get this piece working they don't really matter. :)
View 5 Replies
View Related
Feb 27, 2010
Any experts on AlarmManager out there?I've got something weird going on.The basic code to set my repeating alarm works fine. I can close my app and the alarm will continue to run like clockwork every five minutes. It works fine only if I set it in the app and then close the app.I've got a registered BootReceiver for re-registering the repeating alarm. I know it fires on boot b/c the log message clearly shows it is firing and re-setting the repeating alarm in question for the same frequency. But the AlarmManager is not firing.Basically, the nearly identical code for setRepeating() fires when set from the app and continues to run when the app is closed, so I know my AlarmReceiver is functioning, but the AlarmManager is either not broadcasting this alarm or my receiver doesn't work from an alarm set in the boot receiver.
View 9 Replies
View Related
Jan 19, 2010
I wanted to ask a question regarding the Alarm Manager. I have a requirements of setting long running timers in my application. The minimum duration for my timer is 1 hour...and the maximum may be for 4-5 days. This timer is supposed to run in the background, and when it fires/expires, i have to show something on the GUI. The timer can be re-scheduled once it fires based on user action.
What is the best approach for scheduling such long running timers ?
Should i make use of the Alarm Manager ? Or will it be an overkill ? As far as i know, alarms are retained even if the device goes to sleep and they wake up the device when the alarm goes off.
I am thinking of using a simple Java TimerTask as an alternative to setting an alarm: http://java.sun.com/j2se/1.5.0/docs/api/java/util/TimerTask.html.
But i am not sure what will happen to the timer task if the device went to sleep while the task was running.
View 5 Replies
View Related
Jun 11, 2010
I'm having some strange behavior of wakeup alarms scheduled by AlarmManager in Motorola Milestone (Droid in US). The thing is that they don't wake the device as they should. The same piece of code works fine in Samsung Galaxy and the alarms are fired as they should fire. In Milesstone when the device is in sleep no alarms are fired but all the alarms are fired at once when the device wakes up. I also found out that Milestone doesn't have the /proc/wakelocks file to check the wake lock info but I'm not sure if that has something to do with the problem. For this scenario there is no reason to acquire a wakelock because the AlarmManager acquires it automatically for lifetime of the OnAlarmReceive. I found some other threads about the same problem in Droid/Milestone, but does anybody have an idea what is the problem and is there anyway to solve it.
This is the code that I'm using to test this.
CODE:................
View 2 Replies
View Related
Oct 30, 2009
I have a question about the background thread handling change that went into SDK 1.6. I read here that BG threads get placed in a scheduling class that can't use more than 5-10% of the CPU in order to keep the foreground responsive. Do system services get into that scheduling class?
My app uses repeating alarms. It was great with 1.5, very reliable. Since the upgrade to 1.6, the phone seems to be dropping some of my repeating broadcasts, especially if I am doing something fun in the foreground like with WIFI when the Alarm is supposed to fire. I do not have any of the task killer programs that have been a hot topic lately. To be clear, the dropped alarm broadcast behavior is intermittent. I am not 100% sure if I really am doing something when it has failed. If the timer is a one shot, it seems to work better but there is no real empirical evidence here. My phone is usually in my pocket when I fire one of the one shot alarms. If my theory about system services in the background scheduling class is correct, then I probably cannot find a workaround or defensively code a solution. Will it be the same in 2.0?
Have others seen issues with alarms and with the setRepeating method? I am looking for suggestions to troubleshoot this problem. How can I determine if the problem is the broadcast, if it is the repeating alarm creation, or if there is some other issue like low memory coming in to play.
View 13 Replies
View Related
Aug 27, 2010
I am trying to create authentication system which pops up the login window if the device has been off (SCREEN_OFF) for more than INTERVAL.
I have registered a BroadcastReceiver to listen to SCREEN_ON/OFF events in the onCreate() of the launchable activity:
code:..............
When the alarm goes off, the program crashes:
code:..............
View 1 Replies
View Related
Jun 17, 2009
Is there a recommended way of resetting these alarms? The only way i can think of is registering a receiver for boot time, have it re-read the database and recreate the alarms but that seems so overkill. Why on earth would they be designed to be cleared on reboot?! :/
View 4 Replies
View Related
Nov 10, 2010
I've read comment that the AlarmManager in a earlier API version couldn't start services. Prior to which API Level was that?
I'am currently testing in the emulator with API Level 4 and it start a service just fine.
View 10 Replies
View Related
Mar 17, 2009
I read that the AlarmManager looses all registered intents if case the application that registered those intents is upgraded.What is the correct approach to re-register those intents considering the user does NOT start the application after upgrading it?
View 8 Replies
View Related
Jun 27, 2010
I want for an event to fire every hour (at 5:00, 6:00, 7:00, etc...).
I tried with a persistent background service with a thread but it wasn't the right solution because of:
battery consumption
service termination, due to android memory management
So I'm trying with AlarmManager. It works if I set an alarm to fire in X seconds (using "set" method).
But how can I repeat an event (using "setRepeating" method) at the top of every hour, until the alarm is canceled?
View 1 Replies
View Related
Nov 18, 2010
I'm trying to schedule my alarm manager to fire up an intent every hour in a day. this is what I do , and it doesnt work properly.
code:
new code after edit:
CODE:.................
View 1 Replies
View Related
Dec 8, 2009
Thanks to TasKiller I have reliable way to shutdown updates coming to my AppWidget from the AlarmManager! Now, sarcasm aside, how do I recover from such event? So far I only see that the Alerts are resurrected only after rebooting the phone. I can stick recovery code into few places such as various Activity#onCreate that belong to my app and my widget but is there a better way? Also what if the alerts are OK - is there a way to detect that and not run AlarmManager#setRepeating? Or is there a harm to run it multiple times?
View 1 Replies
View Related
Jul 20, 2009
I am trying to create AlarmManager in BOOT_COMPLETED BroadcastReceiver.
It is NOT working, AlarmManager Receiver is never fired.
BootReceiver:
code:......................
View 3 Replies
View Related
Mar 24, 2010
I have a Service/AlarmManager set to go off ever hour; as seen at: http://github.com/commonsguy/cw-advandroid/tree/master/SystemServices...
The Alarm triggers a Socket connection to communicate with a Web Server. I'm logging the interaction to a file so I can see it later. When I leave the phone on my desk for a day, it seems that more often than not I get a "Network unreachable" error when trying to do any networking.
I believe it is related to how deeply the phone goes into sleep. Is there a special kind of lock I have to hold, or some command required to prep the wireless radio so that it can be ready to access the Internet?
View 21 Replies
View Related
Oct 19, 2010
I want to add an alarm, so I used the following code...
View 1 Replies
View Related
May 30, 2010
I need to run a service each night at midnight. I would like to use the AlarmManager to do this. Can you give me some guidance of how to make it work correctly?
View 1 Replies
View Related
Nov 18, 2010
If I use the AlarmManager to schedule an alarm (a PendintIntent which should be send), how can I identify that alarm later to cancel it? Can I cancel all alarms scheduled by my app?
View 1 Replies
View Related
Sep 12, 2010
I use an AlarmManager to run a Service which tries to download a file from the web. If it fails I'd like to retry that Service in 5 minutes.
Inside the Service I run an AsyncTask to run my code. As far as I know the only way I can tell if it failed or not is from the onPostExecute().
What is the best way of implementing a retry of that Service again?
View 1 Replies
View Related
Apr 10, 2010
In my android app, I'm setting an alarm that I want to occur repeatedly, hence using AlarmManager.setRepeating().
I don't want to keep track of whether the alarm is set myself (sounds like a bad idea that's prone to fail at some point), and there seems to be no API support for checking whether a particular alarm is already set for a given Intent.
Hence, I am pessimistically resetting the alarm each time my app activates:
alarmManager.cancel(pendingIntent);
...
alarmManager.setRepeating(..., pendingIntent);
Question: is calling setRepeating() idempotent i.e. do I need to explicitly cancel() any prior alarm or can I safely just call setRepeating() and be done with it?
View 1 Replies
View Related
Feb 9, 2009
I'm looking for a way to trigger repeated actions. I'd like the user to be able to choose the intervals at which these actions will be executed. One should be able to choose from intervals like "Every Day", "Every Month", and "Every Year". The setRepeating(int, long, long, PendingIntent) method of the android.app.AlarmManager class only supports a long value for choosing the interval between the execution of the pending intent. My problem now is, that I can not just compute the number of milliseconds that "fit into one day", since not all days have the same length (daylight saving). This is also a problem for the interval type "year" (leap years).
I had a quick look at the android.os.Handler class, but as I understood the documentation I'd need to keep a service thread running for my actions to be executed at some future time. I don't consider that a good option for my needs ;-) Is there anything in the API I could configure with a cron expression or the like? I was also thinking about scheduling an alarm with the AlarmManager for a single execution at a given date/time and then having a receiver that does the rescheduling according to a cron expression attached to the intent. But I don't know if I just got something completely wrong here and I'm reinventing the wheel with that approach
View 2 Replies
View Related
Apr 25, 2013
So I've noticed that my phone pretty much never sleeps, and the battery drain is substantial. I installed Wakelock Detector and have narrowed the culprit down to the AlarmManager service in the Android System. I understand that this service itself is not the problem as it's simply used by other apps to keep the phone awake, but I have no way of narrowing down which apps are triggering the alarms. I understand it's possible by running sysdump alarm > file.txt from the terminal, but I've tried that and realized this requires root privilege, which I don't have.
View 24 Replies
View Related
