Thanks for your answers. But they are not convincing. Context.bindService() has the option of creating a "new" service if the service is not created in the first place. The life-cycle events for a brand new service should be identical. But the SDK doc disagrees and says this about BIND_AUTO_CREATE:
"Flag for bindService(Intent, ServiceConnection, int): automatically create the service as long as the binding exists. Note that while this will create the service, its onStart(Intent, int) method will still only be called due to an explicit call to startService(Intent). Even without that, though, this still provides you with access to the service object while the service is created. " Why? Or let me ask it another way. What side-effect does the bindService() implementation try to prevent by not calling onStart() with BIND_AUTO_CREATE? Or did the engineers forget to read one of their own (http://static.googleusercontent.com/external_content/ untrusted_dlcp/research.google.com/en/us/pubs/archive/32713.pdf)? doug -- 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
