title: How to transition from managedQuery to LoaderManager/CursorLoader?
body: <p>I'm developing an Android application that is targeting API level 8 (2.2, Froyo). I'm using a <code>ContentProvider</code> and that's simple enough, and I'm using <code>SimpleCursorAdapter</code> to fill out my list view, but I noticed in the documentation for <a href="http://developer.android.com/reference/android/widget/SimpleCursorAdapter.html#SimpleCursorAdapter%28android.content.Context,%20int,%20android.database.Cursor,%20java.lang.String%5B%5D,%20int%5B%5D%29" rel="noreferrer">SimpleCursorAdapter</a> that the flagless constructor is deprecated with the following note:</p>
  
  <blockquote>This constructor is deprecated.
  This option is discouraged, as it results in Cursor queries being performed on the application's UI thread and thus can cause poor responsiveness or even Application Not Responding errors. As an alternative, use LoaderManager with a CursorLoader.</blockquote>
  
  <p>Since I'm targeting API level 8, a <code>LoaderManager</code> isn't tied to an <code>Activity</code>. The <code>FragmentActivity</code> class in the compatibility package does this, but I'm not using Fragments.</p>
  
  <p>My question is: how exactly should I be using <code>LoaderManager/CursorLoader</code> in an app targeting a pre-11 API level? Am I forced to transition to Fragments or should I just revert back to the deprecated <code>SimpleCursorAdapter</code> constructor (but make use of an <code>AsyncTask</code> to keep it UI thread friendly, which is what the <code>CursorLoader</code> is supposed to do)?</p>