yashsingh1/xdaforums huggingface dataset:
[Android Software Development] guitardedhero:
Your issue is the result of the installation failing to add the Dolby hwservice registration to /system/etc/vintf/manifest.xml.

The registration entry is included in the troubleshooting post if you want to try adding it yourself manually, or I would be more than happy to do that for you if you prefer.

I will need a copy of /system/etc/vintf/manifest.xml in order to do this for you. :good:
[Android Software Development] yyz71:
Hey bro I managed to install The Xperia Dolby one only thing it won't turn on. Is it still magisk issue?
[Android Software Development] JakunTech1010:
Thanks but uhhh that's kinda unnecessary anymore

Why? Well after unsuccessful attempt to install it I uhhhhh tried Motorola One A10 port but then I decided to reinstall it so I remove Motorola port and then reinstall Axon9 0.918 and then surprisingly it work.

I guess that Motorola One A10 port already help me with registering it. Huh. OK cool. :eek: :confused:
[Android Software Development] unomas:
App loads, but the on button doesn't work?
[Android Software Development] laugeek57:
Tried Motorola One A10 port before remove it and install last Dolby axon9 worked for me :good::D
[Android Software Development] Fatal_Equinox:
I have the same issue as you but on the OnePlus 6. As previously mentioned here, this only seems to happen on custom ROMs. I have tested pretty much tried all the zips since I heard of the development and they all seem to have the issue ? Dolby Atmos itself works well though! This is such an odd issue lol
[Android Software Development] nikothebarber:
This is what I found for you in etc
[Android Software Development] nikothebarber:
[MENTION=875143]guita[/MENTION]dedhereo disregard changed back to a stock rom.

---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------

[/COLOR [MENTION=875143]guita[/MENTION]dedhereo disregard changed back to a stock rom.
[Android Software Development] guitardedhero:
Getting closer...
[Android Software Development] guitardedhero:
A few more inches...

forwards, hopefully.
[Android Software Development] JakunTech1010:
DolbyAtmos Axon9 0.93 builds Force Closed ( it doesn't even show the app is Force close until I open the app too many times)
[Android Software Development] guitardedhero:
Script corrections.
[Android Software Development] Aledovale:
Any chances to make it work on a S7 with Oreo, Exynos?
[Android Software Development] guitardedhero:
One more...
[Android Software Development] guitardedhero:
You can try. Incompatibility can be detected and will not install if the firmware cannot support it, so it's a very quick and easy task, especially with Magisk Manager. If compatibility is found, there's a very good chance it will work, though.
[Android Software Development] JakunTech1010:
It work great: No bootloop, no Force close like the previous version. Although it doesn't have bass enhance or surround virtualizer but nah who care.:good:
[Android Software Development] lkp171:
I tried the 0.922 and the latest and both worked. No fc, no bootloop, no Bluetooth issue, good work man:svetius:
[Android Software Development] Zalim Shayar:
Dolby Atmos installed by Magisk...Dolby app opens but dobly does not works...cannot turn on effects inside app....

Using Xperia5 10.0.006-ACDB.zip

Device...Xiaomi Redmi note 5 pro

Android 10

Havoc Os 3.2

Magisk 20.3 stable

Se Linux permissive

Audio modification library installed

Any help would be appreciated...
[Android Software Development] lkp171:
Hi, i have a question about the native dolby atmos in oneplus 7pro and this module. How do they compare?

Maybe someone here has experienced both?
[Android Software Development] crackerjack1957:
I would love to experience 1 or the other on this old Pixel XL............LoL
[Android Software Development] JakunTech1010:
Help me: Installing Atmos Axon9 0.935 on Samsung Stock Rom (Yep no more LOS) but it FAILED TO REGISTER DolbyManagerService.

OK fine no needed manually added. Sorry for bothering and WHY SAMSUNG.
[Android Software Development] laugeek57:
Try flash one power motorola before remove it and install Xperia5 for me works i can turn on Dolby..:good:
[Android Software Development] guitardedhero:
Lots of script adjustments
[Android Software Development] alok932:
None of the versions are working after updating my poco f1 from android 9 to android 10. Every axon9 file used to work before.

Dolby is missing from dumpsys log.
[Android Software Development] lkp171:
Works
[Android Software Development] JakunTech1010:
Worked with Samsung Stock Rom now, so thumbs up for that :good: :good:.

This is the only soundmod that worked with Samsung SoundAlive thanks to ACDB which can saves up some time going to the root directory and remove SoundAlive so another thumbs up for that :good:.

Edit: So I installed Viper4Android with DolbyAtmos and Samsung SoundAlive and here is the resault: Viper and SoundAlive work well but Dolby didn't have any effects.

Now thumbs up if you wanted Guitardedheros to work on a seperated ACDB installer. I'll give hime a first thumb up :good:.
[Android Software Development] Oblias:
I posted this in another thread, but also wanted to post here, for posterity sake....

Wanted to share my experience with the files you have been so generous with. I'm on a OP6T that has been T-Moble International converted, and I'm running OOS 10.3.1 with twrp-3.3.1-31-fajita-installer-mauronofrio.zip recovery and Magisk 20.3 . The only Magisk module I had installed was Busybox.

I ran across this thread early this morning, and read all posts, and tried many things to get Dolby up and running. It always failed, each time I tried something that had been suggested throughout this thread. Then persistence finally paid off. I now have DolbyAtmos-xperia5-A10-0.06-ACDB fully up and running, and functioning very well and persisting thru reboots. The solution, for me, was actually quite simple after hours of trial and error.

The final solution was to boot to TWRP, flash the Omega-10.0_0206.zip custom kernel, and once back into my system, I used Magisk to flash DolbyAtmos-xperia5-A10-0.06-ACDB . After reboot, it all worked like a charm! And sounds very good, much better than stock.

So, for anyone still struggling to get Dolby up and running on OOS 10.3.1, I provide this information for future reference.

Thanks guitardedhero for all your hard work and for sharing with the comminity!!!!!!
[Android Software Development] Riddle5:
Sorry but any have a profile for op6t?
[Android Software Development] Oblias:
There is something that I'm a little unclear about. What is the difference between DolbyAtmos-axon9-0.94-ACDB , DolbyAtmos-xperia5-A10-0.06-ACDB ,

ViPERAtmos_Redux-0.2 , and DolbyAudio-moto-onepower-0.01-ACDB ?? That is still very confusing for me. I'd like to understand the differences in those files, so that I can determine if I have the best version/combination installed for my OnePlus 6T. Anyone who can clear this up for me would be greatly appreciated!

---------- Post added at 01:34 PM ---------- Previous post was at 01:30 PM ----------

I have a OP6T, and I'm not using any profiles. I was not aware that I should be. Is it necessary??
[Android Software Development] EstherTakumi:
All those version are Atmos port from various smartphone.

For universal, you should just using Axon.

ViperAtmos is a package for Dolby and Viper.
[Android Software Development] Oblias:
And how difficult is it to set up the ViperAtmos package? I had both running in Android Pie, but I had to jump through hoops to get it done. For example, to get V4A installed required to flash the Magisk module for V4A, the flash the Audio Modification module, reboot, let the V4A app install the drivers after granting root privledges, reboot again, and then flash Dolby.

I never could get V4A installed in Android Q. So, my question is, how much trouble will I have if I flash the ViperAtmos package, and is there anything special I need to do to get it all up and running in Android 10.3.1?
[Android Software Development] EstherTakumi:
Im using OP6 currently, no need to do anything fancy, you just need custom kernel first.

For my part, Im flashing ACDB module first, reboot, then Axon ACDB and Viper ACDB, and you are done.

Just to make your life easy, please remove everything first from magisk, and start from zero, then follow my guide here.

Guitarhero already share new module above my post, use that.
[Android Software Development] SerVoice:
Hi guys. Thanks all of you for big hard work. Our hero is Man!!! Respekt!

I've waiting DA port for Pie very long time and now i see that i can use it, but here is so many zip's and i dont know which one i may use (with v4a). I use LeEco (LEX720) with RR OS 7.0.2 installed (Android 9, Kernel 3.18.140-BlackScreen 6.6.1). Please, tell me which zip's i can install?
[Android Software Development] guitardedhero:
Audio Calibration Database™

​
[Android Software Development] JakunTech1010:
But uhhhhh what is DolbyAtmos blend? Is it a port of Dolby from another device? Or is it something special?
[Android Software Development] JakunTech1010:
Axon9 0.95 port Installation failed.

DolbyAtmos Blend app force close
[Android Software Development] EstherTakumi:
Yes it was from other devices, probably OP7 Pro, base on codename
[Android Software Development] guitardedhero:
Lol, that's pretty embarrassing.
[Android Software Development] Lilcode:
Any Dolby atoms or viper4android for pie 32bit?
[Android Software Development] JakunTech1010:
Well it installed but sadly the app keep force close

The first one sec.txt is being filtered out with the word "dolby"

The second one sec2.txt is being filtered out with the word "dax"

Forgot to mention those are Logcat
[Android Software Development] alok932:
Actually ACDB 0.25 also fails to install!
[Android Software Development] Oblias:
Outstanding, thank you!! I have the custom kernel installed, I have the very newest Axon ACDB that has been posted, but I cannot find the Viper ACDB file. Would you point me in the right direction? The only one I have is from the OP named ViPERAtmos_Redux-0.2.zip , but I don't think that is the file you are talking about, is it? I now understand the steps to take to flash them, thanks to you, so all I have left to do is to get that Viper ACDB file you are talking about. I even did a thread search, but did not find it....... :(
[Android Software Development] gyuuuu:
0.96 not install

i use pixel 3 stock rom
[Android Software Development] yyz71:
Did you get any of the Dolby to work?
[Android Software Development] carl.13:
Hi,

Havoc os 3, umidigi f1 play;

. 93 first of all didn't register & forced close.

Removed via Magisk.

. 94 failed to install due to incompatible. Removed again.

Thought I would try. 93 again, Voilà all good.

Now working fine.

Able to tune out tinny upper end & add a lot more Bass.

Note, umidigi f1 play uses earpiece speaker as stock, but not true Stereo.

Thanks, Carl
[Android Software Development] EstherTakumi:
I take it from Telegram group that Guitarhero make, it more suitable to get update from there.

[Updates] Dolby Atmos and Viper4Android

Dolby Atmos and Viper4Android by [MENTION=4445176]guitardedhero[/MENTION]

https://t.me/viperatmos
[Android Software Development] Oblias:
Many thanks, once again!! Alright, I'm ready to flash on my OP6T, but as a final check, I want to make sure to do this the right way, with the right files. Will you confirm that this is correct ?

Remove all sound mods from Magisk, and reboot.

Flash ACDB-0.26 and reboot.

Flash DolbyAtmos-axon9-0.96-ACDB and reboot.

Flash ViperFX_2.5.0.5-0.63-ACDB and reboot.

Then I set up Dolby and V4A the way I want them to be.

Is this correct???
[Android Software Development] alok932:
[MENTION=4445176]guitardedhero[/MENTION]

So i installed clean rom and tried again with latest Axon atmos but with no luck.

Got some failure as attached in magisk log.
[Android Software Development] JakunTech1010:
Have anyone try this DolbyAtmos mod with Ainur JamesDSP?
[Android Software Development] EstherTakumi:
Yes, that was a correct order, hope it work for you
[Android Software Development] Oblias:
Everything went very, very well !! WOW, what a difference in the sound quality now! You know, V4A worked pretty good on my old OP3T, but I am sure it works much better on my OP6T . The only thing that is disappointing to me is that the new Viper won't import my old speaker and headphone settings. :( There's no way I can remember all the individual values I used in V4A when I first set it up 2 years ago..

So, now I get to try to figure out what the best settings are for my OP6T for headphones, bluetooth, and headphones. Fun, fun.....

Thank you for all your help, and for your patience. It probably seemed like you were spoon-feeding me, but because the OP6T can't restore a nandroid backup, I wanted to be very, very careful about what I did to the system, you know? Anyway, once again, I do appreciate all the help you gave me!!!!!!!! :good:
[Android Software Development] exodius48:
Last known stable version is axon9 v0.934
[Android Software Development] guitardedhero:
I apologise for being so busy this week.

While unable to repair the new acdb service last night, I came up with a simple form of AML support to include until ACDB functions as intended. Aml is not required, just supported.

The ACDB module will be disabled if installed and not already disabled until ACDB is satisfactory.

Also, incompatibility is now just a warning and no longer a condition aborting installation, for now.
[Android Software Development] guitardedhero:
Effort to increase file patching success.
[Android Software Development] adame09:
Latest 965 not working on OnePlus 7 pro with AML

964 working fine with AML
[Android Software Development] Lord Sithek:
I haven't followed your posts, but if you are talking about V4A 2.7, there is a Magisk script to convert old profiles into a presets working with the new app. You can find it on https://zackptg5.com/android.php. Sorry if I misunderstood you.
[Android Software Development] Oblias:
Hey, thanks a lot! Just what I was looking for. That was great of you to point me in the right direction!! I'm off to learn all about how to use it.
[Android Software Development] Lord Sithek:
You're welcome :) You just need to have old profiles in the Viper's directory on the internal storage and then flash converter in Magisk
[Android Software Development] JakunTech1010:
Uhhhh the installer said Incompatiblity detected. Is that a very bad sign :confused: :silly: :eek:.

Update: OK yep the app refused to open and now so far DolbyAtmos 0.94 is working for me.

Update: OK reinstalled DolbyAtmos 0.965 and got the log file for it. It seem like there's a problem with mounting partition

NewUPDATE: OK so one last attempt I install Viper with JamesDSP with Ainur Sauron with compariblity patch and Atmos and AML. Dolby refused to open. However, I then flash 0.965 and suprisingly it worked :eek: :confused:. I AM SO CONFUSED. But after rethink I think I know what happened! But anyway it work now so OK thx.
[Android Software Development] TalhaGirgen9:
Didn't try the .965 but reporting 0.964 on my Xperia XZ running aosp pie with magisk 20.3

Installed thu magisk, checking compatibility took like 10 mins and it said its not compatible aswell, but it worked just fine after installing, didn't break any other installed sound mods that i've wrote down below. All working just fine.

I already have like 4 other audio mods (Sauron, V4A, Dolby digital plus, DTS) that makes atmos 5.
[Android Software Development] laugeek57:
Awesome Dolby 0.965 works on old Lenovo Vibe K5 :highfive:
[Android Software Development] DerEineDa:
Works fine on my Lenovo Yoga Tab 3 Plus (YTX703L) on official LineageOS 16, although installation freezed for a while on "Checking rom compatibility" and it said "X Incompatibility detected".
[Android Software Development] Bogdans29:
That is normal...
[Android Software Development] FluffyDiscord:
Is 24bit mode working?
[Android Software Development] JakunTech1010:
Wait a minute did you use emulator or is that just a screen mirroring app? I'm pretty dumb.
[Android Software Development] laugeek57:
I use an application on windows which allows to display the screen because the K5 vibe that I tested in the middle of the touch screen which no longer responds ... :(

SCRCPY exe :good:
[Android Software Development] guitardedhero:
Lots of script changes. Be patient with the compatibility check (give up after five minutes, though).
[Android Software Development] guitardedhero:
More refinements...
[Android Software Development] pbergonzi:
Do I need acdb--.zip file if I don't use any other mods--just Atmos?

Incidentally, DolbyAtmos-axon9-0.974-ACDB.zip seems to be working very well, and installed with compatibility on my OP6T.
[Android Software Development] guitardedhero:
You don't need it, but I recommend it.
[Android Software Development] pbergonzi:
Is there an install order, and what does ACDB do--in a nutshell?
[Android Software Development] Skittles9823:
If I remember correctly, it's ACDB last.

In a nutshell it's a similar idea to AML. Just a different implementation.
[Android Software Development] Chip Liang:
Lengthy and Complete Explanation which is easy to understand. Thanks dev!
[Android Software Development] repey6:
Hi. Thanks a lot for your hard work. Please answer me you can't do compatibility DA with AML or not want do this? Regards.
[Android Software Development] guitardedhero:
I've never actually used AML and ACDB came about during this testing phase as a way to evade external conflicts which disrupt everything we have going.

I have nothing against AML and Zack and I are friends.

I simply choose to never put something in my stuff that I cannot read backwards. I have trouble following Zack's shell maneuvering left to right lol.

I can guarantee you that Zack would never implement something he cannot follow, either.

When brainstorming solutions to those disruptions - AML being one of the primary ones, I really had no interest in maintaining something additional to the task at hand in this thread.

When the ACDB solution was prepared in my mind, I immediately went to Zack and laid everything out for him with my blessing that he could do whatever he wanted with it since it fit his niche, obviously. I gave him a week to make a decision before I would actually prepare it and utilize it in this testing phase as ruling out any disruptive variable in periods of testing such as this is critical.

It took a couple dozen revisions to get to where it is now, but I simply could not be happier than I am now with the results. Maintenance is nearly non-existent and development will likely be limited only to enhanced support such as multiple effects in a single acdb.conf as well as support for proxy effects. Other than that, it's a wrap.

The fact that something like AML and ACDB can ever be necessary is something that has always irked me and I was convinced that things like these would never catch on - due to laziness, unawareness, who-gives-a-****ness...

But, I feel ACDB right now has the best chance of catching on than anything else similar. And that is because using this small little file guarantees sufficient and consistent audio effect configuration for the dev requiring, quite possibly, the smallest effort of all tasks completed to provide a product.

And it's so simple and straightforward that users can easily place a completed acdb.conf into a module if the dev doesn't do so.

It cannot be any easier than this. I've tried really hard to find anything easier than this and this is it.

Lastly, having two separate components such as the ACDB module and the acdb.conf files fosters effortless testing of different configs on the fly with no reason to ever do anything outside of the acdb.conf file.

Try it out and test it like I just described. I think you will be very amused with how much effort normally spent targeting, copying, and patching configurations simply disappears lol.
[Android Software Development] repey6:
Thanks for your full answer and clarification of the situation.:good:
[Android Software Development] Skittles9823:
Wow, ACDB really evolved since last I had a look then. Thats really quite simple to use now :cowboy:
[Android Software Development] pbergonzi:
You did very well.
[Android Software Development] alok932:
So its compatible, everything registers as per magisk logs but system is again and again not able to find dolby module. Android 9 used to detect and work instantly but Android 10 is just not ready to accept dolby. Seems it won't work until future updates from device manufacturer changes/fixes something that is broken.
[Android Software Development] Zero_One:
In quote to what you just wrote (Which is amazing) I adapted JamesDSP for make it compatible with acdb module.

Here, I'll share it for anyone who is more comfortable to use it instead of Viper :D
[Android Software Development] alok932:
Not really!

Finally got it working on poco f1 miui 11 android 10 :o

What encoraged to keep trying was your lots of big description all over the xda.

I dont have even the basic knowledge about audio processing and its working on android system and so what i did might not be right and might conflict with other audio libraries but 1. I am not planning to use other library (not at all until atmos works) and 2. It feels good when you fix something and make it work, even if i need to reinstall complete rom to make things right in future.

So what i did in short is copy files that where missing in /sbin/.magisk/mirror/vendor from /data/adb/modules/dolbyatmos/vendor

Though i went through much more. I checked everywhere for audio_effects.xml file and finally found that in /sbin/.magisk/mirror/vendor/etc this file did not register dolby and so i updated it referring the module file. After this my dumpsys log of audio flinger showed no libraries loaded(or something sound like so) which was previously 4 libraries partially loaded. This showed something got breaked but importanly something changed. Then i noticed that audio_effects.xml in /vendor/etc/ has minor syntax error. There was space missing, it was <audioeffect rather than <audio effect so i changed it and now dolby was showing in libraries not loaded as null. And finally i added all missing files to /sbin/.magisk/mirror/vendor and magic happend.

I am sure you will know better what went wrong and if possible you can fix things. I might not need to do it all over again in future but it was fun debugging.

I can understand efforts and time you put into this and the joy of succeeding will be much more. Thanks for all your hardwork.