am: 621b459306
* commit '621b45930610e5e4f37936a13f31ace2fe82e83c':
document the return type of getImportance
Change-Id: I9a208abe9c650f580dea705d33cd45d96d4f5825
am: 3041d49d88
* commit '3041d49d888cf0732c8aafb88d1d931b696b1d41':
document the return type of getImportance
Change-Id: I03bb7490b62e749e16a417297a672769283aebdd
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
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: 82e644de2f
* commit '82e644de2f1db76e20e676086b580e224d5d9d5b':
Move Activity multi-window event logic out of the public methods
Change-Id: I2d7e79c29cbcad62727ed701c1e7d0519deca24e
am: c4b7595962
* commit 'c4b7595962d217d07596469b378831630dd61d72':
Reducing the number of recent tasks we keep.
Change-Id: If80c8f44ebee97ff30cc858ea9edf6ec99909e3b
am: 6e90b67dfa
* commit '6e90b67dfaf02c236b542951dfaac3a7d805ef21':
Move Activity multi-window event logic out of the public methods
Change-Id: I1eb6677d8ecd2208b20c2094eb4d708f6e20bc14
am: 9fc0a7c4c4
* commit '9fc0a7c4c4e8eeddc6b4a74267731b26e87a20f5':
Reducing the number of recent tasks we keep.
Change-Id: I184a3a28a3365c897f108f93947168f228c1c235
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: 8b2dd44f2f
* commit '8b2dd44f2f30a9dd22799ee30dd4b9c5a093aae5':
Addressing API council comments on NetworkStatsManager.
Change-Id: Ie6455799758f0bdb67440f72c266effaf412e22f
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
Callbacks
- DataUsageCallback renamed to UsageCallback
- DataUsagePolicy removed; passing in params directly to register method
- making it an abstract class
- passing in (networkType, subscriberId) that reached its threshold
- renaming onLimitReached to onThresholdReached to match existing naming
- only monitor single network,subscriberId
- no monitoring of specific uids; using device or user wide instead
Tags
- only owner uid can read its tags
- exposing only TAG_NONE to match service side
BUG: 27530098
Change-Id: I2b2664da71806868a1e937d2bf4d1f234637509b
When multiple activities within the same process
try to handle requests for AssistStructure, the
singleton mLastAssistStructure tends to trash
the old structure when a second window's request
comes in.
This change passes in a sessionId so that the
cache is only cleared if the session id changes.
Bug: 28348867
Change-Id: I07efcd933db7e48aefd25a1c95493b71bbcffe4b
The white list of permitted directories is applied for every
classloader namespace by libnativeloader. LoadedApk no longer
needs to do that.
Add mDataDir to permitted paths in the case if for any reason
it is outside of the whitelisted dirs.
Bug: http://b/28639227
Change-Id: I5b61ac64e281ecee3e3e9b1fe56cf04dc6ee7b25
Move the logic for dispatching multi-window mode change events to
fragments and the activity window out of the public API onFoo methods
meant to be overridden by apps. This prevents problems if an extending
class forgets to call super.onFoo in these methods and removes the
need for doing so.
Bug 28667205
Change-Id: Ibf4c543e22b95753e1e4812bbd3e81f7648de54d
am: ad2b44c8c7
* commit 'ad2b44c8c7907a971e7437c5ccd0f823caec53fd':
Move the 'pretend idle jobs can run now' broadcast into AMS
Change-Id: I50b6ca257b7995d6a50fe938f8d4c788f739001a
am: 0588954071
* commit '058895407140de0e513b82150c3acb6131e971a2':
Move the 'pretend idle jobs can run now' broadcast into AMS
Change-Id: Id8bd50f0a5f6d46cf60dea690803081515cb21c3
am: 94d93dd38f
* commit '94d93dd38fbab0ff8f9a9ce397a522cf2fcd6429':
Dismiss docked stack if an activity is shown on top of the lock screen
Change-Id: Iaaf1dc4cd6f4008bf4bc571bb70365d431ea30ed
