Or put together an app that would allow a user to see and kill existing running services. Maybe it's just me, but this seems like a no-brainer and would allow users (not just devs) to identify apps that keep useless services running and slow down the phone's performance. Of course I say this with no clue of the amount of work involved, but it still seems like a worthwhile endevor. A utility that allows the user to disable services that launch on boot seems like it would also be a useful (if not necessary) addition.
On Nov 24, 7:20 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Locale needs to run in the background all the time. It puts an icon in > the status bar. Please do not eliminate light location aware and time > aware services that show presence in the status bar. That would make > the phone a lot less helpful. > > There is room at the end of the boot process to list 3rd party > processes that start at boot allowing the user to discard any not > desired. Asking a user to start every background process at boot is > vista like. A picture of third party additions to the 'autoexec' > file, that dissolves if not 'touched' in 3 seconds, is gently > informative. please consider doing it this way in the next SDK? > > On Nov 24, 4:32 am, Guillaume Perrot <[EMAIL PROTECTED]> wrote: > > > We use startService in our application to keep the xmpp connection > > alive when the user exits the main activity so that he can be notified > > of incoming messages or other events. > > We an option in the settings to deactivate the background service > > (e.g. the service and the xmpp connection will be closed once the main > > activity is destroyed if this option is enabled). > > It may be a good practice, isn't it ? > > > On Nov 24, 5:22 am, G <[EMAIL PROTECTED]> wrote: > > > > Don't worry, apps that leave services running is a pet peeve of mine > > > too. Making sure my service stops when it's supposed to is a priority > > > of mine. > > > > On Nov 23, 7:47 pm, "Dianne Hackborn" <[EMAIL PROTECTED]> wrote: > > > > > Please please please be sure to stop the service when it is no longer > > > > needed. For a media player, this generally means only having it in the > > > > running state when it is actively playing music; otherwise it should > > > > only be > > > > needed when there are clients bound to it. > > > > > If you don't stop your services, then the system has to assume it is > > > > needed > > > > forever and can't remove your process to allow for other things the > > > > user is > > > > actually doing. I think this is actually one of our biggest third party > > > > application issues, applications that just starts a service and never > > > > stops > > > > it. This sucks for the user, and just should not be done. In fact > > > > there is > > > > already code in the system to look for services that have been running a > > > > long time without others doing things to them to let them be killed, but > > > > it's pretty clear we'll need to be even more brutal about this. :( > > > > (Which > > > > sucks for things that really do want to run for a long time, like a > > > > media > > > > player, but it's not clear at all to me what to do about them.) > > > > > Also, there was a suggestion earlier to try running the service in > > > > another > > > > process. Multiple processes is again something to be careful of, and to > > > > stay away from unless you really need them -- processes are quite > > > > heavy-weight entities, so shouldn't be thrown around lightly. > > > > > On Sun, Nov 23, 2008 at 12:42 PM, G <[EMAIL PROTECTED]> wrote: > > > > > > EUREKA! I've figured it out based on some of the documentation I > > > > > missed. For those who also have trouble... > > > > > > The docs for ContextWrapper.startService(Intent service) includes the > > > > > following line... > > > > > "Using startService() overrides the default service lifetime that is > > > > > managed by bindService(Intent, ServiceConnection, int): it requires > > > > > the service to remain running until stopService(Intent) is called, > > > > > regardless of whether any clients are connected to it." > > > > > > This is the trick, simply run startService() before you attempt to > > > > > bind to it! So before, my onCreate contained: > > > > > bindService(new Intent(MDService.class.getName()), > > > > > mConnection, Context.BIND_AUTO_CREATE); > > > > > > Now this has been replaced by: > > > > > Intent i = new Intent(MDService.class.getName()); > > > > > startService(i); > > > > > bindService(i, mConnection, Context.BIND_AUTO_CREATE); > > > > > > After that change, calling unbindService(mConnection) does NOT destroy > > > > > the service :) > > > > > > So starting a service by binding it from an activity links the > > > > > service's life-cycle with that of the activity. While starting the > > > > > Service first, gives it it's own lifecycle, and you can still bind to > > > > > it right after. (And you still know the service will only actually be > > > > > started once.) > > > > > > Also, doing this seems to have alleviated my 2nd problem that I > > > > > described in my 1st post, but this requires a little more testing > > > > > before i can confirm it. > > > > > > On Nov 23, 3:09 pm, G <[EMAIL PROTECTED]> wrote: > > > > > > I just realized that the in API Demo for Remote Service Binding, the > > > > > > service is destroyed when the activity is destroyed as well. So it's > > > > > > no help in this case. Can anyone point to a code sample in which a > > > > > > service outlives it's binding in an activity? Do I need to use a > > > > > > BroadcastReceiver or something? I'm very confused :( > > > > > > > On Nov 23, 2:46 pm, G <[EMAIL PROTECTED]> wrote: > > > > > > > > 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, 2009 > > > > >http://www.bignerdranch.com/schedule.shtml > > > > > -- > > > > Dianne Hackborn > > > > Android framework engineer > > > > [EMAIL PROTECTED] > > > > > Note: please don't send private questions to me, as I don't have time to > > > > provide private support. All such questions should be posted on public > > > > forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
