yashsingh1/xdaforums huggingface dataset:
[Android Software Development] guitardedhero:
ACDB update to correct a few things and add support for up to 11 acdb.conf files per module when two or more effects require configuration.

# Audio Configuration Database
# acdb.conf
# gh

# acdb.conf is a module configuration file sourced by the ACDB module ( $MODPATH/acdb.conf ) to add or remove the configuration of audio libraries and effects to configurations included in this module - determined by the status of an installed Magisk module being installed, disabled, or uninstalled.

# A total of eleven (11) acdb.conf files are allowed to be sourced for each effect for modules requiring the configuration of two or more effects:

acdb.conf
acdb0.conf
acdb1.conf
acdb2.conf
acdb3.conf
acdb4.conf
acdb5.conf
acdb6.conf
acdb7.conf
acdb8.conf
acdb9.conf

# Simply insert the appropriate value for the properties below in $MODPATH/acdb.conf for consistent results:

libraryid=
libraryname=

effectid=
effectuuid=

musicstream=

# The only value acceptable for "musicstream=" is "true" as only the "effectid=" value has any effect here. Anything other than "true" indicates no "musicstream" effect is intended. Rare cases require such an effect, so only add "true" when functionality is compromised without a music stream effect for your effect.

# Values denoted as being "Flexible" indicate values that do not depend on a change in file name or file content.

# Values denoted as being "Restricted" indicate values that are determined by file name or file content.

# Values denoted as being "Fixed" indicate any deviation to the the single acceptable value will return a "False" condition or an empty value.

# Example:

# libraryid=v4a_fx <-- As found from v4a authors. Flexible

# libraryname=libv4a_fx_ics.so <-- As found from v4a authors. Restricted

# effectid=v4a_standard_fx <-- As found from v4a authors. Flexible

# effectuuid=41d3c987-e6cf-11e3-a88a-11aba5d5c51b <-- As found from v4a authors. Restricted

# musicstream=true <-- Unnecessary for v4a and only used for this example. Fixed

# equals:

# <library name="v4a_fx" path="libv4a_fx_ics.so"/>
# </libraries>

# <effect name="v4a_standard_fx" library="v4a_fx" uuid="41d3c987-e6cf-11e3-a88a-11aba5d5c51b"/>
# </effects

# <stream type="music">
# <apply effect="v4a_standard_fx"/>

# libraries {
# v4a_fx {
# path /vendor/lib/soundfx/libv4a_fx_ics.so
# }

# effects {
# v4a_standard_fx {
# library v4a_fx
# uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
# }

# music {
# v4a_standard_fx {
# }
[Android Software Development] guitardedhero:
Shout-out to my right-hand man for this testing phase - [MENTION=6320600]ban.codrut[/MENTION], for suggesting a unique name for the database generated in /data/vendor/dolby/.

This allows a native or otherwise existing Dolby system to have its own database as well, just like has already been done for dax-default.xml.

This build also has "musicstream=true" in acdb.conf to do a little testing for adding the effect to music stream post-processing.

ACDB update only corrects a minor, uneventful error during installation.
[Android Software Development] laugeek57:
Last axon9 works fine on OP7 rom Evolution X 4.1 unofficial...

But I have not tested on a clean installation to know if need that the One power motorola is installed before to allow turn on Dolby ...:highfive:
[Android Software Development] nycdiplomat:
Wanted to also report that the following work for me on A10 Bliss OP7 pro:

ACDB v0.34

Dolby 0.975

Viper 2.5.0.5

Thanks for your work on this. Sounds amazing!
[Android Software Development] Oblias:
I feel completely un-informed, even after reading, and re-reading the excellent and in-depth description of what ACDB is and what it does....

This ACDB.conf file the is referred to.... Is this a file that I need to edit manually or something, in order to get things working correctly on my OP6T? I mean, at this point, I'm not even sure of it's exact location on the OP6T. V4A and Dolby seem to be working now, but what do I know? Maybe they are not working at their full potential??

Is there somewhere that I can read/study on how to insure that the ACDB.conf file on my phone is up to par??
[Android Software Development] guitardedhero:
Absolutely fantastic questions. :good:

ACDB is a Magisk module still in beta and is intended to be a resource for devs preparing Magisk modules that rely on the configuration of one or more audio effects.

However, at this time, I require that the ACDB module itself to never be bundled with another installation and must only ever be installed by the end-user. This ensures the user is at least somewhat aware of the ACDB module being installed.

Modules with ACDB in the filename do not require the ACDB module to be installed at any point, but those modules will take full advantage of the ACDB module when it is present.

Modules relying on an audio effects configuration that do not take advantage of ACDB's convenience and efficiency by not including the acdb.conf in the $MODPATH (/data/adb/modules/<module>/) directory in the event that the ACDB module might be installed by the user at some point will be rendered broken until the dev or user prepares an adequate acdb.conf for the module or the ACDB module itself is uninstalled or removed.

Fortunately, the task of preparing an adequate acdb.conf requires only having access to the configuration of the pertinent audio effect(s) often found in audio_effects.xml and audio_effects.conf files online. I have always encouraged users to familiarize themselves with these files anyway.

So, for maximum effectiveness and consistency, a bit of inconvenience or unexpected results is simply unavoidable with Magisk modules potentially competing for their file(s) to win the "bind mount war" each boot. At least a solution is now available for a user to not have to wait for the dev to add support in almost all cases - cases where configuration details for an effect are available somewhere, primarily the effect UUID.
[Android Software Development] guitardedhero:
I think I can see version 1.0 up ahead...
[Android Software Development] Oblias:
Thank you. I believe my mind has gone from being twisted like a Chinese Finger Trap to now only being twisted as a pretzel. Progress, of sorts.

Case in point... I have 3 Magisk modules installed.. ACDB, Viperfx, and Dolbyatmos . I have located all 3 at the /data/adb/modules/<module>/ directories. However, none of the three have an acdb.conf file within their respective directories. From what I have read, and my limited understanding, at least two of them need that .conf file, viperfx and dolbyatmos.

According to your valuable information, in order for me to make an acdb.conf file for viperfx and for dolbyatmos I need 'access to the configuration of the pertinent audio effect(s) often found in audio_effects.xml and audio_effects.conf files online.'

At this point I once again fall flat on my face. I've googled for those files without success. Perhaps my search parameters are lacking... I don't know. If you could bear with me a bit longer, and point me in the right direction to those files for viperfx and dolbyatoms, I would be grateful!

From there, I do believe I can make the acdb.conf file using both your detailed instructions, and from looking at the example .conf file inside the ACDB.zip files you provide.

I appreciate your patience in this!!!!

---------- Post added at 10:43 PM ---------- Previous post was at 10:15 PM ----------

UPDATE: I have found 3 files that I believe to pertain to this issue of making an ACDB.conf file. Two were in system/system/vendor/etc/ named audio_effects.xml and audio_effects.conf . Then in the system/system/etc/ I found only 1 file named audio_effects.conf . So, I now have copies of those moved to a working directory. Those are the locations on my OnePlus 6T.

But when I open them to have a look, I feel like it's a requirement for me to be in possession of a Master's Degree in Nuclear Physics to decode what I'm seeing!

I have absolutely ZERO experience with audio mods at all (could you tell??) Is there not a straightforward way for a simple man such as myself to create the acdb.conf files needed? Is there not a 'no-brainer' way for me to create one each for viperfx and for dolbyatmos?? Or is it too early in the development stage for me to even contemplate trying??
[Android Software Development] guitardedhero:
You looked everywhere except in the zips I had just posted above, didn't you lol?
[Android Software Development] JakunTech1010:
OK Few quick questions thx:

1. What's the difference between ViperAtmos Redux and ViperAtmos Redux on ice?

2. Is it possible to add some switches in for sample: Bass enhancer, Volume Leveler, Surround Virtualized,...?

3. As seen on the previous DolbyAtmos build for Oreo, there are 2 missing profile: Game and Voice. Is it possible to re-add those cuz my main purpose for DolbyAtmos is Gaming ( and maybe Music too )?

4. Can ACDB work alongside AML?

5. Can ACDB support Android Version lower than 9.0 Pie (not really necessary to answer)?

Thanks if you can answer me with those question. :good:

Maybe some of those questions are already answered but I have no idea where.
[Android Software Development] Oblias:
Not true!! All I found were files with a byte size of 0 named "placeholder" .. in the acdc/system/etc and acdc/system/vendor/etc folders within the ACDB-0.4.zip file you made available.

Those do me no good, obviously, so I've been trying to experiment with the example files in the zip file you provided.

---------- Post added 02-23-2020 at 12:02 AM ---------- Previous post was 02-22-2020 at 11:46 PM ----------

UPDATE: Wait a minute here! I believe a light bulb just went off in my head.... a 25W light bulb, but a glimmer of light, none the less.... I was looking in the wrong zip file you were talking about. I just unzipped the DolbyAtmos-0.98-ACDB file, and there was, indeed, an acdb.conf file already there, and already configured with the uuid and all that lib location and name information...

So, what I'm seeing here is that I DON'T have to manually create an acdb.conf file for each Magisk module I have installed. You already have done that, and put it inside the installation zip for Dolby, V4A, or any of the others, right????

So, why have I been chasing my tail all night trying to figure this out. Why could you have not just told me "You, as the end user, need not be concerned about creating the acdb.conf file, it has already been done by the Dev., and will be automatically installed when run by Magisk" ???

Kinna cruel, don't you think?? :)
[Android Software Development] mrrocketdog:
if not in acdc/system/etc and not in acdc/system/vendor/etc folders ; there are always the ELO/system/etc , BTO/system/vendor/etc , U2/system/etc , KISS/system/etc or ABBA/system/vendor/etc. if you have this last mentioned , there is definitely an error. wipe cache & dalvik ; start over.:good:
[Android Software Development] guitardedhero:
I'm sorry, I felt that it would automatically be assumed that I would include everything necessary to support ACDB by having ACDB in the filename of those zips.

The reason I did not directly tell you where to look was because I believed you would "learn" more if finding it all on your own.

I pride myself on helping everyone the best that I can, and the very few times it might appear I am not quite as helpful as I could be or that I am even dismissive at times is because the user benefits more if looking just a bit closer than had I just attached an acdb.conf to the reply.
[Android Software Development] Oblias:
Hey, I made my last comment as a tongue-in-cheek kinna thing. I was in no way serious. I understand the concept of "Give a man a fish, feed him for a day. Teach a man to fish, feed him for life."

To be clear, I respect the work you are doing, and most greatly appreciate you sharing your efforts with anyone who cares to learn how to use the files!!

Keep on, keeping on! And btw, I miss Arkansas a LOT. I had a small horse ranch up in the Conway area for several years, and I truly miss the lifestyle, and the sort of people from there. Like no other on earth!! :)
[Android Software Development] guitardedhero:
I almost missed your post lol.

1. "on ICE" is merely a play on words describing ViPER|Atmos™ with an inclusion of the latest ICEsound from Asus Pie firmware.

2. Yes, but I cannot help but believe that those switches that are added would produce no effect. The effects for those switches comes from the effect libraries, which more often than not, require system properties to pass license checks that override existing system properties resulting with broken native device features for some users.

Once we hit version 1.0, we will begin playing around with all sorts of cool stuff, so don't worry.

3. Same as 2. but with no possibility to achieve what you are wanting. Those additional profiles will only come from an Android Pie or 10 Dolby implementation that has those. I am constantly checking for new/different Dolby systems.

4. I have not observed what happens when both are installed at the same time. It would be foolish of me to claim an outcome whatsoever. My best guess would be that it would be similar to rolling dice on a text book in your lap while driving a bit too quickly over speed bumps.

5. ACDB will support what Magisk allows a module zip to support at any given time.

:good:
[Android Software Development] guitardedhero:
For sure, I totally read you that way but wanted to ensure you and everyone else that I'll always help the best I can.

Crazy, I worked in Conway all of last week lol. How long has it been since you were last in Conway? It's grown so much.
[Android Software Development] Oblias:
I haven't been there in about 11 years now. Long time. My small ranch was actually up the road from Conway, in a small town named Greenbrier. I just didn't know if you would recognize that name or not... It was one of the most enjoyable periods of my life!!
[Android Software Development] guitardedhero:
Yes, I do know Greenbriar lol. Small world, ain't it lol?
[Android Software Development] Oblias:
It sure is!! And just think, your efforts bring us all together, where like-minded people can associate and benefit. Once again, thanks for ALL your efforts!!!!!!
[Android Software Development] celloh123:
Viperatmos redux acdb come with acdb preinstalled also will that work on 9 also also will that work with ainur narsil?

Edit: just uninstalled narsil, reboot installed acdb reboot, installed viperatmos redux on ice reboot

Viper drivers dont work and dolby atmos app crashes. Please help ASAP
[Android Software Development] JakunTech1010:
Thanks man. You've enchanted some light for those questions.

I've installed ViperAtmos Redux on Ice but Viper didn't work.
[Android Software Development] gokart2:
[MENTION=4445176]guitardedhero[/MENTION]

Dude, you are something else!

DolbyAtmos-axon9-0.965.zip is the first that UI has worked for me, Moto Z2 Force LOS 16. Feels like a birthday present. Thanks for being a badass audiophile with mad skills!
[Android Software Development] Oblias:
When I grab a new version of any of these files, ACDB, ViperFx, DolbyAtmos.... any of them, what is the correct way to update a module that is currently installed via Magisk? I know there is reference to this in the OP, but that was many many versions ago....

For example, I already have ADCB and ViperFx modules flashed thru Magisk. Now I've downloaded the newer versions. Can I just point Magisk at the new module and flash it, or should I remove the old module first, reboot, then flash the newer version?
[Android Software Development] EstherTakumi:
I just flash ACDB and Atmos through magisk then reboot, except Viper, that one I need to remove from magisk first. Then the next reboot, Im Flashing a new Viper version.
[Android Software Development] Oblias:
I'm doing my best to learn as I go here, so I'll ask you why you need to uninstall Viper before updating, and you don't have to uninstall Dolby before updating??
[Android Software Development] EstherTakumi:
I try once, it will say failed to install, because already got the current one installed. The module will install well, but not the viper app.
[Android Software Development] Oblias:
Makes sense. I appreciate the explanation! :)
[Android Software Development] ddloco:
I have a galaxy s9+ running Q rom and atmos installs but the app never opens got any suggestions please
[Android Software Development] JakunTech1010:
Grab a logcat for the app

Ensure there are no any equalizer installed ( For example: MusicFX, soundalive, AudioFX,... )

Try to reinstall and grab the installer log

Post all the log here so that guitardedhero can have a solutions for you.
[Android Software Development] situ1962:
Does Dolby Atmos work on Android 10?
[Android Software Development] Ronan Hansel:
Yes. It worked for me.
[Android Software Development] ifnkemlptr:
Can't install

Hi,

Tried to install it on Realme 3 pro, stock Pie.

But it failed, says it only for pie ROM.

Any clue?

one thing, when I tried to check audio_effects.xml in vendor folder...

the folder is only R/O. I never able to set is as R/W via root explorer.

thus, no Dolby mentioned within the xml.
[Android Software Development] ifnkemlptr:
Edit:

Here's attached the log.

My problem is the APK can't even open. See the attached pic too..

Hope for your suggestion
[Android Software Development] laugeek57:
Thanks for your great works GH

I tested on clean rom on N5X and OP7 v.098 works fine no needed flash other version :highfive:
[Android Software Development] danial.aw:
Just a question... I wanted to try this version out the OnePlus 7 has an in built version of Dolby... Should I freeze that before trying to run this?
[Android Software Development] guitardedhero:
Here's an interesting port zip I came up with today.

It's the Moto™ 1 Android 10 Dolby™ implementation that brings with it a third compatibility check that seems to be a "symbol" unique to Android 10 hardware libraries.

My TG testers have been clamoring all over Moto Dolby ports the last few days and this particular one seemed to be the favorite. I had ported it about three weeks ago but never tried it since I could not pass this third compatibility check with my OnePlus 5 on OOS Pie.

I had forgotten that detail when installing it earlier today, so when realizing I wasn't going to be able to check it out, I began to study the various Dolby implementations I currently have on my phone (I've easily surpassed 100 different Dolby systems since October, but only have room for a small assortment at any time) and prepared a vendor bundle of Dolby content that only needs the two compatibility checks that have been in place for every port since day one.

This custom bundle is probably 80%+ OnePlus 7t Pro Android 10 with Razer 2 Android Pie for the remaining ~20%.

This custom bundle will be installed for "custom compatibility" cases while the full Moto 1 Android 10 port will be installed for "full compatibility" cases.

The two apk's (I have not merged them just yet) are the Moto 1 Android 10 apk's and install in both compatibility cases. Everything else in the port - custom and Moto 1 bundles, included - have already received the customary treatment for maximum compatibility with native Dolby systems and most other OEM audio solutions like SoundAlive.

At any rate, I am really excited about the custom compatibility port. It sounds incredible. Unfortunately, I have no way of comparing both installation results, but I'm sure many of you do, so I'm anxious to hear what you guys think.

Neverending script tweaking/adjustment still takes place as usual, so I anticipate at least some of you to find success here when success seemed hard to come by previously. ACDB has seen some further adjustments as well.

Seems like it's been a while since you guys had something new to play with so I wanted to get this to you as soon as possible and with some clarity on what may be noticed as an introduction of more than one installation result since testing began.

:good:
[Android Software Development] guitardedhero:
I do not pursue projects that require a compromise for the user and their device. A lot of effort is devoted to this very scenario, so I encourage you to test the installation on the state of your device which you prefer.

Experiment with both and be sure to look for any sign of reduced functionality with your native Dolby implementation since you are likely familiar with it.

You may find that you like one or the other more than when both are enabled and processing, but certainly give it a whirl and let me know what you think, and if anything needs to be looked at if some compromise is noticed on your end. :good:
[Android Software Development] marklcp:
Thanks for providing such a good Dolby. I am an htc u11 + mobile phone, Android P, and it can be used with 0.975. However, there is a chance that restarting will cause Dolby to open and will stop running. You need to re-import it. Thank you so much for giving us this good Dolby
[Android Software Development] pbergonzi:
On my OP6T (running OOS 10.3.1 with Omega kernel) this installed compatibly all the way through, but unlike several earlier versions, never showed in app drawer.
[Android Software Development] guitardedhero:
Look for Moto Audio. There's always the Quick Settings tile that can be added as well. If neither is available then something is certainly amiss.
[Android Software Development] adame09:
Working great on a OnePlus 7 Pro with Paranoid Android rom
[Android Software Development] adame09:
Install
[Android Software Development] adame09:
Moto interface
[Android Software Development] louis-JYG4t:
Tested on Xiaomi Mi 8 + xiaomi.eu miui 11 android 10

The installation passes all the checks just fine. When opening the app the first time I get the information screen about what it does, and after the 2nd screen (about the smart adjustments) the app force closes and after that it's not possible to open anymore. The quick settings tile is always on and doesn't do anything by tapping it. It only displays a dialog "moto audio is always on when listening through speaker" when I listen to it through the speaker. I also tried to force stopping the app and deleting it's data and then relaunch but this doesn't help. I also didn't hear any changes in sound at any point.
[Android Software Development] guitardedhero:
This sounds very similar to what I encountered at some point when preparing the custom bundle content. It sounds like you received the full port, but I suspect you are dealing with an audio effects configuration issue resulting in this behavior.

In terminal:

su -c dumpsys media.audio_flinger > /sdcard/dumpsys.txt

Please attach /sdcard/dumpsys.txt any time after running that command so that I can examine the configuration that is loaded.
[Android Software Development] nycdiplomat:
Woooo! I like this. Once again, installs/works flawlessly on Bliss on the op7 pro. You da man, GH! Just when I thought Dolby couldn't get any better!
[Android Software Development] laugeek57:
Moto1 FC on OP7 unofficial Evolution X 4.1

Return to axon9 ;)
[Android Software Development] Arkmars20:
I've never seen anyone more dedicated to get Dolby working. You are a legend.
[Android Software Development] pbergonzi:
This happened to me until I installed the, in this case, mandatory ACDB file [MENTION=4445176]guitardedhero[/MENTION] uploaded with it.

Then it worked, even though I run no other audio mods, even without selinux set permissive.

Oneplus has an inbuilt audio tuner, but it was disabled.
[Android Software Development] RalphMalph:
DolbyAtmos 0.98 in combination with Acdb 0.4 working without a problem on Xiaomi Redmi Note 5 Pro with custom rom ASOiP android 9.0 (latest).

Great job!
[Android Software Development] louis-JYG4t:
Aha problem solved! I indeed had to install ACDB. Thanks!

Will try the sound experience tonight :)
[Android Software Development] guitardedhero:
32-bit Dolby Atmos™ Lenovo M7 port for Android devices 9.0+ with ACDB support. :good:
[Android Software Development] _BГ@ckθut:
Try install on 64 bit app force close is there a version for 64 bit thanks?
[Android Software Development] crackerjack1957:
Maybe you need to go back to post & read a little slower.........32 bit port from M7(32 bit) device.

There are other ports that are 64 bit.