Hi everyone, I have an app that has a service with it. This service is started the first time you open the app is is suppose to run continuously in the background every two minutes. It seems that at some point though the service stops running or alarmManager stops scheduling/doing what is requested of it. Here is a breakdown of my code flow.
User opens the app,. Service is started, Inside the service I cancel any alarms that might be for this app then create a new one set for two minutes out, Once the alarm is set I call a GPS location check to get lat/lon, I then call up a .net web service to do some stuff with the lat/lon, Once text is returned I check that text for certain Items, If a certain item is found I send a broadcast out to a receiver that then creates a wakelock, starts a new intent to open an activity of my app then sounds an alarm, Right after I broadcast I call stopSelf() as well as calling stopSelf() if the text did not contain certain Items, I call finish() on the new activity I started if we go that far once the Active screen of my app is closed. The reason I think something is dieing out here is because after some point in time usually once I wake up in the morning and check the phone I no longer see my GPS icon on my droid checking every two minutes. Does anyone have any idea as to why this might be stopping at some point? Are there any tips on creating long running services like this or am I doing anything wrong in my process? Maybe I am missing something in how my Code flow should be set up as I am new to Android development. Any input/help/comments/constructive criticism would be most appreciated! Tommy -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
