title: Difference between onResume() and onResumeFragments()
body: <p><a href="http://developer.android.com/reference/android/support/v4/app/FragmentActivity.html#onResume()"><code>FragmentActivity.onResume()</code> javadoc:</a></p>
  
  <blockquote>
    <p>Dispatch onResume() to fragments. Note that for better inter-operation with older versions of the platform, at the point of this call the fragments attached to the activity are not resumed. This means that in some cases the previous state may still be saved, not allowing fragment transactions that modify the state. To correctly interact with fragments in their proper state, you should instead override onResumeFragments().</p>
  </blockquote>
  
  <p><a href="http://developer.android.com/reference/android/support/v4/app/FragmentActivity.html#onResumeFragments()"><code>FragmentActivity.onResumeFragments()</code> javadoc:</a></p>
  
  <blockquote>
    <p>This is the fragment-orientated version of onResume() that you can override to perform operations in the Activity at the same point where its fragments are resumed. Be sure to always call through to the super-class.</p>
  </blockquote>
  
  <p>Does the above mean that the platform <em>guarantees</em> that:</p>
  
  <ul>
  <li>fragments are <strong>never</strong> going to be resumed (their <code>onResume()</code> not called) while executing <code>FragmentActivity.onResume()</code> and </li>
  <li>fragments are <strong>always</strong> going to be resumed (their <code>onResume()</code> called) while executing <code>FragmentActivity.onResumeFragments()</code>?</li>
  </ul>
  
  <p>If not, how can a developer correctly utilize and be vigilant regarding the above?</p>