Yes, I agree and even said in my original post that I was working to understand how to make that work correctly. Still would be interested to know why the manifest entry doesn't seem to be working as documented.
On Dec 31, 12:55 pm, TreKing <treking...@gmail.com> wrote: > On Fri, Dec 31, 2010 at 11:48 AM, Robert <rcope...@gmail.com> wrote: > > The reason I want to do this is that the app is accessing a webserver via > > an AsyncTask and I'd like to stop the restart until I can figure out how to > > link the background task to the new pid that is created. I've read some > > pages on it but not yet clear how to do that. > > Quoting the docs for that property: > > *Note:* Using this attribute should be avoided and used only as a > last-resort. Please read Handling Runtime > Changes<http://developer.android.com/guide/topics/resources/runtime-changes.html> > for > more information about how to properly handle a restart due to a > configuration change. > > I highly recommend you spend the time figuring out how to do this correctly > then wasting time on a hack that will cause other problems. > > --------------------------------------------------------------------------- > ---------------------- > 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
