DolbyAtmos-RC1_debug and ACDB-0.47 are working on my OP6T running OxygenOS 10.3.5 without a custom kernel.
Also DolbyAtmos-RC1_debug2 and ACDB-0.48 are working fine on my OP6T running OxygenOS 10.3.5 without a custom kernel.
It a vendor thingy! Basically pixen using oos as vendor that why it doesn't has that high brightness! Other rom dev just refused to use that? make Sense??Atmos does work on OOS and PiXeN rom without the high brightness bug that occurs on other 6t roms. Far as I know PiXeN and OOS are the only roms that don't have that bug where your brightness auto sets to max and won't turn down. Hopefully more roms will use whatever method the PiXeN developer used to get around this. ?
So recently @guitardedhero release and version of Dolby atmos for android Pie and i was excite about it but it only for for android pie only,so i try downgrade back to 9.0.17 but apparently the mod cause the phone go straight to crashdump mode and like hour ago he release couple more version but i was already on android 10 but after messing around with flash script i was able flash it on OOS10 imma attach the file i mod here for specific only for OOS10 only since this the only version that work flawless on OOS10 other test version i try they either force close the app or audio loss, highly recommended flash it along with Ainur Narsil---haven't test with other mod yet but in my opinion Dolby itself already better
UPDATED: *FOR THE PEOPLE ON LATEST 10.3.1 IF YOU EXPERIENCE FORCE CLOSE PLEASE USED CUSTOM KERNEL!*
UPDATE: latest Dolby Port and added Dolby from Motorola One Power also updated Dolby|Atmos Redux to latest!
@guitardedhero (for The Port)
-Me (for testing and mod the file to work on OOS10)
-Dolby (for Dolby Atmos)
I was reading through a lot of that thread and it looks like it's still based for pie and there was a section in there saying that you have to change your build prop setting to SDK level 28 if you are on oxygen 10 and Android 10 you'll be SDK 29 so I was getting force closes and I took a big risk when do the build prop edited my SDK level 228 and went straight into a bootloop. So I had to actually do a factory reset. I then restore from twrp, but I screwed up and restored everything what I should have just done a system and data restore only because then I did a soft brick and had to use the MSM tool and start all over again at Android 9! Lol.. so I know guitardedhero was making special media files for audio library they were . so extensions... I'm going to keep digging because on Android 10 I've got ice sound working which is an Asus driver and I can even change the four configurations as well as the 11 different sound profiles fall through terminal emulator. I also have a flashable DTS 2.0