I'll try to find this out through experiments. Yes, I agree that this probably is freezing UI. But there's a problem here: this cannot be run on a spawned thread as OS may kill the process right after this call returns, thus, again, killing the saving thread in the middle!
On Thursday, July 19, 2012 5:06:10 PM UTC-4, Mark Murphy (a Commons Guy) wrote: > > On Thu, Jul 19, 2012 at 5:00 PM, Andrew wrote: > > So, basically the limit is ANR limit, correct? > > That's my guess. It's a guess, though. > > And, bear in mind that the ANR limit is merely the limit where Android > will take action to stop the bleeding. Your UI should be completely > frozen during these "several seconds", which is very bad for UX. > Anything taking that amount of time needs to be done in a background > thread (e.g., AsyncTask). > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 3.8 Available! > -- 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
