- Mar 19, 2024
-
-
Treehugger Robot authored
-
Vishnu Nair authored
Fixes: 329247258 Test: presubmit Change-Id: I680207e5ed7e4c7cd9fba9b502b3caeffa415c55
-
Zimuzo Ezeozue authored
-
Treehugger Robot authored
-
Dominik Laskowski authored
-
Nolan Scobie authored
This means AutoBackendTexture is not aware of backend-specific texture type and API details, and will be able to accept either a Ganesh or Graphite variant of SkiaBackendTexture. Also delegated SkiaBackendTexture creation to SkiaGpuContext, so that backend-specific contexts handle creating backend-specifc textures. Test: manual validation (GL+VK) & existing tests (refactor) Bug: b/293371537 Change-Id: Ia65306cc825b71fe0b89c7f8545ce1c71a81d86b
-
Zimuzo Ezeozue authored
83483148 Change-Id: I9e37dbb1e6396a8456c57df68932c96dc289d804 Bug: 330172681
-
Dominik Laskowski authored
Multi-display refresh rate selection was flawed: The scheduler runs the refresh rate selection algorithm for each display, and then filters the candidate modes of each follower to match the pacesetter's refresh rate. This means that: 1. The followers incorrectly consider refresh rates that don't match the pacesetter. Because the DM-specified constraint is [59, 61] Hz, some situations caused selection of a fractional rate (e.g. 59.94) instead of 60 on certain external displays. The result would be black screens for several seconds due to mode sets if the selection was not stable. 2. The followers incorrectly evaluate heuristics that should only affect the pacesetter, e.g. per-surface votes, global signals. Fix this by teaching RefreshRateSelector about follower displays. Foldables also benefit from no longer running the algorithm twice. Fixes: 324188430 Bug: 329111930 Test: No black screen for 4 seconds upon rotating mirrored YouTube. Test: 60+60 still works on foldables. Test: RefreshRateSelectorTest.pacesetterConsidered Change-Id: Ie1b27e81d860a709c85651f068fedb2b496861de
-
Gavin Corkery authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3000937 Change-Id: Id963ff0ee27d0dd3e5839a1f7b0e05a741c6a2f2 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Gavin Corkery authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3000937 Change-Id: I7693472656bccc35cf81c1c151fbba9c73849c62 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Gavin Corkery authored
-
Treehugger Robot authored
-
Treehugger Robot authored
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3004577 Change-Id: Ieb13d60e2406d3570f53af6499bcb284597ec1ad Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3004577 Change-Id: I753d9ac2ffc51321b664ecc7ed6e5a0f1cf6b11e Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
- Mar 18, 2024
-
-
Ying Wei authored
-
Treehugger Robot authored
[automerger skipped] Merge "Check mm_events persistent property after persistent properties are ready during boot." into main am: 80f53f4d am: bc0ee118 -s ours am skip reason: Merged-In I091ca35f48e4baf8b6b5c24fba325f1dcae6b8b7 with SHA-1 854ed748 is already in history Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/2954641 Change-Id: Id2d4c71d5138f819951c554dad7671b192ac8179 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
-
Treehugger Robot authored
Merge "Check mm_events persistent property after persistent properties are ready during boot." into main am: 80f53f4d Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/2954641 Change-Id: Ia097616f74fc190e14718d89b5da9671844fcaf1 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
Merge "Check mm_events persistent property after persistent properties are ready during boot." into main
-
Treehugger Robot authored
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3000924 Change-Id: I73c8b65b5a711212c5a3dcd8ec142dac7cead5b9 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3000924 Change-Id: I0d70ccf91a911028b20bdc4071537054180e179a Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Cody Heiner authored
Now that libinput is no longer run in a bootstrap process, we can switch the stats logging library to the standard version. This version is host supported, so we now also remove the `#ifdef __ANDROID__` include guards. Test: m checkinput Test: flash to device, run `statsd_testdrive 718`, then trigger stylus prediction → reported metrics are present and reasonable Bug: 311066949 Change-Id: I04e6f6906e556f4f5a71b711c6ef29d8aa6f3501
-
Prabir Pradhan authored
PointerChoreographer does not yet support drawing tablets. Add support by creating a MousePointerController for each drawing tablet that is connected. Use a MousePointerController so that the default icon is the same as for a mouse (arrow) instead of for a stylus (no icon). The icon will only show while the stylus is hovering or touching. Bug: 329849066 Test: atest inputflinger_tests Change-Id: I0cbb4a8efc8fd5e50ddfdad2b60df0195a3dce16
-
Treehugger Robot authored
-
Yifan Hong authored
Fix this error: Abort message: 'Check failed: bytes != nullptr || len == 0 0x0 32' This bug is introduced by the change below. !hashRet.isOk() should have a break; in it like the other error cases. The change below added this code after the error which used to be the end of the statement. Bug: 329190736 Fixes: b670dd7e ("lshal: Fix mem invalid access (timeoutIPC callers)") Test: TH Change-Id: Iada52b2ca033105962727fcccf651fbb5bdd5736
-
Ying Wei authored
When SF fps doesn't match vsync rate (either due to vrr or frame rate override), the frame interval calculation in Scheduler should take this into account. Bug: 328352850 Test: atest CtsSurfaceControlTests Test: atest libsurfaceflinger_unittest Test: atest FrameRateOverrideTest Change-Id: I3261c7f2245fcb64c3e79bb3dcb21f1b0e44a395
-
Priyanka Advani authored
-
Priyanka Advani authored
Revert submission 26575765-is_tag_enabled Reason for revert: Droid-monitored triggered revert due to breakage in b/330172681. Will be verifying through ABTD before submission. Reverted changes: /q/submissionid:26575765-is_tag_enabled Change-Id: I870c6e3edaada40e44ce843cb343619f73b1a42d
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3001065 Change-Id: Iada59c3076abdf746bb5506783d9259d65be094a Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/3001065 Change-Id: If13a5c5efc3103fd2ebfe6c0e2a4a168c34f657a Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Prabir Pradhan authored
-
Treehugger Robot authored
-
Zimuzo Ezeozue authored
-
- Mar 17, 2024
-
-
Manali Bhutiyani authored
-
- Mar 16, 2024
-
-
Chavi Weingarten authored
-
Chavi Weingarten authored
-
Treehugger Robot authored
-
- Mar 15, 2024
-
-
Krzysztof Kosiński authored
Protobuf 22.x no longer pulls in <set>, it needs to be included explicitly. Bug: 329747255 Test: presubmit Change-Id: I8c0b219322b10a655d5687c506d1047ddb8aa99e
-