| 1b012d302b56b4adf950035136d1d191a1936d5a |
|
20-Aug-2014 |
Jeff Hao <jeffhao@google.com> |
Add sample profiling option to am.
Also bundles all profiling options into a class.
Bug: 17040932
Change-Id: I85d675ee1494bdc7308caffdf94145d27c996e9d
/frameworks/base/tests/MemoryUsage/src/com/android/tests/memoryusage/MemoryUsageTest.java
|
| e2a03fe43d1f8eb5a6ada046870dcc35392d8f17 |
|
08-Aug-2014 |
Guang Zhu <guangzhu@google.com> |
freeze screen rotation during memory and app launch test
Change-Id: I2a039be383562019a0af9470c5053cd3cb1e6142
/frameworks/base/tests/MemoryUsage/src/com/android/tests/memoryusage/MemoryUsageTest.java
|
| 6c77e104bcb265d29f357b7fb5737153c048bcdb |
|
24-Jul-2014 |
wsmlby <wsmlby@google.com> |
Add memory tracking for persistent proccesses and launcher
Change-Id: I5228bd67884dc8b77207a597f279fd4032c7f9d9
/frameworks/base/tests/MemoryUsage/src/com/android/tests/memoryusage/MemoryUsageTest.java
|
| f265ea9d8307282ff1da3915978625a94fc2859e |
|
01-Feb-2013 |
Dianne Hackborn <hackbod@google.com> |
App ops: vibration, neighboring cells, dialing, etc.
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
/frameworks/base/tests/MemoryUsage/src/com/android/tests/memoryusage/MemoryUsageTest.java
|
| d85b8d57a0ce0514a1c9ea8f763b95aa94711645 |
|
20-Nov-2012 |
Maxim Siniavine <siniavine@google.com> |
Switched to another method for launching apps.
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
/frameworks/base/tests/MemoryUsage/src/com/android/tests/memoryusage/MemoryUsageTest.java
|
| a9d9decf87a040087a9bda4340d53c21cd3e672a |
|
15-Sep-2012 |
Maxim Siniavine <siniavine@google.com> |
Go to home screen after launching each app.
Instead of starting one app after another the MemoryUsage
instrumentation goes to the home screen between
launching apps.
Change-Id: Ia0acf9f6f65a23f537b96c98743b59d746681447
/frameworks/base/tests/MemoryUsage/src/com/android/tests/memoryusage/MemoryUsageTest.java
|
| 2effa64ab7192d9c41cbbe1fd57d61d6d6f94ba8 |
|
30-Aug-2012 |
Maxim Siniavine <siniavine@google.com> |
Fixed MemoryUsage issue with reporting results.
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
/frameworks/base/tests/MemoryUsage/src/com/android/tests/memoryusage/MemoryUsageTest.java
|
| 9229700728ec4b7bca28da5325b48a4acb4bfc0d |
|
17-Aug-2012 |
Maxim Siniavine <siniavine@google.com> |
Added a test to measure memory usage of apps.
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
/frameworks/base/tests/MemoryUsage/src/com/android/tests/memoryusage/MemoryUsageTest.java
|