Lol, Mark Murphy, what you know is very far beyond me. I've read that it's better to use an alarm manager then to have a serice running in the backgroun because it'll keep the device awake and drain the battery.
I think I'm doing both one within the other and at the same time. SystemPanel (app) is telling me that my application is always in the 'Active Apps' running in the foreground, background or as a service.. but none the less it is never in the "Inactive" (Cached) slot.. and its ALWAYS using over 10 mb... "Lost soul" - I'll study the code more, its just beyond me at the moment and i'm trying to attain particular functionality on the user end before I start polishing everything. i'm probably one of those guys that'd benefit a lot from google's 'app inventor' because its been nearly ten years since I've played with any computer language. On Jun 17, 6:40 pm, Onomp <[email protected]> wrote: > > > I wonder if this is also what Onomp was trying to say about > > > registering them in the Broadcast Receiver. That after the > > > BroadcastReceiver is no longer running, the alarms are no longer > > > registered. > > > This too is absolutely positively not true. See the > > WakefulIntentService demo code. Manifest-registered BroadcastReceivers > > are "no longer running" as soon as onReceive() ends. > > Are you saying that the alarm is still registered but that it does or > doesn't fire with or with out the WakefulIntentService code? > > also., I use system panel to check what is running... There is a way > to have my service out of memory and the alarmmanager still > triggering?? when I end the actie, background,inactive tasks... its > typically game over for my alarm manager. -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
