summaryrefslogtreecommitdiff
path: root/tests/MemoryUsage/src
Commit message (Collapse)AuthorAgeFilesLines
* Rename featureId -> attributionTagPhilip P. Moltmann2020-03-111-1/+1
| | | | | | | | | | | | | | | | | In the core functionality this changes everything including aidl's and field names: - Context - ContentProvider - AppOps* - Package parsing For the rest, this is a shallow change to only change to the changed APIs. This keeps the change small-ish Exempt-From-Owner-Approval: Rename Fixes: 148792795 Test: TH Change-Id: I2a2245fe76e09e62cb13d5785d2efb4a304ba54a
* Revert "Revert "Activity start: Send featureId from context->AppOpsManager""Philip P. Moltmann2020-02-121-1/+2
| | | | | | | | | This reverts commit e7421e92d947b09ca3cb9e6dfb66bbb27b9ed114. Exempt-From-Owner-Approval: revert-revert and only piping anyway Test: 1:1 revert-revert Bug: 136595429 Change-Id: I44e5fa2019f5604c6e2c08bdd1967129c64a90a7
* Revert "Activity start: Send featureId from context->AppOpsManager"Philip P. Moltmann2020-02-101-2/+1
| | | | | | | | | | | | | | | | Revert "Adjust monkey to changed internal APIs" Revert "Test featureId is correctly used in startActivity" Revert submission 10111030-activityStarter_featureId Reason for revert: presubmit test breakage Reverted Changes: Ic7056b492: Activity start: Send featureId from context->AppOp... I8e2a07da7: Adjust monkey to changed internal APIs I7a6af6fb1: Test featureId is correctly used in startActivity Change-Id: I48c55a962c990b22ea49e923baa7c73b121d179b
* Activity start: Send featureId from context->AppOpsManagerPhilip P. Moltmann2020-02-081-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The expected usage pattern for noteOp is to get the Context#getOpPackageName() and Context#getFeatureId() in the calling app and the call noteOp(callingPackageName, Binder.getCallingUid(), callingFeatureId) As the featureId parameter is new this parameter has to been piped all through from the ...Manager classes running in the app all way deep into the bowels of the system server. There is a special featureId==null for the "default" feature. This is used in two cases: - In case the system server (packageName == null || packageName == "android") makes a call - In the case there is no caller. In this case I left annotations in the code to make clear that the default feature is used Raw binder interfaces (defined in AIDL files) are not supposed to be used by apps. Still historically this has happened and we ended up with @UnsupportedAppUsage tags in these files. Also AIDL does not support two methods with the same name but different parameters. I.e. in the case when I had to add a paramater to a method tagged as UnsupportedAppUsage I - created a new method ...WithFeature with the additional paramter - set a maxTargetSDK for the old method and mention the public API to use in the deprecation method This is really not pretty. Once there is no more app using the old internal API this hack can be removed. Additionally this change removed all internal calls to AppOpsService.noteOperation and AppOpsService.checkOperation and replaces them with the public API equivalent. This sometimes means to move the resolution of the mAppOpsManager to be lazy. Exempt-From-Owner-Approval:: Just piping through arguments Bug: 136595429 Test: atest --test-mapping frameworks/base/services/core/java/com/android/server/am/ atest CtsAppOpsTestCases added test to cover activity start atest WmTests Change-Id: Ic7056b492cb1c9a79158e6c2b4864898a0eb5b2a
* Use real package name in MemoryUsageTestAndrii Kulian2019-07-311-2/+3
| | | | | | | | | ActivityTaskManager requires real package name to be passed to perform UID-package validation. Bug: 137395936 Test: atest com.android.tests.memoryusage.MemoryUsageTest Change-Id: Icf6ba312e9aad4018e79482fccc1d96cd51bd921
* Moved some activities implementation to ActivityTaskManagerService (2/n)Wale Ogunwale2018-06-121-1/+5
| | | | | | | | | | | | | Second step in unifying the window hierarchy that is currently split within AM and WM packages. We move some of the API implementation for activities from ActivityManagerService.java to ActivityTaskManagerService.java. Test: Existing tests pass Test: go/wm-smoke-auto Bug: 80414790 Change-Id: I23dcd924493d8ad1e0b6e3a55386fd72b0146605
* Update usage of ActivityManagerNative.Sudheer Shanka2016-11-141-2/+1
| | | | | | | | | | | - 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
* Add sample profiling option to am.Jeff Hao2014-08-261-1/+1
| | | | | | | Also bundles all profiling options into a class. Bug: 17040932 Change-Id: I85d675ee1494bdc7308caffdf94145d27c996e9d
* freeze screen rotation during memory and app launch testGuang Zhu2014-08-081-0/+13
| | | | Change-Id: I2a039be383562019a0af9470c5053cd3cb1e6142
* Add memory tracking for persistent proccesses and launcherwsmlby2014-07-241-19/+48
| | | | Change-Id: I5228bd67884dc8b77207a597f279fd4032c7f9d9
* App ops: vibration, neighboring cells, dialing, etc.Dianne Hackborn2013-02-011-1/+1
| | | | | | | | | | | | | | | | | Improve handling of vibration op, so that apps are better blamed (there is now a hidden vibrator API that supplies the app to blame, and the system now uses this when vibrating on behalf of an app). Add operation for retrieving neighboring cell information. Add a new op for calling a phone number. This required plumbing information about the launching package name through the activity manager, which required changing the internal startActivity class, which required hitting a ton of code that uses those internal APIs. Change-Id: I3f8015634fdb296558f07fe654fb8d53e5c94d07
* Switched to another method for launching apps.Maxim Siniavine2012-11-201-6/+47
| | | | | | | | Started using a separate thread which calls startActivityAndWait for starting apps. Also increased the minimum and maximum lengths of time to wait for apps to stabilize. Change-Id: I49935a0ed1d1c230e58dc1629e5e4da6b3887903
* Go to home screen after launching each app.Maxim Siniavine2012-09-171-3/+13
| | | | | | | | Instead of starting one app after another the MemoryUsage instrumentation goes to the home screen between launching apps. Change-Id: Ia0acf9f6f65a23f537b96c98743b59d746681447
* Fixed MemoryUsage issue with reporting results.Maxim Siniavine2012-08-301-17/+17
| | | | | | | | | When the memory of the application did not stabilize within the time limit, the test would report that using the application name, instead of the result key. Fixed the test to always use the result key. Change-Id: Ie16969e831bd3d89ee0496b992568f52bf1989cb
* Added a test to measure memory usage of apps.Maxim Siniavine2012-08-212-0/+273
Each app uses a certain amount of memory when running in the foreground. This test takes a list of app on the command line starts them one at a time and reports the total PSS of the app's process. The test allows to monitor memory usage over time. Change-Id: I3411bd96cf7c7af10acbb8deeb9936469b810ea2
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-12 04:54:11 +0000