yashsingh1/xdaforums huggingface dataset:
[Android Software Development] JakunTech1010:
Well this DolbyAtmos mod already made to work with both Pie-Q. I even managed to get it to work with Viper4Android

So what I did (I didn't know at first I could work) was:

- Install latest DolbyAtmos (currently 0.842)

- Install Viper4Android 2.7.1.0 driver and let it restart

- Press the + button in Magisk and rechoose DolbyAtmos zip

- Restart and enjoy

Hope it could work with you. I'm on LineageOS 17.
[Android Software Development] Lord Sithek:
I don't have any idea how to get Dolby working. Installation of the latest version is successfull without a problem, but not processing the sound. Nothing is changing when I'm playing music :crying:

Xiaomi Redmi Note 4X, DerpFest 10 ROM, Magisk stable 20.3
[Android Software Development] Qwerty182:
After update rom dolby atmos can't opened sir, please help
[Android Software Development] guitardedhero:
Please attach the following file:

/vendor/etc/vintf/manifest.xml
[Android Software Development] mohand06:
Hi [MENTION=4445176]guitardedhero[/MENTION], keeping only dolbyatmos as sound mod is OK for me except that I can't access the presets because the UI is just an icon that doesn't respond at all.

Viper atmos redux is for 64bit, I'm on 32bit but v4afxaroma-legacy_v4.4.zip works fine (Android 9)
[Android Software Development] guitardedhero:
Thank you very much. Place in the following directory with 0644 permissions before rebooting:

/sbin/.magisk/mirror/vendor/etc/vintf/

:good:
[Android Software Development] Qwerty182:
Its work sir, thank you very much ?
[Android Software Development] guitardedhero:
Hey, man!

Confirmation can be confirmed by the output of running the following in terminal:

su -c /vendor/bin/hw/*dolby*

32-bit support will come with its very own 32-bit Dolby Atmos™ port once we arrive at version 1.0 with this one.

Those that know me well enough know that I detest versions after 1.0 and view them as a sign of failing on version 1.0, so hopefully, 1.0 allows me to begin working on other stuff beginning first with the 32-bit port and then preparing a catalog of sorts providing an assortment of various dax_default.xml files from me as well as others - that means each of you has an opportunity to contribute something that will be included in the ports and in a stand-alone package, so delve into the dax_default.xml file and experiment with toggling components on or off and adjusting other values.

I tend to type quite a bit, but that may very well be a new record for my longest sentence ever lol. :good:
[Android Software Development] Mervingio:
Only hope final version can work on OP6T A10 works before update to the latest version keep your outstanding job my friend!!!
[Android Software Development] shantam3108:
Same here dolby atmos not opening
[Android Software Development] guitardedhero:
The Dolby hardware service is already registered in this file.

Please attach /sdcard/dumpsys.txt after running the following command in terminal:

su -c dumpsys media.audio_flinger > /sdcard/dumpsys.txt
[Android Software Development] yyz71:
It's installed but won't open. Pixel 4 stock rom..

here are the files :good:
[Android Software Development] shantam3108:
Here
[Android Software Development] the_poseidon:
There is any available dolby version which can be install to Magisk 20.3?

I use android 10 n mi room 20.1.21
[Android Software Development] JakunTech1010:
It's weird but if I use Dolby for sometimes then suddenly it just stopped working: Although the app show it have already turned on but I fell no difference modifying equalizer or turn it off and on. Did anyone experience this or it just me :(
[Android Software Development] Lord Sithek:
I managed to get Dolby working, but I don't really know why. I installed Dolby separately at first, but it didn't work. Then I flashed latest Viper Redux and suddenly Dolby started to work, along with Viper. So I have two modules in Magisk installed now. How and why is this working - I don't really know :confused: But I'm glad :victory:

And, of course, big thanks to [MENTION=4445176]guitardedhero[/MENTION] for resurrecting those great modules! :highfive:
[Android Software Development] mohand06:
32-bit support will come with its very own 32-bit Dolby Atmos™ port once we arrive at version 1.0 with this one.

Those that know me well enough know that I detest versions after 1.0 and view them as a sign of failing on version 1.0, so hopefully, 1.0 allows me to begin working on other stuff beginning first with the 32-bit port and then preparing a catalog of sorts providing an assortment of various dax_default.xml files from me as well as others - that means each of you has an opportunity to contribute something that will be included in the ports and in a stand-alone package, so delve into the dax_default.xml file and experiment with toggling components on or off and adjusting other values.

I tend to type quite a bit, but that may very well be a new record for my longest sentence ever lol. :good:[/QUOTE]
[MENTION=4445176]guitardedhero[/MENTION] I'm sure that your followers appreciate your writing skills as much as your sound mods!

For my point, I understand well that a fully working Dolby is for a certain hardware but nonetheless v0.842 effects are present on my 32bit exynos los16 without the possibility to play with the settings since the UI doesn't open.
[Android Software Development] aarkee:
[MENTION=4445176]guitardedhero[/MENTION] I have managed to edit the manifest file on the vendor, but the app is still crashing.
[Android Software Development] guitardedhero:
The manifest.xml you attached does not have the Dolby registration added and your dumpsys appears to have no Dolby effect-chain.

What exists inside:

/data/data/com.dolby.atmos/shared_prefs/
[Android Software Development] guitardedhero:
Man, I really, really wish I had something better to say, but you are pretty much at the mercy of tjw including support for linking manifest.xml early enough during boot to register the service from a module as well as at the mercy of logical partitions getting write access.

Both seem unlikely, unfortunately.

I've known you for a long time and I'd do everything I could to get you going but these two roadblocks are insurmountable as they exist today. :(

Another missing Dolby effect-chain...

We may need to dive into the logs a bit. If you can provide some logging events filtered with "dolby" and "dlb" while attempting to launch the app, I'll see if I can isolate the issue. :good:

20.3 is, in fact, the version I recommend and use. :good:

Yeah, that may result from a scenario such as losing audio focus, which should be restored by toggling the app off and back on. Has this failed to restore processing for you?
[Android Software Development] JakunTech1010:
Well I do try turning it off and on inside the Dolby app but it didn't work

However restarting my phone seems to temporarily solve it but after a few minutes or hours Dolby just stopped working (The app still work, but there are no effects)

One more things I forgot to mention: I do install Viper4Android 2.7.1.0 and it worked alongside DolbyAtmos. When Dolby stopped processing so does Viper: I toggle Viper on but driver status just said Enabled:No.

So is there anyway to fully fix this? Did Viper cause this? ( No way since both Viper and Atmos worked together).
[Android Software Development] guitardedhero:
Yeah, that's totally not right. Even having to toggle Dolby off and on to get it working again isn't right and was suggested only to see if audio focus was causing this.

To answer your question, Dolby can be impacted by another dsp not processing, especially ViPER4Android. For this very reason, ViPER4Android 2.7 spent a total of 20 minutes on my phone for testing purposes as I was assuming this version might be the more popular one today and I felt I had better familiarize myself with it when preparing to begin testing the new Dolby port.

Never again will I install that mess on my phone. It was a total collapse of what I had become accustomed to with the official ViPER4Android builds and support seemed to be a joke with responses like "But ViPER4Android has NEVER processed LDAC?!".

Yeah, okay.

Combine that with the arrogance of those manning that project with the fact that neither [MENTION=1569052]viper520[/MENTION] nor [MENTION=3901724]zhuhang[/MENTION] is given proper credit in that OP along with no trace link to the original thread and you end up with something uncomfortably large they can choke on.

You guys should use what you want and not feel bad for doing so, either.

But I personally feel I am quite adept at manipulating ViPER4Android, and certainly credit its existence and my working with it to maximize its installation success for my growth as an XDA member - yet I couldn't even get 2.7 to process what 2.5.0.5 was processing immediately before making the switch.

But that confusing as hell "Master Power" button is now a much more logical "Master Limiter" button, so there's that...
[Android Software Development] the_poseidon:
Thanks but i mean i use magisk 20.3, n viper4android, which version of dolby can i install? Cuz i already tried couple of dolby and can not able to install with Magisk 20.3
[Android Software Development] crackerjack1957:
Permissions need to be set to 644 or permissive after install of Dolby if not opening while on enforcing?
[Android Software Development] yyz71:
[MENTION=4445176]guitardedhero[/MENTION]

Hey brother thanks for everything you're trying to do for me ?I totally understand what you mean! I remember when you started to port this.. Same thing happened when I owned the pixel 2 it was the audio flinger that was problem.. I moved on to the pixel 3 after upgrading to Android 10 no TWRP available. Now I have pixel 4 still no TWRP and the partition seems to be a pain in the ass!! Can't win with these phones! Nonetheless I still love em ? I managed to get Digital Dolby plus working. Not the same though. But I will keep my fingers crossed I have lots of faith in you? very talented developer ? Thanks again my friend ?

---------- Post added at 04:29 PM ---------- Previous post was at 04:28 PM ----------

[/COLOR [MENTION=4445176]guitardedhero[/MENTION]

Hey brother thanks for everything you're trying to do for me ?I totally understand what you mean! I remember when you started to port this.. Same thing happened when I owned the pixel 2 it was the audio flinger that was problem.. I moved on to the pixel 3 after upgrading to Android 10 no TWRP available. Now I have pixel 4 still no TWRP and the partition seems to be a pain in the ass!! Can't win with these phones! Nonetheless I still love em ? I managed to get Digital Dolby plus working. Not the same though. But I will keep my fingers crossed I have lots of faith in you? very talented developer ? Thanks again my friend ?

---------- Post added at 04:30 PM ---------- Previous post was at 04:29 PM ----------

Sorry for the double the post.
[Android Software Development] aarkee:
if anyone has an issue with crashing the app on launch with stock rom, just flash a custom kernal. it worked to me with op6 10.3
[Android Software Development] aarkee:
Try to flash a custom kernal and try.. I had same issue.. I flashed a custom kernal..now its working ?
[Android Software Development] Lord Sithek:
[MENTION=4445176]guitardedhero[/MENTION]

I see you are willing to help people, so maybe you'll be able to help me... I'd really love to use your Dolby & Viper together :)

This is my issue:

I was trying to get latest Dolby (0.842) or Viper Redux (0.10) work. After flashing Redux in Magisk, Viper is able to process the sound, but Dolby is not. Also I've tried to flash Dolby alone and Dolby along with the latest Viper 2.7, but with no success. Dolby just doesn't want to cooperate :D The only scenario when I'm able to make Dolby process the sound is when I flash Dolby module first and then flash Viper Redux or when I do it in reverse order. So two modules are present in Magisk. But I observed that after clearing dalvik & cache in recovery Dolby stopped working again.

I must admit that combining Dolby with Viper gives mindblowing results! So I'm determined to get them work togheter :cyclops:

I'm not very skillfull in this matter, but I've read some recent pages of this thread and I concluded that the files I attached here may be helpful to you. I took them when only Viper Redux was installed on my device (the only desired module). Of course, If you would need any other files/logs, I'll provide them with pleasure.

My device is Xiaomi Redmi Note 4X (mido), ROM: AOSiP Derpfest Android 10. I use Magisk 20.3 stable.

I'll be grateful for any help.

Regards
[Android Software Development] Mervingio:
DAMN IT THAT`S IT :good: :highfive: :victory:
[Android Software Development] EstherTakumi:
What version of Dolby you use? And what custom kernel do you use?

Im using Exkernel, but Dolby not working for me, still force close.
[Android Software Development] aarkee:
What is your device.
[Android Software Development] _BГ@ckθut:
Got it fix? I used Omega right now forget to mention!
[Android Software Development] siwan05:
I'm running OP5 on OB5, blu_spark #94 kernel and Magisk 15.3.

I've successfully installed 20180205-1 together with V4A v1.0(2.5.0.5) together with the new AML (1.0) and it works fairly well.

I can get both DA and V4A to process whilst listening via BT but if I pause and resume audio V4A stops processing. I then have to disable master power on V4A, restart V4A and then enable master power and it works again (until the next time I pause the audio.

Any suggestions on what might be the issue?
[Android Software Development] MMWolverine:
I'm also trying to find a solution for the V4A processing issue.

[MENTION=4445176]guitardedhero[/MENTION] Does this still work for you and where exactly did you delete this folder from?
[Android Software Development] Golv:
[MENTION=4445176]guitardedhero[/MENTION] THX for update!

Same here.

HTC U11 (Oreo), Magisk 15.3...On first flash it detected the previous install 0202 and uninstalled it, flashed again to install 0205-1 but device in bootllop.

Then clean install rom with magisk and 20180205-1 after. Device still bootloops.

After that I mounted /system in TWRP and looked: there is no DolbyAtmos.apk in /system/app/DolbyAtmos/ or in /system/priv-app/DolbyAtmos/ , no soundfx folders, no dolby_dax.jar in /system/framwork...

Log attached.
[Android Software Development] btb55:
Thanks for the update.

I already had 0202 installed and working so now updated with 0205-1. On the first flash it detected the previous install and removed it, flashed again to install the update and succeeded. Audio is processing and over bluetooth the improvement is nothing short of amazing.

OP3T with OOS 5.02 and Magisk 15.3, the recovery log is attached in case it might in anyway be useful to help find why other don't get success.
[Android Software Development] memeda:
this suport for rom CARDINAL-AOSP oreo ?
[Android Software Development] jandia7381:
Reporting - just clean flashed update Nos to my Kate and reflash atmos unity but its not processing. In system its located on system/vendor/app and of course on system/magisk too. Before, when its work the atmos folder is located on system/priv_apps. Should i try remove the folder to priv_apps dev? Or anyone please guide me. Tqia
[Android Software Development] Jobe1105:
Updated to the newest build and it installed fine but it's not processing :(

OP3 NOS 8.1
[Android Software Development] ckpv5:
Try delete the one in priv-app if any, no harm trying I guess.

I don't have any in system/priv-app or system/app and dolby atmos works just fine.

Anyway this is on Nexus 6p. And I removed stock MusicFX too.
[Android Software Development] guitardedhero:
Changelog

:

[B]20180206 -[/B]

- Various error corrections.

Note

:

Due to the integration of Unity to maximize installation and functionality success, the arise_parameters.prop options of /system installations for Magisk users and /system-less installations for SuperSU users are not currently supported due to the immense effort required to accommodate those options with this new Unity integration.

The option of installing the additional system libraries from the native firmware of the port still exists in its full form and is still automatically included for the two scenarios currently known to require these additional libraries:

Axon 7 devices

HTC devices

It is important to realize that the two options no longer available were never provided as a means to obtain a successful and functional installation. The remaining option of installing these additional libraries is, in fact, an option to secure a successful and functional installation in the event that the default installation is unsuccessful or non-functional.

:good:
[Android Software Development] Trupen:
Build 6-2 is perfectly installed app is there and it is not conflicting with viper

Only problem is it is not working fc
[Android Software Development] laugeek57:
20180206 - Unity :confused:

Not processing on mi A1
[Android Software Development] Trupen:
Pls find attachment
[Android Software Development] jandia7381:
Reporting - success flash latest unity update, atmos installed not fc but not processing

*redmi note3 SE a.k.a Kate

*latest magisk beta

*latest Nos 8.1 official
[Android Software Development] yyz71:
The only one that install is DolbyAtmos_for_Oreo_(Unity)-20180205.zip but it force closes!
[Android Software Development] guitardedhero:
Who wants to be me right now lol?

Those with FC, please perform some auditing procedures outlined in the OP and provide your findings and outputs for me to examine. :good:
[Android Software Development] Trupen:
Can you pls explain in detail
[Android Software Development] guitardedhero:
Auditing

:

Assessing the installation is encouraged for all users and is especially helpful when the collected information is included in reports of less than perfect experiences.

Dumpsys:

The dumpsys utility in Android can be a very valuable troubleshooting tool, especially audio output processing related issues, when targeting the audioflinger service. Recommended terminal application's include Terminal Emulator for Android and Termux.

In Android Terminal:

su
dumpsys media.audio_flinger

or

su -c dumpsys media.audio_flinger

The output generated upon tapping the Enter key is the information of interest and can be copied from the Terminal and pasted with a report, if necessary.

This output includes the list of successfully configured audio sound effect libraries and any successfully created effect-chains from one or more of those libraries when combined with the successful installation of an appropriate apk, Dolby Atmos being one of many examples.

Logging:

The log utility in Android is another valuable tool for many various purposes, including troubleshooting. This utility is most convenient when used with a logging application such as Matlog in order to utilize features such as word filtering and syntax highlighting among others.

Using the logging application's search feature, the user can filter the displayed log output using words or characters relevant to this Dolby Atmos™ port such as: dolby, dax, dlb, dseffect and include that relevant log output with reports, if necessary.

:good:
[Android Software Development] Trupen:
Hope this helps
[Android Software Development] guitardedhero:
Changelog

:

[B]20180206-1 -[/B]

- Further error corrections.
[Android Software Development] laugeek57:
Not processing mi A1 :confused:

I did not know that Beethoven was part of your audio beta testers ... humor French :laugh:
[Android Software Development] marquelito:
[MENTION=4445176]guitardedhero[/MENTION] very happy to see you and dolby again. Unrooted for months and see your developement, i had to root again to use dolby.

Im on s9+ android 10 stock rooted, without twrp

So here is my problem:

installed redux 0.10. Viper ask for driver but cant install. And dolby doesn't open. I already read some posts but dont wanna mess with files without you're answer.

Already roboot without accept viper driver install. Then booted up it asks again. I accept, error installing driver. Re-installed module. And nothing works.

Attatched dumpsys and manifes.xml

Thanks! And keep going with your excellent work bro!
[Android Software Development] Mervingio:
Yes!!!!!!! but i used Blu Kernel :good:
[Android Software Development] _BГ@ckθut:
Thank for clarifying ill updated the thread and instructions here a little when i got time
[Android Software Development] yyz71:
It's not kernel related issue.. I've already got a custom Kernel installed! This has everything to do with the Pixel 4 partition not being able to modify probably.
[Android Software Development] guitardedhero:
Thank you and glad to see you, too!

Please attach /sbin/.magisk/mirror/vendor/etc/audio_effects_sec.xml as well.

What files exist in /data/adb/modules/dolbyatmos/system/vendor/etc/?
[Android Software Development] guitardedhero:
Everything looks great in those files.

Terminal output of?

su -c getenforce
[Android Software Development] marquelito:
So i have only /data/adb/modules/dolbyatmos/ with costumize.sh and module.prop. no system folder inside

Edit: maybe inside viperatmos? In there there is system folder and other but inside /system/app/ is dolby. Is normal????
[Android Software Development] Lord Sithek:
Wow, that surprised me... :eek: The output is "Permissive" since my custom kernel is permissive by default. Is it bad, worse or worst? :cyclops:
[Android Software Development] guitardedhero:
Man, not sure about all that. ViPERAtmos works as a stand-alone module and what I see could be an incomplete uninstallation or something.

Here those two files you provided me - fully patched for ViPERAtmos and ready to go.

manifest.xml must be placed in /sbin/.magisk/mirror/vendor/etc/vintf/ while booted or/vendor/etc/vintf/ while in recovery and need 0644 permissions.

audio_effects_sec.xml can be placed in /data/adb/modules/viperatmos/system/vendor/etc/ with 0644 permissions.
[Android Software Development] guitardedhero:
I might need to see some logs when attempting to get Dolby to "do something". The stuff you attached was taken with ViPERAtmos installed and Dolby not impacting audio?
[Android Software Development] Lord Sithek:
Yep, that is correct. What logs exactly should I provide you? I'll probably do it tomorrow since it's a bit late now in my location :) Thanks that you're willing to help! :highfive:

PS. I noticed that even if I get Dolby work for a while, often after the simple reboot it stops working again. It seems to be quite random.
[Android Software Development] guitardedhero:
My only guess at this point is Dirac being aggressive enough to cause Dolby to disable itself at times. You could test this without adding/removing anything by disabling the Diarc app(s) in Android Settings.

https://play.google.com/store/apps/details?id=com.dp.logcatapp
[Android Software Development] Lord Sithek:
Hmm, nice idea. I'll test it and report later. Thank you!
[Android Software Development] guitardedhero:
I just realized what you were talking about earlier lol.

I'm pretty sure that folder with only two files was from updating the module which exists in /modules_update/ with only the module.prop in /modules/ until a reboot.
[Android Software Development] EstherTakumi:
One Plus 6, but nevermind, got it worked after change back selinux on and off.
[Android Software Development] Lord Sithek:
I tried to disable other music apps in my device, I found one (MusicFX) and I removed it with Debloater Magisk module, but I'm not 100% sure if this is all I should disable... Still, once Dolby is working fine, once it isn't.

Anyway, I managed to take two logcats, the first one when Dolby is proccessing the audio, the second one when it isn't. I did them this way: First, I enabled Logcat Reader, then opened Spotify, started to play music, then opened Dolby and turned it on, changed some configs, went back to Logcat Reader and saved the log.

Maybe it can give you a clue of what is happening in my case :)

PS. For some reason I couldn't upload two separate .txt files, so I'm attaching them in a .zip.