Yes :-) we are going round in circles a bit! The overiding problem for me is that the behaviours I described above are causing different scenarios with my service. When I press 'back', and then return to the activity, a new connection to the service is created. Which results later in the service not being destoyed when I tell it to, because there is the old connection still hanging around. (Then, depending on user actions, I can get a leak error).
Why am I using bindService()? Well I thought I had to, I'm using an aidl file with methods implemented to get stuff from the service... On Dec 11, 6:14 pm, "Mark Murphy" <[email protected]> wrote: > > > None of that requires bindService() at all. Use startService() when the > user starts the service. Use stopService() when the user stops the > service. I have yet to figure out why you're messing with bindService() at > all -- not that there aren't reasons to use bindService(), but the pattern > you describe doesn't need it. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > Android App Developer Books:http://commonsware.com/books.html -- 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
