On Aug 15, 1:49 pm, Mark Murphy <[email protected]> wrote: > Christine wrote: > > The Service then uploads the file. > > In a background thread?
In its own thread. The activity just kicks the Service using AIDL, basically just handing it a filename, then continues with handling the UI. The AIDL call posts a task in the service which does all the uploading and stuff. I think - but I need to do more testing - that unbinding from the service right after the aidl call solves the problem, but then I lose the callbacks. > an empty call, with no effect. > > What do you mean by this? I thought that if anything in my code in the aidl call may cause a handle to be maintained between the service and the activity, this dependency should disappear if the call basically doesn't do anything, doesn't even refer to a property. Just to test. > You can give a background thread a different priority, Yeah, well, the whole thing of using a service is that it's in a separate thread and that it doesn't stop when the activity pauses or stops or gets destroyed. But maybe I should try forking a separate thread from the service with a lower priority. Thanks for the reply. Christine > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android App Developer Training:http://commonsware.com/training.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 -~----------~----~----~----~------~----~------~--~---
