mirror of
https://github.com/Evolution-X/hardware_interfaces
synced 2026-02-01 22:04:26 +00:00
944b68180b008456ed2eb4d4d329e33b19bd5166
On subsequent hotplug connected event for a display SurfaceFlinger destroys the previous framebuffers and recreates them. When the new buffers are created ComposerClient still holds a handle to the old buffers and they are not destroyed. This way the new framebuffers may get allocated on non continuous memory causing garbled screens for the user. This is already implemented for ComposerClient 2.1-2.3. In this CL only the behavior for ComposerClient 2.4 is changed. Test: manually flash a device Bug: 178785393 Change-Id: I6aa1243d61676c0a3d42cb7aecf19e6f8802cb1a
Merge "audio: Verify that VTS tests can work with vendor extensions" am:
a8b93afc00 am: a40f50ddc0 am: 5e8b252609
Merge "Skip radio VTS test cases on deprecated interfaces" am:
43175bec27 am: defdc18a9d am: 8718ed41fb
Merge "Make the tv tuner hal use libdmabufheap instead of libion" am:
5001056e0f am: 4448d5ff1e am: 5df8053163
Description
No description provided
Languages
C++
56.3%
AIDL
41.2%
C
1.5%
Rust
0.4%
Java
0.4%
Other
0.1%