Window adb device contains a '\r' character,
translate string to integer comparing.
Bug: 232488036
Test: 1. Excute python.exe winscope_proxy.py on Window Powershell.
2. Launch winscope index.html and set the Winscope token.
3. Tablet connect adb and winscope select the device.
4. Tap the 'DUMP STATE' button.
Change-Id: I8c261da523763982ea4a4bfae6883694b221883c
Can now set the buffer sizes for these two traces, as well as set
tracing level and type for WM. Tested for multiple combinations of
config settings, as well as if settings are left as
placeholders/selected as the name of the config.
Bug: b/200159899
Test: Run a SF/WM trace with arbitrary config settings and check that all loads as normal.
Merged-In: I50ccc271bd2f90dba1d22c3e8c568490c4bf831f
Change-Id: I50ccc271bd2f90dba1d22c3e8c568490c4bf831f
(cherry picked from commit 9d3f674027)
Flicker on master diverged form sc-v2, to make it easier to debug
flicker issues on sc-v2, push the current version of flicker into sc-v2
Test: atest FlickerTests WMShellFlickerTests
Bug: 188792659
Change-Id: Iaacfaa75102f93351a6ccd0252ecd739784f94ff
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
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
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
Required because transaction traces now output multiple files
Test: Make sure we can still get the traces from winscope using the proxy
Change-Id: I9c74aab0c659f09f7c30bda6fba06a646d36c637
Currently Winscope proxy doesn't support devices with a model name
containing '.' or ':'. These are necessary for remotely connected
devices, where the device model is in the format IP:PORT
Bug: 165535205
Test: connect to remote device and capture a trace through winscope
Change-Id: Iacc1dcb9fe4f6f07a2b7677b4b70ad8c332551c0
Added a new view for displaying logs, ProtoLog decoding and tracing
with ADB Connect.
Fixed a vertical scrolling bug.
Bug:
Test: yarn run dev
Change-Id: I756b596c10242ff919c0d7053813fa0b9f1f88fd
Added support for capturing WindowManager and SurfaceFlinger dumps
directly from the browser.
Fixed DataFilter errors on non-transaction data files.
Fixed Timeline behaviour on empty data list.
Bug: 140374376
Test: yarn run dev & python3 adb_proxy/winscope_proxy.py
Change-Id: I0d47ec36e1e769b856365d2a36c91bfb1f831b71
Added support for recording SF transactions with ADB Connect,
Fixed device regex not matching emulated devices.
Bug:
Test: yarn run dev & python3 adb_proxy/winscope_proxy.py
Change-Id: I43b45b978841309d3f011df919df69ae7ebc905a
The objective of this feature is to simplify the process
of debugging window transition issues by implementing
an automated trace capture flow for the WindowManager
and SurfaceFlinger trace analysis tool - Winscope.
By creating a bridge between the browser-based Winscope
and locally running ADB server traces can be captured
with a single click.
Design doc: https://goto.google.com/winscope-adb-connect
Bug:
Test: yarn run dev & python3 adb_proxy/winscope_proxy.py
Change-Id: I13ee2274566de5e63c89a9e292708416b654fc65
