- Mar 20, 2024
-
-
Dominik Laskowski authored
am skip reason: Merged-In Ie1b27e81d860a709c85651f068fedb2b496861de with SHA-1 9e88d62f is already in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/26635668 Change-Id: I7eb98f2ceb134c2ee407fce070a94d9d9a207a0c 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/+/3001677 Change-Id: Iafc79576c0aefd8ed2d3ac0382d02097fbd08b0c 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/+/3001677 Change-Id: I30720c7fcc7fcbe98d782c2bdfb9eefcc05de33d Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
-
Treehugger Robot authored
am skip reason: Merged-In I3261c7f2245fcb64c3e79bb3dcb21f1b0e44a395 with SHA-1 af854add is already in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/26633536 Change-Id: Ia51c6402e4e05a83f5c77760c91fd4244efaa3f4 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Ying Wei authored
am skip reason: Merged-In I3261c7f2245fcb64c3e79bb3dcb21f1b0e44a395 with SHA-1 af854add is already in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/26633536 Change-Id: Ib04bf828ee610956d6200837ea800710de9b718d Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Devin Moore authored
am skip reason: Merged-In I4bc27098f09213564e4ec39036783b1a853a11b3 with SHA-1 eb653ee3 is already in history Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/26633847 Change-Id: I4510fcfe468e326e504bdaedc109f657141049ff Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
-
Justin Yun authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/2995998 Change-Id: I576e48d60586b7ffcb7ee57f9d58eab3368a9855 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Justin Yun authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/2995998 Change-Id: I724dad189f6c1706e69dd2d5da509ff52b365858 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Justin Yun authored
-
- Mar 19, 2024
-
-
Prabir Pradhan authored
-
Treehugger Robot authored
-
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 Merged-In: Ie1b27e81d860a709c85651f068fedb2b496861de
-
Vishnu Nair authored
Fixes: 329247258 Test: presubmit Change-Id: I680207e5ed7e4c7cd9fba9b502b3caeffa415c55
-
Zimuzo Ezeozue authored
-
Treehugger Robot authored
-
Dominik Laskowski authored
-
Prabir Pradhan authored
InputThread stops when its destructor is called. Initialize it last in ThreadedBackend so that it is the first thing to be destructed. This will guarantee the thread will not access other members that have already been destructed. Bug: 330211703 Change-Id: Ia50585d8276fe87d40d5528b3eb9480a64ea9854 Test: None
-
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
-
Devin Moore authored
Test: lunch aosp_cf_x86_64_only_phone-next-userdebug Test: VtsHalWifiSupplicantStaNetworkTargetTest Bug: 328328863 (cherry picked from https://android-review.googlesource.com/q/commit:eb653ee3aeaebc02c3439655673b135d397ecdec) Merged-In: I4bc27098f09213564e4ec39036783b1a853a11b3 Change-Id: I4bc27098f09213564e4ec39036783b1a853a11b3
-
Zimuzo Ezeozue authored
83483148 Change-Id: I9e37dbb1e6396a8456c57df68932c96dc289d804 Bug: 330172681
-
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 (cherry picked from commit af854add) Merged-In: I3261c7f2245fcb64c3e79bb3dcb21f1b0e44a395
-
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
-
Justin Yun authored
llndk-versioning.h provides __INTRODUCED_IN_LLNDK and API_LEVEL_AT_LEAST macros. But this header is not availabel in NDK build. It must be included conditionally for the NDK headers. Bug: 302113279 Test: build trunk-staging and next configurations Change-Id: I3294ff7f27ad9baaabd4a76f3f4faa10fe2d8f49
-
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>
-