hm... I see what you mean, but I don't like this thought... there are callbacks to the ui, and recreating the ui while the service is running would mean that i have to maintain a lot of status information in the service, which is actually not the concern of the service at all... it just does its work, and fires some events... which of course don't affect the ui if the activity is finished....
the whole android activity stack and life cycle is that flexible, that you end up programming each possibility you come to your activity (oncreate, onresume, onnewintent, onactivityresult.... ), which gets more and more laborious I think... but you are probably right.. recreate it and store important data in preferences or so... Am Dienstag, 4. September 2012 18:13:44 UTC+2 schrieb TreKing: > > On Tue, Sep 4, 2012 at 7:30 AM, roemer <[email protected]<javascript:> > > wrote: > >> Any ideas on what could probably cause the problem? > > > You have the source code ... step through and see. > > Besides that, I don't think this is what you should be doing anyway. The > fact that this Activity is the UI for a Service does not make it special. > Let it live and die as normal, binding and unbinding from the Service as > necessary, through its lifecycle. > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > > -- 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
