That is what I've been trying to do, below is the service definition
in my AndroidManifest.xml file
<service android:name=".MDService" android:process=":remote">
<intent-filter>
<action android:name="com.episode6.android.carolla.MDService"></
action>
</intent-filter>
</service>
And I bind the service in my activity with the following call...
bindService(new Intent(MDService.class.getName()), mConnection,
Context.BIND_AUTO_CREATE);
And whenever I run unbindService(mConnection); the service still gets
destroyed.
On Nov 23, 1:52 pm, Mark Murphy <[EMAIL PROTECTED]> wrote:
> G wrote:
> > 1) When my main activity is destroyed, my service is getting destroyed
> > along with it. The service's onDestroy get's called, playback stops,
> > the notification gets cleared. How can I avoid this?
>
> Have you tried making your service a remote service, one that runs in
> its own process?
>
> http://code.google.com/android/samples/ApiDemos/src/com/example/andro...
>
> I haven't tried a remote service yet myself, so I'm not 100% certain it
> will resolve this problem.
>
> --
> Mark Murphy (a Commons Guy)http://commonsware.com
>
> Android Training on the Ranch! -- Mar 16-20,
> 2009http://www.bignerdranch.com/schedule.shtml
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
