| c766db0a54679cd67884d7366cee8b6e8ecd447c |
|
12-Jun-2017 |
Sudheer Shanka <sudheersai@google.com> |
Use correct timestamps of events for logging.
Currently when WM detects certain events, it will notify the logger
of these events asynchronously and logger uses the timestamp at which it
gets notified to log these events. It's possible that the delay between
when the event actually occurs and when the logger gets notified could be
large. So for better accuracy, WM should also pass on the event timestamp
to the logger.
Bug: 62375480
Test: Triggered sysui_multi_action event logs and verified that
APP_TRANSITION_DELAY_MS is less than APP_TRANSITION_WINDOWS_DRAWN_DELAY_MS.
Test: When the system is not busy, the timestamps we used to log earlier
and timestamps we log with this change are almost same.
Change-Id: I5f62654a6b7f179d821c0082b180246c8a569df1
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 515dd689ad3fdef0f59088ff0206e4650ecec3eb |
|
05-May-2017 |
Jorim Jaggi <jjaggi@google.com> |
Add TRON logging for bindApplication
Such that we know how much startup latency is the system to blame
and how much of it is the client process to blame.
Test: Open dead app, inspect logs
Change-Id: Ib8d359c2d59ef6f90893928f2b1d4e2ac2590d74
Fixes: 37327717
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| cdfc04e7b1924884fdb641a4f1adc07847e6ba36 |
|
28-Apr-2017 |
Jorim Jaggi <jjaggi@google.com> |
Fix app transition logging when switching quickly
If an app was set to invisible before the transition started,
which happens when quickly open an app and then closing again
before the animation is starting (only possible if starting
window is slightly delayed), we never receive onWindowsDrawn so we
need to cancel the transition in this case.
Also fixes an issue where the wrong activity was reported as
starting to us in case reusedActivity != null but we'll only reuse
it for the task and not the actual activity.
Test: Open Calendar, press home immediately, open another app, make
sure all logged events and times are correct.
Fixes: 37538546
Change-Id: I5819bd97964ab2dd5cb40b2f4e3bc5a9ac348152
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| b7f67abe3475e5397a065826157e1ef9eacb8522 |
|
26-Apr-2017 |
Alison Cichowlas <asc@google.com> |
Use uptimeMillis instead of currentTimeMillis for interval calculation.
uptime is guaranteed monotonic; currentTime may go backwards in the event
of NTP updates or other wackiness.
Test: manual sanity check of logs; android.support.test.metricshelper.MetricsAssertsTest passes
Bug: 37538546, 18584861
Change-Id: I222b20be9d561e1184b11155fe44c574d90872a5
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| d8a5777bf87555979b3f8297cb3cdccb9e34a4cd |
|
15-Apr-2017 |
Jorim Jaggi <jjaggi@google.com> |
Insert missing breaks
Found you!
Test: Go multi-window, go fullscreen, hammer home button
Change-Id: I019d89b95588ab2a0e33d9ef2bdc7240111162d0
Fixes: 36339388
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 56279cb0e17c6c035c58f3d50561fc629b0c2164 |
|
17-Apr-2017 |
Todd Kennedy <toddke@google.com> |
only log calling package for instant apps
Change-Id: I71b09fd130f27d5814638fdaaec33f759b0b2346
Fixes: 37425492
Test: manual
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| cd501ecd91bd7016639e8e62d4a739a01971f95c |
|
07-Apr-2017 |
Wale Ogunwale <ogunwale@google.com> |
Show recents at correct time when starting activity in docked stack
Previous logic relied on the returnTo type of the task of the activity
we are launching which can get the wrong signal at times because the
original task might have been started from home, but since we are
already in docked mode it shouldn't cause recents activity to be
launched.
We now decide if recents ability should be shown based on if the home
stack is currently visible at the time we started the new activity.
Also, renamed ActivityStack.getStackVisibilityLocked() to
ActivityStack.shouldBeVisible() since it is used to determine if the
stack should be visible and also so it isn't confused with the new
method ActivityStack.isVisible() which returns true if the stack is
currently visible.
Test: manual
Change-Id: I051e72ce93c886d25526af2afef851c95812ab3e
Fixes: 37005549
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 8c09ac7435c62a8ba2e34d57a7ac3be2ddf23adc |
|
16-Mar-2017 |
Jason Monk <jmonk@google.com> |
Clean up and cover more QS metrics
Change-Id: I4ab5e54398024c8b16ca8223f0639aadcdef4377
Fixes: 34801532
Test: runtest systemui
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| b3b43130db1c02493ca881ad95adf27ec0cbe8ad |
|
21-Mar-2017 |
Todd Kennedy <toddke@google.com> |
Send launch token to activity manager
When an instant app is installed, control passes from the platform
to the instant app installer. However, when the instant app is
launched, the original launch token needs to be associated with that
launch. Do this by sending the launch token along with the original
launch intent
Change-Id: I5741be343862d4e5c8bfb6b4a81d0bac8e53ea9c
Fixes: 35445667
Test: Build and manully inspect the event logs to ensure the launch token is sent on instant app launch
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 50d946c13a5a47c6617530425479b0ad4f381700 |
|
17-Mar-2017 |
Todd Kennedy <toddke@google.com> |
Add TRON logs
Add logs for instant app resolution [both phase 1 & 2]
as well as new logs for all activity starts.
Change-Id: I0d25daa383854eacd3bc406ce1360d819a8ec4ba
Fixes: 35442251
Fixes: 35441725
Test: Manual; install/run instant app and inspect the event logs for appropriate tags
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 453cae3692579c787d855615a5bb2a8f9c57d907 |
|
16-Mar-2017 |
Jorim Jaggi <jjaggi@google.com> |
Protect against weird null case
No time to figure out what's going on, but this null check helps
Test: Dock app, make fullscreen, hammer home button
Change-Id: I3eb94a8138bc1483b1711556696bcbbaee6084e7
Bug: 36339388
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 3878ca3333da1bf5cbc83d33e5e8b3ce68c8c5e4 |
|
03-Feb-2017 |
Jorim Jaggi <jjaggi@google.com> |
Fix multi-dimen app transition delay tron event
Make sure to log everything.
Test: Open app, inspect log.
Test: com.android.systemmetrics.functional.AppStartTests
Bug: 33086172
Change-Id: I6fdfef625c09267dcf20724e853cf7471abc86c9
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 8347163dbb64fb61012c0393163283106a0a351e |
|
13-Dec-2016 |
Winson Chung <winsonc@google.com> |
Create a new stack for the assistant activity.
- Add a new stack that is not resized with multiwindow, and
appears above the fullscreen and docked stacks, but below
the pinned stack
- Add a method on VoiceInteractionSession to allow the assistant
to launch activities into this new fullscreen stack.
- Also prevent any activities in the assist stack from the
fetching of the on screen assist data.
Bug: 30999386
Test: android.server.cts.ActivityManagerAssistantStackTests
Change-Id: I22ab7629b5f758cf1e66d7d1c26648af6bc887c9
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| b62371434c9b63560c78a85123fe9386edac1205 |
|
23-Jan-2017 |
Chris Wren <cwren@android.com> |
Move MetricsReader to SystemApi
Test: runtest --path frameworks/base/core/tests/coretests/src/android/metrics && runtest --path frameworks/base/core/tests/coretests/src/com/android/internal/logging/legacy/
Change-Id: If55f0444d5a836f24234182d298ebc128643efc1
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 5cc5d8a3e94d8150b2e1b6310ec92569e931c277 |
|
10-Jan-2017 |
Alison Cichowlas <asc@google.com> |
Add a required main category for multi logs.
Test: updated LogBuilderTest
Change-Id: Ia5359e12a7a84af31d9a966f2c81fc943aadfbdb
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 803054dccb2f2201c6b11f5ab4e61ef8dff984e1 |
|
13-Dec-2016 |
Alison Cichowlas <asc@google.com> |
Log wrapper for multi-metrics in tron.
Test: Added new LogBuilderTest; runtest --path frameworks/base/core/tests/coretests/src/com/android/internal/logging/LogBuilderTest.java
new file: core/java/com/android/internal/logging/LogWrapper.java
Change-Id: I8c64a07b95ab9a70f39663d4ec54f9ec1bf49063
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| ae1ff4f85ffd12ab8a14c610b1474a012536888f |
|
11-Nov-2016 |
Matthew Ng <ngmatthew@google.com> |
Split home stack into home and recents stack
Refactored functionality of home stack (HOME_STACK_ID) in the code
base to home stack and recents stack (RECENTS_STACK_ID). Also changed
function and variable names from homeStack to homeOrRecentsStack.
Differentiating home and recents stack will allow readablilty and
managing logic between home and recents stacks. For example, for
multi-window minimized dock state, the home and recents stacks can
be set to different rects where the home stack needs to be a fixed
large size while the recents stack is hidden and the dock stack is
animating to be minimized.
Fixes: 32839371
Test: ./run-test android.server.cts and manually tested split and
rotation
Change-Id: I7603359c2dc20e35924664178634eb761e0367a6
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 383db5ebcc3a4a615faf249bf4f126f42e80b82e |
|
22-Jun-2016 |
Tamas Berghammer <tberghammer@google.com> |
Update package names to work with the proto3 compiler
Bug: b/28974522
Change-Id: I5f3adf4946ee4ba1e09e4f40afe83c151405972a
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 1e630c08296ec6cc311cc4e1c397f7ca50a1a735 |
|
16-May-2016 |
Jorim Jaggi <jjaggi@google.com> |
Fix transition delay tracking when starting activity from recents
- Move logic to determine app switch etc. into ActivityMetricsLogger.
- Make sure the notify the tracker in startActivityFromRecentsInner
Bug: 27295491
Change-Id: Ic68058c88917e3f37183dded2f13cb35055323ee
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| f970410afef518003c84eef022194848b2a4f606 |
|
06-May-2016 |
Jorim Jaggi <jjaggi@google.com> |
Don't crash the system when detecting a transient wrong state
Bug: 28616824
Change-Id: I124f7196d709c33fe70137541b650788af83b3b3
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| be67c90f4c2255cab3bc036ecdc8d9636ed5e4b5 |
|
12-Apr-2016 |
Jorim Jaggi <jjaggi@google.com> |
Don't log transition time if no process switch
If the process of an activity that is launching has another
non-stopped activity, the data is not that interesting,
so remove the logging in these cases.
Bug: 27295491
Change-Id: I65d4a0e01b1e634a589ce8ecbbab337f0e6497ca
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 8051c5c89060906f5a3a1ca4adb3b53bb423e56b |
|
04-Mar-2016 |
Wale Ogunwale <ogunwale@google.com> |
Don't make home stack visible if starting activity isn't translucent
We allow the home stack to be visible right behind the fullscreen
stack if all the activities fullscreen stack are translucent and
visible. However, if we are starting an acitvity it isn't visible
yet so our check for translucent activities in the fullscreen
stack will return true since there is nothing visible. This will
cause the home stack to the visible and the visiblilty of its app
token set to true in window manager and it been factored into the
transition animation.
In addition to checking if the activity is visible, we now also
check if it is the starting activity when trying to determine if
the stack is translucent.
Bug: 27448511
Change-Id: Icbbd57c0632cc5389c7ac894800a41f75d4bc450
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 275561a74677f9d6c8f3f2cebc3cfea416ca586d |
|
23-Feb-2016 |
Jorim Jaggi <jjaggi@google.com> |
App transition delay tracking
Add TRON logging for all kinds aspects when we execute an app transition.
Bug: 27295491
Change-Id: Icb0cbdb92d4d5fbfedadd40a017a50eb217058aa
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 0e381e278a2c2a3a7c86c9951ac5cbcdc3a186f4 |
|
15-Jan-2016 |
Filip Gruszczynski <gruszczy@google.com> |
Fix visible-behind not visible for translucent activity in fullscreen stack.
Bug: 26471802
Change-Id: Ide9945c4478805902ca0df92dc2043359a751600
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| ae255ee61b5e174c2164e58389b8a7ff8a95e14d |
|
04-Jan-2016 |
Chris Wren <cwren@android.com> |
fix ActivityMetricsLogger counter names
Change-Id: I49e4785fdecfdbb60fc168539e654bcb7847d1dd
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| caae14e478e115d01f9b32890cb31231575e65dd |
|
16-Dec-2015 |
Filip Gruszczynski <gruszczy@google.com> |
If pinned stack is focused, look for the one below for logging.
Bug: 26230638
Change-Id: Ibe0b993286c4669e0f565bd2d4af6077553a29e2
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|
| 77d9448e2d6dd8a45c5fedef43c8a1cf4afd28b9 |
|
11-Dec-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Log window mode to tron.
Bug: 26013430
Change-Id: I45d397d956a66f407218047dc10581553f906077
/frameworks/base/services/core/java/com/android/server/am/ActivityMetricsLogger.java
|