payload.js defines a Class that could parse the OTA metadata from
an OTA package(.zip). PackageAnalysis.vue enable users to upload
their own OTA package for analysis. PayloadDetail.vue and
OperationDetail will display the metadata in a human-readable way.
The whole analysis process is done on frontend and no communication
with server is involved after loading the page.
Test: Mannual tested.
Change-Id: I3becba872f6564ec9e44edad3a6cc19eb0714ed6
Use protobufjs to compile the update_metadata.proto
into update_metadata_pb.js
No-Typo-Check: auto-generated artifacts
Test: Mannual tested.
Change-Id: Ia0fefa57154f68809c8775ead9fa5e24d4804013
Add functions:
- Now the ota package generate history is stored in a database.
- Job status page will show some basic info of the jobs.
- Job detail page will show a detailed configuration.
Test: Mannual tested.
Change-Id: Ia98763e783e8d9c903ac8f5c137719df8527d204
New functions:
- The uploaded target files will be stored into a database.
- The detailed info of target files can be shown in the target library.
- Add support for generating partial OTA.
Test: Mannual tested.
Change-Id: Idf715994fe51b9ab6addbfe72792be890243702d
New functions:
- Can upload target file.
- Can select target file from the uploaded ones.
- Can download the generated OTA file.
- Can monitor the stdout during OTA package generation.
Also decoupled the job running function with the web server code.
Test: Mannual tested.
Change-Id: Ic525ef3997f048d73b21ad1d9475d54b1f8d112c
- Use flicker object on the property tree
- Keep `proto` entry on the property tree with the original proto file
- Use `prettyPrint` method on flicker to format output for winscope
Bug: 185516271
Test: build winscope and open WM traces
Change-Id: I1c9f1a106b82f487b78d1b386cc091d21715e04d
Present the values of WM and SF traces alphabetically
Bug: 185516271
Test: build winscope and open WM/SF traces, check the property list
Change-Id: I6cc5553ae6e987d52f812c030b0e4706ab58606b
- Use flicker class type as object type
- Use name from flicker
- Use stableID from flicker
- Refactor element visibility
- Rename `childrenWindows` to children to avoid creating a new property
Bug: 185516271
Test: build winscope and open WM traces
Change-Id: I582c0fe4ac48f8a503d1dccfbce437d489a50ca7
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
