android-loader

I have an app with a fairly standard fragment layout. An expandable listview fragment on the left and a panel on the right that is used for different things depending on what the user chooses to do with the list on the left (displaying data, adding new data, etc). I'm using the LoaderManager (first time using loaders) with CommonWare's loaderex library as I have no need or desire to create a Content Provider for my database just so I can use a standard CursorLoader. This setup works great for displaying my list. The issue I am having is when I use the second fragment to add data to the

Are there any advantages of Loaders over Async task? Also, how to make loaders compatible for phones with Android froyo. Edit: The primary problem here is that I'm not using the native DB(SqlLite). Using the DB on development server. Obviously, I can't use CursorLoader any more. AsyncTaskLoader has no examples at all. If any, please do link. Is it a better idea to load the data required onto the local DB and then query it using CursorLoader ? Yes, Loaders are more advantageous than AsyncTask as they take care of a lot of things that AsyncTask falls short of, miserably. Screen Orientation

I want to implement AsyncTaskLoader for my custom data source: public class DataSource { public interface DataSourceObserver { void onDataChanged(); } ... } DataSource will keep list of registered observers and will notify them about changes. CustomLoader will implement DataSourceObserver . The question is how to properly notify CustomLoader since Loader.onContentChanged() must be called from UI thread but in my case DataSource operations (and calls to DataSourceObserver.onDataChanged() ) will be done from background threads. Updated with idea from Selvin tip : public class CustomLoader

Background I've heard that there are some new solutions for loading data in the background which are more recommended than AsyncTask (like loaders ). The problem AsyncTasks are great and easy to use. However, it has some limitations: The class itself has to be modified since it's limited by the number of pending tasks (about 256 or so). Of course, in a listView's adapter, I always cancel a task if it's not needed(for example when I need to update a view that was used for a different item). I also have to cancel them all (or handle in a different way) when the activity/fragment is being re

Short version: I have a fragment that maintains a ViewPager for displaying two other fragments, let's call them FragmentOne and FragmentTwo . When starting the app FragmentOne is visible and FragmentTwo is off-screen, becoming visible only as one swipes the view to the left. Normally onStart() and onResume() get invoked immediately for both fragments as soon as the app gets started. The problem I have is when FragmentOne starts a custom Loader then onResume() does not get called on FragmentTwo until it becomes fully visible. Questions: Is this a problem with my code or a bug in the Android