You can check out how I handle AsyncTasks and orientation changes at code.google.com/p/shelves. There are various ways to do it, the one I chose in this app is to cancel any currently running task, save its state and start a new one with the saved state when the new Activity is created. It’s easy to … Read more
You should checkout this answer: https://stackoverflow.com/a/10406894/347565 and the link to google groups it includes. I had a similar problem as you, still unclear why it is not working, but I changed my code like this and problem is gone: ASyncTask<Void,Void,Void> my_task = new ASyncTask<Void,Void,Void>() { … }; if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.HONEYCOMB) my_task.executeOnExecutor(AsyncTask.THREAD_POOL_EXECUTOR, (Void[])null); else my_task.execute((Void[])null);
It is a very good question, it takes time as an Android Programmer to fully understand the issue. Indeed AsyncTask have two main issues that are related : They are poorly tied to the activity life cycle They create memory leaks very easily. Inside the RoboSpice Motivations app (available on Google Play) we answer that … Read more
All AsyncTasks are controlled internally by a shared (static) ThreadPoolExecutor and a LinkedBlockingQueue. When you call execute on an AsyncTask, the ThreadPoolExecutor will execute it when it is ready some time in the future. The ‘when am I ready?’ behavior of a ThreadPoolExecutor is controlled by two parameters, the core pool size and the maximum … Read more
My bet is that you forgot to give your app the permission to use the internet. Try adding this to your android manifest: <uses-permission android:name=”android.permission.INTERNET” /> <uses-permission android:name=”android.permission.ACCESS_NETWORK_STATE” />
Just discovered that AlertDialogs‘s boolean cancel(…); I’ve been using everywhere actually does nothing. Great. So… public class MyTask extends AsyncTask<Void, Void, Void> { private volatile boolean running = true; private final ProgressDialog progressDialog; public MyTask(Context ctx) { progressDialog = gimmeOne(ctx); progressDialog.setCancelable(true); progressDialog.setOnCancelListener(new OnCancelListener() { @Override public void onCancel(DialogInterface dialog) { // actually could set running … Read more
AsyncTask manages a thread pool, created with ThreadPoolExecutor. It will have from 5 to 128 threads. If there are more than 5 threads, those extra threads will stick around for at most 10 seconds before being removed. (note: these figures are for the presently-visible open source code and vary by Android release). Leave the AsyncTask … Read more
You can override the constructor. Something like: private class MyAsyncTask extends AsyncTask<Void, Void, Void> { public MyAsyncTask(boolean showLoading) { super(); // do stuff } // doInBackground() et al. } Then, when calling the task, do something like: new MyAsyncTask(true).execute(maybe_other_params); Edit: this is more useful than creating member variables because it simplifies the task invocation. Compare … Read more
I encountered this problem too, reconnecting the WiFi can solve this. For us ,we can check if the phone can resolve the host to IP when we start application. If it cannot resolve, tell the user to check the WiFi and then exit. I hope it helps.
That’s what onPostExecute() is for. It runs on the UI thread and you can deliver your result from there to the screen (or anywhere else you need). It won’t be called until the final result is available. If you want to deliver intermediate results, take a look at onProgressUpdate()