First, you do not typically use both startService() and bindService(), but rather one or the other.
Second, the timing of when the binding is available has nothing to do with onResume(). You find out when the binding is available via onServiceConnected() in your ServiceConnection. This may occur before or after any other particular callback method, such as onResume(). On Wed, Mar 9, 2011 at 4:38 AM, Daniel Rindt <[email protected]> wrote: > Hello, > > i have a Problem with bind to a running service. In my activity starts > the service with startService() and after that i would bind to that > service to communicate with them. I inserted a Log.d to inspect the > behavior of the service and the service connection. My summary is that > the order is not as expected, the service is starting after the > execution of onResume in my activity. So the bind process executed > before that and fails then. > > Hopefully someone can clue me a bit. Thanks for reading. > Daniel > > -- > 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 > -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training Worldwide: http://commonsware.com/training -- 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
