yashsingh1/xdaforums huggingface dataset:
[Android Software Development] guitardedhero:
Please use TWRP for installation. I have been actively trying to be within the requirements for compatibility with Magisk Manager installations and module availability/access, but these requirements have proven to be quite restrictive as I have no desire whatsoever to use the Magisk Module Template script and its components.

It's nothing personal, it's simply that I like to be in control and know/be aware of every single line of code by being the one preparing the entire script.

But I am certainly trying to gain this additional functionality for you guys, I assure you. :good:
[Android Software Development] theduke7:
[MENTION=6315410]Skittles9823[/MENTION] you're right, i thought i did , but apparently it was just the code tag... corrected.

[MENTION=4445176]guitardedhero[/MENTION] still the same with latest release , module there but no app, attached the magisk log.
[Android Software Development] guitardedhero:
Just as I suspected, that log is about as short as Magisk crash could create. Try deleting /magisk/dolbyatmos/service.sh and reboot the device. :good:
[Android Software Development] guitardedhero:
Just as I suspected, that log is about as short as a Magisk crash could create. Try deleting /magisk/dolbyatmos/service.sh and reboot the device. :good:

Edit*

Found errors...
[Android Software Development] guitardedhero:
Interesting...

So, removing execute (x) privileges from "owner" is the difference-maker for you? Bootloop, in your case, results from 0755 permissions applied to the port's audioserver?
[Android Software Development] saiamrock:
I did it but the same, no audio processing

Using 0201 & 0202 got stuck on dolby text in recovery

I'm currently on Kate running NOS

Update: i got it work

So the problem is it conflicting with magisk

When i flash it, my magisk gone

I flash magisk my SIM not detected and dolby gone

I just keep trying and somehow it work now
[Android Software Development] jandia7381:
Thnx for the update.

No arise props dev? No need to edit? Just flash zip? Help me please dev [MENTION=4445176]guitardedhero[/MENTION]
[Android Software Development] truelies1:
Does this install directly under Recovery or need to do something else?
[Android Software Development] guitardedhero:
Changelog

:

[B]20180205-1 -[/B]

- Various error corrections.
[Android Software Development] marcdw:
Wondering the same as [MENTION=7062669]Zalwani7395[/MENTION]. The prop file only has an option of whether or not to install libraries. No longer any options for /system install.

Oops. Got ninjad by the update. ?

ZTE Axon 7 A2017U, CarbonROM CR-5.1-MOO, microG (NoGapps), Multiboot, Tapatalk 4.9.5
[Android Software Development] guitardedhero:
Geez, you guys are right lol. I know [MENTION=6037748]Zackptg5[/MENTION] was using a slightly older build but not quite that old lol!
[Android Software Development] guitardedhero:
"ninjad", you were not lol. This will take some time to implement correctly, I'm afraid.
[Android Software Development] marcdw:
Yeah, I just realized that. LOL.

ZTE Axon 7 A2017U, Stock B32, Tapatalk 4.9.5
[Android Software Development] yyz71:
It's installing on my pixel 2 but Dolby force closes. But at least it's showing in the module ?
[Android Software Development] jandia7381:
Just flashed. Working great & 'BOOM' on my Kate running latest Nos 8.1

Thnx again n again dev ?
[Android Software Development] Trupen:
Thankyou so much for this zip this is what we wanted

This installs Dolby perfectly

But it is conflicting with viper as I flashed Dolby zip it removed viper from magisk

When I again installed viper both stopped working viper and Dolby

Amy solution for this ? [MENTION=4445176]guitardedhero[/MENTION]

---------- Post added at 07:06 AM ---------- Previous post was at 07:03 AM ----------

Dolby is installed but not working
[Android Software Development] repey6:
Sorry but not audio processing as always on my Redmi 4x, Nitrogen 8.1, magisk. On Cardinal 8.1 , supersu badly else. Not processing and system issues.
[Android Software Development] YOSHI011:
I can't open YouTube go sir ?
[Android Software Development] Mr.Demous:
Latest build flashed fine on my Nexus 6 8.1 but Atmos is not processing.
[Android Software Development] arifqur:
The latest build flashed without any drama this time but the device still bootloops. Op3T running NOS8.1.

How to get it working one of these days. Thanks man for all the effort you put in.

Greatly appreciated
[Android Software Development] wutangkillabee:
LG g3 vs985 AICP 8.1 Flashes but then uninstalls says to many symbolic links encountered. No bootloop, it boots fine just displays no Dolby...
[Android Software Development] Trupen:
Earlier zip which used to work is now giving error 2 while flashing
[Android Software Development] cRaWnEr:
Same here for MiA1 with Oreo
[Android Software Development] Trupen:
Latest build installs Dolby but doesn't work and doesn't allow viper to work
[Android Software Development] Qwerty182:
Oh, i see. Thank you sir
[Android Software Development] Qwerty182:
Sir, now its work. The problem is the old module of dolby. Thank you so much
[Android Software Development] guitardedhero:
You bet! :good:
[Android Software Development] guitardedhero:
Added another manifest location variable. (Only relevant to Dolby)
[Android Software Development] alok932:
Installation fails with this new dolby file.
[Android Software Development] guitardedhero:
Thank you, [MENTION=5613876]alok932[/MENTION]. :good:
[Android Software Development] alok932:
Thank you for an updated file.
[Android Software Development] acuicultor:
Unfortunately still no luck for me, viper 0.18 nor viper redux 0.031 are able to install the driver automatically, i can place it manually in his location but we want to have a working zip, isn't it?
[Android Software Development] guitardedhero:
Yeah, I had the same result and made sure the rest of the module looked okay ( I manually made a userdata v4a.apk installation ), decided to reboot and check again, and then everything was all set.

And I'm not on Android 10, either.
[Android Software Development] acuicultor:
Uhh sorry forgot to attach the log of the error
[Android Software Development] acuicultor:
I tried what you did in every version you sent but never worked for me
[Android Software Development] JakunTech1010:
I installed the newest version of Dolby (0.792 is the newest for now) and Viper|Atmos Redux 0.031 and here is what happened:

No bootloop or pitch black screen :good:

Dolby finally process audio since I can fell diferences when turning on and off Dolby

Viper is a different story: it says it needed to upgrade driver. And when I check driver status, it says status abnormal and driver version is 0.0.0.0

So what happened to Viper it is normal? Should I update the driver? Will Audio Modification Library work with Dolby and Viper :confused: ? Thanks for answering all that questions.
[Android Software Development] niyonsv:
A bit OT.. My phone is OnePlus 7T and it comes with Dolby Atmos built-in. It is one of the reasons for not flashing any custom ROMs till now, even it is low in numbers, but HavocOS just released a test version for 7T.

Anyways I want to know is there any difference between the Dolby Atmos that's built-in to 7T and the versions in this post? There's no UI and customization, like in these, in the built-in 7T DA; just a few radio preset buttons. But other than that is there anything?

I remember those Nougat times when I flash the Dolby Atmos right after installing custom ROMs on my Lenovo Z2 Plus. So I'm so excited to test the new DA after the release of some stable custom ROMs for the 7T.
[Android Software Development] guitardedhero:
Man, I'm sorry. I'll try again tomorrow. So, you're having to compromise by either losing storage access or losing its "driver"? Have you had success with v4a 2.5.0.5 on Android 10 previously? Perhaps, you Android 10 guys are better off using v4a 2.7 , assuming that build avoids these two issues for you.

No, I added a forced userdata v4a installation for Android 10 and it seems to have kept the v4a effect configuration from loading for some while others like the Android 10 tester in the pic don't experience this.

I'm not sure if AML has been updated to support the custom effect UUID for this port, but feel free if supported.

I'll have a clearer head tomorrow and get a little more rest than normal as it's not even 02:00 yet.

I think the 0.161 v4a build was the last one before I introduced this recent change for Android 10 installation.

Goodnight! ?
[Android Software Development] guitardedhero:
I suspect they would sound quite different, but having only heard this one and never handling the OP7T I really have no clue lol.
[Android Software Development] Qwerty182:
Uninstal dolby atmos, just use viper atmos module because its include dolby and viper
[Android Software Development] acuicultor:
No bro, don't feel sorry, you're doing a great job, we all know that development is sometimes hit and miss with the huge amount of variables we manage.

Yes, i can't have the driver and storage permissions both working right of the box atm and no, v4a 2.5.0.5 didn't work for me yet in a10, 2.7 worked but needed audio modification library and didn't have compatibility with dolby atmos.
[Android Software Development] Skittles9823:
Just an fyi AOSiP for 7T will have the stock Atmos ported in the next update.
[Android Software Development] niyonsv:
?.. means the Dolby Atmos from the stock 7T? That's great. ?

Still I'm waiting for a stable TWRP, ROMs and DA by guitardedhero. I like a bit customization on DA (but that of V4A is too much for me :) ).
[Android Software Development] JakunTech1010:
Wait, so that viper|atmos redux is for Android 10. If that's true then OMG I'm on Pie (used to be on LOS 17), that's why it won't work. Also when I tried to disable and reenable Atmos it no longer work. I tried turning it back on and off but no used. I will try to reboot to see if that change something.

Also, is that Viper|Atmis Redux module is required to use Dolby Atmos or can I used different version (EX: V4A Legacy 2.5.0.5)? Thanks.

After a reboot from the mentioned problem above: Hello there my old friend: "Dolby Atmos keep stopping":confused: :crying:
[Android Software Development] anttaz:
This version of Dolby is showing in Magisk Canary as well as working in conjunction with viper.

OP3T OOS 9.0.6 pie

Many thanks :good:
[Android Software Development] shantam3108:
Viper installed and folder is also present but the app doesn't show up in app drawer or in all apps.

Running op5 cr droid 6.2 android 10
[Android Software Development] guitardedhero:
Right on, that's pretty damn sweet! :good:

I'm sorry for the confusion. I was just informing that Android 10 will (should, anyway lol) receive v4a installations in userdata, otherwise, typical v4a module installations.

:highfive:

Which zip, exactly?
[Android Software Development] shantam3108:
Latest zip 0.18
[Android Software Development] repey6:
Thanks. ViPERAtmos-Redux0.031.zip works perfectly on my Redmi 4x Havoc OS-v.3.1 , 10.0.
[Android Software Development] guitardedhero:
You might try installing the zip again. When testing the userdata v4a installation, I noticed a driver prompt once booted. I checked the module to make sure the rest of the stuff (besides the app) was there and just rebooted once more.

I didn't agree to the prompt to "install driver", just a reboot. V4a was working properly once booted. I'm not on Android 10, but I didn't want to start messing with userdata unless I could get the installation script correct to automate that.

You can certainly allow v4a to "install driver", but I would try a reboot first so that audio effects configurations remain untouched by the app if a reboot is all you need.

Man, that's amazing news!! :highfive:

The last viperatmos update was maybe close to four years ago?! :eek:

Man, the way time flies...
[Android Software Development] anttaz:
7292

Screens attached
[Android Software Development] shantam3108:
I would try but I don't see viper app. Module is installed and folder is there

Edit : the redux zip is working :)
[Android Software Development] guitardedhero:
Android 10? If so, the installation is intended to install v4a as a userdata app and an empty app folder in the module indicates that the "clean up" function isn't targeting possible "trash" properly.

The three latest versions of each zip (v4a, v4aatmos) should have the very same operations installing v4a so different results are certainly not expected, but different results (not working, now working) can certainly result from the reboot itself (after installing again or a different build/version).

Of course, I could be wrong. Happens all the time lol. :good:
[Android Software Development] acuicultor:
Sorry for the false alarm mate, after seeing some people having success with viper redux 031 decided to do a clean flash of my a10 rom and after that the zip worked flawesly, now I've the driver and the storage permissions both working so we can assume that the zip is fine and ready for a10. Again sorry for any inconvenience and thank you for your time and dedication. Cheers!!
[Android Software Development] guitardedhero:
Man, that's awesome to hear!

I was afraid it might have been a little too early to throw that out there while the script kept progressing along lol.

When porting the Oreo Dolby Atmos, my intention was to finally update the ViPER|Atmos™ series, but the port ended up lacking anywhere close to an acceptable compatibility for being an update to a series that nearly avoided any kind of incompatibility.

While working on this one and studying the various patterns to discern compatibility and comparing to random Pie firmware, I knew this was my chance to finally update ViPER|Atmos™ with content I prepared (except v4a, obviously) since I had never made an attempt to port anything four years ago.

The ViPER|Atmos™ thread has been completely neglected by me since ARISE™ made an appearance and I made a commitment to myself that I would return to the thread once I had something completely new and fresh to bring with me as I had begun porting apk's while working on the ARISE™ project.

All those Dolby Technologies for Android zips you guys might have seen 1-2 years ago were actually my preparation for the ViPER|Atmos™ update. It was going to be all of my Dolby ports: DDP, Dolby Audio, Dolby Atmos, and Dolby Vision along with v4a, and it was looking beautiful.

And then I ported Axon 7's Oreo build, where I found that the one thing everyone was going to be excited about was going to disappoint SO MANY people due to minimal compatibility, so I scrapped the entire project.

And now, the older Dolby Atmos and Dolby Audio (<-- I freaking love that one) ports are totally incompatible with Pie and 10, so Oreo really threw a wrench into my ViPER|Atmos™ spokes, big time.

So yeah, I'm getting pretty pumped up again. :good:
[Android Software Development] acuicultor:
Congrats for the great success mate!! It's awesome to have talented people like you sharing his work with us.
[Android Software Development] Skittles9823:
Yup. TWRP won't be coming any time soon due to dynamic/logical partitions so you can't really mount any partitions.

As far as I know the rom is fairly stable even though it's in alpha at the moment.

---------- Post added at 01:03 AM ---------- Previous post was at 12:58 AM ----------

Dolby Audio ?? dang, I remember that port. That was the real deal.
[Android Software Development] guitardedhero:
No doubt about it, Dolby Audio was an absolute banger! ?
[Android Software Development] repey6:
Can you make unity version? Need AML compatability.
[Android Software Development] Skittles9823:
AML isn't needed if you flash Lennon's zips last.
[Android Software Development] konsolite:
Is possible to add switch: Volume Leveler and Bass Enhancer to latest Dolby?
[Android Software Development] ShadoV90:
Virtualizer switch would be awesome too.
[Android Software Development] yyz71:
Has anyone with a pixel 4 got this working? And if yes please let me know how you did it.
[Android Software Development] Ronan Hansel:
This is such a great mod. The audio is loud, clear, immersive. This port is almost perfect, it's just Google Assistant that is having issues: its voice won't take effect. If this is fixed, the port will be the perfectest port ever.

Thank you!!!
[Android Software Development] repey6:
I know this. Many another sound mods exist, which need AML for collective work.
[Android Software Development] Samuel Holland:
For me to get Viper's driver installed PixelXL3 latest Havoc I've had to uncheck Audio_Modification, reboot and recheck, hitting install driver each time, and then success, but unfortunately I haven't got Dolby working on my device yet. Since we don't have working recovery I have to wait till I'm home to try some more to see if something might work. Thank you and everybody else to help this project become a reality. Like previously mentioned, in the older days with the Arise/Dolby, Wow used to be literally unbelievable. Dolby vision would be awesome. Thank you sincerely.
[Android Software Development] NE0HP:
For me on my device( Mi A2) running AOSiP 10, both Dolby Atmos and V4A 2.7.1.0 works perfectly fine without needing of AML.. My sequence of flashing is like, Flash Dolby Atmos first, reboot device and then flash V4A 2.7.1.0 (During flashing, It will mention that conflicting sound mods found and one must flash aml), reboot device install drivers and reboot device again to complete the installation. Just sharing above steps what works for me and it may differ with different devices and roms.
[Android Software Development] alok932:
[MENTION=4445176]guitardedhero[/MENTION]

i tried with fresh installation. Switched to fresh A10 but no luck yet for MIUI 11.
[Android Software Development] guitardedhero:
Yes, this is possible. However, to have any function, the libraries and xml must be compiled to support the functions.

There are variations in the many, many Dolby Atmos systems in Pie and Android 10 and I spent countless hours dissecting and testing many of them.

The port available now is the one I felt most confident to allow you guys to have a chance to experience it and to finally give me a chance to get some third party feedback on different setups.

Rest assured that I will continue to enhance and improve the Dolby Atmos ports as we progress in this thread. Once we hit a stable 1.0 release, I will then begin working on a 32-bit Dolby Atmos port and then begin working on porting some of the more challenging Dolby Atmos systems that include extra features such as Bass Enhancer.

If you are unable to modify your partitions directly as I suspect, it appears your best bet is a future Magisk update that accommodates my recent issue submission to Magisk's GitHub.

Thank you!

Anything else installed that has any sepolicy rules included? If this issue arose from the zips here, this will need to be resolved swiftly.

Please list any and all zips from this thread that create this issue for you.

As I understand, AML simply needs to include the unique UUID effect and library name to support this port and nothing on my end needs to be done. If AML has been updated within the last week or so, it may very well already have support for this port.

Forgive me, but will you remind what's happening right now? Zip version(s), other details, etc.
[Android Software Development] alok932:
Yes. As atmos was not showing in dumpsys we manually updated the audio effects file in /sbin/.magisk/mirror/vendor/etc. With this atmos shows but as NULL in libraries not loaded.

We checked and confirmed libatmos.so exists at vendor/lib/soundfx.

Last version i tried is 0.7292 and all results in same thing.

Attached some files you had requested.
[Android Software Development] guitardedhero:
Thank you. :good:

Do the following libraries exist in your rom in either /system/lib64/ or /vendor/lib64/:

liblog.so
libutils.so
libcutils.so
libaudioutils.so
libhidlbase.so
libhidltransport.so
libc++.so
libdl.so

Android 9.0 or 10.0?
[Android Software Development] alok932:
Yes this files exists at /system/lib64.

Android 10 now.
[Android Software Development] ckanth12:
Dolby Atmos force closes after rom update.

I clean flashed EvolutionX on my Poco F1 and flashed Dolby Atmos and it is crashing now. In previous build it worked fine. What could have gone wrong?

Used version 0.792.
[Android Software Development] Adamk102:
guys what file do I need to copy and where do I paste to make dolby work? installation proceeds without problems, dolby installs but does not turn on. Android 9 Miui 11

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] anvesh583:
It seems crashing with new a10 miui11 vendor.
[Android Software Development] ckanth12:
I haven't updated vendor yet, as the roms are not ready to be flashed on new a10 vendor.
[Android Software Development] guitardedhero:
Did you have a functioning Atmos system previously on 9.0?

I am not a "Read the OP!" kinda guy, but I provided a link to the Troubleshooting steps to aid you in finding what is happening and how to resolve if feeling comfortable doing so. Otherwise, I'd be more than happy to help you resolve the issue. Unfortunately, I just don't the capacity to find out what is amiss. You will need to do that and relay your findings to me. :good:

Have you confirmed "copy/paste"-ing a file will resolve your issue(s)?
[Android Software Development] guitardedhero:
It is important to know that until Magisk support for symlinking manifest.xml from a module to /vendor/etc/vintf/ early enough for added hardware services to be registered appears in an update, /sbin/.magisk/mirror/(vendor|system/vendor)/etc/vintf/manifest.xml (a hard file (not symlinked) when using Magisk in its current state) will need to be manually edited.

Any rom or firmware update that targets /vendor will result with the stock /vendor/etc/vintf/manifest.xml.

If the Dolby zip fails to successfully edit this file, /sbin/.magisk/mirror/(vendor|system/vendor)/etc/vintf/manifest.xml will need to be manually edited with the following section:

<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>

Just please ensure that this section is not pasted inside another section!!

Find the first instance of the following line:

<hal format="hidl">

and use enter to shift it and everything below one line down. Paste the section in the first code window on that empty line created indented four spaces to the right.

You'll see how it should look and any formatting error should stick out among the previously existing entries so just make sure it blends right in to where no one would be able to detect what was added, if that makes sense.
[Android Software Development] AndrzejDwo:
Hi! Today I've decided to do some testing on my s10+ running HadesRom OneUi2.0 (Android 10) and latest magisk Canary, so I've made full twrp backup and tried my luck with two zips.

First one was ViPERAtmos-Redux0.031.zip, tried flashing 3 times but each time MM was crashing during installation, after that I reverted MM to 7.5.1 and it worked but after reboot there was no Viper in app drawer and Dolby app was crashing.

Second zip was DolbyAtmos-0.7292.zip (flashed after restoring twrp backup), successfully installed but after reboot Dolby app was crashing, same result with or without AML.

Dunno if I missed something, didn't find anything in the thread regarding installation on Samsung devices... If there's anything I can do to help I'm open to it, hopefully it's only an user issue :silly:

Logs attached.

Cheers
[Android Software Development] ckanth12:
Above code is present in my manifest.xml.

from Matlog I think there is some selinux related issue if I am not wrong.

"01-24 02:13:52.383 E/SELinux (549): avc: denied { find } for interface=vendor.dolby.hardware.dms::IDms sid=u : r : hal_audio_default:s0 pid=810 scontext=u : r : hal_audio_default : s0 tcontext=u : object_r : hal_dms_hwservice : s0 tclass=hwservice_manager permissive=1"