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
This CL makes the necessary additions for Winscope to:
1) Accept an IME trace output file (ime_trace.pb) and display its contents
2) Start IME trace from the web interface and display the contents along with other traces
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: I090c9e3ca4e334a273269d11db006ec8cb63756c
When upload an archive for files that don't have a magic number, it is hard to reliable detect their filetype so be tend to have false positive, this adds a check to try and match the filename to keywords for better autodetection
Test: Manually upload a bug report and make sure the correct files are matched
Change-Id: I12fde431498785a7f8674e495805f009a6fb9f2c
Reverts some of the changes that add tranasction merge history handling to Winscope that are not yet compatible with the latest frameworks/native
Test: Make sure winscope compile without the transaction merge history changes of frameworks/native
Change-Id: I5517bb4e14f63e4a93ecade0763051abd40ff09f
Fixes a bug where the layer wasn't highlighted when we clicked on it in the rect view
Test: Click on the rects and make sure they are highlighted in the rect view
Change-Id: Ifa2c18cfbc0d8a255550ac32a3e3ed3946679fd3
Adds a log message class in type script to make sure compile check catch any incompatibilities between formatted and non formatted log messages
Test: Open a trace with invalid log messages and make sure no errors occur
Change-Id: I144c106b2a4ef70c9fb6666deff36a19bde0742a
This is required for production builds since we only deploy a single .html file and don't server the rest of the generated files
Test: Try and build and see if Winscope loads by loading only the generated .html file
Change-Id: Idc7614d72bb91a35da3574f5c93588690ccfb6a0