Reconcile with ics-mr1-release

Change-Id: I72d3a620244c39d998bc58eab247181f6593809c
am 7dc96cc2: SDK only: fix up support documentation and visibility.

* commit '7dc96cc2410f551eefaa973ddc144146ad72d1ec':
  SDK only: fix up support documentation and visibility.
Reconcile with ics-mr1-release

Change-Id: I1af457406f7df8450f7c66d354b7b9ce8dab0fac
Do not dispatch context selection events to non-visible fragments.

When used in a `ViewPager`, fragments that are present on the adjacent,
cached pages will receive context selection dispatches which, depending
on your fragment contents, can be difficult to determine whether or not
the event truly originated from your view.

By using the visible hint we restrict dispatching to only those fragments
which are marked as being visible. Since the fragment pager adapter
updates this setting properly most implementations will be afforded this
fix without any change required. If the user is implementing their own
adapter they likely already understand the implications of these cached
fragments and the reponsibility for updating the boolean falls to them.

Change-Id: Ie6a72c1c82c2784774373670007b6f5948fe16da
Fix potential NPE when saving fragment state.

If a fragment's saved view state is null and the user
visible hint is true then the `result` bundle will have
never been initialized to a value resulting in a
`NullPointerException`.

Change-Id: I8ba585bc6b9298841490d64bc22a8219cd261adb
Fix NPE in `onActivityResult` when target fragment no longer exists.

If an activity result comes in which originated from a fragment that
can no longer be found an attempt is still made to call a method
on the instance. The check for null already existed to produce a
logging statement but the subsequent method call was not placed
into an `else` result in the attempt to call being made every time.

Change-Id: I0378d516a16e511a6195608243c049b1cb50a8c8
am f2fed0f2: Build android-support-v13-ics-mr1 against SDK 15 (ics-mr1).

* commit 'f2fed0f23e5d00ed1c65f3dce567edee1a67a5ce':
  Build android-support-v13-ics-mr1 against SDK 15 (ics-mr1).
am a4613df9: Merge "DO NOT MERGE - Add ShareCompat to the support library." into ics-mr1

* commit 'a4613df91aa2b505bcf59bc3f8874e77aeed9a0a':
  DO NOT MERGE - Add ShareCompat to the support library.
am 82c3b869: Merge "Add app navigation helper code to the support library." into ics-mr1

* commit '82c3b869777603fb566abdcf96369f5339c0c562':
  Add app navigation helper code to the support library.
am 7ac4b376: Don\'t have ShareCompat.IntentBuilder start for result by default.

* commit '7ac4b376371e890eb19838249e6749f64d707ad2':
  Don't have ShareCompat.IntentBuilder start for result by default.
Reconcile with ics-mr1-release

Change-Id: Ifa3235da400e5d573cbdbb9b50294eaed62815f5
am 97b3c54f: Make FragmentActivity#supportInvalidateOptionsMenu public.

* commit '97b3c54fa1e1d75a87fd2429606c615894953946':
  Make FragmentActivity#supportInvalidateOptionsMenu public.
Reconcile with ics-mr1-release

Change-Id: I8022da6fd2a058b11d902d84238eb031d5666c95
Support setNumber(int) in NotificationCompat.Builder

The "number" parameter was ignored in NotificationCompatHoneycomb, so it does not get displayed in the notification. This simply calls through to the native Notification.Builder#setNumber(int) method.

Change-Id: Ic867efa6f4b4b79fa64723443e0df2045f262d01
Signed-off-by: Scott Kennedy <skennedy27@gmail.com>
Merge "Support setNumber(int) in NotificationCompat.Builder"
Merge "Fix NPE in `onActivityResult` when target fragment no longer exists."
Merge "Fix potential NPE when saving fragment state."
Merge "Do not dispatch context selection events to non-visible fragments."
Merge https://github.com/android/platform_frameworks_support into ics