Age | Commit message (Collapse) | Author |
|
Change-Id: Iaf796d8002f958451ecfc7aa842efee1cc2c717a
|
|
P: GraphicBuffer::lock(uint32_t inUsage, void** vaddr);
Q: GraphicBuffer::lock(uint32_t inUsage, void** vaddr, int32_t* outBytesPerPixel, int32_t* outBytesPerStride);
Error: cannot locate symbol "_ZN7android13GraphicBuffer4lockEjPPv" referenced by "/vendor/lib/hw/camera.sdm660.so"
Change-Id: I1c1fe66f3f73149ced601eae87b970ce392d50ee
|
|
* This lib is creating troubles on android 10 requiring old libs in vendor
* Other than that, it's the only culprit for vndk runtime being kept disabled
* Nuke this lib via a empty shim providing the symbols to the camera hal
Change-Id: Ia844e973299d3e1be0a37473e76325be1828415d
|
|
Change-Id: Ibdd8cfad8fa26b147d1c318eb43e4bf181ae4037
|
|
Change-Id: I4251b3853d00308dbd988625f8e7466a66b823fa
Signed-off-by: Akhil Narang <akhilnarang.1999@gmail.com>
|
|
Since lineageos 15.1 the power hal doesn't use the
perf_lock_use_profile() method anymore.
It was used to apply performance profiles.
On startup the perfd daemon is looking for at least
one profile which is used as default.
So there is only a perf-profiles0.conf to make the
daemon happy.
Removes log spam:
E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
Change-Id: I170cda016f99ab2ab00fbefe78ddde9757235c44
|
|
Change-Id: If64a95ae79bb74721731ebf2354fe6b5e0aa09e8
|
|
Change-Id: I903039730f4181f6a326f28e0ea212db68bdabcc
|