Current version of winscope had several dependencies with deprecation
and security warnings. To avoid issues, update to the latest compatible
versions according to `package.json` configuration using `yarn upgrade`
Bug: 162925924
Test: compile and run winscope (yarn run dev)
Change-Id: I29b387e0620e0460d9ea51dbca4039bbeb4deb39
Previously Winscope considered only the `isVisible` property to
determine if the window was visible or not. This failed in cases such as
`com.google.android.googlequicksearchbox/android.app.ContextImpl` when
launching apps, where `isVisible=true` and `alpha=0`
Bug: 181630910
Bug: 182720234
Test: atest FlickerTests
Change-Id: I73de39557f0a9cebaad66d169f81794779793f64
MapNotNull is not a standard TS/JS function
Test: compile winscope and open any file
Bug: 167522376
Change-Id: I796d96eb963627bd3a872dea9dea51c7eaa97e8c
Recently the constructors of the flickerlib objects were
updated to reduce memory.
This CL updates winscope parser objects and fix visualization
so that it is compatible with those changes
Bug: 178572522
Test: `yarn run dev` and open a window manager trace
Change-Id: Ic331fe90d17e5c30c9062f119e26e824dbe1e5a7
This information was removed in a previous code refactor but is still
necessary
Bug: 162925924
Test: Compile winscope. Open a WM trace. Check if the window container
property exists
Change-Id: Ia93b927945f6aafa428fe5ebc3c3aace8223e2a7
The visible region calculation in the surface flinger doesn't consider that a layer with rounded corners can fully occlude another. Use the same behavior in flicker and winscope.
Bug: 174541970
Test: atest FlickerTests
Change-Id: Ie8e871a94b4413d2f02624c5738841d5d861bbbe
Fixes a couple of issues:
- if no flags are set, the configuration will not be send to the proxy.
Fix this by always sending the requested config
- make winscope tracing sync by default as a temp workaround for the
async tracing crashes
Bug: none
Test: toggle composition trace flags from winscope and check trace
Change-Id: I724dcc19309a616d3eb096d966dd40bf00c5d8ed
- Detect if a layer is not drawn if its corner radius crop is incorrectly set
- Add more sf trace flags with usage info
Test: manual testing
Change-Id: I4dbf93c1cc1a51bd713414451832f4f873054afa
Sometimes this information is null on the proto, this would crash
Winscope. Instead use an empty Rect when the information is unavailable
Bug: 167521440
Test: open a WM trace on Winscope
Change-Id: Ia6ceddfbbf8e083d02932925536ac64edafa6a2a
Use the same logic from CTS tests
Read the information from flickerlib and display in winscope
Test: yarn run dev and open a few WM traces
Bug: 167521440
Change-Id: I96cb956968066afaabb3acf53615db53bdfabe37
Flickerlib is migrating to the same structure as the CTS tests. This cl
makes winscope compatible with this changes. It now parses traces with
the new information and add a "flickerObj" entry to each node with the
calculated vlaues from flickerlib
Test: yarn run dev and open a few WM traces
Bug: 167521440
Bug: 170372278
Change-Id: I4a116ccabe392c75e5b5049808d4837f865cb2c7
This change updates the Winscope README with the new way of generating
the IntDefs mapping and copying it to the right location.
Test: N/A
Change-Id: Ifec40c8f0c878df37142899bac87413b46bb9e40
This change modifies the order in which flags are considered for IntDef
matching in Winscope. The most inclusive flags will be considered and
displayed first. Because of this, their composing values will not be
displayed anymore if a more inclusive flag is found first.
Bug: 173682107
Test: do a WM trace through ADB Connect in Winscope and see Gravity
values
Change-Id: I4fbba4d9bd11ef6acfec50acc3147f5994e4bd1f
Fixes incorrect visualization of sf layers if layer bounds are
not at 0,0. This can happen if the parent layer ends up cropping
the child layer.
Test: manual test with problematic winscope trace
Change-Id: I1e0c4ec0e632b015f6fae26ee20985cd6c56aa16
With this change Winscope will display only the current InputConnection
call information, compared to before, when all other methods were
displayed with null information.
This change affects both the client and service views.
Bug: 154348613
Test: upload a cleint or service trace in Winscope and visualise
inputConnectionCall information
Change-Id: I99e254715f7252e9349e27f56dec603d2e5f31bd
This changes fixes the InputMethodManagerSerice file naming for starting
tracing through ADB connect.
Bug: 154348613
Test: start Winscope and do an InputMethodManagerService trace through
ADB connect
Change-Id: Ia627250f523922ef8f73bb277a95f44aacd94f0e
This change updates the tarnsform operation of the clients view in
WInscope. This is done because of the new structure of dumped data on
the clients side: one trigger dumps a single client, instead of the
entire list of active clients.
Bug: 154348613
Test: flash a device
start IME tracing by calling "adb shell ime tracing start"
end IME tracing by calling "adb shell ime tracing stop"
pull generated trace files and visualize in Winscope
or start tracing directly through ADB Connect and visualize traces
Change-Id: I50c9a27a01a2f026acf4ee0f9dc394a6f74c06f2
Updated the IME tracing view in Winscope for the new optimized proto
dump format. This change adds the IMMS view separately from the
previously added clients and IMS views.
Bug: 154348613
Test: build and run the code using "yarn run dev"
build and flash the android code to a device
start and stop IME trace from the command line and then upload the files into Winscope or
start IME trace from the web interface, open an IME on the android device to generate logs, end trace from the web interface to see the logs
Change-Id: I0e3a2089c3d7b29c57477adc882047bb0829d2fd
Updated the IME tracing view in Winscope for the new optimized proto
dump format. This change adds the IMS view separately from the
previously added clients view.
Bug: 154348613
Test: build and run the code using "yarn run dev"
build and flash the android code to a device
start and stop IME trace from the command line and then upload the files into Winscope or
start IME trace from the web interface, open an IME on the android device to generate logs, end trace from the web interface to see the logs
Change-Id: Ia1ae9dc55f20c776c6fccd3399a57e6747737a66
Updated the IME tracing view in Winscope for the new optimized proto
dump format. This change included only the clients view since only
this information is currently dumped.
Bug: 154348613
Test: build and run the code using "yarn run dev"
build and flash the android code to a device
start and stop IME trace from the command line and then upload the file into Winscope or
start IME trace from the web interface, open an IME on the android device to generate logs, end trace from the web interface to see the logs
Change-Id: I3dc01d602147d41af3c5b99b848cb428e402c219
Older WM traces might not have an identifier set for
WindowContainer since this was added in ag/11659380.
This change makes Winscope again backwards compatible with older
WM traces. If it exists, the identifier of a parent holds the
place of a missing WindowContainer identifier. It is possible
that both identifiers are null, in which case the title and the
hashCode of WindowContainer are set as empty strings.
Bug: 170372278
Test: build Winscope locally, upload a WM trace and visualise it
Change-Id: Ieb5adc1d6a94d9a9215304b92114b807f1d812b4
Fallout from previous refactors.
Test: Open sf trace in winscope. Confirm layers are displayed in correct z-order
Change-Id: I256d03fe4fdd475f0172c79b524bbe99f4c2dde4
When zooming in the block size didn't adapt so we would see a large block instead of many small ones like we should be seeing
Test: Zoom in and make sure you see each individual entry and not all of them
Change-Id: I50d588cfe9e633d6aa0e771c6fbaefe4173ecce6
