yashsingh1/xdaforums huggingface dataset:
[Android Software Development] guitardedhero:
The dumpsys utility in troubleshooting is to determine if the Dolby Atmos effect is configured in the audio effects configuration that is sourced for building effects and cannot be used to determine registration for the DolbyManagerService hwservice registration.

The zip failed to patch manifest.xml due to a mounting failure, in some cases read only is only possible while booted.

You can add the registration directly if you want to try it yourself without waiting for a future zip to do it successfully.

I'd rather not patch it for you and share it here as users may mistakenly attempt to use the whole manifest.xml and end up breaking services not included in yours.

The formatting should be pretty clear - you simply want the inserted element section to match the others. Pay special attention to what the beginning and end of these elements to determine if inserted correctly.

Reminder:

• Modifying partitions directly while booted should be done in /sbin/.magisk/mirror/*

/sbin/.magisk/mirror/vendor/etc/vintf/manifest.xml DolbyManagerService hwservice registration code below:

<hal format="hidl">
<name>vendor.dolby.hardware.dms</name>
<transport>hwbinder</transport>
<version>1.0</version>
<interface>
<name>IDms</name>
<instance>default</instance>
</interface>
<fqname>@1.0::IDms/default</fqname>
</hal>

Ensure 0644 permissions for the updated manifest before rebooting.

:good:
[Android Software Development] MitchiePitchie:
How to ensure permissions? As i dont know how to do this. Sorry im still learning.
[Android Software Development] guitardedhero:
View properties of the file when in its intended location.
[Android Software Development] guitardedhero:
For convenience, I have added a direct link to the initial troubleshooting steps at the top of the OP.
[Android Software Development] MitchiePitchie:
You mean the rw- r-- r--? Is that how it suppose to be ?

---------- Post added at 09:00 PM ---------- Previous post was at 08:34 PM ----------

Got it to work now. Any idea on how to make it work with viper4android? I need the Clarity option in it. Seems like the viper4android driver gets automatically uninstalled when you have the Dolby. Any work arounds?
[Android Software Development] guitardedhero:
Those permissions are correct, yes.

The v4a library is still "installed", just not configured in the audio effects configuration that ends up symlinking to vendor by Magisk during boot.

V4A's terminology can cause confusion with terms such as "driver", "install", and "uninstall".

I am still working on the audio effects configuration performed by the zip so your results can still be normal when installing the zip over existing mods that also symlink an audio effects configuration to /vendor.

In the meantime, you can do similar edits to the audio effects configurations as you did to the manifest.xml.

For official v4a in audio_effects.xml under <libraries>:

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

For official v4a in audio_effects.xml under <effects>:

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

For official v4a in audio_effects.conf under libraries {:

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

For official v4a in audio_effects.conf under effects {:

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

The unofficial v4a only differs with the library name itself in /vendor/lib/soundfx/ so just ensure that the "path" element under "libraries" in either configuration matches the name of the v4a library in /vendor/lib/soundfx/.

The effect name does not matter as long as the "library" element matches the "library" name element under "libraries".

Items below in build must match each other or be the correct spelling/location of the library itself depending on which configuration is used - either audio_effects.xml or audio_effects.conf:

For official v4a in audio_effects.xml under <libraries>:

For official v4a in audio_effects.xml under <effects>:

For official v4a in audio_effects.conf under libraries {:

For official v4a in audio_effects.conf under effects {:

I know this can be confusing, just pay close attention to surrounding library and effect elements to ensure proper formatting as well as proper values.

If you need further assistance just ask. :good:
[Android Software Development] MitchiePitchie:
Will viper4android and your dobly work after doing this? I understand what to do although a little confused.
[Android Software Development] guitardedhero:
Indeed, I was near that point towards the end of my post lol.

Both Dolby Atmos and v4a work great together.

I tried the unofficial v4a version for the first time a couple weeks ago and found that it was unable to process LDAC no matter what I tried, so I went back to the official v4a.

If using the unofficial v4a, LDAC processing is the only thing that wouldn't work - to answer your question regarding working together.
[Android Software Development] ShadoV90:
[MENTION=9896370]MitchiePitchie[/MENTION] First try. You will not know if you don't try. It should work, but try first.

[MENTION=4445176]guitardedhero[/MENTION] as i remember viper4android limits processing to 48000Hz/16 bit. Am i right?
[Android Software Development] guitardedhero:
Yes, but v4a does not process "out" directly, hardware/codecs do that afterwards.

The dumpsys for audioflinger provides the output information as well.
[Android Software Development] MitchiePitchie:
Re:

I did the instructions. It does work but somehow viper4android closed 3 minutes into music session. Needs to relaunch it when it closes. Will i need to install Audio Modification Library ?
[Android Software Development] guitardedhero:
Reboot the device and then inspect /vendor/etc/audio_effects.xml and no other location to see the configuration Magisk is symlinking from one of the installed modules.

Go ahead and post it so I can inspect it as well.

If anything needs adjustment, this will need to be done to the source configuration in one of your modules.

Comparing files size is likely sufficient to discern the source configuration from any others.
[Android Software Development] MitchiePitchie:
Im using the latest Viper4Anroid FX from magisk manager downloads combined with your dolby with no Audio Modification Library module installed
[Android Software Development] guitardedhero:
Here's a testing v4a module zip that I'll be using to test the manipulation of audio effects configurations to eliminate any need for additional steps or zips like AML.

I thought I might as well just post it here since it is and will be part of my development in getting the Dolby Atmos zip to accommodate everything needed for consistent configuration of all present audio mods on the device including stock content.

If having issues preparing audio effects configurations manually while v4a is installed or if wanting to add a v4a installation, this zip should resolve that for now.

Keep in mind that this is the official 2.5.0.5 v4a and not the unofficial 2.7 v4a. I will never give you guys something I do not use myself so that I can always provide adequate support and assistance for you guys at any time.

I tried to use 2.7 so that I could become familiar with what could possibly be a more common v4a installation for XDA users, but 2.7 is/was unable to deliver what 2.5.0.5 has always provided me: LDAC processing is crucial as it is 90% or more of all listening sessions.

It's nothing personal, I assure you. Plus, the default ViPERBass frequency setting at 100hz I noticed in 2.7 is just begging to cause "dropout" issues for many that enable it without looking at it or making any adjustments to it. I recommend 40hz (official v4a default) to 50hz max, or lower than 40hz if the receiver speakers handle it appropriately.

Edit*

This zip is not limited to Magisk Manager installations.
[Android Software Development] MitchiePitchie:
This zip was tweaked or is this just the same module from magisk downloads?
[Android Software Development] Wolfcity:
Sounds like it's clearly a tweaked/modded version...
[Android Software Development] guitardedhero:
The configuration you attached does not include the Dolby effect configuration. If Dolby Atmos is currently functioning properly, the configuration you attached is not what is symlinking to /vendor/etc/.

I'm sorry this seems like such a pain in the ass, this is simply a shortcoming of Magisk allowing module folders to contain files of the same name/location when only one instance can ever symlink to /system, /vendor, or wherever.

Zip up module folders containing any audio effects configuration and attach them as well as /sbin/.magisk/mirror/vendor/etc/audio_effects.xml and I will examine everything to provide you a solution.

Also, one piece of additional information I encourage you guys to become familiar with:

The dumpsys utility for audioflinger is how you can determine if audio_effects.xml or audio_effects.conf is the configuration used by audioflinger at any given moment when the rom supports the newer audio_effects.xml:

Underneath the list of loaded libraries is a single line of the result output from loading audio_effects.xml. You can refer to the attached screenshot to see what I am describing.

This line will say one of three statuses:

The status in my screenshot shows that the xml configuration is partially loaded as it had to skip 1 element. This is likely due to my forgetting to comment out the "hw_acc" effect as doing so allows the status to be "loaded successfully".

It is important to understand that as long as the the effect libraries of interest are loaded, a "partially loaded" status is still successful.

A "failed to load" status indicates a formatting error of the xml and that audio_effects.conf is the configuration used. This means that anything done (besides correcting the error) to audio_effects.xml will not matter since audio_effects.conf will be the configuration loaded until audio_effects.xml no longer contains any error.
[Android Software Development] guitardedhero:
This appears to be the same as the previous one. Both could be the same from those two different locations. But, with Dolby Atmos functions, these two configurations seem to be inactive anyway.
[Android Software Development] guitardedhero:
Tweaked installation. The apk and effect library are official stock and untouched.
[Android Software Development] Mervingio:
So can be used on A10 plus your Dolby Atmos too?

OP6T btw
[Android Software Development] guitardedhero:
Adjustments to audio effects configuration maneuvers.

Success can be determined by installing a single zip while other mods are already installed or installing both zips with no audio mod already installed if everything installed still functions properly.
[Android Software Development] Mervingio:
Not sure but Dolby crash I need install via Magisk or TWRP?
[Android Software Development] ramrastus:
I already installed DA 0.64 & v4a 2.7. can i flash this two zip over on it?
[Android Software Development] guitardedhero:
Dolby zip still will only install via Magisk Manager.
[Android Software Development] guitardedhero:
If you want both v4a apps, yes.

Your scenario can test success by flashing one of the two zips.

If flashing the Dolby zip results with Dolby working and v4a 2.7 still working, it was successful.

Important note:

Installation success results from existing audio mods that function before flashing still functioning after flashing.

An existing third party audio mod that does not function due to some effect configuration issue will not be "repaired" and function after installing these zips- if that makes sense.
[Android Software Development] guitardedhero:
Apparently, I introduced an error in the latest Dolby zip - unusual, right?

Sit tight. :good:
[Android Software Development] guitardedhero:
Round 2.
[Android Software Development] ramrastus:
Bro working great on ma op7pro.. but DA effect automatically stopped after switched to other apps (i mean come out of that app it stopped working) & again it's worked after get into DA Why?
[Android Software Development] gyuuuu:
manifest.xml doesn't save correctly after input
[Android Software Development] anvesh583:
Both are working great .
[Android Software Development] guitardedhero:
There may be something else taking over, that is NOT expected behavior. Anything else installed that may be the culprit?

If write privileges are unavailable while booted, simply prepare a copy of your manifest..xml on /sdcard and do the following:

Boot to recovery

Mount > Vendor

Advanced > File Manager

Navigate to /sdcard/manifest.xml > Copy

Navigate to /vendor/etc/vintf > Paste

Navigate to /vendor/etc/vintf/manifest.xml > chmod > 0644

Mount > Uncheck Vendor

Reboot

:good:
[Android Software Development] gyuuuu:
Pixel 3 has no twrp recovery

I'll wait for another way
[Android Software Development] guitardedhero:
Have you been successful in modifying partition content directly at all or is a Magisk module symlinking to the partitions the only way?
[Android Software Development] gyuuuu:
The original partition will not be modified

Magisk module symlinking to the partitions the only way

my mainfest.xml
[Android Software Development] guitardedhero:
I was afraid that may be the case.

You can try creating the /data/adb/modules/dolbyatmos/system/vendor/etc/vintf directory with 0755 permissions and place a prepared copy of manifest.xml there with 0644 permissions.

Unfortunately, I have little confidence this will be sufficient.

Once booted, navigating to /vendor/etc/vintf/ will show the patched manifest, however, log entries showing the same "not found in manifest" errors will likely be the case.

The patched manifest simply did not symlink to vendor in time (by Magisk) to allow the Dolby service to be registered.

This is precisely why there is a "system install" element in this port module.

Of course, I am wrong all the time and I would love to be wrong about this lol. :good:
[Android Software Development] gyuuuu:
The content is entered correctly but it still does not run.
[Android Software Development] guitardedhero:
Directly on partition?
[Android Software Development] gyuuuu:
/ data / adb / modules / dolbyatmos / system / vendor / etc / vintf / mainfest.xml

I pasted this path and it also showed up on my system
[Android Software Development] guitardedhero:
Yeah, that is exactly what I was describing above. It appears everything is in place but still won't work.

It is because the manifest.xml symlinks too late during boot by Magisk to get the Dolby service registered.

I know this because the log errors are the same as well as the failure to launch the app, and placing that very same manifest.xml from the module to the partition fixes everything (when everything else is correct).

This is how I came to the conclusion that hwservice registration occurs earlier in the booting process than does the symlinking of Magisk modules to the partitions.
[Android Software Development] gyuuuu:
Doesn't it apply if I don't run the app?

Thank you for your effort
[Android Software Development] guitardedhero:
I don't understand the question.
[Android Software Development] guitardedhero:
I want to let you guys know I submitted an issue at Magisk's GitHub repository requesting John to take a look at the viability of supporting the registration of hardware services from a Magisk module source.

Here's a link for anyone interested in following the issue submission:

https://github.com/topjohnwu/Magisk/issues/2291

A resolution satisfying the request means 100% module with no partition modifications and instant compatibility with devices currently lacking any capacity for write operations on partitions like some Pixel devices.
[Android Software Development] MitchiePitchie:
Mine skipped 4 elements. Does this mean it didnt worked?

Both Dolby and Viper seems to work when i try to change parameters in both apps.
[Android Software Development] guitardedhero:
I doubt the atmos effect is one of those four skipped elements (likely two libraries with their effects skipped as well) but I have no way of knowing without seeing the top of that output which actually lists the "skipped" libraries.
[Android Software Development] Mervingio:
I tried but still same error....
[Android Software Development] MitchiePitchie:
List of libraries. Will this help?
[Android Software Development] guitardedhero:
What to do.

The atmos library is loaded. Is there a Dolby effect-chain in the lower section of that output?
[Android Software Development] MitchiePitchie:
Seems like there is, and everything works. I just dont know if it works as you intended
[Android Software Development] guitardedhero:
My intention is for it to work as you would expect.
[Android Software Development] MitchiePitchie:
Finishing

Final Testing done. All parameters works in Dolby combined with Viper4AndroidFX. Viper parameters works too combined with the Dolby ones.

Confirmed working in Galaxy A5 2017 HadesPie.

Great work dev.:laugh:
[Android Software Development] guitardedhero:
Thank you. I'm calling it a night now lol. :good:
[Android Software Development] JakunTech1010:
Hello

Can you take a look at this libhidltransport.so please:

https://drive.google.com/file/d/13WBnHZ18zNcj0vTZBagXU2ILfKijwc8M/view?usp=drivesdk

This is libhidltransport.so from Samsung A70 A705F/DS (A705F) running Android 9 Pie

If this compatible I will try out DolbyAtmos Pie Port right now cause I waited so long for this.

Thank you.
[Android Software Development] MitchiePitchie:
Back up and test. Then use trouble shooting guide from OP and give feed back
[Android Software Development] Ceejay343:
Can confirm working Atmos and V4A your versions. No need to use Audio Compatibility Library to patch V4A. Atmos and V4A apps work normally as t would seem.

Xiaomi Redmi Note 7, AOSiP Android 10. Thanks!

I did get an IO error on Viper4Android installing the driver before removing the other V4A i had on. So clean-ish system then no problem. I flashed Dolby first. Also plays nice with already present Mi sound enhancer.
[Android Software Development] NE0HP:
This version of Dolby Atmos works without any issues which I faced in earlier version such as some apps like yt, vlc and system UI fc as reported earlier..Thank you. :highfive:
[Android Software Development] alok932:
In my case its partially loaded with 3 skipped but unfortunately there is no mention of dolby library at all.
[Android Software Development] guitardedhero:
This is precisely what I wanted. Thank you for testing these for me. :good:

I'd like to see your dumpsys output and the audio_effects.xml in the module.
[Android Software Development] guitardedhero:
The library seems to no longer be able to be downloaded.

I predicted widespread compatibility, but compatibility has already surpassed my highest expectations.

Incompatibility on Android Pie seems to be quite rare, actually.
[Android Software Development] louis-JYG4t:
The link you posted leads to a "no results found" page.
[Android Software Development] Adamk102:
the latest version was installed by magisk. the phone started but dolby did not work. Xiaomi Mi6 Miui 11 android 9

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] alok932:
Sure, here it is with some other files if needed. Btw i am using pocofone with android 9 and miui 11.
[Android Software Development] Ceejay343:
YW you do all the hard work though :D

It feels really stable, you need some more testers? I can drop a post in the Redmi Note 7 forum pointing to this thread explicitly asking for Tech savvy testers, in the Dolby Digital app topic there are 6 pages of people not getting it to work, think about 10 or 15 guys. Would that be too much to handle at this point? Just a suggestion. If i dont hear you say do it, i wont, no worries.
[Android Software Development] guitardedhero:
refer to the OP where I recently posted a link at the top for troubleshooting that will direct you to the information necessary to get everything working with minimal effort. :good:

Nothing else installed?

The audio effects configuration appears to be correct, but your dumpsys shows a stock configuration.

You might try installing again, the latest zip. :good:

You will never see a restriction in the OP.

This is the property of Dolby, and I didn't even ask if I could borrow this stuff.

Just because I stole it first doesn't mean no one else can do anything with it lol.

Feel free to do as you wish. :good:
[Android Software Development] guitardedhero:
:eek:
[Android Software Development] mrrocketdog:
QUOTE=guitardedhero;81533553]Here's a testing v4a module zip that I'll be using to test the manipulation of audio effects configurations to eliminate any need for additional steps or zips like AML.

I thought I might as well just post it here since it is and will be part of my development in getting the Dolby Atmos zip to accommodate everything needed for consistent configuration of all present audio mods on the device including stock content.

If having issues preparing audio effects configurations manually while v4a is installed or if wanting to add a v4a installation, this zip should resolve that for now.

Keep in mind that this is the official 2.5.0.5 v4a and not the unofficial 2.7 v4a. I will never give you guys something I do not use myself so that I can always provide adequate support and assistance for you guys at any time.

I tried to use 2.7 so that I could become familiar with what could possibly be a more common v4a installation for XDA users, but 2.7 is/was unable to deliver what 2.5.0.5 has always provided me: LDAC processing is crucial as it is 90% or more of all listening sessions.

It's nothing personal, I assure you. Plus, the default ViPERBass frequency setting at 100hz I noticed in 2.7 is just begging to cause "dropout" issues for many that enable it without looking at it or making any adjustments to it. I recommend 40hz (official v4a default) to 50hz max, or lower than 40hz if the receiver speakers handle it appropriately.

Edit*

This zip is not limited to Magisk Manager installations.

galaxy s4 i337M. stock rooted 5.1.1.

updater script says , "magisk only".

flash ends with error 1. or is this only for O and up.

data connection issue. cannot upload recovery log. :(
[Android Software Development] Bogdans29:
wht you using this on marshmallow this is pie version...
[Android Software Development] JakunTech1010:
So I tried to install the new dolby atmos pie port and here is what happened:

First attempt: Dolby installed without any error. I also disabled Viper4Android 2.7.1.0

Result: I stuck on Samsung Galaxy A70 powered by android... waited 30 minutes. I know somethings was wrong so I removed Dolby Atmos. And the phone booted :confused: :(

Second attempt:Dolby atmos+Viper+Audio modification library( it did not detect Atmos)

Resault: Liveboot showed up but after that it went dark. Nothing but darkness and long 30 minutes wait. So I removed Dolby and it booted (I do reinstalled Magisk with newer TWRP using TWRP Magisk Patch method)

So can anyone help me with this please? :crying:

Oh I forgot: My phone is Samsung A70 A705F with OneUI and Magisk 20.3
[Android Software Development] mrrocketdog:
no i'm asking it on lollipop.

and the real point is gh said not limited to magisk manager but if someone had a different recovery i dont think it would work because of updater script. but , hey i'm no dev ..... so there you have it.
[Android Software Development] Bogdans29:
the point this is pie + version.. your Android is 5.0 and android 9.0+ how completely different way how audio works..
[Android Software Development] mrrocketdog:
no. once again its me questioning the updater script. i'm out. :)
[Android Software Development] Skittles9823:
Yea the customize.sh aborts if a device is on lower than pie.

require_pie() {
ui_print " "
ui_print " • Only Android 9.0+ supported"
ui_print " "
exit 1
}

if [ "$API" -lt "28" ]; then

require_pie
[Android Software Development] alok932:
I don't think so. I had installed Ainur Sauron before. I am using v0.7281 zip but its same output. Thought it might be custom kernel but switching to stock kernel another custom kernel resulted in same.

Attached log for "dolby" keyword, if it helps.