Mark and other Android experts have devoted a lot of attention to counseling against designs that have forever running services. See his link above for a whole blog on this subject and advice on alternatives.
The first issue you face is the platform can kill the process your service is running in if it needs to free memory so there is no guarantee that it will KEEP running. When lots of apps are trying to work around that by restarting their services the system will be thrashing and the user experience will be poor - leading to your app becoming one that users will consider a "problem". On Feb 22, 10:50 am, guich <[email protected]> wrote: > Hi Mark, > > Thanks for the information. > > What i was thinking to do was to write a service that was > automatically started and just keep running in the background, even > with no other intents alive. So, it would be a service-only > application; no user interface at all. It would run and, from time to > time, connect to a server, download data, and sleep again. > > guich -- 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
