summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2022-01-25Merge "Snap for 8113988 from d59857efb33e823960210e507aaeceee6c703e2c to ↵android-vts-12.0_r9android-vts-12.0_r8android-vts-12.0_r7android-vts-12.0_r6android-vts-12.0_r5android-vts-12.0_r4android-vts-12.0_r12android-vts-12.0_r11android-vts-12.0_r10android-cts-12.0_r9android-cts-12.0_r8android-cts-12.0_r7android-cts-12.0_r6android-cts-12.0_r5android-cts-12.0_r4android-cts-12.0_r12android-cts-12.0_r11android-cts-12.0_r10android12-tests-releaseAndroid Build Coastguard Worker
android12-tests-release" into android12-tests-release
2022-01-25Snap for 8113988 from d59857efb33e823960210e507aaeceee6c703e2c to ↵Android Build Coastguard Worker
android12-tests-release Change-Id: Ifb00876f7e3ab609da1620da5903d3d8a3ef43c3
2022-01-25Merge "opengl: tests: Add explict android:exported flag to manifests" into ↵android12-tests-devTreehugger Robot
android12-tests-dev
2022-01-24opengl: tests: Add explict android:exported flag to manifestsJoseph Cheng
After Android S+, it's required to add android:exported flag on manifests if an intent filter is defined[1]. However, it's missing on the manifests of these opengl tests which are targeting to current sdk version leads to installation failures for these APKs. Fix it by adding required android:exported flag. [1]: https://android.googlesource.com/platform/frameworks/base/+/c4e90ac06ad3e0fd2af9e3864742e2d1199a8cdd Test: These APKs are installed successfully on Android 12 devices. Bug: 215940253 Change-Id: Ia95a46cc55103e7f075900acd237b41699f4cbd0
2021-10-18Merge "Snap for 7834066 from fd2a942a07401b0a0fa5f3d73841026da2348220 to ↵android-vts-12.0_r3android-vts-12.0_r2android-cts-12.0_r3android-cts-12.0_r2Android Build Coastguard Worker
android12-tests-release" into android12-tests-release
2021-10-18Snap for 7834066 from fd2a942a07401b0a0fa5f3d73841026da2348220 to ↵Android Build Coastguard Worker
android12-tests-release Change-Id: I905d69e5eadb9c66a6ffb8277f5542a9140fc57f
2021-10-09Merge "Merge "Merge "Merge "vkjson: Use Vulkan API version 1.1 on ↵Automerger Merge Worker
VkJsonGetInstance" into pie-vts-dev am: 2e4003ba01" into android10-tests-dev am: 952de6e2e5" into android11-tests-dev am: 2c487876a8" into android12-tests-dev
2021-10-09Merge "Merge "Merge "vkjson: Use Vulkan API version 1.1 on ↵Automerger Merge Worker
VkJsonGetInstance" into pie-vts-dev am: 2e4003ba01" into android10-tests-dev am: 952de6e2e5" into android11-tests-dev am: 2c487876a8 Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/1236142 Change-Id: I897858870e2fd1c88660b0e56e3feb3397069f2b
2021-10-09Merge "Merge "Merge "Fix testVerifyStatsExternalConsistent case" into ↵Automerger Merge Worker
android10-tests-dev am: f9e600c112" into android11-tests-dev am: 6f05e37e28" into android12-tests-dev
2021-10-09Merge "Merge "Fix testVerifyStatsExternalConsistent case" into ↵Automerger Merge Worker
android10-tests-dev am: f9e600c112" into android11-tests-dev am: 6f05e37e28 Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/1179609 Change-Id: Idf22374a3ecda95c9570ce260b86b704acfd79d7
2021-10-08Merge "Merge "Merge "Change the position of addAndGetFrameTimestamps when ↵Automerger Merge Worker
queueBuffer" into android10-tests-dev am: 7eca3198fd" into android11-tests-dev am: 40b131e027" into android12-tests-dev
2021-10-08Merge "Merge "Change the position of addAndGetFrameTimestamps when ↵Automerger Merge Worker
queueBuffer" into android10-tests-dev am: 7eca3198fd" into android11-tests-dev am: 40b131e027 Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/1191379 Change-Id: I313eec1bc724d26e223d8617096d66dd186644fc
2021-08-12Merge ab/7633965The Android Open Source Project
Bug: 169893837 Merged-In: I2a2d02a0d7e67ee9577857a210cb6157683e5598 Change-Id: Iecdf0a17afe650483461978b42161940ce002101
2021-08-06Merge "Blast: Fix missing release callbacks for shared buffers" into sc-devandroid12-devVishnu Nair
2021-08-06Merge "SF: fix frame rate for layer tree" into sc-devAdy Abraham
2021-08-05Blast: Fix missing release callbacks for shared buffersVishnu Nair
Fixes an issue where buffers were compared only using the buffer id. In shared buffer mode, the client will queue up the same buffer id multiple times so we need to distinguish using the frame number as well. Test: https://buganizer.corp.google.com/issues/195447981#comment18 Fixes: 195447981 Change-Id: I2a2d02a0d7e67ee9577857a210cb6157683e5598
2021-08-05SF: fix frame rate for layer treeAdy Abraham
With the current implementation we might mark layers as NoVote incorrectly when a sibling has a frame rate. Test: adb shell /data/nativetest64/libsurfaceflinger_unittest/libsurfaceflinger_unittest Bug: 195205467 Change-Id: I62641f855a027e1192f9a85a4bc50692b1744764
2021-08-04sensorservice: ProximitySensor needs to report correct sensor state.Chris Kuiper
Calls to ProximitySensor::activate() may repeatedly set enabled=true. The current logic doesn't account for that. In order to correctly report the current sensor state, simply use mSensorDevice.isSensorActive() instead. Bug: 194878856 Test: 1) Reproduced problem and verified mIsProxActive in "dumpsys display" contains the correct value and no more 60/90Hz flicker. 2) Adding local debugs, then mixing making phone calls with additional "sensor_test sample -s8 -n5" commands to create several Prox clients, and verifying logged flags and reference counts. Change-Id: I2342844ff4e6301a6b9ac8a33dc3e6047fca83ad
2021-08-04sensorservice: Fix SensorDevice::isSensorActive().Chris Kuiper
SensorDevice::isSensorActive() currently returns "numActiveClients() > 0", but it should return ".isActive". An "active client" is really one that has some requested batching parameters stored, which it can do even while the sensor is disabled but, the isActive bool tracks whether the the sensor is currently enabled at the HAL, which is what we really want. Bug: b/194878856 Test: Together with ag/15459770: 1) Reproduced problem and verified mIsProxActive in "dumpsys display" contains the correct value and no more 60/90Hz flicker. 2) Adding local debugs, then mixing making phone calls with additional "sensor_test sample -s8 -n5" commands to create several Prox clients, and verifying logged flags and reference counts. Change-Id: Id4a13ebb5cde8de87ee7547d2989c3c0d1a69a09
2021-08-02Merge "SurfaceView: Synchronize destframe updates with SurfaceView size ↵Vishnu Nair
changes" into sc-dev
2021-07-30SurfaceView: Synchronize destframe updates with SurfaceView size changesVishnu Nair
This CL fixes one of the issues with SurfaceView parent frame and content syncing. With BLAST, we have two surface controls each setting a scale. The parent surface control sets a scale based on the requested surface size and the SurfaceView layout size. The BlastBufferQueue surface control scales the buffer to the requested buffer size if the buffer has the appropriate scale mode. The destination frame controls the second scaling and it must be applied with the parent surface scale changes. This cl fixes flickers where the requested fixed surface size changes without any view size changes. This cl allows the caller to pass in a transaction to BLASTBufferQueue#update which is updated with the destination frame changes. This transaction can then be applied with the parent surface changes. This also fixes an issue where destination Frame was being set on every buffer update and when we updated the BlastBufferQueue size. Since buffer transactions can be queued up on the server side, a stale value maybe applied for a few frames causing flickers. Fixes: 194458377 Test: bug repro steps Test: atest SurfaceViewSyncTest#testSurfaceViewSetFixedSize Change-Id: I216586842ff45bfd398659b5cc0c89eaf51394ff
2021-07-29Merge "Don't call invalidateHwcGeometry when handling transactions" into sc-devRob Carr
2021-07-29Merge "Prevent HDRLayerInfoListener traversal from running on every frame" ↵Rob Carr
into sc-dev
2021-07-28Prevent HDRLayerInfoListener traversal from running on every frameRobert Carr
We should only have to update the HDRLayerInfoListener in a few scenarios. 1. A new listener appeared 2. A buffer changed colorspace 3. Surface geometry (visibility, parenting, display, etc) changed We protect the traversal behind these flags to avoid the runtime in the hot path of continuous buffer updates. A follow up fix could consider directly recursively traversing and early returning if !Layer->isVisible. Bug: 186200583 Test: Existing tests pass, simpleperf Change-Id: I549fdf6ea228344f79f6989b86b8e73a6065158a
2021-07-28Don't call invalidateHwcGeometry when handling transactionsRobert Carr
This causes composition engine to trigger a full update when preparing composition state (StateSubset::GeometryAndContent) vs StateSubset::Content. In single buffer update scenarios this costs ~14% of whole process CPU instructions or ~20% of main thread CPU instructions. Bug: 186200583 Test: Existing tests pass Change-Id: I8e3be0e4d828823f665fb05ea275401a178eb861
2021-07-28Merge "mm_events: Add knob to remove mm_event tracing instance" into sc-devKalesh Singh
2021-07-28Merge "MotionEvent: Guard getRawX/Y compatibility logic using feature flag" ↵Prabir Pradhan
into sc-dev
2021-07-28mm_events: Add knob to remove mm_event tracing instanceKalesh Singh
Only create mm_event tracing instance if persist.mm_events.enabled=true. This saves ~5.5MB on low memory devices that don't enable mm_events. The memory saved is slab memory that would be allocated for the ftrace instance's inode/dentry objects. Set the per-CPU trace buffer sizes to 1KB by default to minimize trace buffer memory usage if perfetto isn't started. Also disable tracing by default, traced_probes will enable as needed. Bug: 194156702 Test: boot; ls /sys/kernel/tracing/instances -> No mm_events Test: setprop persist.mm_events.enabled true; boot; ls /sys/kernel/tracing/instances -> mm_events Change-Id: I89d7e5e1cd0d32b5612bc419b1a1c4b8c3c8ade6
2021-07-27Merge "binderVendorDoubleLoadTest: rm from VTS" into sc-devTreeHugger Robot
2021-07-27binderVendorDoubleLoadTest: rm from VTSSteven Moreland
This test largely duplicates generic VNDK tests, and it requires the same vendor/system version, so removing from VTS. Bug: 186785704 Test: N/A Change-Id: I2235ff8c9453e15e5db3848030617a2478407eb7 (cherry picked from commit 105db55a00dab757391e11ba45e67b124870b490) Merged-In: I2235ff8c9453e15e5db3848030617a2478407eb7
2021-07-26MotionEvent: Guard getRawX/Y compatibility logic using feature flagPrabir Pradhan
The getRawX/Y API contains compatibility logic that should only be used when the per-window-input-rotation feature is enabled. The compatibility logic was previously unguarded because it was assumed that the logic was a no-op when the flag was not enabled. However, this turned out to be untrue, resulting in the bug. Bug: 187686656 Test: manual: using repro steps listed in the bug. Change-Id: I6603694f9872e7df4b6f72c7fb2555b3249687a6
2021-07-24Merge "SF: add a solid background when hole punching a cached set" into sc-devAdy Abraham
2021-07-23SF: add a solid background when hole punching a cached setAdy Abraham
When we punch a hole to round the corners on a PIP window we need to make sure that the cached set is opaque to prevent blending of the rounded corner edges with random opaque buffers. Bug: 194307461 Test: PIP window on solid color wallpaper Change-Id: I5ab80103dc5b43db85c4f12c9efd5ba2a1dfd076
2021-07-23Merge "Revert "Add systrace tag for system property"" into sc-devTreeHugger Robot
2021-07-23Merge "Add mechanism for a task's windows to be trusted overlays (SF)" into ↵Winson Chung
sc-dev
2021-07-22Merge "Implement native PerformanceHint API" into sc-devTreeHugger Robot
2021-07-22Merge "[libbinder] Stop exporting std:: and android::sp symbols" into sc-devPirama Arumuga Nainar
2021-07-22Revert "Add systrace tag for system property"Bowgo Tsai
Revert "Adding system property tracing" Revert submission 1403568-sysprop_trace Reason for revert: makes property get/set non-reentrant Reverted Changes: I6f85f3f52:Add systrace tag for system property Id2b93acb2:Adding system property tracing Id78992d23:Add systrace tag for system property I1ba9fc7bd:Add systrace tag for system property Bug: 193050299 Change-Id: I4d8c9e191e28cc99abc4f80600405bfc1b7e48b6 Merged-In: I4d8c9e191e28cc99abc4f80600405bfc1b7e48b6 Test: build and boot a device (cherry picked from commit dc5577c75e0c68de6069e3f14c887edea051ba97)
2021-07-21Add mechanism for a task's windows to be trusted overlays (SF)Winson Chung
- Add a layer state to indicate that this layer and its children in the hierarchy are trusted. This can only be set by callers holding ACCESS_SURFACE_FLINGER, and will be used for the PIP task layer to indicate that activities in PIP are trusted (as they are controlled only by the user and SystemUI) Bug: 191529039 Test: TBD Change-Id: Id92ccb087bd0d8dbaeeef3ba50b67fe015e53db8
2021-07-21Implement native PerformanceHint APIBo Liu
Test: None Bug: 194204196 Change-Id: Ied0068d5069522befd14a7ca60d4fc39b47754d1
2021-07-21[libbinder] Stop exporting std:: and android::sp symbolsPirama Arumuga Nainar
Bug: http://b/194163257 Bug: http://b/193221882 For each map file, do: $ grep -v -e ZNKSt -e ZKSt -e ZTVNSt -e android2sp $mapfile > $mapfile.new $ mv $mapfile.new $mapfile Test: build Change-Id: I99953556565d4044b9e25666a4372a920d874916 Merged-In: Iba9db702ca6f4a0e590e275bf80e770fb1c7361f
2021-07-21Merge "Fix caching flickering for unsecure displays" into sc-devTreeHugger Robot
2021-07-20Merge "Place mirrored layers offscreen instead of at root." into sc-devChavi Weingarten
2021-07-20Fix caching flickering for unsecure displaysAlec Mouri
Rendering a cached set needs to respect the secure mode for the display. Otherwise, compositing a secure layer onto an unsecure display would incorrectly leak information in a cached set. Bug: 193103018 Test: Chrome in incognito mode and verify that both screenrecord and simulating a virtual insecure display does not leak Chrome's content. Change-Id: I6d43e1c7de41f113477d9928b91ee0b286249751
2021-07-20Merge "SF: fix expected vsync time when changing work duration" into sc-devAdy Abraham
2021-07-20Place mirrored layers offscreen instead of at root.chaviw
Mirrored Layers should never be placed at the root of the layer hierarchy. Instead, they should be created offscreen and allow the caller to place the layer where they want in the hierarchy. This behavior was changed with the introduction of LayerCreatedState. Send placeAtRoot flag when creating a layer to allow different create callpoints to specify whether they want the layer created to be placed at the root. Test: Window Magnification no longer flickers. Test: MirrorLayerTest Fixes: 192536474 Change-Id: I08f47b1b1f19b7c655c3687cb4c1fa64844e2cc5
2021-07-19SF: fix expected vsync time when changing work durationAdy Abraham
When changing the work duration for a scheduled callback, we should apply it on the next frame only if we would skip a callback call. This change fixes the condition where we apply a different work duration that doesn't change the wake up time but rather changes the expected vsync time. Test: TouchLatency bouncy ball + expand notification shade Bug: 191969790 Change-Id: I067693fe361200a6f899bd81b74d8a1a155a452d
2021-07-19Merge "SF: allow more than one client to use eEarly[Start|End] flags" into ↵Ady Abraham
sc-dev
2021-07-19SF: allow more than one client to use eEarly[Start|End] flagsAdy Abraham
Bug: 191969790 Test: SF unit tests Change-Id: I0a21600eba986857e0231e02cb4d59fb108e9bd3 Merged-In: I0a21600eba986857e0231e02cb4d59fb108e9bd3
2021-07-17Merge "Don't set the visibleRegion dirty bit if blur regions are changing" ↵TreeHugger Robot
into sc-dev
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-27 19:47:33 +0000