yashsingh1/xdaforums huggingface dataset:
[Android Software Development] guitardedhero:
Hey, Dave!

The v4a zip has this restriction?

Which zip version(s)?

Sounds like incompatible libaudioflinger.so booting behavior. The early zips containef this library as it seemed pretty compatible and was interested to see how many setups accepted the port firmware audioflinger.

Samsung is most definitely incompatible.

It appears Dave is referring to the v4a zip which quoted me saying the Magisk Manager installation requirement was removed.

I sometimes say something before realizing I hadn't yet lol.

You might try making a backup of /sbin/.magisk/mirror/vendor/etc/audio_effects.xml and copying the module configuration in its place.

Ensure 0644 permissions before rebooting.
[Android Software Development] mrrocketdog:
"#Magisk". sorry i even brought it up. doesnt matter as almost everyone above nougat is going to have magisk anyway.

i'm out. back to trolling.
[Android Software Development] guitardedhero:
The v4a zip is intended to allow installation in recovery.

The Dolby zip is still limited to Magisk Manager installation but this will change very soon as the zip continues to improve - which it has quite a bit these last 2-3 days.

The requirement for Android Pie and up cannot change if I want to disappoint as few people as possible. There's a chance some Oreo firmware may be successful in gaining a functional Dolby Atmos system, but it's wiser to focus ahead on Android 10 rather than trying to get it to work on Oreo while risking impacting the installations of Pie and 10 negatively.
[Android Software Development] alok932:
I don't understand what to copy at that place. Is it any file/folder or some content? Can you help me with its location.
[Android Software Development] guitardedhero:
Rename /sbin/.magisk/mirror/vendor/etc/audio_effects.xml to audio_effects.xml.bak

Copy /data/adb/modules/dolbyatmos/system/vendor/etc/audio_effects.xml

Paste into /sbin/.magisk/mirror/vendor/etc/

Set 0644 permissions for /sbin/.magisk/mirror/vendor/etc/audio_effects.xml, if necessary.

Reboot
[Android Software Development] harris123424:
When Dolby Atmos is enable or disable dynamic and music its same. Only video and custom i see difference.
[Android Software Development] alok932:
Thanks for this info.

Now i can see dolby but its in libraries not loaded.
[Android Software Development] Ceejay343:
Hey you think anybody can do what you do? No way, man! hehehe I just meant if you dont mind some more people going " I installed your stuff, now every 3rd email in my inbox is borked, here are the logs can you fix it?" Besides I reconsidered against my proposal because you dont want too many people with MIUI in here. That ll make you grey haired in a hurry.
[Android Software Development] guitardedhero:
Does /vendor/lib/soundfx/libatmos.so exist?

Lol, I hear you. I've been down this rabbit hole more than once. I was just saying that permission isn't needed for stuff I'm "borrowing".

As for written content such as scripts, info, etc... Take it. Please take it. I prepare all that stuff with the hope that someone may be interested enough to see what's happening and what makes things work. I likely have the most readable, logical scripts around here.

I use spacing and small amounts of redundancy to make things easier to follow/understand.

In fact, I wonder how many already know that just the apk alone inside this archive is enough to produce the port as it is installed right now via Magisk Manager.

I merge the UI and Service apk's into one apk with all the necessary library, binary, configuration and script content along with information and directions for someone curious enough to look inside (apk=zip).

I did this as well with the Nougat and Oreo ports.

The reason I prepare such an apk is from my earliest efforts taking a stan at Dolby (Nougat era, when there didn't seem to be any progress porting it) where I found lots and lots of links to download various Dolby Atmos apk's. As many already know, a Dolby Atmos apk downloaded from a website does absolutely nothing for you except in rare cases where native Dolby Atmos firmware content provides no typical Dolby UI. What's the point of linking to apk's that cause nothing but disappointment, right?

When preparing my very first Dolby Atmos port (Axon 7 Nougat, oddly enough), I was thinking about scenarios where the zip may be extracted and its contents scattered and found by the curious trying to make something work.

What file inside might possess the highest probability of being distributed on its own? Well, the apk does, of course.

What I did then is no different than what I do now:

Pack the port content, script(s), configuration entries, and information/instructions to manually recreate the installation that the entire zip does when flashed.

I don't know how much, if any, impact this has had, but I don't do it for me. I do it for everyone other than me.

I would feel foolish trying to say this is mine and you can't have it, share it, or include it in something else.

These days, it seems the progression of Android knowledge, ideas, tricks, and solutions has slowed considerably to what it was like around 2010-2014. So many are driven by secrecy, disguising, and outright lies.

It's a real shame, too.
[Android Software Development] alok932:
Yes this file exists
[Android Software Development] Ceejay343:
Yeah i see that too. This hookup of the APK to the actual libraries, binaries and configuration files of a phone is where your magic lies, I havent seen anybody else actually succeeding in doing so on the entire net. I been around XDA for a decade too and what i also see is loads of people just using other peoples work without even bothering to acknowledge that is pissing the actual developers off to the point they don't bother anymore. It's just like life though really, isn't it. Not many people like you around that think sharing is a good thing.

I know you worked hard back in the day when hooking the Axon and the other 3 ports to Nougat and Oreo. For me i can tell you it changed the way i enjoy music radically. Together with V4A it just sounded and sounds amazing. I can also tell you you have made an impact on others too. I have had several Redmi Note phones and frequented their XDA forums, and i am not the only one (desperately) wanting a Pie/Q Atmos port. Many, many people asking for it.

So really i feel like helping other people enjoying your (and Dolby's) work basically (lol!) just as much by pointing to this thread. My concern of course is you getting swamped!
[Android Software Development] karige:
BTW, how did you manage to get LDAC processing (without reducing the audio sample rate - 96kHz on bluetooth)?
[Android Software Development] guitardedhero:
Right, I make no changes in Developer Options regarding codecs, sample rate, or bits per sample.

It just works, I don't have to do anything special or unique.

I do know Sony's Music Center app seems to be the most consistent, but other players like USB Audio Player Pro are just as consistent as well.

I wish I had an answer of some secret maneuver, but it just works.

However, I've never had LDAC processing with the 20 minutes I had experimented with it, so if using 2.7 without luck, know that I've never witnessed it process LDAC. I am specifically referring to official v4a any time v4a is mentioned except when the 2.7 unofficial build is explicitly mentioned.
[Android Software Development] satria.black:
its works . i am on pie

install DolbyAtmos-0.7281.zip + ViperFX-2.5.0.5_0.15.zip

results dolby work fine but viper not install driver.

and then i add manually viper driver . in vendor/etc/audio_effects.conf

also in system/etc/audio_effects.conf

its works like a charm now. thanks guitardedhero

sorry bad english
[Android Software Development] guitardedhero:
Thank you for the report.

Installing Dolby 0.7281 and ViperFX 0.15 in that order failed to deliver a functional v4a, is that correct?
[Android Software Development] alok932:
Is there anything wrong if this file exists?
[Android Software Development] acuicultor:
Yes same here on oneplus6 running oos Android 10, flashing ViperFX 0.14 fixes the problem but viper app is not able to read or create ViperFX folder although everything else is working fine.
[Android Software Development] guitardedhero:
No, this indicates the effect library is symlinked to the appropriate location from the module in order to be configured correctly. :good:

Thank you very much, I will look into it. :good:
[Android Software Development] acuicultor:
Driver installation is fine with this one but still unable to load or save any effect profile, let me know if you want a logcat of the issue.
[Android Software Development] alok932:
Wow thats nice. So there's hope for library to get loaded in future.
[Android Software Development] guitardedhero:
Unable to save a profile, huh? Very odd...

I feel foolish asking with your experience, but it must be asked - Have you confirmed that storage permissions are granted to v4a in Settings > Apps > System Apps > ViPER4Android?

Any toast message error?

Logs would be great. :good:

The entire module symlinks to /system and /vendor, I was wanting confirmation that the library was present in ordered to be configured properly.

I forget now the issue I was addressing, but likely an instance where the effect library was either "Null" and not loaded or not existing in the audio effects configuration symlinked to /vendor/etc/ - verifiable using the dumpsys utility for the audioflinger service:

su -c dumpsys media.audio_flinger
[Android Software Development] alok932:
I can understand.

Its the effect library is NULL. We manually replaced config files in magisk.
[Android Software Development] guitardedhero:
Please zip up the entire /data/adb/modules/dolbyatmos folder and attach it to a reply so that I can examine the installed module on your device.
[Android Software Development] alok932:
Here it is.
[Android Software Development] guitardedhero:
I just confirmed that saving a new profile and loading the profile works as expected.

My installed v4a module is version 0.13 (the last one I flashed) but version number should not make a difference with your particular issue as all components are identical except for the installation script, which doesn't involve V4A's storage directory.

Do the profile and irs directories show as being empty when attempting to load/within the v4a app?
[Android Software Development] fusob:
Fantastic work by guitarded hero. Dolby atmos zip 727 is working on redmi note 5 pro lineage 16. Thanks so much!
[Android Software Development] acuicultor:
App permissions are greyed out, profile list is empty although the folder and profiles are there.
[Android Software Development] guitardedhero:
This appears to be a permission issue with Android 10, perhaps. Although, the official v4a 2.5.0.5 does work for some Android 10 users, right?

Try replacing /data/adb/modules/viperfx/system/app/ViperFX/ViperFX.apk with the apk below while ensuring 0644 permissions before rebooting.

I merely removed the following permission from Manifest.xml and did nothing more:

[STRIKE]<uses-permission android:name="android.permission.ACCESS_SUPERUSER" />[/STRIKE]
[Android Software Development] acuicultor:
Yes official app worked for me to load profiles but ofc not with dolby, unfortunately replacing the app in 0.16 with this one still doesn't work for me.

Forgot to mention that i can't set default storage path also.
[Android Software Development] guitardedhero:
Hopefully, this zip works. A friend on Android 10 helped me figure out a solution: v4a must be installed as a userdata app in order to request storage permissions, it seems.

I've never had a reason to install anything as a userdata app with a flashable zip so I'm hoping I got the package manager command correct.

You should be able to install this over the currently installed module without issue.

Let me know what you find. :good:
[Android Software Development] Ceejay343:
Might as well delete this post, its late
[Android Software Development] guitardedhero:
The recent v4a zip seems to not install v4a to userdata for Android 10, so I removed it while I work on correcting it.
[Android Software Development] Wolfcity:
I followed this thread for a while and now I wanted to give the new Dolby for Pie a shot on my testing device (Moto G 2014) and got the message "only 64bit devices supported". That's ok, the most actual devices are running 64bit firmware but I don't remember that it's posted somewhere.

Maybe you should note that [MENTION=4445176]guitardedhero[/MENTION]. If I failed to see it I'm sorry.

Anyway keep your great work up.:good:
[Android Software Development] yyz71:
The APK installs fine and processess ?
[Android Software Development] guitardedhero:
Thank you for the suggestion. :good:

There are a few 32-bit Android Pie native Dolby Atmos systems out there right now just waiting to get ported so a 32-bit port is absolutely on the agenda.

The current testing phase for this 64-bit port feels like it is nearly finished (another week or less, perhaps) at which time I will make 32-bit support my primary focus. I just need to sculpt the script a bit more and introduce support for recovery installations.

Kinda crazy, this may very well be the most successful testing phase I have ever conducted. At times, I have found myself revisiting an old habit of awaking in a panic as I reach for the phone to see what damage I caused while asleep lol. But, it's been quiet for the most part. I don't mean lack of discussion, I mean a lack of serious issues.

I consider critical issues and bad experiences as "loud" and successful reports and praise as "quiet" so it's easy to focus and understand the critical feedback while not getting distracted by "It works!!".

So, I have had the time to "work" on "some stuff" that I'm planning for later, but 32-bit support will come first.
[Android Software Development] guitardedhero:
Android 10? Which v4a zip version? Are you able to save and load profiles?
[Android Software Development] yyz71:
Yes Android 10 pixel 4 and I was able to load and save profiles

It wasn't the zip I used it was APK the was posted a couple pages back.
[Android Software Development] guitardedhero:
Which was installed as a data app?
[Android Software Development] yyz71:
Correct
[Android Software Development] guitardedhero:
Awesome. :good:

Surely, this isn't any new information, right? Others must have found this to be the case earlier. I've been away for a while and I have yet to be on Android 10 so I fully understand how I could miss information stating Android 10 needs userdata v4a installs in order to be granted storage permissions.
[Android Software Development] Skittles9823:
Most DSPs on Android 9+ like viper 2.7.x and JDSP get installed as userapps generally.
[Android Software Development] JakunTech1010:
OK so I retry with newer version (0.68) and my phone booted:laugh:. But then I encountered an issues: Dolby Atmos Keep stopping:crying:. So uh I see your troubleshooting in this but honestly I have no idea what's written in it, can you help me? Also, did 0.68 the latest version, or is there a newer version of it? Please help me.

Also, thank you guitardedhero for making this dolby atmos. I really love your work. Thanks.
[Android Software Development] yyz71:
I'm glad I could help my friend ? Now my next accomplishment is to get Dolby Atmos working with the pixel 4 ?
[Android Software Development] guitardedhero:
I knew that to be the case for jdsp, but never heard that about anything else. Official v4a works fine in /system on Android Pie, so I dunno why the unofficial v4a mimics jdsp's unique installation limitation on Android Pie.

Of course, we are also talking about to separate topics - one to do with the installation limitation setting itself and one to do with acquiring permissions while already functioning (without /sdcard access, of course).

The latest version here is 0.7281 or 0.729. I'm not sure if I posted 0.729 and I don't even remember what I changed lol.

:highfive:

Edit*

It appears full v4a permission support for Android 10 has been accommodated in 0.18.
[Android Software Development] Qwerty182:
Need solution, please?
[Android Software Development] Skittles9823:
2.7.x.x is just an apk you install as a user app and it'll install the module from there. So it's not really required to install as a userapps but it's just more convenient to.
[Android Software Development] ramrastus:
Can I flash this file over on v4a 2.7.1.0?

And also pls send/provide download link of working da zip?
[Android Software Development] guitardedhero:
What zip(s) have you installed?
[Android Software Development] Qwerty182:
This module sir
[Android Software Development] guitardedhero:
Yeah, I had prepared a manual system installation when I tested it briefly. So pretty much the same as official v4a apk with how the apk automates the placement of the effect library, configuring the audio effect, and it's add-on script if applicable.

Yes, but results are unknown, to me at least.

Firstly, since the unofficial v4a removed the official v4a package name, you will have both installed.

Secondly, since the unofficial v4a changed the effect library name without changing the library's effect UUID, your audio effects configuration will have two effects with the same UUID when only a single instance of a UUID will be accepted and loaded - likely whichever v4a build was installed after the other ( the audio effects configuration is read from the bottom to the top and scripting effect configurations typically add to the bottom ). Therefore, you will have two apps fighting over the same UUID.

If the v4a package and library names given by the authors ( [MENTION=1569052]viper520[/MENTION] [MENTION=3901724]zhuhang[/MENTION] [MENTION=3311945]www.[/MENTION]audlabs.com <-- the most important three names which are not even found in that 2.7 OP credit section. Even the link to the original v4a thread is nowhere to be found. I think it's a bunch of ****, if you wanna know how I really feel about it. ) were respected and sustained, this wouldn't even be an issue. The apk's would likely be interchangeable with no other maneuvering necessary, but I suspect enough changes have been made to this point that this wouldn't happen today.

Alternatively, if they would just change the effect UUID ( since they've already changed everything else in attempt to separate themselves from those three names you won't see mentioned by them ) cohabitation with both V4A's would be the outcome.

Disclaimer*

In no way am I encouraging a similar mindset or generating a smear campaign. Don't ever feel bad for using what you like using. I get carried away at times and seem to invest myself too much into nerdy **** on nerdy phones.

I was simply providing answers and why those answers are what they are.
[Android Software Development] guitardedhero:
Reboot and do the following in terminal:

su -c dumpsys media.audio_flinger

Copy and paste the output generated from that command so we can assess your current audio effects configuration. :good:
[Android Software Development] Qwerty182:
Sorry, how to paste the result here? I try to paste here but failed, maybe its too long
[Android Software Development] guitardedhero:
su -c dumpsys media.audio_flinger > /sdcard/dumpsys.txt
[Android Software Development] bkkzak:
Pixel Xl BenzoRom 8.1 Magisk 15.3

TWRP install seemed fine, even showed "Dolby" and "good", but said /system failed to mount (resource busy). Boot up and no changes except the arise.prop or whatever in sdcard. I restored then tried to install with the Dolby libs but that kept bootlooping back into TWRP. So restored and can't get it to install. I have AML v4a Magisk module, as well as xposed.
[Android Software Development] Skittles9823:
Correct there is no longer a dancing eq, you can test if it's working by moving the graphic eq yourself.
[Android Software Development] Anadi315:
Magisk module

Can I install this via magisk? Is this systemless?
[Android Software Development] linx1287:
[MENTION=4445176]guitardedhero[/MENTION] Tried the newest version on HTC 10 Oreo Sense with the last props checked and still no dice, erases Boomsound Dolby as well as breaks sound. I am attaching a log this time. I hope it helps. Thanks for your continued work mate.
[Android Software Development] Coumodo:
Bootloop with LOS 15.1 & FrancoKernel + latest Magist 15.3 Beta on OnePlus 5
[Android Software Development] theduke7:
[MENTION=4445176]guitardedhero[/MENTION] on OnePlus 3 Oreo (latest beta) it installs fine and the module is there on magisk , but there's no icon or app

Dumpsys
[Android Software Development] Skittles9823:
May I suggest next time wrapping

tags around the log next time. Or better yet, uploading as a txt file or posting on hastebin for us mobile users to not have to scroll for a day.

Now onto the issue. The fact the app isn't in the drawer means that it or another module have conflicted and is causing magisk to not symlink anything. It would be the best course of action to go into magisk then tap log and swipe to magisk logs. You'll see a short bit of text displaying what magisk has done after boot and the last script there is likely the cause of the lack of symlinking.
[Android Software Development] guitardedhero:
Changelog

:

[B]20180126 -[/B]

- Various corrections of errors
introduced with the changes to
accommodate the recently added
/sdcard/arise_parameters.prop
option.
[Android Software Development] OldMidnight:
Can I update by flashing the new version on top of the old one?
[Android Software Development] guitardedhero:
Those experiencing "no Dolby app in App Drawer" are likely experiencing the failure of the entire dolbyatmos Magisk module from symlinking to /system during device boot due to one or more of the errors referenced in today's changelog above. The only obvious visual evidence for such a scenario is merely the "missing app", however, I strongly suspect everything else is missing as well as the result of a symlinking failure. Confirmation can be confirmed by the presence of a very short Magisk log within the Magisk Manager application.

One or more of these very same errors could also possibly result with a stalled recovery session unable to complete.

Today's update aims to resolve these scenarios as well as anything else discovered to be less than optimal.

I apologise for not noticing these errors before crashing last night, but viewing your reports first thing this morning alerted me to something critical introduced into one or more of yesterday's updates, so thank you for the alerts. :good:
[Android Software Development] laugeek57:
20180126-2 works fine on mi A1 :good:
[Android Software Development] Ramakrishnan ?:
I am installed normally 22jan build via twrp but its not showing in magisk module and its flashed on system but not working not processing dolby because when i connect headphone its not showing on notification when i open dolby its showing notification when i exit notification gone ? and latest 25jan-3 build showing updater script error 2 on twrp recovery i am using Redmi4x and twrp 3.2.1 plzz help me to install this as magisk module or any way to workable on my redmi 4x ?? [MENTION=4445176]guitardedhero[/MENTION]
[Android Software Development] guitardedhero:
I suggest a rom flash to clean up /system of any Dolby contents from these zip's and then try again with today's zip. :good:
[Android Software Development] guitardedhero:
Sorry guys, my bad.

However, this update should affect nearly no one. :good:

Changelog

:

[B]20180126-1 -[/B]

- Corrected, yet another, error
introduced with the latest
/sdcard/arise_parameters.prop
option that would only affect those
installations utilizing this option.
[Android Software Development] Ramakrishnan ?:
I am tried along with rom installation and i am not flashed any other mods dolby zips i am tried urs only and when i flashing via Magisk Manager its showing this is not a magisk module (plzz make it for flashing via magisk manager if possible) . . k now i am going to try new 26 jan build if its faluire i will give u logs

---------- Post added at 05:25 PM ---------- Previous post was at 05:23 PM ----------

Oops just now dwnlded 26jan build . . k dwnlding again ?