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
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.
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?
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 Relatedi have a little frontend showing a list of items that it will retrieve from a service. I want that service to be started in a separate thread.so the UI is still responding to user interaction while waiting for that service to call a callback method. What is the best way to start the service in a detached thread?
View 6 Replies View RelatedI have a service that sometimes starts applications.The problem is: if the *previous app* (any app) was recently exited via the home key, then the following message appears in the log:ActivityManager: Activity start request from 10024 stopped.And there's then around a 5 second delay before the target app (any) is launched.If the previous app was exited with the back key, there's no problem.If the previous app exited more than a few second ago, no problem.The same also occurs with a broadcast receiver (which also requires the NEW_TASK intent flag to launch an activity).I don't know if the delay was there in 1.5, but I'm assuming not since I can't find the error message in the 1.5 source code.
View 5 Replies View RelatedI have a call blocking application. It has 3 files:
1) class BlockMyCall extends BroadcastReceiver
2) class SimpleClass1 extends Service
3) PhoneBlock extends Activity
I start "PhoneBlock " Activity to call Service "SimpleClass1 ", which eventually calls "BlockMyCall" intended to block outbound calls (by setting result to "null").
I want to know if I can run the class1 from service without starting activity. If so , how?
I am starting an activity from one by passing some data in the intent. I want the next activity to call some asynchronous service (rest service) with the data from intent and show the result on screen.
View 1 Replies View RelatedI have two projects in Eclipse: service and UI client.
In onCreate in UI client I have:startService(new Intent(this, ExampleService.class));
But this fragment: ExampleService.class throws NoClassDefFoundError exception at runtime. I have installed ExampleService.apk, and ExampleUiClient.apk. Project compiles, and everything looks fine. What I am doing wrong?
Is it possible to start service from other apk?
I have a Service which tracks the location of the user. Currently, the Service boots when the application starts and stops when the application terminates. Unfortunately, if users keep the application in the background, the Service never stops and drains battery.
I would like the Service to stop when my application is not in the foreground. I was hoping the Application class would let me Override onPause and onResume handlers, but it does not have them.
I have a widget that is supposed to start and stop a service (start it when it's not running, stop it when it is). This is working fine, however, each time the service is started, my app's main activity is also launched, which I don't want from the app's manifest, it works as I want it to (without launching the main-activity, just the service), but then I obviously don't have a main activity anymore.This is how I start the service (I would assume this is the normal way, and I can't see any reference to what might cause the MAIN intent to fire).
View 1 Replies View RelatedI'm having trouble developing an app, while it works in API level 10, it does not in API level 7. I wondery why and I've been looking for a site that summarizes the differences, or the new features from one API level to another and cannot find it.
09-04 04:24:21.485: E/AndroidRuntime(6834): Uncaught handler: thread main exiting due to uncaught exception
09-04 04:24:21.510: E/AndroidRuntime(6834): java.lang.VerifyError: [code]....
There seems to be a problem with an uncaught exception and reflection, although....why does it work on API level 10?
So sometimes I'll go into my contacts and notice that some of them have the green ball lit up telling me that they are online in gtalk. Now I am not signed onto gtalk... but yet somehow I see that in my running services that GTalkService is running.
I can only assume that its eating away battery trying to see how is online and not. I certainly don't need this info unless I wish to go online myself... in which case I would actually go into the gtalk app.
ANyways, obviously i've been killing it in the running services, but it just comes back all on its own. ANy idea why or how to stop it?
Ok, so i go to check running services and i see that sprint hotspot is running. i have not started it since the day i bought the phone. i have no intention of using it, for now. why is it running and how can i stop it from starting? is it supposed to be running?
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. :)
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 RelatedI'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:..............
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 RelatedI 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