Use the visibleRegion property to determine if a layer is visible on
the screen or not. Elements may have a size and a crop but be displayed
below another.
While the visible option cannot be used to render the elements due to
transforms, it only has a value if the element is displayed on the
screen.
Note that elements may still not appear on the screen as all their
visible regions are below the screen (right < 0 or bottom < 0)
Test: Open trace in winscope, check if only layers visible on the screen have a visible chip and are displayed.
Merged-In: I75137a5057a5bda96db887b110b053e64b49f885
Change-Id: I75137a5057a5bda96db887b110b053e64b49f885
It is no longer possible to use only the size property because Color
layers do not set a buffer size.
Use the following rule to highlight the selected layers on the UI:
- If the layer has a size and a crop, use their intersection.
- Else, if the layer has no size, but has crop, use the crop as size
- Else, use the parent size
Bug: 121198524
Test: Open trace in winscope, select visible layer, check if highlighted
Merged-In: I55298f20efa31830097a41d45d8d8b1c6b4ed2e6
Change-Id: I55298f20efa31830097a41d45d8d8b1c6b4ed2e6
SurfaceFlinger trace relies on Display Root#0 layer size to set the display bounds. This layer will
no longer have a size once b/114413815 is fixed. Instead, sf transform will set the bounds to undefined and the
bounds be calculated to be the union of the layer sizes.
see: http://x20web/teams/android-window-manager/winscope/winscope-staging-vishnun.html
Bug: 114413815
Test: build winscope and open trace
Merged-In: Ic04d524f0e095374321ef818f0d0ff420a2d3827
Change-Id: Ic04d524f0e095374321ef818f0d0ff420a2d3827
Top level of the hierarchy contains the entry with a timestamp. When
navigating the timeline with arrow keys, entry loses focus since
the timestamp changes.
See: https://android-window-manager.teams.x20web.corp.google.com/winscope/winscope-staging-vishnun.html
Test: Open trace in winscope, click on entry & navigate timeline with arrow keys
Merged-In: Ifbd88da717354c66d96a05d25a9d619fa5209e26
Change-Id: Ifbd88da717354c66d96a05d25a9d619fa5209e26
We should still be able to properly render traces taken prior to the WindowFrames
refactor - if the property is not available, use the legacy property instead.
Test: yarn run dev
Merged-In: Ie10f7d14ac5673e8be844d2d5a4fa752d502b9df
Change-Id: Ie10f7d14ac5673e8be844d2d5a4fa752d502b9df
The code is changed so the frame protobuf is now under another class
called windowFrames. Update the js code so it can properly draw the
frame with the new code change.
Test: Ran on localhost with updated protobuf file
Bug: 111359087
Merged-In: I072daae54601120de5b6eaa0a64ee7c3096e4a43
Change-Id: I072daae54601120de5b6eaa0a64ee7c3096e4a43
Trace location was incorrect. Changing to correct location.
Test: run capture_sf_trace.sh, upload to winscope, see trace
Merged-In: Ia84501014e6cf83d2fb1d167c1a7aac8b64a06d4
Change-Id: Ia84501014e6cf83d2fb1d167c1a7aac8b64a06d4
Fixes: b/110715663
This tool compares system and product image across models, and generate
common.csv and diff.csv
Here is example output
- common.csv:
filename, sha1sum, targets
/system/a, da39a3ee5e, a;b;c
- diff.csv:
filename, sha1sum, targets
/system/b, da39a3ee5e, a;b
/system/c, 3f786850e3, a
/system/c, 89e6c98d92, b;c
Bug: 131273025
Test: m system_product_image_diff
Test: system_product_image_diff -t model1 model2 -s system product
Change-Id: Ie9cc368e0a6d26e956f1e27ebe683bea5e80465c
Copy advancedFeatures.ini file from
device/generic/goldfish/data/etc, which is the centralized place for
advancedFeatures.ini.
BUG: 135187406
Change-Id: Ib1d2ec2f91d66dde89bc4a884cd99dbb1a2c83cb
Signed-off-by: Weilun Du <wdu@google.com>
The no_standard_libs property is deprecated in favor of
sdk_version:"none" as the latter is simpler and less error prone.
Bug: 134566750
Test: m droid
Change-Id: I410e4b98481cec1a5512cd138f735038a725287b
gdb looks for an executable's dynamic linker using the PT_INTERP setting
from the executable. That value can be various things:
- /system/bin/linker[64]
- /system/bin/linker_asan[64]
- /system/bin/bootstrap/linker[64]
Currently, only the bootstrap linker is available in the sysroot/symbols
directory. The ordinary and ASAN linkers are symlinks on the target and
are missing from the sysroot (aka symbols) directory.
Use the executable's PT_INTERP value to find the symbolized linker binary
and add it to the solib search path. If necessary, copy or pull a linker
binary.
Test: gdbclient.py -r ls
"info sharedlib" shows $OUT/symbols/apex/com.android.runtime.debug/bin/linker64
Test: gdbclient.py -r /data/nativetest64/bionic-unit-tests/bionic-unit-tests
"info sharedlib" shows $OUT/symbols/system/bin/bootstrap/linker64
Test: m asan_test
gdbclient.py -r /data/nativetest64/asan_test/asan_test
"info sharedlib" shows /tmp/gdbclient-linker-HunVs9/linker_asan64
Bug: http://b/134183407
Change-Id: I7f79943dcd9ec762d1aaf21178bb6ab3eff40617
As discussed with Romain Guy in the email thread, the Apache 2.0
license applies to the affected .jpg files now and retroactively from
the time of import.
Each of the images was altered using the exiftool:
exiftool -URL=http://www.apache.org/licenses/LICENSE-2.0 \
-WebStatement=http://www.apache.org/licenses/LICENSE-2.0 \
-UsageTerms='Apache License Version 2.0'
Change-Id: I9843a8f9b285799cc28e824167cbe0f14e4e651e
As discussed with Romain Guy in the email thread, the Apache 2.0
license applies to the affected .jpg files now and retroactively from
the time of import.
Each of the images was altered using the exiftool:
exiftool -WebStatement=http://www.apache.org/licenses/LICENSE-2.0
Change-Id: I557d0129617164209a3eec7ec2d228f266643ca0
* changes:
def-tool: Do not emit errors on public.libraries.txt
def-tool: Support product and product_services partition
def-tool: Remove a dead argument (cont)
This commit skips the errors that are caused by the access from apps (on
vendor or product partitions) to shared libraries described in
`/{system,vendor}/etc/public.libraries.txt`.
Bug: 110184925
Test: ./vndk_definition_tool.py check-dep \
--system ${ANDROID_PRODUCT_OUT}/system \
--vendor ${ANDROID_PRODUCT_OUT}/vendor \
--product ${ANDROID_PRODUCT_OUT}/product \
--tag-file datasets/eligible-list-XX.csv
Change-Id: I6eb07d500d0a625c74cde402ae06a351cad4400b
This commit adds initial support to `product` and `product_services`
partitions.
Test: ./tests/run.sh
Change-Id: I15cc1568c880cc783eed6d22fec288246305b66c
This commit removes a dead argument. This fixes a regression caused
by a related CL earlier.
Test: ./vndk_definition_tool.py deps-insight \
--system ${ANDROID_PRODUCT_OUT}/system \
--vendor ${ANDROID_PRODUCT_OUT}/vendor \
--product ${ANDROID_PRODUCT_OUT}/product
Change-Id: I70b7132f8c0679bd1cd934bae1066d1f127304f8
* changes:
def-tool: Rename FWK to SYSTEM and VND to VENDOR
def-tool: Skip dex test if smali cannot be found
def-tool: Rename *-Indirect to *-Private
def-tool: Remove dead arguments
This commit replaces abbrevations to full names, e.g. FWK-ONLY to
SYSTEM-ONLY and VND-ONLY to VENDOR-ONLY.
Test: ./tests/run.sh
Change-Id: Icf78c7097535ddff40f71a986501858936574f25
This commit skips dex test cases if the `smali` command cannot be found
from the path. Before this commit, the test was not skipped because the
`subprocess.checked_call()` throws `OSError` (instead of `IOError`) in
Python 2.
Test: ./tests/run.sh
Change-Id: Ic7ec11ab9d9de2294132d88a2b084ef11dd01c87