I\'m working on an Android app, which uses an online service, which I need to load my Fragments. Basically, I have a menu, and each button replaces a Fragment underneath. Wh
Never execute a database operation or content provider operation in the context of the main thred. sooner or later you will be running into application Not Responding errors. the ANRs are not a good practice.
Is there a way to prevent that from happening?
Yes: don't take so long on the main application thread. Use StrictMode
to identify likely culprits (disk I/O, network I/O), and use Traceview to find out what else you are doing that might be taking too long.
My app will always take a few seconds to load, because of the web service.
That should be done in a background thread.
I read on Google, that i could use AsyncTask, and finish the loading on the DoOnBackground method.. I don't know if that works, but I can't even try, because it won't let me change the view there, it throws an error about only the original thread can change the views
Which is why you update the views from the onPostExecute()
method, as is described in the documentation for AsyncTask.
You have to do changes to the ui in the onPostExecute() function of your AsyncTask.