am: 3041d49d88
* commit '3041d49d888cf0732c8aafb88d1d931b696b1d41':
document the return type of getImportance
Change-Id: I3cf45be03a8e62ca48d25d26b9b234bb9f800146
For calculating the smallest width, we need to iterate through all possible
orientations, snap the task bounds to a valid snap target and then use the
smallest width across all orientations.
In addition to that, when flinging the divider handle to the bottom of the
screen, we need to pass in fullscreen task bounds to avoid that this new
logic applies so the maximizing app only receives one configuration change.
Change-Id: I37aa9a40938517dfaf26770eb41327d76aec7c62
Fixes: 28469673
There is no useful state to be saved for these views.
This fixes a crash where we try to restore the state of an
ActionView (that shares the same ID as ActionMenuItemView).
Framework version of ag/1020805
Bug: 28110832
Change-Id: I4a09786a1c08bef1765fd8be3affb21dce296272
...but probably shouldn't.
Keep track of whether zram is being included in per-process pss and,
if so, don't add it on separately.
Change-Id: Ic945fc3deca8412272bb6019fe1be4b878cb763a
Framework edition
Fix a bug where child FragmentManagers moving too lazily into the
CREATED state and beyond caused child fragments to not be
attached/created when expected.
Bug 25019275
Change-Id: I04ff0d3bcb693178a6ee3057da591392defdbcf8
am: a625b0b597
* commit 'a625b0b5976c17d8efabcf348613db7fda3e56cf':
PopupWindow: Be more careful with FLAG_LAYOUT_NO_LIMITS
Change-Id: Ia2bb751cd9864ed10e5ee5d38c7bea4d91527b2e
The fix passes the calling userId instead of the current userId to
allow apps running as managed profiles to work.
Fixes bug 28666104
Change-Id: I9f8676ab11bd581d9e67b2b9f385036d4d3576ee
It's certainly not needed for two up, so remove the staging aspect.
Freeform resizing is currently broken because of another bug so this
can't be tested, but because we are not "shipping" it in any case
fixing the 2-up bug is more important, but it shouldn't break freeform
anyways.
Bug: 28618501
Change-Id: I6f285a714281fde50fd7328a3f8999cfa8dfb2c5
Now that we live in an FBE world, we need the user to be involved
with every package move to ensure that CE storage is unlocked. This
means that a package upgrade session that would require moving an
app between storage devices cannot be satisfied.
Bug: 27147501
Change-Id: I274d85cbed727d9185178b77bfc6cef196df17f5
When installing an APK that supports multiple ABIs, the ABI installed
can be forced to the secondary ABI [i.e. On devices that support both
32 and 64 bit variants, the 32-bit version can be forced when it's
the secondary ABI.] In this case, instrumenting the class always tried
to use the primary ABI. Instead of blindly using the primary ABI and
dropping the secondary ABI, we propagate both ABIs and make a
decision on which one should be chosen.
Bug: 28406240
Change-Id: I7ebb2fd264d2281912afd30f6d73ccb460f9cf85
This change adds
- Open/close the disambig shade with a featured app
- Open/close the disambig shade with no featured app
- User selected "Always" for the featured app
- User selected "Just Once" for the featured app
- User chose a non-featured app
Bug: 26108706
Change-Id: I4d2c99cee1a784aa1cab156939c57c83d35a4aa5
am: 56e2aeba8f
* commit '56e2aeba8fb40190dbe1303ae1d299e77e764b44':
Move Activity multi-window event logic out of the public methods
Change-Id: I7c774d19ff87c52594642f1e5f277f26a2a28b39
