am: 3041d49d88
* commit '3041d49d888cf0732c8aafb88d1d931b696b1d41':
document the return type of getImportance
Change-Id: I03bb7490b62e749e16a417297a672769283aebdd
...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: I84b8882069a36c8f625060cb82696660a0c9c681
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
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
am: 56e2aeba8f
* commit '56e2aeba8fb40190dbe1303ae1d299e77e764b44':
Move Activity multi-window event logic out of the public methods
Change-Id: I74706461487dde9e4f3ff3ff62be4e5778190c52
am: 9e935820b5
* commit '9e935820b5d0134d71fc5ae51001b276ab603c51':
Reducing the number of recent tasks we keep.
Change-Id: If44266c1872505f90cb8ae60c6a8fbdbca495d6e
am: f2cbf95b6b
* commit 'f2cbf95b6b48d0c5dea14db4edbd255ff751beaa':
Sum up character widths to get the last line width for ellipsis.
Change-Id: Iaa3cab4dfb904c0291e703eca9125aef0ef50f70
am: f829c1463b
* commit 'f829c1463b4805545d15924ad6243b9405eb83d6':
Revert "Two phases to set the password for disk encryption"
Change-Id: Ic57b08d344020d9705a4bc2208b4adabebbe9151
am: dc5f558640
* commit 'dc5f558640da8785fabc274167ec37a0fda30cd6':
Addressing API council comments on NetworkStatsManager.
Change-Id: I952e69e7cfbd8cebcbac7c3b19ede300e26777e8
- This should decrease the time it takes to fetch the recent task list,
and also reduce the number of tasks we store on-disk.
- Since a user can still open a fair number of tasks within the
time-window, and this list includes tasks that are excluded from the
UI, we are just reducing it to about half for the time being.
Bug: 28318359
Change-Id: Ie21b3d3d09a567007015fbbecaf914123c71cc06
Instead of making multiple calls into the Bluetooth service,
make one call that can timeout. This helps prevent cases
when the Bluetooth process hangs and the system_server is calling into
it and causes a WATCHDOG restart.
Bug:28658141
Change-Id: I37778b7b6e508be420a21bdf23593ae89b38f5b8
If we intend to clip to the screen we can't pass NO_LIMITS.
Luckily the default behavior for LAYOUT_IN_PARENT_FRAME is to not
clip to the parent frame, so we don't have to do anything except
update our local flag we use for explicit size calculations.
Bug: 28194524
Change-Id: I1465efce7f5412cf646bccd83e23a4b049f4dbc4
