Sony 1.5#2
Open
StevenToker wants to merge 14 commits into
Open
Conversation
commits include Ghosuto - dolby: Redesign dolby interface dolby: Add Carousel Profile Selector dolby: Added border stroke to selected profile option dolby: Switch to interactive frequency response curve kenway214 - dolby: add selectable bass curves and curve-based EQ processing dolby: enhance audio controls with treble tuning dolby: add new EQ presets and extend gain range to ±15dB picked from : https://github.com/Pong-Development/hardware_dolby Co-authored-by: kenway214 <kenway214@outlook.com> Signed-off-by: Ghosuto <clash.raja10@gmail.com>
Signed-off-by: Ghosuto <clash.raja10@gmail.com>
- like a16 compose qs tiles Signed-off-by: Ghosuto <clash.raja10@gmail.com>
Signed-off-by: Ghosuto <clash.raja10@gmail.com>
fix - Pong-Development/hardware_dolby@69fdd6c Signed-off-by: Ghosuto <clash.raja10@gmail.com>
Signed-off-by: Ghosuto <clash.raja10@gmail.com>
- Switch between og slider and curve Signed-off-by: Ghosuto <clash.raja10@gmail.com>
- Too bright in some monet colors Signed-off-by: Ghosuto <clash.raja10@gmail.com>
Signed-off-by: Ghosuto <clash.raja10@gmail.com>
Change-Id: I23f9dd5235d84696dd77ee1442889e8450e792e4
* Blobs taken from Sony pdx2** Change-Id: Ifca8bc0df1ddffea21f177586a3072e0b54fd200
- Some devices get this ERROR: files are incompatible: The following instances are in the device manifest but not specified in framework compatibility matrix: Suggested fix: 1. Update deprecated HALs to the latest version. 2. Check for any typos in device manifest or framework compatibility matrices with FCM version >= 6. 3. For new platform HALs, add them to any framework compatibility matrix with FCM version >= 6 where applicable. 4. For device-specific HALs, add to DEVICE_FRAMEWORK_COMPATIBILITY_MATRIX_FILE or DEVICE_PRODUCT_COMPATIBILITY_MATRIX_FILE.: Success Change-Id: I108fbcb4a1b345dbfd3fd41387f3ce9da6be7057
* Extract From https://dumps.tadiphone.dev/dumps/sony/pdx237/-/tree/sssi-user-14-67.1.A.2.229-1-release-keys?ref_type=heads Change-Id: I5a9dbb7eafdbaf3093e08396be291db815fbeafe
>> Needed for Spatial Audio Tested and now it's working with supported content before it was placebo xD << - ee1566d Change-Id: Ia565fa0e3f07acd02d33492a72bf9921e9542847
Contributor
|
i don't want to add this here so i already separated it |
LeDrew2017
pushed a commit
to LeDrew2017/hardware_dolby
that referenced
this pull request
May 7, 2026
08-25 13:26:29.598 1006 1006 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 1006 (vendor.dolby.me), pid 1006 (vendor.dolby.me) 08-25 13:26:29.731 3084 3084 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 08-25 13:26:29.731 3084 3084 F DEBUG : crDroid Version: '11.8' 08-25 13:26:29.731 3084 3084 F DEBUG : Build fingerprint: 'Xiaomi/vili/vili:14/UKQ1.231207.002/V816.0.10.0.UKDMIXM:user/release-keys' 08-25 13:26:29.731 3084 3084 F DEBUG : Revision: '0' 08-25 13:26:29.731 3084 3084 F DEBUG : ABI: 'arm64' 08-25 13:26:29.731 3084 3084 F DEBUG : Timestamp: 2025-08-25 13:26:29.665897496+0530 08-25 13:26:29.731 3084 3084 F DEBUG : Process uptime: 10s 08-25 13:26:29.731 3084 3084 F DEBUG : Cmdline: /vendor/bin/hw/vendor.dolby.media.c2@1.0-service 08-25 13:26:29.731 3084 3084 F DEBUG : pid: 1006, tid: 1006, name: vendor.dolby.me >>> /vendor/bin/hw/vendor.dolby.media.c2@1.0-service <<< 08-25 13:26:29.731 3084 3084 F DEBUG : uid: 1046 08-25 13:26:29.731 3084 3084 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : Cause: null pointer dereference 08-25 13:26:29.731 3084 3084 F DEBUG : x0 b400006f05b52fc0 x1 0000007fc905ed10 x2 0000006f45b59a90 x3 0000007fc905ecd8 08-25 13:26:29.731 3084 3084 F DEBUG : x4 0000000000000028 x5 0200006ef5b52470 x6 0000000000000000 x7 0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : x8 00000000ffffffff x9 00000000eff00000 x10 0000006fe69e4fa4 x11 0000000012b97fad 08-25 13:26:29.731 3084 3084 F DEBUG : x12 0000000000028003 x13 b400006ef5b528e0 x14 0000000000000024 x15 000000000000005f 08-25 13:26:29.731 3084 3084 F DEBUG : x16 0000006fe5ebd230 x17 0000006fede1ca84 x18 0000006fef730000 x19 0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : x20 b400006f05b52eb0 x21 0000006d55852090 x22 0000006fef2fff00 x23 0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : x24 0000006fef2fff00 x25 b400006d55b59140 x26 0000000000000001 x27 0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : x28 0000000000000000 x29 0000007fc905ece0 08-25 13:26:29.731 3084 3084 F DEBUG : lr 0000006fe5e915f4 sp 0000007fc905ece0 pc 0000006fede1caa0 pst 0000000080001000 08-25 13:26:29.731 3084 3084 F DEBUG : 7 total frames 08-25 13:26:29.731 3084 3084 F DEBUG : backtrace: 08-25 13:26:29.731 3084 3084 F DEBUG : #00 pc 0000000000010aa0 /vendor/lib64/libutils.so (android::RefBase::decStrong(void const*) const+28) (BuildId: 2fd112063e39cb6f651b185f9e6234f2) 08-25 13:26:29.731 3084 3084 F DEBUG : swiitch-OFF-Lab#1 pc 00000000000515f0 /vendor/lib64/android.hardware.media.c2@1.0.so (android::hardware::media::c2::V1_0::BnHwComponentStore::_hidl_createInterface(android::hidl::base::V1_0::BnHwBase*, android::hardware::Parcel const&, android::hardware::Parcel*, std::__1::function<void (android::hardware::Parcel&)>)+376) (BuildId: f0d25f49428387d313920490e7ec7c8c) 08-25 13:26:29.731 3084 3084 F DEBUG : swiitch-OFF-Lab#2 pc 00000000000525f0 /vendor/lib64/android.hardware.media.c2@1.0.so (android::hardware::media::c2::V1_0::BnHwComponentStore::onTransact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+1004) (BuildId: f0d25f49428387d313920490e7ec7c8c) 08-25 13:26:29.731 3084 3084 F DEBUG : swiitch-OFF-Lab#3 pc 000000000008ab7c /vendor/lib64/libhidlbase.so (android::hardware::BHwBinder::transact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+92) (BuildId: 1d845c84de7e27fc2c78f04ee8f4aae0) 08-25 13:26:29.731 3084 3084 F DEBUG : #04 pc 0000000000042eac /vendor/lib64/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+1344) (BuildId: 1d845c84de7e27fc2c78f04ee8f4aae0) 08-25 13:26:29.731 3084 3084 F DEBUG : #05 pc 000000000000124c /vendor/bin/hw/vendor.dolby.media.c2@1.0-service (main+500) (BuildId: 394e52c5b5064b9f64c91bd2d615f078) 08-25 13:26:29.731 3084 3084 F DEBUG : #06 pc 0000000000055160 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+116) (BuildId: b310372d5ddccd24fca9f3a465bff80c)
LeDrew2017
pushed a commit
to LeDrew2017/hardware_dolby
that referenced
this pull request
May 7, 2026
08-25 13:26:29.598 1006 1006 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 1006 (vendor.dolby.me), pid 1006 (vendor.dolby.me) 08-25 13:26:29.731 3084 3084 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 08-25 13:26:29.731 3084 3084 F DEBUG : crDroid Version: '11.8' 08-25 13:26:29.731 3084 3084 F DEBUG : Build fingerprint: 'Xiaomi/vili/vili:14/UKQ1.231207.002/V816.0.10.0.UKDMIXM:user/release-keys' 08-25 13:26:29.731 3084 3084 F DEBUG : Revision: '0' 08-25 13:26:29.731 3084 3084 F DEBUG : ABI: 'arm64' 08-25 13:26:29.731 3084 3084 F DEBUG : Timestamp: 2025-08-25 13:26:29.665897496+0530 08-25 13:26:29.731 3084 3084 F DEBUG : Process uptime: 10s 08-25 13:26:29.731 3084 3084 F DEBUG : Cmdline: /vendor/bin/hw/vendor.dolby.media.c2@1.0-service 08-25 13:26:29.731 3084 3084 F DEBUG : pid: 1006, tid: 1006, name: vendor.dolby.me >>> /vendor/bin/hw/vendor.dolby.media.c2@1.0-service <<< 08-25 13:26:29.731 3084 3084 F DEBUG : uid: 1046 08-25 13:26:29.731 3084 3084 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : Cause: null pointer dereference 08-25 13:26:29.731 3084 3084 F DEBUG : x0 b400006f05b52fc0 x1 0000007fc905ed10 x2 0000006f45b59a90 x3 0000007fc905ecd8 08-25 13:26:29.731 3084 3084 F DEBUG : x4 0000000000000028 x5 0200006ef5b52470 x6 0000000000000000 x7 0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : x8 00000000ffffffff x9 00000000eff00000 x10 0000006fe69e4fa4 x11 0000000012b97fad 08-25 13:26:29.731 3084 3084 F DEBUG : x12 0000000000028003 x13 b400006ef5b528e0 x14 0000000000000024 x15 000000000000005f 08-25 13:26:29.731 3084 3084 F DEBUG : x16 0000006fe5ebd230 x17 0000006fede1ca84 x18 0000006fef730000 x19 0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : x20 b400006f05b52eb0 x21 0000006d55852090 x22 0000006fef2fff00 x23 0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : x24 0000006fef2fff00 x25 b400006d55b59140 x26 0000000000000001 x27 0000000000000000 08-25 13:26:29.731 3084 3084 F DEBUG : x28 0000000000000000 x29 0000007fc905ece0 08-25 13:26:29.731 3084 3084 F DEBUG : lr 0000006fe5e915f4 sp 0000007fc905ece0 pc 0000006fede1caa0 pst 0000000080001000 08-25 13:26:29.731 3084 3084 F DEBUG : 7 total frames 08-25 13:26:29.731 3084 3084 F DEBUG : backtrace: 08-25 13:26:29.731 3084 3084 F DEBUG : #00 pc 0000000000010aa0 /vendor/lib64/libutils.so (android::RefBase::decStrong(void const*) const+28) (BuildId: 2fd112063e39cb6f651b185f9e6234f2) 08-25 13:26:29.731 3084 3084 F DEBUG : swiitch-OFF-Lab#1 pc 00000000000515f0 /vendor/lib64/android.hardware.media.c2@1.0.so (android::hardware::media::c2::V1_0::BnHwComponentStore::_hidl_createInterface(android::hidl::base::V1_0::BnHwBase*, android::hardware::Parcel const&, android::hardware::Parcel*, std::__1::function<void (android::hardware::Parcel&)>)+376) (BuildId: f0d25f49428387d313920490e7ec7c8c) 08-25 13:26:29.731 3084 3084 F DEBUG : swiitch-OFF-Lab#2 pc 00000000000525f0 /vendor/lib64/android.hardware.media.c2@1.0.so (android::hardware::media::c2::V1_0::BnHwComponentStore::onTransact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+1004) (BuildId: f0d25f49428387d313920490e7ec7c8c) 08-25 13:26:29.731 3084 3084 F DEBUG : swiitch-OFF-Lab#3 pc 000000000008ab7c /vendor/lib64/libhidlbase.so (android::hardware::BHwBinder::transact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+92) (BuildId: 1d845c84de7e27fc2c78f04ee8f4aae0) 08-25 13:26:29.731 3084 3084 F DEBUG : #04 pc 0000000000042eac /vendor/lib64/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+1344) (BuildId: 1d845c84de7e27fc2c78f04ee8f4aae0) 08-25 13:26:29.731 3084 3084 F DEBUG : #05 pc 000000000000124c /vendor/bin/hw/vendor.dolby.media.c2@1.0-service (main+500) (BuildId: 394e52c5b5064b9f64c91bd2d615f078) 08-25 13:26:29.731 3084 3084 F DEBUG : #06 pc 0000000000055160 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+116) (BuildId: b310372d5ddccd24fca9f3a465bff80c)
swiitchOFF
pushed a commit
that referenced
this pull request
Jun 7, 2026
Commit ("Introduce a dependency monitor for fences") added new
members to the GraphicBuffer struct, increasing its size from 0x100 to
0xd30. libdolbyvision.so creates GraphicBuffer instances using
"new GraphicBuffer(..)", which encodes the allocation size at compile
time. As a result, only 0x100 bytes are allocated while the runtime
GraphicBuffer implementation requires 0xd30 bytes.
When the object is destroyed, GraphicBuffer::~GraphicBuffer() attempts
to access and destruct the newly added members, resulting in memory
access outside the allocated object and a crash during Dolby Vision
playback.
F DEBUG : backtrace:
F DEBUG : #00 pc 000000000003ab6c /vendor/lib64/libui.so (android::GraphicBuffer::~GraphicBuffer()+800)
F DEBUG : #1 pc 0000000000050cd0 /vendor/lib64/libui.so (android::GraphicBuffer::~GraphicBuffer()+16)
F DEBUG : #2 pc 0000000000010a20 /vendor/lib64/libutils.so (android::RefBase::decStrong(void const*) const+196)
F DEBUG : #3 pc 000000000000cd4c /vendor/lib64/egl/eglSubDriverAndroid.so
F DEBUG : #04 pc 0000000000002404 /vendor/lib64/c2.dolby.egl.so (EGLProcessing::setupGraphics(...)+632)
F DEBUG : #05 pc 000000000002fea4 /vendor/lib64/libdolbyvision.so (android::PixelProcessingImpl::handleFrame(unsigned long)+2508)
[1]: LineageOS/android_frameworks_native@df868ba
Patch the allocation size from 0x100 to 0xd30 to match the current
GraphicBuffer implementation and restore Dolby Vision playback.
Change-Id: I353d309d51164a07f9ff5af85ba7f5206e7a4038
Signed-off-by: pabloescobar-reborn <yogivangala07@gmail.com>
swiitchOFF
pushed a commit
that referenced
this pull request
Jun 7, 2026
Commit ("Introduce a dependency monitor for fences") added new
members to the GraphicBuffer struct, increasing its size from 0x100 to
0xd30. libdolbyvision.so creates GraphicBuffer instances using
"new GraphicBuffer(..)", which encodes the allocation size at compile
time. As a result, only 0x100 bytes are allocated while the runtime
GraphicBuffer implementation requires 0xd30 bytes.
When the object is destroyed, GraphicBuffer::~GraphicBuffer() attempts
to access and destruct the newly added members, resulting in memory
access outside the allocated object and a crash during Dolby Vision
playback.
F DEBUG : backtrace:
F DEBUG : #00 pc 000000000003ab6c /vendor/lib64/libui.so (android::GraphicBuffer::~GraphicBuffer()+800)
F DEBUG : #1 pc 0000000000050cd0 /vendor/lib64/libui.so (android::GraphicBuffer::~GraphicBuffer()+16)
F DEBUG : #2 pc 0000000000010a20 /vendor/lib64/libutils.so (android::RefBase::decStrong(void const*) const+196)
F DEBUG : #3 pc 000000000000cd4c /vendor/lib64/egl/eglSubDriverAndroid.so
F DEBUG : #04 pc 0000000000002404 /vendor/lib64/c2.dolby.egl.so (EGLProcessing::setupGraphics(...)+632)
F DEBUG : #05 pc 000000000002fea4 /vendor/lib64/libdolbyvision.so (android::PixelProcessingImpl::handleFrame(unsigned long)+2508)
[1]: LineageOS/android_frameworks_native@df868ba
Patch the allocation size from 0x100 to 0xd30 to match the current
GraphicBuffer implementation and restore Dolby Vision playback.
Change-Id: I353d309d51164a07f9ff5af85ba7f5206e7a4038
Signed-off-by: pabloescobar-reborn <yogivangala07@gmail.com>
swiitchOFF
pushed a commit
that referenced
this pull request
Jun 7, 2026
Commit ("Introduce a dependency monitor for fences") added new
members to the GraphicBuffer struct, increasing its size from 0x100 to
0xd30. libdolbyvision.so creates GraphicBuffer instances using
"new GraphicBuffer(..)", which encodes the allocation size at compile
time. As a result, only 0x100 bytes are allocated while the runtime
GraphicBuffer implementation requires 0xd30 bytes.
When the object is destroyed, GraphicBuffer::~GraphicBuffer() attempts
to access and destruct the newly added members, resulting in memory
access outside the allocated object and a crash during Dolby Vision
playback.
F DEBUG : backtrace:
F DEBUG : #00 pc 000000000003ab6c /vendor/lib64/libui.so (android::GraphicBuffer::~GraphicBuffer()+800)
F DEBUG : #1 pc 0000000000050cd0 /vendor/lib64/libui.so (android::GraphicBuffer::~GraphicBuffer()+16)
F DEBUG : #2 pc 0000000000010a20 /vendor/lib64/libutils.so (android::RefBase::decStrong(void const*) const+196)
F DEBUG : #3 pc 000000000000cd4c /vendor/lib64/egl/eglSubDriverAndroid.so
F DEBUG : #04 pc 0000000000002404 /vendor/lib64/c2.dolby.egl.so (EGLProcessing::setupGraphics(...)+632)
F DEBUG : #05 pc 000000000002fea4 /vendor/lib64/libdolbyvision.so (android::PixelProcessingImpl::handleFrame(unsigned long)+2508)
[1]: LineageOS/android_frameworks_native@df868ba
Patch the allocation size from 0x100 to 0xd30 to match the current
GraphicBuffer implementation and restore Dolby Vision playback.
Change-Id: I353d309d51164a07f9ff5af85ba7f5206e7a4038
Signed-off-by: pabloescobar-reborn <yogivangala07@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.