| a71febe2aaa2796cde538aa21c3e2ff006e7d3f3 |
22-May-2017 |
Winson Chung <winsonc@google.com> |
Fix issue with aspect ratio not applying correctly when PIP is expanded
- The current code always used the default min edge size to calculate the
PIP bounds when the aspect ratio changes, so if a PIP app sets the aspect
ratio in response to the an action, the bounds would be resized down
incorrectly.
- This CL fixes the issue with current aspect ratio not being initialized
correctly, and also ensures that SystemUI always updates the min edge
size when expanding the PIP.
Bug: 38324839
Test: android.server.cts.ActivityManagerPinnedStackTests
Test: go/wm-smoke
Change-Id: Ida0f68b2f8f93f9bf1915dda8762a156704d4709
ctivityTestsBase.java
|
| cb2b2ef73cd245b61292d2f8b524dc2da40df99e |
19-May-2017 |
Sudheer Shanka <sudheersai@google.com> |
Skip ConnOnActivityStartTest and CoreSettingsObserverTest.
- ConnOnActivityStartTest is consistently failing because the device
doesn't have network connectivity. This test probably needs to be moved to a
different test suite but for now just skipping the tests.
- CoreSettingsObserverTest is failing because the test depends on a mock
settings provider but since the Settings class caches the provider
object, the test will end up using real settings provider and fails.
Bug: 38432755
Bug: 38433611
Test: N/A
Change-Id: I0504d9f0df14a0f952e32c8572eefe9ccfebfd2c
oreSettingsObserverTest.java
|
| 09c529a9bc85bfd0d50b65f447472ad064eac16c |
01-May-2017 |
Makoto Onuki <omakoto@google.com> |
Reconnect to DAService after binding is dead
- When the DO/PO process crashes twice with a short interval, AM gives up
and the binding will be "died". Once binding is in this state it'll never
be re-connected.
(Still, DO/PO can disable and re-enable their DAS to force DPMS to bind again
though.)
- Detect this and re-connect after one hour.
- Back-off time will be exponentially increased and never reset until DPMS
explicitly re-connects, which happens when:
-- the device rebooted,
-- the user stopped and re-started, or
-- the DAS is disabled and re-enabled.
Test: adb shell am instrument -e class com.android.server.am.PersistentConnectionTest -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.devicepolicy.DevicePolicyConstantsTest -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.devicepolicy.DevicePolicyManagerTest -w com.android.frameworks.servicestests
Test: cts-tradefed run cts-dev --skip-device-info --skip-preconditions --skip-system-status-check com.android.compatibility.common.tradefed.targetprep.NetworkConnectivityChecker -a armeabi-v7a -l VERBOSE -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.DeviceAdminServiceDeviceOwnerTest
Test: cts-tradefed run cts-dev --skip-device-info --skip-preconditions --skip-system-status-check com.android.compatibility.common.tradefed.targetprep.NetworkConnectivityChecker -a armeabi-v7a -l VERBOSE -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.DeviceAdminServiceProfileOwnerTest
Bug 37711907
Change-Id: Ie0b227a94e6ce85d72a969a4dea1020baf734e2f
ersistentConnectionTest.java
|
| 943ebe705cece8f643d9d7ace005322ddf114d86 |
04-May-2017 |
Bryce Lee <brycelee@google.com> |
Prevent NPE in ActivityStack#shouldbeVisible.
If there is a visibleBehind activity, we check to see if the top
activity in the top stack is not fullscreen. However, it is possible
for the top stack to be empty. This can happen if the previously top
activity is being re-installed.
This changelist addresses the issue by checking if the top activity is
null before referencing it.
Change-Id: I6de904bed1c7035ed1e112c9cacc1b6c2bac4e8f
Fixes: 32180256
Test: bit FrameworksServicesTests:com.android.server.am.ActivityStackTests#testShouldBeVisibleWithVisibleBehindActivity
ctivityStackTests.java
ctivityTestsBase.java
|
| 9c844410572cd432f589d3e1c5a8ea5b67647775 |
28-Apr-2017 |
Winson Chung <winsonc@google.com> |
Fixing test due to null PiP default bounds.
- Also moving the default bounds call into the pinned stack window
controller
Bug: 37682538
Test: bit FrameworksServicesTests:com.android.server.am.ActivityStackSupervisorTests\#testReplacingTaskInPinnedStack
Change-Id: Id6608d484617ec1a596e608aab649a082b4b1e95
ctivityTestsBase.java
|
| 3345c4ea9687bb35a8c419ec21ec90b49616b2c9 |
25-Apr-2017 |
Bryce Lee <brycelee@google.com> |
Don't call adjustFocusedActivityStackLocked on finished activity.
When an activity is finished, adjustFocusedActivityStackLocked is
already called on the associated record and the task association is
lost. Calling it again is redundant and leads to a crash as we
assume the task is still associated with the activity.
Change-Id: Ie7cc9ad8b1542d7415b7409e539c88d3b4ec8dcd
Fixes: 37329424
Test: bit FrameworksServicesTests:com.android.server.am.ActivityStackTests#testStopActivityWhenActivityDestroyed
ctivityStackTests.java
ctivityTestsBase.java
|
| 5daa3121a92f5e3124b8db469aeddea269a4c1df |
19-Apr-2017 |
Bryce Lee <brycelee@google.com> |
Do not pause resumed activity in resumeTopActivityUncheckedLocked.
A number of operations occur between setting the resumed activity and
notifying the activity to resume. One of these steps is updating the
configuration, which can cause the device to pause the resumed
activity. Since the activity has not been told to resume, this leads
to a pause before resume.
This changelist addresses the issue by checking whether we are in the
middle of resuming the top activity before attempting to stop the
currently set resumed activity.
Change-Id: I3b5b61de6b1b5a35b7773912b4e63d6c69096c04
Fixes: 35637717
Test: bit FrameworksServicesTests:com.android.server.am.ActivityStackTests#testNoPauseDuringResumeTopActivity
ctivityStackTests.java
|
| 467deff7e949d99451cd74c98bfbcc11e7a7e8f0 |
18-Apr-2017 |
Bryce Lee <brycelee@google.com> |
Merge "Allow at most one pinned stack task." into oc-dev
|
| 04ab3466fabb7244660adf54740a4f60874b02a1 |
11-Apr-2017 |
Bryce Lee <brycelee@google.com> |
Allow at most one pinned stack task.
This changelist enforces only one task may be present in the pinned
stack at a time. If a task is already persent, the existing task is
moved to the fullscreen stack.
Fixes: 36844394
Test: cts/hostsidetests/services/activityandwindowmanager/util/run-test CtsServicesHostTestCases android.server.cts.ActivityManagerPinnedStackTests#testPipMovedToFullscreenStack
Test: bit FrameworksServicesTests:com.android.server.am.ActivityStackSupervisorTests#testDisallowMultipleTasksInPinnedStack
Change-Id: Iaf0fbda6df835d93738fdf6f7f3a8c5956c2b262
ctivityRecordTests.java
ctivityStackSupervisorTests.java
ctivityStackTests.java
ctivityTestsBase.java
|
| 0da67d661e20a3361f0ee4f10a19d1b8edf5e73d |
17-Apr-2017 |
Adrian Roos <roosa@google.com> |
AppErrors: Add test for AppErrorDialog.onCreate
Also refactor to make sure we always remove the TIMEOUT
message and clear the mProc.mCrashDialog field, even when
dismissing without the Handler.
Bug: 37351370
Test: runtest -c com.android.server.am.AppErrorDialogTest frameworks-services
Change-Id: If9fb348e8ed83c6c1c0f48fa7fd27ffd33b530f2
ppErrorDialogTest.java
|
| 840c566d13b8c84ad5edb37006176d6731bad250 |
13-Apr-2017 |
Bryce Lee <brycelee@google.com> |
Remove window container from empty task when destroying.
Previously, the window container was being removed whenever we were
removing the task in a destroy mode. However, this caused issues
where an activity may still be present in the task record, leading to
a subequent change to limit this to tasks with overlays. This led to
the situation where the window container would not be destroyed when
it was supposed to, such as moving an activity to recents, but
otherwise destroying.
This changelist addresses the issue by always removing the window
container from tasks when removed from their parent stack in a
destroy mode and empty. In the recents flow, this will fire and
cleanup when the activity is destroyed.
Change-Id: I87548d6ff8e4d77b6294504d7cc78370cd5d31fa
Fixes: 37301159
Test: bit FrameworksServicesTests:com.android.server.am.ActivityStackTests
ctivityStackTests.java
ctivityTestsBase.java
|
| d17ebaba9acfdd2e730a504f9a2bd27c099d2b70 |
07-Apr-2017 |
Sudheer Shanka <sudheersai@google.com> |
Merge "Fix testWaitForNetworkStateUpdate." into oc-dev
|
| cfeb32287a5882a1c0fcbb26e58953e8b234c899 |
06-Apr-2017 |
Sudheer Shanka <sudheersai@google.com> |
Merge "Don't populate a setting instead of defaulting to 0 when not set." into oc-dev
|
| 343715b1c195dc08bce4157bdfb58403679aa9e5 |
06-Apr-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Do not stop lock task if it is starting background user" into oc-dev
|
| 18498714fe22c62de461179aba3f08195db17e5f |
05-Apr-2017 |
Bryce Lee <brycelee@google.com> |
Remove accidental debugger wait.
Test: bit FrameworksServicesTests:com.android.server.am.ActivityStackSupervisorTests
Change-Id: I129b139a14d925221f2c9b614f45aedac1f153b5
ctivityStackSupervisorTests.java
|
| 5c2cf03f5f8e26f715931370004d21ee217edcde |
03-Apr-2017 |
Tony Mak <tonymak@google.com> |
Do not stop lock task if it is starting background user
We do not switch user when starting background user, so no need to
stop lock task.
Refactor a bit to make unit test possible.
Test: runtest -x frameworks/base/services/tests/servicestests/src/com/android/server/am/UserControllerTest.java
Test: Lock an app using TestDPC, creating work profile, lock task is not dismissed
Bug: 35591838
Change-Id: I52c1f6ba07860df9266462750bf953a002f69026
serControllerTest.java
|
| 081d2ccd520bc84e5fe3f9724519489242716321 |
05-Apr-2017 |
Bryce Lee <brycelee@google.com> |
Merge "Do not try to restore a task id if it does not exist." into oc-dev
|
| 3115bdf15af01ea43c28e1251657c7154e9acc91 |
05-Apr-2017 |
Bryce Lee <brycelee@google.com> |
Fix ActivityRecordTests.
Tests are not guaranteed to run on the same thread as setup methods.
Therefore, we must ensure any loopers used are already created by the
time the test runs. We do this now by creating a HandlerThread and
referencing its Looper later. Loopers are initialized per
HandlerThread, which will allow us to both isolate its usage and
guarantee the Looper initialization by test time.
Change-Id: If15494783959e5c399375033253cef69b921ff84
Fixes: 36916522
Test: bit FrameworksServicesTests:com.android.server.am.ActivityRecordTests
ctivityRecordTests.java
ctivityTestsBase.java
|
| 4cb9b96d596ca10e298a6398893b773dab1a16c4 |
05-Apr-2017 |
Wale Ogunwale <ogunwale@google.com> |
Disable presubmit for ActivityRecordTests
Failing in CI
Test: ActivityRecordTests
Bug: 36916522
Change-Id: Id5571b722cc5c14f2897fcc65d52d35bf4a78105
ctivityRecordTests.java
|
| 9d3f668d09dea3e8f14094c2efae9fdd7ce25908 |
05-Apr-2017 |
Sudheer Shanka <sudheersai@google.com> |
Fix testWaitForNetworkStateUpdate.
Bug: 36899583
Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services
Change-Id: I9fd94bc74403b173770dd7ec2483780bf6698640
ctivityManagerServiceTest.java
|
| bce47223cb6e178fe3a2547974c93f32548c12ed |
03-Apr-2017 |
Sudheer Shanka <sudheersai@google.com> |
Don't populate a setting instead of defaulting to 0 when not set.
Currently in CoreSettingsObserver while populating settings, when a
setting is not found, it's value is defaulted to 0. Instead don't
populate the setting when it is not found.
Bug: 34735550
Test: runtest -c com.android.server.am.CoreSettingsObserverTest frameworks-services
Change-Id: I9d231330c6db2636e4aa2f0caae455ddfc3e63a2
oreSettingsObserverTest.java
|
| 92b7b659393c79d5eb2ee962abaffdcc64b20790 |
03-Apr-2017 |
Bryce Lee <brycelee@google.com> |
Do not try to restore a task id if it does not exist.
Previously, we were trying to restore the recent task regardless of
if it was found in recents or a stack. This would lead to
referencing a null object later.
Change-Id: I014a751d3254ad267c32ac0b54783b31b8d17e93
Test: bit FrameworksServicesTests:com.android.server.am.ActivityStackSupervisorTests
Fixes: 36688598
ctivityStackSupervisorTests.java
|
| af691c0be7bbfea63e880dd717c51a38a0bc874a |
20-Mar-2017 |
Bryce Lee <brycelee@google.com> |
Clean up activity/stack associations.
The stack currently holds a reference to resuming and pausing
activities. These are usually cleaned up when the activity ends or
the task is reparented. However, it is possible for an activity to
lose its reference to its task in other areas (such as
ActivityStarter), which can lead to the stack not being updated
correctly.
This changelist adds a method to the ActivityStack to disassociate
the stack from an ActivityRecord. In addition to places where this is
called when an activity ends, this method is invoked on the children
of a task when the task is reparented. The task member variable of
ActivityRecord is also now surrounded by a setter/getter, with the
setter always invoking the dissociation logic on a previous stack.
Test: bit FrameworksServicesTests:com.android.server.am.ActivityRecordTests
Change-Id: Iffeccdb6f011958896271673946acfed28856f53
Fixes: 36387417
ctivityRecordTests.java
ctivityTestsBase.java
|
| f4923ea0b25edb6e6ca6804ed4c66f57a8ec29c2 |
28-Mar-2017 |
Sudheer Shanka <sudheersai@google.com> |
Don't increment procStateSeq if uid doesn't have internet permission.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services
and manual
Change-Id: I02bfd86837813cc79f37301d91489485c6a1d056
ctivityManagerInternalTest.java
ctivityManagerServiceTest.java
|
| deeb08fdcb2ccf90d013a9e909122e1a997c40bb |
24-Mar-2017 |
Sudheer Shanka <sudheersai@google.com> |
Uncomment a test.
It was commented earlier because of a crash. Since that issue has been
fixed, uncomment the test.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services
Change-Id: I5f2b1b0bffe032633f42c8c34ed8a7ae5a3dfc10
ctivityManagerServiceTest.java
|
| 5918c6700bd8e660abbf2c8f78cac5ea6a947374 |
22-Mar-2017 |
Sudheer Shanka <sudheersai@google.com> |
Update AMS to use NetworkManagementInternal.isNetworkRestrictedForUid.
And add global setting WAIT_FOR_NETWORK_TIMEOUT_MS.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services
cts-tradefed run singleCommand cts-dev --module CtsHostsideNetworkTests -t com.android.cts.net.HostsideRestrictBackgroundNetworkTests
runtest -c android.provider.SettingsBackupTest frameworks-core
and manual
Change-Id: I6949cd517255670e2ce21ab2de24271082461b11
ctivityManagerServiceTest.java
|
| 84a4895c9c1eb7f381d99fb8eb298d8335d4e480 |
09-Mar-2017 |
Sudheer Shanka <sudheersai@google.com> |
Update AMS to wait for network state update if requested by the main thread.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services
runtest -c com.android.server.am.ActivityManagerInternalTest frameworks-services
cts-tradefed run singleCommand cts-dev --module CtsHostsideNetworkTests
and manual
Change-Id: I7d1052b9941c1fae51ff8ab1c9b89dca3919ccd2
ctivityManagerInternalTest.java
ctivityManagerServiceTest.java
|
| 51ab3acf270c655ed90706895b43915433d022c7 |
08-Mar-2017 |
Sudheer Shanka <sudheersai@google.com> |
Add lastProcStateSeqDispatchedToObservers to UidRecord.
This will help in identifying the last procStateSeq for which AMS
notified NPMS about the process state change.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services
Change-Id: I741a8ffe31de92070f3ebbc9c4f95fc1c0a340cd
ctivityManagerInternalTest.java
ctivityManagerServiceTest.java
|
| e736185ee90e0f19a7092542cadab4cf561a5703 |
07-Mar-2017 |
Sudheer Shanka <sudheersai@google.com> |
Update NPMS to notify AMS when network policy rules are updated.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerInternalTest frameworks-services
runtest -c com.android.server.NetworkPolicyManagerServiceTest frameworks-services
Change-Id: I357fd5c80b7e6d3e63df95397e328c52f233958b
ctivityManagerInternalTest.java
|
| 8025580449081ddd21f449f8719bc87d1cc9fc7b |
04-Mar-2017 |
Sudheer Shanka <sudheersai@google.com> |
Update IUidObserver.onUidStateChanged to include procStateSeq.
This procStateSeq is associated with the process state change of
an uid and will help in identifying if network policy rules have been
updated for a process state change.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerServiceTest
frameworks-services
Change-Id: Iaab8d004f476b96f28d08c886c7b0a6b585b9fef
ctivityManagerServiceTest.java
|
| 4c9afa87d09a9b6abecbddc956343a70363f0c5f |
01-Mar-2017 |
Sudheer Shanka <sudheersai@google.com> |
Add tests for ActivityManagerService.dispatchUidsChanged.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services
Change-Id: Iefab4b8beab710108ba55fde8edeb578ef70349d
ctivityManagerServiceTest.java
|
| 88c4d1ce97f5fa3859dd1854d4a82305e68a2b0e |
24-Feb-2017 |
Sudheer Shanka <sudheersai@google.com> |
Add a process state seq counter to UidRecord.
This seq counter is associated with the process state in UidRecord
and will be incremented whenever the uid state is going from
background to foreground or vice versa.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services
Change-Id: I1183d929bc7e0b2c9912de3822eb344d2bb0dcf7
ctivityManagerServiceTest.java
|
| dc589ac82b5fe2063f4cfd94c8ae26d43d5420a0 |
11-Nov-2016 |
Sudheer Shanka <sudheersai@google.com> |
Update usage of ActivityManagerNative.
- Remove references to ActivityManagerProxy.
- Add isSystemReady to ActivityManager.
Bug: 30977067
Test: cts/hostsidetests/services/activityandwindowmanager/util/run-test android.server.cts
adb shell am instrument -e class com.android.server.am.ActivityManagerTest,com.android.server.am.TaskStackChangedListenerTest \
-w com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner
Change-Id: I07390b6124fb1515821f5c0b37baf6ae74adc8fa
ctivityManagerTest.java
askStackChangedListenerTest.java
|
| bd54c2aab6acc50ac415dfc4a7462d12826e8223 |
25-Oct-2016 |
Yorke Lee <yorkelee@google.com> |
Add new methods to ITaskStackListener
Refactor task change notification logic into a separate class
TaskChangeNotificationController.
Add ActivityManagerService.unregisterTaskStackChangedListener
Add a no-op implementation that clients can subclass to avoid
having to reimplement all new methods when they are added.
Add new methods:
onTaskAdded
onTaskRemoved
onTaskMovedToFront
onTaskDescriptionChanged
onActivityRequestedOrientationChanged
onTaskFinishing
Design doc:
https://docs.google.com/document/d/1IgWZ44rKe9k1CzkjP2Mohv12OgRD1FxH8oLAyzhvCY4/edit#heading=h.yhzl6os0dbo5
Cherry-picked from I8302d6d3baf1ac1ca928765fe203091b9fab4070
Bug: 32277482
Test: Verify that callbacks are called in dummy implementations
Change-Id: I2ac2b870147ef049f3ee05fc5916c99332334526
askStackChangedListenerTest.java
|
| b94292e5fe18a459aa521b9b9631d2db0485ac1b |
19-Oct-2016 |
Andrii Kulian <akulian@google.com> |
Fix NPEs when display is added or removed
- In WindowContainer set parent of the child after it is actually
added. This way if the child class depends on this in overridden
methods it will be in correct state.
- Reconfigure display only if it is attached. Otherwise there is no
corresponding DisplayContent record with configuration.
Change-Id: I20c51522d82f9d0ca98f098070585e6472a23e98
Test: Updated WindowContainerTests.
onfigurationContainerTests.java
|
| 1779e6108ab264689b7d5e5c42ba3cbca6c8189f |
13-Oct-2016 |
Andrii Kulian <akulian@google.com> |
Use ConfigurationContainer for holding configs in AM hierarchy
Extract configuration holding and handling into separate class
and use it both in hierarchy in AM.
Change-Id: I19ca20152f7473af2c4a7bbedeff69422b1454eb
Test: ConfigurationContainerTests
Test: Existing and manual tests still pass.
onfigurationContainerTests.java
|
| 7b614376bc96cae1885fd62b1e6cee39caa7b62e |
28-Sep-2016 |
Jorim Jaggi <jjaggi@google.com> |
Fix case in which onTaskStackChanged was not called
In completeResumeLocked, visibility was changed but we didn't set the
flag so the listeners didn't get notified.
Test:
runtest -c com.android.server.am.TaskStackChangedListenerTest frameworks-services
Change-Id: I4b4076a895baafc877f312d24211a2fc69a98e3b
Fixes: 31527783
askStackChangedListenerTest.java
|
| 9bf04523b49bd4493b5bb1dcdfb3bfcc60e62e41 |
09-Sep-2016 |
Winson <winsonc@google.com> |
Merge commit 'e0b767153ef978a4ca841c9891074717fd979400' into manual_merge_e0b7671
Change-Id: I6b6810db33e4b244cc872abd69d5b18a90547b35
|
| 36f3f0337de86baf8cf8a5fdd67a95e61dff4bcd |
09-Sep-2016 |
Winson Chung <winsonc@google.com> |
Revert "Fixing issue with old tasks being visible in Overview"
Bug: 28908500
This reverts commit b258f6a4bd685e5efcb36c02d5817f659e10479b.
Change-Id: I9b3c04358d6ca693ed3fdcd9220af13f81eb704e
askPersisterTest.java
|
| 70f21570bfeae8ac7b6d5e670be1e20d144f7805 |
03-Sep-2016 |
Winson <winsonc@google.com> |
Fixing issue with old tasks being visible in Overview am: b258f6a4bd am: f4806c80ca
am: 2a4cd1518e
Change-Id: I8a229f3515bebca4cd8456afae963bb97dac96d6
|
| b258f6a4bd685e5efcb36c02d5817f659e10479b |
26-Aug-2016 |
Winson <winsonc@google.com> |
Fixing issue with old tasks being visible in Overview
- This CL does two things, firstly, it ensures that all first & last
active times are monotonically increasing and independent of the
current system time. This allows us to better keep track of which
tasks are historical and should be hidden, and which are not.
Secondly, this CL moves the tracking of the last visible active time
into the system (per user) where it can be adjusted along with the
task active times when they are loaded.
- Following this CL, all active times in the future will be adjusted on
boot such that old tasks are made relative to the current boot time.
It’s not important exactly what time they are, only that they are
adjusted along with the last visible task active time so that we
always keep track of what is visible.
Bug: 28908500
Change-Id: I4f789df3a6bd825517cf3a70e26fb60deff89d06
askPersisterTest.java
|
| 888a45960a0f3b8089319a6a4f40c9be29ebf7fb |
30-Aug-2016 |
Suprabh Shukla <suprabh@google.com> |
Resolving race condition while writing recent taskids am: fd0bd4f39d am: c9e7c49def
am: e59b5664ab
Change-Id: I0a603cc99a2901147a65ded2b54e28d3545ff851
|
| fd0bd4f39deb2efdcc2f01911fc74bd5593cf6b0 |
24-Aug-2016 |
Suprabh Shukla <suprabh@google.com> |
Resolving race condition while writing recent taskids
There was a race condition, due to which, by the time
TaskPersister started writing the taskids to the file,
the user was stopped and its data from memory was unloaded,
resulting in a NullPointerException
Bug: 30944155
Change-Id: Iac3333b7744241c90a7769686983e3f16e6880c1
askPersisterTest.java
|
| 3e0c25bf099e2942ee98b908ee01f82ce5e0bc82 |
09-Aug-2016 |
Evan Rosky <erosky@google.com> |
Add UI-disabled tests for UserController
Added dispatchUserSwitchComplete and failedStartUserInForeground tests
to make sure that WM.setSwitchingUser is called appropriately.
Also set the default for UserSwitchUIEnabled to true.
Bug: 30751014
Change-Id: I9143178cb5da49c0c9524560e9fca2ab6f0d2b00
serControllerTest.java
|
| 9bc8543d45fc7f2edf857181940d3719e480a597 |
04-Aug-2016 |
Fyodor Kupolov <fkupolov@google.com> |
Added UserController tests for continuous testing
Bug: 28817048
Change-Id: Iff318652ff2a2e3c58de94b0f74d0d4ad34873b3
serControllerTest.java
|
| 3b24e5b9d06be5740383e132c02929ff9bfe8715 |
27-Jul-2016 |
Fyodor Kupolov <fkupolov@google.com> |
More tests for UserController
Tests for dispatchUserSwitch and continueUserSwitch. Added TestHandler to
record messages being sent.
Bug: 28817048
Change-Id: Ica2a8de473e5955cd7b1291c1796ee7e2f80ddb3
serControllerTest.java
|
| d6038db83d06524daa4f411081fbe48e595e7a2c |
23-Jun-2016 |
Fyodor Kupolov <fkupolov@google.com> |
Added unit tests for UserController
Initial version UserControllerTest. So far it only tests startUser method.
Bug: 28817048
Change-Id: I56a9e1e0b7c9419402dc27204d2ee95e273e23cd
serControllerTest.java
|
| 479212cf500193db6f1cf109ee58d72885f60a74 |
30-Jun-2016 |
Jeff Sharkey <jsharkey@android.com> |
Move getRecentTasks() to ParceledListSlice.
In extreme cases the list of recent tasks can grow beyond the size
of a single Binder transaction. This change moves over to
ParceledListSlice which handles chunking any large results.
Bug: 29635557
Change-Id: Iaf1227234f5f8c9451f73a6a5c1dc89f2067f05f
ctivityManagerTest.java
|
| 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
askPersisterTest.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
ctivityManagerTest.java
|