| e5266730ebee0e8db5e7881e0e78db22f67fba7b |
|
15-Jun-2016 |
Winson <winsonc@google.com> |
Only skip trimming task if the stacks are not null.
Bug: 29121819, 29359871
Change-Id: I8f8602796e316ed5b36a033e4eaa020650064f74
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 29dbc3cc47a27ae09f0f5aacd778aded427444bc |
|
08-Jun-2016 |
Winson <winsonc@google.com> |
Prevent trimming recent tasks belonging in different stacks.
- When launching an adjacent task, we usually have the same activity
not necessarily launched with MULTIPLE_TASK, so the old recent task
is incorrectly found removed.
Bug: 29121819
Change-Id: Id3bbafe0d3c535fd1a05bb373e521345c18f43d5
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 6976f7bae901d81a354287088ae232ba7236f30e |
|
03-May-2016 |
Winson <winsonc@google.com> |
Disabling movement of entire affiliated task set.
- This CL removes the dependency on the last-active-time of the task
record, since that is dependent on the current system time (which can
be changed by the user). Instead of working around the previous
behavior in ActivityManager which moves all affiliated tasks to the
top when one task is launched, we change the behavior in the AM
directly, and prevent re-sorting the list of recent tasks improperly
(aside from the stable sort which puts the freeform tasks first).
Bug: 27398177
Change-Id: I9fa9b3497d08082fe00aa724538255de87e746d6
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| e8d5f650413dd6e0043f7dcb2e41bbb5df9832fb |
|
23-Apr-2016 |
Wale Ogunwale <ogunwale@google.com> |
Allow multiple recent entries for task with FLAG_ACTIVITY_MULTIPLE_TASK
The caller wants multiple task in this case regardless of if it is the
same activity or intent filter. So allow it.
Bug: 28293748
Change-Id: I97f7900657975291f301cb4dc0a8af93ff6b70ea
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 07317df6ab3577a215f5fcbb8076d7e1d9c94e04 |
|
18-Mar-2016 |
Suprabh Shukla <suprabh@google.com> |
Merge "Added a unit test for TaskPersister" into nyc-dev
|
| f50b458e7107d23483d8c6ba1121d921773e45c6 |
|
24-Feb-2016 |
Suprabh Shukla <suprabh@google.com> |
Added a unit test for TaskPersister
Added a simple unit test which checks the methods used to save and load the set
of taskids to file. The test creates a user, adds some task ids to the
set of taskids for that user, saves it and loads it to see whether the
set loaded is the same as the one that was saved.
Change-Id: If92be8abf9a7e3ef90630a3786867f0e1ba12f3e
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| c4b46dd12d3f8846c52203a2d484a950edfa3014 |
|
17-Mar-2016 |
Fyodor Kupolov <fkupolov@google.com> |
Prevent NPE when syncing recent tasks
Temporary fix to unblock GTS tests for ryu.
Bug: 27686987
Change-Id: Id9398cd8615bf90aecf02051f26db10f39d598b0
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 4bccb46554d9fd0d7de44e069d67af970d178a0b |
|
11-Feb-2016 |
Suprabh Shukla <suprabh@google.com> |
Moving recent tasks and images to /data/system_ce
Moved user sensitive recents data to the credential encrypted directory
/data/system_ce. Since this directory is not available before the user
is unlocked, and unavailable task ids are needed to be known before
assigning an id to a new task, this change adds a file in /data/system_de
for each user, to store the ids of the tasks present in /data/system_ce.
Bug: b/24569398
Change-Id: I340d1abe23e2594e2cee4bff89a697bd8dc61fc7
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 4ccec532d704725cd6115c220f56330edf101674 |
|
13-Jan-2016 |
Andrei Stingaceanu <stg@google.com> |
Hide suspended apps from recents
* Introduce a new boolean realActivitySuspended in TaskRecord to
keep track of the suspended state (this also makes sure the
information is persisted across reboots).
* Introduce a new method onPackagesSuspendedChanged
in RecentTasks which flips the realActivitySuspended for each
TaskRecord for the desired user and packages sent
* Register a new broadcast receiver (for SUSPEND/UNSUSPEND)
in ActivityManager#finishBooting which calls
RecentTasks#markPackagesSuspendedStateForUser
* In ActivityManagerService#getRecentTasks filter out
Taskrecords for suspended apps by checking realActivitySuspended
Bug: 22776761
Change-Id: I52e3593ccb2dae223d1ea11d017a6b1626646639
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 0af6fa7015cd9da08bf52c1efb13641d30fd6bd7 |
|
18-Jan-2016 |
Amith Yamasani <yamasani@google.com> |
Voice Interaction from within an Activity
This allows an app to show a voice search button
and invoke a voice interaction session for use
within the activity. Once the activity exits, the
session is stopped.
Test application has a new activity that
demonstrates it with the test voice interaction
service.
This initial version is functional enough for
an integration test, with some more tests
and improvements to come later.
Bug: 22791070
Change-Id: Ib1e5bc8cae1fde40570c999b9cf4bb29efe4916d
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| f5bf0cb2019d25de1a514206caca3fee0f3f8bc7 |
|
20-Jan-2016 |
Suprabh Shukla <suprabh@google.com> |
Minor fixes
Added a synchronized block around a locked method call, updated javadoc
for a method in RecentTasks.
Change-Id: Ie58ac1d1755485902dbb453eb72a1291f9e65861
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 09a88f5f3e7d4a3bbfce04ac06594ac590c67d27 |
|
02-Dec-2015 |
Suprabh Shukla <suprabh@google.com> |
Keeping only running users recents in memory
Currently, all the users' recent tasks are loaded into memory and kept
in sync with the persistent storage. This changes the system so
that it loads a users recents into memory lazily (i.e. when
getRecentTasks is called for that user) and unloads them from the
memory as soon as the user is stopped. This also required bucketizing
the taskIds per user, so that the next available taskId can be assigned
without having knowledge of all the tasks that are stored away in
persistent storage but are not available in memory.
Bug-Id: b/24569398
Change-Id: Ia5cb64d9f4ee727225dce34e45ca63e946ac27a8
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| c5967e9862489024c932b0c7fcb84ed0af2a7fd7 |
|
08-Jan-2016 |
Jeff Sharkey <jsharkey@android.com> |
More progress on triaging PackageManager callers.
Catch a bunch of simple cases where the PackageManager flags are
obvious. Add the ability to use the MATCH_SYSTEM_ONLY flag on
PackageInfo and ApplicationInfo queries.
Re-examine recent tasks after a user is unlocked, since some of the
activities may now be available and runnable.
Bug: 26471205, 26253870
Change-Id: I989d9f8409070e5cae13202b47e2c7de85bf4a5b
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 7cb57e199fbe84654b6f0974e308f91963bdee35 |
|
10-Nov-2015 |
Robert Carr <racarr@google.com> |
Prevent early recent trimming of distinct documents.
Prevent early trimming of documents with distinct
intents. Otherwise when launching a document
from a given activity, existing recent entries
will always be pruned even if they are distinct
documents. We don't have to worry about overflowing
recents, a seperate codepath (from addLocked)
takes care of second pass trimming when we have
exceeded our total max recents.
Bug: 25460953
Change-Id: I71f8c3d46570df2c999f0d986e05515074e0a098
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| f63b89c0a10b4e3220b0a4aa1703be3aed0c5a98 |
|
28-Oct-2015 |
Fyodor Kupolov <fkupolov@google.com> |
UserController refactoring
Addressed comments from the previous cl. Added getters for UserController
fields, direct access is no longer allowed. Moved the following methods:
- getUserManagerLocked. Became getUserManager() - because locking is not
necessary, double checked locking will suffice.
- startUserInForeground /showUserSwitchDialog/sendUserSwitchBroadcastsLocked
- handleIncomingUser/unsafeConvertIncomingUserLocked/isUserRunningLocked/
getUsers/getProfileIds
Bug: 24745840
Change-Id: Id5a5cfb9604e08add29bd9a03c8fe5200bc51fef
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| d26e079df17e7d8f51fc0e0a652d72b9c67ee343 |
|
12-Oct-2015 |
Robert Carr <racarr@google.com> |
Ensure recent documents are trimmed when relaunching.
With respect to recents trimming, documents excercise a
a special code path, where the number of open documents
is compared to a configured max documents. In fact though
if we have mandated a trim (regardless of recents size)
we don't care about this max documents number.
Bug: 24717461
Change-Id: I2ffb4a037307d666ea0a7f31d75638b64b6eab8e
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 2ab53cf23e97468475601866bddb9c7631269d9c |
|
02-Aug-2015 |
Wale Ogunwale <ogunwale@google.com> |
Also consider task intent when trimming recent tasks
7cbfcd88657ac7d5ab1baf8c964b669c9bd21e24 we stopped comparing
the tasks realActivity when trimming recent task. This led to
task with the same intent been duplicated in the recents list.
We now consider the task intent when deciding when to trim like
we did pre 510e554283d3dc250f836cd3e4abc36d87319333.
Bug: 22812470
Bug: 22564474
Bug: 18642190
Change-Id: I90b3ab9cf7a06b4691099f697e723d8a54def9fa
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 7cbfcd88657ac7d5ab1baf8c964b669c9bd21e24 |
|
21-Jul-2015 |
Wale Ogunwale <ogunwale@google.com> |
Don't duplicate recent tasks of the same affinity.
In change 510e554283d3dc250f836cd3e4abc36d87319333 we stated
limiting the number of document activity entries in recents
by comparing the realActivity of the tasks. This compared was
done for all tasks not just document tasks there by breaking
the use of task affinity to remove tasks with the same affinity
from recent task list. This change limits the compare of
realActivity to just document tasks.
Bug: 22564474
Bug: 18642190
Change-Id: Idc21ec311f194ab2005cb22380ca56303ae0ad94
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| 510e554283d3dc250f836cd3e4abc36d87319333 |
|
20-May-2015 |
Stefan Kuhne <skuhne@google.com> |
Don't exceed max. allowed recent document tasks for an app.
We were exceeding the maximum allowed recents document tasks entry
for an application package because the full Intent object was been
compared for equality which will be different for each task. Now
we are only comparing that the task components match which is
sufficient to determining that the task belongs to the same
application package.
Bug: 18642190
Change-Id: I831b0fcffb876d51e9439e7a7a4c75bb0881db7c
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| ee006da858459e91666ae53432659e934c8a8dbd |
|
30-Mar-2015 |
Wale Ogunwale <ogunwale@google.com> |
Converted more log points in AMS to use ActivityManagerDebugConfig.
Change-Id: I59e777de30e2e9a3c7d086dc634129cd19135fab
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| e23149f1555303940d212b742707518b7f9f84ab |
|
07-Mar-2015 |
Wale Ogunwale <ogunwale@google.com> |
Converted some AMS log points to use ActivityManagerDebugConfig.
Change-Id: I0563bafd29ae0bbe596ed8c06fcc573b5ead50b7
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|
| c82f2f5f9cb1bd4f5bcbd39a8ddf0d8da84f7104 |
|
09-Dec-2014 |
Wale Ogunwale <ogunwale@google.com> |
Add RecentTasks class to house recent tasks functionality.
Cleaned-up ActivityManagerService a little by moving recent
tasks functionality to new class RecentTasks.
Bug: 18556524
Change-Id: I4c877c9695b63d7fdb1b6b7addb737fd663e86c7
/frameworks/base/services/core/java/com/android/server/am/RecentTasks.java
|