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
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?
i am using a unique value (primary ID) to set an alarm. When i want to edit the alarm i am using the same key. But what i see is that both the alarms go off! original as well as edited one. how do i cancel the old alarm ?
View 2 Replies View RelatedIn 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?
I am making an event application and user can set a reminder for events he wants. So i use the alarmManager to create alarms. I would like to put a cancel all option to my main activity so that i could cancel all the alarms created by my application. The usual method for canceling the alarm with the same intent doesnt really help cause i set tha alarms on a different activity than the one I want to cancel them in. So is there a way to cancel all the alarms created by my application?
View 1 Replies View RelatedI'm writing something like a reminder for users. Users will set reminders for their events, when the time comes, a repeating alarm will be set to trigger a status bar notification. But the alarm seems non-stop after I selected the notification or cleared the notification. I am not sure where to cancel this repeating alarm. Below are some of the codes...
How can I stop the alarm when the user selects the notification or clears it?
My problem is this, I downloaded Handcent and really like it, however, I can't send messages from home. I have marginal service here (around -98 avg.) but I do get 3G. Whenever I send a message it says Message Failed - Retry, Cancel? I've even had this problem in places with great coverage for both 3G and cell service. The stock messaging app works just fine. So what I've been doing is receiving messages with Handcent and then sending them using the stock app.
So, does anyone have any ideas of what I can do? Are there any settings that can be changed? Does handcent use 3G to send messages?
I'm now trying Chomp to see if that's any better. And, just an FYI, I'm having trouble with text messages, not MMS. I haven't tried sending any pics or videos yet, I've just been sending SMS.
I m developing an application for creating , deleting and modifing Tasks with a system alarm manager.
Here is the code snippet where i start a service called 'AlarmService'. The role of this service is to create an AlarmManger and send an intent to a receiver called 'AlarmReceiver'. The role of the receiver is to send notification to the user when the alarm goes off.
[HIGH]
public class CreationTaskActivity extends FragmentActivity {
[...]
Intent intent_alarm = new Intent(CreationTaskActivity.this,AlarmService.clas s);[code]....
When i run the application on the emulator, i have this exception:
java.lang.IllegalArgumentException: Enable to start receiver
.java.lang.IllegalArgumentException:contentIntent required....
I tried several alarm clocks on my droid, and they all seem to have a problem. if I set alarms for 6:30, 6:41, and 6:52 am. Each with a different sound. If i snooze alarm 1, alarm 2/3 never goes off. i thought all 3 would be seperate, but it seems only 1 can be active at a time. unless im doing something wrong. this happens on the default alarm clock and, better alarm clock.
View 2 Replies View RelatedI 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 RelatedI 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 Relatedalarms.set(AlarmManager.RTC_WAKEUP, getTime(), alarmIntent);
I have set a alarm,but now i want to delete it? how can i make it.
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.
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.
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.
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.
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 RelatedI 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)
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. :)
I am using service class to play the mp3 file using media player object on Android platform, problem is, i am not able to handle the alarm interruption.When any previous set alarm clock reach to it's alarm time it starts to play in parallel with mp3.I want that mp3 should become paused and after alarm it again start to play,same thing should happen with snooze.
View 1 Replies View RelatedAny 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 RelatedIm creating a mail application, where i need to start a service instance for every account, which will check for the new mails for that account. Now my problem is that i want to identify how my service i have created so far (by calling startService()). And also i want to stop a specific instance of service. I know that calling stopService() will stop all the instances of that service. Is there any work around to it.
View 2 Replies View RelatedI 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.
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:................
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.
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:..............
Can anyone tell me the Android app that can identify your location and tell you what is around?
As in gas stations, food places, movie theaters, etc (3D). It was displayed on a commercial for VZW not too long ago, and I cannot find it on the Android Market place. I got my Incredible yesterday, and I love it.
As far as I'm aware the standard alarm clock will not alarm when the phone is switched off. Does anybody know an alarm clock that will alarm when the phone is switched off ...? (preferably free)
View 2 Replies View RelatedCan I send an email without invoking any activity (with Send/SendTo action)? Just compose a mail and send to recipient from my application.
View 7 Replies View RelatedIs 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