| cbade7f4d3ed06636cdf0f2e2317a9e49b46852a |
|
15-Apr-2016 |
Adam Powell <adamp@google.com> |
Retain loaders through stopped config changes
Framework edition
Previously we would throw away any stopped LoaderManagers when we went
to retain instances to pass along as nonConfigurationInstances during
config changes or similar activity restarts. This causes loaders to do
more work than they need to when a calling activity starts a new
activity on top, a config change happens (e.g. screen rotation) and
then the top activity is finished, restarting the caller in a new
configuration. The loaders would go through onReset unnecessarily,
potentially throwing away data to be reloaded again after the config
change completes.
Instead of throwing away stopped LoaderManagers in this case, restart
them and retain them across the config change so they can resume where
they left off.
Bug 27176186
Change-Id: Ia52c6448d2ad41dcb25d493770d9ffae20a19d2a
/frameworks/base/core/java/android/app/FragmentHostCallback.java
|
| a0c2dc3cf56bf9c90af517f4cd12ef80d375a85a |
|
12-Apr-2016 |
Clara Bayarri <clarabayarri@google.com> |
Provide startIntentSenderForResult for fragments
Bug: 27700608
Change-Id: Ibb7689ba0527048dd5944c4315b986f16030081d
/frameworks/base/core/java/android/app/FragmentHostCallback.java
|
| 2ee19c7f46ab488f19380f4c70904a1ac00fee9a |
|
20-Oct-2015 |
Todd Kennedy <toddke@google.com> |
Retain fragment loaders
Remove the partial fix [it did not work for child fragment managers]
and replace with a more general fix that works with all fragments.
Bug: 23838271
Change-Id: I88b465f6a06a6ad627b9651b9e2eea41fae08972
/frameworks/base/core/java/android/app/FragmentHostCallback.java
|
| 970b59cbe377e23e9c681a5cef30c01f730c7377 |
|
10-Jun-2015 |
Svetoslav <svetoslavganov@google.com> |
Use who when requesting permissions
Change-Id: Id0b231f8b74099b7877eb4441a1664416c641731
/frameworks/base/core/java/android/app/FragmentHostCallback.java
|
| 434bd65ca61ff5cec46fce9fbe866d8ee40579da |
|
04-May-2015 |
Todd Kennedy <toddke@google.com> |
Call Activity#onAttachFragment()
This was accidentally removed during the changes to abstract a Fragment host.
Also ensure Fragment#onInflate(Activity) gets invoked
Bug: 20825263
Change-Id: I981266ae1e8817db5c82ec4609bbcf4a5e676fee
/frameworks/base/core/java/android/app/FragmentHostCallback.java
|
| a5fc6f006f67867417b7a427de6e7394c4312dec |
|
15-Apr-2015 |
Todd Kennedy <toddke@google.com> |
Remove dependency upon FragmentActivity
The FragmentManagerImpl is intimately tied with a FragmentActivity. In
many cases, we want to be able to create / manage Fragments outside of
a FragmentManager. This defines a FragmentController interface that can
be used by any class to host Fragments.
Bug: 19569654
Change-Id: I6816a5c1815122d206062b9f4584ad460b3d41dd
/frameworks/base/core/java/android/app/FragmentHostCallback.java
|