yashsingh1/xdaforums huggingface dataset:
[Android Software Development] guitardedhero:
Is the ACDB module installed?

32-bit ports will work on 32-bit and 64-bit devices.
[Android Software Development] JakunTech1010:
Well it didn't have anything special beside it's a 32bit port.

Work well on 64bit :good:
[Android Software Development] JackHack96:
I tried to install it in my OnePlus One, but I can't even launch it.

Here is the log if I try to launch it from the ADB shell:

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.dolby.atmos/com.dolby.atmos.MainActivity}: java.lang.RuntimeException: Cannot initialize effect engine for type: ec7178ec-e5e1-4432-a3f4-4657e6795210 Error: -3
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3271)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3410)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2017)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7397)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:915)
Caused by: java.lang.RuntimeException: Cannot initialize effect engine for type: ec7178ec-e5e1-4432-a3f4-4657e6795210 Error: -3
at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:468)
at com.dolby.dax.DolbyAudioEffect.<init>(DolbyAudioEffect.java:107)
at com.dolby.atmos.MainActivity.onCreate(MainActivity.java:365)
at android.app.Activity.performCreate(Activity.java:7824)
at android.app.Activity.performCreate(Activity.java:7813)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1306)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3246)
... 11 more

I have JamesDSP and Ainur Narsil installed, could it be their fault?
[Android Software Development] crackerjack1957:
Hmmm........stand corrected on 32 bit port............what would be the purpose of putting 32 bit port on a 64 bit device if there are 64 bit ports for that device.
[Android Software Development] guitardedhero:
Is the ACDB module installed?

The 32-bit option allows those without a 64-bit device to have an opportunity to try Dolby Atmos.
[Android Software Development] JackHack96:
Is there a way I can verify that apart from it being listed in Magisk Manager?
[Android Software Development] guitardedhero:
That is sufficient as long as Magisk Manager shows the module as not being disabled.

Does /data/adb/modules/acdb/system/vendor/etc/audio_effects.xml exist?
[Android Software Development] JackHack96:
Yes it does. I'm attaching it below if it's useful.
[Android Software Development] guitardedhero:
In terminal:

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

Attach /sdcard/flingerdump.txt when done.
[Android Software Development] JackHack96:
Wow man! I hope this isn't taking away too much of your time...

Thank you very much for helping :D
[Android Software Development] Lilcode:
Finally dolby atoms for pie 32bit.

Install well but problem is there's no sound effect even i turn on and off the dolby atoms.
[Android Software Development] guitardedhero:
You bet. :good:

Your dumpsys output shows an attempt to cripple the library effects as if that could somehow force hardware processing (<-- absolutely incorrect assumption) while software processing such as jdsp could still process (<-- would never have a chance at working if Android audio is truly bypassed). Absurd, right?

Essentially, your software side is a mess and I don't even see dolbyatmos in your dumpsys output.

AML could also be involved since those installing ainur and jdsp are instructed to install AML.

What ACDB version is currently installed?
[Android Software Development] guitardedhero:
This particular port did not appear to have any license checks for the effect. You might check logcat for "license" events to see if the effect library is performing a license check.

*Edit

Also, try switching profiles during media playback to be sure the effect is not persistent as to still be active while the app is off.
[Android Software Development] JackHack96:
Mmmh that's not stonks...

I've installed v0.45, the one that came together with the 32-bit port.

BTW yes I have AML installed.
[Android Software Development] guitardedhero:
If AML is installed, disable it in Magisk Manager and reboot. Repeat the process to create /sdcard/flingerdump.txt and attach it so I can see what happens.
[Android Software Development] JackHack96:
I've first nuked all audio mods, then started gradually installing them. In every dump below, AML is disabled.

I made three dumps made in three different moments:

Dolby Atmos only

Dolby Atmos + JamesDSP

Dolby Atmos + JamesDSP + Ainur Narsil

When AML is disabled I can open without problems Dolby Atmos and it works, but obviously James doesn't and crash at startup.
[Android Software Development] guitardedhero:
ACDB support is as easy as placing a single file with the appropriate effect configuration parameters inside the audio mod's module directory next to its module.prop file:

/data/adb/modules/jdsp/acdb.conf

Reboot so that the ACDB module can then configure the newly available acdb.conf into the audio effects configuration.

:good:
[Android Software Development] JackHack96:
OMG it works! Amazing!

Thank you very much :D :good:
[Android Software Development] Jocantonio:
Does it work on arm phones?
[Android Software Development] Wolfcity:
No, the actual mods are all for arm64. There was one mod taken from Moto G6 for 32bit

https://xdaforums.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508/post81656355

that didn't work for me:

After getting a stable build for arm64 a version for 32bit devices is on [MENTION=4445176]guitardedhero[/MENTION] 's list.
[Android Software Development] guitardedhero:
Perhaps, you didn't see it yesterday. ?
[Android Software Development] guitardedhero:
One post up. ?
[Android Software Development] Wolfcity:
Overlooked it indead, apologies.

Will test and report asap!:good:
[Android Software Development] Wolfcity:
On my testing device Moto G 2014 (titan), magisk 20.3 I did the following:

Uninstalled all audio mods

- James DSP

- Ainur Sauron

- AML

Installed

- ACDB-0.45.zip

- Dolby Atmos-lenovo-m7-32bit-0.45-ACDB

(without a reboot in between)

Result:

Dolby

completely

working!:good:

Tried to install this ACDB compatible James DSP mod:

That one doesn't show up in apps, launcher or quick settings.

Installed "normal" James DSP which fc without AML.

With AML it was ok but Dolby wasn't working anymore.

Next step will be trying to install a viper mod, any version that may be recommended?

But first of all: Dolby is fully working.

I attach magisk log and flingerdump nevertheless, will report if I get a viper mod working alongside with Dolby Atmos- lenovo-mt7-32bit.

Great work [MENTION=4445176]guitardedhero[/MENTION] !

Edit

:

ACDB-0.45.zip

Dolby Atmos-lenovo-m7-32bit-0.45-ACDB

working perfectly togehter with ViperFX_2.5.0.5-0.8-ACDB.zip from here:

Thx!
[Android Software Development] guitardedhero:
That's great to hear, man!

That particular jdsp zip does not include the jdsp apk and the acdb.conf for jdsp was prepared by someone else and, unfortunately, included line ending issues.

Below, is the acdb.conf zipped up that should be placed in:

/data/adb/modules/jdsp/

The same can be done for v4a, but since the unofficial guys like to rename the v4a effect library, acdb.conf in the v4a module directory will need to have the same name inside for "libraryname=" as it appears in:

/data/adb/modules/v4a/system/vendor/lib/soundfx/
[Android Software Development] Wolfcity:
Thx man, I edited my post above, found a working combination with an acdb viper build.

But I will keep this in my mind and will do further testing with jdsp :highfive:
[Android Software Development] Wolfcity:
And another result:

Instead of ViperFX_2.5.0.5-0.8-ACDB I installed JamesDSP from magisk repo, copied the acdb.config from your previous post to /data/adb/modules/ainur_jamesdsp and voila Dolby and JDSP play nicely together and produce a really great sound. I'm starting to understand the goal of acdb...;)
[Android Software Development] Zero_One:
Yeah, actually I forgot to put the apk inside the zip! XD

But yeah, I'll fix It tonight and share with you all again!
[Android Software Development] Neejay:
Is there anyone on a pixel + Android 10 custom ROM that has gotten it to work? And if so, what steps did you take?
[Android Software Development] guitardedhero:
Are you able to write directly to the /system or /vendor partitions?

*Edit

Congratulations on your upcoming 1,000th post! :highfive:
[Android Software Development] Neejay:
Nope..the beauty of having a pixel :eek: lol the install seems to fail when trying to back up the "manifest.xml", which results in a "unable to register DolbyManagerService" error. Everything else appears to be successful.

Thanks! I didn't even realize I had that many posts now lol
[Android Software Development] guitardedhero:
That is because there is a single component necessary to directly write to the partition (manifest.xml) because Magisk has no plans for pre-init support which would allow manifest.xml to bind-mount in time to register a new hardware service when in a module setting.

No writing to the partitions is possible, in your case, because the partitions are sized to have zero free space.

Unfortunately, because of these two realities, absolutely nothing can be done to get Dolby Atmos to function as the implementation exists today. :(
[Android Software Development] Neejay:
You just shot me in the heart! :(

I can use Dolby digital, but it doesn't compare to when I was able to use Dolby Atmos...oh, well, thanks for the explanation, and good work!
[Android Software Development] guitardedhero:
I went directly to topjohnwoo regarding this and he has no plans on changing this.

I know that feel, bro...
[Android Software Development] Abhinandan Trilokia:
It's working on pixel with android 10 custom rom but not on stock android 10 because of write restrictions on system & vender partition

I tested dolby with following configuration

TWRP 3.2.3.1

Magisk version 20.3

SELinux status: Permissive

Pixel dust + inbuilt kernal

Evolution X 3.5 + inbuilt kernal

Evolution X 3.5 + King kernal 6.6

Evolution X 3.5 + ElementalX x 5.06p

Most of the times Dolby is working even with viper4android but both rom has weird freezes & random reboot issues.

Razer & xperia dolby mods are also working but it breaks Gcam. Moto mod is not working. Dolby atmos mod on android 8.0 has better audio output as compared to other audio mods

Thanks to [MENTION=4445176]guitardedhero[/MENTION] it is now working on android 10 and sounds much better than Dolby digital plus

I am currently using Dolby 0.98 acdb on evolution 3.5 with elemental x 5.06p. I also tested King kernal 6.6 but elemental x is more stable & solved random reboot issue but sometime Dolby service automatically get disabled. To solve it just toggle Dolby on off and one more thing DO NOT install any other magisk modules along with Dolby except systemless host modules. Whenever I install other modules like magiskhide or cloudflaredns along with it. Dolby stops working. I don't know why it is happening may be because of dirty flashing

You can try it with clean installation and report here back.
[Android Software Development] SicarioTrey:
This file should be unzipped right?
[Android Software Development] guitardedhero:
Correct. :good:
[Android Software Development] Lilcode:
Il try switching profile to during music played. But theres stil no difference when switching.

How do i get the logcat for this? Sorry im just a newbie.
[Android Software Development] pbergonzi:
This might be a way:

https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
[Android Software Development] guitardedhero:
Release Candidate 1

:

• 32-bit and 64-bit installations from a single zip.

• Axon 9 Pro apk and effect library used in both 32-bit and 64-bit installations to provide the most consistent experience for all users.

• This allows 32-bit users to avoid the 3dB GEQ boost limit as well as any license check by Lenovo.

• Removed much of the verbose messaging during the installation.

• Refinements and minor corrections to every single script.

Procedure

:

• Install ACDB 0.45 if not already installed.

• Uninstall any existing Dolby Atmos™ installation and reboot.

• Install RC1 in Magisk Manager or in custom recovery.

• Save installation log before rebooting.

• Apply your best effort to find a failure or force a failure of functionality by any reasonable means - deleting/overwriting something will not count, obviously.
[Android Software Development] pbergonzi:
Simply stunning.

OP6T--OOS 10.3.1--Omega Kernel
[Android Software Development] Goutham Ganesh:
thanks a ton for your work ?

this update works like a charm!
[Android Software Development] RalphMalph:
RC1 working great on Redmi Note 5 Pro with AOSiP 9.0 custom rom.

Great job!
[Android Software Development] dead90:
Someone tried this on OnePlus 7 pro and can tell me the difference between this and dolby digital plus? Thanks a lot
[Android Software Development] Toni Moon:
I tried, Dolby Digital Plus sounds better to me, but the instalation of Dolby Atmos it's more easy in custom roms.
[Android Software Development] Lilcode:
RC1 installed well. But there's no effect also. Im just using stock rom j7 pro.
[Android Software Development] guitardedhero:
Have you tried toggling the QS tile off and on?
[Android Software Development] Lilcode:
Yes but there's no happen on sound.
[Android Software Development] Wolfcity:
Working perfectly on my

32bit testing device Moto G 2014 running RR Pie with latest magisk canary build and alongside with JamesDSP 2.7 and fitting acdb.conf.

Great work!
[Android Software Development] guitardedhero:
Samsung device?
[Android Software Development] repey6:
I installed DolbyAtmos-RC1-ACDB.zip after installed next magisk modules:

ViperFX 2.7.1.0

DDP v.7.2

AML v.2.5

and all works perfectly together on my Redmi 4x Havoc OS official 10-Q.:D
[Android Software Development] Lilcode:
Yes im using samsung j7 pro 32bit.
[Android Software Development] guitardedhero:
Add "true" to "musicstream=" in /data/adb/modules/dolbyatmos/acdb.conf to appear as:

musicstream=true

Save changes and reboot. :good:
[Android Software Development] Lilcode:
wow! Its working now. Thanks alot.
[Android Software Development] RalphMalph:
And why do you want this?

Is Dolby Atmos not enough?

I just dont understand
[Android Software Development] yyz71:
That seems overkill ?
[Android Software Development] guitardedhero:
He's the OP of the other Dolby thread in this forum section. He's just testing stuff.
[Android Software Development] Bordo_Bereli51:
Tried everything to get the logcat but could not get it -.- I do not know why it stuck at bootlogo. I have to reinstall magisk in order to get it boot again.
[Android Software Development] guitardedhero:
Bear with me guys, I am in the process of finishing the update for 20180202 before the Unity integration. :good:
[Android Software Development] yung40oz84:
I was just gonna say no boot in OnePlus 5T, but I'll be patient ?
[Android Software Development] pirrat25:
audioserver

audioserver at my Nokia 6. I have Oreo 8 installed. Dolby Atmos is officially running.
[Android Software Development] yyz71:
20180205 zip installs after that I'm at a loss ?
[Android Software Development] lcsd:
[MENTION=4445176]guitardedhero[/MENTION], after menu reboot, stuck on boot;

Power reboot ok, apk still FC but could start matlog.

Catalog (filter dax) attached.
[Android Software Development] Golv:
HTC U11, Magisk 15.3, 20180206-2.zip, bootloop on logo HTC.
[Android Software Development] guitardedhero:
Standard Edition

:

Latest: 20180206[*]MD5: 99f88d983a8b62e9bf553cfc75267921

Today's update to the standard recovery installation archive without any external integration for testing. :good:
[Android Software Development] RalphMalph:
For me still stuck in boot unfortunately

(no time to do now logcat, sorry)
[Android Software Development] g3v0:
Why does the post-fs-data look for audio_policy_configuration in /vendor/etc/audio/ when the file is supposed to be in /system/etc/ or /vendor/etc?
[Android Software Development] lcsd:
Boot loop. Recovery log attached.
[Android Software Development] guitardedhero:
Does /vendor/etc/audio/audio_policy_configuration.xml exist?

It does on many Oreo firmware, including the native firmware from which this Dolby Atmos™ system is ported.

The reason the script seeks this particular file is because the native Dolby Atmos™ firmware creates the /odm/etc directory each boot and then copies or symlinks that audio_policy_configuration.xml file to /odm/etc before boot completes.

If /odm/etc/audio_configuration.xml does not exist, this can be confirmed with an existing Dolby Atmos™ installation by the following in Android Terminal:

su
/system/bin/audioserver

/system/etc/audio_policy_configuration.xml and/or /vendor/etc/audio_policy_configuration.xml exists as well, but at half or less in total KB than /vendor/etc/audio/audio_policy_configuration.xml (if present, of course).

That is the specific purpose, but if /vendor/etc/audio/audio_policy_configuration.xml does, in fact, not exist, then the appropriate action to take is to seek the file in /vendor/etc and then /system/etc until found.

I forgot this may be the case for some Oreo firmware out there, so I should add that to the script.

Thanks for the head's up! :good:
[Android Software Development] Ghost52367:
The previous two builds worked but the latest one's interface doesn't work at all! No other processing other than the originally set one. Fiddling with the smart eq or graphic eq doesn't change anything at all!

---------- Post added at 03:26 AM ---------- Previous post was at 03:13 AM ----------

The toggle switch not working at all, cannot change any setting in the app. V 20180205
[Android Software Development] guitardedhero:
Standard Edition

:

Latest: 20180206-1[*]MD5: 76dd4784437c6018b89a3429549cc368

Today's second update to the standard recovery installation archive without any external integration for testing. :good:
[Android Software Development] g3v0:
FINALLY GOT IT RUNNING WITHOUT FC!

So I kept moving files back and forth and analyzing the logcats, dumpsys, etc, and realized that libatmos looks for a lot of dependencies in /vendor/lib whereas my phone has those in /system/lib. After copying the required lib, rebooting, etc, I noticed it started asking for weird libs like ones related to the camera, so I just mass copy pasted them. I set my magisk partition size to like a gig and copied /system/lib and lib64 into the magisk/dolbyatmos/system/vendor folder.

App works without FC! Viper doesn't process though, I'll figure that out later. Downside is that copying the libs broke my camera. Now I just gotta figure out which libs were essential, etc

Pixel 2 XL 8.1
[Android Software Development] lcsd:
Boot loop here (Op3T).
[Android Software Development] guitardedhero:
Your log suggests you "ran out of space".
[Android Software Development] yyz71:
PM sent
[Android Software Development] dt0807:
Is there any benefit/advantage to flashing the latest builds if 20180202 has been working just fine for me?
[Android Software Development] Trupen:
Bootloop in this build

---------- Post added at 07:54 AM ---------- Previous post was at 07:51 AM ----------

Stuck in recovery with this build
[Android Software Development] yyz71:
Oh ok I got ya ?
[Android Software Development] repey6:
I wanted to say that can exist different collaboration configurations, even seemingly incompatible mods.

---------- Post added at 08:33 AM ---------- Previous post was at 08:28 AM ----------

Absolutely right!:D
[Android Software Development] RalphMalph:
Ahhhh

That's where i recognize the name :silly:
[Android Software Development] Lilcode:
How do you install Dolby atoms and DDP together? Because when im doing this DDP is not working. Can i get link of your viper fx and ddp?
[Android Software Development] repey6:
DA need install latest mod. After(over) other installed sound mods and AML. DDP module you find in XDA thread but ViperFX in this case i used mod made for self(with pre-installed drivers) , not for all.
[Android Software Development] JakunTech1010:
I've installed DolbyAtmod RC1 on a very old tablet: Samsung Galaxy Tab 4 :eek: running 32bit Snapdragon 400. Dolby app won't open

Su -c returned nothing ( I won't type out the full command )

Here's dumpsys output and logcat.

Oh just in case here's the ROM I'm currently using: LightningFastRom 16.0 ( 9.0 Pie ) by DJABHipHop

Link: https://xdaforums.com/tab-4/development/lightningfastrom-16-0pie-t3998901
[Android Software Development] laugeek57:
DolbyAtmos RC1 on OP7 unofficial EVX4.1 works fine !!!

Thanks GH:)
[Android Software Development] guitardedhero:
The effect is not configured. Is the ACDB module installed?
[Android Software Development] JakunTech1010:
Oh, oh crap. I didn't install ACDB yet. Sorry cuz on my Samsung A70, Dolby work fine with ViperFX and AML without ACDB at all. Installed ACDB and it worked. Thanks.
[Android Software Development] Bobbaloo:
Working on my op7 w/crDroid, stock kernel. It might come in handy as a quick fix when using speaker. Got to try when people aren't sleeping lol. Hey, guitarded - got Viper working on the same system...! Not simultaneously tho. I know your work goes way back and I totally appreciate it!!!! Thanks
[Android Software Development] guitardedhero:
My 2 year old son, Beau, drowned in a pond last night. I just can't do this anymore. I'm sorry.
[Android Software Development] acuicultor:
Sad to hear that mate, rip.
[Android Software Development] shantam3108:
No need to be sorry man. You did so much for us.

Stay strong
[Android Software Development] escorpion_sw:
sad to hear that man, stay strong
[Android Software Development] repey6:
This is terrible. Sorry.:(
[Android Software Development] laugeek57:
There are no words even in French to describe how you should feel ...:crying:

Une pensée pour toi l'ami...
[Android Software Development] Adamk102:
I feel sorry for you my friend. Thank you for your hard work for us.

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] beeshyams:
Very sad. Rip. May God give you strength to bear
[Android Software Development] Wolfcity:
I have no words.My condolences.
[Android Software Development] a_prabhu7:
Sorry mate. Rip
[Android Software Development] zgfg:
Really sorry

RIP - an angel

Take care and cndolences
[Android Software Development] danial.aw:
Sorry for your loss... May he rest in peace
[Android Software Development] RalphMalph:
Wow... Thats so bad and sad.

Pffff thoughts of us are with you.

RIP Beau
[Android Software Development] Chip Liang:
My condolences from Malaysia. ?

Your son must be living happily as an angel in the heaven right now and proud of his dad who has contributed so much for the world in his own way all this while.

I know it's hard for most of us to feel your pain but please be strong and walk the rest of the road knowing that the cute boy of yours will be watching and supporting you from the heaven. :crying:
[Android Software Development] HackerGames197:
hey man i have a OP6T could you tell me how did you manage to get dolby+viper on your phone?
[Android Software Development] niyonsv:
No words can describe how sorry I am for your loss..
[Android Software Development] Bobbaloo:
I can't believe I didn't see that message before. I am so sad to hear about your loss. So sorry

---------- Post added 6th March 2020 at 12:25 AM ---------- Previous post was 5th March 2020 at 11:25 PM ----------

Send me a pm, I can't initiate, I'll explain what I did.
[Android Software Development] aryaherro:
Sorry to hear that,, keep strong..

RIP..