I agree. If you are starting the service by binding to it with the
activity, once the activity goes away the bind will go away and the
OS will think there is no reason to keep the service up.
If the service was started using a pending intent from the activity,
the service then is started by the
I know this thread is talking a lot about task management. I think
the original post was about making alarms that still occur even if the
app is closed. This is how I do it:
1) Use AlarmManager service to schedule PendingIntents in the future
(I.e. xx min from now)
2) Creat an
:34 pm, Jason B. jason.ba...@gmail.com wrote:
Using that approach works great for my app. That way it doesn't
matter if my app ever gets killed. The alarm will trigger in the
future and the intent will restart my service
I believe the point of this thread is that Task Killer apps will kill
I had this problem with both XP and Vista. I can't remember the exact
label but here is what I did to eventually solve it:
1) Install the Android SDK (the \android-sdk-windows-1.5_r3\usb_driver
\x86 folder has usb drivers)
2) Connected my G1 via any USB cable (used a couple different ones,
do this, since
if the first PendingIntent hasn't actually been used yet, and you try
to create another one to be used later, it will match and grab the
first and modify it, effectively getting rid of the first logical
PendingIntent that would have been used.
Jason
On Sep 26, 6:59 pm, Jason B
time for setData().
Lee
p.s. also see the flags you can use at the end of the getService call
(read
the PendingIntent docs). There's something like
'FLAG_REPLACE_CURRENT'.
On Sep 25, 9:39 pm, Jason B. jason.ba...@gmail.com wrote:
Hi,
I'm creating an intent that I'm pushing
Hi,
I'm creating an intent that I'm pushing to the AlarmManager so that a
service will be run at a later time. I have a single string value I
need to pass with the intent so the service knows what to do when
it's onStart() is called.
Here is the code that sets up my intent and pushes it to the
7 matches
Mail list logo
